Ultra-wide bandwidth transmission mechanism in wireless communication

Abstract

Techniques related to ultra-wide-bandwidth (UWB) transmission mechanisms in wireless communications are described. A device (e.g., an access point (AP)) establishes a basic service set (BSS) on a primary link and a secondary link. The device then performs an aggregated bandwidth operation with one or more stations (STAs). The aggregated bandwidth of the primary link and the secondary link depends on the channel availability of each of the primary link and the secondary link.

Description

[0001] Cross-referencing

[0002] This specification is a non-provisional patent application that claims priority to U.S. Provisional Patent Application No. 63 / 598,165, filed on November 13, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to wireless communications, and more specifically, to ultra-wide-bandwidth (UWB) transmission mechanisms in wireless communications. Background Technology

[0004] Unless otherwise stated, the methods described in this section are not prior art as claimed in the following claims, and are not considered prior art because they are included in this section.

[0005] In wireless communications, such as Wi-Fi (or WiFi) and Wireless Local Area Networks (WLANs) under the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the current maximum channel bandwidth is 320 MHz (e.g., maximum 320 MHz) due to channel allocation limitations. In multi-link operation schemes, multi-link devices (MLDs) with multiple radio frequencies allow simultaneous transmit and receive (STR) on multiple links to aggregate the total effective bandwidth. However, multi-link operation schemes require sufficiently large frequency spacing between the multiple links used for transmit and receive to avoid in-device interference (IDC). Otherwise, due to IDC, multi-link devices may only be able to operate on multiple links in non-simultaneous transmission and reception (NSTR) mode. In this case, effective bandwidth cannot be aggregated under the NSTR scheme. On the other hand, single-radio devices can also operate on multiple links, although they can only operate on one link at any given time. Therefore, bandwidth is limited by the bandwidth of the single link used for transmission and reception, as there is no aggregated bandwidth from two or more links. However, some devices may possess higher radio frequency (RF) capabilities and wider bandwidths than 320MHz. Therefore, achieving effective wider bandwidth within a single link for devices with RF capabilities of 340MHz, 360MHz, 400MHz, or 480MHz or greater remains a challenge. Thus, there is an urgent need for a solution that provides an ultra-wideband (UWB) transmission mechanism for wireless communication. Summary of the Invention

[0006] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the following abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some embodiments will be further elaborated in the detailed description below. Therefore, the following abstract is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0007] One objective of this disclosure is to provide schemes, concepts, designs, techniques, methods, and apparatus related to ultra-wideband (UWB) transmission mechanisms in wireless communications. It is believed that implementing one or more of the schemes proposed herein can solve or mitigate the aforementioned problems.

[0008] In one aspect, a method may involve an access point (AP) establishing a basic service set (BSS) on a primary link and a secondary link. The method may also involve the AP performing aggregated bandwidth operations with one or more workstations (STAs), wherein the aggregated bandwidth of the primary link and the secondary link depends on the channel availability of the primary link and the secondary link. The primary link and the secondary link may use a single radio frequency (RF) or multiple RF frequencies respectively, depending on the AP's radio frequency (RF) capabilities.

[0009] In another aspect, a method may involve a non-AP STA receiving a beacon frame or management frame indicating the AP's aggregated bandwidth capability. The method may also involve the non-AP STA performing aggregated bandwidth operations with the AP involving a primary link and a secondary link, wherein the aggregated bandwidth of the primary and secondary links depends on the channel availability of the primary and secondary links. The primary and secondary links may use a single radio frequency or multiple radio frequencies respectively, depending on the AP's radio frequency (RF) capabilities.

[0010] It is worth noting that although the content described herein may be presented in the context of certain wireless access technologies, networks, and network topologies (such as Wi-Fi / WiFi), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, used, and realized in other types of wireless access technologies, networks, and network topologies, such as, but not limited to, Bluetooth, ZigBee, 5G / New Radio (NR), Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Industrial IoT (IIoT), and Narrowband IoT (NB-IoT). Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0011] The accompanying drawings are included in this disclosure to provide a further understanding of the disclosure and form part of it. The drawings illustrate embodiments of the disclosure and, together with the description, serve to explain the principles of the disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0012] Figure 1 This is a schematic diagram of an example network environment in which various solutions and schemes related to this disclosure can be implemented.

[0013] Figure 2 This is a schematic diagram of an example design based on the scheme proposed in this disclosure.

[0014] Figure 3 This is a schematic diagram of an example scenario based on the solution proposed in this disclosure.

[0015] Figure 4 This is a block diagram of an example communication system based on the scheme proposed in this disclosure.

[0016] Figure 5 Here is an example flowchart of the scheme proposed in this disclosure.

[0017] Figure 6 This is a second example flowchart under the scheme proposed in this disclosure. Detailed Implementation

[0018] This specification discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be implemented in various forms. This disclosure can be embodied in many different forms and should not be construed as being limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure exhaustive and complete, and to fully convey the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0019] Overview

[0020] According to the implementation of this disclosure, various technologies, methods, schemes, and / or solutions relate to ultra-wideband (UWB) transmission mechanisms in wireless communication. According to this disclosure, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more possible solutions can be implemented in some combination. The various solutions and schemes implement the proposed schemes between access points (APs) and non-AP workstations (STAs). Therefore, the various solutions and schemes proposed herein can solve or alleviate the aforementioned problems.

[0021] Figure 1 Example network environment 100 is shown, which can implement various solutions and schemes disclosed herein. Figures 2 to 6 Examples of implementing various proposed schemes in a network environment 100 according to this disclosure are shown. The following description of the various proposed schemes refers to... Figures 1 to 6 .

[0022] See Figure 1In part (A), network environment 100 may include at least one first working site (STA), namely STA 110, and one second STA, namely STA 120. One of STA 110 and STA 120 may be an access point (AP) STA (which may be referred to interchangeably as "AP"), and the other may be a non-AP STA (which may be referred to interchangeably as "STA") associated with that AP STA. STA 110 and STA 120 may belong to a basic service set (BSS). Although more STAs may be involved in network environment 100 under one or more of the schemes presented herein, for simplicity, Figure 1 Only two STAs (STA 110 and STA 120) are shown, and it is understood that more STAs may be involved. Each of STA 110 and STA 120 can be configured to implement the various proposed schemes described in this disclosure below. It is worth noting that although the various proposed schemes may be described separately or individually below, in actual implementation, some or all of the proposed schemes may be used or implemented in combination. Of course, each proposed scheme can also be used or implemented individually or separately.

[0023] See Figure 1 In part (B), under the various proposed schemes, the next-generation system can allow the AP to decide which aggregated bandwidth to support, such as 320+20MHz, 320+40MHz, 320+80MHz, 320+160MHz, or 320+320MHz, and use only one radio frequency. Correspondingly, APs with higher radio frequency capabilities (such as the STA 110) can aggregate two or more adjacent channels based on channelization, such as... Figure 1 As shown in section (B). For example, when the AP has a 480MHz RF capability, it can support and / or operate with an aggregated bandwidth of 320 + 80MHz (total 400MHz). Similarly, when the AP has a 640MHz RF capability, it can support and / or operate with an aggregated bandwidth of 320 + 160MHz (total 480MHz). The AP can access channels on two or more adjacent channels according to the enhanced distributed channel access (EDCA) rules, but with certain limitations. Each associated non-AP STA (such as STA 120) can only access channels on the primary channel, without needing to support bandwidth aggregation, but can support dynamic channel switching within the aggregated bandwidth.

[0024] According to the proposed scheme in this disclosure, regarding the notification of bandwidth aggregation operation, an AP with bandwidth aggregation capability (such as STA 110) can establish a Basic Service Set (BSS) on the primary link and secondary links. For example, the primary link can have a bandwidth of 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz, and the secondary link can also have a bandwidth of 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz. The total bandwidth of the primary link and secondary links can depend on the AP's radio frequency bandwidth. The primary link and secondary links can belong to the same BSS, and can be continuous channels (i.e., continuous channels in the frequency domain) or non-continuous channels on the primary link and secondary links. An AP with bandwidth aggregation capability can belong to an AP Multilink Device (MLD), and the link identifiers (IDs) of the primary link and secondary links can be the same or identical.

[0025] Under the proposed scheme, the AP can transmit one or more beacon frames and other management frames, such as probe response frames and / or associated response frames, on the primary link. The AP can carry Ultra-High Reliability (UHR) operation elements or UHR capability elements in the beacon / probe response / associated response frames on the primary link, indicating its aggregated bandwidth capability and / or aggregated bandwidth information. Furthermore, the AP may not need to transmit beacon frames or other management frames (such as probe response frames and / or associated response frames) on the secondary links.

[0026] Under the proposed scheme, each beacon frame or management frame can advertise a secondary link by setting the TBTT information field type subfield to a predefined value (e.g., 1) and the TBTT information field length subfield to another predefined value (e.g., 3) in the Target Beacon Transmission Time (TBTT) information field, using the Simplified Neighbor Report (RNR) element. This TBTT information field corresponds to the AP (which can be the reporting AP itself) reported on the secondary link. The TBTT information field corresponding to the AP reported on the secondary link can contain at least one of the following subfields: Link ID, Link Disabled, and Aggregated Bandwidth.

[0027] The Link Disable subfield indicates whether the secondary link is enabled or disabled. When the Link Disable subfield indicates "Enabled," the aggregate bandwidth can be indicated in the TBTT information field, meaning the reporting AP is operating at aggregate bandwidth. When the Link Disable subfield indicates "Disabled," the Aggregate Bandwidth subfield can be retained in the TBTT information field, meaning the reporting AP is not operating at aggregate bandwidth. Furthermore, the channel number of the secondary link can be indicated in the neighboring AP field corresponding to the reporting AP on the secondary link within the RNR element.

[0028] Figure 2An example design 200 based on the scheme proposed in this disclosure is shown. When the reporting AP belongs to an AP Multi-Link Device (MLD), the reporting AP can, as the reporting AP, advertise the primary and secondary links of neighboring APs belonging to the same AP MLD in terms of aggregate bandwidth capacity. The reporting AP can set the TBTT information field type of the primary link of the reporting AP to a predefined value (e.g., 0) and the TBTT information field type of the secondary link to another predefined value (e.g., 1) in its RNR element. The link IDs corresponding to the primary and secondary links can be set to the same value. Figure 2 The format of the TBTT information field under Design 200 is shown.

[0029] According to the proposed scheme in this disclosure, regarding discovery and association in aggregated bandwidth operation, a non-AP STA (such as STA 120) can identify an AP (such as STA 110) with aggregated bandwidth capability through the UHR operation element or the aggregated bandwidth capability indication in the UHR capability element carried in the beacon / probe response frame. Alternatively, a non-AP STA can discover the auxiliary link of an AP with aggregated bandwidth capability through the RNR element when the TBTT information field type subfield is equal to 1 and the TBTT information field length subfield is equal to 1 or 3. The channel number of the auxiliary link can be determined in the neighbor AP field corresponding to the AP reporting on the auxiliary link in the RNR element. Any non-AP STA can associate with an AP with aggregated bandwidth capability on the BSS's main link.

[0030] Under the proposed scheme, a non-access point (non-AP) workstation (STA) capable of identifying secondary links may not send any probe request frames or association request frames on the secondary link. The non-AP STA can then instruct an access point (AP) with aggregation bandwidth capability whether it can dynamically switch channels within a specific bandwidth. For example, the non-AP STA can instruct an AP with aggregation bandwidth capability to dynamically switch channels within a bandwidth of 80MHz, 160MHz, 320MHz, 340MHz, 360MHz, 400MHz, 480MHz, or 640MHz. This specific bandwidth can be less than or equal to the AP's aggregation bandwidth.

[0031] Under the proposed scheme, a non-AP STA can discover the secondary link of an AP with aggregation bandwidth capability based on the Simplified Neighbor Report (RNR) element, provided that the Target Beacon Transmission Time (TBTT) type subfield is equal to 1 and the TBTT information length subfield is equal to 1 or 3. This non-AP STA can belong to a single-link, single-radio, or multi-radio multi-link device. When the non-AP STA belongs to a single-link or single-radio multi-link device, it can identify the reporting AP with aggregation bandwidth capability by the aggregation bandwidth capability indicated in the Ultra-High Reliability (UHR) operation element or UHR capability element carried in the beacon / probe response frame. The non-AP STA can also identify the secondary link disabled status and aggregation bandwidth of the reporting AP through the RNR element.

[0032] When a non-AP STA belongs to a multi-radio multi-link device, it can also identify the reported AP with aggregation bandwidth capability through the RNR element carried in the beacon / probe response frame. This element may include another neighboring AP whose Target Beacon Transmission Time (TBTT) information field type subfield is set to a predefined value (e.g., 1), and whose TBTT information field length subfield is set to another predefined value (e.g., 1 or 3), and which has the same or other identical link identifier (ID) as the reported AP. The non-AP STA can further identify the link-disabled status of the secondary link and the aggregation bandwidth of the reported AP through the RNR element.

[0033] The channel number of the auxiliary link can be determined by the neighbor AP information field in the RNR element as the primary channel of the auxiliary link of the AP with aggregation bandwidth capability.

[0034] Figure 3 An example scenario 300 is illustrated under the scheme proposed in this disclosure. Scenario 300 may involve aggregated bandwidth transmission under the proposed scheme. See also Figure 3An AP (e.g., STA 110) can establish or set up a Basic Service Set (BSS) on channel 1 (CH1) with an 80MHz bandwidth, which can serve as the AP's primary link, and operate on channel 2 (CH2) with an 80MHz bandwidth, which can serve as the AP's secondary link. The AP can indicate its secondary link operational capabilities in its UHR capability element or UHR operation element. Furthermore, the AP can include an RNR element on CH2 to advertise its secondary link. The AP can perform EDCA backoff on the primary 20MHz channel of the primary link and perform point coordination function (PCF) interframe space (PIFS) idle detection on non-primary channels on both the primary and secondary links. The AP can acquire a transmission opportunity (TXOP) and send an initial control frame (e.g., a trigger frame) to STAs 1, 2, 3, and 4 (e.g., one of which is STA 120), instructing STAs 3 and 4 to switch to the secondary link. Accordingly, STAs 1 and 2 can respond to the initial control response frame on the primary link, and STAs 3 and 4 can switch to the secondary link and respond to the initial control response frame on the secondary link. Subsequently, the AP can send downlink (DL) physical-layer protocol data units (PPDUs) or trigger frames to STA1 and 2 via the main link to request trigger-based uplink (UL) PPDUs, and send them to STA3 and STA4 via the secondary link. Furthermore, STA3 and STA4 can switch back to the main link at the end of the TXOP.

[0035] Example Implementation

[0036] Figure 4 An example system 400 according to embodiments of this disclosure is illustrated, comprising at least one example device 410 and one example device 420. Devices 410 and 420 can perform various functions to implement the schemes, techniques, processes, and methods described herein related to ultra-wideband (UWB) transmission mechanisms in wireless communications, including the foregoing content regarding various proposed designs, concepts, schemes, systems, and methods, as well as the processes described below. For example, device 410 may be implemented in an AP STA (e.g., STA 110), and device 420 may be implemented in a non-AP STA (e.g., STA 120), or vice versa.

[0037] Devices 410 and 420 may be part of an electronic device, such as a portable or mobile device, wearable device, wireless communication device, or computing device. When implemented in a STA, devices 410 and 420 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. Devices 410 and 420 may also be part of a machine-type device, which may be an Internet of Things (IoT) device, such as a non-movable or fixed device, home appliance, wired communication device, or computing device. For example, devices 410 and 420 may be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. When implemented as a network device, devices 410 and / or 420 may be implemented in a network node, such as an access point (AP) or mesh device in a wireless local area network (WLAN).

[0038] In some implementations, devices 410 and 420 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set computing (CISC) processors. In all the above embodiments, devices 410 and 420 may be implemented in a STA or AP. Devices 410 and 420 may each contain... Figure 4 At least some components are shown, such as processor 412 and processor 422. Devices 410 and 420 may also include one or more other components unrelated to the solutions proposed in this disclosure (e.g., internal power supply, display device, and / or user interface device); therefore, for the sake of brevity, Figure 4 These components are not shown and are not described below.

[0039] In one aspect, processors 412 and 422 may be implemented as one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 412 and 422, in some embodiments processors 412 and 422 may comprise multiple processors, and in other embodiments may comprise a single processor. In another aspect, processors 412 and 422 may be implemented in hardware (and optionally firmware) comprising, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more transformers, these electronic components configured and arranged according to the specific purposes of this disclosure. In other words, in at least some embodiments, processors 412 and 422 are special-purpose machines specifically designed, arranged, and configured to perform specific tasks, including tasks related to ultra-wideband (UWB) transmission mechanisms in wireless communications.

[0040] In some embodiments, device 410 may further include a transceiver 416 coupled to processor 412. Transceiver 416 may include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. In some embodiments, device 420 may further include a transceiver 426 coupled to processor 422. Transceiver 426 may include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. It is worth noting that although transceivers 416 and 426 are shown as external and separate from processors 412 and 422, respectively, in some embodiments, transceiver 416 may be integrated into processor 412 as part of a system-on-a-chip (SoC), and transceiver 426 may also be integrated into processor 422 as part of a SoC.

[0041] In some embodiments, device 410 may further include a memory 414 coupled to and accessible by processor 412 for storing data. In some embodiments, device 420 may further include a memory 424 coupled to and accessible by processor 422 for storing data. Each of memory 414 and memory 424 may include a random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of memory 414 and memory 424 may include a read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, or otherwise, each of the memories 414 and 424 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0042] Each of devices 410 and 420 can be a communication entity capable of communicating with each other according to various proposed schemes of this disclosure. For illustrative purposes only and without limitation, the capabilities of device 410 or device 420 as a work station (STA, e.g., STA 120) or access point (AP, e.g., STA 110) are described below in conjunction with example flows 500 and 600. It is worth noting that although the capabilities, functions, and / or technical features of devices 410 and 420 are described in detail below, these also apply to the other of devices 410 and 420, although not described in detail for the sake of brevity. Furthermore, it is worth noting that although the following example implementations are described in a wireless local area network (WLAN) environment, they can also be implemented in other types of networks.

[0043] Explanatory process

[0044] Figure 5An example flow 500 according to an embodiment of this disclosure is illustrated. Flow 500 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 500 may represent one aspect of proposed concepts and schemes related to ultra-wideband (UWB) transmission mechanisms in wireless communication. Flow 500 may include one or more operations, actions, or functions as shown in flow blocks 510 and 520. Although shown as discrete flow blocks, the individual flow blocks of flow 500 may be divided into more flow blocks, merged into fewer flow blocks, or omitted according to desired implementation methods. Furthermore, the flow blocks / sub-flow blocks of flow 500 may be arranged according to... Figure 5 The process can be executed in the order shown, or in a different order. Furthermore, one or more process blocks / sub-process blocks of process 500 can be executed repeatedly or iteratively. Process 500 can be implemented by devices 410 and 420 and any variations thereof. For illustrative purposes only and without limitation, process 500 is described below in conjunction with device 410 as an AP STA (e.g., STA 110) and device 420 as a non-AP STA (e.g., STA 120) in a wireless network (such as a WLAN) within network environment 100, according to one or more of the IEEE 802.11 standards. Process 500 may begin with process block 510.

[0045] In step 510, process 500 may involve the processor 412 of device 410 acting as an AP STA (e.g., STA 110), establishing a Basic Service Set (BSS) on the primary and secondary links via transceiver 416, where the aggregate bandwidth of the primary and secondary links depends on the channel availability of each. The primary and secondary links may use a single radio frequency (RF) or separate RF frequencies depending on the AP's radio frequency (RF) capabilities. Process 500 can continue from 510 to 520.

[0046] At 520, process 500 may involve processor 412 performing aggregated bandwidth operations with one or more workstations (STAs, such as containing device 420 as STA 120) via transceiver 416.

[0047] In some implementations, the AP may belong to an AP multilink device (MLD), and the link identifier (ID) of the primary link is the same as the link ID of the secondary link.

[0048] In some implementations, when performing aggregated bandwidth operation, process 500 may involve processor 412 sending a beacon frame or management frame on the primary link rather than the secondary link to indicate the AP's aggregated bandwidth capability and aggregated bandwidth in the Ultra-High Reliability (UHR) operation element or UHR capability element carried in the beacon frame or management frame on the primary link.

[0049] In some implementations, the management frame may include a probe response frame or an association response frame.

[0050] In some implementations, a beacon frame or management frame may advertise a secondary link by setting the TBTT information field type subfield to a first predefined value (e.g., 1) and the TBTT information field length subfield to a second predefined value (e.g., 1 or 3) in the Target Beacon Transmission Time (TBTT) information field, using a Simplified Neighbor Report (RNR) element, where the TBTT information field corresponds to the AP reported on the secondary link.

[0051] In some implementations, the TBTT information field corresponds to the AP reported on the secondary link and may include at least one link identifier (ID) subfield, a link disabled subfield, and an aggregated bandwidth subfield.

[0052] In some implementations, the Link Disable subfield may indicate whether the secondary link is enabled or disabled, such that: (a) when the Link Disable subfield indicates that the secondary link is enabled, the aggregate bandwidth is indicated in the TBTT Information field to indicate that the AP is operating at aggregate bandwidth; (b) when the Link Disable subfield indicates that the secondary link is disabled, the Aggregate Bandwidth subfield is retained in the TBTT Information field to indicate that the AP is not operating at aggregate bandwidth.

[0053] In some implementations, the channel number of the secondary link can be indicated in the neighbor AP field of the RNR element corresponding to the AP reported on the secondary link.

[0054] In some implementations, when performing aggregated bandwidth operations, process 500 may involve processor 412, as a reporting AP belonging to an AP multilink device (MLD), announcing the primary and secondary links of a neighboring AP that is an aggregated bandwidth capability of the reporting AP, which belongs to the AP MLD.

[0055] In some implementations, during the notification, process 500 may involve processor 412 setting the Target Beacon Transit Time (TBTT) information field type subfield to a first predefined value (e.g., 0) and the TBTT information field length subfield to a second predefined value (e.g., 1) in the Simplified Neighbor Report (RNR) element, and notifying the main link.

[0056] In some implementations, when performing aggregated bandwidth operations with one or more STAs, process 500 may involve processor 412 performing specific operations. For example, process 500 may involve processor 412 acquiring a transmission opportunity (TXOP). Furthermore, process 500 may involve processor 412 sending control frames to a first STA and a second STA among the one or more STAs, instructing them to switch the second STA to a secondary link. Additionally, process 500 may involve processor 412 receiving a first control response frame from the first STA via the primary link and a second control response frame from the second STA via the secondary link. Furthermore, process 500 may involve processor 412 sending a downlink (DL) physical layer protocol data unit (PPDU) or trigger frame to the first STA via the primary link and to the second STA via the secondary link.

[0057] Figure 6 An example flow 600 according to an embodiment of this disclosure is illustrated. Flow 600 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 600 may represent one aspect of proposed concepts and schemes related to ultra-wideband (UWB) transmission mechanisms in wireless communication. Flow 600 may include one or more operations, actions, or functions as shown in flow blocks 610 and 620. Although shown as discrete flow blocks, the individual flow blocks of flow 600 may be divided into more flow blocks, merged into fewer flow blocks, or omitted according to desired implementation methods. Furthermore, the flow blocks / sub-flow blocks of flow 600 may be arranged according to... Figure 6 The process can be executed in the order shown, or in a different order. Furthermore, one or more process blocks / sub-process blocks of process 600 can be executed repeatedly or iteratively. Process 600 can be implemented by devices 410 and 420 and any variations thereof. For illustrative purposes only and without limitation, process 600 is described below in conjunction with device 410 as an AP STA (e.g., STA 110) and device 420 as a non-AP STA (e.g., STA 120) in a wireless network (such as a WLAN) within network environment 100, according to one or more of the IEEE 802.11 standards. Process 600 may begin with process block 610.

[0058] At 610, process 600 may involve the processor 422 of device 420, acting as a non-access point (non-AP) workstation (STA) (e.g., STA 120), receiving, via transceiver 426, beacon frames or management frames indicating the aggregated bandwidth capabilities of an access point (AP) (e.g., device 410). Process 600 may continue from 610 to 620.

[0059] At 620, process 600 may involve processor 422 performing aggregated bandwidth operations involving the primary link and the secondary link with the AP via transceiver 426, wherein the aggregated bandwidth of the primary link and the secondary link depends on the channel availability of each of the primary link and the secondary link. The primary link and the secondary link may use a single radio frequency or separate radio frequencies depending on the radio frequency (RF) capabilities of the AP.

[0060] In some implementations, when performing aggregated bandwidth operations, process 600 may involve processor 422 discovering the secondary link based on the Simplified Neighbor Report (RNR) element, setting the TBTT Information Field Type subfield to a first predefined value (e.g., 1) and the TBTT Information Field Length subfield to a second predefined value (e.g., 1 or 3) in the Target Beacon Transit Time (TBTT) Information field.

[0061] In some implementations, the channel number of the secondary link can be indicated in the neighboring AP field of the AP on the secondary link within the RNR element.

[0062] In some implementations, when performing aggregated bandwidth operation, process 600 may involve processor 422 instructing the AP whether the STA is able to dynamically switch channels within a specific bandwidth less than or equal to the aggregated bandwidth.

[0063] In some implementations, in response to a non-AP STA belonging to a single-radio multi-link device, when performing aggregate bandwidth operation, process 600 may involve processor 422 identifying the reporting AP with aggregate bandwidth capability through the aggregate bandwidth capability in the Ultra-High Reliability (UHR) operation element or UHR capability element indicated in the beacon frame or management frame. In some implementations, when performing aggregate bandwidth operation, process 600 may further involve processor 422 identifying the link-disabled state of the secondary link and the aggregate bandwidth of the reporting AP based on the Simplified Neighbor Report (RNR) element.

[0064] In some implementations, in response to a non-AP STA belonging to a multi-radio multi-link device, when performing aggregate bandwidth operation, process 600 may involve processor 422 identifying a reported AP with aggregate bandwidth capability based on a Simplified Neighbor Report (RNR) element carried in the beacon frame or management frame. This element includes another neighbor AP whose Target Beacon Transmission Time (TBTT) information field type subfield is set to a first predefined value (e.g., 1), its TBTT information field length subfield is set to a second predefined value (e.g., 1 or 3), and it has the same link identifier (ID) as the reported AP. In some implementations, when performing aggregate bandwidth operation, process 600 may further involve processor 422 identifying the link-disabled state of the secondary link and the aggregate bandwidth of the reported AP based on the RNR element.

[0065] In some implementations, when performing aggregated bandwidth operations with the AP, process 600 may involve processor 422 performing specific operations. For example, process 600 may involve processor 422 receiving a control frame from the AP. Furthermore, in response to receiving the control frame, process 600 may involve processor 422 sending a control response frame to the AP via the primary link, or sending a control response frame via the secondary link after switching to the secondary link. Additionally, process 600 may involve processor 422 receiving downlink (DL) physical layer protocol data units (PPDUs) or trigger frames via the primary or secondary link.

[0066] Additional notes

[0067] The topics described herein sometimes demonstrate different components contained within or connected to other different components. It should be understood that such illustrated architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a specific function can be considered “associated with each other” to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operationally connected” or “operationally coupled” to achieve the desired function, and any two components that can be suchly associated can also be considered “operationally coupled” to achieve the desired function. Specific examples of operational coupling include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive and / or logically interactive components.

[0068] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. Various singular / plural arrangements are explicitly listed herein for clarity.

[0069] Furthermore, those skilled in the art will understand that the terms commonly used herein, particularly in appended claims, such as the body portion of appended claims, are generally intended as “open” terms. For example, the word “comprising” should be interpreted as “including but not limited to,” the word “having” should be interpreted as “having at least,” and the word “includes” should be interpreted as “including but not limited to,” etc. Those skilled in the art will also understand that if a specific number of claim statements are explicitly stated in the claim, that intention will be explicitly stated in the claim; if no such statement is present, then that intention does not exist. For example, for ease of understanding, the following appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce claim statements. However, the use of such phrases should not be construed as limiting any particular claim containing such an introductory claim statement to containing only one such statement, even if the same claim contains the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an,” for example, “a” and / or “an” should be interpreted as “at least one” or “one or more”; the same applies to definite articles used to introduce claim statements. Furthermore, even when a specific number of claims is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as at least the stated number; for example, the phrase "two statements" alone, without any other modifiers, means at least two statements, or two or more statements. Additionally, when using conventions such as "at least one A, B, and C, etc.", such structures are generally intended to be understood by those skilled in the art in a manner that makes the convention clear. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems with only A, only B, only C, A and B, A and C, B and C, and systems with A, B, and C, etc. Similarly, when using conventions such as "at least one A, B, or C, etc.", such structures are generally intended to be understood by those skilled in the art in a manner that makes the convention clear. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems with only A, only B, only C, A and B, A and C, B and C, and systems with A, B, and C, etc. Those skilled in the art will further understand that virtually any extractive term and / or phrase presenting two or more alternative terms in the specification, claims, or drawings should be understood to include one, any, or both terms. For example, the phrase “A or B” will be understood to include the possibility of “A” or “B” or “A and B”.

[0070] As can be seen from the foregoing, various implementations of this disclosure have been described herein for illustrative purposes, and various modifications can be made without departing from the scope and spirit of this disclosure. Therefore, the various implementations disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the following claims.

Claims

1. A method, comprising: A basic service set is established by a processor at an access point on a primary link and a secondary link; as well as The processor performs an aggregated bandwidth operation with one or more workstations. The aggregated bandwidth of the main link and the auxiliary link depends on the channel availability of each of the main link and the auxiliary link.

2. The method as described in claim 1, wherein, The access point belongs to a multi-link access point device, and the link identifier of the main link is the same as the link identifier of the auxiliary link.

3. The method as described in claim 1, wherein, Performing the aggregated bandwidth operation involves sending a beacon frame or a management frame on the primary link, but not on the secondary link, to indicate an aggregated bandwidth capability and the aggregated bandwidth in an ultra-high reliability operation element or an ultra-high reliability capability element at the access point, the ultra-high reliability capability element being transmitted on the primary link by the beacon frame or the management frame.

4. The method of claim 3, wherein, The management frame includes either a probe response frame or an association response frame.

5. The method of claim 3, wherein, The beacon frame or the management frame advertises the secondary link by setting a target beacon transmission time information field type subfield to a first predefined value and a target beacon transmission time information field length subfield to a second predefined value in a target beacon transmission time information field, using a simplified neighbor report element, wherein the target beacon transmission time information field corresponds to a reporting access point on the secondary link.

6. The method of claim 5, wherein, The target beacon transmission time information field corresponds to the reported access point on the auxiliary link and includes at least one link identification subfield, one link disabled subfield, and one aggregated bandwidth subfield.

7. The method of claim 6, wherein, The "Link Disabled" subfield indicates whether the secondary link is enabled or disabled, such that: In response to the link disable subfield indicating that the secondary link is enabled, the aggregate bandwidth is indicated in the target beacon transmission time information field to indicate that the access point is operating at the aggregate bandwidth; as well as When the link disabled subfield indicates that the secondary link is disabled, the aggregate bandwidth subfield is retained in the target beacon transmission time information field to indicate that the access point is not operating at the aggregate bandwidth.

8. The method of claim 5, wherein, The channel number of the secondary link is indicated in the simplified neighbor report element in the neighbor access point field corresponding to the access point reported on the secondary link.

9. The method of claim 1, wherein, Performing the aggregated bandwidth operation includes a reporting access point, which is part of an access point multilink device, announcing the primary link and the secondary link of a neighboring access point, which is part of the access point multilink device, as an aggregated bandwidth capability neighboring access point.

10. The method of claim 9, wherein, The notification includes setting a target beacon transmission time information field type subfield to a first predefined value and a target beacon transmission time information field length subfield to a second predefined value in a simplified neighbor report element to notify the main link.

11. The method of claim 1, wherein, Performing the aggregated bandwidth operation with the one or more workstations includes: Obtain a transmission opportunity; Send a control frame to a first workstation and a second workstation among the one or more workstations, and instruct the second workstation to switch to the auxiliary link; A first control response frame is received from the first workstation via the main link, and a second control response frame is received from the second workstation via the auxiliary link; The main link sends a downlink physical layer protocol data unit or a trigger frame to the first workstation, and the auxiliary link sends it to the second workstation.

12. A method comprising: A beacon frame or a management frame indicating an aggregate bandwidth capability of an access point is received by a processor at a non-access point workstation. as well as The processor and the access point perform an aggregated bandwidth operation involving a primary link and a secondary link. The aggregated bandwidth of the main link and the auxiliary link depends on the channel availability of each of the main link and the auxiliary link.

13. The method of claim 12, wherein, Performing this aggregated bandwidth operation involves, based on a simplified neighbor report element, setting a target beacon transmission time information field type subfield to a first predefined value and setting the target beacon transmission time information field length subfield to a second predefined value in a target beacon transmission time information field to discover the secondary link.

14. The method of claim 13, wherein, The channel number of the secondary link is indicated in the neighbor access point field of the access point on the secondary link in the simplified neighbor report element.

15. The method of claim 12, wherein, Performing the aggregated bandwidth operation includes instructing the access point whether the workstation can dynamically switch channels within a specific bandwidth that is less than or equal to the aggregated bandwidth.

16. The method of claim 12, wherein, When the non-access point workstation belongs to a single radio multi-link device, performing the aggregated bandwidth operation includes identifying a reporting access point with aggregated bandwidth capability by means of an aggregated bandwidth capability in an ultra-high reliability operation element or a UHR capability element indicated in the beacon frame or the management frame.

17. The method of claim 16, wherein, Performing the aggregated bandwidth operation further includes identifying a link-disabled state of the secondary link and the aggregated bandwidth of the reporting access point based on a simplified neighbor report element.

18. The method of claim 12, wherein, When the non-access point workstation belongs to a multi-radio multi-link device, performing the bandwidth aggregation operation includes identifying a reporting access point with the bandwidth aggregation capability based on a simplified neighbor reporting element carried in the beacon frame or the management frame. The simplified neighbor reporting element includes another neighbor access point, which has a target beacon transmission time information field type subfield set to a first predefined value, a target beacon transmission time information field length subfield set to a second predefined value, and has the same link identifier as the reporting access point.

19. The method of claim 18, wherein, Performing the aggregated bandwidth operation further includes identifying the link-disabled status of the secondary link and the aggregated bandwidth of the reported access point based on the simplified neighbor reporting element.

20. The method of claim 12, wherein, Performing the aggregated bandwidth operation with the access point includes: Receive a control frame from the access point; In response to receiving the control frame, a control response frame is sent to the access point via the main link or via the secondary link after switching to the secondary link. The next physical layer protocol data unit or a trigger frame is received through the main link or the auxiliary link.

Images