1. READ THE DOCS - Mar 4 2020 U/C Realization. Intention by docs team to move all the wiki pages into the readthedocs. Sofia will talk again at a U/C realization call. Create Jira ticket in Integration Project / In Integration project FOLDER / update RST file (on RST file per Use Case). Andreas Geißler suggested making Use Case Repo for U/C Documents.
2. Architecture S/C Presentations - for R7 Req/UCs - "Due by M1" ~Mid June 2020
3. Get ready for M1
4. OPEN Model Items - A1 Adaptor, C&PS, Licensing

R7 GuiLin Requirements & Proposals -

TIMELINES: R7 GuiLin Release M0 - June (8-19) (may shift due R6)

Requirements S/C page: Requirements subcommittee

R7 new requirements, currently proposals in R7: Guilin release - functional requirements proposed list

PNF & 5G USE CASES/REQUIREMENTS:

Guilin release - functional requirements proposed list#E2ENetworkSlicing

Guilin release - functional requirements proposed list#SupportxNFSoftwareUpgradeinassociationtoschemaupdates

Guilin release - functional requirements proposed list#OOF-SON:5GSelf-OrganizingNetwork(SON)usingONAPOptimizationFramework(OOF)

Guilin release - functional requirements proposed list#RunTimeConfigurationDatabase/DataPersistencyServiceProject

ARCHITECTURE S/C Presentations:

ORAN-ONAP Harmonization Use Case → Approved 19 May 2020 

CMPv2 work → Approved 06 Apr 2020 

PNF Plug and Play → Approved 06 Apr 2020 

PNF Onboarding / Pre-onboarding → Approved 06 Apr 2020 

5G Service Modeling (Modeling) → Approved 06 Apr 2020 

Licensing Management (Modeling/Arch) → 02 Jun 2020 

PM Control Extension → Approved 26 May 2020 

A1 Adaptor Extensions → Approved

5G NRM - Arch Review scheduled 16 Jun 2020 

• Document Use Case Wikis for R7 because the Use Case S/C → Requirement S/C; Architecture S/C; ReadtheDocs → Use Case page under instead of wiki pages.
• New Use Case Template - Use Case Template: Use Case Tracking Template
• R7 Modeling Planning - available ONAP R7 Modeling High Level Requirements

REQ-1

1. David Linking Arch Ticket - ONAP Use Case / Requirements Teams Process Way of Working (WoW)
2. Make Story Jiras - Ben met with David McBride
3. REQ-jiras done

Joanne Liu Rudel

Benjamin Cheung

Architecture S/C presentation for Run Time DB.

Team is working to define the Proposal (see wiki).

Then it will be presented at the Arch S/C and then TSC.

Sync with Sandeep - will meet with Sandeep Fri 7 2020. Ted Johnson. Existing interface.

For R6, will be part of CC-SDK. Met with Yuriy Malakov  & Dan Timoney . CONFIGURATION & PERSISTENCY SERVICE not a separate component in R6.

CMNotify - The DCAE, CMNotify VES event (proper) are pushed to R7

• STEP 1 GENERATE: xNF (RAN Simulator) GENERATES a VES CMNotify - Wipro SON (R6)
• STEP 2 RECEIVES: DCAE VES Collector RECEIVES the CMNotify - Nokia (R7)
• STEP 3 DCAE: DCAE PROCESSES Event- Nokia (R7)
• STEP 4 DMaaP: DCAE PUBLISHES onto DMaaP - Nokia (R7)
• STEP 5 LISTEN: CCSDK (Controller) LISTENS to DMaaP - SandeepShah (R6)
• STEP 6 RTCfgDB: RTCfgDB UPDATES with info - SandeepShah / Techmahindra Devendra Chauhan (R6)

Feb 3-7 Nokia has confirmed that Step 2/3/4 is in R7 due to VES review.

Meeting setup with Sandeep - R7 planning. Need to make a presentation for Alla's call: ONAP Use Case / Requirements Teams Process Way of Working (WoW)

R7 - Decide if we can to be a separate component. need to find a PTL lead. 14 Feb 2020 

Automation tool integration. Schema details.

Q#1 (Seshu) RunTime Catalog in CCSDK vs DPS - they are different & have different purposes. Reuse of existing database.

Q#2 questions controller have config data why isn't that sufficient why can't we store this in A&AI.

 "Source of truth" - controller would be allowed to change / update info for Configdata others Read.

Catalog/  model driven Use Case onboarding package, SO not impacted.

Q#3 - why don't we have this as part of A&AI in Eric Debeau - storing not just inventory, but configuration information and additional information. multiple persona a common data is more elegant than each controller having its own database. 35 databases in ONAP.

Q#4 - structured database / justify the technology selected for this work.

Q#5 - Roadmap of functionality

Q#6 - scalability / performance need queries are not complicated & volume of information will not be as high performance - performance

•  Read the Docs entry https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_usecases.html navigate to USER GUIDES > VERIFIED USE CASES.

Borislav Glozman

Shankar PN

Swaminathan Seetharaman

LIN MENG

Update on slicing proposal. SO/Seshu presented.

Multiple functional requirements/Use Cases. Recursive orchestration of nested services. Didn't want independent W/F for flows but try to leverage/reuse work. Presented the End to End U/C with macro-view for E2E slice. and components impacted. Right now impact will be on SO, OOF, Policy, SDC and AAI. What controller will be used for managing slices? Focusing on design aspects and instantiation and activation. Put up logical E2E slice. Target simple VNFs. Focus to create VNF vs reconfiguring a VNF? Slice segments are going to be both dedicated/shared. Started with discovering existing resources; assume segments created with VNF/PNFs in inventory & discoverable. Spinup new slice instances.

02 Jan 2020:

• (1) ROADMAP - Proceeding with detail, developments for roadmap beyond R6.
• (2) API - defining API in progress.
• (3) PoC - Prototype of PoC from Orange focusing on VNF-portion.
• (4) SO - Implementation in SO W/F and hierarchy using Svc ref concept to be discussed beyond R6.
• (5) ORCHESTRATION - documentation what will ONAP do wr.t. slice orchestration
• (6) MODELING - Discussing Modeling aspects, how to represent CSI, NSSI, NSSMF etc how to implement in SO how to communicate w/ external domain NSSMF.
• (7) VID - Discussion: Milind Jalwadi (Unlicensed)
  • JSON based screens for VID, Is there a slicing GUI that could be re-used.
  • would want to upstream that NSST NSSD
  • Part of the Network Slicing Use Case.

Presentation/slides at: NETWORK SLICING PoC in R6 Frankfurt (Obsolete)

13 Feb 2020 - Development is proceeding. Start R7 release in next couple of weeks. Next week there will be presentation on requirements for R7.

R4 in 3GPP 28.541 - implemented as part properties of a service. didn't create separate TOSCA type for sliceprofile. Plan to introduce new serivce for serivce & slice profile properties in 3GPP those are recent doc updated in january. introduced many new properties from GSP. You've modeling team presentations were made, platform updated w/ network slicing.

Update on slicing proposal. SO/Seshu presented.

Multiple functional requirements/Use Cases. Recursive orchestration of nested services. Didn't want independent W/F for flows but try to leverage/reuse work. Presented the End to End U/C with macro-view for E2E slice. and components impacted. Right now impact will be on SO, OOF, Policy, SDC and AAI. What controller will be used for managing slices? Focusing on design aspects and instantiation and activation. Put up logical E2E slice. Target simple VNFs. Focus to create VNF vs reconfiguring a VNF? Slice segments are going to be both dedicated/shared. Started with discovering existing resources; assume segments created with VNF/PNFs in inventory & discoverable. Spinup new slice instances.

02 Jan 2020:

• (1) ROADMAP - Proceeding with detail, developments for roadmap beyond R6.
• (2) API - defining API in progress.
• (3) PoC - Prototype of PoC from Orange focusing on VNF-portion.
• (4) SO - Implementation in SO W/F and hierarchy using Svc ref concept to be discussed beyond R6.
• (5) ORCHESTRATION - documentation what will ONAP do wr.t. slice orchestration
• (6) MODELING - Discussing Modeling aspects, how to represent CSI, NSSI, NSSMF etc how to implement in SO how to communicate w/ external domain NSSMF.
• (7) VID - Discussion: Milind Jalwadi (Unlicensed)
  • JSON based screens for VID, Is there a slicing GUI that could be re-used.
  • would want to upstream that NSST NSSD
  • Part of the Network Slicing Use Case.

Presentation/slides at: NETWORK SLICING PoC in R6 Frankfurt (Obsolete)

13 Feb 2020 - Development is proceeding. Start R7 release in next couple of weeks. Next week there will be presentation on requirements for R7.

R4 in 3GPP 28.541 - implemented as part properties of a service. didn't create separate TOSCA type for sliceprofile. Plan to introduce new serivce for serivce & slice profile properties in 3GPP those are recent doc updated in january. introduced many new properties from GSP. You've modeling team presentations were made, platform updated w/ network slicing.

•  Read the Docs entry https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_usecases.html navigate to USER GUIDES > VERIFIED USE CASES.

Borislav Glozman

Shankar PN

Swaminathan Seetharaman

LIN MENG

• /submodules/integration.git/docs/docs_usecases.html  navigate to USER GUIDES > VERIFIED USE CASES.
•  Architecture S/C presentations 26 May 2020 
•  A&AI team feels there is more than just Schema changes. Impacts to mS to extract fields from SDC.

Vimal Begwani

marge.hillis

Dongho Kim

Trying to settle on scope of the Use Case. List of many possible contributions that will take more than one release to complete. Impacts for items to be added to wiki (analysis).

Prioritize the work items what we could propose to accomplish.

CM Notify as a new domain has been accepted on the DCAE S/C today Oct 24 2019.

Dongho Kim  will be creating the test/integration page.

21 Nov 2019 - A1 & O1 test integration pages have been added & links. DongHo Kim leading the Integration

02 Jan 2020 Sandeep code was merged w/ SDN-C branch. Current container has the latest code. Continuing to test. In AT&T lab now being tested

• INTEGRATION - .
  
• VES Spec updates -  VES document has been updated. Version 7.2 for R7 will start next release. Trevor created new Split. Processing feedback. Planning Kick off VES 7.2 review. Weekly meetings. VES spec integrated into VNFREQTS Project and using the VNFREQTS Jira project creating tickets for different topics. First step in R7 create baseline 7.2 version (copy of 7.1.1), larger change in review to move some part OUT of VES into VNFREQTS. Some text not about protocol but requirements. Identified overlap between VES & VNFREQTS cleaned up so don't have info in multiple places.
  
• Read the Docs entry https://onap.readthedocs.io/en/latest/submodules/integration.git

•  Architecture S/C presentations 26 May 2020 

•  A&AI team feels there is more than just Schema changes. Impacts to mS to extract fields from SDC.

Vimal Begwani

marge.hillis

Dongho Kim

Trying to settle on scope of the Use Case. List of many possible contributions that will take more than one release to complete. Impacts for items to be added to wiki (analysis).

Prioritize the work items what we could propose to accomplish.

CM Notify as a new domain has been accepted on the DCAE S/C today Oct 24 2019.

Dongho Kim  will be creating the test/integration page.

21 Nov 2019 - A1 & O1 test integration pages have been added & links. DongHo Kim leading the Integration

02 Jan 2020 Sandeep code was merged w/ SDN-C branch. Current container has the latest code. Continuing to test. In AT&T lab now being tested

• INTEGRATION - .
  
• VES Spec updates -  VES document has been updated. Version 7.2 for R7 will start next release. Trevor created new Split. Processing feedback. Planning Kick off VES 7.2 review. Weekly meetings. VES spec integrated into VNFREQTS Project and using the VNFREQTS Jira project creating tickets for different topics. First step in R7 create baseline 7.2 version (copy of 7.1.1), larger change in review to move some part OUT of VES into VNFREQTS. Some text not about protocol but requirements. Identified overlap between VES & VNFREQTS cleaned up so don't have info in multiple places.
  
• Read the Docs entry https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_usecases.html navigate to USER GUIDES > VERIFIED USE CASES
  
• DCAE Presentation → Met with DCAE. Need to show Vijay revised (less complex flow). Back off on Schema broker. Need to represent at Architecture S/C

09 Jan 2020 From SDN-R when we send config change align to NetConf Yang model avail. whatever yang model used, want config DB schema to be aligned w/ yang model to keep model driven. wanted Yang Models from ORAN if possible. In license catch-22. Some yang models for RAN on ORAN website due to licensing issues from Martin Skorupski took 3GPP model converted to files to compile. Issue w/ ORAN getting ok from 3GPP that it is a valid rep of 3GPP model. Option (1) use previous yang model, or (2) switch to ORAN model if available immediately. yang to SQL schema. Only need some parts of the model for SON project. Currently MariaDB continue to use. Piotr, Marek, et al. If there are useful file wo/ IPR issues, should be a way to use interim files.

Modeling Cell. OOF/SON/PCI & Network Slicing will be discussed at C&PS cell 08 May 2020 

5G U/C Team

Andy Mayer

Scott Blandford

Use Case Template -

Ben talked w/ Andy Mayer U/CR call Oct 23. He said he is preparing the page, and would present here at the 5G U/C S/C call.

REQUIREMENTS SUBCOMMITTEE - requirements sub-group / not bring use cases any more, refer to them as requirements. / proposed change talk less about architecture in requirements mtgs & reviews. more clear split between req & arch discussion.   / Alla Goldberg changed U/C S/C to Requirements S/C. Security and ctl loop req will be discussed in those S/C; other things should go to Req S/C.

Monday - 03 Feb 2020 - what input for Req review; should not go into realization aspects should be moved out of req review. What type of info & how much info at M0. when just reviewing proposed req. Andy has said Proposed Functional Template for Use Cases this is ready to go live.

1. New Use Case Template:  Andy Mayer presented on new additions to Use Case Template: Use Case Tracking Template proposed for R7. If a U/C is extending from a Prior Release should we convert to new Template, or can we maintain. Use cases should to link to new req in the proposals.

5G U/C teams

Present on the Req S/C 25 May 2020 

Schedule presentation on Arch S/C

Needs REQ-Jira

R7 - Per artifact package security for the onboarding package. ETSI SOL004. Verified in VNF-SDK/VVP

R7 - dynamic schemas updates to the RTCfgDB with Yang model files.

Presented PNF Pre-onboarding at Arch S/C 05 May 2020 - (accepted/approved by Arch S/C)

Reviewed with SO team.

Preparing for DDF. will discuss with Change Management team, might be presenting. R6 in progress.

Should be able to update/merge all Jiras by M4. No big risk. Integration RC0-RC2

Architecture S/C proposal - GO 12 May 2020 

Oskar Malm

held meeting for discussing Civic Address elements & Geolocation information w/ the modeling S/C

PnP - PNFD/SDC AID/AAI Schema Modeling - Discussion Jan 2, 2020

Eventually will the PNFregistration VES event for PnP (R7).

SO presentations related to Building block definitions. Dependency to REQ-140. Option #2 new arch. is agreed. Option #1 continue w/ old. Use Case Realization Call: February 19, 2020

•  Benjamin Cheung Find out if - will we support >1 PNF instance / template per service 5G Service (Run-Time). Plan to test/Integration how to do the instantiation. Use CLI to do instantition, limitation in SO workflow limitation in controller, PRH.

Presented PNF PnP at Arch S/C 05 May 2020 - (accepted/approved by Arch S/C)

Benjamin Cheung

WIKI: 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt

CDS Data dictionary - Define attribute, in that entry tells you how to get that value. Yuriy Malakov

If you needed the IP@ you can go that entry → points to the REST call. Used for instantiation and configuration management. Model driven ONAP. Modeling Concepts

3GPP TS28.541/TS28.540 - 5G NRM Network Resource Model analysis (spreadsheet). Looking parameters introduce

Classify parameters - CDS Data Dictionary, A&AI, RunTime Cfg DB.

Presentations - Modeling S/C, U/C S/C, U/C Realization, 5G U/C.

Modeling S/C - Experimental info model introduced (standards driven)

A&AI - classification of A&AI parameters. Commission (might need at installation & commissioning) → A&AI.

Onboarding - Onboarding, PNF PNFregistration, CMNotify (VES events), Pre-defined "load 3GPP model"

Information Flows - Where these might be used.

ORAN Standards - Usage of the 3GPP TS28.541 in ORAN Standards. Might want to consider which 3GPP parameters ORAN cares about & when. They might an opinion of when to incorporate parameters.

Presentation at Use Case Realization call 29 Jan 2020 

Use Case Realization Call: January 29, 2020 - next step to present to Modeling S/C.

Presented 5G Svc Modeling at Architecture S/C 05 May 2020  (accepted/approved by Arch S/C)

Pawel Baniewski

Hampus Tjader

M2/M3 CMPv2 & AAF status - CMPv2 GREEN at M2/M3 right now. 

09 Jan 2020 From SDN-R when we send config change align to NetConf Yang model avail. whatever yang model used, want config DB schema to be aligned w/ yang model to keep model driven. wanted Yang Models from ORAN if possible. In license catch-22. Some yang models for RAN on ORAN website due to licensing issues from Martin Skorupski took 3GPP model converted to files to compile. Issue w/ ORAN getting ok from 3GPP that it is a valid rep of 3GPP model. Option (1) use previous yang model, or (2) switch to ORAN model if available immediately. yang to SQL schema. Only need some parts of the model for SON project. Currently MariaDB continue to use. Piotr, Marek, et al. If there are useful file wo/ IPR issues, should be a way to use interim files.

Modeling Cell. OOF/SON/PCI & Network Slicing will be discussed at C&PS cell 08 May 2020 

5G U/C Team

Andy Mayer

Scott Blandford

Use Case Template -

Ben talked w/ Andy Mayer U/CR call Oct 23. He said he is preparing the page, and would present here at the 5G U/C S/C call.

REQUIREMENTS SUBCOMMITTEE - requirements sub-group / not bring use cases any more, refer to them as requirements. / proposed change talk less about architecture in requirements mtgs & reviews. more clear split between req & arch discussion.   / Alla Goldberg changed U/C S/C to Requirements S/C. Security and ctl loop req will be discussed in those S/C; other things should go to Req S/C.

Monday - 03 Feb 2020 - what input for Req review; should not go into realization aspects should be moved out of req review. What type of info & how much info at M0. when just reviewing proposed req. Andy has said Proposed Functional Template for Use Cases this is ready to go live.

1. New Use Case Template:  Andy Mayer presented on new additions to Use Case Template: Use Case Tracking Template proposed for R7. If a U/C is extending from a Prior Release should we convert to new Template, or can we maintain. Use cases should to link to new req in the proposals.
2. Generic Information Model Template -If you think you have modeling impact fill out the following template and include in your project Wiki Page: Generic Information Element Template

5G U/C teams

Present on the Req S/C 25 May 2020 

Schedule presentation on Arch S/C. Chaker rescheduled for July 14.

Needs REQ-Jira ... wangyaoguang 

R7 - Per artifact package security for the onboarding package. ETSI SOL004. Verified in VNF-SDK/VVP

R7 - dynamic schemas updates to the RTCfgDB with Yang model files.

Presented PNF Pre-onboarding at Arch S/C 05 May 2020 - (accepted/approved by Arch S/C)

Reviewed with SO team.

Preparing for DDF. will discuss with Change Management team, might be presenting. R6 in progress.

Should be able to update/merge all Jiras by M4. No big risk. Integration RC0-RC2

Architecture S/C proposal - GO 12 May 2020 

Oskar Malm

Preparing presentations at DDF in Prague in DDF for R6 BulkPM functionality in Jan 2020.

held meeting for discussing Civic Address elements & Geolocation information w/ the modeling S/C

PnP - PNFD/SDC AID/AAI Schema Modeling - Discussion Jan 2, 2020

Eventually will the PNFregistration VES event for PnP (R7).

SO presentations related to Building block definitions. Dependency to REQ-140. Option #2 new arch. is agreed. Option #1 continue w/ old. Use Case Realization Call: February 19, 2020

•  Benjamin Cheung Find out if - will we support >1 PNF instance / template per service 5G Service (Run-Time). Plan to test/Integration how to do the instantiation. Use CLI to do instantition, limitation in SO workflow limitation in controller, PRH.

Presented PNF PnP at Arch S/C 05 May 2020 - (accepted/approved by Arch S/C)

Benjamin Cheung

WIKI: 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt

CDS Data dictionary - Define attribute, in that entry tells you how to get that value. Yuriy Malakov

If you needed the IP@ you can go that entry → points to the REST call. Used for instantiation and configuration management. Model driven ONAP. Modeling Concepts

3GPP TS28.541/TS28.540 - 5G NRM Network Resource Model analysis (spreadsheet). Looking parameters introduce

Classify parameters - CDS Data Dictionary, A&AI, RunTime Cfg DB.

Presentations - Modeling S/C, U/C S/C, U/C Realization, 5G U/C.

Modeling S/C - Experimental info model introduced (standards driven)

A&AI - classification of A&AI parameters. Commission (might need at installation & commissioning) → A&AI.

Onboarding - Onboarding, PNF PNFregistration, CMNotify (VES events), Pre-defined "load 3GPP model"

Information Flows - Where these might be used.

ORAN Standards - Usage of the 3GPP TS28.541 in ORAN Standards. Might want to consider which 3GPP parameters ORAN cares about & when. They might an opinion of when to incorporate parameters.

Presentation at Use Case Realization call 29 Jan 2020 

Use Case Realization Call: January 29, 2020 - next step to present to Modeling S/C.

Presented 5G Svc Modeling at Architecture S/C 05 May 2020  (accepted/approved by Arch S/C)

Pawel Baniewski

Hampus Tjader

M2/M3 CMPv2 & AAF status - CMPv2 GREEN at M2/M3 right now. 

1. REPO Avail - Nokia has created a repo, discussing architecture now.
2. Access - Confirmed, we can access the Repo.
3. Deliveries - Nokia planning to deliver the CertService (accept request from client), CertService Client (init container w/ ONAP apps), and integration with external CMP v2 service.
4. Integration to Border Components - Integration with ONAP modules, DCAE/VES, SDNC, DCAE/DFC very likely to be post-posted to R7. High Risk The ONAP "bordering" components. Consequences - in scenario where you int ONAP w/ external function won't be able to dist cert generated in external Cert. Authority (CA) within ONAP; thus would still be able to integrate a NF to ONAP but would need to distribute manually bring the certs to ONAP. The Automation of distribution would be missing. The NFs contact the CAs to get certs. Integrate ONAP w/ CMPv2 w/ CertSvc to same Ext. CA. Integrate the xNF gets the cert to Ext. CA. ONAP gets matching trust anchors from same Ext. CA, loaded to an ONAP component. CertSvc bought back dist. within ONAP volume where cert is stored & consumed by ONAP component. 3GPP requires/originated. Consumes maximum of what 3GPP has.
5. Slides -

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key ONAPARC-553

6. Integration - Separate integration efforts. 140 is the common part in AAF, including client component that can be reused, there is integration work which have separate requirements. This creates a dependency on those other requirements, being delivered with enough time to do integration.
7. Plug and Play, Bulk PM, NetConf - CMPv2 PnP got descoped, secure Bulk PM is descoped, NetConf is proceeding see: Frankfurt Release Requirements
8. REQ-76 - If we manage to complete the integration into SDN-C (REQ-76) additional integration related to that.

   Jira Legacy
   server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key ONAPARC-553

9. Integration - Separate integration efforts. 140 is the common part in AAF, including client component that can be reused, there is integration work which have separate requirements. This creates a dependency on those other requirements, being delivered with enough time to do integration.
10. Plug and Play, Bulk PM, NetConf - CMPv2 PnP got descoped, secure Bulk PM is descoped, NetConf is proceeding see: Frankfurt Release Requirements
11. REQ-76 - If we manage to complete the integration into SDN-C (REQ-76) additional integration related to that.

    Jira Legacy
    server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-76

12. DEMO - Plugfest in June 2020 it might be nice to demo something.

Presented CMPv2 at Architecture S/C 05 May 2020 (accepted/approved by Arch S/C)

1. REQ-76

2. DEMO - Plugfest in June 2020 it might be nice to demo something.

Presented CMPv2 at Architecture S/C 05 May 2020 (accepted/approved by Arch S/C)

07 May 2020 

zoom_0.mp4

audio_only.m4a

14 May 2020 

zoom_0.mp4

audio_only.m4a

21 May 2020 

04 Jun 2020 

zoom_5GUCTeam_060420.mp4

audio_only_5GUCTeam_060420.m4a

11 Jun 2020 

zoom_202006Jn115G.mp4

audio_only202006Jn115G.m4a

18 Jun 2020 

25 Jun 2020 

02 Jul 2020 

zoom_05GUC_202007Jy02.mp4

audio_only5GUC_202007Jy02.m4a

09 Jul 2020 

zoom_202007Jy09.mp4

audio_only202007Jy09.m4a

23 Jul 2020 

zoom_202007Jy23.mp4

audio_only202007Jy23.m4a

03 Sep 2020 

5GUseCaseMeeting 202009Sp03.mp4

5GUseCaseMeeting 202009Sp03.m4a