WO2019132861A1 - Coordination améliorée de réseau chronosensible pour des transmissions sans fil - Google Patents

Coordination améliorée de réseau chronosensible pour des transmissions sans fil Download PDF

Info

Publication number
WO2019132861A1
WO2019132861A1 PCT/US2017/068438 US2017068438W WO2019132861A1 WO 2019132861 A1 WO2019132861 A1 WO 2019132861A1 US 2017068438 W US2017068438 W US 2017068438W WO 2019132861 A1 WO2019132861 A1 WO 2019132861A1
Authority
WO
WIPO (PCT)
Prior art keywords
plane interface
time sensitive
transmission
control plane
data
Prior art date
Application number
PCT/US2017/068438
Other languages
English (en)
Inventor
Dave Cavalcanti
Laurent Cariou
Mohammad Mamunur Rashid
Carlos Cordeiro
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Priority to PCT/US2017/068438 priority Critical patent/WO2019132861A1/fr
Priority to CN201780095118.9A priority patent/CN111133825A/zh
Publication of WO2019132861A1 publication Critical patent/WO2019132861A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12—Access point controller devices

Definitions

  • This disclosure generally relates to systems, methods, and devices for wireless communications and, more particularly, enhanced time sensitive network coordination for wireless communications.
  • Wireless devices are becoming widely prevalent and are increasingly requesting access to wireless channels.
  • the growing density of wireless deployments require increased network and spectrum availability.
  • FIG. 1 is a diagram illustrating an example network environment, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 2 depicts an illustrative transmission schedule for multiple access points in a wireless time sensitive networking domain, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 3 depicts an illustrative distributed time sensitive coordination architecture, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 4A depicts an illustrative timing diagram of a scheduled data flow in an enhanced time sensitive network, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 4B depicts an illustrative timing diagram of a management frame flow in an enhanced time sensitive network, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 is a diagram illustrating an enhanced time sensitive network environment, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 A illustrates a flow diagram of illustrative process for enhanced time sensitive networking coordination, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6B illustrates a flow diagram of illustrative process for enhanced time sensitive networking coordination, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 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.
  • FIG. 8 illustrates a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.
  • Example embodiments described herein provide certain systems, methods, and devices for enhanced time sensitive network coordination for wireless communications.
  • 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.
  • TSN time sensitive networking
  • TSN applications may require very low and bounded transmission latency and high availability, and may include a mix of traffic patterns and requirements from synchronous data flows (e.g., from sensors to a controller in a closed loop control system), to asynchronous events (e.g., a sensor detecting an anomaly in a monitored process and sending a report right away), to video streaming for remote asset monitoring and background IT/office traffic.
  • Many TSN applications also may require communication between devices across multiple links/hops (e.g., in a mesh topology) with ultra-low latency on the order of lO’s of microseconds.
  • a time synchronized scheduled access mode for Wi-Fi may be enabled in existing and/or future frequency bands (e.g., 6-7 GHz), and in controlled deployments in which it may be feasible to dedicate a channel for a time sensitive operation.
  • frequency bands e.g., 6-7 GHz
  • a greenfield mode may refer to a mode where a device assumes that there are no legacy (e.g., operating under previous protocol rules) stations (STAs) using the same channel.
  • STAs stations
  • a device operating with a greenfield mode may operate under an assumption that all other STAs follow the same (e.g., newest) protocols, and that no legacy STAs are competing for the same channel access.
  • an STA operating with a greenfield mode may at least assume that any legacy STAs that may exist may be managed to operate in a separate channel and/or time.
  • operations with multiple access points (APs) may experience interference, latency, and/or other performance issues. For example, APs may not all be aware of what other APs and STAs may be doing.
  • a greenfield Wi-Fi operation in a 6-7 GHz band or another frequency band, and thereby enable a time synchronized scheduled access mode for multiple APs in the 6-7 GHz band or other existing frequency bands (e.g., 2.4 GHz, 5 GHz) of future Wi-Fi generations.
  • the IEEE 802.11 family of wireless communication standards define many wireless communication parameters and protocols. However, latency and reliability performance guarantees may be improved in some IEEE 802.11 embodiments. For example, the IEEE 802.1 lac standard may improve peak user throughput, and the IEEE 802.11 ax standard may improve efficiency, but additional capability to control user latency may allow for other improvements. For example, a time synchronized/scheduled operation may improve control of latency and reliability, which may be useful in supporting emerging time sensitive operations such as smart factories, professional audio/video, and mobile virtual reality.
  • Example embodiments of the present disclosure relate to systems, methods, and devices for enhanced time sensitive network coordination for wireless communications.
  • network architecture and protocols may enable coordination of time sensitive control and data channels across multiple access points (APs).
  • APs access points
  • a network architecture may include a central entity, such as a wireless TSN controller (e.g., a controller), responsible for configuring and scheduling time sensitive control and data operations across multiple APs.
  • a wireless TSN (WTSN) management protocol may be defined for coordination between multiple APs (e.g., WTSN management clients) and the controller to enable admission control, joint scheduling, and network measurements.
  • multiple APs may synchronize and align control and data transmissions to allow for deterministic latency with a high reliability for time sensitive applications on a shared time sensitive data channel while also allowing coexistence with non time sensitive traffic that may be in the same network.
  • Time sensitive applications may be prioritized over non-time sensitive applications, meaning that transmission schedules may need to be updated to accommodate time sensitive needs.
  • enhanced time sensitive network coordination may be adopted in future Wi-Fi standards for new frequency bands (e.g., 6-7 GHz) in which additional requirements of time synchronization and scheduled operation may be introduced.
  • Enhanced time sensitive network coordination may be used in managed Wi-Fi deployments (e.g., enterprise, industrial, managed home networks, etc.) in which time sensitive traffic may be steered to a dedicated channel in existing as well as new bands.
  • Wi-Fi network may be managed, and that there are no unmanaged Wi-Fi STAs/networks nearby.
  • APs and STAs may synchronize their clocks to a master reference time (e.g., STAs may synchronize to beacons and/or may use time synchronization protocols as defined in the IEEE 802.1 AS standard).
  • APs and STAs may operate according to a time synchronized scheduled mode that may also apply to new frequency bands (e.g., 6-7 GHz), for which new access protocols and requirements also may apply.
  • new frequency bands e.g., 6-7 GHz
  • a controller may make scheduling decisions, collect measurements, and may interact with APs through a backhaul, which may be wireless over Wi Fi or wired connections.
  • Control messages from a controller may use two or more propagation “hops” to reach STAs (e.g., controller to AP, AP to STA).
  • APs may exchange over-the-air control information with STAs, and such exchanges may be coordinated among multiple APs to account for potential interference.
  • a controller when a controller is implemented in the same hardware as an AP, communication with STAs may only require a single propagation hop to reach STAs.
  • a framework may allow for dual connectivity and multi-band operations in which multi-band STAs may be associated with multiple APs to implement specific multi-band features, such as separation of data and control planes, in order to facilitate data traffic in a data plane and control traffic in a control plane (e.g., different bands or sub-bands).
  • enhanced mechanisms may enable direct and indirect connections between a controller and STAs to manage time sensitive traffic scheduling on one or more bands. For example, time sensitive traffic scheduling may use one band, while data traffic may use another band or channel (e.g., through a connection with the closest AP).
  • an extended service set (ESS) wireless controller e.g., a controller
  • ESS extended service set
  • APs in a same ESS may operate in a same or another band, a same or another channel, and/or each AP may have its own basic service set (BSS).
  • BSS basic service set
  • a controller may be operating in a band which may allow for long coverage (e.g., may cover an entire area spanned by STAs).
  • APs may operate in a band which may allow for shorter coverage (e.g., small cells), and may be spread uniformly to enable blanket coverage of an area with specific frequency planning.
  • STAs may perform a dual connection, one with the controller BSS, and one with a best serving AP.
  • STAs may implement multi-band separation of data and control planes on two connections by interacting with a controller on control exchanges which may relate to configuration of an operation on a control plane band, and may interact with a serving AP for a data plane.
  • a controller may collect measurements directly from STAs through a control interface, and may provide scheduling information to STAs directly through the control interface.
  • a controller also may provide scheduling information to serving APs through a backhaul or through a control plane interface.
  • STAs and APs may apply scheduling information for data plane transmissions, and the data plane may be on a band connected with serving APs.
  • multi-hop transmissions may be used or replaced by direct interactions (e.g., a direct controller-to-STA connection), and overall network efficiency may be improved.
  • direct interactions e.g., a direct controller-to-STA connection
  • FIG. 1 is a diagram illustrating an example network environment, in accordance with one or more example embodiments of the present disclosure.
  • Wireless network 100 may include one or more user devices 120 and one or more access point(s) (APs) 102, which may communicate in accordance with and compliant with various communication standards and protocols, such as, Wi-Fi, TSN, Wireless USB, P2P, Bluetooth, NFC, or any other communication standard.
  • the user device(s) 120 may be mobile devices that are non stationary (e.g., not having fixed locations) or may be stationary devices.
  • the user devices 120 and AP 102 may include one or more computer systems similar to that of the functional diagram of FIG. 7 and/or the example machine/system of FIG. 8.
  • One or more illustrative user device(s) 120 and/or AP 102 may be operable by one or more user(s) 108. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of- service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 and the AP(s) 102 may be STAs.
  • STA station
  • An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of- service (QoS) STA, a dependent STA, and a hidden STA.
  • QoS quality-of- service
  • the one or more illustrative user device(s) 120 and the AP(s) 102 may
  • 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).
  • PBSS personal basic service set
  • PCP/AP control point/access point
  • the user device(s) 120 (e.g., 124, 126, or 128) and/or AP 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static, device.
  • user device(s) 120 and/or AP 102 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook tm 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 robotic device, an actuator, a robotic arm, an industrial robotic device, a programmable logic controller (PLC), a safety controller and monitoring 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
  • Any of the user device(s) 120 may be configured to communicate with each other via one or more communications networks 135 and/or 140 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 135 and/or 140 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.
  • any of the communications networks 135 and/or 140 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).
  • any of the communications networks 135 and/or 140 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.
  • coaxial cable twisted-pair wire
  • optical fiber a hybrid fiber coaxial (HFC) medium
  • microwave terrestrial transceivers microwave terrestrial transceivers
  • radio frequency communication mediums white space communication mediums
  • ultra-high frequency communication mediums satellite communication mediums, or any combination thereof.
  • Any of the user device(s) 120 may include one or more communications antennas.
  • the one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s) 120 (e.g., user devices 124, 126, 128, 130, and 132), and AP 102.
  • suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, or the like.
  • the one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 120 and/or AP 102.
  • Any of the user device(s) 120 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network.
  • Any of the user device(s) 120 e.g., user devices 124, 126, 128, 130, and 132
  • 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 124, 126, 128, 130, and 132
  • 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 124, 126, 128, 130, and 132
  • AP 102 may be configured to perform any given directional reception from one or more defined receive sectors.
  • MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming.
  • user devices 120 and/or AP 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.
  • Any of the user devices 120 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 and AP 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 communication standards and protocols, such as, Wi-Fi, TSN, Wireless USB, Wi-Fi P2P, Bluetooth, NFC, or any other communication standard.
  • the radio component in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g., 802.1 lb, 802. l lg, 802.11h, 802.1 lax), 5 GHz channels (e.g., 802.11h, 802.1 lac, 802.1 lax), or 60 GHZ channels (e.g., 802.1 lad, 802.1 lay).
  • 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.
  • LNA low noise amplifier
  • A/D analog-to-digital converter
  • an AP e.g., AP 102
  • 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 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.
  • the data frames may be preceded by one or more preambles that may be part of one or more headers. These preambles may be used to allow a device (e.g., AP 102 and/or user devices 120) to detect a new incoming data frame from another device.
  • a preamble may be a signal used in network communications to synchronize transmission timing between two or more devices (e.g., between the APs and user devices).
  • an AP 102 may communicate with user devices 120.
  • the user devices 120 may include one or more wireless devices (e.g., user devices 124, 128, 130) and one or more wireless TSN devices (e.g., user devices 126 and 132).
  • the user devices may access a channel in accordance with medium access control (MAC) protocol rules or any other access rules (e.g., Wi-Fi, Bluetooth, NFC, etc.).
  • MAC medium access control
  • reserving a dedicated TSN channel and controlling access to it may also be applicable to cellular systems/3GPP networks, such as LTE, 5G, or any other wireless networks.
  • the wireless TSN devices may also access a channel according to the same or modified protocol rules.
  • the AP 102 may dedicate certain channels or sub channels for TSN applications that may be needed by the one or more wireless TSN devices (e.g., user devices 126 and 132), and may allocate other channels or sub-channels for the non- TSN devices (e.g., user devices 124, 128, and 130).
  • the one or more wireless TSN devices e.g., user devices 126 and 132
  • other channels or sub-channels for the non- TSN devices (e.g., user devices 124, 128, and 130).
  • AP 102 may also define one or more access rules associated with the dedicated channels.
  • a channel may be dedicated for TSN transmissions, TSN applications, and TSN devices.
  • user device 126 may access a dedicated TSN channel for TSN transmissions.
  • TSN transmissions may include transmissions that have very low transmission latency and high availability requirements.
  • the TSN transmissions may include synchronous TSN data flows between sensors, actuators, controllers, robots, in a closed loop control system.
  • the TSN transmissions require reliable and deterministic communications.
  • a channel may be accessed by the user device 126 for a number of TSN message flows and is not limited to only one TSN message flow.
  • the TSN message flows may depend on the type of application messages that are being transmitted between the AP 102 and the user device 126.
  • frequency planning and channel management may be used to allow neighboring APs (e.g., AP 104 and AP 106) to operate in different channels
  • the efficiency and feasibility of reserving multiple non-overlapping data channels for time sensitive applications may be improved. It may be desirable to limit the amount of resources reserved for time sensitive data through efficient channel reuse.
  • multiple APs e.g., AP 104 and AP 106
  • share a dedicated channel for time sensitive data transmissions interference among multiple transmissions may be reduced with enhanced coordination between the APs. For example, overlap and interference of control transmissions (e.g., a beacon), downlink data transmissions, and uplink data transmissions may be reduced with enhanced coordination.
  • Such enhanced coordination for multiple APs may enable more efficient channel usage while also meeting latency and reliability requirements of time sensitive applications. For example, if control transmissions are not received and interpreted properly, time sensitive operations may not be scheduled properly, and/or may interfere with other transmissions, possibly causing operational errors.
  • a controller 110 may facilitate enhanced coordination among multiple APs (e.g., AP 104 and AP 106).
  • the controller 110 may be a central entity or another AP, and may be responsible for configuring and scheduling time sensitive control and data operations across the APs.
  • a wireless TSN (WTSN) management protocol may be used to facilitate enhanced coordination between the APs, which may be referred to as WTSN management clients in such context.
  • the controller 110 may enable device admission control (e.g., control over admitting devices to a WTSN), joint scheduling, network measurements, and other operations.
  • APs may be configured to follow the WTSN protocol.
  • controller 110 may facilitate AP synchronization and alignment for control and data transmissions to ensure latency with high reliability for time sensitive applications on a shared time sensitive data channel, while enabling coexistence with non-time sensitive traffic in the same network.
  • the controller 110 and its coordination may be adopted in future Wi-Fi standards for new bands (e.g., 6-7 GHz), in which additional requirements of time synchronization and scheduled operations may be used.
  • Such application of the controller 110 may be used in managed Wi-Fi deployments (e.g., enterprise, industrial, managed home networks, etc.) in which time sensitive traffic may be steered to a dedicated channel in existing bands as well as new bands.
  • Wi-Fi network may be managed, and that there are no unmanaged Wi-Fi STAs/networks nearby.
  • APs and STAs may synchronize their clocks to a master reference time (e.g., STAs may synchronize to beacons and/or may use time synchronization protocols as defined in the IEEE 802.1 AS standard).
  • controller 110 may include a WTSN management client 112 and a switch 114.
  • the WTSN management client 112 may facilitate execution of a WTSN protocol.
  • the switch 114 may allow for different signals to be transmitted between APs and STAs (e.g., a motion controller and a virtual reality server may both send signals to STAs associated with different APs, and switch 114 may allow for control over such communic ations) .
  • APs and STAs may operate according to a time synchronized scheduled mode that may also apply to new frequency bands (e.g., 6-7 GHz), for which new access protocols and requirements also may be proposed.
  • new frequency bands e.g., 6-7 GHz
  • a WTSN domain may be defined as a set of APs (e.g., AP 104 and AP 106) and STAs (e.g., user devices 124, 126, 128, 130, and 132) that may share dedicated wireless resources, and therefore may need to operate in close coordination, at a level of control and time sensitive data scheduling, to ensure latency and reliability guarantees.
  • APs e.g., AP 104 and AP 106
  • STAs e.g., user devices 124, 126, 128, 130, and 132
  • Different APs in the same network may form different WTSN domains (e.g., AP 104 may form a first WTSN domain, and AP 106 may form a second WTSN domain).
  • AP 104 and AP 106 may communicate with controller 110 through a WTSN management protocol.
  • the WTSN management protocol may be executed over a wired (e.g., Ethernet) TSN infrastructure that may provide TSN grade time synchronization accuracy and latency guarantees.
  • the WTSN management protocol may also be executed using wireless links (e.g., a wireless backhaul, which may include Wi-Fi or WiGig links through one or multiple hops).
  • An Ethernet TSN interface may be replaced by a wireless interface (e.g., and 802.11 MAC and/or physical layer PHY).
  • An operation of a second wireless interface may also be managed by controller 110 to avoid interference with an interface used for communication with time sensitive user STAs (e.g., user devices 126 and 132).
  • controller 110 may reduce the workload of APs by facilitating coordination with other devices, which may be more resource-intensive and time consuming for APs to do by themselves.
  • controller 110 may perform admission control and scheduling tasks.
  • an AP e.g., AP 104
  • AP 104 may forward each STA’s admission control request frame to controller 110, or AP 104 may combine admission requests from multiple STAs into one or more admission requests to send to controller 110.
  • Controller 110 may define which APs may be in a WTSN domain, and may determine the admission of new time sensitive data streams based on, for example, available resources and user requirements.
  • Controller 110 may create and/or update a transmission schedule that may include time sensitive operations and/or non time sensitive operations, and the schedule may be provided to requesting APs.
  • APs may be responsible for executing the schedule according to time sensitive protocols defined, for example, at 802.11 MAC/PHY layers.
  • controller 110 may perform transmission schedule updates.
  • the controller 110 may update a transmission schedule for time sensitive data, and may send transmission schedule updates to APs and/or STAs during network operation.
  • a transmission schedule update may be triggered by changes in wireless channel conditions at different APs and/or STAs within a common WTSN domain.
  • the condition changes may include increased interference, new user traffic requests, and other network and/or operational changes that may affect a WTSN domain.
  • controller 110 may collect measurement data from other devices in a WTSN domain.
  • the measurement data may be collected from time sensitive and/or non-time sensitive devices.
  • Controller 110 may maintain detailed network statistics, for example, related to latency, packet error rates, retransmissions, channel access delay, etc.
  • the network statistics may be collected via measurement reports sent from APs and/or STAs.
  • Controller 110 may use network statistics to proactively manage wireless channel usage to allow for a target latency requirement to be satisfied. For example, measurements may be used to determine potential channel congestion and to trigger a change from a joint transmission schedule mode to a mode in which APs may allocate a same slot to multiple non-interfering STAs that may be leveraging spatial reuse capabilities.
  • the APs 102 may serve as relay nodes for data frames transmitted from a source device (e.g., controller 110) to a destination device (e.g., user devices 124, 126, 128, 130, 132).
  • a source device e.g., controller 110
  • a destination device e.g., user devices 124, 126, 128, 130, 132.
  • the APs 102 may be relay devices configured to communicate TSN synchronous data flows from a wireless communication device to a PLC for carrying out one or more operations in an industrial setting.
  • FIG. 2 depicts an illustrative transmission schedule 200 for multiple APs in a wireless TSN domain, in accordance with one or more example embodiments of the present disclosure.
  • one or more APs 202 may be associated with one or more user devices 210 (e.g., user device 212 and user device 214).
  • APs 202 may communicate with user devices 120 during a beacon interval 216 (e.g., a beacon period), which may be a time period (e.g., 110 x a cycle time).
  • the beacon interval 216 may be divided into slots 218 (e.g., time slot 228, time slot 230, time slot 232, time slot 234, time slot 236) during which beacon, uplink, and downlink transmissions may occur. Some slots 218 may not be allocated for transmissions.
  • transmission schedule 200 may be a joint time sensitive schedule defined by a controller (e.g., controller 110 of FIG. 1) for a WTSN domain.
  • a controller may configure APs 202 to schedule beacon transmissions within a same cycle (e.g., beacon interval 216) using different transmission offsets.
  • time sensitive data transmissions may be scheduled in non-overlapping slots 218 to avoid interference.
  • time sensitive data transmissions may share one or more time slots, but may be separated in a frequency and/or code domain.
  • detailed interference information between STAs may not be required to establish a joint (e.g., interference-free) schedule, but such information may be useful to enhance overall network capacity.
  • a first beacon 220 may be sent from one of the APs 202 (e.g., AP 204) during a time slot 218 of the beacon interval 216.
  • a second beacon 222 may be sent from one of the APs 202 (e.g., AP 206) during the same time slot 218 of the beacon interval 216 in which the first beacon 220 was sent.
  • first beacon 220 may be sent after a first transmission offset 224 that begins at the start of the time slot 218 in which the first beacon 220 is sent
  • the second beacon 222 may be sent after a second transmission offset 226 that may begin at the beginning of the slot 218 in which the second beacon 222 is sent, but the second transmission offset 226 may span beyond the first beacon 220 so that there is a time buffer between the first beacon 220 and the second beacon 222.
  • one or more transmissions may be uplink or downlink transmissions and may include data frames.
  • the transmissions may be allocated for time sensitive devices (e.g., user device 214) and/or non-time sensitive devices (e.g., user device 212). Any combination of scheduled transmissions may be associated with any of the APs 202.
  • any combination of time slots 218 e.g., time slot 228, time slot 230, time slot 232, time slot 234, time slot 236) may be allocated for uplink or downlink transmissions to/from time sensitive and/or non-time sensitive devices.
  • FIG. 3 depicts an illustrative distributed time sensitive coordination architecture 300, in accordance with one or more example embodiments of the present disclosure.
  • a network may include one or more controllers 302 (e.g., controller 304, controller 306), which may form a hierarchical management structure.
  • a lowest level controller e.g., controller 304
  • a next level WTSN controller e.g., controller 306
  • the controllers may exchange schedules and/or other control information with each other.
  • a level and/or granularity of coordination between WTSN domains may decrease as layers increase.
  • Controllers e.g., controller 304, controller 306
  • the controllers may be connected via wired or wireless links.
  • Such a hierarchical management architecture may be useful in large Wi-Fi deployment contexts (e.g., enterprise, industrial spaces, etc.), and may be used to manage operations across multiple unlicensed bands.
  • coordination may be achieved through distributed time sensitive coordination architecture 300 that may use a coordination protocol.
  • the coordination protocol may include a neighboring AP time sensitive operation discovery.
  • APs e.g., AP 312, AP 3114 may include information in their respective beacons (e.g., first beacon 220 and second beacon 222 of FIG. 2) that may indicate whether the APs support a TSN mode.
  • a TSN element may be included in a beacon and/or other control frames to provide the indication that the APs may support a TSN mode.
  • TSN mode information may include dedicated channels for time sensitive data, time synchronization, and scheduling (e.g., a reserved slots bitmap).
  • APs may not be within range of all other neighboring APs.
  • discovery through other devices may be supported using STAs (e.g., STA 316, STA 318, STA 320, STA 322).
  • One or more STAs may relay TSN mode information to a neighboring AP (e.g., STA 318 may inform AP 314 of TSN operations associated with AP 312).
  • the communication of TSN mode information may be scheduled by an AP without interfering with time sensitive data transmissions, for example.
  • the coordination protocol may include a time sensitive scheduling adaptation.
  • an AP may commence a TSN operation in a selected channel (e.g., a channel with the least amount of activity detected). If another TSN-capable AP is detected in the same area (e.g., directly or through a relay STA), a TSN-capable AP may need to ensure that it is synchronized with existing APs (e.g., an AP may be synchronized with a master AP across multiple hops), and may identify a clear, non overlapping channel in which to initiate a TSN operation. If no other channel is available, an AP may define a joint transmission schedule to coexist with a control transmission (e.g., beacon) and time sensitive data transmissions of another AP.
  • a control transmission e.g., beacon
  • the AP may broadcast the schedule information within one or more beacons to enable implementation of the transmission schedule among other neighboring APs.
  • the transmission schedule may be valid after a pre-defined future time to allow for the schedule to be propagated and devices to be configured to implement the schedule. Because time sensitive applications may have known traffic patterns, those traffic patterns may facilitate scheduling updates. For instance, scheduling updates may be made while TSN applications have no data to transmit.
  • the coordination protocol may include a distributed time sensitive negotiation.
  • Neighboring APs may implement a WTSN management layer (e.g., WTSN management client 112 of FIG. 1) on top of a MAC/PHY stack of an AP to enable time synchronization and explicit negotiation between APs to allow for fair utilization of a dedicated time sensitive channel.
  • a token-based protocol for example, may be used to determine a fraction of resources (e.g., channel time) for which each AP may be allowed to reserve resources. The amount of resources to be reserved may be defined based on a number of time sensitive flows managed by each AP.
  • a token redistribution algorithm may be used to adapt a number of available tokens for each AP once new time sensitive flows are admitted by neighboring APs to achieve a fair distribution of resources.
  • a WTSN management protocol may include a cluster formation protocol where an AP may assume a role of a“clusterhead” (e.g., a first AP to initialize a cluster), and other APs may join the cluster or create other clusters.
  • a decision to join a cluster or create a new cluster may be implementation-specific.
  • a size of a cluster may be limited to guarantee enhanced performance.
  • a clusterhead may be responsible for scheduling and coordinating transmissions within a cluster. Clusterheads from neighboring clusters may coordinate on behalf of cluster members according to a management protocol (e.g., as shown in FIG. 4B).
  • FIG. 4A depicts an illustrative timing diagram of a scheduled data flow 400 in an enhanced TSN, in accordance with one or more example embodiments of the present disclosure.
  • an AP 402 may communicate with a controller 404.
  • AP 402 may include a WTSN management client (e.g., WTSN management client 112 of FIG. 1), and controller 404 may be a WTSN controller (e.g., controller 110 of FIG. 1).
  • AP 402 may send an admission request 406 to controller 404.
  • the admission request 406 may include an admission request for an STA (e.g., an STA admission request) associated with the AP.
  • the STA may be a time sensitive device or a non-time sensitive device.
  • controller 404 may send an admission response 408 to AP 402.
  • the admission response 408 may include a transmission schedule, which may include a time sensitive transmission schedule (e.g., a TS_SP_Schedule).
  • controller 404 may send a transmission schedule update 410 to AP 402.
  • the transmission schedule update may include one or more additional scheduled transmission slots or changes to an existing transmission schedule.
  • AP 402 may send an acknowledgment 412 to controller 404 to acknowledge receipt of the transmission schedule update 410.
  • AP 402 may send a measurement report 414 to controller 404.
  • the measurement report 414 may include measurements related to time sensitive devices associated with AP 402.
  • FIG. 4B depicts an illustrative timing diagram of a management frame flow 450 in an enhanced TSN, in accordance with one or more example embodiments of the present disclosure.
  • AP 452 may communicate with AP 454.
  • the communications may include management frame exchanges.
  • AP 452 and AP 454 may exchange TSN information through beacons.
  • AP 452 may send a first TSN information element 456 to AP 454 indicating the TSN capabilities of AP 452.
  • AP 454 may send a second TSN information element 458 indicating the TSN capabilities of AP 454.
  • AP 454 may initiate a negotiation of time sensitive data scheduling by sending, to AP 452, a transmission schedule update request 460 (e.g., TS_SP_Schedule_Update_Request), which may include a number of resources requested based on a number of TS tokens available at AP 454.
  • AP 452 may respond by sending a proposed new schedule, such as a schedule update response 462 (e.g.,
  • AP 454 may send a schedule confirmation 464 to AP 452 to acknowledge that the schedule update response 462 was received.
  • FIG. 5 is a diagram illustrating an enhanced time sensitive network environment 500, in accordance with one or more example embodiments of the present disclosure.
  • AP 502 and AP 504 may exist in one or more WTSN domains.
  • AP 502 may be in communication with STA 506 and STA 508, while AP 504 may be in communication with STA 510 and STA 512.
  • Controller 514 may operate in a specific band/channel within one or each of the APs (e.g., AP 502, AP 504) in an ESS, or may operate externally to the APs.
  • APs in a same ESS may be operating in a same band or in another band, in a same channel or another channel, and may each have its own respective BSS.
  • Controller 514 may operate in a band that allows for long coverage (e.g., covering an entire area where STAs are located).
  • AP 502 and AP 504 may be operating in a band that allows for shorter coverage (e.g., small cells), and may be spread uniformly to allow for blanket coverage of an area with specific frequency planning.
  • STAs may use a dual connection, one connection with a BSS of controller 514 and another connection with a best serving AP (e.g., AP 502, AP 504).
  • STA 508 may be a time sensitive device that communicates directly with controller 514 via channel 516, which may be wireless or wired.
  • STA 506 may be a non-time sensitive device or a legacy device (e.g., a device that does not have multi-band capability to communicate with a controller), which may that communicate with controller 514 indirectly via AP 502, and AP 502 may communicate with controller 514 via channel 518, which may be wireless or wired.
  • STA 510 may be a non-time sensitive device that communicates with controller 514 indirectly via AP 504, and AP 504 may communicate with controller 514 via channel 520, which may be wireless or wired.
  • STA 512 may be a time sensitive device that communicates directly with controller 514 via channel 522, which may be wireless or wired.
  • a dual connectivity framework may be used for communication among devices in a WTSN domain.
  • multi-band STAs may be associated with multiple APs and may implement multi-band features with separate data and control planes. Data traffic may occur on a data plane, and control traffic may occur on a control plane.
  • a non-time sensitive device may communicate with controller 514. Even if a device does not have time sensitive requirements, it may be desirable to enable communication with controller 514.
  • STAs may implement a multi-band separation of a data plane and a control plane on the two connections of a dual connection by interacting with controller 514 for control exchanges that may relate to configuring an operation on the control plane.
  • STAs may interact with APs (e.g., AP 502, AP 504) for data transmissions on the data plane.
  • APs e.g., AP 502, AP 504
  • channel 516, channel 518, channel 520, and/or channel 522 may each include two planes in one or more frequency bands, one plane for data transmissions and one plane for control transmissions.
  • channel 516, channel 518, channel 520, and channel 522 may serve as control channels in one or more frequency bands for control transmissions
  • channel 524, channel 526, channel 528, and channel 530 may serve as data channels for data transmissions.
  • channel 516 and channel 518 may be implemented in a single logical/physical control channel that may be shared by all STAs (e.g., STA 506, STA 508, STA 510, STA 512).
  • channel 516 and channel 518 may be implemented in a single channel within the same frequency band. This way, a data plane and control plane may be implemented in a same logical/physical channel facilitated by a control plane interface 501 and a data plane interface 507 of controller 514.
  • some data transmissions may be multiplexed with control information in a control channel (e.g., channel 516, channel 522).
  • a control channel e.g., channel 516, channel 522.
  • controller 514 may collect measurements directly from STAs (e.g., STA 506, STA 508, STA 510, STA 512) through a control plane (e.g., control interface), and may provide scheduling information directly to STAs through the control plane. For example, rather than sending control signals to the APs (e.g., AP 502 and/or AP 504) to pass along to STAs, controller 514 may bypass APs and send the control signals directly to STAs, thereby eliminating propagation hops that may occur when sending control signals through APs. Controller 514 may send a control signal to STA 508 via channel 516, and may send a control signal to STA 512 via channel 522.
  • STAs e.g., STA 506, STA 508, STA 510, STA 512
  • a control plane e.g., control interface
  • controller 514 may provide transmission schedule information to AP 502 and/or AP 504 through a backhaul or through the control plane. In this manner, even if controller 514 communicates wirelessly with STAs associated with AP 502 and/or AP 504 (e.g., via channel 516 and/or channel 522), controller 514 may use wireless connections with AP 502 and/or AP 504, or may use a wired backhaul (e.g., channel 518 and/or channel 520 may be a wired backhaul or wireless connections).
  • a wired backhaul e.g., channel 518 and/or channel 520 may be a wired backhaul or wireless connections.
  • STAs e.g., STA 506, STA 508, STA 510, STA 512
  • APs e.g., AP 502 and/or AP 504
  • the data plane may be on a band connected with the APs.
  • controller 514 may include a control plane interface 501 that may have a large coverage range (e.g., 2.4 GHZ, 900 MHz, or other bands more favorable for longer range communications).
  • the control plane interface 501 may be used to facilitate the exchange of control information between controller 514 and STAs (e.g., STA 506, STA 508, STA 510, STA 512) in an ESS.
  • control frames may be sent over channel 516 and/or channel 522, which may include one or more control planes.
  • STA 508 may have a control plane interface 503 to facilitate communication of control frames over a control plane of channel 516, for example.
  • STA 512 may have a control plane interface 505 to facilitate communication of control frames over a control plane of channel 522.
  • the communications between controller 514 and APs 502 and/or AP 504 in the ESS may be conducted using a backhaul (e.g., channel 518 and/or channel 520 may include Ethernet, Ethernet TSN, Multimedia over Coaxial Cable, etc.), and/or the control plane may be used to facilitate communications between controller 514 and AP 502 and/or AP 504 (e.g., channel 518 and/or channel 520 may include a control plane).
  • Control information sent over a control plane may include network discovery, synchronization, device association/authentication, admission control, scheduling information, and other control data.
  • AP 502 may have a control plane interface 509 to facilitate communication of control frames.
  • AP 504 may have a control plane interface 511 to facilitate communication of control frames.
  • controller 514 may have a data plane interface 507, which may be used for data plane communication with other APs through a backhaul.
  • the data plane interface 507 may operate in one or more frequency bands.
  • channel 518 and/or channel 520 may be part of a backhaul through which controller 514 may communicate over a data plane with AP 502 and/or AP 504.
  • AP 502 may have a data plane interface 517 to facilitate communication of data frames with STA 508 over channel 524, which may include a data plane.
  • STA 508 may include a data plane interface 513 to facilitate data communications.
  • AP 504 may have a data plane interface 519 to facilitate communication of data frames with STA 512 over channel 528, which may include a data plane.
  • STA 512 may include a data plane interface 515 to facilitate data communications.
  • AP 502 may communicate data and/or control frames to STA 506 over channel 526, which may include a data and/or control plane.
  • AP 504 may communicate data and/or control frames to STA 510 over channel 530, which may include a data and/or control plane.
  • a control plane interface may be used to collect measurements from STAs and to manage interference and coordination of data channel allocations/planning across multiple APs.
  • controller 514 may use control plane interface 501 (e.g., including channel 516 and/or channel 522) to communicate control frames to STAs.
  • the control frames may allow coordination across AP 502 and/or AP 504 to mitigate interference and facilitate data transmissions.
  • STAs may have two communication interfaces, one dedicated for a control plane, and one dedicated for data plane communications.
  • channel 516 and/or channel 522 may be included in a control plane
  • channel 518 and/or channel 520 may be included in a data plane.
  • STAs may have only one configurable interface, which may be used for both control and data communications.
  • control plane interface 503 and data plane interface 513 of STA 508 may be a single interface capable of communicating over a control plane and data plane in separate channels, or over a common channel with both a control plane and data plane.
  • controller 514 may schedule all control and feedback (e.g., reporting) information exchanges in a control channel in a periodic or deterministic pattern.
  • controller 514 may execute a central scheduler for all data plane communications in each data channel (e.g., channel 524, channel 526, channel 528, and/or channel 530).
  • a schedule may be communicated to each AP (e.g., AP 502 and AP 504).
  • the APs may execute the schedule locally (e.g., by enabling trigger-based multi-user transmissions).
  • Controller 514 may coordinate all control and data transmissions to avoid conflicts and interference.
  • a wired backhaul may be replaced by a wireless backhaul.
  • channel 518 and/or channel 520 may be wireless connections.
  • Control information may be exchanged over a control plane interface, and specific AP-related control information may be exchanged through a wireless backhaul that may include channel 518 and/or channel 520.
  • a dedicated control beacon may be sent by controller 514.
  • the dedicated control beacon may be a modified beacon (e.g., modified from another beacon defined in the IEEE 802.11 family of standards), and may include an information element to advertise the availability of a dedicated BSS and a corresponding channel for an exchange of control information.
  • a dedicated control beacon may include a control basic service set identifier (BSSID) field, a control information mode, and a control channel medium access configuration.
  • the control BSSID field may indicate that Control BSS capability is supported.
  • the control information mode may indicate which communication mode may be used for an exchange of control information.
  • the control information mode may include broadcast mode, request mode, and/or scheduled mode. Multiple communication modes may be used simultaneously, depending on a configuration of controller 514.
  • the broadcast mode may include periodic announcements (e.g., controller 514 periodically broadcasts control information).
  • STAs may request control information updates on a dedicated control channel (e.g., channel 516 and/or channel 522).
  • controller 514 may provide a schedule of dedicated control information for a single STA (e.g., a unicast transmission) or for a group of STAs (e.g., a multicast transmission).
  • control channel medium access configuration may include parameters used to configure how controller 514, or a controller in another AP (e.g., AP 502 or AP 504), and STAs may access a control channel (e.g., channel 516 and/or channel 522).
  • a control channel e.g., channel 516 and/or channel 522.
  • EDCA contention-based enhanced distributed channel access
  • scheduled or trigger- based access e.g., time-division or orthogonal frequency/code division multiple access-based
  • a dedicated BSS control channel beacon may be sent from controller 514 to AP 502 and/or AP 504, or by a controller implemented by AP 502 or AP 504.
  • a BSS control information element may be included in regular beacon frames (e.g., first beacon 220 or second beacon 222 of FIG. 2) sent from APs that lack controller functionality.
  • the regular beacon frames may be sent within an ESS to advertise the availability of a dedicated control channel.
  • a control channel association procedure may be implemented.
  • STAs may execute a legacy association procedure through regular APs, and may discover a dedicated control BSS through passive scanning on a control channel or as part of an association procedure.
  • STA 506, STA 508, STA 510, and/or STA 512 may use a legacy association procedure to establish an association with AP 502 and/or AP 504.
  • STAs may include a capability information element to indicate an ability to use a dedicated BSS control channel as part of an association procedure.
  • the STA capability (e.g., capability information element) may be forwarded by an associating AP (e.g., AP 502 or AP 504) to controller 514 via a backhaul (e.g., via channel 518 and/or channel 520).
  • a simplified control BSS association request may be sent by an STA in a control channel to indicate the STA’s capability to use the control channel to receive information directly from controller 514 (e.g., STA 508 may send a control BSS association request via channel 516 to controller 514).
  • the association procedure may include and association request to controller 514 followed by an association response from controller 514, and may include other configuration parameters to enable specific control channel operation (e.g., transmission scheduling).
  • the simplified association procedure using the control channel may leverage security features already configured in a regular association procedure, thereby avoiding the need for significantly additional security overhead.
  • other frame types may be modified for exchange in a control channel, including admission control frames, measurement request/response frames, scheduling/trigger frames, and other types of frames.
  • enhanced time sensitive network coordination may be implemented in next generation standards, such as another version of IEEE 802.1 lax, and enhancements for IEEE 802.1 lax for a 6 GHz band.
  • FIG. 6A illustrates a flow diagram of illustrative process 600 for enhanced time sensitive networking coordination, in accordance with one or more example embodiments of the present disclosure.
  • one or more processors of a device may determine a transmission schedule.
  • the transmission schedule may be received over a control plane interface from a controller device (e.g., controller 110 of FIG. 1).
  • the controller device may be within an AP, or may function as a separate device controlling one or more APs in an ESS.
  • the transmission schedule may include transmission times for time sensitive and/or non-time sensitive devices associated with the AP and one or more other APs that may be associated with the controller.
  • the transmission times for time sensitive devices may support time sensitive operations, while the transmission times for non-time sensitive devices may support non-time sensitive operations. Time sensitive operations may be prioritized over non time sensitive operations (e.g., when a time sensitive transmission is needed, it may be scheduled before a non-time sensitive transmission).
  • the one or more processors of the device may cause the device to send a first data frame.
  • the first data frame may be sent to an STA according to the transmission schedule, and may be sent over a data plane interface.
  • the control plane interface may be a separate channel/band from the data plane interface, or the control plane interface and the data plane interfaces may be within a same physical channel.
  • a data frame may be differentiated from a control frame.
  • a control frame may include frames like beacons, trigger frames, measurement requests/reports, and other control/instruction frames that may facilitate transmission of data frames, while data frames may include data that a device user may see (e.g., data from higher layers than control frames).
  • the first data frame may be a downlink transmission.
  • the one or more processors of the device may identify a second data frame.
  • the second data frame may be received over the data plane interface according to the transmission schedule.
  • the second data frame may be an uplink transmission.
  • the one or more processors of the device may cause the device to send a measurement report to the controller device over the control plane interface.
  • the measurement report may include measurements related to time sensitive devices associated with AP.
  • the measurement report may include information that may allow the controller to use network statistics to proactively manage wireless channel usage to allow for a target latency requirement to be satisfied.
  • FIG. 6B illustrates a flow diagram of illustrative process 650 for enhanced time sensitive networking coordination, in accordance with one or more example embodiments of the present disclosure.
  • one or more processors of a device may determine an admission request.
  • the admission request may be received from an STA (e.g., user device 120) or an AP (e.g., APs 102), and may be received over a control plane interface.
  • STA e.g., user device 120
  • AP e.g., APs 102
  • the one or more processors of the device may cause the device to send an admission response.
  • the admission response may be sent to the device that sent the admission request.
  • the admission request may have been sent from an STA to an associated AP, and the AP may send the admission request on behalf of the STA to the device.
  • the STA may send the admission request to the device directly.
  • the admission response may be sent to an STA via the AP that forwards the admission request, or may be sent directly to the STA.
  • the one or more processors of the device may determine a measurement report.
  • the measurement report may be received over the control plane interface from the device that send the admission request.
  • the measurement report may include measurements related to time sensitive devices associated with AP.
  • the measurement report may include information that may allow the controller to use network statistics to proactively manage wireless channel usage to allow for a target latency requirement to be satisfied.
  • the one or more processors of the device may cause the device to send a data frame.
  • the data frame may be sent to the device that sent the admission request.
  • the data frame may be sent over a data plane interface.
  • the data plane interface may be on a different channel/band from the control plane interface, or may be in a same physical channel as the control plane interface.
  • FIG. 7 shows a functional diagram of an exemplary communication station 700 in accordance with some embodiments.
  • FIG. 7 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 700 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.
  • HDR high data rate
  • the communication station 700 may include communications circuitry 702 and a transceiver 710 for transmitting and receiving signals to and from other communication stations using one or more antennas 701.
  • the communications circuitry 702 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals.
  • the communication station 700 may also include processing circuitry 706 and memory 708 arranged to perform the operations described herein. In some embodiments, the communications circuitry 702 and the processing circuitry 706 may be configured to perform operations detailed in FIGs. 2, 3, 4A, 4B, 5, 6A, and 6B.
  • the communications circuitry 702 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 702 may be arranged to transmit and receive signals (it should be understood that the signals may be transmitted and received simultaneously in some embodiments).
  • the communications circuitry 702 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 706 of the communication station 700 may include one or more processors. In other embodiments, two or more antennas 701 may be coupled to the communications circuitry 702 arranged for sending and receiving signals.
  • the memory 708 may store information for configuring the processing circuitry 706 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 708 may include any type of memory, including non- transitory memory, for storing information in a form readable by a machine (e.g., a computer).
  • the memory 708 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.
  • the communication station 700 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • the communication station 700 may include one or more antennas 701.
  • the antennas 701 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals.
  • a single antenna with multiple apertures may be used instead of two or more antennas.
  • each aperture may be considered a separate antenna.
  • MIMO multiple-input multiple-output
  • the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.
  • the communication station 700 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the communication station 700 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may include one or more microprocessors, DSPs, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio- frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements of the communication station 700 may refer to one or more processes operating on one or more processing elements.
  • Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.
  • a computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer).
  • a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
  • the communication station 700 may include one or more processors and may be configured with instructions stored on a computer-readable storage device memory.
  • FIG. 8 illustrates a block diagram of an example of a machine 800 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed.
  • the machine 800 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine 800 may operate in the capacity of a server machine, a client machine, or both in server-client network environments.
  • the machine 800 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments.
  • P2P peer-to-peer
  • the machine 800 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station.
  • PC personal computer
  • PDA personal digital assistant
  • STB set-top box
  • mobile telephone a wearable computer device
  • web appliance e.g., a web appliance
  • network router e.g., a network router, a switch or bridge
  • any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station.
  • 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 (Sa
  • Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating.
  • a module includes hardware.
  • the hardware may be specifically configured to carry out a specific operation (e.g., hardwired).
  • the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating.
  • the execution units may be a member of more than one module.
  • the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.
  • the machine 800 may include a hardware processor 802 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 804 and a static memory 806, some or all of which may communicate with each other via an interlink (e.g., bus) 808.
  • the machine 800 may further include a power management device 832, a graphics display device 810, an alphanumeric input device 812 (e.g., a keyboard), and a user interface (UI) navigation device 814 (e.g., a mouse).
  • the graphics display device 810, alphanumeric input device 812, and UI navigation device 814 may be a touch screen display.
  • the machine 800 may additionally include a storage device (i.e., drive unit) 816, a signal generation device 818 (e.g., a speaker), an enhanced Network Management device 819, a network interface device/transceiver 820 coupled to antenna(s) 830, and one or more sensors 828, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor.
  • GPS global positioning system
  • the machine 800 may include an output controller 834, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 816 may include a machine readable medium 822 on which is stored one or more sets of data structures or instructions 824 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 824 may also reside, completely or at least partially, within the main memory 804, within the static memory 806, or within the hardware processor 802 during execution thereof by the machine 800.
  • one or any combination of the hardware processor 802, the main memory 804, the static memory 806, or the storage device 816 may constitute machine-readable media.
  • the enhanced network management device 819 may carry out or perform any of the operations and processes (e.g., processes 600 and 650) described and shown above.
  • the enhanced network management device 819 may determine a transmission schedule received over a control plane interface from a controller device, the transmission schedule comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation.
  • the enhanced network management device 819 may cause to send a first data frame, according to the transmission schedule, over a data plane interface.
  • the enhanced network management device 819 may identify a second data frame received over the data plane interface according to the transmission schedule.
  • the enhanced network management device 819 may cause to send a measurement report to the controller device over the control plane interface.
  • the enhanced network management device 819 may cause to send a beacon frame over the control plane interface according to the transmission schedule, the beacon frame indicating that the device supports the time sensitive operation, wherein the second data frame is received over the data plane interface from a time sensitive device according to the transmission schedule.
  • the enhanced network management device 819 may identify a third data frame received from the controller device over the data plane interface. [00159] The enhanced network management device 819 may cause to send an admission request to the controller device on behalf of a time sensitive device.
  • the enhanced network management device 819 may determine an admission request received from a first device over a control plane interface.
  • the enhanced network management device 819 may cause to send an admission response over the control plane interface to the first device, the admission response comprising a transmission schedule, the transmission schedule indicating a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation.
  • the enhanced network management device 819 may determine a measurement report received over the control plane interface from the first device.
  • the enhanced network management device 819 may cause to send a data frame to the first device over a data plane interface.
  • the enhanced network management device 819 may determine an updated transmission schedule based on the measurement report, and may cause to send the updated transmission schedule to the first device over the control plane interface.
  • machine-readable medium 822 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 824.
  • 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 824.
  • Various embodiments may be implemented fully or partially in software and/or firmware.
  • This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein.
  • the instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.
  • machine-readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and that cause the machine 800 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions.
  • Non- limiting machine-readable medium examples may include solid-state memories and optical and magnetic media.
  • a massed machine-readable medium includes a machine -readable medium with a plurality of particles having resting mass.
  • massed machine -readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks.
  • semiconductor memory devices e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)
  • EPROM electrically programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • the instructions 824 may further be transmitted or received over a communications network 826 using a transmission medium via the network interface device/transceiver 820 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), hypertext transfer protocol (HTTP), etc.
  • Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others.
  • the network interface device/transceiver 820 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 826.
  • the network interface device/transceiver 820 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.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
  • the operations and processes e.g., process 600 of FIG. 6A and/or process 650 of FIG. 6B) 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.
  • the word“exemplary” is used herein to mean“serving as an example, instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.
  • the terms“computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,”“wireless device” and“user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device.
  • the device may be either mobile or stationary.
  • the term“communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as“communicating,” when only the functionality of one of those devices is being claimed.
  • the term“communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal.
  • a wireless communication unit which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
  • 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, or some other similar terminology known in the art.
  • An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art.
  • Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.
  • Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an 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 (W
  • Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a single input single output (SISO) 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, e.g., a smartphone, a wireless application protocol (WAP) device, or the
  • 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
  • Example 1 the device comprising memory and processing circuitry configured to: determine a transmission schedule received over a control plane interface from a controller device, the transmission schedule indicating one or more transmission times, the one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the device; cause to send a first data frame, according to the transmission schedule, over a data plane interface; identify a second data frame received over the data plane interface according to the transmission schedule; and cause to send a measurement report to the controller device over the control plane interface.
  • Example 2 may include the device of example 1 and/or some other example herein, wherein the transmission schedule further comprises a third transmission time when the device is to send at least one of a beacon over the control plane interface.
  • Example 3 may include the device of example 1 and/or some other example herein, wherein the memory and processing circuitry are further configured to cause to send a beacon frame over the control plane interface according to the transmission schedule, the beacon frame indicating that the device supports the time sensitive operation, wherein the second data frame is received over the data plane interface from a time sensitive device according to the transmission schedule.
  • Example 4 may include the device of example 1 and/or some other example herein, wherein the control plane interface is a separate interface from the data plane interface.
  • Example 5 may include the device of example 1 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 6 may include the device of example 1 and/or some other example herein, wherein the device is a first access point, and wherein the memory and processing circuitry are further configured to cause to send a frame to a second access point of the multiple devices, the frame comprising an indication of the transmission schedule.
  • Example 7 may include the device of example 1 and/or some other example herein, wherein the memory and processing circuitry are further configured to cause to send an admission request to the controller device on behalf of a time sensitive device.
  • Example 8 may include the device of example 1 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals
  • Example 9 may include the device of example 8 and/or some other example herein, further comprising one or more antennas coupled to the transceiver.
  • Example 10 may include a non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: determining, at a controller device, an admission request received from a first device over a control plane interface; causing to send an admission response over the control plane interface to the first device, the admission response comprising a transmission schedule, the transmission schedule indicating one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the first device; determining a measurement report received over the control plane interface from the first device; and causing to send a data frame to the first device over a data plane interface.
  • Example 11 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the first device is an access point, and wherein the admission request is sent by the access point on behalf of a station device.
  • Example 12 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the first device is a station device, and wherein the operations further comprise causing to send a frame in the control plane interface to the station device.
  • Example 13 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the control plane interface is a different plane than the data plane interface.
  • Example 14 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 15 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise: determining an updated transmission schedule based on the measurement report; and causing to send the updated transmission schedule to the first device over the control plane interface.
  • Example 16 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the first device is an access point, and wherein the measurement report was provided by a station device associated with the access point.
  • Example 17 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the first device is a station device associated with an access point, and wherein the access point is associated with the controller device.
  • Example 18 may include a method comprising: identifying, by one or more processors of a first device, a transmission schedule received over a control plane interface from a second device, the transmission schedule indicating one or more transmission times, the one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the first device; causing to send, by the one or more processors, a first data frame, according to the transmission schedule, over a data plane interface; identifying, by the one or more processors, a second data frame received over the data plane interface according to the transmission schedule; and causing to send, by the one or more processors, a measurement report to the second device over the control plane interface.
  • Example 19 may include the method of example 18 and/or some other example herein, wherein the control plane interface is a separate interface from the data plane interface.
  • Example 20 may include the method of example 18 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 21 may include the method of example 18 and/or some other example herein, further comprising identifying a control frame received from the second device over the control plane interface.
  • Example 22 may include the method of example 18 and/or some other example herein, wherein the second device is a controller device, the method further comprising causing to send to the controller device an admission request.
  • Example 23 may include the method of example 18 and/or some other example herein, wherein the second device is an access point of the multiple devices, wherein the access point is associated with a controller device, and the method further comprising causing to send to the second device an admission request associated with the controller device.
  • Example 24 may include the method of example 18 and/or some other example herein, further comprising determining an updated transmission schedule received from the controller device.
  • Example 25 may include the method of example 18 and/or some other example herein, wherein the control plane interface is in a longer range channel than the data plane interface.
  • Example 26 may include an apparatus comprising means for performing a method as claimed in any one of examples 18-25.
  • Example 27 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 18-25.
  • Example 28 may include a machine-readable medium including code, when executed, to cause a machine to perform the method of any one of examples 18-25.
  • Example 29 may include a method comprising: determining a transmission schedule received over a control plane interface from a controller device, the transmission schedule indicating one or more transmission times, the one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the device; causing to send a first data frame, according to the transmission schedule, over a data plane interface; identifying a second data frame received over the data plane interface according to the transmission schedule; and causing to send a measurement report to the controller device over the control plane interface.
  • Example 30 may include the method of example 29 and/or some other example herein, wherein the transmission schedule further comprises a third transmission time when the device is to send at least one of a beacon over the control plane interface.
  • Example 31 may include the method of example 29 and/or some other example herein, further comprising causing to send a beacon frame over the control plane interface according to the transmission schedule, the beacon frame indicating that the device supports the time sensitive operation, wherein the second data frame is received over the data plane interface from a time sensitive device according to the transmission schedule.
  • Example 32 may include the method of example 29 and/or some other example herein, wherein the control plane interface is a separate interface from the data plane interface.
  • Example 33 may include the method of example 29 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 34 may include the method of example 29 and/or some other example herein, wherein the device is a first access point, and wherein the memory and processing circuitry are further configured to cause to send a frame to a second access point of the multiple devices, the frame comprising an indication of the transmission schedule.
  • Example 35 may include the method of example 29 and/or some other example herein, further comprising causing to send an admission request to the controller device on behalf of a time sensitive device.
  • Example 36 may include an apparatus comprising means for performing a method as claimed in any one of examples 29-35.
  • Example 37 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 29-35.
  • Example 38 may include a machine-readable medium including code, when executed, to cause a machine to perform the method of any one of examples 29-35.
  • Example 39 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: determining a transmission schedule received over a control plane interface from a controller device, the transmission schedule indicating one or more transmission times, the one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the device; causing to send a first data frame, according to the transmission schedule, over a data plane interface; identifying a second data frame received over the data plane interface according to the transmission schedule; and causing to send a measurement report to the controller device over the control plane interface.
  • Example 40 may include the non- transitory computer-readable medium of example 39 and/or some other example herein, wherein the transmission schedule further comprises a third transmission time
  • Example 41 may include the non- transitory computer-readable medium of example 39 and/or some other example herein, wherein the memory and processing circuitry are further configured to cause to send a beacon frame over the control plane interface according to the transmission schedule, the beacon frame indicating that the device supports the time sensitive operation, wherein the second data frame is received over the data plane interface from a time sensitive device according to the transmission schedule.
  • Example 42 may include the non- transitory computer-readable medium of example 39 and/or some other example herein, wherein the control plane interface is a separate interface from the data plane interface.
  • Example 43 may include the non- transitory computer-readable medium of example 39 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 44 may include the non-transitory computer-readable medium of example 39 and/or some other example herein, wherein the device is a first access point, and wherein the memory and processing circuitry are further configured to cause to send a frame to a second access point of the multiple devices, the frame comprising an indication of the transmission schedule.
  • Example 45 may include the non-transitory computer-readable medium of example 39 and/or some other example herein, wherein the memory and processing circuitry are further configured to cause to send an admission request to the controller device on behalf of a time sensitive device.
  • Example 46 may include an apparatus comprising means for: means for determining a transmission schedule received over a control plane interface from a controller device, the transmission schedule indicating one or more transmission times, the one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the device; means for causing to send a first data frame, according to the transmission schedule, over a data plane interface; means for identifying a second data frame received over the data plane interface according to the transmission schedule; and means for causing to send a measurement report to the controller device over the control plane interface.
  • Example 47 may include the apparatus of example 46 and/or some other example herein, wherein the transmission schedule further comprises a third transmission time when the device is to send at least one of a beacon over the control plane interface.
  • Example 48 may include the apparatus of example 46 and/or some other example herein, further comprising means for causing to send a beacon frame over the control plane interface according to the transmission schedule, the beacon frame indicating that the device supports the time sensitive operation, wherein the second data frame is received over the data plane interface from a time sensitive device according to the transmission schedule.
  • Example 49 may include the apparatus of example 46 and/or some other example herein, wherein the control plane interface is a separate interface from the data plane interface.
  • Example 50 may include the apparatus of example 46 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 51 may include the apparatus of example 46 and/or some other example herein, wherein the device is a first access point, and wherein the memory and processing circuitry are further configured to cause to send a frame to a second access point of the multiple devices, the frame comprising an indication of the transmission schedule.
  • Example 52 may include the apparatus of example 46 and/or some other example herein, further comprising means for causing to send an admission request to the controller device on behalf of a time sensitive device.
  • Example 53 the device comprising memory and processing circuitry configured to: determining, at a controller device, an admission request received from a first device over a control plane interface; causing to send an admission response over the control plane interface to the first device, the admission response comprising a transmission schedule, the transmission schedule indicating one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the first device; determining a measurement report received over the control plane interface from the first device; and causing to send a data frame to the first device over a data plane interface.
  • Example 54 may include the device of example 53 and/or some other example herein, wherein the first device is an access point, and wherein the admission request is sent by the access point on behalf of a station device.
  • Example 55 may include the device of example 53 and/or some other example herein, wherein the first device is a station device, and wherein the operations further comprise causing to send a frame in the control plane interface to the station device.
  • Example 56 may include the device of example 53 and/or some other example herein, wherein the control plane interface is a different plane than the data plane interface.
  • Example 57 may include the device of example 53 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 58 may include the device of example 53 and/or some other example herein, wherein the memory and processing circuitry are further configured to: determine an updated transmission schedule based on the measurement report; and cause to send the updated transmission schedule to the first device over the control plane interface.
  • Example 59 may include the device of example 53 and/or some other example herein, wherein the first device is an access point, and wherein the measurement report was provided by a station device associated with the access point.
  • Example 60 may include the device of example 53 and/or some other example herein, wherein the first device is a station device associated with an access point, and wherein the access point is associated with the controller device.
  • Example 61 may include the device of example 53 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals.
  • Example 62 may include the device of example 61 and/or some other example herein, further comprising one or more antennas coupled to the transceiver.
  • Example 63 may include a method comprising: determining, at a controller device, an admission request received from a first device over a control plane interface; causing to send an admission response over the control plane interface to the first device, the admission response comprising a transmission schedule, the transmission schedule indicating one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the first device; determining a measurement report received over the control plane interface from the first device; and causing to send a data frame to the first device over a data plane interface.
  • Example 64 may include the method of example 63 and/or some other example herein, wherein the first device is an access point, and wherein the admission request is sent by the access point on behalf of a station device.
  • Example 65 may include the method of example 63 and/or some other example herein, wherein the first device is a station device, and wherein the operations further comprise causing to send a frame in the control plane interface to the station device.
  • Example 66 may include the method of example 63 and/or some other example herein, wherein the control plane interface is a different plane than the data plane interface.
  • Example 67 may include the method of example 63 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 68 may include the method of example 63 and/or some other example herein, further comprising: determining an updated transmission schedule based on the measurement report; and causing to send the updated transmission schedule to the first device over the control plane interface.
  • Example 69 may include the method of example 63 and/or some other example herein, wherein the first device is an access point, and wherein the measurement report was provided by a station device associated with the access point.
  • Example 70 may include the method of example 63 and/or some other example herein, wherein the first device is a station device associated with an access point, and wherein the access point is associated with the controller device.
  • Example 71 may include an apparatus comprising means for performing a method as claimed in any one of examples 63-70.
  • 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 63-70.
  • 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 63-70.
  • Example 74 may include an apparatus comprising: means for determining, at a controller device, an admission request received from a first device over a control plane interface; means for causing to send an admission response over the control plane interface to the first device, the admission response comprising a transmission schedule, the transmission schedule indicating one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the first device; means for determining a measurement report received over the control plane interface from the first device; and means for causing to send a data frame to the first device over a data plane interface.
  • Example 75 may include the apparatus of example 74 and/or some other example herein, wherein the first device is an access point, and wherein the admission request is sent by the access point on behalf of a station device.
  • Example 76 may include the apparatus of example 74 and/or some other example herein, wherein the first device is a station device, and wherein the operations further comprise causing to send a frame in the control plane interface to the station device.
  • Example 77 may include the apparatus of example 74 and/or some other example herein, wherein the control plane interface is a different plane than the data plane interface.
  • Example 78 may include the apparatus of example 74 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 79 may include the apparatus of example 74 and/or some other example herein, further comprising: means for determining an updated transmission schedule based on the measurement report; and means for causing to send the updated transmission schedule to the first device over the control plane interface.
  • Example 80 may include the apparatus of example 74 and/or some other example herein, wherein the first device is an access point, and wherein the measurement report was provided by a station device associated with the access point.
  • Example 81 may include the apparatus of example 74 and/or some other example herein, wherein the first device is a station device associated with an access point, and wherein the access point is associated with the controller device.
  • Example 82 the device comprising memory and processing circuitry configured to: identify, by one or more processors of a first device, a transmission schedule received over a control plane interface from a second device, the transmission schedule indicating one or more transmission times, the one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the first device; cause to send, by the one or more processors, a first data frame, according to the transmission schedule, over a data plane interface; identify, by the one or more processors, a second data frame received over the data plane interface according to the transmission schedule; and cause to send, by the one or more processors, a measurement report to the second device over the control plane interface.
  • Example 83 may include the device of example 82 and/or some other example herein, wherein the control plane interface is a separate interface from the data plane interface.
  • Example 84 may include the device of example 1 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 85 may include the device of example 1 and/or some other example herein, wherein the memory and processing circuitry are further configured to identify a control frame received from the second device over the control plane interface.
  • Example 86 may include the device of example 1 and/or some other example herein, wherein the second device is a controller device, the method further comprising causing to send to the controller device an admission request.
  • Example 87 may include the device of example 1 and/or some other example herein, wherein the second device is an access point of the multiple devices, wherein the access point is associated with a controller device, and the method further comprising causing to send to the second device an admission request associated with the controller device.
  • Example 88 may include the device of example 1 and/or some other example herein, wherein the memory and processing circuitry are further configured to determine an updated transmission schedule received from the controller device.
  • Example 89 may include the device of example 1 and/or some other example herein, wherein the control plane interface is in a longer range channel than the data plane interface.
  • Example 90 may include the device of example 82 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals.
  • Example 91 may include the device of example 90 and/or some other example herein, further comprising one or more antennas coupled to the transceiver.
  • Example 92 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 of a first device, a transmission schedule received over a control plane interface from a second device, the transmission schedule indicating one or more transmission times, the one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the first device; causing to send, by the one or more processors, a first data frame, according to the transmission schedule, over a data plane interface; identifying, by the one or more processors, a second data frame received over the data plane interface according to the transmission schedule; and causing to send, by the one or more processors, a measurement report to the second device over the control plane interface.
  • Example 93 may include the non-transitory computer-readable medium of example 92 and/or some other example herein, wherein the control plane interface is a separate interface from the data plane interface.
  • Example 94 may include the non-transitory computer-readable medium of example 92 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 95 may include the non-transitory computer-readable medium of example 92 and/or some other example herein, wherein the operations further comprise identifying a control frame received from the second device over the control plane interface.
  • Example 96 may include the non-transitory computer-readable medium of example 92 and/or some other example herein, wherein the second device is a controller device, the method further comprising causing to send to the controller device an admission request.
  • Example 97 may include the non-transitory computer-readable medium of example 92 and/or some other example herein, wherein the second device is an access point of the multiple devices, wherein the access point is associated with a controller device, and the method further comprising causing to send to the second device an admission request associated with the controller device.
  • Example 98 may include the non-transitory computer-readable medium of example 92 and/or some other example herein, wherein the operations further comprise determining an updated transmission schedule received from the controller device.
  • Example 99 may include the non-transitory computer-readable medium of example 92 and/or some other example herein, wherein the control plane interface is in a longer range channel than the data plane interface.
  • Example 100 may include an apparatus comprising: means for identifying, by one or more processors of a first device, a transmission schedule received over a control plane interface from a second device, the transmission schedule indicating one or more transmission times, the one or more transmission times comprising a first transmission time for a time sensitive operation and a second transmission time for a non-time sensitive operation, the time sensitive operation having a higher priority than the non-time sensitive operation, the one or more transmission times governing transmissions of multiple devices of an extended service set, the multiple devices comprising the first device; means for causing to send, by the one or more processors, a first data frame, according to the transmission schedule, over a data plane interface; means for identifying, by the one or more processors, a second data frame received over the data plane interface according to the transmission schedule; and means for causing to send, by the one or more processors, a measurement report to the second device over the control plane interface.
  • Example 101 may include the apparatus of example 100 and/or some other example herein, wherein the control plane interface is a separate interface from the data plane interface.
  • Example 102 may include the apparatus of example 100 and/or some other example herein, wherein the control plane interface and the data plane interface are in a common channel.
  • Example 103 may include the apparatus of example 100 and/or some other example herein, further comprising means for identifying a control frame received from the second device over the control plane interface.
  • Example 104 may include the apparatus of example 100 and/or some other example herein, wherein the second device is a controller device, the method further comprising causing to send to the controller device an admission request.
  • Example 105 may include the apparatus of example 100 and/or some other example herein, wherein the second device is an access point of the multiple devices, wherein the access point is associated with a controller device, and the method further comprising causing to send to the second device an admission request associated with the controller device.
  • Example 106 may include the apparatus of example 100 and/or some other example herein, further comprising means for determining an updated transmission schedule received from the controller device.
  • Example 107 may include the apparatus of example 100 and/or some other example herein, wherein the control plane interface is in a longer range channel than the data plane interface.
  • Example 108 may include an apparatus comprising means for performing a method as claimed in any of the preceding examples.
  • Example 109 may include machine-readable storage including machine-readable instructions, when executed, to implement a method as claimed in any preceding example.
  • Example 110 may include machine-readable storage including machine-readable instructions, when executed, to implement a method or realize an apparatus as claimed in any preceding example.
  • Example 111 may include a method of communicating in a wireless network as shown and described herein.
  • Example 112 may include a system for providing wireless communication as shown and described herein.
  • Example 113 may include a device for providing wireless communication as shown and described herein.
  • Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well.
  • the dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims.
  • These computer-executable program instructions may be loaded onto a special- purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks.
  • These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks.
  • certain implementations may provide for a computer program product, comprising a computer- readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.
  • blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.
  • Conditional language such as, among others,“can,”“could,”“might,” or“may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

Landscapes

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

Abstract

La présente invention concerne des systèmes, des procédés, et des appareils relatifs à la coordination d'un réseau sans fil chronosensible. Le dispositif peut déterminer un programme de transmission. Le dispositif peut envoyer une première trame de données. Le dispositif peut identifier une seconde trame de données. Le dispositif peut envoyer un rapport de mesurage.
PCT/US2017/068438 2017-12-26 2017-12-26 Coordination améliorée de réseau chronosensible pour des transmissions sans fil WO2019132861A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/US2017/068438 WO2019132861A1 (fr) 2017-12-26 2017-12-26 Coordination améliorée de réseau chronosensible pour des transmissions sans fil
CN201780095118.9A CN111133825A (zh) 2017-12-26 2017-12-26 用于无线传输的增强型时间敏感网络协调

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2017/068438 WO2019132861A1 (fr) 2017-12-26 2017-12-26 Coordination améliorée de réseau chronosensible pour des transmissions sans fil

Publications (1)

Publication Number Publication Date
WO2019132861A1 true WO2019132861A1 (fr) 2019-07-04

Family

ID=67064079

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/068438 WO2019132861A1 (fr) 2017-12-26 2017-12-26 Coordination améliorée de réseau chronosensible pour des transmissions sans fil

Country Status (2)

Country Link
CN (1) CN111133825A (fr)
WO (1) WO2019132861A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020067966A1 (fr) * 2018-09-27 2020-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil d'interfonctionnement entre réseaux de communication sans fil et filaires
WO2021008385A1 (fr) * 2019-07-12 2021-01-21 华为技术有限公司 Procédé de planification de rapport de service de sensibilité à retard temporel et procédé de rapport de service de sensibilité à retard temporel
WO2021147090A1 (fr) * 2020-01-23 2021-07-29 华为技术有限公司 Procédé de synchronisation temporelle, dispositif de réseau d'accès, appareil de communication, support de stockage informatique et système de communication
CN114071768A (zh) * 2020-08-07 2022-02-18 大唐移动通信设备有限公司 一种时间同步方法、装置及存储介质
WO2022047668A1 (fr) * 2020-09-02 2022-03-10 Qualcomm Incorporated Amélioration de la transmission de liaison montante avec des données sensibles au temps de survie ou sensibles au retard

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111314228B (zh) * 2020-05-11 2020-08-11 之江实验室 一种支持时间敏感网络功能的plc控制系统
CN113709802A (zh) * 2020-05-21 2021-11-26 维沃移动通信有限公司 支持数据传输的方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140148180A1 (en) * 2002-05-23 2014-05-29 Interdigital Technology Corporation Signaling connection admission control in a wireless network
US20150372934A1 (en) * 2013-10-15 2015-12-24 National Instruments Corporation Switch for Scheduled Time-Sensitive Data Egress
EP2774348B1 (fr) * 2011-11-03 2017-04-26 Marvell World Trade Ltd. Procédé et appareil d'arbitrage de transmissions de données sensibles au temps
US20170272366A1 (en) * 2016-03-21 2017-09-21 General Electric Company Communication system and method for controlling data distribution quality of service in time sensitive networks

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7933247B2 (en) * 2004-11-18 2011-04-26 Sanjay M. Gidwani Real-time scalable wireless switching network
WO2006057815A1 (fr) * 2004-11-18 2006-06-01 Sanjay Gidwani Reseau de commutation sans fil evolutif en temps reel
US7787416B2 (en) * 2004-11-18 2010-08-31 Gidwani Sanjay M Wireless network having real-time channel allocation
US20130322275A1 (en) * 2012-05-31 2013-12-05 Telefonaktiebolaget L M Ericsson (Publ) Monitoring and allocation of interface resources in a wireless communication system
CN105637923B (zh) * 2013-08-19 2019-09-20 诺基亚通信公司 无线电接入网（ran）传输演进分组核心（epc）协同作用
JP6496740B2 (ja) * 2013-09-26 2019-04-03 コーヒレント・ロジックス・インコーポレーテッド 次世代放送システム及び方法
CN107113229B (zh) * 2014-12-27 2019-11-29 华为技术有限公司 一种通告消息处理方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140148180A1 (en) * 2002-05-23 2014-05-29 Interdigital Technology Corporation Signaling connection admission control in a wireless network
EP2774348B1 (fr) * 2011-11-03 2017-04-26 Marvell World Trade Ltd. Procédé et appareil d'arbitrage de transmissions de données sensibles au temps
US20150372934A1 (en) * 2013-10-15 2015-12-24 National Instruments Corporation Switch for Scheduled Time-Sensitive Data Egress
US20170272366A1 (en) * 2016-03-21 2017-09-21 General Electric Company Communication system and method for controlling data distribution quality of service in time sensitive networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NARESH GANESH NAYAK ET AL.: "Time-sensitive Software-defined Networks for Real-time Applications", TECHNICAL REPORT 2016/ 03- INSTITUTE OF PARALLEL AND DISTRIBUTED SYSTEMS, May 2016 (2016-05-01), pages 4, 12 - 14-16, XP055622966 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020067966A1 (fr) * 2018-09-27 2020-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil d'interfonctionnement entre réseaux de communication sans fil et filaires
WO2021008385A1 (fr) * 2019-07-12 2021-01-21 华为技术有限公司 Procédé de planification de rapport de service de sensibilité à retard temporel et procédé de rapport de service de sensibilité à retard temporel
WO2021147090A1 (fr) * 2020-01-23 2021-07-29 华为技术有限公司 Procédé de synchronisation temporelle, dispositif de réseau d'accès, appareil de communication, support de stockage informatique et système de communication
CN114071768A (zh) * 2020-08-07 2022-02-18 大唐移动通信设备有限公司 一种时间同步方法、装置及存储介质
CN114071768B (zh) * 2020-08-07 2024-04-09 大唐移动通信设备有限公司 一种时间同步方法、装置及存储介质
WO2022047668A1 (fr) * 2020-09-02 2022-03-10 Qualcomm Incorporated Amélioration de la transmission de liaison montante avec des données sensibles au temps de survie ou sensibles au retard

Also Published As

Publication number Publication date
CN111133825A (zh) 2020-05-08

Similar Documents

Publication Publication Date Title
US20180132234A1 (en) Enhanced wireless networks for time sensitive applications
US20180184438A1 (en) Persistent scheduling and forwarding while receiving in wireless time sensitive networks
WO2019132861A1 (fr) Coordination améliorée de réseau chronosensible pour des transmissions sans fil
US20180184422A1 (en) Multi-channel time synchronized mesh networking
WO2019125396A1 (fr) Mise en réseau améliorée sensible au temps pour des communications sans fil
US20220060991A1 (en) Multicast wakeup in wireless networks
US20210075675A1 (en) Enhanced network architecture in wirless communications
US20180054724A1 (en) Device discovery during link aggregation in wireless communications
US10708720B2 (en) Enhanced location service negotiation
US10492165B2 (en) Enhanced collaborating timing measurements for wireless communications
US20210274502A1 (en) Enhanced high efficiency frames for wireless communications
US10757561B2 (en) Wi-Fi docking in dense environment
US20180054794A1 (en) Enhanced location determination of wireless devices
WO2018182688A1 (fr) Accès déterministe basé sur un déclencheur dans des réseaux wi-fi de nouvelle génération synchronisés dans le temps
CN110024461B (zh) 同步下行链路传输协调
US10750467B2 (en) Bidirectional location measurement report feedback
CN113544993A (zh) 用于定向车联网(v2x)的带有交错的增强型发现资源配置
US20180097605A1 (en) Resource Pre-Allocation and Opportunistic Full-Duplex Downlink Transmission for Wireless Communication
US20220287049A1 (en) Access point configured for signaling configuration and resource allocation inside a synchronized transmission opportunity (s-txop)
US20220338260A1 (en) Communication within synchronized transmission opportunities (s-txops) using short preamble
US20230143575A1 (en) Enhancements to wi-fi devices for enabling cyclic time-sensitive applications with very short cycle times
US10461828B2 (en) Millimeter wave distributed network antenna sector switch
US10448437B2 (en) Enhanced bluetooth channel establishment
WO2019132868A1 (fr) Attribution de ressources hiérarchique
WO2018231734A1 (fr) Attribution d'identification de point d'accès dans un environnement coopératif

Legal Events

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

Ref document number: 17936548

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17936548

Country of ref document: EP

Kind code of ref document: A1