Multicast PQoS Flow Creation via Broadcast and Node Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communications network protocols, such as MoCA 1.x, lack effective multicast group management, leading to issues like low-performing nodes blocking PQoS transmissions and unnecessary multicast traffic flooding, which affects buffer and host bandwidth.
Innovation Solution
Implementing a method that creates a broadcast flow for PQoS transmissions using a 'PQoS Create Flow' transaction, with nodes opting out by responding with 'RESPONSE_CODE_UNINVOLVED', and explicit multicast channel management through an IGMP server, ensuring only interested nodes receive traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If broadcast techniques are used for multicast transmissions in MoCA 1.x networks, then multicast traffic can be delivered to all nodes, but low-performing nodes block PQoS transmissions even when they don't need to receive the traffic
Solution Approach 1:
The patent segments the network into multicast groups based on interest, allowing the network to be divided into subsets of nodes that share common multicast interests. This segmentation enables selective delivery to only those nodes that need the traffic, preventing low-performing nodes from blocking transmissions they don't require while maintaining reliable PQoS transmissions for interested nodes.
Solution Approach 2:
The patent implements local quality by allowing different nodes to have different reception characteristics for multicast traffic. Nodes can selectively receive or ignore multicast packets based on their interest, rather than uniformly processing all broadcast traffic. This local differentiation prevents low-performing nodes from becoming bottlenecks for traffic they don't need.
2Quantity of substance
If broadcast techniques are used for multicast transmissions, then all nodes receive all multicast traffic, but nodes are flooded with unwanted traffic consuming buffer and bandwidth resources
Solution Approach 1:
The patent extracts unwanted multicast traffic from the broadcast stream at the node level. Nodes examine incoming multicast packets and discard those not intended for them, rather than processing and forwarding all broadcast traffic. This extraction mechanism prevents consumption of buffer and bandwidth resources for unwanted traffic while maintaining delivery of desired multicast content.
Solution Approach 2:
Instead of having nodes selectively receive only desired traffic from a broadcast stream, the patent inverts the approach by having nodes receive all broadcast traffic but actively filter out unwanted packets. This inversion allows nodes to maintain simple reception logic while implementing intelligent filtering to eliminate wasteful consumption of resources on unwanted traffic.
3Ease of operation
If multicast group management is not implemented, then the protocol implementation is simpler, but traffic cannot be selectively delivered to specific nodes
Solution Approach 1:
The patent implements self-service by allowing nodes to autonomously manage their own multicast group memberships and filtering preferences without requiring complex centralized multicast management. Each node independently determines which multicast traffic to receive and filters accordingly, maintaining protocol simplicity while enabling selective traffic delivery through distributed self-management.
Data Source
AI summary
When one node has information to transmit to a group of nodes using a parameterized quality of service (PQoS) transmission, a broadcast flow is created rather than creating a multicast flow, which is not available. While the flow is created as a broadcast flow, if the flow is to be directed to less than all of the nodes on the network, then the flow will be considered a Multicast PQoS flow. The broadcast flow is created using a process that is known as a “PQoS Create Flow” transaction.