[go: up one dir, main page]

WO2020092939A1 - Évitement de collision de liaison latérale, renvoi de harq et acquisition de csi - Google Patents

Évitement de collision de liaison latérale, renvoi de harq et acquisition de csi Download PDF

Info

Publication number
WO2020092939A1
WO2020092939A1 PCT/US2019/059449 US2019059449W WO2020092939A1 WO 2020092939 A1 WO2020092939 A1 WO 2020092939A1 US 2019059449 W US2019059449 W US 2019059449W WO 2020092939 A1 WO2020092939 A1 WO 2020092939A1
Authority
WO
WIPO (PCT)
Prior art keywords
sidelink
sci
transmission
resources
harq
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2019/059449
Other languages
English (en)
Inventor
Sergey PANTELEEV
Alexey Khoryaev
Mikhail Shilov
Kilian Peter Anton ROTH
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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 Corp filed Critical Intel Corp
Priority to US17/253,018 priority Critical patent/US11570757B2/en
Publication of WO2020092939A1 publication Critical patent/WO2020092939A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation
    • 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
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • 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
    • 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

  • wireless communications Some aspects relate to wireless networks including 3 GPP (Third Generation Partnership Project) networks, 3 GPP LTE (Long Term Evolution) networks, 3 GPP LTE-A (LTE Advanced) networks, and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, and 5G NR unlicensed spectrum (NR-U) networks.
  • 5G networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, and 5G NR unlicensed spectrum (NR-U) networks.
  • 5G networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, and 5G NR unlicensed spectrum (NR-U) networks.
  • 5G networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, and 5G NR unlicensed spectrum (NR-U) networks.
  • NR new radio
  • NR-U 5G NR unlicensed spectrum
  • 5G-NR networks will continue to evolve based on 3 GPP LTE-Advanced with additional potential new radio access technologies (RATs) to enrich people’s lives with seamless wireless connectivity solutions delivering fast, rich content and services.
  • RATs new radio access technologies
  • mmWave millimeter wave
  • LTE operation in the unlicensed spectrum includes (and is not limited to) the LTE operation in the unlicensed spectrum via dual connectivity (DC), or DC-based L AA, and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without requiring an“anchor” in the licensed spectrum, called MulteFire.
  • MulteFire combines the performance benefits of LTE technology with the simplicity of Wi-Fi-like deployments.
  • LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems, including NR vehicle-to-everything (V2X) systems.
  • V2X vehicle-to-everything
  • Such enhanced operations can include techniques for sidelink collision avoidance (e.g., in broadcast, unicast, and groupcast communications), HARQ feedback procedures, and CSI acquisition procedures.
  • FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.
  • FIG. 1B and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. 2 illustrates group-collision-aware channel access and resource selection, in accordance with some aspects.
  • FIG. 3 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB), an access point (AP), a wireless station (ST A), a mobile station (MS), or a user equipment (UE), in accordance with some aspects.
  • eNB evolved Node-B
  • gNB new generation Node-B
  • AP access point
  • ST A wireless station
  • MS mobile station
  • UE user equipment
  • FIG. 1A illustrates an architecture of a network in accordance with some aspects.
  • the network 140 A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • PDAs Personal Data Assistants
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • LTE and LTE-Advanced are standards for wireless
  • carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device.
  • carrier aggregation may be used where one or more component carriers operate on unlicensed
  • aspects described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (ESA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).
  • ESA Licensed Shared Access
  • SAS Spectrum Access System
  • Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFD carrier data bit vectors to the corresponding symbol resources.
  • any of the UEs 101 and 102 can comprise an
  • any of the UEs 101 and 102 can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB-IoT
  • FeNB-IoT Further Enhanced
  • 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 includes 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.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • eMTC enhanced MTC
  • FeMTC enhanced MTC
  • the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • the RAN 110 may be, for example, an Evolved Universal Mobile T elecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile T elecommunications System
  • E-UTRAN Evolved Universal Mobile T elecommunications System
  • NG RAN NextGen RAN
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 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 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 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 102 is shown to be configured to access an access point
  • connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system
  • the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the communication nodes 111 and 112 can be transmission/reception points (TRPs).
  • the RAN 110 may include one or more RAN nodes for providing macro cel Is, e.g., macro RAN node 111, 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 112.
  • macro cel Is e.g., macro RAN node 111
  • 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 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 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
  • any of the nodes 111 and/or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.
  • gNB Node-B
  • eNB evolved node-B
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113.
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1I).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 1 1 1 and 112 and MMEs 121
  • the CN 120 comprises the MMEs 121, the S-GW
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for
  • the S-GW 122 may terminate the SI interface 113 towards the
  • the S-GW 122 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 of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the EPC netwOrk 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
  • the application server 184 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 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
  • the application server 184 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 101 and 102 via the CN 120.
  • VoIP Voice-over- Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • IP-CAN IP-CAN
  • HPLMN Home PCRF
  • V-PCRF Visited PCRF
  • VPN Visited Public Land Mobile Network
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
  • the communication network 140A can be an IoT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • 5G NR 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • 5G NR 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • 5G NR licensed
  • 5G NR-U unlicensed
  • NB-IoT narrowband-IoT
  • An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120.
  • the NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
  • the core network 120 e.g., a 5G core network or 5GC
  • AMP access and mobility function
  • UPF user plane function
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces.
  • the gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
  • the NG system architecture can use reference points between various nodes as provided by 3 GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12).
  • TS Technical Specification
  • each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • MN master node
  • SN secondary node
  • FIG. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities.
  • 5GC 5G core
  • the 5G system architecture 140B includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.
  • the UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services.
  • DN data network
  • the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
  • the SMF 136 can be configured to set up and manage various sessions according to network policy.
  • the UPF 134 can be deployed in one or more configurations according to the desired service type.
  • the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system).
  • the UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
  • the 5G system architecture 140B includes an IP multimedia subsystem (IM S) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs).
  • IM S IP multimedia subsystem
  • CSCFs call session control functions
  • the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. 1B), or interrogating CSCF (I-CSCF) 166B.
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IM S connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area.
  • the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.
  • the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS).
  • the AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
  • FIG. 1B illustrates the following reference points: Nl (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SAIF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152),
  • N7 (between the SMF 136 and the PCF 148, not shown), 8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown),
  • N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown).
  • Other reference point representations not shown in FIG IE can also be used.
  • FIG. 1C illustrates a 5G system architecture 140C and a service- based representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
  • service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 5G system architecture 140C can include the following service- based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudrn 158E (a service- based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158 A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the
  • NR V2X communication systems will support a wide variety of use cases and deployment scenarios including basic safety message exchange, advanced driving applications, and extended sensor sharing. While basic safety applications may largely reuse LTE design of channel access based on sensing performed at the TX side, the advanced applications may require channel access schemes based on a combination of TX and RX based sensing to achieve higher data rates and reliability. Such new use cases may assume groupcast or unicast type of sidelink communication where the knowledge of intended message recipients may help in adapting transmit (TX) and receive (RX) behavior to select optimal resources in terms of system capacity and link performance.
  • TX transmit
  • RX receive
  • the TX-based channel sensing scheme if it is directly applied for unicast and groupcast operation, targeted to be supported by NR V2X, would substantially limit the achievable link reliability and spectrum efficiency due to the same problems of hidden node interference, in-band emissions, and near-far effects. Additionally, the intended receiver/group of receivers for unicast and groupcast may be assumed to be known due to pre-association, authorization, discovery procedures at least from a higher layer perspective. Therefore, such types of links may employ a more advanced collision avoidance scheme based on a combination of TX and RX based sensing.
  • the i ntroduction of uni cast links together with broadcast operation in the same spectrum requires considerations on seamless co-existence of both communication types. Therefore, at least introduction of unicast links into a broadcast system may not substantially degrade the performance of the broadcast system and/or performance of the unicast system in case of the mix with the broadcast system should not substantially degrade comparing to the unicast-only scenario.
  • the distributed communication mode may be designed to take into account different types of links and may employ a unified channel sensing approach and control signaling design. Techniques discussed herein relate to the following components of unicast and groupcast communication for V2V: procedures for avoiding half- duplex collisions in groupcast and unicast communication, sidelink HARQ feedback procedures, and CSI acquisition procedures.
  • the groups may either be dynamically formed (e.g., a coordinated maneuver, sensor sharing) or be relatively semi-static (e.g., platooning). Due to the fact that the group may be very dynamic, context setup for every group may impose a significant overhead. Therefore, the“connection less” groupcast communication may be more suitable for the NR V2X design assumption. Following the connection-less paradigm of groupcast
  • the resource collision for transmission and reception may be managed. For example, more than one member of a group transmitting data towards other members in the same resource may be avoided. Such collided transmissions may not only interfere at a receiver, but they may also lead to the cases where the transmitting UEs miss each other transmissions without chances for retransmission.
  • the following high-level mechanisms can be used to solve the intra-group collision issues, classified as proactive (i.e., to prevent collisions) and reactive (i.e., to resolve collisions):
  • a floor control function at higher layers can be used, which precludes simultaneous message transmissions within a UE group.
  • Group resource management there may be a group member ID management function that ensures the UEs in the group know each other’s unique group member ID so that these IDs may be unambiguously mapped to transmission resources in time domain multiplexing manner.
  • the group management functions may operate at a relatively long time scale due to higher layer exchange, a lower layer collision avoidance mechanism may be needed for the faster time scale operation.
  • the half- duplex collisions may be minimized during resource selection procedures so that time-domain resources known (from prior PSCCH/PSSCH transmissions) to be used by group members are given lower priority/weight for selection.
  • FIG. 2 illustrates group-collision-aware channel access and resource selection 200, in accordance with some aspects.
  • FIG. 2Error! Reference source not found., if there are near equally loaded resources in two different slots and one of the slots is known to be also used for group member transmission, the slot(s) without group member transmissions or with a minimized number of group member transmissions may be prioritized for selection.
  • Techniques discussed herein below relate to“reactive” half- duplex collision management type and RX side collision indication. Another option to resolve half-duplex collisions in a group is to enable UE(s) which detect multiple simultaneous transmissions towards the same group ID to send a negative acknowledgment (NACK) or to send a dedicated signal with collision announcement.
  • NACK negative acknowledgment
  • the HARQ procedures may need to be flexible enough to handle transmission of HARQ- ACK to multiple group members.
  • the RX UE may need to be able to time-division multiplex (TDM) the responses or to multiplex them in a single sidelink feedback control information (SFCI) message.
  • TDM time-division multiplex
  • SFCI sidelink feedback control information
  • the HARQ-ACK message may be associated with a group ID, and a reserved state of FIARQ-ACK codebook may indicate the NACK regardless of particular source of the transmission.
  • a special signal is designed to announce the collisions, it could be transmitted once and be associated with the group ID and time instance of collision detection. If a TX UE knows there was a collision, the retransmission may be sent with redundancy version 0 (R V0) instead of on changing the RV (e.g., to RY2) that would increase self-decodability of the ReTX.
  • R V0 redundancy version 0
  • ACK signaling from group members In case the transmitting UE knows all the group members and expects both ACK and NACK to be detected from all the members, it may detect a discontinuous transmission (DTX) in case a half-duplex collision happened. The DTX would mean one of the UEs have not detected both control and data. Therefore, the retransmission may need to be performed. Again, similar to the discussion on the dedicated collision announcement signal above, the ReTX may be sent with self-decodable RV0.
  • DTX discontinuous transmission
  • At least one proactive and at least one reactive mechanism may be designed in order to ensure high reliability requested by the NR V2X advanced use cases. Moreover, multiple proactive and multiple reactive mechanisms may be combined in order to have a multi-stage collision avoidance architecture.
  • the HARQ retransmission may be designed asynchronous in a sense that is may come in arbitrary timing relationship with the initial transmission. This may be helpful to keep flexibility in resource allocation so that the resources are selected according to common channel access procedures and avoiding any semi-statically or dynamically reserved/prohibited resources.
  • Having asynchronous retransmission it is natural that it may be scheduled by a new instance of SCI/PSCCH and linked with the previous TX by a HARQ ID.
  • Having a new instance of SCI may be straightforward to allow the change of transmission parameters and resource allocations in order to be able to adapt to changing radio environments and/or increase/decrease SE of retransmissions keeping the TBS assumption consistent between different occasions. Therefore, adaptive HARQ retransmission behavior as currently assumed in NR DL and UL may be supported for sidelink communication.
  • the adaptive and asynchronous HARQ retransmission may include anew data indicator (NDI) and HARQ process ID fields in SCI scheduling PSSCH.
  • NDI new data indicator
  • RV redundancy version
  • explicit redundancy version (RV) indication may also be used to keep the same understanding of the RV index between TX and RX UEs in cases of missed preceding transmissions.
  • TB transport block
  • a processing approach (under ideal feedback assumption) may be to use a minimum number of slots/TTIs for initial transmission and only allocate retransmission in case of NACK/DTX.
  • the principle of resource reservation may not work since there may be no information about retransmissions triggered by feedbacks if the potential retransmissions are not reserved in advance.
  • a transmitting UE should indicate/reserve retransmission resources prior to or during the initial transmission.
  • the indicated retransmission resources may be considered as occupied in the same way as blind repetitions.
  • the following different approach may be applied to retransmission resources assuming those may not be utilized in case of successful reception:
  • a UE may consider feedback based retransmission resources as having a higher priority to be selected under other equal/similar assumptions, e g., similar measurement and QoS metrics.
  • the retransmission resources may be excluded with even bigger certainty assuming ReTX is the last chance for a UE to deliver the service, and therefore it should not interfere.
  • slot aggregation may still be combined with feedback based retransmissions so that the feedback is only expected after the whole bundle, not after every repetition.
  • configuration signaling may be introduced to switch between different behaviors where the feedback based retransmissions resources are signaled or not signaled in advance.
  • the decision to reserve feedback based retransmission resources may be also based on QoS parameters and/or congestion control outcome so that more demanding/reliable service may signal retransmission resources in advance to protect those.
  • the feedback information (standalone or part of other control information, and denoted as sidelink feedback control information, or SFCI) may either be sent with fixed timing relation to the acknowledged PSSCFI or with dynamically/ semi- statically indicated timing relation.
  • dynamic (asynchronous) timing relation may allow UE(s) to perform channel access for the feedback itself or to dynamically take into account the already planned feedback resources and select the more suitable / less congested one for its own operation. That may especially be useful in a mixed scenario of different services, like unicast/groupcast and broadcast wherein the latter does not require any feedback to be sent. Under this assumption, it also needs to be decided where the feedback resource and timing are determined: at TX or RX (with possible restriction from TX).
  • the TX UE determines the feedback resources then the feedback resources may be avoided by others when there is sufficient processing time, once the SCI scheduling PSSCH is detected by the surrounding UEs.
  • this option may be suitable for groupcast HARQ if the NACK transmission is expected in the same resource from multiple PSSCH receivers.
  • the same resource may be applied by all group receivers, otherwise, multiple resource may be selected by the receiver in individual manner.
  • the RX UE determines the feedback resources, those could be selected taking into account current operation at the RX UE, for example, its own plans to transmit PSSCH and PSCCH, sensing information, etc. Moreover, this option may be combined with RX assistance information sending. As a kind of hybrid mode, the TX UE may indicate a set of preferred feedback resources and the RX UE may select one of them.
  • the HARQ feedback may not be needed, e g., for broadcast or in case unicast may suffice with higher layer feedback. In this case, it is natural to support the case when SFCI resource is not provided that effectively means no HARQ feedback requested.
  • a reserved or invalid state of SFCI resource indication may indicate that no HARQ-ACK feedback is requested from the transmitter.
  • the time-frequency resource for SFCI may be selected by the transmitting UE using channel access procedures. For example, the resources known to be used by other UEs may be avoided.
  • RSRP measured on PSCCH/PSSCH of the UE requesting the SFCI transmission may be used.
  • the receiver UE is identifiable at surrounding UEs, those may apply RSRP measured from this UE in previous procedures, or the other UEs may put RSRP on useful link to SCI so that surrounding UEs can calculate hypothetical SINR at potentially collided resource for smarter decision.
  • the feedback from RX may also be transmitted subject to one or more of the following conditions:
  • TX-RX or TX-TX collisions with other procedures may be subject to dropping rules based on quality of service (QoS) indicators and congestion control.
  • QoS indicators here are compared from the traffic requesting feedback transmission and the QoS of the other procedure in conflict, which may be either monitoring of higher priority traffic/signal or transmitting higher priority traffic/signal.
  • resource selection for SFCI may be randomized in some window so that UEs transmitting data at the same time may randomize collisions. UEs transmitting in later time should be able to avoid these resources by control channel decoding.
  • the collisions may not be under full control and may happen on every channel, although the collision probability may depend on loading conditions.
  • the situations where transmission is erroneously considered successful at TX side due to collisions in feedback channel should be minimized, since these situations may only be resolved by higher layer retransmissions at substantially larger timescale.
  • typically the first transmission should be successful in majority of cases (e.g. 90%) in order to achieve stable operation with larger SE comparing to a system w/o feedback.
  • the transmitter assigns SFCI resources, there may be no need to carry HARQ process ID or source ID in the feedback. However, considering collision probability, it may still be instrumental to the UE to know the ID of the source of the detected feedback. Moreover, if the SFCI resource is refined or determined by the RX UE, the feedback should be also associated with an ID so that TX UE understands the source of the feedback and the HARQ process.
  • HARQ-ACK feedback message content can be identified: Category 1 : HARQ-ACK bit(s) only for one or multiple transport blocks; Category 2: HARQ-ACK bit(s) and corresponding HARQ process ID(s); Category 3: HARQ-ACK bit(s) and corresponding group/destination ID(s); and Category 4: HARQ-ACK bit(s), corresponding HARQ process ID(s), and corresponding group/ destination ID(s).
  • dropping procedures may be defined.
  • a dropping rule may be defined so that the lower effective priority PSSCH acknowledgment is dropped while the higher effective priority PSSCH acknowledgment is performed.
  • the effective priority here may be mapped from the L1/L2 quality of services attributes which comprise at least priority, reliability, latency, and communication range.
  • NACK transmission may be prioritized over an acknowledgment (ACK), and the ACK is dropped.
  • the NACK may be dropped assuming it may be detected as DTX and retransmitted again.
  • NACK-only reporting is attractive in terms of system overhead, it may be inefficient for groupcast operation when a receiver does not even detect the transmission (e.g. due to half-duplex or strong interference). In order to avoid such issues, both states may be reported.
  • two different resources may be used for ACK and NACK respectively, especially when PSFCH carrying SFCI has PSCCH structure. In that case, ifNACK is detected or if no ACK is detected, the transmitter may decide to schedule retransmission.
  • the linkage between the two resources may need to be established in order to keep SCI signaling the same as for a single resource.
  • two resources may be multiplexed in the time domain (in different slots) so that there is minimized in-band emission and de- sensitivity impact when UE tries to receive both ACK and NACK.
  • the NACK resource may be placed before the ACK in order to organize retransmission as soon as possible.
  • two resources may be multiplexed in the frequency domain in the same slot. In an enhanced version, the ACK
  • the power backoff may also be a function of measured RSRP at the receiver during PSSCH or PSCCH
  • power controlled transmissions may be employed in order to minimize near-far / in-band emission / de-sensitivity effects.
  • the receiver may apply open loop power control based on the compensation of path gain to the detected source of PSCCH/PSSCH with specific P0 and alpha settings.
  • the potential payload of such a message may need to be determined.
  • the feedback message may at least carry a HARQ-ACK which is one or more bits depending on multiplexing/bundling of the feedbacks for different transport blocks and carry a UE identity.
  • the payload size may be composed of HARQ- ACK +
  • HARQ ID + UE ID which may be estimated as ⁇ [1-2] + 4 + [8-16] bit.
  • the HARQ-ACK is assumed to carry at most two transport block bits, the HARQ ID is assumed to be at most 4 bit (16 processes), and the UE ID may be in range of 8 bit (as in Rel-12 ProSe) to 16 bit (as an RNTI).
  • HARQ- ACKs from different PSSCH transmissions may be requested to be multiplexed in the same SFCI occasion that would require more payload.
  • This PSCCH format may be designed similar to Rel-l4 SCI transmission using a narrow 1-2 PRB structure spanning the full slot (excluding necessary switching gaps and reserved/unavailable symbols). With this structure, the resources for transmission may be selected following the same procedures as for shared channels.
  • This PSCCH format may be designed in a common framework with PSCCH carrying SCI. It may span 2-8 PRB and 2-3 OFDM symbols. In some aspects, it may span 1-2 PRBs and 1-2 OFDM symbols.
  • the SFCI may be carried by a physical sidelink feedback channel (PSFCH).
  • PSFCH physical sidelink feedback channel
  • the control resource set for all PSCCH formats may be either commonly configured or be separately configured. As a result, the PSCCH carrying SFCI and PSCCH carrying SCI may be monitored in the same/ overlapping resource set or in different resource sets.
  • Mode-1 the HARQ feedback on sidelink follows a common procedure with Mode-2 UEs. Therefore, sending the feedback to the TX side is necessary and thus sending the reception status directly from RX UE to gNB may be redundant. Moreover, sending reception status to gNB may be limited only to cases of same serving cell and connected mode for the RX UE leading to unjustified complicated procedures.
  • the sharing of HARQ feedback with gNB may also be unjustified.
  • potential HARQ retransmission resources should be signaled with every (re)transmission.
  • this principle may be used in Mode-l.
  • the resources for potential retransmission need to be signaled to a UE once scheduling initial transmission. This may eliminate the need for sharing HARQ feedback with gNB.
  • the TX may send SR on one or more SR configurations. Multiple configurations mapped to different LCH were already introduced in Rel-15 NR, thus it may be straightforward to reuse this mechanism.
  • PUSCH is scheduled at the same time, usual BSR may be appended to it.
  • one or more than one SR may be appended to it.
  • the configuration configured for transmission on PUCCH may be associated with request of sidelink Mode-l transmission and be also associated with sidelink LCHs.
  • the SR may be triggered not only if there is no valid BSR sent but also if there are HARQ retransmission pending at a UE.
  • Techniques discussed herein below relate to CSI acquisition, including aspects relating to resources for measurements.
  • the link adaptation based on CSI acquisition may consider the inherently mobile environment and changing interference. These considerations may substantially limit the functionality needed for CSI framework in sidelink V2V communication.
  • SL transmissions may be subject to channel access procedures. In that sense, standalone CSI-RS transmission or periodic CSI-RS transmission may violate this principle. Therefore, it may be beneficial to apply common resource allocation mechanisms to the signals for CSI acquisition.
  • CSI-RS there may be no dedicated CSI-RS introduced in sidelink and all measurements could be performed using DM-RS carried with PSCCH and/or PSSCH.
  • a scheme based on DM-RS pre-coder cycling known to the receiver may allow estimating CQI and RI with good accuracy.
  • the precoder / PMI application (alternation or cycling rule) and rank of the transmission may be indicated in SCI scheduling PSSCH.
  • the granularity of precoder application to PSSCH and DMRS also needs to be signaled.
  • Another option may require the allocation of dedicated CSI-RS signals which may also be carried together with PSCCH and/or PSSCH.
  • the CSI-RS bandwidth may be different from the PSCCH/PSSCH bandwidth in order to be able to perform wideband estimation.
  • resources for such transmission may need to be reserved in the system to avoid mismatched measurements due to collisions with other CSI-RS or other physical channels.
  • This option may also use a PSCCH to indicate the presence of CSI- RS.
  • a system and method of unicast, groupcast vehicle-to-vehicle (V2V) communication in a fifth-generation (5G) or new radio (NR) system are disclosed.
  • the method may include transmitting, by a first HE, of control and/or shared channel; transmitting, by a second UE, of feedback in response to the control and/or shared channel; and avoiding, by a UE, of half-duplex collision with other UEs in a group.
  • the half-duplex collisions within a group may be avoided by a higher layer floor control mechanisms.
  • the half-duplex collisions within a group may be avoided by a group member ID management function and its mappings to resource ID.
  • the half-duplex collision within a group may be minimized during resource selection procedures so that time resources known (from prior PSCCH/PSSCH transmission) to be used by group members are given lower priority/weight for selection.
  • the half-duplex collisions within a group may be resolved by sending NACK to the colliding UEs by other UEs detected the collision.
  • the half-duplex collision within a group may be resolved by sending a dedicated collision announcement signal by others UEs detected the collision.
  • the sidelink control information at least carries HARQ ID
  • Time-frequency resource for sidelink feedback control information is carried in SCI.
  • the SFCI resource is detected by UEs not interested in sending SFCI for this PSSCH but interested in avoiding to use this resource for its own operations.
  • the SFCI resource is determined by the receiving UE in a window known to the transmitting UE.
  • the following categories of HARQ feedback payload may be used to send feedback: Category 1 : HARQ-ACK bit(s) only for one or multiple transport blocks; Category 2: HARQ-ACK bit(s) and corresponding HARQ process ID(s); Category 3 :
  • Feedback dropping and multiplexing may be defined in case of multiple triggered feedbacks at the same time resource.
  • the dropping rule may be defined so that the lower effective priority PSSCH acknowledgment is dropped while the higher effective priority PSSCH acknowledgment is performed.
  • a short PSCCH format may be defined to convey SFCI, where it comprises 2-8 PRB in frequency domain and 2-3 symbols in time domain.
  • a long PSCCH format may be defined to convey SFCI, wherein it comprises 1-2 PRB in frequency domain and up to 14 symbols in time domain excluding necessary switching gaps and reserved/ unavailable symbols.
  • the control resource set for all PSCCH formats may be either commonly configured or be separately configured.
  • the PSCCH carrying SFCI and PSCCH carrying SCI may be monitored in the same/ overl apping resource set or in different resource sets.
  • DMRS of PSSCH, PSSCH precoder cycling rule, and rank of PSSCH transmission is signaled in SCI.
  • a transmitting UE may indicate/reserve retransmission resources prior to or during the initial transmission.
  • a HE may consider feedback based retransmission resources as having a higher priority to be selected under other equal/similar assumptions, e.g. similar measurement and QoS metrics.
  • the retransmission resources may be excluded with even bigger certainty- assuming ReTX is the last chance for a UE to deliver the service, and therefore it may not interfere.
  • a UE may consider feedback based retransmission resources as occupied until other indication overriding this assumption is received, e.g. SFCI.
  • SFCI resource is added to the candidate resource set, RSRP measured on PSCCH/PSSCH of the UE requesting the SFCI transmission may be used.
  • Whether to perform SFCI/PSFCH transmission may be subject to dropping rules based on QoS indicators and congestion control by comparing QoS indicators from the traffic requesting feedback transmi ssion and the QoS of the other procedure in conflict, which may be either monitoring of higher priority traffic/signal or transmitting higher priority traffic/signal.
  • two different resources may be used for ACK and NACK respectively.
  • the two resources may be multiplexed in time domain (in different slots) so that there is minimized in-band emission and de- sensitivity impact when UE tries to receive both ACK and NACK.
  • the NACK resource may be placed before the ACK in order to organize retransmission as soon as possible.
  • the two resources may be multiplexed in frequency domain in the same slot.
  • the ACK transmission may be performed with less power so that NACK resource is less masked by nearby high-power responses.
  • resources for potential retransmissions need to be signaled to a HE once scheduling initial transmission.
  • One or more than one SR configuration configured for transmission on PUCCH may be associated with request of sidelink Mode-1 transmission and be also associated with sidelink LCHs.
  • the SR may be triggered not only if there is no valid BSR sent but also if there are HARQ retransmission pending at a UE.
  • FIG. 3 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a next generation Node-B (gNB), an access point (AP), a wireless station (ST A), a mobile station (MS), or a user equipment (UE), in accordance with some aspects and to perform one or more of the techniques disclosed herein.
  • the communication device 300 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.
  • Circuitry e.g., processing circuitry
  • circuitry is a collection of circuits implemented in tangible entities of the device 300 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating.
  • the hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired).
  • the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine-readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation.
  • the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa.
  • the instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation.
  • the machine-readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating.
  • any of the physical components may be used in more than one member of more than one circuitry.
  • execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the device 300 follow.
  • the device 300 may operate as a standalone device or may be connected (e.g., networked) to other devices.
  • the communication device 300 may operate in the capacity of a server communication device, a client communication device, or both in server- client network environments.
  • the communication device 300 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the communication device 300 may be a LIE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smartphone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device. Further, while only a single
  • communication device is illustrated, the term "communication device” shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.
  • cloud computing software as a service
  • SaaS software as a service
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client or server computer
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • firmware or software e.g., instructions, an application portion, or an application
  • the software may reside on a communication device-readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using the software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • the software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Communication device 300 may include a hardware processor 302 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 304, a static memory 306, and mass storage 307 (e.g., hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., bus) 308.
  • a hardware processor 302 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • main memory 304 e.g., a main memory 304
  • static memory 306 e.g., hard drive, tape drive, flash storage, or other block or storage devices
  • the communication device 300 may further include a display device 310, an alphanumeric input device 312 (e.g., a keyboard), and a user interface (UI) navigation device 314 (e.g., a mouse).
  • UI user interface
  • the display device 310, input device 312 and UI navigation device 314 may be a touchscreen display.
  • the communication device 300 may additionally include a signal generation device 318 (e.g., a speaker), a network interface device 320, and one or more sensors 321, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor.
  • GPS global positioning system
  • the communication device 300 may include an output controller 328, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 307 may include a communication device- readable medium 322, on which is stored one or more sets of data structures or instructions 324 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • registers of the processor 302, the main memory 304, the static memory 306, and/or the mass storage 307 may be, or include (completely or at least partially), the device- readable medium 322, on which is stored the one or more sets of data structures or instructions 324, embodying or utilized by any one or more of the techniques or functions described herein.
  • one or any combination of the hardware processor 302, the main memory 304, the static memory 306, or the mass storage 316 may constitute the device-readable medium 322.
  • communication device-readable medium 322 is illustrated as a single medium, the term "communication device-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 324.
  • the term "communication device-readable medium” is inclusive of the terms“machine-readable medium” or“computer-readable medium”, and may include any medium that is capable of storing, encoding, or carrying instructions (e.g., instructions 324) for execution by the communication device 300 and that cause the communication device 300 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting communication device-readable medium examples may include solid-state memories and optical and magnetic media.
  • communication device-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g.,
  • communication device-readable media may include non-transitory
  • communication device-readable media may include communication device-readable media that is not a transitory propagating signal.
  • the instructions 324 may further be transmitted or received over a communications network 326 using a transmission medium via the network interface device 320 utilizing any one of a number of transfer protocols.
  • the network interface device 320 may include one or more physical jacks (e g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 326.
  • the network interface device 320 may include a plurality of antennas to wirelessly communicate using at least one of single-input-multiple-output (SIMO), MIMO, or multiple-input- single-output (MI SO) techniques.
  • SIMO single-input-multiple-output
  • MI SO multiple-input- single-output
  • the network interface device 320 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 300, and includes digital or analog communications signals or another intangible medium to facilitate
  • a transmission medium in the context of this disclosure is a device-readable medium.

Landscapes

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

Abstract

Un appareil d'un UE comprend des circuits de traitement couplés à une mémoire. Pour configurer l'UE pour une communication de liaison latérale NR V2X, les circuits de traitement sont conçus pour décoder des SCI reçues en provenance d'un second UE via un PSCCH, les SCI indiquant des ressources de liaison latérale dans un groupe de ressources de liaison latérale réservé par le second UE. Un ensemble de ressources de liaison latérale candidates est déterminé pour une réservation par l'UE dans le groupe de ressources de liaison latérale. L'ensemble est divisé en de multiples créneaux temporels et sous-canaux de fréquence et ne se recouvre pas dans le temps avec les ressources de liaison latérale réservées par le second UE. Des secondes SCI sont codées aux fins de transmission via le PSCCH, les secondes SCI indiquant une pluralité de ressources de liaison latérale parmi l'ensemble de ressources de liaison latérale candidates. Un PSSCH est codé aux fins de transmission, le PSSCH est codé pour comprendre un bloc de transport mappé à la pluralité de ressources de liaison latérale.
PCT/US2019/059449 2018-11-02 2019-11-01 Évitement de collision de liaison latérale, renvoi de harq et acquisition de csi Ceased WO2020092939A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/253,018 US11570757B2 (en) 2018-11-02 2019-11-01 Sidelink collision avoidance, HARQ feedback, and CSI acquisition

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201862754840P 2018-11-02 2018-11-02
US62/754,840 2018-11-02
US201962791527P 2019-01-11 2019-01-11
US62/791,527 2019-01-11

Publications (1)

Publication Number Publication Date
WO2020092939A1 true WO2020092939A1 (fr) 2020-05-07

Family

ID=70462164

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/059449 Ceased WO2020092939A1 (fr) 2018-11-02 2019-11-01 Évitement de collision de liaison latérale, renvoi de harq et acquisition de csi

Country Status (2)

Country Link
US (1) US11570757B2 (fr)
WO (1) WO2020092939A1 (fr)

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112673697A (zh) * 2020-12-14 2021-04-16 北京小米移动软件有限公司 Drx配置方法及装置、通信设备和存储介质
WO2021237663A1 (fr) * 2020-05-29 2021-12-02 Lenovo (Beijing) Limited Procédés et appareil destinés à une attribution de ressources sur la base d'informations d'assistance de récepteur
WO2021255271A1 (fr) * 2020-06-19 2021-12-23 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Sélection de ressource autonome économe en énergie pour une communication de liaison latérale nr v2x
WO2022026404A1 (fr) * 2020-07-31 2022-02-03 Qualcomm Incorporated Attribution de ressources pour une indication de collision dans une communication de liaison latérale
CN114071721A (zh) * 2020-07-29 2022-02-18 维沃移动通信有限公司 副链路反馈资源配置方法、装置及设备
WO2022073021A1 (fr) * 2020-09-30 2022-04-07 Qualcomm Incorporated Amélioration de la fiabilité de sl par semi-duplex et détection de collision
WO2022073199A1 (fr) * 2020-10-09 2022-04-14 Mediatek Inc. Améliorations d'attribution de ressources sl
WO2022086696A1 (fr) * 2020-10-23 2022-04-28 Qualcomm Incorporated Techniques d'attribution de ressources pour des transmissions de liaison latérale, et sélection dynamique entre des techniques d'attribution de ressources en fonction de la fiabilité de communications de liaison latérale
WO2022082587A1 (fr) * 2020-10-22 2022-04-28 Apple Inc. Gestion de collisions de ressources de liaison latérale et attribution de ressources par coordination d'équipements d'utilisateur
WO2022115333A1 (fr) * 2020-11-24 2022-06-02 Qualcomm Incorporated Détection de collision d'attribution de véhicule à tout cellulaire
WO2022236686A1 (fr) * 2021-05-11 2022-11-17 Qualcomm Incorporated Présignalisation de collision dans des systèmes de communication sans fil
CN115552835A (zh) * 2020-05-15 2022-12-30 高通股份有限公司 对侧链路资源池中的附加带宽的利用
CN115769629A (zh) * 2020-08-04 2023-03-07 富士通株式会社 终端装置、无线通信系统以及重发控制方法
CN115804214A (zh) * 2020-08-05 2023-03-14 英特尔公司 用于nr侧链路通信的功率节省
CN116347601A (zh) * 2020-08-25 2023-06-27 Oppo广东移动通信有限公司 无线通信的方法和终端设备
WO2023130446A1 (fr) * 2022-01-10 2023-07-13 Zte Corporation Procédés et systèmes pour des communications de dispositif à dispositif
CN116527211A (zh) * 2021-01-14 2023-08-01 北京小米移动软件有限公司 通信方法、用户设备及存储介质
WO2023212489A1 (fr) * 2022-04-26 2023-11-02 Qualcomm Incorporated Sélection de version de redondance dans une liaison latérale
EP4236539A4 (fr) * 2020-11-24 2024-02-28 Huawei Technologies Co., Ltd. Procédé et appareil de communication, puce, support de stockage et produit-programme
US12185279B2 (en) 2020-10-23 2024-12-31 Qualcomm Incorporated Receiver assisted sidelink resource allocation using an adaptive threshold

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111132329B (zh) * 2018-11-02 2022-09-16 维沃移动通信有限公司 一种资源指示方法、设备及系统
US11956782B2 (en) * 2018-11-02 2024-04-09 Apple Inc. Resource allocation and processing behaviors for NR V2X sidelink communications
CN115765943B (zh) * 2018-12-13 2024-08-13 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
US11451360B2 (en) * 2019-01-10 2022-09-20 Qualcomm Incorporated Priority-based feedback triggering
WO2020146893A1 (fr) * 2019-01-11 2020-07-16 Apple Inc. Procédures de couche physique de liaison latérale pour l'évitement de collision, la rétroaction de harq et l'acquisition de csi
CN111436151B (zh) * 2019-01-11 2021-10-29 中国移动通信有限公司研究院 控制信息发送方法、接收方法、终端及网络侧设备
US20200280981A1 (en) * 2019-02-28 2020-09-03 Samsung Electronics Co., Ltd. Method and apparatus for managing resource pool in wireless communication system
WO2020220290A1 (fr) * 2019-04-30 2020-11-05 富士通株式会社 Procédé et appareil d'envoi et de réception de données de liaison latérale
CN117596687A (zh) * 2019-05-09 2024-02-23 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
US11483802B2 (en) * 2019-07-18 2022-10-25 Ofinno, Llc Hybrid automatic repeat request feedback in radio systems
CN111817824B (zh) * 2019-07-24 2022-05-31 维沃移动通信有限公司 一种信息传输方法、终端设备和控制节点
CN111836304B (zh) * 2019-08-09 2023-10-13 维沃移动通信有限公司 一种信息传输方法及终端
EP4192053B1 (fr) * 2019-08-16 2025-11-26 Hyundai Motor Company Procédé de transmission de données de liaison montante dans un système de communication
US11122554B2 (en) * 2019-08-19 2021-09-14 Lenovo (Singapore) Pte. Ltd. Using a configured feedback resource for feedback
US11888628B2 (en) * 2019-09-26 2024-01-30 Qualcomm Incorporated Configurable transmission timeline for physical sidelink feedback channel
KR20240028569A (ko) * 2019-10-03 2024-03-05 오피노 엘엘씨 피드백 채널의 무선 리소스 맵핑
CN115834011B (zh) * 2019-11-06 2025-10-31 邦克山科技有限责任公司 一种被用于无线通信的节点中的方法和装置
CN114762385A (zh) * 2019-12-13 2022-07-15 索尼集团公司 信息处理设备、信息处理方法、终端设备、基站设备及程序
CN114846755A (zh) * 2019-12-31 2022-08-02 华为技术有限公司 一种数据的反馈方法及装置
US11457469B2 (en) * 2020-01-07 2022-09-27 Samsung Electronics Co., Ltd. Pre-indication of sidelink transmission intention
CN113259913A (zh) * 2020-02-11 2021-08-13 华硕电脑股份有限公司 无线通信系统中装置到装置侧链路传送调度的方法和设备
CN115066850B (zh) * 2020-02-14 2024-08-06 高通股份有限公司 用于nr v2x周期性调度的保留周期性
US11647517B2 (en) * 2020-02-24 2023-05-09 Qualcomm Incorporated Adaptive sensing based on number of retransmissions
CN115004608B (zh) * 2020-05-15 2024-11-29 中兴通讯股份有限公司 用于多播传输的系统和方法
KR20230040960A (ko) * 2020-07-22 2023-03-23 엘지전자 주식회사 V2x에서 차량에게 자원을 할당하는 방법 및 장치
US12075287B2 (en) * 2020-09-18 2024-08-27 Qualcomm Incorporated User equipment behavior with sidelink preemption indication
US11683727B2 (en) * 2021-03-31 2023-06-20 Qualcomm Incorporated Coexistence of redcap and non-redcap UEs in SL
WO2022236696A1 (fr) * 2021-05-11 2022-11-17 Oppo广东移动通信有限公司 Procédé de communication sans fil et dispositif terminal
CN115580383A (zh) * 2021-06-21 2023-01-06 华为技术有限公司 通信方法及装置
US12185363B2 (en) * 2021-07-08 2024-12-31 Qualcomm Incorporated Sidelink prioritization
US12245233B2 (en) 2021-07-08 2025-03-04 Qualcomm Incorporated Sidelink cancellation with resumption
US12096448B2 (en) 2021-07-08 2024-09-17 Qualcomm Incorporated Sidelink cancellation indication
CN115706628A (zh) * 2021-08-02 2023-02-17 夏普株式会社 由用户设备执行的方法以及用户设备
US20240284481A1 (en) * 2021-08-05 2024-08-22 Qualcomm Incorporated Signaling resource information for sidelink reliability
WO2023028805A1 (fr) * 2021-08-31 2023-03-09 Qualcomm Incorporated Ressources réservées pour des informations de commande de liaison latérale
US12155492B2 (en) * 2022-03-17 2024-11-26 Qualcomm Incorporated Out-band physical sidelink feedback channel (PSFCH) resources for sidelink unlicensed spectrum
US20250351157A1 (en) * 2022-04-07 2025-11-13 Nokia Technologies Oy Indicating radio resources of sidelink transmission
WO2024019522A1 (fr) * 2022-07-19 2024-01-25 주식회사 윌러스표준기술연구소 Procédé, dispositif, et système de transmission et de réception de données dans un système de communication sans fil
CN118042628A (zh) * 2022-11-04 2024-05-14 华为技术有限公司 一种资源选择方法及装置
WO2024207341A1 (fr) * 2023-04-06 2024-10-10 Nec Corporation Dispositif et procédé de communication
WO2025091452A1 (fr) * 2023-11-03 2025-05-08 Qualcomm Incorporated Techniques pour de multiples occasions de canal de rétroaction de liaison latérale physique (psfch) pour psfch avec indication de conflit

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170280469A1 (en) * 2014-11-25 2017-09-28 Lg Electronics Inc. Method for assisting device-to-device communication in wireless communication system supporting device-to-device communication and device therefor
WO2018039079A1 (fr) * 2016-08-25 2018-03-01 Qualcomm Incorporated Sélection autonome de ressources pour multiples transmissions dans des communications de dispositif à dispositif
WO2018143786A1 (fr) * 2017-02-06 2018-08-09 엘지전자(주) Procédé d'exécution d'une communication de liaison latérale dans un système de communications sans fil, et dispositif associé

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3335495B1 (fr) * 2015-08-12 2020-07-29 Intel Corporation Accès à une ressource dans une communication de dispositif à dispositif
CA3066646C (fr) * 2017-08-04 2022-07-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procede d'ordonnancement de donnees et dispositif associe
EP3777382B1 (fr) * 2018-04-11 2022-07-13 Telefonaktiebolaget LM Ericsson (publ) Technique de transmissions de rétroaction en liaison latérale
WO2019201442A1 (fr) * 2018-04-19 2019-10-24 Huawei Technologies Co., Ltd. Dispositif d'émission et dispositif de réception pour communications sans fil
EP4518520A3 (fr) * 2018-08-09 2025-06-25 Koninklijke Philips N.V. Réattribution et réservation de ressources pour des communications à haute priorité et une rétroaction de qos

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170280469A1 (en) * 2014-11-25 2017-09-28 Lg Electronics Inc. Method for assisting device-to-device communication in wireless communication system supporting device-to-device communication and device therefor
WO2018039079A1 (fr) * 2016-08-25 2018-03-01 Qualcomm Incorporated Sélection autonome de ressources pour multiples transmissions dans des communications de dispositif à dispositif
WO2018143786A1 (fr) * 2017-02-06 2018-08-09 엘지전자(주) Procédé d'exécution d'une communication de liaison latérale dans un système de communications sans fil, et dispositif associé

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "Sidelink PHY structure and procedure for NR V2X", 3GPP DRAFT; R1-1810138, vol. RAN WG1, 29 September 2018 (2018-09-29), Chengdu, China, pages 1 - 15, XP051517553 *
LG ELECTRONICS: "Updated feature lead summary for agenda item 7.2.4.1.2 Physical layer", 3GPP DRAFT; R1-1812017 SUMMARY OF PHY FORMAT AND PROCEDURE, vol. RAN WG1, 11 October 2018 (2018-10-11), Chengdu, China, pages 1 - 11, XP051519340 *

Cited By (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115552835A (zh) * 2020-05-15 2022-12-30 高通股份有限公司 对侧链路资源池中的附加带宽的利用
WO2021237663A1 (fr) * 2020-05-29 2021-12-02 Lenovo (Beijing) Limited Procédés et appareil destinés à une attribution de ressources sur la base d'informations d'assistance de récepteur
WO2021255271A1 (fr) * 2020-06-19 2021-12-23 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Sélection de ressource autonome économe en énergie pour une communication de liaison latérale nr v2x
CN114071721A (zh) * 2020-07-29 2022-02-18 维沃移动通信有限公司 副链路反馈资源配置方法、装置及设备
WO2022026404A1 (fr) * 2020-07-31 2022-02-03 Qualcomm Incorporated Attribution de ressources pour une indication de collision dans une communication de liaison latérale
CN116326151A (zh) * 2020-07-31 2023-06-23 高通股份有限公司 用于侧链路通信的具有冲突指示的资源分配
CN115769629A (zh) * 2020-08-04 2023-03-07 富士通株式会社 终端装置、无线通信系统以及重发控制方法
CN115804214A (zh) * 2020-08-05 2023-03-14 英特尔公司 用于nr侧链路通信的功率节省
US12490287B2 (en) 2020-08-25 2025-12-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication method and terminal device
CN116347601A (zh) * 2020-08-25 2023-06-27 Oppo广东移动通信有限公司 无线通信的方法和终端设备
US12267868B2 (en) 2020-09-30 2025-04-01 Qualcomm Incorporated SL reliability enhancement by half duplex and collision detection
CN116235616A (zh) * 2020-09-30 2023-06-06 高通股份有限公司 通过半双工和冲突检测的sl可靠性增强
WO2022073021A1 (fr) * 2020-09-30 2022-04-07 Qualcomm Incorporated Amélioration de la fiabilité de sl par semi-duplex et détection de collision
WO2022073199A1 (fr) * 2020-10-09 2022-04-14 Mediatek Inc. Améliorations d'attribution de ressources sl
WO2022082587A1 (fr) * 2020-10-22 2022-04-28 Apple Inc. Gestion de collisions de ressources de liaison latérale et attribution de ressources par coordination d'équipements d'utilisateur
WO2022086696A1 (fr) * 2020-10-23 2022-04-28 Qualcomm Incorporated Techniques d'attribution de ressources pour des transmissions de liaison latérale, et sélection dynamique entre des techniques d'attribution de ressources en fonction de la fiabilité de communications de liaison latérale
US12335947B2 (en) 2020-10-23 2025-06-17 Qualcomm Incorporated Resource allocation techniques for sidelink transmissions, and dynamic selection between resource allocation techniques based on sidelink communication reliability
US12185279B2 (en) 2020-10-23 2024-12-31 Qualcomm Incorporated Receiver assisted sidelink resource allocation using an adaptive threshold
EP4236539A4 (fr) * 2020-11-24 2024-02-28 Huawei Technologies Co., Ltd. Procédé et appareil de communication, puce, support de stockage et produit-programme
US12063687B2 (en) 2020-11-24 2024-08-13 Qualcomm Incorporated Cellular vehicle-to-everything allocation collision detection
WO2022115333A1 (fr) * 2020-11-24 2022-06-02 Qualcomm Incorporated Détection de collision d'attribution de véhicule à tout cellulaire
CN112673697A (zh) * 2020-12-14 2021-04-16 北京小米移动软件有限公司 Drx配置方法及装置、通信设备和存储介质
CN112673697B (zh) * 2020-12-14 2023-06-06 北京小米移动软件有限公司 Drx配置方法及装置、通信设备和存储介质
CN116527211A (zh) * 2021-01-14 2023-08-01 北京小米移动软件有限公司 通信方法、用户设备及存储介质
EP4280497A4 (fr) * 2021-01-14 2024-03-06 Beijing Xiaomi Mobile Software Co., Ltd. Procédé de communication, appareil de communication et support de stockage
WO2022236686A1 (fr) * 2021-05-11 2022-11-17 Qualcomm Incorporated Présignalisation de collision dans des systèmes de communication sans fil
WO2023130446A1 (fr) * 2022-01-10 2023-07-13 Zte Corporation Procédés et systèmes pour des communications de dispositif à dispositif
WO2023212489A1 (fr) * 2022-04-26 2023-11-02 Qualcomm Incorporated Sélection de version de redondance dans une liaison latérale

Also Published As

Publication number Publication date
US11570757B2 (en) 2023-01-31
US20210127364A1 (en) 2021-04-29

Similar Documents

Publication Publication Date Title
US11570757B2 (en) Sidelink collision avoidance, HARQ feedback, and CSI acquisition
US11825560B2 (en) Physical sidelink feedback channel (PSFCH) transmission and reception in new radio (NR) systems
US11563545B2 (en) HARQ-ACK transmission and retransmission in wireless communication systems
US12495422B2 (en) Resource allocation and processing behaviors for NR V2X sidelink communications
US12089068B2 (en) TCI and QCL configuration in 5G networks
US12150213B2 (en) Reference signal and control information processing in 5G-NR wireless systems
US20200029340A1 (en) Method and apparatus for nr v2x resource selection
TWI628940B (zh) 支援具有不同上行鏈路／下行鏈路分時雙工配置之頻帶間載波聚合之系統及方法
KR20210068430A (ko) V2x에서 harq를 지원하기 위한 방법, 장치 및 시스템
WO2020041269A1 (fr) Gestion de collision pour transmissions d'informations de commande de liaison montante
US11877268B2 (en) Streamlining protocol layers processing, and slotless operation
WO2022212500A1 (fr) Ressources de transmission de liaison latérale pour un retour de coordination inter-ue
US20200374860A1 (en) Physical sidelink control channel (pscch) signaling for multiple transmission time interval (tti) transmissions
JP7775545B2 (ja) Ｄｃｉトリガによるｈａｒｑ－ａｃｋコードブック再送信
JP7781903B2 (ja) 異なる物理層優先度を有するアップリンク制御情報（ｕｃｉ）の多重化
US20240405927A1 (en) Harq-ack based pdsch transmission scheduled by multiple dl assignments
US20240260027A1 (en) Uplink control information (uci) multiplexing for multi-transmission-reception point (m-trp) operations
EP4275310A1 (fr) Harq-ack avec groupage dans le domaine temporel pour pdsch ordonnancés par dci à multi-tti
CN117480845A (zh) 用于多发送接收点（m-trp）操作的上行链路控制信息（uci）复用

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

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

Country of ref document: EP

Kind code of ref document: A1