Non-IP Data Delivery via RDS Port Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In non-Internet Protocol (IP) data delivery systems, particularly in 3GPP and 5G networks, the challenge arises when multiple non-IP PDN connections share the same access point name (APN), leading to incorrect delivery of mobile originated (MO) non-IP data to the wrong application and incorrect charging data recording, due to the Service Capability Exposure Function (SCEF) inability to accurately identify the correct EPS bearer for data transmission.
Innovation Solution
Implementing Reliable Data Service (RDS) port configurations to establish precise associations between non-IP connections and applications, using RDS port configurations managed statically or dynamically, ensuring correct routing of non-IP data by correlating EPS bearer identities with RDS port configurations, thereby ensuring accurate delivery and charging records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple non-IP PDN connections share the same APN, then network resource utilization is improved, but data delivery accuracy deteriorates
Solution Approach 1:
The patent segments the identification process by introducing RDS port configurations as a distinct identification layer. Each non-IP PDN connection is associated with specific RDS port configurations, allowing the SCEF to differentiate between connections sharing the same APN through unique port configuration identifiers rather than relying solely on APN matching.
Solution Approach 2:
The patent introduces RDS port configurations as an intermediary identification mechanism between the APN and the EPS bearer. This intermediary layer provides additional discrimination capability, enabling the SCEF to accurately identify the correct EPS bearer even when multiple connections share the same APN by matching both APN and RDS port configuration parameters.
2Ease of operation
If the SCEF uses basic APN matching to route non-IP data, then routing simplicity is improved, but application identification accuracy deteriorates
Solution Approach 1:
The patent applies preliminary action by pre-configuring RDS port configurations and establishing their associations with specific applications and EPS bearers before data routing occurs. This pre-establishment of identification parameters allows the SCEF to perform accurate application identification without adding complexity to the actual data routing process, as the matching criteria are prepared in advance.
Solution Approach 2:
The patent makes the RDS port configuration mechanism universally applicable across multiple non-IP PDN connections sharing the same APN. Rather than creating separate routing mechanisms for each connection, the universal RDS port configuration approach provides a unified identification method that works for all connections, maintaining routing simplicity while improving identification accuracy.
3Adaptability or versatility
If the system supports multiple PDN connections with the same APN, then connection versatility is improved, but charging record accuracy deteriorates
Solution Approach 1:
The patent segments the charging identification process by incorporating RDS port configuration parameters into the charging data record generation. Each charging record is associated with specific RDS port configurations, which uniquely identify the application and EPS bearer combination. This segmentation ensures that even when multiple PDN connections share the same APN, each connection's charging records are accurately differentiated through their unique RDS port configuration identifiers.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and apparatuses for non-Internet protocol (IP) data delivery are disclosed. According to an embodiment, a network exposure node obtains associations between multiple non-IP connections between a terminal device and the network exposure node and multiple reliable data service (RDS) port configurations configured to the network exposure node by an application related node for multiple applications. The network exposure node receives, from the application related node, a message that is destined to the terminal device and includes non-IP data and one of the multiple RDS port configurations. The network exposure node transfers the non-IP data to the terminal device through one of the multiple non-IP connections that is associated with the one of the multiple RDS port configurations according to the obtained associations.