Ajay Lotan Thakur | 0b01266 | 2022-10-07 20:18:10 -0700 | [diff] [blame^] | 1 | .. |
| 2 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
| 3 | SPDX-License-Identifier: Apache-2.0 |
| 4 | |
| 5 | SD-Core 1.2 Release |
| 6 | =================== |
| 7 | |
| 8 | 1.2.0 Release Details |
| 9 | --------------------- |
| 10 | |
| 11 | SD-Core supports 4G & 5G network functions. SD-Core provides APIs for configuration, telemetry, |
| 12 | policy management. Access networks can connect to AMF or MME depending on the type of access used. |
| 13 | Below is the summary of the features delivered in SD-Core 1.2 Release. |
| 14 | |
| 15 | |
| 16 | Highlights |
| 17 | ---------- |
| 18 | Release 1.2.0 is focused towards releasing the first version of Cloud Native 5G Network Functions. |
| 19 | All development done in this release is around 5G Network functions. Below is highlighted features |
| 20 | of this release, |
| 21 | |
| 22 | |
| 23 | **NRF Keepalive**: All 5G network functions now register with NRF and enable the keep alive feature. |
| 24 | Each network function periodically updates its subscriptions towards NRF. NRF now removes the |
| 25 | Network Function which fails to send keepalive for a configured number of seconds. This is one of |
| 26 | the foundation features for running multiple instances of Network functions. |
| 27 | |
| 28 | **Multiple SMF Instances**: Aether can be deployed with multiple instances of SMF. If required manually |
| 29 | SMF deployment can be scaled out to add more instances or deployment can be scaled in to reduce the |
| 30 | number of SMF instances. A new kubernetes POD UPF Adapter pod is deployed as an anchor POD. UPF adapter |
| 31 | POD talks to UPF NF. All SMF instances share the resources like SEID, IP address, TEID. SMF now stores |
| 32 | subscriber states in MongoDB. |
| 33 | |
| 34 | **Multiple AMF Instances**: Aether can be deployed with multiple AMF instances of AMF. If required |
| 35 | manually AMF deployment can be scaled out to add more instances or AMF deployment can be scaled in |
| 36 | to reduce the number of AMF instances. A new kubernetes POD SCTP-LB is added to terminate sctp |
| 37 | connections from gNB. All AMF instances share the resources pool like TMSI, AMF-NGAPId. SMF now |
| 38 | stores subscriber states in MongoDB. |
| 39 | |
| 40 | **gNBSim Improvements**: Couple of exciting changes are available in gNBSim now. Notable changes |
| 41 | include following features, |
| 42 | |
| 43 | - gNBSim now supports custom profiles. User can define set of procedures to be executed |
| 44 | for given use |
| 45 | - All the subscribers within a profile can run in parallel. Same way if multiple profiles |
| 46 | are configured then all profiles can run in parallel. These features are important to |
| 47 | make multiple parallel transactions in the core network. |
| 48 | - User defined delay between the procedures of the custom profile. |
| 49 | - Step profile is introduced which helps execute one procedure at a time and wait for |
| 50 | users to call APIs to trigger the next procedure for the Users. This is a really |
| 51 | interesting feature for the developers who want more control on their test case execution. |
| 52 | |
| 53 | **Documentation improvements**: SD-Core documentation is updated with clear separation of 4G/5G |
| 54 | documentation wherever it was needed. Also updated documentation around deployment of 5G, |
| 55 | new PODs and their resource requirements. Some of the new sections have been added to explain |
| 56 | QoS support, application filtering and upf configuration. Also a process has started to move |
| 57 | most of the internal design documents to the google drive which can be accessed by any community |
| 58 | member. Link for the SD-Core public document can be found here. |
| 59 | |
| 60 | **Minor Improvements**: There are couple of enhancements which were done in multiple network functions |
| 61 | |
| 62 | - SMF supports UPF based UE address allocation: SMF need not manage UE address pool now, if |
| 63 | UPF supports UE address allocation. |
| 64 | - Helm Chart changes to run MongoDB in the cluster mode to give database redundancy in the |
| 65 | 5G Core Network. |
| 66 | - Image size reduction- gNBSim, simapp now has a small container image size. |
| 67 | - Dockerfile cleanup - Multiple Dockerfile are cleaned to follow best practices and to |
| 68 | update the base images of compile time & run time images. |
| 69 | - Subscriber config & slice config APIs in the simapp now supports http2. |
| 70 | - Network Functions now handle error in grpc connection towards webconsole |
| 71 | - SMF now sends correct QFI towards UPF instead of 5QI |
| 72 | - Dockerfile improvements to use recent golang version and latest runtime alpine image |
| 73 | - Purge UE api now available in the AMF |
| 74 | - Fixing QoS issues by sending correct AMBR rates towards UE |
| 75 | |
| 76 | Known Issues and Limitations |
| 77 | ---------------------------- |
| 78 | |
| 79 | - Only one instance of UPF-adapter pod should be deployed |
| 80 | - Only one instance of SCTP-Lb pod should be deployed |
| 81 | - If webui pod is restarted and if callback configuration is not provided in webui pod |
| 82 | then simapp does not download the config again to webui. Restarting the simapp pod |
| 83 | solves the problem most of the time. |
| 84 | - UPF Pod needs to have UE pool configuration and UPF does not use UE IP Pool |
| 85 | configuration from Slice APIs |
| 86 | - The same IMSI cannot part of multiple device groups |
| 87 | - At most 5 application filtering rules can be added per Slice |
| 88 | - If a subscriber is attached to a Network Slice then subsequent application filter rules modify/deletion is |
| 89 | not notified towards UE & UPF. If UE disconnects and reconnects back to Network Slice then updated |
| 90 | application filters are applied to UE. |
| 91 | - If No Filtering Rules are configured then only Default(Allow-All) Filter rule is added implicitly. |
| 92 | - PLMN update for Slice does not work. It is recommended to delete the slice and recreate it again with |
| 93 | correct PLMN. |
| 94 | |
| 95 | .. note:: |
| 96 | For any 3gpp release compliance refer - (:ref:`4g-compliance`) and (:ref:`5g-compliance`) |
| 97 | |
| 98 | Component Versions in the 1.2.0 Release |
| 99 | --------------------------------------- |
| 100 | |
| 101 | Helm Chart Versions and their component charts and containers: |
| 102 | |
| 103 | * sdcore-helm-chart: ``0.11.14`` |
| 104 | * omec-control-plane: ``0.11.1`` |
| 105 | * hssdb: ``omecproject/c3po-hssdb:master-df54425`` |
| 106 | * hss : ``omecproject/c3po-hss:master-df54425`` |
| 107 | * pcrf : ``omecproject/c3po-pcrf:pcrf-d58dd1c`` |
| 108 | * pcrfdb : ``omecproject/c3po-pcrf:pcrf-d58dd1c`` |
| 109 | * config4g : ``omecproject/5gc-webui:master-87adbcc`` |
| 110 | * spgwc : ``omecproject/spgw:master-e419062`` |
| 111 | * mme : ``omecproject/nucleus:master-a8002eb`` |
| 112 | |
| 113 | * omec-sub-provision: ``0.5.3`` |
| 114 | * simapp: ``omecproject/simapp:main-a4f741a`` |
| 115 | |
| 116 | * 5g-control-plane: ``0.7.15`` |
| 117 | * amf: ``romecproject/5gc-amf:master-af1c9f1`` |
| 118 | * nrf: ``omecproject/5gc-nrf:master-4313faa`` |
| 119 | * smf: ``omecproject/5gc-smf:master-d94b123`` |
| 120 | * ausf: ``omecproject/5gc-ausf:master-c84dff4`` |
| 121 | * nssf: ``omecproject/5gc-nssf:master-4e5aef3`` |
| 122 | * pcf: ``omecproject/5gc-pcf:master-bcbdeb0`` |
| 123 | * udr: ``omecproject/5gc-udr:master-35eb7b7`` |
| 124 | * udm: ``omecproject/5gc-udm:master-a0f0671`` |
| 125 | * webui: ``omecproject/5gc-webui:master-fec9bfc`` |
| 126 | * sctplb: ``omecproject/sctplb:master-bf081d5`` |
| 127 | * upfadapter: ``omecproject/5gc-smf:master-d7c32f2`` |
| 128 | |
| 129 | * bess-upf ``0.1.0`` |
| 130 | * bess: ``omecproject/upf-epc-bess:master-5786085`` |
| 131 | * pfcpiface: ``omecproject/upf-epc-pfcpiface:master-5786085`` |
| 132 | |
| 133 | * 5g-ran-sim ``0.5.9`` |
| 134 | * gnbsim: ``omecproject/5gc-gnbsim:main-0e4b557`` |