1、 ETSI ES 202 391-13 V1.3.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 13: Address List Management(Parlay X 2)floppy3 ETSI ETSI ES 202 391-13 V1.3.1 (2008-05) 2 Reference RES/TISPAN-01056-13-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Ant
2、ipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The pres
3、ent document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers
4、 of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/st
5、atus/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restrict
6、ion extend to reproduction in all media. European Telecommunications Standards Institute 2008. The Parlay Group 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mar
7、k of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 391-13 V1.3.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 2.1 Normative references .6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbrev
8、iations .7 4 Detailed service description .7 4.1 Group URI format 7 4.2 Address list usage in services .8 5 Namespaces8 6 Sequence diagrams.9 6.1 Manage groups (Create, delete, query, set access and query access) .9 6.2 Manage group members (AddMember, AddMembers, DeleteMember, DeleteMembers, QueryM
9、embers) .10 7 XML Schema data type definition .10 7.1 AccessPermissions structure 10 7.2 AttributeStatus enumeration.10 7.3 SimpleAttribute structure .11 8 Web Service interface definition11 8.1 Interface: GroupManagement.11 8.1.1 Operation: createGroup.11 8.1.1.1 Input message: createGroupRequest .
10、11 8.1.1.2 Output message: createGroupResponse 12 8.1.1.3 Referenced faults.12 8.1.2 Operation: deleteGroup.12 8.1.2.1 Input message: deleteGroupRequest .12 8.1.2.2 Output message: deleteGroupResponse 12 8.1.2.3 Referenced faults.12 8.1.3 Operation: queryGroups .12 8.1.3.1 Input message: queryGroups
11、Request 13 8.1.3.2 Output message: queryGroupsResponse .13 8.1.3.3 Referenced faults.13 8.1.4 Operation: setAccess.13 8.1.4.1 Input message: setAccessRequest .14 8.1.4.2 Output message: setAccessResponse 14 8.1.4.3 Referenced faults.14 8.1.5 Operation: queryAccess14 8.1.5.1 Input message: queryAcces
12、sRequest.14 8.1.5.2 Output message: queryAccessResponse .14 8.1.5.3 Referenced faults.14 8.2 Interface: Group .15 8.2.1 Operation: addMember .15 8.2.1.1 Input message: addMemberRequest15 8.2.1.2 Output message: addMemberResponse.15 8.2.1.3 Referenced faults.15 8.2.2 Operation: addMembers .15 8.2.2.1
13、 Input message: addMembersRequest 15 8.2.2.2 Output message: addMembersResponse .15 8.2.2.3 Referenced faults.16 8.2.3 Operation: deleteMember .16 8.2.3.1 Input message: deleteMemberRequest16 ETSI ETSI ES 202 391-13 V1.3.1 (2008-05) 4 8.2.3.2 Output message: deleteMemberResponse.16 8.2.3.3 Reference
14、d faults.16 8.2.4 Operation: deleteMembers16 8.2.4.1 Input message: deleteMembersRequest 16 8.2.4.2 Output message: deleteMembersResponse .17 8.2.4.3 Referenced faults.17 8.2.5 Operation: queryMembers 17 8.2.5.1 Input message: queryMembersRequest.17 8.2.5.2 Output message: queryMembersResponse17 8.2
15、.5.3 Referenced faults.17 8.2.6 Operation: addGroupAttribute 18 8.2.6.1 Input message: addGroupAttributeRequest.18 8.2.6.2 Output message: addGroupAttributeResponse18 8.2.6.3 Referenced faults.18 8.2.7 Operation: deleteGroupAttribute 18 8.2.7.1 Input message: deleteGroupAttributeRequest.18 8.2.7.2 O
16、utput message: deleteGroupAttributeResponse18 8.2.7.3 Referenced faults.18 8.2.8 Operation: queryGroupAttributes .19 8.2.8.1 Input message: queryGroupAttributesRequest19 8.2.8.2 Output message: queryGroupAttributesResponse.19 8.2.8.3 Referenced faults.19 8.2.9 Operation: addGroupMemberAttribute.19 8
17、.2.9.1 Input message: addGroupMemberAttributeRequest .19 8.2.9.2 Output message: addGroupMemberAttributeResponse 19 8.2.9.3 Referenced faults.19 8.2.10 Operation: deleteGroupMemberAttribute.20 8.2.10.1 Input message: deleteGroupMemberAttributeRequest .20 8.2.10.2 Output message: deleteGroupMemberAtt
18、ributeResponse 20 8.2.10.3 Referenced faults.20 8.2.11 Operation: queryGroupMemberAttributes20 8.2.11.1 Input message: queryGroupMemberAttributesRequest 20 8.2.11.2 Output message: queryGroupMemberAttributesResponse .20 8.2.11.3 Referenced faults.20 8.3 Interface: Member 21 8.3.1 Operation: addMembe
19、rAttribute.21 8.3.1.1 Input message: addMemberAttributeRequest .21 8.3.1.2 Output message: addMemberAttributeResponse 21 8.3.1.3 Referenced faults.21 8.3.2 Operation: queryMemberAttributes21 8.3.2.1 Input message: queryMemberAttributesRequest 21 8.3.2.2 Output message: queryMemberAttributesResponse
20、.21 8.3.2.3 Referenced faults.22 8.3.3 Operation: deleteMemberAttribute.22 8.3.3.1 Input message: deleteMemberAttributeRequest22 8.3.3.2 Output message: deleteMemberAttributeResponse 22 8.3.3.3 Referenced faults.22 9 Fault definitions22 9.1 PolicyException .22 9.1.1 POL0210: Too many members in grou
21、p.22 9.1.2 POL0211: Subgroups not supported.23 9.1.3 POL0212: Group name too long.23 9.1.4 POL0213: Group already exists23 10 Service policies 23 Annex A (normative): WSDL for Address List Management24 Annex B (informative): Bibliography.25 History 26 ETSI ETSI ES 202 391-13 V1.3.1 (2008-05) 5 Intel
22、lectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Righ
23、ts (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IP
24、R searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced b
25、y ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 13 of a multi-part deliverable covering Open Service Access (OSA); Parlay X Web Services, as identified below: Part 1: “Common“; Part 2: “Third P
26、arty Call“; Part 3: “Call Notification“; Part 4: “Short Messaging“; Part 5: “Multimedia Messaging“; Part 6: “Payment“; Part 7: “Account Management“; Part 8: “Terminal Status“; Part 9: “Terminal Location“; Part 10: “Call Handling“; Part 11: “Audio Call“; Part 12: “Multimedia Conference“; Part 13: “Ad
27、dress List Management“; Part 14: “Presence“. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. The present document forms part of the Parlay X 2.2 set of specifications. The present document is equivalent to 3GPP TS 29.199-13 V6.5.0 (Re
28、lease 6). ETSI ETSI ES 202 391-13 V1.3.1 (2008-05) 6 1 Scope The present document is part 13 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to make use of network functionality thro
29、ugh an open standardized interface, i.e. the OSA APIs. The present document specifies the Address List Management Web Service. The following are defined here: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service Polic
30、ies. WSDL Description of the interfaces. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete documen
31、t or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the ex
32、pected location might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
33、 reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks incl
34、uded in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific
35、references, the latest edition of the referenced document (including any amendments) applies. 1 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 391-13 V1.3.1 (2008-05) 7 2 ETSI ES 202 391-1: “Ope
36、n Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 2)“. 3 IETF RFC 2396: “Uniform Resource Identifiers (URI): Generic Syntax“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202 391-1 2 and the foll
37、owing apply: application managed group: group created and managed outside of the network, requiring the group members to be passed into the network for processing group: container for a set of addresses, it is not an address itself. When a group contain one or more groups, logically the group contai
38、ns the set of addresses it holds, plus the set of addresses that any contained group holds (including any addresses contained in groups that a contained group holds) group resolution: when a group is processed by a service, it expands the group (and any nested groups) into a set of addresses. The re
39、sulting set of addresses contains no groups, and any duplicate addresses are removed. Thus, a resolved group may be considered an exclusive union of all of its contained members network managed group: group created and managed within a network, allowing Web Services to reference the members of a gro
40、up using the group name 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ES 202 391-1 2 apply. 4 Detailed service description The present document defines two related interfaces, one to manage the groups themselves - creation, deletion, query and access right ma
41、nagement. The second interface manages the members within a group, supporting add, delete and query operations. Addresses are not created using this service, they must already exist. 4.1 Group URI format A group URI is consistent with the style defined in RFC 2396 3, supporting the following URI sty
42、le which is used in schemes such as sip and mailto: scheme: The group URI consists of the following discrete elements: Scheme: selected by the provider of the group URI. Group name: following the conventions of RFC 2396 3. Suffix: may be added by Service Provider (if allowed by creation operation) t
43、o create a unique name when the Prefix + Group name already exists. Sub-domain: defined by the requester, this is contained within the domain provided by the service provider. Domain: defined by the Service Provider, and cannot be specified by the application. ETSI ETSI ES 202 391-13 V1.3.1 (2008-05
44、) 8 This definition of a group URI enables flexibility on the part of the Service Provider and the Requester, while ensuring unique groups are created and providing transparency of implementation of group storage. The following are some group URI examples. sip: sip: mailto: group: These examples sho
45、w (1)(2) use of prefix to create unique names, (1)(3) use of different defined schemes, and (4) use of a service provider defined scheme. 4.2 Address list usage in services When a service has a requirement to support groups of address lists, it may satisfy this requirement by utilizing network manag
46、ed groups. The group URI is passed to the service, and this group URI is resolved to the set of URIs contained within the group. If one or more group URIs are provided in a set of URIs to a service, the service will replace each group URI with its set of contained URIs, and the service processing wi
47、ll apply to the unique union of URIs generated. If supported by the service policy, zero or more of the set of URIs contained within a group may be themselves group URIs, which would also be resolved. Thus, in this case, the list of URIs that the service would process would be the union of individua
48、l URIs (as a set with no duplicates). Unless specifically defined in the semantics of a service, the expected semantic for the results of a service operation will be presented as the results for the set of URIs as processed (the union of non-group and group provided URIs), without group URIs include
49、d in the result. This eliminates a variety of complexity issues including duplicate URIs in multiple groups and the differences between a group URI and a URI referring to an endpoint. 5 Namespaces The GroupManagement interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/group_mgmt/v2_2 The Group interface uses the namespace: http:/www.csap
