Network Resource Information Model and Connectivity Management Architecture

Network Resource Information Model and Connectivity Management Architecture, A Hands On Experience Report Tina 2000 Lyle Bertz Sprint PCS 1/2/2022 1

NRIM v 3. 0 & Sprint Although Sprint uses the NRIM actively in various implementations and has for a few years, it has not been without problems: – Hard to implement – Training time is difficult – Extremely difficult to implement a CMA (idl creep) – Missing fundamental relationships. . . 1/2/2022 2

Some of the Missing Pieces • Lack relationships between – Hardware and logical (NRIM) – Software and hardware • Terminology like “edges” • Lack of alignment between G. 803 and NRIM; if one builds a standards compliant one, do they just dump the NRIM? 1/2/2022 3

Resource Information Model 4. 0 • New version of NRIM • Addresses some connectionless technology • Provides a strong meta-model for Layered Network inter-relationships • Ties hardware, software and logical representation together • Some realignment done with the ITU-T recommendations 1/2/2022 4

Protocol Meta-model • Models Encapsulation, Transport and Signaling • Provides a tracking for the protocols • Drives relationships between layered networks 1/2/2022 5

Protocol Meta-Model 1/2/2022 6

Meta-Model Example IP: Stream. Protocol IP: LNW AAL 5: Internetworking Function ATM: Stream. Protocol 1/2/2022 ATM: LNW 7

Realignment with some ITU-T concepts • All connections in RIM inherit from Transport Entity (but it may be bidirectional; a departure from the ITU models) • Reference Points (Points of Reference in the network; not TINA RPs) all also used • Edge renamed to Subnetwork Termination Point (SNTP) 1/2/2022 8

The TINANetwork. Element (TNE) • Integrates hardware, software and logical (NRIM) viewpoints • Allows for modeling of various levels of knowledge of an element – Unmanaged Network Element (like the NRIM CPE) Hardware/software knowledge only & unmanaged – Managed Network Element hardware/software knowledge & management control 1/2/2022 9

Impacts on the CMA • Requires Binding Managers to be formalized. Binding Managers perform the following: – control & management of reference points – manage inter-layered network relationships (e. g. Interwork/Internetwork functions) • Object Locators are also needed – transform URIs to URLs – resolve URLs to “routable” addresses 1/2/2022 10

Issues • Lack of clear definition on how to define instances of the protocol meta-model when instantiating an interface. – Example, if I start an IP Layered Network Coordinator, how to I specify the “standard” IP Stream Protocol instance • ODL does not cover this; OIF & OQL do, but – OIF is for database loading – OQL is for queries 1/2/2022 11

Issues (cont. ) • RIM uses CIM 2. 0 for the hardware and root model but the current spec is at 2. 2 • No CMA fully defined yet. An implementation does exist from Sprint and is going into production, but this is not an officially endorsed TINA effort nor specification. 1/2/2022 12

Next Steps • Upgrade RIM to include CIM 2. 2 physical model • Resolve how to couple meta-model instances with interfaces/objects (maybe enhancements to TINA ODL? ) • Provide a standardized CMA 1/2/2022 13

The End 1/2/2022 14