Network Slice Instance Specification via Segmented Information Model
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies lack a comprehensive mechanism to specify, deploy, and operate network slice instances (NSIs) effectively, particularly in managing network slices across disparate segments with different technologies and roles, and there is a need for a detailed description of atomic components and their relationships in an object class structure for mobile networks.
Innovation Solution
A function in a communications network that communicates a specification of an NSI, identifying network functions (NFs) and operating them according to the specification, using an information model that describes the instance with details on components, connections, and attributes, including topology and connectivity, to configure and manage NSIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network slicing is implemented across multiple disparate segments with different technologies and roles, then network resource sharing and service capability are improved, but system complexity and difficulty of management increase
Solution Approach 1:
The patent divides the network slice management into distinct segments: network slice template (NST) for design-phase configuration, network slice instance (NSI) for deployment-phase instantiation, and network slice subnet instance (NSSI) for operational-phase management. Each segment handles specific technologies and roles independently, reducing cross-segment complexity while maintaining resource sharing capabilities across segments.
Solution Approach 2:
The patent introduces network slice management functions (NSMF) and network slice subnet management functions (NSSMF) as intermediary entities that coordinate between disparate network segments. These intermediaries translate between different technology domains and roles, enabling resource sharing without requiring direct integration between all segments, thus managing complexity.
2Manufacturing precision
If detailed specification of atomic components and their relationships is provided in an object class structure, then network slice provisioning precision is improved, but information model complexity increases
Solution Approach 1:
The patent segments the information model into hierarchical object classes: managed object class (MOC) for atomic components, managed object class relationship (MOCR) for relationships between components, and managed information model (MIM) for the complete specification. This segmentation allows detailed provisioning precision at each level without overwhelming complexity in the entire model.
Solution Approach 2:
The patent adds a temporal dimension to the information model by distinguishing between template-level definitions (design phase) and instance-level configurations (deployment phase). This dimensional separation allows detailed specifications to be defined once at the template level and then instantiated multiple times without repeating the complexity, improving provisioning precision while managing model complexity.
Data Source
AI summary
A method comprises communicating a specification of a network slice instance (NSI) that identifies a network function (NF), and operating the identified NF in accordance with the specification.