3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; V11.0.

0 (2012-09) Study on management of converged networks Technical Report ( elease !!"

3GPP TR 32.833

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 T 3#$%33 &!!$'$' (#'!#(')"

%eywords
FMC, wireline, wireless

3GPP Postal address 3GPP support office address

650 Rou e !es "u#ioles - $o%&i' (n i%olis V'l)onne - FR(*C+ Tel., -33 . 92 9. .2 00 F'/, -33 . 93 65 .0 16

&nternet
& %,11www.32%%.or2

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.
) *+,*- 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 T 3#$%33 &!!$'$' (#'!#(')"

Con en s
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 &ntroduction...............................................................................................................................................8 , "cope......................................................................................................................................................9 * /eferences..............................................................................................................................................9 3 :efinitions- symbols and abbreviations..................................................................................................;
3., :efinitions..............................................................................................................................................................; 3.* "ymbols..................................................................................................................................................................; 3.3 .bbreviations.........................................................................................................................................................;

< :efinition of the Problem "pace............................................................................................................= 8 7i(ed>Mobile 1onver ence (7M1) 3se 1ases.....................................................................................,,
8., 3se 1ases for common /adio and Transport Mana ement.................................................................................,, 8.,., 2(ample :eployment "cenario.........................................................................................................................,, 8.,.* 7M 31 with alarm from underlyin transport networ#....................................................................................,, 8.,.3 1M 31 addition of new radio networ# resources............................................................................................,* 8.,.< PM 31 supportin PM data correlation from radio and transport networ#s....................................................,* 8.,.8 31 common Mana ement of /adio and underlyin Transport 'etwor#s.......................................................,3 8.,.9 31 2thernet ?5.' provisionin .....................................................................................................................,8 8.,.; 31 .larm monitorin .......................................................................................................................................,8 8.* 3se 1ases for 1onver ed 'etwor#s Mana ement...............................................................................................,9 8.*.,31 7emto .ccess Mana ement.........................................................................................................................,9 8.3 3se 1ases for 1ustomer 7acin "ervices Mana ement.......................................................................................,; 8.3., M'O launches a new service............................................................................................................................,; 8.3.* 2nd user has problems with a streamin service..............................................................................................,@

9 Potential /elationships to other ":Os and &ndustry 7ora....................................................................*+ ; 2valuation of Mana ement 1onver ence Options...............................................................................*+
;., 7acilities...............................................................................................................................................................*+ ;.,., &mport facility....................................................................................................................................................*+ ;.,.,., 1ase , usa e (case>reference)........................................................................................................................*+ ;.,.,.* 1ase * usa e (case>derivative).......................................................................................................................*+ ;.,.,.31ase 3 usa e (case>containment)....................................................................................................................*, ;.* Option ,................................................................................................................................................................*, ;.*., 3se .TM transport networ# case to illustrate the desi n pattern.....................................................................*, ;.*.,., :efine eneric TP (terminatin point) and specific TP &O1s in A*B..............................................................*, ;.*.,.* .ssociate specific lin# with specific TP in specific '/M &/Ps....................................................................** ;.*.* .pply the desi n pattern (discussed in ;.,.,) for ",>MM2 reference point....................................................*3 ;.3 Option *................................................................................................................................................................*< ;.3., 1onte(t *< ;.3.* Procedure *<

@ Mana ement 1onver ence /ecommendations.....................................................................................*8 Annex A: Name-Containment Class diagram from TS 32.622 [12]..........................................26 Annex B: Containment Diagram from ! Net"or# $ie" C %& %B S'e(ifi(ation.............2) Annex C: Brief des(ri'tion of *N .....................................................................................................2+
9., /elations between fra ments and 3mbrella........................................................................................................*@

3GPP

elease !!

3GPP T 3#$%33 &!!$'$' (#'!#(')"

Annex D: Net"or# Annex -:

anagement related T%S&AN Standards...........................................................2,

C.ange .istor/.............................................................................................................30

3GPP

elease !!

3GPP T 3#$%33 &!!$'$' (#'!#(')"

Forewor!
This Technical /eport 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 followsC ?ersion (.y.! whereC ( the first di itC , presented to T"G for informationD * presented to T"G for approvalD 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.

3n ro!u# ion
Traditional networ# mana ement systems are or ani!ed alon silos for the different communication networ# technolo ies- li#e radio networ#s or transport networ#s. .s a conseEuence of this architecture there is little or no #nowled e in one mana ement system about the other mana ement systems. .lso- typically there is no information e(chan e between these systems. This is why true end to end mana ement is normally not possible. This industry is movin towards removin these silos. 'umerous activities have been started recently. One direction is the eneral harmonisation and ali nment of the mana ement approaches and mana ement interfaces. .nother direction is the development of mana ement applications bein able to deal with mana ement information for several networ# technolo ies. The final oal is a conver ed O"". This study assumes that this conver ed O"" is already in place. The scope of this study is to investi ate which new functionalities re ardin a true end to end mana ement are enabled by a conver ed O"". The fra ments loo#ed at are 7ault Mana ement- Performance Mana ement and 1onfi uration Mana ement.

3GPP

elease !!

3GPP T 3#$%33 &!!$'$' (#'!#(')"

$#o%e

The present document investi ates which new functionalities re ardin a true end to end mana ement are enabled by a conver ed O"". The fra ments loo#ed at are 7ault Mana ement- Performance Mana ement and 1onfi uration Mana ement.

2
> > >

Re4eren#es
/eferences are either specific (identified by date of publication- edition number- version number- etc.) or non>specific. 7or a specific reference- subseEuent 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. 3GPP T/ *,.=+8C F?ocabulary for 3GPP "pecificationsF. 3GPP T" 3*.;,*C FTelecommunication mana ementD 1onfi uration Mana ement (1M)D Transport 'etwor# (T') 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)D &nformation "ervice (&")F. 3GPP T" 3*.;<*C FTelecommunication mana ementD 1onfi uration Mana ement (1M)D "i nallin Transport 'etwor# ("T') interface 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)D &nformation "ervice (&")F. 3GPP T" 3*.;9*C FTelecommunication mana ementD 2volved 3niversal Terrestrial /adio .ccess 'etwor# (2>3T/.') 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)D &nformation "ervice (&")F. 3GPP T" 3*.;8*C FTelecommunication mana ementD 2volved Pac#et 1ore (2P1) 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)D &nformation "ervice (&")F. &T3>T G.9@+ O"& networ#in and system aspects H .bstract "ynta( 'otation One (."'.,) 3GPP T" 3*.9<*C FTelecommunication mana ementD 1onfi uration Mana ement (1M)D 3T/.' networ# resources &nte ration /eference Point (&/P)D 'etwor# /esource Model ('/M)F. .TM 7orum- Technical 1ommittee- 'etwor# Mana ement- M< 'etwor# ?iew 1M&P M&0 "pecificationC 1M&P "pecification for the M< &nterface- "ep- ,==8 3GPP T" 3*.9**C FTelecommunication mana ementD 1onfi uration Mana ement (1M)D Generic networ# resources &nte ration /eference Point (&/P)D 'etwor# /esource Model ('/M)F. &T3>T I.*+=,C JTerms and definitions for 'e(t Generation 'etwor#sK $55TMF'081 FMC 4e!er' e! ne wor6 7o!el (F*M) 51.1

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

A,B A*B

A3B

A<B

A8B A=B A,+B A,,B A,*B A,3B A,<B

3GPP

elease !!

3GPP T 3#$%33 &!!$'$' (#'!#(')"

8e4ini ions, s97)ols 'n! '))re5i' ions

3.1 8e4ini ions

7or the purposes of the present document- the terms and definitions iven in T/ *,.=+8 A,B and the followin apply. . term defined in the present document ta#es precedence over the definition of the same term- if any- in T/ *,.=+8 A,B. e'ode0 'ode0 5T2 eEuivalent to the 0T" 3MT" eEuivalent to the 0T"

&n &T3>T- a definition is provided for 7i(ed Mobile 1onver ence (7M1) which applies in eneral to references to 7M1 in this specification. fixed mo1ile (on2ergen(e A&T3>T L.,;9*BC &n a iven networ# confi uration- the capabilities that provide services and application to the end>user re ardless of the fi(ed or mobile access technolo ies bein used and independent of the user$s location. &n the 'G' environment- it means providin 'G' services to end>users re ardless of the fi(ed or mobile access technolo ies bein used (/ec. I.*+=,)

3.2 $97)ols
7or the purposes of the present document- the followin symbols applyC None

3.3 ())re5i' ions

7or the purposes of the present document- the abbreviations iven in T/ *,.=+8 A(B and the followin apply. .n abbreviation defined in the present document ta#es precedence over the definition of the same abbreviation- if any- in T/ *,.=+8 A,B. ... .:"5 .' .TM 0'G 0/." 0"1 0T" 1M&P :'" :"5 :"5.M :M:M 2th 23T/.' 7M1 7' 7'O G2 GG"' N5/ &M" &P 5T2 M&0 MM2 MP5" MM/ .uthentication- .uthori!ation and .ccountin .symmetric :i ital "ubscriber 5ine .ccess 'etwor# .synchronous Transfer Mode 0roadband 'etwor# Gateway 0roadband /emote .ccess "erver (synonym 0'G) 0ase "tation 1ontroller 0ase Transceiver "tation 1ommon Mana ement &nformation Protocol :irectory 'ame "ervice :i ital "ubscriber 5ine :i ital "ubscriber 5ine .ccess Multiple(er :ense Mavelen th :ivision Multiple(in 2thernet 2volved 3niversal Terrestrial /adio .ccess 'etwor# 7i(ed>Mobile 1onver ence 7i(ed 'etwor# 7i(ed 'etwor# Operator Gi abit 2thernet Gateway GP/" "upport 'ode Nome 5ocation /e ister &P Multimedia "ubsystem &nternet Protocol 5on Term 2volution Mana ement &nformation 0ase Mobile Mana ement 2ntity Multiprotocol 5abel "witchin Microwave /adio

3GPP

elease !!

3GPP T 3#$%33 &!!$'$' (#'!#(')"

'M P>GM P:N PO' /G /'1 "G"' "eGM ">GM "N: TP 31 ?5.' M:M

'etwor# Mana ement P:' Gateway Plesiochronous :i ital Nierarchy Passive Optical 'etwor# /esidential Gateway /adio 'etwor# 1ontroller "ervin GP/" "upport 'ode "ecurity Gateway "ervin Gateway "ynchronous :i ital Nierarchy Terminatin Point 3se 1ase ?irtual 5ocal .rea 'etwor# Mavelen th :ivision Multiple(in

3GPP

elease !!

3GPP T 3#$%33 &!!$'$' (#'!#(')"

8e4ini ion o4 &e Pro)le7 $%'#e

"ervices offered to end users use resources from networ#s of multiple technolo ies typically operated by more than just one type of networ# service operator. Mana ement of these services and these networ#s face several challen es. One of the challen es is that the mana ement standards for these technolo ies are defined at different standardi!ation fora and ali#e. .nother challen e is that different parts of the networ# are also mana ed by separate mana ement systems that do not communicate with each other and are usually also operated by different type of networ# service providers. The fi ures below try to present a holistic view towards fi(ed and mobile networ#s. The fi ures are informative and do not try to describe the whole comple(ity of the fi(ed and mobile networ#s. .lso different roles such as fi(ed access provider- internet service provider- mobile networ# operator- transport provider are not considered. &nstead the perspective is topolo y and site oriented. The fi ures show theC most usual sites with typical interconnections typical functionsOproducts within the sites

.igure *$!/ .01 Pro2lem Space/ Typical sites and interconnections in fi3ed and mo2ile networks

3GPP

elease !!

!'

3GPP T 3#$%33 &!!$'$' (#'!#(')"

.igure *$#/ 4etailed .01 Pro2lem Space/ Typical functions and products in fi3ed and mo2ile networks &t should be noted that sites and functions are not all mandatory but may vary due to specific implementations and operator demands. &n contrast to many se mented and abstractOfunctional networ# presentations- this blueprint intends to help understandin networ#s and business close to real life. 1onseEuently it mi ht be useful as a basis for further end>to>end activities- improvements and decisions.

3GPP

elease !!

!!

3GPP T 3#$%33 &!!$'$' (#'!#(')"

Fi/e!-Mo)ile Con5er2en#e (FMC) :se C'ses

5.1 :se C'ses 4or #o77on R'!io 'n! Tr'ns%or M'n'2e7en

5.1.1 +/'7%le 8e%lo97en $#en'rio
The 7i ure 8.,.,., below shows a simplified e(ample for a typical deployment scenario in today$s networ#s. &t depicts networ# elements of the radio networ# controlled by the mobile networ# operatorPs (M'O) 2lementO:omain Mana ers (2MO:M) and networ# elements of the transport networ# controlled by the transport networ# operatorPs (T'O) 2MO:M. The M'O and the T'O may or may not be the same operator and there also may or may not be a common networ# mana ement ('M) layer on top of the radio networ# and the transport networ# specific 2MsO:Ms. The use cases in the followin sections are based on this deployment scenario.

.igure +$!$!$!/ 53ample deployment scenario for common radio and transport network use cases$

5.1.2 FM :C wi & 'l'r7 4ro7 un!erl9in2 r'ns%or ne wor6

"cenario /adio networ# is operated by a Mobile 'etwor# Operator (M'O) and transport networ# by a Transport 'etwor# Operator (T'O). The M'O does not have control over the transport networ#. &n a radio networ# alarm condition it is useful to #now if there is an alarm condition also in the underlyin transport networ#. 'etwor# 1onte(t The M'O mana es transceiver type and controller type 'etwor# 2lements ('2) of the radio networ#. The T'O mana es the wireline mobile bac#haul between the transceiver and the controller type '2s of the radio networ#. Transport networ# has ed e nodes both at the transceiver and controller sides of the transport networ#. 2d e node is assumed to be a atewayOinterface node between the radio and the transport networ#s. :escription

3GPP

elease !!

!#

3GPP T 3#$%33 &!!$'$' (#'!#(')"

The M'O detects alarms at a transceiver type '2 and at a controller type '2. The M'O starts to identify the root cause for the problem. The potential problem may be in the radio networ# but alarms from the transceiver and the controller type of '2s rather indicate a possibility of a problem of mobile bac#haul (transport networ#). The related transport networ# alarms would be needed for end to end investi ation of the potential problem. &mplications &n order to solve the root cause for the radio networ# problem efficientlyC o The M'O needs to et information on the alarms in the underlyin transport networ#. o The M'O needs to be able to correlate the transport networ# alarms with the correspondin radio networ# alarms.

5.1.3 CM :C '!!i ion o4 new r'!io ne wor6 resour#es

"cenario /adio networ# is operated by a Mobile 'etwor# Operator (M'O) and transport networ# by a Transport 'etwor# Operator (T'O). The M'O does not have control over the transport networ#. Mhen new radio networ# resources are added confi uration information needs to be transferred between the M'O and the T'O. 'etwor# 1onte(t The M'O mana es transceiver type (e. . 'ode0) and controller type (e. . /'1) 'etwor# 2lements ('2) of the radio networ#. The T'O mana es the wireline mobile bac#haul between the transceiver and the controller type '2s of the radio networ#. Transport networ# has ed e nodes both at the transceiver and controller sides of the transport networ#. 2d e node is assumed to be a atewayOinterface node between the radio and the transport networ#s. :escription The M'O is mana in a radio networ# with e. . @+ transceiver type '2s and a reEuired number of controller type '2s. The M'O wants to add < new transceiver type '2s usin the same transport networ#. &mplications &n this scenario it is assumed that the radio networ# of the M'O is already usin the transport networ# of the T'O for service offerin . &n order to add new radio networ# resources usin the transport networ#C o o o The M'O and the T'O need to a ree on a service level a reement ("5.) for the new radio resources. Mhen the new radio resources are available the M'O needs to provide the T'O with reEuired information for confi uration purposes. The T'O needs to confi ure the transport networ# to satisfy the reEuirements set by the M'O.

5.1.. PM :C su%%or in2 PM !' ' #orrel' ion 4ro7 r'!io 'n! r'ns%or ne wor6s
"cenario /adio networ# is operated by a Mobile 'etwor# Operator (M'O) and transport networ# by a Transport 'etwor# Operator (T'O). The M'O does not have control over the transport networ#. M'O uses PM counters to analyse offered service level and the networ# status.

3GPP

elease !!

!3

3GPP T 3#$%33 &!!$'$' (#'!#(')"

'etwor# 1onte(t The M'O mana es transceiver type and controller type 'etwor# 2lements ('2) of the radio networ#. The T'O mana es the wireline mobile bac#haul between the transceiver and the controller type '2s of the radio networ#. Transport networ# has ed e nodes both at the transceiver and controller sides of the transport networ#. 2d e node is assumed to be a atewayOinterface node between the radio and the transport networ#s.

:escription M'O collects and analyses PM information from radio networ#. M'O sees a de radin trend of service level or an increasin trend of error level. The potential problem may be in the radio networ# but measurements from the transceiver and the controller type of '2s rather indicate a problem of mobile bac#haul (transport networ#). The transport networ# PM would be needed for end to end investi ation of the potential problem.

&mplications &n order to have a ood end to end view and supportin efficient decision ma#in in radio networ#C M'O needs to et PM information from the transport networ# either re ularly or per reEuest.

5.1.5 :C #o77on M'n'2e7en o4 R'!io 'n! un!erl9in2 Tr'ns%or *e wor6s

"cenario Mobile networ# may use transport networ# (e. . &P transport networ# etc.) to provide the transport function. 7or the conver ed networ# mana ement which focuses on mana in the mobile networ# should have a unified interface- to mana e the mobile networ# and its supportin transport networ#. 'etwor# 1onte(t The mobile networ# and its supportin transport networ#. &mplications The relationship between mobile mana ed resource and transport mana ed resources needs to be #nown by the &/PMana er.

:escription The 7M1 mana ement for common radio and transport mana ement include thatC ,. *. 3. Monitorin and mana in the alarms information of conver ed networ# which includes mobile networ# and its supportin transport networ#. Monitorin and mana in the performance information of conver ed networ# which includes mobile networ# and its supportin transport networ#. Monitorin and mana in the confi uration information of conver ed networ# which includes mobile networ# and its supportin transport networ#.

3GPP

elease !!

!*

3GPP T 3#$%33 &!!$'$' (#'!#(')"

1onver ed networ# mana ement (&/PMana er)

Mobile networ#

"upportin transport networ#

.igure +$!$!$!/ 1onverged network management

3GPP

elease !!

!+

3GPP T 3#$%33 &!!$'$' (#'!#(')"

5.1.6 :C + &erne V"(* %ro5isionin2

"cenario Operator- as a result of a plannin e(ercise- reali!es that additional infrastructure capacity is reEuired to support service rowth (e. . to support new G* lin#s). The capacity- in the form of an 2thernet ?5.' needs to be created and activated across a mi( of wireline '2s and wireless '2s. The 2thernet ?5.' is initially simply point to point. 'etwor# 1onte(t The 2thernet ?5.' terminates in a wireless eEuipment and traverses several wireline eEuipments to terminate at wireline '2. &mplications &t would appear that at a minimumC The relation between wireless '2 and wireline '2 needs to be #nown to the &/PMana er. "ome confi uration parameters need to be sent to the wireless '2.

:escription .s a result of the activation the &/PMana er should be able to discover the 2thernet ?5.' and its path related to the supported G* lin# (as in our e(ample).

5.1.0 :C (l'r7 7oni orin2

"cenario Operator needs to #now if an alarmed radio resource- e. . 2nd Point instance- is related to or not related to any alarmed wireline resources. 'etwor# 1onte(t The wireline circuit- terminatin at both ends in wireless '2s- traverses several wireline '2s. &mplications &t would appear that at a minimumC o Operator needs to #now (e. . the identifier of) the wireline networ# ed e node resource (e. . circuit identifier) that is related to the alarmed radio resource.

:escription %nowin the wireline networ# ed e node resource identifier- operator can discover the identifiers of all wireline resources supportin the alarmed wireless resources. %nowin their identifiers- operator can #now if the identified wireline resources are in alarmed condition and if so- determine if the alarm condition is causin the alarm condition of the wireless resource.

3GPP

elease !!

!,

3GPP T 3#$%33 &!!$'$' (#'!#(')"

5.2 :se C'ses 4or Con5er2e! *e wor6s M'n'2e7en

5.2.1 :C Fe7 o (##ess M'n'2e7en

'oteC This is one possible use case scenario for femto access mana ement. There are other possible scenarios as well. "cenario .n operator operatin both mobile and fi(ed networ#s offers for its customers a service where the end user can ta#e at home into use a femto access point (Nome 'ode 0) to achieve better service Euality over mobile networ#s. The femto access point is attached to an .:"5 connection and connects to the operatorPs mobile core via fi(ed networ#. The fi ure below illustrates the use case with a service flow e(ample showin networ# elements and functions relevant for the scenario. This use case is derived from the :etailed 7M1 Problem "pace (7i ure <.*) but the networ# elements are limited here to the minimum relevant for the femto use case. There could be e. . more networ# elements in between .' and 0'GO0/." (e. . a re ation sta es). 'ote that dependin from the deployment the service flow could loo# different and also the networ# elements involved could be different.

.igure +$#$!$!/ .emto use case service flow with relevant network elements

'etwor# conte(t Mhen mana in the femto access service the operator needs to ensure that the networ# elements belon in to both mobile and fi(ed networ#s are able to provide the necessary service Euality and resources. The most relevant networ# elements from mana ement point of view specific for this scenario areC > .t home premises

3GPP

elease !!

!-

3GPP T 3#$%33 &!!$'$' (#'!#(')"

o o >

a femto access point (Nome 'ode 0) typically mana ed by mobile networ# mana ement systems a /esidential Gateway (/G) typically mana ed by fi(ed networ# mana ement systems

.t local office o a .ccess 'etwor# node (.') typically mana ed by fi(ed networ# mana ement systems

>

.t the central office o a 0roadband 'etwor# Gateway (0'G)- typically mana ed by fi(ed networ# mana ement systems

>

.t mobile control site o a 7emto Gateway (Nome 'ode 0 Gateway)- typically mana ed by the mobile networ# mana ement systems

Nere it is assumed that the underlyin networ# infrastructure has been already confi ured so that the service offerin can ta#e place. 'ot all the relevant networ# elements are considered in this use case- e. . the &P>1ore switch as well as several other networ# elements at the mobile control and the mobile core site. &mplications The relation between the abovementioned networ# elements in mobile and fi(ed networ#s need to be #now to the operatorPs mana ement systems. :escription 7rom mana ement point of view the operator needs to monitor these relevant networ# elements and also needs to be able to e. . correlate any alarms between them.

5.3 :se C'ses 4or Cus o7er F'#in2 $er5i#es M'n'2e7en

5.3.1 M*; l'un#&es ' new ser5i#e
"cenario M'O is providin 5T2 service to its customers. &n addition to the connectivity service the M'O also provides different #ind of content related services for its customers that end users can subscribe to at the M'OPs customer portal or by callin to M'OPs help des#. 'ow the M'O is launchin a new service where customers can subscribe to live broadcastin of football ames. 5T2 radio networ# is operated by a Mobile 'etwor# Operator (M'O) and transport networ# by a Transport 'etwor# Operator (T'O). The M'O does not have control over the transport networ#. 'etwor# 1onte(t The M'O mana es transceiver type and controller type 'etwor# 2lements ('2) of the radio networ#. The T'O mana es the wireline mobile bac#haul between the transceiver and the controller type '2s of the radio networ#. Transport networ# has ed e nodes both at the transceiver and controller sides of the transport networ#. 2d e node is assumed to be a atewayOinterface node between the radio and the transport networ#s. :escription

3GPP

elease !!

!%

3GPP T 3#$%33 &!!$'$' (#'!#(')"

M'O wants to launch a new service offerin - life football broadcastin - over the radio networ# for its customers. &t is estimated that to uarantee service Euality of the live broadcastin the current contract with the T'O is not sufficient- but more bandwidth is needed to support the occasional live football broadcastin services. .lso the M'O needs to add more capacity to the radio networ# at some locations. The M'O needs to ne otiate a new "5. with the T'O. The M'O also needs to add additional transceiver type '2s to some locations. T'O has enou h capacity to support both the increased bandwidth reEuirements as well as the new transceiver type '2s. The new '2s need to be confi ured to the transport networ#. &n addition to networ# confi uration- the M'O also needs to create and enable the new service at its service portal and all the reEuired customer re isters. &mplications &n order to launch a new service efficiently automated processes should be used as much as possible. o The 1M operations from both the M'O and the T'O should have automated processes reEuirin minimum manual confi uration. o There should be means for communicatin reEuired 1M information from M'O to T'O with minimum manual interaction. o The M'OPs service confi uration should support processes reEuirin minimum manual confi uration.

5.3.2 +n! user &'s %ro)le7s wi & ' s re'7in2 ser5i#e

"cenario M'O is providin 5T2 service to its customers. .s part of the M'OPs service offerin customers are also offered subscriptions to live broadcastin of football ames. The 5T2 radio networ# is operated by a Mobile 'etwor# Operator (M'O) and the transport networ# by a Transport 'etwor# Operator (T'O). The M'O does not have control over the transport networ#. 'etwor# 1onte(t The M'O mana es transceiver type and controller type 'etwor# 2lements ('2) of the radio networ#. The T'O mana es the wireline mobile bac#haul between the transceiver and the controller type '2s of the radio networ#. Transport networ# has ed e nodes both at the transceiver and controller sides of the transport networ#. 2d e node is assumed to be a atewayOinterface node between the radio and the transport networ#s. :escription 2nd user is watchin a live football broadcastin usin her mobile phone. "uddenly the broadcastin is interrupted. .s the end user cannot connect to the live football broadcastin a ain she calls to the M'OPs helpdes#. The M'OPs helpdes# answers to the phone call where the end user is informin that she cannot anymore access the live football broadcastin . The helpdes# is able to see that there are some connectivity problems at the cell site- as well as at the nei hbourin cell site- the end user is located in. The helpdes# informs the end user that there seems to be some networ# problems and reEuests the end user to wait for a moment while the helpdes# is as#in for any further information about the problem and when the problem is estimated to be solved.

3GPP

elease !!

!)

3GPP T 3#$%33 &!!$'$' (#'!#(')"

.fter a short moment- the helpdes# is informed that there was a problem in the transport networ# which has been resolved automatically. Nowever- end users mi ht have faced some problems in the service offerin . &n the meanwhile also alarms at the cell sites have been cleared. The help des# informs the end user that the problem should have been solved now and apolo ies for interruption of the service. .s compensation the end user account is credited with an electronic voucher that can be used to pay for some M'OPs service &mplications &n order to solve the customer problem efficientlyC o The M'OPs helpdes# needs to et information from the networ# problems that may affect customersP services. o The actual root cause of the networ# problem should be solved efficiently.

3GPP

elease !!

#'

3GPP T 3#$%33 &!!$'$' (#'!#(')"

Po en i'l Rel' ions&i%s o o &er $8;s 'n! 3n!us r9 For'

3GPP ". is participatin in a Multi>":O initiative where other ":Os and &ndustry 7ora which should be included in this activity are identified. 1urrently the main body of interest seems to be the TM 7orum.

+5'lu' ion o4 M'n'2e7en Con5er2en#e ;% ions

/eference A,<B defines the overall architecture of a 7ederated 'etwor# Model (7'M). &t identifies the major components (called models) and their relations amon them. /efer to .nne( 1 for ease of reference. "ection ;., describes the types of relation (called facilities) that can be used in /+- /,- /*- /3- /<- etc. "ection ;.* illustrates usa e of these facilities in /+- /,- /*- etc. The author of a particular model (e. . author of the J3GPP wireless 'M concrete modelK)- when relatin its classes with classes of other models- need not use all facilities identified in "ection ;., Nowever- the author must- when relatin its classes with classes of other models- use the facilities identified in "ection ;.,.

0.1 F'#ili ies

The facilities identified here are used for sta e * (e. . &") platform>independent>model level usa e. They are not used in sta e 3 (e. . "") platform>specific>model level usa e.

0.1.1 37%or 4'#ili 9

This facility allows a model- e. . the J3GPP wireless 'M concrete modelK such as 23T/.' '/M &/P &" to use a networ# resource modelled class defined elsewhere- e. . in 3mbrella model or other concrete model. There are three such usa e cases.

0.1.1.1

C'se 1 us'2e (#'se-re4eren#e)

This facility allows a class defined in one model to refer (point to) class defined in another model. "uppose model>. has class>.,D model>G has class>G, and class>., needs to point to class>G,. :oC &n Model>. &"- imports model>GCCclass>G,. &n Model>. &"- 1lass>., has an attribute that contains the :istin uished 'ame of model>GCCclass>G,. &n Model>. ""- not to define any definition of model>GCCclass>G,.

0.1.1.2

C'se 2 us'2e (#'se-!eri5' i5e)

This facility allows a class defined in one model to derive itself from a class defined in another model. "uppose model>. has class>.<D model>G has class>G, and class>.< needs to be a derivative of class>G,. :oC &n Model>. &"- imports model>GCCclass>G,.

3GPP

elease !!

#!

3GPP T 3#$%33 &!!$'$' (#'!#(')"

&n Model>. &"- 1lass>.< inherits from the imported class. &n Model>. ""- the authors decide- on case by case basis- if its "" should define its imported class (i.e. i norin the fact that the imported class "" e(ists somewhere else) or not.

0.1.1.3

C'se 3 us'2e (#'se-#on 'in7en )

This facility allows a class defined in one model to contain (or to be name>contained by) a class defined in another model. "uppose model>. has class>.<D model>G has class>G, and class>.< needs to name>contain (or to be name>contained by) class>G,. :oC &n Model>. &"- imports model>GCCclass>G,. &n Model>. &"- class>.< name>contains (or to be name>contained by) the imported class. &n Model>. ""- the authors decide- on case by case basis- if its "" should define a definition of the imported class (i.e. i norin the fact that the imported class "" e(ists somewhere else) or not.

0.2 ;% ion 1
0.2.1 :se (TM r'ns%or ne wor6 #'se o illus r' e &e !esi2n %' ern
0.2.1.1 8e4ine 2eneri# TP ( er7in' in2 %oin ) 'n! s%e#i4i# TP 3;Cs in <2=

/eplace the J7i ure <.*.,.,C Transport 'etwor# '/M 1ontainmentO'amin and .ssociation dia ramK in A*B with the one below (cardinality not shown)C
>>3n4or7' ion;)?e# Cl'ss@@ M'n'2e!+le7en
(4ro7 T$ 32.622)

>>3n4or7' ion;)?e# Cl'ss@@ Tr'ns%or *e wor63n er4'#e

R2 >>3n4or7' ion;)?e# Cl'ss@@ Generi#PTP R1 >>3n4or7' ion;)?e# Cl'ss@@ Generi#CTP AB;RC R3

>>3n4or7' ion;)?e# Cl'ss@@ +/ ernGeneri#CTP

>>3n4or7' ion;)?e# Cl'ss@@ Generi#CTP

.igure -$!$!$!$!/ Transport 6etwork 6 0 1ontainment76aming and Association diagram The GenericCTP ( eneric channel termination point) and GenericPTP ( eneric path termination point) are potential &O1s that canOshould be ali ned with TM7 "&: based TerminationPoint class (which is based on &T3>T M3,++).

3GPP

elease !!

##

3GPP T 3#$%33 &!!$'$' (#'!#(')"

The /, represents a multiple(in relationship (as defined today)- i.e. multiple 1TPs are multiple(ed onto one PTP. The /*- /3 represent a different type (not same type as /,) of relations that are not yet defined by /elease ,+ of A*B. Mhen two 1TPs are related- it means that the information (e. . bits) comin out of one 1TP is received by the related 1TP (and vise versa). "o- if RNCFunction has (via a TransportNetworkInterface) an ATMChannelTerminationPoint-A which is related to another ATMChannelTerminatedPoint-X- most probably the latter is not that of NodeBFunction. The latter can be an ATMChannelTerminationPoint of an element (e. . .TM switch) of the .TM'etwor# (see .nne( . of A*B.) Today- a M&0 can contain &O1 instances of names usin !ternX"# or X"#. .ll the instances whose names usin X"# are within the mana ement scope of the &/P. ent maintainin the M&0. The 2(ternGy! instances are representation of entities that are outside the mana ement scope of the subject &/P. ent. 7or the 7M1 wor#- we would e(tend the capability (or semantics) of !ternX"# to represent entities that are modelled (or defined) by another ":Os specification and whose definition is recommended for use by 3GPP to support 7M1 networ# mana ement. Me su est the followin attributes that are essential for this 2(ternGy!
Attri2ute name id e!ternal ntit"Id ead 8ualifier M M 9rite 8ualifier M M 1omments 8* o4 &e 3;C ins 'n#e 3!en i4i#' ion o4 &e en i 9 re%resen e! )9 +/ ern'lB9D. T&e i!en i4i#' ion is %ri7'ril9 use4ul 4or &e e/ ern'l !o7'in 7'n'2er 7'n'2in2 &' e/ ern'l en i 9. 34 &e e/ ern'l !o7'in 7'n'2er is 3RP #o7%li'n , &en &is ' ri)u e #'rries ' 8*. 34 &e e/ ern'l 8M is 3RP #o7%li'n , &is #'rries 'n IRP%ersion. 34 i is no , &en i is ' s rin2 w&ose %re#ise s9n '/ is TE8 (we &'5e o 4irs i!en i49 &e $8; in5ol5e! 'n! un!ers 'n! i s w'9 o4 n'7in21i!en i49in2 7o!el s%e#i4i#' ions.)

model$pecificationId

0.2.1.2

(sso#i' e s%e#i4i# lin6 wi & s%e#i4i# TP in s%e#i4i# *RM 3RPs

.dd the ATMChannelTerminationPoint &O1 in 7i ure 9.*.,.< of A3B. Ma#e an association between it and Iu&'ink as in 7i ure ;.,.,.*.,.
>>3n4or7' ion;)?e# Cl'ss@@ (TMC&'nnelTer7in' ionPoin
(4ro7 T$ 32 012)

associatedWith

>>3n4or7' ion;)?e# Cl'ss@@ 3u)"in6

.igure -$!$!$#$!/ Association 2etween ATMChannelTerminationPoint and IubLink

3GPP

elease !!

#3

3GPP T 3#$%33 &!!$'$' (#'!#(')"

0.2.2 (%%l9 &e !esi2n %' ern (!is#usse! in 0.1.1) 4or $1-MM+ re4eren#e %oin
This section is an illustration on usin the desi n pattern (discussed in ;.,.,) for lin#s used in /eference Point ",>MM2. .dd the X"#ChannelTerminationPoint &O1 in 7i ure 9.*.,.3 of A8B. Ma#e an association between it and 'ink- NB(MM as follows. 'ote that the name X"#CTP used here is simply a place>holder>name for now. This &O1 is either defined by ".8 in A*B or will be defined by an ":O (yet to be identified) and recommended for use in A*B. This e(act name of this &O1 will be decided later.

>>3n4or7' ion;)?e# Cl'ss@@ MM+Fun# ion

$1-MM+ re4 %oin

>>3n4or7' ion;)?e# Cl'ss@@ "in6F+*EFMM+

associatedWith >>3n4or7' ion;)?e# Cl'ss@@ B9DCTP

(4ro7 T $ 32 012)

>>3n4or7' ion;)?e# Cl'ss@@ +*EFun# ion

(4ro7 T$ 32.062)

.igure -$!$#$!/ 53tended 5P1 6 0 1ontainment76aming and Association:#

3GPP

elease !!

#*

3GPP T 3#$%33 &!!$'$' (#'!#(')"

0.3

;% ion 2

0.3.1 Con e/
The followin is a description of the conte(t under which such pattern use is appropriateC &/P. ent>. has a mana ement scope (responsibility) over mobile and transport networ# resources. The mobile networ# resource model is developed and maintained by 3GPPO".8 while the transport networ# resource model is developed and maintained by another or ani!ation.

The approach is to use "ub'etwor# &O1 to name>contain the transport networ# resource model. 3sin a hypothetical .TM transport networ# resource as an e(ample- the .TM transport networ# resource model would ta#e the place of the QQPro(y1lassRR.ny (of A,3B). "ee .ppendi( . for ease of reference.

0.3.2

Pro#e!ure

To illustrate the use of this pattern we use a hypothetical case when 3T/.' lin# resources A,+B are supported by .TM transport services- defined by the .TM model A,,B (see .ppendi( 0)- ori inally desi ned in .TM 7orum but now maintained by 007. ,) 1reate a new T" and in this hypothetical case- the .TM '/M &/P. *) &n the new T"- ma#e &mport statements to import all relevant Mana ed Object 1lass (see 'ote) definitions and their correspondin 'ame 0indin s found in A,,B- in particular- those of vc5ayer'etwor#:omain and vp5ayer'etwor#:omain. 'ote ,C The term Mana ed Object 1lass in A,,B encompasses the meanin of the two terms used in &/P 7ramewor#- namely Mana ed Object 1lass and &nformation Object 1lass. 3) &n the new T"- declare (e. . draw in the 1lass :ia ram) vc5ayer'etwor#:omain and vp5ayer'etwor#:omain classes to be name>contained by "ub'etwor# &O1. <) Ma#e sure the .TM1hannelTerminationPoint &O1 of A,+B has all the attributes of atm'etwor#1TP M.'.G2: O0S21T 15."" of A,,B. 'ote *C The .TM1NannelTerminationPoint &O1 does not e(ist in current version of A,+B. &t will be present in future version when Option , (described in section <., and <.* of A<B is implemented in A,+B.

3GPP

elease !!

#+

3GPP T 3#$%33 &!!$'$' (#'!#(')"

M'n'2e7en Con5er2en#e Re#o77en!' ions

This study assumes a truly conver ed O"" where the silos between the mana ement systems for the different networ# technolo ies are removed. This study loo#s at functionalities and use cases for a real end to end mana ement bein enabled by this architecture. The fra ments investi ated include 7ault Mana ement- Performance Mana ement and 1onfi uration Mana ement. The analysed use cases show that more insi ht in the networ# performance can be ained- and that confi uration processes can have more automation. This helps to reduce OP2G. &t is hence recommended to further investi ate this topic- and to specify standardi!ed solutions in case reEuired.

3GPP

elease !!

#,

3GPP T 3#$%33 &!!$'$' (#'!#(')"

(nne/ (, *'7e-Con 'in7en Cl'ss !i'2r'7 4ro7 T$ 32.622 <12=

Nere is a class dia ram e(tracted from A,*B.

-7'n'2er 0..n >>3n4or7' ion;)?e# Cl'ss@@ M'n'2e7en *o!e 0..n 1 >>n'7es@@ 0..n 0..n >>n'7es@@ 0..n >>3n4or7' ion;)?e# Cl'ss@@ MeCon e/ 0..1 >>n'7es@@ >>n'7es@@ 1 1 0..1 >>n'7es@@ 0..1 >>n'7es@@ 1 0..n >>3n4or7' ion;)?e# Cl'ss@@ $u)*e wor6 1 >>n'7es@@ 1 >>n'7es@@ 0..n >>Pro/9Cl'ss@@ (n9 ManagementScope

0..n >>n'7es@@ >>3n4or7' ion;)?e# Cl'ss@@ Link

>>3n4or7' ion;)?e# Cl'ss@@ 3RP(2en 1

0..n >>n'7es@@

>>n'7es@@

1..n >>$u%%or 3;C@@ ManagedGenericIRP

!rom 32"312#

0..1 1

0..n 0..n -su)or!in' e

>>3n4or7' ion;)?e# Cl'ss@@ M'n'2e!+le7en

>>Pro/9Cl'ss@@ (n9 1 >>n'7es@@ >>3n4or7' ion;)?e# Cl'ss@@ Top 1 0..n >>3n4or7' ion;)?e# Cl'ss@@ Vs8' 'Con 'iner 1 >>n'7es@@

>>3n4or7' ion;)?e# Cl'ss@@ Managed$%nction

1 >>n'7es@@ 0..n >>Pro/9Cl'ss@@ (n9 >>3n4or7' ion;)?e# Cl'ss@@ EP_RP

(n o% ion'l no e &' #'% ures &e #ons r'in s &' &is (n9 re%resen s.

3GPP

elease !!

#-

3GPP T 3#$%33 &!!$'$' (#'!#(')"

(nne/ E, Con 'in7en 8i'2r'7 4ro7 M. *e wor6 View CM3P M3E $%e#i4i#' ion
The followin is the 1ontainment :ia ram from A,,B.

3GPP

elease !!

#%

3GPP T 3#$%33 &!!$'$' (#'!#(')"

(nne/ C, Erie4 !es#ri% ion o4 F*M

This .nne( contains e(tracts from section 9 of A,<B that briefly hi hli hts the 7'M architecture related to models for 7'M 'M mana ement.

J 9 2lements of the 7'M This section describes the two #ey elements of 7'M in terms of fra ment relations (9.,) and production of model definitions specifications (9.*). *N is a 7ederation of Models for the purpose of 2nd>to>2nd Mana ement- consistin of an 3mbrella Model and a series of :omainOTechnolo y>specific 1oncrete Models. The 3m1rella odel provides abstract definitions applicable across :omainOTechnolo y>specific 1oncrete Models to enable end>to>end consistency of such definitions (it is described as TabstractP in the sense that its components are inherited by :omainOTechnolo y>specific 1oncrete Models- and that it is not desi ned for the purpose of partial or full instantiation of its components and therefore not sufficient to provide meanin ful networ# mana ement service). :omainOTechnolo y>specific Con(rete odels are described as Tconcrete modelsP in the sense that their instantiation is necessary to provide meanin ful mana ement services. These :omainOTechnolo y>specific 1oncrete Models inheritin common definitions from the 3mbrella Model for the purpose of end>to>end consistency of mana ement information semantics. &n addition- these :omainOTechnolo y>specific 1oncrete Models have defined relationships between each other to enable end>to>end monitorin and mana ement of a conver ed networ#.

6.1 Rel' ions )e ween 4r'27en s 'n! :7)rell'

This section is a raphical representation of the 7'M in terms of relation between fra ments and the 3mbrella. There are two areas under study currentlyC The definitions of the classes inside the 3mbrella. The definitions of relation (/+) used between various classes in fra ments and the 3mbrella classes.

Me aim to have identical /+ for use by all fra ments. The relation is not symmetrical in that the 3mbrella classes need not have #nowled e of its usa e by fra ment classes. This would uarantee a form of consistency (e. . resource mana ement style- paradi m) for mana in mobile mana ed resources- as well as other mana ed resources such as transport mana ed resources.

.igure 1$!/ elation 2etween fragments and ;m2rella 4

3GPP

elease !!

#)

3GPP T 3#$%33 &!!$'$' (#'!#(')"

(nne/ 8, *e wor6 M'n'2e7en rel' e! T3$P(* $ 'n!'r!s

There are activities in T&"P.' for 1onver ed Mana ement ('G' is eEuivalent to conver ed mana ement). The followin documents provide hi h level definitions and scenarios documented by T&"P.'. These should be treated as references as wor# is pro ressed for conver ed mana ement in 3GPP. ,. T/ ,@@ ++< is the startin point. &t provides the 'G' Mana ement ?ision. Mith the 'G' networ# architecture and eTOM as iven- it considers customer reEuirements- business reEuirements and re ulatory aspects and derives a hi h level view on 'G' mana ement. T" ,@@ ++3 provides 'G' Mana ement reEuirements. They are collected from a variety of sources and are consolidated into a set of uniEue reEuirements rouped into a number of classes T" ,@@ ++, specifies the 'G' Mana ement architecture. T" ,@@ ++8>, contains the reEuirements for the 'G' 'etwor# /esource Model. >* contains the '/M &" specification.

*. 3. <.

.ll these docs are publicly available via httpCOOpda.etsi.or OpdaOEueryform.asp

3GPP

elease !!

3'

3GPP T 3#$%33 &!!$'$' (#'!#(')"

(nne/ +, C&'n2e &is or9

1hange history
4ate 2010-08 2010-10 2010-10 2010-12 2011-01 2011-03 2011-06 2012-05 2012-05 2012-05 2012-08 2012-09 TSG < -------TSG 4oc$ -------1 -------ev Su2ject71omment -$6ele on 'n! 7' eri'l 4ro7 $5-102223 -:%!' es 4ro7 Con5er2e! M'n'2e7en (!-Go# -MCC1'D Cle'n-u%s -(!!i ions 4ro7 $5-103109 'n! $5-103110 ($(5H0.) -(!!i ions 4ro7 $5-110505 ($(5H05) -(!!i ions 4ro7 $5-111201, $5-111306 ($(5H06) -(!!i ions 4ro7 $5-112089, $5-111800, $5-111801, $5-111802 ($(5H00) (!!i ions 4ro7 $5-1129.2 'n! $5-1129.3 ('2ree! ' $(5H09), 'n! 4ro7 $5-120650 ('2ree! ' $(5H82) $o7e e!i ori'l #&'n2es $en o $( 4or in4or7' ion (!!e! 3n ro!u# ion, $#o%e 'n! Re#o77en!' ion, e!i ori'l #le'nu%. :%!' e o Rel-11 5ersion (MCC) =ld -0.1.0 0.2.0 0.2.1 0.3.0 0...0 0.5.0 0.6.0 0.0.0 0.0.1 1.0.0 1.1.0 6ew 0.1.0 0.2.0 0.2.1 0.3.0 0...0 0.5.0 0.6.0 0.0.0 0.0.1 1.0.0 1.1.0 !!$'$'

3GPP