E2E Test Framework 2.0 Gathering on OSC-RSAC Inputs and MVP Blueprints
This document discusses the gathering of OSC-RSAC inputs on MVP deployment blueprints and requirements for O-RAN Alliance, focusing on enabling deployments and developing critical functions for market needs. It outlines proposed agendas, candidate work items, and fits together various elements of the E2E test framework. Additionally, it covers the release approach discussions within TSC, aligning on major themes, details, phases, and timelines for O-RAN deployment blueprints.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
E2E Test Framework 2.0 Gathering OSC-RSAC inputs on MVP Blueprints and Requirements August 18, 2020 Test and Integration Focus Group (TIFG) Eng Wei Koo (VIAVI) Confidential 1
Proposed Agenda 1. TIFG to kick off this meeting share objectives on the MVP deployment blueprints and approach we are proposing to take 2. OSC RSAC team to share views and inputs on MVP deployment blueprints and requirements for O-RAN Alliance 3. Next steps deliverables and timelines Confidential 2
E2E Test Framework 2.0 Goal is to Enable Deployments Operators O-RAN Deployment Blueprints WHAT can be commercially deployable, WHEN? Listing a few major areas which TIFG members have raised i. NR TDD/FDD Open Fronthaul (OFH) ii. O-RAN MANO - O1 for <managed entity> 1..n, <managed entity example O-DU> iii. RIC-enabled use cases such as Traffic Steering, RAN Slicing etc. iv. Others (still in the process of gathering MVPs from operators) Confidential 3
E2E Test Framework 2.0 Candidates work items MVP: Minimum Viable Product includes critical functions required for market needs To be aligned with Operators and OSC RSAC team Developing a Single pane of Glass Focus of this session 1. O-RAN Deployment Blueprints Roadmap (time phased MVPs) Single Pane of Glass 2. Blueprints Subsystem Profiles Template definition andGlobal Operators inputs i. Industry Requirements (1, 2) What s needed 3. O-RAN TestTraceability matrix 4. O-RAN E2E test cases and use cases focused KPIs definition work ii. O-RAN Alliance support (3) What can be tested 5. Collaborate with WGs and assist with/provide inputs wrt developing testing methodologies/test cases iii. Acceleration required (4, 5) Accelerate test cases Confidential 4
E2E Test Framework 2.0 Fit together Blueprints Elements O-RAN Deployment Blueprints Roadmap (time phased MVPs) requires defining Vertical Slices which can be tested and deployed Traffic Steering O1 for O-RU, O- DU, O-CU SMO O-Cloud APIs and O2 for O-Cloud O-RU, O-DU, O- CU-CP/UP, RIC, SMO etc. Confidential 5
[In Discussions] Propose Release Approach Still in Discussions within TSC (WG1 & TIFG) - Needing to align on the Major Themes and Details of the Themes -> Phases and Timelines O-RAN Themes A + Y months A + X months A + Z months Traffic Steering Release 1 Traffic Steering O-RU, O-DU, O- CU-CP/UP, RIC, SMO etc. Vertical Slice(s) which can be tested and deployed Technical and Test Specifications SMO Additional items Confidential 6
[In Discussions] Enables Alignment and Traceability Still in Discussions within TSC (WG1 & TIFG) enabling alignment of plans across all impacted WGs/TGs/FGs to deliver Vertical Slice contents Traffic Steering Release 1 UCTG: Requirements which are testable OAM: Procedures and Protocols over O1 WG1 Specifications with architecture, design and protocols over A1 support Information and Service models over O1 WG2 Specifications with architecture, design and protocols over E2 support Information and Service models over O1 WG3 WG4/WG5/ WG8 Required Performance Measurements and Statistics Information and Service models over O1 (as required) Test Specifications from the respective WGs/TGs for Subsystem, Subsystem Pair IOT and E2E System Testing xWGs/xTGs Confidential 7
Next steps deliverables and timelines OSC RSAC team to share views and inputs on MVP deployment blueprints and requirements for O-RAN Alliance. Few of the specifics we are thinking of phased requirements for discussions and alignment purposes 1. Traffic Steering 2. SMO 3. Others? Confidential 8
References Confidential 9
Example from 3GPP - Releases and Themes 3GPP Releases and Themes are typically driven by Market Requirements And aligned with the 3GPP working groups for MVP contents [Source: 3GPP] [Source: 3GPP] Confidential 10
Example from 3GPP - Single feature evolution (NB-IOT) Time bounded Release planning approach with clear list of features and capabilities aligned with all related working groups Requirements, Architecture, Protocols, Test [Source: Qualcomm] Including test Confidential 11
Thank You Confidential 12
