Welcome to Daniel's Blogger in Google: IMS Service and Application (1): XDM

IMS Service Enabler and Applications (1) – Network Data Store (XML Document Management – XDM)

http://docs.google.com/View?id=ddh56dhg_265dznvdpcr

Contacts information distributed on multiple databases and terminals: XDM enabler allowing end-users to manage their contacts lists and user profile information from several applications

2). IMS Network Data Store (XDM) supports following functions and features:

- One Shared XDM is to provide common information through same single user profile for different contacts in a number of different applications (IM XDM, PTx XDM, PS XDM, RLS XDM, etc.)

- An IMS user can have several identities defined in user profile, as different applications can use different identifier that is easy for the integration of 3rd party applications.

- Is a presence-based communication for subscribers to store information such as contact lists, bookmarks, and preferences on the network

- Manage the user request and accesses to the XDM/XCAP database – like XML documents (service data and user profile)

- Store well-structured XML documents in the network where it can be located, accessed and manipulated (retrieved, created, changed, deleted, etc.) via XCAP operations (GET, PUT, DELETE)

- While the users publish information over IMS core, the XDM can not be reached directly for control and security reasons, but updated through requesting the Application Server.

- Introduce a new domain for both fixed and mobile services and applications. And always access up to date information from any clients (fixed or mobile)

- Manipulate of the data is performed via an XDM Client (XDMC)

- Authentication and Routing of XDM Client requesting will be supported for access control

- XDM Client via XCAP may need to connect to a proxy server (as a contact point) which can “aggregate to reach several XDMs” for different applications

- Receive an OMA Directory request or an XCAP Capabilities request, aggregate all the results into one single XML document after broadcast the request to all XDMs with user’s data

- Notify client while any changes subscribed in the stored data

- Support partial updates - only send the notification for the changed information, not the entire XML document.

- Synchronization support for multiple clients/devices manipulating the same document

- Store documents accessed and manipulated in a central repository (as an XCAP Database) via XCAP - XML Configuration Access Protocol, as defined by IETF, has been chosen as the common XML Document Management protocol

- XDM interfaces to IMS Core via SIP

- Levels of roles and permissions based on read/write actions during administration or operation will be required.

- Refer to OMA-AD-XDM-V1_0-20060612-A document, or 3GPP TS 23.511, 23.611

3). XDM Functional Entity:

1. The XDM Client (XDMC) is a client entity that provides access to the various XDMS features

2. The Aggregation Proxy is the single contact point for the XDMC implemented in a UE to access XML documents stored in any XDMS.

- Performs authentication of the XDMC;

- Routes individual XCAP requests to the correct XDMS or to the Cross-Network Proxy;

- Routes individual Search requests to the Search Proxy;

- Optionally performs compression/decompression;

- Support secure data transfer between the Aggregation Proxy and the XDMC, using TLS or other means.

3. The Subscription Proxy is the contact point for the XDMC to subscribe for notification of changes in XML documents stored in any XDMS.

- Performs back-end subscriptions as an RLS as described in [RFC4662], using procedures defined in [IETFXCAP_Diff_Event] for notification of changes in XML documents from a particular XDMS;

- Maps XCAP Resources to SIP addresses of appropriate XDMSs;

- Receives notifications from XDMS, and using RLMI as defined in [RFC4662] aggregates them prior to sending them to the XDMC;

- Sends aggregated notifications to the XDMC.

4. The Search Proxy is a server entity to forward & send search request / response

- Forwards search requests to the XDMS, and to the Cross-Network Proxy when needed;

- Receives responses from the XDMS, and from the Cross-Network Proxy when needed;

- Combines results from the XDMS, and also from the Cross-Network Proxy before sending responses to the XDMC;

- Sends search responses to the XDMC.

5. The Cross-Network Proxy is the single contact point for the XDM enablers located in different networks to communicate over trusted connection.

- Performs authorization of the trusted network;

- Routes individual outgoing XCAP requests to the Cross-Network Proxy of the remote network;

- Routes individual outgoing search requests to the Cross-Network Proxy of the remote network;

- Routes individual incoming XCAP responses to the Aggregation Proxy;

- Routes individual incoming search responses to the Search proxy;

- Optionally performs compression/decompression;

- Support secure data transfer between Cross-Network Proxies using TLS or other means.

6. The Shared List XDMS is a server entity that supports:

- Manages and supports content of URI List and Group Usage List XML documents