SIST ES 202 391-13 V1.3.1:2008

• Abstract:

  Update of ES 202 391 to become Parlay X 2.2, to cover maintenance updates.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 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.

• Status: Published
• Publication Date: 15-Jul-2008
• ICS: 35.100.01 - Open systems interconnection in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 19-Jun-2008
• Due Date: 24-Aug-2008
• Completion Date: 16-Jul-2008
• Ref Project: ETSI ES 202 391-13 V1.3.1 (2008-05) - Open Service Access (OSA); Parlay X Web Services; Part 13: Address List Management (Parlay X 2)

SIST ES 202 391-13 V1.3.1:2008 is the Part 13 Parlay X Web Services standard for Open Service Access (OSA), published by ETSI. It specifies the Address List Management Web Service for application developers and service providers that need to create groups, manage members and attributes, and expose address lists through an open standardized interface.

What does SIST ES 202 391-13 V1.3.1:2008 specify?

SIST ES 202 391-13 V1.3.1:2008 is part 13 of the Stage 3 Parlay X 2 Web Services specification for OSA. It defines the Address List Management Web Service and the way applications use network-managed groups as address lists.

The document covers the service model, message structure, interface operations, and fault handling. It also sets out the WSDL description used to implement the interfaces.

A practical point for readers is that the service works on existing addresses. It does not create addresses; it manages groups of addresses and the memberships and attributes attached to them.

Annex	What it covers
Annex A	Normative WSDL for Address List Management, provided in accompanying text files
Annex B	Informative bibliography

What are the key requirements of SIST ES 202 391-13 V1.3.1:2008?

The standard defines three related interfaces - GroupManagement, Group, and Member - and splits the work between creating groups, managing the contents of groups, and handling information about individual entities. In practice, this lets one service expose address lists while other services consume them through a common OSA interface.

Group creation and naming

Clause 8.1.1 defines createGroup. The requester supplies a group name and a domain segment, and the service provider supplies the remaining domain part. The operation also supports autoName, which can append a suffix to avoid name clashes.

This matters because group URIs must be unique. If autoName is false and the name already exists, the document maps the case to a PolicyException.

Group search and access control

Clause 8.1.3 defines queryGroups, with a search domain and a hierarchy flag. A search can return only groups in one sub-domain or groups in that sub-domain plus its sub-domains.

Clause 8.1.4 and 8.1.5 define access management. setAccess assigns permissions, and queryAccess retrieves them. The permissions are adminPermission, addPermission, deletePermission, and queryPermission.

In practice, access to manage a group is separate from access to work with the members inside it. That separation matters when an operator wants one team to administer the group while another team can only read or update membership.

Membership operations and nested groups

Clause 8.2.1 to 8.2.5 covers addMember, addMembers, deleteMember, deleteMembers, and queryMembers. The service can treat another group URI as a member if nested groups are supported, but recursive inclusion is not allowed.

Clause 8.2.5 is especially important: resolveGroups selects whether the service returns the raw member list or the resolved union of members from nested groups, with duplicates removed. That affects how callers count, display, and process the final address set.

Delete operations remove references from the current group only. When a URI is not present in a bulk delete request, the service ignores it and does not raise a fault.

Attributes on groups, group members, and members

Clause 7 defines the XML data structures used for attributes, and clause 8.2.6 to 8.3.3 defines how to add, query, and delete them.

The document reserves the group attribute names Group.Description and Group.ExpiryDate. Group attributes and group member attributes can be added or updated by users with the relevant admin, add, or read permissions. The Member interface provides attribute operations for a particular entity.

This matters in deployment because the standard supports metadata as well as membership. A system can store descriptive or operational data alongside the address list.

Policy limits and faults

Clause 9 defines four PolicyException cases: too many members in a group, subgroups not supported, group name too long, and group already exists. Clause 10 lists the service policies that drive those cases: MaxGroupLength, MaxGroupMembers, and SupportNestedGroups.

These policy names are important for implementers because they tell the platform where deployment-specific limits live. They also tell integration teams which errors to expect when a provider configures tighter limits than an application assumes.

What terms does SIST ES 202 391-13 V1.3.1:2008 define?

• application managed group - A group created and managed outside the network, where the group members are passed into the network for processing.
• group - A container for a set of addresses, not an address itself.
• group resolution - The process of expanding a group, including nested groups, into a unique set of addresses with duplicates removed.
• network managed group - A group created and managed within a network so that Web Services can reference its members by the group name.
• AccessPermissions - A structure that records whether a requester has admin, add, delete, and query permission for a group.
• AttributeStatus - An enumeration with the values Valid, Unknown, and Denied for an attribute.
• SimpleAttribute - A structure that carries an attribute name, type, value, and status.

Who uses SIST ES 202 391-13 V1.3.1:2008?

SIST ES 202 391-13 V1.3.1:2008 is used by application developers, service providers, and platform integrators working with OSA APIs and Parlay X Web Services. It is relevant when they need to expose address lists, group membership, and group-level metadata through a standardized service interface.

It also serves teams that implement or test service-side web services in telecom and converged-service environments. For them, the value is the clear split between group administration, membership management, and attribute handling.

What changed in SIST ES 202 391-13 V1.3.1:2008 from the previous edition?

The foreword states that this version updates ES 202 391 to become Parlay X 2.2 and covers maintenance updates. It also places the document in the Parlay X 2.2 set and identifies it as equivalent to 3GPP TS 29.199-13 V6.5.0 (Release 6).

Which standards are used with SIST ES 202 391-13 V1.3.1:2008?

• ETSI ES 202 391-1, Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 2) - Provides the shared Parlay X framework and the referenced common definitions.
• W3C Recommendation, XML Schema Part 2: Datatypes - Supplies the XML Schema data types used for fields such as xsd:string, xsd:boolean, xsd:anyURI, and xsd:int.
• IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax - Defines the URI style used for group naming and domain structure.
• The Parlay X Web Services family - The foreword places this document in the multi-part set that includes Part 1 Common and the service parts up to Part 14 Presence.

What does the SIST ES 202 391-13 V1.3.1:2008 document contain?

Clause 6 gives two request/response sequence diagrams: one for group administration and one for member management. Clause 7 defines the XML Schema data types used by the service, including the access and attribute structures.

Clause 8 contains the main interface specification, with method descriptions, input and output messages, and referenced faults for group creation, search, access control, membership operations, and attribute operations. Clause 9 defines the PolicyException messages, and clause 10 lists the service policy names that bound behavior.

Annex A provides the normative WSDL representation for implementation. Annex B provides a bibliography for further background.

Final draft ETSI ES 202 391-13 V1.3.1 (2008-02)
ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 13: Address List Management
(Parlay X 2)
�
2 Final draft ETSI ES 202 391-13 V1.3.1 (2008-02)

Reference
RES/TISPAN-01056-13-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
3 Final draft ETSI ES 202 391-13 V1.3.1 (2008-02)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
4.1 Group URI format .7
4.2 Address list usage in services .8
5 Namespaces.8
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,
QueryMembers) .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 definition.11
8.1 Interface: GroupManagement.11
8.1.1 Operation: createGroup.11
8.1.1.1 Input message: createGroupRequest.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: queryGroupsRequest.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: queryAccess.14
8.1.5.1 Input message: queryAccessRequest.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: addMemberRequest.15
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 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: deleteMemberRequest.16
ETSI
4 Final draft ETSI ES 202 391-13 V1.3.1 (2008-02)
8.2.3.2 Output message: deleteMemberResponse.16
8.2.3.3 Referenced faults.16
8.2.4 Operation: deleteMembers.16
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: queryMembersResponse.17
8.2.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: addGroupAttributeResponse.18
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 Output message: deleteGroupAttributeResponse.18
8.2.7.3 Referenced faults.18
8.2.8 Operation: queryGroupAttributes.19
8.2.8.1 Input message: queryGroupAttributesRequest.19
8.2.8.2 Output message: queryGroupAttributesResponse.19
8.2.8.3 Referenced faults.19
8.2.9 Operation: addGroupMemberAttribute.19
8.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: deleteGroupMemberAttributeResponse .20
8.2.10.3 Referenced faults.20
8.2.11 Operation: queryGroupMemberAttributes.20
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: addMemberAttribute.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: queryMemberAttributes.21
8.3.2.1 Input message: queryMemberAttributesRequest.21
8.3.2.2 Output message: queryMemberAttributesResponse .21
8.3.2.3 Referenced faults.22
8.3.3 Operation: deleteMemberAttribute.22
8.3.3.1 Input message: deleteMemberAttributeRequest.22
8.3.3.2 Output message: deleteMemberAttributeResponse.22
8.3.3.3 Referenced faults.22
9 Fault definitions.22
9.1 PolicyException.22
9.1.1 POL0210: Too many members in group.22
9.1.2 POL0211: Subgroups not supported.23
9.1.3 POL0212: Group name too long.23
9.1.4 POL0213: Group already exists.23
10 Service policies .23
Annex A (normative): WSDL for Address List Management.24
Annex B (informative): Bibliography.25
History .26

ETSI
5 Final draft ETSI ES 202 391-13 V1.3.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".
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 (Release 6).
ETSI
6 Final draft ETSI ES 202 391-13 V1.3.1 (2008-02)
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
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
7 Final draft ETSI ES 202 391-13 V1.3.1 (2008-02)
[2] ETSI ES 202 391-1: "Open 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 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 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 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:[e-mail]
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
8 Final draft ETSI ES 202 391-13 V1.3.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:[e-mail]
• sip:[e-mail]
• mailto:[e-mail]
• group:[e-mail]
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 s
...

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 13: Address List Management
(Parlay X 2)
�
2 ETSI ES 202 391-13 V1.3.1 (2008-05)

Reference
RES/TISPAN-01056-13-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
3 ETSI ES 202 391-13 V1.3.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
4.1 Group URI format .7
4.2 Address list usage in services .8
5 Namespaces.8
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,
QueryMembers) .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 definition.11
8.1 Interface: GroupManagement.11
8.1.1 Operation: createGroup.11
8.1.1.1 Input message: createGroupRequest.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: queryGroupsRequest.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: queryAccess.14
8.1.5.1 Input message: queryAccessRequest.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: addMemberRequest.15
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 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: deleteMemberRequest.16
ETSI
4 ETSI ES 202 391-13 V1.3.1 (2008-05)
8.2.3.2 Output message: deleteMemberResponse.16
8.2.3.3 Referenced faults.16
8.2.4 Operation: deleteMembers.16
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: queryMembersResponse.17
8.2.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: addGroupAttributeResponse.18
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 Output message: deleteGroupAttributeResponse.18
8.2.7.3 Referenced faults.18
8.2.8 Operation: queryGroupAttributes.19
8.2.8.1 Input message: queryGroupAttributesRequest.19
8.2.8.2 Output message: queryGroupAttributesResponse.19
8.2.8.3 Referenced faults.19
8.2.9 Operation: addGroupMemberAttribute.19
8.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: deleteGroupMemberAttributeResponse .20
8.2.10.3 Referenced faults.20
8.2.11 Operation: queryGroupMemberAttributes.20
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: addMemberAttribute.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: queryMemberAttributes.21
8.3.2.1 Input message: queryMemberAttributesRequest.21
8.3.2.2 Output message: queryMemberAttributesResponse .21
8.3.2.3 Referenced faults.22
8.3.3 Operation: deleteMemberAttribute.22
8.3.3.1 Input message: deleteMemberAttributeRequest.22
8.3.3.2 Output message: deleteMemberAttributeResponse.22
8.3.3.3 Referenced faults.22
9 Fault definitions.22
9.1 PolicyException.22
9.1.1 POL0210: Too many members in group.22
9.1.2 POL0211: Subgroups not supported.23
9.1.3 POL0212: Group name too long.23
9.1.4 POL0213: Group already exists.23
10 Service policies .23
Annex A (normative): WSDL for Address List Management.24
Annex B (informative): Bibliography.25
History .26

ETSI
5 ETSI ES 202 391-13 V1.3.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".
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 (Release 6).
ETSI
6 ETSI ES 202 391-13 V1.3.1 (2008-05)
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
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
7 ETSI ES 202 391-13 V1.3.1 (2008-05)
[2] ETSI ES 202 391-1: "Open 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 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 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 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:[e-mail]
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
8 ETSI ES 202 391-13 V1.3.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:[e-mail]
• sip:[e-mail]
• mailto:[e-mail]
• group:[e-mail]
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 require
...

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

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 13: Address List Management
(Parlay X 2)
�
2 ETSI ES 202 391-13 V1.3.1 (2008-05)

Reference
RES/TISPAN-01056-13-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
3 ETSI ES 202 391-13 V1.3.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
4.1 Group URI format .7
4.2 Address list usage in services .8
5 Namespaces.8
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,
QueryMembers) .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 definition.11
8.1 Interface: GroupManagement.11
8.1.1 Operation: createGroup.11
8.1.1.1 Input message: createGroupRequest.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: queryGroupsRequest.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: queryAccess.14
8.1.5.1 Input message: queryAccessRequest.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: addMemberRequest.15
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 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: deleteMemberRequest.16
ETSI
4 ETSI ES 202 391-13 V1.3.1 (2008-05)
8.2.3.2 Output message: deleteMemberResponse.16
8.2.3.3 Referenced faults.16
8.2.4 Operation: deleteMembers.16
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: queryMembersResponse.17
8.2.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: addGroupAttributeResponse.18
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 Output message: deleteGroupAttributeResponse.18
8.2.7.3 Referenced faults.18
8.2.8 Operation: queryGroupAttributes.19
8.2.8.1 Input message: queryGroupAttributesRequest.19
8.2.8.2 Output message: queryGroupAttributesResponse.19
8.2.8.3 Referenced faults.19
8.2.9 Operation: addGroupMemberAttribute.19
8.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: deleteGroupMemberAttributeResponse .20
8.2.10.3 Referenced faults.20
8.2.11 Operation: queryGroupMemberAttributes.20
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: addMemberAttribute.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: queryMemberAttributes.21
8.3.2.1 Input message: queryMemberAttributesRequest.21
8.3.2.2 Output message: queryMemberAttributesResponse .21
8.3.2.3 Referenced faults.22
8.3.3 Operation: deleteMemberAttribute.22
8.3.3.1 Input message: deleteMemberAttributeRequest.22
8.3.3.2 Output message: deleteMemberAttributeResponse.22
8.3.3.3 Referenced faults.22
9 Fault definitions.22
9.1 PolicyException.22
9.1.1 POL0210: Too many members in group.22
9.1.2 POL0211: Subgroups not supported.23
9.1.3 POL0212: Group name too long.23
9.1.4 POL0213: Group already exists.23
10 Service policies .23
Annex A (normative): WSDL for Address List Management.24
Annex B (informative): Bibliography.25
History .26

ETSI
5 ETSI ES 202 391-13 V1.3.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".
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 (Release 6).
ETSI
6 ETSI ES 202 391-13 V1.3.1 (2008-05)
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
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
7 ETSI ES 202 391-13 V1.3.1 (2008-05)
[2] ETSI ES 202 391-1: "Open 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 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 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 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:[e-mail]
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
8 ETSI ES 202 391-13 V1.3.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:[e-mail]
• sip:[e-mail]
• mailto:[e-mail]
• group:[e-mail]
These examples show (1)(2)
...