QoS Management Aspects For NR Side Link To Support Advanced V2X Case

Abstract

The invention relates to QoS management aspects for NR side links to support advanced V2X use cases. There is provided an apparatus of a first user equipment (UE) comprising one or more baseband processors to generate a message for a second UE to configure a new air interface (NR) vehicle-to-everything (V2X) link between the first UE and the second UE, where the message comprises a quality of service (QoS) metric to encode a plurality of QoS parameters for the NR V2X link; and encoding a packet of the second UE according to the QoS parameter. The apparatus may include a memory to store the message.

Description

[0001] Division Statement

[0002] This application is a divisional application of the Chinese invention patent application with the application date of September 27, 2019, the invention name of “QoS management aspects of NR side link to support advanced V2X use cases” and the application number of 201980063661.X.

[0003] CROSS-REFERENCE TO RELATED APPLICATIONS

[0004] This application claims the benefit of U.S. Provisional Application No. 62 / 737,488 (AB5639-Z), filed on September 27, 2018. Said application No. 62 / 737,488 is hereby incorporated by reference in its entirety. Technical Field

[0005] The present application relates to the field of wireless communication technology, and more specifically to QoS management aspects of NR sidelink to support advanced V2X use cases. Background Art

[0006] As the use of New Radio (NR) becomes common and widespread, and new use cases for advanced vehicle-to-vehicle communications are identified, mechanisms for NR-based systems should be supported to meet the relevant requirements of these use cases. As the 3rd Generation Partnership Project (3GPP) Vehicle-to-Everything (V2X) standards evolve to incorporate advanced V2X use cases beyond road safety applications, NR-based V2X should be adapted to be able to meet the various requirements set by these use cases. These include aspects such as latency - from three milliseconds (ms) to 100ms in the case of emergency trajectory changes, end-to-end reliability - from 90% to 99.999%, data rates - up to 1000 megabits per second (Mbps) for extended sensor use cases, etc. These technologies are more stringent and varied than the basic V2X use cases addressed in Long Term Evolution (LTE) V2X. The following parameters attempt to represent these service requirements for NR V2X.

[0007] Payload (bytes)

[0008] Transmission rate (messages / second)

[0009] Maximum end-to-end delay (ms)

[0010] ·reliability(%)

[0011] Data rate (Mbps)

[0012] Minimum required communication range (meters)

[0013] To meet such requirements, the Quality of Service (QoS) framework of NR V2X should be enhanced compared to LTE. Summary of the invention

[0014] Some embodiments of the present application provide a device, comprising a processing circuit, wherein the processing circuit is configured to: generate a message for transmission to a user equipment (UE), wherein the message is used to configure a new radio (NR) vehicle-to-everything (V2X) link with the UE, wherein the message includes a quality of service (QoS) metric, wherein the QoS metric represents a set of QoS parameters including a priority parameter value for the NR V2X link; and process one or more packets of the UE according to the QoS parameters.

[0015] Some embodiments of the present application also provide a first user equipment (UE), wherein the first UE includes a transceiver, which is configured to communicate with a second UE; a processor, which is communicatively coupled to the transceiver and is configured to: generate a message for transmission to the second UE, the message is used to configure a new radio (NR) vehicle-to-everything (V2X) link between the first UE and the second UE, wherein the message includes a quality of service (QoS) metric, and the QoS metric represents a set of QoS parameters including a priority parameter value for the NR V2X link; and process one or more packets of the second UE according to the QoS parameters.

[0016] Some embodiments of the present application also provide a method, comprising: generating a message for transmission to a user equipment (UE), the message being used to configure a new radio (NR) vehicle-to-everything (V2X) link with the UE, wherein the message comprises a quality of service (QoS) metric, the QoS metric representing a set of QoS parameters including a priority parameter value for the NR V2X link; and processing one or more packets of the UE according to the QoS parameters. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The claimed subject matter is particularly pointed out and distinctly described in the concluding portion of the specification. However, such subject matter may be understood by reference to the following detailed description when reading the accompanying drawings, wherein:

[0018] Figure 1 is an illustration of mapping various quality of service (QoS) related parameters to a unique identifier according to one or more embodiments.

[0019] Figure 2 The architecture of a system of networks according to some embodiments is shown.

[0020] Figure 3 Example components of an apparatus according to some embodiments are shown.

[0021] Figure 4 An example interface of a baseband circuit according to some embodiments is shown.

[0022] It should be understood that for simplicity and / or clarity of illustration, the elements illustrated in the figures are not necessarily drawn to scale. For example, for clarity, the size of some elements may be enlarged relative to other elements. In addition, if deemed appropriate, reference numerals are repeated in the drawings to indicate corresponding and / or similar elements. DETAILED DESCRIPTION

[0023] In the following detailed description, a number of specific details are provided to provide a comprehensive understanding of the claimed subject matter. However, it will be appreciated by those skilled in the art that the claimed subject matter may be implemented without these specific details. In other cases, well-known methods, processes, components and / or circuits have not yet been described in detail.

[0024] In the following description and / or claims, the terms "coupled" and "connected" and their derivatives may be used. In a particular embodiment, "connected" may be used to indicate that two or more elements are in direct physical and / or electrical contact with each other. "Coupled" may represent that two or more elements are in direct physical and / or electrical contact. However, "coupled" may also refer to that two or more elements may not be in direct contact with each other, but may still cooperate and / or interact with each other. For example, "coupled" may refer to that two or more elements are not in direct contact with each other, but are indirectly joined together via another element or an intermediate element. Finally, the terms "on", "overlying" and "above" may be used in the following description and claims. "On", "overlying" and "above" may be used to indicate that two or more elements are in direct physical contact with each other. However, it should be noted that "above" may also refer to that two or more elements are not in direct contact with each other. For example, "above" may represent that an element is higher than another element but is not in contact with each other, and another one or more elements may be present between the two elements. Furthermore, the term "and / or" may mean "and", it may mean "or", it may mean "exclusive or", it may mean "one", it may mean "some but not all", it may mean "neither", and / or it may mean "both", but does not limit the scope of the claimed subject matter in this regard. In the following description and / or claims, the terms "include" and "comprising", along with their derivatives, may be used and are intended to be synonymous with each other.

[0025] See now Figure 1, a diagram of mapping various quality of service (QoS) related parameters to a unique identifier according to one or more embodiments will be discussed. The overall long term evolution (LTE) based vehicle-to-everything (V2X) design on the sidelink is inherently based on broadcast, where all packets sent by the vehicle user equipment (V-UE) device over the sidelink are sent blindly and optionally have a fixed number of retransmissions. Therefore, the quality of service (QoS) provided by this broadcast mechanism is based on indicating a single priority value associated with each V2X packet, namely the proximity service (ProSe) per-packet priority (PPPP). This is used as the primary QoS metric for any access stratum (AS) layer process (e.g., media access control (MAC) scheduling and / or multiplexing for transmission and resource selection and / or reservation processes). This is in contrast to operations on Uu, where QoS management on Uu is based on radio resource control (RRC) configuration of appropriate MAC layer parameters associated with a specific logical channel. In Release 15 of the 3rd Generation Partnership Project (3GPP) standard, the concept of repeated transmissions on multiple carriers at the Packet Data Convergence Protocol (PDCP) layer was added to enhance reliability and an additional QoS metric for indicating the reliability requirement of ProSe Per Packet Reliability (PPPR) for each packet. However, due to the inherent broadcast nature of V2X transmissions, there is no concept of feedback. This has the following consequences: QoS for LTE V2X is packet driven, where each packet has some QoS parameter or parameters associated with it, and the radio layer attempts to meet the associated QoS requirements on a per-packet basis.

[0026] For the New Radio (NR), one concept is to establish a one-to-one or one-to-many connection on the side link, which allows unicast or multicast V2X communication. This means that the UE should establish a connection and exchange the necessary information and related rules to reach an agreed means of communication. One of these rules is the expected QoS to be provided by such a link. This also raises the fundamental question of whether the QoS framework for such unicast and / or multicast links should directly follow the per-packet QoS approach in LTE. When considering QoS requirements, regardless of whether the application and / or upper layers distinguish between radio access technologies (RATs) and interfaces, the question is whether the QoS framework of NR can be based on LTE at all in its design philosophy. In this regard, the problem can be solved by considering extending the per-packet QoS in LTE to the NR side link and defining unified QoS metrics to simplify the lower layer operations.

[0027] Another aspect to consider is that NR resource allocation for sidelink transmission is expected to follow LTE mechanisms, with two different modes: network scheduled transmission where the evolved Node B (eNB) schedules specific resources and autonomous resource reservation and / or reselection mode where the UE selects resources based on sensing. For the latter case, since it is inherently based on the concept of collision detection and avoidance on a broadcast channel, QoS requirements may or may not be strictly guaranteed unless non-contention resources are allocated for this purpose.

[0028] As discussed above for the case of LTE, each packet generated by the application layer is assigned a PC5 QoS identifier or parameter based on some mapping performed by the V2X function. The packet is then passed to the AS layer along with this QoS parameter. The same principle can be simply extended to at least NR V2X broadcast transmissions over the sidelink. The exact parameter or parameters to be indicated may be different and may evolve compared to LTE to meet the NR V2X use case requirements as described below. Given the set of parameters outlined above, each parameter is shown separately below according to its impact on the AS layer process for QoS.

[0029]

[0030] Table 1: QoS parameters and their impact on the AS layer

[0031] In LTE, the packet delay budget (PDB) associated with each packet is derived from the priority metric PPPP, so from the AS layer perspective, they can be considered equivalent. Alternatively, if priority is envisioned as an independent metric, both delay and priority can be indicated separately. This can be used, for example, for L1 resource preemption of critical V2X services. Considering operation in network control mode, assuming that at least the delay and / or priority and reliability requirements of QoS need to be considered, the MAC layer routines can follow similar behavior as in LTE.

[0032] Buffer Status Report (BSR) reporting based on priority, delay and reliability

[0033] • Logical Channel ID (LCID) mapping and multiplexing of protocols; priority and delay based data units (PDUs) and subsequent indication to the underlying layers.

[0034] In addition, for the autonomous resource selection mode, the following may be the same as that of LTE.

[0035] • The mapping of LCID to priority, delay and reliability may be specified or configured as in LTE or left to UE specific implementation, depending on whether stricter NW control of such mapping at the UE for the sidelink is required.

[0036] Scheduling across different / multiple carriers based on data rate requirements and / or reliability

[0037] Use of QoS metrics reserved by resource pools in addition to zone configuration

[0038] Physical layer related procedures such as resource reservation / selection also need to be considered in MAC. It is expected that the physical layer procedures for autonomous cases will be enhanced compared to LTE to handle issues such as congestion and extensive resource usage by high priority transmissions, which may otherwise lead to resource starvation of other UEs.

[0039] Regarding the abundance of possible values ​​that should be addressed, at least the parameters dealing with priority and reliability requirements can be defined with additional granularity. As a comparison for LTE, eight unique values ​​are defined for PPPP and PPPR to represent priority and reliability, respectively. For NR, taking into account the wider range of requirements, up to 16 values ​​can be considered for both parameters.

[0040] In addition, the association of QoS parameters at the AS layer with a single comprehensive metric may be considered based on some configured or pre-configured mapping to simplify lower layer operations. For example, an overall QoS priority metric representing a set of specific priority, delay, and reliability values ​​may be considered. The granularity of such mappings may be configured to fit a wide variety of scenarios. The upper layers may perform the mapping and simply indicate the relevant value of the new QoS metric to the AS layer, or the mapping may be configured at the AS layer and may be used to map each incoming packet to a relevant value, such as Figure 1 As shown. Figure 1 100, assuming that PPPP and PPPR span a set of values ​​from 1 to 16. In addition, it should be noted that delay requirements or equivalent metrics can be mapped in an overlapping manner. In general, such mappings can be highly flexible if desired to meet different coverage and deployment scenarios (if desired), or the mappings can be hard-coded in the specification for ease of implementation.

[0041] A big advantage of reusing the per-packet QoS approach from LTE is the compatibility with legacy architectures. For example, NR V2X UEs should be able to support legacy V2X services and be able to interact with legacy V2X UEs. This means that any new QoS mechanism should be flexible enough to handle legacy QoS based on PPPP. Reusing the same approach for per-packet QoS allows this situation to be easily handled, even with a different granularity, for example by configuring a mapping between new unified QoS parameters and legacy PPPP values. Another advantage is the flexible QoS handling of V2X packets with different characteristics generated by the same application. A given V2X service may generate packets with different QoS requirements, and using a per-packet based approach allows the AS layer to handle these packets in a simple and efficient way.

[0042] Furthermore, based on whether unicast communications for the NR sidelink for V2X are supported, the question is whether the per-packet QoS is sufficient or needs further enhancement. Assuming this involves setting up a secure layer 2 link between the two UEs over the sidelink, two different options can be considered.

[0043] In the first option, once the unicast link is established, the upper layers can still follow the same behavior as in broadcast, where each packet has an associated set of QoS parameters or a unified QoS metric. The MAC layer process can simply follow the same rules as broadcast for correctly handling the packet.

[0044] In the second option, a mapping between a unique link ID, which may be based on a unique source and destination identifier tuple, and a V2X service is created based on some pre-negotiation between the two UEs to agree on specific QoS characteristics associated with the link. Subsequently, only the corresponding link ID next to each packet is indicated, and a new sublayer responsible for maintaining the mapping and informing the AS layer of the set of QoS parameters or combined QoS metrics required for the link may be provided. In the case where the QoS characteristics of all packets for the link do not change (which may not always be true), the main advantages are enhanced efficiency and reduced signaling. For example, in the case of advanced driving, a unicast link is otherwise established for high data rates, but with low reliability. For example, video sharing will not have suitable QoS support for emergency collision avoidance and emergency trajectory alignment. In this case, the UE may have to rely on a broadcast mechanism or some other option to send this critical packet anyway.

[0045] Figure 2 The architecture of a system 200 of a network according to some embodiments is shown. System 200 is shown to include user equipment (UE) 201 and UE 202. UE 201 and UE 202 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but these UEs can also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handheld terminals, or any computing device that includes a wireless communication interface.

[0046] In some embodiments, either UE 201 and UE 202 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 machine-to-machine (M2M) or machine-type communication (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) communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0047] UE 201 and UE 202 may be configured to connect, e.g., be communicatively coupled, to a radio access network (RAN) 210, which may be, e.g., an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or some other type of RAN. UE 201 and UE 202 utilize connection 203 and connection 204, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connection 203 and connection 204 are shown as air interfaces to achieve communicatively coupling, and may be consistent with a cellular communication protocol, such as a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a cellular PTT (POC) protocol, a universal mobile telecommunications system (UMTS) protocol, a 3GPP long term evolution (LTE) protocol, a fifth generation (5G) protocol, a new radio (NR) protocol, etc.

[0048] In this embodiment, UE 201 and UE 202 may also directly exchange communication data via ProSe interface 205. ProSe interface 205 may alternatively be referred to as a sidelink interface including one or more logical channels including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0049] UE 202 is shown as being configured to access access point (AP) 206 via connection 207. Connection 207 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 206 would include wireless fidelity. In this example, AP 206 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below).

[0050] The RAN 210 may include one or more access nodes that enable connection 203 and connection 204. These access nodes (ANs) may be referred to as base stations (BSs), Node Bs, evolved Node Bs (eNBs), next generation Node Bs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The RAN 210 may include one or more RAN nodes (e.g., macro RAN nodes 211) for providing macro cells, and one or more RAN nodes (e.g., low power (LP) RAN nodes 212) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).

[0051] Either of the RAN node 211 and the RAN node 212 may terminate the air interface protocol and may be the first point of contact for the UE 201 and the UE 202. In some embodiments, either of the RAN nodes 211 and 212 may fulfill various logical functions of the RAN 210, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0052] According to some embodiments, UE 201 and UE 202 may be configured to communicate with each other or with any of RAN node 211 and RAN node 212 through a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communication) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0053] In some embodiments, a downlink resource grid may be used for downlink transmissions from either of RAN node 211 and RAN node 212 to UE 201 and UE 202, 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. For OFDM systems, such a time-frequency plane representation is common practice, which makes wireless resource allocation intuitive. Each column and each 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 a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0054] The physical downlink shared channel (PDSCH) may carry user data and higher layer signaling to UE 201 and UE 202. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocation related to the PDSCH channel, among other things. It may also inform UE 201 and UE 202 of the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 102 within a cell) may be performed at either RAN node 211 or RAN node 212 based on channel quality information fed back from either UE 201 or UE 202. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UE 201 and UE 202.

[0055] PDCCH can use control channel elements (CCE) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to four sets of nine physical resource elements, called resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0056] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. 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 EPDCCH. Similar to the above, each ECCE may correspond to four sets of nine physical resource elements, referred to as enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.

[0057] RAN 210 is shown as being communicatively coupled to a core network (CN) 220 via an S1 interface 213. In various embodiments, CN 220 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 213 is divided into two parts: S1-U interface 214, which carries traffic data between RAN node 211 and RAN node 212 and serving gateway (S-GW) 222; and S1-mobility management entity (MME) interface 215, which is a signaling interface between RAN node 211 and RAN node 212 and MME 221.

[0058] In this embodiment, CN 220 includes MME 221, S-GW 222, Packet Data Network (PDN) Gateway (P-GW) 223 and Home Subscriber Server (HSS) 224. MME 221 may be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 221 may manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 224 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. Depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc., CN 220 may include one or more HSS 224. For example, HSS 224 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0059] The S-GW 222 may terminate the S1 interface 213 towards the RAN 210 and route data packets between the RAN 210 and the CN 220. In addition, the S-GW 222 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies.

[0060] The P-GW 223 may terminate the SGi interface toward the PDN. The P-GW 223 may route data packets between the EPC network 223 and an external network such as a network including an application server 230 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 225. Generally, the application server 230 may be an element that provides an application that uses IP bearer resources with a core network (e.g., a UMTS packet service (PS) domain, a LTE PS data service, etc.). In this embodiment, the P-GW 223 is shown as being communicatively coupled to the application server 230 via an IP communication interface 225. The application server 230 may also be configured to support one or more communication services (e.g., voice over Internet protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 201 and UE 202 via the CN 220.

[0061] The P-GW 223 may also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) 226 is a policy and charging control element of the CN 220. In a non-roaming scenario, there may be a single PCRF in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of the UE. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the UE's IP-CAN session: a domestic PCRF (H-PCRF) within the HPLMN and a visited PCRF (V-PCRF) within a visited public land mobile network (VPLMN). The PCRF 226 may be communicatively coupled to the application server 230 via the P-GW 223. The application server 230 may signal the PCRF 226 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 226 may configure the rule to a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by application server 230 .

[0062] Figure 3Example components of a device 300 according to some embodiments are shown. In some embodiments, the device 300 may include an application circuit 302, a baseband circuit 304, a radio frequency (RF) circuit 306, a front-end module (FEM) circuit 308, one or more antennas 310, and a power management circuit (PMC) 312 (at least coupled together as shown). The components of the illustrated device 300 may be included in a UE or a RAN node. In some embodiments, the device 300 may include fewer elements (e.g., the RAN node cannot utilize the application circuit 302, but includes a processor / controller to process IP data received from the EPC). In some embodiments, the device 300 may include additional elements, such as, for example, 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., the circuit may be separately included in more than one device for a cloud-RAN (C-RAN) implementation).

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

[0064] The baseband circuit 304 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 304 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 306 and generate baseband signals for the transmit signal path of the RF circuit 306. The baseband processing circuit 304 may interact with the application circuit 302 to generate and process baseband signals and control the operation of the RF circuit 306. For example, in some embodiments, the baseband circuit 304 may include a third generation (3G) baseband processor 304A, a fourth generation (4G) baseband processor 304B, a fifth generation (5G base) band processor 304C, or one or more other baseband processors 304D of 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 circuit 304 (e.g., one or more baseband processors in the baseband processors 304A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuit 306. In other embodiments, some or all of the functions of the baseband processors 304A-304D may be included in a module stored in the memory 304G and executed via the central processing unit (CPU) 304E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 304 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 304 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0065] In some embodiments, the baseband circuit 304 may include one or more audio digital signal processors (DSPs) 304F. The audio DSP 304F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 304 and the application circuit 302 may be implemented together, such as on a system on a chip (SOC).

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

[0067] RF circuit 306 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 306 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 306 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 308 and providing baseband signals to baseband circuit 304. RF circuit 306 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 304 and providing RF output signals for transmission to FEM circuit 308.

[0068] In some embodiments, the receive signal path of the RF circuit 306 may include a mixer circuit 306a, an amplifier circuit 306b, and a filter circuit 306c. In some embodiments, the transmit signal path of the RF circuit 306 may include a filter circuit 306c and a mixer circuit 306a. The RF circuit 306 may also include a synthesizer circuit 306d for synthesizing the frequencies used by the mixer circuit 306a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 306a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 308 based on the synthesized frequency provided by the synthesizer circuit 306d. The amplifier circuit 306b may be configured to amplify the down-converted signal, and the filter circuit 306c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 304 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, mixer circuit 306a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0069] In some embodiments, mixer circuit 306a of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 306d to generate an RF output signal for FEM circuit 308. The baseband signal may be provided by baseband circuit 304 and may be filtered by filter circuit 306c.

[0070] In some embodiments, the mixer circuit 306a of the receiving signal path and the mixer circuit 306a of the transmitting signal path may include two or more mixers and may be arranged to be used for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 306a of the receiving signal path and the mixer circuit 306a of the transmitting signal path may include two or more mixers and may be arranged to be used for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 306a of the receiving signal path and the mixer circuit 306a of the transmitting signal path may be arranged to be used for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 306a of the receiving signal path and the mixer circuit 306a of the transmitting signal path may be configured for superheterodyne operation.

[0071] 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 306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 304 may include a digital baseband interface to communicate with RF circuit 306.

[0072] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect. In some embodiments, synthesizer circuit 306 d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 306 d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0073] Synthesizer circuit 306d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 306a of RF circuit 306. In some embodiments, synthesizer circuit 306d may be a fractional-N / N+1 synthesizer.

[0074] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuit 304 or the application processor 302 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 302.

[0075] The synthesizer circuit 306d of the RF circuit 306 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0076] In some embodiments, the synthesizer circuit 306d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 306 can include an IQ / polarity converter.

[0077] The FEM circuitry 308 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 310, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 306 for further processing. The FEM circuitry 308 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 306 for transmission through one or more of the one or more antennas 310. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 306, only in the FEM 308, or in both the RF circuitry 306 and the FEM 308.

[0078] In some embodiments, the FEM circuit 308 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 306). The transmit signal path of the FEM circuit 308 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 306); and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 310).

[0079] In some embodiments, PMC 312 can manage the power provided to baseband circuit 304. Specifically, PMC 312 can control power selection, voltage scaling, battery charging, or DC to DC conversion. When device 300 is capable of being powered by a battery, for example, when the device is included in a UE, PMC 312 can generally be included. PMC 312 can improve power conversion efficiency while providing the desired specific implementation size and heat dissipation characteristics.

[0080] and Figure 3 PMC 312 is shown coupled only to baseband circuitry 304. However, in other embodiments, PMC 312 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 302, RF circuitry 306, or FEM 308) and perform similar power management operations.

[0081] In some embodiments, the PMC 312 may control or otherwise be part of various power saving mechanisms of the device 300. For example, if the device 300 is in an RRC connected state, in which the device is still connected to a RAN node because the device expects to receive communications soon, the device may enter a state called discontinuous reception mode (DRX) after a period of inactivity. During this state, the device 300 may be powered off for short time intervals, thereby saving power.

[0082] If there is no data traffic activity for an extended period of time, the device 300 may transition to the RRC Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The device 300 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 300 cannot receive data in this state, and in order to receive data, it must transition back to the RRC_Connected state.

[0083] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0084] The processor of the application circuit 302 and the processor of the baseband circuit 304 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 304 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 304 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, 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 will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0085] Figure 4 An example interface of a baseband circuit according to some embodiments is shown. As discussed above, Figure 3 The baseband circuit 304 may include processors 304A-304E and a memory 304G utilized by the processors. Each of the processors 304A-304E may include a memory interface 404A-404E, respectively, for sending / receiving data to / from the memory 304G.

[0086] The baseband circuit 304 may also include: one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 412 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 304); an application circuit interface 414 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 304); Figure 3 RF circuit interface 416 (for example, for sending / receiving data to / from the application circuit 302); Figure 3 an interface for sending / receiving data to / from a RF circuit 306); a wireless hardware connection interface 418 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low Energy), components and other communication components to send / receive data); and a power management interface 420 (for example, an interface for sending / receiving power or control signals to / from PMC312).

[0087] The following is an exemplary implementation of the subject matter described herein. In Example 1, an apparatus of a first user equipment (UE) includes one or more baseband processors and a memory for storing a message, the one or more baseband processors generating a message for a second UE to configure a new radio (NR) vehicle-to-everything (V2X) link between the first UE and the second UE, wherein the message includes a quality of service (QoS) metric to encode a plurality of QoS parameters for the NR V2X link, and encodes a packet of the second UE according to the QoS parameter. In Example 2, the QoS metric includes a proximity service (ProSe) per-packet priority (PPPP) parameter with a value of 1 to 16. In Example 3, the QoS metric includes a proximity service (ProSe) per-packet reliability (PPPP) parameter with a value of 1 to 16. In Example 4, the QoS metric includes a delay requirement parameter. In Example 5, the QoS parameter is selected based on the intended use of the NR V2X link. In Example 6, the message will be broadcast to multiple UEs, and the QoS metric is selected based on the operating mode of the NR V2X side link. In Example 7, the QoS parameter includes a subset of available QoS parameters for the NR V2X link. In Example 8, the message will be broadcast using the same QoS metric as the unicast link between the first UE and the second UE. In Example 9, the first UE and the second UE will exchange QoS parameters to be used on the NR V2X link. In Example 10, the QoS parameters are mapped to a unique source identifier (ID) and a unique destination ID for the NR V2X link.

[0088] In Example 11, one or more machine-readable media have instructions thereon that, when executed by a device of a first user equipment (UE), result in generating a message for a second UE to configure a new radio (NR) vehicle-to-everything (V2X) link between the first UE and the second UE, wherein the message includes a quality of service (QoS) metric to encode a plurality of QoS parameters for the NR V2X link, and encodes a packet of the second UE according to the QoS parameter. In Example 12, the QoS metric includes a proximity service (ProSe) per-packet priority (PPPP) parameter with a value of 1 to 16. In Example 13, the QoS metric includes a proximity service (ProSe) per-packet reliability (PPPP) parameter with a value of 1 to 16. In Example 14, the QoS metric includes a delay requirement parameter. In Example 15, the QoS parameter is selected based on the intended use of the NR V2X link. In Example 16, the message is to be broadcast to a plurality of UEs, and the QoS metric is selected based on the operating mode of the NR V2X side link. In Example 17, the QoS parameter includes a subset of available QoS parameters for the NR V2X link. In Example 18, the message will be broadcast using the same QoS metric as the unicast link between the first UE and the second UE. In Example 19, the first UE and the second UE will exchange QoS parameters to be used on the NR V2X link. In Example 20, the QoS parameters are mapped to a unique source identifier (ID) and a unique destination ID for the NR V2X link.

[0089] While the claimed subject matter has been described with a certain degree of particularity, it will be appreciated that elements of the claimed subject matter may be varied by those skilled in the art without departing from the spirit and / or scope of the claimed subject matter. It is believed that the subject matter relating to QoS management aspects of the nr sidelink to support advanced V2X use cases and its many attendant utilities will be understood from the foregoing description, and it will be apparent that various changes may be made in the form, construction and / or arrangement of its components without departing from the scope and / or spirit of the claimed subject matter, or without sacrificing all of its material advantages, the forms described above being merely illustrative embodiments of the components and / or further providing no substantial changes thereto. It is the intent of the claims to encompass and / or include such variations.

Claims

1. An apparatus, comprising a processing circuit, wherein the processing circuit is configured to: generating a message for transmission to a user equipment (UE), the message being used to configure a new radio (NR) vehicle-to-everything (V2X) link with the UE, wherein the message includes a quality of service (QoS) metric representing a set of QoS parameters including a priority parameter value for the NR V2X link; and One or more packets for the UE are processed according to the QoS parameters.

2. The apparatus of claim 1 , wherein the NR V2X link supports broadcast communications.

3. The apparatus of claim 1 , wherein the NR V2X link supports multicast communication.

4. The apparatus of claim 1 , wherein the NR V2X link supports unicast communication.

5. The apparatus of claim 1, wherein the QoS parameters further include a delay parameter value and a reliability parameter value.

6. The apparatus of claim 1, wherein the QoS parameters are defined for each flow of the NRV2X link.

7. The apparatus of claim 1, wherein the QoS parameters are associated with access stratum (AS) procedures.

8. The apparatus of claim 1, wherein the QoS parameters are associated with non-access stratum (NAS) procedures.

9. A first user equipment (UE), the first UE comprising: a transceiver configured to communicate with a second UE; a processor communicatively coupled to the transceiver and configured to: generating a message for transmission to the second UE, the message being used to configure a New Radio (NR) Vehicle-to-Everything (V2X) link between the first UE and the second UE, wherein the message includes a Quality of Service (QoS) metric, The QoS metric represents a set of QoS parameters including a priority parameter value for the NR V2X link; as well as One or more packets for the second UE are processed according to the QoS parameters.

10. The first UE of claim 9, wherein the NR V2X link supports broadcast communications.

11. The first UE according to claim 9, wherein the NR V2X link supports multicast communication.

12. The first UE according to claim 9, wherein the NR V2X link supports unicast communication.

13. The first UE according to claim 9, wherein the QoS parameters further include a delay parameter value and a reliability parameter value.

14. The first UE according to claim 9, wherein the QoS parameters are defined for each flow of the NR V2X link.

15. The first UE of claim 9, wherein the QoS parameter is associated with an access stratum (AS) procedure.

16. The first UE of claim 9, wherein the QoS parameter is associated with a non-access stratum (NAS) procedure.

17. The first UE of claim 9, wherein the transceiver is configured to transmit the message to the second UE.

18. The first UE of claim 9, wherein the transceiver is configured to transmit or receive the one or more packets of the second UE.

19. A method comprising: generating a message for transmission to a user equipment (UE), the message being used to configure a new radio (NR) vehicle-to-everything (V2X) link with the UE, wherein the message includes a quality of service (QoS) metric representing a set of QoS parameters including a priority parameter value for the NR V2X link; as well as One or more packets for the UE are processed according to the QoS parameters.

20. The method of claim 19, wherein the NR V2X link supports broadcast communication, multicast communication, or unicast communication.

Images