WO2024151927A1 - Procédés de conception de mld et procédures pour uhr dans un wlan - Google Patents

Procédés de conception de mld et procédures pour uhr dans un wlan Download PDF

Info

Publication number
WO2024151927A1
WO2024151927A1 PCT/US2024/011365 US2024011365W WO2024151927A1 WO 2024151927 A1 WO2024151927 A1 WO 2024151927A1 US 2024011365 W US2024011365 W US 2024011365W WO 2024151927 A1 WO2024151927 A1 WO 2024151927A1
Authority
WO
WIPO (PCT)
Prior art keywords
dmld
link
aps
sta
mmld
Prior art date
Application number
PCT/US2024/011365
Other languages
English (en)
Inventor
Xiaofei Wang
Zinan Lin
Hanqing Lou
Original Assignee
Interdigital Patent Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Interdigital Patent Holdings, Inc. filed Critical Interdigital Patent Holdings, Inc.
Publication of WO2024151927A1 publication Critical patent/WO2024151927A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • a wireless local area network (WLAN) in Infrastructure Basic Service 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 interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in and out of the BSS.
  • Traffic to STAs that originates from outside the BSS arrives through the AP and is delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS is sent to the AP to be delivered to the respective destinations.
  • Traffic between STAs within the BSS may also be sent through the AP where a source STA sends traffic to the AP and the AP delivers the traffic to a destination STA.
  • Such traffic between STAs within a BSS is peer-to-peer traffic.
  • Such peer-to-peer traffic may also be sent directly between the source and destination STAs with a direct link setup (DLS) using an 802.11e DLS or an 802.11z tunneled DLS (TDLS)
  • DLS direct link setup
  • TDLS 802.11z tunneled DLS
  • IBSS Independent BSS
  • This mode of communication is referred to as an “ad-hoc” mode of communication
  • a method and apparatus are disclosed where a first access point (AP) may be affiliated with a distributed multi-link device (DMLD).
  • the DMLD may comprise APs affiliated with the DMLD.
  • the first AP may be configured to receive a multi-link probe request message from a station (STA).
  • the first AP may be configured to send a multi-link probe response message to the STA.
  • the multi-link probe response message may comprise a DMLD element.
  • the DMLD element may comprise at least information regarding APs that are affiliated with the DMLD.
  • the APs that are affiliated with the DMLD may be in different locations.
  • the multi-link probe request message may be a request for information regarding a coordinating set of APs of the first AP.
  • the multi-link probe request message may be a request for information regarding coordination for a particular operation.
  • the DMLD element may comprise information regarding neighboring APs to the first AP
  • the DMLD element may comprise information regarding collaborating APs of the APs that are affiliated with the DMLD for a particular coordinated operation.
  • the coordinated operation may comprise seamless roaming or redundancy transmission for low latency and high reliability traffic.
  • the DMLD element may comprise an element identification (ID) field and an element ID extension field that indicates that the DMLD element is a multi-link element.
  • the DMLD element may comprise a multi-link control field.
  • the multi-link control field may comprise a type subfield that indicates that the DMLD element is a DMLD variant of a multi-link element.
  • the DMLD element may comprise a multi-link control field.
  • the multi-link control field may comprise a presence bitmap subfield that indicates which optional fields are present in the DMLD element.
  • the DMLD element may comprises a DMLD capabilities subfield.
  • the DMLD capabilities subfield may comprise at least one of: a maximum simultaneous links per channel information, a maximum simultaneous links information, a seamless roaming capable information, and a coordinated operations supported information.
  • FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
  • WTRU wireless transmit/receive unit
  • FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
  • RAN radio access network
  • CN core network
  • FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment
  • FIG. 2 show an example design of a DMLD element using multi-link element format
  • FIG. 3 shows an example method of DMLD discovery
  • FIG. 4 shows an example method of DMLD discovery
  • FIG. 5 shows an example design of an MMLD element
  • FIG. 6 shows an example association and authentication architecture for MMLD
  • FIG. 7 shows an example MMLO GTK KDE format
  • FIG. 8 shows an example MMLO IGTK KDE format
  • FIG. 9 shows an example MMLO BIGTK KDE format
  • FIG. 10 shows an example of MMLD setup with one non-AP MLD associated with two AP MLDs
  • FIG. 11 shows an example of multiple individual TWT agreements with multiple AP MLDs initiated by a single STA
  • FIG. 12 shows an example of an enhanced TWT element format
  • FIG. 13 shows an example of an Enhanced control field in enhanced TWT element
  • FIG. 14 shows an example of enhanced individual TWT Parameter Set field format
  • FIG. 15 shows an example of an individual TWT agreement with MMLD operation.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 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), singlecarrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA singlecarrier FDMA
  • ZT-UW-DFT-S- OFDM zero-tail unique-word discrete Fourier transform Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications 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, though itwill be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs wireless transmit/receive units
  • RAN radio access network
  • CN core network
  • PSTN public switched telephone network
  • Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and/or the other networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (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 wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using NR.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g , an eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e , Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e , Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g, for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g, WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106.
  • the RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc, and/or perform high-level security functions, such as user authentication.
  • the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
  • the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g, the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1 A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit)
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the 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.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 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, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors.
  • the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e g., associated with particular subframes for both the 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 either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e g., for transmission) or the DL (e g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e g., for transmission) or the DL (e g., for reception)).
  • FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1C 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 the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WLAN in Infrastructure Basic Service 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 have access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • DS Distribution System
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to- peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non- contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • IFFT Inverse Fast Fourier Transform
  • time domain processing may be done on each stream separately
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac.
  • 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine- Type Communications (MTC), such as MTC devices in a macro coverage area.
  • MTC Meter Type Control/Machine- Type Communications
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g. , only support for) certain and/or limited bandwidths
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802 11 n, 802.11ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface. [0069] The CN 106 shown in FIG.
  • 1 D 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. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like.
  • PDU protocol data unit
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • the AMF 182a, 182b may provide a control plane function for switching between the 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.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.
  • the CN 106 may facilitate communications with other networks
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers
  • the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • 1A-1 D one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network
  • the emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • an AP may transmit a beacon on a fixed channel, such as a primary channel.
  • This channel may be 20 MHz wide, and may be the operating channel of the BSS.
  • This channel may also be used by the STAs to establish a connection with the AP.
  • a channel access mechanism in an 802.11 system is Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA).
  • CSMA/CA Carrier Sense Multiple Access with Collision Avoidance
  • every STA, including the AP may sense the primary channel. If the channel is detected to be busy, the may STA back off. Hence only one STA may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may also use a 40 MHz wide channel for communication. This may be achieved by combining a primary 20 MHz channel with an adjacent 20 MHz channel to form a 40 MHz wide contiguous channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and 160 MHz wide channels.
  • the 40 MHz and 80 MHz channels may be formed by combining contiguous 20 MHz channels similar to 802.11 n.
  • A160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may also be referred to as an 80+80 configuration.
  • the data after channel encoding, may be passed through a segment parser that may divide it into two streams.
  • An inverse Discrete Fourier Transformation (IDFT) operation and time-domain processing may be done on each stream separately.
  • the streams may then be mapped to the two channels, and the data may be transmitted. At the receiver, this procedure is reversed and the combined data may be sent to the MAC.
  • IDFT inverse Discrete Fourier Transformation
  • Sub 1 GHz modes of operation are supported by 802.11 af, and 802.11 ah.
  • the channel operating bandwidths and carriers are reduced relative to those used in 802.11n and 802.11 ac.
  • 802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • a possible use case for 802.11 ah is support for Meter Type Control (MTC) devices in a macro coverage area.
  • MTC devices may have limited capabilities including only support for limited bandwidths, but also include a requirement for a very long battery life.
  • WLAN systems which support multiple channels and channel widths such as 802.11 n, 802.11 ac, 802.11af, and 802 11 ah, include a channel which is designated as the primary channel.
  • the primary channel may, but not necessarily, have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel is therefore limited by the STA, of all STAs in operating in a BSS, which supports the smallest bandwidth operating mode
  • the primary channel may be 1 MHz wide if there are STAs (e.g MTC type devices) that only support a 1 MHz mode even if the AP and other STAs in the BSS may support a 2 MHz, 4 MHz, 8 MHz, 16 MHz, or other channel bandwidth operating modes. All carrier sensing and NAV settings depend on the status of the primary channel (i.e. if the primary channel is busy, for example, due to a STA supporting only a 1 MHz operating mode is transmitting to the AP, then the entire available frequency bands are considered busy even though a majority of it stays idle and available).
  • the available frequency bands which may be used by 802.11 ah are from 902 MHz to 928 MHz. In Korea, it is from 917.5 MHz to 923.5 MHz, and in Japan, it is from 916.5 MHz to 927.5 MHz.
  • the total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • the IEEE 802.11 Ultra High Reliability (UHR) Study Group was formed in September 2022.
  • UHR is considered as the next major revision to the IEEE 802.11 standards following 802.11 be, which is currently in the Working Group Letter Ballot Stage.
  • UHR is formed to explore the possibility to improve reliability, support low latency traffic, and further increase peak throughput and improve efficiency of the IEEE 802 11 networks.
  • the IEEE Standard board approved the IEEE 802.11 be Task Group (TG) based on a Project Authorization Request (PAR) and Criteria for Standards Development (CSD) developed in the EHT SG.
  • TG Task Group
  • PAR Project Authorization Request
  • CSS Criteria for Standards Development
  • Coordinated Multi-AP (C-MAP) transmissions was discussed in 802 11 be and UHR SG, including: Coordinated Multi-AP OFDMA (co-OFDMA), Coordinated Multi-AP TDMA (co-TDMA), Coordinated Multi-AP Spatial Reuse (CSR), Coordinated beamforming/nulling (CBF), and Joint Transmission (JTX)
  • Co-OFDMA Coordinated Multi-AP OFDMA
  • Co-TDMA Coordinated Multi-AP TDMA
  • CSR Coordinated Multi-AP Spatial Reuse
  • CBF Coordinated beamforming/nulling
  • JTX Joint Transmission
  • a Sharing AP is an EHT AP which obtains a transmission opportunity (TXOP) and initiates the multi-AP coordination.
  • a Shared AP is an EHT AP which is coordinated for the multi-AP transmission by the sharing AP.
  • An AP candidate set is a set of APs that may initiate or participate in multi-AP coordination.
  • Multiple AP multilink devices may be configured to provide coordinated operations over an area (e.g. an office space, an apartment building, a sport stadium, a shopping street, etc.) to achieve enhanced throughput and user experience for STAs and STA MLDs.
  • an area e.g. an office space, an apartment building, a sport stadium, a shopping street, etc.
  • STAs and STA MLDs need to be informed of the presence of the coordinated Multiple AP MLD set as well as the coordinated operations that the set provides.
  • the multiple AP MLD sets needs to be informed of the capabilities of the STA or STA MLDs. There is a need on how to provide an efficient discovery procedure for STA and STA MLDs as well as for multiple AP MLD sets.
  • Multiple STAs and non-AP MLDs may choose to associate with one or more APs, or AP MLDs or with a multi MLD (MMLD) during MMLD operations depending on its applications.
  • MMLD multi MLD
  • TWT target wake time
  • SP Service Period
  • a multi-Mutl i-Lin k-Devices may be comprised of multiple APs or STAs.
  • Each of the APs or STAs that may be part of a physical device which may be a Multi-link Device (MLD)
  • MLD Multi-link Device
  • Each of the MLDs may be located in a same physical location or a different physical location.
  • a distributed AP MLD may be a MLD that is comprised of APs that are located at different locations.
  • a different location may be a different physical location. For example, the different physical location may be out of visible site The different physical location may be a particular or at least a particular distance (e g. feet or meters) away.
  • the different physical location may be in a different room.
  • the different physical location may be a different building.
  • the different physical location may be that the APs are out of range of each other, cannot connect to each other, or cannot see each other at a particular point in time.
  • the different physical location may be locations that have different coordinates
  • a mixed mode Multi-MLD may be an MLD that is comprised of one or more APs. Some of these APs may be a part of a MLD, while other of these APs may be such that it is not affiliated with a MLD other than the MMLD.
  • An MXMLD may also be considered as an MMLD or an operating mode of an MMLD.
  • An AP Multi-MLD is an MMLD of which the STAs affiliated with the MMLD may be APs.
  • a non-AP Multi-MLD is an MMLD of which the STAs affiliated with the MMLD may be non-AP STAs.
  • a mixed STA Multi- MLD is an MMLD of which some of the STAs affiliated with the MMLD may be APs while some of the STAs affiliated with the MMLD may be non-AP STAs.
  • a Distributed MLD (DMLD) may be an MLD in which some or all STAs or APs that are affiliated with the DMLD are located at different physical locations. The STAs or APs that are affiliated with the DMLD may operate on the same or different channels or bands.
  • a Distributed MLD (DMLD) element may be used for STA MMLD and/or AP multi-MLD discovery.
  • a Distributed MLD (DMLD) element may be implemented using an existing multi-link element format.
  • An example design of a DMLD element is shown in FIG. 2.
  • the DMLD element or a DMLD variant of the multilink element may comprise one or more of the following fields.
  • the term DMLD element or DLMD variant of a multi-link element may be used interchangeably.
  • the DMLD element or a DMLD variant may comprise an Element ID field and Element ID Extension field.
  • a combination of the Element ID field value and Element ID Extension field value may indicate that the current element is a Multi-link element.
  • the combination of the Element ID field value and Element ID Extension value may indicate that the current element is a DMLD element.
  • the DMLD element or a DMLD variant may comprise a Length field.
  • the length field may indicate the length of the DMLD element.
  • the DMLD element or a DMLD variant may comprise a Multi-link Control field.
  • the Multi-link control field may comprise a Type subfield and a Presence Bitmap subfield.
  • the Type subfield may indicate that the current element is a Distributed MLD (DMLD) variant of the multi-link element.
  • the Presence Bitmap subfield may indicate which optional fields are present in the DMLD variant of the multi-link element.
  • the Type of DMLD variant of the multi-link element may indicate that all STAs or APs reported may be located at different physical locations. It may also indicate that the reported STAs or APs may operate on a same channel or band.
  • the DMLD element or a DMLD variant may comprise a Common Info field.
  • the Common Info field in the DMLD element may comprise one or more of the following subfields.
  • the Common Info field may comprise a DMLD MAC Address subfield.
  • the DMLD MAC Address subfield may be the MAC address of the MAC-SAP of the Distributed MLD logical entity or the Distributed MLD.
  • a distributed system may deliver all packets that are destined to one or more STAs or non-AP MLDs that are associated with one or one APs that are affiliated with the DMLD or that are associated with the DMLD to the indicated DMLD MAC Address.
  • the Common Info field may comprise a DMLD BSS Color subfield.
  • the DMLD BSS Color subfield may indicate the BSS Color used when DMLD wide transmission is conducted, such as joint transmission or redundant transmission for low latency or high reliability traffic.
  • the DMLD BSS Color subfield may be included in a physical layer convergence protocol (PLCP) header or MAC header, and may be in addition to BSS Color and/or MLD BSS color.
  • the Common Info field may comprise a DMLD Capabilities subfield.
  • the DMLD Capabilities subfield may indicate one or more capabilities of the DMLD.
  • the DMLD Capabilities subfield may indicate or comprise a maximum (Max) simultaneous links per channels subfield
  • the Max simultaneous links per channels subfield may indicate the maximum number of simultaneous links that the DMLD can support on the same channel for a STA or a non-AP MLD.
  • this field may indicate that a STA or a non-AP may concurrently be associated or registered or operate with 2 APs operating on the same channel that are affiliated with the DMLD.
  • Such simultaneous links may be needed if joint transmission may be supported in which one or more APs conduct simultaneous transmissions to the same STA or non-AP MLD (e.g. on the same channel).
  • Such simultaneous links may also be needed if low latency or high reliability traffic may be transmitted or repeated by multiple APs that are affiliated with the same DMLD (e g. operating on the same channel).
  • Such simultaneous links may be needed if seamless roaming is supported so that a non-AP MLD or a STA may establish more than one link with more than one AP while transitioning its association or registration from one AP to the other AP.
  • the DMLD Capabilities subfield may indicate or comprise a maximum (Max) simultaneous links subfield.
  • the Max simultaneous links subfield may indicate the maximum number of links that the DMLD may support across all channels.
  • a non- AP MLD may establish a number of links with the DMLD simultaneously, where some of the links may be on different channels, to enable traditional multi-link operations Some of the links may be on the same channel with different APs for seamless roaming or redundancy for low latency or high reliability traffic support.
  • the DMLD Capabilities subfield may indicate or comprise a seamless roaming capable subfield.
  • the seamless roaming capable subfield may indicate whether seamless roaming is supported, for example, when a STA or non-AP STA may establish more than one link simultaneously with different APs affiliated with the DMLD.
  • the DMLD Capabilities subfield may indicate or comprise a coordinated operations supported subfield.
  • the coordinated operations supported subfield may indicate the coordinated operations among the APs or STAs affiliated with the DMLD that the DMLD supports, such as Joint Transmission, Coordinated OFDMA, Coordinated Beamforming, Coordinated Spatial Reuse, and Transition among DMLD.
  • the DMLD element or a DMLD variant may comprise a Link Info field.
  • the Link Info field may comprise one or more (N) Per-STA Profile subfields Each of the Per-STA Profile subfields may provide or indicate information of a distributed AP or STA that is affiliated with the DMLD.
  • the information for AP or STA N may comprise one or more of the following information.
  • the information may comprise or indicate an identification (ID), which may be an identifier of the AP or STA, such as a MAC address or one or more of ID.
  • the information may comprise or indicate a Link ID, which may be the link identification (ID) for each reported STA and may be unique to the DMLD so that the STA, may be uniquely identified.
  • the information may comprise or indicate operating information, which may be operating information used to interact with the AP or STA.
  • the information may comprise or indicate collaborating AP identifiers, which may include one or more identifiers, such as BSSIDs or MAC address, of APs or STAs that may collaborate on coordinated operations, such as roaming or joint transmissions.
  • Such a set of collaborating APs may be identified by a collaborating set number and/or collaborating set BSS color, for example, when the collaborating set is operating on the same channel
  • an AP that is affiliated with a DMLD may include a DMLD element in a frame that it transmits, such as a beacon, a short beacon, a sub-beacon, other types of beacons or frames, probe responses, fast initial link setup (FILS) discovery frames, and association responses to indicate that it is part of a DMLD and to provide information of one or more APs that are affiliated with the same DMLD
  • a DMLD element in a frame that it transmits such as a beacon, a short beacon, a sub-beacon, other types of beacons or frames, probe responses, fast initial link setup (FILS) discovery frames, and association responses to indicate that it is part of a DMLD and to provide information of one or more APs that are affiliated with the same DMLD
  • An AP that is affiliated with a DMLD may indicate it is a part of a DMLD.
  • the AP may indicate its ability to support seamless roaming.
  • the AP may indicate its ability to support coordinated transmission such
  • a STA which may be affiliated with a non-AP MLD may send a message (e.g. multi-link probe request frame) to the AP, or any other AP, to request information on the AP and/or other directly neighboring APs that may be affiliated with the same DMLD.
  • the STA may send a multi-link probe request frame with an indication of requesting information on the coordinating set of APs of the AP, which may be operating on the same channel or on different channels, for example including a DMLD element.
  • the multi-link probe request frame may indicate the requested coordination for a particular operation, such as for seamless roaming or for joint transmission.
  • the AP may receive the multi-link probe request frame and may respond with a multi-link probe response frame, which may comprise a DMLD element, which may provide information on the APs that are affiliated with the DMLD, in addition to the information on the transmitting AP.
  • a multi-link probe response frame which may comprise a D LD element, which may provide information on all neighboring APs to the transmitting AP (e.g. directly neighboring APs) that are affiliated with the DMLD.
  • the AP may respond with a multi-link probe response frame, which may comprise a DMLD element, which may provide information on collaborating APs of the transmitting AP that are affiliated with the DMLD for a particular coordinated operation, such as seamless roaming, or redundancy transmission for low latency and high reliability traffic, in addition to the information on the transmitting AP.
  • the collaborating APs may be operating on the same channel or on different channels, which may be as requested in the multi-link probe request frame which may include a DMLD element, and may be identified by BSSIDs, Collaborating Set identifiers, Collaborating BSS Colors or other type of identifiers.
  • a STA which may be affiliated with a non-AP MLD, may receive a frame that may comprise a DMLD element or multi-link element and may send an association request that may comprise a DMLD element or a multi-link element.
  • a STA which may be affiliated with a non-AP MLD may include a multi-link element to request association with the DMLD with each STA affiliated with a non-AP MLD registering service on a link that is operating on a different channel.
  • a STA, which may be affiliated with a non-AP MLD may include a multi-link element or DMLD element to request association with the DMLD with only one STA registering service on multiple links that are operating on the same channel.
  • FIG. 3 shows an example method of DMLD discovery 300.
  • An AP that is affiliated with a DMLD, may receive, from a STA, a message (e.g. a multi-link probe request message) 310.
  • the STA may be affiliated with a non-AP MLD.
  • the multi-link probe request message may be a request for information on a coordinating set of APs.
  • the multi-link probe request message may be a request for information on coordination for a particular operation such as joint transmission or seamless roaming.
  • the multi-link probe request message may include a DMLD element, for example as shown in FIG. 2.
  • the AP may send a message to the STA (e.g. a multi-link probe response message) 320.
  • the multi-link probe response message may include a DMLD element, for example as shown in FIG. 2.
  • the DMLD element may comprise information regarding APs that are affiliated with the DMLD.
  • the DMLD may comprise information regarding neighboring APs to the AP.
  • the DMLD element may comprise information regarding collaborating APs of the APs that are affiliated with the DMLD for a particular coordinated operation such as seamless roaming or redundancy transmission for low latency and high reliability traffic.
  • the method of DMLD discovery 300 may include additional or alternate steps.
  • FIG. 4 shows an example method of DMLD discovery 400.
  • a STA that is affiliated with a non-AP MLD, may send, to an AP that is affiliated with a DMLD, a message (e.g.
  • the multi-link probe request message may be a request for information on a coordinating set of APs.
  • the multi-link probe request message may be a request for information on coordination for a particular operation such as joint transmission or seamless roaming.
  • the multi-link probe request message may include a DMLD element, for example as shown in FIG. 2.
  • the STA may receive a message from the AP (e.g. a multi-link probe response message) 420.
  • the multi-link probe response message may include a DMLD element, for example as shown in FIG. 2.
  • the DMLD element may comprise information regarding APs that are affiliated with the DMLD.
  • the DMLD may comprise information regarding neighboring APs to the AP.
  • the DMLD element may comprise information regarding collaborating APs of the APs that are affiliated with the DMLD for a particular coordinated operation such as seamless roaming or redundancy transmission for low latency and high reliability traffic.
  • the method of DMLD discovery 400 may include additional or alternate steps.
  • an AP may be affiliated with a MMLD without being affiliated with a MLD or an AP may be affiliated with an MLD that is a part of an MMLD.
  • Such an AP may include a MMLD element in frames that it transmits, such as a beacon, other type of beacons, a short beacon, probe responses, FILS discovery frames, and association responses, to indicate that it is part of an MMLD and to provide information of one or more MLDs or APs that are affiliated with the same MMLD.
  • An example design of a Multi-AP element or MMLD element is shown in FIG. 5.
  • the MMLD element or MMLD variant of the multi-link element may comprise one or more of the following fields.
  • the terms MMLD element or MMLD variant of multi-link element may be used interchangeably.
  • the MMLD element or MMLD variant of the multi-link element may comprise an Element ID and Element ID Extension field.
  • the combination of the Element ID field value and Element ID Extension field value may indicate that the current element is a Multi-link element.
  • the combination of the Element ID field value and Element ID Extension field value may indicate that the current element is a MMLD element
  • the MMLD element or MMLD variant of the multi-link element may comprise a Length field.
  • the length field may indicate the length of the MMLD element.
  • the MMLD element or MMLD variant of the multi-link element may comprise a Multi-link Control field.
  • the multi-link Control field may comprise a Type subfield and a Presence Bitmap subfield.
  • the Type subfield may indicate that the current element is the MMLD variant of the multi-link element.
  • the Presence Bitmap subfield may indicate which optional fields are present in the MMLD variant of the multi-link element.
  • the MMLD element or MMLD variant of the multi-link element may comprise a Common Info field.
  • the Common Info field in the MMLD element may comprise one or more of the following subfields.
  • the Common Info field may comprise a MMLD MAC Address subfield.
  • the MMLD MAC Address may be the MAC address of the MAC-SAP of the MMLD logical entity or the MMLD.
  • DS may deliver all packets that are destined to one or more STA or non-AP MLD that are associated with one or one APs that are affiliated with the MMLD or that are associated with the MMLD to the MMLD MAC address, or the MMLD MAC Address may be the identifier of the MMLD.
  • the Common Info field may comprise a MMLD BSS Color subfield.
  • the MMLD BSS Color subfield may indicate the BSS Color used when MMLD wide transmission is conducted, such as joint transmission, redundant transmission for low latency or high reliability traffic.
  • the MMLD BSS Color subfield may be included in the PLCP header or MAC header, and may be in addition to BSS Color of the AP, and/or in addition to the DMLD or MLD BSS Color.
  • the Common Info field may comprise a MMLD Capabilities subfield.
  • the MMLD Capabilities subfield may indicate one or more capabilities of the MMLD.
  • the MMLD Capabilities subfield may indicate or comprise a maximum (Max) simultaneous links per channel subfield.
  • the Max simultaneous links per channel subfield may indicate the maximum number of simultaneous links that the MMLD can support on the same channel for a STA or a non-AP MLD.
  • this field may indicate that a STA or a non-AP may concurrently be associated or registered or operate with 2 APs operating on the same channel that are affiliated with the MMLD.
  • Such simultaneous links may be needed if joint transmission may be supported in which one or more APs conduct simultaneous transmissions to the same STA or non-AP MLD.
  • Such simultaneous links may also be needed if low latency or high reliability traffic may be transmitted or repeated by multiple APs that are affiliated with the same MMLD.
  • Such simultaneous links may be needed if seamless roaming is supported so that a non-AP MLD or a STA may establish more than one link with more than one AP while transitioning its association or registration from one AP to the other AP.
  • the MMLD Capabilities subfield may indicate or comprise a maximum (Max) simultaneous links subfield.
  • the Max simultaneous links subfield may indicate the maximum number of links that the MMLD may support across all channels
  • a non-AP MLD may establish a number of links with the MMLD simultaneously, where some of the links may be on different channels, to enable traditional multi-link operations. Some of the links may be on the same channel with different APs for seamless roaming or redundancy for low latency or high reliability traffic support.
  • the MMLD Capabilities subfield may indicate or comprise a seamless roaming capable subfield.
  • the seamless roaming capable subfield may indicate whether seamless roaming is supported, for example, when a STA or non-AP STA may establish more than one link simultaneously with different APs affiliated with the MMLD.
  • the MMLD Capabilities subfield may indicate or comprise a coordinated operations supported subfield.
  • the coordinated operations supported subfield may indicate the coordinated operations among the APs or STAs affiliated with the MMLD that the MMLD supports, such as Joint Transmission, Coordinated OFDMA, Coordinated Beamforming, Coordinated Spatial Reuse, and Transition among MMLD.
  • the MMLD element or MMLD variant of the multi-link element may comprise a Number of Reported STAs field. This field may indicate the number of STA profiles reported in the STA Info field.
  • the MMLD element or MMLD variant of the multi-link element may comprise a STA Info field.
  • the STA Info field may comprise one or more Per-STA Profile subfields, with each of the Per-STA Profile subfields providing information of a distributed AP or STA that is affiliated with the MMLD
  • the STA Info field may comprise one or more (N) Per-STA Profile subfields.
  • the information for AP or STA N may comprise one or more of the following information.
  • the information may comprise or indicate an identification (ID), which may be an identifier of the AP or STA, such as MAC address or one or more of IDs.
  • ID identification
  • the information may comprise or indicate a Link ID, which may be the link ID for each reported STA and may be unique to the MMLD so that the STA may be uniquely identified.
  • the information may comprise or indicate operating information, which may be operating information needed to interact with the AP or STA.
  • the information may comprise or indicate collaborating AP identifiers, which may include one or more identifiers of APs or STAs that may collaborate on coordinated operations, such as roaming or joint transmissions. Such a set of collaborating APs may be identified by a collaborating set number and/or collaborating set BSS color, for example when the collaborating set is operating on the same channel.
  • each Per STA profile may include an MLD Identifier, such as a MLD MAC Address or another MLD ID, or MLD BSS Color field to identify whether the STA is affiliated with an MLD.
  • the MMLD element or MMLD variant of the multi-link element may comprise a Number of Reported MLDs subfield which may indicate the number of MLD profiles reported in the MLD Info field.
  • the MMLD element or MMLD variant of the multi-link element may comprise a MLD Info subfield.
  • the MLD Info field may comprise one or more (N) per-MLD Profile subfields, with each of the per-MLD Profile subfields providing or indicating information of an MLD that is affiliated with the MMLD, such as regular MLD or DMLD.
  • the information for MLD N may comprise one or more of the following information.
  • the information may comprise or indicate an identification (ID), which may be an Identifier of the MLD or DMLD, such as MAC address or one or more of ID.
  • ID identification
  • Each MLD Profile may be provided using a multilink element or a DMLD element or comprise similar information as contained in a multi-link element or a DM LD element.
  • an association through MMLD may be performed.
  • An AP MMLD may be comprised of multiple APs or MLDs.
  • Each of the MLDs/APs that may be a physical device or part of a physical device, may be in a different physical location.
  • the different physical location may be out of visible site.
  • the different physical location may be a particular or at least a particular distance (e.g. feet or meters) away.
  • the different physical location may be in a different room.
  • the different physical location may be a different building.
  • the different physical location may be that the APs are out of range of each other, cannot connect to each other, or cannot see each other at a particular point in time.
  • the different physical location may be locations that have different coordinates.
  • the AP MMLD may be a virtual concept or with a physical device.
  • a STA MMLD may be comprised of multiple STAs or STA MLDs. Each of the STA MLDs/STAs, that may be a physical device or part of a physical device, may be in the same physical location.
  • the STA MMLD may be a virtual concept.
  • FIG. 6 shows an association and authentication architecture for MMLD
  • an AP MMLD may perform an association with a STA MMLD.
  • One or more APs/MLDs may form a relatively static MMLD group.
  • the STA MMLD may be able to communication with one or more MLDs/APs in the MMLD group.
  • the AP MMLD may be associated with the STA MMLD.
  • the AP MMLD may be comprised of MLD 1 , AP 2 and MLD 3.
  • the STA MMLD may be comprised of STA 1 and STA 2, where STA 1 may be communicating with MLD 1 and STA 2 may be communicating with AP 2 STA 1 and STA 2 may have the same MAC address or different MAC addresses.
  • the STA MMLD may be comprised of a single STA, which may be communicating with MLD 1 and AP 2 after MMLD association.
  • a MMLD link may be defined as a communicative link between two devices over a frequency channel where each device may be affiliated or associated with a MMLD. Different communicative links may use different frequency channels or through different non-collocated APs/AP MLDs but using the same or partially overlapping channels.
  • two MMLD links may be established after a MMLD association, where MMLD link 1 may be between STA 1 and MLD 1 and MMLD link 2 may be between STA 2 and AP 2.
  • STA 1 in the example of FIG. 6 is replaced by a STA MLD which may be comprised of two frequency links and each established a communicative link with MLD 1 , then three MMLD links may be established
  • MMLO For Multi-MLD/AP operation, referred to as MMLO, setup between two MLDs, the same pairwise master key (PMK) and the same pairwise temporal key (PTK) across MLDs/APs may be used with the same PN space for a pairwise transient key security association (PTKSA).
  • AP MMLD MAC address and STA MMLD MAC address may be used to derive PMK under secure key establishment protocol and PTK.
  • group keys used for groupcast transmissions for example group temporal key (GTK), integrity group temporal key (IGTK), and beacon integrity group temporal key (BIGTK), may be established in a per MMLD link level There may be different PN spaces used in different MMLD links. GTK/IGTK/BIGTK in different MMLD links may be delivered in one 4-way handshake.
  • robust security network association may be established in a MMLD level and/or MMLD link level.
  • the association, authentication and 4-way handshake procedures may be performed once between the AP MMLD and non-AP STA MMLD and carry information for the other MMLD links. If RSNA has not been established, each message of the 4-way handshake may be sent on the same MMLD link used by the latest exchange of successful (Re)Association Request/Response frames.
  • different GTK/IGTK/BIGTK/PTK/PMK in different MMLD links with different PN spaces may be used.
  • GTK/IGTK/BIGTK/PTK/PMK in different MMLD links may be carried in a MMLO GTK KDE format or updated MLO GTK KDE format and delivered in one 4-way handshake frame exchange sequence.
  • FIG. 7 shows an example MMLO GTK KDE format.
  • FIG. 8 shows an example MMLO IGTK KDE format.
  • FIG. 9 shows an example MMLO BIGTK KDE format.
  • a new field, MMLD Link ID field is carried in the formats.
  • the MMLD Link ID may be used to identify a MMLD link by the MMLD.
  • the MMLD Link ID may comprise an AP MLD/AP ID and a Link ID.
  • the AP MLD/AP ID may indicate an ID of an AP MLD or AP which is part of the MMLD.
  • the AP MLD/AP IDs may be assigned to non-collocated AP MLDs/APs in the MMLD
  • the MMLD Link ID may indicate a frequency link/channel.
  • the MMLD Link ID may be assigned by the MMLD directly to indicate a MMLD link.
  • Different MMLD links of a MMLD may have different MMLD link IDs.
  • a MLD STA may be associated with multiple AP MLDs.
  • FIG. 10 shows an example of a MMLD scenario with one non-AP MLD (i.e. non-AP MLD11) associated with two AP MLDs (i.e. AP MLD1 and AP MLD2) Each of the MLDs comprises three STAs (links).
  • AP11 , AP12 and AP13 are affiliated with AP MLD1 ;
  • AP21 , AP22 and AP23 are affiliated with AP MLD2.
  • Non-AP MLD11 and non-AP MLD12 are affiliated with AP MLD1 and non-AP MLD21 and Non-AP MLD11 are associated with AP MLD2.
  • the MLD STA which is associated with multiple AP MLDs may initiate multiple TWT agreements with its associated AP MLDs using a single frame.
  • FIG. 11 shows an example of multiple individual TWT agreements with multiple AP MLDs initiated by a single STA, using the example MMLD setup from FIG. 10.
  • the TWT agreement is established on a per link basis. It may be extended to the establishment of TWT agreement per MLD basis.
  • the TWT requesting STA, non-AP MLD11 may send an enhanced TWT request to AP MLD 1 and AP MLD2 in link 1 to set up trigger-enabled TWT agreements with AP11 and AP21.
  • AP11 and AP21 may accept the TWT agreements with non-AP STA 111 and confirm the acceptance in the TWT responses sent to non-AP STA111.
  • non-AP STA111 may send the TWT SP information obtained from AP11 and/or AP21 to AP21 and/or AP11 such that both AP11 and AP21 have knowledge on the respective trigger-enabled TWT SP time with AP11 and AP21.
  • AP11 may send an unsolicited TWT response to non-AP STA 121 to set up a trigger- enabled TWT agreement with non-AP STA121 .
  • AP21 may send an unsolicited TWT response to non-AP211 to set up a trigger-enabled TWT agreement with non-AP STA211 .
  • the TWT responding STA may send a Basic Trigger frame to which the TWT requesting STAs indicate that they are awake during the TWT SP.
  • Non-AP STA111 may indicate that it is awake by sending a message (e.g. PS-Poll frame) and non-AP STA121 may indicate that it is awake by sending a message (e.g. QoS Null frame) in response to the Basic Trigger frame.
  • Non-AP STA111 and Non- AP STA121 may receive their DL BUs in a subsequent exchange with the TWT responding STA, AP11, and go to doze state outside of this TWT SP During the trigger-enabled TWT SP within AP21 , the TWT responding STA (e.g AP21) may send a Basic Trigger frame to which the TWT requesting STAs may indicate that they are awake during the TWT SP.
  • Non-AP STA111 may indicate that it is awake by sending a PS-Poll frame and non-AP STA211 may indicate that it is awake by sending a QoS Null frame in response to the Basic Trigger frame.
  • Non-AP STA111 and non-AP STA211 may receive their DL BUs in a subsequent exchange with the TWT responding STA (e.g. AP21) and go to doze state outside of this TWT SP.
  • an enhanced TWT element may be addressed to multiple AP MLDs simultaneously.
  • FIG. 12 shows an example of an enhanced TWT element format.
  • An Enhanced Control field and an Enhanced TWT Parameter Information field are included in the enhanced TWT element.
  • a Multiple TWT Setups subfield is included.
  • the Multiple TWT Setups subfield may indicate if this TWT request is for a single AP or AP MLD or for multiple APs or AP MLDs (e.g. 2 AP MLDs). For example, if this subfield is set to a value (e.g.
  • the Enhanced TWT Parameter Information field may comprise an enhanced individual TWT Parameter Set field, as shown in FIG. 14. In this example, a BSS Color subfield is included in the enhanced individual TWT Parameter Set field.
  • the BSS Color subfield may indicate the AP M LD or the AP or the group of AP MLDs (or the group of APs) identifier that the corresponding individual TWT Parameter Set field is addressed to.
  • the number of enhanced Individual TWT Parameter Set fields contained in the Enhanced TWT Parameter Information field may be equal to the number of STAs or MLDs that the TWT element is addressed to. For example, if Multiple TWT Setups subfield indicates the requesting TWT is addressed to two STAs (or MLDs), then the Enhanced TWT Parameter Information field comprises two enhanced individual TWT Parameter Set fields.
  • MMLD there is a virtual entity MMLD which AP MLD1 and AP MLD2 may be associated with.
  • the non-AP STA e g. non-AP MLD11
  • AP MLD1 may send a TWT request to the MMLD.
  • the MMLD may send a TWT response which may indicate the acceptance of the TWT agreement and may be received by AP MLD1, AP MLD2, and non-AP MLD11.
  • FIG. 15 shows an example of an individual TWT agreements with MMLD operation, using the example MMLD setup from FIG. 10
  • non-AP STA111 which is associated with non-AP MLD11, may send a TWT request to the MMLD and may indicate its preferred TWT SP time with AP11, affiliated with AP MLD1 , and preferred TWT SP time with AP21, affiliated with AP MLD2.
  • the TWT responding STA, MMLD may accept the TWT agreement and may send a TWT response to AP11 , AP21 and non-AP STA 111.
  • AP11 may send an unsolicited TWT response to non-AP STA121 to set up a trigger-enabled TWT agreement with non-AP STA121.
  • AP21 may send an unsolicited TWT response to non-AP STA211 to set up a trigger-enabled TWT agreement with non-AP STA 211.
  • the TWT responding STA i.e AP11
  • Non-AP STA111 may indicate that it is awake by sending a message (e.g.
  • Non-AP STA111 and Non-AP STA121 may indicate that it is awake by sending a message (e.g. QoS Null frame) in response to the Basic Trigger frame.
  • Non-AP STA111 and Non- AP STA121 may receive their DL BUs in a subsequent exchange with the TWT responding STA, AP11, and go to doze state outside of this TWT SP.
  • the TWT responding STA e.g. AP21
  • Non-AP STA111 may indicate that it is awake by sending a PS-Poll frame and non-AP STA211 may indicate that it is awake by sending a QoS Null frame in response to the Basic Trigger frame
  • Non-AP STA 111 and non-AP STA 211 may receive their DL BUs in a subsequent exchange with the TWT responding STA (e.g AP21), and go to doze state outside of this TWT SP.
  • a Non-AP STA may initiate negotiation of a wake Target Beacon Transmission Time (TBTT) with multiple MLD APs.
  • a non-AP STA may transmit a TWT request to its associated AP MLDs.
  • the number of associated AP MLDs may be two or more.
  • the non-AP STA may indicate to the associated AP MLDs that are Target Beacon Transmission Time (TBTT) scheduling AP MLDs and identifies the wake TBTT of the first Beacon frame and the wake interval between subsequent Beacon times that the STA intends to receive.
  • TBTT Target Beacon Transmission Time
  • the TWT request may comprise the following information
  • the TWT request may comprise the target BSS Colors, which may identify the AP MLDs that the TWT request is addressed to.
  • the number of target AP MLDs may be two or more.
  • the TWT request may comprise the requested first wake TBTT for each AP MLD, which may be indicated by a BSS Color.
  • the number of requested first wake TBTT values may be equal to the number of target BSS Colors.
  • the TWT request may comprise the requested wake interval between consecutive TBTTs for each AP MLD, which is indicated by the BSS Color.
  • the number of values of requested wake interval between consecutive TBTTs may be equal to the number of target BSS Colors.
  • the TWT request may comprise the requested TBTT wake duration for each AP MLD, which may be indicated by a BSS Color
  • the number of requested TBTT wake duration values may be equal to the number of target BSS Colors
  • the non-AP STA may send a TWT request to the MMLD which manages AP MLDs this STA associated with and negotiate the wake TBTTs and wake intervals between subsequent Beacon times with one or more than one AP MLD that this STA is associated with.
  • This negotiation may be directly performed between the non-AP STA and MMLD. After the agreement is set, the MMLD may distribute the negotiation results to the AP MLDs that the STA intends to receive the beacons.
  • non-AP STA111 affiliated with non-AP MLD11 which is associated with AP MLD1 and AP MLD2 would like to negotiate with AP 11 and AP21 the respective wake TBTT s of the first Beacon frame and the wake intervals between subsequent Beacon times.
  • Non-AP STA111 may send a TWT request to the MMLD which manages AP MLD1 and AP MLD2 (i.e., AP MLD1 and AP MLD2 are associated with the MMLD and AP11 and AP21 are affiliated with AP MLD1 and AP MLD2 respectively).
  • the MMLD After negotiation is agreed between non-AP STA111 and the MMLD, the MMLD will send the agreement related to the respective wake TBTTs of the first Beacon frame and the wake intervals between subsequent Beacon times that non-AP STA111 will follow in the operations of AP11 and AP21 to AP11 and AP21 . Such negotiation may be exchanged on the MLD level (e.g., between non-AP MLD11 and the MMLD).
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé et un appareil sont divulgués dans lesquels un premier point d'accès (AP) peut être affilié à un dispositif à liaisons multiples distribué (DMLD). Le DMLD peut comprendre des AP affiliés au DMLD. Le premier AP peut être configuré pour recevoir un message de demande de sonde à liaisons multiples en provenance d'une station (STA). Le premier AP peut être configuré pour envoyer un message de réponse de sonde à liaisons multiples à la STA. Le message de réponse de sonde à liaisons multiples peut comprendre un élément DMLD. L'élément DMLD peut comprendre au moins des informations concernant des AP qui sont affiliés au DMLD. Les AP qui sont affiliés au DMLD peuvent être dans différents emplacements. Le message de demande de sonde à liaisons multiples peut être une demande d'informations concernant un ensemble de coordination d'AP du premier AP. Le message de demande de sonde à liaisons multiples peut être une demande d'informations concernant une coordination pour une opération particulière. L'élément DMLD peut comprendre des informations concernant des AP voisins.
PCT/US2024/011365 2023-01-13 2024-01-12 Procédés de conception de mld et procédures pour uhr dans un wlan WO2024151927A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363438921P 2023-01-13 2023-01-13
US63/438,921 2023-01-13

Publications (1)

Publication Number Publication Date
WO2024151927A1 true WO2024151927A1 (fr) 2024-07-18

Family

ID=89983735

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/011365 WO2024151927A1 (fr) 2023-01-13 2024-01-12 Procédés de conception de mld et procédures pour uhr dans un wlan

Country Status (1)

Country Link
WO (1) WO2024151927A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210274574A1 (en) * 2020-05-15 2021-09-02 Chittabrata Ghosh Reduced neighbor report (rnr) element for multi-link devices (mld) and multiple bssids for cohosted and collocated access points

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210274574A1 (en) * 2020-05-15 2021-09-02 Chittabrata Ghosh Reduced neighbor report (rnr) element for multi-link devices (mld) and multiple bssids for cohosted and collocated access points

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
DUNCAN HO (QUALCOMM): "Seamless Roaming for UHR", vol. 802.11 UHR, 15 November 2022 (2022-11-15), pages 1 - 8, XP068199086, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/22/11-22-1910-00-0uhr-seamless-roaming-for-uhr.pptx> [retrieved on 20221115] *
JAMES YEE (MEDIATEK): "Multi-AP Coordination for UHR", vol. 802.11 UHR, 14 September 2022 (2022-09-14), pages 1 - 17, XP068193976, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/22/11-22-1512-00-0uhr-multi-ap-coordination-for-uhr.pptx> [retrieved on 20220914] *
YOSHIHISA KONDO (ATR): "Discussion on Multi-Link with Multiple AP MLDs", vol. 802.11 EHT; 802.11be, 27 August 2020 (2020-08-27), pages 1 - 12, XP068172305, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/20/11-20-1060-00-00be-discussion-on-multi-link-with-multiple-ap-mlds.pptx> [retrieved on 20200827] *

Similar Documents

Publication Publication Date Title
KR102399737B1 (ko) 비-3gpp 액세스 네트워크에 네트워크 슬라이스 능력을 요청하는 단말
US10880835B2 (en) Methods for efficient medium access for wake up radios
EP3997899A1 (fr) Procédés permettant d&#39;activer des wlans à liaisons multiples
US12075239B2 (en) Procedures enabling V2X unicast communication over PC5 interface
US20230100162A1 (en) Power efficient broadcasting in wlan
EP4388787A1 (fr) Systèmes, appareil et procédés destinés à améliorer des services de diffusion dans des réseaux locaux sans fil
US20230080757A1 (en) Systems and methods related to enhanced broadcast services in a multi-acces point system
EP4154471A1 (fr) Procédé de commutation de mode de distribution de service de diffusion générale /diffusion groupée multimédia (mbms)
WO2024151927A1 (fr) Procédés de conception de mld et procédures pour uhr dans un wlan
WO2024191818A1 (fr) Procédés de conception de mld distribuée et procédures pour uhr dans un wlan
WO2024173663A1 (fr) Procédés pour une opération de temps de réveil cible activée par de multiples ap
WO2023059812A1 (fr) Procédés et appareils pour des opérations coordonnées dans un ensemble de dispositifs multi-liaisons à points d&#39;accès multiples dans un réseau local sans fil
WO2024178423A1 (fr) Procédés, architectures, appareils et systèmes pour une opération de temps de réveil cible négociée multi-ap
EP4434268A1 (fr) Mécanismes de signalisation de points d&#39;accès voisins ebcs et leur service disponible
WO2024026082A1 (fr) Procédé et appareil d&#39;activation de communication n3gpp entre une wtru distante et une wtru relais
WO2024102975A1 (fr) Procédés de diffusion et de découverte d&#39;aiml dans un réseau wlan
WO2024102430A1 (fr) Procédés pour permettre une publicité à ondes millimétriques à liaisons multiples
CN118451750A (zh) 用于报告ebcs邻居接入点及其可用服务的机制
WO2024178206A1 (fr) Procédés pour une opération de temps de réveil cible à chevauchement coordonné à ap multiples
WO2024168002A1 (fr) Optimisation de drx pour économie d&#39;énergie de relais u2n
WO2023192146A1 (fr) Sélection d&#39;une route dans un système de communication sans fil
WO2023059612A1 (fr) Contrôle d&#39;accès à un réseau de locaux d&#39;abonné
CN118104319A (zh) Wtru到网络中继的省电方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24706302

Country of ref document: EP

Kind code of ref document: A1