OMATSXDMGroupV110208D.docx

1、OMATSXDMGroupV110208DGroup XDM SpecificationDraft Version 1.1 08 Feb 2010Open Mobile AllianceOMA-TS-XDM_Group-V1_1-20100208-DUse of this document is subject to all of the terms and conditions of the Use Agreement located at http:/www.openmobilealliance.org/UseAgreement.html.Unless this document is c

2、learly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance specification, and is subject to revision or removal without notice.You may use this document or any part of the document for internal or educational purposes only, provided yo

3、u do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. Th

4、e Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorse

5、ment of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document.Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Es

6、sential IPR is related to the prepared or published specification. However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the “OMA IPR Declarations” list at ht

7、tp:/www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret

8、rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form.NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLI

9、ED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPRS REPRESENTED ON THE “OMA IPR DECLARATIONS” LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT SUCH RIGHTS ARE

10、 ESSENTIAL OR NON-ESSENTIAL.THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS. 2010 Open Mob

11、ile Alliance Ltd. All Rights Reserved.Used with the permission of the Open Mobile Alliance Ltd. under the terms set forth above.ContentsFigures1.ScopeThis specification describes the data format and Application Usage for the Group document, which is a common group definition that can be used by all

12、OMA enablers (e.g. PoC and IM). It also defines the data format for the Extended Group Advertisement and procedures for the Group XDMS to send Extended Group Advertisements.2.References2.1Normative ReferencesOMADict“Dictionary for OMA Specifications”, Version 2.4, Open Mobile Alliance, OMA-ORG-Dicti

13、onary-V2_4, URL: http:/www.openmobilealliance.org/PoC_CP“Push to talk Over Cellular (PoC) - Control Plane Specification”, Draft Version 2.0, Open Mobile Alliance, OMA-TS-PoC-ControlPlane-V2_0, URL: http:/www.openmobilealliance.org/PoC_CP-V1_0“OMA PoC Control Plane”, Version 1.0, Open Mobile Alliance

14、 , OMA-TS-PoC-ControlPlane-V1_0, URL: http:/www.openmobilealliance.org/PoC_XDM-V1_0“OMA PoC XDM Specification”, Version 1.0, Open Mobile Alliance , OMA-TS-PoC-XDM-V1_0, URL: http:/www.openmobilealliance.org/SCRRULES“SCR Rules and Procedures”, Version 1.0, Open Mobile Alliance , OMA-ORG-SCR_Rules_and

15、_Procedures-V1_0, URL: http:/www.openmobilealliance.org/XDM_Core“XML Document Management (XDM) Specification”, Version 2.0, Open Mobile Alliance , OMA-TS-XDM_Core-V2_0, URL: http:/www.openmobilealliance.org/XDM_List“Shared List XDM Specification”, Version 2.0, Open Mobile Alliance , OMA-TS-XDM_Share

16、d_List-V2_0, URL: http:/www.openmobilealliance.org/XSD_ext“XML Schema Definition: XDM Extensions”, Version 1.0, Open Mobile Alliance , OMA-SUP-XSD_xdm_extensions-V1_0, URL: http:/www.openmobilealliance.org/XSD_listServ“XML Schema Definition: PoC List Service”, Version 1.0, Open Mobile Alliance , OMA

17、-SUP-XSD_poc_listService-V1_0, URL: http:/www.openmobilealliance.org/XSD_poc_group_ad“XML Schema Definition: PoC Group Advertisement”, Version 1.0, Open Mobile Alliance , OMA-SUP-XSD_ poc_group_advertisement-V1_0, URL: http:/www.openmobilealliance.org/IETFRFC2119IETF RFC 2119 “Key words for use in R

18、FCs to Indicate Requirement Levels”, S. Bradner, March 1997, URL: http:/www.ietf.org/rfc/rfc2119.txtRFC3261IETF RFC 3261 “SIP: Session Initiation Protocol”, J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, E. Schooler, June 2002, URL: http:/www.ietf.org/rf

19、c/rfc3261.txtRFC3428IETF RFC 3428 “Session Initiation Protocol (SIP) Extension for Instant Messaging”, B. Campbell, Ed., J. Rosenberg, H. Schulzrinne, C. Huitema, D. Gurle, December 2002, URL: http:/www.ietf.org/rfc/rfc3428.txt RFC3966IETF RFC 3966 “The tel URI for Telephone Numbers”, H. Schulzrinne

20、, December 2004, URL: http:/www.ietf.org/rfc/rfc3966.txtRFC4745IETF RFC 4745 “Common Policy: A Document Format for Expressing Privacy Preferences”, H. Schulzrinne, J. Morris, H. Tschofenig, J. Cuellar, J. Polk, J. Rosenberg, February 2007, URL: http:/www.ietf.org/rfc/rfc4745.txtRFC4825IETF RFC 4825

21、“The Extensible Markup Language (XML) Configuration Access protocol (XCAP)”, J. Rosenberg, May 2007, URL: http:/www.ietf.org/rfc/rfc4825.txtRFC4826IETF RFC 4826 “The Extensible Markup Language (XML) Formats for Representing Resource Lists”, J. Rosenberg, May 2007, URL: http:/www.ietf.org/rfc/rfc4826

22、.txt3GPP/3GPP23GPP2-X.S0013-0043GPP2 X.S0013-004 “All-IP Core Network Multimedia Domain: IP Multimedia Call Control Protocol Based on SIP and SDP, Stage 3”, URL: http:/3gpp2.org/Public_html/specs/index.cfm3GPP-TS_24.2293GPP TS 24.229 “IP Multimedia Call Control Protocol based on Session Initiation P

23、rotocol (SIP) and Session Description Protocol (SDP); Stage 3”, URL: http:/www.3gpp.org/ftp/Specs/archive/24_series/24.229/2.2Informative ReferencesOMAIM_TS“SIP/SIMPLE Instant Messaging Specification Document”, Draft Version 1.0, Open Mobile Alliance , OMA-TS-IM_SIMPLE-V1_0, URL: http:/www.openmobil

24、ealliance.org/PoC_DocMgmt“OMA PoC Document Management”, Draft Version 2.0. Open Mobile Alliance , OMA-TS-PoC_Document_Management-V2_0, URL: http:/www.openmobilealliance.org/XDM_AD“XML Document Management Architecture”, Version 2.0. Open Mobile Alliance . OMA-AD-XDM-V2_0, URL: http:/www.openmobileall

25、iance.org/ 3.Terminology and Conventions3.1ConventionsThe key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC2119.All sections and appendixes, except “Scope” and “Intro

26、duction”, are normative, unless they are explicitly indicated to be informative.3.2DefinitionsAggregation ProxyUse definition from XDM_ADApplication ServerA functional entity that implements the service logic for SIP Sessions (e.g. PoC Server or IM Server).Application Unique IDA unique identifier wi

27、thin the namespace of Application Unique IDs created by this specification that differentiates XCAP Resources accessed by one application from XCAP Resources accessed by another application. (Source: RFC4825)Application UsageDetailed information on the interaction of an application with an XCAP Serv

28、er. (Source: RFC4825)Document SelectorA sequence of path segments, with each segment being separated by a “/”, that identify the XML document within an XCAP Root that is being selected. (Source: RFC4825)Document URIThe HTTP URI containing the XCAP Root and Document Selector, resulting in the selecti

29、on of a specific document. As a result, performing a GET against the Document URI would retrieve the document. (Source: RFC4825)Global DocumentA document placed under the Global Tree that applies to all users of that Application Usage.Global TreeA URI that represents the parent for all Global Docume

30、nts for a particular Application Usage within a particular XCAP Root. (Source: RFC4825)GroupA Group is a predefined set of Users together with its policies and attributes. A Group is identified by a SIP URI.Group IdentityThe SIP URI of the Pre-arranged Group or Join-in Group. Group MemberA User on t

31、he predefined list of Users associated with a Pre-arranged Group or Join-in Group.Group SessionA Group Session is a Pre-arranged Group, Ad-hoc Group or Join-in Group Session.Group Session Controlling FunctionThe Group Session Controlling Function is implemented in an Application Server and provides

32、centralized Group Session handling, which includes Group policy enforcement.Join-in GroupA persistent Group in which a User individually joins to have a Group Session with other joined Users, i.e., the establishment of a Group Session to a Join-in Group does not result in other Users being invited. A Join-in Grou