WO2020131753A1 - Techniques d'utilisation de ressources et de prise en charge de qualité de service dans des communications en liaison latérale de véhicule à tout en nouvelle radio - Google Patents

Techniques d'utilisation de ressources et de prise en charge de qualité de service dans des communications en liaison latérale de véhicule à tout en nouvelle radio Download PDF

Info

Publication number
WO2020131753A1
WO2020131753A1 PCT/US2019/066651 US2019066651W WO2020131753A1 WO 2020131753 A1 WO2020131753 A1 WO 2020131753A1 US 2019066651 W US2019066651 W US 2019066651W WO 2020131753 A1 WO2020131753 A1 WO 2020131753A1
Authority
WO
WIPO (PCT)
Prior art keywords
sidelink
message
packets
circuitry
flow
Prior art date
Application number
PCT/US2019/066651
Other languages
English (en)
Inventor
Sangeetha L. Bangolae
Youn Hyoung Heo
Ansab ALI
Kyeongin Jeong
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
Priority to CN201980043197.8A priority Critical patent/CN112385262A/zh
Priority to EP19898248.0A priority patent/EP3900430A4/fr
Publication of WO2020131753A1 publication Critical patent/WO2020131753A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • Embodiments of the present invention relate generally to the technical field of wireless communications.
  • V2X vehicle-to-everything
  • 5G fifth generation new radio
  • NR new radio
  • QoS quality of service
  • FIG. 1 schematically illustrates an example of a network comprising a user equipment (UE) and an access node (AN) in a wireless network, in accordance with various embodiments.
  • UE user equipment
  • AN access node
  • Figure 2 illustrates example components of a device in accordance with various embodiments.
  • Figure 3A illustrates an example radio frequency front end (RFFE) incorporating a millimeter Wave (mmWave) RFFE and one or more sub-millimeter wave radio frequency integrated circuits (RFICs) in accordance with some embodiments.
  • Figure 3B illustrates an alternative RFFE in accordance with various embodiments.
  • RFFE radio frequency front end
  • mmWave millimeter Wave
  • RFICs radio frequency integrated circuits
  • FIGS 4A-D illustrate some example media access control (MAC) sub-headers, in accordance with various embodiments.
  • MAC media access control
  • Figure 5A illustrates example MAC control elements (CEs) in formatting control message(s), in accordance with various embodiments.
  • Figure 5B illustrates an example MAC protocol data unit (PDU) format.
  • CEs MAC control elements
  • PDU protocol data unit
  • Figure 6A illustrates an operation flow/algorithmic structure to facilitate a process of initiating an NR V2X sidelink communication from a transmitter UE perspective from a transmitter UE perspective, in accordance with various embodiments.
  • Figure 6B illustrates an operation flow/algorithmic structure to facilitate the process of initiating an NR V2X sidelink communication from a transmitter UE perspective from a receiver UE perspective, in accordance with various embodiments.
  • Figure 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • FIG. 8 illustrates hardware resources in accordance with some embodiments.
  • the phrases“A or B” and“A and/or B” mean (A), (B), or (A and B).
  • the phrases“A, B, or C” and “A, B, and/or C” mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
  • the description may use the phrases“in an embodiment,” or“in embodiments,” which may each refer to one or more of the same or different embodiments.
  • the terms “comprising,”“including,”“having,” and the like, as used with respect to embodiments of the present disclosure are synonymous.
  • circuitry may refer to, be part of, or include any combination of integrated circuits (for example, a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), discrete circuits, combinational logic circuits, system on a chip (SOC), system in a package (SiP), that provides the described functionality.
  • the circuitry may execute one or more software or firmware modules to provide the described functions.
  • circuitry may include logic, at least partially operable in hardware.
  • V-UE or“vehicle-UE” may refer to, be part of, or include any combination of a UE, which is further described infra with respect to Figure 1.
  • a V-UE or vehicle-UE may refer to, be part of, or include any combination of a vehicular system.
  • Advanced V2X use cases have gone beyond road safety applications.
  • Advanced V2X in NR-enabled communications may adapt to various requirements in accordance with various use cases. These requirements may include, but are not limited to, latency, end-to-end reliability, payload, transmission rate, data rate, and minimum required communication range.
  • a payload may be measured in bytes or a similar unit.
  • a transmission rate may be measured in number of messages per second or a similar unit.
  • a maximum end-to-end latency may be measured in milliseconds (ms) or a similar unit.
  • a reliability may be measured in percentage or a similar unit.
  • a data rate may be measured in megabytes per second (Mbps) or a similar unit.
  • a minimum required communication range may be measured in meters or a similar unit.
  • the latency for a V2X communication may need to be as small as 3 ms due to an emergency trajectory and up to 100 ms for some less critical scenarios.
  • An end-to-end reliability may be required to be within a range of 90-99.999%.
  • An example data rate may be required to be up to 1000 Mbps for extended sensor use case.
  • Some of those requirements may be more stringent than the basic V2X use cases in long term evolution (LTE) V2X communications.
  • LTE QoS framework may not be suitable to satisfy those ranges of requirements.
  • Embodiments described herein may include, for example, apparatuses, methods, and storage media for configuring efficient data transmission via NR V2X sidebnk operations.
  • Embodiments may support various QoS requirements associated with different use cases and enable multiplexing/de-multiplexing data packets of different UEs on to the same medium access control (MAC) protocol data unit (PDU).
  • the implementation may improve UE and/or network efficiency in NR V2X sidelink communications.
  • FIG. 1 schematically illustrates an example wireless network 100 (hereinafter“network 100”) in accordance with various embodiments herein.
  • the network 100 may include a UE 105 in wireless communication with an AN 110.
  • the network 100 may be a NR SA network.
  • the UE 105 may be configured to connect, for example, to be
  • connection 112 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as a 5G NR protocol operating at mmWave and sub-6GHz, a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • the UE 105 is illustrated as a smartphone (for example, a handheld touchscreen mobile computing device connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing devices, such as a Personal Data Assistant (PDA), pager, laptop computer, desktop computer, wireless handset, customer premises equipment (CPE), fixed wireless access (FWA) device, vehicle mounted UE or any computing device including a wireless communications interface.
  • PDA Personal Data Assistant
  • CPE customer premises equipment
  • FWA fixed wireless access
  • vehicle mounted UE vehicle mounted UE or any computing device including a wireless communications interface.
  • the UE 105 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • IoT Internet of Things
  • An IoT UE can utilize technologies such as narrowband IoT (NB-IoT), machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • the M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An NB-IoT/MTC network describes interconnecting NB-IoT/MTC UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the NB-IoT/MTC UEs may execute background applications (for example, keep-alive message, status updates, location related services, etc.).
  • the UE 105 may be a vehicular UE (V-UE) that is part of a vehicle with cellular communication capability or is a vehicle system including a communication sub-system for cellular communications.
  • V-UE vehicular UE
  • a V-UE may include multiple baseband chips for connecting with individual access networks.
  • the V-UE may include a cellular network baseband System-on-Chip (SoC) for attaching to and establishing network connectivity with a cellular network and/or other UEs/V -UEs for sidelink communications.
  • SoC System-on-Chip
  • the AN 110 can enable or terminate the connection 112.
  • the AN 110 can be referred to as a base station (BS), NodeB, evolved-NodeB (eNB), Next-Generation NodeB (gNB or ng- gNB), NG-RAN node, cell, serving cell, neighbor cell, and so forth, and can comprise ground stations (for example, terrestrial access points) or satellite stations providing coverage within a geographic area.
  • BS base station
  • eNB evolved-NodeB
  • gNB or ng- gNB Next-Generation NodeB
  • NG-RAN node cell, serving cell, neighbor cell, and so forth
  • ground stations for example, terrestrial access points
  • satellite stations providing coverage within a geographic area.
  • the AN 110 can be the first point of contact for the UE 105.
  • the AN 110 can fulfill various logical functions including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • a downlink resource grid can be used for downlink transmissions from the AN 110 to the UE 105, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for orthogonal frequency division multiplexing (OFDM) systems, which makes it intuitive for radio resource allocation.
  • OFDM orthogonal frequency division multiplexing
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time- frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UE 105.
  • the physical downlink control channel may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UE 105 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel.
  • HARQ hybrid automatic repeat request
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 105 within a cell) may be performed at the AN 110 based on channel quality information fed back from any of the UE 105.
  • the downlink resource assignment information may be sent on the PDCCH used for (for example, assigned to) the UE 105.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • REGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (ePDCCH) that uses PDSCH resources for control information transmission.
  • the ePDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similar to the above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • ePDCCH enhanced physical downlink control channel
  • ECCEs enhanced control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the UE 105 may include millimeter wave communication circuitry grouped according to functions.
  • the circuitry shown here is for illustrative purposes and the UE 105 may include other circuitry shown in Figure 3.
  • the UE 105 may include protocol processing circuitry 115, which may implement one or more of layer operations related to medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) and non-access stratum (NAS).
  • the protocol processing circuitry 115 may include one or more processing cores (not shown) to execute instructions and one or more memory structures (not shown) to store program and data information.
  • the UE 105 may further include digital baseband circuitry 125, which may implement physical layer (PHY) functions including one or more of HARQ functions, scrambling and/or descrambling, coding and/or decoding, layer mapping and/or de-mapping, modulation symbol mapping, received symbol and/or bit metric determination, multi-antenna port pre-coding and/or decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation and/or detection, preamble sequence generation and/or decoding, synchronization sequence generation and/or detection, control channel signal blind decoding, and other related functions.
  • PHY physical layer
  • the UE 105 may further include transmit circuitry 135, receive circuitry 145, radio frequency (RF) circuitry 155, and RF front end (RFFE) 165, which may include or connect to one or more antenna panels 175.
  • transmit circuitry 135, receive circuitry 145, radio frequency (RF) circuitry 155, and RF front end (RFFE) 165 may include or connect to one or more antenna panels 175.
  • RF circuitry 155 may include multiple parallel RF chains or branches for one or more of transmit or receive functions; each chain or branch may be coupled with one antenna panel 175.
  • the protocol processing circuitry 115 may include one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry 125 (or simply,“baseband circuitry 125”), transmit circuitry 135, receive circuitry 145, radio frequency circuitry 155, RFFE 165, and one or more antenna panels 175.
  • control circuitry not shown to provide control functions for the digital baseband circuitry 125 (or simply,“baseband circuitry 125”), transmit circuitry 135, receive circuitry 145, radio frequency circuitry 155, RFFE 165, and one or more antenna panels 175.
  • a UE reception may be established by and via the one or more antenna panels 175,
  • the one or more antenna panels 175 may receive a transmission from the AN 110 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 175. Further details regarding the UE 105 architecture are illustrated in Figures 2, 3, and 6.
  • the transmission from the AN 110 may be transmit-beamformed by antennas of the AN 110.
  • the baseband circuitry 125 may contain both the transmit circuitry 135 and the receive circuitry 145. In other embodiments, the baseband circuitry 125 may be implemented in separate chips or modules, for example, one chip including the transmit circuitry 135 and another chip including the receive circuitry 145.
  • the AN 110 may include mmWave/sub-mmWave communication circuitry grouped according to functions.
  • the AN 110 may include protocol processing circuitry 120, digital baseband circuitry 130 (or simply,“baseband circuitry 130”), transmit circuitry 140, receive circuitry 150, RF circuitry 160, RFFE 170, and one or more antenna panels 180.
  • a cell transmission may be established by and via the protocol processing circuitry 120, digital baseband circuitry 130, transmit circuitry 140, RF circuitry 160, RFFE 170, and one or more antenna panels 180.
  • the one or more antenna panels 180 may transmit a signal by forming a transmit beam.
  • Figure 3 further illustrates details regarding the RFFE 170 and antenna panel 180.
  • Figure 2 illustrates example components of a device 200 in accordance with some embodiments.
  • Figure 2 illustrates example components of the UE 105 or the AN 110 from a receiving and/or transmitting function point of view, and it may not include all of the components described in Figure 1.
  • the device 200 may include application circuitry 202, baseband circuitry 204, RF circuitry 206, RFFE circuitry 208, and a plurality of antennas 210 together at least as shown.
  • the baseband circuitry 204 may be similar to and substantially interchangeable with the baseband circuitry 125 in some embodiments.
  • the plurality of antennas 210 may constitute one or more antenna panels for beamforming.
  • the components of the illustrated device 200 may be included in a UE or an AN.
  • the device 200 may include fewer elements (for example, a cell may not utilize the application circuitry 202, and instead include a processor/controller to process IP data received from an EPC).
  • the device 200 may include additional elements such as, for example, a memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (for example, said circuitry may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • C-RAN Cloud-RAN
  • the application 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 processor(s) may include any combination of general-purpose processors and dedicated processors (for example, graphics processors, application processors, etc.).
  • the processors may be coupled with or may include
  • memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the device 200.
  • instructions stored in the memory /storage may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the device 200.
  • processors of application circuitry 202 may process IP data packets received from an EPC.
  • 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 be similar to and substantially interchangeable with the baseband circuitry 125 and the baseband circuitry 130 in some embodiments.
  • the baseband circuitry 204 may include one or more baseband processors 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 circuitry 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 third generation (3G) baseband processor 204A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processor(s) 204D for other existing generations, generations in development or to be developed in the future (for example, second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 204 (for example, one or more of baseband processors 204A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 206.
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • baseband processors 204 A-D may be included in modules stored in the memory 204G and executed via a central processing unit (CPU) 204E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • signal modulation/demodulation e.g., a codec
  • encoding/decoding e.g., a codec
  • radio frequency shifting e.g., radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 204 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 204 may include one or more audio digital signal processor(s) (DSP) 204F.
  • the audio DSP(s) 204F may include elements for
  • compression/decompression and echo cancellation may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, in 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 SOC.
  • the baseband circuitry 204 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 204 may support communication with an evolved universal terrestrial radio access network (E-UTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • E-UTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 206 may include one or more switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 206 may include receiver circuitry 206A, which may include circuitry to down-convert RF signals received from the RFFE circuitry 208 and provide baseband signals to the baseband circuitry 204.
  • RF circuitry 206 may also include transmitter circuitry 206B, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the RFFE circuitry 208 for
  • 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 integrated circuit (IC) circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • RFFE circuitry 208 may include a receive signal path, which may include circuitry configured to operate on RF beams received from one or more antennas 210.
  • the RF beams may be transmit beams formed and transmitted by the AN 110 while operating in mmWave or sub- mmWave frequency rang.
  • the RFFE circuitry 208 coupled with the one or more antennas 210 may receive the transmit beams and proceed them to the RF circuitry 206 for further processing.
  • RFFE 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 antennas 210, with or without beamforming.
  • the amplification through transmit or receive signal paths may be done solely in the RF circuitry 206, solely in the RFFE circuitry 208, or in both the RF circuitry 206 and the RFFE circuitry 208.
  • the RFFE circuitry 208 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the RFFE circuitry 208 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RFFE circuitry 208 may include a low noise amplifier (LNA) to amplify received RF beams and provide the amplified received RF signals as an output (for example, to the RF circuitry 206).
  • LNA low noise amplifier
  • the transmit signal path of the RFFE circuitry 208 may include a power amplifier (PA) to amplify input RF signals (for example, provided by RF circuitry 206), and one or more filters to generate RF signals for beamforming and subsequent transmission (for example, by one or more of the one or more antennas 210).
  • PA power amplifier
  • Processors of the application circuitry 202 and processors of the baseband circuitry 204 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 204 may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 202 may utilize data (for example, packet data) received from these layers and further execute Layer 4 functionality (for example, transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/AN, described in further detail below.
  • Figure 3A illustrates an embodiment of a radio frequency front end 300 incorporating an mmWave RFFE 305 and one or more sub-6GHz radio frequency integrated circuits (RFICs)
  • the mmWave RFFE 305 may be similar to and substantially interchangeable with the RFFE 165, RFFE 170, and/or the RFFE circuitry 208 in some embodiments.
  • the mmWave RFFE 305 may be used for the UE 105 while operating in FR2 or mmWave; the RFICs 310 may be used for the UE 105 while operating in FR1, sub-6GHz, or LTE bands.
  • the one or more RFICs 310 may be physically separated from the mmWave RFFE 305.
  • RFICs 310 may include connection to one or more antennas 320.
  • the RFFE 305 may be coupled with multiple antennas 315, which may constitute one or more antenna panels.
  • FIG. 3B illustrates an alternate embodiment of an RFFE 325.
  • both millimeter wave and sub-6GHz radio functions may be implemented in the same physical RFFE 330.
  • the RFFE 330 may incorporate both millimeter wave antennas 335 and sub-6GHz antennas 340.
  • the RFFE 330 may be similar to and substantially interchangeable with the RFFE 165, RFFE 170, and/or the RFFE circuitry 208 in some embodiments.
  • Figures 3A and 3B illustrate embodiments of various RFFE architectures for either the UE 105 or the AN 110.
  • the V2X sidelink communications may be based on broadcast. For example, all packets may be blindly sent by vehicle UEs via sidelink. In some cases, the packets may be retransmitted with a fixed number of times by option.
  • the QoS offered by such a broadcast mechanism may be based on indicating single priority value (e.g., ProSe per-packet priority (PPPP)) associated with each V2X packet.
  • PPPP ProSe per-packet priority
  • AS layer procedures may be MAC layer scheduling and/or multiplexing, and associated resource selection and reservation for transmissions.
  • a QoS management is based on RRC configurations of appropriate MAC layer parameters that are related to specific logical channels in operations over an Uu interface, which is a radio interface between the UE and the radio access network.
  • duplication of a transmission on multiple carriers at the PDCP layer is used to enhance reliability, and one or more QoS metrics may be used to indicate reliability requirements for each packet (e.g., ProSe Per-Packet Reliability (PPPR)).
  • PPPR ProSe Per-Packet Reliability
  • an LTE V2X packet may be associated with one or more QoS parameters, and one or more radio layers may aim to meet the associated QoS requirements on a packet basis.
  • one-to-one and/or one-to-many types of V2X communications via sidelink may be established to enable unicast or group-cast V2X communications.
  • the two (or more) UEs involved in such V2X sidelink communications may establish a connection between them and exchange certain information so that a set of rules applied to the particular V2X communications can be agreed upon and established between the two UEs.
  • One or more of the set of the rules may correspond to a set of QoS requirements that are to be fulfilled for the sidelink V2X communications.
  • NR resource allocation for V2X sidelink transmission may use two distinct modes.
  • One of them is a network schedule mode (e.g., Mode-1), in which the network (e.g., an eNB or a gNB) schedules specific resources.
  • the other mode is an autonomous resources reservation/reselection mode (e.g., Mode-2), in which the UE 105 may select or determine resources based on sensing by the UE 105.
  • Mode-2 it may be challenging to achieve certain QoS requirements unless non-contention resources are allocated, since Mode-2 is inherently based on the notion of collision detection and avoidance on a broadcast channel.
  • SDAP Service Data Adoption Protocol
  • a packet that is generated by the application layer may be assigned with a ProSe Sidelink (PC5) or sidelink QoS identifier or parameter based on certain mapping performed by corresponding V2X functions. The packet may then be passed to the AS layer along with this QoS parameter.
  • PC5 V2X may use a QoS flow-based model or sidelink bearer based model, which may be similar to an NR Uu link. Such operations may aid in seamless switching between the NR Uu and the NR sidelink.
  • both PC5 and sidelink refer to V2X communications between the UEs without network after resources for communications have been determined and established.
  • the terms “PC5” and“sidelink” may be used interchangeably throughout this disclosure.
  • V2X is an example communication over sidelink. It can be any device-to-device communication using cellular sidelink.
  • an SDAP layer may be beneficial to have an SDAP layer to enable mapping an incoming QoS flow into sidelink radio bearer.
  • the SDAP layer may further mark the flow with a QoS flow identification (QFI) for uplink and/or downlink packets.
  • QFI QoS flow identification
  • the QFI may be used only by the two V2X UEs for further mapping with adequate vehicle quality index (VQI) or 5G QoS identifier (5QI).
  • the incoming service request from the V2X layer may have associated 5QI/V QI mapping.
  • a corresponding sidelink bearer may be established between the two V2X UEs involved in the NR V2X sidelink communications.
  • the AS layer may perform mapping the service request into a data radio bearer (DRB) identification (ID). Such mapping may be performed based on the generation of the sidelink bearer.
  • the MAC layer may perform mapping the one or more DRB ID to one or more logic channel (LC) ID.
  • DRB data radio bearer
  • LC logic channel
  • the V2X layer may provide supported or available network resource selection mode information with the service information for the V2X UE(s) to initiate a network based scheduled resource selection (e.g., Mode-1) or an autonomous resource selection (e.g., Mode-2).
  • the autonomous resource selection mode may include one or more sub-modes, such as using scheduling UE, pre-configuration, dynamic resource selection, etc. If both Mode-1 and Mode-2 are available, the UE may determine which mode and/or sub-mode to use for a particular V2X sidelink transmission.
  • the network may provide indications and/or assistance information to the UE in this regard. Such information may be configured to the UE via one or more control elements, such as SidelinkUEInformation, RRCReconfiguration, etc.
  • an end marker may be transmitted if a resource re-selection or re configuration of the DRB occurs corresponding to a given sidelink radio bearer. Additionally or alternatively, if a unicast link is lost or a feedback from a receiver UE is not received by a transmitter UE, the same or a different end marker may be transmitted as well.
  • the transmitter UE may determine whether the QoS requirements are fulfilled based on feedback information from the receiver UE. Such feedback information may be via HARQ and/or RLC.
  • the QoS requirements may be associated with a service, QoS flow, a bearer, LCID, or other suitable basis corresponding to one to more packets.
  • the transmitter UE may evaluate and determine one or more changes in mode operation. The transmitter UE may then initiate such a mode change based on information received from the network if it is under the coverage of the network.
  • associated MAC sub-headers and MAC header fields may include one or more below fields:
  • V The MAC PDU format version number field indicates which version of the sidelink shared channel (SL-SCH) sub-header is used. In this version of the specification three format versions are defined, and this field shall therefore be set to“0001”,“0010”, and“0011”. If the DST field is 24 bits, this field may be set to“0011”.
  • the V field size may be 4 bits;
  • the Source Layer-2 ID field carries the identity of the source. It is set to the ProSe UE ID.
  • the SRC field size may be 24 bits;
  • the Destination Layer-2 ID For sidebnk communication, the Destination Layer-2 ID may be set to the ProSe Layer-2 Group ID or ProSe UE ID.
  • the Destination Layer-2 ID may be set to the identifier provided by upper layers. If the V field is set to“0001”, this identifier may be a group-cast identifier. If the V field is set to“0010”, this identifier may be a unicast identifier;
  • LCID The Logical Channel ID field uniquely identifies the logical channel instance within the scope of one Source Layer-2 ID and Destination Layer-2 ID pair of the corresponding MAC service data unit (SDU) or padding. There may be one LCID field for each MAC SDU or padding included in the MAC PDU. In addition to that, one or two additional LCID fields may be included in the MAC PDU, when single-byte or two-byte padding is desired but cannot be achieved by padding at the end of the MAC PDU.
  • the values of LCID from “01011” to“10100” may identify the logical channels used to send duplicated RLC SDUs from logical channels of which the values of LCID range from“00001” to“01010” respectively in sequential order.
  • the LCID field size may be 5 bits;
  • L The Length field indicates the length of the corresponding MAC SDU in bytes. There may be one L field per MAC PDU sub-header except for the last sub-header. The size of the L field may be indicated by the F field;
  • the Format field indicates the size of the Length field as indicated in table 6.2.4-2. There may be one F field per MAC PDU sub-header except for the last sub-header. The size of the F field may be 1 bit. If the size of the MAC SDU is less than 128 bytes, the value of the F field may be set to 0; otherwise it may be set to 1;
  • the Extension field is a flag indicating if more fields are present in the MAC header or not.
  • the E field may be set to“1” to indicate another set of at least R/R/E/LCID fields.
  • the E field may be set to“0” to indicate that either a MAC SDU or padding starts at the next byte;
  • R Reserved bit, set to“0”.
  • FIGS 4A-D illustrate some example MAC sub-headers, in accordance with various embodiments.
  • Those MAC sub-headers may be used for communications related to LTE as well.
  • an MAC header may include one or more MAC sub-headers, source and destination IDs, and MAC SDU.
  • LTE there may be only one or more SDUs per PDU that are designated with one destination ID.
  • a Destination Layer-2 ID may be set to an identifier provided by upper layers. For example, if the“V” field in Figure 4D is set to be“0001,” this identifier may be a group-cast identifier or indicate a group-cast.
  • corresponding source (SRC)/destination (DEST) layer-2 ID fields/length/number of bits may remain the same so that no physical layer changes may be required, since these fields are to be passed down to one or more lower layers.
  • LCID may be extended to support activation and/or deactivation with respect to multiplexing of more than one SDU or an indication associated with multiplexing of more than one SDU.
  • LCID may represent corresponding logical channel ID and have logical channel data that correspond to specific QoS requirements or 5QI characteristics. In some embodiments, there may be 8, 16, or more LCIDs that are supported by the UE.
  • a first group of LCIDs may be categorized to be used in Mode-1 operation, whereas a second group of LCIDs may be categorized to be used in Mode-2.
  • a third group of LCIDs may be categorized to be used in both Mode-1 and Mode-2. Other categorization or classification may be used to assign the LCIDs with their available operations. For example, a specific LCID or a set of LCIDs may be specified to enable the following functions:
  • Activation/Deactivation or start/stop indication for one or more multiplexed or to-be multiplexed SDUs for transmission.
  • corresponding de-multiplexing filter or multiplexing group ID may be transmitted within a data portion of the corresponding MAC SDU.
  • Such an indication may be transmitted or sent to individual receiver UEs that the transmitter UE plans to establish unicast communication(s) with. This indication may also be realized or exchanged via PC5 RRC message(s).
  • the above described activation/deactivation may be shared using the PC5-RRC message with corresponding receiver UE(s), which may cause certain latency and/or signaling overhead.
  • using the PC5-RRC message may provide advantages based on an acknowledgement- response procedure.
  • a specific set of LCIDs may be allocated to support the PC5-RRC messages among transmitter and receiver UEs. Table 1 illustrates an example of such a set of LCIDs.
  • FIG. 5A illustrates example MAC control elements (CEs) in formatting control message(s), in accordance with various embodiments.
  • Certain LCID values e.g., Table 1 may be applied to the MAC CEs to generate or form corresponding control message(s) in PC5-RRC signaling.
  • corresponding activation/deactivation commands may be transmitted along with the LCID for the source/destination (SRC/DEST) pair for which either Mode-1 or Mode-2 may be used.
  • SRC/DEST source/destination
  • Each line e.g., the Line 505) in Figure 5A indicates an octet, which includes eight bits. Certain alignment and/or paddling may be implemented as necessary but not shown in Figure 5A.
  • the source and destination layer-2 ID may be 24 bits as per LTE V2X sidelink communications.
  • NR-based V2X sidelink communication may use the same or different number of bits.
  • a LCIDi 510 may represent LCID2, LCID3, etc.
  • The“L” field may indicate a length of the number of LCIDs. Note that Figure 5A is only exemplary and other like formats of control signaling may be used.
  • an MAC PDU may include header and MAC SDU in NR V2X communications
  • multiplexing MAC SDUs may be supported within one MAC PDU.
  • the transmitter UE may exchange corresponding information via the PC5-RRC message(s) with the receiver UE while establishing the connection for transmission.
  • Such information may include a multiplexing ID indicating that more than one SDU belonging to different receiver UEs are to be included within one MAC PDU. This ID may thus identify the receiver UEs that has SDUs within the MAC PDU.
  • Such information may also include corresponding LCIDs that are associated with the UEs.
  • the transmitter UE may use one or more specific LCIDs to represent an instance of one MAC SDU with the specific MAC PDU. Those LCIDs may be exchanged via PC5-RRC message(s).
  • the MAC PDU may include the following indications, as shown in Figure 5B.
  • “M” field 515:“M” may be used in one of the“R” fields to indicate that the destination ID represents an ID for a group of unicast UEs and a specific filter (e.g., LCID) is to be applied by the destination to obtain the specific MAC SDU(s) within the MAC PDU or the message.
  • a “V” field 520 may be used to indicate a group-cast packet and the same LCID may be used for all the members of the group-cast.
  • “M” field 515 may indicate that a group ID is to be multiplexed with a group of unicast UEs.
  • The“DEST (Mux group ID)” field 525 may include 16 or 24 bits to represent a group of unicast IDs. In some embodiments, corresponding mapping of the destination ID to the multiplexing group ID may be performed based on specific UE implementation.
  • Figure 5B is only exemplary and other like formats of control signaling may be used. Also note that an NR MAC PDU format may be adjusted or modified to represent the V2X sidelink shared channel MAC.
  • Figure 6A illustrates an operation flow/algorithmic structure 600 to facilitate a process of initiating an NR V2X sidelink communication from a transmitter UE perspective, in accordance with various embodiments.
  • the operation flow/algorithmic structure 600 may be performed by the UE 105 or circuitry thereof including, for example, digital baseband circuitry 125.
  • the operation flow/algorithmic structure 600 may include, at 610, determining one or more QoS indicators with respect to a flow of packets that is generated by an application layer and is to be transmitted by the UE in an NR sidelink V2X communication. Such a determination may be based on specific QoS requirements assigned by the application layer.
  • the UE may further receive the flow of packets from the application layer or some other corresponding layer(s).
  • the one or more QoS indicators may be referred to as one or more QoS parameters.
  • the QoS indicators or parameters may be associated with VQI and/or 5QI.
  • the operation flow/algorithmic structure 600 may further include, at 620, establishing a sidelink radio bearer based on the determined one or more QoS indicators.
  • the sidelink radio bearer may be established by the SDAP layer if it is available.
  • the UE may generate a QFI for the flow of packets. This may include both uplink and downlink packets.
  • the UE may map, at an application service layer, a service associated with the flow to a data radio bearer ID associated with the sidelink radio bearer.
  • the UE may not have the SDAP layer.
  • corresponding incoming service request from a V2X layer may have associated VQI/5QI mapping.
  • the AS layer may perform mapping the service request to DRB ID(s). Further mapping DRB ID(s) to LCID(s) may be performed by a corresponding MAC layer.
  • the operation flow/algorithmic structure 600 may further include, at 630, transmitting the flow of packets to a receiver UE via one or more resources corresponding to the established sidelink radio bearer in the NR sidelink V2X communication.
  • the transmitter UE may initiate a network scheduled resource selection or an autonomous resource selection and determine one or more resources for transmitting the one or more multiplexed packets.
  • the UE may generate an end marker corresponding to the sidelink radio bearer, if a unicast of the UE is lost or absent a feedback message transmitted by the receiver UE. Further, the UE may decode, upon reception of the feedback message from the receiver UE, the feedback message with respect to transmission or reception of the one or more multiplexed packets and determine whether the determined one or more QoS indicators are satisfied based on the decoded feedback message.
  • the feedback message may be a HARQ/RLC related message or like message.
  • Figure 6B illustrates an operation flow/algorithmic structure 605 to facilitate the process of initiating an NR V2X sidelink communication from a receiver UE perspective, in accordance with various embodiments.
  • the operation flow/algorithmic structure 605 may be performed by the UE 105 or circuitry thereof including, for example, digital baseband circuitry 125.
  • the operation flow/algorithmic structure 605 may include, at 615, decoding, upon reception of a flow of packets from a transmitter UE in the NR sidelink V2X communication, the flow of packets that includes a sidelink radio bearer with one or more QoS indicators.
  • the reception may be via one or more resources configured based on either a Mode-1 or Mode-2 scheduling.
  • the operation flow/algorithmic structure 605 may further include, at 625, generating, upon decoding the flow of packets, a feedback message.
  • the operation flow/algorithmic structure 605 may further include, at 635, transmitting the feedback message to the transmitter UE via one or more resources for the NR sidelink V2X communication that are configured by the transmitter UE or the network.
  • the receiver UE may further decode, upon reception, a message that indicates an activation or a deactivation of a set of LCIDs for network scheduled resource mode or autonomous resource mode in the sidelink V2X communication.
  • the receiver UE may further decode another message that indicates an activation or a deactivation of multiplexing more than one SDU into one PDU for data transmission to one or more receiver UEs in the NR sidelink V2X communication.
  • Figure 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 204 of Figure 2 may comprise processors 204A-204E and a memory 204G utilized by said processors.
  • the processors 204A- 204E of the UE 105 may perform some or all of the operation flow/algorithmic structure 600 or 605, in accordance with various embodiments with respect to Figures 5A and 5B.
  • Each of the processors 204A-204E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 204G.
  • the baseband circuitry 204 may further include one or more interfaces to
  • a memory interface 712 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 204
  • an application circuitry interface 714 for example, an interface to send/receive data to/from the application circuitry 202 of Figure 2
  • an RF circuitry interface 716 for example, an interface to send/receive data to/from RF circuitry 206 of Figure 2
  • a wireless hardware connectivity interface 718 for example, an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (for example, Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 720 for example, an interface to send/receive power or control signals.
  • Figure 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (for example, a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory /storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840.
  • node virtualization for example, network function virtualization (NFV)
  • a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800.
  • NFV network function virtualization
  • the processors 810 may include, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereol
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory /storage devices 820 may include main memory, disk storage, or any suitable combination thereof.
  • the memory /storage devices 820 may include, but are not limited to, any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 830 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network 808.
  • the communication resources 830 may include wired communication components (for example, for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (for example, Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein, e.g., the operation flows 600 and 605.
  • the instructions 850 may cause the UE to perform some or all of the operation flow/algorithmic structure 600.
  • the instructions 850 may cause the AN 110 to perform some or all of the operation flow/algorithmic structure 605.
  • the instructions 850 may reside, completely or partially, within at least one of the processors 810 (for example, within the processor’s cache memory), the memory /storage devices 820, or any suitable combination thereof.
  • any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806.
  • the memory of processors 810, the memory /storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.
  • Example 1 may include a method comprising: determining one or more quality of service (QoS) indicators with respect to a flow of packets that is generated by an application layer and is to be transmitted by the UE in a new radio (NR) sidelink vehicle-to-everything (V2X) communication; establishing a sidelink radio bearer based on the determined one or more QoS indicators; and transmitting the flow of packets to a receiver UE via one or more resources corresponding to the established sidelink radio bearer in the NR sidelink V2X communication.
  • QoS quality of service
  • NR new radio
  • V2X vehicle-to-everything
  • Example 2 may include the method of example 1 and/or some other examples herein, further comprising generating a QoS flow identification (ID) for the flow of packets.
  • ID QoS flow identification
  • Example 3 may include the method of example 2 and/or some other examples herein, wherein to establish the sidelink radio bearer, the UE is to establish the sidelink radio bearer according to a service data adaption protocol (SDAP).
  • Example 4 may include the method of example 1 and/or some other examples herein, further comprising mapping, at an application service layer, a service associated with the flow to a data radio bearer identification (ID) associated with the sidelink radio bearer.
  • ID data radio bearer identification
  • Example 5 may include the method of example 1 and/or some other examples herein, wherein the one or more QoS indicators are associated with vehicle quality index (VQI) or 5G QoS identifier (5QI).
  • VQI vehicle quality index
  • 5QI 5G QoS identifier
  • Example 6 may include the method of example 1 and/or some other examples herein, wherein to transmit the flow of packets to the receiver UE is to initiate a network scheduled resource selection or an autonomous resource selection; and determine one or more resources for transmitting the flow of packets.
  • Example 7 may include the method of example 1 and/or some other examples herein, further comprising generating an end marker corresponding to the sidelink radio bearer, if at least one of the one or more resources is to be re-determined or a data radio bearer is to be reconfigured.
  • Example 8 may include the method of examples 1-7 and/or some other examples herein, further comprising generating an end marker corresponding to the sidelink radio bearer, if a unicast link of the UE is lost or a feedback message transmitted by the receiver UE is absent.
  • Example 9 may include the method of example 8 and/or some other examples herein, further comprising decoding, upon reception of the feedback message from the receiver UE, the feedback message with respect to transmission or reception of the one or more multiplexed packets; and determining whether the determined one or more QoS indicators are satisfied based on the decoded feedback message.
  • Example 10 may include the method of examples 1-9 and/or some other examples herein, wherein the method is performed by a transmitter UE and/or a transmitter vehicle UE and/or a portion thereof in the NR V2X sidelink communication.
  • Example 11 may include a method, comprising generating a first message that indicates an activation or a deactivation of a set of logic channel identifications (LCIDs) for network scheduled resource mode or autonomous resource mode in a new radio (NR) sidelink vehicle-to- every thing (V2X) communication; generating a second message that indicates an activation or a deactivation of multiplexing more than one service data unit (SDU) into one protocol data unit (PDU) for data transmission to one or more receiver UEs in the NR sidelink V2X
  • LCIDs logic channel identifications
  • NR new radio
  • V2X vehicle-to- every thing
  • Example 12 may include the method of example 11 and/or some other examples herein, further comprising generating an SDU that includes a multiplexing group identification (ID) with respect to multiplexing the more than one service data unit (SDU) into the protocol data unit (PDU); multiplexing the SDU with one or more additional SDUs into the one PDU; and transmitting a third message that includes the PDU to the one or more receiver UEs.
  • ID multiplexing group identification
  • SDU service data unit
  • PDU protocol data unit
  • Example 12 may include the method of example 11 and/or some other examples herein, further comprising generating an SDU that includes a multiplexing group identification (ID) with respect to multiplexing the more than one service data unit (SDU) into the protocol data unit (PDU); multiplexing the SDU with one or more additional SDUs into the one PDU; and transmitting a third message that includes the PDU to the one or more receiver UEs.
  • ID multiplexing group identification
  • Example 13 may include the method of example 12 and/or some other examples herein, wherein the SDU includes one or more de-multiplexing filters.
  • Example 14 may include the method of example 12 and/or some other examples herein, further comprising generating a fourth message that indicates one or more LCIDs of the set of LCIDs correspond to one of the one or more receiver UEs; and transmitting the fourth message to the one of the one or more receiver UEs.
  • Example 15 may include the method of example 11 and/or some other examples herein, wherein the set of LCIDs is a first set of LCIDs, and the first message is further to indicate a second set of LCIDs for both the network scheduled resource mode and autonomous resource mode in the NR sidelink V2X communication.
  • Example 16 may include the method of examples 11-15 and/or some other examples herein, wherein any or all of the first message, the second message and the third message are NR sidelink radio resource control (RRC) messages.
  • RRC radio resource control
  • Example 17 may include the method of examples 11-16 and/or some other examples herein, wherein the method is performed by a transmitter UE and/or a transmitter vehicle UE and/or a portion thereof in the NR V2X sidelink communication.
  • Example 18 may include a method, comprising decoding, upon reception of a flow of packets from a transmitter UE in a new radio (NR) sidelink vehicle-to-every thing (V2X) communication, the flow of packets that includes a sidelink radio bearer with one or more quality of service (QoS) indicators; generating, upon decoding the flow of packets, a feedback message; and transmitting the feedback message to the transmitter UE via one or more resources for the NR sidelink V2X communication that are configured by the transmitter UE.
  • NR new radio
  • V2X vehicle-to-every thing
  • Example 19 may include the method of example 18 and/or some other examples herein, further comprising decoding, upon reception, a first message that indicates an activation or a deactivation of a set of logic channel identifications (LCIDs) for network scheduled resource mode or autonomous resource mode in the NR sidelink V2X communication.
  • LCIDs logic channel identifications
  • Example 20 may include the method of examples 18 or 19, and/or some other examples herein, further comprising decoding, upon reception, a second message that indicates an activation or a deactivation of multiplexing more than one service data unit (SDU) into one protocol data unit (PDU) for data transmission to one or more receiver UEs in the NR sidelink V2X communication.
  • Example 21 may include the method of examples 18-20 and/or some other examples herein, wherein the method is performed by a receiver UE and/or a receiver vehicle UE and/or a portion thereof in the NR V2X sidelink communication.
  • Example 22 may include an apparatus comprising means to perform one or more elements of the method described in or related to any of examples 1-21, or any other method or process described herein.
  • Example 23 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method described in or related to any of examples 1-21, or any other method or process described herein.
  • Example 24 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of the method described in or related to any of examples 1-21, or any other method or process described herein.
  • Example 25 may include a method, technique, or process as described in or related to any of examples 1-21, or portions or parts thereof.
  • Example 26 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-21, or portions thereof.
  • These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means that implement the function/act specified in the flowchart or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart or block diagram block or blocks.

Landscapes

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

Abstract

Selon des modes de réalisation, la présente invention porte sur des procédés, des appareils, des supports d'informations et des systèmes pour configurer une transmission de données efficace par l'intermédiaire d'opérations en liaison latérale de véhicule à tout (V2X) en nouvelle radio (NR). Divers modes de réalisation décrivent comment utiliser diverses exigences de qualité de service (QoS) associées à différents scénarios d'utilisation et permettre le multiplexage/démultiplexage de paquets de données de différents équipements utilisateur (UE) sur la même unité de données de protocole (PDU) de commande d'accès au support (MAC). La mise en œuvre peut améliorer l'efficacité de l'UE et/ou du réseau dans des communications en liaison latérale V2X NR. D'autres modes de réalisation peuvent être décrits et revendiqués.
PCT/US2019/066651 2018-12-17 2019-12-16 Techniques d'utilisation de ressources et de prise en charge de qualité de service dans des communications en liaison latérale de véhicule à tout en nouvelle radio WO2020131753A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980043197.8A CN112385262A (zh) 2018-12-17 2019-12-16 新空口车辆到万物侧链路通信中的资源利用和服务质量支持中的技术
EP19898248.0A EP3900430A4 (fr) 2018-12-17 2019-12-16 Techniques d'utilisation de ressources et de prise en charge de qualité de service dans des communications en liaison latérale de véhicule à tout en nouvelle radio

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862780877P 2018-12-17 2018-12-17
US62/780,877 2018-12-17

Publications (1)

Publication Number Publication Date
WO2020131753A1 true WO2020131753A1 (fr) 2020-06-25

Family

ID=71101858

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/066651 WO2020131753A1 (fr) 2018-12-17 2019-12-16 Techniques d'utilisation de ressources et de prise en charge de qualité de service dans des communications en liaison latérale de véhicule à tout en nouvelle radio

Country Status (3)

Country Link
EP (1) EP3900430A4 (fr)
CN (1) CN112385262A (fr)
WO (1) WO2020131753A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220094420A1 (en) * 2017-06-02 2022-03-24 Apple Inc. Beamformed Measurement for New Radio (NR)
CN114531655A (zh) * 2020-11-23 2022-05-24 维沃移动通信有限公司 资源指示方法、接入网侧设备及核心网功能
EP4087293A1 (fr) * 2021-05-06 2022-11-09 Robert Bosch GmbH Procédés et dispositifs de communication radio

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115499799A (zh) * 2021-06-17 2022-12-20 大唐移动通信设备有限公司 一种计费方法、用户设备及网络侧设备
WO2023216062A1 (fr) * 2022-05-09 2023-11-16 Apple Inc. Sous-regroupement et configuration d'espaces d'id de canal logique pour ce mac/sdu

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018016157A1 (fr) * 2016-07-18 2018-01-25 Panasonic Intellectual Property Corporation Of America Support amélioré de qualité de service pour transmissions v2x
WO2018063081A1 (fr) 2016-09-30 2018-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Relais entre un équipement utilisateur et un réseau

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017052690A1 (fr) * 2015-09-24 2017-03-30 Intel Corporation Contrôle de congestion pour services de « véhicule vers tout »
EP3223575B1 (fr) * 2015-11-19 2019-06-12 ASUSTek Computer Inc. Procédés et appareil pour commuter une interface de communication dans un système de communications sans fil
EP3764581A1 (fr) * 2016-03-30 2021-01-13 IDAC Holdings, Inc. Accès radio flexible nr assisté par évolution à long terme (lte)
US10630410B2 (en) * 2016-05-13 2020-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Network architecture, methods, and devices for a wireless communications network
US10362511B2 (en) * 2016-05-17 2019-07-23 Lg Electronics Inc. Method and apparatus for determining PDU session identity in wireless communication system
WO2018093220A1 (fr) * 2016-11-18 2018-05-24 Lg Electronics Inc. Procédé et appareil d'émission d'informations utilisant une communication v2x dans un système de communication sans fil
US20180324631A1 (en) * 2017-05-05 2018-11-08 Mediatek Inc. Using sdap headers for handling of as/nas reflective qos and to ensure in-sequence packet delivery during remapping in 5g communication systems

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018016157A1 (fr) * 2016-07-18 2018-01-25 Panasonic Intellectual Property Corporation Of America Support amélioré de qualité de service pour transmissions v2x
WO2018063081A1 (fr) 2016-09-30 2018-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Relais entre un équipement utilisateur et un réseau

Non-Patent Citations (10)

* Cited by examiner, † Cited by third party
Title
"Consideration on QoS management for NR V2X", 3GPP TDOC. R2-1816988
"Potential AS layer impacts on SL connection setup and configuration in unicast", 3GPP TDOC. R2-1816517
"Radio bearer configuration and management for NR sidelink", 3GPP TDOC. R2-1816522
3GPP TECHNICAL SPECIFICATION (TS) 36.321, 28 September 2018 (2018-09-28)
3GPP TSG-RAN WG2 #104, November 2018 (2018-11-01)
HUAWEI, HISILICON: "Potential AS layer impacts on SL connection setup and configuration in unicast", 3GPP DRAFT; R2-1816517 POTENTIAL AS LAYER IMPACTS ON SL CONNECTION SETUP AND CONFIGURATION IN UNICAST, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, USA; 20181112 - 20181116, R2-1816517 Potential AS layer impacts on SL connec, 2 November 2018 (2018-11-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051480471 *
HUAWEI, HISILICON: "Radio bearer configuration and management for NR sidelink", 3GPP DRAFT; R2-1816522 RADIO BEARER CONFIGURATION AND MANAGEMENT FOR NR SIDELINK, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, USA; 20181112 - 20181116, R2-1816522 Radio bearer configuration and manageme, 2 November 2018 (2018-11-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051480475 *
QUALCOMM INCORPORATED: "Discussion on Groupcast for NR V2X", 3GPP DRAFT; R2-1817780-DISCUSSION ON NR V2X GROUPCAST, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, United States; 20181112 - 20181116, R2-1817780-Discussion on NR V2X groupcast, 2 November 2018 (2018-11-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051481670 *
See also references of EP3900430A4
VIVO: "Different destination service multiplexing in MAC", 3GPP DRAFT; R2-1817116_DIFFERENT DESTINATION SERVICE MULTIPLEXING IN MAC, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, USA; 20181112 - 20181116, R2-1817116_Different destination service multiplex, 2 November 2018 (2018-11-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051481036 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220094420A1 (en) * 2017-06-02 2022-03-24 Apple Inc. Beamformed Measurement for New Radio (NR)
US11646781B2 (en) * 2017-06-02 2023-05-09 Apple Inc. Beamformed measurement for new radio (NR)
CN114531655A (zh) * 2020-11-23 2022-05-24 维沃移动通信有限公司 资源指示方法、接入网侧设备及核心网功能
CN114531655B (zh) * 2020-11-23 2024-03-22 维沃移动通信有限公司 资源指示方法、接入网侧设备及核心网功能
EP4087293A1 (fr) * 2021-05-06 2022-11-09 Robert Bosch GmbH Procédés et dispositifs de communication radio
US11854392B2 (en) 2021-05-06 2023-12-26 Robert Bosch Gmbh Methods and devices for radio communication

Also Published As

Publication number Publication date
EP3900430A4 (fr) 2022-08-03
CN112385262A (zh) 2021-02-19
EP3900430A1 (fr) 2021-10-27

Similar Documents

Publication Publication Date Title
US11968730B2 (en) Techniques for NR cell/beam identification
US12028731B2 (en) Techniques in system frame number (SFN) and frame timing difference measurements in new radio (NR)
US11363476B2 (en) Techniques in measurement gap configurations in new radio (NR)
US20220046454A1 (en) Techniques in multiple measurement gaps in new radio (nr)
EP3834549B1 (fr) Techniques de configuration d'intervalle de mesure dans de nouvelles communications associées à une radio (nr)
US11546861B2 (en) Techniques in inter-band and intra-band dynamic power sharing in dual connectivity communications
US11108476B2 (en) Techniques in beam measurement
WO2020131753A1 (fr) Techniques d'utilisation de ressources et de prise en charge de qualité de service dans des communications en liaison latérale de véhicule à tout en nouvelle radio
US11646781B2 (en) Beamformed measurement for new radio (NR)
EP3854132A1 (fr) Techniques dans des configurations d'intervalle de mesure (mg) à partie de bande passante (bwp)
US20210385676A1 (en) Dynamic radio frequency switching in new radio for radio resource management in radio resource control connected state
JP7223124B2 (ja) セカンダリセルグループ障害測定報告における技術
EP3854131A1 (fr) Techniques dans des configurations d'intervalle de mesure avec partie de bande passante dans des mesures de multiples signaux de synchronisation
CN111165008B (zh) 用于新无线电系统的新的基于质量的测量定义
KR20240044204A (ko) 무선 통신 시스템에서 그룹 캐스트를 이용한 위치 측정 방법 및 장치

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019898248

Country of ref document: EP

Effective date: 20210719