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

《ETSI TR 129 998-1-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programming.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 129 998-1-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programming.pdf（11页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 129 998-1 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 OSA;Part 1: General issues on API mapping (3GPP TR 29.998-01 v

2、ersion 9.0.0 Release 9)ETSI ETSI TR 129 998-1 V9.0.0 (2010-01)13GPP TR 29.998-01 version 9.0.0 Release 9Reference RTR/TSGC-0029998-01v900 Keywords GSM, LTE, UMTS 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 000

3、17 - 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 available in more than one electronic version or in print. In any c

4、ase 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 p

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

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

7、0. 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 Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of

8、 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-1 V9.0.0 (2010-01)23GPP TR 29.998-01 version 9.0.0 Release 9Intellectual Property Rights IPR

9、s 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 po

10、tentially 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 carrie

11、d 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 Technical Report (TR) has been produced by ETSI 3rd Generation Pa

12、rtnership 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 ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI

13、 identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TR 129 998-1 V9.0.0 (2010-01)33GPP TR 29.998-01 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6

14、g33.1 Definitions 6g33.2 Abbreviations . 6g34 Overview of the Mapping Report TR 29.998 . 7g34.1 Structure of TR 29.998 . 7g34.2 Context of the Mapping 7g35 General Parameter Mapping Issues 8g35.1 API Parameters that do not require a mapping . 8g35.2 Protocol Operation Parameters that do not require

15、a mapping . 8g3Annex A: Change history 9g3History 10g3ETSI ETSI TR 129 998-1 V9.0.0 (2010-01)43GPP TR 29.998-01 version 9.0.0 Release 9Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work

16、 within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to

17、TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. 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 change

18、s have been incorporated in the document. Introduction Structure of the OSA API Mapping (3GPP TR 29.998) The Technical Report 3GPP TR 29.998 consists of a series of parts and subparts. An effort has been made to ensure that the part numbers used in the mapping TR correspond to the part numbers of th

19、e base OSA specification in 3GPP TS 29.198. For this reason, certain parts, for which no suitable mapping could be suggested, have not been delivered. At a later stage a mapping to a new protocol may become evident, in which case these missing parts will be developed. The OSA specification was defin

20、ed jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group. The 3GPP TR 29.998 is based on a mapping document with a wider scope, developed as part of this co-operation. Certain mappings defined in the course of this joint development are not applicable for the present 3GPP Release, which

21、is why not all sub-parts have been delivered as part of the present 3GPP Release. However, it is expected that some may become applicable within the scope of later 3GPP Releases, which is why a common sub-part numbering is being retained, albeit with gaps for the present 3GPP Release. If mapping for

22、 a certain Part is “Not Applicable“ it can either indicate that a mapping does not exist (e.g. Part 2: Common Data), or the API is considered to be implemented directly on a physical entity, or via a proprietary mechanism. The present document is part 1 of a multi-part deliverable covering the Open

23、Service Access (OSA); Application Programming Interface (API) Mapping for OSA. ETSI ETSI TR 129 998-1 V9.0.0 (2010-01)53GPP TR 29.998-01 version 9.0.0 Release 9Table: Overview of the OSA APIs Application Programming Interface (API); Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for the O

24、pen Service Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 6 3GPP TS 29.002: “Mobile Application Part (MAP) specification“. 7 3GPP TS 29.078: “Customised Applications for Mobile network Enhanced Logic (CAMEL); C

25、AMEL Application Part (CAP) specification“. 8 3GPP TS 22.101: “Service Aspects; Service Principles“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 29.198-1 1 apply. 3.2 Abbreviations For the purposes of the presen

26、t document, the abbreviations given in 3GPP TS 29.198-1 1 apply. ETSI ETSI TR 129 998-1 V9.0.0 (2010-01)73GPP TR 29.998-01 version 9.0.0 Release 94 Overview of the Mapping Report TR 29.998 4.1 Structure of TR 29.998 The TR 29.998 consists of a series of parts and subparts. An effort has been made to

27、 ensure that the part numbers used in the mapping report correspond to the part numbers of the base OSA specification in TS 29.198. For this reason, certain parts, for which no suitable mapping could be suggested, have not been delivered. At a later stage a mapping to a new protocol may become evide

28、nt, in which case these missing parts will be developed. The OSA specification was defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group. The 3GPP TR 29.998 is based on a mapping document with a wider scope, developed as part of this co-operation. Certain mappings defined in the

29、course of this joint development are not applicable for the present 3GPP Release, which is why not all sub-parts have been delivered as part of the present 3GPP Release. However, it is expected that some may become applicable within the scope of later 3GPP Releases, which is why a common sub-part nu

30、mbering is being retained, albeit with gaps for the present 3GPP Release. 4.2 Context of the Mapping The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The applications cons

31、titute the top level of the architecture for Open Service Access (OSA). This level is connected to the Service Capability Servers (SCSs) via the OSA interface. The SCSs map the OSA interface onto the underlying telecommunications specific protocols (e.g. MAP, CAP, etc.) and are therefore hiding the

32、network complexity from the applications. The specific Service Capability Server (SCS) under consideration in the present document is the CAMEL Service Environment (CSE). In this case, the OSA API provides the operator or third party applications access to the CAMEL Application Part (CAP) protocol o

33、perations, via the OSA Interface Class methods. On the gsmSCF, the OSA Interface Class methods need to be mapped, or translated, onto the relevant CAP and/or MAP operations. Only the non-framework Service Capability Features (SCFs) will be taken into account for the mapping. The present document is

34、not exhaustive in covering all the mappings that can be expected. It provides several examples, but it should be noted that several other possibilities exist. In particular, only general cases of normal operations are covered and exception scenarios are not within the scope of the present document.

35、In addition to the configuration of SCS and CSE, the present document contains some recommendations for a configuration consisting of SCS and HLR. On the HLR, the OSA Interface Class methods need to be mapped, or translated, onto the relevant MAP protocol operations. The mappings contained in the pr

36、esent document for the SCS/HLR case are not intended to be exhaustive. ETSI ETSI TR 129 998-1 V9.0.0 (2010-01)83GPP TR 29.998-01 version 9.0.0 Release 95 General Parameter Mapping Issues 5.1 API Parameters that do not require a mapping A number of the API method parameters have significance only on

37、the OSA interface and in the SCS. They are used to identify objects implementing parts of the interface for instance. No mapping is required for these parameters. - appInterface: specifies a reference to the application object which implements the callback interface for a call; - assignmentID: speci

38、fies the assigned ID which is used to link associated requests and responses; - callReference: specifies the reference to the call object; - callSessionID: specifies the call session ID of the call object to which this method invocation applies. 5.2 Protocol Operation Parameters that do not require

39、a mapping A number of the CAP and MAP protocol operation parameters deal with the specifics of the underlying core network. these are typically those details that the OSA API was designed to abstract from and therefore do not require a mapping. Examples include: CAP InitialDP: - gsmSCFAddress; - MSC

40、Address; - GMSCAddress; - IPSSPCapabilities. MAP AnyTimeModification: - gsmSCFAddress. ETSI ETSI TR 129 998-1 V9.0.0 (2010-01)93GPP TR 29.998-01 version 9.0.0 Release 9Annex A: Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New Mar 2001 CN_11 NP-010131 011 - CR 29.998:

41、for moving TR 29.998 from R99 to Rel 4 (N5-010159) 3.2.0 4.0.0 Jun 2002 CN_16 - - - Automatically upgraded to Rel-5 (i.e. no change/CR). The overview of the enlarged 29.198/29.998-family was updated in the Introduction. 4.0.0 5.0.0 Dec 2004 CN_26 - - - Automatically upgraded to Rel-6 (i.e. no change

42、/CR). The overview of the enlarged 29.198/29.998-family was updated in the Introduction and clause 4. 5.0.0 6.0.0 Mar 2007 CT_35 - - - Automatic upgrade to R7 (no CR needed) 6.0.0 7.0.0 Dec 2008 CT_42 Upgraded unchanged from Rel-7 7.0.0 2009-12 - - - - Update to Rel-9 version (MCC) 8.0.0 9.0.0 ETSI ETSI TR 129 998-1 V9.0.0 (2010-01)103GPP TR 29.998-01 version 9.0.0 Release 9History Document history V9.0.0 January 2010 Publication