throbber
U.S. AppI’n No. 09/317,235
`Amendment
`
`a) determininga state of at least one parameterofat least one piece of the remote
`
`equipment;
`
`b) communicating [messages regarding] a message indicative of the state from the piece
`
`of remote equipment to a computerserver [central location] as an incoming message[s]; [and ]
`
`c) enabling a user to remotely configure or modify a user-defined message profile
`
`containing outgoing message routing instructions, the user-defined message profile being
`
`storable on the computerserver;
`
`d) determining whether an incoming messageis an incoming exception message
`
`10
`
`indicative of improper operation of the piece of remote equipment;
`
`hd
`Col
`
`[c)]e) if it is determined in step d) that an incoming messageis an incoming exception
`
`message, forwarding at 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.
`
`2.
`
`(Amended)
`
`A method according to Claim 1, wherein said step b) further comprises the
`
`step of communicating[the] a plurality of incoming messages to the computer server [central
`
`location] via one of a plurality of different communication media.
`
`3.
`
`(Amended)
`
`A methodaccording to Claim 2, further comprising the step of [d)]
`
`normalizing the incoming messagesinto a uniform format to create normalized messages,
`
`wherein the outgoing exception messagesare generated based on the normalized messages.
`
`
`5.
`(Amended)
`A method according to Claim 1, wherein step (e) further comprises
`b- [comprising] the step of [e)] determining whether an incoming messageis [an incoming
`Cet
`
`ve
`
`

`

`L
`
`U.S. AppI’n No. 09/317,235
`Amendment
`
`exception message or] a normal status messageindicative of proper operation of the piece of
`
`(yo
`Canbh.
`
`remote equipment.
`
`
`Kindly caxCélClaims&3prithoutprejudice or disclaimer.
`
`.
`
`(H
`
`A method according to Claim [8] 1, wherein [said step h)] the remote
`(Amended)
`K
`configuring or modifying of the message profile enabled in step c) is performed bytheuservia
`
`the Internet.
`
`Ww
`
`(Amended)
`
`A method according to Claim [8] 1, wherein [step g)] the remote
`
`configuring or modifying of the message profile enabled in 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 forwardedin step [c)] d).
`
`A method according to Claim 5, wherein ifthe incoming messageis
`oO (Amended)
`determined in step [e] d) to be a normal status message from the remote equipmentindicatin
` roper operation of the equipment, the method further comprisesthe step of{) storing the normal
`A
`status message in a normal status memory.
`
`A method according to Claim uw further comprising the stepsof:
`1 (Amended)
`J p providing a main list having information identifying [of] all pieces ofthe remote
`equipmentbeing monitored;
`
`WV
`
`

`

`2
`
`U.S. AppI’n No. 09/317,235
`Amendment
`
`| 3
`
`k) comparing the contents of the normal status memory with the mainlist to determine
`
`[which pieces of remote equipment did not communicate] whether a normal status message was
`
`5
`
`e not communicated within a predeterminedperiod oftime_for any pieces ofthe remote equipment
`{jbl
`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 normalstatus message.
`
`
`SinacaticelClaims15andIdwithoutprejudiceordisclaimer.
`
`
`\O
`Ss
`
`(Amended)
`
`A method according to Claim [14] 1, wherein the computer server [central
`
`iiyp
`
`location] includes a [computer] database in which aplurality ofmessage profiles may bestored,
`
`and [said step h)] wherein the remote configuring or modifying of the message profile enabled in
`
`step c) is performed by the user via the Internet.
`
`
`cindy carleclClaim 16 withoutprejudiceordisclaimer.
`
`4% (Amended)
`
`A methodaccording to Claim 1, wherein the at least one remote
`
`
`
`communication devices specifiable by the message profile includeat least one of a facsimile
`
`machine, an e-mail receiving device [account], a cellular telephone, a beeper, a pager, a PCS
`
`Uso
`biyf
`
`‘
`
`device, and a telephone.
`oe
`1.
`
`(Amended)
`
`:
`A method according to Claim 2, wherein the plurality ofcommunication
`
`media of step b) includesat least one of a cellular telephone network, radio transmissions,
`
`telephone lines, and the Internet.
`
`

`

`U.S. AppPn No. 09/317,235
`Amendment
`
`19
`
`(Amended)
`
`A method according to Claim [13] 1, whereinstep [c)] e) further
`
`comprises forwarding multiple outgoing exception messages to multiple user-defined
`
`communication devices in responseto a single incoming message in accordance with the user-
`
`defined messageprofile.
`
`(Amended)
`
`A method according to Claim [13] 1, wherein step [c)] e) further
`
`42
`
`0
`
`comprises forwarding a single outgoing exception message to a user-defined communication
`
`device in response to multiple incoming messages in accordance with the user-defined message
`
`(ls
`Al
`
`profile.
`
`2% (Amended)
`
`A methodaccording to Claim [13] 1, further comprising the step of [m)]
`
`storing a plurality of user-defined message profiles on[at] the computer server [central location].
`
`Yicinay cancel Claims22-24Withoutprejudice or disclaimer.
`
`4
`26.
`
`(Amended)
`
`A method according to Claim 1, wherein said step b) further comprises the
`
`step of communicating in the incoming message an identification code of the piece of remote
`
`ly
`Opt.
`
`equipmentto which the incoming messagepertains [in the incoming messages].
`8
`27.
`
`|
`A method according to Claim 267whereinsaid step [c)] e) further
`
`(Amended)
`
`comprises the step of forwarding the identification code in the outgoing exception message to the
`
`at least one user-defined communication device _in accordance with the user-defined message
`
`profile.
`
`(
`ZB.
`
`(Amended)
`
`A method according to Claim [7] 1, wherein step [g)] c) further comprises
`
`the step of enabling selection of different user-defined communication devices to receive
`
`outgoing exception messagesat different time periods in accordance with the messageprofile,
`
`O&
`
`

`

`U.S. Appl’n No. 09/317,235
`Amendment
`
`the message profile being definable to have the exception messages forwarded to different
`
`My
`Cb
`
`specified remote communication devices at different times.
`
`Ww.
`
`(Amended)
`
`A method according to Claim [11] 5, [further comprising the step of
`
`forwarding] wherein each normalstatus message includes operational information concerning the
`
`piece of remote equipment to which the [embedded within a] normal status message pertains.
`
`We
`
`(Amended)
`
`A system for monitoring remote equipment, comprising:
`
`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;
`
`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
`
`instructions,
`
`wherein whensaid 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
`
`predetermined user-defined remote communication device based on said incoming exception
`
`15
`
`message as specified in said user-defined messageprofile.
`
`Le
`94
`3X (Amended)Asystem according to Claim 31, wherein said message generating
`mechanism ofthe interface unit forwards said incoming exception messages to said computer
`
`.
`
`a
`
`

`

`6
`
`@
`
`U.S. AppI’n No. 09/317,235
`Amendment
`
`dbl
`
`servervia at least one ofaplurality ofcommunication media, said media comprising at least one
`
`of a cellular telephone network, radio transmissions, telephonelines, and the Internet.
`
`
`iy:
`A system according to ClaimPYsaid system monitoring a plurality of
`(Amended)
`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;
`
`a second memory in which communication device identification codes ofall of said user-
`
`defined communication remote devices are stored, said communication device identification
`
`codes being configured in a plurality of said user-defined message profiles.
`
`A system according to Claim 34% wherein said [server further comprising
`(Amended)
`Bo
`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
`
`Ms9
`ar
`([!
`,
`
`from said server.
`ig
`A system according to Claim 36, wherein said user interface enables a user
`7.
`(Amended)
`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 contentofsaid
`
`outgoing exception messages forwardedbysaid server to said user-defined communication
`
`devices.
`
`21
`A system according to Claim 30wherein said remote [user-defined]
`(Amended)
`28.
`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.
`
`KY
`
`

`

`‘
`‘,
`
`U.S. AppPn No. 09/317,235
`Amendment
`
`39
`
`(Amended)
`
`A system according to Claim3%wherein said interface unit periodically
`
`generates a normal status messageif said sensor to which said interface unit is connected detects
`
`a normalstatus 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.
`
`(
`by
`
`(Amended)
`
`Oo
`A system according to Claim said server further [comprises]
`
`comprising:
`
`a third memory for storing said normalstatus messages;
`
`[means for comparing the normal status memory with the mainlist and for identifying] a
`
`comparator processor in communication with said first and third memories adapted to identif
`
`whichof said pieces of monitored remote equipment having an identification code stored in said
`
`first memory did not communicate a normal status messagestored in said third memory within a
`
`predeterminedperiod of time; and
`
`i)
`Ot
`
`{means for generating and forwarding] a server message generator in communication with
`
`10
`
`said comparator processor adapted to generate an outgoing exception messagefor each piece of
`
`equipmentidentified by said [comparing and identifying means]_comparator processor, said
`
`outgoing exception message being forwarded bysaid serverto at least one of said user-defined
`
`communication devices specified by [in accordance with] at least one of said user-defined
`
`message profiles.
`
`A system according to Claim345 said interface unit comprisinga plurality
`35u (Amended)
`
`of remote interface units, wherein each ofsaid plurality of remote interface unitsis locally
`
`respectively connected to a single piece of said remote pieces of equipment.
`
`af
`at A system accordingto Claim357said interfaceunit comprisingaplurality(Amended)
`Gjit
`
`
`
`
`
`of remote interface units, wherein each ofsaid plurality of interface units is locally connected to
`
`

`

`baw
`
`-
`
`@
`
`U.S. AppP’n No. 09/317,235
`Amendment
`
`
`a plurality of sensors which are in turn respectively connected to a numberofsaid remote pieces
`
`of equipment.
`
`49
`
`(Amended)
`
`A system according to Claim34, wherein said user-defined message
`
`profiles are each remotely configurable by a user to cause said server to forward a plurality of
`
`said outgoing exception messagesin responseto receipt of a single incoming exception
`
`message_in accordance with the user-defined message profile.
`
`nd’
`
`Hb

`A system according to Claim 34, wherein said user-defined message
`(Amended)
`oy
`profiles are each remotely configurable by a user to cause said server to forward a single ofsaid
`
`outgoing exception messagesin responseto receipt of multiple incoming exception messages_in
`
`accordance with the user-defined messageprofile.
`
`4
`46.
`
`(Amended)
`
`6
`A system according to Claim 46, wherein said [outgoing exception
`
`message generating and forwarding means] computerserver is adaptable to forward a plurality of
`
`said outgoing exception messages for each piece of equipmentidentified by said [comparing and
`
`identifying means} comparator processor in accordance with the user-defined message profile.
`
`
`
`A system according to Claim4% wherein said outgoing exception
`Bh (Amended)
`message comprises exception information andidentification information concerning said piece of
`
`remote equipment _to which said normal status message pertains.
`
`bY (Amended)
`
`A system according to Claim 39;wherein said normalstatus message
`
`O
`
`further comprises operational information of said piece of remote equipment to which said
`
`KID
`ditt
`
`normal status message pertains.
`
`

`

`U.S. AppP’n No. 09/317,235
`Amendment
`
`kip (Amended)
`A system according to Claim 46, said computer server further comprising
`[!bo a fourth memory upon which outgoing exception messagesare stored.
`
`
`
`Ciinaty agd thefollowing newclaims.
`
`,
`
`a) determininga state of at least one parameterofat least one piece of the remote
`
`equipment;
`
`b) communicating a messageindicative of the state to a computer server as an incoming
`
`5
`
`message, the incoming message havinga respective incoming format;
`
`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
`
`"_
`
`g) determining from the incoming message whétherat least one exception message
`
`(i//
`(art
`
`related to the incoming messageisto be sent to at least one remote communication device
`
`specified by a plurality ofmessage profiles stored at the computer server;
`f) ifit is determinedin step e) that at least one exception messagerelated to the incoming
`
`messageis to be sent, deriving the at least one exception message from the stored normalized
`
`15
`
`message corresponding to the related incoming message and the messageprofiles, theat least
`
`one exception message derived thereby having a respective format suitable for reception by the at
`
`least one remote communication device to which the at least one exception messageis to be sent;
`
`and
`
`g) sending the at least one exception messagederived in step f) to the at least one remote
`
`20
`
`communication device specified by the messageprofiles,
`
`wherein the message profiles may be created or modified at least in part by a user by
`
`remote access of the computer server.
`
`10
`
`B52
`
`

`

`U.S. Appl’n No. 09/317,235
`Amendment
`
`8 A system for monitoring remote equipment, comprising:
`
`a sensor in communication with a piece of the remote equipmentfor detecting the state of
`
`at least one parameter thereof;
`
`an interface unit, coupled to said sensor, said interface unit having a message generating
`
`mechanism for generating messagesindicative ofthe state of the at least one parameter of the
`
`piece of the remote equipment; and
`
`a computer server in communication with said interface unit, said server comprising:
`
`a message interface for receiving messages generated by said interface unit;
`
`a message normalizer for normalizing each one of the messages received from the
`
`10
`
`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;
`
`Oh
`
`a messageprofile database for storing a plurality of messageprofiles;
`
`a message processor for determining from each one of the messagesreceived from
`
`the interface unit whetherat 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 message processorto the at least one remote communication device,
`
`20
`
`the at least one exception message being derived from a normalized message corresponding to
`
`the related message received from the interface unit and the messageprofiles, the at least one
`
`exception message derived thereby having at 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;
`
`25
`
`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
`
`11
`
`a\
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

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.

throbber

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.

Become a Member

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

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket