Multi-Access Registration in 3GPP Non-3GPP Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 3GPP communication protocols do not specify how user equipment (UE) registers with both a 3GPP network and a non-3GPP network, failing to meet the requirement of dual registration in multi-access scenarios.

Innovation Solution

A connection processing method is introduced where a mobility management functional entity receives a registration request message with multi-access indication information and identification information, determining the UE's registration status across both networks and performing the necessary registration procedures to enable multi-access registration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If 3GPP communication protocol is used for network registration, then the network can support single-access registration, but it cannot meet the requirement of dual registration in multi-access scenarios

Engineering Contradiction:
Improvemulti-access registration capabilityVSAvoidprotocol specification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the registration process by introducing distinct indication information for different access types (3GPP access vs. non-3GPP access). The mobility management functional entity separately processes registration requests based on access type indication information, allowing independent handling of each access network while maintaining unified protocol framework.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enhances the universality of the registration protocol by making the registration request message capable of carrying both 3GPP and non-3GPP access type indication information. The same message structure and processing logic can handle both access types, eliminating the need for separate protocol specifications while achieving multi-access registration capability.

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

2Adaptability or versatility

If separate registration procedures are implemented for 3GPP and non-3GPP networks, then dual registration requirement can be met, but session establishment latency increases

Engineering Contradiction:
Improvedual registration capabilityVSAvoidsession establishment latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent merges the registration procedures for 3GPP and non-3GPP networks into a single unified process. The mobility management functional entity receives one registration request message containing both access type indication information and user equipment context, processes both access types simultaneously, and completes dual registration in one operation rather than requiring separate sequential procedures.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements preliminary action by having the mobility management functional entity obtain user equipment context information from the registration request message before processing the actual registration. This allows the entity to prepare necessary processing steps in advance, reducing the time required for session establishment after registration is initiated.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11737045B2Connection processing method and apparatus in multi-access scenario
Publication Date: 2023.08.22 HUAWEI TECH CO LTD
  • US11737045B2 patent drawing
  • US11737045B2 patent drawing
  • US11737045B2 patent drawing

AI summary

Example connection processing methods in a multi-access scenario and apparatus are described. One example method includes receiving a second transmission message by a session management functional entity from a mobility management functional entity. The session management functional entity determines whether establishment of a multi-access PDU session is allowed based on session subscription data of user equipment. In response to determining that the establishment of the multi-access PDU session is allowed, the session management functional entity sends an N4 session establishment or update request message to a user plane functional entity. The user plane functional entity sends a connection establishment reply message to the session management functional entity.