5G Network Node Mediation for Terminal PubSub Subscription
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The conventional technical specifications lack a mechanism for terminals to function as publishers or subscribers in the PubSub platform deployed in 5G systems, leading to issues such as incomplete communication methods, GPSI/SUPI determination failures, and complex cache release processing when specific AFs are behind NAT.
Innovation Solution
Introduce a network node with reception, control, and transmission units to manage payload containers and correlation IDs, enabling terminals to participate in the PubSub platform by enhancing payload container types and introducing Namf_DataManagement for transparent communication with DCCF and MFAF.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the PubSub platform is deployed in 5G system with conventional technical specifications, then the platform architecture can be established, but terminals cannot function as publishers or subscribers leading to incomplete communication methods
Solution Approach 1:
The network node is designed to handle multiple functions: it acts as an intermediary for terminals wanting to subscribe to events, manages payload containers with different types (subscribe, event notification, etc.), and communicates with both DCCF and MFAF. This multi-functional design enables terminals to participate in PubSub operations without requiring separate dedicated mechanisms for each operation type.
Solution Approach 2:
The network node serves as an intermediary between terminals and the PubSub platform (DCCF/MFAF). When a terminal wants to subscribe to an event or publish an event notification, the network node receives the message, determines the appropriate destination based on payload container type, and forwards it accordingly. This intermediary role simplifies terminal implementation while maintaining full PubSub functionality.
2Adaptability or versatility
If specific AFs are placed behind NAT, then network flexibility is improved, but GPSI/SUPI determination fails and cache release processing becomes complex
Solution Approach 1:
The network node acts as a trusted intermediary that maintains the association between terminal identifiers (GPSI/SUPI) and their current network locations. Even when AFs are behind NAT and terminal locations change, the network node preserves the correct identifier mappings, ensuring reliable identifier determination regardless of network configuration changes.
Solution Approach 2:
The network node pre-establishes and maintains the association between terminal identifiers and location information before NAT-related issues occur. By having this information ready in advance and updating it proactively as terminals move or network configurations change, the system avoids the complexity of real-time identifier resolution through NATed networks.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A network node includes: a reception unit configured to receive, from a terminal, a message including a payload container whose type is subscribe; a control unit configured to determine a connection to a DCCF (Data Collection Coordination Function) based on the payload container type; and a transmission unit configured to transmit, to the DCCF, a message including the payload container, information indicating a node itself, and a correlation ID. The control unit stores an association between the terminal, the information indicating the node itself, and the correlation ID.