rn312_mtnm_release notes for release3-5 (word)

8/18/2019 RN312_MTNM_Release Notes for Release3-5 (Word)

1/15

TN Release Notes

Release 3.5

RN306

Version 2.1 August 2008

TeleManagement Forum 2007-2009


2/15

MTNM Release Notes for Release 3.5

0B

Notice

No recipient of this document shall in any way interpret this documentas representing a position or agreement of TM Forum or its members.This document is a draft woring document of TM Forum and ispro!ided solely for comments and e!aluation. "t is not a Forum

#ppro!ed $ocument and is solely circulated for the purposes of assisting TM Forum in the preparation of a final document infurtherance of the aims and mission of TM Forum.

#lthough it is a copyrighted document of TM Forum%

• Members of TM Forum are only granted the limited copyrightwai!er to distribute this document within their companies andmay not mae paper or electronic copies for distributionoutside of their companies.

• Non-members of the TM Forum are not permitted to mae

copies &paper or electronic' of this draft document other thanfor their internal use for the sole purpose of maing commentsthereon directly to TM Forum.

• "f this document forms part of a supply of information in

support of an "ndustry (roup )iaison relationship* thedocument may only be used as part of the wor identified inthe )iaison and may not be used or further distributed for anyother purposes

#ny use of this document by the recipient* other than as set forthspecifically herein* is at its own ris* and under no circumstances willTM Forum be liable for direct or indirect damages or any costs or losses resulting from the use of this document by the recipient.

This document is go!erned by all of the terms and conditions of the #greement on "ntellectual +roperty ,ights between TMForum and itsmembers* and may in!ol!e a claim of patent rights by one or more

TMForum members or by non-members of TMForum.

$irect inuiries to the TM Forum office%20 /eaduarters +laa*1ast Tower 30th Floor*Morristown* N4 07950 6#Tel No. 83 97 9 :300Fa; No. 83 97 9 :330TM Forum


3/15


1B

Table of Contents

Notice.................................................................................................................................................. 2

Table of Contents................................................................................................................................ 3

List of Tables....................................................................................................................................... 3

Overview of MTNM Release 3.5........................................................................................................... 4

ummary of New Features............................................................................................................

>onnectionless Technology Management..................................................................................

#?N >ontrol +ane Management.............................................................................................:

Release Definition............................................................................................................................... 7

$ocument ,elease $escription..................................................................................................... 7

Ma@or $eli!erables.................................................................................................................. 30

Model ,elease $escription..........................................................................................................33

!"inistrative ##en!i$...................................................................................................................%4

$ocument /istory...................................................................................................................... 3

>ontact.......................................................................................................................................3

#cnowledgments....................................................................................................................... 3:

#bout TeleManagement Forum....................................................................................................3:

2B

List of Tables

UTable 3. Main $ocuments in MTNM ,elease .:U 7

UTable 2. upporting $ocuments in MTNM ,elease .: U A

UTable . MTNM ,elease .: $ocument +acagingU 33

,N32* =ersion 2.3 ©TeleManagement Forum 2007-2009 +age of 3:


4/15


3B

Overview of MTNM Release 3.5

MTNM ,elease .: includes two ma@or enhancements of functionality o!er,elease .0. The twoenhancements are%

• >onnectionless Technology Management

• #?N >ontrol +lane Management

>onnectionless Technology Management adds support for the management of >onnectionlessTechnologies with a specific focus in this release on support for 1thernet technology and relatedtechnologies as defined in "T6-T (.A033 and Metro 1thernet Forum &M1F' The term B1thernetC

refers to the 1thernet M#> layer &1T/'.

#?N >ontrol +lane Management adds support for the management of >ontrol +lane established>all and >onnections. "t does not address the configurationDsetup of a >ontrol +lane en!ironmentits focus is on enabling an NM to reuest that >alls be created by the >ontrol +lane and tosubseuently manage those >alls until such time as the >alls are deleted.

6B&'""ar( of New )eat'res

13B

Connectionless Tec*nolo+( Mana+e"ent

The MTNM ,elease .: connectionless solution is primarily targeted at managing 1thernet o!ertraditional or ne;t generation transport networ such as ?N1TD$/*


5/15


• +oint-to-point >all &represent connectionless connecti!ity between N1s' pro!isioning

&including >ontrol +lane option'

• $i!erse routes for point-to-point >alls

• Multipoint Topological )ins &e.g.* for representing ,+, transport connecti!ity'

•

>+T+ pro!isioning• Fi;ed MF$ modelling &e.g.* direct mapped 1+) ser!ices'

• =)#N-unaware routing as per "111 A02.3$

• >-=)#N based tagging as per "111 A02.3E

• -=)#N based tagging as per A02.3ad

• +ort &6N"DNN"'* >-=)#ND1=> andDor >o &A02.3p' based classification

• panning Tree management

• "ngress traffic conditioning

• >-TagD-Tag translation

• Non routed layer 2 networs &using singleton Flow $omains'

• "ntegrated or separate transport &?N1TD$/* etc.' and 1thernet 1Ms

To support the abo!ementioned features the following new terms ha!e been defined%

• Flow $omain &F$'

• Matri; Flow $omain &MF$'

• >onnectionless +ort Termination +oint &>+T+'

• Flow +oint &F+'

• Flow $omain Fragment &F$Fr'

• T> +rofile

14B&ON Control ,ane Mana+e"ent

The MTNM ,elease .: #?N >ontrol +lane solution is primarily targeted at managing >alls and>onnections that may be established through the use of >ontrol +lane protocols.

The >ontrol +lane automates the process for connection setup and tear down in an opticalnetwor. The architecture of the >ontrol +lane is described in "T6-T ,ecommendation (.A0A0.

This architecture pro!ides a separation between the >all &which represents the ser!ice offered tothe user' and the >onnections that deli!er the ser!ice.

The architecture is described in terms of >ontrol +lane components. The communication betweenthese components is separated from the bearer plane that is being controlled. To optimise theperformance of the >ontrol +lane and ma;imie the reuse of e;isting control protocols theaddressing scheme used by the control components to reference the transport resources isindependent of the addressing scheme used by the management applications.

The reuest for a >all can originate from a customer directly !ia a 6N" or from an ? within anoperators networ. For connection reuest from the 6N" the control plane automatically computes

,N32* =ersion 2.3 ©TeleManagement Forum 2007-2009 +age : of 3:


6/15


a route and initiates signalling to establish the connections. "n the case of a reuest from thenetwor operators ? the reuest is directed to the ingress point for the call* the operator maypro!ide may control the routing of the connections by pro!iding an e;plicit route or routingconstraints or allow the >ontrol +lane freedom to compute the route. "n all cases the >ontrol +laneinitiates signalling to establish the reuired connections. The >ontrol +lane can also performautomatic restoration in the e!ent of a traffic plane failure. ontrol +lane may force the >onnections to re!ert to their original &home' route.

To support the abo!ementioned features the following new terms ha!e been defined%

• Multi)ayer ,outing #rea &M),#'

• >all

• >onnection

• Multi)ayer ubnetwor +oint +ool &M)N++'

• Multi)ayer ubnetwor +oint +ool )in &M)N++)in'

• ubnetwor +oint +ool &N++'

• ubnetwor +oint &N+'

,N32* =ersion 2.3 ©TeleManagement Forum 2007-2009 +age 5 of 3:


7/15


4B

Release Denition

This section describes the documents included in MTNM ,elease .:.

7BDoc'"ent Release Descri#tion

#s part of MTNM ,elease .0 all of the documents that were part of that release were baselined at!ersion .0. +rior to ,elease .0 the MTNM documents did not ha!e associated !ersion numbers.

For many of the documents that are specific to the MTNM product release .: is the first time that

the document will ha!e been updated since release .0 of MTNMG with the e;ception of thosedocuments that are also used by the MT?" product.

#ll documents with a Mar 2007 date will ha!e been updated specifically for MTNM ,elease .:. #lldocuments with a ,elease .: !ersion number of greater than .0 but with a date earlier than Mar2007 will ha!e been updated for the MT?" product.

"t should be noted that the B)atest $ateC column in the table reflects the date of the last change tothe document. "t does not necessarily reflect the date on which the document was uploaded to theTMF >ollaboration onnectionless Technology and

#?N >ontrol +lanemanagement.

TMF50A MTNM "nformation

#greement

.0 .: #ug 200A #ddedDupdated 6M) model for

>onnectionless Technology and #?N >ontrol +lanemanagement.

TMFA3 MTNM "$) olution et .0 .2 #ug 200A #ddedDupdated "$) for>onnectionless Technology and

#?N >ontrol +lanemanagement.



8/15


Doc'"ent Title Rel 3.0version

Rel 3.5version

LatestDate

Delta

TMA3# MTNM "mplementationtatement and(uidelines

.0 .3 Mar 2007 6pdated to support changes toTMFA3.

Table 2. &'##ortin+ Doc'"ents in MTNM Release 3.5


Rel 3.5version

LatestDate

Delta

$3-3 #dditional "nformation6sage

.0 .2 #pr 200A #dded new additionalinformation parameterdefinitions.

$3-2 MTNM #ttribute =alue

>hange I tate >hangeNotifications

.0 .2 Feb 200A #dded support for the new

ob@ect classes.

$3- (roup Termiantion+oints and HundledN>

.0 .0 4un 200:

$3- >hanges between "#=ersions

.0 :.0 Mar 2007 ,elease specific detailsupdated.

$3-: #TM >onformance$efinitions

.0 .0 No! 2005

$3-5 >ontained T+s .0 . No! 2007

$3-7 $) ?!er!iew .0 .3 No! 200:$3-A >oding of J.73 and

M.300 tate and tatus"nformation

.0 .2 No! 2007

$3-9 >oding of J.7 #larminformation

.0 .3 No! 2005

$3-30 1uipment Model .0 .3 Mar 2005

$3-33 Feature Matri; .0 No longer part of the release.

>o!ered by this release note

$3-32 ummary of MTNM

,.0 features

.0 No longer part of the release.

>o!ered by this release note.

$3-3 (6" >ut-Through .0 .0 No! 2005

$3-3 "n!erse Multiple;ing?!er!iew

.0 .2 No! 2007

$3-3: "terator 6sage .0 .0 No! 2005

,N32* =ersion 2.3 ©TeleManagement Forum 2007-2009 +age A of 3:


9/15



Rel 3.5version

LatestDate

Delta

$3-35 )ayered +arameters .0 . No! 2007 #dded new layeredtransmission parameterdefinitions.

$3-37 )ayer ,ates .0 . ?ct 2007 #dded new layer ratedefinitions.

$3-3A Functional Modelling>oncepts

.0 . #ug 200A Minor enhancements.

$3-39 )ocation "dentification .0 .0 #pr 200:

$3-20 Maintenance>ommands

.0 .2 No! 2007 #dded new maintenancecommand definitions.

$3-23 Traceability between "#and

.0 .2 4un 2007 ,elease specific detailsupdated.

$3-22 Modelling >omponents .0 .0 #pr 200:

$3-2 N> ManagementModes of ?peration

.0 .0 4un 200:

$3-2 Nati!e 1M Name .0 .0 No!2005

$3-2: Multi-TechnologyNetwor Managementsupport for a Naming>on!ention

.0 . $ec 2007 #dded support for the naming of new ob@ect classes

$3-25 (uidelines for 6sing the?M( Notification andTelecom )og er!ice

.0 .3 Mar 2007 #dded definitions for the newob@ect classes.

$3-27 ?!er!iew of the TMFMTNM NM)-1M)"nterface

.0 .3 Mar 2007 ,elease specific detailsupdated.

$3-2A +erformance+arameters

.0 .3 ?ct 2005

$3-29 +(+ +arameters .0 .0 #pr 200:

$3-0 +M File Format$efinition

.0 .2 $ec 200:

$3-3 +M e;ample te;t file .0 No longer a separate supportingdocument. Now part of $3-0.

$3-2 +M e;ample 1;cel

spreadsheet file

.0 No longer a separate supporting

document. Now part of $3-0.

$3- pecification ofprobable>ause strings

.0 .3 ?ct 2005

$3- +rotection witching .0 .0 #pr 200:

$3-: tate $iagrams .0 .3 Mar 2007 #dded new diagrams for >allstate changes.

$3-5 N> and +rotection .0 .3 Mar 2007



10/15



Rel 3.5version

LatestDate

Delta

$3-7 +M Threshold Types .0 .0 4un 200:

$3-A TMFA3 Front Matter .0 .2 #ug 200A ,elease specific details

updated.$3-9 TMF50A /TM) Front

Matter 0.0 3.0 #ug 200A ,elease specific details

updated.

$3-0 TMF50A M$) FrontMatter

0.0 3.0 #ug 200A ,elease specific detailsupdated.

$3-3 >larification ofrelationship between aT++ool and itsTermination+oints

.0 .0 #pr 200:

$3-2 Traffic +arameters .0 .3 #pr 200:

$3- +rogrammatic

=ersioning

.0 .0 No! 2005

$3- >onnectionlessTechnologyManagement

- 3.3 4un 200A New in this release.

$3-: #?N >ontrol +laneMangement-+rimer

- 3.3 No! 2007 New in this release.

$3-5 #?N >ontrol +laneMangement-cenarios

- 3.0 Mar 2007 New in this release.

15BMa-or Deliverables

The MTNM ,elease .: output consists of ma@or deli!erables* i.e.* Husiness #greement*"nformation #greement* the "$) olution et and the "mplementation tatement.

16BTM)5%3 MTNM /'siness +ree"ent

The MTNM business agreement document pro!ides reuirements and use cases. Thereuirements pertain to the interface itself and describe what is e;pected of an 1M or NM thatsupports MTNM. The use cases pro!ide interaction scenarios concerning 1Ms and NMs thatsupport MTNM.

For someone new to the MTNM specifications* it is recommended that one reads TMF:3 after

reading the MTNM o!er!iew &i.e.* this document'

17BTM)60 MTNM 1nfor"ation +ree"ent

This document contains the protocol independent 6M) model for the MTNM interface. "n additionto being used for MTNM this model has also been used by the MT?" product. /owe!er theMTNM ,elease .: product is a stand-alone product and as such no references to the MT?"product release deli!erables are pro!ide as part of MTNM ,elease .:.



11/15


18BTM)%4 MTNM 1DL &ol'tion &et

This document and associated >?,H# "$) pro!ides the specification for the MTNMimplementation. This deli!erable entails a brief o!er!iew of the MTNM >?,H# "$) interface andthe >?,H# "$) specification itself. The following supporting documents are closely related toTMFA3.

19BTM)%4 MTNM 1"#le"entation &tate"ent

This document pro!ides a template for a compliance statement that is intended to be e;changedbetween two parties that are intending to build an MTNM interface. "t enables each party todetermine e;actly what is supported by both parties implementation.

"n addition to these main deli!erables there are also a number of supporting documents thatpro!ide additional information to better understand the interface and the functionality that itsupports. #lthough these documents by themsel!es are not considered to be a ma@or deli!erablethe collection of supporting documents are essential to understanding the MTNM interface.

8BMo!el Release Descri#tion

The following table describes the !arious file pacages a!ailable for MTNM ,elease .:. Note thateach of the ma@or deli!erables &i.e.* TMF:3* TMF50A and TMFA3' are pacaged along with thesupporting documents that they reference. ,N05 will also be made a!ailable as a separatedocument in addition to be included in each of the three pacages listed in the table below.

Table 3. MTNM Release 3.5 Doc'"ent ,aca+in+

Doc'"ent Title TM)5%3 TM)60 TM)%4 TM)%4

,N32 MTNM .: ,elease Note

TMF:3 MTNM" Husiness #greement

TMF50A MTNM "nformation #greement

TMFA3 MTNM "$) olution et

TMFA3# MTNM "mplematationtatement

$3-3 #dditional "nformation 6sage

$3-2 MTNM #ttribute =alue >hangeI tate >hange Notifications

$3- (roup Termiantion +oints andHundled N>

$3- >hanges between "# =ersions

$3-: #TM >onformance $efinitions

$3-5 >ontained T+s

$3-7 $) ?!er!iew



12/15



$3-A >oding of J.73 and M.300tate and tatus "nformation

$3-9 >oding of J.7 #larminformation

$3-30 1uipment Model

$3-3 (6" >ut-Through

$3-3 "n!erse Multiple;ing ?!er!iew

$3-3: "terator 6sage

$3-35 )ayered +arameters

$3-37 )ayer ,ates

$3-3A Functional Modelling >oncepts

$3-39 )ocation "dentification

$3-20 Maintenance >ommands

$3-23 Traceability between "# and

$3-22 Modelling >omponents

$3-2 N> Management Modes of?peration

$3-2 Nati!e 1M Name

$3-2: Multi-Technology NetworManagement support for aNaming >on!ention

$3-25 (uidelines for 6sing the ?M(Notification and Telecom )oger!ice

$3-27 ?!er!iew of the TMF MTNMNM)-1M) "nterface

$3-2A +erformance +arameters

$3-29 +(+ +arameters

$3-0 +M File Format $efinition

$3- pecification of probable>ausestrings

$3- +rotection witching

$3-: tate $iagrams

$3-5 N> and +rotection

$3-7 +M Threshold Types

$3-A TMFA3 Front Matter

$3-9 TMF50A /TM) Front Matter



13/15



$3-0 TMF50A M$) Front Matter

$3-3 >larification of relationship

between a T++ool and itsTermination+oints

$3-2 Traffic +arameters

$3- +rogrammatic =ersioning

$3- >onnectionless TechnologyManagement

$3-: #?N >ontrol +laneMangement-+rimer

$3-5 #?N >ontrol +laneMangement-cenarios

To better understand how these pacages are actually deli!ered as a set of ip file the followingdocument pro!ides details of the structure of the pacages.

Error! Not a valid link.



14/15


5B

Administrative Appendi

9BDoc'"ent istor(

ersion istor( T*is !oc'"ent

ersion N'"ber Date Mo!ifie! Mo!ifie! b(8 Descri#tion ofc*an+es

0.3 Mar 2007 MTNM Team "nitial !ersion

2.0 #ugust 200A MTNM Team 6pdated to reflect +ostM1 !ersion

2.3 February 2009 Tina ?Kulli!an Minor corrections

Release istor( MTNM Release

Release N'"ber Date Mo!ifie! Mo!ifie! b(8 Descri#tion of c*an+es

.: March 2007 MTNM Team "nitial !ersion

10BContact

For reuests of information or comments concerning this document please contact%

tephen Fratini &mT?+ Team )eader'Telcordia Technologies?ne Telcordia $ri!e,oom ,,>-5E353+iscataway* N4 0AA:

+hone% 83 72 952 3:001mail% HU sfratiniLtelcordia.comUH

eith $oring &MTNM +roduct Manager'>iena >orporation33A: anctuary +arwayuite 00

#lpharetta* (# 000

+hone% 83 57A 5A7 :0071mail% HU doringLciena.comUH


mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]


15/15


11Bcnowle!+"ents

This document was prepared by the members of the TeleManagement Forum MTNM,elease .: team.

12Bbo't TeleMana+e"ent )or'"

TeleManagement Forum is an international consortium of communications ser!icepro!iders and their suppliers. "ts mission is to help ser!ice pro!iders and networoperators automate their business processes in a cost- and time-effecti!e way.pecifically* the wor of the TM Forum includes%

1stablishing operational guidance on the shape of businessprocesses.

#greeing on information that needs to flow from one process acti!ity

to another.

"dentifying a realistic systems en!ironment to support the

interconnection of operational support systems.

1nabling the de!elopment of a maret and real products for

integrating and automating telecom operations processes.

The members of TM Forum include ser!ice pro!iders* networ operators andsuppliers of euipment and software to the communications industry.

rn312_mtnm_release notes for release3-5 (word)

Documents