`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`ETSI Standard
`
`Open Service Access (OSA);
`Parlay X Web Services;
`Part 2: Third Party Call
`(Parlay X 2)
`
`
`
`
`
`
`
`
`
`
`
`
`
`TELESIGN EX1008
`Page 1
`
`

`

`
`
`
`
`
`
`
`
`
`2
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`Reference
`RES/TISPAN-01033-02-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 2006.
`© The Parlay Group 2006.
`All rights reserved.
`
`DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members.
`TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
`3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
`
`ETSI
`
`TELESIGN EX1008
`Page 2
`
`

`

`
`
`
`3
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`Contents
`
`2
`
`3
`3.1
`3.2
`
`4
`
`5
`
`6
`6.1
`
`Intellectual Property Rights ................................................................................................................................4
`Foreword.............................................................................................................................................................4
`Scope ........................................................................................................................................................5
`1
`References ................................................................................................................................................5
`Definitions and abbreviations...................................................................................................................5
`Definitions..........................................................................................................................................................5
`Abbreviations .....................................................................................................................................................5
`Detailed service description .....................................................................................................................6
`Namespaces..............................................................................................................................................6
`Sequence diagrams...................................................................................................................................7
`"Click to Dial" call setup....................................................................................................................................7
`XML Schema data type definition ...........................................................................................................8
`7
`CallStatus enumeration.......................................................................................................................................8
`7.1
`CallTerminationCause enumeration ...................................................................................................................8
`7.2
`CallInformation Structure...................................................................................................................................8
`7.3
`8 Web Service interface definition..............................................................................................................8
`Interface: ThirdPartyCall....................................................................................................................................8
`8.1
`Operation: makeCall .....................................................................................................................................8
`8.1.1
`Input message: makeCallRequest............................................................................................................9
`8.1.1.1
`Output message : makeCallResponse......................................................................................................9
`8.1.1.2
`Referenced faults.....................................................................................................................................9
`8.1.1.3
`Operation: getCallInformation......................................................................................................................9
`8.1.2
`Input message: getCallInformationRequest ............................................................................................9
`8.1.2.1
`Output message : getCallInformationResponse ......................................................................................9
`8.1.2.2
`Referenced faults.....................................................................................................................................9
`8.1.2.3
`Operation: endCall......................................................................................................................................10
`8.1.3
`Input message: endCallRequest ............................................................................................................10
`8.1.3.1
`Output message: endCallResponse .......................................................................................................10
`8.1.3.2
`Referenced faults...................................................................................................................................10
`8.1.3.3
`Operation: cancelCall .................................................................................................................................10
`8.1.4
`Input message: cancelCallRequest ........................................................................................................10
`8.1.4.1
`Output message: cancelCallResponse ...................................................................................................10
`8.1.4.2
`Referenced faults...................................................................................................................................11
`8.1.4.3
`Fault definitions......................................................................................................................................11
`ServiceException..............................................................................................................................................11
`SVC0260: Call already connected ..............................................................................................................11
`SVC0261: Call already terminated .............................................................................................................11
`Service policies ......................................................................................................................................11
`
`9
`9.1
`9.1.1
`9.1.2
`
`10
`
`Annex A (normative):
`
`WSDL for Third Party Call..........................................................................12
`
`Bibliography...................................................................................................13
`Annex B (informative):
`History ..............................................................................................................................................................14
`
`
`ETSI
`
`TELESIGN EX1008
`Page 3
`
`

`

`
`
`
`4
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`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 2 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.1 set of specifications.
`
`The present document is equivalent to 3GPP TS 29.199-02 V6.3.0 (Release 6).
`
`ETSI
`
`TELESIGN EX1008
`Page 4
`
`

`

`
`
` 1
`
`5
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`Scope
`
`The present document is part 2 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.
`
`Name spaces.
`
`Sequence diagrams.
`
`Data definitions.
`
`The present document specifies the Third Party Call Web Service. The following are defined here:
`•
`•
`•
`•
`•
`•
`Service Policies.
`• WSDL Description of the interfaces.
`
`Interface specification plus detailed method descriptions.
`
`Fault definitions.
`
`References
`2
`The following documents contain provisions which, through reference in this text, constitute provisions of the present
`document.
`•
`
`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.
`
`For a non-specific reference, the latest version applies.
`
`Referenced documents which are not found to be publicly available in the expected location might be found at
`http://docbox.etsi.org/Reference.
`
`NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
`their long term validity.
`
`[1]
`
`W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
`
`NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
`
`[2]
`
`ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services;
`Part 1: Common (Parlay X 2)".
`
`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] apply.
`
`3.2
`
`Abbreviations
`
`For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] apply.
`
`ETSI
`
`TELESIGN EX1008
`Page 5
`
`

`

`6
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`
`
` 4
`
`Detailed service description
`
`Currently, in order to perform a third party call in telecommunication networks we have to write applications using
`specific protocols to access Call Control functions provided by network elements (specifically operations to initiate a
`call from applications). This approach requires a high degree of network expertise. We can also use the OSA gateway
`approach, invoking standard interfaces to gain access to call control capabilities, but these interfaces are usually
`perceived to be quite complex by application IT developers. Developers must have advanced telecommunication skills
`to use Call Control OSA interfaces.
`
`In this clause we describe a Parlay X 2 Web Service, Third Party Call, for creating and managing a call initiated by an
`application (third party call). The overall scope of this Web Service is to provide functions to application developers to
`create a call in a simple way. Using the Third Party Call Web Service, application developers can invoke call handling
`functions without detailed telecommunication knowledge.
`
`Figure 1 shows a scenario using the Third Party Call Web Service to handle third party call functions. The application
`invokes a Web Service to retrieve stock quotes and a Parlay X 2 Interface to initiate a third party call between a broker
`and his client.
`
`In the scenario, whenever a particular stock quote reaches a threshold value (1) and (2), the client application invokes a
`third party call between one or more brokers and their corresponding customers to decide actions to be taken. After
`invocation (3) by the application, the Third Party Call Web Service invokes a Parlay API method (4) using the
`Parlay/OSA SCS-CC (Call control) interface. This SCS handles the invocation and sends a message (5) to an MSC to
`set-up a call between user A and user B.
`
`In an alternative scenario, the Parlay API interaction involving steps (4) and (5) could be replaced with a direct
`interaction between the Third Party Call Web Service and the Mobile network.
`
`Stock Quotes
`Stock Quotes
`Web Service
`Web Service
`
`Third Party
`Call Web
`3PC-X
`Service
`component
`
`Parlay X I/F
`
`4
`
`SCS-CC
`SCS-CC
`
`1
`
`Parlay API
`
`Parlay Gateway
`
`5
`
`3
`
`……..
`getStockQuote ()
`…..
`Retrieve
`user Profile ( userA,
`userB)
`
`….
`makeACall (userA,
`userB,,)
`
`2
`
`User
`profile
`
`MSCMSC
`
`Mobile network
`
`UserB
`(customer)
`
`UserA
`(broker)
`
`
`
`Figure 1: Third party call scenario
`
`Namespaces
`5
`The ThirdPartyCall interface uses the namespace:
`
`http://www.csapi.org/wsdl/parlayx/third_party_call/v2_3
`
`The data types are defined in the namespace:
`
`http://www.csapi.org/schema/parlayx/third_party_call/v2_3
`
`ETSI
`
`TELESIGN EX1008
`Page 6
`
`

`

`
`
`
`7
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`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.
`
`6
`
`Sequence diagrams
`
`6.1
`
`"Click to Dial" call setup
`
`A common convergence application is Click to Dial, where a self service portal provides a web page that can initiate a
`call between two phones. This sequence shows a basic call setup, and ending the call through the portal.
`
` : End User
`
` : Self Serve
`Portal
`
` : Third Party Call
`Web Service
`
`Access portal
`
`Use Click to Dial page
`
`Report call in progress
`
`Some
`discussion
`
`Click on end call
`
`Make call
`
`Call identifier
`
`End call
`
`Figure 2
`
`
`
`ETSI
`
`TELESIGN EX1008
`Page 7
`
`

`

`8
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`XML Schema data type definition
`
`
`
` 7
`
`
`
`7.1
`
`CallStatus enumeration
`
`List of call status values.
`
`Enumeration value
`CallInitial
`CallConnected
`CallTerminated
`
`Description
`The call is being established
`The call is active
`The call was terminated
`
`
`
`7.2
`
`CallTerminationCause enumeration
`
`List of call termination cause values.
`
`Enumeration value
`CallingPartyNoAnswer
`CalledPartyNoAnswer
`CallingPartyBusy
`CalledPartyBusy
`CallingPartyNotReachable
`CalledPartyNotReachable
`CallHangUp
`CallAborted
`
`Description
`Calling Party did not answer
`Called Party did not answer
`Calling Party was busy
`Called Party was busy
`Calling Party was not reachable
`Called Party was not reachable
`The call was terminated by either party hanging up
`The call was aborted (any other termination cause)
`
`
`
`7.3
`
`CallInformation Structure
`
`Call information for this call.
`
`Element name
`callStatus
`
`Element type
`CallStatus
`
`Optional
`No
`
`startTime
`
`duration
`
`xsd:dateTime
`
`xsd:int
`
`Yes
`
`Yes
`
`terminationCause
`
`CallTerminationCause Yes
`
`Description
`It indicates the current status of the call (see possible values
`below)
`When applicable (callStatus <> CallInitial), it indicates the
`time of the beginning of the call
`When applicable (callStatus = CallTerminated), it indicates
`the duration of the call expressed in seconds
`When applicable (callStatus = CallTerminated), it indicates
`the cause of the termination of the call
`
`Web Service interface definition
`
` 8
`
`
`
`8.1
`
`Interface: ThirdPartyCall
`
`This interface provides the ability to setup, end and determine the status of a call.
`
`8.1.1 Operation: makeCall
`
`The invocation of makeCall requests to set-up a voice call between two addresses, callingParty and calledParty,
`provided that the invoking application is allowed to connect them. Optionally the application can also indicate the
`charging information (charging).
`
`ETSI
`
`TELESIGN EX1008
`Page 8
`
`

`

`
`
`
`9
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`By invoking this operation the application may monitor the status of the requested call. The returned parameter,
`callIdentifier, can be used to identify the call. In order to receive the information on call status the application has to
`explicitly invoke getCallInformation.
`
`8.1.1.1
`
`Input message: makeCallRequest
`
`Part name
`callingParty
`calledParty
`charging
`
`
`Optional
`Part type
`No
`xsd:anyURI
`No
`xsd:anyURI
`common:ChargingInformation Yes
`
`Description
`It contains the address of the first user involved in the call
`It contains the address of the second user involved in the call
`Charge to apply to the call
`
`8.1.1.2
`
`Output message : makeCallResponse
`
`Part name
`result
`
`
`Part type
`xsd:string
`
`Optional
`No
`
`Description
`It identifies a specific call request
`
`8.1.1.3
`
`Referenced faults
`
`ServiceException from ES 202 391-1 [2]:
`•
`•
`
`SVC0002 - Invalid input value.
`
`SVC0001 - Service error.
`
`PolicyException from ES 202 391-1 [2]:
`•
`•
`
`POL0001 - Policy error.
`
`POL0008 - Charging not supported.
`
`8.1.2 Operation: getCallInformation
`
`The invocation of getCallInformation retrieves the current status, callInformation, of the call identified by
`CallIdentifier. This method can be invoked multiple times by the application even if the call has already ended.
`However, after the call has ended, status information will be available only for a limited period of time that is specified
`in the service policy "StatusRetentionTime".
`
`8.1.2.1
`
`Input message: getCallInformationRequest
`
`Part name
`callIdentifier
`
`
`Part type
`xsd:string
`
`Optional
`No
`
`Description
`It identifies a specific call request
`
`8.1.2.2
`
`Output message : getCallInformationResponse
`
`Part name
`result
`
`
`Part type
`CallInformation
`
`Optional
`No
`
`Description
`It identifies the status of the call
`
`8.1.2.3
`
`Referenced faults
`
`ServiceException from ES 202 391-1 [2]:
`•
`•
`
`SVC0002 - Invalid input value.
`
`SVC0001 - Service error.
`
`ETSI
`
`TELESIGN EX1008
`Page 9
`
`

`

`
`
`
`10
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`PolicyException from ES 202 391-1 [2]:
`•
`
`POL0001 - Policy error.
`
`8.1.3 Operation: endCall
`
`The invocation of endCall terminates the call identified by callIdentifier. If the call is still in the initial state this
`method has the same effect as the cancelCall operation.
`
`8.1.3.1
`
`Input message: endCallRequest
`
`Part name
`callIdentifier
`
`
`Part type
`xsd:string
`
`Optional
`No
`
`Description
`It identifies a specific call request
`
`8.1.3.2
`
`Output message: endCallResponse
`
`Part name
`None
`
`
`
`
`Part type
`
`Optional
`
`
`
`
`
`8.1.3.3
`
`Referenced faults
`
`Description
`
`ServiceException from ES 202 391-1 [2]:
`•
`•
`•
`
`SVC0001 - Service error.
`
`SVC0002 - Invalid input value.
`
`SVC0261 - Call already terminated.
`
`PolicyException from ES 202 391-1 [2]:
`•
`
`POL0001 - Policy error.
`
`8.1.4 Operation: cancelCall
`
`The invocation of cancelCall cancels the previously requested call identified by callIdentifier. Note that this method
`differs from the endCall operation since it only attempts to prevent the call from starting but it does not have any effect
`if the call has already started.
`
`8.1.4.1
`
`Input message: cancelCallRequest
`
`Part name
`callIdentifier
`
`
`Part type
`xsd:string
`
`Optional
`No
`
`Description
`It identifies a specific call request
`
`8.1.4.2
`
`Output message: cancelCallResponse
`
`Part name
`None
`
`
`
`
`Part type
`
`Optional
`
`
`
`
`
`Description
`
`ETSI
`
`TELESIGN EX1008
`Page 10
`
`

`

`
`
`
`11
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`8.1.4.3
`
`Referenced faults
`
`ServiceException from ES 202 391-1 [2]:
`•
`•
`•
`
`SVC0001 - Service error.
`
`SVC0002 - Invalid input value.
`
`SVC0260 - Call already connected.
`
`PolicyException from ES 202 391-1 [2]:
`•
`
`POL0001 - Policy error.
`
`Fault definitions
`9
`The following faults are defined for this service.
`
`9.1
`
`ServiceException
`
`9.1.1
`
`SVC0260: Call already connected
`
`Part name
`messageId
`text
`variables
`
`SVC0260
`Call has already been connected, it cannot be cancelled
`None
`
`Description
`
`
`
`9.1.2
`
`SVC0261: Call already terminated
`
`Part name
`messageId
`text
`variables
`
`
`
`SVC0261
`Call has already been terminated
`None
`
`Description
`
`Service policies
`10
`These service policies are defined for the Third Party Call service.
`
`Name
`ChargingAllowed
`StatusRetentionTime
`
`
`Type
`xsd:boolean
`xsd:int
`
`Description
`Is charging allowed for makeCall operation
`Length of time, in seconds, to retain status after the termination of the call
`
`ETSI
`
`TELESIGN EX1008
`Page 11
`
`

`

`
`
`
`12
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`Annex A (normative):
`WSDL for Third Party Call
`The document/literal WSDL representation of this interface specification is compliant to ES 202 391-1 [2] and is
`contained in text files (contained in archive es_20239102v010201p0.zip) which accompany the present document.
`
`ETSI
`
`TELESIGN EX1008
`Page 12
`
`

`

`
`
`
`13
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`Annex B (informative):
`Bibliography
`ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications
`System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905)".
`
`ETSI
`
`TELESIGN EX1008
`Page 13
`
`

`

`
`
`
`14
`
`ETSI ES 202 391-2 V1.2.1 (2006-12)
`
`History
`
`V1.1.1
`
`V1.2.1
`
`V1.2.1
`
`
`
`
`
`
`
`Document history
`
`March 2005
`
`Publication
`
`October 2006 Membership Approval Procedure MV 20061215: 2006-10-17 to 2006-12-15
`
`December 2006 Publication
`
`
`
`
`
`
`
`
`
`ETSI
`
`TELESIGN EX1008
`Page 14
`
`

`

`1, Christian Loyau, declare:
`
`1.
`
`I make this declaration based upon my personal knowledge. I am over the age of
`
`21 and am competent to make this declaration.
`
`2.
`
`I am a Legal Affairs and Governance Services Director at
`
`the European
`
`Telecommunications Standards Institute ("ETSI"). My business address is 650 route des Lucioles,
`
`F 06921 Sophia Antipolis France.
`
`3.
`
`I began working at ETSI in January 2013 and have been the Legal Affairs Director
`
`at ETSI since 2013.
`
`4.
`
`5.
`
`6.
`
`ETSI is a neutral third party to the dispute in the current IPR.
`
`Neither I nor ETSI itself is being compensated for this declaration.
`
`As part of its ordinary course of business ETSI publishes and makes available
`
`technical articles and standards. All technical articles and standards ever produced may be
`
`purchased by the public on DVDs via ETSI’s WEBstore and/or publicly searched and freely
`
`downloaded at www.ctsi.org.
`
`7.
`
`ETSI maintains records of the articles and standards and the dates on which they
`
`were first published. I have personal knowledge of these records. These records are maintained as
`
`part of the ordinary course of business of ETSI.
`
`'8.
`
`To the best ofmy knowledge, the attached ETSI Standards 202 391—1 v1.2.1 — 202
`
`39 l -12 v l .2. l, which are attached to this Declaration, represent a true and correct copy ofthe Open
`
`Service Access (OSA) Parlay X Web Services, ETSI Standards 202 391-1 v1.2.1 — 202 391—12
`
`v1.2.1. This document is maintained and kept in the course of our regularly conducted activity of
`
`ETSI. The preparation of this document is a regular practice of ETSI.
`
`TELESI%X1008
`Page 15
`
`TELESIGN EX1008
`Page 15
`
`

`

`9.
`
`Based on my review of ETSI' s records, the ETSI Standards 202 391-1 v1.2.1 — 202
`
`391-12 v1.2.1, were published and available to the public as of December 12, 2006 without
`
`restrictions, in print and digital formats. The records that inform my knowledge were made at or
`
`near the time the Open Service Access (OSA) Parlay X Web Services, ETSI Standards 202 391-1
`
`v1.2.1 - 202 391-12 v1.2.1 were published, they were kept in the course of a regularly conducted
`
`activity of ETSI, and making the records was a regular practice of ETSI.
`
`10.
`
`A true and correct copy of a screenshot of search-results for the above standards at
`
`www.ETSI.com, indicating the date they were published and that they are currently available for
`
`download, is attached as Appendix A.
`
`11.
`
`I declare that all statements made herein of my own knowledge are true and that all
`
`statements made on information and belief are believed to be true and further that these statements
`
`were made with the knowledge that willful false statements and the like so made are punishable
`
`by fine or imprisonment, or_ both, under 18 USC § 1001, and that such willful false statements may
`
`jeopardize the validity of these proceedings.
`
`Dated: MAY—g4?
`
`«=1; ' his.
`Christian L—oyal,
`_
`Legal Affairs and Governance Services Director
`
`
`
`' ETSI
`650 route des Lucioles
`
`F-06921 Sophia Antipolls Cedex
`
`- FRANCE 42 10
`Tel: +33 4 92 94'
`
`Siret N’ 348 623 562 00017 - MAP 7420
`
`I
`K
`I:
`
`
`
`
`
`
`TELESIGN EX1008
`
`Page 16
`
`TELESIGN EX1008
`Page 16
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`APPENDIX A
`APPENDIX A
`
`EEEEEEEEEEEEEE
`
`TELESIGN EX1008
`Page 17
`
`

`

`
`C l (D www.etsiorg/standardsisearchitpage=1&search=es 202 39172&title=1&etsiNumber=1&c0ntent:0&version=1&onApproval=1&published=1&historica|=1&st
`For quick access, place your bookmarks here on the bookmarks bar. Import bookmarks now...
`
`6
`- Apps
`
`
`Search 81 Browse Standards
`
`es 202 39172
`
`Filter search results
`
`Sta '1 do rds
`
`[3
`
`C1
`
`SEARCH TERM
`
`es 202 391—21
`SEARCH IN
`
`l?! Title
`[Z ETSI number
`El Content
`
`VERSION ,l' STATUS
`L.) All versions
`
`0 Major versions only
`
`
`
`There are l resulls
`
`Sort By Date published V
`
`published
`351 ES 202 39172 V1.2.1 (2006712)
`Open Service Access (GSA); Parlay X Web Services; Part 2: Third Party Call
`(Parlay X 2)
`
`a E
`
`[E On Approval I
`E published -
`El Historical I
`FILTER EN,r RESE!’
`Published from
`
`
`11/1512II6
`Published to
`61f23l2867
`Select Keywords
`X.31
`
`
`
`
`
`A
`
`TELESIGN EX1008
`
`Page 18
`
`TELESIGN EX1008
`Page 18
`
`