Link negotiation including priority traffic

Abstract

The present disclosure relates to link negotiation including priority traffic. The invention describes methods, systems, and apparatuses for negotiating, by an access point (AP) multi-link device (MLD) and a non-AP MLD, a mapping between traffic streams and different links. The AP MLD can transmit an initial request for a first restricted mapping. The non-AP MLD can change to the first restricted mapping. The non-AP MLD can register one or more high-priority traffic streams, and can change to a second mapping that accommodates the high-priority traffic streams on at least one additional link. The non-AP MLD and the AP MLD can additionally exchange second and final mapping negotiation messages.

Description

[0001] Priority requirements

[0002] This patent application claims priority to U.S. Provisional Patent Application Serial No. 63 / 304,267 entitled “Link negotiation”, filed on January 28, 2022, the entire contents of which are incorporated herein by reference as fully and completely set forth herein. Technical Field

[0003] This application relates to wireless communication, including techniques for wireless communication between wireless stations and / or access points in a wireless networking system. Background Technology

[0004] The use of wireless communication systems is growing rapidly. Furthermore, wireless communication technology has evolved from voice communication alone to include the transmission of data such as the internet and multimedia content. A commonly used short- / mid-range wireless communication standard is Wireless Local Area Network (WLAN). Most modern WLANs are based on the IEEE 802.11 standard (and / or simply 802.11) and are sold under the Wi-Fi brand name. A WLAN network links one or more devices to a wireless access point, which in turn provides connectivity to the internet over a wider area.

[0005] In an 802.11 system, devices wirelessly connected to each other are called “sites,” “mobile stations,” “user equipment,” “user gear,” or simply STA or UE. A wireless site can be a wireless access point or a wireless client (and / or mobile station). An access point (AP), also known as a wireless router, acts as a base station for the wireless network. An AP transmits and receives radio frequency signals used to communicate with wireless client devices. An AP can also be coupled to the Internet via wired and / or wireless means. Wireless clients operating on an 802.11 network can be any device from a variety of sources, such as laptops, tablets, smartphones, smartwatches, or fixed devices such as desktop computers. This document refers to wireless client devices as user gear (and / or simply UE). Some wireless client devices are also collectively referred to herein as mobile devices or mobile stations (but as mentioned above, wireless client devices can also generally be stationary devices).

[0006] Mobile electronic devices can take the form of smartphones or tablets that users typically carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, an example being a smartwatch. Additionally, low-cost, low-complexity wireless devices designed for static or dynamic deployment are rapidly increasing as part of the development of the “Internet of Things”. In other words, the required devices are becoming increasingly diverse in terms of complexity, capabilities, traffic patterns, and other characteristics.

[0007] Some WLANs can utilize multi-link operation (MLO), for example, the concurrent use of multiple channels (e.g., links). APs and / or STAs with MLO capability can be referred to as multi-link devices (MLDs). For example, an AP with MLO capability can be referred to as an AP-MLD, and an MLO-capable STA that does not act as an AP can be referred to as a non-AP MLD. Improvements in this art are expected. Summary of the Invention

[0008] The implementation schemes described herein relate to systems, methods, apparatuses, and mechanisms for link mapping negotiation between AP MLDs and non-AP MLDs.

[0009] An Access Point (AP) Multilink Device (MLD) (AP MLD) can provide multiple links. The AP MLD can transmit an Initial Traffic Identifier (TID) to Link (T2L) mapping request for a first mapping between multiple TIDs and at least a subset of multiple links for communication with the non-AP MLD. According to this first mapping, a first TID can be mapped to a first number of links. The AP MLD can receive a request from the non-AP MLD to register the first TID as a high priority. In response to the request to register the first TID as a high priority, the AP MLD can change to a second mapping for communication with the non-AP MLD. According to this second mapping, the first TID can be mapped to a second number of links, greater than the first number.

[0010] A non-AP MLD can associate itself with an AP MLD using a default mapping between multiple traffic identifiers and multiple links. The multiple links may include different links connecting the AP MLD and the non-AP MLD. The non-AP MLD can receive an indication of a second mapping between the multiple traffic identifiers and multiple links from the AP MLD. According to this second mapping, at least a first traffic identifier can be mapped to fewer links than according to the default mapping. The non-AP MLD can determine that the first traffic identifier is of high priority. In response to the determination that the first traffic identifier is of high priority, the non-AP MLD can transmit a request to the AP MLD to register the first traffic identifier as high priority and can change to a third mapping. According to this third mapping, at least the first traffic identifier can be mapped to more links than according to the second mapping.

[0011] AP MLDs and non-AP MLDs can exchange additional messages with additional proposals and information related to link mapping negotiation.

[0012] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0013] A better understanding of the subject matter can be obtained by considering the following specific description of the implementation scheme in conjunction with the accompanying drawings.

[0014] Figure 1 An exemplary wireless communication system according to some implementation schemes is shown.

[0015] Figure 2 An exemplary simplified block diagram of a wireless device according to some implementation schemes is shown.

[0016] Figure 3 An exemplary WLAN communication system according to some implementation schemes is shown.

[0017] Figure 4 An exemplary simplified block diagram of a WLAN access point (AP) according to some implementation schemes is shown.

[0018] Figure 5 An exemplary simplified block diagram of a wireless station (STA) according to some implementation schemes is shown.

[0019] Figure 6 An exemplary simplified block diagram of a wireless node according to some implementation schemes is shown.

[0020] Figure 7 An example of an AP MLD according to some implementation schemes is shown.

[0021] Figure 8 An example of two MLDs communicating according to some implementation schemes is shown.

[0022] Figures 9 to 11 Exemplary mappings according to some implementation schemes are shown.

[0023] Figure 12 An exemplary method for link mapping negotiation by MLD according to some implementation schemes is shown.

[0024] Figure 13 An exemplary method for prioritizing traffic according to some implementation schemes is shown.

[0025] Figure 14 The following are illustrated according to some implementation schemes. Figure 12 The state diagram of the method.

[0026] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0027] acronym

[0028] Various acronyms are used throughout this patent application. The definitions of the most prominent acronyms that may appear throughout this patent application are as follows:

[0029] UE: User Equipment

[0030] AP: Access Point

[0031] STA: Wireless Station

[0032] TX: Transmission / Transmission

[0033] RX: Receive / Receive

[0034] MLD: Multi-link device

[0035] LAN: Local Area Network

[0036] WLAN: Wireless Local Area Network

[0037] RAT: Radio Access Technology

[0038] QoS: Quality of Service

[0039] the term

[0040] The following is a glossary of terms used in this disclosure:

[0041] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0042] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0043] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), mainframe computers, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (and / or combination of devices) having at least one processor that executes instructions from a memory medium.

[0044] Mobile device (and / or mobile station) — any of a variety of computer system devices that are mobile or portable and perform wireless communication using WLAN communication. Examples of mobile devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM (phones), and tablets such as iPads TM Samsung Galaxy TM Various other types of devices that include Wi-Fi, or both cellular and Wi-Fi capabilities, will fall into this category, such as laptops (e.g., MacBooks). TM ), portable gaming devices (e.g., Nintendo DS) TMPlayStation Portable TM Gameboy Advance TM iPhone TM Portable internet devices and other handheld devices, as well as wearable devices such as smartwatches, smart glasses, headphones, pendants, earbuds, etc. Generally, the term "mobile device" can be broadly defined as any electronic, computing, and / or communication device (and / or combination of devices) that is easily transportable by the user and capable of wireless communication using WLAN or Wi-Fi.

[0045] Wireless device (and / or wireless site) — Any of a variety of computer system devices that perform wireless communication using WLAN communication. As used herein, the term “wireless device” can refer to a mobile device as defined above or a stationary device such as a stationary wireless client or wireless base station. For example, a wireless device can be any type of wireless site in an 802.11 system, such as an access point (AP) or client site (STA or UE). Other examples include televisions, media players (e.g., Apple TV). TM Roku TM Amazon FireTV TM Google Chromecast TM (etc.), refrigerators, washing machines, thermostats, etc.

[0046] WLAN—The term “WLAN” has the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by WLAN access points and through which connectivity to the Internet is provided. Most modern WLANs are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” WLAN networks are different from cellular networks.

[0047] Processing element—refers to various specific implementations of digital circuitry that perform functions in a computer system. Furthermore, processing element can refer to various implementations of analog or mixed-signal (combination of analog and digital) circuitry that perform functions (and / or multiple functions) in a computer or computer system. Processing elements include, for example, circuits (such as integrated circuits (ICs), ASICs (Application-Specific Integrated Circuits), portions or circuits of individual processor cores), entire processor cores, individual processors, programmable hardware devices (such as field-programmable gate arrays (FPGAs)), and / or a large portion of a system comprising multiple processors.

[0048] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent "automatically" performed actions are not specified by the user, for example, not performed "manually," where, in the case of manual execution, the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, a user can invoke the automatic filling of a form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0049] Concurrency refers to the parallel execution or implementation of tasks, processes, signaling, messages, or programs in a manner that overlaps at least partially. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0050] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0051] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0052] Figures 1 to 2 —Wireless communication system

[0053] Figure 1 Exemplary (and simplified) wireless communication systems are shown, in which various aspects of this disclosure can be implemented. It should be noted that... Figure 1 The system described herein is only one example of a possible system, and embodiments of this disclosure can be implemented in any of a variety of systems as needed.

[0054] As shown in the figure, the exemplary wireless communication system includes a ("first") wireless device 102 communicating with another ("second") wireless device. The first wireless device 102 and the second wireless device 104 can perform wireless communication using any of a variety of wireless communication technologies, possibly including ranging wireless communication technologies.

[0055] As an option, the first wireless device 102 and the second wireless device 104 may perform ranging using wireless local area network (WLAN) communication technologies (e.g., IEEE 802.11 / Wi-Fi based communication) and / or WLAN-based wireless communication technologies. One or both of wireless devices 102 and 104 may also communicate via one or more additional wireless communication protocols, such as Bluetooth (BT), Bluetooth Low Energy (BLE), Near Field Communication (NFC), GSM, UMTS (WCDMA, TDSCDMA), LTE, LTE-A Advanced, NR, 3GPP 2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-MAX, GPS, etc.

[0056] Wireless device 102 and wireless device 104 can be any of a variety of wireless devices. As one possibility, one or more of wireless devices 102 and / or 104 can be substantially portable wireless user equipment (UE) devices, such as smartphones, handheld devices, wearable devices (such as smartwatches), tablets, motor vehicles, or virtually any type of wireless device. As another possibility, one or more of wireless devices 102 and / or wireless device 104 can be substantially stationary devices, such as set-top boxes, media players (e.g., audio or video equipment), game consoles, desktop computers, appliances, doors, access points, base stations, or any of a variety of other types of devices.

[0057] Each of wireless devices 102 and 104 may include wireless communication circuitry configured to enhance the performance of wireless communication, which may include various digital and / or analog radio frequency (RF) components, a processor configured to execute program instructions stored in memory, programmable hardware elements such as field-programmable gate arrays (FPGAs), and / or any of various other components. Wireless devices 102 and / or 104 may use any or all of these components to perform any of the method embodiments described herein, or any part thereof.

[0058] Each of wireless devices 102 and 104 may include one or more antennas for communicating using one or more wireless communication protocols. In some cases, one or more portions of the receive chain and / or transmit chain may be shared among multiple wireless communication standards; for example, the device may be configured to communicate using either Bluetooth or Wi-Fi with partially or fully shared wireless communication circuitry (e.g., using shared radio components or at least shared radio components). The shared communication circuitry may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Alternatively, the device may include independent transmit and / or receive chains (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate using it. As another possibility, the device may include one or more radios or radio components shared among multiple wireless communication protocols, as well as one or more radios or radio components specifically used by a single wireless communication protocol. For example, the device may include shared radio components for communicating using one or more of LTE, CDMA2000 1xRTT, GSM, and / or 5G NR, and separate radio components for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0059] As mentioned above, it can be combined Figure 1 The aspects of this disclosure are implemented using a wireless communication system. For example, a wireless device (e.g., either wireless device 102 or 104) may be configured to perform methods for: robust discovery of a new AP in an Access Point (AP) MLD, robust link addition to an AP MLD, AP beacon mode when an AP is added to or removed from an AP MLD, robust BSS transition management (BTM) signaling for guiding non-AP MLDs to the optimal AP MLD and the most suitable AP, and privacy improvements for associated non-AP MLDs.

[0060] Figure 6An exemplary wireless device 100 (e.g., corresponding to wireless device 102 and / or wireless device 104) that can be configured for use in conjunction with various aspects of this disclosure is illustrated. Device 100 can be any of a variety of types of devices and can be configured to perform any of a variety of types of functions. Device 100 can be a substantially portable device or a substantially fixed device, and may include any of a variety of types of devices. Device 100 can be configured to perform one or more ranging wireless communication techniques or features, such as any techniques or features subsequently shown and / or described herein with respect to any or all of the accompanying drawings.

[0061] As shown, device 100 may include processing element 101. The processing element may include or be coupled to one or more memory elements. For example, device 100 may include one or more storage media (e.g., memory 105), which may include any type of memory and be usable for any function. For example, memory 105 may be RAM used as system memory for processing element 101. Other types and functions are also possible.

[0062] Additionally, device 100 may include wireless communication circuitry 130. The wireless communication circuitry may include any of a variety of communication elements (e.g., antennas for wireless communication, analog and / or digital communication circuitry / controllers, etc.) and may enable the device to perform wireless communication using one or more wireless communication protocols.

[0063] It should be noted that in some cases, such as when processing element 101 is used, wireless communication circuitry 130 may include its own processing element (e.g., a baseband processor). For example, processing element 101 may be an "application processor" whose primary function may be to support application layer operations in device 100, while wireless communication circuitry 130 may be a "baseband processor" whose primary function may be to support baseband layer operations in device 100 (e.g., to facilitate wireless communication between device 100 and other devices). In other words, in some cases, device 100 may include multiple processing elements (e.g., it may be a multiprocessor device). Other configurations utilizing a multiprocessor architecture (e.g., alternatives to or other than the application processor / baseband processor configuration) are also possible.

[0064] Depending on the intended function of device 100, device 100 may additionally include any of a variety of other components (not shown) for implementing the device function, which may also include processing elements and / or memory elements (e.g., audio processing circuitry), one or more power supply elements (which may depend on battery power and / or external power), user interface elements (e.g., display, speaker, microphone, camera, keyboard, mouse, touch screen, etc.), and / or any of a variety of other components.

[0065] Components of device 100, such as processing element 101, memory 105, and wireless communication circuitry 130, may be operatively coupled via one or more interconnect interfaces, which may include any of a variety of types of interfaces, and possibly combinations of multiple types of interfaces. As an example, a USB High Speed ​​Chip-to-Chip (HSIC) interface may be provided for chip-to-chip communication between processing elements. Alternatively (and / or in addition), any of the following communication interfaces may be used for communication between various device components: Universal Asynchronous Receiver / Transmitter (UART), Serial Peripheral Interface (SPI), Internal Integrated Circuit (I2C), System Management Bus (SMBus), and / or various other communication interfaces. Other types of interfaces (e.g., on-chip interfaces for communication within processing element 101, peripheral interfaces for communication with peripheral components inside or outside device 100, etc.) may also be provided as part of device 100.

[0066] Figure 3 —WLAN system

[0067] Figure 3 An exemplary WLAN system according to some embodiments is illustrated. As shown, the exemplary WLAN system includes multiple wireless client sites or devices (e.g., STAs or User Equipment (UEs)) 106 configured to communicate with an access point (AP) 112 via a wireless communication channel 142. AP 112 may be a Wi-Fi access point. AP 112 may communicate with one or more other electronic devices (not shown) and / or another network 152 (such as the Internet) via wired and / or wireless communication channels 150. Additional electronic devices, such as remote devices 154, may communicate with components of the WLAN system via network 152. For example, remote device 154 may be another wireless client site, a server associated with an application running on one of the STAs 106, etc. The WLAN system may be configured to operate according to any of a variety of communication standards, such as various IEEE 802.11 standards. In some embodiments, at least one wireless device 106 is configured to communicate directly with one or more adjacent mobile devices without using access point 112.

[0068] Furthermore, in some implementations, wireless device 106 (which may be an exemplary specific implementation of device 100) may be configured to perform methods for: robust discovery of new APs in an access point (AP) MLD, robust link addition to an AP MLD, AP beacon mode when an AP is added to or removed from an AP MLD, robust BSS transition management (BTM) signaling for guiding non-AP MLDs to the best AP MLD and the most suitable AP, and privacy improvements for associated non-AP MLDs.

[0069] Figure 4 —Access Point Diagram

[0070] Figure 4 An exemplary block diagram of access point (AP) 112 is shown, which may be Figure 4 This is one possible exemplary embodiment of the device 100 shown. It should be noted that... Figure 4 The block diagram of the AP is only one example of a possible system. As shown, AP 112 may include a processor 204 capable of executing program instructions for AP 112. Processor 204 may also be (directly or indirectly) coupled to memory management unit (MMU) 240 or other circuitry or devices, which may be configured to receive addresses from processor 204 and translate these addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0071] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide internet access to multiple devices, such as mobile device 106. For example, network port 270 (and / or additional network ports) may be configured to couple to a local network, such as a home network or a business network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to additional networks such as the internet.

[0072] AP 112 may include at least one antenna 234, which may be configured to operate as a wireless transceiver and further configured to communicate with mobile device 106 via wireless communication circuitry 230. Antenna 234 communicates with wireless communication circuitry 230 via communication link 232. Communication link 232 may include one or more receive links, one or more transmit links, or both. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, in small cell scenarios where the AP coexists with a base station, or in other situations where it may be desirable for AP 112 to communicate via various different wireless communication technologies, wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, LTE, LTE-A Advanced, GSM, WCDMA, CDMA2000, etc.

[0073] Furthermore, in some implementations, as further described below, AP 112 may be configured to perform methods for: robust discovery of new APs in an Access Point (AP) MLD, robust link addition to an AP MLD, AP beacon mode when an AP is added to or removed from an AP MLD, robust BSS transition management (BTM) signaling for directing non-AP MLDs to the best AP MLD and the most suitable AP, and privacy improvements for associated non-AP MLDs.

[0074] Figure 5 —Client Site Diagram

[0075] Figure 5 An exemplary simplified block diagram of client site 106 is shown, which can be Figure 4 This is one possible exemplary embodiment of the device 100 shown. According to various embodiments, the client site 106 may be a user equipment (UE) device, a mobile device or mobile station, and / or a wireless device or wireless site. As shown, the client site 106 may include a system-on-a-chip (SOC) 300, which may include components for various purposes. The SOC 300 may be coupled to various other circuitry of the client site 106. For example, the client site 106 may include various types of memory (e.g., including NAND flash memory 310), connector interfaces (I / F) (and / or docking stations) 320 (e.g., for coupling to computer systems, taskbars, charging stations, etc.), a display 360, cellular communication circuitry (e.g., cellular radio components) 330 (such as for 5G NR, LTE, GSM, etc.), and short-to-medium range wireless communication circuitry (e.g., Bluetooth). TMand WLAN radio components) 329 (e.g., Bluetooth) TM (And WLAN circuitry). Client site 106 may also include one or more smart cards 315 incorporating SIM (Subscriber Identity Module) functionality, such as one or more UICCs (One or more Universal Integrated Circuit Cards). Cellular communication circuitry 330 may be coupled to one or more antennas, such as antennas 335 and 336 as shown. Short-to-medium-range wireless communication circuitry 329 may also be coupled to one or more antennas, such as antennas 337 and 338 as shown. Alternatively, in addition to or instead of being coupled to antennas 337 and 338, short-to-medium-range wireless communication circuitry 329 may be coupled to antennas 335 and 336. The short-to-medium-range wireless communication circuitry 329 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams in a configuration such as Multiple-Input Multiple-Output (MIMO). Some or all of the components of short-to-medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may be used for ranging communication, for example, ranging communication using WLAN communication, Bluetooth communication, and / or cellular communication.

[0076] As shown, the SOC 300 may include one or more processors 302 and display circuitry 304. The processors execute program instructions for client site 106, and the display circuitry performs graphics processing and provides display signals to display 360. The SOC 300 may also include motion sensing circuitry 370, which may detect motion of client site 106, for example, using a gyroscope, accelerometer, and / or any of various other motion sensing components. One or more processors 302 may also be coupled to a memory management unit (MMU) 340 and / or other circuitry or devices (such as display circuitry 304, cellular communication circuitry 330, short-range wireless communication circuitry 329, connector interface (I / F) 320, and / or display 360). The MMU may be configured to receive addresses from one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some implementations, the MMU 340 may be included as part of the processor 302.

[0077] As described above, client station 106 can be configured to directly communicate wirelessly with one or more adjacent client stations. Client station 106 can be configured to communicate according to a WLAN RAT to enable communication in applications such as... Figure 3 Communication in the WLAN network shown or as Figure 1 The distance measurement shown.

[0078] As described herein, client site 106 may include hardware and software components for implementing the features described herein. For example, processor 302 of client site 106 may be configured to implement some or all of the features described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (and / or in addition), processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Alternatively (and / or in addition), in conjunction with one or more of other components 300, 304, 306, 310, 315, 320, 329, 330, 335, 336, 337, 338, 340, 350, 360, 370, processor 302 of UE 106 may be configured to implement some or all of the features described herein.

[0079] Furthermore, as described in this invention, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.

[0080] Furthermore, as described herein, both the cellular communication circuit 330 and the short-range wireless communication circuit 329 may include one or more processing elements. In other words, one or more processing elements may be included in either the cellular communication circuit 330 or the short-range wireless communication circuit 329. Thus, each of the cellular communication circuit 330 and the short-range wireless communication circuit 329 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330 and the short-range wireless communication circuit 329, respectively. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330 and the short-range wireless communication circuit 329.

[0081] Figure 6 —Wireless Node Diagram

[0082] Figure 6 A possible block diagram of wireless node 107 is shown, which can be Figure 5One possible exemplary implementation of the device 106 shown is illustrated. As shown, the wireless node 107 may include a system-on-a-chip (SOC) 400, which may include components for various purposes. For example, as shown, the SOC 400 may include one or more processors 402 capable of executing program instructions for the wireless node 107 and display circuitry 404 capable of performing graphics processing and providing display signals to a display 460. The SOC 400 may also include motion sensing circuitry 470, which may detect motion of the wireless node 107, for example, using a gyroscope, accelerometer, and / or any of various other motion sensing components. One or more processors 402 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from one or more processors 402 and translate these addresses into locations in memory (e.g., memory 406 and read-only memory (ROM) 450, flash memory 410). The MMU 440 may be configured to perform memory protection and page table translation or setup. In some implementations, the MMU 440 may be included as part of the processor 402.

[0083] As shown in the figure, the SOC 400 can be coupled to various other circuits of the wireless node 107. For example, the wireless node 107 may include various types of memory (e.g., including NAND flash memory 410), connector interface 420 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 460, and wireless communication circuitry 430 (e.g., for 5G NR, LTE, LTE-A, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.).

[0084] Wireless node 107 may include at least one antenna, and in some embodiments, may include multiple antennas 435 and 436 for performing wireless communication with a base station and / or other devices. For example, wireless node 107 may use antennas 435 and 436 to perform wireless communication. As described above, wireless node 107 may be configured in some embodiments to perform wireless communication using a variety of wireless communication standards or radio access technologies (RATs).

[0085] The wireless communication circuit 430 may include a Wi-Fi logic component 432, a cellular modem 434, and a Bluetooth logic component 439. The Wi-Fi logic component 432 enables the wireless node 107 to perform Wi-Fi communication (e.g., on an 802.11 network). The Bluetooth logic component 439 enables the wireless node 107 to perform Bluetooth communication. The cellular modem 434 may be able to perform cellular communication according to one or more cellular communication technologies. Some or all of the components of the wireless communication circuit 430 may be used for ranging communication, for example, utilizing WLAN communication, Bluetooth communication, and / or cellular communication.

[0086] As described herein, wireless node 107 may include hardware and software components for implementing embodiments of this disclosure. For example, one or more components of wireless communication circuitry 430 (e.g., Wi-Fi logic component 432) of wireless node 107 may be configured to implement some or all of the methods described herein, for example, by a processor executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), a processor configured as an FPGA (Field Programmable Gate Array), and / or using dedicated hardware components that may include ASICs (Application-Specific Integrated Circuits).

[0087] Figures 7 to 8 —Multi-link device (MLD) operation

[0088] Various communication standards (such as IEEE 802.11be) may include multi-link device (MLD) capabilities. In current implementations, access point (AP) MLD nodes can manage their associated APs. Therefore, AP MLD nodes can modify, add, and / or remove associated APs to increase capacity, manage Basic Service Set (BSS) interference and coverage, including switching APs to operate in channels with minimal interference, and / or manipulating associated non-AP MLD nodes to operate on the APs and / or AP MLD nodes with optimal performance.

[0089] Figure 7 An AP MLD 112 according to some embodiments is shown. This AP MLD can operate any number of auxiliary APs, such as APs 712a, 712b, 712c, and 712d in the illustrated example. Auxiliary APs can operate on any frequency band across a variety of frequency bands. Auxiliary APs can operate on different frequency ranges (e.g., channels) within the same frequency band or on different frequency bands. In the illustrated example, AP 712a can operate in the 2.4 GHz band, AP 712b can operate in the 5 GHz band, and APs 712c and AP 712d can operate in the 6 GHz band. Other arrangements (e.g., within the same and / or other frequency bands) are possible.

[0090] AP MLDs can provide auxiliary APs from a single physical device (e.g., a single shared enclosure) and potentially using the same antenna. In some implementations, AP MLDs can provide APs from multiple different devices (e.g., a first device can provide one or more APs, a second device can provide different one or more APs, etc.). In some implementations, the various auxiliary APs can be spatially separated (e.g., beams in different directions, using different antennas with a shared enclosure (e.g., antennas of the same physical device) and / or different antennas of different devices, etc.).

[0091] In some implementations, spatially separated auxiliary APs can operate on the same (or overlapping) channels.

[0092] Figure 8 The transmission MLD A (e.g., 112 or 106) communicating with the receiving MLD B (e.g., 112 or 106) is shown according to some embodiments.

[0093] As shown in the figure, an MLD can operate multiple (e.g., three each in the illustrated example) attached STAs. Each corresponding STA on the MLD can communicate via a corresponding link. For example, STA A1 can communicate with STA B1 via link 1, etc.

[0094] Data packets / frames with different Traffic Identifiers (TIDs) can be exchanged via the same and / or different links (e.g., via corresponding STAs). Transmit MLDs and receive MLDs can be buffered with different TIDs, for example, in TX buffers / queues and RX buffers / queues, respectively.

[0095] The relationship between a TID and a link can be referred to as a mapping (e.g., a TID-to-link or T2L mapping). As will be understood, many mappings are possible, including, for example, one-to-one, one-to-many, many-to-one, and / or many-to-many mappings. In the illustrated example, TIDs 1 through 3 are mapped to link 2, and TIDs 2 through 4 are mapped to link 3.

[0096] The packet (e.g., frame or other information unit) can be transmitted via one or more links mapped to by the packet's TID. For example, a packet for TID 2 can be transmitted via either or both of link 2 and / or link 3. The transmit MLD can be selected from one or more mapping links based on any of a variety of factors, such as the first available link, minimum energy usage, highest probability of successful reception, channel conditions, input from the receive MLD, and / or any combination of these and / or other factors (e.g., trade-offs between them). In some embodiments, the transmit AP MLD can be transmitted on all mapping links used for the TID, and the receive non-AP MLD can be received on any one or more mapping links. In some embodiments, the transmit non-AP MLD can be transmitted on any one or more mapping links used for the TID, and the receive non-AP MLD can be monitored for potential reception on all mapping links.

[0097] A link is considered enabled if at least one TID is mapped to an established link, and a link is considered disabled if no TID is mapped to an established link. If a link is enabled, it can be used for frame switching, but only for data frames and management frames corresponding to the mapped TID. If a link is disabled, it may not be used for frame switching, including some management frame switching.

[0098] TIDs can be mapped to at least one establishment link, for example, unless admission control is used.

[0099] In some implementations, the TID-to-link mapping can be unidirectional; for example, a TID mapped to an uplink (UL) link may be different from a TID mapped to the corresponding downlink (DL) link. In some implementations, the mapping can be bidirectional; for example, a TID may be mapped to the same link used for UL as the link used for DL, and vice versa.

[0100] In some implementations, by default, all TIDs can be mapped to all established links used for both UL and DL. Therefore, all established links can be enabled. The default TID-to-link mapping mode can be used in the following situations: the AP MLD and non-AP MLD do not negotiate different mappings; the AP MLD and non-AP MLD cannot agree on any alternative mapping; or... APMLD and non-AP MLD have disconnected from previous protocols, for example, for alternative mappings.

[0101] In some implementations, TID-to-link mapping negotiation may occur, for example, via an association frame or via a TID-to-link mapping handshake during the multi-link (ML) establishment process. For instance, an AP MLD or a non-AP MLD may initiate negotiation, and the AP MLD or non-AP MLD may accept or reject a TID-to-link mapping request from a peer. Furthermore, if a TID-to-link mapping is not accepted, the peer may propose a preferred / alternative mapping.

[0102] Affiliate STAs can include various layers, such as the Media Access Control (MAC) and / or Physical (PHY) layers, and various other possibilities. Affiliate STAs of an AP MLD can use different Basic Service Sets (BSS) and / or different BSS identifiers (BSSIDs), such as BSSID 1 to BSSID 3. It should be understood that any number of affiliated STAs can be used in any combination of frequency bands. For example, an MLD can operate multiple affiliated STAs in one frequency band and / or may not operate any affiliated STAs in any frequency band. A non-AP MLD can operate STAs of some or all of the APs corresponding to the AP MLD, or STAs of APs not corresponding to the AP MLD. Affiliate STAs can use different addresses.

[0103] A non-AP MLD can provide auxiliary STAs from a single physical device (e.g., a single shared enclosure) and potentially using the same antenna. In some embodiments, a non-AP MLD can provide STAs from multiple different devices (e.g., a first device can provide one or more STAs, a second device can provide different one or more STAs, etc.). In some embodiments, the various auxiliary STAs can be spatially separated (e.g., beams in different directions, using different antennas with a shared enclosure (e.g., antennas of the same physical device) and / or different antennas of different devices, etc.).

[0104] Various affiliated STAs can communicate concurrently / simultaneously. For example, STA A1 can exchange uplink and / or downlink data with STA B1 on a first link, while STA A2 can exchange uplink and / or downlink data with STA B2 on a second link, and so on. It should be understood that such concurrent communication may include (e.g., different) data being exchanged on different links at the same time, overlapping times, and / or different times. The number of APs and / or STAs may change over time.

[0105] Figures 9 to 11 —Example Mapping

[0106] Figures 9 to 11 Examples of various types of mappings are shown. It should be understood that an AP MLD can use mappings that are the same as or different from different non-AP MLDs (e.g., the same or different types). For example, an AP MLD can use a mapping with a first non-AP MLD and a second mapping with a second non-AP MLD.

[0107] Figure 9 An example of a mapping type, where all TIDs are mapped to all links (e.g., all TIDs to all links (AT2AL) mapping), is shown according to some implementations. According to some implementations, the AT2AL mapping can be used as the default or initial mapping. As shown, TIDs 0 through 3 (and any additional TIDs) are mapped to all links.

[0108] AT2AL mapping is perhaps the most flexible for non-AP MLDs. For example, a non-AP MLD can dynamically select the link best suited for DL ​​and UL data communication. However, for AP MLDs, AT2AL mapping can struggle to balance traffic load across multiple links (e.g., associated with multiple non-AP MLDs). For instance, due to the different link selections made by various non-AP MLDs, some links may be heavily loaded (e.g., at a given time or throughout the entire duration), while others may be lightly loaded.

[0109] Figure 10An example of a type of mapping, according to some implementations, in which all TIDs are mapped to a (e.g., the same) subset of all links (e.g., all TIDs to a subset of links (AT2LS) mapping), is shown. As shown, TIDs 0 to TID3 (and any additional TIDs) are mapped to links 1 and 2; no TIDs are mapped to link 3.

[0110] AT2LS mapping can be beneficial for AP MLDs to balance traffic load across multiple links. For example, an AP MLD can move some non-AP MLDs from busy links to idle links by disabling them from using busy links (e.g., by moving these non-AP MLDs to AT2LS mapping).

[0111] However, AT2LS mapping can be less flexible for non-AP MLDs. For example, some non-AP MLDs may be assigned to links that are not suitable for them (e.g., links with significant coexistence interference). Similarly, in the case of AT2LS mapping, if the assigned link is blocked (e.g., due to a non-AP MLD or a change in user location), the non-AP MLD may not quickly move high-priority traffic from one link to another.

[0112] Figure 11 Examples of mapping types according to some implementation schemes are shown, where one or more TIDs are mapped to a subset of all links, and one or more TIDs are mapped to all links (e.g., Enhanced Link Subset (EAT2LS) mapping). As shown, TIDs 0 through 1 are mapped to links 1 and 2; TIDs 2 through 3 are mapped to links 1 through 3. Any additional TIDs may be mapped to all links or subsets of links (e.g., the same or potentially different subsets, such as links 1 and 3 (but not link 2) etc.).

[0113] EAT2LS mapping allows AP MLDs to balance traffic load by moving low-priority traffic from busy links to idle links. For example, a non-AP MLD using EAT2LS to prevent non-AP MLDs from using busy links for low-priority traffic can free up some time / frequency resources on busy links used for high-priority traffic by other non-AP MLDs. Furthermore, EAT2LS mapping allows non-AP MLDs the flexibility to use all links for high-priority traffic.

[0114] It should be understood that Figures 9 to 11The mappings shown are examples and other mappings are possible. For example, for a non-AP MLD, some TIDs can be mapped to a first subset of links, other TIDs can be mapped to a second subset (e.g., including more, fewer, and / or different links), and other additional TIDs can be mapped to all links, etc.

[0115] Figure 12 —Mapping negotiation

[0116] In some implementations, the AP MLD requests AT2LS mapping, for example, to facilitate multi-link traffic load balancing across non-AP MLDs and / or other non-APs. However, non-AP MLDs may prefer to use AT2AL or EAT2LS mapping for optimal flexibility, such as to better support high-priority traffic. Therefore, a good TID-to-link mapping negotiation strategy can balance the benefits of both AP MLDs and non-AP MLDs.

[0117] The implementation schemes described herein provide systems, methods, and mechanisms for performing link mapping negotiation for AP and non-AP MLDs. For example, according to Figure 12 In the implementation scheme, AP MLD and non-AP MLD can exchange various messages to negotiate link mapping.

[0118] Figure 12 Aspects of the method can be implemented by an AP MLD communicating with a non-AP MLD. The AP MLD and / or non-AP MLD may be shown and described as in the various figures herein, or more generally, may be shown and described as needed in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures above. For example, the processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements. For example, one or more processors (or processing elements) (e.g., processors 101, 204, 302, 402, 432, 434, 439, baseband processors, processors associated with communication circuits such as 130, 230, 232, 329, 330, 430, etc., and various possibilities) may cause a wireless device, STA, UE, non-AP MLD, and / or AP MLD or other device to perform this method element.

[0119] It should be noted that, although described in a manner relating to the communication technologies and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents. Figure 12 This description includes at least some elements of the method, but it is not intended to limit this disclosure. Figure 12 Various aspects of the method can be used in any suitable wireless communication system as needed. Similarly, although described in a manner relevant to non-AP MLDs... Figure 12 The method includes elements, but this description is not intended to limit this disclosure, and Figure 12 The method can be used by STAs that are not MLDs, as needed.

[0120] Among other devices, the method shown can be used in conjunction with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method can operate as follows.

[0121] According to some implementations, the non-AP MLD 106 and AP MLD 112 are within communication range and can know (e.g., independently) the default mapping (1202). For example, the default mapping can be an AT2AL mapping and various other possibilities. The default mapping can be set by a wireless standard (e.g., 802.11, etc.) and / or can be broadcast by the AP MLD or otherwise signaled (e.g., in a beacon frame, etc.). Therefore, the non-AP MLD can become aware of the default mapping based on receiving an indication of the default mapping from the AP MLD.

[0122] According to some implementations, the AP MLD can determine the AP-preferred mapping (1204). The AP MLD can select the AP-preferred mapping based on any combination of factors, such as to balance the load of the link across the AP MLD. The AP-preferred mapping may be specific to non-AP MLDs, or may be preferred for multiple non-AP MLDs (e.g., all non-AP MLDs or a subset of non-AP MLDs within the communication range of the AP MLD) (e.g., by AP MLD). This determination can occur before, simultaneously with, or after the first communication between a non-AP MLD and the AP MLD (e.g., in 1206). The determination can be updated and / or revisited periodically or as needed (e.g., based on changing load and / or radio link conditions).

[0123] In some implementations, the AP MLD may broadcast an indication of the AP-preferred mapping. Non-AP MLDs may receive such indications and thus know the AP-preferred mapping before being associated with the AP MLD.

[0124] The AP-preferred mapping can be the same as or different from the default mapping. For example, the AT2LS mapping can be the AP-preferred mapping as well as various other possibilities.

[0125] The AP MLD may broadcast (e.g., or transmit to non-AP MLDs) the AP-preferred mapping along with a reason code and / or additional information elements (e.g., to justify or explain the AP-preferred mapping). For example, the AP MLD may include a reason code indicating "load balancing," etc. Furthermore, the AP MLD may include BSS load elements and / or high-efficiency (HE) BSS load elements, which may indicate the number of associated non-AP STAs, the number of associated HE STAs, and channel utilization information, etc. The AP MLD may also include a reason code indicating "guaranteed low latency" and low-latency support elements, which may indicate the number of associated low-latency STAs and their guaranteed service intervals, etc.

[0126] According to some implementations, AP MLDs and non-AP MLDs can establish communication / association with each other (1206). For example, a non-AP MLD can transmit association requests, beacons, probes, or similar messages to the AP MLD to initiate communication. In some implementations, messages from a non-AP MLD can confirm information about the default and / or AP-preferred mappings received by the non-AP MLD.

[0127] AP MLDs can respond positively to non-AP MLDs, for example, using associated responses, beacon responses, probe responses, or similar messages. Positive responses from AP MLDs can establish communication associations between devices.

[0128] In some implementations, the AP MLD may indicate the AP-preferred mapping in response to a non-AP MLD. The non-AP MLD may transmit acknowledgment of such indication to the AP MLD. In some implementations, the AP MLD may select the AP-preferred mapping in response to a message from a non-AP MLD (e.g., an association request, etc.). Therefore, the AP MLD may select the AP-preferred mapping in part based on messages from non-AP MLDs.

[0129] AP MLDs and non-AP MLDs may communicate with either the default or AP-preferred mapping. For example, if the AP has indicated (e.g., in a broadcast message as discussed in 1204 and / or in a response message as discussed in 1206) an AP-preferred mapping, the AP MLD and non-AP MLDs may initially use the AP-preferred mapping. However, if the AP has not yet indicated an AP-preferred mapping, the AP MLD and non-AP MLDs may initially use the default mapping. In some embodiments, if a non-AP MLD has not yet acknowledged such an indication of an AP-preferred mapping, the AP MLD and non-AP MLDs may initially use the default mapping.

[0130] According to some implementations, if the AP MLD and non-AP MLDs initially use a default mapping and this default mapping differs from the AP-preferred mapping, the AP MLD may transmit an initial request (1208) for the AP-preferred mapping to the non-AP MLD. The non-AP MLD may receive this request. Such an initial request may be transmitted at any time after (or simultaneously with) association. For example, the initial request may be transmitted after association, or immediately whenever the AP MLD determines that the AP-preferred mapping differs from the default mapping (e.g., in response to load changes on one or more links, etc.). The initial request for the AP-preferred mapping may be transmitted as a T2L negotiation request. In some implementations, the T2L negotiation request may be transmitted as a multicast message, for example, having addresses or identifiers (IDs) of multiple non-AP MLDs (e.g., these multiple non-AP MLDs are requested to use the AP-preferred mapping). Alternatively, the T2L negotiation request may be transmitted as a unicast message to a single non-AP MLD.

[0131] As described above, the AP MLD can multicast or unicast the AP preferred mapping together with the cause code and / or additional information elements, for example, to prove and / or explain the AP preferred mapping.

[0132] In some implementations, the AP MLD may start a counter-proposal timer simultaneously with the transmission of an initial request for an AP-preferred mapping. A non-AP MLD may also start a counter-proposal timer in response to receiving a request. Such counter-proposal timers are operable to allow a peer (e.g., a non-AP MLD in this example) time to respond to a T2L negotiation request. If a peer (e.g., a non-AP MLD) does not respond to a T2L negotiation request with a counter-proposal or other message indicating a rejection of the proposed mapping (e.g., the AP-preferred mapping), the proposed mapping may be applied (via both MLDs) when the counter-proposal timer expires.

[0133] In some implementations, a response can be anticipated before the counterproposal timer expires. Therefore, a non-AP MLD can be configured to respond using a T2L negotiation response before the counterproposal timer expires, which indicates: 1) accepting the AP-proposed mapping; or 2) rejecting it with a counterproposal. The counterproposal includes: 1) no mapping change; 2) a fallback to the default mapping; or 3) an alternative mapping (e.g., different from the current mapping, the default mapping, or the AP-proposed mapping).

[0134] According to some implementations, in certain situations, the AP-preferred mapping (1210) can be applied to both the AP MLD and non-AP MLD. For example, if the AP-preferred mapping is an EAT2LS mapping, the non-AP MLD can take an EAT2LS mapping request from the AP MLD and can transmit / receive allowed TIDs on all links. Prior to applying the EATLS mapping, the non-AP MLD can also be requested to register high-priority TIDs (e.g., or priority information about some or all TIDs can be provided). For example, the AP MLD can provide an indication that the non-AP MLD should register priority information (e.g., using the AP-preferred mapping or in a separate message).

[0135] According to some implementations, a non-AP MLD can determine whether a mapping proposed by the AP MLD (e.g., an AP-preferred mapping) is appropriate and / or prioritize one or more TIDs (1212). These determinations can be made at any time. For example, they can be made in response to implementing an AP-preferred mapping (e.g., in 1206), in response to receiving a request for an AP-preferred mapping (e.g., in 1208, for example, when a counter-proposal timer is running), periodically, and / or in response to detecting changes in conditions (e.g., which TIDs are active, the amount of traffic on one or more active TIDs, congestion levels, determinations related to whether a TID meets its Quality of Service (QoS) objectives, latency, throughput, congestion of any links, and / or other conditions).

[0136] As a possibility, a non-AP MLD can determine the priority of any active TID, for example, whether any TID is considered high priority. Such determination can be made for any or all individual TIDs and / or for any group of TIDs. This determination can be based on the TID's QoS characteristics, the application or application type associated with the TID, the signaling type associated with the TID, and / or other factors. Exemplary QoS characteristics may include: minimum service interval, maximum service interval, minimum data rate, and delay limits.

[0137] For example, a non-AP MLD can perform a binary determination of whether a TID meets the definition of high priority. As a possibility, TIDs 4 through 7 can be considered high priority; other TIDs can not be considered high priority. Alternatively, a non-AP MLD can determine the priority level of a TID according to any desired priority level scheme (e.g., high, medium, and low; priority levels 1 through 10, etc.).

[0138] In some implementations, the mapping from TID to traffic can be fixed. For example, TID 0 to TID 3 can be mapped to background and best traffic. TID 4 and TID 5 can be mapped to video traffic. TID 6 and TID 7 can be mapped to voice traffic. Generally, larger TID values ​​are mapped to higher priority traffic.

[0139] Non-AP MLDs may consider the applicability of mapping proposals (e.g., AP-preferred mappings). For example, a non-AP MLD may consider a proposal based on the priority of the TID. For example, a non-AP MLD may determine whether a TID is mapped to a sufficient number of links or a set of links for the corresponding priority level. Such determinations can be made in various ways. As one possibility, if a high-priority TID (e.g., a priority level above a threshold level) is mapped to fewer than a threshold number of links (e.g., the threshold could be all links or any desired number), a non-AP MLD may determine that the high-priority TID may not be mapped to a sufficient number of links. As another possibility, different priority levels may be associated with different thresholds (e.g., a high-priority TID has a threshold of at least 3 links, a medium-priority TID has a threshold of at least 2 links, etc.). As yet another possibility, different links may be evaluated as having different qualities. For example, a first link may be considered to be of higher quality than a second link, and a non-AP MLD may consider that a high-priority TID (e.g., a priority above a threshold) must be mapped to a threshold number of links, each with a quality above the corresponding threshold. Similarly, different priority levels of TIDs can be associated with different threshold numbers of links and / or different link quality thresholds. In some implementations, TIDs with priorities below the threshold may not be associated with the number of links and / or quality thresholds, or a basic threshold may be used (e.g., at least one low-quality link may be considered sufficient for a low-priority TID, etc.).

[0140] To determine whether a mapping proposal is appropriate, a non-AP MLD can, for example, determine whether each active TID is mapped to a sufficient number of links or a set of links based on the priority of the TID and the number and / or quality of links mapped for each TID.

[0141] If at least one TID is not mapped to a sufficient number of links or a set of links, the non-AP MLD may determine that the mapping proposal is unsuitable. In some implementations, the non-AP MLD may store information about TIDs that have not been mapped to a sufficient number of links due to one or more reasons why the proposal is considered unsuitable. One or more reasons may be provided to the AP MLD, for example, at the time of determination or at a future time. For example, the non-AP MLD and the AP MLD may have a shared (e.g., normalized) set of reason codes that can be used to indicate such reasons or other information. The reasons and / or other information may be determined by the AP MLD in a manner that is useful for selecting further mapping proposals.

[0142] In some implementations, if at least one TID is not mapped to a sufficient number of links or sets of links, the non-AP MLD may further determine one or more suitable mappings, for example, for use in counter-proposals against the AP MLD. As discussed above, one or more suitable mappings may be determined based on TID priority, link quality, and thresholds for priority, quality, and number of links. For example, the non-AP MLD may determine one or more mappings that result in each TID being mapped to a sufficient number of links / sets of links. In some implementations, the non-AP MLD may determine mappings in which each TID is mapped to a minimum number and / or quality of links sufficient for its respective priority.

[0143] If a TID is mapped to a sufficient number of links or sets of links (e.g., if the respective corresponding TIDs are mapped to a sufficient number of links or sets of links), the non-AP MLD can determine that the mapping proposal is appropriate. In response to determining that the mapping proposal is appropriate, the non-AP MLD can adopt / implement the mapping proposal. For example, if the non-AP MLD does not have any high-priority traffic, it can adopt the AP-preferred mapping (e.g., an AT2LS or EAT2LS mapping request from the AP MLD). In other words, the non-AP MLD can apply the AP-preferred mapping for these TIDs. The non-AP MLD can apply the AP-preferred mapping when the counter-proposal timer expires. The AP MLD can also apply the AP-preferred mapping simultaneously (e.g., when the counter-proposal timer expires).

[0144] It should be understood that, according to some implementation schemes, if the non-AP ML deems the AP-preferred mapping appropriate, then Figure 12Some or all of the subsequent parts may be omitted or delayed indefinitely. For example, an AP-preferred mapping may be used by both the AP MLD and non-AP MLDs until either MLD determines that the AP-preferred mapping is no longer suitable (e.g., due to changes in the TID, load, or conditions of the activity as described above). If either MLD determines that the current mapping (e.g., the AP-preferred mapping or any mapping implemented by each other) is no longer suitable, the MLD may transmit a T2L negotiation request to the peer MLD, as discussed further below with respect to 1232.

[0145] According to some implementations, a non-AP MLD can utilize the AP MLD to register priority traffic (1214). For example, a non-AP MLD can utilize the AP MLD to register any high-priority (e.g., above a priority threshold) TID as a high-priority TID. Similarly, a non-AP MLD can provide the AP MLD with information regarding the prioritization (and / or other characteristics) of TIDs (e.g., only high-priority TIDs or all TIDs). For example, a non-AP MLD can transmit an indication of any reason why an AP-preferred mapping is considered inappropriate.

[0146] To register priority traffic, both AP MLDs and non-AP MLDs can complete one or more Flow Classification Service (SCS) handshakes. This is discussed further below. Figure 13 An SCS handshake according to some implementation schemes is shown.

[0147] In some implementations, as an alternative to or in addition to registration priority traffic, a non-AP MLD may transmit a T2L negotiation request to the AP MLD. The T2L negotiation request may contain a counter-proposal mapping (or mapping), such as a suitable EAT2LS mapping. For example, the non-AP MLD may indicate one or more suitable mappings, such as mapping active TIDs to sufficient links or sets of links based on their priority (e.g., as discussed above with respect to 1212). In response to transmitting such a counter-proposal, the non-AP MLD may stop (e.g., cancel or reset) a counter-proposal timer (e.g., this counter-proposal timer may have been started based on receiving the AP-preferred mapping in 1208). The non-AP MLD may start (e.g., restart) a counter-proposal timer based on the transmission of a counter-proposal. The AP MLD may receive a T2L negotiation request with a counter-proposal and may cancel / reset a first counter-proposal timer (e.g., from 1208) and start / restart a counter-proposal timer based on receiving a counter-proposal from the non-AP MLD. Thus, the AP MLD and non-AP MLD may each use their respective counter-proposal timers.

[0148] In some implementations, a T2L negotiation request from a non-AP MLD may include a counter-proposed mapping (or mapping) indicating an alternative AT2LS mapping (different from the first mapping proposed by the AP MLD). The non-AP MLD may include a reason code and / or additional information elements, along with the counter-proposal. For example, the non-AP MLD may include a reason code indicating “multi-radio coexistence” and also include a link preference element specifying which link is likely to suffer from severe multi-radio coexistence problems (e.g., due to Wi-Fi / Bluetooth (BT) coexistence issues, etc.). The reason code and additional information elements can be used to justify or explain a counter-proposal with an alternative AT2LS mapping.

[0149] According to some implementations, AP MLDs and non-AP MLDs can determine and apply a second mapping based on registered priority traffic (1216). In other words, if information about priority traffic has been registered (e.g., in 1214), AP MLDs and non-AP MLDs can determine a second mapping that provides sufficient links for the registered priority TIDs. For example, an MLD can (e.g., individually) determine an EAT2LS mapping that maps all registered priority TIDs to all links. Other TIDs can be mapped to fewer links, e.g., as in the AP-preferred mapping. In other words, the second mapping can be determined based on adjusting the AP-preferred mapping so that high-priority TIDs are mapped to all links without making other changes (e.g., by each MLD). Other methods for determining the second mapping can be used as needed.

[0150] In some implementations, the second mapping can be applied without using a counterproposal timer. For example, the second mapping can be applied immediately after the registered priority traffic (e.g., subject to a processing delay period, if applicable). For example, the second mapping can be applied upon SCS response from an AP MLD to a non-AP MLD.

[0151] Therefore, registering a high-priority TID (in 1214) allows both non-AP MLDs and AP MLDs to rapidly transmit and receive traffic with the prioritized TID on all links (e.g., or links mapped in the second mapping).

[0152] In some implementations, a counter-proposal mapping (e.g., provided by a non-AP MLD in 1214) can be applied as a second mapping. For example, the AP MLD can verify that a TID mapped to an additional link (e.g., based on a counter-proposal of a mapping preferred by the AP) can be registered as a priority TID. If such verification is performed, the AP MLD can treat the counter-proposal mapping as a second mapping and apply that second mapping.

[0153] AP MLD and non-AP MLD can each start (e.g., restart) the counterproposal timer based on the application's second mapping.

[0154] According to some implementations, the AP MLD can determine whether a second mapping or counter-proposal mapping from a non-AP MLD is appropriate (1218). This determination can be made while a counter-proposal timer (e.g., initiated by registering priority traffic in 1214 or by counter-proposals from a non-APMLD in 1214) is running. For example, the AP MLD can determine whether a second or counter-proposal mapping is appropriate based on whether the mapping might allow the AP MLD to balance the load of any non-APMLD connection across all available links that provide available information such as traffic patterns and load levels.

[0155] If the second or counter-proposal mapping is deemed appropriate, the AP MLD may apply it. Such mappings can be updated as needed, for example, as discussed relative to 1232. Therefore, according to some embodiments, it may be omitted. Figure 12 The rest of the text.

[0156] If a second mapping or counter-proposal is determined to be inappropriate, the AP MLD may determine a further counter-proposal mapping. This further counter-proposal mapping may be selected based on information regarding TID prioritization, the reasons provided by the inappropriateness of the mapping preferred by the non-AP MLD for the AP, information regarding the constraints faced by the non-AP MLD, and / or information regarding AP MLD load balancing and traffic on the links. For example, in response to registration priority traffic, the AP MLD may determine a counter-proposal mapping that provides more and / or better quality links for high-priority TIDs, while potentially allowing the AP MLD to balance the load of any non-AP MLD connection across all available links for which available information (such as traffic patterns and load levels) is given. Similarly, in response to a counter-proposal from a non-AP MLD, the AP MLD may determine a counter-proposal mapping that provides more and / or better quality links (relative to the AP-preferred mapping) for TIDs that will be mapped to all links according to the non-AP MLD's counter-proposal, while potentially allowing the AP MLD to balance the load of any non-AP MLD connection across all available links for which available information (such as traffic patterns and load levels) is given. In other words, the AP MLD can attempt to select more and / or better links for any TID that is prioritized by non-APMLD indications, while also maintaining sufficient flexibility for the AP MLD to balance the load. Further counter-proposal mappings could be AT2LS mappings or EAT2LS mappings.

[0157] If the second mapping or counter-proposal is determined to be inappropriate, the AP MLD may determine one or more reason codes and / or other information regarding the load balancing constraints. This information may be determined in a manner not used by the AP MLD, for example, to select further mapping proposals.

[0158] According to some implementations, the AP MLD may send a second request (1220) for a mapping to a non-AP MLD. The second request for a mapping may include instructions for further counter-proposed mappings. For example, the AP MLD may send a T2L negotiation request to a non-AP MLD. For example, when a non-AP MLD proposes the following mappings, the AP MLD may request / recommend an AT2LS mapping: 1) an EAT2LS mapping; 2) a different AT2LS mapping. Furthermore, when a non-AP MLD proposes a different EAT2LS mapping, the AP MLD may also request / recommend an EAT2LS mapping.

[0159] The second request for mapping may include an indication of why a second mapping or counter-proposal by a non-AP MLD is deemed unsuitable by the AP MLD, and / or an indication of constraints faced by the AP MLD (e.g., in terms of load balancing). Furthermore, the second request for mapping may include a reason code or other indication of constraints faced by the AP MLD, such as those related to link usage and / or load balancing. For example, the second request may indicate the number of TIDs that can be mapped to one or more links (e.g., and / or other metrics of traffic volume). As another example, a reason code indicating "load balancing" or "guaranteed low latency" and related information elements, as discussed above, may be provided. This information may be used by the non-AP MLD when selecting a mapping proposal acceptable to the AP MLD.

[0160] AP MLD and non-AP MLD can each start (e.g., or restart) a counter-proposal timer based on the transmission of a second request for mapping (e.g., or, in the case of non-AP MLD, based on reception).

[0161] According to some implementations, upon receiving a second request for mapping (e.g., a T2L negotiation request), the non-AP MLD may determine (1221) and potentially send (1222) a response (e.g., a T2L negotiation response). To determine this response, the non-AP MLD may determine whether the proposal is appropriate or an acceptable compromise. For example, the non-AP MLD may consider the priority of the TIDs of the links mapped relative to the proposal used for mapping (e.g., a further counter-proposal), for example, as discussed above with respect to 1212. The non-AP MLD may also consider its link constraints, such as multi-radio coexistence issues discussed above. Additionally, the non-AP MLD may consider reason codes or other information provided by the AP MLD, for example, to determine whether the further counter-proposal can be considered an acceptable compromise given the constraints of the AP MLD. For example, even if the further counter-proposal may not be entirely appropriate (e.g., because at least one TID is not mapped to a sufficient number / quality of links), the further counter-proposal may be considered an acceptable compromise if the reason / constraint indicates that the AP MLD may not be able to provide a completely appropriate mapping. In this context, depending on some implementations, non-AP MLDs may consider one or more secondary thresholds (e.g., higher priority thresholds and / or lower thresholds for the number / quality of links) to determine the acceptability of a mapping.

[0162] The response to a second request for mapping may use one of the following options: 1.) accept and apply a further counter-proposal (e.g., the requested AT2LS or EAT2LS mapping); 2.) propose an alternative mapping; 3.) request continued use of the current mapping (e.g., the second or counter-proposal, such as EAT2LS). For example, if the further counter-proposal is not accepted, the response may also include one or more reasons (e.g., codes) or other information related to the further counter-proposal. Furthermore, if the response includes option 2 or option 3 (e.g., a counter-proposal), the non-AP MLD may continue to use the current mapping for a period of time, for example, as discussed further below.

[0163] In some implementations, if a further counterproposal is accepted, no response can be transmitted. In this case, both the AP MLD and non-AP MLD can apply a further counterproposal when the counterproposal timer expires.

[0164] In some implementations, if further counterproposals are accepted, the mapping may be used indefinitely, for example, to undergo updates as needed, such as as described relative to 1232.

[0165] According to some implementations, in the case of a response transmitted according to option 2 or 3, the AP MLD can receive the response and determine whether to accept the proposed mapping or issue a final instruction (1224). For example, in response to receiving a counter-proposal in a T2L negotiation response from a non-AP MLD, the AP MLD can send a T2L negotiation request with a final decision. A T2L negotiation request with a final decision may or may not request a response from a non-AP MLD. For example, the T2L negotiation request may include fields indicating whether a response is requested, or different formats that can be used in the request to indicate this, etc.

[0166] To determine whether to accept the proposal, AP MLD may consider the factors discussed above relative to 1218. Additionally, AP MLD may consider any reasons or other information indicated by non-AP MLDs. Furthermore, AP MLD may use one or more lower thresholds for load balancing, for example, to determine whether the proposal is an acceptable compromise based on prioritization / reasons provided by non-AP MLDs.

[0167] If the AP MLD determines that a proposal from a non-AP MLD is acceptable, the AP MLD can map the proposal. At that point, the AP MLD can notify the non-AP MLD and complete the mapping. Therefore, the AP MLD can send a response with a final decision to accept the non-AP proposal.

[0168] If the AP MLD determines that a proposal from a non-AP MLD is unacceptable, the AP MLD may transmit a final response rejecting the proposal. This final response may instruct the non-AP MLD to fulfill the requirements of the AP MLD's most recent proposal (e.g., a further counter-proposal transmitted in 1220). In some implementations, the final response may specify a mapping.

[0169] In some implementations, the mapping indicated in the final response may differ from the previously requested mapping (e.g., as in the further counterproposal transmitted in 1220). For example, the AP MLD may determine one or more modifications to the further counterproposal based on reasons or other information provided by a non-AP MLD in 1222. Thus, the AP MLD may provide an indication of the modifications to the mapping relative to the further counterproposal.

[0170] As described above, a previous mapping (e.g., the second mapping of 1216) may remain valid for a period of time (e.g., while the AP MLD determines how to respond to a counterproposal from a non-AP MLD). In some implementations, this period may last until the AP MLD transmits and the non-AP MLD receives a final T2L request from the AP MLD. In some implementations, a counterproposal timer may also be used. For example, based on a response with a counterproposal transmitted by the non-AP MLD, the non-AP MLD may start (e.g., restart) the counterproposal timer. Similarly, the AP MLD may start (e.g., restart) the counterproposal timer. If the counterproposal timer expires without a final mapping instruction from the AP MLD, the AP MLD and non-AP MLD may use the current mapping indefinitely. In other words, the AP MLD may decide not to transmit the final T2L request, and thus allow the non-AP MLD to continue using the current mapping. This result may occur, for example, if the response in 1222 is based on option 3 (e.g., a request from the non-AP MLD instructing continued use of the second mapping of 1216).

[0171] According to some implementations, the non-AP MLD can receive any final mapping instruction and can transmit a response (1228). This response can be an acknowledgment of the final mapping instruction. When the response is transmitted, the mapping according to the final mapping instruction can be implemented.

[0172] In some implementations, for example, no response may be transmitted if the final mapping instruction does not result in a change to the previous mapping and / or if the T2L negotiation request with a final decision does not request a response.

[0173] Therefore, according to some implementation schemes, the AP MLD and non-AP MLD can implement the final mapping (1230) according to the final mapping instruction. The final mapping can be the same as or different from the default mapping, the second mapping, the AP-preferred mapping, or any other previously applied mapping. The AP MLD and non-AP MLD can exchange data and / or management / control information in the uplink and / or downlink directions according to the final mapping.

[0174] According to some implementations, the AP MLD and non-AP MLDs can update the current mapping (e.g., final mapping, etc.) as needed (1232). As described above, a mapping (e.g., final mapping, default mapping, AP-preferred mapping, or any mutually agreed mapping) can be used by the AP MLD and non-AP MLDs until either MLD determines that the mapping is no longer suitable (e.g., due to changes in the activity's TID, load, and / or other conditions as described above). If either MLD determines that a mapping (e.g., AP-preferred mapping or any mutually agreed mapping) is no longer suitable, the MLD can determine a proposed updated mapping and transmit a T2L negotiation request with an indication of the proposed updated mapping to the peer MLD. Each MLD can start a counter-proposal timer based on the T2L negotiation request. If no counter-proposal is provided before the timer expires, the proposed updated mapping can be implemented. If a counter-proposal is provided, the counter-proposal timer can be restarted by both devices. In some implementations, after each MLD has had the opportunity to make a proposal or counter-proposal for the updated mapping, the AP MLD can make a final decision on the updated mapping to be applied. In some implementations, after each MLD has had the opportunity to propose or counterpropose an update map, a non-AP MLD may make a final decision on which update map to apply.

[0175] As another possible method for updating the current mapping, updates can be applied automatically under certain conditions. For example, if all registered priority TIDs are terminated or become inactive, the non-AP MLD operation based on the EAT2LS mapping can automatically revert to the AT2LS mapping (or possibly a different EAT2LS mapping). In response to the deregistration or termination of a priority TID, the AP MLD can automatically change to the AT2LS mapping accordingly. For example, in such cases, both the AP MLD and non-AP MLD can automatically switch to the AP-preferred mapping. In some implementations, the fallback mapping (e.g., the same or different from the AP-preferred mapping) can be specified by the AP MLD for use in such situations.

[0176] Figures 13 to 14 and additional information .

[0177] In some implementations, the AP MLD may receive proposed mappings from non-AP MLDs (e.g., at any time) and may accept them with conditions. These conditions may include certain actions that the non-AP MLD must follow or avoid when the proposed mapping is in use. Such conditions can be used by the AP MLD to manage traffic on multiple links, while also providing non-AP MLDs with increased flexibility to use more / different links (e.g., according to the proposed mapping). As an example condition, the AP MLD can specify that non-AP MLDs follow Multi-User (MU) Enhanced Distributed Channel Access (EDCA) (MU-EDCA) for uplink transmissions on a specified link. As another example condition, the AP MLD can specify that non-AP MLDs wait for a trigger from the AP MLD before transmitting uplink transmissions on the specified link. As another example condition, the AP MLD can specify that non-AP MLDs use a specified link based on a specific duty cycle (e.g., only at a specific time). As another example condition, the AP MLD can allocate a specific number of tokens to non-AP MLDs (or groups of non-AP MLDs), and each token can allow a non-AP MLD to access a specified link within one or a specific number of UL Transmission Opportunities (TXOPs) or a specific time window, etc. As another example condition, the AP MLD can specify that non-AP MLDs use a specific link (only) within a restricted time window during a specific time period, etc. As another example condition, the AP MLD can specify that non-AP MLDs... MLDs use specified links subject to usage or utilization rate limitations; for example, an AP MLD can specify the maximum data rate of a link. AP MLDs can combine these (or other conditions) in various ways. For example, an AP MLD can specify a link (or link) for non-AP MLDs to use based on duty cycle, time limit, or trigger-based usage. For instance, a non-AP MLD might be allowed to use a link at any time during a time limit and, after the time limit, to use the link solely based on duty cycle or trigger-based usage.

[0178] In some implementations, T2L negotiation may include a three-way message structure. For example, such a structure may include: 1) a request, 2) a response, and 3) an acknowledgment. For example, (1) the initiator sends a mapping request. Then, (2) the responder sends a mapping response, which may include a counter-proposal with a counter-reason and / or other information. Then, (3) the initiator sends a mapping acknowledgment with a final decision. Such a three-way message structure may be, for example, based on… Figure 12 Examples of using 1232 and various other possibilities to perform updates. However, such a three-way message structure can also be used as needed. Figure 12 It is used in other parts of the method.

[0179] For example, a default mapping can be used to establish communication. The AP MLD (initiator) can initiate a three-way message (1208) with a request (1) for the AP-preferred mapping. The non-AP MLD can respond with a counter-proposal and other information (2)(1214). The AP MLD can then send an acknowledgment (3)(1226) with a final mapping instruction.

[0180] As another example, a default mapping can be used to establish communication. A non-AP MLD (initiator) can initiate a three-way message (1214) with a request (1) for an alternative mapping. The AP MLD can respond with a counter-proposal and other information (2)(1220). The non-AP MLD can then send an acknowledgment (3)(1222) accepting or rejecting the counter-proposal.

[0181] In some implementations, non-AP MLDs can be included in the T2L negotiation response (e.g., in...). Figure 12 The final decision is made in 1222. This final decision can be defined by the following options: 1) receiving a mapping from the AP MLD request (e.g., as...). Figure 12 (as indicated in 1220); 2) Select one with the constraints (e.g., these constraints may be provided by AP MLD, for example, in Figure 12 The alternative AT2LS or EAT2LS mappings are: 1) alternative AT2LS or EAT2LS mappings (in option 1220); 2) alternative EAT2LS mappings, where high-priority TIDs are mapped to all links and other TIDs are mapped to the links from the requested AT2LS mappings from the AP MLD. As examples of options 2 and 3, suppose the AP MLD proposes an AT2LS mapping that enables links 1 and 2 but disables link 3. For option 2, the non-AP MLD can choose to enable links 1 and 3 but disable link 2 (e.g., an alternative AT2LS mapping relative to the AP MLD's proposal). For option 3, the non-AP MLD can select links 1 and 2 as enabled (the same as the AP MLD's AT2LS proposal) and map high-priority TIDs to link 3 (e.g., as well as links 1 and 2). Therefore, in option 3, the AT2LS proposed by the AP MLD can be considered a subset of the EAT2LS chosen by the non-AP MLD.

[0182] Figure 13 An exemplary Flow Classification Service (SCS) handshake according to some implementation schemes is illustrated. As shown, three different types of SCS handshakes can be used, such as for registering, updating, or terminating priority TIDs.

[0183] According to some implementations, in order to register a priority TID, a non-AP MLD may send an SCS request to the AP MLD (1302). This request may include Quality of Service (QoS) characteristic elements. QoS characteristic elements may describe the TID, for example, using a TID identifier, an indication of uplink or downlink, or an indication of minimum and / or maximum service intervals (e.g., to describe the interval between packets of, for example, periodic traffic). For example, each period, the application may generate one or a batch of packets (which may then be paused until the next period), a minimum data rate, and / or delay limits (e.g., delay). According to some implementations, the AP MLD may transmit a response (e.g., an acknowledgment) (1304).

[0184] According to some implementations, in order to update the priority TID, a non-AP MLD may send an SCS request (1306) to the AP MLD. This request may include QoS characteristic elements and an indication that the priority TID registration will be updated. The QoS characteristic elements may describe aspects of the TID update. According to some implementations, the AP MLD may transmit a response (e.g., an acknowledgment) (1308).

[0185] According to some implementations, in order to deactivate / terminate a priority TID, a non-AP MLD may send an SCS request (1310) to the AP MLD. This request may include a QoS feature element and an indication that the registration of the priority TID will be cancelled. The QoS feature element may identify the TID. According to some implementations, the AP MLD may transmit a response (e.g., an acknowledgment) (1312).

[0186] Figure 14 The following are illustrated according to some implementation schemes. Figure 12The method is illustrated in the state diagram. As shown, the AP MLD and non-AP MLD can begin communication using a default mapping (e.g., AT2AL) (1402). The AP MLD can transmit an initial request to switch to a different (e.g., AP-preferred) mapping, such as AT2LS or EAT2LS (1403 or 1404, respectively). After 1403, if no high-priority TID is active, the non-AP MLD can operate in the AP-preferred AT2LS mapping (1405) or can register any high-priority TID (1406). After 1406, the AP MLD and non-AP MLD can operate in EAT2LS (e.g., according to a second mapping, such as having high-priority TIDs mapped to all links) (1407). Similarly, after 1404, the AP MLD and non-AP MLD can operate in EAT2LS (e.g., according to the EAT2LS mapping proposed by the AP MLD in 1404) (1407). Once in EAT2LS in 1407, AP MLD and non-AP MLD can operate in EAT2LS until the final mapping is negotiated (1408).

[0187] Starting at 1407, if the active EAT2LS mapping is not suitable for the AP MLD, the AP MLD may initiate further (non-final) T2L negotiation (1409). To do this, the AP MLD may transmit a second T2L request to the non-AP MLD. The second T2L request may indicate a further counter-proposed mapping (e.g., a proposed AT2LS mapping or a different proposed EAT2LS mapping). The non-AP MLD may transmit a T2L response to the non-AP MLD. This response may: 1) accept the proposal (e.g., causing the proposed mapping to be implemented as the final mapping by both the AP MLD and the non-AP MLD); 2) propose an alternative mapping (or an EAT2LS or AT2LS different from the current EAT2LS); or 3) propose to remain in the current EAT2LS mapping. If the non-AP MLD transmits a response according to option 2) or 3), the AP MLD and the non-AP MLD may operate in the current EAT2LS until a final mapping is negotiated (1408).

[0188] If the non-AP MLD transmits a response according to option 3), the AP MLD may determine, for example, whether the current (e.g., EAT2LS) mapping is acceptable based on any information provided by the non-AP MLD. If the current mapping is acceptable, the AP MLD may allow the counterproposal to end, and thus allow the current mapping to become final (1407).

[0189] If the non-AP MLD transmits a response according to option 2), the AP MLD may determine whether the proposed alternative mapping is acceptable. If the proposed mapping is acceptable, the AP MLD may accept the proposed mapping (1410), and both the AP MLD and the non-AP MLD may operate according to the alternative mapping (1411). If the proposed mapping is unacceptable, the AP MLD may initiate a final T2L negotiation (1412). The AP MLD may transmit a final T2L request, for example, indicating the final mapping. The non-AP MLD may respond to acknowledge the instruction, for example. Both the AP MLD and the non-AP MLD may operate according to the final mapping.

[0190] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0191] For example, by interpreting each message / signal X received by a non-AP MLD in the DL as a message / signal X transmitted by the AP MLD, and interpreting each message / signal Y transmitted by a non-AP MLD in the UL as a message / signal Y received by the AP MLD, any method described herein for operating an AP MLD can serve as the basis for a corresponding method for operating a non-AP MLD (and vice versa). Furthermore, methods described relative to AP MLDs can be interpreted as methods for non-AP MLDs in a similar manner.

[0192] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0193] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein, if executed by a computer system, the program instructions cause the computer system to perform a method, such as any method embodiment of the method embodiments described herein, or any combination of method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0194] In some implementations, the wireless device may be configured to include a processor (and / or a set of processors) and a memory medium storing program instructions, wherein the processor is configured to read from and execute the program instructions, wherein the program instructions are executable to cause the wireless device to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any combination of these subsets). The device may be implemented in any of a variety of forms.

[0195] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A method for communication, comprising: At the access point AP multi-link device MLD: Provide multiple links; Transmit an initial traffic identifier (TID) to link T2L mapping request for a first mapping to a non-access point MLD (non-AP MLD), the first mapping being between a plurality of TIDs and at least a subset of the plurality of links for communication with the non-AP MLD, wherein, according to the first mapping, a first TID is mapped to a first number of the plurality of links; Receive a request from the non-AP MLD to register the first TID as a high priority; as well as In response to the request to register the first TID as a high priority, the mapping is changed to a second mapping for communication with the non-AP MLD, wherein, according to the second mapping, the first TID is mapped to a second number of the plurality of links, which is greater than the first number.

2. The method of claim 1, wherein registering the first TID as a high-priority request includes a Stream Classification Service (SCS) request.

3. The method of claim 2 further includes transmitting an SCS response acknowledging the SCS request to the non-AP MLD.

4. The method of claim 1, further comprising associating with the non-AP MLD, wherein the initial T2L mapping request includes a T2L negotiation request transmitted after the association.

5. The method of claim 1, wherein the initial T2L mapping request includes at least one of an association response or a beacon / probe response.

6. The method of claim 1, wherein the request to register the first TID as a high priority includes a list of high-priority TIDs.

7. The method of claim 1, wherein registering the first TID as a high-priority request includes a proposed mapping.

8. The method of claim 7, wherein the second mapping is the proposed mapping.

9. An apparatus for communication, the apparatus comprising: Processor, the processor being configured to make the non-access point AP multilink device MLD non-AP MLD: A default mapping between multiple traffic identifiers and multiple links is used to associate the AP MLD, wherein the multiple links include various links connecting the AP MLD and the non-AP MLD; The AP MLD receives an indication of a second mapping between the plurality of traffic identifiers and the plurality of links, wherein, according to the second mapping, at least the first traffic identifier is mapped to fewer links than according to the default mapping; It is determined that the first traffic identifier is of high priority; as well as In response to the determination that the first traffic identifier is of high priority: A request to register the first traffic identifier as a high priority is transmitted to the AP MLD; as well as The mapping is changed to a third mapping, in which the first traffic identifier is mapped to at least more links than according to the second mapping.

10. The apparatus of claim 9, wherein, according to the third mapping, at least the first traffic identifier is mapped to all of the plurality of links.

11. The apparatus of claim 9, wherein registering the first traffic identifier as a high-priority request includes a Flow Classification Service (SCS) request, wherein the processor is further configured to cause the non-AP MLD: In addition to the SCS request, an indication of the third mapping is transmitted to the AP MLD.

12. The apparatus of claim 9, wherein the processor is further configured to cause the non-AP MLD: Determine to update the third mapping; Transmit a request for an alternative mapping to the AP MLD; Receive a counterproposal from the AP MLD; as well as The AP MLD transmits an acknowledgment of acceptance or rejection of the counterproposal.

13. The apparatus of claim 9, wherein the processor is further configured to cause the non-AP MLD: Receive beacons from the AP MLD; and The default mapping is determined based on the beacon.

14. The apparatus of claim 9, wherein registering the first traffic identifier as a high-priority request includes an indication of a proposed mapping.

15. The apparatus of claim 9, wherein the processor is further configured to cause the non-AP MLD: Start a timer upon receiving the instruction of the second mapping; and The timer is reset when the request to register the first traffic identifier as a high priority is transmitted.

16. The apparatus of claim 15, wherein the change to the third mapping is in response to the expiration of the timer.

17. The apparatus of claim 9, further comprising a radio component operatively coupled to the processor.

18. An apparatus for communication, the apparatus comprising: Processor, the processor being configured to enable access point AP multi-link device MLD AP MLD: A default mapping between multiple traffic identifiers and multiple links is used to associate non-AP MLDs, wherein the multiple links include various links connecting the AP MLD and the non-AP MLD; The non-AP MLD is transmitted with an indication of a second mapping between the plurality of traffic identifiers and the plurality of links, wherein, according to the second mapping, at least the first traffic identifier is mapped to fewer links than according to the default mapping; Receive a request from the non-AP MLD to register the first traffic identifier as a high priority; as well as The mapping is changed to a third mapping, in which the first traffic identifier is mapped to at least more links than according to the second mapping.

19. The apparatus of claim 18, wherein the processor is further configured to cause the AP MLD: starting a timer upon receiving the request, wherein The change to the third mapping is triggered by the expiration of the timer.

20. The apparatus of claim 18, further comprising a radio component operatively coupled to the processor.

Images