Group Management (IMS)

 

   还是以《IMS IP Multimedia Concepts and Services》里的内容为主。结合自己的工作中所接触到的东西进行补充，解释说明。

   Group managerment (also known as 'data manipulation') is a service that allows users to store service-specific data in the service provider network.These data can be created,modified and deleted at will by the user. Data could be anything that a user needs to complete a service.

   Various services-such as presence,POC,IM,Multimedia Telephony etc.-need support for access to and manipulation of certain data that are needed by these servuces

 Some example of such data include:

1. Resouce List: a list of users who are potential notifiers,so that this list can be used to collectively subscriber to the status of each resource in that list. An example of such a list is the presence list.

2. Access Policy: a document that contains rules for handling communication attempts to specific user or to specific resource. An example of access policy is barring list for IM communication or setting POC auto-answer mode for particular users.

3.Configuration data for IMS Supplementary services: a document that contains values for each active supplementary serviuce. An example of such is call forwarding to a specific number when the user is not reachable.

对于IMS 中的Presence，POC 或者IM, 都涉及到buddy list，或者buddy list中还有群组（类似QQ群） 这样的管理。 一个用户buddy list，需要有各个buddy 的具体信息，群名字。

另外对于临时建立的 Add-hoc （临时组） 或者Conference(messaging or meeting)来讲，都需要对一个Group的数据进行建立，管理，和删除等操作。

用户针对每个具体的buddy 可能有不同的操作权限已经不同的业务。例如有些buddy 可以给用户打电话，有些只能给用户发短信。同样的，对于buddy中的群组，也会有相应的业务策略管理。 那针对这些不同的需求，需要有不同的服务器来存储这些用户自定义的数据。

这部分的数据在 之前的 Presence 里也谈到点，都是存储在XDMS 服务器中。

 Data are stored in the network where they can be located, accessed and manipulated(created,channged,deleted) by authorized users. This enables data to be shared and accessed by several devices and services that need them.

 Open Mobile Alliance(OMA) has adopted the term XML Document Management (XDM) to be synonymous withe the term 'group managerment'. The XDM service specifies documents that can be shared by multiple services.

  The XML Configuration Access Protocol (XCAP), has been selected by OMA and Third Generation Partnership Project as the protocol for transporting accessing,reading and manipulationg the XML documents that contain the data.

  Applications, like presence and IM,need to define an XCAP application usage (AUID),which define the way tahat a unique application can make use of XCAP. It defines the XML document for the application. ( AUID : org.openmobilealliance.pre-rule,  AUID: rls-services)

  There are four opertaions inherited from HTTP namely creat( HTTP PUT), fetch( HTTP GET),Modify (HTTP PUT) and Delete ( HTTP DELETE).

XCAP 沿用了HTTP 的4个操作，来完成对document 的创建，获取，修改和删除的功能。 并且通过AUID 来告知 XDMS Server 当前的操作的document是针对那一部分的service。

例如： PUT /resouce-lists/users/sip:alice@example.com.friends HTTP/1.1

这边 PUT 之后的 resouce-list 就是AUID, 但是它并不指示在Server上这段document 存储的具体路径。 由Server 自己来存储。 用户可以通过HTTP GET + AUID 来获取document的具体路径，然后进行下载。。

XCAP 的 HTTP GET 只是用来获得document 在Server 上的具体路径，还是要通过后续动作来获取真正的用户的document。（好像是？ 明天重新确认下）

             OMA 定义了四种类型的XDMS：

IM XDMS:  a server that store conversation history metadata and deferred messageing metadata ( 存储了history 的短信信息或者聊天信息， deferred  messageing, 如果对方目前离线，那么发过去的短信会暂时存储起来，等到对方上线或者 超时之后删除）;

Poc XMD: a server that stores PoC group propertities and information about Poc user access policies.

Presence XDMS : a server that contains rules for presence information subscribptions adn ruls for oresence information publication.

RLS XDMS: a server that contains user's presence buddylist. 

对于 Presence 来讲。 Presence XDMS 和RLS XDMS 是需要用到的。相比而言， Presence XDMS 存储了更多信息，除了Presentity的信息还是相关的policy u也在Presence XDMS 上。