Multi-access point collaboration method, apparatus, equipment and storage medium

Abstract

This invention discloses a multi-access point collaboration method, apparatus, device, and storage medium. The method includes: a first access point sending a collaboration request message to a second access point; the second access point confirming the multi-point collaboration operation execution type requested by the first access point based on the collaboration request message, and determining whether to agree to the collaboration request based on the multi-point collaboration operation execution type requested by the first access point and whether the second access point is currently performing a multi-point collaboration operation; the second access point sending a collaboration response message to the first access point, the collaboration response message indicating whether to agree to the collaboration request. This invention categorizes multi-point collaboration operation execution types into mandatory and optional types, and an access point can only participate in one mandatory multi-point collaboration operation at a time, improving the efficiency of multi-point collaboration operations and ensuring the service quality of the target terminal.

Description

Technical Field

[0001] This invention relates to the field of wireless communication, and more particularly to a multi-access point coordination method, apparatus, device, and storage medium. Background Technology

[0002] 802.11be systems, also known as Extremely High Throughput (EHT) systems, achieve extremely high throughput through a range of system features and multiple mechanisms. With the continued growth in the use of Wireless Local Area Networks (WLANs), providing wireless data services in many environments, such as homes, businesses, and hotspots, is becoming increasingly important. In particular, video traffic will continue to be a major traffic type in many WLAN deployments. The throughput requirements for these applications are constantly evolving due to the emergence of 4K and 8K video (uncompressed rates of 20Gbps). New high-throughput, low-latency applications such as virtual reality or augmented reality, gaming, remote offices, and cloud computing will proliferate (e.g., latency of less than 5 milliseconds for real-time gaming).

[0003] Given the high throughput and stringent real-time latency requirements of these applications, users expect higher throughput, greater reliability, less latency and jitter, and higher power efficiency when supporting their applications via WLAN. 802.11be systems are designed to ensure WLAN competitiveness by further increasing overall throughput and reducing latency, while ensuring backward compatibility and coexistence with older technology standards. 802.11 compliant devices operate in the 2.4 GHz, 5 GHz, and 6 GHz bands. Summary of the Invention

[0004] When a terminal is located at the edge of an access point's coverage area or within a co-frequency coverage area, strong interference signals cause a decrease in the terminal's transmission rate. Therefore, the 802.11be system proposes a method for multiple access points to collaboratively transmit data, transforming interference signals into useful data transmission signals or reducing interference signals through collaborative processing, thereby improving the data transmission rate for edge users and the network's spectrum utilization efficiency. In view of this, the present invention provides a multi-access point collaborative method, apparatus, device, and storage medium to improve the efficiency of multi-point collaborative operation.

[0005] In a first aspect, the present invention provides a multi-access point collaboration method, comprising:

[0006] The second access point receives a collaboration request message sent by the first access point, the collaboration request message being used to request the execution of a multi-point collaboration operation;

[0007] The second access point confirms the multi-point collaborative operation execution type requested by the first access point based on the collaborative request message. The multi-point collaborative operation execution type includes mandatory and optional types.

[0008] The second access point determines whether to agree to the collaboration request based on the type of multi-point collaborative operation requested by the first access point and whether the second access point is currently performing a multi-point collaborative operation.

[0009] The second access point sends a collaboration response message to the first access point, the collaboration response message indicating whether it agrees to the collaboration request.

[0010] In one possible implementation, the second access point determines whether to agree to the collaboration request based on the type of multi-point collaboration operation requested by the first access point and whether the second access point is currently performing a multi-point collaboration operation, including one or more of the following:

[0011] If the second access point is performing a forced multipoint collaboration operation, the second access point rejects the collaboration request;

[0012] If the second access point is performing an optional multipoint coordination operation, and the first access point requests a mandatory multipoint coordination operation, then the second access point agrees to the coordination request and stops the optional multipoint coordination operation that is being performed.

[0013] If the second access point is performing an optional multipoint coordination operation, and the first access point requests an optional multipoint coordination operation, the second access point agrees to the coordination request if the resources of the optional multipoint coordination operation being performed by the second access point do not overlap with those of the optional multipoint coordination operation requested by the first access point; otherwise, the second access point rejects the coordination request.

[0014] If the second access point is not currently performing multi-point collaboration, then the second access point agrees to the collaboration request.

[0015] In one possible implementation, the collaboration request message includes at least one of an identifier of the first access point and an indication of the type of multi-point collaborative operation to be performed.

[0016] The second access point confirms, based on the collaboration request message, that the multi-point collaborative operation execution type requested by the first access point includes:

[0017] The second access point determines the type of multi-point collaborative operation requested by the first access point based on the identifier of the first access point in the collaborative request message and the multi-point collaborative information stored by the second access point. The multi-point collaborative information includes an access point identifier and the multi-point collaborative operation execution type corresponding to the access point indicated by the access point identifier; or...

[0018] The second access point confirms the multi-point collaborative operation execution type requested by the first access point based on the indication of the multi-point collaborative operation execution type requested in the collaborative request message.

[0019] In one possible implementation, before the second access point receives the collaboration request message sent by the first access point, the following steps are also included:

[0020] The second access point receives a network formation request message sent by the first access point, the network formation request message being used to request network formation;

[0021] The second access point sends a network response message to the first access point, the network response message indicating whether it agrees to the network request; and at least one of the network request message and the network response message contains a multi-point collaborative operation execution type.

[0022] The second access point stores the multi-point coordination information corresponding to the first access point. The multi-point coordination information includes the access point identifier and the multi-point coordination operation execution type corresponding to the access point indicated by the access point identifier.

[0023] If the network response message contains a multi-point collaborative operation execution type, then the multi-point collaborative operation execution type corresponding to the identifier of the first access point in the multi-point collaborative information is the same as the multi-point collaborative operation execution type in the network response message; otherwise, the multi-point collaborative operation execution type corresponding to the identifier of the first access point in the multi-point collaborative information is the same as the multi-point collaborative operation execution type in the network request message.

[0024] In one possible implementation, the multipoint collaboration information further includes an indication of whether the access point indicated by the access point identifier is performing a multipoint collaboration operation.

[0025] Secondly, the present invention provides a multi-access point collaboration method, comprising:

[0026] The first access point sends a collaboration request message to the second access point. The collaboration request message is used to request the execution of a multi-point collaboration operation, and the second access point is used to confirm the execution type of the multi-point collaboration operation requested by the first access point. The execution type of the multi-point collaboration operation includes mandatory and optional types.

[0027] The first access point receives a collaboration response message sent by the second access point, the collaboration response message indicating whether or not the collaboration request is agreed to.

[0028] In one possible implementation, the collaboration request message includes at least one of an identifier of the first access point and an indication of the requested multi-point collaborative operation execution type, which is used by the second access point to confirm the multi-point collaborative operation execution type requested by the first access point based on the identifier of the first access point or the indication of the requested multi-point collaborative operation execution type.

[0029] In one possible implementation, before the first access point sends a cooperation request message to the second access point, the following steps are also included:

[0030] The first access point sends a network formation request message to the second access point, the network formation request message being used to request network formation;

[0031] The first access point receives a network response message sent by the second access point, wherein the network response message indicates whether the network request is agreed to; and at least one of the network request message and the network response message contains a multi-point collaborative operation execution type.

[0032] The first access point stores the multi-point collaboration information corresponding to the second access point. The multi-point collaboration information includes the access point identifier and the multi-point collaboration operation execution type corresponding to the access point indicated by the access point identifier.

[0033] If the network response message contains a multi-point collaborative operation execution type, then the multi-point collaborative operation execution type corresponding to the identifier of the second access point in the multi-point collaborative information is the same as the multi-point collaborative operation execution type in the network response message; otherwise, the multi-point collaborative operation execution type corresponding to the identifier of the second access point in the multi-point collaborative information is the same as the multi-point collaborative operation execution type in the network request message.

[0034] In one possible implementation, the multipoint collaboration information further includes an indication of whether the access point indicated by the access point identifier is performing a multipoint collaboration operation.

[0035] One possible implementation also includes:

[0036] The first access point determines the type of multi-point collaborative operation to be executed in the request;

[0037] The first access point selects candidate access points that meet the multi-point collaborative operation execution type of the determined request based on the stored multi-point collaboration information; the second access point is an access point among the candidate access points.

[0038] Thirdly, the present invention provides a multi-access point collaborative device, including a collaborative module, the collaborative module being used to perform the following steps:

[0039] The second access point receives a collaboration request message sent by the first access point, the collaboration request message being used to request the execution of a multi-point collaboration operation;

[0040] The second access point confirms the multi-point collaborative operation execution type requested by the first access point based on the collaborative request message. The multi-point collaborative operation execution type includes mandatory and optional types.

[0041] The second access point determines whether to agree to the collaboration request based on the type of multi-point collaborative operation requested by the first access point and whether the second access point is currently performing a multi-point collaborative operation.

[0042] A collaboration response message is sent from the second access point to the first access point, and the collaboration response message indicates whether the collaboration request is agreed to.

[0043] Fourthly, the present invention provides a multi-access point collaborative device, including a collaborative module, the collaborative module being used to perform the following steps:

[0044] The first access point sends a collaboration request message to the second access point. The collaboration request message is used to request the execution of a multi-point collaboration operation, and the second access point is used to confirm the execution type of the multi-point collaboration operation requested by the first access point. The execution type of the multi-point collaboration operation includes mandatory and optional types.

[0045] The first access point receives a collaboration response message sent by the second access point, the collaboration response message indicating whether or not the collaboration request is agreed to.

[0046] Fifthly, the present invention provides an electronic device including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the method described in the first or second aspect.

[0047] In a sixth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method described in the first or second aspect.

[0048] In a seventh aspect, the present invention provides a computer program product comprising computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is executed in an electronic device, a processor in the electronic device performs the method described in the first aspect or the second aspect.

[0049] It should be noted that the apparatus described in the third aspect is used to perform the method provided in the first aspect, the apparatus described in the fourth aspect is used to perform the method provided in the second aspect, the electronic device described in the fifth aspect, the storage medium described in the sixth aspect, and the computer program product described in the seventh aspect are used to perform the method provided in the first or second aspect. Therefore, they can achieve the same beneficial effects as the method described in the first or second aspect, and will not be described in detail hereafter.

[0050] This invention categorizes multi-point collaborative operation execution types into mandatory and optional types, and an access point can only participate in one mandatory multi-point collaborative operation at a time, thereby improving the efficiency of multi-point collaborative operations and ensuring the service quality of the target terminal. Attached Figure Description

[0051] Figure 1 A schematic diagram of the structure of a communication system provided in an embodiment of the present invention;

[0052] Figure 2 A flowchart of a multi-access point collaboration method provided in an embodiment of the present invention;

[0053] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0054] To enable those skilled in the art to better understand the technical solutions of this invention, the technical solutions in the embodiments of this invention will be clearly and completely described below. Obviously, the described embodiments are only some embodiments of this invention, and not all embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this invention and are not intended to limit this invention. Although the disclosure in this invention is presented according to one or several exemplary examples, it should be understood that each aspect of these disclosures can constitute a complete technical solution on its own. Without conflict, the following embodiments and features described herein can be combined with each other.

[0055] In the embodiments of the present invention, "at least one" refers to one or more, and "more than one" refers to two or more. To facilitate a clear description of the technical solutions of the embodiments of the present invention, the terms "first," "second," etc., are used to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order; they are only used for illustration and differentiation of the described objects, and do not indicate any particular limitation on the number of devices or messages in the embodiments of the present invention, nor do they constitute any limitation on the embodiments of the present invention. The term "comprising" is used to indicate the presence of the feature subsequently declared, but does not exclude the addition of other features.

[0056] First, a brief explanation of the multi-point collaborative operation execution types involved in this invention is given. The multi-point collaborative operation execution types include mandatory and optional types. The mandatory type means that the multi-point collaborative operation must be executed, while the optional type means that the multi-point collaborative operation can be executed selectively. An access point can participate in multiple optional multi-point collaborative operations at the same time, but can only participate in one mandatory multi-point collaborative operation at the same time.

[0057] Figure 1 This is a schematic diagram of a communication system provided in an embodiment of the present invention. Figure 1 As shown, the communication system includes three access points, P-AP1, S-AP1, and S-AP2. These three access points can connect to terminals themselves and can also connect to other access points.

[0058] It should be understood that Figure 1 This is merely a schematic diagram of a communication system architecture. The number and type of devices in the communication system are not limited in this embodiment of the invention, and may include more access points. Furthermore, those skilled in the art will understand that, based on the principles and functions described herein, the term "access point (AP)" in this application can also be used to describe an access port or any other access point capable of receiving and transmitting wireless signals within a network architecture. Therefore, the use of "access point" is merely exemplary.

[0059] The general inventive concept of this invention is as follows: Figure 2 As shown, the process includes the following: a first access point sends a collaboration request message to a second access point, requesting the execution of a multi-point collaboration operation; the second access point confirms the type of multi-point collaboration operation requested by the first access point based on the received collaboration request message, and determines whether to agree to the collaboration request based on the type of multi-point collaboration operation requested by the first access point and whether the second access point is currently executing a multi-point collaboration operation; the second access point sends a collaboration response message to the first access point, the collaboration response message indicating whether to agree to the collaboration request.

[0060] The following combination Figure 1 The communication system shown further illustrates the present invention. In the following embodiments, access point P-AP1 is the requester of multi-point cooperative operation, and S-AP1 and S-AP2 are the responders of multi-point cooperative operation.

[0061] S101 and P-AP1 send a coordination request message to S-AP1, requesting the execution of a multi-point coordination operation.

[0062] The collaboration request message contains address information such as the message sender address (TA) and the message receiver address (RA), with TA set to the address of the first access point and RA set to the address of the second access point.

[0063] In some embodiments, the collaboration request message may also include one or more of the following parameters:

[0064] Operation type: The type of multi-point collaborative operation execution. If set to M, it indicates a mandatory type; if set to O, it indicates an optional type. In this embodiment, it is set to M.

[0065] STA info: Terminal information, such as the terminal's identifier (e.g., address), multi-point cooperative operation mode, channel status information reported by the terminal, etc.

[0066] AP ID: The identifier of the access point, such as the address of the access point or other values ​​that can identify the access point. In this embodiment, it is set to the address of P-AP1.

[0067] S102 and S-AP1 confirm the type of multi-point collaborative operation requested by P-AP1 based on the received collaborative request message.

[0068] The following is an example of how S-AP1 confirms the multi-point collaborative operation execution type requested by P-AP1:

[0069] If the collaboration request message received by S-AP1 contains the parameter "Operation type", the multi-point collaboration operation execution type of the P-AP1 request can be determined directly based on the value of this parameter.

[0070] If the coordination request message received by S-AP1 contains the parameter STA info, S-AP1 can determine the type of multipoint coordination operation requested by P-AP1 based on the terminal's information. If the STA info indicates that the multipoint coordination operation mode is C-OFDMA or C-BF, then P-AP1 is confirmed to be requesting an optional multipoint coordination operation. If it indicates JT mode, then P-AP1 is confirmed to be requesting a mandatory multipoint coordination operation. If the STA info contains channel state information reported by the terminal indicating high interference, then P-AP1 is confirmed to be requesting an optional multipoint coordination operation. If the interference is low, then P-AP1 is confirmed to be requesting a mandatory multipoint coordination operation.

[0071] Among them, C-BF mode: cooperative beamforming mode. In this cooperative mode, the beamforming angle of other access points is adjusted according to the beamforming angle of the terminal and the access point communicating with it, so as to reduce interference.

[0072] C-OFDMA mode: Cooperative Orthogonal Frequency Division Multiple Access. In this cooperative mode, multiple access points are coordinated to use orthogonal time and frequency resources for data transmission, turning interference signals into useful data transmission signals.

[0073] JT mode: Joint transmission mode. In this cooperative mode, multiple access points simultaneously transmit data to the terminal or simultaneously receive data transmitted by the terminal under the same time and frequency resources.

[0074] If the collaboration request message received by S-AP1 contains the parameter AP ID, S-AP1 can query the locally stored multipoint collaboration information based on the address of P-AP1 to confirm the type of multipoint collaboration operation to be executed by P-AP1. An example of the multipoint collaboration information stored by S-AP1 is shown in Table 1.

[0075] Table 1

[0076] Access point identifier Multi-point collaborative operation execution type P-AP1 M P-AP2 O P-AP3 O

[0077] In Table 1, P-AP1, P-AP2, and P-AP3 indicate that S-AP1 can perform multipoint collaborative operations with these three access points. The multipoint collaborative operation performed with P-AP1 is a mandatory multipoint collaborative operation, while the multipoint collaborative operation performed with P-AP2 and P-AP3 is an optional multipoint collaborative operation.

[0078] Optionally, S-AP1 can also query locally stored multipoint collaboration information based on the TA in the received collaboration request message to confirm the type of multipoint collaboration operation to be executed by P-AP1.

[0079] S-AP1 allows for manual configuration of multi-point collaboration information during setup, or for access points to negotiate and configure multi-point collaboration information during network formation. An example of the latter configuration method is shown below:

[0080] S2001 and P-AP1 send a network formation request message to request network formation. P-AP1 can send the network formation request in the form of broadcast or unicast to a specific access point. In this embodiment, it is assumed that P-AP1 sends a network formation request message to S-AP1 and S-AP2.

[0081] Optionally, the network request message may include the following parameters:

[0082] Operation type: The type of multi-point collaborative operation execution. If set to M, it indicates a mandatory type; if set to O, it indicates an optional type. In this embodiment, it is set to M.

[0083] S2002, S-AP1 reads the networking request message sent by P-AP1 and sends a networking response message to P-AP1. The networking response message indicates whether the networking request is agreed to. In this embodiment, it is assumed that S-AP1 agrees to P-AP1's networking request.

[0084] Optionally, the network request message may include the following parameters:

[0085] Operation type: The type of multi-point collaborative operation execution. If set to M, it indicates a mandatory type; if set to O, it indicates an optional type. In this embodiment, it is set to M.

[0086] S2003 and S-AP1 store the multi-point coordination information corresponding to P-AP1 locally, as shown in Table 1. P-AP1 stores the multi-point coordination information corresponding to S-AP1 locally, as shown in Table 2.

[0087] Table 2

[0088]

[0089]

[0090] S2004, S-AP2 reads the networking request message sent by P-AP1 and sends a networking response message to P-AP1. The networking response message indicates whether it agrees to the networking request. In this embodiment, it is assumed that S-AP2 agrees to P-AP1's networking request.

[0091] Optionally, the network request message may include the following parameters:

[0092] Operation type: The type of multi-point collaborative operation execution. If set to M, it indicates a mandatory type; if set to O, it indicates an optional type. In this embodiment, it is set to O.

[0093] S2005 and S-AP2 store the multi-point collaboration information corresponding to P-AP1 locally, as shown in Table 3.

[0094] Table 3

[0095] Access point identifier Multi-point collaborative operation execution type P-AP1 O

[0096] P-AP1 stores the multi-point collaboration information corresponding to S-AP2 locally, as shown in Table 4.

[0097] Table 4

[0098] Access point identifier Multi-point collaborative operation execution type S-AP1 M S-AP2 O

[0099] The networking requests initiated by P-AP2 and P-AP3 can be referred to in steps S2001-S2005 above, and will not be described in detail here. It should be noted that even if P-AP2 or P-AP3 sets the value of the Operation type parameter to "M" in the networking request message, S-AP1 can only confirm the execution of optional multipoint cooperative operation with P-AP2 and P-AP3, that is, in the cooperative response message sent to P-AP2 and P-AP3, the value of the Operation type parameter is set to "O", because S-AP1 has already confirmed the execution of mandatory multipoint cooperative operation with P-AP1.

[0100] S103 and S-AP1 determine whether to agree to the collaboration request based on the multi-point collaboration operation execution type requested by P-AP1 and whether S-AP1 is currently performing a multi-point collaboration operation, and send a collaboration response message to P-AP1, which indicates whether to agree to the collaboration request.

[0101] In step S102, S-AP1 confirms that P-AP1 is requesting a mandatory multipoint collaboration operation. If S-AP1 has already performed a mandatory multipoint collaboration operation, it sets the value of the parameter status to "refuse" to indicate that the collaboration request is rejected. If S-AP1 has not yet performed a mandatory multipoint collaboration operation, that is, S-AP1 is currently performing an optional multipoint collaboration operation or has not performed a multipoint collaboration operation, it sets the value of the parameter status to "agree" to indicate that the collaboration request is agreed to. Then, it includes the parameter status in the collaboration response message and sends it to P-AP1, and stops the currently executing optional multipoint collaboration operation.

[0102] In some embodiments, the multipoint collaboration information stored locally by each access point may also include an indication of whether a multipoint collaboration operation is being performed, such as the example of multipoint collaboration information stored by S-AP1 shown in Table 5.

[0103] Table 5

[0104] Access point identifier Multi-point collaborative operation execution type Is a multi-point collaborative operation being performed? P-AP1 M 0 P-AP2 O 1 P-AP3 O 0

[0105] It should be understood that S-AP1 can also use other methods to indicate whether it is performing a mandatory multipoint cooperative operation, such as saving the parameter OP MODE locally. Setting it to "M" indicates that a mandatory multipoint cooperative operation is currently being performed, setting it to "O" indicates that an optional multipoint cooperative operation is currently being performed, and setting it to empty indicates that a multipoint cooperative operation is not currently being performed. In addition, the resources of the optional multipoint cooperative operation that is currently being performed can also be saved.

[0106] This embodiment assumes that S-AP1 is performing an optional multipoint cooperative operation with P-AP2. In the cooperative response message sent by S-AP1 to P-AP1, the value of the status parameter is set to "agree", and a cooperative termination message is sent to P-AP2 to indicate the termination of the multipoint cooperative operation.

[0107] S104 and P-AP1 send a coordination request message to S-AP2, requesting the execution of a multi-point coordination operation.

[0108] S105 and S-AP2 confirm the type of multi-point collaborative operation requested by P-AP1 based on the received collaborative request message.

[0109] The specific implementation of steps S104-S105 can be referred to steps S101-S102, and will not be described in detail here. The difference is that S-AP2 confirms that P-AP1 is requesting an optional multi-point collaborative operation.

[0110] S106, S-AP2 determines whether to agree to the collaboration request based on the multipoint collaboration operation execution type requested by P-AP1 and whether S-AP2 is currently performing a multipoint collaboration operation, and sends a collaboration response message to P-AP1, indicating whether to agree to the collaboration request.

[0111] In step S105, S-AP2 confirms that P-AP1 is requesting an optional multipoint coordination operation. If S-AP2 has already executed a mandatory multipoint coordination operation, it sets the value of the `status` parameter to "refuse," indicating that the coordination request is rejected. If S-AP2 is currently executing an optional multipoint coordination operation, and the resources of the optional multipoint coordination operation requested by P-AP1 do not overlap with the resources of the optional multipoint coordination operation currently being executed by S-AP2, it sets the value of the `status` parameter to "agree," indicating that the coordination request is agreed upon. In this case, S-AP2 can execute multiple optional multipoint coordination operations. If the resources of the optional multipoint coordination operation requested by P-AP1 overlap with the resources of the optional multipoint coordination operation currently being executed by S-AP2, it sets the value of the `status` parameter to "refuse," indicating that the coordination request is rejected. If S-AP2 is not currently executing a multipoint coordination operation, it sets the value of the `status` parameter to "agree," indicating that the coordination request is agreed upon. Then, the `status` parameter is included in the coordination response message and sent to P-AP1.

[0112] S107, P-AP1, and S-AP1 and S-AP2 perform multi-point cooperative operations.

[0113] In some embodiments, after P-AP1 locally stores multi-point coordination information, it can first determine the multi-point coordination operation execution type, and then only send coordination request messages to access points that meet the determined multi-point coordination operation execution type, thereby reducing unnecessary signaling overhead. P-AP1 can determine the multi-point coordination operation execution type according to its own policy, or it can determine the multi-point coordination operation execution type according to the request of the multi-point coordination operation initiator.

[0114] For example, after receiving a multipoint cooperative operation request from a terminal, P-AP1 determines the type of multipoint cooperative operation to be executed based on the request. If the multipoint cooperative operation request indicates the requested multipoint cooperative operation mode, such as C-OFDMA or C-BF mode, then it determines to execute optional multipoint cooperative operation and sends a cooperative request message to the access points that can participate in optional multipoint cooperative operation based on the locally stored multipoint cooperative information, or sends a cooperative request message to the access points that can participate in both optional and mandatory multipoint cooperative operation; if it is JT mode, then it determines to execute mandatory multipoint cooperative operation and sends a cooperative request message to the access points that can participate in mandatory multipoint cooperative operation based on the locally stored multipoint cooperative information. If the multipoint cooperative operation request includes the terminal's channel state information, and the interference is high, then a mandatory multipoint cooperative operation is determined to be performed. Based on the locally stored multipoint cooperative information, a cooperative request message is sent to the access points that can participate in the mandatory multipoint cooperative operation. If the interference is low, then an optional multipoint cooperative operation is determined to be performed. Based on the locally stored multipoint cooperative information, a cooperative request message is sent to the access points that can participate in the optional multipoint cooperative operation, or a cooperative request message is sent to the access points that can participate in both the optional and mandatory multipoint cooperative operations.

[0115] This invention also provides a multi-access point collaborative device, including a collaborative module, which is used to perform the following steps:

[0116] The second access point receives a collaboration request message sent by the first access point, the collaboration request message being used to request the execution of a multi-point collaboration operation;

[0117] The second access point confirms the multi-point collaborative operation execution type requested by the first access point based on the collaborative request message. The multi-point collaborative operation execution type includes mandatory and optional types.

[0118] The second access point determines whether to agree to the collaboration request based on the type of multi-point collaborative operation requested by the first access point and whether the second access point is currently performing a multi-point collaborative operation.

[0119] A collaboration response message is sent from the second access point to the first access point, and the collaboration response message indicates whether the collaboration request is agreed to.

[0120] In an optional example, those skilled in the art will understand that the above-described device may specifically be S-AP1 or S-AP2 in the above embodiments. The device may be used to execute the various processes and / or steps corresponding to S-AP1 or S-AP2 in the above method. To avoid repetition, it will not be described again here.

[0121] This invention also provides a multi-access point collaborative device, including a collaborative module, which is used to perform the following steps:

[0122] The first access point sends a collaboration request message to the second access point. The collaboration request message is used to request the execution of a multi-point collaboration operation, and the second access point is used to confirm the execution type of the multi-point collaboration operation requested by the first access point. The execution type of the multi-point collaboration operation includes mandatory and optional types.

[0123] The first access point receives a collaboration response message sent by the second access point, the collaboration response message indicating whether or not the collaboration request is agreed to.

[0124] In an optional example, those skilled in the art will understand that the above-described device may specifically be P-AP1 in the above embodiments. This device can be used to execute the various processes and / or steps corresponding to P-AP1 in the above method. To avoid repetition, it will not be described again here.

[0125] It should be understood that the device described here is embodied in the form of functional modules. The term "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memories for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. The device described above has the function of implementing the corresponding steps in the described method; the functions described above can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. In embodiments of the present invention, the device can also be a chip or a chip system, such as a system-on-a-chip (SoC). The present invention is not limited thereto.

[0126] This invention also provides an electronic device. Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Figure 3 As shown, device 300 includes processor 301, memory 302 and communication interface 303. The processor 301, memory 302 and communication interface 303 communicate with each other through bus 304. The memory 302 stores instructions that can be executed by the processor 301. The instructions are loaded and executed by the processor 301 to control the communication interface 303 to send and / or receive signals.

[0127] It should be understood that device 300 may specifically be P-AP1, S-AP1, or S-AP2 in the above embodiments, or the functions of P-AP1, S-AP1, or S-AP2 in the above embodiments may be integrated into device 300, and device 300 may be used to execute the various steps and / or processes corresponding to P-AP1, S-AP1, or S-AP2 in the above embodiments. Optionally, memory 302 may include read-only memory and random access memory, and provide instructions and data to processor 301. A portion of memory 302 may also include non-volatile random access memory. For example, memory 302 may also store device type information. Processor 301 may be used to execute instructions stored in memory 301, and when processor 301 executes the instructions, processor 301 may execute the corresponding various steps and / or processes in the above method embodiments.

[0128] It should be understood that, in this embodiment of the invention, the processor may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0129] In implementation, each step of the above method can be completed by integrated logic circuits in the processor hardware or by instructions in software. The steps of the method disclosed in the embodiments of this invention can be directly manifested as execution by a hardware processor, or as a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor executes the instructions in the memory, combining them with its hardware to complete the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0130] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) 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 includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0131] It should be understood that in the various embodiments of the present invention, the sequence number of each process 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 the present invention. Modules described as separate components may or may not be physically separate. Components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the embodiments of the present invention.

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

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

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

Claims

1. A multi-access point coordination method, characterized by, The method comprises the following steps: The second access point receives a coordination request message sent by the first access point, and the coordination request message is used for requesting to perform a multi-point coordination operation; The second access point confirms the multi-point coordination operation execution type requested by the first access point according to the coordination request message, and the multi-point coordination operation execution type comprises a forced type and an optional type; The second access point judges whether to agree with the coordination request according to the multi-point coordination operation execution type requested by the first access point and whether the second access point is performing a multi-point coordination operation, and specifically comprises the following steps: If the second access point is performing a forced multi-point coordination operation, the second access point refuses the coordination request; If the second access point is performing an optional multi-point coordination operation, and the first access point requests a forced multi-point coordination operation, the second access point agrees with the coordination request and stops the optional multi-point coordination operation being performed; If the second access point is performing an optional multi-point coordination operation, and the first access point requests an optional multi-point coordination operation, when the optional multi-point coordination operation being performed by the second access point does not overlap with the resource of the optional multi-point coordination operation requested by the first access point, the second access point agrees with the coordination request; When the optional multi-point coordination operation being performed by the second access point overlaps with the resource of the optional multi-point coordination operation requested by the first access point, the second access point refuses the coordination request; 2. The method of claim 1, wherein, If the second access point is not performing a multi-point coordination operation at present, the second access point agrees with the coordination request; The second access point sends a coordination response message to the first access point, and the coordination response message indicates whether to agree with the coordination request. The coordination request message comprises at least one of the following two: the identity of the first access point and the indication of the multi-point coordination operation execution type requested by the first access point; The second access point confirms the multi-point coordination operation execution type requested by the first access point according to the coordination request message, and the multi-point coordination operation execution type comprises:

3. The method of claim 1, wherein, The second access point confirms the multi-point coordination operation type requested by the first access point according to the identity of the first access point in the coordination request message and the multi-point coordination information saved by the second access point, and the multi-point coordination information comprises the identity of an access point and the multi-point coordination operation execution type corresponding to the access point indicated by the identity of the access point; or The second access point confirms the multi-point coordination operation execution type requested by the first access point according to the indication of the multi-point coordination operation execution type requested by the first access point in the coordination request message. Before the second access point receives the coordination request message sent by the first access point, the method further comprises the following steps: The second access point receives a networking request message sent by the first access point, and the networking request message is used for requesting networking; The second access point sends a networking response message to the first access point, and the networking response message indicates whether to agree with the networking request; and at least one of the networking request message and the networking response message comprises the multi-point coordination operation execution type; The second access point saves the multi-point coordination information corresponding to the first access point, and the multi-point coordination information comprises the identity of an access point and the multi-point coordination operation execution type corresponding to the access point indicated by the identity of the access point; If the multi-point cooperative operation execution type is contained in the networking response message, the multi-point cooperative operation execution type corresponding to the identification of the first access point in the multi-point cooperative information is same as the multi-point cooperative operation execution type in the networking response message; otherwise, the multi-point cooperative operation execution type corresponding to the identification of the first access point in the multi-point cooperative information is same as the multi-point cooperative operation execution type in the networking request message.

4. The multi-access point coordination method of claim 2 or 3, wherein, The multi-point cooperative information further comprises an indication of whether the access point indicated by the access point identification is performing the multi-point cooperative operation.

5. A multi-access point coordination method, characterized by, The method comprises: The first access point sends a cooperative request message to the second access point, the cooperative request message being used for requesting to perform the multi-point cooperative operation and being used for the second access point to confirm the multi-point cooperative operation execution type requested by the first access point, the multi-point cooperative operation execution type comprising a forced type and an optional type, wherein the second access point judges whether to agree to the cooperative request according to the multi-point cooperative operation execution type requested by the first access point and whether the second access point is performing the multi-point cooperative operation, and the judgment specifically comprises: if the second access point is performing the forced type multi-point cooperative operation, the second access point rejects the cooperative request; if the second access point is performing the optional type multi-point cooperative operation and the first access point requests the forced type multi-point cooperative operation, the second access point agrees to the cooperative request and stops the optional type multi-point cooperative operation being performed; if the second access point is performing the optional type multi-point cooperative operation and the first access point requests the optional type multi-point cooperative operation, when the optional type multi-point cooperative operation being performed by the second access point does not overlap with the resource of the optional type multi-point cooperative operation requested by the first access point, the second access point agrees to the cooperative request; when the optional type multi-point cooperative operation being performed by the second access point overlaps with the resource of the optional type multi-point cooperative operation requested by the first access point, the second access point rejects the cooperative request; if the second access point is not currently performing the multi-point cooperative operation, the second access point agrees to the cooperative request. The first access point receives the cooperative response message sent by the second access point, the cooperative response message indicating whether to agree to the cooperative request.

6. The method of claim 5, wherein, The cooperative request message comprises at least one of the identification of the first access point and the indication of the requested multi-point cooperative operation execution type, and is used for the second access point to confirm the multi-point cooperative operation execution type requested by the first access point according to the identification of the first access point or the indication of the requested multi-point cooperative operation execution type.

7. The method of claim 5, wherein, Before the first access point sends the cooperative request message to the second access point, the method further comprises: The first access point sends a networking request message to the second access point, the networking request message being used for requesting networking; The first access point receives a networking response message sent by the second access point, the networking response message indicating whether to agree to the networking request; and at least one of the networking request message and the networking response message comprises a multi-point cooperative operation execution type; The first access point saves multi-point cooperative information corresponding to the second access point, the multi-point cooperative information comprising an access point identification and a multi-point cooperative operation execution type corresponding to the access point indicated by the access point identification; If the multi-point cooperative operation execution type is contained in the networking response message, the multi-point cooperative operation execution type corresponding to the identification of the second access point in the multi-point cooperative information is the same as the multi-point cooperative operation execution type in the networking response message; otherwise, the multi-point cooperative operation execution type corresponding to the identification of the second access point in the multi-point cooperative information is the same as the multi-point cooperative operation execution type in the networking request message.

8. The method of claim 7, wherein, The multi-point cooperative information further comprises an indication of whether the multi-point cooperative operation is being performed by the access point indicated by the access point identification.

9. The method of claim 7, wherein, Further comprising: The first access point determines the requested multi-point cooperative operation execution type; The first access point selects a candidate access point satisfying the determined requested multi-point cooperative operation execution type according to the saved multi-point cooperative information; The second access point is an access point in the candidate access points.

10. A multi-access point coordination apparatus, comprising: The coordination module is configured to perform the following steps: The second access point receives a coordination request message sent by the first access point, the coordination request message being used for requesting to perform a multi-point cooperative operation; The second access point confirms the multi-point cooperative operation execution type requested by the first access point according to the coordination request message, the multi-point cooperative operation execution type comprising a forced type and an optional type; The second access point judges whether to agree to the coordination request according to the multi-point cooperative operation execution type requested by the first access point and whether the second access point is performing a multi-point cooperative operation, specifically comprising that if the second access point is performing a forced type multi-point cooperative operation, the second access point rejects the coordination request; If the second access point is performing an optional type multi-point cooperative operation and the first access point requests a forced type multi-point cooperative operation, the second access point agrees to the coordination request and stops the optional type multi-point cooperative operation being performed; if the second access point is performing an optional type multi-point cooperative operation and the first access point requests an optional type multi-point cooperative operation, when the optional type multi-point cooperative operation being performed by the second access point does not overlap with the resource of the optional type multi-point cooperative operation requested by the first access point, the second access point agrees to the coordination request; When the optional type multi-point cooperative operation being performed by the second access point overlaps with the resource of the optional type multi-point cooperative operation requested by the first access point, the second access point rejects the coordination request; If the second access point is not currently performing a multi-point cooperative operation, the second access point agrees to the coordination request; The second access point sends a coordination response message to the first access point, the coordination response message indicating whether to agree to the coordination request.

11. A multi-access point coordination apparatus, comprising: The coordination module is configured to perform the following steps: The first access point sends a coordination request message to the second access point, the coordination request message being used to request to perform the multipoint coordination operation and being used for the second access point to confirm the multipoint coordination operation execution type requested by the first access point, the multipoint coordination operation execution type including a forced type and an optional type, wherein the second access point judges whether to agree to the coordination request according to the multipoint coordination operation execution type requested by the first access point and whether the second access point is performing the multipoint coordination operation, and specifically includes: if the second access point is performing the forced type multipoint coordination operation, the second access point rejects the coordination request; if the second access point is performing the optional type multipoint coordination operation and the first access point requests the forced type multipoint coordination operation, the second access point agrees to the coordination request and stops the optional type multipoint coordination operation being performed; if the second access point is performing the optional type multipoint coordination operation and the first access point requests the optional type multipoint coordination operation, when the optional type multipoint coordination operation being performed by the second access point does not overlap with the resource of the optional type multipoint coordination operation requested by the first access point, the second access point agrees to the coordination request; when the optional type multipoint coordination operation being performed by the second access point overlaps with the resource of the optional type multipoint coordination operation requested by the first access point, the second access point rejects the coordination request; if the second access point is not currently performing the multipoint coordination operation, the second access point agrees to the coordination request. The first access point receives a coordination response message sent by the second access point, the coordination response message indicating whether to agree to the coordination request.

12. An electronic device comprising a memory, a processor, and a computer program stored on the memory, wherein the computer program, when executed by the processor, is arranged to perform the method of any one of claims 1 to 11. The processor executes the computer program to implement the method of any one of claims 1-9.

13. A computer readable storage medium having stored thereon a computer program, characterized in that The computer program is executed by the processor to implement the method of any one of claims 1-9.

Images