A&AI Instance Modeling in Guilin

A&AI Instance Model Structure for E2E Network Slicing Case

Overview

E2E Network Slicing implements CSMF, NSMF and NSSMF in ONAP, in A&AI there has entities respectively corresponding to different instance management function.

For the whole network slicing management lifecycle. there has 2 parallel lines, one is for single s-NSSAI requirements which is dynamic and comes from slicing user requests, there are CSIs, sevice profile instances and slice profile instances for different user requirements. In design time, you can find CST, Service profile T and Slice Profile T for them(Templates details can be found at Template Design for Option2). 

Another line is for network slicing requirements which can carry multiple s-NSSAI(user) requirements, there are NSIs and NSSIs. In design time, you can find NST and NSST for them. User requirements will be translated and mapped to network slicing requirements.

The overall E2E Network Slicing A&AI instance model photo is:



Papyrus Diagram and ONAP AAI object mapping is:

Note: only when option 1, there will have self-nested cycles for RAN slice profile instance and RAN NSSI.

The whole design time Modeling framework can be found at Modeling enhancements.

New feature in R7

In Guilin release, there has 3 new features:

  • Transport Slicing models, and 3 subnet connection endpoint

  • Add completed Slice profile service instance(changing node SliceProfile relationship from NSSI to sevice instance object) 

  • Add underlay resources associations with NSSI

Transport Network Slicing Model

Overview

Transport Slicing model is part of the E2E Nerwork Slicing Modeling Structure, which will be used and maintained by TN NSSMF at Management and Control Plane level. Transport Slicing model will be mapped to TN Network reosurce model- CCVPN Model.  Transport Slicing model refers IETF specification draft-rokui-5g-transport-slice-00.pdf.

Details of how to map to CCVPN Network model can be found at: 

IETF Model Reference

IETF original model expression:

Transport model mapping:

Transport 3 Level Plane Models Relationship and Mapping

Network Slicing and ONAP A&AI Schema Attributes Mapping

ONAP Service Instance

Communication Service Instance

Data Type

Remarks

ONAP Service Instance

Communication Service Instance

Data Type

Remarks

service-instance-id

id

String



service-instance-name

name

String



service-role



String

Communication Service Instance

orchestration-status

status

String



service-type

sST

String

eMBB/mMTC/uRLLC

created-at

createTime

String

2019-12-19 11:30:45

workload-context

useInterval

String



environment-context

s-NSSAI

String





ONAP Service Instance

Service/Slice Profile Instance

Data Type

Remarks

ONAP Service Instance

Service/Slice Profile Instance

Data Type

Remarks

service-instance-id

id

String



service-instance-name

name

String



service-role



String

Service/Slice Profile Instance

orchestration-status

status

String



service-type

sST

String

eMBB/mMTC/uRLLC

service-instance-location-id

PLMNIdList

String



environment-context

s-NSSAI

String



workload-context

domainType

String

 AN, CN, etc., only used in Slice Profile Instance



ONAP Service Instance

NSI/NSSI

Data Type

Remarks

ONAP Service Instance

NSI/NSSI

Data Type

Remarks

service-instance-id

id

String



service-instance-name

name

String



service-role



String

nsi/nssi

orchestration-status

status

String



service-type

sST

String

eMBB/mMTC/uRLLC

service-instance-location-id

PLMNIdList

String



service-function



String

Shared/Non-Shared

workload-context

domainType

String

AN, CN, etc., only used in NSSI 



ONAP Network Route

Endpoint

Data Type

Remarks

ONAP Network Route

Endpoint

Data Type

Remarks

route-id

id

String



role



String

cn/an

ip-address

ipAddress

String



logical-interface-id

logicInterfaceId

String



next-hop

nextHopInfo

String





ONAP Logical Link

ConnectionLink

Data Type

Remarks

ONAP Logical Link

ConnectionLink

Data Type

Remarks

link-id

id

String



link-name



String

RAN and Core Endpoint Ids

in-maint



Boolean

false

link-type



String

ConnectionLink

relationship-list





Guilin didn't use relationship-list to associate with Network Routes, consider to use in the future releases.



ONAP Network Policy

TransportSlicePolicy

Data Type

Remarks

ONAP Network Policy

TransportSlicePolicy

Data Type

Remarks

network-policy-id

id

String



latency

latency

Integer



jitter

jitter

Integer



max-bandwidth

maxBandwidth

Integer