Multi-channel power line exchange protocol
First Claim
1. A method for arbitrating use of a network medium to avoid collisions caused by multiple nodes attempting to transmit data on the network medium at the same time, said method comprising the steps of:
- sending a token packet from an active server to a first client node, said token packet granting network medium access to said first client node;
sending an end of token session packet from said first client to said server, said end of token session packet relinquishing network medium access by said first client node; and
broadcasting a lineup insertion packet from said server, said lineup insertion packet comprising an address mask, said server configure to wait for a prescribed time period after broadcasting said lineup insertion packet to allow a second client node to send a lineup insertion response packet to said active server, said second client node sending said lineup insertion response packet if an address of said second client node falls within a range of addresses given by said address mask.
3 Assignments
0 Petitions
Accused Products
Abstract
A scalable networking protocol that allows multiple nodes to communicate via a multi-channel network medium is described. The networking protocol allows any node on the network to assign itself as the active network server. The active network server polls client nodes based on a lineup card. The lineup card includes a high priority queue for low-latency devices, and a low priority queue for devices that can tolerate higher latencies. Network information is sent on the channels as fragments. The protocol provides bad-channel detection and retransmission of fragments in a fragment-by-fragment basis. Support for streaming data or asynchronous data is provided by allocating time slots on the network and allowing two intelligent nodes to talk directly to each other during count-limited token sessions, as arbitrated by the active network server. The network node serving as the active network server can be changed on a dynamic basis, and is typically determined by the first node initiating a transmit request on a sleeping network. Client nodes are addressed by dynamic-polling using an address isolation scheme.
117 Citations
15 Claims
-
1. A method for arbitrating use of a network medium to avoid collisions caused by multiple nodes attempting to transmit data on the network medium at the same time, said method comprising the steps of:
-
sending a token packet from an active server to a first client node, said token packet granting network medium access to said first client node; sending an end of token session packet from said first client to said server, said end of token session packet relinquishing network medium access by said first client node; and broadcasting a lineup insertion packet from said server, said lineup insertion packet comprising an address mask, said server configure to wait for a prescribed time period after broadcasting said lineup insertion packet to allow a second client node to send a lineup insertion response packet to said active server, said second client node sending said lineup insertion response packet if an address of said second client node falls within a range of addresses given by said address mask. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A networking architecture to provide isochronous and non-isochronous data transmission on a network medium, comprising:
-
an active server node, said active server node configured to send a lineup insertion packet containing an address mask and listen to said network medium for a specified period of time after sending said lineup insertion packet; and at least one client node configured to request insertion onto a lineup card of said active server node by responding to said lineup insertion packet, said active server node configured to provide a token to said at least one client node, said at least one client node configured to transmit on said medium for no more than a specified time period before sending an end of token session packet to said active server node. - View Dependent Claims (14, 15)
-
Specification