Method for providing coordinated transmission between multiple access points - Patents.com

Abstract

A method for configuring a multiple access point (M-AP) set includes an access point (AP) initiating a new M-AP set by transmitting an information element including multiple octets. One of the multiple octets indicates the presence of an extension octet of the multiple octets. A bit of the extension octet indicates whether an M-AP cooperative transmission (CT) basic service set (BSS) is enabled for this AP. A method for establishing a multiple access point (M-AP) set between APs includes transmitting, by a first AP, a first message advertising the M-AP cooperative transmission (CT) basic service set (BSS); receiving, by the first AP, a second message advertising a second M-AP CT BSS from the second AP; and initiating peering used by the M-AP set including the first AP and the second AP in response to receiving the first message or the second message.

Description

[Technical Field]

[0001] The present disclosure relates generally to the field of wireless communications, and more particularly to providing wireless connectivity between a set of multiple access points (APs) operating on a common channel. [Background technology]

[0002] Wireless local area network (WLAN) systems may operate in unlicensed bands, which means that WLANs operating with overlapping coverage may interfere with each other. To reduce the amount of local interference, access points (APs) operating within the same coverage area and coordinating transmissions have been proposed. Currently, the IEEE 802.11 standards committee is working to add features and functionality that will allow APs to coordinate transmissions to stations (STAs) while the APs may overlap in their coverage.

[0003] There are many challenges in coordinating transmissions by APs given the time, space, and frequency overlap that must be overcome to provide a robust multi-AP configuration. This involves communicating between APs using mechanisms for the APs to discover each other, establish connections, communicate, and later adjust transmission parameters. While this can be done over wired links, it is advantageous for at least a portion of the communication to occur over a wireless medium.

[0004] Therefore, what is needed is a method for configuring and managing a group of APs into a set with agreed-upon cooperation methods and transmission parameters that avoids or mitigates one or more limitations of the prior art.

[0005] This background information is intended to provide information of possible relevance to the present invention. It is not necessarily intended, nor should it be construed, that any of the preceding information constitutes prior art against the present invention. Summary of the Invention

[0006] Embodiments of the present disclosure generally provide methods and apparatus for providing wireless connectivity between a set of multiple APs (M-AP set) operating on the same channel to facilitate the establishment of a cooperative transmission (CT) agreement between a subset of APs under this M-AP set. Existing IEEE 802.11-based standard mesh network procedures that define discovery, connection, and communication mechanisms can be adapted and reused for the creation of a multi-AP (M-AP) cooperative transmission (CT) basic service set (BSS). Because existing IEEE 802.11 mesh mechanisms do not involve a central entity, such as an AP in an infrastructure BSS, they can be reused by a set of APs to form an M-AP CT BSS. In these mesh mechanisms, discovery, connection management, security, and communication are already defined for peering between mesh stations (STAs). The distributed nature of mesh networking can be adapted to provide connectivity between a subset of APs for the purpose of creating a CT agreement between the subset of APs operating on the same channel under this M-AP set. [Means for solving the problem]

[0007] According to one embodiment of the present disclosure, there is provided a method for configuring a multiple access point (M-AP) set. The method includes transmitting, by an access point (AP) initiating a new M-AP set, an information element including a plurality of octets, one of the plurality of octets indicating the presence of an extension octet of the plurality of octets. The extension octet indicates whether an M-AP cooperative transmission (CT) basic service set (BSS) is enabled for this AP.

[0008] In a further embodiment, enablement of the M-AP coordinated transmission (CT) basic service set (BSS) is indicated by a bit in the extended capabilities octet.

[0009] In a further embodiment, the information element is included in a beacon frame or a probe response frame transmitted in an M-AP CT BSS.

[0010] In a further embodiment, the Mesh Capability subfield, which indicates the presence of the last octet, is encoded as the hexadecimal value 0x81.

[0011] In a further embodiment, the bit is coded as 1 to indicate that the M-AP CT feature is enabled.

[0012] In a further embodiment, the information element further includes a mesh ID and an authentication protocol identifier.

[0013] In a further embodiment, the information element further comprises any of a length, an active path selection metric identifier, an active path selection metric identifier, a congestion control mode identifier, a synchronization method protocol identifier, mesh formation information, or mesh capabilities.

[0014] In further embodiments, the Length subfield has a value of 8, the Active Path Selection Metric Identifier subfield has a value of 254, the Active Path Selection Metric Identifier subfield has a value of 254, the Congestion Control Mode Identifier subfield has a value of 254, the Synchronization Method Protocol Identifier subfield has a value of 254, or the Mesh Formation Information subfield has a value of 0.

[0015] In a further embodiment, the mesh component includes an extended mesh capabilities subfield.

[0016] In a further embodiment, the Enhanced Mesh Capability subfield includes a bit indicating enablement of M-AP CT BSS.

[0017] In further embodiments, the mesh capabilities subfield includes any of an additional mesh peering acceptance subfield, an MCCA support subfield, an MCCA enable subfield, a forwarding subfield, an MBCA enable subfield, a TBBT adjustment subfield, a mesh power saving level subfield, or an extended mesh capabilities present subfield.

[0018] In further embodiments, the Additional Mesh Peering Acceptance subfield has a value of 1, the MCCA Support subfield has a value of 0, the MCCA Enable subfield has a value of 0, the Forwarding subfield has a value of 0, the MBCA Enable subfield has a value of 0, the TBBT Adjustment subfield has a value of 0, the Mesh Power Saving Level subfield has a value of 0, or the Enhanced Mesh Capability Present subfield has a value of 1.

[0019] According to one embodiment of the present disclosure, a method for establishing a multiple access point (M-AP) set among access points (APs) is provided. The method includes transmitting, by a first AP, a first message advertising an M-AP cooperative transmission (CT) basic service set (BSS). The method also includes receiving, by the first AP, a second message from a second AP advertising a second M-AP CT BSS. In response to receiving the first message or the second message, the method further includes initiating peering for use by the M-AP set including the first AP and the second AP.

[0020] The embodiment further includes receiving, by the first AP, a peering open message from the second AP.

[0021] The embodiment further includes sending, by the first AP, a peering open message to the second AP.

[0022] The embodiment further includes provisioning the M-AP set with the security credentials.

[0023] In a further embodiment, the step of provisioning the M-AP set includes the steps of: transmitting a mesh peering open frame by the first AP to the second AP; and receiving, by the first AP from the second AP, a mesh peering confirm frame transmitted by the second AP in response to the second AP receiving the mesh peering open frame.

[0024] According to one embodiment of the present disclosure, a method for an access point (AP) to initiate establishment of a multiple access point (M-AP) set or join an existing M-AP set is provided, where the AP is part of a multiple basic service set identifier (MBSSID) set. The method includes adding, by the AP, a sub-element to a multiple basic service set identifier (MBSSID) element carried in a beacon frame or probe response frame transmitted by a transmitting BSSID of the MBSSID set. The sub-element includes a mesh component including a mesh ID element and parameters of an M-AP cooperative transmission (CT) basic service set (BSS).

[0025] In a further embodiment, the sub-element corresponds to a non-transmitting BSSID profile sub-element. The non-transmitting BSSID profile sub-element further includes a non-inheriting element including a list of element IDs. The list of element IDs includes element ID values ​​of mesh components and mesh ID elements.

[0026] In a further embodiment, the subelement corresponds to an M-AP CT BSS subelement. The M-AP CT BSS subelement includes a mesh component, a mesh ID element, and an MBSSID index list element. The MBSSID index list element includes a list of non-transmitting BSSIDs that correspond to an MBSSID set that is also a member of an existing M-AP set.

[0027] In a further embodiment, a transmitting BSSID that is a member of the M-AP set is indicated as index 0 in the BSSID index list.

[0028] According to one embodiment of the present disclosure, a method is provided for an access point (AP) associated with an access point multilink device (AP MLD) and operating on a specific link of multiple links to initiate establishment of a set of multiple access points (M-APs) configured on another link of the same AP MLD or to join an existing M-AP set on another link of the same AP MLD. The method includes adding, by the AP, a first subfield to a STA control field of a per-STA profile subelement included in a basic multilink element carried in a beacon or probe response frame. The first subfield includes an indication that M-AP cooperative transmission (CT) basic service set (BSS) information is present in the STA information field of the per-STA profile subelement. The step of adding, by the AP, further elements to the STA information field of the per-STA profile subelement includes, specifically, a mesh ID element and a mesh component including parameters of the M-AP CT BSS.

[0029] The embodiment further includes receiving, by the AP, a beacon frame or a probe response frame that includes an MBSSID element, the MBSSID element including sub-elements, and extracting, by the AP, a profile of an M-AP set from the sub-elements, the M-AP set being capable of M-AP CT operation.

[0030] According to one embodiment of the present disclosure, there is provided a method for configuring a medium access control (MAC) layer by a station management entity (SME), the method including receiving, by the SME, multiple AP (M-AP) coordinated transmission (CT) basic service set (BSS) configuration parameters from an external management entity.

[0031] In a further embodiment, the external management entity is a WLAN controller device or a multi-access point (AP) controller.

[0032] The embodiment further includes receiving, by the MAC layer management entity (MLME), from the SME, a request primitive including a mesh ID associated with the M-AP CT BSS, an authentication protocol identifier for the M-AP CT BSS, or authentication information for the M-AP CT BSS.

[0033] The embodiment further comprises sending, by the MLME, a confirmation primitive to the SME that includes the status of the configuration request.

[0034] According to one embodiment of the present disclosure, there is provided a method for configuring a multiple access point (M-AP) set, the method including monitoring, by an external management entity, a first multiple AP (M-AP) coordinated transmission (CT) basic service set (BSS) and transmitting, by the external management entity, second M-AP CT BSS configuration parameters to APs participating in the first M-AP CT BSS, instructing the APs to associate with the second M-AP CT BSS.

[0035] According to one embodiment of the present disclosure, there is provided a method for configuring a multiple access point (M-AP) set, the method including receiving, by an access point (AP) participating in a first multiple AP (M-AP) coordinated transmission (CT) basic service set (BSS), a second M-AP CT BSS configuration parameter set from an external management entity, and joining, by the AP, the second M-AP CT BSS in response to receiving the second M-AP CT BSS configuration parameter set.

[0036] An embodiment includes discovering, by the AP, a second M-AP CT BSS;

[0037] The AP joining the second M-AP CT BSS.

[0038] In a further embodiment, the external management entity is a WLAN controller of a multi-access point (AP) controller.

[0039] According to one embodiment of the present disclosure, there are provided apparatuses and systems configured to perform all or part of any of the methods described herein. The apparatuses may include electronic or computing devices such as those found in a wireless infrastructure, including access points, base stations, management entities, etc. Multiple apparatuses may be combined to form all or part of a system that performs the methods described herein.

[0040] According to one embodiment of the present disclosure, a computer-readable medium is provided that includes software instructions or data for implementing all or part of any of the methods described herein. The embodiments have been described above in conjunction with aspects of the present disclosure in which they may be implemented. Those skilled in the art will understand that an embodiment may be implemented in conjunction with the described aspect, but may also be implemented with other embodiments of that aspect. When embodiments are mutually exclusive or otherwise incompatible with one another, this will be apparent to those skilled in the art. Some embodiments may be described in connection with one aspect, but may also be applicable to other aspects, as will be apparent to those skilled in the art. [Brief explanation of the drawings]

[0041] [Figure 1] 1 provides an example of a WLAN having an M-AP set according to an embodiment of the present disclosure. [Figure 2] 1 illustrates the steps required before performing coordinated transmission (CT) according to the prior art and embodiments of the present disclosure. [Figure 3]1 provides an example of M-AP cooperative transmission behavior in a WLAN (where only a portion of the APs support M-AP CT) according to the prior art and embodiments of the present disclosure. [Figure 4] 1 provides an example of an M-AP CT BSS discovery and peering method according to an embodiment of the present disclosure. [Figure 5] According to an embodiment of the present disclosure, a mesh component for an M-AP CT BSS having a mesh capability subfield and an extended mesh capability subfield is provided. [Figure 6a] 10 provides an example of indicating M-AP CT BSS as part of a non-transmit profile of an MBSSID element according to an embodiment of the present disclosure. [Figure 6b] 1 provides an example of indicating an M-AP CT BSS as a new MBSSID sub-element according to an embodiment of the present disclosure. [Figure 6c] 1 provides an example of an optional sub-element ID for a multiple BSSID element, according to an embodiment of the present disclosure. [Figure 6d] 1 provides an example of including a Mesh Configuration and Mesh ID element in the Link Information Field / Per-STA Profile sub-element of the Basic Multilink element, according to an embodiment of the present disclosure. [Figure 7] 1 illustrates a flow diagram of M-AP CT BSS discovery and peering according to an embodiment of the present disclosure. [Figure 8] 1 illustrates an initial M-AP CT-BSS network topology during dynamic configuration according to an embodiment of the present disclosure. [Figure 9] 1 provides an updated M-AP CT-BSS network topology during dynamic configuration according to an embodiment of the present disclosure. [Figure 10] 1 illustrates a general block diagram of a communication device of an AP in an M-AP set according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0042] It should be noted that throughout the accompanying drawings, like features are identified by like numerals.

[0043] Embodiments of the present disclosure facilitate the use of multiple APs organized in a multi-AP (M-AP) cooperative transmission (CT) basic service set (BSS). The term multi-AP is synonymous with multiple APs. Existing IEEE 802.11-based standard mesh networking procedures that define discovery, connection, and communication mechanisms can be adapted and reused for the creation and management of an M-AP CT BSS. APs that use the same channel and have overlapping bandwidth (BW) can form a mesh network to create an M-AP set. A subset of APs within an M-AP CT BSS may establish a cooperative transmission (CT) agreement, also referred to simply as a "cooperative agreement," which allows these APs to employ cooperative transmission in their BSS without interfering with each other.

[0044] WLAN systems may operate in unlicensed bands, which in some cases results in individual WLANs operating with overlapping coverage on the same channel, and therefore interfering with each other in time, space, frequency, etc. Embodiments provide features and functionality that allow APs to coordinate transmissions to other BSS APs and their associated stations (STAs), even in overlapping BSS coverage.

[0045] Embodiments organize wireless devices into Basic Service Sets (BSSs), which are the IEEE 802.11 definition of a set of wireless station devices / entities that can communicate with each other directly or through an access point (in the case of an infrastructure BSS). A BSS is the basic network building block of an IEEE 802.11 WLAN. If a wireless device is part of a mesh BSS (MBSS), i.e., a mesh network, that does not support infrastructure BSS functionality, the wireless device may attempt to discover other mesh wireless station devices / entities and transmit beacon frames advertising the MBSS. The other mesh wireless station devices / entities may then use traditional IEEE 802.11 discovery mechanisms, such as passive scanning (listening for beacon frames) or active scanning (sending probe requests and receiving probe responses). A "mesh profile" identifies the MBSS and may be included in beacon and probe request / response frames. The mesh profile includes a "mesh ID" (e.g., an information element in a management frame) that identifies an instance of the MBSS.

[0046] Mesh peering is a distributed, non-hierarchical, and non-exclusive agreement between two mesh wireless devices to establish communication and may include authentication and other security methods used between the wireless devices. Each mesh wireless device may manage peering with other mesh wireless devices. Various modes of mesh peering may be used, including secure peering (using authenticated mesh peering exchange (AMPE)) and unsecure peering (using mesh peering management (MPM)). As part of the peering process, a capability check may be performed by profile matching, and each peering has attributes that must be agreed upon. Note that each peer wireless device may provide attributes to use for potential peering, and each peer wireless device must then confirm the agreed-upon attributes that define the peering. After each side proposes and confirms the agreement, peering is established. Each peer wireless device can initiate peering, and both sides can initiate peering simultaneously. However, in some cases, only one peer wireless device can be the responder.

[0047] FIG. 1 illustrates an embodiment including a WLAN 100 in which APs 1-4 (102a-102d) are members of an M-AP set that may also participate in cooperative transmission (CT), while APs 5 and 6 (104a and 104b) do not support M-AP cooperative transmission. Multi-AP (M-AP) cooperative transmission is a mechanism by which a group of Overlapping BSS (OBSS) APs that share a common BW on the same operating channel coordinate parameters to initiate multiple frame exchanges within a period known as a transmit opportunity (TXOP). As referred to herein, OBSS APs that exhibit the ability to participate in CT may be referred to as APs in the M-AP set. A group of APs that exhibit their ability to cooperatively perform cooperative communications is referred to as the M-AP set. Each AP in the M-AP set shares a common BW on the same operating channel and is associated with several STAs in an infrastructure BSS. Each AP shown in FIG. 1 may have overlapping coverage and may cause interference to each other under certain conditions.

[0048] FIG. 2 illustrates a timeline and process 200 for cooperative transmission (CT) among a group of APs sharing a common BW on the same operating channel, such as APs 102a-102d in FIG. 1, according to one embodiment. In process 200, it may be assumed that some of the transmission parameter values ​​for cooperative transmission 210 may change between transmission opportunities (TXOPs) 206, and thus APs participating in a cooperative transmission agreement 204 may communicate with each other to negotiate parameter values. Examples of CT parameters include a list of APs, a cooperation scheme, and radio resource allocation. In step 202, a set of APs sharing a common BW on the same operating channel that participate in an M-AP CT BSS may be established. In step 204, a subset of APs in the M-AP set may negotiate a cooperative (transmission) agreement. This cooperative agreement enables the subset of APs in the M-AP set to perform cooperative transmissions under the same CT agreement over several TXOPs up to duration 206. Many of the CT agreement parameters negotiated in establishing the CT agreement do not require updating; only those required by network dynamics are actually updated for each TXOP. CT agreement-based announcement frames are introduced in the pre-transmission period (Pre-TX) 208 to allow an AP that acquires a TXOP to indicate the specific cooperative parameters of the current TXOP to other APs operating under the same CT agreement that will participate in the cooperative transmission of the current TXOP. Once the CT parameters have been exchanged or updated, M-AP cooperative transmission (CT) 210 may occur.

[0049] An embodiment implementing CT among multiple APs may utilize terminology introduced by the IEEE 802.11be task group. An Extremely High Throughput (EHT) AP that acquires a TXOP and initiates multi-AP cooperation may be referred to as a sharing AP. An EHT AP coordinated for multi-AP cooperative transmission by a sharing AP may be referred to as a shared AP. In a WLAN that supports cooperation between APs, a TXOP holder may share resources with other APs in the same M-AP set operating under the same cooperation agreement. A TXOP holder may be able to notify other APs that may participate in the cooperative transmission occurring in the current TXOP about the proposed cooperation parameters. Figure 3 shows TXOP holders 302a-302d, 304a, and 304b. TXOP holders 304a and 304b correspond to AP5 104a and AP6 104b, which do not participate in the cooperative transmission. The TXOP holders 302a-302d correspond to AP1-AP4 (reference numerals 102a-102d) and are configured for cooperative transmission as disclosed in the embodiments described herein to share the communication resources of the holders 302a-302d.

[0050] Embodiments facilitate communication between multiple APs sharing a common BW on the same operating channel, including establishing an M-AP set or coordination agreement. Communication between APs may be independent of the link that provides network access to other WLAN devices, such as STAs, that communicate with the AP.

[0051] While some communication between APs may occur over wired links, embodiments provide the advantage that some communication may occur over a wireless medium. To perform cooperative transmission (CT), multiple APs sharing a common BW on the same operating channel and optionally operating within the same coverage area may establish communications that enable long-term cooperative transmission with sufficient flexibility to change cooperative transmission agreement parameters as needed. APs wishing to establish in an M-AP set for CT purposes may perform AP peer provisioning and discovery, establishing communications between peer APs in a secure manner independent of STAs' operational network access, or managing and reconfiguring connection states between AP peers.

[0052] Embodiments provide a method for establishing an M-AP CT BSS as the basis for a set of APs (M-AP set) operating on the same channel with a common BW. Embodiments may apply mesh networking discovery, connection, and communication mechanisms from the IEEE 802.11-based standard for creating a multi-AP (M-AP) coordinated transmission (CT) basic service set (BSS). Because existing IEEE 802.11 mesh mechanisms do not include a central entity, such as an AP role, within an infrastructure BSS, these mechanisms can be reused by a set of APs to form an M-AP CT BSS. Mechanisms for discovery, connection management, security, and communication already defined for peering between mesh STAs may be adapted for peering between APs in an M-AP CT BSS. The distributed nature of mesh networking may be adapted to provide connectivity between subsets of APs for the purpose of generating CT agreements between APs operating on the same channel with a common BW.

[0053] An M-AP CT BSS is a special variant of a Mesh Basic Service Set (MBSS) in which peer APs form a multi-AP set. The IEEE 802.11-based standard Mesh ID may be used to identify the M-AP CT BSS for the purpose of frame exchange between APs in the M-AP set. AP members of an M-AP set operating within the same M-AP CT BSS can establish a CT agreement to apply one or more cooperative transmissions between these APs.

[0054] In embodiments, APs participating in an M-AP CT BSS may follow mesh requirements for advertising, discovery, authentication peering, security, MBSS synchronization, support for additional mesh peering, broadcasting, and triggered UL. Criteria for when an AP can join may be established. For example, embodiments may be most effective when APs in the M-AP set are within a minimum range of each other; therefore, an AP may choose to peer only with other APs in the M-AP set based on a proximity indication. An example of a proximity indication may be when the received signal strength indicator (RSSI) of a probe response frame measured from a received beacon frame exceeds an RSSI threshold, e.g., -62 dBm. Participating APs are not required to follow mesh requirements for path selection, hybrid wireless mesh, interworking with distribution systems (DSs), or bridging, power saving, or MCCA, as described in IEEE 802.11-based standards.

[0055] FIG. 4 illustrates a frame flow 400 that may be used in an embodiment to establish a peering relationship between any pair of APs in an M-AP CT BSS based on a WLAN mesh peering protocol. The APs may advertise the M-AP CT BSS in a beacon frame 402 using an “M-AP CT BSS” indicator. Existing IEEE 802.11 authentication protocols for mesh networking, such as Simultaneous Authentication of Equals (SAE) messages 404 and 406, may also be used between AP1 102a and AP2 102b. To establish a connection, mesh peering open 408 and 410 and mesh peering confirm 412 and 414 peering messages may be sent and received between candidate APs in the M-AP CT BSS. Each AP in the M-AP set completes peering with the other APs in the group to join and communicate with other group APs. Once peering is complete, AP members of the M-AP CT BSS exchange management frames to facilitate coordinated transmission. The management frame format follows the requirements for both individually addressed and group addressed management frame transmissions within an MBSS. An AP may terminate its M-AP CT BSS connection to another AP peer by sending a Mesh Peer Reclose frame.

[0056] The embodiment shown in FIG. 4 may be used to enable peer APs to advertise M-AP CT BSS capabilities in a distributed manner to initiate frame exchanges between peer APs in an M-AP set.

[0057] Referring to FIG. 5, embodiments may utilize existing beacon frames and probe response frames with modified mesh capability fields to advertise an M-AP CT BSS. An M-AP CT BSS may be advertised by adapting existing beacon frames or probe response frames used for mesh BSS. The beacon frames or probe response frames used for mesh BSS configuration include a mesh ID and authentication protocol identifier (as specified in the IEEE 802.11-2020 standard). FIG. 5 illustrates how the mesh component 502 used in a beacon frame or probe response frame may be modified to advertise an M-AP CT BSS. A beacon frame or probe response frame transmitted in an M-AP CT BSS may include various elements, namely: Mesh ID element limited to 2 octets, a mesh component 502; ·, a beacon timing element (optionally present); and Mesh channel switch parameter element (optionally present) Includes:

[0058] The mesh component 502 includes several fields. In an embodiment, some fields may be set to the values ​​shown in parentheses. A field with a recommended value set to the value 254 may be used to indicate that the field is not applicable when this element is carried in beacon and probe response frames transmitted in an M-AP CT BSS. Element ID 504 (recommended value = 45) Length 506 (recommended value = 8) Active Path Selection Protocol Identifier 508 (recommended value = 254) Active Path Selection Metric Identifier 510 (recommended value = 254) Congestion control mode identifier 512 (recommended value = 254) Synchronization method identifier 514 (recommended value = 254) Authentication Protocol Identifier field 516 (recommended value = valid value defined in IEEE 802.11-2020) Mesh Formulation Information field 518 (recommended values: 0 or 255) Mesh feature field 520 Mesh Extension Field 522

[0059] The mesh capability field 520 may be one octet in length, and the eight bits of the field are defined as follows: · B0: The M-AP may set Additional Mesh Peering Acceptance 524 to 1 to advertise mesh peering acceptance for the CT BSS. B1:MCCA Support 526 (recommended value = 0) B2: MCCA Enabled 528 (recommended value = 0) B3: Transfer 530 (recommended value = 0) B4: MBCA Enabled 532 (recommended value = 0) B5:TBBT adjustment 534 (recommended value = 0) B6: Mesh power saving level 536 (recommended value = 0) B7: Extended Mesh Capabilities Present 538 may be set to 1 to advertise that the mesh BSS is an M-AP CT BSS or to indicate the presence of an additional mesh capabilities extension field 522. In the latter case, the M-AP CT BSS may be advertised in the mesh capabilities extension field 522.

[0060] The mesh capability extension field 522 may be one octet in length and may be used when the extended mesh capability present bit 538 is set to one. B0: CT M-AP enabled 540 (recommended value = 1 if enabled) · B1-7: Reserved 542 and may be set to all 0's.

[0061] 5 with suggested fixed values ​​for the mesh configuration parameters shown in parentheses. A single reserved bit 538 (bit 7, extended mesh capabilities present field) is present in the mesh capabilities field 520. If the reserved bit 538 is not used to advertise an M-AP CT BSS, the mesh component 502 is 7 octets long and the extended mesh capabilities field 522 is not required. If the reserved bit 538 is used to advertise the presence of the extended mesh capabilities field 522 (to maintain scalability of the mesh component 502), the reserved bit 538 may be set to 1 to indicate that the extended mesh capabilities field 522 is present.

[0062] In an embodiment, a subset of APs, such as AP1-AP4 (reference numerals 102a-102d) in FIG. 1, that wish to establish an M-AP set need to form an M-AP CT BSS. In this case, an initiator AP, such as AP1 102a, may invite other responder APs within range to join the M-AP set initiated by AP1 102a. The initiator AP (e.g., AP1 102a) begins transmitting beacon frames advertising the M-AP CT BSS. Responder APs, such as any of AP2 102b, AP3 103c, or AP4 102d, may join the M-AP CT BSS and establish an M-AP set. APs joining the M-AP set may be assumed to be provisioned (e.g., using the method shown in FIG. 4) with a mesh ID and, if necessary, security credentials to complete peering securely. When a responder AP receives a beacon frame or probe response frame in which an M-AP CT BSS is advertised, it may begin advertising the M-AP CT BSS using the same mesh ID value and mesh components included in the received beacon frame or probe response frame and begin peering with the initiator AP and all responder APs within range (provided that each of them begins advertising their M-AP CT BSS using the same mesh ID value and mesh components as the responder AP). This embodiment may enable peer APs, such as those illustrated in FIG. 1, to utilize existing discovery and peering mechanisms used for mesh networks (e.g., using the functional values ​​shown in FIG. 5 and described in the description of FIG. 5) to establish an M-AP set with an M-AP CT BSS.

[0063] An embodiment may include both an M-AP CT BSS and an infrastructure BSS operating independently, which may result in an AP supporting multiple types of BSSs and even additional M-AP CT BSSs transmitting separate beacon frames for each type of BSS. In an embodiment, an M-AP CT BSS service may be operated by APs belonging to the same M-AP set, and the M-AP CT BSS may be advertised in beacon frames transmitted by each AP for its infrastructure BSS.

[0064] If any of the APs that want to initiate an M-AP set or join an existing M-AP set are part of a multi-BSSID (MBSSID) set, the M-AP CT BSS parameters may be added as a subelement within the multi-BSSID (MBSSID) element carried in the beacon frame transmitted by the transmitting BSSID of the multi-BSSID set (e.g., transmitted as part of the infrastructure BSS protocol).

[0065] In an embodiment, an AP configured to join an M-AP CT BSS may advertise a mesh membership and mesh ID element in a beacon or probe response frame to facilitate M-AP CT BSS discovery. Figures 6a and 6b show two ways to use the MBSSID (multi-BSSID) element 602 to advertise an M-AP CT BSS.

[0066] 6a, the existing non-transmitting BSSID profile sub-element included in the multi-BSSID element may be extended to include a mesh component 618 and a mesh ID element 620 for the corresponding non-transmitting BSSID. The mesh component 618 and mesh ID element 620 may be included in the non-transmitting BSSID profile sub-element only if the transmitting BSSID is not part of the M-AP set. In addition, if the transmitting BSSID is not included in the M-AP set, the list of element IDs (included in the non-inherited element 622 of the non-transmitting BSSID profile sub-element 610) should include the element ID values ​​of the mesh component 618 and mesh ID element 620.

[0067] The MBSSID element 602 includes the following elements: 1-octet element ID 604 (recommended value = 71) Length 606 MaxBSSID indicator 608 Variable length optional subelement 609 · Vendor-specific sub-element 612

[0068] The optional subelement 609 may include one or more non-transmit SSID profile subelements for different BSSs 610. Each non-transmit SSID profile subelement for a particular BSS in the multi-BSSID set 610 may include the following elements: 1-octet subelement ID 614 (recommended value = 0) Length 616 Non-transmitting BSSID specific element 617 Non-inheriting elements 622

[0069] The non-transmitting BSSID specific element 617 may further include required mesh components 618 and a mesh ID 620 .

[0070] The non-inheriting element 622 includes an element ID 624, a length 626, an element ID extension 628, an element ID list 630, and an element ID extension list.

[0071] 6b, in an embodiment, an M-AP CT profile sub-element 632 may be defined as a new sub-element of the Multiple BSSIDs element 602. As shown in the table of FIG. 6c, a sub-element ID 614 of value 1 may be used to indicate an M-AP CT BSS profile. The M-AP CT profile sub-element 632 may include the following: Mesh Component 618 Mesh ID element 620 Multiple BSSID Index List Element 634

[0072] The multiple BSSID index list element 634 may contain a list of all non-transmitting BSSIDs that are members of the MBSSID set and also members of the M-AP set. In this embodiment, the mesh component 618 and mesh ID element 620 are included only in the M-AP CT profile sub-element 632. If the transmitting BSSID is also a member of the M-AP set, the BSSID index list shall contain index 0. The existing non-transmitting BSSID profile remains unchanged from other embodiments.

[0073] Embodiments may include adding M-AP CT BSS as a sub-element of the Multi-BSSID (MBSSID) element defined in existing networking standards such as IEEE 802.11. This profile is ignored by non-AP STAs (i.e., stations that are not access points) and is only parsed by APs that support the M-AP cooperative transmission mechanism as described herein.

[0074] In an embodiment, the mesh component and mesh ID elements advertising the M-AP CT BSS may be included in a beacon frame or probe response frame as a profile in the common information field of an MBSSID element, a standalone element, or a multilink element. The MBSSID element may be carried in a beacon frame or probe response frame with the M-AP CT parameters included in a sub-element of the MBSSID element.

[0075] To discover peer APs for M-AP CT operations, an AP configured to join an M-AP set may scan for the M-AP CT BSS in beacon frames or probe response frames transmitted within an infrastructure BSS, or in the case of a multi-BSSID in an M-AP CT BSS profile included in a non-transmitting BSSID profile or MBSSID element. At the same time, if the AP does not discover an M-AP CT BSS advertised in a peer AP's infrastructure BSS beacon frame, it may add the M-AP CT BSS to the beacon frames it transmits to begin advertising the M-AP CT BSS itself. If the AP is a non-transmitting BSSID in a multi-BSSID set, the transmitting BSSID must add the M-AP CT BSS to the non-transmitting BSSID profile subelement or M-AP CT BSS profile subelement included in the MBSSID element carried in the beacon frame or probe response frame. Alternatively, all APs participating in the M-AP CT BSS discovery process may include the M-AP CT BSS in their beacon and probe response frames to facilitate faster discovery.

[0076] 6d, in an embodiment, in the case of multi-link operation (MLO), the M-AP CT BSS information of APs that belong to the same AP MLD as the current (reporting) AP may be included in the STA information field 651 of the per-STA profile sub-element 648 included in the basic multi-link element 640, e.g., the multi-link element defined in the IEEE 802.11 TGbe specification. The basic multi-link element 640 includes the following fields: Element ID 604 (recommended value = 255) Length 606 Element ID extension 642 (recommended value = 107) Multi-link control 644 Variable length common information 646 Variable length link information 648

[0077] The STA Control field 649 of the Per-STA Profile sub-element 648 included in the Link Information field 647 of the Basic Multilink element 640 may include an M-AP CT BSS Information Present sub-field 650. The STA Information field 651 may include a Mesh Component 665 and a Mesh ID element 666.

[0078] In summary, to advertise an M-AP CT BSS, an AP must include the Mesh Configuration and Mesh ID elements in its beacon or probe response frame. For non-transmitting BSSIDs in a multi-BSSID set, the transmitting AP may include these elements in either the non-transmitting BSSID profile subelement or the M-AP CT BSS subelement included in the MBSSID element. For multi-link operation, the current AP may advertise the M-AP CT BSS of other associated APs operating on other links in the same MLD.

[0079] 6a-6d, when an M-AP CT BSS is defined by an AP that includes a non-transmitting BSSID in its MBSSID set, embodiments may provide a new mechanism for an AP to listen for peer APs advertising the M-AP CT BSS profile. (In this embodiment, the MBSSID set includes the set of non-transmitting BSSIDs advertised in the multi-BSSID element included in beacon and probe response frames transmitted by the transmitted BSSIDs of this set.) In addition, this may lead to a reduction in the number of beacon and probe response frames transmitted, thus efficiently utilizing the intermediate time available for data frame exchange. In embodiments, mesh component 618 may have the same format as mesh component 502 of FIG. 5.

[0080] If an M-AP CT BSS is listed in an M-AP CT subelement, the M-AP CT BSS may include a subelement ID 614, a length 616, a mesh component 618, a mesh ID 620, and a multiple BSSID index list element 634. In an embodiment, the mesh component 618 may have the same format as the mesh component 502 of FIG.

[0081] It should be noted that in an embodiment, if an AP attempting to join an M-AP set does not detect an M-AP CT BSS non-transmitting BSSID profile containing an MBSSID element in a received beacon frame or probe response frame, it may begin transmitting itself and initiate the creation of a new M-AP CT BSS for the establishment of the M-AP set.

[0082] In an embodiment, the M-AP CT BSS may be configured at the medium access control (MAC) layer via a station management entity (SME). The SME may receive the M-AP CT BSS configuration via an external management entity, such as a WLAN controller or multi-AP controller, as may be done with other networking protocols such as Wi-Fi Easy mesh. Configuration parameters are conveyed to the MAC layer using MAC sublayer management entity (MLME) primitives that can be used to configure the M-AP CT BSS. Embodiments may include primitives such as the MLME-M-AP-CT-BSS-CONFIG.request(mesh-id, auth-proto-id, authentication information, mesh configuration) primitive or the MLME-M-AP-CT-BSS-CONFIG.confirm(status) primitive. In these primitives, "mesh-ID" may refer to the mesh-ID element of the M-AP CT BSS, "auth-proto-id" may refer to the authentication protocol identifier of the M-AP CT BSS, "credential-info" may refer to the authentication information of the M-AP-CT-BSS based on the value of the authentication protocol identifier, "Mesh Configuration" may refer to the mesh components, and "status" may refer to the status code of the request, which may have a value of at least SUCCESS or FAIL.

[0083] In embodiments, existing primitives already defined in the IEEE 802.11 standard, such as the MLME-MESHPEERINGMANAGEMENT primitive, may be used by the SME to manage the connectivity state of APs in an M-AP CT BSS. Embodiments allow for an interface to be defined within the AP to allow an external management entity to control the creation of an M-AP CT BSS.

[0084] In embodiments, an M-AP CT BSS may be formed using the functionality of existing MBSS mechanisms from other standards. An AP wishing to establish an M-AP set transmitting beacon frames may advertise the M-AP CT BSS in its beacon frame or probe response frame, such as by including an MBSS element in the beacon frame. An AP wishing to join an existing M-AP CT BSS may discover and peer with neighboring APs operating on the same channel and having a common BW, and establish a security association (SA), which may include the following IEEE 802.11 security keys: PMKSA, PTKSA, and GTKSA. CT APs may be configured by an external management entity of the M-AP CT BSS, as described herein. APs wishing to establish a secure M-AP set may use authenticated mesh peering exchange (AMPE) to establish the SA for secure peering. Within AMPE, SAE may be used as the authentication protocol within IEEE 802.11 authentication frames. Mesh peering may be used to establish AP-AP links.

[0085] Referring to FIG. 7, method 700 begins in step 702 when an AP receives an M-AP CT BSS configuration from a management entity, such as an SME. In step 704, the AP may advertise M-AP CT BSS parameters in a beacon frame. If the AP associates with an MBSSID set and supports non-transmitting BSSIDs in this set, the transmit BSSIDs shall include M-AP CT BSS parameters in the beacon frames they transmit. Two sets of actions may then occur: the AP scans for peers and responds appropriately, or the AP receives a probe request and then responds to the received peering request. In step 706, the AP scans for neighboring APs that belong to the same M-AP CT BSS, and these parameters may be included in probe response frames or beacon frames transmitted by these neighboring APs. In step 708, the AP may initiate peering with any peer APs discovered in step 706 with the same M-AP CT BSS profile. In step 710, the AP may respond to probe request frames from any neighboring APs. Then, in step 712, the AP may respond to any successive peering requests received from these neighboring APs in step 710. After both step 708 and step 712, the AP can establish a CT agreement with either the peer AP from step 708 or step 712.

[0086] In an embodiment, APs may be provisioned to discover and peer with other APs that are members of the same M-AP CT BSS. This provisioning may be performed by an external (M-AP) management entity, which may reside in a WLAN controller (as used in a Wi-Fi Easy mesh) or a multi-AP controller. This M-AP management entity may monitor overall network performance and dynamically change the M-AP CT BSS configuration to add or remove APs and form different M-AP groups. When an AP receives a new configuration from the M-AP management entity, the AP may be configured to disconnect from its current M-AP CT BSS and discover and join a new M-AP CT BSS. It is also possible to split an existing M-AP CT BSS into smaller M-AP CT BSSs with different mesh profiles, and dynamic reconfiguration may be achieved by the peer APs themselves without the assistance of an M-AP management entity.

[0087] Referring to the topology 800 illustrated in FIG. 8, a network controller element 808 provides network access outside of topologies 800 and 900. One M-AP CT BSS, designated CT-BSS 0A-01 802, includes AP1 804 and AP2 806. A second M-AP CT BSS, designated CT-BSS 0A-02 818, includes AP3 820 and AP4 822. If a change in the radio environment occurs, the change may trigger an M-AP management entity to update the configuration. In FIG. 9, the M-AP management entity changes the M-AP CT BSS configuration of AP3 820 and AP4 822. AP3 820 and AP4 822 apply the new configuration and peer with AP1 804 and AP2 806 in the same CT-BSS, CT-BSS 0A-01 802, which has mesh ID 0A-01.

[0088] The ability of embodiments to modify and reuse existing mesh network protocols and data structures provides the technical advantage of facilitating implementation into existing WLAN systems and methods.

[0089] It will be understood by those skilled in the art that the elements, fields, and bit encodings may be modified and changed in a consistent and standardized manner to enable the design and manufacture of compatible wireless systems and protocols without departing from the teachings described herein.

[0090] 10 is a schematic diagram of a communication device 1000 that may be used in the embodiments of the present disclosure described herein. For example, an AP, an SME, and an STA are all examples of communication devices. It should also be noted that a communication device of the present disclosure may include a microcontroller or microprocessor that executes program instructions stored in a memory, or other digital or analog circuitry, or a combination thereof.

[0091] As shown, the device includes a processor 1010, such as a central processing unit (CPU), or a special-purpose processor such as a graphics processing unit (GPU), or other such processing unit, memory 1020, non-transitory mass storage 1030, I / O interface 1040, and network interface 1050, all communicatively coupled via a bidirectional bus 1070. According to a particular embodiment, any or all of the illustrated elements may be utilized, or only a subset of the elements may be utilized. Furthermore, communications device 1000 may include multiple instances of a particular element, such as multiple processors, memories, or transceivers. Elements of a hardware device may also be directly coupled to other elements without a bidirectional bus.

[0092] The memory 1020 may include any type of non-transitory memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or any combination of the like. The mass storage element 1030 may include any type of non-transitory storage device, such as a solid-state drive, a hard disk drive, a magnetic disk drive, an optical disk drive, a USB drive, or any computer program product configured to store data and machine-executable program code. According to particular embodiments, the memory 1020 or mass storage 1030 may record statements and instructions executable by the processor 1010 to perform any of the method steps described above.

[0093] Although specific embodiments of the present technology have been described herein for illustrative purposes, it should be understood that various modifications can be made without departing from the scope of the present technology. Accordingly, the specification and drawings should be considered merely as illustrative of the disclosure as defined by the appended claims, and it is intended to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the present disclosure. In particular, it is within the scope of the present technology to provide a computer program product or program element, or a program storage or memory device, such as a magnetic or optical wire, tape, or disk, for storing machine-readable signals, for controlling the operation of a computer in accordance with the methods of the present technology, and / or for structuring some or all of its components in accordance with the systems of the present technology.

[0094] The operations associated with the methods described herein may be embodied as coded instructions in a computer program product, which is a computer-readable medium having recorded thereon software code for performing the methods when the computer program product is loaded into a memory and executed on a microprocessor of a wireless communication device.

[0095] The operations associated with the methods described herein may be embodied as coded instructions in multiple computer program products. For example, a first portion of the method may be performed using one computing device, and a second portion of the method may be performed using another computing device, a server, etc. In this case, each computer program product is a computer-readable medium having software code recorded thereon for performing appropriate portions of the method when the computer program product is loaded into memory and executed on a microprocessor of the computing device.

[0096] Furthermore, each step of the method can be executed on any communication device according to one or more, or one or more partial program elements, modules, or objects created from any programming language, such as C++, Java, etc. In addition, each step, or a file, object, etc. implementing each said step, may be executed by dedicated hardware or a circuit module designed for that purpose.

[0097] While the invention has been described with reference to particular features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the invention. Accordingly, the specification and drawings are to be regarded solely as illustrative of the invention as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations or equivalents that are within the scope of the invention. [Explanation of symbols]

[0098] 102a AP1, 102b AP2, 102c AP3, 102d AP4, 104a AP5, 104b AP6, 200 Process, 204 Cooperative Transmission Agreement, 206 Transmission Opportunity (TXOP), duration, 208 Pre-Transmission Period (Pre-TX), 210 Cooperative Transmission, 302a, 302b, 302c, 302d, 304a, 304b TXOP Holder, 400 Frame Flow, 402 Beacon Frame, 404, 406 Simultaneous Authentication of Equals (SAE) Message, 408, 410 Mesh Peering Open, 412, 414 Mesh Peering Confirm, 502 Mesh Element, 504 Element ID, 506, 606, 616, 626 Length, 508 Active Path Selection Protocol Identifier, 510 Active Path Selection Metric Identifier, 512 Congestion Control Mode Identifier, 514 Synchronization Method Identifier, 516 Authentication Protocol Identifier Field, 518 Mesh Formulation Information Field, 520 Mesh Capability Field, 522 Mesh Capability Extensions Field, Extended Mesh Capability Field, 524 Additional Mesh Peering Acceptance, 526 MCCA Support, 528 MCCA Enable, 530 Forwarding, 532 MBCA Enable, 534 TBBT Adjustment, 536 Mesh Power Save Level, 538 Extended Mesh Capability Present Bit, Reserved Bit, 540 CT M-AP Enable, 542 Reserved, 602 MBSSID (Multi-BSSID) Element, Multiple BSSID Element, 604, 624 Element ID, 608 MaxBSSID Indicator, 609 Variable Length Optional Subelement, 610 Non-Transmit BSSID Profile Subelement, 612 Vendor-Specific Subelement, 614 Subelement ID, 617 Non-Transmit BSSID Specific Elements, 618 Mesh Component, 620 Mesh ID Element, 622 Non-Inherited Element, 628 Element ID Extension, 630 Element ID List, 632 M-AP CT Profile Sub-Element, 634 Multiple BSSID Index List Element, 640 Basic Multilink Element, 642 Element ID Extension, 644 Multilink Control, 646 Common Information, 647 Link Information Field, 648 Link Information Sub-Element, 649 STA Control Field, 650 M-AP CT BSS Information Presence Sub-Element, 651 STA Information Field, 665 Mesh Component, 666Mesh ID element, 700, method, 800, topology, 802, CT-BSS 0A-01, 804, AP1, 806, AP2, 808, network controller element, 818, CT-BSS 0A-02, 820, AP3, 822, AP4, 1000, communication device, 1010, processor, 1020, memory, 1030, non-transitory mass storage, mass storage element, 1040, I / O interface, 1050, network interface, 1070, bidirectional bus

Claims

1. 1. A method for configuring a multiple access point (M-AP) set, the method comprising: transmitting, by an access point (AP) initiating a new M-AP set, an information element including a plurality of octets, one of the plurality of octets indicating the presence of an extension octet of the plurality of octets, the extension octet indicating whether a M-AP cooperative transmission (CT) basic service set (BSS) is enabled for this AP; A method comprising:

2. The method of claim 1 , wherein the enablement of the M-AP cooperative transmission (CT) basic service set (BSS) is indicated by a bit in the extension function octet.

3. The method of claim 1 or 2, wherein the information element is included in a beacon frame or a probe response frame transmitted within the M-AP CT BSS.

4. 4. The method of claim 1, wherein the Mesh Capability subfield indicating the presence of the Extensions octet is coded as the hexadecimal value 0x81.

5. The method of any one of claims 2 to 4, wherein the bit is coded as 1 to indicate that the M-AP CT function is enabled.

6. The method of claim 1 , wherein the information element further comprises a mesh ID and an authentication protocol identifier.

7. The information element is: length, Active path selection metric identifier, Active path selection metric identifier, Congestion control mode identifier, Synchronization method protocol identifier, Mesh formation information, or Mesh Features 6. The method of claim 1, further comprising:

8. 8. The method of claim 7, wherein the length subfield has a value of 8, the active path selection metric identifier subfield has a value of 254, the active path selection metric identifier subfield has a value of 254, the congestion control mode identifier subfield has a value of 254, the synchronization method protocol identifier subfield has a value of 254, or the mesh formation information subfield has a value of 0.

9. The method of claim 1 , wherein the mesh component comprises an extended mesh capabilities subfield.

10. The method according to any one of claims 2 to 9, wherein the enhanced mesh capability subfield includes the bit indicating the enablement of the M-AP CT BSS.

11. The last octet is Additional Mesh Peering Acceptance subfields, MCCA support subfields, MCCA Enable subfield, Transfer subfield, MBCA Enable subfield, TBBT adjustment subfield, Mesh Power Save Level subfield, or Enhanced Mesh Feature Presence Subfield 11. The method of claim 1, comprising:

12. 12. The method of claim 11 , wherein the Additional Mesh Peering Acceptance subfield has a value of 1, the MCCA Support subfield has a value of 0, the MCCA Enable subfield has a value of 0, the Forwarding subfield has a value of 0, the MBCA Enable subfield has a value of 0, the TBBT Adjustment subfield has a value of 0, the Mesh Power Saving Level subfield has a value of 0, or the Enhanced Mesh Capability Present subfield has a value of 1.

13. 1. A method for establishing a multiple access point (M-AP) set among access points (APs), the method comprising: transmitting, by a first AP, a first message advertising a M-AP cooperative transmission (CT) basic service set (BSS); receiving, by the first AP, a second message from a second AP advertising a second M-AP CT BSS; initiating peering used by an M-AP set including the first AP and the second AP in response to receiving the first message or the second message; A method comprising:

14. The method of claim 13 , further comprising receiving, by the first AP, a peering open message from the second AP.

15. The method of claim 13 , further comprising sending, by the first AP, a peering open message to the second AP.

16. The method of any one of claims 13 to 15, further comprising the step of provisioning the M-AP set with security credentials.

17. The step of provisioning the M-AP set includes: sending, by the first AP, a mesh peering open frame to the second AP; receiving, by the first AP, from the second AP, a mesh peering confirm frame transmitted by the second AP in response to the second AP receiving the mesh peering open frame; 17. The method of any one of claims 13 to 16, comprising:

18. 1. A method for an access point (AP) to initiate establishment of a multiple access point (M-AP) set or join an existing M-AP set, the AP being part of a multiple basic service set identifier (MBSSID) set, the method comprising: adding, by the AP, a sub-element to a Multiple Basic Service Set Identifier (MBSSID) element carried in a beacon frame or a probe response frame transmitted on a transmitting BSSID of the MBSSID set, the sub-element including a Mesh ID element and a Mesh Component element containing the parameters of a M-AP cooperative transmission (CT) basic service set (BSS); A method comprising:

19. 20. The method of claim 18, wherein the sub-element corresponds to a non-transmitting BSSID profile sub-element, the non-transmitting BSSID profile sub-element further comprising a non-inheriting element, the non-inheriting element comprising a list of element IDs, the list of element IDs comprising element ID values ​​of the mesh components and the mesh ID element.

20. 19. The method of claim 18, wherein the subelement corresponds to an M-AP CT BSS subelement, the M-AP CT BSS subelement including the mesh component, the mesh ID element, and an MBSSID index list element, the MBSSID index list element including a list of non-transmitting BSSIDs corresponding to the MBSSID set that are also members of the existing M-AP set.

21. The method of claim 20, wherein the transmitting BSSID that is a member of the M-AP set is indicated as index 0 in the BSSID index list.

22. 1. A method for an access point (AP) associated with an access point multilink device (AP MLD) and operating on a particular link of a plurality of links to initiate establishment of a multiple access point (M-AP) set on another link of the same AP MLD or to join an existing M-AP set on another link of the same AP MLD, the method comprising: adding, by the AP, a first subfield to a STA Control field of a Per-STA Profile sub-element included in a Basic Multilink element carried in a beacon or probe response frame, the first sub-field including an indication that M-AP cooperative transmission (CT) basic service set (BSS) information is present in a STA Information field of the Per-STA Profile sub-element; adding, by the AP, further elements to the STA information field of the Per-STA Profile sub-element, specifically, a Mesh Component including the Mesh ID element and the parameters of the M-AP CT BSS; A method comprising:

23. receiving, by the AP, a beacon frame or a probe response frame including the MBSSID element, the MBSSID element including the sub-element; extracting, by the AP, profiles of the M-AP set from the sub-elements, the M-AP set being capable of M-AP CT operations; 23. The method of any one of claims 18 to 22, further comprising:

24. 1. A method for configuring a medium access control (MAC) layer by a station management entity (SME), the method comprising: receiving, by the SME, multiple AP (M-AP) coordinated transmission (CT) basic service set (BSS) configuration parameters from an external management entity; A method comprising:

25. The method of claim 24 , wherein the external management entity is a WLAN controller device or a multi-access point (AP) controller.

26. receiving, by a MAC Layer Management Entity (MLME), from the SME, a request primitive including a mesh ID associated with the M-AP CT BSS, an authentication protocol identifier for the M-AP CT BSS, or authentication information for the M-AP CT BSS; 26. The method of claim 24 or 25, further comprising:

27. sending, by the MLME, to the SME, a confirmation primitive including the status of the configuration request.

27. The method of claim 26, further comprising:

28. 1. A method for configuring a multiple access point (M-AP) set, the method comprising: monitoring, by an external management entity, a first multiple AP (M-AP) coordinated transmission (CT) basic service set (BSS); sending, by the external management entity, second M-AP CT BSS configuration parameters to APs participating in the first M-AP CT BSS, instructing the APs to associate with the second M-AP CT BSS; A method comprising:

29. 1. A method for configuring a multiple access point (M-AP) set, the method comprising: receiving, by an access point (AP) participating in a first multiple-AP (M-AP) coordinated transmission (CT) basic service set (BSS), a second M-AP CT BSS configuration parameter set from an external management entity; joining, by the AP, to the second M-AP CT BSS in response to receiving the second M-AP CT BSS configuration parameter set; A method comprising:

30. discovering, by the AP, a second M-AP CT BSS; joining, by the AP, the second M-AP CT BSS; 30. The method of claim 29, further comprising:

31. 31. The method of claim 28 or 30, wherein the external management entity is a WLAN controller of a multi-access point (AP) controller.

Images