The service profile is created from the request that comes from CSMF. Below screen shows the fields that are fed as an input to CSMF.
The input entered in CSMF is passed to NSMF. NSMF does the below mapping to create the service profile.
Service Profile | Source /SO Calculation Rules |
sNSSAI | CS User Input |
pLMNIdList | Hasn’t given values in current implementation in service profile, but NST/NSST has values in templates. |
maxNumberofUEs | CS User Input |
coverageAreaTAList | CS User Input |
latency | CS User Input |
uEMobilityLevel | CS User Input |
resourceSharingLevel | CS User Input |
sST | CST gives fixed value (eg. embb) in the template, service profile will read from it. |
availability | Optional, can leave empty |
dLThptPerSlice | dLThptPerUE* maxNumberofUEs* activityFactor* any number between 2-6 |
dLThptPerUE | Same value with CS User Input expDataRateDL |
uLThptPerSlice | uLThptPerUE* maxNumberofUEs* activityFactor*any number between 2-6 |
uLThptPerUE | Same value with CS User Input expDataRateUL |
maxPktSize | Optional, can leave empty |
maxNumberofConns | maxNumberofUE*activityFactor*3 |
termDensity | Optional, can leave empty |
activityFactor | If CS has a value, then copy, if not, any value beyond 60 |
jitter | 10 |
survivalTime | Optional, can leave empty |
reliability | Optional, can leave empty |