Mobility Proxy for Service-Based 5G RAN Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing 5G radio access network (RAN) architecture lacks a service-based solution for handling requests to RAN nodes after a UE context handover or when the UE becomes idle, and RAN nodes cannot directly address services offered by 5GC nodes, while maintaining security protection between RAN and core networks.

Innovation Solution

A mobility proxy is introduced to handle service-based requests by identifying and forwarding or redirecting requests to the appropriate network functions within the RAN and 5GC, using mapping relationships to ensure secure and efficient service delivery, even during UE handovers or when the UE is idle.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional non-service-based interfaces are used between AMF and RAN, then security protection is maintained, but service-based architecture cannot be implemented in access network

Engineering Contradiction:
Improveservice-based architecture implementationVSAvoidsecurity protection
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a mobility proxy as an intermediary component that sits between the RAN and 5GC. This proxy handles service-based requests from RAN nodes, performs necessary translations and mappings, and forwards requests to appropriate 5GC network functions. The mobility proxy enables service-based architecture in the access network while maintaining security boundaries, as it acts as a controlled interface that can validate and manage communications between the traditional and service-based architectures.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If AMF shields mobility from 5GC, then security is improved, but RAN nodes cannot directly address 5GC services

Engineering Contradiction:
Improvedirect service addressingVSAvoidmobility shielding
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the network functionality by introducing a mobility proxy that handles specific mobility-related service-based requests. This segmentation allows RAN nodes to directly address mobility services through the proxy without compromising the overall mobility shielding architecture. The proxy is specifically dedicated to handling service-based interface requests related to mobility, while other AMF functions continue to shield mobility information from 5GC as designed.

Inventive Principle:
Principle #1Segmentation

3Productivity

If service-based interface is introduced in RAN, then service delivery during handover is improved, but request routing complexity increases

Engineering Contradiction:
Improveservice delivery efficiencyVSAvoidrequest routing mechanism
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The mobility proxy implements self-service mechanisms by maintaining local mapping relationships between RAN node identifiers and 5GC network function addresses. When a RAN node sends a service-based request, the proxy autonomously resolves the routing using its stored mappings without requiring complex external routing protocols or additional network function coordination. This self-service approach simplifies the overall routing complexity while enabling efficient service delivery during handovers.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240422233A1Mobility in SBA access network
Publication Date: 2024.12.19 NOKIA TECHNOLOGIES OY
  • US20240422233A1 patent drawing
  • US20240422233A1 patent drawing
  • US20240422233A1 patent drawing

AI summary

Method comprising: receiving, from a first network function of a first domain, a request for a first service related to one of one or more terminals or to one or more PDU sessions of the one or more terminals, identifying an address of one of one or more second network functions of a second domain based on the requested first service, the one or more terminals and the one ore more PDU sessions, respectively, and a first mapping relationship; forwarding the request or redirecting the request towards the one second network function, wherein the first mapping relationship indicates, for each of the one or more terminals and for each of the one or more PDU sessions, respectively, a respective address of the one second network function capable to serve the one or more terminals or the one or more PDU sessions.