Core Network Data Channel URL Mapping for Multiple UE Sessions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies are limited in establishing multiple data channels (DCs) for a single user equipment (UE), hindering the provision of enhanced services like screen sharing and file transmission during calls.

Innovation Solution

A method and apparatus for establishing data channels involving multiple core network devices that create and manage uniform resource locators (URLs) for identifying and managing data channels, enabling the establishment of multiple DCs by recording and replacing URLs based on specific information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single UE establishes only one DC according to existing technologies, then the system complexity is low and management is simple, but the service capability is limited and cannot support multiple concurrent services

Engineering Contradiction:
Improveservice capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the data channel management by introducing unique identifiers (DC-UE-ID) for each data channel. When a UE needs to establish multiple DCs, each DC is assigned a distinct identifier, allowing the system to manage multiple channels separately. The AS maintains a mapping relationship between DC identifiers and UE identifiers, enabling differentiated management of each channel while keeping the overall system structure intact.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a new dimension to DC management by introducing the DC-UE-ID identifier layer. Instead of managing DCs solely through UE identity, the system now operates in a two-dimensional space of (DC identifier, UE identifier). This dimensional expansion allows multiple DCs per UE without increasing fundamental system complexity, as each DC can be independently identified and managed along the new identifier dimension.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If multiple DCs are established for a single UE, then enhanced services like screen sharing and file transmission can be provided, but the difficulty of detecting and measuring channel correspondence increases

Engineering Contradiction:
Improveservice capabilityVSAvoidchannel correspondence tracking
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements feedback mechanisms where the AS maintains and updates mapping relationships between DC identifiers and UE identifiers. When a UE establishes a new DC, the AS records the correspondence in a mapping table. This feedback loop ensures that the system always has accurate information about which DC belongs to which UE, making it easy to track and manage multiple channels without increasing detection difficulty.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces the AS as an intermediary that manages the mapping between DC identifiers and UE identifiers. Rather than requiring direct tracking between multiple DCs and UEs, the AS acts as a central mediator that maintains the correspondence information. This intermediary approach simplifies the detection and measurement of channel correspondence, as all mapping information is centralized and managed by the AS.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If a uniform resource locator URL is assigned to each data channel, then precise channel identification and management is enabled, but the information processing overhead and message transmission complexity increases

Engineering Contradiction:
Improvechannel identification precisionVSAvoidinformation processing overhead
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies local quality by assigning unique identifiers (DC-UE-ID) and URLs specifically to data channels that require enhanced services. Not all DCs need complex identification mechanisms - only those supporting screen sharing, file transmission, or other enhanced services. This localized application of precise identification reduces overall information processing overhead while maintaining precision where needed.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent changes the identification parameters from simple UE-based identification to DC-specific identifier parameters (DC-UE-ID). This parameter change enables precise channel identification without requiring complex processing, as the new parameters are designed to be compact and efficiently manageable. The URL structure is also optimized to include necessary identification information without excessive complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP4665070A1Data channel establishment method, apparatus, core network device and storage medium
Publication Date: 2025.12.17 VIVO MOBILE COMM CO LTD
  • EP4665070A1 patent drawingFigure 1~2
  • EP4665070A1 patent drawingFigure 3~4
  • EP4665070A1 patent drawingFigure 5

AI summary

This application discloses a method and apparatus for establishing a data channel, a core network device, and a storage medium, and pertains to the field of wireless communication technologies. The method for establishing a data channel according to embodiments of this application includes: receiving, by a first core network device, a first message sent by a second core network device, where the first message is used for establishing a data channel for a terminal, and the first message includes first information; creating, by the first core network device based on the first information, a uniform resource locator URL corresponding to the data channel; and sending, by the first core network device, a second message to the second core network device, where the second message includes the URL; where the first information includes at least one of the following: information used for identifying the data channel; and information used for indicating an application content source corresponding to the data channel.