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

2 (2013-03) Fixed Mo ile !onvergence "FM!# Technical Report 3GPP $ TM Forum concrete model relationships and use cases "%elease &&#

3GPP TR 32.854

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 "eport 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 "eports for implementation of the 3GPP TM system should be obtained via the 3GPP Or ani!ational Partners% Publications Offices.

%elease &&

'

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

&eywords
NGMN, NGCOR, Converged Managemen , !N"M, #"M

3GPP Postal address 3GPP support office address

$50 Ro% e de& '%()o*e& - +o,-)a .n ),o*)& Va*/onne - !R.NC0 Te*.1 233 4 32 34 42 00 !a41 233 4 33 $5 45 1$

'nternet
- ,166777.3g,,.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$' 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'()*+ ,&&(-(' "'-&3.-3#

Con en &
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 'ntroduction...............................................................................................................................................9 - $cope......................................................................................................................................................: + "eferences..............................................................................................................................................: 3 ;efinitions and abbreviations.................................................................................................................<
3.- ;efinitions..............................................................................................................................................................< 3.+ /bbreviations.........................................................................................................................................................<

8 /ssurance = 7ault 5ocation 1onte)t......................................................................................................>

8.- Operator /ctivity 1onte)t description...................................................................................................................> 8.+ Operator re?uirements covered..............................................................................................................................> 8.3 $pecific use cases...................................................................................................................................................> 8.8 $tyli!ed networ#...................................................................................................................................................-, 8.9 Problem statement usin styli!ed networ# model e)amples................................................................................-8.@ $olution proposal.................................................................................................................................................-3 8.: Potential mana ement environment solution forms.............................................................................................-9

9 7ulfilment = $ervice construction conte)t............................................................................................-: @ 7ulfilment = 2n ineerin wor#s conte)t..............................................................................................-< : 1omplete model proposal.....................................................................................................................->
:.- (avi able lin# from mobile to bac#haul networ#................................................................................................->

Annex A: Change history.............................................................................................................22

3GPP

%elease &&

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

!ore7ord
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 reAreleased by the T$G with an identifyin chan e of release date and an increase in version number as followsB Cersion ).y.! whereB ) the first di itB - 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. corrections. updates. 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.

3GPP

%elease &&

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

"n rod%( )on

OnA oin industry conver ence and pressure to reduce cost is placin everAincreasin emphasis on the need to rationali!e and ali n various networ# mana ement aspects across boundaries of standardsEspecifications producin or ani!ations. The cost. resultin from inte ration and mana ement challen es. of the lac# of a coherent treatment of the whole networ# is becomin increasin ly apparent to the point where operators of networ#s are demandin action. To drive for action the operators are developin re?uirements that articulate aspects of the problem to be tac#led. 'n addition '$C and e?uipment vendors are also developin re?uirements. The intention from these two activities is to develop a consistent and complete set of re?uirements to cover the problem space. /nalysis of these re?uirements led to the identification of a number of use cases that hi hli ht detailed e)amples of the problems and enable solutions to these problems to be e)plored (notin that durin the process described here the use cases were confirmed appropriate valuable cases to cover). 't is intended that throu h these onA oin e)plorationsB $pecific relationships between 3GPP model elements and TM 7orum model elements can be identified Overlaps of the 3GPP and TM 7orum models can be hi hli hted Gaps in modellin . where neither 3GPP nor TM 7orum provide suitable capability. can be plu ed

This documentB 1aptures the use cases considered e)plainin them in the conte)t ofB The re?uirements and scenarios that occur as a result of 7M1 "eal application needs described in terms of an operator activity conte)t

;evelops the use cases to the form of detailed scenarios 2)plainin a stylised networ# dia ram Fomin in on the critical area of interaction

Provides pictorial forms for the model interaction $howin the essence of the model relationships Offerin a familiar and penetrable form

Provides detailed formal views of the model interactions These are in 3M5 form

Offers a specific solution "esultin from an evaluation of various proposals not captured in the document

3ses the use cases and re?uirements to validate the recommendation Provides views of the interrelationship between models to achieve the support for the solution in 3GPP and TM 7orum

The wor# covered by this document was carried out as part of the 3mbrella model activity G+H. as there is interplay between these two areas. 0oth activities drew from and fed into each other. Throu h the pro ression described above there was close and appropriate en a ement of operator as well as the wider 3GPP and TM 7orum community. This involved en a ement in the process ofB 1hoosin the cases for analysis with focus on the relationship to operator re?uirements

3GPP

%elease &&

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

1onfirmin the appropriateness of the detailed scenarios especially in the conte)t of the pictorial form of the model interactions Calidatin the solution proposals at both a hi h level and a detailed level especially in the conte)t of the solution phasin

This led to focus on areas of the model for intense ali nment and to the development of mechanisms for model interrelationship. The proposal set out in this document supports the Objectives set out in 819. This document proposes some specific structure of model and realisation of that structure across 3GPP and TM 7orum. The proposal ta#es advanta e of the TM 7orum 'nformation 7ramewor# ($';) G3H and the TM 7orum 'nte ration 7ramewor# (MT(MEMTO$') G8H and 3GPP $/9 roup wor# G9H (("M '"Ps etc.). The proposal provides an initial pra matic solution for reduction in cost of inte ration and improvement of de ree of inte ration for the purpose of 2ndAtoA2nd mana ement for a specific aspect of the problem.

3GPP

%elease &&

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

+(o,e

This document sets out a number of independent operator activity conte)ts where each conte)t has been chosen to e)ercise one or more of the operator re?uirements and to lead to points of intersection of the networ# model wor# of 3GPP and TM 7orum where some de ree of harmonisation would conse?uently seem valuable. 2ach conte)t description focuses on one or more use cases that suitably describe the relevant details of that operator activity with respect to an e)pected area of intersection. The use cases are first e)plained and then depicted via one or more styli!ed networ# and model dia rams. The model dia ram is then developed to a formal model structure. 7inally the set of chan es proposed cumulated from all conte)t analyses are provided as a coherent recommendation. "espective concrete models must use this model to support the 7M1 use cases to claim 7M1 networ# mana ement compliance. 't should be noted that the 3'M cannot be used directly for implementation. 'mplementation classes must be derived from those in the 3'M by 'nheritance or some other appropriate mechanism. 1lasses derived from those in the 3'M (e. . for the fi)ed environment) must use different names from those used in the 3'M. This content of this document has been jointly developed by 3GPP and TM 7orum as part of the Ioint Jor#in Group on "esource Model /li nment G--H.

2
A A A

Re:eren(e&
"eferences are either specific (identified by date of publication. edition number. version number. etc.) or nonAspecific. 7or a specific reference. subse?uent revisions do not apply. 7or a nonAspecific reference. the latest version applies. 'n the case of a reference to a 3GPP document (includin a G$M document). a nonAspecific reference implicitly refers to the latest version of that document in the same Release as the present document. 3GPP T$ 3+.-,:B K7i)ed Mobile 1onver ence (7M1) 7ederated (etwor# 'nformation Model (7('M)L 3GPP T$ +<.@+,B K7i)ed Mobile 1onver ence (7M1) 3mbrella 'nformation Model (3'M)L TM 7orum G0>++B K'nformation 7ramewor# ($';) $uite. "elease >.,L (httpBEEwww.tmforum.or Ebrowse.asp)Mcat';N>+<9OartfNartf+,8<) TM 7orumB KMTO$' +.,L (httpBEEwww.tmforum.or EMTO$'"elease+,EMTO$'$olution$uiteE39+9+Earticle.html) 3GPP T$ 3+.@++B KGeneric networ# resources '"PB ("ML 3GPP T$ 3+.-9@B K7i)ed Mobile 1onver ence (7M1) Model "epertoireL (GM(B K(G1O" (e)t Generation 1onver ed Operations "e?uirementsL. C-.3 3GPP T" 3+.<33B K$tudy on Mana ement of 1onver ed (etwor#sL 3GPP T" 3+.<93B K3GPP $/9 A TM 7orum T'P 7ault Mana ement Farmoni!ation 7inal report from the Ioint Jor# Group ad hocL 3GPP T$ 3+.:-+ Transport (etwor# (T() interface (etwor# "esource Model (("M) 'nte ration "eference Point ('"P)D 'nformation $ervice ('$)

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

G-H G+H G3H G8H G9H G@H G:H G<H G>H G-,H

3GPP

%elease &&

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

;e:)n) )on& and a//rev)a )on&

7or the purposes of the present document. the terms and definitions iven in T" +-.>,9 G-+H and the followin apply. / term defined in the present document ta#es precedence over the definition of the same term. if any. in T" +-.>,9 G-+H. 7or definitions. symbols and abbreviations not found here see also G-H. G+H and G@H.

3.1 ;e:)n) )on&

(o specific terms were defined durin the eneration of this document.

3.2 .//rev)a )on&

7or the purposes of the present document. the abbreviations iven in T" +-.>,9 G-+H 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" +-.>,9 G-+H. 1P2 1TP 2M$ 2th M2 (2 (M$ (O1 (J O1 O$$ PTP $;F $5/ TP TP2 1ustomer Premises 2?uipment 1onnection Termination Point 2lement Mana ement $ystem 2thernet Mana ed 2lement (etwor# 2lement (etwor# Mana ement $ystem (etwor# Operations 1enter (etwor# Operations 1enter Operations $upport $ystem Physical Termination Point $ynchronous ;i ital Fierarchy $ervice 5evel / reement Termination Point Termination Point 2ncapsulation

3GPP

%elease &&

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

.&&%ran(e < !a%* 'o(a )on Con e4

4.1 O,era or .( )v) = Con e4 de&(r), )on

This operator activity conte)t focuses on the location and repair of a fault. / number of fault e)amples are used. 2ach fault e)ample is chosen at a point in the networ# where it will cause an effect in both the wireless and wireAline part of the networ#. The e)amples are used to ether to demonstrate improvements in the operations characteristics that could be achieved by interconnectin and harmoni!in the TM 7orum and 3GPP models. The descriptions focus on the detection of the alertin of the presence of a fault. The descriptions assume a fault location and repair process but do not impose any particular detail on that process. The primary focus is on the relatin of reports of problems from the two networ# fra ments (3GPP 1oncrete Model and TM 7orum 1oncrete Model) rather than the rationalisation of the specific report details (covered by the other harmonisation activity G>H).

4.2 O,era or re>%)remen & (overed

/ #ey focus is ?uality of alarms and ease of interrelationship of those alarms (see G<H).

4.3 +,e():)( %&e (a&e&

$cenario / conver ed "adioETransport networ# is operated from a sin le (etwor# Mana ement $ystem ((M$). bein part of a (etwor# Operations 1enter ((O1). The scenario is as followsB Problem occurs in the networ# /larms are enerated by systems mana ed via the 3GPP model and the TM 7orum model

(etwor# 1onte)t The O1 mana es all (etwor# 2lements ((2) of both the radio networ# and transport networ#. The networ# is operational The radio networ# elements are mana ed usin a 3GPP mana ement approach and the transport networ# is mana ed usin a TM 7orum mana ement approach. The radio networ# element includes transport networ# terminations.

;escription 7ault location system in the (M$ receives alarms from both the radio (2 and the transport (2 and interrelates them usin networ# and temporal information 7ault location system identifies the PrimaryE"oot 1ause alarm(s)Eevent(s) $ervice impact system identifies de ree of impact and criticality of repair "epair action initiated /larms clear and services are restored

'mplications 'n a normal networ# there will be severalEmany simultaneous problems and wor# activities to be balanced. The networ# operator will want to prioritise scarce maintenance resource to fi) the problems and to choose the ri ht

3GPP

%elease &&

&-

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

se?uence of actions to ma)imise return. Therefore #nowin both the root cause and location of the fault and the de ree of impact from each fault is vital. 'n order to solve the root cause for the radio networ# problem efficiently the O1 needs to et information on the alarms in the underlyin transport networ# and radio networ#s in a consistent and interAconnected model form so as to be able to easily interrelate the alarms.

4.4 + =*)?ed ne 7or@

/ basic networ# has been chosen to simplify the consideration and a simple fault in the optical networ# has been chosen to hi hli ht the case.

Figure &2 3xample net4or5 configuration 6 high level

Figure '2 3xample net4or5 configuration 6 detailed 6 layered vie4 718 /s a result of the fault in the optical networ# delivery there is eitherB ;e radation of service due to errors /ssumes that the failures are soft so as not to cause the protection schemes to activate but sufficient to cause errors and low level impact on the service sufficient to push it outside $5/

3GPP

%elease &&

&&

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

;e radation of service due to reduced capacity Jhere an optical system has failed and althou h there are other systems providin alternative feed the networ# is loaded at pea# such that under this failure scenario there is some de ree of overboo#in of the networ# durin pea# usa e

5oss of resilience Jhere the networ# has capacity to carry all necessary traffic even with the specific optical failure but there is now insufficient capacity to enable en ineerin wor#s on other optical systems and the overall networ# is at ris# of de radation or loss of service if there are any further failures

5oss of service Jhere there has been a failure in one or more optical systems as a result of shared ris# or misfortune such that the capacity of the networ# has dropped to a point where some service is lost.

0ased upon the wor# prioritisation consideration noted in an earlier section the operator will need to understand both the location of a fault and its impact for each of the above cases. 1learly any ambi uity especially the appearance of two separate faults where there is actually one fault and a conse?uence will waste valuable maintenance resource. 't is therefore vital that in each case location clarity can be achieved.

4.5 Pro/*em & a emen %&)ng & =*)?ed ne 7or@ mode* e4am,*e&
The position of the fault hi hli hted on the earlier networ# dia ram is ma nified in the followin dia rams. Prior to hi hli htin the fault positionin it is important to show an e)ample of the arran ement of mana ement solution components in the mi)ed wirelessAwireAline solution and the positionin of some of the #ey model entities.
Management System

OS S 3GPP Model IRP Agent IRP Agent Scope

Function e*g* eNo"e+ $unction

TM Forum Model EMS2 EMS2 Scope

Network Element TM Forum Connection Termination Point TM Forum Physical Termination Point !PPManage" Function

Note that there is generalise" co,erage $or trans(ort ca(a)ilities in the !PP mo"el )ut this re-uires ,en"or e.tension*

Function e*g* IRP Trans(ort Entities NE with wireless access ire!line NE

Note that the scenario is sim(li$ie" )y consi"ering only a single "irection o$ tra$$ic**
#irection o$ tra$$ic NEto EMS % IRP Agent local inter$ace !PPIRP Agent to OSSinter$ace TM Forum EMSto OSSinter$ace &MTNM%MTOS I' O(tical $i)er

Figure 32 3xample of current deployment context using unrelated concrete models The fi ure above shows a deployment scenario usin unrelated concrete models. The fi ure shows two (2s. one wireless and one wireAline bein mana ed by two separate mana ement solutions. one based upon 3GPP and one based upon TM 7orum. both feedin to a sin le O$$ where some form of networ# mana ement is bein performed that includes fault localisation. The fi ure shows the unrelated TM 7orum and 3GPP classes that would represent aspects of behaviour of the respective (2s. There would be many other classes in the models for the (2s but only the classes shown are considered relevant in the followin cases. 't should be noted that the TM 7orum Physical Termination Point

3GPP

%elease &&

&'

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

and 1onnection Termination Point combination represents the optical port. its layersEprotocols and its fle)ible connection termination capability. This scenario can be eneralised to emphasise the model differences as below. The fi ure intentionally does not show the mana ement structure. as this is (OT the focus of this document.
Management En,ironment

Network Element TM Forum C onnection Termination Point TM Forum Physical Termination Point !PPManage" Function

3GPP!S A" Scope

Function e*g* eNo"e+ $unction

TM Forum Scope

Note that there is generalise" co,erage $or trans(ort ca(a)ilities in the !PP mo"el )ut this re-uires ,en"or e.tension*

Function e*g* IRP Trans(ort Entities NE with wireless access ire!line NE

Note that the scenario is sim(li$ie" )y consi"ering only a single "irection o$ tra$$ic**
#irection o$ tra$$ic Management in$ormation $low O(tical $i)er

Figure +2 Generalised form of current deployment context using unrelated concrete models The ne)t two fi ures show the location of alarms in the models under two different fault scenarios. The first is a unidirectional fibre brea# and the second is a laser fail.
Management En,ironment

Network Element TM Forum Connection Termination Point TM Forum Physical Termination Point !PPManage" Function

3GPP!S A" Scope

Function e*g* eNo"e+ $unction

TM Forum Scope

#
Function e*g* IRP Trans(ort Entities NE with wireless access

Position o$ $ault Alarm (oint #irection o$ tra$$ic Management in$ormation $low O(tical $i)er

ire!line NE

Figure *2 Alarm positioning for 9Fi re :rea5; case

3GPP

%elease &&

&3

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

(oteB Jith respect to the red circle in the e(ode0 function it is reco nised that under some conditions there will be no alarm either due to resilience or due to the alarm on the e(ode0 function will be suppressed in the (2 with wireless access by the alarm on the Transport 2ntities. Fowever there are often more subtle scenarios where de radations could not be suitably apportions. 'n addition the indication may be necessarily e)posed not suppressed to indicate a service impact. 'n the fibre brea# case shown above. one indication of the problem is from the (2 with wireless access. 't should be noted that there is no standardised entity in the 3GPP ("M a ainst which to report the fibre fail.
Management En,ironment

Network Element TM Forum Connection Termination Point TM Forum Physical Termination Point !PPManage" Function

3GPP!S A" Scope

Function e*g* eNo"e+ $unction

TM Forum Scope

#
Function e*g* IRP Trans(ort Entities NE with wireless access

Position o$ $ault Alarm (oint #irection o$ tra$$ic Management in$ormation $low O(tical $i)er

#
ire!line NE

Figure /2 Alarm positioning for 9<aser Fail; case 'n the laser fail case shown above there is an indication of a problem from the (2 with wireless access that is identical to the indication in the fibre brea# case. and there is also an indication of a problem from the wireAline (2 that is raised a ainst the port represented by the TM 7orum Physical Termination Point. 3sin the current solution as depicted above there is no relationship between the alarmed '"P Transport entity (of the wireless (2) and the alarmed TM 7orum Physical Termination Point (of the wireAline (2) and as a conse?uence analysis (e. . correlation) of the alarms will prove difficult. Fence it can be ar ued that the ?uality of the alarm reportin in these scenarios can be improved from the perspective of fault isolation (a primary process of the Mana ement 2nvironment) by better interrelationship of the model representations of the two (2s.

4.$ +o*% )on ,ro,o&a*

The followin solution proposal introduces #ey model interrelationships that would better enable fault isolation. This solution description incorporates further classes from the current models. the 3GPP 5in# and the TM 7orum Topolo ical 5in#. and show how they can be interrelated. The solution also show the introduction of necessary aspects of the Physical Termination Point concepts and 1onnection Termination Point concepts into the (2 with wireless access in reco nition of the fact that the wireAline protocols terminate in that (2 and hence a representation of those protocol termination is re?uired. The necessary aspects of these Termination Point concepts support the capabilities and relationships hi hli hted by the use case depicted in 7i ure :B Topolo ical 5in# between the two (2%s with wireless access Topolo ical 5in# between one of the two (2%s with wireless access to this ed e node of the transport networ#D

3GPP

%elease &&

&+

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

Jhere this Topolo ical 5in# is supportin the 5in# between the two (2%s with wireless access.

"elationship to physical port "elationship to a function in the (2 with wireless access e. . 2(07unction Place a ainst which to raise transport alarms

'n both fault cases shown in the fi ures below the si nal fail alarm on the (2 with wireless access will be raised a ainst enhanced '"P Transport entities (that have incorporated the Physical Termination Point concept) and in the 5aser 7ail case the alarms at both ends of the fibre can be related via an understandin of the Topolo ical5in# between the Physical Termination Point and the enhanced '"P Transport entity. The Topolo ical5in# between the two (2s may be discovered from the networ# if appropriate discovery protocols are enabled or may be operator provisioned. The specific approach to this is not considered further here. The adjacency information related to the Topolo ical5in# will be conveyed to the Mana ement 2nvironment usin the forei n TP capability (3GPP term for this is 2)ternalPy!). This will not be discussed further here as the solutions that are already used in the 3GPP mana ed environment G-,H and in the core of the wireAline environment G8H are suitable.
Management En,ironment

Network Element /ink entity &connecti,ity e*g* 02' To(ological /ink +ase" on C onnection Termination Point conce(t +ase" on Physical Termination Point conce(t !PPManage" Function C onnection Termination Point

Function e*g* eNo"e+ $unction

Physical Termination Point

OR

OR

Position o$ $ault Alarm (oint #irection o$ tra$$ic Association% relationshi( S trong can"i"ate association%relationshi( Alarm in$ormation $low &semantics' O(tical $i)er

NE with wireless access

ire!line NE

NE with wireless access

Figure 02 Alarm positioning for 9Fi re :rea5; case using related concrete models

3GPP

%elease &&

&*

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

Management En,ironment

Network Element /ink entity &connecti,ity e*g* 02' To(ological /ink +ase" on Connection Termination Point conce(t +ase" on Physical Termination Point conce(t !PPManage" Function Connection Termination Point

Function e*g* eNo"e+ $unction

Physical Termination Point

OR

OR

Position o$ $ault Alarm (oint #irection o$ tra$$ic Association%relationshi( S trong can"i"ate association%relationshi( Alarm in$ormation $low &semantics' O(tical $i)er

#
NE with wireless access ire!line NE

NE with wireless access

Figure )2 Alarm positioning for 9<aser Fail; case using related concrete models

4.5 Po en )a* managemen env)ronmen &o*% )on :orm&

/lthou h. as emphasised earlier. the scope of this document is information model conver ence and resolution of the mana ement environment solution is out of scope it is considered important to hi hli ht some mana ement environment deployment considerations that will re?uire further resolution. 't is clear that there are several potential mana ement environment implementation forms that will cater for the introduction of Physical Termination PointE1onnection Termination Point concepts to describe the wireAline ports of (2s with wireless access. One potential form is shown in the followin fi ure where the Physical Termination Point. 1onnection Termination Point and Topolo ical5in# model concepts built into the 3GPP ("M '"Ps and e)posed via 3GPP '"P / ent usin e)ternal references to lin# the two (2s. "e ardless of the structure of the mana ement environment solution. the solution proposal in section 9.@ is considered appropriate and sufficient.

3GPP

%elease &&

&/

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

OS S 3GPP Model IRP Agent IRP Agent Scope

Function e*g* eNo"e+ $unction

TM Forum Model EMS2 EMS2 S cope

Network Element /ink entity &connecti,ity e*g* 02' To(ological /ink +ase" on Connection Termination Point conce(t +ase" on Physical Termination Point conce(t !PPManage" Function Connection Termination Point Physical Termination Point

OR

OR

Position o$ $ault Alarm (oint #irection o$ tra$$ic Association% relationshi( S trong can"i"ate association% relationshi(

#
NE with wireless access ire!line NE

Alarm in$ormation $low &semantics' O(tical $i)er !PPIRP Agent to OS Sinter$ace TM Forum EMSto OSSinter$ace &MTNM%MTOS I'

NE with wireless access

Figure 12 Alarm flo4 through =%P Agent for >3 4ith 4ireless access

3GPP

%elease &&

&0

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

!%*:)*men < +erv)(e (on& r%( )on (on e4

2ditorQs noteB This section is for future consideration and will provide details on another conte)t and will be laid out in the same flow as the /ssurance conte)t. 't may be considered appropriate to move this into a separate document.

3GPP

%elease &&

&)

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

!%*:)*men < 0ng)neer)ng 7or@& (on e4

2ditorQs noteB This section is for future consideration and will provide details on another conte)t and will be laid out in the same flow as the /ssurance conte)t. 't may be considered appropriate to move this into a separate document.

3GPP

%elease &&

&1

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

Com,*e e mode* ,ro,o&a*

2ditorQs noteB This section provides the accumulation of the chan es from the three conte)ts discussed above. 'f the conte)ts are moved into separate documents this section may be yet another document or may be deemed unnecessary.

5.1 Nav)ga/*e *)n@ :rom mo/)*e o /a(@-a%* ne 7or@

/n alarm correlation 3se 1ase is defined 7i ure < (/larm positionin for K5aser 7ailL case usin related concrete models). One '"P/ ent is mana in the wireless (2. /nother a ent is mana in the wireline transport networ# includin the ed e node of transport networ# but e)cludin the 1P2 (namely. the wireless (2). These two a ents would receive alarms from their mana ed elementsD The two a ents forward their received alarms to (M$. (M$ can then correlate the alarms (e. . alarmA- from a wireless (2. the 1P2. is correlated with alarmA<> from transport networ# ed e node)

'n 7i ure <. the two a ents and (M$ are RlumpedQ to ether in a bo) called KMana ement 2nvironmentL. The 7i ure < is redrawn below as 7i ure -,. 7i ure -, introduces names (includin 5in# / and 5in# 0). The named items in the 3se 1ase dia ram (7i ure -,) identify the objects that would be represented by classes (see 7i ure --). 't should also be noted that in 7i ure -, theB 5in# is shown in two possible positions on this and previous dia rams. The 5in# is shown between 1TPs or e(ode0. The eventual positionin of the 5in# will be a 3GPP responsibility. "emote (2 has had detailed items added that aid model e)planation
#
Position o$ $ault Alarm (oint #irection o$ tra$$ic Association% relationshi( S trong can"i"ate association%relationshi( Alarm in$ormation $low &semantics' O(tical $i)er To(ological /ink +ase" on C onnection Termination Point conce(t +ase" on Physical Termination Point conce(t !PP Manage" Function C onnection Termination Point

Management En,ironment

Network Element /ink entity &connecti,ity e*g* 02'

Function e*g* eNo"e+ $unction

Physical Termination Point

/inkA

Function e*g* eNo"e+ $unction

/ink+

NE1
NEwith wireless access

NE2
ire!line NE

NE
NEwith wireless access

Figure &-2 =ntroduce names for t4o o jects of Figure ) and other enhancements

3GPP

%elease &&

'-

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

The proposed model solution depicted in 7i ure --has the followin characteristicsEpropertiesB 't supports the alarm correlation 3se 1ases described in this document. 't models wireless nodes that would use 'PAbased transport servicesD 't supports navi ation from modeled elements of wireless node (a customer premise e?uipment (1P2) from view of the transport networ#) to modeled elements of the ed e node of the transport networ#D 't models the lin#(s) between 1P2sD and 't models the lin# between 1P2 and the transport networ# ed e node.

Figure &&2 !lass diagram for oth 4ireless and 4ireline cases (oteB / wireless 2)ternal1TP is intentionally not shown in the class dia ram. ;efinition of this class is a 3GPP matter.

3sin the class dia ram above an instance dia ram for the networ# case in 7i ure -, can be constructed as shown in 7i ure -+ below.

Figure &'2 =nstance diagram for case sho4n in Figure &-

3GPP

%elease &&

'&

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

7i ure -3 (below) shows the derivation of the wireless and wireline classes from the 3mbrella classes (where the inheritance relationship between the 3mbrella and the other models is used to depict any appropriate derivation mechanism).

Figure &32 ?iagram sho4ing derivation of 4ireless and 4ireline classes

3GPP

%elease &&

''

3GPP T% 3'()*+ ,&&(-(' "'-&3.-3#

.nne4 .1 C-ange -)& or=

!hange history
?ate TSG @ TSG ?oc( !% %ev Su ject$!omment Ald >e4

2012-08 2012-03 2012-10 2012-12 2012-12 2013-01 2013-03

"n) )a* ;ra: /a&ed on 8119 V2.1 +%/m) ed o +.A55 :or "n:orma )on #,da e /a&ed on 8119 V3.0 +%/m) ed o +.A58 :or a,,rova* Ne7 ver&)on a: er a,,rova* !)4ed *a=o% ,ro/*em& !)4ed ) *e o: -e &,e( /= remov)ng a &em)-(o*on

--0.1.0 1.0.0 1.1.0 2.0.0 11.0.0 11.0.1

0.1.0 1.0.0 1.1.0 2.0.0 11.0.0 11.0.1 11.0.2

3GPP