©
`
`®@
`
`U.S. Appl’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`d) determining whether an incoming messageis an incoming exception message
`
`10
`
`indicative of improper operation of the piece of remote equipment;
`
`[c)]e) if it is determined in step d) that an incoming messageis an incoming exception
`message,
`forwardingat least one outgoing exception message[s] based on the incoming
`message[s] to at least one user-defined communication device specifiable in the user-defined
`
`messageprofile,
`
`15
`
`wherein the user can remotely configure or modify the user-defined message profile by
`
`remotely accessing the computer server.
`
`A method according to Claim 1, wherein said step b) further comprises the
`(Amended)
`2.
`step of communicating [the] a plurality of incoming messages to the computerserver [central
`location] via one of a phurality of different communication media.
`
`3.
`
`(Amended)
`
`A method according to Claim 2, further comprisingthe step of [d)]
`
`normalizing the incoming messages into a uniform format to create normalized messages,
`
`wherein the outgoing exception messages are generated based on the normalized messages.
`
`A method according to Claim 1, wherein step (e) further comprises
`(Amended)
`5.
`[comprising] the step of [e)] determining whether an incoming messageis [an incoming
`exception message or] a normalstatus messageindicative of proper operation ofthe piece of
`
`remote equipment.
`
`Kindly cancel Claims 6-8 without prejudice or disclaimer.
`
`A method according to Claim [8] 1, wherein [said step h)] the remote
`(Amended)
`9.
`configuring or modifying of the message profile enabled in step c) is performed by the user via
`
`the Internet.
`
`
`
`®@
`
`U.S. Appl’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`d) determining whether an incoming messageis an incoming exception message
`
`10
`
`indicative of improper operation of the piece of remote equipment;
`
`[c)]e) if it is determined in step d) that an incoming messageis an incoming exception
`message,
`forwardingat least one outgoing exception message[s] based on the incoming
`message[s] to at least one user-defined communication device specifiable in the user-defined
`
`messageprofile,
`
`15
`
`wherein the user can remotely configure or modify the user-defined message profile by
`
`remotely accessing the computer server.
`
`A method according to Claim 1, wherein said step b) further comprises the
`(Amended)
`2.
`step of communicating [the] a plurality of incoming messages to the computerserver [central
`location] via one of a phurality of different communication media.
`
`3.
`
`(Amended)
`
`A method according to Claim 2, further comprisingthe step of [d)]
`
`normalizing the incoming messages into a uniform format to create normalized messages,
`
`wherein the outgoing exception messages are generated based on the normalized messages.
`
`A method according to Claim 1, wherein step (e) further comprises
`(Amended)
`5.
`[comprising] the step of [e)] determining whether an incoming messageis [an incoming
`exception message or] a normalstatus messageindicative of proper operation ofthe piece of
`
`remote equipment.
`
`Kindly cancel Claims 6-8 without prejudice or disclaimer.
`
`A method according to Claim [8] 1, wherein [said step h)] the remote
`(Amended)
`9.
`configuring or modifying of the message profile enabled in step c) is performed by the user via
`
`the Internet.
`
`
`
`geew
`
`_
`
`\ 8
`
`U.S. Appl’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`A method according to Claim [8] 1, wherein [step g)] the remote
`(Amended)
`10.
`configuring or modifying ofthe message profile enabledin step
`c)
`further comprises the steps
`
`of:
`
`1) selecting at least one type of user-defined communication device to which outgoing
`exception messagesare to be forwarded;
`|
`2) selecting specific user-defined communication devices of the types selected in step 1);
`
`and
`
`3) determining the content of the outgoing exception messages forwarded instep [c)] d).
`
`11.
`
`(Amended)
`
`A method according to Claim 5, wherein if the incoming messageis
`
`determinedin step [e] d) to be a normal status message from the remote equipmentindicating
`proper operation of the equipment, the method further comprises the step of i) storing the normal
`
`status message in a normalstatus memory.
`
`12.
`
`A methodaccording to Claim 11, further comprising thestepsof:
`(Amended)
`j) providing a main list having information identifying [of] all pieces of the remote
`
`equipment being monitored;
`k) comparing the contents of the normal status memory with the main list to determine
`[which pieces of remote equipment did not communicate] whether a normal status message was
`not communicated within a predetermined period of time_for any pieces of the remote equipment
`
`being monitored; and
`1) generating an outgoing exception message in accordance with the messageprofile for
`each piece of equipmentidentified in step k) as not having sent a normal status message.
`
`Kindly cancel Claims 13 and 14 without prejudice or disclaimer.
`
`
`
`@
`
`@
`
`U.S. Appl’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`A method according to Claim [14] 1, wherein the computerserver[central
`(Amended)
`15.
`location] includes a [computer] database in which a plurality of message profiles maybestored,
`and[said step h)] wherein the remote configuring or modifying of the message profile enabled in
`step c) is performedbythe user via the Internet.
`
`Kindly cancel Claim 16 withoutprejudice or disclaimer.
`
`A method according to Claim 1, wherein theat least one remote
`(Amended)
`17.
`communication devices specifiable by the message profile include at least one of a facsimile
`
`machine, an e-mail receiving device [account], a cellular telephone, a beeper, a pager, a PCS
`
`device, and a telephone.
`
`A method according to Claim 2, wherein the plurality of communication
`(Amended)
`18.
`mediaof step b) includes at least one ofa cellular telephone network,radio transmissions,
`
`telephonelines, and the Internet.
`
`A method according to Claim [13] 1, whereinstep [c)] e) further
`(Amended)
`19.
`comprises forwarding multiple outgoing exception messages to multiple user-defined
`communication devices in responseto a single incoming message in accordancewiththeuser-
`
`defined messageprofile.
`
`A method according to Claim [13] 1, wherein step [c)] e) further
`(Amended)
`20.
`comprises forwardinga single outgoing exception messageto a user-defined communication
`device in response to multiple incoming messagesin accordance with the user-defined message
`
`profile.
`
`
`
`|
`
`U.S. AppI’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`A methodaccording to Claim [13] 1, further comprising the step of [m)]
`(Amended)
`21.
`storing a plurality of user-defined messageprofiles on[at] the computer server [centrallocation].
`
`Kindly cancel Claims 22-24 withoutprejudice or disclaimer.
`
`A method according to Claim 1, wherein said step b) further comprises the
`(Amended)
`26.
`step of communicating in the incoming messagean identification code of the piece of remote
`equipment to which the incoming messagepertains [in the incoming messages].
`
`27.
`(Amended)
`A method according to Claim 26, wherein said step [c)] e) further
`comprises the step of forwarding the identification code in the outgoing exception messageto the
`at least one user-defined communication device in accordance with the user-defined message
`
`profile.
`
`A method according to Claim [7] 1, wherein step [g)] c) further comprises
`(Amended)
`28.
`the step of enabling selection ofdifferent user-defined communication devicesto receive
`outgoing exception messagesat different time periods in accordance with the messageprofile,
`the message profile being definable to have the exception messages forwarded to different
`
`specified remote communication devicesat different times.
`
`A method according to Claim [11] 5, [further comprising the step of
`(Amended)
`30.
`forwarding] wherein each normal status message includes operational information concerning the
`piece of remote equipment to which the [embedded within a] normal status message pertains.
`
`31.
`
`A system for monitoring remote equipment, comprising:
`(Amended)
`a sensor in local communication with a piece of remote equipment, said sensor detecting
`
`a state of at least one parameter of the piece of remote equipment;
`
`
`
`,
`
`U.S. AppI’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`an interface unit, locally connected to said sensor, said interface unit having a message
`
`generating mechanism; and
`
`a [central] computer server in remote communication with said interface unit, said server
`
`adapted to receive messages generated by said interface unit, said computer server having a user
`
`interface, a user being capable of remotely accessing said computer server via said user interface
`
`to remotely configure a user-defined message profile containing outgoing message routing
`
`10
`
`instructions,
`
`wherein when said sensor detects an exception condition in the piece of remote
`
`equipment,said interface unit generates an incoming exception messageindicative of the
`
`exception condition and forwards said messageto said server,
`
`and wherein said server forwardsat least one outgoing exception messageto at least one
`
`15
`
`predetermined user-defined remote communication device based on said incoming exception
`
`messageas specified in said user-defined messageprofile.
`
`32.
`
`(Amended)
`
`A system according to Claim 31, wherein said message generating
`
`mechanism ofthe interface unit forwards said incoming exception messages to said computer
`
`servervia at least one of a plurality of communication media, said media comprising at least one
`
`of a cellular telephone network,radio transmissions, telephonelines, and the Internet.
`
`35.
`
`(Amended)
`
`A system according to Claim 31, said system monitoring a plurality of
`
`pieces of equipment, each piece having an identification code, said server further comprising:
`
`a first memory on which equipmentidentification codes of all monitored equipmentare
`
`stored;
`_ asecond memory in which communication device identification codesofall of said user-
`defined communication remote devices are stored, said communication device identification
`
`codes being configured in a plurality of said user-defined messageprofiles.
`
`
`
`@
`
`, @
`
`U.S. AppI’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`A system according to Claim 35, wherein said [server further comprising
`(Amended)
`36.
`a] user interface [remotely accessible by users and] is in communication with said second
`memory[, wherein] so that users can create or edit said user-defined message profiles remotely
`
`from said server.
`
`A system according to Claim 36, wherein said user interface enables a user
`(Amended)
`37.
`to configure a user-defined messageprofile to select at least one type of [user-defined]
`communication device to which outgoing exception messagesare to be forwarded, select specific
`user-defined communication devices of the types selected, and determine the contentof said
`outgoing exception messages forwardedby said server to said user-defined communication
`
`devices.
`
`A system accordingto Claim 31, wherein said remote [user-defined]
`(Amended)
`38.
`communication devices include [communication devices including] at least one of a facsimile
`machine,an e-mail receiving device [account], a cellular telephone, a beeper, a pager, a PCS
`
`device, and a land line telephone.
`
`A system according to Claim 35, wherein said interface unit periodically
`(Amended)
`39.
` generates a normal status messageif said sensor to which said interface unit is connected detects .
`
`a normal status condition indicative of proper operation of[its] said respective piece of
`
`equipmentto which said sensor is connected [is functioning properly], said normalstatus
`message including an equipmentidentification code of said respective piece of equipment.
`
`A system according to Claim 39, said server further [comprises]
`
`(Amended)
`40.
`comprising:
`a third memory for storing said normal status messages;
`
`
`
`S
`
`©
`
`U.S. Appl’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`{means for comparingthe normalstatus memory with the mainlist and for identifying] a
`comparator processor in communication with said first and third memories adapted to identify
`whichofsaid pieces of monitored remote equipment having an identification code stored in said
`first memory did not communicate a normalstatus message stored in said third memory within a
`predeterminedperiod of time; and
`{means for generating and forwarding] a server message generator in communication with
`said comparator processor adapted to generate an outgoing exception message for each piece of
`equipmentidentified by said [comparing and identifying means] comparator processor, said
`outgoing exception message being forwardedby said serverto at least one ofsaid user-defined
`communication devices specified by [in accordance with] at least one ofsaid user-defined
`
`10
`
`messageprofiles.
`
`A system according to Claim 35, said interface unit comprisinga plurality
`(Amended)
`42.
`
`of remote interface units, wherein each ofsaid plurality of remote interface units is locally
`
`respectively connectedto a single piece of said remote pieces of equipment.
`
`A system according to Claim 35, said interface unit comprising a plurality
`(Amended)
`43.
` of remote interface units, wherein eachofsaid plurality of interface units is locally connected to
`
`a plurality of sensors whichare in turn respectively connected to a numberofsaid remote pieces
`
`of equipment.
`
`A system according to Claim 35, wherein said user-defined message
`(Amended)
`44.
`profiles are each remotely configurable by a user to cause said server to forward a plurality of
`said outgoing exception messages in responseto receipt of a single incoming exception
`message_in accordance with the user-defined message profile.
`
`
`
`e
`
`‘e
`
`U.S. AppPn No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`45.
`(Amended)
`A system according to Claim 35, wherein said user-defined message
`profiles are each remotely configurable bya user to cause said server to forward a single ofsaid
`outgoing exception messages in responseto receipt of multiple incoming exception messages_in
`accordance with the user-defined message profile.
`
`46.
`
`(Amended)
`
`A system according to Claim 40, wherein said [outgoing exception
`
`message generating and forwarding means] computer server is adaptable to forwardaplurality of
`said outgoing exception messages for each piece of equipmentidentified by said [comparing and
`identifying means]_comparator processor in accordance with the user-defined messageprofile.
`
`A system according to Claim 47, wherein said outgoing exception
`(Amended)
`48.
`message comprises exception information andidentification information concerning said piece of
`remote equipment to which said normalstatus message pertains.
`
`49.
`(Amended)
`A system according to Claim 39, wherein said normalstatus message
`further comprises operational information ofsaid piece of remote equipment to which said
`
`normalstatus message pertains.
`
`50.
`
`(Amended)
`
`A system according to Claim 40, said computer server further comprising
`
`a fourth memory upon which outgoing exception messagesare stored.
`
`Kindly add thefollowing new claims.
`
`—51. Amethod for monitoring remote equipment comprisingthestepsof:
`a) determining a state of at least one parameterofat least one piece of the remote
`equipment;
`b) communicating a message indicative of the state to a computerserver as an incoming
`message, the incoming message having a respective incoming format,
`
`
`
`e
`
`e
`
`U.S. Appl’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`c) normalizing the incoming message to form a corresponding normalized message
`
`having a predetermined uniform format;
`d) storing the normalized message in a normalized message database on the computer
`
`Server;
`
`10
`
`15
`
`e) determining from the incoming message whetherat least one exception message
`related to the incoming messageis to be sent to at least one remote communication device
`
`specified by a plurality of message profiles stored at the computer server;
`f) if it is determinedin step e) that at least one exception messagerelated to the incoming
`messageis to besent, deriving the at least one exception message from the stored normalized
`message correspondingto the related incoming message and the messageprofiles, the at least
`one exception message derived thereby having a respective format suitable for reception by theat
`least one remote communication device to which the at least one exception messageis to be seni;
`
`and
`
`g) sending the at least one exception message derived in step f) to the at least one remote
`
`20
`
`communication device specified by the message profiles,
`
`wherein the messageprofiles may be created or modified at least in part by a user by
`
`remote access of the computerserver.
`
`52.|Asystem for monitoring remote equipment, comprising:
`a sensor in communication with a piece ofthe remote equipmentfor detecting thestate of
`at least one parameter thereof;
`an interface unit, coupledto said sensor, said interface unit having a message generating
`
`mechanism for generating messagesindicative of the state of the at least one parameter of the
`
`piece of the remote equipment; and
`a computerserver in communication with said interface unit, said server comprising:
`a message interface for receiving messages generated bysaid interface unit;
`
`10
`
`
`
`U.S. Appl’n No. 09/317,235
`Proposed Amendment
`FOR INTERVIEW PURPOSES ONLY
`
`10
`
`15
`
`20
`
`25
`
`30
`
`a message normalizer for normalizing each one of the messages received from the
`interface unit to form corresponding normalized messages having a predetermined uniform
`
`format;
`
`a normalized message database for storing normalized messages, including
`
`normalized messages from the message normalizer;
`
`a messageprofile database for storing a plurality of message profiles;
`a message processorfor determining from each one of the messages received from
`
`the interface unit whether at least one exception messagerelated to the received messageis to be
`
`sent to at least one remote communication device specified by the messageprofiles;
`
`an exception message generator for deriving the at least one exception message
`
`determined to be sent by the messageprocessorto the at least one remote communication device,
`the at least one exception message being derived from a normalized message correspondingto
`the related message received from the interface unit and the messageprofiles, the at least one
`exception message derived thereby havingat least one respective format suitable for reception by
`the at least one remote communication device to which the at least one exception messageis to
`
`be sent;
`
`a messageinterface for sending the at least one exception message derived by the
`exception message generatorto the at least one remote communication device specified by the
`
`message profiles; and
`a user interface for enabling a user at a remote location to create or modify atleast
`
`a portion of the messageprofiles in the message profile database,
`wherein whensaid sensor detects an exception condition in the piece of remote
`equipment, said intertace unit generates an incoming messageindicative ofthe exception
`conditionand forwards said messageto said server.—
`
`11
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
