S-NSSAI value fix

docker-compose/docker-compose-slicing-basic-nrf.yaml

@@ -197,11 +197,11 @@ services:
             - PLMN_SUPPORT_MNC=95
             - PLMN_SUPPORT_TAC=0xa000
             - SST_0=128
-            - SD_0=2
+            - SD_0=128
             - SST_1=1
             - SD_1=0xFFFFFF
             - SST_2=130
-            - SD_2=4
+            - SD_2=130
             - AMF_INTERFACE_NAME_FOR_NGAP=eth0
             - AMF_INTERFACE_NAME_FOR_N11=eth0
             - SMF_INSTANCE_ID_0=1
@@ -292,7 +292,7 @@ services:
             - DISCOVER_UPF=yes
             - USE_FQDN_DNS=yes
             - NSSAI_SST0=128
-            - NSSAI_SD0=2
+            - NSSAI_SD0=128
         depends_on:
             - oai_amf
             - oai_nrf_slice12
@@ -385,7 +385,7 @@ services:
             - DISCOVER_UPF=yes
             - USE_FQDN_DNS=yes
             - NSSAI_SST1=130
-            - NSSAI_SD1=4
+            - NSSAI_SD1=130
         depends_on:
             - oai_amf
             - oai_nrf_slice3
@@ -428,7 +428,7 @@ services:
             - NRF_API_VERSION=v1
             - NRF_FQDN=oai_nrf_slice12
             - NSSAI_SST_0=128
-            - NSSAI_SD_0=2
+            - NSSAI_SD_0=128
             - DNN_0=default
         depends_on:
             - oai_nrf_slice12
@@ -516,7 +516,7 @@ services:
             - INTERFACE_ACCESS=eth1
             - INTERFACE_CORE=eth2
             - INTERFACE_CP=eth0
-            - NSSAI_SD_0=4
+            - NSSAI_SD_0=130
             - SST=130
             - DNN=oai.ipv4
             - REGISTER_NRF=yes

docker-compose/docker-compose-slicing-ransim.yaml

@@ -15,7 +15,7 @@ services:
             - GTP_IP=192.168.70.152
             - NGAP_PEER_IP=192.168.70.138
             - SST=128
-            - SD=2
+            - SD=128
             - IGNORE_STREAM_IDS=true
             # UE Config Parameters
             - NUMBER_OF_UE=1
@@ -29,10 +29,12 @@ services:
             - GNB_IP_ADDRESS=192.168.70.152
             - PDU_TYPE=IPv4
             - APN=default
+            - SST_R=128
+            - SD_R=128
             - SST_C=128
-            - SD_C=2
+            - SD_C=128
             - SST_D=128
-            - SD_D=2
+            - SD_D=128
         networks:
             public_net:
                 ipv4_address: 192.168.70.152
@@ -126,7 +128,7 @@ services:
             - GNBID=5
             - TAC=0x00a000
             - SST=130
-            - SD=000004
+            - SD=000082
             - PagingDRX=v32
             - RANUENGAPID=0 
             - IMEISV=35609204079514

docker-compose/nssf_slice_config.yaml

@@ -6,7 +6,7 @@ configuration:
   nsiInfoList:
     - snssai:
         sst: 128
-        sd: '2'
+        sd: '128'
       nsiInformationList:
         nrfId: http://192.168.70.136:80/nnrf-disc/v1/nf-instances
         nsiId: '11'
@@ -17,7 +17,7 @@ configuration:
         nsiId: '12'
     - snssai:
         sst: 130
-        sd: '4'
+        sd: '130'
       nsiInformationList:
         nrfId: http://192.168.70.137:80/nnrf-disc/v1/nf-instances
         nsiId: '12'
@@ -74,10 +74,10 @@ configuration:
                 tac: 33456
               supportedSnssaiList:
                 - sst: 128
-                  sd: 2
+                  sd: 128
                 - sst: 1
                 - sst: 130
-                  sd: 4
+                  sd: 130
         - nfId: 405e8251-cc5a-45dd-a494-efb9eaf1cd68
           supportedNssaiAvailabilityData:
               tai:

docs/DEPLOY_SA5G_SLICING.md

@@ -74,9 +74,9 @@ 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=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
+* Slice1: [SST=128,SD=128] =>   NRF1, SMF1, UPF1, GNB1, UE1
+* Slice2: [SST=1]          =>   NRF1, SMF2, UPF2, GNB2, UE2
+* Slice3: [SST=130,SD=130] =>   NRF2, SMF3, VPP-UPF3, GNB3, UE3
 
 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/>