ETSI TR 129 998-4-4-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi_1.pdf

1、 ETSI TR 129 998-4-4 V9.0.0 (2010-01)Technical Report Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA);Application Programming Interface (API)Mapping for Open Service Access;Part 4: Call Control Service Mapping;Subp

2、art 4: Multiparty Call Control ISC (3GPP TR 29.998-04-4 version 9.0.0 Release 9)ETSI ETSI TR 129 998-4-4 V9.0.0 (2010-01) 13GPP TR 29.998-04-4 version 9.0.0 Release 9 Reference RTR/TSGC-0029998-04-4v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.:

3、 +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made av

4、ailable 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

5、 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

6、 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

7、in all media. European Telecommunications Standards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Member

8、s and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 129 998-4-4 V9.0.0 (2010-01) 23GPP

9、TR 29.998-04-4 version 9.0.0 Release 9 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

10、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 ETS

11、I 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

12、 This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding

13、ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TR 129 998-4-4 V9.0.0 (2010-01) 33GPP TR 29.998-04-4 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 6g3I

14、ntroduction 6g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 10g34 Mapping OSA Call and Call Leg to SIP 10g34.1 Introduction 10g34.2 SIP Call-id 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control

15、. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction Structure of the OSA API Mapping (3GPP TR 29.998) The present do

16、cument is part 4, subpart 4, of a multi-part deliverable covering the Open Service Access (OSA); Application Programming Interface (API) Mapping for OSA. Table: Overview of the OSA APIs Application Programming Interface (API); Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for the Open Se

17、rvice Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TR 21.905: “Vocabulary for 3GPP specifications“. 5 3GPP TS 29.198-4-1/5: “Open Service Access (OSA); Application Programming Interface (API); Part 4: Call control; Sub-part 1: Call Control Common Definitions

18、“. Sub-part 2: Generic Call Control SCF“. Sub-part 3: “Multi-Party Call Control SCF“. Sub-part 4: “Multi-Media Call Control SCF“. Sub-part 5: “Conference call control SCF“. 6 3GPP TS 23.218: “IP Multimedia (IM) session handling; IP Multimedia (IM) call model; Stage 2“. 7 3GPP TS 22.101: “Service asp

19、ects; Service principles“. 8 3GPP TS 29.228 “ IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents“. 9 3GPP TR 29.998-1: “ Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 1: General Issues on API Mapping“. 1

20、0 IETF RFC 2806: “URLs for Telephone Calls“. 11 3GPP TS 23.228: “IP Multimedia Subsystem (IMS); Stage 2“. 12 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3“. 13 3GPP TS 24.228: “Signalling flows for the IP multimedia call control based on SIP and SDP; Stage 3“. ET

21、SI ETSI TR 129 998-4-4 V9.0.0 (2010-01) 83GPP TR 29.998-04-4 version 9.0.0 Release 9 14 RFC 3261: “SIP: Session Initiation Protocol“. 15 3GPP TS 29.328: “IP Multimedia Subsystem (IMS) Sh Interface signalling flows and message contents“. 16 RFC 3725: “Best Current Practices for Third Party Call Contr

22、ol (3pcc) in the Session Initiation Protocol (SIP)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 29.198-1 1, TS 23.228 11 and TS 24.228 13 and the following apply: Back-To-Back User Agent (B2BUA): logical entity that

23、 receives a request, and processes it as a UAS In order to determine how the request should be answered, it acts as a UAC and generates requests. Unlike a proxy server, it maintains dialog state, and must participate in all requests sent on the dialogs it has established. Since it is a concatenation

24、 of a UAC and UAS, no explicit definitions are needed for its behaviour. call: informal term that refers to a dialog between peers, generally set up for the purposes of a multimedia conversation call leg: another name for a dialogue in a SIP context In an OSA context the communication path as seen f

25、rom an application to an addressable entity/call party in the network. call stateful: proxy which retains state for a dialog from the initiating INVITE to the terminating BYE request client: any network element that sends SIP requests, and receives SIP responses Clients may or may not interact direc

26、tly with a human user. User agent clients and proxies are clients. dialog: peer-to-peer SIP relationship between a UAC and UAS that persists for some time A dialog is established by SIP messages, such as a 2xx response to an INVITE request. A dialog is identified by a call identifier, local address,

27、 and remote address. downstream: direction of message forwarding within a transaction which refers to the direction that requests flow from the user agent client to user agent server final response: response that terminates a SIP transaction, as opposed to a provisional response that does not All 2x

28、x, 3xx, 4xx, 5xx and 6xx responses are final. informational response: provisional response initiator, calling party, caller: The party initiating a session with an INVITE request. A caller retains this role from the time it sends the INVITE until the termination of any dialogs established by the INV

29、ITE. invitation: INVITE request. invitee, invited user, called party, callee: party that receives an INVITE request for the purposes of establishing a new session. A callee retains this role from the time it receives the INVITE until the termination of the dialog established by that INVITE. location

30、 server: See location service. location service: service is used by a SIP redirect or proxy server to obtain information about a callees possible location(s) It is an abstract database, sometimes referred to as a location server. The contents of the database can be populated in many ways, including

31、being written by registrars. method: primary function that a request is meant to invoke on a server The method is carried in the request message itself. Example methods are INVITE and BYE. ETSI ETSI TR 129 998-4-4 V9.0.0 (2010-01) 93GPP TR 29.998-04-4 version 9.0.0 Release 9 outbound proxy: proxy th

32、at receives all requests from a client, even though it is not the server resolved by the Request-URI The outbound proxy sends these requests, after any local processing, to the address indicated in the Request-URI, or to another outbound proxy. parallel search: In a parallel search, a proxy issues s

33、everal requests to possible user locations upon receiving an incoming request. Rather than issuing one request and then waiting for the final response before issuing the next request as in a sequential search , a parallel search issues requests without waiting for the result of previous requests. pr

34、ovisional response: response used by the server to indicate progress, but that does not terminate a SIP transaction 1xx responses are provisional, other responses are considered final. proxy, proxy server: intermediary entity that acts as both a server and a client for the purpose of making requests

35、 on behalf of other clients A proxy server primarily plays to role of routing, which means its job is to ensure that a request is passed on to another entity that can further process the request. Proxies are also useful for enforcing policy and for firewall traversal. A proxy interprets, and, if nec

36、essary, rewrites parts of a request message before forwarding it. redirect server: server that accepts a SIP request, maps the address into zero or more new addresses and returns these addresses to the client Unlike a proxy server, it does not initiate its own SIP request. Unlike a user agent server

37、, it does not accept calls. registrar: server that accepts REGISTER requests, and places the information it receives in those requests into the location service for the domain it handles sequential search: in a sequential search, a proxy server attempts each contact address in sequence, proceeding t

38、o the next one only after the previous has generated a non-2xx final response server: network element that receives requests in order to service them, and sends back responses to those requests Examples of servers are proxies, user agent servers, redirect servers, and registrars. session: From the S

39、DP specification: “A multimedia session is a set of multimedia senders and receivers and the data streams flowing from senders to receivers. A multimedia conference is an example of a multimedia session.“ (see RFC 2327 6) (A session as defined for SDP can comprise one or more RTP sessions.) As defin

40、ed, a callee can be invited several times, by different calls, to the same session. If SDP is used, a session is defined by the concatenation of the user name , session id , network type , address type and address elements in the origin field. (SIP) transaction: transaction which occurs between a cl

41、ient and a server and comprises all messages from the first request sent from the client to the server up to a final (non-1xx) response sent from the server to the client, and the ACK for the response in the case the response was a 2xx The ACK for a 2xx response is a separate transaction. spiral: SI

42、P request which is routed to a proxy, forwarded onwards, and arrives once again at that proxy, but this time, differs in a way which will result in a different processing decision than the original request Typically, this means that it has a Request-URI that differs from the previous arrival. A spir

43、al is not an error condition, unlike a loop. stateless proxy: logical entity that does not maintain the client or server transaction state machines defined in this specification when it processes requests A stateless proxy forwards every request it receives downstream and every response it receives

44、upstream. stateful proxy: logical entity that maintains the client and server transaction state machines defined by this specification during the processing of a request Also known as a transaction stateful proxy A stateful proxy is not the same as a call stateful proxy. upstream: direction of messa

45、ge forwarding within a transaction which refers to the direction that responses flow from the user agent server to user agent client User Agent Client (UAC): A user agent client is a logical entity that creates a new request, and then uses the client transaction state machinery to send it. The role

46、of UAC lasts only for the duration of that transaction. In other words, if a piece of software initiates a request, it acts as a UAC for the duration of that transaction. If it receives a request later on, it takes on the role of a User Agent Server for the processing of that transaction. ETSI ETSI

47、TR 129 998-4-4 V9.0.0 (2010-01) 103GPP TR 29.998-04-4 version 9.0.0 Release 9 User Agent Server (UAS): logical entity that generates a response to a SIP request The response accepts, rejects or redirects the request. This role lasts only for the duration of that transaction. In other words, if a pie

48、ce of software responds to a request, it acts as a UAS for the duration of that transaction. If it generates a request later on, it takes on the role of a User agent client for the processing of that transaction. User Agent (UA): logical entity which can act as both a user agent client and user agen

49、t server for the duration of a dialog user: logical, identifiable entity which uses services In a SIP context it encompasses a User Agent (UA). 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Mapping OSA Call and Call Leg to SIP 4.1 Introduction In the MPCCS the CallSessionID designates the call as seen from the application, i.e. the ID used to identify a call session. The MPCC API uses this callSessionID to identify a call session. In SIP, a SIP dialogue (or call) is identi