5G Network Slice Capability Configuration via Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is no clear solution for configuring the capabilities of a terminal device when it supports multiple air-interface slices in 5G networks, which affects system performance across various scenarios and service types.

Innovation Solution

A capability configuration method where a network device sends configuration information to the terminal device to determine and match the capabilities of each air-interface slice, using a candidate set that includes unique and shared capabilities, ensuring both devices have a common understanding of the supported capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a terminal device supports multiple air-interface slices, then the device can serve various scenarios and service types (eMBB, URLLC, mMTC), but there is no clear solution for configuring the device's capabilities in each slice

Engineering Contradiction:
Improvesupport for multiple air-interface slicesVSAvoidcapability configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The capability configuration is segmented by dividing capabilities into two categories: unique capabilities (specific to each air-interface slice) and shared capabilities (common across multiple slices). This segmentation allows the network device to configure capabilities separately for each slice type, resolving the configuration ambiguity while supporting multiple slices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different capability configuration approaches are applied to different air-interface slices based on their specific requirements. Unique capabilities are configured individually for each slice type (eMBB, URLLC, mMTC), while shared capabilities are configured collectively. This local quality approach ensures each slice receives appropriate capability configuration without unnecessary complexity.

Inventive Principle:
Principle #3Local quality

2Reliability

If optimization is implemented for high reliability and low latency (URLLC), then these service requirements are met, but spectral efficiency is reduced

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidspectral efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments different service requirements into separate air-interface slices (URLLC slice for reliability-critical services, eMBB slice for throughput-critical services). Each slice is configured with capabilities optimized for its specific service type, allowing URLLC to achieve high reliability without forcing eMBB services to compromise spectral efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different capability configurations are applied locally to different service types. URLLC services receive capability configurations optimized for reliability and low latency, while eMBB services receive configurations optimized for spectral efficiency. This local optimization allows each service type to achieve its performance goals without negatively impacting other services.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12035417B2Capability configuration method and apparatus for configuring a network slice of a radio access network
Publication Date: 2024.07.09 HUAWEI TECH CO LTD
  • US12035417B2 patent drawing
  • US12035417B2 patent drawing
  • US12035417B2 patent drawing

AI summary

A capability configuration method and an apparatus are provided. The method includes: sending, by a network device, capability configuration information to a terminal device, where the capability configuration information is used to indicate a capability corresponding to an air-interface slice supported by the terminal device, and the capability corresponding to the air-interface slice supported by the terminal device is determined from a capability candidate set reported by the terminal device; and communicating, by the network device, with the terminal device by using the air-interface slice supported by the terminal device.