WO2020069291A1 - Aspects de gestion de qos permettant à une liaison latérale nr de prendre en charge des cas d'utilisation v2x avancés - Google Patents

Aspects de gestion de qos permettant à une liaison latérale nr de prendre en charge des cas d'utilisation v2x avancés Download PDF

Info

Publication number
WO2020069291A1
WO2020069291A1 PCT/US2019/053417 US2019053417W WO2020069291A1 WO 2020069291 A1 WO2020069291 A1 WO 2020069291A1 US 2019053417 W US2019053417 W US 2019053417W WO 2020069291 A1 WO2020069291 A1 WO 2020069291A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos
link
circuitry
parameter
metric
Prior art date
Application number
PCT/US2019/053417
Other languages
English (en)
Inventor
Ansab ALI
Keyongin JEONG
Sangeetha L. Bangolae
Youn Hyoung Heo
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN201980063661.XA priority Critical patent/CN113243122A/zh
Priority to US17/250,920 priority patent/US11997530B2/en
Publication of WO2020069291A1 publication Critical patent/WO2020069291A1/fr
Priority to US18/668,349 priority patent/US20240306032A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • NR New Radio
  • 3 GPP Third Generation Partnership Project
  • V2X vehicle-to-everything
  • NR based V2X should adapt to be able to meet the diverse set of requirements set by these use cases. These include aspects such as latency, from three milliseconds (ms) in case of emergency trajectory change to 100 ms, end-to-end reliability, from 90% to 99.999%, data rate, up to 1000 megabits per second (Mbps) for extended sensor use case, and so on.
  • LTE Long Term Evolution
  • QoS Quality of Service
  • FIG. 1 is a diagram of mapping various Quality of Service (QoS) related parameters to a unique identifier in accordance with one or more embodiments.
  • QoS Quality of Service
  • FIG. 2 illustrates an architecture of a system of a network in accordance with some embodiments.
  • FIG. 3 illustrates example components of a device in accordance with some embodiments.
  • FIG. 4 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • Coupled may mean that two or more elements are in direct physical and/or electrical contact.
  • coupled may also mean that two or more elements may not be in direct contact with each other, but yet may still cooperate and/or interact with each other.
  • “coupled” may mean that two or more elements do not contact each other but are indirectly joined together via another element or intermediate elements.
  • “On,” “overlying,” and “over” may be used to indicate that two or more elements are in direct physical contact with each other. It should be noted, however, that “over” may also mean that two or more elements are not in direct contact with each other. For example, “over” may mean that one element is above another element but not contact each other and may have another element or elements in between the two elements.
  • 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”, although the scope of claimed subject matter is not limited in this respect.
  • the terms “comprise” and “include,” along with their derivatives, may be used and are intended as synonyms for each other.
  • FIG. 1 a diagram of mapping various Quality of Service (QoS) related parameters to a unique identifier in accordance with one or more embodiments will be discussed.
  • LTE Long Term Evolution
  • V2X vehicle-to-everything
  • QoS Quality of Service
  • QoS Quality of Service
  • ProSe Proximity Services
  • PPPP per-packet priority
  • AS access stratum
  • MAC media access control
  • RRC radio resource control
  • the concept of duplicated transmissions on multiple carriers at the Packet Data Convergence Protocol (PDCP) layer was added to enhance reliability and an additional QoS metric for indicating reliability requirement for each packet for ProSe per-packet reliability (PPPR).
  • PDCP Packet Data Convergence Protocol
  • PPPR ProSe per-packet reliability
  • NR New Radio
  • one concept is establishment of one-to-one or one-to-many connections over sidelink which allow for unicast or groupcast V2X communication. This implies that the UEs shall set up a connection and exchange necessary information and related rules to agree upon a common means of communication.
  • One of these rules is the expected QoS to be afforded by such a link. This also raises a fundamental question as to whether the QoS framework for such unicast and/or groupcast links should directly follow the per-packet QoS methodology in LTE.
  • the question is whether the QoS framework for NR fundamentally can be based on LTE in its design philosophy. In this regard, this question can be addressed by considering the extension of per-packet QoS as in LTE to NR sidelink as well as defining a unified QoS metric to simplify lower layer operations.
  • RATs radio access technologies
  • NR resource allocation for sidelink transmission is expected to follow the LTE mechanism wherein two distinct modes: the network scheduled transmissions where the evolved NodeB (eNB) schedules specific resources and the autonomous resources reservation and/or reselection mode where the UE selects resources based on sensing.
  • eNB evolved NodeB
  • the autonomous resources reservation and/or reselection mode where the UE selects resources based on sensing.
  • QoS requirements may or may not be strictly guaranteed unless non-contention resources are allocated for this purpose.
  • each packet generated by the application layer is assigned a PC5 QoS identifier or parameter based on some mapping by the V2X function.
  • the packet is then passed to the AS layer along with this QoS parameter.
  • the same principle can simply be extended to at least NR V2X broadcast transmission over sidelink.
  • the exact parameter or parameters to be indicated can be different and can evolve compared to LTE to meet the NR V2X use case requirement as discussed below.
  • each parameter is shown individually below in terms of their impact on the AS layer procedures for QoS.
  • the packet delay budget (PDB) associated with each packet was derived from the priority metric PPPP, so from the AS layer point of view, they can be considered equivalent.
  • both latency and priority can be separately indicated if it is envisioned that priority is a standalone metric. For example, this can be useful for Ll resource pre-emption for critical V2X services.
  • the MAC layer routines can follow similar behavior as in LTE.
  • BSR Buffer Status Reporting
  • LCID Logical Channel ID mapping and multiplexing of protocol
  • PDUs data units
  • mapping of LCIDs to priority, latency and reliability can be specified or configured, or left to the UE implementation as in LTE, depending on whether there is a need for stricter NW control on such mapping at the UE for sidelink.
  • Physical layer related procedures such as resource reservation/selection will also need to be considered in MAC. It is expected that physical layer procedures for autonomous case will be enhanced compared to LTE to handle issues such as congestion and extensive resource usage by high priority transmissions which can otherwise result in resource starvation for other UEs.
  • the unification of the QoS parameters at the AS layer to a single, comprehensive metric can be considered based on some configured or preconfigured mapping to simplify lower layer operations.
  • an overall QoS priority metric which represents set of specific priority, delay, and reliability values can be considered.
  • the granularity of such mapping can be configurable to cater to a wide variety of scenarios.
  • the upper layer can either perform this mapping and simply indicate the relevant value for this new QoS metric to the AS layer or this mapping can be configured at the AS layer and can be used to map each incoming packet to the relevant value, as shown in FIG. 1.
  • mapping can be highly flexible if required to cater to different coverage and deployment scenarios if needed, or the mapping can be hardcoded in the specification for ease of implementation.
  • One big advantage to reusing the per-packet QoS methodology from LTE is compatibility with legacy architectures. For instance, a NR V2X UE 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 the legacy QoS based on PPPP.
  • Reusing the same methodology of per packet QoS can allow this case to be handled easily, even with differing granularity, for example by configuring a mapping between the new unified QoS parameter and legacy PPPP values.
  • Another advantage is flexible QoS handling for V2X packets with differing characteristics generated by the same application. It is possible that a given V2X service generates packets with different QoS requirements and using the per-packet based methodology allows for the AS layer to handle these in a simple and efficient fashion.
  • the upper layer can still follow the same behavior as in broadcast wherein each packet has an associated set of QoS parameters, or the unified QoS metric.
  • the MAC layer procedures can simply follow the same rules as broadcast for proper processing of this packet.
  • a mapping between the unique link ID which can be for example based on unique source and destination identifier tuple, and the V2X service is created.
  • a new sublayer can be provided that is responsible for maintaining this mapping and informing the AS layer of the set of QoS parameters, or the combined QoS metric, required for this link.
  • a unicast link otherwise established for high data rate but low reliability For example, video sharing would not have suitable QoS support for emergency collision avoidance and emergency trajectory alignment.
  • the UE may have to rely on broadcast mechanism or some other option to send this critical packet anyway.
  • FIG. 2 illustrates an architecture of a system 200 of a network in accordance with some embodiments.
  • the system 200 is shown to include a user equipment (UE) 201 and a UE 202.
  • the UEs 201 and 202 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets or any computing device including a wireless communications interface.
  • any of the UEs 201 and 202 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to- device (D2D) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UEs 201 and 202 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 210—
  • the RAN 210 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 201 and 202 utilize connections 203 and 204, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 203 and 204 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, 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 PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 201 and 202 may further directly exchange communication data via a ProSe interface 205.
  • the ProSe interface 205 may alternatively be referred to as a sidelink interface comprising 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).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 202 is shown to be configured to access an access point (AP) 206 via connection 207.
  • the connection 207 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 206 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 206 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 210 can include one or more access nodes that enable the connections 203 and 204.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 210 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 211, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 212.
  • macro RAN node 211 e.g., macro RAN node 211
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes 211 and 212 can terminate the air interface protocol and can be the first point of contact for the UEs 201 and 202.
  • any of the RAN nodes 211 and 212 can fulfill various logical functions for the RAN 210 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs 201 and 202 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 211 and 212 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency- Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC- FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 211 and 212 to the UEs 201 and 202, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 201 and 202.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCFI channel, among other things. It may also inform the UEs 201 and 202 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 211 and 212 based on channel quality information fed back from any of the UEs 201 and 202.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 201 and 202.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 210 is shown to be communicatively coupled to a core network (CN) 220— via an Sl interface 213.
  • the CN 220 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the Sl interface 213 is split into two parts: the Sl-U interface 214, which carries traffic data between the RAN nodes 211 and 212 and the serving gateway (S-GW) 222, and the Sl -mobility management entity (MME) interface 215, which is a signaling interface between the RAN nodes 211 and 212 and MMEs 221.
  • S-GW serving gateway
  • MME Sl -mobility management entity
  • the CN 220 comprises the MMEs 221, the S-GW 222, the Packet Data Network (PDN) Gateway (P-GW) 223, and a home subscriber server (HSS) 224.
  • the MMEs 221 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 221 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 224 may comprise a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the CN 220 may comprise one or several HSSs 224, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 224 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 222 may terminate the Sl interface 213 towards the RAN 210, and routes data packets between the RAN 210 and the CN 220.
  • the S-GW 222 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 223 may terminate an SGi interface toward a PDN.
  • the P-GW 223 may route data packets between the EPC network 223 and external networks such as a network including the application server 230 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 225.
  • the application server 230 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 223 is shown to be communicatively coupled to an application server 230 via an IP communications interface 225.
  • the application server 230 can 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 UEs 201 and 202 via the CN 220.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 223 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 226 is the policy and charging control element of the CN 220.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • 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 the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 226 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 230.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • the device 300 may include application circuitry 302, baseband circuitry 304, Radio Frequency (RF) circuitry 306, front-end module (FEM) circuitry 308, one or more antennas 310, and power management circuitry (PMC) 312 coupled together at least as shown.
  • the components of the illustrated device 300 may be included in a UE or a RAN node.
  • the device 300 may include less elements (e.g., a RAN node may not utilize application circuitry 302, and instead include a processor/controller to process IP data received from an EPC).
  • the device 300 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .
  • C-RAN Cloud-RAN
  • the application circuitry 302 may include one or more application processors.
  • the application circuitry 302 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 300.
  • processors of application circuitry 302 may process IP data packets received from an EPC.
  • the baseband circuitry 304 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 304 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 306 and to generate baseband signals for a transmit signal path of the RF circuitry 306.
  • Baseband processing circuity 304 may interface with the application circuitry 302 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 306.
  • the baseband circuitry 304 may include a third generation (3G) baseband processor 304A, a fourth generation (4G) baseband processor 304B, a fifth generation (5G) baseband processor 304C, or other baseband processor(s) 304D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 304 e.g., one or more of baseband processors 304A-D
  • baseband processors 304A-D may be included in modules stored in the memory 304G and executed via a 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.
  • modulation/demodulation circuitry of the baseband circuitry 304 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 304 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 304 may include one or more audio digital signal processor(s) (DSP) 304F.
  • the audio DSP(s) 304F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 304 and the application circuitry 302 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 304 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 304 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • RF circuitry 306 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 306 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 306 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 308 and provide baseband signals to the baseband circuitry 304.
  • RF circuitry 306 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 304 and provide RF output signals to the FEM circuitry 308 for transmission.
  • the receive signal path of the RF circuitry 306 may include mixer circuitry 306a, amplifier circuitry 306b and filter circuitry 306c.
  • the transmit signal path of the RF circuitry 306 may include filter circuitry 306c and mixer circuitry 306a.
  • RF circuitry 306 may also include synthesizer circuitry 306d for synthesizing a frequency for use by the mixer circuitry 306a of the receive signal path and the transmit signal path.
  • the mixer circuitry 306a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 308 based on the synthesized frequency provided by synthesizer circuitry 306d.
  • the amplifier circuitry 306b may be configured to amplify the down-converted signals and the filter circuitry 306c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 304 for further processing.
  • the output baseband signals may be zero- frequency baseband signals, although this is not a requirement.
  • mixer circuitry 306a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 306a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 306d to generate RF output signals for the FEM circuitry 308.
  • the baseband signals may be provided by the baseband circuitry 304 and may be filtered by filter circuitry 306c.
  • the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 304 may include a digital baseband interface to communicate with the RF circuitry 306.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 306d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 306d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 306d may be configured to synthesize an output frequency for use by the mixer circuitry 306a of the RF circuitry 306 based on a frequency input and a divider control input.
  • the synthesizer circuitry 306d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage- controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage- controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 304 or the applications processor 302 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 302.
  • Synthesizer circuitry 306d of the RF circuitry 306 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • DLL delay-locked loop
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
  • synthesizer circuitry 306d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 306 may include an IQ/polar converter.
  • FEM circuitry 308 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 310, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 306 for further processing.
  • FEM circuitry 308 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 306 for transmission by one or more of the one or more antennas 310.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 306, solely in the FEM 308, or in both the RF circuitry 306 and the FEM 308.
  • the FEM circuitry 308 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 306).
  • the transmit signal path of the FEM circuitry 308 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 306), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 310).
  • PA power amplifier
  • the PMC 312 may manage power provided to the baseband circuitry 304. ln particular, the PMC 312 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 312 may often be included when the device 300 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 312 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • F1G. 3 shows the PMC 312 coupled only with the baseband circuitry 304.
  • the PMC 3 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 302, RF circuitry 306, or FEM 308.
  • 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, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 300 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 300 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 300 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 300 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 302 and processors of the baseband circuitry 304 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 304 may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 304 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 4 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 304 of FIG. 3 may comprise processors 304A-304E and a memory 304G utilized by said processors.
  • Each of the processors 304A-304E may include a memory interface, 404A-404E, respectively, to send/receive data to/from the memory 304G.
  • the baseband circuitry 304 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 412 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 304), an application circuitry interface 414 (e.g., an interface to send/receive data to/from the application circuitry 302 of FIG. 3), an RF circuitry interface 416 (e.g., an interface to send/receive data to/from RF circuitry 306 of FIG.
  • a memory interface 412 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 304
  • an application circuitry interface 414 e.g., an interface to send/receive data to/from the application circuitry 302 of FIG. 3
  • an RF circuitry interface 416 e.g., an interface to send/receive data to/from RF circuitry 306 of FIG.
  • a wireless hardware connectivity interface 418 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 420 e.g., an interface to send/receive power or control signals to/from the PMC 312.
  • an apparatus of a first user equipment comprises one or more baseband processors to generate a message for a second UE to configure a New Radio (NR) vehicle-to-everything (Y2X) 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 to encode a packet for the second UE according to the QoS parameter, and a memory to store the message.
  • the QoS metric includes a Proximity Services (ProSe) per- packet priority (PPPP) parameter having a value from one to 16.
  • ProSe Proximity Services
  • PPPP per- packet priority
  • the QoS metric includes a Proximity Services (ProSe) per-packet reliability (PPPP) parameter having a value from one to 16.
  • the QoS metric includes latency requirement parameter.
  • the QoS parameters are selected based on an intended use for the NR V2X link.
  • the message is to be broadcast to a plurality of UE and the QoS metric is selected based on an operational mode for the NR V2X sidelink.
  • the QoS parameter includes a subset of available QoS parameters for the NR V2X link.
  • the message is to be broadcast using a same QoS metric as a unicast link between the first UE and the second UE.
  • the first UE and the second UE are to exchange QoS parameters to be used over the NR V2X link.
  • the QoS parameters are mapped to a unique source identifier (ID) and a unique destination ID for the NR V2X link.
  • one or more machine-readable media have instructions thereon that, when executed by an apparatus 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 encoding a packet for the second UE according to the QoS parameter.
  • the QoS metric includes a Proximity Services (ProSe) per-packet priority (PPPP) parameter having a value from one to 16.
  • ProSe Proximity Services
  • PPPP per-packet priority
  • the QoS metric includes a Proximity Services (ProSe) per-packet reliability (PPPP) parameter having a value from one to 16.
  • the QoS metric includes latency requirement parameter.
  • the QoS parameters are selected based on an intended use for the NR Y2X link.
  • the message is to be broadcast to a plurality of UE and the QoS metric is selected based on an operational mode for the NR V2X sidelink.
  • the QoS parameter includes a subset of available QoS parameters for the NR V2X link.
  • the message is to be broadcast using a same QoS metric as a unicast link between the first UE and the second UE.
  • the first UE and the second UE are to exchange QoS parameters to be used over the NR V2X link.
  • the QoS parameters are mapped to a unique source identifier (ID) and a unique destination ID for the NR V2X link.

Landscapes

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

Abstract

Selon la présente invention, un appareil d'un premier équipement utilisateur (UE) comprend un ou plusieurs processeurs de bande de base pour générer un message à l'intention d'un second UE en vue de la configuration d'une liaison de véhicule à tout (V2X) New Radio (NR) entre le premier UE et le second UE, le message contenant une métrique de qualité de service (QoS) pour coder une pluralité de paramètres de QoS pour la liaison V2X NR, et coder un paquet pour le second UE d'après le paramètre de QoS. L'appareil peut comprendre une mémoire pour stocker le message.
PCT/US2019/053417 2018-09-27 2019-09-27 Aspects de gestion de qos permettant à une liaison latérale nr de prendre en charge des cas d'utilisation v2x avancés WO2020069291A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201980063661.XA CN113243122A (zh) 2018-09-27 2019-09-27 NR侧链路的用以支持高级V2X用例的QoS管理方面
US17/250,920 US11997530B2 (en) 2018-09-27 2019-09-27 QoS management aspects for NR sidelink to support advanced V2X use cases
US18/668,349 US20240306032A1 (en) 2018-09-27 2024-05-20 QOS Management Aspects for NR Sidelink to Support Advanced V2X Use Cases

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862737488P 2018-09-27 2018-09-27
US62/737,488 2018-09-27

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US17/250,920 A-371-Of-International US11997530B2 (en) 2018-09-27 2019-09-27 QoS management aspects for NR sidelink to support advanced V2X use cases
US18/668,349 Continuation US20240306032A1 (en) 2018-09-27 2024-05-20 QOS Management Aspects for NR Sidelink to Support Advanced V2X Use Cases

Publications (1)

Publication Number Publication Date
WO2020069291A1 true WO2020069291A1 (fr) 2020-04-02

Family

ID=69953325

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/053417 WO2020069291A1 (fr) 2018-09-27 2019-09-27 Aspects de gestion de qos permettant à une liaison latérale nr de prendre en charge des cas d'utilisation v2x avancés

Country Status (3)

Country Link
US (2) US11997530B2 (fr)
CN (1) CN113243122A (fr)
WO (1) WO2020069291A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11006256B2 (en) * 2018-11-01 2021-05-11 Qualcomm Incorporated Sidelink link adaptation feedback
US20210337423A1 (en) * 2018-09-27 2021-10-28 Apple Inc. QOS Management Aspects for NR Sidelink to Support Advanced V2X Use Cases

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111278165B (zh) * 2019-01-11 2022-01-28 维沃移动通信有限公司 连接建立方法、终端设备及网络设备
WO2021084027A1 (fr) * 2019-10-29 2021-05-06 Telefonaktiebolaget Lm Ericsson (Publ) Procédés de traduction d'exigences d'application de commande cyber-physique en paramètres radio
US20230171315A1 (en) * 2019-11-05 2023-06-01 Qualcomm Incorporated Sensor performance indication
US11653333B2 (en) * 2020-06-26 2023-05-16 Lg Electronics Inc. Activation and deactivation for pool of resources

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017003230A1 (fr) * 2015-06-30 2017-01-05 엘지전자 주식회사 Terminal et son procédé de communication v2x dans un système de communication v2x
US20170201461A1 (en) * 2016-01-12 2017-07-13 Qualcomm Incorporated Lte based v2x communication qos and congestion mitigation
WO2017173579A1 (fr) * 2016-04-05 2017-10-12 华为技术有限公司 Procédé, dispositif et système de génération de qualité de service (qos)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11082908B2 (en) * 2018-01-19 2021-08-03 Qualcomm Incorporated Techniques for providing and/or applying quality of service in wireless communications
US10939447B2 (en) * 2018-01-22 2021-03-02 Qualcomm Incorporated Policy-based control of reliability request for eV2X
WO2020033628A1 (fr) * 2018-08-08 2020-02-13 Idac Holdings, Inc Sélection et commande de ressource de liaison latérale
CN113170487B (zh) * 2018-09-27 2024-06-04 瑞典爱立信有限公司 无线通信系统的自主模式下的副链路服务质量管理以及相关的方法和装置
US11997530B2 (en) * 2018-09-27 2024-05-28 Apple Inc. QoS management aspects for NR sidelink to support advanced V2X use cases

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017003230A1 (fr) * 2015-06-30 2017-01-05 엘지전자 주식회사 Terminal et son procédé de communication v2x dans un système de communication v2x
US20170201461A1 (en) * 2016-01-12 2017-07-13 Qualcomm Incorporated Lte based v2x communication qos and congestion mitigation
WO2017173579A1 (fr) * 2016-04-05 2017-10-12 华为技术有限公司 Procédé, dispositif et système de génération de qualité de service (qos)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3GPP; TSGSSA; Study on architecture enhancements for EPS and 5G System to support advanced V2X services (Release 16", 3GPP TR 23.786, 28 August 2018 (2018-08-28) *
FRAUNHOFER IIS ET AL.: "QoS Management for NR V2X", R1-1808540, 3GPP TSG RAN WG1 MEETING #94, 10 August 2018 (2018-08-10), Gothenburg, Sweden, XP051515918 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210337423A1 (en) * 2018-09-27 2021-10-28 Apple Inc. QOS Management Aspects for NR Sidelink to Support Advanced V2X Use Cases
US11997530B2 (en) * 2018-09-27 2024-05-28 Apple Inc. QoS management aspects for NR sidelink to support advanced V2X use cases
US11006256B2 (en) * 2018-11-01 2021-05-11 Qualcomm Incorporated Sidelink link adaptation feedback

Also Published As

Publication number Publication date
US11997530B2 (en) 2024-05-28
US20240306032A1 (en) 2024-09-12
CN113243122A (zh) 2021-08-10
US20210337423A1 (en) 2021-10-28

Similar Documents

Publication Publication Date Title
US10986548B2 (en) Enhanced conditional handover
US11240692B2 (en) Measurement design for next radio (NR) and long term evolution (LTE)
US11985626B2 (en) Paging cause determination for an inactive device in a 5G system
US11997530B2 (en) QoS management aspects for NR sidelink to support advanced V2X use cases
WO2020051152A1 (fr) Multiplexage d'informations de commande de liaison montante (uci) sur plusieurs canaux physiques partagés de liaison montante (pusch)
US20190215906A1 (en) Signaling to support reduced processing time
US20210400633A1 (en) Resource Allocation and Configuration for Broadcast and Unicast Operation Over Sidelink for NR V2X
US20210243766A1 (en) Bandwidth Part Switching Delay for Uplink Transmission
US20210400738A1 (en) Connection Management Solution to Support Unicast and Groupcast Communication Over Sidelink for EV2X
WO2018064403A1 (fr) Définition de bloc de ressources physiques (brp) avec un espacement de sous-porteuses extensible
WO2020076750A1 (fr) Transfert de contexte de dispositif mobile dans un système 5g
US20210212138A1 (en) SERVICE ANNOUNCEMENT AND DISCOVERY CONSIDERATIONS FOR SIDELINK UNICAST CONNECTION ESTABLISHMENT FOR eV2X
EP3602931B1 (fr) Informations de commande de liaison descendante pour prendre en charge une transmission de sous-trame partielle de liaison montante sur une cellule secondaire à accès assisté sous licence (laa)
WO2020041205A1 (fr) Détection de défaillance de faisceau, détection de faisceau candidat et reprise sur défaillance de faisceau en nouvelle radio
US11930443B2 (en) Enhancement for SMTC configuration for new radio
US11968568B2 (en) Performance measurements in a next generation radio access network (NG-RAN)
CN112997512B (zh) 用于nr v2x的无线电接入技术(rat)选择

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19864502

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19864502

Country of ref document: EP

Kind code of ref document: A1