Oracle® Communications Network Slice Selection Function (NSSF) Cloud Native User's Guide Release 1.0 F16990-01 |
|
![]() Previous |
![]() Next |
The following NSSF managed objects can be configured using REST APIs :
Table 3-1 NSI Profile - Parameters
S.No | Field Name | Type | Description (With Default Values) |
1 | name | String | Network Slice Instance Profile Name. |
2 | nrfUri | String | URI of the Network Resource Function |
3 | nsiId | String | Network Slice Intance Identifier |
5 | regionId | String | Target AMF Region Id |
6 | setId | String | Target AMF Set Id |
7 | setFqdn | String | Target AMF Set Fqdn |
Customer can configure NSI Profiles by following the information provided in the table below. The supported operations are POST, GET, DELETE, and PUT. The following table provides information about the REST APIs supported by the NSI Profile managed object.
Table 3-2 Supported REST APIs - NSI Profile
Resource Name | URI | Data Type | HTTP Method | Description |
NSI Profiles | /nssf-configuration/v1/nsiprofiles | array(NssfNsiProfile) | POST | Create a network slice instance profile |
GET | Read all network slice instance profiles | |||
NSI Profile | /nssf-configuration/v1/nsiprofiles/{name} | NsiProfile | GET | Read a network slice instance profile |
DELETE | Delete a network slice instance profile | |||
PUT | Update a network slice instance profile |
NSS Rule: The NSS Rule managed object enables customer to configure policy rules, NSS Rule allows customer to allow/reject/associate a Network slice based on NSSAI(SST and SD) , PLMN(MCC and MNC) ,TAC , AMF_ID. Operator can configure salience value to prioritize one rule over other.
Table 3-3 NSS Rule Parameters
S.No | Field Name | Type | Description (With Default Values) |
1 | name | String | Network Slice Selection Rule Name |
2 | amfId | String | AMF Identifier |
3 | plmnId | String | AMF Identifier |
4 | mcc | String | Mobile Country Code |
5 | mnc | String | Mobile Network Code |
6 | tac | String | AMF Identifier |
8 | sst | Integer | Slice/Service type |
9 | sd | String | Slice Differentiator |
10 | salience | Integer | Order of importance, higher salience, more important |
12 | grant | String | Whether the requested s-NSSAI is allowed or restricted |
13 | accesstype | String | Access Type in which the grant applies |
Customer can configure NSS Rules by following the information provided in the table below. The supported operations are POST, GET, DELETE, and PUT. The following table provides information about the REST APIs supported by the NSS Rule managed object.
Table 3-4 Supported REST APIs - NSS Rule
Resource Name | URI | Data Type | HTTP Method | Description |
NSS Rules | /nssf-configuration/v1/nssrules | array(NssfNssRule) | POST | Create a network slice selection rule |
GET | Read all network slice selection rules | |||
NSS Rule | /nssf-configuration/v1/nssrules/{name} | NssRule | GET | Read a network slice selection rule |
DELETE | Delete a network slice selection rule | |||
PUT | Update a network slice selection rule |
Table 3-5 AMF Resolution - Parameters
S.No | Field Name | Type | Description (With Default Values) |
1 | regionId | Integer | Region ID of the target AMF list |
2 | setId | Integer | Set ID of the target AMF list |
3 | fqdn | String | Fqdn of the target AMF list |
4 | instanceId | String | Instance ID of the target AMF list |
Customer can configure AMF Resolution by following the information provided in the table below. The supported operations are POST, GET, DELETE, and PUT. The following table provides information about the REST APIs supported by the AMF Resolution managed object.
Table 3-6 Supported REST APIS - AMF Resolution
Resource Name | URI | Data Type | HTTP Method | Description |
AMF Resolutions | /nssf-configuration/v1/amfresolutions | array(NssfAmfResolution) | POST | Create a AMF resolution |
GET | Read all AMF resolutions | |||
AMF Resolution | /nssf-configuration/v1/amfresoltuions/{region_id}[:{set_id}[:{instance_id}]] | NssfAmfResolution | GET | Read a AMF resolution |
DELETE | Delete a AMF resolution | |||
PUT | Update a AMF resolution |
Table 3-7 Configured NSSAI - Parameters
S.No | Field Name | Type | Description (With Default Values) |
1 | amfId | Integer | AMF Identifier |
2 | mcc | Integer | Mobile Country Code |
3 | mnc | Integer | Mobile Network Code |
4 | tac | Integer | AMF Identifier |
5 | salience | Integer | Order of importance, higher salience, more important |
6 | sst | Integer | Slice/Service type |
sd | String | Slice Differentiator |
Customer can configure Configured NSSAI by following the information provided in the table below. The supported operations are POST, GET, DELETE, and PUT. The following table provides information about the REST APIs supported by the Configured NSSAI managed object.
Table 3-8 Supported REST APIs - Configured NSSAI
Resource Name | URI | Data Type | HTTP Method | Description |
Configured NSSAIs | /nssf-configuration/v1/configurednssais | array(NssfConfiguredNssai) | POST | Create a configured NSSAI |
GET | Read all configured NSSAIs | |||
Configured NSSAI | /nssf-configuration/v1/configurednssais/{amf_id}:{mcc}:{mnc}[:{tac}[:{sst}:{sd}]]] | NssfConfiguredNssai | GET | Read a configured NSSAI |
DELETE | Delete a configured NSSAI |
For a sample Open API Specification, see Open API Specification.