You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

This page captures the details of the Modeling enhancements (IM, DM of NSST, NSSI, service and slice profiles, etc.) and the associated component impacts (e.g., SDC, AAI), as a part of E2E Network Slicing.

Main Contact(s): Chuyi GuoBorislav Glozman

Participants: LIN MENGSwaminathan SeetharamanSeshu Kumar MudigantiChuanyu ChenShankaranarayanan Puzhavakath Narayanan,Fei Zhang Alessandro Gerardo D'Alessandro

Enhancement Aspects

  • E2E Model structure optimization
  • 3 domain combination solution -Endpoint 
  • Add RAN Model
  • Add TN model

E2E Model structure optimization

  1. New/Enhanced features

    • Introduce Slice Profile Templates to carry user slicing subnet requirements, in ONAP we have 3 kinds of Slice Profile Templates, for RAN, Core and CN separately.
    • Add RAN NSST and TN NSST to support RAN and TN NSSI deployment, in TN side, also add TN Network Requirement Template to support TN connection links creation.
    • Has allotted resource relationship between slice subnet requirements and subnet slice resource, see 1, 2, 3. Allotted resource 4 is inner TN, between subnet resource and logical network resource.
    • Update relationship between NST and NSST using allotted resource, instead of nested, see 5. 
  2. Supprting for both option 1 and option 2
    ONAP option 1 and 2 differs on the RAN and FH/BH relationship, in option 1, RAN NSSMF will decide FH/MH requirements and send to TN side, so RAN NSST will nest FH/MH NSST, and slice profile requirements will contain not only RAN side requirements but also FH/MH. In option 2, FH and MH are independent requirments when doing E2E requirements decomposition. Detailed background of option 1 and 2, please see  E2E Network Slicing Use Case in R7 Guilin.


Supporting Files

Model Design Files

Description

File

Changes
WIP model of RAN part
Design Time model-Update Core model-(This sildes include latest RAN part)Fixed a typo
WIP Modeling files (Aug 6)
WIP Modeling files (Aug 14)
  1. Change EP design: NSST will have EP information while slice profile not.
  2. Change attribute(serviceRole and etc.) values.
  3. Add all RAN side templates(4 in total). 
WIP Modeling files (Aug 20)

1.DLThptPerSlice, uLThptPerSlice, maxNumberofConns and maxNumberofPDUSession

2.EP for supporting FH and MH

WIP RAN Option 1 (Oct 4)

AAI Instance Model

Description

File

Changes

AAI model proposal.

Including a E2E design and 3 domain subnets instance model.


AAI model proposal update
  1. Update different domain view(also separate option 1 and 2)
  2.  Update the attributes mapping for idenifying option1/option2, external/internal.

Final attributes mapping for service instance

update the latest changes of AAI, reusing Network-route to carry EP information, adding modeling overview picture 

Design Time Template

R7 Option 2 Templates-v1.0.zip

Service Profile and Slice Profile Attributes Mapping in R7

Slice Profile

Attribute Name Derived

From Service Profile

DomainValueSupport

sNSSAI

sNSSAI

All

Copy

M

pLMNIdList

pLMNIdList

All

Copy

M

maxNumberofUEs

maxNumberofUEs

CN AN

Copy

M

coverageAreaTAList

coverageArea

AN

Transfers into TA ids

O

latency

latency

All

Derived from

M

uEMobilityLevel

uEMobilityLevel

CN AN

Copy

O

resourceSharingLevel

resourceSharingLevel

CN AN

Copy

M

sST

sST

All

Copy

M

maxBandwidth

dLThptPerSlice,

uLThptPerSlice

TN

Derived from

O

expDataRateDL

(eMBB)

dLThptPerSlice

CN AN

Copy

O

expDataRateUL

(eMBB)

uLThptPerSlic

CN AN

Copy

O

areaTrafficCapDL

(eMBB)


CN AN

Calculate internally

O

areaTrafficCapUL

(eMBB)


CN AN

Calculate internally

O

maxNumberofPDUSession

maxNumberofConns

CN AN

Copy

O

overallUserDensity

(eMBB)

termDensity

AN

Copy

O

activityFactor

(eMBB)

activityFactor

CN AN

Copy

O

jitter

jitter

TN

Derived from

O

survivalTime

(uRLLC)

survivalTime

CN AN

Copy

O

transferIntervalTarget

(uRLLC)

No mapping in R7


CN AN


O

cSAvailabilityTarget

(uRLLC)

availability

CN AN

Copy

O

cSReliabilityMeanTime

(uRLLC)

Reliability

CN AN

Copy

O

expDataRate

(uRLLC)

dLThptPerSlice,

uLThptPerSlice

CN AN

Derived from

O

msgSizeByte

(uRLLC)

maxPktSize

CN

Copy

O

Note: Support "M" means this attribute must have a value in the slice profile when doing decomposition, "O" means may have a value or not depending on customer requirements.

  • No labels