Versions Compared

Old Version 2

changes.mady.by.user Swaminathan Seetharaman

Saved on

compared with

New Version Current

changes.mady.by.user Swaminathan Seetharaman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Functional view

Note: Priority 1 items are proposed to be part of Honolulu. Priority 2 items will be considered as "Stretch goals".

TrackDetails
Interested RAN Slicing
  • Preparation phase, involving RAN NF instantiation and onboarding
    • Configuration of RAN NFs over standard O1 - will depend on availability of info models from O-RAN
    Impacted Component(s)CompaniesPriority
    Guilin functional enhancements



    Completion of remaining Guilin Integration Tests, fixing of related bugs (across all tracks)

    		UUI, SO, OOF, SDN-C/CCSDK, DCAE, Policy, ExtAPI

    CMCC, Wipro, Tech Mahindra, TIM, Huawei, LTTS

    		1
    Endpoint related enhancements (NSMF, RAN/Core/TN NSSMF)
    • Service & Slice Profile modeling enhancements
    • Interface between NSMF and NSSMF (modifyNSSI, no NSST info for allocateNSSI, etc.)
    • UUI enhancements for TMF 641 API support
    Standards AlignmentKPI Monitoring
  • TMF 628 implementation
    • UUI, SO, OOF, SDN-C/CCSDKCMCC, Wipro, Tech Mahindra, TIM, Huawei1
    3GPP API alignment (Service/Slice Profile - e.g., coverageArea and coverageAreaTAList), modeling enhancements, minor workflow enhancements for NSMF, all 3 NSSMFs and NSSMF adaptor for e2e network sliceSO, AAICMCC, Wipro, Tech Mahindra, Huawei1
    NST selection enhancementOOFHuawei, Wipro1
    Use of resource occupancy levels in NSI/NSSI for NSI/NSSI selection (involves collecting and storing/analyzing the data, and then using this info for NSI/NSSI selection) (ArchCom)DCAE (to be confirmed), SO, OOFWipro2
    TMF 641 alignment for Slice LCMUUICMCC2
    RAN Slicing




    		A1 interface for Closed Loop and Intelligent SlicingSDN-R/CCSDKWipro, IBM
  • Slice assurance use cases - this needs to be evaluated further.
  • Endpoints and transport connectivity related aspects, for e.g., parameters required to be passed to TN NSSMF (how they shall be determined), MP to MP connection, etc.
    • Core SlicingTransport Slicing
    • Endpoints and transport connectivity related aspects, for e.g., parameters required to be passed to TN NSSMF (how they shall be determined), MP to MP connection, etc.
    • Transport NSSI selection and reuse
    1
    RAN Slice resource (re)allocation, Slice profile decomposition at Near-RT RIC levelSDN-R/CCSDK, OOFWipro, IBM1
    Coverage Area to TA mappingSO/OOF?Wipro1
    RAN Service enhancements, including service instantiation actionsSO, SDN-R/CCSDKWipro2
    3GPP specs related enhancements including yang updatesSDN-R/CCSDKWipro, IBM2
    Use of CPS instead of Config DBSDN-R, DCAEWipro, IBM2
    Core SlicingEnhancements to Core NF configurationSO, CDSTech Mahindra, TIM1
    Core NF placementSO, OOFTech Mahindra, Wipro2
    Transport Slicing

    Enhancements related to TN NSSI reuse, considering occupancy levels, modification of associated NSSI with SLA, etc.

    		SO, SDN-C/CCSDKHuawei1
    TN model enhancements, alignment to SDOsSO, AAI, SDN-CHuawei2
    Support of MP to MP connectionSO, OOF, SDN-CHuawei, Wipro2
    KPI Monitoring

    Complete PM-mapper/new MS with all required functionality for KPI computation (ArchCom)

    		DCAECMCC1

    Computation of KPIs at NSI/NSSI level, policy-driven list of KPIs

    		DCAECMCC2
    Retrieval of historic KPI values for Closed Loop and by UUIDCAECMCC, Wipro2
    TMF 628 API support for KPI monitoring (ArchCom)ExtAPI, UUIWipro2
    Aggregator function (to aggregate data from all NFs of same type, otherwise KPI computation logic to be refined) (ArchCom)??????2
    Closed Loop

    Closed Loop scenario involving RAN and Core - details being worked out

    		SO, DCAE, SDN-R/CCSDKWipro (RAN, RAN Simulator), IBM (SDN-R), LTTS (Core NF Simulator)1
    Intelligent Slicing
  • Closed Loop involving RAN and Core
    • Split intelligence, with guidance coming over A1
    Enhance existing scenario with CoreDCAE, SDN-R/CCSDKWipro, IBM1
    Modeling enhancements
  • Support for both options
    • RAN service design enhancements
    • Endpoints
    • Service and Slice Profiles
    		SDC, AAI, SOCMCC, Amdocs, Wipro1

    Component view

    Note: Only Priority 1 items are listed.

    ComponentImpactsCommitment
    AAI
    • Guilin bugs
    • Modeling enhancements
    		CMCC, Huawei
    SDN-C/CCSDK
    • Guilin bugs
    • TN NSSI reuse and config updates
    		Huawei
    SDN-R/CCSDK
    • RAN resource (re)allocation
    • A1 interface support
    		IBM, Wipro
    SO
    • Guilin bugs
    • NSMF enhancements and NSSMF workflow enhancements for all 3 subnets (mainly fixing Guilin gaps and any minor enhancements for RAN, Core, TN for e2e slice stitching), endpoints enhancements
    • CoverageArea → TA list mapping (will it be part of OOF?) (RAN)
    • RAN NSSI related enhancements (RAN)
    • Reuse of TN NSSI (TN)
    • Core NF config updates (Core)
    • Closed Loop related enhancements (RAN/NSMF)
    		CMCC (NSMF), Wipro (RAN NSSMF), Tech Mahindra (Core NSSMF), TIM (Core NSSMF), Huawei (TN NSSMF)
    CDS
    • Core NF config updates (Core)
    		Tech Mahindra
    OOF
    • NST selection enhancements
    • Use of endpoints for NSSI selection
    • CoverageArea → TA list mapping (will it be part of SO?)
    • TN NSSI selection enhancements (if any)
    • Generic functional enhancements (Slice profile generation, etc.)
    • RAN resource (re)allocation including Slice Profile decomposition
    		Wipro, Huawei
    Policy
    • Guilin bugs
    		Wipro
    ExtAPI
    • Guilin bugs
    		Wipro
    DCAE
    • Guilin bugs
    • Enhancements in PM Mapper/New MS for KPI computation
    • DES for historic KPI retrieval
    • Enhancements in Slice Analysis MS for Closed Loop

    CMCC (PM Mapper/New MS and DES)

    Wipro (Slice Analysis MS)

    UUI
    • Enhancements related to endpoints
    		CMCC
    Config DB/CPS
    • Guilin bugs
    • Enhancements related to endpoints, etc.

    (Note: CPS may be a stretch goal, and may be realized as a PoC)

    		Wipro, IBM