WO2018071051A1 - Procédures et signalisation de planification et attribution de ressources dans un système de communication de liaison latérale d'objets de nouvelle radio 5g - Google Patents

Procédures et signalisation de planification et attribution de ressources dans un système de communication de liaison latérale d'objets de nouvelle radio 5g Download PDF

Info

Publication number
WO2018071051A1
WO2018071051A1 PCT/US2016/068906 US2016068906W WO2018071051A1 WO 2018071051 A1 WO2018071051 A1 WO 2018071051A1 US 2016068906 W US2016068906 W US 2016068906W WO 2018071051 A1 WO2018071051 A1 WO 2018071051A1
Authority
WO
WIPO (PCT)
Prior art keywords
subframe
data
urllc
ues
pras
Prior art date
Application number
PCT/US2016/068906
Other languages
English (en)
Inventor
Yaser M. FOUAD
Satish Chandra Jha
Dawei YING
Qian Li
Guangjie Li
Xiaoyun May Wu
Geng Wu
JoonBeom Kim
Vesh Raj SHARMA BANJADE
Lu LU
Hassan GHOZLAN
Song Noh
Original Assignee
Intel 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 Corporation filed Critical Intel Corporation
Publication of WO2018071051A1 publication Critical patent/WO2018071051A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1835—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/52—Allocation or scheduling criteria for wireless resources based on load
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS

Definitions

  • Embodiments pertain to radio access networks. Some embodiments relate to wearable devices in various cellular and wireless local area network (WLAN) networks, including Third Generation Partnership Project Long Term Evolution (3GPP LTE) networks and LTE advanced (LTE-A) networks as well as 4 ih generation (4G) networks and 5 th generation (5G) networks. Some embodiments relate to 5G wearable or other "tilings" devices and network interactions, in particular handling of user and control plane data in sidelink communications.
  • WLAN wireless local area network
  • 3GPP LTE Third Generation Partnership Project Long Term Evolution
  • LTE-A LTE advanced
  • 4G 4 ih generation
  • 5G 5 th generation
  • 3 GPP LTE systems has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs.
  • UEs user equipment
  • MTC machine type communication
  • M2M machine-to-machine
  • tUE user-based IoT devices developed recently whose popularity has exploded is "things" user equipment (tUE), such as wearable devices, in addition to one or more network UEs (nUE).
  • wearable devices include fitness trackers, smart watches, and smart glasses.
  • Wearable devices typically have lower processing capability, a small battery capacity, and a low internal memory capacity.
  • each user may carry multiple wearable devices, and may be located in a highly -dense populated situation with other people carrying one or more other wearable devices and nUEs.
  • tUEs may have a mobility similar to that of nUEs and limited functionality compared to the nUEs, independent of the type of tUE.
  • the sidelmk communication in the 5G network between a tUE and nUE remains to be determined due at least in part to the vast changes in design of the 5G network.
  • FIG. 1 is a block diagram of a system architecture for supporting wearable devices in accordance with some embodiments.
  • FIG. 2 illustrates components of a communication device in accordance with some embodiments.
  • FIG. 3 illustrates a block diagram of a communication device in accordance with some embodiments.
  • FIG. 4 illustrates another block diagram of a communication device in accordance with some embodiments.
  • FIG. 5 illustrates a protocol stack in accordance with some embodiments.
  • FIGS. 6A and 6B illustrate downlink and uplink subframe structures in accordance with some embodiments.
  • FIG. 7 illustrates a flowchart of scheduling and resource allocation in accordance with some embodiments.
  • FIG. 1 is a block diagram of a system architecture 100 for supporting wearable devices.
  • the system architecture 100 includes a network user equipment (nUE) 110, one or more things user equipment (tUEs) 120a, 120b, 120c, an evolved universal terrestrial radio access network (E- UTRAN or EUTRAN) base station (BS, also referred to as an evolved NodeB (eNB)) or 5G base station 130, and an evolved packet core (EPC) or 5G core 140.
  • BS also referred to as an evolved NodeB (eNB)
  • EPC evolved packet core
  • the nUE 110 and the tUEs 120 together form a personal area network (PAN) 150 or side link cell.
  • PAN personal area network
  • the EUTRAN thus may include eNBs 130 that provide user plane and control plane protocol tenninations towards the nUE 1 10.
  • the eNBs 130 may be connected by means of the X2 interface.
  • the eNBs 130 may also be connected to a Mobility Management Entity (MME) via a Sl-MME and to a Serving Gateway (S-GW) via a Sl-U.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • the nUE 1 10 may be any user equipment capable of
  • the nUE 110 may be a mobile phone, a tablet computer, a wearable device such as a smart watch, etc.
  • the nUE may be a tUE that is capable of communicating with the base station 130 and has sufficient battery life (e.g., greater than 30%, 50%, 75%, 90% of the maximum amount of battery power etc.).
  • the nUE 110 may have a full infrastructure network access protocol and full control and user plane (C/U-dlane) functions. As shown, the nUE 110 may communicate with the base station 130 via a Xu-d (direct) air interface.
  • Each tUE 120 may include a wireless interface (Xu ⁇ d or Xu-s) for communicating within the PAN 150.
  • the tUE 120 may communicate with the nUE 110 or another tUE 120 through the Xu-s (sidelink) intra-PAN air interface.
  • the tUE 120 may include, for example, smart watches, smart glasses, smart headphones, fitness sensors, movement trackers, sleep sensors, etc.
  • the tUE 120 may also communicate directly with the base station 130 via a Xu-d air interface.
  • the tUE 120 may be unable to communicate directly with the base station 130.
  • the nUE 110 may act as a master UE in a sidelink cell formed by the nUE 1 0 and associated tUEs 120.
  • the tUE 120 may have a full sidelink protocol stack and may or may not have standalone direct link protocol stack.
  • the tUE 120 may act as a slave UE in the side link cell.
  • the base station 130 may be a base station of a cellular network.
  • the base station 130 is may be an eNB in a LTE cellular network or a 5G Radio Access Network (RAN) in a next generation (5G) network.
  • the 5G RAN may be a standalone base station or a booster cell anchored to an eNB.
  • the base station 130 may communicate with a core network 140 (EPC for LTE or 5G core for 5G) using an SI interface.
  • EPC for LTE or 5G core for 5G
  • SI interface SI interface
  • the base station 130 may be a macro base station or a smaller base station (micro, pico, nano) that may terminate the air interface protocol.
  • the base station 130 may fulfill various logical functions for the RAN including, but not limited to, RNC (radio network controller functions) such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller functions
  • UEs 120 may be configured to communicate orthogonal frequency division multiplexed (OFDM) communication signals with the base station 130 over a muiticarrier communication channel in accordance with an OFDMA communication technique.
  • the OFDM signals may comprise a plurality of orthogonal subcarriers.
  • non-OFDM signals may be used in addition or instead of OFDM signals.
  • the SI interface may be the interface that separates the RAN 130 and the core network 140.
  • the SI interface may be split into two parts: the Sl- U, which may carry traffic data between base stations of the RAN 130 and other elements of the core network, such as a serving GW, and the S l-MME, which may be a signaling interface between the RAN 130 and an MME.
  • FIG. 2 illustrates components of a communication device in accordance with some embodiments.
  • the communication device 200 may be a UE, eNB or other network component as described herein.
  • the communication device 200 may be a stationary, non-mobile device or may be a mobile device.
  • the UE 200 may include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208 and one or more antennas 210, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • At least some of the baseband circuitry 204, RF circuitry 206, and FEM circuitry 208 may form a transceiver.
  • other network elements, such as the MME may contain som e or all of the components shown in FIG. 2.
  • the application or processing circuitry 202 may include one or more application processors.
  • the application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi- core processors.
  • the processors may include any combination of general- purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 204 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206.
  • Baseband processing circuity 204 may interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206.
  • the baseband circuitry 204 may include a second generation (2G) baseband processor 204a, third generation (3G) baseband processor 204b, fourth generation (4G) baseband processor 204c, and/or other baseband processor(s) 204d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 5G, etc.).
  • the baseband circuitry 204 e.g., one or more of baseband processors 204a-d
  • the radio control functions may include, but are not limited to, signal modulation/demodulation,
  • modulation/demodulation circuitry of the base band circuitry 204 may include FFT, precoding, and/or constellation mapping/demapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 204 may include elements of a protocol stack such as, for example, elements of an Evolved UTRAN (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) elements, and/or Non- Access Stratum (NAS) elements.
  • EUTRAN Evolved UTRAN
  • a central processing unit (CPU) 204e of the baseband circuitry 204 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers, and/or NAS.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 204f.
  • DSP audio digital signal processor
  • the audio DSP(s) 204f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 204 and the application circuitry 202 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 204 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 204 may support communication with an EUTRAN and/or other wireless metropolitan area networks (VVMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • VVMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • the device can be configured to operate in accordance with communication standards or other protocols or standards, including Institute of Electrical and Electronic Engineers (IEEE) 802.16 wireless technology (WiMax), IEEE 802.11 wireless technology (WiFi) including IEEE 802.11 ad, which operates in the 60 GHz millimeter wave spectrum, various other wireless technologies such as global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE radio access network (GERAN), universal mobile telecommunications system (UMTS), UMTS terrestrial radio access network (UT AN), or other 2G, 3G, 4G, 5G, etc. technologies either already developed or to be developed.
  • RF circuitry 206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204.
  • RF circuitry 206 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for transmission.
  • the RF circuitry 206 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 206 may include mixer circuitry 206a, amplifier circuitry 206b and filter circuitry 206c.
  • Hie transmit signal path of the RF circuits" ⁇ ' 206 m ay include filter circuitry 206c and mixer circuitry 206a.
  • RF circuitry 206 may also include synthesizer circuitry 2()6d for synthesizing a frequency for use by the mixer circuitry 206a of the receive signal path and the transmit signal path.
  • the mixer circuitry 206a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206d.
  • the amplifier circuitry 206b may be configured to amplify the down-converted signals and the filter circuitry 206c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 204 for further processing.
  • the output baseband signals may be zero-fre uency baseband signals, although this is not a requirement.
  • mixer circuitry 206a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitiy 206a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206d to generate RF output signals for the FEM circuitry 208.
  • the baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206c.
  • the filter circuitry 206c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect,
  • the rrrixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 204 may include a digital baseband interface to communicate with the RF circuitry 206.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 206d may be a fractional-N svntiiesizer or a fractional N/N+ l svntiiesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 206d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 206d may be configured to synthesize an output frequency for use by the mixer circuitry 206a of the RF circuitry 206 based on a frequency input and a divider control input.
  • the synthesizer circuitry 206d may be a fractional N N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitiy 204 or the applications processor 202 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from, a lookup table based on a channel indicated by the applications processor 202.
  • Synthesizer circuitrv' 206d of the RF circuitry 206 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a cam' out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 206d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitiy to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (flo).
  • the RF circuitry 206 may include an IQ/polar converter,
  • FEM circuitry 208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify' the received signals and provide the amplified versions of the received signals to the RF circuitiy 206 for further processing.
  • FEM circuitry 208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 210.
  • the FEM circuitry 208 may include a TX RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 206).
  • LNA low-noise amplifier
  • the transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 210.
  • PA power amplifier
  • the communication device 200 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface as described in more detail below.
  • the communication device 200 described herein may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless
  • PDA personal digital assistant
  • the communication device 200 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the sy stem.
  • the communication device 200 may include one or more of a keyboard, a keypad, a touchpad, a display, a sensor, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, one or more antennas, a graphics processor, an application processor, a speaker, a microphone, and other I/O components.
  • the display may be an LCD or LED screen including a touch screen.
  • the sensor may include a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit.
  • the positioning unit may communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.
  • GPS global positioning system
  • the antennas 2 ! 0 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals.
  • the antennas 210 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • the communication device 200 is illustrated as having several separate functional elements, one or more of the functional elements may ⁇ be combined and may be implemented by combinations of software -configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits ( FICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements may refer to one or more processes operating on one or more processing elements.
  • Embodiments may be implemented in one or a combination of hardware, firmware and software. 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 mechanism for storing information in a form readable by a machine (e.g., a computer).
  • a computer-readable storage device may include readonly memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
  • Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
  • the device may be a UE, for example, such as the UE shown in FIG. 1.
  • the physical layer circuitry 302 may perform various encoding and decoding functions that may include formation of baseband signals for transmission and decoding of received signals.
  • the communication device 300 may also include medium access control layer (MAC) circuitry 304 for controlling access to the wireless medium.
  • the communication device 300 may also include processing circuitry 306, such as one or more single-core or multi-core processors, and memory 308 arranged to perform, the operations described herein.
  • the physical layer circuitry 302, MAC circuitry 304 and processing circuitry 306 may handle various radio control functions that enable communication with one or more radio networks compatible with one or more radio technologies.
  • the radio control functions may include signal modulation, encoding, decoding, radio frequency shifting, etc.
  • communication may be enabled with one or more of a WMAN, a WLAN, and a WPAN.
  • the communication device 300 can be configured to operate in accordance with 3GPP standards or other protocols or standards, including WiMax, WiFi, WiGig, GSM, EDGE, GERAN, UMTS, UTRAN, or other 3G, 3G, 4G, 5G, etc. technologies either already developed or to be developed.
  • the communication device 300 may include transceiver circuitr 7 312 to enable communication with other external devices wirelessly and interfaces 314 to enable wired communication with other external devices.
  • the transceiver circuitry 312 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range.
  • RF Radio Frequency
  • the antennas 301 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some MIMO embodiments, the antennas 3 1 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • the communication device 300 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including DSPs, and/or other hardware elements. For example, some elements may comprise one or more
  • the functional elements may refer to one or more processes operatmg on one or more processing elements.
  • Embodiments may be implemented in one or a combination of hardware, firmware and software. 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.
  • FIG. 4 illustrates another block diagram of a communication device in accordance with some embodiments.
  • the communication device 400 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.
  • the communication device 400 may operate in the capacity of a server communication device, a client communication device, or both in server- client network environments.
  • the communication device 400 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the communication device 400 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device.
  • the term ' " communication device" shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • modules are temporari ly configured, each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Communication device 400 may include a hardware processor 402 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a mam memory 404 and a static memory 406, some or all of which may communicate with each other via an interlink (e.g., bus) 408.
  • a hardware processor 402 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • a mam memory 404 e.g., RAM
  • static memory 406 e.g., static memory
  • the communication device 400 may further include a display unit 41 , an alphanumeric input device 412 (e.g., a keyboard), and a user interface (UI) navigation device 414 (e.g., a mouse).
  • the display unit 410, input device 412 and UI navigation device 414 may be a touch screen display.
  • the communication device 400 may additionally include a storage device (e.g., drive unit) 416, a signal generation device 418 (e.g., a speaker), a network interface device 420, and one or more sensors 421, such as a global positioning system (GPS) sensor, compass, acceierometer, or other sensor.
  • GPS global positioning system
  • the communication device 400 may include an output controller 428, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 416 may include a communication device readable medium 422 on which is stored one or more sets of data structures or instructions 424 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 424 may also reside, completely or at least partially, within the main memory 404, within static memory 406, or within the hardware processor 402 during execution thereof by the communication device 400.
  • one or any combination of the hardware processor 402, the main memory 404, the static memory 406, or the storage device 416 may constitute communication device readable media.
  • the term "communication device 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 424.
  • the term "communication device readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 400 and that cause the communication device 400 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 communication device readable medium examples may include solid-state memories, and optical and magnetic media.
  • communication device readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices
  • magnetic disks such as internal hard disks and removable disks
  • magneto-optical disks Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • communication device readable media may include non-transitory communication device readable media.
  • communication device readable media may include communication device readable media that is not a transitory propagating signal .
  • the instructions 424 may further be transmitted or received over a communications network 426 using a transmission medium via the network interface device 420 utilizing any one of a number of transfer protocols (e.g., frame relay , internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay , internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., IEEE 802.11 family of standards known as WiFi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802, 15.4 family of standards, a LTE family of standards, a UMTS family of standards, peer-to-peer (P2P) networks, among others.
  • the network interface device 420 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 426.
  • the network interface device 420 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple -output
  • the network interface device 420 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 400, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
  • a tUE such as a wearable device or vehicle-embedded device, may be temporarily or permanently constrained to communicate with the EUTRAN through a nUE.
  • Several tUEs may be associated with a particular nUE to form a PAN .
  • a large number of nUEs may be located in a particular geographical region served by a single EUTRAN.
  • Each nUE may be associated with a different PAN, which may create a high density network scenario.
  • the RAN may furthermore assign a common resource pool for wearable communication. This resource pool may be shared among all of the PANs in the geographical area and within each PAN on a contention -based resource access basis.
  • Each nUE may have two higher layer protocol stacks, one for the Xu-s interface with the tUE and one for the Xu-d interface with the EUTRAN.
  • the tUEs may have the same two higher layer protocol stacks or may have a single higher layer protocol stack for one for the Xu-s interface with the nUE.
  • Physical resource allocation (PRA) handling by the nUE may involve several procedures to make challenging decisions in the PAN.
  • a first decision includes allocation of uplink (UL) and downlink (DL) subframes within a particular frame of the time division duplexing (TDD) system that uses the Xu- s interface.
  • the nUE may also decide scheduling among one or more tUEs with different buffer sizes in a given DL subframe. Similarly, for a given DL subfrarne the nUE may decide scheduling ⁇ ' ⁇ one o iTio c tu Es with different buffer sizes.
  • the nUE scheduling may be flexible enough to accommodate tUEs with different UL and DL priorities.
  • UL and DL scheduling provided by the nUE may not be limited solely to new tUE transmissions, that is, it may be desirable for the nUE to effectively schedule resources for hybrid automatic repeat request (HARQ) tUE retransmissions in addition to new tUE transmission scheduling.
  • HARQ hybrid automatic repeat request
  • signaling mechanisms between the nUE and tUEs may enable the nUE to efficiently make scheduling decisions. For example, the nUE may use information of buffered data at each of the tUEs for UL transmission scheduling. Similarly, the nUE may transmit the UL or DL scheduling information to the associated tUEs. To address these issues, various procedures and signaling mechanisms are provided for scheduling and resource assignment in 5G R-Things Sidelmk communication system.
  • FIG. 5 illustrates a protocol stack in accordance with some embodiments.
  • the protocol stack may be provided in any of the nUEs or tUEs described in FIGS. 1-4.
  • the higher layer protocol stack (tSL-HL) 504 may refer primarily to the protocol layers between the PHY (tSL-PHY) 506 and
  • the tSL-HL 504 may refer to one or more of the MAC, RLC and PDCP layers of legacy LTE protocol layers.
  • FIGS. 6A and 6B illustrate downlink and uplink subframe structures in accordance with some embodiments.
  • the DL and UL subframe structures 610, 630 may be used by any of the nUEs or tUEs shown in FIGS. 1 - 5.
  • Each DL and UL subframe 610, 630 may be 1ms, although other
  • Each DL and UL subframe 6 ! 0, 630 may be divided into multiple physical resource blocks (PRB) in the frequency domain in which each PRE may occupy 3 subcarriers over one subframe. For a subcarrier spacing of 60 kHz and subframe duration of 1ms, each PRB may occupy 180 kHz over 1 ms.
  • the PRBs may be grouped into subchannels in which each subchannel occupies 6 PRBs consecutive in the frequency domain. The minimum system bandwidth is of the size of a subchannel.
  • the channels may be transmitted on a PRA, which may be an aggregation of multiple continuous PRBs.
  • Each DL and UL subframe 610, 630 may be divided into a number of sections, each of which is addressed to the same tUE.
  • the first symbol in the subframe 610, 630 may be a common control channel 612 and may indicate whether the data channel 622 is an UL or DL data channel.
  • the common control channel 612 may be a DL common control channel independent of whether the data channei 622 in the subframe 610, 630 is UL or DL.
  • the common control channel 612 may have a 10 bit payload in which the UL/DL indication is a single bit.
  • the DL common control channei 612 may be followed by a
  • the TAS channel 616 may be a DL channel in the DL subframe 610 and an UL channel in the UL subframe 630.
  • the TAS channel 616 may be used by the transmitter to transmit a reference signal for measurement by the receiver. For example, in the DL subframe 610, the nUE may transmit the reference signal and the tUE may measure the reference signal.
  • the TAS channel 616 may have a 6 bit payload in which the new data indicator (NDI) is a single bit with a 2 bit repetition and 3 bit CRC.
  • NDI new data indicator
  • a Receiver resource Acknowledgement and Sounding (RAS) channel 618 may be provided subsequent to the TAS channel 616, The receiver, e.g., the tUE in the RAS channel 618 in the DL subframe 610, may transmit the measurement to the transmitter (nUE in the DL subframe 610).
  • the RAS channel 618 may provide a CSI and power head room (PHR) report.
  • the RAS channel 618 may have a 10 bit pay load in which the modulation and coding scheme (MCS) is 4 bits with a 2 bit PHR and 4 bit CRC.
  • MCS modulation and coding scheme
  • the TA S and RAS channels 616, 618 may be followed by a DL data channel 622 in a DL subframe 610, or UL data channel in an UL subframe 630.
  • the data channel 622 may contain data provided from the transmitter to the receiver. This data may include ID and security information or user data.
  • the data channel 622 may be followed by an ACK/NACK channel 624,
  • the ACK/NACK channel 624 may contain a response to transmission of the data in the data channel 622 and be used by the transmitter to determine whether retransmission of the data in the data channel 622 is to occur.
  • the ACK/NACK channel 624 may have a 10 bit payload in which the
  • ACK/NACK is 2 bits with a 4 bit buffer status report (BSR) in a DL subframe 610 indicating whether data is present for transmission and 4 bit CRC.
  • BSR buffer status report
  • Tire guard periods 614 may be used to reduce inter-symbol interference or permit the tUE to switch between the transmitter and receiver chains. At least some of the guard periods 614 may have different lengths. For example, the guard periods between the DL common control channel 612 and the TAS channel 616, between the TAS channel 616 and the RAS channel 618 and after the ACK/NACK channel 624 may occupy 1 symbol (17.7 , us total), the guard period 614 between the RAS channel 618 and the data channel 622 may occupy 1 symbol + 8.33 ⁇ $ (26.03
  • a majority of the subchannels in the system may be used to provide data between UEs. However, one or more of the subchannels may be reserved for control signaling. For example, 1-2 resource elements (REs) of one of the central 6 PRBs in the first DL subframe of each frame may provide broadcast channel information, as well as paging and discovery information. 1 RE may be defined as 1 subcarrier over 1 symbol, 1 resource unit (RU) may be defined as 3 subcarriers over 4 consecutive symbols (in total 12 REs).
  • the DL common control channel, the TAS channel, the RAS channel and the ACK channel may each occupy one RU, while the data channel may occupy the 3 subcarriers over 34 symbols.
  • the total subframe in this embodiment may thus extend over 56 symbols (including the above guard periods).
  • the nUE may transmit scheduling decisions in the common control channel of an UL subframe and in the TAS channel in a DL subframe. It is desirable for the number of PRAs for UL transmission for a tUE to be based on the buffer size of the tUE, that is, the amount of data that the tUE has to transmit to the nUE.
  • the amount of data to be carried on each PRA in the data channel may be unknown in the scheduling phase - the amount of data on each PRA (and thus number of PRAs to transmit the data) may instead be determined by the nUE after the RAS channel as the MCS is contained in the RAS channel. This leads to the nUE using an estimate of the MCS efficiency when determining the scheduling for the tUE,
  • FIG. 7 illustrates a flowchart of scheduling and resource allocation in accordance with some embodiments.
  • the method may be performed by any nUE shown in FIGS. 1-4.
  • the various operations described may have an order different from that shown in FIG. 7.
  • the order of operations 706 and 708 may be switched.
  • the order of these and other operations may be changed.
  • some of the operations shown in FIG. 7 may be combined.
  • the nUE may schedule new transmissions and HARQ retransmissions at the same time.
  • the nUE may at operation 702 determine the subframe direction in each subframe of a frame in a TDD system.
  • the subframe direction may be UL or DL.
  • the nUE may use various parameters and methods to determine the DL/UL priority for a particular subframe within the TDD frame.
  • the nUE may determine the subframe direction at different granularities.
  • the granularity may extend from a single subframe (the next subframe) to multiple subframes after the current subframe.
  • the subframes may include the next subframe and extend for the subframes across an entire frame or more.
  • the UL/DL determination for multiple subframes may be simultaneously performed by the nUE.
  • the DL or UL subframe indication for a subframe may be transmitted sent at the beginning of each subframe.
  • the nUE can decide the UL or DL direction for a subframe n at the end of subframe n-1 or at the beginning of subframe n.
  • the next subframe may refer to the current subframe when the UL or DL subframe decision for subframe n is made at the beginning of subframe n.
  • the parameters that can be used to determine the subframe direction by the nUE include the DL/UL subframe ratio.
  • the DL UL subframe ratio can be decided based on the ratio of pending DL data to reported UL data.
  • Each of the UL and DL data may include both new and/or retransmission data.
  • An additional parameter used to determine the subframe ratio may be the number of tUEs with pending DL data to the number of tUEs with reported UL data.
  • Hie nUE may also use the ratio of pending mission critical/ultra-high reliability and low latency communication (MC/URLLC) DL data amount to reported mission critical/URLLC UL data amount.
  • MC/URLLC mission critical/ultra-high reliability and low latency communication
  • Each of the UL and DL MC/URLLC data, as above, may include both new and/or retransmission data.
  • the number of tUEs with reported UL data may be different than the number of tUEs with UL data. Th e num ber of tUEs with reported UL data may represent only those tUEs that have UL data and have also informed the nUE about the reported UL data.
  • the UL data may be received at the nUE in a buffer status report (BSR) from the tUE. Only reported data may count towards the data pending for UL transmission.
  • BSR buffer status report
  • AN UL/DL subframe direction selection decision for each subframe may use some or all of the above parameters.
  • a scheduling decision may depend on which subframe within the frame the UL/DL subframe direction selection decision (referred to herein as subframe n) is being made, that is, the location of the subframe within the frame. For example, if subframe n is the first subframe of the frame (subframe 0), the nUE may schedule subframe n as a DL subframe to allow for control signaling between the nUE and tUEs. On the other hand, if subframe n is the last subframe of a frame, reported UL data is pending, and no UL subframe was scheduled in the frame, the nUE may schedule subframe n as an UL subframe.
  • the nUE schedule may depend on whether or not any MC/URLLC data is pending for transmission. If MC/URLLC data is pending for transmission, whether UL or DL, the scheduling may further depend on which type(s) of data are pending for transmission by the tUEs. in some embodiments, if only DL MC/URLLC data pending, subframe n may be scheduled as a DL subframe; if only UL MC/URLLC data pending, subframe n may be scheduled as an UL subframe.
  • the nUE may schedule subframe n as UL.
  • the nUE may schedule subframe n as UL. If no UL MC/URLLC data was present in the previous subframe, the disposition of subframe n may be based on the data pending.
  • the nUE may schedule subframe n as a DL subframe: if the number of tUEs with UL MC/URLLC data is greater than the number of tUEs with DL MC/URLLC data, the nUE may schedule subframe n as an UL subframe; and if the number of tUEs with UL MC/URLLC data is equal to the number of tUEs with DL MC/URLLC data, the nUE may schedule subframe n as an UL or DL subfrarne with equal probability. In this last case, the nUE may- schedule subframe n as an UL or DL subframe randomly.
  • the nUE may use priority information of the subframe.
  • the priority information may depend on the amount of new transmission data, the amount of retransmission data and the number of tUEs with pending data.
  • the nUE may calculate the DL subframe priority
  • the DL parameters may be normalized - for example, the amount of DL data pending for new transmission may be normalized based on the total amount of UL and DL data pending for new transmission.
  • the UL parameters may again be normalized - for example, the amount of UL data pending for new transmission may be normalized based on the total amount of UL and DL data pending for new transmission.
  • the nUE may determine the direction of subframe n using the calculated priorities DL_sf_priority and UL_sf_priority. Specifically, if
  • the nUE may schedule subframe n as a DL subframe, while if UL sf priority is greater than DL sf priority, the nUE may schedule subframe n as an UL subframe. If DL sf priority and
  • the nUE may schedule subframe n as an UL or DL subframe with equal probability. In this last case, the nUE may schedule subframe n as an UL or DL subframe randomly.
  • the 2.4 may estimate the number of PRAs for one or more of the tUEs in the PAN.
  • the number of PRAs to be assigned by the nUE for a particular tUE may be based on the amount of data to be transmitted or received by the particular tUE, as indicated to the nUE by the particular tUE prior to the estimation.
  • the data to be transmitted by the particular tUE may be the amount of data indicated to the nUE as being buffered in a memory of the particular tUE.
  • the nUE may repeat this for each tUE in the PAN.
  • the number of PRAs also referred to herein as the grant size, for a given PDU size determination may be dependent on the Modulation and Coding Scheme (MCS).
  • Scheduling may be performed at the nUE, however, before estimating or obtaining channel information such as the MCS.
  • the scheduler at the nUE which may be in the processor, may thus initially estimate the number of PRAs for a tUE to transmit data in buffer.
  • a history of the previous cha nel quality can be maintained to permit the nUE to make this estimation.
  • the MCS history may be retained for one or more frames such that the MCS of a subframe is removed as new MCS information is obtained from the tUEs.
  • a mid-level MCS and buffer size of available data for transmission may be used by the nUE to estimate number of PRAs to be allocated to a tUE.
  • the mid-level MCS may be an intermediate MCS level among the possible MCS levels allowed in the sidelink communication system.
  • the estimated MCS may be determined from the MCS history, for example either an average or a median of the MCS history.
  • the MCS level selected by the nUE may be dependent on the type of data; for example, when URLLC data is to be transmitted, the lowest allowable MCS level may be used by the nUE,
  • the nUE may schedule UL subframes and allocate PRAs among the tUEs. To accomplish this, the nUE may calculate the amount of resources to be used by the tUEs for UL transmissions and thereby identify the number of UL subframes in the TDD frame. The nUE may convey the UL scheduling information to the tUEs for which UL transmissions are to be assigned. The UL scheduling information may thus be received by the tUEs. In various embodiments, tlie nUE may schedule UL subframes for from 0 to all tUEs in the PAN.
  • the nUE may schedule DL subframes and allocate PRAs among the tUEs. Similar to the above operation, the nUE may identify the number of DL subframes in the TDD frame and calculate the amount of resources to be used by tlie tUEs for DL transmissions from the nUE to the tUEs.
  • the DL transmissions may originate at the nUE or may be transmitted from the EUTRAN through the nUE to the tUEs.
  • the nt J may convey the DL scheduling information to at least the tUEs associated with the DL transmissions for reception at the tUEs.
  • the nUE may schedule DL subframes for from 0 to all tUEs in the PAN.
  • the nUE may receive from each tUE that has
  • the nUE may receive a BSR or scheduling request (SR) from each such tUE to indicate UL data pending for transmission.
  • the BSR may provide the estimated UL data amount pending for new transmission as well as for retransmission.
  • the BSR may report the amount of new transmission and retransmission data, in separate fields of a BSR control element. The nUE may thus have information about UL data amount pending for (re)transmission and number of tUEs with UL data pending for (retransmission.
  • a DL control channel may be present at the beginning of each subframe in each frame.
  • the DL control channel may indicate whether the subframe is a DL or UL subframe.
  • a tUE-specific similar control channel may cam' a DL or UL subframe indication along with UE- specific UL scheduling information in the UL subframe or UE-specific DL scheduling information in the DL subframe .
  • scheduling information may be transmitted to each tUE that has transmitted a BSR or SR.
  • a PRA may be provided in which a DL/UL indication may be scrambled with a PAN -wide ID.
  • the PAN-wide ID may be tlie nUE ID, a discovery ID for the PAN, or any othe predetermined ID.
  • the use of a PAN-wide ID permits tUEs that want to join the network but may not have a tUE-specific Temporary ID to decode the DL/UL indication.
  • the location of the PRA may be fixed or may be deterministic, based on say, the nUE ID.
  • each tUE may obtain a tUE-specific control search space at the beginning of each subframe.
  • the tUE may monitor a DL control message that is scrambled with the tUE temporary ID to obtain UL scheduling information along with the DL/UL indication.
  • the tUE-specific control search space may be for one or only a few (e.g., 2-4) PRAs.
  • the scheduling information may carry actual PRA allocation, such as the starting PRA number and the number of contiguous PRAs.
  • the DL control message may use 1 bit to indicate the DL/UL subframe indication, 7 bits to specify the starting PRA number; and 4 bits to indicate the number of PRAs allocated. This means that a maximum of 16 PRAs can be allocated to one tUE. In other embodiments, the number of bits used in one or more of these fields may be different.
  • a tUE- specific control channel may be spread over multiple PRAs (mPRA), 2PRA for example, in the first symbol of the subframe. This may limit the maximum number of tU Es that can be scheduled simultaneously to a floor [(max)
  • the tUE-specific DL control search space may not be used solely for a single tUE.
  • the DL control search space can be shared among more than one tUE in cases in which the PAN contains a large number of active tUEs.
  • the nUE may schedule the tUEs in different subframes by applying a scheduling algorithm. For example, the nUE may assign a tUE with MC/URLLC data the highest priority, or at least a higher priority than a tUE with non-MC/non-URLLC data.
  • the nUE may at operation 710 determine resource allocation fairness among the tUEs in the PAN.
  • the nUE may maintain fairness among the scheduled tUEs through the use of a credit-based scheduling mechanism.
  • Credit-based scheduling may not be the only basis for allocating the PAN resources.
  • the nUE may also use priority-based UL/DL scheduling and resource allocation for the tUEs.
  • the nUE may use priority-based and credit-based scheduling of tUEs in an UL subframe for UL transmission and for DL subframe for DL transmission.
  • a scheduling decision for subframe n may take place at the end of subframe n-1 or at the beginning of subfranie n after deciding that subframe n is an UL subframe.
  • the nUE may obtain the number oftUEs with pending regular (non-MC/non-URLLC) UL data, the amount of new
  • the nUE may schedule the tUE in subframe n and allocate PRAs to an amount dependent on the amount of UL data of the tUE.
  • the number of PRAs may be the minimum of: the maximum allowed PRA allocation and the estimated number of PRAs to transmit all pending URLLC data. If multiple tUEs have URLLC data to transmit, the nUE may schedule the tUEs using a predetermined pattern. For example, the nUE may allocate PRAs sequentially or in a round robin fashion.
  • the nUE may schedule the first tUE, then the second tUE, then the third tUE before scheduling the first tUE again, etc.
  • the nUE may allocate PRAs in a manner similar to the above, that is the number of PRAs may ⁇ be die minimum of: the maximum allowed PRA allocation and the estimated number of PRAs to transmit ail pending URLLC data for the tUE.
  • the nUE may then calculate the remaining unallocated PRAs. If the number of PRAs remaining is not zero, the nUE may serve tUEs with non- URLLC data. The nUE may first serve the maximum number of tUEs that have UL credit from previous subframes. In some embodiments, the nUE may serve the tUEs with an allocation equal to the minimum of: the UL credit associated with the tUE and the estimated number of PRAs to transmit all data of the tUE. If all tUEs having non-URLLC data cannot be accommodated, the nUE may select tUEs to be served in subframe n with equal probability, e.g., randomly. For fairness, once tUEs having non-URLLC data have been served, the nUE may reduce the UL credit of the served tUEs by the served amount and may retain UL credit for the unserved tUEs in memory.
  • the nUE may divide the remaining PRAs equally among tUEs with pending regular data. If the number of PRAs after equal distribution is greater than the minimum allowed PRA allocation, the nUE may schedule all tUEs. The allocation to each tUE in this case may be equal to the minimum of the number of PRAs from equal distribution and the estimated number of PRAs to transmit all data of the tUE.
  • the nUE may accommodate the maximum number of tUEs at least with an allocation of the minimum of: the minimum allowed number of PRAs and the estimated number of PRAs to transmit all data of the tUE.
  • the nUE may maintain a record of unserved tUEs in memory and allocate the tUEs an UL credit equal to the minimum allowed number of PRAs for the next UL subframe. The nUE may then serve these tUEs with the UL credit amount of allocation in next UL subframe.
  • DL scheduling by the nUE may be similar to UL scheduling, with some differences.
  • the nUE retains information regarding DL data for new transmission and retransmission for each tUE without a BSR or SR from the tUE.
  • the DL control channel may be present at the beginning of each subframe in each frame and a PRA may be provided in which a DL UL indication may be scrambled with a PAN -wide ID.
  • the nUE may provide the tUE with the tUE-specific control search space where the scheduling information may be provided.
  • the DL control message and tUE-specific control channel may be similar to that indicated above and may provide DL scheduling information.
  • the nUE may have information regarding the number of tUEs with pending regular DL data, as well as the amount of new transmission and retransmission regular data of each of the tUEs, the number of tUEs with pending URLLC DL data, and the amount of new transmission and retransmission U RLLC data of each of the tUEs with URLLC data.
  • tUEs with a particular type of data are treated equally within the class of data but tUEs with URLLC data may have a higher priority than those without URLLC data.
  • the nUE may serve tUEs with pending DL data in a similar manner as those with pending UL data. Similar to the above, if only one tUE has URLLC data to be received from the nUE, the nUE may schedule the tUE in subframe n and allocate PRAs per the minimum of: the maximum allowed PRA allocation and the estimated number of PRAs to transmit all pending URLLC data to the tUE. If multiple tUEs have URLLC data to be received, the nUE may schedule the tUEs using a predetermined pattern that may be the same as UL scheduling or may be different. The nUE may allocate PRAs for each tUE as the minimum of: the maximum allowed PRA allocation and the estimated number of PRAs to transmit all pending URLLC data to each tUE.
  • the nUE may then calculate the remaining unallocated PRAs. If the number of PRAs remaining is not zero, the nUE may provide PRAs for tUEs for which non-URLLC data is to be provided by the nUE. The nUE may first serve the maximum number of tUEs that have DL credit from previous subframes. In some embodiments, the nUE may serve the tUEs with an allocation equal to the minimum of: the DL credit associated with the tUE and the estimated number of PRAs to transmit all data to the tUE. If all tUEs to which non-URLLC data is to be provided from the nUE cannot be
  • the nUE may select tUEs to be served in subframe n with equal probability. For fairness, once tUEs having non-URLLC data have been served, the nUE may reduce the DL credit of the served tUEs by the served amount and may retain DL credit for the unserved tUEs in memory.
  • the nUE may divide the remaining PRAs equally among tUEs with pending regular data for the tUEs. If the number of PRAs after equal distribution is greater than the minimum allowed PRA allocation, the nt j may schedule DL transmissions to ail tUEs. The allocation for each tUE in this case may be equal to the minimum of the number of PRAs from equal distribution and the estimated number of PRAs to transmit all data to the tUE.
  • the nUE may accommodate the maximum number of tUEs at least with an allocation of the minimum of: the minimum allow ed number of PRAs and the estimated number of PRAs to transmit all data to the tUE.
  • the nUE may maintain a record of unserved tUEs in memoiy and allocate the tUEs a DL credit eq ual to the minimum allowed number of PRAs for the next UL subframe. The nUE may then serve these tUEs with the DL credit amount of allocation in next DL subframe.
  • new transmissions are not the only transmissions that may be scheduled by the nUE.
  • the nUE may also schedule and allocate resources for HARQ retransmissions.
  • HARQ ACK NACK scheduling may be per PRA. That is, transmission on each PRA may be retransmitted until a HARQ ACK is receiv ed or a maximum number of HARQ retransmissions reached.
  • the tUE may have acquired multiple contiguous PRAs for an original transmission in an subframe. If a tUE has multiple contiguous PRAs in a subframe, different options may be used by the nUE for wHL PDU generations.
  • a single PDU may be used for all contiguous
  • a HARQ process may maintain multiple HARQ ACK/NACK state variables for a PDU at the transmit entity (in the memory of the nUE for DL transmissions or the tUE for UL transmissions). The number of variables may be equal to the number contiguous PRAs.
  • a peer HARQ process at the receive side may wait for a successful reception of all PRAs-data before decoding the PDU. An unsuccessful transmission of any part of the PDU, that is transmission of any PRA that has failed after a maximum HARQ retransmission, may indicate that the entire PDU has failed.
  • the first PRA number may be used to decide the HARQ process number or ID.
  • the first PRA number may be the lowest index of contiguous PRAs.
  • multiple PDUs may be used, one PDU for each PRA.
  • HARQ retransmission two types of scheduling can be used.
  • a predetermined schedule may be used for HARQ Retransmission.
  • the PRAs can be same as those for original transmission or can be determined from original PRAs and/or previous retransmission PRAs.
  • the HARQ retransmission can be performed in next same direction subframe or the subframe can be determined from the original transmission subframe and/or previous retransmission subframe.
  • an ACK from the nUE may be lost, in which case the tUE may assumes the response is a NACK, or the ACK bit may toggle (be distorted), which may indicate a NACK to the tUE.
  • the nUE may allocate the HARQ retransmission resource for a new transmission to another tUE, potentially resulting in a collision between the new transmission and the HARQ retransmission from different tUEs within the PAN.
  • a NACK may occur due to an inter-PAN collision.
  • the tUEs colliding for a new transmission may also collide during HARQ retransmission as the predetermined schedules of the tUEs from different PANs may be same.
  • dynamic scheduling may be used by the nUE for HARQ retransmission.
  • the nUE may schedule the HARQ retransmission based on the URLLC and/or credit considerations above.
  • the use of dynamic scheduling may provide the nUE with more flexibility at the cost of additional DL control signals to send scheduling information from the nUE to the tUE.
  • Example 1 is an apparatus of user equipment (UE), the apparatus comprising; a memory; and processing circuitry in communication with the memory and arranged to: decode, from another UE in a personal area network (PAN) comprising the UE and the other UE, a buffer status report (BSR) comprising an amount and type of pending uplink (UL) data buffered for transmission from the other UE to the UE, the BSR provided through a sidelink interface; determine, based on the BSR, whether a next subframe for communication with the other UE is an UL or downlink (DL) subframe; and send, for transmission to the other UE through the sidelink interface, an indication of whether the next subframe is an UL or DL subframe.
  • PAN personal area network
  • BSR buffer status report
  • Example 2 the subject matter of Example 1 optionally includes, wherein: a determination of whether the next subframe is an UL or DL subframe is dependent on at least one of: (i) a ratio of an amount of pending DL data, to be transmitted from the UE to other UEs in the PAN through the sidelink interface, to an amount of reported UL data from BSRs of the other UEs, (ii) a ratio of a number of the other UEs with pending DL data to a number of the other UEs with reported UL data, or (iii) a ratio of an amount of pending ultra- high reliability and low latency communication (URLLC) DL data to an amount of reported URLLC UL data.
  • a determination of whether the next subframe is an UL or DL subframe is dependent on at least one of: (i) a ratio of an amount of pending DL data, to be transmitted from the UE to other UEs in the PAN through the sidelink interface, to an amount of reported UL data from
  • Example 3 the subject matter of any one or more of Examples
  • processing circuitry is further configured to: schedule the next subframe as a DL subframe when the next subframe is a first subframe of a frame, and schedule the next subframe as an UL subframe when the next subframe is a last subframe of the frame, the BSR indicates that pending UL data is present, and all oilier subframes in the frame are DL subframes.
  • Example 4 the subject matter of Example 3 optionally includes, wherein: when the subframe is neither the first nor last subframe in the frame, the processing circuitry- is further configured to: schedule the next subframe as a DL subframe in response to a determination that ultra-high reliability and low latency communication (URLLC) DL data is pending and the BSR indicates that the other UE is free from pending URLLC UL data, schedule the next subframe as an UL subframe in response to a determination that the BSR indicates that URLLC UL data is pending and the UE is free from pending URLLC DL data,
  • URLLC ultra-high reliability and low latency communication
  • Example 5 the subject matter of Example 4 optionally includes, wherein: in response to the BSR indicating that URLLC UL data is pending the other UE and a determination that URLLC DL data is pending: schedule the next subframe as an UL subframe in response to a determination that the current subframe is a DL subframe due to the presence of URLLC DL data, schedule the next subframe as a DL subframe in response to a
  • the current subframe is an UL subframe due to the presence of URLLC UL data, and otherwise: schedule the next subframe as a DL subframe in response to a number of other UEs in the PAN to which URLLC DL data is to be transmitted being greater than a number of other UEs in the PAN having URLLC UL data, schedule the next subframe as an UL subframe in response to the number of other UEs having URLLC UL data being greater than the number of other UEs to which URLLC DL data is to be transmitted from the UE.
  • Example 6 the subject matter of any one or more of Examples
  • processing circuitry is further configured to: in response to a determination that BSRs from other UEs in the PAN, with winch the UE communicates through the side link interface, indicate that the other UEs are free from ultra-high reliability and low latency communication (URLLC) UL data, the UE is free from pending URLLC DL data for the other UEs, and the subframe is neither the first nor last subframe in the frame:
  • URLLC ultra-high reliability and low latency communication
  • a DL subframe priority from a sum of: al times an amount of new DL data to be transmitted to the other UEs, bl times an amount of retransmission DL data to be transmitted to the other UEs, and cl times a number of the other UEs to which DL data is to be transmitted, whether new DL data or
  • retransmission data the sum of al , b l and cl equals 1
  • calculate an UL subframe priority from a sum of: a2 times an amount of new UL data, reported by the other UEs, b2 times an amount of retransmission DL data reported by the other UEs, and c2 times a number of the other UEs reported to have U L data, whether new UL data or retransmission data, the sum of a2, b2 and c2 equals 1 , schedule the next subframe as a DL subframe in response to a determination thai the DL subframe priority being greater than the UL subframe priority, and schedule the next subframe as an UL subframe in response to a determination that the UL subframe priority being greater than the DL subframe priority.
  • Example 7 the subject matter of any one or more of Examples
  • the memory is configured to store a modulation and coding schemes (MCS) history of MCS used for communication with the other UE
  • MCS modulation and coding schemes
  • the processing circuitry is further configured to estimate, based on the BSR and an estimated MCS and prior to being provided with MCS information from the other UE in the next subframe, a number of Physical Resource Allocations (PRAs) to be used by the other UE for UL transmission in the next subframe.
  • PRAs Physical Resource Allocations
  • Example 8 the subject matter of Example 7 optionally includes, wherein the processing circuitry is further configured to at least one of: use a lowest MCS as the estimated MCS in response to the BSR indicating ultra- high reliability and low latency communication (URLLC) UL data is buffered for transmission, or otlierwise use as the estimated MCS one of a middle MCS or an average or median MCS as determined from, the MCS history.
  • the processing circuitry is further configured to at least one of: use a lowest MCS as the estimated MCS in response to the BSR indicating ultra- high reliability and low latency communication (URLLC) UL data is buffered for transmission, or otlierwise use as the estimated MCS one of a middle MCS or an average or median MCS as determined from, the MCS history.
  • URLLC ultra- high reliability and low latency communication
  • Example 9 the subject matter of any one or more of Examples 1-8 optionally include, wherein: the BSR comprises separate fields that indicate the amount of each type of pending UL data, and the type of pending UL data comprises new UL data and retransmission UL data, a DL control channel is disposed at a beginning of each subframe, the DL control channel of a particular subframe configured to indicate whether the particular subframe is a DL or UL subframe and comprising UE-specific UL scheduling information when the particular subframe is an UL subframe or UE-specific DL scheduling information when the particular subframe is a DL subframe, the UL or DL scheduling information comprising a starting Physical Resource Allocation (PRA) number and a number of contiguous PRAs, and the processing circuitry is further configured to: scramble, using a PAN-wide identification (ID), an indication of whether the particular subframe is an UL or DL subframe on a PRA, the PRA being one of fixed or dependent on an identification
  • PRA Physical
  • Example 10 the subject matter of Example 9 optionally includes, wherein: the UE-specific search space is shared among multiple other UEs, and the processing circuitry is further configured to schedule the other UEs m different subframes by applying a scheduling algorithm in which other tUEs with ultra-high reliability and low latency communication (URLLC) UL data have a highest priority.
  • the UE-specific search space is shared among multiple other UEs
  • the processing circuitry is further configured to schedule the other UEs m different subframes by applying a scheduling algorithm in which other tUEs with ultra-high reliability and low latency communication (URLLC) UL data have a highest priority.
  • URLLC ultra-high reliability and low latency communication
  • Example 1 the subject matter of any one or more of
  • Examples 1-10 optionally include, wherein: the BSR comprises separate fields that indicate the amount of each type of pending UL data, and the type of pending UL data comprises new UL data and retransmission UL data for ultra- high reliability and low latency communication (URLLC) UL data, and non- URLLC UL data, the processing circuitry is further configured to: decode BSRs from a plurality of other UEs in the PAN in the current subframe, and prioritize URLLC UEs in the PAN having URLLC UL data over non-URLLC UEs in the PAN having non-URLLC in scheduling of the other UEs for UL transmission in the next subframe.
  • the BSR comprises separate fields that indicate the amount of each type of pending UL data
  • the type of pending UL data comprises new UL data and retransmission UL data for ultra- high reliability and low latency communication (URLLC) UL data
  • non- URLLC UL data the processing circuitry is further configured to: decode BSRs from a plurality
  • Example 12 the subject matter of Example 1 optionally includes, wherein the processing circuitry is further configured to: in response to a determination that at most one of the other U Es is an UL URLLC UE, schedule the URLLC UE in the next subframe and allocate a number of Physical
  • PRAs Resource Allocations
  • Example 13 the subject matter of Example 12 optionally includes, wherein the processing circuitry is further configured to: independent of a number of U RLLC U Es, calculate a number of remaining unallocated PRAs in the next subframe, and, in response to at least one of the other UEs being a non-URLLC UE that is free from URLLC UL data: schedule a maximum number of non-URLLC UEs that have UL credit from previous subframes, an allocation for a particular non-URLLC UE equal to a minimum of: UL credit associated with the particular non-URLLC UE and an estimated number of PRAs to transmit the U L data of the particular non-URLLC UE, and reduce UL credit of the particular non-URLLC U E by the allocation, and after having scheduled the non-URLLC UEs that have UL credit and when PRAs remain to be allocated, distribute the remaining PRAs equally among remaining other UEs and: in response to a number of PRAs after distribution being greater than a minimum allowed PRA allocation
  • Example 14 the subject matter of any one or more of
  • Examples 1-13 optionally include, wherein: the processing circuitry is further configured to allocate a plurality of contiguous Physical Resource Allocations (PRAs) for an original DL transmission to the other UE when the next subframe is a DL subframe, the memory is configured to maintain a hybrid automatic repeat request (HARQ) state variable for each of the plurality of contiguous PRAs, a HARQ identification associated with original DL transmission being a lowest index of the plurality of contiguous PRAs, and the processing circuitry is further configured to decode a single HARQ Acknowledgment/Negative Acknowledgment (ACK/N ACK) for the original DL transmission from, the other UE and allocate new PRAs for a HARQ retransmission in response to reception of a NACK.
  • PRAs Physical Resource Allocations
  • HARQ hybrid automatic repeat request
  • Example 15 the subject matter of Example 14 optionally includes, wherein the processing circuitry is further configured to: schedule the HARQ retransmission in one of an immediately subsequent DL subframe or in a DL subframe determined based on at least one of the original DL transmission or a previous HARQ retransmission of the original DL transmission.
  • Example 16 the subject matter of any one or more of
  • Examples 14- 15 optionally include, wherein the processing circuitry is further configured to: dynamically schedule the HARQ retransmission based on an amount and type of pending UL and DL data in. the PAN.
  • Example 17 the subject matter of any one or more of
  • Examples 1-16 optionally include, wherein: the processing circuitry is further configured to allocate a plurality of contiguous Physical Resource Allocations (PRAs) for an original DL transmission to the other UE when the next subframe is a DL subframe, the memory is configured to maintain a hybrid automatic repeat request (HARQ) state variable for each of the plurality of contiguous PRAs, a HARQ identification associated with original DL transmission being a lowest index of the plurality of contiguous PRAs, and the processing circuitry is further configured to decode a HARQ Acknowledgment/Negative
  • PRAs Physical Resource Allocations
  • HARQ hybrid automatic repeat request
  • Example 18 the subject matter of any one or more of
  • Examples 1-17 optionally include, wherein the processing circuitry is further configured to: determine, in a single determination, whether each of a plurality of consecutive subframes immediately after the current subframe is an UL or DL subframe.
  • Example 19 the subject matter of any one or more of
  • Examples 1-18 optionally include, wherein: the processing circuitry comprises a baseband processor, and the apparatus further comprises a transceiver configured to communicate with the other UE.
  • Example 20 is an apparatus of user equipment (UE), the apparatus comprising: a memory; and processing circuitry in communication with the memory and arranged to: generate, for transmission to another UE in a personal area network (PAN) comprising the UE and the other UE through a sidelink interface, a buffer status report (BSR) comprising fields that indicate an amount of new and retransmission ultra-high reliability and low latency communication (URLLC) uplink (UL) data and an amount of new and retransmission non-URLLC UL data buffered in the memory for transmission to the other UE; determine, from an indication in a DL control channel received at the UE, whether a subframe is an UL or downlink (DL) subframe for communication with the other UE, the DL control channel comprising the indication and UE-specific scheduling information dependent on a direction of the subframe, the UE-specific scheduling information comprising a starting Physical Resource Allocation (PRA) number and a number of contiguous PRAs; and in response to a determination
  • Example 21 the subject matter of Example 20 optionally includes, wherein: whether the subframe is an UL or DL subframe is dependent on at least one of: (i) a ratio of an amount of pending DL data, to be transmitted from the other UE to UEs in the PAN through the sidelink interface, to an amount of reported UL data from BSRs of the other UEs, (ii) a ratio of a number of the UEs with pending DL data to a number of the UEs with reported UL data, or (iii) a ratio of an amount of pending URLLC DL data to an amount of reported URLLC UL data.
  • Example 22 the subject matter of any one or more of Examples 20-21 optionally include, wherein: the subframe is a DL subframe when the subframe is a first subframe of a frame, the subframe is an UL subframe when the subframe is a last subframe of the frame, the BSR indicates that UL data is present, and all oilier subframes in the frame are DL subframes, and when the subframe is neither the first nor last subframe in the frame: the subframe is a DL subframe when URLLC DL data is pending and the BSR indicates that the UE is free from URLLC UL data, the subframe is an UL subframe when that the BSR indicates that URLLC UL data is pending and the UE is free from URLLC DL data.
  • Example 23 the subject matter of Example 22 optionally includes, wherein: in response to the BSR indicating that URLLC UL data is pending at the other UE and a determination that URLLC DL data, is pending: the subframe is an UL subframe when the current subframe is a DL subframe due to the presence of URLLC DL data, the subframe is a DL subframe when the current subframe is an UL subframe due to the presence of URLLC UL data, and otherwise: the subframe is a DL subframe when a number of UEs in the PAN to which URLLC DL data is to be transmitted is greater than a number of UEs in the PAN having URLLC UL data, the subframe is an UL subframe when the number of UEs having URLLC UL data is greater than the number of UEs to which URLLC DL data is to be transmitted.
  • Example 24 the subject matter of any one or more of
  • Examples 20-23 optionally include, wherein: a number of PRAs allocated for UL transmission in the subframe, as indicated in the UE-speeific scheduling information, is based on the BSR and an estimated modulation and coding scheme (MCS), the estimated MCS is a lowest MCS of available MCSs when URLLC UL data is buffered for transmission and is otherwise a middle MCS of the available MCSs, and the processing circuitry is further configured to generate, for transmission to the other UE, MCS information in the subframe after having received the UE-specific scheduling information in the subframe.
  • MCS modulation and coding scheme
  • Example 25 the subject matter of any one or more of
  • Examples 20-24 optionally include, wherein: the processing circuitry is further configured to decode, on a particular PRA on initial access to the PAN, a first indication of whether the subframe is an UL or DL subframe and a second indication of a UE-specific search space for the UE, the particular PRA is one of fixed or dependent on an identification of the other UE, the first indication scrambled using a PAN-wide identification, and the UE-specific search space is disposed at a beginning of the subframe and is scrambled using an identification of the UE.
  • Example 26 the subject matter of any one or more of
  • Examples 20-25 optionally include, wherein: a plurality of contiguous PRAs are allocated for an original DL transmission to the UE when the subframe is a DL subframe, a hybrid automatic repeat request (HARQ) identification associated with original DL transmission is a lowest index of the plurality of contiguous PRAs, and the processing circuitry is further configured to: determine whether the original DL transmission has been successfully received, decode the original DL transmission in response to a determination that the original DL transmission has been successfully received and generate for transmission a single HARQ Acknowledgment (ACK) that indicates the original DL transmission has been successfully received, and in response to a determination that DL data in at least one of the plurality of PRAs has not been successfully received, generate for transmission a single HARQ Negative ACK (NACK) that indicates the original DL transmission has not been successfully received.
  • HARQ hybrid automatic repeat request
  • Example 27 the subject matter of Example 26 optionally includes, wherein the processing circuitry is further configured to: after transmission of the NACK, decode a HARQ retransmission of the original DL transmission in one of an immediately subsequent DL subframe or in a DL subframe determined based on at least one of: the original DL transmission, a previous HARQ retransmission of the original DL transmission, or based on an amount and type of pending UL and DL data in the PAN.
  • Example 28 is a computer-readable storage medium, that stores instructions for execution by one or more processors of a user equipment (UE), the one or more processors to: decode, from each of a plurality of other UEs in a personal area network (PAN) comprising the UE and the other UEs, a buffer status report (BSR) comprising fields that indicate an amount of new and retransmission ultra-high reliability and low latency communication (URLLC) uplink (UL) data and an amount of new and retransmission non-URLLC UL data buffered in the memory for transmission to the other UE: determine whether a subframe is an UL or downlink (DL) subframe for communication with the other UEs and schedule communications with the other UEs in the subframe, based on the BSR and an amount of new and retransmission URLLC DL data and an amount of new and retransmission non-URLLC DL data; and transmit to the other UEs through the side link interface an indication of whether the subframe is an UL
  • Example 29 the subject matter of Example 28 optionally includes, wherein: whether the subframe is an UL or DL subframe is dependent on at least one of: (i) a ratio of an amount of pending DL data, to be transmitted from the UE to the other UEs, to an amount of reported UL data from the BSRs of the other UEs, (ii) a ratio of a number of the UEs with, pending DL data to a number of the UEs with reported UL data, or (iii) a ratio of an amount of pending URLLC DL data to an amount of reported URLLC UL data.
  • Example 30 is an apparatus of user equipment (UE), the apparatus comprising: means for decoding, from each of a plurality of other UEs in a personal area network (PAN) comprising the UE and the other UEs, a buffer status report (BSR) comprising fields that indicate an amount of new and retransmission ultra-high reliabil ity and Sow latency communication (URLLC) uplink (UL) data and an amount of new and retransmission non-URLLC UL data buffered in the memory for transmission to the other UE: means for determining whether a subfranie is an UL or downlink (DL) subfranie for communication with the other UEs and schedule communications with the other UEs in the subframe, based on the BSR and an amount of new and retransmission URLLC DL data and an amount of new and retransmission non-URLLC DL data; and means for transmitting to the other UEs through the sidelink interface an indication of whether the subframe is an UL or DL subframe
  • Example 31 the subject matter of Example 30 optionally includes, wherein: whether the subframe is an UL or DL subframe is dependent on at least one of: (i) a ratio of an amount of pending DL data, to be transmitted from the UE to the other UEs, to an amount of reported UL data from the BSRs of the other UEs, (li) a ratio of a number of the UEs with pending DL data to a number of the UEs with reported UL data, or (iii) a ratio of an amount of pending URLLC DL data to an amount of reported URLLC UL data.
  • Example 32 is a method of communicating through a sidelink interface of a user equipment (UE), the method comprising: means for decoding, from each of a plurality of other UEs in a personal area network (PAN) comprising the UE and the other UEs, a buffer status report (BSR) comprising fields that indicate an amount of new and retransmission ultra-high reliability and low latency communication (URLLC) uplink (UL) data and an amount of new and retransmission non-URLLC UL data buffered in the memory for transmission to the other UE; means for determining whether a subframe is an UL or downlink (DL) subframe for communication with the other UEs and schedule communications with the other UEs in the subframe, based on the BSR and an amount of new and retransmission URLLC DL data and an amount of new and retransmission non-URLLC DL data; and means for transmitting to the other UEs through the sidelink interface an indication of whether the subframe is an UL or DL
  • Example 33 the subject matter of Example 32 optionally includes, wherein: whether the subframe is an UL or DL subframe is dependent on at least one of: (i) a ratio of an amount of pending DL data, to be transmitted from the UE to the other UEs, to an amount of reported UL data from the BSRs of the other UEs, (ii) a ratio of a number of the UEs with pending DL data to a number of the UEs with reported UL data, or (iii) a ratio of an amount of pending URLLC DL data to an amount of reported URLLC UL data.

Landscapes

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

Abstract

D'une manière générale, l'invention concerne des systèmes et des procédés de planification de transmissions D2D de liaison montante (UL) et de liaison descendante (DL). Le nUE détermine si une sous-trame est DL ou UL, et planifie des PRA sur la base de la quantité d'URLLC, de non-URLLC, de données UL et DL nouvelles et/ou de retransmission, et du nombre d'UE associés à chaque type de données. Des données de URLLC sont classées par ordre de priorité, et les attributions pour un même type de données sont distribuées de manière uniforme; des sous-trames consécutives pour un UE sont de types opposés si des données UL et DL de URLLC existent pour l'UE, et de multiples UE associés au même type de données sont attribués de manière uniforme si une quantité suffisante de PRA existe. Si les PRA sont insuffisantes pour desservir les UE, un mécanisme basé sur le crédit est utilisé, mécanisme selon lequel les UE ayant une plus grande quantité de crédit sont servis en premier. Lorsque de multiples PRA sont attribuées au même UE, une seule retransmission HARQ est planifiée soit pour chaque PRA, soit pour toutes les PRA.
PCT/US2016/068906 2016-10-14 2016-12-28 Procédures et signalisation de planification et attribution de ressources dans un système de communication de liaison latérale d'objets de nouvelle radio 5g WO2018071051A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662408378P 2016-10-14 2016-10-14
US62/408,378 2016-10-14

Publications (1)

Publication Number Publication Date
WO2018071051A1 true WO2018071051A1 (fr) 2018-04-19

Family

ID=61905917

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/068906 WO2018071051A1 (fr) 2016-10-14 2016-12-28 Procédures et signalisation de planification et attribution de ressources dans un système de communication de liaison latérale d'objets de nouvelle radio 5g

Country Status (1)

Country Link
WO (1) WO2018071051A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111316690A (zh) * 2019-12-03 2020-06-19 北京小米移动软件有限公司 信息处理方法、装置、基站、用户设备及存储介质
CN113261334A (zh) * 2018-12-27 2021-08-13 株式会社Ntt都科摩 用户装置以及通信装置
WO2022116835A1 (fr) * 2020-12-03 2022-06-09 展讯通信（上海）有限公司 Procédé et appareil de mise en œuvre de transmission de données de liaison montante, et équipement d'utilisateur
US11979238B2 (en) 2019-02-15 2024-05-07 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e. V. V2X HARQ process management

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016163762A1 (fr) * 2015-04-07 2016-10-13 Lg Electronics Inc. Procédé et appareil pour effectuer une procédure de rapport d'état de tampon pour le relais dans un système de communication sans fil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016163762A1 (fr) * 2015-04-07 2016-10-13 Lg Electronics Inc. Procédé et appareil pour effectuer une procédure de rapport d'état de tampon pour le relais dans un système de communication sans fil

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CATT: "NR frame structure for multiplexing of URLLC and eMBB traffic", RI-1608764, 3GPP TSG RAN WG1 MEETING #86BIS, 1 October 2016 (2016-10-01), XP051159111 *
HUAWEI ET AL.: "Scheduling for URLLC", R2-166991, 3GPP TSG RAN WG2 MEETING #95BIS, 1 October 2016 (2016-10-01), XP051162349 *
HUAWEI ET AL.: "Support of URLLC in UL", RL-1608845, 3GPP TSG RAN WG1 MEETING #86BIS, 1 October 2016 (2016-10-01), XP051159172 *
LG ELECTRONICS: "Discussion on control and data transmission of URLLC", RI-1609237, 3GPP TSG RAN WG1 MEETING #86BIS, 1 October 2016 (2016-10-01), XP051159349 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113261334A (zh) * 2018-12-27 2021-08-13 株式会社Ntt都科摩 用户装置以及通信装置
US11979238B2 (en) 2019-02-15 2024-05-07 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e. V. V2X HARQ process management
CN111316690A (zh) * 2019-12-03 2020-06-19 北京小米移动软件有限公司 信息处理方法、装置、基站、用户设备及存储介质
CN111316690B (zh) * 2019-12-03 2024-01-23 北京小米移动软件有限公司 信息处理方法、装置、基站、用户设备及存储介质
WO2022116835A1 (fr) * 2020-12-03 2022-06-09 展讯通信（上海）有限公司 Procédé et appareil de mise en œuvre de transmission de données de liaison montante, et équipement d'utilisateur

Similar Documents

Publication Publication Date Title
US11245480B2 (en) Devices and methods for robust measurement and data receiving
US11291079B2 (en) 5G FDD low latency transmission subframe structure system and method of use
EP3403375B1 (fr) Dispositif et procédé de cadre d'octroi de ressources destinés à la planification de largeur de bande
US10560174B2 (en) Latency reduction for wireless data transmission
US10897694B2 (en) Personal area network communication for wearable devices
WO2017099860A1 (fr) Dispositif pour une émission en liaison montante non planifiée dans le spectre non autorisé
WO2017127126A1 (fr) Dispositifs et procédés pour fournir une requête de liaison montante 5g
US11122643B2 (en) LWIP enhancements for reliable DRB switching
CN110393036B (zh) 在暂停后具有连续lbt的txop
WO2018080561A1 (fr) Rapport d'état de tampon dans des communications de liaison latérale de l'internet des objets nr 5g
US10694453B2 (en) Discovery and network access procedures for 5G things communication system
US11082950B2 (en) User equipment (UE) and method of sidelink data communication in fifth generation (5G) new radio (NR) things networks
US10749635B2 (en) Random-access and scheduling-request in new radio-things sidelink
US20170265105A1 (en) Coexistence through use of less power constrained assisted devices
WO2018080565A1 (fr) Procédures de transfert et de réception de données dans des communications de liaison latérale 5g/s
WO2018084880A1 (fr) Planification d'ue réseau assistée par nœud b évolué dans une liaison latérale d'objets de nouvelle radio 5g
WO2018071051A1 (fr) Procédures et signalisation de planification et attribution de ressources dans un système de communication de liaison latérale d'objets de nouvelle radio 5g
WO2018080566A1 (fr) Structure de sous-trame et procédure de communication pour une communication véhicule à véhicule d'objets nr 5g
WO2018031085A1 (fr) Multiples entités mac par équipement d'utilisateur
WO2017151173A1 (fr) Structure autonome à trame tdd et configuration dl-ul dans un système 5g
WO2018017161A1 (fr) Améliorations de lwa pour équipement wi-fi à trois bandes (2,4 ghz, 5 ghz et 60 ghz)
WO2017146783A1 (fr) Découverte et radiomessagerie dans une nouvelle liaison latérale d'objets radio

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

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

Country of ref document: EP

Kind code of ref document: A1