ETSI ES 202 504-13 V1.1.1 (2008-05)

Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
ETSI Standard


Open Service Access (OSA);
Parlay X Web Services;
Part 13: Address List Management
(Parlay X 3)



�

---------------------- Page: 1 ----------------------
2 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)



Reference
DES/TISPAN-01034-13-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis 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 enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present 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 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/status/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 restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI

---------------------- Page: 2 ----------------------
3 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
2.1 Normative references.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Detailed service description .8
4.1 Group URI format .8
4.2 Address list usage in services .9
5 Namespaces.9
6 Sequence diagrams.10
6.1 Manage groups (Create, delete, query, set access and query access) .10
6.2 Manage group members (AddMember, AddMembers, DeleteMember, DeleteMembers,
QueryMembers) .11
7 XML Schema data type definition .11
7.1 AccessPermissions structure.11
7.2 AttributeStatus enumeration.11
7.3 SimpleAttribute structure.12
8 Web Service interface definition.12
8.1 Interface: GroupManagement.12
8.1.1 Operation: createGroup.12
8.1.1.1 Input message: createGroupRequest.12
8.1.1.2 Output message: createGroupResponse.13
8.1.1.3 Referenced faults.13
8.1.2 Operation: deleteGroup.13
8.1.2.1 Input message: deleteGroupRequest.13
8.1.2.2 Output message: deleteGroupResponse.13
8.1.2.3 Referenced faults.13
8.1.3 Operation: queryGroups.13
8.1.3.1 Input message: queryGroupsRequest.14
8.1.3.2 Output message: queryGroupsResponse.14
8.1.3.3 Referenced faults.14
8.1.4 Operation: setAccess.14
8.1.4.1 Input message: setAccessRequest .15
8.1.4.2 Output message: setAccessResponse.15
8.1.4.3 Referenced faults.15
8.1.5 Operation: queryAccess.15
8.1.5.1 Input message: queryAccessRequest.15
8.1.5.2 Output message: queryAccessResponse.15
8.1.5.3 Referenced faults.15
8.2 Interface: Group.16
8.2.1 Operation: addMember.16
8.2.1.1 Input message: addMemberRequest.16
8.2.1.2 Output message: addMemberResponse.16
8.2.1.3 Referenced faults.16
8.2.2 Operation: addMembers.16
8.2.2.1 Input message: addMembersRequest.16
8.2.2.2 Output message: addMembersResponse.17
8.2.2.3 Referenced faults.17
8.2.3 Operation: deleteMember.17
ETSI

---------------------- Page: 3 ----------------------
4 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
8.2.3.1 Input message: deleteMemberRequest.17
8.2.3.2 Output message: deleteMemberResponse.17
8.2.3.3 Referenced faults.17
8.2.4 Operation: deleteMembers.17
8.2.4.1 Input message: deleteMembersRequest.18
8.2.4.2 Output message: deleteMembersResponse .18
8.2.4.3 Referenced faults.18
8.2.5 Operation: queryMembers.18
8.2.5.1 Input message: queryMembersRequest.18
8.2.5.2 Output message: queryMembersResponse.18
8.2.5.3 Referenced faults.19
8.2.6 Operation: addGroupAttribute.19
8.2.6.1 Input message: addGroupAttributeRequest.19
8.2.6.2 Output message: addGroupAttributeResponse.19
8.2.6.3 Referenced faults.19
8.2.7 Operation: deleteGroupAttribute.19
8.2.7.1 Input message: deleteGroupAttributeRequest.19
8.2.7.2 Output message: deleteGroupAttributeResponse.20
8.2.7.3 Referenced faults.20
8.2.8 Operation: queryGroupAttributes.20
8.2.8.1 Input message: queryGroupAttributesRequest.20
8.2.8.2 Output message: queryGroupAttributesResponse.20
8.2.8.3 Referenced faults.20
8.2.9 Operation: addGroupMemberAttribute.20
8.2.9.1 Input message: addGroupMemberAttributeRequest.20
8.2.9.2 Output message: addGroupMemberAttributeResponse .21
8.2.9.3 Referenced faults.21
8.2.10 Operation: deleteGroupMemberAttribute.21
8.2.10.1 Input message: deleteGroupMemberAttributeRequest.21
8.2.10.2 Output message: deleteGroupMemberAttributeResponse .21
8.2.10.3 Referenced faults.21
8.2.11 Operation: queryGroupMemberAttributes.21
8.2.11.1 Input message: queryGroupMemberAttributesRequest.21
8.2.11.2 Output message: queryGroupMemberAttributesResponse.22
8.2.11.3 Referenced faults.22
8.3 Interface: Member.22
8.3.1 Operation: addMemberAttribute.22
8.3.1.1 Input message: addMemberAttributeRequest.22
8.3.1.2 Output message: addMemberAttributeResponse.22
8.3.1.3 Referenced faults.22
8.3.2 Operation: queryMemberAttributes.23
8.3.2.1 Input message: queryMemberAttributesRequest.23
8.3.2.2 Output message: queryMemberAttributesResponse .23
8.3.2.3 Referenced faults.23
8.3.3 Operation: deleteMemberAttribute.23
8.3.3.1 Input message: deleteMemberAttributeRequest.23
8.3.3.2 Output message: deleteMemberAttributeResponse.23
8.3.3.3 Referenced faults.23
9 Fault definitions.24
9.1 PolicyException.24
9.1.1 POL0210: Too many members in group.24
9.1.2 POL0211: Subgroups not supported.24
9.1.3 POL0212: Group name too long.24
9.1.4 POL0213: Group already exists.24
10 Service policies .24
Annex A (normative): WSDL for Address List Management.25
Annex B (informative): Bibliography.26
History .27
ETSI

---------------------- Page: 4 ----------------------
5 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
Intellectual 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 Rights (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 IPR 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 by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN), and is now submitted for the ETSI standards
Membership Approval Procedure.
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 Party 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: "Address List Management";
Part 14: "Presence";
Part 15: "Message Broadcast";
Part 16: "Geocoding";
Part 17: "Application-driven Quality of Service (QoS)";
Part 18: "Device Capabilities and Configuration";
Part 19: "Multimedia Streaming Control";
Part 20: "Multimedia Multicast Session Management".
ETSI

---------------------- Page: 5 ----------------------
6 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
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 3.0 set of specifications.
The present document is equivalent to 3GPP TS 29.199-13 V7.0.2 (Release 7).
ETSI

---------------------- Page: 6 ----------------------
7 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
1 Scope
The present document is part 13 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through 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 Policies.
• 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 document 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 expected 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
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 included 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 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

---------------------- Page: 7 ----------------------
8 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
[2] ETSI ES 202 504-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 3)".
[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 504-1 [2] and the following 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 contains 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 resulting 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 group using the group name
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 504-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 management. 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 style which is used in
schemes such as sip and mailto:
scheme:dept1294@mydivision.mycompany.serviceprovider.com
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) to 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

---------------------- Page: 8 ----------------------
9 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
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:salesteam@sales.acme.anytelco.com
• sip:salesteam1@sales.acme.anytelco.com
• mailto:fieldservice@cityofaustin.anytelco.com
• group:mailroom@bldg001.acme.anytelco.com
These examples show (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
managed 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 will 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 individual 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 included 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/v3_0
The Group interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/group/v3_0
The GroupMember interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/group_member/v3_0
The data types are defined in the namespace:
http://www.csapi.org/schema/parlayx/group/v3_0
The "xsd" namespace is used in the present document to refer to the XML Schema data types defined in
XML Schema [1]. The use of the name "xsd" is not semantically significant.
ETSI

---------------------- Page: 9 ----------------------
10 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
6 Sequence diagrams
6.1 Manage groups (Create, delete, query, set access and
query access)
Pattern: Request / Response.
The group management functions are shown in this diagram, showing a sequence including the creation of a group,
setting access permissions to the group, querying those permissions, query of groups and finally deletion of a group.
: Application : Address List
Web Service
Create group
Verify or create name
Create group
Group URI
Set access
Query access
Access permissions
Query groups
Groups
Delete group

Figure 1
ETSI

---------------------- Page: 10 ----------------------
11 Final draft ETSI ES 202 504-13 V1.1.1 (2008-02)
6.2 Manage group members (AddMember, AddMembers,
DeleteMember, DeleteMembers, QueryMembers)
Pattern: Request / Response.
The group membership functions are shown in this diagram, showing the two add, two delete, and the query function.
: Application : Address List
Web Service
Add member
Query members
Members
Delete member

Figure 2
7 XML Schema data type definition
7.1 AccessPermissions structu
...

SLOVENSKI STANDARD
SIST ES 202 504-13 V1.1.1:2008
01-september-2008
Odprti dostop do storitve (OSA) - Spletne storitve Parlay X - 13. del: Upravljanje
seznama naslovov (Parlay X 3)
Open Service Access (OSA) - Parlay X Web Services - Part 13: Address List
Management (Parlay X 3)
Ta slovenski standard je istoveten z: ES 202 504-13 Version 1.1.1
ICS:
35.100.01 Medsebojno povezovanje Open systems
odprtih sistemov na splošno interconnection in general
SIST ES 202 504-13 V1.1.1:2008 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ES 202 504-13 V1.1.1:2008

---------------------- Page: 2 ----------------------

SIST ES 202 504-13 V1.1.1:2008

ETSI ES 202 504-13 V1.1.1 (2008-05)
ETSI Standard


Open Service Access (OSA);
Parlay X Web Services;
Part 13: Address List Management
(Parlay X 3)



�

---------------------- Page: 3 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 2 ETSI ES 202 504-13 V1.1.1 (2008-05)



Reference
DES/TISPAN-01034-13-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis 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 enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present 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 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/status/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 restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI

---------------------- Page: 4 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 3 ETSI ES 202 504-13 V1.1.1 (2008-05)
Contents
Foreword.6
1 Scope.7
2 References.7
2.1 Normative references.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Detailed service description .8
4.1 Group URI format .8
4.2 Address list usage in services .9
5 Namespaces.9
6 Sequence diagrams.10
6.1 Manage groups (Create, delete, query, set access and query access) .10
6.2 Manage group members (AddMember, AddMembers, DeleteMember, DeleteMembers,
QueryMembers) .11
7 XML Schema data type definition .11
7.1 AccessPermissions structure.11
7.2 AttributeStatus enumeration.11
7.3 SimpleAttribute structure.12
8 Web Service interface definition.12
8.1 Interface: GroupManagement.12
8.1.1 Operation: createGroup.12
8.1.1.1 Input message: createGroupRequest.12
8.1.1.2 Output message: createGroupResponse.13
8.1.1.3 Referenced faults.13
8.1.2 Operation: deleteGroup.13
8.1.2.1 Input message: deleteGroupRequest.13
8.1.2.2 Output message: deleteGroupResponse.13
8.1.2.3 Referenced faults.13
8.1.3 Operation: queryGroups.13
8.1.3.1 Input message: queryGroupsRequest.14
8.1.3.2 Output message: queryGroupsResponse.14
8.1.3.3 Referenced faults.14
8.1.4 Operation: setAccess.14
8.1.4.1 Input message: setAccessRequest .15
8.1.4.2 Output message: setAccessResponse.15
8.1.4.3 Referenced faults.15
8.1.5 Operation: queryAccess.15
8.1.5.1 Input message: queryAccessRequest.15
8.1.5.2 Output message: queryAccessResponse.15
8.1.5.3 Referenced faults.15
8.2 Interface: Group.16
8.2.1 Operation: addMember.16
8.2.1.1 Input message: addMemberRequest.16
8.2.1.2 Output message: addMemberResponse.16
8.2.1.3 Referenced faults.16
8.2.2 Operation: addMembers.16
8.2.2.1 Input message: addMembersRequest.16
8.2.2.2 Output message: addMembersResponse.17
8.2.2.3 Referenced faults.17
8.2.3 Operation: deleteMember.17
8.2.3.1 Input message: deleteMemberRequest.17
ETSI

---------------------- Page: 5 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 4 ETSI ES 202 504-13 V1.1.1 (2008-05)
8.2.3.2 Output message: deleteMemberResponse.17
8.2.3.3 Referenced faults.17
8.2.4 Operation: deleteMembers.17
8.2.4.1 Input message: deleteMembersRequest.18
8.2.4.2 Output message: deleteMembersResponse .18
8.2.4.3 Referenced faults.18
8.2.5 Operation: queryMembers.18
8.2.5.1 Input message: queryMembersRequest.18
8.2.5.2 Output message: queryMembersResponse.18
8.2.5.3 Referenced faults.19
8.2.6 Operation: addGroupAttribute.19
8.2.6.1 Input message: addGroupAttributeRequest.19
8.2.6.2 Output message: addGroupAttributeResponse.19
8.2.6.3 Referenced faults.19
8.2.7 Operation: deleteGroupAttribute.19
8.2.7.1 Input message: deleteGroupAttributeRequest.19
8.2.7.2 Output message: deleteGroupAttributeResponse.20
8.2.7.3 Referenced faults.20
8.2.8 Operation: queryGroupAttributes.20
8.2.8.1 Input message: queryGroupAttributesRequest.20
8.2.8.2 Output message: queryGroupAttributesResponse.20
8.2.8.3 Referenced faults.20
8.2.9 Operation: addGroupMemberAttribute.20
8.2.9.1 Input message: addGroupMemberAttributeRequest.20
8.2.9.2 Output message: addGroupMemberAttributeResponse .21
8.2.9.3 Referenced faults.21
8.2.10 Operation: deleteGroupMemberAttribute.21
8.2.10.1 Input message: deleteGroupMemberAttributeRequest.21
8.2.10.2 Output message: deleteGroupMemberAttributeResponse .21
8.2.10.3 Referenced faults.21
8.2.11 Operation: queryGroupMemberAttributes.21
8.2.11.1 Input message: queryGroupMemberAttributesRequest.21
8.2.11.2 Output message: queryGroupMemberAttributesResponse.22
8.2.11.3 Referenced faults.22
8.3 Interface: Member.22
8.3.1 Operation: addMemberAttribute.22
8.3.1.1 Input message: addMemberAttributeRequest.22
8.3.1.2 Output message: addMemberAttributeResponse.22
8.3.1.3 Referenced faults.22
8.3.2 Operation: queryMemberAttributes.23
8.3.2.1 Input message: queryMemberAttributesRequest.23
8.3.2.2 Output message: queryMemberAttributesResponse .23
8.3.2.3 Referenced faults.23
8.3.3 Operation: deleteMemberAttribute.23
8.3.3.1 Input message: deleteMemberAttributeRequest.23
8.3.3.2 Output message: deleteMemberAttributeResponse.23
8.3.3.3 Referenced faults.23
9 Fault definitions.24
9.1 PolicyException.24
9.1.1 POL0210: Too many members in group.24
9.1.2 POL0211: Subgroups not supported.24
9.1.3 POL0212: Group name too long.24
9.1.4 POL0213: Group already exists.24
10 Service policies .24
Annex A (normative): WSDL for Address List Management.25
Annex B (informative): Bibliography.26
History .27
ETSI

---------------------- Page: 6 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 5 ETSI ES 202 504-13 V1.1.1 (2008-05)
Intellectual 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 Rights (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 IPR 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 by 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 Party 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: "Address List Management";
Part 14: "Presence";
Part 15: "Message Broadcast";
Part 16: "Geocoding";
Part 17: "Application-driven Quality of Service (QoS)";
Part 18: "Device Capabilities and Configuration";
Part 19: "Multimedia Streaming Control";
Part 20: "Multimedia Multicast Session Management".
ETSI

---------------------- Page: 7 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 6 ETSI ES 202 504-13 V1.1.1 (2008-05)
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 3.0 set of specifications.
The present document is equivalent to 3GPP TS 29.199-13 V7.0.2 (Release 7).
ETSI

---------------------- Page: 8 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 7 ETSI ES 202 504-13 V1.1.1 (2008-05)
1 Scope
The present document is part 13 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through 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 Policies.
• 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 document 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 expected 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
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 included 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 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

---------------------- Page: 9 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 8 ETSI ES 202 504-13 V1.1.1 (2008-05)
[2] ETSI ES 202 504-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 3)".
[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 504-1 [2] and the following 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 contains 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 resulting 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 group using the group name
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 504-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 management. 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 style which is used in
schemes such as sip and mailto:
scheme:dept1294@mydivision.mycompany.serviceprovider.com
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) to 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

---------------------- Page: 10 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 9 ETSI ES 202 504-13 V1.1.1 (2008-05)
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:salesteam@sales.acme.anytelco.com
• sip:salesteam1@sales.acme.anytelco.com
• mailto:fieldservice@cityofaustin.anytelco.com
• group:mailroom@bldg001.acme.anytelco.com
These examples show (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
managed 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 will 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 individual 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 included 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/v3_0
The Group interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/group/v3_0
The GroupMember interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/group_member/v3_0
The data types are defined in the namespace:
http://www.csapi.org/schema/parlayx/group/v3_0
The "xsd" namespace is used in the present document to refer to the XML Schema data types defined in
XML Schema [1]. The use of the name "xsd" is not semantically significant.
ETSI

---------------------- Page: 11 ----------------------

SIST ES 202 504-13 V1.1.1:2008
 10 ETSI ES 202 504-13 V1.1.1 (2008-05)
6 Sequence diagrams
6.1 Manage groups (Create, delete, query, set access and
query access)
Pattern: Request / Response.
The group management functions are shown in this diagram, showing a sequence including the creation of a group,
setting access permissions to the group, querying those permissions, query of groups an
...