Transport mechanism selection for Multi-Access Point Coordination Group (CG)
By receiving transmission capacity information and path estimation, and selecting appropriate wired or wireless transmission modes, the problem of low MAPC coordination efficiency in the Wi-Fi 8 standard is solved, achieving efficient communication and reliability in multi-access point networks.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CISCO TECHNOLOGY INC
- Filing Date
- 2024-12-19
- Publication Date
- 2026-07-31
AI Technical Summary
The existing Wi-Fi 8 standard fails to effectively address the issue of choosing between wired or wireless paths for transmitting MAPC coordination messages in the Multi Access Point Coordination (MAPC) mode, resulting in low coordination efficiency.
By receiving transmission capability information from other devices through network equipment, estimating the transmission time of wired and wireless paths, selecting the appropriate transmission mode based on the MAPC mode, including C-TDMA and C-SR modes, and utilizing path estimation and mode selection between the leader AP or decentralized APs, synchronous communication within the network is ensured.
It improves communication efficiency and reliability under multi-access point coordination, adapts to dynamic network environments, ensures the selection of the optimal transmission path under different network conditions, and achieves efficient MAPC coordination.
Smart Images

Figure CN122498124A_ABST
Abstract
Description
[0001] Cross-references to related applications This application claims the benefit of pending U.S. provisional patent application No. 63 / 612,295, filed on December 19, 2023. The aforementioned related patent application is incorporated herein by reference in its entirety. Technical Field
[0002] The embodiments presented in this disclosure generally relate to wireless communication. More specifically, the embodiments disclosed herein relate to selecting a transmission mechanism for a Coordination Group (CG) based on the deployed Multi Access Point Coordination (MAPC) mode and estimated path characteristics. Background Technology
[0003] The emerging Wi-Fi 8 standard primarily focuses on inter-BSS (over-the-air) communication for MAPC. However, it does not address the potential of network infrastructure to facilitate MAPC coordination through traditional connections such as access point (AP) to AP Ethernet / WiFi links, AP-Wireless LAN controller (WLC)-AP Ethernet / IP communication, or even root access point (RAP)-mesh access point (MAP) mesh networks (excluding point-to-point setups). In these configurations, APs can transmit discovery and coordination messages for MAPC across the network, using wired or wireless paths, to improve overall coordination efficiency. Despite these possibilities, the choice between these transmission options (wired or wireless paths for multi-AP coordination) and the rationale for such decisions are not yet defined by existing standards. Attached Figure Description
[0004] To gain a more detailed understanding of the features described above, reference can be made to embodiments that provide a more specific description of the disclosure briefly outlined above, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only typical embodiments and should not be considered limiting; other equally effective embodiments are also contemplated.
[0005] Figure 1A-1C An example network architecture for multi-AP coordination according to some embodiments of this disclosure is described.
[0006] Figure 2 This is a flowchart depicting communication between an AP and a STA for transmission mode selection and multi-AP coordination, according to some embodiments of the present disclosure.
[0007] Figure 3 Wired path configurations for a CG with a leading AP are depicted according to some embodiments of this disclosure.
[0008] Figures 4A-4CWired path configurations for decentralized CG are shown according to some embodiments of this disclosure.
[0009] Figure 5 An example method for leading an AP to determine the transmission mode of a CG, according to some embodiments of the present disclosure, is described.
[0010] Figure 6 Example methods for participating in AP estimation of path and transmission time for transmission mode selection are described according to some embodiments of the present disclosure.
[0011] Figure 7 This is a flowchart depicting an example method for selecting a transport mode based on a MAPC deployment mode, according to some embodiments of the present disclosure.
[0012] Figure 8 Example network devices configured to perform various aspects of this disclosure are described.
[0013] For ease of understanding, the same reference numerals are used where possible to designate the same elements common in the figures. It is contemplated that elements disclosed in one embodiment may be advantageously used in other embodiments without specific description. Detailed Implementation
[0014] Overview One embodiment presented in this disclosure provides a method comprising: receiving information from one or more other network devices within a coordination group (CG), wherein the CG is configured to operate using a Multi-AP Coordination Protocol (MAPC) mode, and the information indicating, for each of the one or more other network devices, support for acting as a transport node on a wired connection and a MAPC transport role within the CG; estimating, based on the received information, a wired path between the network device and at least one of the one or more other network devices in the CG; determining, by the network device, the transmission time required to communicate via at least one of the wired paths; determining, by the network device, the transmission time required to communicate via at least one wireless path between the network device and at least one of the one or more other network devices in the CG; selecting, by the network device, a transport mode for at least one of the one or more other network devices in the CG based on the transmission time of the wired path, the transmission time of the wireless path, and at least one of the MAPC modes; communicating the transport mode to at least one of the one or more other network devices in the CG; and performing network coordination operations with the one or more other network devices in the CG using the transport mode.
[0015] Other embodiments of this disclosure provide one or more non-transitory computer-readable media that contain computer program code in any combination, which, when executed by the operation of a computer system, performs operations according to one or more of the methods described above; other embodiments of this disclosure also provide a system for a network device, comprising: one or more memories that collectively contain one or more programs; and one or more computer processors, wherein the one or more processors are individually or collectively configured to perform operations according to one or more of the methods described above.
[0016] Example Implementation Messages used for MAPC can be transmitted via wired or wireless (or over-the-air (OTA)) connections using various network configurations, including AP-to-AP Ethernet / WiFi links, AP-WLC-AP Ethernet / IP communication, or even RAP-MAP mesh networks. The Wi-Fi 8 standard and existing frameworks do not fully address this possibility, nor do they provide clear guidance for choosing among these transmission options. Furthermore, different MAPC modes may have different transmission requirements, further complicating the selection of the appropriate transmission mode for multi-AP coordination. For example, Coordinated Time Division Multiple Access (C-TDMA) mode prioritizes group reliability over speed because Transmission Opportunities (TXOPs) are scheduled for the future, and TXOPs are wasted or destroyed if all APs in the CG fail to comply (e.g., do not receive messages). In contrast, Coordinated Spatial Multiplexing (C-SR) mode requires group distribution speed rather than high reliability because coordination occurs over one or a few TXOPs, primarily for best-effort service among a large number of potential APs. In C-SR mode, MAPC coordination can still succeed if messages are lost, although fewer APs are involved.
[0017] This disclosure describes techniques for selecting an appropriate transmission mechanism for a Group Control Center (CG) based on the currently used MAPC mode (e.g., C-TDMA, C-SR, or other modes) and the transmission characteristics of the evaluated wired or wireless paths. More specifically, this disclosure provides a method for APs in a CG to broadcast their transmission capability information to other devices within the group. In some embodiments, the transmission capability information may include an indication of the AP's ability to act as a transmission node in wired communications, and its role within the network (e.g., relay or endpoint). In embodiments where a leader AP (or WLC) exists within the CG, MAPC coordination may be centralized, involving one-to-N communication between the leader AP (or WLC) and participating APs within the CG. In this configuration, the leader AP (or WLC) can collect broadcast information from each participating AP and estimate the path and transmission time from itself to each of these participating APs. The estimation process may take into account both wired and wireless paths, as well as the specific requirements of the currently used MAPC mode (e.g., C-TDMA or C-SR). By evaluating these factors, the leader AP (or WLC) can make an informed decision about whether to use wired or wireless transmission for multi-AP coordination throughout the CG. The selected transmission mode can be aligned with the performance and reliability requirements indicated by the deployed MAPC mode (e.g., C-TDMA, C-SR, or other modes).
[0018] In embodiments where there is no leading AP within the CG, MAPC coordination can be decentralized, involving N-to-N communication between APs. In a decentralized setting, each participating AP within the CG can independently estimate the path and transmission time between itself and other APs. These estimates can then be collectively analyzed (e.g., by a designated AP for transmission mode selection) to determine an appropriate transmission mode for the entire CG, taking into account the MAPC mode the CG is operating in (e.g., C-TDMA, C-SR, or other modes) and the specific requirements of that mode for reliability, speed, and flexibility.
[0019] Figure 1A-1C An example network architecture for multi-AP coordination according to some embodiments of this disclosure is described.
[0020] Figure 1A A network setup 100A with AP-to-AP Ethernet / WiFi connections is depicted. The diagram illustrates how the APs communicate via both wired and wireless connections. In some embodiments, the wireless connection may also be referred to as an OTA connection. Three APs are depicted, including AP 1 (105-1), AP 2 (105-2), and AP 3 (105-3). In some embodiments, each AP can connect to one or more Stations (STAs) and form a Basic Service Set (BSS). In some embodiments, the three APs can collectively form a CG for multi-AP coordination.
[0021] As shown in the figure, three APs 105 are connected via Ethernet cables 115, forming a wired backbone for communication within the CG. In addition to these Ethernet connections 115, wireless links 110 are also established between the APs 105. This setup allows for the use of wired or wireless paths (e.g., 115 or 110) or both, providing flexibility in MAPC communication.
[0022] In some embodiments, MAPC messages (e.g., discovery or coordination messages) can be transmitted via Ethernet cable 115 or wireless link 110, depending on network conditions and the specific requirements of the MAPC mode in operation. For example, when low-latency and high-reliability communication is required (e.g., in C-TDMA mode), wired Ethernet path 115 may be more suitable for transmitting coordination messages to ensure that all APs 105 (including AP 1 (105-1), AP 2 (105-2), and AP 3 (105-3)) receive information synchronously. Conversely, in embodiments where flexibility and rapid deployment are prioritized (e.g., in C-SR mode), wireless link 110 can be used to quickly distribute MAPC messages across APs.
[0023] Furthermore, in some embodiments, the choice between wired or wireless transmission modes may also need to consider the condition of the path. For example, in C-TDMA mode, a wired mode can be selected if the Ethernet cable 115 is in good condition, the AP 105 on the path can handle the required relay with minimal (or at least reduced) latency, and the overall transmission time is within acceptable limits to ensure synchronous communication across the CG. If any of these conditions are not met, the system can switch to wireless mode to maintain the required coordination. When the CG is operating in C-SR mode, wireless mode may be preferred because wireless link 110 can provide greater flexibility and adaptability. However, if the wireless path experiences high congestion or reduced signal strength, which negatively impacts communication performance, the system can switch to wired mode, utilizing wired connection 115 to maintain efficient MAPC communication.
[0024] Figure 1B A network setup 100B with an AP-WLC-AP Ethernet / WiFi connection is depicted. The diagram illustrates how AP 105 connects to WLC 120 using both wired and wireless connections, and how they connect to each other.
[0025] Three access points (APs) are depicted, including AP 1 (105-1), AP 2 (105-2), and AP 3 (105-3). The three APs are connected to a Wireless Local Area Network (LAN) Controller (WLC) 120 via Ethernet cable 115. In some embodiments, each AP 105 can connect to one or more STAs and form a BSS, and the three APs 105 can operate collaboratively within a CG for multi-AP coordination. In the example network setup 100B, the wired connection 115 can be used to transmit MAPC messages (e.g., discovery or coordination messages) between the WLC 120 and the APs 105. When the wired connection 115 is interrupted or the WLC 120 is not enabled, the wireless connection 110 between the APs 105 can provide an alternative communication path for MAPC. These wireless links 110 allow the network to continue operating and maintain coordination even in the absence of a direct wired connection.
[0026] In embodiments where the WLC 120 is also wirelessly connected to the AP 105 (as shown by dashed line 125), both wired and wireless communications can support multi-AP coordination. In this configuration, the choice of communication path (e.g., wireless or wired) may need to take into account the MAPC mode in operation. For example, when using C-TDMA mode, which requires precise timing and high reliability, a wired Ethernet path 115 may be preferred to ensure that all APs 105 receive coordination messages synchronously. When using C-SR mode, which prioritizes speed and flexibility over reliability, a wireless link 125 between the WLC 120 and the AP 105 can be selected if these links offer better performance under current network conditions.
[0027] Figure 1C A hierarchical mesh network setup 100C is depicted, in which a root access point (RAP) 135 is wirelessly connected to several mesh access points (MAPs) 130 located at different levels within the network. The RAP 135 acts as the main gateway of the network and is connected to the network backbone (e.g., a switch 150) via an Ethernet cable 115. The MAPs 130 are arranged in a hierarchical structure, communicating wirelessly with the RAP 135 and with each other, forming a multi-level mesh network. In the MAPs, MAP 1 (130-1), MAP 2 (130-2), and MAP 3 (130-3) are located in the first level and are directly connected to the RAP 135, while MAP 4 (130-4), MAP 5 (130-5), and MAP 6 (130-6) are located in the second level and are connected to their respective MAPs in the first level. In this configuration, MAPC messages (e.g., discovery or coordination messages) can be transmitted via a wireless link 110 between the RAP 135 and the MAPs 130 to form a CG and / or perform coordination.
[0028] Due to its multi-level mesh structure, MAPC message transmission follows a hierarchical relay pattern. For example, when RAP 135 needs to send a coordination message to MAP 130 in the second level (e.g., MAP 4 (130-4)), the message can first be wirelessly transmitted to the first level MAP (e.g., MAP 1 (130-1)). Then, MAP 1 (130-1) can relay the message to MAP 4 (130-4). This relay mechanism ensures that MAPC messages are effectively propagated throughout the network, reaching all necessary levels, and maintaining the coordination and synchronization of the entire mesh network.
[0029] In the depicted mesh network, MAP 130 is wirelessly connected to RAP 135. Therefore, only the wireless path is available for transmitting MAPC messages. However, in embodiments where MAP 130 in different levels is also connected to RAP via cable 140 (shown as dashed lines), MAPC messages can also be relayed via wired connections. For example, MAP 4 (130-4) in the second level can be connected to MAP 1 (130-1) in the first level via one cable, and then MAP 1 (130-1) can be connected to RAP 135 via another cable. Messages from RAP 135 to MAP 4 (130-4) can be forwarded by MAP 1 (130-1) via two wired cables 140. In this configuration, both wired and wireless connections (e.g., 140 and 110) can be used to transmit MAPC messages, and the choice of path or transmission mode (wired or wireless) can take into account the specific requirements of the MAPC mode being used within the CG. For example, if using C-TDMA mode, wired path 140 may be preferred due to its high reliability and low latency. Alternatively, if using C-SR mode, Wireless Path 110 may be favored for its flexibility and speed in dynamic network environments.
[0030] More details regarding the calculation of transmission time for wired and wireless paths within CG, as well as the selection of transmission mechanisms (wired or wireless), will be provided below. Figure 2 -4 will be discussed.
[0031] Figure 2 This is a flowchart 200 depicting communication between an AP (e.g., 205 or 210) and a STA (e.g., 215) for transmission mode selection and multi-AP coordination, according to some embodiments of the present disclosure.
[0032] In some embodiments, AP 205 may correspond to a participating AP (also referred to as a peer AP in some embodiments) in an established CG or a potential (not yet fully formed but exchanging discovery messages) CG. The participating AP may be configured to send a request to the leading AP or WLC to coordinate data transmission using a shared channel. In some embodiments, AP 205 may correspond to Figure 1A AP 105-2 and 105-3 as depicted in the document Figure 1B The AP 105-1, 105-2 and 105-3 depicted in the document, or Figure 1C MAP 130 as depicted in the document.
[0033] In some embodiments, AP / WLC 210 may correspond to a leading AP or WLC in an established CG or a potential (not yet fully formed but exchanging discovery messages) CG. The leading AP or WLC may be configured to: aggregate information from participating APs, determine the MAPC mode (e.g., C-TDMA, C-SR, or other modes) and / or transmission mode (wired or wireless), and provide instructions for data transmission to ensure synchronous communication within the CG. In some embodiments, AP 205 may correspond to... Figure 1A AP 105-1 as depicted in the document Figure 1B The WLC 120 depicted in the article, or Figure 1C RAP 135 as depicted in the text.
[0034] In a decentralized setup where there is no leading AP or WLC, AP / WLC 210 can correspond to another participating AP, which communicates directly with AP 205 to coordinate MAPC activities.
[0035] As shown in the figure, AP 205 broadcasts its transmission capability information to AP / WLC 210 (step 220). In some embodiments, the transmission capability information may include an indication of AP 205's ability to act as a transmission node in wired communication. As used herein, the ability to act as a transmission node in wired communication may refer to the ability to transmit MAPC signals over a wired cable. In some embodiments, the capability information may also include details about the possible role or location of device 205, such as whether it is an endpoint in the network topology or a relay point connecting two APs via a wired connection.
[0036] In some embodiments, capability information may be included and transmitted via beacon or probe responses. In some embodiments, broadcasting may occur during the initial discovery phase, when the AP is negotiating and forming a CG. In some embodiments, broadcasting may occur after the CG has been established, wherein the AP 205 confirms its role and capabilities within the network.
[0037] In some embodiments, after receiving capability information from AP 205 and other APs in the CG (or potential CG), AP / WLC 210 can estimate the path of the wired connection based on the received information. In a centralized MAPC configuration, AP / WLC 210 may correspond to a leader AP or WLC (e.g., Figure 1A AP 105-1, Figure 1B WLC 120, or Figure 1C (RAP 135). AP / WLC 210 can estimate the path (1×N) from itself to each participating AP. More details on path estimation (1×N) will be provided below. Figure 3 Let's discuss this. In a decentralized MAPC configuration where there is no single leader AP, AP / WLC 210 can correspond to another participating AP in the CG (e.g., Figure 1A AP 105-2 or 105-3, Figure 1B AP 105, or Figure 1C (MAP130). AP 205, AP 210, and other participating APs in CG can estimate the path (N×N) from each AP to each other AP. More details on path estimation (N×N) will be provided below. Figures 4A-4C Let's have a discussion.
[0038] Once the path is estimated, in some embodiments, the AP / WLC 210 can calculate the transmission time for each wired connection. As used herein, the transmission time of a wired path can include the time it takes for a signal to travel between APs over a cable and the time it takes for the signal to be processed at the destination AP for multi-AP coordination.
[0039] In some embodiments, the calculation of transmission time may take into account termination-delay and hop-delay. As used herein, termination-delay may refer to the delay encountered at the end of the path, more specifically, the time taken for a MAPC message to reach the MAPC process on the destination AP (or WLC). Hop-delay, as used herein, may refer to the delay at each relay point along the wired path where a signal is transmitted from one AP to another. The termination-delay and hop-delay can be summed to determine the total transmission time of the wired path. For example, if the formed CG includes, for example, termination-delay and hop-delay, the transmission time of the wired path can be calculated as follows: Figure 1CGiven RAP 135 and MAP 130, AP / WLC 210 corresponds to RAP 135, and AP 305 corresponds to MAP 4 (130-4). In this setup, a message sent from RAP 135 to MAP 4 (130-4) needs to be relayed by MAP 1 (130-1). The transmission time for this message (e.g., transmitted via cable 140 between RAP 135 and MAP 4 (130-4)) may include a hop delay at MAP 1 (130-1) and a termination delay at MAP 4 (130-4). RAP 135 can estimate the transmission time of messages sent from itself to each MAP in the CG via wired connections.
[0040] In some embodiments, after calculating the transmission time of the wired path, the AP / WLC 210 can continue to evaluate the wireless path between APs. The AP / WLC 210 may consider metrics reflecting network conditions, such as wireless signal strength, traffic load, and interference levels, to determine the use of wireless links (e.g., Figure 1C The transmission time that may occur when transmitting MAPC messages (140) is considered. Figure 1C In one example, this might include determining the transmission time of messages sent over the air from RAP 135 to each MAP 130 in CG.
[0041] In some embodiments, the AP / WLC 210 can then evaluate the current MAPC model and various factors to select the most suitable transmission mode (or a transmission mode that provides improved performance for MAPC). These factors may include transmission time, packet loss rate, and other metrics reflecting the condition of wired and wireless paths. For example, when the CG operates in C-TDMA mode, a wired mode can be selected to ensure accurate timing and synchronized communication. However, in embodiments where wired connections cannot reach every AP (e.g., when the cable exists only in the RAP, for example, ...), Figure 1C 135) and the first-level MAP (e.g., Figure 1C When between MAP 1 (130-1), MAP 2 (130-2), or MAP 3 (130-3), the wireless mode can be selected in C-TDMA mode. Even if the desired path reaches each AP (e.g., when a cable exists in both RAP and AP), the wireless mode can be selected. Figure 1C 135) and the first-level MAP (e.g., Figure 1C Between MAP 1 (130-1), MAP 2 (130-2), or MAP 3 (130-3), and also existing between the first-level MAP and the second-level MAP (e.g., Figure 1CWhen the calculation results reveal a location between MAP 4 (130-4), MAP 5 (130-5), or MAP 6 (130-6), if the calculation results reveal a location at a relay point (e.g., Figure 1C There is a significant hop delay at MAP 1 (130-1), yet wireless mode can still be selected. This is because the significant hop delay may cause RAP (e.g., Figure 1C (135) and the second-level MAP (requires relay at the first-level MAP) (e.g., Figure 1C The transmission time between MAP 4 (130-4) is much longer than the transmission time between RAP and the first-level MAP (e.g., MAP 2 (130-2)), making wired transmission unsuitable for C-TDMA mode (which requires high reliability and synchronization between all APs in the same CG).
[0042] Alternatively, if using C-SR mode (which prioritizes speed and flexibility over reliability), wireless mode may be preferred due to its ability to quickly adapt to changing network conditions (even if estimates show a slight increase in latency compared to a wired connection). However, if the system detects that the wireless network is experiencing congestion, high interference levels, or reduced signal strength, making wireless transmission unreliable, the system can switch to wired mode.
[0043] After determining the transmission mode (wired or wireless), as shown in the figure, AP / WLC 210 communicates the determined mode back to AP 205 (step 225). This communication instructs AP 205 to follow the determined transmission mechanism when sending and receiving MAPC coordination messages. In some embodiments, messages transmitting the selected transmission mode may be transmitted using specific management frames (e.g., beacon or probe responses).
[0044] As shown in the figure, AP 205 sends a transmission request to AP / WLC 210 using the determined transmission mode (step 230). In some embodiments, the request may include information such as AP 205 needing to use a shared channel to transmit data, as well as details about the type of data transmission (e.g., uplink or downlink data), desired timing, priority (e.g., best-effort service, voice, and video), and any other relevant parameters. Upon receiving the transmission request, AP / WLC 210 evaluates the request based on the current network conditions and the MACC mode. Then, AP / WLC 210 sends a response back to AP 205 using the determined transmission mode (step 235). In some embodiments, the response may include instructions for performing data transmission. More specifically, the response may specify timing, channel access parameters, and any specific protocols to be followed. In embodiments where the instructions from AP / WLC 210 are for downlink transmission, AP 205 may directly follow the instructions and send its downlink data to its associated STA 215 (step 240). The data can be transmitted according to the parameters set by AP / WLC 210 and aligned with the synchronization communication strategy within the CG. In an embodiment where an instruction from AP / WLC 210 is used for uplink transmission, AP 205 can forward the instruction to STA 215 (step 240). STA 215 can then follow the instruction and send its uplink data to AP 205 (step 245).
[0045] Figure 3 Wired path configuration 300 for a CG having a leader AP is depicted according to some embodiments of this disclosure. In some embodiments, the leader AP 405-1 may correspond to Figure 1A The depicted AP 105-1, Figure 1B The WLC120 depicted, or Figure 1C The RAP 135 depicted.
[0046] Figure 3The diagram depicts six access points (APs): AP 305-1, AP 305-2, AP 305-3, AP 305-4, AP 305-5, and AP 305-6. AP 305-1 is directly connected to APs 305-2, AP 305-3, and AP 305-4 via wired cables (e.g., Ethernet cables). Additionally, AP 305-2 is wired to AP 305-5, and AP 305-4 is wired to AP 305-6. Since AP 305-1 acts as the leader AP, a total of (1×N) wired paths can be estimated for exchanging MAPC messages (e.g., discovery, negotiation, or coordination messages), where "1" represents the leader AP and "N" represents the number of participating APs. As shown in the figure, when AP 305-1, AP 305-3, AP 305-5, and AP 305-6 form (or intend to form) a CG, three wired paths can be considered: Path 1 (310) connecting the leader AP 305-1 to AP 305-5 via AP 305-2, Path 2 (315) directly connecting the leader AP 305-1 to AP 305-3, and Path 3 (320) connecting AP 305-1 to AP 305-6 via AP 305-4. Each AP can broadcast its ability to act as a transmission node and its role to the leader AP 305-1. For example, AP 305-5 can indicate that it is an endpoint node in the network topology, while AP 305-2 can indicate its role as a relay node (forwarding messages between the leader AP 305-1 and AP 305-5).
[0047] In some embodiments, the transmission time for each wired path within the CG can be calculated by considering both the termination delay and the hop delay on the path. For path 1 (310), the transmission time may include calculating the termination delay at AP 305-5 (or AP 305-1) and the hop delay at AP 305-2 (where the signal is at a relay). For path 2 (315), the transmission time may include only the termination delay at AP 305-3 (or AP 305-1) because there is no intermediate relay point (e.g., no hop delay). For path 3, the transmission time may include calculating the termination delay at AP 305-6 (or AP 305-1) and the hop delay at AP 305-4.
[0048] Then, considering the MAPC mode in use, the transmission time of the wired paths can be used to determine the appropriate transmission mode within the CG. For example, when using C-TDMA mode in a CG consisting of AP 305-1, AP 305-3, AP 305-5, and AP 305-6, the wired transmission mode can be chosen because the wired paths (including paths 1, 2, and 3) can reach each participating AP, and wired communication offers high reliability and low latency. However, if calculations reveal significant hop delays, making the transmission times of paths 1 and 3 much longer than that of path 2, the choice may shift to the wireless mode. This difference indicates that a message may arrive at AP 305-3 earlier than it arrives at AP 305-5 or AP 305-6. In this configuration, the wired mode may not be chosen because C-TDMA mode requires synchronous communication across the CG.
[0049] In embodiments using the C-SR mode, the wireless transmission mode may be preferred due to its flexibility and speed. However, if calculations reveal that the transmission time of the wired path (including paths 1, 2, and 3) is significantly shorter than that of the wireless transmission (possibly due to wireless congestion, low signal strength, or high interference levels), the choice may shift to the wired mode to ensure that communication within the CG remains efficient and reliable.
[0050] Figures 4A-4C A wired path configuration 400 for decentralized CG is shown according to some embodiments of the present disclosure. Figures 4A-4C Network settings and Figure 3 Similar to the previous example, it has APs 405-1, 405-2, 405-3, 405-4, 405-5, and 405-6 connected via wired connections. The only difference is that AP 405-1 no longer acts as the leader AP. Instead, the network operates under decentralized MAPC. In a decentralized setup, each AP sends MAPC messages to other APs in the same CG. The total number of paths in use can be represented by N×N, where N represents the total number of APs in the CG minus 1. As shown in the figure, when the CG includes APs 405-1, 405-3, 405-5, and 405-6, the total number of wired paths used for MAPC can include a total of nine paths.
[0051] In a decentralized setup, each AP participates in the path estimation and transmission time calculation process. As shown in the diagram, each AP can broadcast its ability to act as a transmission node and its role or location in the network. For example, AP 405-5 can indicate that it is an endpoint node in the network, while AP 405-2 can indicate its role as a relay node (forwarding messages between the leader AP 405-1 and AP 405-5). When a CG is formed or may be formed (not yet fully established) between AP 405-1, AP 405-3, AP 405-5, and AP 405-6, AP 405-1 can estimate the path estimation and transmission time calculation process. Figure 4A The following three paths are depicted: Path 1 (410) connecting AP 405-1 to AP 405-5 via AP 405-2, Path 2 (415) directly connecting AP 405-1 to AP 405-3, and Path 3 (420) connecting AP 405-1 to AP 405-6 via AP 405-4. The transmission time of Path 1 (410) may include the termination delay at AP 405-5 (or AP 405-1) and the hop delay at AP 405-2. The transmission time of Path 2 (415) may include the termination delay at AP 405-3 (or AP 405-1) and has no hop delay. The transmission time of Path 3 (420) may include the termination delay at AP 405-6 (or AP 405-1) and the hop delay at AP 405-4.
[0052] Within CG, AP 405-5 can be estimated as follows: Figure 4B The following three paths are depicted: path 4 (425) connecting AP405-5 to AP405-1 via AP 405-2; path 5 (430) connecting AP405-5 to AP405-3 via AP 405-2 and AP 405-1; and path 6 (435) connecting AP405-5 to AP405-6 via AP 405-2, AP 405-1, and AP 405-4. The transmission time of path 4 (425) may be the same as that of path 1 (410), including the termination delay at AP 405-5 (or AP405-1) and the hop delay at AP 405-2. The transmission time of path 5 (430) may include the termination delay at AP 405-5 (or AP 405-3) and the hop delay at AP 405-2 and AP 405-1. The transmission time of path 6 (435) may include the termination delay at AP 405-5 (or AP 405-6) and the hop delay at AP 405-2, AP 405-1 and AP 405-4.
[0053] Within CG, AP 405-6 can be estimated as follows: Figure 4CThe following three paths are depicted: path 7 (440) connecting AP405-6 to AP405-1 via AP 405-4; path 8 (445) connecting AP405-6 to AP405-3 via AP 405-4 and AP 405-1; and path 9 (450) connecting AP405-6 to AP405-5 via AP 405-4, AP 405-1, and AP 405-2. The transmission time of path 7 (440) may include the termination delay at AP 405-6 (or AP 405-1) and the hop delay at AP 405-4. The transmission time of path 8 (445) may include the termination delay at AP 405-6 (or AP 405-3) and the hop delay at AP 405-4 and AP 405-1. The transmission time of path 9 (450) can be the same as that of path 6 (435), including the termination delay at AP 405-6 (or AP 405-5) and the hop delay at AP 405-4, AP 405-1 and AP 405-2.
[0054] In some embodiments, the total number of paths can be represented by N×N×P, where "P" represents additional factors that may need to be considered in more complex network topologies, such as redundancy or failover paths. For simplicity, CG operation can be limited to the L2 broadcast domain (whether wired LAN or Wi-Fi), and in this embodiment, N×N×P can be simplified to N×1×2. This simplification assumes that the broadcast domain (BCAST) represents any link, which may not be strictly accurate for Virtual LANs (VLANs), where the broadcast domain may be segmented and not all links are universally accessible.
[0055] In a decentralized MAPC setup, each AP in the CG (e.g., AP 405-1, AP 405-3, AP 405-5, and AP 405-6) can actively participate in path estimation and calculate the corresponding transmission time for each path. Following these calculations, in some embodiments, each AP can report its transmission time to an AP designated for transmission mode selection. The designated AP can aggregate the calculated times from all APs in the CG, evaluate the relevant transmission times of the wireless paths, and check the MAPC mode being used. Based on these factors, the designated AP can then determine the most suitable transmission mode (or a transmission mode that provides improved performance) for the CG for multi-AP coordination.
[0056] exist Figures 4A-4CIn the depicted network, wired connections reach each AP in the CG (including AP 405-1, AP 405-3, AP 405-5, and AP 405-6), which may be preferred when the CG operates in C-TDMA mode. However, as mentioned above, if hop delays are significant, making the transmission time of some paths (e.g., path 2 (415)) much shorter than that of other paths (e.g., paths 1, 3, and 4-9), the system may switch to wireless mode. When using C-SR mode, wireless mode may be chosen for its speed and flexibility, but if calculations reveal that wired paths offer much faster transmission than wireless paths (e.g., possibly due to congestion or interference in the wireless network), the system may switch to wired mode to maintain efficient coordination within the CG.
[0057] In some embodiments, a software-defined networking (SDN) based controller (e.g., CatalystCenter) can be established. The SDN-based controller can operate at the IP layer, enabling it to centralize the selection of transport modes across the entire network (including multiple CGs). In some embodiments, the SDN-based controller can collect transport capability data from all APs across the network. For example, in the depicted network setup, assuming CG 1 is configured to include APs 405-1, 405-3, 405-5, and 405-6, and CG 2 is configured to include APs 405-2 and 405-4, the controller can perform calculations for all paths within each CG (whether 1×N or N×N) and determine the most suitable transport mode (or the transport mode that provides improved performance) for each CG. In some embodiments, each AP can perform its own path estimation and transport time calculations and then report these results to the SDN-based controller. The controller can aggregate the data and determine the transport mode for each CG.
[0058] like Figure 3 and Figures 4A-4C The depicted network setup (which includes six APs wired to each other and forming a CG between AP405-1, AP 405-3, AP 405-5, and AP 405-6) is provided for conceptual clarity. In some embodiments, any number of APs may be present within the network, and the APs may be connected via wired connections, wireless connections, or a combination of both.
[0059] Figure 5 An example method 500 for a leading AP to determine the transmission mode of a CG, according to some embodiments of the present disclosure, is described. In some embodiments, the leading AP may correspond to... Figure 1C AP 105-1, Figure 1C RAP 135 Figure 2 AP / WLC210, or Figure 3 AP 305-1. In some embodiments, example method 500 can be provided by WLC (e.g., Figure 1B The WLC120 described is being executed.
[0060] At box 505, the leader AP (or WLC), after being elected as the leader, initializes its settings within the CG. In some embodiments, initialization may include establishing the required configuration and defining its responsibility for coordinating communication between APs in the CG.
[0061] At box 510, the leader AP (or WLC) receives capability information from the other APs in the CG. In some embodiments, the capability information may include details such as each AP's ability to act as a transmission port in a wired connection and its role or location within the network (e.g., relay or endpoint). In some embodiments, the capability information may be transmitted via beacon or probe response frames. By processing the received information, the leader AP (or WLC) can develop a comprehensive understanding of the network topology, the capabilities of each AP, and its potential role in MAPC communications. This information can later be used to estimate wired paths, calculate transmission times (or delays), and select appropriate transmission modes for the CG.
[0062] At box 515, the leader AP (or WLC) verifies that each AP in the CG has provided the required data, such as its transmission capabilities, role, and other performance metrics. If capability information has been received from all other APs in the CG, method 500 proceeds to box 520. If some APs have not yet sent their capability information, method 500 returns to box 510, and the leader AP (or WLC) can wait for the remaining data to arrive. In some embodiments, the leader AP (or WLC) may send additional requests to APs to collect their capability data.
[0063] At box 520, the leader AP (or WLC) discovers wired paths and calculates or estimates the transmission time (or delay) for each path. In some embodiments, the leader AP (or WLC) may use protocols such as Internet Control Message Protocol (e.g., traceroute) or Address Resolution Protocol to identify available wired routes. Since the CG has a leader AP (or WLC) configured to coordinate data transmission, it is only necessary to estimate the path from the leader AP (or WLC) to each participating AP (also referred to as peer AP in some embodiments), resulting in a total of 1×N wired paths (where "1" represents the leader AP and "N" represents the number of participating APs in the CG). When identifying wired paths, the leader AP (or WLC) calculates the transmission time (or delay) for each path based on considerations such as hop delay and termination delay. As used herein, the transmission time (or delay) of a wired path may include the time it takes for a signal to travel between APs over a cable and the time it takes for the signal to be processed at the endpoints for multi-AP coordination. These transmission times can then be used to evaluate the suitability of the wired paths for MAPC communication and coordination within the CG.
[0064] At box 525, the leader AP (or WLC) evaluates the wireless paths between itself and other APs in the CG. In some embodiments, the speed and reliability of wireless transmissions may be affected by metrics such as signal strength, traffic load, or interference levels from other devices. By taking these factors into account, the leader AP (or WLC) calculates the total transmission time (or delay) for each wireless path. As used herein, the transmission time (or delay) of a wireless path can refer to the time it takes for a signal to travel through the air between APs and the time it takes for the signal to be processed at the endpoints for multi-AP coordination.
[0065] At box 530, the lead AP (or WLC) assesses the MAPC mode (e.g., C-TDMA, C-SR, or other modes) being used by the CG and determines the corresponding requirements for speed, synchronization, and / or reliability.
[0066] At box 535, the leader AP (or WLC) selects the appropriate transmission mode (wired or wireless) for multi-AP coordination. In some embodiments, the leader AP (or WLC) can compare the transmission times of the wired and wireless paths. If the wired path offers lower transmission time, lower packet loss rate, and higher reliability, the wired transmission mode can be selected. Furthermore, the specific MAPC mode being used may also influence the choice of transmission mode. For example, when using C-TDMA mode (which requires low latency, low packet loss, and high reliability), a wired path may be preferred to maintain accurate timing and synchronization. If the CG is operating in C-SR mode (which prioritizes speed and flexibility over reliability), a wireless path can be selected even if the transmission time is slightly longer than that of the wired path. Additionally, the leader AP (or WLC) can adjust the transmission mode based on real-time changes in network conditions. For example, if a wireless transmission mode was initially selected for a CG operating in C-SR mode, but the leader AP (or WLC) detects a significant increase in network congestion and interference (e.g., increased packet loss rate) or a decrease in signal strength, the leader AP (or WLC) can switch to a wired connection to maintain stable and efficient MAPC communication.
[0067] At box 540, the lead AP (or WLC) communicates the selected transmission mode to all participating APs in the CG. In some embodiments, the selected transmission mode can be sent via a beacon or probe response frame.
[0068] At box 545, the leader AP (or WLC) performs centralized multi-AP coordination using the selected transmission mode. If a wired mode is selected, the leader AP (or WLC) can send and receive MAPC messages via a wired cable. Messages may include data transmission requests received from participating APs (e.g., Figure 2 230) and instructions sent to the AP for timing synchronization and data transmission (e.g., Figure 2 (235). If wireless mode is selected, the leader AP (or WLC) can use a wireless connection (e.g., a Wi-Fi link) to coordinate MAPC communication. The leader AP (or WLC) can broadcast and receive MAPC messages over the air.
[0069] Figure 6 An example method 600 for a participating AP to estimate path and transmission time for transmission mode selection, according to some embodiments of the present disclosure, is described. In some embodiments, the participating AP may correspond to... Figure 1A AP 105-2 or 105-3, Figure 1B AP 105, Figure 1C MAP 130, Figure 2 AP 205, Figure 3AP 305-2, 305-3, 305-4, 305-5 or 305-6, or AP 405 of Figure 4.
[0070] At box 605, the participating AP (also referred to as the peer AP in some embodiments) initializes its settings and prepares to communicate with other APs in the CG.
[0071] As used in this article, the participating AP in a centralized MAPC configuration refers to the dependent leader AP or WLC (e.g., Figure 1A 105-1 or Figure 1B The participating APs (APs) coordinate the use of a shared channel for data transmission. Participating APs can send requests to the leading AP (or WLC) indicating their need for coordination, and the leading AP (or WLC) can respond with instructions regarding timing synchronization and data transmission. As used herein, a participating AP in a decentralized MAPC setup refers to any AP in the CG. Participating APs communicate directly with other APs in the CG for coordination and data transmission, without relying on a centralized leading AP (or WLC).
[0072] At box 610, the participating AP broadcasts its transmission capability information to other APs in the CG, including its ability to act as a transmission node via a wired connection and its role in the network (e.g., relay or endpoint).
[0073] At box 615, the participating AP listens and receives transmission capability information from other APs in the same CG.
[0074] At box 620, the participating AP checks whether it has received capability information from all other APs in the CG. If any data is missing, method 600 returns to box 615, where the participating AP can wait for the remaining data or send an additional request to ensure that complete information has been collected.
[0075] At box 625, participating APs estimate the wired paths between themselves and every other AP in the CG. In some embodiments, participating APs may use protocols such as ICMP (e.g., traceroute) or ARP to identify available wired routes. In a decentralized configuration, each participating AP can communicate directly with every other AP in the CG for data transfer. Therefore, for each participating AP, the path from that AP to every other AP can be estimated, resulting in a total of 1×N wired paths (where "1" represents a participating AP and "N" represents the number of APs in the CG minus 1). Each participating AP can then report the estimated paths to the coordinator, resulting in a total of N×N wired paths estimated for the entire CG.
[0076] Once the path is determined, the participating APs calculate or estimate the transmission time (or delay) for each wired path based on factors such as hop delay and termination delay.
[0077] At box 635, participating APs evaluate the wireless path by measuring transmission time, taking into account factors such as signal strength, traffic load, and interference levels.
[0078] At box 640, the participating AP reports the estimated transmission times for both the wired and wireless paths to the coordinator. The coordinator can be a central AP or WLC in a centralized MAPC configuration (e.g., ...). Figure 1A 105-1 or Figure 1B (120). In a decentralized MAPC configuration, the coordinator can be any AP specified in the CG for transport mode selection (e.g., Figure 4A (405-5) or network devices. In some embodiments, the coordinator can assess the MAPC mode (e.g., C-TDMA or C-SR) being used within the CG and analyze the reported transmission times. Based on this assessment, the coordinator can determine the appropriate transmission mode (wired or wireless) for the CG.
[0079] At box 645, the participating AP receives the selected transmission mode (wired or wireless) from the coordinator.
[0080] At box 650, the participating AP sends and / or receives MAPC messages using the selected transmission mode.
[0081] In some embodiments, the operations at blocks 615-640 can be performed entirely by the coordinator. In such a configuration, participating APs can simply broadcast their capability information to the coordinator, which then performs N×N wired path estimation, transmission time calculation, and / or wireless link speed and quality assessment.
[0082] In some embodiments, the coordinator can be an SDN-based controller that collects metrics across the entire network, including multiple CGs. The SDN-based controller can operate at the IP layer and is configured to determine the transmission pattern for each CG within the network.
[0083] Figure 7 This is a flowchart depicting an example method 700 for selecting a transport mode based on a MAPC deployment mode, according to some embodiments of the present disclosure.
[0084] At box 705, network devices (e.g., Figure 2 The AP / WLC 210 receives information from one or more other network devices within the Coordination Group (CG), such as... Figure 2(as depicted in step 220), wherein the CG is configured to operate using the Multi-AP Coordination Protocol (MAPC) mode, and the information indicates for each of one or more other network devices support for acting as a transmission node on a wired connection and the MAPC transmission role within the CG.
[0085] At box 710, the network device estimates the wired path between itself and at least one of one or more other network devices in the CG based on the received information (e.g., Figure 3 Paths 1-3).
[0086] At box 715, the network device determines the transmission time required to communicate via at least one wired path.
[0087] At box 720, the network device determines the transmission time required to communicate via at least one wireless path between the network device and at least one of one or more other network devices in the CG.
[0088] At box 725, the network device selects a transmission mode for at least one of one or more other network devices in the CG based on at least one of the following: transmission time for a wired path, transmission time for a wireless path, and MAPC mode.
[0089] At box 730, the network device communicates the transmission mode to at least one of one or more other network devices in the CG (such as...). Figure 2 (as depicted in step 225).
[0090] At box 735, the network device uses this transport mode to perform network coordination operations with one or more other network devices in the CG (such as...). Figure 2 (as depicted in steps 230-235).
[0091] In some embodiments, the network device may broadcast information to at least one of one or more other network devices in the CG, indicating support for acting as a transmission node on a wired connection and the network device's MAPC transmission role within the CG.
[0092] In some embodiments, the network device may include a leader access point (AP) in the CG (e.g., Figure 2 AP / WWLC 210, Figure 3 AP 305-1). In some embodiments, the network device may include a wireless local area network (LAN) controller (WLC) (e.g., AP 305-1). Figure 1B WLC 120, Figure 2 AP / WLC 210).
[0093] In some embodiments, the network device may include participating access points (APs) in the CG (e.g., Figure 2 AP205), and the selection of transmission mode also considers at least one of the following: the transmission time of the wired path between each of one or more other network devices in the CG (e.g., ... Figures 4A-4C The transmission time of the wireless path between each of paths 1-9, or one or more other network devices in the CG.
[0094] In some embodiments, the network device may transmit the transmission time of the wired path to a central controller (which collects transmission times from one or more other CGs in the network) and receive a second transmission mode for the CG determined by the central controller.
[0095] In some embodiments, the MAPC transport role may include one of the relays or endpoints within the CG.
[0096] In some embodiments, broadcasting information is performed using over-the-air (OTA) transmission, and the information may be transmitted in a frame that includes at least one of a beacon or a probe response.
[0097] In some embodiments, the transmission time for communication via at least one wired path is determined based on the termination delay associated with the termination node and the hop delay associated with one or more relay nodes.
[0098] In some embodiments, the selection of the transmission mode may also take into account at least one of packet loss in the wired path and packet loss in the wireless path.
[0099] Figure 8 An example network device 800 configured to perform various aspects of this disclosure is depicted. In some embodiments, the example network device 800 may correspond to a leader AP, such as... Figure 1A The depicted AP105-1, Figure 1C The RAP 135 described Figure 2 The AP / WLC 210 depicted, or Figure 3 The AP 305-1 is depicted. In some embodiments, the example network device 800 may correspond to a WLC, such as... Figure 1B The WLC 120 depicted, or Figure 2 The depicted AP / WLC 210. In some embodiments, the example network device 800 may correspond to a participating AP, such as... Figure 1A The depicted AP105-2 or 105-3, Figure 1B The AP 105 depicted Figure 1C The depicted MAP 130, Figure 2 The AP 205 depicted Figure 3 The AP 305-2, 305-3, 305-4, 305-5 or 305-6 described, or Figures 4A-4C The AP 405 is depicted.
[0100] As shown in the figure, the example network device 800 includes a processor 805, a memory 810, a storage device 815, one or more transceivers 820, one or more I / O interfaces 880, and one or more network interfaces 825. In some embodiments, an I / O device 840 is connected via one or more I / O interfaces 880. Furthermore, via the network interface 825, the network device 800 can be communicatively coupled to one or more other devices and components (e.g., via a network, which may include the Internet, one or more local area networks, etc.). Each component is communicatively coupled via one or more buses 830. In some embodiments, one or more antennas 835 may be coupled to the transceiver 820 for transmitting and receiving wireless signals.
[0101] Processor 805 typically represents a single central processing unit (CPU) and / or graphics processing unit (GPU), multiple CPUs and / or GPUs, a microcontroller, an application-specific integrated circuit (ASIC), or a programmable logic device (PLD). Processor 805 processes information received via transceiver 820, I / O interface 880, and network interface 825. Processor 805 retrieves and executes programming instructions stored in memory 810, and stores and retrieves application data residing in storage device 815.
[0102] Storage device 815 can be any combination of disk drives, flash-based storage devices, etc., and can include fixed and / or removable storage devices, such as fixed disk drives, removable memory cards, caches, optical storage, network-attached storage (NAS), or storage area networks (SAN). Storage device 815 can store various types of data for the efficient operation of the system.
[0103] Memory 810 may include random access memory (RAM) and read-only memory (ROM). Memory 810 may store processor-executable software code containing instructions that, when executed by processor 805, cause network device 800 to perform the various functions for wireless communication described herein. In the example shown, memory 810 includes four software components: a transmission information management component 845, a path estimation component 850, a transmission mode selection component 855, and a coordination control component 860.
[0104] In one embodiment, the transmission information management component 845 can broadcast the transmission capabilities (e.g., wired support) and transmission roles (e.g., relay or endpoint) of the device 800 to other APs or WLCs, and receive transmission information from other APs. In some embodiments, the transmission information management component 845 can be part of a messaging and communication component that uses specific frames (e.g., beacons, probe responses, or custom MAPC frames) to handle network discovery and coordination communications.
[0105] In one embodiment, path estimation component 850 can perform path estimation and link analysis on both wired and wireless networks. Based on received transmission information, path estimation component 850 can discover wired paths between device 800 and other APs in the CG (e.g., using protocols such as ICMP or ARP). After determining the wired paths, path estimation component 850 can calculate the transmission time of these paths based on hop delay and termination delay. When wireless links are available, path estimation component 850 can measure wireless path metrics (e.g., signal strength, traffic load, and interference levels) and estimate the speed and reliability of wireless transmissions.
[0106] In one embodiment, the transmission mode selection component 855 can select an appropriate transmission mode (wired or wireless) based on estimated path performance and the MAPC mode in use. In one embodiment, the coordination control component 860 can manage multi-AP coordination, thereby interacting with other APs in the CG using the selected transmission mode.
[0107] Although depicted as discrete components for clarity of concept, in some embodiments, the operation of the depicted components (and other components not shown) can be combined or distributed across any number of components. Furthermore, although depicted as software residing in memory 810, in some aspects, the operation of the depicted components (and other components not shown) can be implemented using hardware, software, or a combination of hardware and software.
[0108] Various embodiments have been referenced in this disclosure. However, the scope of this disclosure is not limited to the specific embodiments described. Rather, any combination of the described features and elements (whether or not related to different embodiments) is contemplated to implement and practice the contemplated embodiments. Furthermore, when elements of an embodiment are described in the form of "at least one of A and B" or "at least one of A or B," it will be understood that embodiments including element A alone, including element B alone, and including elements A and B are all considered. Moreover, while some embodiments disclosed herein may achieve advantages over other possible solutions or over the prior art, whether a particular advantage is achieved by a given embodiment does not limit the scope of this disclosure. Therefore, the aspects, features, embodiments, and advantages disclosed herein are merely illustrative and should not be considered elements or limitations of the appended claims unless expressly recited in one or more claims. Similarly, references to "the invention" should not be construed as a generalization of any inventive subject matter disclosed herein and should not be considered elements or limitations of the appended claims unless expressly recited in one or more claims.
[0109] As those skilled in the art will understand, the embodiments disclosed herein can be embodied as systems, methods, or computer program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, which may generally be referred to herein as "circuit," "module," or "system." Furthermore, embodiments can take the form of computer program products embodied in one or more computer-readable media, on which computer-readable program code is embodied. In one example, a computer-readable medium is provided carrying instructions that, when executed by one or more processors, cause any of the methods described herein to be performed.
[0110] Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, RF, or any suitable combination thereof.
[0111] Computer program code used to perform the operations of embodiments of this disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages (such as Java, Smalltalk, C++, etc.) and conventional procedural programming languages (such as the "C" programming language or similar programming languages). The program code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)) or may be connected to an external computer (e.g., via the Internet through an Internet service provider).
[0112] This document describes aspects of the disclosure with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments presented in this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.
[0113] These computer program instructions may also be stored in a computer-readable medium that can instruct a computer, other programmable data processing apparatus or other device to operate in a particular manner, such that the instructions stored in the computer-readable medium produce an article of writing including the instructions, which implement the functions / actions specified in one or more blocks of a flowchart and / or block diagram.
[0114] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device, thereby producing a computer-implemented process, such that the instructions, which execute on the computer, other programmable data processing apparatus, or other device, provide a process for implementing the functions / actions specified in one or more boxes of a flowchart and / or block diagram.
[0115] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments. In this regard, each box in a flowchart or block diagram may represent a module, segment, or portion of code, including one or more executable instructions for implementing one or more specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the boxes may occur in a different order than indicated in the drawings. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved. It will also be noted that each box in the block diagrams and / or flowcharts, and combinations of boxes in the block diagrams and / or flowcharts, may be implemented by a system based on dedicated hardware, or a combination of dedicated hardware and computer instructions, that performs the specified functions or actions.
[0116] In view of the foregoing, the scope of this disclosure is defined by the appended claims.
Claims
1. A method comprising: A network device receives information from one or more other network devices within a coordination group (CG), wherein the CG is configured to operate using a multi-AP coordination protocol (MAPC) mode, and wherein the information indicates, for each of the one or more other network devices, support for acting as a transmission node on a wired connection and a MAPC transmission role within the CG. The network device estimates the wired path between itself and at least one of the other network devices in the CG based on the received information. The network device determines the transmission time required to communicate via at least one of the wired paths; The network device determines the transmission time required to communicate via at least one wireless path between the network device and at least one of the one or more other network devices in the CG; The network device selects a transmission mode for at least one of the one or more other network devices in the CG based on the transmission time of the wired path, the transmission time of the wireless path, and at least one of the MAPC modes. The network device communicates the transmission mode to at least one of the other network devices in the CG; as well as The network device uses the transmission mode to perform network coordination operations with one or more other network devices in the CG.
2. The method according to claim 1, further comprising: The network device broadcasts information to at least one of the other network devices in the CG, indicating support for acting as a transmission node on a wired connection and the network device's MAPC transmission role within the CG.
3. The method according to claim 2, wherein, The broadcast of the information is performed using over-the-air (OTA) transmission, and the information is transmitted in frames that include at least one of a beacon or a probe response.
4. The method according to any one of the preceding claims, wherein, The network device includes the leader access point (AP) in the CG.
5. The method according to any one of the preceding claims, wherein, The network device includes participating access points (APs) in the CG, and the selection of the transmission mode also considers at least one of the following: the transmission time of the wired path between each of the one or more other network devices in the CG, or the transmission time of the wireless path between each of the one or more other network devices in the CG.
6. The method according to any one of the preceding claims, wherein, The network device includes a wireless local area network (LAN) controller (WLC).
7. The method according to any one of the preceding claims further comprises: The network device transmits the transmission time of the wired path to the central controller, wherein the central controller collects the transmission time from one or more other CGs in the network; as well as The network device receives the second transmission mode for the CG determined by the central controller.
8. The method according to any one of the preceding claims, wherein, The MAPC transmission role includes one of the relays or endpoints within the CG.
9. The method according to any one of the preceding claims, wherein, The transmission time for communication via at least one of the wired paths is determined based on the termination delay associated with the termination node and the hop delay associated with one or more relay nodes.
10. The method according to any one of the preceding claims, wherein, The selection of the transmission mode also takes into account at least one of packet loss in the wired path and packet loss in the wireless path.
11. A system for network devices in a wireless network, comprising: One or more memories that collectively contain one or more programs; One or more processors, wherein the one or more processors are individually or jointly configured to perform operations including: A network device receives information from one or more other network devices within a coordination group (CG), wherein the CG is configured to operate using a multi-AP coordination protocol (MAPC) mode, and wherein the information indicates, for each of the one or more other network devices, support for acting as a transport node on a wired connection and a MAPC transport role within the CG. The network device estimates the wired path between itself and at least one of the other network devices in the CG based on the received information. The network device determines the transmission time required to communicate via at least one of the wired paths; The network device determines the transmission time required to communicate via at least one wireless path between the network device and at least one of the one or more other network devices in the CG; The network device selects a transmission mode for at least one of the one or more other network devices in the CG based on the transmission time of the wired path, the transmission time of the wireless path, and at least one of the MAPC modes. The network device communicates the transmission mode to at least one of the one or more other network devices in the CG; and The network device uses the transmission mode to perform network coordination operations with one or more other network devices in the CG.
12. The system according to claim 11, wherein, The operation further includes: the network device broadcasting information to at least one of the one or more other network devices in the CG, the information indicating support for acting as a transmission node on a wired connection and the network device's MAPC transmission role within the CG.
13. The system according to claim 12, wherein, The broadcast of the information is performed using over-the-air (OTA) transmission, and the information is transmitted in frames that include at least one of a beacon or a probe response.
14. The system according to any one of claims 11 to 13, wherein, The network device includes participating access points (APs) in the CG, and the selection of the transmission mode also considers at least one of the following: the transmission time of the wired path between each of the one or more other network devices in the CG, and the transmission time of the wireless path between each of the one or more other network devices in the CG.
15. The system according to any one of claims 11 to 14, wherein, The network device includes a wireless local area network (LAN) controller (WLC).
16. The system according to any one of claims 11 to 15, wherein, The operation also includes: The network device transmits the transmission time of the wired path to a central controller, wherein the central controller collects the transmission time from one or more other CGs in the network; and The network device receives the second transmission mode for the CG determined by the central controller.
17. The system according to any one of claims 11 to 16, wherein, The MAPC transmission role includes one of the relays or endpoints within the CG.
18. The system according to any one of claims 11 to 17, wherein, The transmission time for communication via at least one of the wired paths is determined based on the termination delay associated with the termination node and the hop delay associated with one or more relay nodes.
19. The system according to any one of claims 11 to 18, wherein, The selection of the transmission mode also takes into account at least one of packet loss in the wired path and packet loss in the wireless path.
20. The system according to any one of claims 11 to 19, wherein, The network device includes the leader access point (AP) in the CG.
21. One or more non-transitory computer-readable media containing computer program code in any combination, which, when executed by a computer system, performs operations including: A network device receives information from one or more other network devices within a coordination group (CG), wherein the CG is configured to operate using a multi-AP coordination protocol (MAPC) mode, and wherein the information indicates, for each of the one or more other network devices, support for acting as a transport node on a wired connection and a MAPC transport role within the CG. The network device estimates the wired path between itself and at least one of the other network devices in the CG based on the received information. The network device determines the transmission time required to communicate via at least one of the wired paths; The network device determines the transmission time required to communicate via at least one wireless path between the network device and at least one of the one or more other network devices in the CG; The network device selects a transmission mode for at least one of the one or more other network devices in the CG based on the transmission time of the wired path, the transmission time of the wireless path, and at least one of the MAPC modes. The network device communicates the transmission mode to at least one of the other network devices in the CG; as well as The network device uses the transmission mode to perform network coordination operations with one or more other network devices in the CG.
22. One or more non-transitory computer-readable media according to claim 21, wherein, The operation includes the method according to any one of claims 2 to 10.
23. An apparatus and / or system arranged to perform the method according to any one of claims 1 to 10.