| Title of Invention | METHOD AND APPARATUS FOR STORING AND RESTORING STATE INFORMATION OF REMOTE USER INTERFACE |
|---|---|
| Abstract | Provided are an apparatus and method of restoring a remote user interface (RUI) in a Universal Plug and Play (UPnP) environment. In the apparatus and method, an RUI client requests an external storage server to store the state information of the RUI by using a Hypertext Transfer Protocol (HTTP) object processing a HTTP request without reloading a web page, and restores the original state of the RUI by using the stored state information. Accordingly, it is possible to apply a method of storing and restoring state information of a remote user interface, in a UPnP environment, to a HTTP-based remote protocol model having stateless characteristics which do not allow state information of a remote user interface to be stored. |
| Full Text | FORM 2 THE PATENTS ACT, 1970 (39 of 1970) & The Patents Rules, 2003 COMPLETE SPECIFICATION (See section 10, rule 13) “METHOD AND APPARATUS FOR STORING AND RESTORING STATE INFORMATION OF REMOTE USER INTERFACE” SAMSUNG ELECTRONICS CO., LTD., a Korean Corporation, of 416, Maetan-dong, Yeongtong-gu, Suwon-si, Gyeonggi-do, Republic of Korea. The following specification particularly describes the invention and the manner in which it is to be performed. METHOD AND APPARATUS FOR STORING AND RESTORING STATE INFORMATION OF REMOTE USER INTERFACE CROSS-REFERENCE TO RELATED PATENT APPLICATION [01] This application claims the benefits of US Provisional Patent Application No. 60/758,219, filed on January 12, 2006 in the USPTO, and Korean Patent Application No. 10-2006-0042617, filed on May 11, 2006 in the Korean Intellectual Property Office, the disclosures of which are incorporated herein in their entirety by reference. BACKGROUND OF THE INVENTION 1. Field of the Invention [02] Apparatuses and methods consistent with the present invention relate to restoring state information of a remote user interface (RUI), and more particularly, to restoring an RUI in a Universal Plug and Play (UPnP) environment. 2. Description of the Related Art [03] FIG. 1 is a block diagram of a conventional Universal Plug and Play (UPnP)-based remote user interface (RUI) network system ("the system"). Referring to FIG. 1, the system includes an RUI control point (CP) 11, an RUI client 12, and an RUI server 13. Here, the RUI Control Point (CP) 11 corresponds to a UPnP CP supporting a remote user interface, and the RUI 2 client 12 and the RUI server 13 correspond to a UPnP controlled device (CD) supporting the remote user interface. [04] According to UPnP, the RUI CP 11 discovers and controls the RUI client 12 and the RUI server 13. The RUI client 12 and the RUI server 13 that are connected under the control of the RUI CP 11, process a request and response received via an RUI according to out-of-band remote protocol, such as remote desktop protocol (RDP) and extended remote technology (XRT) protocol. [05] FIG. 2 is a diagram illustrating a conventional process of storing and restoring state information of an RUI according to UPnP. In particular, the process of FIG. 2 is related to a case where a connection of a first RUI client 22 to an RUI server 24 is changed to a connection of a second RUI client 23 to the RUI server 24. [06] In operation 201, the RUI CP 21 searches for RUI connections that are currently in progress by calling GetCurrentConnection() to the first RUI client 22, and learns a connection to the RUI server 24 from the searched RUI connections. [07] In operation 202, the RUI CP 21 calls SetUILifetime() to the RUI server 24 in order to instruct the RUI server 24 to maintain the RUI connections that are currently in progress, for a predetermined time. [08] In operation 203, the RUI CP 21 calls Disconnect(0 to the first RUI client 22 in order to terminate the RUI connections that are in progress. [09] In operation 204, the RUI CP 21 calls Connect() to the second 3 RUI client 23 in order to start the RUI connections maintained according to the instructions given in operation 202. [10] However, as described above, the conventional method of FIG. 2 is applicable only to a remote protocol model which allows all state information of URIs to be stored in an RUI server. However, in the case of a HyperText Transfer Protocol (HTTP)-based remote protocol model, when a transaction that processes a request and a response is completed, the state information of a remote interface is lost and is not stored due to the stateless characteristics of the HTTP, and therefore, the RUI client manages most of the state information. [11] Accordingly, the conventional process of storing and restoring state information of an RUI according to UPnP is applicable to remote protocol models, such as RDP and XRT, in which all state information of RUIs is stored in an RUI server. However, the conventional process has a problem in that it cannot be applied to remote protocol models, such as HTTP, in which most of the state information is managed by an RUI client. In particular, binary protocol-based RDP and XRT need a wider network bandwidth than HTTP. Therefore, since a HTTP-based RUI is widely used, the above problems exist. SUMMARY OF THE INVENTION [12] The present invention provides a method and apparatus for allowing a process of storing and restoring state information of a remote user 4 interface (RUT) in a Universal Plug and Play (UPnP) environment, to be applied to a HyperText Transfer Protocol (HTTP)-based remote protocol model, having stateless characteristics, that does not allow state information of an RUI to be stored. [13] The present invention also provides a computer readable recording medium having recorded thereon a program for executing the method. [14] According to an aspect of the present invention, there is provided a method of allowing a client, which receives the remote user interface from a server, to request state information of a remote user interface to be saved, the method comprising obtaining the state information of the remote user interface, which is generated when the remote user interface is used, by using an object which processes a predetermined request without reloading the remote user interface; and requesting that the obtained state information be stored. [15] According to another aspect of the present invention, there is provided a computer readable medium having recorded thereon a program for executing the method of requesting that state information regarding a remote user interface be stored. [16] According to another aspect of the present invention, there is provided an apparatus for allowing a client, which uses the remote user interface provided from a server, to request storage of state information of a remote user interface, the apparatus comprising a remote user interface control 5 point module obtaining information regarding a storage server which provides storage for storing the state information; and a web browser module requesting the storage server to store the state information by using an object processing a predetermined request without reloading the remote user interface, based on the information regarding the storage server obtained by the remote user interface control point module. [17] According to another aspect of the present invention, there is provided a method of allowing a client, which receives the remote user interface from a server, to restore state information of a remote user interface, the method comprising obtaining state information, which is generated when the remote user interface is used, by using an object processing a predetermined request without reloading the remote user interface; and reflecting the obtained state information in the remote user interface. [18] According to another aspect of the present invention, there is provided a computer readable medium having recorded thereon a program for executing the method of restoring state information regarding a remote user interface. [19] According to another aspect of the present invention, there is provided an apparatus for allowing to a client, which receives the remote user interface from a server, to restore state information of a remote user interface, the apparatus comprising a remote user interface control point module obtaining information regarding a storage server providing storage for storing the state information; and a web browser module obtaining the state 6 information from the storage server by using an object processing a predetermined request without reloading the remote user interface, based on the information regarding the storage server obtained by the remote user interface control point module; and reflecting the obtained state information in the remote user interface. BRIEF DESCRIPTION OF THE DRAWINGS [20] The above and other aspects of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings in which: [21 ] FIG. 1 is a block diagram of a conventional Universal Plug and Play (UPnP)-based remote user interface (RUI) network system; [22] FIG. 2 is a diagram illustrating a conventional process of storing and restoring state information of an RUI according to UPnP; [23] FIG. 3 is a block diagram of a UPnP-based RUI network system according to an exemplary embodiment of the present invention; [24] FIG. 4 is a block diagram of an RUI client according to an exemplary embodiment of the present invention; [25] FIG. 5 illustrates syntax representing an interface of a State Storage (SS) handler according to an exemplary embodiment of the present invention; [26] FIG. 6 illustrates syntax representing an interface of a Transmission Control Protocol (TCP) connection object according to an 7 exemplary embodiment of the present invention; [27] FIG. 7 is a block diagram of an RUI server according to an exemplary embodiment of the present invention; [28] FIGS. 8A and 8B illustrate syntax representing a savable page according to an exemplary embodiment of the present invention; [29] FIGS. 9A and 9B illustrate syntax representing another exemplary embodiment of the savable page represented by the syntax shown in FIGS. 8A and 8B according to the present invention; [30] FIG. 10 is a block diagram of an SS server according to an exemplary embodiment of the present invention; [31] FIG. 11 illustrates the format of a GETSTATES request message according to an exemplary embodiment of the present invention; [32] FIG. 12 illustrates the format of a GETSTATES response message according to an exemplary embodiment of the present invention; [33] FIG. 13 illustrates the format of a SAVE request message according to an exemplary embodiment of the present invention; [34] FIG. 14 illustrates the format of a restoring page request message according to an exemplary embodiment of the present invention; [35] FIG. 15 illustrates the format of a restoring page response message according to an exemplary embodiment of the present invention; [36] FIG. 16 illustrates the format of a restoring request message according to an exemplary embodiment of the present invention; [37] FIG. 17 illustrates syntax representing a savable page 8 corresponding to a restoring response document according to an exemplary embodiment of the present invention; [38] FIG. 18 is a timing diagram of a method of storing state information of an RUI according to an exemplary embodiment of the present invention; [39] FIG. 19 is a timing diagram of a method of restoring state information of an RUI according to an exemplary embodiment of the present invention; and [40] FIG. 20 is a timing diagram of an apparatus that is a combination of the RUI server of FIG. 7 and the SS server of FIG. 10 according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION [41] Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In this disclosure, a remote user interface (RUI) based on a HyperText Transfer Protocol (HTTP) which is a stateless protocol that does not store state information, will be described with respect to a web page containing a HTTP object which is a Java script object that processes a HTTP request without reloading the web page. However, it would be apparent to those of ordinary skill in the technical field to which the present invention pertains mat the exemplary embodiments of the present invention are applicable to other types of remote user interfaces, and not just the web page. [42] FIG. 3 is a block diagram of a Universal Plug and Play (UPnP)- based* RUI network system ("the system") according to an exemplary embodiment of the present invention. Referring to FIG. 3, the system includes RUI client 31 and an Nth RUI client 32, RUI servers 33 and 34, and a State Storage (SS) server 35. In particular, the SS server 35 is a server that provides a state storage for storing the state information of a web page corresponding to an RUI. Also, the RUI client 31 and an Nth RUI client 32 and the RUI servers 33 and 34 are 2-box models, each having a built-in RUI control point (CP) module and acquiring information regarding the SS server 35 during UPnP discovery. However, the RUI clients 31 and 32 and the RUI servers 33 and 34 do not need to have the built-in RUI CP module, and can receive the information regarding the SS server 35 from another node in this case. [43] FIG. 4 is a block diagram of an RUI client 4 according to an exemplary embodiment of the present invention. Referring to FIG. 4, the RUI client 4 includes an RUI CP module 41, an RUI controlled device (CD) module 42, and a web browser module 43. In particular, the RUI CP module 41 and the RUI CD module 42 are optional modules needed when the RUI client 4 is located in an autonomous network, such as a home network, to which UPnP is applicable. Also, the RUI CP module 41 may be located outside the RUI client 4, instead of inside thereof. [44] The RUI CP module 41 acts as a UPnP CP that discovers and controls UPnP CDs. In particular, according to an exemplary embodiment of the present invention, the RUI CP module 41 acquires information regarding 10 an SS server 10, based on UPnP, during discovery of an RUI server 7 and an SS server 10 which are CDs based on UPnP. Also, the RUI CP module 41 provides the information regarding the SS server 10 to an SS handler 431 in order to request that state information of a remote interface, i.e., a web page, be stored. [45] The RUI client 4 may include " hasControlPoint>", indicating that it has the RUI CP module 41, in a HTTP header. [46] The RUI CD module 42 advertises that it is a UPnP CD, and acts as a UPnP CD to be controlled by a UPnP CP that discovers the RUI CD module 42 in response to the advertisement. [47] The web browser module 43 acts as a HTTP-based general web browser. That is, the web browser module 43 is a client module mat receives a request for the web page corresponding to the remote user interface from a user, transmits the request to the RUI server 7 having a web server, and renders the web page acquired in response to the request, so as to display the rendering result. [48] In particular, the web browser module 43 may include the SS handler 431 therein or in the form of a plug-in. The SS handler 431 is an optional module needed only when the RUI CP module 41 is present. The RUI CP module 41 and the SS handler 431 are capable of establishing internal communications via interprocess communication (IPC) or a UNIX domain socket. When receiving the HTTP header and realizing that the RUI client 4 11 includes the RUICP module 41, the RUI server 7 may provide a savable page, represented by the syntax shown in FIGS. 8A and 8B, which contains a Java script using the SS handler 431 to obtain the information regarding the SS server 10. That is, when the Java script is executed, the SS handler 431 obtains the information regarding the SS server 10 from the RUI CP module 41 and provides the savable page with the obtained information. [49] FIG. 5 illustrates syntax representing an interface of the SS handler 431 illustrated in FIG. 4 according to an exemplary embodiment of the present invention. Referring to FIG. 5, the interface of the SS handler 431 provides properties representing uniform resource locators (URLs) (array URLs) of SS servers providing a state storage that stores state information of a web page corresponding to an RUI, and the names of the SS servers (array names). [50] Also, the web browser module 43 includes the HTTP object 432 in the form of a native object or plug-in. The HTTP object 432 is a Java script object that processes a request for HTTP without reloading the web page. The HTTP object 432 may be an XMLHttpRequest or a Transmission Control Protocol (TCP) connection object. [51] FIG. 6 illustrates syntax representing an interface of a TCP connection object according to an exemplary embodiment of the present invention. Referring to FIG. 6, the interface of the TCP connection object provides a callback regarding an event notifying a change in the state of a TCP connection, a callback regarding an event notifying the arrival of data, a 12 callback regarding an event notifying that a data transfer error occurs, a method of opening a TCP/IP connection, a method of acquiring the data, a method of transmitting the data, etc. [52] The web browser module 43 receives the savable page represented by the syntax shown in FIGS. 8A and 8B from the RUI server 7. Also, when receiving from the user a command to save state information regarding an RUI, that is, when the user clicks a "SAVE" button on the savable page, the web browser module 43 requests the state information regarding the RUI server 7, which is generated when the user uses the web page, in the case where a Java script included in the web page is executed to generate the state information of the RUI server 7. That is, the web browser module 43 transmits a GETSTATES request message illustrated in FIG. 11 to the RUI server 7. [53] Also, the web browser module 43 acquires the state information of the RUI server 7 in response to the request. That is, the web browser module 43 receives from the RUI server 7 a GETSTATES response message illustrated in FIG. 12 in response to the GETSTATES request message, and obtains the state information of the RUI server 7 by executing the Java script included in the web page. If the user uses a web page regarding product sales, information regarding a product that the user selects remains in the RUI server 7. Also, if the user uses a web page regarding user authentication, information regarding a result of user authentication remains in the RUI server 7. Such items of information are examples of the state information of the RUI server 7. 13 [54] Also, the web browser module 43 executes the Java script included in the web page to read the state information of the RUI client 4, which is generated when the user uses the web page, from the web page. While the user is using the web page, form input information, cookie information, and state information of an audio/visual (AV) object corresponding to an input value from the user are generated. Such items of information are examples of the state information of the RUI client 4. [55] In order to request the SS server 10 to save the above generated information and the obtained state information of the web page, that is, the state information of the RUI client 4 and the RUI server 7, the web browser module 43 receives information regarding the SS server 10 from the RUI CP module 41 or an RUI CP module 71 of the RUI server 7. More specifically, the web browser module 43 may execute the Java script included in the web page in order to display the information of the SS server 10 to the user so that the user can select the SS server 10 as a storage server for storing the state information of the web page. Otherwise, the web browser module 43 may request the SS handler 431 to provide the information of the SS server 10, and display the obtained information to the user so that the user can select the SS server 10 as a storage server for storing the state information of the web page. [56] Also, the web browser module 43 executes the Java script in the web page in order to request the SS server 10 to save the state information of the web page by using the information of the SS server 10 selected by the user, i.e., a URL of the SS server 10. That is, the web browser module 43 14 transmits a SAVE request message illustrated in FIG. 20 to the SS server 10. [57] Also, when receiving from the user a command to display a list of web pages that can be restored according to the user's selection, i.e., a list of restoring pages, the web browser module 43 receives the information of the SS server 10 from the RUI CP module 41 or the RUI CP module 71 of the RUT server 7. Also, the web browser module 43 requests the SS server 10 to provide the list of restoring pages by using the information of the SS server 10, i.e., the URL of the SS server 10. That is, the web browser module 43 transmits a restoring page request message illustrated in FIG. 14 to the SS server 10. [58] Also, the web browser module 43 obtains the list of restoring pages from a response to the request. That is, the web browser module 43 receives from the SS server 10 a restoring page response message, illustrated in FIG. 15, in response to the restoring page request message, and obtains from the restoring page response message the URLs of web pages corresponding to the list of restoring pages (RUIs), the state information of the RUI server 7, and the URL which is location information of a site that stores the state information of the RUI client 4. Also, the web browser module 43 displays the list of restoring pages to the user, and receives a selection from the user who views the displayed list of restoring pages. That is, the web browser module 43 is given the URL of a web page that the user desires to restore. [59] Also, the web browser module 43 requests the RUI server 7 to 16 restore the web page selected by the user. That is, the web browser module 43 requests the RUI server 7 to start execution of an RUI application by providing the RUT server 7 with a restoring request message, illustrated in FIG. 16, which contains the state information of the RUI server 7 and the URL which is the location information of the site storing the state information of the RUI client 4. [60] Also, the web browser module 43 transmits the restoring request message illustrated in FIG. 16 to the RUI server 7, and receives as a response to the restoring request message a savable page, represented by the syntax shown in FIG. 17, which contains a Java script allowing the state information of the RUI client 4 to be received using the URL which is the location information of the site storing the state information of the RUI client 4. [61] Also, the web browser module 43 executes the Java script in the savable page represented by the syntax shown in FIG. 17 in order to obtain from the SS server 10 the state information of the RUI client 4, which is needed to recover the selected web page by using the URL which is the location information of the site storing the state information of the RUI client 4. Also, the web browser module 43 executes the Java script in the savable page to reflect the state information of the RUI client 4 into the savable page, thereby restoring the state of the RUI client 4 in the web page. [62] FIG. 7 is a block diagram of the RUI server 7 of FIG. 4 according to an exemplary embodiment of the present invention. Referring to 17 FIG. 7, the RUI server 7 includes an RUI CP module 71, an RUI CD module 72, a web server module 73, an RUI application module 74, a state manager 75, and an SS server selector 76. In particular, the RUI CP module 71 and the RUI CD module 72 are optional modules needed when the RUI server 7 is located in an autonomous network, such as a home network to which UPnP is applicable. Also, the RUI CP module 71 may be located outside the RUI server 7, instead of inside thereof. [63] The RUI CP module 71 acts as a UPnP CP that discovers and controls UPnP CDs. In particular, according to an exemplary embodiment of the present embodiment, when the RUI client 4 does not include the RUI CP module 41, the RUI CP module 71 obtains information of the SS server 10 during discovery of the SS server 10 according to UPnP and provides it to the SS server selector 76. [64] The RUI CD module 72 advertises that it is a UPnP CD, and acts as a UPnP CD controlled by a UPnP CP that discovers the RUI CD module 72 according to the advertisement. [65] The web server module 73 acts as a HTTP-based general web server. That is, the web server module 73 is a HTTP server module that receives a request for an application from the RUI client 4, processes the application, and provides the result of processing, in response to the request. In particular, when receiving a request for a general web page from the RUI client 4, the web server module 73 creates and provides a web page in response to the request. 18 [66] The state manager 75, which manages the state information of the RUI server 7, is an optional module needed only when the state information of the RUI server 7 is generated when a user of the RUI client 4 uses a web page corresponding to an RUI provided by the RUI server 7. More specifically, when receiving from the RUI client 4 a request for the state information of the RUI server 7, generated when the user of the RUI client 4 uses a web page provided from the RUI server 7, the state manager 75 provides the state information of the RUI server 7 to the RUI client 4. That is, upon receiving the GETSTATES request message illustrated in FIG. 11 via the web server module 73, the state manager 75 transmits a GETSTATES response message illustrated in FIG. 12 in response to the GETSTATES request message. [67] Also, when receiving the state information of the RUI server 7 from the RUI client 4, the state manager 75 restores the state of the RUI server 7 based on the received information. That is, when receiving "ServerStatesString" in a restoring request message illustrated in FIG. 16 from the RUI client 4, the state manager 75 restores the state of the RUI server 7 based on the "ServerStatesString". [68] The RUI application module 74 performs an application for a web page corresponding to an RUI remote user interface. More specifically, when receiving a request for a web page from the RUI client 4 via the web server module 73, the RUI application module 74 creates a savable page providing a unit, e.g., a "SAVE" button, via which the user can instruct that 19 the state information of the web page be saved, and provides the savable page to the RUI client 4. [69] Also, when receiving from the RUI client 4 a request to restore a web page selected by the user, the RUI application module 74 creates a savable page containing a Java script allowing the RUI client 4 to acquire the state information of the RUI client 4, by using the URL which is the location information of the site storing the state information of the RUI client 4, and provides the savable page to the RUI client 4. [70] The SS server selector 76 is an optional module needed only when the RUI CP module 71 is present. The SS server selector 76 creates a representation page displaying the information about the SS server 10 obtained by the RUI CP module 71 to a user, and provides the information to the RUI client 4. Also, as described above, when the user who recognizes the representation page selects the SS server 10, the SS server selector 76 provides a call window (not shown) with the information about the SS server 10 by using an opener object of the Java script. [71] FIGS. 8A and 8B illustrate syntax representing a savable page according to an exemplary embodiment of the present invention. Referring to FIGS. 8A and 8B, the savable page is a HyperText Markup Language (HTML) document. As illustrated in FIGS. 8A and 8B, the savable page provides a "SAVE" button to a user, and the Java script in the savable page, which is returned from the RUI server 7 through an on-click event callback for the "SAVE" button, i* executed to perform a GETSTATES command and a 20 information of the RUI server 7. [74] In particular, the web browser module 43 transmits a SAVE request message by using the HTTP object 432 and "save(url)" to request the SS server 10 to save the state information of the web page. That is, the web browser module 43 requests the SS server 10 to save the state information of the web page by opening a new socket, i.e., not the socket that is being used by a web page corresponding to an RUI and transmitting the SAVE request message via the new socket. [75] In particular, the web browser module 43 obtains the state information of the RUI client 4 from the SS server 10 by using HTTP object 432 and "checkSaveResuhO". That is, the web browser module 43 opens a new socket, i.e., not the socket that is being used by the web page corresponding to the RUI, requests the SS server 10 to provide the state information of the RUI client 4 via the new socket, and obtains the state information of the RUI client 4 in response to the request from the SS server 10 via the new socket. [76] If the RUI client 4 does not include the RUI CP module 41 and the SS handler 431, and the RUI server 7 includes the RUI CP module 71 and the SS server selector 76, the RUI server 7 provides a savable page represented by the syntax shown in FIGS. 9A and 9B, for example, which is different from the savable page represented by the syntax shown in FIGS. 8A and 8B. [77] FIGS. 9A and 9B illustrate syntax representing another 21 exemplary embodiment of the savable page represented by the syntax shown in FIGS. 8A and 8B according to the present invention. The savable page represented by the syntax shown in FIGS. 9A and 9B is in the form of a HTML document when the RUI server 7 includes the RUI CP module 71 and the SS server selector 76. When a "SAVE" button in the savable page is clicked, Java scripts "getserverstate()", "setserverstate()", and "startSelectingSSS()" in a savable page are sequentially executed, and "startSelectingSSS()" executes "window.open()". Thus, the SS server selector 76 provides a list of SS servers in the form of hyperlinks, and an on-click event handler for each of the hyperlinks corresponding to the SS servers is set to "opener.save(url)tt. As a result, a "save()" function is called to execute a "SAVE" command. [78] FIG. 10 is a block diagram of the SS server 10 according to an exemplary embodiment of the present invention. Referring to FIG. 10, the SS server 10 includes an RUI CD module 101, a web server module 102, a save handler 103, an RUT restoring unit 104, and a state storage unit 105. [79] The RUI CD module 101 advertises that it is a UPnP CD, and acts as a UPnP CD controlled by either the UPnP CP module 41 of the RUI client 4 or the UPnP CP module 71 of the RUI server 7, which discovers the RUI CD module 101 according to the advertisement. That is, the RUI CD module 101 may include information, such as 22 unit 105 capable of storing state information of a remote interface, i.e., a web page. [80] The web server module 102 acts as a HTTP-based general web server. That is, the web server module 102 is a HTTP server module that receives a request for an application from the RUI client 4, and processes the application and provides the processing result in response to the request. In particular, the web server module 102 receives and processes commands to save and restore the state information of a web page, which is received from the RUI client 4. [81] When receiving a SAVE request message illustrated in FIG. 13 via the web server module 102, the save handler 103 stores all state information of the web page, which is contained in the SAVE request message, i.e., the state of the RUI client 4 and the state information of the RUI server 7, in the state storage unit 105. [82] The RUI restoring unit 104 allows the RUI client 4 to select and restore state information of the web page desired by a user. More specifically, when receiving a request for a list of restoring pages from the RUI client 4, the RUI restoring unit 104 provides the URLs of restoring pages stored in the state storage unit 105 (web pages corresponding to RUIs), the state information of the RUI server 7, and the URL which is location information of a site storing the state information of a first RUI client 401, as illustrated in FIG. 18. That is, when receiving the restoring page request message illustrated in FIG. 14 from the RUI client 4 via the web server 23 module 102, the RUI restoring unit 104 transmits a restoring page response message illustrated in FIG. 15 in response to the message. Also, if the user selects one of the restoring pages, upon receiving a request for the selected restoring page, the RUI restoring unit 104 creates a savable page containing a Java script enabling the state information of the RUI client 4 to be obtained by using the URL which is the location information of the site storing the state information of the RUI client 4, and returns the savable page to a second RUI client 402 as illustrated in FIG. 18. That is, when receiving a restoring request page illustrated in FIG. 16 via the web server module 102, the UI restoring unit 104 transmits a savable page represented by the syntax shown in FIG. 17 to the RUI client 4 in response to the received page. [83] Also, when receiving a request for the state information of the RUI client 4, which is needed to restore the savable page provided to the RUI client 4, the RUI restoring unit 104 reads the state information of the RUI client 4 from the state storage unit 105 and provides it to the RUI client 4. [84] The state storage unit 105 stores all the state information of the web page which is received from the RUI client 4, e.g., the state information of the RUI client 4 and the state information of the RUI server 7, such as information regarding cookies generated when the user used RUIs, information regarding forms, AV object information. [85] FIG. 11 illustrates the format of a GETSTATES request message according to an exemplary embodiment of the present invention. The GETSTATES request message of FIG. 11 is a type of HTTP GET request 24 message. Referring to FIG. 11, in order to request the state information of the RUI server 7, the name "GETSTATES" that is the URL of the state information of the RUI server 7 is input in a GET request line. However, it would be apparent to those of ordinary skill in the art that a name other than "GETSTATES" may also be used. Also, a user agent header contains "Protocol/version(capability_string)" indicating that the RUI client 4 can support a HTTP-based remote user interface, and may contain ">hasControlPoint>ture;>/hasControlPoint>" indicating that the RUI client 4 includes the RUI CP module 41 although it is not shown in FIG. 11. In particular, ">hasControlPomt>ture>/hasControlPoint>" is a string allowing an XML fragment, such as " [86] FIG. 12 illustrates the format of a GETSTATES response message according to an exemplary embodiment of the present invention. The GETSTATES response message of FIG. 12 is a type of HTTP GET response message. Referring to FIG. 12, a content type field in the GETSTATES response message records the content type value of the state information of the RUI server 7. The content type value may be text/plain or application/x-www-url-encoded. Also, a field containing a string of server states in the GETSTATES response message records a state information value of the RUI server 7. Here, the state information value of the RUI server 7 must be determined in order to be interpreted by a Java script in a web page, which is provided by the RUI application module 74 of the RUIS server 7. 25 [87] FIG. 13 illustrates the format of a SAVE request message according to an exemplary embodiment of the present invention. The SAVE request message of FIG. 13 is a type of HTTP GET request message. Referring to FIG. 13, "/SAVE" of a "POST /SAVE? name_=NameForToBeSaved States" field is a command to save the state information of an RUI, which is generated by the RUI application module 74. [88] A "?_name_=NameForToBeSavedStates" of the "POST /SAVE?__name__=NameForToBeSavedStates" field indicates the name of a web page to be stored in the SS server 10 and must be set to have a unique value. For example, the unique name may be " |
|---|
09-mum-2007-correspondence-others.pdf
09-mum-2007-correspondence-received.pdf
09-mum-2007-description (complete).pdf
9-MUM-2007-ABSTRACT(19-10-2010).pdf
9-mum-2007-abstract(2-1-2007).pdf
9-mum-2007-abstract(granted)-(22-12-2010).pdf
9-mum-2007-cancelled pages(13-12-2010).pdf
9-mum-2007-claims(2-1-2007).pdf
9-MUM-2007-CLAIMS(AMENDED)-(13-12-2010).pdf
9-MUM-2007-CLAIMS(AMENDED)-(19-10-2010).pdf
9-mum-2007-claims(granted)-(22-12-2010).pdf
9-mum-2007-correspondence(16-11-2010).pdf
9-MUM-2007-CORRESPONDENCE(22-11-2010).pdf
9-mum-2007-correspondence(ipo)-(23-12-2010).pdf
9-mum-2007-description(complete)-(2-1-2007).pdf
9-mum-2007-description(granted)-(22-12-2010).pdf
9-MUM-2007-DRAWING(19-10-2010).pdf
9-mum-2007-drawing(2-1-2007).pdf
9-mum-2007-drawing(granted)-(22-12-2010).pdf
9-MUM-2007-FORM 1(19-10-2010).pdf
9-mum-2007-form 1(2-1-2007).pdf
9-mum-2007-form 1(4-5-2007).pdf
9-mum-2007-form 18(2-1-2007).pdf
9-mum-2007-form 2(2-1-2007).pdf
9-mum-2007-form 2(granted)-(22-12-2010).pdf
9-MUM-2007-FORM 2(TITLE PAGE)-(19-10-2010).pdf
9-mum-2007-form 2(title page)-(2-1-2007).pdf
9-mum-2007-form 2(title page)-(granted)-(22-12-2010).pdf
9-MUM-2007-FORM 26(19-10-2010).pdf
9-MUM-2007-FORM 3(19-10-2010).pdf
9-mum-2007-form 3(2-1-2007).pdf
9-mum-2007-form 3(4-5-2007).pdf
9-MUM-2007-FORM 5(19-10-2010).pdf
9-mum-2007-form 5(2-1-2007).pdf
9-mum-2007-general power of attorney(2-1-2007).pdf
9-MUM-2007-OTHER DOCUMENT(19-10-2010).pdf
9-MUM-2007-REPLY TO EXAMINATION REPORT(19-10-2010).pdf
9-MUM-2007-REPLY TO HEARING(13-12-2010).pdf
| Patent Number | 244858 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Indian Patent Application Number | 9/MUM/2007 | ||||||||||||
| PG Journal Number | 52/2010 | ||||||||||||
| Publication Date | 24-Dec-2010 | ||||||||||||
| Grant Date | 22-Dec-2010 | ||||||||||||
| Date of Filing | 02-Jan-2007 | ||||||||||||
| Name of Patentee | SAMSUNG ELECTRONICS CO., LTD | ||||||||||||
| Applicant Address | 416,MAETAN-DONG, YEONGTONG-GU, SUWON-SI, GYEONGGI-DO, | ||||||||||||
Inventors:
|
|||||||||||||
| PCT International Classification Number | H04L29/10 | ||||||||||||
| PCT International Application Number | N/A | ||||||||||||
| PCT International Filing date | |||||||||||||
PCT Conventions:
|
|||||||||||||