throbber
5,894,506
`[11] Patent Number:
`[:9]
`Umted States Patent
`
`Pinter
`[451 Date of Patent:
`Apr. 13, 1999
`
`US005894SO6A
`
`6/1982 Levine ................................... 3-101311
`4.336.524
`4382256 M983 Nag-ua
`3w!8?5.44
`5.321486
`7.-‘I994 WISE et 9].
`3793210
`5331366
`1n99s Sflb
`_ arose
`5.539.303 mesa Innagx.
`.. 3796‘?
`
`OTHER PUBLICATIONS
`
`
`
`......
`etfl
`
`[54] METHOD AND APPARATUS FOR
`GENERATING AND COMMUNICATING
`MESSAGES BE1-WEE” sUBsC 10
`AN ELECTRONIC MSSAGING NETWORK
`Inventor: Gregory J. Pinter. Brandon. Miss.
`
`[75]
`
`Assignee: SkyTel Communications. Inc.
`lncbon. Miss.
`
`Appl. No.: 081708.696
`
`Sep. 5. 1996
`
`
`
`Filed:
`
`Int. Cl." ..
`US. Cl.
`
`.................... HMM U64
`3798823: 37983.15:
`37993.24: 34-0I'325.44: 455}?! 12
`37967. 88. 39.
`Field of Seanch
`379/93.24. 93.25. 93.26: 45581.3. 31.2:
`395f200.3. 200.31. 200.34. 200.37. 200.41
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`1731
`
`['21]
`
`[22]
`
`[51]
`[52]
`
`[531
`
`[5 6]
`
`"New Radio Paging System.“ by Mitsunu Komtn-a et al.
`Japan Telecommunications Review. Jul. 1977. vol. 19. No.
`3. pp. '21? and 220-225.
`"Paging System Broadcasts Nationwide on FM Radio Chan-
`nel." Electronics International. Jan. 4. 1979. vol. 52. No. 1.
`pp. 67-68.
`“A Development Project of a Pockctsize Receiver for n
`Nationwide Paging System." by Kari Kiishinen et nL IEIE.
`1979. pp. 383-387.
`
`Primary E.ramr'ner—Fan S. Tsnng
`Adams}; Agent. or F£rm—Finnegan. Henderson. Farabow.
`Garrett 8: Dunner. L.L.P.
`
`[57]
`
`ABSTRACT
`
`An electronic messaging network comprises 3 network
`operation center and plural message tenninals. all including
`memories for storing corresponding files of canned mes-
`sages and associated message codes. To send a canned
`message. a calling party selects a canned message stored at
`one message terminal and trnnsrnits the assigned message
`code to a receivingparty at another message texnninal via the
`network operation center. The receiving terminal retrieves
`the selected canned message from its memory using the
`received message code for display to the receiving party.
`Files of canned responses and associated response codes
`may also be stored in the memories at the terminals and
`network operation center to allow the exchange of selected
`canned response options in conjunction with canned mes-
`sages to be in response code form.
`
`21 Claims, 7 Drawing Sheets
`
`36
`
`RETRIEVE
`CANNED
`RESPGNSE
`I OP‘T|-UN FILE
`
`.
`T _. L.
`DIE-PLAY CANNED
`RESPCFNSE
`OPTION FILE
`
`38
`
`
`
`
`
`
`ID
`
`SELECT
`CANNED
`RESPONSE
`OFTIDN5
`
`
`
`RETPJEVE CCIDCS
`FOR SELECT ED
`
`
`
`RESPONSE
`OFTIONS
`
`
`42
`
`
`
`ENTER
`_“____.
`5 PAHAMETERIS:
`
`
`
`
`
`APPLE 1001
`
`3.973.676
`3,5l3.443
`3.714.375
`3.818.145
`3,84-6.783
`3.35l,2$l
`3.944.724
`3,976,995
`3.95-1,775
`4,010,463
`4.0 10.461
`4.13.1240
`4.173.-175
`‘l.l9'.n'.526
`4249.165
`-1.263.430
`4,330.".-'80
`
`...
`..
`
`-4!l96I Spencer ...................... 31-W154
`5:I"l9'?D Andersen
`. “W154
`l.:I'l9'.r'3 Stove:
`.....
`l'.I'9f2
`61197-I Hallway
`.. 179M-I
`ll:’l9'i'4 Apsell et al.
`3405]!
`1131974 Vvlgller El al.
`.. 3355
`3fl9'r'6 Kilby et al.
`.
`. 17814.!
`8fl9'i6 Sdlifityell
`340037
`l0I"l9T§ [Ethel el Ill.
`32555
`3Il9':'7
`3!I 977
`'Hl979
`l2Il9'l'9
`4119813
`211981
`411981
`511982
`
`
`
`RETRIEVE
`CANNED
`
`MESSAGE FlI..E
`
`22-
`
`
`
`
`
`Jul
`
`D|'5F'LA‘f
`CANNED
`MESSAGE FILE
`
`
`
`
`
`SE1. ECI
`CANINED
`ME S5-N35
`
`'15 --~~
`
`RE lRlE\tE
`CODE FOR
`
`SELECTED
`CANNED MESSAGE
`
`
`
`
`CODES AME
`
`: Pnsnmeremsi
`
`TRJNSMIT
`3. -._J_
`MESSAGE
`comes a
`I PAFl.A||oEETEl1iS)
`I
`to Noe 12
`
`
`
`
`‘J2
`
`APPLE 1001
`
`1
`
`

`
`Apr. 13, 1999
`
`Sheet 1 of 7
`
`605.,493,5
`
`._<z__>_mm:Goz.mmfizmo
`
`oz_>_mom_mxmoafizoz_._._<o
`
`
`zo_»<mmn_o4<z__>_mmF
`
`F.03
`
` US.Patent
`
`2
`
`

`
`U.S. Patent
`
`Apr. 13, 1999
`
`Sheet 2 of 7
`
`5,894,506
`
`
`
`SELECT
`CANNED
`RESPONSE
`
`OPTIONS
`
`RETRIEVE CODES
`FOR SELECTED
`RESPONSE
`
`OPTIONS
`
`35
`
`RETRIEVE
`CANNED
`RESPONSE
`
`OPTION FILE
`
`33
`
`DISPLAY CANNED
`RESPONSE
`OPTION FILE
`
`22
`
`24
`
`26
`
`28
`
`RETRIEVE
`CANNED
`MESSAGE FILE
`
`DISPLAY
`CANNED
`MESSAGE FILE
`
`SELECT
`CANNED
`MESSAGE
`
`RETRIEVE
`
`
`
`CODEFOR
`SELECTED
`CANNED MESSAGE
`
`30
`
`ENTER
`PARAMETER(S)
`
`44
`
`ENTER
`PARAMETER(S)
`
`32
`
`34
`
`COMPKE
`MESSAGE
`CODESAND
`
`PARAMETER(S)
`
`TRANSMH'
`
`MESSAGE
`
`TO NOC 12
`
`CODES 8.
`PARAMETER(S)
`
`UWG3)
`
`FIG. 2
`
`3
`
`

`
`US. Patent
`
`Apr. 13, 1999
`
`Sheet 3 of 7
`
`5,894,506
`
`54
`
`
`
`RECEIVE MESSAGE
`CODES AND PARAMETER(S)
`FROM TERMINAL ‘I0
`
`
`
`50
`
`
`
`STORE
`
`IDENTIFY
`TERMINALS 10 & 14
`
`
`
`TERMINAL |DENT|T|ES
`
`
`
`TRANSMIT
`MESSAGE (CODE
`OR TEXT) TO
`TERMINAL 14
`
`58
`
`RETRIEVE CANNED
`MESSAGE 8: RESPONSE
`OPTIONS TEXT
`
`
`
`60
`
`(FIG 4)
`
`FIG. 3
`
`4
`
`

`
`U.S. Patent
`
`Apr. 13, 1999
`
`Sheet 4 of 7
`
`5,894,506
`
`70
`
`
`
`RECEIVE MESSAGE
`
`FROM NOC 12
`
` RETRIEVE
`76
`MESSAGE 8:
`RESPONSE
`OPTIONS TEXT
`
`
`
` DISPLAY
`74
`MESSAGE &
`RESPONSE
`
`
`
`OPTIONS TEXT
`
`SELECT
`
`RESPONSE OPTION
`
`80
`
`
`
`
`TRANSMIT
`SELECTED
`
`RESPONSE
`
`
`
`OPTION TO
`NOC 12
`
`
`
`
`
`(TO FIG 5)
`
`FIG. 4
`
`5
`
`

`
`US. Patent
`
`Apr. 13, 1999
`
`Sheet 5 of 7
`
`5,8 94,506
`
`RECEIVE SELECTED
`RESPONSE OPTION
`FROM TERMINAL ‘I4
`
`82
`
` TEXT OR
`
`83
`
`
`TEXT
`
`CODE
`RECEIVED?
`
`CODE
`
`84
`
`
`
`
`
`TRANSM IT
`CODE
`OR TEXT?
`
`as
`
`
`
`
`
`
`RETRIEVE
`SELECTED
`REPONSE
`OPTION TEXT
` TO TERMINAL 10 FROM MEMORY
`
`
`
`TRANSMIT
`SELECTED
`RESPONSE OPTION
`(CODE OR TEXT)
`
`
`
`
`RECEIVE SELECTED
`RESPONSE OPTION
`FROM Not: 12
`
`90
`
`92
`
`94
`
`95
`
`CODE
`OR
`CODE
`TEXT
` RETRIEVE SELECTED
`
`RESPONSE OPTION
`TEXT
`
`
`DISPLAY
`SELECTED
`
`
`RESPONSE
`
`
`OPTION TEXT
`
`
`
`FIG. 5
`
`6
`
`

`
`U.S. Patent
`
`Apr. 13, 1999
`
`Sheet 6 of 7
`
`5,894,506
`
`UPDATE CANNED
`IVIESSAGEIRESPONSE
`OPTION FILES
`
`100
`
`STORE UPDATED
`CANNED FILES
`IN NOC
`
`TRANSMIT UPDATED
`CANNED FILES
`TO TERMINALS
`
`IN MESSAGING
`
`GROUP
`
`"I02
`
`‘I04
`
`RECEIVE UPDATED
`CANNED FILES
`
`105
`
`STORE UPDATED
`CANNED FILES
`
`108
`
`FIG. 6
`
`7
`
`

`
`
`
`
`
`QMNm_.mm>_mommE:mm_nm__mwmn_VowN_.><._n_m_oN:EQ:
`
`
`
`
`
`U
`
`P
`
`D._A
`
`W
`
`H.._....m
`
`5,894,506
`
`...ofl
`
`n_<n_>mv.mm:EE0M92
`mm.E_>_mz<Em:.Emm?
`
`smo<mmms_
`Mxm..__n=aoo
`
`8
`
`8
`
`
`

`
`5.894.506
`
`1
`METHOD AND APPARATUS FOR
`GENERATING AND COMIVIUNICATING
`MESSAGES BETWEEN SUBSCRIBERS ‘F0
`AN ELECTRONIC MESSAGING NETWORK
`
`FIELD OF THE INVENTION
`
`The present invention relates to electronic information
`services and more particularly to the exchange of electronic
`messages among subscribers to an electronic messaging
`network.
`
`BACKGROUND OF THE INVENTION
`
`As more and more people sign on to information
`networks. congestion of the communications links compris-
`ing these networks. both wircline and wireless. and the
`consequential transmission delays become increasingly sig-
`nificant problems. Faster transmission rates. data compres-
`sion techniques. and more eflicient spectrum utilization are
`among the approaches that have been considered. and to
`some extent
`implemented.
`to increase the capacities of
`communications links.
`
`One area of particularly rapid growth is the electronic
`messaging field. More and more people are moving about
`with portable devices. such as laptop computers and portable
`digtal devices. which can be economically equipped to
`function as message sendingireceiving terminals. Mcreovat.
`wireless paging hardware. software. and support services are
`being upgraded to accommodate two-way messaging. That
`is. portable pagers are being developed not only to receiving
`paging messages. but also to send back a signal acknowl-
`edging receipt of a paging message or even a message
`answering the received paging message. While such
`upgraded paging services are highly desirable. they can
`severely strain the capacity of wireless paging channels.
`SUMMARY OF THE INVENTION
`
`.15
`
`25
`
`35
`
`It is accordingly a principle object of the present invention
`to provide an improved electronic messaging network and
`method. wherein communications link capacity is conserved
`by transtnitting certain messages with an improved degree of
`message compression.
`Particularly in the case of radio paging. many paging
`messages consists of a relatively small nurnba of common
`phrases. such as “I am on the way home". “I am working
`late“. “Can we meet for lunch". etc. This being the case. such
`commonly used phrases can be treated as “canned” mes-
`sages that can be replaced by short message codes as simple
`as. for ettarnple. one or several ASCII characters.
`The present invention takes advantage of this fact by
`providing. in accordance with one preferred embodiment. a
`method of communicating messages between subscribers of
`an electronic messaging network. comprising the steps of
`maintaining. at a network operation center. a first file of
`canned messages individually retrievable using unique-
`abbreviated message codes respectively assigned to the
`auined messages: maintaining. at a terminal of a calling
`subscriber. a second file of canned messages corresponding
`to the firs! file: selecting an appropriate canned message
`from the second file for transmission to :1 terminal of a
`designated receiving subscriber: sending the message code
`assigned to the selected canned message to the network
`operation center; retrieving the selected canned message
`from the first file using the message code received from the
`calling subscriber terminal; and communicating the selected
`canned message to the designated receiving party terminal
`where it is displayed.
`
`2
`In accordance with a feature of the present invention. the
`fir-st and second canned message files may be updated. either
`by the network operation center or from a subscriber termi-
`nal in order to customize the canned messages according to
`the needs of a particular group or organization of subscrib-
`ers. In addition. the canned messages may be phrased to
`accept the addition of one or more parameters. which are
`entered at the calling subscriber terminal and then included
`with the message codes sent to the network operation center.
`The selected canned messages are retrieved from the first file
`using the message codes and communicated to terminals of
`designated receiving subscribers with the added parameters
`incorporated in the bodies of the canned messages.
`The present invention also accommodates the addition of
`multiple response options to the canned messages selected
`by calling subscribers. The multiple response options are
`then included with the canned message codes sent to the
`network. operation center. The selected canned messages are
`then retrieved from the first file and communicated to the
`designated receiving subscribas. together will: the added
`multiple response options. The receiving parties then select
`the appropriate one of the multiple options for transmission
`back to the appropriate calling subscribers via the network
`opaation center. The multiple response options may also be
`canned responses maintained in files at the network opera-
`tion centcr and the subscriber terminals and. like the canned
`messages. have assigned response codes that are handled in
`the same manner as the message codes.
`In accordance with another feature of the present
`invention. corresponding canned message files are also
`maintained at receiving subscriber terminals. such that the
`canned messages may be communicated to the receiving
`subscribers in message code form. The received message
`codes are then used to retrieve the appropriate canned
`messages and multiple response options lrom stored files.
`and displayed by the receiving party terminals.
`Additional features and advantages of the invention will
`be set forth in the description which follows. and in part will
`be apparent from the description. or may be learned by
`practice of the invention. The objectives and other advan-
`tagcs of the invention may be realized and attained by the
`method and apparatus particularly pointed out in the written
`description and the appended claims. as well as the accom-
`panying drawings.
`It will be understood that both the foregoing general
`description and the following detailed description are exem-
`plary and explanatory and are intended to provide further
`explanation of the invention as claimed.
`The accompanying drawings are intended to provide a
`further understanding of the invention and are incorporated
`in and constitute a part of the specification. illustrate a
`preferred embodiment of the invention. and. together with
`the description. serve to explain the principles of the inven-
`tron.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a block diagram illustrating an electronic mes-
`saging network utilized in the practice of a preferred
`embodiment of the present invention;
`FIG. 2 is a flow diagram illustrating the operation of a
`calling terminal in the network of FIG. 1 when sending a
`message in accordance with one embodiment of the inven-
`tion;
`
`65
`
`FIG. 315 a flow diagram illustrating the operation of the
`network operation center (NOC) in the network of FIG. 1
`when relaying a message from the calling terminal to the
`receiving terminal in accordance with one embodiment of
`the invention:
`
`9
`
`

`
`5.894.506
`
`3
`FIG. 4 is a now diagram illustrating the operation of the
`receiving terminal in the network of FIG. 1 when receiving
`a message in accordance with one embodiment of the
`invention;
`FIG. 5 is a flow diagram illustrating the operations of the
`NOC and the calling terminal regarding a message response
`from the receiving terminal in accordance with one embodi-
`ment of the invention:
`
`FIG. 6 is a flow diagram illustrating the network operation
`to update message tiles in the bloc and the callingireoeivlng
`terminals in accordance with one embodiment of the inven-
`tion;
`
`FIG. 7 is a schematic block diagram of the calling
`terminal of FIG. 1 in accordance with one embodiment of
`the invention: and
`FIG. 8 is a schematic block diagram of the NOC of FIG.
`1 in accordance with one embodiment of the invention.
`
`Corresponding reference numerals refer to like parts
`throughout the drawings.
`DETAILED DE‘iCR]Pi'l0N OF THE
`PREFERRED EMBODIMENT
`
`As seen in FIG. 1. an electronic messaging network in
`accordance with a preferred embodiment of the present
`invention includes. at calling party terminal 10, a network
`operation center (NOC) 12. and a receiving party terminal
`14. It will be appreciated that. in practice. the network will
`include pluralities of calling and receiving party tutninals.
`The calling party tenninal 10 is connected to NOC 12 by a
`communications link 16. which may take the form of land
`line (e.g.. phonclines}. a direct computer link. a wireless
`link. or a satellite linlc NOC 12 is preferably connected to
`receiving party terminal 14 by a wireless communications
`link 18. An example of a preferable network operation centa
`that can be implemented in the practice of the present
`invention is the network operation center being developed
`by Destineer Corporation of Jackson- Miss. to handle their
`Nationwide Wireless Network {NWN) paging services. ‘that
`NOC and a preferred two—way wireless network for imple-
`menting the present invention are described in U.S. patent
`application Ser. Number 03124216. the contents of which
`are hereby incorporated by reference.
`In accordance with the present invention. calling lamina]
`10 includes a stored file of canned messages and associated
`canned message codes. Referring to the flow chart of FIG.
`2. when a calling patty wishes to send a message to a
`receiving party at terminal 14 (FIG. 1). the terminal retrieves
`the file of the canned messages from storage (step 22) and
`displays the file to the calling party (step 24). The calling
`party browscs through the file to determine if the text of any
`of the canned messages is appropriate to convey the par-
`ticular message that the calling party wishes to send to the
`receiving party. If an appropriate canned message is noted.
`the milling party selects this canned message (step 26) using
`suitable pointing means. such as a mouse. cursor. etc. Based
`on the canned message selection. terminal 10 retrieves the
`associated canned message code from the file {step 28).
`If the selected canned message calls for the inclusion of
`a pararneterts). such as. for example. time. date. phone
`number. etc.. the calling party enters a desired para.meter(s).
`using an appropriate entry device. such as a keypad (step
`30). The ceiling terminal 10 compiles the retrieved message
`code associated with the selected canned message with an
`appropriate indicator code. calling and receiving terminal
`addresses. and added parttrneters. if any (step 32). Tenninal
`to then transmits the compiled canned message codes and
`
`4
`together with calling and receiving
`if any.
`parameters.
`terminal addresses to NOC 12 over communications linlt 16
`(FIG. 1) (step 3!).
`Assume. for example. that the canned message selected
`by the calling party in step 26 is “I are on my way home".
`This canned message does not call for the addition of
`parameters- The associated code for this canned message.
`may be. for example. the number 36 in ASCII code. To
`indicate that number 36 is a canned message code.
`the
`calling terminal 10 adds a suitable indicator code. such as
`ASCII control character 26. Thus. the compiled canned
`message codes representing the canned message “I am on
`my way home” is Iransrnitted in step 34 to NOC‘ [2 simply
`as d6>36.
`
`An example of a canned message calling for the inclusion
`of parameters may be “Call me at at phone number . This
`canned message calls for the calling party to till in a desired
`time parameter and a phone ntunbcr (step 30). Suppose the
`calling patty wishes the receiving party to call him at 4 PM
`at phone number 555-1212. the following canned message
`codes are then compiled by the calling terminal Ill and
`transmitted to NOC 12 as:
`<16‘>I3-C22:-1l“Md9>55§l2l.1
`
`where:
`db is an ASCII control character serving as a canned
`message indicator.
`18 is the code associated with canned message “Call rne '
`at at phone number "'.
`<29) is an ASCII control character serving as a parameter
`separator. and
`4PM and 5551212 are the keyed-in parameters.
`In addition to parameters. the present invention also
`provides for the addition of response options to certain
`canned messages typically posed as questions. To this end.
`terminal [0 maintains a file of canned response options.
`‘Then. if the calling party wishes to add response options to
`a selected canned message. the calling party accesses the
`canned response options file (step 36). which is then dis-
`played by terminal 10 {step 38). The calling party btowses
`through this file to determine which of the multiple response
`options are appropriate for addition to the selected canned
`message to he sent to the designated receiving party. The
`calling parry selects the agiropriate canned response options
`(step 40) in the same manner as in the selection of the canned
`message. and the calling terminal 1-! retrieves the particular
`codes associated with the selected canned response options
`(step 42). If the selected canned response options call for the
`addition of parameters. such as time. the calling party enters
`the desired parnmetetfs) (step 44). The selected canned
`response codes and parameters are then compiled with the
`canned message code and any canned message parameters
`(step 32). The calling terminal then transmits the compiled
`canned message and response codes. together with any
`parameters to NOC 12 [step 34).
`By way of example. if the selected canned message is
`“Can we sign the document first thing tomorrow?” followed
`by selected canned response options “yes”. "no". and
`“change to 1 PM". the canned message codes and param-
`eters transmitted to NBC 12 would preferably be as follows:
`-dd:-624!lbdfin-l d-l.:>-<26:-2-G1::-d[r>7d9> I PM
`
`where:
`
`I0
`
`I5
`
`25
`
`30
`
`35
`
`45
`
`55
`
`6.5
`
`<26> is an ASCII control character serving as the canned
`message and multiple response options indicator.
`<29) is an ASCII control character serving as the param-
`eter separator.
`
`10
`
`10
`
`

`
`5.894.506
`
`5
`
`<3l> is an ASCII control character unit separator used as
`n delineator separating multiple response options from the
`canned message and from each other.
`62 is the code associated with canned rrtessage “Can we
`sign the document first thing tomorrow?".
`1 is the code associated with canned response option
`"yes".
`2 is the code associated with canned response option
`can“.
`7 is the code associated with canned response option
`"change to“. and
`1PM is the keyed-in parameter.
`in some cases.
`The following example illustrates that.
`parameters added to canned messages may be canned
`parameters also stored at the calling terminal 10. Such
`canned parameters may be included in the canned message
`file.
`the canned multiple response options file. or in at
`separate canned parameter file stored at the calling terminal.
`If canned parameters are stored in separate file from the
`canned message file and the canned multiple rewonse option
`file. parameter selection by the calling party is achieved
`using a separate subroutine corresponding to the subroutine
`used to select canned multiple response options.
`To illustrate this case. consider the canned message "Can
`we meet for lunch at or '?”. and the selected multiple
`response options are “noon”. “l2:3D" or “call me”. The
`compilation of codes and parameters transmitted to NBC 12
`would then be:
`
`d-63-l[ld6>l5-<19>I2:30fil>d&>l5d1>l1:30d-l:r<26>8
`
`where:
`
`<26) is the ASCII control character‘ serving as the canned
`message and multiple response options indicator.
`dis» is the ASCII control character serving as a delin-
`eator for separating the canned message and multiple
`response options from each other.
`<29> is the parameter separator.
`I0 is the code associated with canned message “Can we
`meet for lunch at or 1"‘.
`8 is the code associated widt the canned parameter and
`response option “call me”.
`[5 is the code associated with canned parameter and
`response option “noon”. and
`12:30 is the keyed-in parameter.
`FIG. 3 illustrates the operation of NOC 12 in accordance
`with one embodiment of the invention. The canned message.‘
`response option codes and any pararneters transmitted by
`calling terminal 10 over communications link 16 are
`received by a NOC receiver (step 50). From the calling and
`receiving terminal addresses included with the canned
`messagelresponse option codes. the identifies of the calling
`and receiving terminals 10 and 14 (FIG. 1) are determined
`[step 52]. These determinations are stored in memory {step
`54}. From the identity of the receiving terminal 14. NOC 12
`determines if receiving terminal 14 is capable of accepting
`this particular canned messagelresponse option. NOC 12 is
`programmed to make this deterrnination for several reasons.
`For example. NBC 12 needs to know whether the designated
`receiving party is a member of a messaging group or
`organization that has established a file of customized canned
`messages and response options and thus has access to a
`terminal in which files of the customized canned messages}
`response options and associated codes are stored in memory.
`Also.
`the tiles of canned messages may include both
`standard. networlcwide canned messages and canned mes-
`sages cuslomized for a particular group. Thus. NOC 12 must
`determine whether the designated receiving party terminal
`
`6
`can accept only standard canned messageslresponse options.
`only customized canned messageslresponse options or both.
`In any case. NOC 12 maintains multiple files of canned
`messages and canned response options. including files iden-
`tical to those stated at calling terminal 10 and possibly also
`at receiving terminal 14.
`Based on this determination. NOC 12 determines whether
`the designated receiving party terminal can accept
`the
`canned message in code form.
`i.e.. as received from the
`sending party terminal. or whether the canned message must
`be lransrnitled in full text to the receiving party terminal
`(step 56). If the designated receiving terminal can accept
`canned rnessagelrcsponse option codes. they are transmitted
`to the designated receiving party terminal in the same form
`as received from the sending party terminal {step 58). If the
`designated receiving party terminal is not equipped to pro-
`cess canned messagclresponse option codes. NOC 12 uses
`the canned messagelresponse option codes received from the
`calling party terminal 10 to retrieve from the appropriate
`filofsj the text of the associated canned message and mul-
`tiple response options. if any. from a memory [ step 60). The
`text of the canned message and response options. together
`with parameters. is then transmitted in standard message
`code format by NOC 12 to the receiving terminal (step 58).
`FIG. 4 illnslntes the operation of receiving terminal 14
`upon receiving a message transmission. according to an
`errtbodilnent of the invention. Initially. tennlnal 14 receives
`the canned rncssagcfresponse option transmission from
`NOC 12 (step 70). The receiving tcurninal then determines
`whether the canned messagefresponse option reception is in
`message text or canned message code (step '72}. If in text. the
`canned message and any response options are displayed to
`the receiving party (step 74}.A1tcrnatively. if the reception
`is in canned rnessagefresponse option codes. the receiving
`party terminal 14. using these codes. retrieves the associated
`canned messages. canned response options. and canned
`parameters from the various stored files identical to those
`stored at calling terminal 10 and NO-C 12 (step 1'6}. The
`retrieved canned message. response options. and parameters.
`if any. are displayed in text font: for viewing by the
`receiving party terminal (step 74).
`If any response options are included with the canned
`message. the receiving party selects the appropriate response
`option (step 78). which is then transmitted by the receiving
`terminal back to NDC 12 (step 80). Since a typical response
`option is very short. it can be cficiently transmitted back to
`NOC 12 in ASCII text code fomtat. However. it will be
`appreciated that the receiving terminal may he so equipped
`that
`the code associated with the selected response. as
`received fiom NOC 12. may simply be transmitted back to
`the NOC 12 in response option code. Alternatively. the
`receiving terminal may be equipped with keys positioned in
`associated relation with the display of the multiple response
`options. Depression of any one of the keys selects the
`associated one of the response options. and a unique. simple
`code assigned to the depressed key is transmitted back to the
`NOC 12.
`
`FIG. 5 illustrates the operation of the NOC and the calling
`terminal
`in relaying a selected response option from the
`receiving terminal to the milling terminal in accordance with
`an embodiment of the invention. Initially. NBC 12 receives
`the selected response option transmitted by the receiving
`party terminal 14 (step 82). NOC then determines whether
`the received response option is in ASCII text code formal or
`in canned response option code {step 83). If in text code.
`NOC simply relays the selected response option to the
`calling party terminal 10 ( step 86]. if the selected response
`
`Ln
`
`ID
`
`15
`
`30
`
`35
`
`I15
`
`55
`
`65
`
`11
`
`11
`
`

`
`5.894.506
`
`'7
`option is received from the receiving party terminal in
`canned response option code. a decision is made whether to
`transmit the selected response option to the calling party
`terminal in canned response code orin ASCII text code {step
`84). If the former.
`the canned response code is simply
`transmitted to the calling party terminal 10 as received from
`the receiving terrninai {step 86). [fin ASCII text code. NOC
`12 is prograrnmed to access its stored tanned multiple
`response option file and. using the received response option
`code. retrieve the selected canned response option text (stop
`88). which is then transmitted in ASCII text code to die
`calling party terrninal 10 (step 86).
`The selected response option relayed by NOC 12 is
`received by calling terminal 10 (step 90). which then deter-
`mines whether the response option is in test code format or
`canned response code (step 92). If in text code. the response
`option is decoded and displayed to the calling party (step
`94). if the selected response option is in code form. the
`calling terminal simply aooesses its stored response options
`file and. using the received response option code. retrieves
`the associated response option text (step 96). which is then
`displayed to the calling party {step 94).
`NOC 12. as part of its system responsibilities. is capable
`of updating the canned message. canned response option.
`and canned parameter files. FIG. 6 illustrates the procedure
`for updating these files in accordance with one embodiment
`of the invention. NOC 12 updates the files (step 100} and
`stores the canned file updates in the NOC memory (step
`102). NOC 12 then transmits the updated canned files to all
`of the terminals in at particular two-way messaging group.
`including calling tenninal 10 and receiving terminal 14 (step
`104). The canned file updates are received by the messaging
`group terminals (step 106} and stored in the terminal n1erno~
`ties (step 108]. It will be appreciated that updated canned
`files may be created at one of the terminals and transmitted
`to NOC 12. which then opt:-ates to disseminate the file
`updates to other terminals of the messaging group.
`As indicated above. the calling terminal 10 and NOC 12
`are disclosed more fully in the cited application SH. No.
`081124216 and preferably comprise the structure disclosed
`in this application For illustrative purposes. applicants
`include FIGS. 7 and 8 to illustrate preferred sn'ucture in
`block diagram form.
`A preferred st:rut:tu:re of calling terminal 10 appropriate
`for practicing the present invention is illustrated in FIG. 7.
`As shown. the calling terminal 10 includes a CPU 110. a
`ROM 112 to store an application program for controlling
`terminal optnation in accordance with the present invention.
`a RAM 114 to store the canned messagelresponse options!
`parameter files and associated codes. and a compiler 116 for
`assembling the messagefresponse optionsipararneter codes.
`indicator and separator codes. and address codes into a
`message under the control of the application program and
`CPU 110. Calling terminal 10 also includes an inputloutput
`(HO) device 118 selectively connecting a transmitter 120
`and a receiver 122 into the terminal circuitry. A coder!‘
`decoder 124 encodes text messages transmitted by the
`terminal to NOC 12 and decodes text messages received
`from NOC. including selected response options in text code
`received from a receiving terminal 14. A terminal keypad
`126 is used by the calling party to designate a receiving party
`(typically by phone number}. to retrieve canned message}
`response optionslparameter files from RAM 114. to scroll
`through the displayed files. and to select
`the canned
`messag-‘Jresponse optionsfparameterlsl appropriate for
`sending to the receiving party. Display 123 also displays
`selected response options from receiving parties relayed by
`
`8
`NBC 12. These terminal components are intuconnected in
`operative relation by a system bus 130. While FIG. 7
`illustrates the operative strucniral oonftgtuation of calling
`terminal 10. it will be appreciated that. preferably. receiving
`terminal 14 is structurally configured in the same manner.
`FIG. 8 illustrates the snucrure of NOC 12 in accordance
`with one embodiment of the invention. As shown. NOC 12
`includes a CPU 131 connected by a system bus 132 to an
`inputloutput (U0) device 134. to which a transmitter 136 and
`a receiver 138 are connected. A ROM 139 stores an appli-
`cation program appropriate for connolling NOC 12 in
`accordance with the present invention. A RAM 140 stores
`sets of canned rnessageslresponse optionsiparameters files
`for various messaging groups. including the group to which
`terminals 10 and 14 belong. Thus. RAM 140 stores a set of
`canned files identical to the set stored in the RAMs of
`terminals Ill and 14. NOC 12 also includes a memory 142
`for stcring the identities of the calling and receiving term.i-
`nals involved in a message that is being relayed. as well as
`the messages. Message storage is preferred in case receiving
`terminals do not receive an original message transmission
`and. thus. retransmission is required. Retention of terminal
`identities is required so that selected response options
`received from receiving terminals are correctly relayed to
`the appropriate calling terminals.
`Finally. NOC 12 also includes a message compiler 144
`that may be required for message formatting and for adding
`appropriate codes. such as terminal address codes not
`included in the messages being relayed by the NDC. This is
`particularly so in the case of a selected response option
`which typically does not
`include the calling terminal
`address. NUC then refers to the calling terminal identify
`stored in memory 142 pursuant to determining the calling
`tmniaal address that rnustbe included in the transmission of
`the selected response option. if it is to be relayed to the
`correct calling terminal.
`It will be apparent to those skilled in the art that various
`modifications and variations can be nude in the. method of
`the present invention without departing from the spirit of the
`

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