Multi-link traffic identifier tid mapping

Abstract

A first MLD, configured to communicate with at least one second MLD, is configured to assign a score to each link of a plurality of available links, the score being based on a communication capability of each link; assign an aggregation score to a set of links, the set of links including at least two links selected from the plurality of available links, the aggregation score being based on the scores of each link of the set of links and being assigned based on satisfaction of a condition; select, for a transmission, one of a first link of the plurality of available links or the set of links, the selection being based on the score of the first link or on the aggregation score of the set of links; and transmit using the selected one of the first link or the set of links.

Description

[0001] MULTI-LINK TRAFFIC IDENTIFIER TID MAPPING

[0002] FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to configurations for multi-link traffic identifier mapping.

[0004] INTRODUCTION

[0005] Wi-Fi, also known as Wireless Local Area Network (WLAN), is a technology that currently mainly operates on the 2.4 GHz or the 5 GHz band, though it may operate in other bands including, e.g., the 6 GHz band. There are specifications regulating an access points' or wireless terminals' physical (PHY) layer, medium access layer (MAC) layer and other aspects in order to secure compatibility and inter-operability between different WLAN entities, e.g., between an access point and mobile terminals, both of which may be referred to as stations (STAs) herein. Wi-Fi is generally operated in unlicensed bands, and as such, communication over Wi-Fi may be subject to interference sources from any number of known and unknown devices. Wi-Fi is commonly used as wireless extensions to fixed broadband access, e.g., in domestic environments and hotspots, like airports, train stations and restaurants.

[0006] Multi-link operation in IEEE 802.11be

[0007] Standards, such as those specified by Institute of Electrical and Electronics Engineers (IEEE) 802.11be, describe multi-link operation (MLO) for Wi-Fi devices. MLO allows a multi-link device (MLD) to have more than one radio that can either transmit or receive concurrently, commonly referred to as a “link.” Thus, a MLD can, e.g., use one radio in the 5 GHz band and one in the 6 GHz band simultaneously, possibly providing higher throughput, lower channel access delay as well as higher reliability due to redundancy.

[0008] IEEE 802.1 Ibe defines four different modes of multi-link operation, as follows:

[0009] • Simultaneous Transmit and Receive (STR)

[0010] • Non-Simultaneous Transmit and Receive (NSTR)

[0011] • Enhanced Multi-Link Single Radio (EMLSR)

[0012] • Enhanced Multi-Link Multiple Radio (EMLMR)

[0013] These different modes come with different capabilities and complexity. Essentially, STR allows simultaneous and asynchronous operation of the links, NSTR allows simultaneous operation of the links but requires their synchronization to avoid selfinterference, and EMLSR / EMLMR allow non-simultaneous operation.

[0014] An MLD device according to, e.g., IEEE 802.11 may choose to deliver data belonging to a certain traffic flow on one or more links. When making this choice, the device can use the Traffic ID (TID)-to-link mapping element. This element allows for quick rearranging of what TIDs are mapped to a certain link and may be used dynamically.

[0015] Integrated mmWave

[0016] At the March 2023 IEEE 802.11 meeting, the Project Authorization Request (PAR) developed by the Ultra High Reliability Study Group (UHR SG) was approved, and as a result, Task Group (TG) bn will be in operation beginning November 2023 to develop the UHR amendment. The amendment seeks to increase throughput, lower latency, increase reliability, increase the scalability and reduce complexity of the next generation of Wi-Fi products.

[0017] During the UHR SG development, it was suggested to enhance the multi-link operation (MLO) introduced in the IEEE 802.1 Ibe amendment by allowing a combination of links operating in the sub-7 GHz band with links operating in the 60 GHz band. Furthermore, a suggestion was to re-use one of the sub-7 GHz PHYs in the 60 GHz band. This may represent a significant simplification in comparison to other standards operating in the 60 GHz bands (e.g., IEEE 802.1 lad, IEEE 802.1 lay) that specify their own separate PHY designs.

[0018] At the March 2023 IEEE 802.11 meeting, it was proposed to reuse the sub 7 GHz PHY and upclock it eight times such that a sub 7 GHz 160 MHz channel would become a 1280 MHz channel in 60 GHz. Thus, potentially giving a capacity boost when compared to a sub 7 GHz channel.

[0019] 3GPP / Cellular

[0020] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks. In 3GPP, multi-link operation has existed since high-speed packet access (HSPA). A primary multi-link operation mode for cellular systems is carrier aggregation, where a single scheduler is responsible for scheduling data on multiple licensed carriers. In this operation, the scheduler is responsible for both splitting of data and scheduling. Hence, data assigned to carrier can be transmitted, and splitting data can be straightforward.

[0021] For a 3GPP-specified system, there may also be another multi-link operation mode, namely, dual connectivity. In dual connectivity, the data is split higher up in the protocol stack and sent to independent schedulers responsible for a subset of the available licensed carriers. Hence, the splitting of data may be less intuitive, and this mode resembles the Wi-Fi multi-link operation, in that the splitting function may not have full control of when the data is to be transmitted.

[0022] SUMMARY

[0023] Aspects are provided in the independent claims, and embodiments thereof are provided in the dependent claims.

[0024] Some embodiments advantageously provide methods, systems, and apparatuses for multi-link traffic identifier mapping in wireless communication systems.

[0025] Wi-Fi Multi-link Scheduling

[0026] Existing approaches to scheduling data effectively (i.e., with low delays and packet losses) over more than one link between a pair of MLDs have proven challenging. This is because the manner in which to split the data over (both) links becomes unintuitive, as any wideband license-exempt spectrum technology has to contend for the wireless medium independently on each link. As such, it may not be efficient to split the data over more than one link if the chance to obtain the channel access on the second link is low.

[0027] Furthermore, a good strategy to deliver data may be to use the links in a “greedy” manner, i.e., whenever channel access is gained on a link transmit as much data on that link as possible. This scheduling principle is further described herein.

[0028] Described herein are example embodiments including a method for a pair of communicating devices with the potential to use the MLO framework for their communication to efficiently transition into the optimal link configuration depending on the different capabilities of the links.

[0029] According to embodiments described herein, it is possible to effectively choose how to map a certain TID to one or more available link without loss to performance, regardless of whether there exists asymmetry between the different communication links. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0031] FIG. l is a schematic diagram of an example network architecture illustrating a communication system according to the principles in the present disclosure;

[0032] FIG. 2 is a block diagram of an AP communicating with a Non-AP STA over an at least partially wireless connection according to some embodiments of the present disclosure;

[0033] FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0034] FIG. 4 is a block diagram of a host computer communicating via an access point with a non-AP STA over an at least partially wireless connection according to some embodiments of the present disclosure;

[0035] FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for executing a client application at a non-AP STA according to some embodiments of the present disclosure;

[0036] FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data at a non-AP STA according to some embodiments of the present disclosure;

[0037] FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data from the non-AP STA at a host computer according to some embodiments of the present disclosure;

[0038] FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data at a host computer according to some embodiments of the present disclosure;

[0039] FIG. 9 is a flowchart of an example process in an AP , according to some embodiments of the present disclosure; FIG. 10 is a graph of simulation results; and

[0040] FIG. 11 is another graph of simulation results.

[0041] DETAILED DESCRIPTION

[0042] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to multi-link traffic identifier mapping. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0043] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0044] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0045] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections. In some embodiments, the term “access point” or “AP” is used interchangeably and may comprise, or be, a network node. The AP may include any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, integrated access and backhaul (IAB), donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The AP may also comprise test equipment. The AP may comprise a radio router, a radio transceiver, WiFi access point, wireless local area network (WLAN) access point, a network controller, etc.

[0046] In some embodiments, the non-limiting term “device” is used to describe a wireless device (WD) and / or user equipment (UE) that may be used to implement some embodiments of the present disclosure. In some embodiments, the device may be and / or comprise an access point (AP) station (STA). In some embodiments, the device may be and / or comprise a non-access point station (non-AP STA). In some embodiments, the device may be any type of device capable of communicating with a network node, such as an AP, over radio signals. The device may be any radio communication device, target device, a portable device, device-to-device (D2D) device, machine type device or device capable of machine to machine communication (M2M), low-cost and / or low-complexity device, a sensor equipped with a device, a computer, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, Reduced Capability (RedCap) device, etc.

[0047] A device may be considered a network node and may include physical components, such as processors, allocated processing elements, or other computing hardware, computer memory, communication interfaces, and other supporting computing hardware. The network node may use dedicated physical components, or the node may be allocated use of the physical components of another device, such as a computing device or resources of a datacenter, in which case the network node is said to be virtualized. A network node may be associated with multiple physical components that may be located either in one location, or may be distributed across multiple locations.

[0048] Even though the descriptions herein may be explained in the context of one of a Downlink (DL) and an Uplink (UL) communication, it should be understood that the basic principles disclosed may also be applicable to the other of the one of the DL and the UL communication. In some embodiments in this disclosure, the principles may be considered applicable to a transmitter and a receiver. For DL communication, the AP station may be the transmitter and the receiver is the non-AP station. For the UL communication, the transmitter may be the non-AP station and the receiver is the AP station.

[0049] Note also that some embodiments of the present disclosure may be supported by an Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. IEEE 802.11 denotes a set of Wireless Local Area Network (WLAN) air interface standards developed by the IEEE 802.11 committee for short-range communications (e.g., tens of meters to a few hundred meters). Some embodiments may also be supported by standard documents disclosed in Third Generation Partnership Project (3GPP) technical specifications. That is, some embodiments of the description can be supported by the above documents. In addition, all the terms disclosed in the present document may be described by the above standard documents.

[0050] Note that although terminology from one particular wireless system, such as, for example, IEEE 802.11, 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), 5th Generation (5G) and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0051] In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or one or both of A and B . In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and / or A, B, C or a combination thereof.

[0052] Note further, that functions described herein as being performed by one or more of a STA, AP, non-AP STA, wireless device, network node, etc., may be distributed over a plurality of STAs, APs, non-AP STAs, wireless devices, network nodes, etc. In other words, it is contemplated that the functions of the devices described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0053] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0054] Some embodiments provide configurations for multi-link traffic identifier mapping.

[0055] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of the communication system 10, according to one embodiment, constructed in accordance with the principles of the present disclosure. The communication system 10 in FIG. 1 is a nonlimiting example and other embodiments of the present disclosure may be implemented by one or more other systems and / or networks. Referring to FIG. 1, system 10 may comprise a wireless local area network (WLAN). The devices in the system 10 may communicate over one or more spectrums, such as, for example, an unlicensed spectrum, which may include frequency bands typically used by Wi-Fi technology. One or more of the devices may be further configured to communicate over other frequency bands, such as shared licensed frequency bands, etc. The system 10 may include one or more coverage areas 12a, 12b, etc. (collectively referred to herein as “coverage area 12”), which may be defined by corresponding access points (APs) 14a, 14b, etc. (collectively referred to herein as “AP 14”). The AP 14 may or may not be connectable to another network, such as a core network over a wired or wireless connection. The system 10 includes a plurality of non-AP devices, such as, for example, non-AP STAs 16a, 16b, 16c (collectively referred to as non-AP STAs 16). Each of the non-AP STAs 16 may be located in one or more coverage areas 12 and may be configured to wirelessly connect to one or more AP 14. Note that although two APs 14a and 14b and two non-AP STAs 16a and 16b are shown for convenience, the communication system may include many more non-AP STAs 16 and APs 14. Each AP 14 may connect to / serve / configure / schedule / etc. one or more non-AP STAs 16. According to one or more embodiments, AP 14 and / or non-AP STA 16 may be multilink devices (MLDs) that perform one or more functions described herein. It should be understood that the system 10 may include additional nodes / devices not shown in FIG. 1. In addition, the system 10 may include many more connect! ons / interfaces than those shown in FIG. 1. Thus, the elements shown in FIG. 1 are presented for ease of understanding.

[0056] Also, it is contemplated that a non-AP STA 16 can be in communication and / or configured to separately communicate with more than one AP 14 and / or more than one type of AP 14. Furthermore, an AP 14 may be in communication and / or configured to separately communicate with other APs 14, which may be via wired and / or wireless communication channels.

[0057] An AP 14 is configured to include a MLO unit 18, which is configured to perform one or more AP 14 functions described herein, such as multi -link traffic identifier mapping.

[0058] Example implementations, in accordance with an embodiment, of the AP 14 and non-AP STA 16 discussed in the preceding paragraphs will now be described with reference to FIG. 2.

[0059] The AP 14 includes hardware 20 including a communication interface 22, processing circuitry 24, a processor 26, and memory 28. The communication interface 22 may be configured to communicate with any of the nodes / devices in the system 10 according to some embodiments of the present disclosure, such as with one or more other APs 14 and / or one or more non-AP STAs 16. In some embodiments, the communication interface 22 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and / or one or more RF transceivers, and / or may be considered a radio interface. In some embodiments, the communication interface 22 may also include a wired interface.

[0060] The processing circuitry 24 may include one or more processors 26 and memory, e.g., memory 28. In addition to a processor 26 and memory 28, the processing circuitry 24 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 26 may be configured to access (e.g., write to and / or read from) the memory 28, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). The AP 14 may further include software 30 stored internally in, for example, memory 28, or stored in external memory (e.g., database) accessible by the AP 14 via an external connection. The software 30 may be executable by the processing circuitry 24. The processing circuitry 24 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., AP 14. The memory 28 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 30 may include instructions stored in memory 28 that, when executed by the processor 26 and / or MLO unit 18 causes the processing circuitry 24 and / or configures the AP 14 to perform the processes described herein with respect to the AP 14 (e.g., processes described with reference to FIG. 9, and / or any of the other figures herein).

[0061] Referring still to FIG. 2, the non-AP STA 16 includes hardware 32, which may include a communication interface 34, processing circuitry 36, a processor 38, and memory 40. The communication interface 34 may be configured to communicate with one or more AP 14, such as via wireless connection 35, and / or with other elements in the system 10, according to some embodiments of the present disclosure. In some embodiments, the communication interface 34 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and / or one or more RF transceivers, and / or may be considered a radio interface. In some embodiments, the communication interface 34 may also include a wired interface.

[0062] The processing circuitry 36 may include one or more processors 38 and memory, such as, the memory 40. Furthermore, in addition to a traditional processor and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0063] Thus, the non-AP STA 16 may further include software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database) accessible by the non- AP STA 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by the non-AP STA 16. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software may include instructions stored in memory 40 that, when executed by the processor 38, causes the processing circuitry 36 and / or configures the non-AP STA 16 to perform the processes described herein with respect to the non-AP STA 16 (e.g., processes described with reference to FIG. 9, and / or any of the other figures herein).

[0064] In FIG. 2, the connection between the devices AP 14 and the non-AP STAs 16 is shown without explicit reference to any intermediary devices or connections. However, it should be understood that intermediary devices and / or connections may exist between these devices, although not explicitly shown.

[0065] Although FIG. 2 shows MLO unit 18, as being within a processor, it is contemplated that this element may be implemented such that a portion of the element is stored in a corresponding memory within the processing circuitry. In other words, the element may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0066] FIG. 3 is a schematic diagram of a communication system 10, according to another embodiment of the present disclosure. In the example of FIG. 3, the access point 14 and non-AP STAs 16 may be similar to those of the example of FIG. 1, described herein. Additionally, in the example of FIG. 3, one or more APs 14 and / or non-AP STAs 16 may form and / or be part of a service set network 44 (e.g., a basic service set, or any other network, set, and / or grouping of APs 14 and non-AP STAs 16). The communication system 10 and / or service set network 44 may itself be connected to a host computer 46, which may be embodied in the hardware and / or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 46 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 48, 50 between the communication system 10 and / or the service set network 44 and the host computer 46 may extend directly from the service set network 44 to the host computer 46 or may extend via an optional intermediate network 52. The intermediate network 52 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 52, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 52 may comprise two or more sub-networks (not shown).

[0067] The communication system of FIG. 3 as a whole enables connectivity between one of the connected non-AP STAs 16 and the host computer 46. The connectivity may be described as an over-the-top (OTT) connection. The host computer 46 and the connected non AP-STAs 16 are configured to communicate data and / or signaling via the OTT connection, using the service set network 44, any intermediate network 52 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, an AP 14 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 46 to be forwarded (e.g., handed over) to a connected non-AP STA 16. Similarly, the AP 14 need not be aware of the future routing of an outgoing uplink communication originating from the non-AP STA 16 towards the host computer 46.

[0068] Example implementations, in accordance with an embodiment, of the non-AP STA 16 (e.g., type of MLD), AP 14 (e.g., another type of MLD), and host computer 46 discussed in the preceding paragraphs will now be described with reference to FIG. 4. In the example of FIG. 4, the AP 14 and the non-AP STA 16 may have similar features and components as the AP 14 and non-AP STA 16 depicted in FIG. 2. Additionally, the host computer 46 comprises hardware (HW) 53 including a communication interface 54 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 46 further comprises processing circuitry 56, which may have storage and / or processing capabilities. The processing circuitry 56 may include a processor 58 and memory 60. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 56 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 58 may be configured to access (e.g., write to and / or read from) memory 60, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Processing circuitry 56 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by host computer 46. Processor 58 corresponds to one or more processors 58 for performing host computer 46 functions described herein. The host computer 46 includes memory 60 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 62 and / or the host application 64 may include instructions that, when executed by the processor 58 and / or processing circuitry 56, causes the processor 58 and / or processing circuitry 56 to perform the processes described herein with respect to host computer 46. The instructions may be software associated with the host computer 46.

[0069] The software 62 of host computer 46 may be executable by the processing circuitry 56. The software 62 includes a host application 64. The host application 64 may be operable to provide a service to a remote user, such as a non-AP STA 16 connecting via an OTT connection 66 terminating at the non-AP STA 16 and the host computer 46. In providing the service to the remote user, the host application 64 may provide user data which is transmitted using the OTT connection 66. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 46 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 56 of the host computer 46 may enable the host computer 46 to observe, monitor, control, transmit to and / or receive from the AP 14 and / or the non-AP STA 16. The processing circuitry 56 of the host computer 46 may include a Cloud Configuration unit 68 configured to enable the service provider to observe / monitor / control / transmit to / receive from / configure / etc. the AP 14 and / or the non- AP STA 16.

[0070] The communication interface 22 of AP 14 may be configured to facilitate a connection 66 to the host computer 46. The connection 66 may be direct or it may pass through a service set network 44 of the communication system 10 and / or through one or more intermediate networks 52 outside the communication system 10. The communication interface 34 of non-AP STA 16 may be configured to facilitate a connection 66 to the host computer 46. The connection 66 may be direct or it may pass through a service set network 44 of the communication system 10 and / or through one or more intermediate networks 52 outside the communication system 10. The software 42 of non-AP STA 16 may include a client application 70. The client application 70 may be operable to provide a service to a human or non-human user via the non-AP STA 16, with the support of the host computer 46. In the host computer 46, an executing host application 64 may communicate with the executing client application 70 via the OTT connection 66 terminating at the non-AP STA 16 and the host computer 46. In providing the service to the user, the client application 70 may receive request data from the host application 64 and provide user data in response to the request data. The OTT connection 66 may transfer both the request data and the user data. The client application 70 may interact with the user to generate the user data that it provides.

[0071] In some embodiments, the inner workings of the AP 14, non-AP STA 16, and host computer 46 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3.

[0072] In FIG. 4, the OTT connection 66 has been drawn abstractly to illustrate the communication between the host computer 46 and the non-AP STA 16 via the AP 14, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the non-AP STA 16 or from the service provider operating the host computer 46, or both. While the OTT connection 66 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0073] The wireless connection 35 between the non-AP STA 16 and the AP 14 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the non-AP STA 16 using the OTT connection 66, in which the wireless connection 35 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0074] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 66 between the host computer 46 and non-AP STA 16, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 66 may be implemented in the software 62 of the host computer 46 or in the software 42 of the non-AP STA 16, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 66 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 62, 42 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 66 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the AP 14, and it may be unknown or imperceptible to the AP 14. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary wireless device signaling facilitating the host computer’s 46 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 62, 42 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 66 while it monitors propagation times, errors, etc.

[0075] Thus, in some embodiments, the host computer 46 includes processing circuitry 56 configured to provide user data and a communication interface 54 that is configured to forward the user data to a wireless network and / or cellular network for transmission to the non-AP STA 16. In some embodiments, the wireless network and / or cellular network also includes the AP 14 with a communication interface 22. In some embodiments, the AP 14 is configured to, and / or the AP 14 processing circuitry 24 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the non-AP STA 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the non-AP STA 16.

[0076] In some embodiments, the host computer 46 includes processing circuitry 56 and a communication interface 54 that is configured to receive user data originating from a transmission from a non-AP STA 16 to an AP 14. In some embodiments, the non-AP STA 16 is configured to, and / or comprises a communication interface 34 and / or processing circuitry 36 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the AP 14, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the AP 14. FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 7 and 8, in accordance with one embodiment. The communication system may include a host computer 46, an AP 14 and a non-AP STA 16, which may be those described with reference to FIG. 4. In a first step of the method, the host computer 46 provides user data (Block SI 00). In an optional substep of the first step, the host computer 46 provides the user data by executing a host application, such as, for example, the host application 64 (Block SI 02). In a second step, the host computer 46 initiates a transmission carrying the user data to the non-AP STA 16 (Block S104). In an optional third step, the AP 14 transmits to the non-AP STA 16 the user data which was carried in the transmission that the host computer 46 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the non-AP STA 16 executes a client application, such as, for example, the client application 70, associated with the host application 64 executed by the host computer 46 (Block SI 08).

[0077] FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 46, an AP 14 and a non-AP STA 16, which may be those described with reference to FIGS. 7 and 8. In a first step of the method, the host computer 46 provides user data (Block SI 10). In an optional substep (not shown) the host computer 46 provides the user data by executing a host application, such as, for example, the host application 64. In a second step, the host computer 46 initiates a transmission carrying the user data to the non-AP STA 16 (Block SI 12). The transmission may pass via the AP 14, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the non-AP STA 16 receives the user data carried in the transmission (Block S114).

[0078] FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 46, an AP 14 and a non-AP STA 16, which may be those described with reference to FIGS. 7 and 8. In an optional first step of the method, the non-AP STA 16 receives input data provided by the host computer 46 (Block SI 16). In an optional substep of the first step, the non-AP STA 16 executes the client application 70, which provides the user data in reaction to the received input data provided by the host computer 46 (Block SI 18). Additionally or alternatively, in an optional second step, the non-AP STA 16 provides user data (Block S120). In an optional substep of the second step, the non-AP STA 16 provides the user data by executing a client application, such as, for example, client application 70 (Block S122). In providing the user data, the executed client application 70 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the non-AP STA 16 may initiate, in an optional third substep, transmission of the user data to the host computer 46 (Block S124). In a fourth step of the method, the host computer 46 receives the user data transmitted from the non-AP STA 16, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

[0079] FIG. 8 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 46, an AP 14 and a non-AP STA 16, which may be those described with reference to FIGS. 7 and 8. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the AP 14 receives user data from the non-AP STA 16 (Block S128). In an optional second step, the AP 14 initiates transmission of the received user data to the host computer 46 (Block S130). In a third step, the host computer 46 receives the user data carried in the transmission initiated by the AP 14 (Block S132).

[0080] FIG. 9 is a flowchart of an example process in a MLD (e.g., first AP 14 such as, for example, a sharing or participating AP) for multi -link traffic identifier mapping. For example, one or more Blocks and / or functions and / or methods performed by the first AP 14 (e.g., sharing AP 14) may be performed by one or more elements of the first AP 14 such as by MLO unit 18 in processing circuitry 24, memory 28, processor 26, communication interface 22, etc. according to the example process / method. The first MLD is configured to assign a score to each link of a plurality of available links, the score being based on a communication capability of each link (Block SI 34). The first MLD is configured to assign an aggregation score to a set of links, the set of links including at least two links selected from the plurality of available links, the aggregation score being based on the scores of each link of the set of links and being assigned based on satisfaction of a condition (Block S136). The first MLD is configured to select, for a transmission, one of a first link of the plurality of available links or the set of links, the selection being based on the score of the first link or on the aggregation score of the set of links (Block S138). The first MLD is configured to transmit using the selected one of the first link or the set of links (Block S140).

[0081] In at least one embodiment, the first MLD is a first access point (AP) and the second MLD is one of a second AP or a non-AP station (non-AP STA).

[0082] In at least one embodiment, the condition is based on a similarity of the scores of each link of the set of links.

[0083] In at least one embodiment, the first MLD is further configured to modify, based on the condition not being met, the communication capabilities of at least one link of the set of links to achieve the similarity of the scores of each link of the set of links.

[0084] In at least one embodiment, the selection is based on at least one parameter associated with each of the plurality of available links, the at least one parameter including at least one of a maximum allowed transmit (Tx) power; a usable bandwidth of the available link; a maximum Aggregated MAC Protocol Data Unit (A-MPDU) duration; a maximum Transmit Opportunity (TXOP) duration; at least one channel conditions of the available link; a number of Tx antennas; a number of receive (Rx) antennas; at least one physical (PHY) transmission feature; at least one hardware capability; and an increase in a load on the available link.

[0085] In at least one embodiment, selecting one of the first link or the set of links for the transmission comprises altering a property of at least one of the at least two links of the set of links.

[0086] Single-link operation may outperform multi-link operation in certain circumstances and for some particular types of traffic. See, e.g., FIG. 10, which depicts a comparison of the throughput of a single 1280 MHz mmWave link and an MLD with the same 1280 MHz mmWave link and an additional 20 MHz link in the 5 GHz band for different file sizes of a file transfer protocol, FTP, download.

[0087] As shown, the relative performance between the single-link (SL) and multi-link (ML) configuration varies depending on the file size of the FTP download. There are three different effects that, in combination, may explain the characteristics. 1. In the leftmost portion of FIG. 10, ML outperforms SL by about 20%. At this point, the size of data to be delivered is small enough such that after the setup of the FTP / transmission control protocol (TCP) connection the payload fits into a single medium access control (MAC) protocol data unit (MPDU), in both links despite their largely different bandwidth. Thus, it may be more important to deliver the data reliably with a single transmission, in either of the two links, rather than with a high speed, risking rare transmission errors. As the 20 MHz link may be significantly more reliable than the mmWave link, in approximately 10% of the cases when the 20 MHz link was used to deliver the data it was delivered in one shot, whereas the mmWave needed retransmissions for the link adaptor to accurately adapt. These retransmissions can produce a long tail in the latency distribution of the mmWave SL, which may explain the advantage of the ML.

[0088] 2. Moving from the leftmost portion of FIG. 10, as the file size increases, the performance of ML significantly drops down to only about 30% to that of SL. In this region, the payload is split by TCP into several fragments, which are then given to the MAC layer according to the TCP congestion window (CWD) size. As this size has a small start value and is only increased when data was transmitted successfully, with these file sizes the MAC layer may not get sufficient data to use the two links concurrently. With the selected link selection strategy (“greedy”), the link is randomly selected for each transmission. If the 20 MHz link is selected, i.e., as the MAC layer did not get enough data from TCP, the fast mmWave will be idle during the complete long transmission time. Hence, the total FTP file transmission takes much longer in comparison to only using the mmWave link, even considering the higher probability of transmission errors and the resulting retransmissions.

[0089] 3. The final effect that was found was in the ascending region where performance starts increasing from the 30%. In this region, TCP has enough data to increase the CWD to a size such that concurrent operation is possible. However, initially for the smaller file sizes, there is insufficient data to have efficient concurrent use. Rather, when a 20 MHz transmission occurs, there might be enough data to have a single mmWave transmission that will occupy just a small portion of the total airtime of the 20 MHz transmission. However, as the file size increases, eventually there is sufficient data such that efficient concurrent use can be operated until the performance converges to -107% relative performance and the initial effects of point 1 and 2 becomes insignificant in relation to the total transmission duration. Thus, there exists a need for methods that will allow for efficient MLO usage for all potential sizes of data transfer as well as varying capabilities and transmission configurations at the different devices.

[0090] Various embodiments described herein relate to a method for a pair of communication devices capable of operating on multiple asynchronous communication links to efficiently select how to operate on these links. As was explained above the method may be applicable for MLO communication between at least two of MLDs, wherein one of them is a transmitter device transmitting to a receiver device, including but not limited by the DL communication, wherein the transmitter device may be the AP and the receiver devices may be the STA (e.g., non-AP STA), or the UL communication, wherein the transmitter device may be the STA and the receiver device may be the AP. For the sake of conciseness, this MLO communication is described below in the examples as DL communication between the AP MLD (e.g., MLD that is an AP STA) and non-AP STA MLD (e.g.,. MLD that is a non-AP STA). Example methods, which may be implemented, e.g., in an MLO Unit 18 of an AP 14, include:

[0091] Example 1 : An AP 14 (e.g., AP STA) that receives a request to start data communication for a new TID and wants to decide how to map this TID to one or more available links, a. Collects necessary capabilities and measurements on the available links. b. Assigns a score to each available link based on the estimated communication capability of that link. c. Upon verification of certain conditions, assigns aggregated scores to one or more set of links, each set consisting of two or more available links. d. Selects the highest score link, or the highest aggregated score set of links, for the new TID mapping.

[0092] Example 2: As in Example 1, where the conditions to verify relate to the similarity between each link’s score in the set, i.e., that only set of links with similar scores are assigned an aggregated score.

[0093] Example 3: As in either of Examples 1-2, where the scores assigned in step b may account for successive modification to the communication capability of a link such that the link’s scores are changed.

[0094] Example 4: As in any one of Examples 1-3, where the TID mapping is changed recurringly depending on what configurations currently has the highest score. Example 5: As in any one of Examples 1-4, where the assigned score is based on, but not limited to any of

[0095] • The maximum allowed transmit (Tx) power by regulations

[0096] • The usable bandwidth of the link

[0097] • The maximum Aggregated MAC Protocol Data Unit (A-MPDU) duration

[0098] • The maximum Transmit Opportunity (TXOP) duration

[0099] • The channel conditions on the links

[0100] • The number of Tx antennas

[0101] • The number of receive (Rx) antennas

[0102] • Other physical (PHY) related features, e.g., the size of the cyclic prefix

[0103] • Hardware capabilities, such as receiver sensitivity

[0104] • Additional load on each link, both within the basic service set (BSS) and as interference / occupiers of the medium

[0105] Various embodiments described herein relate to finding a suitable TID to link mapping configuration for a certain data flow belonging to a single traffic source, such as via an AP 14, by:

[0106] 1. Collecting information about the possible configurations, channel conditions and Tx parameters affiliated with each of the possible links.

[0107] 2. Assigning a score that represents the overall capabilities of each of the link.

[0108] 3. Depending on some condition, aggregating the score together of one or more links, e.g., if the scores of the individual links are close enough to one another.

[0109] 4. Deciding which TID to link configuration is most suitable depending on the scores.

[0110] Some parameters that may vary between two different Wi-Fi links and thus change the assigned score and potentially make these two links asymmetric towards each other are, e.g.:

[0111] • The maximum allowed Tx power by regulations

[0112] • The usable bandwidth of the link

[0113] • The maximum A-MPDU duration

[0114] • The maximum TXOP duration

[0115] • The channel conditions on the links

[0116] • The number of Tx antennas The number of Rx antennas

[0117] • Other PHY related features, e.g., the size of the cyclic prefix

[0118] • Hardware capabilities, such as receiver sensitivity

[0119] Additional load on each link, both within the BSS and as interference / occupiers of the medium

[0120] All this information is available to an AP 14 either when a STA wants to associate to the BSS and exchanges its capabilities or during operation as part of some measurement. However, as described above, the choice of how to map a TID to one or more links may not be obvious.

[0121] Discussed below are embodiments and examples that use this information to achieve proper operation between two communication devices when choosing to map a TID to one or more links.

[0122] Static Restricted Operation

[0123] In at least one embodiment, the AP 14 cho oses to only engage in MLO if there exist two or more links with equal properties, and good enough aggregated score for such set of links, such that essentially there exists no asymmetry between them (or that the asymmetry is sufficiently small), i.e., the AP has assigned them the same (or close enough) score. In such a case, there exists no need to take specific care of which link to use as essentially, they are the same.

[0124] For example, an AP 14 that has the choice of mapping a TID between 3 links where two are “similar” sub 7 GHz links that are assigned scores of 6 and 7, and one is a 1280 MHz mmWave link with score 10. In this case the AP decides to MAP the TID to the two sub 7 GHz links due to having a larger aggregated score than the single mmWave link as well as the difference between the two links being close enough for the AP to combine them. In another example, however, the assigned score of the sub 7 GHz links is 2 and 3 respectively, and the mmWave link has the same score of 10. In this case the AP would decide to map the TID to the single mmWave link due to the aggregated score of the sub 7 GHz links not being higher than the single mmWave link. In another example, the AP would still choose the single mmWave link if the scores of the sub 7 GHz links are too far apart such that they cannot be combined. This would be the case if, for example, the sub 7 GHz links have scores of 5 and 8 which are deemed to be too different by the AP to be combined.

[0125] This embodiment may be especially attractive for modern multi-link devices that may have more than one link in a single band, e.g., two links in the 6 GHz band. Dynamic Operation

[0126] In at least one embodiment, the AP 14 may instead of limiting the available options of links that are possible, change some communication parameters of the two links such that their relative performance is much closer to one another, i.e., change some Tx parameter such that the scores of the two links become close enough such that they may be combined according to other embodiments described herein.

[0127] In doing so, the AP 14 has two choices, either throttle the faster link or adjust how much of a bottleneck the slower link may become.

[0128] The first option may be suitable as a simple option when the related data has no stringent performance requirements that needs to be met and the AP 14 is more interested in improving the overall network efficiency. For example, if an AP 14 delivers data to STA 16 on a 20 MHz link in 2.4 GHz and on a 160 MHz link in 5 GHz. In this case, the AP 14 may instead choose to only deliver data on 20 MHz on the 5 GHz link in order to make the two links more equal in performance. This may be particularly useful if the AP 14 has other STAs 16 it can multiplex using OFDMA in the 5 GHz band.

[0129] If, however, there exists some stringent performance requirements related to the data to be delivered and all available resources should preferably be used for this data transfer it is more suitable 1) to restrict the operation on the slower link such that it does not produce significant bottlenecks, or 2) to allocate more resources to the slower link, e.g., using larger bandwidth, so that its score increases and becomes similar to the score of the other link(s) in use.

[0130] An example of how such a restriction may be imposed could be to reduce the maximum time that the slower link may be able to transmit (either through A-MPDU or TXOP duration limitations for example). As such, the likelihood that channel access is gained on the fast link and data is delivered while the slow link is still transmitting is lowered. In another example, the MLDs always tries to get channel access on the faster link first and only uses the slower link once channel access has been gained and never for a longer time duration than the faster link is already transmitting.

[0131] FIG. 11 depicts Simulation results of different FTP file sizes over a ML configuration of a 1280 MHz mmWave link and a 20 MHz sub 7 GHz link, with varying TXOP limits on the 20 MHz link. Results from the same scenario as described above can be seen but with varying TXOP limits for the slower 20 MHz link. As illustrated in FIG. 11, there is significant improvement in the performance region where previously the SL operation was performing much better, and the expected gain of >100% is reached for much smaller file sizes. There is, however some cost. For the smallest file size, the gain from having a robust link is lost because it is no longer possible to fit all data into a single transmission. Likewise at the largest file sizes, the top end gain has shrunk by a small margin, which is due to the aggregation gains on the slow link being not as good as with a longer allowed transmission duration.

[0132] Time-varying Dynamic Operation

[0133] At least one embodiment relates to adapting both the Tx configuration and link to TID mapping based both on the varying channel conditions, load, and interference as well as the buffer status of the TID.

[0134] Thus, in at least one embodiment, an AP 14 varies the TID to link mapping as well as the Tx configuration on each of the links throughout the lifespan of a certain data flow. For example, one strategy may be that the AP 14:

[0135] 1. Initially uses the most robust link to deliver the initial data frames with maximum transmission limit.

[0136] 2. When the data to be delivered starts to become significant, the AP may shift over to the faster link (which may be the same link).

[0137] 3. If there is data left in the buffer belonging to the TID, even after a transmission on the faster link has started, the AP 14 may start using both links with a reduced transmission limit on the slow link.

[0138] 4. When there starts to be significant data in the buffer even when trying to deliver as much as possible, the AP 14 can turn on all links without any restrictions.

[0139] By doing so, the AP 14 may keep the relative scores between the different links close enough such that TID to link mapping always has the highest score throughout the lifetime of the data transfer.

[0140] This strategy may perform well in scenarios where there is no interference and the AP 14 has only a single TID belonging to a TCP supported data flow to prioritize, and more complex strategies might need to be employed in more realistic scenarios.

[0141] In at least one embodiment, the AP 14 uses a non-heuristic approach to choose how to map the TID to the links and what Tx configuration to use on each link. For example, the AP 14 could maintain a database of the performance of different configurations and collect statistics of this operation in order to choose what is the best configurations. This operation could, for example, be similar to that of the minstrel link adaptation algorithm that uses similar principles and chooses the best performing modulation and coding scheme (MCS) to use by choosing from the database 90% of the time and 10% of the time it tries out new MCS to update its database. Although, the time scale at which to try out new configurations may be very different in some situations. This may be an attractive alternative if it is especially difficult to determine the asymmetry between the links. A similar approach, e.g., according to some embodiments, may also be to use machine learning principles to predict which TID mapping would be the best configuration instead of using a statistics-based approach.

[0142] In at least one embodiment, the AP 14 can use a default score for some parameters. This may be useful, as some information may not be immediately available to the AP but collected in a later stage of the communication. Thus, the AP 14 may make some assumptions in order to get a score that may be used, e.g., according to various embodiments described herein.

[0143] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0144] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. 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 may be provided to a processor of a general purpose computer (to thereby create a special 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 / acts specified in the flowchart and / or block diagram block or blocks.

[0145] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0146] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0147] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0148] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0149] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0150] Abbreviations that may be used in the preceding description include: Abbreviation Explanation

[0151] A-MPDU Aggregated MAC Protocol Data Unit

[0152] AP Access Point

[0153] MCS Modulation and Coding Scheme

[0154] MLD Multi-link Device

[0155] MLO Multi-link Operation

[0156] OFDMA Orthogonal Frequency Division Multiple Access ST A Station

[0157] TID Traffic Identifier

[0158] TXOP Transmit Opportunity

[0159] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

[0160] Embodiments:

[0161] Embodiment Al . A first multilink device (MLD) configured to communicate with at least one second MLD and / or at least one non-AP station (non-AP STA), the first MLD configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: assign a score to each link of a plurality of available links, the score being based on a communication capability of each link; assign an aggregation score to a set of links, the set of links including at least two links selected from the plurality of available links, the aggregation score being based on the scores of each link of the set of links and being assigned based on satisfaction of a condition; select, for a transmission, one of a first link of the plurality of available links or the set of links, the selection being based on the score of the first link or on the aggregation score of the set of links; and transmit using the selected one of the first link or the set of links.

[0162] Embodiment A2. The first MLD of Embodiment Al, wherein the first MLD is a first access point (AP) and the second MLD is one of a second AP or a non-AP station (non-AP ST A).

[0163] Embodiment A3. The first MLD of Embodiment Al, wherein the condition is based on a similarity of the scores of each link of the set of links.

[0164] Embodiment A4. The first MLD of Embodiment A3, wherein the first MLD is further configured to modify, based on the condition not being met, the communication capabilities of at least one link of the set of links to achieve the similarity of the scores of each link of the set of links.

[0165] Embodiment A5. The first MLD of Embodiment Al, wherein the selection is based on at least one parameter associated with each of the plurality of available links, the at least one parameter including at least one of: a maximum allowed transmit (Tx) power; a usable bandwidth of the available link; a maximum Aggregated MAC Protocol Data Unit (A-MPDU) duration; a maximum Transmit Opportunity (TXOP) duration; at least one channel conditions of the available link; a number of Tx antennas; a number of receive (Rx) antennas; at least one physical (PHY) transmission feature; at least one hardware capability; and an increase in a load on the available link.

[0166] Embodiment A6. The first MLD of any one of Embodiments A1-A5, wherein selecting one of the first link or the set of links for the transmission comprises altering a property of at least one of the at least two links of the set of links.

[0167] Embodiment BL A method implemented in a first multilink device (MLD)access point (AP) configured to communicate with at least one second multilink device (MLD)AP and / or at least one non-AP station (non-AP STA), the method comprising: assigning a score to each link of a plurality of available links, the score being based on a communication capability of each link; assigning an aggregation score to a set of links, the set of links including at least two links selected from the plurality of available links, the aggregation score being based on the scores of each link of the set of links and being assigned based on satisfaction of a condition; selecting, for a transmission, one of a first link of the plurality of available links or the set of links, the selection being based on the score of the first link or on the aggregation score of the set of links; and transmitting using the selected one of the first link or the set of links.

[0168] Embodiment B2. The method of Embodiment Bl, wherein the first MLD is a first access point (AP) and the second MLD is at least one of a second AP and a non-AP station (non-AP STA).

[0169] Embodiment B3. The method of Embodiment Bl, wherein the condition is based on a similarity of the scores of each link of the set of links.

[0170] Embodiment B4. The method of Embodiment B3, further comprising modifying, based on the condition not being met, the communication capabilities of at least one link of the set of links to achieve the similarity of the scores of each link of the set of links.

[0171] Embodiment B5. The method of Embodiment Bl, wherein the selection is based on at least one parameter associated with each of the plurality of available links, the at least one parameter including at least one of: a maximum allowed transmit (Tx) power; a usable bandwidth of the available link; a maximum Aggregated MAC Protocol Data Unit (A-MPDU) duration; a maximum Transmit Opportunity (TXOP) duration; at least one channel conditions of the available link; a number of Tx antennas; a number of receive (Rx) antennas; at least one physical (PHY) transmission feature; at least one hardware capability; and an increase in a load on the available link. Embodiment B6. The method of any one of Embodiments B1-B5, wherein selecting one of the first link or the set of links for the transmission comprises altering a property of at least one of the at least two links of the set of links.

Claims

Claims:

1. A first multilink device (MLD) (14a) configured to communicate with at least one second MLD (14b), the first MLD configured to, and / or comprising a radio interface (22) and / or comprising processing circuitry (24) configured to: assign a score to each link of a plurality of available links, the score being based on a communication capability of each link; assign an aggregation score to a set of links, the set of links including at least two links selected from the plurality of available links, the aggregation score being based on the scores of each link of the set of links and being assigned based on satisfaction of a condition; select, for a transmission, one of a first link of the plurality of available links or the set of links, the selection being based on the score of the first link or on the aggregation score of the set of links; and transmit using the selected one of the first link or the set of links.

2. The first MLD of Claim 1, wherein the first MLD is a first access point (AP) (14a) and the second MLD is one of a second AP (14b) or a non-AP station (non-AP ST A) (16).

3. The first MLD of any one of Claims 1 and 2, wherein the condition is based on a similarity of the scores of each link of the set of links.

4. The first MLD of Claim 3, wherein the first MLD is further configured to modify, based on the condition not being met, the communication capabilities of at least one link of the set of links to achieve the similarity of the scores of each link of the set of links.

5. The first MLD of any one of Claims 1-4, wherein the selection is based on at least one parameter associated with each of the plurality of available links, the at least one parameter including at least one of: a maximum allowed transmit (Tx) power; a usable bandwidth of the available link; a maximum Aggregated MAC Protocol Data Unit (A-MPDU) duration; a maximum Transmit Opportunity (TXOP) duration;at least one channel conditions of the available link; a number of Tx antennas; a number of receive (Rx) antennas; at least one physical (PHY) transmission feature; at least one hardware capability; and an increase in a load on the available link.

6. The first MLD of any one of Claims 1-5, wherein selecting one of the first link or the set of links for the transmission comprises altering a property of at least one of the at least two links of the set of links.

7. A method implemented in a first multilink device (MLD)access point (AP) configured to communicate with at least one second multilink device (MLD), the method comprising: assigning a score to each link of a plurality of available links, the score being based on a communication capability of each link (SI 34); assigning an aggregation score to a set of links, the set of links including at least two links selected from the plurality of available links, the aggregation score being based on the scores of each link of the set of links and being assigned based on satisfaction of a condition (SI 36); selecting, for a transmission, one of a first link of the plurality of available links or the set of links, the selection being based on the score of the first link or on the aggregation score of the set of links (SI 38); and transmitting using the selected one of the first link or the set of links (S140).

8. The method of Claim 7, wherein the first MLD is a first access point (AP) and the second MLD is at least one of a second AP and a non-AP station (non-AP STA).

9. The method of any one of Claims 7 and 8, wherein the condition is based on a similarity of the scores of each link of the set of links.

10. The method of Claim 9, further comprising modifying, based on the condition not being met, the communication capabilities of at least one link of the set of links to achieve the similarity of the scores of each link of the set of links.

11. The method of any one of Claims 7-10, wherein the selection is based on at least one parameter associated with each of the plurality of available links, the at least one parameter including at least one of: a maximum allowed transmit (Tx) power; a usable bandwidth of the available link; a maximum Aggregated MAC Protocol Data Unit (A-MPDU) duration; a maximum Transmit Opportunity (TXOP) duration; at least one channel conditions of the available link; a number of Tx antennas; a number of receive (Rx) antennas; at least one physical (PHY) transmission feature; at least one hardware capability; and an increase in a load on the available link.

12. The method of any one of Claims 7-11, wherein selecting one of the first link or the set of links for the transmission comprises altering a property of at least one of the at least two links of the set of links.

Images