- David Perez Caparros (Swisscom)
- Tim Carey (Nokia)
- Oskar Malm (Ericsson)
- Atul Purohit (Vodafone)
- Min Sang Yoon (TATA)
- Bharath Thiruveedula
- Steve Polston
- Chaker Al-Hakim
- Chris Rapposelli-Manzo (AT&T)
- Marge Hillis
- Thomas Theimer (Nokia)
vijay ramachandran (Infosys)
- John Quilty
- yaoguang wang
- Joanne Liu Rudel (AT&T)
- Gerard Kelly
- Chuyi Guo
- Gerard Hynes (AT&T)
|R5 El Alto Use Case Discussion||Benjamin Cheung|
|A&AI Schema Changes for R5 El Alto (ESR, Complex, PNFid/PNFname)||James Forsyth|
ESR (external NMS) - EMS/NMS + ONAP.
Complex (Cloud Region ID/Home) - (verify with Jimmy)
New A&AI parameters for xNF.
Physical Location, Location within system (Cloud location)
|BBS U/C Platform evolution|
San Jose presented proposals for next release for R5/R6.
Slide set linked in R5 proposed U/C.
List of proposals & functional requirements.
|San Jose DF Discussion|
|M4 R4 Milestone discussion|
TSC M4 Score Card
R4 Dublin M4 Milestone April 11, 2019 (Tomorrow)
Platform Evolution for Data Persistency (R-future)
|Controller to NF Association (R-future)||Benjamin Cheung|
|Firewall U/C in R4/R5||Bharath Thiruveedula|
|PM Dictionary, FM Meta Data GUI evolution|
R4 FM Initial GUI will be available, that work is underway. Only able to present fields are defined in VES events. Will need evolution in a future release and updates in the next releases.
3GPP release which integrates VES events into 3GPP.
PM - change structure of defined VES event provided working discussions to talk about modifying to have each measurement be its own record in the VES file. Better organized information for GUI to pull into a policy engine. Modify and create a proposal.
Requirements for PM / FM are completed.
|PNF S/W Upgrade U/C R5|
|ETSI SOL001...SOL007 Modeling|
|PNF Pre-onboarding/Onboarding U/C in R5||PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt|
|Network Slicing in R5|
|Controller LCM API Evolution||Oskar Malm|
Proposal in ARCHCOM:https://wiki.onap.org/download/attachments/50202249/2019-04-09%20ONAP_LCM_API_Evolution_El_Alto.pptx?api=v2
High level goals:
One possible solution was presented based on existing LCM API defined in YANG, but consolidated into CCSDK with APPC code as likely starting point. When receiving incoming API requests, this code performs logical functions such as request validation, optional NF locking and finally dispatch - today this means selection of Directed Graph (DG) to execute. The common implementation would be extended for PNFs and CDS integration.
This is ongoing topic and there is no ARCHCOM recommendation yet.
R5 El Alto Cadence Proposal (EUAG / End-User Advisory Group)
Summary: The El Alto release could be shortened
and focus on internal (tech) debt and defect backlogs.
A proposed release cycle is presented.
|Audio Only (M4A)|
|5G Use Cases in Next release (R5 or R6)|