4 Subscription Management (SuM) architecture
32.1413GPPRelease 17Subscription Management (SuM) architectureTelecommunication managementTS
3G Telecommunication Management focuses on the most 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 Subscription 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 employ 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.
4.1 Functional entities
Functional entities belonging to SuM are described in Figure 1. The figure also contains the actors related to Subscriptions.
Subscriber
Subscriber
Service
Service
Subscription
Profile
Service
Preferences
Subscription
Profile
Component
Defines
1
0..n
1
PLMN operator/Service Provider
PLMN operator/Service Provider
1
User
User
Has
Has
Has
Consists of
Refers to
0..n
0..n
Has
System
Resides in
0..n
1
1
0..n
0..n
1
Has
1
1
0..n
0..n
SM&O mapping of information entities
Figure 1: Functional entities in SUM
Actors described in Figure 1 are:
– Subscriber (definition See TS 21.905)
– User (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)
– System (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 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.
– A Subscription 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 distributed 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
Figure 2: Overview of PLMN Telecom Management Domains and Itf-N (3GPP TS 32.102 [4])
The Itf-N for SuM is realized 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 Domain and specifically that of the Common CN Domain. Subscription Profile Components are located in the NEs OSF’s within the Common CN Domain or their NEs OSF’s in the NE management systems, and are in either case accessed consistent with the IRP concept. SuM OSF’s 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 (see 3GPP TS 32.150 [7]), and the user of the IRPAgent, called IRPManager (see 3GPP TS 32.150 [7]).
The IRPAgent implements and supports the Interface IRPs for SuM NRM IRP. The IRPAgent can reside in an Element Manager (EM) or a Network Element (NE) (3GPP TS 32.102 [4]). In the former case, the interface (represented by a thick dotted line) between the EM and the NEs is not the subject of the Interface IRPs for SuM NRM IRP.
An IRPManager using the Interface IRPs for SuM NRM IRP shall choose one of the two System Contexts defined here, for each NE. For instance, if an EM is responsible for managing a number of NEs, the NM shall access the Interface IRPs for SuM NRM IRP through the EM and not directly to those NEs.
The interface IRPs for SuM NRM IRP can be the following:
– Basic CM IRP
NEs
EM
IRPAgent
IRPManager
NM
Itf
–
N
SuM
IRP
NEs
EM
IRPAgent
IRPManager
NM
Itf
–
N
SuM
IRP
Interface IRPs for SuM NRM IRP
Figure 3: System Context A
Figure 4: System Context B
4.3.1 IRP security
The IRP interface is made secure by controlling access to the network and management systems. Operations processes must insure that only authorized personnel have the access authority to retrieve and alter SuM data. Standard protocols used over the interface between the IRPManager and the IRPAgent provide some degree of security. The exact nature of the security is described in the Solution Set for that protocol. In addition to the requirement that the IRPManager and the IRPAgent be secure, most physical links between them are secured as well.
4.4 Methodology
The methodology used to conclude the standard work for SuM shall follow the IRP methodology described in 3GPP TS 32.150 [4]. This subclause describes how to apply that methodology.
4.4.1 SuM Stage 1
SuM Stage 1 is documented in 3GPP TS 32.140 [5].
4.4.2 SuM Stage 2
SuM Stage 2 is documented as follows:
a) The present document (3GPP TS 32.141) is finalized by identifying the relevant IRPs.
b) 3GPP TS 32.171 (for non-converged management) and TS 28.751 (for converged management) define the Requirements for the SuM NRM IRP.
3GPP TS 32.171 and TS 28.751 shall, where applicable, follow the structure in 3GPP TS 32.621 (for non-converged management) and TS 28.621 (for converged management) (Generic NRM IRP: Requirements) , respectively.
c) 3GPP TS 32.172 (for non-converged management) and TS 28.752 (for converged management) describe the Information Service for the SuM NRM IRP – containing the Information Object Classes (IOCs), attributes, relations etc. for SuM.
3GPP TS 32.172 and TS 28.752 shall, where applicable, follow the structure in 3GPP TS 32.622 (for non-converged management) and TS 28.622 (for converged management) (Generic NRM IRP: Information Service) , respectively.
4.4.3 SuM Stage 3
SuM Stage 3 is documented in the following documents:
– TS 32.176 (for non-converged management) and TS 28.623 (for converged management) SuM NRM IRP: Solution Set definition s.
Annex A (informative): Void
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
Mar 2003 |
SA_19 |
SP-030042 |
— |
— |
Submitted to SA#19 as v1.0.0 for Information |
1.0.0 |
— |
|
Sep 2003 |
SA_21 |
SP-030405 |
— |
— |
Submitted to SA#21 as v2.0.0 for Approval |
2.0.0 |
6.0.0 |
|
Mar 2004 |
SA_23 |
SP-040108 |
0001 |
— |
Subscription Management TS-family (32.14x and 32.17x) title alignment ("SM" becomes "SuM" and delete "Services operations management") |
6.0.0 |
6.1.0 |
|
Jun 2007 |
SA_36 |
— |
— |
— |
Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. |
6.1.0 |
7.0.0 |
|
Dec 2008 |
SA_42 |
— |
— |
— |
Upgrade to Release 8 |
7.0.0 |
8.0.0 |
|
Sep 2009 |
SA_45 |
SP-090627 |
0002 |
— |
Align with TS 32.140 SuM requirements |
8.0.0 |
9.0.0 |
|
Mar 2011 |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.0.0 |
10.0.0 |
|
2012-09 |
– |
– |
– |
– |
Update to Rel-11 version (MCC) |
10.0.0 |
11.0.0 |
|
2013-06 |
SA_60 |
Sp-130304 |
0003 |
2 |
SuM Arch |
11.0.0 |
11.1.0 |
|
2014-10 |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.1.0 |
12.0.0 |
|
2016-01 |
– |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
|
2017-03 |
– |
– |
– |
– |
Update to Rel-14 version (MCC) |
13.0.0 |
14.0.0 |
|
2018-06 |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
14.0.0 |
15.0.0 |
|
2020-07 |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
15.0.0 |
16.0.0 |
|
2022-03 |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
16.0.0 |
17.0.0 |