5G Terminal RQoS Control and Network Slice Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The 5G mobile communication system lacks clear definitions for terminal apparatus-initiated Reflective Quality of Service (RQoS) control, network-initiated RQoS control, authentication and authorization functions by the data network, and management processes for network slices, particularly in connecting to multiple slices.

Innovation Solution

A terminal apparatus and core network apparatus are configured to transmit and receive specific information for RQoS support and validation, including a QoS Flow Identity (QFI) in encrypted headers, with a timer for managing RQoS state, enabling terminal-initiated and network-initiated RQoS control, authentication, and congestion management across network slices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If network-initiated RQoS control mechanisms are defined, then network control capability is improved, but terminal apparatus-initiated RQoS control remains undefined

Engineering Contradiction:
Improvenetwork control capabilityVSAvoidterminal apparatus-initiated control
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent defines a universal RQoS control framework that accommodates both network-initiated and terminal apparatus-initiated control modes through the same core mechanism. The network device and terminal apparatus can both initiate RQoS control procedures using standardized message exchanges, making the system multi-functional and adaptable to different control scenarios without requiring separate mechanisms.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Ease of manufacture

If authentication and authorization functions by data network are summarized, then functional overview is improved, but detailed message transmission and reception are not defined

Engineering Contradiction:
Improvefunctional overviewVSAvoidmessage transmission details
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The authentication and authorization function is segmented into distinct message exchange phases: capability indication, authentication request/response, and authorization confirmation. Each phase is defined with specific message types and information elements, providing both functional overview and detailed transmission specifications without redundancy.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If terminal apparatus is connectible to multiple network slices, then network connectivity is improved, but management process for multiple slices is not defined

Engineering Contradiction:
Improvenetwork slice connectivityVSAvoidmanagement process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by requiring the terminal apparatus to indicate its multi-network slice capability before actual connection. The network device then pre-configures slice-specific parameters and management rules, establishing a structured framework that simplifies subsequent multi-slice management rather than handling complexity ad hoc.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If RQoS state change request is implemented, then RQoS flexibility is improved, but state management complexity increases

Engineering Contradiction:
ImproveRQoS state flexibilityVSAvoidstate management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The RQoS state change mechanism incorporates feedback loops where the terminal apparatus requests state changes and the network device responds with acceptance or rejection indications. The network device also provides feedback on current RQoS status and capabilities, enabling flexible state management through standardized feedback messages that reduce management complexity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3644648B1Terminal device, core network device
Publication Date: 2022.09.07 SHARP KK
  • EP3644648B1 patent drawingFigure 1
  • EP3644648B1 patent drawingFigure 2
  • EP3644648B1 patent drawingFigure 3

AI summary

A terminal apparatus or a device in a core network exchanges capability information for each function in a registration procedure or a PDU session establishment procedure, and in user data communication additional information is added into an uplink packet to implement terminal apparatus-initiated RQoS control, and additional information is added into a downlink packet to implement network device-initiated RQoS control. A dedicated control message and information for an authentication and/or authorization function by a DN are defined to implement the authentication and/or authorization function by the DN. Furthermore, the terminal apparatus and the device in the core network have a timer or a control process for each network slice to implement a management process such as congestion management for each network slice. This provides a communication control method in order to implement the terminal apparatus-initiated or network-initiated RQoS control, implement the authentication and/or authorization function by the DN, and implement the management process such as congestion management for each network slice.