[go: up one dir, main page]

WO2024005794A1 - Planification efficace dans une bande de 60 ghz - Google Patents

Planification efficace dans une bande de 60 ghz Download PDF

Info

Publication number
WO2024005794A1
WO2024005794A1 PCT/US2022/035372 US2022035372W WO2024005794A1 WO 2024005794 A1 WO2024005794 A1 WO 2024005794A1 US 2022035372 W US2022035372 W US 2022035372W WO 2024005794 A1 WO2024005794 A1 WO 2024005794A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
twt
frame
circuitry
ghz
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2022/035372
Other languages
English (en)
Inventor
Laurent Cariou
Dmitry Akhmetov
Dibakar Das
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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 Corp filed Critical Intel Corp
Priority to PCT/US2022/035372 priority Critical patent/WO2024005794A1/fr
Publication of WO2024005794A1 publication Critical patent/WO2024005794A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
    • 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

  • This disclosure generally relates to systems and methods for wireless communications and, more particularly, to efficient scheduling in 60 GHz band.
  • Wireless devices are becoming widely prevalent and are increasingly requesting access to wireless channels.
  • the Institute of Electrical and Electronics Engineers (IEEE) is developing one or more standards that utilize Orthogonal Frequency-Division Multiple Access (OFDMA) in channel allocation.
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • FIG. 1 is a network diagram illustrating an example network environment for efficient 60 GHz scheduling, in accordance with one or more example embodiments of the present disclosure.
  • FIGs. 2-3 depict illustrative schematic diagrams for efficient 60 GHz scheduling, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 4 illustrates a flow diagram of a process for an illustrative efficient 60 GHz scheduling system, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 illustrates a functional diagram of an exemplary communication station that may be suitable for use as a user device, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 illustrates a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 is a block diagram of a radio architecture in accordance with some examples.
  • FIG. 8 illustrates an example front-end module circuitry for use in the radio architecture of FIG. 7, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 9 illustrates an example radio IC circuitry for use in the radio architecture of FIG. 7, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 10 illustrates an example baseband processing circuitry for use in the radio architecture of FIG. 7, in accordance with one or more example embodiments of the present disclosure.
  • WiFi-8 will operate in the 60 GHz bands by reusing some baseline PHY PPDUs (e.g., 1 lac) with SU transmissions. This is in contrast to IEEE 802.1 lax (“11 ax”) or IEEE 802.11be (“l lbe”) design which assumes MU operation using OFDMA in both UL and DL. Because of the very high data rate offered by those bands, the inefficiency of SU transmissions will largely be offset.
  • a STA typically uses EDCA for channel access even in a TWT SP.
  • the 60 GHz bands use the same EDCA contention method as in lower bands with respect to slot time value, AIFSN duration, and contention window, this may constitute significant time overhead concerning actual data transmission time.
  • the 60 GHz band is expected to be typically OBSS contention- free which opens the possibility of a much higher degree of interference management within the BSS even without EDCA.
  • the contention time for channel access can be significantly shortened in scheduled TWT SPs in 60 GHz bands.
  • an AP may poll a STA using a BSRP or NFRP TF to obtain its UL transmission requirements before allocating resources to it in a Basic TF. Since the 60 GHz band may only allow SU PPDUs, a polling mechanism may need to be defined.
  • Example embodiments of the present disclosure relate to systems, methods, and devices for efficient scheduling in 60 GHz band for WiFi- 8.
  • an efficient 60 GHz scheduling system may facilitate that the TWT SPs defined in 60 GHz band can be classified based on whether the initial PPDU in the SP is a directional PPDU or not.
  • an efficient 60 GHz scheduling system may facilitate that inside a SP where the initial PPDU is a directional PPDU, the STA that is assigned the role of a transmitter (“initiator STA”) can obtain channel aggressively using a short deferral time (e.g., PIFS).
  • a short deferral time e.g., PIFS
  • an efficient 60 GHz scheduling system may facilitate that soliciting BSR information or polling can be performed by defining new TFs for 60 GHz for this purpose or by redefining the existing TFs like MU-RTS or BSRP.
  • the TWT Setup frame may contain one or more (“60 GHz link specific info”) information (some of the information may be conditionally present).
  • the information may include whether the TWT SP can be initiated with a directional PPDU. If yes, one of the STAs assumes the role of an initiator STA and is responsible for transmitting Data frames within the SP from whom one or more other responder STAs are expected to receive directional PPDUs.
  • the information may also include whether the STA sending the TWT Setup frame is going to be an initiator or responder in the SP.
  • the information may also include if the initiator is a non-AP STA whether the SP is only for UL traffic or for both UL and P2P traffic or only for P2P traffic.
  • the information may also include whether the initiator STA is going to return any unused time in the SP to the responder STA.
  • the information may also include the contention period to be used prior to channel access.
  • FIG. 1 is a network diagram illustrating an example network environment of efficient 60 GHz scheduling, according to some example embodiments of the present disclosure.
  • Wireless network 100 may include one or more user devices 120 and one or more access points(s) (AP) 102, which may communicate in accordance with IEEE 802.11 communication standards.
  • the user device(s) 120 may be mobile devices that are non- stationary (e.g., not having fixed locations) or may be stationary devices.
  • the user devices 120 and the AP 102 may include one or more computer systems similar to that of the functional diagram of FIG. 5 and/or the example machine/ system of FIG. 6.
  • One or more illustrative user device(s) 120 and/or AP(s) 102 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of- service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 and the AP(s) 102 may be STAs.
  • STA station
  • An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of- service (QoS) STA, a dependent STA, and a hidden STA.
  • QoS quality-of- service
  • the one or more illustrative user device(s) 120 and/or AP(s) 102 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP).
  • PBSS personal basic service set
  • PCP/AP control point/access point
  • the user device(s) 120 (e.g., 124, 126, or 128) and/or AP(s) 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device.
  • user device(s) 120 and/or AP(s) 102 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabookTM computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (loT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA
  • the term “Internet of Things (loT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection.
  • An loT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like.
  • QR quick response
  • RFID radio-frequency identification
  • An loT device can have a particular set of attributes (e.g., a device state or status, such as whether the loT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a lightemitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an loT network such as a local ad-hoc network or the Internet.
  • a device state or status such as whether the loT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a lightemitting function, a sound-emitting function, etc.
  • loT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the loT network.
  • loT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc.
  • the loT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).
  • “legacy” Internet-accessible devices e.g., laptop or desktop computers, cell phones, etc.
  • devices that do not typically have Internet-connectivity e.g., dishwashers, etc.
  • the user device(s) 120 and/or AP(s) 102 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3GPP standards. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired. The user device(s) 120 may also communicate peer-to-peer or directly with each other with or without the AP(s) 102.
  • Any of the user device(s) 120 e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired.
  • the user device(s) 120 may also communicate peer-to-peer or directly with each other with or without the AP(s) 102.
  • any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs).
  • MANs metropolitan area networks
  • WANs wide area networks
  • LANs local area networks
  • PANs personal area networks
  • any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, micro wave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.
  • medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, micro wave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.
  • HFC hybrid fiber coaxial
  • Any of the user device(s) 120 (e.g., user devices 124, 126, 128) and AP(s) 102 may include one or more communications antennas.
  • the one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s) 120 (e.g., user devices 124, 126 and 128), and AP(s) 102.
  • suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi- omnidirectional antennas, or the like.
  • the one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 120 and/or AP(s) 102.
  • Any of the user device(s) 120 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network.
  • Any of the user device(s) 120 e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions.
  • Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional reception from one or more defined receive sectors.
  • MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming.
  • user devices 120 and/or AP(s) 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.
  • any of the user devices 120 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 and AP(s) 102 to communicate with each other.
  • the radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols.
  • the radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards.
  • the radio component in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g. 802.11b, 802.11g, 802.1 In, 802.1 lax), 5 GHz channels (e.g. 802.1 In, 802.1 lac, 802.1 lax, 802.11be, etc.), 6 GHz channels (e.g., 802.1 lax, 802.11be, etc.), or 60 GHZ channels (e.g. 802. Had, 802. Hay). 800 MHz channels (e.g. 802.11 ah).
  • the communications antennas may operate at 28 GHz and 40 GHz.
  • non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra-High Frequency (UHF) (e.g. IEEE 802.11af, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications.
  • the radio component may include any known receiver and baseband suitable for communicating via the communications protocols.
  • the radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband.
  • LNA low noise amplifier
  • A/D analog-to-digital
  • a user device 120 may be in communication with one or more APs 102.
  • one or more APs 102 may implement an efficient 60 GHz scheduling 142 with one or more user devices 120.
  • the one or more APs 102 may be multi-link devices (MLDs) and the one or more user device 120 may be non-AP MLDs.
  • MLDs multi-link devices
  • Each of the one or more APs 102 may comprise a plurality of individual APs (e.g., API, AP2, ..., APn, where n is an integer) and each of the one or more user devices 120 may comprise a plurality of individual STAs (e.g., STA1, STA2, ..., STAn).
  • the AP MLDs and the non-AP MLDs may set up one or more links (e.g., Linkl, Link2, . . ., Linkn) between each of the individual APs and STAs.
  • links e.g., Linkl, Link2, . . ., Linkn
  • FIG. 2 depicts an illustrative schematic diagram for an efficient 60 GHz scheduling system, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 2. shows an example of how an initiator AP may return unused time to a STA.
  • the example in FIG.2 shows an AP using an MU-RTS TXS frame to return any remaining part of a SP in which the AP is the initiator to a STA during an allocated SP.
  • FIG. 3 shows an example of how the AP may signal slot allocation information using a cross-link TWT setup in sub-7 GHz.
  • FIG. 3 shows the example of a STA negotiating an individual TWT SP on a 60 GHz link where the SP is divided into multiple slots. Also shown is the resultant split of the TBTT interval into slots where the AP is unavailable to listen for non-directional PPDUs sent from an unscheduled STA as well as ones where it is available to listen those PPDUs.
  • a TWT SP is initiated with non-directional PPDU (e.g., on link 1 between STA1 of STA MLD and API of AP MLD)
  • the initiator or responder roles may not be defined.
  • the 802.11 specifications may define an AP to be the default initiator of a TWT SP.
  • an efficient 60 GHz scheduling system may define an AP to be the default initiator of every TXOP in the 60 GHz band.
  • UL uplink
  • P2P managed peer-to-peer
  • the TWT setup frame may contain an additional element carrying the 60 GHz link-specific information. This element may be carried if the TWT setup frame is sent in a 60 GHz link or the TWT setup frame contains a TWT element with a Link ID bitmap signaling whether this TWT SP is applied to a 60 GHz link.
  • Table 1 shows an example element format containing information for a TWT SP setup in a 60 GHz link. This element may be sent on a sub-7 GHz link of an MLD to indicate that the TWT SP is applied to a 60 GHz link.
  • Table 2 shows an example TWT setup frame action field format, where if the action field is set to 5, this indicates that the TWT setup frame will contain 60 GHz SP information.
  • a Reserved field in the TWT element (e.g., bit B7) may be used to signal the presence of an additional field containing the 60 GHz link-specific information.
  • an initiator ST A can initiate communication with multiple other STAs within that SP.
  • an AP may setup a broadcast TWT SP where it communicates with multiple associated STAs within the SP.
  • a STA may be granted an individual or Broadcast TWT SP within which it can initiate transmissions to either its associated AP or for P2P or both. Additional signaling may be indicated as part of the SP negotiation to identify and/or regulate how the STA is going to use this SP.
  • the remaining SP may be allocated to the responder STA. For example:
  • the AP may transmit a Ctrl frame (e.g., MU-RTS TXS frame) or include signaling in the last DL frame (e.g., similar to RDG) returning the remaining time (in the SP or the remaining TXOP) to a responding STA as the transmitter while the AP itself may switch back to the role of a responder and may be prepared to receive directional UL PPDUs from the initiator. Additional signaling may be defined to indicate what the role of the AP is going to be for the rest of the SP.
  • a Ctrl frame e.g., MU-RTS TXS frame
  • signaling in the last DL frame e.g., similar to RDG
  • Additional signaling may be defined to indicate what the role of the AP is going to be for the rest of the SP.
  • the STA may transmit a Ctrl or Mgt frame or include some signaling in the last UL PPDU sent to its associated AP that the STA is going to switch back to the role of a responder at the end of this frame transmission.
  • the STA may transmit a Ctrl or Mgt frame or include some signaling in the last UL PPDU (e.g., in an A-Ctrl field) sent to its associated AP that the STA is not going to transmit any more PPDUs to the AP in the remaining time.
  • the STA or a collocated STA may still transmit as an initiator of a P2P link in the remaining time.
  • the AP is expected to switch back to omni-Rx for the remaining time.
  • the initiator STA may switch its mode to receive only non-directional initial PPDU.
  • a non-AP STA that initiates the SP or one that has been granted allocation for the remaining time in a SP for UL or P2P traffic may send a unicast frame to its associated AP (e.g., a management (Mgt) or control (Ctrl) frame or a data frame containing an A-Ctrl field) signaling end of the allocation.
  • the AP may reuse the remaining time for its own transmissions.
  • a non-AP STA that initiates the SP or one that has been granted allocation for the remaining time in a SP for UL or P2P traffic may send a unicast frame to its associated AP (e.g., a Mgt or Ctrl frame or a Data frame containing an A-Ctrl field) signaling end of the allocation for UL traffic.
  • the AP may switch to omni-Rx mode on receipt of this frame.
  • a STA that initiates the SP or one that has been granted allocation for the remaining time in a SP may send a unicast or Broadcast frame (e.g., a Mgt or Ctrl frame) on receipt of which other participants of the SP switch to receive non-directional PPDUs.
  • a unicast or Broadcast frame e.g., a Mgt or Ctrl frame
  • several of the current TFs defined for sub-7 GHz when sent in the 60 GHz band are interpreted to solicit SU PPDUs.
  • several of the current TFs when sent in 60 GHz band are interpreted to solicit SU PPDUs when additional info is included (e.g., presence of a Special User Info).
  • the reception of a CTS frame in response to an MU-RTS frame (or a variant of it) sent to a STA in the 60 GHz band signals the presence of that STA.
  • the STA may send an SU PPDU on receipt of a TF (e.g., an MU-RTS subvariant) which contains additional information to assist AP’s scheduling (e.g., which secondary channels are free or busy, requested airtime for UL or P2P, etc.).
  • a TF e.g., an MU-RTS subvariant
  • the frame may be sent in the 60 GHz band in an SU PPDU whose bandwidth is lower than or equal to the bandwidth of the soliciting TF.
  • several fields of current TFs when sent in 60 GHz band may be reserved since the response is an SU PPDU.
  • Such reserved fields may be the fields that are only useful for MU UL TB PPDU transmission (e.g., UL MCS, UL DCM, SS Allocation/RA-RU Information).
  • the individual functionality of most of the current TFs is preserved i.e., the Basic TF solicits UL Data, BSRP TF solicits BSR information.
  • One possible exception may be for the BQRP TF where each bit in the response signals channel busy information in units of the primary channel BW defined for the 6 GHz band (e.g., 160 MHz) instead of 20 MHz as defined in the baseline (legacy).
  • an AP may broadcast the time windows when it is able to listen in omni-mode s.t. all STAs may attempt to initiate a TXOP to the AP during this time using EDCA with the first frame being a non-directional PPDU.
  • a TBTT or a time-period in the TBTT of a 60 GHz link is divided into smaller time windows or slots. For each slot, the AP signals whether this is assigned to one or more STAs and if so, who is the expected initiator in that slot.
  • the signaling can be done in multiple steps.
  • the AP broadcasts the presence of one or more sequential broadcast TWT SPs in broadcast frames (e.g., Beacon or Probe Response) where each SP corresponds to a slot.
  • the SPs are further ordered so that low overhead signaling is possible.
  • the AP also includes a bitmap signaling whether a given SP is assigned or not.
  • AP may be ready to receive PPDUs during the unoccupied SPs provided that the frame exchange is initiated with non-directional PPDUs.
  • Each occupied slot is assigned to a STA using TWT negotiation.
  • the AP transmits a new element that signals the aggregate slot allocation information i.e., slot duration, periodicity, start time and information specific to each slot (such as whether that slot is assigned to some STA or not).
  • the AP may include an element signaling which STAs are allocated to a set of SPs and whether for each slot they are the initiator or responder. This element may be broadcast or unicast.
  • slots are assigned to a STA during TWT negotiation by including an additional field or element that signals the role of the STA in that slot as well as other information (whether UL only or P2P only or both UL and P2P if STA is the owner).
  • an AP may extend the fully scheduled mode signaling so that each STA is allocated to a slot/SP in the 60 GHz link dynamically using some frame sent in that link or in a sub-7 GHz link (i.e., cross-link signaling).
  • an efficient 60 GHz scheduling system may define a timeout after failed directional PPDU transmissions following which a STA is required to transmit PPDUs using omni-mode. On receiving Ack for such omni-mode PPDUs the STA may switch back to transmitting directional PPDU transmission.
  • FIG. 4 illustrates a flow diagram of illustrative process 400 for an efficient 60 GHz scheduling system, in accordance with one or more example embodiments of the present disclosure.
  • a device may generate a target wake time (TWT) setup frame to be sent on a first link comprising information for allocation of one or more service periods on a second link.
  • TWT target wake time
  • the device may cause to send the TWT setup frame to a responder device.
  • the device may identify a TWT response frame received from the responder device on the first link.
  • the device may allocate the one or more service periods on the second link, wherein the second link operates on a 60 GHz band.
  • FIG. 5 shows a functional diagram of an exemplary communication station 500, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1) or a user device 120 (FIG. 1) in accordance with some embodiments.
  • the communication station 500 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.
  • HDR high data rate
  • the communication station 500 may include communications circuitry 502 and a transceiver 510 for transmitting and receiving signals to and from other communication stations using one or more antennas 501.
  • the communications circuitry 502 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals.
  • the communication station 500 may also include processing circuitry 506 and memory 508 arranged to perform the operations described herein. In some embodiments, the communications circuitry 502 and the processing circuitry 506 may be configured to perform operations detailed in the above figures, diagrams, and flows.
  • the communications circuitry 502 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 502 may be arranged to transmit and receive signals.
  • the communications circuitry 502 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 506 of the communication station 500 may include one or more processors.
  • two or more antennas 501 may be coupled to the communications circuitry 502 arranged for sending and receiving signals.
  • the memory 508 may store information for configuring the processing circuitry 506 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 508 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer).
  • the memory 508 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.
  • the communication station 500 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • the communication station 500 may include one or more antennas 501.
  • the antennas 501 may include 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.
  • a single antenna with multiple apertures may be used instead of two or more antennas.
  • each aperture may be considered a separate antenna.
  • MIMO multiple-input multiple-output
  • the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.
  • the communication station 500 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the communication station 500 is illustrated as having several separate functional elements, two 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.
  • DSPs digital signal processors
  • some elements may include 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 of the communication station 500 may refer to one or more processes operating on one or more processing elements.
  • Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.
  • a computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer).
  • a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
  • the communication station 500 may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
  • FIG. 6 illustrates a block diagram of an example of a machine 600 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed.
  • 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 environments.
  • P2P peer-to-peer
  • the machine 600 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station.
  • PC personal computer
  • PDA personal digital assistant
  • STB set-top box
  • mobile telephone a wearable computer device
  • web appliance e.g., a web appliance
  • network router e.g., a router, or bridge
  • switch or bridge any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station.
  • 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), or other computer
  • 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 when operating.
  • a module includes hardware.
  • the hardware may be specifically configured to carry out a specific operation (e.g., hardwired).
  • the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating.
  • the execution units may be a member of more than one module.
  • the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.
  • the 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.
  • the machine 600 may further include a power management device 632, a graphics display device 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse).
  • the graphics display device 610, alphanumeric input device 612, and UI navigation device 614 may be a touch screen display.
  • the machine 600 may additionally include a storage device (i.e., drive unit) 616, a signal generation device 618 (e.g., a speaker), an efficient 60 GHz scheduling device 619, a network interface device/transceiver 620 coupled to antenna(s) 630, and one or more sensors 628, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor.
  • a storage device i.e., drive unit
  • a signal generation device 618 e.g., a speaker
  • an efficient 60 GHz scheduling device 619 e.g., a network interface device/transceiver 620 coupled to antenna(s) 630
  • a network interface device/transceiver 620 coupled to antenna(s) 630
  • sensors 628 such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor.
  • GPS global positioning system
  • the machine 600 may include an output controller 634, 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 with or control one or more peripheral devices (e.g., a printer, a 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 with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).
  • IR infrared
  • NFC near field communication
  • peripheral devices e.g., a printer, a card reader, etc.
  • the operations in accordance with one or more example embodiments of the present disclosure may be carried out by a baseband processor.
  • the baseband processor may be configured to generate corresponding baseband signals.
  • the baseband processor may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with the hardware processor 602 for generation and processing of the baseband signals and for controlling operations of the main memory 604, the storage device 616, and/or the efficient 60 GHz scheduling device 619.
  • the baseband processor may be provided on a single radio card, a single chip, or an integrated circuit (IC).
  • the storage device 616 may include a machine readable medium 622 on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 624 may also reside, completely or at least partially, within the main memory 604, within the static memory 606, or within the hardware processor 602 during execution thereof by the machine 600.
  • one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the storage device 616 may constitute machine-readable media.
  • the efficient 60 GHz scheduling device 619 may carry out or perform any of the operations and processes (e.g., process 400) described and shown above.
  • the efficient 60 GHz scheduling device 619 may be configured to perform and that other functions included throughout this disclosure may also be performed by the efficient 60 GHz scheduling device 619.
  • 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.
  • 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; a flash memory, etc.
  • 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.
  • a massed machine-readable medium includes a machine-readable medium with a plurality of particles having resting mass.
  • massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks.
  • semiconductor memory devices e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)
  • EPROM electrically programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • the instructions 624 may further be transmitted or received over a communications network 626 using a transmission medium via the network interface device/transceiver 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 communications 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, 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, and peer-to-peer (P2P) networks, among others.
  • the network interface device/transceiver 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/transceiver 620 may include a plurality of antennas 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
  • 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 media to facilitate communication of such software.
  • FIG. 7 is a block diagram of a radio architecture 105 A, 105B in accordance with some embodiments that may be implemented in any one of the example APs 102 and/or the example STAs 120 of FIG. 1.
  • Radio architecture 105A, 105B may include radio front-end module (FEM) circuitry 704a-b, radio IC circuitry 706a-b and baseband processing circuitry 708a-b.
  • FEM radio front-end module
  • Radio architecture 105 A, 105B 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
  • the FEM circuitry 704a-b may include a WLAN or Wi-Fi FEM circuitry 704a and a Bluetooth (BT) FEM circuitry 704b.
  • the WLAN FEM circuitry 704a may include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas 701, to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry 706a for further processing.
  • the BT FEM circuitry 704b may include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas 701, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry 706b for further processing.
  • FEM circuitry 704a may also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry 706a for wireless transmission by one or more of the antennas 701.
  • FEM circuitry 704b may also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry 706b for wireless transmission by the one or more antennas.
  • FIG. 1 In the embodiment of FIG.
  • FEM 704a and FEM 704b 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 706a-b as shown may include WLAN radio IC circuitry 706a and BT radio IC circuitry 706b.
  • the WLAN radio IC circuitry 706a may include a receive signal path which may include circuitry to down-convert WLAN RF signals received from the FEM circuitry 704a and provide baseband signals to WLAN baseband processing circuitry 708a.
  • BT radio IC circuitry 706b may in turn include a receive signal path which may include circuitry to down-convert BT RF signals received from the FEM circuitry 704b and provide baseband signals to BT baseband processing circuitry 708b.
  • WLAN radio IC circuitry 706a may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 708a and provide WLAN RF output signals to the FEM circuitry 704a for subsequent wireless transmission by the one or more antennas 701.
  • BT radio IC circuitry 706b may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 708b and provide BT RF output signals to the FEM circuitry 704b for subsequent wireless transmission by the one or more antennas 701.
  • radio IC circuitries 706a and 706b 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 WLAN 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 circuity 708a-b may include a WLAN baseband processing circuitry 708a and a BT baseband processing circuitry 708b.
  • the WLAN baseband processing circuitry 708a 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 708a.
  • Each of the WLAN baseband circuitry 708a and the BT baseband circuitry 708b 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 706a-b, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry 706a-b.
  • Each of the baseband processing circuitries 708a and 708b may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with a device for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 706a-b.
  • PHY physical layer
  • MAC medium access control layer
  • WLAN-BT coexistence circuitry 713 may include logic providing an interface between the WLAN baseband circuitry 708a and the BT baseband circuitry 708b to enable use cases requiring WLAN and BT coexistence.
  • a switch 703 may be provided between the WLAN FEM circuitry 704a and the BT FEM circuitry 704b to allow switching between the WLAN and BT radios according to application needs.
  • antennas 701 are depicted as being respectively connected to the WLAN FEM circuitry 704a and the BT FEM circuitry 704b, 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 704a or 704b.
  • the front-end module circuitry 704a-b, the radio IC circuitry 706a-b, and baseband processing circuitry 708a-b may be provided on a single radio card, such as wireless radio card 702.
  • the one or more antennas 701, the FEM circuitry 704a-b and the radio IC circuitry 706a-b may be provided on a single radio card.
  • the radio IC circuitry 706a-b and the baseband processing circuitry 708a-b may be provided on a single chip or integrated circuit (IC), such as IC 712.
  • the wireless radio card 702 may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect.
  • the radio architecture 105 A, 105B 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 105 A, 105B 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 105 A, 105B 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, 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.1 lac, 802. Hah, 802. Had, 802. Hay and/or 802.1 lax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect.
  • Radio architecture 105 A, 105B may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.
  • the radio architecture 105 A, 105B may be configured for high- efficiency Wi-Fi (HEW) communications in accordance with the IEEE 802.1 lax standard or future 802.11 standards (e.g., Wi-Fi 8, etc.).
  • the radio architecture 105 A, 105B 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 105 A, 105B 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 708b may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 8.0 or Bluetooth 6.0, or any other iteration of the Bluetooth Standard.
  • BT Bluetooth
  • the radio architecture 105 A, 105B may include other radio cards, such as a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE-Advanced or 7G communications).
  • a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE-Advanced or 7G communications).
  • the radio architecture 105 A, 105B may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or 80+80 MHz (160MHz) (with non-contiguous bandwidths).
  • a 920 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.
  • FIG. 8 illustrates WLAN FEM circuitry 704a in accordance with some embodiments. Although the example of FIG. 8 is described in conjunction with the WLAN FEM circuitry 704a, the example of FIG. 8 may be described in conjunction with the example BT FEM circuitry 704b (FIG. 7), although other circuitry configurations may also be suitable.
  • the FEM circuitry 704a may include a TX/RX switch 802 to switch between transmit mode and receive mode operation.
  • the FEM circuitry 704a may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 704a may include a low-noise amplifier (LNA) 806 to amplify received RF signals 803 and provide the amplified received RF signals 807 as an output (e.g., to the radio IC circuitry 706a-b (FIG. 7)).
  • LNA low-noise amplifier
  • the transmit signal path of the circuitry 704a may include a power amplifier (PA) to amplify input RF signals 809 (e.g., provided by the radio IC circuitry 706a- b), and one or more filters 812, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 815 for subsequent transmission (e.g., by one or more of the antennas 701 (FIG. 7)) via an example duplexer 814.
  • PA power amplifier
  • BPFs band-pass filters
  • LPFs low-pass filters
  • the FEM circuitry 704a 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 704a may include a receive signal path duplexer 804 to separate the signals from each spectrum as well as provide a separate LNA 806 for each spectrum as shown.
  • the transmit signal path of the FEM circuitry 704a may also include a power amplifier 810 and a filter 812, such as a BPF, an LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 804 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 701 (FIG. 7).
  • BT communications may utilize the 2.4 GHz signal paths and may utilize the same FEM circuitry 704a as the one used for WLAN communications.
  • FIG. 9 illustrates radio IC circuitry 706a in accordance with some embodiments.
  • the radio IC circuitry 706a is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 706a/706b (FIG. 7), although other circuitry configurations may also be suitable.
  • FIG. 9 may be described in conjunction with the example BT radio IC circuitry 706b.
  • the radio IC circuitry 706a may include a receive signal path and a transmit signal path.
  • the receive signal path of the radio IC circuitry 706a may include at least mixer circuitry 902, such as, for example, down-conversion mixer circuitry, amplifier circuitry 906 and filter circuitry 908.
  • the transmit signal path of the radio IC circuitry 706a may include at least filter circuitry 912 and mixer circuitry 914, such as, for example, up- conversion mixer circuitry.
  • Radio IC circuitry 706a may also include synthesizer circuitry 904 for synthesizing a frequency 905 for use by the mixer circuitry 902 and the mixer circuitry 914.
  • the mixer circuitry 902 and/or 914 may each, according to some embodiments, be configured to provide direct conversion functionality.
  • the latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation.
  • FIG. 9 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 914 may each include one or more mixers
  • filter circuitries 908 and/or 912 may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs.
  • mixer circuitry 902 may be configured to down-convert RF signals 807 received from the FEM circuitry 704a-b (FIG. 7) based on the synthesized frequency 905 provided by synthesizer circuitry 904.
  • the amplifier circuitry 906 may be configured to amplify the down-converted signals and the filter circuitry 908 may include an LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 907.
  • Output baseband signals 907 may be provided to the baseband processing circuitry 708a-b (FIG. 7) for further processing.
  • the output baseband signals 907 may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 902 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 914 may be configured to up-convert input baseband signals 911 based on the synthesized frequency 905 provided by the synthesizer circuitry 904 to generate RF output signals 809 for the FEM circuitry 704a-b.
  • the baseband signals 911 may be provided by the baseband processing circuitry 708a-b and may be filtered by filter circuitry 912.
  • the filter circuitry 912 may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 902 and the mixer circuitry 914 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 904.
  • the mixer circuitry 902 and the mixer circuitry 914 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 902 and the mixer circuitry 914 may be arranged for direct down-conversion and/or direct up- conversion, respectively.
  • the mixer circuitry 902 and the mixer circuitry 914 may be configured for super-heterodyne operation, although this is not a requirement.
  • Mixer circuitry 902 may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths).
  • RF input signal 807 from FIG. 9 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 905 of synthesizer 904 (FIG. 9).
  • 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 (the percentage of one period in which the LO signal is high) and/or offset (the difference between start points of the period). In some embodiments, the LO signals may have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) and quadrature phase (Q) path) may operate at an 80% duty cycle, which may result in a significant reduction is power consumption.
  • the in-phase (I) and quadrature phase (Q) path may operate at an 80% duty cycle, which may result in a significant reduction is power consumption.
  • the RF input signal 807 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-noise amplifier, such as amplifier circuitry 906 (FIG. 9) or to filter circuitry 908 (FIG. 9).
  • the output baseband signals 907 and the input baseband signals 911 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals 907 and the input baseband signals 911 may be digital baseband signals. In these alternate embodiments, 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 904 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 904 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 904 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry.
  • frequency input into synthesizer circuity 904 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 708a-b (FIG. 7) depending on the desired output frequency 905.
  • 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 example application processor 710.
  • the application processor 710 may include, or otherwise be connected to, one of the example secure signal converter 101 or the example received signal converter 103 (e.g., depending on which device the example radio architecture is implemented in).
  • synthesizer circuitry 904 may be configured to generate a carrier frequency as the output frequency 905, while in other embodiments, the output frequency 905 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 905 may be a LO frequency (fLO).
  • fLO LO frequency
  • FIG. 10 illustrates a functional block diagram of baseband processing circuitry 708a in accordance with some embodiments.
  • the baseband processing circuitry 708a is one example of circuitry that may be suitable for use as the baseband processing circuitry 708a (FIG. 7), although other circuitry configurations may also be suitable.
  • FIG. 9 may be used to implement the example BT baseband processing circuitry 708b of FIG. 7.
  • the baseband processing circuitry 708a may include a receive baseband processor (RX BBP) 1002 for processing receive baseband signals 909 provided by the radio IC circuitry 706a-b (FIG. 7) and a transmit baseband processor (TX BBP) 1004 for generating transmit baseband signals 911 for the radio IC circuitry 706a-b.
  • the baseband processing circuitry 708a may also include control logic 1006 for coordinating the operations of the baseband processing circuitry 708a.
  • the baseband processing circuitry 708a may include ADC 1010 to convert analog baseband signals 1009 received from the radio IC circuitry 706a-b to digital baseband signals for processing by the RX BBP 1002.
  • the baseband processing circuitry 708a may also include DAC 1012 to convert digital baseband signals from the TX BBP 1004 to analog baseband signals 1011.
  • the transmit baseband processor 1004 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 1002 may be configured to process received OFDM signals or OFDMA signals by performing an FFT.
  • the receive baseband processor 1002 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 701 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 701 may each include a set of phased-array antennas, although embodiments are not so limited.
  • radio architecture 105 A, 105B 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.
  • 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.
  • the word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.
  • the terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device.
  • the device may be either mobile or stationary.
  • the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed.
  • the term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal.
  • a wireless communication unit which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
  • AP access point
  • An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art.
  • An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art.
  • Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.
  • Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an onboard device, an off-board device, a hybrid device, a vehicular device, a non- vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN),
  • Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multistandard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.
  • WAP wireless application protocol
  • Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3 GPP, long term evolution (LTE), LTE advanced, enhanced data rates for G
  • Example 1 may include a device comprising processing circuitry coupled to storage, the processing circuitry configured to: generate a target wake time (TWT) setup frame to be sent on a first link comprising information for allocation of one or more service periods on a second link; cause to send the TWT setup frame to a responder device; identify a TWT response frame received from the responder device on the first link; and allocate the one or more service periods on the second link, wherein the second link operates on a 60 GHz band.
  • TWT target wake time
  • Example 2 may include the device of example 1 and/or some other example herein, wherein the respondent device may be an AP or non-AP device.
  • Example 3 may include the device of example 1 and/or some other example herein, wherein the first link operates on a sub 7 GHz band.
  • Example 4 may include the device of example 1 and/or some other example herein, wherein a reserved field of a TWT element may be used to signal the presence of an additional field containing 60 GHz link specific information.
  • Example 5 may include the device of example 1 and/or some other example herein, wherein the TWT set up frame may be a TWT request frame.
  • Example 6 may include the device of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to cause to send a multiple user request to send (MU-RTS) triggered TXOP sharing (TXS) frame following the end of a last downlink PPDU.
  • MU-RTS multiple user request to send
  • TXS TXOP sharing
  • Example 7 may include the device of example 6 and/or some other example herein, wherein the MU-RTS TXS frame returns a remaining time in an SP or TXOP to a responder device.
  • Example 8 may include the device of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to cause to switch to receiving only non-directional initial physical layer (PHY) convergence protocol data unit (PPDU) after returning any unused time and receiving no directional PPDUs within a specific time.
  • PHY physical layer
  • PPDU convergence protocol data unit
  • Example 9 may include the device of example 1 and/or some other example herein, wherein a trigger frame sent in a 60 GHz band may be interpreted to solicit from the receiving device a single user physical layer (PHY) convergence protocol data unit (PPDU).
  • PHY physical layer
  • Example 10 may include a non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: generating a target wake time (TWT) setup frame to be sent on a first link comprising information for allocation of one or more service periods on a second link; causing to send the TWT setup frame to a responder device; identifying a TWT response frame received from the responder device on the first link; and allocating the one or more service periods on the second link, wherein the second link operates on a 60 GHz band.
  • TWT target wake time
  • Example 11 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the respondent device may be an AP or non-AP device.
  • Example 12 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the first link operates on a sub 7 GHz band.
  • Example 13 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein a reserved field of a TWT element may be used to signal the presence of an additional field containing 60 GHz link specific information.
  • Example 14 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the TWT set up frame may be a TWT request frame.
  • Example 15 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise causing to send a multiple user request to send (MU-RTS) triggered TXOP sharing (TXS) frame following the end of a last downlink PPDU.
  • MU-RTS multiple user request to send
  • TXS TXOP sharing
  • Example 16 may include the non-transitory computer-readable medium of example 15 and/or some other example herein, wherein the MU-RTS TXS frame returns a remaining time in an SP or TXOP to a responder device.
  • Example 17 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise causing to switch to receiving only non-directional initial physical layer (PHY) convergence protocol data unit (PPDU) after returning any unused time and receiving no directional PPDUs within a specific time.
  • PHY physical layer
  • PPDU convergence protocol data unit
  • Example 18 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein a trigger frame sent in a 60 GHz band may be interpreted to solicit from the receiving device a single user physical layer (PHY) convergence protocol data unit (PPDU).
  • PHY physical layer
  • Example 19 may include a method comprising: generating, by one or more processors, a target wake time (TWT) setup frame to be sent on a first link comprising information for allocation of one or more service periods on a second link; causing to send the TWT setup frame to a responder device; identifying a TWT response frame received from the responder device on the first link; and allocating the one or more service periods on the second link, wherein the second link operates on a 60 GHz band.
  • TWT target wake time
  • Example 20 may include the method of example 18 and/or some other example herein, wherein the respondent device may be an AP or non-AP device.
  • Example 21 may include the method of example 18 and/or some other example herein, wherein the first link operates on a sub 7 GHz band.
  • Example 22 may include the method of example 18 and/or some other example herein, wherein a reserved field of a TWT element may be used to signal the presence of an additional field containing 60 GHz link specific information.
  • Example 23 may include the method of example 18 and/or some other example herein, wherein the TWT set up frame may be a TWT request frame.
  • Example 24 may include the method of example 18 and/or some other example herein, further comprising causing to send a multiple user request to send (MU-RTS) triggered TXOP sharing (TXS) frame following the end of a last downlink PPDU.
  • MU-RTS multiple user request to send
  • TXS TXOP sharing
  • Example 25 may include the method of example 23 and/or some other example herein, wherein the MU-RTS TXS frame returns a remaining time in an SP or TXOP to a responder device.
  • Example 26 may include the method of example 18 and/or some other example herein, further comprising causing to switch to receiving only non-directional intial physical layer (PHY) convergence protocol data unit (PPDU) after returning any unused time and receiving no directional PPDUs within a specific time.
  • PHY physical layer
  • PPDU convergence protocol data unit
  • Example 27 may include the method of example 18 and/or some other example herein, wherein a trigger frame sent in a 60 GHz band may be interpreted to solicit from the receiving device a single user physical layer (PHY) convergence protocol data unit (PPDU).
  • PHY physical layer
  • Example 28 may include an apparatus comprising means for: generating a target wake time (TWT) setup frame to be sent on a first link comprising information for allocation of one or more service periods on a second link; causing to send the TWT setup frame to a responder device; identifying a TWT response frame received from the responder device on the first link; and allocating the one or more service periods on the second link, wherein the second link operates on a 60 GHz band.
  • TWT target wake time
  • Example 29 may include the apparatus of example 27 and/or some other example herein, wherein the respondent device may be an AP or non-AP device.
  • Example 30 may include the apparatus of example 27 and/or some other example herein, wherein the first link operates on a sub 7 GHz band.
  • Example 31 may include the apparatus of example 27 and/or some other example herein, wherein a reserved field of a TWT element may be used to signal the presence of an additional field containing 60 GHz link specific information.
  • Example 32 may include the apparatus of example 27 and/or some other example herein, wherein the TWT set up frame may be a TWT request frame.
  • Example 33 may include the apparatus of example 27 and/or some other example herein, further comprising causing to send a multiple user request to send (MU-RTS) triggered TXOP sharing (TXS) frame following the end of a last downlink PPDU.
  • MU-RTS multiple user request to send
  • TXS TXOP sharing
  • Example 34 may include the apparatus of example 32 and/or some other example herein, wherein the MU-RTS TXS frame returns a remaining time in an SP or TXOP to a responder device.
  • Example 35 may include the apparatus of example 27 and/or some other example herein, further comprising causing to switch to receiving only non-directional intial physical layer (PHY) convergence protocol data unit (PPDU) after returning any unused time and receiving no directional PPDUs within a specific time.
  • Example 36 may include the apparatus of example 27 and/or some other example herein, wherein a trigger frame sent in a 60 GHz band may be interpreted to solicit from the receiving device a single user physical layer (PHY) convergence protocol data unit (PPDU).
  • PHY physical layer
  • Example 37 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process described herein.
  • Example 38 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process described herein.
  • Example 39 may include a method, technique, or process as described in or related to any of examples 1-36, or portions or parts thereof.
  • Example 40 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-36, or portions thereof.
  • Example 41 may include a method of communicating in a wireless network as shown and described herein.
  • Example 42 may include a system for providing wireless communication as shown and described herein.
  • Example 43 may include a device for providing wireless communication as shown and described herein.
  • Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well.
  • the dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims.
  • These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks.
  • These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks.
  • certain implementations may provide for a computer program product, comprising a computer- readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.
  • blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.
  • conditional language such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

Landscapes

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

Abstract

La présente divulgation concerne des systèmes, des procédés et des dispositifs associés à une planification efficace pour 60 GHz. Un dispositif peut générer une trame de configuration de temps de réveil cible (TWT) à envoyer sur une première liaison comprenant des informations concernant l'attribution d'une ou plusieurs périodes de service sur une seconde liaison. Le dispositif peut provoquer l'envoi de la trame de configuration de TWT à un dispositif répondeur. Le dispositif peut identifier une trame de réponse de TWT reçue du dispositif répondeur sur la première liaison. Le dispositif peut attribuer la ou les périodes de service sur la seconde liaison, la seconde liaison fonctionnant sur une bande de 60 GHz.
PCT/US2022/035372 2022-06-28 2022-06-28 Planification efficace dans une bande de 60 ghz Ceased WO2024005794A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2022/035372 WO2024005794A1 (fr) 2022-06-28 2022-06-28 Planification efficace dans une bande de 60 ghz

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2022/035372 WO2024005794A1 (fr) 2022-06-28 2022-06-28 Planification efficace dans une bande de 60 ghz

Publications (1)

Publication Number Publication Date
WO2024005794A1 true WO2024005794A1 (fr) 2024-01-04

Family

ID=89380973

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/035372 Ceased WO2024005794A1 (fr) 2022-06-28 2022-06-28 Planification efficace dans une bande de 60 ghz

Country Status (1)

Country Link
WO (1) WO2024005794A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130003662A1 (en) * 2011-06-29 2013-01-03 Broadcom Corporation Method and system for reliable service period allocation in 60 GHz MAC
US20180115950A1 (en) * 2016-10-24 2018-04-26 Qualcomm Incorporated Optimizing target wake-up time (twt) operation
US20180132178A1 (en) * 2016-11-08 2018-05-10 Lg Electronics Inc. Method for managing power of wireless terminal in wireless local area network and wireless terminal using the same
US20220141680A1 (en) * 2020-10-30 2022-05-05 Samsung Electronics Co., Ltd. Electronic device performing rescheduling over wireless channel and method for controlling same

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130003662A1 (en) * 2011-06-29 2013-01-03 Broadcom Corporation Method and system for reliable service period allocation in 60 GHz MAC
US20180115950A1 (en) * 2016-10-24 2018-04-26 Qualcomm Incorporated Optimizing target wake-up time (twt) operation
US20180132178A1 (en) * 2016-11-08 2018-05-10 Lg Electronics Inc. Method for managing power of wireless terminal in wireless local area network and wireless terminal using the same
US20220141680A1 (en) * 2020-10-30 2022-05-05 Samsung Electronics Co., Ltd. Electronic device performing rescheduling over wireless channel and method for controlling same

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
DONG WEI (NXP): "TWT for WLAN Sensing", IEEE DRAFT; 11-21-2004-00-00BF-TWT-FOR-WLAN-SENSING, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11bf, no. 0, 13 December 2021 (2021-12-13), Piscataway, NJ USA, pages 1 - 14, XP068187388 *

Similar Documents

Publication Publication Date Title
US20240129977A1 (en) Single-radio multi-channel medium access
US20210084711A1 (en) Multi-link operation for a single radio multi-link device
US10917770B2 (en) Enhanced negotiation protocol for triggered peer to peer communications
EP4496419A1 (fr) Mécanisme pour gérer une terminaison d'opportunité de transmission dans un accès à un canal non primaire
US20230133701A1 (en) Target wake for multi-link operation restrictions
US12302428B2 (en) Ultra-low latency medium access control design for 802.11
US12363778B2 (en) Mechanisms to reduce the worst-case latency for ultra-low latency applications
US20230319871A1 (en) Low latency traffic and overlapping basic service set with preemption mechanism
US20230127299A1 (en) Enhanced signaling of dynamic quality of service over wi-fi
EP4454403A1 (fr) Indication d'unités pouvant être mises en tampon (bu) à adresse de groupe dans une carte d'indication de trafic (tim) pour un fonctionnement à liaisons multiples
US12262304B2 (en) Long range beacon for power difference between 5 and 6 GHz
US20240064805A1 (en) Transmit opportunity preemption for low latency application for registered or unregistered low latency devices
US20250193931A1 (en) Enhanced wi-fi ultra-low latency operations
US11812410B2 (en) Efficient poll response frame
US12464140B2 (en) Enhanced Wi-Fi sensing measurement setup and sensing trigger frame for responder-to-responder sensing
US20250351211A1 (en) Signaling for multi-ap operations
EP4226735A1 (fr) Élément silencieux pour fonctionnement à liaisons multiples
US20250063612A1 (en) Handling pre-association exchanges with extended long range operation
US20240292455A1 (en) Enhanced non-primary channel access, dynamic sub-band operation, and non-dynamic sub-band operation with per-bandwidth virtual sensing
US20230246757A1 (en) Enhanced scheduling of asynchronous multi-access point transmissions on different frequency segments in wireless communications
US20240284454A1 (en) Trigger for uplink trigger based duplicate physical layer convergence protocol data unit
US20240008087A1 (en) Multi-link device enhanced multi-link single-radio operation with a legacy station device support
EP4387300A1 (fr) Indications de capacité pour terminaison précoce d'unité de données de protocole de convergence de couche physique (phy) (ppdu)
US20250240832A1 (en) Host identity protocol (hip) enhanced distributed channel access (edca) - access point (ap) access compensation
US20250358848A1 (en) A system for accessing multiple primary channels in a wireless medium

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

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

Country of ref document: EP

Kind code of ref document: A1