ETSI TS 122 127-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Service requirement for the Open Services Access (O_1.pdf

1、 ETSI TS 122 127 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Service requirement for the Open Services Access (OSA);Stage 1 (3GPP TS 22.127 version 9.0.0 Release 9)ETSI ETSI TS 122 127 V9.0.0 (201

2、0-01)13GPP TS 22.127 version 9.0.0 Release 9Reference RTS/TSGS-0122127v900 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 00017 - NAF 742 C Association but non lucratif enregistre la Sous-

3、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 case of existing or perceived difference in contents between suc

4、h 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 subjec

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

6、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 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM,

7、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 ETSI currently being registered for the benefit of its Members

8、 and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 122 127 V9.0.0 (2010-01)23GPP TS 22.127 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially essential to the present document may hav

9、e 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 standa

10、rds“, 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 othe

11、r 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 Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to t

12、echnical 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 identities can be found under http:/webapp.etsi.org/key/quer

13、yform.asp. ETSI ETSI TS 122 127 V9.0.0 (2010-01)33GPP TS 22.127 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33

14、.2 Abbreviations . 8g34 General Description of OSA 8g35 The role of OSA within the VHE framework for services . 8 g35.1 Physical location of applications using the OSA interface . 9g36 High level requirements to OSA 9g37 Void . 10g38 Charging requirements . 10g39 Requirements on interfaces at differ

15、ent levels of abstractions . 11g310 Security and Privacy requirements . 11g310.1 Security requirements on User Profile Management 11g310.2 Privacy requirements on Subscriber Identity 12g310.3 Topology hiding . 12g311 Requirements for Policy Management . 12g312 Event Notification Function . 12g312.1

16、Subscriber Related events: . 13g312.2 Network Related Events: 14g312.3 Other Related Events: . 14g313 Functions offered by OSA 14g313.1 The Framework functions 15g313.1.1 Trust and Security Management . 15g313.1.1.1 Authentication . 15g313.1.1.2 Authorisation . 15g313.1.1.3 Policy for service capabi

17、lity features access and usage 16g313.1.2 Service Registration feature 16g313.1.3 Service De-Registration function . 16g313.1.4 Service Discovery feature . 16g313.1.5 Integrity Management function. 16g313.1.5a Service Subscription function . 17g313.1.6 APIs Usage Accounting 17g313.1.7 Support for Id

18、entity Management Framework 17g313.2 Network functions 17g313.2.1 Call and Session Control functions . 17g313.2.1.1 CS Call Control functions 17g313.2.1.2 PS Session Control functions . 18g313.2.1.3 IM Session Control functions 19g313.2.2 Void 20g313.2.3 Void 20g313.2.4 Charging functions 20g313.2.5

19、 Void 21g3ETSI ETSI TS 122 127 V9.0.0 (2010-01)43GPP TS 22.127 version 9.0.0 Release 913.2.6 QoS management functions 21g313.3 User data related functions . 21g313.3.1 User Status functions 21g313.3.2 User Location functions 22g313.3.3 Void 23g313.3.4 Void 23g313.3.5 Terminal Capabilities functions

20、23g313.3.6 Void 23g313.4 Void 23g313.5 Presence related capability functions . 23g313.5.1 Relationship to Release 6 Presence Service 23g313.5.2 Functions 23g313.5.3 Presence Compatibility . 24g313.6 Void 24g313.7 Multimedia Messaging function . 24g313.8 Content Management function . 24g314 Service B

21、rokering Function 25g3Annex A (informative) : Use cases . 26g3A.1 Travel support and information service 26g3A.2 Void 27g3A.3 Access to SCFs in another network 27g3Annex B (informative): Change history . 29g3History 33g3ETSI ETSI TS 122 127 V9.0.0 (2010-01)53GPP TS 22.127 version 9.0.0 Release 9Fore

22、word This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be

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

24、d 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. ETSI ETSI TS 122 127 V9.0.0 (2010-01)63GPP TS 22.127 version 9.0.0 Release 91 Scope This d

25、ocument specifies the stage 1 requirements for realisation of an Open Service Access (OSA). OSA enables applications to make use of network functionality through an open standardised interface (the OSA API). OSA provides the glue between applications and network functionality. In this way applicatio

26、ns implementing the services become independent from the underlying network technology. Applications which make use of network functionality offered through the OSA interface are not standardised by 3GPP. The network functionality offered through the OSA interface may or may not be standardised by 3

27、GPP. OSA is one toolkit, amongst others, that enables certain aspects of the requirements of the Virtual Home Environment (VHE) concept to be realised. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. Refere

28、nces are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM do

29、cument), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 2.1 Normative references 1 Void 2 3GPP TS 22.101: “Service principles“. 3 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 4 3GPP TS 23.107: “QoS Concept and A

30、rchitecture“. 5 3GPP TS 22.024: “Description of Charge Advice Information (CAI)“. 6 3GPP TS 29.198: “Open Service Architecture; Application Programming Interface“. 7 3GPP TS 22.141: “Presence Service Stage 1“. 8 3GPP TS 22.228: “IP Multimedia Subsystem (IMS) Stage 1“. 9 3GPP TS 22.071: “Location Ser

31、vices (LCS) Stage 1“. 10 3GPP TS 29.240: 3GPP Generic User Profile (GUP); Stage 3; Network 2.2 Informative references 10 World Wide Web Consortium Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation (www.w3.org) ETSI ETSI TS 122 127 V9.0.0 (2010-01)73GPP T

32、S 22.127 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Access Rules: For the definition see 7. Applications: software components providing services to users by utilising service capability f

33、eatures. Application Interface: standardised Interface used by applications to access service capability features. Availability: a property of a user denoting his/her ability and willingness to communicate based on factors such as the identity or properties of the requester of the information and th

34、e preferences and/or policies that are associated with the user. This property may be computed through information available from various capabilities within the network including (but not necessarily) the presence service. Call: A logical association between several users pertaining to the CS CN do

35、main Charging: A function whereby information related to a chargeable event is formatted and transferred in order to make it possible to determine usage for which the charged party may be billed. HE-VASP: Home Environment Value Added Service Provider. For the definition see 3 Home Environment: For t

36、he definition see 3 IM : IP Multimedia. For definition see 8 IM Session: For definition see 8 Local Service: For the definition see 3 Personal Service Environment: For the definition see 3 Policy: is a formalism that may be used to express business, engineering or management criteria. A policy is re

37、presented by a set of rules. Rules are expressed as condition(s)-actions(s) pairs. When the conditions associated with a rule are satisfied the associated actions are executed. Note: Policies created by applications are matched against the policies of a Network. Policy Event : A policy event is asso

38、ciated with the action part of designated rule(s). The event is generated when the action part is executed. Policy Management: is the capability to create, modify and delete policy related information, including policy events. Policy Enabled Service: is a Service which has some or all of its propert

39、ies expressed in terms of policy rules. E.g. Charging Service wherein charging criteria are expressed in terms of policy rules Policy Decision Point: A function of the network where the applicable policy is chosen. Policy Enforcement Point: A function of the network where the chosen policy is applie

40、d. Policy Repository: A function of the network where policies are stored. Policy Enabled network: is a network that supports at least one instance of a Policy Repository and Policy Decision Point and Policy Enforcement Point. Presence Service: For the definition see 7. Presence Information: For the

41、 definition see 7. Presence Entity (presentity): For the definition see 7. Service Capabilities: bearers defined by parameters, and/or mechanisms needed to realise services. These are within networks and under network control. ETSI ETSI TS 122 127 V9.0.0 (2010-01)83GPP TS 22.127 version 9.0.0 Releas

42、e 9Service Capability Feature: functionality offered by service capabilities that are accessible via the standardised application interface. Service Provider: an organisation which delivers services to the subscriber. This can be e.g. the operator of the subscribers Home Environment or an authorised

43、 VASP. Note: In the context of this specification it is assumed, that at least one application providing the services of the Service Provider makes use of OSA functions Services: a service is the user experience provided by one or more applications. User: For the definition see 3 Virtual Home Enviro

44、nment: For the definition see 3 Watcher: For the definition see 7. Watcher Information: For the definition see 7. Further 3G related definitions are given in 3G TR 21.905 3. 3.2 Abbreviations For the purposes of this TS the following abbreviations apply: API Application Programming Interface CAMEL C

45、ustomised Application For Mobile Network Enhanced Logic HE Home Environment PS Packet SwitchedPSE Personal Service Environment VHE Virtual Home Environment OSA Open Service Access SCF Service Capability Feature MExE Mobile Execution Environment Further 3G related abbreviations are given in 3G TS 21.

46、905 3. 4 General Description of OSA In order to be able to implement future applications/end user services that are not yet known today, a highly flexible Framework for Services is required. The Open Service Access (OSA) enables applications implementing the services to make use of network functiona

47、lity. Network functionality offered to applications is defined in terms of a set of Service Capability Features (SCFs). These SCFs provide functionality of network capabilities which is accessible to applications through the standardised OSA interface upon which service developers can rely when desi

48、gning new services (or enhancements/variants of already existing ones). The aim of OSA is to provide a standardised, extensible and scalable interface that allows for inclusion of new functionality in the network with a minimum impact on the applications using the OSA interface. 5 The role of OSA wi

49、thin the VHE framework for services The goal of standardisation in 3GPP with respect to services is to provide a framework within which services can be created based on standardised service capability features. 3GPP services will generally not rely on the traditional detailed service engineering (evident for supplementary services in second-generation systems), but instead provides services using generic toolkits. OSA is one of these toolkits, standardised within 3GPP, for the support of services within 3GPP syst