Subscriber Data Node Flow Descriptions for NIDD QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication networks lack a mechanism to differentiate and ensure Quality of Service (QoS) for Non-Internet Protocol (IP) Data Delivery (NIDD) traffic, as existing methods cannot identify and prioritize different types of data exchanged between Machine-Type Communication (MTC) applications, leading to inconsistent handling of critical and non-critical data.
Innovation Solution
Introduce a non-IP flow description mechanism that includes an application identifier and a non-IP flow identifier, allowing network nodes to associate and identify data specifically per application, enabling traffic differentiation and appropriate QoS treatment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing NIDD traffic handling methods are used, then all NIDD traffic is treated uniformly, but this prevents differentiation and QoS assurance for different application types
Solution Approach 1:
The patent segments NIDD traffic into different categories by introducing flow descriptors that identify specific application types (e.g., smart metering, telehealth, smart grid). Each flow descriptor contains application-specific parameters that enable the network to differentiate and apply appropriate QoS policies to each segment of traffic, rather than treating all NIDD traffic uniformly.
Solution Approach 2:
The patent changes the parameters used for traffic identification by introducing new flow descriptor parameters including application identifiers, message types, and QoS requirements. These parameter changes enable the network nodes to recognize and differentiate between various application traffic types, allowing for customized QoS handling based on the specific application needs.
2Ease of operation
If uniform NIDD traffic handling is applied, then implementation is simple, but critical and non-critical data cannot be prioritized differently
Solution Approach 1:
The patent applies preliminary action by pre-defining flow descriptors and QoS policies for different application types before actual data transmission occurs. The network nodes are pre-configured with application identifiers and corresponding QoS rules, enabling automatic differentiation and prioritization when NIDD traffic arrives, without requiring complex real-time analysis.
3Reliability
If application-specific identification is implemented, then QoS differentiation is enabled, but the signaling overhead between network nodes increases
Solution Approach 1:
The patent creates a universal flow descriptor structure that can identify multiple application types using a standardized format. This multi-functional descriptor can accommodate different application identifiers (smart metering, telehealth, smart grid, etc.) within a single signaling framework, reducing the need for multiple separate signaling mechanisms and thereby limiting the increase in signaling overhead.
Data Source
AI summary
A method performed by a subscriber's data node for differentiating Non-IP Data Delivery, NIDD, traffic in a communication network. The communication network comprises the subscriber's data node, a serving node and an exposure function node. The subscriber's data node receives, from the exposure function node, a NIDD authorization request comprising a first identifier. The first identifier comprises any one out of a service capability server identifier, an application server identifier and an application function identifier. The subscriber's data node generates a non-IP flow description, based on the received first identifier. The non-IP flow description comprises an application identifier and a non-IP flow identifier for the NIDD authorization. The subscriber's data node transmits the non-IP flow description towards the serving node. The subscriber's data node transmits a NIDD authorization response comprising the non-IP flow identifier, towards the exposure function node.