System and method for managing XDM service information

• US 8,543,719 B2
• Filed: 08/01/2006
• Issued: 09/24/2013
• Est. Priority Date: 08/19/2005
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Oh, Jae-Kwon, Kim, Wuk, Sung, Sang-Kyung
• Primary Examiner(s): CHANNAVAJJALA, SRIRAMA T
• Application Number:
  US11/497,213
• Publication Number:
  US 20070043692A1
• Time in Patent Office: 2,611 Days
• Field of Search: 707 1- 2, 707/10, 707/100, 707/102, 707103 X-103 Z, 707/200, 707/601, 707/802, 707/811, 707/807, 715/234, 715/760, 715/239, 717/116, 717/152, 717/171, 717/176, 455517-519, 455/413, 455/556.2
• US Class Current: 709/230
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 17/00 Digital computing or data processing equipment or methods, specially adapted for specific functions information retrieval, database structures or file system structures therefor G06F16/00
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs
• CPC Class Codes: H04H 20/71 Wireless systems
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor

Abstract

Disclosed is a system and method for managing XDM (XML Document Management) service information to improve management efficiency for OMA (Open Mobile Alliance) service information. The apparatus includes a controller for creating a shared User Resource Identifier (URI), and using a value created by the controller as a static value to be used as a newly-created reference handle for shared service information referred to by service information. The newly-created value is set as an unchanged value (i.e., it remains static until a corresponding element vanishes), thereby preventing signaling overhead, compatibility degradation, and resource waste due to modification of the shared service information.

Claims

1. An apparatus for managing XML Document Management (XDM) service information in an XDM client included in a user terminal of an Open Mobile Alliance (OMA) system, the apparatus comprising:

a controller for creating a shared User Resource Identifier (URI) list including a static reference handle value for indicating the shared URI list, in response to a request to create the shared URI list, transmitting the shared URI list to a shared XDM Server (XDMS) for storage as a reference for service information corresponding to a plurality of OMA services in accordance with the static reference handle value, changing at least one piece of the service information, and maintaining, at the shared XDMS, the static reference handle value for the shared URI list after the at least one piece of the service information is changed;

a receiving device for receiving the request to create the shared URI list and receiving an error message, if the XDM client proposes a creation of the shared URI list without the static reference handle value from an XDMS; and

a transmitting device for transmitting the shared URI list to the shared XDMS,

wherein the service information is at least one of RLS (Resource List Server) service information, PoC (Push-to-Talk over Cellular) service information, and XDM service information, and

wherein the XDM client creates the PoC service information, used to provide a PoC group service, referring to the shared URI list by using the static reference handle value of the shared URI list, and transmits the PoC service information to a PoC XDMS.

2. The apparatus of claim 1, wherein the static reference handle value is a random value.

3. The apparatus of claim 1, wherein the shared URI list is created using an XML Configuration Access Protocol (XCAP).

4. The apparatus of claim 1, wherein the controller creates the service information using the static reference handle value;

and

wherein the transmitting device transmits the service information to each XDM server for corresponding service.

5. The apparatus of claim 1, wherein the static reference handle value is a name attribute of the shared URI list.

6. A system for managing XDM (XML Document Management) service information in an OMA (Open Mobile Alliance) system, the system comprising:

a shared XDMS (XML Document Management Server) for storing a shared URI (Uniform Resource Identifier) list as a reference for service information corresponding to a plurality of OMA services, storing changes made to at least one piece of the service information, and maintaining the static reference handle value for the shared URI list after the at least one piece of the service information is changed;

an XDM client included in a user terminal for receiving a request to create the shared URI list, receiving an error message when the XDM client proposes a creation of the shared URI list without a static reference handle value from an XDMS, creating the shared URI list including the static reference handle value for identifying the shared URI list, transmitting the shared URI list to the shared XDMS, creating service information referring to the shared URI list using the reference handle value, transmitting the service information to a corresponding XDMS that stores such service information, and changing the at least one piece of the service information, wherein the service information is at least one of RLS (Resource List Server) service information, PoC (Push-to-Talk over Cellular) service information, and XDM service information; and

a PoC XDMS for storing the PoC service information used to provide a PoC group service,

wherein the XDM client creates the PoC service information referring to the shared URI list by using the static reference handle value of the shared URI list, and transmits the PoC service information to the PoC XDMS.

7. The system of claim 6, further comprising:

an RLS (Resource List Server) XDMS for storing RLS service information,

wherein the XDM client creates the RLS service information referring to the shared URI list by using the static reference handle value of the shared URI list, and transmits the RLS service information to the RLS XDMS.

8. The system of claim 6, wherein the XDM client transmits a changed content of the shared URI list to the shared XDMS upon receipt of a request to change the shared URI list.

9. The system of claim 6, wherein the static reference handle value is randomly created.

10. A method for managing XDM (XML Document Management) service information in an XDM client included in a user terminal of an Open Mobile Alliance (OMA) system, the method comprising:

receiving a request, at the XDM client, to create a shared URI (Uniform Reference Identifier) list to be stored in a shared XDM Server (XDMS);

receiving an error message, if the XDM client proposes a creation of the shared URI list without a static reference handle value from an XDMS;

creating, by the XDM client, the shared URI list including the static reference handle value for identifying the shared URI list, in response to the request;

transmitting the shared URI list from the XDM client to the shared XDMS for storage as a reference for service information corresponding to a plurality of OMA services in accordance with the static reference handle value;

changing at least one piece of the service information; and

maintaining, at the shared XDMS, the static reference handle value for the shared URI list after the at least one piece of the service information is changed,

wherein the service information is at least one of RLS (Resource List Server) service information, PoC (Push-to-Talk over Cellular) service information, and XDM service information, and

wherein the XDM client creates the PoC service information, used to provide a PoC group service, referring to the shared URI list by using the static reference handle value of the shared URI list, and transmits the PoC service information to a PoC XDMS.

11. The method of claim 10, wherein the static reference handle value is randomly created.

12. The method of claim 10, further comprising transmitting the created shared URI list to the shared XDM (XML Document Management) server.

13. The method of claim 10, further comprising creating the service information using the static reference handle value and transmitting the service information to each XDM server for corresponding service.

14. The method of claim 10, further comprising transmitting changed content of the shared URI list to a shared XDM server, upon receipt of a request to change the shared URI list.

15. The method of claim 10, wherein the static reference handle value is a name attribute of the shared URI list.

16. The method of claim 10, further comprising receiving an error message, if the XDM client proposes a creation of the shared URI list without the static reference handle value.

17. The method of claim 10, wherein the static reference handle value conforms to uniqueness constraints in an XML Configuration Access Protocol (XCAP).

18. The method of claim 10, wherein the static reference handle value is used as a reference handle of an external element and a resource-list element in the shared URI list.

19. A method for managing XDM (XML Document Management) service information in an XDM client included in a user terminal of an Open Mobile Alliance (OMA) system, the method comprising:

receiving, at the XDM client, a request to create a shared URI list to be stored in a shared XDM Server (XDMS);

receiving an error message, if the XDM client proposes a creation of the shared URI list without a list name from an XDMS;

creating, by the XDM client, the shared URI list including the list name;

statically fixing the list name of the shared URI list by the XDM client;

transmitting the shared URI list including the statically fixed list name from the XDM client to the shared XDMS for storage as a reference for service information corresponding to a plurality of OMA services in accordance with the statically fixed list name;

changing at least one piece of the service information; and

maintaining, at the shared XDMS, the statically fixed list name for the shared URI list after the at least one piece of the service information is changed,

wherein the service information is at least one of RLS (Resource List Server) service information, PoC (Push-to-Talk over Cellular) service information, and XDM service information, and

wherein the XDM client creates the PoC service information, used to provide a PoC group service, referring to the shared URI list by using the statically fixed list name of the shared URI list, and transmits the PoC service information to a PoC XDMS.

20. A method for managing XDM (XML Document Management) service information in an XDM client included in a user terminal of an Open Mobile Alliance (OMA) system, the method comprising:

receiving, by the XDM client, a request to create a shared URI list including an entry element to be stored in a shared XDM Server (XDMS);

receiving an error message, if the XDM client proposes a creation of the shared URI list without a unique identifier from an XDMS;

creating, by the XDM client, the shared URI list including the entry element having the unique identifier;

statically fixing the unique identifier of the entry element by the XDM client; and

transmitting the shared URI list including the statically fixed unique identifier of the entry element from the XDM client to the shared XDMS for storage as a reference for service information corresponding to a plurality of OMA services in accordance with the statically fixed unique identifier;

changing at least one piece of the service information; and

maintaining, at the shared XDMS, the statically fixed unique identifier for the shared URI list after the at least one piece of the service information is changed;

wherein the service information is at least one of RLS (Resource List Server) service information, PoC (Push-to-Talk over Cellular) service information, and XDM service information, and

wherein the XDM client creates the PoC service information, used to provide a PoC group service, referring to the shared URI list by using the statically fixed unique identifier of the shared URI list, and transmits the PoC service information to a PoC XDMS.