Communication apparatus and communication method

Abstract

A non-access point station includes: a control unit that generates a signal indicating that an obtained resource has been allocated, said signal specifying an allocation period; and a wireless transmission / reception unit that transmits the generated signal.

Description

Technical Field

[0001] The present disclosure relates to a communication device and a communication method. Background Art

[0002] The technical specifications of IEEE 802.11be (hereinafter referred to as "11be") are being planned as the successor standard of IEEE 802.11ax (hereinafter referred to as "11ax"), the standard of the Institute of Electrical and Electronics Engineers (IEEE: The Institute of Electrical and Electronics Engineers) 802.11. 11ax is also called "High Efficiency (HE)" and 11be is also called "Extreme High Throughput (EHT)". In addition, the requirement specifications related to the successor standard of 11be are also being studied. Hereinafter, the successor standard of 11be will be referred to as "Enhanced 11be (Beyond 11be)".

[0003] Prior art literature

[0004] Non-patent literature

[0005] Non-patent document 1: IEEE 802.11-22 / 0729r1

[0006] Non-patent document 2: IEEE 802.11-22 / 0734r0

[0007] Non-patent document 3: IEEE 802.11-20 / 0005r1

[0008] Non-patent document 4: IEEE 802.11-21 / 0894r6

[0009] Non-patent document 5: IEEE 802.11-21 / 2032r2

[0010] Non-patent document 6: IEEE P802.11-REVme TM / D1.3, June 2022

[0011] Non-patent document 7: IEEE P802.11be TM / D2.0, May 2022 Summary of the invention

[0012] However, a detailed resource allocation method including TXOP (Transmission Opportunity) sharing from a non-access point (Non-AP) to an AP has not yet been studied.

[0013] The non-limiting embodiments of the present disclosure help provide a communication device and a communication method that can improve transmission efficiency in wireless communications.

[0014] A non-AP STA (Non-Access Point Station) according to an embodiment of the present disclosure includes: a control unit that generates a signal indicating the following allocation, wherein the allocation is an allocation of acquired resources that is specified during the allocation period; and a wireless transceiver unit that transmits the generated signal.

[0015] It should be noted that these general or specific aspects may be implemented by a system, an apparatus, a method, an integrated circuit, a computer program or a recording medium, or may be implemented by any combination of systems, apparatuses, methods, integrated circuits, computer programs and recording media.

[0016] According to an embodiment of the present disclosure, for example, transmission efficiency in wireless communication can be improved.

[0017] More advantages and effects of an embodiment of the present disclosure will be explained through the description and drawings. These advantages and / or effects are provided by several embodiments, and the features described in the description and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1A This is a diagram showing a structural example of a MAC (Medium Access Control) frame.

[0019] Figure 1B This is a diagram showing an example of the structure of an HT (High Throughput) control field.

[0020] Figure 1C This is a diagram showing an example of the structure of the A-Control subfield.

[0021] Figure 1D This is a diagram showing an example of the structure of a control list (Control List).

[0022] Figure 1EThis is a diagram showing an example structure of a control information subfield.

[0023] Figure 2 This is a diagram showing a structural example of a CAS (Command and status) control subfield.

[0024] Figure 3 This is a diagram showing an example of a trigger frame.

[0025] Figure 4 This is a diagram showing a structural example of a common information field (Common Info field).

[0026] Figure 5 This is a diagram showing a structural example of the user information field (User Info field) in the MU-RTS TXS trigger frame.

[0027] Figure 6 This is a diagram showing a structural example of a special user information field (Special User Info field).

[0028] Figure 7 It is a block diagram showing a configuration example of a non-AP100.

[0029] Figure 8 It is a block diagram showing a configuration example of the AP 200 .

[0030] Fig. 9 This is a diagram showing an example of an allocation period indicating a TXOP.

[0031] Fig.10 This is a diagram showing an example of a sequence of notifying RDG and allocation period.

[0032] Fig.11 This is a diagram showing an example of a trigger frame format (Trigger frame format) for non-AP transmission.

[0033] Fig.12 This is a diagram showing an example of a general information field for non-AP transmission.

[0034] Fig.13 This is a diagram showing an example of a user information field for MU-RTS TXS for non-AP transmission.

[0035] Fig.14 This diagram shows an operation in which the non-AP 100 obtains the transmission right of the TXOP shared control information and allocates it to the AP 200 .

[0036] Fig.15This diagram shows an operation in which the non-AP 100 obtains the transmission right of data and TXOP shared control information and allocates it to the AP 200 .

[0037] Fig.16 This is a diagram showing a structural example of the RD protocol.

[0038] Fig.17 This is a sequence diagram for allowing communication with a non-AP different from the non-AP 100 .

[0039] Fig.18 This is a sequence diagram in which the AP 200 as the RD responder instructs a non-AP different from the non-AP 100 to transmit an uplink using a trigger frame.

[0040] Fig.19 This is a diagram showing a structural example of a MU-RTS TXS trigger frame.

[0041] Fig. 20 This is a sequence diagram in which the non-AP 100 transmits a MU-RTS TXS trigger frame including the transmission destination of the AP 200 in the allocated period, and instructs the AP 200 to share the TXOP.

[0042] Fig.21 This is a diagram showing a structural example of the RD protocol.

[0043] Fig. 22 This is a diagram showing a structural example of a MU-RTS TXS trigger frame.

[0044] Fig.23 This is a sequence diagram in which the non-AP 100 sends a MU-RTS TXS trigger frame including a traffic class that can be communicated during the allocation period, and indicates TXOP sharing to the AP 200.

[0045] Fig.24 This is a sequence diagram of a non-AP 100 that has shared a TXOP and reacquires the TXOP when the number of low-latency services reserved by the AP is small.

[0046] Fig.25 This is a sequence diagram of a case where the priority of data retained by the AP200 is lower than the priority of data retained by non-AP100.

[0047] Fig.26 This is a sequence diagram for a case where the priority of data retained by the AP 200 is higher than the priority of data retained by non-AP 100 .

[0048] Fig. 27 This is a diagram showing a new structural example of the HT Control field.

[0049] Fig.28 This is a diagram showing a new structural example of the HT Control field. DETAILED DESCRIPTION

[0050] Hereinafter, each embodiment of the present disclosure will be described in detail with reference to the drawings.

[0051] 11be and enhanced 11be assume use cases such as gaming or virtual reality (VR), and propose the need to further reduce latency (see, for example, non-patent documents 1 to 2).

[0052] In 11be, a priority control method called "Enhanced Distributed Channel Access (EDCA)" can be used in the same way as 11ax to give priority to the transmission opportunities dedicated to each access category (AC). In EDCA, for example, an AC that has obtained the right to transmit can continuously transmit wireless signals at intervals of the minimum waiting time (SIFS: Short Inter Frame Space). The time during which this continuous transmission can be performed can be called a "transmission opportunity (TXOP)". For example, the upper limit time of the TXOP can be specified individually for each AC.

[0053] With low latency as one of the goals, research is being conducted on allocating TXOPs (TXOP sharing) acquired by non-AP STAs (also called "Non-Access Point Stations" or "terminals." Hereinafter, referred to as "non-APs") to AP STAs (also called "Access Point Stations" or "base stations." Hereinafter, referred to as "APs") (for example, refer to non-patent documents 3 to 5).

[0054] In IEEE 802.11n (hereinafter referred to as "11n"), a TXOP sharing from an RD initiator to an RD responder using an RD (Reverse direction) protocol is introduced (for example, refer to Non-Patent Document 6).

[0055] use Figure 1A The high throughput (HT) control field contained in the MAC header of the media access control (MAC) frame shown controls the RD protocol.

[0056] like Figure 1B As shown, in 11ax and 11be, control is performed using the A control subfield included in the HT control field.

[0057] In detail, Figure 1C As shown, the A control subfield contains a control list.

[0058] like Figure 1D As shown, the control list includes a control ID subfield and a control information subfield.

[0059] like Figure 1E As shown, the format of the control information subfield (transmission information, size, number of subfields included in the A control subfield) changes according to the value of the control ID subfield.

[0060] When the value of the Control ID subfield indicates Command and Status (CAS) (Control ID value = 6), the Control Information subfield becomes Figure 2 The CAS Control subfield is defined in the format shown. Figure 2 The RD protocol is controlled by the value of the RDG / More PPDU subfield in the CAS Control subfield. Although both the RD initiator and the RD responder use the RDG / More PPDU subfield, the RD initiator controls the RD Grant (RDG) and the RD responder controls the value of this subfield based on the intent of the More PPDU.

[0061] The RD initiator that has obtained the TXOP allows the RD responder, which is the destination, to transmit during the remaining TXOP period of the RD initiator by sending a physical layer protocol data unit (PPDU) with the value of the RDG subfield set to 1 (RDG subfield=1). The RD responder transmits a PPDU (also called a "Response Burst") containing data sent to the RD initiator during the allocated TXOP period (the remaining TXOP period). When the RD responder continues to send PPDUs during the allocated period, it sends a PPDU with the value of the More PPDU subfield set to 1 (More PPDU subfield=1). When there is no data to be sent during the allocated TXOP period and the RD responder sends the last PPDU, it sends a PPDU with the value of the More PPDU subfield set to 0 (More PPDU subfield=0). In this way, the RD responder can return the TXOP to the RD initiator.

[0062] In the TXOP sharing using the multi-user request-to-send (MU-RTS) TXOP sharing (TXS) trigger frame introduced in 11be, a part of the TXOP obtained by the AP can be shared with non-APs (for example, refer to non-patent document 7).

[0063] In 11be, for example, a study was conducted on the use of a trigger frame in which the AP sets MU-RTS as the type of the trigger frame (e.g., called "Trigger Type") to instruct TXOP sharing to one STA (e.g., refer to non-patent document 7). Hereinafter, the trigger frame instructing TXOP sharing is referred to as a "MU-RTS TXS trigger frame".

[0064] Figure 3 is a diagram showing an example of a trigger frame. Figure 3 As shown, the trigger frame includes a field containing information common to the plurality of non-APs (e.g., Common Info field) and a field called "User Info List" for a plurality of non-APs subjected to frequency multiplexing (FDM: Frequency Division Multiplexing). The User Information List may include, for example, one or more fields containing information specific to (or inherent to) the non-APs (e.g., User Info field).

[0065] In addition, in 11be, for example, the trigger frame may include a field (for example, a “special user information field”) including information for a terminal corresponding to 11be (EHT) (not shown).

[0066] Figure 4 This is a diagram showing a structural example of a general information field studied in 11be (for example, refer to non-patent document 7).

[0067] Figure 5 This is a diagram showing a structural example of the user information field in the MU-RTS TXS trigger frame studied in 11be (for example, refer to non-patent document 7).

[0068] Figure 6 This is a diagram showing a structural example of a special user information field (for example, refer to non-patent document 7).

[0069] For example, Figure 4The Trigger Type subfield in the General Information field shown is a subfield that indicates the category of the trigger frame (e.g., the category of the signal sent by the AP to the non-AP). For example, the AP can indicate the MU-RTS TXS trigger frame to the specified non-AP by setting the value of the trigger type to a value indicating MU-RTS (e.g., in the case of 11be, the Trigger Type subfield value = 3) and setting the value of the Triggered TXOP Sharing Mode subfield in the General Information field to a specified value.

[0070] For example, when a non-AP receives a MU-RTS TXS trigger frame and specifies the association identifier (AID: Association Identifier) ​​of the non-AP in the user information field contained in the received MU-RTS TXS trigger frame, the non-AP sends a Clear To Send (CTS: Clear To Send) frame to the AP, thereby notifying the start of TXOP sharing and sending PPDU during the subsequent allocation period. Since only the trigger frame can be sent by the AP, TXOP sharing cannot be performed by non-APs.

[0071] Regarding the allocation of TXOPs acquired by non-APs to APs, detailed studies are insufficient.

[0072] (Implementation Method 1)

[0073] In the first embodiment, the non-AP allocates a part of the period of the acquired resources (TXOP) to the AP.

[0074] A method of efficiently performing communication from a non-AP to an AP during an allocation period and a method of performing communication according to the priority of traffic will be described.

[0075] The wireless communication system of the first embodiment includes, for example, Figure 7 Non-AP100 and Figure 8 AP200 shown.

[0076] [Structural example other than AP100]

[0077] Figure 7 It is a block diagram showing a configuration example of a non-AP100.

[0078] Figure 7The non-AP 100 shown may, for example, include a scheduling unit 101, a TXS control information generating unit 102, a data generating unit 103, a MAC information generating unit 104, an error correction coding unit 105, a modulation unit 106, a wireless transceiver unit 107, a demodulation unit 108, an error correction decoding unit 109 and a resource request information retention unit 110.

[0079] For example, the scheduling unit 101, the TXS control information generation unit 102, the data generation unit 103, the MAC information generation unit 104, and the resource request information retention unit 110 may be included in an access control (eg, MAC) unit.

[0080] For example, at least one of the scheduling unit 101, the TXS control information generating unit 102, the data generating unit 103, the MAC information generating unit 104, the error correction coding unit 105, the modulation unit 106, the demodulation unit 108, the error correction decoding unit 109 and the resource request information retaining unit 110 may also be a control unit.

[0081] Non-AP100 may also send a PPDU including a control signal indicating TXOP sharing (for example, MAC information defined in a format based on an RDG or MU-RTS TXS trigger frame) to AP200. AP200 may also receive a control signal indicating TXOP sharing, and based on the allocation period, send a signal to a non-AP that has shared, or other non-APs, or other APs that perform coordinated transmission. AP200 may also be set as an AP to which non-AP100 is connected (also referred to as an "Associated AP"). In addition, AP200 may also be set as one of the multiple APs that perform coordinated transmission with non-AP100.

[0082] The scheduling unit 101 performs scheduling for AP200. For example, the scheduling unit 101 may determine the control information (allocation period, communication destination during the allocation period, service category (TID: Traffic Identifier) ​​etc.) applied to TXOP sharing of AP200 based on the buffer information retained by AP200 input from the resource request information retaining unit 110.

[0083] The allocation period for the AP 200 may be a period of a part of the TXOP that the non-AP 100 has already obtained.

[0084] In addition, the communication destination in the allocation period may include not only control limited to communication with non-AP 100, but also control excluding non-AP 100. For example, communication may be performed with a non-AP different from non-AP 100 or an AP different from AP 200 (for example, one of the APs performing coordinated transmission).

[0085] In addition, high-priority services (eg, low-latency services) may be indicated as service categories (TIDs) that can be communicated during the allocation period. Thus, only high-priority services can be transmitted during the allocation period for the AP.

[0086] The scheduling unit 101 outputs the determined TXOP sharing control information for the AP 200 to the TXS control information generation unit 102 , for example.

[0087] The TXS control information generation unit 102 may also generate TXS control information using a prescribed MAC frame format. As TXS control information, for example, MAC data (also referred to as "MAC Protocol Data Unit (MPDU)") including TXS control information may be generated in a format based on an RDG or MU-RTS TXS trigger frame. Details will be described below.

[0088] The TXS control information generation unit 102 may output MAC data including the TXS control information to the MAC information generation unit 104 .

[0089] The data generation unit 103 may generate MAC data (for example, data in MPDU format) to be transmitted to the AP 200, and output the generated data to the MAC information generation unit 104. In addition, when the data to be transmitted to the AP 200 is not to be retained, it may not be output to the MAC information generation unit 104.

[0090] The MAC information generation unit 104 combines the MAC data including the TXS control information from the TXS control information generation unit 102 and the MAC data including the data signal from the data generation unit 103, and outputs the combined MAC data to the error correction coding unit 105. In addition, the MAC data obtained by combining multiple types of MAC data is sometimes referred to as "Aggregated MPDU (A-MPDU)".

[0091] For example, the error correction coding unit 105 may perform error correction coding on the MAC data input from the MAC information generation unit 104 , and output the coded signal to the modulation unit 106 .

[0092] For example, the modulation unit 106 may perform modulation processing on the signal input from the error correction coding unit 105 , and output the modulated signal to the wireless transmission / reception unit 107 .

[0093] In addition, when the modulated data signal is an orthogonal frequency division multiplexing (OFDM) signal, non-AP100 can also map the modulated signal to a specified frequency resource and perform inverse fast Fourier transform (IFFT) processing to convert it into a time waveform, and add a cyclic prefix (CP) to form an OFDM signal.

[0094] The wireless transceiver 107 may perform wireless transmission processing such as D / A (Digital / Analog) conversion and up-conversion of the modulated signal input from the modulation unit 106, and transmit the signal after the wireless transmission processing to the AP 200 via the antenna. In addition, the wireless transceiver 107 may receive a signal transmitted from the AP 200 via the antenna, perform wireless reception processing such as down-conversion to baseband frequency and A / D (Analog / Digital) conversion on the received signal, and output the signal after the wireless reception processing to the demodulation unit 108.

[0095] The demodulation unit 108 may also perform demodulation processing on the signal input from the wireless transceiver unit 107, and output the demodulated signal to the error correction decoding unit 109. In addition, when the signal input to the demodulation unit 108 is an OFDM signal, the non-AP 100 may perform CP removal processing and Fast Fourier Transform (FFT) processing.

[0096] The error correction decoding unit 109 decodes the signal input from the demodulation unit 108, for example, to obtain a received data signal from the AP 200. For example, when the decoded received data includes resource request information of the AP, the error correction decoding unit 109 may output the decoded data including the resource request information of the AP to the resource request information storage unit 110.

[0097] The resource request information retaining unit 110 may also obtain (or retain) the resource request information of the AP from the decoded data input from the self-error correction decoding unit 109, and output the obtained resource request information to the scheduling unit 101. The resource request information of the AP may also be, for example, at least one of whether the AP 200 requests the non-AP 100 to allocate resources, the request time of the resource allocation converted into a specified bandwidth (for example, 20 MHz), and information related to the buffer status retained by the AP 200 (for example, at least one of the destination of the reserved buffer, the AC or TID of the reserved buffer, the queue size of each AC and TID, the delay budget (the allowable range of delay), etc.). In addition, the buffer status information retained by the AP 200 and sent to the non-AP other than the non-AP 100 may also be included as the resource request information.

[0098] [Structural example of AP200]

[0099] For example, AP200 receives a PPDU including a control signal indicating TXOP sharing from non-AP100. Then, based on the control signal indicating TXOP sharing, AP200 communicates with the permitted transmission destination within the allocated period for the permitted service category. In addition, AP200 notifies non-AP100 of resource request information of AP200 at a predetermined timing.

[0100] Figure 8 It is a block diagram showing a configuration example of the AP 200 .

[0101] Figure 8 The AP 200 shown may include, for example, a wireless transceiver unit 201 , a demodulator unit 202 , an error correction decoder unit 203 , a TXS control information acquisition unit 204 , a scheduler unit 205 , a data generator unit 206 , an error correction encoder unit 207 and a modulator unit 208 .

[0102] For example, the TXS control information acquisition unit 204, the scheduling unit 205, and the data generation unit 206 may be included in an access control (eg, MAC) unit.

[0103] The wireless transceiver 201 may receive a received signal using an antenna, perform wireless reception processing such as down-conversion and A / D conversion on the received signal, and output the signal after the wireless reception processing to the demodulator 202. In addition, the wireless transceiver 201 may perform wireless transmission processing such as up-conversion and D / A conversion on the signal input from the modulator, and transmit the signal after the wireless transmission processing from the antenna.

[0104] The demodulation unit 202 may demodulate the received data input from the wireless transceiver unit, and output the demodulated signal to the error correction decoding unit 203. When the signal input to the demodulation unit 202 is an OFDM signal, the AP 200 may perform CP removal and FFT processing, for example.

[0105] The error correction decoding unit 203 may decode the demodulated signal input from the demodulation unit 202 and output the decoded signal as a received data signal. In addition, the error correction decoding unit 203 may output MAC data including TXS control information in the received data signal to the TXS control information acquisition unit 204, for example.

[0106] The TXS control information acquisition unit 204 may also extract the TXS control information from the MAC data input from the self-error correction decoding unit 203, and acquire the control information related to TXOP sharing (at least one of the allocation period, the communication destination in the allocation period, and the service type (TID) that can communicate during the allocation period). The TXS control information acquisition unit 204 may also output the extracted control information related to TXOP sharing to the scheduling unit 205.

[0107] The scheduling unit 205 may determine at least one of the signal length, the transmission destination, and the transmission service type of the data that can be transmitted during the allocation period based on the control information related to TXOP sharing input from the TXS control information acquisition unit 204. In addition, the wireless parameters (at least one of the signal length, modulation method, error correction coding rate, spatial multiplexing number, transmission power, etc.) applied to the transmission data may be determined and output to the data generation unit 206, the error correction coding unit 207, and the modulation unit 208.

[0108] The data generation unit 206 may generate a data signal based on the radio parameters input from the scheduling unit, and output the data signal to the error correction coding unit 207 .

[0109] The error correction coding unit 207 may perform error correction coding on the data signal input from the data generation unit 206 , and output the coded signal to the modulation unit 208 .

[0110] The modulation unit 208 may also modulate the signal input from the error correction coding unit 207 and output the modulated signal to the wireless transceiver unit 201. In addition, when the modulated signal is an OFDM signal, the AP 200 may map the modulated signal to frequency resources, perform IFFT processing, and add a CP to form an OFDM signal.

[0111] [Action example]

[0112] An operation example of the non-AP 100 and the AP 200 according to the first embodiment will be described.

[0113] Two examples, action example 1 and action example 2, are described. Action example 1 is an action example in which a non-AP uses the HT control field to send TXS information including an allocation period to AP200 in addition to sending RDG. Action example 2 is an action example in which the TXS information including the allocation period is included in the MU-RTS TXS trigger frame for notification.

[0114] The non-AP controls the allocation period, thereby improving the transmission efficiency.

[0115] [Action Example 1]

[0116] Hereinafter, an example will be described in which the non-AP 100 transmits TXOP sharing control information generated by the non-AP 100 (for example, the TXS control information generating unit 102 ) to the AP 200 and allocates a portion of the acquired TXOP period to the AP 200 .

[0117] The TXS control information generated by the TXS control information generation unit 102 may include an allocation period from the non-AP 100 to the AP 200. The allocation period may be a period of a portion of the TXOP obtained by the non-AP 100. For example, the TXS control information including the allocation period may be notified along with the control information (RDG) of the RD protocol.

[0118] Specifically, if Fig. 9 As shown, you can also Figure 2 The reserved bit of the control information subfield is set to the allocation duration subfield (Allocation Duration subfield), indicating the allocation period of the TXOP allocated to AP200. For example, an allocation period of a specified granularity (for example, 16 [us (microsecond)] units) may be notified. Alternatively, the allocation period may be defined with different granularities (for example, units greater than 16 [us] or units less than 16 [us]). The granularity may also be determined in consideration of the signaling amount. Alternatively, the ratio (for example, X% unit) to the remaining period (the time notified by the duration field (Duration field) of the MAC header) in the TXOP already obtained by non-AP100 may be notified. In addition, the notified allocation period may also include an indication of all remaining periods in the TXOP already obtained by non-AP100.

[0119] Furthermore, when control is performed to always limit the allocation period to the entire remaining period of the TXOP, the remaining period of the TXOP is notified by the duration field of the MAC header, and therefore, notification of the allocation duration subfield of the control information subfield is not necessary.

[0120] Fig.10Indicates that the RD initiator is not AP100 ( Fig.10 During the RDG and allocation period, the non-AP STA1) notifies the AP200 ( Fig.10 An example of a sequence of TXOP sharing is indicated by an AP).

[0121] Fig.10 This indicates an operation in which non-AP 100 obtains the right to transmit data and TXOP sharing control information ("Data+HTC" in the figure), sets a TXOP, and allocates a part of or all of the remaining TXOP to AP 200 (performing TXOP sharing).

[0122] Fig.10 In the following example, non-AP100 uses the uplink data sent to AP200 in addition to sending the uplink data. Fig. 9 The format shown is set to RDG = 1, and the AD contains the allocation period ( Fig.10 The AP 200 is notified of an example of TXOP sharing by sending TXS control information (S1001) of "Allocation Duration in RDG" of the AP 200. The allocation period is set based on the resource request information of the AP 200 obtained from the AP 200 in advance.

[0123] The non-AP 100 considers the buffer status (size, etc.) of the high-priority traffic addressed to itself, calculates the period required to transmit the traffic, and sets the allocation period. The AP 200 communicates during the allocation period indicated by the non-AP 100.

[0124] When the last PPDU in the allocation period is sent, the value of the More PPDU subfield is set to 0 (More PPDU=0) (S1002). Non-AP 100 sends a block acknowledgment (BA: Block Ack) to AP 200 as an acknowledgment (ACK: acknowledgement) (S1003). After the allocation period for AP 200 ends, the non-AP 100 that has obtained the TXOP reacquires the remaining TXOP. Fig.10 This shows an example in which the non-AP 100 transmits data to another non-AP STA 2 during the remaining period of the reacquired TXOP ( S1004 ), and the non-AP STA 2 transmits a BA to the non-AP 100 ( S1005 ).

[0125] [Action Example 2]

[0126] For example, the TXS control information including the allocation period may be included in the MU-RTS TXS trigger frame for non-AP transmission and notified. Figure 5The allocation duration subfield of the user information field shown indicates the allocation period of the TXOP allocated to AP200. For example, an allocation period of a specified granularity (e.g., 16 [us] units) may be notified. Alternatively, the allocation period may be defined at different granularities (e.g., units greater than 16 [us] or units less than 16 [us]). The granularity may also be determined in consideration of the signaling amount. In addition, the notified allocation period may also include an indication that the remaining entire period in the TXOP obtained by non-AP100 is allocated and is not limited to a portion of the TXOP obtained by non-AP100.

[0127] The format of the trigger frame sent by the non-AP may be different from the format of the trigger frame sent by the AP. Fig.11 This shows an example of the trigger frame format for non-AP transmission.

[0128] In the trigger frame format for AP transmission, the connection destination is defined in a user information list consisting of a plurality of user information fields. In the trigger frame format for non-AP transmission, the connection destination in the user information field can also be limited to the AP to which the non-AP is connected. Fig.11 As shown, the user information list may also be composed of a user information field.

[0129] In addition, in the case of sending a trigger frame for non-AP transmission to multiple APs, for example, when a non-AP requests multiple APs for coordinated transmission to notify resource allocation request information or uplink quality information, the user information list of the trigger frame for non-AP transmission may also include multiple user information fields.

[0130] In addition, in the trigger frame format for AP transmission, the frame defined in the frame control field (Frame Controlfiled) of the MAC header is a trigger subtype (Trigger Subtype) (the value of the subtype subfield (Subtype subfield) is 0010) of the control type (Control Type) (the value of the type subfield (Type subfield) is 01). The trigger frame format for non-AP transmission (sent to AP) of implementation mode 1 can also use the same type and subtype as that for AP transmission. Alternatively, a new type and / or subtype different from that for AP transmission can be defined for non-AP transmission.

[0131] For example, the reserved bits (0000-0001) of the subtype may also be used to newly define the purpose of triggering AP, namely, "AP Trigger Subtype" as the control type (the value of the type subfield is 01).

[0132] In this way, the type and / or subtype is changed according to AP transmission (sending to non-AP) and non-AP transmission (sending to AP), thereby reducing the reception processing amount of non-AP. For example, a non-AP that receives a trigger frame for non-AP transmission (sending to AP) can recognize that it is a trigger frame sent to AP based on the MAC header, and thus can stop subsequent reception processing.

[0133] In the trigger frame format for non-AP transmission (sent to AP), when it is sent to a connected AP, the RA (Receiver Address or Receiving station Address) field can also be set to the MAC address of AP200 to which non-AP100 is connected. When a trigger frame for non-AP transmission is sent to multiple APs, for example, when a non-AP requests multiple APs for coordinated transmission to notify resource allocation request information, a broadcast address can also be set in the RA field.

[0134] [Notification format]

[0135] Fig.12 This shows an example of a general information field used for non-AP transmission.

[0136] The general information field for non-AP transmission can also be used relative to the general information field for AP transmission (refer to Figure 4 ), change the information or subfield name contained, that is, change UL information to DL information, and change STA information to AP information. For example, Figure 4 The UL length subfield (UL Length subfield) can also be changed to a DL length subfield, which contains the value of the content of the L-SIG length field of the preamble (Preamble) of the downlink signal (PPDU) responded by the AP. In addition, Figure 4 The UL BW subfield may also be changed to a DL BW subfield, which includes the value of the content of the EHT-SIG-A field of the preamble of the downlink signal (PPDU) to which the AP responds. It should be noted that the size of the DL BW subfield may also be defined as a size that can notify the size of the supported bandwidth. In addition, Figure 4 The AP TX Power subfield (AP TX Power subfield) may also be changed to a non-AP STA TX Power subfield including the transmit power of non-AP 100 .

[0137] In addition, with respect to the general information field sent by the AP (refer to Figure 4 ), the general information field for non-AP transmission may also delete some subfields. For example, Figure 4The triggered TXOP sharing mode subfield may also be deleted from the general information field when it is included in the user information field. In addition, the reserved bit may also be deleted.

[0138] In addition, although the special user information field sent by the AP (refer to Figure 6 ), but in the trigger frame for non-AP transmission, the general information for the terminal can also be included in the general information field. In this case, the special user information field flag (SpecialUser Info Field Flag) can also be deleted in the general information field for non-AP transmission.

[0139] Fig.13 This shows an example of the user information field for MU-RTS TXS for non-AP transmission.

[0140] For the user information field sent by the AP (refer to Figure 5 ), or delete redundant information (subfields) in the user information field for non-AP transmission. For example, as described above, when the RA field contains the MAC address of the connected AP, the AID12 subfield indicating the identification ID of the connected AP may be deleted. In addition, the reserved bit may be deleted.

[0141] It should be noted that, when the RA field contains a broadcast address, Fig.13 A subfield is added to the format of the following ID, which identifies the AP from multiple APs.

[0142] In order to coexist with legacy STAs that only support the old standard, the MU-RTS TXS trigger frame and the CTS frame responding to the MU-RTS TXS trigger frame may be included in a non-HT PPDU or a non-HTduplicate PPDU and transmitted.

[0143] [Sequence example]

[0144] use Fig.14 , Fig.15 , indicating two sequence examples in which non-AP100 (non-AP STA1 in the figure) notifies the MU-RTS TXS trigger frame including the allocation period and indicates TXOP sharing to AP200 (AP in the figure).

[0145] [Sequence example 1]

[0146] Fig.14The following sequence example is shown, that is, non-AP 100 obtains the transmission right of TXOP sharing control information ("MU-RTS TXSTF" in the figure) and sets a TXOP, and non-AP 100 allocates part of the TXOP or all of the remaining TXOP to AP 200 (performs TXOP sharing).

[0147] exist Fig.14 In the example, non-AP 100 sends a MU-RTS TXS trigger frame (S1401) containing an allocation period ("Allocation Duration in MU-RTS TXS TF" in the figure) in AD to indicate TXOP sharing to AP 200. Fig.10 Similarly to the example of , the non-AP 100 sets the allocation period based on the resource request information of the AP 200 acquired in advance from the AP 200 .

[0148] AP200 communicates during the allocated period indicated by non-AP100. AP200 first sends a CTS frame to non-AP100 to notify the start of communication during the allocated period (S1402), and then sends data (S1403). Non-AP100 sends a BA to AP200 (S1404). After the allocated period for AP200 ends, the non-AP100 that has obtained the TXOP regains the remaining TXOP. Fig.14 , there is shown an example in which the non-AP 100 transmits data to other non-AP STA 2 during the remaining period of the reacquired TXOP ( S1405 ), and the non-AP STA 2 transmits a BA to the non-AP 100 ( S1406 ).

[0149] [Sequence example 2]

[0150] Fig.15 The following sequence example is shown, that is, non-AP 100 obtains the transmission right of data and TXOP sharing control information ("data + MU-RTS TXS TF" in the figure) and sets a TXOP, and non-AP 100 allocates part of the TXOP or the remaining entirety to AP 200 (TXOP sharing).

[0151] exist Fig.15 In addition to sending a MU-RTS TXS trigger frame containing an allocation period ("allocation duration in MU-RTS TXS TF" in the figure) in AD, non-AP100 also multiplexes uplink data (A-MPDU) sent to AP200 (S1501) to indicate TXOP sharing to AP200. Fig.15In the case of AP200, after sending the CTS frame (S1502), AP200 responds to the non-AP100 with data and BA for uplink data (S1503). Fig.14 same.

[0152] As described in the above specific example, non-AP 100 appropriately controls the allocation period based on resource request information of itself and AP 200, thereby improving transmission efficiency.

[0153] [Destination in TXOP sharing]

[0154] Hereinafter, a method will be described in which the non-AP 100 transmits TXOP shared control information generated by the non-AP 100 (for example, a TXS control information generating unit) to the AP 200 to control the transmission destination of the AP 200 in the allocated period.

[0155] The TXS control information generated by the TXS control information generating unit may also include information related to the transmission destination of AP200 during the allocation period. For example, non-AP100 may also allow transmission that does not include non-AP100 itself during the allocation period for AP200. In addition, when AP200 communicates with a non-AP different from non-AP100, non-AP100 may also allow only high-priority services (for example, low-latency services). In addition, it is also possible to allow communication that does not include the RD initiator only when the AP is the RD responder.

[0156] For example, the transmission destination information of AP200 during the allocation period may also be notified along with the control information (RDG) of the RD protocol. Fig.16 As shown, you can also Figure 5 A portion of the reserved bits of the control information subfield is set to information related to the transmission destination of AP200 during the allocation period ( Fig.16 The destination mode subfield (Destination mode subfield) notifies AP200 of the sending destination.

[0157] The transmission destination of the AP 200 during the allocation period can be, for example, any of the following information.

[0158] 00: Only non-APs that have been shared (non-AP100)

[0159] 01: Non-AP (non-AP100) or other non-APs that have been shared

[0160] 10: Non-APs that are already shared (non-AP100), or APs that are different from the shared AP (AP200) and are performing coordinated transmission

[0161] 11: Non-APs that have been shared (non-AP100), or other non-APs, or APs that are coordinated and sent differently from the shared AP (AP200)

[0162] For example, when non-AP100 knows from AP200's resource request information that AP200 has reserved high-priority services (e.g., low-latency services) for non-APs other than non-AP100, non-AP100 may also allow AP200 to communicate with other non-APs during the allocation period.

[0163] Furthermore, when the non-AP 100 determines that a performance improvement effect can be expected by applying coordinated transmission by a plurality of APs, the non-AP 100 may allow an AP that performs coordinated transmission different from the AP 200 to communicate during the allocated period.

[0164] Fig.17 , Fig.18 The following sequence example is shown, i.e., non-AP100 (non-AP STA1 in the figure) as the RD initiator notifies AP200 (AP in the figure) of the sending destination in the RDG and the allocation period ("allocation duration in RDG (Remaining TXOP)") in the figure), and instructs AP200 as the RD responder to share the TXOP.

[0165] exist Fig.17 , Fig.18 The following action is shown in which non-AP100 obtains the right to transmit data and control information including an indication of TXOP sharing (RDG=1) and information related to the transmission destination (DM), and sets TXOP ("data+HTC" in the figure). Then, non-AP100 allocates part of the TXOP or all of the remaining TXOP to AP200 (TXOP sharing).

[0166] exist Fig.17 In the example shown below, in addition to sending uplink data to AP200, non-AP100 also uses Fig.16 The format shown is an example of instructing AP200 to share TXOP (S1701) by setting the value of the RDG subfield to 1 (RDG=1) and including the transmission destination (DM) of AP200 during the allocation period. Non-AP100 sets the transmission destination of AP200 during the allocation period based on the resource request information obtained in advance from the AP.

[0167] Fig.17This indicates that non-AP100 allows AP200 to communicate with a non-AP different from non-AP100. That is, non-AP100 allows the transmission of the RD initiator that does not include the response burst using the RD protocol. After AP200 sends a BA to non-AP100 (S1702), it communicates with the allowed object within the allocation period (S1703) and receives the BA (S1704). Fig.17 In the example, AP200 sends a low-latency service to non-AP STA2.

[0168] Fig.18 also with Fig.17 Likewise, communication with a non-AP different from the non-AP 100 is permitted. Fig.18 In the example, AP200 as the RD responder uses a trigger frame (e.g., a basic trigger frame) to instruct a non-AP (non-AP STA2) different from non-AP100 to send uplink data (S1803), and non-AP STA2 sends uplink data (S1804). In addition, similarly to the above specific example, the uplink transmission can also be limited to low-latency services.

[0169] Here, in the 11n RD protocol, when the RD responder is an AP, the AP can only send a basic trigger frame with a trigger type of basic. However, for this embodiment, when communication with other non-APs is allowed during the allocation period, the AP as the RD responder can also be allowed to send a MU-RTS TXS trigger frame. For example, the AP can use the MU-RTS TXS trigger frame to share the resource TXOP during the allocation period with a non-AP (a non-AP different from non-AP100) that reserves a large-size low-latency service.

[0170] In addition, the specification may be that when a non-AP is an RD responder, the PPDU transmission (response burst) during the allocation period must include the specification that it is sent to the RD initiator. The specification may also be that when an AP is an RD responder, the PPDU transmission during the allocation period may not necessarily include the specification that it is sent to the RD initiator.

[0171] In addition, for example, non-AP 100 may include the transmission destination information of AP 200 in the allocation period in the MU-RTS TXS trigger frame for non-AP transmission and notify it. Fig.19 As shown, non-AP100 can also be used Figure 5 The reserved bit of the user information field shown indicates the transmission destination of the AP 200 during the allocation period (the allocation duration subfield in the figure). For example, the transmission destination of the AP 200 during the allocation period is made the same as the specific example of the RD protocol described above. Fig.19An example is shown in which the AID12 subfield indicating the identification ID of the connected AP and the reserved bits are deleted.

[0172] Fig. 20 The following sequence example is shown, namely, non-AP100 (non-AP STA1 in the figure) notifies AP200 (AP in the figure) of the MU-RTS TXS trigger frame of the transmission destination including the allocation period ("allocation duration in MU-RTS TXS TF" in the figure) to instruct AP200 to share TXOP.

[0173] Fig. 20 The following operation is shown, in which the non-AP 100 obtains the transmission right of the TXOP sharing control information ("MU-RTSTXS TF" in the figure) and sets the TXOP. Then, the non-AP 100 allocates part of the TXOP or the remaining whole to the AP 200 (performs TXOP sharing).

[0174] exist Fig. 20 In the example, non-AP100 sends a MU-RTS TXS trigger frame (S2001) including the transmission destination of AP200 during the allocation period, indicating TXOP sharing to AP200. Similar to the above example, non-AP100 sets the communication destination of the service with high reservation priority as the transmission destination of AP200 during the allocation period based on the resource request information of AP200 obtained in advance from AP200.

[0175] exist Fig. 20 In the example, AP200 communicates with a non-AP (non-AP STA2) different from non-AP100. That is, an example is shown in which non-AP100 allows transmissions during the allocation period that do not include non-AP100. After AP200 sends CTS to non-AP100 (S2002), it communicates with the allowed object during the allocation period (S2003) and receives BA (S2004). Fig. 20 In the example, AP200 sends a low-latency service to non-AP STA2.

[0176] As shown in the above specific example, AP200 can send high-priority services (low-latency services) to other non-AP100 during the allocation period by non-AP100. In addition, non-AP100 allows communication with other APs that perform coordinated transmission during the allocation period, thereby improving throughput due to coordinated communication of multiple APs.

[0177] [TXOP sharing service category]

[0178] Hereinafter, a method will be described in which the non-AP 100 transmits TXOP sharing control information generated by the non-AP 100 (eg, a TXS control information generating unit) to the AP 200 to control the traffic type (TID, etc.) that can be communicated during the allocation period.

[0179] The TXS control information generated by the TXS control information generating unit includes information on the types of services that can be communicated during the allocation period. For example, non-AP 100 can limit communication to high-priority services (eg, low-latency services) during the allocation period for AP 200.

[0180] For example, information related to the service category that can be communicated during the allocation period can also be notified along with the control information (RDG) of the RD protocol. Fig.21 As shown, the reserved bits of the control information subfield may also be used to indicate the service categories that can be communicated during the allocation period (Restricted TID Bitmap subfield in the figure).

[0181] The service categories that can be communicated during the allocation period can also be used, for example, in the form of a bitmap to indicate whether they can be sent according to the TID. When the restricted TID bitmap subfield is 11000000, only service data with TID numbers 0 and 1 can be sent UL / DL during the allocation period. The TID is related to the allowed latency, so by specifying the TID, only services requiring low latency can be sent during the allocation interval. In addition, the service categories that can be communicated separately in UL and DL can also be notified. The service categories may not be 8 (the bitmap is 8 bits).

[0182] In addition, Figure 2 When the value of the control ID subfield shown is different from the size of the control information subfield when indicating CAS, it is sufficient to newly define the format of the control information subfield as a new control ID for non-APs and APs supporting enhanced 11be.

[0183] In addition, for example, information related to the types of services that can be communicated during the allocation period can also be included in the MU-RTS TXS trigger frame for non-AP transmission and notified. Fig. 22 As shown, you can also use Figure 5 A portion of the reserved bits of the user information field shown indicates the type of service that can be communicated ( Fig. 22 Restricted TID Bitmap subfield).

[0184] Fig.23 , Fig.24A sequence example is shown in which the non-AP 100 (non-AP STA1 in the figure) notifies the AP 200 (AP in the figure) of TXOP sharing by sending a MU-RTS TXS trigger frame including a traffic type that can be communicated during the allocation period.

[0185] Fig.23 , Fig.24 The following operation is shown, in which the non-AP 100 obtains the transmission right of the TXOP sharing control information ("MU-RTS TXS TF" in the figure) and sets the TXOP. Then, the non-AP 100 allocates part of the TXOP or the remaining whole to the AP 200 (performs TXOP sharing).

[0186] exist Fig.23 In the above, non-AP 100 sends a MU-RTS TXS trigger frame (S2301) including a service class that can be communicated during the allocation period ("allocation duration in MU-RTS TXS TF" in the figure), and instructs AP 200 to share TXOP. Based on the resource request information of AP 200 obtained in advance from AP 200, non-AP 100 sets a service class (TID) with a high priority among services sent from AP 200 or from AP 200 to other non-APs as a service class that can be communicated during the allocation period.

[0187] exist Fig.23 In the non-AP 100, the low-latency service is set as the service category that can be communicated during the allocation period. The AP 200 sends the indicated service category during the allocation period (S2303).

[0188] In addition, when the low-latency services reserved by the AP are small relative to the allocation period indicated by the non-AP 100, for example, when the allocation period is not properly set, the AP does not send the PPDU even if the allocation period remains. Fig.24 As shown in FIG. 24, when the non-AP 100 that has shared the TXOP does not detect a signal within a specified time (e.g., PIFS: Point coordination function (PCF) Inter Frame Space) by using carrier sensing, the non-AP 100 reacquires the TXOP and sends data to the AP 200 (S2405). Thus, only high-priority services are sent during the allocation period.

[0189] As shown in the above specific example, non-AP100 can instruct AP200 to send a service (low-latency service) with a higher priority than the service reserved by itself.

[0190] [TXOP shared resource request information]

[0191] Hereinafter, a method in which a non-AP 100 (for example, a resource request information storage unit) requests resource request information of an AP will be described.

[0192] The AP may report the transmission buffer status to the non-AP. The resource request information generated by the resource request information storage unit and notified by the AP 200 to the non-AP 100 may be, for example, a request flag, a requested allocation time, or the transmission buffer information of the AP.

[0193] The request flag is flag information indicating whether to request non-AP 100 to allocate resources.

[0194] The requested allocation time is a request time for resource allocation converted into a predetermined bandwidth (for example, 20 MHz).

[0195] The sending buffer information of the AP is at least one of the destination of the buffers reserved by the AP and the AC or TID of each buffer, the queue size of each AC and TID, and the delay budget.

[0196] The resource request information may also be set as information dedicated to each of the plurality of non-APs 100 connected to the AP 200. For example, it may be set as a set of a terminal ID (association identifier) ​​of the non-AP 100 and a flag indicating whether resource allocation is requested. Alternatively, it may be a bitmap of terminal IDs and information indicating whether resource allocation is requested.

[0197] The flag information indicating whether to request resource allocation can also be used to steal the Null Data Packet (NDP) Feedback Report that sends resource request information from the non-AP to the AP. That is, by frequency multiplexing the flag information for multiple non-APs in a specified tone within the channel, one PPDU can be used to send from AP200 to multiple non-APs100.

[0198] In addition, the resource request information may be set as information common to multiple non-APs 100 connected to AP 200. For example, a flag common to multiple non-APs 100 may be set based on the total buffer amount of multiple non-APs 100 connected to AP 200. In this case, for example, AP 200 may broadcast a resource allocation request to multiple connected non-APs 100 as broadcast information using a beacon.

[0199] The transmission buffer information of the AP may also include the transmission buffer information of other non-APs connected to the AP.

[0200] According to the above specific example, the non-AP 100 understands the resource request information of the AP 200, thereby the non-AP 100 can understand the buffer status or resource allocation request of the AP 200. Therefore, the non-AP 100 can appropriately allocate necessary resources in TXOP sharing.

[0201] In addition, by setting the resource request information as a request flag for resource allocation, non-AP 100 can grasp the resource allocation request of AP 200 with less overhead. By setting the resource request information as the requested allocation time or the transmission buffer information reserved by AP 200, although the signaling amount (overhead) is greater than the request flag, non-AP 100 can grasp the detailed buffer status, and thus can more accurately calculate the TXOP sharing allocation period for AP 200.

[0202] The resource request information may also be notified by the AP 200 after the non-AP 100 obtains the TXOP. For example, the AP 200 may also notify the resource request information by multiplexing (A-MPDU) when sending an ACK to the non-AP 100.

[0203] For example, Fig.25 , Fig.26 As shown, after obtaining TXOP, non-AP100 (non-AP STA1 in the figure) can also request AP200 to include resource request information ("RR (Resource Request)" in the figure) when sending ACK ("BA" in the figure). Fig.25 , Fig.26 In addition to sending data to AP200, non-AP100 also sends to AP200 the RDG subfield with the value set to 0 ("RDG=0" in the figure) and information prompting the sending of resource request information (for example, called "RR polling (Poll) signal". ("RR Polling" in the figure)) (S2501, S2601).

[0204] In accordance with the instruction from the non-AP 100 , the AP 200 transmits resource request information to the non-AP 100 in addition to transmitting ACK ( S2502 , S2602 ).

[0205] The non-AP 100 determines whether to implement TXOP sharing based on the resource request information from the AP 200 in the acquired TXOP.

[0206] Fig.25This indicates a sequence in which the priority of the data retained by AP200 is lower than the priority of the data retained by non-AP100. In this case, non-AP100 does not implement TXOP sharing and gives priority to the data retained by non-AP100, and transmits the data retained by non-AP100 to AP200 in the remaining TXOP (S2503, S2505).

[0207] Fig.26 Indicates a sequence in which the priority of data retained by AP200 is greater than the priority of data retained by non-AP100 (for example, in the case where AP200 retains a low-latency service). In this case, non-AP100 implements TXOP sharing (S2603) so that the data retained by AP200 is sent first (S2604).

[0208] According to the above specific example, when the AP 200 reserves a service with a higher priority than the non-AP 100, the non-AP 100 can appropriately perform TXOP sharing.

[0209] [Modifications]

[0210] TXOP sharing can combine the above records.

[0211] For example, non-AP100 can give an allocation period to a specified service category according to the transmission destination. For example, non-AP100 can give a specified allocation time to AP200 and give other specified allocation times to other APs. For example, non-AP100 can give AP200 a specified allocation time for non-AP STA1 and other specified allocation times for non-AP STA2. For example, resource request information can be set as buffer information for each service category of each STA. In addition, it can also be set to switch the communication device between non-AP STA and AP STA according to the setting.

[0212] The names of the frames, signals and formats may also be other names. The resource request information may also be other names, for example, resource information or resource request.

[0213] The names of the fields and subfields may also be other names. The user information field of the trigger frame sent by non-AP100 may also be other names. For example, it may also be an AP information field. For example, in the case of MAP coordinated transmission, there may also be multiple AP information fields.

[0214] The trigger frame sent by the non-AP 100 may also be different from the trigger frame sent by the AP 200 in format (data type or size). For example, the trigger type that can be set by the non-AP 100 may also be set as a part of the trigger type that can be set by the AP 200. For example, the trigger frame sent by the non-AP 100 may also be limited to basic and MU-RTS. By limiting the function, the implementation of the trigger frame by the non-AP becomes easy.

[0215] It is also possible to newly define an HT control field including an RDG / More PPDU subfield. For example, it is also possible to define a new control information subfield in an A-Control field by adding a control ID using reserved bits.

[0216] For example, Fig. 27 As shown, a new definition may also be provided to include, in addition to the RDG / More PPDU subfield indicating TXOP sharing, a communicable service ID ( Fig. 27 TID Constraint subfield), allocation period ( Fig. 27 The allocation duration subfield), the communication destination information during the allocation period ( Fig. 27 The control information subfield of at least one of the destination mode subfields.

[0217] In addition, if Fig.28 As shown, the RDG / More PPDU subfield indicating TXOP sharing may not include the communication destination information during the allocation period ( Fig.28 The RDG / More PPDU subfield already included in the Destination Mode subfield of the PPDU defines the control information subfield that can implement the RD protocol.

[0218] Although the present disclosure describes an example of a format of a MU-RTS TXS trigger frame using the RD protocol, the format is not limited thereto.

[0219] For example, it may be a format based on an RTS frame. The MAC header of the RTS frame does not include the HT control field (size is 0). For example, in enhanced 11be, it is also possible to define a format that includes the HT control field in the MAC header of the RTS frame. Alternatively, the HT control field may be included by packaging the RTS frame into a control wrapper frame.

[0220] Furthermore, the A control subfield contained in the HT control field may also be used to define the following Fig. 27 or Fig.28 Alternatively, a new RTS frame with a control information subfield as shown in the figure can be added to the content of the RTS frame to realize TXOP sharing. Fig. 27or Fig.28 The RTS TXS frame composed of such fields can also be defined as a new control frame. These frames based on the RTS frame can also be used instead of the MU-RTS TXS trigger frame in the above specific example.

[0221] The present disclosure can be implemented by software, hardware, or software in cooperation with hardware. The functional blocks used in the description of the above embodiments are partially or entirely implemented as LSI (Large Scale Integration) as an integrated circuit, and the processes described in the above embodiments may also be partially or entirely controlled by one LSI or a combination of LSIs. LSI can be composed of individual chips, or it can be composed of one chip in a manner that includes part or all of the functional blocks. LSI may also include data input and output. LSI is sometimes referred to as "IC (Integrated Circuit)", "System LSI", "Super LSI", "Ultra LSI" depending on the degree of integration.

[0222] The method of integrated circuitization is not limited to LSI, and can also be implemented by a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (Field Programmable Gate Array) that can be programmed after LSI manufacturing, or a reconfigurable processor (Reconfigurable Processor) that can reconfigure the connection or setting of the circuit block inside the LSI can also be used. The present disclosure can also be implemented as digital processing or analog processing.

[0223] Furthermore, if integrated circuit technology that replaces LSI emerges as semiconductor technology advances or other technologies are derived, it is of course possible to use this technology to achieve integration of functional blocks. There is also the possibility of applying biotechnology, etc.

[0224] The present disclosure can be implemented in all kinds of devices, equipment, and systems (collectively referred to as "communication devices") with communication functions. The communication device may also include a wireless transceiver and a processing / control circuit. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these parts. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or a device similar to these. Non-limiting examples of communication devices include: phones (mobile phones, smart phones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, notebook computers, etc.), cameras (digital cameras, digital video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smart watches, tracking devices, etc.), game consoles, e-book readers, telehealth / telemedicine (telehealth / medical prescription) equipment, vehicles with communication functions or transportation vehicles (cars, airplanes, ships, etc.), and combinations of the above-mentioned various devices.

[0225] Communication devices are not limited to portable or movable devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed, such as smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.

[0226] The communication includes data communication performed by a cellular system, a wireless LAN (Local Area Network) system, a communication satellite system, etc., and also includes data communication performed by a combination of these systems.

[0227] In addition, the communication device also includes devices such as controllers or sensors connected or linked to the communication device that performs the communication function described in the present invention. For example, it includes a controller or sensor that generates a control signal or data signal used by the communication device that performs the communication function of the communication device.

[0228] In addition, the communication device includes infrastructure equipment that communicates with the above-mentioned non-limiting various devices or controls the above-mentioned various devices, such as base stations, access points, and all other devices, equipment, and systems.

[0229] A non-access point station (non-AP STA) according to an embodiment of the present disclosure includes: a control unit that generates a signal indicating the following allocation, wherein the allocation is the allocation of the acquired resources specified during the allocation period; and a wireless transceiver that transmits the generated signal.

[0230] In a non-AP STA according to an embodiment of the present disclosure, the signal is a signal that allows transmission to a destination that does not include the non-AP STA.

[0231] In a non-AP STA according to an embodiment of the present disclosure, the signal is a signal that allows transmission of a specified service class when a transmission destination does not include the non-AP STA.

[0232] In a non-AP STA of an embodiment of the present disclosure, the signal is a signal allowing transmission to other access point stations (AP STA).

[0233] In a non-AP STA of one embodiment of the present disclosure, the signal is a signal indicating a transmission destination by the non-AP STA.

[0234] In the non-AP STA of one embodiment of the present disclosure, the signal is a signal indicating to the AP STA a service ID that can be communicated during the allocation period.

[0235] In a non-AP STA according to an embodiment of the present disclosure, the control unit obtains resource request information from the AP STA.

[0236] In a non-AP STA of an embodiment of the present disclosure, the resource request information is a request flag indicating whether to request resources.

[0237] In a non-AP STA according to an embodiment of the present disclosure, the resource request information specifies an allocation time for bandwidth conversion.

[0238] In a non-AP STA of one embodiment of the present disclosure, the resource request information is the transmission buffer information of the AP STA.

[0239] In a non-AP STA of an embodiment of the present disclosure, the resource request information is included in a positive response.

[0240] In a communication method according to an embodiment of the present disclosure, a non-AP STA performs the following processing: generating a signal indicating allocation of acquired resources specified during an allocation period; and transmitting the generated signal.

[0241] The disclosed contents of the specification, drawings, and abstract contained in the Japanese patent application No. 2022-131164 filed on August 19, 2022 are incorporated herein by reference in their entirety.

[0242] Industrial Applicability

[0243] One embodiment of the present disclosure is useful for a communication system.

[0244] Description of Reference Numerals

[0245] 100 Non-AP100

[0246] 101, 205 Dispatching Department

[0247] 102 TXS control information generation unit

[0248] 103 Data Generation Unit

[0249] 104 MAC information generation unit

[0250] 105, 207 Error Correction Coding Unit

[0251] 106, 208 Modulation Department

[0252] 107, 201 Wireless transceiver unit

[0253] 108, 202 Demodulation Unit

[0254] 109, 203 Error correction decoding unit

[0255] 110 Resource Request Information Retention Department

[0256] 200AP200

[0257] 204 TXS control information acquisition unit

[0258] 206 Data Generation Unit

Claims

1. A non-access point station, characterized in that: include: a control unit that generates a signal indicating allocation of the acquired resources specified in the allocation period; as well as The wireless transceiver sends the generated signal.

2. The non-access point station of claim 1, wherein: The signal is a signal that allows transmission to which a transmission destination does not include the non-access point station.

3. The non-access point station of claim 2, wherein: The signal is a signal for allowing transmission of a prescribed traffic class when the transmission destination does not include the non-access point station.

4. The non-access point station of claim 2, wherein: The signal is a signal that allows transmission to other access point stations.

5. The non-access point station of claim 2, wherein: The signal is a signal indicating a transmission destination by the non-access point station.

6. The non-access point station of claim 1, wherein: The signal is a signal indicating to the access point station a traffic identifier that may be communicated during the allocation.

7. The non-access point station of claim 1, wherein: The control unit obtains resource request information from an access point site.

8. The non-access point station of claim 7, wherein: The resource request information is a request flag indicating whether to request a resource.

9. The non-access point station of claim 7, wherein: The resource request information specifies the allocation time for bandwidth conversion.

10. The non-access point station of claim 7, wherein: The resource request information is the sending buffer information of the access point.

11. The non-access point station of claim 7, wherein: The resource request information is included in the positive response.

12. A communication method, characterized in that: Non-access point stations perform the following processing: generating a signal indicating an allocation of the acquired resources that was specified during an allocation; and The generated signal is transmitted.

Images