(12) United States Patent
`Tsutsumitake
`
`USOO648.0883B1
`US 6,480,883 B1
`(10) Patent No.:
`Nov. 12, 2002
`(45) Date of Patent:
`
`(54) REAL-TIME INFORMATION
`TRANSMISSION SYSTEM
`
`(75)
`
`Inventor: Hideyuki Tsutsumitake, Yokohama
`(JP)
`(73) Assignee: Kabushiki Kaisha Toshiba, Kawasaki
`(JP)
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(*) Notice:
`
`(21) Appl. No.: 09/342,732
`(22) Filed:
`Jun. 29, 1999
`(30)
`Foreign Application Priority Data
`Jun. 30, 1998
`(JP) ........................................... 10-199587
`(51) Int. Cl. ................................................ G06F 15/16
`(52) U.S. Cl. ....................... 709/203; 709/217; 709/218;
`709/219; 709/232
`(58) Field of Search ................................. 709/203, 217,
`709/218, 219, 232
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`5,774,670 A * 6/1998 Montulli..................... 345/835
`
`5,893,091 A * 4/1999 Hunt et al. ................... 707/10
`5,925,100 A * 7/1999 Drewry et al. .............. 709/203
`6,021,437 A
`2/2000 Chen et al. ................. 709/202
`6,243,761 B1 * 6/2001 Mogul et al. ............... 709/217
`6,247,056 B1
`6/2001 Chou et al. ................... 707/10
`6.289,370 B1 * 9/2001 Panarello et al. ........... 345/706
`6,304,909 B1 * 10/2001 Mullaly et al. ............. 709/232
`* cited by examiner
`Primary Examiner Krisna Lim
`(74) Attorney, Agent, or Firm-Finnegan, Henderson,
`Farabow, Garrett & Dunner, L.L.P.
`(57)
`ABSTRACT
`A real-time information transmission System can immedi
`ately transmit information updated on a Server to a client,
`even if directly communication between the Server and the
`client is not established. If the Server receives a page request
`from the client, the Server returns a requested page to the
`client. The same connection ID is added to the request from
`the client and to an associated response from the Server. The
`client analyzes the page. If an event request is included in the
`analyzed page, the client adds another connection ID to the
`request and Sends it to the Server. Using the connection ID,
`the Server Sends an event to the client each time the event has
`occurred. The client processes the event and reflects the
`processed result on a Screen of a display.
`
`12 Claims, 13 Drawing Sheets
`
`111
`
`PAGE REQUEST
`UNT
`
`e
`
`PAGE RECE WING
`UNT
`
`109
`
`
`
`NETWORK
`NERFACE
`
`12
`NETWORK
`TCP/IP
`
`NETWORK
`NTERFACE
`
`
`
`
`
`INPUT/
`OUTPUT
`UNIT
`
`
`
`
`
`
`
`
`
`
`
`EVENT REQUEST
`UNIT
`
`
`
`
`
`
`
`EVENT RECE WING
`UNIT
`
`PAGE TRANS
`MISSION UNT
`
`PAGE REQUEST
`TRANSMSSION
`UNIT
`
`
`
`EVENT REQUEST
`
`t UNIT
`
`EVEN TRANS
`MISSION UNIT
`
`CONNECTION
`MANAGEMENT
`UNIT
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`EVENT GENERAT
`MONITORNG UN
`
`ON
`T
`
`
`
`EVENT GENERATION
`UNT
`
`INFORMATION
`PROW DING
`SERVER
`
`CONTROER
`
`PLANT SYSTEM
`
`42
`
`
`
`
`
`INFORMATION
`DISPLAY CLENT
`
`
`
`11
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 1 of 26
`
`

`

`Sheet 1 of 13
`
`
`
`INSIT9AVIdS1d
`
`LINA
`
`U.S. Patent
`
`Nov.12, 2002
`
`LINA
`
`
`
`ONIATIOAYFOV
`
`LINN
`
`
`
`-SNVULJOVd
`
`INNNOISSIW
`
`
`
`1San03u39Vd
`
`NOISSIWSNVUL
`
` LINA
`LNdLno/LNdNI
`
`LS3Nb3YFDVd*
`
`LINN
`
`LSan0auIN3AF
`
`JOVAYSIN|
`MYOMLAN
`MYOMLAN
`dt/dol
`JOVAYSIN|MYOMLAN
`
`LS3nbaeLNAAS
`
`LINA
`
`US 6,480,883 B1
`
`L“91s
`
`Vv
`
`WALSASLNVId
`
`YATTIOULNOD
`
`ONIG1AOUd
`
`YSANAS
`
`
`NOILYWYOSNI
`
`NO!LVYANS9LNSAAS
`
`LINN
`
` N
`
`INO|LYNYO-N|0
`SNIALSOAYLNSASLINA
`
`
`
`INIL
`
`
`
`VudNsadLNSAS
`
`NONIYOLINOW
`
`LINANOISSIW
`
`
`
` -SNVULLNSAS-LINASNIAISOSY
`LNAWSOVNVA
`NO1LOANNOO
`
`PETITIONERS - AMERICAN/SOUTHWEST,Exhibit 1006
`Page 2 of 26
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 2 of 26
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 2 of 13
`
`US 6,480,883 B1
`
`
`
`< HTML D
`< HEAD D
`< TITLED SAMPLE PAGE </TITLED
`</HEAD D
`< BODY )
`< H1 D SAMPLE PAGE </H1 D
`THIS PAGE INCLUDES EVENT REQUEST
`< EMBED D
`< EVENT URL=http://abc. def/hij. evt D
`</EMBED D
`</BODY D
`</HTMLD
`
`F. G. 2
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 3 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 3 of 13
`
`US 6,480,883 B1
`
`GENERATE PAGE REQUEST
`FROM INPUT/OUTPUT UNIT
`
`CUT OFF CONNECTION F
`CURRENTLY DISPLAYED PAGE--- A2
`INCLUDES EVENT REQUEST
`
`PAGE REQUEST UNIT ISSUES
`PAGE REQUEST TO PROPER SEVER
`
`A3
`
`PREPARE TO READ RESPONSEA4
`FROM SERVER
`
`A5 G. e.
`
`
`
`
`
`
`
`
`
`PAGE BEEN SENT
`FROM SERVEB
`YES
`ANALYZE PAGE
`
`A6
`
`YES
`
`
`
`A7
`
`
`
`S
`EVENT REQUEST
`INCLUDED
`
`NO
`
`A 2
`
`DISPLAY PAGE ON
`INPUT/OUTPUT UNIT
`
`PROCESS EVENT
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 4 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 4 of 13
`
`US 6,480,883 B1
`
`RECEIVE REQUEST FROM CLIENT -- B1
`
`
`
`B2
`IS
`REQUES, A PAGE
`
`
`
`B3
`IS
`REQUESTAN EVENT
`
`YES
`
`YES
`ANALYZE PAGE AND INFORM
`PAGE TRANSMISSION UNIT
`OF ANALYS IS RESULT
`
`B4
`
`
`
`
`
`B7
`
`RETURN ERROR TO CLIENT
`
`B5
`
`S
`THERE HTML
`FLE CORRESPONDING TO
`ARGE. PAGE
`YES
`
`B6
`
`RETURN HTML FILE TO
`CLENT
`
`ASK CONNECTION MANAGEMENT UNIT
`WHETHER EVENT ID AND CLIENT Dhu-B8
`ARE REGISTERED
`
`B9
`
`
`
`
`
`REGISTER
`
`CUT CONNECTION WITH CLENT-- B10
`
`F. G. 4
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 5 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 5 of 13
`
`US 6,480,883 B1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`HAS
`EVENT OCCURRED
`
`NFORM EVENT
`TRANSM SS ON
`UNIT
`
`
`
`HAS
`PREDETERMINED TME
`PASSED SINCE PREVIOUS
`EVENT WAS
`SENT
`
`B14
`
`SEND EVENT TO CLIENT
`
`SEND SYSTEM EVENT TO
`CLENT
`
`
`
`
`
`
`
`HAS
`EVENT BEEN SENT
`CORRECTLY
`NO
`
`CUT CONNECT ON WITH CENT
`AND DELETE ASSOCATED ENTRY
`FROM CONNECT ON MANAGEMENT
`UNIT
`
`
`
`B18
`
`F.G. 5
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 6 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 6 of 13
`
`US 6,480,883 B1
`
`SEWER 10
`
`C ENT 11
`
`PAGE TRANSMISSION
`
`uten- PAGE REQUEST
`Conn 1 f--PAGE ANALYSIS
`Conn 2
`EVENT REQUEST
`
`TIME
`
`EVENT GENERATION
`EVENT TRANSMISSION
`
`EVENT GENERATION
`EVENT TRANSMSSION
`
`Conn 2
`O
`
`Conn 2
`
`EVENT PROCESSING
`
`-- EVENT PROCESSING
`
`EVENT GENERATION
`Conn 2
`EVENT TRANSMISSION T EVENT PROCESSING
`EVENT GENERATION
`EVENT TRANSMISSION -
`ERROR DETECTION
`DELETE ITEM
`PAGE TRANSMISSION
`
`Conn 2
`- - -
`
`Conn 3
`
`ANOTHER PAGE
`REQUEST,
`CUT CONNECTION
`
`F G 6
`
`Conn 3
`- PAGE ANALYSIS
`Conn 4
`EVENT REQUEST
`
`
`
`CURRENT STATE
`MONITOR SCREEN
`
`PRESENT ELECTRIC
`CURRENT WALUE
`20 A
`STATE OF DEVICE
`ABNORMAL
`
`FIG. 7
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 7 of 26
`
`

`

`U.S. Patent
`
`
`
`US 6,480,883 B1
`
`8 ° 0 | -
`
`< GWEH > < TWIH >
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 8 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 8 of 13
`
`US 6,480,883 B1
`
`
`
`
`
`6 º 0 | -
`
`0N | 0 || M08'd
`HEM HES
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 9 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 9 of 13
`
`US 6,480,883 B1
`
`ANALYZE FORMAT OF EVENT
`REQUEST INPAGE
`
`C1
`
`C2
`
`
`
`S
`OCCURRENCE OF EVENT
`PER pDg
`
`NO
`
`
`
`SET TIME INTERVAL OF EVENT
`OCCURRENCE AT TM
`
`
`
`
`
`S
`TM LONGER THAN
`PREDETERMINED
`TIME 2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`YES
`
`C6
`
`C3
`
`NSTRUCT EVENT REQUEST UNIT
`TO ISSUE EVENT REQUEST TO
`SERVER
`
`INSTRUCT EVENT REQUEST UNIT
`TO ISSUE EVENT REQUEST TO
`SERVER
`
`CUT NETWORK CONNECTION
`IF EVENT IS ONCE RECEIVED
`FROM SERVER
`
`C7
`
`HALT FOR TIME TM
`
`C8
`
`F. G. 10
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 10 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 10 of 13
`
`US 6,480,883 B1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`RECEIVE EVENT SENT FROM SERVER
`WA EVENT RECEIVING UNIT
`
`IS TIME OF
`NEXT OCCURRENCE OF
`SAME-KND EVENT DESCRIBED
`NEVENT
`
`
`
`
`
`SET TIME AT TM
`
`IS
`EVENT RECEIVED AT TIME
`TM
`
`
`
`NSTRUCT EVENT REQUEST UNIT TO
`ISSUE EVENT REQUEST TO SERVER
`
`D5
`
`F. G. 11
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 11 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 11 of 13
`
`US 6,480,883 B1
`
`
`
`
`
`
`
`E3
`
`RECEIVE EVENT REQUEST FROM
`CLENT
`
`E1
`
`S
`EVENT REQUEST
`PERIODIC
`
`SET TIME INTERVAL AT TM
`
`S EVENT
`REQUEST RECEIVED
`AFTER ME TM
`
`NO
`
`DELETE ASSOCATED ITEM FROM
`CONNECTION MANAGEMENT UNIT
`AND CUT CONNECT ON RELATING
`TO EVENT
`
`E6
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`F.G. 12
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 12 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 12 of 13
`
`US 6,480,883 B1
`
`|
`
`08
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 13 of 26
`
`

`

`U.S. Patent
`
`Nov. 12, 2002
`
`Sheet 13 of 13
`
`US 6,480,883 B1
`
`RECEIVE FROM PAGE REQUEST
`RECEIVING UNIT A QUERY AS
`TO WHETHER DESIGNATED PAGE
`IS EXCLUSIVE PAGE
`
`Fl
`
`YES
`
`ASK CONNECTION MANAGEMENT
`UNIT WHETHER CONNECTION FOR
`EVENT REQUEST DESCRIBED IN
`PAGE IS REGISTERED
`
`E4
`
`F5
`
`END
`
`F3
`
`NO
`
`F7
`
`F6
`
`
`
`GENERATE HTML FILE IN WHCH
`TAG OF EVENT REQUEST IS
`EcgRERATED N HTML FILE
`
`RETURN TO CLIENT SPECIFIC
`PAGE FOR PERIOD CALLY
`ISSUING EVENT REQUEST
`
`SEND HTML FILE TO CLENT
`
`F8
`
`F. G. 14
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 14 of 26
`
`

`

`US 6,480,883 B1
`
`1
`REAL-TIME INFORMATION
`TRANSMISSION SYSTEM
`
`2
`to information described in the HTML file, which relates to,
`e.g. the next update time. If the next update time has arrived,
`the browser issues a request for provision of the updated
`page to the Server. According to the push mechanism, a
`useless access to the Server can be eliminated and Such an
`effect that the page is updated as if in real time can be
`obtained with the browser-Side processing alone.
`AS examples of Such browserS having the automatic
`function of periodically accessing the Server and being
`capable of reducing the operational load on the user, "Point
`Cast” (produced by Point Cast corporation) and “Castanet
`Tuner” (produced by Marimba corporation) have been pro
`vided. These browsers are provided with such devices as
`enable the user to designate the time interval of automatic
`update or the browser to receive only different data on the
`updated page.
`In the above-described Smart-pull mechanism and push
`mechanism, it is the browser, and not the Server, that updates
`the display of the page. AS mentioned above, even when the
`page Stored in the Server has been updated, unless the
`browser issues a request, the Server performs nothing. This
`characteristic of the client/server System causes Some prob
`lems described below.
`In the Smart-pull mechanism, the browser automatically
`accesses the Server on a periodical basis in order to check
`whether the page has been updated. Although no special
`attribute is needed in the HTML file constituting the page,
`the periodical acceSS is repeated unconditionally even if the
`Server-Side information is, in fact, not updated, and useleSS
`accesses will increase.
`On the other hand, the push mechanism is based on the
`special file (extended HTML file) in which information
`indicating the next update time is described beforehand as
`page attribute. Thus, no useleSS access to the Server is
`performed to check whether the information has been
`updated on the Server Side, if it is assumed that the page is
`actually updated on the Server Side according to the infor
`mation on the update time.
`However, the push mechanism is effective only in the case
`where the next update time or timing can be specified in
`advance. Specifically, in the push mechanism, if it is
`assumed that the page is updated asynchronously and at a
`non-specified timing, the update time information cannot be
`prepared. That is, the client Side is unable to know when the
`automatic update is to be made.
`There is a common problem with the Smart-pull mecha
`nism and the push mechanism. That is, when the update
`interval of the page to be provided is very short, e.g. one
`Second, the efficiency of communication processing is very
`low. The reason is as follows. In general, when communi
`cation is Started between the Server and client, Some com
`munication negotiations need to be performed before data is
`transmitted. In the above example, negotiations have to be
`performed every one Second. In this case, the ratio of the
`negotiations to the transmission/reception of page text will
`increase, and the communication efficiency from the Stand
`point of communication cost, etc. decreases.
`It appears that this problem will be solved if the server can
`Voluntarily and directly Send updated information to the
`client, independently from the request by the client. In view
`of the framework of the current WWW, however, this ideal
`is not practical. The reason is as follows.
`In the current WWW, there is a case where a plurality of
`relay Servers intervene between the Server and client. Some
`relay Servers are provided with mechanisms called “fire
`wall” for transferring information only in one direction. The
`
`15
`
`BACKGROUND OF THE INVENTION
`The present invention relates generally to a client/server
`type System wherein an information providing Server pro
`vides information upon request from an information display
`client, and more particularly to a real-time information
`transmission System for realizing novel and advantageous
`information transmission from an information providing
`Server to an information display client.
`In these years, the WWW (World Wide Web) has perme
`ated through Societies, and various information is provided
`via the WWW. The WWW is a distributed-type information
`provision/information-display System using the Internet, and
`it comprises Servers (information providing Servers) and
`clients. AS is well known, a Worldwide information network
`using hypertexts including images and Sounds has been
`constructed by the WWW and utilized by many people.
`In general, the Server provides information to the client in
`units of a document called “page'. The page is an electronic
`file described in a format called HTML (Hypertext Markup
`Language). The client is normally realized with use of a
`software called “browser' for information display
`(information browsing), and the browser accesses the server
`to acquire and display pages including images and Sounds.
`In the general use of the WWW, an address (called URL)
`of a page to be displayed is designated in the browser, and
`the browser issues a request to the Server. The Server returns
`the page corresponding to the address to the browser. It
`should be noted here that the server performs nothing unless
`it receives a request from the browser. This means that even
`if pages Stored in the Server have been updated, the browser
`is unable to immediately know the change.
`For example, while the browser is displaying pages Such
`as news and weather reports, which are updated in real time,
`the browser is not informed of the fact that the pages have
`been updated on the server side. That is, the content of the
`updated page is not reflected on the display Screen of the
`browser side.
`The user on the browser side can immediately know the
`update of the page Stored in the Server, if the browser
`accesses the Server periodically. In this case, however, the
`user needs to periodically re-access the Server, for example,
`by depressing a reload button generally provided in the
`browser, and this means that a very time-consuming opera
`tional load is put on the user.
`There is known a mechanism called "Smart-pull mecha
`nism' as an example of the mechanism for automatically
`updating the display of the page on the browser Side in
`accordance with the update of the page on the Server Side. In
`the Smart-pull mechanism, the browserSide operation by the
`user of positively depressing the reloadbutton is automated.
`The Smart-pull mechanism provides the user with Such a
`feeling that the page updated on the Server Side is automati
`cally sent to the browser, like TV broadcasting.
`There is a mechanism called “push mechanism' as
`another example of the mechanism for automatically updat
`ing the display of the page on the browser Side. The push
`mechanism is provided with means for extending an HTML
`file provided by the information providing server (WWW
`server), thereby describing in the HTML file various infor
`65
`mation relating to the display update of the page. The
`browser, which has received the extended HTML file, refers
`
`45
`
`50
`
`55
`
`60
`
`25
`
`35
`
`40
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 15 of 26
`
`

`

`US 6,480,883 B1
`
`3
`firewall is generally used, in particular, in companies, in
`order to prevent outside intruder from entering the Systems
`within the companies (e.g. Intranet).
`Where such relay servers intervene, the object with which
`the client directly communicates is the relay Server closest to
`the client, and the object with which the server directly
`communicates is the relay Server closest to the Server.
`Accordingly, the direct client of the Server is this relay
`Server, and the Server cannot specify the client used by the
`user on the network.
`AS a result, the Server cannot directly Send an update
`notification to the browser. Moreover, Since the intervening
`relay Server receives accesses from many non-Specified
`clients or servers, there is a problem with reliability or
`stability. It is not ensured that the update notification from
`the Server is quickly Sent to the client with Safety and
`eXactneSS.
`
`4
`be reduced. In particular, where the interval of occurrence of
`events is one Second or less, the efficiency is high and high
`real-time performance can be expected. Furthermore, Since
`the Server continuously sends event notifications in response
`to the request (event request) from the client, this invention
`is realized by using only the existing WWW protocols.
`On the other hand, in the conventional push technique on
`the WWW, for example, a time of update of page informa
`tion provided by the Server is described in the page infor
`mation and thereby the client (browser) accesses the server
`at that time. In this technique, problems arise with respect to
`data, Such as time-Sequential data, which is updated at a
`Short interval of about one Second, Since the connection/
`disconnection of the network occurs frequently.
`The present invention is also characterized in that at least
`one event request information unit for enabling the client,
`which has received page information Sent from the Server in
`response to a page request from the client, to issue the event
`request, that is, for activating an event notification on the
`Server Side, is Set in the page information.
`In this structure, the client, which received the requested
`page information from the Server, can automatically issue
`the event request to the Server according to the event request
`information Set in the page information, and can activate the
`event notification. Specifically, by associating the page
`information with the event, the page information opened on
`the client Side can be dynamically changed according to the
`event notification Sent from the Server.
`In order for the server to determine whether the client has
`normally received an event notification, it is necessary to
`actually Send the event notification. However, the Server can
`perform nothing until an event occurs in the Server. Thus,
`even if the page processing is finished in the client, the load
`for network connection is applied to the Server.
`According to this invention, in the Situation in which each
`time an event has occurred in the Server the event notifica
`tion has to be sent to the client at the event request
`originating point, if no event has occurred for a predeter
`mined time period, a special event notification (client State
`confirmation event notification) for confirming the State of
`the client at the event request originating point is sent from
`the server to the client. When the event notification
`(including the client State confirmation event notification) is
`sent from the server, the server determines whether the event
`notification is Successful. If the event notification has failed,
`the network connection for the event notification is cut off on
`the Server Side.
`In this Structure, when no event has occurred for a
`predetermined time period or more, the Special event noti
`fication for confirming the State of the client at the event
`request originating point is generated explicitly and periodi
`cally and sent to the client. Thereby, the state of the client
`can be understood. If the transmission of the event notifi
`cation fails due to the termination of the page processing in
`the client or the disconnection of the network, the Server cuts
`off the network connection and the useleSS load can be
`reduced.
`In an example of application of the client-side processing
`for the event notification, if the client has received the event
`notification, the content of the notification may immediately
`be reflected on the Screen. For this purpose, Some device is
`needed when the page information opened on the client Side
`is to be changed.
`In the present invention, a predetermined procedure to be
`executed by the client is Set in the page information includ
`ing the event request information, which is Sent from the
`
`15
`
`25
`
`35
`
`40
`
`BRIEF SUMMARY OF THE INVENTION
`The present invention has been made in consideration of
`the above circumstances, and an object of the invention is to
`provide a real-time information transmission System for
`realizing real-time information transmission from a Server to
`a client in an existing WWW framework, thereby coping
`with information update in the Server.
`Another object of the invention is to proyide a real-time
`information transmission System, wherein even if the time
`interval of information update on the Server Side is very short
`or information update occurs at a non-specified time, infor
`mation update on the Server Side can be efficiently reflected
`on the client side, and the reliability and stability of com
`munication between the Server and client can be enhanced.
`Still another object of the invention is to provide a
`real-time information transmission System for realizing Such
`an exclusive control that the same page cannot simulta
`neously displayed on a plurality of clients excluding one
`client.
`The present invention provides a real-time information
`transmission System for transmitting information in real time
`from a Server to a client via a network, the System compris
`ing: determination means for determining, on the basis of an
`information transmission request from the client to the
`Server, whether the request is a page request or an event
`request, page transmission means for transmitting, if the
`determination means has determined that the request is the
`page request, information of the requested page only once
`from the Server to the client at an originating point of the
`page request, event generating means for generating events,
`and event transmission means for transmitting, when the
`determination means has determined that the request is the
`event request, those of the events generated by the event
`generating means which are associated with the event
`request, from the Server to the client at an originating point
`of the information transmission request in response to the
`event request issued once.
`In this structure, a novel concept of “event request' for
`requesting updated information of currently opened page
`information is introduced in addition to a conventionally
`known concept of "page request'. In the State in which the
`Server and the client are being connected, the Server con
`tinuously transmits event notifications to the client in
`response to a Single event request in accordance with the
`occurrence of events. Thereby, each time page information
`has been updated on the Server Side, the updated content can
`automatically be reflected on the client side. Moreover, the
`load of communication between the Server and the client can
`
`45
`
`50
`
`55
`
`60
`
`65
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 16 of 26
`
`

`

`S
`Server in response to the page request from the client. When
`the client which received the page information changes the
`display of the page information to display of page informa
`tion corresponding to another page request, that is, when the
`client changes to another page, the client cuts off, according
`to the aforementioned procedure, the network connection
`associated with the event notification from the server in
`response to the event request.
`In this Structure, if the client has changed to another page,
`the client cuts off the network connection for receiving the
`event notification for reflecting the update of the previous
`page. Thus, useleSS communication can be eliminated.
`Moreover, the client does not require a special System for
`this processing.
`In this invention, information indicating whether occur
`rence of an associated event is periodic or non-periodic,
`information on a time interval if the occurrence of the event
`is periodic and a predetermined procedure to be executed by
`the client are Set in page information with information on the
`event request, which page information is transmitted from
`the Server in accordance with the page request from the
`client. Thereby, when the occurrence of the associated event
`is periodic and the time interval thereof is greater than a
`predetermined time, the client which has received the page
`information temporarily cuts off network connection each
`time the client receives an event notification from the Server
`in response to the event request, according to the predeter
`mined procedure. The client also executes an operation to
`issue the event request once again after an event generation
`scheduled time set by the time interval has arrived.
`In this structure, where the occurrence of events is peri
`odic and the interval of occurrence is long, the client
`temporarily cuts off the network connection. If the Set time
`of occurrence of events has drawn near, the network con
`nection is made again and the event request is issued. Thus,
`the useless load of network and the load of the CPUs in the
`Server and client can be reduced. Moreover, the client Side
`does not require a special System for this processing.
`In the present invention, a predetermined procedure to be
`executed by the client is Set in page information with the
`event request information, which page information is sent
`from the Server in response to the page request from the
`client, or in an event notification transmitted from the Server
`in response to the event request from the client, and time
`information on occurrence of the same event occurs is Set in
`the event notification. Thereby, the client, which has
`received the event notification, is caused to monitor the
`arrival of the next event notification according to the pre
`determined procedure, and to issue the event request to the
`server where the client could not receive the next event
`notification from the Server at a set time indicated in the time
`information in the received event notification.
`In this structure, where the time of occurrence of the event
`can be estimated, if the event has not been Sent from the
`Server at that time, it is assumed that the network has
`temporarily been cut off. Then, the event request is issued
`once again from the client, and the network connection can
`be resumed. Thus, the reliability is enhanced. Specifically,
`the connection for the event notification is maintained, but
`if the connection is cut off due to Some external cause, the
`client automatically re-connects the network. Accordingly,
`even in the case of an unstable network, the reliability can
`be expected to Some degree. In addition, the client Side does
`not require a special System for this processing.
`In the present invention, a procedure for adding time
`information for issuing a next event request to the event
`
`15
`
`25
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 6,480,883 B1
`
`6
`request issued by the client is Set in page information with
`the event request information, which page information is
`Sent from the Server in response to the page request from the
`client. Thereby, when the event request with the time infor
`mation has been issued from the client, which received the
`page information, to the Server, the Server monitors arrival of
`the next event request from the client, and cuts off network
`connection relating to the event request, if the Server could
`not receive the next event request at a Set time indicated in
`the time information in the preceding event request.
`In this structure, the Server can recognize in advance the
`fixed time of the occurrence of the event request from the
`client. If the event request has not been issued at that time,
`the Server determines that the client does not normally
`function (the operation is terminated or the network is
`disconnected). Thus, the server cuts off the network con
`nection and the useless load on the CPU in the server can be
`reduced. Moreover, the client does not require a special
`System for notifying the Server of the preset time of occur
`rence of the next event request.
`In the present invention, information on an exclusive
`page, which is prohibited from being displayed Simulta
`neously on a plurality of clients, is registered in the Server.
`Where the Server has received the page request from the
`client, the Server determines whether the requested page is
`an exclusive page, on the basis of the registered information
`of the exclusive page. If the request page is the exclusive
`page, the Server determines whether the page is being
`displayed on another client. If the page is not being dis
`played on the another client, new page information, in which
`the event request information is Set in the requested page
`information, is Sent to the client at the originating point of
`the page request. If the page is being displayed on the
`another client, specific page information, in which specific
`event request information for issuing a specific event request
`is Set, is Sent to the client at the originating point of the page
`request, instead of the requested page information, and the
`client is caused to wait for display of the requested page
`information. Where network connection relating to an event
`notification from the server to the client which is in the state
`of displaying the exclusive page is cut off and there are
`clients which are in the State of waiting for display of the
`exclusive page, new page information, in which the event
`request information is Set in the requested page information,
`is Sent to one of the clients waiting for the display of the
`exclusive page as a response to the Specific event request.
`In this Structure, the event request issuance from the client
`according to the event request information incorporated in
`the page information is utilized to easily realize a mecha
`nism (page lock mechanism) which prevents simultaneous
`display of the same page on a plurality of clients. This
`mechanism has been difficult to achieve in the conventional
`WWW. Moreover, where the page processing in the client
`displaying the exclusive page is finished, another client
`which could not display the page is informed to that effect.
`Thus, this client can automatically change the display to the
`actually requested page. Therefore, the user interface is
`enhanced.
`In the present invention, where the page request or the
`event request has been Sent to the Server from the client
`which is in the waiting State Since the requested page is the
`exclusive page and is displayed on another client, processing
`of the request in the Server is changed from normal State.
`If the request is issued from the client, which is in the wait
`State for the locked page, to the Server, the processing for the
`request is changed from a normal one. For example, by
`
`PETITIONERS - AMERICAN/SOUTHWEST, Exhibit 1006
`Page 17 of 26
`
`

`

`7
`ignoring the request, the client itself can be virtually locked.
`When a control device is controlled from the client side, a
`control is prevented from being transferred to another client,
`and the reliability is enhanced.
`Additional objects and advantages of the invention will be
`set forth in the description which follows, and in part will be
`obvious from the description, or may be learned by practice
`of the invention. The objects and advantages of the invention
`may be realized and obtained by means of the instrumen
`talities and combinations particularly pointed out hereinaf
`ter.
`
`BRIEF DESCRIPTION OF THE SEVERAL
`VIEWS OF THE DRAWING
`The accompanying drawings, which are incorporated in
`and constitute a part of the Specification, illustrate presently
`preferred embodiments of the inventi