Hierarchical Gateway QoS Allocation for Vehicle Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network configurations in vehicle computers face challenges in managing quality-of-service (QoS) guarantees across multiple domains, leading to inefficiencies and increased complexity due to the need for centralized resource management and complex communication paths, which can affect functional safety and scalability.
Innovation Solution
A method for configuring QoS in a network with a tree-shaped structure of gateways, where each gateway allocates and manages quality-of-service quantities in a decentralized manner, allowing for fine-grained access control and efficient communication between domains, using a secure gateway to ensure end-to-end guarantees and reduce the number of logic connections, thereby enhancing scalability and fail-safe operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If centralized resource management is used for QoS configuration, then QoS guarantees can be maintained across domains, but network complexity and administration overhead increase significantly
Solution Approach 1:
The network is divided into multiple domains with hierarchical QoS management. Each domain has its own QoS parameters and policies, allowing decentralized configuration while maintaining overall QoS guarantees through domain boundary enforcement. This segmentation reduces the complexity of managing QoS across the entire network centrally.
2Adaptability or versatility
If multiple logic connections are established for inter-domain communication, then communication paths are available, but the number of connections increases complexity and affects scalability
Solution Approach 1:
Domain boundary elements act as intermediaries that manage communication between domains. Instead of establishing multiple direct logic connections between all domains, these boundary elements mediate the communication, reducing the number of direct connections needed while maintaining communication flexibility and adaptability.
3Reliability
If fine-grained access control is implemented across all domains, then functional safety is improved, but the configuration and management complexity increases
Solution Approach 1:
Each domain is assigned specific QoS parameters and access control policies tailored to its functional requirements. This local quality approach allows fine-grained access control to be implemented where needed for functional safety without requiring complex centralized configuration, as each domain manages its own security and QoS settings independently.
4Reliability
If centralized QoS management is used, then QoS policies can be uniformly enforced, but network scalability is limited due to administration overhead
Solution Approach 1:
The network is segmented into independent domains that can be configured and managed separately. Each domain enforces QoS policies locally according to its specific requirements, enabling the network to scale by adding new domains without increasing centralized administration overhead, while still maintaining uniform QoS enforcement through standardized domain boundary protocols.
Data Source
AI summary
A method for configuring quality-of-service quantities in a network including a first network segment has a first gateway as a network subscriber and each of multiple second network segments has a second gateway as a network subscriber. The first gateway and the second gateways are logically set up in a tree structure having multiple stages. Each gateway in a stage is connected in a data-conducting manner to precisely one gateway in a stage situated below. The first gateway forms the lowest stage. Each gateway makes a quality-of-service quantity available for the forwarding of data. The method includes: an addressed gateway receiving a quality-of-service request from a requesting network subscriber; checking whether the addressed gateway has a sufficient free quality-of-service quantity; if not, rejecting the quality-of-service request by a negative reply; if so, forwarding the quality-of-service request to the gateway in the stage situated below.