Network Application Protocol Interface for Transport Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication networks, based on the OSI architecture, lack an efficient interface for applications to influence packet transport behavior, leading to suboptimal utilization of network resources and reduced Quality-of-Service, especially in multipath transmission scenarios.
Innovation Solution
A Network Application Protocol Interface (NAPI) is introduced between the application layer (Layer 7) and layers 3 to 5 of the communication network to provide information about application-specific quality requirements, enabling the transport layer to manage data streams efficiently and optimize scheduling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If applications cannot directly influence packet transport behavior through the standard OSI architecture, then the network structure remains simple and standardized, but network resource utilization becomes inefficient and Quality-of-Service deteriorates
Solution Approach 1:
The NAPI is introduced as an intermediary component between the application layer and transport layer. It receives quality requirement information from applications and forwards it to the transport layer for scheduling decisions, enabling applications to influence packet transport behavior without fundamentally altering the OSI architecture. This mediator approach resolves the contradiction by adding controlled complexity only where needed while maintaining overall architectural simplicity.
Solution Approach 2:
The NAPI functionality is segmented into distinct modules: a quality requirement information receiving module that interfaces with applications, and a transport layer interface module that communicates with the transport layer. This segmentation allows the system to add application influence capabilities while keeping each module's complexity manageable and well-defined.
2Reliability
If cross-layer information exchange interfaces are implemented (as in US 2016/056927 A1), then Quality-of-Service improves through optimized media data delivery, but the system complexity increases with additional interface layers
Solution Approach 1:
The NAPI is designed as a universal interface that handles multiple functions: receiving quality requirement information from various applications, translating this information into transport layer scheduling parameters, and supporting different data stream types. This multi-functionality reduces the need for multiple specialized interfaces, thereby improving QoS while limiting complexity growth.
Solution Approach 2:
The NAPI acts as a mediator that simplifies cross-layer communication by providing a standardized interface between application layer quality requirements and transport layer scheduling. Instead of implementing complex direct interactions between multiple layers, the NAPI mediates this communication, improving reliability while controlling interface structure complexity.
3Reliability
If no direct interface exists between application layer and transport layer, then the OSI architecture remains intact and simple, but applications cannot efficiently influence packet transport behavior resulting in reduced Quality-of-Service
Solution Approach 1:
The NAPI serves as a mediator that enables application control over packet transport behavior by receiving quality requirement information from applications and forwarding it to the transport layer. This intermediary approach directly addresses the contradiction by providing the needed control capability while maintaining architectural integrity.
Solution Approach 2:
The NAPI implements a feedback mechanism where application quality requirements are communicated to the transport layer, which then adjusts packet scheduling accordingly. This feedback loop enables applications to efficiently influence transport behavior, improving Quality-of-Service while maintaining ease of operation through automated control.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The disclosure relates to a network entity (200), comprising: a transport layer interface (201) configured to transport a plurality of application-specific data streams (202) over a communication network (250); a network application protocol interface (NAPI) (137) configured to receive information about application-specific quality requirements (211) with respect to reliability, throughput, latency and/or jitter requirements per application-specific data stream (202) from an application layer (210) of the communication network (250); and a processor (205), configured to schedule transmission of the plurality of application-specific data streams (202) over the communication network (250) according to a transport schedule (206) which is based on the information about the application-specific quality requirements (211) received via the NAPI (137) from the application layer (210).