Controlling multiple nodes to execute messages only once
First Claim
1. A method of managing one or more nodes comprising the steps of:
- (a) forming a packet comprising a network layer header, including a destination address for routing the packet to a destination, a second header identifying a syntax and semantic by which a payload of the packet may be parsed in a predefined fashion, and the payload containing a message to be executed by each of one or more to-be-managed nodes to which the packet is destined, and(b) transmitting the packet plural times to a plurality of nodes, including the one or more to-be-managed nodes,wherein the message in the particular packet is executed only a single time regardless of the number of times that a copy of the particular packet is received in the state enabling execution by the to-be-managed nodes of the message therein, andwherein the transmission of the particular packet plural times increases the likelihood that each of the to-be-managed nodes receives at least one copy of the particular packet in the state enabling execution of the message contained therein.
9 Assignments
0 Petitions
Accused Products
Abstract
A broadcast satellite network transmits from a source to multiple router nodes digital real-time program information and best-effort data. The router nodes are specifically suited for extracting best-effort data streams from the multiplexed signal received via, e.g., a satellite. A number of management techniques are disclosed. According to one technique, a packet is formed having a network layer header, including a destination address for routing a packet to a destination, a second header identifying a syntax and semantic by which a payload of the packet may be parsed in a predefined fashion, and a payload containing a command to be executed by each of one or more to-be-managed nodes to which the packet is destined. The packet is transmitted a plural amount of times to a plurality of nodes, including the one or more to-be-managed nodes, but the command in the particular packet is executed only a single time. According to other techniques, the nodes are divided into groups. In one technique, a unique identifier is assigned to each group and the packet containing the command contains the identifier. The packet is transmitted once but received by all nodes, including the group of nodes to which the same identifier was assigned. Only those nodes of the group with the same identifier execute the command. According to anther embodiment, a manager node maintains a list of the addresses of all nodes in a group and automatically transmits the packet once to each address, thereby enabling automatic communication of the same packet to multiple nodes.
15 Citations
23 Claims
-
1. A method of managing one or more nodes comprising the steps of:
-
(a) forming a packet comprising a network layer header, including a destination address for routing the packet to a destination, a second header identifying a syntax and semantic by which a payload of the packet may be parsed in a predefined fashion, and the payload containing a message to be executed by each of one or more to-be-managed nodes to which the packet is destined, and (b) transmitting the packet plural times to a plurality of nodes, including the one or more to-be-managed nodes, wherein the message in the particular packet is executed only a single time regardless of the number of times that a copy of the particular packet is received in the state enabling execution by the to-be-managed nodes of the message therein, and wherein the transmission of the particular packet plural times increases the likelihood that each of the to-be-managed nodes receives at least one copy of the particular packet in the state enabling execution of the message contained therein. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 19)
-
-
11. A method for managing one or more nodes in a network comprising the steps of:
-
(a) receiving one or more times a particular packet comprising a network layer header, including a destination address for routing the packet to a destination, a second header identifying a syntax and semantic by which a payload of the particular packet may be parsed in a predefined fashion, and the payload containing a message to be executed by each of one or more to-be-managed nodes to which the particular packet is destined, (b) if information in each received copy of the particular packet indicates that the particular packet is destined for a particular node, processing the particular packet, including, in response to detecting the second header, obtaining the message in the particular packet, if possible, and if at least one copy of the particular packet is received in a state enabling execution of the obtained message, executing the obtained message in the particular packet only a single time regardless of the number of times that the particular packet is received in the state enabling execution by the to-be-managed nodes of the obtained message therein, wherein the transmission of the particular packet plural times increases the likelihood that each of the to-be-managed nodes receives at least one copy of the particular packet in the state enabling execution by the to-be-managed nodes of the message contained therein. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18)
-
-
20. A packet for causing one or more to-be-managed nodes to robustly receive a to-be-executed message from a source in the absence of a return path from the to-be-managed nodes to the source comprising:
-
(a) a network layer header, including a destination address designating that the packet is to be received by a group of nodes, (b) a second header, identifying the packet as being parseable according to a predefined syntax and semantic, (c) an identifier designating each of the to-be-managed nodes as recipients of the packet, (d) a message to be executed, and (e) version information, for preventing one of the to-be-managed nodes from executing the message more than one time. - View Dependent Claims (21)
-
-
22. A sequence of plural packets for causing one or more to-be-managed nodes to robustly receive a to-be-executed message from a source in the absence of a return path from the to-be-managed nodes to the source comprising:
-
(a) a first packet containing a message to be executed, (b) one or more second packets, each of which is identical to the first packet, and (c) a third packet following the first and second packets containing a message which initiates execution of the command by the to-be-managed node only once regardless of the number of times the message is received at a to-be-managed node. - View Dependent Claims (23)
-
Specification