Wireless communication method using multilink and wireless communication terminal using the same
The wireless communication method and terminal optimize traffic management across multiple links using multilink technology, addressing throughput and density challenges in wireless LANs by efficiently distributing traffic, enhancing performance in high-density environments.
Patent Information
- Application Number
- JP2026197507
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-05-27
- Filing Date
- 2026-08-31
- Publication Date
- 2026-11-19
AI Technical Summary
Existing wireless LAN standards face challenges in supporting very high throughput (VHT) and efficient communication in high-density environments with dense access points and terminals, necessitating improved methods for managing traffic across multiple links.
A wireless communication method and terminal utilizing multilink technology, including a transceiver and processor that manage traffic across multiple links by interpreting beacon frames with TIM and Multi-Link Traffic elements to determine buffered traffic and recommend optimal link usage, employing Per-Link Traffic Indication Bitmap subfields for efficient traffic management.
The method enables efficient use of multilink communication, optimizing traffic distribution across multiple links for improved throughput and reliability in high-density wireless LAN environments.
Smart Images

Figure 2026182909000001_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present invention relates to a wireless communication method using multilink and a wireless communication terminal using the same.
BACKGROUND ART
[0002] Recently, as the penetration of mobile devices has expanded, Wireless LAN (WLAN) technology that can provide fast wireless Internet services to these devices has attracted attention. WLAN technology is a technology that enables mobile devices such as smartphones, smart pads, laptop PCs, portable multimedia players, and embedded devices to wirelessly connect to the Internet in homes, enterprises, or specific service providing areas, based on short-range wireless communication technology.
[0003] Since IEEE (Institute of Electrical and Electronics Engineers) 802.11 supported the initial WLAN technology using the 2.4GHz frequency, various technical standards have been put into practical use or are under development. First, IEEE 802.11b uses the 2.4GHz band frequency and supports a maximum communication speed of 11Mbps. IEEE 802.11a, which was commercialized after IEEE 802.11b, uses the 5GHz band frequency instead of the 2.4GHz band, thereby reducing the impact of interference compared to the considerably congested 2.4GHz band frequency, and uses OFDM technology to increase the communication speed up to 54Mbps. However, IEEE 802.11a has the disadvantage of a shorter communication distance than IEEE 802.11b. Then, IEEE 802.11g, like IEEE 802.11b, uses the 2.4GHz band to achieve a maximum communication speed of 54Mbps, satisfies backward compatibility and has attracted considerable attention, and is also superior to IEEE 802.11a in terms of communication distance.
[0004] Furthermore, IEEE 802.11n is a technical standard established to overcome the limitations in communication speed that had been pointed out as a vulnerability in wireless LANs. The purpose of IEEE 802.11n is to increase network speed and reliability and extend the operating range of wireless networks. Specifically, IEEE 802.11n supports high throughput (HT) with a data processing speed of up to 540 Mbps or more, and is based on MIMO (Multiple Inputs and Multiple Outputs) technology, which uses multiple antennas at both the transmitter and receiver ends to minimize transmission errors and optimize data speed. In addition, this standard uses a coding method that transmits multiple duplicate copies to improve data reliability.
[0005] As the proliferation of wireless LANs accelerates and the applications using them diversify, there is a growing need for new wireless LAN systems that can support very high throughput (VHT) higher than the data processing speed supported by IEEE 802.11n. Among these, IEEE 802.11ac supports a wide bandwidth (80MHz to 160MHz) at the 5GHz frequency. Although the IEEE 802.11ac standard is defined only in the 5GHz band, early 11ac chipsets are expected to support operation in the 2.4GHz band for backward compatibility with older 2.4GHz band products. Theoretically, this standard allows for a minimum wireless LAN speed of 1Gbps and a maximum single-link speed of 500Mbps. This is achieved by extending the wireless interface concepts accepted in 802.11n, including wider radio frequency bandwidth (up to 160MHz), more MIMO spatial streams (up to 8), multi-user MIMO, and high-density modulation (up to 256QAM). Another method for transmitting data using the 60GHz band instead of the conventional 24GHz / 5GHz band is IEEE 802.11ad. IEEE 802.11ad is a transmission standard that utilizes beamforming technology to provide speeds of up to 7Gbps, making it suitable for streaming large amounts of data and high-bitrate video such as uncompressed HD video. However, the 60GHz frequency band has the disadvantage of being difficult to pass through obstacles, limiting its use to devices in short-range spaces.
[0006] Meanwhile, the IEEE 802.11ax (High Efficiency WLAN, HEW) standard has been developed and is nearing completion as a wireless LAN standard for 802.11ac and 802.11ad and beyond, to provide highly efficient and high-performance wireless LAN communication technology in high-density environments where access points (APs) and terminals are densely packed. In an 802.11ax-based wireless LAN environment, it is necessary to provide highly frequency-efficient communication indoors and outdoors in the presence of high-density stations and APs (Access Points), and various technologies have been developed to realize this.
[0007] Furthermore, in order to support new multimedia applications such as high-definition video and real-time games, development has begun on a new wireless LAN standard to increase the maximum transmission speed. The 7th generation wireless LAN standard, IEEE 802.11be (Extremely High Throughput, EHT), is currently under development with the goal of supporting a maximum transmission rate of 30 Gbps in the 2.4 / 5 / 6 GHz band through wider bandwidth, increased spatial streams, and multiple AP coordination. [Overview of the Initiative] [Problems that the invention aims to solve]
[0008] One embodiment of the present invention aims to provide a wireless communication method using multilink and a wireless communication terminal using the same. [Means for solving the problem]
[0009] In one embodiment of the present invention, a non-AP (access point) multilink device including a plurality of stations operating on a plurality of links includes a transceiver and a processor. The processor receives a beacon frame including a TIM element and a Multi-Link Traffic element from the AP multilink device and determines whether traffic for the non-AP multilink device is buffered in the AP multilink device based on the Partial Virtual Bitmap subfield of the TIM element. In this case, the Partial Virtual Bitmap subfield includes one or more first bits and one or more second bits, where one of the one or more first bits indicates that traffic for the non-AP multilink device corresponding to that bit has been buffered in the AP multilink device, and one of the one or more second bits indicates that traffic for the non-AP station corresponding to that bit has been buffered in the AP multilink device. When traffic for the non-AP multilink device is buffered by the AP multilink device, the processor determines, based on the Per-Link Traffic Indication List subfield of the Multi-Link Traffic element, which of the multiple links buffered the traffic for the non-AP multilink device, or which of the multiple links the AP multilink device recommends the non-AP multilink device retrieve traffic from.In this case, the Per-Link Traffic Indication List subfield includes n Per-Link Traffic Indication Bitmap subfields, where n is the sum of the number of bits set to 1 among the one or more first bits and the number of bits set to 1 among the one or more second bits, and each of the n Per-Link Traffic Indication Bitmap subfields is mapped to a non-AP multilink device corresponding to the bit set to 1 among the one or more first bits and to a non-AP station corresponding to the bit set to 1 among the one or more second bits.
[0010] The Per-Link Traffic Indication Bitmap subfield that maps to a non-AP station corresponding to one or more of the second bits set to 1 may be set as a reserved bit.
[0011] The value of the reserved bit may be 0.
[0012] If the non-AP multilink device successfully performs TID-to-link mapping with the AP multilink device, and not all TIDs are mapped to all links, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device indicates whether traffic for the non-AP multilink device is buffered on each of the multiple links.
[0013] When a default mapping is applied to the link between the non-AP multilink device and the AP multilink device, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device can indicate which of the multiple links the non-AP multilink device recommends directing traffic transmission to. In this case, the default mapping is one in which all TIDs are mapped to all links.
[0014] Of the bits in the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device, bits corresponding to links not configured by the AP multilink device or the non-AP multilink device may be set as reserved bits.
[0015] Of the bits in the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device, the bits corresponding to disabled links of the non-AP multilink device may be set as reserved bits. The disabled link may be a link on which uplink and downlink transmission has been stopped.
[0016] The multiple link IDs may be mapped in ascending order to the bits of the Per-Link Traffic Indication Bitmap subfield that is mapped to the non-AP multilink device.
[0017] If the AP that transmitted the beacon frame does not belong to a multiple BSSID set, the range of values that the AP multilink device can assign as an AID (association ID) may be determined based on the value of the Group Addressed BU Indication Exponent subfield. The value of the Group Addressed BU Indication Exponent subfield can indicate the number of bits used by the AP multilink device to indicate a buffered group address frame that corresponds to an AP different from the AP that transmitted the beacon frame.
[0018] When the AP that transmitted the beacon frame from the AP multilink device belongs to a multiple BSSID set, the range of values that the AP multilink device can assign as AID may be determined based on the value of the Group Addressed BU Indication Exponent subfield and the bitmap limit. In this case, the bitmap limit may be 48 bits.
[0019] An access point (AP) multilink device according to an embodiment of the present invention, which includes a plurality of stations operating on a plurality of links, includes a transmitting / receiving unit and a processor. The processor sets a TIM element and a Multi-Link Traffic element included in a beacon frame to be transmitted to a non-AP multilink device. In this case, the TIM element includes a Partial Virtual Bitmap subfield. The Partial Virtual Bitmap subfield includes one or more first bits and one or more second bits, the bit set to one of the one or more first bits indicates that traffic for the non-AP multilink device corresponding to that bit has been buffered in the AP multilink device, and the bit set to one of the one or more second bits indicates that traffic for the non-AP station corresponding to that bit has been buffered in the AP multilink device. When traffic for the non-AP multilink device is buffered by the AP multilink device, the processor sets the Per-Link Traffic Indication List subfield of the Multi-Link Traffic element depending on which of the multiple links is buffering traffic for the non-AP multilink device, or which of the multiple links the AP multilink device recommends the non-AP multilink device retrieve traffic from.
[0020] The processor transmits the beacon frame via the transmitting / receiving unit.
[0021] The Per-Link Traffic Indication List subfield includes n Per-Link Traffic Indication Bitmap subfields, where n is the sum of the number of bits set to 1 among the one or more first bits and the number of bits set to 1 among the one or more second bits. Each of the n Per-Link Traffic Indication Bitmap subfields is mapped to a non-AP multilink device corresponding to the bit set to 1 among the one or more first bits and to a non-AP station corresponding to the bit set to 1 among the one or more second bits.
[0022] The processor can set a Per-Link Traffic Indication Bitmap subfield, which maps to a non-AP station corresponding to a bit set to 1 among the one or more second bits, as a reserved bit.
[0023] The value of the reserved bit may be 0.
[0024] If the non-AP multilink device successfully performs TID-to-link mapping with the AP multilink device, and not all TIDs are mapped to all links, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device can indicate whether or not traffic for the non-AP multilink device is buffered on each of the multiple links.
[0025] When a default mapping is applied to the link between the non-AP multi-link device and the AP multi-link device, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multi-link device can indicate which one of the plurality of links is the link that the non-AP multi-link device recommends to guide traffic transmission. At this time, the default mapping may be a mapping in which all TIDs are mapped to all links.
[0026] The processor can set, as a reserved bit, a bit corresponding to a link that is not configured by the AP multi-link device or the non-AP multi-link device, among bits of the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multi-link device.
[0027] The processor can set, as a reserved bit, a bit corresponding to a disabled link of the non-AP multi-link device, among bits of the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multi-link device. The disabled link may be a link on which uplink and downlink transmissions are suspended.
[0028] The plurality of link IDs may be mapped in ascending order to the bits of the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multi-link device.
[0029] When the AP that transmitted the beacon frame in the AP multi-link apparatus does not belong to a multiple BSSID set, the range of values that the AP multi-link apparatus can assign as an AID (association ID) may be determined based on the value of the Group Addressed BU Indication Exponent subfield. The value of the Group Addressed BU Indication Exponent subfield may indicate the number of bits used to indicate buffered group addressed frames corresponding to APs different from the AP that transmitted the beacon frame in the AP multi-link apparatus.
[0030] When the AP that transmitted the beacon frame in the AP multi-link apparatus belongs to a multiple BSSID set, the range of values that the AP multi-link apparatus can assign as an AID may be determined based on the value of the Group Addressed BU Indication Exponent subfield and a bitmap limit. At this time, the bitmap limit may be 48 bits.
[0031] The operation method of a non-AP (access point) multilink device including multiple stations operating on multiple links is a step of receiving a beacon frame including a TIM element and a Multi-Link Traffic element from an AP multilink device, and a step of determining whether traffic for the non-AP multilink device is buffered in the AP multilink device based on the Partial Virtual Bitmap subfield of the TIM element, wherein the Partial Virtual Bitmap subfield includes one or more first bits and one or more second bits, the bit set to 1 of the one or more first bits indicates that traffic for the non-AP multilink device corresponding to the bit has been buffered in the AP multilink device, and the bit set to 1 of the one or more second bits indicates that traffic for the non-AP station corresponding to the bit has been buffered in the AP multilink device, and when traffic for the non-AP multilink device is buffered in the AP multilink device, the Per-Link Traffic Indication of the Multi-Link Traffic element The process includes determining, based on the List subfield, which of the multiple links buffered traffic for the non-AP multilink device, or which of the multiple links the AP multilink device recommends the non-AP multilink device retrieve traffic from.The Per-Link Traffic Indication List subfield includes n Per-Link Traffic Indication Bitmap subfields, where n is the sum of the number of bits set to 1 among the one or more first bits and the number of bits set to 1 among the one or more second bits, and each of the n Per-Link Traffic Indication Bitmap subfields is mapped to a non-AP multilink device corresponding to the bit set to 1 among the one or more first bits and to a non-AP station corresponding to the bit set to 1 among the one or more second bits.
[0032] The Per-Link Traffic Indication Bitmap subfield that maps to a non-AP station corresponding to one or more of the second bits set to 1 may be set as a reserved bit. [Effects of the Invention]
[0033] One embodiment of the present invention provides a wireless communication method that efficiently uses multilink and a wireless communication terminal that uses the same. [Brief explanation of the drawing]
[0034] [Figure 1] This figure shows a wireless LAN system according to one embodiment of the present invention. [Figure 2] This figure shows a wireless LAN system according to another embodiment of the present invention. [Figure 3] This figure shows the configuration of a station according to one embodiment of the present invention. [Figure 4] This figure shows the configuration of an access point according to one embodiment of the present invention. [Figure 5] This diagram schematically illustrates the process by which STA establishes a link with AP. [Figure 6]This diagram illustrates the CSMA (Carrier Sense Multiple Access) / CA (Collision Avoidance) method used in wireless LAN communication. [Figure 7] Examples of various standard generational PPDU (PLCP Protocol Data Unit) formats are shown. [Figure 8] Examples of various EHT (Extremely High Throughput) PPDU (Physical Protocol Data Unit) formats and methods for specifying them, according to embodiments of the present invention, are shown. [Figure 9] This shows a multi-link device according to an embodiment of the present invention. [Figure 10] This shows a multilink mapped by a TID-to-link mapping method according to an embodiment of the present invention. [Figure 11] This illustrates the power management operation performed by a station according to an embodiment of the present invention. [Figure 12] The format of a TIM element according to an embodiment of the present invention is shown. [Figure 13] The format of a Multi-Link Traffic element according to an embodiment of the present invention is shown. [Figure 14] This embodiment of the present invention shows how the Partial Virtual Bitmap subfield of a Multi-Link Traffic element and a TIM element signals buffered traffic to an AP multilink device. [Figure 15] This document describes a method for configuring a Multi-Link Traffic element according to an embodiment of the present invention. [Figure 16] This invention describes a method for setting the Per-Link Traffic Bitmap subfield of a Multi-Link Traffic element when the link set on which the AP multilink device operates and the link set on which the non-AP multilink device communicating with the AP multilink device operates are different. [Figure 17] This invention illustrates a method by which the link indicated by the Per-Link Traffic Bitmap subfield is determined by TID-to-link mapping. [Figure 18] This describes yet another embodiment of the present invention, in which an AP multilink device sets the Per-Link Traffic Indication Bitmap subfield of a Multi-Link Traffic element. [Figure 19] An EHT Operation element according to an embodiment of the present invention is shown. [Figure 20] This shows a Traffic indication virtual bitmap according to an embodiment of the present invention. [Figure 21] This shows a Traffic indication virtual bitmap according to an embodiment of the present invention. [Figure 22] This shows signaling related to a Multi-Link element and MediumSyncDelay according to one embodiment of the present invention. [Figure 23] This shows the multilink setup process according to an embodiment of the present invention. [Figure 24] The format of the Reduced Neighbor Report element according to an embodiment of the present invention is shown. [Figure 25] This document describes a method for setting the ID of a multilink device according to an embodiment of the present invention. [Figure 26] An embodiment of the present invention illustrates a method for assigning an AID to a non-AP station belonging to a multilink device. [Figure 27] An embodiment of the present invention illustrates a method for assigning an AID to a non-AP station belonging to a multilink device. [Figure 28] An embodiment of the present invention illustrates a TID-to-link mapping negotiation in which an AP multilink device transmits a TID-to-link mapping request. [Figure 29]An embodiment of the present invention illustrates a TID-to-link mapping negotiation in which an AP multilink device transmits a TID-to-link mapping request. [Figure 30] This invention illustrates a TID-to-link mapping negotiation in a case where the link set requesting TID-to-link mapping and the link set set by the TID-to-link mapping response are different. [Figure 31] This invention provides an embodiment of a method by which a non-AP multilink device can determine traffic buffered by an AP multilink device. [Modes for carrying out the invention]
[0035] The terminology used herein has been selected to the greatest extent possible from currently widely used general terms, taking into account the function of the present invention; however, this may differ depending on the intent, conventions, or emergence of new technologies of the articulators. In addition, in certain cases, the applicant has arbitrarily selected some terms, in which case their meaning will be described in the relevant section of the invention description. Therefore, it should be made clear that the terms used herein are not merely names of terms, but should be interpreted based on the substantive meaning of the terms and the overall content of this specification.
[0036] Throughout the specification, when one component is described as being "connected" to another, this includes not only cases where they are "directly connected," but also cases where they are "electrically connected" with other components in between. Furthermore, when a component is described as "containing" a particular component, this means, unless otherwise stated, that it may contain other components rather than excluding them. In addition, limitations such as "greater than or equal to" or "less than or equal to" a specific threshold may be appropriately replaced by "greater than" or "less than" depending on the embodiment.
[0037] In the present invention, the terms "field" and "subfield" may be used interchangeably.
[0038] Figure 1 shows a wireless LAN system according to one embodiment of the present invention.
[0039] A wireless LAN system includes one or more Basic Service Sets (BSS), where a BSS represents a set of devices that have successfully synchronized and can communicate with each other. Generally, BSSs are classified into infrastructure BSSs and independent BSSs (IBSSs), and Figure 1 shows an infrastructure BSS.
[0040] As shown in Figure 1, the infrastructure BSS BSS1, BSS2 includes one or more stations STA1, STA2, STA3, STA4, STA5, access points AP-1, AP-2 which are stations that provide distribution services, and a distribution system DS that connects multiple access points AP-1, AP-2.
[0041] A Station (STA) is any device that includes Medium Access Control (MAC) and a Physical Layer interface to a wireless medium in accordance with the IEEE 802.11 standard, and in a broad sense includes not only non-AP stations but also all access point (AP) stations. In this specification, "terminal" is used to refer to non-AP, AP, or both. A station for wireless communication includes a processor and a communication unit, and depending on the embodiment, further includes a user interface unit and a display unit, etc. The processor generates frames to be transmitted over the wireless network or processes frames received over the wireless network, and performs various other processing for controlling the station. The communication unit is functionally connected to the processor and sends and receives frames over the wireless network for the station. In this invention, "terminal" is used as a term that includes user equipment (UE).
[0042] An Access Point (AP) is an individual device that provides connectivity to a distribution system (DS) via a wireless medium for stations associated with it. In infrastructure BSS, communication between non-AP stations is generally conducted via APs, however, direct communication is possible between non-AP stations if a direct link is configured. In this invention, AP is used as a concept that includes PCP (Personal BSS Coordination Point), but in a broader sense, it includes all concepts such as central controllers, base stations (BS), node B, BTS (Base Transceiver System), or site controllers. In this invention, AP is also referred to as a base wireless communication terminal, but in a broader sense, base wireless communication terminal is used as a term that includes APs, base stations, eNBs (eNodeBs), and transmission points (TPs). Furthermore, base wireless communication terminals include various forms of wireless communication terminals that allocate and schedule communication medium resources in communication with multiple wireless communication terminals.
[0043] Multiple infrastructure BSSs are connected to each other via a distribution system DS. In this case, multiple BSSs connected via the distribution system are called an Extended Service Set (ESS).
[0044] Figure 2 shows an independent BSS, which is a wireless LAN system according to another embodiment of the present invention. In the embodiment of Figure 2, redundant explanations are omitted for parts that are the same as or corresponding to the embodiment of Figure 1.
[0045] As shown in Figure 2, BSS3 is an independent BSS and does not include APs, so all stations (STA6, STA7) are not connected to APs. An independent BSS is not allowed to connect to a distribution system and forms a self-contained network. In an independent BSS, each station (STA6, STA7) is directly connected to one another.
[0046] Figure 3 is a block diagram showing the configuration of a station 100 according to one embodiment of the present invention. As shown, the station 100 according to the embodiment of the present invention includes a processor 110, a communication unit 120, a user interface unit 140, a display unit 150, and a memory 160.
[0047] First, the communication unit 120 transmits and receives wireless signals such as wireless LAN packets and may be incorporated into or externally mounted to the station 100. According to one embodiment, the communication unit 120 may include at least one communication module that uses different frequency bands. For example, the communication unit 120 may include communication modules for different frequency bands such as 2.4GHz, 5GHz, 6GHz, and 60GHz. According to one embodiment, the station 100 may include a communication module that uses a frequency band of 7.125GHz or higher and a communication module that uses a frequency band of 7.125GHz or lower. Each communication module can wirelessly communicate with an AP or external station based on the wireless LAN standard of the frequency band supported by the communication module. Depending on the performance and requirements of the station 100, the communication unit 120 may operate only one communication module at a time or operate multiple communication modules together simultaneously. When the station 100 includes multiple communication modules, each communication module may be provided in an independent form, or the multiple modules may be integrated as a single chip. In embodiments of the present invention, the communication unit 120 can represent an RF (Radio Frequency) communication module that processes RF signals.
[0048] Next, the user interface 140 includes various forms of input / output means provided in the station 100. In other words, the user interface unit 140 receives user input using various input means, and the processor 110 controls the station 100 based on the received user input. The user interface unit 140 also outputs based on instructions from the processor 110 using various output means.
[0049] Next, the display unit 150 outputs an image to the display screen. The display unit 150 outputs various display objects, such as content generated by the processor 110 or user interfaces based on control instructions from the processor 110. The memory 160 stores control programs used by the station 100 and various data associated with them. Such control programs include connection programs necessary for the station 100 to connect with APs or external stations.
[0050] The processor 110 of the present invention executes various instructions or programs and processes data within the station 100. The processor 110 also controls each unit of the station 100 and controls the transmission and reception of data between units. In an embodiment of the present invention, the processor 110 executes a program for connection with the AP stored in the memory 160 and receives a communication setup message transmitted by the AP. The processor 110 also reads information regarding the priority conditions of the station 100 contained in the communication setup message and requests a connection to the AP based on the priority conditions of the station 100. The processor 110 of the present invention may refer to the main control unit of the station 100, or, depending on the embodiment, may refer to a control unit for individually controlling a part of the station 100's configuration, such as the communication unit 120. In other words, the processor 110 may be a modem or a modulator and / or demodulator that modulates and demodulates the wireless signals transmitted and received from the communication unit 120. The processor 110 controls various operations of wireless signal transmission and reception of the station 100 according to an embodiment of the present invention. A detailed embodiment of this will be described later.
[0051] The station 100 shown in Figure 3 is a block diagram according to one embodiment of the present invention, and the separately shown blocks represent logically distinguished elements of the device. Therefore, the above-described elements of the device are mounted on one chip or multiple chips depending on the device design. For example, the processor 110 and the communication unit 120 may be integrated and implemented on a single chip, or they may be implemented on separate chips. Furthermore, in the embodiment of the present invention, some components of the station 100, such as the user interface unit 140 and the display unit 150, may be selectively provided in the station 100.
[0052] Figure 4 is a block diagram showing the configuration of AP200 according to one embodiment of the present invention. As shown, AP200 according to an embodiment of the present invention includes a processor 210, a communication unit 220, and a memory 260. In Figure 4, redundant explanations are omitted for parts of the AP200 configuration that are the same as or correspond to the configuration of station 100 in Figure 3.
[0053] Referring to Figure 4, the AP 200 according to the present invention includes a communication unit 220 for operating a BSS in at least one frequency band. As described above in the embodiment of Figure 3, the communication unit 220 of the AP 200 may also include a plurality of communication modules using different frequency bands. That is, the AP 200 according to an embodiment of the present invention may include two or more communication modules using different frequency bands, for example, 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz. Preferably, the AP 200 may include a communication module using a frequency band of 7.125 GHz or higher and a communication module using a frequency band of 7.125 GHz or lower. Each communication module can communicate wirelessly with the station based on the wireless LAN standard of the frequency band supported by the communication module. Depending on the performance and requirements of the AP 200, the communication unit 220 may operate only one communication module at a time or operate multiple communication modules together simultaneously. In an embodiment of the present invention, the communication unit 220 may represent an RF (Radio Frequency) communication module that processes RF signals.
[0054] Next, the memory 260 stores the control program used by the AP200 and various data associated with it. Such a control program includes a connection program that manages the connection of stations. The processor 210 controls each unit of the AP200 and controls the transmission and reception of data between units. In one embodiment of the present invention, the processor 210 executes the program for connecting with stations stored in the memory 260 and sends a communication setting message to one or more stations. In this case, the communication setting message includes information regarding the connection priority conditions of each station. The processor 210 also sets up the connection in response to the connection request from the station. In one embodiment, the processor 210 is a modem or modulation / demodulation unit that modulates and demodulates the wireless signals transmitted and received from the communication unit 220. The processor 210 controls various operations of wireless signal transmission and reception of the AP200 according to the embodiment of the present invention. A detailed embodiment relating thereto will be described later.
[0055] Figure 5 is a schematic diagram illustrating the process by which STA establishes a link with AP.
[0056] Referring to Figure 5, the link between STA100 and AP200 is established through three main steps: scanning, authentication, and association. First, the scanning step is the step in which STA100 obtains connection information for the BSS operated by AP200. There are two methods for performing scanning: passive scanning, which obtains information using only the beacon message S101 that AP200 periodically transmits, and active scanning, in which STA100 sends a probe request to AP S103, receives a probe response from AP S105, and obtains connection information.
[0057] In the scanning step, if STA100 successfully receives wireless connection information, it sends an authentication request (S107a), receives an authentication response from AP200 (S107b), and performs the authentication step. After the authentication step is performed, STA100 sends an association request (S109a), receives an association response from AP200 (S109b), and performs the association step. In this specification, "association" basically means wireless coupling, but the present invention is not limited to this, and in a broad sense, coupling includes all wireless and wired couplings.
[0058] Meanwhile, an additional 802.1X-based authentication step S111 and an IP address acquisition step S113 via DHCP are performed. In Figure 5, Server 300 is a server that processes authentication between STA100 and the 802.1X-based system, and may be physically connected to AP200 or exist as a separate server.
[0059] Figure 6 shows the CSMA (Carrier Sense Multiple Access) / CA (Collision Avoidance) method used in wireless LAN communication.
[0060] A terminal performing wireless LAN communication checks whether a channel is busy or not by performing carrier sensing before transmitting data. If a wireless signal above a certain strength is detected, the channel is determined to be busy, and the terminal delays access to that channel. This process is called Clear Channel Assessment (CCA), and the level at which the detection of the signal is determined is called the CCA threshold. If a wireless signal above the CCA threshold is received by the terminal and the terminal is the recipient, the terminal processes the received wireless signal. On the other hand, if no wireless signal is detected from the channel, or if a wireless signal below the CCA threshold is detected, the channel is determined to be idle.
[0061] If a channel is determined to be idle, each terminal with data to transmit performs a backoff procedure after a time period determined by the status of each terminal, such as an IFS (Inter Frame Space), AIFS (Arbitration IFS), PIFS (PCF IFS), etc. In this embodiment, the AIFS is used as a replacement for the conventional DIFS (DCF IFS). Each terminal waits, decreasing a slot time equal to a random number determined for that terminal during the interval of idle state of the channel, and the terminal that has exhausted all of its slot time attempts to access the channel. The period in which each terminal performs this backoff procedure is called the competition window period. At this time, the random number can be called the backoff counter. That is, the initial value of the backoff counter is set by an integer, which is a random number acquired by the terminal. If a terminal senses that the channel is idle during the slot time, the terminal can decrease the backoff counter by 1. Also, when the backoff counter reaches 0, the terminal may be allowed to access the channel. Therefore, terminal transmission may be permitted when the channel is idle during the AIFS time and the backoff counter slot time.
[0062] If a specific terminal successfully accesses the channel, it transmits data through the channel. However, if the terminal attempting access collides with another terminal, the colliding terminals are each assigned a new random number and perform a further backoff procedure. In one embodiment, the random number newly assigned to each terminal is determined within a range twice the range (competition window, CW) of the random number previously assigned to that terminal (2*CW). Meanwhile, each terminal attempts access again in the next competition window interval by performing a further backoff procedure, but this time, each terminal performs the backoff procedure from the slot time remaining in the previous competition window interval. In this way, each terminal performing wireless LAN communication can avoid collisions with each other for a specific channel.
[0063] <Examples of various PPDU formats>
[0064] Figure 7 shows examples of various standard generational PPDU (PLCP Protocol Data Unit) formats. More specifically, Figure 7(a) shows an example of a legacy PPDU format based on 802.11a / g, Figure 7(b) shows an example of an HE PPDU format based on 802.11ax, and Figure 7(c) shows an example of a non-legacy PPDU (i.e., EHT PPDU) format based on 802.11be. Figure 7(d) shows the detailed field configuration of L-SIG and RL-SIG commonly used in the aforementioned PPDU formats.
[0065] Referring to Figure 7(a), the legacy PPDU preamble includes L-STF (Legacy Short Training field), L-LTF (Legacy Long Training field), and L-SIG (Legacy Signal field). In embodiments of the present invention, the L-STF, L-LTF, and L-SIG can be referred to as the legacy preamble.
[0066] Referring to Figure 7(b), the HE PPDU preamble further includes RL-SIG (Repeated Legacy Short Training field), HE-SIG-A (High Efficiency Signal A field), HE-SIG-B (High Efficiency Signal B field), HE-STF (High Efficiency Short Training field), and HE-LTF (High Efficiency Long Training field) in addition to the legacy preamble. In embodiments of the present invention, RL-SIG, HE-SIG-A, HE-SIG-B, HE-STF, and HE-LTF can be referred to as the HE preamble. The specific configuration of the HE preamble may be modified according to the HE PPDU format. For example, HE-SIG-B may be used only in the HE MU PPDU format.
[0067] Referring to Figure 7(c), the EHT PPDU preamble further includes RL-SIG (Repeated Legacy Short Training field), U-SIG (Universal Signal field), EHT-SIG-A (Extremely High Throughput Signal A field), EHT-SIG-A (Extremely High Throughput Signal B field), EHT-STF (Extremely High Throughput Short Training field), and EHT-LTF (Extremely High Throughput Long Training field) in addition to the legacy preamble. In embodiments of the present invention, RL-SIG, EHT-SIG-A, EHT-SIG-B, EHT-STF, and EHT-LTF can be referred to as the EHT preamble. The specific configuration of the non-legacy preamble may be modified according to the EHT PPDU format. For example, EHT-SIG-A and EHT-SIG-B may be used in only some of the EHT PPDU formats.
[0068] The L-SIG field included in the PPDU preamble is configured with 64 FFT OFDM and consists of a total of 64 subcarriers. Of these, 48 subcarriers, excluding the guard subcarrier, DC subcarrier, and pilot subcarrier, are used for L-SIG data transmission. Since BPSK and Rate=1 / 2 MCS (Modulation and Coding Scheme) are applied to L-SIG, it may contain a total of 24 bits of information. Figure 7(d) shows the 24-bit information structure of L-SIG.
[0069] Referring to Figure 7(d), L-SIG includes the L_RATE field and the L_LENGTH field. The L_RATE field consists of 4 bits and indicates the MCS used for data transmission. Specifically, the L_RATE field indicates one of the transmission speeds of 6 / 9 / 12 / 18 / 24 / 36 / 48 / 54 Mbps, which is a combination of a modulation scheme such as BPSK / QPSK / 16-QAM / 64-QAM and a code rate such as 1 / 2, 2 / 3, or 3 / 4. Combining the information from the L_RATE and L_LENGTH fields allows us to determine the total length of the PPDU. In the non-legacy PPDU format, the L_RATE field is set to the minimum speed of 6 Mbps.
[0070] The L_LENGTH field is measured in bytes, with a total of 12 bits allocated, allowing for signaling up to 4095. In combination with the L_RATE field, it can indicate the length of the PPDU. In this case, legacy and non-legacy terminals can parse the L_LENGTH field in different ways.
[0071] First, the method by which a legacy or non-legacy terminal analyzes the length of a PPDU using the L_LENGTH field is as follows: When the L_RATE field is set to 6Mbps, 3 bytes (i.e., 24 bits) may be transmitted in 4us, which is the symbol duration of one 64FFT. Therefore, by adding the 3 bytes corresponding to the SVC field and the Tail field to the L_LENGTH field value and dividing this by the transmission amount of one symbol, which is 3 bytes, the number of 64FFT reference symbols after L-SIG is obtained. After multiplying the obtained number of symbols by the symbol duration of one, which is 4us, and then adding the 20us required for transmission of L-STF, L-LTF, and L-SIG, the length of the PPDU, i.e., the reception time (RXTIME), is obtained. This can be expressed mathematically as shown in Equation 1 below.
[0072]
number
[0073] At this time,
number
[0074]
number
[0075] Here, TXTIME is the total transmission time that constitutes the PPDU, as shown in Equation 3 below. In this case, TX represents the transmission time of X.
[0076]
number
[0077] Referring to the above formula, the length of the PPDU is calculated based on the rounded-up value of L_LENGTH / 3. Therefore, for any value of k, three different values L_LENGTH = {3k+1, 3k+2, 3(k+1)} indicate the same PPDU length.
[0078] Referring to Figure 7(e), the U-SIG (Universal SIG) field persists in EHT PPDUs and subsequent generations of wireless LAN PPDUs, playing a role in distinguishing which generation of PPDU it is, including 11be. The U-SIG is a 64FFT-based OFDM with two symbols, capable of transmitting a total of 52 bits of information. Of these, 43 bits, excluding the 9 bits of CRC / tail, are broadly divided into the VI (Version Independent) field and the VD (Version Dependent) field.
[0079] The VI bit maintains its current bit configuration, allowing current 11be terminals to obtain information about a PPDU from its VI field even when subsequent generations of PPDUs are defined. To this end, the VI field consists of the PHY version, UL / DL, BSS color, TXOP, and Reserved fields. The PHY version field is 3 bits and is responsible for sequentially distinguishing 11be and subsequent generations of wireless LAN standards by version. 11be has a value of 000b. The UL / DL field distinguishes whether the PPDU is an uplink or downlink PPDU. The BSS color represents the BSS identifier defined in 11ax and has a value of 6 bits or more. The TXOP represents the Transmit Opportunity Duration, which was transmitted in the MAC header, but by adding it to the PHY header, the length of the TXOP containing the PPDU can be inferred without decoding the PPDU, and it has a value of 7 bits or more.
[0080] The VD field may consist of the PPDU format as signaling information useful only for the 11be version of PPDU, fields that are common to any PPDU format such as BW, and fields that are defined differently depending on the PPDU format. The PPDU format is a divisor that distinguishes between EHT SU (Single User), EHT MU (Multiple User), EHT TB (Trigger-based), EHT ER (Extended Range) PPDU, etc. The BW field broadly signals five basic PPDU BW options of 20, 40, 80, 160 (80+80), and 320 (160+160) MHz (BW that can be expressed in the form of a power of 20*2 can be called a basic BW), and various remaining PPDU BWs composed of preamble puncturing. In addition, after being signaled at 320 MHz, some 80 MHz may be punctured and then signaled. Furthermore, the punctured and deformed channel shape may be signaled directly in the BW field, or it may be signaled using both the BW field and fields appearing after the BW field (for example, fields within the EHT-SIG field). If the BW field is 3 bits, a total of 8 BW signalings are possible, so a maximum of 3 puncturing modes can be signaled. If the BW field is 4 bits, a total of 16 BW signalings are possible, so a maximum of 11 puncturing modes can be signaled.
[0081] Fields located after the BW field vary depending on the form and format of the PPDU. MU PPDUs and SU PPDUs may be signaled in the same PPDU format. A field to distinguish between MU PPDUs and SU PPDUs may be located before the EHT-SIG field, and additional signaling may be performed for this purpose. Both SU PPDUs and MU PPDUs include an EHT-SIG field, but some fields unnecessary for the SU PPDU may be compressed. In this case, the information of the compressed fields may be omitted or have a reduced size compared to the original fields included in the MU PPDU. For example, in the case of a SU PPDU, the common fields of the EHT-SIG may be omitted or replaced, or user-specific fields may be replaced or reduced to one, resulting in a different configuration.
[0082] Alternatively, the SU PPDU may further include a compression field indicating whether or not it is compressed, and depending on the value of the compression field, some fields (e.g., the RA field) may be omitted.
[0083] If a portion of the EHT-SIG field of an SU PPDU is compressed, the information contained in the compressed field may be signaled together with the uncompressed field (e.g., a common field). In the case of an MU PPDU, since it is a PPDU format for simultaneous reception by multiple users, the EHT-SIG field must be transmitted after the U-SIG field, and the amount of information signaled may be variable. That is, since multiple MU PPDUs are transmitted to multiple STAs, each STA must know the location of the RU to which the MU PPDU is transmitted, the STA to which each RU is assigned, and whether or not the transmitted MU PPDU was sent to them. Therefore, the AP must transmit the EHT-SIG field with the above information included. To this end, the U-SIG field signals information for efficiently transmitting the EHT-SIG field, which may be the number of symbols and / or the modulation method (MCS) of the EHT-SIG field. The EHT-SIG field may include size and location information of the RU assigned to each user.
[0084] In the case of an SU PPDU, multiple RUs may be assigned to the STA, and these RUs may be consecutive or discontinuous. When the RUs assigned to the STA are not consecutive, the STA can efficiently receive the SU PPDU only if it recognizes the punctured RU in the middle. Therefore, the AP can transmit the SU PPDU including information about the punctured RUs among the RUs assigned to the STA (e.g., the puncturing pattern of the RUs). That is, in the case of an SU PPDU, the EHT-SIG field may contain a puncturing mode field that includes information on whether a puncturing mode was applied and the puncturing pattern shown in bitmap format or similar, and the puncturing mode field can signal the form of discontinuous channels appearing within the bandwidth.
[0085] The form of the signaled discontinuous channels is limited and, in combination with the value of the BW field, indicates the BW and discontinuous channel information of the SU PPDU. For example, in the case of an SU PPDU, since it is a PPDU transmitted to only one terminal, the STA can recognize the bandwidth allocated to it from the BW field included in the PPDU, and can recognize the punctured resources within the allocated bandwidth from the puncturing mode field of the U-SIG field or EHT-SIG field included in the PPDU. In this case, the terminal can receive the PPDU on the remaining resource units other than the specific channel of the punctured resource unit. At this time, the multiple RUs allocated to the STA may consist of different frequency bands or tones.
[0086] The reason only restricted forms of discontinuous channel configurations are signaled is to reduce the signaling overhead of the SU PPDU. Since puncturing can be performed on each 20MHz subchannel, when puncturing is performed on a bandwidth with multiple 20MHz subchannels, such as 80, 160, and 320MHz, in the case of 320MHz, the usage status of the remaining 15 20MHz subchannels other than the primary channel must be represented, and the discontinuous channel configuration (if a configuration where only the end 20MHz is punctured is also considered discontinuous) must be signaled. Using 15 bits to signal discontinuous channel configurations for single-user transmissions in this way can result in excessive signaling overhead when considering the low transmission speed of the signaling portion.
[0087] This invention proposes a method for signaling the discontinuous channel configuration of an SU PPDU and illustrates the discontinuous channel configuration determined by the proposed method. Furthermore, it proposes a method for signaling the primary 160MHz and secondary 160MHz puncturing configurations of an SU PPDU in a 320MHz BW configuration.
[0088] Furthermore, in one embodiment of the present invention, a method is proposed in which the configuration of the PPDU indicated by the preamble puncturing BW value differs depending on the signaled PPDU format in the PPDU format field. Assuming that the BW field is 4 bits, in the case of an EHT SU PPDU or TB PPDU, one symbol of EHT-SIG-A is further signaled after U-SIG, or it is not necessary to signal EHT-SIG-A from the beginning. Taking this into consideration, it is necessary to fully signal up to 11 puncturing modes using only the BW field of U-SIG. However, in the case of an EHT MU PPDU, EHT-SIG-B is further signaled after U-SIG, so up to 11 puncturing modes can be signaled in a different way than in an SU PPDU. In the case of an EHT ER PPDU, the BW field can be set to 1 bit to signal whether the PPDU uses a 20MHz or 10MHz bandwidth. Detailed puncturing patterns for each PPDU type will be described in detail in Figures 11 and 12.
[0089] Figure 7(f) shows the format-specific fields of the VD field when EHT MU PPDU is indicated in the U-SIG PPDU format field. In the case of MU PPDU, SIG-B, which is a signaling field for simultaneous reception by multiple users, is required, and SIG-B may be transmitted after U-SIG without a separate SIG-A. For this purpose, U-SIG must signal information for decoding SIG-B. Such fields include SIG-B MCS, SIG-B DCM, Number of SIG-B Symbols, SIG-B Compression, and Number of EHT-LTF Symbols fields.
[0090] Figure 8 shows examples of various EHT (Extremely High Throughput) PPDU (Physical Protocol Data Unit) formats and methods for specifying them according to embodiments of the present invention.
[0091] Referring to Figure 8, a PPDU may consist of a preamble and a data portion, and one type of format, EHT PPDU, may be distinguished by a U-SIG field included in the preamble. Specifically, whether or not the PPDU format is EHT PPDU may be indicated based on the PPDU format field included in the U-SIG field.
[0092] Figure 8(a) shows an example of the EHT SU PPDU format for a single STA. The EHT SU PPDU is a PPDU used for single-user (SU) transmission between an AP and a single STA, and may have an EHT-SIG-A field for additional signaling after the U-SIG field.
[0093] Figure 8(b) shows an example of an EHT trigger-based PPDU format, which is an EHT PPDU transmitted based on a trigger frame. An EHT trigger-based PPDU is an EHT PPDU transmitted based on a trigger frame and is an uplink PPDU used as a response to a trigger frame. Unlike an EHT SU PPDU, an EHT PPDU does not have an EHT-SIG-A field after the U-SIG field.
[0094] Figure 8(c) shows an example of the EHT MU PPDU format, which is an EHT PPDU for multiple users. An EHT MU PPDU is a PPDU used to send a PPDU to one or more STAs. In the EHT MU PPDU format, the HE-SIG-B field may be located after the U-SIG field.
[0095] Figure 8(d) shows an example of the EHT ER SU PPDU format used for single-user transmissions with STAs in an extended range. EHT ER SU PPDU may be used for single-user transmissions with STAs in a wider range than EHT SU PPDU described in Figure 8(a), and the U-SIG field may be repeatedly positioned on the time axis.
[0096] The EHT MU PPDU described in Figure 8(c) can be used by an AP to transmit downlink data to multiple STAs. In this case, the EHT MU PPDU may include scheduling information so that multiple STAs can simultaneously receive PPDUs transmitted from the AP. The EHT MU PPDU can transmit the AID information of the recipient and / or sender of the PPDU transmitted through the user-specific field of EHT-SIG-B to the STAs. Therefore, multiple terminals that receive the EHT MU PPDU can perform spatial reuse operations based on the AID information in the user-specific field included in the preamble of the received PPDU.
[0097] Specifically, the resource unit allocation (RA) field in the HE-SIG-B field included in the HE MU PPDU may contain information about the configuration of the resource units (e.g., the division of the resource units) within a specific bandwidth on the frequency axis (e.g., 20 MHz). That is, the RA field can instruct the STA on the configuration of the resource units divided by the bandwidth for transmitting the HE MU PPDU in order to receive the PPDU. Information about the STA allocated (or specified) to each divided resource unit may be included in the user-specific field of EHT-SIG-B and transmitted to the STA. That is, the user-specific field may contain one or more user fields corresponding to each divided resource unit.
[0098] For example, among the multiple divided resource units, the user field corresponding to at least one resource unit used for data transmission may contain the recipient's or sender's AID, while the user fields corresponding to the remaining resource units not used for data transmission may contain a previously set Null STA ID.
[0099] For the sake of clarity, the terms frame or MAC frame may be used interchangeably with MPDU in this specification.
[0100] When a single wireless communication device communicates using multiple links, the communication efficiency of the wireless communication device can be increased. In this case, a link is a physical path and may be configured as a single wireless medium that can be used to transmit an MSDU (MAC service data unit). For example, if the frequency band of one link is being used by another wireless communication device, the wireless communication device can continue to communicate using another link. In this way, the wireless communication device can make effective use of multiple channels. Furthermore, when the wireless communication device communicates simultaneously using multiple links, the overall throughput can be increased. However, existing wireless LANs are defined on the premise that one wireless communication device uses one link. Therefore, a wireless LAN operation method for using multiple links is necessary. Referring to Figures 9 to 26, the wireless communication method for a wireless communication device using multiple links will be explained. First, Figure 9 will be used to explain a specific form of a wireless communication device using multiple links.
[0101] Figure 9 shows a multi-link device according to an embodiment of the present invention.
[0102] A multi-link device (MLD) may be defined for the wireless communication method using the multiple links described above. A multi-link device can represent a device having one or more affiliated stations. In specific embodiments, a multi-link device can represent a device having two or more affiliated stations. A multi-link device can also have interchangeable multi-link elements. A multi-link element contains information about one or more stations or one or more links. A multi-link element may include the multi-link setup element described later. In this case, the multi-link device may be a logical entity. Specifically, a multi-link device may have multiple affiliated stations. A multi-link device can be called an MLLE (multi-link logical entity) or an MLE (multi-link entity). A multi-link device may have one medium access control service access point (SAP) up to logical link control (LLC). An MLD may also have one MAC data service.
[0103] Multiple stations included in a multilink system can operate on multiple links. Furthermore, multiple stations included in a multilink system can operate on multiple channels. Specifically, multiple stations included in a multilink system can operate on different links or different channels. For example, multiple stations included in a multilink system can operate on different channels of 2.4GHz, 5GHz, and 6GHz.
[0104] The operation of a multilink device can be called multilink operation, MLD operation, or multi-band operation. Furthermore, if the station paired with the multilink device is an AP (Application Platform), the multilink device can be called an AP MLD (Application Platform Multilink). Conversely, if the station paired with the multilink device is a non-AP station, the multilink device can be called a non-AP MLD (Application Platform Multilink).
[0105] Figure 9 illustrates the communication operation between a non-AP MLD and an AP-MLD. Specifically, the non-AP MLD and AP-MLD communicate using three links each. The AP MLD includes the first AP (AP1), the second AP (AP2), and the third AP (AP3). The non-AP MLD includes the first non-AP STA (non-AP STA1), the second non-AP STA (non-AP STA2), and the third non-AP STA (non-AP STA3). The first AP (AP1) and the first non-AP STA (non-AP STA1) communicate via the first link (Link1). The second AP (AP2) and the second non-AP STA (non-AP STA2) communicate via the second link (Link2). The third AP (AP3) and the third non-AP STA (non-AP STA3) communicate via the third link (Link3).
[0106] Multilink operation may include a multilink setup operation. Multilink setup corresponds to the association operation of the single-link operation described above and must be performed before frame exchange in multilink. A multilink device can obtain the information necessary for multilink setup from a multilink setup element. Specifically, the multilink setup element may include capability information related to multilink. In this case, the capability information may include information indicating whether one of the multiple devices included in the multilink device can transmit and the other devices can receive simultaneously. The capability information may also include information about the links available to each station included in the MLD. Furthermore, the capability information may include information about the channels available to each station included in the MLD.
[0107] Multilink configuration may be established through negotiations between peer stations. Specifically, multilink configuration may be performed through communication between stations without communication with the AP. Furthermore, multilink configuration may be established through any one of the links. For example, even if links 1 through 3 are configured via a multilink, the multilink configuration may be performed through link 1.
[0108] Furthermore, a mapping between TIDs (traffic identifiers) and links may be configured. Specifically, frames corresponding to a specific TID value may be exchanged only through pre-specified links. The mapping between TIDs and links may be configured in a directional-based manner. For example, if multiple links are configured between a first multilink device and a second multilink device, the first multilink device may be configured to send frames with a first TID to multiple first links, and the second multilink device may be configured to send frames with a second TID to the first links. Additionally, a default setting may exist for the mapping between TIDs and links. Specifically, if there are no additional settings in the multilink configuration, the multilink device can exchange frames corresponding to TIDs on each link according to the default setting. In this case, the default setting may be such that all TIDs are exchanged on any one link.
[0109] Let's explain TID in detail. TID is an ID used to classify traffic and data to support QoS (Quality of Service). TID may be used and assigned at layers higher than the MAC layer. TID can also indicate traffic category (TC) and traffic stream (TS). There may be 16 distinct TID values. For example, a TID may be specified as any one of 0 to 15. Different TID values may be specified depending on the access policy, channel access, or medium access method. For example, when EDCA (enhanced distributed channel access) or HCAF (hybrid coordination function contention based channel access) is used, the TID value may be assigned in the range of 0 to 7. When EDCA is used, TID can indicate user priority (UP). In this case, UP may be specified by TC or TS. UP may be assigned at layers higher than MAC. Furthermore, when HCCA (HCF controlled channel access) or SPCA is used, the TID value may be assigned in the range of 8 to 15. When HCCA or SPCA is used, TID can represent TSID. Furthermore, when HEMM or SEMM is used, the TID value may be assigned in the range of 8 to 15. When HEMM or SEMM is used, TID can represent TSID.
[0110] UP and AC (access category) may be mapped. AC may be a label for providing QoS in EDCA. AC may be a label for indicating an EDCA parameter set. EDCA parameters or EDCA parameter sets are parameters used in EDCA channel contention. QoS stations can guarantee QoS using AC. AC may also include AC_BK, AC_BE, AC_VI, and AC_VO. AC_BK, AC_BE, AC_VI, and AC_VO can indicate background, best effort, video, and voice, respectively. AC_BK, AC_BE, AC_VI, and AC_VO may also be classified into sub-ACs. For example, AC_VI can be subdivided into AC_VI primary and AC_VI alternate. Similarly, AC_VO can be subdivided into AC_VO primary and AC_VO alternate. UP or TID may also be mapped to AC. For example, each of 1, 2, 0, 3, 4, 5, 6, and 7 in UP or TID may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI, AC_VI, AC_VO, and AC_VO, respectively. Also, each of 1, 2, 0, 3, 4, 5, 6, and 7 in UP or TID may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI alternate, AC_VI primary, AC_VO primary, and AC_VO alternate, respectively. Furthermore, the priority of 1, 2, 0, 3, 4, 5, 6, and 7 in UP or TID may be in that order from highest to lowest. That is, 1 may have a lower priority and 7 may have a higher priority. Therefore, the priority may be in the order of AC_BK, AC_BE, AC_VI, and AC_VO, from highest to lowest. Furthermore, AC_BK, AC_BE, AC_VI, and AC_VO can each correspond to ACI (AC index) 0, 1, 2, and 3, respectively. Due to these characteristics of TIDs, the mapping between TIDs and links can represent the mapping between ACs and links.Furthermore, the mapping between links and ACs can represent the mapping between TIDs and links.
[0111] As mentioned above, a TID may be mapped to each of multiple links. The mapping may specify which links can exchange traffic corresponding to a particular TID or AC. Additionally, TIDs or ACs that can be transmitted in different transmission directions within a link may be specified. As mentioned above, a default setting may exist for the mapping between TIDs and links. Specifically, in a multilink configuration where no additional settings are made, the multilink device can exchange frames corresponding to TIDs on each link according to the default setting. In this case, the default setting may be that all TIDs are exchanged on any one link. At any given time, any TID or AC may always be mapped to at least one link. Management frames and control frames may be transmitted on all links.
[0112] When a link is mapped to a TID or AC, only data frames corresponding to the TID or AC mapped to that link may be transmitted on that link. Therefore, when a link is mapped to a TID or AC, frames that do not correspond to a TID or AC not mapped to that link do not need to be transmitted on that link. When a link is mapped to a TID or AC, the ACK may also be transmitted based on the link to which the TID or AC is mapped. For example, a block ACK agreement may be determined based on the mapping between TIDs and links. Furthermore, in other specific embodiments, the mapping between TIDs and links may be determined based on a block ACK agreement. Specifically, a block ACK agreement may be set for a TID mapped to a particular link.
[0113] The aforementioned mapping of TIDs to links may ensure QoS. Specifically, a relatively small number of stations may be operational, or higher-priority ACs or TIDs may be mapped to links with good channel conditions. Furthermore, the aforementioned mapping of TIDs to links may enable stations to maintain a power-saving state for longer periods.
[0114] Figure 10 shows a multilink mapped by a TID-to-link mapping method according to an embodiment of the present invention.
[0115] Referring to Figure 10, a mapping relationship between TID and link may exist, as explained in Figure 9. In this invention, the mapping relationship between TID and link can be called TID-to-link mapping, TID to link mapping, TID mapping, link mapping, etc. TID may be a traffic identifier. TID may also be an identifier used to classify traffic, data, etc., in order to support QoS (quality of service).
[0116] Furthermore, the TID may be an ID used or assigned at a layer higher than the MAC layer. The TID can represent TC (traffic categories) or TS (traffic streams). The TID may also have 16 values, for example, values from 0 to 15. The TID value used may differ depending on the access policy or channel connection or medium access method. For example, when using EDCA (HCF (hybrid coordination function) contention-based channel connection, enhanced distributed channel connection), possible TID values may be from 0 to 7. When using EDCA, the TID value may represent UP (user priority), and the UP may relate to TC or TS. The UP may also be a value assigned at a layer higher than MAC. Furthermore, when using HCCA (HCF controlled channel access) or SPCA, possible TID values may be from 8 to 15. Furthermore, when using HCCA or SPCA, the TID may represent the TSID. Furthermore, when using HEMM or SEMM, the possible TID values may be between 8 and 15. Also, when using HEMM or SEMM, the TID may represent the TSID.
[0117] Furthermore, a mapping relationship between UP and access category (AC) may exist. AC may be a label that indicates a label or set of EDCA parameters for providing QoS in EDCA. The EDCA parameters or set of EDCA parameters may be those used for channel connection. AC may be used by QoS STA.
[0118] The value of AC may be set to one of AC_BK, AC_BE, AC_VI, or AC_VO. AC_BK, AC_BE, AC_VI, and AC_VO may represent background, best effort, video, and voice, respectively. Furthermore, AC_BK, AC_BE, AC_VI, and AC_VO can be subdivided. For example, AC_VI may be subdivided into AC_VI primary and AC_VI alternate. Similarly, AC_VO may be subdivided into AC_VO primary and AC_VO alternate. Additionally, UP values or TID values may be mapped to AC values. For example, UP values or TID values 1, 2, 0, 3, 4, 5, 6, and 7 may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI, AC_VI, AC_VO, and AC_VO, respectively. Alternatively, UP values or TID values 1, 2, 0, 3, 4, 5, 6, and 7 may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI alternate, AC_VI primary, AC_VO primary, and AC_VO alternate, respectively. Furthermore, UP values or TID values 1, 2, 0, 3, 4, 5, 6, and 7 may have increasing priority in that order. That is, 1 may have a lower priority and 7 may have a higher priority. Therefore, the priority may increase in the order of AC_BK, AC_BE, AC_VI, and AC_VO. Also, AC_BK, AC_BE, AC_VI, and AC_VO may correspond to AC indices (ACI) 0, 1, 2, and 3, respectively.
[0119] Therefore, a relationship between TID and AC can exist. Thus, the TID-to-link mapping of the present invention may also be a mapping relationship between AC and the link. Furthermore, in the present invention, the mapping of TID may also mean that AC is mapped, and vice versa.
[0120] According to one embodiment of the present invention, there may be TIDs mapped to each link in a multilink. For example, there may be a mapping for which links among multiple links are permitted to transmit and receive a particular TID or AC. Furthermore, such mappings may be defined separately for each direction of the link. Also, as mentioned above, there may be a default setting for the mapping between TIDs and links. For example, the mapping between TIDs and links may basically be such that all TIDs are mapped to a certain link. Also, according to one embodiment, at a particular time, a certain TID or AC may be mapped to at least one link. Furthermore, a management frame or control frame may be transmitted on all links.
[0121] In this invention, data frames corresponding to TIDs or ACs mapped to a given direction of a link may be transmitted. Conversely, data frames corresponding to TIDs or ACs that are not mapped to a given direction of a link do not need to be transmitted.
[0122] According to one embodiment, TID-to-link mapping may also be applied to acknowledgments. For example, a block ack agreement may be based on TID-to-link mapping. Alternatively, TID-to-link mapping may be based on a block ack agreement. For example, a block ack agreement can exist for a TID that has been TID-to-link mapped.
[0123] TID-to-link mapping makes it possible to provide QoS services. For example, by mapping high-priority ACs and TIDs to links with good channel status or few STAs, it may be possible to transmit data for those ACs and TIDs faster. Alternatively, TID-to-link mapping can help enable STAs on a specific link to power save (or enter a doze state).
[0124] Referring to Figure 10, an AP MLD containing AP1 and AP2 may exist. A Non-AP MLD containing STA1 and STA2 may also exist. Furthermore, the AP MLD may have multiple links, namely Link1 and Link2. AP1 and STA1 may be associated via Link1, and AP2 and STA2 may be associated via Link2.
[0125] Therefore, Link1 may include a link from AP1 to STA1 and / or a link from STA1 to AP1, and Link2 may include a link from AP2 to STA2 and / or a link from STA2 to AP2. In this case, each link may be mapped to a TID and / or AC.
[0126] For example, all TIDs and all ACs may be mapped to the link from AP1 to STA1 on Link1, and to the link from STA1 to AP1 on Link1. On the other hand, only TIDs corresponding to AC_VO or AC_VO may be mapped to the link from STA2 to AP2 on Link2. Furthermore, only data for mapped TIDs and / or ACs can be transmitted on that link. Data for TIDs or ACs that are not mapped to a link will not be transmitted on that link.
[0127] Figure 11 shows the power management operation performed by a station according to an embodiment of the present invention.
[0128] In an embodiment of the present invention, the station can operate in power-saving mode (PS). In this state, the station operating in power-saving mode can switch between an awake state and a doze state. In the awake state, the station operates at full power. In the awake state, the station can transmit and receive. In the doze state, the station may be restricted from transmitting and receiving. In power-saving mode, if a frame to be transmitted is buffered by the station, the station switches to the awake state; otherwise, it can operate in the power-saving state. In power-saving mode, the station can frequently switch between the awake state and the power-saving state. In active mode, the station always maintains a state where it can transmit and receive. That is, in active mode, the station can always operate in the awake state.
[0129] Thus, when a station operates in power-saving mode, it may be unable to receive signals. Therefore, the AP can signal to the station that the traffic it is sending will be buffered, and then receive a response from the station and proceed with the transmission. For convenience of explanation, the signaling by the AP to the station that the traffic it is sending will be buffered is called traffic cindication. The signaling for traffic cindication is called traffic cindication signaling. Traffic cindication between the AP and the station may be performed as follows. In this specification, traffic may include one of the following: frame, BU, MSDU, and MPDU.
[0130] When traffic to be sent to a station is buffered by an AP, the AP can send a traffic indication signaling to the station indicating that the traffic to be sent has been buffered. In this specification, the traffic indication signaling may, depending on the context, indicate that traffic has been buffered, and may not be limited to traffic for a specific station. The traffic indication signaling may include at least one of a TIM (traffic indication map) element and a multi-link traffic element. The traffic indication signaling may be in bitmap format. Specifically, the traffic indication signaling can indicate whether the traffic corresponding to each bit of the bitmap has been buffered by the AP sending the bitmap. The traffic indication signaling can also indicate the recipient of the buffered traffic. For example, the traffic indication signaling can indicate that the buffered traffic corresponds to at least one of the following: group-addressed traffic, group-cast traffic, broadcast traffic, and individually addressed traffic. The bitmap can signal which group the traffic belongs to and which station the traffic belongs to, based on the position of the bits in the bitmap. The station can determine, based on the position of the bits in the bitmap, whether the traffic belonging to the group containing the station is being buffered by the AP, or whether the traffic for the station is being buffered by the AP.
[0131] Traffic instruction signaling may be transmitted based on a predetermined time. This allows a station in a power-saving state to switch from power-saving to awake state based on the time the traffic instruction signaling is transmitted. Traffic instruction signaling may be included in a beacon frame. Traffic instruction signaling may also be included in a TIM frame. Furthermore, an AP can transmit traffic instruction signaling periodically. Specifically, an AP can transmit traffic instruction signaling based on TBTT (target beacon transmission time). However, if the channel is not idle (busy) at TBTT, the AP can transmit traffic instruction signaling at a later time than TBTT. A station can receive traffic instruction signaling while maintaining an awake state at TBTT. The beacon frame containing the traffic instruction signaling may not be transmitted precisely at TBTT. Therefore, a station can maintain an awake state for a certain period of time including the TBTT time.
[0132] In the embodiment described above, it was assumed that the AP transmits the traffic instruction signaling and the station receives it. In this case, the station may be a non-AP station. Also, the AP may be included in the AP multilink device, and the non-AP station may be included in the non-AP multilink device. Furthermore, the aforementioned traffic may represent a BU (bufferable unit) or a buffered BU.
[0133] An AP can send a DTIM (delivery TIM) before sending group address traffic or broadcast traffic. A DTIM is a type of TIM that indicates whether group address traffic and broadcast traffic have been buffered by the AP. A beacon frame containing a DTIM can be called a DTIM beacon frame. If a DTIM received by a station indicates that group traffic for a group including the station is being sent, the station can send a signaling to the AP indicating that it will receive the group traffic.
[0134] A station that receives a traffic instruction signaling can send a retrieve signaling signaling to the station. In this case, the retrieve signaling signaling to the station may be at least one of either a PS-Poll frame or a U-APSD trigger frame. An AP that receives a retrieve signaling signaling to a station sends the buffered traffic to the station.
[0135] In Figure 11, the first AP (AP1) includes a TIM in the beacon frame and transmits a beacon frame for each TBTT. The TIM transmitted by the first AP (AP1) indicates that traffic for the first station (STA1) should be buffered. The first station (STA1) transmits a PS-Poll frame and maintains an awake state to receive traffic. The first AP (AP1) transmits the buffered traffic (Data to STA1) to the first station (STA1). The first station (STA1) receives the buffered traffic and can enter a power-saving state. The first station (STA1) can also maintain an awake state when transmitting the next TIM.
[0136] Furthermore, in Figure 11, the first AP (AP1) transmits a DTIM every three beacon frames. Therefore, the DTIM interval is three beacon frames. At this time, the first station (STA1), operating in power-saving mode, maintains an awake state each time a DTIM is transmitted. After transmitting the DTIM beacon, the first AP (AP1) transmits broadcast traffic or group address traffic. When the DTIM indicates that the broadcast traffic or group address traffic to be received by the first station (STA1) should be buffered, the first station (STA1) maintains an awake state to receive the broadcast traffic or group address traffic. This allows the first station (STA1) to stably receive broadcast traffic or group address traffic even in power-saving mode. Figure 12 illustrates the format of TIM elements that may be included in traffic instruction signaling.
[0137] Figure 12 shows the format of a TIM element according to an embodiment of the present invention.
[0138] A TIM element includes the TIM described above. A TIM element may include at least one of the following: Element ID subfield, Length subfield, DTIM Count subfield, DTIM Period subfield, Bitmap Control subfield, and Partial Virtual Bitmap subfield. The length of the Element ID subfield, Length subfield, DTIM Count subfield, DTIM Period subfield, and Bitmap Control subfield is 1 octet, i.e., 8 bits. The Partial Virtual Bitmap subfield may have a variable length, up to 251 octets. The length of the Partial Virtual Bitmap subfield may be determined by the Bitmap Control field or the Bitmap Offset subfield of the Bitmap Control field.
[0139] The Element ID subfield indicates the ID of the element that contains the Element ID subfield.
[0140] The Length subfield indicates the length of the element containing the Length subfield. Specifically, the Length subfield can indicate the length of an element excluding the Element ID subfield and the Length subfield.
[0141] The DTIM Count subfield indicates how many beacon frames will be sent until the next DTIM. Specifically, the value of the DTIM Count subfield can indicate how many beacon frames will be sent until the next DTIM, including the beacon frame containing the DTIM Count subfield. For example, a value of 0 for the DTIM Count subfield can indicate that the DTIM Count subfield is included in the DTIM beacon.
[0142] The DTIM Period subfield indicates the number of beacon frames sent between DTIMs. The value of the DTIM Period subfield is set to 1 when all TIMs are DTIMs.
[0143] The Bitmap Control subfield may include a Traffic Indicator subfield and a Bitmap Offset subfield. The Traffic Indicator subfield may be a 1-bit field, and the Bitmap Offset subfield may be a 7-bit field. The Traffic Indicator subfield can indicate whether group address traffic is buffered. Specifically, if group address traffic is buffered, the AP can set the value of the Traffic Indicator subfield to 1. Group address traffic may be traffic with a recipient AID of 0. The Bitmap Offset subfield indicates the starting point of the bits corresponding to the Partial Virtual Bitmap in the Traffic indication virtual bitmap. The AID (association ID) corresponding to the Partial Virtual Bitmap is determined by the Bitmap Offset subfield.
[0144] Each bit in the Partial Virtual Bitmap field indicates whether the traffic destined for the station corresponding to the AID is buffered by the AP sending the TIM. A value of 1 in the Partial Virtual Bitmap field indicates that the traffic destined for the station corresponding to the AID is buffered by the AP sending the TIM. A value of 0 in the Partial Virtual Bitmap field indicates that the traffic destined for the station corresponding to the AID is not buffered by the AP sending the TIM. Therefore, if the value of a bit in the Partial Virtual Bitmap field is 1, the station receiving the TIM can determine that the traffic destined for the station corresponding to the AID is buffered by the AP sending the TIM. If the value of a bit in the Partial Virtual Bitmap field is 0, the station receiving the TIM can determine that the traffic destined for the station corresponding to the AID is not buffered by the AP sending the TIM. Furthermore, a station that receives a TIM can determine that traffic destined for a station with an AID not indicated by the Partial Virtual Bitmap is not being buffered by the AP that sent the TIM.
[0145] A TIM element may include a Traffic indication virtual bitmap subfield. In this case, the bit number of the Traffic indication virtual bitmap subfield can indicate the AID of the station corresponding to the bit. Specifically, a bit with bit number n in the Traffic indication virtual bitmap subfield indicates that a frame destined for a station with AID n is buffered by the AP sending the TIM element. Specifically, when the bit number of the Traffic indication virtual bitmap subfield is N, that bit can indicate whether traffic destined for a station with AID N or a group with Group ID N is buffered by the AP sending the TIM. A TIM may include a Partial Virtual Bitmap subfield instead of a Traffic indication virtual bitmap subfield. A Partial Virtual Bitmap subfield is obtained by omitting consecutive bits that are valued as 0 in the Traffic indication virtual bitmap subfield. A Partial Virtual Bitmap subfield may be obtained by omitting the first consecutive bit of a set of consecutive bits that are valued as 0 in the Traffic indication virtual bitmap subfield, or by omitting the last consecutive bit. Specifically, the Partial Virtual Bitmap subfield may be the bits from octet number N1 to N2 of the Traffic indication virtual bitmap subfield. N1 may be the largest even number in the Traffic indication virtual bitmap subfield where bit numbers 1 to (N1*8-1) are all 0.N2 may be the smallest number in the Traffic indication virtual bitmap subfield where all bit numbers from (N2+1)*8 to 2007 are 0. This may be a method of configuring the Partial Virtual Bitmap subfield when multiple BSSID sets are not supported, i.e., when dot11MultiBSSIDImplemented is false. In this specification, the bit number n of a bitmap or subfield represents the (n+1)th bit of the bitmap or subfield.
[0146] In the Traffic indication virtual bitmap subfield, if all bits except the bit number 0 are valued at 0, the Partial Virtual Bitmap subfield may have a length of 1 octet, and all bits in the Partial Virtual Bitmap subfield may be set to 0. In this case, the value of the Bitmap Offset field may be 0, and the value of the Length field may be set to 4.
[0147] Furthermore, when all bits in the Traffic indication virtual bitmap subfield are 0 and all bits in the Bitmap Control subfield are 0, the TIM element does not need to include a Partial Virtual Bitmap field or a Bitmap Control field. In this case, the value of the Length field may be set to 2. Thus, a TIM may have a Bitmap Control field when a Partial Virtual Bitmap field exists.
[0148] When a multiple BSSID set is supported, i.e., when dot11MultiBSSIDImplemented is True, the method for configuring the Partial Virtual Bitmap subfield may be as described in the following embodiment. When a multiple BSSID set is used, the management frame transmitted from the AP corresponding to the transmitted BSSID may include information for the BSS corresponding to the nontransmitted BSSID. In this case, the management frame may include at least one of a beacon frame or a probe response frame. The TIM element of the beacon frame transmitted from the transmitted BSSID can indicate whether the AP corresponding to the nontransmitted BSSID included in the multiple BSSID set containing the transmitted BSSID should buffer the frame. The method for configuring the Partial Virtual Bitmap subfield with this in mind will be described below.
[0149] If n is the maximum number of BSSIDs that a multiple BSSID set can have, then the bits from bitmap number 1 to bitmap number (2^n-1) in the Traffic indication virtual bitmap subfield can indicate whether a group address frame has been buffered by the AP that transmits the TIM element. In this case, the group address frame may be a frame buffered by the AP corresponding to a nontransmitted BSSID. Therefore, the group address frame is the group address frame of the AP or BSS corresponding to a nontransmitted BSSID. Each bit from bitmap number 1 to bitmap number (2^n-1) in the Traffic indication virtual bitmap subfield can indicate whether a frame has been buffered by the AP corresponding to each bit. In this case, bits with bit numbers greater than (2^n-1) in the Traffic indication virtual bitmap subfield indicate whether a frame sent to a station with AID n has been buffered by the AP that transmits the TIM element. Therefore, APs do not need to assign AIDs from 1 to (2^n-1). In such an embodiment, the bits corresponding to an inactive (nontransmitted) BSSID may be set as reserved bits. In this case, the value of the reserved bits may be set to 0. Also, the AP can assign a station AID to a number equal to or greater than 2^n. In this case, the AP can assign a station AID from a value between 2^n and 2007. The EHT AP does not have to assign 2007 as the AID. The range in which AIDs can be assigned in this way is called the AID space. Transmitted BSSIDs and nontransmitted BSSIDs can share one AID space. In a specific embodiment, the EHT AP does not have to assign 2007 as the station AID.
[0150] The maximum number of BSSIDs n that a multiple BSSID set may have may be signaled by the multiple BSSID element. n may be the value indicated by the MaxBSSID Indicator of the multiple BSSID element.
[0151] This section describes how to configure the subfields of a Partial virtual bitmap. The method for configuring the subfields of a Partial virtual bitmap may differ depending on the multiple BSSID set-related function of the AP that transmits the TIM element. Non-S1G APs can configure the subfields of the Partial virtual bitmap by method A or method B. S1G APs can configure the subfields of the Partial virtual bitmap by method C. Non-HT APs, HT APs, VHT APs, HE APs, and EHT APs may all be non-S1G APs. An S1G AP refers to an AP that operates in a frequency band of 1 GHz or less, while a non-S1G AP refers to an AP that operates in a frequency band greater than 1 GHz.
[0152] First, let's explain Method A. The subfields of the Partial virtual bitmap may consist of bits from octet number 0 to N2 of the Traffic indication virtual bitmap. N2 is the smallest number in the Traffic indication virtual bitmap that satisfies the condition that all bits from bit number (N2+1)*8 to 2007 have a value of 0. If no such N2 exists, then N2 is 250. In Method A, the value of the Bitmap Offset field is 0. Also, the value of the Length field is N2+4.
[0153] Method B will be described. The subfield of the Partial virtual bitmap may be composed of bits from octet number 0 to (N0-1) of the Traffic indication virtual bitmap, and bits from octet number N1 to N2 of the Traffic indication virtual bitmap. N0 may be the largest positive integer that satisfies (N0*8-2^n<8). When N0 is an odd number, N1 may be the largest even number that satisfies N0<N1 and all bit values from bit number N0*8 to (N1*8-1) are 0. If there is no value that satisfies N1>N0, N1 may be N0. In addition, N2 is the smallest positive integer that satisfies all bit values from bit number (N2+1)*8 to 2007 of the Traffic indication virtual bitmap are 0. If there is no N2 that satisfies this condition, N2 may be 250. In Method B, the value of the Bitmap Offset field is (N1-N0) / 2. In addition, the value of the Length field is (N0+N2-N1+4). When there are no buffered frames in any BSS corresponding to the transmitted BSSID and nontransmitted BSSID, the length of the Partial Virtual Bitmap subfield is 1 octet, and all bit values of the Partial Virtual Bitmap subfield may be set to 0. At this time, the value of the Bitmap Offset field is 0. In addition, the value of the Length field is 4.
[0154] If no individually addressed frames are buffered in any BSS corresponding to transmitted BSSIDs and nontransmitted BSSIDs, and group address frames are buffered in one or more BSSs, then the subfields of the Partial virtual bitmap may consist of bits from octet number 0 to (N0-1). N0 is the largest positive integer satisfying (N0*8-2^n)<8.
[0155] It may be necessary to direct buffered traffic to each of the multilinks on which the multilink device operates. This will be explained using Figures 13 to 18.
[0156] Figure 13 shows the format of a Multi-Link Traffic element according to an embodiment of the present invention.
[0157] APs operating on a single multilink device can share an AID space. Specifically, one multilink device may have one AID space. In this case, when a station uses the TIM element described in Figure 12 to indicate a buffered frame to the AP, it can be difficult for the station to determine which link the frame is buffered on. A traffic instruction signaling method is needed to solve this. Specifically, the multilink device can perform traffic instruction signaling on a link-by-link basis. In a specific embodiment, the multilink device can perform traffic instruction signaling for each station belonging to the multilink device. The TIM element transmitted by the multilink device can indicate whether or not there are buffered frames on each multilink on which the multilink device operates. In this case, the TIM element transmitted by the multilink device is called a Multi-Link Traffic element.
[0158] A multi-link device can transmit Multi-Link Traffic elements in beacon frames or TIM frames. Furthermore, Multi-Link Traffic elements may be included in frames containing TIM elements.
[0159] In Figure 13, the Multi-Link Traffic element may include an Element ID subfield, a Length subfield, an Element ID Extension subfield, a Multi-Link Traffic Control subfield, and a Per-Link Traffic Indication List subfield.
[0160] The Element ID subfield is a one-octet field that indicates the ID of the element containing the Element ID subfield.
[0161] The Length subfield is a one-octet field that indicates the length of the element containing the Length subfield. Specifically, the Length subfield can indicate the length of an element excluding the Element ID subfield and the Length subfield.
[0162] The Element ID Extension subfield is a one-octet field that, when combined with the value of the Element ID subfield containing it, indicates a value that identifies the element.
[0163] The Multi-Link Traffic Control subfield is a one-octet field containing the Bitmap Size subfield and the AID Offset subfield. The Bitmap Size subfield is a four-bit subfield that indicates the size of the Per-Link Traffic Indication Bitmap subfield. When the value of Bitmap Size is M, the size of the Per-Link Traffic Indication Bitmap subfield may be M+1. A value of 0 for Bitmap Size is a reserved value.
[0164] The AID Offset subfield is an 11-bit subfield that indicates the starting bit position of the Traffic indication virtual bitmap indicated by the Per-Link Traffic Indication List or Per-Link Traffic Indication Bitmap subfield. Therefore, the AID Offset subfield determines the AID (association ID) corresponding to the Per-Link Traffic Indication List or Per-Link Traffic Indication Bitmap subfield. When the value of AID Offset is K, the Per-Link Traffic Indication List or Per-Link Traffic Indication Bitmap subfield indicates the Traffic indication virtual bitmap starting with bit number K. Also, when the value of the AID Offset subfield is K, the smallest value among the AIDs corresponding to the Per-Link Traffic Indication List or Per-Link Traffic Indication Bitmap subfield is K. The Per-Link Traffic Indication List subfield is a variable-length field and may contain one or more Per-Link Traffic Indication Bitmap subfields. When the value of the AID Offset subfield is K, each Per-Link Traffic Indication Bitmap subfield indicates starting with bit number K of the Traffic indication virtual bitmap. The number of Per-Link Traffic Indication Bitmap subfields included in the Per-Link Traffic Indication List subfield may be the number of bits in the Partial Virtual Bitmap that correspond to the AID of a non-AP multilink device and are set to 1.Multiple Per-Link Traffic Indication Bitmap subfields are Per-Link Traffic Indication List subfields and may be sorted by the AID corresponding to the Per-Link Traffic Indication Bitmap subfield. Specifically, multiple Per-Link Traffic Indication Bitmap subfields are Per-Link Traffic Indication List subfields and may be sorted in ascending order of the AID corresponding to the Per-Link Traffic Indication Bitmap subfield.
[0165] When the value of the Bitmap Size field is m, the size of the Per-Link Traffic Indication Bitmap subfield is m+1 bits. If the TID-to-link mapping negotiation is successful, the bits in the Per-Link Traffic Indication Bitmap subfield indicate whether the traffic destined for the non-AP station operating on the corresponding link is buffered. Specifically, when the value of a bit in the Per-Link Traffic Indication Bitmap subfield is 1, the bit in the Per-Link Traffic Indication Bitmap subfield can indicate that the traffic destined for the non-AP station operating on the corresponding link is buffered. When the value of a bit in the Per-Link Traffic Indication Bitmap subfield is 0, the bit in the Per-Link Traffic Indication Bitmap subfield can indicate that the traffic destined for the non-AP station operating on the corresponding link is not buffered. When the TID-to-link mapping is the default mapping, the bits in the Per-Link Traffic Indication Bitmap subfield can indicate whether or not it is recommended to retrieve buffered traffic on the corresponding link. Specifically, when the value of a bit in the Per-Link Traffic Indication Bitmap subfield is 1, the bit in the Per-Link Traffic Indication Bitmap subfield can indicate that it is recommended to retrieve buffered traffic on the corresponding link. When the TID-to-link mapping for a link is the default mapping, uplink and downlink transmissions on that link may be performed without TID restrictions. Also, the default mapping is applied to links where TID-to-link mapping negotiations have not been successfully completed.Therefore, if the TID-to-link mapping negotiation is successful, it can indicate that the TID-to-link mapping negotiation is successful and not all TIDs are mapped to all links.
[0166] The bits in the Per-Link Traffic Indication Bitmap subfield are mapped to links by their bit number. Specifically, in the Per-Link Traffic Indication Bitmap subfield, a bit with bit number n may be mapped to a link with link ID n. The Per-Link Traffic Indication List subfield may also include a padding field. This allows the Per-Link Traffic Indication List subfield to have a length in octets. The padding field may have a length of 0 to 7 bits.
[0167] AP multilink devices can transmit frames that include both Multi-Link Traffic elements and TIM elements. In this case, the frame may be a beacon frame. Figure 14 illustrates how AP multilink devices signal buffered traffic using Multi-Link Traffic elements and TIM elements.
[0168] Figure 14 shows how the Partial Virtual Bitmap subfield of the Multi-Link Traffic element and TIM element according to an embodiment of the present invention signals buffered traffic to the AP multilink device.
[0169] The Partial Virtual Bitmap subfield or Traffic indication virtual bitmap of the TIM element transmitted by the AP multilink device may have a bit corresponding to the non-AP multilink device set to 1. In this case, the non-AP multilink device can parse the Multi-Link Traffic element. Based on the Per-Link Traffic Indication Bitmap subfield corresponding to the non-AP multilink device in the Multi-Link Traffic element, the non-AP multilink device can determine which link the non-AP multilink device recommends retrieving buffered traffic from, or which link the non-AP multilink device has buffered traffic on. As explained in Figure 13, if the TID-to-link mapping negotiation is successful, the non-AP multilink device can determine, based on the bit value in the Per-Link Traffic Indication Bitmap subfield corresponding to the non-AP multilink device, whether or not traffic is buffered for transmission to the non-AP multilink device station operating on the corresponding link. Furthermore, when TID-to-link mapping is the default mapping, a non-AP multilink device can indicate whether or not it recommends that an AP multilink device request the transmission of buffered traffic on the link corresponding to the bit in the Per-Link Traffic Indication Bitmap subfield that pertains to the non-AP multilink device.
[0170] A non-AP multilink device can request an AP multilink device to transmit buffered traffic on the link corresponding to the bit set to 1 in the Per-Link Traffic Indication Bitmap subfield that corresponds to the non-AP multilink device. Specifically, if the TID-to-link mapping negotiation is successful, the non-AP multilink device can request the AP multilink device to transmit buffered traffic on the link corresponding to the bit set to 1 in the Per-Link Traffic Indication Bitmap subfield that corresponds to the non-AP multilink device. If the TID-to-link mapping is the default mapping, the non-AP multilink device can request the AP multilink device to transmit buffered traffic on one or more links, including the link corresponding to the bit set to 1 in the Per-Link Traffic Indication Bitmap subfield that corresponds to the non-AP multilink device. In such an embodiment, the non-AP multilink device can request the AP multilink device to transmit buffered traffic by sending a U-APSD trigger frame or a PS-Poll frame. When an AP multilink device receives a request to send buffered traffic, it can send the buffered traffic to a non-AP multilink device. Alternatively, when an AP multilink device receives a request to send buffered traffic, it can send a QoS Null frame instead of the buffered traffic.
[0171] In the embodiment shown in Figure 14, legacy stations prior to EHT or stations where TID-to-link mapping is set as the default mapping are assigned an AID value smaller than K. Non-AP stations where negotiations regarding TID-to-link mapping have been successfully completed are assigned an AID value equal to or greater than K. In the Traffic indication virtual bitmap in Figure 14, all bits smaller than bit number (N-1)*8 are set to 0. Therefore, the AP multilink device does not buffer traffic to stations with an AID smaller than (N-1)*8. At least one bit corresponding to bit number (N-1)*8 or greater is set to 1. N-1 is an even number, and the N*8 value is k. Therefore, the Partial Virtual Bitmap subfield first includes bit number (N-1)*8 of the Traffic indication virtual bitmap. At this time, the value of the Bitmap Offset subfield of the Partial Virtual Bitmap subfield is set to (N-1) / 2. Additionally, the bits in the Partial Virtual Bitmap subfield corresponding to AID (N-1)*8, (N-1)*8+2, (N-1)*8+3, k, k+2, and k+3 are set to 1.
[0172] As mentioned above, the AID Offset subfield of the Multi-Link Traffic element can indicate the AID of the multilink device corresponding to the first Per-Link Traffic Indication Bitmap subfield of the Multi-Link Traffic element. In Figure 14, the value of the AID Offset subfield is set to K. The Multi-Link Traffic element includes a Per-Link Traffic Indication Bitmap subfield corresponding to the multilink device whose Partial Virtual Bitmap subfield is indicated as 1. In Figure 14, the Multi-Link Traffic element includes Per-Link Traffic Indication Bitmap subfields for each of the stations or non-AP multilink devices whose AIDs are k, k+2, and k+3. In this case, the Per-Link Traffic Indication Bitmap subfields are sorted in ascending order of AID.
[0173] The value of the Bitmap Size field of the Multi-Link Traffic element is 2. Therefore, the Per-Link Traffic Indication Bitmap subfield of the Multi-Link Traffic element contains 3 bits. In this case, the first bit (B0) of the Per-Link Traffic Indication Bitmap subfield is mapped to the link with link ID 0, the second bit (B1) is mapped to the link with link ID 1, and the third bit (B2) is mapped to the link with link ID 2.
[0174] As mentioned above, the default mapping was applied to multilink devices with an AID value of K, and TID-to-link mapping was successfully performed for multilink devices with AID values of K+2 and K+3. Therefore, the Per-Link Traffic Indication Bitmap subfield corresponding to AID K indicates that it is recommended to request the transmission of buffered traffic on the link with link ID 1. Furthermore, the Per-Link Traffic Indication Bitmap subfield corresponding to AID K+2 indicates that the AP multilink device is buffering traffic on two links with link IDs 1 and 2. In this case, the traffic buffered on the link with link ID 1 and the traffic buffered on the link with link ID 2 may be the same or different. Furthermore, the Per-Link Traffic Indication Bitmap subfield corresponding to AID K+3 indicates that the AP multilink device is buffering traffic on the link with link ID 1.
[0175] However, it is not guaranteed that the AIDs of non-AP multilink devices connected to an AP multilink device will be assigned consecutively. Also, an AID of a non-AP station not included in the multilink device may be assigned to an AID between AIDs of non-AP multilink devices. In this case, it may be difficult for the non-AP multilink device to determine which AID belongs to a station not included in the non-AP multilink device. Therefore, if the Multi-Link Traffic element does not include a Per-Link Traffic Bitmap subfield for stations not included in the non-AP multilink device, the non-AP multilink device may have difficulty parsing the Per-Link Traffic Bitmap subfield. For example, in the embodiment shown in Figure 14, AID K+1 is assigned to a non-AP multilink device, and the value of the bit corresponding to AID K+1 in the Partial Virtual Bitmap subfield of the TIM element may be 1. In this case, a non-AP multilink device with AID K+2 or K+3 cannot determine which of the three Per-Link Traffic Bitmap subfields is the Per-Link Traffic Bitmap subfield for that non-AP multilink device. Therefore, a method for configuring the Multi-Link Traffic element is needed to resolve this. This is explained in Figure 15.
[0176] Figure 15 shows a Multi-Link Traffic element configuration method according to an embodiment of the present invention.
[0177] In embodiments of the present invention, the AP multilink device may include a Per-Link Traffic Bitmap subfield in the Multi-Link Traffic element for non-AP stations not included in the multilink device. Specifically, the AP multilink device may include a Per-Link Traffic Bitmap subfield for non-AP stations in the Multi-Link Traffic element, even if the station is a non-AP station not included in the multilink device, if the bit value of the Traffic Indication Bitmap subfield or Partial Virtual Bitmap subfield corresponding to the non-AP station is 1. Therefore, the AP multilink device may include a Per-Link Traffic Bitmap subfield in the Multi-Link Traffic element for all stations corresponding to the bit of the Traffic Indication Bitmap subfield or the bit of the Partial Virtual Bitmap subfield set to 1. For convenience of explanation, stations corresponding to the bit of the Traffic Indication Bitmap subfield or the bit of the Partial Virtual Bitmap subfield set to 1 are referred to as stations with buffered traffic indicated.
[0178] In this case, the AP multilink device may include a Per-Link Traffic Bitmap subfield for all stations to which buffered traffic is directed in the Multi-Link Traffic element, regardless of whether the station to which the buffered traffic is directed belongs to a multilink device, whether it is a non-AP multilink device, or which AP or BSS it belongs to. Whether the station to which the buffered traffic is directed belongs to an AP or BSS can be indicated by whether the station to which the buffered traffic is directed belongs to a multiple BSSID set.
[0179] An AP multilink device can include a Per-Link Traffic Bitmap subfield in its Multi-Link Traffic element equal to the number of stations to which buffered traffic is directed. This section describes how an AP multilink device can configure the Per-Link Traffic Bitmap subfield for stations that do not belong to the multilink device.
[0180] An AP multilink device can set the bit values of the Per-Link Traffic Bitmap subfield corresponding to stations that do not belong to the multilink device to 0. That is, an AP multilink device can set the bit values of the Per-Link Traffic Bitmap subfield corresponding to stations that do not belong to the multilink device as reserved fields. In yet another specific embodiment, an AP multilink device can set the bit values of the Per-Link Traffic Bitmap subfield corresponding to stations that do not belong to the multilink device to an arbitrary value. In yet another specific embodiment, an AP multilink device can set the bit value of the Per-Link Traffic Bitmap subfield corresponding to stations that do not belong to the multilink device to 1. In this case, a non-AP multilink device can ignore the bit values of the Per-Link Traffic Bitmap subfield corresponding to stations that do not belong to the multilink device. In yet another specific embodiment, an AP multilink device can set the bit value of the Per-Link Traffic Bitmap subfield corresponding to stations that do not belong to the multilink device to 1. In yet another specific embodiment, the AP multilink device can set the value of the bits in the Per-Link Traffic Bitmap subfield that correspond to the links on which stations not belonging to the multilink device are operating to 1, and set the value of the remaining bits to 0.
[0181] In the embodiment shown in Figure 15, the settings for the Traffic indication virtual bitmap and the Partial Virtual Bitmap subfield may be the same as those for the Traffic indication virtual bitmap and Partial Virtual Bitmap subfield in Figure 14. However, in the embodiment shown in Figure 15, AID k and AID k+3 correspond to non-AP multilink devices. AID K+2 corresponds to a station not included in the multilink device. The Per-Link Traffic Bitmap subfields corresponding to AID k and AID k+3 of the Multi-Link Traffic element are set as in the embodiment shown in Figure 14. Since AID K+2 is a station not included in the multilink device, all bits in the Per-Link Traffic Bitmap subfield corresponding to AID k+2 of the Multi-Link Traffic element are set to 0.
[0182] The AID Offset subfield of the Multi-Link Traffic element can indicate the bits after all bits corresponding to the Group ID and group address frame in the bits of the Traffic indication virtual bitmap and the Partial Virtual Bitmap subfield. In this case, the Group ID may include AID values of 0. The Group ID may also include the bit number of the Traffic indication virtual bitmap corresponding to the multiple BSSID set, i.e., the AID corresponding to the bit number. The Group ID may also include the bit number of the Traffic indication virtual bitmap corresponding to the transmitted BSSID and nontransmitted BSSID, i.e., the AID corresponding to the bit number. When the maximum number of possible BSSIDs in the multiple BSSID set is 2^n, the Group ID may include values corresponding to AID 0 to (2^n-1). When a multiple BSSID set is used and the maximum number of possible BSSIDs in the multiple BSSID set is 2^n, the AID Offset subfield can indicate values after the values corresponding to AID 0 to (2^n-1). The reason for setting the AID Offset field in this way is that group address frames are not limited to those transmitted over a specific link, making it less meaningful to signal them on a link-by-link basis.
[0183] According to yet another embodiment of the present invention, even if the AID Offset subfield indicates bits in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfield prior to the bits indicating the Group ID, the Per-Link Traffic Indication Bitmap subfield corresponding to the Group ID does not need to be included in the Multi-Link Traffic element. Even if the AID Offset subfield indicates bits in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfield prior to the bits indicating the Group ID, the Multi-Link Traffic element may include only the Per-Link Traffic Indication Bitmap subfield corresponding to individual stations among the stations to which buffered traffic is indicated. Specifically, when the maximum number of configurable BSSIDs in a multiple BSSID set is 2^n, the AID Offset subfield can indicate bits in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfield corresponding to AIDs of (2^n-1) or less. In this case, the Multi-Link Traffic element may include only the Per-Link Traffic Indication Bitmap corresponding to the bits of the Traffic indication virtual bitmap and the bits of the Partial Virtual Bitmap subfield that correspond to AID2^n and are set to 1.A station receiving a Multi-Link Traffic element can determine that the Multi-Link Traffic element contains only the Per-Link Traffic Indication Bitmap, which includes bits in the Traffic indication virtual bitmap and the Partial Virtual Bitmap subfield that correspond to AID2^n and are set to 1.
[0184] According to yet another embodiment of the present invention, regardless of whether the AID Offset subfield indicates bits in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfield prior to the bit indicating the Group ID, the Multi-Link Traffic element may include a Per-Link Traffic Indication Bitmap corresponding to each of the bits set to 1 after the bit indicated by the AID Offset subfield in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfield. In this case, the AP multilink device can set the values of both the Traffic indication virtual bitmap and the Per-Link Traffic Indication Bitmap field corresponding to the bits in the Partial Virtual Bitmap subfield corresponding to the group address to a predetermined value. The predetermined value may be 0. In yet another specific embodiment, the AP multilink device can set the values of the Per-Link Traffic Indication Bitmap field corresponding to the Traffic indication virtual bitmap and the bits in the Partial Virtual Bitmap subfield corresponding to the group address to any value. The AP multilink device can set the bit corresponding to the link to which the group address frame is transmitted to 1 and the remaining bits to 0 in the Per-Link Traffic Indication Bitmap field, which corresponds to the bits in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields corresponding to the group address.
[0185] Figure 16 shows a method for setting the Per-Link Traffic Bitmap subfield of the Multi-Link Traffic element when the link set on which the AP multilink device according to an embodiment of the present invention operates is different from the link set on which the non-AP multilink device communicating with the AP multilink device operates.
[0186] The link set on which an AP multilink device operates may differ from the link set on which a non-AP multilink device communicating with the AP multilink device operates. For example, an AP multilink device may communicate with a first non-AP multilink device on links 1 through 3, and the AP multilink device may communicate with a second non-AP multilink device on links 1 and 2. In this case, the method of setting the Per-Link Traffic Bitmap subfield of the Multi-Link Traffic element may become an issue.
[0187] Even if the link set on which the AP multilink device operates is different from the link set on which the non-AP multilink device communicating with the AP multilink device operates, the AP can set the size of all Per-Link Traffic Indication Bitmap subfields contained in the Multi-Link Traffic element to be the same, and set the links mapped to each bit of each Per-Link Traffic Indication Bitmap subfield to be the same. Specifically, the AP multilink device can set the number of bits in all Per-Link Traffic Indication Bitmap subfields contained in the Multi-Link Traffic element to be greater than the number of links set by the AP multilink device. This is because the multiple link IDs set by the AP multilink device may not start from 0, or the IDs of multiple links may not be consecutive. For example, the AP multilink device can set the number of bits in all Per-Link Traffic Indication Bitmap subfields contained in the Multi-Link Traffic element to be the maximum number of links that the AP multilink device can set. In yet another specific embodiment, the AP multilink device can set the number of bits in all Per-Link Traffic Indication Bitmap subfields included in the Multi-Link Traffic element to the maximum link ID value that the AP multilink device can set plus 1.
[0188] A potential issue is how to set the bit values in the Per-Link Traffic Indication Bitmap subfield corresponding to links not configured by the AP multilink device and links not configured by the non-AP multilink device corresponding to the Per-Link Traffic Indication Bitmap subfield. For convenience of explanation, the bits in the Per-Link Traffic Indication Bitmap subfield corresponding to links not configured by the AP multilink device and links not configured by the non-AP multilink device corresponding to the Per-Link Traffic Indication Bitmap subfield are referred to as "no-link bits." The AP multilink device can set the value of the no-link bits to a predetermined value. Therefore, the AP multilink device can set the bits in the Per-Link Traffic Indication Bitmap subfield corresponding to links not configured by the AP multilink device or the non-AP multilink device to a predetermined value. In this case, the predetermined value may be 0. Furthermore, in other specific embodiments, the AP multilink device can set the value of the no-link bits to any value. In this case, the non-AP station can ignore the value of the no-link bits.
[0189] Furthermore, the bit value in the Per-Link Traffic Indication Bitmap subfield corresponding to a disabled link may be set to reserved. Specifically, the bit value in the Per-Link Traffic Indication Bitmap subfield corresponding to a disabled link may be set to 0. In this case, a disabled link may be a link on which uplink and downlink transmission has been stopped. Specifically, a disabled link may be a link on which uplink and downlink transmission of individual address frames has been stopped. In this case, a non-AP station can ignore the value of the no-disabled bit.
[0190] In the embodiment shown in Figure 16, as seen in Figure 16(a), the AP multilink device (AP MLD) operates on the first link (Link0) to the third link (Link2). The first multilink device (MLD 1) and the AP multilink device (AP MLD) configure the first link (Link0) to the third link (Link2). The second multilink device (MLD 2) and the AP multilink device (AP MLD) configure the first link (Link0) to the second link (Link1). The AP multilink device (AP MLD) sets the number of bits in the Per-Link Bitmap subfield of the Multi-Link Traffic element to 3 bits. The Multi-Link Traffic element transmitted by the AP multilink device (AP MLD) includes the Per-Link Bitmap subfield corresponding to the first multilink device (MLD 1), the first station (STA1), and the second multilink device (MLD 2), respectively. The AP Multilink Device (AP MLD) sets the value of the Per-Link Bitmap subfield corresponding to the first multilink device (MLD 1) according to the embodiment described in Figures 14 and 15. The AP Multilink Device (AP MLD) also sets the value of the Per-Link Bitmap subfield corresponding to the first station (STA1) according to the embodiment described in Figure 15. The AP Multilink Device (AP MLD) sets the values of the first bit (B0) and second bit (B1) of the Per-Link Bitmap subfield corresponding to the second multilink device (MLD 2) according to the embodiment described in Figures 14 and 15. Furthermore, the AP Multilink Device (AP MLD) sets the value of the third bit (B2) of the Per-Link Bitmap subfield corresponding to the second multilink device (MLD 2) to 0, as previously specified.
[0191] In the previously described embodiment, it was explained that the bit number of a bit in the Per-Link Traffic Indication Bitmap subfield and the ID of the link corresponding to that bit are the same. However, in a specific embodiment, the bit number of a bit in the Per-Link Traffic Indication Bitmap subfield and the ID of the link corresponding to that bit do not have to be the same. The bit number of a bit in the Per-Link Traffic Indication Bitmap subfield may be mapped in ascending order to the link IDs of the links set by the AP multilink device that transmitted the Per-Link Traffic Indication Bitmap subfield. The AP multilink device may set a link with ID 1 and a link with ID 3, and the Per-Link Traffic Indication Bitmap subfield may be a 2-bit field. In this case, the first bit (B0) of the Per-Link Traffic Indication Bitmap subfield is mapped to the link with ID 1, and the second bit (B1) is mapped to the link with ID 3.
[0192] Figure 17 shows how the link indicated by the Per-Link Traffic Bitmap subfield according to an embodiment of the present invention is determined by TID-to-link mapping.
[0193] As mentioned above, if the TID-to-link mapping negotiation is successful, the bits in the Per-Link Traffic Indication Bitmap subfield indicate whether traffic destined for a non-AP station operating on the corresponding link is buffered. Specifically, if the value of a bit in the Per-Link Traffic Indication Bitmap subfield is 1, the bit in the Per-Link Traffic Indication Bitmap subfield can indicate that traffic destined for a non-AP station operating on the corresponding link is buffered. If the value of a bit in the Per-Link Traffic Indication Bitmap subfield is 0, the bit in the Per-Link Traffic Indication Bitmap subfield can indicate whether or not it is recommended to retrieve buffered traffic on the corresponding link. Specifically, when the value of a bit in the Per-Link Traffic Indication Bitmap subfield is 1, the bit in the Per-Link Traffic Indication Bitmap subfield can indicate that it is recommended to request the transmission of buffered traffic on the corresponding link. If a link's TID-to-link mapping is the default mapping, uplink and downlink transmissions on that link may be performed without TID restrictions. The default mapping is also applied to links where TID-to-link mapping negotiations have not been successfully conducted or where TID-to-link mapping negotiations have been terminated (tear down).
[0194] If the aforementioned TID-to-link mapping negotiation is successful, it can indicate that the TID-to-link mapping was applied instead of the default mapping. Also, as mentioned above, the TID-to-link mapping may be applied separately for each transmission direction. Therefore, in the above-described embodiment, if the TID-to-link mapping negotiation is successful, it can indicate that the TID-to-link mapping negotiation for downlink transmission was successful. Also, if the default mapping is applied, it can indicate that the TID-to-link mapping for downlink transmission is the default mapping.
[0195] In the embodiment shown in Figure 17, the AP multilink device (AP MLD) and the non-AP multilink device (non-AP MLD 1) successfully negotiate TID-to-link mapping. The AP multilink device (AP MLD) and the non-AP multilink device (non-AP MLD 1) map TID value 0 to the uplink transmission of the first link (link0). The AP multilink device (AP MLD) and the non-AP multilink device (non-AP MLD 1) also map TID values 1 to 7 to the uplink transmission of the second link (link1). At this time, the AP multilink device (AP MLD) and the non-AP multilink device (non-AP MLD 1) apply default mapping to the downlink transmission of the first link (link0) and the downlink transmission of the second link (link1). Therefore, if the value of a bit in the Per-Link Traffic Indication Bitmap subfield transmitted by the AP multilink device (AP MLD) is 1, the non-AP multilink device (non-AP MLD 1) determines that the AP multilink device (AP MLD) recommends that the non-AP multilink device (non-AP MLD 1) request traffic transmission on the link corresponding to the bit set to 1. In Figure 17(a), the value of the bit corresponding to the second link (link1) in the Per-Link Traffic Indication Bitmap subfield is 1, so the non-AP multilink device (non-AP MLD 1) determines that it recommends requesting traffic transmission on the second link (link1).
[0196] Figure 17(b) shows the TID-to-Link Mapping element used in TID-to-link mapping negotiations. A multilink device may include the TID-to-Link Mapping element in (Re)Association Request frames, (Re)Association Response frames, TID-to-Link mapping request frames, and TID-to-Link mapping response frames. When a multilink device requests TID-to-link mapping, it may include the TID-to-Link Mapping element in the (Re)Association Request frame or the TID-to-Link mapping request frame. When a multilink device responds to a TID-to-link mapping request, it may include the TID-to-Link Mapping element in the (Re)Association Response frame or the TID-to-Link mapping response frame.
[0197] A TID-to-Link Mapping element may include an Element ID subfield, a Length subfield, an Element ID Extension subfield, a TID-To-Link Mapping Control subfield, and seven Link Mapping subfields corresponding to TIDs 0 through 7. The TID-to-Link Mapping Control subfield may include a Direction subfield, a Default Link Mapping subfield, a Reserved subfield, and a Link Mapping Presence Indicator subfield. The Direction subfield can indicate which transmission direction the TID-to-Link Mapping element, including the Direction subfield, is intended for TID-to-Link mapping negotiations to apply the default mapping. Specifically, the Default Link Mapping subfield can indicate whether a TID-To-Link Mapping element containing the Default Link Mapping subfield is for TID-to-link mapping negotiation to apply the default mapping to the transmission direction indicated by the Direction subfield.
[0198] Each bit in the Link Mapping Presence Indicator subfield indicates whether the Link Mapping subfield corresponding to that bit is included in the TID-To-Link Mapping element. Each bit in the Link Mapping Presence Indicator subfield may be mapped to a Link Mapping subfield for a TID that has a value such as a bit index. That is, the nth bit (Bn-1) of the Link Mapping Presence Indicator subfield may be mapped to the Link Mapping subfield corresponding to TID n-1. The Link Mapping subfield indicates that the TID corresponding to the Link Mapping subfield is subject to negotiation for TID-to-link mapping performed by the TID-to-Link Mapping element.
[0199] Figure 18 shows a method by which an AP multilink device sets the Per-Link Traffic Indication Bitmap subfield of a Multi-Link Traffic element, according to yet another embodiment of the present invention.
[0200] In the embodiment described in Figure 16, the Multi-Link Traffic element includes a Per-Link Traffic Indication Bitmap subfield for stations that indicate buffered traffic, regardless of whether the stations that indicate buffered traffic are included in the multilink device. In yet another embodiment of the present invention, the Multi-Link Traffic element may include a Per-Link Traffic Indication Bitmap subfield for some of the stations that indicate buffered traffic, and may not include a Per-Link Traffic Indication Bitmap subfield for the remaining stations that indicate buffered traffic. In this case, stations that indicate buffered traffic may be limited to stations that indicate buffered traffic from the bit corresponding to the AID indicated by the AID Offset subfield. Specifically, the AP multilink device does not need to include a Per-Link Traffic Indication Bitmap subfield for stations that indicate buffered traffic in the Multi-Link Traffic element if the stations that indicate buffered traffic are not included in the multilink device. This prevents the length of the Multi-Link Traffic element from becoming too long.
[0201] In yet another specific embodiment, the AP multilink device does not need to include in the Multilink Traffic element the Per-Link Traffic Indication Bitmap subfield for stations whose buffered traffic is indicated after a specific bit. A station receiving the Multilink Traffic element can determine the last Per-Link Traffic Indication Bitmap subfield included in the Multilink Traffic element based on the Length subfield of the Multilink Traffic element. Therefore, even if the Multilink Traffic element does not include the Per-Link Traffic Indication Bitmap subfield for stations whose buffered traffic is indicated after a specific bit, a station receiving the Multilink Traffic element can parse the Multilink Traffic element successfully. In such an embodiment, the AP multilink device may assign a smaller AID value to stations included in the multilink device than to the AID of stations not included in the multilink device.
[0202] In the embodiment shown in Figure 18, the AID Offset of the Multi-Link Traffic element indicates an AID value of K. Stations that indicate buffered traffic with an AID greater than K are those not included in the two multilink devices with AIDs K and K+2, and stations not included in the multilink devices with AIDs K+6 and K+7. The Multi-Link Traffic element includes a Per-Link Traffic Indication Bitmap subfield for the two multilink devices with AIDs K and K+2.
[0203] In yet another specific embodiment, the Multi-Link Traffic element may include an AID Offset2 subfield. A station receiving the Multi-Link Traffic element can parse the Per-Link Traffic Indication Bitmap subfield of the Multi-Link Traffic element based on the AID Offset2 subfield. The AID Offset2 subfield can indicate which AID corresponds to the last Per-Link Traffic Indication Bitmap subfield of the Multi-Link Traffic element. In this case, the AID Offset2 subfield can indicate all AID values. In yet another specific embodiment, the AID Offset2 subfield can indicate the maximum value of the AID that can correspond to the last Per-Link Traffic Indication Bitmap subfield.
[0204] In further specific embodiments, the AID Offset2 subfield can specify the AIDs corresponding to the last Per-Link Traffic Indication Bitmap subfield in units of a predetermined number. For example, when the value of the AID Offset2 subfield is n, the AID Offset2 subfield can specify 2^N as the AIDs corresponding to the last Per-Link Traffic Indication Bitmap subfield, where N is an integer. In such embodiments, the AID Offset2 subfield may have a length of (11-N) bits.
[0205] When the value of the AID Offset2 subfield is n, the AID Offset2 subfield can indicate that the AID value is 2^N*n, where n is an integer. For example, it can indicate AIDs in units of 8. In this case, the AID Offset2 subfield may have a length of 8 bits. In such an embodiment, the AID Offset2 subfield can indicate AIDs such as 8, 16, 24, 32, etc. This allows the length of the AID Offset2 subfield to be defined as less than 11 bits.
[0206] In other specific embodiments, the AID Offset2 subfield can specify AID in the same units as the AID Offset subfield. This reduces the number of bits occupied by the AID Offset2 and AID Offset subfields.
[0207] In the embodiment described above, a single frame may contain multiple Multi-Link Traffic elements. Specifically, in an AID list obtained by sorting the AID values of stations that have buffered traffic with AIDs equal to or greater than the AID indicated by the AID Offset subfield in ascending order, the AP multilink device can generate Multi-Link Traffic elements containing Per-Link Traffic Indication Bitmaps for one or more multilink devices corresponding to the AID values, from the first AID in the list up to the excluded AIDs corresponding to stations not included in the multilink device. At this time, AIDs from the AID list up to the excluded AIDs are excluded from the AID list, and the AP multilink device can generate Multi-Link Traffic elements containing Per-Link Traffic Indication Bitmaps for one or more multilink devices corresponding to the AID values up to the new excluded AID in the AID list. The AP multilink device can repeat this operation to the end of the AID list and generate even more Multi-Link Traffic elements containing Per-Link Traffic Indication Bitmaps for one or more multilink devices. As a result, even if an AID not included in the multilink device is assigned between the AIDs of the multilink device, the Multi-Link Traffic element does not need to include a Per-Link Traffic Indication Bitmap subfield for the multilink device, but does not need to include a Per-Link Traffic Indication Bitmap subfield not included in the multilink device.
[0208] In such embodiments, a non-AP multilink device can ignore Multi-Link Traffic elements that do not contain a Per-Link Traffic Indication Bitmap subfield corresponding to the non-AP multilink device's AID. A non-AP multilink device can determine whether a Multi-Link Traffic element contains a Per-Link Traffic Indication Bitmap subfield corresponding to the non-AP multilink device's AID based on at least one of the values of the AID Offset subfield and the Length subfield of the Multi-Link Traffic element. A non-AP multilink device can determine whether a Multi-Link Traffic element contains a Per-Link Traffic Indication Bitmap subfield corresponding to the non-AP multilink device's AID based on at least one of the values of the AID Offset subfield and the AID Offset2 subfield of the Multi-Link Traffic element.
[0209] Furthermore, in the embodiment described above, if the buffered traffic of the non-AP multilink device is not directed to a station, the non-AP multilink device can ignore the Multi-Link Traffic element.
[0210] The method for determining the AID space will be explained using Figures 19 to 21. First, the EHT Operation element will be explained using Figure 19.
[0211] Figure 19 shows an EHT Operation element according to an embodiment of the present invention.
[0212] Figure 19(a) shows the format of an EHT Operation element, and Figure 19(b) shows the EHT Operation Parameters field. An EHT Operation element may include an Operation Parameters field. The Operation Parameters field may be a 1-octet field. An EHT Operation element may include an EHT Operation Information field. The EHT Operation Information field may have a size of 0, 3, or 5 octets. The EHT Operation Information field may include an EHT Operation Information field or a Disabled Subchannel Bitmap field.
[0213] The EHT Operation Parameters field may include the EHT Operation Information Present subfield, the Disabled Subchannel Bitmap Present subfield, the Group Addressed BU Indication Limit subfield, and the Group Addressed BU Indication Exponent subfield. The EHT Operation Information Present subfield may be a 1-bit field, the Disabled Subchannel Bitmap Present subfield may be a 1-bit field, the Group Addressed BU Indication Limit subfield may be a 1-bit field, and the Group Addressed BU Indication Exponent subfield may be a 1-bit field.
[0214] The EHT Operation Information Present subfield can indicate whether or not an EHT Operation element contains the EHT Operation Information subfield. If the value of the EHT Operation Information Present subfield is 0, the EHT Operation element does not need to contain the EHT Operation Information subfield. That is, when the EHT Operation Information Present subfield is set to 0, the length of the EHT Operation Information subfield may be 0 octets. If the value of the EHT Operation Information Present subfield is 1, the EHT Operation element may contain the EHT Operation Information field. In this case, the length of the EHT Operation Information subfield may be 3 or 5 octets.
[0215] The Disabled Subchannel Bitmap Present subfield can indicate whether the EHT Operation Information field contains the Disabled Subchannel Bitmap subfield. If the value of the Disabled Subchannel Bitmap Present subfield is 0, the EHT Operation Information subfield does not need to contain the Disabled Subchannel Bitmap subfield. In this case, the size of the EHT Operation Information subfield may be 3 octets. If the value of the Disabled Subchannel Bitmap Present subfield is 1, the EHT Operation Information subfield may contain the Disabled Subchannel Bitmap subfield. In this case, the size of the EHT Operation Information subfield may be 5 octets.
[0216] The Group Addressed BU Indication Limit subfield can indicate whether there are buffered group address frames for other APs belonging to the same AP multilink device as all nontransmitted BSSIDs in a multiple BSSID set, and whether there are any restrictions on indicating this in the TIM element. The specific setting method for the Group Addressed BU Indication Limit subfield is as follows:
[0217] The Group Addressed BU Indication Limit subfield may be set to 0 if at least one of the following conditions is met, and to 1 otherwise.
[0218] - Condition 1. The AP (the AP that transmits the EHT Operation element) does not belong to a multiple BSSID set.
[0219] - Condition 2. The number of bits required to indicate whether an AP (an AP that transmits an EHT Operation element, an AP that transmits a beacon frame, or an AP corresponding to a transmitted BSSID) belongs to a multiple BSSID set, and whether there is a buffered group address frame that corresponds to all nontransmitted BSSIDs and all other APs belonging to the same AP multilink device is not greater than 48 bits.
[0220] Furthermore, the Group Addressed BU Indication Exponent subfield can specify the number of bits (N) used to indicate the buffered group address frame corresponding to the other APs of the multilink device corresponding to each nontransmitted BSSID. The value of N will be discussed further later.
[0221] Furthermore, the aforementioned 48 bits may be replaced with other numbers of bits. This means that the number of bits in the bitmap required to indicate group address traffic to other APs on the same multilink device as the AP with a nontransmitted BSSID in the Traffic indication virtual bitmap may change. In this invention, 48 bits or other numbers of bits can be referred to as the "bitmap limit".
[0222] Figure 20 shows a Traffic indication virtual bitmap according to an embodiment of the present invention.
[0223] The Traffic Indication Virtual Bitmap can indicate group address traffic corresponding to APs of multilink devices, such as transmitted BSSIDs, or nontransmitted BSSIDs, and APs of multilink devices. A station receiving the Traffic Indication Virtual Bitmap can determine whether or not group address traffic is buffered at the AP (or BSS) to which the station is connected. The station can also use this to receive buffered group address traffic.
[0224] In embodiments of the present invention, the Traffic indication virtual bitmap may have bits for group address traffic positioned first, followed by bits for individually addressed traffic to stations or multilink devices.
[0225] An AP that transmits a TIM element can indicate a buffered group address frame corresponding to another AP belonging to the multilink device to which the AP belongs. To indicate a buffered group address frame corresponding to another AP belonging to the multilink device to which the AP belongs, the N bits from the last bit used to indicate a nontransmitted BSSID in the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap may be used. If the AP does not belong to a multiple BSSID set, the N bits following the first bit (B0) of the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap can be used to indicate a buffered group address frame corresponding to another AP included in the multilink device to which the AP belongs. In this case, each of the N bits is mapped in order of link ID, and each of the N bits can indicate whether or not a group address frame is buffered on the link mapped to the bit.
[0226] Bits X through X+N-1 of the Partial Virtual Bitmap subfield or Traffic indication virtual bitmap can indicate the group address frame corresponding to the reporting AP (or, if the AP belongs to a multiple BSSID set, the AP corresponding to the transmitted BSSID) and other APs belonging to the multilink device to which the reporting AP belongs. In this case, the reporting AP represents the AP that transmits the TIM element. Also, X-1 may be the last bit used to indicate a nontransmitted BSSID in the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap. If a multiple BSSID set is not used, X-1 may be 0. Also, N may be the N mentioned earlier in the description of the EHT Operation element. Specifically, if the AP transmitting the TIM element does not belong to a multiple BSSID set, X-1 may be 0. Also, N may be the N mentioned earlier in the description of the EHT Operation element. The value of N may be determined based on the Group Addressed BU Indication Exponent subfield. The value of N may be 2^(value of the Group Addressed BU Indication Exponent subfield + 1) - 1. That is, if the value of the Group Addressed BU Indication Exponent subfield is 1, the value of N may be 2^(1 + 1) - 1. That is, the value of N may be 3. In addition, the N bits from bit X to X + N - 1 can indicate whether or not group address traffic is buffered for each link in ascending order of link ID. Of the N bits, the first n bits indicate the group address frame corresponding to other APs in the AP multilink device to which the AP belongs, and the remaining bits may be set to 0.
[0227] The last bit indicating a nontransmitted BSSID in a TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap may be determined based on the theoretical maximum number of BSSIDs in a multiple BSSID set. When the theoretical maximum number of BSSIDs in a multiple BSSID set is 2^n, AIDs 1 to (2^n-1) are reserved for the AID of a nontransmitted BSSID, and the last bit indicating a nontransmitted BSSID in a TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap may correspond to AID(2^n-1). Therefore, bit 2^n of the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap may begin to indicate a buffered group address frame to another AP in the multilink device to which the AP (reporting AP) of a transmitted BSSID belongs.
[0228] In yet another specific embodiment of the present invention, the last bit indicating a nontransmitted BSSID in a TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap may be determined based on the actual bits used as the nontransmitted BSSID. If the maximum number of nontransmitted BSSIDs possible in a multiple BSSID set are not actually used, it may be the last bit of the bits corresponding to the nontransmitted BSSID actually used in the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap.
[0229] In Figure 20, a Partial Virtual Bitmap subfield is constructed using a portion of the Traffic indication virtual bitmap. Each bit in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfield indicates whether or not there is buffered traffic to be sent to the station corresponding to the AID. In this case, the bit numbers of the bits in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfield may be mapped to AID values. In Figure 20, the first bit (B0) of the Traffic indication virtual bitmap is mapped to the transmitted BSSID. In other specific embodiments, the first bit (B0) of the Traffic indication virtual bitmap may be mapped to the reporting AP (the AP that transmits the TIM element). That is, if the reporting AP belongs to a multiple BSSID set, the first bit (B0) of the Traffic indication virtual bitmap is mapped to the reporting AP or the transmitted BSSID. If the reporting AP does not belong to a multiple BSSID set, the first bit (B0) of the Traffic indication virtual bitmap is mapped to the reporting AP. Buffered traffic corresponding to an AP may be group address traffic.
[0230] In the embodiment shown in Figure 20, the second bit (B1) to the fourth bit (B3) of the Traffic indication virtual bitmap are mapped to the nontransmitted BSSID. In this case, (X-1) is 3. Also, the fifth bit (B4) to the seventh bit (B6) of the Traffic indication virtual bitmap may correspond to other APs belonging to the AP multilink device to which the reporting AP or transmitted BSSID belongs. In this case, the value of the Group Addressed BU Indication Exponent subfield is 1. Therefore, N is 3.
[0231] A reporting AP can use the N bits following the last bit (i.e., B X+N-1) in the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap that indicates whether group address traffic corresponding to other APs in the same AP MLD as the AP of the transmitted BSSID has been buffered, to indicate whether group address frames corresponding to other APs in the AP multilink device to which the AP corresponding to the k-th nontransmitted BSSID belongs. Specifically, to indicate a group address frame corresponding to another AP in the AP multilink device to which the AP corresponding to the k-th nontransmitted BSSID belongs, the reporting AP can use the k-th N bits following the last bit (i.e., B X+N-1) in the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap that indicates group address traffic corresponding to other APs in the AP multilink device to which the AP of the transmitted BSSID belongs. In this case, the N bits corresponding to each nontransmitted BSSID are mapped to N links in order of link ID, and each of the N bits indicates whether or not a group address frame has been buffered on the link corresponding to that bit.
[0232] The bits from bit number Y+(k-1)*N to bit number Y+k*N-1 in the reporting Partial Virtual Bitmap subfield or Traffic indication virtual bitmap can indicate whether or not group address traffic corresponding to other APs in the AP multilink device to which the k-th nontransmitted BSSID AP belongs has been buffered. Such embodiments may be applied only when the bit number is smaller than a pre-specified bit number. The pre-specified value may be determined based on the bitmap limit. The pre-specified value may be Y+(bitmap limit). In this case, in the k-th nontransmitted BSSID, k may start from 1. Y-1 may be the last bit indicating whether or not group address frames corresponding to the AP multilink device to which the AP corresponding to the transmitted BSSID belongs have been buffered. That is, Y-1 may be the same value as X+N-1. Also, N may be the N mentioned earlier in the EHT Operation element related embodiments. N may be determined based on the Group Addressed BU Indication Exponent subfield. N may be 2^(value of the Group Addressed BU Indication Exponent subfield + 1) - 1. Also, in the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap, the N bits from bit number Y + (k-1)*N to Y + k*N-1 are mapped to N links in order of link ID, and each of the N bits indicates whether or not a group address frame has been buffered for the link corresponding to that bit. Of the N bits, the first n bits indicate whether or not a group address frame corresponding to another AP belonging to the AP multilink device to which the k-th nontransmitted BSSID AP belongs has been buffered, and the remaining bits may be set to 0.
[0233] In Figure 20, Y is 7 and N is 3. Therefore, in the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap, bits 7+(k-1)*3 to 7+k*3-1 can indicate a group address frame corresponding to another AP belonging to the AP multilink device to which the AP corresponding to the k-th nontransmitted BSSID belongs. That is, in the TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap, bits 7 to 9 indicate a group address frame corresponding to another AP belonging to the AP multilink device to which the AP corresponding to the first nontransmitted BSSID belongs. Also, the k-th nontransmitted BSSID may be a nontransmitted BSSID corresponding to AID k.
[0234] The Traffic indication virtual bitmap and Partial Virtual Bitmap subfields may include, as part of the group address frame, a portion corresponding to the reporting AP (or, if the reporting AP belongs to a multiple BSSID set, the transmitted BSSID), a portion corresponding to the nontransmitted BSSID (if the reporting AP belongs to a multiple BSSID set), a portion corresponding to other APs belonging to the AP multilink device to which the reporting AP belongs, and a portion corresponding to other APs belonging to the AP multilink device to which the nontransmitted BSSID AP belongs (if the reporting AP belongs to a multiple BSSID set). Furthermore, the order in which each portion is included in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields may be the same as the order mentioned above.
[0235] According to the embodiment described in Figure 14, the value of the AID Offset subfield does not need to indicate the portion corresponding to the group ID and group address frame in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields. That is, the value of the AID Offset subfield can indicate a value greater than the maximum value corresponding to the group ID and group address frame in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields. Alternatively, the value of the AID Offset subfield can indicate an individually addressed frame in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields. Alternatively, the value of the AID Offset subfield can indicate a value corresponding to a non-AP station or non-AP multilink device in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields.
[0236] More specifically, in the embodiment described in Figure 14, the value of the AID Offset subfield is determined based on the maximum number of BSSIDs in the multiple BSSID set, so that the value of the AID Offset subfield does not indicate the portion corresponding to the group address frame in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields. According to the embodiments in Figures 19-20, the value of the AID Offset subfield may be determined by further considering other factors. This is because a larger number of bits in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields can indicate a group address frame compared to the maximum number of BSSIDs that the multiple BSSID set can contain.
[0237] According to embodiments of the present invention, the range of values that the AID Offset subfield can indicate may be determined based on the number of bits required to indicate a group address frame corresponding to another AP in the AP multilink device to which the AP corresponding to a transmitted BSSID or nontransmitted BSSID belongs. For example, the range of values that the AID Offset subfield can indicate may be determined based on the maximum number of BSSIDs that the aforementioned multiple BSSID set may contain and the number of bits required to indicate a group address frame corresponding to another AP belonging to the AP multilink device to which the AP corresponding to a transmitted BSSID or nontransmitted BSSID belongs. Alternatively, the range of values that the AID Offset subfield can indicate may be determined based on the maximum number of BSSIDs that the multiple BSSID set may contain, the number of bits required to indicate a group address frame corresponding to another AP belonging to the AP multilink device to which the AP corresponding to a transmitted BSSID or nontransmitted BSSID belongs, and the bitmap limit.
[0238] According to embodiments of the present invention, the AID Offset subfield does not need to indicate the portion corresponding to the group address frame in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields. Alternatively, the AID Offset subfield can indicate the portion not corresponding to the group address frame in the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields.
[0239] In the Traffic indication virtual bitmap and Partial Virtual Bitmap subfields, the portion corresponding to the Group address frame may include the portion corresponding to the reporting AP (or, if the reporting AP belongs to a multiple BSSID set, the transmitted BSSID), the portion corresponding to the nontransmitted BSSID (if the reporting AP belongs to a multiple BSSID set), the portion corresponding to other APs in the same AP MLD as the reporting AP, and the portion corresponding to other APs belonging to the AP multilink device to which the nontransmitted BSSID AP belongs (if the reporting AP belongs to a multiple BSSID set).
[0240] In other words, the value of the AID Offset subfield does not have to be set to less than or equal to the smaller of the value obtained by adding N*((number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs)+1) to (X-1) plus the bitmap limit (or either of the two values if both are the same). The value of the AID Offset subfield may be set to a value greater than the smaller of the value obtained by adding N*((number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs)+1) to (X-1) plus the bitmap limit (or either of the two values if both are the same). As mentioned above, (X-1) may be the last bit that indicates the group address frame for APs belonging to the AP multilink device to which the reporting AP or AP corresponding to the transmitted BSSID belongs. In other words, the AID Offset subfield does not need to specify a value less than or equal to min((X-1)+N*X, X-1+bitmap limit). The value of the AID Offset subfield may be set to a value greater than min((X-1)+N*X, X-1+bitmap limit). In this case, the previously mentioned details regarding N and the bitmap limit have been omitted.
[0241] Another explanation for the same content is that M can be (the maximum number of BSSIDs that a multiple BSSID set may contain) or (the number of BSSIDs in a multiple BSSID set). The value of the AID Offset subfield does not have to be set to the smaller of 1) the sum of M-1 and M*N, or 2) the sum of M-1 and N + bitmap limit. The value of the AID Offset subfield may be set to a value greater than the smaller of 1) the sum of M-1 and M*N, or 2) the sum of M-1 and N + bitmap limit. If the reporting AP does not belong to a multiple BSSID set, M may be 1.
[0242] Furthermore, the same content can be explained separately for cases where the reporting AP belongs to a multiple BSSID set and cases where it does not. When the reporting AP belongs to a multiple BSSID set, the value of the AID Offset subfield cannot be set to less than or equal to N. Also, the value of the AID Offset subfield may be set to a value greater than N. When the reporting AP belongs to a multiple BSSID set, the AID Offset does not need to be set to the smaller of the value obtained by adding N*(number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs) to (X-1) plus the bitmap limit (if both values are the same, either value). The value of the AID Offset subfield may be set to a value greater than the smaller of the following two values: (X-1) plus N*(number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs) plus (X-1) plus the bitmap limit (or either of the two values if both are the same). min(A,B) may be less than either A or B if A and B are different, and may be A=B if A and B are the same.
[0243] In the above embodiment, the number of nontransmitted BSSIDs or the number of BSSIDs in a multiple BSSID set may be the number of BSSIDs actually used in the multiple BSSID set. Also, the maximum number of nontransmitted BSSIDs or the maximum number of BSSIDs that a multiple BSSID set may contain may be the maximum number that a multiple BSSID set can contain based on the MaxBSSID Indicator value.
[0244] In the embodiments shown in Figures 19 and 20, the AID (association ID) space may be restricted (to non-AP stations or non-AP MLDs). This is because the AID range assigned to the group address frame is changed in the embodiments shown in Figures 19 and 20. The AID is assigned by the AP to the non-AP station (or non-AP multilink device). The AID may also be transmitted to the non-AP station (or non-AP multilink device) in a coupling response frame or a reconnection response frame.
[0245] Under the existing IEEE 802.11 standard, an AP could assign an AID value between 1 and 2007 to a non-AP station. However, if the AP belonged to a multiple BSSID set, it could not assign an AID value corresponding to a nontransmitted BSSID to the non-AP station. In other words, if the AP belonged to a multiple BSSID set, it could not assign an AID value equal to or less than the maximum number of BSSIDs in the multiple BSSID set minus 1 to the non-AP station. That is, the AP could assign an AID to a non-AP station within the range of (maximum number of BSSIDs in the multiple BSSID set) up to 2007.
[0246] Furthermore, the EHT standard may not allow an AP to assign 2007 as the non-AP station AID. This is because the AID value 2007 is used to indicate the Special User Info field included in the trigger frame. In other words, if the AP is not included in a multiple BSSID set, the AP can assign an AID to a non-AP station in the range of 1 to 2006. Also, when using a multiple BSSID set, the AP can assign an AID to a non-AP station in the range of (the maximum number of BSSIDs that the multiple BSSID set can include) to 2006.
[0247] Furthermore, according to embodiments of the present invention, the AID space may be restricted based on the value of the Group Addressed BU Indication Exponent field or a bitmap limit.
[0248] In a specific example, if the AP does not belong to a multiple BSSID set, the AP can assign AIDs to non-AP stations in the range of N+1 to 2006. If the AP belongs to a multiple BSSID set, the AP cannot assign an AID to a non-AP station up to the smaller of (X-1) plus N*((number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs)+1) plus (X-1) plus the bitmap limit (if both values are the same, either value). In other words, the AP can assign AIDs to non-AP stations in the range of 2006 from the smaller of (X-1) plus N*((number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs)+1) plus (X-1) plus the bitmap limit plus 1. Therefore, if an AP belongs to a multiple BSSID set, the AP can assign an AID to a non-AP station in the range of 2^(MaxBSSID Indicator)+(2^(MaxBSSID Indicator))*(2^(Value of the Group Addressed BU Indication Exponent subfield+1)-1) to 2006.
[0249] If the AP does not belong to a multiple BSSID set, the AID space may be determined based on the value of the Group Addressed BU Indication Exponent subfield. If the AP does belong to a multiple BSSID set, the AID space may be determined based on the value of the MaxBSSID Indicator subfield and the value of the Group Addressed BU Indication Exponent subfield.
[0250] The MaxBSSID Indicator subfield may be included in the Multiple BSSID element or the Reduced Neighbor Report element. The Multiple BSSID element or Reduced Neighbor Report element may be included in the beacon frame, probe response frame, coupled response frame, and recoupled response frame.
[0251] Figure 21 shows a Traffic indication virtual bitmap according to an embodiment of the present invention.
[0252] In yet another embodiment of the present invention, (X-1) may be replaced with (Y-1) in the embodiment described in Figures 19 and 20. Specifically, when adding the bitmap limit to (X-1), (X-1) may be replaced with (Y-1). The bitmap limit may be the number of the last bit that can indicate a group address frame among the bits corresponding to other APs belonging to the AP multilink device to which the AP corresponding to the transmitted BSSID belongs in the Traffic indication virtual bitmap. Also, in the embodiment described later, (Y-1) may be replaced with (X-1).
[0253] As mentioned above, the AP can extract a portion of the Traffic indication virtual bitmap to generate a Partial Virtual Bitmap subfield. Furthermore, each bit in the Traffic indication virtual bitmap or Partial Virtual Bitmap subfield can indicate whether traffic for the AID station has been buffered. The bit numbers of the bits in the Traffic indication virtual bitmap or Partial Virtual Bitmap subfield may be mapped to the AID. The first bit (B0) of the Traffic indication virtual bitmap or Partial Virtual Bitmap subfield may be mapped to the transmitted BSSID. In yet another specific embodiment, the first bit (B0) of the Traffic indication virtual bitmap or Partial Virtual Bitmap subfield may be mapped to the reporting AP. If the reporting AP belongs to a multiple BSSID set, the first bit (B0) of the Traffic indication virtual bitmap is mapped to the reporting AP or the transmitted BSSID. If the reporting AP does not belong to the multiple BSSID set, the first bit (B0) of the Traffic indication virtual bitmap is mapped to the reporting AP.
[0254] In the embodiment shown in Figure 21, the second bit (B1) to the fourth bit (B3) of the Traffic indication virtual bitmap may be mapped to a nontransmitted BSSID. In this case, the (X-1) value is 3. Also, the fifth bit (B4) to the seventh bit (B6) of the Traffic indication virtual bitmap may be mapped to other APs belonging to the AP multilink device to which the reporting AP or transmitted BSSID belongs. In this case, the value of the Group Addressed BU Indication Exponent subfield may be set to 1. In this case, N is 3.
[0255] In the embodiment shown in Figure 21, Y is 7, and N is 3. Therefore, bits 7+(k-1)*3 to 7+k*3-1 of the Traffic indication virtual bitmap indicate whether or not a group address frame corresponding to another AP in the AP multilink device to which the AP corresponding to the k-th nontransmitted BSSID belongs has been buffered. That is, bits 8 (B7) to 10 (B9) of the Traffic indication virtual bitmap can indicate whether or not a group address frame corresponding to another AP in the AP multilink device to which the AP corresponding to the first nontransmitted BSSID belongs has been buffered. Furthermore, the k-th nontransmitted BSSID may be the nontransmitted BSSID corresponding to AID k.
[0256] The Traffic indication virtual bitmap or Partial Virtual Bitmap subfield may include, as part of the group address frame, a portion corresponding to the reporting AP (or, if a multiple BSSID set is used, the transmitted BSSID), a portion corresponding to the nontransmitted BSSID (if a multiple BSSID set is used), a portion corresponding to other APs belonging to the AP multilink device to which the reporting AP belongs, and a portion corresponding to other APs belonging to the AP multilink device to which the nontransmitted BSSID AP belongs (if a multiple BSSID set is used). Furthermore, the order in which each portion is included in the Traffic indication virtual bitmap may be the same as the order mentioned above.
[0257] In a specific embodiment, the AID space may be the same as the range of AIDs that the AID Offset subfield can indicate. Also, the range that AP cannot assign as an AID may be the same as the range of AIDs that the AID Offset subfield cannot indicate. Furthermore, the AID space may be a set of bit numbers of bits that do not indicate that a group address frame has been buffered in the Traffic indication virtual bitmap. That is, the AID space does not have to include bit numbers of bits that indicate that a group address frame has been buffered in the Traffic indication virtual bitmap. AIDs that AP cannot assign as an AID may be a set of bit numbers of bits that indicate that a group address frame has been buffered in the Traffic indication virtual bitmap.
[0258] In a first embodiment of the AID space of the present invention, the AID space may be determined based on X or X-1. The AID space may be determined based on the maximum number of nontransmitted BSSIDs. Therefore, the AID space may be determined based on the Group Addressed BU Indication Exponent subfield. Specifically, the AID space may be determined based on the value obtained by adding N*((number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs)+1) to (X-1). For example, the minimum value of the AID space may be (X-1) + N*((number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs)+1)+1. The maximum value of the AID space may be 2006. (X-1) may be the bit number of the last bit used to indicate a nontransmitted BSSID in a TIM element, Partial Virtual Bitmap subfield, or Traffic indication virtual bitmap. If the reporting AP does not belong to a multiple BSSID set, X-1 is 0. If the reporting AP belongs to a multiple BSSID set, (X-1) is (2^(MaxBSSID Indicator value)-1). The MaxBSSID Indicator value can indicate the maximum number of BSSIDs in a multiple BSSID set. The maximum number of BSSIDs in a multiple BSSID set is 2^(MaxBSSID Indicator value).
[0259] In other specific embodiments, the minimum value of the AID space may be (X-1) plus N*X+1. If the reporting AP does not belong to a multiple BSSID set, the minimum value of the AID space may be N+1. If the reporting AP belongs to a multiple BSSID set, the minimum value of the AID space may be (X-1) plus N*((number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs)+1)+1. That is, if the AP belongs to a multiple BSSID set, the minimum value of the AID space may be (2^(MaxBSSID Indicator value)-1)+(2^(MaxBSSID Indicator value))*(2^(Group Addressed BU Indication Exponent subfield value+1)-1)+1. If the AP belongs to a multiple BSSID set, the minimum value of the AID space may be 2^((MaxBSSID Indicator value)+(Group Addressed BU Indication Exponent subfield value+1)).
[0260] In a second embodiment of the AID space of the present invention, the AID space may be determined based on a bitmap limit. In this case, the bitmap limit may be 48 bits. The AID space may be determined based on Y and the bitmap limit. Specifically, the AID space may be determined based on Y-1 and the bitmap limit. Specifically, the AID space may be determined based on the sum of Y-1 and the bitmap limit. In a specific embodiment, the minimum value of the AID space may be the value obtained by adding 1 to the value obtained by adding the bitmap limit value to (Y-1).
[0261] As mentioned above, Y may be replaced with X. Therefore, the AID space may be determined based on X and the bitmap limit. Specifically, the AID space may be determined based on X-1 and the bitmap limit. Specifically, the AID space may be determined based on the sum of X-1 and the bitmap limit. In a specific embodiment, the minimum value of the AID space may be the value obtained by adding 1 to (X-1) plus the bitmap limit.
[0262] (Y-1) may be the last bit in the Traffic indication virtual bitmap that indicates the group address frame of the AP multilink device to which the AP corresponding to the transmitted BSSID belongs. That is, Y-1 may be the same value as X+N-1. Also, N is the N explained earlier in the EHT Operation element related embodiment. N may be determined based on the value of the Group Addressed BU Indication Exponent subfield. N may be 2^(value of the Group Addressed BU Indication Exponent subfield+1)-1. N may be the number of bits that indicate the group address frame for one multilink device in the Traffic indication virtual bitmap minus 1. Alternatively, N may be the number of bits that indicate the group address frame corresponding to other APs in the multilink device to which the AP corresponding to the reporting AP, transmitted BSSID, or nontransmitted BSSID belongs. If the reporting AP does not belong to the multiple BSSID set, Y-1 may be N. If the reporting AP belongs to a multiple BSSID set, Y-1 may be X-1 + N. That is, if the reporting AP belongs to a multiple BSSID set, Y-1 may be ((maximum number of BSSIDs in the multiple BSSID set)-1)+N.
[0263] An AP is not permitted to assign AIDs to non-AP stations or non-AP multilink devices that correspond to only the bits beyond bit number (Y-1) in the Traffic indication virtual bitmap. In other words, an AP can assign a value greater than (Y-1) + (bitmap limit) to a non-AP station or non-AP multilink device. That is, in the embodiment shown in Figure 20, an AP can assign a value greater than 6 + 48, which is 55 or greater, to the AID of a non-AP station or non-AP multilink device.
[0264] When the bit limit is 48, if the reporting AP does not belong to a multiple BSSID set, the AID value that the reporting AP can assign may be (N+1) or greater. Also, if the AP belongs to a multiple BSSID set, the AID value that the AP can assign may be (Y+48) or greater.
[0265] In a third embodiment of the AID space of the present invention, the AID space may be determined based on the first and second embodiments. The AID space may be determined based on X, N, Y, the number of nontransmitted BSSIDs (or the maximum number of nontransmitted BSSIDs), and the bitmap limit. The minimum value of the AID space may be the smaller of (X-1) plus N*((number of nontransmitted BSSIDs or maximum number of nontransmitted BSSIDs)+1) and (Y-1) plus the bitmap limit, plus 1. The minimum value of the AID space may be min((X-1)+N*X, Y-1+bitmap limit)+1. That is, the minimum value of the AID space may be min(X+N*X, Y+bitmap limit).
[0266] When the reporting AP does not belong to a multiple BSSID set, the minimum value of the AID space may be N+1. When the reporting AP belongs to a multiple BSSID set, the minimum value of the AID space may be the smaller one of N+1 and Y+bitmap limit. When the reporting AP belongs to a multiple BSSID set, the minimum value of the AID space may be a value obtained by adding 1 to the smaller one of a value obtained by adding N*(the number of nontransmitted BSSIDs or the maximum number of nontransmitted BSSIDs +1) to (X-1), and a value obtained by adding the bitmap limit to (Y-1). That is, when the reporting AP belongs to a multiple BSSID set, the minimum value of the AID space may be min(X+N*X, Y+bitmap limit). This may be expressed as follows. When the reporting AP belongs to a multiple BSSID set, the minimum value of the AID space may be min((a), (b)).
[0267] (a)(2^(MaxBSSID Indicator value)-1)+(2^(MaxBSSID Indicator value))*(2^(value of Group Addressed BU Indication Exponent subfield+1)-1)+1
[0268] (b)(Y-1)+(bitmap limit)+1=2^(MaxBSSID Indicator value)-1+2^(value of Group Addressed BU Indication Exponent subfield+1)-1+(bitmap limit)+1=2^(MaxBSSID Indicator value)+2^(value of Group Addressed BU Indication Exponent subfield+1)-1+(bitmap limit)
[0269] When the bitmap limit is 48 and the reporting AP does not belong to a multiple BSSID set, the minimum value of the AID space is N+1. When the bitmap limit is 48 and the reporting AP belongs to a multiple BSSID set, the minimum value of the AID space may be min(Y+48, Y+N*(the number of nontransmitted BSSIDs or the maximum number of nontransmitted BSSIDs)).
[0270] When the reporting AP does not belong to a multiple BSSID set, 0 can be applied to the value of the MaxBSSID Indicator and 0 can be applied to the number of nontransmitted BSSIDs or the maximum number of nontransmitted BSSIDs in the formula applied when the reporting AP belongs to a multiple BSSID set. In the previous embodiment, the number of nontransmitted BSSIDs or the number of BSSIDs in the multiple BSSID set may indicate the number of BSSIDs actually used in the multiple BSSID set. In addition, the maximum number of nontransmitted BSSIDs or the maximum number of BSSIDs that the multiple BSSID set may have may be determined based on the MaxBSSID Indicator value. A non-AP station can obtain the number of Nontransmitted BSSIDs from the Multiple BSSID element. In still another specific embodiment, the non-AP station can obtain the number of nontransmitted BSSIDs from an element or frame that indicates the maximum number of BSSIDs in the multiple BSSID set.
[0271] Further, the bitmap limit may be a pre-specified value. For example, the bitmap limit may be 48.
[0272] In the embodiments described above, multiple BSSIDs or sets of multiple BSSIDs may be replaced with co-located BSSIDs or sets of co-located BSSIDs (co-located BSSID lists). Co-located BSSIDs may be BSSIDs of BSSs that have the same physical location as the reporting BSS or reporting AP. Co-located BSSIDs may be BSSIDs that correspond to the same physical device as the reporting BSS or reporting AP.
[0273] In the first embodiment of the AID space of the present invention, when the number of BSSIDs in the multiple BSSID set is small or N is small, there is an advantage that the number of bits indicating the group address frame in the Traffic indication virtual bitmap is small, resulting in a wide AID space. However, when the number of BSSIDs in the multiple BSSID set is large or N is large, there is a disadvantage that the number of bits indicating the group address frame in the Traffic indication virtual bitmap increases, resulting in a narrow AID space. A wide or narrow AID space means that the number of connectable stations or multilink devices is large or small. Furthermore, the first embodiment of the AID space of the present invention may have the advantage of being simpler to calculate or implement compared to the third embodiment of the AID space of the present invention.
[0274] In the second embodiment of the AID space of the present invention, even when the number of BSSIDs in the multiple BSSID set is large or N is large, the number of bits used to indicate the group address frame in the Traffic indication virtual bitmap is limited, which has the advantage of a wide AID space. On the other hand, even when the number of BSSIDs in the multiple BSSID set is small or N is small, the AID space may be limited to some extent, which is a disadvantage. Therefore, there may be AID values that are neither used as AIDs nor used to indicate the group address frame. Furthermore, the second embodiment of the AID space of the present invention has the advantage of being simpler to calculate or implement compared to the third embodiment of the AID space of the present invention.
[0275] A third embodiment of the AID space of the present invention may have the advantage of combining the advantages of the first and second embodiments and reducing their disadvantages. However, a third embodiment of the AID space of the present invention may have the disadvantage of being more complex to calculate or implement compared to the first or second embodiment.
[0276] Figures 22 to 26 will be used to explain how to configure multi-link. First, Figure 22 will be used to explain the Multi-Link element.
[0277] Figure 22 shows signaling related to a Multi-Link element and MediumSyncDelay according to one embodiment of the present invention.
[0278] A multilink device can perform multilink discovery and multilink setup using multilink elements. In this case, the multilink elements may be included in the management frame. Specifically, the multilink elements may be included in at least one of the following: a beacon frame, a probe request frame, a probe response frame, an authentication frame, a coupling request frame, a coupling response frame, a recouping request frame, and a recouping response frame.
[0279] A Multi-Link element may include an Element ID subfield, a Length subfield, an Element ID Extension subfield, a Multi-Link Control subfield, a Common Info subfield, and a Link Info subfield. The Element ID subfield or Element ID Extension subfield can indicate the ID of the element containing the Element ID subfield or the Element ID Extension subfield. The Length subfield can indicate the length of the element containing the Length subfield. The Multi-Link Control subfield may include a Type subfield and a Presence Bitmap subfield. The Type subfield can indicate the type of the Multi-Link element. The format of the Multi-Link element may also be determined based on the type of the Multi-Link element. The Presence Bitmap subfield can indicate whether any subfields that may be included in the Multi-Link element are included. For example, the Presence Bitmap subfield can indicate whether any subfields that may be included in the Common Info subfield included in the Multi-Link element are included. The Presence Bitmap subfield, which indicates whether or not it is included in the Multi-Link element, may include the MAC address subfield of the multi-link device, the Link ID Info subfield, the BSS Parameters Change Count subfield, the Medium Synchronization Delay Information subfield, the EML Capabilities subfield, and the MLD Capabilities subfield. The Medium Synchronization Delay Information subfield may also include MediumSyncDelay and related information.
[0280] The Common Info subfield may contain information about multiple links or all links. The Common Info subfield may contain information that is commonly required or applicable to multiple links or all links. The Link Info subfield may contain information about the link to which the Link Info subfield pertains.
[0281] Information related to MediumSyncDelay indicates the value to be set as the duration of MediumSyncDelay and may have a default value. Under certain circumstances, a multilink device can initialize the duration of MediumSyncDelay to its default value. Also, if a multilink device (non-AP multilink device) fails to receive information related to MediumSyncDelay from a peer multilink device (AP multilink device), the multilink device can set the duration of MediumSyncDelay to its default value. If a multilink device (non-AP multilink device) receives information related to MediumSyncDelay from a peer multilink device (AP multilink device), it can set the duration of MediumSyncDelay to the value indicated by the received information related to MediumSyncDelay.
[0282] In Figure 22, the Medium Synchronization Delay Information subfield may include the Medium Synchronization Duration subfield, the Medium Synchronization OFDM ED Threshold subfield, and the Medium Synchronization Maximum Number Of TXOPs subfield.
[0283] The Medium Synchronization Duration subfield can specify the MediumSyncDelay. That is, the Medium Synchronization Duration subfield can specify a value to set the MediumSyncDelay timer. For example, the Medium Synchronization Duration subfield may be an 8-bit field. Also, the Medium Synchronization Duration subfield can specify the duration in units of 32us. That is, if the Medium Synchronization Duration subfield is set to A, the time specified by the Medium Synchronization Duration subfield may be A * 32us.
[0284] The Medium Synchronization OFDM ED Threshold subfield can specify a CCA threshold when MediumSyncDelay is applied. The CCA threshold specified by the Medium Synchronization OFDM ED Threshold subfield may be a CCA ED threshold. That is, the Medium Synchronization OFDM ED Threshold subfield can specify dot11MSDOFDMEDthreshold. The Medium Synchronization OFDM ED Threshold subfield may be a 4-bit field. The CCA threshold specified by the Medium Synchronization OFDM ED Threshold subfield is the value of the Medium Synchronization OFDM ED Threshold subfield plus -72, and the unit of the CCA threshold may be dBm. Therefore, when the value of the Medium Synchronization OFDM ED Threshold subfield is 0 or greater, the CCA threshold specified by the Medium Synchronization OFDM ED Threshold subfield may be a value of -72 dBm or greater. Furthermore, the maximum value of the CCA threshold indicated by the Medium Synchronization OFDM ED Threshold subfield may be -62 dBm. In this case, the value of the Medium Synchronization OFDM ED Threshold subfield may be set in the range of 0 to 10. At this time, values from 11 to 15 may be reserved for the Medium Synchronization OFDM ED Threshold subfield. That is, when the value of the Medium Synchronization OFDM ED Threshold subfield is set to 0 to 10, the Medium Synchronization OFDM ED Threshold subfield can indicate that the CCA threshold is between -72 dBm and -62 dBm.In other words, if the value of the Medium Synchronization OFDM ED Threshold subfield is x, then the Medium Synchronization OFDM ED Threshold subfield indicates that the CCA threshold is (x-72 dBM).
[0285] The Medium Synchronization Maximum Number Of TXOPs subfield can indicate MSD_TXOP_MAX, that is, the maximum number of transmission attempts a station may attempt while MediumSyncDelay is applied. The Medium Synchronization Maximum Number Of TXOPs subfield may be a 4-bit field. In a specific embodiment, the value of the Medium Synchronization Maximum Number Of TXOPs subfield may be MSD_TXOP_MAX. In yet another specific embodiment, the value of the Medium Synchronization Maximum Number Of TXOPs subfield may be (MSD_TXOP_MAX+1). In yet another specific embodiment, the value of the Medium Synchronization Maximum Number Of TXOPs subfield may be (MSD_TXOP_MAX-1). Such embodiments may apply when the value of the Medium Synchronization Maximum Number Of TXOPs subfield is not set to the maximum value. If the value of the Medium Synchronization Maximum Number Of TXOPs subfield is set to the maximum value, for example, 15 if the Medium Synchronization Maximum Number Of TXOPs subfield is a 4-bit field, then the Medium Synchronization Maximum Number Of TXOPs subfield can indicate that the station is allowed to attempt transmission without limit on the number of transmission attempts while MediumSyncDelay is applied.
[0286] Figure 23 shows the multilink setup process according to an embodiment of the present invention.
[0287] In Figure 23, the AP multilink device includes a first AP (AP1), a second AP (AP2), and a third AP (AP3). The non-AP multilink device (non-AP MLD) includes a first non-AP station (STA1), a second non-AP station (STA2), and a third non-AP station (STA3). The first AP (AP1) and the first non-AP station (STA1) operate on the first link (link1). The second AP (AP2) and the second non-AP station (STA2) operate on the second link (link2). The third AP (AP3) operates on the third link (link3).
[0288] The first AP (AP1) can transmit a Reduced Neighbor Report element to signal the presence of an AP Multilink Device (AP MLD) and AP MLD-related parameters. The Reduced Neighbor Report element transmitted by the first AP (AP1) may include information about the second AP (AP2) or the third AP (AP3). The Reduced Neighbor Report element may be included in a beacon frame or a probe response frame.
[0289] Furthermore, a first non-AP station (STA1) that receives a frame containing a Reduced Neighbor Report element can recognize the AP or AP multilink device indicated by the Reduced Neighbor Report element. At this time, the first non-AP station (STA1) can send a probe request frame containing a Multi-Link element to the first AP (AP1) to request the first AP (AP1) for information regarding the AP multilink device (AP MLD) or the multilink on which the AP multilink device (AP MLD) operates. At this time, the Multi-Link element may include information regarding the non-AP multilink device, or information regarding the AP included in the non-AP multilink device.
[0290] The first AP (AP1) may transmit a probe response frame to a non-AP station (STA1) as a response to a probe request frame. At this time, the probe response frame may include a Multi-Link element. The Multi-Link element may include information related to the AP multi-link device or information related to APs included in the AP multi-link device (AP MLD). Specifically, the Multi-Link element may include information requested by the first non-AP station (STA1).
[0291] The first non-AP station (STA1) may transmit an association request frame or a re-association request frame to the first AP (AP1). The association request frame and the re-association request frame may include a Multi-Link element. At this time, the Multi-Link element may include information related to links for which the non-AP multi-link device intends to perform multi-link setup. For example, in Figure 22, the Multi-Link element may include information related to the first link (link1) and the second link (link2).
[0292] The first AP (AP1) may transmit an association response frame or a re-association response frame to the first non-AP station (STA1). At this time, the association response frame and the re-association response frame may include a Multi-Link element. At this time, the Multi-Link element may include information related to links on which multi-link setup is performed. The links on which multi-link setup is performed may be determined based on the links for which the non-AP multi-link device intends to perform multi-link setup. In Figure 22, the Multi-Link element may include information related to the first link (link1) and the second link (link2) for which the first non-AP station (STA1) intends to perform multi-link setup.
[0293] If a combined response frame or a recombined response frame is successfully transmitted, the multilink configuration for the link indicated by the Multi-Link element included in the combined response frame or recombined response frame may be considered successful.
[0294] Figure 24 shows the format of a Reduced Neighbor Report element according to an embodiment of the present invention.
[0295] This explanation will be provided in addition to the Reduced Neighbor Report element described in Figure 23.
[0296] A station or AP that transmits an element is referred to as a reporting station or reporting AP. A station or AP that an element directs is referred to as a reported station or reported AP. A station or AP that transmits a Reduced Neighbor Report element or a Multi-Link element is referred to as a reporting station or reporting AP. A station or AP that a Reduced Neighbor Report element or a Multi-Link element directs is referred to as a reported station or reported AP.
[0297] Referring to Figure 24(a), a Reduced Neighbor Report element may include an Element ID subfield, a Length subfield, and one or more Neighbor AP Information subfields. The Element ID subfield can indicate the ID of the element. The Element ID subfield of a Reduced Neighbor Report element can indicate the ID of the Reduced Neighbor Report element. The Length subfield can indicate the size of the Reduced Neighbor Report element. For example, the Length subfield can indicate the length of the Reduced Neighbor Report element excluding the Element ID subfield and the Length subfield. That is, in the embodiment of Figure 24(a), the Length subfield can indicate the length of the Neighbor AP Information subfield.
[0298] Each of the one or more Neighbor AP Information fields included in the Reduced Neighbor Report element may be identical to the Neighbor AP Information subfields shown in Figure 24(b). The Neighbor AP Information subfields may include the TBTT Information Header subfield, the Operating Class subfield, the Channel Number subfield, and the TBTT Information Set subfield.
[0299] The TBTT Information Header subfield may be a 2-octet field. The format of the TBTT Information Header subfield may also be the same as that shown in Figure 24(c). The TBTT Information Header subfield may include the TBTT Information Field Type subfield, the Filtered Neighbor AP subfield, the Reserved subfield, the TBTT Information Count subfield, and the TBTT Information Length subfield. The TBTT Information Field Type subfield may be a 2-bit field, the Filtered Neighbor AP subfield a 1-bit field, the Reserved subfield a 1-bit field, the TBTT Information Count subfield a 4-bit field, and the TBTT Information Length subfield an 8-bit field.
[0300] The TBTT Information Field Type subfield, along with the TBTT Information Length subfield, identifies the TBTT Information subfield. The value of the TBTT Information Field Type subfield is set to 0, and values 1, 2, and 3 of the TBTT Information Field Type subfield may be reserved values.
[0301] The Filtered Neighbor AP subfield is set as a reserved field except when the Reduced Neighbor Report element is carried in a Probe Response frame transmitted by a TVHT AP. The Filtered Neighbor AP subfield may be set to 1 if the Filtered Neighbor AP subfield is included in the probe response frame transmitted by the TVHT AP and all BSSs of APs within the Filtered Neighbor AP subfield correspond to a specific SSID. Otherwise, the Filtered Neighbor AP subfield may be set to 0.
[0302] The TBTT Information Count subfield can indicate the number of TBTT Information subfields contained within the Neighbor AP Information subfield that contains the TBTT Information Count subfield. For example, the TBTT Information Count subfield may be set to a value obtained by subtracting 1 from the number of TBTT Information subfields contained within the Neighbor AP Information subfield that contains the TBTT Information Count subfield.
[0303] The TBTT Information Length subfield can specify the length of each TBTT Information subfield contained within the Neighbor AP Information subfield that contains the TBTT Information Length subfield. Furthermore, the TBTT Information Length subfield can specify the composition of each TBTT Information subfield contained within the Neighbor AP Information subfield that contains the TBTT Information Length subfield. In this case, the TBTT Information Length subfield can specify both the length and composition of each TBTT Information subfield.
[0304] The TBTT Information Set subfield may contain one or more TBTT Information subfields.
[0305] The TBTT Information subfield may be identical to that shown in Figure 24(d). The TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, BSSID subfield, Short SSID subfield, BSS Parameters subfield, 20MHz PSD subfield, and MLD Parameters subfield. The size of each subfield may be identical to that shown in Figure 24(d). In this case, the subfields included in the TBTT Information subfield may be selectively included.
[0306] The Neighbor AP TBTT Offset subfield can specify an offset that rounds down the interval between the previous TBTT and the next TBTT for an AP sending a Reduced Neighbor Report element to the nearest TU. A value of 254 in the Neighbor AP TBTT Offset subfield indicates that the offset is 254 TU or greater. A value of 255 in the Neighbor AP TBTT Offset subfield indicates that the offset value is unknown.
[0307] The BSSID subfield can indicate the BSSID.
[0308] The Short SSID subfield can specify the SSID. Specifically, the Short SSID subfield can specify abbreviated SSID information.
[0309] The BSS Parameters subfield can indicate information about the BSS. This information may include information about BSS operation.
[0310] The 20MHz PSD subfield can indicate the maximum transmit power for the default category on the 20MHz main channel. In this case, the 20MHz PSD subfield can indicate the maximum transmit power in dBm / MHz units. The value of the 20MHz PSD subfield is a signed integer, and a value of -128 is a reserved value. A value of 127 indicates that there is no limit to the maximum transmit power for the default category. Also, when the value of the 20MHz PSD subfield, Y, is in the range of -127 to 126, the 20MHz PSD subfield can indicate that the maximum transmit power for the default category on the 20MHz main channel is Y / 2dBM / MHz.
[0311] The TBTT Information field configuration indicated by the value of the TBTT Information Length subfield may be as follows: If the value of the TBTT Information Length subfield is 1, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield. If the value of the TBTT Information Length subfield is 2, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield and the BSS Parameters subfield. If the value of the TBTT Information Length subfield is 4, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield and the MLD Parameters subfield. If the value of the TBTT Information Length subfield is 5, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield and the Short SSID subfield. If the value of the TBTT Information Length subfield is 6, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, the Short SSID subfield, and the BSS Parameters subfield. If the value of the TBTT Information Length subfield is 7, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield and the BSSID subfield. If the value of the TBTT Information Length subfield is 8, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, the BSSID subfield, and the BSS Parameters subfield.If the value of the TBTT Information Length subfield is 9, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, the BSSID subfield, the BSS Parameters subfield, and the 20MHz PSD subfield. If the value of the TBTT Information Length subfield is 10, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, the BSSID subfield, and the MLD Parameter subfield. If the value of the TBTT Information Length subfield is 11, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, the BSSID subfield, and the Short SSID subfield. If the value of the TBTT Information Length subfield is 12, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, the BSSID subfield, the Short SSID subfield, and the BSS Parameters subfield. If the value of the TBTT Information Length subfield is 13, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, the BSSID subfield, the Short SSID subfield, the BSS Parameters subfield, and the 20MHz PSD subfield. If the value of the TBTT Information Length subfield is 16, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, the BSSID subfield, the Short SSID subfield, the BSS Parameters subfield, the 20MHz PSD subfield, and the MLD Parameters subfield.If the value of the TBTT Information Length subfield is 17 or greater, the TBTT Information subfield may include the Neighbor AP TBTT Offset subfield, BSSID subfield, Short SSID subfield, BSS Parameters subfield, 20MHz PSD subfield, and MLD Parameters subfield in the preceding 16 octets. Any remaining subfields of the TBTT Information subfield not mentioned above may be designated as reserved. That is, if the TBTT Information Length subfield is 4, 10, 16, or 17 or greater, it may include the MLD Parameters subfield.
[0312] The MLD Parameter subfield may be as shown in Figure 24(e). The MLD Parameter subfield may include the MLD ID subfield, Link ID subfield, BSS Parameter Change Count subfield, and Reserved subfield. The MLD ID subfield may be an 8-bit field. The Link ID subfield may be a 4-bit field. The BSS Parameter Change Count subfield may be an 8-bit field. The Reserved subfield may be a 4-bit field.
[0313] The MLD ID subfield can specify the ID of a multilink device, such as an AP multilink device. The MLD subfield can specify the ID of the multilink device corresponding to the TBTT Information subfield, which includes the MLD ID subfield. The specific method for setting the MLD ID subfield is as shown in Figure 25.
[0314] The Link ID subfield can specify the ID of the link corresponding to the reported AP. If the reported AP does not belong to a multilink device or the reporting AP does not have relevant information, the link ID may be set to 15.
[0315] The BSS Parameters Change Count subfield can be configured to increment when a significant update occurs in the beacon frame of a reported AP. The value of the BSS Parameters Change Count subfield may be initialized to 0. The value of the BSS Parameters Change Count subfield may increment by 1 each time a significant update occurs in the AP or BSS to which the BSS Parameters Change Count subfield belongs. A significant update may include an update to a pre-specified parameter. The pre-specified parameter may include an operation parameter. If the reported AP does not belong to a multilink device or the reporting AP does not have information about the multilink device to which the reported AP belongs, the value of the BSS Parameters Change Count subfield may be set to 255.
[0316] Figure 25 shows a method for setting the ID of a multilink device according to an embodiment of the present invention.
[0317] The ID of the multilink device may be a value indicated by the MLD ID subfield described in Figure 24. The MLD ID subfield may be 8 bits. The MLD ID subfield can represent a value from 0 to 255. In embodiments of the present invention, a reporting AP may represent an AP that sets and transmits the MLD ID subfield. A reported AP may represent an AP indicated by the MLD ID subfield or a TBTT Information subfield containing the MLD ID subfield.
[0318] According to embodiments of the present invention, the MLD ID subfield may be set as follows: The MLD ID subfield can indicate the ID of the AP multilink device to which the reported AP belongs. If the reported AP belongs to the AP multilink device to which the reporting AP belongs, the MLD ID subfield may be set to 0. If the reported AP belongs to the multilink device set to which a nontransmitted BSSID belonging to a multiple BSSID set belongs, the value of the MLD ID subfield may be set to the same value as the BSSID Index field of the Multiple BSSID-Index element of the nontransmitted BSSID propyl corresponding to the nontransmitted BSSID. If the reported AP is part of another AP multilink device and the frame containing the MLD ID subfield does not contain a Multiple BSSID element, the value of the MLD ID subfield may be set to a value greater than 0 and less than 255. Furthermore, if the reported AP is part of another AP multilink device and the frame containing the MLD ID subfield contains a Multiple BSSID element, the value of the MLD ID subfield may be set to a value greater than 2^n-1 and less than 255. In this case, n is the value of the MaxBSSID Indicator subfield of the Multiple BSSID element. If the reported AP is not part of a multilink device, or if the reporting AP has no information about the reported AP's multilink device, the value of the MLD ID subfield may be set to 255. That is, if the reported AP belongs to the same multilink device as the reporting AP, the value of the MLD ID subfield may be set to 0. Specifically, if the reported AP is not part of a multilink device, or if the reporting AP has no information about whether the reported AP belongs to a multilink device, the value of the MLD ID subfield may be set to 255. That is, if the reported AP belongs to the same multilink device as the reporting AP, the value of the MLD ID subfield may be set to 0.
[0319] In the embodiment shown in Figure 25, the reporting AP operates on the first link (link1). The reporting AP belongs to the first multilink device and transmits the Reduced Neighbor Report element and the MLD ID subfield. The first multilink device (MLD 1) operates on the first link (link1), the second link (link2), and the third link (link3). In this case, the reporting AP sets the value of the MLD ID subfield corresponding to the AP operating on the second link (link2) and the third link (link3) to 0.
[0320] Furthermore, the reporting AP can send multiple BSSID elements along with the Reduced Neighbor Report element. In other specific embodiments, the reporting AP does not need to send multiple BSSID elements. In this case, if the reporting AP does send multiple BSSID elements, it may be because the reporting AP belongs to a multiple BSSID set. Conversely, if the reporting AP does not send multiple BSSID elements, it may be because the reporting AP does not belong to a multiple BSSID set.
[0321] According to embodiments of the present invention, when a reported AP is included in a multiple BSSID set to which a reporting AP belongs, the value of the MLD ID subfield may be set to the BSSID index of the multiple BSSID set. Also, when a reported AP belongs to a multilink device to which an AP belonging to the multiple BSSID set to which a reporting AP belongs belongs, the value of the MLD ID subfield may be set to the BSSID index of the AP belonging to that multiple BSSID set. When a reported AP belongs to a multilink device to which an AP with a nontransmitted BSSID belonging to the multiple BSSID set to which a reported AP belongs belongs, the value of the MLD ID subfield may be set to the BSSID index of the reported AP.
[0322] The multiple BSSID set to which the reporting AP belongs may include APs that operate on the first link (link1) and belong to the second multilink device (MLD2). The second multilink device (MLD2) may include APs that operate on the first link (link1) and APs that operate on the second link (link2). The reporting AP can set the value of the MLD ID subfield corresponding to the AP operating on the first link (link1) and the AP operating on the second link (link2) of the second multilink device (MLD2) to the BSSID index of the reported AP. This is because the AP of the second multilink device (MLD2) operating on the first link (link1) and the AP of the second multilink device (MLD2) operating on the second link (link2) belong to the same multiple BSSID set as the reporting AP or belong to a multilink device included in the multiple BSSID set to which the reporting AP belongs.
[0323] When a reporting AP transmits a multiple BSSID element, if the reported AP does not belong to the multilink device to which the reporting AP belongs, does not belong to the multiple BSSID set to which the reporting AP belongs, and does not belong to the multilink device to which the APs in the multiple BSSID set to which the reporting AP belongs belong, the value of the MLD ID subfield may be set to a value greater than (2^n-1) and less than a pre-specified value.
[0324] Furthermore, when a reporting AP transmits a multiple BSSID element, if the reported AP does not belong to the multilink device to which the reporting AP belongs, does not belong to the multiple BSSID set to which the reporting AP belongs, and does not belong to the multilink device to which the APs in the multiple BSSID set to which the reporting AP belongs belong, the value of the MLD ID subfield may be set to a value greater than (2^n-1) and less than a pre-specified value. This may also be limited to cases where the reported AP belongs to the MLD. The previously set value may be the maximum value that the MLD ID subfield can represent. The previously set value may be 255. Also, n may be the MaxBSSID Indicator value corresponding to the multiple BSSID set to which the reporting AP is included.
[0325] In Figure 25, the third multilink device (MLD3) may include an AP operating on the first link (link1) and an AP operating on the second link (link2). Furthermore, an AP belonging to the third multilink device (MLD3) and operating on the first link (link1) does not have to belong to the multiple BSSID set to which the reporting AP belongs. In this case, the value of the MLD ID subfield for the AP belonging to the third multilink device (MLD3) and operating on the first link (link1), and the AP belonging to the third multilink device (MLD3) and operating on the second link (link2), may be set to a value greater than 2^n-1 and less than 255. This is because the AP belonging to the third multilink device (MLD3) and operating on the first link (link1), and the AP belonging to the third multilink device (MLD3) and operating on the second link (link2), do not belong to the multilink device to which the reporting AP belongs, and these two APs are not included in the multilink device to which the APs of the multiple BSSID set to which the reporting AP belongs belong.
[0326] If the reporting AP does not transmit multiple BSSID elements, and the reported AP does not belong to the multilink device to which the reporting AP belongs, the value of the MLD ID subfield may be set to a value greater than 0 and less than a pre-specified value. This may also apply only if the reported AP belongs to a multilink device. The pre-specified value may be the maximum value that the MLD ID subfield can represent. The pre-specified value may be 255.
[0327] Furthermore, if 1) the reported AP does not belong to a multilink device, 2) the reporting AP does not have information regarding whether the reported AP belongs to a multilink device, or 3) the reporting AP does not have information to set the value of the MLD ID subfield mentioned above, the reporting AP may set the value of the MLD ID subfield to a predetermined value. In yet another specific embodiment, if 1) the reported AP does not belong to a multilink device, 2) the reporting AP does not have information regarding whether the reported AP belongs to a multilink device, or 3) the reporting AP does not have information to set the value of the MLD ID subfield mentioned above, the reporting AP may set the value of the MLD ID subfield to a value greater than or equal to a predetermined value. The predetermined value may be the maximum value that the MLD ID subfield can represent. The predetermined value may be 255.
[0328] In Figure 25, the fourth AP (AP4) operates on the first link (link1). In this case, the fourth AP (AP4) does not belong to any multilink device. Therefore, the reporting AP can set the value of the MLD ID subfield corresponding to the fourth AP (AP4) to 255.
[0329] A station can determine which BSS a frame was sent from based on the MAC address field in the MAC header of the received frame. Specifically, a station can determine, based on the MAC address field in the MAC header of the received frame, whether the received frame was sent from an AP to which the station is connected or from an AP belonging to the multiple BSSID to which the connected AP belongs. In a specific example, a station can determine, based on the TA field in the MAC header of the received frame, whether the received frame was sent from an AP to which the station is connected or from an AP belonging to the multiple BSSID to which the connected AP belongs. In this case, if the TA field of the frame received by the station indicates the MAC address of the AP to which the station is connected or the MAC address of an AP belonging to the multiple BSSID set to which the connected AP belongs, the station can determine that the received frame was sent from an AP to which the station is connected or from an AP belonging to the multiple BSSID set to which the connected AP belongs. If the TA field of a frame received by a station does not indicate the MAC address of the AP to which the station is connected, or the MAC addresses of the APs belonging to the multiple BSSID set to which the AP to which the station is connected belong, the station can determine that the received frame was sent from the AP to which the station is connected and the APs belonging to the multiple BSSID set to which the AP to which the station is connected belong.
[0330] A station can determine to which AP a frame is to be sent based on the MAC address field in the MAC header of the received frame. In a specific example, a station can determine to which AP a received frame is to be sent based on the RA field in the MAC header of the received frame. In this case, if the RA field of the frame received by the station indicates the MAC address of the AP to which the station is connected or the MAC address of an AP belonging to the multiple BSSID set to which the AP to which the station is connected belongs, the station can determine that the received frame was sent to the AP to which the station is connected or to an AP belonging to the multiple BSSID set to which the AP to which the station is connected belongs. If the RA field of the frame received by the station does not indicate the MAC address of the AP to which the station is connected or the MAC address of an AP belonging to the multiple BSSID set to which the AP to which the station is connected belongs, the station can determine that the received frame was sent to the AP to which the station is connected and to an AP belonging to the multiple BSSID set to which the AP to which the AP to which the station is connected belongs.
[0331] A station can determine if a frame is an Inter-BSS frame based on the MAC address field in the MAC header of the received frame. The MAC address field may contain at least one of the RA field, TA field, and BSSID field. A station can determine a received frame is an Inter-BSS frame if none of the RA field, TA field, and BSSID field of the frame received by the station indicate the MAC address of the AP to which the station is connected or the MAC address of an AP belonging to the multiple BSSID set to which the AP to which the station is connected belongs. A station can determine a received frame is an Intra-BSS frame if at least one of the RA field, TA field, and BSSID field of the frame received by the station indicates the MAC address of the AP to which the station is connected or the MAC address of an AP belonging to the multiple BSSID set to which the AP to which the AP to which the station is connected belongs.
[0332] In such embodiments, the BSSID may be used instead of the AP's MAC address.
[0333] If the BSS color included in the preamble of the PPDU received by the station is the same as the BSS color of the BSS to which the station belongs, and the preamble of the PPDU received by the station indicates that it is for downlink transmission, the station can determine that it transmitted the PPDU received by the AP to which the station is coupled or by an AP belonging to the multiple BSSID set to which the AP to which the station is coupled belongs. If the BSS color included in the preamble of the PPDU received by the station is different from the BSS color of the BSS to which the station belongs, or if the preamble of the PPDU received by the station does not indicate that it is for downlink transmission, the station can determine that it did not transmit the PPDU received by the AP to which the station is coupled or by an AP belonging to the multiple BSSID set to which the AP to which the AP to which the station is coupled belongs.
[0334] A multiple BSSID set may be a set of multiple BSSs from which information about a BSS can be signaled in a single beacon frame or a single probe response frame. Specifically, a set of BSSIDs indicated by a single multiple BSSID element can be called a multiple BSSID set. Also, a single TIM element included in a single beacon frame or a single TIM frame can indicate a buffered frame to multiple BSSIDs included in a multiple BSSID set. Furthermore, a single beacon frame or a single probe response frame may contain a multiple BSSID element. A multiple BSSID element can signal information about multiple BSSs. The BSSID of the BSS from which the aforementioned single beacon frame or probe response frame was transmitted is called the transmitted BSSID. In a multiple BSSID set, the remaining BSSIDs excluding the transmitted BSSID are called nontransmitted BSSIDs. Also, for BSSs corresponding to nontransmitted BSSIDs, a beacon frame or probe response frame does not need to be transmitted.
[0335] As mentioned above, the maximum number of BSSIDs that a multiple BSSID set may contain may be 2^n, where n is a value signaled by the Multiple BSSID element. For example, n may be a value indicated by the MaxBSSID Indicator included in the Multiple BSSID element. A station receiving a Multiple BSSID element can determine the MAC address or BSSID of the AP included in the multiple BSSID set based on the received Multiple BSSID element. In addition, each of the BSSIDs included in the multiple BSSID set may be mapped to each of the multiple BSSID indices. Therefore, the BSSIDs included in the multiple BSSID set may be identified by their BSSID index. The maximum value of the MaxBSSID Indicator may be 8.
[0336] However, in the example described above regarding the setting method for the MLD ID subfield, there may be cases where the value of the MLD ID subfield cannot be set.
[0337] In the embodiments described above, the reporting AP can set the value of the MLD ID subfield to a predetermined value if at least one of the predetermined conditions is met. Furthermore, in other specific embodiments, the reporting AP can set the value of the MLD ID subfield to a value greater than or equal to the predetermined value if the predetermined conditions are met. The predetermined value may be the maximum value that the MLD ID subfield can represent. In this case, the predetermined value may be 255. The predetermined conditions may include at least one of the following: 1) the reported AP does not belong to a multilink device, 2) the reporting AP does not have information on whether or not the reported AP belongs to a multilink device, and 3) the reporting AP does not have information for setting the value of the MLD ID subfield as described above. The predetermined conditions may also include, when the value of the MaxBSSID Indicator field corresponding to the reporting AP is the maximum value, the reported AP is not included in the multilink device to which the AP of the multiple BSSID set to which the reporting AP belongs belongs. Such a condition may be that the reporting AP sends multiple BSSID elements. The maximum value of the MaxBSSID Indicator field may be 8.
[0338] When a reporting AP transmits a multiple BSSID element, the MLD ID subfield can be set to the BSSID index of an AP included in the multiple BSSID set if the reported AP is an AP included in the multiple BSSID set that contains the reporting AP, or if the reported AP belongs to the same multilink device to which the APs in the multiple BSSID set that contain the reporting AP belong. If the value of the MaxBSSID Indicator subfield is 8, the maximum number of BSSIDs that a multiple BSSID set can contain may be 2^8 = 256. Therefore, according to the conditions mentioned above, there should be no value greater than 2^n-1 and less than 255.
[0339] Furthermore, when the value of the MaxBSSID Indicator subfield corresponding to the reporting AP is at its maximum value, the reporting AP may not be able to set the value of the MLD ID subfield, even if the reported AP belongs to the same multilink device as the APs in the multiple BSSID set to which the reporting AP belongs. For example, the reporting AP cannot indicate a multilink device with a BSSID index of 255. The aforementioned embodiment allows the value of the MLD ID subfield to be set to 255. Therefore, when the value of the MLD ID subfield is 255, it is difficult to distinguish whether it is 255 set based on the BSSID index or 255 set based on a pre-specified value.
[0340] Therefore, the condition for setting the value of the MLD ID subfield to a predetermined value may further include the condition that the reported AP belongs to the multilink device to which the APs in the multiple BSSID set to which the reporting AP belong belong, when the value of the MaxBSSID Indicator subfield corresponding to the reporting AP is the maximum value. Furthermore, in other specific embodiments, it is not permissible for 255 to be used as the BSSID index in the multiple BSSID set.
[0341] Furthermore, according to the aforementioned embodiment, regardless of whether the reporting AP transmits multiple BSSID elements or not, it may be difficult for the reporting AP to set the value of the MLD ID subfield. For example, when the reporting AP is providing information about a large number of APs, it may be difficult for the reporting AP to set the value of the MLD ID subfield. Because the number of reported APs is greater than the number of configurable multilink device IDs, it may not be possible to identify the reported APs by their multilink device IDs. For example, when the reporting AP transmits multiple BSSID elements and transmits information to more than (254-2^n+1) APs, it may not be possible to identify the reported APs by their limited range of multilink device IDs. When the reporting AP does not transmit multiple BSSID elements and transmits information to more than (254-1+1) APs, it may not be possible to identify the reported APs by their limited range of IDs. The conditions for setting the value of the MLD ID subfield to a pre-specified value may further include cases where the reported AP cannot be identified by a limited range of IDs.
[0342] To solve the aforementioned problem, the size of the MLD ID subfield can be set to a number of bits greater than 8. In this case, the pre-specified value may be the maximum value that the MLD ID subfield can indicate. That is, if the size of the MLD ID subfield is N bits, the pre-specified value may be 2^N-1. For example, if the size of the MLD ID subfield is 9 bits, the pre-specified value may be 511. As yet another example, if the size of the MLD ID subfield is 16 bits, the pre-specified value may be 65535.
[0343] Figures 26 and 27 show a method for assigning an AID to a non-AP station belonging to a multilink device according to an embodiment of the present invention.
[0344] According to an embodiment of the present invention, a single AID (association ID) may be assigned to a multilink device. That is, the AIDs of stations included in a single multilink device may be the same.
[0345] AID assignment may be performed by the AP. For example, the AID assigned by the AP can be sent to a non-AP STA. The non-AP STA can recognize that the AID received from the AP is the AID that applies to it. A non-AP station that receives a subfield containing the AID value assigned to it can recognize that the subfield containing the AID value assigned to the non-AP station points to the non-AP station.
[0346] The AID assigned to a non-AP station may be included in the coupling response frame or the reconnection response frame. If multilink configuration is performed after the AP has assigned an AID to a non-AP station, the AID assigned to the non-AP station may be the same AID that was assigned to the multilink device to which the non-AP station belonged.
[0347] AID or information related to AID may be included in the PPDU preamble. In this case, the PPDU preamble can use the AID to indicate that the intended recipient of the PPDU is a non-AP station corresponding to the AID. The PPDU preamble can use the AID to indicate that the sender of the PPDU is a non-AP station corresponding to the AID. Also, as mentioned above, AID may be used for traffic indication. A frame can use the AID to indicate that the station corresponding to the AID is the recipient of the frame. For example, a trigger frame can use the AID to indicate the station that the trigger frame will trigger.
[0348] An AID assigned to a multilink device does not need to be permitted to be assigned to another station or another multilink device. In a specific embodiment, an AID assigned to a multilink device does not need to be permitted to be assigned to a station or multilink device that operates on a link that does not operate on the link used by the multilink device.
[0349] In Figure 26, the first multilink device (MLD 1) operates on the first link (Link 1) and the second link (Link 2). The second multilink device (MLD 2) operates on the third link (Link 3) and the fourth link (Link 4). In this case, X is assigned as the AID for the first multilink device (MLD 1). Therefore, it is not permitted for X to be assigned as the AID for the second multilink device (MLD 2), and Y is assigned instead.
[0350] In a specific embodiment of the present invention, an AP multilink device can reassign an AID assigned to any one multilink device to another station or other multilink device. The AP multilink device can reassign an AID assigned to any one multilink device to another station or other multilink device if certain pre-specified conditions are met. In this case, the pre-specified conditions may include that multilink devices or stations to which one AID is commonly assigned operate on different links. That is, the pre-specified conditions may include that multilink devices or stations to which one AID is commonly assigned operate on links that do not overlap. In this case, it is not permissible for stations or multiple multilink devices operating on a single link to receive the same AID assignment. Furthermore, in another specific embodiment, it may include that multilink devices or stations to which one AID is commonly assigned operate on channels that do not overlap.
[0351] In Figure 27(a), the first multilink device (MLD 1) operates on the first link (Link 1) and the second link (Link 2). The AP multilink device assigns X as the AID for the station of the first multilink device (MLD 1). In this case, the AP multilink device can assign X as the AID for the first station (STA1), which does not belong to the first multilink device (MLD 1) and operates on the third link (Link 3) instead of the first link (Link 1) and the second link (Link 2).
[0352] In such embodiments, if a frame contains information about multiple links, a single AID assigned to multiple multilink devices or stations may cause confusion. To prevent this, information transmitted on any one link may apply to the station or multilink device operating on that link. For example, information transmitted on the first link may apply to the station or multilink with AID X operating on the first link, but not to the station or multilink with AID X operating on the second link.
[0353] In Figure 27(b), beacon frames containing TIMs are transmitted on both the first link (Link1) and the second link (Link2). At this time, the TIMs transmitted on both the first link (Link1) and the second link (Link2) indicate that traffic corresponding to AID X should be buffered. The TIM transmitted on the first link (Link1) indicates that traffic for the multilink device (MLD 1) operating on the first link (Link1) has been buffered, and the TIM transmitted on the second link (Link2) indicates that traffic for the station (STA1) operating on the second link (Link2) has been buffered.
[0354] Figures 28 to 30 are used to explain TID-to-link mapping negotiation.
[0355] Figure 28 shows a TID-to-link mapping negotiation according to one embodiment of the present invention.
[0356] As mentioned above, default mapping may be applied to links that do not have TID-to-link mapping. Also, if TID-to-link mapping is removed (tear down) from a link for which TID-to-link mapping negotiations have been completed, default mapping may be applied again to that link.
[0357] TID-to-link mapping negotiations may be conducted through TID-to-link mapping requests and TID-to-link mapping responses. Specifically, a multilink device can make a TID-to-link mapping request by transmitting a frame containing a TID-to-link mapping element. In this case, the frame may include a coupling request frame, a recouping request frame, and a TID-to-link mapping request frame. Therefore, a non-AP station or non-AP multilink device can request TID-to-link mapping by transmitting a coupling request frame, a recouping request frame, or a TID-to-link mapping request frame. An AP or AP multilink device can request TID-to-link mapping by transmitting a TID-to-link mapping request frame. A multilink device that has received a TID-to-link mapping request can make a TID-to-link mapping response by transmitting a frame containing a TID-to-link mapping element. In this case, the frame may include a coupling response frame, a recouping response frame, and a TID-to-link mapping response frame. Therefore, an AP or AP multilink device can respond to a TID-to-link mapping request by sending a coupling response frame, a reconnection response frame, or a TID-to-link mapping request frame. A non-AP station or a non-AP station multilink device can respond to a TID-to-link mapping request by sending a TID-to-link mapping response frame.
[0358] A multilink device can initiate TID-to-link mapping by sending a TID-to-link mapping request. At this time, the multilink device can request default mapping by sending a frame containing a TID-to-link element. A multilink device that receives a TID-to-link mapping request can accept the TID-to-link mapping by sending a TID-to-link mapping response to the TID-to-link mapping request. At this time, a multilink device that receives a TID-to-link mapping request can accept the TID-to-link mapping by sending a frame that does not contain a TID-to-link Mapping element. In yet another specific embodiment, a multilink device that receives a TID-to-link mapping request can accept the TID-to-link mapping by sending a frame containing a TID-to-link Mapping element with the same content as the TID-to-link Mapping element received from a non-AP multilink device.
[0359] Furthermore, a multilink device that receives a TID-to-link mapping request may reject the TID-to-link mapping by sending a TID-to-link mapping response to the TID-to-link mapping request. In this case, the multilink device that receives the TID-to-link mapping request may reject the TID-to-link mapping by sending a frame that does not contain a TID-to-link Mapping element. In yet another specific embodiment, the multilink device that receives a TID-to-link mapping request may reject the TID-to-link mapping by sending a frame that contains a TID-to-link Mapping element with content different from the content of the received TID-to-link Mapping element. If the TID-to-link mapping is rejected, a default mapping may be applied to the link.
[0360] In such embodiments, the frames transmitted by the multilink device for TID-to-link mapping requests and responses may include, as described above, at least one of the following: a coupling request frame, a coupling response frame, a recouping request frame, a recouping response frame, a TID-to-link mapping request frame, and a TID-to-link mapping response frame. Specifically, a multilink device that receives a TID-to-link mapping request can transmit a TID-to-link mapping response frame in response to the TID-to-link mapping request. At this time, the multilink device that receives the TID-to-link mapping request can accept or reject the TID-to-link mapping request by inserting a status code into the TID-to-link mapping response frame. Specifically, a multilink device that receives a TID-to-link mapping request can accept the TID-to-link mapping request by setting the status code of the TID-to-link mapping response frame to SUCCESS. Furthermore, a multilink device that receives a TID-to-link mapping request may reject the request by setting the status code of the TID-to-link mapping response frame to REJECT or DENIED_TID_TO_LINK_MAPPING. Alternatively, a multilink device that receives a TID-to-link mapping request may reject the request by setting the status code of the TID-to-link mapping response frame to PREFERRED_TID_TO_LINK_MAPPING_SUGGESTED. In this case, the multilink device that receives the TID-to-link mapping request may propose a preferred TID-to-link mapping while rejecting the request. Additionally, a multilink device that receives a TID-to-link mapping request may reject the request by sending a TID-to-link mapping rejection frame.
[0361] The TID-To-Link Mapping element included in a TID-to-link matching request indicates the TID-to-link mapping that is the target of the TID-to-link mapping request. Additionally, a TID-To-Link Mapping element sent when accepting a TID-to-link mapping can indicate the accepted TID-to-link mapping. Furthermore, a TID-To-Link Mapping element sent when rejecting a TID-to-link mapping can indicate a newly proposed TID-to-link mapping.
[0362] If a TID-to-link mapping request is accepted, the TID-to-link mapping included in the request will be set for the links that are subject to TID-to-link mapping. If a TID-to-link mapping request is rejected, a default mapping may be applied to the links that are subject to TID-to-link mapping.
[0363] Furthermore, for TID-to-link mapping negotiation, the TID-to-link mapping request frame and the TID-to-link mapping response frame may include a Dialog Token. The Dialog Token maps the TID-to-link mapping request frame and the TID-to-link mapping response frame. Specifically, if the value of the Dialog Token in the TID-to-link mapping request frame and the value of the Dialog Token in the TID-to-link mapping response frame are the same, the TID-to-link mapping response frame may be considered a response to the TID-to-link mapping request frame. Therefore, when a multilink device receives a TID-to-link mapping request frame and sends a TID-to-link mapping response frame, the multilink device can set the Dialog Token value of the TID-to-link mapping response frame to the Dialog Token value of the TID-to-link mapping request frame. When a multilink device sends a TID-to-link mapping response frame without receiving a TID-to-link mapping request frame, the multilink device can set the dialog token value of the TID-to-link mapping response frame to a pre-specified value. In this case, the pre-specified value may be 0. That is, when a multilink device sends an unsolicited TID-to-Link Mapping Response frame, the multilink device can set the dialog token value of the TID-to-link mapping response frame to a pre-specified value. The field indicating the dialog token in the TID-to-link mapping request frame and the TID-to-link mapping response frame may be a one-octet field. The value of the dialog token may be one of the values from 0 to 255.
[0364] A multilink device can perform TID-to-link mapping if its capacity supports it. Furthermore, the capacity of the multilink device may affect the range of TID-to-link mapping it can perform. For example, the capacity of the multilink device may affect the number of TIDs it can map to links or the number of TID-to-link mapping combinations it can apply. The capacity of the multilink device can indicate whether it can map all TIDs to a set of links where they are identical. It can also indicate how many set of links the multilink device can map a TID to.
[0365] In the embodiment shown in Figure 28, the AP multilink device (AP ML) includes a first AP (AP1), a second AP (AP2), and a third AP (AP3). The non-AP multilink device (Non-AP MLD) includes a first non-AP station (Non-AP STA1) and a second non-AP station (Non-AP STA2). The non-AP multilink device (Non-AP MLD) sends a coupling request frame containing a TID-to-link mapping element to the AP multilink device (AP ML). The AP multilink device (AP ML) can accept or reject the TID-to-link mapping corresponding to the TID-to-link mapping element by sending a coupling response frame containing a TID-to-link mapping element to the non-AP multilink device (Non-AP MLD). Furthermore, a non-AP multilink device (Non-AP MLD) can send a TID-to-link mapping request frame to an AP multilink device (AP ML) to renegotiate the TID-to-link mapping. At this time, the AP multilink device (AP ML) can send a TID-to-link mapping response frame to the non-AP multilink device (Non-AP MLD) to accept or reject the TID-to-link mapping corresponding to the TID-to-link Mapping element.
[0366] Figure 29 shows a TID-to-link mapping negotiation in which an AP multilink device sends a TID-to-link mapping request according to an embodiment of the present invention.
[0367] An AP multilink device can send a TID-to-link mapping request using a coupling response frame, a reconnection response frame, and a TID-to-link mapping request frame. Specifically, an AP multilink device can initiate TID-to-link mapping negotiations using a coupling response frame, a reconnection response frame, and a TID-to-link mapping request frame. At this time, the AP multilink device can include a TID-to-link Mapping element in the coupling response frame, the reconnection response frame, and the TID-to-link mapping request frame. Specifically, an AP multilink device can initiate TID-to-link mapping negotiations by including a TID-to-link Mapping element in the coupling response frame, the reconnection response frame, and the TID-to-link mapping request frame. This is because a TID-to-link mapping request sent by a non-AP multilink device may be in a form undesirable to the AP multilink device, and therefore, the AP multilink device may not send a TID-to-link mapping request sent from a non-AP multilink device. Furthermore, AP multilink devices can more easily grasp the overall network status compared to non-AP multilink devices, enabling efficient TID-to-link mapping. In this case, the AP multilink device first sends a coupling response frame or a recouping response frame before completing the TID-to-link mapping negotiation, allowing for the completion of multilink configuration and reconfiguration. When a non-AP multilink device receives a TID-to-link mapping request and sends a TID-to-link mapping response, the TID-to-link mapping negotiation is successfully completed.
[0368] The AP multilink device may be restricted in its ability to send TID-to-link mapping requests using coupling response frames and re-coupling response frames. Specifically, if the coupling request frame does not request TID-to-link mapping, the AP multilink device may send a TID-to-link mapping request in the coupling response frame. If the coupling request frame does not contain a TID-to-link mapping element, the AP multilink device can determine that the coupling request frame does not request TID-to-link mapping. Similarly, if the re-coupling request frame does not request TID-to-link mapping, the AP multilink device may send a TID-to-link mapping request in the re-coupling response frame. If the re-coupling request frame does not contain a TID-to-link mapping element, the AP multilink device can determine that the re-coupling request frame does not request TID-to-link mapping. If a coupling request frame transmitted by a non-AP multilink device does not contain a TID-to-link mapping element, the non-AP multilink device can determine that a coupling response frame containing a TID-to-link mapping element is requesting TID-to-link mapping, upon receiving it in response to the coupling request frame. Similarly, if a re-coupling request frame transmitted by a non-AP multilink device does not contain a TID-to-link mapping element, the non-AP multilink device can determine that a re-coupling response frame containing a TID-to-link mapping element is requesting TID-to-link mapping, upon receiving it in response to the re-coupling request frame. This is because if the coupling request frame contains a TID-to-link element, the non-AP multilink device may confuse the intent behind the inclusion of the TID-to-link element in the coupling response frame. The same applies to re-coupling request frames.
[0369] Furthermore, in such embodiments, the AP multilink device may not determine that the TID-to-link mapping has been successfully completed until it receives a TID-to-link mapping response from the non-AP multilink device. Therefore, the AP multilink device may operate using the default mapping until it receives a TID-to-link mapping response from the non-AP multilink device. Also, even if the AP multilink device receives an ACK for the coupling response frame or re-coupling response frame, it may not determine that the TID-to-link mapping has been successfully completed.
[0370] A non-AP multilink device can respond to a TID-to-link mapping request transmitted by an AP multilink device in a coupling frame or re-coupling frame, as described in the embodiments above. However, the non-AP multilink device must clearly indicate that it is responding to a TID-to-link mapping request transmitted by an AP multilink device in a coupling frame or re-coupling frame. The non-AP multilink device can transmit a TID-to-link mapping response in a response frame to a coupling response frame or a re-coupling response frame requesting TID-to-link mapping. Furthermore, the non-AP multilink device can set the dial log token value of the TID-to-link mapping response to be the same as the dialog token value included in the coupling response frame or re-coupling response frame requesting TID-to-link mapping. However, the coupling response frame and re-coupling response frame requesting TID-to-link mapping do not need to include a dialog token.
[0371] Therefore, a TID-to-link Mapping element may include a response instruction field indicating that it is a response to a TID-to-link mapping request. In this case, the response instruction field may be included in the aforementioned TID-to-Link Mapping Control field. Specifically, the response instruction field may be included in the reserved field of the aforementioned TID-to-Link Mapping Control field. For example, the response instruction field may be any one of the fourth bit (B3) to the eighth bit (B8) of the TID-to-Link Mapping Control field. A multilink device that receives a TID-to-link element can determine, based on the response instruction field, whether the TID-to-link Mapping element requests TID-to-link mapping.
[0372] Since a non-AP multilink device sends a TID-to-link mapping response frame as a response to a coupling request frame or a re-coupling request frame, the AP multilink device needs to distinguish which frame the TID-to-link mapping response frame is a response to. Specifically, when a non-AP multilink device sends a TID-to-link mapping response frame as a response to a coupling request frame or a re-coupling request frame, the non-AP multilink device can set the value of the dialog token in the TID-to-link mapping response frame to a random value. Also, if the value of the dialog token in the TID-to-link mapping response frame is the same as the value of the dialog token in the TID-to-link mapping request frame sent by the AP multilink device, the TID-to-link mapping response frame may be a response to the TID-to-link mapping request frame. Also, if the value of the dialog token in the TID-to-link mapping response frame is different from the value of the dialog token in the TID-to-link mapping request frame sent by the AP multilink device, the TID-to-link mapping response frame may be a response to a coupling request frame or a re-coupling request frame.
[0373] In yet another specific embodiment, when an AP multilink device transmits a TID-to-link mapping request in a coupling response frame or a re-coupling response frame, the value of the dialog token in the TID-to-link mapping response frame transmitted as a response to the TID-to-link mapping request may be set to a pre-specified value. In this case, the pre-specified value may be 0, 1, or 255. When an AP multilink device transmits a TID-to-link mapping request in a coupling frame or a re-coupling frame and receives a TID-to-link mapping response frame whose pre-specified value is the value of the dialog token, the AP multilink device can determine that the received TID-to-link mapping response frame is a response to the transmitted TID-to-link mapping request.
[0374] In another specific embodiment, when an AP multilink device transmits a TID-to-link mapping request in a coupling response frame or a re-coupling response frame, the status code of the TID-to-link mapping response frame transmitted as a response to the TID-to-link mapping request may be a pre-specified value. In this case, the pre-specified status code value may differ from the status code value of the TID-to-link mapping response frame transmitted as a response to a TID-to-link mapping request transmitted by the multilink device in a frame other than a coupling frame or a re-coupling frame. This allows the AP multilink device to determine, based on the status code of the received TID-to-link mapping response frame, whether the received TID-to-link mapping response frame is a response to a TID-to-link mapping request transmitted by the AP multilink device in a coupling response frame or a re-coupling response frame. Specifically, if the status code of the received TID-to-link mapping response frame is a pre-specified value, the AP multilink device can determine that the received TID-to-link mapping response frame is a response to a TID-to-link mapping request transmitted by the AP multilink device in a coupling response frame or a re-coupling response frame.
[0375] In further specific embodiments, the AP multilink device can determine whether a received TID-to-link mapping response frame is a response to a TID-to-link mapping request transmitted by the AP multilink device in a coupling response frame or a re-coupling response frame, based on the value of the Link Mapping field for the TID in the received TID-to-link mapping response frame. Specifically, if the value of the Link Mapping field for the TID in the received TID-to-link mapping response frame is the same as the value of the Link Mapping field for the TID in the TID-to-link mapping request transmitted by the AP multilink device in a coupling response frame or a re-coupling response frame, the AP multilink device can determine that the received TID-to-link mapping response frame is a response to a TID-to-link mapping request transmitted by the AP multilink device in a coupling response frame or a re-coupling response frame. Specifically, the received TID-to-link mapping response frame may include Link Mapping fields for multiple TIDs. In this case, if all the Link Mapping field values in the TID-to-link mapping response frame are the same as all the Link Mapping field values in the TID-to-link mapping request sent by the AP multilink device in the coupling response frame or re-coupling response frame, the AP multilink device can determine that the received TID-to-link mapping response frame is a response to the TID-to-link mapping request sent by the AP multilink device in the coupling response frame or re-coupling response frame. If the Link Mapping field value for the TID in the TID-to-link mapping response frame received by the AP multilink device is different from the Link Mapping field value for the TID in the TID-to-link mapping request sent by the AP multilink device in the coupling response frame or re-coupling response frame, the AP multilink device does not need to send an ACK for the received TID-to-link mapping response frame.Furthermore, if the Link Mapping field for the TID in the TID-to-link mapping response frame received by the AP multilink device contains at least one of the values of the Link Mapping field for the TID in the TID-to-link mapping request transmitted by the AP multilink device in the coupling response frame or re-coupling response frame, the AP multilink device does not need to send an ACK for the received TID-to-link mapping response frame. Also, if the TID-to-link mapping response frame received by the AP multilink device does not contain any Link Mapping fields for the TID in the TID-to-link mapping request transmitted by the AP multilink device in the coupling response frame or re-coupling response frame, or if the value of the Link Mapping field in the TID-to-link mapping response frame received by the multilink device is different from the value of the Link Mapping field for the TID in the TID-to-link mapping request transmitted in the coupling response frame or re-coupling response frame, the AP multilink device does not need to send an ACK for the received TID-to-link mapping response frame. The above-described embodiment is also applicable when the TID-to-link mapping request is not transmitted in the combined response frame or the recombined response frame.
[0376] In the embodiment shown in Figure 29, the AP multilink device (AP ML) includes a first AP (AP1), a second AP (AP2), and a third AP (AP3). The non-AP multilink device (Non-AP MLD) includes a first non-AP station (Non-AP STA1) and a second non-AP station (Non-AP STA2). The non-AP multilink device (Non-AP MLD) sends a coupling request frame to the AP multilink device (AP ML) that does not include a TID-to-link mapping element. The AP multilink device (AP ML) sends a coupling response frame that includes a TID-to-link mapping element to the non-AP multilink device (Non-AP MLD) to request a TID-to-link mapping corresponding to the TID-to-link mapping element. At this time, the non-AP multilink device (Non-AP MLD) accepts the TID-to-link mapping request by sending a TID-to-link mapping response frame to the AP multilink device (AP ML).
[0377] Figure 30 illustrates a TID-to-link mapping negotiation in an embodiment of the present invention when the link set requesting TID-to-link mapping and the link set set by the TID-to-link mapping response are different.
[0378] The link sets for which TID-to-link mapping is requested in a join request frame or rejoin request frame may be different from the link sets for which TID-to-link mapping is intended to be set in a join response frame or rejoin response frame. For example, TID-to-link mapping may be requested for three links in a join request frame or rejoin request frame, and TID-to-link mapping may be set for two links in a join response frame or rejoin response frame. Furthermore, different link sets may include different link set configurations. Specifically, different link set configurations may include different operating channels for the link sets. Also, different link sets may include different link set configurations.
[0379] In some embodiments shown in Figure 28, when an AP multilink device receives a coupling request frame or recouping request frame containing a TID-to-link mapping element, the AP multilink device can establish a multilink by sending a coupling response frame or recouping response frame that does not contain a TID-to-link mapping element. However, as mentioned above, the link set requesting TID-to-link mapping in the coupling request frame or recouping request frame may be different from the link set for which TID-to-link mapping is to be established in the coupling response frame or recouping response frame.
[0380] Therefore, in yet another embodiment of the present invention, if an AP multilink device receives a coupling request frame or a recouping request frame containing a TID-to-link mapping element and attempts to set a different link set than the multilink link set that the coupling request frame or recouping request frame attempts to set, the AP multilink device may send a coupling response frame or a recouping response frame that does not contain a TID-to-link mapping element. This allows the AP multilink device to reject the TID-to-link mapping. In this case, a default mapping may be applied to the AP multilink device and the non-AP multilink device.
[0381] When an AP multilink device receives a coupling request frame or recouping request frame containing a TID-to-link mapping element and sends a coupling response frame or recouping response frame that sets a different link set than the multilink link set that the coupling request frame or recouping request frame intends to set, the AP multilink device may send a coupling response frame or recouping response frame that does not contain a TID-to-link mapping element. Also, when a non-AP multilink device sends a coupling request frame or recouping request frame containing a TID-to-link mapping element and receives a coupling response frame or recouping response frame that sets a different link set than the multilink link set that the coupling request frame or recouping request frame intends to set, the non-AP multilink device may determine that the TID-to-link mapping request has been rejected, even if the received coupling response frame or recouping response frame does not contain a TID-to-link mapping element. In this case, default mapping may be applied to the AP multilink device and the non-AP multilink device.
[0382] In yet another specific embodiment, if the AP multilink device receives a coupling request frame or a recouping request frame containing a TID-to-link mapping element and intends to set a different link set than the multilink link set that the coupling request frame or recouping request frame intends to set, the AP multilink device may transmit a coupling response frame or a recouping response frame containing a TID-to-link mapping element. At this time, the TID-to-link mapping element contained in the coupling response frame or recouping response frame can instruct the TID-to-link mapping proposed by the AP multilink device. In this case, the operation of the non-AP multilink device may be the same as in the embodiment described in Figure 28.
[0383] In the embodiments described above, for the sake of explanation, the operation of the multilink device was described, but the operation of the multilink device may also be performed by the stations included in the multilink device.
[0384] Figure 31 shows a method by which a non-AP multilink device according to an embodiment of the present invention determines the traffic buffered by an AP multilink device.
[0385] The non-AP multilink device receives a beacon frame, including the beacon frame, from the AP multilink device (S3101).
[0386] The non-AP multilink device determines whether traffic for the non-AP multilink device is buffered in the multilink device based on the Partial Virtual Bitmap subfield of the TIM element (S3103). In this case, the Partial Virtual Bitmap subfield includes one or more first bits and one or more second bits. A bit set to 1 among the one or more first bits indicates that traffic for the non-AP multilink device corresponding to that bit has been buffered in the AP multilink device. A bit set to 1 among the one or more second bits indicates that traffic for the non-AP station corresponding to that bit has been buffered in the AP multilink device. The specific Partial Virtual Bitmap subfield format and settings can be followed according to the embodiment described in Figures 13 to 18.
[0387] When traffic for a non-AP multilink device is buffered by the AP multilink device, the Per-Link Traffic Indication List subfield of the Multi-Link Traffic element can be used to determine which of the multiple links buffered the traffic for the non-AP multilink device, or which of the multiple links the AP multilink device recommends the non-AP multilink device retrieve traffic from. The Per-Link Traffic Indication List subfield may contain n Per-Link Traffic Indication Bitmap subfields, where n is the sum of the number of bits set to 1 among the one or more first bits and the number of bits set to 1 among the one or more second bits. Each of the n Per-Link Traffic Indication Bitmap subfields may be mapped to a non-AP multilink device corresponding to a bit set to 1 among the one or more first bits, and to a non-AP station corresponding to a bit set to 1 among the one or more second bits. Furthermore, multiple link IDs may be mapped in ascending order to the bits of the Per-Link Traffic Indication Bitmap subfield that is mapped to the non-AP multilink device.
[0388] Additionally, the Per-Link Traffic Indication Bitmap subfield, which maps to non-AP stations corresponding to one or more second bits set to 1, may have a reserved bit set. In this case, the value of the reserved bit may be 0.
[0389] If a non-AP multilink device successfully performs TID-to-link mapping with an AP multilink device, and not all TIDs are mapped to all links, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device can indicate whether traffic for the non-AP multilink device is buffered on each of the multiple links. Furthermore, if a default mapping is applied to the link between the non-AP multilink device and the AP multilink device, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device can indicate which of the multiple links the non-AP multilink device recommends directing traffic transmission to. In this case, the default mapping may map all TIDs to all links.
[0390] Bits in the Per-Link Traffic Indication Bitmap subfield mapped to a non-AP multilink device that correspond to links not configured by the AP multilink device or the non-AP multilink device may be set as reserved bits. Also, bits in the Per-Link Traffic Indication Bitmap subfield mapped to a non-AP multilink device that correspond to disabled links of the non-AP multilink device may be set as reserved bits. In this case, a disabled link may be a link on which uplink and downlink transmission has been stopped.
[0391] The specific Per-Link Traffic Indication List subfield of the Multi-Link Traffic element can be as described in Figures 13 to 18.
[0392] Although the present invention has been described using wireless LAN communication as an example, it is not limited thereto and may be applied similarly to other communication systems such as cellular communication. Furthermore, although the methods, apparatus, and systems of the present invention have been described in relation to specific embodiments, some or all of the components and operations of the present invention can be implemented using a computer system having a general-purpose hardware architecture.
[0393] The features, structures, and effects described in the examples above are included in at least one embodiment of the present invention, but are not necessarily limited to a single embodiment. Furthermore, the features, structures, and effects exemplified in each embodiment can be combined or modified and implemented in other embodiments by a person with ordinary skill in the art to which the embodiment belongs. Therefore, it should be interpreted that such combinations and modifications are included within the scope of the present invention.
[0394] The above description has focused on embodiments, but these are merely examples and do not limit the present invention. Anyone with ordinary skill in the art to which the present invention belongs will understand that various modifications and applications not exemplified above are possible, as long as they do not deviate from the essential characteristics of these embodiments. For example, each component specifically shown in the embodiments can be modified and implemented. Such differences related to modifications and applications should be interpreted as being within the scope of the present invention as defined in the attached claims. [Explanation of symbols]
[0395] 100 stations 110 processors 120 Communications Department 140 User Interface Section 150 display units 160 memory 200 AP (Access Point) 210 processors 220 Communications Department 260 memory
Claims
1. A non-AP (access point) multilink device including multiple stations, each operating on multiple links, Transmitter / receiver unit, Processor and Includes, The aforementioned processor, The AP multilink device receives a beacon frame containing a TIM (traffic indication map) element and a Multi-Link Traffic element. Based on the Partial Virtual Bitmap subfield of the TIM element, it is determined whether traffic for the non-AP multilink device is buffered in the AP multilink device, the Partial Virtual Bitmap subfield includes one or more first bits and one or more second bits, the bit set to 1 among the one or more first bits indicates that traffic for the non-AP multilink device corresponding to the bit among the one or more first bits has been buffered in the AP multilink device, the bit set to 1 among the one or more second bits indicates that traffic for a non-AP station that does not belong to any multilink device, corresponding to the bit among the one or more second bits, has been buffered in the AP multilink device. When traffic for the non-AP multilink device is buffered by the AP multilink device, the Per-Link Traffic Indication List subfield of the Multi-Link Traffic element determines which of the multiple links the link on which traffic for the non-AP multilink device is buffered, or which of the multiple links the AP multilink device recommends retrieving traffic to the non-AP multilink device. The Per-Link Traffic Indication List subfield includes n Per-Link Traffic Indication Bitmap subfields, n is equal to the sum of the number of bits set to 1 among the one or more first bits and the number of bits set to 1 among the one or more second bits. Each of the n Per-Link Traffic Indication Bitmap subfields is mapped to the non-AP multilink device corresponding to the bit set to 1 among the one or more first bits, and to the non-AP station corresponding to the bit set to 1 among the one or more second bits, If the non-AP multilink device successfully performs TID-to-link mapping with the AP multilink device, and not all TIDs are mapped to all links in the TID-to-link mapping, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device indicates whether traffic for the non-AP multilink device is buffered on each of the multiple links. The Per-Link Traffic Indication Bitmap subfield mapped to the non-AP station corresponding to the bit set to 1 of the one or more second bits is set as a reserved bit, and the value of the reserved bit is 0. The AID (association ID) Offset subfield of the Multi-Link Traffic element indicates the AID corresponding to the first Per-Link Traffic Indication Bitmap subfield among the n Per-Link Traffic Indication Bitmap subfields. Non-AP multilink device.
2. The non-AP multilink device according to claim 1, wherein, among the bits of the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device, bits corresponding to links not set by the AP multilink device or the non-AP multilink device are set as reserved bits.
3. Of the bits in the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device, the bits corresponding to the disabled link of the non-AP multilink device are set as reserved bits. The non-AP multilink device according to claim 1, wherein the disabled link is a link on which uplink and downlink transmission has been discontinued.
4. The non-AP multilink device according to claim 1, wherein the IDs of the plurality of links are mapped in ascending order to the bits of the Per-Link Traffic Indication Bitmap subfield which is mapped to the non-AP multilink device.
5. If the AP that transmitted the beacon frame from the AP multilink device does not belong to the multiple BSSID set, the range of values that the AP multilink device can assign as AID is determined based on the value of the Group Addressed BU Indication Exponent subfield. The non-AP multilink device according to claim 1, wherein the value of the Group Addressed BU Indication Exponent subfield indicates the number of bits used by the AP multilink device to indicate a buffered group address frame corresponding to an AP different from the AP that transmitted the beacon frame.
6. The non-AP multilink device according to claim 5, wherein, when the AP that transmitted the beacon frame belongs to the multiple BSSID set, the range of values that the AP multilink device can assign as AID is determined based on the value of the Group Addressed BU Indication Exponent subfield and a bitmap limit, the bitmap limit being 48 bits.
7. An access point (AP) multilink device including multiple stations, each operating on multiple links, Transmitter / receiver unit, Processor and Includes, The aforementioned processor, The beacon frame transmitted to the non-AP multilink device is configured with a TIM (traffic indication map) element and a Multi-Link Traffic element, the TIM element includes a Partial Virtual Bitmap subfield, the Partial Virtual Bitmap subfield includes one or more first bits and one or more second bits, the bit set to one of the one or more first bits indicates that traffic for the non-AP multilink device corresponding to the bit of the one or more first bits has been buffered by the AP multilink device, the bit set to one of the one or more second bits indicates that traffic for a non-AP station not belonging to any multilink device, corresponding to the bit of the one or more second bits, has been buffered by the AP multilink device. When traffic for the non-AP multilink device is buffered by the AP multilink device, the Per-Link Traffic Indication List subfield of the Multi-Link Traffic element is set depending on which of the multiple links the link to which the traffic for the non-AP multilink device is buffered, or which of the multiple links the AP multilink device recommends retrieving traffic to the non-AP multilink device. The beacon frame is transmitted via the aforementioned transmitting / receiving unit. The Per-Link Traffic Indication List subfield includes n Per-Link Traffic Indication Bitmap subfields, n is equal to the sum of the number of bits set to 1 among the one or more first bits and the number of bits set to 1 among the one or more second bits. Each of the n Per-Link Traffic Indication Bitmap subfields is mapped to the non-AP multilink device corresponding to the bit set to 1 among the one or more first bits, and to the non-AP station corresponding to the bit set to 1 among the one or more second bits, If the non-AP multilink device successfully performs TID-to-link mapping with the AP multilink device, and not all TIDs are mapped to all links in the TID-to-link mapping, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device indicates whether traffic for the non-AP multilink device is buffered on each of the multiple links. The Per-Link Traffic Indication Bitmap subfield mapped to the non-AP station corresponding to the bit set to 1 of the one or more second bits is set as a reserved bit, and the value of the reserved bit is 0. The AID (association ID) Offset subfield of the Multi-Link Traffic element indicates the AID corresponding to the first Per-Link Traffic Indication Bitmap subfield among the n Per-Link Traffic Indication Bitmap subfields. AP multilink device.
8. The aforementioned processor, The AP multilink device according to claim 7, wherein the bits of the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device that correspond to links not set by the AP multilink device or the non-AP multilink device are set as reserved bits.
9. The aforementioned processor, Of the bits in the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device, the bits corresponding to the disabled link of the non-AP multilink device are set as reserved bits. The AP multilink device according to claim 7, wherein the disabled link is a link on which uplink and downlink transmission has been discontinued.
10. The AP multilink device according to claim 7, wherein the IDs of the plurality of links are mapped in ascending order to the bits of the Per-Link Traffic Indication Bitmap subfield which is mapped to the non-AP multilink device.
11. If the AP that transmitted the beacon frame from the AP multilink device does not belong to the multiple BSSID set, the range of values that the AP multilink device can assign as AID is determined based on the value of the Group Addressed BU Indication Exponent subfield. The AP multilink device according to claim 7, wherein the value of the Group Addressed BU Indication Exponent subfield indicates the number of bits used by the AP multilink device to indicate a buffered group address frame corresponding to an AP different from the AP that transmitted the beacon frame.
12. The AP multilink device according to claim 11, wherein, when the AP that transmitted the beacon frame belongs to the multiple BSSID set, the range of values that the AP multilink device can assign as AID is determined based on the value of the Group Addressed BU Indication Exponent subfield and a bitmap limit, wherein the bitmap limit is 48 bits.
13. A method for operating a non-AP (access point) multilink device, which includes multiple stations operating on multiple links, The steps include receiving a beacon frame from an AP multilink device, which includes a TIM (traffic indication map) element and a Multi-Link Traffic element, A step of determining whether traffic for the non-AP multilink device is buffered in the AP multilink device based on the Partial Virtual Bitmap subfield of the TIM element, wherein the Partial Virtual Bitmap subfield includes one or more first bits and one or more second bits, the bit set to 1 of the one or more first bits indicates that traffic for the non-AP multilink device corresponding to the bit of the one or more first bits has been buffered in the AP multilink device, and the bit set to 1 of the one or more second bits indicates that traffic for a non-AP station not belonging to any multilink device, corresponding to the bit of the one or more second bits, has been buffered in the AP multilink device. When traffic for the non-AP multilink device is buffered by the AP multilink device, the step of determining, based on the Per-Link Traffic Indication List subfield of the Multi-Link Traffic element, which of the multiple links is the link on which traffic for the non-AP multilink device is buffered, or which of the multiple links is the link on which the AP multilink device recommends retrieving traffic transmission to the non-AP multilink device. Includes, The Per-Link Traffic Indication List subfield includes n Per-Link Traffic Indication Bitmap subfields, n is equal to the sum of the number of bits set to 1 among the one or more first bits and the number of bits set to 1 among the one or more second bits. Each of the n Per-Link Traffic Indication Bitmap subfields is mapped to the non-AP multilink device corresponding to the bit set to 1 among the one or more first bits, and to the non-AP station corresponding to the bit set to 1 among the one or more second bits, If the non-AP multilink device successfully performs TID-to-link mapping with the AP multilink device, and not all TIDs are mapped to all links in the TID-to-link mapping, the Per-Link Traffic Indication Bitmap subfield mapped to the non-AP multilink device indicates whether traffic for the non-AP multilink device is buffered on each of the multiple links. The Per-Link Traffic Indication Bitmap subfield mapped to the non-AP station corresponding to the bit set to 1 of the one or more second bits is set as a reserved bit, and the value of the reserved bit is 0. The AID (association ID) Offset subfield of the Multi-Link Traffic element indicates the AID corresponding to the first Per-Link Traffic Indication Bitmap subfield among the n Per-Link Traffic Indication Bitmap subfields. How it works.
