System and method of data communication using wake-up radio frames

Abstract

This invention provides a system and method for data communication using Wake-Up Radio (WUR) frames. [Solution] In a data communication system, the method includes transmitting a wake-up radio (WUR) data frame by a WUR transmitter based on IEEE 802.11ba. The WUR data frame includes a frame header and a frame body. The frame body includes a data payload field for storing the data to be communicated and a data payload length field indicating the bit length of the data payload field. The method also includes a network device receiving a WUR data frame and decoding the data payload contained in the received WUR data frame.

Description

Technical Field

[0003]

[0001]

[0001] This subject matter relates to systems and methods for data communication, and more particularly, to systems and methods for data communication using wake-up radio frames.

Background Art

[0002]

[0002] Wireless data communication involves transmitting and receiving data using radio frequency (RF) signals. A transmitter generates a data frame for transmission by allocating data to blocks of modulation symbols. A symbol refers to any suitable representation of information. For example, in some applications, a symbol may correspond to a single bit. In some applications, a symbol may correspond to a sequence of chips. Any suitable modulation scheme may be used to allocate data to modulation symbols. For example, the modulation scheme may include on-off keying (OOK), phase shift keying (PSK), or frequency shift keying (FSK).

[0003]

[0003] Wake-up radio (WUR) operation enables an energy-efficient radio data receiving mode for a device. A low-power WUR receiver monitors the RF spectrum of one or more WUR frames. In response to receiving a wake-up command, the device can switch from the low-power WUR receiver to a high-power primary connectivity radio (PCR) for further communication. For example, WUR operation as defined in the IEEE 802.11ba standard enables low-power communication with WUR active power consumption of less than 1 mW. However, WUR operation may have overhead related to maintaining the association between the device and the network infrastructure. For example, WUR operation may have overhead related to using beacon frames for synchronization between access point (AP) stations and non-AP stations. [Overview of the project]

[0004]

[0004] The following introduction is provided to introduce the reader to the following more detailed explanation. The introduction is not intended to limit or define any claimed or unclaimed invention. One or more inventions may be any combination or partial combination of elements or process steps disclosed in any part of this document, including its claims and drawings.

[0005]

[0005] In one broad embodiment, a method of data communication is provided. This method includes transmitting a wake-up radio (WUR) data frame by a radio transmitter based on IEEE 802.11ba. The WUR data frame includes a frame header and a frame body. The frame body includes a data payload field for storing the data to be communicated and a data payload length field indicating the bit length of the data payload field.

[0006]

[0006] The frame header may include an 8-bit frame control field, which includes a 3-bit type field that stores a type identifier value indicating the WUR frame type of the WUR data frame as the "data" frame type.

[0007]

[0007] The WUR data frame may conform to the IEEE 802.11ba standard.

[0008]

[0008] The frame header may be a 32-bit MAC header including an 8-bit frame control field and a 24-bit multicast address data field, the 24-bit multicast address data field being formed by a combination of a 12-bit ID field and a 12-bit type-dependent control field.

[0009]

[0009] The multicast address data field may include an IEEE 802.11bc Enhanced Broadcast Service (EBCS) traffic stream identifier.

[0010]

[0010] The 8-bit frame control field may further include a 3-bit length / other field for storing bits indicating data fragmentation.

[0011]

[0011] The method may further include receiving and decoding data frames by one or more devices, each of which includes a wireless receiver based on IEEE 802.11ba.

[0012]

[0012] One or more devices may include ambient power devices that comply with the IEEE 802.11bp standard.

[0013]

[0013] One or more devices may include backscatter tags.

[0014]

[0014] The WUR data frame may be transmitted by a wireless transmitter based on IEEE 802.11ba at a non-access point (AP) station (STA).

[0015]

[0015] In another broad embodiment, a data communication system is provided. This system includes a first device and a second device. The first device includes an IEEE 802.11ba radio transmitter for transmitting wake-up radio (WUR) data frames. The WUR data frame includes a frame header and a frame body. The frame body includes a data payload field for storing data to be communicated and a data payload length field indicating the bit length of the data payload field. The second device includes a WUR receiver for receiving the WUR data frame containing the data stored in the data payload field.

[0016]

[0016] The frame header may include an 8-bit frame control field, which includes a 3-bit type field that stores a type identifier value indicating the WUR frame type of the WUR data frame as the "data" frame type.

[0017]

[0017] The WUR data frame may conform to the IEEE 802.11ba standard.

[0018]

[0018] The frame header may be a 32-bit MAC header including an 8-bit frame control field and a 24-bit multicast address data field, the 24-bit multicast address data field being formed by a combination of a 12-bit ID field and a 12-bit type-dependent control field.

[0019]

[0019] The multicast address data field may include an IEEE 802.11bc Extended Broadcast Service (EBCS) traffic stream identifier.

[0020]

[0020] The 8-bit frame control field may further include a 3-bit length / other field for storing bits indicating data fragmentation.

[0021]

[0021] The WUR receiver may be a wireless receiver based on IEEE802.11ba.

[0022]

[0022] The second device may be a surrounding power device compliant with the IEEE802.11bp standard.

[0023]

[0023] The second device may be a backscatter tag.

[0024]

[0024] The first device may be a non-access point (AP) station (STA).

[0025] [[ID=二十一]] [[ID=二十二]]

[0025] Other features and advantages of this application will become apparent from the following detailed description. However, the detailed description and specific examples, while showing embodiments of this application, are given by way of illustration only, and it should be understood that the scope of the claims should not be limited by these embodiments, but the broadest interpretation consistent with the description as a whole should be given.

Brief Description of the Drawings

[0026]

[0026] To better understand the embodiments described in this specification and to more clearly show how they can be implemented, next, by way of illustration only, reference is made to the accompanying drawings showing at least one exemplary embodiment.

[0027] [Figure 1A] It is a schematic diagram of a data communication system according to an exemplary embodiment.

[0028] 。 [Figure 1B] It is a schematic diagram of a data communication system according to another exemplary embodiment.

[0029]

[0029] [Figure 2] The process flow of an exemplary embodiment of a method of data communication using a WUR data frame.

[0030] [Figure 3] A block diagram of an exemplary WUR data frame transmitted during the execution of the method of FIG. 2.

[0031] <00001​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​

[0036] For the sake of simplicity and clarity of the examples, it will be understood that, where appropriate, reference numerals may be repeated between drawings to indicate corresponding or similar elements or steps. In addition, numerous specific details are provided to give a complete understanding of the exemplary embodiments described herein. However, it will be understood by those skilled in the art that the embodiments described herein can be carried out without these specific details. In other examples, well-known methods, procedures, and components are not described in detail so as not to obscure the embodiments described herein. Furthermore, this description should not be considered to limit the scope of the embodiments described herein in any way, but rather to simply describe embodiments of the various embodiments described herein.

[0037]

[0037] Unless otherwise specified, the terms “an embodiment,” “embodiment,” “embodiments,” “the embodiment,” “the embodiments,” “one or more embodiments,” “some embodiments,” and “one embodiment” mean “one or more (but not all) embodiments of the present invention.”

[0038]

[0038] The terms “including,” “comprising,” and their variations mean “including, but not limited to,” unless otherwise specified. The list of items does not imply that any or all of the items are mutually exclusive unless otherwise specified. The terms “a,” “an,” and “the” mean “one or more,” unless otherwise specified.

[0039]

[0039] As used herein and in the claims, two or more parts are said to be “joined,” “connected,” “attached,” or “fixed” insofar as the connection is made, if the parts are joined directly or indirectly (i.e., through one or more intermediate parts) or work together. As used herein and in the claims, two or more parts are said to be “directly joined,” “directly connected,” “directly attached,” or “directly fixed” if the parts are connected by physical contact with each other. As used herein, two or more parts are said to be “firmly joined,” “firmly connected,” “firmly attached,” or “firmly fixed” if the parts are joined so that they move as one while maintaining a certain orientation relative to each other. None of the terms “joined,” “connected,” “attached,” and “fixed” distinguish how two or more parts are joined to each other.

[0040]

[0040] When used herein, terms of degree such as “substantially,” “about,” and “approximately” should be noted to mean a reasonable degree of deviation from the modified term so as not to significantly alter the final result. These terms of degree should be interpreted as including a deviation from the modified term, unless the deviation negates the meaning of the term that the degree term modifies.

[0041]

[0041] In addition, as used herein, the terms “and / or” are intended to be comprehensive or inclusive. That is, “X and / or Y” is intended to mean, for example, X or Y or both of them. As a further example, “X, Y, and / or Z” is intended to mean X or Y or Z or any combination thereof.

[0042]

[0042] Furthermore, the method steps may be described in a sequential order (in this disclosure and / or claims), but such methods may be configured to function in an alternative order. In other words, any order or sequence of steps that may be described does not necessarily imply that the steps must be performed in that order. The steps of the methods described herein may be performed in any practical order. Furthermore, some steps may be performed simultaneously.

[0043]

[0043] As used herein and in the claims, a group of elements is said to “collectively” perform an action if the action is performed by any one of the elements in the group or by two or more (or all) of the elements in the group in a coordinated manner.

[0044]

[0044] Some elements in this specification may be identified by a subnumber consisting of a base number followed by an alphabetical or subscript (e.g., 112a or 1121). Multiple elements in this specification may be identified by subnumbers that share a common base number but have different subscripts (e.g., 1121, 1122, and 1123). All elements having a common base number may be referred to collectively or generically using the base number without a subscript (e.g., 112).

[0045]

[0045] The IEEE 802.11ba standard provides a WUR frame, which is a control frame or management frame. Furthermore, WUR frames are transmitted by an access point (AP) to a non-AP station (STA). The disclosed system and method can leverage power-efficient WUR operation for data communications using WUR frames. The disclosed WUR data frames can be transmitted by an AP (e.g., as described with reference to Figure 5A) or a non-AP STA (e.g., as described with reference to Figure 5B). Furthermore, the disclosed system and method can provide improved power efficiency by reducing the overhead of WUR operation related to maintaining association. The disclosed WUR frame has a frame header that includes a multicast address data field. Multicast addressing can enable the disclosed system and method to provide data communications while avoiding the requirement for devices to maintain association with the network infrastructure.

[0046]

[0046] Next, we refer to Figure 1A, which is a schematic diagram of a data communication system 100a according to an exemplary embodiment. The system 100a includes a network infrastructure device 104 and a network device 108a.

[0047]

[0047] The network infrastructure device 104 may be any suitable infrastructure device. For example, the network infrastructure device 104 may be an access point (AP). The network infrastructure device 104 may enable WUR operation by transmitting WUR frames 112. The network infrastructure device 104 may include a WUR transmitter 105 configured to transmit WUR frames 112. The network infrastructure device 104 may include a WUR receiver 106 configured to receive WUR frames 112.

[0048]

[0048] In some embodiments, the transmitted WUR frame 112 may conform to the IEEE 802.11ba standard. For example, the WUR transmitter 105 may be a wireless transmitter based on IEEE 802.11ba, and the WUR receiver 106 may be a wireless receiver based on IEEE 802.11ba. In other embodiments, the transmitted WUR frame 112 may be based on a different standard.

[0049]

[0049] The network device 108a may be any suitable device including a WUR receiver 110a that enables WUR operation. In some embodiments, the WUR receiver 110a may be based on a low-complexity, low-power envelope detector. The envelope detector can enable ultra-low-power or ambient-power operation of the network device 108a. For example, the WUR frame 112 may utilize OOK modulation that can be demodulated by the envelope detector of the WUR receiver 110a. In other embodiments, the WUR receiver 110a may use a different design to demodulate the received WUR frame.

[0050]

[0050] In the illustrated example, the network device 108a includes a WUR transmitter 109a. Optionally, the WUR transmitter 109a may be a wireless transmitter based on IEEE 802.11ba. In other examples, the network device 108a may not include a WUR transmitter.

[0051]

[0051] The network device 108a may be any non-AP STA. The network device 108a may include, for example, an Internet of Things (IoT) device. The IoT device may include an ambient power device. The ambient power device may comply with the IEEE 802.11bp standard. In some embodiments, the network device 108a may include a backscatter tag.

[0052]

[0052] Next, we refer to Figure 1B, a schematic diagram of a data communication system 100b according to an exemplary embodiment. System 100b includes a network infrastructure device 104 and a plurality of network devices 108. System 100b may include any appropriate number of network devices 108. In the illustrated exemplary embodiment, system 100b includes three network devices 108a to 108c. In other embodiments, system 100b may include a different number of network devices 108.

[0053]

[0053] As described above in this specification with reference to Figure 1A, the network infrastructure device 104 may be any suitable infrastructure device (e.g., an AP). The network infrastructure device 104 may include a WUR transmitter 105 configured to transmit WUR frames 112 and a WUR receiver 106 configured to receive WUR frames 112. In the illustrated exemplary embodiment (Figures 1A and 1B), the system 100 includes a single network infrastructure device 104. In other embodiments, the system 100 may include multiple network infrastructure devices 104.

[0054]

[0054] As described above in this specification with reference to Figure 1A, the network devices 108a, 108b, and 108c may include corresponding WUR receivers 110a, 110b, and 110c, respectively. Optionally, the WUR receivers 110a, 110b, and / or 110c may be based on a low-complexity, low-power envelope detector. Alternatively, the WUR receivers 110a, 110b, and / or 110c may use different designs to demodulate the received WUR frames. The network devices 108a, 108b, and 108c may include corresponding WUR transmitters 109a, 109b, and 109c, respectively.

[0055]

[0055] Network devices 108a, 108b, and / or 108c may be any suitable non-AP STA device, including, for example, an IoT device. The IoT device may include an ambient power device, which may conform to the IEEE 802.11bp standard. Optionally, network devices 108a, 108b, and / or 108c may include a backscatter tag.

[0056]

[0056] In the example shown in Figures 1A and 1B, the network infrastructure device 104 transmits a WUR frame 112 that is received by the network device 108. In other examples, one or more network devices 108 (e.g., 108a, 108b, and / or 108c) may transmit a WUR frame 112 that is received by other devices.

[0057]

[0057] Devices 104 and 108 of system 100 may include any suitable combination of processor and memory devices to carry out the methods described herein.

[0058]

[0058] In the IEEE 802.11ba standard, a WUR frame is a control frame or management frame (e.g., a discovery frame, a beacon frame). A WUR frame may be used to initialize communication, enabling the initial low-power receiver operation to receive WUR frames. Subsequently, data frames based on different 802.11 standards (which require switching from low-power receiver operation to high-power radio receiver / PCR operation) are commonly used for data transfer between devices.

[0059]

[0059] In contrast, the disclosed systems and methods can mitigate the power consumption problem of the receiver by providing WUR data frames. The disclosed WUR data frames can enable data communication between devices using low-power WUR receivers. Optionally, the receiver device (e.g., network device 108a) does not have to include a high-power / PCR receiver. Alternatively, the receiver device may include a high-power / PCR receiver, but can receive WUR data frames without switching the high-power / PCR receiver on.

[0060]

[0060] Next, we refer to Figure 2, which is a process flow of an exemplary embodiment of Method 200 for data communication using WUR frames. Method 200 can be implemented using any suitable data communication system. For example, Method 200 may be implemented using system 100a (Figure 1A) or system 100b (Figure 1B), with the components shown in Figures 1A and 1B being referenced simultaneously.

[0061]

[0061] In operation 204, method 200 includes transmitting a WUR data frame. For example, a WUR transmitter 105 of network infrastructure device 104 may transmit a WUR data frame 112.

[0062]

[0062] Next, we refer to Figure 3, a block diagram of an exemplary WUR data frame 112 transmitted in operation 204. The WUR data frame 112 may include a frame header 304 and a frame body 308a. In some embodiments, the WUR data frame 112 may further include a frame check sequence (FCS) 312.

[0063]

[0063] The frame header 304 may include a multicast address data field. The multicast address data field may include multicast address data indicating one or more network devices that are addressed, for example, network devices 108a to 108c. By using multicast addressing, method 200 can avoid the overhead associated with maintaining associations between network infrastructure devices 104 (e.g., access points) and network devices 108 (e.g., non-AP stations).

[0064]

[0064] In some embodiments, the multicast address data field may include an IEEE 802.11bc Extended Broadcast Service (EBCS) traffic stream identifier. The IEEE 802.11bc EBCS standard requires devices to send and receive full Wi-Fi transmissions that include a complete header. However, the WUR data frame 112 can improve data communication efficiency compared to 802.11bc EBCS by using a shorter frame header 304 (e.g., a higher ratio of data payload length to frame header length). By leveraging the capabilities of the IEEE 802.11bc Extended Broadcast Service (EBCS), method 200 can avoid the overhead of typical WUR operations related to association and beacons.

[0065]

[0065] In some embodiments, the WUR data frame 112 may include a 32-bit frame header 304 (similar to the 32-bit MAC header length of an IEEE 802.11ba WUR frame). In other embodiments, the frame header 304 may have a different bit length. For example, a longer frame header 304 may allow for a longer multicast address data field. As another example, a shorter frame header 304 may improve data communication efficiency.

[0066]

[0066] Next, we refer to Figure 4A, a block diagram of a frame header 304 according to an exemplary embodiment. The frame header 304 may be configured to provide compatibility with the frame header length of an IEEE 802.11ba WUR frame. For example, the frame header 304 may have a length of 32 bits and may include an 8-bit frame control field 404, a 12-bit ID field 408, and a 12-bit type-dependent control field 412. In other embodiments, the frame header 304 may have a different configuration.

[0067]

[0067] The combination of the ID field 408 and the type-dependent control field 412 may be configured to provide a 24-bit multicast address data field. The 24-bit multicast address data field can store a 24-bit EBCS stream identifier corresponding to the last 24 bits of the MAC address of the IEEE802.11bc EBCS content.

[0068]

[0068] Next, we refer to Figure 4B, which is a block diagram of the frame control field 404 of Figure 4A. The 8-bit frame control field 404 may include a 3-bit type field 416, a 1-bit protection field 420, a 1-bit frame body presence / absence field 424, and a 3-bit length / other field 428. In other embodiments, the frame control field 404 may have a different configuration.

[0069]

[0069] The 3-bit type field 416 may be used to store a 3-bit type identifier which is set to one of the reserved values ​​specified by the IEEE 802.11ba standard. The selected reserved value may be used to specify that the frame type of the WUR frame is a "data" frame type. The 1-bit frame body presence field 424 may store a value of "1" which indicates that a frame body exists. The 3-bit length / other field 428 may be used to store a bit which indicates data fragmentation.

[0070]

[0070] In the IEEE 802.11ba standard, the 3-bit length / other field in the frame control field of the frame header is used to define the length of the frame body (if any). However, the maximum length of the frame body that can be defined using this field is limited to 18 bytes. While this maximum length of the frame body may be sufficient for control or management frames provided by the 802.11ba standard, this maximum length may not be sufficient for many data transfer applications. The disclosed systems and methods mitigate this technical problem by providing a separate data payload length field (as described below with reference to Figures 5A and 5B).

[0071]

[0071] Next, refer to Figure 5A, which is a block diagram of the frame body 308a in Figure 3. In some embodiments, the frame body 308a may have a variable bit length. In other embodiments, the frame body 308a may have a fixed bit length.

[0072]

[0072] The frame body 308a may include a data payload length field 504 and a data payload field 508. The data payload length field 504 may be configured to store a payload length value indicating the bit length of the data payload field 508. In some embodiments, the frame body 308a may not include the data payload length field 504. For example, a WUR data frame may have a fixed-length data payload field, and the fixed length may not be defined within the frame body.

[0073]

[0073] The data payload length field 504 may have any suitable bit length. In some embodiments, the data payload length field 504 may be an 8-bit field. In other embodiments, the data payload length field 504 may have different bit lengths (e.g., less than 8 or greater than 8). A data payload length field 504 with a smaller bit length may improve data communication efficiency. A data payload length field 504 with a longer bit length may allow specifying a data payload field 508 with a wider range of variable bit lengths.

[0074]

[0074] In some embodiments, the frame body 308a may include one or more header fields. Header fields may be used to provide additional information relating to, for example, the type of data payload, source / destination address, etc.

[0075]

[0075] Referring back to Figure 2, in operation 208, method 200 includes receiving the WUR data frame transmitted in operation 204. For example, network device 108 may receive WUR data frame 112. Network device 108 can use the multicast address data contained in WUR data frame 112 to determine whether WUR data frame 112 is addressed to that device.

[0076]

[0076] In some embodiments, multiple network devices 108 can be addressed simultaneously using multicast address data. This allows data transfer to multiple devices and / or triggering of multiple network devices 108 using a single WUR frame.

[0077]

[0077] In operation 212, method 200 includes decoding the data payload contained in the WUR data frame received in operation 208. For example, one or more network devices 108 may determine that the received WUR data frame 112 is addressed to that network device. In response, the network device 108 may decode the data payload contained in the WUR data frame 112.

[0078]

[0078] In some embodiments, method 200 may further include the transmission of a WUR data frame by the network device 108. For example, the network device 108 may transmit a WUR data frame in response to the instruction / data decoded in operation 212. As another example, the network device 108 may transmit a WUR data frame based on generating or receiving data for transmission to another device.

[0079]

[0079] Next, we refer to Figure 5B, a block diagram of an exemplary embodiment of a frame body 308b that can be transmitted by the network device 108.

[0080]

[0080] In some embodiments, the frame body 308b may have a variable bit length. In other embodiments, the frame body 308b may have a fixed bit length.

[0081]

[0081] The frame body 308b may include a data payload length field 504, a data payload field 508, and an ADDR / SN / FN field 512. In some embodiments, the frame body 308b may not include the data payload length field 504.

[0082]

[0082] The data payload length field 504 may be configured to store a payload length value indicating the bit length of the data payload field 508. Different bit lengths may be selected for the data payload field 508 based on the requirements of the data payload being communicated. For example, the network device 108 may be coupled to a sensor that generates 16 bits of sensor data. In this application, the bit length of the data payload field 508 may be configured to be 16 bits. In other applications, the bit length of the data payload field 508 may be different (e.g., less than 16 bits or more than 16 bits).

[0083]

[0083] In some embodiments, the ADDR / SN / FN field 512 may be used to supplement the 24-bit multicast address data field provided by the frame header 304. The additional bit storage provided by the ADDR / SN / FN field 512 can make it possible to specify the full address of the network device 108 that transmits the WUR data frame. This can make it possible for a receiver device decoding the WUR data frame to identify the network device 108 that transmitted the WUR frame.

[0084]

[0084] In some embodiments, the ADDR / SN / FN field 512 may be used to provide additional bit storage for specifying a sequence counter and / or fragment number associated with the data payload.

[0085]

[0085] While the above description provides examples of embodiments, it will be understood that some features and / or functions of the described embodiments can be modified without departing from the spirit and principles of operation of the described embodiments. Therefore, it will be understood by those skilled in the art that what is described above is intended to illustrate the invention and is not limiting, and that other modifications and changes can be made without departing from the scope of the invention as defined in the appended claims. The claims should not be limited by preferred embodiments and examples, and should be given the broadest interpretation that is consistent with the description as a whole. [Explanation of symbols]

[0086] 100a...Data communication system, 100b...Data communication system, 104...Network infrastructure device, 105...WUR transmitter, 106...WUR receiver, 108a...Network device, 109a...WUR transmitter, 110a...WUR receiver, 108b...Network device, 109b...WUR transmitter, 110b...WUR receiver, 108c...Network device, 109c...WUR transmitter, 110c...WUR receiver, 112...WUR data frame, 304...Frame Header, 308... Frame body, 308a... Frame body, 308b... Frame body, 312... Frame check sequence, 404... Frame control field, 408... ID field, 412... Type-dependent control field, 416... Type field, 420... Protection field, 424... Frame body presence / absence field, 428... Length / Other fields, 504... Data payload length field, 508... Data payload field, 512... ADDR / SN / FN field

Claims

1. A method of data communication, A step of transmitting a wake-up radio (WUR) data frame by a radio transmitter based on IEEE 802.11ba, wherein the WUR data frame is Frame header and, It is a frame body, A data payload field for storing the data to be communicated, and Data payload length field indicating the bit length of the aforementioned data payload field Frame body including Steps including A method that includes this.

2. The method according to claim 1, wherein the frame header includes an 8-bit frame control field, and the 8-bit frame control field includes a 3-bit type field that stores a type identifier value indicating the WUR frame type of the WUR data frame as a "data" frame type.

3. The method according to claim 1, wherein the WUR data frame conforms to the IEEE 802.11ba standard.

4. The method according to claim 2, wherein the frame header is a 32-bit MAC header including the 8-bit frame control field and the 24-bit multicast address data field, and the 24-bit multicast address data field is formed by a combination of a 12-bit ID field and a 12-bit type-dependent control field.

5. The method according to claim 4, wherein the multicast address data field includes an IEEE 802.11bc Extended Broadcast Service (EBCS) traffic stream identifier.

6. The method according to claim 2, wherein the 8-bit frame control field further includes a 3-bit length / other field for storing bits indicating data fragmentation.

7. The method according to claim 1, further comprising the step of receiving and decoding the data frame by one or more devices, wherein each of the one or more devices includes a wireless receiver based on IEEE 802.11ba.

8. The method according to claim 7, wherein one or more of the devices include an ambient power device compliant with the IEEE 802.11bp standard.

9. The method according to claim 7, wherein one or more of the devices include a backscatter tag.

10. The method according to claim 1, wherein the WUR data frame is transmitted by a wireless transmitter based on IEEE 802.11ba of a non-access point (AP) station (STA).

11. A data communication system, A first device including an IEEE 802.11ba-based radio transmitter for transmitting a Wake-Up Radio (WUR) data frame, wherein the WUR data frame is Frame header and, It is a frame body, A data payload field for storing the data to be communicated, and Data payload length field indicating the bit length of the aforementioned data payload field Frame body including A first device including, A second device comprising a WUR receiver for receiving the WUR data frame containing the data stored in the data payload field, and A system equipped with these features.

12. The system according to claim 11, wherein the frame header includes an 8-bit frame control field, and the 8-bit frame control field includes a 3-bit type field that stores a type identifier value indicating the WUR frame type of the WUR data frame as a "data" frame type.

13. The system according to claim 11, wherein the WUR data frame conforms to the IEEE 802.11ba standard.

14. The system according to claim 12, wherein the frame header is a 32-bit MAC header including the 8-bit frame control field and the 24-bit multicast address data field, and the 24-bit multicast address data field is formed by a combination of a 12-bit ID field and a 12-bit type-dependent control field.

15. The system according to claim 14, wherein the multicast address data field includes an IEEE 802.11bc Extended Broadcast Service (EBCS) traffic stream identifier.

16. The system according to claim 12, wherein the 8-bit frame control field further includes a 3-bit length / other field for storing bits indicating data fragmentation.

17. The system according to claim 11, wherein the WUR receiver is a wireless receiver based on IEEE 802.11ba.

18. The system according to claim 17, wherein the second device is an ambient power device compliant with the IEEE 802.11bp standard.

19. The system according to claim 17, wherein the second device is a backscatter tag.

20. The system according to claim 11, wherein the first device is a non-access point (AP) station (STA).

Images