MULTI-ACKED MULTICAST PROTOCOL

Abstract

Multicast transmissions do not allow for individual receivers to acknowledge that data was received by each receiver in the network. This is not acceptable for isochronous systems that require specific levels of QoS for each device. A multimedia communications protocol supports using multicast transmissions (one-to-many) in multimedia isochronous systems. A transmitter establishes a Multi-ACKed Multicast protocol within which a group of receiving devices can acknowledge the multicast transmission during a multi-acknowledgment period.

Claims

1. A method, comprising: providing a contention period in which a transmitter is granted contention free access to a medium; communicating using a Multi-ACKed Multicast protocol comprising: initialization of a multicast group of receivers by assigning an acknowledgement time within a multi-acknowledgment period based on Frame Length (FL) specified in a Start of Frame (SOF) delimiter; transmitting by a transmitter of a multicast transmission comprising a first SOF delimiter and a medium access (MAC) data payload; wherein the first SOF delimiter contains a first FL field that establishes a multi-acknowledgment period; transmitting by each receiver of an acknowledgement at its acknowledgement time to the transmitter of the multicast transmission during the multi-acknowledgment period; and wherein each acknowledgment contains a second FL field that indicates a time until the FL specified in the first FL field of the first SOF delimiter expires; and terminating multicast transmission at the use of one of: a selective ACK (SACK) or expiration of the multi-acknowledgment period, wherein communicating using the Multi-ACKed Multicast protocol is compatible and compliant with a native communications protocol.

2. The method of claim 1, wherein the Multi-ACKed Multicast protocol is compatible and compliant because it does not affect interoperability with non-participating group receivers in the network that are using the native protocol.

3. The method of claim 1, wherein the Multi-ACKed Multicast protocol is compatible and compliant because it may be terminated without affecting interoperability of any device in the network using the native protocol.

4. The method of claim 1, wherein the acknowledgment time is established at one of: time of manufacture of the group of receivers or by a user of each receiver.

5. The method of claim 1, wherein the acknowledgement time is calculated by the receivers based on an offset time multiplied by a device group sequence number.

6. The method of claim 1, where the acknowledgement is a Reverse SOF (RSOF) delimiter containing the FL in the second FL field that is calculated to be equal to the time remaining in the FL of the first FL field.

7. The method of claim 1, wherein the acknowledgement contains digital information about communications quality, further comprising using the digital information about communications quality by the transmitter to determine best parameters to use in a common Tone Map for subsequent multicast transmissions.

8. The method of claim 1, further comprising: utilizing a second and subsequent SOF delimiter having a tone map for a subgroup of devices whose acknowledgment window falls after the first SOF but before one of: a subsequent SOF, or SACK or expiration of the multi-acknowledgment period; wherein each tone map is used to optimize communications efficiency for that subgroup of receivers.

9. The method of claim 8, further comprising: discontinuing the multicast transmission in favor of a native protocol method when the transmitter determines that the performance of the network is not as effective as a native protocol transmission.

10. The method of claim 9, wherein the native distribution protocol method is unicast.

11. A method, comprising: receiving by a receiver of a multicast transmission which includes a first start of frame (SOF) delimiter and a medium access (MAC) data payload, wherein the first SOF contains a first Frame Length (FL) field that establishes a multi-acknowledgment period; responding by the receiver with a transmission of an acknowledgement at an acknowledgement time during the multi-acknowledgment period, wherein the acknowledgment contains a second FL field that indicates a time until a duration of the multi-acknowledgment period expires; and calculating the acknowledgment time by the receiver based on an offset time multiplied by a device group sequence number.

12. The method in claim 11, further comprising terminating multicast transmission in response to a selective ACK (SACK) by the receiver.

13. The method in claim 11, further comprising terminating multicast transmission in response to expiration of the multi-acknowledgment period.

14. The method in claim 11, where the acknowledgement is a Reverse SOF (RSOF) delimiter containing the second FL field.

15. The method of claim 11, wherein the acknowledgement contains digital information about communications quality, further comprising using the digital information about communications quality to determine one or more best parameters to use in a common Tone Map for subsequent multicast transmissions.

16. A multicast communications method for a carrier sense multiple access (CSMA) network, comprising: transmitting, by a transmitter, of a multicast transmission to a plurality of receivers comprising a first start of frame (SOF) delimiter, a second SOF delimiter and a medium access (MAC) data payload, wherein the first SOF delimiter contains a first Frame Length (FL) field that establishes a multi-acknowledgment period and wherein the multicast transmission is terminated by the use of one of: a selective ACK (SACK) by one of the receivers and an expiration of the multi-acknowledgment period; wherein the second SOF delimiter contains a tone map that is optimized for a subgroup of receivers whose acknowledgment window falls at one of: after the second SOF delimiter but before a subsequent SOF delimiter, or SACK or expiration of the multi-acknowledgment period specified in the first FL field; transmitting, by each of the receivers, of an acknowledgement at an acknowledgement time during the multi-acknowledgment period to the transmitter of the multicast transmission; and wherein the acknowledgment contains a second FL field that indicates a time until a duration of the multi-acknowledgment period expires.

17. The method in claim 16, wherein the acknowledgement time is established by one of: at time of manufacture of a group of devices which include the receivers or by a user of each receiver.

18. The method in claim 16, wherein the acknowledgment time is calculated by each of the receivers based on an offset time multiplied by a device group sequence number.

19. The method in claim 16, where the acknowledgement is a Reverse SOF (RSOF) delimiter containing the second FL field that indicates information calculated to be equal to a time remaining in the multi-acknowledgment period set by the first FL field.

20. The method of claim 16, wherein the acknowledgement contains digital information about communications quality, further comprising using the digital information about communications quality by the transmitter to determine one or more best parameters to use in a common Tone Map for subsequent multicast transmissions.

21. The method of claim 16, wherein each tone map is used to optimize the communications efficiency for that subgroup of receivers.

22. The method of claim 16, wherein a link identification (LID) is used by different SOF delimiters to create separate subgroups of receivers.

23. The method of claim 16, wherein the acknowledgment contains digital information about communications quality, and further comprising using the digital information about communications quality by the transmitter to group the receivers into subgroups that share a subgroup-specific Tone Map that is optimized for that subgroup; wherein the Tone Map is used by the SOF delimiter and the devices within the subgroup are assigned to acknowledgement times at one of: after the SOF delimiter and before a subsequent SOF, or SACK or expiration of the multi-acknowledgment period specified by the first FL.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0009] FIG. 1 illustrates an example of a MPDU bursting sequence;

[0010] FIG. 2 illustrates an example of the bidirectional burst sequence:

[0011] FIG. 3 illustrates interframe spacing used in bidirectional bursting;

[0012] FIG. 4 illustrates the multi-acknowledgement period according to an embodiment;

[0013] FIG. 5 illustrates an example of a powerline communication multimedia network protocol using SOF and RSOF according to an embodiment; and

[0014] FIG. 6 illustrates an example of a powerline communication multimedia network protocol using multiple SOFs per burst and RSOF according to an embodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

[0015] The making and using of embodiments are discussed in detail below. It should be appreciated, however, that the present disclosure provides many applicable inventive concepts that may be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention.

[0016] Embodiments are described, without limitation, in a specific context of a protocol method and apparatus used to minimize communications packet latency and jitter for data used by multimedia devices such as an audio system wherein all of the individual network devices act as a group that has isochronous QoS requirements in order to deliver one combined experience. This disclosure also uses the HomePlug AV specification as contextual framework (including terms) for presenting the invention, although the disclosed invention is not limited to that protocol. In this disclosure, receiver is a topology term to help distinguish between a multicast transmitter and the receiving multicast destinations, but all transmitters and receivers described here are functionally transceivers.

[0017] In accordance with the present disclosure, network initialization data is programmed, by one or more methods such as a user interface, at the time of manufacture or a discovery protocol, with the digital information about devices on the network that are part of a group of multimedia devices that function together, such as an audio system that is rendering one music file. The digital information includes identifiers (such as device ID, MAC ID, Link ID), topology digital information (such as a sequence number for all of the devices in the network that define the device order within the group), a sequence back-off value, as well as delimiter frame lengths and other information as embodied below. The initialization data can be field programmable in order to allow equipment to be replaced or repurposed after the sale or installation.

[0018] In accordance to an embodiment, FIG. 4 illustrates a method of using the multi-acknowledgment period for the Multi-ACKed Multicast protocol. When the transmitter has won a CSMA contention process 400 of a carrier sense multiple access (CSMA) protocol, the transmitter transmits a start of frame (SOF) delimiter 410 which contains data including the frame length (FL) field 420 (a digital value representing duration in time) and assignment of Multi-ACK time windows. It also transmits the MAC protocol data unit (MPDU) payload 430.

[0019] Reference is now also made to FIG. 5. The multicast transmission is addressed to all of the members of a group of receiving devices 520 that share a common function (such as in the example of audio speakers). It is followed by a multi-acknowledgment period 440 during which each receiving device in the multicast group acknowledges the status of the last multicast transmission at its assigned acknowledgement time (570, 575, 580 and 585). The acknowledgement delimiter is a reverse start of frame (RSOF) delimiter 590. The RSOF delimiter does not transmit any payload, but does contain frame length 598a-d that extends to the end of the FL allocated by the SOF 425. Because the FL sent within the RSOF indicates when the multi-acknowledgment period is over, any network device that may be hidden to the original transmitter can use the RSOFs to determine when to contend for access. The RSOF's acknowledgment time for each device in the multicast group is part of the initialization protocol previously mentioned. The specific receiver's acknowledgement time can be assigned to each receiver from the end of the MPDU payload, or a receiver may be assigned a unique sequence number within the multicast group and calculate its acknowledgment time based on an offset time (transmitted in the SOF) multiplied by the receiver's sequence number. For example, the SOF may transmit a SOF FL number that was generated by adding the RSOF duration plus a time space between the RSOFs to account for timing variations (the RSOF interfame spacing (RSIFS)), times the number of devices in the multicast group. The receiver can multiply its sequence number by the FL divided by the number if devices in the multicast group to calculate the acknowledgement time for each receiver. Each receiver than sends a RSOF in its time window as an acknowledgement. If any RSOF is received by the original transmitter during the multi-acknowledgment period, the original transmitter concludes that there were no collisions with other devices on the network. If any receiver does not acknowledge or acknowledges that the data was not received, the original transmitter can retransmit the packet. If a receiver does not acknowledge the packet, the transmitter can retransmit the packet or extend the acknowledgement window by transmitting another SOF before the FL expires and request the receiver to acknowledge again. Any device can terminate the multi-acknowledgment period by sending a selective acknowledgment (SACK) delimiter, but the preferred method is for the last device in the multicast group sequence to terminate the multi-acknowledgment period. At the end of the original FL, all devices in the network look for the next delimiter and can contend for access.

[0020] The disclosed protocol method is an independent method but is also compatible with and can be used to modify existing native protocols such as the IEEE 802.11 series standard, the IEEE 1901-2010 standard and HomePlug AV-based specifications. The ability to hold off a transmission for an acknowledgement period is similar to HomePlug AV's bidirectional burst method except that the Multi-ACKed Multicast protocol modifies the SOF and RSOF delimiters to support multi-acknowledgements from multiple receivers which is specifically not permitted or anticipated in HomePlug AV. By modifying an existing mechanism, the Multi-ACKed Multicast protocol can be initialized using compatible delimiters and operates within the acknowledgement period which is isolated from and can contain a protocol that is different from the native protocol, without affecting the native protocol. In this way the protocol can be used to modify an existing (native) protocol to support the Multi-ACKed Multicast protocol.

[0021] In another embodiment, the RSOF transmissions 590 from the receiver to the original transmitter include digital information about the quality of the received signal. The transmitter analyzes the RSOF digital information and decides which carrier frequencies and other transmitter parameters will result in the most efficient and successful communications with all of the group's devices. The result is communicated to the receiver group using a common tone map.

[0022] In another embodiment, as illustrated in FIG. 6, before the FL period 425 expires or is terminated, the transmitter may send a subsequent SOF delimiter 610 to continue to transmit without contending for medium access, or send a selective acknowledgement (SACK) 595 delimiter to relinquish medium ownership and end the Multi-ACKed Multicast protocol's multi-acknowledgment period. Different subgroups 620, 630 of devices within the group may have different QoS requirements. For example, tweeter speakers may be a subgroup of devices that share the same MPDU payload. A second subgroup may be the bass speakers. In this embodiment, a second or subsequent SOF delimiter 610 may use a different Tone Map or other digital information than the first or subsequent SOFs in order to optimize the communications efficiency and reduce latency. The receivers can be pre-assigned (grouped) to a specific SOF by a local link ID (LID) contained in the SOF.

[0023] In yet another embodiment, the RSOF 590 transmission from the receiver to the original transmitter includes digital information about the quality of the received signal. The transmitter analyzes the RSOF digital information and partitions the group into subgroups by channel performance (rather than application function) so that the tone map parameters for each SOF subgroup (620, 630) can be optimized for which channel frequencies and transmission parameters (e.g., modulation) will result in the most efficient, lowest packet latency, communications.

[0024] Although not a limitation of this disclosure, the maximum time the transmitter can hold off contention with the Multi-ACKed Multicast protocol is usually limited to allow devices not participating in the group to contend for access to the network. The total original transmitter's concatenated FL is typically between 5 and 10 ms.

[0025] When the Multi-ACKed Multicast protocol is used within a native protocol, it can be turned on or off depending on its effectiveness, without affecting interoperability or compatibility with the native protocol. For example, if the transmitter determines that the channel conditions are such that the Multiple-ACKed Multicast protocol is performing less than required by the receiving devices, the Multi-ACKed Multicast protocol can be suspended in favor of a native protocol, such as packet distribution using unicast transmissions to each device, or other methods. The transmitter or upper communications layers decide which protocol to use for each transmission.

[0026] While the invention has been illustrated and described in detail in the drawings and foregoing description, such illustration and description are considered illustrative or exemplary and not restrictive; the invention is not limited to the disclosed embodiments. Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure, and the appended claims.