SIST ES 202 504-8 V1.1.1:2008

• Abstract:

  New edition of ParlayX specification based on requirements in EG 201 988-4, corresponding to 3GPP TS 29.199 Rel-7.The present document is part 8 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 Terminal Status 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: 14-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: 18-Jun-2008
• Due Date: 23-Aug-2008
• Completion Date: 15-Jul-2008
• Ref Project: ETSI ES 202 504-8 V1.1.1 (2008-05) - Open Service Access (OSA); Parlay X Web Services; Part 8: Terminal Status (Parlay X 3)

SIST ES 202 504-8 V1.1.1:2008 is an ETSI standard in the Open Service Access (OSA) Parlay X Web Services family, Part 8: Terminal Status. It specifies the Terminal Status Web Service for requesting the status of a single terminal or a group of terminals and for subscribing to terminal status changes, together with the interface messages, data types, faults, service policies, namespaces, and WSDL. It is aimed at application developers and implementers that expose or consume network status information through the OSA APIs.

What does SIST ES 202 504-8 V1.1.1:2008 specify?

SIST ES 202 504-8 V1.1.1:2008 specifies the Parlay X 3 Terminal Status Web Service within Open Service Access (OSA). In practice, that means it defines how an application can ask for terminal status, how it can receive status-change notifications, and how those exchanges are described in XML and WSDL.

The document is organized around the service description, namespaces, sequence diagrams, XML Schema data types, web service interfaces, fault definitions, service policies, and a normative WSDL annex. Clause 4 explains the service behavior, Clauses 6 to 10 define the messages and policies, and Annex A provides the WSDL representation.

Annex	What it covers
Annex A	WSDL for Terminal Status
Annex B	Bibliography

What are the key requirements of SIST ES 202 504-8 V1.1.1:2008?

SIST ES 202 504-8 V1.1.1:2008 is mainly about three use cases: query one terminal, query a set of terminals, and subscribe to terminal status changes. The practical effect is that a client must choose the right operation for the address type it has, and it must handle policy limits and partial results.

Terminal status values and retrieval behavior

Clause 4 and Clause 7 define the status model used by the service. The status of a terminal can be Reachable, Unreachable, or Busy, and the service notes that not every terminal supports the Busy condition. In practice, an application should check the service properties before assuming Busy can be used as a returned status or a notification trigger.

For group requests, the service may return a full or partial result set. Where no attempt was made for a given address, the result uses NotRetrieved; where retrieval failed, it uses Error and may include error information. This is important when a batch request is time-sensitive, because the caller can retry only the unresolved addresses instead of repeating the whole set.

Query operations

Clause 8.1 defines getStatus for a single terminal and getStatusForGroup for one or more terminals, including group URIs. The single-terminal operation expects a single terminal URI, and if a group URI is supplied it can lead to a PolicyException. That matters when building clients, because the address form has to match the operation.

The group query accepts a list of URIs and can include group URIs. The service may intentionally return incomplete information to avoid timeouts or other service constraints, so the caller should treat the response as a result set rather than a guaranteed all-or-nothing answer.

Notification setup and delivery

Clause 8.2 defines startNotification and endNotification for terminal status monitoring. The setup includes a reference correlator, one or more terminal addresses, the status criteria to watch for, checkImmediate, notification frequency, optional duration, and optional count. The correlator must be unique while the notification is being initiated, or the request can fail with a ServiceException.

The checkImmediate flag is important in real deployments because it closes the gap between setup and monitoring. If it is true, the service checks the current status after the subscription is established and sends a notification immediately if the criteria already match. That prevents missed events in cases such as “call when available” services.

The notification lifecycle is controlled by both the request and the service policies in Clause 10. Frequency, duration, count, group support, nested group support, and whether unlimited count is allowed can all be governed by policy. If the duration or count limit ends, the service sends a statusEnd event; if the application ends the notification with endNotification, statusEnd is not invoked.

Data structures and error handling

Clause 7 defines the data structures used in requests and notifications. StatusData carries the terminal address, the retrieval status, the current status when available, and error information when retrieval fails. StatusInformation is the simplified structure used by the notification interface, carrying the terminal address and its current status.

Clause 9 defines a specific PolicyException, POL0200, for cases where Busy is not supported as a criteria. In practice, this means an application must be prepared to downgrade its criteria or choose another status if the service policy does not allow Busy-based triggering.

What terms does SIST ES 202 504-8 V1.1.1:2008 define?

• Status - The terminal condition reported by the service, with the values Reachable, Unreachable, and Busy.
• RetrievalStatus - The result of an individual retrieval inside a group request, showing whether the status was retrieved, not retrieved, or ended in error.
• StatusData - The structure used for group-style results, combining the terminal address, retrieval status, current status when available, and error information when needed.
• StatusInformation - The simpler structure used in notifications, carrying a terminal address and its current status.
• checkImmediate - A Boolean request parameter that tells the service to check the current status right after the notification is set up.
• correlator - The identifier used to link notification setup, delivery, and termination messages for the same subscription.

Who uses SIST ES 202 504-8 V1.1.1:2008?

SIST ES 202 504-8 V1.1.1:2008 is used by application developers who need terminal status from a network through the OSA APIs. It is also used by service implementers, platform engineers, and integrators who expose the Terminal Status Web Service or consume it from an application.

In practice, the standard is relevant for telecom and service-platform work where an application must check whether a device is reachable, watch for state changes, or handle group status queries. Quality and test teams use it to verify message formats, policy behavior, notification flows, and fault handling.

Which standards are used with SIST ES 202 504-8 V1.1.1:2008?

The main normative companion is ETSI ES 202 504-1, which supplies the common OSA Parlay X definitions, abbreviations, and referenced faults used by this part. Several faults in Clause 8 point back to that common part, so implementers need it to interpret shared error handling correctly.

The other normative reference is the W3C Recommendation XML Schema Part 2: Datatypes. It provides the datatype rules behind the xsd types used in the schema and message definitions, such as anyURI, boolean, integer, and string.

What does the SIST ES 202 504-8 V1.1.1:2008 document contain?

The document contains a service description, two kinds of query sequence diagrams, and two notification scenarios, including the checkImmediate case. Clause 7 provides XML Schema data type tables for the terminal status enumerations and data structures used by requests, results, and notifications.

Clause 8 contains the web service interface definitions for TerminalStatus, TerminalStatusNotificationManager, and TerminalNotification, with the request and response message parts for each operation. Clause 9 lists the policy exception for unsupported Busy criteria, and Clause 10 lists the service policy parameters that shape address limits, frequency, duration, counts, group support, and nested group support.

Annex A provides the document/literal WSDL for the service in accompanying text files, which is the practical starting point for implementation and interoperability testing.

Final draft ETSI ES 202 504-8 V1.1.1 (2008-02)
ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 8: Terminal Status
(Parlay X 3)
�
2 Final draft ETSI ES 202 504-8 V1.1.1 (2008-02)

Reference
DES/TISPAN-01034-8-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 504-8 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
5 Namespaces.8
6 Sequence diagrams.9
6.1 Terminal status query.9
6.2 Terminal status group query.10
6.3 Terminal status notification.11
6.4 Terminal Status Notification with Check Immediate .12
7 XML Schema data type definition .13
7.1 Status enumeration.13
7.2 RetrievalStatus enumeration.13
7.3 StatusData structure.14
7.4 StatusInformation structure.14
8 Web Service interface definition.14
8.1 Interface: TerminalStatus.14
8.1.1 Operation: getStatus.14
8.1.1.1 Input message: getStatusRequest .14
8.1.1.2 Output message: getStatusResponse.14
8.1.1.3 Referenced faults.14
8.1.2 Operation: getStatusForGroup.15
8.1.2.1 Input message: getStatusForGroupRequest.15
8.1.2.2 Output message: getStatusForGroupResponse.15
8.1.2.3 Referenced faults.15
8.2 Interface: TerminalStatusNotificationManager .15
8.2.1 Operation: startNotification.16
8.2.1.1 Input message: startNotificationRequest.16
8.2.1.2 Output message: startNotificationResponse.16
8.2.1.3 Referenced faults.16
8.2.2 Operation: endNotification.17
8.2.2.1 Input message: endNotificationRequest.17
8.2.2.2 Output message: endNotificationResponse.17
8.2.2.3 Referenced faults.17
8.3 Interface: TerminalNotification.17
8.3.1 Operation: statusNotification.17
8.3.1.1 Input message: statusNotificationRequest.18
8.3.1.2 Output message: statusNotificationResponse.18
8.3.1.3 Referenced faults.18
8.3.2 Operation: statusError.18
8.3.2.1 Input message: statusErrorRequest .18
8.3.2.2 Output message: statusErrorResponse.18
8.3.2.3 Referenced faults.18
8.3.3 Operation: statusEnd.18
8.3.3.1 Input message: statusEndRequest .18
8.3.3.2 Output message: statusEndResponse.18
ETSI
4 Final draft ETSI ES 202 504-8 V1.1.1 (2008-02)
8.3.3.3 Referenced faults.19
9 Fault definitions.19
9.1 PolicyException.19
9.1.1 POL0200: Busy criteria not supported .19
10 Service policies .19
Annex A (normative): WSDL for Terminal Status.20
Annex B (informative): Bibliography.21
History .22

ETSI
5 Final draft ETSI ES 202 504-8 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 8 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
6 Final draft ETSI ES 202 504-8 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-08 V7.0.2 (Release 7).
ETSI
7 Final draft ETSI ES 202 504-8 V1.1.1 (2008-02)
1 Scope
The present document is part 8 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 Terminal Status 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
8 Final draft ETSI ES 202 504-8 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 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 504-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 504-1 [2] apply.
4 Detailed service description
Terminal Status provides access to the status of a terminal through:
• Request for the status of a terminal.
• Request for the status of a group of terminals.
• Notification of a change in the status of a terminal.
The status of a terminal can be expressed as reachable, unreachable or busy - however not all terminals distinguish a
busy status, so applications should be able to adapt to what information is available (using the service properties to
determine available information).
When a request for a group of terminals is made, the response may contain a full or partial set of results. This allows the
service to provide results based on a number of criteria including number of terminals for which the request is made and
amount of time required to retrieve the information. This allows the requester to initiate additional requests for those
terminals for which information was not provided.
5 Namespaces
The TerminalStatus interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/terminal_status/v3_0
The TerminalStatusNotificationManager inter
...

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 8: Terminal Status
(Parlay X 3)
�
2 ETSI ES 202 504-8 V1.1.1 (2008-05)

Reference
DES/TISPAN-01034-8-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 504-8 V1.1.1 (2008-05)
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
5 Namespaces.8
6 Sequence diagrams.9
6.1 Terminal status query.9
6.2 Terminal status group query.10
6.3 Terminal status notification.11
6.4 Terminal Status Notification with Check Immediate .12
7 XML Schema data type definition .13
7.1 Status enumeration.13
7.2 RetrievalStatus enumeration.13
7.3 StatusData structure.14
7.4 StatusInformation structure.14
8 Web Service interface definition.14
8.1 Interface: TerminalStatus.14
8.1.1 Operation: getStatus.14
8.1.1.1 Input message: getStatusRequest .14
8.1.1.2 Output message: getStatusResponse.14
8.1.1.3 Referenced faults.14
8.1.2 Operation: getStatusForGroup.15
8.1.2.1 Input message: getStatusForGroupRequest.15
8.1.2.2 Output message: getStatusForGroupResponse.15
8.1.2.3 Referenced faults.15
8.2 Interface: TerminalStatusNotificationManager .15
8.2.1 Operation: startNotification.16
8.2.1.1 Input message: startNotificationRequest.16
8.2.1.2 Output message: startNotificationResponse.16
8.2.1.3 Referenced faults.16
8.2.2 Operation: endNotification.17
8.2.2.1 Input message: endNotificationRequest.17
8.2.2.2 Output message: endNotificationResponse.17
8.2.2.3 Referenced faults.17
8.3 Interface: TerminalNotification.17
8.3.1 Operation: statusNotification.17
8.3.1.1 Input message: statusNotificationRequest.18
8.3.1.2 Output message: statusNotificationResponse.18
8.3.1.3 Referenced faults.18
8.3.2 Operation: statusError.18
8.3.2.1 Input message: statusErrorRequest .18
8.3.2.2 Output message: statusErrorResponse.18
8.3.2.3 Referenced faults.18
8.3.3 Operation: statusEnd.18
8.3.3.1 Input message: statusEndRequest .18
8.3.3.2 Output message: statusEndResponse.18
ETSI
4 ETSI ES 202 504-8 V1.1.1 (2008-05)
8.3.3.3 Referenced faults.19
9 Fault definitions.19
9.1 PolicyException.19
9.1.1 POL0200: Busy criteria not supported .19
10 Service policies .19
Annex A (normative): WSDL for Terminal Status.20
Annex B (informative): Bibliography.21
History .22

ETSI
5 ETSI ES 202 504-8 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 8 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
6 ETSI ES 202 504-8 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-08 V7.0.2 (Release 7).
ETSI
7 ETSI ES 202 504-8 V1.1.1 (2008-05)
1 Scope
The present document is part 8 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 Terminal Status 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
8 ETSI ES 202 504-8 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 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 504-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 504-1 [2] apply.
4 Detailed service description
Terminal Status provides access to the status of a terminal through:
• Request for the status of a terminal.
• Request for the status of a group of terminals.
• Notification of a change in the status of a terminal.
The status of a terminal can be expressed as reachable, unreachable or busy - however not all terminals distinguish a
busy status, so applications should be able to adapt to what information is available (using the service properties to
determine available information).
When a request for a group of terminals is made, the response may contain a full or partial set of results. This allows the
service to provide results based on a number of criteria including number of terminals for which the request is made and
amount of time required to retrieve the information. This allows the requester to initiate additional requests for those
terminals for which information was not provided.
5 Namespaces
The TerminalStatus interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/terminal_status/v3_0
The TerminalStatusNotificationManager interface uses the
...

SLOVENSKI STANDARD
01-september-2008
Odprti dostop do storitve (OSA) - Spletne storitve Parlay X - 8. del: Stanje
terminala (Parlay X 3)
Open Service Access (OSA) - Parlay X Web Services - Part 8: Terminal Status (Parlay X
3)
Ta slovenski standard je istoveten z: ES 202 504-8 Version 1.1.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 8: Terminal Status
(Parlay X 3)
�
2 ETSI ES 202 504-8 V1.1.1 (2008-05)

Reference
DES/TISPAN-01034-8-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 504-8 V1.1.1 (2008-05)
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
5 Namespaces.8
6 Sequence diagrams.9
6.1 Terminal status query.9
6.2 Terminal status group query.10
6.3 Terminal status notification.11
6.4 Terminal Status Notification with Check Immediate .12
7 XML Schema data type definition .13
7.1 Status enumeration.13
7.2 RetrievalStatus enumeration.13
7.3 StatusData structure.14
7.4 StatusInformation structure.14
8 Web Service interface definition.14
8.1 Interface: TerminalStatus.14
8.1.1 Operation: getStatus.14
8.1.1.1 Input message: getStatusRequest .14
8.1.1.2 Output message: getStatusResponse.14
8.1.1.3 Referenced faults.14
8.1.2 Operation: getStatusForGroup.15
8.1.2.1 Input message: getStatusForGroupRequest.15
8.1.2.2 Output message: getStatusForGroupResponse.15
8.1.2.3 Referenced faults.15
8.2 Interface: TerminalStatusNotificationManager .15
8.2.1 Operation: startNotification.16
8.2.1.1 Input message: startNotificationRequest.16
8.2.1.2 Output message: startNotificationResponse.16
8.2.1.3 Referenced faults.16
8.2.2 Operation: endNotification.17
8.2.2.1 Input message: endNotificationRequest.17
8.2.2.2 Output message: endNotificationResponse.17
8.2.2.3 Referenced faults.17
8.3 Interface: TerminalNotification.17
8.3.1 Operation: statusNotification.17
8.3.1.1 Input message: statusNotificationRequest.18
8.3.1.2 Output message: statusNotificationResponse.18
8.3.1.3 Referenced faults.18
8.3.2 Operation: statusError.18
8.3.2.1 Input message: statusErrorRequest .18
8.3.2.2 Output message: statusErrorResponse.18
8.3.2.3 Referenced faults.18
8.3.3 Operation: statusEnd.18
8.3.3.1 Input message: statusEndRequest .18
8.3.3.2 Output message: statusEndResponse.18
ETSI
4 ETSI ES 202 504-8 V1.1.1 (2008-05)
8.3.3.3 Referenced faults.19
9 Fault definitions.19
9.1 PolicyException.19
9.1.1 POL0200: Busy criteria not supported .19
10 Service policies .19
Annex A (normative): WSDL for Terminal Status.20
Annex B (informative): Bibliography.21
History .22

ETSI
5 ETSI ES 202 504-8 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 8 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
6 ETSI ES 202 504-8 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-08 V7.0.2 (Release 7).
ETSI
7 ETSI ES 202 504-8 V1.1.1 (2008-05)
1 Scope
The present document is part 8 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 Terminal Status 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
8 ETSI ES 202 504-8 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 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 504-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 504-1 [2] apply.
4 Detailed service description
Terminal Status provides access to the status of a terminal through:
• Request for the status of a terminal.
• Request for the status of a group of terminals.
• Notification of a change in the status of a terminal.
The status of a terminal can be expressed as reachable, unreachable or busy - however not all terminals distinguish a
busy status, so applications should be able to adapt to what information is available (using the service properties to
determine available information).
When a request for a group of terminals is made, the response may contain a full or partial set of results. This allows the
service to provide results based on a number of criteria including number of terminals for which the request is made and
amount of time required to retrieve the information. This allows the requester to initiate addi
...