diff --git a/docker-compose/docker-compose-slicing-basic-nrf.yaml b/docker-compose/docker-compose-slicing-basic-nrf.yaml
index 4e1ccbfbdd132a4ed36e584861839baddd1535a9..b34b3048013c30b3f01c7fe230eed64f439eaa35 100644
--- a/docker-compose/docker-compose-slicing-basic-nrf.yaml
+++ b/docker-compose/docker-compose-slicing-basic-nrf.yaml
@@ -198,8 +198,10 @@ services:
- PLMN_SUPPORT_TAC=0xa000
- SST_0=128
- SD_0=2
- - SST_1=129
- - SD_1=3
+ - SST_1=1
+ - SD_1=0xFFFFFF
+ - SST_2=130
+ - SD_2=4
- AMF_INTERFACE_NAME_FOR_NGAP=eth0
- AMF_INTERFACE_NAME_FOR_N11=eth0
- SMF_INSTANCE_ID_0=1
@@ -335,8 +337,8 @@ services:
- REGISTER_NRF=yes
- DISCOVER_UPF=yes
- USE_FQDN_DNS=yes
- - NSSAI_SST1=129
- - NSSAI_SD1=3
+ - NSSAI_SST1=1
+ - NSSAI_SD1=0
depends_on:
- oai_amf
- oai_nrf_slice12
@@ -473,8 +475,8 @@ services:
- NRF_PORT=80
- NRF_API_VERSION=v1
- NRF_FQDN=oai_nrf_slice12
- - NSSAI_SST_0=129
- - NSSAI_SD_0=3
+ - NSSAI_SST_0=1
+ - NSSAI_SD_0=0
- DNN_0=oai
depends_on:
- oai_nrf_slice12
diff --git a/docker-compose/docker-compose-slicing-ransim.yaml b/docker-compose/docker-compose-slicing-ransim.yaml
index c6257955e4831860f52c42c5c4a152aadf305fc9..5093de600cba1264ec91b531115f3a44acd13b06 100644
--- a/docker-compose/docker-compose-slicing-ransim.yaml
+++ b/docker-compose/docker-compose-slicing-ransim.yaml
@@ -53,8 +53,8 @@ services:
MCC: '208'
MNC: '95'
MNC_LENGTH: 2
- NSSAI_SST: 129
- NSSAI_SD0: 3
+ NSSAI_SST: 1
+ NSSAI_SD0: 0
NSSAI_SD1: 112233
AMF_IP_ADDRESS: 192.168.70.138
GNB_NGA_IF_NAME: eth0
@@ -80,8 +80,8 @@ services:
FULL_KEY: '0C0A34601D4F07677303652C0462535B'
OPC: '63bfa50ee6523365ff14c1f45f88737d'
DNN: oai
- NSSAI_SST: 129
- NSSAI_SD: 3
+ NSSAI_SST: 1
+ NSSAI_SD: 0
USE_ADDITIONAL_OPTIONS: -E --sa --rfsim -r 106 --numerology 1 -C 3619200000 --nokrnmod
depends_on:
- oai-gnb
@@ -103,8 +103,8 @@ services:
# FULL_KEY: '0C0A34601D4F07677303652C0462535B'
# OPC: '63bfa50ee6523365ff14c1f45f88737d'
# DNN: oai
-# NSSAI_SST: 129
-# NSSAI_SD: 3
+# NSSAI_SST: 1
+# NSSAI_SD: 0
# USE_ADDITIONAL_OPTIONS: -E --sa --rfsim -r 106 --numerology 1 -C 3619200000 --nokrnmod
# depends_on:
# - oai-gnb
diff --git a/docker-compose/nssf_slice_config.yaml b/docker-compose/nssf_slice_config.yaml
index 607797b476c238af50cff9c7d7027258e099a3b2..47f43ecf8d467d3ec84239d861c4757de0a378dd 100644
--- a/docker-compose/nssf_slice_config.yaml
+++ b/docker-compose/nssf_slice_config.yaml
@@ -11,8 +11,7 @@ configuration:
nrfId: http://192.168.70.136:80/nnrf-disc/v1/nf-instances
nsiId: '11'
- snssai:
- sst: 129
- sd: '3'
+ sst: 1
nsiInformationList:
nrfId: http://192.168.70.136:80/nnrf-disc/v1/nf-instances
nsiId: '12'
@@ -76,8 +75,7 @@ configuration:
supportedSnssaiList:
- sst: 128
sd: 2
- - sst: 129
- sd: 3
+ - sst: 1
- sst: 130
sd: 4
- nfId: 405e8251-cc5a-45dd-a494-efb9eaf1cd68
diff --git a/docs/DEPLOY_SA5G_SLICING.md b/docs/DEPLOY_SA5G_SLICING.md
index 19f33ff10fca4a0bdd7a95b9e92aa55b57ed8406..829a91ee407a1756663006d69bd241cbce2805ff 100644
--- a/docs/DEPLOY_SA5G_SLICING.md
+++ b/docs/DEPLOY_SA5G_SLICING.md
@@ -74,11 +74,11 @@ Currently 3GPP allows up to eight (8) S-NSSAIs in the NSSAI sent in signaling me
As shown in figure above, there are 3 S-NSSAIs configured (Can be differentiated with colors) viz. <br/>
Note:- Here we have used standardised SST values (2,3,4), because rf-simulator only supports SST values 1,2,3,4. Moreover, it only for numerical refernece and does not reflect standrd SST behaviour e.g. URLCC, MIoT, V2X etc.<br/>
-* Slice1: [SST=2,SD=2] => NRF1, SMF1, UPF1, GNB1, UE1
-* Slice2: [SST=3,SD=3] => NRF1, SMF2, UPF2, GNB2, UE2
-* Slice3: [SST=4,SD=4] => NRF2, SMF3, VPP-UPF3, GNB3, UE3
+* Slice1: [SST=128,SD=2] => NRF1, SMF1, UPF1, GNB1, UE1
+* Slice2: [SST=1] => NRF1, SMF2, UPF2, GNB2, UE2
+* Slice3: [SST=130,SD=4] => NRF2, SMF3, VPP-UPF3, GNB3, UE3
-Here AMF, NSSF, UDM, UDR, AUSF are common to all slices. SMF and UPF in S-NSSAI 2 and 3 have same NRF hence both UPFs are discoverable to both SMF. You can verify in the logs that both SMFs are successfullt associated to both UPFs in S-NSSAI 2 and 3. Here number of SMFs/UPFs for registered under single (NSI) NRF is part of operator's network planning.<br/>
+Here AMF, NSSF, UDM, UDR, AUSF are common to all slices. SMF and UPF in slice 1 and 2 have same NRF hence both UPFs are discoverable to both SMF. You can verify in the logs that both SMFs are successfullt associated to both UPFs in slice 2 and 3. Here number of SMFs/UPFs for registered under single (NSI) NRF is part of operator's network planning.<br/>
**Let's begin !!**
@@ -400,4 +400,3 @@ Removing network oai-public-core
```
## 12. Reference logs
-