Page History

https://wiki.o-ran-sc.org/download/attachments/3604609/TIM-2023.03.22-OSC-RSAC_Architectural_principles_for_SMO_Services_integration.pdf?api=v2

https://wiki.o-ran-sc.org/download/attachments/3604609/ONAP_OSC_Areas_20230321.pdf?api=v2

Video: https://zoom.us/rec/share/D3ZkRsAQ1lu9QY1zomJmAnmXzAUL3FTWJSFqCPDIUKVmZ96HbEu7DQLy34yidjDe.GMyDeZXm34UwgOSR

Audio: https://zoom.us/rec/share/WHxLIovLZwplnMMG8S-ug0if9N6_Yan_EozSFIU-MsqlazU_AJoLeLMIxELzPw_d.HJXpZGiTQNOF3XUI 

NTUST Lab: Ankit was unclear if lab was reverted. Prof Ray indicates the server is the same they have been using. Bimo there was some work for integration to real RU but now is connected to the TM500. Ankit to verify if change corrects the blocking issue.

O-DULOW no plan to upgrade to newer version. Willing to provide bug fixes as needed.

ONAP projects with OSC synergies not yet available. Work is in progress.

SMO Function Flows. Discussed current work for O2IMS Cloud Registration and Discovery flow and Homing Flow.

Video: https://zoom.us/rec/share/GqibkTXPX22Nna8ugM5lMPs1GQNUgTyjFeY9WhLeV-nPnk4qwNRlUmy-qRz2xBrj.w_-Q2VUHw2EZtptR

Audio Transcript: https://zoom.us/rec/share/TTR6lFw7o_K-u8NKhKTOJzm_zS4CisX-di1QEhRnvw5Lo4Z85PsarvNNrCXMYM-S.mnAh9buqT2J6gCto

Video: https://zoom.us/rec/share/9X1v6Yhvqj8FlPU6-OObqnGhH8BY_kYFUqbH7fADygY7gIsRPicwquKawfDQDL8b._S8SB51ogACVaxkg

Audio: https://zoom.us/rec/share/Z09nCSFLm31P3_JJDtj1EXou9UigMRiloauWsMsK7kF5-BJcKMtQ_V9ZArSVBhEw.5FoRyzPECAd8gTRn

OAM Project

• Update VES messages and align with 3GPP Rel 18

SIM Project

• NS-3 project update to E2SM 2.0 (reach out to Michele Polese)
• OAI and OSC interop

INT Project

• Work ongoing with INF project in CA lab

SMO Project

• Gaps for "H"
  • FOCOM
    • Cloud Registration
    • DMS Deploy/Config (Tacker)
    • Cloud Inventory
    • Package Onboarding
    • Package Inventory
  • NFO
    • Homing
      • - 2 tags
        • Cluster-Type (AIO-SX, AIO-DX, AIO-DX+)
        • Package Type (ASD, ETSI)
      • All Deployment Items to same DMS, later might have distributed deployment
    • Package Deployment Inventory
      • Multiple Deployment Items
• Integrations
  • AIML-SMO Influx

 INT Project

• • OAM+SMO+NONRTRIC+AIML=baseline SMO

End-to-End Lab

• Need Cloud connections to OAM/CP/UP networks, need ODU-HIGH to OAM/CP/UP networks.
  • ODU-OCU CP/UP bidirectional
  • ODU-OCU to SMO bidirectional
  • OCU-AMF on CP
  • OCU-UPF on UP
• Deploy O-CU
• Taiwan Lab
  • Working server configuration for ODU install
    • Server is more powerful than needed but something is off on the configuration. Need Radysis and Intel to assist.
    • Would like more documentation on configuration for both O-DUHIGH annd O-DULOW.
    • O-Cloud Simplex Install Complete

O-RAN F2F

• Need "G" Summary/"H" Plan

NTUST - ODU Scheduler Decoupling so that different schedulers can be used.

• Coordinate with Ankit for NTUST for new committer.

Open RAN Work Shop on Feb 13 and 14: https://www.knaintl.com.tw/2023OpenRan/

Need to ensure O=RAN F2F does not conflict.

"H" Release Planning - Are we ready for O-RAN F2F?

AIML

• DME Integration
• Training pipeline Enhancement
• SMO - InfluxDB Integration
• KServe adapter
  • Deployments to Near-RT RIC
  • Suggest Deployments to Non-RT RIC as well

O-DU HIgh

• End-to-End Integration
  • TDD/MU1/100Mhz
  • FDD/MU0/20Mhz
• Feature Enhancement - Stub-based Testing
  • Alignment WG-8 AAD Specification 
  • Inter CU Handover Support
  • E2 Interface enhancement

TACKER

• Need to find out how to fill in the SMO Gaps

OSC/ONAP 

• Trying to establish more structure around the relationship.

NTUST

• Upcoming Open RAN Workshop

Blockers for Release "G"

Tacker (SMO) - Ready

AI/ML - Ready

O-DUHIGH - Move blockers to "H" Backlog

Some Cleanup is needed, this will drop the Lines of Code this will be done during the maintenance release. This will not result in any functional change.

"H" Activities

OSC - OAI Integration

Possible Options: End-to-End using OSC RAN and OAI Mobile Core can be incremental in where the workloads execute. Target would be to use O-Cloud?  Goal: End-to-End 5G Open Source Network

Possible Options: OSC SMO Integration with OAI Elements Goal: Would standard manageability

Possible Options: RIC-RICAPP Portability OSC RIC with OAI RICAPPs, and vice-verse Goal: xApp Portability

Step 1: What would it take for SMO to deploy in a (OSC or OAI) lab a OAI CN element. Goal: Explore the gap between OAI NF and OSC Infrastructure/SMO.

OSC - ONF Integration

Possible Options: RIC-RICAPP Portability OSC RIC with OAI RICAPPs, and vice-verse Goal: xApp Portability

Tacker "G" Update

Supporting 02DMS-ETSI looks like part of Cloud

Can be configured with K8s API which would be like a consumer of the O2DMS-K8s and therefore deployed as part of the SMO

For "H" we need new SMO functions for Homing, Inventory, and NFO. These can be minimal in which ASD support by Tacker would consume the O2DMS.

Need to work out how Tacker for ETSI as a O2DMS-ETSI is registered with SMO, vs Tacker as a NFO extension, uses the O2DMS-ETSI. Could NFO then just use the passed Tacker instance as its orchestration end point?

SMO/OAM/AI-ML/NonRT RIC/O-Cloud Integration for Release H

• No RSAC calls in 2022 after the 12/14 meeting.
• Focus of "H" will be "SMO Integration" to be further discussed on 12/7/22 RSAC after the SMO project meeting.
  • NFs to work on packaging and PNF/CNF Registration
  • SMO Blueprints (SMO/OAM/Non-RT RIC/AIML)
  • INF to support VMs for SMO components
  • Lab O-Cloud Build-out to move off of Lab OpenStack VMs

Release H Planning

• O-DU

Lab Status

• Update on OSC US East Lab Network update

Release H Planning

• SMO
  • Tacker Capability - SOL001 and SOL003 (VM/CNF)
  • "F" Tacker integrated with CISM
  • "G" Tacker integrated with VIM
  • "H" Tacker integrated with OAM (Packaging)
    • ETSI NFV first
    • K8s second
    • Extend to support ASD
    • FM/PM requires O-RAN WG6 specification
  • Need Contributions outside of Tacker for:
    • Cloud Registration (FOCOM)
    • Cloud Inventory (FOCOM)
    • Homing
• INF
  • Do we need OpenStack support for SMO/Tacker deployments via the O-Cloud?
• AI/ML
  • Interface prototyping
    • AI/ML to DME?
    • What is the data interface for xApps
    • Integrated Installs

Lab Planning

• David to get with Rich for server network interface to support OAM, Control, and User Plane connections. Then configure Core Simulator for Control and User Plane network connections.

Release H Planning

• Non-RT RIC
  • Wrap-up rApp Mgmt
    • LCM Instantiate/Terminate/Update
    • Onboarding/Registration
    • Service Exposure/Discovery
    • Data Exposure/Discovery
      • DME Subscription - Stretch Goals
    • A1 over R1
• SMO/INF
  • O2 Integration
• SMO/NF OAM SMOF
  • Alarm Analytics
  • Performance Job Management
  • Alarm/Performance DME Registration - Stretch Goals
• AI/ML
  • Componentize AI/ML-NonRTRIC interface functions
  • Interactions with DME/Databases
  • Continued CI/CD Improvements from "G"
• INT
  • OSC Project/SCCL Project Integration

• F2F videos

Next week video submission 10/11/22 deadline to RSAC https://wiki.o-ran-sc.org/display/RSAC/Contributions
SMO - O-DU and SMO video (Mahesh)
OAM, SIM - Martin, video for O1 notify PNF registration, 3GPP alarms, WG4 and WG10 (Martin, Alex)
Integration - James to update the current video 
AI/ML framework - Joseph to show the dashboard and initial training flow video
O-DU - O-Du setup and handover video (10 min video Ankit)
Non-RT RIC - prepare a short presentation (Status update by John K)
Near-RT RIC - 30 min video (Thoralf)
INF - O-Cloud ?? send email to Jackie

- H planning
  SMO and O2 integration
  TAacker vs K8s native, both DMS available
  AOSX, AODX, AODX+ selection attribute in DMS
  5G super blueprint
  OAI ?? Can only run in Taiwan lab (Academia)
  AI/ML framework and SMO flows
    Where does AIML f/w derive its data from (training data)?
    SMO -> R1 -> DME -> O1 -> AI/ML
  Non-RT RIC
    R1 implementation and rApp mgmt, start enforcing the use of R1 i/f
    SME module
    rApp LCM enforcement
    DME will have examples of the use of PM jobs over R1 (Streamed and file based)

Create a short OSC overview deck, accomplishments and status update for G release (Jinri, James, David, Rittwik)
- 6 releases
- 3 independent labs
- 10 projects
- TOC/RSAC
- https://insights.lfx.linuxfoundation.org/projects/oran/o-ran-sc/dashboard

AOB
Joint FYUZ conference following O-RAN F2F
-windrvr to present

F2F Agenda

• AI/ML will create a video
• INT project demo recording
• SIM - Video record StdDefined VES
• O-DU - recorded Handover feature
• Near-RT Demo recorded - 30 minutes
  • How to deploy Near-RT RIC
• SMO - planned demo of receiving O1 from O-DU

"H" Planning

• Super Blueprint

O-DU

• Need ASN Decoder, current Git source is now archived
• Points to Nokia seed however, some messages are not being properly encoded
• It is unknown who to contact to correct in code base or what is wrong with O-DU code
• Will bring up at the TOC

O-CU Deployment into O-Cloud

O-DU Status

190 Server should have images and HELM but currently doesn't allow SSH.  – Rich to Check...

Once SSH is re-enabled then we need to know the directory 

10am Eastern Thursday Ankit (O-DU), James (INT), David (RSAC), Jon (INF), Rittwik (RSAC), Bimo (NTUST) - David to setup meeting

AI/ML Project status

Madrid F2F agenda

NJ Lab Review

O-CU deployment

O-DU 190/191 reachability issue

Demo Availability for O-RAN F2F Oct 20th 4:30pm-7:45p, Madrid 

• OAM
• SIM
• NON-RT RIC
• RICAPP
• AI/ML

AP: David Kinsey to schedule synch up for OCU Deployment from SMO via TACKER using O2 Interface from INF.

OAM - VES Standard Defined Message

SIM - Yang Sim or E2 Sim demo -

Potential Integrated demo: SIM VES Generation, OAM Collection, SMO Storage in InfluxDB

CU Deployment

Non-RT RIC: Will come up with something specific for O-RAN

AI/ML: Joseph will look into what is possible from the initial seed.

RICAPP: No data

RICPLT: No data

SMO: No data

Draft Agenda:

Demo Availability

• INF
• RICPLT
• RICAPP
• OAM
• SIM
• Non-RT RIC
• SMO
• AI/ML
• ODU
• E2E

INT Project: XFT Framework demo Wed RSAC Sep 21st. Will record and make available to Tue participants.

ODUHigh: Demo Sept 13 or 27 Handover feature from "F"; Stub based demo; In Local Dev Lab.

End-2-End will be prior release tests: Closed Loop tests.

Draft Agenda:

Demo Availability

• INF
• RICPLT
• RICAPP
• OAM
• SIM
• Non-RT RIC
• SMO
• AI/ML
• ODU
• E2E

INT proj (James) to set up discussion for XTF testing framework

AI/ML proj to provide a repo structure 

AI/ML project to interface with SMO project to understand the touchpoints

OAM project is working with Tacker proj for initial integration

Release "G" Feature Planning

• RICPLT
• NONRTRIC
• OAM - Received in e-mail - In project will add to Release
• SIM - In project will add to Release
• AI/ML
  • "G" Standalone, possible RICAPP deliverable too
  • "H" begin cross-project integrations

Lab Status

• US WEST

AI/ML Project Proposal

Release "G" Feature Planning

• ODUHIGH

  • End to End Integration support (Spillover from previous releases)
    1.TDD/Mu1/100MHz
    2.FDD/Mu0/20MHz *

  • 
    

    Feature verification (Spillover from previous releases)

    • Closed-Loop Automation

      • Link Failure Detection and Recovery

      • Slicing PM Reporting and PRB Reservation

    • 16QAM and 64 QAM

  • 
    

    Feature Development
    1. Implementation of Discontinuous Reception (DRX)
    2. Inter CU Handover support
    3. Aligning all modules and interfaces to latest specifications

  • Question to INT for Health Check requirement, request parameters and expected results.
    • Alarm Summary?
    • Module Status?
    • Interface Status?
• ODULOW
• RICAPP in project meeting notes
• INF - Received in e-mail

Lab Status

• US EAST

Reviewed proposal for new AI/ML Framework project

Reviewed proposal for new AI/ML Framework project

• Slides will be posted when available
• Scope noted as large, suggestion from other PTL was to commit to a focus initially and expand over time
• Some LCM may overlap with Non-RT RIC rAPP LCM this needs to be refined such that a clear demarcation exists between the two projects
• With four projects for the overall SMO one project will need to be responsible for ensuring they can all be assembled into an O-RAN SMO. Suggestion was for the SMO project to be this point but the PTL was unable to make the meeting.

Topic: Zoom1 O-RAN SC's Personal Meeting Room
Date: Jun 15, 2022 08:07 AM Eastern Time (US and Canada)

Meeting Recording:
https://zoom.us/rec/share/sCINkMMM7TRqQ4QuN7h4tzbedDAzUhrIQe4dvSeSKedZ-yjgOBHNYbVURjLAosde.g7X-rxZ8SXsCs7xD

1. ORU-ODU pairwise testing progress (10 minutes)
   1. ODU Synch still the same skipping clock. 
   2. Action Item: David will get with Rich to verify if 190 is connected to the O-RU or 191?
2. OCU deployment on O-Cloud progress (5 minutes)
   
   1. Binaries have been released from Radysis.
   2. Action Item: David will get with Bin (INF) to verify IP and availability of AIO-SX.
   3. Action Item: Ankit will FTP to lab and work with Bin (INF) to deploy onto AIO-SX,
3. Release G Planning and O-RAN F2F Synch (45 minutes)
   1. Only the ODUHIGH and INT PTLs were present. Planning was not able to occur.
      1. ODUHIGH "F" Features were held up by lack of O-RU availability, therefore "F" Features are backlogged into "G".
      2. INT "F" Features were held up by OTF no longer maintained and thus non-viable. Therefore "F" Features are backlogged and will have to be replanned into "G". PTL is working with LF to find out how their CI/CD Toolchain might be used. Will require participation by each PTL in "G".
   2. Action Item: David to bring up to TOC that RSAC is only effective if PTLs participate.
   • • • DUPLEX+
4. Walk Ons:
   1. Samsung proposal for AI/ML Framework project. John Keeney had to drop and Mahesh was not in attendance. We need those projects and preferable OAM and INT as well to understand how the SMO is assembled from the potential 4 projects.
      1. Action Item: Samsung will start an e-mail thread and hope we will have a quorum to discuss either on the SMO+RSAC or the next RSAC+SMO calls.
   2. Tacker development team still needs lab access for SMO project
      1. Action Item: David to reach out to Rich to make sure the request didn't get missed.

IXR Should be ready by 5/20/22. We found a bad optic cable and are replacing it.

OTF is permanently down, we are soliciting ideas from PTLs for new test automation tooling or ideas.

INT needs each PTL to create a "Healthcheck" type of test/script in which the project can be deployed and verified as "healthy". INT will then look for interoperability across projects. This will require participation from the individual projects and is not something INT can do entirely on its own.

We identified while working towards the OTF workshop that projects sometimes assume things still work, when in fact they don't. This verifies the need for automated testing.

O-DU HIGH needs O-DU LOW to install/verify the latest build in installed in the OSC lab. David and Rittwik will reach out to ODULOW to ensure there are not any blockers.

OTF workshop postponed to next week. 

Here is the progress in Taiwan OSC Lab (Prof. Ray):

- New results

1. Modified OAI CU 

     * Topology: PHY-Stub <--> OSC O-DU-High <--> OAI CU: RRC  Connection Setup is done.

 2. Tested the S-Plane in Chunghwa Telecom (CHT)

     * Topology: GM <--> O-DU <--> TM500 RU Simulator

- New partner: Auray will also provide their TM500 to support the OSC testing. Auray is also running OTIC Lab. in Taiwan 

- On-going jobs

1. Joint survey paper
2. Auray will make a trip to US. They hope to visit OSC Community NJ Lab. Please check any available slots if possible.

- On-going jobs in Taiwan lab and need support from Radisys. 

1. Testing Intel FlexRAN 21.03 version of O-DU Low

Ankit: This activity has not been planned in F release and will be taken in account during next Release planning phase (G release)

2. We added an E2 Handler in O-DU High and connect it to RIC: Ankit, please reply with an email showing your plan.

Ankit: As of now we are reaching towards end of the F release and do not have bandwidth to accommodate these changes with review.

Topic: Zoom1 O-RAN SC's RSAC mtg
Start Time: Apr 7, 2022 09:08 AM

Meeting Recording:
https://zoom.us/rec/share/wCsBDCOaJiCpyWDorvmkLjEKOSSl6srTASAWYQe5HpmBkT9KYXUWbB02j5JYEWv0.bQ6lnFyGjIMVpJ10

Lab Update

• 3 Servers identified for INF Project
• IXR Configuration in Progress. Have Nokia Resource to assist. 
  • Requires new 10.10.11.xx IP for OAM Network Gateway on M-Plan VLAN

Lab Needs

• DU and RU connections
  • vlans 
  • Clock Multi-Cast Address (hard coded or default/std)

"F" Release

• SMO
  • Integration to O2 (INF)
• INF
  • O2 IMS
  • O2 DMS (pre-spec aka HELM)
  • System Controller Cloud
    • Manages Sub-Clouds aka distributed resource pools)
    • Creates Distributed Cloud Architecture
  • O-Cloud with three resource pools
    • SIMPLEX
    • DUPLEX
    • DUPLEX+
• ODUHIGH
  • Support Paging Feature
  • Inter-DU Handover
    • 2 DUs under same CU
    • Requires another Server for second Physical O-DU
    • Need to check with Viavi to see how this affects the O-RU simulator

"G" Release

• SMO
  • Possible bring in ONAP ASD Orchestrator (O2DMS candidate)
    • Contact Byung-Woo Jun from ONAP Architecture
  • Needs to support O-Cloud Registration (O2IMS)
• INF
  • Add 4th resource pool from Blockhouse Resources
  • add those resources to Duplex+ Cluster creatings a distributed cluster

Next Meeting 1/4/2022

"F" Release

• RICAPP
  • OTF "F" Release Test
  • RC xAPP (Slice Management)
• RIC
  • OTF "F" Release Test
• OCU
  • OTF "F" Release Test
  • Test Stub Image Basic Support of O1
• ODUHIGH
  • OTF "F" Release Test
  • Support HARQ Feedback
  • Scalability (Scheduler Enhancement)
  • E2 Interface Upgrade
    • Near-RT RIC Connection (Stretch Goal)
• ODULOW
• OAM
  • OTF "F" Release Test
  • O1 Pre-Release for Message/Streaming
• SIM
  • OTF "F" Release Test
  • O1 Pre-Release for Message/Streaming
• NonRTRIC
  • OTF "F" Release Test
  • R1 Service Exposure
    • A1 Policy
    • A1 Enrichment
    • rAPP Onboarding/Deploy
  • Test Scenario Organization
    • By Scenario/Use Case
• SMO
  • TACKER (Orchestration) (Docomo)
    • What will be deployed?
  • CRD Based Onboarding (Kubernetes Deployment) (VMWare)
    • xAPP
    • rAPP (Stretch)
  • OTF "F" Release Test
• INF
  • 3 Resource Pools (SIMPLEX, DUPLEX, DUPLEX+) Kubernetes
  • OTF "F" Release Test
• INT
  • OTF "F" Release Test

Lab Status

• NJ Lab
  • O-DU High still not accessible
    • Pending correction of this to install FHG (IXR+PTP-GM)
    • May have to resort to invasive recovery of the hardware
  • Discussing with Viavi on strategy for TM500 sharing from the lab
• "F" Release
  • Discussed Windriver plan for O-Cloud/O2 builds in "F"
  • Discussed VMWare plan for xAPP Onboarding Package in "F"
  • There was a mention of O2 from DCM, "Tacker". More information expected on SMO call Thursday.
• "G" Release
  • Migration of all xAPPs and Near-RT RIC to deployments from SMO, with homing to blockhouse servers in the Duplex+ Cluster (Spans two resource pools).

https://zoom.us/rec/share/rc59UMy0Dwu5ufHBwgU7p3OOR_pr52HtkTkYPHfhCBv9pfOS_r9gm6IDBGcyZ929.ZgUiufRZwTPzvjHA?startTime=1638929199000

https://zoom.us/rec/share/trMp1skIckvuRm_YzhPVraYXnutpoD6OHAPYGpXKg0-NaU960-RANQ0vpyU69sd9.KpxB5iw5OFA7VYV9?startTime=1638885823000

Lab Status

• NJ Lab
  • Clock in progress
  • IXR pending Cable

"F" Release

• SMO - INF Integration
  • Might look at CU for Deployment Option
  • VM Server needs have the ConfD Server installed
• APP Packaging
  • VMWare is interested in SMO Contribution using CRD packaging proposal
    • Need
• O1 PM CR Status
  • Rationale presented to O1 Focus Group
  • 3GPP PM Streaming supports GPB, O1 does not, CR Submitted for next meeting 11/29.
  • Will break down the CR into smaller chunks that can be independently addressed.
    • Decouple Stream Consumer and Job Manager from using common index to map value to measurename
    • Subscription Enhancements, Decouple Job from Reporting
    • Use Stream Report as Event Report in REST/JSON mechanism

Release "E" Slice Reporting

• Extension of VES Measurement Domain. Will be StdDefined in "F" Release
  • Started work on "F" JSON; more is still needed
• Config still not baselined, critical for rAPP work
  • Martin will finalize HelloWorld to work for us
  • ODU-H is good with this

CR Status

• On Track for First Nov O1 Meeting

Lab Status

• Viavi "Demo" Equipment
• IXR
• PTP-GM

Slice Use 

CR Status

• Alex provided link to GNMI Flow for incorporation into CR

Integration Status

• Interfaces are not defined for the closed loop Use Case
  • Need PM interface between O-DU-HIGH→SMO
    • We have a non-3GPP Plan, using VES Measurement Domain
  • Need PM Interface between SMO→ rAPP
    • TopicName: MeasurementEvent (4 Values)
  • Need CM Interface between rAPP → OAM
    • Driven by YANG of O-DU-HIGH (RESTCONF)
  • Need CM Interface between OAM → O-DU-HIGH
    • Driven by YANG of O-DU (In Discussion)
    • Believe we can use 3GPP in build and reference forge path  but cannot tag the replicated file used for the build for the Release in order to preserve 3GPP Copyright.

3GPP

• OAM/SIM will work on Best Practice for using 3GPP (forge) documents in builds/documentation without publishing as part of the release.

Lab Status

• Still waiting on IXR
• Haven't resolved the plan for the PTP-GM

Slicing Use Case

• Will have 2 rRMPolicyMemberList (MCC MNC SD SST)
  • 1 Best Effort, Slice 1 Managed Slice
  • MCC/MNC (aka PLMN) should be same as known by Core
• Will use rRMPolicyDedicatedRatio for Managed slice
• PM is Average DL/UL UE Thoughtput
  • Collection Interval same as Reporting Interval
  • Reporting Interval will be every 60s
  • One counter for each (UL/DL) (Uint32, kbits/sec)
    • DRB.UEThpDI.SNSSAI
    • DRB.UEThpUI.SNSSAI
  • SLA for the Managed slice is a throughput of 1Mb/s
  • Initial Managed slice has PRBs with a 40% reserved/quota
  • The rAPP should have a configuration value for enabling and disabling the control loop to allow the test controller to identify when the SUT has a stable traffic load.
  • When throughput drops below the 1MB/s SLA by 10% (900Kb/s) then the rAPP increases the reserved/quota by 10%
  • When throughput goes above the SLA of 1MB/S by 10% (1.1MB/s)  then the rAPP decreases the reserved/quota by 10%; this cannot go below the baseline slice reservation (40%)

9/9/21

9AM EDT

VES Improvements

• Disaggregation Tabled for now
• Kafka Backend to Influx/Elastic-Search/DMaaP
• Streaming PM (Should be an "F" Release Target)
  • VES/JSON (Requires O1 CR) (AT&T)
  • HV-VES Websocket/GPB (Requires O1 CR) (DELL

Scorecard

• Specification Compliance Scorecard
  • Element Maturity (Behavioral Compliance)
    • PTL to self report to Scorecard ("E")
  • Interface (Specification) Compliance
    • OTF (INT) is looking at the FH Test Specification for M-Plane ("E")
    • OTF for Element which would apply the applicable Interfaces required by the NF (OCU-CP, OCU-CP, ODU, NearRT RIC)
    • PTL Self Report ("E")
    • OTF Auto Report ("F")

8/12/21

9 AM EDT

Discussed using format of ODU-HIGH Release "E" plan to formulate a release plan with one for each project. David Kinseyto send that. E-Mail sent with proposed template. This would replace the single 9MB growing powerpoint with a per-release plan.

7/22/21

9 AM EDT

4/13/21 

9 PM EST

Discussed 5G super blueprint for E release

DU - RU message interaction blockers

TM500 equipment preparation by Viavi for delivery to OSC lab NJ

Meeting recording: https://zoom.us/rec/share/DuzSNJy8-iAE-ll5JAh-GR4LEgHH4N3_J6on5A3p2O0TqShiW4Lfp5v1WwZhRRmk.O1sBLrdw6K86qN-E

3/11/21

9am EST

3/1/21

9 PM EST

2/25/21

9 AM EST

Meeting recording

https://zoom.us/rec/share/Fw56lJ-t3FnHqBqrc-fWVcNfTq4BvLClnNO69jV3FFVAxMN9mcgelDCaOR_LT5sR.69SVCt37YleQy-8N

1/14/21

9 AM EST

Meeting Recording

https://zoom.us/rec/share/mKYOGkB3mgpvIo2Hx1eY5Oifyw9qV9NQd7NiEj-FxQKP0kUpWOc7yvMO_LLPhA_M.lmx2LCh7-QwDHAFi

11/19

9 AM EST

Meeting Recording

https://zoom.us/rec/share/VFSBeQa7lt1AlmAR3VIm4Sc8ooVaIOeMNiVbBKcB3MUOj3OCmK1hMozwT8PjFfpo.ATGZ99NFppAp5jbo Passcode: 5aKgaDF=

9/15

9 PM EST

Meeting Recording: 

https://zoom.us/rec/share/kqC7KdRNI3DMrDUNktdYl5OCw49pLaDtvq18hFYByNYixatyCBf9kLomcrngPsoU.GuHU_cB9kpTPc80W Passcode: Qw*z$6Zb 

9/1

9 PM EST

• Discussion about OSC lab setup and timelines for testing and integration

  
  

  Week starting

  Sept 7 – Configure Intel servers and install OS (windriver, server 1)

  Sept 14 – O-DU Low software installation and unit testing with stub RU simulator (server 1)

  Sept 21 – O-DU High software installation and unit testing with stub CU simulator (server 1)

  Sept 21 – Viavi O-RU emulator, O-CU emulator, EPC installation on (Server 2)

  Sept 28 –  O-CU software installation and unit testing (Server 2)

  Oct 5 – O-DU high and O-CU unit testing

  Oct 19 – UE attachment and HO test

  Oct 26 – UE attachment and HO test

  
  

  The OSC lab server addresses are

  Server 1

  Management IP 192.168.4.29

  Interface 1 192.168.41.190

  
  

  Server 2

  Management IP 192.168.4.30

  Interface1 192.168.41.191

8/18

9 PM EST

Meeting Recording:
https://zoom.us/rec/share/3NIlIoHd5nlIQoWX90_TX6A-T4XLaaa8gXca_qdbxElpW9nzSwAkkYnIq3rVWIHt

Access Password: zYN&Hv3s

7/28

9 PM EST

• Meeting Recording:
  https://zoom.us/rec/share/y85SdZrNp3lJZ5HvyBHva6kzOIi9eaa81igYrvZexUoZMVDrqQzkhXCuzECxunt4

  Access Password: M!s2VJg0

7/16/2020

9 AM EDT

Meeting Recording:
https://zoom.us/rec/share/ou4lNK3RzDxJQ7f1s0bPZpMeF53Ueaa8hndK_qYOykxKEdi7dj46TU6b_Mxlyk-N

Access Password: y$SNs?w7

INF project cherry epics

• HA in O-Cloud - 2 server deployment scenario duplex

  
  Start Time : May 26, 2020 09:01 PM

  
  

• Meeting Recording:
  https://zoom.us/rec/share/-upyKIvR6DxIZtLy6kjkevdiGK_VX6a81yhL_qUIxU2sJ0PJ9nDsaKLVCk3ubLEW

  
  

Topic: Cherry release planning
Start Time : May 12, 2020 09:00 PM

RSAC requesting PTLs to start suggesting EPICS for Cherry

4/28/2020

9 PM EDT

4/9/2020 

9 am EDT

3/26/2020

9 am EDT

3/10/2020

9 pm EDT

Bronze rel. – PTL reports from ODU LOW, INT

3/3/2020,

9 am EST

Bronze release documents

Epics spreadsheet: RSAC_Bronze_release_planning.xlsx

Traffic steering use case: RSAC_Bronze_Use Case-Traffic Steering QoE.doc

Health check use case: RSAC_Bronze_HealthCheck_UseCase.docx

Reviewed and addressed comments

• Created epics for different project groups