Skip to end of metadata
Go to start of metadata

Following are child pages (currently showing up to 2 levels)

5G Radio Network, Slicing, and Optimization Requirements Version 2


5G Use Case - Casablanca Requirements for F2F discussion - in LA on March 26, 2018





Attachments:

  File Modified
Microsoft Word Document 5G_RAN_UseCase_for_R2_v3.docx Aug 10, 2017 by Vimal Begwani
Microsoft Word Document 5G_RAN_UseCase_for_R2_v3-reflections-v3.docx Aug 10, 2017 by Vimal Begwani
Microsoft Word Document 5G_RAN_UseCase_for_R2_v4.docx Aug 10, 2017 by Vimal Begwani
Microsoft Word Document 5G_RAN_UseCase_v4.docx Aug 14, 2017 by Shekar Sundaramurthy
Microsoft Word Document 5G_RAN_UseCase_v4-noMarks.docx Aug 14, 2017 by Shekar Sundaramurthy
Microsoft Powerpoint Presentation UC-5G-status-081417.pptx Aug 14, 2017 by Shekar Sundaramurthy
Microsoft Word Document 5G_RAN_UseCase_v4-Ciena.docx Aug 15, 2017 by Raghu Ranganathan
Microsoft Word Document 5G_RAN_UseCase__v4_EricssonSuggestions.docx Some suggested clarifications of use cases Aug 16, 2017 by Peter Loborg
Microsoft Word Document Members-081117.docx Use Case Discussion Group Members Aug 17, 2017 by Shekar Sundaramurthy
Microsoft Powerpoint Presentation UC-5G-agenda-081717.pptx Agenda-081717 Aug 17, 2017 by Shekar Sundaramurthy
Microsoft Word Document Members-081817.docx Members-081817 Aug 18, 2017 by Shekar Sundaramurthy
Microsoft Word Document 5G_RAN_UseCase_v5.docx Version as of 081717 Aug 21, 2017 by Shekar Sundaramurthy
Microsoft Word Document 5G_RAN_UseCase_v5_Cisco-optimization.docx Aug 27, 2017 by Vladimir Yanover
Microsoft Word Document 5G_RAN_UseCase_v5-opt-frwk-multi-cloud-v2-ib.docx FurtherUpdatesOnOptimization-SP-RK Aug 29, 2017 by Shekar Sundaramurthy
Microsoft Word Document 5G_RAN_UseCase_v5-opt-frwk-multi-cloud-v2-ib-sarat.docx FurtherUpdatesOnOptimization-SP-RK-Sarat Aug 31, 2017 by Shekar Sundaramurthy
Microsoft Word Document 5G_RAN_UseCase__v4_B_Ericsson.docx Aug 31, 2017 by Peter Loborg
Microsoft Word Document 5G_RAN_onboarding_Flow.docx Sep 06, 2017 by Vimal Begwani
Microsoft Word Document Arch_Answers.docx Sep 06, 2017 by Vimal Begwani
Microsoft Word Document 5G_RAN_UseCase_v5-opt-frwk-multi-cloud -- ib2-rk-sp.docx Further updates on RAN optimization Sep 12, 2017 by Ioannis Broustis
Microsoft Powerpoint Presentation 5G RAN Slicinfg and Optimization Framework v5.pptx Sep 26, 2017 by Vimal Begwani
Microsoft Powerpoint Presentation ControllerScope_v3.pptx Controller scope in 5G use case - reviewed by Vimal Begwani Nov 02, 2017 by Shekar Sundaramurthy
Microsoft Word Document ONAP-RAN-use-cases-optimization-logging-coordination-contributions-Amdocs.docx Nov 30, 2017 by Karpura Suryadevara
Microsoft Powerpoint Presentation 5GucOV_V2.pptx Dec 07, 2017 by Vimal Begwani
Microsoft Powerpoint Presentation Infrastructure controller to support 5G MEC and E2E Network Slicing- V1.0 Dec'17.pptx PNF support for 5G use case Dec 11, 2017 by Vivien Yang
PDF File PNF and Hybrid Services Support in ONAP.pdf Dec 14, 2017 by Oskar Malm
PDF File PNF and Hybrid Services Support in ONAP 1.1.pdf Jan 10, 2018 by Oskar Malm
Microsoft Powerpoint Presentation PNFOnboarding_ONAPPlugnPlay_11Jan2018v4.pptx PNFOnboarding-ONAPPlugandPlay_11Jan2018v4 Jan 12, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFOnboarding_ONAPPlugnPlay_14Jan2018v6.pptx PNF Onboarding ONAP Plug and Play with Descriptions v6 14-Jan-2018 Jan 15, 2018 by Benjamin Cheung
PDF File PNFOnboarding_ONAPPlugnPlay_16Jan2018v7a.pdf PNF Onboarding ONAP Plug and Play with Descriptions v7a 16-Jan-2018 Jan 17, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFOnboarding_ONAPPlugnPlay_17Jan2018v8.pptx Updated PNF Onboarding ONAP Plug and Play with notes from meeting held v8 17-Jan-2018 Jan 17, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation ONAPNetworkSlicingv3_25Jan2018.pptx ONAP & Network Slicing 24 Jan 2018 v3 Jan 26, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFOnboarding_ONAPPlugnPlay_04Feb2018v11.pptx PNF Onboarding v11 ONAP Plug and Play updated Jan29-Feb2 SDC-SO Feb 05, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFOnboarding_ONAPPlugnPlay_05Feb2018v11.pptx PNF Onboarding v11a ONAP Plug and Play Feb5 (meeting updates) Feb 05, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFOnboarding_ONAPPlugnPlay_06Feb2018v12.pptx PNF Onboarding v11 ONAP Plug and Play Feb 6 (presentation updates) Feb 06, 2018 by Benjamin Cheung
PDF File PNFPlugnPlay_09Feb2018v13.pdf PNF Plug and Play (Feb 9, 2018) PDF M2 Release 2 Gate Discussion Feb 09, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlay_09Feb2018v13.pptx PNF Plug and Play (Feb 9, 2018) PPT M2 Release 2 Gate Discussion Feb 09, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlay_12Feb2018v14.pptx PNF Plug & Play (Feb 12, 2018) PPT M2 Release 2 Gate Discussion Cot'd Feb 12, 2018 by Benjamin Cheung
PDF File PNFPlugnPlay_12Feb2018v14.pdf PNF Plug & Play (Feb 12, 2018) PDF M2 Release 2 Gate Discussion Cot'd Feb 12, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlay_19Feb2018v14.pptx PNF Plug & Play (Feb 19, 2018) PPT M2/R2 Project Impacts Feb 19, 2018 by Benjamin Cheung
PDF File PNFPlugnPlay_19Feb2018v14.pdf PNF Plug & Play (Feb 19, 2018) PDF M2/R2 Project Impacts Feb 19, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlay_23Feb2018v15.pptx PNF Plug & Play Use Case v15 (Feb 23, 2018) PPT Feb 24, 2018 by Benjamin Cheung
PDF File PNFPlugnPlay_23Feb2018v15.pdf PNF Plug & Play Use Case v15 (Feb 23, 2018) PDF Feb 24, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation 5GucCasablanca-031618.pptx Mar 16, 2018 by Vimal Begwani
Microsoft Powerpoint Presentation PNFPlugnPlay_16Mar2018v16.pptx PNF Plug & Play Use Case v16 (Mar 16, 2018) PPT Mar 17, 2018 by Benjamin Cheung
PDF File PNFPlugnPlay_16Mar2018v16.pdf PNF Plug & Play Use Case v16 (Mar 16, 2018) PDF Mar 17, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation Cisco proposed changes 5GucCasablanca-031618.pptx Mar 18, 2018 by Vladimir Yanover
Microsoft Powerpoint Presentation 5GucCasablanca-03222018.pptx Casablana Reqmts - updated Mar 22, 2018 by Shekar Sundaramurthy
PNG File service2slice.png Mar 22, 2018 by Ulas Kozat
Microsoft Powerpoint Presentation 5GucCasablanca-03222018v2.pptx Casablanca Requirements - updated 03/23/18 Mar 23, 2018 by Shekar Sundaramurthy
Microsoft Powerpoint Presentation 5GucCasablanca-03222018v3_Cisco.pptx Mar 26, 2018 by Vladimir Yanover
Microsoft Powerpoint Presentation 5GucCasablanca-03222018v3.pptx Incorporated sugegsted edits from Ramki & Raghu Mar 29, 2018 by Shekar Sundaramurthy
PDF File PNFPlugnPlayBeijing_29Mar2018v17.pdf PNF Plug & Play Use Case (Beijing) w/ Integration Showcasing Mar 29, 2018 Mar 29, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlay_enhancement_in_Step1and4.pptx Mar 30, 2018 by Li Xiang
Microsoft Powerpoint Presentation 5GucCasablanca-03222018v4.pptx Apr 01, 2018 by Vladimir Yanover
Microsoft Powerpoint Presentation 5GCUC-PNFDeployment_Casablanca_05Apr2018v3.pptx PNF Deployment UC Casablanca Apr 5, 2018 v3 (PPT) Apr 06, 2018 by Benjamin Cheung
PDF File 5GCUC-PNFDeployment_Casablanca_05Apr2018v3.pdf PNF Deployment UC Casablanca Apr 5, 2018 v3 (PDF) Apr 06, 2018 by Benjamin Cheung
PDF File 5G RAN Deployment - Casablanca - Ericsson 04122018v1b.pdf Apr 13, 2018 by Oskar Malm
Microsoft Excel Spreadsheet 5G-NFD-funcReqmts.xlsx 5G Deployment - Functional Requirements (1st Draft) Apr 18, 2018 by Shekar Sundaramurthy
PDF File 5G RAN Deployment - Casablanca - Ericsson 04192018v2.pdf Apr 19, 2018 by Oskar Malm
PDF File Optimization Use Case .pdf 5G RAN Deployment Optimization Use Case Nokia 04/19/2018 Apr 20, 2018 by Marge Hillis
Microsoft Powerpoint Presentation 5Guc-RAN Deployment (SWCfg_Mgmt)-Casablanca-Huawei 04282018v3.pptx Apr 29, 2018 by yaoguang wang
PDF File PNFPlugnPlayCasablanca_03May2018v2.pdf 5G PNF Plug and Play Use Case Casablanca 03-May-2018 v2 pdf May 04, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlayCasablanca_03May2018v2.pptx 5G PNF Plug and Play Use Case Casablanca 03-May-2018 v2 pptx May 04, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation 5GCUC-PNFDeployment_Casablanca_07May2018v5.pptx PNF Deployment Use Cases for Casablanca May 07 2018 (ppt) May 07, 2018 by Benjamin Cheung
PDF File 5GCUC-PNFDeployment_Casablanca_07May2018v5.pdf PNF Deployment Use Cases for Casablanca May 07 2018 (PDF) May 07, 2018 by Benjamin Cheung
PDF File 5GCUC-PNFDeploymentCasabSummary_07May2018v1.pdf PNF Deployment Use Cases for Casablanca SUMMARY May 07 2018 (PDF) May 07, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation 5Guc-RAN Operations (SW upgrade)-Casablanca-Huawei&CMCC 05112018v1.pptx May 11, 2018 by yaoguang wang
Microsoft Powerpoint Presentation PNFPlugnPlay_a_potential_PNF_Template05102018CMCC&HUAWEI.pptx May 14, 2018 by Li Xiang
Microsoft Powerpoint Presentation PNFPlugnPlayCasablanca_16May2018v3.pptx PNF Deployment Use Case for Casblanca V3 May 16 2018 (PPT) May 16, 2018 by Benjamin Cheung
PDF File PNFPlugnPlayCasablanca_16May2018v3.pdf PNF Deployment Use Case for Casblanca V3 May 16 2018 (PDF) May 16, 2018 by Benjamin Cheung
PDF File 5GUCCasablancaSummary-051018.pdf 5G Use Cases for Casablanca (Summary) May 10 2018 (PDF) May 18, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation 5GUCCasablancaSummary-051018.pptx 5G Use Cases for Casablanca (Summary) May 10 2018 (PPT) May 18, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation 5GUCCasablancaSummary-051018v2.pptx May 18, 2018 by Ulas Kozat
PDF File 5GCUC-PNFDeployment_Casablanca_22May2018v6.pdf PNF Deployment Use Cases for Casablanca May 22 2018 v6 (PDF) May 22, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation 5GUCCasablancaSummary-051018v3.pptx Jun 04, 2018 by Vladimir Yanover
PDF File Real Time PM--HV Event proposal to DCAE 5G Use Case Presentation.pdf Real Time PM-HV event proposal to enhance DCAE Jun 13, 2018 by Marge Hillis
Text File VES_PerformanceMeasurementFields.proto.txt Real Time PM - HV Event - VES Performance Measurements Fields (Proto File) [Txt] Jun 21, 2018 by Benjamin Cheung
Text File VES_Event.proto.txt Real Time PM - HV Event - VES_Event (Proto File) [Txt] Jun 21, 2018 by Benjamin Cheung
PDF File PNFPlugnPlayCasablanca_26Jun2018v5.pdf 5G PNF Plug and Play Use Case Casablanca June 26 2018 v6 (PDF) Jun 26, 2018 by Benjamin Cheung
PDF File ONAPCasablancaDevForum-SummaryBC27Jun2018v2.pdf ONAP Casablanca Developers Forum Conference Summary BC27Jun2018 v2 (PDF) Jun 27, 2018 by Benjamin Cheung
PDF File 5GucCasablancaSummary-06292018.pdf 5G Use Case Summary for Casablanca (June 29, 2018) [PDF] Jun 29, 2018 by Benjamin Cheung
PDF File PNFPlugnPlayCasablanca_03Jul2018v6.pdf 5G PNF Plug and Play Use Case Casablanca July 3 2018 v6 (PDF) Jul 04, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlayCasablanca_03Jul2018v6.pptx 5G PNF Plug and Play Use Case Casablanca July 3 2018 v6 (PPT) Jul 04, 2018 by Benjamin Cheung
PDF File PNFPlugnPlayCasablanca_16Jul2018v7.pdf 5G PNF Plug and Play Use Case Casablanca July 16 2018 v7 (PDF) Jul 16, 2018 by Benjamin Cheung
PDF File PNFPlugnPlayCasablanca_25Jul2018v7.pdf 5G PNF Plug and Play Use Case Casablanca July 25 2018 v7 (PDF) Jul 25, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlayCasablanca_25Jul2018v7.pptx 5G PNF Plug and Play Use Case Casablanca July 25 2018 v7 (PPT) Jul 25, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation OOF_PCI_proposal_v1_20180725.pptx Jul 26, 2018 by N. K. Shankaranarayanan
Microsoft Powerpoint Presentation OOF_PCI_proposal_v2_20180730.pptx Aug 09, 2018 by N. K. Shankaranarayanan
PDF File PNFPlugnPlayCasablanca_09Aug2018v8.pdf 5G PNF Plug and Play Use Case Casablanca Aug 09 2018 v8 (PDF) Aug 09, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation PNFPlugnPlayCasablanca_09Aug2018v8.pptx 5G PNF Plug and Play Use Case Casablanca Aug 09 2018 v8 (PPT) Aug 09, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation OOF_PCI_Microservice_RANSimulator_Aug10_2018.pptx Aug 16, 2018 by N. K. Shankaranarayanan
Microsoft Powerpoint Presentation Slicing_in_3GPP_Rel15.pptx Aug 16, 2018 by Ulas Kozat
PDF File PNFPlugnPlayCasablanca_28Aug2018v8.pdf 5G UC Plug and Play Casablanca 28-Aug-2018 (PDF) Aug 29, 2018 by Benjamin Cheung
Microsoft Powerpoint Presentation FM Dictionary via VES Registration.pptx Sep 14, 2018 by Marge Hillis
PDF File PNFPlugnPlayCasablanca_14Sep2018v8.pdf 5G UC Plug and Play Casablanca 14-Sep-2018 (PDF) Sep 17, 2018 by Benjamin Cheung
PDF File 5GUseCaseMeeting_BCMH01Nov2018.pdf 5G Use Case Meeting Notes / November 01, 2018 (PDF) [Ben C & Marge H] Nov 01, 2018 by Benjamin Cheung


  • No labels

86 Comments

  1. Folks, Please use the "LATEST" document (without change marks) for providing your inputs (comments, suggestions, contributions etc.); this would allow the reader to attribute suggestions/changes appropriately.

  2. The next review of the document is scheduled for August 17, 11-12 EDT - See zoom info below.

    5G Use Case Discussion

    When

    Thu Aug 17, 2017 8am – 9am Pacific   Time

    Where

    https://zoom.us/j/926506738 (map)

    ONAP Meeting 3 is inviting you to a scheduled Zoom meeting.

    Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/926506738

    Or iPhone one-tap (US Toll): +14086380968,,926506738# or +16465588656,,926506738#

    Or Telephone:
    Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
    +1 855 880 1246 (US Toll Free)
    +1 877 369 0926 (US Toll Free)
    Meeting ID: 926 506 738
    International numbers available: https://zoom.us/zoomconference?m=fVEW3lbNLOBQ0oV57R-B2aWXKdzg-VTA

  3. In today's status readout to the Use Case sub-committee, there were some comments (from Alla Goldner, Yoav Kluger & Alexander Vul et al) suggesting that, in addition to capturing the architectural impacts in the document, we post the architectural requirements identified in support of the use case under Architecture Requirements for R2 use cases section in the wiki.

  4. Hi, Shekar

    What is the procedure for modification of the document?  Make changes directly in the version N and upload as the version N+1? Submit changes in a separate contribution?

    Thanks

    Vladimir

  5. Hi Vladimir

    As Ciena & Ericsson have done above, please take the "5G_RAN_UseCase_v4-noMarks.docx" version and mark with your suggested edits/changes - once the team discusses the changes on the call, we can include the changes in the subsequent version. Hope that helps.

    Regards,

    Shekar Sundaramurthy

  6. Hi Shekar,

    What happened with the comments and suggestions by Ciena and Ericsson on v4, they seem to have disapeared in the v5 document although they are mentioned in the revision history of the document?

    Br, Peter

  7. Peter, I had put in a placeholder with a comment indicating that it is part of the planned discussion for Aug 24 (tomorrow) - I was under the assumption you were going to continue to complete the pre/post items based on comments received - your original/initial suggested text are still in the v4 doc - please let me know if this clarifies - didn't mean to confuse folks.

    1. Ok, I missed that one. Sorry. I'll see what we can add during the day.

      ...we will not have anything new to upload, but we need to discuss the following in order to proceed this work:

      • re-iterate the discussin about proper actors (I failed to make something usefull out from my notes from the last meeting...)
      •  discussion about the slicing concept - what do we really mean, what form of separation (or prioritisation or sharing) do we want to discuss, and how much CN services (creation/allocation) should be included?

      Br/Peter 

  8. During the ONAP use case call last week, there was a suggestion to use “standard’ or ‘already established’ names/titles for the use case actors – I was provided an ONAP SDC contact who may be able to help with that (Michael Lando) – however, I haven’t had any feedback about established names for use case ‘actors’.

    For now, to keep the exercise simple and focused, my suggestion is to use the following 3 actors:

    VNF/PNF Provider:                         The supplier of the network/service function (and it’s underlying infrastructure) – e.g. VNF/PNF vendors

    ONAP Service Designer:               The ONAP designer (user of ONAP design studio) that on-boards the VNF/PNF and defines/models the workflows/analytics/policies/extensions
    for management/automation using the ONAP Design Studio

    Service/Network Operator:                               The ONAP operations user (operator of the realized service managed by ONAP) that processes the various dashboards/reports/logs and responsible for other management functions (change/configuration etc.)

  9. Here are the 3 action items that I took away from today's meeting:

    1)      Ericsson (Peter Loborg et al) to continue with the use case description by adding “pre” and “post” conditions for the first 2 cases

    2)      Vmware and AT&T (Ramki Krishnan & Sarat Puthenpura) to provide similar edits for the expanded optimization case

    3)      A&T (Vimal Begwani) to provide pictorial representation of R1 use case samples (sequence diagrams) to use as reference for depicting these R2 use cases

    Regards,

    Shekar Sundaramurthy

  10. Hello,

    I just uploaded suggestions from Cisco, on the optimization part

    Thanks

    Vladimir

  11. Uploaded document received from Sarat Puthenpura, Ramki Krishnan et al - further updates on the Optimization section

  12. Hello, All

    When/how next version (v6?) will be created? 

    Thanks

    Vladimir

  13. Based on discussion from the 8/31/17 meeting, I created 5 pages (see top of the page) for direct update of the wiki by the respective section contributors - Feel free to upload your word documents (if you choose) to call out specific changes you have made (with markings). I filled in the "Introduction" sub-page and look to the respective section authors to update the other sub-pages. Hope this helps,

    Regards,

    Shekar

  14. Also added a section for "ONAP Optimization Framework (ONAP-OF) and Multi Cloud (ONAP-MC)"

    Regards,

    Shekar

  15. Thanks for incorporation of the contribution by Cisco!

    (I will appreciate adding the name of the company to the list of contributors.)

    Vladimir

  16. Is there any way we could make wiki pages out of those documents? Attaching documents instead of generating wiki pages is really not best practice for ONAP use cases (this is the only one)  and makes it very difficult to find the current version tracking history. 

    Oliver

    1. We started doing that last week, Oliver - See updates at the top of the page.

      Regards,

      Shekar

  17. I don't know if in Wiki, version tracking would be possible at all.

    That said, I agree that we need better the version management. Having some experience, I can propose the process, of course, if the group is interested

    1. >> if in Wiki, version tracking would be possible

      wiki page: click the three dots (...) to the right of 'SHARE'. choose 'Page history' to see previous versions....and even compare between tw

      attachment: click the chevron (>) before file name see prior versions. ...assuming same name.

      • Attachments might be displayed as above (using attachment macro)
      • or,..you can click the three dots to the right of SHARE to get to Attachments.


  18. Thanks, Raghu. Let me ask this.

    We need to

    1. Publish the clean baseline version N

    2. Collect change proposals based on N (with rev. marks)  - sort of branching

    3. Discuss and approve (some of) the proposed changes

    4. Create clean version N+1.

    How this can be done in Wiki? 

    1. not elegant...but some options are (my pref is 1)

      1. one person is 'owner/editor' of page....with round-robin editing (simultaneous doesn't work well)
        1. editor sets/releases 'restrictions' to allow editing by specific person (see under .../restrictions)
        2. prefer inserting comments+alternate text. changes can be viewed via page history/compare.
      2. copy page (see .../copy) to make a child page...each interested person can do this
        1. hopefully, titles have some uniqueness, e.g., "<old title>-RRedit"
        2. edit/save.....but, may become too many and, no elegant way to merge. parent page updates will be separately done.
        3. discussion can be based on comparing 

      ..etc...I don't see talk macro being available. maybe admin can install that to allow commenting inline (without editing)

  19. All,

    Please use the instructions in the attached document to create flow diagrams for each sub-case.

    Vimal Begwani

  20. Dear All,

      I have created the attached response to the set of questions from the Architecture subcommittee regarding our 5G RAN / Slicing / Optimization use case.  Please review and let me know if you have additional comments.


    Regards,

    Vimal

    1. Vimal Begwani ..and all - see page tree at top of page for child wiki page to continue work on this.

  21. Dear Vimal and All,

    > 4.    Do we need to consider enhanced networking features (e.g., underlays)

    > Not applicable

    In the scenario when a network slice is instantiated (or modified), cannot underlays be involved, e.g. in the part of networking resources allocation (re-allocation)?

    Thanks

    Vladimir

  22. All

      I have created a page for "Summary Functional Requirements arising from 5G Use Case" at 

    Summary of Functional Platform Requirements arising from 5G Use Case

    Please review and enhance with your comments/updates.

    Regards,

    Shekar

  23. Hi all! Whom can i reach out to discuss potential collaboration and contribution to 5G use case development?

  24. Dmitriy,

      I just forwarded meeting invitations for our group discussions.


  25. Vimal,

    I did not receive any invitations. Can you please advise where/how the invitations were posted?

    Vladimir Yanover (Cisco)

    1. If you go to the "Community Meetings & Calendar" page

      Community Meetings & Calendar

      The Thursday 11 AM - 12 noon (US ET) slot contains the zoom meeting info for this Use Case group.

      Regards, Shekar

  26. Hi, Vimal

    Should we add one more Sub Case about Transport?

    This is also main part of 5G Network, provide connectivity between Central and Edge Clouds, and also area for Slicing and Optomisation.

    Thanks, Evgeniy.

  27. Shekar,

    Thanks for the ControllerScope_v3 contribution. Now it looks much better.

    Still, I have a couple of comments/questions. I understand that some of the parts mentioned below are not new, but should not we try to be as clear as we can? 

    1. I am not sure what "Disaggregated core" means. At this level of details, there is only one 5G core architecture in 3GPP specified in 23.501 which is not using the term "disaggregated".

    2. The diagrams  show separated CP and UP nodes; seems natural to show also CP and UP connectivity separated

    3. The terminology "Front Haul"/"Mid Haul" does not match that of 3GPP where Fronthaul means link between CU and DU

    4. "5G Base Station" usually means the combination RU + DU + CU-UP + CU-CP.  

    5. Generic VNF Controller is said to provide for network application configuration of various nodes. In this context I wonder why it is marked as L4-L7. Much of configuration (e.g. in RAN) is applied to lower layers. So if it is about what is configured, "L4-L7" must be wrong. If it is about what entities provide configuration, in 3GPP management system is not explicitly associated with any of network layers, so again "L4-L7" is wrong.

    Thanks

    Vladimir


  28. PNF Onboarding (ONAP Plug & Play) Use Case and architectural flow. (Note you should download the slides, the previewer sometimes shows just mathematical symbols in the web-PPT-viewer).

    Best regards, -Ben Cheung

  29. Meeting today (2/15/18) discussed the establishment of a liaison between ONAP and 3GPP - there were 3 volunteers (Anatoly-Nokia, Vladimir Yanover-Cisco, Benjamin Cheung-Nokia) whose names are being referred to the use-case subcommittee chair. If you are interested in adding your name to the volunteer list please reach out to Vimal or Alla.

    Shekar Sundaramurthy

  30. Team,

      As per our discussion yesterday. I have started capturing requirements for Casablanca release to support 5G network deployment and Radio Slice Segment creation.  Please review them and add your comments or suggest changes.  Requirements for optimization and OOF are still under construction.  Marge-Nokia please feel free to add requirements under optimization section.  Sarat-ATT will work on OOF.

    Vimal Begwani

  31. Explanations to the "Cisco proposed changes 5GucCasablanca-031618"

    The purpose of the proposed changes is mostly to align with 3GPP terminology.

    Slide #3

    1. Radio Slice Segment => Radio Network Slice Subnet Instance (3GPP term)
    2. “Focus initially on RAN Slices Using A Simple Model” – not clear what the simple model is. Deleted
    3. “Use complex services (composite, allotted resource, etc.) to manage (model, on-board, create, configure, monitor) the slices” – not clear what “complex” means in this context (nested?). Replaced with “Lifecycle management of Radio Slice Subnet Instances” (that can be nested per 3GPP definition)

     

    Slide #4

    1. The term "Disaggregated core" does not exists in 3GPP – deleted
    2. The role of the (incomplete) list of the 5G Core nodes is not clear – deleted
    3. The term “5G Base Unit” is not common - deleted. If “Base Unit” means Base Station, it’s CU+DUs+RRUs, not the CU alone
    4.  “Low and high” partitioning in the “CU-CP – Centralized Control Plane (low and high)” and “CU-CP-H/L” is not defined in any (known to me) standard. So it should be either clearly defined (which is not really in the scope of ONAP.org) or referenced or removed. In the meantime it’s deleted.
    5. “Macro Radio & Small Cell Antennas” – modified to the “Radio Antennas”.
    6. The diagram does not match the first phase of 5G, so called Non-Stand-Alone (NSA) architecture where the gNB is backhauled to the 4G RAN. To address this, a separate diagram may be needed – to discuss in the group.
    7. “Edge Analytics” - made a separate bullet as it is not necessarily combined with the Near-real Time Data Collection.

     

    Slide #5

    1. “Disaggregated 5G RAN consists of hybrid network elements (PNF and VNF) and will require a cloud infrastructure deployment at the edge.”   => “Disaggregated 5G RAN may include VNFs” in which case cloud infrastructure deployment at the edge is required.  Beijing implemented the first phase of PNF discovery and instantiation
    2. The term “PNF Radio Element Controller” is not defined in ONAP (neither “Radio Element Controller” nor “Element Controller“) – deleted
    3. “such as Assign, configure, deactivate, etc.” Where these LCM examples come from? Need to add reference or remove - deleted

     

    Slide #6

    1. The term "Disaggregated core" is not used in 3GPP – deleted
    2. “E2E Slice Instances (NSIs)” => “Network Slice Instances (NSIs)”, per 3GPP definition
    3. “Core Network Slice Segments (NSSIs)” => “Core Network Slice Subnet Instances (NSSIs)” , per 3GPP definition
    4. “Transport Slice Segments (NSSIs)” => “Transport Network Slice Subnet Instances (NSSIs)” , per 3GPP definition
    5. “RAN Network Slice Segment (NSSIs)” => “Radio Network Slice Subnet Instances (NSSIs)” , per 3GPP definition
    6. The blue frame extended to include “Transport Abstraction Model” and all xHauls
    7. Added blue frame to associate the Core NSSIs and “Core Abstraction Model” with the Centralized Cloud
    8. “Macro Radio & Small Cell Antennas” – modified to the “Radio Antennas”.
    9. The role of the (incomplete) list of the 5G Core nodes is not clear, particularly for the slice management (e.g. AMF is not there) – deleted

     

    Slide #7

    1. “and Services implemented across PNFs & VNFs” – there is no concept of sharing the services as a part of slicing in 3GPP where “service” means the service provided to the end user. Modified to “sharing network functions and network slice subnet instances”
    2. Multiple changes “Slice segment” => “Network Slice Subnet Instance”, per 3GPP terminology
    3. “Define and instantiate monitoring and management of slice segments, slice instances and slice services”  – “slice services” need explanation (Slice as a Service?); in the meantime deleted
    4. “Slice segments supported and demonstrated in Casablanca will be limited to two smple slices, eMBB (enhance Mobile Broad Band) and URLLC (Ultra-Reliable, Low-latency Communications) in the RAN” – not clear why these two slice types are considered “simple”. The URLLC probably is the most complex in implementation as it requires extremely low latency. The sentence is made less restricting.
  32. Based on today's call, there are seemingly at least two processes for ONAP's role in RAN slicing:

    Process-1: ONAP takes "service requirements" as input and translates this into a slice request (e.g., Service A uses Slice X) for "5G slice management system". The gap here is that ONAP needs to collect a minimum set of data (e.g., what slices are running in the 5G cloud, their performance characteristics, utilization, etc.) to correlate the service requests with an existing RAN slice.

    Process-2: ONAP is used to onboard, configure, instantiate an e2e 5G slice that will be consumable by new services at the end of the process-2 (where Process-1 kicks in).  For this to work, there should be a vendor agnostic workflow for onboarding and configuring VNFs/PNFs with vendor-specific (most likely opaque) software and configuration. The model here is that vendor X deploys a network slice over operator Y's cloud infrastructure. There are many options here: (1) Existing VNFs & PNFs already have the slice implementation and they are simply configured to activate/deactivate these preloaded slices. (2) Existing VNFs & PNFs are upgraded/loaded with new software/hardware. (3) New VNFs & PNFs are deployed, configured, launched.

    Both processes can be done without ONAP knowing anything about RAN-specific configuration, radio resource management, etc., that are internal to the vendor provided functions.

    1. We need to align with 3GPP slice management where the following entities are involved:

      - NSMF    Network Slice Management Function (NSI LCM is here)

      - NSSMF Network Slice Segment Management Function

      A Network Slice Instance (NSI) typically is composed of one CN NSSI and one RAN NSSI. Creation / modification of every NSSI is managed by the corresponding NSSMF.

      Therefore the question is whether NSMF and NSSMF should be implemented as ONAP components.

      1. In my view too, this is the key question.  Should that NSMF and NSSMF be part of ONAP or are they users of ONAP?  In my mind, visualizing NSMF and NSSMF  as user applications of ONAP is intuitive (smile).  That way, ONAP can be kept use case independent. That said, any gaps in ONAP to realize NSMF and NSSMF should be fixed.  In my view, it would be good if requirements of NSMF and NSSMF be identified keeping ONAP service orchestration in mind.

        Some food for thought:

        • Are NS/NSS MFs applications on top of ONAP utilizing ONAP API or part of ONAP?
        • How do NS/NSS MFs are informed of deployment architecture ?  Are existing ONAP APIs good enough?
          • Information about Edge Clouds,  Base station clouds,  Core Clouds
          • Various VNFC information (such as reachability) and their roles (where role is some ONAP independent qualification and transparent to ONAP) - Does some modeling enhancements required to add roles to the VNFCs?
          • How Clouds are connected to each other? Front haul, Mid Haul and Back Haul Controllers information.
          • Authentication and Authorization of NS/NSS MFs by ONAP
        • Do NS/NSS MFs configure QoS information/Isolation/Resource management  per PDP context/slice be handled between NS/NSS MFs and gNB VNFC/PNF by itself or does ONAP need to come in picture? If ONAP can add value, what is it?
        • Any isolation/QoS at the infrastructure level (NFVI/Switches) is best handled by ONAP?  If so, are there sufficient APIs available to program ONAP?
        • Do NS/NSS MFs configure UE permissions per slice to PCFs and other 3GPP NFs directly or does ONAP need to come in picture? If ONAP can add value, what is it?
        • NS/NSS MF need to know whether edge/core clouds support slicing, if supported, slicing capabilities.  ONAP can add value, but these capability representation need to be generic to keep ONAP use case independent.

        Srini




  33. Blue boxes and interfaces are to be implemented by ONAP components.

  34. I have a few questions related to this:

    1. In 3GPP specifications, do PNFs in the 5G network have to support Network Slicing as well as the VNFs? (I assume Yes)
    2. Does 3GPP specify exactly what is a Network Slice and how it should work or does 3GPP leave it open to the vendors to decide?
    3. Have 5G vendors converged on what exactly is a Network Slice and how it should work or is each vendor implementing it in a different way?
    4. Does 3GPP specify a Configuration protocol (i.e. NETCONF/Yang) for configuring 5G network components or does 3GPP leave it open to the vendors to decide?

    Thanks.

    1. For questions 1-3, please take a look at the document I uploaded Slicing_in_3GPP_Rel15.pptx

      1. It's a very good presentation to understand how slicing can be supported in RAN. I think for the purpose of ONAP it should be complemented with review of the SA5 slice management. Will contribute at some point.

        1. I agree. SA5 related parts are missing in this version of the document. 

    2. 3GPP spec does not define VNF vs. PNF. How functions are implemented is up to the vendor.

      In the current specs, RAN is "slice-aware". How slices are supported in a gNB is not defined. Each PDU session is configured with a slice profile. When a network flow belonging to a PDU session arrives at gNB, gNB knows whether it is associated with a particular slice on gNB based on this slice profile. 

      1. The TS 23.501  is not using the term "slice profile". The only "profiles" in that TS are "QoS profile" and "subscription profile".  

        The PDU session contains one or several "QoS flows", for every of which "QoS profile" is defined (similar to the QCI role in LTE). When a PDU session is being established, the Core Network associates it with certain slice. For the gNB association of the PDU session with particular slice instance is based on the parameter called NSSAI (Network Slice Selection Assistance Information), see 38.300 /16.3. I am not sure 3GPP already defined how the gNB interprets the received NSSAI(s); can think of OAM-based configuration at the gNB.

        1. Indeed "slice profile" is not used, I used it to refer to the mapping between S-NSSAI and PDU session in gNB.

  35. Thanks Ulas.

    It appears that the concept of "Network Slices" is very much similar, or modeled after, "MPLS Tunnels" in core IP networks. A "Pipe" with a "QoS Contract".

    The job of provisioning a pipe with a specific QoS contract through a large network is not an easy task. In core IP networks, there are long established protocols for "Traffic Engineering" and "Path Calculation" defined for this purpose. Whatever entity (ONAP?) that is responsible for calculating a slice path, that guarantees a QoS contract through the network, needs to be aware of all consumed and available resources on every physical network equipment and cloud infrastructure equipment involved in the network.

    1. It is a bit more complicated than a pipe model as the CP/UP functions across the pipes would be different and needs to be managed as well. The way it is formulated in Rel. 15 as "slice aware" makes it possible to support slicing with a more glorified radio resource management that provides SLAs across slice/service owners each of which serves many customers. Naturally, intra-slice QoS is also part of this scheduler. But, such glorified radio resource managers are not easily extensible when slightly different requirements show up or more experimental ideas need to be tested in an actual operational network without disturbing the existing tenants (i.e., services). 

  36. Hi Shekar,

    Can you please upload the latest slides which were discussed today?

    Thanks,

    Ramki


  37. Shekar Sundaramurthy - please tweak 'midhaul' to 'fronthaul-II' in figures .... similar to slide 4 in http://sites.ieee.org/sagroups-1914/files/2017/12/tf3_1710_maiden_ngnm_xran_1.pdf, ie., RU--(NGFI-I)--DU---(NGFI-II)–CU. Midhaul is typically for between cell sites, eg., macro<>small or macro<>macro, for example. So, in the 5G view, gNB <> gNB as a whole versus within gNB.

    1. The ITU doc i mention below in comment to Sigmar shows Figure A-1 with 'midhaul'. maybe use IEEE terms for now.

  38. Sigmar Lust - regarding soft/hard isolation, see clause 10 in https://www.itu.int/dms_pub/itu-t/opb/tut/T-TUT-HOME-2018-PDF-E.pdf. It is essentially about impact to one slice vs another. One example i suggested was a separate CU-UP instance, e.g., identified by a different flow ID (eg., VLAN in a eCPRI frame) and processed by a different VNF/server/etc. depending on what isolation level we want. For the purposes of our initial efforts, we can decide that soft isolation is a reasonable starting point.

  39. @Shekar Sundaramurthy - can you please make the following changes in the latest casablanca requirements deck in slide 7 "Radio Network Slice Management – ONAP Requirements"

    • Add in Description 
      • Enhance Multi-Cloud and A&AI to support Guarantee (hard isolation), Burstable (soft isolation) and Best Effort (no isolation) QoS classes for Edge Clouds
    • Add in Impacted ONAP components

      • Multi-Cloud, A&AI
  40. Ramki, can you please clarify what hard/soft/no isolation mean?

  41. Explanation to the changes made in 5GucCasablanca-03222018v3_Cisco.pptx.

    The main issue is request for extending the OF functionality to network optimization like SON. We think feasibility of such extension needs additional study, for the following reasons:

    1. The OF so far is to optimize very few parameters. There are exactly three types of NFVI resources; the optimization goal can be easily expressed in terms of utilization of these resources.

    As different from that, RAN alone has several dozens of KPIs, hundreds of PM measurements and hundreds OAM parameters that control RAN operations.

    2. In the OF, the situation(resource allocation) is under full control of the orchestration system.

    As different from that, RAN is an open system, strongly affected by the Core Network, mobility, interference etc.

    3. NFV resources are independent while RAN KPIs are not. RAN OAM parameters typically affect multiple KPIs, subject to multiple tradeoffs.

    4. In most scenarios, once VMFs are instantiated and provided with certain resources, they do not influence each other in terms of resources

    There are multiple aspects in which RAN nodes influence each other: interference, mobility etc.

    5. There is a developed and commonly accepted “theory of virtualization”: what are NFVI resources, VNFs and PNFs , which LCM operations exist, what is Network Service (per ETSI) etc.

    As different from that, there is no commonly known “theory “of network optimization; existing solutions are proprietary.

    To summarize, RAN is much more complex and much more complex and open system than the orchestration system. We can therefore expect that implementation of RAN optimization may differ in many points from what is currently defined in the OF 

  42. In order for OOF to be able to make the right RAN optimization decisions, ONAP has to first implement the discovery and continuous update of RAN resources (PNFs, QoS, OAM, ...) and populate the RAN data in a database (A&AI?) to be used by OOF. This RAN resources discovery function could be implemented in SDN-C or in a new ONAP RAN management module.

  43. Arash, in RAN optimization (SON), there are no "RAN resources" that would be defined / measured /manipulated in same way as NFVI resources. RAN optimization is application level activity where application level performance measurements are collected (example: statistics of call drops) and  application level (OAM) configuration changes are applied to optimize, for example, network coverage 

    1. Aren't slices and slice segments RAN entities that consume resources that need to be managed and optimized?

  44. RAN entity (also known as Base Station) may include virtualized part. ONAP should be able to support the corresponding VNFs as such, i.e. their VNF aspects. This part is different from support of other VNF types in two elements. One is that such VNFs are running in the edge cloud rather than in the central cloud. Second is that specific arrangements for general management are needed. The latter, we assume, will be provided via the SDN-C (SDN-R); currently not available yet. If/when these two elements are addressed, the VNF part of the BS can be made running under ONAP. Another piece of the puzzle is to support the parts of the BS that are not virtualized (PNFs). Having that addition, we will be able to run the whole BS under ONAP. In this configuration we can think of optimization of NFV related aspects of the BS. Probably the OF can be extended to cover this part to optimize resource utilization and similar aspects of the VNF components of the BSs. However all said is not SON, which is application level optimization. In the future, combined optimization of both BS faces (NFV level and application level) may evolve.

    Network slices consist of network functions (NFs) which can be virtulaized, fully or partially. Some NFs may be shared between slices. The virtualized parts can be subject to OF-like optimization of NFV resources. However slicing includes also significant application level functionality specified in 3GPP. That application level part is orthogonal to virtualization aspects. It can be subject to (application level) optimization too. 

  45. Well described. Agreed.

  46. Hi guys, I'm lost at what exactly (if anything) is being implemented in R2 (Beijing) release. I see more docs on Casablanca so it is very unclear. Could you please summarize?

  47. Dear Benjamin Cheung:

             I have a little supplement to PNFPlugnPlay in the stage of Design Time step 1 and step 4, I would prefer to add PNF geo-location information in PNF Resource Definition which has been standardized in ETSI NFV IFA014 PNFD definition. It could be used in ONAP too.

             And the reson why I prefer to add this arttibute is that we can do e2e NW orchestration in the specific region, or in order to satify radio interface requirement, deploy virtualized RAN part in a suitable NFVI-PoP, etc.

            The attachmnt adds the attribute, please review? and any comments are welcome?

    Best Regards

    Li Xiang 


    1. Any update from this?   Did geo-location information get added?

  48. Cisco changes applied on top of v3, resulting in v4; please see comments from March, 26.

    Thanks

    Vladimir

  49. For the 5G RAN deployment, we’d like to understand more about the workflows, policies and requirements for placement of the VNFs. I’m guessing the same workflows that we used for vCPE in R2 will work, but we should hash it out just to make sure we aren’t missing anything. Here’s a draft based on the VNF placement workflow that is used in Beijing - Homing 5G RAN VNFs.

  50. Agenda for April 19, 2018

    - 5G VNF/PNF deployment use case – Scenario 1 (covered by Nokia on 4/5/18)

    - 5G VNF/PNF deployment use case – Scenario 2 (covered by Ericsson on 4/12/18)

    - 5G slicing use case for Casablanca - All

    - Discuss definition/scoping

    - identify volunteer/leads for different sections

            - UC description/scenario/scope/Functional Requirements

            - Service Model (ONAP, 3GPP)

            - ONAP Design phase items/flow

            - ONAP Execution phase items/flow

    - 5G Optimization/Framework use case – (Vmware/AT&T)

    - Mapping Nokia/Ericsson presentations on PNF/VNF Deployment to Functional Requirements for Casablanca - All

    - Other items?

     

    Regards,

    Shekar Sundaramurthy

  51. I uploaded a Functional Requirements (1st draft) for the deployment (to capture the requirements from the 2 flows/presentations from Nokia & Ericsson) - Please review to add/edit additional items to the flow - we can discuss on the call. I think this format may lend itself to discussing the details for each component with the PTLs.

     https://wiki.onap.org/download/attachments/10784151/5G-NFD-funcReqmts.xlsx?api=v2

    Regards,

    Shekar Sundaramurthy

  52. Following the discussion on the call, I have a couple of comments on the SW management in the presentation.

     5Guc-RAN Deployment (SWCfg_Mgmt)-Casablanca-Huawei 04282018v3.pptx

    My first point is that the description does not include the step of reboot (after #4 in the slide 5). I think it should; otherwise there is a new requirement for the RAN node: capability of the SW upgrade without service interruption. If this requirement is OK for RAN vendors, fine. If not, the step of reboot is mandatory and this changes the whole picture, triggering a batch of questions on what exactly the device "remembers" after the reboot:

    - does it "remember" IPs /IDs of ONAP modules (APP-C)?

    - does it "remember" the context created with ONAP ?

    - does it "remember" the application level context, such as Radio configuration?

    - how other peers (e.g. CN nodes) update the context associated with this RAN node, but created before the SW upgrade/reboot?

    - does it preserve secure association with the ONAP system (which may require also certain arrangement in the ONAP system)?

    - ...

    Every of these bullets triggers a new requirement to the RAN node implementation, and some of them impose requirements also on the CN nodes. If we want to avoid this, the simplest way would be to use same process as for bootstrap. Then the only thing needed from the ONAP system, would be to supply the new SW version to the Initial EM and trigger the reboot.



    1. Reboot steps are shown in the more detailed flow diagrams on slide 8 (labeled as step R7) and slide 9 (labeled as step R9).  

      1. Slides 8 and 9 show DU reboot. The question was about the CU reboot. With the CU virtualized or not, there is a moment when the old firmware is deactivated and the new is activated. The question was what happens with the application level context created by the old version.

        1. I see. Requiring a CU reboot raises all the issues you raised, propagating a local change to the rest of the system including the core network is not a desirable thing to have. The implicit assumption for CU is that it does not require a reboot.

    2. Before clarification, i think these questions should focus on sw mgmt (since you mention the slide page and ask another questions later). Btw, SW upgrade is actually another import topics, which is not covered in this slides.  

      In a nutshell, reboot is necessary. For "If we want to avoid this, the simplest way would be to use same process as for bootstrap", can you explain it more clear, since i did understand the difference about 'remember' things from ONAP perspective. Imo, If these 'remember' things need to help PNF complete deployment to ONAP, they should be remembered regardless of processes.

      1. I think that in the document "5Guc-RAN Operations (SW upgrade)-Casablanca-Huawei&CMCC 05112018v1.pptx" it is showing software upgrade use case only if "option b" from "5Guc-RAN Deployment (SWCfg_Mgmt)-Casablanca-Huawei 04282018v3.pptx" is used.   

        Is there anything detailing PNF software upgrade if "option a" was used?  When APPC talks directly to the PNF and not to its EM?  

        Also what mechanism is used to ensure the data models being used by ONAP (artifacts in PNF package - alarms, counters, config schema, etc) are aligned with the models used at the PNF?   Is the intention that swVersion is the key to ensuring this alignment or is there another proposal?

  53. I have some questions on the application-level configuration in the presentation

     5Guc-RAN Deployment (SWCfg_Mgmt)-Casablanca-Huawei 04282018v3.pptx

    (slides 6 - 7)

    1. Please clarify the following terms:

      - "service" and how it's related to the RAN node to be configured

      - "service instantiation" and how it's related to the RAN configuration action. Cannot application-level configuration be required in the context other than "service instantiation"?

    2. In slide 6, please clarify "generate configuration data from Vendor Adapter": which function is generating the configuration data? Which data model is used? Is this data model proprietary?

    3. In slide 6, "configure PNF/VNF separately (for DU, cfg data contains CU IP for DU homing to a CU)" - where this data comes from? Where the information on the inter-connect comes from?

    4. In slide 6, "CU-DU inter-connect" - What exactly happens in this step?

    5. In slide 6, "configure PNF/VNF separately (for DU, cfg data contains CU IP for DU homing to a CU)" - is it assumed that the CU is VNF and the DU is PNF? Will the process work if the CU is PNF too?

    6. In slide 7, "generate configuration data" (by the EM) - Which information is used to generate the data? Which data model is used for the configuration data? Is this data model proprietary?

    7. In slide 7 "(4) configure PNF/VNF via EM" - must be "by EM"?

      I also have a general question: how this process is aligned with what the SDN-R group is doing?

      Thanks

      Vladimir








    1. My tentative answers to quickly respond:

      1. This is "PNF Service" instantiation. I think the same terminology was used in Beijing release. This is mainly to configure the PNF instance after target software download and before restart.
      2. Vendor Adapter generates the vendor specific configuration data. It also includes ONAP generated configuration data as well (e.g., CU IP address). Data model and configuration values can be vendor specific or following a 3GPP or other SDO models.
      3. Connectivity, homing, IP address assignments, etc. are handled by ONAP functions. APP-C should pull this information from other ONAP components (e.g., SDN-C). Some of the information can be also based on steps 1 and 2.  But, this step is mainly for vendor-specific configuration data. 
      4. This is after reboot, DU re-establishes connection with its CU. Slide 8 is more clear about the steps.
      5. The implicit assumption was indeed that CU is VNF and DU is PNF.   
      6. My answer is the same as my answers to option-a questions. ONAP generated data (e.g., IP address assignments, transport configurations, etc., or data generated based on steps 1 and 2) must be passed by APP-C to EM. Vendor specific operational configuration plus ONAP provided configuration data are jointly used to generate configuration data in step 3. The data model can be proprietary or standards based.
      7. Yes, in this option it must be "by EM". The way you asked the question is intriguing though, what do you have in mind?

      SDN-R question is interesting as there were some questions in the meeting whether APP-C will be SDN-R. I do not know how SDN-R will evolve towards Casablanca (e.g., will it be adopted as APP-C for RAN functions?) and to what extent it will give enough flexibility to the vendor for configuring and controlling their own devices, etc., is not clear to me.


  54. SDN-R is intended to replace both SDN-C & APP-C for RAN.

    SDN-R Use Cases and Objectives

    It is intended to use standards specified Yang model definitions and use NETCONF to manage configuration deployment for RAN components.

    SDN-R Documents


    1. So SDN-R does not have a plug-in architecture that can support different SBIs including vendor specific ones? 

      1. Yes it does, just like SDN-C & APP-C. But there is a distinction between vendor specific SBI logic and vendor specific SBI configuration protocol. Just like SDN-C & APP-C, if the vendor xNF/EMS supports a configuration protocol that is already supported by SDN-x (REST, NETCONF, Ansible, ...) then the job of a vendor plugin is straightforward (or a plugin may not even be needed if the configuration model Yang/JSON/XML is defined at design time). But if vendor xNF/EMS speaks a language (proprietary protocol) that is not supported by SDN-x then the job of a vendor plugin is complex. The SDN-R PTL is the best contact in that regard.

    2. Wrt "standards specified Yang model definitions" - is there a good place to find more details on this?

    3. Hi Arash Hekmat, wrt "It is intended to use standards specified Yang model definitions and use NETCONF to manage configuration deployment ".   Can you clarify the expected timing of vendors adopting standardized YANG and where it comes from?  

      For Casablanca can we use vendor provided data models for PNF configuration?   I think you are implying Yes by your comment below "a plugin may not even be needed if the configuration model Yang/JSON/XML is defined at design time".   If vendor-specific configuration of PNFs is supported in Casablanca, is CDT tool (CDS in Casablanca?) used for generating configuration (like APPC)?

      1. I believe the SDN-C/R (CCSDK) framework, which is based on OpenDaylight Karaf distribution, is intended to allow vendor Yang models to be added and supported. Also, the CDT/CDS framework is intended to integrate vendor configuration models (XML/JSON templates). The CDT/CDS code is being moved to CCSDK so that after Casablanca both SDN-C/R and APPC have the CDT/CDS functionality. But what Yang models would be used in the Casablanca release are driven by Casablanca use case requirements and managed by the PTLs of the SDN-C/R and CDT/CDS projects. You can contact the PTLs for specifics. What I know is that a set of standard/common Yang models are already added to CCSDK code in ccsdk/apps/sdnr/model/yang (https://gerrit.onap.org/r/gitweb?p=ccsdk/apps.git;a=tree;f=sdnr/model/yang;h=a3725e068e7b71265b783d591183fc28e607676d;hb=HEAD) to support the 5G use cases in Casablanca. In the future, depending on the requirements, any other standard or vendor Yang models can similarly be added.

  55. I added "target software management" to 5G Use Case Casablanca Summary on the "deployment" bullet (slide 3). Since Service Configuration Improvement and Life-cycle Management Support rows (slides 4 and 5) may cover this, I did not add a new entry in the tables.