Communication device, control method, and program

MYPI2025004522A0Undetermined Publication Date: 2024-07-30CANON KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
MYPI2025004522
Authority / Receiving Office
MY · MY
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-01-30
Filing Date
2023-12-28
Publication Date
2024-07-30

AI Technical Summary

Technical Problem

The existing IEEE 802.11 standards, including R-TWT, are inadequate for transmitting data that requires low latency outside of scheduled periods, necessitating a mechanism for preferential low-latency transmission.

Method used

A communication device capable of transmitting other data instead of scheduled data during radio frame transmission, using a Preemptible PPDU mechanism that includes information about data interruption in the preamble, allowing for interrupting and prioritizing low-latency data transmission.

Benefits of technology

Enables efficient and prioritized low-latency data transmission by interrupting scheduled data transmission and transmitting low-latency data during designated intervals, enhancing communication efficiency and meeting the demand for low-latency communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure PI2025004522_DRAWING_001
    Figure PI2025004522_DRAWING_001
  • Figure PI2025004522_DRAWING_002
    Figure PI2025004522_DRAWING_002
  • Figure PI2025004522_DRAWING_003
    Figure PI2025004522_DRAWING_003
Patent Text Reader

Abstract

A communication device capable of performing wireless communication based on an IEEE 802.11 standard transmits a wireless frame having a preamble of a physical layer (PHY) and a data field containing data. If a specific condition is satisfied while the communication device is transmitting first data using one or more wireless frames that include information related to data preemption in the preamble, the communication device interrupts transmission of the first data and preemptively transmits second data different from the first data. Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

Communication device, control method, and program

[0001] The present invention relates to a communication device that performs wireless communication.

[0002] The Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard is known as a communication standard for wireless local area networks (LANs). The IEEE 802.11be standard and its successor standards are designed to improve communication efficiency and throughput by cooperatively operating multiple access point devices (hereinafter simply referred to as APs).

[0003] Furthermore, Patent Document 1 discloses a technology called R-TWT (Restricted Target Wake Time) that provides a period that can be used for communication of data that requires low latency, and transmits the data that requires low latency during that period.

[0004] US Patent Application Publication No. 2022 / 0070772

[0005] The R-TWT technology described above can reduce latency when constantly occurring data is transmitted at scheduled intervals.

[0006] On the other hand, data requiring low latency may occur outside the scheduled period. In order to transmit such data with low latency, it is necessary to realize preferential low latency transmission using a technique other than R-TWT.

[0007] The present invention has been made in consideration of at least one of the above-mentioned problems, and an object of the present invention is to provide a mechanism for transmitting, during transmission of a radio frame communicating certain data, other data instead of the data in question.

[0008] One aspect of the present invention provides a communication device capable of wireless communication based on the IEEE 802.11 standard, and includes a transmitting means for transmitting a wireless frame having a physical layer (PHY) preamble and a data field in which data is stored after the preamble, wherein the transmitting means includes information related to data interruption in the preamble when the communication device is transmitting a wireless frame in which first data is stored in the data field, and when certain conditions are met, the transmitting means interrupts the transmission of the first data and interrupts and transmits second data different from the first data.

[0009] According to one aspect of the present invention, during transmission of a radio frame communicating certain data, it becomes possible to transmit other data instead of the data.

[0010] 1 is a diagram illustrating an example of a network configuration; FIG. 2 is a diagram illustrating a hardware configuration of a communication device; FIG. 3 is a diagram illustrating a software configuration of a communication device; FIG. 4 is a diagram illustrating an example of a wireless frame; FIG. 5 is a schematic diagram illustrating interrupt control in the first embodiment; FIG. 6 is an example of control executed by an AP in the first embodiment; FIG. 7 is an example of control executed by an STA in the first embodiment; FIG. 8 is a schematic diagram illustrating interrupt control in the second embodiment; FIG. 9 is an example of control executed by an AP in the second embodiment; FIG. 10 is an example of control executed by an STA in the second embodiment; FIG. 11 is a diagram illustrating a modified example of the second embodiment; FIG. 12 is a diagram illustrating a modified example of the second embodiment;

[0011] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims. Although multiple features are described in the embodiments, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined arbitrarily. Furthermore, in the accompanying drawings, the same reference numerals are used to designate the same or similar components, and redundant explanations will be omitted.

[0012] <First embodiment> <Configuration of communication system> Fig. 1 shows an example of the configuration of a wireless communication system according to the first embodiment. This wireless communication system includes one access point device (hereinafter simply referred to as an AP, AP STA, or access point) and two station devices (hereinafter simply referred to as STAs, Non-AP STAs, or stations). Hereinafter, AP 101 and STAs 102-103 will be collectively referred to as communication devices.

[0013] The AP 101 is configured to be able to communicate wireless frames that comply with the successor standard to the IEEE 802.11be standard, which targets a maximum transmission speed of 46.08 Gbps and is intended to achieve a maximum transmission speed of 90 Gbps to 100 Gbps or more. Similarly, the STAs 102 to 103 are configured to be able to communicate wireless frames that comply with the successor standard to the IEEE 802.11be standard.

[0014] IEEE stands for Institute of Electrical and Electronics Engineers. This successor standard to IEEE 802.11be features support for highly reliable communication and low latency communication, as well as AP cooperation as its main features. Based on the above, in this embodiment, the successor standard to IEEE 802.11be, which targets a maximum transmission speed of 90 Gbps to 100 Gbps or more, is also referred to as IEEE 802.11UHR (Ultra High Reliability). Furthermore, the wireless frame communicated under this successor standard is also referred to as UHR PPDU. PPDU stands for PLCP Protocol Data Unit, and PLCP stands for Physical Layer Convergence Protocol.

[0015] The names IEEE802.11UHR and UHR standards are given for convenience in consideration of the goals to be achieved by the successor standards and the key features of the standards, and may be named differently once the standards are fully established. However, please note that this specification and the appended claims are essentially successor standards to the IEEE802.11be standard and are applicable to all successor standards.

[0016] 1 shows a wireless communication network including one AP and two STAs as an example, but the number of these devices may be more or less than that shown. Furthermore, while AP 101 and STAs 102-103 are described as supporting UHR PPDU communication (transmission and reception), they may also be configured to support PPDU communication of legacy standards that predate the UHR standard. Specifically, AP 101 and STAs 102-103 may be configured to support PPDU transmission and reception of IEEE 802.11a / b / g / n / ac / ax / be standards, etc.

[0017] The AP 101 provides a network for the STAs. The STAs 102 to 103 are STAs that participate in the network provided by the AP 101. In the example shown in FIG. 1, the STAs 102 to 103 participate in the network provided by the AP 101.

[0018] The AP 101 and the STAs 102 and 103 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.

[0019] The AP 101 can also be configured to support wired communication using an Ethernet (registered trademark) cable or wired communication using optical fiber. In this embodiment, it is assumed that the AP 101 is connected to the Internet via an Ethernet cable. Specific examples of the AP 101 and the STAs 102-103 include, but are not limited to, a wireless LAN router and a personal computer (PC). The AP 101 and the STAs 102-103 may also be information processing devices such as wireless chips that support the transmission and reception of UHR PPDUs. Specific examples of the STAs 102-103 include, but are not limited to, a camera, a tablet, a smartphone, a PC, a mobile phone, a video camera, a projector, and wearable devices such as smart glasses.

[0020] Furthermore, each communication device such as the AP 101 and the STAs 102 to 103 can communicate using bandwidths of 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, 480 MHz, and 640 MHz.

[0021] Recently, the demand for low-latency communication has been increasing in wireless communication. For example, in the 802.11be standard, in order to meet the demand for low-latency communication, a function called R-TWT (Restricted Target Wake Time) has been established, which provides a period that can be used for communication that requires low latency. This R-TWT function can reduce the latency when regularly occurring data is transmitted within a scheduled period. On the other hand, data that requires low latency may also be generated outside the aforementioned scheduled period. In order to transmit such data with low latency, it is necessary to achieve preferential low-latency transmission using a technology different from R-TWT.

[0022] In this embodiment, in order to transmit data requiring low-latency communication that occurs irregularly with priority, a mechanism is provided that allows low-latency data to be transmitted instead of certain data during transmission of a wireless frame that communicates that data. A specific description will be given below.

[0023] 2 is a diagram showing an example of the hardware configuration of a communication device (AP and STA). As an example of the hardware configuration, the communication device has a storage unit 201, a control unit 202, a function unit 203, an input unit 204, an output unit 205, a communication unit 206, and an antenna 207. Note that, although this embodiment assumes that the communication device has multiple antennas, it may also have a single antenna.

[0024] The storage unit 201 is configured with ROM and / or RAM, and stores various information such as programs for performing various operations described below and communication parameters for wireless communication. RAM stands for Random Access Memory, and ROM stands for Read Only Memory. Note that the storage unit 201 may be a storage medium such as a non-volatile storage device, such as a hard disk or SSD (Solid State Drive), in addition to memories such as ROM and RAM.

[0025] The control unit 202 is configured by, for example, a processor 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 202 executes programs stored in the storage unit 201 and controls the entire device by operating hardware circuits such as the ASIC. Note that the control unit 202 may also control the entire device in cooperation with the programs stored in the storage unit 201 and an OS (Operating System).

[0026] The control unit 202 also controls the functional unit 203 to perform predetermined processes such as capturing images, printing, and projection. The functional unit 203 is hardware that enables the device to perform predetermined processes. For example, if the communication device is a camera such as a digital still camera or a smartphone equipped with a camera, the functional unit 203 is an imaging unit that captures images of the surroundings via a camera unit (not shown) included in the communication device. For example, if the communication device is a printer, the functional unit 203 is a printing unit that performs printing on a sheet such as paper based on print data obtained from the outside via wireless communication. For example, if the communication device is a projector or smart glasses, the functional unit 203 is a projection unit that performs projection of image data or video data obtained from the outside via wireless communication. In the case of smart glasses, the projection surface is the end user's retina, for example. The data processed by the functional unit 203 may be data stored in the storage unit 201 or data communicated with another AP or STA via the communication unit 206 (described later).

[0027] The input unit 204 receives various operations from the user. The output unit 205 outputs various types of information to the user. Here, the output by the output unit 205 includes, for example, at least one of displaying on a screen of a display, audio output by a speaker, vibration output, etc. Note that both the input unit 204 and the output unit 205 may be realized by a single module, such as a touch panel.

[0028] The communication unit 206 controls wireless communications compliant with the IEEE 802.11 series of standards and IP communications. In this embodiment, the communication unit 206 cooperates with the antenna 207 to transmit and receive UHR PPDUs, which are wireless frames of the UHR standard, and PPDUs conforming to earlier standards. The antenna 207 is an antenna capable of transmitting and receiving signals in at least one of the frequency bands, for example, the sub-GHz band, the 2.4 GHz band, the 5 GHz band, the 6 GHz band, the 7 GHz band, and the 60 GHz band.

[0029] If the communication device is compatible with the NFC standard, Bluetooth standard, or the like, the communication unit 206 may be configured to control wireless communication in accordance with these communication standards.

[0030] Next, the functional configuration of the communication device (AP 101 and STAs 102-103) will be described with reference to Fig. 3. Fig. 3 is a block diagram illustrating the functional configuration of the communication device.

[0031] The communication device includes a wireless LAN control unit 301 , a frame generation unit 302 , a frame processing unit 303 , a setting management unit 305 , and a UI control unit 304 .

[0032] Each function will be described below. Wireless LAN control unit 301 controls antenna 207 and communication unit 206 for transmitting and receiving wireless signals to and from other communication devices. Specifically, wireless LAN control unit 301 cooperates with frame generation unit 302 and frame processing unit 303 to execute communication control of wireless frames such as UHR PPDU in accordance with the IEEE 802.11 standard series.

[0033] The frame generation unit 302 controls the communication unit and antenna to generate a wireless frame to be transmitted based on instructions from the wireless LAN control unit 301. The wireless frame consists of a preamble field and a data field. The data field stores MAC (Medium Access Control) frames such as management frames, control frames, and data frames. The wireless LAN control unit 301 manages multiple transmission queues with priorities (not shown), and instructs the frame generation unit 302 to generate a wireless frame based on the data accumulation status in the multiple transmission queues, etc.

[0034] The wireless frame including the physical layer (PHY) preamble and data generated by the generation unit 302 is transmitted to the outside by the wireless LAN control unit 301, the communication unit 206, and the antenna 207. Furthermore, the data of the wireless frame received by the antenna 207, the communication unit 206, and the wireless LAN control unit 301 working together is passed to the frame processing unit 303. The frame processing unit 303 analyzes the data of the wireless frame and notifies a function of an upper layer (not shown), and performs control processing of wireless communication based on the information obtained by interpretation. For example, if data addressed to STA 102 is stored in a wireless frame received from the outside, the data is stored in one of the transmission queues described above based on the type of the data.

[0035] The setting management unit 305 manages communication parameters necessary for network construction and STA communication, such as the MCS used for communication with other communication devices, its own operating frequency band, BSSID, BSS Color, and information on the bandwidth for communicating PPDU. MCS stands for Modulation and coding scheme, and is information indicating the modulation and coding scheme applied to communication. It also stores operational settings such as whether to transmit a Preemptible PPDU, which will be described later.

[0036] The UI control unit 304 cooperates with the output unit 205 to provide an operation screen for the user, and cooperates with the input unit 204 to detect user operations such as changes to operation settings made on the operation screen and request a change to the operation settings from the setting management unit 305. The UI control unit 304 cooperates with the output unit 205 to provide the user with a change screen for changing the operation settings, such as whether to transmit a Preemptible PPDU. When the UI control unit 304 detects a user operation made on the change screen to change the operation settings, it requests the setting management unit 305 to change the operation settings. Upon receiving the request, the setting management unit 305 changes the stored operation settings.

[0037] Next, the UHR PPDU communicated by the communication device in this embodiment will be described with reference to Fig. 4. Fig. 4 shows an example of the format of a UHR MU (Multi User) PPDU transmitted by the communication device.

[0038] The UHR PPDU shown in Fig. 4 includes fields of STF (Short Training field), LTF (Long Training field), and SIG (Signal field). As shown in Fig. 4, the beginning of the PPDU includes fields 401 to 403 for ensuring backward compatibility with the IEEE 802.11a / b / g / n / ax standards. Specifically, the training fields include L-STF (Legacy Short Training field) 401 and L-LTF (Legacy Long Training field) 402. In addition, L-SIG (Legacy Signal field) 403 is included as a signal field.

[0039] Note that L-LTF is placed immediately after L-STF, and L-SIG is placed immediately after L-LTF. Furthermore, RL-SIG (Repeated L-SIG) is placed immediately after L-SIG. In the RL-SIG field, the contents of L-SIG are repeatedly transmitted. RL-SIG allows the receiver to recognize that the PPDU is compliant with the IEEE 802.11ax standard or later.

[0040] The L-STF is used for detecting PHY layer radio frame signals, automatic gain control (AGC), timing detection, etc. The L-LTF is used for highly accurate frequency and time synchronization, acquisition of propagation channel information (CSI), etc. The L-SIG is used to transmit control information including information on the data transmission rate and PHY frame length. A communication device receiving a radio frame can determine the timing at which transmission of the radio frame is completed using the information on the data transmission rate and PHY frame length. Devices conforming to the IEEE 802.11a / b / g / n / ax standards, the 802.11be standard, and its successor, the UHR standard, can decode the various legacy fields.

[0041] The PPDU further includes a U-SIG 405 (Universal Signal field) placed immediately after the RL-SIG. The U-SIG is a field for transmitting control information for each standard, which is planned to be used in common in standards from IEEE 802.11be onwards. The U-SIG includes a field called a PHY Version Identifier that stores a PHY version identifier, and a field called a BSS Color that stores a color code for BSS determination. In the case of a UHR MU PPDU, a value indicating a UHR MU PPDU (e.g., 1) is stored in the PHY Version Identifier field.

[0042] Immediately following the U-SIG is placed an Ultra High Reliability Signal field (UHR-SIG) 406. The UHR-SIG contains control information that cannot be contained in the U-SIG and control information that should be notified to each user when performing multi-user transmission.

[0043] Subsequently, UHR-SIG 406 is followed by UHR-STF 407, which is an STF for UHR, and UHR-LTF 408, which is an LTF for UHR. UHR-LTF is information used for MIMO estimation, beamforming estimation, etc. Multiple UHR-LTFs can be arranged based on the number of MIMO antennas and whether beamforming is required. A maximum of eight UHR-LTFs can be arranged.

[0044] After these control fields are placed a data field 409 and a PE (Packet extension field) 410. The fields from L-STF to UHR-LTF of the PPDU in Fig. 4 are called a PHY preamble.

[0045] The UHR-SIG 406 further includes a common field 406-1 and one or more user specific fields 406-2. Hereinafter, the user specific fields will also be simply referred to as user fields.

[0046] Common field 406-1 includes information exemplified in Table 1 for non-OFDMA and in Table 2 for OFDMA. OFDMA stands for Orthogonal Frequency Division Multiple Access. Subfields such as Preempt Enable and Preempt Timing in Table 1 and Table 2 are examples of fields that include information related to data interruption.

[0047]

[0048] Table 1 shows an example of a common field for non-OFDMA. In Table 1, Spatial Reuse is a subfield that indicates whether or not the Spatial Reuse mode is permitted for other communication devices during transmission of this PPDU. GI+LTF is a subfield that indicates the size of the guard interval and LTF.

[0049] The Number Of UHR-LTF Symbols is a subfield that stores a value indicating the number of symbols in the UHR-LTF training field. The LDPC Extra Symbol Segment is a subfield that stores information related to LDPC (Low Density Parity Check). The Pre-FEC Padding Factor is a subfield that stores information related to the forward error correction function. The PE Disambiguity and Disregard fields store information equivalent to the fields of the same name in the PHY preamble of the IEEE 802.11ax standard or IEEE 802.11be.

[0050] Next, Preempt Enable is a subfield that stores information indicating whether an interruption of low-latency communication may occur during the transmission of this PPDU. Storing 1 in this subfield means True, which indicates that an interruption may occur. Storing 1 in this subfield means False, which indicates that an interruption will not occur. Note that the combination of values ​​and corresponding information is not limited to this, and any information may be used as long as it can convey to the other device in the preamble of a wireless frame whether an interruption transmission of other data may occur during the transmission of the wireless frame. Hereinafter, a PPDU with Preempt Enable set to True is also referred to as a Preemptible PPDU.

[0051] The Preempt Timing subfield indicates the timing at which low-latency communication may occur during the transmission of this PPDU. In this embodiment, a value of n indicates that an interrupt may occur at intervals of n+1 milliseconds, but this is not limited to this. For example, the exponent, such as a predetermined number raised to the power of n, may be specified to specify the interrupt interval to the remote device. Note that if the Preempt Enable subfield indicates False, the Preempt Timing subfield is set to "0."

[0052] Finally, the Number of Non-OFDMA Users subfield stores information indicating the total number of users to which the MU transmission is directed. The following encoding blocks store information notifying each individual destination of the MU PPDU.

[0053] Next, the Common field 406-1 for OFDMA will be described using Table 2. The information stored in B0 to B18 is the same as the information stored in the case of non-OFDMA, so description will be omitted, but as in the case of non-OFDMA, information regarding low latency communication is stored in B14-B18. From B19 onwards, an RU Allocation-A subfield that stores information indicating the allocation status of resource units for OFDMA communication, as well as subfields representing CRC and Tail, are stored. The RU Allocation-A subfield stores allocation information for resource units for one 20 MHz subband or allocation information for resource units for two 20 MHz subbands, depending on the bandwidth.

[0054]

[0055] The names of the subfields and the positions and sizes of the bits that make up each subfield are not limited to those listed in Tables 1 and 2. Subfields with different names that can transmit similar information to a destination device may be used, and the positions and sizes of the subfields may be modified as appropriate. While this embodiment illustrates an example in which information about low latency communication is stored in Common field 406-1 of UHR-SIG 406, this is not limiting. For example, information about low latency communication may be stored in U-SIG 405.

[0056] Next, interrupt communication in this embodiment will be described with reference to Fig. 5. Fig. 5 is a schematic diagram for explaining interrupt communication in this embodiment.

[0057] AP 101 transmits a Preemptible PPDU indicated by 501 to subordinate STAs such as STA 102 and STA 103. Fig. 5 illustrates an example in which data addressed to STA 102 is being transmitted. If data to be transmitted using low latency communication is not stored in AP 101's transmission queue during transmission of the Preemptible PPDU indicated by 501, AP 101 completes transmission of the Preemptible PPDU without performing interrupt processing. Hereinafter, data to be transmitted using low latency communication will also be referred to as low latency data.

[0058] On the other hand, if low latency data is stored in the transmission queue of the AP 101 during transmission of the Preemptible PPDU indicated by 501, an interrupt transmission process indicated by 502 is executed.

[0059] Specifically, when low-latency data is stored in the transmission queue of AP 101, AP 101 transmits a signal consisting of a special bit string called a PPDU Endmarker, which notifies the communication partner of the occurrence of an interruption. Subsequently, after completion of transmission of this signal, and in response to the lapse of a Short Interframe Space (SIFS) time, AP 101 transmits a PPDU containing the low-latency data to the transmission destination of the low-latency communication. Here, a case is illustrated in which a PPDU containing low-latency data is transmitted to STA 103. Upon completion of transmission of the PPDU containing the low-latency data, AP 101 transmits a PPDU for transmitting the remaining data that was interrupted as necessary. Here, a case is illustrated in which a PPDU for transmitting the remaining data is transmitted to STA 102. It should be noted that whether or not the remaining data is transmitted is optional. For example, if data with a higher priority than the remaining data is stored in the transmission queue, the transmission of the higher-priority data can be prioritized.

[0060] Specific control will be described using Figures 6 and 7. Figure 6 is a flowchart illustrating PPDU transmission control performed by AP 101, which is a communication device, and Figure 7 is a flowchart illustrating Preemptible PPDU reception control performed by STAs 102 and 103, which are communication devices. The flowcharts of Figures 6 and 7 excerpt a series of procedures for realizing interrupt control using a Preemptible PPDU. Each process shown in the flowchart of Figure 6 is executed by the processor of control unit 202 of AP 101 executing a computer program stored in storage unit 201. Each process shown in the flowchart of Figure 7 is executed by the processor of control unit 202 of STA 102 or STA 103 executing a computer program stored in storage unit 201. 6 and 7, some of the processes such as transmission, modulation, reception, and decoding are realized by the processor of the control unit 202 of each communication device in cooperation with the communication unit 206, the ASIC, DSP, FPGA, etc. of the control unit 202. When it is desired to clearly indicate the subject of processing, the functional unit described in FIG. 3 will be used as the subject.

[0061] First, PPDU transmission control on the AP 101 side will be described using Fig. 6. The processes shown in the flowchart of Fig. 6 represent processes executed when data to be transmitted is stored in a transmission queue managed by the control unit 301 of the AP 101 and the data is transmitted to an external device. In other words, the processes shown in the flowchart of Fig. 6 represent processes executed when the AP 101 determines that it can acquire a transmission opportunity (TXOP) based on contention control based on EDCA and transmits a PPDU. EDCA stands for Enhanced Distributed Channel Access.

[0062] In S601, the control unit 301 determines whether a low-latency communication interrupt is likely to occur. If it is determined that a low-latency communication interrupt is likely to occur, the process proceeds to S604. If it is determined that a low-latency communication interrupt is not likely to occur, the process proceeds to S602. This determination can be made based on the priority of data communicated with each STA over a certain period of time. For example, the AP 101 determines that an interrupt is likely to occur if it has communicated IP packets over a certain period of time in which the DSCP value included in the DS field of the IP packet is set to a value indicating Expedite Forwarding. DSCP stands for Differentiated Services Code Point. Furthermore, if the data to be transmitted is transmission data (low-latency data) with a high priority for low-latency communication, the control unit 301 determines that a low-latency communication interrupt is unlikely to occur. This determination process prohibits interrupt transmission if the data to be transmitted is low-latency data. In other words, AP 101 stores data with a lower priority than low-latency data in the Preemptible PPDU. Furthermore, in cooperation with the setting management unit 305, the control unit 301 determines that a low-latency communication interrupt is unlikely to occur even if it determines that the communication device's operational settings indicate that Preemptible PPDU transmission is not to be performed.

[0063] The first three bits of the DS field may be regarded as an IP precedence value, and an interrupt may be determined to be likely if an IP packet with a value of "5" indicating Critical has been communicated within a certain period of time. The determination method is not limited to this. A specific terminal may be pre-registered in the AP as a terminal with the highest priority in AP 101's communications, and an interrupt may be determined to be likely if the specific terminal is participating in AP 101's network. Alternatively, time-series data of past communications over a certain period of time may be input to estimate the probability that low-latency data will be generated, and a determination may be made as to whether an interrupt is likely to occur based on the estimated probability. For example, by inputting past communication data into trained model data that has been trained using a known machine learning algorithm such as supervised learning or deep learning, an inference result indicating the probability that low-latency data will be generated can be obtained.

[0064] Next, in S602, the control unit 301, in cooperation with the frame generation unit 302, sets the Preempt Enable subfield of the PHY preamble to False. At this time, the Preempt Timing subfield is set to 0. Next, the control unit 301, in cooperation with the frame generation unit 302, sets information based on transmission parameters and the like in the other preamble fields as appropriate, and generates a UHR MU PPDU including data to be transmitted in the data field.

[0065] In S603, the control unit 301 transmits the UHR MU PPDU generated in S602, and ends a series of transmission processes.

[0066] Next, a case where it is determined that an interruption of low latency communication is likely to occur will be described. In S604, the control unit 301, in cooperation with the frame generation unit 302, sets True to the Preempt Enable subfield of the PHY preamble and sets a predetermined value to the reempt Timing subfield. Next, in cooperation with the frame generation unit 302, the control unit 301 sets appropriate values ​​based on transmission parameters and the like to other preamble fields and generates a Preemptible PPDU including data to be transmitted in the data field.

[0067] In S605, the control unit 301 cooperates with the communication unit 206 and the antenna 207 to start transmitting the generated Preemptible PPDU. Subsequently, in S606, the control unit 301 determines whether an interrupt transmission of low-latency data is required. If it is determined that an interrupt transmission of low-latency data is required, the process proceeds to S608. If it is determined that an interrupt transmission of low-latency data is not required, the process proceeds to S607. Specifically, the control unit 301 determines that an interrupt transmission of low-latency data is required when transmission data corresponding to an IP packet whose DSCP value is set to a value indicating Expedited Forwarding is stored in the transmission queue. It is also possible to regard the first three bits of the DS field as an IP Precedence value and determine that an interrupt transmission is required when transmission data corresponding to an IP packet whose value indicates Critical is stored in the transmission queue.

[0068] In this embodiment, the case where low latency data is determined based on QoS (Quality of Service) information in the IP packet is illustrated, but the present invention is not limited to this. For example, it may be determined that interrupt transmission is necessary even when transmission data corresponding to a STA pre-registered in the AP as a top priority terminal is stored in a transmission queue. The process of determining that interrupt transmission of the low latency data is necessary is an example of a process of determining that a specific condition is met.

[0069] In S607, the control unit 301 determines whether the transmission process of the Preemptible PPDU has been completed. If it is determined that the transmission process of the Preemptible PPDU has been completed, the control unit 301 ends the series of transmission control steps. On the other hand, if it is not determined that the transmission process of the Preemptible PPDU has been completed (i.e., if it is determined that the Preemptible PPDU is currently being transmitted), the control unit 301 proceeds to S605 and continues the transmission process of the Preemptible PPDU.

[0070] Finally, the interrupt control of low latency data will be described. In S608, the control unit 301 continues transmitting the data field until the time corresponding to the Preempt Timing set in the PHY preamble of the Preemptible PPDU arrives. Then, when the time corresponding to the Preempt Timing arrives, the control unit 301 proceeds to S609.

[0071] In S609, the control unit 301 transmits data consisting of a special bit string as a PPDU Endmarker to notify the communication partner of the occurrence of the interruption, and interrupts the transmission process of the Preemptible PPDU.

[0072] At S610, the control unit 301 waits for the SIFS time before transmitting. At S6111, the control unit 301 transmits a PPDU storing low latency data generated in cooperation with the frame generation unit 302 to the STA that is the destination of the low latency data. As described above, the destination of the low latency data may be a different destination from the destination of the Preemptible PPDU transmitted at S605. Note that the PPDU generation process is performed in parallel while the AP 101 waits for the SIFS time. Also, it is assumed that False is set to the Preempt Enable subfield of the preamble of the PPDU transmitted at S610. Upon completing transmission of the PPDU storing the low latency data, the AP 101 proceeds to S612.

[0073] In S612, the control unit 301 determines whether to resume the interrupted data transmission. If it determines to resume the interrupted data transmission, the process proceeds to S613. If it determines not to resume the interrupted data transmission, the process ends. For example, the control unit 301 determines whether to resume the interrupted data transmission based on the priority of the interrupted data included in the Preemptible PPDU, the remaining TXOP, etc. More specifically, if the priority of the data newly stored in the transmission queue is higher than the priority of the interrupted data or if the remaining TXOP period is short, the control unit 301 may determine not to resume the interrupted data transmission. If it determines not to resume, the interrupted remaining data is returned to the transmission queue and retransmitted appropriately when the AP 101 secures a next or subsequent transmission opportunity.

[0074] In S613, the control unit 301 waits for the SIFS time before transmitting. In S614, the control unit 301, in cooperation with the frame generation unit 302, regenerates a Preemptible PPDU that stores data so that it fits within the remaining TXOP, and starts (resumes) the transmission of the remaining data that was interrupted in S609. The control unit 301 may regenerate a Preemptible PPDU that includes only a portion of the remaining data, or may regenerate a Preemptible PPDU that includes all of the remaining data by increasing the MCS in the data field. Note that the PPDU regeneration process is performed in parallel while the AP 101 is waiting for the SIFS time.

[0075] When the transmission process is resumed, the control unit 301 advances the process to S606 and attempts to transmit a Preemptible PPDU or perform interrupt control for other low latency data.

[0076] By the above-described process, when low latency data is stored in the transmission queue, it becomes possible to suspend the transmission of other data and transmit the low latency data preferentially.

[0077] Next, PPDU reception control in the communication devices STA102 and STA103 will be described with reference to Fig. 7. Each process shown in the flowchart in Fig. 7 indicates a process executed when STA102 or STA103 receives a Preemptible PPDU addressed to itself.

[0078] In S701, the control unit 301 cooperates with the frame processing unit 303 to perform reception processing of the Preemptible PPDU. Specifically, the reception processing includes signal demodulation processing and data decoding processing. In S702, the control unit 301 references the Preempt Timing value set in the preamble of the Preemptible PPDU. Based on the referenced Preempt Timing value and the time elapsed since the start of reception of the Preemptible PPDU, the control unit 301 determines whether a preemption can occur. If it is determined that a preemption can occur, the process proceeds to S703. If it is determined that a preemption cannot occur, the process proceeds to S704.

[0079] In S703, the control unit 301 determines whether a PPDU Endmarker has been received in cooperation with the frame processing unit 303. If it is determined that a PPDU Endmarker has been received, the process proceeds to S705. On the other hand, if it is determined that a PPDU Endmarker has not been received, the data decoded by the reception process is treated as data to be received, and the process proceeds to S701 to continue the PPDU reception process.

[0080] In S704, the control unit 301 determines whether or not all Preemptible PPDUs have been received in cooperation with the frame processing unit 303. If the control unit 301 determines that all Preemptible PPDUs have been received, the process proceeds to S705. If the control unit 301 determines that all Preemptible PPDUs have been received, the process proceeds to S701.

[0081] In S705, the control unit 301 executes processing to complete reception of the PPDU. Note that if the determination in S703 is Yes, the control unit 301 suspends the reception processing of the Preemptible PPDU and then executes the processing to complete reception. When the processing to complete reception is executed, the STA, such as STA 102 or STA 103, that has completed reception of the PPDU transitions to a state in which it can control data transmission based on EDCA.

[0082] Note that when the STA receives a PPDU that is not a Preemptible PPDU, i.e., a PPDU with the Preempt Enable subfield set to False and addressed to itself, the STA can receive and decode the PPDU. Therefore, a PPDU with the Preempt Enable subfield set to False transmitted from the AP 101 in S603 or S611 is properly received using a known reception procedure that is well known in the IEEE 802.11 standard series.

[0083] As described above, a communication device such as STA 102 or 103 that receives a Preemptible PPDU detects a PPDU Endmarker and thereby understands that the transmission process of the Preemptible PPDU will be interrupted. Then, by performing control to stop the reception process in response to this detection, it becomes possible to appropriately terminate the reception process of the Preemptible PPDU midway.

[0084] Furthermore, after suspending the transmission process of the Preemptible PPDU, the AP 101 can transmit a completely different PPDU storing low-latency data to another destination, thereby realizing interrupt transmission of low-latency data.

[0085] Second Embodiment In the first embodiment, a method for realizing an interruption by interrupting the transmission of a Preemptible PPDU and transmitting another PPDU containing low latency data was described. In the second embodiment, a mechanism for transmitting low latency data during the transmission of one Preemptible PPDU is provided. Note that the hardware and software configurations of the communication device are the same as those in the first embodiment, and therefore description thereof will be omitted.

[0086] The control mechanism of the second embodiment will be described using the schematic diagram of Fig. 8. In the second embodiment, as shown in 801 of Fig. 8, a Preemptible PPDU is transmitted in which the data field is configured in the A-MPDU format in which multiple MPDUs are aggregated. MPDU is an abbreviation for MAC Protocol Data Unit, and is a MAC frame including a MAC header and a payload. Furthermore, A-MPDU is an abbreviation for Aggregation-MAC Protocol Data Unit.

[0087] If low-latency data is stored in the transmission queue during transmission of a Preemptible PPDU in the A-MPDU format, an interrupt is performed by switching the MPDU to be transmitted to an MPDU corresponding to the low-latency data. Reference numeral 802 shows a Preemptible PPDU transmitted when interrupt control is performed. FIG. 8 illustrates an example in which three MPDUs addressed to STA 102 are transmitted, followed by an MPDU addressed to STA 103 containing low-latency data. The remaining three MPDUs addressed to STA 102 are then transmitted during the remaining TXOP, and padding data is transmitted during the remaining fractional time. When AP 101 performs an interrupt transmission as illustrated in reference numeral 802, it transmits data corresponding to the three MPDUs, which are the remaining data prepared but not transmitted to STA 102, at the next or subsequent transmission opportunity.

[0088] Specific control will be described using Figures 9 and 10. Figure 9 is a flowchart illustrating PPDU transmission control performed by AP 101, which is a communication device, and Figure 10 is a flowchart illustrating PPDU reception control performed by STAs 102 and 103, which are communication devices. The flowcharts of Figures 9 and 10 excerpt a series of procedures for realizing interrupt control using a Preemptible PPDU. Each process shown in the flowchart of Figure 6 is executed by the processor of control unit 202 of AP 101 executing a computer program stored in storage unit 201. Each process shown in the flowchart of Figure 10 is executed by the processor of control unit 202 of STA 102 or STA 103 executing a computer program stored in storage unit 201. 9 and 10 are realized by the processor of the control unit 202 of each communication device in cooperation with the communication unit 206, the ASIC of the control unit 202, the DSP, the FPGA, etc. When it is desired to clearly indicate the subject of processing, the functional unit described in FIG.

[0089] First, the PPDU transmission control on the AP 101 side will be described with reference to Fig. 9. Fig. 9 shows transmission control executed in place of the flowchart of Fig. 6 of the first embodiment. Due to space limitations, the description will focus on the differences from the first embodiment, while omitting descriptions of the same controls as in the first embodiment as appropriate.

[0090] The determination process of S901 and the non-preemptible PPDU transmission process of S902 to S903 are similar to the determination process of S601 and the non-preemptible PPDU transmission process of S601 to S603 in the first embodiment, and therefore description thereof will be omitted.

[0091] At S934, the control unit 301 sets True to the Preempt Enable subfield. While a predetermined value was set in the Preempt Timing subfield in the first embodiment, this embodiment differs in that a predetermined value is not set in the Preempt Timing subfield. Note that when interrupt control is performed using the mechanism described in the second embodiment, the UHR MU PPDU may be configured so that the Preempt Timing subfield is not included in the preamble.

[0092] In S935, the control unit 301 generates a Preemptible PPDU in the A-MPDU format, the data portion of which is composed of multiple MPDUs, in cooperation with the frame generation unit 302. In this embodiment, it is assumed that the Preemptible PPDU in the A-MPDU format generated in this process is an A-MPDU addressed to a single STA (e.g., STA 102), such as that shown in 801 in FIG.

[0093] Subsequently, in S935, the control unit 301 cooperates with the communication unit 206 and the antenna 207 to transmit a Preemptible PPDU storing data in the A-MPDU format.

[0094] Next, in S906, the control unit 301 performs interrupt determination processing similar to the processing described in S606. If it is determined that an interrupt is not necessary, the process proceeds to S907. In S907, the control unit 301 determines whether transmission of the Preemptible PPDU has been completed, similar to S607. If it is determined that transmission of the Preemptible PPDU has not been completed, the control unit 301 continues the transmission processing of the Preemptible PPDU, and if it is determined that transmission has been completed, the process ends.

[0095] Next, the interrupt transmission process will be described. In S938, the control unit 301 suspends the transmission of data up to the end of the MPDU being transmitted. When the transmission of data up to the end of the MPDU is completed, the process proceeds to S939.

[0096] In S939, the control unit 301 cooperates with the frame generation unit 302 to generate an MPDU containing low-latency data, replaces the data with the data to be transmitted, and continues transmitting the PPDU. Note that if the low-latency data is data addressed to a STA (e.g., STA 103) different from the destination of the A-MPDU (e.g., STA 102) indicated in 801, the destination of the MAC header of the MPDU is specified as the different destination (e.g., STA 103). When transmission of the MPDU containing the low-latency data is complete, the control unit 301 proceeds to S912. In S912, similar to S612, the control unit 301 determines whether to resume the interrupted data transmission. If it is determined not to resume, the series of transmission processes is completed; if it is determined to resume, the control unit 301 proceeds to S934.

[0097] In S944, the control unit 301 reconstructs the remaining data to be transmitted so that it fits within the remaining TXOP. The control unit 301 then proceeds to S935 and continues the transmission process of the MPDU containing the reconstructed data to be transmitted. For example, as illustrated in 802, the control unit 301 resumes transmission of MPDUs that were originally scheduled to be transmitted so that they fit within the remaining TXOP. Furthermore, the AP 101 transmits padding data as necessary. By performing this process in S944, after the interrupt transmission is completed, it is possible to resume transmission of data to the originally scheduled destination (e.g., STA 102).

[0098] Next, PPDU reception control in the communication devices STA102 and STA103 will be described with reference to Fig. 10. Each process shown in the flowchart in Fig. 10 indicates a process executed when STA102 or STA103 detects that a PPDU is being transmitted by another communication device.

[0099] In S1001, the control unit 301, in cooperation with the antenna 207, the communication unit 206, and the frame processing unit 303, performs a reception process for a PPDU transmitted by another communication device. In S1002, the control unit 301 determines whether the received PPDU is a Preemptible PPDU addressed to the BSS to which the STA belongs. If it is determined that the received PPDU is a Preemptible PPDU addressed to the BSS to which the STA belongs, the process proceeds to S1003. On the other hand, if it is not determined that the received PPDU is a Preemptible PPDU addressed to the BSS to which the STA belongs, the process proceeds to S1005. The determination of whether the PPDU is addressed to the BSS to which the STA belongs can be realized by comparing the value of the BSS Color field included in the U-SIG, which is the preamble of the PPDU, with the value of the BSS Color of the BSS to which the STA belongs, which is managed by the STA. If the value of the BSS Color field matches the BSS Color value of the BSS managed by the STA to which the STA belongs, the control unit 301 determines that the PPDU is addressed to the BSS to which the STA belongs. On the other hand, if the value of the BSS Color field does not match the BSS Color value of the BSS managed by the STA to which the STA belongs, the control unit 301 determines that the PPDU is not addressed to the BSS to which the STA belongs. Furthermore, whether or not the PPDU is a Preemptible PPDU is determined by whether or not True is set in the Preempt Enable subfield included in the PPDU preamble. If True is set in the Preempt Enable subfield, the control unit 301 determines that the PPDU is a Preemptible PPDU. In addition, the control unit 301 determines that the PPDU is not a Preemptible PPDU if the Preempt Enable subfield is set to False. Furthermore, the control unit 301 also determines that the received PPDU is not a Preemptible PPDU if it is an EHT PPDU, HE PPDU, VHT PPDU, or the like that does not include a Preempt Enable subfield.

[0100] If the control unit 301 determines in the above-mentioned determination process that the received PPDU is addressed to the BSS to which the control unit 301 belongs and that the received PPDU is a Preemptible PPDU, the control unit 301 determines that the received PPDU is a Preemptible PPDU addressed to the BSS to which the control unit 301 belongs. Furthermore, if the control unit 301 determines in the above-mentioned determination process that the received PPDU is not addressed to the BSS to which the control unit 301 belongs and / or that the received PPDU is not a Preemptible PPDU, the control unit 301 determines that the received PPDU is not a Preemptible PPDU addressed to the BSS to which the control unit 301 belongs. The process of analyzing the preamble described in S1002 to determine whether the received PPDU is a Preemptible PPDU addressed to the BSS to which the control unit 301 belongs may be configured to be implemented by a hardware circuit such as an ASIC or DSP included in the communication unit 206.

[0101] Next, in S1003, the control unit 301 cooperates with the frame processing unit 303 to wait for an MPDU addressed to the control unit 301 and decode the MPDU addressed to the control unit 301 to receive data addressed to the control unit 301. The frame processing unit 303 also performs control to read and discard MPDUs addressed to other devices without performing decoding processing. The determination of whether an MPDU is addressed to the control unit 301 can be realized by comparing the destination address included in the MAC header of the MPDU with the control unit's own address.

[0102] In S1004, the control unit 301 determines whether all Preemptible PPDUs have been received. If it is determined that all Preemptible PPDUs have been received, the control unit 301 ends the series of reception processes. If it is determined that all Preemptible PPDUs have not been received, the control unit 301 continues the reception process of Preemptible PPDUs.

[0103] By the processes of S1003 and S1004, while a Preemptible PPDU addressed to the BSS to which the STA belongs is being transmitted by another communication device, the STA continues to perform a reception process for interpreting the data field of the Preemptible PPDU. Therefore, an STA expecting an interrupt transmission can also appropriately interpret the Preemptible PPDU and appropriately receive an MPDU containing low-latency data transmitted to the STA itself.

[0104] On the other hand, in S1005, the control unit 301 determines whether the received PPDU is a PPDU addressed to itself. If it is determined that the received PPDU is a PPDU addressed to itself, the process proceeds to S1006. If it is determined that the received PPDU is not a PPDU addressed to itself, the process proceeds to S1007. This determination may be realized by comparing its own STAID with the value stored in the STAID subfield of the User Specific field of the UHR-SIG, which is the preamble of the UHR MU PPDU.

[0105] In S1006, the control unit 301 cooperates with the processing unit 303 to decode the data included in the PPDU, thereby obtaining the data addressed to itself.

[0106] Meanwhile, in S1007, the control unit 301 sets a NAV (Network Allocation Vector) based on the data transmission rate and PHY frame length included in the preamble of the PPDU received in S1011. Then, during the period in which the NAV is set, the control unit 301 transitions to a Doze state in which power saving is achieved by partially or completely stopping the power supply to the communication unit 206 and the antenna 207, and the series of reception processes ends.

[0107] In addition, the STA that has transitioned to the Doze state resumes power supply to the communication unit 206 and antenna 207 after the period for which the NAV was set has elapsed, and transitions to the Awake state in which it can receive data and perform data transmission processing.

[0108] Through the series of processes described above, when the STA 102, STA 103, etc. detects a Preemptible PPDU addressed to the BSS to which it belongs, it becomes possible to control the STA 102, STA 103, etc. to wait for and interpret an MPDU addressed to itself.

[0109] In the first embodiment, a Preemptible PPDU preamble includes a Preempt Timing subfield, and a predetermined value is set in the subfield. However, the subfield may be omitted. In this case, the communication devices such as the STAs 102 and 103 may be configured to constantly monitor whether the data to be decoded includes a specific bit sequence corresponding to the PPDU Endmarker, and to detect the specific bit sequence corresponding to the PPDU Endmarker.

[0110] Furthermore, in the second embodiment, when a Preemptible PPDU addressed to the BSS to which the STA belongs is detected, each STA belonging to the BSS is controlled to wait for an MPDU addressed to the STA in an Awake state, but this is not limited to this. For example, modifications can be made to further limit the range of STAs that are targets for waiting for reception. Modifications will be described using Figures 11A to 11C. Figure 11A illustrates a modification of the UHR-SIG transmitted by AP 101. Also, Figure 11B is a schematic diagram illustrating a communication situation when MU DL OFDMA communication is performed and no interrupt transmission occurs. Finally, Figure 11C is a schematic diagram illustrating a communication situation when an interrupt transmission to destination 4 is performed using communication resources used for data transmission to destination 2.

[0111] When transmitting a UHR MU PPDU capable of interrupt transmission, the AP 101 also lists STAs for which low-latency communication may occur in the User Specific field. In this case, the AP 101 first lists user fields 1101-1 and 1101-2 addressed to the STAs that are the primary destinations for data communication. Here, an example is shown in which a UHR MU PPDU is used for downlink DL MU OFDMA transmission to two STAs. Next, the AP 101 lists user fields 1102-1 and 1102-2 corresponding to STAs for which low-latency communication may occur. Here, the number of STAs for which low-latency communication may occur is limited to a number that does not exceed the number of primary destinations (two destinations in the case of Figures 11A to 11C).

[0112] A case where no interrupt transmission occurs will be described using Figure 11B. In this case, the STA of destination 1 refers to the RU Allocation-A subfield and monitors "RU #1", which is the resource unit (hereinafter referred to as RU) allocated to the first STA. Then, the STA of destination 1 waits for the MPDU addressed to itself transmitted in "RU #1" and decodes it appropriately.

[0113] In this case, the STA with destination 2 refers to the RU Allocation-A subfield, monitors "#RU2", the RU allocated to the second STA, and waits for and decodes the MPDU addressed to itself that is transmitted in that RU as appropriate.

[0114] At this time, the STA corresponding to destination 3 also refers to the RU Allocation-A subfield and waits for an MPDU of interrupt data addressed to itself in "RU#1" assigned to the first STA. Also, at this time, the STA corresponding to destination 4 monitors "RU#2" assigned to the second STA and waits for an MPDU of interrupt data.

[0115] When low latency data for destination 3 or destination 4 is stored in the transmission queue, AP 101 replaces the data to be transmitted in the corresponding RU with an MPDU in which the low latency data is stored.

[0116] 11C illustrates an example of interrupt transmission when low-latency data for destination 4 is stored in the transmission queue. In this case, AP 101 suspends the transmission of an MPDU addressed to destination 2 at "#RU2," which is monitored by both destinations 2 and 4, at the timing indicated by 1104. Then, AP 101 transmits an MPDU addressed to destination 4, storing low-latency data, using "#RU2." The STA corresponding to destination 4 is monitoring RU#2 as described above. Therefore, it can properly receive the MPDU addressed to its own device that was interrupt-transmitted and decode the data. AP 101 also resumes the transmission of the remaining data to destination 2 as appropriate at the timing indicated by 1105, when the MPDU transmission to destination 4 is completed.

[0117] According to the modification described above, by further restricting the range of STAs waiting for low latency data, it is possible to perform interrupt transmission while suppressing an increase in standby power generated in the entire BSS. Furthermore, according to this modification, it is possible to appropriately realize interrupt transmission even in cases where data is being transmitted simultaneously to two or more devices using MU DL OFDMA.

[0118] The present invention can also be realized by a process in which a program that realizes one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a 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.

[0119] The invention is not limited to the above-described embodiments, and various changes and modifications can be made without departing from the spirit and scope of the invention. Accordingly, the following claims are appended to apprise the public of the scope of the invention.

[0120] 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, the following claims are appended to apprise the public of the scope of the present invention.

[0121] This application claims priority based on Japanese Patent Application No. 2023-012278, filed on January 30, 2023, the entire contents of which are incorporated herein by reference.

[0122] 101 AP 102 STA 103 STA 202 Control unit 206 Communication unit

Claims

1. A communications device capable of wireless communications based on the IEEE 802.11 standard, comprising a transmission means for transmitting a wireless frame having a physical layer (PHY) preamble followed by a data field in which data is stored, wherein the transmission means includes information related to data interruption in the preamble when the communications device is transmitting a wireless frame in which first data is stored in the data field, and when a specific condition is satisfied, interrupts the transmission of the first data and interrupts and transmits second data different from the first data.

2. The communication device according to claim 1, wherein the preamble includes an L-STF (Legacy Short Training field), an L-LTF (Legacy Long Training field), an L-SIG (Legacy Signal field), an RL-SIG (Repeated L-SIG), a U-SIG (Universal Signal field), an UHR-STF (Ultra High Reliability Short Training field), and an UHR-LTF (Ultra High Reliability Long Training field).

3. The communication device of claim 2, wherein the U-SIG of the preamble includes a subfield indicating whether or not there is a possibility that the data will be interrupted, and the information related to the data interruption is information indicating that there is a possibility that the data will be interrupted, and when the communication device determines that there is a possibility that the data will be interrupted, it stores information indicating that there is a possibility that the data will be interrupted in the subfield.

4. The communication device according to claim 2, characterized in that the wireless frame is a UHR MU PPDU including a UHR-SIG (Ultra High Reliability Signal field) between the U-SIG of the preamble and the UHR-STF, the UHR-SIG includes a common field and one or more user fields, the information related to the data interruption is information indicating that the data interruption may occur, and when the communication device determines that there is a possibility of a data interruption, it stores information indicating that the data interruption may occur in the common field.

5. A communication device as claimed in any one of claims 1 to 4, wherein the preamble of a radio frame containing information relating to the interruption of data transmitted by the transmitting means further contains second information indicating a timing at which the data may be interrupted.

6. A communication device according to any one of claims 1 to 5, further comprising a resuming means for resuming transmission of the remaining data incomplete among the first data whose transmission was interrupted after the second data has been transmitted by interrupt transmission.

7. A communication device as claimed in any one of claims 1 to 6, characterized in that, when interrupting transmission of the first data, the transmitting means notifies a recipient of the wireless frame via the wireless frame of information indicating that transmission is to be interrupted, and, after interrupting transmission of the first data, transmits a second wireless frame including a preamble and a data field in which the second data is stored, the second wireless frame being addressed to a destination different from that of the wireless frame.

8. A communication device as described in any one of claims 1 to 7, characterized in that the second data is data that should be communicated using low latency communication, the first data is data that has a lower transmission priority than the second data, and the transmitting means, when transmitting a wireless frame storing the first data, if the second data is stored in a transmission queue, interrupts the transmission of the first data and interrupts and transmits second data different from the first data.

9. A communication device capable of wireless communication based on the IEEE 802.11 standard, comprising: a receiving means for receiving a wireless frame including a physical layer (PHY) preamble including information related to data interruption and a data field in which first data is stored following the preamble; and a halting means for halting the reception process of the wireless frame when the receiving means receives information indicating that the transmission of the wireless frame is to be interrupted before the reception of the first data of the wireless frame is completed during the reception process.

10. A control method for a communication device capable of wireless communication based on the IEEE 802.11 standard, comprising a transmission control step of transmitting a wireless frame having a physical layer (PHY) preamble and a data field in which data is stored after the preamble, wherein in the transmission control step, the communication device includes information related to data interruption in the preamble, and when a wireless frame in which first data is stored in the data field is being transmitted, if a specific condition is satisfied, the transmission of the first data is interrupted and second data different from the first data is transmitted instead.

11. A control method for a communication device capable of wireless communication based on the IEEE 802.11 standard, comprising: a receiving step of receiving a wireless frame including a physical layer (PHY) preamble including information related to a data interruption and a data field in which first data is stored, after the preamble; and an abort step of aborting the reception process of the wireless frame when information indicating that the transmission of the wireless frame is to be interrupted is received before the reception of the first data of the wireless frame is completed by the reception process in the receiving step.

12. A program for causing a computer to function as a communication device according to any one of claims 1 to 9.