Mobile Node Mobility Data Management via Shared Memory

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobility management systems for mobile nodes across different IP networks require duplicating mobility data in multiple modules, leading to increased risk of errors and maintenance costs due to the need for data duplication across various home agents.

Innovation Solution

A method where a mobile node stores mobility data in a single memory zone, accessible by multiple modules, allowing each module to obtain necessary data from this central storage, thereby eliminating the need for duplication and reducing maintenance and error risks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If mobility data is duplicated in multiple management modules for different network types, then each module can independently manage mobility sessions, but the risk of data entry errors increases and maintenance complexity increases

Engineering Contradiction:
Improvemobility data consistencyVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the mobility data storage from multiple separate management modules into a single shared memory area. The first and second management modules both access the same mobility data stored in one location, eliminating the need for duplication. This resolves the contradiction by maintaining data consistency across modules while reducing the complexity of managing multiple copies of the same data.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The shared memory area serves as a universal storage location that can be accessed by multiple different management modules simultaneously. Instead of each module having its own dedicated storage, the universal memory area allows any module to retrieve mobility data as needed, reducing overall system complexity while ensuring all modules work with identical data.

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

2Adaptability or versatility

If separate data trees are defined for each network type in a tree structure, then each network can be managed independently, but any addition, modification, or deletion of mobility data must be performed in each management module

Engineering Contradiction:
Improvenetwork type adaptabilityVSAvoiddata maintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent combines multiple separate data trees for different network types into a single unified data structure in shared memory. Instead of maintaining separate trees that must be同步 updated, the unified structure allows single-point modifications that are immediately available to all management modules, dramatically reducing maintenance time while preserving network-specific adaptability through the data structure organization.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The mobility data is pre-organized in a unified tree structure in shared memory that anticipates the needs of multiple network types. This preliminary organization allows management modules to access and use the data without requiring separate preparation or duplication efforts for each network type, saving time during operations.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If each management module has its own mobility data storage, then data can be accessed locally without dependency on other modules, but the number of errors in entering mobility data increases

Engineering Contradiction:
Improvedata access independenceVSAvoiddata entry accuracy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent merges the mobility data storage into a single shared memory area that is accessible by all management modules. This eliminates data entry errors by ensuring there is only one source of truth for mobility data, while modules maintain operational independence by directly accessing the shared data as needed without requiring other modules to intervene.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3008927B1Method for managing the mobility of a node
Publication Date: 2019.07.31 AIRBUS DS SLC
  • EP3008927B1 patent drawingFigure 1
  • EP3008927B1 patent drawingFigure 2~3

AI summary

The invention concerns a method for managing the mobility of a mobile node (100) in a plurality of telecommunications networks (10, 20), said plurality of telecommunications networks (10, 20) comprising at least a first telecommunications network (10) and a second telecommunications network (20), said mobile node (100) comprising: - a memory area, in which there is stored a set of data concerning the mobility of the mobile node (100) in the plurality of networks (10, 20), - a first module for managing the mobility of said mobile node (100), configured to establish, through the first network (10), from at least one item of mobility data, a mobility session with a home agent (200), and, - a second module for managing the mobility of said mobile node (100), configured to establish, through the second network (20), from at least one item of mobility data, a mobility session with said home agent (200), the method being characterised in that, the first module being configured to access the set of mobility data stored in the memory area, it comprises a step of obtaining, by the second module, from the first module, at least one item of mobility data from the set of data that can be accessed by the first module.