US6480883B1 - Real-time information transmission system - Google Patents

Real-time information transmission system Download PDF

Info

Publication number
US6480883B1
US6480883B1 US09/342,732 US34273299A US6480883B1 US 6480883 B1 US6480883 B1 US 6480883B1 US 34273299 A US34273299 A US 34273299A US 6480883 B1 US6480883 B1 US 6480883B1
Authority
US
United States
Prior art keywords
event
page
request
client
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
US09/342,732
Other languages
English (en)
Inventor
Hideyuki Tsutsumitake
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toshiba Corp
Original Assignee
Toshiba Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Toshiba Corp filed Critical Toshiba Corp
Assigned to KABUSHIKI KAISHA TOSHIBA reassignment KABUSHIKI KAISHA TOSHIBA ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TSUTSUMITAKE, HIDEYUKI
Application granted granted Critical
Publication of US6480883B1 publication Critical patent/US6480883B1/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates generally to a client/server type system wherein an information providing server provides 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.
  • the WWW World Wide Web
  • the WWW is a distributed-type information-provision/information-display system using the Internet, and it comprises servers (information providing servers) and clients.
  • servers information providing servers
  • 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.
  • 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).
  • 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.
  • 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.
  • 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 operational load is put on the user.
  • smart-pull mechanism 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.
  • the browserside operation by the user of positively depressing the reload button is automated.
  • the smart-pull mechanism provides the user with such a feeling that the page updated on the server side is automatically sent to the browser, like TV broadcasting.
  • 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 information relating to the display update of the page.
  • the browser which has received the extended HTML file, refers 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.
  • 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.
  • 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.
  • the special file extended HTML file
  • 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.
  • 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.
  • firewall 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 “firewall” for transferring information only in one direction.
  • the firewall is generally used, in particular, in companies, in order to prevent outside intruder from entering the systems within the companies (e.g. Intranet).
  • 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.
  • the server cannot directly send an update notification to the browser.
  • the intervening relay server 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.
  • 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, information update on the server side can be efficiently reflected on the client side, and the reliability and stability of communication 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 simultaneously 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 comprising: 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.
  • 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.
  • 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.
  • the page information opened on the client side can be dynamically changed according to the event notification sent from the server.
  • 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.
  • a special event notification for confirming the state of the client at the event request originating point is sent from the server to the client.
  • 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.
  • the special event notification for confirming the state of the client at the event request originating point is generated explicitly and periodically and sent to the client. Thereby, the state of the client can be understood. If the transmission of the event notification 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.
  • the content of the notification may immediately be reflected on the screen.
  • some device is needed when the page information opened on the client side is to be changed.
  • a predetermined procedure to be executed by the client is set in the page information including the event request information, which is sent from the server in response to the page request from the client.
  • the client which received the page information changes the display of the page information to display of page information 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.
  • 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.
  • information indicating whether occurrence 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.
  • 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 predetermined 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.
  • the client temporarily cuts off the network connection. If the set time of occurrence of events has drawn near, the network connection 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.
  • 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.
  • the client which has received the event notification, is caused to monitor the arrival of the next event notification according to the predetermined 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.
  • 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.
  • 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.
  • the client side does not require a special system for this processing.
  • a procedure for adding time information for issuing a next event request to the event 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.
  • 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 connection 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 occurrence of the next event request.
  • information on an exclusive page which is prohibited from being displayed simultaneously on a plurality of clients, is registered in the server.
  • 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 displayed 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.
  • 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.
  • 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.
  • the event request issuance from the client according to the event request information incorporated in the page information is utilized to easily realize a mechanism (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.
  • 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.
  • this client can automatically change the display to the actually requested page. Therefore, the user interface is enhanced.
  • the processing for the request is changed from a normal one. For example, by ignoring the request, the client itself can be virtually locked.
  • a control device is controlled from the client side, a control is prevented from being transferred to another client, and the reliability is enhanced.
  • FIG. 1 is a block diagram showing the structure of a real-time information transmission system according to a first embodiment of the present invention
  • FIG. 2 shows an example of the format of an HTML file applied to this embodiment
  • FIG. 3 is a flow chart for describing the flow of processing in a client 11 shown in FIG. 1;
  • FIG. 4 shows a part of a flow chart for describing the flow of processing in a server 10 shown in FIG. 1;
  • FIG. 5 shows the other part of the flow chart for describing the flow of processing in the server 10 shown in FIG. 1;
  • FIG. 6 shows an example of a process of communication between the server 10 and client 11 in FIG. 1 in relation to a time axis
  • FIG. 7 shows an example of a screen image of a browser
  • FIG. 8 shows an example of the format of a page on which the screen image in FIG. 7 is based
  • FIG. 9 is a block diagram showing the structure of a real-time information transmission system according to a second embodiment of the present invention.
  • FIG. 10 is a flow chart for describing the operation of, in particular, a timer unit A of the client 21 in the system shown in FIG. 9;
  • FIG. 11 is a flow chart for describing the operation of, in particular, a timer unit B of the client 21 in the system shown in FIG. 9;
  • FIG. 12 is a flow chart for describing the operation of, in particular, a timer unit C of the server 20 in the system shown in FIG. 9;
  • FIG. 13 is a block diagram showing the structure of a real-time information transmission system according to a third embodiment of the present invention.
  • FIG. 14 is a flow chart for describing the operation of, in particular, an exclusive page management unit 300 of the server 30 in the system shown in FIG. 13 .
  • FIG. 1 is a block diagram showing the structure of a real-time information transmission system according to a first embodiment of the present invention.
  • an information providing server 10 functions as a WWW (World Wide Web) server and is connected to a network 12 such as the Internet.
  • An information display client 11 has a browser for issuing a request to the information providing server 10 and displaying a result.
  • the browser may be a general-purpose one such as the Netscape Navigator (Netscape Communications Corporation) or the Internet Explorer (Microsoft Corporation).
  • proxy server may be provided between the information providing server 10 and information display client 11 .
  • the proxy server receives a request from the client, sends the request to the server as it is, and returns a result from the server directly to the client.
  • a plurality of such proxy servers may be provided between the information providing server 10 and information display client 11 .
  • the information providing server is referred to simply as “server”, and the information display client as “client”.
  • the client may be called “browser” in some cases.
  • FIG. 1 shows only one client 11 connected to the network 12 , but in general a plurality of clients 11 are connected to the network 12 .
  • the number of servers 10 is not limited to one.
  • FIG. 1 shows a case where a plant system 42 is connected to the server 10 via a controller 40 .
  • the plant system 42 and its controller 40 may be connected not to the server 10 but to the network 12 .
  • the server 10 monitors the operation of the plant system 42 through the controller 40 , and provides various useful information to the client 11 .
  • the plant system 42 is merely an example of the application of this invention, and the invention is applicable to OA equipment, mobile phones, TV sets, etc.
  • a network interface 101 functions to receive data from the network 12 and to transmit data to the network 12 .
  • the network interface 101 also functions to discriminate the type of received data and to deliver the data to a unit in the server 10 , which is associated with the discriminated type.
  • a page request receiving unit 102 receives a page request sent from the client 11 via the network interface 101 , analyzes it, and informs a page transmission unit 103 of a page to be sent to the client 11 .
  • a format called URL Uniform Resource Locator
  • URL Uniform Resource Locator
  • the page transmission unit 103 transmits an HTML file 100 stored in the server 10 to the network 12 via the network interface 101 .
  • Information to be transmitted is not limited to the HTML file ( 100 ), and may be freely chosen one such as image or voice.
  • An event request receiving unit 104 receives an event request sent from the client 11 via the network interface 101 , analyzes it, and communicates with a connection management unit 105 to determine whether the event request should be processed.
  • the event request receiving unit 104 instructs an event transmission unit 106 , where necessary, to transmit an event to the client 11 .
  • An event generating unit 107 generates events asynchronously or non-periodically.
  • the kind of event to be generated is freely chosen.
  • the examples are an event indicating the fact that a current flowing a specific control device in the plant system 42 has exceeded a predetermined value, an event indicating the fact that the number of clients 11 accessing the server 10 has reached a predetermined value, and an event indicating that a predesignated time has arrived.
  • An event generated by the event generating unit 107 is directly sent to the event transmission unit 106 .
  • an event generation monitoring unit 108 may monitor a factor of generation of an event and, as a result, may generate an event of a different kind which is not generated by the event generating unit 107 and send it to the event transmission unit 106 .
  • a predetermined value e.g. 100 A or less
  • the event generation monitoring unit 108 also generates other various events, for example, an event for notifying the client 11 of the fact that the number of times of generation of a specific event in the event generating unit 107 has reached a predetermined value.
  • the events to be input to the event transmission unit 106 are generated from two systems: the event generating unit 107 and event generation monitoring unit 108 . However, only one of them may be provided.
  • the event transmission unit 106 transmits the event, which has been sent from the event generating unit 107 or event generation monitoring unit 108 , to the client 11 via the network interface 101 . In a case where the same event is requested by a plurality of clients 11 , the event transmission unit 106 sends the same event to the respective clients 11 .
  • connection management unit 105 manages, for example, on a table format, information indicating which event is requested by which client, namely, connection information.
  • the event transmission unit 106 refers to the information managed by the connection management unit 105 , and sends the event to all clients 11 requesting it. It should be noted that unlike the page sent by the page transmission unit 103 , the event is a transient one and the same event has to be copied by a number corresponding to the number of clients 11 , irrespective of the number of clients 11 requesting the event, and the copied events have to be sent.
  • a network interface 109 sends a page request or an event request from the client 11 to the sever 10 which is to be sent to the server 10 connected to the network 12 , and receives a response from the server 10 .
  • the network interface 109 forwards the response from the server 10 to a page receiving unit 112 or an event receiving unit 114 according to the kind of the response.
  • An input/output unit 110 comprises a keyboard, a display and a mouse.
  • the URL of the page request is sent to a page request unit 111 by an operation using the input/output unit 110 , for example, by directly inputting the URL to, e.g. the keyboard of the input/output unit 110 , or by clicking a link on the page by means of the mouse.
  • the input/output unit 110 requests the server 10 via the network interface 109 to transmit the page specified by the URL.
  • the page receiving unit 112 receives a response from the server 10 to the page request, that is, the requested page, via the network interface 109 .
  • the received page is displayed on the display of the input/output unit 110 .
  • the page received from the server 10 includes a description for issuing an event request to the server 10 .
  • the page receiving unit 112 informs an event request unit 113 of the URL of the event request.
  • the event request unit 113 sends the URL of the event request to the server 10 via the network interface 109 .
  • the URL of the event request may not only be delivered from the page receiving unit 112 , but also it may be directly input to the input/output unit 10 by the user.
  • the event receiving unit 114 receives the event sent from the server 10 on the basis of the request to the server 10 from the event request unit 113 .
  • the received event is sent to the input/output unit 110 , where necessary. For example, if the received event is an event indicating the update of the page in the server 10 , the client 11 issues a page request to the server 10 and enables the updated page to be displayed on the display screen once again (i.e. the updated content being reflected on the display).
  • the format of the page sent from the server 10 in response to the page request from the client 11 is a normal HTML file format.
  • a normal HTML file format is a normal HTML file format.
  • another format may be adopted.
  • FIG. 2 shows an example of the HTML file format.
  • an event request to the server is included in the page.
  • the event request is expressed by an attribute “URL” in a tag “EVENT” in a tag “EMBED”.
  • the format of expression of the event request is not limited to this. It may be assumed, for example, that the event request is not positively described in the HTML file but is expressed as a link to another page, and the event request is described in the page of the destination link and is sent to the server 10 from the HTML file at the originating point.
  • the network interface 109 cuts off network connection relating to the transmission of the requested event from the server 10 (step A 2 ).
  • This is realized by describing in advance in the currently displayed page the procedure wherein when another page request has been generated in the client 11 , i.e. when the currently displayed page is to be changed, the network connection for receiving the event relating to the currently displayed page including the event request is cut off from the client ( 11 ) side.
  • Java Applet
  • JavaScript JavaScript of Netscape Communications
  • the page request unit 111 issues the page request to a proper server 10 b (step A 3 ).
  • the page receiving unit 112 prepares to read a response from the server 10 (step A 4 ) and waits until the page is sent from the server 10 (step A 5 ).
  • the page receiving unit 112 analyzes the content of the page sent from the server 10 (step A 6 ) to determine whether an event request is included in the page (step A 7 ).
  • the page receiving unit 112 outputs the page to the input/output unit 110 (step A 12 ).
  • the content of the received page is displayed on the display of the input/output unit 110 .
  • the page receiving unit 112 informs the event request unit 113 of the URL of the event and causes the event request unit 113 to send the event request to the server 10 (step A 8 ). In this case, the page receiving unit 112 prepares to read a response (event) from the server 10 (step A 9 ) to check whether the event has been sent from the server 10 (step A 10 ). If the event is not sent, the page receiving unit 112 continues to wait. If the even has been sent, the page receiving unit 112 processes it (step A 11 ). The display screen image of the input/output unit 110 is updated, depending on the result of processing of the event, as will be described later.
  • step A 8 to A 11 The processing indicated by a dot-and-dash line in the flow chart of FIG. 3 (steps A 8 to A 11 ) may be carried out in parallel to step A 12 .
  • the reading or processing of the event can be performed.
  • the events can be processed simultaneously.
  • the characteristic of the processing on the client ( 11 ) side is that the number of responses to the page request is one while the number of responses to the event request is infinite. Though not shown, an external instruction is needed to terminate the event processing.
  • the network interface 101 in the server 10 always stands by to receive a request from the client 11 (step B 1 ). If the interface 101 receives the request from the client 11 , it determines whether the request is a page request or an event request (steps B 2 , B 3 ).
  • the network interface 101 delivers it to the page request receiving unit 102 .
  • the page request receiving unit 102 analyzes the content of the page request and informs the page transmission unit 103 of the result of analysis (step B 4 ).
  • the page transmission unit 103 determines whether there is an HTML file 100 corresponding to the requested page (in a file storage unit not shown) (step B 5 ). If there is the corresponding HTML file 100 , the page transmission unit 103 sends the file 100 back to the client 11 at the request originating point (step B 6 ). If not, the page transmission unit 103 sends an error message back to the client 11 (step B 7 ).
  • the page file is the HTML file, but the file format is not limited to this.
  • the network interface 101 delivers it to the event request receiving unit 104 .
  • the event request receiving unit 104 asks the connection management unit 105 whether or not an identifier (event ID) of the event requested by the event request and an identifier (client ID) of the client 11 at the request originating point have already been registered (steps B 8 , B 9 ). If they are registered, the connection with the client 11 is cut off (step B 10 ). If they are not registered, a pair of the identifier (event ID) of the event requested by the event request and the identifier (client ID) of the client 11 at the request originating point are registered in the connection management unit 105 (step B 11 ).
  • connection management unit 105 means that communication (connection) has already been established between the server 10 and the client 11 identified by the client ID.
  • connection By cutting off the connection in step B 10 , double transmission of the event to the same client 11 is prevented.
  • step B 12 it is determined whether an event has occurred in at least one of the event generation unit 107 and event generation monitoring unit 108 (step B 12 ). If no event has occurred, it is determined whether a predetermined time period has passed since the latest event was transmitted from the event transmission unit 106 (step B 13 ). If the predetermined time period has passed, the event transmission unit 106 transmits a special event called “system event” to the client 11 at the event request originating point, thereby to confirm the condition, etc. of this client 11 (step B 14 ). On the other hand, if the time period has not yet passed, it is determined once again whether an event has occurred in the event generation unit 107 or event generation monitoring unit 108 (step B 12 ).
  • the event transmission unit 106 is instructed to send the event to the client 11 (step B 15 ).
  • the event transmission unit 106 sends the generated event to the client 11 at the event request originating point via the network interface 101 (step B 16 ).
  • step B 17 After the event was sent to the client 11 , it is determined whether the event has correctly been sent on the basis of a response from the client 11 (step B 17 ). If the event has correctly been sent, the next occurrence of event is awaited. If the event has not correctly been sent, the connection with the client 11 is cut off and the associated item is deleted from the connection management unit 105 (step B 18 ).
  • the connection between the server 10 and client 11 at the event request originating point is always maintained. If the event is not correctly sent, the connection is cut off.
  • a special event notification for confirming the state of the client 11 at the event request originating point is sent from the server 10 to the client 11 .
  • the server 10 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 ( 10 ) side.
  • the server 10 cuts off the network connection and thus a useless communication load is reduced.
  • FIG. 6 shows an example of the communication process between the server 10 and client 11 in relation to the time axis.
  • the server 10 If a page request is sent from the client 11 to the server 10 , the server 10 returns the requested page to the client 11 .
  • the same ID (Conn 1 in FIG. 6) is added to the request from the client 11 and the response by the server 10 in order to establish their correspondency.
  • the client 11 analyzes the sent page, searches for an event request described therein, and sends it to the server 10 .
  • another connection ID (Conn 2 ) is used. If an event has occurred, the server 10 sends it to the client 11 with use of this connection ID. Subsequently, as shown in FIG. 6, each time an event has occurred, it is sent repeatedly with use of the ID (Conn 2 ).
  • the client 11 When the client 11 sends another page request (Conn 3 ), it simultaneously cuts off the connection of the request Conn 2 . Then, if the event to be sent with ID Conn 2 has occurred in the server 10 , an error is detected and the associated item is deleted from the connection management unit 105 . In response to a new page request from the client 11 , the server 10 sends the associated page to the client 11 . Similar communication operations will be repeated.
  • the following advantage is obtained by cutting off the connection for event transmission from the server 10 when the client 11 has issued another page request.
  • a visual effect is provided on the screen image of the page associated with the requested event in the event processing on the client ( 11 ) side. If the display is switched to another page and the page itself associated with the event request disappears from the screen, this means that the received event has become useless. In other words, useless event processing is prevented. Needless to say, however, the event processing may be continued by system configuration even after the page associated with the event request has been switched to another page by an explicit instruction.
  • FIG. 7 shows an example of the screen image of the browser. This example relates to a page for monitoring the state of current in a specific control device in the plant system 42 .
  • a page comprising a current value display section 71 indicating a value of electric current at present and a state display section 72 indicating the state of a device (control device) is displayed by the browser.
  • an event request is described on this page. If the page is displayed by the browser, the event request described on the page is sent to the server 10 which provides this page.
  • the event requested on this page includes an event indicating a present value of an electric current, which is sent from the server 10 at intervals of one second, and an event indicating the state (normal/abnormal) of the device, which is sent from the server 10 asynchronously.
  • the current value in the specific device in the plant system 42 is monitored by the server 10 every second through the controller 40 .
  • the event generating unit 107 or event generation monitoring unit 108 generates the event of the present value of electric current at intervals of one second.
  • the state (normal/abnormal) of the control device is monitored by the server 10 through the controller 40 .
  • the event generating unit 107 or event generation monitoring unit 108 generates events of the state (normal/abnormal) of the control device non-periodically.
  • the browser processes a plurality of events (both the event indicating the present value of current and the event indicating the state of the device being transmitted in real time) sent from the server 10 in response to one event request issued in accordance with the displayed page, and reflects on the screen the event processing results on the current value display section 71 or device state display section 72 .
  • the event processing results can be reflected on the page screen image (event screen image) by using the Java(Applet) of Sun Microsystems, JavaScript of Netscape Communications, or Dynamic HTML of Microsoft. Needless to say, the method is not limited to these.
  • FIG. 8 shows an HTML expression of a page, on which the screen display in FIG. 7 is based.
  • the event request to the server 10 is designated by a tag “EVENT” on the page.
  • This tag includes attributes such as a time interval (“period”) of events to be sent to the client 11 and a target (“target”) for reflecting the received event on the screen.
  • a tag “HANDLER” is introduced as a tag for reflecting the event on the screen.
  • This tag includes attributes such as a format (“type”) for screen display and a name (“name”). The same name as the name attribute is designated in the target attribute in the tag “EVENT”.
  • This example of expression is merely an example, and other formats may be used.
  • the user can monitor the present electric current value of the specific control device of the plant system at intervals of one second, without performing a display update operation, for example, by depressing a reload button.
  • the user can monitor the change in state (normal/abnormal) of the control device.
  • the server continuously returns responses (generated events) to a single event request from the client 11 while the connection is being maintained, the information transmission can be efficiently carried out without increasing a communication load between the client 11 and server 10 .
  • FIG. 9 is a block diagram showing the structure of a real-time information transmission system according to a second embodiment of the invention.
  • the structural parts common to those in FIG. 1 are denoted by like reference numerals.
  • the system in FIG. 9 differs from that in FIG. 1 in that the server 10 in FIG. 1 is replaced with a server (information providing server) 20 to which a timer unit C is added, and the client 11 in FIG. 1 is replaced with a client (information display client) 21 to which a timer unit A and a timer unit B are added.
  • the system in FIG. 9 is characterized by the provision of the timer units A to C.
  • the event transmission method is flexibly changed in accordance with the interval of occurrence of events in the server 20 , and an event request from the client 21 to the server 20 is automatically issued once again when the network 12 is cut off due to some fault.
  • timer unit A in the client 21 in the system of FIG. 9 will now be described with reference to the flow chart of FIG. 10 .
  • the timer unit A receives the page via the page receiving unit 112 and analyzes the format of the event request in the page (step C 1 ). The timer unit A then determines whether the occurrence of events is periodic on the basis of the analysis result in step C 1 (step C 2 ). If the occurrence of events is periodic, the time interval of occurrence of events is described on the page.
  • the timer unit A does not perform a special operation characterizing the present embodiment and directly instructs the event request unit 113 to issue the event request to the server 20 (step C 3 ).
  • the timer unit A sets the event occurrence time interval (obtained from the page analysis result received from the page receiving unit 112 ) at TM (step C 4 ) and determines whether the TM is longer than a predetermined time (step C 5 ).
  • the timer unit A does not perform a special operation characterizing this embodiment and directly instructs the event request unit 113 to issue the event request to the server 20 (step C 3 ).
  • the timer unit A sets the time TM in the timer unit A and starts the measurement of time, and instructs the event request unit 113 to issue the event request to the server 20 (step C 6 ).
  • the event request is issued from the event request unit 113 to the server 20 .
  • the event request unit 113 issues an event request to which the information on the time of the issuance of the next event request is added.
  • the event receiving unit 114 processes the event and the network interface 109 cuts off the connection of the network 12 relating to this event (step C 7 ).
  • the event (event notification) sent from the server 20 is provided with information on the occurrence time of a same-kind event if the time of the next occurrence of the same-kind event is understood, for example, in a case where the events are generated periodically.
  • the timer unit A halts until the measurement of the time TM is completed, that is, from the-time of start of step C 6 to the end of time TM (step C 8 ). If the time TM is measured, that is, if the time of occurrence of the next event arrives, the timer unit A returns to step C 6 and repeats the same processing.
  • the functions of the timer A are as follows. Where the time interval of occurrence of events in the server 20 is periodic, and where the time interval TM is longer than the predetermined time, the timer unit A measures the time TM up to the reception of the event and, during this time period, cuts off the network connection for receiving the event. If the time TM has been measured, the event request is explicitly issued from the client 21 (i.e. the event request unit 113 in the client 21 ) to the server 21 . Thereby, a useless load on the server ( 20 ) side is reduced while the event does not occur. On the client ( 21 ) side, too, a useless load is reduced when the client 21 waits for the reception of the event in a time period in which no event is to be sent from the server 20 .
  • time interval of occurrence of events is used.
  • an absolute time of occurrence of events may be used.
  • timer unit B in the client 21 in the system of FIG. 9 The operation of, in particular, the timer unit B in the client 21 in the system of FIG. 9 will now be described with reference to the flow chart of FIG. 11 .
  • the timer unit B receives via the event receiving unit 114 the event sent from the server 20 (step D 1 ).
  • the timer unit B determines whether the time of the next occurrence of a same-kind event is described in the event (step D 2 ). If it is not described, the control returns to step D 1 . If it is described, the time of the next occurrence of the same-kind event is set at TM (step D 3 ) and it is checked whether the next event has been actually received at that time (step D 4 ). If the event has been received at time TM, the control returns to step D 2 . On the other hand, if the event has not been received at time TM, the event request unit 113 is instructed to issue the event request to the server 20 and the control returns to step D 1 .
  • the functions of the timer unit B are as follows. If information on the time of the next occurrence of the same-kind event is added to the event sent from the server 20 , for example, in a case where the time interval of events generated in the server 20 is periodic, the timer unit B monitors whether the event has been sent from the server 20 to the client 21 in response to the event request from the client 21 at the time represented by the information. If the event is not sent from the server 20 at the time at which it should normally be sent, the client 21 issues the event request to the server 20 once again. Thereby, even if the network 12 is temporarily cut off due to some cause, the reception of the event can be resumed
  • an associated processing procedure may be preset in a page in which the event request is set and this page may be sent from the server 20 to the client 21 .
  • this processing procedure may be set in the event sent from the server 20 to the client 21 in response to the event request.
  • the Java Applet
  • JavaScript of Netscape Communications
  • the event request is periodically sent by the timer unit A from the client 21 to the server 20 . If the time of the next occurrence of the event request is known in the client 21 as in the case where the event requests are issued periodically from the client 21 , the event request to which information on the time of the next occurrence of the event request is added is issued to the server 20 .
  • the timer unit C is used to check the event request to which the information on the time of the next occurrence of the event request is added, which is sent from the client 21 (i.e. the event request unit 113 in the client 21 ).
  • step E 1 the timer unit C determines whether the time of issuance of the next event request is described in the event request. If it is not described, the timer unit C performs nothing (step E 3 ).
  • the timer unit C sets the time at TM (step E 4 ) and determines whether the next event request has been actually received at the time TM (step E 5 ). If the event request has been received, the control returns to step E 2 and repeats the same operations. If the event request has not been received, the associated item is deleted from the connection management unit 105 and the connection relating to this event is cut off (step E 6 ).
  • the functions of the timer unit C are as follows.
  • the timer unit C measures a set time of arrival of the event request which is to be sent from the client 21 to the server 20 . If the event request has not arrived at the set time, the timer unit C determines that some fault has occurred in the network 12 or abnormality has occurred in the client 21 , and cuts off the connection. If there occurred no fault or abnormality in the network 12 or client 21 and the connection was cut off due to a temporary delay in the network 12 , the event request is issued once again from the client 21 by the above-described function of the timer unit B in the client 21 . Therefore, the connection can be automatically resumed.
  • FIG. 13 is a block diagram showing the structure of a real-time information transmission system according to a third embodiment of the invention.
  • the structural parts common to those in FIG. 1 are denoted by like reference numerals.
  • the system in FIG. 13 differs from that in FIG. 1 in that the server 10 in FIG. 1 is replaced with a server 30 to which an exclusive page management unit 300 is added.
  • the exclusive page management unit 300 registers sets of page identifiers (e.g. URL) for identifying pages which cannot be displayed at the same time on a plurality of clients 11 , that is, exclusive pages. Where there is a client 11 waiting for display of an exclusive page, the identifier of the exclusive page as well as a queue of a client identifier of the client 11 in the waiting state are added.
  • the exclusive page (the identifier thereof) is registered in the exclusive page management unit 300 by setting, in the page request to be sent to the server 30 from client 11 , information declaring that the request page is to be used exclusively.
  • the exclusive page management unit 300 has a function of processing a given HTML file 100 by adding thereto a tag “EMBED” or a tag “EVENT” so as to issue a specific event request.
  • the system shown in FIG. 13 is characterized by using the server 30 to which the exclusive page management unit 300 is added. Thereby, as will be described later, while a certain client 11 (client A) is displaying a specific page (e.g. page P) sent from the server 30 , even if another client (client B) issues the same page request to the server 30 , the server 30 sends to the client B a page (e.g. page Q) different from the requested page P.
  • the system in FIG. 13 is further characterized in that when the client A has displayed another page, the screen of the client B is automatically enabled to display the requested page (page P).
  • the system in FIG. 13 is characterized in that the same page cannot be displayed at the same time on a plurality of clients 11 .
  • the server 30 which is constructed by adding the exclusive page management unit 300 to the server in the first embodiment, is used, and the client 11 used in the first embodiment is used as such.
  • the server 20 and client 21 used in the second embodiment may be substituted.
  • the exclusive page management unit 300 receives from the page request receiving unit 102 a query as to whether the requested page is a page registered in the exclusive page management unit 300 , that is, an exclusive page (steps F 1 , F 2 ). If it is not the exclusive page, the exclusive page management unit 300 performs no operation and the control ends (step F 3 ). In this case, the requested page is told from the page request receiving unit 102 to the page transmission unit 103 .
  • the HTML file 100 corresponding to the requested page is sent from the page transmission unit 103 to the client 11 (A) at the request originating point via the network interface 101 .
  • the exclusive page management unit 300 asks the connection management unit 105 whether the connection to the event request described in the page (P) is registered (steps F 4 , F 5 ). It should be noted that if the connection is registered, another client 11 (client B) has already displayed the same page (P).
  • the exclusive page management unit 300 may register, an identifier of the client displaying the exclusive page in combination with the page identifier of this page.
  • the exclusive page management unit 300 registers the identifier of the client 11 (A) at the page request originating point in the queue combined with the identifier of the exclusive page (P). At this time, if there is no client identifier already registered in the queue, the identifier of the client 11 (A) is registered at the first position of the queue.
  • the exclusive page management unit 300 tells a specific page (page Q) for periodically issuing event requests to the page transmission unit 103 via the page request receiving unit 102 and instructs the page transmission unit 103 to return the specific page (Q) to the client 11 (A) (step F 6 ).
  • the specific page (Q) is a page different from the target page (P) requested by the client 11 (A). It should suffice if the client 11 (A) receives the page (Q) and can determine that the requested page (P) has already been displayed on another client 11 .
  • the exclusive page management unit 300 incorporates a tag for periodically issuing event requests in the HTML file 100 corresponding to the requested page (P), and generates a new HTML file 100 (step F 7 ).
  • the exclusive page management unit 300 instructs the page transmission unit 103 to send the generated HTML file 100 to the client 11 (A) at the request originating point (step F 8 ).
  • the server side can detect that the client changes the display to another page, that the network has been cut off due to some fault, or that abnormality (including a normal termination) has occurred in the client.
  • the server 30 can detect the abnormality since the event request cannot be sent from the client 11 or the event request cannot be sent to the server 30 , despite the event request being described in the HTML file 100 sent to the client 11 at the request originating point.
  • the server 30 sends the event for displaying the same page as the target page (P), i.e. the page returned in step F 7 , to the other client 11 (B) requesting the same page (P), i.e. the client 11 (B) displaying the specific page (Q) returned in step F 6 .
  • the client 11 (B) which received this event the screen image is changed according to the event processing result and the target page (P) is automatically displayed.
  • the client 11 (B) which has received the page generated in step F 6 , does not display the target page (P). In this case, since the client 11 (B) cannot display the target page, it may be considered that the client 11 (B) is in the locked state.
  • the server 30 may be provided with a function of ignoring a specific request, if such a specific request, e.g. a page request or an event request, is sent from the client 11 (B) to the server 30 .
  • This embodiment aims at preventing simultaneous display of the same page on a plurality of clients.
  • the number of clients which can simultaneously display a specific page is not limited to one as in this embodiment.
  • the functional element groups constituting the above-described server (information providing server) 10 , 20 , 30 , or the processing procedures executed in the server 10 , 20 , 30 are realized by programs for enabling computers to function as an assembly of the functional element groups. Alternatively, they are realized by mounting in computers recording media such as CD-ROMs recording programs for enabling the computers to execute the processing procedures, and causing the computers to read and execute the programs. These programs may be loaded in the computers via communication media such as communication lines.
  • the above-described systems are applicable to control devices and OA devices connected to a network, or mobile phones and TV sets.
  • the network in this context is not limited to a large-scale one such as the Internet. It refers to an entirety in which a plurality of functional elements are interconnected and information is exchanged among the functional elements.
  • the network may be a serial bus.
  • a server and a client may be accommodated in one housing.
  • An examples of this structure is a system comprising a CPU in a personal computer and a microprocessor (input/output driver) of a peripheral device.
  • this invention is applicable to a system comprising a server for monitoring the occurrence of an event corresponding to update of information (in the case of OA equipment such as a printer, an event indicating lack of printing paper, or an event indicating lack of toner) and a client requiring such information.
  • a server for monitoring the occurrence of an event corresponding to update of information (in the case of OA equipment such as a printer, an event indicating lack of printing paper, or an event indicating lack of toner) and a client requiring such information.
  • event request which requests updated information of currently opened page information
  • event notifications reflecting updated information contents are automatically sent to the client in response to a single event request from the client, each time an event corresponding to update of information on the server side, on which the information displayed on the client side is based, has occurred. Therefore, the information update on the server side can be automatically and immediately reflected on the client side.
  • information update on the server side can be efficiently reflected on the screen of the client side, and the reliability and stability of communication between the server and client can be enhanced.
  • an exclusive control can be performed to prevent a specific page from being simultaneously displayed on a plurality of clients.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
US09/342,732 1998-06-30 1999-06-29 Real-time information transmission system Expired - Fee Related US6480883B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP10-199587 1998-06-30
JP19958798A JP4634547B2 (ja) 1998-06-30 1998-06-30 リアルタイム情報配信方法

Publications (1)

Publication Number Publication Date
US6480883B1 true US6480883B1 (en) 2002-11-12

Family

ID=16410334

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/342,732 Expired - Fee Related US6480883B1 (en) 1998-06-30 1999-06-29 Real-time information transmission system

Country Status (2)

Country Link
US (1) US6480883B1 (ja)
JP (1) JP4634547B2 (ja)

Cited By (59)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010014601A1 (en) * 2000-02-14 2001-08-16 Tatsuru Kuwabara Client server system for mobile phone
US20010051982A1 (en) * 1999-12-27 2001-12-13 Paul Graziani System and method for application specific chat room access
US20020002633A1 (en) * 2000-06-23 2002-01-03 Colling John K. Event notification system
US20020010803A1 (en) * 2000-05-25 2002-01-24 Oberstein Brien M. Method, system and apparatus for establishing, monitoring, and managing connectivity for communication among heterogeneous systems
US20020152239A1 (en) * 2001-04-16 2002-10-17 David Bautista-Lloyd Method, system, and program for providing data updates to a page including multiple regions of dynamic content
US20020178266A1 (en) * 2001-04-27 2002-11-28 Alexander Perez High speed server system
US20020191025A1 (en) * 2001-06-19 2002-12-19 International Business Machines Corporation Method and system for processing wait window information
US20030009488A1 (en) * 2001-05-22 2003-01-09 Reuters America, Inc System and method of accelerating delivery of dynamic web pages over a network
US20030028620A1 (en) * 2001-06-20 2003-02-06 Ludger Woelfel Method of handling a data request
US20030200255A1 (en) * 2002-04-19 2003-10-23 International Business Machines Corporation System and method for preventing timeout of a client
US20040107272A1 (en) * 2001-06-01 2004-06-03 Manukyan Jaques A. Method and system for automatically configuring a client-server network
US6763384B1 (en) * 2000-07-10 2004-07-13 International Business Machines Corporation Event-triggered notification over a network
US20040139350A1 (en) * 2003-01-15 2004-07-15 Xerox Corporation A generic application architecture suitable for firewall traversal
US6829639B1 (en) * 1999-11-15 2004-12-07 Netvision, Inc. Method and system for intelligent global event notification and control within a distributed computing environment
US20050010923A1 (en) * 2003-07-11 2005-01-13 Davis Bradford C. Trigger support for a bi-directional broker
US20050071754A1 (en) * 2003-09-30 2005-03-31 Morgan Daivid J. Pushing information to distributed display screens
US20050132217A1 (en) * 2003-02-07 2005-06-16 Broadon Communications Corp. Secure and backward-compatible processor and secure software execution thereon
US20050188078A1 (en) * 2004-02-23 2005-08-25 Kotzin Michael D. System and method for managing and associating dynamic containers of a content providing device
US20050197932A1 (en) * 2004-03-03 2005-09-08 George Gati Method for displaying accumulated interest
US20050203917A1 (en) * 2004-03-12 2005-09-15 Ocean And Coastal Environmental Sensing, Inc. System and method for delivering information on demand
US20050273439A1 (en) * 2003-02-07 2005-12-08 Wei Yen System and method for generating new licenses
US6978303B1 (en) * 1999-10-26 2005-12-20 Iontal Limited Monitoring of computer usage
US20070076227A1 (en) * 2005-09-30 2007-04-05 Tobias Lindquist Electronic apparatus with server device for managing setting data
JP2007516527A (ja) * 2003-12-18 2007-06-21 サムスン エレクトロニクス カンパニー リミテッド ネットワーク化された装置に通知をプッシングする方法及びシステム
US20080010386A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method and apparatus for client wiring model
US20080010387A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method for defining a Wiki page layout using a Wiki page
US20080010590A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method for programmatically hiding and displaying Wiki page layout sections
US20080010388A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method and apparatus for server wiring model
US20080010345A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method and apparatus for data hub objects
US20080010338A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method and apparatus for client and server interaction
US20080010615A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Generic frequency weighted visualization component
US20080010249A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Relevant term extraction and classification for Wiki content
US20080016153A1 (en) * 1996-06-12 2008-01-17 Mount Hamilton Partners, Llc System and Method for Generating a Modified Web Page by Inline Code Insertion in Response to an Information Request From a Client Computer
JP2008515032A (ja) * 2004-08-17 2008-05-08 ショー パーシング リミティド ライアビリティ カンパニー リアルタイム配信ネットワークによって個別コンテンツを配信する技法
US20080126944A1 (en) * 2006-07-07 2008-05-29 Bryce Allen Curtis Method for processing a web page for display in a wiki environment
US20090089368A1 (en) * 2007-09-28 2009-04-02 International Business Machines Corporation Automating user's operations
US7529835B1 (en) * 2003-12-22 2009-05-05 The Weather Channel, Inc. Website changes to scalability, capacity, server impact, bandwidth and end-user presentation based on a triggered event
US20090149165A1 (en) * 2000-10-17 2009-06-11 Sony Ericsson Mobile Communications Ab Exchange of Information in a Communication Network
US7613915B2 (en) 2006-11-09 2009-11-03 BroadOn Communications Corp Method for programming on-chip non-volatile memory in a secure processor, and a device so programmed
US7624276B2 (en) 2006-10-16 2009-11-24 Broadon Communications Corp. Secure device authentication system and method
US20100131595A1 (en) * 2008-11-27 2010-05-27 Ricoh Company, Ltd. Apparatus and method for updating displayed web page
US7779482B1 (en) 2003-02-07 2010-08-17 iGware Inc Delivery of license information using a short messaging system protocol in a closed content distribution system
US20100217872A1 (en) * 2009-02-26 2010-08-26 Microsoft Corporation Notification model over a server-to-server connection pool
US7787872B2 (en) 2000-01-19 2010-08-31 Sony Ericsson Mobile Communications Ab Method and apparatus for event-triggered exchange of location-based information in a communications network
US7929470B2 (en) * 2000-01-19 2011-04-19 Sony Ericsson Mobile Communications Ab Method and apparatus for exchange of information in a communication network
US8009592B2 (en) 2000-01-19 2011-08-30 Sony Ericsson Mobile Communications Ab Method and apparatus for exchange of information in a communication system
US8027443B2 (en) 2001-08-15 2011-09-27 Sony Ericsson Mobile Communications Ab Method and apparatus for exchange of data objects between network nodes depending on terminal capability
US8200961B2 (en) 2006-11-19 2012-06-12 Igware, Inc. Securing a flash memory block in a secure device system and method
CN103080916A (zh) * 2011-06-13 2013-05-01 株式会社Ntt都科摩 通信终端以及内容更新方法
US20130197699A1 (en) * 2010-10-18 2013-08-01 Mitsubishi Electric Corporation Air conditioner control device, equipment system, and program
US8560956B2 (en) 2006-07-07 2013-10-15 International Business Machines Corporation Processing model of an application wiki
US8627097B2 (en) 2012-03-27 2014-01-07 Igt System and method enabling parallel processing of hash functions using authentication checkpoint hashes
CN101057476B (zh) * 2004-08-17 2014-01-08 肖分析有限公司 用实时路由网络递送个人化内容的方法和装置
US9071648B2 (en) 2000-12-18 2015-06-30 Shaw Parsing L.L.C. Asynchronous messaging using a node specialization architecture in the dynamic routing network
US9130765B1 (en) * 1996-06-12 2015-09-08 Michael Carringer System and method for generating a modified web page by inline code insertion in response to an information request from a client computer
US9613076B2 (en) 2000-12-18 2017-04-04 Zarbaña Digital Fund Llc Storing state in a dynamic content routing network
US9646142B2 (en) 2003-02-07 2017-05-09 Acer Cloud Technology Inc. Ensuring authenticity in a closed content distribution system
US9800671B1 (en) * 2000-06-28 2017-10-24 Intel Corporation Repeatedly accessing a storage resource normally accessed through a web page without accessing the web page
US10664575B2 (en) 2006-05-02 2020-05-26 Acer Cloud Technology, Inc. Virtual vault of licensed content

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030005456A1 (en) * 2000-01-27 2003-01-02 Takefumi Naganuma Method and system for distributing program, server and client terminals for executing program, device for obtaining program, and recording medium
US6728763B1 (en) * 2000-03-09 2004-04-27 Ben W. Chen Adaptive media streaming server for playing live and streaming media content on demand through web client's browser with no additional software or plug-ins
JP4588190B2 (ja) * 2000-10-27 2010-11-24 シャープ株式会社 テレビ番組ホームページ検索システム、そのクライアント装置、サーバ装置、及びホームページのｕｒｌ情報の取得方法
JP4307747B2 (ja) 2001-01-25 2009-08-05 インターナショナル・ビジネス・マシーンズ・コーポレーション 接続受付システム、受付サーバ、クライアント端末、接続受付管理方法、記憶媒体、コンピュータプログラム
JP4890740B2 (ja) * 2001-09-29 2012-03-07 シーベル・システムズ・インコーポレイテッド ウェブブラウザに対する非同期メッセージのプッシュ
KR100676384B1 (ko) * 2001-11-01 2007-01-30 시바우라 메카트로닉스 가부시키가이샤 기판 반송장치 및 기판 반송방법
US7526672B2 (en) * 2004-02-25 2009-04-28 Microsoft Corporation Mutual exclusion techniques in a dynamic peer-to-peer environment
JP2006185384A (ja) * 2004-12-28 2006-07-13 Matsushita Electric Ind Co Ltd コンテンツサーバ、コンテンツ受信装置、プログラム及び記録媒体
US20070022198A1 (en) * 2005-07-19 2007-01-25 Samsung Electronics Co., Ltd. Method and system for pushing asynchronous notifications to networked devices
KR100772861B1 (ko) 2005-09-23 2007-11-02 삼성전자주식회사 원격 사용자 인터페이스를 제공하는 장치 및 방법
JP2009289163A (ja) * 2008-05-30 2009-12-10 Toshiba Corp サーバ装置および通信システム
JP2012059056A (ja) * 2010-09-09 2012-03-22 Sharp Corp コンテンツ配信システム、コンテンツ配信方法、サーバ、コンテンツ再生装置、プログラム、および記録媒体

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5774670A (en) * 1995-10-06 1998-06-30 Netscape Communications Corporation Persistent client state in a hypertext transfer protocol based client-server system
US5893091A (en) * 1997-04-11 1999-04-06 Immediata Corporation Multicasting with key words
US5925100A (en) * 1996-03-21 1999-07-20 Sybase, Inc. Client/server system with methods for prefetching and managing semantic objects based on object-based prefetch primitive present in client's executing application
US6021437A (en) * 1996-07-17 2000-02-01 Bull S.A. Process and system for real-time monitoring of a data processing system for its administration and maintenance support in the operating phase
US6243761B1 (en) * 1998-03-26 2001-06-05 Digital Equipment Corporation Method for dynamically adjusting multimedia content of a web page by a server in accordance to network path characteristics between client and server
US6247056B1 (en) * 1997-02-03 2001-06-12 Oracle Corporation Method and apparatus for handling client request with a distributed web application server
US6289370B1 (en) * 1998-11-30 2001-09-11 3Com Corporation Platform independent enhanced help system for an internet enabled embedded system
US6304909B1 (en) * 1998-12-18 2001-10-16 International Business Machines Corporation Client-controlled link processing in computer network

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5774670A (en) * 1995-10-06 1998-06-30 Netscape Communications Corporation Persistent client state in a hypertext transfer protocol based client-server system
US5925100A (en) * 1996-03-21 1999-07-20 Sybase, Inc. Client/server system with methods for prefetching and managing semantic objects based on object-based prefetch primitive present in client's executing application
US6021437A (en) * 1996-07-17 2000-02-01 Bull S.A. Process and system for real-time monitoring of a data processing system for its administration and maintenance support in the operating phase
US6247056B1 (en) * 1997-02-03 2001-06-12 Oracle Corporation Method and apparatus for handling client request with a distributed web application server
US5893091A (en) * 1997-04-11 1999-04-06 Immediata Corporation Multicasting with key words
US6243761B1 (en) * 1998-03-26 2001-06-05 Digital Equipment Corporation Method for dynamically adjusting multimedia content of a web page by a server in accordance to network path characteristics between client and server
US6289370B1 (en) * 1998-11-30 2001-09-11 3Com Corporation Platform independent enhanced help system for an internet enabled embedded system
US6304909B1 (en) * 1998-12-18 2001-10-16 International Business Machines Corporation Client-controlled link processing in computer network

Cited By (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080016153A1 (en) * 1996-06-12 2008-01-17 Mount Hamilton Partners, Llc System and Method for Generating a Modified Web Page by Inline Code Insertion in Response to an Information Request From a Client Computer
US9130765B1 (en) * 1996-06-12 2015-09-08 Michael Carringer System and method for generating a modified web page by inline code insertion in response to an information request from a client computer
US9021023B2 (en) 1996-06-12 2015-04-28 Smooth Ride, Series 53 Of Allied Security Trust I System and method for generating a modified web page by inline code insertion in response to an information request from a client computer
US8601050B2 (en) 1996-06-12 2013-12-03 Michael Carringer System and method for generating a modified web page by inline code insertion in response to an information request from a client computer
US6978303B1 (en) * 1999-10-26 2005-12-20 Iontal Limited Monitoring of computer usage
US6829639B1 (en) * 1999-11-15 2004-12-07 Netvision, Inc. Method and system for intelligent global event notification and control within a distributed computing environment
US20010051982A1 (en) * 1999-12-27 2001-12-13 Paul Graziani System and method for application specific chat room access
US7787872B2 (en) 2000-01-19 2010-08-31 Sony Ericsson Mobile Communications Ab Method and apparatus for event-triggered exchange of location-based information in a communications network
US8009592B2 (en) 2000-01-19 2011-08-30 Sony Ericsson Mobile Communications Ab Method and apparatus for exchange of information in a communication system
US7929470B2 (en) * 2000-01-19 2011-04-19 Sony Ericsson Mobile Communications Ab Method and apparatus for exchange of information in a communication network
US20010014601A1 (en) * 2000-02-14 2001-08-16 Tatsuru Kuwabara Client server system for mobile phone
US20020010803A1 (en) * 2000-05-25 2002-01-24 Oberstein Brien M. Method, system and apparatus for establishing, monitoring, and managing connectivity for communication among heterogeneous systems
US7216145B2 (en) * 2000-06-23 2007-05-08 Mission Communications, Llc Event notification system
US20020002633A1 (en) * 2000-06-23 2002-01-03 Colling John K. Event notification system
US9800671B1 (en) * 2000-06-28 2017-10-24 Intel Corporation Repeatedly accessing a storage resource normally accessed through a web page without accessing the web page
US6763384B1 (en) * 2000-07-10 2004-07-13 International Business Machines Corporation Event-triggered notification over a network
US8037192B2 (en) 2000-10-17 2011-10-11 Sony Ericsson Mobile Communications Ab Exchange of information in a communication network
US20090149165A1 (en) * 2000-10-17 2009-06-11 Sony Ericsson Mobile Communications Ab Exchange of Information in a Communication Network
US20110161458A1 (en) * 2000-12-18 2011-06-30 Shaw Parsing, Llc Techniques For Delivering Personalized Content With A Real-Time Routing Network
US9613076B2 (en) 2000-12-18 2017-04-04 Zarbaña Digital Fund Llc Storing state in a dynamic content routing network
US7930362B2 (en) 2000-12-18 2011-04-19 Shaw Parsing, Llc Techniques for delivering personalized content with a real-time routing network
US9071648B2 (en) 2000-12-18 2015-06-30 Shaw Parsing L.L.C. Asynchronous messaging using a node specialization architecture in the dynamic routing network
US20020152239A1 (en) * 2001-04-16 2002-10-17 David Bautista-Lloyd Method, system, and program for providing data updates to a page including multiple regions of dynamic content
US7000008B2 (en) * 2001-04-16 2006-02-14 Sun Microsystems, Inc. Method, system, and program for providing data updates to a page including multiple regions of dynamic content
US20020178266A1 (en) * 2001-04-27 2002-11-28 Alexander Perez High speed server system
US7376653B2 (en) * 2001-05-22 2008-05-20 Reuters America, Inc. Creating dynamic web pages at a client browser
US20030009488A1 (en) * 2001-05-22 2003-01-09 Reuters America, Inc System and method of accelerating delivery of dynamic web pages over a network
US7177897B2 (en) 2001-06-01 2007-02-13 Intergenix Method and system for automatically configuring a client-server network
US20040107272A1 (en) * 2001-06-01 2004-06-03 Manukyan Jaques A. Method and system for automatically configuring a client-server network
US7062720B2 (en) * 2001-06-19 2006-06-13 International Business Machines Corporation Method and system for processing wait window information
US20020191025A1 (en) * 2001-06-19 2002-12-19 International Business Machines Corporation Method and system for processing wait window information
US20030028620A1 (en) * 2001-06-20 2003-02-06 Ludger Woelfel Method of handling a data request
US8027443B2 (en) 2001-08-15 2011-09-27 Sony Ericsson Mobile Communications Ab Method and apparatus for exchange of data objects between network nodes depending on terminal capability
US7330894B2 (en) * 2002-04-19 2008-02-12 International Business Machines Corporation System and method for preventing timeout of a client
US20080052351A1 (en) * 2002-04-19 2008-02-28 International Business Machines Corporation System and method for preventing timeout of a client
US20030200255A1 (en) * 2002-04-19 2003-10-23 International Business Machines Corporation System and method for preventing timeout of a client
US20040139350A1 (en) * 2003-01-15 2004-07-15 Xerox Corporation A generic application architecture suitable for firewall traversal
US7480936B2 (en) * 2003-01-15 2009-01-20 Xerox Corporation Generic application architecture suitable for firewall traversal
US7380275B2 (en) 2003-02-07 2008-05-27 Broadon Communications Corp. Secure and backward-compatible processor and secure software execution thereon
US9646142B2 (en) 2003-02-07 2017-05-09 Acer Cloud Technology Inc. Ensuring authenticity in a closed content distribution system
US20050273439A1 (en) * 2003-02-07 2005-12-08 Wei Yen System and method for generating new licenses
US7779482B1 (en) 2003-02-07 2010-08-17 iGware Inc Delivery of license information using a short messaging system protocol in a closed content distribution system
US8131649B2 (en) 2003-02-07 2012-03-06 Igware, Inc. Static-or-dynamic and limited-or-unlimited content rights
US20050132217A1 (en) * 2003-02-07 2005-06-16 Broadon Communications Corp. Secure and backward-compatible processor and secure software execution thereon
US7322042B2 (en) 2003-02-07 2008-01-22 Broadon Communications Corp. Secure and backward-compatible processor and secure software execution thereon
US9985781B2 (en) 2003-02-07 2018-05-29 Acer Cloud Technology, Inc. Ensuring authenticity in a closed content distribution system
US10263774B2 (en) 2003-02-07 2019-04-16 Acer Cloud Technology, Inc. Ensuring authenticity in a closed content distribution system
US7757235B2 (en) * 2003-07-11 2010-07-13 Computer Associates Think, Inc. Trigger support for a bi-directional broker
US20050010923A1 (en) * 2003-07-11 2005-01-13 Davis Bradford C. Trigger support for a bi-directional broker
US20050071754A1 (en) * 2003-09-30 2005-03-31 Morgan Daivid J. Pushing information to distributed display screens
JP2007516527A (ja) * 2003-12-18 2007-06-21 サムスン エレクトロニクス カンパニー リミテッド ネットワーク化された装置に通知をプッシングする方法及びシステム
US7529835B1 (en) * 2003-12-22 2009-05-05 The Weather Channel, Inc. Website changes to scalability, capacity, server impact, bandwidth and end-user presentation based on a triggered event
US20050188078A1 (en) * 2004-02-23 2005-08-25 Kotzin Michael D. System and method for managing and associating dynamic containers of a content providing device
US20050197932A1 (en) * 2004-03-03 2005-09-08 George Gati Method for displaying accumulated interest
US7949726B2 (en) 2004-03-12 2011-05-24 Ocean And Coastal Environmental Sensing, Inc. System and method for delivering information on demand
US20050203917A1 (en) * 2004-03-12 2005-09-15 Ocean And Coastal Environmental Sensing, Inc. System and method for delivering information on demand
CN101057476B (zh) * 2004-08-17 2014-01-08 肖分析有限公司 用实时路由网络递送个人化内容的方法和装置
JP2008515032A (ja) * 2004-08-17 2008-05-08 ショー パーシング リミティド ライアビリティ カンパニー リアルタイム配信ネットワークによって個別コンテンツを配信する技法
US20070076227A1 (en) * 2005-09-30 2007-04-05 Tobias Lindquist Electronic apparatus with server device for managing setting data
US8150944B2 (en) * 2005-09-30 2012-04-03 Sony Ericsson Mobile Communications Ab Electronic apparatus with server device for managing setting data
US10664575B2 (en) 2006-05-02 2020-05-26 Acer Cloud Technology, Inc. Virtual vault of licensed content
US10733271B2 (en) 2006-05-02 2020-08-04 Acer Cloud Technology, Inc. Systems and methods for facilitating secure streaming of electronic gaming content
US20080010388A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method and apparatus for server wiring model
US20080010387A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method for defining a Wiki page layout using a Wiki page
US20080010338A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method and apparatus for client and server interaction
US20080010615A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Generic frequency weighted visualization component
US8196039B2 (en) 2006-07-07 2012-06-05 International Business Machines Corporation Relevant term extraction and classification for Wiki content
US20080010590A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method for programmatically hiding and displaying Wiki page layout sections
US8219900B2 (en) 2006-07-07 2012-07-10 International Business Machines Corporation Programmatically hiding and displaying Wiki page layout sections
US20080010345A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method and apparatus for data hub objects
US20080010386A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Method and apparatus for client wiring model
US20080010249A1 (en) * 2006-07-07 2008-01-10 Bryce Allen Curtis Relevant term extraction and classification for Wiki content
US7954052B2 (en) 2006-07-07 2011-05-31 International Business Machines Corporation Method for processing a web page for display in a wiki environment
US8560956B2 (en) 2006-07-07 2013-10-15 International Business Machines Corporation Processing model of an application wiki
US8775930B2 (en) 2006-07-07 2014-07-08 International Business Machines Corporation Generic frequency weighted visualization component
US20080126944A1 (en) * 2006-07-07 2008-05-29 Bryce Allen Curtis Method for processing a web page for display in a wiki environment
US7624276B2 (en) 2006-10-16 2009-11-24 Broadon Communications Corp. Secure device authentication system and method
US7991999B2 (en) 2006-10-16 2011-08-02 Igware Inc. Block-based media content authentication
US9589154B2 (en) 2006-11-09 2017-03-07 Acer Cloud Technology Inc. Programming on-chip non-volatile memory in a secure processor using a sequence number
US8621188B2 (en) 2006-11-09 2013-12-31 Acer Cloud Technology, Inc. Certificate verification
US8601247B2 (en) 2006-11-09 2013-12-03 Acer Cloud Technology, Inc. Programming non-volatile memory in a secure processor
US8856513B2 (en) 2006-11-09 2014-10-07 Acer Cloud Technology, Inc. Programming on-chip non-volatile memory in a secure processor using a sequence number
US7613915B2 (en) 2006-11-09 2009-11-03 BroadOn Communications Corp Method for programming on-chip non-volatile memory in a secure processor, and a device so programmed
US9881182B2 (en) 2006-11-09 2018-01-30 Acer Cloud Technology, Inc. Programming on-chip non-volatile memory in a secure processor using a sequence number
US8200961B2 (en) 2006-11-19 2012-06-12 Igware, Inc. Securing a flash memory block in a secure device system and method
US9355059B2 (en) * 2007-09-28 2016-05-31 International Business Machines Corporation Automating user's operations
US9832285B2 (en) 2007-09-28 2017-11-28 International Business Machines Corporation Automating user's operations
US20090089368A1 (en) * 2007-09-28 2009-04-02 International Business Machines Corporation Automating user's operations
US20100131595A1 (en) * 2008-11-27 2010-05-27 Ricoh Company, Ltd. Apparatus and method for updating displayed web page
US8346852B2 (en) 2008-11-27 2013-01-01 Ricoh Company, Ltd. Apparatus and method for updating displayed web page
US8886787B2 (en) * 2009-02-26 2014-11-11 Microsoft Corporation Notification for a set of sessions using a single call issued from a connection pool
US20100217872A1 (en) * 2009-02-26 2010-08-26 Microsoft Corporation Notification model over a server-to-server connection pool
US20130197699A1 (en) * 2010-10-18 2013-08-01 Mitsubishi Electric Corporation Air conditioner control device, equipment system, and program
US9535430B2 (en) * 2010-10-18 2017-01-03 Mitsubishi Electric Corporation Air conditioner control device, equipment system, and program
CN103080916B (zh) * 2011-06-13 2015-11-25 株式会社Ntt都科摩 通信终端以及内容更新方法
US20130145013A1 (en) * 2011-06-13 2013-06-06 Ntt Docomo, Inc. Communication terminal and content update method
CN103080916A (zh) * 2011-06-13 2013-05-01 株式会社Ntt都科摩 通信终端以及内容更新方法
US8966278B2 (en) 2012-03-27 2015-02-24 Igt System and method enabling parallel processing of hash functions using authentication checkpoint hashes
US8627097B2 (en) 2012-03-27 2014-01-07 Igt System and method enabling parallel processing of hash functions using authentication checkpoint hashes

Also Published As

Publication number Publication date
JP4634547B2 (ja) 2011-02-16
JP2000020423A (ja) 2000-01-21

Similar Documents

Publication Publication Date Title
US6480883B1 (en) Real-time information transmission system
US6393475B1 (en) Method of performing a network management transaction using a web-capable agent
US6065051A (en) Apparatus and method for communication between multiple browsers
US5996010A (en) Method of performing a network management transaction using a web-capable agent
KR100359366B1 (ko) 자각-개시 푸시를 제공하기 위한 방법 및 장치
US7290262B2 (en) Method and apparatus for dynamically determining information for deploying a web service
KR100288490B1 (ko) 상태정보를보존하는컴퓨터화된방법및상태정보보존컴퓨터시스템
US6029175A (en) Automatic retrieval of changed files by a network software agent
KR100773016B1 (ko) 데이터 처리 시스템, 테스트 방법, 모니터링 방법, 네트워크 데이터 처리 시스템, 데이터 처리 시스템 및 기록 매체
US20140149382A1 (en) Technology for Web Site Crawling
US7165222B1 (en) Information providing method and information distribution apparatus
GB2366037A (en) Customising an HTML document
US20120060079A1 (en) Discovering alternative user experiences for websites
EP1153354B1 (en) Addressing in the internet
JP2006268470A (ja) 非同期通信方法
US20070124664A1 (en) Site redirection
JP2006260343A (ja) リンク切れチェックプログラム
JPH10207805A (ja) Ｗｗｗサーバ・ｗｗｗブラウザ・システム
US20060123107A1 (en) Web link management systems and methods
US20020194327A1 (en) Method for sensing the status of a client from a server
JPH11184784A (ja) 実行状況報告機能付きサーバ及び実行状況表示機能付きクライアント
JP3682914B2 (ja) データ通信システムおよびこれに用いるデータ処理装置、ブラウザを利用した接続維持方法、記録媒体
JP2009080587A (ja) データ転送サーバ
JPH11259354A (ja) インターネット上の情報更新確認方法
JP3215060B2 (ja) サーバクライアント管理サーバ及びクライアント及びネットワークシステム

Legal Events

Date Code Title Description
AS Assignment

Owner name: KABUSHIKI KAISHA TOSHIBA, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TSUTSUMITAKE, HIDEYUKI;REEL/FRAME:010211/0380

Effective date: 19990628

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20101112