Ankur Upadhyaya | 12fc2e7 | 2023-05-05 18:23:24 +0530 | [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.3 Release |
| 6 | =================== |
| 7 | |
| 8 | 1.3.0 Release Details |
| 9 | --------------------- |
| 10 | |
| 11 | SD-Core supports 4G & 5G network functions and includes APIs for configuration, telemetry, |
| 12 | policy management. Access networks can connect to Access & Mobility Management Function (AMF) |
| 13 | or Mobility Management Entity (MME) depending on the type of access used. Below is the summary |
| 14 | of the features delivered in SD-Core 1.3 Release. |
| 15 | |
| 16 | Highlights |
| 17 | ---------- |
| 18 | |
| 19 | Release v1.3.0 focuses on stabilizing Cloud Native support to 5G network functions and adding Metrics support. |
| 20 | Also, towards greater adoption by community members, many members used SD-Core to tests against real |
| 21 | hardware gNodeB and phones. |
| 22 | All new functionality in this release contributes to support of 5G Network functionality. |
| 23 | |
| 24 | |
| 25 | **Real gNodeB & real UE Tests**: Multiple community members mentioned success with SD-Core being used against |
| 26 | real UE & gNB. To name the few, CPQD(Brazil), ONF, Pronto project for DARPA, etc. ONF used gNodeB from Sercomm and |
| 27 | while the real phones were Google Pixel and Moto5G. |
| 28 | |
| 29 | We also enhanced 5G core to support the test IMSI(the one having mcc/mnc as leading zeroes) for development testing. |
| 30 | |
| 31 | **5G Metric Dashboard**: A new NF, Metric Function has been added to provision 5G Cloud Native metrics. |
| 32 | The Metric Function acts as both metrics aggregator and processor towards metric consumers like Analytics Engine, |
| 33 | API Server or Prometheus Server. |
| 34 | |
| 35 | The 5G Metric dashboard shows whether the gNodeB and UPF are connected to the core, how many active UEs are connected, |
| 36 | including UE’s IMSI and Slice information, and the uplink (Tx Bitrate) and downlink (Rx Bitrate) throughput at the UPF. |
| 37 | Metrics work can be extended to show various metrics from 5G core network. |
| 38 | |
| 39 | **NRF Cache and Notification**: As part of NF Discovery Service, Each NF discovers Target NF for its profiles from NRF |
| 40 | and stores Target NF profiles in a local cache. One cache is created per Target NF Type to make the lookup faster. |
| 41 | |
| 42 | The NF creates subscription for the NF profiles received from the NRF. When a notification is received from the NRF |
| 43 | on profile Deregistration, the entry is evicted from the local cache. This will trigger the host NF to perform |
| 44 | requested NF Discovery during the next UE procedure. |
| 45 | |
| 46 | **Test IMSI Support**: This support allows users to employ Test UEs with leading zeroes(mcc/mnc with leading zeroes) |
| 47 | with SD-Core 5G. This eliminates the conflict with commercial PLMNs during UE attach. |
| 48 | |
| 49 | **Static UE IP-Address Support**: The SMF shall support allocation of static IP-address to UE. This feature shall be |
| 50 | available via configuration of SUPI to IP-address mapping under SMF specific section via override values file. |
| 51 | |
| 52 | **Dynamic Subscription revoking provision**: This feature enables 5G network to revoke subscription of specific UE. |
| 53 | It is required that user identifies the IP-Address of specific UE to be disabled. The custom user application can |
| 54 | make available the IP-Address of specific UE to 5G core network via Metric-Function API. The 5G network shall revoke |
| 55 | the specific UE’s subscription based on UE IP-Addresses received. |
| 56 | |
| 57 | **Multiple gNBs Support in gNBSim**: This enhancement allows deploying multiple gNBSim instances. This would extend |
| 58 | gNBSim capabilities towards XN and N2 handover procedures. |
| 59 | |
| 60 | **Inter-op stabilisation across multiple instances of SMF and AMF**: Enhancements have been done around stabilisation |
| 61 | of multiple instances of SMF and AMF inter-operation. This adds robustness towards cloud native stateless and |
| 62 | high-availability feature. |
| 63 | |
| 64 | **Autoscaling of AMF/SMF instances in AIAB using KEDA**: It enables dynamic scaling of network functions to handle |
| 65 | increased traffic or workload demands, ensuring optimal performance and cost-effectiveness. |
| 66 | Kubernetes Event-driven Autoscaling (KEDA) is an open-source tool that makes it easier to implement autoscaling for |
| 67 | cloud-native network functions(https://github.com/kedacore/keda). |
| 68 | |
| 69 | **Minor Enhancements**: |
| 70 | |
| 71 | - Update Subscriber Context in DB after the Handover Procedure is completed. |
| 72 | - Multiple instances of Sctp-lb could run but this should be done manually. |
| 73 | |
| 74 | Known Limitations: |
| 75 | -------------------- |
| 76 | |
| 77 | - Only one instance of the UPF-adapter pod should be deployed. |
| 78 | |
| 79 | - Scale up or down instances of AMF/SMF/Sctp-Lb can be done manually. |
| 80 | |
| 81 | - If webui pod is restarted and if callback configuration is not provided in webui pod then simapp does |
| 82 | not download the config again to webui. Restarting the simapp pod solves the problem most of the time. |
| 83 | |
| 84 | - UPF Pod needs to have UE pool configuration and UPF does not use UE IP Pool configuration from Slice APIs. |
| 85 | |
| 86 | .. note:: |
| 87 | For any 3gpp release compliance refer - (:ref:`4g-compliance`) and (:ref:`5g-compliance`) |
| 88 | |
| 89 | Component Versions in the 1.3.0 Release |
| 90 | --------------------------------------- |
| 91 | |
| 92 | Helm Chart Versions and their component charts and containers: |
| 93 | |
Ankur Upadhyaya | a8c137e | 2023-05-10 20:58:54 +0530 | [diff] [blame^] | 94 | * sdcore-helm-chart: ``0.12.8`` |
Ankur Upadhyaya | 12fc2e7 | 2023-05-05 18:23:24 +0530 | [diff] [blame] | 95 | * omec-control-plane: ``0.12.0`` |
| 96 | * hssdb: ``omecproject/c3po-hssdb:master-df54425`` |
| 97 | * hss : ``omecproject/c3po-hss:master-df54425`` |
| 98 | * pcrf : ``omecproject/c3po-pcrf:pcrf-d58dd1c`` |
| 99 | * pcrfdb : ``omecproject/c3po-pcrf:pcrf-d58dd1c`` |
| 100 | * config4g : ``omecproject/5gc-webui:master-1121545`` |
| 101 | * spgwc : ``omecproject/spgw:master-e419062`` |
| 102 | * mme : ``omecproject/nucleus:master-a8002eb`` |
| 103 | |
| 104 | * omec-sub-provision: ``0.6.0`` |
| 105 | * simapp: ``omecproject/simapp:main-a4f741a`` |
| 106 | |
Ankur Upadhyaya | a8c137e | 2023-05-10 20:58:54 +0530 | [diff] [blame^] | 107 | * 5g-control-plane: ``0.8.15`` |
Ankur Upadhyaya | 12fc2e7 | 2023-05-05 18:23:24 +0530 | [diff] [blame] | 108 | * amf: ``omecproject/5gc-amf:master-a4759db`` |
| 109 | * nrf: ``omecproject/5gc-nrf:master-b747b98`` |
Ankur Upadhyaya | a8c137e | 2023-05-10 20:58:54 +0530 | [diff] [blame^] | 110 | * smf: ``omecproject/5gc-smf:master-13e5671`` |
Ankur Upadhyaya | 12fc2e7 | 2023-05-05 18:23:24 +0530 | [diff] [blame] | 111 | * ausf: ``omecproject/5gc-ausf:master-c84dff4`` |
| 112 | * nssf: ``omecproject/5gc-nssf:master-4e5aef3`` |
| 113 | * pcf: ``omecproject/5gc-pcf:master-bcbdeb0`` |
| 114 | * udr: ``omecproject/5gc-udr:master-35eb7b7`` |
| 115 | * udm: ``omecproject/5gc-udm:master-6956659`` |
| 116 | * webui: ``omecproject/5gc-webui:master-1121545`` |
| 117 | * sctplb: ``omecproject/sctplb:master-bf081d5`` |
| 118 | * metricfunc: ``omecproject/metricfunc:main-58fa274`` |
Ankur Upadhyaya | a8c137e | 2023-05-10 20:58:54 +0530 | [diff] [blame^] | 119 | * upfadapter: ``omecproject/5gc-smf:master-13e5671`` |
Ankur Upadhyaya | 12fc2e7 | 2023-05-05 18:23:24 +0530 | [diff] [blame] | 120 | |
| 121 | * bess-upf ``0.1.0`` |
| 122 | * bess: ``omecproject/upf-epc-bess:master-5786085`` |
| 123 | * pfcpiface: ``omecproject/upf-epc-pfcpiface:master-5786085`` |
| 124 | |
| 125 | * 5g-ran-sim ``0.6.5`` |
| 126 | * gnbsim: ``omecproject/5gc-gnbsim:main-1caccfc`` |