Communication device, control method, and program
DSO dynamically allocates frequency domains based on station capabilities, addressing inefficient frequency use in multi-channel communication systems, enhancing throughput and reliability by optimizing frequency resource utilization.
Patent Information
- Application Number
- PCT/JP2026/016438
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-24
- Publication Date
- 2026-11-12
AI Technical Summary
Existing communication systems using multiple channels struggle with inefficient frequency resource utilization, particularly when the bandwidth capabilities of access points and stations differ, leading to underutilized frequency bands.
Implementing Dynamic Subband Operation (DSO) to dynamically allocate frequency domains based on the bandwidth capabilities of stations, allowing access points to adjust frequency bands used by stations for efficient frequency division multiplexing communication.
Enhances frequency utilization efficiency by allowing access points to effectively utilize available frequency resources, even when stations have narrower bandwidth capabilities, thereby improving communication throughput and reliability.
Smart Images

Figure JP2026016438_12112026_PF_FP_ABST
Abstract
Description
COMMUNICATION APPARATUS, CONTROL METHOD, AND PROGRAM
[0001] The present invention relates to a communication technique in a communication apparatus capable of performing communication using a communication link configured by a plurality of channels.
[0002] In recent years, along with an increase in the volume of data to be communicated, development of communication techniques such as wireless LAN (Local Area Network) has been advanced. As a major communication standard for wireless LAN, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard series is known. The IEEE 802.11 standard series includes the IEEE 802.11a / b / g / n / ac / ax / be standards and the like. For further improvement of communication reliability, development of the IEEE 802.11bn standard as a successor standard to the IEEE 802.11be standard is progressing. In the IEEE 802.11 WG (Working Group) that formulates the IEEE 802.11bn standard, the goals, study scope, and the like of this standard are defined in the UHR SG, and detailed technical contents to be included in this standard are scheduled to be defined in the TGbn. Note that UHR SG is an abbreviation for Ultra High Reliability Study Group. Also, TGbn is an abbreviation for Task Group bn.
[0003] As one of candidate technologies to be included in the IEEE 802.11bn standard, a technology for efficiently using frequency resources in a communication method using a communication link configured by a plurality of channels is under study. For example, Patent Document 1 describes a technique for performing communication using another channel when the Primary Channel used to acquire a transmission right cannot be used.
[0004] U.S. Patent No. 11696353 Specification
[0005] The present invention provides a suitable technique for improving frequency use efficiency in a communication system that uses a communication link configured by a plurality of channels.
[0006] A communication device according to one aspect of the present invention is an access point device capable of wirelessly communicating with a station device using a frame compliant with the IEEE 802.11 standard series, and is characterized by comprising: frequency domain allocation means for allocating a frequency domain that does not include a primary channel from among a plurality of frequency domains to the station device; and transmission means for transmitting the value of the transmission power when transmitting a trigger frame in the frequency domain allocated by the frequency domain allocation means, and the value of the reception power that the access point device expects when the station device transmits data in that frequency domain.
[0007] According to the present invention, in a communication system that uses a communication link composed of multiple channels, the frequency utilization efficiency can be improved.
[0008] This is a diagram showing an example of the configuration of a wireless communication system. This is a schematic diagram showing an example of a time chart when a communication device transmits data. This is a schematic diagram showing an example of a time chart for communication using a DSO. This is a diagram showing an example of the hardware configuration of a communication device. This is a diagram showing an example of the functional configuration of an AP. This is a diagram showing an example of the functional configuration of an STA. This is a diagram showing an example of a sequence executed when a communication device establishes a connection. This is a diagram showing an example of the configuration of a UHR Capabilities element. This is a diagram showing an example of a time chart when uplink data communication is performed using a DSO. This is a diagram showing an example of a time chart when uplink data communication is performed using a DSO. This is a diagram showing an example of the configuration of an Initial Control frame. This is a diagram showing an example of the configuration of an Initial Control frame. This is a diagram showing an example of the configuration of an Initial Control frame. This is a diagram showing an example of the configuration of a Common Info field. This is a diagram showing an example of the configuration of an Initial Control Response frame. This is a diagram showing an example of the processing flow executed when an AP performs uplink communication. This figure shows an example of the processing flow executed when STA performs uplink communication. This figure shows an example of the configuration of the User Info field. This figure shows an example of the mapping between the value of the RU Allocation subfield, the value of the PS160 subfield, and frequency resources (RUs). This figure shows an example of the RU arrangement in communication using OFDMA and the RU index associated with each RU. This figure explains the challenges when performing uplink communication using DSO. This figure explains the challenges when performing uplink communication using DSO. This figure explains an example of the functions for channel access in AP and STA. This figure explains an example of a Probe Response frame.
[0009] The embodiments will be described in detail below with reference to the attached drawings. Note that the following embodiments do not limit the invention as defined in the claims. While the embodiments describe multiple features, not all of these features are essential to the invention, and the features may be combined in any way. Furthermore, in the attached drawings, identical or similar configurations are given the same reference numerals, and redundant descriptions are omitted.
[0010] (System Configuration) Figure 1 shows an example of the configuration of a wireless communication system according to this embodiment. The wireless communication system includes, for example, an access point (AP) 101 and stations (STA) 111 and STA 112. A station (STA) is also called a Non-access-point (Non-AP) station. STA 111 and STA 112 are sometimes referred to as STA 110 without distinction. Also, AP 101 and STA 110 are sometimes referred to as communication device 100 without distinction. AP 101 and STA 110 are communication devices capable of performing wireless communication in accordance with the IEEE 802.11 standard series. IEEE is an abbreviation for Institute of Electrical and Electronics Engineers. Figure 1 shows a configuration in which STA111 and STA112 participate in network 121 established by AP101. Network 121 may also be called a Basic Service Set (BSS). In network 121 in Figure 1, a configuration with one AP101 and two STA110s is shown, but for example, there may be multiple AP101s, and there may be one or more STA110s. In that case, each STA110 may be connected to one AP101, or one STA110 may be connected to multiple AP101s.
[0011] In this embodiment, the communication device 100 is configured to execute a communication method compliant with the IEEE 802.11bn standard. The IEEE 802.11bn standard is the successor to the IEEE 802.11be standard, which aims for a maximum transmission speed of 46.08 Gbps (Gigabits per second). The main features of the IEEE 802.11bn standard are that it has functions that realize highly reliable communication, low latency communication, and improved throughput when communication traffic is congested. The wireless frame used in a communication method compliant with this standard may be called a UHR (Ultra High Reliability) PPDU. PPDU is an abbreviation for PLCP Protocol Data Unit, and PLCP is an abbreviation for Physical Layer Convergence Protocol. Note that the names UHR and IEEE 802.11bn, etc., may be changed to different names once the standard is finalized. Also note that this specification and the claims attached herein are applicable to communication devices using all successor standards to IEEE 802.11be. Furthermore, the communication device 100 may correspond to at least one of the legacy standards that precede the IEEE 802.11bn standard. Legacy standards include, for example, the IEEE 802.11a / b / g / n / ac / ax / be standards. Furthermore, the communication device 100 may support other communication standards such as Bluetooth®, NFC, UWB, ZigBee, and MBOA. UWB is an abbreviation for Ultra Wide Band, and MBOA is an abbreviation for Multi Band OFDM Alliance. NFC is an abbreviation for Near Field Communication. UWB includes wireless USB, wireless 1394, WiNET, etc. The communication device 100 may also support communication standards such as wired LAN. AP101 is, for example, a wireless LAN router or a personal computer (PC), but is not limited to these. AP101 may be an information processing device such as a wireless chip capable of performing wireless communication compliant with the IEEE 802.11bn standard, etc.STA110 is, for example, a camera, tablet, smartphone, PC, mobile phone, video camera, headset, smart glasses, HMD (head-mounted display) and other wearable devices, but is not limited to these. STA110 may be an information processing device such as a wireless chip capable of performing wireless communication that supports the transmission and reception of PPDUs compliant with the IEEE 802.11bn standard, etc. In this case, it can be configured to perform various controls by hardware circuits inside the wireless chip. It can also be configured so that various processes are performed by the cooperation of a processor such as an ASIP, memory and hardware circuits inside the wireless chip. ASIP is an abbreviation for Application-specific instruction set processor.
[0012] The communication device 100 can communicate using radio signals in frequency bands such as the 2.4 GHz band, 3.6 GHz band, 5 GHz band, 6 GHz band, and millimeter wave bands such as the 45 GHz band and 60 GHz band. The frequency bands used by the communication device 100 are not limited to these, and may include, for example, the Sub1 GHz band. Furthermore, the communication device 100 can communicate using bandwidths of 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, 540 MHz, 640 MHz, 1080 MHz, and 2160 MHz. The bandwidths used by the communication device 100 are not limited to these, and may include, for example, 240 MHz or 4 MHz. Note that the IEEE 802.11 standard series specifies frequency channels using a bandwidth of 20 MHz as basic channels in frequency bands such as the 2.4 GHz, 5 GHz, and 6 GHz bands. Furthermore, this standard defines multiple usable channels in the 2.4 GHz, 5 GHz, and 6 GHz frequency bands. In this standard, the communication device 100 can use one channel in combination with other adjacent channels. This use of one channel in combination with other adjacent channels may be called channel bonding. Also, a bundle of channels formed by one or two or more adjacent channels may be called a communication link. That is, one link formed by two channels with a bandwidth of 20 MHz may use a bandwidth of 40 MHz.
[0013] The IEEE 802.11be standard and its successors (including the IEEE 802.11bn standard and its successors) are expected to specify a maximum bandwidth of 320 MHz or more for a single link. For example, a link using a 320 MHz bandwidth may be constructed by bundling 16 channels with a bandwidth of 20 MHz each using channel bonding. Signals transmitted in this bandwidth may be continuous or discontinuous on the frequency axis. A communication link, which is a bundle of channels formed by one or two or more adjacent channels, may also be called a channel. AP101 and STA110 may be Multi-Link Devices (AP MLD) and STA MLDs, respectively, that support Multi-Link, which establishes and communicates on multiple links simultaneously.
[0014] The communication device 100 establishes one or more links between devices in order to communicate data with other communication devices. For example, STA 110 performs a connection procedure with AP 101 to establish a link with AP 101. The connection procedure includes, for example, STA 110 sending a connection request and AP 101 sending a connection response. Upon completion of the connection procedure, a link is established between STA 110 and AP 101. The establishment of a link is sometimes referred to as establishing a connection. With the link established, the communication device 100 can access the wireless medium and communicate data, etc., with the other communication device. For example, if one link using a bandwidth of 320 MHz is established between devices, the communication device 100 can perform communication by channel bonding using all or some of the channels that constitute the link, depending on the channel status.
[0015] When the communication device 100 transmits a signal using a link established with another communication device, it performs carrier sensing to determine whether or not to transmit. Carrier sensing is the operation in which the communication device 100 determines whether or not there is a signal on the channel that it intends to use for transmission. For example, the communication device 100 measures the strength of the signal received on the channel (received signal strength) and determines that a signal exists if the received signal strength exceeds a predetermined threshold (physical carrier sensing). The received signal strength may also be called the Received Signal Strength Indicator (RSSI). The communication device 100 may also determine the presence or absence of a signal based on information such as the Duration field contained in the signal received on the channel (virtual carrier sensing). For example, the communication device 100 stores the period indicated by the Duration field contained in the received signal as a Network Allocation Vector (NAV) within its own device. The communication device 100 can treat the stored NAV as a period during which it does not transmit. In this embodiment, the operation by which the communication device 100 sets a period during which it does not transmit based on information such as the Duration field of the received signal is called setting the NAV. That is, until the NAV set for the channel expires, the communication device 100 determines that a signal is present on the channel. In this way, the communication device 100 determines whether or not a signal is present on the channel based on the results of performing physical carrier sensing and virtual carrier sensing. If the communication device 100 determines that a signal is present on the channel, it may determine that the channel is in a state where it cannot transmit. In this case, the state of the channel may be called a busy state. On the other hand, a state in which no signal is detected on the channel in carrier sensing and no NAV is set may be called an idle state. If the communication device 100 is in an idle state, it may determine that the channel is in a state where it can transmit.
[0016] When communication is performed using a link with a predetermined bandwidth, the communication device 100 may determine whether transmission is possible using only the 20 MHz bandwidth Primary Channel (PCH) included in that link. For example, the PCH is one of 16 20 MHz bandwidth channels that make up a 320 MHz bandwidth link. In this case, the communication device 100 may determine that transmission is impossible based on the PCH being busy, or that transmission is possible based on the PCH being idle. Therefore, if the communication device 100 determines that transmission is impossible as a result of carrier sensing on the PCH, it may postpone transmission even if other channels included in the same link are idle. Note that each channel other than the PCH that makes up a single link may be called a secondary channel (SCH). Secondary channels may also be called non-primary channels (NPCH).
[0017] The IEEE 802.11 standard series specifies a function that increases communication speed by enabling AP101 to perform multi-user (MU) communication, where it multiplexes radio resources and communicates simultaneously with multiple STA110s. For example, AP101 can communicate in parallel with multiple STA110s using OFDMA. OFDMA is an abbreviation for Orthogonal Frequency Division Multiple Access. In OFDMA, multiple units are formed on the frequency axis in a PPDU transmitted using a frequency channel of a predetermined bandwidth. Each of these units is called a Resource Unit (RU). AP101 assigns one or more different RUs to each STA110. Multi-user communication can be performed by AP101 communicating in parallel with each STA110 using the RU assigned to each STA110. The predetermined bandwidth can be 20MHz, 40MHz, 80MHz, 160MHz, 320MHz, etc. Each RU is composed of multiple subcarriers. For example, an RU composed of 26 subcarriers is called a 26-tone RU. Based on the number of subcarriers that make up the RU, 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, 996-tone RUs, etc. can be configured.
[0018] Here, the usable frequency bandwidth of the communication device 100 may vary depending on the communication device 100. For example, suppose AP 101 can use a bandwidth up to 320 MHz, while STA 111 and STA 112 can each use a bandwidth up to 80 MHz. In this case, according to the current IEEE 802.11 standard series, the frequency bandwidth used for communication between AP 101 and each STA 110 will be the 80 MHz bandwidth including the PCH within the 320 MHz frequency bandwidth used by the AP. The 80 MHz channel including the PCH is called the Primary 80 MHz Channel. Therefore, when AP 101 communicates with STA 111 and STA 112 using OFDMA, it will form multiple RUs in the 80 MHz frequency bandwidth of the Primary 80 MHz Channel and assign an RU to each STA 110. Figure 2 shows an example sequence when AP101 communicates with STA111 and STA112 using OFDMA on the primary 80MHz channel. At time t0, AP101 starts transmitting PPDUs to STA111 and STA112 respectively. At time t1, STA111 and STA112 each start transmitting PPDUs to AP101. Furthermore, at time t2, AP101 starts transmitting PPDUs to STA111 and STA112 respectively. In all cases, communication is performed using the 80MHz frequency band (primary 80MHz channel) including the PCH, and the RU used between AP101 and each STA110 is a part of this 80MHz frequency band. Thus, even if AP101 can use a bandwidth of 320 MHz, if each STA110 can use a bandwidth of 80 MHz, the frequency band used between AP101 and the multiple STA110s is limited to the primary 80 MHz channel. As a result, there are unused frequency resources in the frequency band that AP101 can use, and these unused frequency resources become larger the greater the difference between the bandwidth that AP101 can use and the bandwidth that STA110 can use.For example, in Figure 2, the 240 MHz bandwidth will not be used.
[0019] In light of these circumstances, AP101 in this embodiment allocates frequency resources in frequency division multiplexing communication with multiple STA110s based on whether or not it has the ability to change the frequency band used by STA110 to perform communication. For example, suppose that in the first frequency band of the first bandwidth used by AP101 for communication, there is a second frequency band determined based on the second bandwidth that STA110 can handle, and a third frequency band other than the second frequency band. For example, in the example in Figure 2, the first bandwidth is 320 MHz and the second bandwidth is 80 MHz. The first frequency band is the 320 MHz frequency band usable by AP101, the second frequency band is the 80 MHz frequency band usable by STA111 and STA112, and the third frequency band is the unused 240 MHz frequency band. First, AP101 obtains capability information from STA110 indicating whether or not STA110 has the capability to change the frequency band used to perform frequency division multiplexing communication from the second frequency band to a fourth frequency band that includes a portion of the third frequency band. Based on the fact that STA110 does not have the capability, AP101 allocates frequency resources to STA110 from the second frequency band. Alternatively, based on the fact that STA110 has the capability, AP101 allocates frequency resources to STA110 from the second frequency band, or from the fourth frequency band after STA110 changes the frequency band it uses to the fourth frequency band. Meanwhile, STA110 notifies AP101 of the capability information indicating whether or not it has the capability. STA110 identifies the frequency resources in the second frequency band that were allocated to it based on the fact that its device does not have the capability. Furthermore, STA110 identifies frequency resources in a second or fourth frequency band, which are allocated to it based on the fact that its device has a predetermined capability. If STA110 is allocated frequency resources in the fourth frequency band, it changes the frequency band to be used to the fourth frequency band. AP101 and STA110 communicate using the frequency resources allocated to STA110.With this configuration, STA 110 can change to the fourth frequency band and participate in frequency division multiplexing communication with AP 101 if the frequency resources of the second frequency band are allocated to an STA 110 other than its own communication device. By changing the frequency band used while maintaining the bandwidth used by STA 110 in this way, AP 101 can perform frequency division multiplexing communication using a wide bandwidth even if the corresponding bandwidth of each STA 110 is narrow. An example of the configuration and processing of a communication device 100 that operates in this manner will be described below.
[0020] (Overview of DSO) First, an overview of the operation of Dynamic Subband Operation (DSO) performed by the communication device 100 of this embodiment will be described. Between AP 101 and STA 110, which are capable of performing DSO, multiple frequency domains are set within the frequency band used by AP 101. A frequency domain is also called a frequency band or frequency bandwidth. One of the multiple frequency domains may be the communication link (link) described above. The bandwidth of one of the multiple frequency domains shall be 80 MHz or more. Alternatively, the bandwidth of one of the multiple frequency domains shall be 160 MHz or more. The multiple frequency domains may be set so as not to overlap with each other, or they may be set to partially overlap. Each frequency domain may be explicitly set as a range on the frequency axis. Alternatively, each frequency domain may be implicitly set by setting either the lower or upper end of the domain and the bandwidth available to STA 110 based on that lower or upper end. The settings for each frequency domain are not limited to these; it is sufficient to indicate the target frequency when changing the frequency band used by STA110. For example, the frequency domain used by STA110 may be indicated using the distance on the frequency axis with respect to the PCH or the relationship with the PCH. The relationship with the PCH can be indicated as Secondary 20MHz Channel, Secondary 40MHz Channel, Secondary 80MHz Channel, Secondary 160MHz Channel, etc. Alternatively, the relationship with the PCH can be indicated as Primary 20MHz Channel, Primary 40MHz Channel, Primary 80MHz Channel, Primary 160MHz Channel, etc. Each frequency domain may be called a segment, subblock, subband, etc. If there are two frequency domains to be defined, the frequency domain containing the PCH may be defined as the primary channel, primary band, or primary subband, and the frequency domain not containing the PCH may be defined as the secondary channel, subband, or secondary subband.Figure 3 shows an example where AP101, which uses a frequency band with a bandwidth of 320 MHz, sets four frequency domains, from the first to the fourth, in relation to STA110, which is capable of using a bandwidth of 80 MHz.
[0021] Each frequency domain can be set with the bandwidth usable by STA110 as a single unit. Note that the definitions of the first to fourth frequency bands explained using Figure 2 and the first to fourth frequency domains used in the explanation of Figure 3 are different. AP101 may set a frequency domain that is commonly used in the BSS configured by its own device. In this case, a bandwidth larger than the usable bandwidth of STA110 may be set.
[0022] For example, in Figure 3, two frequency domains with a bandwidth of 160 MHz may be set. In this case, the frequency band used by STA110 will be the frequency band of the bandwidth available to STA110 that is included in each frequency domain. Each frequency domain may consist of different bandwidths. AP101 can set frequency domains according to the bandwidth available to STA110. For example, if the bandwidth available to STA110 is 20 MHz, AP101 can set up to eight frequency domains with a bandwidth of 40 MHz, up to four frequency domains with a bandwidth of 80 MHz, two frequency domains with a bandwidth of 160 MHz, etc.
[0023] STA110 changes the frequency band it uses in response to a notification from AP101 and communicates with AP101. Changing the frequency band used by STA110 can be described as moving along the frequency axis. For example, in Figure 3, suppose AP101 and STA110 are communicating data 301 in a first frequency domain including PCH at times t0 to t1. At time t2, AP101 sends a notification 302 to STA110 indicating that it should move to a third frequency domain. AP101 may explicitly notify STA110 that it should move to a third frequency domain. Alternatively, it may implicitly notify STA110 using a frequency resource notification by using the frequency domain that contains the frequency resources to be allocated to STA110. In response to this notification 302, STA110 moves to the third frequency domain. Then, AP101 and STA110 communicate data 303 in the third frequency domain. In parallel with the communication of data 303, AP101 communicates with other STA110s in the first frequency domain using frequency division multiplexing. Once the communication of data 303 is complete, STA110 can return to the first frequency domain. In this way, by switching the frequency band used by STA110 in response to notifications from AP101, AP101 can communicate with STA110s while effectively utilizing the frequency resources in the frequency band available to its device.
[0024] Alternatively, instead of setting the frequency range as described above, a distance to be moved on the frequency axis to change the frequency band used by STA110 may be set. For example, in Figure 3, the lower end of the 320 MHz frequency band used by AP101 may be set as the first frequency, and second, third, and fourth frequencies may be set at 80 MHz intervals. In this case, STA110 may set a frequency band with one of the first to fourth frequencies as its lower end as the frequency band used by its device, based on a notification from AP101. Each of the first to fourth frequencies may be called a frequency switching position.
[0025] (Device Configuration) Figure 4 shows an example of the hardware configuration of the communication device 100 of this embodiment. As an example of its hardware configuration, the communication device 100 has, for example, a storage unit 401, a control unit 402, a function unit 403, an input unit 404, an output unit 405, a communication unit 406, and an antenna 407. The communication device 100 may have multiple antennas.
[0026] The storage unit 401 is composed of one or more memories, including ROM and RAM, and may store control programs for various operations of each functional unit constituting the communication device 100, as well as various information such as parameters for communication. ROM and RAM are abbreviations for Read Only Memory and Random Access Memory, respectively. In addition to memories such as ROM and RAM, the storage unit 401 may also be composed of storage media such as flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, magnetic tapes, non-volatile memory cards, and DVDs.
[0027] The control unit 402 is composed of one or more processors, such as a CPU and an MPU, and controls the entire communication device 100 by executing a control program stored in the storage unit 401. Alternatively, the control unit 402 may control the entire communication device 100 through cooperation between the control program stored in the storage unit 401 and the OS (Operating System). CPU and MPU are abbreviations for Central Processing Unit and Micro Processing Unit, respectively. If the control unit 402 has multiple processors that can be implemented as a multi-core system, the entire communication device 100 may be controlled by these multiple processors.
[0028] Furthermore, the control unit 402 controls the functional unit 403 to perform predetermined processes such as communication, imaging, printing, and projection. The functional unit 403 is hardware that enables the communication device 100 to perform the predetermined processes described above. For example, if the device is a camera, the functional unit 403 is the imaging unit and performs imaging processing. Also, for example, if the device is a printer, the functional unit 403 is the printing unit and performs printing processing. Also, for example, if the device is a projector, the functional unit 403 is the projection unit and performs projection processing.
[0029] The input unit 404 receives various operations from the user. The output unit 405 outputs various information to the user via a monitor screen or speaker. The output from the output unit 405 may be a display on the monitor screen, audio output via a speaker, vibration output, etc. The input unit 404 and the output unit 405 may both be implemented in a single module, such as a touch panel. The input unit 404 and the output unit 405 may each be an integrated device with the communication device 100, or they may be separate devices.
[0030] The communication unit 406 controls wireless communication in accordance with the IEEE 802.11bn standard. In addition to the IEEE 802.11bn standard, the communication unit 406 may also control wireless communication in accordance with other IEEE 802.11 standard series, such as legacy standards. The communication unit 406 controls the antenna 407 to transmit and receive signals for wireless communication generated by the control unit 402. The communication unit 406 is a so-called wireless chip and may itself have one or more processors and memory. If the communication device 100 supports other wireless communication standards such as NFC and Bluetooth standards, or wired communication such as wired LAN, in addition to the IEEE 802.11bn standard, the communication unit 406 may also control communication in accordance with these communication standards. Furthermore, if the communication device 100 can perform wireless communication in accordance with multiple communication standards, the communication device 100 may be configured to have separate communication units and antennas corresponding to each communication standard. The communication device 100 communicates data with the other party's communication device via the communication unit 406. The antenna 407 may be configured separately from the communication unit 406, or it may be configured as a single module together with the communication unit 406.
[0031] Antenna 407 is an antenna capable of communication in millimeter waves such as the 2.4 GHz band, 5 GHz band, 6 GHz band, 45 GHz band, and 60 GHz band. Figure 4 shows a configuration in which the communication device 100 has two antennas 407, but the communication device 100 may have one or more antennas, or one or more antennas for each frequency band that the device can use. Furthermore, if the communication device 100 has multiple antennas, the communication device 100 may have a communication unit 406 for each antenna.
[0032] (Functional Configuration) Figure 5 shows an example of the functional configuration of AP101. The functional configuration in this embodiment is an example of a functional configuration realized by one or more processors executing programs stored in one or more memories. AP101 may be configured to include a wireless communication control unit 501, an information acquisition unit 502, a resource allocation unit (frequency domain allocation unit, frequency domain designation unit) 503, and a DSO control unit 504.
[0033] The wireless communication control unit 501 controls communication with the STA 110. For example, the wireless communication control unit 501 can send and receive frames necessary for performing OFDMA communication with the STA 110. As an example, the wireless communication control unit 501 can send UHR MU PPDU and Trigger frames and receive UHR TB PPDUs. The wireless communication control unit 501 can adjust the length of the frame to be transmitted based on the time required for the STA 110 to move on the frequency axis when performing DSO.
[0034] The information acquisition unit 502 acquires information related to STA 110. For example, the information acquisition unit 502 may acquire information that determines whether or not STA 110 has the capability to perform communication using DSO. The information acquisition unit 502 may also acquire information indicating the distance that STA 110 can travel on the frequency axis when performing communication using DSO. Furthermore, the information acquisition unit 502 may acquire information indicating the time required for STA 110 to travel on the frequency axis. The information acquired by the information acquisition unit 502 can be used by the resource allocation unit 503 and the DSO control unit 504.
[0035] The resource allocation unit 503 performs the allocation of frequency resources to STA 110. For example, when the wireless communication control unit 501 communicates with STA 110 using OFDMA, the resource allocation unit 503 may select a frequency range to allocate frequency resources based on whether or not STA 110 has the capability to perform DSO. Alternatively, the resource allocation unit 503 may select a frequency range to allocate frequency resources to STA 110 based on the distance STA 110 can move along the frequency axis. The resource allocation unit 503 allocates the frequency resources included in the selected frequency range to STA 110. If the resource allocation unit 503 allocates frequency resources from a frequency range other than the first frequency range to STA 110, it may notify STA 110 that it should move along the frequency axis.
[0036] The DSO control unit 504 controls the communication using DSO with the STA 110. For example, the DSO control unit 504 decides whether or not to perform DSO communication with the STA 110 based on whether or not the STA 110 has the capability to perform DSO. The DSO control unit 504 may also decide whether or not to perform DSO communication with the STA 110 based on the distance the STA 110 can move on the frequency axis and the time required to move. The DSO control unit 504 may set multiple frequency ranges or one or more frequency switching positions as destinations for changing the frequency band used by the STA 110.
[0037] Figure 6 shows an example of the functional configuration of STA110. The functional configuration in this embodiment is an example of a functional configuration realized by, for example, one or more processors executing programs stored in one or more memories. STA110 may be configured to include a wireless communication control unit 601, an information notification unit 602, an information acquisition unit 603, and a frequency band control unit 604.
[0038] The wireless communication control unit 601 controls communication with AP 101. For example, the wireless communication control unit 601 can send and receive frames necessary for performing OFDMA communication with AP 101. As an example, the wireless communication control unit 601 can receive UHR MU PPDU and Trigger frames and transmit UHR TB PPDUs. The wireless communication control unit 601 communicates with AP 101 using the frequency resources allocated to its own device.
[0039] The information notification unit 602 notifies AP 101 of information relating to its own device. For example, the information notification unit 602 may notify AP 101 of information indicating whether or not its own device has the capability to perform communication using DSO. In addition, the information notification unit 602 may notify AP 101 of information indicating the distance that its own device can travel on the frequency axis when performing communication using DSO. Furthermore, the information notification unit 602 may notify AP 101 of information indicating the time required for its own device to travel on the frequency axis.
[0040] The information acquisition unit 603 acquires information from AP 101. The information acquisition unit 603 may acquire information that identifies whether AP 101 has the capability to perform communication using DSO. The information acquisition unit 603 may also acquire information that identifies the delay time that AP 101 allows in communication using DSO. Furthermore, the information acquisition unit 603 may acquire information that identifies the frequency resources allocated to its own device. The information identifying the frequency resources acquired by the information acquisition unit 603 can be used by the wireless communication control unit 601, the frequency band control unit 604, etc.
[0041] The frequency band control unit 604 controls the frequency band used by the device. For example, in its normal state, the frequency band control unit 604 sets the first frequency domain, which includes the PCH, as the frequency band used by the device. If the frequency resources allocated to the device are included in a frequency domain other than the first frequency domain, the frequency band control unit 604 sets the frequency domain including those frequency resources as the frequency band used by the device. Furthermore, when communication in that frequency band is completed, the frequency band control unit 604 returns the used frequency band to the first frequency domain. In addition, if the frequency band control unit 604 is notified by AP101 to move along the frequency axis, it may change the frequency band used in accordance with that notification.
[0042] (Processing Flow) Below, we will describe some examples of the processing flow performed by AP101 and each STA in this embodiment.
[0043] (Sharing of Capability Information for Executing Communication Using DSO) AP101 and STA110 can share information regarding the capability of each communication device to execute DSO when establishing a connection between the devices. The operations performed by each communication device when a connection is established between AP101 and STA110 will be explained using Figure 7. Figure 7 shows an example of a sequence of processes performed when a connection is established between AP101 and STA110. This sequence may be executed, for example, when the power of STA110 is turned on and the connection with AP101 is started. First, AP101 periodically transmits Beacon frames (F701). The Beacon frame may contain capability information of AP101 and communication parameters to be used in the BSS configured by AP101. Capability information may be called Capabilities information. Communication parameters may be called Operation information. The BSS configured by AP101 is sometimes called its own BSS. For example, AP101 may transmit information about its capabilities, such as the frequency bandwidth available to it and its ability to perform DSO, via a Beacon frame. AP101 may also transmit information in a Beacon frame that identifies the frequency bandwidth and PCH used by its BSS, and that identifies whether DSO is enabled or disabled, as communication parameters. A Beacon frame includes at least one of the UHR Capabilities Element and the UHR Operation Element. Information that identifies whether DSO is enabled or disabled may be included in either the UHR Capabilities Element or the UHR Operation Element. Alternatively, compatibility can be ensured by placing information that identifies whether DSO is enabled or disabled in the Beacon frame after at least Timestamp, Beacon Interval, Capability Information, Service Set Identifier (SSID), and Supported Rates and BSS Membership Selectors.Communication devices that only support standards prior to the IEEE 802.11be standard cannot understand the content of information that identifies whether the DSO is enabled or disabled, and therefore discard information after that information. For example, if information that identifies whether the DSO is enabled or disabled is transmitted before information about communication compliant with the IEEE 802.11be standard, the receiving device may not be able to obtain the information about the transmitting device's communication compliant with the IEEE 802.11be standard. By arranging information that identifies whether DSO is enabled or disabled to be communicated after Timestamp, Beacon Interval, Capability Information, Service Set Identifier (SSID), and Supported Rates and BSS Membership Selectors, communication devices that receive Beacons and support standards prior to IEEE 802.11be can obtain information about communications of standards prior to IEEE 802.11be. This ensures compatibility with legacy terminals (legacy communication devices) that support standards prior to IEEE 802.11be. STA110 receives Beacon frames transmitted from AP101. STA110 can use the received Beacon frame to identify the frequency band and PCH being used by AP101, and determine whether AP101 has the capability to use DSO, whether DSO is enabled, etc.
[0044] STA 110 starts a connection procedure by transmitting a Probe Request frame to AP 101 based on information acquired from a Beacon frame (F702). The Probe Request frame may include capability information and communication parameters of STA 110. For example, STA 110 may transmit, via the Probe Request frame, information indicating the usable frequency bandwidth of its own apparatus, the presence or absence of the capability to perform DSO, and that DSO is enabled or disabled, as the capability information of its own apparatus. For example, STA 110 may notify AP 101 that its own apparatus has the capability to perform DSO, using a UHR Capabilities element and a UHR Operation element included in the Probe Request frame. Note that in a case where AP 101 does not transmit a Beacon, or a case where STA 110 cannot properly receive a Beacon transmitted by AP 101, STA 110 may start the connection procedure without receiving a Beacon. For example, STA 110 may start the connection procedure by transmitting a Probe Request frame using an SSID (Service Set Identifier) or the like registered in advance by a user or the like. Note that the information indicating the usable frequency bandwidth of its own apparatus, the presence or absence of the capability to perform DSO, and that DSO is enabled or disabled, as the capability information of its own apparatus, may be arranged in the Probe Request frame so as to be communicated at least after a Service Set Identifier (SSID) and Supported Rates and BSS Membership Selectors. Thereby, compatibility can be ensured for the same reason as described above.
[0045] When AP101 receives a Probe Request frame, it transmits a Probe Response frame (F703). In the Probe Response frame, AP101 may notify STA110 of its own device capability information and communication parameters to be used in its BSS. The information indicating the device capability information and communication parameters to be used in its BSS may be arranged in the Probe Response frame so that it is transmitted at least after Timestamp, Beacon Interval, Capability Information, Service Set Identifier (SSID), and Supported Rates and BSS Membership Selectors. This ensures compatibility for the same reasons as described above. AP101 and STA110 authenticate each other's communication devices by exchanging Authentication frames (F704).
[0046] Once STA110 has completed authentication of the other party's communication device, it sends an Association Request frame (F705). STA110 may also use the Association Request frame to notify AP101 of its own device's capabilities and communication parameters. For example, STA110 may use the UHR Capabilities element and UHR Operation element included in the Association Request frame to notify AP101 that its device has the capability to perform DSO. Alternatively, information indicating the capabilities of the device, such as the frequency bandwidth available to the device, whether or not it has the capability to perform DSO, and whether or not DSO is enabled or disabled, may be arranged in the Association Request frame so that it is communicated at least after Capability Information, Listen Interval, Service Set Identifier (SSID), and Supported Rates and BSS Membership Selectors. This ensures compatibility for the same reasons as described above. When AP101 receives an Association Request frame, it transmits an Association Response frame (F706). AP101 may notify STA110 of its own device capability information and its BSS communication parameters using an Association Response frame. Information indicating the device's capability information and communication parameters to be used in its BSS may be arranged in the Association Response frame so that it is communicated at least after Capability Information, Status Code, AID, Supported Rates, and BSS Membership Selectors. This ensures compatibility for the same reasons as described above.
[0047] When STA110 receives an Association Response frame from AP101, a connection is established between AP101 and STA110, and the connection procedure is completed. AP101 and STA110 may then perform a 4-way Handshake to share security information.
[0048] AP101 and STA110 can exchange information for performing DSO during the connection procedure. For example, AP101 and STA110 can notify each other of information indicating whether their own device has the capability to perform DSO, and can obtain information indicating whether the other communication device has the capability to perform DSO. Based on the fact that STA110 has the capability to perform DSO, AP101 can allocate frequency resources included in frequency domains other than the first frequency domain set between AP101 and STA110 to STA110. Based on the fact that AP101 has the capability to perform DSO, STA110 can start exchanging information necessary for performing DSO between its own device and AP101. AP101 and STA110 can notify each other of information indicating whether their own device has enabled or disabled the function to perform DSO, and can obtain information indicating whether the other communication device has enabled or disabled the function to perform DSO. Each communication device 100 may disable the DSO function due to interference in the surroundings, etc., even if its own device has the capability to perform DSO. By exchanging information indicating whether or not the DSO function is enabled, it becomes possible to determine whether the communication device of one device and the other device are in a state where DSO can be executed. AP101 and STA110 may also determine that the other device does not have the ability to execute DSO if the frame received from the other device does not contain a UHR Capabilities element or a UHR Operation element. This makes it possible to notify the other device of whether or not it has the ability to execute DSO without having to include a field in the UHR Capabilities element or UHR Operation element to notify whether or not it has the ability to execute DSO.
[0049] The AP 101 and the STA 110 may exchange information indicating the distance that the STA 110 can move on the frequency axis when executing DSO. This enables a plurality of frequency regions to be set within the frequency band used by the AP 101 between the AP 101 and the STA 110. For example, by acquiring the usable bandwidth of the STA 110, the AP 101 can set a plurality of frequency regions within the usable range of the STA 110 in the frequency band used by its own apparatus. For example, when the AP 101 uses a frequency band with a bandwidth of 320 MHz and the usable bandwidth of the STA 110 is 80 MHz, the AP 101 may set four frequency regions from the first frequency region to the fourth frequency region. At this time, if the distance that the STA 110 can move on the frequency axis is 80 MHz, the STA 110 can use the first frequency region and the second frequency region, and cannot use the third frequency region and the fourth frequency region. In this case, the AP 101 sets two frequency regions (the first frequency region and the second frequency region) with a bandwidth of 80 MHz between itself and the STA 110. In this way, by sharing the information indicating the distance that the STA 110 can move on the frequency axis when executing DSO between the AP 101 and the STA 110, it becomes possible to set a frequency region within a range that can be set as the frequency band used by the STA 110.
[0050] Furthermore, AP101 and STA110 can exchange information indicating the time required for STA110 to move along the frequency axis when performing DSO. The time required for STA110 to move along the frequency axis when performing DSO may be called frequency switching delay. As a result, AP101 may determine that it will not perform DSO with STA110 if STA110's frequency switching delay exceeds the time that its own device can tolerate for performing DSO. Also, if STA110's frequency switching delay exceeds a predetermined time, AP101 may perform control to assist STA110's DSO. The predetermined time may be a time defined by standards such as Short Interface Space (SIFS). For example, AP101 may adjust the length of the frame transmitted by its own device as control to assist STA110's DSO. For example, AP101 may use the frequency switching delay of STA110 to determine the length of the frame when performing DSO. As an example, AP101 may add padding corresponding to the frequency switching delay of STA110 in a frame that notifies STA110 to move to another frequency domain. The padding may be pseudo-data to adjust the length of the frame. This may ensure that the time necessary for STA110 to move to the other frequency domain is secured. Note that the first frequency switching delay when STA110 moves from the first frequency domain to another frequency domain may differ from the second frequency switching delay when STA110 moves from another frequency domain to the first frequency domain. In this case, AP101 may obtain both the first and second frequency switching delays from STA110. Furthermore, AP101 can add padding according to the cases in which STA110 moves from the first frequency domain to another frequency domain, and from another frequency domain to the first frequency domain. AP101 may also identify a frequency domain in which at least one or both of the first frequency switching delay and the second frequency switching delay satisfy a predetermined threshold as a frequency domain in which STA110 can be used for DSO.Furthermore, if the frequency switching delay differs depending on the distance STA110 moves along the frequency axis, AP101 may acquire the frequency switching delay for each frequency domain. For example, AP101 may acquire the first frequency switching delay for STA110 to move to the second, third, and fourth frequency domains, respectively, with respect to the first frequency domain. It may also acquire the second frequency switching delay for STA110 to move from the second, third, and fourth frequency domains to the first frequency domain. In this case, AP101 may add padding to the frame that notifies STA110 to move to another frequency domain, according to the frequency switching delay corresponding to the frequency domain containing the frequency resources allocated to STA110. The frequency switching delay information that STA110 transmits to AP101 as described above may be notified via a Probe Request frame, an Association Request frame, etc.
[0051] AP101 can notify STA110 of the acceptable time for frequency switching delay when its device performs DSO. This acceptable time may be notified via Beacon frames, Probe Response frames, Association Response frames, etc. Upon receiving this acceptable time, STA110 can determine whether its device's frequency switching delay exceeds AP101's acceptable time. Based on the finding that its device's frequency switching delay exceeds AP101's acceptable time, STA110 can disable DSO. In this case, STA110 can notify AP101 that its device has disabled DSO. This allows AP101 and STA110 to skip the exchange of information necessary to perform DSO. Furthermore, if the frequency switching delay of its own device varies depending on the distance moved along the frequency axis, STA110 can notify AP101 of information indicating the distance that can be moved within a range that does not exceed AP101's allowable time. This simplifies the exchange of information between AP101 and STA110 for executing DSO.
[0052] AP101 may notify STA110 of its own device capability information and communication parameters using Beacon frames, Probe Response frames, Association Response frames, etc. STA110 may notify AP101 of its own device capability information and communication parameters using Probe Request frames, Association Request frames, etc. AP101 and STA110 may voluntarily notify each other of their own device capability information, etc., or they may notify each other of their own device capability information, etc., based on a request from the other party's communication device. Furthermore, AP101 and STA110 may passively acquire capability information by waiting for notification of capability information from the other party's communication device, or they may actively acquire capability information by making a request to the other party's communication device. AP101 can efficiently notify an unspecified number of STA110s of its capabilities by broadcasting its capabilities information using Beacon frames. Furthermore, by having STA110s acquire AP101's capabilities information before starting the connection procedure with STA110s, the amount of information exchanged during the connection procedure can be reduced. Note that FILS Discovery frames may be used instead of Beacon frames. FILS Discovery frames may be used to broadcast only a portion of the information contained in Beacon frames (such as SSID and channel information). In addition, the information indicating the distance that STA110s can move on the frequency axis when performing DSO, and the information indicating the time required for STA110s to move on the frequency axis when performing DSO, are also capabilities information, and the above conditions may apply to them.
[0053] (Configuration of information on the capability to perform DSO) The configuration of the information used by the communication device 100 when it notifies the other party's communication device of its own capability information regarding DSO is described below. Figure 8 shows an example of the configuration of information elements used by the communication device 100 when it notifies the other party's communication device of its own capability information regarding DSO. Information elements may be called Information Element (IE). The information elements in Figure 8 may be called UHR Capabilities elements. UHR Capabilities elements may be included in Beacon frames, Probe Response frames, Association Response frames, etc. Also, UHR Capabilities elements may be included in Probe Request frames, Association Request frames, etc. The UHR Capabilities element may be included in frames other than these. For example, the UHR Capabilities element may be included in the Action frame. This makes it possible to change values such as frequency switching delay depending on the surrounding conditions, for example, after the connection between AP101 and STA110 has been established.
[0054] The UHR Capabilities element includes an Element ID field 801, a Length field 802, and an Element ID Extension field 803. The UHR Capabilities element may also include a DSO Transmit Capable (DTC) field 804 and a DSO Receive Capable (DRC) field 805. Furthermore, the UHR Capabilities element may include a DSO padding delay field 806, a DSO Transaction Delay field 807, and a DSO Subbandwidth field 808. Furthermore, the UHR Capabilities element may include a DSO Padding Timeout field 809 and a DSO Transition Timeout field 810.
[0055] The combination of the Element ID field 801 and the Element ID Extension field 803 indicates the type of information element. For example, if the Element ID field 801 is set to 255 and the Element ID Extension field 803 is set to 138, it indicates that this information element is a UHR Capabilities element. The Length field 802 indicates the length of this information element. The DTC field 804 indicates whether the communication device 100 has the capability to perform transmission processing in the DSO. Alternatively, the DSO UL Capable field may be included instead of the DTC field 804. The DSO UL Capable field indicates whether the communication device 100 has the capability to perform uplink data processing in the DSO. The DRC field 805 indicates whether the communication device 100 has the capability to perform receiving processing in DSO. Alternatively, the DSO DL Capable field may be included instead of the DRC field 805. The DSO DL Capable field indicates whether the communication device 100 has the capability to perform downlink data processing in DSO. Furthermore, the DTC field 804 and the DRC field 805 may be configured as a single field. In this case, this single field indicates whether the communication device 100 has the capability to perform DSO. A value of 1 in these fields indicates that the communication device 100 has the capability to perform DSO, while a value of 0 indicates that the communication device 100 does not have the capability to perform DSO. The communication device 100 may implicitly indicate its ability to perform DSO by transmitting a frame containing the UHR Capabilities element. In this case, if the bandwidth available to STA110 is smaller than the bandwidth of the frequency band used by AP101, then STA110 can be interpreted as being capable of DSO operation. For example, if the bandwidth of the frequency band used by AP101 is 320 MHz, then a communication device 100 operating with a bandwidth up to 160 MHz can be interpreted as being capable of performing DSO.Furthermore, the UHR Capabilities element may include a field indicating whether the communication device 100 has enabled or disabled the DSO, in addition to the DTC field 804 and the DRC field 805. This field may also be included in information elements other than the UHR Capabilities element. For example, this field may be included in the UHR Operation element.
[0056] The DSO padding delay fields 806 to DSO Subbandwidth fields 808 may be included in the frame transmitted by STA110. Additionally, the DSO Padding Timeout field 809 and DSO Transaction Timeout field 810 may be included in the frame transmitted by AP101. If the frame transmitted by AP101 includes the DSO padding delay fields 806 to DSO Subbandwidth fields 808, these fields may be treated as reserved areas. Furthermore, if the frame transmitted by STA110 includes the DSO Padding Timeout field 809 and DSO Transaction Timeout field 810, these fields may be treated as reserved areas. The above fields may exist when a value of 1 is set in the DTC field 804 or the DRC field 805, that is, when the communication device 100 has the ability to perform DSO.
[0057] The DSO padding delay field 806 indicates the time required for STA 110 to move along the frequency axis when performing DSO (frequency switching delay). For example, the DSO padding delay field 806 may indicate a first frequency switching delay required for STA 110 to move from a first frequency domain to another frequency domain. The first frequency switching delay may be the time required from when STA 110 finishes receiving the User Info field assigned to its device in the Trigger frame described later until it becomes ready to communicate in the other frequency domain. An example configuration of the DSO padding delay field 806 is shown in Table 1. Table 1 shows the values set in the DSO padding delay field 806 and the corresponding time when the DSO padding delay field 806 is configured with 3 bits. For example, if the UHR Capabilities element received by STA110 contains a DSO padding delay field 806, AP101 can determine the first frequency switching delay of STA110 based on Table 1. If the first frequency switching delay differs depending on the distance STA110 moves along the frequency axis, DSO padding delay fields 806 corresponding to each distance may be provided.
[0058]
[0059] The DSO Transition delay field 807 indicates the time required for STA 110 to move along the frequency axis when performing DSO (frequency switching delay). For example, the DSO Transition delay field 807 may indicate a second frequency switching delay required for STA 110 to move from another frequency domain to the first frequency domain. An example configuration of the DSO Transition delay field 807 is shown in Table 2. Table 2 shows the values set in the DSO Transition delay field 807 and the corresponding times when the DSO Transition delay field 807 is configured with 3 bits. For example, if the UHR Capabilities element received by STA110 contains a DSO Transition delay field 807, AP101 can determine the second frequency switching delay of STA110 based on Table 2. If the second frequency switching delay differs depending on the distance STA110 moves along the frequency axis, DSO Transition delay fields 807 corresponding to each distance may be provided.
[0060]
[0061] The DSO Subbandwidth field 808 indicates information that shows the distance that STA 110 can move on the frequency axis when performing DSO. The distance that can move may be the distance that STA 110 can move on the frequency axis when moving from a state in which it is communicating in a predetermined frequency band to a state in which it is communicating in a different frequency band. The distance that can move may also be the distance that STA 110 can move on the frequency axis to change the frequency band used by AP 101 within the allowable time range for AP 101 to perform DSO. An example configuration of the DSO Subbandwidth field 808 is shown in Table 3. Table 3 shows the values set in the DSO Subbandwidth field 808 and the frequencies corresponding to those values when the DSO Subbandwidth field 808 is configured with 3 bits. For example, if the UHR Capabilities element received by STA110 contains the DSO Subbandwidth field 808, AP101 can determine the travelable distance of STA110 based on Table 3. For example, suppose the DSO Subbandwidth field 808 is set to a value of 3, and the usable frequency bandwidth of STA110 is set to 80 MHz. In this case, it may be shown that STA110 can switch the frequency range used from a first frequency domain with an 80 MHz bandwidth to a range within 80 MHz. For example, it may be shown that STA110 can use the 80 MHz bandwidth from the first frequency domain to the second frequency domain in Figure 3. The travelable distance may also indicate the frequency bandwidth that STA110 becomes usable by performing DSO. For example, suppose it is shown that the usable bandwidth of STA110 is 80 MHz, and that setting the DSO Subbandwidth field 808 to a value of 4 allows for a bandwidth range of 160 MHz. This indicates that the range in which STA110 can select the 80 MHz bandwidth for communication is 160 MHz wide.
[0062] The DTC field 804, the DRC field 805, and the DSO Subbandwidth field 808 may be configured as a single field. In this case, if the value of 0 is set in this field, it may indicate that the communication device 100 cannot perform DSO. Conversely, if a value other than 0 is set in this field, it may indicate that the communication device 100 can perform DSO. On the other hand, if the DSO Subbandwidth field 808 is configured independently of the DTC field 804, etc., the value of 0 in the DSO Subbandwidth field may be associated with 20MHz of DSO Subbandwidth. In this case, the DSO Subbandwidth corresponding to each value in the DSO Subbandwidth field is incremented. For example, a value of 1 in the DSO Subbandwidth field is associated with 40MHz in the DSO Subbandwidth.
[0063]
[0064] The DSO Padding Timeout field 809 indicates the allowable time for the frequency switching delay of STA 110 when AP 101 performs DSO. For example, the DSO Padding Timeout field 809 may indicate the allowable time for the first frequency switching delay required for STA 110 to move from one frequency domain to another. An example configuration of the DSO Padding Timeout field 809 is shown in Table 4. Table 4 shows the values set in the DSO Padding Timeout field 809 and the time corresponding to those values when the DSO Padding Timeout field 809 is configured with 4 bits. For example, if the UHR Capabilities element received from AP101 contains a DSO Padding Timeout field 809, STA110 can determine the allowable time for the first frequency switching delay based on Table 4. If the allowable time for the first frequency switching delay differs depending on the distance STA110 moves along the frequency axis, DSO Padding Timeout fields 809 corresponding to each distance may be provided.
[0065]
[0066] The DSO Transition Timeout field 810 indicates the allowable time for the frequency switching delay of STA 110 when AP 101 performs DSO. For example, the DSO Transition Timeout field 810 may indicate the allowable time for a second frequency switching delay required for STA 110 to move from another frequency domain to the first frequency domain. The DSO Transition Timeout field 810, like the DSO Padding Timeout field 809, may be configured as shown in Table 4, for example.
[0067] Note that the mapping of values in Tables 1 to 4 above is just an example, and the mappings can be different. For example, Tables 1 to 4 show an example where the corresponding value increases exponentially for each increase of 1 in the field value, but the corresponding value can be set to increase by the same amount for each increase of 1 in the field value. For example, in Table 1, the value of the DSO Padding Delay field 806 may increase by 16 μsec each time. Also, in Tables 1, 2, and 4, different values are mapped to the same value set in the field, but the same value may be mapped. For example, when the value of the DSO Padding Delay field in Table 1 is 1, 16 μsec may be mapped, similar to when the value of the DSO Padding Delay field in Table 2 is 1. Furthermore, Tables 1 to 3 show an example where each field consists of 3 bits, but each field may consist of 1, 2, 4 or more bits. Similarly, Table 4 shows an example where the field consists of 4 bits, but the field may consist of 1 to 3, 5 or more bits. Also, the DSO Padding Delay field 806 and the DSO Transition Delay field 807 may be configured as a single field. Similarly, the DSO Padding Timeout field 809 and the DSO Transition Timeout field 810 may be configured as a single field. For example, if the first frequency switching delay and the second frequency switching delay are of similar magnitude, configuring these fields as a single field can reduce the amount of information communicated.
[0068] Fields other than those included in Figure 8 may be included in the UHR Capabilities element. For example, a predetermined field may be included that indicates information for identifying each frequency domain to be set in the frequency band used by AP101. For example, STA110 may use this predetermined field to notify AP101 of information indicating the number of frequency domains to be set in the frequency band used by AP101, or information indicating the number of frequency switching positions. For example, if the number of frequency domains is indicated by this predetermined field, the same number of frequency domains with the same bandwidth as the bandwidth available to STA110 may be set as the number of frequency domains indicated by this predetermined field. Alternatively, if the number of frequency domains is indicated by this predetermined field, the number of frequency domains indicated by this predetermined field may be set in the frequency band used by AP101. In this case, the bandwidth of each frequency domain can be determined by dividing the bandwidth of the frequency band used by AP101 by the number of frequency domains to be set. Alternatively, STA110 may use this predetermined field to notify AP101 of the bandwidth of the frequency domains to be set in the frequency band used by AP101.
[0069] Furthermore, if the number of frequency switching positions is indicated by this predetermined field, then in the frequency band used by AP101, the number of frequency switching positions indicated by this predetermined field may be set for each bandwidth usable by STA110. Also, if the number of frequency switching positions is indicated by this predetermined field, then each frequency switching position may be set at a position on the frequency axis obtained by dividing the frequency band used by AP101 by the number indicated by this predetermined field. AP101 may determine multiple frequency domains and frequency switching positions to be set in the frequency band used by its device based on the value of the predetermined field included in the frame received from STA110. AP101 may then notify STA110 of the result in the predetermined field in the frame transmitted by its device. AP101 may also unilaterally determine multiple frequency domains and frequency switching positions to be set in the frequency band used by its device and notify STA110 of them.
[0070] Figure 8 shows an example in which a communication device 100 uses a UHR Capabilities element to notify the other communication device of its ability to perform DSO. However, this notification of capability information can be performed using other information elements. For example, an Extended Capabilities element to extend the UHR Capabilities element or a Multi-Link element to notify information related to multilink communication can be used. In addition, a new element (such as a DSO element) may be defined for exchanging capability information related to the communication device's DSO.
[0071] (Uplink data communication processing between AP and STA) Figure 9 shows an example sequence when uplink communication (uplink communication) is performed in which STA110 transmits data to AP101. OFDMA is used in this communication. For example, each STA110 transmits data using a UHR TB PPDU corresponding to OFDMA. UHR TB PPDU is an abbreviation for Ultra High Reliability Trigger-based PPDU. In this example, AP101 and STA111 are in a state where they can perform communication using DSO, while STA112 is in a state where it cannot perform communication using DSO. In this example, it is also assumed that in the connection between AP101 and STA111, two 160 MHz bandwidth frequency domains are set up to perform DSO in the frequency band used by AP101. Assume that STA111 and STA112 are storing data, and AP101 is obtaining information that each of STA110 is storing data. In other words, STA110 sends information to AP101 in advance regarding the amount of data it should transmit and the transmission queue. AP101 allocates frequency resources in the first frequency domain to STA112, which cannot use DSO, and allocates frequency resources in the second frequency domain to STA111, which can perform DSO, in order to transmit this data. In other words, AP101 uses the information obtained from STA110 regarding the amount of data it should transmit and the transmission queue when deciding on the frequency resource allocation for STA110.
[0072] First, AP101 sends a notification 901 to move STA111 to a second frequency domain prior to data transmission by STA110. For example, AP101 may send an Initial Control frame (ICF) as notification 901. An Initial Control frame (ICF) is a control frame. This Initial Control frame (ICF) may be a Trigger frame. If the ICF is a Trigger frame, the Trigger Type field (=4) and the GI And H E-LTF field (=3) of the Trigger frame identify it as an ICF. This Trigger frame may be a Basic type Trigger frame. Alternatively, this Trigger frame could be a Buffer Status Report Pol (BSRP) type Trigger frame. Alternatively, this Trigger frame could be one of the following: Beamforming Report Pol (BFRP), MU-BAR, MU-RTS, GCR MU-BAR, Bandwidth Query Report Pol (BQRP), or NDP Feedback Report Pol (NFRP).
[0073] (Frame Configuration) Next, an example of the configuration of a wireless frame transmitted and received by a communication device will be described. Figure 12A shows an example of the configuration of a MAC frame of an ICF according to this embodiment. The ICF includes a Frame Control field 1201, a Duration field 1202, an RA field 1203, a TA field 1204, a Common Info field 1205, and a User Info List field 1206 (User Info field 1206, User Specific field 1206).
[0074] Furthermore, the ICF further includes padding fields 1207 and FCS 1208.
[0075] Note that the names of fields and subfields used in Figure 12A and its description are for illustrative purposes only, and at least some of them may be called by different names that have the same function. Also, some "fields" may be read as "subfields," and vice versa. Furthermore, at least some of the fields or subfields described below may be omitted, and further fields or subfields may be added. In other words, the following frame configuration is an example, and any frame configuration that includes fields performing at least some of the functions of the configuration according to this embodiment described below is intended to be included in the scope of this embodiment.
[0076] The Frame Control field 1201 is a field that stores information related to the control of the entire frame, including information indicating the type of this frame. For example, if the 2-bit Type field of the 3rd and 2nd bits of the Frame Control field 1201 is set to "01 (=1)", it indicates that this frame is a control frame. Furthermore, in a control frame, if the 4-bit Sub type field of the 7th to 4th bits of the Frame Control field 1201 is set to "0010 (=2)", it indicates that this frame is a trigger frame. In other words, an ICF having the format BSRP GI3 is a frame where the combination of the Type field and Sub type field in the Frame Control field 1201 is "01" and "0010". The Frame Control field 1201 contains various other information, but its explanation is omitted here. The Duration field 1202 stores information indicating the time required to transmit the frame. The RA field 1203 stores the MAC address (Receiver Address) of the recipient of this frame. The TA field 1204 stores the MAC address (Transmitter Address) of the sender of this frame. The Common Info field 1205 stores information common to all users (recipients) of this frame. The User Info List 1206 consists of one or more User Info fields, and each User Info field stores control information specific to the user (recipient).
[0077] The Common Info field 1205 includes the Trigger Type field 1211 and the GI And HE / EHT / UHR-LTF Type / TXS Mode / ICF Mode field 1212. In the following, the GI And HE / EHT / UHR-LTF Type / TXS Mode / ICF Mode field 1212 may be referred to as the GI field. In the BSRP GI3 format ICF, the Trigger Type field 1211, consisting of 4 bits from the 3rd bit to the 0th bit, is set to "0100 (=4)" to indicate BSRP. Also, in the BSRP GI3 format ICF, the GI field, consisting of 2 bits from the 21st bit to the 20th bit, is set to "11 (=3)". Thus, a trigger frame in which the Trigger Type field 1211 and the GI field are set to "4" and "3" respectively is called a BSRP GI3. In this embodiment, an ICF Type field 1213 is further added to the Common Info field 1205. This ICF Type field 1213 makes it possible to indicate which of the features of the IEEE 802.11bn standard the frame is related to.
[0078] Here, the conventional Common Info field configuration is shown in Figure 13. In Figure 13, the bit position within the Common Info field is represented by "Bx", where "Bx" refers to the x-th bit. In this Common Info field, as described above, the Trigger Type field is set to "4", and the GI And HE / EHT / UHR-LTF Type / TXS Mode / ICF Mode field is set to "3". The Common Info field also contains various other information, but as shown in Figure 13, it also includes multiple unused areas (Reserved areas). By utilizing this area as the ICF Type field 1213, the ICF Type field 1213 can be prepared without changing the format of the conventional Common Info field. For example, the three bits from the 63rd to the 61st bit may be used as the ICF Type field 1213. If four or more bits are required for the ICF Type field 1213, at least one of the 22nd, 26th, and 53rd bits may be added. In another example, the 22nd, 26th, and 53rd bits may be used for a three-bit ICF Type field 1213. Furthermore, only a portion of the bits from the 63rd to the 61st bit may be used in combination with at least one of the 22nd, 26th, and 53rd bits. In other words, the ICF Type field 1213 can be prepared using any area that was previously designated as Reserved in the Common Info field. The ICF Type field 1213 may also be two bits or less. Furthermore, these are just examples, and the format of the Common Info field may be changed to prepare the ICF Type field 1213. For example, the ICF Type field 1213 may be placed immediately after the GI And HE / EHT / UHR-LTF Type / TXS Mode / ICF Mode field.Furthermore, the ICF Type field 1213 may be provided as part of the Trigger Dependent Common Info. Alternatively, the content indicated by the ICF Type field 1213 described above may be indicated by the Trigger Type field 1211. In other words, the Trigger Type field 1211 can be used to indicate which of the features of the IEEE 802.11bn standard the ICF frame relates to.
[0079] Next, we will explain an example of the use of the ICF Type field 1213 (the content indicated by the ICF Type field 1213) using Figure 12B. In this example, each value of the ICF Type field 1213 is associated with a communication characteristic. For example, if the value of the ICF Type field 1213 is "0", it indicates that this ICF is a frame related to Enhanced Multi Link Single Radio (EMLSR). Also, if the value of the ICF Type field 1213 is "1", it indicates that this ICF is a frame related to Dynamic Power Saving (DPS). In addition, different characteristics are associated with each of the ICF Type fields 1213 from "2" to "8". In this example, when the value of the ICF Type field 1213 is "4", it indicates that this ICF is a frame related to Dynamic Subband Operation (DSO). As mentioned above, since ICFs, which are Trigger frames, are used to control various functions in standards such as IEEE 802.11bn, it is necessary to indicate which function the ICF frame relates to in order to prevent malfunctions in communication devices that receive the ICF. Even when AP 101 and STA 111 perform Dynamic Subband Operation, by explicitly indicating to STA 110 and nearby communication devices that the ICF is for controlling DSO, nearby communication devices can perform appropriate communication. Note that the value of the ICF Type field 1213 and its associated features are just examples, and other combinations of values and features may be used. Furthermore, this example shows the case where the ICF Type field 1213 is 4 bits to represent each of the nine types of features, but it is not limited to this. For example, to accommodate future features, this field may be made 5 bits or more, and values that are not currently used may be set to Reserved (values "9" to "15" in the example of Figure 12B).Alternatively, the Multi-AP can be grouped together under a single identifier, and a MAP Type field can be provided in another field to identify the Multi-AP method. For example, in ICF Type, ID 5 is assigned to Multi-AP, and this value is used for Co-TDMA, Co-BF, Co-SR, and Co-OFDMA. The 22nd and 26th bits can then be used as the MAP Type field to identify Co-TDMA, Co-BF, Co-SR, and Co-OFDMA.
[0080] Furthermore, the value of the ICF Type field 1213 may be defined by the information that is required to be collected by the ICR, which is the response to this frame, as shown in Figure 12C. For example, DPS and Solicited / Unsollicited Coexistence (Coex) require the collection of information on the timing and duration of use of their features. Therefore, the ICF Type field 1213 is set to a value of "0" to indicate that this information is required. Similarly, in DSO control, if the amount of data held in the buffer of the communication device receiving this ICF is required, the ICF Type field 1213 is set to a value of "1". In this way, by defining the type of ICF by the information that is required to be collected, multiple types of features that require the same information can be represented by a single value, thus potentially reducing the number of bits in the ICF Type field 1213. Note that in this example, an example is shown where the ICF Type field 1213 is 3 bits to illustrate each of the six types of features, but this is not the only option. For example, to accommodate future features, this field may be made 4 bits or more, and values not currently used may be set to Reserved (values "6" to "7" in the example of Figure 12C).
[0081] Furthermore, depending on the value of the ICF Type field 1213, the information stored in the User Info List field 1206 (User Info field 1206) may be changed or added. The User Info List field 1206 will be described later.
[0082] Let's return to Figure 9 for explanation. As described above, AP101 transmits a Trigger frame in the first frequency domain including the PCH so that both STA111 and STA112 can receive it (901). The Trigger frame may include User Info fields corresponding to STA111 and STA112, respectively. The User Info fields may include information indicating the frequency resources allocated to the corresponding STA110. For example, AP101 uses the User Info field corresponding to STA112 to notify STA112 that it is being allocated frequency resources in the first frequency domain. Then, for example, AP101 uses the User Info field corresponding to STA111 to notify STA111 that it is being allocated frequency resources in the second frequency domain. This implicitly instructs STA111 to move to the second frequency domain. In this way, AP101 can notify each STA110 of the frequency resources (RU) it has assigned to them using the User Info field corresponding to each STA110. At this time, AP101 may assign all of the frequency resources in the second frequency domain to STA111, or it may assign only a portion of the frequency resources in the second frequency domain. In other words, STA111 may communicate using all of the second frequency domain, or it may communicate using only a portion of the frequency resources in the second frequency domain. Similarly, AP101 may assign all of the frequency resources in the first frequency domain to STA112, or it may assign only a portion of the frequency resources in the first frequency domain. In other words, STA112 may communicate using all of the first frequency domain, or it may communicate using only a portion of the frequency resources in the first frequency domain.
[0083] This allows AP101 to instruct STA111 to move to the second frequency domain and to notify each of STA110 of the frequency resources allocated to them, all in a single notification. AP101 may notify STA111 of the instruction to move to the second frequency domain and to notify each of STA110 of the frequency resources allocated to them using different information or different frames. For example, a new field for instructing a move to the frequency domain may be defined in the Trigger frame, or a new frame for instructing a move to the frequency domain may be defined. This allows AP101 to explicitly notify STA111 that it should move to the second frequency domain.
[0084] Furthermore, the User Info field included in the Trigger frame contains information for determining the transmit power value when STA111 and STA112 transmit the frame. Based on this information for determining the transmit power value and the Received Signal Strength Indicator of the Trigger frame measured by STA111 and STA112, STA111 and STA112 respectively determine the transmit power value when transmitting the frame.
[0085] For example, if notification 901 is a Basic type Trigger frame, STA111 may determine from the information contained in the User Info field associated with its own device that a frequency resource in a second frequency domain has been allocated to its own device. In this case, based on the allocation of a frequency resource in a second frequency domain to its own device, STA111 may determine that it should move to the second frequency domain. When STA111 receives a Trigger frame (901) from AP101, it sends an Initial Control Response frame in the first frequency domain including the PCH as a response to the Trigger frame. STA111 sends the Initial Control Response frame (904) after the Short Interframe Space (SIFS) (903) period has elapsed since receiving the Trigger frame. Furthermore, when STA112 receives a Trigger frame (901) from AP101, it transmits an Initial Control Response frame in the first frequency domain including the PCH as a response to the Trigger frame. STA112 transmits the Initial Control Response frame (905) after the Short Interframe Space (SIFS) (903) period has elapsed since receiving the Trigger frame. As mentioned above, the Trigger frame (901) may be an Initial Control frame.
[0086] Here, we will describe the frame structure of the Initial Control Response frame (ICR) transmitted by a communication device that receives the ICF as described above. The Initial Control Response frame (ICR) is a control frame. Figure 14 shows an example of the MAC frame structure of an ICR used, for example, as a response to an ICF for a DSO. In this embodiment, the Multi-STA Block Ack (M-BA) frame is assumed to be used as the ICR. Reusing an existing frame has the effect of reducing development costs. The M-BA format ICR will be described below.
[0087] In an M-BA format ICR, the Type field and Subtype field of the Frame Control field 1401 are set to "01" and "1001", respectively. This indicates that the frame is a Block Ack (BA) frame. Furthermore, the BA Type subfield 711 in the BA Control field 1402 contained within the BA frame is set to "1011 (=11)", indicating that it is a Multi-STA type (M-BA). This indicates that the frame is M-BA. In addition, it is indicated in the BA Information field 1403 that it is an ICR. Specifically, the Per AID TID Info field 1421 contained within the BA Information field 1403 contains the AID TID Info field 1431. Then, the 1-bit Ack Type subfield 1442 in the AID TID Info field 1431 is set to "0", and the 4-bit TID subfield 1443 is set to "1101 (=13)", indicating that this frame is an ICR. The AID 11 subfield 1441 may store the AID of the STA transmitting this ICR or a specific value (e.g., 2008).
[0088] In this embodiment, the frame includes an ICR Type indicating which feature of the IEEE 802.11bn standard the ICR corresponds to. In the example in Figure 14, the TID_INFO subfield includes the ICR Type information, resulting in the TID_INFO / ICR Type subfield 1412. That is, the TID_INFO subfield can be used as the ICR Type subfield in this frame. Note that this is just one example; for example, an existing Reserved bit, such as the Reserved bit between the BA Type subfield 1411 and the TID_INFO subfield, may be used as the ICR Type subfield. Alternatively, a new field for indicating the ICR Type may be defined. The ICR Type may store a value similar to the values described using, for example, Figures 12B and 12C. In addition to the ICR Type, one or more bits may be provided to indicate that this frame is an ICR corresponding to an ICF (in BSRP GI3 format). In one example, a communication device that sent an ICF may identify an ICR that it sent when it receives an ICR that has its own address in the RA field and contains one bit indicating that it is an ICR corresponding to an ICF. In another example, the ICF may include information such as a token that identifies the frame, and the same value as that token may be included in the ICR. That is, if it is sufficient to identify that the ICR accepts the type of communication specified by the ICF, the ICR does not need to include an ICR Type, as long as it has a form that identifies it as a response to the ICF. For example, the Reserved bit between the BA Type subfield 711 and the TID_INFO subfield may be used for this purpose.
[0089] The ICR then stores information corresponding to the ICR Type value. For example, if the ICR Type is "DSO" in Figure 12B or Buffer Status Report in Figure 12C, the ICR stores information indicating the buffer status at the sender. Figure 14 shows the configuration of the ICR in that case. In this example, the ACI Bitmap field 1433 to the Queue Size All field 1437 are placed after the Block Ack Starting Sequence Control field 1432. In a normal M-BA, the Block Ack Bitmap field is placed after the Block Ack Starting Sequence Control field 1432, but in the ICR, values corresponding to each feature may be placed instead. Furthermore, the ACI Bitmap field 1433 to the Queue Size All field 1437 correspond to the information transmitted in the conventional Buffer Status Report (BSR). The ACI Bitmap field 1433 to the Queue Size All field 1437 may also be treated as subfields within the Block Ack Bitmap field.
[0090] The ACI Bitmap field 1433 is a bitmap indicating which access category (AC) data is currently held in the ICR sender's queue. This bitmap has a 4-bit structure, with the 0th bit corresponding to best-effort (AC_BE), the 1st bit to background (AC_BK), the 2nd bit to video (AC_VI), and the 3rd bit to audio (AC_VO). In this bitmap, the bit corresponding to ACs where data is held is set to "1," and the bit corresponding to ACs where data is not held is set to "0." The ACI High field 1434 stores information indicating the AC with the largest queue size (amount of data held). The Scale Factor field 1435 stores the scaling factor for the reported queue size, and the queue size is reported in units of the octets indicated in the Scale Factor field 1435. For example, if the value of the Scaling Factor field 1435 is "0", the queue size is reported in units of 16 octets; if it is "1", it is reported in units of 256 octets; if it is "2", it is reported in units of 2048 octets; and if it is "3", it is reported in units of 32768 octets. Note that if the unit of the queue size to be reported is predetermined, the Scaling Factor field 1435 may be omitted. The Queue Size High field 1436 stores a value indicating the queue size of the AC indicated by the ACI High field 1434. The Queue Size All field 1437 stores a value indicating the total queue size of all ACs.
[0091] The Block Ack Starting Sequence Control field 1432 includes the Fragment Number subfield 1444 and the Starting Sequence Number subfield 1445. STA 111 and STA 112 may have padding 902 added in the Initial Control Response frames (904, 905). The padding 902 may be added based on the frequency switching delay required for STA 111 to move to a second frequency domain.
[0092] When STA111 transmits an Initial Control Response frame (904), it moves to the second frequency domain based on the fact that STA111 is allocated to the second frequency domain. After moving to the second frequency domain, STA111 transmits data 906 using the frequency resources allocated to its device. Note that STA111 transmits data (906) after the Short Interframe Space (SIFS) period has elapsed since transmitting the ICR frame. Alternatively, STA111 may transmit data 906 if the time taken from the start of movement to the second frequency domain until it is ready to transmit data is less than or equal to the allowable time notified by AP101. In this case, when STA111 has completed the transmission of the ICF, it starts moving to the second frequency domain and activates a timer (not shown). The timer may be set to expire within the allowable time notified by AP101. When STA111 transmits data 906, it transmits data 906 if the timer has not expired, and does not transmit data 906 if the timer has expired. This prevents STA111 from transmitting data 906 at a time exceeding the acceptable time for AP101.
[0093] When STA112 transmits an Initial Control Response frame (905), it transmits data 907 using the frequency resources allocated to itself in the first frequency domain. STA112 transmits data (907) after the Short Interframe Space (SIFS) period has elapsed since transmitting the ICR frame (905).
[0094] For example, if notification 901 is a Basic type Trigger frame, STA112 transmits data 907 using the frequency resources allocated in the User Info field corresponding to its own device in the Trigger frame. Once STA112 has finished transmitting the ICF, it starts a timer (not shown). The timer may be set to expire within the allowable time notified by AP101. When STA112 transmits data 907, it transmits data 907 if the timer has not expired, and does not transmit data 907 if the timer has expired. This prevents STA112 from transmitting data 907 at a time exceeding the allowable time set by AP101.
[0095] When AP101 receives data from each of the STA110, it performs an acknowledgment. For example, AP101 may perform an acknowledgment by transmitting a Block Ack frame. AP101 transmits a Block Ack frame 908 in the second frequency domain in response to data 906 received from STA111 in the second frequency domain. AP101 transmits the Block Ack frame (908) after the Short Interface Space (SIFS) period has elapsed since receiving data 906. The Block Ack frame (908) may be the Multi-STA Block Ack (M-BA) frame described above.
[0096] Furthermore, AP101 transmits a Block Ack frame 909 in the first frequency domain in response to the data 907 received from STA112 in the first frequency domain. AP101 transmits the Block Ack frame (909) after the Short Interface Space (SIFS) period has elapsed since receiving the data 907. The Block Ack frame (909) may be the Multi-STA Block Ack (M-BA) frame described above.
[0097] STA110 completes the transmission process by receiving an acknowledgment for the data it has transmitted. STA111 then moves to the first frequency domain once it has received the Block Ack 908 for data 906.
[0098] (Processing performed by AP when performing uplink communication) An example of the processing flow performed by AP101 when performing uplink communication will be explained using Figure 15. Figure 15 is, for example, the processing flow performed by AP101 when performing uplink communication in Figure 9. This processing flow may be started when AP101 detects that data is being stored in STA110. AP101 may obtain information from each of the STA110 to identify the data storage status in order to determine whether or not there is data stored in each of the STA110. For example, AP101 may inquire about the presence or absence of data stored in STA110 by sending a Buffer Status Report Polling (BSRP) frame to STA110. When STA110 receives the BSRP frame, it may notify AP101 of the Buffer Status Report. In this way, AP101 can obtain the data accumulation status in each of STA110.
[0099] AP101 allocates (specifies) frequency resources to each of the one or more STA110s that are storing data (S1501). For example, AP101 may allocate frequency resources based on whether each STA110 is in a state where it can perform DSO. In this example, AP101 allocates frequency resources in the first frequency domain to STA112, which is in a state where it cannot perform DSO, and allocates frequency resources in the second frequency domain to STA111, which is in a state where it can perform DSO.
[0100] If AP101 allocates a frequency resource in the first frequency domain, including the PCH, to either STA111 or STA112 (NO in S1502), it notifies that no frequency resources in the second frequency domain have been allocated (S1503). For example, AP101 can notify by sending a Basic-type Trigger frame containing information indicating the frequency resources in the first frequency domain allocated to each of STA110. On the other hand, if AP101 allocates a frequency resource in the second frequency domain to one or more of STA110 (YES in S1502), it notifies that a frequency resource in the second frequency domain has been allocated (S1504). In other words, AP101 and STA110 perform the DSO control described above. By notifying that a frequency resource in the second frequency domain has been allocated, AP101 can implicitly instruct STA110 to move to the second frequency domain. Furthermore, AP101 may notify STA110 of information explicitly instructing it to move to a second frequency domain. For example, AP101 may transmit a Basic-type Trigger frame containing information indicating the frequency resources in the second frequency domain allocated to STA110. As described above, the Trigger frame may be an ICF frame. In this case, AP101 may notify STA110 of the RU allocated to it using the PS160 subfield and the RU Allocation subfield of the User Info field corresponding to each STA110 included in the Trigger frame. STA110 may determine that it should move to the second frequency domain based on the fact that the allocated RU is included in the second frequency domain. AP101 may adjust the frame size in the notification indicating that there is an allocation of frequency resources in the second frequency domain.
[0101] Furthermore, AP101 notifies STA110 of the information necessary for STA110 to determine the transmission power, by including it in the AP Tx Power subfield of the Common Info field included in the Trigger frame and in the UL Target Receive Power subfield of the User Info field corresponding to each STA110.
[0102] AP101 receives data from each of the STA110 (S1505). For example, AP101 may receive UHR TB PPDUs from each of the STA110 that are transmitted using the frequency resources allocated to each of the STA110. AP101 then performs an acknowledgment of the received data and terminates the reception process. For example, if AP101 does not allocate frequency resources in the second frequency domain, it may perform an acknowledgment by transmitting a Multi-STA Block ACK in the first frequency domain. A Multi-STA Block ACK is a frame used to perform acknowledgments to multiple STAs using a single frame. Alternatively, if AP101 allocates frequency resources in the second frequency domain to STA111 and frequency resources in the first frequency domain to STA112, it may transmit a Block ACK in each frequency domain (908, 909). For example, AP101 may transmit a Block ACK acknowledgment in the first frequency domain for data received from STA112, and transmit a Block ACK acknowledgment in the second frequency domain for data received from STA111. When AP101 allocates frequency resources in the second frequency domain to STA111, it may add padding to the Block ACK frame. In this case, AP101 may add padding to the Block ACKs transmitted in each frequency domain. This prevents the next communication from being executed until STA111 becomes ready to communicate in the first frequency domain.
[0103] (Processing performed by STA when performing uplink communication) Next, an example of the processing flow performed by STA110 when performing uplink communication will be explained using Figure 16. Figure 16 is, for example, the processing flow performed by STA111 in Figure 9 when performing uplink communication. First, STA110 receives a frame (ICF frame) in the PCH of the first frequency domain (S1601). STA110 transmits a frame (ICF frame) as a response to the received frame (S1602). Then, STA110 determines whether the frame received in S1601 contains an instruction indicating that its own device should move to the second frequency domain (S1603). For example, if the received frame is a Basic type Trigger frame, STA110 can identify the frequency resource allocated to its own device in the User Info field corresponding to its own device. STA110 may determine that it should move to the second frequency domain if the identified frequency resource is included in the second frequency domain. If STA110 determines that it should move to the second frequency domain based on the frame received in S1603 (YES in S1603), it moves to the second frequency domain (S1604). For example, if STA110 determines that it should move to the second frequency domain based on information obtained from the User Info field corresponding to its own device in the Trigger frame, it may start moving immediately after completing the transmission of the ICR frame. In this case, if STA110 completes the move to the second frequency domain before the timer started at the start of the move expires (YES in S1605), it transmits data using the frequency resource allocated to its own device in the second frequency domain (S1606). For example, STA110 transmits a UHR TB PPDU using the RU allocated to its own device by the Trigger frame. On the other hand, if STA110 does not complete the transition to the second frequency domain before the timer expires (NO in S1605), it returns to the first frequency domain without transmitting data and completes the process.
[0104] On the other hand, if STA110 does not determine that it should move to the second frequency domain (NO in S1603), it continues to communicate in the first frequency domain. For example, if the received frame is a Trigger frame, STA110 transmits data using the frequency resources allocated to its own device (S1606).
[0105] (Configuration of information used for data communication between AP and STA) The configuration of information used by AP101 when notifying STA110 of the frequency resources it has allocated will be described below. In controlling DSO, AP101 divides the first, second, third, and fourth frequency domains into 80MHz bands, as shown in Figure 3. Figure 17 shows an example of the configuration of the User Info field included in the Trigger frame used by AP101 when notifying STA110 of the frequency resources it has allocated. AP101 transmits the Trigger frame in each frequency domain to which AP101 allocates STA110. In this embodiment, it is assumed that AP101 allocates STA112, which cannot perform DSO, to the first frequency domain, and STA111, which can perform DSO, to the second frequency domain, and the following explanation will be given accordingly. Therefore, in this embodiment, AP101 transmits Trigger frames in the first frequency domain and the second frequency domain.
[0106] A Trigger frame may contain one or more User Info fields corresponding to one or more destination STA110s. The User Info fields shown in Figure 17 may be included in Basic type Trigger frames or MU-RTS frames. Alternatively, the User Info fields shown in Figure 17 may be included in a new frame defined by AP101 to cause STA110 to move in the frequency domain. The User Info field in Figure 17 may consist of an AID 12 subfield 1701, a RU Allocation subfield 1702, and a PS160 subfield 1708. The AID 12 subfield 1701 indicates information for identifying the STA110 corresponding to this User Info field. For example, the AID 12 subfield indicates 12 digits of the AID of STA110 assigned by AP101 when establishing a connection with STA110. AID is an abbreviation for Association Identifier. STA110 can determine whether a User Info field corresponds to its own device based on whether the value of the AID 12 subfield contained in each User Info field matches the 12 digits of its own device's AID. The RU Allocation subfield 1702 and PS160 subfield 1708 are specific information for uniquely identifying the frequency resource allocated to STA110 corresponding to this User Info field.
[0107] An example of the correspondence between the values of the RU Allocation subfield 1702 and the PS160 subfield 1708 and frequency resources (RUs) is explained using Figure 18. In Figure 18, PS160 represents the value of the PS160 subfield 1708. B0 represents the value of the 0th bit of the RU Allocation subfield 1702. B7-B1 represent the decimal values indicated by the 7th to 1st bits of the RU Allocation subfield 1702, and each value corresponds to the RU indicated by the RU index. For example, if the values of B7-B1 are 0, it indicates that a 26-tone RU with RU index RU1 is allocated. RU or MRU size indicates the size of the allocated RU, from 26-tone to 996-tone RUs. Furthermore, the RU index indicates the range of RU indices that AP101 can assign to STA110.
[0108] The relationship between the RU bandwidth (tone) and the RU index in the 80 MHz bandwidth is shown in Figure 19.
[0109] AP101 can use the frequency resource allocation information configured as described above to notify STA110 that it should move to a different frequency domain. For example, AP101 can use the PS160 value and the B0 value to notify STA111 of a value from 1 to 3, thereby notifying STA111 that it should move to the second to fourth frequency domains. At this time, AP101 can use the PS160 value and the B0 value to notify STA112 of a value of 0, thereby notifying STA112 that it should remain in the first frequency domain and continue communicating.
[0110] Furthermore, when AP101 notifies STA110 to move to a different frequency domain using a MU-RTS frame during downlink communication, it can use this MU-RTS frame to notify multiple types of information at once. For example, AP101 can use a MU-RTS frame to notify STA110 at once whether or not to move to a different frequency domain, the frequency resources allocated to STA110, and the channel on which STA110 should transmit CTS frames. As an example, AP101 can use the PS160 value, the B0 value, and the B7-B1 values of the MU-RTS frame to notify STA110 of the frequency resources allocated to it.
[0111] Furthermore, AP101 may implicitly notify STA110 (STA111) that it should move to a different frequency domain by indicating that the frequency domain containing the frequency resource allocated to STA110 does not include a PCH. AP101 may also notify STA110 that it should transmit CTS frames in a given frequency domain (channel) by notifying STA110 of the RU allocated to it. Based on the received MU-RTS frames, STA110 may identify the frequency domain to move to, the frequency domain (channel) to which CTS frames should be transmitted, and the RU to which data should be received.
[0112] Figure 18 illustrates the allocation of frequency resources when AP101 assigns one RU to STA110. Even when AP101 assigns multiple RUs to STA111, similar operation is possible based on the MRU allocation specified in the IEEE 802.11be standard. MRU stands for Multiple Resource Unit. For example, by setting B7-B1 to predetermined values, AP101 can implicitly notify STA111 to move to a second frequency domain and to allocate an MRU.
[0113] As described above, according to this embodiment, AP101 acquires capability information indicating whether STA110 has the capability to perform communication using DSO, and selects a frequency range that includes frequency resources to be allocated based on STA110's capability information. STA110 moves to the frequency range that includes the frequency resources allocated to its device and performs communication with AP101. This allows AP101 to utilize frequency bands that were not being used in the available frequency band, thereby improving frequency utilization efficiency.
[0114] In this embodiment, the operation of communicating using a frequency domain that does not include the PCH is exemplified as DSO, but it is not limited to this and may be referred to by other names. In this embodiment, the frequency domain that includes the PCH is exemplified as the first frequency domain, and the frequency domain that does not include the PCH is exemplified as the second frequency domain, etc., but it is not limited to this and may be referred to by other names. Also, in this embodiment, the parameters referred to as frequency switching delay, frequency switching position, etc. may be referred to by other names. Similarly, the fields and subfields included in the configuration examples in Figures 8, 12A to 12C, 13, 14, and 17 may be referred to by other names. The setting values and corresponding values of the information shown in Figures 12A to 12C, 18, and Tables 1 to 4 may be configured to be different.
[0115] Next, we will describe how to determine the transmission power when STA110 transmits data. In this embodiment, when STA111 and STA112 receive notification 901 in Figure 9, STA111 transmits data 906, and at the same time, STA112 also transmits data 907. In other words, AP101 receives data 906 and data 907 simultaneously from STA111 and STA112. The problems in this case will be explained using Figures 20A and 20B. Assume that the frequency domain in which STA111 transmits data to AP101 (second frequency domain) and the frequency domain in which STA112 transmits data to AP101 (first frequency domain) are adjacent. As shown in Figure 20A, when AP101 receives data simultaneously from STA111 and STA112, if the power of the data received by AP101 from STA111 and STA112 is approximately the same, AP101 can demodulate each of the data. On the other hand, as shown in Figure 20B, consider the case where AP101 receives data from STA111 and STA112 simultaneously, and the power difference between the data received by AP101 from STA111 and STA112 is greater than a predetermined value. In this case, AP101 may be unable to demodulate the data from STA111, which has lower power. As shown within the dashed box in Figure 20B, the ratio of the side lobes of STA111 to the subcarriers of STA112 is relatively large. In such a case, the side lobes of STA112 become noise that cannot be ignored for the subcarriers of STA111, which have lower data power, and AP101 becomes unable to demodulate the data from STA111. Therefore, in order to prevent this, it is necessary to control the received power (received level, RSSI) of the data from STA111 and STA112 received by AP101 to be approximately the same. The method for performing this control is described below.
[0116] As described above, AP101 transmits a Trigger frame in the frequency domain where the frequency resource allocated to STA110 exists. In this embodiment, as shown in Figure 9, notification 901 is transmitted in the first frequency domain. In this embodiment, the first and second frequency domains are assumed to be 80 MHz. AP101 includes information regarding the transmit power of the Trigger frame transmitted by AP101 in the "AP Tx Power subfield (shown in Figure 13)" within the Common Info field 1205 in the Trigger frame. The information regarding the transmit power of the Trigger frame is the transmit power value required by AP101 to transmit the Trigger frame in the bandwidth through which AP101 transmits the Trigger frame. Alternatively, the information regarding the transmit power of the Trigger frame is the transmit power value normalized over a predetermined bandwidth from the transmit power value required by AP101 to transmit the Trigger frame. Alternatively, the information regarding the transmission power of the Trigger frame refers to the transmission power value expressed in units of a predetermined bandwidth, which represents the transmission power value required by AP101 to transmit the Trigger frame.
[0117] Then, AP101 includes information about the expected received power at AP101 for the data transmitted by STA110 in the "UL Target Receive Power subfield (1707)" within the User Info field 1206 of the Trigger frame. In other words, it is information about the expected received power value of the data when AP101 receives the data transmitted by STA110. The information about the expected received power value of the data at AP101 is information about the expected power value of the received power of the data in the frequency domain where the data from STA110 is received. Alternatively, the information about the expected received power value of the data at AP101 is the power value that AP101 expects for the received power of the data in the frequency domain where the data from STA110 is received, normalized over a predetermined bandwidth.
[0118] Alternatively, the information regarding the expected received power value of the data that AP101 expects is the expected power value, expressed in units of a predetermined bandwidth, for the received power of the data in the frequency domain where the data from STA110 is received. The information regarding the expected power value that AP101 expects for the received power of the data described above will be referred to below as the expected received power value. In other words, AP101 notifies each STA110 of the expected received power value when each STA110 transmits data in the predetermined frequency domain to which it is assigned.
[0119] Meanwhile, STA110 receives the Trigger frame transmitted by AP101 and measures the received power (received level, RSSI) of the Trigger frame. STA110 then stores information regarding the value of the received power of the Trigger frame. This information regarding the value of the received power of the Trigger frame is the received power value normalized by a predetermined bandwidth from the received power value of the Trigger frame received by STA110. Alternatively, this information regarding the value of the received power of the Trigger frame is the expected power value expressed in units of a predetermined bandwidth from the received power value of the Trigger frame received by STA110.
[0120] The STA110 then calculates the difference between the transmit power value of AP101 included in the AP Tx Power subfield and the measured RSSI (received signal strength) of the trigger frame. This difference corresponds to the propagation loss (radio wave propagation loss).
[0121] Then, STA110 calculates the transmit power value by adding the calculated propagation loss value described above to the expected received power value shown in the UL Target Receive Power subfield. From the expected received power value and the propagation loss value, STA110 determines what transmit power value its own device should transmit the uplink signal with to satisfy the received power value (level) expected by AP101. The determined value is then set as the transmit power value of STA110.
[0122] Then, STA110 uses the determined transmission power value to perform data transmission (UHR-TB-PPDU, etc.).
[0123] In summary, AP101 and STA110 perform transmit power control using the following procedure (transmit power control procedure): (1) AP101 stores information indicating the transmit power value of AP101 at the time of transmission in the CommonInfo field (APTxPower subfield) of the trigger frame it transmits. (2) AP101 stores information regarding the received power value of the uplink signal it expects in each UserInfo field (UL TargetReceivedPower subfield) of the trigger frame. Note that "information regarding the received power value of the uplink signal that AP101 expects" is associated with the information of the STA that transmits the uplink signal. This can be achieved by showing the AID12 subfield and the UL TargetReceivedPower subfield of 1707 as a single set, as shown in 1701 in Figure 17. (3) STA110 receives the trigger frame transmitted by AP101 and measures the RSSI (Received Signal Strength) of the trigger frame. (4) STA110 calculates the difference between the transmit power value of AP101 included in the AP Tx Power subfield and the measured RSSI (Received Signal Strength) of the trigger frame. This difference corresponds to the propagation loss (radio wave propagation loss) value. (5) STA110 calculates the transmit power value by adding the calculated propagation loss value described above to the expected receive power value shown in the UL Target Receive Power subfield. (6) STA110 uses the determined transmit power value to perform data transmission (UHR-TB-PPDU, etc.).
[0124] Details of each of (1) to (6) are as described above.
[0125] Next, in this embodiment, the method for controlling the transmission power when STA 110 transmits data to AP 101 (uplink communication) will be explained in more detail. As shown in Figure 9, when multiple STA 110s transmit data simultaneously in different frequency domains, if the power of the signals transmitted by each STA differs significantly, there is a concern that the reception quality of STAs transmitting at low power will deteriorate due to predetermined sidelobe interference. Therefore, in this embodiment, AP 101 notifies information for adjusting the transmission power using a trigger frame, thereby reducing interference when multiple STA 110s transmit simultaneously.
[0126] In Figure 9, AP101 sends notification 901 to STA111 and STA112 in the first frequency domain, which is the primary channel. In response to notification 901, STA111 and STA112 send Initial Control Response frames (904, 905) to AP101 in the first frequency domain. AP101 and STA110 perform transmit power control using the procedures (1) to (6) described above (transmit power control procedure). In this case, AP101 includes "information regarding the transmit power of the Trigger frame" corresponding to the first frequency domain in notification 901.
[0127] Furthermore, AP101 notifies STA111 of the expected received power value when STA111 transmits data in the second frequency domain via notification 901. Also, AP101 notifies STA112 of the expected received power value when STA112 transmits data in the first frequency domain via notification 901.
[0128] STA110 measures the received power (received level, RSSI) of the Trigger frame received in the first frequency domain.
[0129] By controlling the system as described above, even if multiple STAs 110 transmit simultaneously in different frequency domains, the signals from each STA received by AP 101 are controlled to have approximately the same received power, thereby reducing the effects of sidelobe interference. In the example above, in step (6) of the transmit power control procedure, the STA 110 performs data transmission (UHR-TB-PPDU, etc.) using the determined transmit power value. The STA 110 may also perform transmission of the Initial Control Response frame (904, 905) using the transmit power value determined in the transmit power control procedure. This makes it possible to suppress interference and perform efficient communication even when transmitting ICR frames.
[0130] The above describes the case where AP101 and STA110 control the transmission power of STA110 using the control method shown in Figure 9.
[0131] Next, we will describe the case where AP101 and STA110 control the transmission power of STA110 using the control method shown in Figure 10. We will mainly explain the differences from the case in Figure 9. In Figure 9, AP101 transmits notification 901, which is a Trigger frame (ICF frame), to STA111 and STA112 in the first frequency domain. On the other hand, in Figure 10, AP101 transmits notification 1001, which is a Trigger frame (ICF frame), to STA111 in the second frequency domain. Then, AP101 transmits notification 1002, which is a Trigger frame (ICF frame), to STA112 in the first frequency domain.
[0132] Then, STA111 transmits an Initial Control Response frame (1003) in the second frequency domain to AP101 in response to notification 1001. Then, STA112 transmits an Initial Control Response frame (1004) in the first frequency domain to AP101 in response to notification 1002.
[0133] Then, AP101 and STA110 each perform steps (1) to (6) of the transmission power control procedure described above. In this case, AP101 includes in notification 1001 "information regarding the transmission power of the Trigger frame" corresponding to the second frequency domain. AP101 also includes in notification 1002 "information regarding the transmission power of the Trigger frame" corresponding to the first frequency domain.
[0134] AP101 then notifies STA111 of the expected received power value when STA111 transmits data in the second frequency domain via notification 1001. AP101 also notifies STA112 of the expected received power value when STA112 transmits data in the first frequency domain via notification 1002.
[0135] STA111 measures the received power (received level, RSSI) of the Trigger frame received in the second frequency domain. AP101 also includes in notification 1002 "information regarding the transmitted power of the Trigger frame" and "expected received power value" corresponding to the first frequency domain. STA112 measures the received power (received level, RSSI) of the Trigger frame received in the first frequency domain.
[0136] The effects of controlling as shown in Figure 10 are described below. As mentioned above, the propagation loss between AP101 and STA110 is used in the transmission power control of STA110. Since the propagation loss is the loss when radio waves propagate from AP101 to STA110, it is frequency dependent. For example, generally, the higher the frequency of the radio waves, the greater the propagation loss. Therefore, if the frequency domains used for data transmission of STA111 and STA112 are different, it is possible to perform more precise control by calculating the propagation loss in each frequency domain and controlling the transmission power of STA110 based on that.
[0137] In the example described above, in step (6) of the transmit power control procedure, STA110 performs data transmission (UHR-TB-PPDU, etc.) using the determined transmit power value. Alternatively, STA110 may perform transmission (1003, 1004) of the Initial Control Response frame using the transmit power value determined in the transmit power control procedure. This makes it possible to suppress interference and perform efficient communication even when transmitting ICR frames.
[0138] Next, we will describe the case where AP101 and STA110 control the transmit power of STA110 using the control method shown in Figure 11. We will mainly explain the differences from the case in Figure 9. In Figure 9, AP101 transmits notification 901 to STA111 and STA112 in the first frequency domain. On the other hand, in Figure 11, AP101 transmits notification 1101, which is a Trigger frame (ICF frame), to STA111 and STA112 using the first and second frequency domains. Then, STA111 and STA112 transmit Initial Control Response frames (1102, 1103) to AP101 in the first and second frequency domains as a response to notification 1101. Then, AP101 and STA110 each perform steps (1) to (6) of the transmit power control procedure described above.
[0139] In this case, AP101 includes in the notification 1101 "information regarding the transmit power of the Trigger frame" corresponding to the Trigger frame to be transmitted in the first frequency domain and the second frequency domain.
[0140] AP101 then notifies STA111 of the expected received power value when STA111 transmits data in the second frequency domain via notification 1101. AP101 also notifies STA112 of the expected received power value when STA112 transmits data in the first frequency domain via notification 1101.
[0141] STA111 measures the received power (received level, RSSI) of Trigger frames received in the first frequency domain and the second frequency domain. STA112 also measures the received power (received level, RSSI) of Trigger frames received in the first frequency domain and the second frequency domain.
[0142] The effects of controlling as shown in Figure 11 are described below. As mentioned above, the propagation loss between AP101 and STA110 is used in the transmission power control of STA110. Since propagation loss is the loss when radio waves propagate from AP101 to STA110, it is dependent on time changes. For example, due to the effect of fading, the propagation loss may increase only at a specific frequency during a specific period. Alternatively, noise from other devices may be present only at a specific frequency during a specific period. If STA110 measures the received power (received level, RSSI) of the Trigger frame used to calculate propagation loss during the "specific period" mentioned above, the accuracy of the received power value of the Trigger frame may decrease due to the effects of fading and noise mentioned above. Therefore, in order to mitigate the effects of fading and noise at the specific frequency mentioned above, the frequency bandwidth of the signal (frame) used by STA110 to measure the received power used to calculate propagation loss is widened. In this embodiment, the signal (frame) that STA110 uses to measure the received power for calculating propagation loss is a Trigger frame (ICF frame). In this way, AP101 transmits notification 1101 (Trigger frame, ICF frame) that uses two frequency domains: a second frequency domain used by STA111 and a first frequency domain used by STA112. STA110 then measures the received power of the notification 1101 in the first and second frequency domains. By controlling the transmit power of STA110 based on this received power, more precise control becomes possible.
[0143] In the example described above, in step (6) of the transmit power control procedure, STA110 uses the determined transmit power value to perform data transmission (UHR-TB-PPDU, etc.). Alternatively, STA110 may use the determined transmit power value in the transmit power control procedure to perform transmission (1102, 1103) of the Initial Control Response frame. This makes it possible to suppress interference and perform efficient communication even when transmitting ICR frames.
[0144] Note that 1005 in Figure 10 is padding, and plays the same role as the padding 902 described above. Also, 1007 in Figure 10 is data transmitted by STA111 using the frequency resources allocated to its device. 1008 in Figure 10 is data transmitted by STA112 using the frequency resources allocated to its device. Note that STA110 transmits Initial Control Response frames (1003, 1004) after receiving the Trigger frame and after the Short Interframe Space (SIFS) (1006) period has elapsed. AP101 transmits a Block Ack frame 1009 in the second frequency domain in response to the data 1007 received from STA111 in the second frequency domain. AP101 transmits a Block Ack frame (1009) after receiving data 1007 and after the Short Interface Space (SIFS) period has elapsed. The Block Ack frame (1009) may be the Multi-STA Block Ack (M-BA) frame described above. AP101 transmits a Block Ack frame 1010 in the first frequency domain in response to data 1008 received from STA112 in the first frequency domain. AP101 transmits a Block Ack frame (1010) after receiving data 1008 and after the Short Interface Space (SIFS) period has elapsed. The Block Ack frame (1010) may be the Multi-STA Block Ack (M-BA) frame described above.
[0145] Furthermore, 1104 in Figure 11 is padding, and plays the same role as the padding 902 described above. Also, 1106 in Figure 11 is data transmitted by STA 111 using the frequency resources allocated to its device. 1107 in Figure 11 is data transmitted by STA 112 using the frequency resources allocated to its device. Note that STA 110 transmits Initial Control Response frames (1102, 1103) after receiving the Trigger frame and after the Short Interframe Space (SIFS) (1105) period has elapsed.
[0146] AP101 transmits a Block Ack frame 1108 using the first and second frequency domains for data 1106 received from STA111 in the second frequency domain and data 1107 received from STA112 in the first frequency domain. AP101 transmits the Block Ack frame (1108) after the Short Interface Space (SIFS) period has elapsed since receiving data 1106 and / or data 1107. The Block Ack frame (1108) may be the Multi-STA Block Ack (M-BA) frame described above. As described above, AP101 responds with a Block Ack (BA) or Multi-STA Block Ack (M-BA) after receiving uplink data from each STA110. STA110 can confirm that data transmission has been completed successfully by receiving this response. AP101 may also add additional padding to the Block Ack (BA) or Multi-STA Block Ack (M-BA) it transmits. This ensures the frequency switching delay required for STA110 to switch frequency domains when a change in the operating frequency band is necessary.
[0147] In the above embodiment, an example was described in which STA 110 adds padding to the Initial Control Response frame. However, the AP 101 may also add padding to the Trigger frame that AP 101 transmits. The amount of padding to be added is determined by AP 101 based on the frequency switching delay required for STA 110 to switch frequency domains (the value indicated by the DSO padding delay field or the DSO Transition delay field). This ensures that STA 110 has enough time to complete the frequency change and transmit the uplink signal at the target transmit power.
[0148] The above describes the transmit power control that determines the transmit power of STA110 when STA110 performs DSO (e.g., moving to a frequency domain other than the primary channel) by switching bandwidths on the frequency axis. After receiving a trigger frame from AP101, STA111 moves to a second frequency domain (a frequency band that does not include the PCH) and starts transmitting data while performing the transmit power adjustment described above.
[0149] By configuring the system as described above, the difference in received power at AP101 for data transmitted synchronously from multiple STAs can be reduced, thereby mitigating sidelobe interference. Furthermore, the frame design, which takes frequency switching delay into account, allows STA110 to switch bandwidths at the appropriate timing, providing an environment that facilitates achieving the desired transmission power level. This further improves frequency utilization efficiency while meeting the requirements of broadband, high reliability, and low latency envisioned by standards such as IEEE 802.11bn.
[0150] In other words, this method enables highly accurate, low-interference OFDMA communication by multiple users by dynamically utilizing the frequency domain using DSO and notifying information related to the determination of the STA110's transmit power via trigger frames. The above explains how the STA110's transmit power is determined in DSO.
[0151] The following describes the control of EDCA (Enhanced Distributed Channel Access) when STA110 performs the DSO control described above and changes the frequency range used to transmit data.
[0152] Using Figure 21, an example of the channel access function in AP101 and STA110 will be explained. The channel access function includes a data categorization unit 2101, a queue 2102, and a channel access control unit 2105. The channel access control unit 2105 also includes a CSMA / CA execution unit 2103 and a backoff / collision control unit 2104.
[0153] The data categorization unit 2101 classifies the data received from the upper layer into traffic categories compliant with the EDCA mechanism defined in the IEEE 802.11e standard. The EDCA mechanism prioritizes data transmission by class so that certain types of traffic are given priority. The data categorization unit 2101 classifies the data into one of the four access categories (ACs) defined in the EDCA mechanism. Typically, the four ACs are "AC_VO" for voice, "AC_VI" for video, "AC_BE" for best effort, and "AC_BK" for background data. The data categorization unit 2101 stores the data (MAC frame) classified into one of the ACs in the queue 2102 corresponding to that AC. The queue 2102, also called a traffic buffer, is provided for each AC.
[0154] The channel access control unit 2105 performs channel access control based on CSMA / CA for data held in the queue corresponding to each AC in the CSMA / CA execution unit 2103. CSMA / CA is an abbreviation for Carrier Sense Multiple Access with Collision Avoidance. When the CSMA / CA execution unit 2103 detects that data has been stored in the queue corresponding to each AC, it reads the EDCA parameters associated with that queue (AC) stored in the backoff / collision control unit 2104. Then, the CSMA / CA execution unit 2103 determines the transmission waiting time, consisting of the AIFS and the backoff counter, based on the read EDCA parameters. Hereafter, the transmission waiting time, including the AIFS and the backoff counter, will also be simply referred to as the backoff parameters. EDCA parameters can be set so that radio signal transmission is relatively prioritized in the order of VO, VI, BE, BK. Each EDCA parameter includes CWmin, CWmax, AIFS, and TXOPLimit. CWmin is the minimum CW time, which is the waiting time for transmission, and CWmax is the maximum CW time. The shorter CWmin and CWmax, the easier it is to get a transmission opportunity. AIFS is the transmission interval for radio signals. The smaller AIFS, the easier it is to get a transmission opportunity. TXOPLimit is the upper limit of TXOP, which is the channel occupancy time. The larger TXOPLimit, the more data can be transmitted in a single transmission opportunity.
[0155] The backoff / collision control unit 2104 monitors the channel status and notifies the CSMA / CA execution unit 2103 of the channel status information obtained through monitoring. The CSMA / CA execution unit 2103 then decrements the set backoff parameter while the notified channel status is idle and waits without transmitting data until the waiting time becomes zero. The CSMA / CA execution unit 2103 stops the decrementing of the backoff parameter while the notified channel status is busy. The CSMA / CA execution unit 2103 then determines that it has acquired an opportunity to transmit when the waiting time becomes zero. The CSMA / CA execution unit 2103 retrieves data (MAC frame) from the queue and, in cooperation with the backoff / collision control unit 2104, the communication unit 406, and the antenna 407, transmits the UHR PPDU containing the MAC frame to other communication devices.
[0156] The backoff / collision control unit 2104 also mediates when there is an internal conflict in the acquisition of transmission opportunities by the CSMA / CA execution units 2103 corresponding to each AC. That is, when CSMA / CA execution units 2103 corresponding to different ACs acquire transmission opportunities simultaneously and request data transmission, the backoff / collision control unit 2104 controls the system so that data stored in the higher priority queue is transmitted preferentially. For example, when a CSMA / CA execution unit 2103 corresponding to the VO queue and a CSMA / CA execution unit 2103 corresponding to the BK queue acquire transmission opportunities simultaneously, the backoff / collision control unit 2104 controls the system so that data stored in the VO queue is transmitted preferentially. At this time, the backoff / collision control unit 2104 notifies the CSMA / CA execution unit 2103 corresponding to the BK queue that a collision has occurred and increases the CW managed by the CSMA / CA execution unit 2103 corresponding to the BK queue.
[0157] The backoff / collision control unit 2104 performs controls such as notifying the CSMA / CA execution unit 2103 of changes in channel status, sending transition notifications indicating that the frequency domain used for communication has transitioned to a different frequency domain, and sending re-transition notifications indicating that the frequency domain used for communication has transitioned back to the original frequency domain. When the CSMA / CA execution unit 2103 receives a transition notification or re-transition notification, it updates the backoff parameters as necessary. The above is a description of the EDCA control. The execution of the EDCA control described above may be referred to as "performing EDCA" below.
[0158] Here, we consider the case where an access point gives station 1 a transmission opportunity by sending a Trigger frame, and then station 1 transmits data to the access point. In this case, station 1 transmits data after being given a transmission opportunity by the access point. On the other hand, suppose there is station 2 in the same frequency band that was not given a transmission opportunity by the access point. In this case, in order for station 1 and station 2 to obtain the next transmission opportunity to transmit data to the access point, station 1 must be at a disadvantage compared to station 2. This is because station 1 has already been given a transmission opportunity by the access point and has transmitted data. MU EDCA is a mechanism in multi-user uplink communication that makes it difficult for an STA that has been assigned a Resource Unit (RU) and performed uplink communication to access the channel via EDCA for a certain period of time. In other words, in the example above, after station 1 has been given a transmission opportunity by the access point and has transmitted data, in order to obtain the next transmission opportunity, it is controlled by EDCA parameters different from the EDCA parameters described above. These EDCA parameters different from the EDCA parameters described above are called MU EDCA parameters. The MU EDCA parameters may be parameters that are less favorable than the EDCA parameters described above. The MU EDCA parameters are set in the VO, VI, BE, and BK categories, and include CWmin, CWmax, AIFS, and TXOPLimit, respectively. At least one of the MU EDCA parameters CWmin, CWmax, and AIFS may be a larger value than the EDCA parameters CWmin, CWmax, and AIFS. Alternatively, the MU EDCA parameter TXOPLimit may be a smaller value than the EDCA parameter TXOPLimit. The duration for which MU EDCA is performed using the above-described MU EDCA parameters is determined by the MU EDCA Timer. When MU EDCA starts, the MU EDCA Timer countdown begins, and when the timer value reaches zero, control returns to the EDCA described above. The above is an explanation of MU EDCA.
[0159] Here, we will describe the EDCA control when performing DSO as described in this embodiment. As shown in Figures 9 to 11, STA 110 transmits data triggered by a Trigger frame (ICF frame) from AP 101. In other words, even in the case of DSO control described in this embodiment, STA 110 transmits data when given a transmission opportunity by AP 101. Therefore, after STA 110 has transmitted the data, it is controlled by EDCA parameters different from the EDCA parameters described above in order to obtain the next transmission opportunity. The EDCA parameters used after DSO execution are called DSO EDCA parameters. After STA 110 has transmitted data by the DSO control described above, it performs EDCA based on the DSO EDCA parameters. The DSO EDCA parameters may be parameters that result in less favorable conditions than the EDCA parameters described above. The DSO EDCA parameters are set in the VO, VI, BE, and BK categories, and include CWmin, CWmax, AIFS, and TXOPLimit, respectively. At least one of the DSO EDCA parameters CWmin, CWmax, and AIFS may be a larger value than the EDCA parameters CWmin, CWmax, and AIFS. Alternatively, the DSO EDCA parameter TXOPLimit may be a smaller value than the EDCA parameter TXOPLimit. The duration of EDCA using the above-mentioned DSO EDCA parameters is determined by the DSO EDCA Timer. When DSO EDCA starts, the DSO EDCA Timer countdown begins, and when the timer value reaches zero, control of EDCA returns to the above-mentioned settings. The DSO EDCA parameters and the DSO EDCA Timer values can be determined by AP101 and notified to STA110.
[0160] STA110 uses DSO control to transition AP101 to a frequency range with favorable radio wave conditions, and then AP101 is given an opportunity to transmit data. Therefore, data transmission is possible under better conditions compared to other STAs. After STA110 has performed the data transmission, it is controlled by EDCA parameters different from the EDCA parameters or MU EDCA parameters mentioned above in order to obtain the next transmission opportunity. At least one of the DSO EDCA parameters CWmin, CWmax, and AIFS may be a larger value than the CWmin, CWmax, and AIFS of the MU EDCA parameters. Alternatively, the TXOPLimit of the DSO EDCA parameter may be a smaller value than the TXOPLimit of the MU EDCA parameter. The period for performing EDCA using the above-mentioned DSO EDCA parameters is determined by the DSO EDCA Timer. When DSO EDCA is started, the DSO EDCA Timer countdown begins, and when the timer value reaches zero, control of the EDCA as described above returns. The DSO EDCA parameters and the value of the DSO EDCA Timer are determined by AP101 and can be notified to STA110.
[0161] Next, we will describe the case where, when STA110 receives the Trigger frame (ICF frame) from AP101 for the DSO control described above (901, 1001, 1002, 1101), the MU EDCA Timer countdown has already started and the timer value is not 0. In this case, STA110 takes over the timer value of the MU EDCA Timer and performs MU EDCA based on the MU EDCA parameters until the timer value becomes zero. Alternatively, STA110 does not take over the timer of the MU EDCA Timer, the MU EDCA ends, and EDCA is performed based on the DSO EDCA parameters and the value of the DSO EDCA Timer.
[0162] The DSO EDCA parameters mentioned above may be replaced with MU EDCA parameters. Similarly, the DSO EDCA Timer mentioned above may be replaced with MU EDCA Timer. In other words, instead of creating new DSO EDCA parameters and DSO EDCA Timers, the MU EDCA parameters and MU EDCA Timer may be used in DSO control.
[0163] AP101 can notify STA110 of the above-mentioned DSO EDCA parameters and DSO EDCA Timer values in Beacon frames, Probe Response frames, and Association Response frames. In other words, the above-mentioned DSO EDCA parameters and DSO EDCA Timer values are transmitted in management frames.
[0164] Let's take a Probe Response frame transmitted by an AP as an example. The Probe Response frame corresponds to F703 in Figure 7 above. Figure 22 is an example of a Probe Response frame. The Probe Response frame contains various elements in the order indicated by "Order," such as Timestamp, Beacon Interval, Capability Information, etc. The MU EDCA Parameter Set element stores parameter information for Multi-User (MU) EDCA. The UHR Capabilities element stores information about the network's or the AP's capabilities that transmit this frame, relating to IEEE 802.11bn (UHR). The UHR Operation element stores information used to control operations related to IEEE 802.11bn (UHR). The DSO EDCA Parameter Set element stores information about the parameters for EDCA in DSO. That is, it stores the DSO EDCA parameters and the DSO EDCA Timer values.
[0165] Furthermore, Probe Request frames, Association Request frames, and Association Response frames may also contain information elements similar to those in Probe Response frames. Additionally, Association Request frames and Association Response frames may include specific elements related to the association. The above describes the control of EDCA when performing DSO as described in this embodiment.
[0166] Next, we will explain the application of the DSO control described in this embodiment to multilink communication.
[0167] First, let's explain multilink communication as defined in the IEEE 802.11be standard. Multilink communication (hereinafter also referred to as "ML communication") is a technology that expands communication bandwidth and improves communication reliability by simultaneously establishing multiple wireless links between two communication devices and using these multiple links in parallel. For example, a device compliant with the multilink-compatible wireless LAN standard (MLD: Multi-Link Device) can easily achieve high throughput and fast response times that cannot be obtained with a single link by simultaneously using multiple frequency bands and channels.
[0168] More specifically, APs (Access Points) and STAs (Stations) performing ML communication each have multiple wireless interfaces. By effectively utilizing these interfaces simultaneously, it becomes possible to use another link when communication on a single link is congested, or to distribute high-load data transfers across multiple links. Furthermore, even if a problem occurs on one link, communication can continue using other links, thereby achieving fault tolerance and high reliability. Each of the multiple links can use a different frequency domain (frequency band, frequency channel).
[0169] When AP101 performs the aforementioned multilink communication (MLD) with multiple STA110s, AP101 and STA110 may enable or disable DSO for each link. That is, when multiple links are established between AP101 and STA110, DSO may be used (DSO permitted, DSO enabled) only for a specific link, while DSO is not used (disabled) or given a low priority for other links. This allows for stable maintenance of the frequency bandwidth for communications using some links where switching of frequency bandwidth is undesirable (such as communications requiring ultra-low latency), while improving frequency utilization efficiency through DSO on other links. In this case, AP101 may acquire DSO capability information for each link and then set the DSO (use DSO) according to the characteristics of that link (required bandwidth, latency characteristics, etc.). The method for acquiring DSO capability information and the process up to using DSO are as described above.
[0170] Furthermore, when STA110 performs DSO, it is conceivable that different upper limits on transmit power may be applied to each frequency domain (frequency band, frequency channel). Therefore, STA110 may maintain a maximum transmit power value or EIRP (Equivalent Isotropically Radiated Power) limit for each of the multiple frequency domains, and control the transmit power to be below a predetermined upper limit depending on the destination frequency domain indicated by AP101. STA110 may also notify AP101 of the maximum transmit power value or EIRP information set for each of the multiple frequency domains mentioned above. AP101 may then determine information related to STA110's transmit power (for example, the expected received power value mentioned above) based on this information.
[0171] Alternatively, AP101 may include a field in the trigger frame or ICF that clearly indicates the destination of the DSO along with the upper limit of the transmit power corresponding to that frequency domain. Upon receiving the information in this field, STA110 can compare the estimated propagation loss with the upper limit to determine a more appropriate transmit power value.
[0172] Furthermore, in another embodiment of the present invention, STA110, upon receiving an instruction from AP101 to move to a different frequency domain, may detect whether a portion of the destination frequency domain is being used by another system or an adjacent BSS. For example, before moving along the frequency axis, STA110 first performs a Clear Channel Assessment (CCA) in a portion of the destination frequency domain (e.g., a 20 MHz bandwidth) and transmits (reports) the result to AP101. Based on this, AP101 readjusts the frequency domain to which STA110 should actually move, thereby avoiding interference with external systems communicating in that frequency domain. In this way, by STA110 providing feedback on frequency usage to AP101 at the stage of starting DSO, stable communication can be achieved even in environments with limited frequency resources.
[0173] The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (for example, an ASIC) that implements one or more functions.
[0174] The invention is not limited to the embodiments described above, and various modifications and variations are possible without departing from the spirit and scope of the invention. Accordingly, claims are attached to disclose the scope of the invention.
[0175] This application claims priority based on Japanese Patent Application No. 2025-078510, filed on 9 May 2025, and all of its contents are incorporated herein by reference.
[0176] 101 AP 111 STA 112 STA 121 Network
Claims
1. An access point device capable of wirelessly communicating with a station device using a frame compliant with the IEEE 802.11 standard series, comprising: a frequency domain allocation means for allocating a frequency domain that does not include a primary channel from among a plurality of frequency domains to the station device; and a transmission means for transmitting a value of transmission power when transmitting a trigger frame in the frequency domain allocated by the frequency domain allocation means, and a value of reception power that the access point device expects when the station device transmits data in that frequency domain.
2. An access point device capable of wirelessly communicating with a station device using a frame compliant with the IEEE 802.11 standard series, comprising: a frequency domain allocation means for allocating a frequency domain that does not include the primary channel from among a plurality of frequency domains to the station device; and a transmission means for transmitting parameters related to EDCA (Enhanced Distributed Channel Access) performed by the station device after it has transmitted data in the frequency domain allocated by the frequency domain allocation means to the station device.
3. An access point device capable of wirelessly communicating with a station device using a frame compliant with the IEEE 802.11 standard series, comprising: an acquisition means for acquiring capability information from the station device for the station device to communicate while switching between multiple frequency domains; a frequency domain allocation means for allocating a frequency domain to the station device from among the multiple frequency domains based on the capability information acquired by the acquisition means; and a receiving means for receiving data transmitted by the station device in the frequency domain allocated by the frequency domain allocation means, wherein at least one of the multiple frequency domains does not include a primary channel, and the frequency domain allocation means allocates the frequency domain that does not include the primary channel to the station device.
4. A station device capable of wirelessly communicating with an access point device using a frame compliant with the IEEE 802.11 standard series, comprising: receiving means for receiving information from the access point device indicating that a frequency domain not including the primary channel is to be specified as the frequency domain for communication; measuring means for measuring the received power value of a trigger frame transmitted in the frequency domain specified to the station device; and transmitting power determination means for determining the transmitting power value of the station device based on the received power value measured by the measuring means.
5. A station device capable of wirelessly communicating with an access point device using a frame compliant with the IEEE 802.11 standard series, comprising a receiving means for receiving information from the access point device indicating that a frequency range not including the primary channel is to be specified as the frequency range for communication, and a station device characterized by transmitting data in the frequency range specified by the information and then performing EDCA control.
6. A station device capable of wirelessly communicating with an access point device using a frame compliant with the IEEE 802.11 standard series, comprising: a transmitting means for transmitting capability information to the access point device for performing communication while switching between multiple frequency domains; a receiving means for receiving information from the access point device indicating that a frequency domain not including the primary channel is to be specified as the frequency domain for communication; a frequency switching means for switching the frequency domain used by the station device based on the information; and a transmitting means for transmitting data using the frequency domain switched by the frequency switching means.
7. A communication method for an access point device capable of wirelessly communicating with a station device using a frame compliant with the IEEE 802.11 standard series, comprising: a frequency domain allocation step of allocating a frequency domain that does not include a primary channel from among a plurality of frequency domains to the station device; and a transmission step of transmitting a value of the transmission power when transmitting a trigger frame in the frequency domain allocated by the frequency domain allocation step, and a value of the reception power that the access point device expects when the station device transmits data in that frequency domain.
8. A communication method for an access point device capable of wirelessly communicating with a station device using a frame compliant with the IEEE 802.11 standard series, comprising: a frequency domain allocation step of allocating a frequency domain that does not include a primary channel from among a plurality of frequency domains to the station device; and a transmission step of transmitting parameters related to EDCA (Enhanced Distributed Channel Access) to the station device after the station device has transmitted data in the frequency domain allocated by the frequency domain allocation step.
9. A communication method for an access point device capable of wirelessly communicating with a station device using a frame compliant with the IEEE 802.11 standard series, comprising: an acquisition step of acquiring capability information from the station device for the station device to communicate while switching between multiple frequency domains; a frequency domain allocation step of allocating a frequency domain to the station device from among the multiple frequency domains based on the capability information acquired in the acquisition step; and a reception step of receiving data transmitted by the station device in the frequency domain allocated in the frequency domain allocation step, wherein at least one of the multiple frequency domains does not include a primary channel, and the frequency domain allocation step allocates the frequency domain that does not include the primary channel to the station device.
10. A communication method for a station device capable of wirelessly communicating with an access point device using frames compliant with the IEEE 802.11 standard series, comprising: a receiving step of receiving information from the access point device indicating that a frequency domain not including the primary channel is to be specified as the frequency domain for communication; a measuring step of measuring the received power value of a trigger frame transmitted in the frequency domain specified to the station device; and a transmitting power determination step of determining the transmitting power value of the station device based on the received power value measured in the measuring step.
11. A communication method for a station device capable of wirelessly communicating with an access point device using a frame compliant with the IEEE 802.11 standard series, comprising a receiving step of receiving information from the access point device indicating that a frequency range not including the primary channel is to be specified as the frequency range for communication, and then performing EDCA control after transmitting data in the frequency range specified by the information.
12. A communication method for a station device capable of wirelessly communicating with an access point device using a frame compliant with the IEEE 802.11 standard series, comprising: a transmission step of transmitting capability information for performing communication while switching between multiple frequency domains to the access point device; a reception step of receiving information from the access point device indicating that a frequency domain not including the primary channel is to be specified as the frequency domain for communication; a frequency switching step of switching the frequency domain to be used by the station device based on the information; and a transmission step of transmitting data using the frequency domain switched by the frequency switching step.
13. A program for causing a computer to function as each of the means of the access point device described in any one of claims 1 to 3.
14. A program for causing a computer to function as one of the means of the station device described in any one of claims 4 to 6.
