# The Jenkins job requires a tag to build the Docker image.
# Global-JJB script assumes this file is in the repo root.
---
-tag: 5.0.3
+tag: 6.0.1
API-Docs
**********
-This is the API-docs for e-release o-du/l2.
+This is the API-docs for F release o-du/l2.
.. contents::
:depth: 3
A. MAC to Scheduler
a. Air Interface Time : Sends timing information over air interface in terms of SFN and slo, as per Section
- 9.2.3.1.1 of the AAD Spec
+ 9.2.3.1.1 of the AAD Spec.
- b. Cell Configuration Request : MAC provides SCH the cell configuration as per Section 9.2.3.2.1 of the AAD Spec
+ b. Cell Configuration Request : MAC provides SCH the cell configuration as per Section 9.2.3.2.1 of the AAD Spec.
- c. Add UE Configuration Request : MAC provides SCH the configuration/capabilities of a UE as per Section 9.2.3.2.5 of the AAD Spec
+ c. Add UE Configuration Request : MAC provides SCH the configuration/capabilities of a UE as per Section 9.2.3.2.5 of the AAD Spec.
d. Modify UE Reconfiguration Request : MAC provides SCH the re-configuration of UE, also used to
- add/release/modify existing bearers, as per Section 9.2.3.2.6 of the AAD Spec
+ add/release/modify existing bearers, as per Section 9.2.3.2.6 of the AAD Spec.
- e. RACH Indication : MAC receives the RACH Indication and share the contents with SCH as per Section 9.2.3.2.12 of the AAD Spec
+ e. RACH Indication : MAC receives the RACH Indication and share the contents with SCH as per Section 9.2.3.2.12 of the AAD Spec.
f. DL RLC Buffer Status Information : Reports data volume per LC when it is received at MAC as per Section
- 9.2.3.2.16 of the AAD Spec
+ 9.2.3.2.16 of the AAD Spec.
g. UL Buffer Status Report Indication : On reception and decoding of received BSR from the UE, MAC provides SCH
- buffer status report for UL scheduling, as per Section 9.2.3.2.18 of the AAD Spec
+ buffer status report for UL scheduling, as per Section 9.2.3.2.18 of the AAD Spec.
h. UE Delete Request : MAC receives UE delete request and forwards the request to SCH as per Section 9.2.3.2.7
- of the AAD spec.
+ of the AAD Spec.
i. Cell Delete Request : MAC receives UE delete request and forwards the request to SCH as per Section 9.2.3.2.2
- of the AAD spec.
+ of the AAD Spec.
j. Slice Configuration Request : MAC receives Slice Configuration request and forwards the request to SCH as per Section
- 9.2.3.2.3 of the AAD Spec
+ 9.2.3.2.3 of the AAD Spec.
k. Slice Reconfiguration Request : MAC receives Slice Reconfiguration request and forwards the request to SCH as per
- Section 9.2.3.2.4 of the AAD Spec
+ Section 9.2.3.2.4 of the AAD Spec.
+
+ l. Paging Indication : MAC receives Paging Indication and forwards the trigger to SCH as per Section 9.2.3.2.13 of the AAD Spec.
+
+ m. RACH Resource Request : MAC receives RACH Resource Request for dedicated RACH resource allocation and forwards to SCH as per
+ Section 9.2.3.2.14 of the AAD Spec.
+
+ n. RACH Resource Release : MAC receives RACH Resource Release from DU APP and forwards to SCH as per Section 9.2.3.2.15 of the
+ AAD Spec.
+
+ o. DL HARQ Indication : MAC receives UCI Indication and forwards any DL HARQ feedback from UE to SCH as per Sectiion 9.2.3.2.8
+ of the AAD spec.
- l. Paging Indication : MAC receives Paging Indication and forwards the trigger to SCH as per Section 9.2.3.2.13 of the AAD Spec
+ p. UL HARQ CRC Indication : MAC receives CRC Indication from PHY and forwards the decoded results to SCH as per Section
+ 9.2.3.2.9 of the AAD Spec.
B. Scheduler to MAC
- a. Cell Configuration Response - Response to cell configuration request from MAC, as per Section 9.2.3.3.1 of the AAD Spec
+ a. Cell Configuration Response - Response to cell configuration request from MAC, as per Section 9.2.3.3.1 of the AAD Spec.
- b. UE Reconfiguration Response - Response to UE reconfiguration request from MAC, as per Section 9.2.3.3.6 of the AAD Spec
+ b. UE Reconfiguration Response - Response to UE reconfiguration request from MAC, as per Section 9.2.3.3.6 of the AAD Spec.
c. DL Scheduling Information - Provides scheduling information for a given slot for downlink data, as per Section
9.2.3.3.8 of the AAD spec.
e. RAR Information - Informs MAC of uplink scheduling and Msg3 scheduling information, as per Section 9.2.3.3.10 of the AAD Spec.
f. Downlink Control Channel Information - Provides DCI scheduling information for a given slot on PDCCH, as per
- Section 9.2.3.3.11 of the AAD Spec
+ Section 9.2.3.3.11 of the AAD Spec.
g. Downlink Broadcast Allocation - Provides DCI and DL data scheduling information for SIB1 for a given slot for
Broadcast Channel, as per Section 9.2.3.3.12 of the AAD Spec.
- h. UE Delete Response - Response to UE delete request from MAC, as per Section 9.2.3.3.7
+ h. UE Delete Response - Response to UE delete request from MAC, as per Section 9.2.3.3.7 of the AAD Spec.
- i. Cell Delete Response - Response to Cell delete request from MAC, as per Section 9.2.3.3.2
+ i. Cell Delete Response - Response to Cell delete request from MAC, as per Section 9.2.3.3.2 of the AAD Spec.
- j. Slice Configuration Response : Response to Slice Configuration request from MAC, as per Section 9.2.3.3.3 of the AAD Spec
+ j. Slice Configuration Response : Response to Slice Configuration request from MAC, as per Section 9.2.3.3.3 of the AAD Spec.
- k. Slice Reconfiguration Response : Response to Slice Reconfiguration request from MAC, as per Section 9.2.3.3.4 of the AAD Spec
+ k. Slice Reconfiguration Response : Response to Slice Reconfiguration request from MAC, as per Section 9.2.3.3.4 of the AAD Spec.
l. Downlink Paging Allocation : Provides DCI and DL data scheduling information for any Paging queued for a given slot
for Paging Channel, as per Section 9.2.3.3.13 of the AAD Spec.
f. UE Delete Request - Deletes UE information at MAC as per Section 9.2.4.7 of the AAD Spec.
g. DL PCCH Indication - Sends DL PCCH Message to MAC for any Paging scheduled on a slot, as per Section 9.2.4.17 of the AAD Spec.
-
+ h. RACH Resource Request - Requests for dedicated RACH resources for CF-RA with a UE, as per Section 9.2.4.9 of the AAD Spec.
+
+ i. RACH Resource Release - Releases dedicated RACH resources allocated for a UE for CF-RA, as per Section 9.2.4.11 of the AAD Spec.
+
B. MAC to DU APP
a. UE Create Response - Response to UE Create Request from DU Manager as per Section 9.2.4.4 of the AAD Spec.
c. UL-CCCH Indication - Sends the UL CCCH Message received from UE to DU APP as per Section 9.2.4.15 of AAD Spec.
d. UE Delete Response - Response to UE Delete Request from DU Manager as per Section 9.2.4.8 of the AAD Spec.
+
+ e. RACH Resource Response - Responds with dedicated resources allocated for CF-RA for a UE, as per Section 9.2.4.10 of the AAD Spec.
4. DU APP - RLC Interface
B. RLC to DU APP
- a. UE Create Response - Response to UE Create Request from DU APP, as per Section 9.2.5.3
+ a. UE Create Response - Response to UE Create Request from DU APP, as per Section 9.2.5.3 of the AAD Spec.
- b. UE Reconfiguration Response - Response to UE Recofiguration Request from DU APP, as per Section 9.2.5.4
+ b. UE Reconfiguration Response - Response to UE Recofiguration Request from DU APP, as per Section 9.2.5.4 of the AAD Spec.
c. UL RRC Message Tranfer - Delivers RRC Message from UE to CU as per Section 9.2.5.8 of the AAD spec.
d. RRC Message Delivery Report - Informs DU Manager on failed/successful delivery of a DL RRC message to UE, as
per Section 9.2.5.9 of the AAD Spec.
- e. UE Delete Response - Response to UE Delete Request from DU APP, as per section 9.2.5.6
+ e. UE Delete Response - Response to UE Delete Request from DU APP, as per section 9.2.5.6 of the AAD Spec.
5. SMO-OAM - DU APP
A. SMO-OAM to DU APP
- a. Cell Configuration - Sends Basic Cell Configurations to DU APP as per Section 9.2.1.1
+ a. Cell Configuration - Sends Basic Cell Configurations to DU APP as per Section 9.2.1.1 of the AAD Spec.
- b. Slice Configuration - Sends Slice Configurations to DU APP as per Section 9.2.1.2
+ b. Slice Configuration - Sends Slice Configurations to DU APP as per Section 9.2.1.2 of the AAD Spec.
Additional APIs
----------------
e. Slice PM - DU APP sends PM for all Slices in 60sec duration.
+4. MAC - SCH Interface
+
+ A. SCH to MAC
+
+ a. RACH Resource Response : Response to RACH Resource Request for dedicated resource for CF-RA
+
+ b. HARQ Process Release : SCH indicates MAC to release a HARQ process in case a positive acknowledement is received or maximum retransmissions are done already.
| **Date** | **Ver.** | **Author** | **Comment** |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
+| 2022-06-16 | 4.0.0 | Radisys, | F release |
+| | | HCL Technologies | |
+| | | Ltd. | |
++--------------------+--------------------+--------------------+--------------------+
| 2022-01-14 | 3.0.0 | Radisys, | e-release |
| | | HCL Technologies | |
| | | Ltd. | |
As seen in the Figure 9,
-- When a Paging is received from CU and the Cell to be Paged is UP then DU APP will calculate Paging Frame(PF) and i_s(Index of Paging Ocassion/Slot) and groups the Paging of UEs falling on same PF/SFN together and stores in its Cell's Databse.
+- When a Paging is received from O-CU and the Cell to be Paged is UP then DU APP will calculate Paging Frame(PF) and i_s(Index of Paging Ocassion/Slot) and groups the Paging of UEs falling on same PF/SFN together and stores in its Cell's Databse.
- When a Slot Indication for SFN is received then DU APP extracts the Paging of all UEs whose PF is ahead by PAGING_DELTA and builds Paging RRC PDU. DU APP sends the same via DL PCCH Indication to MAC.
- MAC forwards the PAGE to PHY in TX_Data.Request.
+Inter-DU Handover within O-CU
+------------------------------
+
+This section describes the handling of inter-DU handover of a UE within O-DU High.
+
+.. figure:: Inter_DU_Handover_Within_OCU.png
+ :width: 600
+ :alt: Inter-DU Handover withing O-CU
+
+ Figure 9 - Inter_DU Handover call flow
+
+Assumption: UE is RRC connected with DU and PDU data session is active.
+
+- The UE sends Measurement Report message to the source O-DU. This message is sent from O-DU to O-CU in the UL RRC MESSAGE TRANSFER message over F1AP interface.
+
+- Based on UE Measurement Report, O-CU makes a handover decision to another cell belonging to the target O-DU.
+
+- The O-CU sends a UE CONTEXT MODIFICATION REQUEST message to source O-DU to query the latest configuration.
+
+- The DU APP in source O-DU responds with a UE CONTEXT MODIFICATION RESPONSE message that includes latest full configuration information.
+
+- The O-CU sends a UE CONTEXT SETUP REQUEST message to the target O-DU to create an UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message includes Hand-overPreparationInformation. At target O-DU, DU APP sends UE Create Request to MAC and RLC layers to create the UE context with radio resources and receives UE Create Response from the respective protocol layers.
+
+- The target O-DU responds with a UE CONTEXT SETUP RESPONSE message if the target O-DU can admit resources for the handover.
+
+- The O-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source O-DU, which includes RRCReconfiguration message towards the UE. The O-CU also indicates the source O-DU to stop the data transmission for the UE.
+
+- The source O-DU forwards the received RRCReconfiguration message to the UE and then sends the UE Reconfiguration Request to MAC/Scheduler and RLC layer and get the UE Reconfiguration Response from the respective protocol layers.
+
+- The source O-DU responds to the O-CU with UE CONTEXT MODIFICATION RESPONSE message.
+
+- UE triggers Random Access procedure at the target O-DU. This is a contention free random access if UE was informed about its dedicated RACH resources in RRC Reconfiguration message.
+
+- Once Random Access procedure with target O-DU is complete, the UE responds to the target O-DU with a RRCReconfigurationComplete message.
+
+- The target O-DU sends UL RRC MESSAGE TRANSFER message to O-CU to convey the received RRCReconfigurationComplete message.
+
+- The downlink and uplink data packets are sent to/from the UE through the target O-DU.
+
+- The O-CU sends UE CONTEXT RELEASE COMMAND message to the source O-DU.
+
+- The source O-DU sends UE DELETE REQUEST to MAC/RLC layers to release the UE context and receives UE DELETE RESPONSE message.
+
+- The source O-DU responds to O-CU with UE CONTEXT RELEASE COMPLETE message.
+
+
OSC Testcases Supported
=========================
Release-Notes
**************
-
-This document provides the release notes for D Release of O-DU-L2.
+This document provides the release notes for F Release of O-DU-L2.
.. contents::
:depth: 3
| **Date** | **Ver.** | **Author** | **Comment** |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
+|2022-06-16 | 6.0.0 | Radisys, | F release |
+| | | HCL Technologies | |
+| | | Ltd. | |
++--------------------+--------------------+--------------------+--------------------+
| 2022-01-14 | 5.0.0 | Radisys, | e-release |
| | | HCL Technologies | |
| | | Ltd. | |
^^^^^^^^^^
This release contains the following:
- - Upgrade to E2AP version 2.0.
- - Support for IDLE Mode Paging.
+ - HARQ framework support and scheduler enhancement to prioritize retransmission
+
+ - Upgrade to E2AP version 2.0
+
+ - Support for IDLE Mode Paging
+
+ - Mobility mode Support (Intra-CU handover)
+
- O1 Module
Release Data
------------
+F release
+^^^^^^^^^^
++--------------------------------------+--------------------------------------+
+| **Project** | ODUHIGH |
+| | |
++--------------------------------------+--------------------------------------+
+| **Repo/commit-ID** |o-du/l2/ |
+| |I2eeed74163fe985e6421ea563c5170f8cf81 |
+| |7e6d |
++--------------------------------------+--------------------------------------+
+| **Release designation** | F release |
+| | |
++--------------------------------------+--------------------------------------+
+| **Release date** |2022-06-16 |
+| | |
++--------------------------------------+--------------------------------------+
+| **Purpose of the delivery** | F release |
+| | |
++--------------------------------------+--------------------------------------+
e-release
^^^^^^^^^^
| **JIRA REFERENCE** | **SLOGAN** |
| | |
+-----------------------------------------------+-----------------------------------------------+
+| https://jira.o-ran-sc.org/browse/ODUHIGH-402 | Support for HARQ and scheduler enhancement to |
+| | prioritize retransmission |
++-----------------------------------------------+-----------------------------------------------+
| https://jira.o-ran-sc.org/browse/ODUHIGH-404 | Support for E2AP version 2.0 |
| | |
+-----------------------------------------------+-----------------------------------------------+
+| https://jira.o-ran-sc.org/browse/ODUHIGH-405 | Support for Inter-DU Handover |
+| | |
++-----------------------------------------------+-----------------------------------------------+
| https://jira.o-ran-sc.org/browse/ODUHIGH-406 | Support for Idle Mode Paging |
| | |
+-----------------------------------------------+-----------------------------------------------+
----------
1. ORAN-WG8.AAD.0-v05.00.00
-2. ORAN WG3.E2AP v02.00
+2. O-RAN.WG5.C.1-v05.00
+
+3. ORAN WG3.E2AP v02.00
-3. 3GPP 38.473-f60 v15.3
+4. 3GPP 38.473-f60 v15.3
-4. 3GPP TS 38.211 v15.3
+5. 3GPP TS 38.211 v15.3
-5. 3GPP TS 38.212 v15.3
+6. 3GPP TS 38.212 v15.3
-6. 3GPP TS 38.213 v15.3
+7. 3GPP TS 38.213 v15.3
-7. 3GPP TS 38.214 v15.3
+8. 3GPP TS 38.214 v15.3
-8. 3GPP TS 38.321 v15.3
+9. 3GPP TS 38.321 v15.3
-9. 3GPP TS 38.331 v15.3
+10. 3GPP TS 38.331 v15.3
-10. 5G PHY FAPI Specification v1.0.5
+11. 5G PHY FAPI Specification v1.0.5
-11. 3GPP TS 28.541 Specfication V16.6
+12. 3GPP TS 28.541 Specfication V16.6
-12. O-RAN WG1.O1-Interface v04.00
+13. O-RAN WG1.O1-Interface v04.00
-13. O-RAN WG1.OAM-Architecture v04.00
+14. O-RAN WG1.OAM-Architecture v04.00
User Guide
***********
-This is the user guide for e-release of O-DU/l2.
+This is the user guide for F release of O-DU/l2.
Follow installation-guide to get all the dependencies ready.
.. contents::
The call flow between O-DU High and CU Stub can be achieved by executing docker containers.
- Pull the last built docker images:
- - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:5.0.3
- - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:5.0.3
+ - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:6.0.1
+ - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:6.0.1
- Run CU Stub docker:
- docker run -it --privileged --net=host --entrypoint bash
- nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:5.0.3
+ nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:6.0.1
- ./cu_stub
- Run ODU docker:
- docker run -it --privileged --net=host --entrypoint bash
- nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:5.0.3
+ nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:6.0.1
- ./odu
---
distribution_type: container
-container_release_tag: 5.0.3
+container_release_tag: 6.0.1
container_pull_registry: nexus.o-ran-sc.org:10004
container_push_registry: nexus.o-ran-sc.org:10002
project: o-du-l2
-ref: 726a82abf1f485704459e2ce3777b8bac8cc16b6
+ref: eda4b205c3734bde66da2ec74427220890479920
containers:
- name: o-du-l2
-version: 5.0.3
+version: 6.0.1
---
distribution_type: container
-container_release_tag: 5.0.3
+container_release_tag: 6.0.1
container_pull_registry: nexus.o-ran-sc.org:10004
container_push_registry: nexus.o-ran-sc.org:10002
project: o-du-l2
-ref: 726a82abf1f485704459e2ce3777b8bac8cc16b6
+ref: eda4b205c3734bde66da2ec74427220890479920
containers:
- name: o-du-l2-cu-stub
-version: 5.0.3
+version: 6.0.1
Code Review / o-du / l2.git / commitdiff
