You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- ``omec-control-plane``: 4G network function Helm charts
25
+
- ``5g-control-plane``: 5G network function Helm charts
26
+
- ``omec-sub-provision``: Simapp Helm charts
27
+
- ``5g-ran-sim``: gNBSim Helm charts
25
28
26
29
Configuration Methods
27
30
---------------------
28
-
SD-Core supports 2 ways to configure network functions and micro services.
29
31
30
-
- Helm Chart
32
+
SD-Core supports two methods to configure network functions and microservices:
31
33
32
-
- Each individual network function and microservice has its own helm chart.
33
-
- User needs to provide override values and deploy the network functions as per their need.
34
-
- Use above helm charts appropriately and provide override values and install 4G/5G NFs.
34
+
Helm Chart Configuration
35
+
^^^^^^^^^^^^^^^^^^^^^^^^
35
36
36
-
- REST Config Interface
37
+
- Each network function and microservice has its own Helm chart
38
+
- Users provide override values and deploy network functions according to their requirements
39
+
- Use the appropriate Helm charts with override values to install 4G/5G network functions
37
40
38
-
- Basic static configuration is still passed through helm chart ( logging level, image,...)
39
-
- Dynamic *Network Slice* management APIs are provided through REST interface.
40
-
- REST APIs are defined to create/modify/delete network slice.
41
-
- REST APIs are also provided to provision subscribers and grouping the subscribers under device Group.
41
+
REST Configuration Interface
42
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
43
+
44
+
- Basic static configuration is provided through Helm charts (e.g., logging level, images)
45
+
- Dynamic Network Slice management APIs are available through a REST interface
46
+
- REST APIs enable creation, modification, and deletion of network slices
47
+
- REST APIs also support subscriber provisioning and grouping subscribers into device groups
42
48
43
49
.. note::
44
-
- Simapp is the example of REST interface based configuration to provision subscribers in SD-Core
45
-
- Simapp is also used to provision Network Slices in SD-Core in the absence of Portal
46
-
- Aether ROC Portal used REST interface to configure Network Slices in SD-Core
50
+
- Simapp is an example implementation of REST interface-based configuration for
51
+
provisioning subscribers in SD-Core
52
+
- Simapp is also used to provision network slices in SD-Core in the absence of a portal
53
+
- Aether ROC Portal uses the REST interface to configure network slices in SD-Core
47
54
48
55
.. image:: ../_static/images/config_slice.png
49
56
:width:500px
@@ -53,59 +60,67 @@ SD-Core supports 2 ways to configure network functions and micro services.
53
60
54
61
Configuration Steps
55
62
-------------------
56
-
This Configuration describes what to configure at high level from RoC/SIMAPP. ConfigPod stores this configuration
57
-
and publish to respective clients over REST/grpc.
58
63
59
-
- Step1 : Provision subscriber in 4G/5G subsystem
64
+
This section describes the high-level configuration steps from ROC/Simapp. The ConfigPod
65
+
stores this configuration and publishes it to respective clients over REST/gRPC.
60
66
61
-
- *Can be done only through SIMAPP*
62
-
- This step is used to configure IMSI in the SD-Core
63
-
- This procedure is used to configure security keys for a subscriber
64
-
- Subscribers can be created during system startup or later
67
+
**Step 1: Provision Subscribers in 4G/5G Subsystem**
65
68
66
-
- Step2 : Device Group Configuration
69
+
- Can be done only through Simapp
70
+
- Configure IMSI (International Mobile Subscriber Identity) in SD-Core
71
+
- Configure security keys for each subscriber
72
+
- Subscribers can be created during system startup or at runtime
67
73
68
-
- Group multiple devices under device group
69
-
- Configure QoS for the device group
70
-
- Configure IP domain configuration for the device group e.g. MTU, IP Pool, DNS server
74
+
**Step 2: Device Group Configuration**
71
75
76
+
- Group multiple devices under a device group
77
+
- Configure QoS (Quality of Service) for the device group
78
+
- Configure IP domain settings for the device group (e.g., MTU, IP pool, DNS server)
72
79
73
-
- Step3: Network Slice Configuration
80
+
**Step 3: Network Slice Configuration**
74
81
75
-
- Configuration to create a Network Slice
76
-
- Add device Group into Network Slice
77
-
- Slice contains the Slice level QoS configuration
78
-
- Site configuration including UPF, eNBs/gNBs assigned to the slice
79
-
- Applications allowed to be accessed by this slice (see :ref:`application-filtering`)
82
+
- Create a network slice
83
+
- Add device groups to the network slice
84
+
- Configure slice-level QoS settings
85
+
- Configure site information including UPF, eNBs/gNBs assigned to the slice
86
+
- Define applications allowed to be accessed by this slice (see :ref:`application-filtering`)
80
87
81
88
.. note::
82
-
- Step1 can only be done through Simapp. Look for simapp override values.
83
-
- Step2 & Step3 can be done through Simapp or ROC. Simapp has option to create network slice. Look for configuration *provision-network-slice: false* in simapp configuration
89
+
- Step 1 can only be performed through Simapp. Refer to Simapp override values.
90
+
- Steps 2 and 3 can be performed through either Simapp or ROC. Simapp has an option
91
+
to create network slices. Look for the configuration parameter
92
+
``provision-network-slice: false`` in the Simapp configuration.
84
93
85
94
.. note::
86
95
If UPF is used to allocate UE address allocation then even if you have specified UE
87
96
address pool in the slice config, you still need to add the address pool
88
97
configuration in the UPF deployment.
89
98
90
-
4G, 5G Configuration Differences
91
-
--------------------------------
92
-
One of the most important difference in 4G & 5G configuration is around network slice. 5G has
93
-
network slice Ids sent on 3gpp defined protocol messages whereas 4G does not have any slice Id in
94
-
3gpp defined protocol messages. We implement slicing in 4G using APNs. Let's go over these
95
-
difference in detail below,
96
-
97
-
- **Slice Id** : Since 4G does not have slice Id in any protocol messages, configured slice Ids
98
-
are ignored in 4G components. So it also means that even if configured slice Ids are
99
-
duplicate it will not have any impact. But its still a good practice to have unique Slice
100
-
Id per slice.
101
-
102
-
- **APN/DNN configuration**: In case of 4G each slice should have separate APN. This is required
103
-
because APN is used as slice identifier internally in the 4G modules. This is not true in
104
-
case of 5G because 5G has slice Id along with APN/DNN. So in general its good practice to
105
-
keep APN/DNN in the slice unique so same slice can work for 4G & 5G configuration.
106
-
107
-
- **DNN/APN in Initial Attach/Register Message** : In case of 4G, if UE has set any random APN then
108
-
MME overrides the APN based on the user profile in HSS. So its important to note that even if APN
109
-
is not matching with configured APN we are still good. In case of 5G, apn name & Slice ID coming
110
-
from UE is used to select SMF, so its important to have UE configured with correct APN/DNN name.
111
-
Core network passed allowed slice IDs to UE in the registration accept message.
99
+
4G and 5G Configuration Differences
100
+
------------------------------------
101
+
102
+
One of the most important differences between 4G and 5G configuration relates to network
103
+
slicing. 5G includes network slice IDs in 3GPP-defined protocol messages, whereas 4G does
104
+
not. In 4G, we implement slicing using APNs (Access Point Names). Key differences include:
105
+
106
+
**Slice ID**
107
+
108
+
Since 4G does not include slice IDs in protocol messages, configured slice IDs are ignored
109
+
in 4G components. This means duplicate slice IDs will not cause issues in 4G. However, it's
110
+
still best practice to use unique slice IDs per slice for consistency.
111
+
112
+
**APN/DNN Configuration**
113
+
114
+
In 4G, each slice should have a separate APN. This is required because the APN serves as
115
+
the slice identifier internally in 4G modules. In 5G, this restriction doesn't apply because
116
+
5G uses both slice ID and DNN (Data Network Name). As a best practice, keep APNs/DNNs unique
117
+
per slice so the same configuration works for both 4G and 5G.
118
+
119
+
**DNN/APN in Initial Attach/Register Message**
120
+
121
+
In 4G, if a UE sends a random APN, the MME overrides it based on the user profile in HSS.
122
+
This means the connection succeeds even if the APN doesn't match the configured value.
123
+
124
+
In 5G, the APN name and Slice ID from the UE are used to select the SMF, so the UE must
125
+
be configured with the correct APN/DNN name. The core network sends allowed slice IDs to
0 commit comments