Apparatus and computer-readable medium for efficient new radio sidelink vehicle-to-everything communications

By adopting data packet multiplexing/demultiplexing technology in NR V2X side link communication, supporting multiple QoS requirements, the problem of inefficient resource use in the prior art is solved, and more efficient communication efficiency and quality is achieved.

CN112385262BActive Publication Date: 2024-12-06INTEL CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980043197.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-12-17
Filing Date
2019-12-16
Publication Date
2024-12-06
Estimated Expiration
2039-12-16

AI Technical Summary

Technical Problem

The existing 5G new air interface (NR) V2X side link communication cannot efficiently use network resources according to quality of service (QoS) requirements in different use case scenarios, resulting in inefficiency.

Method used

By supporting QoS requirements associated with different use cases in NR V2X side link communication, data packet multiplexing/demultiplexing technology is adopted to enable multiple UEs on the same Media Access Control (MAC) protocol data unit (PDU) The data transmission can improve network and UE efficiency.

Benefits of technology

The efficiency of NR V2X side link communication network and user equipment can better meet the QoS requirements of different use cases, and improve the quality and efficiency of communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112385262B_ABST
    Figure CN112385262B_ABST
Patent Text Reader

Abstract

Embodiments of the present disclosure describe methods, apparatus, storage media, and systems for configuring efficient data transmission via New Radio (NR) vehicle-to-everything (V2X) sidelink operations. Various embodiments describe how to utilize various QoS requirements associated with different use cases and enable multiplexing / demultiplexing of data packets of different user devices onto the same medium access control (MAC) protocol data unit (PDU). The implementation can improve UE and / or network efficiency in NR V2X sidelink communications. Other embodiments may be described and claimed.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 780,877, filed on December 17, 2018, entitled “Methods for Efficient Resource Utilization and QoS Support for NR V2X Sidelink UE,” the entire disclosure of which is hereby incorporated by reference in its entirety. Technical Field

[0003] Embodiments of the present invention generally relate to the technical field of wireless communications. Background Art

[0004] The background description provided here is to give a general background of the present disclosure. The work of the inventors currently nominated (to the extent that it is described in this background section) and some aspects that may not be suitable for description as prior art at the time of application for other reasons are neither explicitly nor implicitly admitted as prior art of the present disclosure. Unless otherwise indicated herein, the schemes described in this section are not prior art of the claims in the present disclosure and are not admitted to be prior art by being included in this section.

[0005] Various use cases for advanced vehicle-to-everything (V2X) communications involving fifth generation (5G) New Radio (NR) communications require unicast, groupcast, broadcast, and other appropriate communication modes. Existing sidelink V2X (V2X) communications may not use network resources efficiently according to the different quality of service (QoS) requirements associated with various use case scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The embodiments will be easily understood by the following detailed description in conjunction with the accompanying drawings. To aid this description, similar reference numerals designate similar structural elements. The embodiments are illustrated in the accompanying drawings by way of example and not by way of limitation.

[0007] Figure 1 An example of a network including a user equipment (UE) and an access node (AN) in a wireless network is schematically illustrated according to various embodiments.

[0008] Figure 2 Example components of a device are illustrated in accordance with various embodiments.

[0009] Figure 3A An example radio frequency front end (RFFE) is illustrated according to some embodiments, comprising a millimeter wave (mmWave) RFFE and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). Figure 3BA replacement RFFE is illustrated according to various embodiments.

[0010] Figures 4A-4D Some example medium access control (MAC) subheaders are illustrated in accordance with various embodiments.

[0011] Figure 5A An example MAC Control Element (CE) is illustrated in accordance with various embodiments when formatting a control message. Figure 5B An example MAC protocol data unit (PDU) format is illustrated.

[0012] Fig. 6A An operational flow / algorithm structure that facilitates a process of initiating NR V2X sidelink communication from a transmitting UE perspective is illustrated according to various embodiments. Figure 6B An operational flow / algorithm structure of a process that facilitates initiating NR V2X sidelink communication from a transmitting UE perspective from a receiving UE perspective is illustrated according to various embodiments.

[0013] Figure 7 Example interfaces for baseband circuitry are illustrated in accordance with some embodiments.

[0014] Figure 8 Hardware resources are illustrated according to some embodiments. DETAILED DESCRIPTION

[0015] In the following detailed description, reference is made to the accompanying drawings, which form a part of this document, wherein like reference numerals designate like parts throughout, and in which embodiments that may be implemented are shown by way of illustration. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description should not be understood in a limiting sense.

[0016] Various operations can be described in sequence as multiple discrete actions or operations in a manner that is most helpful for understanding the claimed subject matter. However, the order of description should not be interpreted as meaning that these operations must be dependent on the order. In particular, these operations may not be performed in the order presented. The operations described may be performed in an order different from the described embodiments. Various additional operations may be performed and / or the operations described may be omitted in additional embodiments.

[0017] For purposes of this disclosure, the phrases "A or B" and "A and / or B" mean (A), (B), or (A and B). For purposes of this disclosure, 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).

[0018] The description may use the phrases "in one embodiment" or "in an embodiment", each of which may refer to one or more of the same or different embodiments. In addition, the terms "including", "comprising", "having", etc. used in connection with the embodiments of the present disclosure are synonymous.

[0019] As used herein, the term "circuitry" may refer to, may be a part of, or may include any combination of integrated circuits (e.g., field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.), discrete circuits, combinational logic circuits, systems on a chip (SOCs), systems in packages (SiPs) that provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware modules to provide the described functionality. In some embodiments, the circuitry may include logic that is at least partially operable in hardware.

[0020] As used herein, the term "V-UE" or "vehicle UE" may refer to, may be a part of, or may include any combination of UEs, UEs hereinafter referred to as Figure 1 Further description. V-UE or vehicle UE may refer to, may be part of, or may include any combination of vehicle systems. Throughout this disclosure, "UE", "V-UE" and "vehicle UE" are used interchangeably unless otherwise stated.

[0021] Advanced V2X use cases go beyond road safety applications. Advanced V2X in NR-enabled communications can be adapted to various requirements based on 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. In general, payload may be measured in bytes or similar units. Transmission rate may be measured in messages per second or similar units. Maximum end-to-end latency may be measured in milliseconds (ms) or similar units. Reliability may be measured in percentages or similar units. Data rate may be measured in megabytes per second (Mbps) or similar units. Minimum required communication range may be measured in meters or similar units. For example, the latency of V2X communications may need to be as small as 3ms due to emergency trajectories, while it may be as high as 100ms for some less critical scenarios. End-to-end reliability may need to be in the range of 90-99.999%. Example data rates may need to be up to 1000Mbps for extended sensor use cases. Some of these requirements may be more stringent than basic V2X use cases in long-term evolution (LTE) V2X communications. The existing LTE QoS framework may not be suitable to meet these range of requirements.

[0022] Embodiments described herein may include, for example, apparatus, methods, and storage media for configuring efficient data transmission via NR V2X sidelink operation. Embodiments may support various QoS requirements associated with different use cases and enable multiplexing / demultiplexing of data packets of different UEs onto the same medium access control (MAC) protocol data unit (PDU). The implementation may improve UE and / or network efficiency in NR V2X sidelink communications.

[0023] Figure 1 An example wireless network 100 (hereinafter referred to as "network 100") is schematically illustrated according to various embodiments herein. Network 100 may include UE 105 in wireless communication with AN 110. In some embodiments, network 100 may be an NR SA network. UE 105 may be configured, for example, to be connected to be communicatively coupled with AN 110. In this example, connection 112 is shown as an air interface to enable communicatively coupling, and may conform to a cellular communication protocol, 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.

[0024] UE 105 is shown as a smart phone (e.g., a handheld touch screen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop, a desktop computer, a wireless handset, a customer premises equipment (CPE), a fixed wireless access (FWA) device, a vehicle-mounted UE, or any computing device that includes a wireless communication interface. In some embodiments, UE 105 may include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as narrowband IoT (NB-IoT), machine-to-machine (M2M), or machine-type communications (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communications, a sensor network, or an IoT network. The M2M or MTC data exchange may be a machine-initiated data exchange. NB-IoT / MTC network description uses short-term connections to interconnect NB-IoT / MTC UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). NB-IoT / MTC UEs can execute background applications (e.g., keep-alive messages, status updates, location-related services, etc.).

[0025] UE 105 may be a vehicle VE (V-UE), which is part of a vehicle with cellular communication capabilities or a vehicle system that includes a communication subsystem for cellular communication. In some implementations, the V-UE may include multiple baseband chips for connecting to individual access networks. For example, 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 to enable sidelink communications.

[0026] AN 110 may enable or terminate connection 112. AN 110 may be referred to as a base station (BS), a Node B, an evolved Node B (eNB), a next generation Node B (gNB or ng-gNB), an NG-RAN node, a cell, a serving cell, a neighbor cell, etc., and may include a ground station (e.g., a terrestrial access point) or a satellite station that provides coverage in a certain geographic area.

[0027] AN 110 may be the first point of contact for UE 105. In some embodiments, AN 110 may perform 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.

[0028] In some embodiments, a downlink resource grid may be used for downlink transmissions from AN 110 to UE 105, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. This time-frequency plane representation is a common practice in orthogonal frequency division multiplexing (OFDM) systems, which makes it intuitive for radio resource allocation. Each column and first row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes several resource blocks, which describe the mapping of a specific physical channel to a resource element. Each resource block includes a set of resource elements; in the frequency domain, this can represent the minimum number of resources that can currently be allocated. There are several different physical downlink channels that are transported using such resource blocks.

[0029] The physical downlink shared channel (PDSCH) can carry user data and higher layer signaling to the UE 105. The physical downlink control channel (PDCCH) can carry information about the transport format and resource allocation related to the PDSCH channel, etc. It can also inform the UE 105 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to UEs 105 within a cell) can be performed at the AN 110 based on channel quality information fed back from any one of the UEs 105. The downlink resource assignment information can be sent on the PDCCH for (e.g., assigned to) the UE 105.

[0030] PDCCH can use control channel elements (CCE) to carry control information. Before being mapped to resource elements, PDCCH complex symbols can first be organized into quaternions, which can then be permuted using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to nine sets of four physical resource elements referred to as resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size and channel conditions of the downlink control information (DCI), one or more CCEs can be used to transmit PDCCH.

[0031] Some embodiments may use resource allocation concepts for control channel information, which are extensions of the above concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (ePDCCH) that uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) may be used to transmit the ePDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements referred to as enhanced resource element groups (EREGs). ECCEs may have other numbers of EREGs in some cases.

[0032] like Figure 1As shown in , UE 105 may include millimeter wave communication circuits grouped according to functions. The circuits shown here are for illustration, and UE 105 may include other circuits shown in Figure 3. UE 105 may include protocol processing circuit 115, which may implement one or more of the layer operations related to medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and non-access layer (NAS). The protocol processing circuit 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.

[0033] The UE 105 may also include a digital baseband circuit 125, which may implement physical layer (PHY) functions, including one or more of the following: HARQ functions, scrambling and / or descrambling, encoding and / or decoding, layer mapping and / or demapping, modulation symbol mapping, received symbol and / or bit metric determination, multi-antenna port precoding and / or decoding (which may include one or more of space-time, space-frequency or space 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.

[0034] UE 105 may also include transmit circuitry 135 , receive circuitry 145 , radio frequency (RF) circuitry 155 , and an RF front end (RFFE) 165 , which may include or be connected to one or more antenna panels 175 .

[0035] In some embodiments, 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 to an antenna panel 175 .

[0036] In some embodiments, the protocol processing circuit 115 may include one or more instances of a control circuit (not shown) to provide control functions for the digital baseband circuit 125 (or simply referred to as "baseband circuit 125"), the transmitting circuit 135, the receiving circuit 145, the radio frequency circuit 155, the RFFE 165 and one or more antenna panels 175.

[0037] UE reception may be established by and via one or more antenna panels 175, RFFE 165, RF circuitry 155, receive circuitry 145, digital baseband circuitry 125, and protocol processing circuitry 115. One or more antenna panels 175 may receive transmissions from AN 110 via receive beamformed signals received by multiple antennas / antenna elements of one or more antenna panels 175. More details on the UE 105 architecture are provided in Figure 2 , 3 and 6. Transmissions from AN 110 may be transmit beamformed by the antenna of AN 110. In some embodiments, baseband circuitry 125 may include both transmit circuitry 135 and receive circuitry 145. In other embodiments, baseband circuitry 125 may be implemented in separate chips or modules, such as one chip including transmit circuitry 135 and another chip including receive circuitry 145.

[0038] Similar to UE 105, AN 110 may include mmWave / sub-mmWave communication circuits grouped according to functions. AN 110 may include protocol processing circuits 120, digital baseband circuits 130 (or simply referred to as "baseband circuits 130"), transmission circuits 140, reception circuits 150, RF circuits 160, RFFE 170, and one or more antenna panels 180.

[0039] Cell transmission can be established by and via the protocol processing circuit 120, the digital baseband circuit 130, the transmission circuit 140, the RF circuit 160, the RFFE 170 and one or more antenna panels 180. The one or more antenna panels 180 can transmit signals by forming a transmit beam. FIG. 3 further illustrates details about the RFFE 170 and the antenna panels 180.

[0040] Figure 2 Example components of device 200 are illustrated according to some embodiments. Figure 1 In contrast, Figure 2 Example components of UE 105 or AN 110 are illustrated from a receiving and / or transmitting functional perspective and may not include Figure 1 All components described in . In some embodiments, the device 200 may include an application circuit 202, a baseband circuit 204, an RF circuit 206, an RFFE circuit 208, and multiple antennas 210 together at least as shown. The baseband circuit 204 may be similar to the baseband circuit 125 in some embodiments and substantially interchangeable with the baseband circuit 125. Multiple 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. In some embodiments, the device 200 may include fewer elements (e.g., a cell may not utilize the application circuit 202, but include a processor / controller to process IP data received from the EPC). In some embodiments, the device 200 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., for a cloud RAN (C-RAN) implementation, the circuit may be separately included in more than one device).

[0041] The application circuit 202 may include one or more application processors. For example, the application circuit 202 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The (one or more) processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to a memory / storage device or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 200. In some embodiments, the processor of the application circuit 202 may process IP data packets received from the EPC.

[0042] The baseband circuit 204 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 204 may be similar to the baseband circuit 125 and the baseband circuit 130 in some embodiments and may be substantially interchangeable with the baseband circuit 125 and the baseband circuit 130. The baseband circuit 204 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of the RF circuit 206 and generate baseband signals for the transmit signal path of the RF circuit 206. The baseband circuit 204 may interface with the application circuit 202 to generate and process baseband signals and control the operation of the RF circuit 206. For example, in some embodiments, the baseband circuit 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 (one or more) baseband processors 204D for other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 204 (e.g., one or more of the baseband processors 204A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 206. In other embodiments, some or all of the functions of the baseband processors 204A-D may be included in a module stored in the memory 204G and executed via the central processing unit (CPU) 204E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency offset, and the like. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 204 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples, and may include other suitable functions in other embodiments.

[0043] In some embodiments, the baseband circuit 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP 204F may include elements for compression / decompression and echo cancellation, and may include other appropriate processing elements in other embodiments. The components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or arranged on the same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuit 204 and the application circuit 202 may be implemented together, for example, on a SOC.

[0044] In some embodiments, the baseband circuit 204 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 204 may support communications with an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0045] The RF circuit 206 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuit 206 may include one or more switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 206 may include a receiver circuit 206A, which may include circuitry to down-convert RF signals received from the RFFE circuit 208 and provide a baseband signal to the baseband circuit 204. The RF circuit 206 may also include a transmitter circuit 206B, which may include circuitry to up-convert baseband signals provided by the baseband circuit 204 and provide an RF output signal to the RFFE circuit 208 for transmission.

[0046] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 206 may include analog to digital converter (ADC) and digital to analog converter (DAC) circuits and baseband circuit 204 may include a digital baseband interface to communicate with RF circuit 206.

[0047] In some dual-mode embodiments, separate radio integrated circuit (IC) circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this regard.

[0048] The RFFE circuitry 208 may include a receive signal path that 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 when operating in the mmWave or sub-mmWave frequency range. The RFFE circuitry 208 coupled to the one or more antennas 210 may receive the transmit beams and forward them to the RF circuitry 206 for further processing. The RFFE circuitry 208 may also include a transmit signal path that may include circuitry configured to amplify signals provided by the RF circuitry 206 for transmission for transmission by one or more of the antennas 210 with or without beamforming. In various embodiments, amplification by the transmit or receive path may be done only in the RF circuitry 206, only in the RFFE circuitry 208, or in both the RF circuitry 206 and the RFFE circuitry 208.

[0049] In some embodiments, the RFFE circuit 208 may include a TX / RX switch to switch between transmit mode and receive mode operation. The RFFE circuit 208 may include a receive signal path and a transmit signal path. The receive signal path of the RFFE circuit 208 may include a low noise amplifier (LNA) to amplify the received RF beam and provide an amplified received RF signal as an output (e.g., provided to the RF circuit 206). The transmit signal path of the RFFE circuit 208 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 206) and one or more filters to generate an RF signal for beamforming and subsequent transmission (e.g., transmitted by one or more of the one or more antennas 210).

[0050] The processor of the application circuit 202 and the processor of the baseband circuit 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 204 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 202 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). For the purposes of this document, layer 3 may include a radio resource control (RRC) layer, which is described in more detail below. For the purposes of this document, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which is described in more detail below. For the purposes of this document, layer 1 may include a physical (PHY) layer of the UE / AN, which is described in more detail below.

[0051] Figure 3AAn embodiment of a radio frequency front end 300 including a mmWave RFFE 305 and one or more sub-6 GHz radio frequency integrated circuits (RFICs) 310 is illustrated. The mmWave RFFE 305 may be similar to and substantially interchangeable with the RFFE 165, RFFE 170, and / or RFFE circuitry 208 in some embodiments. The mmWave RFFE 305 may be used for the UE 105 when operating in FR2 or mmWave; the RFIC 310 may be used for the UE 105 when operating in FR1, sub-6 GHz, or LTE bands. In this embodiment, the one or more RFICs 310 may be physically separated from the mmWave RFFE 305. The RFIC 310 may include connections to one or more antennas 320. The RFFE 305 may be coupled to a plurality of antennas 315, which may constitute one or more antenna panels.

[0052] Figure 3B An alternative embodiment of RFFE 325 is illustrated. In this aspect, both mmWave and sub-6 GHz radio functionality may be implemented in the same physical RFFE 330. RFFE 330 may include both mmWave antennas 335 and sub-6 GHz antennas 340. RFFE 330 may be similar to and substantially interchangeable with RFFE 165, RFFE 170, and / or RFFE circuitry 208 in some embodiments.

[0053] Figure 3A and 3B Embodiments of various RFFE architectures are illustrated for UE 105 or AN 110.

[0054] In an LTE network, V2X sidelink communications can be broadcast based. For example, all packets can be sent blindly by the vehicle UE via the sidelink. In some cases, as an option, the packet can be retransmitted a fixed number of times. The QoS provided by this broadcast mechanism can be based on a single priority value (e.g., ProSe per-packet priority (PPPP)) indicating that it is associated with each V2X packet. This serves as the primary QoS metric for any access stratum (AS) layer process. Such AS layer processes can be MAC layer scheduling and / or multiplexing, as well as associated resource selection and transmission reservation. In contrast, QoS management is based on RRC configuration of appropriate MAC layer parameters associated with a specific logical channel in operation over the Uu interface, which is the radio interface between the UE and the wireless access network.

[0055] Conventionally, duplication of transmissions 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)). However, due to the inherent nature of broadcasts in conventional V2X transmissions, there may not be any feedback mechanism in this process. Thus, LTE V2X packets may be associated with one or more QoS parameters, and one or more radio layers may be designed to meet the associated QoS requirements on a packet basis.

[0056] In NR, one-to-one and / or one-to-many type V2X communications via a side link may be established to enable unicast or multicast V2X communications. Accordingly, two (or more) UEs involved in such V2X side link communications may establish a connection between them and exchange certain information so that a set of rules applicable to a specific V2X communication may be agreed upon and established between the two UEs. One or more of the set of rules may correspond to a set of QoS requirements fulfilled for the side link V2X communication. There may be one or more schemes for addressing QoS requirements or implementing a QoS framework. For example, an extension and / or unified QoS metric based on per-packet QoS may be used, regardless of whether the application layer or upper layer is different between two different RATs and associated interfaces.

[0057] In some embodiments, two different modes may be used for NR resource allocation for V2X sidelink transmissions. One of them is a network scheduled mode (e.g., Mode 1), in which the network (e.g., eNB or gNB) schedules specific resources. The other mode is an autonomous resource reservation / reselection mode (e.g., Mode 2), in which the UE 105 may select or determine resources based on sensing performed by the UE 105. In Mode 2, unless non-contention resources are allocated, it may be challenging to achieve certain QoS requirements because Mode 2 is inherently based on the concept of collision detection and avoidance on a broadcast channel.

[0058] Service Data Adaptation Protocol (SDAP) and bearer configuration

[0059] Traditionally in LTE V2X sidelink communications, packets generated by the application layer are assigned a ProSe sidelink (PC5) or sidelink QoS identifier or parameter based on some mapping performed by the corresponding V2X function. The packet can then be passed to the AS layer together with this QoS parameter. In contrast, NR V2X can use a QoS flow-based model or a sidelink bearer-based model, which can be similar to the NR Uu link. This operation can help seamless switching between NR Uu and NR sidelink. Note that both PC5 and sidelink refer to V2X communications without a network between UEs after resources for communication have been determined and established. The terms "PC5" and "sidelink" can be used interchangeably throughout this disclosure. In addition, V2X is an example communication through a sidelink. It can be any device-to-device communication using a cellular sidelink.

[0060] In an embodiment, it may be beneficial to have the SDAP layer enable mapping of incoming QoS flows to sidelink radio bearers. The SDAP layer may also mark flows with a QoS Flow Identifier (QFI) for uplink and / or downlink packets. In some embodiments, the QFI may be used by only two V2X UEs for further mapping with an appropriate Vehicle Quality Index (VQI) or 5G QoS Identifier (5QI).

[0061] In an embodiment, if SDAP is not supported by the sidelink communication, the incoming service request from the V2X layer may have an associated 5QI / VQI mapping. The corresponding sidelink bearer may be established between the two V2X UEs involved in the NR V2X sidelink communication. The AS layer may perform mapping of the service request to a data radio bearer (DRB) identifier (ID). This mapping may be performed based on the generation of the sidelink bearer. In addition, the MAC layer may perform mapping of one or more DRB IDs to one or more logical channel (LC) IDs.

[0062] In addition, the V2X layer may provide supported or available network resource selection mode information with service information for (one or more) V2X UEs to initiate network-based scheduled resource selection (e.g., Mode 1) or autonomous resource selection (e.g., Mode 2). The autonomous resource selection mode may include one or more sub-modes, such as using a scheduled UE, pre-configuration, dynamic resource selection, and the like. 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. Additionally or alternatively, the network may provide indications and / or auxiliary 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, and the like.

[0063] In an embodiment, an end marker may be sent if resource reselection or reconfiguration of a DRB occurs corresponding to a given sidelink radio bearer. Additionally or alternatively, the same or different end marker may also be sent if the unicast link is lost or feedback from the receiving UE is not received by the sending UE.

[0064] In an embodiment, the sender UE may determine whether the QoS requirement is fulfilled based on feedback information from the receiver UE. Such feedback information may be via HARQ and / or RLC. The QoS requirement may be associated with a service, a QoS flow, a bearer, an LCID, or other appropriate basis corresponding to one or more packets. After such determination, the sender UE may evaluate and determine one or more changes in the mode operation. The sender UE may then initiate such a mode change based on information received from the network if it is under the coverage of the network.

[0065] Extensions to the MAC header for sidelink unicast / multicast support

[0066] Traditionally in V2X sidelink communications, the associated MAC subheader and MAC header fields may include one or more of the following fields:

[0067] -V: MAC PDU format version number field, which indicates which version of the Sidelink Shared Channel (SL-SCH) subheader is used. Three format versions are defined in this version of the specification, and this field should therefore be set to "0001", "0010" and "0011". If the DST field is 24 bits, this field can be set to "0011". The V field size can be 4 bits;

[0068] -SRC: The Source Layer 2 ID field carries the identity of the source. It is set to the ProSe UE ID. The SRC field size can be 24 bits;

[0069] -DST: The DST field can be 16 bits or 24 bits. If it is 16 bits, it carries the 16 most significant bits of the destination layer 2 ID. If it is 24 bits, it can be set to the destination layer 2 ID. For sidelink communication, the destination layer 2 ID can be set to the ProSe layer 2 group ID or the ProSe UE ID. For V2X sidelink communication, the destination layer 2 ID can be set to an identifier provided by the upper layer. If the V field is set to "0001", this identifier can be a multicast identifier. If the V field is set to "0010", this identifier can be a unicast identifier.

[0070] -LCID: The Logical Channel ID field uniquely identifies a logical channel instance within the range of a source Layer 2 ID and destination Layer 2 ID pair of a 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, when single-byte or two-byte padding is desired but cannot be achieved by padding at the end of the MAC PDU, one or two additional LCID fields may be included in the MAC PDU. LCID values ​​ranging from "01011" to "10100" may identify a logical channel for sending duplicate RLC SDUs from logical channels having LCID values ​​ranging from "00001" to "01010" in sequential order, respectively. The LCID field size may be 5 bits;

[0071] -L: The length field indicates the length of the corresponding MAC SDU in bytes. There can be one L field for each MAC PDU subheader, except for the last subheader. The size of the L field can be indicated by the F field;

[0072] -F: The format field indicates the size of the length field, as indicated in Table 6.2.4-2. There may be one F field for each MAC PDU subheader, except for the last subheader. 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;

[0073] -E: The extension field is a flag indicating whether there are more fields in the MAC header. The E field can be set to "1" to indicate another set of at least R / R / E / LCID fields. The E field can be set to "0" to indicate that the MAC SDU or padding starts at the next byte;

[0074] -R: Reserved bit, set to "0".

[0075] Figures 4A-4D Some example MAC subheaders are illustrated according to various embodiments. These MAC subheaders may also be used for communications related to LTE. For example, a MAC header may include one or more MAC subheaders, source and destination IDs, and a MAC SDU. In LTE, there may be only one or more SDUs specified by a destination ID for each PDU. In V2X sidelink communications, the destination Layer 2 ID may be set to an identifier provided by an upper layer. For example, if Figure 4D If the "V" field in is set to "0001", this identifier may be a multicast identifier or indicate multicast. If there is a more efficient unicast communication via the side link in the NR V2X communication, some additional functions may be required. Note Figures 4A-4Dand the corresponding description is about 3GPP Technical Specification (TS) 36.321v14.8.0 (September 28, 2018).

[0076] In NR V2X communication, if the UE performs unicast link establishment with more than one receiving UE or has groupcast communication with more than one receiving UE, it may be feasible to multiplex different SDUs within one MAC PDU to efficiently use the allocated sidelink grants. In some embodiments, the corresponding source (SRC) / destination (DEST) layer 2 ID field / length / number of bits may remain the same, so that no physical layer changes may be required because these fields will be passed down to one or more lower layers.

[0077] In an embodiment, the LCID may be extended to support activation and / or deactivation of multiplexing of more than one SDU or indications associated with multiplexing of more than one SDU. The LCID may represent a corresponding logical channel ID and have logical channel data corresponding to a specific QoS requirement or 5QI characteristic. In some embodiments, 8, 16 or more LCIDs may be supported by the UE.

[0078] In some embodiments, a first group of LCIDs may be classified as being used in Mode 1 operation, while a second group of LCIDs may be classified as being used in Mode 2 operation. Additionally or alternatively, a third group of LCIDs may be classified as being used in both Mode 1 and Mode 2. Other classifications and gradings may be used to assign available operations to LCIDs. For example, a particular LCID or set of LCIDs may be specified to enable the following functions:

[0079] Activate / deactivate a specific operation mode (e.g., Mode 1 or Mode 2) towards the destination V2X UE or recipient UE for fast enablement. Additionally or alternatively, such information may be exchanged via PC5 RRC messages.

[0080] Activation / deactivation or start / stop indication for one or more multiplexed or to-be-multiplexed SDUs for transmission. In addition, the corresponding demultiplexing filter or multiplexing group ID may be transmitted within the data portion of the corresponding MAC SDU. Such indication may be transmitted or sent to the individual receiving UEs with which the transmitting UE intends to establish unicast communication. This indication may also be implemented or exchanged via PC5 RRC messages.

[0081] The activation / deactivation may be shared with the corresponding receiving UE using PC5-RRC messages, which may cause a certain delay and / or signaling overhead. However, using PC5-RRC messages may provide advantages based on the confirmation-response process.

[0082] In an embodiment, a specific set of LCIDs may be allocated to support PC5-RRC messages between the sender and receiver UEs. Table 1 illustrates an example of such a set of LCIDs.

[0083] Table 1

[0084]

[0085]

[0086] Figure 5A An example MAC control element (CE) is illustrated in accordance with various embodiments when formatting a control message. Certain LCID values ​​(e.g., Table 1) may be applied to a MAC CE to generate or form a corresponding control message in PC5-RRC signaling. In this scheme with a MAC CE format, for a source / destination (SRC / DEST) pair for which Mode 1 or Mode 2 is to be used, a corresponding activation / deactivation command may be transmitted along with the LCID. Figure 5A Each row in (e.g., row 505) indicates a byte, which includes eight bits. Some alignment and / or padding may be implemented if necessary, but this is not Figure 5A Not shown. In summary, the source and destination Layer 2 IDs may be 24 bits per LTE V2X sidelink communications. NR based V2X sidelink communications may use the same or a different number of bits. LCIDi 510 may represent LCID2, LCID3, and so on. The “L” field may indicate the length of the number of LCIDs. NOTE Figure 5A This is exemplary only, and other similar formats of control signaling may be used.

[0087] In an embodiment, since the MAC PDU may include a header and a MAC SDU in NR V2X communication, multiplexing of MAC SDUs may be supported within one MAC PDU. In order to enable multiplexing of multiple MAC SDUs within one MAC PDU so that the allocated resources can be efficiently used in a better manner, the transmitting UE may exchange corresponding information with the receiving UE via a PC5-RRC message while establishing a connection for transmission. Such information may include a multiplexing ID indicating that more than one SDU belonging to different receiving UEs is to be included in one MAC PDU. This ID can thereby identify the receiving UE with the SDU within the MAC PDU. Such information may also include a corresponding LCID associated with the UE. The transmitting UE may use one or more specific LCIDs to represent an instance of a MAC SDU with a specific MAC PDU. These LCIDs may be exchanged via PC5-RRC messages.

[0088] In addition, the MAC PDU may include the following indications, such as Figure 5B as shown in .

[0089] "M" field 515: "M" may be used in one of the "R" fields to indicate that the destination ID represents the ID of a group of unicast UEs and that 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 message. Additionally or alternatively, the "V" field 520 may be used to indicate a multicast packet and the same LCID may be used for all members of the multicast. In contrast, the "M" field 515 may indicate that the group ID is to be multiplexed with a group of unicast UEs.

[0090] • "DEST (Multiplexing Group ID)" field 525: The "DEST (Multiplexing Group ID)" field 525 may include 16 or 24 bits to represent a set of unicast IDs. In some embodiments, the corresponding mapping of destination IDs to multiplexing group IDs may be performed based on the specific UE implementation.

[0091] Notice Figure 5B This is exemplary only, and other similar formats of control signaling may be used. Note also that the NR MAC PDU format may be adapted or modified to represent the V2X sidelink shared channel MAC.

[0092] Fig. 6A An operational flow / algorithm structure 600 of facilitating a process of initiating NR V2X sidelink communication from the perspective of a transmitting UE is illustrated according to various embodiments. The operational flow / algorithm structure 600 may be performed by the UE 105 or its circuits (including, for example, the digital baseband circuit 125).

[0093] The operational flow / algorithm structure 600 may include, at 610, determining one or more QoS indicators for a flow of packets generated by an application layer and to be sent by a UE in an NR sidelink V2X communication. This determination may be based on a specific QoS requirement assigned by the application layer. The UE may also receive a 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 indicator or parameter may be associated with a VQI and / or a 5QI.

[0094] The operation flow / algorithm structure 600 may also 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. In addition, the UE may generate a QFI for a flow of packets. This may include both uplink and downlink packets.

[0095] In an embodiment, the UE may map the service associated with the flow to a data radio bearer ID associated with the sidelink radio bearer at the application service layer.

[0096] In some embodiments, the UE may not have an SDAP layer. Thus, the corresponding incoming service request from the V2X layer may have an associated VQI / 5QI mapping. The AS layer may perform the mapping of the service request to the DRB ID. Further mapping of the DRB ID to the LCID may be performed by the corresponding MAC layer.

[0097] The operation flow / algorithm structure 600 may also include, at 630, sending the stream of packets to the receiving UE via one or more resources corresponding to the established sidelink radio bearer in the NR sidelink V2X communication. In order to send the stream of packets to the receiving UE, the sending UE may initiate network scheduled resource selection or autonomous resource selection and determine one or more resources to send one or more multiplexed packets.

[0098] In an embodiment, if the UE's unicast is lost or there is no feedback message sent by the receiving UE, the UE may generate an end marker corresponding to the sidelink radio bearer. In addition, the UE may decode the feedback message for the transmission or reception of one or more multiplexed packets after receiving the feedback message from the receiving UE, 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 a similar message.

[0099] Figure 6B An operational flow / algorithm structure 605 for facilitating the process of initiating NR V2X sidelink communication from the perspective of a receiving UE is illustrated according to various embodiments. The operational flow / algorithm structure 605 may be performed by the UE 105 or its circuits (including, for example, the digital baseband circuit 125).

[0100] The operational flow / algorithm structure 605 may include, upon receiving a stream of packets from a transmitting UE in NR sidelink V2X communication, decoding a stream of packets including a sidelink radio bearer with one or more QoS indicators at 615. The reception may be via one or more resources configured based on mode 1 or mode 2 scheduling.

[0101] The operational flow / algorithm structure 605 may also include, at 625, generating a feedback message after decoding the stream of packets.

[0102] The operation flow / algorithm structure 605 may also include, at 635, sending a feedback message to the sending UE via one or more resources configured by the sending UE or the network for NR sidelink V2X communication.

[0103] In some embodiments, the receiving UE may also decode a message upon reception indicating activation or deactivation of a set of LCIDs regarding a network scheduled resource mode or an autonomous resource mode in the sidelink V2X communication.

[0104] In some embodiments, the transmitting UE may also decode another message indicating activation or deactivation of multiplexing more than one SDU into one PDU for data transmission to one or more receiving UEs in NR sidelink V2X communication.

[0105] Figure 7 An example interface of a baseband circuit is illustrated according to some embodiments. As described above, Figure 2 The baseband circuit 204 of the UE 105 may include processors 204A-204E and a memory 204G utilized by the processors. The processors 204A-204E of the UE 105 may be based on the Figure 5A and 5B Various embodiments of the present invention perform some or all of the operation flow / algorithm structure 600 or 605. Each of the processors 204A-204E may include a memory interface 704A-704E, respectively, to send / receive data to / from the memory 204G.

[0106] The baseband circuit 204 may also include one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 712 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204), an application circuit interface 714 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204), and an application circuit interface 715 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204). Figure 2 202), RF circuit interface 716 (e.g., to / from Figure 2 RF circuit 206 to send / receive data), wireless hardware connectivity interface 718 (e.g., to / from near field communication (NFC) components, Components (e.g., low energy ), components and other communication components to send / receive data) and a power management interface 720 (for example, an interface for sending / receiving power or control signals).

[0107] Figure 8 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein according to some example embodiments. Specifically, Figure 8A diagrammatic representation of hardware resources 800 is shown, 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. For embodiments utilizing node virtualization (e.g., network function virtualization (NFV)), a hypervisor 802 may be executed to provide an execution environment for one or more network slices / sub-slices utilizing the hardware resources 800.

[0108] Processor 810 (e.g., 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) (e.g., a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination of these) may include, for example, processor 812 and processor 814.

[0109] The memory / storage device 820 may include a main memory, a disk storage device, or any suitable combination of these. The memory / storage device 820 may include, but is 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 devices, and the like.

[0110] The communication resources 830 may include an interconnect or network interface component or other appropriate device to communicate with one or more peripheral devices 804 or one or more databases 806 via the network 808. For example, the communication resources 830 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Components (e.g., low energy ), components and other communication components.

[0111] The instructions 850 may include software, programs, applications, applet programs, apps, or other executable codes for causing at least any one of the processors 810 to perform any one or more methods discussed herein (e.g., the operation flows 600 and 605). For example, in an embodiment where the hardware resource 800 is implemented in the UE 105, the instructions 850 may cause the UE to perform some or all of the operation flow / algorithm structure 600. The instructions 850 may cause the AN 110 to perform some or all of the operation flow / algorithm structure 605. The instructions 850 may exist in whole or in part in at least one of the processors 810 (e.g., in a cache memory of the processor), in the memory / storage device 820, or in any suitable combination of these. In addition, any portion of the instructions 850 may be transmitted to the hardware resource 800 from any combination of the peripheral device 804 or the database 806. Therefore, the memory of the processor 810, the memory / storage device 820, the peripheral device 804, and the database 806 are examples of computer-readable and machine-readable media.

[0112] Some non-limiting examples of various embodiments are provided below.

[0113] Example 1 may include a method comprising: determining one or more quality of service (QoS) indicators for a stream of packets generated by an application layer and to be sent by a 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 sending the stream of packets to a receiving UE via one or more resources corresponding to the established sidelink radio bearer in the NR sidelink V2X communication.

[0114] Example 2 may include a method as described in Example 1 and / or some other examples herein, further comprising: generating a QoS flow identification (ID) for the packetized flow.

[0115] Example 3 may include a method as described in Example 2 and / or some other examples herein, wherein, to establish the sidelink radio bearer, the UE will establish the sidelink radio bearer according to a service data adaptation protocol (SDAP).

[0116] Example 4 may include a method as described in Example 1 and / or some other examples herein, further comprising: mapping a service associated with the flow to a data radio bearer identifier (ID) associated with the sidelink radio bearer at an application service layer.

[0117] Example 5 may include a method as described in Example 1 and / or some other examples herein, wherein the one or more QoS indicators are associated with a vehicle quality index (VQI) or a 5G QoS identifier (5QI).

[0118] Example 6 may include a method as described in Example 1 and / or some other examples herein, wherein sending the stream of packets to the receiving UE will initiate network scheduled resource selection or autonomous resource selection; and determining one or more resources for sending the stream of packets.

[0119] Example 7 may include a method as described in Example 1 and / or some other examples herein, further comprising: if at least one of the one or more resources is to be re-determined, or the data radio bearer is to be reconfigured, generating an end marker corresponding to the sidelink radio bearer.

[0120] Example 8 may include a method as described in Examples 1-7 and / or some other examples herein, further comprising: if the unicast link of the UE is lost, or there is no feedback message sent by the receiving UE, generating an end marker corresponding to the side link radio bearer.

[0121] Example 9 may include a method as described in Example 8 and / or some other examples herein, further comprising: after receiving the feedback message from the receiving UE, decoding the feedback message for the sending or receiving of one or more multiplexed packets; and determining whether the determined one or more QoS indicators are met based on the decoded feedback message.

[0122] Example 10 may include a method as described in Examples 1-9 and / or some other examples herein, wherein the method is performed by a sending UE and / or a sending vehicle UE and / or a portion thereof in NR V2X side link communication.

[0123] Example 11 may include a method, comprising generating a first message indicating the activation or deactivation of a set of logical channel identifiers (LCIDs) for a network scheduled resource mode or an autonomous resource mode in a new radio (NR) sidelink vehicle-to-everything (V2X) communication; generating a second message indicating the activation or deactivation of multiplexing more than one service data unit (SDU) into a protocol data unit (PDU) for data transmission to one or more receiving UEs in the NR sidelink V2X communication; and after generation, sending the first message and the second message to the one or more receiving UEs.

[0124] Example 12 may include a method as described in Example 11 and / or some other examples herein, further comprising: generating an SDU comprising a multiplexing group identifier (ID) for multiplexing the more than one service data units (SDUs) into the protocol data unit (PDU); multiplexing the SDU with one or more additional SDUs into the one PDU; and sending a third message including the PDU to the one or more receiving UEs.

[0125] Example 13 may include a method as described in Example 12 and / or some other examples herein, wherein the SDU includes one or more demultiplexing filters.

[0126] Example 14 may include a method as described in Example 12 and / or some other examples herein, further comprising: generating a fourth message indicating that one or more LCIDs in the set of LCIDs correspond to one of the one or more receiving UEs; and sending the fourth message to one of the one or more receiving UEs.

[0127] Example 15 may include a method as described in Example 11 and / or some other examples herein, wherein the set of LCIDs is a first set of LCIDs and the first message also indicates a second set of LCIDs for both a network scheduled resource mode and an autonomous resource mode in the NR sidelink V2X communication.

[0128] Example 16 may include a method as described in 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.

[0129] Example 17 may include a method as described in Examples 11-16 and / or some other examples herein, wherein the method is performed by a sending UE and / or a sending vehicle UE and / or a part thereof in the NR V2X side link communication.

[0130] Example 18 may include a method comprising: after receiving a stream of packets from a sending UE in a New Radio (NR) sidelink vehicle-to-everything (V2X) communication, decoding the stream of packets including a sidelink radio bearer having one or more quality of service (QoS) indicators; generating a feedback message after decoding the stream of packets; and sending the feedback message to the sending UE via one or more resources configured by the sending UE for the NR sidelink V2X communication.

[0131] Example 19 may include a method as described in Example 18 and / or some other examples herein, further comprising: decoding a first message after reception, wherein the first message indicates activation or deactivation of a set of logical channel identifiers (LCIDs) for a network scheduled resource mode or an autonomous resource mode in the NR sidelink V2X communication.

[0132] Example 20 may include a method as described in Example 18 or 19 and / or some other examples herein, further comprising: decoding a second message after reception, the second message indicating activation or deactivation of multiplexing more than one service data unit (SDU) into one protocol data unit (PDU) for data transmission to one or more receiving UEs in the NR sidelink V2X communication.

[0133] Example 21 may include a method as described in Examples 18-20 and / or some other examples herein, wherein the method is performed by a receiving UE and / or a receiving vehicle UE and / or a portion thereof in the NR V2X side link communication.

[0134] Example 22 may include an apparatus comprising modules for performing one or more elements of a method described in or related to any of Examples 1-21, or any other method or process described herein.

[0135] Example 23 may include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 1-21 or any other method or process described herein.

[0136] Example 24 may include a device comprising logic, modules, and / or circuits for performing one or more elements of a method described in or related to any of Examples 1-21, or any other method or process described herein.

[0137] Example 25 may include a method, technique, or process as described in or related to any of Examples 1-21, or some portion or fragment thereof.

[0138] Example 26 may include a device comprising: one or more processors and one or more computer-readable media comprising instructions, which, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or some portion thereof, as described in or related to any of Examples 1-21.

[0139] The present disclosure is described with reference to the flowchart or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It will be understood that each square block of the flowchart or block diagram and the combination of square blocks in the flowchart or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that these instructions, when executed by the processor of the computer or other programmable data processing device, create a module for implementing the function / action specified in one or more square blocks of the flowchart or block diagram.

[0140] These computer program instructions may also be stored in a computer-readable medium, which may direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable medium produce a product including an instruction device that implements the functions / actions specified in one or more boxes of a flowchart or block diagram.

[0141] Computer program instructions may also be loaded onto a computer or other programmable data processing apparatus so that a series of operating steps are executed on the computer or other programmable apparatus to produce a process implemented by a computer, whereby the instructions executed on the computer or other programmable apparatus provide a process for implementing the functions / actions specified in one or more blocks of the flowchart or block diagram.

[0142] The descriptions of the illustrated implementations herein, including those described in the Abstract, are not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Although specific implementations and examples are described herein for illustration, as will be appreciated by those skilled in the relevant art, various alternative or equivalent embodiments or implementations intended to achieve the same purpose may be made from the above detailed description without departing from the scope of the disclosure.

Claims

1. One or more computer-readable media, comprising instructions for efficient new radio NR sidelink vehicle-to-everything V2X communication, which instructions, when executed by one or more processors of a user equipment UE, cause the UE to: determining, for a flow of packets generated by an application layer and to be sent by the UE in NR V2X communication, one or more quality of service (QoS) indicators; Based on the determined one or more QoS indicators, establish a sidelink radio bearer, wherein, to establish the sidelink radio bearer, the UE will establish the sidelink radio bearer according to a service data adaptation protocol SDAP; and In the NR sidelink V2X communication, sending the stream of packets to a recipient UE via one or more resources corresponding to the established sidelink radio bearer, Wherein, when the instruction is executed, the UE further: At the SDAP layer, a QoS flow identification ID is generated for the packet flow.

2. One or more computer-readable media as claimed in claim 1, wherein: When executed, the instructions further cause the UE to: At the application service layer, a service associated with the packet flow is mapped to a data radio bearer identification ID associated with the sidelink radio bearer.

3. One or more computer-readable media as claimed in claim 1, wherein: The one or more QoS indicators are associated with a vehicle quality index VQI or a 5G QoS identifier 5QI.

4. One or more computer-readable media as claimed in claim 1, wherein: To send the stream of packets to the recipient UE, the instructions, when executed, cause the UE to: Initiate network scheduling resource selection or autonomous resource selection; and One or more resources are determined for transmitting the flow of packets.

5. One or more computer-readable media as claimed in claim 4, wherein: The instructions When executed, the UE is also caused to: If at least one of the one or more resources is to be re-determined, or the data radio bearer is to be reconfigured, an end marker corresponding to the sidelink radio bearer is generated.

6. One or more computer-readable media as described in any one of claims 1 to 5, wherein: When executed, the instructions further cause the UE to: If the unicast link of the UE is lost, or there is no feedback message sent by the receiving UE, an end marker corresponding to the sidelink radio bearer is generated.

7. One or more computer-readable media as claimed in claim 6, wherein: When executed, the instructions further cause the UE to: After receiving the feedback message from the receiving UE, decoding the feedback message for transmission or reception of one or more multiplexed packets; as well as Based on the decoded feedback message, it is determined whether the determined one or more QoS indicators are satisfied.

8. A device for a user equipment UE for efficient new radio NR side link vehicle-to-everything V2X communication, comprising: Processing circuitry for: determining one or more quality of service (QoS) parameters for a flow of packets generated by an application layer and to be sent by the UE in NR V2X communication; generating a sidelink radio bearer for the packetized flow according to a service data adaptation protocol SDAP based on the determined one or more QoS parameters; and an interface circuit coupled to the processing circuit, the interface circuit being configured to: Generating a QoS flow identification ID corresponding to the flow of the packet at the SDAP layer; as well as The stream of packets is sent to at least one recipient UE via one or more resources corresponding to the sidelink radio bearer.

9. The device of claim 8, wherein: The processing circuit is further configured to: For the flow sending the packet, one or more resources are determined in a network scheduled resource mode or an autonomous resource selection mode.

10. The device of claim 9, wherein: The processing circuit is further configured to: An end marker is generated in the sidelink radio bearer based on resource reselection for transmitting one or more transmit packets.

11. The device according to any one of claims 8 to 10, wherein: The processing circuit is further configured to generate an end marker in the sidelink radio bearer based on decoding a feedback message regarding reception of one or more transmitted packets, and the interface circuit is further configured to receive the feedback message from the receiving UE.