US 10,560,968 B2
Broadcast messaging
David Edwin Splitz, Sandwich, MA (US); Dale McLeod Magley, Norton, MA (US); and Brent Dukes, Raynham, MA (US)
Assigned to Mueller International, LLC, Atlanta, GA (US)
Filed by Mueller International, LLC, Atlanta, GA (US)
Filed on Jun. 13, 2017, as Appl. No. 15/621,619.
Prior Publication US 2018/0359778 A1, Dec. 13, 2018
Int. Cl. H04W 74/08 (2009.01); H04W 74/04 (2009.01)
CPC H04W 74/085 (2013.01) [H04W 74/04 (2013.01)] 10 Claims
OG exemplary drawing
 
1. A method of avoiding response signal collisions, comprising the steps of:
broadcasting a message from a broadcasting device to a plurality of downstream devices, the message containing response window information dictating whether each downstream device targeted in the message must respond to the message, and if so, when each targeted downstream device should send its response to the message after successfully receiving the message;
receiving a response from at least one downstream device in the plurality of downstream devices that was commanded to respond and that successfully received the message, each such downstream device comprising a responding device, wherein each responding device sends its response when performing an upload of data collected by the responding device; and
determining whether every targeted downstream device successfully received the message,
wherein, for required responses, the response window information is selected from at least one of the group comprising an instruction that each responding device commence its upload at a predefined recurring time, an instruction that each responding device perform its upload immediately following expiration of a predefined delay period commencing at a time of sending of the message, and an instruction that each responding device pick a random time within a predefined time window in which to perform its upload,
wherein the broadcasting device receives the message from a server, and wherein the server has a memory containing a first list, the first list reciting identifications of all downstream devices from which a response to the message is expected, and containing a second list, the second list reciting identifications of all responding devices, and wherein the step of determining whether every downstream device targeted in the message successfully received the message further comprises the steps of
comparing the first list to the second list,
ascertaining whether the server failed to receive a response to the message from any downstream device identified in the first list, and
re-broadcasting the message to each downstream device from which the server failed to receive a response,
wherein the step of determining whether every downstream device targeted in the message successfully received the message further comprises the steps of:
receiving, from each downstream device successfully receiving a re-broadcast message, each such device comprising a re-broadcast responding device, a response when each re-broadcast responding device performs an upload of data collected by each re-broadcast responding device, a time of each upload dictated by the response window information,
producing an updated second list by adding, to the second list, identifications of each re-broadcast responding device,
comparing the first list to the updated second list,
ascertaining whether the server failed to receive a response to the re-broadcast message from any downstream device identified in the first list,
determining whether a pre-defined limit on a number of broadcasts has been reached, and
responsive to determining that the pre-defined limit on the number of broadcasts has not been reached, again re-broadcasting the message to all downstream devices from which the server has still failed to receive a response.