[go: up one dir, main page]

WO2018200038A1 - Dispositif, procédé et système pour mettre en œuvre un mécanisme de réduction de puissance opportuniste pour convergence de trafic dans des réseaux sensibles au temps basés sur wi-fi - Google Patents

Dispositif, procédé et système pour mettre en œuvre un mécanisme de réduction de puissance opportuniste pour convergence de trafic dans des réseaux sensibles au temps basés sur wi-fi Download PDF

Info

Publication number
WO2018200038A1
WO2018200038A1 PCT/US2017/068822 US2017068822W WO2018200038A1 WO 2018200038 A1 WO2018200038 A1 WO 2018200038A1 US 2017068822 W US2017068822 W US 2017068822W WO 2018200038 A1 WO2018200038 A1 WO 2018200038A1
Authority
WO
WIPO (PCT)
Prior art keywords
tsn
period
txoffset
category
edca
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2017/068822
Other languages
English (en)
Inventor
Dave Cavalcanti
Laurent Cariou
Vallabhajosyula S. Somayazulu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
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 Individual filed Critical Individual
Publication of WO2018200038A1 publication Critical patent/WO2018200038A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • Embodiments generally relate to the management of wireless networks.
  • embodiments generally relate to controlling contention-based wireless traffic in the context of converging Time Sensitive Network (TSN) frames with Wireless Local Area Network (WLAN) frames.
  • TSN Time Sensitive Network
  • WLAN Wireless Local Area Network
  • Time Sensitive Networks aim to ensure time synchronization and timeliness with respect to critical data flows while taking into consideration deterministic latencies, reliability and traffic redundancies.
  • TSNs may include networks where the data traffic is compliant with the Institute of Electrical and Electronics Engineers (IEEE) 802.1 standards.
  • IEEE Institute of Electrical and Electronics Engineers
  • TSNs have many use cases, some of which involve Internet of Things (IoT) verticals such as Industrial Internet (e.g. involving process control, autonomous machines, etc.); automotive applications (e.g. involving in-vehicle instrumentation, control and infotainment); utility networks; building automation, consumer audio and video applications, professional audio and video applications, and wireless Virtual Reality (VR), to name just a few.
  • IoT Internet of Things
  • Industrial Internet e.g. involving process control, autonomous machines, etc.
  • automotive applications e.g. involving in-vehicle instrumentation, control and infotainment
  • utility networks building automation, consumer audio and video applications
  • TSN networks require deterministic, synchronized communication to address the tight latency requirements that define them.
  • non-TSN Wi-Fi devices may be at a disadvantage with respect to accessing the wireless medium in light of having to defer to the TSN traffic.
  • Such disadvantage can result in collisions, added latencies to the Wi-Fi converged network communications, and overall network inefficiencies.
  • Fig. 1 illustrates a Wi-Fi converged network including TSN and non-TSN devices in accordance with some demonstrative embodiments
  • FIG. 2 illustrates a radio system of a STA or an AP from the network of Fig. 1 in accordance with some demonstrative embodiments
  • FIG. 3 illustrates signaling in a scheduled converged TSN network similar to the network of Fig. 1 ;
  • Fig. 4 illustrates a signaling diagram showing communications from a TSN
  • Fig. 5 illustrates a signaling diagram showing communications in a scheduled converged network such as the network of Fig. 1, and including an opportunistic backoff mechanism according to one demonstrative embodiment
  • FIG. 6 illustrates a flow-chart of a method according to some demonstrative embodiments.
  • Fig. 7 illustrates a product of manufacture in accordance with some demonstrative embodiments.
  • TSN applications typically use wired connectivity, such as by way of a number of well-known proprietary wired protocols, although emerging standards are aiming to enable the use of TSNs over Ethernet. Wired connectivity is often not suitable for TSN applications, which applications tend to require control of fast-moving or rotating objects.
  • wireless technologies such as the wireless technology set forth in the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4e standard, or cellular standards, such as the third generation of wireless mobile telecommunications technology (3G), or the fourth generation of wireless mobile telecommunications technology (4G), do not have the speed or capacity required to meet the latency (low) and reliability (high) requirements in a converged environment involving both cellular and TSN traffic.
  • Wi-Fi is a potential candidate to enable cost-effective deployment of wireless TSNs, especially given increasing data rates supported by standards such as IEEE 802.11ac and 802. Had which enable Gigabit per second data transmission rates.
  • the proposed enhancements for Wi-Fi may also be applicable to future protocols designed within the 5G family of standards.
  • Wi-Fi is primarily a contention-based access system, with inherent randomness with respect to channel access. This randomness makes Wi-Fi difficult to apply to applications such as TSN which require a guarantee with respect to bounded latencies.
  • TSN applications include a mix of traffic patterns and requirements, for example from critical synchronous data flows (e.g. from sensor to a controller in a closed loop control system), to asynchronous events (e.g. a sensor detecting an anomaly in the monitored process and sending a report to a controller soon thereafter), to video streaming for virtual/augmented reality, remote asset monitoring and control.
  • critical synchronous data flows e.g. from sensor to a controller in a closed loop control system
  • asynchronous events e.g. a sensor detecting an anomaly in the monitored process and sending a report to a controller soon thereafter
  • video streaming for virtual/augmented reality, remote asset monitoring and control.
  • TSN requirements may be summarized as follows: (1) precise time synchronization, from the nanosecond (ns or nsec) to the millisecond (ms or msec) range, although 1 msec is expected to enable most TSN applications (or for example, from 10 ⁇ ec to 10 msec, with 1 msec being a good target for the majority of applications); (2) deterministic/bounded end-to-end delivery latency, with maximum and minimum latency from source to destination defined (for example, a maximum latency allowed in the latency ranges provided above, along with a maximum allowed jitter of 10 ⁇ 8 ⁇ ), keeping in mind that average, mean or typical values would be of no interest; (3) extremely low packet loss probability, such as, for example, a packet loss probability lower than about 10 "5 , which requires highly reliable links and devices; and (4) convergence, with sufficient capacity for critical streams and other traffic on a single network.
  • next generation wireless networks will need to support the convergence TSN and non-TSN applications, such as, for example, non-TSN applications that rely on typical Access Categories in Wi-Fi including video, voice, best effort, and background to gain access to the wireless medium of the converged network (i.e. the network including the TSN network and the non-TSN Wi-Fi network).
  • non-TSN applications that rely on typical Access Categories in Wi-Fi including video, voice, best effort, and background to gain access to the wireless medium of the converged network (i.e. the network including the TSN network and the non-TSN Wi-Fi network).
  • Embodiments will be described below with respect to Figs. 1-3 and 5-7 to enable efficient convergence of TSN operations with non-TSN operations in a Wi-Fi network. It is to be noted that embodiments are not limited to what is described and shown herein with respect to Figs. 1-3 and 5-7.
  • FIG. 1 is a diagram illustrating an example network environment, such as a
  • Wireless network 100 may include one or more wireless stations (STAs) including a number of TSN STAs, that is, TSN STA 1, TSN STA 2, and TSN STA 3, a number of non-TSN STAs, such as non-TSN STA 4 and non-TSN STA 5, and, in addition, one or more access point(s) AP, such as AP 104, which may communicate in accordance with various communication standards and protocols, such as, Wi-Fi, IEEE 802.15.4 low-rate Wireless Personal Area Networks (WPAN), Wireless Universal Serial Bus, Wi-Fi Peer-to-Peer (P2P), Bluetooth, Near Field Communication, or any other communication standard.
  • STAs wireless stations
  • WLAN Wireless Universal Serial Bus
  • P2P Wi-Fi Peer-to-Peer
  • Bluetooth Near Field Communication
  • the TSN STAs may all include stationary devices in a fixed environment.
  • the TSN STAs may be configured to communicate using TSN frames.
  • the TSN STAs as shown in Fig. 1 may include IoT devices, such as sensors, actuators, gauges and mobile devices as a few examples.
  • AP 104 may be connected to a Programmable Logic Controller (PLC) which forms part of the core network or backbone (Extended Service Set or ESS) including AP 104.
  • PLC Programmable Logic Controller
  • IoT Internet of Things
  • IP Internet protocol
  • ID Bluetooth identifier
  • NFC near-field communication
  • An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like.
  • QR quick response
  • RFID radio-frequency identification
  • An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet.
  • a device state or status such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.
  • CPU central processing unit
  • ASIC application specific integrated circuitry
  • IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network.
  • IoT devices may also include slot phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc.
  • the STAs and AP 104 of Fig. 1 may include one or more systems similar to that of the radio system shown by way of example in Fig. 2 to be described further below.
  • the STA and/or AP of Fig. 1 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3GPP standard, or higher layer standards (such as, for example, a network layer standard) managed by the Internet Engineering Task Force (IETF) community, such as, for example, the Routing Protocol for Low power and Lossy Networks (RPL) routing standard.
  • IETF Internet Engineering Task Force
  • RPL Routing Protocol for Low power and Lossy Networks
  • Any of the STAs and AP of Fig. 1 may be configured to communicate with each other via one or more communications networks.
  • the STAs of Fig. 1 may also communicate directly with each other without the intermediary of AP 104 (in a P2P fashion).
  • Fig. 2 depicts one embodiment of radio system 200 such as one embodiment of a STA, or one embodiment of a AP, such as the APs, or any of the STAs shown in Fig. 1.
  • Fig. 2 will be described in reference to a system such as a STA, while at certain other points within the below description, Fig. 2 will be described in reference to a system such as an AP.
  • the context will however be clear based on the description being provided.
  • "processor” and “processing circuitry” are used interchangeably, and refer to circuitry forming one or more processor “blocks” that provides processing functionality.
  • a block diagram is shown of a wireless communication radio system 200 such as a STA or AP (hereinafter STA/AP) such as the STAs the AP of Fig. 1, according to some demonstrative embodiments.
  • a wireless communication system may include a radio card 202 in accordance with some demonstrative embodiments.
  • Radio card 202 may include radio front-end module (FEM) circuitry 204, radio Integrated Circuit (IC) circuitry 206 and baseband processor 208.
  • FEM radio front-end module
  • IC radio Integrated Circuit
  • the block diagram of Fig. 2 is meant to provide a description of only one examples of many different radio systems that may be used to carry out operations according to embodiments, and is not meant to be limiting in any way.
  • FIG. 2 is shown to include multiple radios, including Wi-Fi and cellular, embodiments could encompass a simple architecture including Wi-Fi capability and a sensing mechanism without many of the other components shown in Fig. 2.
  • Fig. 2 it is to be noted that the representation of a single antenna may be interpreted to mean one or more antennas.
  • FEM circuitry 204 may include Wi-Fi functionality, and may include receive signal path comprising circuitry configured to operate on Wi-Fi signals received from one or more antennas 201, to amplify the received signals and to provide the amplified versions of the received signals to the radio IC circuitry 206 for further processing.
  • FEM circuitry 204 may also include a transmit signal path which may include circuitry configured to amplify signals provided by the radio IC circuitry 206 for wireless transmission by one or more of the antennas 201.
  • the antennas may include directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple- input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • MIMO multiple- input multiple-output
  • Radio IC circuitry 206 may include Wi-Fi functionality, and may include a receive signal path which may include circuitry to down-convert signals received from the FEM circuitry 204 and provide baseband signals to baseband processor 208.
  • the radio IC circuitry 206 may also include a transmit signal path which may include circuitry to up- convert baseband signals provided by the baseband processor 208 and provide RF output signals to the FEM circuitry 204 for subsequent wireless transmission by the one or more antennas 201.
  • Baseband processor 208 may include processing circuitry that provides Wi-Fi functionality.
  • the baseband processor 208 may include a memory 209, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the baseband processor 208.
  • Processing circuitry 210 may include control logic to process the signals received from the receive signal path of the radio IC circuitry 206.
  • Baseband processor 208 is also configured to also generate corresponding baseband signals for the transmit signal path of the radio IC circuitry 206, and may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with application processor 211 for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 206.
  • a MAC mobility management processor 213 may include a processor having logic to provide a number of higher MAC functionalities. In the alternative, or in conjunction with the MAC mobility management processor 213, some of the higher-level MAC functionalities above may be provided by application processor 211.
  • the front-end module circuitry 204, the radio IC circuitry 206, and baseband processor 208 may be provided on a single radio card, such as wireless radio card 202.
  • the one or more antennas 201, the FEM circuitry 204 and the radio IC circuitry 206 may be provided on discrete/separate cards or platforms.
  • the radio IC circuitry 206 and the baseband processor 208 may be provided on a single chip or integrated circuit (IC), such as IC 212.
  • the wireless radio card 202 may include a Wi-Fi radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect.
  • the radio card 202 may be configured to transmit and receive signals transmitted using one or more modulation techniques other than OFDM or OFDMA, such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, and On-Off Keying (OOK), although the scope of the embodiments is not limited in this respect.
  • DS-CDMA direct sequence code division multiple access
  • FH-CDMA frequency hopping code division multiple access
  • TDM time-division multiplexing
  • FDM frequency-division multiplexing
  • OOK On-Off Keying
  • the system 200 may include other radio cards, such as a cellular radio card in the form of Cellular Baseband, Radio IC and Front-End Module Circuitry 216 configured for cellular communication (e.g., 3 GPP such as LTE, LTE- Advanced or 5G communications).
  • a cellular radio card in the form of Cellular Baseband, Radio IC and Front-End Module Circuitry 216 configured for cellular communication (e.g., 3 GPP such as LTE, LTE- Advanced or 5G communications).
  • 3 GPP such as LTE, LTE- Advanced or 5G communications
  • the radio card 202 may be configured for communication over various channel bandwidths including bandwidths having center frequencies of 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of lower than 5 MHz, or of about 1 MHz, 2 MHz, 2.5 MHz, 4 MHz, 5MHz, 8 MHz, 10 MHz, 16 MHz, 20 MHz, 40MHz, 80MHz (with contiguous bandwidths) or 80+80MHz (160MHz) (with non-contiguous bandwidths), or any combination of the above frequencies or bandwidths, or any frequencies or bandwidths between the ones expressly noted above.
  • a 320 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.
  • STA/AP may further include an input unit 218, an output unit 219, a memory unit 215.
  • STA/AP may optionally include other suitable hardware components and/or software components.
  • some or all of the components of STA/AP may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links.
  • components of STA/AP may be distributed among multiple or separate devices.
  • application processor 211 may include, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller.
  • Application processor 211 may execute instructions, for example, of an Operating System (OS) of STA/AP and/or of one or more suitable applications.
  • OS Operating System
  • input unit 218 may include, for example, one or more input pins on a circuit board, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or other suitable pointing device or input device.
  • Output unit 219 may include, for example, one or more output pins on a circuit board, a monitor, a screen, a touch-screen, a flat panel display, a Light Emitting Diode (LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices.
  • LED Light Emitting Diode
  • LCD Liquid Crystal Display
  • memory 215 may include, for example, a
  • Storage unit 217 may include, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units.
  • Memory unit 215 and/or storage unit 217 may store data processed by STA/AP.
  • the system 200 may further include a sensing mechanism/location engine 250, which may be coupled to the baseband processor 208 and application processor 211, and which may be configured to detect information regarding a location of the system 200.
  • the location engine may include either dedicated processing circuitry including logic to allow a determination of location information, or it may include logic that is embedded within the application processor 211 (not shown).
  • the location information/information regarding a location of the system may include information indicating location (latitude, longitude and/or altitude for either a current location or an estimated target location), direction of movement, speed of movement, acceleration, etc.
  • the location engine may include functionality of a compass, an accelerometer, a gyroscope, a Global Positioning System (GPS), for example in combination, which together may tell the system its speed and direction, as would be recognized by one skilled in the art.
  • GPS Global Positioning System
  • a wireless communication device may encompass some or all of a radio system, such as system 200 of Fig. 2.
  • a wireless communication device may encompass a baseband processor, such as baseband processor 208 of Fig. 2, or it may encompass an integrated circuit including a baseband processor such as baseband processor 208 along with a radio IC circuitry, such as radio IC circuitry 206 of Fig. 2, or it may encompass a wireless circuit card such as wireless circuit card 260, or it may include any system which includes a baseband processor, such as the radio system 200 of Fig. 2, and such as a STA or an AP.
  • Fig. 3 depicts a signaling diagram 300, with time depicted on the horizontal axis, to provide an example of a typical approach to support TSN applications by using resource reservation, or the reservation of Service Periods (SPs) during a Beacon Period for TSN operation.
  • SPs Service Periods
  • TSN STAs are shown as having been allotted specific time slots corresponding to a Cycle Time or SP 302.
  • certain ones of Cycle Times or SPs 302 are restricted (R) as being reserved for TSN communications.
  • restricted slots 302a may be reserved for TSN communication between TSN STAs 1 and 2 of Fig. 1 on the one hand, and the AP of Fig.
  • restricted slots 302b may be reserved for TSN communication between the AP of Fig. 1 on the one hand, and the TSN STA 3 of Fig. 1 on the other hand.
  • assigned TSN STAs may contend for the wireless medium, or they may be assigned a fine-grained schedule for communication within their restricted time slot SP 302.
  • TXOPs Non-TSN Transmission Opportunities
  • the Non-TSN TXOPs do not necessarily need to start and stop at slot boundaries within slots of a given SP, except that such Non-TSN TXOP should not extend beyond the start time or stop time of the Beacon Period 312 within which they occur nor extend beyond the start time of a restricted TSN SP.
  • the SPs may be established by a beacon frame 308 which is aligned to the start time or slot boundary 310 of a given SP 302, and which may include information on a master reference time including a Target Beacon Transmission Time (TBTT, corresponding to the Beacon Period), and a Cycle Time (corresponding to the time period of each cycle, time slot or SP, typically about 1 ms).
  • TBTT Target Beacon Transmission Time
  • Cycle Time corresponding to the time period of each cycle, time slot or SP, typically about 1 ms.
  • the beacon frame 308 allows all STAs within a network, such as all STAs in the network 100 of Fig. 1, to record the TBTT and Cycle Time/SP duration/time slot, and to synchronize to the Cycle Time in order to be able to align their communications to the slot boundaries of the SP.
  • the above scheme involving use of an SP may involve all 802.11 radio operations including data, control and management frame transmissions to ensure that critical TSN data and management frames are transmitted in a deterministic manner without conflicts with application defined control cycles applicable to the TSN network.
  • the integer number would then correspond to the number of cycles or SPs within the Beacon Period.
  • the cycle time may be set based on the requirements of the TSN applications. For instance, if the application needs packets to be delivered with latency less than 1msec, the cycle time may be set to 1 msec and the AP is responsible for schedule STAs with the SPs to ensure the latency bound can be met.
  • TSN traffic/frames as referred to herein encompass not only TSN traffic/frames compliant with the IEEE 802.1 TSN set of protocols, but also to any traffic/frames having requirements comparable to those of IEEE 802.1 compliant TSN frames, such as those noted above, namely: (1) precise time synchronization, from the nanosecond (ns) to the millisecond (ms) range, such as about 1 microsecond ⁇ sec) (or for example, from 10 ⁇ ec to 10 msec, with 1 msec being a good target for the majority of applications); (2) deterministic/bounded end-to-end delivery latency, with maximum and minimum latency from source to destination defined (for example, a maximum latency allowed in the latency ranges provided above, along with a maximum allowed jitter of 10 ⁇ 8 ⁇ ), keeping in mind that average, mean or typical values would be of no interest; (3) extremely low packet loss probability, such as
  • Fig. 4 illustrates a convergence scenario where restricted (R) SPs are assigned to TSN applications while STAs with non-TSN traffic must defer access.
  • Fig. 4 clarifies the problem addressed by embodiments, and illustrates how embodiments, to be described further below, complement the existing Contention Window (CW) Backoff (BO) mechanism in 802.11 to avoid collisions in a time-synchronized/scheduled MAC framework.
  • CW Contention Window
  • BO Backoff
  • a time- synchronized/scheduled 802.11 MAC framework is being considered as part of the next generation of the 802.11 /Wi-Fi standard to enable better control of latency and reliability for time-sensitive applications.
  • FIG. 4 an example set of communications/signaling diagram is shown as plotted against time on the horizontal axis in three consecutive graphs for communications from TSN STA 1, Non-TSN STA 4 and Non-TSN STA 5 of Fig. 1, with the top graph pertaining to signaling for TSN STA 1, the middle graph pertaining to signaling for Non-TSN STA 4, and the bottom graph pertaining to signaling for Non-TSN STA 5.
  • Fig 4 shows communications in a typical convergence scenario involving TSN and non-TSN communications in a Wi-Fi network.
  • TSN STA 1 having knowledge of SP 402 by way of a beacon frame similar to the one described in the context of Fig. 3, first defers transmission for an Arbitration Interframe Spacing (AIFS) period depending on its MAC Access Category (AC) under an Enhanced Distributed Channel Access (EDCA) scheme under 802.11. Since the STA in the top graph is a TSN STA, its AC would correspond to a Time Sensitive or (TS) AC, which would result in a AIFS (TS) 404, a shorter AIFS as compared with an AIF for the next level AC, which may include an AC corresponding to Voice. AIFS (TS) 404, includes a guard time or Guard Interval (GI) at the beginning of the same.
  • AIFS Arbitration Interframe Spacing
  • EDCA Enhanced Distributed Channel Access
  • the GI may be equal to 0.8 microseconds to 0.4 microseconds depending on application requirements. Other values for GI may also be used depending on the time synchronization accuracy expected from the STAs.
  • AIFS in general functions by shortening or expanding the period a wireless node has to wait before it is allowed to transmit its next frame based on the AC. After the AIFS (TS) 404 period, TSN STA 1 is shown as having access to a Transmission Opportunity (TXOP) 406 during which it is shown as sending a data frame, followed by a period equal to a Short Interframe Space (SIFS), followed by an Acknowledgment (ACK) frame from a receiver of the data frame.
  • TXOP Transmission Opportunity
  • SIFS Short Interframe Space
  • ACK Acknowledgment
  • the SP 402 is followed by another SP 408, and bounded from the same by a SP boundary 416 as shown.
  • the next SP 408 is shown as not having been assigned to a TSN communication, and therefore represents a shared resource with other TSN and also non-TSN devices within the network (a Shared Resources (SR) SP).
  • SR SP 408 represents an example of a shared resource
  • SP 402 represents an example of an assigned resource or assigned SP, since at least one of its Cycle Times is assigned to a TSN communication.
  • Non-TSN STAs 4 and 5 having knowledge of SP 402 by way of a beacon frame similar to the one described in the context of Fig. 3, first defer transmission for respective AIFS periods 410 and 420 depending on their MAC Access Category (AC), which in the shown case is Best Effort (BE). Since non-TSN STAs 4 and 5 are non-TSN STA, their AIFS are longer as compared with AIFS (TS) 404 for TSN STA 1. AIFS (BE) period 410 and 420 also include a GI (now shown).
  • AC MAC Access Category
  • BE Best Effort
  • non-TSN STA 4 and non-TSN STA 5 are shown as encountering the wireless medium as being busy during 412, as, during this time, TSN STA 1 is using TXOP 406 to communicate.
  • Non-TSN STA 4 and 5 set their respective NAVs for the duration of TXOP 406.
  • the Non-TSN STA 4 and non- TSN STA 5 are shown as waiting for another AIFS (BE) period 410 and 420, at which time, sensing the wireless medium idle within SP 402, they begin decrementing their respective BO counters.
  • Non-TSN STA 4 is shown to have been set to expire after five BO time slots 414 until the BO counter decrease from 5 to 0.
  • the BO counter of Non-TSN STA 5 is shown to have been set to expire after seven BO time slots 414 until the BO counter decrease from 7 to 0.
  • Non-TSN STA 4 and Non-TSN STA 5 are shown as waiting until the boundary 416, the start of the SR SP, before beginning transmission of their respective data frames at 418 and 426.
  • Non-TSN STA 4 and Non-TSN STA 5 are transmitting data to the same destination (e.g. the AP, which is not shown in Fig. 4), or even if those STAs are transmitting to a different destination within range of each other's receivers, even if NON-TSN STA 4 and NON-TSN STA 5 select different BO counters when they defer to TSN STA 1, as shown in Fig.
  • a collision 428 will happen at the beginning of the next SR SP 408, which is at boundary 416, while such collision would not happen in an existing Carrier Sense Multiple Access (CSMA) with Collision Avoidance (CA) (CSMA/CA) schemes involving non-TSN communication using a standard BO mechanism.
  • the existing CW backoff mechanism would handle collision 428 by selecting another BO counter for each non-TSN STA, and would retransmit, although it would not avoid the collision in the first instance. Without modifications to the existing backoff procedure, the number of collisions in time synchronized access modes such as those used in TSN networks and described above in relation to Fig. 3 would increase.
  • TxOffset Transmit Time Offset (TxOffset) to transmissions from non-TSN devices starting at the slot boundary of the next shared resource service period, where the TxOffset may be a randomly determined TxOffset, or one that is based on an EDCA procedure different from the EDCA procedure of the BO used during the first SP.
  • TxOffset may be a randomly determined TxOffset, or one that is based on an EDCA procedure different from the EDCA procedure of the BO used during the first SP.
  • the non-TSN STAs may avoid a collision by applying the TxOffset waiting period.
  • the above scheme involving a TxOffset at the beginning of the next SR SP would advantageously improve channel utilization and reduce latency for converged networks involving both TSN and non-TSN STAs.
  • embodiments allow a better utilization of SP resources without actually transmitting non-TSN data within an assigned SP in a way as to interfere with TSN applications.
  • the reduction in latency brought about by embodiments with respect to Non-TSN Networks further does not compromise the QoS, including latency and reliability of converted TSN applications.
  • Another approach that has been proposed to address the issue of collisions of non-TSN communications in synchronized TSN networks is to re-utilize the time during a SP by having the SP owner (such as a STA or an AP) explicitly end the SP by way of sending a Contention Free end frame, or CF-end frame.
  • the SP owner such as a STA or an AP
  • CF-end frame Contention Free end frame
  • beacon frames 402 through a beacon frame may have set their NAVs as the channel is busy for the duration of SP 402, and would not contend for access during that interval (not shown in Fig. 4 as this feature is a prior art feature). But in the latter case, without more, the non-TSN STAs will experience longer latencies and medium utilization will be lower.
  • the first idea according to some demonstrative embodiments is to allow the non-TSN STAs to contend and decrement their backoff within the TSN SP 402, but not transmit when the counter reaches 0. If we allow only this feature without more (e.g. to improve efficiency), then we arrive at the situation shown in Fig. 4, where a collision will happen in the next SP due to the time synchronization. Therefore, we need the second part of the solution which is the randomized backoff at the next SP as described above.
  • APs and STAs can synchronize their clocks to a master reference time, such as by way of a beacon frame decoding as described in relation to Fig. 3, and/or by way of using time synchronization protocols as set forth in 802. IAS and 802.11 standards; and (2) the AP can define a time synchronized slotted time including Cycle Times and SP as described in relation to Fig. 3 above.
  • Fig. 5 shows an example set of communications plotted against time on the horizontal axis in three consecutive graphs for communications from TSN STA 1, Non-TSN STA 4 and Non-TSN STA 5 of Fig. 1, with the top graph pertaining to signaling for TSN STA 1, the middle graph pertaining to signaling for Non-TSN STA 4, and the bottom graph pertaining to signaling for Non-TSN STA 5.
  • Fig 5 shows communications in a convergence scenario according to some demonstrative embodiments involving TSN and non-TSN communications in a Wi-Fi network.
  • TSN STA 1 having knowledge of SP 502 by way of a beacon frame similar to the one described in the context of Fig. 3, first defers transmission for an Arbitration Interframe Spacing (AIFS) period depending on its MAC Access Category (AC) under an Enhanced Distributed Channel Access (EDCA) scheme under 802.11. Since the STA in the top graph is a TSN STA, its AC would correspond to a Time Sensitive or (TS) AC, which would result in a AIFS (TS) 504, a shorter AIFS as compared with an AIF for the next level AC, which may include an AC corresponding to Voice. AIFS (TS) 404, includes a guard time or Guard Interval (GI) 505 at the beginning of the same.
  • AIFS Arbitration Interframe Spacing
  • EDCA Enhanced Distributed Channel Access
  • the GI may be equal to 0.8 microseconds to 0.4 microseconds depending on application requirements.
  • AIFS in general functions by shortening or expanding the period a wireless node has to wait before it is allowed to transmit its next frame based on the AC.
  • TSN STA 1 is shown as having access to a Transmission Opportunity (TXOP) 506 during which it is shown as sending a data frame, followed by a duration equal to a Short Interframe Space (SIFS), followed by an Acknowledgment (ACK) frame from a receiver of the data frame.
  • TXOP Transmission Opportunity
  • SIFS Short Interframe Space
  • ACK Acknowledgment
  • the SP 502 is followed by another SP 508, and bounded from the same by a SP boundary 516 as shown.
  • the next SP 508 is shown as not having been assigned to a TSN communication, and therefore represents a shared resource with other TSN and also non-TSN devices within the network (a Shared Resources (SR) SP).
  • SR Shared Resources
  • Non-TSN STAs 4 and 5 having knowledge of SP 402 by way of a beacon frame similar to the one described in the context of Fig. 3, first defer transmission for respective AIFS periods 510 and 520 depending on their MAC Access Category (AC), which in the shown case is Best Effort (BE). They may set their NAVs for the SP duration, but will continue to their EDCA access procedure during SP 502 to be able to decrement their BO counters when the medium is free, but will still not transmit. Since non-TSN STAs 4 and 5 are non-TSN STA, their AIFS are longer as compared with AIFS (TS) 504 for TSN STA 1.
  • AC MAC Access Category
  • BE Best Effort
  • AIFS (BE) period 510 and 520 also include a GI (now shown).
  • GI now shown.
  • non-TSN STA 4 and non-TSN STA 5 are shown as encountering the wireless medium as being busy during 512, as, during this time, TSN STA 1 would be using TXOP 506 to communicate.
  • the Non-TSN STA 4 and non-TSN STA 5 are shown as waiting for another AIFS (BE) period 510 and 520, at which time, sensing the wireless medium idle within SP 502, they begin decrementing their respective BO counters.
  • Non-TSN STA 4 is shown to have been set to expire after five BO time slots 514 until the BO counter decrease from 5 to 0.
  • the BO counter of Non-TSN STA 5 is shown to have been set to expire after seven BO time slots 514 until the BO counter decrease from 7 to 0.
  • Non-TSN STA 4 and Non-TSN STA 5 are shown as waiting until the slot boundary 516, that is, as deferring their respective transmissions to the next shared resource opportunity, that is, to the start of the SR SP.
  • Non-TSN STAs 4 and 5 area each shown as employing a respective TxOffset period 530 and 532, with TxOffset period 530 being different from TxOffset period 532 according to some demonstrative embodiments.
  • Some demonstrative embodiments provide a TxOffset period at a slot boundary of the next shared resource in order to avoid direct collisions with other non-TSN STAs that may have also decremented their BO counters during the assigned SP.
  • the non-TSN STA 4 is shown as gaining access to a non-TSN TXOP 536 during which it is able to send data, and, after a SIFS period, to receive an ACK frame from its recipient(s).
  • the non-TSN STA 5 is shown as encountering the wireless medium as being busy during 513, as, during this time, non-TSN STA 4 would be using TXOP 536 to communicate.
  • Non-TSN STA 5 After the end of the Busy Medium period 513, the Non-TSN STA 5 is shown as waiting for another AIFS (BE) period 510 and 520, at which time, sending the wireless medium idle within SP 502, it begins decrementing its BO counter from 7 to 0 at CW 519 as part of a non-TSN Wi-Fi legacy contention process. Non-TSN STA 5 may also pick another BO counter different from the previous BO counter. If the wireless medium is busy after the CW 519, Non-TSN STA may then access the wireless medium by gaining access to a TXOP in the usual manner.
  • BE AIFS
  • the TxOffset period may be a randomly determined TxOffset period.
  • the TxOffset may be equal to the applicable GI for the TSN data, plus a random number of time slots for the assigned SP, such as SP 502 of Fig. 5.
  • Each time slot may for example correspond to a time slotsdefined in the 802.11 Medium Access Control layer of 9 microseconds, other time slot durations being possible according to embodiments.
  • a maximum value for the TxOffset period is based on an AIFS for the non-TSN data plus a BO counter value corresponding to an Access Category (AC) for the non-TSN data.
  • a TxOffset period may have the GI for the non- TSN data as a minimum value, and the BO counter value for the AC of the non-TSN data as a maximum value. Having the GI value for the non-TSN data as a minimum value accounts for any synchronization inaccuracies and potential delay spread.
  • the TxOffset period may be randomly determined based on an Access Category (AC) of the non-TSN data. For example, certain non-TSN applications (such as those have a Voice or a Video AC) could still get faster access compared to other delay tolerant applications such as, for example, BE.
  • non-TSN STAs can advantageously decrement their BO counters within assigned SPs and can access the wireless medium with shorter latency, while still avoiding potential collisions in the next shared resource.
  • the TxOffset period may be determined based on an EDCA category that is different from, and preferably that leads to faster access as compared with, the EDCA corresponding to the BO counter for the BO period or CW used by a non-TSN STA during an assigned SP.
  • TxOffset period 530 for non- TSN STA 4 may be based on an EDCA that corresponds to a Voice AC (providing faster access), while the BO counter of non-TSN STA 4 during the assigned SP 502 may be based on an EDCA that corresponds to a BE AC (providing comparatively slower access).
  • a wireless communication device such as a baseband processor 208 within the STA or AP side of Fig. 2, may comprise a memory, such as memory 209 of Fig. 2, and processing circuitry, such as processing circuitry 210 of Fig. 2, the processing circuitry being coupled to the memory 209.
  • Memory 209 may include instructions or logic, and the processing circuitry may be configured to implement or perform the instructions or logic.
  • the processing circuit may implement the logic to set a Network Allocation Vector (NAV) during a Time Sensitive Network Service Period (SP) assigned to one or more TSN devices, such as devices corresponding to TSN STAs 1-3 of Fig.
  • NAV Network Allocation Vector
  • SP Time Sensitive Network Service Period
  • decrement a Backoff (BO) counter as shown for example at 515 in Fig. 5, during the SP in response to a determination that a wireless medium is idle; refrain from wireless transmission of non-TSN data during the SP and until a next shared resource period, such as SR SP 508 of Fig 5; and cause transmission of the non-TSN data after expiration of a transmission offset (TxOffset) period beginning at a slot boundary of the next shared resource period, such as after expiration of TxOffset period 530 at slot boundary 516 of the SR SP 508 of Fig. 5.
  • TxOffset transmission offset
  • a processing circuitry may cause transmission, that is, may generate a frame for transmission, the actual transmission itself may be effected by way of the system such as the radio system 200 and antennas 201.
  • the memory may encompass memory 209 and/or memory 215, and the processing circuitry may encompass processing circuitry 210 of Fig. 2 and/or application processor 211 of Fig. 2.
  • Fig. 6 illustrates a method 600 of operating a wireless communication device according to some demonstrative embodiments.
  • the method 600 may begin with operation 602, which includes setting a Network Allocation Vector (NAV) during a Time Sensitive Network Service Period (SP) assigned to one or more TSN devices.
  • NAV Network Allocation Vector
  • SP Time Sensitive Network Service Period
  • the method includes decrementing a Backoff (BO) counter during the SP in response to a determination that a wireless medium is idle.
  • the method includes refraining from wireless transmission of non-TSN data during the SP and until a next shared resource period.
  • the method includes causing transmission of the non-TSN data after expiration of a transmission offset (TxOffset) period beginning at a slot boundary of the next shared resource period.
  • TxOffset transmission offset
  • Fig. 7 illustrates a product of manufacture 700, in accordance with some demonstrative embodiments.
  • Product 700 may include one or more tangible computer- readable non-transitory storage media 702, which may include computer-executable instructions, e.g., implemented by logic 704, operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at one or more STAs or APs, and/or to perform one or more operations described above with respect to Figs. 1-3 and 5-6, and/or one or more operations described herein.
  • the phrase "non-transitory machine-readable medium" is directed to include all computer- readable media, with the sole exception being a transitory propagating signal.
  • product 700 and/or storage media 702 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like.
  • storage media 702 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR- DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppy disk, a hard drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and the like.
  • RAM random access memory
  • DDR- DRAM Double-Data-Rate DRAM
  • SDRAM static RAM
  • ROM read-only memory
  • the computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.
  • a communication link e.g., a modem, radio or network connection.
  • logic 704 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein.
  • the machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.
  • logic 704 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like.
  • the instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • the instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function.
  • the instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.
  • Some demonstrative 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. Those instructions may then be read and executed by one or more processors to cause the system 200 of Fig. 2 to perform the methods and/or 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.
  • Example 1 includes a wireless communication device comprising a memory and processing circuitry coupled to the memory, the processing circuitry including logic, the processing circuitry configured to implement the logic: set a Network Allocation Vector (NAV) during a Time Sensitive Network Service Period (SP) assigned to one or more TSN devices; decrement a Backoff (BO) counter during the SP in response to a determination that a wireless medium is idle; refrain from wireless transmission of non-TSN data during the SP and until a next shared resource period; and cause transmission of the non-TSN data after expiration of a transmission offset (TxOffset) period beginning at a slot boundary of the next shared resource period.
  • NAV Network Allocation Vector
  • SP Time Sensitive Network Service Period
  • BO Backoff
  • Example 2 includes the subject matter of Example 1, and optionally, wherein the TxOffset period is a randomly determined TxOffset period.
  • Example 3 includes the subject matter of Example 1, and optionally, wherein the TxOffset period correspond to a duration equal to a Guard Interval for the non-TSN data, plus a random number of time slots.
  • Example 4 includes the subject matter of Example 3, and optionally, wherein a maximum value for the TxOffset period is based on an Arbitration Interframe Spacing (AIFS) for the non-TSN data plus a BO counter value corresponding to an Access Category (AC) for the non-TSN data.
  • AIFS Arbitration Interframe Spacing
  • AC Access Category
  • Example 5 includes the subject matter of Example 2, and optionally, wherein the TxOffset period is randomly determined based on an Access Category (AC) of the non-TSN data.
  • AC Access Category
  • Example 6 includes the subject matter of Example 1, and optionally, wherein a value of the BO counter is based on a first Enhanced Distributed Channel Access (EDCA) category, and wherein the TxOffset period is based on a second EDCA category different from the first EDCA category.
  • EDCA Enhanced Distributed Channel Access
  • Example 7 includes the subject matter of Example 6, and optionally, wherein the second EDCA category is to enable faster access to the wireless medium than the first EDCA category.
  • Example 8 includes the subject matter of Example 1, and optionally, wherein the processing circuitry is to implement the logic to: decode a beacon frame including information on a master reference time including a Target Beacon Transmission Time (TBTT) and Cycle Times for a TSN network including the one or more TSN devices; synchronize to the master reference time; and align communications to and from the device to the Cycle Times.
  • TBTT Target Beacon Transmission Time
  • Example 9 includes the subject matter of Example 8, and optionally, wherein the TBTT includes an integer number of the Cycle Times.
  • Example 10 includes the subject matter of Example 1, and optionally, further including a radio integrated circuit coupled to the processing circuitry, and a front-end module coupled to the radio integrated circuit.
  • Example 11 includes the subject matter of Example 10, and optionally, further including one or more antennas coupled to the front-end module.
  • Example 12 includes a wireless communication device including: means for setting a Network Allocation Vector (NAV) during a Time Sensitive Network Service Period (SP) assigned to one or more TSN devices; means for decrementing a Backoff (BO) counter during the SP in response to a determination that a wireless medium is idle; means for refraining from wireless transmission of non-TSN data during the SP and until a next shared resource period; and means for causing transmission of the non-TSN data after expiration of a transmission offset (TxOffset) period beginning at a slot boundary of the next shared resource period.
  • NAV Network Allocation Vector
  • SP Time Sensitive Network Service Period
  • BO Backoff
  • TxOffset transmission offset
  • Example 13 includes the subject matter of Example 12, and optionally, wherein the TxOffset period is a randomly determined TxOffset period.
  • Example 14 includes the subject matter of Example 12, and optionally, wherein the TxOffset period correspond to a duration equal to a Guard Interval for the non-TSN data, plus a random number of time slots.
  • Example 15 includes the subject matter of Example 14, and optionally, wherein a maximum value for the TxOffset period is based on an Arbitration Interframe Spacing (AIFS) for the non-TSN data plus a BO counter value corresponding to an Access Category (AC) for the non-TSN data.
  • AIFS Arbitration Interframe Spacing
  • AC Access Category
  • Example 16 includes the subject matter of Example 13, and optionally, wherein the TxOffset period is randomly determined based on an Access Category (AC) of the non-TSN data.
  • Example 17 includes the subject matter of Example 12, and optionally, wherein a value of the BO counter is based on a first Enhanced Distributed Channel Access (EDCA) category, and wherein the TxOffset period is based on a second EDCA category different from the first EDCA category.
  • EDCA Enhanced Distributed Channel Access
  • Example 18 includes the subject matter of Example 17, and optionally, wherein the second EDCA category is to enable faster access to the wireless medium than the first EDCA category.
  • Example 19 includes the subject matter of Example 12, and optionally, further including: means for decoding a beacon frame including information on a master reference time including a Target Beacon Transmission Time (TBTT) and Cycle Times for a TSN network including the one or more TSN devices; means for synchronizing to the master reference time; and means for aligning communications to and from the device to the Cycle Times.
  • TBTT Target Beacon Transmission Time
  • Example 20 includes the subject matter of Example 19, and optionally, wherein the TBTT includes an integer number of the Cycle Times.
  • Example 21 includes a product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, cause the at least one computer processor to implement operations at a wireless communication device, the operations comprising: setting a Network Allocation Vector (NAV) during a Time Sensitive Network Service Period (SP) assigned to one or more TSN devices; decrementing a Backoff (BO) counter during the SP in response to a determination that a wireless medium is idle; refraining from wireless transmission of non-TSN data during the SP and until a next shared resource period; and causing transmission of the non-TSN data after expiration of a transmission offset (TxOffset) period beginning at a slot boundary of the next shared resource period.
  • NAV Network Allocation Vector
  • SP Time Sensitive Network Service Period
  • BO Backoff
  • Example 22 includes the subject matter of Example 21, and optionally, wherein the TxOffset period is a randomly determined TxOffset period.
  • Example 23 includes the subject matter of Example 21, and optionally, wherein the TxOffset period correspond to a duration equal to a Guard Interval for the non-TSN data, plus a random number of time slots.
  • Example 24 includes the subject matter of Example 23, and optionally, wherein a maximum value for the TxOffset period is based on an Arbitration Interframe Spacing (AIFS) for the non-TSN data plus a BO counter value corresponding to an Access Category (AC) for the non-TSN data.
  • AIFS Arbitration Interframe Spacing
  • AC Access Category
  • Example 25 includes the subject matter of Example 22, and optionally, wherein the TxOffset period is randomly determined based on an Access Category (AC) of the non-TSN data.
  • AC Access Category
  • Example 26 includes the subject matter of Example 21, and optionally, wherein a value of the BO counter is based on a first Enhanced Distributed Channel Access (EDCA) category, and wherein the TxOffset period is based on a second EDCA category different from the first EDCA category.
  • EDCA Enhanced Distributed Channel Access
  • Example 27 includes the subject matter of Example 26, and optionally, wherein the second EDCA category is to enable faster access to the wireless medium than the first EDCA category.
  • Example 28 includes the subject matter of Example 21, and optionally, wherein the operations further include: decoding a beacon frame including information on a master reference time including a Target Beacon Transmission Time (TBTT) and Cycle Times for a TSN network including the one or more TSN devices; synchronizing to the master reference time; andaligning communications to and from the device to the Cycle Times.
  • TBTT Target Beacon Transmission Time
  • Example 29 includes the subject matter of Example 28, and optionally, wherein the TBTT includes an integer number of the Cycle Times.
  • Example 30 includes a method to be performed at a wireless communication device, the method comprising: setting a Network Allocation Vector (NAV) during a Time Sensitive Network Service Period (SP) assigned to one or more TSN devices; decrementing a Backoff (BO) counter during the SP in response to a determination that a wireless medium is idle; refraining from wireless transmission of non-TSN data during the SP and until a next shared resource period; and causing transmission of the non-TSN data after expiration of a transmission offset (TxOffset) period beginning at a slot boundary of the next shared resource period.
  • NAV Network Allocation Vector
  • SP Time Sensitive Network Service Period
  • BO Backoff
  • Example 31 includes the subject matter of Example 30, and optionally, wherein the TxOffset period is a randomly determined TxOffset period.
  • Example 32 includes the subject matter of Example 30, and optionally, wherein the TxOffset period correspond to a duration equal to a Guard Interval for the non-TSN data, plus a random number of time slots.
  • Example 33 includes the subject matter of Example 32, and optionally, wherein a maximum value for the TxOffset period is based on an Arbitration Interframe Spacing (AIFS) for the non-TSN data plus a BO counter value corresponding to an Access Category (AC) for the non-TSN data.
  • AIFS Arbitration Interframe Spacing
  • AC Access Category
  • Example 34 includes the subject matter of Example 31, and optionally, wherein the TxOffset period is randomly determined based on an Access Category (AC) of the non-TSN data.
  • AC Access Category
  • Example 35 includes the subject matter of Example 30, and optionally, wherein a value of the BO counter is based on a first Enhanced Distributed Channel Access (EDCA) category, and wherein the TxOffset period is based on a second EDCA category different from the first EDCA category.
  • EDCA Enhanced Distributed Channel Access
  • Example 36 includes the subject matter of Example 35, and optionally, wherein the second EDCA category is to enable faster access to the wireless medium than the first EDCA category.
  • Example 37 includes the subject matter of Example 30, and optionally, wherein the operations further include: decoding a beacon frame including information on a master reference time including a Target Beacon Transmission Time (TBTT) and Cycle Times for a TSN network including the one or more TSN devices; synchronizing to the master reference time; andaligning communications to and from the device to the Cycle Times.
  • TBTT Target Beacon Transmission Time
  • Example 38 includes the subject matter of Example 37, and optionally, wherein the TBTT includes an integer number of the Cycle Times.

Landscapes

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

Abstract

L'invention concerne un dispositif, un système et un procédé de communication sans fil. Le dispositif peut comprendre une mémoire mémorisant des instructions, et un montage de circuits de traitement couplé à la mémoire pour exécuter les instructions. Le montage de circuits de traitement peut être configuré pour : configurer un vecteur d'attribution de réseau (NAV) pendant une période de service (SP) de réseau sensible au temps attribuée à un ou plusieurs dispositifs TSN ; décrémenter un compteur de réduction de puissance (BO) pendant la SP en réponse à une détermination selon laquelle un milieu sans fil est au repos ; s'abstenir de transmettre sans fil des données non TSN pendant la SP et jusqu'à une période de ressource partagée suivante ; et provoquer la transmission des données non TSN après expiration d'une période de décalage de transmission (TxOffset) commençant à une limite de créneau de la période de ressource partagée suivante.
PCT/US2017/068822 2017-04-27 2017-12-28 Dispositif, procédé et système pour mettre en œuvre un mécanisme de réduction de puissance opportuniste pour convergence de trafic dans des réseaux sensibles au temps basés sur wi-fi Ceased WO2018200038A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762490806P 2017-04-27 2017-04-27
US62/490,806 2017-04-27

Publications (1)

Publication Number Publication Date
WO2018200038A1 true WO2018200038A1 (fr) 2018-11-01

Family

ID=63918651

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/068822 Ceased WO2018200038A1 (fr) 2017-04-27 2017-12-28 Dispositif, procédé et système pour mettre en œuvre un mécanisme de réduction de puissance opportuniste pour convergence de trafic dans des réseaux sensibles au temps basés sur wi-fi

Country Status (1)

Country Link
WO (1) WO2018200038A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020155149A1 (fr) * 2019-02-02 2020-08-06 Lenovo (Beijing) Limited Planification améliorée de mise en réseau sensible au temps
CN112166638A (zh) * 2019-02-14 2021-01-01 捷开通讯(深圳)有限公司 时间敏感型网络支持
CN113518464A (zh) * 2019-09-18 2021-10-19 Oppo广东移动通信有限公司 资源配置的方法和接入网设备
WO2023057320A1 (fr) * 2021-10-05 2023-04-13 Sony Group Corporation Premier et deuxième dispositifs de communication et procédés
WO2023059030A1 (fr) * 2021-10-05 2023-04-13 현대자동차주식회사 Procédé et dispositif de transmission inverse de données rapides dans un système de communication
US11949499B2 (en) * 2019-05-07 2024-04-02 Zte Corporation Methods, apparatus and systems for time mapping in a wireless communication

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050063589A (ko) * 2003-12-22 2005-06-28 한국전자통신연구원 Ｅｄｃａ 지원을 위한 무선 랜 매체 접근 제어 프레임전송 장치 및 방법
KR20080026461A (ko) * 2006-09-20 2008-03-25 엘지전자 주식회사 경쟁 기반의 데이터 송수신용 단말장치 및 베이스 스테이션그리고 이들을 포함한 시스템 및 경쟁 기반의 데이터송수신 방법
US20120327919A1 (en) * 2001-11-02 2012-12-27 Mathilde Benveniste Fixed deterministic post-backoff for cyclic prioritized multiple access (cpma) contention-free sessions
US20160021017A1 (en) * 2014-07-18 2016-01-21 Cisco Technology, Inc. Distributed rescheduling of bounded flows in a time sensitive network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120327919A1 (en) * 2001-11-02 2012-12-27 Mathilde Benveniste Fixed deterministic post-backoff for cyclic prioritized multiple access (cpma) contention-free sessions
KR20050063589A (ko) * 2003-12-22 2005-06-28 한국전자통신연구원 Ｅｄｃａ 지원을 위한 무선 랜 매체 접근 제어 프레임전송 장치 및 방법
KR20080026461A (ko) * 2006-09-20 2008-03-25 엘지전자 주식회사 경쟁 기반의 데이터 송수신용 단말장치 및 베이스 스테이션그리고 이들을 포함한 시스템 및 경쟁 기반의 데이터송수신 방법
US20160021017A1 (en) * 2014-07-18 2016-01-21 Cisco Technology, Inc. Distributed rescheduling of bounded flows in a time sensitive network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TOMMI LARSSON ET AL.: "A Study of EDCA and DCF in Multihop Ad Hoc Networks", 13 March 2008 (2008-03-13), XP055526779, Retrieved from the Internet <URL:http://www.eit.lth.se/fileadmin/eit/home/sdkd.aha/Larsson_Liu_MastersThesis.pdf> *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020155149A1 (fr) * 2019-02-02 2020-08-06 Lenovo (Beijing) Limited Planification améliorée de mise en réseau sensible au temps
US11902959B2 (en) 2019-02-02 2024-02-13 Lenovo (Beijing) Limited Enhanced scheduling of time sensitive networking
CN112166638A (zh) * 2019-02-14 2021-01-01 捷开通讯(深圳)有限公司 时间敏感型网络支持
CN112166638B (zh) * 2019-02-14 2024-02-09 捷开通讯(深圳)有限公司 时间敏感型网络支持
US11949499B2 (en) * 2019-05-07 2024-04-02 Zte Corporation Methods, apparatus and systems for time mapping in a wireless communication
CN113518464A (zh) * 2019-09-18 2021-10-19 Oppo广东移动通信有限公司 资源配置的方法和接入网设备
US11950277B2 (en) 2019-09-18 2024-04-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Resource configuration method and access network device
WO2023057320A1 (fr) * 2021-10-05 2023-04-13 Sony Group Corporation Premier et deuxième dispositifs de communication et procédés
WO2023059030A1 (fr) * 2021-10-05 2023-04-13 현대자동차주식회사 Procédé et dispositif de transmission inverse de données rapides dans un système de communication

Similar Documents

Publication Publication Date Title
JP7324779B2 (ja) チャネル化および帯域幅パート（ｂｗｐ）
US20190007941A1 (en) Device, Method and System to Implement Preemptive Transmission of a Wireless Time Sensitive Network Frame
WO2018200038A1 (fr) Dispositif, procédé et système pour mettre en œuvre un mécanisme de réduction de puissance opportuniste pour convergence de trafic dans des réseaux sensibles au temps basés sur wi-fi
US10701688B2 (en) Dynamic channel bonding and multi-band aggregation
US10694518B2 (en) Enhanced channel access for wireless communications
US12004217B2 (en) Random access preamble sending method, random access preamble receiving method, and communications apparatus
CN109217960B (zh) 利用资源聚合进行多信道时间同步无线联网
EP3216297B1 (fr) Contrôle d&#39;accès au support pour accès assisté par licence
KR20210100732A (ko) 신호 전송 방법, 우선순위 구성 방법 및 장치
CN111757459B (zh) 一种通信方法及装置
WO2019125396A1 (fr) Mise en réseau améliorée sensible au temps pour des communications sans fil
EP3577912B1 (fr) Détermination d&#39;un créneau d&#39;accès pour des communications sur une interface radio
US20250039921A1 (en) Wireless communication method for saving power and wireless communication terminal using same
US20170265105A1 (en) Coexistence through use of less power constrained assisted 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
JP6891302B2 (ja) 無線通信ネットワークにおいて通信するための装置および方法
CN104640225A (zh) 用于无线网络传输的方法和装置
US20230143575A1 (en) Enhancements to wi-fi devices for enabling cyclic time-sensitive applications with very short cycle times
JP7248702B2 (ja) 衝突回避のある決定論的バックオフ
WO2019032148A1 (fr) Programmation améliorée pour communications sans fil
US20250113377A1 (en) Coordinated Channel Access in Wireless Communication Systems
WO2025200956A1 (fr) Procédé de communication et appareil de communication
WO2025200958A1 (fr) Procédé de communication et appareil de communication
CN120730458A (zh) 通信方法及通信装置

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

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

Country of ref document: EP

Kind code of ref document: A1