Communication method and communication apparatus

Abstract

The present application relates to the field of optical communication. Provided are a communication method and a communication apparatus. In the communication method and the communication apparatus provided in the present application, a master FTTR unit indicates, to a slave FTTR unit, whether the slave FTTR unit is required to synchronously transmit a message with the other FTTR units, such that the slave FTTR unit learns whether its message transmission mode is synchronous or asynchronous. Thus, the slave FTTR unit can be controlled to transmit the message in an appropriate mode, so as to avoid signal interference with the other slave FTTR units, thereby helping to improve the communication performance of a terminal.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411564954.5, filed with the State Intellectual Property Office of China on November 4, 2024, entitled "Communication Method and Communication Device", and to Chinese Patent Application No. 202510049296.4, filed with the State Intellectual Property Office of China on January 9, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of optical communications, and more particularly to communication methods and communication devices. Background Technology

[0003] Fiber to the room (FTTR) is a solution that brings fiber optic cables to every room, enabling home networks to achieve ultra-high contracted bandwidth and cover every corner of the home, thereby meeting user needs.

[0004] FTTR networks typically consist of multiple FTTR units (FUs). These FUs provide communication services to terminals via wireless local area networks (WLANs). If these multiple FTTR units are located in the same physical space and operate on the same wireless frequency band, parallel data transmission between them can cause signal interference in overlapping areas, thus affecting the terminal's communication performance. Summary of the Invention

[0005] This application provides a communication method and a communication device that help avoid mutual interference between multiple FTRR devices in the same frequency band, thereby improving the communication performance of the terminal.

[0006] Firstly, this application provides a communication method that can be executed by a communication device. The communication device can be a communication equipment, or one or more of the following: a module, apparatus, processor, chip, or circuit configured for use in or in conjunction with a communication device. For example, this communication device includes an FTTR device, which can be referred to as a main FTTR device.

[0007] This communication method includes: sending coordination information, which includes synchronization marker information, indicating whether a first FTTR device needs to synchronize message transmission with other FTTR devices, wherein the first FTTR device and the other FTTR devices operate on the same frequency band; and sending coordination information to the first FTTR device.

[0008] In some possible implementations, the first FTTR device and other FTTR devices can be referred to as slave FTTR devices.

[0009] In some possible implementations, not needing to send messages synchronously can be understood as sending messages asynchronously.

[0010] In this communication method, the master FTTR device indicates to the slave FTTR device whether the slave FTTR device needs to send messages synchronously with other FTTR devices. This allows the slave FTTR device to know whether it is sending messages synchronously or asynchronously, thereby controlling the slave FTTR device to send messages in a reasonable manner to avoid signal interference with other slave FTTR devices and helping to improve the communication performance of the terminal.

[0011] In some possible implementations, when the synchronization marker information indicates that the first FTTR device needs to synchronize the transmission of messages with other FTTR devices, the coordination information also includes synchronization type information, which indicates: transmitting messages according to the start transmission timestamp, transmitting messages based on the time when the synchronization message is triggered, or transmitting messages based on the time when the synchronization message is triggered and the synchronization message is triggered by other synchronization messages.

[0012] When the master FTTR device instructs the first FTTR device to send messages synchronously with other FTTR devices, it also instructs the first FTTR device on the type of messages to be sent synchronously with other FTTR devices, so that the first FTTR device can accurately know the method to achieve synchronous message sending, thereby accurately achieving synchronous message sending.

[0013] In some possible implementations, when the synchronization type information indicates that a message is sent according to the start time stamp, the coordination information also includes an indication of the start time stamp.

[0014] In this implementation, the master FTTR device instructs the slave FTTR device to start sending a timestamp, enabling the slave FTTR device to achieve synchronized message transmission in a simple way.

[0015] In some possible implementations, when the synchronization type information indicates that a message is sent based on the time triggered by the first synchronization message, or when the synchronization type information indicates that a message is sent based on the time triggered by the first synchronization message and the first synchronization message is triggered by the second synchronization message, the coordination information also includes synchronization message sending indication information, which indicates whether the first FTTR device needs to actively send a synchronization message.

[0016] In this implementation, the method specified by the master FTTR device for synchronous message transmission via synchronization messages, and the sending behavior of the slave FTTR device for synchronization messages, help the slave FTTR device and other FTTR devices to accurately coordinate and achieve synchronous message transmission.

[0017] In some possible implementations, this communication method further includes: determining cooperative space multiplexing scheduling information, which includes: the transmission power of the first FTTR device sending a message to the first terminal, wherein the first FTTR device is one of multiple FTTR devices operating in the same frequency band; and sending the cooperative space multiplexing scheduling information.

[0018] In some possible implementations, these multiple FTTR devices can be referred to as slave FTTR devices.

[0019] By implementing the communication method provided in the first aspect, the master FTTR device indicates cooperative spatial multiplexing scheduling information to the slave FTTR device. When the slave FTTR device supports receiving cooperative spatial multiplexing scheduling information and sending messages according to the cooperative spatial multiplexing scheduling information, it can control or adjust the power of the slave FTTR device sending messages to the terminal in the same frequency band, that is, control or adjust the signal coverage range of the slave FTTR device. This helps to control the difference between the signal-to-noise ratio of the signal received by the terminal from the first FTTR device and the signal-to-noise ratio of the signal received by the terminal from other FTTR devices in the same frequency band, so that the difference can enable the terminal to correctly interpret the signal received by the terminal from the first FTTR device, thereby helping to avoid the terminal being interfered with by the signals of other FTTR devices, and thus helping to improve the communication performance of the terminal.

[0020] In some possible implementations, the cooperative space reuse scheduling information also includes at least one of the following: the identifier of the first FTTR device, the identifier corresponding to the cooperative space reuse scheduling information, the operating frequency band, the identifier of the first terminal, the TID to be transmitted by the first terminal, the effective time of the transmission power, the transmission rate of the first terminal, the indication information of whether the first FTTR device needs to synchronously transmit messages with other FTTR devices among the plurality of FTTR devices, the synchronization type information when the first FTTR synchronously transmits messages, the start transmission timestamp of the first FTTR device synchronously transmitting messages, the indication information of whether the first FTTR device needs to actively transmit synchronization messages, the number of other FTTR devices among the plurality of FTTR devices, or, the identifier of other FTTR devices among the plurality of FTTR devices.

[0021] The collaborative space reuse scheduling information includes the identifier of the first FTTR device, which helps the master FTTR device to accurately send the collaborative space reuse scheduling information to the first FTTR device.

[0022] The cooperative space multiplexing scheduling information includes an identifier corresponding to the cooperative space multiplexing scheduling information, which helps the master FTTR device and the first FTTR device to identify which cooperative space multiplexing scheduling information the currently transmitted cooperative space multiplexing scheduling information belongs to, so as to distinguish it from the cooperative space multiplexing scheduling information sent at other times or in other scenarios, thereby enabling the accurate use of the cooperative space multiplexing scheduling information transmitted in this instance.

[0023] The cooperative space reuse scheduling information includes the operating frequency band, which helps the master FTTR device and the first FTTR device to align which operating frequency band the current cooperative space reuse is targeting. This allows for more accurate reduction of interference between FTTR devices targeting that operating frequency band, thereby accurately improving the communication performance of the terminal.

[0024] The collaborative space reuse scheduling information includes the identifier of the first terminal, which helps the first FTTR device to clearly identify which terminal the currently indicated transmission power is for, thereby accurately improving the communication performance of the terminal.

[0025] The collaborative space reuse scheduling information includes the TID to be transmitted by the first terminal, which helps the first FTTR device to clearly identify which TIDs of the terminal the currently indicated transmission power is for, thereby accurately improving the communication performance of the terminal.

[0026] The collaborative space multiplexing scheduling information includes the effective time of the transmission power, which helps the first FTTR device avoid using the transmission power during the invalid time. This can prevent the first FTTR device from causing signal interference with other FTTR devices, and thus prevent the communication performance of the terminal from being affected.

[0027] The collaborative spatial multiplexing scheduling information includes the transmission rate of the first terminal, which helps the first FTTR device complete the transmission of the first terminal's message within the effective time of the transmission power, thereby avoiding the impact on the communication performance of the first terminal.

[0028] The collaborative space reuse scheduling information includes indication information on whether the first FTTR device needs to send messages synchronously with other FTTR devices among the multiple FTTR devices. This helps the first FTTR device to accurately know how it sends messages, thereby avoiding interference with other FTTR devices through a reasonable message sending method, and thus improving the communication performance of the first terminal.

[0029] The collaborative space multiplexing scheduling information includes synchronization type information when the first FTTR synchronously transmits messages. This helps the first FTTR accurately know its own synchronization transmission method, thereby avoiding interference with other FTTR devices through a reasonable synchronization transmission method, and thus improving the communication performance of the first terminal.

[0030] The collaborative space reuse scheduling information includes the start timestamp of the first FTTR device's synchronous transmission of messages with other FTTR devices, enabling the first FTTR device to achieve synchronous transmission of messages with other FTTR devices in a more direct or simpler way.

[0031] The collaborative space reuse scheduling information includes an indication of whether the first FTTR device needs to actively send a synchronization message, enabling the first FTTR device to more flexibly achieve synchronized message transmission with other FTTR devices.

[0032] The collaborative space reuse scheduling information includes the number of other FTTR devices among multiple FTTR devices or the identifiers of other FTTR devices among multiple FTTR devices. This helps the first FTTR device know which FTTR devices it is working with, such as accurately knowing which FTTR devices to send synchronization messages to, or which FTTR devices to respond to when it receives synchronization messages. This helps to avoid interference and thus helps to improve the communication performance of the terminal.

[0033] In some possible implementations, the synchronization type includes: sending a message according to the start sending timestamp, sending a message based on the time triggered by the synchronization message, or sending a message based on the time triggered by the synchronization message and said synchronization message is triggered by other synchronization messages.

[0034] In some possible implementations, this communication method further includes: receiving cooperative space multiplexing result information, which includes: the number of data units transmitted by the first FTTR device using the transmit power, and / or, the packet error rate of the data units transmitted by the first FTTR device using the transmit power.

[0035] In this implementation, the master FTTR device learns the cooperative space multiplexing result information, which helps the master FTTR device to adjust or update one or more pieces of information in the cooperative space multiplexing scheduling information of the slave FTTR device based on the result information. This helps to more reasonably avoid interference between slave FTTR devices and more reasonably improve the communication performance of the terminal.

[0036] In some possible implementations, the collaborative space reuse result information also includes: the identifier of the first FTTR device, and / or, the identifier corresponding to the collaborative space reuse result information, and the identifier corresponding to the collaborative space reuse scheduling information and the identifier corresponding to the collaborative space reuse result information are associated.

[0037] The collaborative space multiplexing result information includes the identifier of the first FTTR device, which helps the master FTTR device to know that the collaborative space multiplexing result information was reported by the first FTTR device. Therefore, the master FTTR device can accurately adjust or update the collaborative space multiplexing scheduling information of the first FTTR device based on the collaborative space multiplexing result, thereby helping to avoid interference between the first FTTR device and other FTTR devices, and ultimately improving the communication performance of the terminal.

[0038] The collaborative space reuse result information includes the identifier corresponding to the collaborative space reuse result information, and the identifier corresponding to the collaborative space reuse scheduling information is associated with the identifier corresponding to the collaborative space reuse result information. This helps the master FTTR device to associate the collaborative space reuse scheduling information with the corresponding collaborative space reuse result information, and more accurately adjust or update the collaborative space reuse scheduling information of the first FTTR device based on the associated collaborative space reuse scheduling information and collaborative space reuse result information.

[0039] As an example, the identifier corresponding to the collaborative space reuse scheduling information and the identifier corresponding to the collaborative space reuse result information are related, including: the identifier corresponding to the collaborative space reuse scheduling information and the identifier corresponding to the collaborative space reuse result information are the same identifier.

[0040] In some possible implementations, the communication method further includes: receiving cooperative space multiplexing related information, which includes downlink transmission information of each terminal in at least one terminal, wherein the at least one terminal is a terminal communicating with a first FTTR device.

[0041] In this communication method, since the cooperative space multiplexing information includes the downlink transmission information of the terminal, the master FTTR can obtain more reasonable cooperative space multiplexing scheduling information based on the cooperative space multiplexing information, thereby avoiding interference between FTTR devices with higher efficiency or higher accuracy, and thus improving the communication performance of the terminal with higher efficiency or higher accuracy.

[0042] In some possible implementations, the downlink transmission information includes at least one of the following: the identifier of each terminal, the transmission rate of each terminal, the number of TIDs with data in each terminal's TID, or the transmission information of each TID with data in each terminal's TID.

[0043] Based on this information, the master FTTR can obtain more reasonable cooperative spatial multiplexing scheduling information, thereby avoiding interference between FTTR devices with higher efficiency or accuracy, and thus improving the communication performance of the terminal with higher efficiency or accuracy.

[0044] In some possible implementations, the transmission information of each TID includes at least one of the following: total buffer size, number of data units, head-of-queue latency, and size of each data unit.

[0045] Based on this information, the master FTTR can obtain more reasonable cooperative spatial multiplexing scheduling information, thereby avoiding interference between FTTR devices with higher efficiency or accuracy, and thus improving the communication performance of the terminal with higher efficiency or accuracy.

[0046] In some possible implementations, the information related to collaborative spatial reuse also includes at least one of the following: the identifier of the first FTTR device, its operating frequency band, or the number of the at least one terminal.

[0047] Based on this information, the master FTTR can obtain more reasonable cooperative spatial multiplexing scheduling information, thereby avoiding interference between FTTR devices with higher efficiency or accuracy, and thus improving the communication performance of the terminal with higher efficiency or accuracy.

[0048] In some possible implementations, before receiving information related to collaborative space reuse, the communication method further includes: sending collaborative space reuse information collection information, which is used to trigger the first FTTR device to report collaborative space reuse information.

[0049] In this implementation, the master FTTR device can trigger the first FTTR device to report collaborative space reuse information based on demand, which can avoid resource waste caused by the first FTTR device arbitrarily reporting collaborative space reuse information.

[0050] In some possible implementations, the information collected for collaborative space reuse includes: the identifier of the at least one terminal, and / or, the grouping information of the at least one terminal.

[0051] The collaborative space reuse information collection method can flexibly indicate the terminals that need to report uplink and downlink transmission information by using the identifier of each terminal, which can improve the application flexibility of this communication method and expand the application scenarios.

[0052] Cooperative space reuse information collection uses terminal packet information to indicate terminals that need to report downlink transmission information, which can save the overhead of indication information.

[0053] In some possible implementations, this communication method further includes: receiving cooperative space multiplexing capability information, which is used to indicate whether the first FTTR device supports at least one of the following capabilities: actively reporting cooperative space multiplexing related information, responding to the instruction of the master FTTR device to report cooperative space multiplexing related information, synchronously sending messages, asynchronously sending messages, or actively sending synchronization messages.

[0054] In this communication method, the master FTTR can obtain more reasonable collaborative space multiplexing information collection information or collaborative space multiplexing scheduling information based on the collaborative space multiplexing capability information of the first FTTR device. This can avoid interference between FTTR devices with higher efficiency or higher accuracy, thereby improving the communication performance of the terminal with higher efficiency or higher accuracy.

[0055] In some possible implementations, the collaborative spatial reuse capability information may also include: the identifier of the first FTTR device, and / or, the operating frequency band.

[0056] The collaborative space reuse capability information includes the identifier of the first FTTR device, which helps the master FTTR device to accurately know that the collaborative space reuse capability information is the collaborative space reuse capability information of the first FTTR device, thereby enabling it to accurately collect relevant information of the first FTTR device or accurately schedule the first FTTR device.

[0057] The cooperative spatial reuse capability information includes the operating frequency band, which helps the master FTTR device determine which operating frequency band of the first FTTR device the cooperative spatial reuse capability information belongs to. This allows for more accurate reduction of interference between FTTR devices targeting that operating frequency band, thereby accurately improving the communication performance of the terminal.

[0058] In some possible implementations, before receiving the cooperative space reuse capability information, the communication method further includes: sending cooperative space reuse capability request information, which is used to instruct the first FTTR device to report the cooperative space reuse capability information.

[0059] In this implementation, the master FTTR device can trigger the first FTTR device to report collaborative space reuse capability information based on demand, which can avoid resource waste caused by the first FTTR device arbitrarily reporting collaborative space reuse capability information.

[0060] In some possible implementations, the collaborative space reuse capability request information may also include: the identifier of the first FTTR device, and / or, the operating frequency band.

[0061] The collaborative space reuse capability request information includes the identifier of the first FTTR device, which helps the master FTTR device to accurately send the collaborative space reuse capability request information to the first FTTR device.

[0062] The cooperative spatial reuse capability request information includes the operating frequency band, which helps the first FTTR device to report the accurate cooperative spatial reuse capability of the operating frequency band according to the instructions of the master FTTR device. This allows for more accurate reduction of interference between FTTR devices for that operating frequency band, thereby accurately improving the communication performance of the terminal.

[0063] Secondly, this application provides a communication method that can be executed by a communication device. The communication device can be a communication equipment, or one or more of the following: a module, apparatus, processor, chip, or circuit configured for use in or in conjunction with a communication device. For example, this communication device includes an FTTR device, which can be referred to as a slave FTTR device or a first FTTR device.

[0064] This communication method includes: receiving coordinated spatial multiplexing scheduling information, which includes: the transmission power of a first fiber-to-the-room FTTR device sending a message to a first terminal, wherein the first FTTR device is one of multiple FTTR devices operating in the same frequency band; and sending a message to the first terminal according to the coordinated spatial multiplexing scheduling information.

[0065] In some possible implementations, the cooperative space reuse scheduling information also includes at least one of the following: the identifier of the first FTTR device, the identifier corresponding to the cooperative space reuse scheduling information, the operating frequency band, the identifier of the first terminal, the TID to be transmitted by the first terminal, the effective time of the transmission power, the transmission rate of the first terminal, the indication information of whether the first FTTR device needs to synchronize and transmit messages with other FTTR devices among the plurality of FTTR devices, the synchronization type information when the first FTTR device synchronizes and transmits messages with other FTTR devices, the start transmission timestamp of the first FTTR device synchronizes and transmits messages with other FTTR devices, the indication information of whether the first FTTR device needs to actively transmit synchronization messages, the number of other FTTR devices among the plurality of FTTR devices, or the identifier of other FTTR devices among the plurality of FTTR devices.

[0066] In some possible implementations, this communication method further includes: sending cooperative spatial multiplexing result information, which includes: the number of data units transmitted by the first FTTR device using the transmission power, and / or, the packet error rate of the data units transmitted by the first FTTR device using the transmission power.

[0067] In some possible implementations, the collaborative space reuse result information also includes: the identifier of the first FTTR device, and / or, the identifier corresponding to the collaborative space reuse result information, and the identifier corresponding to the collaborative space reuse scheduling information and the identifier corresponding to the collaborative space reuse result information are associated.

[0068] As an example, the identifier corresponding to the collaborative space reuse scheduling information and the identifier corresponding to the collaborative space reuse result information are related, including: the identifier corresponding to the collaborative space reuse scheduling information and the identifier corresponding to the collaborative space reuse result information are the same identifier.

[0069] In some possible implementations, this communication method further includes: receiving acknowledgment information, which is used to indicate that the first terminal has received the message.

[0070] In some possible implementations, this communication method further includes: sending cooperative space multiplexing related information, which includes downlink transmission information of each terminal in at least one terminal, wherein at least one terminal is a terminal communicating with a first FTTR device.

[0071] In this communication method, the first FTTR device sends cooperative space multiplexing-related information to the second FTTR device. When the second FTTR device supports receiving cooperative space multiplexing-related information and can send cooperative space multiplexing scheduling information based on the cooperative space multiplexing-related information, the second FTTR device can send more reasonable cooperative space multiplexing scheduling information based on the cooperative space multiplexing-related information, thereby avoiding signal interference between FTTR devices more efficiently and accurately, and thus improving the communication performance of the terminal more efficiently and accurately.

[0072] In some possible implementations, the downlink transmission information includes at least one of the following: the identifier of each terminal, the transmission rate of each terminal, the number of TIDs with data in each terminal's TID, or the transmission information of each TID with data in each terminal's TID.

[0073] In some possible implementations, the transmission information for each TID includes at least one of the following: total buffer size, number of data units, head-of-queue latency, and size of each data unit.

[0074] In some possible implementations, the information related to collaborative spatial reuse also includes at least one of the following: the identifier of the first FTTR device, its operating frequency band, or the number of the at least one terminal.

[0075] In some possible implementations, before determining the cooperative space reuse-related information, the communication method further includes: receiving cooperative space reuse information collection information, which is used to trigger the first FTTR device to report cooperative space reuse-related information.

[0076] In some possible implementations, the information collected for collaborative space reuse includes: the identifier of the at least one terminal, and / or, the grouping information of the at least one terminal.

[0077] In some possible implementations, this communication method further includes: sending cooperative space multiplexing capability information, which is used to indicate whether the first FTTR device supports at least one of the following capabilities: actively reporting cooperative space multiplexing related information, responding to the instruction of the master FTTR device to report cooperative space multiplexing related information, synchronously sending messages, asynchronously sending messages, or actively sending synchronization messages.

[0078] In this communication method, the first FTTR device sends cooperative space multiplexing capability information to the master FTTR device. When the master FTTR device supports receiving cooperative space multiplexing capability information and can determine cooperative space multiplexing information collection information or cooperative space multiplexing scheduling information more accurately and efficiently based on the cooperative space multiplexing capability information, it can avoid interference between FTTR devices more efficiently or with higher accuracy, thereby improving the communication performance of the terminal more efficiently or with higher accuracy.

[0079] In some possible implementations, the collaborative space reuse capability information may also include: the identifier of the first FTTR device, and / or, the operating frequency band.

[0080] In some possible implementations, before sending the cooperative space reuse capability information, the communication method further includes: receiving cooperative space reuse capability request information, which is used to instruct the first FTTR device to report cooperative space reuse capability information.

[0081] In some possible implementations, the collaborative space reuse capability request information may also include: the identifier of the first FTTR device, and / or, the operating frequency band.

[0082] In some possible implementations, this communication method further includes: receiving coordination information, which includes synchronization tag information, indicating whether the first FTTR device needs to synchronize message transmission with other FTTR devices, wherein the first FTTR device operates on the same frequency band as the other FTTR devices; and transmitting messages according to the coordination information.

[0083] In some possible implementations, when the synchronization marker information indicates that the first FTTR device needs to synchronize the transmission of messages with other FTTR devices, the coordination information also includes synchronization type information, which indicates: transmitting messages according to the start transmission timestamp, transmitting messages based on the time when the synchronization message is triggered, or transmitting messages based on the time when the synchronization message is triggered and the synchronization message is triggered by other synchronization messages.

[0084] In some possible implementations, when the synchronization type information indicates that a message is sent according to the start time stamp, the coordination information also includes an indication of the start time stamp.

[0085] In some possible implementations, the synchronization type information indicates when a message is sent based on the time triggered by the first synchronization message, or indicates when a message is sent based on the time triggered by the first synchronization message and the first synchronization message is triggered by the second synchronization message. The coordination information also includes synchronization message sending indication information, which indicates whether the first FTTR device needs to actively send a synchronization message.

[0086] Thirdly, this application provides a communication device. This communication device may include modules corresponding to each of the methods / operations / steps / actions described in any possible implementation of the first aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0087] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in any possible implementation of the first aspect above, while the processing module is used to perform the processing actions involved in the method described in any possible implementation of the first aspect above.

[0088] In one design, the communication device may be an FTTR device, or a device, module, circuit or chip configured in the FTTR device, or a device that can be used in conjunction with the FTTR device.

[0089] Fourthly, this application provides a communication device. This communication device may include modules corresponding to each of the methods / operations / steps / actions described in any possible implementation of the second aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0090] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in any possible implementation of the second aspect above, while the processing module is used to perform the processing actions involved in the method described in any possible implementation of the second aspect above.

[0091] In one design, the communication device may be an FTTR device, or a device, module, circuit or chip configured in the FTTR device, or a device that can be used in conjunction with the FTTR device.

[0092] Fifthly, this application provides a communication device including a processor, wherein instructions are executed by the processor to cause the method as described in any possible implementation of the first aspect to be implemented.

[0093] Optionally, the communication device may further include a storage medium that stores the instructions executed by the processor.

[0094] In some implementations, the storage medium is integrated with the processor, for example, the storage medium is integrated into the processor.

[0095] In a sixth aspect, this application provides a communication device including a processor, wherein instructions are executed by the processor to cause the method as described in any possible implementation of the second aspect to be implemented.

[0096] Optionally, the communication device may further include a storage medium that stores the instructions executed by the processor.

[0097] In some implementations, the storage medium is integrated with the processor, for example, the storage medium is integrated into the processor.

[0098] In a seventh aspect, this application provides a chip including a processing circuit for running a program or instructions to implement the method as described in any possible implementation of the first aspect.

[0099] Optionally, the chip may further include a memory for storing programs or instructions.

[0100] Optionally, the chip may also include the transceiver circuit, or an input / output interface.

[0101] Eighthly, this application provides a chip including processing circuitry for running programs or instructions to implement methods as described in any possible implementation of the second aspect.

[0102] Optionally, the chip may further include a memory for storing programs or instructions.

[0103] Optionally, the chip may also include the transceiver circuit, or an input / output interface.

[0104] A ninth aspect provides a computer-readable storage medium comprising instructions that, when executed by a processor, cause a method as described in any possible implementation of the first aspect to be implemented.

[0105] In a tenth aspect, this application provides a computer-readable storage medium including instructions that, when executed by a processor, cause the method as described in any possible implementation of the second aspect to be implemented.

[0106] In one aspect, this application provides a computer program product comprising computer program code or instructions that, when executed, cause the method in any possible implementation of the first aspect to be implemented.

[0107] In a twelfth aspect, this application provides a computer program product comprising computer program code or instructions that, when executed, cause the method in any possible implementation of the second aspect to be implemented.

[0108] In a thirteenth aspect, this application provides a communication system for performing the methods described in any possible implementation of the first aspect above and the methods described in any possible implementation of the second aspect above.

[0109] It is understandable that the technical effects in any of the second to thirteenth aspects can be referenced from the technical effects in the first aspect. Attached Figure Description

[0110] Figure 1 is an architecture diagram of a home network provided in an embodiment of this application;

[0111] Figure 2 is a schematic diagram of a topology provided in an embodiment of this application;

[0112] Figure 3 is a flowchart illustrating a communication method according to an embodiment of this application;

[0113] Figure 4 is a schematic diagram of the signal coverage of an FTTR device according to an embodiment of this application;

[0114] Figure 5 is a schematic diagram of the synchronous spatial concurrency process according to an embodiment of this application;

[0115] Figure 6 is a schematic diagram of the asynchronous spatial concurrency process according to an embodiment of this application;

[0116] Figure 7 is a schematic diagram of non-interactive message synchronous transmission according to an embodiment of this application;

[0117] Figure 8 is a schematic diagram of interactive message synchronous transmission according to an embodiment of this application;

[0118] Figures 9 to 14 are schematic flowcharts of the communication method according to embodiments of this application;

[0119] Figure 15 is a schematic diagram of a communication device provided in an embodiment of this application;

[0120] Figure 16 is a schematic diagram of a communication device provided in another embodiment of this application. Detailed Implementation

[0121] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0122] In the description of the embodiments of this application, unless otherwise stated, "a plurality of" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0123] In the description of the embodiments of this application, the terms "first" and "second" are used to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0124] In the description of the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0125] In the description of the embodiments of this application, the terms "information", "signal", "message", "channel", and "signaling" may sometimes be used interchangeably. It should be noted that when their distinctions are not emphasized, their intended meanings are matched.

[0126] In the description of the embodiments of this application, the terms "of", "corresponding (relevant)" and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are matched.

[0127] In the description of the embodiments of this application, the order of the process numbers does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0128] In the description of the embodiments of this application, "preset," "predefined," or "preconfigured" can be implemented by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminals and FUs), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. The one or more memories can be separate settings or integrated into an encoder or decoder, processor, or communication device. The one or more memories can also be partially separate settings and partially integrated into a decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0129] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation.

[0130] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0131] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0132] In this application, when entity A sends information to entity B, it can be either A sending the information directly to B or A sending the information indirectly to B through other entities. Similarly, when entity B receives information from entity A, it can be either entity B receiving the information sent by entity A directly or entity B receiving the information sent by entity A indirectly through other entities.

[0133] It is understood that the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0134] It should be noted that the following embodiments of this application are not limited to home networks; for example, they can also be enterprise networks or factory networks. The example given here is merely a home network scenario and should not be construed as limiting the embodiments of this application.

[0135] For example, referring to FIG1, an embodiment of this application provides an architecture diagram of a home network. As shown in FIG1, the home network includes: a main FTTR unit (MFU), referred to simply as the main FTTR, as shown in FIG1 as main FTTR 101; multiple sub FTTR units (SFU), referred to simply as sub FTTRs, as shown in FIG1 as sub FTTR 102-1 to sub FTTR 102-5; and a terminal device, referred to in FIG1 as terminal 103. The main FTTR 101 is used to connect to the multiple sub FTTRs (including sub FTTR 102-1 to sub FTTR 102-5) respectively.

[0136] In one possible implementation, as shown in Figure 1, the aforementioned home network also includes a connection device (refer to connection device 104 in Figure 1). Optionally, this connection device may be an optical distribution box or an optoelectronic distribution box.

[0137] It is understood that, for ease of explanation, the architecture shown in Figure 1 is used as an example only and should not be construed as limiting the embodiments of this application. For example, the terminal 103 in the above-described home network includes various types of terminal devices deployed in different locations within the home (e.g., different rooms), such as the computer, tablet, robot vacuum cleaner, and virtual reality (VR) glasses shown in Figure 1. Furthermore, the network architecture described above may also include more communication devices or apparatuses.

[0138] For example, referring to Figure 1, when the home network is deployed in a large-scale home (such as a villa) with a large coverage area, the terminal 103 deployed in the home communicates with the main FTTR or the slave FTTR using wireless transmission technology, such as WLAN. However, due to the large coverage area, users experience problems such as insufficient bandwidth and poor network coverage, leading to frequent network lag and severely impacting the user's network experience.

[0139] It is understood that the terminal in the embodiments of this application may be referred to as a station (STA).

[0140] Terminal devices can also be devices that provide voice / data, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, 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 wireless modems, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), devices in a Zigbee network, devices in a LoRa network, Bluetooth slaves, BLE slaves, Wi-Fi stations (STAs), etc.

[0141] To address this issue, FTTR (Fiber to the Room) can be adopted, enabling the home network to achieve ultra-high contracted bandwidth and cover every corner of the home, thereby meeting user needs. Taking the home network shown in Figure 1 as an example, the main FTTR 101 will be connected to multiple secondary FTTRs (including secondary FTTR 102-1 to secondary FTTR 102-5) deployed in different rooms via fiber optic cables.

[0142] In some scenarios, multiple FTTR devices are located in the same physical space and operate on the same radio frequency band. In such scenarios, if these multiple FTTRs transmit data in parallel, they will interfere with each other in areas where their signal coverage overlaps, affecting communication performance.

[0143] In the embodiments of this application, multiple FTTR devices located in the same physical space and operating in the same wireless frequency band transmit data concurrently, which can be referred to as spatial multiplexing or spatial multiplexing concurrency.

[0144] For example, referring to FIG2, an embodiment of this application provides a schematic diagram of a topology, illustrating a typical topology with overlapping signal coverage.

[0145] Referring to Figure 2, this topology includes two FTTR devices, denoted as SFU1 and SFU2. The dashed box on the left represents the signal coverage area of ​​SFU1, and the dashed box on the right represents the signal coverage area of ​​SFU2. As shown in Figure 2, the signal coverage areas of SFU1 and SFU2 overlap. STA1 communicates with SFU1 and is located within this overlapping area.

[0146] The frequency bands of SFU1 and SFU2 overlap, causing mutual interference within their overlapping coverage areas and affecting the communication performance of terminals in those areas. For example, if the received power of SFU2 at STA1 is similar to that of SFU1 at STA1, SFU2 will interfere with SFU1, preventing STA1 from correctly interpreting the signal transmitted by SFU1 and thus affecting STA1's communication performance.

[0147] To address the aforementioned problems, this application proposes a new technical solution. In this solution, multiple slave FTTR devices operating in the same frequency band are centrally scheduled or collaboratively scheduled by a master FTTR device. This allows these slave FTTR devices to reduce mutual interference by lowering their power, thereby improving the terminal's communication performance and increasing the communication system's throughput. This technical solution can be referred to as coordinated spatial reuse (Co-SR) scheduling technology, coordinated spatial division multiplexing technology, spatial concurrency technology, or coordinated spatial multiplexing. Co-SR can be called coordinated spatial division multiplexing.

[0148] In some implementations, under the FTTR architecture, if the interference relationship between the master FTTR device and / or slave FTTR device and the STA meets certain conditions, the master FTTR device centrally or collaboratively schedules multiple slave FTTR devices operating in the same frequency band, so that these multiple slave FTTR devices reduce mutual interference by reducing power.

[0149] In some implementations, if any two devices (master FTTR device, slave FTTR device, or terminal) can detect the signal sent by the former device while one device (master FTTR device, slave FTTR device, or terminal) is sending a message over the air interface, then the two devices are said to have an interference relationship.

[0150] As an example, the interference relationship between two devices may meet certain conditions, such as the signal strength detected by the latter device from the former device being greater than a certain threshold.

[0151] Normally, if the signal strength detected by a later device from a previous device exceeds a certain threshold, the later device will be unable to send messages according to the normal processing method.

[0152] As an example, by centrally or collaboratively scheduling multiple slave FTTR devices operating on the same frequency band through a master FTTR device, these slave FTTR devices can reduce mutual interference by reducing their power, including reducing the transmission power of the former device so that the strength of the signal from the former device detected by the latter device is less than a threshold.

[0153] As another example, by centrally or collaboratively scheduling multiple slave FTTR devices operating in the same frequency band through a master FTTR device, these slave FTTR devices can reduce mutual interference by lowering their power. This includes collaboratively reducing the transmit power of the two devices (in practice, it may not actually be reduced), so that each device can send messages to its respective receiving terminal at an appropriate transmit power, and the receiving terminal can successfully parse the message. However, during synchronous spatial concurrency, the transmit power may not be reduced.

[0154] The following describes some embodiments of this application, with reference to the accompanying drawings, of a method for implementing concurrent communication in a collaborative space within FTTR. Figure 3 is a schematic flowchart of a communication method according to an embodiment of this application. This communication method includes step S310.

[0155] The communication apparatus for performing the communication method shown in FIG3 in this embodiment includes a first FTTR device and a second FTTR device.

[0156] It is understood that the first FTTR device in the embodiments of this application can be replaced by one or more of the following: modules, devices, processors, chips, or circuits configured for use in or in conjunction with the first FTTR device. In some implementations, the first FTTR device may be referred to as a slave FTTR device.

[0157] It is understood that the second FTTR device in the embodiments of this application can be replaced by one or more of the following: modules, devices, processors, chips, or circuits configured for use in or in conjunction with the second FTTR device. In some implementations, the second FTTR device can be referred to as the main FTTR device.

[0158] S310, the second FTTR device sends cooperative space multiplexing scheduling information, which includes: the transmission power of the first FTTR device sending the message to the first terminal, and the first FTTR device is one of multiple FTTR devices with the same operating frequency band.

[0159] In some implementations, these multiple FTTR devices are slave FTTR devices, such as slave FTTR devices managed by the same FTTR device.

[0160] In some implementations, these multiple FTTR devices operate on the same frequency band, or multiple FTTR devices operate on the same frequency band, which can be understood as: the operating frequency bands of these multiple FTTR devices completely or partially overlap.

[0161] It can be understood that these multiple FTTR devices are spatially multiplexed FTTR devices, meaning that these multiple FTTR devices are located in different positions in the same space and operate in the same frequency band.

[0162] In some implementations, the second FTTR device is the master FTTR device among these multiple FTTR devices.

[0163] It can be understood that the first terminal is the terminal that communicates with the first FTTR device.

[0164] As an example, the second FTTR device is the main FTTR 101 in Figure 1. The plurality of FTTR devices include FTTR 102-1 to FTTR 102-5 in Figure 1. The first FTTR device is any one of FTTR 102-1 to FTTR 102-5. The first terminal is terminal 103 in Figure 1.

[0165] It is understood that the information name "cooperative space reuse scheduling information" in this embodiment is only an example and should not limit the function or content of the information. The information name can be replaced with any other name.

[0166] It is understandable that the first FTTR device determines or obtains the cooperative space multiplexing scheduling information before sending it.

[0167] In some implementations, the communication method of this embodiment further includes: the first FTTR device receiving cooperative space multiplexing scheduling information and sending messages according to the cooperative space multiplexing scheduling information.

[0168] For example, if the first FTTR device has the ability to receive cooperative space multiplexing scheduling information and the ability to send messages according to the cooperative space multiplexing scheduling information, the first FTTR device receives the cooperative space multiplexing scheduling information and sends messages according to the cooperative space multiplexing scheduling information.

[0169] In some implementations, the first FTTR device sends a message to the first terminal according to the cooperative space multiplexing scheduling information. This can be understood as the first FTTR device sending a message to the first terminal according to the instructions of the cooperative space multiplexing scheduling information.

[0170] For example, the first FTTR device sends a message to the first terminal using the transmit power indicated by the cooperative spatial multiplexing scheduling information.

[0171] In some implementations, the first FTTR device sends a data frame that carries a message.

[0172] In the implementation method where the first FTTR device receives cooperative spatial multiplexing scheduling information and sends messages according to the cooperative spatial multiplexing scheduling information, the master FTTR device can control or adjust the power of the first FTTR device among multiple FTTR devices in the same frequency band to send messages to the terminal. That is, it controls or adjusts the signal coverage of these multiple FTTR devices. This helps to control the difference between the signal-to-noise ratio of the signal received by the terminal from the first FTTR device and the signal-to-noise ratio of the signal received by the terminal from other FTTR devices in the same frequency band. This difference allows the terminal to correctly interpret the signal received from the first FTTR device, thereby helping to avoid the terminal being interfered with by the signals of other FTTR devices and thus helping to improve the communication performance of the terminal.

[0173] For example, in the topology shown in Figure 2, the master FTTR device indicates a larger power to SFU1 through cooperative spatial multiplexing scheduling information, so that the received power of the signal sent by STA1 to SFU1 is greater than the received power of the signal sent by STA1 to SFU2. The difference between these two received powers enables STA1 to correctly resolve the signal received by STA1 from SFU1, that is, to avoid or reduce the interference of SFU2's signal to SFU1's signal, thereby improving STA1's communication performance.

[0174] Figure 4 is a schematic diagram of the signal coverage of an FTTR device according to an embodiment of this application. In the example shown in Figure 4, the master FTTR device indicates a lower transmission power to SFU2 through cooperative spatial multiplexing scheduling information. The signal transmitted at this power allows STA2, which communicates with SFU2, to correctly parse the signal transmitted by SFU2. Furthermore, the signal coverage of this transmission power does not include STA1, thereby avoiding interference between the signal of SFU2 and the signal of SFU1 and improving the communication performance of STA1.

[0175] In some implementations, the first FTTR device sends a message to the first terminal based on the cooperative space multiplexing scheduling information. This can be understood as the first FTTR device sending a message to the first terminal with reference to the instructions of the cooperative space multiplexing scheduling information.

[0176] For example, the content of the collaborative space reuse scheduling information indication is adjusted, and messages are sent based on the adjusted information.

[0177] In some implementations, the first FTTR device lacks the capability to receive cooperative space multiplexing scheduling information, or lacks the capability to send messages based on the cooperative space multiplexing scheduling information. In this case, the communication method of this embodiment does not include: the first FTTR device receiving cooperative space multiplexing scheduling information and sending messages based on the cooperative space multiplexing scheduling information.

[0178] For the second FTTR device, it needs to be compatible with multiple FTTR devices. It cannot guarantee that all the FTTR devices it manages have the ability to receive cooperative space multiplexing scheduling information and send messages according to the cooperative space multiplexing scheduling information. However, the second FTTR device can have the ability to send cooperative space multiplexing scheduling information. This way, if the FTTR devices it manages have the ability to receive cooperative space multiplexing scheduling information and send messages according to the cooperative space multiplexing scheduling information, they can receive the cooperative space multiplexing scheduling information and send messages according to the cooperative space multiplexing scheduling information. This can avoid signal interference and improve the communication performance of the terminal.

[0179] In other words, the ability of the second FTTR device to send cooperative spatial multiplexing scheduling information helps to avoid signal interference between FTTR devices and improves the communication performance of the terminal.

[0180] In some implementations, the communication method of this embodiment further includes: a first terminal sending confirmation information, the confirmation information indicating that the first terminal has received a message sent by a first FTTR device. Accordingly, the first FTTR device receives the confirmation information.

[0181] In some implementations, the first terminal sends confirmation information, including: the first terminal sends a confirmation frame, the confirmation frame carrying confirmation information.

[0182] As an example, acknowledgment frames include block acknowledgement (BA) frames.

[0183] In some implementations, the cooperative space reuse scheduling information also includes at least one of the following: the identifier of the first FTTR device, the identifier corresponding to the cooperative space reuse scheduling information, the operating frequency band, the identifier of the first terminal, the TID to be transmitted by the first terminal, the effective time of the transmission power, the transmission rate of the message sent to the first terminal, the indication information of whether the first FTTR device needs to synchronously transmit messages with other FTTR devices among these multiple FTTR devices, the synchronization type when the first FTTR synchronously transmits messages, the start transmission timestamp of the synchronous transmission of messages by the first FTTR device, the indication information of whether the first FTTR device needs to actively transmit synchronization messages, the number of other FTTR devices among these multiple FTTR devices, or the identifier of other FTTR devices among these multiple FTTR devices.

[0184] The identifier of the first FTTR device can also be referred to as the number of the first FTTR device, or as the number of the FTTR that receives the cooperative space multiplexing scheduling information.

[0185] The identifier corresponding to the collaborative space reuse scheduling information can be called the identifier of the collaborative space reuse scheduling information, or the number corresponding to the collaborative space reuse scheduling information, or the number of the collaborative space reuse scheduling information.

[0186] In some implementations, the identifier of the first terminal can be the media access control (MAC) address or number of the first terminal.

[0187] In some implementations, the effective time of the transmission power can be referred to as the transmission time of the transmission power.

[0188] In some implementations, the first FTTR device does not need to send messages synchronously with the other FTTR devices among these multiple FTTR devices. This can be understood as the first FTTR device sending messages asynchronously with the other FTTR devices among these multiple FTTR devices.

[0189] In some implementations, synchronous message sending can be called synchronous spatial concurrency, and asynchronous message sending can be called asynchronous spatial concurrency.

[0190] In some implementations, during the concurrent synchronization process, the start and end times of data frames sent by each slave FTTR device need to be consistent to ensure that multiple terminals within the coverage area of ​​different slave FTTR devices can synchronously reply with acknowledgment frames after receiving data frames. This synchronous reply with acknowledgment frames from multiple terminals can be understood as: the start times of sending acknowledgment frames by these multiple terminals being consistent.

[0191] In some implementations, during asynchronous concurrent spatial processes, each slave FTTR device can independently compete for air interface resources to send data frames. Because each slave FTTR device sends data frames asynchronously, terminals within the coverage area of ​​different FTTR devices can asynchronously send back acknowledgment frames after receiving the data frames.

[0192] In some implementations, synchronous spatial concurrency can be achieved by controlling multiple FTTR devices to have the same start time and control messages to have the same send time, while asynchronous spatial concurrency does not require controlling the send time and end time of messages.

[0193] Compared to asynchronous concurrency, synchronous spatial concurrency can further reduce mutual interference between SFUs and is applicable to a wider range of scenarios. Asynchronous spatial concurrency, compared to synchronous spatial concurrency, is simpler to implement and has lower requirements for coordination.

[0194] Figure 5 is a schematic diagram of the synchronous spatial concurrency process according to an embodiment of this application. As shown in Figure 5, in the synchronous spatial concurrency process, SFU1 and SFU2 synchronously send data frames, and the data frames carry messages; STA1 is the STA within the coverage area of ​​SFU1, and STA2 is the STA within the coverage area of ​​SFU2. STA1 and STA2 synchronously send acknowledgment frames, for example, STA1 and STA2 synchronously send block acknowledgement (BA) frames.

[0195] Figure 6 is a schematic diagram of the asynchronous spatial concurrency process according to an embodiment of this application. As shown in Figure 6, in the asynchronous spatial concurrency process, SFU1 and SFU2 asynchronously send data frames, and the data frames carry messages; STA1 is a STA within the coverage area of ​​SFU1, and STA2 is a STA within the coverage area of ​​SFU2. STA1 and STA2 can asynchronously send acknowledgment frames, for example, STA1 and STA2 asynchronously send BA frames.

[0196] In the example shown in Figure 6(a), the data frames sent by SFU1 and SFU2 have different start times and different end times; this is just an example. In this embodiment, asynchronous can be understood as at least one of the start and end times of the frames being different.

[0197] In some implementations, the indication information indicating whether the first FTTR device needs to synchronize message transmission with the other FTTR devices among these multiple FTTR devices can be called a synchronization flag. The synchronization flag can indicate synchronous message transmission or asynchronous message transmission.

[0198] In some implementations, the first transmit power configured by the master FTTR device for the first FTTR device will not interfere with the transmit power of at least one other FTTR device, and a synchronization flag is used to instruct the first FTTR device to transmit messages asynchronously. In this way, no device in the FTTR device set consisting of the first FTTR device and these at least one FTTR device will hear messages from other FTTR devices in the set, thus preventing any device from refusing to compete for the air interface to transmit messages due to a busy channel. In other words, this device can transmit messages asynchronously with other FTTR devices through spatial multiplexing.

[0199] As shown in Figure 6(b), the transmit power configured for SFU1 and SFU2 by the master FTTR device does not interfere with each other. SFU1 sends a message first, and SFU2 checks whether it has detected messages sent by other SFUs before sending messages. Because the transmit power configured for SFU1 and SFU2 by the master FTTR device does not interfere with each other, SFU2 will not detect messages sent by SFU1, thus determining that the air interface is idle, and therefore sends a message.

[0200] In some implementations, the first transmit power configured by the master FTTR device for the first FTTR device does not take into account whether it will interfere with the transmit powers of at least one other FTTR device, or the first transmit power configured by the master FTTR device for the first FTTR device will interfere with the transmit powers of at least one other FTTR device. In this case, a synchronization flag can instruct the first FTTR device to transmit messages asynchronously.

[0201] When the synchronization flag indicates that the first FTTR device is sending messages asynchronously, if the first FTTR device detects messages from other FTTR devices, and those other FTTR devices are FTTR devices that the main FTTR device indicates are sending messages asynchronously with the first FTTR device, then the first FTTR device can ignore the channel status being busy and send messages according to its own needs.

[0202] For example, after the first FTTR device detects a message from another FTTR device and parses the message to obtain the identifier of that other FTTR device, if it determines that the identifier is included in the other FTTR device indicated in the first FTTR device's cooperative spatial multiplexing scheduling information, it ignores the channel state being busy and sends messages according to its own needs.

[0203] As shown in Figure 6(c), SFU1 sends a message first, and SFU2 checks whether it has detected messages sent by other SFUs before sending messages. After SFU2 detects SFU1's message and parses the message to obtain SFU1's MAC address, it determines that the information of other FTTR devices indicated in SFU2's cooperative spatial multiplexing scheduling information includes SFU1's MAC address. Then, SFU2 can ignore the channel state and send messages.

[0204] In some implementations, the synchronization type when the first FTTR device sends messages synchronously with other FTTR devices can be understood as: the operation performed by the first FTTR device to fulfill the requirement of synchronously sending messages with other FTTR devices.

[0205] As an example, the synchronization type includes: sending a message according to the start sending timestamp, sending a message based on the time the synchronization message is triggered, or sending a message based on the time the synchronization message is triggered and the synchronization message is triggered by other synchronization messages.

[0206] Sending messages according to the start time stamp can be understood as: defining the start time stamp for each message for these multiple FTTR devices, and after these multiple FTTR devices learn of the start time stamp, they all start sending messages at that start time stamp, thereby achieving synchronous message transmission.

[0207] For example, in Figure 5, the times when SFU1 starts sending messages and the times when SFU2 starts sending messages are timestamps specified by the master FTTR device.

[0208] The synchronization type indicated by the cooperative space multiplexing scheduling information includes, in some implementations, the start time stamp when sending messages according to the start time stamp.

[0209] It is understandable that the start transmission timestamp can be predefined and known in advance by each FTTR device, so that the cooperative space reuse scheduling information does not need to indicate the start transmission timestamp.

[0210] In some implementations, messages are sent based on a synchronization message trigger time, including: one FTTR device sending a message to other FTTR devices; for ease of description, this message is referred to as the first message; the FTTR device sending the first message sends the message after the end time of the first message's transmission, for a time interval of a first duration after the end time of the transmission, and the other FTTR devices send messages after the end time of the first message's reception, for a time interval of a first duration after the end time of the reception. This allows multiple FTTR devices to send messages synchronously.

[0211] In this embodiment, the time-based message transmission based on the synchronization message trigger can be referred to as: non-interactive air interface message synchronous transmission. This is because after one FTTR device sends the first message, multiple FTTR devices can achieve synchronous message transmission.

[0212] In this embodiment, the first message can be called a synchronization message because the first message is used to realize the different transmission of messages.

[0213] In some implementations, the first message can be a clear to send (CTS) message.

[0214] In some implementations, the first duration can be a predefined duration. As an example, the first duration can be a short interframe space (SIFS).

[0215] Figure 7 is a schematic diagram of non-interactive message synchronous transmission according to an embodiment of this application. As shown in Figure 7, SFU1 sends a CTS message; SFU1 starts timing at the end time of CTS message transmission, and sends the message when the timing duration is SIFS; SFU2 receives CTS messages, starts timing at the end time of CTS message reception, and sends the message when the timing duration is SIFS.

[0216] In some implementations, sending messages based on the timing of a synchronization message trigger, where the synchronization message is triggered by other synchronization messages, includes: one FTTR device sending a message to other FTTR devices (for ease of description, this message is referred to as a second message); after receiving the second message, the other FTTR devices send a message (for ease of description, this message is referred to as a first message); the FTTR device sending the first message sends the message after the end time of the first message's transmission, for a time interval of a first duration after the end time of the first message's transmission, and the FTTR device receiving the first message sends the message after the end time of the first message's reception, for a time interval of a first duration after the end time of the reception. This allows multiple FTTR devices to send messages synchronously.

[0217] In this embodiment, sending messages based on the time triggered by a synchronization message, and the synchronization message being triggered by other synchronization messages, can be referred to as: interactive air interface message synchronous transmission. This is because after one FTTR device sends a second message, triggering other FTTR devices to send a first message, these multiple FTTR devices achieve synchronized message transmission.

[0218] In this embodiment, the first message and the second message can be called synchronization messages because the first message and the second message are used to realize different transmission of messages.

[0219] In some implementations, the first message can be a CTS message.

[0220] In some implementations, the first message can be a request to send (RTS) message.

[0221] In some implementations, the first duration can be a predefined duration. As an example, the first duration can be SIFS.

[0222] Figure 8 is a schematic diagram of interactive message synchronous transmission according to an embodiment of this application. As shown in Figure 8, SFU1 sends an RTS message; SFU2 receives the RTS, indicating that the air interface resources are available; SFU2 sends a CTS message; SFU2 starts timing at the end time of CTS message transmission, and sends the message when the timing duration is SIFS; SFU1 receives the CTS message, starts timing at the end time of CTS message reception, and sends the message when the timing duration is SIFS.

[0223] In some implementations, the synchronization type includes sending messages based on the time triggered by a synchronization message, or, in the case where the synchronization type includes sending messages based on the time triggered by a synchronization message and the synchronization message is triggered by other synchronization messages, the cooperative space reuse scheduling information can also indicate whether the first FTTR device needs to actively send a synchronization message.

[0224] For example, if the cooperative space multiplexing scheduling information indicates that the first FTTR device needs to actively send a synchronization message, then the first FTTR can act as SFU1 in Figure 7 or Figure 8; if the cooperative space multiplexing scheduling information indicates that the first FTTR device does not need to actively send a synchronization message, then the first FTTR can act as SFU2 in Figure 7 or Figure 8.

[0225] In some implementations, the message carrying the cooperative space reuse scheduling information can be called: airspace resource allocation message or Co-SR scheduling result message.

[0226] In this embodiment of the application, the master FTTR device sends a cooperative spatial multiplexing scheduling information to the slave FTTR device once, which can be referred to as a Co-SR scheduling.

[0227] Figure 9 is a schematic flowchart of a communication method according to an embodiment of this application. As shown in Figure 9, the communication method of this embodiment further includes: S320, a first FTTR device sends cooperative spatial multiplexing result information, the cooperative spatial multiplexing result information including: the number of data units transmitted by the first FTTR device using the transmission power, and / or, the packet error rate of the data units transmitted by the first FTTR device using the transmission power. Correspondingly, a second FTTR device receives the cooperative spatial multiplexing result information.

[0228] In some implementations, the data unit is the MAC service data unit (MSDU).

[0229] It is understood that the information name "Collaborative Space Reuse Result Information" in this embodiment is only an example and should not limit the function or content of the information. The information name can be replaced with any other name.

[0230] In some implementations, the collaborative space reuse result information may also include: the identifier of the first FTTR device, and / or, the identifier corresponding to the collaborative space reuse result information, and the identifier corresponding to the collaborative space reuse scheduling information and the identifier corresponding to the collaborative space reuse result information are associated.

[0231] In some implementations, the identifier corresponding to the collaborative space reuse result information can be called: the identifier of the collaborative space reuse result information, the number corresponding to the collaborative space reuse result information, or the number of the collaborative space reuse result information.

[0232] As an example, the identifier corresponding to the collaborative space reuse scheduling information is the same as the identifier corresponding to the collaborative space reuse result information.

[0233] In some implementations, transmission time affects the number of MPDUs; packet error rate may be constrained by the overall factors of transmission time, transmission power, transmission rate, and whether synchronous transmission is used in the cooperative space multiplexing scheduling information.

[0234] In some implementations, the message carrying the result information of the Co-SR transmission can be called: Co-SR transmission result message.

[0235] Table 1-1 is an example of the content of a Co-SR scheduling result message according to one embodiment of this application. It is understood that Table 1-1 is merely an example, and the Co-SR scheduling result message in this embodiment may contain more or less information than that in Table 1-1, or may contain information with similar functions. In the embodiments of this application, the cooperating user can be understood as the terminal involved or affected by this Co-SR scheduling, which is the terminal communicating with the SFU that receives the message.

[0236] Table 1-1

[0237] The transmission time length of this Co-SR in Table 1-1 can be understood as: the effective time or effective duration of the transmission power; the transmission power of this Co-SR cooperating user can be understood as: the transmission power of the SFU sending messages to the cooperating user; the transmission rate of this Co-SR cooperating user can be understood as: the transmission rate of the SFU sending messages to the cooperating user.

[0238] As an example, the synchronization flag field can occupy 1 bit, the synchronization type field can occupy 2 bits, and whether to send a synchronization message can occupy 1 bit.

[0239] Table 1-2 shows an example of the content of a Co-SR scheduling result message according to one embodiment of this application. It is understood that Table 1-2 is merely an example, and the Co-SR scheduling result message in this embodiment may contain more or less information than that in Table 1-2, or may contain information with similar functions. In some implementations, this message format is used to schedule asynchronous message transmission.

[0240] Table 1-2

[0241] Tables 1-3 are examples of the content of a Co-SR scheduling result message according to one embodiment of this application. It is understood that Tables 1-3 are merely examples, and the Co-SR scheduling result message in the embodiments of this application may contain more or less information than that in Tables 1-3, or may contain information with similar functions.

[0242] Table 1-3

[0243] In Table 1-3, the SFU can determine the transmission rate based on the expected SINR value. For example, the SFU can determine the optimal transmission rate under one or more conditions such as different bandwidths, different generations of Wi-Fi protocols, and service requirements (such as buffering, latency, etc.) based on the SINR value, thereby improving the performance of collaborative spatial multiplexing.

[0244] In Table 1-3, SRG OBSS PD level and non-SRG OBSS PD level indicate that different CCA thresholds can be used for packets in spatial multiplexing groups and non-spatial multiplexing groups to improve cooperative spatial multiplexing performance. SFUs that typically support Wi-Fi 6 and later generations of Wi-Fi protocols typically support this field setting. For example, the CCA threshold used for spatial multiplexing packets can be larger than the CCA threshold used for packets in non-spatial multiplexing groups.

[0245] Table 2-1 is an example of the content of a Co-SR transmission result message according to one embodiment of this application. It is understood that Table 2-1 is only an example, and the Co-SR transmission result message in the embodiment of this application may contain more or less information than that in Table 2-1, or contain information with similar functions.

[0246] Table 2-1

[0247] Table 2-2 is an example of the content of a Co-SR transmission result message according to one embodiment of this application. It is understood that Table 2-2 is only an example, and the Co-SR transmission result message in the embodiment of this application may contain more or less information than that in Table 2-2, or contain information with similar functions.

[0248] Table 2-2

[0249] Figure 10 is a flowchart illustrating a communication method according to an embodiment of this application. As shown in Figure 10, the communication method may include: S308, a first FTTR device sends cooperative spatial multiplexing related information to a second FTTR device, the cooperative spatial multiplexing related information including downlink transmission information of each terminal in at least one terminal, wherein the at least one terminal is a terminal communicating with the first FTTR device.

[0250] In some implementations, the at least one terminal includes a first terminal.

[0251] In some implementations, the second FTTR device has the ability to receive information related to cooperative space multiplexing. Therefore, the communication method in this embodiment further includes: the second FTTR device receiving information related to cooperative space multiplexing.

[0252] In some implementations, the second FTTR device has the capability to send cooperative space multiplexing scheduling information to the first FTTR device based on cooperative space multiplexing related information. In this case, the communication method of this embodiment further includes: the second FTTR device sending cooperative space multiplexing scheduling information to the first FTTR device based on cooperative space multiplexing related information.

[0253] In some implementations, the interference relationship between the FTTR device and the terminal determines whether Co-SR is possible and the performance limit of Co-SR scheduling. Therefore, the second FTTR device can perform Co-SR scheduling based on the interference relationship between the FTTR device and the terminal, combined with the Co-SR related information reported by the FTTR device.

[0254] As an example, FTTR device 1 sends a message to terminal 1, while FTTR device 2 sends a message to terminal 2. By appropriately reducing the transmission power of FTTR device 1, its interference intensity at terminal 2 is reduced (e.g., maintaining consistency with the noise floor after power reduction), thereby reducing the impact of the signal transmitted by FTTR device 1 on terminal 2's parsing of the message from FTTR device 2. The transmission power of FTTR device 2 is handled similarly. FTTR devices 1 and FTTR device 2 correspondingly reduce their transmission rates to achieve parallel transmission. Reducing the transmission rate ensures that the receiving end can correctly parse the message, resulting in a low packet error rate. In some implementations, the total rate of parallel transmission simply needs to be greater than the rate of a single transmission.

[0255] In this implementation, since the cooperative space multiplexing scheduling information is sent by the second FTTR device based on the cooperative space multiplexing related information, the cooperative space multiplexing related information is taken into account. Therefore, it helps to improve the accuracy of the cooperative space multiplexing scheduling information, thereby helping to avoid interference from signals between FTTR devices to the terminal more efficiently and accurately, and thus helping to improve the communication performance of the terminal more efficiently and accurately.

[0256] In some implementations, the downlink transmission information includes at least one of the following: the identifier of each terminal, the transmission rate of each terminal, the number of TIDs with data in each terminal's TID, or the transmission information of each TID with data in each terminal's TID.

[0257] In some implementations, the transmission information of each TID includes at least one of the following: total buffer size, number of data units, head-of-queue latency, and size of each data unit.

[0258] As an example, the data unit is MSDU.

[0259] In some implementations, the information related to collaborative space reuse also includes at least one of the following: the identifier of the first FTTR device, its operating frequency band, or the number of the at least one terminal.

[0260] In some implementations, messages carrying information related to collaborative space reuse can be called Co-SR related information messages.

[0261] Table 3 shows an example of the content of a Co-SR related information message according to one embodiment of this application. It is understood that Table 3 is merely an example, and the Co-SR related information messages in the embodiments of this application may contain more or less information than those in Table 3, or may contain information with similar functions.

[0262] Table 3

[0263] It is understood that in the embodiments of this application, the user can be understood as the terminal.

[0264] Figure 11 is a flowchart illustrating a communication method according to an embodiment of this application. As shown in Figure 11, the communication method may further include: S306, the second FTTR device sends cooperative space reuse information collection information, the cooperative space reuse information collection information being used to trigger the first FTTR device to report cooperative space reuse related information.

[0265] In some implementations, the first FTTR device has the capability to receive cooperative space multiplexing information collection information. In this implementation, the communication method further includes: the first FTTR device receiving cooperative space multiplexing information collection information.

[0266] In some implementations, the first FTTR device has the following capability: collecting and transmitting cooperative space multiplexing-related information based on cooperative space multiplexing information. In this implementation, the communication method further includes: the first FTTR device collecting and transmitting cooperative space multiplexing-related information based on cooperative space multiplexing information.

[0267] In this embodiment, the first FTTR device responds to the information collection information on collaborative space reuse by sending collaborative space reuse-related information, which can avoid the first FTTR device sending unnecessary collaborative space reuse-related information, thereby helping to avoid resource waste.

[0268] In summary, the second FTTR device sending cooperative space reuse information collection information helps avoid the first FTTR device sending unnecessary cooperative space reuse related information, thereby helping to avoid resource waste.

[0269] In some implementations, the information collected for collaborative space reuse includes: indication information from at least one terminal. It can be understood that this at least one terminal is the user who needs to report information.

[0270] In some implementations, the message carrying Co-SR information collection information can be called: trigger Co-SR information collection message.

[0271] Table 4 is an example of the content of a Co-SR information collection trigger message according to one embodiment of this application. It is understood that Table 4 is only an example, and the Co-SR information collection trigger message in the embodiment of this application may contain more or less information than that in Table 4, or contain information with similar functions.

[0272] Table 4

[0273] In some implementations, the indication information for the at least one terminal includes: the identifier of the at least one terminal, and / or, the grouping information of the at least one terminal. Alternatively, users who need to report information can be indicated using different methods. One method includes listing the MAC addresses or IDs of all users who need to report information, as shown in Table 5; another method includes pre-grouping users and instructing relevant users according to group IDs, as shown in Table 6.

[0274] Table 5

[0275] Table 6

[0276] In one example of the user group number field in Table 6, users are divided into P groups, where P is a positive integer. This field can have P+1 values, where each of the P values ​​corresponds to a user in group P, each value indicates the corresponding user group, and the remaining value indicates the information of all users to be reported.

[0277] As an example, P is a positive integer not greater than 8.

[0278] In some exemplary communication methods of this application, the first FTTR device can proactively report information related to collaborative space reuse.

[0279] Some exemplary communication methods of this application include S308 and S310.

[0280] Some exemplary communication methods of this application include S308, S310 and S320.

[0281] Some exemplary communication methods of this application include S306, S308 and S310.

[0282] Some exemplary communication methods of this application include S306, S308, S310 and S320.

[0283] Figure 12 is a flowchart illustrating a communication method according to an embodiment of this application. As shown in Figure 12, the communication method includes: S304, a first FTTR device sends cooperative space multiplexing capability information, the cooperative space multiplexing capability information being used to indicate whether the first FTTR device supports at least one of the following capabilities: actively reporting cooperative space multiplexing related information, responding to the instruction of the master FTTR device to report cooperative space multiplexing related information, synchronously sending messages, asynchronously sending messages, or actively sending synchronous messages.

[0284] In some implementations, proactively reporting collaborative space reuse information can be understood as: the first FTTR device needs instructions from other devices and proactively sends collaborative space reuse information itself.

[0285] In some implementations, the second FTTR device has the capability to receive cooperative space multiplexing capability information. In this implementation, the communication method further includes: the second FTTR device receiving cooperative space multiplexing capability information.

[0286] In some implementations, the second FTTR device has the following capability: sending cooperative space multiplexing scheduling information to the first FTTR device based on the cooperative space multiplexing capability information. In this implementation, the communication method further includes: the second FTTR device sending cooperative space multiplexing scheduling information to the first FTTR device based on the cooperative space multiplexing capability information.

[0287] For example, the capability required for the scheduling information indicated by the second FTTR device to the first FTTR device is the capability possessed by the first FTTR device.

[0288] In this case, because the cooperative space multiplexing information collection information is sent by the second FTTR device based on the cooperative space multiplexing capability information, taking into account the cooperative space multiplexing capability of the first FTTR device, the cooperative space multiplexing information collection information indicated by the second FTTR device is more accurate. This helps to collect more accurate cooperative space multiplexing related information more efficiently, thereby helping to avoid interference of the FTTR device's signal to the terminal, and ultimately helping to improve the terminal's communication performance.

[0289] As can be seen from the above, the first FTTR device sending cooperative spatial multiplexing capability information helps the first FTTR device to collect more accurate cooperative spatial multiplexing related information more efficiently, thereby helping to avoid interference of the FTTR device's signal to the terminal, and ultimately helping to improve the terminal's communication performance.

[0290] In some implementations, the collaborative space reuse capability information also includes: the identifier of the first FTTR device, and / or, the operating frequency band.

[0291] In some implementations, messages carrying information about the Co-SR-related capability response can be called: Co-SR related capability response messages.

[0292] Table 7-1 is an example of the content of a Co-SR related capability response message according to one embodiment of this application. It is understood that Table 7-1 is only an example, and the Co-SR related capability response message in the embodiment of this application may contain more or less information than that in Table 7-1, or contain information with similar functions.

[0293] Table 7-1

[0294] Table 7-2 is an example of the content of a Co-SR related capability response message according to one embodiment of this application. It is understood that Table 7-2 is merely an example, and the Co-SR related capability response message in this embodiment may contain more or less information than that in Table 7-2, or may contain information with similar functions.

[0295] Table 7-2

[0296] As an example, the field "Actively report Co-SR related information" occupies 1 bit; the field "Report Co-SR related information in response to MFU instructions" occupies 1 bit; the field "Synchronous or asynchronous Co-SR capability" occupies 2 bits; the field "Co-SR synchronization concurrency type" occupies 2 bits; and the field "Actively send synchronization message" occupies 1 bit.

[0297] It is understood that in some implementations, the communication method of this embodiment does not include S308. For example, when the first FTTR device does not have the ability to send cooperative spatial multiplexing related information.

[0298] It is understood that in some implementations, the communication method of this embodiment does not include S306. For example, when the second FTTR device does not have the ability to send cooperative spatial multiplexing information collection information.

[0299] Figure 13 is an exemplary flowchart of a communication method according to an embodiment of this application. As shown in Figure 13, the communication method may further include S302, in which the second FTTR device sends a cooperative space multiplexing capability request message, the cooperative space multiplexing capability request message being used to instruct the first FTTR device to report cooperative space multiplexing capability information.

[0300] In some implementations, the first FTTR device has the capability to receive cooperative space multiplexing capability request information. In this implementation, the communication method further includes: the first FTTR device receiving cooperative space multiplexing capability request information.

[0301] In some implementations, the first FTTR device has the following capability: sending cooperative space multiplexing capability information based on the cooperative space multiplexing capability request information. In this implementation, the communication method may further include: the first FTTR device sending cooperative space multiplexing capability information based on the cooperative space multiplexing capability request information.

[0302] For example, the capability reported by the first FTTR device is the capability to request information for collaborative space reuse capability.

[0303] In this case, because the first FTTR device sends the cooperative space reuse capability information according to the cooperative space reuse capability request information, it helps to avoid the first FTTR device sending unnecessary cooperative space reuse capability information, thereby helping to avoid resource waste.

[0304] As can be seen from the above, the second FTTR device sending a cooperative space reuse capability request information helps to prevent the first FTTR device from sending unnecessary cooperative space reuse capability information, thereby helping to avoid resource waste.

[0305] In some implementations, the collaborative space reuse capability request information also includes: the identifier of the first FTTR device, and / or, the operating frequency band.

[0306] In some implementations, a message carrying a request for Co-SR related capability negotiation can be called a Co-SR related capability negotiation request message.

[0307] Table 8-1 is an example of the content of a Co-SR related capability negotiation request message according to one embodiment of this application. It is understood that Table 8-1 is only an example, and the Co-SR related capability negotiation request message in the embodiment of this application may contain more or less information than that in Table 8-1, or contain information with similar functions.

[0308] Table 8-1

[0309] Table 8-2 is an example of the content of a Co-SR related capability negotiation request message according to one embodiment of this application. It is understood that Table 8-2 is only an example, and the Co-SR related capability negotiation request message in the embodiment of this application may contain more or less information than that in Table 8-2, or contain information with similar functions.

[0310] Table 8-2

[0311] In some exemplary communication methods of this application, the first FTTR device can proactively report cooperative space reuse capability information.

[0312] In some implementations, S306, S308, S310, and S320 can be executed repeatedly, and each repetition can be called a round of collaborative space sharing call.

[0313] In some implementations, the communication method of this application also includes the initialization of the FTTR device and / or the time synchronization process between FTTR devices.

[0314] Some exemplary communication methods of this application include S304 and S310.

[0315] Some exemplary communication methods of this application include S304, S308 and S310.

[0316] Some exemplary communication methods of this application include S304, S310 and S320.

[0317] Some exemplary communication methods of this application include S304, S308, S310 and S320.

[0318] Some exemplary communication methods of this application include S302, S304 and S310.

[0319] Some exemplary communication methods of this application include S304, S306, S308 and S310.

[0320] Some exemplary communication methods of this application include S304, S306, S308, S310 and S320.

[0321] Some exemplary communication methods of this application include S302, S304, S306, S308, S310 and S320.

[0322] Figure 14 is a flowchart illustrating a communication method according to an embodiment of this application. As shown in Figure 14, the communication method includes: S310-1, the second FTTR device sends coordination information, the coordination information including synchronization marker information, the synchronization marker information indicating whether the first FTTR device needs to synchronize message transmission with other FTTR devices, and the first FTTR device operates on the same frequency band as the other FTTR devices.

[0323] In some implementations, the first FTTR device and other FTTR devices are slave FTTR devices.

[0324] In some implementations, not needing to send messages synchronously can be understood as sending messages asynchronously.

[0325] In some implementations, the first FTTR device has the capability to receive coordination information. In this implementation, the communication method further includes: the first FTTR device receiving coordination information.

[0326] In some implementations, the first FTTR device has the ability to send messages based on coordination information. In this implementation, the communication method further includes: the first FTTR device sending messages based on coordination information.

[0327] For example, the first FTTR device sends messages in accordance with the coordination information instructions, thereby enabling synchronous or asynchronous message transmission between the first FTTR device and other FTTR devices.

[0328] The content of synchronous and asynchronous message transmission in this embodiment can be found in the relevant content of the embodiment shown in Figure 3.

[0329] In this communication method, the master FTTR device indicates to the slave FTTR device whether the slave FTTR device needs to send messages synchronously with other FTTR devices. This allows the slave FTTR device to know whether it is sending messages synchronously or asynchronously, thereby controlling the slave FTTR device to send messages in a reasonable manner to avoid signal interference with other slave FTTR devices and affecting the communication performance of the terminal.

[0330] In some possible implementations, when the synchronization marker information indicates that the first FTTR device needs to synchronize the transmission of messages with other FTTR devices, the coordination information also includes synchronization type information, which indicates: transmitting messages according to the start transmission timestamp, transmitting messages based on the time when the synchronization message is triggered, or transmitting messages based on the time when the synchronization message is triggered and the synchronization message is triggered by other synchronization messages.

[0331] In this embodiment, messages are sent according to the start sending timestamp, or based on the time triggered by a synchronization message, or based on the time triggered by a synchronization message and the synchronization message is triggered by another synchronization message. Please refer to the relevant content in the embodiment shown in Figure 3, which will not be repeated here.

[0332] When the master FTTR device instructs the first FTTR device to send messages synchronously with other FTTR devices, it also instructs the first FTTR device on the type of messages to be sent synchronously with other FTTR devices, so that the first FTTR device can accurately know the method to achieve synchronous message sending, thereby accurately achieving synchronous message sending.

[0333] In some possible implementations, when the synchronization type information indicates that a message is sent according to the start time stamp, the coordination information also includes an indication of the start time stamp.

[0334] In this implementation, the master FTTR device instructs the slave FTTR device to start sending a timestamp, enabling the slave FTTR device to achieve synchronized message transmission in a simple way.

[0335] In some possible implementations, when the synchronization type information indicates that a message is sent based on the time triggered by the first synchronization message, or when the synchronization type information indicates that a message is sent based on the time triggered by the first synchronization message and the first synchronization message is triggered by the second synchronization message, the coordination information also includes synchronization message sending indication information, which indicates whether the first FTTR device needs to actively send a synchronization message.

[0336] In this implementation, the method specified by the master FTTR device for synchronous message transmission via synchronization messages, and the sending behavior of the slave FTTR device for synchronization messages, help the slave FTTR device and other FTTR devices to accurately coordinate and achieve synchronous message transmission.

[0337] Some exemplary communication methods of this application include S304 and S310-1.

[0338] Some exemplary communication methods of this application include S304, S308 and S310-1.

[0339] Some exemplary communication methods in this application include S304 and S310-1.

[0340] Some exemplary communication methods in this application include S304, S308, and S310-1.

[0341] Some exemplary communication methods of this application include S302, S304 and S310-1.

[0342] Some exemplary communication methods of this application include S304, S306, S308 and S310-1.

[0343] Some exemplary communication methods of this application include S304, S306, S308, and S310-1.

[0344] Some exemplary communication methods in this application include S302, S304, S306, S308, and S310-1.

[0345] Optionally, any of the above exemplary communication methods may further include S320.

[0346] It is understood that, in order to achieve the functions in the above embodiments, the first FTTR device and the second FTTR device include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0347] Figures 15 and 16 are schematic diagrams of the communication devices according to embodiments of this application. These communication devices can be used to implement the functions of the first FTTR device or the second FTTR device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0348] As shown in Figure 15, the communication device 1500 includes a processing unit 1510 and a transceiver unit 1520. The communication device 1500 is used to implement the functions of the first FTTR device or the second FTTR device in any of the above method embodiments.

[0349] As an example, when the communication device 1500 is used for the function of the second FTTR device in any of the aforementioned method embodiments: the processing unit 1510 is used to perform at least one of the following operations: determining coordination information, determining coordination space multiplexing scheduling information, determining coordination space multiplexing information collection information, or determining coordination space multiplexing capability request information; the transceiver unit 1520 is used to perform at least one of the following operations: sending the coordination space multiplexing scheduling information, receiving coordination space multiplexing result information, sending coordination information, receiving coordination space multiplexing related information, sending coordination space multiplexing information collection information, receiving coordination space multiplexing capability information, or sending coordination space multiplexing capability request information.

[0350] As an example, when the communication device 1500 is used for the function of the first FTTR device in any of the aforementioned method embodiments: the processing unit 1510 is used to perform at least one of the following operations: determining cooperative space multiplexing result information, determining cooperative space multiplexing related information, or determining cooperative space multiplexing capability information; the transceiver unit 1520 is used to perform at least one of the following operations: receiving the cooperative space multiplexing scheduling information, sending the cooperative space multiplexing result information, sending the cooperative space multiplexing related information, receiving cooperative information, receiving cooperative space multiplexing information collection information, sending cooperative space multiplexing capability information, or receiving cooperative space multiplexing capability request information.

[0351] For a more detailed description of the processing unit 1510 and the transceiver unit 1520, please refer to the relevant descriptions in the foregoing method embodiments.

[0352] As shown in Figure 16, the communication device 1600 includes a processor 1610 and an interface circuit 1620. The processor 1610 and the interface circuit 1620 are coupled to each other. It is understood that the interface circuit 1620 can be a transceiver or an input / output interface. Optionally, the communication device 1600 may also include a memory 1630 for storing instructions executed by the processor 1610, or storing input data required by the processor 1610 to execute instructions, or storing data generated after the processor 1610 executes instructions. Sometimes, the interface circuit 1620 can also be understood as part of the processor 1610, in which case the communication device 1600 includes the processor 1610.

[0353] As an example, when the communication device 1600 is used to implement any of the aforementioned methods, the processor 1610 is used to implement the functions of the processing unit 1510, and the interface circuit 1620 is used to implement the functions of the transceiver unit 1520.

[0354] As an example, when the aforementioned communication device is a chip used in a communication equipment, the chip receiving information can be understood as the information being first received by other modules (such as an RF module or antenna) in the communication equipment, and then sent to the chip by these modules. Similarly, the chip sending information can be understood as the information being first sent to other modules (such as an RF module or antenna) in the communication equipment, and then sent by these modules.

[0355] In some embodiments of this application, a computer program product is also provided, which, when run on a processor, can implement the method implemented by the first FTTR device in any of the above embodiments.

[0356] Some embodiments of this application also provide a computer program product that, when run on a processor, can implement the method implemented by the second FTTR device in any of the above embodiments.

[0357] In some embodiments of this application, a computer-readable storage medium is also provided, which contains computer instructions that, when executed on a processor, can implement the method implemented by the first FTTR device in any of the above embodiments.

[0358] In some embodiments of this application, a computer-readable storage medium is also provided, which contains computer instructions that, when executed on a processor, can implement the method implemented by the second FTTR device in any of the above embodiments.

[0359] In some embodiments of this application, a communication system is also provided, which can implement the methods implemented by the first FTTR device and the second FTTR device in any of the above method embodiments.

[0360] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be FTTR devices or terminals, or modules within FTTR devices or terminals. Information transmission and reception can be between an FTTR device and a terminal; between two FTTR devices; or between different modules within a single device, such as the chip of an FTTR device and other modules within that device, or the chip of a terminal and other modules within that terminal.

[0361] It is understood that the processor in the embodiments of this application can be a central processing unit, or other general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, 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.

[0362] In this embodiment of the application, the processor may include one or more of the following: central processing unit (CPU), application-specific integrated circuit (ASIC), digital signal processor (DSP), microprocessor unit (MPU), microcontroller unit (MCU), graphics processing unit (GPU), field programmable gate array (FPGA), artificial intelligence processor (AI processor), or neural processing unit (NPU).

[0363] In this application embodiment, the memory may include, but is not limited to, cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions for storing computer programs or instructions, and / or data.

[0364] 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, optical discs, or any other form of storage medium well 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 the storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the ASIC can reside in a base station or terminal. The processor and the storage medium can also exist as discrete components in the base station or terminal.

[0365] 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.

[0366] 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.

Claims

1. A communication method, characterized in that, The communication method includes: Determine the coordination information, which includes synchronization marker information. The synchronization marker information indicates whether the first fiber-to-room FTTR device needs to transmit messages synchronously with other FTTR devices. The first FTTR device and the other FTTR devices operate on the same frequency band. The coordination information is sent to the first FTTR device.

2. The communication method according to claim 1, characterized in that, The synchronization tag information indicates that the first FTTR device needs to synchronize message transmission with the other FTTR devices; The coordination information further includes synchronization type information, which indicates that: a message is sent according to the start sending timestamp, a message is sent based on the time of the synchronization message trigger, or a message is sent based on the time of the synchronization message trigger and the synchronization message is triggered by other synchronization messages.

3. The communication method according to claim 2, characterized in that, The synchronization type information indicates that messages are sent according to the start timestamp. The collaborative information also includes indication information for the start sending timestamp.

4. The communication method according to claim 2, characterized in that, The synchronization type information indicates that: a message is sent based on the time triggered by the first synchronization message, or a message is sent based on the time triggered by the first synchronization message and the first synchronization message is triggered by the second synchronization message; The coordination information also includes synchronization message sending indication information, which indicates whether the first FTTR device needs to actively send a synchronization message.

5. A communication method, characterized in that, The communication method includes: Receive coordination information, the coordination information including synchronization marker information, the synchronization marker information indicating whether the first fiber-to-room FTTR device needs to transmit messages synchronously with other FTTR devices, the first FTTR device and the other FTTR devices operating on the same frequency band; Send messages based on the aforementioned collaborative information.

6. The communication method according to claim 5, characterized in that, The synchronization tag information indicates that the first FTTR device needs to synchronize message transmission with the other FTTR devices; The coordination information further includes synchronization type information, which indicates that: a message is sent according to the start sending timestamp, a message is sent based on the time of the synchronization message trigger, or a message is sent based on the time of the synchronization message trigger and the synchronization message is triggered by other synchronization messages.

7. The communication method according to claim 6, characterized in that, The synchronization type information indicates that messages are sent according to the start timestamp. The collaborative information also includes indication information for the start sending timestamp.

8. The communication method according to claim 6, characterized in that, The synchronization type information indicates that: a message is sent based on the time triggered by the first synchronization message, or a message is sent based on the time triggered by the first synchronization message and the first synchronization message is triggered by the second synchronization message; The coordination information also includes synchronization message sending indication information, which indicates whether the first FTTR device needs to actively send a synchronization message.

9. A communication device, characterized in that, Includes modules or units for performing the communication method according to any one of claims 1 to 8.

10. A communication device, characterized in that, include: A processor coupled to a memory for storing a computer program, wherein when the processor invokes the computer program, the communication device performs the communication method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, Used for storing computer programs, said computer programs including instructions for implementing the communication method as described in any one of claims 1 to 8.

12. A computer program product, the computer program product comprising instructions, characterized in that, When the instructions are executed on a computer, the computer causes the computer to implement the communication method as described in any one of claims 1 to 8.

Images