Mechanisms and processes for low-latency service transmission in WLAN systems

By transmitting high-priority service indications and backoff mechanisms in wireless LANs, the latency and jitter issues of low-latency services are resolved, achieving efficient low-latency service management and meeting the latency and jitter requirements of services.

CN123126022APending Publication Date: 2026-11-17INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580027084.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-10
Filing Date
2025-04-09
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In wireless local area networks (WLANs), existing technologies struggle to effectively manage latency and jitter in low-latency services, causing some services to fail to meet maximum latency and jitter requirements.

Method used

By transmitting indications of high-priority services and associated transmission parameters in the wireless medium, a backoff mechanism is implemented to determine whether there is a conflict, and to transmit high-priority services when there is no conflict, or to postpone transmission.

Benefits of technology

It enables effective management of low-latency services in wireless LANs, ensuring that service transmission efficiency and reliability are improved while meeting latency and jitter requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123126022A_ABST
    Figure CN123126022A_ABST
Patent Text Reader

Abstract

Methods and apparatus are disclosed for a station (STA) in a wireless local area network (WLAN) to indicate its intention to transmit high-priority services (such as low-latency services) over a shared wireless medium. Several embodiments for STAs to transmit a signal called a Low-Latency Service Indication (LLTI) and low-latency services are disclosed. An access point (AP) manages the STAs, which can transmit the LLTI and compete for conditions of the wireless medium for the purpose of transmitting low-latency services, and can solicit the LLTI and low-latency services from the STAs. Several embodiments of the methods and apparatus are disclosed.
Need to check novelty before this filing date? Find Prior Art

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Patent Application Serial No. 18 / 632,118, filed April 10, 2024, the contents of which are incorporated herein by reference in their entirety. Background Technology

[0002] A Wireless Local Area Network (WLAN) in Infrastructure Basic Services Set (BSS) mode has an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP typically has access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic to and from the BSS. Traffic originating outside the BSS and destined for a STA arrives at and is delivered to the STA via the AP. Traffic from a STA to a destination outside the BSS is sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can also be sent via the AP, where the source STA sends the traffic to the AP, and the AP delivers the traffic to the destination STA. For certain types of traffic, referred to herein as "low-latency traffic," such as traffic that may require or be expected to meet certain maximum latency and / or jitter requirements, latency management features may be desired in the WLAN. Summary of the Invention

[0003] The aspects of the embodiments disclosed herein can solve one or more of the above-described problems or needs.

[0004] In some aspects, an embodiment of a method for a Station (STA) is disclosed, the method comprising: transmitting a frame having an indication of a high-priority service and associated transmission parameters via a wireless medium in a wireless local area network (WLAN); performing backoff before transmitting the high-priority service; determining whether a transmission has occurred via the wireless medium during the backoff period; if it is determined that no transmission has occurred via the wireless medium during the backoff period, transmitting the high-priority service via the wireless medium; and if it is determined that a transmission has occurred via the wireless medium during the backoff period, delaying the transmission of the high-priority service via the wireless medium.

[0005] In some aspects, an embodiment of a station (STA) is disclosed, including a transceiver and a processor communicatively coupled to the transceiver, the transceiver and the processor being configured to: transmit a frame having an indication of a high-priority service and associated transmission parameters via a wireless medium in a wireless local area network (WLAN); perform backoff before transmitting the high-priority service; determine whether a transmission has occurred via the wireless medium during the backoff period; if it is determined that no transmission has occurred via the wireless medium during the backoff period, transmit the high-priority service via the wireless medium; and if it is determined that a transmission has occurred via the wireless medium during the backoff period, postpone the transmission of the high-priority service via the wireless medium.

[0006] In some aspects, an embodiment of a method for a site (STA) is disclosed, the method comprising: receiving a high-priority service solicitation from an access point (AP) via a wireless medium in a wireless local area network (WLAN); and, based on the high-priority service solicitation, transmitting, via the wireless medium, at least one of an indication of a high-priority service and a high-priority service.

[0007] In some aspects, an embodiment of a station (STA) is disclosed, including a transceiver and a processor communicatively coupled to the transceiver, the transceiver and the processor being configured to: receive a high-priority service solicitation from an access point (AP) via a wireless medium in a wireless local area network (WLAN); and, based on the high-priority service solicitation, transmit, via the wireless medium, an indication of a high-priority service and at least one of the high-priority services.

[0008] In some aspects, an embodiment of a method for an access point (AP) is disclosed, the method comprising: transmitting a high-priority service solicitation to a station (STA) via a wireless medium in a wireless local area network (WLAN); and receiving, via the wireless medium, at least one of an indication of a high-priority service and a high-priority service, from the STA based on the high-priority service solicitation.

[0009] Other aspects were also disclosed.

[0010] One or more embodiments also provide a computer program including instructions that, when executed by one or more processors, cause the one or more processors to perform a method according to any of the embodiments described herein. Attached Figure Description

[0011] A more detailed understanding can be obtained from the following description, given by way of example in conjunction with the accompanying drawings, wherein the same reference numerals in the drawings denote the same elements, and wherein: Figure 1AThis is a system diagram illustrating an example communication system that can implement one or more of the disclosed embodiments; Figure 1B This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shown is of an example wireless transmit / receive unit (WTRU) used in the communication system. Figure 1C This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shows an example radio access network (RAN) and an example core network (CN) used in the communication system shown. Figure 1D This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shown illustrates another example RAN and another example CN used within the communication system. Figure 2 This is a system diagram illustrating an example wireless local area network (WLAN) that can implement one or more of the disclosed embodiments; Figure 3 This is a timing diagram illustrating a representative operation of setting the TXOP duration to ensure priority access for low-latency services; Figure 4 An exemplary format of Low Latency Service Indication (LLTI) Null Data Packet (NDP) Physical Layer Protocol Data Unit (PPDU) used in WLAN is shown; Figure 5 This is a sequence diagram illustrating a representative process of AP soliciting LLTI; Figure 6 This is a timing diagram illustrating a representative process of an AP soliciting an uplink OFDMA Random Access (UORA) LLTI; and Figure 7 This is a timing diagram illustrating a typical process of the AP soliciting low-latency transmission from UORA. Detailed Implementation

[0012] The methods, devices, and systems presented herein are well-suited for communications involving both wired and wireless networks. For an overview of the various types of wireless devices and infrastructure, please refer to [link / reference]. Figure 1A-1D Provided, wherein the various elements of the network can utilize, perform, be adapted to and / or be configured for the methods, apparatus and systems provided herein.

[0013] Figure 1AThis diagram illustrates an example communication system 100 that can implement one or more of the disclosed embodiments. The communication system 100 may be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access such content through shared system resources including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word Discrete Fourier Transform Extended OFDM (ZT-UW-DFT-S-OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0014] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a station (STA)) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile user units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices (e.g., gaming devices), devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0015] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks such as CN 106, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node Bs, eNodeBs (eNBs), home node Bs, home eNodeBs, next-generation node Bs such as gNodeBs (gNBs), new radio (NR) node Bs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0016] Base station 114a may be part of RAN 104, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a specific geographic area that may be relatively fixed or may change over time. A cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one for each sector of the cell. In embodiments, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0017] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0018] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN 104 and WTRUs 102a, 102b, and 102c can implement radio technologies, such as using Wideband CDMA (WCDMA) to establish Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) for air interface 116. WCDMA can include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink (UL) Packet Access (HSUPA).

[0019] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies, such as using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro) to establish Evolved UMTS Terrestrial Radio Access (E-UTRA) for air interface 116.

[0020] In the embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies, such as using NR to establish NR radio access for air interface 116.

[0021] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for instance, use the dual connectivity (DC) principle to jointly implement LTE radio access and NR radio access. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0022] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., WiFi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0023] Figure 1A Base station 114b can be, for example, a wireless router, a home node B, a home eNodeB, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in localized areas such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for use by drones), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can be directly connected to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN 106.

[0024] RAN 104 can communicate with CN 106, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although... Figure 1AAs not shown, but will be understood, RAN 104 and / or CN 106 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104. For example, in addition to connecting to RAN 104, which may be utilizing NR radio technology, CN 106 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0025] CN 106 can also serve as a gateway for WTRUs 102a, 102b, 102c, and 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 or a different RAT.

[0026] Some or all of the WTRUs 102a, 102b, 102c, and 102d in communication system 100 may include multi-mode capabilities (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example, Figure 1A The WTRU 102c shown can be configured to communicate with a base station 114a that can use cellular-based radio technology and with a base station 114b that can use IEEE 802 radio technology.

[0027] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It will be understood that, while remaining consistent with the embodiments, WTRU 102 may include any sub-combination of the foregoing elements.

[0028] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, which can be coupled to transmitting / receiving element 122. Although Figure 1B While the processor 118 and transceiver 120 are depicted as separate components, it will be understood that the processor 118 and transceiver 120 can be integrated together in an electronic package or chip.

[0029] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF signals and optical signals. It will be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0030] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0031] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, transceiver 120 can include multiple transceivers for enabling WTRU 102 to communicate via various RATs (e.g., such as NR and IEEE 802.11).

[0032] The processor 118 of WTRU 102 can be coupled to and receive user input data from: a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Additionally, the processor 118 can access information and store data from any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access information and store data from memory not actually located on WTRU 102, such as on a server or home computer (not shown).

[0033] The processor 118 may receive power from the power supply 134 and may be configured to distribute power to other components in the WTRU 102 and / or control power to those other components. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0034] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that, while remaining consistent with the embodiments, the WTRU 102 may acquire location information using any suitable location determination method.

[0035] The processor 118 can also be connected to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors. These sensors may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, humidity sensors, etc.

[0036] WTRU 102 may include a full-duplex radio, wherein some or all of the transmission and reception of signals (e.g., associated with a specific subframe of both UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In embodiments, WTRU 102 may include a half-duplex radio, wherein some or all of the transmission and reception of signals (e.g., associated with a specific subframe of either UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0037] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also communicate with CN 106.

[0038] RAN 104 may include eNode-Bs 160a, 160b, and 160c, but it will be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

[0039] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0040] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. While the foregoing elements are depicted as part of CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0041] The MME 162 can connect to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, activating / deactivating bearers, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0042] The SGW 164 can connect to each of the eNodeBs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to or from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during eNodeB handover, triggering paging when DL data is available to WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0043] SGW 164 can be connected to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0044] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional terrestrial line communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108, or can communicate with it. Additionally, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0045] Figure 1D This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also communicate with CN 106.

[0046] RAN 104 may include gNBs 180a, 180b, and 180c, but it will be understood that RAN 104 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Thus, for example, gNB 180a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In embodiments, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be located on unlicensed spectrum, while the remaining component carriers may be located on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0047] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable parameter sets. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can be varied for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes of various or scalable lengths or transmission time intervals (TTIs) (e.g., containing different numbers of OFDM symbols and / or absolute times of varying durations).

[0048] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can use one or more of gNBs 180a, 180b, and 180c as mobile anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c while also communicating / connecting with another RAN (such as eNode-Bs 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobile anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput to serve WTRUs 102a, 102b, and 102c.

[0049] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support for network slicing, interoperability between DC, NR, and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0050] Figure 1DThe CN 106 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although the foregoing elements are depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0051] AMF 182a and 182b can connect to one or more of the gNBs 180a, 180b, and 180c in RAN 104 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating Non-Access Stratum (NAS) signaling, mobility management, etc. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service types being used by WTRU 102a, 102b, and 102c. For example, different network slices can be created for different use cases, such as services that rely on Ultra Reliable Low Latency (URLLC) access, services that rely on Enhanced Massive Mobile Broadband (eMBB) access, and services for MTC access. AMF 182a and 182b can provide control plane functions for handover between RAN 104 and other RANs (not shown) that employ other radio technologies (such as LTE, LTE-A, LTE-A Pro) and / or non-3GPP access technologies (such as WiFi).

[0052] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 106 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 106 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure service routing through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing DL data notifications. PDU session types can be IP-based, non-IP-based, or Ethernet-based.

[0053] UPF 184a and 184b can connect to one or more of the gNBs 180a, 180b, and 180c in RAN 104 via the N3 interface. These gNBs can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering DL packets, and providing mobility anchoring.

[0054] CN 106 can facilitate communication with other networks. For example, CN 106 may include or be able to communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108. Additionally, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c can be connected to DNs 185a and 185b via UPFs 184a and 184b through their N3 interfaces and the N6 interface between UPFs 184a and 184b and local DNs 185a and 185b.

[0055] Given Figures 1A to 1D and Figures 1A to 1D The corresponding descriptions can be performed by one or more emulation devices (not shown) that perform one or more of the functions described herein with respect to: WTRU 102a to 102d, base stations 114a to 114b, eNode-B 160a to 160c, MME 162, SGW 164, PGW 166, gNB 180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b, and / or any other devices described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0056] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices may perform one or more functions when fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices may perform one or more functions when temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices may be directly coupled to another device for testing purposes and / or use over-the-air wireless communication to perform tests.

[0057] One or more simulation devices may perform one or more functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, a simulation device may be used to test scenarios in a laboratory and / or an undeployed (e.g., tested) wired and / or wireless communication network to enable testing of one or more components. One or more simulation devices may be test equipment. Simulation devices may transmit and / or receive data using direct RF connections and / or wireless communication via an RF circuit system (e.g., which may include one or more antennas).

[0058] Despite WTRU in Figures 1A to 1D While described as a wireless terminal, it is envisioned that, in some representative embodiments, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0059] In a representative embodiment, the other network 112 may be a WLAN.

[0060] A WLAN in Infrastructure Basic Services Set (BSS) mode may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may access a Distribution System (DS) or another type of wired / wireless network that loads and / or loads services into and / or out of the BSS, or have an interface to it. Services originating outside the BSS and destined for a STA can be delivered to the AP via it. Services from a STA to a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Services between STAs within the BSS can be sent via the AP, for example, where a source STA can send a service to the AP, and the AP can deliver the service to the destination STA. Services between STAs within the BSS can be considered and / or referred to as point-to-point services. Point-to-point services can be sent between a source STA and a destination STA using a Direct Link Setup (DLS) (e.g., directly between them). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as a "self-organizing" communication mode in this document.

[0061] The AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a bandwidth of 20 MHz) or dynamically configured. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented, for example, in an 802.11 system. For CSMA / CA, each STA (e.g., every STA), including the AP, can sense the primary channel. If a particular STA senses / detects that the primary channel is busy and / or determines that the primary channel is busy, the particular STA can back off for a certain period of time before sensing again. In a given BSS, given any given spatial, temporal, and frequency resources, one STA (e.g., only one station) can transmit.

[0062] In other representative embodiments, the AP can allocate bandwidth resources through which the associated STA communicates with the AP. The bandwidth resources may include one or more channels (i.e., continuous or discontinuous), one or more sub-channels within a channel, one or more resource elements (RUs) within an Orthogonal Frequency Division Multiple Access (OFDMA) system, and the one or more RUs allocated therefrom may be adjacent (i.e., continuous) or discontinuous, occupying one or more channels or sub-channels, etc.

[0063] High-throughput (HT or 802.11n) STAs can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels.

[0064] Very High Throughput (VHT or 802.11ac) STAs can support 20MHz, 40MHz, 80MHz, and / or 160MHz wide channels for transmission in the 5GHz band using OFDMA. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, data, after channel coding, can be passed through a fragment resolver that splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each stream separately. The streams can be mapped onto the two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0065] High-efficiency wireless (HEW or 802.11ax) STAs can support 20MHz, 40MHz, 80MHz, and / or 160MHz wide channels in the 2.4GHz, 5GHz, and 6GHz bands, enabling OFDMA and multi-user multiple-input multiple-output (MU-MIMO) capabilities. OFDMA subcarrier modulation in HE STAs includes formats such as BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, and 1024-QAM. The evolution of 802.11 to Ultra-High Throughput (EHT) STAs extends to channels with a width of 320MHz.

[0066] While earlier generations of 802.11 STAs (e.g., HEW or 802.11ax) could choose to transmit on one of the 2.4, 5.0, or 6 GHz bands, EHT STAs further enable multi-link operation (MLO), allowing data transmission between EHT APs and non-AP STAs to occur simultaneously on multiple bands (e.g., 5 GHz and 6 GHz), thereby increasing throughput and / or reliability. EHT STAs also benefit from the jump in QAM modulation from 1024-QAM to 4K-QAM, achieving peak data rates of approximately 46 Gbps, compared to 9.6 Gbps for HEW STAs.

[0067] The next-generation 802.11 standard, 802.11bn (i.e., Ultra-High Reliability - UHR), explores the possibilities of improving reliability on top of HEW, supporting further reduced low-latency services, further increasing peak throughput, improving energy efficiency, and enhancing the efficiency of IEEE 802.11 networks. These improvements are driven by technological advancements such as 360° immersive video, ultra-high-resolution streaming, online gaming, remote surgery, and the rapid expansion of the Internet of Things (IoT). Other examples of 802.11 standard development target areas such as the application and management of Artificial Intelligence and Machine Learning (AIML) in WLANs, extending WiFi communication to the millimeter-wave band (Integrated Millimeter Wave - IMW), energy harvesting based on WiFi RF signals to facilitate WLAN communication for low-power IoT devices, and MAC address randomization in WLANs.

[0068] Low-latency service channel access According to the existing channel access procedure, IEEE 802.11 sites (STAs) typically perform a random backoff procedure before transmission in each contention period.

[0069] When a STA with frames queued for transmission determines that the radio medium is idle, and the radio medium remains idle for the Distributed Inter-Frame Interval (DIFS) or Extended Inter-Frame Interval (EIFS) period immediately following the end of the preceding medium busy event, the STA may invoke a random backoff procedure. The STA may begin transmission if the radio medium remains idle after the backoff counter (set to a randomly selected initial value) at the STA decrements to 0. The backoff counter is set to an integer value randomly selected in a uniform distribution between 0 and CW[AC], where CW is an integer value between aCWmin and aCWmax, and AC is an index corresponding to the access class (e.g., voice, video, best-effort, background). aCWmin and aCWmax are values ​​set by the AP. The STA (AP or non-AP) sets the initial value of CW to aCWmin. CW is doubled in the event of a collision or transmission failure, but up to aCWmax. After each successful transmission, CW is reset to aCWmin. If no media activity is indicated during the duration of a specific backoff time slot, the backoff process should decrement its backoff counter.

[0070] To support low-latency service transmission, one approach is to allow STAs with low-latency services to transmit a delay signal (DS) without backoff during contention periods. Upon receiving the delay signal, STAs without low-latency services can maintain their contention and wait for the next transmission opportunity (TXOP). Simultaneously, STAs that have just transmitted a delay signal (DS) can initiate a backoff procedure to compete for channel access to transmit their low-latency services. This backoff procedure reduces the chance of transmission conflicts between STAs with low-latency services. It should also be noted that for such STAs, the contention window value (CW) can be smaller than that of traditional STAs or STAs without low-latency services.

[0071] The purpose of delay signals (DS) and similar mechanisms is to aggressively grant access to the medium to STAs with low-latency services, as there is no backoff for DS transmission. However, any aggressive STA, regardless of its potential service type (low latency or not), can always transmit DS at the start of a contention period. If there is one such aggressive STA in the BSS, it will always be able to occupy the medium when it wants. If there is a group of such aggressive STAs in the BSS, this group will always have a higher priority for accessing the medium than other STAs in the BSS. If all STAs in the BSS are aggressive STAs, the situation is similar to traditional channel access, except that DS is always transmitted unnecessarily and becomes additional overhead during any contention period. Therefore, a flexible control mechanism is desired to give high priority to STAs with low-latency services by using DS, while maintaining a degree of fairness among other STAs in the network and preventing deliberately aggressive STAs from unnecessarily occupying the medium.

[0072] In a WLAN, it may be desirable for STAs with low-latency services to have a higher priority in accessing the radio medium than STAs without low-latency services. According to representative embodiments of this disclosure, STAs with low-latency services can transmit such services in a limited or non-backoff manner by first transmitting a signal referred to herein as a Low Latency Service Indication (LLTI), an LLTI signal, or an LLTI frame.

[0073] More than one STA can transmit LLTI signals simultaneously. LLTI signals can be transmitted without backoff. After transmitting an LLTI signal, STAs with low-latency services and / or those that have transmitted LLTI signals may be able to compete for the radio medium. Limited backoff may require the use of backoff procedures with higher priority and / or lower backoff counters, etc. After transmitting an LLTI signal, an STA can execute a backoff procedure, where it randomly determines a backoff period, senses any transmission activity on the radio medium, and if no such activity is sensed during that backoff period, it can proceed to transmit its low-latency service on the radio medium.

[0074] STAs without low-latency services or that are not transmitting LLTI signals can suspend transmission after detecting the transmission of an LLTI signal from another STA. For example, an STA without low-latency services can postpone its channel access after detecting an LLTI signal.

[0075] The above process can be permitted within a specific time period or duration, such as within TXOP, within a beacon interval, or for any contention period, which can be given dynamically or semi-statically.

[0076] Figure 2 An example WLAN 200 is shown, including STA 202, STA 206, STA 208, and AP 210. WLAN 200 is in Infrastructure Basic Services Set (BSS) mode, and STAs 202, 206, and 208, along with AP 210, are considered to constitute a BSS. Figure 2 In the illustrative scenario depicted, STA 202 has transmitted LLTI frame 204 to indicate its need to transmit low-latency service and to notify non-low-latency transmitting STAs to postpone the transmission of their services. The transmission of LLTI frame 204 is based on LLTI management element 205 received from, for example, AP 210. LLTI management element 205 provides one or more conditions for managing the transmission of low-latency service by facilitating and managing the transmission of LLTI frame 204. Representative content of LLTI management element 205 is described in U.S. Patent Application No. ____, filed on the same date as this application, Attorney General's File No. 2024P00230 US, which is incorporated herein by reference in its entirety.

[0077] LLTI signal transmission Several embodiments and variations thereof for transmitting LLTI signals will now be described.

[0078] Method I According to a representative embodiment of this disclosure, the transmission of the LLTI signal can be performed in such a manner that, after the LLTI signal is transmitted, a conventional STA will use an extended inter-frame spacing (EIFS) before contention or transmission of the radio medium. In such an implementation, the LLTI can be carried by a physical layer protocol data unit (PPDU), referred to herein as a UHR or UHR+ PPDU, where “UHR+” indicates any generation of 802.11 standard after UHR / 802.11bn.

[0079] When a STA determines that the medium is idle after a frame containing an erroneous PPDU or an incorrect Frame Check Sequence (FCS) value in the PHY_RXEND.indication primitive, the STA can use EIFS before transmitting on the medium. Therefore, one way to force a conventional STA to use EIFS is to have the STA issue a PHY_RXEND.indication primitive containing an error.

[0080] A traditional STA may be able to detect the L-SIG field of a UHR PPDU, but it will not understand other SIG fields of the UHR PPDU, such as the SIG field used for UHR or UHR+ first-generation WiFi signals. Therefore, for UHR / UHR+ PPDUs carrying LLTI, a traditional STA will issue a PHY_RXEND.indication primitive containing an error and / or the Frame Check Sequence (FCS) value will be incorrect.

[0081] In a representative embodiment, the LLTI signal can be transmitted on the primary 20MHz channel. A conventional STA in the same BSS can detect the transmission on the primary 20MHz channel and suspend contention for the medium during the subsequent EIFS period. An LLTI-aware STA can detect the transmission on the primary 20MHz channel and know that it is an LLTI signal, and therefore can avoid performing any transmission on the primary and / or secondary channels during the TXOP duration of the LLTI.

[0082] When the LLTI is carried by a UHR / UHR+ PPDU, the signaling fields of the UHR / UHR+ PPDU (e.g., U-SIG, UHR-SIG, etc.) can be set according to the following rules: The BW field can be set to indicate the bandwidth of the UHR / UHR+ PPDU carrying LLTI. For example, the BW field can be set to 20MHz.

[0083] • The TXOP field can be set to a value that allows STAs that understand the TXOP field to set a network allocation vector (NAV) long enough to cover the maximum possible contention period after an LLTI transmission. Figure 3 This illustrates setting the TXOP duration to ensure priority access for low-latency services. In this example, the maximum contention period for the LLTI can be predefined or determined and broadcast by the AP. The maximum contention period for the LLTI can be the maximum backoff duration for the STA to access the radio medium immediately after its LLTI transmission. The TXOP field in the U-SIG field can be set to a value equal to or approximately equal to the maximum contention period for the LLTI. Unexpected UHR / UHR+ STAs (i.e., STAs that do not transmit the LLTI for the current TXOP, e.g.) Figure 3In the example, STA3 can use the TXOP field to set its NAV. This allows an unexpected UHR STA to compete after the period indicated by its NAV setting. STAs that transmit LLTI can back off immediately after the LLTI. Because the backoff duration is less than the maximum competition period, and therefore less than the NAV set by the unexpected STA, one of the STAs that transmitted LLTI will be guaranteed channel access. Figure 3 In the example scenario shown, STA2 acquires the channel.

[0084] • The BSS Color field can be set to indicate the BSS color of the BSS. This allows PPDUs carrying LLTIs to vary from BSS to BSS. Alternatively, the BSS Color field can be set to an unassigned value so that STAs from different BSSs can have the same value.

[0085] The UL / DL field can be set to UL. When an AP and a non-AP STA are simultaneously transmitting LLTI, the AP may need to set the UL / DL field to UL so that overlapping LLTI PPDUs from the AP and non-AP STAs can be identical, allowing the STA receiving the overlapping LLTI PPDUs to decode them. Alternatively, the UL / DL field can be set to DL, even if it is transmitted by a non-AP STA. The baseline is that all current LLTI transmitters on the same BSS and / or different BSSs set this field to the same value so that the receiving STA can decode the PPDU.

[0086] In a representative embodiment, the LLTI can be carried by a UHR / UHR+Null Data Packet (NDP) PPDU. An exemplary format of this LLTINDP 400 is as follows: Figure 4 As shown.

[0087] LLTI NDP 400 may include L-STF field 402, L-LTF field 404, L-SIG field 406, RL-SIG field 408, and U-SIG field 410. Packet Extension (PE) field 412 may be included at the end of the LLTI NDP.

[0088] In a representative embodiment, the LLTI NDP 400 can be implicitly indicated via the length field in the L-SIG field 406. The TXTIME of the LLTI NDP 400 can be set to override all fields of the LLTI NDP 400. For example, if... Figure 4 The example LLTI NDP 400 shown does not have a PE field 412, so TXTIME = 8+8+4+4+8 = 32 and SignalExtension = 0. Following existing methods... 6(1) In other words, for this LLTI NDP 400, the length field in its L-SIG field 406 will be set to 6. Furthermore, the PHY version identifier field in its U-SIG field 410 will be set to indicate that the LLTI NDP 400 is a UHR / UHR+PPDU. Thus, the STA receiving this PPDU can determine that the PPDU is a UHR / UHR+ LLTI NDP, such as... Figure 4 As shown.

[0089] In a representative embodiment, the TXTIME parameter is returned by the PLME-TXTIME.confirm primitive, as described in IEEE P802.11be™ / D5.0 “Information Technology Standards Draft – Inter-System Telecommunications and Information Exchange – Local Area Networks and Metropolitan Area Networks – Specific Requirements, Part 11: Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification, Amendment 8: Ultra High Throughput (EHT) Enhancement,” November 2023, Section 36.4.3 TXTIME and PSDU_LENGTH calculations. Expression (1) is Equation 36-17 in Section 36.3.12.5 L-SIG of the same document. SignalExtension is described in IEEE P802.11-REVme™ / D5.0 “Information Technology Standards Draft – Inter-System Telecommunications and Information Exchange – Local Area Networks and Metropolitan Area Networks – Specific Requirements, Part 11: Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification,” February 2024, Table 27-61 – HE PHY Characteristics.

[0090] In a representative embodiment, the LLTI NDP 400 can be explicitly indicated by one or more fields in the U-SIG field 410. For example, the PHY version identifier field in the U-SIG field 410 of the LLTI NDP will be set to indicate that its PHY version is UHR / UHR+. A PPDU type field may be included in the U-SIG field 410 to indicate that the PPDU is a UHR / UHR+ LLTINDP.

[0091] Method II In a representative embodiment, the LLTI may be carried in a frame referred to herein as an LLTI frame. The LLTI frame may be a control frame.

[0092] In a representative embodiment, the LLTI frame can be carried within a conventional PPDU, such as a non-HT PPDU or a non-HT DupPPDU. The SIG field in the PPDU can be set according to certain rules so that concurrent transmissions of PPDUs carrying LLTI frames from multiple STAs can be identical.

[0093] The duration field of an LLTI frame can be set to allow an unintended STA to set a sufficiently long NAV to cover the value of the maximum possible contention period immediately following the LLTI. In such implementations, the maximum contention period of the LLTI can be predefined or determined and broadcast by the AP. The maximum contention period of the LLTI can be the maximum backoff duration for the STA to access the radio medium immediately after its LLTI transmission. The duration field in the MAC header of the LLTI frame can be set to a value equal to or approximately equal to the maximum contention period of the LLTI. Unintended UHR / UHR+ STAs can use the duration field of the LLTI frame to set their NAV. An unintended legacy STA may not understand that it is an LLTI frame, but it may be able to decode the duration field of the frame and use it to set its NAV.

[0094] The L-SIG field of a PPDU carrying an LLTI frame can have a rate of 6 Mb / s.

[0095] The TXVECTOR parameter SCRAMBLER_INITIAL_VALUE of the PPDU carrying the LLTI frame can be set to a fixed value so that all STAs can use the same scrambling seed to transmit the LLTI frame, and therefore the LLTI frame can remain identical and decodeable if multiple STAs transmit LLTI frames simultaneously. In a representative embodiment, the parameter can be set to the TXVECTOR parameter SCRAMBLER_INITIAL_VALUE of the last PPDU received by the STA before the LLTI frame, or set to a predefined value. In a representative embodiment, the AP can choose a value for the parameter and broadcast it in management frames (e.g., beacon frames, probe response frames, association response frames) or control frames.

[0096] The bandwidth signaling transmit address (TA) may not be used in the LLTI frame. If the TA is not used, the TXVECTOR parameter CH_BANDWIDTH_IN_NON_HT may not exist.

[0097] The Power Management and More Data subfields of the Frame Control field in an LLTI frame can be set to 0 (or another value). Other subfields of the Frame Control field in an LLTI frame should be set so that LLTI frames transmitted from different STAs are identical. In a representative embodiment, all PPDU and frame-related information are identical for all LLTI PPDUs and frames.

[0098] In a representative embodiment, the LLTI can be carried in a field of the Media Access Control (MAC) header of the frame, such as the HT Control, A-Control, or QoS Control field. In a representative embodiment, the LLTI can be carried in a QoS empty frame, where the MAC header may contain a QoS Control field, but the MAC body is absent. For example, the 7th bit of a QoS empty frame can be used for the LLTI. In another example, the 7th bit of the QoS Control field of the empty frame can be used to indicate that the QoS empty frame carries an LLTI.

[0099] Method III In a representative embodiment, the LLTI can be solicited by the AP. The AP can allow the STA to transmit the LLTI over the entire available bandwidth or over bandwidths that are multiples of 20 MHz, so LLTI transmissions can overlap. Thus, the solicited LLTI can be carried by a PPDU of a pre-selected format, such as a non-HT PPDU, a non-HT Dup PPDU, or a UHR / UHR+ PPDU, etc.

[0100] An exemplary process for AP to solicit LLTI is as follows: Figure 5 As shown. Through this process, the AP can transmit frames to determine whether any associated or nearby STAs (including unassociated STAs) have low-latency services. For example, the AP can transmit a special frame, referred to herein as a Low-Latency Polling (LLP) frame, to solicit LLTI transmissions from STAs. The LLP frame can carry a field to indicate that it is an LLP frame. In a representative embodiment, the LLP frame can be a trigger frame. A new trigger type value can be defined and used to indicate that this trigger frame is an LLP trigger frame. Alternatively, a special association ID (AID) value can be carried in the AID field of the user information or special user information field to indicate that the frame is an LLP trigger frame or that the trigger frame carries low-latency polling information. In the case where the AID12 in the user information field of the trigger frame is used to indicate LLP, the trigger frame can allocate UL resources for LLTI and other types of trigger-based transmissions. Since the AP may not know which STA will respond to the LLP trigger frame by transmitting LLTI, the receiver address (RA) field of the LLP frame can be set to a broadcast address. The duration field of the LLP frame can be set to cover a possible contention period after the LLTI transmission. The duration field can be set to cover the maximum contention period of the LLTI, and also takes into account the time between the STA receiving the LLP frame and the STA transmitting the LLTI, as well as the time spent by the STA transmitting the LLTI. This duration is... Figure 5 As shown in the diagram, an LLP frame can allocate UL resources for an LLTI transmission. For example, it can indicate one or more 20MHz subchannels allocated to an LLTI transmission. The allocated subchannels may include a primary 20MHz subchannel.

[0101] STAs with low-latency services can respond to LLP frames with trigger-based (TB) PPDUs, non-HT PPDUs, or non-HT duplicate PPDUs carrying LLTI. These LLTI PPDUs can be transmitted at the inter-frame interval xIFS following the receipt of the LLP frame. "xIFS" refers to a specific inter-frame interval, such as the Short Inter-Frame Inter-Inter ...

[0102] In TB, non-HT, or non-HT replicated PPDUs carrying LLTI, all fields in L-SIG and UHR or UHR+ SIG can be specified to be set to the same value so that overlapping LLTI PPDUs from multiple STAs can be decoded.

[0103] In a representative embodiment, LLTI PPDUs from multiple STAs can be identical (i.e., the PLCP header and MAC frame are the same) so that overlapping LLTI PPDUs can be decoded. However, since LLTIs from different STAs will be identical, the lack of STA-specific information means the AP will be unable to distinguish which STA transmitted the LLTI.

[0104] It should be noted that the rules for setting the SIG field and / or field / subfield of the MAC frame for LLTI disclosed in Methods I and II can be applied to Method III and Method IV as described below.

[0105] After the LLTI transmission, during the xIFS period, the STA that transmitted the LLTI can initiate the backoff procedure. In a representative embodiment, xIFS can be zero or SIFS. The duration of the backoff procedure can be limited by the maximum contention period of the LLTI parameter. The maximum contention period of the LLTI parameter can be predefined in the standard or selected and signaled by the AP, for example, in a beacon frame.

[0106] In a representative embodiment, the AP can configure the LLP frame to indicate that it is polling low-latency services above a certain priority threshold. In at least some of these embodiments, the LLP frame can be a basic trigger frame format, and the priority threshold can be indicated in a trigger-related user information subfield, for example, preferably the AC field. In a representative embodiment where the LLP frame is a newly defined LLP trigger frame, as described above, the service priority field with the priority threshold can be carried in a common information field, a user information field, a special user information field, and / or some other trigger-related information fields. It may be desirable to indicate the priority threshold in the LLP frame if it may change dynamically from time to time. If the priority threshold is static or substantially static, it can be indicated in, for example, a management frame. STAs that transmit LLTI in response to the LLP frame can indicate their priority in the LLTI.

[0107] Method IV In a representative embodiment, the LLTI can be solicited by an AP, which can allocate a set of resource units (RUs) for any STA responding to the solicitation to perform an uplink OFDMA random access (UORA) transmission to carry the LLTI. Thus, the solicited LLTI can be carried by a UHR / UHR+ TB PPDU. An LLTI transmitted using UORA may also be referred to herein as a UORA LLTI.

[0108] In this implementation, similar to Method III, the AP can transmit an LLP frame to determine if any associated or nearby STAs have low-latency service. The LLP frame may carry a field indicating that it is an LLP frame. In a representative embodiment, the LLP frame may be a trigger frame. A new trigger type value can be defined and used to indicate that this trigger frame is an LLP trigger frame. Alternatively, a special association ID (AID) value can be carried in the AID field of the user information or special user information field to indicate that the frame is an LLP trigger frame or that the trigger frame carries low-latency polling information. The trigger type value and / or special AID value can further indicate that the LLP frame solicits LLTI transmitted using UORA. The receiver address (RA) field of the LLP frame can be set to a broadcast address because the AP may not know which STA will respond to the LLP trigger frame by transmitting an LLTI.

[0109] As described in Method III above, in a representative embodiment, the AP can configure an LLP frame to indicate that it is polling low-latency services above a certain priority threshold. In at least some of these embodiments, the LLP frame can be a basic trigger frame format, and the priority threshold can be indicated in a trigger-related user information subfield, for example, preferably the AC field. In a representative embodiment where the LLP frame is a newly defined LLP trigger frame, as described above, the service priority field with the priority threshold can be carried in a common information field, a user information field, a special user information field, and / or some other trigger-related information fields. It may be desirable to indicate the priority threshold in the LLP frame if it may change dynamically from time to time. If the priority threshold is static or substantially static, it can be indicated in, for example, a management frame. STAs that transmit an LLTI in response to an LLP frame can indicate their priority in the LLTI.

[0110] Figure 6 An exemplary process is shown, illustrating the AP soliciting the UORA LLTI and subsequently transmitting low-latency services from one or more STAs. Figure 6 In the process, the AP transmits an LLP frame configured to solicit UORA LLTI, and its duration field is set to cover the duration of the LLTI frame plus the xIFS inter-frame interval. xIFS can be, for example, SIFS, twice SIFS, or another multiple of SIFS. Upon receiving the LLP frame, a STA with low-latency service satisfying certain priority conditions (such as those specified in the LLP frame or the general LLTI protocol) can randomly select a user information field from the LLP frame and use the Random Access Resource Unit (RA-RU) or RA-RU specified in that user information field to transmit its LLTI. In a representative embodiment, such an LLTI frame may have... Figure 4The UHR / UHR+ LLTI NDP format shown carries the fields illustrated therein. Additionally, the LLTI frame may carry some user-specific fields, such as the UHR / UHR+ SIG field. The LLTI frame may contain STA-specific information, including one or more of the following: the STA's ID and / or address, its low-latency service QoS information, and the duration of its requested low-latency service transmission. Note that the rules for setting the SIG field of the LLTI and the field / subfield of the MAC frame as disclosed in Methods I through III also apply here. The PPDU and / or MAC frame carrying the LLTI may also carry one or more of the following fields: such as the proposed MCS, LL service size / length, LL delay limit, and LL service TID / AC. The proposed MCS may indicate the proposed MCS for the STA (e.g., a non-AP STA) so that the AP can allocate the MCS for the STA in a subsequent trigger frame. The LL service size / length may indicate the low-latency service size / length for the STA (e.g., a non-AP STA) so that the AP can estimate the maximum UL data length to be used in the TB PPDU across all users and correctly allocate the UL length field in a subsequent trigger frame. LL delay limits indicate the urgency of a STA's need to transmit low-latency services. This information helps the AP schedule UL transmissions in the appropriate order. The Service Identifier (TID) and / or Access Class (AC) of a low-latency service can indicate the TID and / or AC of a STA (e.g., a non-AP STA) for its low-latency service, allowing the AP to associate the TID / AC with the low-latency service and use this information, for example, to ensure compliance with applicable LLTI transmission rules.

[0111] If a given RA-RU is used by only one STA to transmit its LLTI, the AP will be able to decode that LLTI. Otherwise, if multiple STAs transmit their LLTIs on the same RA-RU or multiple RA-RUs, the AP cannot decode conflicting LLTIs. The AP then sends a trigger frame (TF) to further facilitate low-latency data transmission for those surviving STAs that have captured the RA-RU without collisions. Figure 6 In the example scenario depicted, STA1 and STA2 have transmitted their respective LLTIs on different RA-RUs without conflict, thus representing the aforementioned surviving STAs.

[0112] In the TF, the AP can set the duration of subsequent low-latency transmissions. When setting this duration, the AP can consider the requested low-latency service transmission duration information received in the decoded LLTI. In each of one or more user information fields in the TF, the AP can specify the AID, resource unit allocation, and other information for each of one or more surviving STAs for its low-latency data transmission. Upon receiving the TF, all STAs coordinated by the TF will send their low-latency services according to the TF's specifications. Figure 6 In the example scenario, STA1 and STA2 send their low-latency services according to the TF's specifications.

[0113] In such Figure 7 In another exemplary method shown, the AP does not solicit LLTI, but instead solicits low-latency services from the STA. For example... Figure 7 As described, the AP can send an LLP frame to indicate that it has reserved the NAV duration for low-latency services above a certain priority threshold after the LLP frame. The LLP frame can allocate a set of RA-RUs for STAs to perform uplink OFDMA random access (UORA) transmissions for their low-latency services. Each STA then randomly grabs one of these RA-RU allocations and transmits its low-latency service. Note that STAs can do this without first transmitting an LLTI. If only one STA transmits on a certain RA-RU allocation, its transmission can be successfully decoded at the AP; otherwise, if multiple STAs transmit on the same RA-RU allocation, their PPDUs will conflict and may not be decoded at the AP. If this occurs, the AP can repeat the process according to this method or any other method described herein.

[0114] It should be noted that although a trigger frame is used to carry the LLP in the described process and examples, the LLP can be carried by other frames. For example, the LLP can be carried by the Trigger Response Schedule (TRS) field in the HT control field. Reserved bits in the TRS field can indicate that the TRS field carries the LLP. This can be accomplished through embodiments according to methods III and IV.

[0115] Furthermore, in representative embodiments according to methods III and IV, the AP can configure the LLP to solicit LLTI and / or traffic from one or more specific STAs by indicating the ID and / or address of the expected STA in the LLP. In a representative embodiment, the AP can configure the LLP to indicate that it is polling periodic low-latency traffic.

[0116] Although this disclosure refers to "low-latency services," the methods and apparatus disclosed herein are not limited to low-latency services, but can also be implemented for other types of high-priority services, services that may require or expect to provide high-priority transmission, or transmissions with a higher priority than non-high-priority services. Therefore, for example, an indication such as the aforementioned LLTI that can be used for high-priority services can be referred to as a High-Priority Service Indicator (HPTI) or an indication for high-priority services, which contains some or all of the same information as the LLTI or its equivalents.

[0117] Various numerical values ​​are used in this disclosure. These specific values ​​are for illustrative purposes only, and the aspects described are not limited to these specific values.

[0118] This document describes various methods, and each method includes one or more steps or actions for implementing the described method. Unless the correct operation of the method requires a specific order of steps or actions, the order and / or use of specific steps and / or actions can be modified or combined. Furthermore, terms such as "first," "second," etc., may be used in various embodiments to modify elements, components, steps, operations, etc. The use of such terms does not imply an ordering of the modified operations unless specifically required. Therefore, in this example, the first operation does not need to be performed before the second operation and may occur, for example, before, during, or within an overlapping period of time with the second operation.

[0119] The implementations and aspects described herein can be implemented, for example, in a method or process, an apparatus, a software program, a data stream, or a signal. Even if discussed only in the context of a single form of implementation (e.g., discussed only as a method), the implementation of the features discussed can also be implemented in other forms (e.g., an apparatus or a program). An apparatus can be implemented, for example, in appropriate hardware, software, and firmware. A method can be implemented, for example, in an apparatus, such as a processor, which refers to a general-purpose processing device, including, for example, a computer, a microprocessor, an integrated circuit, or a programmable logic device. A processor also includes communication devices, such as a computer, a cellular phone, a portable / personal digital assistant (“PDA”), and other devices that facilitate information communication between end users.

[0120] The reference to "an embodiment" or "an implementation" or "an implementation" and its other variations means that a particular feature, structure, characteristic, etc., described in connection with that embodiment is included in at least one embodiment. Therefore, the appearance of the phrase "in an embodiment" or "in an implementation" or "in an implementation" and any other variations in different places throughout this disclosure does not necessarily refer to the same embodiment.

[0121] Furthermore, this disclosure may refer to "determining" various types of information. Determining information may include, for example, one or more of estimated information, calculated information, predicted information, or information retrieved from memory.

[0122] Furthermore, this disclosure may refer to "accessing" various types of information. Accessing information may include, for example, receiving information, retrieving information (e.g., from memory), storing information, moving information, copying information, calculating information, determining information, predicting information, or estimating information, or more of these.

[0123] Furthermore, this disclosure may refer to "receiving" various types of information. Like "accessing," "receiving" is intended to be a broad term. Receiving information may include, for example, accessing information or retrieving information (e.g., from memory) or more. Moreover, "receiving" generally refers to information in some way during operation, such as storing information, processing information, transmitting information, moving information, copying information, erasing information, calculating information, determining information, predicting information, or estimating information.

[0124] It should be understood that the use of any of the following “ / ”, “and / or”, and “at least one”, for example, in the cases of “A / B”, “A and / or B”, and “at least one of A and B”, is intended to cover selecting only the first listed option (A), or only the second listed option (B), or both options (A and B). As another example, in the cases of “A, B, and / or C” and “at least one of A, B, and C”, such wording is intended to cover selecting only the first listed option (A), or only the second listed option (B), or only the third listed option (C), or only the first and second listed options (A and B), or only the first and third listed options (A and C), or only the second and third listed options (B and C), or all three options (A, B, and C). As will be apparent to those skilled in the art and related fields, this can be extended to as many items as possible listed.

[0125] As will be apparent to those skilled in the art, implementations can generate signals of various formats to carry information, which may, for example, be stored or transmitted. The information may include, for example, instructions for performing a method, or data generated by one of the described implementations. For example, the signal may be formatted to carry a bitstream of the described embodiments. Such a signal may be formatted, for example, as an electromagnetic wave (e.g., using the radio frequency portion of the spectrum) or as a baseband signal. Formatting may include, for example, encoding a data stream and modulating a carrier wave with the encoded data stream. The information carried by the signal may be, for example, analog or digital information. The signal may be transmitted via various different wired or wireless links, as known. The signal may be stored on a processor-readable medium.

[0126] Although the features and elements of the invention are described in specific combinations in preferred embodiments, each feature or element may be used alone without other features and elements of the preferred embodiments, or in various combinations with or without other features and elements of the invention. While the solutions described herein contemplate the 802.11-specific protocol, it should be understood that the solutions described herein are not limited to this specific implementation and are also applicable to other wireless systems.

[0127] Although SIFS can be used to indicate various inter-frame intervals in the design and flow examples, all other inter-frame intervals, such as RIFS, AIFS, DIFS, or other agreed time intervals, can be applied in the same solution. The Long Training Field (LTF) can be any type of predefined sequence known on both the transmitter and receiver sides.

[0128] Although the features and elements have been described above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. Furthermore, the methods described herein can be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM discs and digital multifunction disks (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method for a site (STA), the method comprising: In a wireless local area network (WLAN), frames with indications of high-priority services and associated transmission parameters are transmitted over a wireless medium. Perform a backoff before transmitting the high-priority service; Determine whether a transmission has occurred via the wireless medium during the backoff period; If it is determined that no transmission occurred via the wireless medium during the backoff period, the high-priority service is transmitted via the wireless medium. as well as If it is determined that a transmission has already occurred via the wireless medium during the backoff period, the transmission of the high-priority service via the wireless medium is postponed.

2. The method according to claim 1, wherein, The instructions are included in the PPDU.

3. The method according to claim 2, wherein, The PPDU is at least one of UHR, UHR+, non-HT, non-HT copy, and NDPPPDU.

4. A method for a site (STA), the method comprising: In a wireless local area network (WLAN), high-priority service requests are received from an access point (AP) via a wireless medium. as well as Based on the high-priority service solicitation, an indication of a high-priority service and at least one of the high-priority services are transmitted via the wireless medium.

5. The method according to claim 4, wherein, The instructions are included in TB, non-HT, non-HT copy, UHR, or UHR+PPDU.

6. The method according to claim 4, wherein, The solicitation is included in the trigger frame.

7. The method according to claim 4, wherein, The instruction is to use the entire bandwidth or a portion of the bandwidth of the wireless medium for transmission, wherein the portion of the bandwidth is a multiple of 20 MHz.

8. The method according to claim 4, wherein, The high-priority service is transmitted using one or more random access resource units.

9. The method according to any one of claims 1 to 8, wherein, The high-priority services include low-latency services.

10. A site (STA) comprising: A transceiver and a processor communicatively connected to the transceiver, the transceiver and the processor being configured to: In a wireless local area network (WLAN), frames with indications of high-priority services and associated transmission parameters are transmitted over a wireless medium. Perform a backoff before transmitting the high-priority service; Determine whether a transmission has occurred via the wireless medium during the backoff period; If it is determined that no transmission occurred via the wireless medium during the backoff period, the high-priority service is transmitted via the wireless medium. as well as If it is determined that a transmission has already occurred via the wireless medium during the backoff period, the transmission of the high-priority service via the wireless medium is postponed.

11. The STA according to claim 10, wherein, The instructions are included in the PPDU.

12. The STA according to claim 11, wherein, The PPDU is at least one of UHR, UHR+, non-HT, non-HT copy, and NDPPPDU.

13. A site (STA), comprising: A transceiver and a processor communicatively connected to the transceiver, the transceiver and the processor being configured to: Receiving high-priority service requests from an access point (AP) via wireless media in a wireless local area network (WLAN); and Based on the high-priority service solicitation, an indication of a high-priority service and at least one of the high-priority services are transmitted via the wireless medium.

14. The STA according to claim 13, wherein, The instructions are included in TB, non-HT, non-HT copy, UHR, or UHR+PPDU.

15. The STA according to claim 13, wherein, The solicitation is included in the trigger frame.

16. The STA according to claim 13, wherein, The instruction is to use the entire bandwidth or a portion of the bandwidth of the wireless medium for transmission, wherein the portion of the bandwidth is a multiple of 20 MHz.

17. The STA according to claim 13, wherein, The high-priority service is transmitted using one or more random access resource units.

18. A method for an access point (AP), the method comprising: In a wireless local area network (WLAN), a high-priority service solicitation is transmitted to a station (STA) via a wireless medium. as well as Based on the high-priority service solicitation, the STA receives, via the wireless medium, an indication of a high-priority service and at least one of the high-priority services.

19. The method of claim 18, wherein, The instructions are included in TB, non-HT, non-HT copy, UHR, or UHR+PPDU.

20. The method according to claim 18, wherein, The solicitation is included in the trigger frame.

21. The method of claim 18, wherein, The instruction is to use the entire bandwidth or a portion of the bandwidth of the wireless medium for transmission, wherein the portion of the bandwidth is a multiple of 20 MHz.

22. The method according to claim 18, wherein, The high-priority service is transmitted using one or more random access resource units.

23. The method according to any one of claims 18 to 22, wherein, The high-priority services include low-latency services.