HSS UDM IMEI Synchronization via Intermediary Notification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telecommunication networks face issues with IMEI synchronization across 4G and 5G domains, leading to incorrect decisions and inefficient notifications due to the lack of defined interworking between HSS and UDM when they are deployed as separate entities, resulting in duplicated or wrong notifications.

Innovation Solution

Implementing a method where HSS and UDM inform each other about IMEI changes, ensuring that the latest IMEI is synchronized in both domains, allowing for single notification of IMEI change events and local retrieval of IMEIs without additional interworking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If HSS and UDM are deployed as separate entities without defined interworking, then network flexibility and deployment options are improved, but IMEI synchronization and notification accuracy deteriorate

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidIMEI notification accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary mechanism where the HSS and UDM exchange IMEI change notifications through defined interfaces. When an IMEI changes in one network, the affected network node notifies the other network, ensuring synchronization without requiring tight coupling or merged deployment of HSS and UDM.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If HSS and UDM exchange IMEI change notifications frequently, then IMEI synchronization accuracy is improved, but network signaling overhead and complexity increase

Engineering Contradiction:
ImproveIMEI synchronization accuracyVSAvoidnotification system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent establishes subscription mechanisms in advance where network nodes subscribe to IMEI change events. When an IMEI change occurs, pre-configured notification procedures are automatically triggered, eliminating the need for continuous polling or complex real-time synchronization protocols.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If HSS retrieves IMEI from UDM for every IMS request, then IMEI data accuracy is improved, but network latency and response time increase

Engineering Contradiction:
ImproveIMEI data accuracyVSAvoidIMEI retrieval time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements a mechanism where the HSS proactively retrieves and caches the latest IMEI from the UDM in advance, triggered by IMEI change notifications. This allows the HSS to serve subsequent IMS requests with cached IMEI data locally, avoiding repeated real-time queries to the UDM.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates and maintains a local copy of the IMEI data in the HSS that is kept synchronized with the UDM through notification mechanisms. This local copy enables fast retrieval without requiring continuous access to the UDM, while still maintaining data accuracy through periodic updates via notifications.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20230171587A1IMEI retrieval and IMEI change notification in 5GC-EPC interworking scenarios
Publication Date: 2023.06.01 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20230171587A1 patent drawing
  • US20230171587A1 patent drawing
  • US20230171587A1 patent drawing

AI summary

According to an aspect, there is provided a method of operating a first network node (420; 430; 520; 530; 620; 630; 730; 740) in a first core network of a telecommunication network. The first network node (420; 430; 520; 530; 620; 630; 730; 740) is for managing data relating to subscribers of the first core network, and the telecommunication network further comprises a second core network having a second network node (420; 430; 520; 530; 620; 630; 730; 740) that is for managing data relating to subscribers of the second core network. The method comprises, after a first wireless device identifier for a first subscriber of the first core network and the second core network is changed to a second wireless device identifier, sending (1101) a first message to the second the second wireless device identifier for the first subscriber.