1 / 16

Information Modelling Task Force Stockholm Meeting Minutes

Information Modelling Task Force Stockholm Meeting Minutes. WP 4 Network Management and Control/Protocols Håkon Lønsethagen, Telenor. Agenda – Intended ;-). 10 min. Brief status and agenda bashing 30 min TMF MTNM CP-MP IM work 30 min LION IM

mckile
Télécharger la présentation

Information Modelling Task Force Stockholm Meeting Minutes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Information Modelling Task ForceStockholm MeetingMinutes WP 4 Network Management and Control/Protocols Håkon Lønsethagen, Telenor WP4 IM TF

  2. Agenda – Intended ;-) • 10 min. Brief status and agenda bashing • 30 min TMF MTNM CP-MP IM work • 30 min LION IM • 20 min Brainstorming and following up the MTNM and LION presentations: Identify Challenges for IM work: Important issues/concepts/ideas that need further considerations • 10 min NMI-A cases to focus on • 15 min Approach/Method for further work – and action points (division of work) • 5 min Wrap up WP4 IM TF

  3. Agenda – Real • 10 min. Brief status • 60 min? NMI-A cases to focus on • 45 min? LION IM • 30 min? Wrap up: Approach/Method for further work – and action points (division of work) WP4 IM TF

  4. Key issues/concepts to address (NOC’04 IM paper – Identifying issues and possible directions) (This slide was not discussed) TBD • See (Alcatel Italy / TMF MTNM contribution on definitions) • MLSC (Multi-Layer Switching Capable) ports and links • Modelling of control node (CN) entities • E.g.: CN entities relative to SCL (Switching Capability Layer) • … WP4 IM TF

  5. NE stereotypes The notion of NE stereotypes is used to identify a few NE types that represents typical NE types, covering NEs for both short term, medium term, as well as long term scenarios.A NE stereotype is typically rich on functionality, functionality that is possible considering its type of NE. • A tentative agreement on the following NE stereotypes and NMI-A cases was reached – see next slides (Case 1a, 1b, 2, and 3) • The following is just a rough sketch of the NE stereotypes • These NE stereotypes should be detailed and elaborated • Other cases – No time for discussion (FFS) • NE stereotypes are useful for describing Use cases; describing interactions over given interfaces of these (No time to discuss how to proceed on these kinds of use cases) • E.g. UNI use case, E-NNI use case, NMI-A use case WP4 IM TF

  6. NE / NMI-A Case 1a • MLSC • TDSC • LSC G.709 • Unified CP • GMPLS/ASON NMI-A, Case 1  GMPLS/ASON  G.709   Client/tributaryports   Colour code: MP CP-1 CP-2 PSC L2SC TDSC LSC WSC FSC WP4 IM TF

  7. NE / NMI-A Case 1a NMI-A, Case 1 UNI NNI WP4 IM TF

  8. Colour code: MP CP-1 CP-2 PSC L2SC TDSC LSC WSC FSC NE / NMI-A Case 1b • MLSC • TDSC • LSCG.709 and Lambda switching • Unified CP • GMPLS/ASON NMI-A, Case 1b GMPLS/ASON G.709 / l WP4 IM TF

  9. Colour code: MP CP-1 CP-2 PSC L2SC TDSC LSC WSC FSC Use Case / NMI-A Case 2 NMI-A, Case 2 IP/MPLS GMPLS/ASON WP4 IM TF

  10. Colour code: MP CP-1 CP-2 PSC L2SC TDSC LSC WSC FSC Use Case / NMI-A Case 3 NMI-A, Case 3 GMPLS/ASON WP4 IM TF

  11. Colour code: MP CP-1 CP-2 PSC L2SC TDSC LSC WSC FSC NMI-A Case ? - FFS • SCLs • PSC • MLSC • TDM • LSC • WSC • Goal: from an external point of view it should look like one NE • Unified CP • CN not physically unified with NEs NMI-A, Case F Location(With intra-office link) WP4 IM TF

  12. Colour code: MP CP-1 CP-2 PSC L2SC TDSC LSC WSC FSC Case ??PCE – Path computation Element The following alternatives applies • Example 1a: • CN not unified with NE is a PCE (Path Computation Element) which also supports routing protocols • CN unified with NE only take care of the signalling protocols • Example 1b: • CN not unified with NE is a PCE which take care of inter-AS/domain routing • CN unified with NE take care of signalling and intra-AS routing • Both CNs need a NMI-A interface NMI-A, Case _ NMI-A, Case _ PCE GMPLS/ASON? GMPLS/ASON WP4 IM TF

  13. LION Information modelling • See slide set sent out before • Out-of-band not modelled by LION • According to M.3100 philosophy • IM is single switching layer – e.g. VC4 • Discussed issues • (Georg will provide a list of issues that came up during the presentation) • St. Anne will provide an update of their IM proposals along with comments regarding the LION model WP4 IM TF

  14. Approach/Method for further work • Methodology • See IM TF Review document • Tentative decision: Build further on the Alcatel Italy / TMF MTNM contribution on definitions • Change proposals are still possible • Open Action points • See IM TF conf.call minutes 2004-08-26 • See next foil WP4 IM TF

  15. Action points • Alcatel CIT – Collect GMPLS definitions/concepts • Alcatel CIT – A note on Modelling of CP components – next week • St.Anna – Revised IM – with comments on the LION model • Georg – Issues raised during the LION presentation • All – Read & comment NOC’04 IM paper. Available on the NOBEL server • Abdel - Will provide a note on issues and management needs in the case CP and TP are separated and interfaces by an NE-external CCI – Consider also PCE • Abdel – Based on TMF MTNM – comments/and ideas on layering – for IM – first version in 2 weeks • Use Cases – To be appointed !!! • Could Abdel and Georg provide some use case examples to explain the use case template? WP4 IM TF

  16. Open issues • Policy-based mgmt – wrt. Services and CAC/CallAC • Other … WP4 IM TF

More Related