Tag-Based Network Slice Resource Mapping Across Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network slicing technologies face challenges in efficiently managing and allocating resources across multiple domains to meet the diverse service requirements of different network slices, leading to inefficiencies and difficulties in maintaining performance characteristics for each slice.
Innovation Solution
A method and apparatus that utilize a tag-based resource mapping system to dynamically allocate and manage resources across multiple domains, allowing for efficient switching and adaptation to service requirements by using a tag identifier to map in-domain resources and network slices, reducing the burden on the application layer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network slicing technology is used to support various services, then service diversity and customization are improved, but resource management complexity and allocation inefficiency increase across multiple domains
Solution Approach 1:
The patent introduces a first entity (NF translator) as an intermediary between the second entity (network slice manager) and domain-specific nodes. This intermediary translates network slice information into domain-specific resource requests, managing the complexity of cross-domain resource allocation while maintaining service diversity. The translator acts as a mediator that converts abstract slice requirements into concrete resource allocations across different domains without requiring each domain to directly understand slice management protocols.
2Productivity
If traditional resource allocation methods are used without tag-based mapping, then system simplicity is maintained, but resource utilization efficiency and dynamic adaptation to service demands decrease
Solution Approach 1:
The patent implements a universal tag-based resource mapping mechanism that can be applied across multiple domains and service types. The tag system provides a multi-functional identifier that can represent different resource types, service requirements, and domain-specific parameters in a unified manner. This universal mapping approach enables efficient resource allocation for diverse services without requiring separate allocation mechanisms for each service type or domain.
Solution Approach 2:
The patent utilizes parameter changes by dynamically modifying resource allocation based on service requirements expressed through tags. The system changes resource parameters (such as bandwidth, computing power, storage) according to the tag identifiers that represent different service levels and requirements. This allows dynamic adaptation of resource characteristics to match varying service demands without permanent reconfiguration of the network infrastructure.
3Measurement precision
If domain-specific resource management is implemented, then resource allocation precision for each domain is improved, but cross-domain resource coordination and information exchange difficulty increase
Solution Approach 1:
The patent segments resource management into domain-specific operations while maintaining a unified tag-based coordination layer. Each domain can manage its resources with high precision using domain-specific parameters and policies, while the tag system provides a segmented yet connected framework for cross-domain coordination. The first entity divides the complex cross-domain management task into manageable translation operations between different domain interfaces.
Data Source
AI summary
A method performed by means of a first entity is provided. The method includes an operation of receiving, from a second entity for managing a network slice, an initiate message including network slice information, based on the network slice information, transmitting, to a first node of a first domain, a request message including an identifier for indicating a tag, an ingress identifier, an egress identifier, and information about a policy related to the tag, and receiving, from the first node, a response message corresponding to the request message, wherein the ingress identifier includes an identifier indicating a second domain for transmitting a packet to the first domain, wherein the egress identifier includes an identifier indicating a third domain for receiving the packet from the first domain, and wherein the tag is an identifier for mapping an in-domain resource for the packet and at least one network slice associated to the packet.