ajay | b3f4098 | 2021-12-08 14:26:11 -0800 | [diff] [blame] | 1 | .. |
| 2 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
| 3 | SPDX-License-Identifier: Apache-2.0 |
| 4 | |
ajay | d19711c | 2021-12-07 12:07:04 -0800 | [diff] [blame] | 5 | Configuration Overview |
| 6 | ====================== |
ajay | 60fd69f | 2021-11-23 22:38:10 -0800 | [diff] [blame] | 7 | |
ajay | 2c0f6f4 | 2021-12-02 22:45:19 -0800 | [diff] [blame] | 8 | Reference helm chart |
| 9 | -------------------- |
ajay | 60fd69f | 2021-11-23 22:38:10 -0800 | [diff] [blame] | 10 | |
ajay | 2c0f6f4 | 2021-12-02 22:45:19 -0800 | [diff] [blame] | 11 | - `SD-Core Helm Chart Repository <https://gerrit.opencord.org/admin/repos/sdcore-helm-charts>`_ |
| 12 | |
| 13 | Configuration Methods |
| 14 | --------------------- |
| 15 | SD-Core supports 2 ways to configure network functions and micro services. |
| 16 | |
| 17 | - Helm Chart |
| 18 | |
| 19 | - Each individual network function and microservice has its own helm chart. |
| 20 | - User needs to provide override values and deploy the network functions as per their need. |
| 21 | |
| 22 | - REST Config Interface |
| 23 | |
| 24 | - Basic static configuration is passed through helm chart |
| 25 | - Dynamic slice creation APIs are provided through REST interface. |
| 26 | - REST APIs are defined to create/modify/delete network slice. |
| 27 | - REST APIs are also provided to provision subscribers and grouping the subscribers under device Group. |
| 28 | |
ajay | ec9bb9d | 2021-12-08 00:03:36 -0800 | [diff] [blame] | 29 | Configuration Steps |
| 30 | ------------------- |
Vijaya Rani | 59a1783 | 2021-12-03 19:27:41 +0530 | [diff] [blame] | 31 | This Configuration describes what to configure at high level from RoC/SIMAPP. ConfigPod stores this configuration |
ajay | ec9bb9d | 2021-12-08 00:03:36 -0800 | [diff] [blame] | 32 | and publish to respective clients over REST/grpc. |
ajay | 2c0f6f4 | 2021-12-02 22:45:19 -0800 | [diff] [blame] | 33 | |
ajay | ec9bb9d | 2021-12-08 00:03:36 -0800 | [diff] [blame] | 34 | - Step1 : Provision subscriber in 4G/5G subsystem |
ajay | 2c0f6f4 | 2021-12-02 22:45:19 -0800 | [diff] [blame] | 35 | |
ajay | ec9bb9d | 2021-12-08 00:03:36 -0800 | [diff] [blame] | 36 | - This step is used to configure IMSI in the SD-Core |
| 37 | - This procedure is used to configure security keys for a subscriber |
| 38 | - Subscribers can be created during system startup or later |
| 39 | |
| 40 | - Step2 : Device Group Configuration |
| 41 | |
| 42 | - Group multiple devices under device group |
| 43 | - Configure QoS for the device group |
| 44 | - Configure IP domain configuration for the device group e.g. MTU, IP Pool, DNS server |
| 45 | |
| 46 | |
| 47 | - Step3: Network Slice Configuration |
| 48 | |
| 49 | - Configuration to create a Network Slice |
| 50 | - Add device Group into Network Slice |
| 51 | - Slice contains the Slice level QoS configuration |
Vijaya Rani | 59a1783 | 2021-12-03 19:27:41 +0530 | [diff] [blame] | 52 | - Site configuration including UPF, eNBs/gNBs assigned to the slice |
ajay | 8794529 | 2021-12-08 00:52:00 -0800 | [diff] [blame] | 53 | - Applications allowed to be accessed by this slice (see :ref:`application-filtering`) |
Vijaya Rani | 59a1783 | 2021-12-03 19:27:41 +0530 | [diff] [blame] | 54 | |
Vijaya Rani | 59a1783 | 2021-12-03 19:27:41 +0530 | [diff] [blame] | 55 | |