Communication device, control method, and program
The communication device and method address the fairness issue in IEEE 802.11bn by setting an upper limit on preemption time, ensuring balanced performance for low-latency and non-low-latency data communications.
Patent Information
- Application Number
- PCT/JP2025/016694
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-05-31
- Filing Date
- 2025-05-07
- Publication Date
- 2025-12-04
AI Technical Summary
The IEEE 802.11bn standard faces issues with fairness between low-latency and non-low-latency data communications due to preemption, where significant impairment of non-low-latency data communication performance occurs when large amounts of low-latency data are generated.
A communication device and method that includes communication means for transmitting a first PPDU during a transmission opportunity (TXOP) and notification means for setting an upper limit on the transmission opportunity for a second PPDU during preemption, ensuring fair data communication by limiting the preemption time.
The solution prevents or reduces the decrease in fairness between data communications by limiting the preemption time, maintaining balanced performance for both low-latency and non-low-latency data transmissions.
Smart Images

Figure JP2025016694_04122025_PF_FP_ABST
Abstract
Description
Communication device, control method, and program
[0001] The present disclosure relates to a communication device, a control method, and a program.
[0002] With the recent increase in the amount of data being communicated, development of communication technologies such as wireless LANs (Local Area Networks) is progressing. The IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards is known as a major communication standard for wireless LANs. The IEEE 802.11 series of standards includes standards such as IEEE 802.11a / b / g / n / ac / ax / be. To further improve communication reliability, the IEEE 802.11bn standard is being developed as a successor to the IEEE 802.11be standard. In the IEEE 802.11 Working Group (WG), which develops the IEEE 802.11bn standard, the UHR SG will determine the goals and scope of the standard, and the TGbn will specify the detailed technical content to be included in the standard. UHR SG is an abbreviation for Ultra High Reliability Study Group. TGbn is an abbreviation for Task Group bn. The name UHR was established for convenience based on the goals to be achieved in the successor standard and the key features of the standard, and may be a different name once the standard is fully developed. Similarly, the name IEEE 802.11bn may be a different name once the standard is fully developed. However, this specification and the appended claims are applicable to essentially all successor standards to the 802.11be standard.
[0003] One of the candidate technologies included in the IEEE 802.11bn standard is a communication format called Preemption, which enables data communication categorized as low-latency data. Preemption is a technology that interrupts non-low-latency data communication when low-latency data arrives during the transmission of non-low-latency data, and is expected to improve latency performance compared to existing standards.
[0004] Japanese Patent Application Laid-Open No. 2018-50133
[0005] As such, IEEE 802.11bn is currently studying the standardization of preemption communication to improve latency characteristics. However, when a large amount of data (e.g., low-latency data) that should be preempted is generated, the communication performance of other data (e.g., non-low-latency data) may be significantly impaired. In this case, fairness between these data may become an issue.
[0006] The present invention has been made in consideration of at least one of the above-mentioned problems, and an object of one aspect of the present invention is to provide a mechanism for preventing or reducing a decrease in fairness between data communications due to interrupts.
[0007] A communication device according to one aspect of the present invention is a communication device that performs communication in accordance with the IEEE 802.11 standard series, and is characterized by comprising: communication means for communicating a first PPDU (Physical layer (PHY) Protocol Data Unit) with a first other communication device during a period in which the communication device has a transmission opportunity (TXOP) for transmitting the PPDU; and notification means for notifying an upper limit value of the transmission opportunity for transmitting the second PPDU when a second other communication device transmits a second PPDU during the period.
[0008] According to one aspect of the present invention, it is possible to provide a mechanism for preventing or reducing a decrease in fairness between data communications due to interrupts.
[0009] 1 is a diagram showing an example of the configuration of a wireless communication system according to the present embodiment. FIG. 2 is a diagram showing an example of the functional configuration of a communication device according to the present embodiment. FIG. 3 is a diagram showing the hardware configuration of a communication device according to the present embodiment. FIG. 4 is a sequence diagram showing communication processing executed in the first embodiment. FIG. 5 is a diagram showing an example of the format of a control frame used to notify a preemption communication time upper limit value in the first embodiment. FIG. 6 is a diagram showing an example of the format of a control frame used to notify a preemption communication time upper limit value in the first embodiment. FIG. 7 is a diagram showing an example of the format of a PPDU used to notify a preemption communication time upper limit value in the first embodiment. FIG. 8 is a flowchart showing processing executed by an AP 102 in the first embodiment. FIG. 9 is a flowchart showing processing executed by a STA 104 in the first embodiment. FIG. 10 is a sequence diagram showing communication processing executed in the second embodiment. FIG. 11 is a diagram showing an example of the format of a frame used to notify a preemption communication time upper limit value in the second embodiment. FIG. 12 is a flowchart showing processing executed by an AP 102 in the second embodiment. FIG. 13 is a flowchart showing processing executed by a STA 103 in the second embodiment. FIG. 14 is a sequence diagram showing communication processing executed in the third embodiment. FIG. 15 is a sequence diagram showing communication processing executed in the third embodiment. FIG. 13 is a diagram showing an example of the format of a first portion used to notify a preemption communication time upper limit value in the third embodiment.
[0010] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the claimed invention. Although the embodiments describe multiple features, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined in any desired manner.
[0011] (Network Configuration) Fig. 1 shows an example of the configuration of a network according to this embodiment. Fig. 1 shows a configuration including one AP 102 and two STAs 103 and 104 as communication devices that perform wireless LAN communication in accordance with the IEEE 802.11bn standard. As shown in Fig. 1, the network formed by the AP 102 is indicated by a circle 101. The STAs 103 and 104 can transmit and receive signals transmitted and received by the AP 102.
[0012] Note that this diagram is merely an example, and other communication devices performing wireless LAN communication may exist in a wider area. These communication devices may be communication devices performing wireless LAN communication in accordance with the IEEE 802.11be standard. Alternatively, they may be so-called legacy devices that are not compliant with the IEEE 802.11bn standard but are compliant only with the IEEE 802.11a / b / g / n / ac / ax / be standard.
[0013] The AP 102 and the STAs 103 and 104 may also be configured to support wireless communication based on other communication standards such as Bluetooth (registered trademark), NFC, Bluetooth (registered trademark) LE (Low Energy), etc. NFC stands for Near Field Communication.
[0014] The AP 102 and the STAs 103 and 104 may also be configured to support wired communication using an Ethernet cable or wired communication using optical fiber. The AP 102 and the STAs 103 and 104 may also be configured to support cellular wireless communication such as 5G or LTE (Long Term Evolution).
[0015] Specific examples of the AP 102 include, but are not limited to, a wireless LAN router and a personal computer (PC). The AP 102 and the STAs 103 and 104 may also be information processing devices such as wireless chips that support the transmission and reception of PPDUs. In this case, the wireless chips may be configured to perform various controls using internal hardware circuits. The wireless chips may also be configured to perform various processes through the cooperation of a processor, memory, and hardware circuits such as an ASIP within the wireless chip. ASIP stands for Application-Specific Instruction Set Processor.
[0016] Specific examples of the STAs 103 and 104 include, but are not limited to, cameras, tablets, smartphones, PCs, mobile phones, video cameras, smart glasses, and wearable devices such as HMDs (head-mounted displays).
[0017] In the following description, the AP 102 and the STAs 103 and 104 will be used as examples.
[0018] (Configuration of AP and STA) FIG. 2 is a block diagram showing the functional configuration of the AP 102 and the STAs 103 and 104. As shown in FIG.
[0019] Here, the AP 102 and the STAs 103 and 104 have a wireless LAN control unit 201 , a wireless frame generation unit 202 , a wireless frame processing unit 203 , a UI control unit 204 and a storage control unit 205 .
[0020] The wireless LAN control unit 201 includes an antenna and circuitry for transmitting and receiving wireless signals to and from other communication devices, and a program for controlling them. The wireless LAN control unit 201 controls wireless LAN communications based on frames generated by the frame generation unit in accordance with the IEEE 802.11 standard series.
[0021] The wireless frame generating unit 202 generates a frame to be transmitted by the wireless LAN control unit 201 .
[0022] The wireless frame processing unit 203 processes frames received from other communication devices.
[0023] The UI control unit 204 includes hardware related to the user interface, such as a touch panel or buttons, for accepting operations on the AP by a user who uses the AP, and programs for controlling these. The UI control unit 204 also has a function for presenting information to the user, such as displaying images or outputting audio. The memory control unit 205 controls writing and reading of data to and from memory units, such as ROM and RAM, that store programs and data running on the AP.
[0024] 3 shows the hardware configuration of the AP 102 and the STAs 103 and 104 according to this embodiment. The AP and the STA each include, as an example of their hardware configuration, a storage unit 301, a control unit 302, a function unit 303, an input unit 304, an output unit 305, a communication unit 306, and a wireless antenna 307.
[0025] The storage unit 301 is configured with one or more memories such as ROM and / or RAM, and stores various information such as programs for performing various operations described below and communication parameters for wireless communication. Note that in addition to memories such as ROM and RAM, storage media such as flexible disks, hard disks, SSDs, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, magnetic tapes, non-volatile memory cards, and DVDs may also be used as the storage unit 301. SSD is an abbreviation for Solid State Drive.
[0026] The control unit 302 is configured by, for example, one or more processors such as a CPU or MPU, an ASIC (application-specific integrated circuit), a DSP (digital signal processor), an FPGA (field programmable gate array), etc. Here, CPU is an acronym for Central Processing Unit, and MPU is an acronym for Micro Processing Unit. The control unit 302 controls the entire device by executing programs stored in the storage unit 301.
[0027] The control unit 302 may control the device in cooperation with an OS (Operating System) and a program stored in the storage unit 301. The control unit 302 also controls the function unit 303 to perform predetermined processes such as imaging, printing, and projection.
[0028] The functional unit 303 is hardware that enables the AP or STA to execute predetermined processing. For example, if the AP or STA is a camera, the functional unit 303 is an imaging unit that performs imaging processing. Also, for example, if the AP or STA is a printer, the functional unit 303 is a printing unit that performs printing processing. Also, for example, if the AP or STA is a projector, the functional unit 303 is a projection unit that performs projection processing. The data processed by the functional unit 303 may be data stored in the storage unit 301, or may be data communicated with another communication device via the communication unit 306, which will be described later.
[0029] The input unit 304 receives various operations from the user. The output unit 305 outputs various types of information to the user. Here, the output by the output unit 305 includes at least one of display on a screen, audio output by a speaker, vibration output, and the like. Note that both the input unit 304 and the output unit 305 may be implemented by a single module, such as a touch panel. Furthermore, the input unit 304 and the output unit 305 may be integrated with the AP or STA, respectively, or may be separate units.
[0030] The communication unit 306 includes a so-called wireless LAN chip and controls wireless communication compliant with the IEEE 802.11 standard series and IP communication. In this embodiment, the communication unit 306 can execute processing compliant with at least the IEEE 802.11bn standard.
[0031] The communication unit 306 is a processing device that generates a UHR PPDU (Physical layer (PHY) Protocol Data Unit) defined in the IEEE 802.11bn standard. However, the communication unit 306 may have a function to generate a type of PPDU defined in a standard earlier than the IEEE 802.11bn standard.
[0032] The communication unit 306 also controls the wireless antenna 307 to transmit and receive wireless signals for wireless communication. The AP and STA communicate content such as image data, document data, and video data with other communication devices via the communication unit 306.
[0033] The wireless antenna 307 may be physically configured with two or more antennas to realize MIMO (Multi-Input and Multi-Output) transmission and reception. The wireless antenna 307 may be configured as a separate unit from the communication unit 306, or may be configured as a single module together with the communication unit 306. The wireless antenna 307 is an antenna capable of communication in the 2.4 GHz band, 5 GHz band, 6 GHz band, 45 GHz band, and 60 GHz band.
[0034] 3, the communication device has one antenna, but the communication device may have two or more antennas. Alternatively, the communication device may have a different antenna for each frequency band. In the example of FIG. 3, the communication device is configured to have only one communication unit 306, but a separate communication unit may be provided for each of multiple wireless antennas.
[0035] The AP 102 may be any communication device having the configurations of Figures 2 and 3, and may be a so-called AP-dedicated communication device such as a wireless LAN router, or may be a communication device having AP functionality such as a smartphone, camera, or printer.
[0036] (Processing Flow) Next, several embodiments will be described, including the processing flow executed by the AP and STA as described above, and the sequence in the wireless communication system.
[0037] First Embodiment FIG. 4 is a sequence diagram showing an example of a process in which the STA 104 transmits a preemption signal to the AP 102 while the AP 102 is transmitting a signal to the STA 103 .
[0038] In this embodiment, the AP 102 acquires a TXOP in order to transmit a PPDU to the STA 103. In this TXOP, the AP 102 permits preemption communication to all connected STAs that support preemption communication. The AP 102 divides the PPDU to be transmitted to the STA 103 into an appropriate number of PPDUs and transmits the divided PPDUs in multiple batches.
[0039] The AP 102 transmits an RTS (Request-To-Send) frame 401 to the STA 103. Upon receiving the RTS frame 401, the STA 103 transmits a CTS (Clear-To-Send) frame 402 to the AP 102. A preemption-incompatible STA (not shown) that receives the CTS frame 402 enters a NAV (Network Allocation Vector: transmission prohibition time) and is unable to transmit during the transmission time of the AP 102. The preemption-compatible STA 104 does not enter the NAV. The AP 102 transmits a PPDU 403 to the STA 103, and the STA 103 transmits a BlockAck frame 404, which is a signal acknowledging receipt of the PPDU 403, to the AP 102. Next, AP 102 transmits PPDU 405 to STA 103, and STA 103, having received PPDU 405, transmits BlockAck frame 406 to AP 102. The transmission of PPDU 405 is the second transmission of the segmented PPDU, and if there is no preemption communication, the transmission of the PPDU from AP 102 to STA 103 and the transmission of BlockAck from STA 103 to AP 102 are repeated the number of times equal to the number of segmented PPDUs.
[0040] In this embodiment, the STA 104 receives low-latency data while the AP 102 is transmitting a PPDU 405. The STA 104 transmits the received low-latency data to the AP 102 by preemption communication, and therefore transmits a Preemption Request 407 to the AP 102 after transmitting a BlockAck frame 406. The AP 102 receives the Preemption Request frame 407 and transmits a Preemption Response frame 408 to the STA 104 to notify it of permission for preemption communication and the upper limit of the transmission PPDU time.
[0041] The upper limit of the transmission PPDU time can be determined by the AP 102 before acquiring the TXOP, depending on the specifications and settings of the AP 102 or the communication conditions of the AP itself and surrounding terminals. The determination may be made after acquiring the TXOP, or may be changed as appropriate during the process.
[0042] Upon receiving the Preemption response frame, STA 104 transmits a PPDU 409 to AP 102 based on the information about preemption included in the frame. AP 102 transmits a BlockAck frame 410 to STA 104, ending preemption communication, and resumes transmission of a PPDU 411 to STA 103. STA 103 transmits a BlockAck frame 412 in response to PPDU 411 to AP 102, but STA 104 can then perform preemption communication again.
[0043] The frame formats of the Preemption Request frame 407 and the Preemption Response frame 408 are shown in FIGS. 5A and 5B, respectively.
[0044] The format of the Preemption Request frame is made up of a Frame control field 501, a Duration / ID field 502, an RA field 503, a TA field 504, and an FCS field 505. The Frame control field 501 has a Protocol Version subfield 506, a Type subfield 507, and a Subtype subfield 508 from the beginning.
[0045] The format of the Preemption response frame includes a Frame control field 509 and a Duration / ID field 510. This format also includes an RA field 511, a Preemption allowance field 512, a Preemption limit field 513, and an FCS field 514. The Frame control field 509 is the same as the Frame control field 501 of the Preemption request frame. That is, the Frame control field 509 includes a Protocol Version subfield 506, a Type subfield 507, and a Subtype subfield 508.
[0046] The type of the frame is indicated by the values of the Type subfield 507 and the Subtype subfield 508. Table 1 shows the relationship between the values and the types.
[0047]
[0048] A value of 01 in the Type subfield indicates that both the Preemption request frame and the Preemption response frame are Frame Control. The Subtype subfield contains a value indicating the type of frame, but the values shown in Table 1 are merely examples and other values may be used. Also, in Table 1, the type of frame is expressed by a combination of the Type subfield and the Subtype subfield, but other subfields may be used appropriately to express the type of frame.
[0049] The Preemption allowance field 512 included in the Preemption response frame is a 1-bit field as follows: That is, it is a 1-bit field indicating whether or not the AP 102 permits preemption to the STA 104 that transmitted the Preemption request frame.
[0050] The Preemption limit field 513 indicates the upper limit of the time length of a single PPDU transmitted by the STA 104 in preemption communication. For example, it can be set to a 15-bit field that can indicate a value from 0 to 65,535 microseconds. The number of bits may be other than 15, and the value may not be in units of 1 microsecond. Alternatively, the upper limit of the time length of the PPDU may be determined from the value of the Preemption limit field according to a predetermined table.
[0051] The Preemption limit field 513 may be an upper limit value for the total time length of a single PPDU that the STA 104 transmits in preemption in the TXOP. In other words, when preemption communication is performed multiple times in the TXOP, a frame exchange of a Preemption request frame and a Preemption response frame occurs between the AP 102 and the STA 104 for each communication. However, the value included in the Preemption limit field 513 indicated by the Preemption response frame may be a value obtained by subtracting the time length of PPDUs that have already been transmitted in preemption. Alternatively, the Preemption limit field 513 may be an upper limit value indicating the number of PPDUs that the STA 104 transmits in preemption in the TXOP. For example, storing a 0 in this field may indicate that the STA 104 may transmit only a single SU PPDU in the TXOP. Additionally, this may indicate that the STA 104 may transmit only a single MU PPDU or a single TB PPDU in the TXOP. Note that SU PPDU stands for Single-User PPDU, MU PPDU stands for Multi-User PPDU, and TB PPDU stands for Trigger-based PPDU.
[0052] In addition to the above-described configuration, the preemption communication time upper limit value may be included in the PPDU 405 transmitted by the AP 102 to the STA 103. The frame format of the PPDU in this case is shown in FIG.
[0053] The PPDU includes a Frame control field 601, a Duration / ID field 602, an Address 1 field 603, an Address 2 field 604, and an Address 3 field 605. The PPDU also includes a Sequence Control field 606, an Address 4 field 607, and a QoS Control field 608. The PPDU also includes an A-Control field 609, a Frame body field 610, and an FCS field 611. The Type subfield and Subtype subfield included in the Frame control field 601 are Type=10 and Subtype=0000, respectively, which indicates that this frame is a PPDU. The A-Control field 609 is made up of a Control list subfield 612 and a Padding field 613. The Control list subfield 612 is made up of a combination of a Control ID subfield 614 and a Control information subfield 615.
[0054] The Control list subfield with Control ID = 10 is defined as the Preemption Control subfield. The Control ID may be any other value that is a reserved value in existing standards. The Control information subfield 615 is composed of a Preemption allowance subfield 616 and a Preemption limit subfield 617. Both subfields store the same information as the subfields of the same name contained in the Preemption response frames in Figures 5A and 5B. However, the A-Control field 609 is 30 bits and the Control ID subfield 614 is 4 bits, as determined by the IEEE 802.11 standard. Therefore, the combined length of the Preemption allowance subfield 616 and the Preemption limit subfield 617 must be 26 bits or less.
[0055] FIG. 7 is a flowchart illustrating the operation of the AP 102 in this embodiment.
[0056] After the AP 102 acquires the TXOP, it divides the PPDU to be transmitted to the STA 103 into N pieces (S701).
[0057] N is an integer of 2 or more and is a predetermined value.
[0058] An RTS frame is transmitted to the STA 103 (S702), and a CTS frame transmitted from the STA 103 is received (S703).
[0059] Thereafter, the STA 103 transmits a PPDU to the STA 103 (S704), and receives a BlockAck frame (denoted as "BA" in FIG. 7) transmitted by the STA 103 (S705).
[0060] It is determined whether a Preemption Request frame is received within a certain time period after receiving the BlockAck frame (S706), and if a Preemption Request frame is received, the process proceeds to S707. In S707, the AP 102 transmits a Preemption response frame to the STA 104 in response to the Preemption request frame.
[0061] Thereafter, the AP 102 receives the PPDU transmitted by the STA 104 in the preemption communication (S708), and transmits a BlockAck frame including reception success / failure information of the received PPDU to the STA 104 (S709). When S709 ends, the process returns to S706.
[0062] If a Preemption request frame is not received in S706, the process proceeds to S710. If the transmitted PPDU is the Nth PPDU, the process proceeds to S711. If the transmission inhibition period (NAV) has ended, the sequence ends.
[0063] If it is determined in step S711 that the transmission inhibition period (NAV) has not ended, the process proceeds to step S706, where the reception of a preemption request frame is waited for a certain period of time.
[0064] If the PPDU transmitted in S710 is not the Nth PPDU, the process proceeds to S702 to transmit the next PPDU.
[0065] FIG. 8 is a flowchart illustrating the operation of the STA 104 in this embodiment.
[0066] First, the STA 103 receives an RTS frame transmitted to another STA belonging to the BSS to which the STA 103 belongs and a CTS frame transmitted to the AP by the STA to which the RTS frame is transmitted, and acquires the transmission inhibition period (NAV) (S801).
[0067] It is determined whether the transmission prohibition time has ended (S802), and if it has ended, this sequence ends.
[0068] If the transmission prohibition time has not expired, it is determined whether low-latency data to be transmitted by preemption communication exists in the transmission buffer of the STA 104 (S803). If low-latency data does not exist in the transmission buffer of the STA 104, the process returns to S802.
[0069] If low-latency data exists, the process proceeds to S804, and if frame transmission is not performed for a certain period of time, the process proceeds to S805.
[0070] In S805, a preemption request frame is transmitted to the AP 102.
[0071] The preemption response frame is received from the AP 102, and the values of the preemption allowance field and the preemption limit field are obtained (S806). The calculated preemption transmission time upper limit is denoted as L_prlim.
[0072] If the Preemption allowance field has a value that allows preemption communication (S807), the process proceeds to S808.
[0073] The PPDU length (denoted as L_ppdu) to be transmitted to the AP 102 is determined so as to be equal to or less than L_prlim (S808).
[0074] The PPDU is transmitted to the AP 102 as a preemption (S809), and a BlockAck frame is received from the AP 102 (S810).
[0075] Then, the process proceeds to S802. If it is determined in S803 that low-latency data does not exist in the transmission buffer of the STA 104, the process proceeds to S802.
[0076] If preemption is not permitted in S807, the process proceeds to S811, where the process waits until the transmission prohibition time has ended, and when the transmission prohibition time has ended, the process of this flowchart ends.
[0077] In the example shown in FIG. 8, if preemption is not permitted in S807, the process proceeds to S811, but may also be returned to S802.
[0078] 8, the process returns to S802 after S810. However, if the PPDU length required to transmit the low-latency data to be transmitted in preemption communication is longer than L_prlim, the process may proceed as follows. That is, although the process returns to S802, if the transmission prohibition time has not expired in S802, S803 may be skipped. If frame transmission is not performed for a certain period of time in S804, S805 to S807 may be skipped and the process may proceed to S808.
[0079] According to the first embodiment described above, when a PPDU of low latency data is transmitted from the STA 104 to the AP 102 by interrupt during a transmission prohibition time, the transmission time of the low latency data can be limited so as not to exceed the upper limit value (L_prlim). This ensures a certain level of fairness between communications of low latency data and non-low latency data.
[0080] In the first embodiment, a case where a PPDU of low latency data is transmitted from STA 104 to AP 102 by interrupt during a transmission prohibition time is mainly described, but the present invention is not limited to this. That is, the first embodiment is also applicable to a case where a PPDU of low latency data is transmitted from AP 102 to STA 104 by interrupt during a transmission prohibition time. In this case, STA 103 may acquire a TXOP to transmit a PPDU to AP 102, and may notify AP 102 of a preemption communication time upper limit. In this case, the preemption communication time upper limit may be included in a PPDU (not shown) transmitted from STA 103 to AP 102. In this case, the frame format of the PPDU may be as shown in FIG. 6 .
[0081] Second Embodiment FIG. 9 is a sequence diagram showing an example of a process in which the AP 102 transmits a PPDU to the STA 104 in preemption communication while the STA 103 that has acquired a TXOP is transmitting to the AP 102.
[0082] In this embodiment, STA 103 acquires a TXOP in order to transmit a PPDU to AP 102. In this TXOP, STA 103 permits preemption communication to all STAs connected to preemption communication-compatible APs. STA 103 divides the PPDU to be transmitted to AP 102 into an appropriate number of PPDUs and transmits the divided PPDUs in multiple transmissions.
[0083] After acquiring the TXOP, the STA 103 transmits a Preemption report frame 901 to all STAs that belong to the same BSS as the connected AP.
[0084] FIG. 10 shows the frame format of the preemption report frame 901 .
[0085] The Preemption Report frame includes a Frame Control field 1001, a Duration / ID field 1002, an RA field 1003, and a TA field 1004. The Preemption Report frame also includes a BSSID field 1005, a Preemption Allowance field 1006, a Preemption Limit field 1007, and an FCS field 1008.
[0086] The configuration of the Frame control field 1001 is the same as that shown in the first embodiment, and the Type subfield and Subtype subfield included therein specify the type of frame. In this embodiment, when the value of the Type subfield is 01 and the value of the Subtype subfield is 0010, this indicates that the frame is a Preemption report frame. However, even if the above values are different, it is sufficient as long as it indicates that the frame is a Preemption report frame.
[0087] The AP and STA that received this frame determine from the BSSID field 1005 whether or not the frame was sent to the BSS to which the terminal itself belongs.
[0088] If the value of the BSSID field 1005 matches the BSS to which the terminal belongs, information on whether preemption communication is permitted is obtained from the value of the Preemption allowance field 1006. Also, information on the upper limit of preemption communication is obtained from the Preemption limit field 1007.
[0089] The Preemption limit field indicates the upper limit of the total preemption communication time allowed for the AP and STA in the TXOP. For example, it can be set as a 15-bit field that can indicate a range from 0 to 65,535 microseconds. The number of bits may be other than 15, and may not be in units of 1 microsecond. A method may be used in which the upper limit of the PPDU time length is determined from the value of the Preemption limit field according to a predetermined table.
[0090] The Preemption limit field may be an upper limit value of the total time length of a single PPDU that the AP 102 transmits in preemption in the TXOP. In other words, if preemption communication is performed multiple times in the TXOP, frame exchange occurs multiple times between the AP 102 and the STA 104. That is, frame exchange of a preemption request frame and a preemption response frame occurs between the AP 102 and the STA 104 for each preemption communication. In this case, the value included in the Preemption limit field indicated by the Preemption response frame may be a value obtained by subtracting the time length of the PPDU that has already been transmitted in preemption. The Preemption limit field may also be an upper limit value indicating the number of PPDUs that the STA 104 transmits in Preemption during the TXOP. For example, storing 0 in this field may indicate that the STA 104 may transmit only a single SU PPDU during the TXOP. In addition, this may also indicate that the STA 104 may transmit only a single MU PPDU or a single TB PPDU during the TXOP. SU PPDU stands for Single-User PPDU, MU PPDU stands for Multi-User PPDU, and TB PPDU stands for Trigger-based PPDU.
[0091] In this embodiment, preemption is performed during the NAV period set by the STA 103. However, the upper limit of the total preemption communication time permitted for each of the AP and STA in the NAV may be equal to the product of the NAV time length and the value of the Preemption limit field. Alternatively, instead of the upper limit of the total preemption communication time, the upper limit of the total time length of a single PPDU to be transmitted may be considered. In either case, the value of the Preemption limit field is between 0 and 1. For example, when the Preemption limit field is 7 bits, the value obtained by multiplying the decimal representation of the Preemption limit field by 1 / 128 becomes the Preemption limit.
[0092] The AP and STA that receive the preemption report frame 901 acquire preemption permission information and a preemption upper limit value, which are information about preemption communication included in the frame.
[0093] The STA 103 transmits an RTS frame 902 to the AP 102 , and the AP 102 transmits a CTS frame to the STA 103 as a response signal to the RTS frame 902 .
[0094] Thereafter, the STA 103 transmits a PPDU 904 to the AP 102 , and upon receiving the PPDU 904 , the AP 102 transmits a BlockAck frame 905 including PPDU reception information to the STA 103 .
[0095] The STA 103 transmits the next segmented PPDU 906 to the AP 102 , and the AP 102 transmits a BlockAck frame 907 to the STA 103 .
[0096] The AP 102 obtains the low latency data while receiving the PPDU 906 .
[0097] In response to this, the AP 102 transmits a Preemption request frame 908 to the STA 104 , and the STA 104 transmits a Preemption response frame to the AP 102 .
[0098] The Preemption response frame of this embodiment may be different from the Preemption response frame described in the first embodiment. That is, it may not have a Preemption limit field that specifies the length of the PPDU to be transmitted in Preemption. The upper limit of the length of the PPDU to be transmitted in Preemption may be specified based on the Preemption limit field specified in the Preemption report frame 901.
[0099] The AP 102 transmits a PPDU 910 including low-latency data to the STA 104, and the STA 104 transmits a BlockAck frame 911 including information on whether the PPDU can be received to the AP 102.
[0100] Upon receiving the completion of the preemption communication, the STA 103 transmits a PPDU 912 , which is the next PPDU after the PPDU 906 , to the AP 102 , and the AP 102 transmits a BlockAck frame to the STA 103 .
[0101] FIG. 11 is a flowchart illustrating the operation of the AP 102 in this embodiment.
[0102] The flowchart starts by receiving a Preemption report frame from the STA 103 and acquiring the Preemption limit. The acquired value is defined as L_prlim.
[0103] The AP 102 receives an RTS frame from the STA 103 and acquires the NAV (S1101).The AP 102 transmits a CTS frame to the STA 103 in response to the RTS frame (S1102).
[0104] When a PPDU is received from the STA 103 in step S1103, a BlockAck frame is transmitted to the STA 103 (S1104).
[0105] If no PPDU is received from the STA 103 in step S1103, the process proceeds to S1105.
[0106] It is determined whether NAV has ended (S1105), and if so, this flowchart ends. If NAV has not ended, the process proceeds to S1106. Then, it is confirmed whether low-latency data to be preemption-transmitted exists in the transmission buffer (S1106). If low-latency data does not exist in the transmission buffer, the process returns to S1103.
[0107] If low-delay data exists, a preemption request frame is transmitted to the STA 104 (S1107).
[0108] If a Preemption response frame is received from the STA 104 in S1108, the process proceeds to S1109, and if not, the process proceeds to S1102.
[0109] The PPDU length (denoted as L_ppdu) to be transmitted to the STA 104 is determined so as to be equal to or less than L_prlim (S1109).
[0110] A PPDU is transmitted to the STA 104 (S1110), and the value of L_prlim is updated by subtracting L_ppdu from it (S1111).
[0111] A BlockAck frame is received from the STA 104 (S1112), and the process proceeds to S1102.
[0112] FIG. 12 is a flowchart illustrating the operation of the STA 103 in this embodiment.
[0113] After the STA 103 acquires the TXOP, it transmits a Preemption report frame to the AP and STAs that belong to the same BSS (S1201).
[0114] The PPDU to be transmitted to the AP 102 is divided into N pieces (S1202), where N is a predetermined integer equal to or greater than 2. An RTS frame is transmitted to the AP 102 (S1203), and a CTS frame transmitted from the AP 102 is received (S1204).
[0115] Thereafter, the PPDU is transmitted to the AP 102 (S1205), and the BlockAck frame transmitted by the AP 102 is received (S1206).
[0116] If a preemption request frame addressed to another terminal is received in S1207, the process proceeds to S1208, and if not, the process proceeds to S1209.
[0117] In S1208, preemption communication is performed between the AP 102 and the STA 104, and the STA 103 receives the PPDU and BlockAck frame exchanged between the frames, and the process proceeds to S1207.
[0118] If it is determined in S1209 that the segmented PPDU transmitted in S1205 is the Nth segment, the process proceeds to S1210; if not, the process proceeds to S1205.
[0119] If NAV has not ended in S1210, the process proceeds to S1207, and if it has ended, the process ends this flowchart.
[0120] According to the second embodiment described above, when a PPDU of low latency data is transmitted from the AP 102 to the STA 104 by interrupt during a transmission prohibition time, the transmission time of the low latency data can be limited so as not to exceed the upper limit value (L_prlim). This ensures a certain level of fairness between communications of low latency data and non-low latency data.
[0121] Although the second embodiment mainly describes a case where a PPDU of low latency data is transmitted from the AP 102 to the STA 104 by interrupt during a transmission prohibition time, the present invention is not limited to this. That is, the second embodiment is also applicable to a case where a PPDU of low latency data is transmitted from the STA 104 to the AP 102 by interrupt during a transmission prohibition time.
[0122] Furthermore, the second embodiment assumes a case in which the AP 102 transmits a preemption signal to the STA 104 while the STA 103 acquires a TXOP and is transmitting a PPDU to the AP 102, but is not limited to this. That is, the second embodiment is also applicable to a case in which the STA 104 transmits a preemption signal to the AP 102 while the AP 102 acquires a TXOP and is transmitting a PPDU to the STA 103. In this case, the AP 102 may transmit a frame corresponding to the preemption report frame to the STA 103 or STA 104 after acquiring the TXOP.
[0123] 13A and 13B are sequence diagrams showing an example of processing based on the same premise below. The premise is as follows: AP 102 notifies the connected STA of information related to preemption communication, including a preemption limit. Then, while AP 102 acquires a TXOP and is transmitting a PPDU to STA 103, STA 104 transmits a preemption to AP 102.
[0124] First, the format shown in Fig. 13A will be described. AP 102 transmits a beacon frame 1301 to all connected STAs at regular intervals. The beacon frame 1301 includes a Preemption element, an example of which is shown in Fig. 14. The Preemption element includes an Element ID field 1401, a Length field 1402, and an Element ID Extension field 1403. The Preemption element also includes a Preemption allowance field 1404 and a Preemption limit field 1405.
[0125] When the value of the Element ID field is 255 and the value of the Element ID Extension field is 136, this indicates that this element is a Preemption element.
[0126] The values in the Element ID field and the Element ID Extension field are merely examples, and other combinations that do not overlap with the elements defined in the IEEE 802.11 series standards may be used.
[0127] The Preemption element may use the Element ID field, which is a reserved value in existing standards, for the Preemption element, and may not include the Element ID Extension field. The bit lengths and meanings of the Preemption allowance field 1404 and Preemption limit field 1405 are the same as those of the fields with the same names described in the first and second embodiments.
[0128] After acquiring the TXOP, the AP 102 transmits an RTS frame 1302 to the STA 103 and receives a CTS frame 1303 transmitted by the STA 103 .
[0129] The AP 102 divides the PPDU to be transmitted to the STA 103 into an appropriate number of PPDUs and transmits the divided PPDUs to the STA 103 in multiple batches.
[0130] The AP 102 transmits a PPDU 1304 to the STA 103 and receives a BlockAck frame 1305 transmitted by the STA 103 .
[0131] The AP 102 again transmits a PPDU 1306 to the STA 103 , and after receiving a BlockAck frame 1307 transmitted by the STA 103 , receives a Preemption request frame 1308 from the STA 104 .
[0132] The AP 102 transmits a Preemption response frame 1309 to the STA 104 as a response signal.
[0133] The frame format of the preemption request frame and the preemption response frame may be the frame format described in the first embodiment, or may be a configuration that does not include the preemption allowance field and the preemption limit field.
[0134] The STA 104 transmits a PPDU 1310 including low-latency data to the AP 102 as a preemption, and the AP 102 transmits a BlockAck frame 1311 to the STA 104 .
[0135] After the preemption communication is completed, the AP 102 transmits the divided PPDU 1312 to the STA 103 , and the STA 103 transmits a BlockAck frame 1313 to the AP 102 .
[0136] In the form shown in FIG. 13B, information regarding preemption is notified by including it in the information exchanged when the AP and the STA connect.
[0137] When the AP 102 and the STA 104 connect to each other, the STA 104 transmits an association request frame 1314 to the AP 102, and then the AP 102 transmits an association response frame 1315 to the STA 104. The association response frame 1315 includes the preemption element shown in Fig. 14. The preemption element is the same as that described in the embodiment in which information related to preemption communication is notified by the beacon frame.
[0138] The association request frame 1314 may include a preemption element. In this case, the value indicated by the preemption limit field 1405 may be used as the requested upper limit value for the total time length of the PPDU in preemption communication transmitted from the STA 104 to the AP 102. Upon receiving the association request frame 1314, the AP 102 determines or updates the upper limit value for the total time length of the PPDU from the requested value. For example, if the specified value is greater than the requested value from the STA 104, the requested value from the STA 104 may be used as the upper limit value for the total time length of the PPDU, and if the specified value is smaller than the requested value from the STA 104, the upper limit value for the total time length of the PPDU may not be updated. In this embodiment, the beacon frame, the association request frame, and the association response frame include a preemption element, but the present invention is not limited to this. For example, the probe request frame, the probe response frame, the reassociation request frame, and the reassociation response frame may include the preemption element. This allows the STA 104 to notify the upper limit required for the total time length of the PPDU in preemption communication using the probe request frame and the reassociation request frame. Also, for example, the AP 102 can notify the upper limit of the total time length of the PPDU in preemption communication using a probe response frame and a reassociation response frame.
[0139] The processing performed after the AP 102 acquires the TXOP is the same as that described above in the embodiment in which information related to preemption communication is notified using a beacon frame, and therefore a description thereof will be omitted. Information related to preemption communication using an association response frame is notified only at the time of connection. Therefore, by combining this method with the information notification using the beacon frame described above and the information notification method described in the first and second embodiments, it is also possible to update related information.
[0140] According to the third embodiment described above, when a PPDU of low latency data is transmitted from the STA 104 to the AP 102 by interrupt during a transmission prohibition time, the transmission time of the low latency data can be limited so as not to exceed the upper limit value (L_prlim). This ensures a certain level of fairness between communications of low latency data and non-low latency data.
[0141] (Other Embodiments) A storage medium on which program code for software that realizes the above-described functions is recorded may be supplied to a system or device, and a computer (CPU, MPU) of the system or device may read and execute the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium on which the program code is stored constitutes the above-described device.
[0142] Examples of storage media that can be used to supply the program code include flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, and DVDs.
[0143] In addition, not only can the above-mentioned functions be realized by the computer executing the program code it has read, but the OS running on the computer can also perform some or all of the actual processing based on the instructions of the program code to realize the above-mentioned functions.
[0144] Furthermore, the program code read from the storage medium may be written to a memory provided in a function expansion board inserted into a computer or a function expansion unit connected to the computer, and a CPU provided in the function expansion board or function expansion unit may then perform some or all of the actual processing based on the instructions of the program code to realize the above-mentioned functions.
[0145] The present invention can also be realized by supplying a program that realizes one or more of the functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program.The present invention can also be realized by a circuit (e.g., an ASIC) that realizes one or more of the functions.
[0146] The present invention is not limited to the above-described embodiments, and various modifications and variations can be made without departing from the spirit and scope of the present invention. Therefore, to apprise the public of the scope of the present invention, the following claims are appended.
[0147] This application claims priority based on Japanese Patent Application No. 2024-088647, filed May 31, 2024, the entire contents of which are incorporated herein by reference.
Claims
1. A communications device that performs communications in accordance with the IEEE 802.11 standard series, comprising: a communications means for communicating a first PPDU (Physical layer (PHY) Protocol Data Unit) with a first other communications device during a period in which the communications device has a transmission opportunity (TXOP) for transmitting the PPDU; and a notification means for notifying the second other communications device of an upper limit of the transmission opportunity for transmitting the second PPDU when the second other communications device transmits a second PPDU during the period.
2. A communications device that communicates in accordance with the IEEE 802.11 standard series, comprising: a communications means for communicating a first PPDU (Physical layer (PHY) Protocol Data Unit) with a first other communications device during a period in which the first other communications device has a transmission opportunity (TXOP) for transmitting the PPDU; and a notification means for notifying a second other communications device of an upper limit of the transmission opportunity for transmitting the second PPDU when the second other communications device transmits a second PPDU during the period.
3. The communication device according to claim 1 or 2, characterized in that the notification means notifies the second other communication device of the upper limit value during the period.
4. A communication device according to any one of claims 1 to 3, further comprising a receiving means for receiving a first frame indicating a request for transmission of the second PPDU from the second other communication device, and wherein the notifying means, upon receiving the first frame, notifies the second other communication device of the upper limit value using a second frame.
5. The communication device according to any one of claims 1 to 4, wherein the notification means notifies the upper limit value using a PPDU having a MAC (Media Access Control) header that includes the upper limit value in an A-Control field.
6. The communication device according to claim 1 or 2, wherein the notification means notifies the upper limit value before the period starts.
7. The communication device according to claim 1, 2 or 6, characterized in that the notification means notifies the upper limit value using a beacon frame, a probe response frame or an association response frame prior to the period in which the device has the transmission opportunity.
8. The communication device according to any one of claims 1 to 7, characterized in that the communication device is an access point device having an access point function, further comprising a construction means for constructing a network, and the first other communication device and the second other communication device are communication devices participating in the network.
9. The communication device according to any one of claims 1 to 8, wherein the second other communication device transmits the second PPDU by interrupt communication.
10. The communication device according to any one of claims 1 to 9, wherein the second PPDU is a PPDU including data categorized as low latency data.
11. A communication device according to any one of claims 1 to 10, characterized in that the upper limit value indicates a time during which the second other communication device is able to communicate within the period.
12. A communication device according to any one of claims 1 to 10, wherein the upper limit value indicates the number of PPDUs that the second other communication device can communicate during the period.
13. A communications device that performs communications in accordance with the IEEE 802.11 standard series, comprising: a first transmitting means for transmitting a first PPDU to an access point device having access point functionality during a period when another communications device has a transmission opportunity; and a receiving means for receiving a first frame that includes information indicating an upper limit of transmission opportunities for transmitting the first PPDU during the period.
14. The communication device according to claim 13, further comprising control means for controlling the transmission of said first PPDU during said period so that said upper limit value is not exceeded.
15. A communication device according to claim 13 or 14, further comprising second transmitting means for transmitting a second frame indicating a request for transmitting the first PPDU when transmitting the first PPDU during the period.
16. The communication device according to claim 15, wherein the first frame is a response frame to the second frame.
17. The communication device according to any one of claims 13 to 16, wherein the first frame is a beacon frame or an association response frame.
18. The communication device according to any one of claims 13 to 17, wherein the first PPDU is a PPDU including data categorized as low latency data.
19. A control method for a communication device that communicates in accordance with the IEEE 802.11 standard series, comprising: a communication step of communicating a first PPDU (Physical layer (PHY) Protocol Data Unit) with a first other communication device during a period in which the communication device has a transmission opportunity (TXOP) for transmitting the PPDU; and a notification step of notifying the second other communication device of an upper limit of the transmission opportunity for transmitting the second PPDU when the second other communication device transmits a second PPDU during the period.
20. A control method for a communication device that communicates in accordance with the IEEE 802.11 standard series, comprising: a communication step of communicating a first PPDU (Physical layer (PHY) Protocol Data Unit) with a first other communication device during a period in which the first other communication device has a transmission opportunity (TXOP) for transmitting the PPDU; and a notification step of notifying a second other communication device of an upper limit of the transmission opportunity for transmitting the second PPDU when the second other communication device transmits a second PPDU during the period.
21. A control method for a communication device that communicates in accordance with the IEEE 802.11 standard series, comprising: a first transmitting step of transmitting a first PPDU to an access point device having access point functionality during a period in which another communication device has acquired a transmission opportunity; and a receiving step of receiving a first frame including information indicating an upper limit of transmission opportunities for transmitting the first PPDU during the period.
22. A program for causing a computer to function as the control method for a communication device according to claim 18.
23. A program for causing a computer to function as the communication device control method according to claim 19.
24. A program for causing a computer to function as the communication device control method according to claim 20.
Citation Information
Patent Citations
Latency-sensitive traffic transmission
US20240163922A1
Preemption / interruption of an ongoing low priority ppdu
WO2023044263A1