Patent Application
20240107371
The present specification relates to a multi-link operation in a wireless LAN system, and more particularly, to a method and apparatus for transmitting BSR information for another link based on an A-Control field.
A wireless local area network (WLAN) has been improved in various ways. For example, the IEEE 802.11ax standard proposed an improved communication environment using orthogonal frequency division multiple access (OFDMA) and downlink multi-user multiple input multiple output (DL MU MIMO) techniques.
The present specification proposes a technical feature that can be utilized in a new communication standard. For example, the new communication standard may be an extreme high throughput (EHT) standard which is currently being discussed. The EHT standard may use an increased bandwidth, an enhanced PHY layer protocol data unit (PPDU) structure, an enhanced sequence, a hybrid automatic repeat request (HARQ) scheme, or the like, which is newly proposed. The EHT standard may be called the IEEE 802.11be standard.
In a new WLAN standard, an increased number of spatial streams may be used. In this case, in order to properly use the increased number of spatial streams, a signaling technique in the WLAN system may need to be improved.
The present specification proposes a method and apparatus for transmitting BSR information for another link based on an A-Control field in a wireless LAN system.
An example of this specification proposes a method for transmitting BSR information for another link based on the A-Control field.
The present embodiment may be performed in a network environment in which a next generation WLAN system (IEEE 802.11be or EHT WLAN system) is supported. The next generation wireless LAN system is a WLAN system that is enhanced from an 802.11ax system and may, therefore, satisfy backward compatibility with the 802.11ax system.
This embodiment newly defines the existing A-Control field to support Multi-Link, and propose a method and apparatus for transmitting and receiving BSR information of another link (or other receiving STA) based on the newly defined A-Control field. Here, the transmitting MLD may correspond to the AP MLD, and the receiving MLD may correspond to the non-AP MLD.
A receiving multi-link device (MLD) generates an A-Control field.
The receiving MLD transmits the A-Control field to a transmitting MLD through a first link.
The transmitting MLD includes a first transmitting station (STA) operating on the first link, a second transmitting STA operating on a second link, and a third transmitting STA operating on a third link.
The receiving MLD includes a first receiving STA operating on the first link, a second receiving STA operating on the second link, and a third receiving STA operating on the third link.
The A-Control field includes a control identifier and control information for a Buffer Status Report (BSR). The control information for the BSR may be set based on the control identifier. A value of the control identifier may be 3. The A-Control field is composed of the control identifier and control information according to the control identifier. When the value of the control identifier is 3, the control information may be set as control information for the BSR.
The control information for the BSR includes a link identifier, an Access Category Index (ACI) bitmap subfield, a Delta Traffic Identifier (TID) subfield, an ACI High subfield, a Scaling Factor subfield, and a Queue Size High subfield.
Control information for a BSR supporting one existing link includes the ACI bitmap subfield, the Delta TID subfield, the ACI High subfield, the scaling factor subfield, the Queue Size High subfield, and the Queue Size All subfield. The ACI bitmap subfield is 4 bits, the Delta TID subfield is 2 bits, the ACI High subfield is 2 bits, the scaling factor subfield is 2 bits, the Queue Size High subfield is 8 bits, and the Queue Size All subfield is 8 bits. That is, the control information for the existing BSR consists of a total of 26 bits.
When the A-Control field defined in the 802.11ax wireless LAN system includes a control identifier and control information for BSR (supporting one link), since the control identifier is 4 bits and the control information for the existing BSR is 26 bits, it is assumed that the A-Control field must be configured within 30 bits.
However, as in this embodiment, when the link identifier is included in the control information for the BSR to configure the control information for the BSR supporting Multi-Link, since the link identifier is 4 bits, there may be a problem that the size of the A-Control field exceeds 30 bits. Accordingly, in order to include control information for the BSR supporting Multi-Link using the existing A-Control field, a format that is lighter than the control information for the existing BSR is required. This embodiment proposes a method for transmitting and receiving BSR information for another receiving STA in a receiving MLD (non-AP MLD) in one frame (the A-Control field) by omitting some subfields (Queue Size All subfields to be described later) in the control information for the existing BSR to configure the control information of the A-Control field.
According to the embodiment proposed in this specification, frame overhead can be reduced by transmitting and receiving BSR information (or control information) for several links in one frame. Even if the link of another STA is not in an awake state, it is possible to transmit BSR information of the other STA using the link of a specific STA, which is effective in terms of power saving.
In the present specification, “A or B” may mean “only A”, “only B” or “both A and B”. In other words, in the present specification, “A or B” may be interpreted as “A and/or B”. For example, in the present specification, “A, B, or C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, C”.
A slash (/) or comma used in the present specification may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”.
In the present specification, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present specification, the expression “at least one of A or B” or “at least one of A and/or B” may be interpreted as “at least one of A and B”.
In addition, in the present specification, “at least one of A, B, and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”. In addition, “at least one of A, B, or C” or “at least one of A, B, and/or C” may mean “at least one of A, B, and C”.
In addition, a parenthesis used in the present specification may mean “for example”. Specifically, when indicated as “control information (EHT-signal)”, it may denote that “EHT-signal” is proposed as an example of the “control information”. In other words, the “control information” of the present specification is not limited to “EHT-signal”, and “EHT-signal” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., EHT-signal)”, it may also mean that “EHT-signal” is proposed as an example of the “control information”.
Technical features described individually in one figure in the present specification may be individually implemented, or may be simultaneously implemented.
The following example of the present specification may be applied to various wireless communication systems. For example, the following example of the present specification may be applied to a wireless local area network (WLAN) system. For example, the present specification may be applied to the IEEE 802.11a/g/n/ac standard or the IEEE 802.11ax standard. In addition, the present specification may also be applied to the newly proposed EHT standard or IEEE 802.11be standard. In addition, the example of the present specification may also be applied to a new WLAN standard enhanced from the EHT standard or the IEEE 802.11be standard. In addition, the example of the present specification may be applied to a mobile communication system. For example, it may be applied to a mobile communication system based on long term evolution (LTE) depending on a 3rd generation partnership project (3GPP) standard and based on evolution of the LTE. In addition, the example of the present specification may be applied to a communication system of a 5G NR standard based on the 3GPP standard.
Hereinafter, in order to describe a technical feature of the present specification, a technical feature applicable to the present specification will be described.
In the example of
For example, the STAs 110 and 120 may serve as an AP or a non-AP. That is, the STAs 110 and 120 of the present specification may serve as the AP and/or the non-AP.
The STAs 110 and 120 of the present specification may support various communication standards together in addition to the IEEE 802.11 standard. For example, a communication standard (e.g., LTE, LTE-A, 5G NR standard) or the like based on the 3GPP standard may be supported. In addition, the STA of the present specification may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, or the like. In addition, the STA of the present specification may support communication for various communication services such as voice calls, video calls, data communication, and self-driving (autonomous-driving), or the like.
The STAs 110 and 120 of the present specification may include a medium access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for a radio medium.
The STAs 110 and 120 will be described below with reference to a sub-figure (a) of
The first STA 110 may include a processor 111, a memory 112, and a transceiver 113. The illustrated process, memory, and transceiver may be implemented individually as separate chips, or at least two blocks/functions may be implemented through a single chip.
The transceiver 113 of the first STA performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be, etc.) may be transmitted/received.
For example, the first STA 110 may perform an operation intended by an AP. For example, the processor 111 of the AP may receive a signal through the transceiver 113, process a reception (RX) signal, generate a transmission (TX) signal, and provide control for signal transmission. The memory 112 of the AP may store a signal (e.g., RX signal) received through the transceiver 113, and may store a signal (e.g., TX signal) to be transmitted through the transceiver.
For example, the second STA 120 may perform an operation intended by a non-AP STA. For example, a transceiver 123 of a non-AP performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be packet, etc.) may be transmitted/received.
For example, a processor 121 of the non-AP STA may receive a signal through the transceiver 123, process an RX signal, generate a TX signal, and provide control for signal transmission. A memory 122 of the non-AP STA may store a signal (e.g., RX signal) received through the transceiver 123, and may store a signal (e.g., TX signal) to be transmitted through the transceiver.
For example, an operation of a device indicated as an AP in the specification described below may be performed in the first STA 110 or the second STA 120. For example, if the first STA 110 is the AP, the operation of the device indicated as the AP may be controlled by the processor 111 of the first STA 110, and a related signal may be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory 112 of the first STA 110. In addition, if the second STA 120 is the AP, the operation of the device indicated as the AP may be controlled by the processor 121 of the second STA 120, and a related signal may be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory 122 of the second STA 120.
For example, in the specification described below, an operation of a device indicated as a non-AP (or user-STA) may be performed in the first STA 110 or the second STA 120. For example, if the second STA 120 is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor 121 of the second STA 120, and a related signal may be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory 122 of the second STA 120. For example, if the first STA 110 is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor 111 of the first STA 110, and a related signal may be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory 112 of the first STA 110.
In the specification described below, a device called a (transmitting/receiving) STA, a first STA, a second STA, a STA1, a STA2, an AP, a first AP, a second AP, an AP1, an AP2, a (transmitting/receiving) terminal, a (transmitting/receiving) device, a (transmitting/receiving) apparatus, a network, or the like may imply the STAs 110 and 120 of
The aforementioned device/STA of the sub-figure (a) of
For example, the transceivers 113 and 123 illustrated in the sub-figure (b) of
A mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, a user, a user STA, a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, a receiving unit, a transmitting unit, a receiving STA, a transmitting STA, a receiving device, a transmitting device, a receiving apparatus, and/or a transmitting apparatus, which are described below, may imply the STAs 110 and 120 illustrated in the sub-figure (a)/(b) of
For example, a technical feature in which the receiving STA receives the control signal may be understood as a technical feature in which the control signal is received by means of the transceivers 113 and 123 illustrated in the sub-figure (a) of
Referring to the sub-figure (b) of
The processors 111 and 121 or processing chips 114 and 124 of
In the present specification, an uplink may imply a link for communication from a non-AP STA to an SP STA, and an uplink PPDU/packet/signal or the like may be transmitted through the uplink. In addition, in the present specification, a downlink may imply a link for communication from the AP STA to the non-AP STA, and a downlink PPDU/packet/signal or the like may be transmitted through the downlink.
An upper part of
Referring the upper part of
The BSS may include at least one STA, APs providing a distribution service, and a distribution system (DS) 210 connecting multiple APs.
The distribution system 210 may implement an extended service set (ESS) 240 extended by connecting the multiple BSSs 200 and 205. The ESS 240 may be used as a term indicating one network configured by connecting one or more APs 225 or 230 through the distribution system 210. The AP included in one ESS 240 may have the same service set identification (S SID).
A portal 220 may serve as a bridge which connects the wireless LAN network (IEEE 802.11) and another network (e.g., 802.X).
In the BSS illustrated in the upper part of
A lower part of
Referring to the lower part of
In S310, a STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, to access a network, the STA needs to discover a participating network. The STA needs to identify a compatible network before participating in a wireless network, and a process of identifying a network present in a particular area is referred to as scanning. Scanning methods include active scanning and passive scanning.
Although not shown in
After discovering the network, the STA may perform an authentication process in S320. The authentication process may be referred to as a first authentication process to be clearly distinguished from the following security setup operation in S340. The authentication process in S320 may include a process in which the STA transmits an authentication request frame to the AP and the AP transmits an authentication response frame to the STA in response. The authentication frames used for an authentication request/response are management frames.
The authentication frames may include information related to an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), and a finite cyclic group.
The STA may transmit the authentication request frame to the AP. The AP may determine whether to allow the authentication of the STA based on the information included in the received authentication request frame. The AP may provide the authentication processing result to the STA via the authentication response frame.
When the STA is successfully authenticated, the STA may perform an association process in S330. The association process includes a process in which the STA transmits an association request frame to the AP and the AP transmits an association response frame to the STA in response. The association request frame may include, for example, information related to various capabilities, a beacon listen interval, a service set identifier (SSID), a supported rate, a supported channel, RSN, a mobility domain, a supported operating class, a traffic indication map (TIM) broadcast request, and an interworking service capability. The association response frame may include, for example, information related to various capabilities, a status code, an association ID (AID), a supported rate, an enhanced distributed channel access (EDCA) parameter set, a received channel power indicator (RCPI), a received signal-to-noise indicator (RSNI), a mobility domain, a timeout interval (association comeback time), an overlapping BSS scanning parameter, a TIM broadcast response, and a QoS map.
In S340, the STA may perform a security setup process. The security setup process in S340 may include a process of setting up a private key through four-way handshaking, for example, through an extensible authentication protocol over LAN (EAPOL) frame.
As illustrated, various types of PHY protocol data units (PPDUs) are used in IEEE a/g/n/ac standards. Specifically, an LTF and a STF include a training signal, a SIG-A and a SIG-B include control information for a receiving STA, and a data field includes user data corresponding to a PSDU (MAC PDU/aggregated MAC PDU).
As illustrated in
Hereinafter, a resource unit (RU) used for a PPDU is described. An RU may include a plurality of subcarriers (or tones). An RU may be used to transmit a signal to a plurality of STAs according to OFDMA. Further, an RU may also be defined to transmit a signal to one STA. An RU may be used for an STF, an LTF, a data field, or the like.
The RU described in the present specification may be used in uplink (UL) communication and downlink (DL) communication. For example, when UL-MU communication which is solicited by a trigger frame is performed, a transmitting STA (e.g., an AP) may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA through the trigger frame, and may allocate a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA. Thereafter, the first STA may transmit a first trigger-based PPDU based on the first RU, and the second STA may transmit a second trigger-based PPDU based on the second RU. The first/second trigger-based PPDU is transmitted to the AP at the same (or overlapped) time period.
For example, when a DL MU PPDU is configured, the transmitting STA (e.g., AP) may allocate the first RU (e.g., 26/52/106/242-RU. etc.) to the first STA, and may allocate the second RU (e.g., 26/52/106/242-RU, etc.) to the second STA. That is, the transmitting STA (e.g., AP) may transmit HE-STF, HE-LTF, and Data fields for the first STA through the first RU in one MU PPDU, and may transmit HE-STF, HE-LTF, and Data fields for the second STA through the second RU.
TB PPDUs 1041 and 1042 may be transmitted at the same time period, and may be transmitted from a plurality of STAs (e.g., user STAs) having AIDs indicated in the trigger frame 1030. An ACK frame 1050 for the TB PPDU may be implemented in various forms.
A specific feature of the trigger frame is described with reference to
Each field shown in
A frame control field 1110 of
In addition, an RA field 1130 may include address information of a receiving STA of a corresponding trigger frame, and may be optionally omitted. A TA field 1140 may include address information of a STA (e.g., an AP) which transmits the corresponding trigger frame.
A common information field 1150 includes common control information applied to the receiving STA which receives the corresponding trigger frame. For example, a field indicating a length of an L-SIG field of an uplink PPDU transmitted in response to the corresponding trigger frame or information for controlling content of a SIG-A field (i.e., HE-SIG-A field) of the uplink PPDU transmitted in response to the corresponding trigger frame may be included. In addition, as common control information, information related to a length of a CP of the uplink PPDU transmitted in response to the corresponding trigger frame or information related to a length of an LTF field may be included.
In addition, per user information fields 1160 #1 to 1160 #N corresponding to the number of receiving STAs which receive the trigger frame of
In addition, the trigger frame of
Each of the per user information fields 1160 #1 to 1160 #N shown in
A length field 1210 illustrated has the same value as a length field of an L-SIG field of an uplink PPDU transmitted in response to a corresponding trigger frame, and a length field of the L-SIG field of the uplink PPDU indicates a length of the uplink PPDU. As a result, the length field 1210 of the trigger frame may be used to indicate the length of the corresponding uplink PPDU.
In addition, a cascade identifier field 1220 indicates whether a cascade operation is performed. The cascade operation implies that downlink MU transmission and uplink MU transmission are performed together in the same TXOP. That is, it implies that downlink MU transmission is performed and thereafter uplink MU transmission is performed after a pre-set time (e.g., SIFS). During the cascade operation, only one transmitting device (e.g., AP) may perform downlink communication, and a plurality of transmitting devices (e.g., non-APs) may perform uplink communication.
A CS request field 1230 indicates whether a wireless medium state or a NAV or the like is necessarily considered in a situation where a receiving device which has received a corresponding trigger frame transmits a corresponding uplink PPDU.
An HE-SIG-A information field 1240 may include information for controlling content of a SIG-A field (i.e., HE-SIG-A field) of the uplink PPDU in response to the corresponding trigger frame.
A CP and LTF type field 1250 may include information related to a CP length and LTF length of the uplink PPDU transmitted in response to the corresponding trigger frame. A trigger type field 1260 may indicate a purpose of using the corresponding trigger frame, for example, typical triggering, triggering for beamforming, a request for block ACK/NACK, or the like.
It may be assumed that the trigger type field 1260 of the trigger frame in the present specification indicates a trigger frame of a basic type for typical triggering. For example, the trigger frame of the basic type may be referred to as a basic trigger frame.
A user identifier field 1310 of
In addition, an RU allocation field 1320 may be included. That is, when the receiving STA identified through the user identifier field 1310 transmits a TB PPDU in response to the trigger frame, the TB PPDU is transmitted through an RU indicated by the RU allocation field 1320.
The subfield of
In addition, the subfield of
Hereinafter, a UL OFDMA-based random access (UORA) scheme will be described.
A transmitting STA (e.g., an AP) may allocate six RU resources through a trigger frame as shown in
In the example of
Specifically, since the STA1 of
Hereinafter, a PPDU transmitted/received in a STA of the present specification will be described.
The PPDU of
The PPDU of
In
A subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields of
In the PPDU of
The L-SIG field of
For example, the transmitting STA may apply BCC encoding based on a ½ coding rate to the 24-bit information of the L-SIG field. Thereafter, the transmitting STA may obtain a BCC coding bit of 48 bits. BPSK modulation may be applied to the 48-bit coding bit, thereby generating 48 BPSK symbols. The transmitting STA may map the 48 BPSK symbols to positions except for a pilot subcarrier{subcarrier index −21, −7, +7, +21} and a DC subcarrier {subcarrier index 0}. As a result, the 48 BPSK symbols may be mapped to subcarrier indices −26 to −22, −20 to −8, −6 to −1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map a signal of {−1, −1, −1, 1} to a subcarrier index{−28, −27, +27, +28}. The aforementioned signal may be used for channel estimation on a frequency domain corresponding to {−28, −27, +27, +28}.
The transmitting STA may generate an RL-SIG generated in the same manner as the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving STA may know that the RX PPDU is the HE PPDU or the EHT PPDU, based on the presence of the RL-SIG.
A universal SIG (U-SIG) may be inserted after the RL-SIG of
The U-SIG may include information of N bits, and may include information for identifying a type of the EHT PPDU. For example, the U-SIG may be configured based on two symbols (e.g., two contiguous OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG may have a duration of 4 μs. Each symbol of the U-SIG may be used to transmit the 26-bit information. For example, each symbol of the U-SIG may be transmitted/received based on 52 data tomes and 4 pilot tones.
Through the U-SIG (or U-SIG field), for example, A-bit information (e.g., 52 un-coded bits) may be transmitted. A first symbol of the U-SIG may transmit first X-bit information (e.g., 26 un-coded bits) of the A-bit information, and a second symbol of the U-SIB may transmit the remaining Y-bit information (e.g. 26 un-coded bits) of the A-bit information. For example, the transmitting STA may obtain 26 un-coded bits included in each U-SIG symbol. The transmitting STA may perform convolutional encoding (i.e., BCC encoding) based on a rate of R=½ to generate 52-coded bits, and may perform interleaving on the 52-coded bits. The transmitting STA may perform BPSK modulation on the interleaved 52-coded bits to generate 52 BPSK symbols to be allocated to each U-SIG symbol. One U-SIG symbol may be transmitted based on 65 tones (subcarriers) from a subcarrier index −28 to a subcarrier index +28, except for a DC index 0. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) except for pilot tones, i.e., tones −21, −7, +7, +21.
For example, the A-bit information (e.g., 52 un-coded bits) generated by the U-SIG may include a CRC field (e.g., a field having a length of 4 bits) and a tail field (e.g., a field having a length of 6 bits). The CRC field and the tail field may be transmitted through the second symbol of the U-SIG. The CRC field may be generated based on 26 bits allocated to the first symbol of the U-SIG and the remaining 16 bits except for the CRC/tail fields in the second symbol, and may be generated based on the conventional CRC calculation algorithm. In addition, the tail field may be used to terminate trellis of a convolutional decoder, and may be set to, for example, “000000”.
The A-bit information (e.g., 52 un-coded bits) transmitted by the U-SIG (or U-SIG field) may be divided into version-independent bits and version-dependent bits. For example, the version-independent bits may have a fixed or variable size. For example, the version-independent bits may be allocated only to the first symbol of the U-SIG, or the version-independent bits may be allocated to both of the first and second symbols of the U-SIG. For example, the version-independent bits and the version-dependent bits may be called in various terms such as a first control bit, a second control bit, or the like.
For example, the version-independent bits of the U-SIG may include a PHY version identifier of 3 bits. For example, the PHY version identifier of 3 bits may include information related to a PHY version of a TX/RX PPDU. For example, a first value of the PHY version identifier of 3 bits may indicate that the TX/RX PPDU is an EHT PPDU. In other words, when the transmitting STA transmits the EHT PPDU, the PHY version identifier of 3 bits may be set to a first value. In other words, the receiving STA may determine that the RX PPDU is the EHT PPDU, based on the PHY version identifier having the first value.
For example, the version-independent bits of the U-SIG may include a UL/DL flag field of 1 bit. A first value of the UL/DL flag field of 1 bit relates to UL communication, and a second value of the UL/DL flag field relates to DL communication.
For example, the version-independent bits of the U-SIG may include information related to a TXOP length and information related to a BSS color ID.
For example, when the EHT PPDU is divided into various types (e.g., various types such as an EHT PPDU related to an SU mode, an EHT PPDU related to a MU mode, an EHT PPDU related to a TB mode, an EHT PPDU related to extended range transmission, or the like), information related to the type of the EHT PPDU may be included in the version-dependent bits of the U-SIG.
For example, the U-SIG may include: 1) a bandwidth field including information related to a bandwidth; 2) a field including information related to an MCS scheme applied to EHT-SIG; 3) an indication field including information regarding whether a dual subcarrier modulation (DCM) scheme is applied to EHT-SIG; 4) a field including information related to the number of symbol used for EHT-SIG; 5) a field including information regarding whether the EHT-SIG is generated across a full band; 6) a field including information related to a type of EHT-LTF/STF; and 7) information related to a field indicating an EHT-LTF length and a CP length.
In the following example, a signal represented as a (TX/RX/UL/DL) signal, a (TX/RX/UL/DL) frame, a (TX/RX/UL/DL) packet, a (TX/RX/UL/DL) data unit, (TX/RX/UL/DL) data, or the like may be a signal transmitted/received based on the PPDU of
Each device/STA of the sub-figure (a)/(b) of
A processor 610 of
A memory 620 of
Referring to
Referring to
Hereinafter, technical features of multi-link (ML) supported by the STA of the present specification will be described.
STAs (AP and/or non-AP STA) of the present specification may support multi-link (ML) communication. ML communication may mean communication supporting a plurality of links. Links related to ML communication may include channels (e.g., 20/40/80/160/240/320 MHz channels) of the 2.4 GHz band, the 5 GHz band, and the 6 GHz band.
A plurality of links used for ML communication may be set in various ways. For example, a plurality of links supported by one STA for ML communication may be a plurality of channels in the 2.4 GHz band, a plurality of channels in the 5 GHz band, and a plurality of channels in the 6 GHz band. Alternatively, a plurality of links may be a combination of at least one channel within the 2.4 GHz band (or 5 GHz/6 GHz band) and at least one channel within the 5 GHz band (or 2.4 GHz/6 GHz band). Meanwhile, at least one of a plurality of links supported by one STA for ML communication may be a channel to which preamble puncturing is applied.
The STA may perform ML setup to perform ML communication. ML setup may be performed based on management frames or control frames such as Beacon, Probe Request/Response, and Association Request/Response. For example, information on ML setup may be included in element fields included in Beacon, Probe Request/Response, and Association Request/Response.
When ML setup is completed, an enabled link for ML communication may be determined. The STA may perform frame exchange through at least one of a plurality of links determined as an enabled link. For example, an enabled link may be used for at least one of a management frame, a control frame, and a data frame.
When one STA supports a plurality of Links, a transmitting/receiving device supporting each Link may operate like one logical STA. For example, one STA supporting two links may be expressed as one ML device (Multi Link Device; MLD) including a first STA for a first link and a second STA for a second link. For example, one AP supporting two links may be expressed as one AP MLD including a first AP for a first link and a second AP for a second link. In addition, one non-AP supporting two links may be expressed as one non-AP MLD including a first STA for the first link and a second STA for the second link.
More specific features of the ML setup are described below.
An MLD (AP MLD and/or non-AP MLD) may transmit information about a link that the corresponding MLD can support through ML setup. Link-related information may be configured in various ways. For example, link-related information includes at least one of 1) information on whether the MLD (or STA) supports simultaneous RX/TX operation, 2) information on the number/upper limit of uplink/downlink links supported by the MLD (or STA), 3) information on the location/band/resource of uplink/downlink link supported by MLD (or STA), 4) type of frame available or preferred in at least one uplink/downlink link (management, control, data etc.), 5) available or preferred ACK policy information on at least one uplink/downlink link, and 6) information on available or preferred TID (traffic identifier) on at least one uplink/downlink link. The TID is related to the priority of traffic data and is represented by 8 types of values according to the conventional wireless LAN standard. That is, 8 TID values corresponding to 4 access categories (AC) (AC_BK (background), AC_BE (best effort), AC_VI (video), AC_VO (voice)) according to the conventional wireless LAN standard may be defined.
For example, it may be set in advance that all TIDs are mapped for uplink/downlink links. Specifically, if negotiation is not done through ML setup, all TIDs may be used for ML communication, and if mapping between uplink/downlink links and TIDs is negotiated through additional ML setup, the negotiated TIDs may be used for ML communication.
A plurality of links that can be used by the transmitting MLD and the receiving MLD related to ML communication can be set through ML setup, and this can be called an enabled link. The enabled link can be called differently in a variety of ways. For example, it may be called various expressions such as a first link, a second link, a transmitting link, and a receiving link.
After the ML setup is complete, the MLD may update the ML setup. For example, the MLD may transmit information about a new link when updating information about a link is required. Information about the new link may be transmitted based on at least one of a management frame, a control frame, and a data frame.
The device described below may be the apparatus of
In EHT (extremely high throughput), a standard being discussed after 802.11ax, a multi-link environment in which one or more bands are simultaneously used is considered. When a device supports multi-link, the device can simultaneously or alternately use one or more bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, 60 GHz, etc.).
In the following specification, MLD means a multi-link device. The MLD has one or more connected STAs and has one MAC service access point (SAP) that communicates with the upper link layer (Logical Link Control, LLC). MLD may mean a physical device or a logical device. Hereinafter, a device may mean an MLD.
In the following specification, a transmitting device and a receiving device may mean MLD. The first link of the receiving/transmitting device may be a terminal (e.g., STA or AP) included in the receiving/transmitting device and performing signal transmission/reception through the first link. The second link of the receiving/transmitting device may be a terminal (e.g., STA or AP) that transmits/receives a signal through the second link included in the receiving/transmitting device.
In IEEE802.11be, two types of multi-link operations can be supported. For example, simultaneous transmit and receive (STR) and non-STR operations may be considered. For example, STR may be referred to as asynchronous multi-link operation, and non-STR may be referred to as synchronous multi-link operation. Multi-links may include multi-bands. That is, multi-links may mean links included in several frequency bands or may mean multiple links included in one frequency band.
EHT (11be) considers multi-link technology, where multi-link may include multi-band. That is, multi-link can represent links of several bands and multiple multi-links within one band at the same time. Two major multi-link operations are being considered. Asynchronous operation, which enables TX/RX simultaneously on several links, and synchronous operation, which is not possible, are being considered. Hereinafter, a capability that enables simultaneous reception and transmission on multiple links is referred to as STR (simultaneous transmit and receive), an STA having STR capability is referred to as STR MLD (multi-link device), and an STA that does not have STR capability is referred to as a non-STR MLD.
In the following specification, for convenience of explanation, it is described that the MLD (or the processor of the MLD) controls at least one STA, but is not limited thereto. As described above, the at least one STA may transmit and receive signals independently regardless of MLD.
According to an embodiment, an AP MLD or a non-AP MLD may have a structure having a plurality of links. In other words, a non-AP MLD can support multiple links. A non-AP MLD may include a plurality of STAs. A plurality of STAs may have Link for each STA.
In the EHT standard (802.11be standard), the MLD (Multi-Link Device) structure in which one AP/non-AP MLD supports multiple links is considered as a major technology. STAs included in the non-AP MLD may transmit information about other STAs in the non-AP MLD together through one link. Accordingly, there is an effect of reducing the overhead of frame exchange. In addition, there is an effect of increasing the link use efficiency of the STA and reducing power consumption.
Referring to
For example, the non-AP MLD may include STA 1, STA 2, and STA 3. STA 1 can operate on link 1. link 1 may be included in the 5 GHz band. STA 2 can operate on link 2. link 2 may be included in the 6 GHz band. STA 3 can operate on link 3. link 3 may be included in the 6 GHz band. Bands included in link 1/2/3 are exemplary and may be included in 2.4, 5, and 6 GHz.
As such, in the case of an AP/non-AP MLD supporting multi-link, each AP of the AP MLD and each STA of the non-AP MLD may be connected to each link through a link setup process. And at this time, the connected link can be changed or reconnected to another link by AP MLD or non-AP MLD depending on the situation.
In addition, in the EHT standard, a link may be classified as an anchored link or a non-anchored link in order to reduce power consumption. An anchored link or non-anchored link can be called variously. For example, an anchored link may be referred to as a primary link. A non-Anchored Link can be called a Secondary link.
According to an embodiment, an AP MLD supporting multi-link can be managed by designating each link as an anchored link or a non-anchored link. The AP MLD may support one or more links among a plurality of links as an anchored link. A non-AP MLD can use it by selecting one or more of its own anchored links from the Anchored Link List (list of anchored links supported by the AP MLD).
For example, Anchored Link can be used for non-data frame exchange (i.e. Beacon and Management frame) as well as frame exchange for synchronization. Also, non-anchored links can only be used for data frame exchange.
The non-AP MLD can monitor only the anchored link for receiving beacons and management frames during the idle period. Therefore, in the case of non-AP MLD, at least one anchored link must be connected to receive beacon and management frame. The one or more Anchored Links must always maintain an enable state. In contrast, non-anchored links are used only for data frame exchange. Accordingly, an STA corresponding to a non-anchored link (or an STA connected to a non-anchored link) may enter doze during an idle period not using a channel/link. This has the effect of reducing power consumption.
Therefore, in the following specification, a protocol for recommending or requesting link reconnection by an AP MLD or a non-AP MLD dynamically according to circumstances may be proposed for efficient link connection. In addition, in the following specification, an anchored link reconnection protocol considering characteristics of an anchored link used for the purpose of power reduction as well as a general link may be additionally proposed.
According to an embodiment, each link between an AP MLD and a non-AP MLD may be determined in an Association or (re)Association process. At this time, the AP MLD and the non-AP MLD can perform frame exchange through the connected Link. A specific embodiment in which an AP MLD and a non-AP MLD are connected through a link setup process can be described with reference to
Referring to
For example, AP 1 and STA 1 may be connected through link 1 through a first link setup process. AP 2 and STA 2 may be connected through link 2 through a second link setup process. For another example, AP MLD and non-AP MLD may be connected through a one-time link setup process. In other words, the AP MLD and the non-AP MLD may be connected through link 1 and link 2 based on a link setup process once.
As described above, each AP and STA may perform frame exchange through the connected Link. In addition, information of other APs on a different link or other STAs on a different link may be transmitted and received through one link.
However, after this link setup process, the AP MLD or non-AP MLD may request link change or reconnection for more efficient frame exchange (e.g., load balancing or interference avoiding, etc.) depending on the situation/environment.
An embodiment of link change or reconnection may be described with reference to
Referring to
Referring to
According to an embodiment, the non-AP MLD and the AP MLD may request link transition to improve performance. The AP MLD and the non-AP MLD can transmit/receive/exchange various information and link state information for each current link. Therefore, the AP MLD and the non-AP MLD can select a link more suitable for transmitting and receiving signals based on various information and link states for each current link, and can transmit the above-described information to help the selection. For example, various types of information for each current link may include information about data traffic load for each link and channel access capability between links. For example, a link state may be set to disable or enable.
In the following specification, the process of negotiating with the non-AP MLD/AP MLD to request a change or reconnection to a link other than the link to which the AP MLD/non-AP MLD is connected to improve performance may be referred to as “Link switching negotiation”. The name of the “Link switching negotiation” may be called variously, and may be changed.
In the link switching negotiation process, the non-AP MLD (or AP MLD) requests to change the Link connected to a specific STA to another Link, the AP MLD (or non-AP MLD) may respond to this request through a request acceptance or rejection message.
For example, as shown in
Hereinafter, a link change or reconnection process can be described by dividing into a case requested by an AP MLD and a case requested by a non-AP MLD.
According to an embodiment, the AP MLD may request link change or reconnection from the non-AP MLD for efficient data transmission. For example, based on data traffic of each AP for load balancing, the AP MLD may request the STA to change or reconnect to a more efficient link.
For example, AP MLD is non-AP MLD based on data traffic load information for each AP and/or channel access capability information between each link (e.g., Simultaneous TX/RX (STR) capability information, etc.) Links suitable for STAs of can be calculated/confirmed/confirmed. Thereafter, the AP MLD may request link change or reconnection to the STA (or non-AP MLD) based on data traffic load information for each AP and/or channel access capability information between each link.
As described above, when requesting a Link change, the AP MLD may transmit Link information it considers most suitable to the non-AP MLD through a request message. For example, the request message may include a Beacon or a management frame.
In relation to the above-described embodiment, an element or field including link information that is considered most suitable may be newly proposed. A newly proposed element or field may be defined as a “recommended link”. “Recommended link” is an example, and the name of a specific element or field may be changed.
recommend link (element/field): An element or field for the AP MLD to recommend the most suitable Link to the STA of the non-AP MLD based on various information (e.g., data load for each Link) for each Link. For example, recommend link (element/field) may be indicated by Link ID information of AP MLD or AP BSS information. In other words, the recommend link (element/field) may include AP MLD Link ID information or AP BSS information.
According to one embodiment, the recommend link (element/field) may optionally be included in a link switching response and transmitted. For example, the STA may establish a connection with the Link recommended by the AP based on the element/field (i.e., recommend Link). For another example, the STA may perform a connection request to a Link different from the indicated Link based on the element/field (i.e., recommend Link) and additional information possessed by the STA.
A detailed signal exchange process between an AP MLD and a non-AP MLD according to the above-described embodiment may be described with reference to
Referring to
The AP MLD (or AP 2) may request the non-AP MLD (or STA 2) to reconnect to AP 3 having relatively few STA connections. In general, a message for requesting reconnection is transmitted to the STA (i.e., STA 2) that wants to reconnect, but depending on the situation (e.g., channel status or link status), the message may be transmitted to any STA (i.e., other STA). In other words, based on the channel condition or link condition, the STA to which the request message for requesting reconnection (e.g., Link switching request frame) is transmitted may be changed.
For example, when the STA (i.e., STA 2) receiving the request message for requesting reconnection accepts the request, an “Accept” response message (e.g., Link switching response frame) may be sent. For another example, the STA (i.e., STA 2) may transmit a “Decline” response message when rejecting the request.
In general, the STA accepting reconnection (i.e., STA 2) sends a response message to the existing link (connection link prior to reconnection), the response message may be transmitted through any Link (i.e., another STA) using the multi-link characteristic.
If STA 2 accepts the link reconnection request, after transmitting the response message, STA 2 may disconnect from the existing AP 2 and request link reconnection to AP 3. At this time, the reconnection request process may be performed in the same way as the link setup process between existing MLDs. After the link setup process between AP 3 and STA 2 is completed, STA 2 may perform frame exchange with AP 3 through Link 2.
Conversely, when STA 2 rejects the link reconnection request, STA 2 and AP 2 may use the existing linked link (i.e., link 2) as it is.
According to an embodiment, when an AP requests a link change from an STA, if a suitable link is recommended, the STA may or may not change the link to the recommended link. For example, the above-described recommend link may be used for the AP to recommend a link suitable for the STA.
For example, the STA may approve a link change as a response message to a request message for requesting reconnection of the AP. The STA may approve/confirm the link change with the recommended link, and may request another link change from the AP based on information other than the information included in the request message.
Therefore, the AP needs to inform the STA whether or not to accept the response message. To this end, the AP may transmit a Confirmation message (e.g., link switching confirmation frame) for the STA's response message (e.g., Link switching Response frame) to the STA.
Specific operations of the AP MLD and non-AP MLD of the above-described embodiment may be described with reference to
Referring to
STA 2 may transmit whether to accept the link request through a Link switching Response frame.
For example, when Link switching is accepted, STA 2 may transmit Link switching response frame including Link information to be changed. At this time, Link information to be changed may or may not be the same as the recommended link.
For another example, when STA 2 selects a link other than the recommended link provided by AP 2 and responds with a link switching response frame, the AP may transmit a message on whether or not to approve the final to the STA. The message may be referred to as a Link switching confirmation frame.
For example, AP 2 may accept link change to a link designated by STA 2 through a Link switching Confirmation frame. Based on the Link switching Confirmation frame, STA 2 may attempt to change the link to a link designated by itself.
As another example, AP 2 may reject link change to a link designated by STA 2 through a Link switching Confirmation frame. STA 2 and AP 2 can maintain a connection with an existing Link without changing the link.
The embodiment shown in
According to an embodiment, the non-AP MLD may request link change or reconnection to the AP MLD for efficient data transmission. For example, in order to use the STR capability during data transmission, the non-AP MLD may request connection link change or reconnection from the AP MLD.
Referring to
EHT (802.11be) considers a multi-link device (MLD) structure in which one AP/non-AP MLD supports multiple links as a major technology. In the case of supporting Multi-Link, an STA may transmit information about other STAs in a non-AP MLD together through one link. This characteristic can reduce the overhead of frame exchange, increase the STA's link use efficiency, and reduce power consumption. Therefore, this specification proposes a Buffer Status Report method considering Multi-Link, which can transfer the Buffer Status information of other Links at once through one Link.
This specification proposes a Buffer Status Report (BSR) operation considering multi-link usable in an 802.11be environment supporting multi-link.
In an AP/non-AP MLD connection structure connected by multiple Links, data transmission can be efficient if Buffer status information of other STAs in the same non-AP MLD can be transmitted together through one Link. At this time, it is assumed that each STA in the non-AP MLD has its own Buffer Queue.
In the existing 802.11ax standard, an A-Control field and a Control subfield as shown in
The upper part of
Referring to the bottom of
The Control ID subfield indicates the type of information delivered in the Control Information subfield. The length of the Control Information subfield is fixed for each value of the non-reserved Control ID subfield. The value of the Control ID subfield and the associated value of the Control Information subfield are defined as follows.
By including the value of the Control ID subfield defined in the table above and control information corresponding to the value in the Control Information subfield within the Control subfield and transmitting it, the STA can control or indicate various pieces of information.
If present, the Padding subfield comes after the last Control subfield and is set to a sequence of 0 to match the length of the A-Control field transmitted in the HT Control field to 30 bits.
802.11be proposes a multi-link device (MLD) structure supporting multi-link. Therefore, this specification proposes a control subfield structure considering multi-link in which an STA can request control information for several links (i.e., other STAs) at once.
To this end, this specification proposes the following Control subfield structure considering multi-link.
Unlike the existing structure, in the structure of
At this time, a new ‘Control Information per Link’ subfield including a Link ID subfield and a Control information subfield may be defined. An example of a detailed subfield structure for this is shown in
As shown in
For example, in the case of a field where the Control ID value is indicated as 3 to indicate the STA's BSR information, the Control Information per Link (i.e. Control information per Link) subfield includes Buffer status information for each Link (i.e., STA).
In this way, the reason why the information about each STA is indicated as the Link ID subfield in order to deliver information about other STAs through one link in this specification is that non-AP MLD and AP MLD This is because the Link ID subfield is used when determining which AP to establish a link with. In other words, since the non-AP MLD and AP MLD exchange Link ID information (i.e., Link ID subfield) for each link in the multi-link setup (i.e., association) process, the non-AP MLD determines which link each link It already knows if it has an identifier. Therefore, when transmitting information on other STAs in one frame, if information on other STAs is divided into Link ID subfields and transmitted, upon receiving this, the AP MLD can separately receive Link ID information and corresponding Control information regardless of the received Link.
The non-AP MLD may initiate multi-link setup related to the AP MLD to (re)establish one or more links with APs associated with the AP MLD. When the non-AP MLD initiates multi-link (re)setup with the AP MLD, the STA belonging to the non-AP MLD must transmit a (Re)Association Request frame in the link to be used as part of the multi-link (re)setup. The AP associated with the AP MLD must transmit the (Re)Association Response frame in the link receiving the (Re)Association Request frame.
An STA belonging to a non-AP MLD that initiates multi-link (re)setup with an AP MLD must include a Basic Multi-Link element in the transmitted (Re)Association Request frame.
Basic Multi-Link element included in (Re)Association Request frame must include Common Info field and Link Info field.
In addition to the link through which the (Re)Association Request frame is transmitted, the Link Info field of the Basic Multi-Link element included in the (Re)Association Request frame must include the corresponding Per-STA Profile subelement for each requested link. For each Per-STA Profile subelement included in the Link Info field, the Complete Profile subfield of the STA Control field shall be set to 1.
The Link ID subfield of the STA Control field of the Per-STA Profile subelement for the non-AP STA requesting a link for multi-link (re)setup with the AP MLD is set as the link ID of the AP associated with the AP MLD operating on the corresponding link. Link ID is obtained during multi-link discovery.
The STA may indicate control information for several links to the AP at once by including Control information per Link corresponding to several Control IDs in the Control List subfield of the A-Control field. A detailed field structure for this is shown in
In the present specification, a field structure in which an STA can deliver several pieces of control information at once for several links is proposed. In the case of the above definition, the STA can transmit control information for other STAs at once by transmitting including Control information subfield information for each Link in the Control Information per Link subfield. This field structure considering multi-link is particularly useful for non-AP MLD operating in power save mode. In 802.11be, for MLD supporting multi-link, beacon reception is not required for all links. This means that some links (e.g. anchor links) are periodically awake for beacon reception, but some other links (e.g. non-anchor links) can remain doze regardless of beacon reception to reduce power. As such, in the case of a non-AP MLD operating in power save mode, it is inefficient in terms of power consumption to awake all corresponding links to transmit control information of the STA through the A-Control field. Therefore, using the method and structure proposed in this specification, if all links can transmit one frame including information of other STAs together using links of STAs currently in an awake state or waiting for transmission of UL traffic, without needing to be awake for information transmission, this will be very efficient not only in terms of frame overhead but also in terms of power saving.
Additionally, in this specification, a structure for indicating control information for several links usable in 802.11be is proposed as follows.
When requesting control information through the existing Link ID field, since the Link ID field is 4 bits, it may be difficult to indicate and request information of several links at once through the A-Control (sub) field. The A-Control (sub)field structure defined in the existing 802.11ax is the same as the top of
Accordingly, in the present specification, a Link ID Indication (LII) Bitmap capable of indicating several links at once is defined.
If a specific Link ID can be indicated through the LII Bitmap, the STA can provide control information information of several links through one A-Control field. An embodiment for this is shown in
As shown in
In addition, although the non-AP MLD requests information of the same Information type, considering the case of having different Control Information for each link (when the corresponding Control Information is defined as STA Level information rather than MLD Level), the format shown in
Referring to
In addition, when providing various types of control information for a specific link, the format shown in
As shown in
Also, information on multiple links rather than one link may be included in one A-control subfield as shown in
Referring to
However, in this case, due to the length of the A-Control subfield, the contents included may be limited according to the length of control information according to the information type. For this purpose, it may be necessary to propose a control information format for additional MLD.
Additionally, in this specification, a structure for MLD level control information usable in 802.11be is proposed as shown in
If the information type (see Table 1 above) previously provided as control information is defined as the same value for each MLD (i.e., defined as MLD level information), the A-Control field in
In particular, the present specification focuses on the BSR (Buffer Status Report) operation of non-AP MLD and proposes a BSR Control Information subfield structure for BSR operation considering multi-link that can increase various efficiencies as follows.
To this end, a control subfield structure considering BSR multi-link as shown in
Since the BSR Control subfield of
The proposed BSR Control Information subfield structure for each link is shown in
The Control Information per Link subfield in the BSR Control subfield has as many BSR Control Information subfields as the number of Links in the non-AP MLD (see
The Link ID subfield means a link identifier for identifying a link, and the rest of the fields are the same as the field values defined in the existing 802.11 standard. An example of the BSR Control subfield for each link using the link identifier is shown in
Additionally, this specification proposes a lightweight BSR Control subfield suitable for multi-link devices. According to the existing standard, the Control ID field is 4 bits and the length of the Control information subfield corresponding to the BSR is 26 bits (see Table 1 above). The sum of these two equals 30 bits. Currently, the length of the A-Control field defined in 802.11ax is 30 bits (see
Therefore, when link indicator information for requesting information for each link of a multi-link device is included, the length of the existing standard may be exceeded. Therefore, in this specification, a new format in which the control information format defined for BSR operation is lightened is proposed as follows.
First, the control information subfield format for the existing BSR control is shown in
Referring to
The ACI Bitmap subfield indicates the access category for which the buffer status is reported, and its encoding is shown in Table 2. Each bit of the ACI Bitmap subfield is set to 1 to indicate that the buffer status of the corresponding AC (Access Category) is included in the Queue Size All subfield, and is set to 0 otherwise. However, when the ACI Bitmap subfield is 0 and the Delta TID subfield is 3, it is set as above except that the buffer status of all 8 Traffic Identifiers (TIDs) is included. (See Table 3).
The Delta TID subfield indicates the number of TIDs for STAs reporting the buffer status together with the value of the ACI Bitmap subfield. The encoding of the Delta TID subfield is defined in Table 3.
The ACI High subfield indicates the ACI of the AC for which the BSR is indicated in the Queue Size High subfield. ACI to AC mapping is shown in Table 4.
The Scaling Factor subfield indicates the unit SF (Scaling Factor, Octet) of the Queue Size High and Queue Size All subfields. The encoding of the Scaling Factor subfield is shown in Table 5.
The Queue Size High subfield indicates the amount of traffic buffered for the AC identified by the ACI High subfield for the STA identified by the receiver address of the frame including the BSR Control subfield in units of SF octets.
The Queue Size All subfield indicates the amount of buffered traffic in units of SF octets for all ACs identified by the ACI Bitmap subfield for the STA identified by the receiver address of the frame including the BSR Control subfield.
The queue size value of the Queue Size High and Queue Size All subfields is a value obtained by rounding the total size of all MSDUs and A-MSDUs (including MSDUs or A-MSDUs in the same PSDU as the frame containing the BSR Control subfield) buffered in the STA to the nearest multiple of SF octets in the delivery queue used for MSDUs and A-MSDUs with AC(s) specified in the ACI High and ACI Bitmap subfields, respectively.
A queue size value of 254 in the Queue Size High and Queue Size All subfields indicates that the amount of buffered traffic is greater than 254×SF octets. A queue size value of 255 in the Queue Size High and Queue Size All subfields indicates that the amount of buffered traffic is unspecified or unknown.
The queue size value of QoS data frames containing fragments can be kept constant in all fragments even if the amount of queued traffic changes as successive fragments are transmitted. When a QoS data frame including a fragment is delivered in an A-MPDU, the queue size value of the MPDU including a fragment is set according to the rules of the HT control field operation.
In 802.11be, the Link ID subfield was defined as an indicator for indicating each link, and it was agreed to define it as 4 bits. Considering this, when the Link ID subfield is included in the control information for requesting BSR information for each link of MLD, 4 bits are exceeded, so a lightweight format considering this is required to reuse the existing A-Control field. The way to narrow the existing A-Control field to request BSR information for each link of MLD is as follows.
1) Format Omitting Queue Size all Information
When the STA provides its Buffer Status information by BSR operation (Solicited method or Unsolicited method), an embodiment is shown in
The Queue Size All subfield included in the existing format (
As such, when using the new format of
2) Format Omitting ACI High Information
An example of a new format for the case where the ACI High information is omitted when the STA provides its own Buffer Status information by BSR operation (Solicited method or Unsolicited method) is shown in
Referring to
Unlike the conventional method of indicating Buffer status information for one STA indicated by one RA, this specification proposes a method of indicating Buffer status information for all STAs in a non-AP MLD in one frame.
Upon receiving this, the AP MLD can allocate resources for UL-MU operation in consideration of the Buffer status of all STAs in the non-AP MLD.
An example of the field format proposed in
In the case of unsolicited BSR operation as shown in
Even in a Solicited BSR operation in which an AP requests a BSR from an STA, the STA may transmit the BSR for all STAs in the non-AP MLD by responding to the proposed frame through one link, as in
Hereinafter, the above-described embodiment will be described with reference to
The example of
This embodiment newly defines the existing A-Control field to support Multi-Link, and propose a method and apparatus for transmitting and receiving BSR information of another link (or other receiving STA) based on the newly defined A-Control field. Here, the transmitting MLD may correspond to the AP MLD, and the receiving MLD may correspond to the non-AP MLD.
In step S3510, a transmitting multi-link device (MLD) receives an A-Control field from a receiving MLD through a first link.
In step S3520, the transmitting MLD decodes the A-Control field.
The transmitting MLD includes a first transmitting station (STA) operating on the first link, a second transmitting STA operating on a second link, and a third transmitting STA operating on a third link.
The receiving MLD includes a first receiving STA operating on the first link, a second receiving STA operating on the second link, and a third receiving STA operating on the third link.
The A-Control field includes a control identifier and control information for a Buffer Status Report (BSR). The control information for the BSR may be set based on the control identifier. A value of the control identifier may be 3. The A-Control field is composed of the control identifier and control information according to the control identifier. When the value of the control identifier is 3, the control information may be set as control information for the BSR.
The control information for the BSR includes a link identifier, an Access Category Index (ACI) bitmap subfield, a Delta Traffic Identifier (TID) subfield, an ACI High subfield, a Scaling Factor subfield, and a Queue Size High subfield.
Control information for a BSR supporting one existing link includes the ACI bitmap subfield, the Delta TID subfield, the ACI High subfield, the scaling factor subfield, the Queue Size High subfield, and the Queue Size All subfield. The ACI bitmap subfield is 4 bits, the Delta TID subfield is 2 bits, the ACI High subfield is 2 bits, the scaling factor subfield is 2 bits, the Queue Size High subfield is 8 bits, and the Queue Size All subfield is 8 bits. That is, the control information for the existing BSR consists of a total of 26 bits.
When the A-Control field defined in the 802.11ax wireless LAN system includes a control identifier and control information for BSR (supporting one link), since the control identifier is 4 bits and the control information for the existing BSR is 26 bits, it is assumed that the A-Control field must be configured within 30 bits.
However, as in this embodiment, when the link identifier is included in the control information for the BSR to configure the control information for the BSR supporting Multi-Link, since the link identifier is 4 bits, there may be a problem that the size of the A-Control field exceeds 30 bits. Accordingly, in order to include control information for the BSR supporting Multi-Link using the existing A-Control field, a format that is lighter than the control information for the existing BSR is required. This embodiment proposes a method for transmitting and receiving BSR information for another receiving STA in a receiving MLD (non-AP MLD) in one frame (the A-Control field) by omitting some subfields (Queue Size All subfields to be described later) in the control information for the existing BSR to configure the control information of the A-Control field. According to this embodiment, frame overhead can be reduced by transmitting and receiving BSR information (or control information) for several links in one frame. Even if the link of another STA is not in an awake state, it is possible to transmit BSR information of the other STA using the link of a specific STA, which is effective in terms of power saving.
According to this embodiment, the control information for the BSR may omit the Queue Size All subfield. Since the Queue Size All subfield is omitted, the control information for the BSR may include information on an amount of buffered traffic for an access category (AC) identified by the ACI High subfield. Also, the Delta TID subfield may be omitted according to a value of the ACI bitmap subfield.
As another example, a case of omitting the ACI High subfield may also be considered. Since the ACI High subfield is omitted, the control information for the BSR may include information on an amount of buffered traffic for all ACs indicated through the ACI bitmap subfield of a specific link (or buffer information in all queues for each link).
When the link identifier is an identifier for the second link, the control information for the BSR may be BSR information for the second link. When the link identifier is an identifier for the third link, the control information for the BSR may be BSR information for the third link. That is, BSR information for a link can be determined according to the link identifier.
For example, when the link identifier is an identifier for the second link, the receiving MLD (or the first receiving STA) may include the BSR information for the second link in the A-Control field and transmit it to the transmitting MLD (or the first transmitting STA). When the link identifier is an identifier for the third link, the receiving MLD (or the first receiving STA) may include the BSR information for the third link in the A-Control field and transmit it to the transmitting MLD (or the first transmitting STA).
The first receiving STA may be in an awake state or in a state in which there is traffic buffered for Uplink (UL) transmission. Alternatively, the second and third receiving STAs may be in a doze state. As described above, it is inefficient in terms of power consumption for the receiving MLD operating in power saving mode to awake all receiving STAs to transmit control information of the receiving STA through the A-Control field. According to this embodiment, the BSR information of the second or third receiving STA can be transmitted through the A-Control field without awakening the second and third receiving STAs, and it has the effect of being efficient in terms of power saving.
When a separate link identifier is included in the A-Control field, the link identifier is omitted from the control information for the BSR.
The example of
This embodiment newly defines the existing A-Control field to support Multi-Link, and propose a method and apparatus for transmitting and receiving BSR information of another link (or other receiving STA) based on the newly defined A-Control field. Here, the transmitting MLD may correspond to the AP MLD, and the receiving MLD may correspond to the non-AP MLD.
In step S3610, a receiving multi-link device (MLD) generates an A-Control field.
In step S3620, the receiving MLD transmits the A-Control field to a transmitting MLD through a first link.
The transmitting MLD includes a first transmitting station (STA) operating on the first link, a second transmitting STA operating on a second link, and a third transmitting STA operating on a third link.
The receiving MLD includes a first receiving STA operating on the first link, a second receiving STA operating on the second link, and a third receiving STA operating on the third link.
The A-Control field includes a control identifier and control information for a Buffer Status Report (BSR). The control information for the BSR may be set based on the control identifier. A value of the control identifier may be 3. The A-Control field is composed of the control identifier and control information according to the control identifier. When the value of the control identifier is 3, the control information may be set as control information for the BSR.
The control information for the BSR includes a link identifier, an Access Category Index (ACI) bitmap subfield, a Delta Traffic Identifier (TID) subfield, an ACI High subfield, a Scaling Factor subfield, and a Queue Size High subfield.
Control information for a BSR supporting one existing link includes the ACI bitmap subfield, the Delta TID subfield, the ACI High subfield, the scaling factor subfield, the Queue Size High subfield, and the Queue Size All subfield. The ACI bitmap subfield is 4 bits, the Delta TID subfield is 2 bits, the ACI High subfield is 2 bits, the scaling factor subfield is 2 bits, the Queue Size High subfield is 8 bits, and the Queue Size All subfield is 8 bits. That is, the control information for the existing BSR consists of a total of 26 bits.
When the A-Control field defined in the 802.11ax wireless LAN system includes a control identifier and control information for BSR (supporting one link), since the control identifier is 4 bits and the control information for the existing BSR is 26 bits, it is assumed that the A-Control field must be configured within 30 bits.
However, as in this embodiment, when the link identifier is included in the control information for the BSR to configure the control information for the BSR supporting Multi-Link, since the link identifier is 4 bits, there may be a problem that the size of the A-Control field exceeds 30 bits. Accordingly, in order to include control information for the BSR supporting Multi-Link using the existing A-Control field, a format that is lighter than the control information for the existing BSR is required. This embodiment proposes a method for transmitting and receiving BSR information for another receiving STA in a receiving MLD (non-AP MLD) in one frame (the A-Control field) by omitting some subfields (Queue Size All subfields to be described later) in the control information for the existing BSR to configure the control information of the A-Control field. According to this embodiment, frame overhead can be reduced by transmitting and receiving BSR information (or control information) for several links in one frame. Even if the link of another STA is not in an awake state, it is possible to transmit BSR information of the other STA using the link of a specific STA, which is effective in terms of power saving.
According to this embodiment, the control information for the BSR may omit the Queue Size All subfield. Since the Queue Size All subfield is omitted, the control information for the BSR may include information on an amount of buffered traffic for an access category (AC) identified by the ACI High subfield. Also, the Delta TID subfield may be omitted according to a value of the ACI bitmap subfield.
As another example, a case of omitting the ACI High subfield may also be considered. Since the ACI High subfield is omitted, the control information for the BSR may include information on an amount of buffered traffic for all ACs indicated through the ACI bitmap subfield of a specific link (or buffer information in all queues for each link).
When the link identifier is an identifier for the second link, the control information for the BSR may be BSR information for the second link. When the link identifier is an identifier for the third link, the control information for the BSR may be BSR information for the third link. That is, BSR information for a link can be determined according to the link identifier.
For example, when the link identifier is an identifier for the second link, the receiving MLD (or the first receiving STA) may include the BSR information for the second link in the A-Control field and transmit it to the transmitting MLD (or the first transmitting STA). When the link identifier is an identifier for the third link, the receiving MLD (or the first receiving STA) may include the BSR information for the third link in the A-Control field and transmit it to the transmitting MLD (or the first transmitting STA).
The first receiving STA may be in an awake state or in a state in which there is traffic buffered for Uplink (UL) transmission. Alternatively, the second and third receiving STAs may be in a doze state. As described above, it is inefficient in terms of power consumption for the receiving MLD operating in power saving mode to awake all receiving STAs to transmit control information of the receiving STA through the A-Control field. According to this embodiment, the BSR information of the second or third receiving STA can be transmitted through the A-Control field without awakening the second and third receiving STAs, and it has the effect of being efficient in terms of power saving.
When a separate link identifier is included in the A-Control field, the link identifier is omitted from the control information for the BSR.
The technical features of the present disclosure may be applied to various devices and methods. For example, the technical features of the present disclosure may be performed/supported through the device(s) of
The technical features of the present disclosure may be implemented based on a computer readable medium (CRM). For example, a CRM according to the present disclosure is at least one computer readable medium including instructions designed to be executed by at least one processor.
The CRM may store instructions that perform operations including generating an A-Control field; and transmitting the A-Control field to a transmitting multi-link device (MLD) through a first link. At least one processor may execute the instructions stored in the CRM according to the present disclosure. At least one processor related to the CRM of the present disclosure may be the processor 111, 121 of
The foregoing technical features of the present specification are applicable to various applications or business models. For example, the foregoing technical features may be applied for wireless communication of a device supporting artificial intelligence (AI).
Artificial intelligence refers to a field of study on artificial intelligence or methodologies for creating artificial intelligence, and machine learning refers to a field of study on methodologies for defining and solving various issues in the area of artificial intelligence. Machine learning is also defined as an algorithm for improving the performance of an operation through steady experiences of the operation.
An artificial neural network (ANN) is a model used in machine learning and may refer to an overall problem-solving model that includes artificial neurons (nodes) forming a network by combining synapses. The artificial neural network may be defined by a pattern of connection between neurons of different layers, a learning process of updating a model parameter, and an activation function generating an output value.
The artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include synapses that connect neurons. In the artificial neural network, each neuron may output a function value of an activation function of input signals input through a synapse, weights, and deviations.
A model parameter refers to a parameter determined through learning and includes a weight of synapse connection and a deviation of a neuron. A hyper-parameter refers to a parameter to be set before learning in a machine learning algorithm and includes a learning rate, the number of iterations, a mini-batch size, and an initialization function.
Learning an artificial neural network may be intended to determine a model parameter for minimizing a loss function. The loss function may be used as an index for determining an optimal model parameter in a process of learning the artificial neural network.
Machine learning may be classified into supervised learning, unsupervised learning, and reinforcement learning.
Supervised learning refers to a method of training an artificial neural network with a label given for training data, wherein the label may indicate a correct answer (or result value) that the artificial neural network needs to infer when the training data is input to the artificial neural network. Unsupervised learning may refer to a method of training an artificial neural network without a label given for training data. Reinforcement learning may refer to a training method for training an agent defined in an environment to choose an action or a sequence of actions to maximize a cumulative reward in each state.
Machine learning implemented with a deep neural network (DNN) including a plurality of hidden layers among artificial neural networks is referred to as deep learning, and deep learning is part of machine learning. Hereinafter, machine learning is construed as including deep learning.
The foregoing technical features may be applied to wireless communication of a robot.
Robots may refer to machinery that automatically process or operate a given task with own ability thereof. In particular, a robot having a function of recognizing an environment and autonomously making a judgment to perform an operation may be referred to as an intelligent robot.
Robots may be classified into industrial, medical, household, military robots and the like according uses or fields. A robot may include an actuator or a driver including a motor to perform various physical operations, such as moving a robot joint. In addition, a movable robot may include a wheel, a brake, a propeller, and the like in a driver to run on the ground or fly in the air through the driver.
The foregoing technical features may be applied to a device supporting extended reality.
Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphic technology of providing a real-world object and background only in a CG image, AR technology is a computer graphic technology of providing a virtual CG image on a real object image, and MR technology is a computer graphic technology of providing virtual objects mixed and combined with the real world.
MR technology is similar to AR technology in that a real object and a virtual object are displayed together. However, a virtual object is used as a supplement to a real object in AR technology, whereas a virtual object and a real object are used as equal statuses in MR technology.
XR technology may be applied to a head-mount display (HMD), a head-up display (HUD), a mobile phone, a tablet PC, a laptop computer, a desktop computer, a TV, digital signage, and the like. A device to which XR technology is applied may be referred to as an XR device.
The claims recited in the present specification may be combined in a variety of ways. For example, the technical features of the method claims of the present specification may be combined to be implemented as a device, and the technical features of the device claims of the present specification may be combined to be implemented by a method. In addition, the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented as a device, and the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented by a method.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2021-0019504 | Feb 2021 | KR | national |
This application is the National Stage filing under 35 U.S.C. 371 of International Application No. PCT/KR2022/001842, filed on Feb. 7, 2022, which claims the benefit of earlier filing date and right of priority to Korean Application No. 10-2021-0019504, filed on Feb. 10, 2021, the contents of which are all incorporated by reference herein in their entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2022/001842 | 2/7/2022 | WO |
