Link identification for frame communicated information

Abstract

This disclosure relates to link identifiers for information used in frame communication. In some aspects, a receiving device may: receive a management frame addressed to the receiving device; parse the management frame to identify a link identifier included in the management frame; associate the link identifier with link information included in the management frame; and update the communication configuration for the link identified by the link identifier based at least in part on the link information. Numerous other aspects are provided.

Description

[0001] This application is a divisional application of the patent application filed on May 24, 2021, with application number 202180036662.2, international application number PCT / US2021 / 070602, and entitled "Link Identifier for Information Transmitted in Frames".

[0002] Cross-reference to related applications

[0003] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 030,240, filed May 26, 2020, entitled “LINK IDENTIFICATION FOR MANAGEMENT FRAME CONVEYED INFORMATION”; U.S. Provisional Patent Application No. 63 / 122,010, filed December 7, 2020, entitled “LINKED IDENTIFICATION FOR FRAME CONVEYED INFORMATION”; and U.S. Non-Provisional Patent Application No. 17 / 327,424, filed May 21, 2021, entitled “LINK IDENTIFICATION FOR FRAME CONVEYED INFORMATION”, which are hereby expressly incorporated by reference. Technical Field

[0004] Various aspects of this disclosure generally relate to wireless communication, and to techniques and apparatus for managing link identification for frame transmission. Background Technology

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0006] A wireless network may include several base stations (BSs) capable of supporting communication between several user equipments (UEs). UEs may communicate with the BS via downlinks and uplinks. A "downlink" (or "forward link") refers to the communication link from the BS to the UE, while an "uplink" (or "reverse link") refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a B-node, gNB, access point (AP), radio headend, transmit / receive point (TRP), new radio (NR) BS, 5G B-node, etc.

[0007] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different user equipment to communicate at the city, country, region, and even global levels. NR (also known as 5G) is an enhancement set to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on the downlink (DL), CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to grow. Summary of the Invention

[0008] In some aspects, a wireless communication method performed by a receiving device (e.g., a multi-link device) may include: receiving a management frame addressed to the receiving device; parsing the management frame to identify a link identifier included in the management frame; associating the link identifier with link information included in the management frame; and updating a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0009] In some aspects, a receiver device for wireless communication includes: a memory and one or more processors coupled to the memory, the one or more processors being configured to: receive a management frame addressed to the receiver device; parse the management frame to identify a link identifier included in the management frame; associate the link identifier with link information included in the management frame; and update a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0010] In some aspects, a non-transient computer-readable medium storing one or more instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a receiving device, cause the one or more processors to: receive a management frame addressed to the receiving device; parse the management frame to identify a link identifier included in the management frame; associate the link identifier with link information included in the management frame; and update a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0011] In some aspects, an apparatus for wireless communication includes: means for receiving a management frame addressed to the apparatus; means for parsing the management frame to identify a link identifier included in the management frame; means for associating the link identifier with link information included in the management frame; and means for updating a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0012] In some aspects, a wireless communication method performed by a receiving device includes: receiving a frame addressed to the receiving device; parsing the frame to identify a link identifier included in the frame; associating the link identifier with link information included in the frame; and updating a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0013] In some aspects, a receiver device for wireless communication includes: a memory, one or more processors coupled to the memory, and a set of queues, wherein the one or more processors are configured to: receive a frame; identify the frame as link-dependent or link-unknown based at least in part on a type or subtype field in the frame's Media Access Control header; and assign the frame to a queue in the set of queues.

[0014] In some aspects, a receiver device for wireless communication includes: a memory and one or more processors coupled to the memory, the one or more processors being configured to: receive a frame addressed to the receiver device; parse the frame to identify a link identifier included in the frame; associate the link identifier with link information included in the frame; and update a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0015] In some aspects, a non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions, which, when executed by one or more processors of a receiving device, cause the receiving device having a set of queues to: receive a frame addressed to the receiving device; parse the frame to identify a link identifier included in the frame; associate the link identifier with link information included in the frame; and update a communication configuration for the link identified by the link identifier, at least in part based on the link information.

[0016] In some aspects, a non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a receiving device, cause the receiving device to: receive a frame; identify the frame as link-dependent or link-unknown based at least in part on a type or subtype field in the frame's Media Access Control header; and assign the frame to a queue in a queue set.

[0017] In some aspects, an apparatus for wireless communication includes: means for receiving a frame addressed to a receiving device; means for parsing the frame to identify a link identifier included in the frame; means for associating the link identifier with link information included in the frame; and means for updating a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0018] In some aspects, an apparatus includes: means for receiving a frame; means for identifying the frame as link-dependent or link-unknown based at least in part on a type or subtype field in the Media Access Control header of the frame; and means for assigning the frame to a queue in a queue set.

[0019] In some aspects, a wireless communication method performed by a receiver device having a set of queues includes: receiving a frame; identifying the frame as link-dependent or link-unknown based at least in part on a type or subtype field in the frame's Media Access Control header; and assigning the frame to a queue in the set of queues.

[0020] The aspects generally include, as substantially described herein with reference to the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transient computer-readable media, user equipment, base stations, wireless communication equipment, and / or processing systems.

[0021] The foregoing has broadly outlined the features and technical advantages of the examples according to this disclosure in an effort to facilitate a better understanding of the following detailed description. Additional features and advantages will be described thereafter. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for implementing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and their associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not for defining limitations on the claims.

[0022] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects may be implemented via integrated chip embodiments or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, or AI-enabled devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include several components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers) for analog and digital purposes. The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0023] To gain a more detailed understanding of the features described above in this disclosure, reference can be made to various aspects of the above brief overview, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as other equivalent aspects are permissible in this description. Identical reference numerals in different drawings may identify the same or similar elements.

[0024] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0025] Figure 2 This is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to this disclosure.

[0026] Figure 3A and 3B This is a diagram illustrating an example of a link identifier associated with information used to manage frame communication according to this disclosure.

[0027] Figure 4-6 This is a diagram illustrating an example process associated with a link identifier used to manage the information conveyed by a frame, according to this disclosure.

[0028] Figure 7 This is a block diagram of an example apparatus for wireless communication according to the present disclosure. Detailed Implementation

[0029] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as being limited to any specific structure or function given throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using additional structures, functionalities, or structures and functionalities that complement or supplement the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be implemented by one or more elements of the claims.

[0030] Several aspects of a telecommunications system will now be described with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and explained in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0031] It should be noted that although the aspects may be described herein using terms commonly associated with 5G or NR radio access technology (RAT), the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or RATs after 5G (e.g., 6G).

[0032] Figure 1This is a diagram illustrating an example of a wireless network 100 according to this disclosure. The wireless network 100 may be a 5G (NR) network and / or an LTE network, etc., or may include elements thereof. The wireless network 100 may include several base stations 110 (shown as BS110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, B-node, gNB, 5G B-node (NB), access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0033] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with a service subscription. Picocells can cover a relatively small geographic area and allow unrestricted access by UEs with a service subscription. Femtocells can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1 In the example shown, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “B node,” “5G NB,” and “cell” are used interchangeably herein.

[0034] In some respects, the cell need not be stationary, and the geographical area of ​​the cell can move depending on the location of the mobile BS. In some respects, BSs can interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks, using any suitable transport network).

[0035] The wireless network 100 may also include a relay station. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and transmitting those data transmissions to a downstream station (e.g., a UE or a BS). A relay station may also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, relay, etc.

[0036] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0037] Network controller 130 can be coupled to a set of Base Stations (BSs) and can provide coordination and control over these BSs. Network controller 130 can communicate with each BS via backhaul. These BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0038] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may be a cellular phone (e.g., a smartphone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet, camera, gaming device, netbook, smartbook, ultrabook, medical device or equipment, biometric sensor / device, wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), entertainment device (e.g., music or video device, or satellite radio), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0039] Some UEs may be considered Machine-Type Communication (MTC) UEs, or evolved or enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes may provide connectivity to or to a network (e.g., a wide area network, such as the Internet) or a cellular network, for example, via wired or wireless communication links. Some UEs may be considered Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered Customer Premises Equipment (CPE). UE 120 may be included within a housing that houses components of UE 120, such as processor components and / or memory components. In some aspects, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0040] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0041] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this scenario, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0042] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices of the wireless network 100 can communicate using an operating band with a first frequency range (FR1) and / or an operating band with a second frequency range (FR2), the first frequency range (FR1) spanning from 410 MHz to 7.125 GHz and the second frequency range (FR2) spanning from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency bands. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, although different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often referred to as the "millimeter wave" band. Therefore, unless otherwise stated, it should be understood that, if used herein, the terms sub-6 GHz, etc., can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise stated, it should be understood that, if used herein, the terms "millimeter wave," etc., can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., less than 24.25 GHz). It is conceivable that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some respects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive a management frame addressed to a receiving device; parse the management frame to identify a link identifier included in the management frame; associate the link identifier with link information included in the management frame; or update the communication configuration for the link identified by the link identifier based at least in part on the link information; and so on. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0044] In some respects, base station 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may: receive management frames addressed to receiving devices; parse the management frames to identify link identifiers included in the management frames; associate the link identifiers with link information included in the management frames; or update the communication configuration for the link identified by the link identifier based at least in part on the link information; and so on. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0045] As indicated above, Figure 1 This is provided as an example. Other examples may differ from the one provided. Figure 1 The example described.

[0046] Figure 2 This is a diagram illustrating an example 200 of communication between a base station 110 and a UE 120 in a wireless network 100 according to this disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein generally T ≥ 1 and R ≥ 1.

[0047] At base station 110, transmit processor 220 can receive data destined for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from each UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively.

[0048] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM) to obtain received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) these detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some respects, one or more components of the UE 120 may be included in the housing 284.

[0049] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in the core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0050] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, antenna groups, antenna element assemblies, and / or antenna arrays. Antenna panels, antenna groups, antenna element assemblies, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element assemblies, and / or antenna arrays may include coplanar antenna element assemblies and / or non-coplanar antenna element assemblies. Antenna panels, antenna groups, antenna element assemblies, and / or antenna arrays may include antenna elements within a single housing and / or multiple antenna elements within housings. Antenna panels, antenna groups, antenna element assemblies, and / or antenna arrays may include elements coupled to one or more transmission and / or reception components (such as...). Figure 2 One or more antenna elements (one or more components).

[0051] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, and / or CQI). Transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 can be pre-encoded by TX MIMO processor 266, where applicable, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, modulators and demodulators (e.g., MOD / DEMOD 254) of UE 120 can be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receiver processors 258, transmitter processors 264, and / or TX MIMO processors 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein, for example, as referenced. Figure 3A-6 As described.

[0052] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein, for example, as referenced. Figure 3A-6 As described.

[0053] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more techniques associated with the link identifier used for frame communication, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component of (such as) can execute or direct, for example Figure 4 Process 400 Figure 5 Process 500 Figure 6 The operation of process 600 and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include: a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120 (e.g., direct execution, or execution after compilation, transformation, and / or interpretation), the one or more processors, UE 120, and / or base station 110 may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 4 Process 500 Figure 5 Process 500 Figure 6 The operation of process 600 and / or other processes described herein. In some aspects, the execution instructions may include run instructions, translate instructions, compile instructions, and / or interpret instructions, etc.

[0054] In some aspects, the receiving device may include: means for receiving a management frame addressed to the receiving device; means for parsing the management frame to identify a link identifier included in the management frame; means for associating the link identifier with link information included in the management frame; and / or means for updating a communication configuration for the link identified by the link identifier based at least in part on the link information. In some aspects, means for the receiving device to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, means for enabling the receiving device to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a demodulator 254, a MIMO detector 256, a receiver processor 258, a transmitter processor 264, a TX MIMO processor 266, a modulator 254, a controller / processor 280, or a memory 282.

[0055] In some aspects, the receiving device includes: means for receiving a frame addressed to the receiving device; means for parsing the frame to identify a link identifier included in the frame; means for associating the link identifier with link information included in the frame; and / or means for updating a communication configuration for the link identified by the link identifier based at least in part on the link information. In some aspects, the means for the receiving device to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, means for enabling the receiving device to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a demodulator 254, a MIMO detector 256, a receiver processor 258, a transmitter processor 264, a TX MIMO processor 266, a modulator 254, a controller / processor 280, or a memory 282.

[0056] In some aspects, the receiving device includes: means for receiving a frame; means for identifying the frame as link-dependent or link-unknown based at least in part on a type or subtype field in the Media Access Control header of the frame; and / or means for assigning the frame to a queue in a queue set. In some aspects, the means for the receiving device to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, means for enabling the receiving device to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a demodulator 254, a MIMO detector 256, a receiver processor 258, a transmitter processor 264, a TX MIMO processor 266, a modulator 254, a controller / processor 280, or a memory 282.

[0057] although Figure 2 The boxes in the diagram are interpreted as different components, but the functions described above with respect to these boxes can be implemented by a single hardware component, software component, or combination of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of controller / processor 280.

[0058] As indicated above, Figure 2 This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0059] In some communication systems (such as 802.11 type communication systems), a transmitting device (e.g., a multi-link device (MLD)) can transmit data to a receiving device (another MLD) across multiple links. For example, the transmitting device can transmit frames to the receiving device. In this case, the transmitting device can queue multiple frames in a shared queue for transmission. The multiple frames in the shared queue may include management frames (e.g., frames of a specific type) that can convey information that varies from link to link (e.g., information applicable to a single link, information applicable only to a subset of multiple links, etc.).

[0060] At least in part, based on the fact that management frames are included in a shared queue used by multiple stations of the transmitting device, any station of the transmitting device can transmit management frames when the corresponding link is available. For example, a first station of the transmitting device (e.g., associated with a corresponding Media Access Control (MAC) entity) can receive a management frame from the shared queue and can transmit the management frame to a first station of the receiving device (e.g., associated with a corresponding MAC entity) via a first link. Similarly, a second station of the transmitting device can transmit another management frame to a second station of the receiving device via a second link.

[0061] Furthermore, non-access point receiver devices or transmitter devices can perform basic service set operations on a single link rather than multiple links. For example, a transmitter device or receiver device can deactivate one or more stations associated with one or more links to conserve power resources. Additionally or alternatively, one or more stations may be unreachable due to range or channel congestion issues. However, when a non-access point receiver device has unreachable stations, the transmitter device may be unable to update the parameters for the links associated with those unreachable stations.

[0062] Because management frames reside in a shared queue at the transmitting device and are assigned to individual stations at least in part based on link availability, the link information in the management frame may not be applicable (or may not only apply to) the link on which the management frame was received. As a result, the receiving device may be unable to identify which links(s) to which it should apply the link information included in the received management frame. In this situation, the receiving device may be unable to update the communication configuration for that one or more links, leading to a lack of communication configuration synchronization, which can result in communication loss, reduced throughput, and so on.

[0063] The aspects described herein enable a transmitting device (e.g., a first MLD) to include one or more link identifiers in a management frame transmitted to a receiving device (e.g., a second MLD). In this scenario, the receiving device can receive the management frame, identify the link identifier, associate the link identified in the link identifier with link information, and update the link with a communication configuration determined at least in part based on the link information. In this way, both the transmitting and receiving devices can update the communication configuration for the link, even if the station associated with the link is unreachable.

[0064] Figure 3A and 3B This is a diagram illustrating an example 300 associated with a link identifier used to manage information conveyed by frames or other frames, according to this disclosure. (See diagram for example.) Figure 3A As shown, Example 300 includes a transmitting device 310 (e.g., a first MLD) and a receiving device (e.g., a second MLD). For example, the transmitting device 310 may include a shared queue from which one or more management frames or other frames are dequeued for one or more stations (STAs) having corresponding MAC entities. The one or more stations of the transmitting device 310 may be associated with one or more links to one or more stations (e.g., each having a corresponding MAC entity) of the receiving device 320. The receiving device 320 may queue received frames in the shared queue for processing.

[0065] As in Figure 3A As further shown by reference numeral 330 in the accompanying drawings, the receiving device 320 may receive management frames or other types of frames. For example, the receiving device 320 may receive management frames containing link information that identifies the communication configuration of one or more links. In some aspects, the transmitting device 310 may configure the management frame to convey a link identifier along with the link information. For example, the transmitting device 310 may include a link identifier in the management frame to indicate one or more links to which the link information in the management frame is to be applied, as described in more detail herein. In this way, the transmitting device 310 and the receiving device 320 may be able to update operating parameters on behalf of stations that are unreachable (e.g., due to range, channel conditions, power-saving configurations, etc.).

[0066] As in Figure 3A As further illustrated by reference numeral 340 in the accompanying drawings, the receiving device 320 can determine link information and update the communication configuration. For example, based at least in part on the receipt of a management frame, the receiving device 320 can identify a link identifier, associate the link identified by the link identifier with link information, and update the communication configuration for that link according to the link information.

[0067] In some respects, the receiving device 320 may identify a link identifier in a field of the management frame. For example, the receiving device 320 may parse the Address 3 (A3) field of the management frame to identify the stations to which the link information in the management frame is applicable (and associate it with the links). In this case, the A3 field may be specified to convey the MAC address of the station to which the link information is applicable. Additionally or alternatively, when the link information pertains to all links of, for example, all stations of the receiving device 320, the A3 field may be specified to convey the address of the receiving device 320. In this case, at least in part because the link identifier is located in a fixed position, the latency associated with identifying the station to which the link information is to be applied (and updating the corresponding communication configuration) can be reduced. Furthermore, at least in part because the A3 field is a protected field, the likelihood of a malicious attacker updating the contents of the A3 field to disrupt the communication configuration update can be reduced.

[0068] In some respects, the receiving device 320 can distinguish the link identifier. For example, when the link identifier is included in the A3 field and can identify a station or receiving device using a common MAC address, the receiving device 320 can identify a global / local (U / L) bit, which is set to indicate whether the identified MAC address is for an identifying station or a receiving device.

[0069] Additionally or alternatively, the receiving device 320 may identify (e.g., in the MAC header) a header field that indicates whether the MAC address is from an identifying station or a receiving device. For example, it may have a Distribution System (DS) field that has previously been reserved for management frames. To DS (For example, "go to the distribution system") is set to 0 and From DS ("From distributed system") is set to 1 or To DS Set to 1 and From DS The configuration set to 1) can be specified to be used to signal that the address 3 field identifier is the destination of the MLD rather than its station. Additionally or alternatively, the receiving device 320 can determine whether the MAC address identifies the station or the receiving device based at least in part on the frame type. For example, when the management frame is a (re)association request ( (Re-) Association Request ) frame, (re)associate response ( (Re-)Association Response ) frame, or authentication ( Authentication When a frame is received, the receiving device 320 can determine that the MAC address identifies the receiving device. In some respects, the MAC address can be specified to be unique to avoid conflicts between shared MAC addresses of stations or receiving devices.

[0070] In some aspects, the receiving device 320 may identify the link identifier in the High Efficiency (HE) control portion of the header of the management frame. For example, the A-control field may be specified in the header of the management frame in which the link identifier is conveyed, and the receiving device 320 may identify the link identifier. In this way, by providing the link identifier in a fixed location, the latency associated with identifying the link identifier (and updating the corresponding communication configuration) can be reduced compared to other technologies. In some aspects, the management frame may include HE control and the link identifier, which are repeated as information elements in the body of the management frame. In this case, the receiving device 320 may verify the link identifier from the body against the link identifier from the header before updating the communication configuration, thereby improving information security (by verifying that the content of the unprotected HE control (such as the link identifier information) has not been tampered with). Similarly, in some aspects, the management frame may include HE control and an information element conveying a Message Integrity Code (MIC) for the HE control. In this case, the receiving device 320 may verify the MIC for the HE control before updating the communication configuration, thereby improving information security.

[0071] Similarly, in some aspects, management frames may include HE control and Additional Authentication Data (AAD) bits. For example, receiving device 320 may verify a variable-size AAD (e.g., which may provide security for one or more link identifiers), a fixed-size AAD (e.g., which includes one or more bits in the packet number field when a fixed-size AAD is used to protect multiple link identifiers), etc., before updating the communication configuration. In this way, transmitting device 310 and receiving device 320 can reduce the possibility of malicious alteration of link identifiers by using security techniques in conjunction with unprotected HE control data. In some aspects, the link identifier may be in a different part of the frame (e.g., different from the HE control), such as in the sequence number (SN) or packet number (PN) portion or in the AAD or another field in the frame. In some aspects, the AAD may provide protection for HE control, another type of A-control field that may include the link identifier, SN, or PN, the link identifier value (e.g., carried in the HE control field), or a field carrying link information, etc. In some respects, a link identifier can be a numerical value (e.g., a 4-bit field that can carry up to 16 unique values) or a MAC address (e.g., a 48-bit field that uniquely identifies the MAC address of the expected link). For example, a link identifier can be the MAC address of the expected station (STA) or the basic service set identifier (BSSID) of the expected link.

[0072] In some respects, the receiving device 320 may identify the link identifier in a dedicated element of the management frame. For example, a new information element may be designated and appended as the last (or another designated position) information element within the management frame. In this case, the receiving device 320 may identify the link identifier at the designated information element position. In this way, the link identifier can be protected by using information elements in the management frame.

[0073] In some respects, receiver device 320 may identify multiple link identifiers (or link identifiers applicable to multiple links) in management frames. For example, receiver device 320 may receive multiple consecutive management frames (e.g., transmitter device 310 may use Short Interframe Spacing (SIFS) bursts to transmit multiple consecutive management frames), which include link identifiers for different links. Additionally or alternatively, receiver device 320 may identify multiple link identifiers in aggregated management frames. For example, transmitter device 310 may aggregate multiple management frames with corresponding link information into a single Physical Layer (PHY) Protocol Data Unit (PPDU). To support carrying more than one management frame in a single PPDU, a block acknowledgment scheme for management frames may be used. For example, in a block acknowledgment scheme, management frames may have a sequence number associated with them, and block acknowledgment (ACK) frames may be used to acknowledge multiple management frames at least in part based on the corresponding sequence number.

[0074] In some respects, the receiving device 320 may parse fields to identify multiple link identifiers of multiple links to which link information is to be applied. For example, when the link identifier is in the A3 field, the receiving device 320 may identify multiple information elements that convey multiple link identifiers, such as multiple target wake-up time (TWT) information elements that convey multiple link identifiers. Additionally or alternatively, the receiving device 320 may identify multiple dedicated link identifier information elements that convey multiple link identifiers (e.g., based at least in part on a specification that specifies multiple dedicated link identifier information elements, or at least in part on parsing management frames to identify multiple dedicated link identifier information elements).

[0075] Additionally or alternatively, when a link identifier is included in the HE control, the HE control can be configured to implement signal notification of multiple link identifiers. As an example, the HE control may include 4 bits for signaling the HE A-control type and the link identifier may be 8 bits. In this case, a 2-bit field may be specified to implement signal notification of a predefined set of links. For example, a value of 0 may indicate that the link information applies to all links, resulting in an A-control of 6 bits (4 bits for type and 2 bits for the 2-bit field). In this case, the receiving device 320 can use the 2-bit field to determine the size of the A-control and thereby parse the HE control to determine one or more link identifiers. As another example, a value of 1 may indicate that the link information applies to a single link, which may indicate an A-control size of 14 bits (e.g., 4 bits for type, 2 bits for the field, and a single 8-bit link identifier). Similarly, a value of 2 may indicate that the link information applies to two links, which may indicate an A-control size of 22 bits, and a value of 3 may indicate that the link information applies to three links, which may indicate an A-control size of 30 bits. In this manner, by using a 2-bit field and a variable-size A-control, the transmitting device 310 can indicate multiple link identifiers, and the receiving device 320 can identify these multiple link identifiers. Furthermore, this signaling scheme will enable the definition of a variable-size A-control field.

[0076] In some respects, the receiving device 320 may update the communication configuration at least in part based on one or more identified link identifiers. For example, the receiving device 320 may update the link on which link information is received, the link different from the link on which link information is received, multiple links (e.g., one of which may or may not be the link on which link information is received), and so on. For example, as... Figure 3B As shown, a TWT information frame transmitted by access point (AP2) of access point MLD (e.g., transmitter device 310) on the first link may include a link identifier for updating scheduling or parameters for the second link, thereby enabling scheduling or parameter updates when the second link is unreachable (e.g., in a low-power state, outside range, experiencing congestion or interference, etc.). In this case, as Figure 3BAs shown, a non-AP station (STA2) of a non-AP MLD (e.g., receiver device 320) can transmit confirmation for TWT information. As a result, the non-AP MLD can extend the sleep state (e.g., power-saving state) of another non-AP station (STA1) of the non-AP MLD without waking that other station to receive link information associated with the extended sleep state. In this way, the transmitting device 310 and the receiving device 320 can use link identifiers for cross-link signaling. In some aspects, the link identifier can map Receiver Not Ready (RNR) entries to Multiple Link Address (MLA) information elements. For example, when the HE control or link identifier information element conveys a link identifier (e.g., a value of 1 octet, 2 octets, etc., which contrasts with an address 3 field that can convey a MAC address with 6 octets), the link identifier can map RNR entries to the MLA information element.

[0077] As indicated above, Figure 3A and 3B This is provided as an example. Other examples may differ from the one provided. Figure 3A and Figure 3B The example described.

[0078] Figure 4 This is a diagram illustrating an example process 400 performed by a receiving device, for example, according to various aspects of this disclosure. Example process 400 is an example in which a receiving device (e.g., it may be an MLD, BS 110, UE 120, receiving device 320, etc.) performs operations associated with a link identifier used to manage the information conveyed by frames.

[0079] like Figure 4 As shown, in some aspects, process 400 may include receiving management frames addressed to the receiving device (block 410). For example, the receiving device (e.g., using an MLD such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may receive management frames addressed to the receiving device, as described above.

[0080] like Figure 4As further shown, in some aspects, process 400 may include parsing the management frame to identify the link identifier included in the management frame (box 420). For example, a receiving device (e.g., using an MLD of antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may parse the management frame to identify the link identifier included in the management frame, as described above.

[0081] like Figure 4 As further shown, in some aspects, process 400 may include associating the link identifier with link information included in the management frame (box 430). For example, a receiving device (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receiver processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receiver processor 258, controller / processor 280, etc.) may associate the link identifier with the link information included in the management frame, as described above.

[0082] like Figure 4 As further shown, in some aspects, process 400 may include updating the communication configuration for the link identified by the link identifier based at least in part on the link information (block 440). For example, a receiving device (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may update the communication configuration for the link identified by the link identifier based at least in part on the link information, as described above.

[0083] Process 400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0084] In the first aspect, the link identifier includes information identifying the station associated with the receiving device and to which the link information applies, and the information identifying the station is included in the address 3 (A3) field of the management frame.

[0085] In the second aspect, either alone or in combination with the first aspect, the information identifying the station is a unique MAC address that distinguishes the station from the MLD associated with that station.

[0086] In a third aspect, either alone or in combination with one or more of the first and second aspects, the receiving device is configured to determine, at least in part, that the information is associated with identifying the station based on at least one of the U / L bits of the MAC address of the management frame, a reserved field in the MAC address, or the frame type of the management frame.

[0087] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the link identifier is included in the HE control of the header of the management frame.

[0088] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the HE control and link identifier are repeated as information elements in the body of the management frame, and the receiving device is configured to verify the link identifier in the header of the management frame against the link identifier in the information elements of the management frame before updating the communication configuration.

[0089] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the receiving device is configured to verify the HE control by referring to the MIC for HE control included in the information elements of the body of the management frame before updating the communication configuration.

[0090] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the receiving device is configured to use an AAD to verify HE control before updating the communication configuration, and the AAD is one of the following: a variable-size AAD, a fixed-size AAD that includes one or more bits of a packet number field and is applicable to one or more link identifiers.

[0091] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the link identifier is included in a dedicated element of the management frame.

[0092] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, a management frame is one of a set of coherent management frames that include common link information applicable to the corresponding set of link identifiers.

[0093] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, management frames are aggregated into a PPDU comprising multiple management frames having multiple link identifiers for multiple links.

[0094] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the receiving device is configured to acknowledge the PPDU using multiple sequence numbers corresponding to multiple management frames aggregated into the PPDU.

[0095] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the management frame includes multiple information elements that convey multiple link identifiers of multiple links to which link information applies.

[0096] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the management frame includes multiple link identifier information elements that convey multiple link identifiers of multiple links to which the link information applies.

[0097] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the management frame includes HE control having fields having multiple link identifiers for identifying multiple links to which the link information applies.

[0098] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the link identifier is mapped to cross-link parameters.

[0099] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the field controlled by HE may be a variable-length field, and the variable length may be based at least in part on the number of link identifiers among a plurality of link identifiers.

[0100] In the seventeenth aspect, protection for HE control is provided in the AAD field, either alone or in combination with one or more of the first to sixteenth aspects.

[0101] In the eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, all HE controls are protected in the AAD field.

[0102] although Figure 4 An example box of process 400 is shown, but in some respects, process 400 may include... Figure 4 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 400 can be executed in parallel.

[0103] Figure 5 This is a diagram illustrating an example process 500 performed by a receiving device, for example, according to various aspects of this disclosure. Example process 500 is an example in which a receiving device (e.g., an MLD using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) performs the operations described herein.

[0104] like Figure 5As shown, in some aspects, process 500 may include receiving frames addressed to the receiving device (block 510). For example, the receiving device (e.g., using an MLD of antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may receive frames addressed to the receiving device, as described above.

[0105] like Figure 5 As further shown, in some aspects, process 500 may include parsing the frame to identify the link identifier included in the frame (box 520). For example, a receiving device (e.g., using an MLD of antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may parse the frame to identify the link identifier included in the frame, as described above.

[0106] like Figure 5 As further shown, in some aspects, process 500 may include associating the link identifier with link information included in the frame (box 530). For example, a receiving device (e.g., using an MLD such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may associate the link identifier with link information included in the frame, as described above.

[0107] like Figure 5 As further shown, in some aspects, process 500 may include updating the communication configuration for the link identified by the link identifier based at least in part on the link information (block 540). For example, a receiving device (e.g., using an MLD such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may update the communication configuration for the link identified by the link identifier based at least in part on the link information, as described above.

[0108] Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0109] In the first aspect, the link identifier is conveyed in a field outside the HE control field of the frame header.

[0110] In the second aspect, alone or in combination with the first aspect, the field includes at least one of the following: a portion of the SN field, a portion of the PN field, or a portion of the AAD field.

[0111] In the third aspect, protection of the link identifier is conveyed by at least a portion of the AAD field, either alone or in combination with one or more of the first and second aspects.

[0112] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the AAD field includes one or more bits reserved for one or more other fields.

[0113] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the one or more other fields include at least one of a sequence number field or a group number field.

[0114] although Figure 5 An example box of process 500 is shown, but in some respects, process 500 may include... Figure 5 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 500 can be executed in parallel.

[0115] Figure 6 This is a diagram illustrating an example process 600 performed by a receiving device, for example, according to various aspects of this disclosure. Example process 600 is an example in which a receiving device (e.g., an MLD using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) performs the operations described herein.

[0116] like Figure 6 As shown, in some aspects, process 600 may include receiving frames (block 610). For example, a receiving device (e.g., using an MLD such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may receive frames as described above.

[0117] like Figure 6As further shown, in some aspects, process 600 may include identifying the frame as link-dependent or link-unknown based at least in part on the type or subtype field in the Media Access Control header of the frame (box 620). For example, a receiving device (e.g., using an MLD such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may identify the frame as link-dependent or link-location-dependent based at least in part on the type or subtype field in the Media Access Control header of the frame, as described above. In some aspects, link-unknown frames are associated with an MLD. Examples of link-unknown frames include reassociation request frames, reassociation response frames, association request frames, association response frames, or additional block acknowledgement (ACK) (AADBA) frames, etc.

[0118] like Figure 6 As further shown, in some aspects, process 600 may include assigning the frame to a queue in a queue set (box 630). For example, a receiving device (e.g., using an MLD such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may assign the frame to a queue in a queue set, as described above.

[0119] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0120] In the first aspect, the group number is obtained from the shared pool.

[0121] In the second aspect, either alone or in combination with the first aspect, one or more links-unknown frames are assigned to a shared queue in the queue set.

[0122] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 600 includes performing link-level replay verification for frames that vary depending on the link.

[0123] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 600 includes performing MLD-level replay verification for frames with unknown links.

[0124] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the queue set includes a shared queue and at least one queue that varies depending on the link.

[0125] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the queue set includes at least one queue that varies depending on the link and does not include a shared queue.

[0126] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 600 includes queuing link-specific management frames into link-specific queues.

[0127] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 600 includes queuing link-unknown management frames into active, link-specific queues.

[0128] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the first frame includes a link identifier field in its initial portion, and the one or more processors are configured to encapsulate or tunnel a second frame containing content suitable for a particular link and transmit the first frame on any available link. In some aspects, the first frame may provide one or more of the following: the length of the second frame, frame header information of the second frame, or the frame body of the second frame. For example, in a multi-link setup including two or more links, an AP or non-AP STA of the MLD may transmit a frame (e.g., a multi-link encapsulated frame) that encapsulates a MAC Management Protocol Data Unit (MMPDU). The multi-link encapsulated frame may include one or more of the following: an MMPDU length field, an MMPDU frame control field, or an MMPDU frame body field, and others. The multi-link encapsulated frame may be transmitted on a first link carrying an MMPDU intended for use on a second or third link.

[0129] although Figure 6 An example box of process 600 is shown, but in some respects, process 600 may include... Figure 6 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 600 can be executed in parallel.

[0130] Figure 7This is a block diagram of an example device 700 for wireless communication. Device 700 may be a receiver device, or a receiver device may include device 700. In some aspects, device 700 includes a receiving component 702 and a transmitting component 704, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 700 may use the receiving component 706 and the transmitting component 702 to communicate with another device 706 (such as a UE, a base station, or another wireless communication device). As further shown, device 700 may include a communication manager 140 or 150. Communication manager 140 or 150 may include one or more of the following: frame parsing component 708, link association component 710, link update component 712, link identification component 714, or queue assignment component 716, and others.

[0131] In some respects, Equipment 700 can be configured to perform the actions described in this article. Figures 3A-3B One or more operations described herein. Additionally or alternatively, equipment 700 may be configured to perform one or more processes described herein, such as... Figure 4 Process 400 Figure 5 Process 500 Figure 6 The process 600, or a combination thereof. In some respects, Figure 7 The equipment 700 and / or one or more components shown may include a combination Figure 2 One or more components of the described receiving device. Additionally or alternatively, Figure 7 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of that component.

[0132] Receiver 702 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from equipment 706. Receiver 702 may provide the received communications to one or more other components of equipment 700. In some aspects, receiver 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of equipment 706. In some aspects, receiver 702 may include combinations of... Figure 2 The described receiver device includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0133] The transmission component 704 can transmit communications (such as reference signals, control information, data communications, or combinations thereof) to the device 706. In some aspects, one or more other components of the device 706 can generate communications and provide the generated communications to the transmission component 704 for transmission to the device 706. In some aspects, the transmission component 704 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and can transmit the processed signals to the device 706. In some aspects, the transmission component 704 may include combinations of... Figure 2 The described receiver device includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof. In some aspects, the transmit component 704 may coexist with the receive component 702 in a transceiver.

[0134] The receiving component 702 can receive management frames addressed to the receiving device. The frame parsing component 708 can parse the management frame to identify the link identifier included in the management frame. The link association component 710 can associate the link identifier with the link information included in the management frame. The link update component 712 can update the communication configuration for the link identified by the link identifier based at least in part on the link information.

[0135] The receiving component 702 can receive frames addressed to the receiving device. The frame parsing component 708 can parse the frame to identify the link identifier included in the frame. The link association component 710 can associate the link identifier with the link information included in the frame. The link update component 712 can update the communication configuration for the link identified by the link identifier based at least in part on the link information.

[0136] The receiving component 702 can receive frames. The link identification component 714 can identify the frame as link-dependent or link-unknown, at least in part, based on the type or subtype field in the frame's Media Access Control header. The queue assignment component 716 can assign the frame to a queue in a queue set.

[0137] Figure 7 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 7 The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 7 The two or more components shown can be implemented within a single component, or Figure 7 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 7 The collection of components shown (e.g., one or more components) can be executed as described by Figure 7 The other set of components shown in the diagram performs one or more functions.

[0138] The following provides an overview of the various aspects of this disclosure: Aspect 1: A wireless communication method performed by a receiving device, comprising: receiving a management frame addressed to the receiving device; parsing the management frame to identify a link identifier included in the management frame; associating the link identifier with link information included in the management frame; and updating a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0139] Aspect 2: The method of aspect 1, wherein the link identifier includes information identifying a station associated with the receiving device and to which the link information applies, and wherein the information identifying the station is included in the address 3 (A3) field of the management frame.

[0140] Aspect 3: The method of aspect 2, wherein the information of the identifying station is a unique Media Access Control (MAC) address that distinguishes the station from the multi-link device (MLD) associated with the station.

[0141] Aspect 4: The method of any of Aspects 2 to 3, wherein the receiving device is configured to determine that the information is associated with the identification station based at least in part on at least one of the following: the global / local (U / L) bits of the media access control (MAC) address of the management frame, a reserved field in the MAC address, or the frame type of the management frame.

[0142] Aspect 5: The method of any of Aspects 1 to 4, wherein the link identifier is included in the efficient (HE) control of the header of the management frame.

[0143] Aspect 6: The method of aspect 5, wherein protection for HE control is in the Additional Authentication Data (AAD) field.

[0144] Aspect 7: As in aspect 6, where all HE controls are protected in the AAD field.

[0145] Aspect 8: The method of any of Aspects 5 to 7, wherein the HE control and the link identifier are repeated as information elements in the body of the management frame, and wherein the receiving device is configured to verify the link identifier in the header of the management frame against the link identifier in the information elements in the body of the management frame before updating the communication configuration.

[0146] Aspect 9: The method of any of Aspects 5 to 8, wherein the receiving device is configured to verify the HE control by referring to the Message Integrity Code (MIC) for HE control included in the information element in the body of the management frame before updating the communication configuration.

[0147] Aspect 10: The method of any of Aspects 5 to 9, wherein the receiving device is configured to verify the HE control using Additional Authentication Data (AAD) before updating the communication configuration, and wherein the AAD is one of a variable-size AAD or a fixed-size AAD that includes one or more bits of a packet number field and is applicable to one or more link identifiers.

[0148] Aspect 11: The method of any of Aspects 1 to 10, wherein the link identifier is included in a dedicated element of the management frame.

[0149] Aspect 12: The method of any of Aspects 1 to 11, wherein the management frame is one of a set of coherent management frames that include common link information applicable to the corresponding link identifier set.

[0150] Aspect 13: The method of any of Aspects 1 to 12, wherein the management frame is aggregated into a Physical Layer (PHY) Protocol Data Unit (PPDU) comprising a plurality of management frames having a plurality of link identifiers for a plurality of links.

[0151] Aspect 14: The method of aspect 13, wherein the receiving device is configured to acknowledge the PPDU using multiple sequence numbers corresponding to multiple management frames aggregated into the PPDU.

[0152] Aspect 15: The method of any of Aspects 1 to 14, wherein the management frame includes multiple information elements that convey multiple link identifiers of multiple links to which the link information applies.

[0153] Aspect 16: The method of any of Aspects 1 to 15, wherein the management frame includes a plurality of link identifier information elements that convey the plurality of link identifiers to which the link information applies.

[0154] Aspect 17: The method of any of Aspects 1 to 16, wherein the management frame includes efficient (HE) control having a field having multiple link identifiers for identifying multiple links to which the link information applies.

[0155] Aspect 18: The method of aspect 17, wherein the field controlled by the HE can be a variable-length field, and the variable length can be based at least in part on the number of link identifiers among the plurality of link identifiers.

[0156] Aspect 19: The method of any of Aspects 1 to 18, wherein the link identifier is mapped to cross-link parameters.

[0157] Aspect 20: The method of aspect 6, wherein a portion of the link identifier communicated in the HE control is protected in the AAD field.

[0158] Aspect 21: The method of either Aspect 6 or Aspect 20, wherein a portion of the HE control is protected in the AAD field.

[0159] Aspect 22: The method of aspect 21, wherein the portion controlled by the HE includes one or more A-control fields.

[0160] Aspect 23: A wireless communication method performed by a receiving device, comprising: receiving a frame addressed to the receiving device; parsing the frame to identify a link identifier included in the frame; associating the link identifier with link information included in the frame; and updating a communication configuration for the link identified by the link identifier based at least in part on the link information.

[0161] Aspect 24: The method of aspect 23, wherein the link identifier is conveyed in a field outside the efficiency (HE) control of the header of the frame.

[0162] Aspect 25: The method of aspect 24, wherein the field includes at least one of the following: a portion of a serial number (SN) field, a portion of a group number (PN) field, or a portion of an additional authentication data (AAD) field.

[0163] Aspect 26: The method of any of Aspects 23 to 24, wherein protection of the link identifier is conveyed using at least a portion of the Additional Authentication Data (AAD) field.

[0164] Aspect 27: The method of aspect 26, wherein the AAD field includes one or more bits reserved for one or more other fields.

[0165] Aspect 28: The method of aspect 27, wherein the one or more other fields include at least one of the following: a serial number field or a group number field.

[0166] Aspect 29: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform methods as described in one or more of aspects 1-22.

[0167] Aspect 30: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform methods as described in one or more aspects of aspects 1-22.

[0168] Aspect 31: An apparatus for wireless communication, comprising: at least one means for performing a method as described in one or more aspects of aspects 1-22.

[0169] Aspect 32: A non-transient computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods as described in one or more aspects of aspects 1-22.

[0170] Aspect 33: A non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions which, when executed by one or more processors of a device, cause the device to perform methods as described in one or more aspects of aspects 1-22.

[0171] Aspect 34: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform methods as described in one or more aspects of aspects 23-28.

[0172] Aspect 35: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform methods as described in one or more aspects of aspects 23-28.

[0173] Aspect 36: An apparatus for wireless communication, comprising: at least one means for performing a method as described in one or more aspects of aspects 23-28.

[0174] Aspect 37: A non-transient computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods as described in one or more aspects of aspects 23-28.

[0175] Aspect 38: A non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions which, when executed by one or more processors of a device, cause the device to perform methods as described in one or more aspects of aspects 23-28.

[0176] Aspect 39: The method of any of Aspects 1 to 22 further includes identifying the link of the receiving device; and wherein updating the communication configuration includes updating the communication configuration at least in part based on identifying the link of the receiving device.

[0177] Aspect 40: The method of any of Aspects 1 to 22 or 39, wherein the information of the identification station includes fields associated with the identification distribution system (DS).

[0178] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or may be obtained through practice.

[0179] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, processors are implemented using hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in any way. Thus, the operation and behavior of these systems and / or methods are described herein without reference to any specific software code—it is understood that software and hardware can be designed to implement these systems and / or methods, at least in part, based on the descriptions herein.

[0180] As used in this article, depending on the context, a threshold can refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0181] Although specific combinations of features are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below may be directly subordinated to only one claim, the disclosure of aspects includes each dependent claim being combined with each other claim in this set of claims. As used herein, the phrase “at least one of” refers to any combination of these items, including single members. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0182] The elements, actions, or instructions used herein should not be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “a certain” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items referenced in conjunction with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Moreover, as used herein, the terms “have,” “contain,” “include,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Moreover, as used herein, the term “or” is intended to be inclusive when used in a sequence and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., in combination with “either of” or “only one of”).

Claims

1. A receiver device for wireless communication, comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, the one or more processors being configured to: Receive management frames on the first link; The management frame is parsed to identify the link identifier and link information included in the management frame, wherein the link identifier corresponds to at least a second link, and wherein the first link and the second link are part of a multi-link setup; The communication configuration of the second link identified by the link identifier is updated at least in part based on the link information.

2. The receiving device of claim 1, wherein the link identifier includes a value associated with the second link.

3. The receiving device of claim 1, wherein the link identifier includes a bitmap associated with the second link.

4. The receiving device of claim 1, wherein the one or more processors configured to receive the management frame are configured to: Receive a Target Wake-up Time (TWT) information frame, wherein the TWT information frame includes the link identifier for updating the scheduling or parameters for the second link.

5. The receiving device of claim 4, wherein the link identifier includes an update to the TWT schedule or parameters for the second link.

6. The receiving device of claim 1, wherein the management frame is addressed to the receiving device.

7. The receiving device as claimed in claim 1, wherein the management frame includes an association request frame or an association response frame.

8. The receiving device of claim 1, wherein the management frame includes a reassociation request frame or a reassociation response frame.

9. The receiving device of claim 1, wherein the link identifier is mapped to cross-link parameters.

10. The receiving device of claim 1, wherein the link identifier is used for cross-link signaling.

11. The receiving device of claim 1, wherein the second link is different from the first link.

12. The receiving device of claim 1, wherein the link identifier is included in a dedicated element of the management frame.

13. A method for wireless communication at a receiving device, comprising: Receive management frames on the first link; The management frame is parsed to identify the link identifier and link information included in the management frame, wherein the link identifier corresponds to at least a second link, and wherein the first link and the second link are part of a multi-link setup; as well as The communication configuration of the second link identified by the link identifier is updated at least in part based on the link information.

14. The method of claim 13, wherein the link identifier includes a value associated with the second link.

15. The method of claim 13, wherein the link identifier includes a bitmap associated with the second link.

16. The method of claim 13, wherein receiving the management frame further comprises: Receive a Target Wake-up Time (TWT) information frame, wherein the TWT information frame includes the link identifier.

17. The method of claim 16, wherein the link identifier includes an update to the TWT schedule or parameters for the second link.

18. The method of claim 13, wherein the management frame includes an association request frame or an association response frame.

19. The method of claim 13, wherein the management frame includes a reassociation request frame or a reassociation response frame.

20. The method of claim 13, wherein the second link is different from the first link.

21. A transmitter device for wireless communication, comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, the one or more processors being configured to: A management frame is transmitted on a first link, wherein the management frame includes a link identifier, wherein the link identifier corresponds to at least a second link, and wherein the first link and the second link are part of a multi-link setup; as well as Update the communication configuration of the second link identified by the link identifier.

22. The transmitting device of claim 21, wherein the link identifier includes a value associated with the second link.

23. The transmitting device of claim 21, wherein the link identifier includes a bitmap indicating the second link.

24. The transmitting device of claim 21, wherein the one or more processors configured to transmit the management frame are configured to: Transmit a Target Wake-up Time (TWT) information frame, wherein the TWT information frame includes the link identifier for updating the scheduling or parameters for the second link.

25. The transmitter device of claim 24, wherein the link identifier includes an update to the TWT schedule or parameters for the second link.

26. The transmitting device of claim 21, wherein the management frame is addressed to the receiving device.

27. The transmitting device of claim 21, wherein the management frame includes an association request frame or an association response frame.

28. The transmitting device of claim 21, wherein the management frame includes a reassociation request frame or a reassociation response frame.

29. The transmitting device of claim 21, wherein the link identifier is mapped to cross-link parameters.

30. The transmitting device of claim 21, wherein the link identifier is used for cross-link signaling.

31. The transmitting device of claim 21, wherein the second link is different from the first link.

32. The transmitting device of claim 21, wherein the link identifier is included in a dedicated element of the management frame.

Images