Network Node Identifier Mapping for 5G PubSub Terminal Association
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The conventional technical specifications lack a mechanism for enabling terminals to function as publishers or subscribers in the PubSub platform deployed in the 5G system, particularly due to issues with Network Address Translation (NAT) and complex cache release processing, leading to potential miss recognition of terminals during association management.
Innovation Solution
Introduce a network node with a reception and transmission unit to handle messages between the Data Collection Coordination Function (DCCF) and Access and Mobility Management Function (AMF), along with a control unit to store associations, enabling terminals to participate in the PubSub platform by enhancing payload container types and introducing new interfaces like Namf_DataManagement for transparent data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If terminals are enabled to participate in PubSub platform with NAT traversal, then service flexibility and adaptability are improved, but association management complexity and terminal recognition accuracy deteriorate due to complex cache release processing
Solution Approach 1:
The network node acts as an intermediary between terminals and the PubSub platform. It receives messages from terminals containing first identifiers, obtains second identifiers from AMF, establishes associations between these identifiers, and manages the caching relationships. This intermediary role simplifies terminal operations while maintaining accurate associations despite NAT address translations.
2Adaptability or versatility
If terminals are enabled to participate in PubSub platform, then service flexibility is improved, but terminal recognition accuracy deteriorates due to NAT address translation issues
Solution Approach 1:
The network node implements a feedback mechanism where it receives messages from terminals with first identifiers, queries AMF to obtain corresponding second identifiers, establishes bidirectional associations, and maintains cache relationships. This feedback loop ensures accurate terminal recognition by continuously updating and verifying identifier mappings despite NAT address translations.
3Ease of manufacture
If conventional cache release processing is used, then memory management is simplified, but terminal association accuracy deteriorates leading to miss recognition
Solution Approach 1:
The network node serves as an intermediary that manages cache associations between first identifiers (from terminals) and second identifiers (from AMF). It receives messages from terminals, obtains corresponding AMF identifiers, establishes and maintains accurate cache relationships, and releases caches appropriately. This intermediary management maintains association accuracy while simplifying the overall cache management process.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A network node includes: a reception unit configured to receive, from a DCCF (Data Collection Coordination Function), a message that includes: a first identifier configured by a terminal; information indicating an AMF (Access and Mobility Management Function); and a second identifier configured by the AMF; a transmission unit configured to transmit, to the DCCF, a response that is a response to the message and includes information indicating the node itself and a third identifier; and a control unit configured to store an association between the first identifier, the second identifier, and the third identifier.