Non-IP APN Embedding for IoT Traffic Prioritization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless network technologies face challenges in efficiently managing and prioritizing non-Internet Protocol (IP) data delivery for Internet of Things (IoT) devices, lacking a standardized method to embed Class of Service (CoS) and Quality of Service (QoS) indicators within Access Point Names (APNs) for differentiated service plans.
Innovation Solution
The implementation of a provisioning system that generates non-IP APNs with embedded CoS and QoS indicators, allowing for the differentiation of service plans and prioritization of traffic based on these indicators within the wireless network, enabling efficient data delivery between IoT devices and application servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-IP data delivery is implemented for IoT devices, then new service capabilities are enabled, but lack of standardized CoS and QoS embedding in APNs prevents efficient traffic prioritization
Solution Approach 1:
The patent applies parameter changes by embedding CoS and QoS indicators as additional parameters within the APN structure. This allows the network to differentiate and prioritize traffic based on these embedded parameters, resolving the contradiction by enabling efficient traffic management while maintaining the non-IP data delivery capability.
Solution Approach 2:
The provisioning system acts as an intermediary that generates APNs with embedded CoS and QoS indicators based on selected service plans. This intermediary function enables the translation of service requirements into standardized network parameters, allowing efficient traffic prioritization without compromising service versatility.
2Adaptability or versatility
If service plans are differentiated without standardized CoS and QoS indicators, then service customization is possible, but traffic prioritization and preemption cannot be effectively implemented
Solution Approach 1:
The patent embeds CoS and QoS indicators as standardized parameters within APNs, enabling reliable traffic prioritization and preemption while maintaining service plan differentiation. The provisioning system maps service plan characteristics to these standardized parameters, ensuring both customization and reliability.
Solution Approach 2:
The standardized APN structure with embedded CoS and QoS indicators serves multiple functions: it enables service plan differentiation, traffic prioritization, preemption, and efficient routing. This universal structure resolves the contradiction by making the same mechanism serve both customization and reliability requirements.
3Ease of operation
If APNs are used for network identification without embedded service indicators, then network connectivity is established, but Class of Service and Quality of Service control is lost
Solution Approach 1:
The patent merges network identification (APN) with service control indicators (CoS and QoS) into a single unified structure. This combination maintains the simplicity of APN-based connectivity while embedding service control capabilities, resolving the contradiction by eliminating the need for separate control mechanisms.
Solution Approach 2:
The enhanced APN structure performs multiple functions simultaneously: network identification, service plan differentiation, traffic prioritization, and QoS control. This multi-functional approach resolves the contradiction by maintaining ease of operation while reducing the need for additional complex control mechanisms.
Data Source
AI summary
A mobility management node in a wireless network receives message data from an Internet of Things (IoT) device. The mobility management node obtains a non-Internet Protocol (IP) Access Point Name (APN) associated with the message data, and extracts Class of Service (CoS) and/or Quality of Service (QoS) indicators embedded in the non-IP APN. The mobility management node queues and prioritizes the message data, among other message data, based on the extracted CoS and QoS indicators. The mobility management node dequeues and forwards the message data, among the other message data, from the mobility management node to a Service Capability Exposure Function (SCEF) node based on the extracted CoS and QoS indicators.


