Communication method and communication apparatus

By optimizing the backoff time information and coordinating backoff behavior of devices in the FTTR system, the air interface collision problem when devices send data frames is solved, thereby reducing data transmission latency and achieving efficient operation of the communication system.

WO2026092059A1PCT designated stage Publication Date: 2026-05-07HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
HUAWEI TECH CO LTD
Filing Date
2025-10-09
Publication Date
2026-05-07

AI Technical Summary

Technical Problem

In a Fiber to the Room (FTTR) system, air interface collisions may occur when the device transmits data frames, leading to increased data transmission latency.

Method used

By receiving and adjusting the backoff time information of the devices, the probability of data conflicts between devices is reduced. Communication methods and devices are used to optimize the backoff process, including adjusting the backoff duration and sending corresponding information to coordinate the backoff behavior of the devices.

Benefits of technology

It effectively reduces the probability of collisions when devices send data, lowers data transmission latency, and improves the efficiency of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025126535_07052026_PF_FP_ABST
    Figure CN2025126535_07052026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a communication method and a communication apparatus, which can be applied to WLAN systems supporting next-generation Wi-Fi protocols of IEEE 802.11ax, such as 802.11be, i.e., Wi-Fi 7 or EHT, or 802.11 series protocols such as Wi-Fi 8, i.e., the next generation of 802.11be, and which can also be applied to FTTR systems. The method comprises: receiving first information of each of at least one device, wherein the first information indicates a first duration, and the first duration is an expected backoff duration; and executing backoff on the basis of second information of a first device, wherein the second information is determined on the basis of the first information of each device, the second information indicates a second duration, and the second duration is a backoff duration to be used. By means of determining, on the basis of received expected backoff time information corresponding to each device, backoff time information to be used by the first device, the probability of conflicts occurring between devices when sending data can be reduced, and thus the data transmission latency can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods and communication devices

[0001] Related cross-references

[0002] This application claims priority to Chinese Patent Application No. 202411556579.X, filed on November 2, 2024, entitled "Communication Method and Communication Device", and Chinese Patent Application No. 202411556579.X, filed on May 22, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology

[0004] With the development of communication technology, optical fiber transmission is increasingly being used in communication systems, among which fiber to the room (FTTR) is a crucial component of optical networks. An FTTR system includes a main device and sub-devices, connected via optical fiber. The main device, acting as an optical network terminal (ONT) or optical network unit (ONU) in a passive optical network (PON), is connected to the optical line terminal (OLT) at the operator's central office via optical fiber.

[0005] In an FTTR system, each device can independently compete for the channel. For example, an enhanced distributed channel access (EDCA) mechanism can be used for backoff and channel preemption, and data can be transmitted after successful channel preemption. Once a device has preempted the channel, other devices can determine the busy / idle state of the channel based on channel monitoring, and can backoff and access the channel if it is idle.

[0006] Under this channel access mechanism, air interface collisions may occur when two devices send data frames. This means that neither device can detect the other's initiation of data frame transmission in time, causing their data packets to interfere with each other and preventing timely data transmission, thus increasing data transmission latency. Therefore, reducing data transmission latency is a problem that needs to be considered. Summary of the Invention

[0007] This application provides a communication method and a communication device that can reduce the probability of air interface collisions during data transmission, thereby reducing data transmission latency.

[0008] In a first aspect, a communication method is provided, which can be executed by a first device or by a component of the first device (e.g., a chip, circuit, or chip system). The following description assumes execution by the first device.

[0009] The method includes: receiving first information from at least one device, each corresponding to the first device, the first information indicating a first duration for each device, the first duration being an expected backoff duration; and performing backoff based on second information corresponding to the first device, the second information being determined based on the first information corresponding to each device, the second information indicating a second duration being a backoff duration to be used.

[0010] Based on the above scheme, the first device can determine the backoff time information to be used for the first device based on the expected backoff time information of each of the at least one device received, thereby reducing the probability of the first device sending data conflicting with the data sent by at least one device and reducing data transmission latency.

[0011] In some implementations of the first aspect, the at least one device includes a second device, the first duration corresponding to the second device is the same as the first duration corresponding to the first device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the first device is less than a first threshold, and the first duration corresponding to the first device is adjusted to the second duration corresponding to the first device, and the second duration corresponding to the first device is different from the first duration corresponding to the first device.

[0012] In some implementations of the first aspect, if the first duration corresponding to each device is different from the first duration corresponding to the first device, or if the difference between the first duration corresponding to each device and the first duration corresponding to the first device is greater than or equal to a first threshold, then the second duration corresponding to the first device is the first duration corresponding to the first device.

[0013] In some implementations of the first aspect, the at least one device includes a second device, the first duration corresponding to the second device is the same as the first duration corresponding to the first device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the first device is less than a first threshold. The method further includes: sending the second information corresponding to the second device to the second device, the second information corresponding to the second device indicating that the second device corresponds to the second duration, and the second duration corresponding to the second device is different from the first duration corresponding to the second device.

[0014] Based on the above scheme, the first device can determine the backoff time information to be used by the second device based on the expected backoff time information corresponding to the first device, thereby reducing the probability of data conflict between the data sent by the second device and the data sent by the first device, and reducing data transmission latency.

[0015] In some implementations of the first aspect, the at least one device includes a second device and a third device, wherein the first duration corresponding to the second device is the same as the first duration corresponding to the third device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the third device is less than a first threshold, and the second information corresponding to the second device is sent to the second device, wherein the second duration corresponding to the second device is different from the first duration corresponding to the second device; and / or, the second information corresponding to the third device is sent to the third device, wherein the second duration corresponding to the third device is different from the first duration corresponding to the third device; wherein the second duration corresponding to the second device is different from the second duration corresponding to the third device.

[0016] Based on the above scheme, the first device can determine the backoff time information to be adopted for the second device and / or the third device based on the expected backoff time information corresponding to the second device and the third device among the at least one device, thereby reducing the probability of data transmission conflict between the second device and the third device and reducing data transmission latency.

[0017] In some implementations of the first aspect, the first information includes any one of the following: first indication information, an expected backoff end time; wherein the first indication information is used to determine the expected backoff end time, the first indication information includes the end time of the first channel being occupied and a first parameter set, the first channel being used to transmit data after the backoff, and the first parameter set includes the number of arbitration frame gaps and a first random backoff value.

[0018] In some implementations of the first aspect, the second information includes any one of the following: second indication information, a backoff end time to be adopted; wherein the second indication information is used to determine the backoff end time to be adopted, and the second indication information includes a second random backoff value.

[0019] In some implementations of the first aspect, a third indication information is received from each device, the third indication information indicating a statistical value of data transmission failures of each device during a first time period.

[0020] In some implementations of the first aspect, the determination of whether to send the second information corresponding to each device is based on the relationship between the statistical value of data transmission failures of each device and the second threshold.

[0021] In some implementations of the first aspect, a fourth indication information is received from each device, the fourth indication information indicating a first time difference between a first time and a second time, the first time being the time when each device is expected to send the first information corresponding to each device or the current time, and the second time being the end time when the first channel is occupied or the expected backoff start time or the expected backoff start time.

[0022] In some implementations of the first aspect, it is determined whether to send the second information corresponding to each device to each device based on the relationship between the first time difference corresponding to each device and the third threshold.

[0023] Secondly, a communication method is provided, which can be executed by a second device or by a component of the second device (e.g., a chip, circuit, or chip system). For ease of understanding, the following description assumes execution by a second device.

[0024] The method includes: sending first information to a first device, the first information indicating a first duration corresponding to the second device, the first duration being an expected backoff duration; receiving second information from the first device, the second information indicating a second duration corresponding to the second device, the second duration being a backoff duration to be used, the first duration being different from the second duration; and performing backoff based on the second information.

[0025] In some implementations of the first aspect, the first information includes any one of the following information corresponding to the second device: first indication information, expected backoff end time; wherein the first indication information is used to determine the expected backoff end time, the first indication information includes the end time of the first channel being occupied and a first parameter set, the first channel is used for the second device to transmit data after performing the backoff, and the first parameter set includes the number of arbitration frame gaps corresponding to the second device and a first random backoff value.

[0026] In some implementations of the first aspect, the second information includes any one of the following information corresponding to the second device: second indication information, a backoff end time to be adopted; wherein the second indication information is used to determine the backoff end time to be adopted, and the second indication information includes a second random backoff value corresponding to the second device, the second random backoff value being different from the first random backoff value.

[0027] In some implementations of the first aspect, the method further includes: sending a third indication message to the first device, the third indication message indicating a statistical value of data transmission failures of the second device within a first time period, the statistical value of data transmission failures of the second device being used in relation to a second threshold to determine whether to send the second message.

[0028] In some implementations of the first aspect, the first information is sent to the first device based on the relationship between the statistical value of the second device's data transmission failures within a first time period and a second threshold.

[0029] In some implementations of the first aspect, a fourth indication information is sent to the first device, the fourth indication information indicating a first time difference between a first time and a second time, the first time being the time when each device is expected to send the first information corresponding to each device or the current time, and the second time being the end time when the first channel is occupied or the expected backoff start time or the expected backoff start time.

[0030] In some implementations of the first aspect, the first information to be sent to the first device is determined based on the relationship between the first time difference and the third threshold. The first time difference is the time difference between a first moment and a second moment. The first moment is the moment when each device is expected to send the first information corresponding to each device or the current moment. The second moment is the end moment when the first channel is occupied or the expected backoff start moment or the expected backoff start moment.

[0031] Thirdly, a communication device is provided. The device can be a first device or a component of the first device (e.g., a chip, circuit, or chip system). The device can have the functions described in the first aspect. For example, the device includes modules, units, or means corresponding to the operations involved in the first aspect. The modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0032] Specifically, the device includes: a transceiver unit for receiving first information from at least one device, each corresponding to the first device, the first information indicating a first duration for each device, the first duration being an expected backoff duration; the device further includes: a processing unit for performing backoff based on second information corresponding to the first device, the second information being determined based on the first information corresponding to each device, the second information indicating a second duration, the second duration being a backoff duration to be used.

[0033] In some implementations of the third aspect, the at least one device includes a second device, the first duration corresponding to the second device is the same as the first duration corresponding to the device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the device is less than a first threshold, and the processing unit is further configured to: adjust the first duration corresponding to the device to the second duration corresponding to the device, the second duration corresponding to the device being different from the first duration corresponding to the device.

[0034] In some implementations of the third aspect, if the first duration corresponding to each device is different from the first duration corresponding to the device, or if the difference between the first duration corresponding to each device and the first duration corresponding to the device is greater than or equal to a first threshold, then the second duration corresponding to the device is the first duration corresponding to the device.

[0035] In some implementations of the third aspect, the at least one device includes a second device, the first duration corresponding to the second device is the same as the first duration corresponding to the device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the device is less than a first threshold. The transceiver unit is further configured to: send the second information corresponding to the second device to the second device, the second information corresponding to the second device indicating that the second device corresponds to the second duration, and the second device corresponds to the second duration differently from the first duration corresponding to the second device.

[0036] In some implementations of the third aspect, the at least one device includes a second device and a third device, wherein the first duration corresponding to the second device is the same as the first duration corresponding to the third device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the third device is less than a first threshold. The transceiver unit is further configured to: send the second information corresponding to the second device to the second device, wherein the second duration corresponding to the second device is different from the first duration corresponding to the second device; and / or send the second information corresponding to the third device to the third device, wherein the second duration corresponding to the third device is different from the first duration corresponding to the third device; wherein the second duration corresponding to the second device is different from the second duration corresponding to the third device.

[0037] In some implementations of the third aspect, the first information includes any one of the following: first indication information, and an expected backoff end time; wherein the first indication information is used to determine the expected backoff end time, the first indication information includes the end time of the first channel being occupied and a first parameter set, the first channel being used to transmit data after the backoff, and the first parameter set includes the number of arbitration frame gaps and a first random backoff value.

[0038] In some implementations of the third aspect, the second information includes any one of the following: second indication information, a backoff end time to be adopted; wherein the second indication information is used to determine the backoff end time to be adopted, and the second indication information includes a second random backoff value.

[0039] In some implementations of the third aspect, the transceiver unit is further configured to: receive third indication information from each device, the third indication information indicating statistical values ​​of data transmission failures of each device within a first time period.

[0040] In some implementations of the third aspect, the processing unit is further configured to: determine whether to send the second information corresponding to each device to each device based on the relationship between the statistical value of each device's data transmission failure and the second threshold.

[0041] In some implementations of the third aspect, the transceiver unit is further configured to: receive fourth indication information from each device, the fourth indication information indicating a first time difference between a first time and a second time, the first time being the time when each device is expected to send the first information corresponding to each device or the current time, and the second time being the end time when the first channel is occupied or the expected backoff start time or the expected backoff start time.

[0042] In some implementations of the third aspect, the processing unit is further configured to: determine whether to send the second information corresponding to each device to each device based on the relationship between the first time difference and the third threshold corresponding to each device.

[0043] Fourthly, a communication device is provided. The device can be a second device or a component of the second device (e.g., a chip, circuit, or chip system). The device can have the functions described in the second aspect. For example, the device includes modules, units, or means corresponding to the operations involved in the second aspect. The modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0044] The device includes: a transceiver unit for sending first information to a first device, the first information indicating a first duration corresponding to the second device, the first duration being an expected backoff duration; the transceiver unit is also configured to receive second information from the first device, the second information indicating a second duration corresponding to the device, the second duration being a backoff duration to be used, the first duration being different from the second duration; the device further includes a processing unit for performing backoff based on the second information.

[0045] In some implementations of the fourth aspect, the first information includes any one of the following information corresponding to the device: first indication information, expected backoff end time; wherein the first indication information is used to determine the expected backoff end time, the first indication information includes the end time of the first channel being occupied and a first parameter set, the first channel is used for the device to transmit data after performing the backoff, and the first parameter set includes the number of arbitration frame gaps corresponding to the device and a first random backoff value.

[0046] In some implementations of the fourth aspect, the second information includes any one of the following information corresponding to the device: second indication information, a backoff end time to be adopted; wherein the second indication information is used to determine the backoff end time to be adopted, and the second indication information includes a second random backoff value corresponding to the device, the second random backoff value being different from the first random backoff value.

[0047] In some implementations of the fourth aspect, the transceiver unit is further configured to: send a third indication message to the first device, the third indication message indicating a statistical value of data transmission failures of the device within a first time period, the statistical value of data transmission failures of the device being used in relation to a second threshold to determine whether to send the second message.

[0048] In some implementations of the fourth aspect, the transceiver unit is specifically used to: determine, based on the relationship between the statistical value of the device's data transmission failures within a first time period and a second threshold, send the first information to the first device.

[0049] In some implementations of the fourth aspect, the transceiver unit is further configured to: send fourth indication information to the first device, the fourth indication information indicating a first time difference between a first time and a second time, the first time being the time when each device is expected to send the first information corresponding to each device or the current time, the second time being the end time when the first channel is occupied or the expected backoff start time or the expected backoff start time, and the relationship between the first time difference and the third threshold is used to determine whether to send the second information.

[0050] In some implementations of the fourth aspect, the transceiver unit is specifically used to: determine the transmission of the first information to the first device based on the relationship between the first time difference and the third threshold, wherein the first time difference is the time difference between the first moment and the second moment, the first moment is the moment when each device is expected to transmit the first information corresponding to each device or the current moment, and the second moment is the end moment when the first channel is occupied or the expected backoff start moment or the expected backoff start moment.

[0051] It should be understood that for any parts of the third and fourth aspects that are not described in detail, please refer to the first and second aspects.

[0052] Fifthly, a communication device is provided, comprising: a memory for storing a program; and at least one processor for executing the computer program or instructions stored in the memory to perform the method provided in any of the foregoing aspects or their implementations.

[0053] In one implementation, the device is either a first device or a second device.

[0054] In another implementation, the device is a chip, chip system, or circuit for use in a first or second device.

[0055] Sixthly, a communication apparatus is provided, comprising: at least one processor and a communication interface, the at least one processor being configured to obtain a computer program or instructions stored in a memory via the communication interface to execute the method provided in any of the foregoing aspects or their implementations. The communication interface may be implemented in hardware or software.

[0056] In one implementation, the device also includes a memory.

[0057] In a seventh aspect, a processor is provided for performing the methods provided in the above aspects.

[0058] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0059] Eighthly, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including methods for performing any of the foregoing aspects or their implementations.

[0060] Ninthly, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method provided in any of the foregoing aspects or their implementations.

[0061] In a tenth aspect, a chip is provided, comprising a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface and executes the method provided in any of the above aspects or their implementations. The communication interface can be implemented in hardware or software.

[0062] Optionally, as one implementation, the chip also includes a memory that stores computer programs or instructions. The processor is used to execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to perform the methods provided by any of the above aspects or their implementations.

[0063] When the method provided in this application is executed by a chip, this application does not limit the specific number of chips implementing the method. For example, it can be executed by one chip, or by two or more chips. Furthermore, when the number of chips implementing the method is two or more, the chip manufacturers are not limited; they can be from the same manufacturer or different manufacturers.

[0064] In the eleventh aspect, a computer program product is provided that, when run on a computer, causes the method provided by any of the foregoing aspects or their implementations to be executed.

[0065] In a twelfth aspect, a communication system is provided, including the first device and the second device described above.

[0066] It should be understood that the beneficial effects of aspects five through twelfth and any of their implementations can be referenced in aspects one and two and any of their implementations. Attached Figure Description

[0067] Figure 1 is a schematic diagram of an application scenario to which this application applies.

[0068] Figure 2 is a schematic diagram of a communication system to which this application applies.

[0069] Figure 3 is a schematic diagram of another application scenario to which this application applies.

[0070] Figure 4 is an example of the random backoff process among multiple APs based on the EDCA mechanism.

[0071] Figure 5 is a schematic flowchart of the communication method 500 provided in this application.

[0072] Figure 6 is a schematic flowchart of the communication method 600 provided in this application.

[0073] Figure 7 is an example diagram of the equipment retreating process.

[0074] Figure 8 is a schematic flowchart of the communication method 800 provided in this application.

[0075] Figure 9 is a schematic flowchart of the communication method 900 provided in this application.

[0076] Figures 10 and 11 are schematic diagrams of the structure of the communication device provided in the embodiments of this application. Detailed Implementation

[0077] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0078] The embodiments of this application can be applied to wireless local area networks (WLANs), for example, supporting IEEE 802.11 related standards, such as 802.11a / b / g standards, 802.11n standards, 802.11ac standards, 802.11ax standards (i.e., Wi-Fi 6, also known as the high efficient (HE) standard), 802.11be standards (i.e., Wi-Fi 7, also known as the extremely high throughput (EHT) standard), 802.11bn standards (i.e., Wi-Fi 8, also known as the ultra high reliability (UHR) standard) or next-generation Wi-Fi 8 standards, and also include 802.11ad, 802.11ay standards, etc. The embodiments of this application can also be applied to wireless local area network systems that support integrated millimeter wave (IMMW), wireless local area network systems that support ultra-wideband (UWB) such as the 802.15 series standards, sensing systems such as the 802.11bf series standards, or wireless positioning such as 802.11az. This application can also support standard protocols such as spark link and near link.

[0079] The various aspects described in this application can be extended to other networks employing various standards or protocols, such as high-performance radio local area networks (HIPERLANs), wireless wide area networks (WWANs), wireless personal area networks (WPANs), or other networks now known or developed in the future. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in this application can be applied to any suitable wireless network.

[0080] The technical solutions of this application embodiment can also be applied to various communication systems, such as: WLAN communication systems, Wi-Fi systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems or new radio (NR) systems, next-generation communication systems, Internet of Things (IoT) networks or vehicle-to-everything (V2X) networks, etc.

[0081] The technical solutions of this application embodiment can also be applied to various passive optical network (PON) systems, such as next-generation PON (NG-PON), NG-PON1, NG-PON2, gigabit-capable PON (GPON), 10 gigabit per second PON (XG-PON), 10-gigabit-capable symmetric passive optical network (XGS-PON), Ethernet PON (EPON), 10 gigabit per second EPON (10G-EPON), next-generation EPON (NG-EPON), wavelength-division multiplexing (WDM) PON, time-division wavelength-division multiplexing (TWDM) PON, and point-to-point WDM. PON, including Asynchronous Transfer Mode PON (APON), Broadband PON (BPON), and others, as well as 25 gigabit per second PON (25G-PON), 50 gigabit per second PON (50G-PON), 100 gigabit per second PON (100G-PON), 25 gigabit per second EPON (25G-EPON), 50 gigabit per second EPON (50G-EPON), 100 gigabit per second EPON (100G-EPON), and other rates such as GPON and EPON. It can also be used in optical networks such as optical transport networks (OTN).

[0082] The communication systems described above that are applicable to this application are merely illustrative examples, and the communication systems applicable to this application are not limited thereto.

[0083] Figure 1 is a schematic diagram of an application scenario applicable to an embodiment of this application. As shown in Figure 1, the communication method provided by this application is applicable to data communication between stations (STAs). A station can be an access point (AP) type station or a non-access point station (non-AP STA), referred to as an AP and a non-AP station, respectively. Specifically, the solution of this application is applicable to communication between an AP and one or more non-AP stations (e.g., communication between AP1 and non-AP STA1, non-AP STA2), communication between APs (e.g., communication between AP1 and AP2), and communication between non-AP STAs (e.g., data communication between non-AP STA2 and non-AP STA3). Unless otherwise specified in this application, a station (or STA) includes both non-AP STAs and APs; that is, a station (or STA) can be either a non-AP STA or an AP.

[0084] An Access Point (AP) can be a node that allows terminals (such as mobile phones) to access a wired (or wireless) network. It is primarily deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. Of course, it can also be deployed outdoors. An AP acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet.

[0085] Specifically, an AP can be a terminal or network device with a Wi-Fi chip. This network device can be a server, router, switch, bridge, computer, mobile phone, relay station, vehicle-mounted equipment, wearable device, network device in a 5G network, network device in a 6G network, or network device in a public land mobile network (PLMN), etc., and this application embodiment is not limited to these. The AP can be a device that supports Wi-Fi standards. For example, the AP can also support one or more standards in the IEEE 802.11 series, such as 802.11be and 802.11be next generation.

[0086] Non-AP sites can be wireless communication chips, wireless sensors, or wireless communication terminals, and can also be referred to as users, user equipment (UE), access terminals, user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication equipment, user agents, or user devices. Non-AP sites can be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, IoT devices, wearable devices, terminal devices in 5G networks, terminal devices in future communication systems, or terminal devices in PLMNs, etc., and this application embodiment is not limited to these. Non-AP sites can be devices that support WLAN standards. For example, non-AP sites can support one or more standards in the IEEE 802.11 series, such as 802.11be and 802.11be next generation.

[0087] For example, non-AP sites can be mobile phones, tablets, set-top boxes, smart TVs, smart wearable devices, vehicle communication devices, computers, Internet of Things (IoT) nodes, sensors, smart home devices such as smart cameras, smart remote controls, smart water and electricity meters, and sensors in smart cities.

[0088] The aforementioned AP or non-AP sites may include transmitters, receivers, memory, processors, etc., wherein the transmitter and receiver are used for transmitting and receiving packet structures, respectively, the memory is used for storing signaling information and pre-agreed preset values, etc., and the processor is used for parsing signaling information and processing related data, etc.

[0089] Figure 2 is a schematic diagram of the system architecture of fiber to the home or fiber to the office (FTTH / O) applicable to embodiments of this application.

[0090] As shown in Figure 2, an optical line terminal (OLT) connects to upper-layer network-side devices (such as switches and routers) and lower-layer devices (such as optical distribution networks, ODNs). An ODN includes passive optical splitters for optical power distribution, a backbone fiber connecting the passive optical splitter and the OLT, and branch fibers connecting the passive optical splitter and ONUs. When transmitting downlink signals, the downlink signal sent by the OLT is transmitted to each ONT through the splitter, and the ONT selectively receives downlink data belonging to itself from the downlink signal. When transmitting uplink signals, the uplink signals sent by N ONTs are combined into a single optical signal by the splitter and transmitted to the OLT. An optical network unit (ONU) provides a user-side interface to the ODN and is also connected to the ODN. If the ONU also provides user port functionality, such as an Ethernet user port or a plain old telephone service (POTS) user port, it is called an optical network termination (ONT).

[0091] Building upon FTTH / O, to address the issue of home Wi-Fi coverage, fiber optic cables can be extended further into residents' rooms. Optical terminal equipment providing Wi-Fi access is installed inside the rooms, thus reducing the distance between the user's terminal and the Wi-Fi access point and improving signal quality. This application scenario is called Fiber to the Room (FTTR).

[0092] Figure 3 is a schematic diagram of the system architecture of FTTR applicable to embodiments of this application.

[0093] As shown in Figure 3, in FTTH / O, the OLT is deployed in the central equipment room, while the ONT is deployed in homes or offices. The master device in the FTTR network acts as both the ONT in the FTTH network and the upstream device for the FTTR slave devices, managing them. The slave devices in FTTR can be deployed in various rooms of homes or offices to provide signal to user terminals. The slave devices possess the functions of an ONT and can also function as wireless access points (APs).

[0094] Multiple slave devices can be deployed in an FTTR system, each connected to the master device via an optical splitter. The master device can centrally manage and configure all slave devices. The master device can also be called a "master gateway," "master optical modem," or "master FTTR unit (MFU)," while slave devices can be called "slave gateways," "slave optical modems," or "slave FTTR units (SFU)," etc.

[0095] In the above application scenarios, each station can independently compete for the channel and transmit data after successfully seizing the channel. This could be an AP in a WLAN communication system, a non-AP STA, or a master or slave device in an FTTR. The following explanation uses an AP as an example. For instance, an AP can use an enhanced distributed channel access (EDCA) mechanism to back off and seize the channel, and transmit data after successfully seizing it. Once an AP seizes the channel, other APs can determine the busy / idle state of the channel based on channel monitoring, and back off and access the channel if it is idle.

[0096] The EDCA mechanism primarily uses a backoff and waiting method to grant high-priority packets priority in transmission and more bandwidth. The basic idea of ​​EDCA is that when an AP intends to send data, it needs to perform Clear Channel Access (CCA). If the channel is idle for a period of time (such as the Arbitration Inter-Frame Spacing (AIFS)), the AP can initiate a random backoff (or random backoff) process. If the channel is occupied (busy), the AP must wait for the channel to become idle, and after remaining idle for a period of time (such as AIFS), it will begin the random backoff process. After the random backoff process is complete, the AP can transmit data.

[0097] It should be understood that the AP in this application may refer to the MFU and SFU in an FTTR network, or to the AP in a WLAN communication system (see the description above for details), without limitation.

[0098] Figure 4 shows an example of a random backoff process among multiple APs based on the EDCA mechanism.

[0099] As shown in Figure 4, initially, AP1 sends a data frame, while AP2, AP3, and AP4 all delay sending their data frames. After AP1 finishes sending its data frame (i.e., the channel becomes idle), AP2, AP3, and AP4 remain idle for a period of time (e.g., AIFS) before initiating a random backoff process. At time #1, AP3 completes its random backoff process first, sends a data frame, and AP2 and AP4 freeze their remaining backoff time, as shown by the shaded area in Figure 4. While AP3 is sending its data frame, AP5 delays sending its data frame. After AP3 finishes sending its data frame (i.e., the channel becomes idle), AP2, AP4, and AP5 remain idle for a period of time before initiating a random backoff process. At time #2, AP4 completes its random backoff process first, sends a data frame, and AP2 and AP5 freeze their remaining backoff time, as shown by the shaded area in Figure 4. This continues until time #3, when AP5 completes its random backoff process and sends a data frame. At time #4, AP2 completes its random backoff process and sends a data frame.

[0100] The following is a brief introduction to the method by which the AP determines the random backoff time required for rollback. For example, the random backoff time required by the AP is a random backoff value (or random backoff value) multiplied by the duration of a time slot. The random backoff value is randomly selected from a uniformly distributed window [0, CW]. The contention window (CW) has multiple values. It is initialized to its minimum value (CWmin) during the initial attempt. Each time a transmission fails (e.g., a collision occurs), a retransmission is required, and CW increases progressively until it reaches its maximum value (CWmax). When data is successfully transmitted, CW is reset to CWmin.

[0101] EDCA allows services of different access categories (ACs) to have different sets of EDCA parameters. Currently, the protocol defines the following ACs: Background Information Access Category (AC_background, AC_BK), Best Effort Access Category (AC_best effort, AC_BE), Voice Access Category (AC_voice, AC_VO), Video Access Category (AC_video, AC_VI), and Legacy Access Category. Different access categories can also represent different service types.

[0102] The EDCA parameter set includes a set of parameters for channel access corresponding to each AC. Parameters in the EDCA parameter set include CWmin, CWmax, AIFSN (which can be used to determine AIFS), and the transmission opportunity (TXOP) limit, i.e., the maximum number of transmission opportunities. Table 1 shows an example of the (default) EDCA parameter values ​​for a different AC.

[0103] Table 1

[0104] As can be seen from Table 1, different arbitration interframe spacing number (AIFSN) and CW settings will be used for different service types (such as voice, video, etc.). These settings can enable high-priority services to obtain the channel more quickly, thereby reducing latency and improving service quality.

[0105] As shown above, multiple APs can determine the expected end time of their backoff behavior based on the AIFSN and CW corresponding to each service. That is, after the channel occupancy of the previous transmission ends, the expected end time of the backoff behavior is determined based on the remaining backoff time slots (count value) corresponding to the random backoff value determined by the AIFSN and CW. For high-priority services, there is usually a smaller CW, resulting in a smaller range of random backoff values ​​[0, CW]. Therefore, it is possible for two APs in the network to select the same random backoff value, increasing the probability of air interface collisions (i.e., neither AP can detect the other's data frame transmission in time, causing their data packets to interfere with each other and preventing timely data transmission) when sending data frames. It can be understood that when there are multiple adjacent APs in the network, the probability of air interface collisions between APs further increases with the number of APs.

[0106] In view of this, this application proposes a communication method and a communication device that can reduce the probability of air interface collision when the AP sends data frames and reduce data transmission latency.

[0107] To facilitate understanding of the embodiments of this application, the following points are provided.

[0108] First, the terms "first," "second," and various numerical designations (e.g., "#1," "#2," etc.) shown in this application are for descriptive convenience and to distinguish objects, and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish different devices, etc., and are not used to describe a specific order or sequence. It should be understood that such described objects can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0109] Second, in the embodiments of this application, the terms "of", "corresponding (relevant)", "corresponding" and "associate" can sometimes be used interchangeably. It should be noted that when their differences are not emphasized, their intended meanings are consistent.

[0110] It should be understood that the embodiments shown below illustrate the method by using a first device, a second device, and a third device as examples of interactive execution entities. However, this application does not limit the execution entity; any program capable of running the code of the method provided in the embodiments of this application can communicate according to the method provided in the embodiments of this application. The execution entity of the method provided in the embodiments of this application can be a first device, a second device, or a third device, or a functional module in the first device, second device, or third device capable of calling and executing a program. For example, the first device in FIG5 can also be a chip, chip system, or processor that supports the method that the first device can implement, or it can be a logic module or software that can implement all or part of the functions of the first device; the second device in FIG5 can also be a chip, chip system, or processor that supports the method that the second device can implement, or it can be a logic module or software that can implement all or part of the functions of the second device; the third device in FIG5 can also be a chip, chip system, or processor that supports the method that the third device can implement, or it can be a logic module or software that can implement all or part of the functions of the third device.

[0111] Figure 5 is a schematic flowchart of a communication method 500 provided in this application. As shown in Figure 5, the method includes the following steps.

[0112] S510, the second device sends first statistical information to the first device. Accordingly, the first device receives the first statistical information.

[0113] As an example, the first device can be an AP or a non-AP STA; the second device can be an AP or a non-AP STA.

[0114] As another example, the first device is an FTTR network device, such as an MFU or SFU in an FTTR network; the second device is an FTTR network device, such as an MFU or SFU in an FTTR network.

[0115] For example, the first device and the second device can be different APs or different STAs, or the first device can be a STA and the second device can be an AP.

[0116] For example, the first device and the second device may both be SFUs in the FTTR network, or the first device may be an MFU in the FTTR network and the second device may be an SFU in the FTTR network.

[0117] Optionally, the first device is a third-party device, for example, a controller for adjusting the backoff time.

[0118] This first statistic can indicate the data frame transmission status of the second device.

[0119] As an example, the first statistic may include statistics on data frame transmission failures (or successes) (or conflict statistics), and this first statistic may be referred to as a conflict statistics report or historical conflict information.

[0120] The statistical value for data frame transmission failure (success) can be the number of times data frame transmission failed (successfully) or the ratio of the number of times data frame transmission failed (successfully) to the total number of data frames transmitted in time period #1 (or the number of times data frames were successfully (failed)), or other statistical values ​​used to characterize the data frame transmission status, without specific limitations. The following explanation uses the number of times data frame transmission failed as the statistical value for data frame transmission failure (successfully) as an example.

[0121] It should be understood that data frame transmission statistics can be performed at the granularity of physical layer protocol data units (PPDUs) or MAC protocol data units (MACs), without limitation. For example, the number of data frame transmission failures could be the number of PPDU transmission failures or the number of MPDU transmission failures; similarly, the total number of data frames transmitted could be the total number of MPDUs transmitted or the total number of MPDU transmissions.

[0122] For example, the number of times the data frame transmission failed is the number of times the data frame transmission failed within time period #1. This application does not limit the duration of time period #1, but can set it according to the actual situation. For example, time period #1 is the time period corresponding to N rounds of contention for access between the second device and at least one device, where N is a positive integer.

[0123] Optionally, the first statistical information may also include the access type AC of the service corresponding to the number of data frame transmission failures, that is, the first statistical information may indicate the number of data frame transmission failures for each AC in at least one AC corresponding to the first device.

[0124] For example, the first statistical information includes the number of data frame transmission failures #1 and the number of data frame transmission failures #2. The number of data frame transmission failures #1 corresponds to AC#1 of the first device (e.g., AC_VO), indicating the number of times the first device failed to transmit data frames for the AC#1 service within the time period #1; the number of data frame transmission failures #2 corresponds to AC#2 of the first device (e.g., AC_VI), indicating the number of times the first device failed to transmit data frames for the AC#2 service within the time period #1.

[0125] As another example, the first statistic includes the service load of the first device.

[0126] For example, the first statistical information includes the load status of service #1 and service #2 of the first device. The first statistical information can indicate the load status of the first device in sending data of service #1 within time period #1, such as high load, and the load status of sending data of service #2, such as low load.

[0127] Similarly, the first set of statistics also includes the access type (AC) of the service corresponding to the number of data frame transmission failures.

[0128] For example, the first statistical information may be carried in the frame sent by the second device to the first device, or it may be carried in the physical layer (PHY) header or medium access control (MAC) header of any physical layer protocol data unit (PPDU) sent by the second device, or it may be carried in the broadcast frame sent by the second device, without limitation.

[0129] This application does not limit the specific method by which the second device sends the first statistical information to the first device. For example, both the first device and the second device operate on the same channel when performing S510, and the second device sends the first statistical information on that channel; or, for another example, the second device may also send the first statistical information to the first device through a wired channel (e.g., the Wi-Fi management and control interface (WMCC) in a PON).

[0130] The second device may also be one of at least one devices, with specific examples of the at least one device provided in the second device description. Each of the at least one devices may send the first statistical information corresponding to that device to the first device. The first statistical information corresponding to each device is similar to the first statistical information corresponding to the second device; for example, the portion of the description of the first statistical information involving the second device can be replaced with that of each device.

[0131] The method by which at least one device sends the first statistical information to the first device is similar to the method by which the second device sends it, and there is no limitation thereto.

[0132] S520, the first device sends second information to the second device. Accordingly, the second device receives the second information.

[0133] The second information indicates the first parameter set, the values ​​of which are determined based on the first statistical information. The parameters in this first parameter set are used by the second device to access the channel based on the corresponding channel access mechanism.

[0134] It should be understood that this application does not limit the specific mechanism used by the second device to compete for channel access. For example, the mechanism may be the EDCA mechanism, or it may be a high-priority (HiP) channel access mechanism. When different channel access mechanisms are used, the first parameter set can be the parameter sets corresponding to different channel access mechanisms, and the comparison is not limited.

[0135] The following introduction uses the EDCA mechanism as an example for channel access.

[0136] The first parameter set can be understood as the adjusted EDCA parameter set, that is, the first device adjusts the values ​​of the parameters in the EDCA parameter set based on the first statistical information to obtain the adjusted EDCA parameter set. The values ​​of the parameters in the EDCA parameter set before adjustment are shown in Table 1 above.

[0137] For example, if the first statistical information includes the number of data frame transmission failures, the first device determines to adjust the EDCA parameter set, such as increasing or decreasing CW, based on the relationship between the number of data frame transmission failures and the threshold #1.

[0138] For example, if the number of data frame transmission failures is greater than or equal to threshold #1, the first device adjusts the EDCA parameter set based on the first statistical information; otherwise, it does not adjust it.

[0139] If the first statistical information includes relevant business information, the first device determines to adjust the EDCA parameter set based on the relevant business information.

[0140] For example, when the load is high, the first device adjusts the EDCA parameter set based on the first statistical information, such as increasing CW; otherwise, it does not adjust it.

[0141] Optionally, if the first statistical information includes the access type AC corresponding to the service, the first device may adjust the EDCA parameter set corresponding to at least one of the multiple ACs corresponding to the first device based on the first statistical information.

[0142] For example, the first device can determine the relationship between the number of times data frames are sent for AC#1 service and AC#2 service and the threshold #1, and adjust the EDCA parameter set corresponding to ACs whose number of data frame transmission failures is greater than or equal to the threshold #1.

[0143] In one possible implementation, the second information may include the adjusted EDCA parameters, for example, the adjusted AIFSN value, the adjusted CW value, etc.

[0144] In another possible implementation, the second information indicates the difference between the adjusted EDCA parameters and the original EDCA parameters. That is, the second information indicates the adjustment method for adjusting the EDCA parameter set. For example, the second information may indicate to add 1 or subtract 1 from CW.

[0145] It should be understood that this application does not limit the specific values ​​of the parameters in the EDCA parameter set, which can be determined according to actual needs.

[0146] Optionally, the second device accesses the channel based on the adjusted EDCA parameter set.

[0147] Specifically, the second device can perform a random backoff procedure based on the adjusted EDCA parameter set and access the channel. This random backoff procedure is described above and will not be repeated here.

[0148] Optionally, the first device sends the second information corresponding to the other device (e.g., the third device) to the other device among the at least one devices. The specific method by which the first device sends the second information to the third device is the same as the method by which the first device sends the second information to the second device, and will not be repeated here.

[0149] Based on the above scheme, by having the first device adjust the parameter set for channel access corresponding to at least one device based on the data frame transmission status of at least one device in the network, the probability of air interface collision can be reduced, thereby reducing the data transmission latency.

[0150] Figure 6 is a schematic flowchart of a communication method 600 provided in this application. As shown in Figure 6, the method includes the following steps.

[0151] S610, the second device sends first information to the first device. Accordingly, the first device receives the first information.

[0152] The first device and the second device are described in S510.

[0153] The first information indicates the expected backoff time information, or the first information indicates the expected time information for transmitting data frames, or the first information indicates the expected time information for delayed access. This first information may be referred to as backoff information or backoff time information.

[0154] It should be understood that in this application, "expected information (e.g., expected retreat time information)" and "expected information (e.g., expected retreat time information)" are interchangeable and have the same meaning unless otherwise specified.

[0155] As an example, the first information is information #1 (an example of a first indication information), which includes information for determining the expected end time of the backoff.

[0156] For example, information #1 includes the end time when channel #1 (an example of the first channel) is occupied, AIFSN (or the duration corresponding to AIFS), and the expected backoff time (or backoff duration, or backoff countdown).

[0157] For example, as shown in Figure 7(a), the expected backoff start time, i.e. time #3, can be determined based on the end time of channel #1 being occupied (i.e. time #2) and AIFS #1, and the expected backoff end time, i.e. time #4, can be determined based on time #3 and the expected backoff duration.

[0158] The expected backoff end time can be understood as the expected end time of the backoff execution, assuming that channel #1 is in an idle state during the backoff time, starting from the backoff start time.

[0159] Channel #1 can be understood as the channel used to transmit data frames after the backoff ends. The end time of channel #1 being occupied can be determined by the length of time channel #1 needs to be occupied. For example, the end time of channel #1 being occupied is the sum of the current time and the length of time device #1 needs to occupy the channel, where device #1 can be the device currently occupying channel #1. For instance, a second device receives a radio frame from device #1 and determines the length of time device #1 needs to occupy the channel based on the value of the network allocation vector (NAV) set in the duration field of the radio frame, thereby determining the end time of channel #1 being occupied.

[0160] It should be understood that the end time of channel #1 being occupied is optional. For example, the end time of channel #1 being occupied can also be determined by the first device, such as the first device determining the end time in a manner similar to that of the second device.

[0161] There are no specific limitations on channel #1. For example, channel #1 is the main channel, such as the main 20MHz channel. The operating frequency band of channel #1 can be 2.4GHz, 5GHz, 6GHz, or 60GHz, etc.

[0162] The AIFSN corresponds to the access category of the service provided by the second device. Refer to the description above for the specific correspondence between access categories and AIFSNs. Alternatively, information #1 may include indication information indicating the service category.

[0163] It should be understood that AIFSN corresponds to AIFS, and the first information may include either one of them.

[0164] The expected backoff time can be represented by the number of remaining backoff slots. The expected backoff time can be the product of the number of remaining backoff slots and the length of the slots. The number of remaining backoff slots can be replaced by a random backoff value or the value of a backoff counter (or backoff countdown).

[0165] It should be understood that if the second device does not perform backoff, the remaining backoff time slots are the initially determined backoff time slots. This initially determined backoff time slot number can be selected from the contention window; for example, the initially determined backoff time slot number can be randomly selected from [0, CWmin].

[0166] Table 2 shows an example of the content included in information #1.

[0167] Table 2

[0168] As another example, this first information includes the expected backoff end time (or the expected data frame transmission time).

[0169] That is, the expected backoff end time can be determined by the second device, which then sends the expected backoff end time determined by the first device to the first device. For example, the second device determines the expected backoff end time based on the aforementioned information #1.

[0170] Alternatively, the first information includes the expected start time of the backoff and the number of remaining backoff slots.

[0171] Table 3 shows an example of the contents included in the first information.

[0172] Table 3

[0173] It should be understood that the aforementioned channel number is optional information. For example, without reporting the channel number, the first device can determine the occupied channel. The device identifier is used by the first device to communicate with the device, and the device identifier is optional information. Taking the second device as an example, without including the identifier of the second device, the first device can communicate with the second device based on the media access control (MAC) address corresponding to the second device, or the first device can determine the second device based on other information, such as the time information of communication with the second device.

[0174] Optionally, the second device sends the first information to the first device if it determines that the conditions shown in the following example are met.

[0175] Example #1: The statistical value of data frame transmission (or success) failures of the second device within time period #1 (an example of the first time period) is greater than or equal to threshold #1. The following explanation uses the statistical value of data frame transmission failures as an example.

[0176] For example, the statistical value for data frame transmission failure can be the number of times data frame transmission failed, or the ratio of the number of times data frame transmission failed to the total number of data frames transmitted in time period #1 (or the number of times data frames were successfully transmitted), or other values ​​used to characterize the probability of data frame transmission failure, without specific limitations. For example, this statistical value can be determined by the value of a counter that tracks the transmission status of data frames. A statistical value for data frame transmission failure by the second device in time period #1 exceeding a threshold can also be interpreted as the second device having a higher probability of encountering a conflict during the contention for access to the channel.

[0177] Example #2: The duration of time period #2 is greater than or equal to the threshold #2.

[0178] Wherein, time period #2 can be the time period between the expected time (or the current time) to send the first information and the end time when channel #1 is occupied. Time period #2 can also be the time interval between the expected time (or the current time) to send the first information and the end time of backoff. Time period #2 can also be the time period between the expected time (or the current time) to send the first information and the start time of backoff; this application does not specifically limit time period #2.

[0179] It should be understood that the second device can determine whether to send the first information to the first device based on any of the above examples, or it can combine examples #1 and #2 to determine whether to send the first information to the first device, without limitation.

[0180] It should also be understood that this application does not limit the size of the above thresholds (e.g., threshold #1, threshold #2), and they can be determined according to actual needs. For example, the value of threshold #2 can be the delay in the second device sending information to the first device. The above thresholds can be pre-configured or preset in the corresponding devices (e.g., the first device and / or the second device).

[0181] Optionally, the second device sends to the first device at least one of the statistical values ​​of data frame transmission failures during time period #1 (an example of the first time period) and the duration corresponding to time period #2, so that the first device can determine whether to send the second information to the second device (see the description below for details).

[0182] The second device sending the time period #2 to the first device can occur before S610. The time period #2 sent by the second device to the first device can indicate the capability information of the second device, that is, whether the second device has the capability to execute method 600. For example, if the time period #2 is less than the threshold #2, it indicates that the second device does not support executing the method.

[0183] It should be understood that this application does not limit the specific information representing the capability information. That is, the second device may also send other capabilities to the first device to indicate whether the second device supports the method. For example, the second device may send capability information that directly indicates whether it supports executing the method according to its own settings.

[0184] For example, the second device described above can be one of at least one devices. Each of the at least one devices can send the first information corresponding to each device to the first device.

[0185] For example, if the first device is an MFU in an FTTR network, the at least one device may include at least one SFU in the FTTR network; or, if the first device is an SFU in an FTTR network, the at least one device may include other SFUs in the FTTR network besides the SFU in question.

[0186] The first information corresponding to the other device sent by the at least one device other than the second device to the first device can refer to the first information corresponding to the second device. For example, the part of the first information corresponding to the second device that involves the second device can be replaced with the other device.

[0187] For example, the at least one device further includes a third device. The first information corresponding to the third device may include the end time of channel #1 being occupied, the AIFSN corresponding to the access category of the service of the third device, and the expected backoff time corresponding to the third device. Alternatively, the first information corresponding to the third device may include the expected backoff end time determined by the third device.

[0188] The specific method by which the other device sends the first information corresponding to the other device to the first device is similar to the method by which the second device sends the first information corresponding to the second device to the first device. Please refer to the description above for details, which will not be repeated here.

[0189] S620, the first device performs backoff based on the second information corresponding to the first device.

[0190] The second information corresponding to the first device is determined based on the first information corresponding to each of the at least one device. The first information corresponding to each device is described above.

[0191] The second piece of information indicates the backoff time information to be adopted (or updated, or adjusted).

[0192] That is, the first device can adjust the expected retreat time information corresponding to the first device according to the first information corresponding to each device, and obtain the adjusted retreat time information.

[0193] As an example, the second information may include the adjusted number of remaining backoff slots, or the second information may include the adjusted backoff end time.

[0194] As another example, the second information includes either a first value or a second value. The first value is the difference between the adjusted remaining backoff time slots and the expected remaining backoff time slots; the second value is the difference between the adjusted backoff end time and the expected backoff end time.

[0195] For example, the first value is an integer.

[0196] For example, the first value is N1, where N1 is a positive integer. This means that the adjusted number of remaining backoff time slots is greater than the expected number of remaining backoff time slots. In other words, the adjusted backoff time can be obtained by extending the expected backoff time by N1 * the length of the time slot, where * represents multiplication.

[0197] For example, the first value is N2, where N2 is a negative integer. This means that the adjusted number of remaining backoff time slots is less than the expected number of remaining backoff time slots. In other words, the adjusted backoff time can be obtained by shortening the expected backoff time by N2 * the length of the time slot.

[0198] For example, the first value is 0, which means that the expected number of remaining backoff slots will not be adjusted, or in other words, the number of remaining backoff slots to be used is the expected number of remaining backoff slots.

[0199] The range of values ​​for the second value is similar to that for the first value, so it will not be repeated here.

[0200] For example, before performing backoff based on the second information corresponding to the first device, the first device determines the second information corresponding to itself based on the first information corresponding to each of the at least one device. Specifically, this may include: if it is determined that device #2 exists among the at least one device, adjusting the expected backoff time information of the first device based on the first information of device #2. Here, device #2 may be a device whose expected backoff time information conflicts with the expected backoff time information of the first device. For example, the expected backoff end time of device #2 is the same as the expected backoff end time of the first device; or, for another example, the difference between the expected backoff end time of device #2 and the expected backoff end time of the first device is less than a threshold #3.

[0201] Taking device #2 as the second device as an example, assuming that the backoff time information of the first device and the second device before adjustment is as shown in Figure 7(a), the backoff time information after adjustment can be as shown in Figure 7(b). That is, the second information corresponding to the first device includes a first value, which is 2 (the number of time slots corresponding to the T1 duration in Figure 7(b)).

[0202] For example, the process of the first device performing the backoff based on the second information corresponding to the first device is shown in Figure 7(b) or Figure 7(c).

[0203] As shown in Figure 7(b), at time #1, the first device listens to channel #1 and the state is busy; at time #2, the first device listens to channel #1 and the state is idle. After the first device maintains this state for a period of time (such as AIFS), it starts the backoff process at time #3; at time #4, the value of the backoff counter is 0, the first device completes the backoff process, and the first device sends a data frame.

[0204] Alternatively, as shown in Figure 7(c), the first device listens to channel #1 and it is busy; at time #2, the first device listens to channel #1 and it is idle. The first device holds this state for a period of time (e.g., AIFS) and then starts the backoff process at time #3; at time #4, the first device listens to channel #1 and it is busy. The first device freezes the remaining backoff time until the first device listens to channel #1 and it is idle. The first device holds this state for a period of time (e.g., AIFS) and then continues the backoff process; at time #5, the backoff counter value is 0, the first device completes the backoff process, and the first device sends a data frame.

[0205] Optionally, the method further includes: the first device sending the second information corresponding to the second device to the second device.

[0206] That is, if the expected backoff time information of the second device conflicts with the expected backoff time information of the first device, the first device can send the adjusted backoff time information corresponding to the second device to the second device, so that the second device can perform the backoff process based on the adjusted backoff time information. The second information corresponding to the second device is the same as the second information corresponding to the first device, and will not be described again.

[0207] In this case, the first device may not adjust its expected backoff time, or in other words, the backoff time information to be used by the first device is the expected backoff time information. The first device may perform backoff based on the second information corresponding to the first device, or it may perform backoff based on the expected backoff time information of the first device, for example, as shown in Figure 7(a).

[0208] Table 4 shows an example of the second information sent by the first device.

[0209] Table 4

[0210] Table 5 shows another example of the second information sent by the first device.

[0211] Table 5

[0212] In summary, when the expected backoff time information of the second device conflicts with that of the first device, the first device may adjust only its own expected backoff time information, for example, by increasing or decreasing the expected remaining backoff time slots. The first device may also adjust only the expected backoff time information of the second device, for example, by increasing or decreasing the expected remaining backoff time slots. Alternatively, the first device may adjust both its own and the second device's expected backoff time information simultaneously, for example, by increasing the expected remaining backoff time slots of the first device and decreasing the expected remaining backoff time slots of the second device. The above examples of the first device adjusting its expected backoff time information are merely illustrations; specific adjustment methods can be found in the description above.

[0213] Optionally, if the first device receives information #2 from the second device, and information #2 includes at least one of the following: statistical values ​​of the second device's failure to send data frames during time period #1, and the duration corresponding to time period #2 (refer to the description in S610), the first device may also determine whether to send a second message to the second device based on information #2.

[0214] For example, if it is determined that the statistical value of data frame transmission failures of the second device within time period #1 is greater than threshold #1, it is determined that second information will be sent to the second device. As another example, if it is determined that the duration corresponding to time period #2 is greater than threshold #2, it is determined that second information will be sent to the second device. The thresholds #1 and #2 can be referred to in the description in S610.

[0215] Optionally, if at least one of the devices contains other devices whose expected backoff time information conflicts with that of the second device, the first device may also adjust the expected backoff time information of the other devices.

[0216] For example, if the remaining backoff time information of the third device conflicts with the remaining backoff time information of the second device, the first device may send its corresponding second information to at least one of the second and third devices.

[0217] It should be understood that the first device can also determine whether to send corresponding second information to other devices besides the second and third devices. The specific process is similar to the process by which the first device sends the second information to the second and / or third devices, and will not be described in detail here.

[0218] That is, the first device can be used to adjust the backoff time information of the at least one device, that is, to adjust the expected backoff time information to the backoff time information to be used, thereby reducing the air interface collision probability when the device sends data frames and reducing data transmission latency.

[0219] It should be understood that in this application, if the first device is a third-party device, step S620 may not be performed, i.e., the third-party device does not perform backoff. In this case, the first device can determine whether the expected backoff time information corresponding to each of the at least two devices needs to be adjusted based on the expected backoff time information received from each device. For the specific determination method, refer to the description of the first device determining whether there is a conflict between the backoff time information of the devices. And if there are devices with conflicting expected backoff time information among the at least two devices (e.g., the second device and the third device), the first device sends the adjusted backoff time information to at least one of the second device and the third device.

[0220] Figures 8 and 9 are schematic flowcharts of communication methods 800 and 900 provided in this application, respectively. Methods 800 and 900 are illustrated using the example of a first device being an MFU, a second device being an SFU#1, and a third device being an SFU#2. Methods 800 and 900 can be considered as specific implementations of methods 500 and 600.

[0221] As shown in Figure 8, the method 800 includes the following steps.

[0222] Capability negotiation takes place between S801, MFU, SFU#1, and SFU#2.

[0223] That is, MFU, SFU#1, and SFU#2 negotiate whether each device supports the subsequent steps of this method.

[0224] For example, SFU#1 and SFU#2 respectively send their corresponding time period #2 to MFU (refer to time period #2 above).

[0225] Co-EDCA configuration for S802, MFU, SFU#1, and SFU#2.

[0226] Co-EDCA can be understood as the EDCA mechanism corresponding to the information in the embodiments of this application.

[0227] For example, the Co-EDCA configuration can configure MFU, SFU#1, and SFU#2 to execute the EDCA mechanism according to the information in the embodiments of this application.

[0228] S803, SFU#1 sends a conflict statistics report to MFU (i.e., the conflict statistics report corresponding to SFU#1, an example of the first statistics information).

[0229] S804, SFU#2 sends a conflict statistics report to MFU (i.e., the conflict statistics report corresponding to SFU#2, an example of the first statistics information).

[0230] For details of the aforementioned conflict statistics report, please refer to the description in S510.

[0231] S805, MFU determines the adjusted EDCA parameter set.

[0232] For example, the MFU determines the EDCA parameter set corresponding to SFU#1 based on the conflict statistics report of SFU#1. The specific determination method is described in S520.

[0233] For example, the MFU determines not to adjust the EDCA parameter set corresponding to SFU#2 based on the conflict statistics report of SFU#2. The specific determination method is described in S520.

[0234] S806, MFU indicates the adjusted EDCA parameter set to SFU#1 (an example of the second information).

[0235] S807, SFU#1 accesses the channel based on the adjusted EDCA parameter set.

[0236] For specific details, please refer to the method of accessing the channel using the EDCA mechanism.

[0237] The conflict statistics report sent by SFU can adopt the message format shown in Table 6 below:

[0238] Table 6

[0239] Not all parameters in the above message format need to be sent to the MFU. The SFU can select one or more parameters to report as needed. For example, the statistical report sent by the SFU may only include BE queue statistics parameters or SFU air interface duty cycle parameters.

[0240] In addition, statistical information from the four queues—BE queue statistics, BK queue statistics, VI queue statistics, and VO queue statistics—can be sent to one or more of them as needed.

[0241] In addition, the equipment surrounding the SFU includes other SFUs, MFUs, STAs, and other equipment in the FTTR network.

[0242] The length values ​​of the fields in the above message format are just an example; SFU can adjust them as needed.

[0243] As shown in Figure 9, the method 900 includes the following steps.

[0244] Capability negotiation takes place between S901, MFU, SFU#1, and SFU#2.

[0245] That is, MFU, SFU#1, and SFU#2 negotiate whether each device supports the subsequent steps of this method.

[0246] For example, SFU#1 and SFU#2 respectively send their corresponding time period #2 to MFU (refer to time period #2 above).

[0247] Co-EDCA configuration for S902, MFU, SFU#1, and SFU#2.

[0248] Co-EDCA can be understood as the EDCA mechanism corresponding to the information in the embodiments of this application.

[0249] For example, the Co-EDCA configuration can configure MFU, SFU#1, and SFU#2 to execute the EDCA mechanism according to the information in the embodiments of this application.

[0250] S903, SFU#1 sends backoff time information to MFU (i.e., the expected backoff time information corresponding to SFU#1, an example of the first information).

[0251] S904, SFU#2 sends backoff time information to MFU (i.e., the expected backoff time information corresponding to SFU#2, an example of the first information).

[0252] For details regarding the expected retreat time, please refer to the description in S610.

[0253] S905, MFU confirms the adjusted retreat time information.

[0254] For example, the MFU determines to adjust the expected backoff time information corresponding to SFU#1 based on the conflict between the expected backoff time information of SFU#1 and SFU#2, or determines to adjust the expected backoff time information corresponding to SFU#2, or determines to adjust the expected backoff time information corresponding to both SFU#1 and SFU#2. The specific determination method is described in S620.

[0255] S906, MFU instructs SFU#1 on the adjusted expected backoff time information (an example of the second information).

[0256] S907, SFU#1 performs the backoff process based on the adjusted expected backoff time information.

[0257] It should be understood that methods 800 and 900 are illustrated using an MFU as the first device, but the first device can also be a third-party device, which is not limited in this application.

[0258] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 1 to 9. The apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 10 and 11. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0259] Figures 10 and 11 are schematic diagrams of the communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of the terminal or base station in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be a first device, a second device, or a third device, or it can be a module (such as a chip) applied to the first device, the second device, or the third device.

[0260] As shown in Figure 10, the communication device 2000 includes a transceiver unit 2020. Optionally, the communication device 2000 also includes a processing unit 2010. The communication device 2000 is used to implement the functions of the first device, the second device, or the third device in the method embodiments shown in Figures 5 and 6 above.

[0261] When the communication device 2000 is used to implement the function of the first device in the method embodiment shown in Figures 5 and 6: the transceiver unit 2020 is used to: receive first information from each of at least one device, the first information indicating a first duration corresponding to each device, the first duration being the expected backoff duration; the processing unit 2010 is used to: perform backoff based on second information corresponding to the first device, the second information corresponding to the first device being determined based on the first information corresponding to each device, the second information indicating a second duration, the second duration being the backoff duration to be used.

[0262] When the communication device 2000 is used to implement the function of the second device in the method embodiment shown in Figures 5 and 6: the transceiver unit 2020 is used to: send first information to the first device, the first information indicating a first duration corresponding to the second device, the first duration being the expected backoff duration; receive second information from the first device, the second information indicating a second duration corresponding to the second device, the second duration being the backoff duration to be adopted, the first duration being different from the second duration; the processing unit 2010 is used to: perform backoff based on the second information.

[0263] For a detailed description of the functions performed by the processing unit 2010 and the transceiver unit 2020, please refer to the relevant description in the method 500 shown in Figures 5 and 6.

[0264] As shown in Figure 11, the communication device 3000 includes a processor 3010 and an interface circuit 3020. The processor 3010 and the interface circuit 3020 are coupled together. It is understood that the interface circuit 3020 can be a transceiver or an input / output interface. Optionally, the communication device 3000 may also include a memory 3030 for storing instructions executed by the processor 3010, or storing input data required by the processor 3010 to execute instructions, or storing data generated after the processor 3010 executes instructions. Sometimes, the interface circuit 3020 can also be understood as part of the processor 3010, in which case the communication device 3000 includes the processor 3010.

[0265] When the communication device 3000 is used to implement the methods shown in FIG5 and FIG6, the processor 3010 is used to implement the functions of the processing unit 2010, and the interface circuit 3020 is used to implement the functions of the transceiver unit 2020.

[0266] When the aforementioned communication device is a chip applied to the first device, the chip implements the functions of the first device in the above method embodiments. The chip receives information from the second or third device, which can be understood as the information being first received by other modules (such as an RF module or antenna) in the first device, and then sent to the chip by these modules. The chip sends information to the second or third device, which can be understood as the information being first sent to other modules (such as an RF module or antenna) in the first device, and then sent to the second or third device by these modules.

[0267] When the aforementioned communication device is a chip applied to the second device, the chip implements the functions of the second device in the above method embodiments. The chip receives information from the first device, which can be understood as the information being first received by other modules (such as an RF module or antenna) in the second device, and then sent to the chip by these modules. The chip sends information to the first device, which can be understood as the information being first sent to other modules (such as an RF module or antenna) in the second device, and then sent to the first device by these modules.

[0268] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0269] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0270] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0271] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0272] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0273] In this application, "predefined" can be achieved by pre-storing corresponding codes, tables or other means that can be used to indicate relevant information in the device, and this application does not limit the specific implementation method.

[0274] It should be understood that in the various embodiments of this application, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above processes does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0275] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0276] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0277] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0278] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0279] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0280] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0281] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A communication method, characterized in that, Applied to a first device, the method includes: Receive first information from each of at least one device, the first information indicating a first duration for each device, the first duration being the expected backoff duration; The backoff is performed based on the second information corresponding to the first device. The second information corresponding to the first device is determined based on the first information corresponding to each device. The second information indicates a second duration, which is the duration to be used for backoff. The method according to claim 1, characterized in that, The at least one device includes a second device, wherein the first duration corresponding to the second device is the same as the first duration corresponding to the first device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the first device is less than a first threshold, and the method further includes: The first duration corresponding to the first device is adjusted to the second duration corresponding to the first device, and the second duration corresponding to the first device is different from the first duration corresponding to the first device. The method according to claim 1, characterized in that, If the first duration corresponding to each device is different from the first duration corresponding to the first device, or if the difference between the first duration corresponding to each device and the first duration corresponding to the first device is greater than or equal to a first threshold, then the second duration corresponding to the first device is the first duration corresponding to the first device. The method according to claim 1, characterized in that, The at least one device includes a second device, wherein the first duration corresponding to the second device is the same as the first duration corresponding to the first device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the first device is less than a first threshold, and the method further includes: Send the second information corresponding to the second device to the second device. The second information corresponding to the second device indicates the second duration corresponding to the second device. The second duration corresponding to the second device is different from the first duration corresponding to the second device. The method according to claim 1, characterized in that, The at least one device includes a second device and a third device, wherein the first duration corresponding to the second device is the same as the first duration corresponding to the third device, or the difference between the first duration corresponding to the second device and the first duration corresponding to the third device is less than a first threshold, and the method further includes: Send the second information corresponding to the second device to the second device, wherein the second duration corresponding to the second device is different from the first duration corresponding to the second device; and / or, Send the second information corresponding to the third device to the third device, wherein the second duration corresponding to the third device is different from the first duration corresponding to the third device; The second duration corresponding to the second device is different from the second duration corresponding to the third device. The method according to any one of claims 1 to 5, characterized in that, The first information includes any one of the following: The first indication is the expected end time of the retreat; Wherein, the first indication information is used to determine the expected backoff end time, the first indication information includes the end time of the first channel being occupied and a first parameter set, the first channel is used to transmit data after the backoff is performed, and the first parameter set includes the number of arbitration frame gaps and a first random backoff value. The method according to any one of claims 1 to 6, characterized in that, The second information includes any one of the following: The second instruction is the time when the retreat will end; The second indication information is used to determine the end time of the backoff to be adopted, and the second indication information includes a second random backoff value. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Receive a third indication message from each of the devices, the third indication message indicating the statistical value of data transmission failures of each device within a first time period. The method according to claim 8, characterized in that, The method further includes: Based on the relationship between the statistical value of data transmission failures of each device and the second threshold, it is determined whether to send the second information corresponding to each device to each device. The method according to any one of claims 1 to 9, characterized in that, The method further includes: Receive a fourth indication information from each of the devices, the fourth indication information indicating a first time difference between a first time and a second time, wherein the first time is the time when each device is expected to send the first information corresponding to each device or the current time, and the second time is the end time when the first channel is occupied or the expected backoff start time or the expected backoff start time. The method according to claim 10, characterized in that, The method further includes: Based on the relationship between the first time difference and the third threshold corresponding to each device, it is determined whether to send the second information corresponding to each device to each device. A communication method, characterized in that, Applied to a second device, the method includes: Send a first message to the first device, the first message indicating a first duration corresponding to the second device, the first duration being the expected duration for backoff; Receive second information from the first device, the second information indicating a second duration corresponding to the second device, the second duration being the duration to be used for backoff, and the first duration being different from the second duration; The backoff is executed based on the second information. The method according to claim 12, characterized in that, The first information includes any one of the following information corresponding to the second device: The first indication is the expected end time of the retreat; The first indication information is used to determine the expected backoff end time. The first indication information includes the end time of the first channel being occupied and a first parameter set. The first channel is used for the second device to transmit data after the backoff. The first parameter set includes the number of arbitration frame gaps corresponding to the second device and a first random backoff value. The method according to claim 13, characterized in that, The second information includes any one of the following information corresponding to the second device: The second instruction is the time when the retreat will end; The second indication information is used to determine the end time of the backoff to be adopted. The second indication information includes a second random backoff value corresponding to the second device, and the second random backoff value is different from the first random backoff value. The method according to any one of claims 12 to 14, characterized in that, The method further includes: A third indication message is sent to the first device. The third indication message indicates the statistical value of the second device's failure to send data within a first time period. The relationship between the statistical value of the second device's failure to send data and the second threshold is used to determine whether to send the second message. The method according to any one of claims 12 to 15, characterized in that, Sending the first information to the first device includes: Based on the relationship between the statistical value of the second device's data transmission failures during the first time period and the second threshold, the first information is sent to the first device. The method according to any one of claims 12 to 16, characterized in that, The method further includes: Send a fourth indication information to the first device, the fourth indication information indicating a first time difference between a first time and a second time, wherein the first time is the time when each device is expected to send the first information corresponding to each device or the current time, and the second time is the end time when the first channel is occupied or the expected backoff start time or the expected backoff start time. The method according to any one of claims 12 to 16, characterized in that, Sending the first information to the first device includes: The first information is sent to the first device based on the relationship between the first time difference and the third threshold. The first time difference is the time difference between the first moment and the second moment. The first moment is the moment when each device is expected to send the first information corresponding to each device or the current moment. The second moment is the end moment when the first channel is occupied or the expected backoff start moment or the expected backoff start moment. A communication device, characterized in that, include: The unit is used to perform the method as described in any one of claims 1 to 11, or includes a unit used to perform the method as described in any one of claims 12 to 18. A communication device, characterized in that, include: A transceiver and a processor, the transceiver being configured to receive a signal and transmit the signal to the processor or another communication device other than the communication device, the processor being configured to perform the method as claimed in any one of claims 1 to 11, or to perform the method as claimed in any one of claims 12 to 18. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 11. A computer program product, characterized in that, Includes a computer program that, when run, implements the method as described in any one of claims 1 to 11, or implements the method as described in any one of claims 12 to 18.

Citation Information

Patent Citations

  • Scheduling method, system and device

    CN116684981A

  • Cooperative spatial multiplexing method and device based on FTTR and readable medium

    CN117835442A

  • Methods and apparatus to handle enhanced distributed channel access parameters

    US20190075575A1

  • Slave device, master device, communication system, and data transmission method

    WO2024192994A1