Multi-access point coordination

Abstract

Embodiments of the present disclosure relate to multiple access point coordination. An apparatus, method, and computer program are described that include receiving, at a first node of a wireless communication network, MAPC parameter set data from one or more other nodes of the wireless communication network, wherein each MAPC parameter set data comprises: MAPC capability information identifying one or more MAPC features supported by the corresponding other node, and details of supported functionality of each identified supported MAPC feature; exchanging information for establishing or modifying an MAPC group with one or more of the other nodes, the MAPC group being usable to define coordination between the nodes of the MAPC group; and performing one or more features defined by one or more management frames received from one or more of the other nodes according to the defined coordination.

Description

Technical Field

[0001] Example embodiments relate to multiple access point coordination (MAPC), and more particularly, to systems, methods, and / or computer programs for defining and using multiple access point coordination parameters. Background Art

[0002] For example, consider the use of different types of Multiple Access Point Coordination (MAPC) in Wi-Fi networks. Summary of the Invention

[0003] The independent claims define the scope of protection of various embodiments of the present invention. Embodiments and features described in this specification that do not belong to the scope of the independent claims (if any) are to be construed as examples that help to understand various embodiments of the present invention.

[0004] According to a first aspect, an apparatus is described that includes: means for receiving, at a first node of a wireless communication network (e.g., a Wi-Fi network), multi-access point coordination (MAPC) parameter set data from one or more other nodes of the wireless communication network (e.g., from each other node of the network), wherein each MAPC parameter set data includes: MAPC capability information identifying one or more MAPC features supported by the respective other node, and details of supported functionality for each identified supported MAPC feature; means for providing the MAPC parameter set data of the first node to one or more of the other nodes of the wireless communication network; means for exchanging (e.g., using direct and / or relayed messages) information with one or more of the other nodes for establishing or modifying (e.g., updating or terminating) a MAPC group that can be used to define coordination between nodes of the MAPC group; and means for executing one or more features defined by one or more management frames received from one or more of the other nodes in accordance with the defined coordination. The apparatus may be the first node. Alternatively, the apparatus may form part of the first node or may be accessible by the first node (e.g., provided remotely from the first node).

[0005] The means for receiving the MAPC parameter set data may include means for receiving data broadcast by one or more of the nodes.

[0006] The means for providing the MAPC parameter set data for the first node may comprise means for broadcasting the data.

[0007] Some example embodiments further include: means for sending (e.g., broadcasting) a request (e.g., a probe request) to a node of the wireless communication network (e.g., the node identified in the request), the request requesting coordination information from the node of the wireless communication network; and means for receiving a response from the node in response to the request for coordination information, wherein the response includes: MAPC parameter set data for the corresponding node. The response may be a probe response. The probe response may be a directed message (e.g., with a destination address set to the ID of the device to which the probe request was sent / broadcasted in response).

[0008] Some example embodiments further comprise: means for receiving a request from one of the nodes to provide coordination information to the node; and means for sending a response to the request to the node, wherein the response comprises: MAPC parameter set data for the first node.

[0009] The MAPC parameter set data may be received or provided (eg, exchanged) as part of beacon frames exchanged between the respective nodes. The MAPC parameter set data may be received or provided (eg, exchanged) as part of probe response messages exchanged between the respective nodes.

[0010] The means for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: means for sending an authentication request from the first node to one of the other nodes, the authentication request requesting authentication by the other node; and means for receiving an authentication response from the other node in response to the authentication request, wherein the authentication response is used to establish a trusted setup between at least some of the nodes of the MAPC group, the at least some of the nodes including the first node. The authentication may be performed by an identified leader node of the MAPC group.

[0011] The means for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: means for receiving, at a first node, an authentication request from one of the other nodes, the authentication request requesting authentication by the first node; and means for providing an authentication response in response to the authentication request, wherein the response is used to establish a trusted setup between at least some of the nodes of the MAPC group, the at least some of the nodes including the first node and the other nodes. The authentication may be performed by an identified leader node of the MAPC group.

[0012] The means for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: a means for sending an association request to a node of the wireless communication network, the association request requesting the addition of a new node to the MAPC group, the request including: the agreed coordination capabilities of the new node; and a means for receiving an association response from the node in response to the authentication request, wherein the response includes: the agreed capabilities of the new node.

[0013] The means for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: a means for receiving an association request at a first node, the association request requesting the addition of a new node to the MAPC group, the request including: the agreed-upon coordination capabilities of the new node; and a means for providing an association response in response to the authentication request, wherein the response includes: the agreed-upon capabilities of the new node.

[0014] Some example embodiments further comprise means for exchanging one or more MAPC management frames between at least two nodes of the MAPC group, wherein the or each MAPC management frame comprises a MAPC header and one or more information elements defining features to be performed by the MAPC group.

[0015] Some example embodiments further include means for modifying coordination between nodes of the group in response to a MAPC management frame. The means for modifying coordination between nodes of the group may include means for exchanging management frames between at least two nodes of the MAPC group, the management frames indicating the removal of the identified node from the MAPC group. Example management frames include deauthentication management frames or disassociation management frames. Such management frames may be exchanged directly or using relay messages. The management frame indicating the removal of the identified node may include a reason code providing a reason for the removal and an identifier identifying the MAPC group.

[0016] For example, each of the nodes may be an access point multi-link device (AP-MLD).

[0017] According to a second aspect, a method is described, comprising: receiving, at a first node of a wireless communication network (e.g., a Wi-Fi network), multi-access point coordination (MAPC) parameter set data from one or more other nodes of the wireless communication network (e.g., from each other node of the network), wherein each MAPC parameter set data comprises: MAPC capability information identifying one or more MAPC features supported by the respective other nodes, and details of the supported functionality of each identified supported MAPC feature; exchanging (e.g., using direct and / or relay messages) information with one or more of the other nodes for establishing or modifying (e.g., updating or terminating) a MAPC group, wherein the MAPC group can be used to define coordination between nodes of the MAPC group; and performing, in accordance with the defined coordination, one or more features defined by one or more management frames received from one or more of the other nodes.

[0018] Receiving the MAPC parameter set data may include receiving data broadcast by one or more of the nodes.

[0019] The method may further include providing MAPC parameter set data for the first node (eg, by broadcasting the data).

[0020] Some example embodiments further include: sending (e.g., broadcasting) a request to a node of the wireless communication network (e.g., the node identified in the request), the request requesting coordination information from the node of the wireless communication network; and receiving a response from the node in response to the request for coordination information, wherein the response includes: MAPC parameter set data for the corresponding node. The response may be a probe response. The probe response may be a directed message (e.g., with a destination address set to the ID of the device to which the probe request was sent / broadcasted in response).

[0021] The MAPC parameter set data may be received or provided (eg, exchanged) as part of beacon frames or probe response messages exchanged between respective nodes.

[0022] Exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: sending an authentication request from the first node to one of the other nodes, the authentication request requesting authentication by the other node; and receiving an authentication response from the other node in response to the authentication request, wherein the authentication response is used to establish a trusted setup between at least some of the nodes of the MAPC group, the at least some of the nodes including the first node. The authentication may be performed by an identified leader node of the MAPC group.

[0023] Exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: receiving, at a first node, an authentication request from one of the other nodes, the authentication request requesting authentication by the first node; and providing an authentication response in response to the authentication request, wherein the response is used to establish a trusted setup between at least some of the nodes of the MAPC group, the at least some of the nodes including: the first node and the other nodes. The authentication may be performed by an identified leader node of the MAPC group.

[0024] Exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: sending an association request to a node of the wireless communication network, the association request requesting the addition of a new node to the MAPC group, the request including: the agreed coordination capabilities of the new node; and receiving an association response from the node in response to the authentication request, wherein the response includes: the agreed capabilities of the new node.

[0025] Exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: receiving an association request at a first node requesting the addition of a new node to the MAPC group, the request including: agreed-upon coordination capabilities of the new node; and providing an association response in response to the authentication request, wherein the response includes: the agreed-upon capabilities of the new node.

[0026] Some example embodiments further comprise exchanging one or more MAPC management frames between at least two nodes of the MAPC group, wherein the or each MAPC management frame comprises a MAPC header and one or more information elements defining features to be performed by the MAPC group.

[0027] Some example embodiments further include modifying coordination between nodes of the group in response to a MAPC management frame. Modifying coordination between nodes of the group may include exchanging management frames between at least two nodes of the MAPC group, the management frames indicating removal of the identified node from the MAPC group. Example management frames include deauthentication management frames or disassociation management frames. Such management frames may be exchanged directly or using relay messages. The management frame indicating removal of the identified node may include a reason code providing a reason for the removal and an identifier identifying the MAPC group.

[0028] According to a third aspect, a method is described, comprising: providing MAPC parameter set data of a first node to one or more other nodes of a wireless communication network (e.g., a Wi-Fi network); exchanging information for establishing or modifying a MAPC group with one or more other nodes of the other nodes (e.g., using direct and / or relay messages), wherein the MAPC group can be used to define coordination between nodes of the MAPC group, the nodes including the first node; and performing one or more features defined by one or more management frames received from one or more other nodes of the other nodes in accordance with the defined coordination.

[0029] Providing the MAPC parameter set data to the first node may include broadcasting the data.

[0030] Some example embodiments further comprise: receiving a request from one of the nodes to provide coordination information to the node; and sending a response to the request to the node, wherein the response comprises: MAPC parameter set data for the first node.

[0031] The MAPC parameter set data may be received or provided (eg, exchanged) as part of beacon frames or probe response messages exchanged between respective nodes.

[0032] Exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: sending an authentication request from the first node to one of the other nodes, the authentication request requesting authentication by the other node; and receiving an authentication response from the other node in response to the authentication request, wherein the authentication response is used to establish a trusted setup between at least some of the nodes of the MAPC group, the at least some of the nodes including the first node. The authentication may be performed by an identified leader node of the MAPC group.

[0033] Exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: receiving, at a first node, an authentication request from one of the other nodes, the authentication request requesting authentication by the first node; and providing an authentication response in response to the authentication request, wherein the response is used to establish a trusted setup between at least some of the nodes of the MAPC group, the at least some of the nodes including: the first node and the other nodes. The authentication may be performed by an identified leader node of the MAPC group.

[0034] Exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: sending an association request to a node of the wireless communication network, the association request requesting the addition of a new node to the MAPC group, the request including: the agreed coordination capabilities of the new node; and receiving an association response from the node in response to the authentication request, wherein the response includes: the agreed capabilities of the new node.

[0035] Exchanging information for establishing or modifying a MAPC group with one or more of the other nodes may include: receiving an association request at a first node requesting the addition of a new node to the MAPC group, the request including: agreed-upon coordination capabilities of the new node; and providing an association response in response to the authentication request, wherein the response includes: the agreed-upon capabilities of the new node.

[0036] Some example embodiments further comprise exchanging one or more MAPC management frames between at least two nodes of the MAPC group, wherein the or each MAPC management frame comprises a MAPC header and one or more information elements defining features to be performed by the MAPC group.

[0037] Some example embodiments further include modifying coordination between nodes of the group in response to a MAPC management frame. Modifying coordination between nodes of the group may include exchanging management frames between at least two nodes of the MAPC group, the management frames indicating removal of the identified node from the MAPC group. Example management frames include deauthentication management frames or disassociation management frames. Such management frames may be exchanged directly or using relay messages. The management frame indicating removal of the identified node may include a reason code providing a reason for the removal and an identifier identifying the MAPC group.

[0038] According to a fourth aspect, a computer-readable instruction is provided which, when executed by a computing device, causes the computing device to perform (at least) any method described herein (including the methods of the second and third aspects above).

[0039] According to a fifth aspect, a computer-readable medium (such as a non-transitory computer-readable medium) is provided, which includes program instructions stored thereon, which are used to execute (at least) any method described herein (including the methods of the second and third aspects above).

[0040] According to the sixth aspect, a device is provided, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, causes the device to perform (at least) any method described herein (including the methods of the second and third aspects above).

[0041] According to the seventh aspect, a computer program comprising instructions is provided, which, when executed by an apparatus, causes the apparatus to at least perform: receiving, at a first node of a wireless communication network, multi-access point coordination (MAPC) parameter set data from one or more other nodes of the wireless communication network, wherein each MAPC parameter set data comprises: MAPC capability information identifying one or more MAPC features supported by the corresponding other nodes, and details of the supported functions of each identified supported MAPC feature; exchanging information for establishing or modifying a MAPC group with one or more of the other nodes, the MAPC group being usable to define coordination between nodes of the MAPC group; and executing, in accordance with the defined coordination, one or more features defined by one or more management frames received from one or more of the other nodes.

[0042] According to an eighth aspect, a computer program comprising instructions is provided, which, when executed by an apparatus, causes the apparatus to at least perform: providing MAPC parameter set data of a first node to one or more other nodes among the other nodes of a wireless communication network; exchanging information for establishing or modifying a MAPC group with one or more other nodes among the other nodes, wherein the MAPC group can be used to define coordination between nodes of the MAPC group, the nodes including the first node; and executing one or more features defined by one or more management frames received from one or more other nodes among the other nodes according to the defined coordination.

[0043] According to a ninth aspect, there is provided an apparatus comprising: an input (or some other component) of a first node of a wireless communication network (e.g., a Wi-Fi network) for receiving multi-access point coordination (MAPC) parameter set data from one or more other nodes of the wireless communication network, wherein each MAPC parameter set data comprises: MAPC capability information identifying one or more MAPC features supported by the corresponding other node, and details of the supported functions of each identified supported MAPC feature; a control module (or some other component) for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes, the MAPC group being usable to define coordination between nodes of the MAPC group; and a processor (or some other component) for executing one or more features defined by one or more management frames received from one or more of the other nodes in accordance with the defined coordination.

[0044] According to a tenth aspect, a device is provided, comprising: an output (or some other component) of a node of a wireless communication network, for providing MAPC parameter set data of a first node to one or more other nodes of the other nodes of the wireless communication network; a control module (or some other component) for exchanging information for establishing or modifying a MAPC group with one or more other nodes of the other nodes, the MAPC group being usable to define coordination between nodes of the MAPC group, the nodes including the first node; and a processor (or some other component) for executing one or more features defined by one or more management frames received from one or more other nodes of the other nodes according to the defined coordination. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Example embodiments will now be described, by way of non-limiting examples, with reference to the accompanying drawings, in which:

[0046] Figure 1 is a block diagram of a wireless communication network according to an example embodiment;

[0047] Figure 2 is a block diagram of a wireless communication network according to an example embodiment;

[0048] Figure 3 is a flowchart illustrating a method according to an example embodiment;

[0049] Figure 4 is a message flow diagram according to an example embodiment;

[0050] Figure 5 is a block diagram illustrating a message format according to an example embodiment;

[0051] Figure 6 is a block diagram illustrating a message format according to an example embodiment;

[0052] Figures 7 to 9 is a message flow diagram according to an example embodiment;

[0053] Figures 10 to 14 is a block diagram illustrating a message format according to an example embodiment;

[0054] Figure 15 is a flowchart illustrating a method according to an example embodiment;

[0055] Figure 16 is a flowchart illustrating a method according to an example embodiment;

[0056] Figure 17 is a block diagram of components of a system according to an example embodiment; and

[0057] Figure 18An example of a tangible medium for storing computer-readable code is shown. When the code is executed by a computer, the method according to the above-described exemplary embodiment can be performed. DETAILED DESCRIPTION

[0058] Figure 1 is a block diagram of a wireless communication network, generally indicated by the reference numeral 10, according to an example embodiment.

[0059] The network 10 includes a first node 12, a second node 14, and a third node 16. Each node is in bidirectional communication with some or all other nodes of the network. The network 10 may be, for example, a Wi-Fi network.

[0060] The nodes of network 10 may be configured to share multi-access point coordination (MAPC) information. Such information, which may conform to the IEEE 802.11 Wi-Fi standard, may be used to enable some or all of nodes 12, 14, 16 to share coordination information, thereby improving the management and organization of network 10.

[0061] Before sending a transmission, the coordination parameters may be shared among at least some of the nodes of network 10. In this manner, the parameters may be utilized to optimize coordination requirements, such as based on the capabilities and requirements of each node.

[0062] To support the different types of MAPC coordination features that can be implemented, a flexible MAPC framework can be provided, as discussed in detail below. For example, such a framework can enable the creation and execution of coordination feature sets.

[0063] Figure 2 is a block diagram of a wireless communication network according to an example embodiment, the network generally indicated by the reference numeral 20. The network 20 is an example implementation of the network 10 described above, and may be, for example, a Wi-Fi network.

[0064] Network 20 includes a first access point multi-link device (AP-MLD) 21, a second AP-MLD 22, and a third AP-MLD 23. Each of the AP-MLDs (and typically the other AP-MLDs) coexists in the same physical area and can communicate with each other. Note that some communications between the AP-MLDs may involve one or more relay nodes, such as one or more other AP-MLDs, and / or one or more devices (e.g., stations (STAs)); this may occur, for example, if a pair of AP-MLDs cannot communicate directly with each other.

[0065] Each of AP-MLDs 21 through 23 communicates with one or more devices (e.g., stations (STAs)). For example, in system 20, first and second devices STA 1.1 and STA 1.2 both communicate bidirectionally with first AP-MLD 21. Similarly, third, fourth, and fifth STAs STA 2.1, STA 2.2, and STA 2.3 all communicate bidirectionally with second AP-MLD 22. Finally, sixth, seventh, and eighth STAs STA 3.1, STA 3.2, and STA 3.3 all communicate bidirectionally with third AP-MLD 23. The various devices (STAs) may be, for example, user equipment (UEs), laptops, or some other computing or communication devices.

[0066] Using coordination signaling, AP-MLDs 21-23 can establish coordination sets and implement new policies using different types of coordination.

[0067] To enable coordination between APs and MLDs, the following process can be defined:

[0068] Announce / discover AP-MLD coordination capabilities.

[0069] MAPC group negotiation and establishment. Negotiation can be performed between pairs of nodes or using a leader node.

[0070] MAPC feature-specific negotiation and information exchange.

[0071] MAPC change management and finalization. This may include, for example, the node termination process.

[0072] Each process is discussed in detail below.

[0073] Figure 3 is a flow chart illustrating a method according to an example embodiment, generally designated by reference numeral 30. Method 30 may be implemented at a node of system 10 or at a node / AP-MLD of system 20. As an example, the following description describes method 30 implemented at first AP-MLD 21 of system 20.

[0074] Method 30 begins with operation 32, in which the first AP-MLD 21 of the wireless communication network 20 receives multi-access point coordination MAPC parameter set data from one or more (e.g., all) other nodes of the network (e.g., the second AP-MLD 22 and the third AP-MLD 23); for example, the first AP-MLD 21 can exchange MAPC parameter set data with the (multiple) other nodes. Each MAPC parameter set data includes: MAPC capability information identifying one or more MAPC features supported by the corresponding other node, and details of the supported functions of each identified supported MAPC feature. Although not shown in method 30, the second AP-MLD 22 and / or the third AP-MLD 23 can receive MAPC parameter sets from one or more (e.g., all) other nodes of the network. Therefore, operation 32 can be used to implement the above-mentioned "announcement / discovery of AP-MLD coordination capabilities."

[0075] As discussed in detail below, operation 32 may include requesting MAPC information using a broadcast message (eg, to scan for nearby MAPC-capable devices). Such a broadcast message may be in the form of a probe request.

[0076] As part of operation 32, the first AP-MLD 21 may provide the MAPC parameter set data of the first node to one or more of the other nodes of the wireless communication network (e.g., to the second AP-MLD 22 and / or the third AP-MLD 23). Similarly, the second AP-MLD 22 and / or the third AP-MLD 23 may provide the MAPC parameter set data to the other node(s). In this manner, the MAPC parameter set data may be exchanged between nodes.

[0077] At operation 34, information for establishing or modifying (e.g., updating or terminating) a MAPC group is exchanged between the first node / AP-MLD 21 and one or more of the other nodes (e.g., the second AP-MLD 22 and / or the third AP-MLD 23). A MAPC group can be used for coordination between nodes that define the MAPC group. As discussed in detail below, the information is exchanged using one or more frames (e.g., management frames). The establishment and negotiation of the MAPC group (see step 34 of method 30) can be achieved through direct or relayed messages (e.g., management frames) between nodes (e.g., between AP-MLDs). Such messages can enable inter-BSS AP-MLD and non-AP-MLD communication for coordination.

[0078] At operation 36, one or more features defined by one or more management frames received from one or more of the other nodes are performed (eg, by the first node 21) in accordance with the defined coordination.

[0079] Finally, at operation 38, one or more MAPC groups are modified (eg, changed, expanded, or terminated), as discussed in detail below.

[0080] Figure 4 4 is a message flow diagram according to an example embodiment, generally indicated by the reference numeral 40. The message flow diagram 40 illustrates messages transmitted between a first node 41 and a second node 42 of a wireless communication network, such as a Wi-Fi network. For example, the first node 41 may be the first node 12 or the first AP-MLD 21 (or some similar node). The second node 42 may be the second node 14 or the second AP-MLD 22 (or some similar node).

[0081] The sequence 40 begins by sending multi-access point coordination MAPC parameter set data from the second node 42 to the first node 41 in a message 44. As described above with reference to operation 32 of method 30, such MAPC parameter set data may be received at the first node 41 from each of a plurality of other nodes of the wireless communication network. The MAPC parameter set data received in the message 44 includes MAPC capability information identifying one or more MAPC features supported by the respective other nodes, and details of supported functionality for each identified supported MAPC feature.

[0082] The first node 41 sends a message 45 to the second node 42 (and possibly also to one or more other nodes of the wireless communication network) providing the MAPC parameter set data of the first node.

[0083] Thus, messages 44 and 45 are example implementations of operation 32 of method 30 described above, in which MAPC parameter set data is exchanged between nodes. It should be noted that messages 44 and 45 need not be sent in order as shown in message sequence 40.

[0084] In message 46, information for establishing or modifying (e.g., updating or terminating) a MAPC group is exchanged between the first node and the second node. Although a single double-headed arrow is shown, message 46 may be implemented by exchanging multiple messages. Note, of course, that the MAPC group may involve other nodes, and that the message 46 (or similar such messages) exchanged between the first node and the second node may also be exchanged with other nodes of the MAPC group. The information exchanged in message 46 may be used to define coordination between the nodes of the MAPC group. Message 46 is an example implementation of operation 34 described above. As discussed in detail below, the information exchanged in message 46 may be exchanged using one or more frames (e.g., management frames).

[0085] In message 47, information is exchanged between the first node and the second node for performing one or more features defined by one or more management frames received from one or more of the other nodes in accordance with the defined coordination. Message 47 is an example implementation of operation 36 described above. As discussed in detail below, the information exchanged in message 47 may be exchanged using one or more frames (e.g., management frames).

[0086] In message 48, information is exchanged between the first node and the second node for changing, updating, or terminating one or more nodes defined by one or more management frames received from one or more of the other nodes in accordance with the defined coordination. Message 48 is an example implementation of operation 38 described above. As discussed in detail below, the information exchanged in message 48 may be exchanged using one or more frames (e.g., management frames).

[0087] The various message exchanges in message sequence 40 (or similar message sequences) can take the form of MAPC management frame exchanges between at least two nodes of a MAPC group. A MAPC management frame can include a MAPC header and one or more information elements that define the characteristics to be performed by the MAPC group. For example, coordination between the nodes of the group can be modified in response to a MAPC management frame. The frames exchanged (e.g., management frames) can have the same form, with parameters of the frame being changed to indicate the type of frame.

[0088] The message sequence 40 is provided as an example only. In some example embodiments, the message sequence exchanged may be different. For example, some steps may be repeated or interleaved with other steps.

[0089] Figure 5 1 is a block diagram illustrating a message format according to an example embodiment, which is generally designated by reference numeral 50. Message format 50 is a MAPC parameter set. Messages 44 and 45 described above may be implemented using MAPC parameter set 50.

[0090] The MAPC parameter set 50 includes: an element ID (e.g., 8-bit data), length data (e.g., 8-bit data), element ID extension data (e.g., 8-bit data), and variable-length MAPC information 52. In this way, the MAPC information 52 is embedded in the MAPC parameter set. If MAPC is implemented, the MAPC parameter set message element can be optional (otherwise, it is not present), thereby ensuring backward compatibility with older generation Wi-Fi protocols.

[0091] The MAPC information portion 52 of the MAPC parameter set 50 includes the following fields:

[0092] ○ MAPC Capability Information: This field contains the set of supported MAPC features (eg, C-SR, C-BF, C-OFDMA, etc.).

[0093] ○ MAPC Feature Details 54. For each implemented / enabled MAPC feature, specific details are provided to indicate the supported functionality (many of these MAPC feature details are in Figure 5 The number of MAPC feature information fields 54 is variable and depends on the set of MAPC functions implemented. The length of each MAPC feature information field 54 may also be variable, for example, depending on the specific information required for each feature.

[0094] Each instance of MAPC characteristic information 54 may include one or more of the following:

[0095] o Band Description: Used to indicate the frequency band(s) in which the feature is supported / enabled.

[0096] o Coordination Limits: This field is used to indicate potential limitations on establishing / operating a MAPC group for a particular feature (eg, maximum MAPC group size).

[0097] o Coordination Time Limit: This field is used to indicate a potential time limit and / or time window for enabling the coordination feature.

[0098] o Supported Security: This may indicate the supported security methods and security requirements of the coordination feature. Certain coordination features may require security measures to be established to protect sensitive data (eg, STA identifiers, STA locations, etc.).

[0099] o Feature Support Capabilities: This field is used to indicate specific capabilities of the corresponding MAPC feature (eg, MAPC group leader, threshold, transmission capability, number of antennas, etc.).

[0100] Of course, in some example embodiments, some parameters of the MAPC parameter set 50 may be omitted, while in some example embodiments, some other parameters may be included.

[0101] Figure 6 is a block diagram illustrating a message format according to an example embodiment, which is generally indicated by the reference numeral 60. The message format 60 includes the aforementioned MAPC parameter set 50. The message format 60 may be, for example, a beacon frame.

[0102] The message format 60 includes a MAC header and a frame body 62. Figure 6 As shown in FIG, the MAPC parameter set 50 is provided in an optional portion of the frame body 62.

[0103] Figure 7 is a message flow diagram, generally indicated by the reference numeral 70, in accordance with an example embodiment.

[0104] Message flow diagram 70 shows messages transmitted between a first AP-MLD 71 and a second AP-MLD 72 of a wireless communication network (such as a Wi-Fi network). The first AP-MLD 71 includes three access points (AP1, AP2, AP3), and the second AP-MLD 72 includes three access points (AP1, AP2, and AP3). It should be noted that each AP-MLD can include any number of access points (and they can have different numbers of access points). For example, the various access points can operate in different frequency bands. Note that for MAPC signaling, each pair of access points (e.g., AP1 from AP-MLD 1 and AP2 from AP-MLD 2) can operate in the same frequency band and channel).

[0105] Sequence 70 provides an example implementation of message 44 of message sequence 40, wherein MAPC parameter set data is sent from a second node (the second AP-AP of MLD 72) to a first node (the first AP-AP of MLD 71). Figure 5 The MAPC parameter set data includes capability information identifying one or more MAPC features supported by the corresponding other node, and details of supported functions of each identified supported MAPC feature.

[0106] Two example mechanisms for communicating MAPC parameter set data are shown in message sequence 70. The first mechanism involves sending one or more beacon frames 74 (as in message format 60 described above) from a second AP-MLD 72 to a first AP-MLD 71. The second mechanism involves sending probe request and response frames 76 between the first and second AP-MLDs. The beacon frames 74 and probe request / response frames 76 carry the MAPC parameter set 50 described above.

[0107] The use of beacon frames 74 (such as message format 60) may be referred to as implicit mode. The use of probe request / response frames may be referred to as explicit mode. Some example AP-MLDs may need to be able to support both methods. For example, such an AP-MLD may include the following functionality:

[0108] o Ability to read and process beacon frames 74 from other AP-MLDs to discover their MAPC capabilities.

[0109] o The ability to send a probe request management frame 76a to other AP-MLDs to request information about their MAPC capabilities.

[0110] o Ability to read Probe Response Management Frames 76b from other AP-MLDs to learn their MAPC capabilities.

[0111] Thus, exchanging parameter sets in operation 32 of method 30 may include providing MAPC parameter set data for a respective node by broadcasting the data in a beacon frame, and receiving MAPC parameter set data from one or more other nodes in a beacon frame broadcast by the respective other node(s).

[0112] Alternatively or additionally, exchanging parameter sets in operation 32 may include sending (e.g., broadcasting) a probe request to a node of the wireless communication network requesting coordination information from the node of the wireless communication network, and receiving one or more probe responses from one or more nodes in response to the request, wherein the probe response(s) include: MAPC parameter set data of the corresponding node(s). The probe response(s) may be directed messages (whose destination address is set to the ID of the device sending / broadcasting the probe request).

[0113] Similarly, beacon and probe frames may be used to implement messages 44 and 45 of message sequence 40 described above.

[0114] In message 44, the second node 42 provides the second node's MAPC parameter set data to the first node 41 (and possibly to one or more other nodes of the wireless communication network). The MAPC parameter set data may form part of a beacon frame 74 or a probe response 76b (sent in response to a probe request).

[0115] Similarly, the first node 41 provides the first node's MAPC parameter set data to the second node 42 (and possibly to one or more other nodes of the wireless communication network) in message 45. The MAPC parameter set data may form part of a beacon frame 74 or a probe response 76b (sent in response to a probe request).

[0116] The establishment and negotiation of the MAPC group (see step 34 of method 30) is achieved through direct messaging between nodes (eg, between APs and MLDs). Example messages include authentication and association messages.

[0117] Figure 8 8 is a message flow diagram according to an example embodiment, generally indicated by the reference numeral 80. The message flow diagram 80 illustrates messages transmitted between a first node 81 and a second node 82 in a wireless communication network, such as a Wi-Fi network. For example, the first node 81 may be any one of the nodes 12, 21, 41, and 71 described above. For example, the second node 82 may be any one of the nodes 14, 22, 42, and 72 described above.

[0118] Message sequence 80 includes: a first node 81 sends an authentication request 84 to a second node 82. In response to authentication request 84, the second node provides an authentication response 86 to the first node. As discussed in detail below, the authentication response can be used to establish a trusted setup between at least some nodes of the MAPC group, including the first node. The authentication request and response can be implemented using management frames.

[0119] The authentication request 84 may include a pre-shared key (or some other authentication information) to be verified by the second node 82. Note that authentication may be mutual (depending on the method indicated in the "MAPC Authentication Mode" discussed below). Thus, in summary, in this case, the authentication request is not intended to request authentication information, as the authentication information is already known from the MAPC parameter set.

[0120] As discussed in detail below, the same management frame may be used for both the authentication request 84 and the authentication response 86, but with different fields.

[0121] Figure 9 90 is a message flow diagram according to an example embodiment, generally indicated by the reference numeral 90. The message flow diagram 90 illustrates messages transmitted between a first node 91 and a second node 92 in a wireless communication network, such as a Wi-Fi network. For example, the first node 91 may be any one of the nodes 12, 21, 41, 71, and 81 described above. For example, the second node 92 may be any one of the nodes 14, 22, 42, 72, and 82 described above.

[0122] Message sequence 90 includes: a first node 91 sends an association request 94 to a second node 92 requesting the addition of a new node to a MAPC group. In response to association request 94, the second node provides an association response 96 to the first node. The association request may include the agreed coordination capabilities of the new node. The association response may include the agreed coordination capabilities of the new node. The association request and response may be implemented using management frames.

[0123] The same management frame may be used for both the association request 94 and the association response 96, but with different fields. In fact, the association request, association response, authentication request, and authentication response may all use the same management frame, but with different fields.

[0124] In some example embodiments, the authentication request 84 and / or the authentication response 86 may be sent via a relay node. Similarly, in some example embodiments, the association request 94 and / or the authentication response 96 may be sent via a relay node.

[0125] The above authentication and association process can be performed in two different ways when applied by a node (e.g., AP-MLD) for MAPC group establishment:

[0126] Based on pair groups, where nodes (such as AP-MLD) communicate in pairs to negotiate the establishment of a MAPC group. In this case, AP-MLD can be equal.

[0127] Based on a group leader, where an identified leader node of a MAPC group handles the joining of new AP-MLDs in the group. Thus, authentication and association for joining a given MAPC group is performed through the MAPC group leader. The address of the MAPC group leader can be announced during the announcement / discovery of AP-MLD coordination capabilities (e.g., as part of the MAPC parameter set 50). For example, the leader node can be elected arbitrarily, randomly, voluntarily, or following any leader election method (such as a voting-based election).

[0128] In the event that a leader node is provided, non-leader nodes may be able to relay information to the leader node. This can be useful, for example, in situations where the requesting node cannot reach the leader node (e.g., the leader node is out of range).

[0129] When messages are relayed between nodes (in either a pairwise embodiment or a leader-based embodiment), one or more user terminals (eg, STAs) may be involved in the message relay.

[0130] Some existing methods under the 802.11 Wi-Fi standard can be extended to support the establishment and negotiation of MAPC groups, as follows:

[0131] Authentication frames and association request / response frames may be required to carry new fields.

[0132] Used for MAPC establishment and negotiation;

[0133] AP-MLDs may need to be able to read and process the proposed extensions to authentication frames from other AP-MLDs to establish MAPC groups; and

[0134] • AP-MLDs may need to be able to read and process the proposed extensions to Association Request / Response frames from other AP-MLDs to establish a MAPC group.

[0135] Authentication may be required for certain subsets of MAPC features that require a high degree of trust between participants (e.g., features involving the exchange of sensitive data). For less restrictive coordination schemes, open authentication may be used. Some example embodiments utilize and extend the currently standardized authentication frame for MAPC authentication purposes. During authentication, the AP-MLD may establish a trusted setup and exchange keys that are later used for MAPC communications (e.g., for frame encryption).

[0136] Figure 10 is a block diagram illustrating a message format according to an example embodiment, generally designated by the reference numeral 100. The message format 100 is an authentication frame (which is an example of a management frame).

[0137] The authentication frame 100 may be used as an authentication request (e.g., request 84 described above) or an authentication response (e.g., request 86 described above). This may depend on the values ​​of various fields within the authentication frame.

[0138] The authentication frame 100 includes a frame body 102. The frame body includes MAPC authentication information 104, which can be used by the AP-MLD for authentication, including some or all of the following fields:

[0139] MAPC Group ID: Used when a group has been established and a new AP-MLD wishes to join.

[0140] MAPC authentication mode: used to indicate the authentication / association mode, including pairwise authentication, group leader-based authentication, etc.

[0141] Relay Mode: Used to indicate whether the message has been relayed (used for MAPC signaling coverage extension).

[0142] MAPC Group Leader ID: used for group leader-based authentication type.

[0143] After authentication is complete, AP-MLD may proceed to formalize the establishment / expansion of the MAPC group by exchanging Association Request and Response frames, as described below.

[0144] It should be noted that instances of the authentication frame 100 (and other management frames described herein) may be exchanged using direct messaging or using relayed messaging.

[0145] Figure 11 is a block diagram illustrating a message format according to an example embodiment, generally designated by reference numeral 110. Message format 110 is an association request (which is an example of a management frame). The association request may be used in request 94 described above.

[0146] The association request 110 includes a MAC header and a frame body 112 . The frame body 112 includes a MAPC negotiated capability field 114 .

[0147] Figure 12 is a block diagram illustrating a message format, generally designated by reference numeral 120, according to an example embodiment. Message format 120 is an association response (which is an example of a management frame). The association response may be used in response 96 described above.

[0148] The association response 120 includes a MAC header and a frame body 122. The frame body 122 includes a MAPC group ID 124 and a MAPC negotiated capability field 126.

[0149] The MAPC negotiated capabilities field 114 of the association request 110 can be used to inform the recipient of the association request of the terms of the coordination, thereby indicating specific parameters of the target coordination characteristics (e.g., the maximum number of empty spaces to be placed in a C-BF with empty turns, the maximum number of parallel transmissions in a C-SR, etc.).

[0150] Similarly, the association response frame is adapted to include: the last negotiated capability set plus the MAPC group ID (instead of the association ID used when joining the STA through the current association process). The MAPC group ID 124 can be used to identify a specific MAPC group and to indicate the purpose of upcoming coordinated transmission. Therefore, the MAPC group ID 124 can potentially be used to allow non-AP-MLD devices to decode frames from other AP-MLDs in the same MAPC group.

[0151] Figure 13 1 is a block diagram illustrating a message format according to an example embodiment, generally designated by reference numeral 130. Message format 130 is a MAPC management frame (which is an example of a management frame). After a MAPC group is established, operations of specific features (e.g., C-SR, C-BF) are performed using management frames such as MAPC management frame 130.

[0152] The MAPC management frame 130 may be used by the coordination device to request, share, and confirm relevant information for implementing the coordination use case. Thus, the MAPC management frame 130 may be used to implement operation 36 of the above-described method 30. Thus, such a management frame may be exchanged in message 47 of the above-described message sequence 40.

[0153] The MAPC management frame 130 may be generated by appropriately configuring the "subtype" field from the existing general management frame structure.

[0154] The MAPC management frame 130 includes a MAC header 131 and a frame body 132 .

[0155] The MAC header 131 includes a frame control portion. Within the frame control portion, a new management frame subtype is indicated. For example, available codes between 0000 and 1111 can be assigned to MAC purposes.

[0156] The frame body 132 includes some or all of the following fields:

[0157] • Coordination Protocol: Indicates the actual coordination protocol being executed (e.g., C-SR, C-BF, etc.) This is part of the MAPC header.

[0158] Message Type: Indicates the type of control message, which includes signaling for coordinating simultaneous transmissions, triggering data exchange (e.g., CSI information from STAs, used RU resources, available / unavailable SPs, etc.), etc. This is also part of the MAPC header.

[0159] Information element: Contains relevant information for performing the operations required for a specific use case. The content of the information element may depend on the coordination protocol and the message type. For example, in C-SR, an AP (shared) may send a message to trigger another AP (shared) to initiate a simultaneous transmission. In this trigger, the shared AP may indicate the maximum transmit power to be used by the shared AP during the transmission, as well as other relevant information.

[0160] Figure 14 1 is a block diagram illustrating a message format, generally designated by reference numeral 140, according to an example embodiment. Message format 140 is a deauthentication / disassociation frame (which is an example of a management frame). Message format 140 may be exchanged in message 48 of message sequence 40.

[0161] The MAPC Change Management and Termination procedures may be used to modify the terms and conditions of a given ongoing coordination and to terminate the coordination, respectively. Figure 13 The MAPC management frame 130 in question notifies of the relevant changes.

[0162] When it comes to MAPC termination, some example embodiments extend the currently standardized deauthentication / disassociation frame. As with MAPC establishment, termination can be handled differently depending on the MAPC mode implemented (e.g., pairwise partnership, group leader-based, etc.).

[0163] The deauthentication / disassociation frame 140 includes a MAC header 141 and a frame body 142. As described above, management frames such as the deauthentication / disassociation frame 140 may be exchanged through direct or relayed messages.

[0164] The frame body 142 includes the following fields:

[0165] • Reason codes, which are extended to support MAPC related termination codes (e.g., MAPC inactivity, coordination timeout, disassociation due to poor performance, etc.).

[0166] • MAPC Group ID, which indicates the group for which coordination is terminated.

[0167] Figure 15is a flow chart illustrating a method according to an example embodiment, generally indicated by reference numeral 150. The method 150 may be implemented at a node (eg, an AP-MLD) of a wireless communication network.

[0168] Method 150 begins at operation 152, where a first node of the wireless communication network (e.g., one of the nodes 12, 21, 41, 71, 81, and 91 described above) receives a MAPC parameter set (e.g., MAPC parameter set 50) from one or more other nodes of the wireless communication network (e.g., one of the nodes 14, 22, 42, 72, 82, and 92 described above). As described above, each MAPC parameter set includes MAPC capability information that identifies one or more MAPC features supported by the corresponding other node, as well as details of supported functions for each identified supported MAPC feature.

[0169] At operation 154, information is exchanged between the nodes for establishing or modifying a MAPC group with one or more of the other nodes, the MAPC group being usable for coordination between the nodes defining the MAPC group. This information may take the form of management frames.

[0170] At operation 156, one or more features defined by one or more management frames received from one or more of the other nodes are performed in accordance with the defined coordination.

[0171] Figure 16 is a flow chart illustrating a method according to an example embodiment, generally indicated by reference numeral 160. The method 160 may be implemented at a node (eg, an AP-MLD) of a wireless communication network.

[0172] Method 160 begins at operation 162, where a MAPC parameter set of a first node of a wireless communication network (e.g., one of the nodes 12, 21, 41, 71, 81, and 91 described above) is provided to one or more other nodes of the wireless communication network (e.g., one of the nodes 14, 22, 42, 72, 82, and 92 described above).

[0173] At operation 164 , information is exchanged between the nodes for establishing or modifying a MAPC group with one or more of the other nodes, the MAPC group being operable for coordination between the nodes defining the MAPC group, including the first node.

[0174] At operation 166, one or more features defined by one or more management frames received from one or more of the other nodes are performed in accordance with the defined coordination.

[0175] Features of methods 160 and 170 may be combined such that the relevant nodes receive parameter set data (operation 152) and provide parameter set data (operation 162). Suitable methods and message sequences are discussed in detail above.

[0176] For the sake of completeness, Figure 17 3 is a schematic diagram of components of one or more example embodiments described previously (hereinafter collectively referred to as processing system 300). For example, processing system 300 may be an apparatus as recited in the following claims.

[0177] The processing system 300 may have a processor 302, a memory 304 tightly coupled to the processor and consisting of RAM 314 and ROM 312, and optionally a user input 310 and a display 318. The processing system 300 may include one or more network / device interfaces 308 for connecting to a network / device, such as a wired or wireless modem. The network / device interface 308 may also operate as a connection to other devices (such as devices / apparatuses that are not network-side devices). Thus, direct connections between devices / apparatuses are possible without the involvement of a network.

[0178] Processor 302 is connected to each of the other components to control their operation.

[0179] The memory 304 may include non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD). The ROM 312 of the memory 304 stores an operating system 315 and the like, and may store software applications 316. The RAM 314 of the memory 304 is used by the processor 302 to temporarily store data. The operating system 315 may contain code that, when executed by the processor, implements various aspects of the methods and sequences 30, 40, 70, 80, 90, 15, and 160 described above. Note that in the case of small devices / apparatuses, the memory is best suited for small size, i.e., not always a hard disk drive (HDD) or a solid-state drive (SSD).

[0180] Processor 302 may take any suitable form. For example, it may be a microcontroller, multiple microcontrollers, a processor, or multiple processors.

[0181] The processing system 300 can be a standalone computer, server, console, or network thereof. The processing system 300 and the required structural components can all be inside a device / apparatus, such as an IoT device / apparatus, i.e., embedded in a very small size.

[0182] In some example embodiments, the processing system 300 may also be associated with external software applications. These may be applications stored on a remote server device / apparatus and may run partially or exclusively on the remote server device / apparatus. These applications may be referred to as cloud-hosted applications. The processing system 300 may communicate with the remote server device / apparatus in order to utilize the software applications stored therein.

[0183] Figure 18 Tangible media in the form of a removable memory unit 365 is shown, storing computer-readable code that, when executed by a computer, can perform methods according to the exemplary embodiments described above. Removable memory unit 365 can be a memory stick, such as a USB memory stick, having internal memory 366 for storing computer-readable code. Internal memory 366 can be accessed by the computer system via connector 367. Of course, other forms of tangible storage media can be used, as will be apparent to one of ordinary skill in the art. Tangible media can be any device / device capable of storing data / information that can be exchanged between devices / devices / networks.

[0184] Embodiments of the present invention may be implemented using software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside in memory or on any computer medium. In an example embodiment, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, "memory" or "computer-readable medium" may be any non-transitory medium or component that can contain, store, convey, propagate, or transmit instructions for use by or in conjunction with an instruction execution system, apparatus, or device (such as a computer).

[0185] Where relevant, references to "computer-readable medium," "computer program product," "tangibly embodied computer program," etc., or "processor" or "processing circuitry," etc., should be understood to encompass not only computers with different architectures (such as single / multi-processor architectures and sequential / parallel architectures), but also dedicated circuits such as field programmable gate arrays (FPGAs), application-specific circuits (ASICs), signal processing devices / apparatuses, and other devices / apparatuses. References to computer programs, instructions, code, etc., should be understood to represent software of programmable processor firmware (such as the programmable content of hardware devices / apparatuses) as instructions for a processor, or configured settings or configuration settings of fixed-function devices / apparatuses, gate arrays, programmable logic devices / apparatuses, etc.

[0186] If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the above functions may be optional or may be combined. Likewise, it should also be understood that Figure 3 、 Figure 4 、 Figures 7 to 9 、 Figure 15 and Figure 16 The methods and message flow diagrams are merely examples, and the various operations described therein may be omitted, reordered, and / or combined.

[0187] It should be understood that the above exemplary embodiments are purely illustrative and do not limit the scope of the present invention. After reading this specification, those skilled in the art will understand other changes and modifications.

[0188] Furthermore, the disclosure of this application should be understood to include any novel feature or any novel combination of features disclosed herein, whether explicitly or implicitly, or any generalization thereof, and that during the prosecution of this application or any application derived therefrom, new claims may be issued to cover any such feature and / or such combination of features.

[0189] Although various aspects of the invention are set out in the independent claims, further aspects of the invention comprise other combinations of features from the above-described example embodiments and / or dependent claims with features of the independent claims, not just the combinations explicitly set out in the claims.

[0190] The term "component" as used in the specification and claims may refer to one or more individual components configured to perform the corresponding one or more functions, or it may refer to several components that perform such one or more functions. In addition, several functions recited in the claims may be performed by the same individual component or the same combination of components. For example, the performance of one or more such functions in a device may be caused by a processor executing instructions stored in a memory of the device.

[0191] Although various aspects of the invention are set out in the independent claims, further aspects of the invention comprise other combinations of features from the above-described example embodiments and / or dependent claims with features of the independent claims, not just the combinations explicitly set out in the claims.

[0192] It should also be noted herein that although various examples are described above, these descriptions should not be viewed in a limiting sense. Rather, several variations and modifications are possible without departing from the scope of the present invention as defined in the appended claims.

Claims

1. A device for communication, comprising: means for receiving, at a first node of a wireless communication network, multi-access point coordination (MAPC) parameter set data from one or more other nodes of the wireless communication network, wherein each MAPC parameter set data comprises: MAPC capability information identifying one or more MAPC features supported by the respective said other node, and details of supported functionality of each identified supported MAPC feature; means for providing MAPC parameter set data of the first node to one or more of the other nodes of the wireless communication network; means for exchanging information with one or more of the other nodes for establishing or modifying a MAPC group that can be used to define coordination between nodes of the MAPC group; and Means for performing one or more features defined by one or more management frames received from one or more of the other nodes in accordance with the defined coordination.

2. The apparatus of claim 1 , wherein the means for receiving the MAPC parameter set data comprises: Means for receiving data broadcast by one or more of said nodes.

3. The apparatus according to claim 1 or 2, wherein the means for providing the MAPC parameter set data of the first node comprises: means for broadcasting said data.

4. The device according to any one of claims 1 to 3, further comprising: means for sending a request to a node of the wireless communication network, the request requesting coordination information from the node of the wireless communication network; as well as Means for receiving a response from the node in response to the request for coordination information, wherein the response comprises: MAPC parameter set data for the corresponding node.

5. The apparatus according to any one of the preceding claims, further comprising: means for receiving, from one of said nodes, a request to provide coordination information to said node; as well as means for sending a response to the request to the node, wherein the response comprises: the MAPC parameter set data for the first node.

6. An apparatus according to any preceding claim, wherein the MAPC parameter set data is received or provided as part of a beacon frame or probe response message exchanged between respective nodes.

7. The apparatus of any preceding claim, wherein the means for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes comprises: means for sending, from the first node, an authentication request to one of the other nodes, the authentication request requesting authentication by the other node; as well as means for receiving authentication responses from the other nodes in response to the authentication request, wherein the authentication responses are used to establish a trusted setup between at least some of the nodes of the MAPC group, the at least some nodes including the first node.

8. The apparatus of any preceding claim, wherein the means for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes comprises: means for receiving, at the first node, an authentication request from one of the other nodes, the authentication request requesting authentication by the first node; as well as means for providing an authentication response in response to the authentication request, wherein the response is used to establish a trusted setup between at least some of the nodes of the MAPC group, the at least some of the nodes including: the first node, and the other nodes.

9. The apparatus of claim 7 or 8, wherein authentication is performed by the identified leader node of the MAPC group.

10. The apparatus of any preceding claim, wherein the means for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes comprises: means for sending an association request to a node of the wireless communication network, the association request requesting the addition of a new node to the MAPC group, the request including: the agreed coordination capabilities of the new node; and Means for receiving an association response from the node in response to the authentication request, wherein the response includes the negotiated capabilities of the new node.

11. The apparatus of any preceding claim, wherein the means for exchanging information for establishing or modifying a MAPC group with one or more of the other nodes comprises: means for receiving, at the first node, an association request requesting the addition of a new node to the MAPC group, the request comprising: agreed coordination capabilities of the new node; and means for providing an association response in response to the authentication request, wherein the response comprises: the negotiated capabilities of the new node.

12. The apparatus according to any one of the preceding claims, further comprising: Means for exchanging one or more MAPC management frames between at least two nodes of the MAPC group, wherein the or each MAPC management frame comprises a MAPC header and one or more information elements defining features to be performed by the MAPC group.

13. The apparatus according to any one of the preceding claims, further comprising: Means for modifying the coordination among nodes of the group in response to a MAPC management frame.

14. The apparatus of claim 13, wherein the means for modifying the coordination between the nodes of the group comprises: Means for exchanging management frames between at least two nodes of the MAPC group, the management frames indicating removal of the identified node from the MAPC group.

15. The apparatus of claim 14, wherein the management frame indicating removal of the identified node comprises: A reason code is provided for the reason for the removal, and an identifier identifying the MAPC group.

16. The apparatus of any preceding claim, wherein each of the nodes is an access point multi-link device.

17. The apparatus of any preceding claim, wherein the apparatus is the first node.

18. A method for communication, comprising: receiving, at a first node of a wireless communication network, multiple access point coordination (MAPC) parameter set data from one or more other nodes of the wireless communication network, wherein each MAPC parameter set data comprises: MAPC capability information identifying one or more MAPC features supported by the respective one of the other nodes, and details of supported functionality for each identified supported MAPC feature; exchanging information with one or more of the other nodes for establishing or modifying a MAPC group that can be used to define coordination between nodes of the MAPC group; and One or more features defined by one or more management frames received from one or more of the other nodes are performed according to the defined coordination.

19. A method for communication, comprising: providing MAPC parameter set data of the first node to one or more other nodes of the wireless communication network; exchanging information for establishing or modifying a MAPC group with one or more of the other nodes, the MAPC group being operable to define coordination between nodes of the MAPC group, the nodes including the first node; as well as One or more features defined by one or more management frames received from one or more of the other nodes are performed according to the defined coordination.

20. A computer program product comprising instructions which, when executed by an apparatus, cause the apparatus to at least: At a first node of a wireless communication network, multiple access point coordination (MAPC) parameter set data is received from one or more other nodes of the wireless communication network, wherein each MAPC parameter set data comprises: MAPC capability information identifying one or more MAPC features supported by the respective other nodes, and details of supported functionality for each identified supported MAPC feature; exchanging information for establishing or modifying a MAPC group with one or more of the other nodes, the MAPC group being operable to define coordination between nodes of the MAPC group; as well as One or more features defined by one or more management frames received from one or more of the other nodes are performed according to the defined coordination.

Images