3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; V11.1.

0 (2013-06) Telecommunication management; Technical Specification Subscription Management (SuM architecture (!elease ""

3GPP TS 32.141

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Or ani!ational Partners and shall not be implemented. This "pecification is provided for future development wor# within 3GPP only. The Or ani!ational Partners accept no liability for any use of this "pecification. "pecifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Or ani!ational Partners$ Publications Offices.

!elease ""

3GPP TS 3#$"%" &""$"$' (#'"3(')

%eywords
Subscription Management !on"erge# Management arc$itecture

3GPP Postal address 3GPP support office address

6%0 &oute #es 'ucio(es - Sop$ia )ntipo(is Va(bonne - *&)+!, Te(.- .33 4 /2 /4 42 00 *a0- .33 4 /3 6% 41 16

&nternet
$ttp-22333.3gpp.org

Copyright Notification 'o part may be reproduced e(cept as authori!ed by written permission. The copyri ht and the fore oin restriction e(tend to reproduction in all media.
) *+,3- 3GPP Or ani!ational Partners (./&0- .T&"- 11".- 2T"&- TT.- TT1). .ll ri hts reserved. 3MT"4 is a Trade Mar# of 2T"& re istered for the benefit of its members 3GPP4 is a Trade Mar# of 2T"& re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners 5T24 is a Trade Mar# of 2T"& currently bein re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners G"M6 and the G"M lo o are re istered and owned by the G"M .ssociation

3GPP

!elease ""

3GPP TS 3#$"%" &""$"$' (#'"3(')

!ontents
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 &ntroduction...............................................................................................................................................8 , "cope......................................................................................................................................................9 * /eferences..............................................................................................................................................9 3 :efinitions and abbreviations.................................................................................................................9
3., :efinitions..............................................................................................................................................................9 3.* .bbreviations.........................................................................................................................................................;

8 "ubscription Mana ement ("uM) architecture.......................................................................................;

8., 7unctional entities..................................................................................................................................................< 8.* &nterfaces................................................................................................................................................................= 8.*., .pplication of &tf>' for "uM..............................................................................................................................= 8.*.* ?oid = 8.3 Overview of &/P....................................................................................................................................................= 8.3., &/P security.......................................................................................................................................................,+ 8.8 Methodolo y........................................................................................................................................................,+ 8.8., "uM "ta e ,......................................................................................................................................................,+ 8.8.* "uM "ta e *......................................................................................................................................................,+ 8.8.3 "uM "ta e 3......................................................................................................................................................,,

Annex A (informative): Void................................................................................................................12 Annex B (informative): Change history......................................................................................13

3GPP

!elease ""

3GPP TS 3#$"%" &""$"$' (#'"3(')

*ore3or#
This Technical "pecification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuin wor# within the T"G and may chan e followin formal T"G approval. "hould the T"G modify the contents of the present document- it will be re>released by the T"G with an identifyin chan e of release date and an increase in version number as follows@ ?ersion (.y.! where@ ( the first di it@ , presented to T"G for informationA * presented to T"G for approvalA 3 or reater indicates T"G approved document under chan e control. y the second di it is incremented for all chan es of substance- i.e. technical enhancements- correctionsupdates- etc. ! the third di it is incremented when editorial only chan es have been incorporated in the document.

Ready for Converged Management

This specification is part of a set that has been developed for conver ed mana ement solutions.

4ntro#uction
The present document is part a T">family coverin the 3rd Generation Partnership ProjectA Technical "pecification Group "ervices and "ystem .spectsA Telecommunication mana ement- as identified below@ T" 3*.,8+@ T 32.1!1: T" 3*.,;,@ T" 3*.,;*@ T" 3*.,;9@ T" *<.;D,@ T" *<.;D*@ T" *<.;D3@ B"ubscription Mana ement ("uM) reCuirementsB. " #$s%ri&tion Management ( #M) ar%hite%t#re". B"ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)@ /eCuirementsB. B"ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)@ &nformation "ervice (&")B. B"ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)A "olution "et ("") definitionsB. B"ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)@ /eCuirementsB. B"ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)@ &nformation "ervice (&")B. B"ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)A "olution "ets ("") definitionsB.

The 3G environment reCuires more comple( service delivery mechanisms and is no lon er simply an internal matter for a sin le operator but a capability that is achieved by lin#in to ether features across multiple service providers and

3GPP

!elease ""

3GPP TS 3#$"%" &""$"$' (#'"3(')

operators. "ubscription Mana ement ("uM) is a feature that permits "ervice Providers- ?alue .dded "ervice Providersand 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 confi uration of services that they offer to their subscribers. 7or further details see 3GPP T" 3*.,8+ EDF on "uM reCuirements that ives an overview of "uM.

3GPP

!elease ""

3GPP TS 3#$"%" &""$"$' (#'"3(')

Scope

The present document defines the architecture for "ubscription Mana ement ("uM) - includin 1onver ed Mana ement of fi(ed and mobile networ#s.

&e5erences
/eferences are either specific (identified by date of publication- edition number- version number- etc.) or non>specific. 7or a specific reference- subseCuent revisions do not apply. 7or a non>specific reference- the latest version applies. &n the case of a reference to a 3GPP document (includin a G"M document)- a non>specific reference implicitly refers to the latest version of that document in the same Release as the present document. E,F E*F E3F E8F EDF E9F E;F 3GPP T/ *,.=+D@ B?ocabulary for 3GPP "pecificationsB. 3GPP T" *3.++*@ B'etwor# .rchitectureB. 3GPP T" 3*.,+,@ BTelecommunication mana ementA Principles and hi h level reCuirementsB. 3GPP T" 3*.,+*@ BTelecommunication mana ementA .rchitectureB. 3GPP T" 3*.,8+@ BTelecommunication mana ementA "ubscription Mana ement ("uM) reCuirementsB. 3GPP T" *3.++<@ BOr ani!ation of subscriber dataB. 3GPP T" 3*.,D+@ B&nte ration /eference Point (&/P) 1oncept and definitionsB.

The followin documents contain provisions which- throu h reference in this te(t- constitute provisions of the present document.

6e5initions an# abbre"iations

3.1 6e5initions
7or the purposes of the present document- the followin terms and definitions apply@ s#$s%ri$er: "ee 3GPP T/ *,.=+D E,F. servi%e: "ee 3GPP T/ *,.=+D E,F. 'ntegration Referen%e (oint ('R(): "ee 3GPP T" 3*.,+, E3F. #ser: "ee 3GPP T/ *,.=+D E,F. s#$s%ri&tion: "ee 3GPP T/ *,.=+D E,F. #$s%ri&tion Management ( #M): "ee 3GPP T/ 3*.,8+ EDF. #$s%ri&tion (rofi)e: "ee 3GPP T/ 3*.,8+ EDF. #$s%ri&tion (rofi)e Com&onent: "ee 3GPP T/ 3*.,8+ EDF.

3GPP

!elease ""

3GPP TS 3#$"%" &""$"$' (#'"3(')

3.2 )bbre"iations
7or the purposes of the present document- the followin abbreviations apply@ *G 3G .P& ."P .u1 0*0 1" 2&/ GTT G3P G2 G5/ G"" &M" &/P &"P 'P:0 '/M O.M O". O"7 O"" P" "5. "MHO "P "uM TM' T/>&/P 3&11 3"&M ?."P ?G2 ?'O "econd Generation Mobile Third Generation Mobile .pplication Pro rammin &nterface .pplication "ervice Provider .uthentication 1enter 0usiness to 0usiness 1ircuit "witch 2Cuipment &dentity /e ister Global Te(t Telephony Generic 3ser Profile Gome 2nvironment Gome 5ocation /e ister Gome "ubscriber "erver &P Multimedia "ubsystem &nte ration /eference Point (3GPP T" 3*.,+* E8F) &nternet "ervice Provider 'umber Portability :ata 0ase 'etwor# /esource Model Operations- .dministration and Maintenance Open "ervices .ccess Operations "ystem 7unctions Operations "upport "ystem Pac#et "witch "ervice 5evel . reement "ervice Mana ement and Operations (TM7I&T3>T) "ervice Provider "ubscription Mana ement Telecommunication Mana ement 'etwor# Tradin Partner &/P 3niversal &nte rated 1ircuit 1ard 3niversal "ubscriber &dentity Module ?alue .dded "ervice Provider ?irtual Gome 2nvironment ?irtual 'etwor# Operator

Subscription Management (SuM) arc$itecture

3G Telecommunication Mana ement focuses on the most important and strate ic conte(ts in the physical architecture for the mana ement of 3MT". The framewor# to help define a telecom mana ement physical architecture for a planned 3MT" and to adopt standards and provide products that are easy to inte rate is defined in 3GPP T" 3*.,+* E8F. "uM mana es "ubscription Profile 1omponents stored in networ# resources for the purpose of providin services to specific subscribers. This is done with an architecture that is consistent with the one specified in 3GPP T" 3*.,+* E8F. "ubscription Profiles represent services and are associated to subscribers that employ these services (3GPP T" 3*.,8+ EDF). To the e(tent the G"" controls certain services- "ubscription Profile 1omponents can be associated with the G"". Other services- and as a result "ubscription Profiles 1omponents- are outside the jurisdiction of the G"".

3GPP

!elease ""

3GPP TS 3#$"%" &""$"$' (#'"3(')

4.1 *unctiona( entities

7unctional entities belon in to "uM are described in 7i ure ,. The fi ure also contains the actors related to "ubscriptions.

1 P'M+ operator2Ser"ice Pro"i#er 1 8as 0..n

8as

0..n

Ser"ice 1 &e5ers to 0..n

1 Subscriber 1 8as 0..n 1 7ser 8as

"MHO mappin of information entities 8as

0..n

Subscription Pro5i(e 1

!onsists o5

6e5ines 0..n 0..n Ser"ice Pre5erences Subscription Pro5i(e !omponent 0..n

&esi#es in

"ystem

,igure "- ,unctional entities in S.M .ctors described in 7i ure , are@ #$s%ri$er (definition "ee T" *,.=+D) *ser (definition "ee T" *,.=+D) ervi%e (rovider (definition "ee T" *,.=+D) (+M, -&erator (definition "ee T" *,.=+D)

The entities described in 7i ure , are@ #$s%ri&tion (rofi)e (definition "ee T" 3*.,8+) #$s%ri&tion (rofi)e Com&onent (definition "ee T" 3*.,8+) ervi%e (definition "ee T" *,.=+D) ystem (definition "ee T" 3*.,+*) ervi%e (referen%es@ 1ontains the service preferences chosen for a user. 2ach user confi ures his preferences for a particular subscribed service- but only within the limits defined by the "ubscription.

C)arifi%ations to the fig#re: . P5M' OperatorI"ervice Provider has one or several "ervices to offer for "ubscribers. . "ubscriber has one or several "ubscription Profiles- where each describes an offered "ervice.

3GPP

!elease ""

<

3GPP TS 3#$"%" &""$"$' (#'"3(')

. 3ser has one or several "ervice Preferences- where each describes the userJs chosen preferences for the service. . "ubscription Profile may consist of one or several "ubscription Profile 1omponents. . "ubscription Profile may define one or several "ervice Preferences. . "ubscription Profile 1omponent resides in one or several systems "ubscriptions are mana ed in the form of "ubscription profile components- which may be distributed across "ervice Mana ement H Operations ("MHO)- 'etwor# /esource Mana ement H Operations (/MHO) and 'etwor# :omains. There may also be mappin s amon the "MHO- /MHO and 'etwor# :omains.

4.2 4nter5aces
4.2.1 )pp(ication o5 4t5-+ 5or SuM

0S, for 4et5or6 Management and Service Management

7tf(4
0S,
Service Specific entities

0S,
.ser 12uipment 3omain

0S,
Access 4et5or6 3omain

0S, !ore +et3or9 :asic ,ntities 6omain

8ommon 84 3omain 8S 3omain PS (GP!S 3omain

!ore net3or9

41 Management

,igure #- 0vervie5 of P9M4 Telecom Management 3omains and 7tf(4 (3GPP TS 3#$"'# :%; The &tf>' for "uM is reali!ed by means of an &nte ration /eference Point (&/P) as defined in 3GPP T" 3*.,+* E8F. Operations "ystem 7unctions (O"7) functionality can be reali!ed in '2s or in the '2 Mana ement systems. "uM- for this release- is concerned with the O"7 functionality contained in the 1ore 'etwor# 0asic 2ntities :omain and specifically that of the 1ommon 1' :omain. "ubscription Profile 1omponents are located in the '2s O"7$s within the 1ommon 1' :omain or their '2s O"7$s in the '2 mana ement systems- and are in either case accessed consistent with the &/P concept. "uM O"7$s for 'etwor# Mana ement and "ervice Mana ement are located in networ#> and service mana ement systems.

4.2.2 Voi#

4.3 ;"er"ie3 o5 4&P

7i ures 3 and 8 identify system conte(ts of the &/P in terms of its implementation- called &/P. ent (see 3GPP T" 3*.,D+ E;F)- and the user of the &/P. ent- called &/PMana er (see 3GPP T" 3*.,D+ E;F). The &/P. ent implements and supports the &nterface &/Ps for "uM '/M &/P. The &/P. ent can reside in an 2lement Mana er (2M) or a 'etwor# 2lement ('2) (3GPP T" 3*.,+* E8F). &n the former case- the interface (represented by a thic# dotted line) between the 2M and the '2s is not the subject of the &nterface &/Ps for "uM '/M &/P. .n &/PMana er usin the &nterface &/Ps for "uM '/M &/P shall choose one of the two "ystem 1onte(ts defined herefor each '2. 7or instance- if an 2M is responsible for mana in a number of '2s- the 'M shall access the &nterface &/Ps for "uM '/M &/P throu h the 2M and not directly to those '2s. The interface &/Ps for "uM '/M &/P can be the followin @

3GPP

!elease ""

"'

3GPP TS 3#$"%" &""$"$' (#'"3(')

>

0asic 1M &/P

&/PMana er

&/P. ent 2M

NEs

'M

&tf >'

"uM &nterface &/P&/Ps for "uM '/M &/P

,igure 3- System 8onte=t A

&/PMana er 'M &tf>'

&/P. ent '2

&nterface &/Ps for "uM &/P '/M &/P

,igure %- System 8onte=t >

4.3.1 4&P securit<

The &/P interface is made secure by controllin access to the networ# and mana ement systems. Operations processes must insure that only authori!ed personnel have the access authority to retrieve and alter "uM data. "tandard protocols used over the interface between the &/PMana er and the &/P. ent provide some de ree of security. The e(act nature of the security is described in the "olution "et for that protocol. &n addition to the reCuirement that the &/PMana er and the &/P. ent be secure- most physical lin#s between them are secured as well.

4.4 Met$o#o(og<
The methodolo y used to conclude the standard wor# for "uM shall follow the &/P methodolo y described in 3GPP T" 3*.,D+ E8F. This subclause describes how to apply that methodolo y.

4.4.1 SuM Stage 1

"uM "ta e , is documented in 3GPP T" 3*.,8+ EDF.

4.4.2 SuM Stage 2

"uM "ta e * is documented as follows@ a) The present document (3GPP T" 3*.,8,) is finali!ed by identifyin the relevant &/Ps.

b) 3GPP T" 3*.,;, (for non>conver ed mana ement) and T" *<.;D, (for conver ed mana ement) define the /eCuirements for the "uM '/M &/P. 3GPP T" 3*.,;, and T" *<.;D, shall- where applicable- follow the structure in 3GPP T" 3*.9*, (for non> conver ed mana ement) and T" *<.9*, (for conver ed mana ement) (Generic '/M &/P@ /eCuirements) respectively.

3GPP

!elease ""

""

3GPP TS 3#$"%" &""$"$' (#'"3(')

c)

3GPP T" 3*.,;* (for non>conver ed mana ement) and T" *<.;D* (for conver ed mana ement) describe the &nformation "ervice for the "uM '/M &/P K containin the &nformation Object 1lasses (&O1s)- attributesrelations etc. for "uM. 3GPP T" 3*.,;* and T" *<.;D* shall- where applicable- follow the structure in 3GPP T" 3*.9** (for non> conver ed mana ement) and T" *<.9** (for conver ed mana ement) (Generic '/M &/P@ &nformation "ervice) - respectively.

4.4.3 SuM Stage 3

"uM "ta e 3 is documented in the followin documents@ > T" 3*.,;9 (for non>conver ed mana ement) and T" *<.9*3 (for conver ed mana ement) "uM '/M &/P@ "olution "et definition s.

3GPP

!elease ""

"#

3GPP TS 3#$"%" &""$"$' (#'"3(')

)nne0 ) (in5ormati"e)- Voi#

3GPP

!elease ""

"3

3GPP TS 3#$"%" &""$"$' (#'"3(')

)nne0 : (in5ormati"e)!$ange $istor<

8hange history
3ate Mar 2003 Sep 2003 Mar 2004 Aun 2001 6ec 200? Sep 200/ Mar 2011 2012-0/ 2013-06 TSG ? S)=1/ S)=21 S)=23 S)=36 S)=42 S)=4% S)=60 TSG 3oc$ SP-030042 SP-03040% SP-04010? --SP-0/0621 Sp-130304 8! --0001 --0002 0003 !ev ------2 Subject@8omment Submitte# to S)>1/ as "1.0.0 5or 4n5ormation Submitte# to S)>21 as "2.0.0 5or )ppro"a( Subscription Management TS-5ami(< (32.140 an# 32.110) tit(e a(ignment (@SM@ becomes @SuM@ an# #e(ete @Ser"ices operations management@) )utomatic upgra#e to &e(-1 (no !&) at 5reeBe o5 &e(-1. 7pgra#e to &e(ease ? )(ign 3it$ TS 32.140 SuM reCuirements 7p#ate to &e(-10 "ersion (M!!) 7p#ate to &e(-11 "ersion (M!!) SuM )rc$ 0ld 1.0.0 2.0.0 6.0.0 6.1.0 1.0.0 ?.0.0 /.0.0 10.0.0 11.0.0 4e5 -6.0.0 6.1.0 1.0.0 ?.0.0 /.0.0 10.0.0 ""$'$' ""$"$'

3GPP