WO2019078911A1 - Architecture de réseau segmentée pour convergence multi-accès générique - Google Patents

Architecture de réseau segmentée pour convergence multi-accès générique Download PDF

Info

Publication number
WO2019078911A1
WO2019078911A1 PCT/US2018/013355 US2018013355W WO2019078911A1 WO 2019078911 A1 WO2019078911 A1 WO 2019078911A1 US 2018013355 W US2018013355 W US 2018013355W WO 2019078911 A1 WO2019078911 A1 WO 2019078911A1
Authority
WO
WIPO (PCT)
Prior art keywords
gma
control message
message
control
radio
Prior art date
Application number
PCT/US2018/013355
Other languages
English (en)
Inventor
Laurent Cariou
Bahareh Sadeghi
Jing Zhu
Original Assignee
Intel IP Corporation
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 Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2019078911A1 publication Critical patent/WO2019078911A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2643—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA]
    • H04B7/2656—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA] for structure of frame, burst
    • 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

  • Embodiments pertain to wireless networks and wireless communications. Some embodiments relate to wireless local area networks (WLANs) and Wi-Fi networks including networks operating in accordance with the IEEE 802.11 family of standards. Some embodiments relate to IEEE
  • Some embodiments relate to methods, computer readable media, and apparatus for allocating at least a portion of a transmission opportunity to multiple devices.
  • a Next gen Wi-Fi device is capable of operating at different unlicensed bands, e.g. 2.4GHz, 5GHz, and 60GHz, simultaneously. This may include end to end (e2e) throughput and QoS by delivering user traffic over multiple bands, aka “Link/Band Aggregation.”
  • a generic multi-access (GMA) protocol stack in which each radio has its own PHY and MAC, operates independently in a specific band. It may also be possible to include a non- Wi-Fi radio, e.g. Ethernet, Bluetooth, LTE, etc. From the perspective of an application, a single Internet Protocol (IP) address may be shared among these radios, and a tunneling (adaptation) mechanism, e.g. IP-in-IP may be used if required to deliver user traffic over individual radio.
  • IP-in-IP Internet Protocol
  • a trailer-based multi-radio convergence method has been proposed. This solution provides for including additional control information, e.g. a sequence number, as a trailer of an IP packet to avoid any impact to link layer protocols, e.g. 802.2 LLC/SNAP, Ethernet Type II framing, etc., or network layer protocols, e.g. IP.
  • FIG. 1 is a block diagram of a radio architecture 100 in accordance with some embodiments.
  • FIG. 2 illustrates FEM circuitry 200 in accordance with some aspects
  • FIG. 3 illustrates radio IC circuitry 300 in accordance with some
  • FIG. 4 illustrates a functional block diagram of baseband processing circuitry 400 in accordance with some embodiments.
  • FIG. 5 illustrates a WLAN 500 in accordance with some embodiments.
  • FIG. 6 illustrates a block diagram of an example machine 600 upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform
  • FIG. 7 illustrates a block diagram of an example wireless device 700 upon which any one or more of the techniques (e.g., methodologies or operations) discussed herein may perform
  • FIG. 8 shows a generic multi-access (GMA) protocol stack.
  • FIG. 9 shows a trailer-based GMA PDU format that may be utilized by the protocol stack of FIG. 8.
  • FIG. 10 shows a proposed Split Link Layer (L2) based GMA control protocol stack.
  • FIG. 11 shows an example embodiment of an encapsulation message 1100 that may encapsulate a GMA control message.
  • FIG. 12 shows an example information element that may be transmitted or received in some of the disclosed embodiments.
  • FIG. 13 shows an example of a media access control (MAC) action frame for delivering a GMA control message (e.g. 1100) that may be implemented in some of the disclosed embodiments.
  • MAC media access control
  • FIG. 14 shows some example multi-access management services
  • FIG. 15 shows an example of a beacon frame.
  • FIG. 16 is an example of a GMA discovery control flow that may be implemented in at least some of the disclosed embodiments.
  • FIG. 17 is a flowchart of an example method of decoding an action frame.
  • FIG. 18 is a flowchart of an example method for encoding a GMA
  • FIG. 19 is a flowchart of a method for receiving a MAMS control plane message.
  • Multi Access Management Services is a programmable framework that provides for flexible selection of network paths in a multi-access communication environment.
  • the network path selection and configuration procedures use a user plane to exchange data between the functional elements in the network and the end-user device without any impact to the control plane signaling schemes of each individual access network.
  • a network connection manager may be a functional entity in the network that oversees distribution of data packets over the multiple available access and core network paths.
  • a client connection manager may be a functional entity in a station that exchanges MAMS Signaling with the network connection manager and configures multiple network paths for transport of user data.
  • a MAMS user plane protocol includes two sublayers.
  • a multi-access (MX) convergence sublayer This sublayer performs multi-access specific tasks, such as access (path) selection, multi-link (path) aggregation, splitting/reordering, lossless switching, fragmentation, concatenation, keep-alive. and probing.
  • a second sublayer is a multi-access (MX) adaptation sublayer, which performs functions including tunneling, network layer security, and network address translation.
  • a CCM and NCM in MAMS exchange signaling messages (control plan messages) to configure the user plane functions, client multi access data proxy (C-MADP) and network multi access data proxy (N-MADP) and the client and network respectively.
  • the N-MADP may be a functional entity in the network that handles user data traffic forwarding across multiple network paths.
  • N-MADP is responsible for MAMS related user-plane functionalities in the network.
  • N-MADP may be responsible for MAMS related user-plane functionality in the network.
  • the C-MADP is a functional entity in the client that handles user data traffic forwarding across multiple network paths.
  • C- MADP may be responsible for MAMS related user-plane functionality in the client.
  • a discovery process is performed that allows the CCM to obtain NCM credentials.
  • the NCM may assign additional NCM addresses for sending additional control plane messages.
  • a CCM may exchange capabilities with the NCM.
  • the NCM provides credentials of an N-MADP end-point and negotiates parameters for the user plane.
  • CCM configures C-MADP to setup the user plane path with the N- MADP based on the credentials.
  • the disclosed embodiments propose a new light-weight method to transmit the MAMS control plane messages over layer 2 signaling in the next generation multi-radio local area network (LAN).
  • the layer 2 transport may run over Wi-Fi or other radio technologies, such as Bluetooth or zigbee.
  • These disclosed embodiments provide a multi-radio device to support both Wi-Fi and Bluetooth connected to the gateway via a multi-radio access point that supports both Bluetooth and Wi-Fi.
  • the GMA control messages may be transmitted over Bluetooth while Wi-Fi may be used for data transfer.
  • a Bluetooth connection to the multi-radio access point is over a multi-hop path, as the AP may be too far from the multi-radio device for direct connection over Bluetooth in some aspects.
  • the connection may be via Bluetooth master mode.
  • the multi-radio device supports only Bluetooth and Zigbee and does not support Wi- Fi.
  • the disclosed embodiments split the e2e control connection between a device and network (controller) into two parts, called access and backhaul for convenience.
  • the access link may be between the device (e.g. STA) and its associated access point (AP).
  • the access link may be via a multi-radio AP supporting the other radio, for example Bluetooth.
  • the backhaul link may be between the associated AP and a central controller (such as a gateway). Both the backhaul link and the access link may be comprised of one or more hops.
  • the disclosed embodiments may use a new radio specific "multi-band management" comment to deliver the GMA control messages between the STA, AP, and a new 1905.1 CMDU (CMDU) Type- Length-Value (TLV) message container to deliver the GMA control message between the AP and the controller.
  • CMDU CMDU
  • TLV Type- Length-Value
  • a Wi-Fi "multi-band management" action frame is provided to deliver the GMA control message between an STA and its associated AP.
  • a logical link control and adaptation protocol (L2CAP) commands are used to deliver the message between multi-radio AP and the Bluetooth device. This may include multiple Bluetooth hops in some aspects.
  • FIG. 1 is a block diagram of a radio architecture 100 in accordance with some embodiments.
  • Radio architecture 100 may include radio front-end module (FEM) circuitry 104, radio IC circuitry 106 and baseband processing circuitry 108.
  • Radio architecture 100 as shown includes both Wireless Local Area Network (WLAN) functionality and Bluetooth (BT) functionality although embodiments are not so limited.
  • WLAN Wireless Local Area Network
  • BT Bluetooth
  • FEM circuitry 104 may include a WLAN or Wi-Fi FEM circuitry
  • the WLAN FEM circuitry 104A may include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas 101 , to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry 106A for further processing.
  • the BT FEM circuitry 104B may include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas 101, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry 106B for further processing.
  • FEM circuitry 104 A may also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry 106 A for wireless transmission by one or more of the antennas 101.
  • FEM circuitry 104B may also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry 106B for wireless transmission by the one or more antennas.
  • FIG. 1 In the embodiment of FIG.
  • FEM 104 A and FEM 104B are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of an FEM (not shown) that includes a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuitries where at least some of the FEM circuitries share transmit and/or receive signal paths for both WLAN and BT signals.
  • Radio IC circuitry 106 as shown may include WLAN radio IC circuitry 106 A and BT radio IC circuitry 106B.
  • the WLAN radio IC circuitry 106A may include a receive signal path which may include circuitry to down- convert WLAN RF signals received from the FEM circuitry 104A and provide baseband signals to WLAN baseband processing circuitry 108 A.
  • BT radio IC circuitry 106B may in turn include a receive signal path which may include circuitry to down-convert BT RF signals received from the FEM circuitry 104B and provide baseband signals to BT baseband processing circuitry 108B.
  • WLAN radio IC circuitry 106 A may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 108 A and provide WLAN RF output signals to the FEM circuitry 104 A for subsequent wireless transmission by the one or more antennas 101.
  • BT radio IC circuitry 106B may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 108B and provide BT RF output signals to the FEM circuitry 104B for subsequent wireless transmission by the one or more antennas 101.
  • radio IC circuitries 106A and 106B are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLA and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals.
  • Baseband processing circuitry 108 may include a WLAN baseband processing circuitry 108 A and a BT baseband processing circuitry 108B.
  • the WLAN baseband processing circuitry 108A may include a memory, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuitry 108 A
  • Each of the WLAN baseband circuitry 108 A and the BT baseband circuitry 108B may further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuitry 106, and to also generate corresponding WL AN or BT baseband signals for the transmit signal path of the radio IC circuitry 106.
  • Each of the baseband processing circuitries 108 A and 108B may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with application processor 111 for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 106.
  • the wireless radio card 102 may include separate baseband memory for one or more of the WLAN baseband processing circuitry 108 A and Bluetooth baseband processing circuitry 108B, shown as baseband memories 109 A and 109B respectively.
  • WLAN-BT coexistence circuitry 113 may include logic providing an interface between the WL AN baseband circuitry 108 A and the BT baseband circuitry 108B to enable use cases requiring WLAN and BT coexistence.
  • a switch 103 may be provided between the WLAN FEM circuitry 104 A and the BT FEM circuitry 104B to allow switching between the WLAN and BT radios according to application needs.
  • the antennas 101 are depicted as being respectively connected to the WLAN FEM circuitry 104 A and the BT FEM circuitry 104B, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM 104 A or 104B.
  • the front-end module circuitry 104, the radio IC circuitry 106, and baseband processing circuitry 108 may be provided on a single radio card, such as wireless radio card 102.
  • the one or more antennas 101, the FEM circuitry 104 and the radio IC circuitry 106 may be provided on a single radio card.
  • the radio IC circuitry 106 and the baseband processing circuitry 108 may be provided on a single chip or integrated circuit (IC), such as IC 112.
  • the wireless radio card 102 may include a
  • the radio architecture 100 may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multicarrier communication channel.
  • OFDM orthogonal frequency division multiplexed
  • OFDMA orthogonal frequency division multiple access
  • radio architecture 100 may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device.
  • STA Wi-Fi communication station
  • AP wireless access point
  • radio architecture 100 may be configured to transmit and receive signals in accordance with specific communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards including, IEEE 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, IEEE 802.11ac, and/or IEEE 802.11ax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect.
  • Radio architecture 100 may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.
  • the radio architecture 100 may be configured for high-efficiency (HE) Wi-Fi (HEW) communications in accordance with the IEEE 802.11ax standard.
  • the radio architecture 100 may be configured to communicate in accordance with an OFDMA technique, although the scope of the embodiments is not limited in this respect.
  • the radio architecture 100 may be configured to transmit and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.
  • spread spectrum modulation e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)
  • TDM time-division multiplexing
  • FDM frequency-division multiplexing
  • the BT baseband circuitry 108B may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 4.0 or Bluetooth 5.0, or any other iteration of the Bluetooth Standard.
  • BT Bluetooth
  • the radio architecture 100 may be configured to establish a BT synchronous connection oriented (SCO) link and'or a BT low energy (BT LE) link.
  • SCO BT synchronous connection oriented
  • BT LE BT low energy
  • the radio architecture 100 may be configured to establish an extended SCO (eSCO) link for BT communications, although the scope of the embodiments is not limited in this respect.
  • the radio architecture may be configured to engage in a BT
  • Asynchronous Connection-Less (ACL) communications although the scope of the embodiments is not limited in this respect.
  • the functions of a BT radio card and WLAN radio card may be combined on a single wireless radio card, such as single wireless radio card 102, although embodiments are not so limited, and include within their scope discrete WLAN and BT radio cards
  • the radio-architecture 100 may include other radio cards, such as a cellular radio card configured for cellular (e.g., 3GPP such as LTE, LTE-Advanced or 5G communications).
  • a cellular radio card configured for cellular (e.g., 3GPP such as LTE, LTE-Advanced or 5G communications).
  • the radio architecture 100 may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GFIz, 5 GHz, and bandwidths of about 1 MHz, 2 MHz, 2.5 MHz, 4 MHz, 5MHz, 8 MHz, 10 MHz, 16 MHz, 20 MHz, 40MHz, 80MHz (with contiguous bandwidths) or 80+80MHz (160MHz) (with non-contiguous bandwidths).
  • bandwidths having center frequencies of about 900 MHz, 2.4 GFIz, 5 GHz, and bandwidths of about 1 MHz, 2 MHz, 2.5 MHz, 4 MHz, 5MHz, 8 MHz, 10 MHz, 16 MHz, 20 MHz, 40MHz, 80MHz (with contiguous bandwidths) or 80+80MHz (160MHz) (with non-contiguous bandwidths).
  • a 320 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.
  • FIG. 2 illustrates FEM circuitry 200 in accordance with some embodiments.
  • the FEM circuitry 200 is one example of circuitry that may be suitable for use as the WLAN and/or BT FEM circuitry 104A/104B (FIG. 1), although other circuitry configurations may also be suitable.
  • the FEM circuitry 200 may include a X/RX switch 202 to switch between transmit mode and receive mode operation.
  • the FEM circuitry 200 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 200 may include a low-noise amplifier (LNA) 206 to amplify received RF signals 203 and provide the amplified received RF signals 207 as an output (e.g., to the radio IC circuitry 106 (FIG. 1)).
  • LNA low-noise amplifier
  • the transmit signal path of the circuitry 200 may include a power amplifier (PA) to amplify input RF signals 209 (e.g., provided by the radio IC circuitry 106), and one or more filters 212, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 215 for subsequent transmission (e.g., by one or more of the antennas 101 (FIG. 1)) ⁇
  • PA power amplifier
  • filters 212 such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters
  • the FEM circuitry 200 may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum
  • the receive signal path of the FEM circuitry 200 may include a receive signal path duplexer 204 to separate the signals from each spectrum as well as provide a separate LN A 206 for each spectrum as shown.
  • the transmit signal path of the FEM circuitry 200 may also include a power amplifier 210 and a filter 212, such as a BPF, a LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 214 to provide the signals of one of the different spectrums onto a single transmit path for subsequent transmission by the one or more of the antennas 101 (FIG. 1).
  • BT communications may utilize the 2.4 GHZ signal paths and may utilize the same FEM circuitry 200 as the one used for WLAN communications.
  • FIG. 3 illustrates radio IC circuitry 300 in accordance with some embodiments.
  • the radio IC circuitry 300 is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 106A/106B (FIG. 1), although other circuitry configurations may also be suitable.
  • the radio IC circuitry 300 may include a receive signal path and a transmit signal path.
  • the receive signal path of the radio IC circuitry 300 may include at least mixer circuitry 302, such as, for example, down-conversion mixer circuitry, amplifier circuitry 306 and filter circuitry 308.
  • the transmit signal path of the radio IC circuitry 300 may include at least filter circuitry 312 and mixer circuitry 314, such as, for example, up- conversion mixer circuitry.
  • Radio IC circuitry 300 may also include synthesizer circuitry 304 for synthesizing a frequency 305 for use by the mixer circuitry 302 and the mixer circuitry 314.
  • the mixer circuitry 302 and/or 314 may each, according to some embodiments, be configured to provide direct conversion functionality.
  • Fig. 3 illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component.
  • mixer circuitry 320 and/or 314 may each include one or more mixers
  • filter circuitries 308 and/or 312 may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs.
  • mixer circuitries when mixer circuitries are of the direct-conversion type, they may each include two or more mixers.
  • mixer circuitry 302 may be configured to down-convert RF signals 207 received from the FEM circuitry 104 (FIG. 1) based on the synthesized frequency 305 provided by synthesizer circuitry 304.
  • the amplifier circuitry 306 may be configured to amplify the down-converted signals and the filter circuitry 308 may include a LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 307.
  • Output baseband signals 307 may be provided to the baseband processing circuitry 108 (FIG. 1 ) for further processing.
  • the output baseband signals 307 may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 302 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 314 may be configured to up-convert input baseband signals 311 based on the synthesized frequency 305 provided by the synthesizer circuitry 304 to generate RF output signals 209 for the FEM circuitry 104.
  • the baseband signals 311 may be provided by the baseband processing circuitry 108 and may be filtered by filter circuitry 312.
  • the filter circuitry 312 may include a LPF or a BPF, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 302 and the mixer circuitry 314 may each include two or more mixers and may be arranged for quadrature down-conversion and or up-conversion respectively with the help of synthesizer 304.
  • the mixer circuitry 302 and the mixer circuitry 314 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 302 and the mixer circuitry 314 may be arranged for direct down- conversion and/or direct up-conversion, respectively.
  • the mixer circuitry 302 and the mixer circuitry 314 may be configured for superheterodyne operation, although this is not a requirement.
  • Mixer circuitry 302 may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths).
  • RF input signal 207 from Fig. 3 may be down- converted to provide I and Q baseband output signals to be sent to the baseband processor
  • Quadrature passive mixers may be driven by zero and ninety- degree time-varying LO switching signals provided by a quadrature circuitry which may be configured to receive a LO frequency (fLO) from a local oscillator or a synthesizer, such as LO frequency 305 of synthesizer 304 (FIG. 3).
  • a LO frequency fLO
  • the LO frequency may be the carrier frequency
  • the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency).
  • the zero and ninety-degree time- varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect.
  • the LO signals may differ in duty cycle
  • each branch of the mixer circuitry e.g., the in-phase (I) and quadrature phase (Q) path
  • the RF input signal 207 may comprise a balanced signal, although the scope of the embodiments is not limited in this respect.
  • the I and Q baseband output signals may be provided to low-nose amplifier, such as amplifier circuitry 306 (FIG. 3) or to filter circuitry 308 (FIG. 3).
  • the output baseband signals 307 and the input baseband signals 311 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate
  • the output baseband signals 307 and the input baseband signals 311 may be digital baseband signals.
  • the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, or for other spectrums not mentioned here, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 304 may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 304 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 304 may include digital synthesizer circuitry.
  • frequency input into synthesizer circuitry 304 may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • a divider control input may further be provided by either the baseband processing circuitry 108 (FIG. 1) or the application processor 111 (FIG. 1) depending on the desired output frequency 305.
  • a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the application processor 111.
  • synthesizer circuitry 304 may be configured to generate a carrier frequency as the output frequency 305, while in other embodiments, the output frequency 305 may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the output frequency 305 may be a LO frequency (fLO).
  • fLO LO frequency
  • FIG. 4 illustrates a functional block diagram of baseband processing circuitry 400 in accordance with some embodiments.
  • the baseband processing circuitry 400 is one example of circuitry that may be suitable for use as the baseband processing circuitry 108 (FIG. 1), although other circuitry configurations may also be suitable.
  • the baseband processing circuitry 400 may- include a receive baseband processor (RX BBP) 402 for processing receive baseband signals 309 provided by the radio IC circuitry 106 (FIG. 1) and a transmit baseband processor (TX BBP) 404 for generating transmit baseband signals 311 for the radio IC circuitry 106.
  • the baseband processing circuitry 400 may also include control logic 406 for coordinating the operations of the baseband processing circuitry 400.
  • the baseband processing circuitry 400 may include ADC 410 to convert analog baseband signals received from the radio IC circuitry 106 to digital baseband signals for processing by the RX BBP 402.
  • the baseband processing circuitry 400 may also include DAC 412 to convert digital baseband signals from the TX BBP 404 to analog baseband signals.
  • the transmit baseband processor 404 may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT).
  • IFFT inverse fast Fourier transform
  • the receive baseband processor 402 may be configured to process received OFDM signals or OFDMA signals by performing an FFT.
  • the receive baseband processor 402 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation, to detect a preamble, such as a short preamble, and by performing a cross-correlation, to detect a long preamble.
  • the preambles may be part of a predetermined frame structure for Wi-Fi communication.
  • the antennas 101 are identical to each other. [0064] Referring back to FIG. 1, in some embodiments, the antennas 101 are identical to each other.
  • FIG. 1 may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals.
  • the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • Antennas 101 may each include a set of phased-array antennas, although embodiments are not so limited.
  • the radio-architecture 100 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements may refer to one or more processes operating on one or more processing elements.
  • FIG. 5 illustrates a WLAN 500 in accordance with some embodiments.
  • the WLAN 500 may comprise a basis service set (BSS) that may include a HE access point (AP) 502, which may be an AP, a plurality of high- efficiency wireless (e.g., IEEE 802.11 ax) (HE) stations 504, and a plurality of legacy (e.g., IEEE 802.11n/ac) devices 506.
  • BSS basis service set
  • AP HE access point
  • HE high- efficiency wireless
  • legacy e.g., IEEE 802.11n/ac
  • the HE AP 502 may be an AP using the IEEE 802.11 to transmit and receive.
  • the HE AP 502 may be a base station.
  • the HE AP 502 may use other communications protocols as well as the IEEE 802.11 protocol.
  • the IEEE 802.11 protocol may be IEEE 802.11ax.
  • the IEEE 802.11 protocol may include using orthogonal frequency division multiple-access (OFDMA), time division multiple access (TDMA), and/or code division multiple access (CDMA).
  • the IEEE 802.11 protocol may include a multiple access technique.
  • the IEEE 802.11 protocol may include space-division multiple access (SDMA) and/or multiple-user multiple-input multiple-output (MU-MIMO).
  • SDMA space-division multiple access
  • MU-MIMO multiple-user multiple-input multiple-output
  • There may be more than one HE AP 502 that is part of an extended service set (ESS).
  • a controller (not illustrated) may store information that is common to the more than one
  • the legacy devices 506 may operate in accordance with one or more of IEEE 802.11 a/b/g/n/ac/ad/af/ah/aj/ay, or another legacy wireless communication standard.
  • the legacy devices 506 may be STAs or IEEE STAs.
  • the HE STAs 504 may be wireless transmit and receive devices such as cellular telephone, portable electronic wireless communication devices, smart telephone, handheld wireless device, wireless glasses, wireless watch, wireless personal device, tablet, or another device that may be transmitting and receiving using the IEEE 802.11 protocol such as IEEE 802. 11 ax or another wireless protocol.
  • the HE STAs 504 may be termed high efficiency (HE) stations.
  • HE high efficiency
  • the HE AP 502 may communicate with legacy devices 506 in accordance with legacy IEEE 802.11 communication techniques.
  • the HE AP 502 may also be configured to communicate with HE STAs 504 in accordance with legacy IEEE 802.11 communication techniques.
  • a HE frame may be configurable to have the same bandwidth as a channel.
  • the HE frame may be a physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU).
  • PLCP physical Layer Convergence Procedure
  • PPDU Protocol Data Unit
  • MAC media access control
  • the bandwidth of a channel may be 20MHz, 40MHz, or 80MHz,
  • the bandwidth of a channel may be 1 MHz, 1.25MHz, 2.03MHz, 2.5MHz, 4.06 MHz, 5MHz and 10MHz, or a combination thereof or another bandwidth that is less or equal to the available bandwidth may also be used.
  • the bandwidth of the channels may be based on a number of active data subcarriers. In some embodiments, the bandwidth of the channels is based on 26, 52, 106, 242, 484, 996, or 2x996 active data subcarriers or tones that are spaced by 20 MHz In some embodiments, the bandwidth of the channels is 256 tones spaced by 20 MHz.
  • the channels are multiple of 26 tones or a multiple of 20 MHz.
  • a 20 MHz channel may comprise 242 active data subcarriers or tones, which may determine the size of a Fast Fourier Transform (FFT).
  • FFT Fast Fourier Transform
  • An allocation of a bandwidth or a number of tones or sub- carriers may be termed a resource unit (RU) allocation in accordance with some embodiments.
  • the RU are used in the 20 MHz, 40 MHz, 80 MHz, 160 MHz and 80+80 MHz OFDMA HE PPDU formats.
  • the 106-subcarrier RU is used in the 20 MHz, 40 MHz, 80 MHz, 160 MHz and 80+80 MHz OFDMA and MU-MIMO HE PPDU formats.
  • the 242-subcarrier RU is used in the 40 MHz, 80 MHz, 160 MHz and 80+80 MHz OFDMA and MU- MIMO HE PPDU formats.
  • the 484-subcarrier RU is used in the 80 MHz, 160 MHz and 80+80 MHz OFDMA and MU-MIMO HE PPDU formats.
  • the 996-subcarrier RU is used in the 160 MHz and 80+80 MHz OFDMA and MU-MIMO HE PPDU formats.
  • a HE frame may be configured for transmitting a number of spatial streams, which may be in accordance with MU-MIMO and may be in accordance with OFDMA.
  • the HE AP 502, HE STA 504, and/or legacy device 506 may also implement different technologies such as code division multiple access (CDMA) 2000, CDMA 2000 IX, CDMA 2000 Evolution-Data Optimized (EV-DO), Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Long Term Evolution (LTE), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), BlueTooth®, or other technologies.
  • CDMA code division multiple access
  • CDMA 2000 IX CDMA 2000 Evolution-Data Optimized
  • EV-DO Evolution-Data Optimized
  • IS-2000 IS-2000
  • IS-95 IS-95
  • IS-856 Interim Standard 856
  • LTE Long Term Evolution
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • a HE AP 502 may operate as a master station which may be arranged to contend for a wireless medium (e.g., during a contention period) to receive exclusive control of the medium for an HE control period.
  • the HE control period may be termed a transmission opportunity (TXOP).
  • TXOP transmission opportunity
  • the HE AP 502 may transmit a HE master-sync transmission, which may be a trigger frame or HE control and schedule transmission, at the beginning of the HE control period.
  • the HE AP 502 may transmit a time duration of the TXOP and sub-channel information.
  • HE ST As 504 may communicate with the HE AP 502 in accordance with a non-contention based multiple access technique such as OFDMA or MU-MIMO. This is unlike conventional WLAN communications in which devices communicate in accordance with a contention-based communication technique, rather than a multiple access technique.
  • the HE AP 502 may communicate with HE stations 504 using one or more HE frames.
  • the HE STAs 504 may operate on a sub-channel smaller than the operating range of the HE AP 502.
  • legacy stations refrain from communicating. The legacy stations may need to receive the communication from the HE AP 502 to defer from communicating.
  • the trigger frame may indicate an uplink (UL) UL-MU-MIMO and/or UL OFDMA TXOP.
  • the trigger frame may include a DL UL-MU-MIMO and/or DL OFDMA with a schedule indicated in a preamble portion of trigger frame.
  • the multiple-access technique used during the HE TXOP may be a scheduled OFDMA technique, although this is not a requirement.
  • the multiple access technique may be a time-division multiple access (TDMA) technique or a frequency division multiple access (FDMA) technique.
  • the multiple access technique may be a space-division multiple access (SDMA) technique.
  • the multiple access technique may be a Code division multiple access (CDMA).
  • the HE AP 502 may also communicate with legacy' stations 506 and/or HE stations 504 in accordance with legacy IEEE 802.11 communication techniques.
  • the HE AP 502 may also be configurable to communicate with HE stations 504 outside the HE TXOP in accordance with legacy IEEE 802.11 communication techniques, although this is not a requirement.
  • the HE station 504 may be a "group owner" (GO) for peer-to-peer modes of operation.
  • a wireless device may be a HE station 502 or a HE AP 502.
  • the HE station 504 and/or HE AP 502 may be configured to operate in accordance with IEEE 802.1 lmc.
  • the radio architecture of FIG. 1 is configured to implement the HE station 504 and/or the HE AP 502.
  • the front-end module circuitry of FIG. 2 is configured to implement the HE station 504 and/or the HE AP 502.
  • the radio IC circuitry of FIG. 3 is configured to implement the HE station 504 and/or the HE AP 502.
  • the base-band processing circuitry of FIG. 4 is configured to implement the HE station 504 and/or the HE AP 502.
  • the HE stations 504, HE AP 502, an apparatus of the HE stations 504, and/or an apparatus of the HE AP 502 may include one or more of the following: the radio architecture of FIG. 1, the front- end module circuitry of FIG. 2, the radio IC circuitry of FIG. 3, and/or the baseband processing circuitry of FIG. 4.
  • the radio architecture of FIG. 1, the front-end module circuitry of FIG. 2, the radio IC circuitry of FIG. 3, and/or the base-band processing circuitry of FIG. 4 may be configured to perform the methods and operations/functions herein described in conjunction with FIGS. 1- 19.
  • the HE station 504 and/or the HE AP 502 are configured to perform the methods and operations/functions described herein in conjunction with FIGS. 1-19.
  • an apparatus of the HE station 504 and/or an apparatus of the HE AP 502 are configured to perform the methods and functions described herein in conjunction with FIGS. 1-19.
  • the term Wi-Fi may refer to one or more of the IEEE 802.11
  • AP and STA may refer to HE access point 502 and or HE station 504 as well as legacy devices 506.
  • a HE AP STA may refer to a HE AP 502 and a HE STAs 504 that is operating a HE APs 502.
  • when an HE STA 504 is not operating as a HE AP it may be referred to as a HE non-AP STA or HE non-AP.
  • HE STA 504 may be referred to as either a HE AP STA or a HE non-AP.
  • FIG. 6 illustrates a block diagram of an example machine 600 upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform
  • the machine 600 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine 600 may operate in the capacity of a server machine, a client machine, or both in server-client network environments.
  • the machine 600 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the machine 600 may be a HE AP 502, HE station 504, personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a portable communications device, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • PC personal computer
  • PDA personal digital assistant
  • portable communications device a mobile telephone
  • smart phone a web appliance
  • network router, switch or bridge or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • machine shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
  • Machine 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604 and a static memory 606, some or all of which may communicate with each other via an interlink (e.g., bus) 608.
  • a hardware processor 602 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • main memory 604 e.g., main memory
  • static memory 606 e.g., static memory
  • main memory 604 includes Random Access
  • RAM Random Access Memory
  • semiconductor memory devices which may include, in some embodiments, storage locations in semiconductors such as registers.
  • static memory 606 include non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Erasable Programmable Read
  • the machine 600 may further include a display device 610, an input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse).
  • the display device 610, input device 612 and UI navigation device 614 may be a touch screen display.
  • the machine 600 may additionally include a mass storage (e.g., drive unit) 616, a signal generation device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 621, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • GPS global positioning system
  • the machine 600 may include an output controller 628, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • the processor 602 and/or instructions 624 may comprise processing circuitry and/or transceiver circuitry.
  • the storage device 616 may include a machine readable medium
  • the instructions 624 may also reside, completely or at least partially, within the main memory 604, within static memory 606, or within the hardware processor 602 during execution thereof by the machine 600.
  • the hardware processor 602, the main memory 604, the static memory 606, or the storage device 616 may constitute machine readable media
  • machine readable media may include: nonvolatile memory, such as semiconductor memory devices (e.g., EPROM or EEPROM) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.
  • nonvolatile memory such as semiconductor memory devices (e.g., EPROM or EEPROM) and flash memory devices
  • magnetic disks such as internal hard disks and removable disks
  • magneto-optical disks such as CD-ROM and DVD-ROM disks.
  • machine readable medium 622 is illustrated as a single medium, the term “machine readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 624.
  • machine readable medium may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 624.
  • An apparatus of the machine 600 may be one or more of a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604 and a static memory 606, sensors 621, network interface device 620, antennas 660, a display device 610, an input device 612, a UI navigation device 614, a mass storage 616, instructions 624, a signal generation device 618, and an output controller 628.
  • the apparatus may be configured to perform one or more of the methods and/or operations disclosed herein.
  • the apparatus may be intended as a component of the machine 600 to perform one or more of the methods and/or operations disclosed herein, and/or to perform a portion of one or more of the methods and/or operations disclosed herein.
  • the apparatus may include a pin or other means to receive power.
  • the apparatus may include power conditioning hardware.
  • the term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 600 and that cause the machine 600 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non- limiting machine readable medium examples may include solid-state memories, and optical and magnetic media
  • Specific examples of machine readable media may include: non- olatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks;
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • machine readable media may include non-transitory machine readable media.
  • machine readable media may include machine readable media that is not a transitory propagating signal.
  • the instructions 624 may further be transmitted or received over a communications network 626 using a transmission medium via the network interface device 620 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others.
  • LAN local area network
  • WAN wide area network
  • POTS Plain Old Telephone
  • wireless data networks e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®
  • IEEE 802.15.4 family of standards e.g., Institute of Electrical and Electronics Engineers (IEEE
  • the network interface device 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 626.
  • the network interface device 620 may include one or more antennas 660 to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques.
  • SIMO single-input multiple-output
  • MIMO multiple-input multiple-output
  • MISO multiple-input single-output
  • the network interface device 620 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 600, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a machine readable medium
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Some embodiments may be implemented fully or partially in software and/or firmware.
  • This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein.
  • the instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • Such a computer-readable medium may include any tangible non- transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, etc.
  • FIG. 7 illustrates a block diagram of an example wireless device
  • the wireless device 700 may be a HE device.
  • the wireless device 700 may be a HE STA 504 and/or HE AP 502 (e.g., FIG. 5).
  • a HE STA 504 and/or HE AP 502 may include some or all of the components shown in FIGS. 1-6.
  • the wireless device 700 may be an example machine 600 as disclosed in conjunction with FIG. 6.
  • the wireless device 700 may include processing circuitry 708.
  • the processing circuitry 708 may include a transceiver 702, physical layer circuitry (PHY circuitry) 704, and MAC layer circuitry (MAC circuitry) 706, one or more of which may enable transmission and reception of signals to and from other wireless devices 700 (e.g., HE AP 502, HE STA 504, and/or legacy devices 506) using one or more antennas 712.
  • the PHY circuitry 704 may perform various encoding and decoding functions that may include formation of baseband signals for transmission and decoding of received signals.
  • the transceiver 702 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range.
  • RF Radio Frequency
  • the PHY circuitry 704 and the transceiver 702 may be separate components or may be part of a combined component, e.g., processing circuitry 708.
  • some of the described functionality related to transmission and reception of signals may be performed by a combination that may include one, any or all of the PHY circuitry 704 the transceiver 702, MAC circuitry 706, memory 710, and other components or layers.
  • the MAC circuitry 706 may control access to the wireless medium.
  • the wireless device 700 may also include memory 710 arranged to perform the operations described herein, e.g., some of the operations described herein may be performed by instructions stored in the memory 710.
  • the antennas 712 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals.
  • the antennas 712 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • One or more of the memory 710, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706, the antennas 712, and/or the processing circuitry 708 may be coupled with one another.
  • memory 710, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706, the antennas 712 are illustrated as separate components, one or more of memory 710, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706, the antennas 712 may be integrated in an electronic package or chip.
  • the wireless device 700 may be a mobile device as described in conjunction with FIG. 6.
  • the wireless device 700 may be configured to operate in accordance with one or more wireless communication standards as described herein (e.g., as described in conjunction with FIGS. 1-6, IEEE 802.11).
  • the wireless device 700 may include one or more of the components as described in conjunction with FIG. 6 (e.g., display device 610, input device 612, etc.)
  • the wireless device 700 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements may refer to one or more processes operating on one or more processing elements.
  • an apparatus of or used by the wireless device 700 may include various components of the wireless device 700 as shown in FIG. 7 and/or components from FIGS. 1-6. Accordingly, techniques and operations described herein that refer to the wireless device 700 may be applicable to an apparatus for a wireless device 700 (e.g., HE AP 502 and/or HE STA 504), in some embodiments.
  • the wireless device 700 is configured to decode and or encode signals, packets, and/or frames as described herein, e.g., PPDUs.
  • the MAC circuitry 706 may be arranged to contend for a wireless medium during a contention period to receive control of the medium for a HE TXOP and encode or decode an HE PPDU. In some embodiments, the MAC circuitry 706 may be arranged to contend for the wireless medium based on channel contention settings, a transmitting power level, and a clear channel assessment level (e.g., an energy detect level).
  • a clear channel assessment level e.g., an energy detect level
  • the PHY circuitry 704 may be arranged to transmit signals in accordance with one or more communication standards described herein.
  • the PHY circuitry 704 may be configured to transmit a HE PPDU.
  • the PHY circuitry 704 may include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 708 may include one or more processors.
  • the processing circuitry 708 may be configured to perform functions based on instructions being stored in a RAM or ROM, or based on special purpose circuitry.
  • the processing circuitry 708 may include a processor such as a general-purpose processor or special purpose processor.
  • the processing circuitry 708 may implement one or more functions associated with antennas 712, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706, and/or the memory 710. In some embodiments, the processing circuitry 708 may be configured to perform one or more of the functions/operations and/or methods described herein.
  • communication between a station (e.g., the HE stations 504 of FIG. 5 or wireless device 700) and an access point (e.g., the HE AP 502 of FIG. 5 or wireless device 700) may use associated effective wireless channels that are highly directionally dependent.
  • beamforming techniques may be utilized to radiate energy' in a certain direction with certain beam width to communicate between two devices.
  • the directed propagation concentrates transmitted energy toward a target device in order to compensate for significant energy loss in the channel between the two communicating devices.
  • Using directed transmission may extend the range of the millimeter- wave communication versus utilizing the same transmitted energy in omni-directional propagation.
  • FIG. 8 shows a generic multi-access (GMA) protocol stack 800.
  • the stack 800 includes a TCP/UDP transport layer 802, an Internet Protocol (IP) network layer 804, a generic multi-access (GMA) convergence layer 806.
  • the layer 806 may run over a 802.2 link layer control (LLC) subnetwork access protocol (SNAP) layer 809 or a non-WiFi radio 808, such as ethernet, Bluetooth, or LTE.
  • LLC link layer control
  • SNAP subnetwork access protocol
  • the 802.2 LLC/SNAP layer 809 may run over one or more WiFi Radio's, such as any of the radios 810a-c.
  • the radios 810a-c may include one or more of a 2.4 Gigahertz radio 810a, a 5G radio 810b, or a 60 Gigahertz radio 812c.
  • An application running over the protocol stack 800 may use a single IP address that may be shared among the radios 810a-c.
  • a tunneling mechanism, such as IP-in-IP may be used as needed to delivery user traffic over an individual radio.
  • FIG. 9 shows a trailer-based GMA PDU format that may be utilized by the protocol stack 800 of FIG. 8.
  • the PDU includes an IP v4 or IP v6 header 902, an IP payload 904, and a generic multi-access (GMA) trailer 906.
  • the IP header 902 may include the illustrated protocol type field 912, IP length field 914, and the IP checksum field 916.
  • the protocol type field 912 may be modified to include a predetermined value to indicate the presence of the GMA trailer 906.
  • the IP length field 914 may be set to indicate a length of the GMA PDU.
  • the IP checksum field 916 may be recalculated after changing the protocol type field 912 and IP length field 914 to reflect the new values.
  • Original values for the IP protocol type field 912, IP length field 914 and IP checksum field 916 may be include in the GMA trailer 906 in fields 922, 924, and 926 respectively. This provides for a device receiving the frame 900 recovering the original IP packet after the GMA trailer 906 is removed.
  • the trailer 906 may indicate additional information, such as a sequence number 928, to support specific multi-radio operation such as fragmentation, reordering, retransmission, concatenation, and other networking capabilities.
  • a set of control messages may manage multi-radio operation such as for discovery, capability negotiation, measurement, traffic steering.
  • FIG. 10 shows a proposed Split Link Layer (L2) based GMA control protocol stack that may be implemented in at least some of the disclosed embodiments.
  • the protocol stack 1000 includes a STA 504, AP 502, and a Controller 1050.
  • the STA includes a GMA Agent 1002a.
  • the GMA Agent 1002a generates a GMA control message 1004.
  • the GMA control message 1004 may include, as discussed in more detail below, a multi-access management services (MAMS) message, such as a MAMS control plane message.
  • MAMS multi-access management services
  • the GMA Agent 1002a may be configured to perform one or more functions of a MAMS client connection manager (CCM).
  • CCM MAMS client connection manager
  • the GMA Control message 1004 is transmitted over either a L2CAP protocol stack 1006a running over, in some aspects, a Bluetooth radio 1008a, or the GMA control message 1004 may be encapsulated within a Wi-Fi multi-band action frame 1010a, which is then sent over a WiFi layer 1012a.
  • the AP 502 includes a L2CAP layer 1006b and may receive the GMA control message 1004 from the L2C AP layer 1006a on the station 504.
  • the AP 502 may alternatively receive the GMA control message 1004 via the Wi-Fi multi-band action frame 1010a sent from the station, shown at the AP 502 as multi-band action frame 1010b.
  • the AP 502 may strip the WiFi Multi-band action frame 1010b from the GMA Control message 1004 and forward the GMA control message 1004 to the 1905.1 layer 1016a.
  • the GMA control message 1004 may then be transmitted to the controller 1050.
  • the controller 1050 may be a wireless LAN controller.
  • the wireless LAN controller may be configured to control multiple access points in some aspects.
  • the wireless LAN controller may provide for a centralized method of configuration (e.g. a control plane), where AP
  • the wireless LAN controller may be configured to perform additional functions in various embodiments.
  • the controller 1050 may be physically integrated into the access point 502.
  • the wireless LAN controller 1050 may be a physically separate hardware from the access point 502.
  • the wireless network controller 1050 may include one or more hardware components corresponding to any of the devices shown in FIGs. 1-7 above.
  • either the L2CAP layer 1006b or the WiFi Phy/Mac layer 1012b may forward the GMA control message 1004 to the 1905.1 layer 1016a.
  • the layer 1016a may implement another protocol other than 1905.1 in various aspects.
  • the 1905.1 layer 1016a may forward the message 1004 to the L1/L2 layer 1018a, which communicates the message to the L1/L2 layer 1018b.
  • the GMA control message 1004 may then be delivered to the GMA Control server 1002b.
  • the GMA control server 1002b may be configured to perform one or more functions of a MAMS network connection manager (NCM).
  • NCM MAMS network connection manager
  • FIG. 11 shows an example embodiment of a GMA control message 1100.
  • the GMA control message 1004 may be equivalent to the GMA control message 1100.
  • the GMA control message 1100 includes a device identifier 1105, a length 1110, and a payload 1115.
  • the device identifier field 1105 may uniquely identify the GMA agent transmitting the message 1100.
  • the device identifier is not an Internet Protocol (IP) address.
  • IP Internet Protocol
  • a media access control address of a radio of the transmitting device may be used as a unique identifier.
  • the device identifier field 1105 may carry a MAC address of the WiFi Phy/MAC 1012a.
  • the length field 1110 may indicate a length of the payload field 1115.
  • the payload field 1115 may carry data, such as a MAMS control plane message, examples of which are discussed with respect to FIG. 14 below.
  • FIG. 12 shows an example information element that may be transmitted or received in some of the disclosed embodiments.
  • the information element 1200 illustrated in FIG. 12 may provide a mechanism for devices to communicate support for the split architecture described above with respect to FIG. 10.
  • the information element 1200 may be a capability element (for example, an NBT capability element) or may be in a specific element.
  • the information element 1200 may be transmitted or received as part of a beacon frame probe response frame (transmitted by an AP received by a STA), or a probe request frame (transmitted by an STA received by an AP).
  • the information element 1200 may be included in a neighbor report or other elements.
  • the information element 1200 may be included by an AP to indicate the AP supports generic multi-access convergence (GMA), for example, in an association response message.
  • GMA generic multi-access convergence
  • the element id field 1202 may indicate a predetermined value indicating that it is a multi-band information element or generic multi-access information element.
  • the length field 1204 indicates a length, in bytes, of data following the length field 1204.
  • the attribute 1206 may indicate whether the device transmitting the frame supports generic multi-access convergence (GMA).
  • a first predetermined value in the attribute field 1206 indicates the transmitting device supports GMA. In some aspects, this first predetermined value is one (1). A value of zero may indicate the device does not support GMA. In some aspects, if the device does not support GMA, it does not transmit the information element 1200.
  • the indication of whether the device supports GMA may be confined to a subset of bits available in the attribute field 1206. For example, in some aspects, only one bit may be used for this purpose.
  • the information element 1200 may signal additional information.
  • the information element 1200 may signal whether multiple different capabilities are individually supported by a device transmitting the information element 1200.
  • a first predetermined set of bits in the attribute field 1206 may be used to indicate whether the transmitting device is capable of forwarding MAMS control plane messages, such as any of the messages discussed below with respect to FIG. 14. For example, if the first predetermined set of bits are set to zero (0), this may indicate the device does not have this capability, while if the first predetermined set of bits indicate a value of one (1 ), this may indicate the device does have this capability.
  • a second predetermined set of bits in the attribute field 1206 may indicate whether the device transmitting the information element 1200 is capable of forwarding MAMS data plane messages.
  • a first predetermined value in these second predetermined set of bits may indicate the transmitting device is capable, while a second predetermined value in these second predetermined set of bits map indicate the transmitting device is not capable of forwarding data plane messages.
  • Other bits in the attribute field 1206 may be reserved for future use.
  • neighbor report elements may be included in a message.
  • the elements may include a basic service set identifier and related information, such as a channel and/or a band, to allow a receiving device to locate the device transmitting the neighbor report elements.
  • Such neighbor report elements may allow a device to establish a list of neighboring BSSID's that may be good candidates for use of GMA functionality.
  • FIG. 13 shows an example of a media access control (MAC) action frame for delivering a GMA control message (e.g. 1004 or 1100) that may be implemented in some of the disclosed embodiments.
  • the action frame 1300 includes a frame control field 1305, duration field 1310, destination address field 1315, source address field 1320, basic service set identifier field 1325, sequence control field 1330, category field 1335, action field 1340, elements field(s) 1345, and a frame check sequence field 1350.
  • the action frame 1300 may deliver the GMA control message 1004 or 1100 over an access link.
  • the frame 1300 may be defined as a different type of action frame, named a "multi-band action frame.”
  • the multi- band action frame may be distinguished from other types of action frames via a first predetermined value in the category field 1335.
  • the action field 1340 may be set to a value of zero (0).
  • the category field 1335 may have a value consist with a management action frame but the action field 1340 may be set to a second predetermined value that indicates the frame is the different type of action frame (i.e. "multi-band action frame").
  • the elements field 1345 of the multi-band action frame may carry a GMA control message, such as 1004 or 1100.
  • FIG. 14 shows some example MAMS control plane messages.
  • a multi-access management services (MAMS) architecture provides for a network connection manager (NCM) and a client connection manager (CCM) in a control plane.
  • NCM network connection manager
  • CCM client connection manager
  • N-MADP network multi-access data proxy
  • C-MADP client multi-access data proxy
  • the MAMS control plane procedures provide for configuration of user plane functions, such as C-MADP and N-MADP, at the client and network respectively.
  • the message 1400 is an example of a MX discovery message.
  • the MX discovery message 1400 includes a type indicator 1402a, a multi-access management services (MAMS) version 1404a, and a sequence number field 1406a.
  • the type indicator field 1402a indicates a type of the message 1400, e.g. MX discovery, mx capability (see below), etc.
  • the MAMS version field 1404a indicates a version of the MAMs control protocol in use by a device transmitting the message 1400.
  • the sequence number field 1406a is an incremented integer to uniquely identify a transaction of message exchange, e.g. MX Capability' Req/Response.
  • a second message 1420 illustrated in FIG. 14 is an example MX system information message 1420.
  • the example MX system information message includes a type indicator field 1402b, a MAMS version field 1404b, a sequence number field 1406c, a connection identifier field 1407, a connection type field 1408, and a network connection manager (NCM) endpoint address field 1410.
  • the type indicator field 1402b, version field 1404b, and the sequence number field 1406b have functions similar to those described above for fields 1402a, 1404a, and 1406a respectively.
  • the NCM endpoint address field 1410 may include an IP address or Fully Qualified Domain Name (FQDN) and/or a port number in some aspects.
  • the example MX system information message 1420 may be used to acknowledge the MX discovery message 1400 in some aspects.
  • FIG. 14 also illustrates an example MX Capability request message 1440.
  • a client connection manager may determine an IP address and port and transmit a MX capability request message 1440.
  • the example MX capability' request message 1440 includes a type indicator field 1402c, an MX feature activation list field 1412, a number of anchor connections field 1414.
  • the message 1440 may include a connection identifier field 1416, and a connection type field 1418.
  • the connection identifier field 1416 and connection type field 1418 may repeat a number of times as indicated by the number of anchor connections field 1414.
  • the connection type field 1418 may indicate whether the connection is a Wi-Fi connection, 5G NR connection, MulteFire connection, or LTE connection in some aspects.
  • the example MX capability request message 1440 also includes a number of delivery connections (access links) field 1420.
  • a connection identifier field 1422 and connection type field 1424 repeat a number of times equivalent to a value stored in the number of delivery connections field 1420.
  • the connection type field 1424 may indicate whether the delivery connection is a Wi-Fi connection, 5G NR connection, MulteFire connection, or LTE connection in some aspects.
  • the example MX capability request message 1440 may also include an MX convergence method support list field 1426 and a mx adaptation method support list field 1428.
  • the MX convergence method support list field 1426 may indicate whether the transmitting device of the message trailer based MX convergence, MPTCP Proxy, GRE Aggregation Proxy.
  • Adaptation Method Support List field 1428 may indicate whether the transmitting device supports UDP Tunnel without DTLS, UDP Tunnel with DTLS, IPsec Tunnel (e.g. RFC 3948), or a client network address translation.
  • FIG. 14 shows three examples of MAMS control plane messages
  • other MAMS control plane messages not shown in FIG. 14 include a MX capability response message, MX capability acknowledgement message, MX session terminate, MX reconfiguration request, MX UP Setup CNF message, MX path estimation configuration message, MX active probe request message, MX traffic steering request and MX traffic steering response messages, and others.
  • FIG. 15 shows an example of a beacon frame.
  • the beacon frame 1500 includes a frame control field 1502, duration field 1504, destination address field 1506, source address field 1508, basic service set identifier field 1510, sequence/control field 1512, frame body 1514, and frame check sequence field 1516.
  • the beacon frame may be a management frame.
  • the frame control field 1502 may include a type field (not shown) that has a predetermined value indicating the frame 1500 is a management frame.
  • the frame control field 1502 may have a subtype field (also not shown) that has a value indicating the frame 1500 is a beacon frame.
  • the frame body field 1514 may include one or more of a timestamp field 1518, beacon interval field 1520, capability info field 1522, SS ID field 1524, frequency hopping (FH) parameter set field 1526, direct sequence (DS) parameter set field 1528, contention free (CF) parameter set field 1530, independent basic service set (IBSS) parameter set field 1532, traffic
  • the beacon frame 1500 also may include at least one information element 1540a Multiple information elements may be included in up to "n" information element fields, as shown by information element field 1540n.
  • information element 1200 discussed above may be included in a beacon frame, such as the example beacon frame 1500.
  • the information element 1200 may be included in any one of the IE fields 1540a-n in some aspects.
  • FIG. 16 is an example of a GMA discovery control flow that may be implemented in at least some of the disclosed embodiments.
  • the control flow 1600 shows the AP 502 transmitting a beacon message 1602.
  • the beacon message 1602 may be transmitted periodically by the AP 502 in some aspects.
  • the beacon message 1602 may include one or more of the fields discussed above with respect to beacon frame 1500 in FIG. 15.
  • the STA 504 may decode one or more information elements included in the beacon message 1602, such as the information element 1200 discussed above with respect to FIG. 12.
  • the STA 504 may determine that the AP supports the GMA forwarding capability, for example, by decoding the attribute field 1206 to determine whether a set of bits defined to include an indication of whether the AP supports GMA capability. For example, as discussed above, bit 0 of the attribute field 1206 may indicate whether the AP is capable of forwarding GMA control messages, bit one (1) may indicate whether the AP 502 is capable of forwarding GMA data packets.
  • the STA 504 may transmit an encapsulated discovery message 1604 to the AP 502.
  • the encapsulated discovery message 1604 may, in some aspects, conform to the format 1100 shown in FIG. 11.
  • the encapsulated discovery message 1604 may include an action frame, such as action frame 1300 discussed above with respect to FIG. 13.
  • the action frame 1300 of the encapsulated discovery message 1604 may cany a MAMS control plane MX discovery message (e.g. 1400) in the elements field 1345 of the action frame 1300 discussed above with respect to FIG. 13.
  • the discovery message itself such as message 1400 discussed above with respect to FIG.
  • the discovery message may include a field including a value that indicates the message is a discovery message (e.g. 1402a).
  • the discovery message may also include, in some aspects, a version indication (e.g. 1404a) for a multi-access management services (MAMS) running on the STA 504.
  • MAMS multi-access management services
  • FIG. 16 shows an example of the encapsulated discovery message 1604 as it is transmitted from the STA 504 to the AP 502.
  • the encapsulated discovery message 1604 includes the action frame 1300.
  • the elements portion 1345 of the action frame 1300 may be the GMA control message, such as the message 1004 or 1100, which may include a MAMS discovery message in the payload field 1115.
  • the AP 502 may remove the GMA control message 1004 or 1100 from the action frame 1300 and transmit the message 1004 or 1100 to the wireless LAN controller 1050.
  • FIG. 16 also shows the multi-radio controller 1050 transmitting a system information message 1420 over 1905.1 protocol to the AP 502.
  • the system information message 1420 may be included in a payload field 1115 of a GMA control message 1100 in some aspects.
  • the system information message 1420 may include one or more of the fields described above with respect to message 1420, discussed above with respect to FIG. 14.
  • the AP 502 may encapsulate the GMA control message 1100 into an action frame 1630, such as the action frame 1300 discussed above with respect to FIG. 13.
  • the AP 502 may then transmit the action frame 1630 encapsulating the GMA control message 1100 (including the system information message 1420 in the payload field 1115) to the STA 504.
  • the STA 504 may extract the GMA control message 1100 0 from the action frame 1300, and pass the GMA control message 1100 (including the system information message 1420) to the GMA agent (not shown in FIG. 16) (e.g. 1002a).
  • FIG. 17 is a flowchart of an example method of decoding an action frame.
  • one or more of the functions discussed below with respect to FIG. 17 may be performed by the application processor 111.
  • one or more of the functions discussed below with respect to FIG. 17 may be performed by the control logic 406.
  • a device performing process 1700 may be referred to as an executing device.
  • an action frame is decoded.
  • the action frame is received from an HE STA, such as the HE STA 504, discussed above with respect to FIG. 10.
  • the action frame is received from a Wi-Fi radio, such as Wi-Fi radio 1012a discussed above with respect to FIG. 10.
  • the action frame is decoded to extract a GMA control message, such as the GMA control message 1100 discussed above with respect to FIG. 11.
  • block 1710 may decode a category field of the action frame (e.g. 1335) to determine the action frame encapsulates a GMA control message. For example, in some aspects, if the category field has a first predetermined value, block 1710 may extract the GMA control message from the action frame in response. In some other aspects, an action field (e.g. 1335) of the action frame may indicate the frame carries a GMA control message. Thus, in these aspects, in response to the action field having a second predetermined value, block 1710 may extract a GMA control message from the action frame.
  • a category field of the action frame e.g. 1335
  • block 1710 may extract the GMA control message from the action frame in response.
  • the GMA control message 1100 may include a MAMS control plane message in the payload field 1115.
  • the MAMS control plane message may be an MAMS MX discovery message, such as message 1400 discussed above with respect to FIG. 14.
  • the MAMS control plane message may be at least any of the example MX messages shown in FIG. 14.
  • the GMA control message 1100 may be included in the elements field 1345 of the example action frame 1300.
  • a length may be determined by decoding the length field 1110.
  • the GMA control message, of the determined length may then be extracted from the action frame in some aspects.
  • block 1710 includes generating a beacon frame, the beacon frame including an information element indicating the HE AP supports forwarding of GMA control messages.
  • the beacon frame is generated to include an information element including one or more of the fields of information element 1200, discussed above with respect to FIG. 12.
  • the attribute field 1206 may be encoded in the beacon frame to indicate whether the HE AP supports forwarding of GMA control messages and/or forwarding of GMA data messages.
  • Block 1710 may also include configuring the HE AP to transmit the beacon frame.
  • the executing device may decode the action frame to determine a source media access control address indicated in the action frame (e.g. 1320).
  • the executing device may also decode the GMA control message to obtain a device identifier (e.g. 1105).
  • the executing device may store an association between the device identifier and the source MAC address. This association may be used later when another GMA control message is received from the controller. The association may be used to properly route GMA control messages received from the controller to the proper STA.
  • block 1710 includes receiving a second GMA control message.
  • the second GMA control message may be received over a different radio than the first GMA control message.
  • the second GMA control message may be received over a Bluetooth radio.
  • the second GMA control message may not be encapsulated in an action frame. Instead, in some aspects, the second GMA control message may be received over a L2CAP protocol.
  • Block 1710 may also include configuring the HE AP to transmit the second GMA control message to the controller.
  • the HE access point is configured to transmit the GMA control message to a controller (e.g. 1050).
  • the controller may implement a network connection manager (NCM).
  • NCM is defined as a functional entity in the network that oversees distribution of data packets over multiple available access and core network paths.
  • the controller may be a wireless LAN controller.
  • the wireless LAN controller may implement a lightweight access point protocol (LWAPP) to manage the access point.
  • LWAPP lightweight access point protocol
  • the wireless LAN controller may manage a plurality of wireless access points.
  • configuring the HE AP to transmit the GMA control message may include the application processor 111 communicating the GMA control message to a baseband processor 108.
  • the application processor 111 may share memory with the baseband processor 108.
  • the application processor 111 may write the GMA control message to the shared memory and then signal the baseband processor 108 that the message is available in the memory for transmission.
  • Other embodiments may use different technology for communication between the baseband processor 108 and the application processor 111.
  • block 1720 configures the HE AP to transmit the GMA control message over a 1905.1 protocol to the controller.
  • block 1720 includes decoding another GMA control message received from the controller.
  • the executing device may determine how to route this GMA control message may extracting a device identifier from a device identifier field (e.g. 1305) from the other GMA control message.
  • the executing device may then consult the association between device identifiers and station MAC addresses, discussed above, to obtain a MAC address for a station identified by a device identifier in the other GMA control message.
  • Block 1720 may also include generating a third action frame, and encoding the third action frame to encapsulate or store the decoded second GMA control message, for example, in an elements field (e.g. 1345).
  • a destination address e.g.
  • the second GMA control message includes a MX system information message, such as message 1420 discussed above with respect to FIG. 14, in its payload field (e.g. 1115).
  • FIG. 18 is a flowchart of an example method for encoding a
  • MAMS control plane message for transmission.
  • one or more of the functions discussed below with respect to FIG. 18 may be performed by the application processor 111.
  • one or more of the functions discussed below with respect to FIG. 18 may be performed by the control logic 406.
  • a device performing process 1800 may be referred to as an executing device.
  • the executing device may be configured to perform one or more functions associated with a MAMS client connection manager (CCM).
  • CCM MAMS client connection manager
  • the executing device may be the STA 504, as discussed above with respect to at least FIG. 10.
  • a MAMS control plane message is encoded in a GMA control message.
  • the MAMS control plane message may be included in a payload field (e.g. 1115) of the GMA control message.
  • a device identifier field (e.g. 1105) of the GMA control message may be set to a unique identifier of the executing device.
  • a media access control address or station address of the executing device may be used as the device identifier.
  • a length of the MAMS control plane message may be determined. The determined length may be encoded into a length field (e.g. 1110) of the GMA control message in some aspects.
  • an action frame is encoded to include the GMA control message.
  • the GMA control message may be encoded in an action frame, specifically, in some aspects, the GMA control message may be encoded in an elements field of the action frame (e.g. 1345).
  • a category field e.g. 1335) of the action frame is set to a predetermined value to indicate that the action frame carries or encapsulates the GMA control message.
  • an action field e.g. 1340
  • block 1810 includes associating with the access point.
  • associating with the access point may include transmitting an association request to the access point and receiving an association response from the access point, the response indicating a successful association.
  • the association response may include an association identifier for the executing device to use when identifying itself to the access point.
  • the association response may include one or more fields of the information element 1200, discussed above. In some aspects, this may provide a way for the executing device to determine whether the access point supports forwarding of GMA control and/or GMA data messages to a controller.
  • block 1810 may include encoding a second GMA control message using a logical link control and adaptation protocol (L2CAP) protocol, and configuring the HE STA to transmit the second GMA control message over a second radio.
  • the second GMA control message may also be generated to include a MAMS control plane message in its payload field.
  • the second GMA control message may also be encoded to include a device identifier (e.g. MAC address) of the executing device in a device identifier field of the GMA control message (e.g. 1105).
  • the second radio may not be a Wi-Fi radio, but instead may be, for example, a Bluetooth radio in some aspects.
  • the executing device may then transmit the second GMA control message to the controller.
  • Some aspects of block 1810 include decoding a beacon frame received from an access point.
  • the beacon frame may be received from the access point in some aspects.
  • the beacon frame may be decoded to determine whether the access point supports forwarding of GMA control messages and/or GMA data messages.
  • the beacon frame may include one or more fields of the information element 1200, discussed above with respect to FIG. 12.
  • the beacon frame may include one or more of the fields described above with respect to beacon frame 1500.
  • a high efficiency (HE) station ST A is configured to transmit the GMA control message.
  • the STA 504 may transmit the GMA control message over a variety of link technologies, including Wi-Fi or Bluetooth as two examples.
  • the GMA control message may be included in a MAC action frame, as discussed above.
  • the HE station is configured to transmit the GMA control message to an access point to which the executing device is associated.
  • the GMA control message may be transmitted using a Wi-Fi radio that provides wireless connectivity between the HE STA and an HE AP.
  • Some aspects of process 1800 further include decoding a second GMA control message.
  • the second GMA control message may include a second MAMS control plane message, which may function as a response to the first MAMS control plane message.
  • the executing device may extract the second GMA control message from a second action frame in some aspects, for example, if the second GMA control message was received from a Wi-Fi network (e.g. from an access point).
  • FIG. 19 is a flowchart of a method for receiving a MAMS control plane message.
  • one or more of the functions discussed below with respect to FIG. 19 and process 1900 may be performed by the application processor 111.
  • one or more of the functions discussed below with respect to FIG. 19 may be performed by the control logic 406.
  • a device performing process 1800 may be referred to as an executing device.
  • the executing device may be configured to perform one or more functions of a MAMS network connection manager (NCM).
  • the executing device may be the controller 1050.
  • a first generic multi-access (GMA) control message is decoded to extract a first multi-access management services (MAMS) control plane message.
  • MAMS control plane message may be extracted by decoding a length field of the GMA control message to determine a length of the first MAMS control plane message and extracting a number of bytes indicated by the determined length from a payload field of the first GMA control message.
  • the first GMA control message is received from an HE AP.
  • the first MAMS control plane message is decoded.
  • decoding the first MAMS control plane message may include at least determining a type of the first MAMS control plane message. This may be accomplished, in some aspects, by comparing a value stored in a type identifier field (e.g. 1402a-c) to a set of predetermined values that identify different types of MAMS control plane messages.
  • a type identifier field e.g. 1402a-c
  • a second MAMS control plane message may be generated.
  • the second MAMS control plane message may be generated as a MX system information message.
  • the second MAMS control plane message is encoded in a second GMA control message.
  • block 1930 includes encoding the second MAMS control plane message is a payload field of the second GMA control message (e.g. 1115).
  • a length of the second MAMS control plane message may be written to a length field of the second GMA control message (e.g. 1110).
  • a device identifier field of the second GMA control message (e.g. 1105) is assigned a value of a device identifier field of the first GMA control message (e.g. 1105).
  • the device identifier field may be a MAC address of a device running a GMA client in some aspects. In some aspects, the device identifier may uniquely identify the GMA client, but may not be a network address. The device identifier is not an Internet Protocol (IP) address.
  • IP Internet Protocol
  • a WLAN controller is configured to transmit the second GMA control message. In some aspects, the WLAN controller is configured to transmit the second GMA control message to the HE AP.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a machine readable medium
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • Example 1 is an apparatus of an access point (AP) comprising memory; and processing circuitry coupled to the memory, the AP configured to provide communications between a station (STA) and a wireless local area network (WLAN) controller without an Internet Protocol (IP) address for the STA, the processing circuitry configured to: decode a category field or an action field of a media access control (M AC) action frame received from the STA to determine the MAC action frame carries a generic multi-access (GMA) control message, the GMA control message encapsulating a multi-access management services (MAMS) control plane message; extract the GMA control message from the M AC action frame based on the determination; and configure the AP to transmit the extracted GMA control message to the wireless local, area network (WLAN) controller.
  • MAC media access control
  • MAMS multi-access management services
  • Example 2 the subject matter of Example 1 optionally includes wherein the processing circuitry is further configured to decode an elements field of the action frame to extract the GMA control message.
  • Example 3 the subject matter of any one or more of Examples 1-2 optionally include the processing circuitry being further configured to configure the AP to transmit the GMA control message over a 1905.1 protocol to the wireless LAN controller.
  • Example 4 the subject matter of any one or more of Examples 1-3 optionally include wherein the processing circuitry is further configured to: decode the action frame to determine a media access control source address: decode the GMA control message to determine a device identifier; and store an association between the media access control source address and the determined device identifier.
  • Example 5 the subject matter of Example 4 optionally includes wherein the processing circuitry is further configured to: decode a second GMA control message received from the wireless LAN controller:
  • the action frame generated to include the second GMA control message; identify an address of an STA based on the association and a device identifier indicated in the second GMA control message; and configure the AP to transmit the second action frame to the STA at the identified address.
  • Example 6 the subject matter of Example 5 optionally includes wherein the second GMA control message includes a MX system information message in a payload field of the second GMA control message.
  • Example 7 the subject matter of any one or more of Examples 1-6 optionally include wherein the processing circuitry is further configured to: generate a beacon frame, the beacon frame including an information element indicating the AP supports forwarding of GMA control messages; and configure the AP to transmit the beacon frame.
  • Example 8 the subject matter of any one or more of Examples 1-7 optionally include wherein the action frame is received from a Wi-Fi radio, and wherein the processing circuitry is further configured to decode a second GMA control message received from a second radio, and configure the AP to transmit the second GMA control message to the wireless LAN controller.
  • Example 9 the subject matter of Example 8 optionally includes the second radio being a Bluetooth radio and the second GMA control message is received from a logical link control and adaptation protocol (L2CAP) protocol.
  • L2CAP logical link control and adaptation protocol
  • Example 10 the subject matter of any one or more of
  • Examples 1-9 optionally include wherein the memory stores the action frame.
  • Example 11 the subject matter of any one or more of
  • Examples 1-10 optionally include wherein the processing circuitry comprises a baseband processor.
  • Example 12 the subject matter of any one or more of
  • Examples 1—11 optionally include transceiver circuitry coupled to a plurality of antennas, wherein the AP is configured to transmit the GMA control message over the plurality of antennas.
  • Example 13 is an apparatus of an access point (AP), the AP configured to provide communications between a station (STA) and a wireless local area network (WLAN) controller without an Internet Protocol (IP) address for the STA, the apparatus comprising: means for decoding a category field or an action field of a media access control (MAC) action frame received from the STA to determine the MAC action frame carries a generic multi-access (GMA) control message, the GMA control message encapsulating a multi-access management sendees (MAMS) control plane message; means for extracting the GMA control message from the MAC action frame based on the determination: and means for configuring the AP to transmit the extracted GMA control message to the wireless local, area network (WLAN) controller.
  • MAC media access control
  • MAMS multi-access management sendees
  • Example 14 the subject matter of Example 13 optionally includes means for decoding an elements field of the action frame to extract the GMA control message.
  • Example 15 the subject matter of any one or more of
  • Examples 13-14 optionally include configuring the AP to transmit the GMA control message over a 1905.1 protocol to the wireless LAN controller.
  • Example 16 the subject matter of any one or more of
  • Examples 13-15 optionally include means for decoding the action frame to determine a media access control source address; means for decoding the GMA control message to determine a device identifier; and means for storing an association between the media access control source address and the determined device identifier.
  • Example 17 the subject matter of Example 16 optionally includes means for decoding a second GMA control message received from the wireless LAN controller; means for generating a second action frame, the action frame generated to include the second GMA control message; means for identifying an address of an STA based on the association and a device identifier indicated in the second GMA control message; and means for configuring the AP to transmit the second action frame to the STA at the identified address.
  • Example 18 the subject matter of Example 17 optionally includes wherein the second GMA control message includes a MX system information message in a payload field of the second GMA control message.
  • Example 19 the subject matter of any one or more of
  • Examples 13-18 optionally include means for generating a beacon frame, the beacon frame including an information element indicating the AP supports forwarding of GMA control messages; and means for configuring the AP to transmit the beacon frame.
  • Example 20 the subject matter of any one or more of
  • Examples 13-19 optionally include wherein the action frame is received from a Wi-Fi radio, and apparatus further comprising means for decoding a second
  • GMA control message received from a second radio and means for configuring the AP to transmit the second GMA control message to the wireless LAN controller.
  • Example 21 the subject matter of Example 20 optionally includes the second radio being a Bluetooth radio and the second GMA control message is received from a logical link control and adaptation protocol (L2CAP) protocol.
  • L2CAP logical link control and adaptation protocol
  • Example 22 is a method for an access point (AP), the AP configured to provide communications between a station (STA) and a wireless local area network (WLAN) controller without an Internet Protocol (IP) address for the STA, the method comprising: decoding a category field or an action field of a media access control (MAC) action frame received from the STA to determine the M AC action frame carries a generic multi-access (GMA) control message, the GMA control message encapsulating a multi-access management services (MAMS) control plane message; extracting the GMA control message from the MAC action frame based on the determination; and configuring the AP to transmit the extracted GMA control message to the wireless local, area network (WL AN) controller.
  • MAC media access control
  • MAMS multi-access management services
  • Example 23 the subject matter of Example 22 optionally includes decoding an elements field of the action frame to extract the GMA control message.
  • Example 24 the subject matter of any one or more of
  • Examples 22-23 optionally include configuring the AP to transmit the GMA control message over a 1905.1 protocol to the wireless LAN controller.
  • Example 25 the subject matter of any one or more of
  • Examples 22-24 optionally include decoding the action frame to determine a media access control source address; decoding the GMA control message to determine a device identifier; and storing an association between the media access control source address and the determined device identifier.
  • Example 26 the subject matter of Example 25 optionally includes decoding a second GMA control message received from the wireless LAN controller; generating a second action frame, the action frame generated to include the second GMA control message; identifying an address of an STA based on the association and a device identifier indicated in the second GMA control message; and configuring the AP to transmit the second action frame to the STA at the identified address.
  • Example 27 the subject matter of Example 26 optionally includes wherein the second GMA control message includes a MX system information message in a payload field of the second GMA control message.
  • Example 28 the subject matter of any one or more of
  • Examples 22-27 optionally include generating a beacon frame, the beacon frame including an information element indicating the AP supports forwarding of GMA control messages; and configuring the AP to transmit the beacon frame.
  • Example 29 the subject matter of any one or more of
  • Examples 22-28 optionally include wherein the action frame is received from a Wi-Fi radio, and the method further comprising decoding a second GM A control message received from a second radio, and configuring the AP to transmit the second GMA control message to the wireless LAN controller.
  • Example 30 the subject matter of Example 29 optionally includes the second radio being a Bluetooth radio and the second GMA control message is received from a logical link control and adaptation protocol (L2CAP) protocol.
  • L2CAP logical link control and adaptation protocol
  • Example 31 is a non-transitory computer readable storage medium comprising instructions for an access point (AP), the AP configured to provide communications between a station (STA) and a wireless local area network (WLAN) controller without an Internet Protocol (IP) address for the
  • AP access point
  • STA station
  • WLAN wireless local area network
  • IP Internet Protocol
  • STA the instructions, when executed by one or more hardware processors, cause the one or more hardware processors to perform operations comprising:
  • MAC media access control
  • MAMS multi-access management services
  • Example 32 the subject matter of Example 31 optionally includes the operations further comprising decoding an elements field of the action frame to extract the GMA control message.
  • Example 33 the subject matter of any one or more of
  • Examples 31-32 optionally include configuring the AP to transmit the GMA control message over a 1905.1 protocol to the wireless LAN controller.
  • Example 34 the subject matter of any one or more of
  • Examples 31 -33 optionally include the operations further comprising: decoding the action frame to determine a media access control source address; decoding the GMA control message to determine a device identifier; and storing an association between the media access control source address and the determined device identifier.
  • Example 35 the subject matter of any one or more of
  • Examples 25-34 optionally include the operations further comprising: decoding a second GMA control message received from the wireless LAN controller; generating a second action frame, the action frame generated to include the second GMA control message; identifying an address of an STA based on the association and a device identifier indicated in the second GMA control message; and configuring the AP to transmit the second action frame to the STA at the identified address.
  • Example 36 the subject matter of Example 35 optionally includes wherein the second GM A control message includes a MX system information message in a payload field of the second GMA control message.
  • Example 37 the subject matter of any one or more of Examples 31-36 optionally include the operations further comprising:
  • the beacon frame including an information element indicating the AP supports forwarding of GMA control messages; and configuring the AP to transmit the beacon frame.
  • Example 38 the subject matter of any one or more of
  • Examples 31-37 optionally include wherein the action frame is received from a Wi-Fi radio, and the operations further comprising decoding a second GMA control message received from a second radio, and configuring the AP to transmit the second GMA control message to the wireless LAN controller.
  • Example 39 the subject matter of Example 38 optionally includes wherein the second radio is a Bluetooth radio and the second GMA control message is received from a logical link control and adaptation protocol (L2CAP) protocol.
  • L2CAP logical link control and adaptation protocol
  • Example 40 is an apparatus of a station (STA) comprising memory; and processing circuitry coupled to the memory, the STA configured to communicate with a wireless local area network (WL AN) controller without use of an Internet Protocol (IP) address for the STA, the processing circuitry configured to: encode a generic multi-access (GMA) management sendees (MAMS) control plane message in a GMA control message; encode a device identifier of the STA in the GMA control message; encode the GMA control message in a media access control (MAC) action frame; encode a category field or an action field of the action frame to indicate the action frame encodes the GMA control message and configure the station to transmit the action frame to an access point (AP).
  • GMA generic multi-access
  • MAMS management sendees
  • MAC media access control
  • AP access point
  • Example 41 the subject matter of Example 40 optionally includes wherein the action frame is transmitted over a first radio, and the processing circuitry is further configured to: encode a second GMA control message including a second MAMS control plane message using a logical link control and adaptation protocol (L2CAP) protocol; and configure the STA to transmit the second GMA control message over a second ratio.
  • L2CAP logical link control and adaptation protocol
  • Example 42 the subject matter of Example 41 optionally includes wherein the first radio is a Wi-Fi radio and the second radio is a Bluetooth radio.
  • Example 43 the subject matter of any one or more of Examples 40-42 optionally include wherein the processing circuitry is further configured to decode a beacon frame to determine whether the AP supports forwarding of GMA control messages; and encode the MAMS control plane message in the GMA control message in response to the determination.
  • Example 44 is an apparatus of a station (STA), the STA configured to communicate with a wireless local area network (WLAN) controller without use of an Internet Protocol (IP) address for the STA, the apparatus comprising: means for encoding a generic multi-access (GMA) management services (MAMS) control plane message in a GMA control message; means for encoding a device identifier of the STA in the GMA control message; means for encoding the GMA control message in a media access control (MAC) action frame; means for encoding a category field or an action field of the action frame to indicate the action frame encodes the GMA control message; and means for configuring the station to transmit the action frame to an access point (AP).
  • GMA generic multi-access
  • MAMS management services
  • Example 45 the subject matter of Example 44 optionally includes wherein the action frame is transmitted over a first radio, and the method further comprises: means for encoding a second GMA control message including a second MAMS control plane message using a logical link control and adaptation protocol (L2CAP) protocol; and means for configuring the STA to transmit the second GMA control message over a second ratio.
  • L2CAP logical link control and adaptation protocol
  • Example 46 the subject matter of Example 45 optionally includes wherein the first radio is a Wi-Fi radio and the second radio is a Bluetooth radio.
  • Example 47 the subject matter of any one or more of Examples 44-46 optionally include means for decoding a beacon frame to determine whether the AP supports forwarding of GMA control messages; and means for encoding the MAMS control plane message in the GMA control message in response to the determination.
  • Example 48 is a method for a station (STA), the STA configured to communicate with a wireless local area network (WLAN) controller without use of an Internet Protocol (IP) address for the STA, the method comprising: encoding a generic multi-access (GMA) management services (MAMS) control plane message in a GMA control message; encoding a device identifier of the STA in the GMA control message; encoding the GMA control message in a media access control (MAC) action frame; encoding a category field or an action field of the action frame to indicate the action frame encodes the GMA control message; and configuring the station to transmit the action frame to an access point (AP).
  • GMA generic multi-access
  • MAMS management services
  • Example 49 the subject matter of Example 48 optionally includes wherein the action frame is transmitted over a first radio, and the method further comprises: encoding a second GMA control message including a second MAMS control plane message using a logical link control and adaptation protocol (L2CAP) protocol; and configuring the STA to transmit the second
  • L2CAP logical link control and adaptation protocol
  • Example 50 the subject matter of Example 49 optionally includes wherein the first radio is a Wi-Fi radio and the second radio is a Wi-Fi radio.
  • Example 51 the subject matter of any one or more of Examples 48-50 optionally include decoding a beacon frame to determine whether the AP supports forwarding of GMA control messages; and encoding the MAMS control plane message in the GMA control message in response to the determination.
  • Example 52 is a non-transitory computer readable medium comprising instructions for a station (STA), the STA configured to communicate with a wireless local area network (WLAN) controller without use of an Internet Protocol (IP) address for the STA, the instructions, when executed, causing one or more hardware processors to perform operations comprising: encoding a generic multi-access (GMA) management services (MAMS) control plane message in a GMA control message: encoding a device identifier of the STA in the GMA control message; encoding the GMA control message in a media access control (MAC) action frame; encoding a category field or an action field of the action frame to indicate the action frame encodes the GMA control message; and configuring the station to transmit the action frame to an access point (AP).
  • GMA generic multi-access
  • MAMS management services
  • Example 53 the subject matter of Example 52 optionally includes wherein the action frame is transmitted over a first radio, and the method further comprises: encoding a second GMA control message including a second MAMS control plane message using a logical link control and adaptation protocol (L2CAP) protocol; and configuring the STA to transmit the second GMA control message over a second ratio.
  • L2CAP logical link control and adaptation protocol
  • Example 54 the subject matter of Example 53 optionally includes wherein the first radio is a Wi-Fi radio and the second radio is a Bluetooth radio.
  • Example 55 the subject matter of any one or more of Examples 52-54 optionally include decoding a beacon frame to determine whether the AP supports forwarding of GMA control messages; and encoding the MAMS control plane message in the GMA control message in response to the determination.
  • Example 56 is an apparatus of a wireless local area network (WLAN) controller comprising memory; and processing circuitry coupled to the memory, the processing circuitry configured to: decode a first generic multi- access (GMA) control message from an access point (AP) AP to extract a multiaccess management services (MAMS) control plane message; decode the MAMS control plane message; generate a second MAMS control plane message in response to the decoding of the MAMS control plane message; encode the second MAMS control plane message in a second GMA control message; decode the first GMA control message to determine a device identifier of a device that generated the first GMA control message: encode the second GMA control message to indicate the determined device identifier; and configure the WLAN controller to transmit the second GMA control message to the AP.
  • GMA generic multi- access
  • MAMS multiaccess management services
  • Example 57 the subject matter of Example 56 optionally includes wherein the processing circuitry is further configured to: decode a length field of the GMA control message to obtain a length of the MAMS control plane message; and decode a payload field of the GMA control message based on the obtained length to extract the MAMS control plane message.
  • Example 58 the subject matter of any one or more of Examples 56-57 optionally include wherein the processing circuitry is further configured to: determine a length of the second MAMS control plane message; encode the length in a length field of the second GMA control message; and encode the second MAMS control plane message in a payload field of the second GMA control message.
  • Example 59 is an apparatus for a wireless local area network (WLAN) controller, the apparatus comprising: means for decoding a first generic multi-access (GMA) control message from an access point (AP) AP to extract a multi-access management services (MAMS) control plane message; means for decoding the MAMS control plane message; means for generating a second MAMS control plane message in response to the decoding of the MAMS control plane message; means for encoding the second MAMS control plane message in a second GMA control message; means for decoding the first GMA control message to determine a device identifier of a device that generated the first GMA control message; means for encoding the second GMA control message to indicate the determined device identifier; and means for configuring the WLAN controller to transmit the second GMA control message to the AP.
  • GMA generic multi-access
  • MAMS multi-access management services
  • Example 60 the subject matter of Example 59 optionally includes means for decoding a length field of the GMA control message to obtain a length of the MAMS control plane message; and means for decoding a payload field of the GMA control message based on the obtained length to extract the MAMS control plane message.
  • Example 61 the subject matter of any one or more of
  • Examples 59-60 optionally include means for determining a length of the second MAMS control plane message; means for encoding the length in a length field of the second GMA control message; and means for encoding the second MAMS control plane message in a payload field of the second GM A control message.
  • Example 62 is a method for a wireless local area network (WLAN) controller, the method comprising: decoding a first generic multiaccess (GMA) control message from an access point (AP) AP to extract a multi- access management services (MAMS) control plane message; decoding the MAMS control plane message; generating a second MAMS control plane message in response to the decoding of the MAMS control plane message; encoding the second MAMS control plane message in a second GMA control message; decoding the first GMA control message to determine a device identifier of a device that generated the first GMA control message; encoding the second GMA control message to indicate the determined device identifier; and configuring the WLAN controller to transmit the second GMA control message to the AP.
  • GMA generic multiaccess
  • MAMS multi- access management services
  • Example 63 the subject matter of Example 62 optionally includes decoding a length field of the GMA control message to obtain a length of the MAMS control plane message; and decoding a payload field of the GMA control message based on the obtained length to extract the MAMS control plane message.
  • Example 64 the subject matter of any one or more of
  • Examples 62-63 optionally include determining a length of the second MAMS control plane message; encoding the length in a length field of the second GMA control message; and encoding the second M AMS control plane message in a payload field of the second GMA control message.
  • Example 65 is a non-transitory computer readable medium for a wireless local area network (WLAN) controller comprising instructions that when executed by one or more hardware processors, cause the one or more hardware processors to perform operations comprising: decoding a first generic multi-access (GMA) control message from an access point (AP) AP to extract a multi-access management services (MAMS) control plane message; decoding the MAMS control plane message; generating a second MAMS control plane message in response to the decoding of the MAMS control plane message; encoding the second MAMS control plane message in a second GMA control message; decoding the first GMA control message to determine a device identifier of a device that generated the first GMA control message; encoding the second GMA control message to indicate the determined device identifier; and configuring the WLAN controller to transmit the second GMA control message to the AP.
  • GMA generic multi-access
  • MAMS multi-access management services
  • Example 66 the subject matter of Example 65 optionally includes the operations further comprising: decoding a length field of the GMA control message to obtain a length of the MAMS control plane message; and decoding a payload field of the GMA control message based on the obtained length to extract the MAMS control plane message.
  • Example 67 the subject matter of any one or more of
  • Examples 65-66 optionally include the operations further comprising:
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • modules are temporari ly confi gured, each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Various embodiments may be implemented fully or partially in software and/or firmware.
  • This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein.
  • the instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • Such a computer-readable medium may include any tangible non- transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, etc.

Landscapes

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

Abstract

L'invention concerne des procédés, des dispositifs et des supports de stockage lisibles par ordinateur pour une connexion de commande de bout en bout fractionnée entre une station et un réseau (contrôleur) en deux parties, appelées accès et amenée pour plus de commodité. La liaison d'accès peut relier la station et son point d'accès (AP) associé. Selon un aspect, l'invention concerne un appareil d'un point d'accès (AP) comprenant une mémoire ; et un circuit de traitement relié à la mémoire, le circuit de traitement étant configuré pour décoder une trame d'action reçue depuis une station pour en extraire un message de commande multi-accès générique (GMA) ; et pour configurer l'AP en vue de la transmission du message de commande GMA à un contrôleur.
PCT/US2018/013355 2017-10-20 2018-01-11 Architecture de réseau segmentée pour convergence multi-accès générique WO2019078911A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762575274P 2017-10-20 2017-10-20
US62/575,274 2017-10-20

Publications (1)

Publication Number Publication Date
WO2019078911A1 true WO2019078911A1 (fr) 2019-04-25

Family

ID=66174561

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/013355 WO2019078911A1 (fr) 2017-10-20 2018-01-11 Architecture de réseau segmentée pour convergence multi-accès générique

Country Status (1)

Country Link
WO (1) WO2019078911A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114430932A (zh) * 2019-09-26 2022-05-03 高通股份有限公司 用于无线局域网(wlan)中的多链路操作的地址转译

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030169713A1 (en) * 2001-12-12 2003-09-11 Hui Luo Zero-configuration secure mobility networking technique with web-base authentication interface for large WLAN networks
US20140119353A1 (en) * 2012-10-26 2014-05-01 Research In Motion Limited Multiple access point name and ip service connectivity
US20150264726A1 (en) * 2014-03-13 2015-09-17 Jing Zhu Bearer mobility and splitting in a radio access network-based, 3rd generation partnership project network having an integrated wireless local area network
WO2017011026A1 (fr) * 2015-07-13 2017-01-19 Intel Corporation Fractionnement de porteuse

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030169713A1 (en) * 2001-12-12 2003-09-11 Hui Luo Zero-configuration secure mobility networking technique with web-base authentication interface for large WLAN networks
US20140119353A1 (en) * 2012-10-26 2014-05-01 Research In Motion Limited Multiple access point name and ip service connectivity
US20150264726A1 (en) * 2014-03-13 2015-09-17 Jing Zhu Bearer mobility and splitting in a radio access network-based, 3rd generation partnership project network having an integrated wireless local area network
WO2017011026A1 (fr) * 2015-07-13 2017-01-19 Intel Corporation Fractionnement de porteuse

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA ET AL.: "Control Plane Protocols and Procedures for Multiple Access Management Services", DRAFT-ZHU-INTAREA-MAMS-CONTROL-PROTOCOL-01, 27 March 2017 (2017-03-27), pages 1 - 19, XP015118910, Retrieved from the Internet <URL:http://www.watersprings.org/pub/id/draft-zhu-intarea-mams-control-protocol-01.pdf> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114430932A (zh) * 2019-09-26 2022-05-03 高通股份有限公司 用于无线局域网(wlan)中的多链路操作的地址转译

Similar Documents

Publication Publication Date Title
US11632752B2 (en) Methods for multi-link setup between a multi-link access point (AP) logical entity and a multi-link non-AP logical entity
US11503605B2 (en) Extreme high throughput physical layer data rate
US11558777B2 (en) Methods of multi-link buffer management without block acknowledgement (BA) negotiation
US11051174B2 (en) Grouping of access points (AP) into multi-AP groups to enable coordination of downlink transmissions
US11856565B2 (en) Communicating elements between multi-link devices
US20210153125A1 (en) Station (sta), access point (ap) and methods to indicate a restriction of contention based access
WO2018232138A1 (fr) Rapports de voisinage à 6 ghz et éléments de capacité et de fonctionnement
US10869310B2 (en) Classification of basic service sets based on transmission opportunity holder addresses
WO2018217901A1 (fr) Coordination multi-connectivité
US11350299B2 (en) Received signal strength indicator thresholds for transitions
EP4229993A1 (fr) Résolution de défaut d&#39;appariement de machine à états à liaisons multiples
US11234174B2 (en) Zero latency BSS transition with on-channel tunneling (OCT)
WO2018164707A1 (fr) Station (sta) de l&#39;internet des objets (ido), point d&#39;accès (ap) et procédés de communication non associée
US20230097045A1 (en) Multi-link operating channel validation
WO2019078911A1 (fr) Architecture de réseau segmentée pour convergence multi-accès générique
US20230164676A1 (en) Basic service set channel operation
US20230094028A1 (en) Dynamic puncturing with dynamic signaling
US20220330099A1 (en) Quality of service policies in wireless lans
US20230380001A1 (en) Non-collocated ap mld reconfiguration
US20230371101A1 (en) Non-collocated ap mld transition
US20230337017A1 (en) Crosslink management frames for non-collocated mlds
US20230379855A1 (en) Critical updates for non-collocated ap mlds
US20240137188A1 (en) P2p resource request signaling
US20230209602A1 (en) Clear-to-send duration field adjustments
WO2022081873A1 (fr) Demandes d&#39;enquêtes réduites à eht

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: 18867393

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18867393

Country of ref document: EP

Kind code of ref document: A1