1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommSubscription Ma(3GPP TS 32.1TECHNICAL SPECIFICATION132 141 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; M nagement (SuM) architectu.141 version 13.0.0 Release 1316-02) hase 2+); (UMTS); ture
2、13) ETSI ETSI TS 132 141 V13.0.0 (2016-02)13GPP TS 32.141 version 13.0.0 Release 13Reference RTS/TSGS-0532141vd00 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
3、 but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print vers
4、ions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a spe
5、cific 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 error
6、s in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm excep
7、t as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. D
8、ECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI 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 GS
9、M Association. ETSI ETSI TS 132 141 V13.0.0 (2016-02)23GPP TS 32.141 version 13.0.0 Release 13Intellectual 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
10、 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 (h
11、ttps:/ipr.etsi.org/). 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, es
12、sential 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 technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be inter
13、preted 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/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need no
14、t“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 141 V13.0.0 (2016-0
15、2)33GPP TS 32.141 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Subscription Management (SuM) archite
16、cture . 7g34.1 Functional entities 8g34.2 Interfaces 9g34.2.1 Application of Itf-N for SuM 9g34.2.2 Void 9g34.3 Overview of IRP . 9g34.3.1 IRP security 10g34.4 Methodology 10g34.4.1 SuM Stage 1 10g34.4.2 SuM Stage 2 10g34.4.3 SuM Stage 3 11g3Annex A (informative): Void . 12g3Annex B (informative): C
17、hange history . 13g3History 14g3ETSI ETSI TS 132 141 V13.0.0 (2016-02)43GPP TS 32.141 version 13.0.0 Release 13Foreword 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 a
18、nd 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 TSG for informati
19、on; 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 changes have been incor
20、porated in the document. Ready for Converged Management This specification is part of a set that has been developed for converged management solutions. Introduction The present document is part a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and Sys
21、tem Aspects; Telecommunication management, as identified below: TS 32.140: “Subscription Management (SuM) requirements“. TS 32.141: “Subscription Management (SuM) architecture“. TS 32.171: “Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements“. T
22、S 32.172: “Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. TS 32.176: “Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions“. TS 28.751: “Subscription Manag
23、ement (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements“. TS 28.752: “Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. TS 28.753: “Subscription Management (SuM) Network Resource Model (NRM) Integ
24、ration Reference Point (IRP); Solution Sets (SS) definitions“. The 3G environment requires more complex service delivery mechanisms and is no longer simply an internal matter for a single operator but a capability that is achieved by linking together features across multiple service providers and ET
25、SI ETSI TS 132 141 V13.0.0 (2016-02)53GPP TS 32.141 version 13.0.0 Release 13operators. Subscription Management (SuM) is a feature that permits Service Providers, Value Added Service Providers, and Mobile Operators to provision services for a specific subscriber. The feature is necessary to allow se
26、rvice providers and operators to provision, control, monitor and bill the configuration of services that they offer to their subscribers. For further details see 3GPP TS 32.140 5 on SuM requirements that gives an overview of SuM. ETSI ETSI TS 132 141 V13.0.0 (2016-02)63GPP TS 32.141 version 13.0.0 R
27、elease 131 Scope The present document defines the architecture for Subscription Management (SuM) , including Converged Management of fixed and mobile networks. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document
28、. References 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
29、a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.002: “Network Architecture“. 3 3GPP TS 32.101: “Telecommunication management; Principle
30、s and high level requirements“. 4 3GPP TS 32.102: “Telecommunication management; Architecture“. 5 3GPP TS 32.140: “Telecommunication management; Subscription Management (SuM) requirements“. 6 3GPP TS 23.008: “Organization of subscriber data“. 7 3GPP TS 32.150: “Integration Reference Point (IRP) Conc
31、ept and definitions“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: subscriber: See 3GPP TR 21.905 1. service: See 3GPP TR 21.905 1. Integration Reference Point (IRP): See 3GPP TS 32.101 3. user: See 3GPP TR 21.90
32、5 1. subscription: See 3GPP TR 21.905 1. Subscription Management (SuM): See 3GPP TR 32.140 5. Subscription Profile: See 3GPP TR 32.140 5. Subscription Profile Component: See 3GPP TR 32.140 5. ETSI ETSI TS 132 141 V13.0.0 (2016-02)73GPP TS 32.141 version 13.0.0 Release 133.2 Abbreviations For the pur
33、poses of the present document, the following abbreviations apply: 2G Second Generation Mobile 3G Third Generation Mobile API Application Programming Interface ASP Application Service Provider AuC Authentication Center B2B Business to Business CS Circuit Switch EIR Equipment Identity Register GTT Glo
34、bal Text Telephony GUP Generic User Profile HE Home EnvironmentHLR Home Location Register HSS Home Subscriber Server IMS IP Multimedia Subsystem IRP Integration Reference Point (3GPP TS 32.102 4) ISP Internet Service Provider NPDB Number Portability Data Base NRM Network Resource Model OAM Operation
35、s, Administration and Maintenance OSA Open Services Access OSF Operations System Functions OSS Operations Support System PS Packet Switch SLA Service Level Agreement SM&O Service Management and Operations (TMF/ITU-T) SP Service Provider SuM Subscription Management TMN Telecommunication Management Ne
36、twork TR-IRP Trading Partner IRP UICC Universal Integrated Circuit Card USIM Universal Subscriber Identity Module VASP Value Added Service Provider VHE Virtual Home Environment VNO Virtual Network Operator 4 Subscription Management (SuM) architecture 3G Telecommunication Management focuses on the mo
37、st important and strategic contexts in the physical architecture for the management of UMTS. The framework to help define a telecom management physical architecture for a planned UMTS and to adopt standards and provide products that are easy to integrate is defined in 3GPP TS 32.102 4. SuM manages S
38、ubscription Profile Components stored in network resources for the purpose of providing services to specific subscribers. This is done with an architecture that is consistent with the one specified in 3GPP TS 32.102 4. Subscription Profiles represent services and are associated to subscribers that e
39、mploy these services (3GPP TS 32.140 5). To the extent the HSS controls certain services, Subscription Profile Components can be associated with the HSS. Other services, and as a result Subscription Profiles Components, are outside the jurisdiction of the HSS. ETSI ETSI TS 132 141 V13.0.0 (2016-02)8
40、3GPP TS 32.141 version 13.0.0 Release 134.1 Functional entities Functional entities belonging to SuM are described in Figure 1. The figure also contains the actors related to Subscriptions. Figure 1: Functional entities in SUM Actors described in Figure 1 are: Subscriber (definition See TS 21.905) U
41、ser (definition See TS 21.905) Service Provider (definition See TS 21.905) PLMN Operator (definition See TS 21.905) The entities described in Figure 1 are: Subscription Profile (definition See TS 32.140) Subscription Profile Component (definition See TS 32.140) Service (definition See TS 21.905) Sys
42、tem (definition See TS 32.102) Service Preferences: Contains the service preferences chosen for a user. Each user configures his preferences for a particular subscribed service, but only within the limits defined by the Subscription. Clarifications to the figure: A PLMN Operator/Service Provider has
43、 one or several Services to offer for Subscribers. A Subscriber has one or several Subscription Profiles, where each describes an offered Service. A User has one or several Service Preferences, where each describes the user“s chosen preferences for the service. SubscriberServiceSubscription Profile
44、ServicePreferencesSubscriptionProfile ComponentDefines10n 1PLMN operator/Service Provider1 UserHasHasHasConsists ofRefers to0n 0n HasSystem Resides in0n 11 0n 0n 1Has110n0nSM&O mapping of information entities ETSI ETSI TS 132 141 V13.0.0 (2016-02)93GPP TS 32.141 version 13.0.0 Release 13 A Subscript
45、ion Profile may consist of one or several Subscription Profile Components. A Subscription Profile may define one or several Service Preferences. A Subscription Profile Component resides in one or several systems Subscriptions are managed in the form of Subscription profile components, which may be d
46、istributed across Service Management & Operations (SM&O), Network Resource Management & Operations (RM&O) and Network Domains. There may also be mappings among the SM&O, RM&O and Network Domains. 4.2 Interfaces 4.2.1 Application of Itf-N for SuM OSF User Equipment Domain OSF for Network Management a
47、nd Service Management Itf-N NE Management OSF Access Network Domain OSF Core network Service Specific entities OSF Core Network Basic Entities Domain Common CN Domain CS Domain PS (GPRS) Domain Figure 2: Overview of PLMN Telecom Management Domains and Itf-N (3GPP TS 32.102 4) The Itf-N for SuM is re
48、alized by means of an Integration Reference Point (IRP) as defined in 3GPP TS 32.102 4. Operations System Functions (OSF) functionality can be realized in NEs or in the NE Management systems. SuM, for this release, is concerned with the OSF functionality contained in the Core Network Basic Entities
49、Domain and specifically that of the Common CN Domain. Subscription Profile Components are located in the NEs OSFs within the Common CN Domain or their NEs OSFs in the NE management systems, and are in either case accessed consistent with the IRP concept. SuM OSFs for Network Management and Service Management are located in network- and service management systems. 4.2.2 Void 4.3 Overview of IRP Figures 3 and 4 identify system contexts of the IRP in terms of its implementation, called IRPAgent (
