8.2.1 Resource definitions
28.5313GPPManagement and orchestrationProvisioningRelease 16TS
8.2.1.1 Resource ObjectManagement/NS/ServiceProfiles
8.2.1.1.1 Description
This resource represents collects of network slice related requirement (i.e. ServiceProfiles).
8.2.1.1.2 URI
Resource URI: {URI authority}/ObjectManagement/NS/ServiceProfiles
The URI authority is defined by the service provider.
8.2.1.1.3 HTTP methods
8.2.1.1.3.1 POST
The POST method create a serviceProfile, the provider may create a NSI or using existing NSI to satisfy the serviceProfile.
This method shall support the request data structures, and the response data structures and response codes specified in the following tables.
Table 8.2.1.1.3.1-1: Data structures supported by the POST Request Body on this resource
|
Name |
DATA TYPE |
P |
Cardinality |
Description |
|
attributeListIn |
LIST OF SEQUENCE< attribute name, attribute value> |
M |
1 |
This parameter specifies the network slice related requirements or network related requirements defined in ServiceProfile in Clause 6.3.3 in TS 28.541 [6]. |
Table Y.2.1.1.3.1-2: Data structures supported by the POST Request Body on this resource
|
Name |
DATA TYPE |
P |
Cardinality |
Description |
|
Href |
URI |
M |
1 |
HTTP reference to an NSI or Network resource. |
|
attributeListOut |
LIST OF SEQUENCE< attribute name, attribute value> |
M |
1 |
For each returned NSI: A list of name/value pairs for NSI defined in Network Slice IOC. |
|
status |
HTTP response code |
M |
1 |
HTTP response code 200 indicates “OperationSucceeded”. All other HTTP response codes indicate “OperationFailed”. |
8.2.1.2 Resource ObjectManagement/NSS/SliceProfiles
8.2.1.2.1 Description
This resource represents collects of network slice subnet related requirements (i.e. SliceeProfiles).
8.2.1.2.2 URI
Resource URI: {URI authority}/ObjectManagement/NSS/SliceProfiles
The URI authority is defined by the service provider.
8.2.1.2.3 HTTP methods
8.2.1.2.3.1 POST
The POST method create a SliceProfile, the provider may create a new NSSI or using existing NSSI to support the SliceProfile.
This method shall support the request data structures, and the response data structures and response codes specified in the following tables.
Table 8.2.1.2.3.1-1: Data structures supported by the POST Request Body on this resource
|
Name |
DATA TYPE |
P |
Cardinality |
Description |
|
attributeListIn |
LIST OF SEQUENCE< attribute name, attribute value> |
M |
1 |
This parameter specifies the network slice subnet related requirements defined in SliceeProfile in Clause 6.3.4 in TS 28.541 [6]. |
Table 8.2.1.2.3.1-2: Data structures supported by the POST Request Body on this resource
|
Name |
DATA TYPE |
P |
Cardinality |
Description |
|
Href |
URI |
M |
1 |
HTTP reference to an NSSI resource. |
|
attributeListOut |
LIST OF SEQUENCE< attribute name, attribute value> |
M |
1 |
For each returned NSSI: A list of name/value pairs for NSSI defined in Network Slice Subnet IOC. |
|
status |
HTTP response code |
M |
1 |
HTTP response code 200 indicates “OperationSucceeded”. All other HTTP response codes indicate “OperationFailed”. |
8.2.1.3 Resource ObjectManagement/ServiceProfiles
8.2.1.3.1 Description
This resource represents collects of network related requirements (i.e. ServiceProfiles).
8.2.1.3.2 URI
Resource URI: {URI authority}/ObjectManagement/ServiceProfiles
The URI authority is defined by the service provider.
8.2.1.3.3 HTTP methods
8.2.1.3.3.1 POST
The POST method create a serviceProfile.
This method shall support the request data structures, and the response data structures and response codes specified in the following tables.
Table 8.2.1.3.3.1-1: Data structures supported by the POST Request Body on this resource
|
Name |
DATA TYPE |
P |
Cardinality |
Description |
|
attributeListIn |
LIST OF SEQUENCE< attribute name, attribute value> |
M |
1 |
This parameter specifies the network related requirements defined in ServiceProfile in Clause 6.3.3 in TS 28.541 [6]. |
Table 8.2.1.3.3.1-2: Data structures supported by the POST Request Body on this resource
|
Name |
DATA TYPE |
P |
Cardinality |
Description |
|
status |
HTTP response code |
M |
1 |
HTTP response code 200 indicates “OperationSucceeded”. All other HTTP response codes indicate “OperationFailed”. |
Annex A (informative):
A network slice journey example
The Generic Slice Template (GST) ([9]) provides a standardized list of attributes that can be used to characterise different types of network slice. GST is generic and is not tied to any:
– Type of network slice
– Agreement between a Network Slice Customer (NSC) and a Network Slice Provider (NSP).
A Network Slice Type (NEST) is a GST filled with (ranges of) values. There may be two kinds of NESTs:
– Standardized NESTs (S-NEST), i.e. NESTs which character attributes are assigned (ranges of) values by SDOs, working groups, foras, etc. such as e.g. 3GPP, GSMA, 5GAA, 5G-ACIA, etc.;
– Private NESTs (P-NEST), i.e. NESTs which character attributes are assigned (ranges of) values by the Network Slice Providers, which are different from those assigned in S-NESTs.
Network Slice Providers can build their network slice product offering based on S-NESTs and/or their P-NESTs. For example, a Standardized Network Slice Type (S-NEST) NST-A, for which the attribute ‘Packet delay budget’ (see [x] – clause 3.4.26) value range is between 1 ms and 100 ms, is specified by 3GPP. Netwok Slice Provider Y may offer e.g. 3 products based on NST-A:
– Platinum NST-A based network slice product, where the attribute ‘Packet delay budget’ (see [x] – clause 3.4.26) value range is between 1 ms and 10 ms;
– Gold NST-A based network slice product, where the attribute ‘Packet delay budget’ (see [x] – clause 3.4.26) value range is between 11 ms and 50 ms;
– Silver NST-A based network slice product, where the attribute ‘Packet delay budget’ (see [x] – clause 3.4.26) value range is between 51 ms and 100 ms.
NSP Y’s customers can then order network slice instances from Y’s product catalog, as depicted by Figure A.1.
Figure A.1: From GST to S-(/P-)NEST based product ordering
1) A Network Slice Customer orders network slice instance to a Network Slice Provider, based on NSP’s product offering, by sending a request to NSP’ BSS
2) NSP’s BSS receives the request from NSC and translates NSC requirements into NSP technical parameter values
3) NSP’s BSS sends a request to NSP’s OSS to provide a network slice instance which fits NSC’s requirements (see Table 6.1-1)
4) NSP’s Network Slice Provisioning MnS either creates a new network slice instance or assigns an already existing network slice instance to NSC’s request
5) NSP’s Network Slice Provisioning MnS may have to request the Network Slice Subnet Provisioning MnS to provide a network slice subnet instance corresponding to the network slice instance (see Table 6.2-1)
6) NSP’s Network Slice Subnet Provisioning MnS may have to create one or more inner network slice subnet instances
7) NSP’s Network Function Provisioning MnS configures VNFs and/or PNFs (see Table 6.3-1).
Figure A.2: Network Slice journey (NSaaS model) – high-level call flow
Depending on NSP’s product offering, NSC can order network slice instances spanning one or more network domains, e.g.:
– network slice instances composed of a RAN-only network slice subnet instance
Figure A.3: RAN-only network slice subnet exposed as network slice
– network slice instances composed of a CN-only network slice subnet instance
– network slice instances composed of a RAN network slice subnet instance + Transport network slice subnet + CN network slice subnet instance
Figure A.4: RAN+TN+CN network slice subnets exposed as network slice
– network slice instances composed of a RAN network slice subnet instance + CN network slice subnet instance + IMS network slice subnet instance
– or more, as shown below..
Figure A.5: RAN+TN+CN+TN+IMS+TN+AS network slice subnets exposed as network slice
Annex B (informative):
General information for network slice related identifiers
The following network slice related identifiers serve different purposes:
|
Identifier |
Description |
|
Identifiers for network slice management purpose |
|
|
NetworkSlice identifier |
To identify a NetworkSlice instance defined in TS 28.530 (see [4]), it is DN of a managed object instance of NetworkSlice IOC, see TS 28.541 [6] |
|
NetworkSliceSubnet identifier |
To identify a NetworkSliceSubnet instance defined in TS 28.530 (see [4]), it is DN of a managed object instance of NetworkSliceSubnet IOC, see TS 28.541 [6] |
|
Identifiers for network slice signaling purpose |
|
|
NSI ID |
NSI ID is only for 5GC signaling use, i.e. to identify Core Network part of a Network Slice instance when multiple Network Slice instances of the same Network Slice are deployed, and there is a need to differentiate between them in the 5GC, see clause 3.1 of TS 23.501 [10]. The NRM attribute cNSIIdList of NRFFunction and NSSFFunction, see TS 28.541 [6], is a list for NSI ID(s). |
|
S-NSSAI |
To identify Network Slice defined in TS 23.501. Referred to TS 23.501 [10] and TS 38.300 [11]. NRM attribute sNSSAIList defines the S-NSSAI(s) supported by the corresponding managed object, see TS 28.541 [6]. |
|
PLMN ID |
Represent PLMN identifier. |
The NSI ID and S-NSSAI are configuration parameters of the management system.
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-09 |
SA#81 |
Upgrade to change control version |
15.0.0 |
||||
|
2018-12 |
SA#82 |
SP-181043 |
0001 |
1 |
F |
Complete the reference information and reword the note |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181043 |
0002 |
– |
F |
Update operation names in the procedures of NSI provisioning |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181043 |
0003 |
– |
F |
Update operation names in the procedures of NSSI provisioning |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181043 |
0004 |
1 |
F |
Update operation names in the procedures of NF provisioning |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181043 |
0005 |
1 |
F |
Remove release specific information from clause 7.9.1 |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181043 |
0006 |
1 |
F |
Correct procedures with reference to TS 28.541 |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181043 |
0009 |
1 |
B |
Add Network slice subnet management use case with assigned priority |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181043 |
0010 |
2 |
B |
Add network slice management interactions with NFV MANO for network service priority |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181044 |
0011 |
2 |
D |
Implement minor corrections |
16.0.0 |
|
2019-03 |
SA#83 |
SP-190123 |
0013 |
– |
A |
Update management services tables |
16.1.0 |
|
2019-03 |
SA#83 |
SP-190123 |
0015 |
– |
A |
Correction on procedure of Network Slice Subnet Instance Deallocation |
16.1.0 |
|
2019-03 |
SA#83 |
SP-190123 |
0017 |
1 |
A |
Correct management service term |
16.1.0 |
|
2019-05 |
SA#84 |
SP-190370 |
0019 |
1 |
A |
Editor’s change for configuration management service |
16.2.0 |
|
2019-09 |
SA#85 |
SP-190754 |
0022 |
– |
A |
Update the incorrect reference |
16.3.0 |
|
2019-09 |
SA#85 |
SP-190750 |
0024 |
1 |
B |
Add informative annex to describe a network slice journey |
16.3.0 |
|
2019-09 |
SA#85 |
SP-190754 |
0026 |
1 |
A |
Add the identifier description |
16.3.0 |
|
2019-09 |
SA#85 |
SP-190742 |
0028 |
1 |
A |
Fix inconsistencies related to service requirements |
16.3.0 |
|
2019-12 |
SA#86 |
SP-191175 |
0032 |
1 |
A |
Fix inconsistencies in feasibility check use cases and requirements |
16.4.0 |
|
2019-12 |
SA#86 |
SP-191159 |
0033 |
1 |
F |
Clean up for incosistence |
16.4.0 |
|
2020-03 |
SA#87E |
SP-200166 |
0039 |
– |
F |
Replace occurences of Management Function by Management Service |
16.5.0 |
|
2020-07 |
SA#88-e |
SP-200498 |
0044 |
1 |
A |
Fix Network Slice subnet termination use case |
16.6.0 |
|
2020-07 |
SA#88-e |
SP-200484 |
0045 |
1 |
F |
Fix NSI activation and deactivation use cases |
16.6.0 |
|
2020-07 |
SA#88-e |
SP-200484 |
0047 |
1 |
F |
Clarification on network slice related identifiers |
16.6.0 |
|
2020-09 |
SA#89-e |
SP-200724 |
0053 |
1 |
F |
Editorial corrections to remove redundant text from use cases |
16.7.0 |
|
2020-09 |
SA#89-e |
SP-200735 |
0056 |
– |
A |
Add clarifying note to ServiceProfile |
16.7.0 |
|
2020-09 |
SA#89-e |
SP-200724 |
0057 |
– |
F |
Fix general information of network slice related identifiers |
16.7.0 |
|
2020-12 |
SA#90e |
SP-201053 |
0058 |
1 |
F |
Move service profile definition to 28530 |
16.8.0 |
|
2020-12 |
SA#90e |
SP-201050 |
0059 |
1 |
F |
Correction of allocateNsi operations and procedures |
16.8.0 |
|
2021-03 |
SA#91e |
SP-210146 |
0060 |
– |
F |
Correction of URI of Resource |
16.9.0 |
|
2021-03 |
SA#91e |
SP-210146 |
0061 |
1 |
F |
Correction of NSI and NSSI Operations |
16.9.0 |
|
2021-06 |
SA#92e |
SP-210417 |
0064 |
1 |
A |
Clarify misleading information in network slicing use cases |
16.10.0 |
|
2021-09 |
SA#93e |
SP-210881 |
0068 |
1 |
A |
Correction of network slice subnet configuration |
16.11.0 |
|
2021-09 |
SA#93e |
SP-210881 |
0075 |
– |
A |
Removing network slice capacity planning |
16.11.0 |
|
2021-09 |
SA#93e |
SP-210881 |
0078 |
– |
A |
Removing Notify Network Slice Subnet Capability Information |
16.11.0 |
|
2021-09 |
SA#93e |
SP-210885 |
0081 |
1 |
F |
Updating NSSI deallocation |
16.11.0 |
|
2021-09 |
SA#93e |
SP-210885 |
0082 |
1 |
F |
Updating NSSI deactivation |
16.11.0 |
|
2021-09 |
SA#93e |
SP-210885 |
0083 |
1 |
F |
Updating NSSI allocation |
16.11.0 |
|
2021-12 |
SA#94e |
SP-211454 |
0086 |
1 |
F |
Technical errors in use case descriptions |
16.12.0 |
|
2022-09 |
SA#97e |
SP-220857 |
0132 |
1 |
A |
Remove example from network slice subnet instance modification –> nothing to implement (MCC) |
16.13.0 |
|
2022-09 |
SA#97e |
SP-220857 |
0134 |
1 |
A |
Remove example from network slice instance modification |
16.13.0 |
|
2022-09 |
SA#97e |
SP-220853 |
0136 |
1 |
F |
Correct roles in network slice subnet allocation use case |
16.13.0 |
|
2022-12 |
SA#98e |
SP-221173 |
0147 |
1 |
A |
Correct vocabulary |
16.14.0 |
|
2022-12 |
SA#98e |
SP-221178 |
0161 |
1 |
A |
Clarification and update of deallocation use case |
16.14.0 |
|
2023-01 |
SA#98e |
Previous version contained a corrupted file (MCC) |
16.14.1 |
||||