Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for updating a User Interface (UI) by a Remote UI (RUI) client in an RUI system providing a UI, comprising: receiving a UI page from an RUI server and rendering the received UI page; storing a UI state of the UI page upon detecting a change in capability of the RUI client, and requesting the RUI server to update the UI page according to the changed capability; receiving a UI page updated according to the changed capability, from the RUI server; reflecting the stored UI state in the updated UI page by: comparing a UI state of the received updated UI page with the stored UI state; and if there are attributes to be added or deleted as a result of the comparison, adding or deleting the attributes in the received updated UI page; and rendering the UI-state-reflected updated UI page, wherein the capability of the RUI client is not changed by a user input.
A remote UI client updates its display by first receiving and rendering a UI page from a server. When the client detects a change in its internal capabilities (excluding changes from user input), it saves the current state of the UI. The client then requests an updated UI page from the server, indicating its changed capabilities. Upon receiving the updated page, the client compares the new page's state with the previously stored state. If there are differences (attributes to add or remove), the client modifies the new page to reflect the old UI state, then renders the modified, updated UI.
2. The method of claim 1 , wherein requesting the RUI server comprises: transmitting the changed capability to the RUI server.
In the method for updating a UI as described above, the client informs the server about the change in its capabilities by sending the changed capability information directly to the server when requesting the UI update.
3. The method of claim 1 , wherein requesting the RUI server comprises: determining whether an update of the UI page is required according to the changed capability, and requesting the RUI server to update the UI page according to the changed capability if an update of the UI page is required.
In the method for updating a UI as described above, the client first determines if the change in its capabilities actually requires a UI update. It only requests the server to update the UI page if an update is deemed necessary based on the detected change. This prevents unnecessary server requests when the UI can remain the same.
4. The method of claim 1 , wherein changed capability comprises: state information of at least one of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a memory, a network and a battery of the RUI client.
In the method for updating a UI as described above, the detected change in capability that triggers the update process includes changes in the client's hardware or software state, specifically the state of the CPU, GPU, memory, network connection, or battery level. These changes affect the client's ability to render or interact with the UI, triggering a request for an updated UI from the server.
5. The method of claim 2 , wherein requesting the RUI server to update comprises: transmitting both of the changed capability and an old capability, to the RUI server.
In the method for updating a UI as described above, the client sends not only its changed capability to the server, but also information about its capabilities *before* the change occurred. This allows the server to understand the context of the change and provide a more appropriate UI update.
6. The method of claim 1 , wherein rendering comprises: parsing the updated UI page, re-requesting the RUI server to provide elements to be updated, and receiving the re-requested elements; and merging the elements received from the RUI server with the stored UI state, and rendering the merged UI page.
In the method for updating a UI as described above, rendering the updated UI page involves several steps. The client first parses the updated UI page. Then, it requests specific elements needing updates from the server. Once the server provides these updated elements, the client merges these elements with the stored UI state and renders the final, merged UI page.
7. A method for updating a User Interface (UI) by a Remote UI (RUI) server in an RUI system providing a UI, comprising: transmitting a UI page to an RUI client; receiving an update request for the transmitted UI page, where the update request includes a changed capability of the RUI client and where the update request was transmitted by the RUI client; determining whether there are items to be updated in the UI page according to the changed capability of the RUI client; if there are items to be updated, updating the UI page according to the changed capability of the RUI client, and transmitting the updated UI page to the RUI client wherein, upon receiving the updated UI page transmitted by the RUI server, the RUI client compares a UI state of the received updated UI page with a UI state stored by the RUI client when the change in capability was detected and, if there are attributes to be added or deleted as a result of the comparison, adds or deletes the attributes in the received updated UI page; and if there are no items to be updated, transmitting an error code to the RUI client, wherein the capability of the RUI client is not changed by a user input.
A remote UI server supports UI updates by first sending a UI page to a client. It then receives an update request from the client, which includes information about the client's changed capabilities (excluding changes from user input). The server checks if the UI page needs to be updated based on these changed capabilities. If updates are needed, the server updates the UI page and sends it back to the client. The client compares the new page's state with its stored state. If there are differences (attributes to add or remove), the client modifies the new page to reflect the old UI state. If no updates are needed, the server sends an error code to the client.
8. The method of claim 7 , wherein changed capability comprises state information of at least one of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a memory, a network and a battery of the RUI client.
In the method for updating a UI by the server as described above, the client's changed capability includes changes in the client's hardware or software state, specifically the state of the CPU, GPU, memory, network connection, or battery level. These changes affect the client's ability to render or interact with the UI, triggering the server to update and send the UI.
9. The method of claim 7 , further comprising: receiving an update request for elements of the UI page from the RUI client, updating the requested elements, and transmitting the updated elements to the RUI client, after updating the UI page and transmitting the updated UI page to the RUI client.
In the method for updating a UI by the server as described above, after the server updates the UI page based on the initial request and sends it to the client, the server may receive a subsequent update request specifically for certain elements within the UI page. In this case, the server updates those specific elements and sends only those updated elements back to the client.
10. A method for updating a User Interface (UI) by a Remote UI (RUI) client in an RUI system providing a UI, comprising: receiving a UI page from an RUI server and rendering the received UI page; upon detecting a change in capability of the RUI client, storing a UI state of the UI page and sending a request to update the UI page according to the changed capability, to the RUI server along with the UI state; receiving from the RUI server a UI-state-reflected updated UI page, wherein the RUI server had updated the UI page according to the changed capability and reflected the UI state in the request in the updated UI page by comparing a UI state of the updated UI page with the UI state in the request and, if there are attributes to be added or deleted as a result of the comparison, adding or deleting the attributes in the updated UI page; and rendering the received UI-state-reflected updated UI page, wherein the capability of the RUI client is not changed by a user input.
A remote UI client updates its display by receiving and rendering a UI page from a server. When the client detects a change in its internal capabilities (excluding changes from user input), it saves the current state of the UI and sends a request to the server for an updated UI page. This request includes both the changed capabilities and the saved UI state. The server updates the UI based on the changed capabilities and applies the provided UI state to the updated UI. The client then receives and renders this UI-state-reflected updated UI page.
11. The method of claim 10 , wherein requesting the RUI server comprises: transmitting the changed capability to the RUI server.
In the method for updating a UI as described above, the client informs the server about the change in its capabilities by sending the changed capability information directly to the server when requesting the UI update.
12. The method of claim 10 , wherein requesting the RUI server comprises: determining whether an update the UI page is required according to the changed capability, and requesting the RUI server to update the UI page according to the changed capability if an update of the UI page is required.
In the method for updating a UI as described above, the client first determines if the change in its capabilities actually requires a UI update. It only requests the server to update the UI page if an update is deemed necessary based on the detected change. This prevents unnecessary server requests when the UI can remain the same.
13. The method of claim 10 , wherein changed capability comprises: state information of at least one of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a memory, a network and a battery of the RUI client.
In the method for updating a UI as described above, the detected change in capability that triggers the update process includes changes in the client's hardware or software state, specifically the state of the CPU, GPU, memory, network connection, or battery level. These changes affect the client's ability to render or interact with the UI, triggering a request for an updated UI from the server.
14. The method of claim 11 , wherein requesting the RUI server comprises: transmitting both of the changed capability and a capability prior to a change thereof, to the RUI server.
In the method for updating a UI as described above, the client sends not only its changed capability to the server, but also information about its capabilities *before* the change occurred. This allows the server to understand the context of the change and provide a more appropriate UI update.
15. A method for updating a User Interface (UI) by a Remote UI (RUI) server in an RUI system providing a UI, comprising: transmitting a UI page to an RUI client; receiving, from the RUI client, an update request for the transmitted UI page, where the update request includes a changed capability of the RUI client and a UI state of the UI page when the RUI client detected the change in capability; determining whether there are items to be updated in the UI page according to the changed capability of the RUI client; if there are items to be updated, updating the UI page according to the changed capability of the RUI client, applying the UI state included in the update request to the updated UI page by comparing a UI state of the updated UI page with the UI state included in the request and, if there are attributes to be added or deleted as a result of the comparison, adding or deleting the attributes in the updated UI page, and transmitting the UI-state-applied updated UI page to the RUI client; and if there are no items to be updated, transmitting an error code to the RUI client, wherein the capability of the RUI client is not changed by a user input.
A remote UI server supports UI updates by first sending a UI page to a client. It then receives an update request from the client, which includes information about the client's changed capabilities (excluding changes from user input) and the UI state at the time of the capability change. The server checks if the UI page needs to be updated based on these changed capabilities. If updates are needed, the server updates the UI page and applies the UI state received in the request to the updated page. If no updates are needed, the server sends an error code to the client.
16. The method of claim 15 , wherein changed capability comprises state information of at least one of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a memory, a network and a battery of the RUI client.
In the method for updating a UI by the server as described above, the client's changed capability includes changes in the client's hardware or software state, specifically the state of the CPU, GPU, memory, network connection, or battery level. These changes affect the client's ability to render or interact with the UI, triggering the server to update and send the UI.
17. A Remote User Interface (RUI) client apparatus for updating a User Interface (UI) in an RUI system providing a UI, comprising: a web browser configured for receiving a UI page from an RUI server and rendering the received UI page; a capability change detector configured for detecting a change in capability of the RUI client; a UI state storage configured for storing a UI state of the UI page when as the change in capability is detected by the capability change detector; a UI request triggerer configured for requesting the RUI server to update the UI page according to the changed capability; and a UI state reflector configured for: receiving, from the RUI server, a UI page updated according to the changed capability; reflecting the UI state stored in the UI state storage in the updated UI page by comparing a UI state of the received updated UI page with the UI state stored in the UI state storage and, if there are attributes to be added or deleted as a result of the comparison, adding or deleting the attributes in the received updated UI page; and transmitting the UI-state-reflected UI page to the web browser, wherein the capability of the RUI client is not changed by a user input.
A remote UI client device updates a user interface by using a web browser to display content from a remote server. It monitors its own CPU, GPU, memory, network, and battery to detect capability changes (excluding user input). When such a change occurs, it saves the current state of the UI. It then sends a request to the server to update the UI, based on the changed capability. The client receives an updated UI from the server and merges the previously stored UI state into this updated UI to prevent loss of user-specific settings or data. The final result is then displayed in the browser.
18. The apparatus of claim 17 , wherein the UI request triggerer transmits the changed capability to the RUI server when requesting the RUI server to update the UI page.
The remote UI client device, when requesting the server to update the UI, sends specific information about the changed capability to the server. This allows the server to tailor the updated UI specifically to the client's new capabilities.
19. The apparatus of claim 17 , wherein the UI request triggerer determines whether an update the UI page is required according to the changed capability, and requests the RUI server to update the UI page according to the changed capability if an update of the UI page is required.
The remote UI client device first determines if an update to the UI is actually needed after a capability change is detected. The request to the server to update the UI is only sent if it is determined that the capability change affects the UI rendering or functionality.
20. The apparatus of claim 17 , wherein the capability change detector detects a change in state information of at least one of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a memory, a network and a battery of the RUI client.
The remote UI client device monitors the state of its Central Processing Unit (CPU), Graphic Processing Unit (GPU), memory, network connection, and battery to detect changes in its capabilities. Any change in the state of these components triggers the UI update process.
21. The apparatus of claim 18 , wherein the UI request triggerer transmits both of the changed capability and a capability prior to a change thereof, to the RUI server.
When the remote UI client device requests an update to the UI, it sends both the new changed capability and information about its capability before the change occurred. This gives the server more context to generate the most appropriate updated UI.
22. A Remote User Interface (RUI) server apparatus for updating a User Interface (UI) in an RUI system providing a UI, comprising: a web server configured for receiving an update request from a RUI client for a UI page previously transmitted to the RUI client, and sending a response to the update request to the RUI client, where the update request includes a changed capability of the RUI client and where the update request was transmitted by the RUI client after storing a UI state of the UI page upon detecting the change in capability of the RUI client; and a UI generator configured for determining whether there are items to be updated in the UI page according to the changed capability of the RUI client included in the update request, updating the UI page according to the changed capability of the RUI client and transmitting the updated UI page to a web browser if there are items to be updated, and transmitting an error code to the web server if there are no items to be updated, wherein, upon receiving the updated UI page transmitted by the RUI server, the RUI client compares a UI state of the received updated UI page with a UI state stored by the RUI client when the change in capability was detected and, if there are attributes to be added or deleted as a result of the comparison, adding or deleting the attributes in the received updated UI page wherein the capability of the RUI client is not changed by a user input.
A remote UI server provides UI updates to a client. It receives a request from the client to update a previously sent UI page based on the client's changed capabilities. When a client detects a change in its capabilities (excluding changes from user input), it saves the current state of the UI and requests the UI update. The server determines if there are UI elements needing updates based on the changed capabilities. If updates are required, the server generates an updated UI and sends it to the client. If no updates are needed, the server sends an error code. The client merges the new page's state with its stored state. If there are differences (attributes to add or remove), the client modifies the new page to reflect the old UI state.
23. The apparatus of claim 22 , wherein changed capability comprises state information of at least one of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a memory, a network and a battery of the RUI client.
In the remote UI server as described above, the client's changed capability includes changes in the client's hardware or software state, specifically the state of the CPU, GPU, memory, network connection, or battery level. These changes affect the client's ability to render or interact with the UI, triggering the server to update and send the UI.
24. A Remote User Interface (RUI) client apparatus for updating a User Interface (UI) in an RUI system providing a UI, comprising: a web browser configured for receiving a UI page from an RUI server and rendering the received UI page; a capability change detector configured for detecting a change in capability of the RUI client; a UI state storage configured for storing a UI state of the UI page when the change in capability is detected by the capability change detector; and a UI request triggerer configured for requesting the RUI server to update the UI page according to the changed capability by sending a request including the stored UI state and changed capability; wherein, upon receiving the request, the RUI server updates the UI page according to the changed capability in the request and reflects the UI state included in the request in the updated UI page by comparing a UI state of the updated UI page with the UI state included in the request and, if there are attributes to be added or deleted as a result of the comparison, adding or deleting the attributes in the updated UI page, wherein the web browser receives the UI-state-reflected updated UI page from the RUI server and renders the received UI-state-reflected updated UI page, wherein the capability of the RUI client is not changed by a user input.
A remote UI client device updates a user interface by using a web browser to display content from a remote server. It monitors its own CPU, GPU, memory, network, and battery to detect capability changes (excluding user input). When such a change occurs, it saves the current state of the UI. It then sends a request to the server to update the UI, based on the changed capability, and includes the saved UI state with the request. The server merges the received UI state into this updated UI to prevent loss of user-specific settings or data. The final result is then displayed in the browser.
25. The apparatus of claim 24 , wherein the UI request triggerer determines whether an update the UI page is required according to the changed capability, and requests the RUI server to update the UI page according to the changed capability if an update of the UI page is required.
The remote UI client device first determines if an update to the UI is actually needed after a capability change is detected. The request to the server to update the UI is only sent if it is determined that the capability change affects the UI rendering or functionality.
26. The apparatus of claim 24 , wherein the capability change detector detects a change in state information of at least one of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a memory, a network and a battery of the RUI client.
The remote UI client device monitors the state of its Central Processing Unit (CPU), Graphic Processing Unit (GPU), memory, network connection, and battery to detect changes in its capabilities. Any change in the state of these components triggers the UI update process.
27. The apparatus of claim 24 , wherein the UI request triggerer transmits both the changed capability and a capability prior to a change thereof, when requesting the RUI server to update the UI page.
When the remote UI client device requests an update to the UI, it sends both the new changed capability and information about its capability before the change occurred. This gives the server more context to generate the most appropriate updated UI.
28. A Remote User Interface (RUI) server apparatus for updating a User Interface (UI) in an RUI system providing a UI, comprising: a web server configured for receiving an update request from a RUI client for a UI page previously transmitted to the RUI client, and sending a response to the update request to the RUI client, where the update request includes a changed capability of the RUI client and a UI state of the UI page when the RUI client detected the changed capability; a UI generator configured for determining whether there are items to be updated in the UI page according to the changed capability of the RUI client included in the update request, updating the UI page according to the changed capability of the RUI client if there are items to be updated, and generating an error code and transmitting the error code to the web server if there are no items to be updated; and a UI state reflector configured for applying the UI state included in the update request to the updated UI page by comparing the UI state of the updated UI page with the UI state included in the update request and, if there are attributes to be added or deleted as a result of the comparison, adding or deleting the attributes in the updated UI page, and delivering the UI-state-applied UI page to the web server, wherein the capability of the RUI client is not changed by a user input.
A remote UI server provides UI updates to a client. It receives a request from the client to update a previously sent UI page, the request including the client’s changed capabilities (excluding changes from user input) and the UI state at the time of that change. The server determines if there are UI elements needing updates based on the changed capabilities. If updates are required, the server generates an updated UI. It then applies the UI state received in the request to the updated UI to prevent data loss. If no updates are needed, the server sends an error code.
29. The apparatus of claim 28 , wherein the changed capability comprises state information of at least one of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a memory, a network and a battery of the RUI client.
In the remote UI server as described above, the client's changed capability includes changes in the client's hardware or software state, specifically the state of the CPU, GPU, memory, network connection, or battery level. These changes affect the client's ability to render or interact with the UI, triggering the server to update and send the UI.
Unknown
July 29, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.