Use this template to submit Use Cases for submission to the 5G Super Blueprint Use Case & Requirements Advisory Group. All input marked Mandatory is required for the blueprint use case proposal to be deemed ready for review by the Use Case & Requirements Advisory Group.
Use Case Name:
(Mandatory)
Intent Driven Orchestration for an Autonomous 5G Network
Use Case Description:
(Mandatory)
Showcase Level 4 Autonomous 5G Network that can be provisioned using Intents and also maintain intents by effectively managing and resolving conflicts without manual interventions. Use case would use TMF 921 standards for the intent management.
-Epic
-Problem Statement
(Mandatory)
Operators are required to maintain highly complex 5G network based on the varied business requirements/intents.
Following are the solutions to be addressed in this usecase
Automatically manage network availability, scalability and other quality of services as per business requirements/intents with minimal or zero manual interventions.
Standardize the construct used to write Intents and maintain the same.
Scalable to fulfill Edge, Core and RAN Requirements using intents
Provide agility to autonomously resolve conflicts between the intents
Blueprint Owner
(Mandatory)
Infosys Ltd; China Mobile
Users Stories
(at least one (1) User Story is Mandatory)
a.
b.
c.
Interaction with other open source projects and components
(Mandatory)
a.
b.
c.
Resources -people
(Mandatory)
Resources (people) to execute on the blueprint:
enter name 1
enter name 2
...
Steps to Realization
What is the very 1st step to realization?
2nd step?
3rd step?
High-level architecture diagram
(Mandatory)
High level lab topology diagram
(Mandatory)
Dependencies - list of any dependencies that rely of future releases of a specfic component.
(Mandatory)
Yes
Enter details:
or
No
High-level timeline
(Mandatory)
Month that build can begin: enter month/year
Approximate duration of build: enter number of weeks or months
Approximate completion of outputs: enter month/year
Upstreaming Opportunities
(Mandatory)
enter project(s) and details
Blueprint Outputs
(Mandatory)
check all that apply:
Code repository
Configuration files (e.g. Helm charts, etc.)
Upstreaming to relevant projects
Continuous Integration
Test requirements and test results (if applicable)
Documentation:
Overview and Theory of Operation (i.e., what does it do?)
Deployment and setup
Videos
demo
lab setup/behind the scenes
other
High-level timeline
(Mandatory)
Month that build can begin: enter month/year
Approximate duration of build: enter number of weeks or months
Approximate completion of all outputs: enter month/year
Links to existing documentation (Build Guide, Slideware, etc), if available (optional).
Achieve cross-domain intent processing, including business, service, and resources (RAN, Transport, Core, Edge, and Cloud)
What open source components for RAN, Core, Edge are planned?
Continuously enhance the ONAP large model convergence platform to support the integration of more large models
Continuously develop intelligent agents based on large models to promote the evolution of autonomous networks to a higher level of automation and intelligence, achieving optimized allocation and dynamic management of network resource
Need to stitch ONAP APIs with Nephio APIs. Ganesh to respond and add a diagram
update from Keguang
Attached is the preliminary plan for ONAP API specifications. See link to file above
We plan to present a demo of ONAP knowledge Q&A based on large models at the ONE Summit.
Regarding the installation of nephio, the current issue we identified is related to the network connectivity within our own container, and we are still trying to fix it.
Status Update Meeting
Ganesh provided Nehio API specifications: Nephio API
Keguang (via email)- The progress on our team mainly involves building an ONAP knowledge Q&A system based on China Mobile's Jiutian large model, which is undergoing further optimization.
Potential issue with both CMCC and Infosys attendance at ONE Summit.
