WO2019132868A1

WO2019132868A1 - Hierarchic resource allocation

Info

Publication number: WO2019132868A1
Application number: PCT/US2017/068465
Authority: WO
Inventors: Yaron Alpert; Laurent Cariou; Ehud Reshef
Original assignee: Intel IP Corporation
Priority date: 2017-12-27
Filing date: 2017-12-27
Publication date: 2019-07-04
Also published as: DE112017008318T5

Abstract

This disclosure describes systems, methods, and devices related to hierarchic resource allocation. A device may identify a first resource allocation request received from a first entity of a hierarchic network. The device may identify a second resource allocation request received from a second entity of the hierarchic network. The device may determine a hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request. The device may cause to send the hierarchic resource allocation request.

Description

HIERARCHIC RESOURCE ALLOCATION

TECHNICAL FIELD

[0001] This disclosure generally relates to systems and methods for wireless communications and, more particularly, to resource allocation among wireless devices.

BACKGROUND

[0002] 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.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] FIG. 1 depicts a network diagram illustrating an example network environment of hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure.

[0004] FIG. 2 depicts a network diagram illustrating a hierarchic network, in accordance with one or more example embodiments of the present disclosure.

[0005] FIGs. 3A-3B depict illustrative flow diagrams for hierarchic resource allocation request messaging, in accordance with one or more example embodiments of the present disclosure.

[0006] FIGs. 4A-4B depict illustrative flow diagrams for hierarchic availability signaling, in accordance with one or more example embodiments of the present disclosure.

[0007] FIGs. 5A-5B depict illustrative flow diagrams for hierarchic physical layer (PHY) collaborative network sounding, in accordance with one or more example embodiments of the present disclosure.

[0008] FIGs. 6A-6B depict illustrative flow diagrams for downlink (DL) hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure.

[0009] FIGs. 7A-7B depict illustrative flow diagrams for uplink (UL) hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure.

[0010] FIG. 8 depicts a flow diagram of an illustrative process for hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure.

[0011] FIG. 9 depicts a flow diagram of an illustrative process for hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure. [0012] FIG. 10 illustrates a functional diagram of an example communication station that may be suitable for use as a user device, in accordance with one or more example embodiments of the present disclosure.

[0013] FIG. 11 is 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.

DETAILED DESCRIPTION

[0014] Example embodiments described herein provide certain systems, methods, and devices for resource allocation, including, but not limited to, for the IEEE 802.11 family of standards.

[0015] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0016] In Communication Collaborative Networks (CCNs), specifically Wireless Collaborative Networks (WCNs), distributing available wireless resources to entities (e.g., a station (STA), an access point (AP), a range extender (RE), or other entities) based on the entities’ Quality of Service (QoS) requirements, underlying channel conditions, and network topology is a challenge. Particularly, an AP in a WCN may currently only control traffic or allocate resources to/from STAs or REs that the AP directly serves to (e.g., serving entities). The AP is unable to control traffic or allocate resources to/from STAs or REs that are not being served by (or are unconnected to) the AP. Managing resources for unconnected entities in WCNs, specifically in massive multiple input, multiple output (MIMO) networks, would enable resource management and allocation beyond the serving entities that are connected to the AP, increase network capacity, and improve QoS.

[0017] IEEE 802.11 ax has introduced a mechanism for a point to multi-point uplink resource allocation based on trigger frame/ A-control signaling. Particularly, this mechanism enables an AP to, for example, solicit simultaneous uplink transmissions from multiple STAs that the AP is serving. However, this AP is unable to solicit uplink transmissions from WLAN entities (e.g., STAs, REs, etc.) that are not being served by this AP, for example, in a WCN or a massive MIMO network. [0018] Example embodiments of the present disclosure relate to systems, methods, and devices for hierarchic resource allocation.

[0019] An over the air (OTA) hierarchic resource allocation mechanism that provides autonomous, decentralized (or centralized) scheduling offers a way to manage resources for both serving entities and unconnected entities in a WCN. Managing resources for the serving entities and unconnected entities in the WCN enables increased network resource utilization, improved end-point performance by entities (e.g., power consumption), and improved end-to- end QoS.

[0020] In one embodiment, a hierarchic network (e.g., a WCN) may comprise (1) a central coordinator (e.g., a central/distributed resource allocation function at an AP), (2) one or more level 1 entities (e.g., STAs) that are served by the central coordinator, (3) one or more level 1 aggregation entities (e.g., REs) that are served by the central coordinator and serve lower hierarchical entities, and (4) level 2 entities (e.g., STAs) that are served by a level 1 aggregation entity of the one or more level 1 aggregation entities. The hierarchic network may comprise additional entities or aggregation entities at lower levels (e.g., level 2 aggregation entities, level 3 entities, etc.). A hierarchic resource allocation mechanism that facilitates resource allocation in the hierarchic network may comprise (a) data collection and (b) resource allocation by the central coordinator. Data collected in the data collection may be, for example, resource allocation requests by entities in the hierarchic network, availability of the entities in the hierarchic network, etc. Based on the data collection, resources may be allocated (e.g., by the central coordinator) to all of the entities of the hierarchic network.

[0021] In one embodiment, the data collection may comprise: (1) hierarchic resource allocation request messaging, (2) hierarchic availability signaling, and (3) hierarchic physical layer (PHY) collaborative network sounding.

[0022] In one embodiment, hierarchic resource allocation request messaging may enable the central coordinator to determine resource allocation for all entities in the hierarchic network (instead of just entities that are served by the central coordinator). Particularly, an aggregation entity (e.g., of the one or more level 1 aggregation entities) may determine a hierarchic resource allocation request based on resource allocation requests that are received from entities that the aggregation entity serves (e.g., one or more of the level 2 entities). In an aggregated (or pass through) mode, the aggregation entity determines the hierarchic resource allocation requests by (a) aggregating the resource allocation requests (e.g., identifying and encapsulating) and (b) causing to send the hierarchic allocation requests to the central coordinator (or to a higher level aggregation entity if the aggregation entity is not served by the central coordinator). In an accumulated mode, the aggregation entity determines the hierarchic resource allocation requests by (a) determining a total amount of resource(s) that are requested in the resource allocation requests (for each resource) and (b) causing to send the determined hierarchic resource allocation requests (that include the total amount of requested resource(s)) to the central coordinator (or to the higher level aggregation entity if the aggregation entity is not served by the central coordinator). Both the aggregated mode and the accumulated mode enable resource allocation requests from lower level entities to propagate through the hierarchic network to reach the central coordinator. The central coordinator may make decisions (or schedule) hierarchic resource allocation (e.g., spatial streams, timing, etc.) and transmission format (e.g., orthogonal frequency division multiplexing (OFDM) values, MIMO, modulation and coding scheme (MCS) values, orthogonal frequency division multiple access (OFDMA) values, MIMO and OFDMA combination values, etc.) for all the entities in the hierarchic network.

[0023] In one embodiment, the hierarchic resource allocation request may be an extension or modification of the Buffer Status Report (BSR) mechanism defined by 802.1 lax. Broadly, BSR allows an AP to (1) know an uplink (UL) buffer status of each STA in STAs that are connected to the AP and (2) allocate UL resources for the connected STAs. For example, the hierarchic resource allocation requests may reuse the 802.11 ax resource allocation request method (e.g., BSR), while adding unique hierarchic entity identifiers or aggregate entity identifiers. The hierarchic allocation requests may additionally include relevant scheduling information, transmission opportunities (TxOPs), and PHY protocol data unit (PPDU) restriction information.

[0024] In one embodiment, hierarchic availability signaling enables entities of a hierarchic network to define and negotiate synchronized availability periods. Particularly, service periods across Basic Service Sets (BSSs) and throughout the hierarchic network may be defined so that availability of entities for, for example, TxOPs, in the hierarchic network is known by the central coordinator. Availability negotiation may be propagated through the hierarchic network. Further, the availability negotiation may occur in either an aggregated (or pass through) mode or an accumulated mode. In the aggregated (or pass-through) mode, intermediate aggregation entities (e.g., level 1 aggregation entities) identify availability windows of entities that the aggregation serves and causes to send the availability windows to the central coordinator (or to a higher level aggregation entity if the aggregation entity is not served by the central coordinator). The central coordinator, thus, may receive availability windows of every entity in the hierarchic network. Based on the availability windows, the central coordinator may allocate long or short term availability periods to the entities. In the accumulated mode, an aggregation entity (a) receives availability periods from entities that the aggregation entity is serving, (b) determines an accumulated availability window (that is based on the availability periods of the entities that are served), and (c) negotiates with a higher level hierarchic entity (e.g., the central coordinator or to a higher level aggregation entity if the aggregation entity is not served by the central coordinator) based on the determined accumulated availability window. Further, the aggregation entity may act as an availability coordinator that allocates long or short term availability periods to the entities that the aggregation entity serves.

[0025] In one embodiment, hierarchic availability signaling may be facilitated by extending or modifying IEEE 802.11 availability request methods (e.g., target wake time (TWT)) by, for example, adding a hierarchic entity identifier or an aggregate entity identifier to availability requests.

[0026] In one embodiment, hierarchic PHY collaborative network sounding enables entities in a hierarchic network to perform sounding reporting (e.g., channel quality indicator (CQI), beamforming (BF), etc.) to prepare for collaborative MIMO or massive MIMO transmission/reception. A central coordinator (or an aggregation entity) may use a reference sounding element to perform, for example, channel estimation. In an example, in order to conduct collaborative simultaneous MIMO transmission/reception, the central coordinator (or the aggregation entity) may trigger a sounding sequence to an entity that the central coordinator serves (e.g., a STA), the STA may process the sounding sequence by performing channel estimation, and the STA may then send feedback to the central coordinator.

[0027] In one embodiment, subsequent to data collection of the hierarchic network being performed, a central coordinator may assign ownership of TxOPs for a hierarchic service period to entities (that are served by the central coordinator, for example, aggregation entities). The central coordinator may cause to send a triggered hierarchic resource allocation that propagates throughout the hierarchic network and meets transmission constraints of the hierarchic network (based on the data collection). The triggered hierarchic resource allocation coordinates immediate simultaneous transmission/reception from/to the aggregation entities. Further, the aggregation entities may use the triggered hierarchic resource allocation to further assign ownership of portions of a TxOP the entities that the aggregation entities serve (e.g., lower hierarchy entities or aggregation entities). For example, the central coordinator may schedule uplink and downlink periods for each entity in the hierarchic network. [0028] In one embodiment, data collection and hierarchic resource allocation in a hierarchic network may occur in a non-simultaneous (serial) method. In such embodiment, the hierarchic network comprises entities or channel conditions that prevent a central coordinator (or aggregation entities) from for example, simultaneously sending or identifying frames from served entities. In another embodiment, the data collection and the hierarchic resource allocation may occur in a simultaneous method. In such embodiment, the hierarchic network comprises entities or channel conditions that allow the central coordinator (or the aggregation entities) to, for example, simultaneously send the frames to or identify the frames from served entities. Particularly, in the hierarchic network that facilitates the simultaneous method, collisions among transmissions of the entities do not (or are unlikely to) occur.

[0029] The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures.

[0030] FIG. 1 is a network diagram illustrating an example network environment of an enhanced location service negotiation, according to some example embodiments of the present disclosure. Wireless network 100 may include one or more user devices 120 (e.g., user devices 122, 124, 126) and one or more AP(s) 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.

[0031] In some embodiments, the user devices 120 and the one or more APs 102 may include one or more computer systems similar to that of the functional diagram of FIG. 10 and/or the example machine/system of FIG. 11.

[0032] One or more illustrative user device(s) 120 and/or AP 102 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a STA. A 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. The one or more illustrative user device(s) 120 and/or AP 102 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP). The user device(s) 120 (e.g., 122, 124, 126) and/or AP 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, for example, a static, device. For example, user device(s) 120 and/or AP 102 may include, a user equipment (UE), a STA, an 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 ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) 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 device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a“carry small live large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an“origami” device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set- top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list.

[0033] As used herein, the term“Internet of Things (IoT) 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 may transmit information to one or more other devices over a wired or wireless connection. An IoT 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. An IoT device may have a particular set of attributes (e.g., a device state or status, such as whether the IoT 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 light-emitting function, a sound-emitting function, etc.) that may be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT 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 IoT network. IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT 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.).

[0034] The user device(s) 120 and/or AP 102 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3 GPP standards.

[0035] Any of the user device(s) 120 (e.g., user devices 122, 124, 126), and AP 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 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). In addition, 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, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.

[0036] Any of the user device(s) 120 (e.g., user devices 122, 124, 126) and AP 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 122, 124, 126), and AP 102. Some non-limiting examples of 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, 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 102.

[0037] Any of the user device(s) 120 (e.g., user devices 122, 124, 126) and AP 102 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 122, 124, 126), and AP 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 122, 124, 126), and AP 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 122, 124, 126), and AP 102 may be configured to perform any given directional reception from one or more defined receive sectors.

[0038] UL and/or DL MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming. In some embodiments, in performing a given MIMO transmission, user devices 120 and/or AP 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.

[0039] Any of the user devices 120 (e.g., user devices 122, 124, 126) and AP 102 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 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 IEEE 802.11 standards and/or the Wi-Fi Alliance standards. In certain example embodiments, the radio component, in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g. 802.l lb, 802.llg, 802.11h, 802.l lax), 5 GHz channels (e.g. 802.11h, 802.l lac, 802.l lax), 60 GHZ channels (e.g. 802.llad, 802.llay, etc.), 800 MHz channels (e.g., 802.llah), 28 GHz channels, or 40 GHz channels. It should be understood that this list of communication channels in accordance with certain 802.11 standards is only a partial list and that other 802.11 standards may be used (e.g., Next Generation Wi-Fi, or other standards). In some embodiments, 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.llaf, 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.

[0040] When an AP (e.g., AP 102) establishes communication with one or more user devices 120 (e.g., user devices 122, 124, and/or 126), the AP 102 may communicate in a downlink direction and the user devices 120 may communicate with the AP 102 in an uplink direction by sending data frames in either direction. The user devices 120 may also communicate peer-to-peer or directly with each other with or without the AP 102.

[0041] In one embodiment, and with reference to FIG. 1, a user device 120 may perform hierarchic resource allocation with one or more AP(s) 102. User device 120 may be considered as an initiating device, also referred to as a station device (STA), and at least one of the AP(s) 102 may be considered as a responding device.

[0042] With reference to FIG. 1, the wireless network 100 may comprise a hierarchic network, where the one or more user devices 120 may comprise an aggregation entity (e.g., an RE) and entities that are served by a central coordinator (e.g., the one or more AP(s) 102). In another embodiment, the one or more user devices 120 may comprise entities in a hierarchic network that are served by an aggregation entity (e.g., the one or more AP(s) 102). The wireless network 100 may implement an OTA hierarchic resource allocation mechanism that provides autonomous, decentralized (or centralized) scheduling to the one or more user devices 120 and the one or more AP(s) 102. The hierarchic resource allocation mechanism facilitates resource allocation in the wireless network 100.

[0043] The hierarchic resource allocation mechanism that facilitates resource allocation in the hierarchic network may comprise (a) data collection and (b) resource allocation by the central coordinator. Data collected in the data collection may be, for example, resource allocation requests by entities in the hierarchic network, availability of the entities in the hierarchic network, etc. The data collection may be facilitated by the one or more user devices 120 causing to send e.g., a hierarchic resource request 140 (e.g., a frame) to the one or more AP(s) 102. The AP may serve the one or more devices 120 as a central coordinator or an aggregation entity. Based on the data collection, resources (e.g., a resource unit) may be allocated by the one or more AP(s) 102 to the one or more devices 120. The resources may be allocated by the one or more APs 102 causing to send, for example, a hierarchic resource response 150 (e.g., a frame) that allocates a resource in the wireless network 100.

[0044] FIG. 2 depicts a network diagram illustrating a hierarchic network, in accordance with one or more example embodiments of the present disclosure.

[0045] The example of FIG. 2 is an example hierarchic network 200 (e.g., a WCN) that comprises entities that implement a hierarchic resource allocation mechanism to facilitate hierarchic resource allocation. The entities comprise: (1) a central coordinator 202 (e.g., an AP that comprises a central/distributed resource allocation); (2) one or more level 1 entities 212 (e.g., STAs) that are served by the central coordinator 202; (3) one or more level 1 aggregation entities 210 (e.g., REs) that are served by the central coordinator 202 and serve lower hierarchical entities, (4) one or more level 2 entities 222 (e.g., STAs) that are served by a level 1 aggregation entity of the one or more level 1 aggregation entities 210; (5) one or more level 2 aggregation entities 220 that are served by the one or more level 1 aggregation entities 210 and serve lower hierarchical entities; and (6) one or more level 3 aggregation entities and one or more level 3 entities 230 that are served by the one or more level 2 aggregation entities 220. It is understood that the hierarchic network 200 may comprise additional entities or aggregation entities at lower levels (e.g., level 4 aggregation entities, level 4 entities, etc.).

[0046] The hierarchic resource allocation mechanism that facilitates resource allocation in the hierarchic network 200 may comprise (a) data collection and (b) resource allocation by the central coordinator 202. Data collected in the data collection may be, for example, resource allocation requests by entities in the hierarchic network 200, availability of the entities in the hierarchic network 200, etc. Based on the data collection, resources may be allocated (by, for example, the central coordinator 202) to all of the entities of the hierarchic network 200.

[0047] In one embodiment, the data collection may comprise: (1) hierarchic resource allocation request messaging, (2) hierarchic availability signaling, and (3) hierarchic physical layer (PHY) collaborative network sounding.

[0048] In one embodiment, hierarchic resource allocation request messaging enables the central coordinator 202 to determine resource allocation for all entities in the hierarchic network 200 (instead of just entities that are served by the central coordinator 202). Particularly, an aggregation entity (e.g., of the one or more level 1 aggregation entities 210, the one or more level 2 aggregation entities 220, etc.) may determine a hierarchic resource allocation request based on resource allocation requests that are received from entities that the aggregation entity serves (e.g., the one or more of the level 1 entities 212, the one or more of the level 2 entities 222, etc.)· In an aggregated (or pass-through) mode, the aggregation entity determines the hierarchic resource allocation requests by: (a) aggregating the resource allocation requests (e.g., identifying and encapsulating) and (b) causing to send the hierarchic allocation requests to the central coordinator 202 (or to a higher level aggregation entity if the aggregation entity is not served by the central coordinator 202). In an accumulated mode, the aggregation entity determines the hierarchic resource allocation requests by (a) determining a total amount of resource(s) that are requested in the resource allocation requests (for each resource); and (b) causing to send the determined hierarchic resource allocation requests (that include the total amount of requested resource(s)) to the central coordinator 202 (or to the higher level aggregation entity if the aggregation entity is not served by the central coordinator 202). Both the aggregated mode and the accumulated mode enable resource allocation requests from lower level entities (e.g., the one or more of the level 1 entities 212, the one or more of the level 2 entities 222, etc.) to propagate through the hierarchic network 200 to reach the central coordinator 202. The central coordinator 202 may make decisions (or schedule) hierarchic resource allocation (e.g., spatial streams, timing, etc.) and transmission format (e.g., OFDM values, MIMO values, MCS values, OFDMA values, MIMO and OFDMA combination values, etc.) for all the entities in the hierarchic network 200.

[0049] In one embodiment, the hierarchic resource allocation request may be an extension or modification of the BSR mechanism defined by 802.1 lax. Broadly, BSR allows an AP to: (1) know an UL buffer status of each STA in STAs that are connected to the AP; and (2) allocate UL resources for the connected STAs. For example, the hierarchic resource allocation requests may reuse the 802.1 lax resource allocation request method (e.g., BSR), while adding unique hierarchic entity identifiers or aggregate entity identifiers. The hierarchic allocation requests may additionally include relevant scheduling information, TxOPs, and PPDU restriction information.

[0050] In one embodiment, hierarchic availability signaling enables entities of the hierarchic network 200 to define and negotiate synchronized availability periods. Particularly, service periods across BSSs and throughout the hierarchic network 200 may be defined so that availability of entities for, for example, TxOPs, in the hierarchic network 200 is known by the central coordinator 202. Availability negotiation may be propagated through the hierarchic network 200. Further, the availability negotiation may occur in either an aggregated (or pass through) mode or an accumulated mode. In the aggregated (or pass-through) mode, intermediate aggregation entities identify availability windows of entities that the aggregation serves and causes to send the availability windows to the central coordinator 202 (or to a higher level aggregation entity if the aggregation entity is not served by the central coordinator 202). The central coordinator 202, thus, may receive availability windows of every entity in the hierarchic network 200. Based on the availability windows, the central coordinator 202 may allocate long or short term availability periods to the entities. In the accumulated mode, an aggregation entity: (a) receives availability periods from entities that the aggregation entity is serving; (b) determines an accumulated availability window (that is based on the availability periods of the entities that are served); and (c) negotiates with a higher level hierarchic entity (e.g., the central coordinator 202 or to a higher level aggregation entity if the aggregation entity is not served by the central coordinator 202) based on the determined accumulated availability window. Further, the aggregation entity may act as an availability coordinator that allocates long or short term availability periods to the entities that the aggregation entity serves.

[0051] In one embodiment, hierarchic availability signaling may facilitated by extending or modifying IEEE 802.11 availability request methods (e.g., TWT) by, for example, adding a hierarchic entity identifier or an aggregate entity identifier to availability requests.

[0052] In one embodiment, hierarchic PHY collaborative network sounding enables entities in the hierarchic network 200 to perform sounding reporting (e.g., CQI, BF, etc.) to prepare for collaborative MIMO or massive MIMO transmission/reception. The central coordinator 202 (or an aggregation entity) may use a reference sounding element to perform, for example, channel estimation. In an example, in order to conduct collaborative simultaneous MIMO transmission/reception, the central coordinator 202 (or the aggregation entity) may trigger a sounding sequence to an entity that the central coordinator 202 serves (e.g., an entity of the level 1 entities 212), the entity of the level 1 entities 212 may process the sounding sequence by performing channel estimation, and the entity of the level 1 entities 212 may then send feedback to the central coordinator 202.

[0053] In one embodiment, subsequent to data collection of the hierarchic network 200 being performed, the central coordinator 202 may assign ownership of TxOPs for a hierarchic service period to entities (that are served by the central coordinator 202, e.g., aggregation entities). The central coordinator 202 may cause to send a triggered hierarchic resource allocation that propagates throughout the hierarchic network 200 and meets transmission constraints of the hierarchic network 200 (based on the data collection). The triggered hierarchic resource allocation coordinates immediate simultaneous transmission/reception from/to the aggregation entities. Further, the aggregation entities may use the triggered hierarchic resource allocation to further assign ownership of portions of a TxOP the entities that the aggregation entities serve (e.g., lower hierarchy entities or aggregation entities). For example, the central coordinator 202 may schedule uplink and downlink periods for each entity in the hierarchic network.

[0054] In one embodiment, data collection and hierarchic resource allocation in the hierarchic network 200 may occur in a non-simultaneous (serial) method. In such embodiment, the hierarchic network 200 comprises entities or channel conditions that prevent the central coordinator 202 (or aggregation entities) from e.g., simultaneously sending or identifying frames from served entities. In another embodiment, the data collection and the hierarchic resource allocation may occur in a simultaneous method. In such embodiment, the hierarchic network 200 comprises entities or channel conditions that allow the central coordinator 202 (or the aggregation entities) to, for example, simultaneously send the frames to or identify the frames from served entities. Particularly, in the hierarchic network 200 that facilitates the simultaneous method, collisions among transmissions of the entities do not (or are unlikely to) occur. For example, the one or more level 1 aggregation entities 210 may be coordinated, and, thus, capable of causing to send coordinated frames, messages, transmissions, etc.

[0055] It is understood that the above is only an example meant for illustrative purposes.

[0056] FIGs. 3A-3B depict illustrative flow diagrams for hierarchic resource allocation request messaging, in accordance with one or more example embodiments of the present disclosure.

[0057] The example of FIG. 3A is an example non-simultaneous (serial) hierarchic resource allocation request protocol 300 for a hierarchic resource allocation mechanism among: a central coordinator 302, a first level 1 aggregation entity 304 that is served by the central coordinator 302, first level 1 entities 306 that are served by the level 1 aggregation entity 304, a second level 1 aggregation entity 308 that is served by the central coordinator 302, and second level 1 entities 310 that are served by the second level 1 aggregation entity 308. The example hierarchic resource allocation request protocol 300 may be an extension or modification of the BSR mechanism defined by 802.11 ax. The example hierarchic resource protocol 300 may be non-simultaneous (serial) when entities or channel conditions that prevent the central coordinator 302 (or aggregation entities) from, for example, simultaneously sending or identifying frames from served entities.

[0058] In the example shown in FIG. 3A, the central coordinator 302 may send a first trigger frame (TF) BSR 322 to the first level 1 aggregation entity 304. The first level 1 aggregation entity 304, based on the first TF BSR 322, may send a first BSR 324 to the first level 1 entities 306 that the first level 1 aggregation entity 304 serves. Each entity of the first level 1 entities 306 (that are associated with the first level 1 aggregation entity 304) may be a BSR in BSRs (1 to n, where n is a positive integer) 326 to the first level 1 aggregation entity 304, where each BSR (of the BSRs (1 to n ) 326) indicates a request for resources for the each entity. The BSRs (1 to n) 326 may be sent simultaneously by the first level 1 entities 306. The central coordinator 302 may send a second TF BSR 328 to the second level aggregation entity 308. The second level 1 aggregation entity 308, based on the second TF BSR 328, may cause to send a second BSR 330 to the second level 1 entities 310 that the second level 1 aggregation entity 308 serves. Each entity of the second level 1 entities 310 (that are associated with the second level 1 aggregation entity 308) may cause to send a BSR in BSRs (n+ 1 to p, where p is a positive integer greater than n+1) 332 to the second level 1 aggregation entity 308, where each BSR (of the BSRs (n+ 1 to p) 332) indicates a request for resources for the each entity. The BSRs (n+ 1 to p) 332 may be sent simultaneously by the second level 1 entities 310.

[0059] The central coordinator 302 may then cause to send a first TF 334 to the first level 1 aggregation entity 304. Based on the first TF 334, the first level 1 aggregation entity 304 may determine an aggregated (or accumulated) hierarchic resource allocation request 336 (that is based on the BSRs (1 to n) 326) and cause to send the aggregated (or accumulated) hierarchic resource allocation request 336 to the central coordinator 302. When the aggregated (or accumulated) hierarchic resource allocation request 336 is aggregated, the first level 1 aggregation entity 304 may determine the hierarchic resource allocation request 336 by (a) aggregating the BSRs (1 to n) 326 (e.g., identifying and encapsulating) and (b) causing to send the hierarchic resource allocation request 336 to the central coordinator 302. When the aggregated (or accumulated) hierarchic resource allocation request 336 is accumulated, the first level 1 aggregation entity 304 may determine the hierarchic resource allocation request 336 by (a) determining a total amount of resource(s) that are requested in the BSRs (1 to n) 326 (for each resource) and (b) causing to send the determined the hierarchic resource allocation request 336 (that includes the total amount of requested resource(s)) to the central coordinator 302. The central coordinator 302 may then cause to send a second TF 338 to the second level 1 aggregation entity 308. Based on the second TF 338, the second level 1 aggregation entity 308 may determine an aggregated (or accumulated) hierarchic resource allocation request 340 (that is based on the BSRs (n+ 1 to p) 332) and cause to send the aggregated (or accumulated) hierarchic resource allocation request 340 to the central coordinator 302.

[0060] The example of FIG. 3B is an example simultaneous hierarchic resource allocation request protocol 350 for a hierarchic resource allocation mechanism among: a central coordinator 352, a first level 1 aggregation entity 354 that is served by the central coordinator 352, first level 1 entities 356 that are served by the level 1 aggregation entity 354, a second level 1 aggregation entity 308 that is served by the central coordinator 352, and second level 1 entities 360 that are served by the second level 1 aggregation entity 358. The example simultaneous hierarchic resource allocation request protocol 350 may occur at a second level of the hierarchic network. Further, the example hierarchic resource allocation request protocol 350 may be an extension or modification of the BSR mechanism defined by 802.1 lax. The example hierarchic resource protocol 350 may be simultaneous when entities or channel conditions that allow the central coordinator 352 (or aggregation entities) to, for example, simultaneously send or identify frames from served entities. For example, the level 1 aggregation entity 354 and the level 2 aggregation entity 358 may be coordinated, and, thus, capable of causing to send coordinated frames, messages, transmissions, etc.

[0061] In the example shown in FIG. 3B, the central coordinator 352 causes to send a trigger frame (TF) BSR 362 to the first level 1 aggregation entity 354 and the second level 1 aggregation entity 358. The first level 1 aggregation entity 354 and the second level 1 aggregation entity 358 may simultaneously identify the TF BSR 362. The first level 1 aggregation entity 354 and the second level 1 aggregation entity 358 may, based on the TF BSR 362, cause to respectively send a first BSR 364 (to the first level 1 entities 356 that the first level 1 aggregation entity 354 serves) and a second BSR 366 (to the second level 1 entities 360 that the second level 1 aggregation entity 358 serves). Each entity of the first level 1 entities 356 causes to send a BSR in BSRs (1 to n, where n is a positive integer) 368 to the first level 1 aggregation entity 354, where each BSR (of the BSRs (1 to n ) 368) indicates a request for resources for the each entity. Simultaneously, each entity of the second level 1 entities 360 causes to send a BSR in BSRs (n+ 1 to p, where p is a positive integer greater than n+ 1) 370 to the second level 1 aggregation entity 358, where each BSR (of the BSRs (n+ 1 to p) 370) indicates a request for resources for the each entity.

[0062] The central coordinator 352 may then cause to send a TF 372 to the first level 1 first level 1 aggregation entity 354 and the second level 1 aggregation entity 358. Based on the TF 372, the first level 1 aggregation entity 354 and the second level 1 aggregation entity 358 may simultaneously determine aggregated (or accumulated) hierarchic resource allocation requests (that is, respectively, based on the BSRs (1 to n ) 368 and based on the BSRs (n+ 1 to p) 370). The first level 1 aggregation entity 354 may cause to send the aggregated (or accumulated) hierarchic resource allocation request 374 to the central coordinator 352, and the second level 1 aggregation entity 358 may simultaneously cause to send the aggregated (or accumulated) hierarchic resource allocation requests 376 to the central coordinator 352. [0063] When an aggregated (or accumulated) hierarchic resource allocation request 374, 376 is aggregated, a level 1 aggregation entity 354, 358 may determine the hierarchic resource allocation request 374, 376 by (a) aggregating the BSRs 368, 370 (e.g., identifying and encapsulating) and (b) causing to send the hierarchic resource allocation request 374, 376 to the central coordinator 352. When an aggregated (or accumulated) hierarchic resource allocation request 374, 376 is accumulated, a level 1 aggregation entity 354, 358 may determine the hierarchic resource allocation request 374, 376 by (a) determining a total amount of resource(s) that are requested in the BSRs 368, 370 (for each resource) and (b) causing to send the determined the hierarchic resource allocation request 374, 376 (that includes the total amount of requested resource(s)) to the central coordinator 352.

[0064] It is understood that the above is only an example meant for illustrative purposes.

[0065] FIGs. 4A-4B depict illustrative flow diagrams for hierarchic availability signaling, in accordance with one or more example embodiments of the present disclosure.

[0066] The example of FIG. 4A is an example non-simultaneous (serial) hierarchic availability signaling protocol 400 for a hierarchic resource allocation mechanism among: a central coordinator 402, a first level 1 aggregation entity 404 that is served by the central coordinator 402, first level 1 entities 406 that are served by the level 1 aggregation entity 404, a second level 1 aggregation entity 408 that is served by the central coordinator 402, and second level 1 entities 410 that are served by the second level 1 aggregation entity 408. The example hierarchic availability signaling protocol 400 may be an extension or modification of IEEE 802.11 availability request methods (e.g., target wake time (TWT)) by, for example, adding a hierarchic entity identifier or an aggregate entity identifier to availability requests. The example hierarchic availability signaling protocol 400 may be non-simultaneous (serial) when entities or channel conditions that prevent the central coordinator 402 (or aggregation entities) from, for example, simultaneously sending or identifying frames from served entities.

[0067] In the example shown in FIG. 4A, the central coordinator 402 causes to send a first TF for TWT 412 to the first level 1 aggregation entity 404. The first level 1 aggregation entity 404, based on the first TF for TWT 412, causes to send a second TF for TWT 414 to the first level 1 entities 406 that the first level 1 aggregation entity 404 serves. Each entity of the first level 1 entities 406 causes to send a TWT request in TWT requests (1 to n, where n is a positive integer) 416 to the first level 1 aggregation entity 404, where each TWT request (of the TWT requests (1 to n ) 416) indicates an availability period for the each entity. The central coordinator 402 causes to send a third TF for TWT 418 to the second level 1 aggregation entity 408. The second level 1 aggregation entity 408, based on the third TF for TWT 418, causes to send a fourth TF for TWT 420 to the second level 1 entities 410 that the second level 1 aggregation entity 408 serves. Each entity of the second level 1 entities 410 causes to send a TWT request in TWT requests (n+ 1 to p, where p is a positive integer greater than n+ 1) 422 to the second level 1 aggregation entity 408, where each TWT request (of the TWT requests (n+ 1 to p) 422) indicates an availability period for the each entity.

[0068] The central coordinator 402 may then cause to send a first TF for aggregated/accumulated TWT 424 to the first level 1 aggregation entity 404. Based on the first TF for aggregated/accumulated TWT 424, the first level 1 aggregation entity 404 may determine a first aggregated (or accumulated) TWT request 426 (that is based on the TWT requests (1 to n) 416) and cause to send the first aggregated (or accumulated) TWT request 426 to the central coordinator 402. The central coordinator 402 may then cause to send a second TF for aggregated/accumulated TWT 428 to the second level 1 aggregation entity 408. Based on the second TF for aggregated/accumulated TWT 428, the second level 1 aggregation entity 404 may determine a second aggregated (or accumulated) TWT request 430 (that is based on the TWT requests (n+ 1 to p) 422) and cause to send the second aggregated (or accumulated) TWT request 430 to the central coordinator 402.

[0069] Based on the first TF for aggregated/accumulated TWT 426, the central coordinator 402 may (1) allocate or schedule long or short term availability periods for the first level aggregation entity 404 (and, thus, first level 1 entities 406) and (2) cause to send the allocated or scheduled long or short term availability periods to the first level 1 aggregation entity 404 in a first downlink (DL) TWT response 432 to the first level 1 aggregation entity 404. Based on the first DL TWT response 432, the first level 1 aggregation entity 404 may cause to send (and optionally determine) long or short term availability periods to the first level 1 entities 406 in a second DL TWT response 434 that identifies the first level 1 entities 406. After identifying the second DL TWT response 434, each entity of the first level 1 entities 406 may respond with an acknowledgement in acknowledgements 436 indicating that the each entity has received an allocated or scheduled long or short term availability period (in the long or short term availability periods).

[0070] Additionally, based on the second TF for aggregated/accumulated TWT 430, the central coordinator 402 may (1) allocate or schedule long or short term availability periods for the second level 1 aggregation entity 408 (and, thus, the second level 1 entities 410) and (2) cause to send the allocated or scheduled long or short term availability periods to the second level 1 aggregation entity 408 in a third downlink (DL) TWT response 438 to the second level 1 aggregation entity 408. Based on the third DL TWT response 438, the second level 1 aggregation entity 408 may cause to send (and optionally determine) long or short term availability periods to the second level 1 entities 410 in a fourth DL TWT response 440 that identifies the second level 1 entities 410. After identifying the fourth DL TWT response 440, each entity of the second level 1 entities 410 may respond with an acknowledgement in acknowledgements 442 indicating that the each entity has received an allocated or scheduled long or short term availability period (in the long or short term availability periods).

[0071] The example of FIG. 4B is an example simultaneous hierarchic availability signaling protocol 450 for a hierarchic resource allocation mechanism among: a central coordinator 452, a first level 1 aggregation entity 454 that is served by the central coordinator 452, first level 1 entities 456 that are served by the level 1 aggregation entity 454, a second level 1 aggregation entity 458 that is served by the central coordinator 452, and second level 1 entities 460 that are served by the second level 1 aggregation entity 458. The example hierarchic availability signaling protocol 450 may be an extension or modification of IEEE 802.11 availability request methods (e.g., target wake time (TWT)) by, for example, adding a hierarchic entity identifier or an aggregate entity identifier to availability requests. The example hierarchic resource protocol 450 may be simultaneous when entities or channel conditions that allow the central coordinator 452 (or aggregation entities) to, for example, simultaneously send or identify frames from served entities. For example, the level 1 aggregation entity 454 and the level 2 aggregation entity 458 may be coordinated, and, thus, capable of causing to send coordinated frames, messages, transmissions, etc.

[0072] In the example shown in FIG. 4B, the central coordinator 452 causes to send a first TF for TWT 462 to the first level 1 aggregation entity 454 and the second level 1 aggregation entity 458. The first level 1 aggregation entity 454, based on the first TF for TWT 462, causes to send a second TF for TWT 464 to the first level 1 entities 456 that the first level 1 aggregation entity 454 serves, and, simultaneously, the second level 1 aggregation entity 454, based on the first TF for TWT 462, causes to send a third TF for TWT 466 to the second level 1 entities 460 that the second level 1 aggregation entity 458 serves. Each entity of the first level 1 entities 456 causes to send a TWT request in TWT requests (1 to n, where n is a positive integer) 468 to the first level 1 aggregation entity 404, where each TWT request (of the TWT requests (1 to n ) 468) indicates an availability period for the each entity. Simultaneously, each entity of the second level 1 entities 460 causes to send a TWT request in TWT requests (n+ 1 to p, where p is a positive integer greater than n+ 1) 470 to the second level 1 aggregation entity 458, where each TWT request (of the TWT requests (n+ 1 to p) 470 indicates an availability period for the each entity. [0073] The central coordinator 452 may then cause to send a TF for aggregated/accumulated TWT 472 to the first level 1 aggregation entity 454 and the second level 1 aggregation entity 458. Based on the TF for aggregated/accumulated TWT 472, the first level 1 aggregation entity 454 may determine a first aggregated (or accumulated) TWT request 474 (that is based on the TWT requests (1 to n) 468) and cause to send the aggregated (or accumulated) TWT request 472 to the central coordinator 452. Simultaneously, the second level 1 aggregation entity 458 may determine a second aggregated (or accumulated) TWT request 476 (that is based on the TWT requests (n+ 1 to p) 470) based on the TF for aggregated/accumulated TWT 472,

[0074] Based on the first aggregated (or accumulated) TWT request 474 and the second aggregated (or accumulated) TWT request 476 TF for aggregated/accumulated TWT 476, the central coordinator 452 may allocate or schedule long or short term availability periods to for the first level aggregation entity 454 (and, thus, first level 1 entities 456) as well as the second level aggregation entity 458 (and, thus, the second level 1 entities 460). Additionally, the central coordinator 452 may cause to send the allocated or scheduled long or short term availability periods to the first level 1 aggregation entity 454 and the second level 1 aggregation entity 458 in a downlink (DL) TWT response 478 to the first level 1 aggregation entity 454 and the second level 1 aggregation entity 458. Based on the DL TWT response 478, the first level 1 aggregation entity 454 and the second level 1 aggregation entity 458 may, respectively, cause to send (and optionally determine) long or short term availability periods to the first level 1 entities 456 and the second level 1 entities 460. The first level aggregation entity 454 may (a) determine a second DL TWT response 480 that includes the (determined) long or short term availability periods and identifies the first level 1 entities 406 and (b) cause to second DL TWT response 480 the first level 1 entities 456. Simultaneously, the second level aggregation entity 458 may (a) determine a third DL TWT response 482 that includes the (determined) long or short term availability periods and identifies the second level 1 entities 460 and (b) cause to third DL TWT response 482 the second level 1 entities 460.

[0075] After identifying the second DL TWT response 480, each entity of the first level 1 entities 456 may respond with an acknowledgement in acknowledgements 484 indicating that the each entity has received an allocated or scheduled long or short term availability period (in the long or short term availability periods). Simultaneously, after identifying the third DL TWT response 482, each entity of the second level 1 entities 460 may respond with an acknowledgement in acknowledgements 486 indicating that the each entity has received an allocated or scheduled long or short term availability period (in the long or short term availability periods).

[0076] It is understood that the above is only an example meant for illustrative purposes.

[0077] FIGs. 5A-5B depict illustrative flow diagrams for hierarchic PHY collaborative network sounding, in accordance with one or more example embodiments of the present disclosure.

[0078] The example of FIG. 5A is an example non- simultaneous (serial) hierarchic PHY collaborative network sounding protocol 500 for a hierarchic resource allocation mechanism among: a central coordinator 502, a first level 1 aggregation entity 504 that is served by the central coordinator 502, first level 1 entities 506 that are served by the level 1 aggregation entity 504, a second level 1 aggregation entity 508 that is served by the central coordinator 502, and second level 1 entities 510 that are served by the second level 1 aggregation entity 508. The example hierarchic PHY collaborative network sounding protocol 500 may be an extension or modification of IEEE 802.11 sounding reporting (e.g., CQI, BF, etc.). The example hierarchic PHY collaborative network sounding protocol 500 may be non- simultaneous (serial) when entities or channel conditions that prevent the central coordinator 502 (or aggregation entities) from, for example, simultaneously sending or identifying frames from served entities.

[0079] In the example shown in FIG. 5A, the central coordinator 502 causes to send a first sounding sequence and a first sounding TF 512 to the first level 1 aggregation entity 504. The first level 1 aggregation entity 504 then causes to send a second sounding sequence 514 to the first level 1 entities 506. The central coordinator 502 then causes second sounding TF 516 to the second level 1 aggregation entity 508. The second level 1 aggregation entity 508 then causes to send a third sounding sequence 518 to the second level 1 entities 510. The first sounding TF 512, the second sounding sequence TF 516, and the third sounding sequence 518 may each comprise null data packets (NDPs) and/or null data packet announcements (NDPAs).

[0080] The central coordinator 502 may cause to send a first TF for a beamforming report (BFR) 520 to the first level 1 aggregation entity 504. Based on the first TF for the BFR 520, the first level 1 aggregation entity 504 may cause to send a second TF for a BFR 522 to the first level 1 entities 506. Each of the entities of the first level 1 entities 506 may, based on the second TF for the BFR 522, process a sounding sequence by performing channel estimation and send feedback in a BFR of first BFRs (1 to n, where n is a positive integer) 524 to the first level 1 aggregation entities 504. Based on the first BFRs (1 to n ) 524, the first level 1 aggregation entity 504 determines a first aggregated (or accumulated) BFR 526 (that is based on the first BFRs (1 to n) 524) and causes to send the first aggregated (or accumulated) BFR 526 to the central coordinator 502. The first BFRs (1 to n) 524 may each comprise a response for each NDP and/or NDPA that is included in the first sounding TF 512, the second sounding sequence TF 516, or the third sounding sequence 518.

[0081] The central coordinator 502 may cause to send a third TF for a beamforming report (BFR) 528 to the second level 1 aggregation entity 508. Based on the third TF for the BFR 528, the second level 1 aggregation entity 508 may cause to send a fourth TF for a BFR 530 to the second level 1 entities 510. Each of the entities of the second level 1 entities 510 may, based on the fourth TF for the BFR 530, process a sounding sequence by performing channel estimation and send feedback in a BFR of second BFRs (n+ 1 to p, where p is a positive integer greater than n + 1) 532 to the second level 1 aggregation entities 508. Based on the second BFRs (n+ 1 to p) 532, the second level 1 aggregation entity 508 determines a first aggregated (or accumulated) BFR 534 (that is based on the second BFRs (n+ 1 to p) 532) and causes to send the first aggregated (or accumulated) BFR 534 to the central coordinator 502. The second BFRs (n+ 1 to p) 532 may each comprise a response for each NDP and/or NDPA that is included in the first sounding TF 512, the second sounding sequence TF 516, or the third sounding sequence 518.

[0082] The example of FIG. 5B is an example simultaneous hierarchic PHY collaborative network sounding protocol 550 for a hierarchic resource allocation mechanism among: a central coordinator 552, a first level 1 aggregation entity 554 that is served by the central coordinator 552, first level 1 entities 556 that are served by the level 1 aggregation entity 554, a second level 1 aggregation entity 558 that is served by the central coordinator 552, and second level 1 entities 560 that are served by the second level 1 aggregation entity 558. The example hierarchic PHY collaborative network sounding protocol 500 may be an extension or modification of IEEE 802.11 sounding reporting (e.g., CQI, BF, etc.). The example hierarchic PHY collaborative network sounding protocol 550 may be simultaneous when entities or channel conditions that allow the central coordinator 552 (or aggregation entities) to, for example, simultaneously send or identify frames from served entities. For example, the level 1 aggregation entity 554 and the level 2 aggregation entity 558 may be coordinated, and, thus, capable of causing to send coordinated frames, messages, transmissions, etc.

[0083] In the example shown in FIG. 5B, the central coordinator 552 causes to send a first sounding sequence and a first sounding TF 562 to the first level 1 aggregation entity 554 and the second level 1 aggregation entity 558. The first level 1 aggregation entity 554 then causes to send a second sounding sequence and second sounding TF 564 to the first level 1 entities 556. Simultaneously, the second level 1 aggregation entity 558 causes to send a third sounding sequence and third sounding TF 566 to the second level 1 entities 560.

[0084] Each of the entities of the first level 1 entities 556 may, based on the second sounding sequence and the second sounding TF 564, process the sounding sequence by performing channel estimation and send feedback in a BFR of first BFRs (1 to n, where n is a positive integer) 568 to the first level 1 aggregation entities 554. Simultaneously, each of the entities of the second level 1 entities 560 may, based on the third sounding sequence and the third sounding TF 566, process the sounding sequence by performing channel estimation and send feedback in a BFR of second BFRs (n+ 1 to p, where p is a positive integer greater than n + 1) 570 to the second level 1 aggregation entities 558.

[0085] The central coordinator 552 may then cause to send a TF that indicates a request for BFR 572 to the first level 1 aggregation entity 405 and the second level 1 aggregation entity 558. Based on the TF that indicates a request for BFR 572, the first level 1 aggregation entity 554 determines a first aggregated (or accumulated) BFR 574 (that is based on the first BFRs (1 to n ) 568) and causes to send the first aggregated (or accumulated) BFR 574 to the central coordinator 552. Simultaneously, based on a TF that indicates a request for BFR 572, the second level 1 aggregation entity 558 determines a second aggregated (or accumulated) BFR 576 (that is based on the second BFRs (n+ 1 to p) 570) and causes to send the second aggregated (or accumulated) BFR 574 to the central coordinator 552.

[0086] It is understood that the above is only an example meant for illustrative purposes.

[0087] FIGs. 6A-6B depict illustrative flow diagrams for DL hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure.

[0088] The example of FIG. 6A is an example non- simultaneous (serial) DL hierarchic resource allocation protocol 600 for a hierarchic resource allocation mechanism among: a central coordinator 602, a first level 1 aggregation entity 604 that is served by the central coordinator 602, first level 1 entities 606 that are served by the level 1 aggregation entity 604, a second level 1 aggregation entity 608 that is served by the central coordinator 602, and second level 1 entities 610 that are served by the second level 1 aggregation entity 608. The example DL hierarchic resource allocation protocol 600 may be non-simultaneous (serial) when entities or channel conditions that prevent the central coordinator 602 (or aggregation entities) from, for example, simultaneously sending or identifying frames from served entities.

[0089] In the example shown in FIG. 6A, the central coordinator 602 causes to send one or more DL multi-user (MU) resource allocation frames 612 for each aggregation entity in a hierarchic network (e.g., the first level 1 aggregation entity 604 and the second level 1 aggregation entity 608). Based on a DL MU resource allocation frame (of the one or more DL MU resource allocation frames 612), the first level 1 aggregation entity 604 causes to send a first acknowledgement 614 to the central coordinator 602 and the second level 1 aggregation entity 608 causes to send a second acknowledgement 616 to the central coordinator 602.

[0090] The central coordinator 602 may then cause to send a first TF 618 indicating that the first level 1 aggregation entity 604 is to allocate resources to the first level 1 entities 606. Based on the first TF 618, the first level 1 aggregation entity 604 causes to send a first set of DL data 620 (that comprises first allocated data for each entity 1 to entity n in the first level 1 entities 606) to the first level 1 entities 606. Each entity in the first level 1 entities 606 may, subsequent to receiving the first allocated data, causes to send an acknowledgement in a first set of acknowledgements 622 to the first level 1 aggregation entity 604. The central coordinator 602 may then cause to send a second TF 624 indicating that the second level 1 aggregation entity 608 is to allocate resources to the second level 1 entities 610. Based on the second TF 626, the second level 1 aggregation entity 608 causes to send a second set of DL data 626 (that comprises second allocated data for each entity n+ 1 to entity p in the second level 1 entities 610) to the second level 1 entities 610. Each entity in the second level 1 entities 610 may, subsequent to receiving the second allocated data, causes to send an acknowledgement in a second set of acknowledgements 622 to the second level 1 aggregation entity 608.

[0091] The example of FIG. 6B is an example simultaneous DL hierarchic resource allocation protocol 650 for a hierarchic resource allocation mechanism among: a central coordinator 652, a first level 1 aggregation entity 654 that is served by the central coordinator 652, first level 1 entities 656 that are served by the level 1 aggregation entity 654, a second level 1 aggregation entity 658 that is served by the central coordinator 652, and second level 1 entities 660 that are served by the second level 1 aggregation entity 658. The example simultaneous DL hierarchic resource allocation protocol 650 may be simultaneous when entities or channel conditions that allow the central coordinator 652 (or aggregation entities) to, for example, simultaneously send or identify frames from served entities. For example, the level 1 aggregation entity 654 and the level 2 aggregation entity 658 may be coordinated, and, thus, capable of causing to send coordinated frames, messages, transmissions, etc.

[0092] In the example shown in FIG. 6B, the central coordinator 652 causes to send one or more DL MU resource allocation frames 662 for each aggregation entity in a hierarchic network (e.g., the first level 1 aggregation entity 654 and the second level 1 aggregation entity 658). Based on a DL MU resource allocation frame (of the one or more DL MU resource allocation frames 662), the first level 1 aggregation entity 654 causes to send a first acknowledgement 664 to the central coordinator 652 and the second level 1 aggregation entity 658 causes to send a second acknowledgement 666 to the central coordinator 652.

[0093] The central coordinator 652 may then cause to send a TF 668 indicating that the first level 1 aggregation entity 654 and the second level aggregation entity 658 are to allocate resources to the first level 1 entities 656. Based on the TF 668, the first level 1 aggregation entity 654 causes to send a first set of DL data 670 (that comprises first allocated data for each entity 1 to entity n in the first level 1 entities 656) to the first level 1 entities 656. Simultaneously, based on the TF 668, the second level 1 aggregation entity 658 causes to send a second set of DL data 672 (that comprises second allocated data for each entity n+ 1 to entity p in the second level 1 entities 660) to the second level 1 entities 660.

[0094] Each entity in the first level 1 entities 656 may, subsequent to receiving the first allocated data, cause to send an acknowledgement in a first set of acknowledgements 674 to the first level 1 aggregation entity 654. Simultaneously, each entity in the second level 1 entities 660 may, subsequent to receiving the second allocated data, cause to send an acknowledgement in a second set of acknowledgements 676 to the second level 1 aggregation entity 658.

[0095] It is understood that the above is only an example meant for illustrative purposes.

[0096] FIGs. 7A-7B depict illustrative flow diagrams for UL hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure.

[0097] The example of FIG. 7A is an example non-simultaneous (serial) UL hierarchic resource allocation protocol 700 for a hierarchic resource allocation mechanism among: a central coordinator 702, a first level 1 aggregation entity 704 that is served by the central coordinator 702, first level 1 entities 706 that are served by the level 1 aggregation entity 704, a second level 1 aggregation entity 708 that is served by the central coordinator 702, and second level 1 entities 710 that are served by the second level 1 aggregation entity 708. The example DL hierarchic resource allocation protocol 700 may be non-simultaneous (serial) when entities or channel conditions that prevent the central coordinator 702 (or aggregation entities) from, for example, simultaneously sending or identifying frames from served entities.

[0098] In the example shown in FIG. 7A, the central coordinator 702 causes to send a first TF 712 that indicates a solicitation to upload (from entities that are unconnected or unserved) to the first level 1 aggregation entity 704 and the second level 1 aggregation entity 708. Based on the first TF 712, the first level 1 aggregation entity 704 causes to send a second TF 714 that indicates a solicitation to upload to the first level 1 entities 706. Each entity (entity 1 to entity n ) in the first level 1 entities 706, based on the second TF 714, causes to send data in a first set of data 716 to the first level 1 aggregation entity 704. Subsequent to receiving/identifying the first set of data 716, the first level 1 aggregation entity 704 causes to send a first MU BA 718 to the first level 1 entities 706. Based on the first TF 712, the second level 1 aggregation entity 708 causes to send a third TF 720 that indicates a solicitation to upload to the second level 1 entities 710. Each entity (entity n+ 1 to entity p) in the second level 1 entities 710, based on the third TF 720, causes to send data in a second set of data 722 to the second level 1 aggregation entity 708. Subsequent to receiving/identifying the second set of data 722, the second level 1 aggregation entity 708 causes to send a second MU BA 724 to the second level 1 entities 710.

[0099] The central coordinator 702 then causes to send a fourth TF 726 that indicates a solicitation to upload (from entities that are connected or served) to the first level 1 aggregation entity 704 and the second level 1 aggregation entity 708. The first level 1 aggregation entity 704 and the second level 1 aggregation entity 708 each may accumulate or aggregate, respectively, the first set of data 716 and the second set of data 722. Further, first level 1 aggregation entity 704 and the second level 1 aggregation entity 708 may cause to send, respectively, a first UL data 728 (that is the accumulated or aggregated first set of data 716) and a second UL data 730 (that is the accumulated or aggregated second set of data 722). The central coordinator 702, based on the first UL data and the second UL may cause to send a third MU BA 732 to the first level 1 aggregation entity 704 and the second level 1 aggregation entity 708.

[0100] The example of FIG. 7B is an example simultaneous UL hierarchic resource allocation protocol 750 for a hierarchic resource allocation mechanism among: a central coordinator 752, a first level 1 aggregation entity 754 that is served by the central coordinator 752, first level 1 entities 756 that are served by the level 1 aggregation entity 754, a second level 1 aggregation entity 758 that is served by the central coordinator 752, and second level 1 entities 760 that are served by the second level 1 aggregation entity 708. The example DL hierarchic resource allocation protocol 750 may be simultaneous when entities or channel conditions that allow the central coordinator 752 (or aggregation entities) to, for example, simultaneously send or identify frames from served entities. For example, the level 1 aggregation entity 754 and the level 2 aggregation entity 758 may be coordinated, and, thus, capable of causing to send coordinated frames, messages, transmissions, etc.

[0101] In the example shown in FIG. 7B, the central coordinator 752 causes to send a first TF 762 that indicates a solicitation to upload (from entities that are unconnected or unserved) to the first level 1 aggregation entity 754 and the second level 1 aggregation entity. Based on the first TF 762, the first level 1 aggregation entity 754 causes to send a second TF 764 that indicates a solicitation to upload to the first level 1 entities 756. Simultaneously, based on the first TF 762, the second level 1 aggregation entity 758 causes to send a third TF 766 that indicates a solicitation to upload to the second level 1 entities 760. Each entity (entity 1 to entity n) in the first level 1 entities 756, based on the second TF 764, causes to send data in a first set of data 768 to the first level 1 aggregation entity 754. Simultaneously, each entity (entity n+ 1 to entity p) in the second level 1 entities 760, based on the third TF 766, causes to send data in a second set of data 770 to the second level 1 aggregation entity 758. Subsequent to receiving/identifying, respectively, the first set of data 768 and the second set of data 770, the first level 1 aggregation entity 754 causes to send a first MU BA 772 to the first level 1 entities 756 and the second level 1 aggregation entity 758 causes to send a second MU BA 774 to the second level 1 entities 760.

[0102] The central coordinator 752 then causes to send a fourth TF 776 that indicates a solicitation to upload (from entities that are connected or served) to the first level 1 aggregation entity 754 and the second level 1 aggregation entity 758. The first level 1 aggregation entity 754 and the second level 1 aggregation entity 758 each may accumulate or aggregate, respectively, the first set of data 768 and the second set of data 770. Further, first level 1 aggregation entity 754 and the second level 1 aggregation entity 758 may cause to send, respectively, a first UL data 778 (that is the accumulated or aggregated first set of data 768) and a second UL data 780 (that is the accumulated or aggregated second set of data 770). The central coordinator 752, based on the first UL data and the second UL may cause to send a third MU BA 782 to the first level 1 aggregation entity 754 and the second level 1 aggregation entity 758.

[0103] It is understood that the above is only an example meant for illustrative purposes.

[0104] FIG. 8 illustrates a flow diagram of illustrative process 800 for an illustrative hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure.

[0105] At block 802, a device (e.g., the user device(s) 120 and/or the AP 102 of FIG. 1) may identify a first resource allocation request received from a first entity of a hierarchic network. For example, the device may be an aggregation entity that serves one or more entities in a hierarchic network. The device may receive the first resource allocation request from a first entity in the one or more entities.

[0106] At block 804, the device may identify a second resource allocation request received from a second entity of the hierarchic network. For example, the device may be the aggregation entity of block 904 that serves the one or more entities in the hierarchic network. The device may receive the second resource allocation request from a second entity in the one or more entities.

[0107] At block 806, the device may determine a hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request. For example, an aggregation entity may determine the hierarchic resource allocation request based on resource allocation requests that are received from entities that the aggregation entity serves In an aggregated (or pass-through) mode, the aggregation entity determines the hierarchic resource allocation request by (a) aggregating the resource allocation requests (e.g., identifying and encapsulating) and (b) causing to send the hierarchic allocation requests to the central coordinator (or to a higher level aggregation entity if the aggregation entity is not served by the central coordinator). In an accumulated mode, the aggregation entity determines the hierarchic resource allocation requests by (a) determining a total amount of resource(s) that are requested in the resource allocation requests (for each resource) and (b) causing to send the determined hierarchic resource allocation requests (that include the total amount of requested resource(s)) to the central coordinator (or to the higher level aggregation entity if the aggregation entity is not served by the central coordinator).

[0108] At block 808, the device may cause to send the hierarchic resource allocation request. For example, the aggregated mode and the accumulated mode enable resource allocation requests from lower level entities to propagate through the hierarchic network to reach the central coordinator. The device may cause to send the hierarchic resource allocation to, for example, a central coordinator.

[0109] It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0110] FIG. 9 illustrates a flow diagram of illustrative process 900 for an illustrative hierarchic resource allocation, in accordance with one or more example embodiments of the present disclosure.

[0111] At block 902, a device (e.g., the user device(s) 120 and/or the AP 102 of FIG. 1) may identify a hierarchic resource allocation request received from a first aggregation entity of one or more first aggregation entities wherein the one or more first aggregation entities are connected to one or more second aggregation entities and wherein the hierarchic resource allocation request comprises a resource allocation request from a second aggregation entity of the one or more second aggregation entities sent by the second aggregation entity to the first aggregation entity. The hierarchic resource allocation request may be an extension or modification of the BSR mechanism defined by 802.1 lax. Further, the device (e.g., a central coordinator) may be configured to receive the hierarchic resource allocation requests from aggregation entities that the device serves in a hierarchic network.

[0112] At block 904, the device may determine a hierarchic resource allocation associated with the one or more first aggregation entities and the one or more second aggregation entities, wherein the hierarchic resource allocation comprises a first resource unit allocated to the first aggregation entity and a second resource unit allocated to the second aggregation entity. For example, an aggregation entity may determine the hierarchic resource allocation request based on resource allocation requests that are received from entities that the aggregation entity serves In an aggregated (or pass-through) mode, the aggregation entity determines the hierarchic resource allocation request by (a) aggregating the resource allocation requests (e.g., identifying and encapsulating) and (b) causing to send the hierarchic allocation requests to the central coordinator (or to a higher level aggregation entity if the aggregation entity is not served by the central coordinator). In an accumulated mode, the aggregation entity determines the hierarchic resource allocation requests by (a) determining a total amount of resource(s) that are requested in the resource allocation requests (for each resource) and (b) causing to send the determined hierarchic resource allocation requests (that include the total amount of requested resource(s)) to the central coordinator (or to the higher level aggregation entity if the aggregation entity is not served by the central coordinator).

[0113] At block 906, the device may cause to send the hierarchic resource allocation to the one or more first aggregation entities. For example, the device may cause to send a triggered hierarchic resource allocation that propagates throughout the hierarchic network and meets transmission constraints of the hierarchic network (based on the data collection). The triggered hierarchic resource allocation coordinates immediate simultaneous transmission/reception from/to the aggregation entities.

[0114] It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0115] FIG. 10 shows a functional diagram of an exemplary communication station 1000 in accordance with some embodiments. In one embodiment, FIG. 10 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 1000 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. [0116] The communication station 1000 may include communications circuitry 1002 and a transceiver 1010 for transmitting and receiving signals to and from other communication stations using one or more antennas 1001. The communications circuitry 1002 may include circuitry that may operate the physical layer (PHY) communications and/or media 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 1000 may also include processing circuitry 1006 and memory 1008 arranged to perform the operations described herein. In some embodiments, the communications circuitry 1002 and the processing circuitry 1006 may be configured to perform operations detailed in FIGs. 1-7.

[0117] In accordance with some embodiments, the communications circuitry 1002 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 1002 may be arranged to transmit and receive signals. The communications circuitry 1002 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 1006 of the communication station 1000 may include one or more processors. In other embodiments, two or more antennas 1001 may be coupled to the communications circuitry 1002 arranged for sending and receiving signals. The memory 1008 may store information for configuring the processing circuitry 1006 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 1008 may include any type of memory, including non- transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 1008 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.

[0118] In some embodiments, the communication station 1000 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.

[0119] In some embodiments, the communication station 1000 may include one or more antennas 1001. The antennas 1001 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. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, 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.

[0120] In some embodiments, the communication station 1000 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.

[0121] Although the communication station 1000 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. For example, 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. In some embodiments, the functional elements of the communication station 1000 may refer to one or more processes operating on one or more processing elements.

[0122] 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). For example, 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. In some embodiments, the communication station 1000 may include one or more processors and may be configured with instructions stored on a computer-readable storage device memory.

[0123] FIG. 11 illustrates a block diagram of an example of a machine 1100 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. In other embodiments, the machine 1100 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 1100 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 1100 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments. The machine 1100 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. Further, while only a single machine is illustrated, the term“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 cluster configurations.

[0124] 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. In an example, the hardware may be specifically configured to carry out a specific operation (e.g., hardwired). In another example, 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. In this example, the execution units may be a member of more than one module. For example, under operation, 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.

[0125] The machine (e.g., computer system) 1100 may include a hardware processor 1102 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1104 and a static memory 1106, some or all of which may communicate with each other via an interlink (e.g., bus) 1108. The machine 1100 may further include a power management device 1132, a graphics display device 1110, an alphanumeric input device 1112 (e.g., a keyboard), and a user interface (UI) navigation device 1114 (e.g., a mouse). In an example, the graphics display device 1110, alphanumeric input device 1112, and UI navigation device 1114 may be a touch screen display. The machine 1100 may additionally include a storage device (i.e., drive unit) 1116, a signal generation device 1118 (e.g., a speaker), an hierarchic resource allocation device 1119, a network interface device/transceiver 1120 coupled to antenna(s) 1130, and one or more sensors 1128, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine 1100 may include an output controller 1134, 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.)).

[0126] The storage device 1116 may include a machine readable medium 1122 on which is stored one or more sets of data structures or instructions 1124 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 1124 may also reside, completely or at least partially, within the main memory 1104, within the static memory 1106, or within the hardware processor 1102 during execution thereof by the machine 1100. In an example, one or any combination of the hardware processor 1102, the main memory 1104, the static memory 1106, or the storage device 1116 may constitute machine -readable media.

[0127] The hierarchic resource allocation device 1119 may carry out or perform any of the operations and processes (e.g., process 800) described and shown above. The hierarchic resource allocation device 1119 may determine a hierarchic resource allocation request based on (1) hierarchic resource allocation request messaging, (2) hierarchic availability signaling, or (3) hierarchic PHY collaborative network sounding. Further, the hierarchic resource allocation device 1119 may cause to send the determined hierarchic resource allocation request to, in a hierarchic network, a central coordinator or to an aggregation entity

[0128] In another example, the hierarchic resource allocation device 1119 may be configured to identify the hierarchic resource allocation request to determine, for example, transmission or network restraints of a hierarchic network. Based on the determination, the hierarchic resource allocation device 1119 may determine a hierarchic resource allocation response that allocates resources to one or more entities in a hierarchic network. The hierarchic resource allocation response may comprise, for example, a resource unit. Further, the hierarchic resource allocation device 1119 may cause to send the hierarchic resource allocation response to entities (or aggregation entities) that are served/connected in the hierarchic network.

[0129] It is understood that the above are only a subset of what the hierarchic resource allocation device 1119 may be configured to perform and that other functions included throughout this disclosure may also be performed by the hierarchic resource allocation device 1119. [0130] While the machine-readable medium 1122 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 1124.

[0131] 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.

[0132] The term“machine-readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 1100 and that cause the machine 1100 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. In an example, a massed machine -readable medium includes a machine-readable medium with a plurality of particles having resting mass. Specific examples of 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.

[0133] The instructions 1124 may further be transmitted or received over a communications network 1126 using a transmission medium via the network interface device/transceiver 1120 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.). 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., 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. In an example, the network interface device/transceiver 1120 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 1126. In an example, the network interface device/transceiver 1120 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. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 1100 and includes digital or analog communications signals or other intangible media to facilitate communication of such software. The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.

[0134] 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.

[0135] As used within this document, 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. For example, 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.

[0136] As used herein, unless otherwise specified, the use of the ordinal adjectives“first,” “second,”“third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0137] The term“access point” (AP) as used herein may be a fixed station. 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.

[0138] 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 on board 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), and the like.

[0139] Some embodiments may be used in conj unction 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, multi- standard radio devices or systems, a wired or wireless handheld device, for example, a smartphone, a wireless application protocol (WAP) device, or the like.

[0140] 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 GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks.

[0141] Example 1 may be a device comprising memory and processing circuitry configured to: identify a first resource allocation request received from a first entity of a hierarchic network; identify a second resource allocation request received from a second entity of the hierarchic network; determine a hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request; and cause to send the hierarchic resource allocation request.

[0142] Example 2 may include the device of example 1 and/or some other example herein, wherein to determine the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises the memory and the processing circuitry configured to aggregate the first resource allocation request and the second resource allocation request.

[0143] Example 3 may include the device of example 1 and/or some other example herein, wherein to determine the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises the memory and the processing circuitry configured to accumulate the first resource allocation request and the second resource allocation request.

[0144] Example 4 may include the device of example 1 and/or some other example herein, wherein the hierarchic resource allocation request comprises at least one of a hierarchic entity identifier or an aggregate entity identifier. [0145] Example 5 may include the device of example 1 and/or some other example herein, wherein the memory and the processing circuitry are further configured to identify a hierarchic resource allocation received from a central coordinator of the hierarchic network.

[0146] Example 6 may include the device of example 5 and/or some other example herein, wherein the memory and the processing circuitry are further configured to determine a transmission format associated with the hierarchic resource allocation.

[0147] Example 7 may include the device of example 6 and/or some other example herein, wherein the transmission format comprises one of an orthogonal frequency division multiplexing value, a multiple-input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

[0148] Example 8 may include the device of example 5 and/or some other example herein, wherein the hierarchic resource allocation comprises a first resource unit allocated to the first entity and a second resource unit allocated to the second entity.

[0149] Example 9 may include the device of example 8 and/or some other example herein, wherein the memory and the processing circuitry are further configured to: determine a trigger frame comprising the first resource unit allocated to the first entity and the second resource unit allocated to the second entity; and cause to send the trigger frame to the first entity and the second entity.

[0150] Example 10 may include the device of example 1 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals.

[0151] Example 11 may include the device of example 10 and/or some other example herein, further comprising one or more antennas coupled to the transceiver.

[0152] Example 12 may include a non-transitory computer-readable medium storing computer-executable instructions that when executed by one or more processors result in performing operations comprising: identifying a hierarchic resource allocation request received from a first aggregation entity of one or more first aggregation entities wherein the one or more first aggregation entities are connected to one or more second aggregation entities, and wherein the hierarchic resource allocation request comprises a resource allocation request from a second aggregation entity of the one or more second aggregation entities sent by the second aggregation entity to the first aggregation entity; determining a hierarchic resource allocation associated with the one or more first aggregation entities and the one or more second aggregation entities, wherein the hierarchic resource allocation comprises a first resource unit allocated to the first aggregation entity and a second resource unit allocated to the second aggregation entity; and causing to send the hierarchic resource allocation to the one or more first aggregation entities.

[0153] Example 13 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein the hierarchic resource allocation request comprises one or more resource allocation requests that are aggregated by the first aggregation entity and received from the one or more second aggregation entities.

[0154] Example 14 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein the hierarchic resource allocation request comprises one or more hierarchic entity identifiers associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0155] Example 15 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein the hierarchic resource allocation comprises an extension or a modification of a buffer status report.

[0156] Example 16 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein determining the hierarchic resource allocation comprises determining a transmission format associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0157] Example 17 may include the non-transitory computer-readable medium of example 16 and/or some other example herein, wherein the transmission format comprises one of an orthogonal frequency division multiplexing value, a multiple-input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

[0158] Example 18 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein determining the hierarchic resource allocation comprises allocating a hierarchic transmission opportunity associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0159] Example 19 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein the operations further comprising: determining a sounding sequence, wherein the sounding sequence comprises a reference sounding element associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities; and causing to send the sounding sequence.

[0160] Example 20 may include the non-transitory computer-readable medium of example 19 and/or some other example herein, wherein the operations further comprising identifying a sounding report associated with the sounding sequence from at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0161] Example 21 may include a method comprising: identifying, by one or more processors, a first resource allocation request received from a first entity of a hierarchic network; identifying a second resource allocation request received from a second entity of the hierarchic network; determining a hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request; and causing to send the hierarchic resource allocation request.

[0162] Example 22 may include the method of example 21 and/or some other example herein, wherein determining the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises aggregating the first resource allocation request and the second resource allocation request.

[0163] Example 23 may include the method of example 21 and/or some other example herein, wherein determining the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises accumulating the first resource allocation request and the second resource allocation request.

[0164] Example 24 may include the method of example 21 and/or some other example herein, wherein the hierarchic resource allocation request comprises at least one of a hierarchic entity identifier or an aggregate entity identifier.

[0165] Example 25 may include the method of example 21 and/or some other example herein, further comprising identifying a hierarchic resource allocation received from a central coordinator of the hierarchic network.

[0166] Example 26 may include the method of example 25 and/or some other example herein, further comprising determining a transmission format associated with the hierarchic resource allocation.

[0167] Example 27 may include the method of example 26 and/or some other example herein, further comprising one of an orthogonal frequency division multiplexing value, a multiple-input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

[0168] Example 28 may include the method of example 25 and/or some other example herein, further comprising a first resource unit allocated to the first entity and a second resource unit allocated to the second entity. [0169] Example 29 may include the method of example 28 and/or some other example herein, further comprising: determining a trigger frame comprising the first resource unit allocated to the first entity and the second resource unit allocated to the second entity; and causing to send the trigger frame to the first entity and the second entity.

[0170] Example 30 may include an apparatus comprising means for performing a method as claimed in any one of examples 21-29.

[0171] Example 31 may include a system, comprising at least one memory device having programmed instruction that, in response to execution, cause at least one processor to perform the method of any one of examples 21-29.

[0172] Example 32 may include a machine readable medium including code, when executed, to cause a machine to perform the method of any one of examples 21-29.

[0173] Example 33 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: identifying, by one or more processors, a first resource allocation request received from a first entity of a hierarchic network; identifying a second resource allocation request received from a second entity of the hierarchic network; determining a hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request; and causing to send the hierarchic resource allocation request.

[0174] Example 34 may include the non-transitory computer-readable medium of example 33 and/or some other example herein, wherein determining the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises aggregating the first resource allocation request and the second resource allocation request.

[0175] Example 35 may include the non-transitory computer-readable medium of example 33 and/or some other example herein, wherein determining the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises accumulating the first resource allocation request and the second resource allocation request.

[0176] Example 36 may include the non-transitory computer-readable medium of example 33 and/or some other example herein, wherein the hierarchic resource allocation request comprises at least one of a hierarchic entity identifier or an aggregate entity identifier. [0177] Example 37 may include the non-transitory computer-readable medium of example 33 and/or some other example herein, wherein identifying a hierarchic resource allocation received from a central coordinator of the hierarchic network.

[0178] Example 38 may include the non-transitory computer-readable medium of example

37 and/or some other example herein, wherein determining a transmission format associated with the hierarchic resource allocation.

[0179] Example 39 may include the non-transitory computer-readable medium of example

38 and/or some other example herein, wherein one of an orthogonal frequency division multiplexing value, a multiple-input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

[0180] Example 40 may include the non-transitory computer-readable medium of example 37 and/or some other example herein, wherein a first resource unit allocated to the first entity and a second resource unit allocated to the second entity.

[0181] Example 41 may include the non-transitory computer-readable medium of example 40 and/or some other example herein, wherein operations further comprising: determining a trigger frame comprising the first resource unit allocated to the first entity and the second resource unit allocated to the second entity; and causing to send the trigger frame to the first entity and the second entity.

[0182] Example 42 may include an apparatus comprising means for: identifying, by one or more processors, a first resource allocation request received from a first entity of a hierarchic network; means for identifying a second resource allocation request received from a second entity of the hierarchic network; means for determining a hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request; and means for causing to send the hierarchic resource allocation request.

[0183] Example 43 may include the apparatus of example 42 and/or some other example wherein determining the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises aggregating the first resource allocation request and the second resource allocation request.

[0184] Example 44 may include the apparatus of example 42 and/or some other example wherein determining the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises accumulating the first resource allocation request and the second resource allocation request. [0185] Example 45 may include the apparatus of example 42 and/or some other example wherein the hierarchic resource allocation request comprises at least one of a hierarchic entity identifier or an aggregate entity identifier.

[0186] Example 46 may include the apparatus of example 42 and/or some other example wherein identifying a hierarchic resource allocation received from a central coordinator of the hierarchic network.

[0187] Example 47 may include the apparatus of example 46 and/or some other example wherein determining a transmission format associated with the hierarchic resource allocation.

[0188] Example 48 may include the apparatus of example 47 and/or some other example wherein one of an orthogonal frequency division multiplexing value, a multiple-input multiple- output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

[0189] Example 49 may include the apparatus of example 46 and/or some other example wherein a first resource unit allocated to the first entity and a second resource unit allocated to the second entity.

[0190] Example 50 may include the apparatus of example 49 and/or some other example, further comprising: means for determining a trigger frame comprising the first resource unit allocated to the first entity and the second resource unit allocated to the second entity; and means for causing to send the trigger frame to the first entity and the second entity.

[0191] Example 51 may be a device comprising memory and processing circuitry configured to: identify a hierarchic resource allocation request received from a first aggregation entity of one or more first aggregation entities wherein the one or more first aggregation entities are connected to one or more second aggregation entities, and wherein the hierarchic resource allocation request comprises a resource allocation request from a second aggregation entity of the one or more second aggregation entities sent by the second aggregation entity to the first aggregation entity; determine a hierarchic resource allocation associated with the one or more first aggregation entities and the one or more second aggregation entities, wherein the hierarchic resource allocation comprises a first resource unit allocated to the first aggregation entity and a second resource unit allocated to the second aggregation entity; and cause to send the hierarchic resource allocation to the one or more first aggregation entities.

[0192] Example 52 may include the device of example 51 and/or some other example herein, wherein the hierarchic resource allocation request comprises one or more resource allocation requests that are aggregated by the first aggregation entity and received from the one or more second aggregation entities. [0193] Example 53 may include the device of example 51 and/or some other example herein, wherein the hierarchic resource allocation request comprises one or more hierarchic entity identifiers associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0194] Example 54 may include the device of example 51 and/or some other example herein, wherein the hierarchic resource allocation comprises an extension or a modification of a buffer status report.

[0195] Example 55 may include the device of example 51 and/or some other example herein, wherein determining the hierarchic resource allocation comprises determining a transmission format associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0196] Example 56 may include the device of example 55 and/or some other example herein, wherein the transmission format comprises one of an orthogonal frequency division multiplexing value, a multiple-input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

[0197] Example 57 may include the device of example 51 and/or some other example herein, wherein determining the hierarchic resource allocation comprises allocating a hierarchic transmission opportunity associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0198] Example 58 may include the device of example 51 and/or some other example herein, wherein the processing circuitry is further configured to: determine a sounding sequence, wherein the sounding sequence comprises a reference sounding element associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities; and cause to send the sounding sequence.

[0199] Example 59 may include the device of example 58 and/or some other example herein, wherein the processing circuitry is further configured to: identify a sounding report associated with the sounding sequence from at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0200] Example 60 may include the device of example 51 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals.

[0201] Example 61 may include the device of example 60 and/or some other example herein, further comprising one or more antennas coupled to the transceiver. [0202] Example 62 may include a method comprising: identifying a hierarchic resource allocation request received from a first aggregation entity of one or more first aggregation entities wherein the one or more first aggregation entities are connected to one or more second aggregation entities, and wherein the hierarchic resource allocation request comprises a resource allocation request from a second aggregation entity of the one or more second aggregation entities sent by the second aggregation entity to the first aggregation entity; determining a hierarchic resource allocation associated with the one or more first aggregation entities and the one or more second aggregation entities, wherein the hierarchic resource allocation comprises a first resource unit allocated to the first aggregation entity and a second resource unit allocated to the second aggregation entity; and causing to send the hierarchic resource allocation to the one or more first aggregation entities.

[0203] Example 63 may include the method of example 62 and/or some other example herein, wherein the hierarchic resource allocation request comprises one or more resource allocation requests that are aggregated by the first aggregation entity and received from the one or more second aggregation entities.

[0204] Example 64 may include the method of example 62 and/or some other example herein, wherein the hierarchic resource allocation request comprises one or more hierarchic entity identifiers associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0205] Example 65 may include the method of example 62 and/or some other example herein, wherein the hierarchic resource allocation comprises an extension or a modification of a buffer status report.

[0206] Example 66 may include the method of example 62 and/or some other example herein,, wherein determining the hierarchic resource allocation comprises determining a transmission format associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0207] Example 67 may include the method of example 66 and/or some other example herein, wherein the transmission format comprises one of an orthogonal frequency division multiplexing value, a multiple-input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

[0208] Example 68 may include the method of example 62 and/or some other example herein, wherein determining the hierarchic resource allocation comprises allocating a hierarchic transmission opportunity associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0209] Example 69 may include the method of example 62 and/or some other example herein, further comprising: determining a sounding sequence, wherein the sounding sequence comprises a reference sounding element associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities; and causing to send the sounding sequence.

[0210] Example 70 may include the method of example 69 and/or some other example herein, further comprising identifying a sounding report associated with the sounding sequence from at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0211] Example 71 may include an apparatus comprising means for performing a method as claimed in any one of examples 62-70.

[0212] Example 72 may include a system, comprising at least one memory device having programmed instruction that, in response to execution, cause at least one processor to perform the method of any one of examples 62-70.

[0213] Example 73 may include a machine readable medium including code, when executed, to cause a machine to perform the method of any one of examples 62-70.

[0214] Example 74 may include an apparatus comprising means for: identifying a hierarchic resource allocation request received from a first aggregation entity of one or more first aggregation entities wherein the one or more first aggregation entities are connected to one or more second aggregation entities, and wherein the hierarchic resource allocation request comprises a resource allocation request from a second aggregation entity of the one or more second aggregation entities sent by the second aggregation entity to the first aggregation entity; means for determining a hierarchic resource allocation associated with the one or more first aggregation entities and the one or more second aggregation entities, wherein the hierarchic resource allocation comprises a first resource unit allocated to the first aggregation entity and a second resource unit allocated to the second aggregation entity; and means for causing to send the hierarchic resource allocation to the one or more first aggregation entities.

[0215] Example 75 may include the apparatus of example 74 and/or some other example herein, wherein the hierarchic resource allocation request comprises one or more resource allocation requests that are aggregated by the first aggregation entity and received from the one or more second aggregation entities. [0216] Example 76 may include the apparatus of example 74 and/or some other example herein, wherein the hierarchic resource allocation request comprises one or more hierarchic entity identifiers associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0217] Example 77 may include the apparatus of example 74 and/or some other example herein, wherein the hierarchic resource allocation comprises an extension or a modification of a buffer status report.

[0218] Example 78 may include the apparatus of example 74 and/or some other example herein, wherein determining the hierarchic resource allocation comprises determining a transmission format associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0219] Example 79 may include the apparatus of example 78 and/or some other example herein, wherein the transmission format comprises one of an orthogonal frequency division multiplexing value, a multiple-input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

[0220] Example 80 may include the apparatus of example 74 and/or some other example herein, wherein determining the hierarchic resource allocation comprises allocating a hierarchic transmission opportunity associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0221] Example 81 may include the apparatus of example 74 and/or some other example herein, further comprising: means for determining a sounding sequence, wherein the sounding sequence comprises a reference sounding element associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities; and means for causing to send the sounding sequence.

[0222] Example 82 may include the apparatus of example 81 and/or some other example herein, means for identifying a sounding report associated with the sounding sequence from at least one of the one or more first aggregation entities or the one or more second aggregation entities.

[0223] Example 83 may include an apparatus comprising means for performing a method as claims in any one of the preceding examples.

[0224] Example 84 may include machine-readable storage including machine-readable instructions, when executed, to implement a method as claimed in any preceding example. [0225] Example 85 may include machine-readable storage including machine-readable instructions, when executed, to implement a method of realize an apparatus as claimed in any preceding example.

[0226] Example 86 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-85, or any other method or process described herein.

[0227] Example 87 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-85, or any other method or process described herein.

[0228] Example 88 may include a method, technique, or process as described in or related to any of examples 1-85, or portions or parts thereof.

[0229] Example 89 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-85, or portions thereof.

[0230] Example 90 may include a method of communicating in a wireless network as shown and described herein.

[0231] Example 91 may include a system for providing wireless communication as shown and described herein.

[0232] Example 92 may include a device for providing wireless communication as shown and described herein.

[0233] 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, for example, method, may be claimed in another claim category, for example, 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) may be claimed as well, so that any combination of claims and the features thereof are disclosed and may be claimed regardless of the dependencies chosen in the attached claims. The subject- matter which may be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims may be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein may be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims.

[0234] The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0235] Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations.

[0236] 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. As an example, 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. [0237] Accordingly, 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.

[0238] 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.

[0239] Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

CLAIMS What is claimed is:

1. A device, the device comprising memory and processing circuitry configured to: identify a first resource allocation request received from a first entity of a hierarchic network;

identify a second resource allocation request received from a second entity of the hierarchic network;

determine a hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request; and

cause to send the hierarchic resource allocation request.

2. The device of claim 1, wherein to determine the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises the memory and the processing circuitry configured to aggregate the first resource allocation request and the second resource allocation request.

3. The device of claim 1, wherein to determine the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises the memory and the processing circuitry configured to accumulate the first resource allocation request and the second resource allocation request.

4. The device of claim 1, wherein the hierarchic resource allocation request comprises at least one of a hierarchic entity identifier or an aggregate entity identifier.

5. The device of any one of claims 1 to 4, wherein the memory and the processing circuitry are further configured to identify a hierarchic resource allocation received from a central coordinator of the hierarchic network.

6. The device of claim 5, wherein the memory and the processing circuitry are further configured to determine a transmission format associated with the hierarchic resource allocation.

7. The device of claim 6, wherein the transmission format comprises one of an orthogonal frequency division multiplexing value, a multiple-input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

8. The device of claim 5, wherein the hierarchic resource allocation comprises a first resource unit allocated to the first entity and a second resource unit allocated to the second entity.

9. The device of claim 8, wherein the memory and the processing circuitry are further configured to:

determine a trigger frame comprising the first resource unit allocated to the first entity and the second resource unit allocated to the second entity; and

cause to send the trigger frame to the first entity and the second entity.

10. The device of claim 1, further comprising a transceiver configured to transmit and receive wireless signals.

11. The device of claim 10, further comprising one or more antennas coupled to the transceiver.

12. A non-transitory computer-readable medium storing computer-executable instructions that when executed by one or more processors result in performing operations comprising: identifying a hierarchic resource allocation request received from a first aggregation entity of one or more first aggregation entities wherein the one or more first aggregation entities are connected to one or more second aggregation entities, and wherein the hierarchic resource allocation request comprises a resource allocation request from a second aggregation entity of the one or more second aggregation entities sent by the second aggregation entity to the first aggregation entity;

determining a hierarchic resource allocation associated with the one or more first aggregation entities and the one or more second aggregation entities, wherein the hierarchic resource allocation comprises a first resource unit allocated to the first aggregation entity and a second resource unit allocated to the second aggregation entity; and

causing to send the hierarchic resource allocation to the one or more first aggregation entities.

13. The non-transitory computer-readable medium of claim 12, wherein the hierarchic resource allocation request comprises one or more resource allocation requests that are aggregated by the first aggregation entity and received from the one or more second aggregation entities.

14. The non-transitory computer-readable medium of claim 12, wherein the hierarchic resource allocation request comprises one or more hierarchic entity identifiers associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

15. The non-transitory computer-readable medium of claim 12, wherein the hierarchic resource allocation comprises an extension or a modification of a buffer status report.

16. The non-transitory computer-readable medium of any one of claims 12 to 15, wherein determining the hierarchic resource allocation comprises determining a transmission format associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

17. The non-transitory computer-readable medium of claim 16, wherein the transmission format comprises one of an orthogonal frequency division multiplexing value, a multiple- input multiple-output (MIMO) value, a modulation and coding scheme value, an orthogonal frequency division multiple access (OFDMA) value, or a MIMO and OFDMA combination value.

18. The non-transitory computer-readable medium of claim 12, wherein determining the hierarchic resource allocation comprises allocating a hierarchic transmission opportunity associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities.

19. The non-transitory computer-readable medium of claim 12, wherein the operations further comprising: determining a sounding sequence, wherein the sounding sequence comprises a reference sounding element associated with at least one of the one or more first aggregation entities or the one or more second aggregation entities; and

causing to send the sounding sequence.

20. The non-transitory computer-readable medium of claim 19, wherein the operations further comprising identifying a sounding report associated with the sounding sequence from at least one of the one or more first aggregation entities or the one or more second aggregation entities.

21. A method comprising:

identifying, by one or more processors, a first resource allocation request received from a first entity of a hierarchic network;

identifying a second resource allocation request received from a second entity of the hierarchic network;

determining a hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request; and

causing to send the hierarchic resource allocation request.

22. The method of claim 21, wherein determining the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises aggregating the first resource allocation request and the second resource allocation request.

23. The method of claim 21, wherein determining the hierarchic resource allocation request associated with the first resource allocation request and the second resource allocation request comprises accumulating the first resource allocation request and the second resource allocation request.

24. The method of claim 21, wherein the hierarchic resource allocation request comprises at least one of a hierarchic entity identifier or an aggregate entity identifier.

25. The method of any one of claims 21 to 24, further comprising identifying a hierarchic resource allocation received from a central coordinator of the hierarchic network.