Configure NSSF using REST APIs
Before configuring NSSF using REST APIs, ensure that the NSSF is installed. For information on how to install NSSF, refer Network Selection Slice Function Installation Guide.
To Configure NSSF using REST APIs:
- Configure the NSI-Profile managed
object:
NSI-Profile consists of network slice name and ID and NRF-ID ,Target AMF lists which are associated to the slice.
- Request_Type: POST
- URL: http://{apiRoot}/nnssf-configuration/v1/nsiprofiles
- Body: Refer to Sample NSI-Profile-Body section for sample message/s and OpenAPI for schema.
REST message sample - NSI Profiles
http://host:port/nnssf-configuration/v1/nsiprofiles POST Content-Type: application/json BODY { "name": "NSI001", "nrfUri": "https://nrf.slice11.oracle.com/nnrf-disc/v1", "nsiId": "SLICE1", "nrfNfMgtUri":"https://nrf.slice11.oracle.com/nnrf-nfm/v1", "nrfAccessTokenUri":"https://nrf.slice11.oracle.com/oauth2/token", "targetAmfSets": [ { "regionId": "01", "setId": "001", "setFqdn": "set001.region01.amfset.5gc.mnc311.mcc282.3gppnetwork.org" }, { "regionId": "01", "setId": "002", "setFqdn": "set002.region01.amfset.5gc.mnc311.mcc282.3gppnetwork.org" } ] } POST Content-Type: application/json BODY { "name": "NSI002", "nrfUri": "https://nrf.slice2.oracle.com/nnrf-disc/v1", "nsiId": "SLICE2", "nrfNfMgtUri":"https://nrf.slice2.oracle.com/nnrf-nfm/v1", "nrfAccessTokenUri":"https://nrf.slice2.oracle.com/oauth2/token", "targetAmfSets": [ { "regionId": "01", "setId": "001", "setFqdn": "set001.region01.amfset.5gc.mnc311.mcc282.3gppnetwork.org" }, { "regionId": "02", "setId": "002", "setFqdn": "set002.region01.amfset.5gc.mnc311.mcc282.3gppnetwork.org" } ] }
- Configure the Time Profile managed
object:
NSI-Profile consists of network slice name and ID and NRF-ID ,Target AMF lists which are associated to the slice.
- Request_Type: POST
- URL: http://host:port/nnssf-configuration/v1/timeprofiles
- Body: Refer to Sample TimeProfile-Body section for sample message/s and OpenApi for schema.
REST message sample - Time Profiles
http://host:port/nnssf-configuration/v1/timeprofiles POST Content-Type: application/json BODY { "name": "WEEKDAY-BUSY", "startDate": "2020-01-01", "endDate": "2020-12-01", "daysOfWeek": [ "MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY" ] "timeSpans": [ { "startTime": "09:00:00", "endTime": "12:00:00" }, { "startTime": "16:00:00", "endTime": "21:00:00" } ] }
- Configure the Nssai Auth managed object:
- Request_Type: POST
- URL: http://localhost:5755/nnssf-configuration/v1/nssaiauth/
- Body: Refer to Sample Nssai Auth -Body section for sample message/s and OpenApi for schema.
REST message sample - Nssai Auth
http://localhost:5755/nnssf-configuration/v1/nssaiauth/ POST { "name": "NSSAI-ATH-1", "plmnId": { "mcc": "311", "mnc": "282" }, "tac": "100001", "snssai": { "sst": "1", "sd": "EABB01" }, "grant": "ALLOWED" }
- Configure the NSS Rule managed object:
NSS Rules are policy rules which enable operator to ALLOW/REJECT a request for Network Slice Selection request and If allowed then map to a Network Slice.
- Request_Type: POST
- URL: http://{apiRoot}/nnssf-configuration/v1/nssrules
- Body: Refer to Sample NSS-Rule -Body section for sample message/s and OpenApi for schema.
REST message sample - NSS Rules
http://host:port/nnssf-configuration/v1/nssrules POST Content-Type: application/json BODY { "name": "NSSRULE01", "amfId": "1", "plmnId": { "mcc": "311", "mnc": "282", }, "tac": "100001", "snssai": { "sst": "1", "sd": "EABB01" }, "salience": "0", "behavior": { "accessType": "3GPP_ACCESS", "nsiProfiles": [ { "name": "NSI001", "timeProfile": "WEEKDAY-BUSY", "salience": 1 }, { "name": "NSI002", "salience": 0 } ] } }
- Configure the Configured NSSAI managed
object:
Configured NSSAI enables customer to configure default configures NSSAI based on one or more of the following parameters PLMN, TAC, AMF-ID .
- Request_Type: POST
- URL: http://{apiRoot}/nnssf-configuration/v1/configuredsnssais
- Body: Refer to Sample Configured-NSSAI-Body section for sample message/s and OpenApi for schema.
REST message sample - Configured S-NSSAIs
http://host:port/nnssf-configuration/v1/configuredsnssais POST Content-Type: application/json BODY { "plmn": { "mcc": "311", "mnc": "282", }, "tac": "100001"", "salience": 0 "nssai": [ { "sst": 1, "sd": "EABB01"" } ] }
- Configure the AMF Resolution managed
object:
AMF Resolution enables customer to configure mapping candidate AMF list to a Target AMF set ID and Region ID.
- Request_Type: POST
- URL: http: //{apiRoot}/nnssf-configuration/v1/amfresolutions
- Body: Refer to Sample AMF Resolution-Body section for sample messages and Open API for schema.
REST message sample - AMF Resolutions
http://host:port/nnssf-configuration/v1/amfresolutions POST Content-Type: application/json BODY { "regionId": "01", "setId": "001", "candidateAmfList": [ { "fqdn": "pt01.set001.region01.amfset.5gc.mnc311.mcc282.3gppnetwork.org", "instanceId": "9faf1bbc-6e4a-4454-a507-aef01a101a03" }, { "fqdn": "pt02.set001.region01.amfset.5gc.mnc311.mcc282.3gppnetwork.org", "instanceId": "9faf1bbc-6e4a-4454-a507-aef01a101a04" } ] }