Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map
Top   in Index   Prev   Next

TS 32.140 (SA5)
Telecommunication management –
Subscription Management (SuM) requirements

ToC   3GPP‑Page   ETSI‑search   Help    
V14.0.0 (PDF)  2017/03  41 p.
V13.0.0  2016/01  41 p.
V12.0.0  2014/10  41 p.
V11.1.0  2013/06  41 p.
V10.0.0  2011/04  41 p.
V9.1.0  2009/12  41 p.
V8.0.0  2008/12  38 p.
V7.0.0  2007/06  38 p.
V6.4.0  2007/06  38 p.

Rapporteur:  Mr. Toche, Christian
See also:  –

Subscription Management (SuM) is a feature which will develop over a number of 3GPP releases. It is intended to permit Service Providers, Value Added Service Providers and Mobile Operators to provision services for a specific subscriber. The feature is necessary to allow Service Providers and Operators to provision, control, monitor and bill the configuration of services that they offer to their subscribers. SuM focuses on the OAM processes to manage subscription information. These correspond to the 'Fulfilment' Process areas of the TeleManagement Forum Telecom Operations Map.

This TS defines the service requirements and high-level architecture for SuM. It provides additional supporting material, which whilst not within the scope of this release, provides an insight towards the future evolution. This is in order that initial work may be done with an appreciation of the wider context expected in future releases of 3GPP specifications.

SuM for 3GPP is primarily concerned with the ability to define subscription profiles and associate the profile with subscribers, users and services that are authorized by agreements. The subscription profile may be used in the process of configuring various network resources (access and core) to make the service a reality for the user.

The management capabilities extend to the creation, modification, synchronization, and re application of subscription profiles.

This TS is oriented towards a standardized interface into the Home Subscriber Server (HSS) in order that services can be provisioned and maintained.


Here   Top



1  ScopePDF-p. 7
2  References
3  Definitions and abbreviationsPDF-p. 8
4  General descriptionPDF-p. 10
5  SuM assumptions and methodsPDF-p. 19
6  High-level requirementsPDF-p. 20Up
A  Business modelPDF-p. 23
B  Example use casePDF-p. 26
C  Change historyPDF-p. 39

Up   Top