World Class Standards Co-op on Information Models- NRM TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia...

World Class Standards

Co-op on Information Models- NRM

TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15th 2007.

Source: Geoff CaryerBT

2


Table of Contents

Overview of NGN

Reuse of the 3GPP NRM (IMS) by TISPAN

Other Possible Reuse

Integration with other SDOs (TMF)

Summary

3


The Next Generation Network O

ther n

etworks

Other subsystems

Core IMS

PSTN/ISDN Emulationsubsystem

User Equ

ipmen

t

Service Layer

Transport Layer

Transfer Functions

Resource and Admission Control

Subsystem

Network Attachment Subsystem

Applications

Userprofiles

4


Key Aspects of the NGN NRM

The NGN comprises a Transport and Service layer The NGN Transport Layer, Control layer (including IMS) and

Applications could be in different administrative domains (i.e. operated by different organisations).

The NRM shall allow management of resources which are shared between administrative domains.

5


NGN Common Components (Service Layer)

IBCF

IWF

Transfer Functions

Transport control

To/Fromother IP networks

Service Control Subsystems

Transport Layer

Service Layer

ASF(type 2)

UPSFASF(type 1) Data Collection

Charging mediation

Mediationto other

management applications

…

SLF

6


Network Attachment Subsystem (Transport layer)

a4

Service control subsystems and

applications

TE CNG

a3 a1

a2

e1

e2 e4

e3

Resource and

Admission Control

Subsystem

CLF

NACF CPECF

AMF

PDBF UAAF

ARF e1

e2

e5

CNGCF

UE

7


Resource Allocation Subsystem (Transport layer)

Di

Transport Layer

Rq

Di

A-RACF

Ia

e4

Re

Gq’

Ra

NASS

AF

SPDF

CoreBorder Node

BGF

Ip Edge

RCEF

L2TPointAccess

Node

RACS

UEDs

Di

Transport Layer

Rq

Di

A-RACF

Ia

e4

Re

Gq’

Ra

NASS

AF

SPDF

CoreBorder Node

BGF

Ip Edge

RCEF

L2TPointAccess

Node

RACS

UEDs

8


TISPAN NRM IS

Reuses the IS template in 3GPP TS 32.152 Reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS

32.622 Reuses relevant parts of the IMS NRM IRP:IS in 3GPP TS 32.732

by importing IOCs

9


Imported IOCs (1)

32.622 [2], information object class, Link 32.622 [2], information object class, ManagedElement 32.732 [1], information object class, CscfFunction 32.732 [1], information object class, IcscfFunction 32.732 [1], information object class, PcscfFunction 32.732 [1], information object class, ScscfFunction 32.732 [1], information object class, BgcfFunction 32.732 [1], information object class, MgcfFunction 32.732 [1], information object class, MrfcFunction 32.732 [1], information object class MrfpFunction 32.732 [1], information object class ImsMGwFunction 32.732 [1], information object class, AsFunction 32.732 [1], information object class, SlfFunction

10


Imported IOCs (2) 32.732 [1], information object class, Link_As_Cscf 32.732 [1], information object class, Link_As_Scscf 32.732 [1], information object class, Link_As_Slf 32.732 [1], information object class, Link_Bgcf_Bgcf 32.732 [1], information object class, Link_Bgcf_Cscf 32.732 [1], information object class, Link_Bgcf_Mgcf 32.732 [1], information object class, Link_Bgcf_Scscf 32.732 [1], information object class, Link_Cscf_Cscf 32.732 [1], information object class, Link_Cscf_Icscf 32.732 [1], information object class, Link_Cscf_Mgcf 32.732 [1], information object class, Link_Cscf_Mrfc 32.732 [1], information object class, Link_Cscf_Pcscf 32.732 [1], information object class, Link_Cscf_Scscf 32.732 [1], information object class, Link_Cscf_Slf 32.732 [1], information object class, Link_Icscf_Slf 32.732 [1], information object class, Link_Mgcf_Scscf 32.732 [1], information object class, Link_Mrfc_Mrfp 32.732 [1], information object class, Link_Mrfc_Scscf 32.732 [1], information object class, Link_Scscf_Scscf 32.732 [1], information object class, Link_Scscf_Slf

11


TISPAN NRM Release 2 - Outstanding Issues with SA5

Do we model I-CSCF, P-CSCF and S-CSCF as 3 classes (I-CSCF, P-CSCF and S-CSCF) or CSCF?. TISPAN agree to keep table as is until we receive a contribution from FT, which will propose an additional CSCF for emergency calls

The addition of As1 and As2 is awaiting resolution of discussions between 3GPP and 3GPP

Section on “Information attribute definitions “ is section is under CR in 3GPP SA5, TISPAN are await clarification before completing

12


TISPAN NRM Release 2 - Outstanding Issues with TeleManagement Forum

Do we need to link the NRM to the TMF Shared Information Data Model (SID)?

If yes, how do we do this?

13


3GPP Inheritance

Top<<InformationObjectClass>>

ManagedElement

ManagedFunction

ManagementNode

MeContext

SubNetwork

14


SID resource Hierarchy

ResourceRoleResourceSpecification Resource 0..1 0..n0..1 0..n

ResourceTakesOnRoles

1 0..n1 0..n

SpecifiesResource

LogicalResourceRolePhysicalResourceLogicalResource

0..1 0..n0..1 0..n

RolesDescribeLogicalResource

0..n0..n 0..n0..n

PResourceSupportsLResource

PhysicalResourceRole

15


Candidate Requirements for TMF SID / 3GPP NRM integration

1. The main requirement that drives a Service Provider in the integration of the 3GPP NRM (Network Resource Model), TISPAN NRM and the TMF SID, is to ensure compatibility between these information models and underlying specification approaches.

2. TISPAN Service and Network Resource models shall be derived by extension from the 3GPP Generic NRM IRP (TS32.622) and the TeleManagement Forum Shared Information/Data Model (TMF GB922) using multiple inheritance.

3. TISPAN Service and Network Resource models shall make use of the URIs for naming; the path component of the URI shall comply with 3GPP specified naming conventions.

4. The TISPAN Service and Network Resource Model URIs shall be prefixed with “tispan-nosi”, e.g., “tispan-nosi://hostname.domain.com/<3GPP-compliant-name>”.

16


BT Assertions There is a high level requirement to harmonize the TISPAN/3GPP work

with the TMF SID. The requirement is high level - it has not been stated what the outcome

should look like nor what aspects of data should be shared nor what operations should be common to both. It is the BT view that this should be clarified since it may determine the outcome.

The SID is structured according to the eTOM layers model (CRM, Service, Resource) - The 3GPP model should also be aligned with the architectural principles of eTOM going forward. Currently the 3GPP SuM model definitely is not and it is possible to align it (although more investigation is needed to verify that the other aspects of the 3GPP model may not be. However the starting point will be the SuM model)

Multiple Inheritance is a possible means of achieving convergence but is not an end in itself. It is possible to achieve the same results as MI through other means.

Quote: UML User Guide pg 142 "Use MI carefully...in most cases MI can be replaced by delegation, in which a child inherits from only one parent and then uses aggregation to obtain the structure and behaviour of more subordinate parents...".

17


Possible Solutions Refactoring: Restructuring the model - eg Classes and Association structure

without changing the behaviour of the model as a whole. Multiple Inheritance. Since it has not been established what classes need to inherit

what from where this is slightly speculative, however this involves subclasses inheriting operations and attributes via UML generalization from multiple superclasses (presumably a SID class and a 3GPP class).

Interface; UML offers a classifier called interface, this is distinct in that it is technology neutral but similar in appearance and behaviour to Java interfaces. It is possible to define a technology neutral model in UML using classes and interfaces, by suitable configuration it is possible to automatically generate technology specific models. For example in a Java implementation the interface remains in situ, but in C++ the interface is automatically replaced by MI relationships between respective classes.

Mixins: Steve has not needed to use this before - numerous examples on Google e.g. http://www-128.ibm.com/developerworks/library/j-diag1203/

Polymorphism: Again, other point to investigate further. Essentially it means that an entity may have several types. numerous articles via Google, simple example at http://www.developer.com/design/article.php/10925_3507221_2

18


TISPAN NRM Future Releases

The ETSI and 3GPP have agreed to move all TISPAN standardisation work concerned with the "common IMS" to 3GPP.

The responsibility for reference points between the IMS and TISPAN entities will become the responsibility of 3GPP.

Will SA5 update the IMS NRM to include these reference points and in what timescale?

19


Summary

TISPAN NRM builds on: 3GPP methodology Generic NRM IMS NRM

Relationship with TMF SID is being considered.

How can 3GPP SA5 and TISPAN WG8 best progress NRM issues?

World Class Standards Co-op on Information Models- NRM TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia...

Documents

Transcript of World Class Standards Co-op on Information Models- NRM TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia...