Wireless communication devices, control methods and programs

Abstract

A wireless communication device conforming to the IEEE 802.11 standard family performs the following: determining whether the primary channel of the basic service set (BSS) to which the wireless communication device belongs is busy; if the determining component determines that the primary channel is busy, transmitting an occupancy request frame for requesting to secure a transmission opportunity (TXOP) in at least one channel different from the primary channel; and performing a predetermined communication to transmit data without using the primary channel based on the response to the occupancy request frame, wherein the occupancy request frame includes predetermined information that identifies a TXOP requested for the predetermined communication.

Description

Technical Field

[0001] This invention relates to wireless communication devices, control methods, and programs that conform to the IEEE 802.11 standard. Background Technology

[0002] As a communication standard associated with wireless LANs (Wireless Local Area Networks), the IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard is known. In the IEEE 802.11be standard, or its successor, the IEEE 802.11bn standard, research has been conducted on reducing communication latency and improving channel utilization efficiency. PTL 1 describes a technique in which alternative channels are used for communication when the primary channel (PCH) intended for acquiring transmission opportunities is unavailable. Existing technical documents Patent documents

[0003] Patent Document 1: US Patent No. 11696353 Summary of the Invention The problem the invention aims to solve

[0004] To activate non-primary channel (NPCH) communication that does not include the aforementioned primary channel, notification to the receiving side and control signals for status confirmation are required. In the traditional IEEE 802.11 standard, if a control signal is detected on a channel other than the primary channel, the receiving side typically interprets it as an error. On the other hand, if a new frame is defined as in PTL 1, time overhead may occur because both the frame used to secure the transmission opportunity and the new frame need to be transmitted. Furthermore, additional signal transmission may occur because it is necessary to confirm whether the other party's wireless communication device can interpret the new frame.

[0005] As mentioned above, the convenience of performing communication without a main channel is low. Solution for solving the problem

[0006] To address the aforementioned problems, according to the present invention, a wireless communication device conforming to the IEEE 802.11 standard series is provided, comprising: The judgment component is used to determine whether the main channel of the basic service set (BSS) to which the wireless communication device belongs is in a busy state. The transmission unit is configured to, when the determination unit determines that the main channel is in the busy state, transmit an occupancy request frame for requesting to secure a transmission opportunity (TXOP) on at least one channel different from the main channel; and A communication control unit is configured to perform predetermined communication to transmit data without using the main channel, based on a response to the occupancy request frame. The occupancy request frame includes reservation information that identifies the request to secure a TXOP for the reserved communication. Advantages of the invention

[0007] According to the present invention, the convenience of performing communications that do not include the main channel can be improved.

[0008] Other features and advantages of the invention will become apparent from the following description taken in conjunction with the accompanying drawings. Note that throughout the drawings, the same reference numerals denote the same or similar components. Attached Figure Description

[0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and, together with the specification, serve to explain the principles of the invention. Figure 1 This is a diagram illustrating the configuration of a communication system according to an embodiment; Figure 2 This is a diagram illustrating the hardware configuration of a communication device according to an embodiment; Figure 3 This is a diagram illustrating the software configuration of a communication device according to an embodiment; Figure 4 This is a diagram illustrating the relationship between the MAC layer and the PHY layer; Figure 5 It is a diagram showing the arrangement of elements in a beacon frame; Figure 6A This is a diagram showing the configuration of HT operation elements; Figure 6B This is a diagram showing the structure of HT operation information; Figure 7A This is a diagram showing the configuration of VHT operation elements; Figure 7B This is a diagram showing the structure of VHT operation information; Figure 8 This is a diagram showing the configuration of the HE operation elements; Figure 9 This is a diagram showing the configuration of EHT operating elements; Figure 10 This is a diagram showing the structure of the service field for non-HT PPDUs; Figure 11 This is a diagram showing an example of how the value of TXVECTOR can be set; Figure 12A This is a diagram showing an example of how the value of RXVECTOR can be set; Figure 12B This is a diagram showing an example of how the value of RXVECTOR can be set; Figure 13AThis is a diagram showing an example of the settings for the TXVECTOR value used for NPCH communication; Figure 13B This is a diagram showing an example of the settings for the RXVECTOR value used for NPCH communication; Figure 14 This is a sequence diagram illustrating the first example; Figure 15 This is a flowchart illustrating an example of the processing performed by the AP according to the first example; Figure 16 This is a flowchart illustrating an example of a process performed by a wireless communication device on the transmission side according to the first example; Figure 17A This is a flowchart illustrating an example of the processing performed by a wireless communication device (non-AP STA) on the receiving side according to the first example; Figure 17B This is a flowchart illustrating an example of the processing performed by a receiving-side wireless communication device (non-AP STA) according to the first example; and Figure 18 This is a diagram showing the configuration of non-master operation elements. Detailed Implementation

[0010] In the following, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments are not intended to limit the scope of the claimed invention. Multiple features are described in the embodiments, but this does not limit the invention to requiring all such features, and multiple such features can be appropriately combined. Furthermore, in the drawings, the same reference numerals are given the same or similar configuration, and redundant descriptions are omitted.

[0011] <Explanation of Terms> Main Channel (PCH): In standards up to IEEE 802.11be, a 20MHz idle channel is required for transmission.

[0012] Channel Wider: A concept introduced in the IEEE 802.11n standard when a 40 MHz bandwidth is obtained by bonding to a channel adjacent to a 20 MHz channel. In this case, the original 20 MHz channel is sometimes referred to as P20 (primary 20), and the bonded channel is sometimes referred to as S20 (secondary 20). Note that bandwidth is sometimes expressed as channel width.

[0013] Bandwidth signaling: The bandwidth negotiation process introduced in the 802.11ac standard. In the IEEE 802.11be standard, bandwidths up to 320 MHz can be used.

[0014] Non-Master Channel (NPCH) communication: Communication that is performed even when the PCH is busy (not idle). In NPCH communication, there is no guaranteed bandwidth in the PCH.

[0015] SPCH (Secondary Primary Channel): A 20 MHz channel that replaces PCH in NPCH communication.

[0016] <Configuration of the Communication System> Reference Figure 1 The configuration of the wireless communication system 1 according to this embodiment is described.

[0017] The wireless communication system 1 includes access points (APs) 101 and 104 (hereinafter referred to as APs without distinction); terminals (STAs) 102, 103, 105 and 106 (hereinafter referred to as STAs without distinction); and a distributed system (DS) 107.

[0018] AP 101 and 104 are configured to work with... Figure 1 A wireless communication device that communicates with a terminal (STA) located in the area indicated by the circle. Figure 1 In the diagram, a solid-line circle indicates the feasible range (service area) for communication with AP 101, and a dotted-line circle indicates the feasible range for communication with AP 104. Note that in... Figure 1 In the example shown, STAs 102, 103, and 106 exist in the service area of ​​AP 101, and STAs 103, 105, and 106 exist in the service area of ​​AP 104, but the number of STAs is unlimited. APs 101 and 104 each manage a Basic Service Set (BSS), and the BSS managed by AP 104 is the Overlapping Basic Service Set (OBSS) for AP 101.

[0019] STAs 102, 103, 105, and 106 are wireless communication devices each connected to an AP for communication. STAs are also called non-access point terminals (non-AP STAs). In this embodiment, the description will assume that STAs 102 and 103 are connected to AP 101 and STAs 105 and 106 are connected to AP 104. Note that in this embodiment, STAs 102 and AP 104 are in a hidden terminal state. AP 101 and STAs 102 and 103 can perform data communication by exchanging wireless frames conforming to the IEEE 802.11bn standard, which is the successor to the IEEE 802.11be standard with a target maximum transmission speed of 46.08 Gbps. Furthermore, AP 104 and STAs 105 and 106 can also perform data communication by exchanging wireless frames conforming to the IEEE 802.11bn standard. The main features of the IEEE 802.11bn standard, the successor to IEEE 802.11be, are high-reliability communication, low-latency communication, and improved throughput under congestion. Radio frames used in communication in the successor standard will also be referred to as UHR (Ultra-Reliable) PPDUs. PPDU is an abbreviation for Physical Layer Protocol Data Unit. Note that the name UHR is a convenient designation given the goals to be achieved in the successor standard or its main features, and may be different when the standard is finalized. Similarly, the name IEEE 802.11bn may also be different when the standard is finalized. On the other hand, note that this specification and the appended claims substantially apply to all successor standards that are successors to the 802.11be standard. It is assumed that individual devices support communication (transmission / reception) of UHR PPDUs and are also configured to support communication of PPDUs of the legacy standards that preceded the UHR standard. More specifically, AP 101 and STA 102 are configured to support the transmission / reception of PPDUs conforming to the IEEE 802.11a / b / g / n / ac / ax / be standards. Furthermore, in this embodiment, PPDUs corresponding to standards prior to the IEEE 802.11n standard (High Throughput Standard) will be referred to as non-HT PPDUs.

[0020] The DS 107 is a network device that provides Distributed System Access Function (DSAF) to APs 101 and 104. It can connect not only to the BSS managed by APs 101 and 104, but also to other BSSs or external networks. This access function can be via wired communication, such as Ethernet. ®Alternatively, the access function can be a telephone network, etc. Or, wireless communication such as LTE (Long Term Evolution) or WiMAX (Global Microwave Access Interoperability). Furthermore, it can be a wireless LAN compliant with the IEEE 802.11 standard. In this case, the wireless channel used in communication between the DS 107 and the AP can be the same as, or different from, the wireless channel used in communication between the AP and the STA.

[0021] Figure 2 A hardware configuration suitable for a wireless communication device including an AP and a STA according to this embodiment is shown. As an example of the hardware configuration, the wireless communication device includes a storage unit 201, a control unit 202, a functional unit 203, an input unit 204, an output unit 205, a communication unit 206, and an antenna 207.

[0022] Storage unit 201 is formed of a memory such as read-only memory (ROM) or random access memory (RAM), and stores programs configured to perform various operations described later, as well as various information such as communication parameters for wireless communication. Note that storage unit 201 may be used instead of memory such as ROM or RAM, or in addition to such memory, storage media such as floppy disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, magnetic tapes, non-volatile memory cards, or DVDs. Furthermore, storage unit 201 may include the aforementioned multiple memories.

[0023] The control unit 202 is formed, for example, by a processor (such as a central processing unit (CPU) or microprocessor unit (MPU), an ASIC (Application-Specific Integrated Circuit), a DSP (Digital Signal Processor), or a FPGA (Field-Programmable Gate Array). The control unit 202 controls the operation of the entire AP by executing a program stored in the storage unit 201. Note that the control unit 202 can control the operation of the entire AP through the cooperation of the program stored in the storage unit 201 and the OS (Operating System). Alternatively, the control unit 202 may include multiple processors, such as a multi-core processor, and control the operation of the entire AP.

[0024] In addition, the control unit 202 controls the function unit 203 to perform the AP function or STA function of the function unit 203 or predetermined processing such as camera, printing or projection.

[0025] Functional unit 203 is hardware used by the AP or STA to perform predetermined processes. In the example, functional unit 203 may have functions such as AP function, STA function, camera function, printing function, and projection function. If the wireless communication device has at least one of the camera function, printing function, and projection function, then the wireless communication device may be a multifunction printer or a projector.

[0026] Input unit 204 includes an input interface configured to accept various operations from the user. Output unit 205 includes an output interface configured to provide various outputs to the user. Here, the outputs using output unit 205 include at least one of on-screen display, audio output via speaker, and vibration output. Note that the functions of both input unit 204 and output unit 205 can be implemented by a single module, similar to a touch panel.

[0027] Communication unit 206 controls wireless communications compliant with the IEEE 802.11 series and Wi-Fi compliant. ® The communication unit 206 transmits / receives wireless signals for wireless communication by controlling the antenna 207. In other words, the communication unit 206 and the antenna 207 cooperate to transmit / receive wireless frames such as the aforementioned UHR PPDU.

[0028] exist Figure 2 For simplicity, antenna 207 includes a single antenna, but it may include multiple antennas. Typically, antenna 207 includes a number of antennas corresponding to the number of spatial flows. Note that communication unit 206 and antenna 207 each include a number of radio frequency (RF) chains corresponding to the corresponding frequency bands (2.4 GHz band, 5 GHz band, and 6 GHz band) and the number of corresponding flows.

[0029] Figure 3 The software configuration of a wireless communication device is illustrated. As an example, the wireless communication device includes a wireless LAN control unit 301, an NPCH communication control unit 302, a punched communication control unit 303, a bandwidth control unit 304, a 20MHz communication control unit 305, and a storage unit 306. The wireless communication device also includes a user interface (UI) control unit 307 and an antenna control unit 308.

[0030] The wireless LAN control unit 301 is configured to include circuitry configured to transmit wireless signals to / receive wireless signals from other wireless LAN devices (e.g., other APs or STAs), and programs for controlling these circuitry. Through the wireless LAN control unit 301, wireless communication devices perform wireless LAN communication control according to the IEEE 802.11 standard family, such as frame generation, frame transmission, or reception of wireless frames from other wireless communication devices.

[0031] When the PCH is busy, the NPCH communication control unit 302 attempts to control the communication in the NPCH.

[0032] The punch communication control unit 303 performs communication in a configuration in which the signal including the preamble is not present on a 20 MHz channel adjacent to a certain bandwidth.

[0033] The bandwidth control unit 304 performs communication by binding a 20 MHz channel. With a communication bandwidth of 20 MHz, the 20 MHz communication control unit 305 performs NPCH communication.

[0034] Storage unit 306 is configured to include storage devices such as ROM or RAM for storing programs to be executed by the AP and various data.

[0035] The UI control unit 307 is configured to include hardware associated with a user interface (UI), such as a touch panel and buttons for accepting user operations on the wireless communication device, and a program configured to control this hardware. Note that the UI control unit 307 may also have functions for presenting information to the user (e.g., displaying images and audio output). The antenna control unit 308 controls antenna functions.

[0036] Figure 4 The relationship between the MAC layer and the PHY layer is shown in the diagram, where the Physical Layer Protocol Data Unit (PPDU) is a frame conforming to the IEEE 802.11 standard.

[0037] Training Symbol 401 is a 2-octet field serving as the training symbol. Here, an octet indicates the data size like a byte, and one octet equals 8 bits. Header 402 is a 2-octet field serving as the Physical Layer (PHY) header. Details will be described later with reference to fields 406 through 411. Physical Service Data Unit (PSDU) 403 indicates the data unit of the service provided by the PHY to the upper layer (MAC layer) and is a 6-octet field.

[0038] Tail Bit 404 is a 0 or 6 octet field indicating the tail bit of the PDU. Padding 405 is the padding for the PPDU and is a 0 or 6 octet field.

[0039] RATE 406 is a 4-bit field storing data indicating the frame transmission rate. Reserved 407 is a reserved area (1 bit long). LENGTH 408 is a 12-bit field indicating the frame length. Parity 409 is a 1-bit field indicating a code calculated / added to detect errors occurring during frame transmission. Trailer 410 is a 6-bit field that serves as the tail bit of the PHY header. Services 411 is a 12-bit services field.

[0040] The structure of the MAC frame stored in PSDU 403 will be described next. Frame control 412 is a 2-byte frame control field that includes 10 subfields and indicates the type and direction of transmission, such as management / control / data.

[0041] Duration 413 is a field with a length of 2 octets and indicates the length of a predetermined time period. For example, Duration 413 indicates the length of a frame or the length of a Transmission Opportunity (TXOP) period requested to be secured by a frame. The most significant bit (MSB: B15) of Duration 413 is set to "1", and the remaining 15 bits indicate the time length from 0 to 32767 μsec.

[0042] Addresses 1 through 4 (414, 415, 416, and 418) are each a 6-byte field used to set the BSS identifier (BSSID) or the address of the source or destination terminal, depending on the MAC frame type. Addresses 2 through 4 are not included in the frame, depending on the frame type. In the following explanation, addresses 1 (414), 2 (415), 3 (416), and 4 (418) are sometimes referred to indiscriminately as the address fields.

[0043] Serial control 417 is a 2-octet field used for sequence control. Depending on the frame type, serial control 417 is not included in the frame.

[0044] QoS Control 419 is a 0 or 2 octet field used for QoS control of data frames. In standards prior to IEEE 802.11ax, the Buffer Status Report (BSR) was stored in QoS Control 419.

[0045] The HT control (HTC) 420 is a field of 0 or 4 octet bytes that includes control information associated with high throughput (HT) or ultra-high throughput (VHT).

[0046] The Frame Body 421 is a variable-length field that stores various information elements (IEs) in the case of a frame control 412 type indicating the management frame (i.e., a beacon or probe request / response).

[0047] The Frame Check Sequence (FCS) 422 is a 4-octet field that is stored to check whether the MAC header or data portion does not contain erroneous values.

[0048] TXVECTOR 423 and RXVECTOR 424 indicate how MAC frames are transmitted between the MAC layer and the PHY layer in the IEEE 802.11 standard. For example, the MAC layer instructs the PHY layer how to transmit MAC frames using parameters (TXVECTOR parameters). Conversely, the PHY layer instructs the MAC layer how to receive MAC frames using parameters (RXVECTOR parameters). An example parameter is CH_BANDWIDTH, which indicates the bandwidth.

[0049] Notice, Figure 4 The format of the PHY layer shown varies according to standards, and the format of a non-high-throughput (HT) PPDU is shown here. The term "non-HT" indicates that this format predates the IEEE 802.11n standard (High Throughput Standard). The non-HT format is used in control frames that request to transmit (RTS) or allow to transmit (CTS), where RTS is an occupancy request frame requesting assurance of transmission opportunities, and CTS is an occupancy response frame to the occupancy request frame. Furthermore, in the case of a non-HT PPDU, MAC layer QoS control 419 and HT control 420 are not present in the MAC frame.

[0050] Reference Figures 5 to 12A and Figure 12B This describes the notifications regarding the PCH and bandwidth. These operational elements, managed by IEEE 802.11 management frames, are shown in the Basic Service Set (BSS).

[0051] Figure 5 The arrangement of the elements in a beacon frame is shown. These elements are also called information elements (IEs). The sequence indicates their order within the beacon frame body, and the information indicates the name of the information element. Within these elements, information related to channel operation, along with the evolution of the IEEE 802.11 standard, is distributed to several operational elements.

[0052] Figure 6A and Figure 6B The configuration of an HT operating element conforming to the IEEE 802.11n standard is shown.

[0053] The primary channel 601 is an octet field that indicates the primary channel number. The HT operation information 602 is a 5-octet field. The secondary channel offset 603 is a 2-bit field that indicates the frequency relative position of the secondary channel to the primary channel or the presence / absence of the secondary channel. The STA channel width 604 is a 1-bit field indicating whether the bandwidth of the transmitted PPDU is 20 MHz.

[0054] Figure 7A and Figure 7BThe configuration of the Ultra High Throughput (VHT) operating element of the IEEE 802.11ac standard is shown. Figure 7B It is shown Figure 7A The diagram shows the configuration of the VHT operation information fields.

[0055] VHT Operation Information 701 is a 3-octet field that serves as channel-related information.

[0056] Channel width 702 is an octet field indicating whether the bandwidth is 20 or 40 MHz, 80 MHz or 160 MHz or 80+80 MHz, 160 MHz or 80+80 MHz. Channel center band 0 703 and channel center band 1 704 are each an octet field indicating the center frequency of the channel.

[0057] In the IEEE 802.11ac standard, a 160MHz band can be transmitted by combining two non-contiguous 80 MHz bands. Therefore, the center frequencies of bands not exceeding 80 MHz and 160 MHz or 80+80 MHz are indicated by the values ​​of channel center bands 703 and 704.

[0058] Note that the IEEE 802.11ac standard introduced signaling for bandwidth using the RTS. This is the process of placing bandwidth information in the RTS (not HT PPDU format) and using the TA (transmitter address, i.e., address 2415) as the group address. Here, the bandwidth information is indicated by the bits corresponding to CH_BANDWIDTH_IN_NON_HT and DYN_BANDWIDTH_IN_NOT_HT in the service field of the PHY header. Furthermore, the group address is obtained by setting the individual / group bit in the MAC address structure to "1".

[0059] Figure 8 The high-efficiency (HE) operating elements of the IEEE 802.11ax standard are shown.

[0060] HE operation parameter 801 is a 3-octet field storing the parameters for the HE operation. VHT operation information 802 is a 0- or 3-octet field storing the parameters for the VHT operation. 6 GHz operation information 803 is a 0- or 5-octet field storing information indicating the channel information for the 6 GHz band available from IEEE 802.11ax onwards.

[0061] The presence / absence of VHT operation information 802 and 6 GHz operation information 803 is indicated by the corresponding field (1 bit) of HE operation parameter 801.

[0062] The main channel 804 is an octet field that indicates the main channel of the 6 GHz band.

[0063] Control 805 is an octet field that includes channel width 808, repeating beacon 809, and regulatory information 810, which will be described later.

[0064] The channel center band 0 806 and the channel center band 1 807 are each an octet field that stores information indicating the center frequency of the channel, similar to the fields present in VHT operations.

[0065] Channel width 808 is a 2-bit field indicating which of the following is the channel width: 20 / 40 / 80 / 160 MHz. Repeat beacon 809 is a 1-bit field indicating whether a different channel should be used to transmit beacon frames with the same BSSID. Regulatory information 810 is a 3-bit field indicating regulatory or restrictive provisions regarding wireless communication specifications in a specific area.

[0066] Figure 9 The configuration of the EHT operating elements of the IEEE 802.11be standard (draft 4.1) is shown.

[0067] EHT Operation Information 901 is a field of 0, 3, or 5 octet bytes for Storage Control 902, CCFS0 903, CCFS1 904, and Disabled Subchannel Bitmap 905.

[0068] Control 902 is an octet of control field that stores the channel width 906, which will be described later.

[0069] CCFS0 903 is an octet field that indicates the center frequency when the bandwidth is 80 MHz or less. If the bandwidth is 160 MHz, CCFS0 903 indicates the center frequency of the primary channel at 80 MHz. If the bandwidth is 320 MHz, CCFS0 903 indicates the center frequency of the primary channel at 160 MHz. CCFS1 904 indicates the center frequency of the secondary channel when the bandwidth is 160 or 320 MHz.

[0070] The disabled subchannel bitmap 905 is a 2-octet field that uses each of the 16 bits to indicate a 20 MHz channel that is not used (set to punch state) in a bandwidth of up to 320 MHz.

[0071] The channel width 906 is a 3-bit field that uses 3 bits to indicate which of the following is the channel width: 20 / 40 / 80 / 160 / 320 MHz.

[0072] Figure 10The service fields of the non-HT PPDU and the parameters of TXVECTOR / RXVECTOR are shown, especially the relationship between CH_BANDWIDTH_IN_NON_HT and DYN_BANDWIDTH_IN_NON_HT.

[0073] Column 1001 indicates the first 7 bits of service 411 of the non-HT PPDU. In the first 7 bits of service 411, column 1002 indicates 4 bits from bit 0 (B0) to bit 3 (B3), column 1003 indicates bit 4 (B4), and column 1004 indicates 2 bits from bit 5 (B5) to bit 6 (B6).

[0074] Line 1005 indicates the 7-bit configuration in TXVECTOR (i.e., the transfer from the MAC layer to the PHY layer) when CH_BANDWIDTH_IN_NON_HT is present and DYN_BANDWIDTH_IN_NON_HT is absent.

[0075] Line 1006 indicates the 7-bit configuration in TXVECTOR when CH_BANDWIDTH_IN_NON_HT and DYN_BANDWIDTH_IN_NON_HT are present.

[0076] Line 1007 indicates the 7-bit configuration in RXVECTOR when CH_BANDWIDTH_IN_NON_HT and DYN_BANDWIDTH_IN_NON_HT are present.

[0077] Figure 11 This is a graph showing the relationship between the 3-bit value of CH_BANDWIDTH_IN_NON_HT of TXVECTOR and the channel bandwidth (CBW). If the value of CH_BANDWIDTH_IN_NON_HT is 1, it indicates 40 MHz (CBW40), a value of "2" indicates 80 MHz (CBW80), a value of "3" indicates 160 MHz (CBW160 or CBW80+80), and a value of "4" indicates 320 MHz (CBW320).

[0078] Figure 12A and Figure 12B The relationship between CH_BANDWIDTH_IN_NON_HT and CH_BANDWIDTH_IN_NON_HT_INDICATOR is shown. Figure 12A The values ​​of CH_BANDWIDTH_IN_NON_HT for VHT(802.11ac)STA or HE(802.11ax)STA are shown. Figure 12BThe value of CH_BANDWIDTH_IN_NON_HT for EHT(802.11be)STA is shown.

[0079] Figure 12A Column 1201 indicates the value of the CH_BANDWIDTH_IN_NON_HT_INDICATOR field for the first 7 bits of the scrambling sequence. Column 1202 indicates the value of dot11CurrentChannelCenterFrequencyIndex1 (dot11 Current Channel Center Frequency Index 1). Column 1203 indicates the CH_BANDWIDTH_IN_NON_HT value associated with the values ​​in columns 1201 and 1202.

[0080] like Figure 12A As shown, if the value of CH_BANDWIDTH_IN_NON_HT_INDICATOR is 0, it indicates 20 MHz (CBW20); a value of "1" indicates 40 MHz (CBW40); and a value of "2" indicates 80 MHz (CBW80). When the value of CH_BANDWIDTH_IN_NON_HT_INDICATOR is 3, if the value of dot11CurrentChannelCenterFrequencyIndex1 is 0, it indicates 160 MHz (CBW160). When the value of CH_BANDWIDTH_IN_NON_HT_INDICATOR is 3, if the value of dot11CurrentChannelCenterFrequencyIndex1 is not 0, it indicates 80 MHz + 80 MHz (CBW80 + 80).

[0081] Figure 12B Column 1211 indicates the values ​​of bits 0 and 1 of the CH_BANDWIDTH_IN_NON_HT_INDICATOR field for the first 7 bits of the scrambling sequence. Column 1212 indicates the value of bit 2 of the CH_BANDWIDTH_IN_NON_HT_INDICATOR field. Column 1213 indicates the CH_BANDWIDTH_IN_NON_HT value associated with the values ​​in columns 1211 and 1212.

[0082] like Figure 12BAs shown, if bits 0 and 1 of CH_BANDWIDTH_IN_NON_HT_INDICATOR are both 1, it indicates 40 MHz (CBW40). If bits 0 and 1 of CH_BANDWIDTH_IN_NON_HT_INDICATOR are both 2, it indicates 80 MHz (CBW80), and a value of "3" indicates 160 MHz (CBW160). If bits 0 and 1 of CH_BANDWIDTH_IN_NON_HT_INDICATOR are both 0 and bit 2 is 0, then CH_BANDWIDTH_IN_NON_HT indicates 20 MHz (CBW20). If bits 0 and 1 of CH_BANDWIDTH_IN_NON_HT_INDICATOR are both 0 and bit 2 is 1, then CH_BANDWIDTH_IN_NON_HT indicates 320 MHz (CBW320).

[0083] Figure 13A This is a table showing the relationship between the 4-bit value of CH_BANDWIDTH_IN_NON_HT of TXVECTOR used for NPCH communication and CBW (channel bandwidth). Columns 1101 to 1103 are referenced. Figure 11 The descriptions of columns 1101 to 1103 are the same, and their descriptions will be omitted.

[0084] Column 1301 indicates bit 3 of CH_BANDWIDTH_IN_NON_HT_INDICATOR, and this is the bit that is set to "1" in NPCH communication. That is, in NPCH communication, as... Figure 11 As shown, bit 3, which is set to "0" and is unused in PCH communication, is given meaning. That is, bit 3 of CH_BANDWIDTH_IN_NON_HT_INDICATOR is treated as information that can identify that the frame is an RTS used for NPCH communication. However, column 1302 indicates the value of CH_BANDWIDTH_IN_NON_HT.

[0085] exist Figure 13A In the example shown, if the 4-bit value of CH_BANDWIDTH_IN_NON_HT is 8, it indicates a bandwidth of 20 MHz (CBW20), and if the value is 9, it indicates a bandwidth of 40 MHz (CBW40). Furthermore, if the value is 10, it indicates a bandwidth of 80 MHz (CBW80), if the value is 11, it indicates a bandwidth of 160 MHz or 80+80 MHz (CBW160 or CBW80+80), and if the value is 12, it indicates a bandwidth of 320 MHz (CBW320).

[0086] Figure 13B This is a table showing the relationship between the 4-bit value of CH_BANDWIDTH_IN_NON_HT of RXVECTOR used for NPCH communication and CBW (channel bandwidth). Columns 1211 to 1213 and references... Figure 12B The descriptions of columns 1211 to 1213 are the same, and their descriptions will be omitted.

[0087] Column 1311 indicates bit 3 of CH_BANDWIDTH_IN_NON_HT_INDICATOR, and this is the bit that is set to "1" in NPCH communication. That is, like column 1301, in NPCH communication, bit 3, which is set to "0" and is not used in PCH communication, is given meaning.

[0088] exist Figure 13B In the example shown, if the 4-bit value of CH_BANDWIDTH_IN_NON_HT is 8, the bandwidth indicates 20 MHz (CBW20), and if the value is 9, the bandwidth indicates 40 MHz (CBW40). Furthermore, if the value is 10, the bandwidth indicates 80 MHz (CBW80), if the value is 11, the bandwidth indicates 160 MHz (CBW160), and if the value is 12, the bandwidth indicates 320 MHz (CBW320).

[0089] <Example 1> Figure 14 An operational sequence diagram according to a first example of this embodiment is shown. Figure 14 The operation is shown in the following cases: Figure 1 In the configuration shown, when a transfer is made from AP 101 to STA 103, AP 104 in OBSS transfers RTS to STA 105 and operates as a TXOP holder.

[0090] Channels 1401 to 1404 schematically represent 20 MHz channels.

[0091] AP 101 pre-broadcasts operational element 1405, which includes BSS channel usage information. In this example, the primary channel is channel 1401 with a bandwidth of 80 MHz, and channels 1401 to 1404 are used.

[0092] Next, AP 104 transmits RTS 1406 to STA 105. This ensures the TXOP period 1407. Typically, the length of TXOP period 1407 corresponds to the time specified in the duration field of RTS 1406.

[0093] AP 101 sets NAV (Network Assignment Vector) 1408 by detecting RTS 1406 transmitted from AP 104. NAV, also known as a transmission prohibition period, prohibits transmission on channel 1401 for the time specified in the duration field of RTS 1406. STA 103 can also detect RTS 1406 transmitted from AP 104 and therefore sets NAV 1409 on channel 1401, just like AP 101. If the receiving side of AP 101 is STA 102, then... Figure 1 In the terminal arrangement shown, STA102 does not detect signals from AP 104 (i.e., STA 102 and AP 104 maintain a hidden terminal relationship). Therefore, STA 102 does not set NAV.

[0094] The transmission / reception of frames from RTS 1406 onwards in OBSS (i.e., frames from CTS onwards transmitted from STA 105, which is the TXOP responder, to AP 104) will be omitted from the description.

[0095] Following the NAV setup, AP 101 decides to perform NPCH communication, selects a channel other than PCH from the 80 MHz band, and begins backoff (BO) counter control 1410. Here, BO counter control 1410 is performed on channel 1402, but other channels 1403 or 1404 can be used.

[0096] The idle state of channel 1402 continues, and channels 1403 and 1404 are idle during Priority Inter-Frame Spacing (PIFS) 1411 and 1412 before the counter of BO counter control 1410 becomes zero. In this case, AP 101 uses channels 1402 to 1404 to transmit RTS 1413 to 1415 for NPCH communication, respectively.

[0097] STA 103, having received RTS 1413 to 1415 from AP 101, confirms the idle status of each channel and then transmits CTS 1416 to 1418 to AP 101. In this example, three channels are determined to be idle. However, sometimes it may be determined that one of the channels is busy. In this case, CTS is not transmitted on the busy channel.

[0098] AP 101 determines the puncturing channel information 1419 of the preamble based on the channel to which the CTS is received. Therefore, the PHY header of the 80 MHz PPDU indicates that channel 1401 is in a punctured state 1420. Note that if a CTS corresponding to one of channels 1402 to 1404 is not returned, the channel for which no CTS has been transmitted is also set to a punctured state. Immediately following the preamble, AP 101 transmits the PSDU 1421 of the PPDU.

[0099] If the data can be decoded normally, then STA 103 has received a block acknowledgment (BlockAck) (BA)1422 from AP 101 via PSDU 1421.

[0100] As mentioned above, even when the PCH is busy, AP 101 can use NPCH instead of PCH to transmit data to STAs in the BSS.

[0101] Figure 15 This is a flowchart illustrating an example of BSS channel operation setup processing performed by AP 101. In step S1500, AP 101 begins BSS management frame processing. BSS management frame processing is performed at, for example, predetermined time intervals. Figure 15 In the process shown, AP 101 determines the conditions associated with operations such as the use of channels and bandwidth in the BSS, and broadcasts information in the BSS using management frames such as beacons or action frames.

[0102] In step S1501, AP 101 determines the PCH. In step S1502, AP 101 determines the bandwidth to be used in communication. Note that these decisions can be made based on settings performed by the administrator of AP 101 or settings maintained in storage unit 201.

[0103] In step S1503, AP 101 determines whether to permit NPCH communication within the BSS. In step S1504, AP 101 constructs the operational element and broadcasts it via a beacon. Through the beacon signal, AP 101 can notify non-access point terminals (non-AP STAs) whether NPCH is permitted.

[0104] In step S1505, AP 101 notifies NPCH communication of information. This notification can be broadcast by including the information in element 505 of the beacon, or it can be done using a newly defined action frame.

[0105] Figure 16 This is a flowchart illustrating an example of the processing performed by the wireless communication device on the transmission side. That is, Figure 16The flowchart is common to both the AP and STA. If transmission data is generated, then the following steps are performed. Figure 16 The process shown is (step S1600).

[0106] In step S1601, the wireless communication device detects that the terminal in the OBSS is the TXOP holder of the main channel. For example, when an RTS signal from a terminal in the OBSS is detected on the main channel, it can be determined that the terminal in the OBSS is the TXOP holder of the main channel.

[0107] In step S1602, the wireless communication device sets the NAV for the BSS and starts the NAV timer. Note that in this embodiment, spatial reuse introduced in IEEE 802.11ax is not operated. Therefore, control via the two types of NAVs (basic NAV and intra-BSS NAV) is not performed, and the NAV set in step S1602 is synonymous with the basic NAV.

[0108] In step S1603, the wireless communication device decides whether to attempt NPCH communication. In step S1603, for example, if the PCH is busy, it can be determined that NPCH communication should be attempted. In another example, in step S1603, if an RTS from the OBSS is detected, it can be determined that NPCH communication should be attempted. To attempt NPCH communication (Yes in step S1603), the wireless communication device advances the process to step S1604 to determine the channel for transmitting the RTS used to activate NPCH communication. This process corresponds to 1410 in sequence. On the other hand, if it is decided not to attempt NPCH communication (No in step S1603), the wireless communication device advances the process to step S1615 to perform conventional communication control using the PCH.

[0109] In step S1605, the wireless communication device constructs a preamble and MAC frame for the RTS (Record of Time) used for NPCH communication. This preamble reflects the TXVECTOR notified from the MAC layer to the PHY layer. More specifically, the preamble is formed by setting "1" to bit 3 of the 4 bits corresponding to CH_BANDWIDTH_IN_NON_HT. Furthermore, the duration of the RTS in NPCH communication is shorter than the NAV (Non-Active Time) period via OBSS. This is because NPCH communication is defined as communication permitted only during the NAV setting period via OBSS.

[0110] In step S1606, the wireless communication device performs backoff control to transmit the RTS for requesting secure TXOP communication for the NPCH, and determines whether a channel in the NPCH is idle until the backoff counter becomes zero. If the backoff counter becomes zero while a channel in the NPCH remains idle, the wireless communication device uses that channel to transmit the RTS (step S1608). Simultaneously, the RTS can be transmitted even in NPCHs that are idle during the Priority Inter-Frame Spacing (PIFS) before the backoff counter becomes zero. Here, the NPCH for transmitting the RTS is specified by the channel width notified by the operating element.

[0111] Next, the wireless communication device receives a CTS as a response to the RTS transmitted in step S1608 (step S1608). Note that, as described above, the wireless communication device on the other side that has received the RTS only transmits the CTS on channels that are idle. Therefore, the wireless communication device receives the CTS on the NPCH where the RTS has already been transmitted (step S1608) and identifies the channel on which the CTS has been received. The wireless communication device creates puncturing channel information that invalidates the individual channels that have not yet received the CTS, and constructs a PHY header for data transmission (step S1609). Note that in draft 4.1 of the IEEE 802.11be standard, the number of bits used for transmitting puncturing channel information in the U-SIG of the PHY header is 5. In a 5-bit area, it may not be possible to represent the puncturing pattern of any 20 MHz channel within 320 MHz. In this case, a puncturing pattern that makes communication on channels that have already received the CTS as valid as possible is selected. Furthermore, the PPDU format can be extended to indicate more flexible puncturing. In this configuration, the PPDU used for data communication is configured as a PPDU for Ultra-High Reliability (UHR), and a new 16-bit field for transmission puncturing is defined in the UHR-SIG, which is a unique PHY header specific to UHR. This 16-bit field is simply a bitmap area indicating whether a particular 20 MHz subband is enabled or disabled.

[0112] Subsequently, the wireless communication device transmits a PPDU including the constructed PHY header to the other wireless communication device (step S1610). As described above, the channel through which the PPDU is transmitted is the channel in NPCH where a CTS has already been received. After the PPDU is transmitted, the wireless communication device receives a Block Acknowledgment (BA) (step S1611) and terminates NPCH communication (step S1612). The PPDU transmitted in step S1610 is, for example, a UHR PPDU of the IEEE 802.11bn standard. Note that the PPDU can also be an EHT (Extremely High Throughput) PPDU of the IEEE 802.11be standard.

[0113] Figure 17A and Figure 17B This is a flowchart illustrating an example of processing performed by a non-AP STA operating as a receiving wireless communication device. The following processing is implemented by the non-AP STA's control unit 202 executing a program stored in the storage unit 201.

[0114] Control unit 202 waits for signals from other wireless communication devices at a predetermined time. If a non-AP STA receives a management frame including a beacon or action frame (Yes in step S1701), control unit 202 advances the process to step S1702; if no management frame is received (No in step S1701), control unit 202 advances the process to step S1703.

[0115] In step S1702, the control unit 202 acquires the operational elements included in the beacon or action frame. The acquired object element is a reference... Figures 6A to 9 and Figure 18 The information elements described. In step S1703, the control unit 202 determines whether an RTS conforming to the standard up to the IEEE 802.11n standard has been received. If it is determined that an RTS conforming to the standard up to the IEEE 802.11n standard has been received (Yes in step S1703), the control unit 202 checks whether the channel receiving the RTS is in an idle state (step S1704). If it is determined that the channel receiving the RTS is in an idle state (Yes in step S1704), the control unit 202 proceeds the process to step S1705. If it is determined that the channel is not in an idle state (No in step S1704), the control unit 202 proceeds the process to step S1713. In step S1705, the control unit 202 uses the channel receiving the RTS to prepare for the transmission of a CTS conforming to the standard up to the IEEE 802.11n standard.

[0116] In step S1706, control unit 202 determines whether an RTS for legacy bandwidth signaling has been received. Here, "legacy" means "up to 802.11be draft 4.1". That is, in step S1706, it is determined whether it is an RTS requesting to ensure TXOP in one or more channels including the primary channel. If it is determined that an RTS for bandwidth signaling has been received (yes in step S1706), control unit 202 proceeds the process to step S1707. If it is determined that no RTS for bandwidth signaling has been received (no in step S1706), control unit 202 proceeds the process to step S1709.

[0117] In step S1707, the control unit 202 determines whether the channel receiving the RTS is in an idle state. If it is determined that the channel receiving the RTS is in an idle state (Yes in step S1707), the control unit 202 proceeds the process to step S1708. If it is determined that the channel is not in an idle state, the control unit 202 proceeds the process to step S1713.

[0118] In step S1708, the control unit 202 uses the channel that receives the RTS to prepare for the transmission of CTS for RTS used for conventional bandwidth signaling.

[0119] In step S1709, the control unit 202 determines whether an RTS for NPCH communication has been received. This determination is based on the RXVECTOR notified from the PHY layer to the MAC layer. More specifically, it determines whether bit 3 of the 4 bits corresponding to CH_BANDWIDTH_IN_NON_HT_INDICATOR is set to "1". Note that in this embodiment, the RTS for NPCH communication is not transmitted on the PCH. If it is determined that an RTS for NPCH communication has been received (Yes in step S1709), the control unit 202 proceeds the process to step S1710. If it is determined that no RTS for NPCH communication has been received (No in step S1709), the control unit 202 proceeds the process to step S1712.

[0120] In step S1710, the control unit 202 determines whether the channel receiving the RTS for NPCH communication is idle. If it is determined that the channel receiving the RTS for NPCH communication is idle (Yes in step S1710), the control unit 202 proceeds the process to step S1711. If it is determined that the channel is not idle (No in step S1710), the control unit 202 proceeds the process to step S1713. Note that if it is determined in step S1710 that at least one of the multiple channels is idle, the control unit 202 proceeds the process to step S1711. In step S1711, the control unit 202 uses the channel receiving the RTS to prepare for the transmission of the CTS for NPCH communication.

[0121] In step S1712, the control unit 202 performs reception processing for frames other than beacons or RTS.

[0122] In step S1713, control unit 202 uses various 20 MHz channels to transmit the CTS prepared in steps S1705, S1708, or S1711. For example, if no CTS is prepared, control unit 202 may not transmit the CTS. In step S1714, control unit 202 receives PPDUs on the channels used to transmit CTSs. Note that, depending on the return status of the CTS, one or more channels are used to receive PPDUs without a PHY header. The absence of a PHY header can be identified by control unit 202 analyzing the punched channel information of the PHY header. If the PPDU reception is completed normally, control unit 202 transmits the BA (step S1715) and returns the processing to step S1701. Note that in Figure 17A and Figure 17B If the wireless communication device on the receiving side is an AP, then instead of the processing in steps S1701 and S1702, the AP determines the operation elements and transmits beacons including these operation elements.

[0123] Note that in steps S1703 and S1706, the condition that an RTS is received on the PCH is considered an RTS reception. For this reason, if a conventional standard RTS is received but no RTS is received on the PCH, it can be considered an error. On the other hand, in step S1709, the receiving wireless communication device can identify that an RTS has not been transmitted on the PCH. Therefore, in step S1709, if an RTS for NPCH communication is received using one or more channels other than the PCH, the control unit 202 advances the process to step S1710.

[0124] As mentioned above, the RTS used for NPCH communication differs from the traditional RTS. Even if the PCH is not detected when the receiver determines it is idle, the RTS will never be considered an error, thus ensuring stable communication. Furthermore, since the control frame duration is not increased, media utilization efficiency is improved.

[0125] <Example 2> Example 1 illustrates how the transmitting and receiving sides can use a 20 MHz channel adjacent to the main channel to transmit / receive RTS / CTS. Example 2 illustrates an example without using the 40 MHz bonding concept of IEEE 802.11n or the wider channel concept from IEEE 802.11ac onwards. In this case, the wireless communication device needs to use an arbitrary channel independent of the PCH for 20 MHz bandwidth communication. For this, the transmitting and receiving sides need to identify the channel to use for information other than the HT / VHT / HE / EHT operational element information. For this identification, using... Figure 18 The non-master operation element shown.

[0126] The non-master channel condition 1801 is an 8-bit field, and each bit in this field has the meaning described below.

[0127] Bit 0, set to 1, indicates permission for NPCH communication. Bit 1, set to 1, indicates that control frames for NPCH communication are shared as control frames for bandwidth signaling. Bit 2, set to 1, indicates that control frames for bandwidth signaling are not used to control NPCH communication. Bits from bit 3 onwards are unused (reserved).

[0128] The number of auxiliary master channels 1802 is an octet field that indicates the number of arbitrary channels.

[0129] The secondary master channel 1803 stores information about the non-master channels. The non-master operation elements include the number of secondary master channels 1803 specified by the number of secondary master channels 1802. Note that if the number of secondary master channels 1802 is 0 (zero), then there is no NPCH to be used for NPCH communication in the BSS (i.e., NPCH communication is not performed).

[0130] In addition, Figure 14 In the sequence shown, if the receiving STA 103 does not detect RTS 1406, the receiving STA 103 may not be set to a state of waiting for RTS on any channel. As described above, ease of use is improved because the channel used to activate NPCH communication can be controlled according to the characteristics of the receiving side.

[0131] <Variation Example> In the above embodiments, it has been illustrated that information identifying the RTS used for NPCH communication is stored in the RTS transmitted using the secondary channel for NPCH communication. However, the invention is not limited thereto. If the AP is about to initiate NPCH communication, information identifying the NPCH communication can be stored in the MU-RTS trigger frame. In this case, the information identifying the NPCH communication is also stored in the PHY header portion of the frame. Information identifying the NPCH communication can be stored in other frames. These other frames are, for example, frames that trigger communication between devices. More specifically, if the AP initiates NPCH communication, information identifying the NPCH communication can be stored in the BSRP (Buffered Status Report Polling) trigger frame. In this case, the information identifying the NPCH communication is also stored in the PHY header portion of the frame.

[0132] <Other Embodiments> This invention can be implemented by supplying a program for implementing one or more functions of the above embodiments to a system or device via a network or storage medium, and causing one or more processors in the computer of the system or device to read and execute the program. This invention can also be implemented by circuitry (e.g., an ASIC) for implementing one or more functions. Furthermore, the disclosure of the embodiments includes the following wireless communication devices and their control methods and procedures.

[0133] This invention is not limited to the embodiments described above, and various changes and modifications can be made within the spirit and scope of this invention. Therefore, the appended claims are made to inform the public of the scope of this invention.

[0134] This application claims the benefit of Japanese Patent Application 2024-006209, filed on January 18, 2024, the entire contents of which are incorporated herein by reference. Explanation of reference numerals in the attached figures 101: AP, 103: STA, 104: AP, 402: Header, 403: PSDU, 411: Service, 412: Frame Control, 413: Duration / ID, 414: Address 1, 415: Address 2, 501: HT Operation, 502: VHT Operation, 503: HE Operation, 504: EHT Operation, 505: Non-Master Operation, 1005, 1006: TXVECTOR, 1007: RXVECTOR, 1301: Value in bit 3 of CH_BANDWIDTH_IN_NON_HT

Claims

1. A wireless communication device conforming to the IEEE 802.11 standard series, characterized in that, include: The judgment component is used to determine whether the main channel of the basic service set (BSS) to which the wireless communication device belongs is in a busy state. A transmission component is configured to transmit an occupancy request frame for requesting to secure a transmission opportunity (TXOP) in at least one channel different from the main channel when the determination component determines that the main channel is in the busy state. as well as A communication control unit is configured to perform predetermined communication to transmit data without using the main channel, based on a response to the occupancy request frame. The occupancy request frame includes reservation information that identifies the request to secure a TXOP for the reserved communication.

2. The wireless communication device according to claim 1, characterized in that, The reservation information is stored in the service field included in the physical layer header, i.e., the PHY header, of the occupancy request frame.

3. The wireless communication device according to claim 1 or 2, characterized in that, It also includes a detection component, which is used to detect a response to the occupancy request frame transmitted by the transmission component. The communication control component requests in the occupancy request frame that the physical layer protocol data unit (PPDU) be transmitted in at least one of the channels of the TXOP that has received the response.

4. The wireless communication device according to claim 3, characterized in that, The transmission component transmits multiple occupancy request frames in multiple channels different from the main channel, and The communication control component controls the transmission so that the PPDU is not transmitted in the channel in which the detection component does not detect the response in the plurality of channels through which the transmission component transmits the plurality of occupancy request frames.

5. The wireless communication device according to claim 4, characterized in that, The physical layer header (PHY header) of the PPDU includes information that can identify channels that are not transmitting the PPDU.

6. The wireless communication device according to claim 4 or 5, characterized in that, Before transmitting the occupancy request frame on the plurality of channels, the transmission component performs backoff control on one of the plurality of channels, and transmits the occupancy request frame on a channel that is not the one of the plurality of channels, on a channel that is idle during the priority inter-frame interval (PIFS) before the backoff counter becomes zero.

7. The wireless communication device according to any one of claims 1 to 6, characterized in that, The wireless communication device is the access point for managing the BSS, and The wireless communication device further includes a second transmission component for transmitting parameters to be used in the predetermined communication, the parameters being included in an operating element.

8. The wireless communication device according to claim 7, characterized in that, The operational element includes information indicating whether to control bandwidth in the occupancy request frame.

9. The wireless communication device according to claim 7 or 8, characterized in that, The operational element includes information for indicating the channel capable of transmitting the occupancy request frame.

10. A wireless communication device conforming to the IEEE 802.11 standard series, characterized in that, include: The receiving component is configured to receive, in at least one channel that is different from the main channel of the basic service set (BSS) to which the wireless communication device belongs, an occupancy request frame for requesting to secure a transmission opportunity (TXOP) on that channel. The determining component is configured to determine, for the occupancy request frame received by the receiving component, whether the not less than one channel is in an idle state, when the occupancy request frame includes predetermined information that can identify a TXOP requesting to ensure predetermined communication for transmitting data without using the main channel. A transmission component is configured to transmit an occupancy response frame on one of the channels determined by the determination component to be in the idle state; as well as A communication control component is used to execute the predetermined communication based on the occupancy response frame.

11. The wireless communication device according to claim 10, characterized in that, The reservation information is stored in the service field included in the physical layer header, i.e., the PHY header, of the occupancy request frame.

12. The wireless communication device according to claim 10 or 11, characterized in that, The receiving component detects multiple occupancy request frames on multiple channels different from the main channel, and The transmission component controls the transmission so that the occupancy response frame is not transmitted on the channel determined by the determination component to be in a busy state among the plurality of channels where the receiving component receives the plurality of occupancy request frames.

13. The wireless communication device according to any one of claims 10 to 12, characterized in that, The wireless communication device is a non-access point terminal (NAPT) belonging to the BSS, i.e., a non-AP STA. The receiving component determines the channel used to detect the occupancy request frame based on the operation elements received from the access point.

14. The wireless communication device according to claim 13, characterized in that, The operational element includes information indicating whether to control bandwidth in the occupancy request frame.

15. The wireless communication device according to any one of claims 10 to 14, characterized in that, If the receiving unit does not receive the occupancy request frame on the main channel, and the occupancy request frame received on a channel other than the main channel does not include the predetermined information that can identify a request to ensure TXOP for the predetermined communication, the transmitting unit does not transmit the occupancy response frame for the occupancy request frame.

16. A control method executed by a wireless communication device conforming to the IEEE 802.11 standard series, characterized in that, include: Determine whether the main channel of the basic service set (BSS) to which the wireless communication device belongs is in a busy state; If it is determined that the main channel is in the busy state, a TXOP (Turn-Occupy Request) frame is transmitted in at least one channel different from the main channel to request that a transmission opportunity on that channel be secured. as well as Based on the response to the occupancy request frame, a predetermined communication is performed to transmit data without using the main channel. The occupancy request frame includes reservation information that identifies the request to secure a TXOP for the reserved communication.

17. A control method executed by a wireless communication device conforming to the IEEE 802.11 standard series, characterized in that, include: Receive an occupancy request frame for securing a transmission opportunity (TXOP) on at least one channel that is different from the main channel of the Basic Service Set (BSS) to which the wireless communication device belongs. If the occupancy request frame includes predetermined information that can identify a TXOP request to ensure predetermined communication for transmitting data without using the main channel, then for the received occupancy request frame, it is determined whether the not less than one channel is in an idle state. An occupancy response frame is transmitted on one of the channels that is determined to be in the idle state. as well as Based on the occupancy response frame, the predetermined communication for transmitting data without using the main channel is performed.

18. A program configured to cause a computer to be used as a wireless communication device as defined in any one of claims 1 to 15.

Images