Mobility Information Exchange in Cellular Radio Communications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication networks lack continuous and accurate information on user equipment (UE) speed, which hinders efficient management and adaptation of mobility-related parameters, as UE speed information is only available during specific events like handover or radio link failure, and may not reflect the actual mobility state of all UEs.

Innovation Solution

Implementing a method where UEs report their mobility state upon switching to RRC Connected Mode, estimating speed by measuring handovers or using location information, and requesting and transmitting mobility information from UEs to serving nodes, enabling the network to gather comprehensive and accurate speed data for all UEs, even in idle mode.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the network requests mobility information from all UEs upon connection, then the network obtains comprehensive and accurate UE speed information, but the signaling overhead and network traffic increase

Engineering Contradiction:
ImproveUE speed information accuracyVSAvoidsignaling overhead
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The UE estimates its mobility state (low, medium, high) in advance while in idle mode based on handover counts or location changes, and stores this information ready for reporting. When the network requests mobility information upon connection, the UE can immediately provide pre-calculated data without requiring complex real-time measurements, thus reducing signaling overhead while maintaining accuracy.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If the network obtains UE speed information only during handover or RLF events, then the signaling overhead is reduced, but the network lacks continuous and accurate mobility information for all UEs

Engineering Contradiction:
Improvesignaling overheadVSAvoidmobility information availability
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The UE autonomously estimates its own mobility state using local measurements of handover events or location information while in idle mode. This self-service approach allows the UE to maintain up-to-date mobility information without continuous network intervention, ensuring information availability while minimizing signaling overhead since the UE only reports when connecting.

Inventive Principle:
Principle #25Self-service

3Ease of manufacture

If the network uses UE History information to estimate speed, then the implementation is simple, but the accuracy is reduced due to varying cell sizes and UE movement patterns

Engineering Contradiction:
Improveimplementation simplicityVSAvoidspeed estimation accuracy
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

Instead of relying on UE History information that varies with cell sizes and movement patterns, the invention changes the measurement parameter to count the number of handovers or location changes within a specific time window. This standardized parameter (handover count or location update frequency) provides more consistent and accurate mobility state estimation across different network configurations while remaining simple to implement.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10924915B2Exchange of mobility information in cellular radio communications
Publication Date: 2021.02.16 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US10924915B2 patent drawing
  • US10924915B2 patent drawing
  • US10924915B2 patent drawing

AI summary

A connection request is received from a remote terminal of a radio communications system at a serving node of the radio communications system. Mobility information is requested (230) from the remote terminal based on receiving (200) the connection request. The requested mobility information is received (240) from the remote terminal, and the requested connection is established (250) with the remote terminal.