H release documentation

[Task-ID: ODUHIGH-515]

Change-Id: I790792e199edecd7932fb7dc89c167b231708a5f
Signed-off-by: lal.harshita <Harshita.Lal@radisys.com>

diff --git a/container-tag.yaml b/container-tag.yaml
index 3b270aa..a4ae307 100644 (file)
--- a/container-tag.yaml
+++ b/container-tag.yaml
@@ -1,4 +1,4 @@
 # The Jenkins job requires a tag to build the Docker image.
 # Global-JJB script assumes this file is in the repo root.
 ---
-tag: 7.0.4
+tag: 8.0.1

diff --git a/docs/5G_NR_SCH_Design.PNG b/docs/5G_NR_SCH_Design.PNG
new file mode 100644 (file)
index 0000000..da533c7
Binary files /dev/null and b/docs/5G_NR_SCH_Design.PNG differ

diff --git a/docs/Multi_Scheduling_Algorithm_Call_Flow.PNG b/docs/Multi_Scheduling_Algorithm_Call_Flow.PNG
new file mode 100644 (file)
index 0000000..dcdcff4
Binary files /dev/null and b/docs/Multi_Scheduling_Algorithm_Call_Flow.PNG differ

diff --git a/docs/Xn_Based_Inter_CU_Handover.png b/docs/Xn_Based_Inter_CU_Handover.png
new file mode 100644 (file)
index 0000000..2752a6e
Binary files /dev/null and b/docs/Xn_Based_Inter_CU_Handover.png differ

diff --git a/docs/api-docs.rst b/docs/api-docs.rst
index 9cbbff6..c5b6500 100644 (file)
--- a/docs/api-docs.rst
+++ b/docs/api-docs.rst
@@ -6,7 +6,7 @@
 API-Docs
 **********
 
-This is the API-docs for G release o-du/l2.
+This is the API-docs for H release o-du/l2.
 
 .. contents::
    :depth: 3
@@ -15,243 +15,199 @@ This is the API-docs for G release o-du/l2.
 
 Introduction
 -----------------
-This document lists the APIs implemented between various modules of ODU-High and their functionality.
-These are in line with ORAN-WG8.AAD-v5.00.00, hereafter referred to as AAD Spec.
+This document tabulates the APIs Aligned(Implemented)/Not Implemented/Additional APIs between various modules of 
+ODU-High and their functionality.
+These are in line with ORAN-WG8.AAD-v7.00.00, hereafter referred to as AAD Spec.
 
 Note: DU APP module consist functionality related to F1 Handler and O1 Handler
 
-API Functions
--------------
-1. RLC-MAC Interface
+API Table
+-----------
++------------+-------------------------------+-----------------+-----------+-----------------------------------------+
+| Interface  |    API                        | Status          | Section   | Remark                                  |
++============+===============================+=================+===========+=========================================+
+|            |Cell Configuration             | Aligned         |11.2.1.1   |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice Configuration            | Aligned         |11.2.1.2   |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Bring Cell Up                  | Additional API  |           |Notify DU to bring specific cell up      |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|**SMO-OAM** |Bring Cell Down                | Additional API  |           |Notify DU to bring specific cell down    |
+|& **DU APP**+-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice PM                       | Additional API  |           |DU APP sends PM for all Slices every 60s |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Raise Cell Alarm               | Additional API  |           |DU APP alarms during cell state change   |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Set the cell operational state | Additional API  |           |DU APP inform cell state[ACTIVE/INACTIVE]|
++------------+-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL Transfer                    | Aligned         |11.2.3.1   |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL Transfer                    | Aligned         |11.2.3.2   |                                         |
+| **RLC**    +-------------------------------+-----------------+-----------+-----------------------------------------+
+| & **MAC**  |Schedule Result Reporting(DL)  | Aligned         |11.2.3.3   |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Buffer Status Report(UL)       | Aligned         |11.2.3.4   |                                         |
++------------+-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Air Interface Time             | Aligned         |11.2.4.1.1 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Configuration Request     | Aligned         |11.2.4.2.1 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Delete Request            | Aligned         |11.2.4.2.2 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice Configuration Request    | Aligned         |11.2.4.2.3 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice Reconfiguration Request  | Aligned         |11.2.4.2.4 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Add UE Configuration Request   | Aligned         |11.2.4.2.5 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Reconfiguration Request     | Aligned         |11.2.4.2.6 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Delete UE Request              | Aligned         |11.2.4.2.7 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL HARQ Indication             | Aligned         |11.2.4.2.8 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL Harq Indication(CRC)        | Aligned         |11.2.4.2.9 |                                         |
+| **MAC** to +-------------------------------+-----------------+-----------+-----------------------------------------+
+|  **SCH**   |UL Channel Quality Information | Not Implemented |11.2.4.2.10|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL Channel Quality Information | Not Impelemented|11.2.4.2.11|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RACH Indication Contents       | Aligned         |11.2.4.2.12|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Paging Indication Contents     | Aligned         |11.2.4.2.13|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RACH Resource Request          | Aligned         |11.2.4.2.14|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RACH Resource Release          | Aligned         |11.2.4.2.15|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL RLC Buffer Status Info      | Aligned         |11.2.4.2.16|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Scheduling Request Indication  | Aligned         |11.2.4.2.17|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL Buffer Status Report Ind    | Aligned         |11.2.4.2.18|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Power Headroom Indication      | Aligned         |11.2.4.2.19|                                         |
++------------+-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Configuration Response    | Aligned         |11.2.4.3.1 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Delete Response           | Aligned         |11.2.4.3.2 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice Configuration Response   | Aligned         |11.2.4.3.3 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice ReConfiguration Response | Aligned         |11.2.4.3.4 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Configuration Response      | Aligned         |11.2.4.3.5 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE ReConfiguration Response    | Aligned         |11.2.4.3.6 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Delete Response             | Aligned         |11.2.4.3.7 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+| **SCH** to |DL Scheduling Information      | Aligned         |11.2.4.3.8 |                                         |
+|    **MAC** +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL Scheduling Information      | Aligned         |11.2.4.3.9 |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RAR Information                | Not Required    |11.2.4.3.10|Included in DL Scheduling Info           |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Downlink Control Channel Info  | Not Required    |11.2.4.3.11|Included in DL Scheduling Info           |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Downlink Broadcast Allocation  | Not Required    |11.2.4.3.12|Included in DL Scheduling Info           |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Downlink Paging Allocation     | Aligned         |11.2.4.3.13|                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |HARQ Process Release           | Additional API  |           |SCH indicates MAC to release a HARQ      |
+|            |                               |                 |           |process in case a positive acknowledement|
+|            |                               |                 |           |is received or achieved maximum retrans. |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RACH Resource Response         | Additional API  |           |Response to RACH Resource Request for    |
+|            |                               |                 |           |dedicated resource for CF-RA             |
++------------+-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Start                     | Aligned         |1.1.1.1    |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Stop                      | Aligned         |1.1.1.2    |                                         |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Configuration Request     | Additional API  |           |Configures cell information at MAC.      | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Configuration Response    | Additional API  |           |Response to cell Cfg Req from DUAPP      |    
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Delete Request            | Additional API  |           |Deletes cell information at MAC.         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Cell Delete Response           | Additional API  |           |Response to Cell Del request from DU APP | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice Configuration Request    | Additional API  |           |Configures Slice at MAC                  | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice ReConfiguration Request  | Additional API  |           |ReConfigures Slice at MAC                | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice Configuration Response   | Additional API  |           |Response to Slice Cfg req from DU APP    |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice ReConfiguration Response | Additional API  |           |Response to Slice ReCfg req from DU APP  |
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|**DU APP**  |UE Create Request              | Aligned         |1.1.1.3    |                                         | 
+| & **MAC**  +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Create Response             | Aligned         |1.1.1.4    |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Reconfiguration Request     | Aligned         |1.1.1.5    |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Reconfiguration Response    | Aligned         |1.1.1.6    |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Delete Request              | Aligned         |1.1.1.7    |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Delete Response             | Aligned         |1.1.1.8    |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RACH Resource Request          | Aligned         |1.1.1.9    |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RACH Resource Response         | Aligned         |1.1.1.10   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RACH Resource Release          | Aligned         |1.1.1.11   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Reset Request               | Not Implemented |1.1.1.12   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Reset Response              | Not Implemented |1.1.1.13   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Sync Status Indication      | Not Implemented |1.1.1.14   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL CCCH Indication             | Aligned         |1.1.1.15   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL CCCH Indication             | Aligned         |1.1.1.16   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL PCCH Indication             | Aligned         |1.1.1.17   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL Broadcast Request           | Not Implemented |1.1.1.18   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slot Indication                | Additional API  |           |Indication about the ongoing SFN and     |
+|            |                               |                 |           | Slot information to DU APP              | 
++------------+-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Create                      | Aligned         |11.2.5.1   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Create Response             | Aligned         |11.2.5.2   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Reconfiguration             | Aligned         |11.2.5.3   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Reconfiguration Response    | Aligned         |11.2.5.4   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Delete                      | Aligned         |11.2.5.5   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UE Delete Response             | Aligned         |11.2.5.6   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL-RRC Message Transfer        | Aligned         |11.2.5.7   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL-RRC Message Transfer        | Aligned         |11.2.5.8   |                                         | 
+|**DU APP**  +-------------------------------+-----------------+-----------+-----------------------------------------+
+|  & **RLC** |UL-RRC Message Delivery Report | Aligned         |11.2.5.9   |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |RLC Max Retransmission Reached | Not Implemented |11.2.5.10  |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL-RLC Re-establishment Request| Not Implemented |11.2.5.11  |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL-RLC Re-establshment Response| Not Implemented |11.2.5.12  |                                         | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL RRC Message Response        | Additional API  |           |Informs DU APP if a DL RRC Message was   |
+|            |                               |                 |           |successfuly procesed at RLC & sent to MAC| 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |DL User Data                   | Additional API  |           |DL user data exchanged from DUAPP to RLC | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |UL User Data                   | Additional API  |           |UL user data exchanged from RLC to DUAPP | 
+|            +-------------------------------+-----------------+-----------+-----------------------------------------+
+|            |Slice Performance Metrics      | Additional API  |           |Performance Metrics informed to DUAPP    |
+|            |                               |                 |           |every 60sec for every slice configured   | 
++------------+-------------------------------+-----------------+-----------+-----------------------------------------+
 
-   - AAD Spec : section 9.2.2
-
-   A. RLC to MAC
-   
-      a. Data Transfer(DL) : Transfers DL data to MAC as per Section 9.2.2.1 of the AAD Spec
-
-      b. Buffer Status Reporting(DL) : Reports DL data volume pending in the RLC entity, as per Section 9.2.2.4 of the
-         AAD Spec
-
-   B. MAC to RLC
-
-      a. Data Transfer(UL) : Transfers UL data to RLC as per Section 9.2.2.2 of the AAD Spec
-
-      b. Schedule Result Reporting (DL) : Reports DL schedule result to RLC as per Section 9.2.2.3 of the AAD Spec
-
-2. MAC-Scheduler Interface
-
-   - AAD Spec : section 9.2.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.
-
-      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.
-
-      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.
-
-      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.
-
-      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.
-
-      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.
-
-      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.
-
-      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.
-        
-      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.
-
-      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.
-
-      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.
-
-      q. Scheduling Request Indication : MAC indicates to scheduler through this API when UE has to be scheduled for uplink 
-         grant as per Spec 9.2.3.2.17 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.
-
-      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.
-    
-      d. UL Scheduling Information - Provides scheduled information for MAC to form the UL_TTI.request towards O-DU Low,
-         as per Section 9.2.3.3.9 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.
-
-      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 of the AAD Spec.
-
-      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.
-        
-      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.
-
-      m. Ue Configuration Response : Response to UE reconfiguration request from MAC, as per Section 9.2.3.3.5 of the AAD Spec.
-
-3. DU APP - MAC Interface
-
-   - AAD Spec : section 9.2.4
-
-   A. DU APP to MAC
-   
-      a. Cell Start - Commands MAC to start cell at L1 and to start broadcasting system information, as per Section
-         9.2.4.1 of the AAD Spec.
-
-      b. UE Create Request - Adds UE information at MAC as per Section 9.2.4.3 of the AAD Spec.
-
-      c. UE Reconfiguration Request - Reconfigure UE information for a UE already added at MAC, as per Section 9.2.4.5 of the AAD Spec.
-
-      d. DL CCCH Indication - Sends DL CCCH Message to MAC to be sent to UE, as per Section 9.2.4.16 of the AAD Spec.
-
-      e. Cell Stop - Commands MAC to stop cell at L1, as per Section 9.2.4.2 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.
-
-      b. UE Reconfiguration Response - Response to UE Reconfiguration Request from DU APP as per Section 9.2.4.6 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
-   
-   - AAD Spec : section 9.2.5
-
-   A. DU APP to RLC
-
-      a. UE Create - Adds UE associated RLC entity and related information as per Section 9.2.5.1 of the AAD Spec.
-
-      b. UE Reconfiguration - Reconfigures the UE associated RLC entity previously added at RLC, as per Section 9.2.5.3 of the AAD Spec.
-
-      c. DL RRC Message Transfer - Requests RLC to deliver RRC message from CU to the UE, as per Section 9.2.5.7 of the AAD Spec.
-
-      d. UE Delete Request - Deletes UE associated RLC entity and related information as per Section 9.2.5.5 of the  AAD Spec.
-
-   B. RLC to DU APP
-
-      a. UE Create Response - Response to UE Create Request from DU APP, as per Section 9.2.5.2 of the AAD Spec.
-
-      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 of the AAD Spec.
-
-5. SMO-OAM - DU APP
-
-   - AAD Spec: Section 9.2.1
-
-   A. SMO-OAM to DU APP
-
-      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 of the AAD Spec.
-
-Additional APIs
-----------------
-
-1. DU APP - MAC Interface
-
-   A. DU APP to MAC
-     
-      a. Cell Configuration Request - Configures cell information at MAC.
-
-      b. Cell Delete Request - Deletes cell information at MAC.
-      
-      c. Slice Configuration Request : Triggers Slice Configuration request once received from O1 towards MAC.
-        
-      d. Slice Reconfiguration Request : Triggers Slice Reconfiguration request once received from O1 towards MAC. 
-
-   B. MAC to DU APP
-
-      a. Cell Configuration Response - Response to Cell Configuration Request from DU APP
-
-      b. Cell Delete Response - Response to Cell Delet request from DU APP
-      
-      c. Slice Configuration Respone :  Response to Slice Configuration request from DU Manager.
-        
-      d. Slice Reconfiguration Request : Response to Slice Reconfiguration request from DU Manager.
-
-      e. Slot Indication : Indication about the ongoing SFN and Slot information to DU APP.
-
-2. DU APP - RLC Interface
-
-   A. RLC to DU APP
-
-      a. DL RRC Message Response - Informs DU APP if a DL RRC Message was successfuly processed at RLC and sent to MAC.
-
-      b. Slice Performance Metrics - Sends PM to DU APP every 60sec for every Slice configured.
-
-
-3. DU APP - SMO-OAM
-
-   a. Bring cell up - Informs DU to bring a specific cell up
-
-   b. Bring cell down - Informs DU to bring specific cell up
-
-   c. Set the cell operational state - Sets the cell state to ACTIVE/INACTIVE
-
-   d. Raise a cell alarm - Raise an alarm when the cell is ACTIVE/INACTIVE
-
-   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.

diff --git a/docs/developer-guide.rst b/docs/developer-guide.rst
index 2340191..5507841 100644 (file)
--- a/docs/developer-guide.rst
+++ b/docs/developer-guide.rst
@@ -26,9 +26,9 @@ O-DU High uses C languages. The coding guidelines followed are:
 
 .. figure:: LicHeader.jpg
   :width: 600
-  :alt: Figure 16 License Header and Footer
+  :alt: Figure 17 License Header and Footer
 
-  Figure 16 : License Header and Footer
+  Figure 17 : License Header and Footer
 
 O-DU High code
 ---------------
@@ -280,9 +280,9 @@ Here,
 
 .. figure:: ModeofCommunication.jpg
    :width: 600
-   :alt: Figure 17 Mode of communication between O-DU High entities
+   :alt: Figure 18 Mode of communication between O-DU High entities
 
-   Figure 17: Mode of communication between O-DU High entities
+   Figure 18: Mode of communication between O-DU High entities
 
 Steps of Communication
 ++++++++++++++++++++++
@@ -344,9 +344,9 @@ Below figure summarized the above steps of intra O-DU High communication
 
 .. figure:: StepsOfCommunication.jpg
    :width: 600
-   :alt: Figure 18 Communication between entities
+   :alt: Figure 19 Communication between entities
 
-   Figure 18: Steps of Communication between O-DU High entities
+   Figure 19: Steps of Communication between O-DU High entities
 
 
 Communication with Intel O-DU Low
@@ -601,6 +601,39 @@ the following APIs for communication.
        b. Input - handle of WLS interface
        c. Returns number of available blocks in slave to master queue
 
+Scheduler Framework with plug-in support
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+5G NR SCH module is encapsulated within 5G NR MAC of ODU-High. Any communication to/from SCH will happen only through MAC.
+The scheduler framework in ODU-High provides support to plug-in multiple scheduling algorithms easily.
+
+Design
++++++++
+
+.. figure:: 5G_NR_SCH_Design.PNG
+   :width: 600
+   :alt: 5G NR Scheduler Framework Design
+   
+   Figure 20: 5G NR Scheduler Framework Design
+
+- The code for scheduler has been divided into 2 parts i.e. the common APIs and scheduler-specific APIs. 
+- Any code (structure/API) which is specific to a scheduling algorithm must be within scheduler-specific files such as sch_rr.c and sch_rr.h for round-roubin scheduler.
+- Function pointers are used to identify and call APIs belonging to the scheduling algorithm in use at any given point in time. 
+- All supported scheduling algorithm are listed in SchType enum in sch.h file.
+- All function pointers are declared in SchAllApis structure in sch.h 
+- For each scheduling algorithm, function pointers must be initialised to scheduler-specific APIs during scheduler initialisation. 
+
+Call Flow
++++++++++
+
+- In any call flow, a common API calls the scheduler-specific API using function pointer and its output is returned back to the common API, which will be further processed and communicated to MAC.
+
+.. figure:: Multi_Scheduling_Algorithm_Call_Flow.PNG
+   :width: 600
+   :alt: Call flow example of Multi-Scheduling Algorithm framework
+
+   Figure 21: Example of a call flow in multi-scheduling algorithm framework
+
 Additional Utility Functions
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 

diff --git a/docs/installation-guide.rst b/docs/installation-guide.rst
index 0d87235..0ac3714 100644 (file)
--- a/docs/installation-guide.rst
+++ b/docs/installation-guide.rst
@@ -18,6 +18,9 @@ Version history
 | **Date**           | **Ver.**           | **Author**         | **Comment**        |
 |                    |                    |                    |                    |
 +--------------------+--------------------+--------------------+--------------------+
+| 2023-06-13         |  6.0.1             |  Radisys           |  H release         |
+|                    |                    |                    |                    |
++--------------------+--------------------+--------------------+--------------------+
 | 2022-12-15         |  5.0.1             |  Radisys,          |  G release         |
 |                    |                    |  HCL Technologies  |                    |
 |                    |                    |  Ltd.              |                    |

diff --git a/docs/overview.rst b/docs/overview.rst
index 54dae01..eb28463 100644 (file)
--- a/docs/overview.rst
+++ b/docs/overview.rst
@@ -94,13 +94,15 @@ on the various logical channels.
 Functions of the 5G NR MAC module are as follows:
 
 - 5G NR MAC is responsible for multiplexing and de-multiplexing of the data on various logical channels.
-
-- 5G NR SCH schedules resources in UL and DL for cell and UE based procedures.
-  5G NR SCH is completely encapsulated within the 5G NR MAC i.e., all interactions of the 5G NR SCH is via the 5G NR MAC.
-
 - Lower MAC interfaces between the MAC and the O-DU Low. It implements all the messages of FAPI
   specification. It has a receiver thread to handle messages from L1.
 
+5G NR SCH
+**********
+
+- This module is completely encapuslated withing 5G NR MAC i.e. all interactions of the 5G NR SCH is via the 5G NR MAC.
+- Schedules resources in UL and DL for cell and UE based procedures.
+- SCH framework design supports plugging-in new scheduling algorithm easily. Refer to section "Scheduler Framework with plug-in support" in Developer-Guide document for details.
 
 O-DU Utility and Common Functions
 *********************************
@@ -109,7 +111,7 @@ These modules contain platform specific files and support O-DU High functionalit
 
 
 O1 Module
-==========
+*********
 
 .. figure:: ODU-O1-Arch.jpg
   :width: 554
@@ -188,6 +190,8 @@ As shown in Figure 3, O-DU High interfaces with the following modules:
     - E2 Setup
 
     - E2 Node Configuration Update 
+    
+    - E2 Reset
 
   - Near RT RIC Functional Procedures
                
@@ -316,16 +320,22 @@ The above channels are used to achieve the below messages:
 
   - Registraton Request
 
-  - Security Mode Command
+  - NAS Authentication Request
+
+  - NAS Authentication Response
+
+  - NAS Security Mode Command
 
-  - Security Mode Complete
+  - NAS Security Mode Complete
+
+  - RRC Security Mode Command
+
+  - RRC Security Mode Complete
 
   - Registraton Accept
 
   - Registraton Complete
 
-  - Several NAS Message Exchanges
-
   - RRC Reconfiguration
 
   - RRC Reconfiguration Complete
@@ -492,6 +502,73 @@ Assumption: UE is RRC connected with DU and PDU data session is active.
 
 - The source O-DU responds to O-CU with UE CONTEXT RELEASE COMPLETE message.
 
+==============================
+Inter-CU Handover (Xn-Based)
+==============================
+
+This section describes the handling of inter-CU handover of a UE over Xn interface.
+
+.. figure:: Xn_Based_Inter_CU_Handover.png
+   :width: 600
+   :alt: Xn-Based Inter-CU Handover
+ 
+   Figure 11 -  Xn-Based Inter-CU Handover call flow
+
+Terminology:
+
+- Source GNB : GNB to which UE is connected and will be handed over from .
+- Source GNB DU : O-DU in source GNB
+- Source GNB CU : O-CU in source GNB
+- Target GNB : GNB to which UE will be handed over to.
+- Target GNB DU : O-DU in target GNB
+- Target GNB CU : O-CU in target GNB
+- Xn Inteface : Interface between Source GNB CU and Target GNB CU
+- UE : UE in handover from source GNB to target GNB
+
+Assumptions: 
+
+- Xn setup is established between the two GNB 
+- UE is RRC connected with DU 
+- PDU data session is active.
+
+Call Flow :
+
+- UE sends Measurement Report message to source GNB. 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 handover decision to a cell belonging to another GNB. Hereafter, this GNB will be referred to as target GNB.
+
+- Before initiating the handover procedure, source GNB CU sends a UE CONTEXT MODIFICATION REQUEST message to source GNB DU to query the latest configurations.
+
+- The source GNB DU responds with UE CONTEXT MODIFICATION RESPONSE message that includes latest full configuration information.
+
+- To start the handover, source GNB CU sends HANDOVER REQUEST to target GNB CU with UE configuration received from source GNB DU.
+
+- Target GNB CU sends a UE CONTEXT SETUP REQUEST message to target GNB DU to create a UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message includes Hand-overPreparationInformation. At 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 GNB DU responds with UE CONTEXT SETUP RESPONSE message if it can admit resources for the handover.
+
+- Consequetively, target GNB CU sends HANDOVER REQUEST ACKNOWLEDGE message to source GNB CU to proceed with handover.
+
+- Now source GNB CU sends UE CONTEXT MODIFICATION REQUEST message to source GNB DU, which includes RRCReconfiguration message towards the UE. The CU also indicates the DU to stop the data transmission for the UE.
+
+- Source GNB DU forwards received RRCReconfiguration message to the UE and then sends DOWNLINK DATA DELIVERY STATUS message to CU to inform about successful delivery of message to UE.
+
+- Source GNB DU also sends UE Reconfiguration Request to MAC/Scheduler and RLC layers to stop data scheduling as requested by CU. Once all layers have responded with UE reconfiguration response, source GNB DU send UE CONTEXT MODIFICATION RESPONSE message to source GNB CU.
+
+- Using the information received in RRC Reconfiguration message, UE triggers Random Access procedure towards target GNB DU. This is a contention free random access if UE receives dedicated RACH resources information in RRC Reconfiguration message.
+
+- Once Random Access procedure with target GNB is complete, UE responds to target GNB DU with a RRCReconfigurationComplete message.
+
+- The target GNB DU sends UL RRC MESSAGE TRANSFER message to CU to convey the received RRCReconfigurationComplete message. This completes the UE attach to target GNB.
+
+- The downlink and uplink data packets are now sent to/from the UE through target GNB.
+
+- Once UE is successfully handed over to target GNB, its CU sends UE CONTEXT RELEASE message to source GNB CU.
+
+- Hence, source GNB CU sends UE CONTEXT RELEASE COMMAND message to the source GNB DU. 
+
+- DU releases UE context at all layers and responds to source GNB CU with UE CONTEXT RELEASE COMPLETE message.
+
 =============================
 Discontinuous reception (DRX)
 =============================
@@ -503,7 +580,7 @@ This section describes the Discontinuous reception (DRX) feature within O-DU Hig
   :width: 600
   :alt: Discontinuous reception flow
 
-  Figure 11 -  Discontinuous reception flow
+  Figure 12 -  Discontinuous reception flow
 
 - The connected mode DRX is used to improve UE's battery power consumption. This allows UE to be active for a certain amount of time to monitor PDCCH. UE shall become active or inactive based on the DRX timers. 
 
@@ -523,7 +600,7 @@ This section describes the Discontinuous reception (DRX) feature within O-DU Hig
   :width: 600
   :alt: onDurationTimer,InactivityTimer,ShortCycleTimer flow
 
-  Figure 12 -  onDurationTimer,InactivityTimer,ShortCycleTimer flow
+  Figure 13 -  onDurationTimer,InactivityTimer,ShortCycleTimer flow
 
 - If HARQ is received/sent, drx-HARQ-RTT-TimerDL or drx-HARQ-RTT-TimerUL is started. On its expiry drx-RetransmissionTimerDL or drx-RetransmissionTimerUL will start. While it is running, UE becomes active for retransmission of data in DL/UL. Refer to figure 13 and 14 below for detailed working of these timers.
 
@@ -531,13 +608,13 @@ This section describes the Discontinuous reception (DRX) feature within O-DU Hig
   :width: 600
   :alt: HARQ-RTT-TimerDL, RetransmissionTimerDL flow
 
-  Figure 13 - DL Harq Retransmission Timers flow
+  Figure 14 - DL Harq Retransmission Timers flow
 
 .. figure:: Drx_Ul_Harq_Retransmission_Timer.png
   :width: 600
   :alt: HARQ-RTT-TimerUL, RetransmissionTimerUL flow
 
-  Figure 14 - UL Harq Retransmission Timers flow
+  Figure 15 - UL Harq Retransmission Timers flow
 
 - If O-DU receives DRX configuration release indicator IE as a part of UE CONTEXT MODIFICATION REQUEST from O-CU, DU APP will forward this indicator to MAC which forwards it to SCH as part of UE reconfiguration request. In this case SCH stops all DRX timers, deletes DRX configuration and marks UE as active by default. 
 

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 59a3efe..7add7e7 100644 (file)
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -5,7 +5,7 @@
 Release-Notes
 **************
 
-This document provides the release notes for F Release of O-DU-L2.
+This document provides the release notes for H Release of O-DU-L2.
 
 .. contents::
    :depth: 3
@@ -19,11 +19,14 @@ Version history
 | **Date**           | **Ver.**           | **Author**         | **Comment**        |
 |                    |                    |                    |                    |
 +--------------------+--------------------+--------------------+--------------------+
-|2022-12-15          | 7.0.3              | Radisys,           | G release          |
+| 2023-05-15         | 8.0.0              | Radisys            | H release          |
+|                    |                    |                    |                    |
++--------------------+--------------------+--------------------+--------------------+
+| 2022-12-15         | 7.0.3              | Radisys,           | G release          |
 |                    |                    | HCL Technologies   |                    |
 |                    |                    | Ltd.               |                    |
 +--------------------+--------------------+--------------------+--------------------+
-|2022-06-16          | 6.0.0              | Radisys,           | F release          |
+| 2022-06-16         | 6.0.0              | Radisys,           | F release          |
 |                    |                    | HCL Technologies   |                    |
 |                    |                    | Ltd.               |                    |
 +--------------------+--------------------+--------------------+--------------------+
@@ -50,6 +53,25 @@ Version history
 Summary
 -------
 
+H- release
+^^^^^^^^^^
+This release contains the following:
+
+ - Multi-Scheduling algorithm framework design
+
+ - Alignment to "O-RAN WG8 AAD v07.00" Specification
+
+ - Mobility mode Support (Inter-CU handover)
+ 
+ - Upgrade to E2AP v3.0 and implementation of E2 messages
+   
+   - E2 Setup failure
+   - Reset Procedure
+
+ - End-to-end integration support
+
+   - Testing with TM500 UE simulator to detect broadcast message
+
 G- release
 ^^^^^^^^^^
 This release contains the following:
@@ -193,19 +215,38 @@ This release contains the following:
 
 Release Data
 ------------
+H release
+^^^^^^^^^^
++--------------------------------------+------------------------------------------+
+| **Project**                          | ODUHIGH                                  |
+|                                      |                                          |   
++--------------------------------------+------------------------------------------+
+| **Repo/commit-ID**                   | o-du/l2/                                 |
+|                                      | I790792e199edecd7932fb7dc89c167b231708a5f|
++--------------------------------------+------------------------------------------+
+| **Release designation**              | H release                                |
+|                                      |                                          |   
++--------------------------------------+------------------------------------------+
+| **Release date**                     | 2023-06-13                               |
+|                                      |                                          |   
++--------------------------------------+------------------------------------------+
+| **Purpose of the delivery**          | H release                                |
+|                                      |                                          |   
++--------------------------------------+------------------------------------------+
+
 G release
 ^^^^^^^^^^
 +--------------------------------------+------------------------------------------+
 | **Project**                          | ODUHIGH                                  |
 |                                      |                                          |   
 +--------------------------------------+------------------------------------------+
-| **Repo/commit-ID**                   |o-du/l2/                                  |
-|                                      |I18c6f314f9a927ae49db92e4f9b0e4a3113f3bdb |
+| **Repo/commit-ID**                   | o-du/l2/                                 |
+|                                      | I18c6f314f9a927ae49db92e4f9b0e4a3113f3bdb|
 +--------------------------------------+------------------------------------------+
 | **Release designation**              | G release                                |
 |                                      |                                          |   
 +--------------------------------------+------------------------------------------+
-| **Release date**                     |2022-12-05                                |
+| **Release date**                     | 2022-12-05                               |
 |                                      |                                          |   
 +--------------------------------------+------------------------------------------+
 | **Purpose of the delivery**          | G release                                |
@@ -218,15 +259,15 @@ F release
 | **Project**                          | ODUHIGH                              |
 |                                      |                                      |   
 +--------------------------------------+--------------------------------------+
-| **Repo/commit-ID**                   |o-du/l2/                              |
-|                                      |Ice63cef7030a5c08820bcced7ea06467e2c88|
-|                                      |20b                                   |
+| **Repo/commit-ID**                   | o-du/l2/                             |
+|                                      | Ice63cef7030a5c08820bcced7ea06467e2c8|
+|                                      | 820b                                 |
 |                                      |                                      |
 +--------------------------------------+--------------------------------------+
 | **Release designation**              | F release                            |
 |                                      |                                      |   
 +--------------------------------------+--------------------------------------+
-| **Release date**                     |2022-06-16                            |
+| **Release date**                     | 2022-06-16                           |
 |                                      |                                      |   
 +--------------------------------------+--------------------------------------+
 | **Purpose of the delivery**          | F release                            |
@@ -343,6 +384,27 @@ Feature Additions
 
 **JIRA BACK-LOG:**
 
+H-release
+^^^^^^^^^^
+
++-----------------------------------------------+-----------------------------------------------+
+| **JIRA REFERENCE**                            | **SLOGAN**                                    |
+|                                               |                                               |
++-----------------------------------------------+-----------------------------------------------+
+| https://jira.o-ran-sc.org/browse/ODUHIGH-463  | Inter-CU Handover                             |
+|                                               |                                               |
++-----------------------------------------------+-----------------------------------------------+
+| https://jira.o-ran-sc.org/browse/ODUHIGH-488  | Alignment to ORAN WG8 AAD v7.0 specification  |
+|                                               | and Enhancement for Multi-scheduling alogrithm|
+|                                               | framework                                     |
++-----------------------------------------------+-----------------------------------------------+
+| https://jira.o-ran-sc.org/browse/ODUHIGH-510  | E2 upgrade to v3.0 and enhancement            |
+|                                               |                                               |
++-----------------------------------------------+-----------------------------------------------+
+| https://jira.o-ran-sc.org/browse/ODUHIGH-475  | Integration of ODU-High with L1               |
+|                                               |                                               |
++-----------------------------------------------+-----------------------------------------------+
+
 G-release
 ^^^^^^^^^^
 
@@ -573,7 +635,7 @@ System Limitations
 
 - Current code is locally tested to support upto three UEs.
 
-- NR-MAC supports Round Robin scheduling currently.
+- NR-MAC supports Round Robin scheduling currently, however the framework provides support to plug-in any other scheduling algorthim easily.
 
 - Cell broadcast is for SSB and SIB1 only.
 
@@ -630,11 +692,11 @@ O-DU High uses FAPI interface files provided by Intel and therefore, not complet
 
 References
 ----------
-1. ORAN-WG8.AAD.0-v05.00.00
+1. ORAN-WG8.AAD.0-v07.00.00
 
 2. O-RAN.WG5.C.1-v05.00
 
-3. ORAN WG3.E2AP v02.00
+3. ORAN WG3.E2AP v03.00
 
 4. 3GPP 38.473-f60 v15.3
 

diff --git a/docs/user-guide.rst b/docs/user-guide.rst
index 167417d..c532eec 100644 (file)
--- a/docs/user-guide.rst
+++ b/docs/user-guide.rst
@@ -4,7 +4,7 @@
 User Guide
 ***********
 
-This is the user guide for G release of O-DU/l2.
+This is the user guide for H release of O-DU/l2.
 Follow installation-guide to get all the dependencies ready.
 
 .. contents::
@@ -66,17 +66,17 @@ II. Execution - Using Docker Images
 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:7.0.4
-    -  docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:7.0.4
+    -  docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:8.0.1
+    -  docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:
 
 - 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:7.0.4
+      nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:8.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:7.0.4
+      nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:8.0.1
     - ./odu
 
 
@@ -84,7 +84,7 @@ B. Pairwise testing with Intel O-DU Low:
 -----------------------------------------
 
 This section describes the changes required in compilation and execution of O-DU High binaries to successfully integrate
-with Intel O-DU Low in timer mode.
+with Intel O-DU Low in radio mode.
 
 
 I. Pre-requisites
@@ -197,9 +197,9 @@ Following diagram shows P5 messages exchanged with O-DU Low in timer mode.
 
 .. figure:: O-DU_High_Low_Flow.PNG
   :width: 600
-  :alt: Figure 15 O-DU High - O-DU Low Message Flow Diagram
+  :alt: Figure 16 O-DU High - O-DU Low Message Flow Diagram
 
-  Figure 15 - O-DU High - O-DU Low Message Flow Diagram
+  Figure 16 - O-DU High - O-DU Low Message Flow Diagram
 
 Note: UL IQ-Sample request and response are needed by Intel O-DU Low in timer mode(testing mode) only. Code changes for
 these are guarded under INTEL_TIMER_MODE flag which can be enabled using compilation option "PHY_MODE=TIMER", as

diff --git a/releases/container-release-o-du-l2 b/releases/container-release-o-du-l2
index cd40a6a..334e6e4 100644 (file)
--- a/releases/container-release-o-du-l2
+++ b/releases/container-release-o-du-l2
@@ -1,11 +1,11 @@
 ---
 
 distribution_type: container
-container_release_tag: 7.0.4
+container_release_tag: 8.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: 835385c065ae59f6e62368c5c2cb452750422461
+ref: 2e1af025a72168244cc7d7697b069a26edd859e0
 containers:
 - name: o-du-l2
-version: 7.0.4
+version: 8.0.1

diff --git a/releases/container-release-o-du-l2-cu-stub b/releases/container-release-o-du-l2-cu-stub
index d4827da..dce1d7f 100644 (file)
--- a/releases/container-release-o-du-l2-cu-stub
+++ b/releases/container-release-o-du-l2-cu-stub
@@ -1,11 +1,11 @@
 ---
 
 distribution_type: container
-container_release_tag: 7.0.4
+container_release_tag: 8.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: 835385c065ae59f6e62368c5c2cb452750422461 
+ref: 2e1af025a72168244cc7d7697b069a26edd859e0 
 containers:
 - name: o-du-l2-cu-stub
-version: 7.0.4
+version: 8.0.1