Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 13 Next »


Updated: 23 April 2020

Jira: EPICS  Status is mentioned below:

Risks:

  • E2SM Specification baseline is still not available while the development is being done using below draft specifications.
    • ORAN WG3.E2AP v01.00
    • ORAN WG3.E2SM v01.00
  • WLS, FAPI interface files baseline - FAPI interface development is dependent on this. 
  • UE Attach Scenario development - Completed till msg-2, remaining scope moved to C release as E2 changes were included in the scope.

Status:

Raised 18 change requests in WG8 AAD Specification; Already presented to the WG8 Task groups to be addressed in subsequent releases of the document.

O-DU High layers (MAC, RLC, and app):

  • Re-align seed code to 3GPP Release 15.3.0 - Done (completed for all the messages until msg-2)
  • Align seed code to WG8 AAD specification and interfaces - MAC - RLC Interface is done, RLC-F1AP interface is partially done (completed for all the data path messages)
  • Implementation of cell broadcast procedure and UE attach procedure (SA mode) 
    for FDD mode and FR1 (Numerology = 0, Bandwidth = 20 MHz) and basic scheduler APIs for single UE and single HARQ transmission
    • Cell Broadcast procedure - WIP
    • UE attach - WIP

F1-U interface development - Done

E2 Traffic Steering implementation based on draft specification - Done (with some limitations due to specifications)

F1-C interface enhancement:  Done (procedures identified for bronze released is done)

  • Support for following additional F1AP messages:
    • Initial UL RRC Message Transfer
    • UL/DL RRC Message Transfer
    • UE Context Setup Request/Response
  • Enhance F1AP messages:
    • F1AP Setup Request/Response
    • GNB DU Config Update

Basic FAPI messages Implementation - WIP (based on Intel FAPI 1.0.5 version)

Out of Scope:

  • Use cases – Traffic Steering, Health Check related messages and call flows
  • TDD functionality, NSA
  • End to end testing

Limitations/Dependencies:

  • FAPI Implementation – Dependency on O-DU Low to open source WLS files, interface files
  • Testing: Currently only some unit testing can be done due to lack of test infrastructure i.e UE or UE simulator, O-RU, O-CU, and core components.

===========

Updated: 10 April 2020

Risks:

  • E2SM Specification baseline is still not available while the development is being done using draft specifications
  • WLS, FAPI interface files baseline - FAPI interface development is dependent on this. 
  • UE Attach Scenario development - in medium risk due to the effort needed to complete the development

Status:

Raised 16 changes in WG8 AAD Specification; working with Ganesh to get them addressed in the next release of the document.

O-DU High layers (MAC, RLC, and app):

  • Re-align seed code to 3GPP Release 15.3.0 - WIP
  • Align seed code to WG8 AAD specification and interfaces - MAC - RLC Interface is done, RLC-F1AP interface is WIP
  • Implementation of cell broadcast procedure and UE attach procedure (SA mode) 
    for FDD mode and FR1 (Numerology = 0, Bandwidth = 20 MHz) and basic scheduler APIs for single UE and single HARQ transmission
    • Cell Broadcast procedure - WIP
    • UE attach - Open

F1-U interface development - Done

E2 Traffic Steering implementation based on draft specification - Done (with some limitations due to specifications)

F1-C interface enhancement:  Done (procedures identified for bronze released is done)

  • Support for following additional F1AP messages:
    • Initial UL RRC Message Transfer
    • UL/DL RRC Message Transfer
    • UE Context Setup Request/Response
  • Enhance F1AP messages:
    • F1AP Setup Request/Response
    • GNB DU Config Update

Basic FAPI messages Implementation - Open

Out of Scope:

  • Use cases – Traffic Steering, Health Check related messages and call flows
  • TDD functionality, NSA
  • End to end testing

Limitations/Dependencies:

  • FAPI Implementation – Dependency on O-DU Low to open source WLS files, interface files
  • Testing: Currently only some unit testing can be done due to lack of test infrastructure i.e UE or UE simulator, O-RU, O-CU, and core components.



======

Updated: 26 March 2020

Risks:

  • E2SM Specification baseline is still not available while the development is being done using draft specifications
  • WLS, FAPI interface files baseline - FAPI interface development is dependent on this
  • UE Attach Scenario development - in medium risk due to the effort needed to complete the development

Status:

O-DU High layers (MAC, RLC, and app):

  • Re-align seed code to 3GPP Release 15.3.0
  • Align seed code to WG8 AAD specification and interfaces - WIP
  • Implementation of cell broadcast procedure and UE attach procedure (SA mode)
    for FDD mode and FR1 (Numerology = 0, Bandwidth = 20 MHz) and basic scheduler APIs for single UE and single HARQ transmission

F1-U interface development - WIP

E2 Traffic Steering implementation based on draft specification - WIP

F1-C interface enhancement:  Done

  • Support for following additional F1AP messages:
    • Initial UL RRC Message Transfer
    • UL/DL RRC Message Transfer
    • UE Context Setup Request/Response
  • Enhance F1AP messages:
    • F1AP Setup Request/Response
    • GNB DU Config Update

Basic FAPI messages Implementation - Open

Out of Scope:

  • Use cases – Traffic Steering, Health Check related messages and call flows
  • TDD functionality, NSA
  • End to end testing

Limitations/Dependencies:

  • FAPI Implementation – Dependency on O-DU Low to open source WLS files, interface files
  • Testing: Currently only some unit testing can be done due to lack of test infrastructure i.e UE or UE simulator, O-RU, O-CU, and core components.
  • No labels