Apparatuses, systems, methods, and computer-readable media for performing control to handle inter-UE prioritization for NR V2X

Abstract

The present disclosure relates to apparatuses, systems, methods, and computer readable media for performing control to handle inter-UE prioritization for NR V2X. Some embodiments relate to an electronic device configured to schedule transmission of data to at least one other electronic device via a sidelink resource in a wireless communication network; identify another transmission preemption in which the scheduled transmission of the data occurs within at least a portion of the sidelink resource; and control the transmission of the data to the at least one other electronic device based on the identification.

Description

[0001] This application is a divisional application of patent application 202080025014.2, filed on February 5, 2020, entitled "Apparatus, System, Method and Computer-readable Medium for Performing Control to Process NR V2X Inter-UE Priority Ordering".

[0002] Cross-reference to related applications

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 825,374, filed on March 28, 2019, which is incorporated herein by reference in its entirety. Technical Field

[0004] This disclosure generally relates to wireless communications, and more particularly to wireless communication systems, apparatus, methods, and computer-readable media having computer-executable instructions for performing control to handle: inter-UE collisions between dynamically scheduled or configured sidelink transmissions and dynamically scheduled very low latency or high priority downlink (DL) or uplink (UL) transmissions, or inter-UE collisions between dynamically scheduled or configured sidelink transmissions and dynamically scheduled very low latency or high priority sidelink transmissions, or inter-UE prioritization in New Radio (NR) Vehicle-to-Everything (V2X) communication. Background Technology

[0005] The “Background Art” description provided herein is intended to generally present the background of this disclosure. To the extent described in this Background Art section, the work of the currently named inventors, and aspects of the description that may not constitute prior art at the time of filing this application, are neither expressly nor implicitly acknowledged as prior art to this invention.

[0006] For New Radio (NR) Vehicle-to-Everything (V2X) Mode 1 shared carrier scenarios, the gNB can allocate sidelink transmissions on a shared carrier with downlink (DL) and / or uplink (UL) transmissions on the Uu interface using dynamic scheduling, Type 1 Configuration Grant (CG), or Type 2 Configuration Grant (CG). For example, the gNB can schedule very low latency or high priority DL data transmissions on the Uu interface for a UE, which may overlap with a sidelink transmission already scheduled or configured for another UE. In this case, both transmissions can degrade or even fail. Therefore, this paper discloses mechanisms to handle inter-UE conflicts between dynamically scheduled or configured sidelink transmissions and dynamically scheduled very low latency or high priority DL or UL transmissions.

[0007] For NR V2X Mode 1, the gNB can allocate sidelink transmissions using dynamic scheduling, Type 1 configuration granting, or Type 2 configuration granting. For example, the gNB can schedule very low-latency or high-priority data transmissions on a sidelink for a UE, which may overlap with sidelink transmissions already scheduled or configured for another UE. In this case, both transmissions may degrade or even fail. Therefore, this paper discloses mechanisms to handle inter-UE conflicts between dynamically scheduled or configured sidelink transmissions and dynamically scheduled very low-latency or high-priority sidelink transmissions. Summary of the Invention

[0008] This disclosure generally relates to wireless communications, and more particularly to wireless communication systems, apparatus, methods, and computer-readable media having computer-executable instructions for performing control to process: user equipment (UE) conflicts between dynamically scheduled or configured sidelink transmissions and dynamically scheduled very low latency or high priority downlink (DL) or uplink (UL) transmissions, or UE conflicts between dynamically scheduled or configured sidelink transmissions and dynamically scheduled very low latency or high priority sidelink transmissions, or UE priority ordering in New Radio (NR) Vehicle-to-Everything (V2X).

[0009] The Summary Section is provided to introduce, in a simplified form, some concepts further described in the Detailed Description Section. The Summary Section is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to addressing any or all of the deficiencies mentioned in any part of this disclosure. Attached Figure Description

[0010] The scope of this disclosure can be better understood by reading in conjunction with the following detailed description of exemplary embodiments, in which:

[0011] Figure 1A This is a system diagram showing an example 3GPP architecture;

[0012] Figure 1B This is a system diagram of an example device or apparatus configured for wireless communication;

[0013] Figure 1C This is a system diagram illustrating an example of a Radio Access Network (RAN) architecture and a core network architecture;

[0014] Figure 1D This is a system diagram illustrating examples of Radio Access Network (RAN) architecture and core network architecture;

[0015] Figure 1EThis is a system diagram illustrating an example of a Radio Access Network (RAN) architecture and a core network architecture;

[0016] Figure 1F This is a system diagram illustrating an example of a computing system used in a communication network;

[0017] Figure 1G This is a system diagram showing an example 3GPP architecture;

[0018] Figure 2 This illustrates a sidelink transmission preempted by a dynamically scheduled Uu transmission, according to an exemplary embodiment.

[0019] Figure 3 The example illustrates a UE detecting an explicit preemption indication and performing a retransmission according to an exemplary embodiment.

[0020] Figure 4 The diagram illustrates the signaling for UE detection of joint ground indication of explicit preemption indication and retransmission scheduling according to an exemplary embodiment;

[0021] Figure 5 This illustrates a UE detecting an implicit preemption indication via retransmission scheduling DCI according to an exemplary embodiment.

[0022] Figure 6 A method for detecting preemption of Uu transmission and retransmitting broadcast signals on a side link, according to an exemplary embodiment, is shown.

[0023] Figure 7 This illustrates a joint indication for reducing power and retransmission for a preempted side link, according to an exemplary embodiment.

[0024] Figure 8 Separate instructions for reducing power and retransmission for preempted sidelink transmissions are shown according to an exemplary embodiment.

[0025] Figure 9 A method for detecting a power reduction indicator according to an exemplary embodiment is shown, the power reduction indicator being used for a broadcast sidelink UE that has an inter-UE conflict with a scheduled Uu transmission;

[0026] Figure 10 A method for detecting a cancellation indication according to an exemplary embodiment is shown, the cancellation indication being used for a broadcast-side link UE that has an inter-UE conflict with a scheduled Uu transmission;

[0027] Figure 11 A method according to an exemplary embodiment is shown, which is used to perform a UE detection of preemption by a unicast sidelink UE, the unicast sidelink UE having an inter-UE conflict with a scheduled Uu transmission;

[0028] Figure 12 A process according to an exemplary embodiment is shown, which is used to detect preemption of a unicast sidelink UE by a receiving UE, the unicast sidelink UE having an inter-UE conflict with a scheduled Uu transmission;

[0029] Figure 13 A method according to an exemplary embodiment is shown, which is used to detect a power reduction indicator of a unicast sidelink UE that is transmitting and has inter-UE conflict with a scheduled Uu transmission;

[0030] Figure 14 A process according to an exemplary embodiment is shown, which is used to detect a power reduction indicator of a unicast sidelink UE that is receiving a UE and has an inter-UE conflict with a scheduled Uu transmission.

[0031] Figure 15 A method according to an exemplary embodiment is shown, which is used to detect the cancellation indication of a unicast sidelink UE that is transmitting a Uu transmission that has an inter-UE conflict with the scheduled Uu transmission;

[0032] Figure 16 A process according to an exemplary embodiment is shown, which is used to receive a UE detection cancellation indication of a unicast sidelink UE, the unicast sidelink UE having an inter-UE conflict with the scheduled Uu transmission;

[0033] Figure 17 A method according to an exemplary embodiment is shown, which is used to perform preemption of a multicast sidelink UE for transmission, the multicast sidelink UE having inter-UE conflict with a scheduled Uu transmission;

[0034] Figure 18 A process according to an exemplary embodiment is shown, which is used to perform a receiving UE detection of preemption by a multicast sidelink UE, which has inter-UE conflict with a scheduled Uu transmission;

[0035] Figure 19 A method according to an exemplary embodiment is shown, which is used to detect a power reduction indicator of a multicast sidelink UE that is transmitting a multicast sidelink UE that has an inter-UE conflict with a scheduled Uu transmission;

[0036] Figure 20A process according to an exemplary embodiment is shown, which is used to detect a power reduction indicator of a multicast sidelink UE that is receiving a multicast sidelink UE and has inter-UE conflict with a scheduled Uu transmission;

[0037] Figure 21 A process according to an exemplary embodiment is shown, which is used to perform a cancellation indication of a multicast sidelink UE for transmission, the multicast sidelink UE having an inter-UE conflict with the scheduled Uu transmission;

[0038] Figure 22 A process according to an exemplary embodiment is shown, which is used to receive a UE detection cancellation indication of a multicast sidelink UE, which has an inter-UE conflict with the scheduled Uu transmission;

[0039] Figure 23 The procedure for a cancellation indicator for a UE with a configured authorized side link that conflicts with the scheduled Uu transmission is illustrated.

[0040] Figure 24 The procedure for detecting a cancellation indicator for a UE with a configured authorized side link that conflicts with the scheduled Uu transmission is illustrated.

[0041] Figure 25 An alternative procedure for detecting preemption of a UE with a configured authorized side link that has an inter-UE conflict with the scheduled Uu transmission is shown.

[0042] Figure 26 An example of a sidelink transmission with 3 repetitions scheduled by a gNB in ​​NR V2X mode 1 is shown.

[0043] Figure 27 An example of a sidelink transmission being preempted during a repetition is shown;

[0044] Figure 28 An example of sidelink transmission with simultaneous transmission of the first-stage SCI and the second-stage SCI is shown.

[0045] Figure 29 This illustrates the inter-UE conflict between two dynamically scheduled sidelink transmissions;

[0046] Figure 30 This illustrates inter-UE conflicts between dynamically scheduled sidelink transmissions and configuration-authorized sidelinks.

[0047] Other applicable areas of this disclosure will become apparent from the detailed description provided below. It should be understood that the detailed description of the exemplary embodiments is for illustrative purposes only and is therefore not necessarily intended to limit the scope of this disclosure. Detailed Implementation

[0048] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities—including work on codecs, security, and quality of service. Recent Radio Access Technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced, and New Radio (NR), also known as “5G.” The development of 3GPP NR standards is expected to continue and include the definition of next-generation radio access technologies (new RATs), expected to include new flexible radio access below 7 GHz and new ultra-mobile broadband radio access above 7 GHz. Flexible radio access is expected to include new, non-backward-compatible radio access in the new spectrum below 7 GHz and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with varying requirements. Ultra-mobile broadband is expected to include centimeter wave (cmWave) and millimeter wave (mmWave) spectrum, which will provide opportunities for ultra-mobile broadband access for applications such as indoor spaces and hotspots. In particular, Ultra Mobile Broadband is expected to share a common design framework with flexible radio access below 7 GHz, featuring design optimizations specific to cmWave and mmWave.

[0049] 3GPP has identified a variety of use cases that NR is expected to support, resulting in diverse user experience requirements regarding data rates, latency, and mobility. Use cases include the following general categories: Enhanced Mobile Broadband (eMBB) Ultra-Reliable Low-Latency Communications (URLLC), Massive Machine-Type Communications (mMTC), network operations (e.g., network slicing, routing, migration and interworking, energy saving), and Enhanced Vehicle-to-Everything (eV2X) communications, which can include any of vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P), and vehicle-to-other-entities communications. Specific services and applications within these categories include, for example, surveillance and sensor networks, remote device control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first-responder connectivity, automotive electronic calling (ecall), disaster alerts, real-time gaming, multi-person video calling, autonomous driving, augmented reality, touch-sensitive internet, virtual reality, home automation, robotics, and aerial drones, among others. This document anticipates all of these use cases, as well as others.

[0050] The following is a list of acronyms related to service levels and core network technologies that may appear in the following description. Unless otherwise stated, acronyms used herein refer to the corresponding terms listed below.

[0051] List of ABBREVIATIONS (Abbreviations)

[0052]

[0053]

[0054] Example communication systems and networks

[0055] Figure 1A An example communication system 100 is illustrated, in which the systems, methods, and apparatus described and claimed herein can be used. Communication system 100 may include wireless transceiver units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g, which are generally or collectively referred to as one or more WTRUs 102. Communication system 100 may include radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, core networks 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and network services 113. Network services 113 may include, for example, V2X servers, V2X functions, ProSe servers, ProSe functions, IoT services, video streaming, and / or edge computing.

[0056] It should be understood that the concepts disclosed herein can be used with any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102 can be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Figure 1A In the example, each of WTRU 102 is in Figure 1A-1E The device is described as a handheld wireless communication device. It is understood that, for the various use cases considered for wireless communication, each WTRU may include or be included in any type of device or apparatus configured to transmit and / or receive wireless signals. By way of example only, such devices or apparatus include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, tablets, netbooks, notebook computers, personal computers, wireless sensors, consumer electronics, wearable devices such as smartwatches or smart clothing, medical or e-health devices, robots, industrial equipment, drones, vehicles such as cars, buses, or trucks, trains, or airplanes, etc.

[0057] The communication system 100 may also include base station 114a and base station 114b. Figure 1AIn the example, each base station 114a and 114b is depicted as a single element. In practice, base stations 114a and 114b may include any number of interconnected base stations and / or network elements. Base station 114a may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, the Internet 110, network services 113, and / or other networks 112). Similarly, base station 114b may be any type of device configured to wired and / or wirelessly interface with Remote Radio Headends (RRHs) 118a and 118b, Transmit and Receive Points (TRPs) 119a and 119b, and / or Roadside Units (RSUs) 120a and 120b to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or network services 113). RRH 118a, 118b can be any type of device configured to wirelessly interface with at least one of WTRU 102 (e.g., WTRU 102c) to facilitate access to one or more communication networks (such as core network 106 / 107 / 109, Internet 110, network service 113 and / or other network 112).

[0058] TRPs 119a and 119b can be any type of device configured to wirelessly interface with at least one of WTRUs 102d to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, Internet 110, network services 113, and / or other networks 112). RSUs 120a and 120b can be any type of device configured to wirelessly interface with at least one of WTRUs 102e or 102f to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, Internet 110, other networks 112, and / or network services 113). For example, base stations 114a and 114b can be base transceivers (BTS), nodes-B, eNode B, home nodes-B, home eNode B, next-generation nodes-B (gNode B), satellites, site controllers, access points (APs), wireless routers, etc.

[0059] Base station 114a may be part of RAN 103 / 104 / 105, and may also include other base station and / or network elements (not shown), such as Base Station Controller (BSC), Radio Network Controller (RNC), relay nodes, etc. Similarly, base station 114b may be part of RAN 103b / 104b / 105b, and may also include other base station and / or network elements (not shown), such as BSC, RNC, relay nodes, etc. Base station 114a may be configured to transmit and / or receive radio signals within a specific geographical area that may be referred to as a cell (not shown). Similarly, base station 114b may be configured to transmit and / or receive wired and / or radio signals within a specific geographical area that may be referred to as a cell (not shown). The cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, for example, base station 114a may include three transceivers, for example, one for each sector of the cell. For example, base station 114a can employ multiple-input multiple-output (MIMO) technology, thus allowing multiple transceivers to be used for each sector of the cell.

[0060] Base station 114a can communicate with one or more of WTRUs 102a, 102b, 102c, and 102g via air interfaces 115 / 116 / 117, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interfaces 115 / 116 / 117.

[0061] Base station 114b can communicate with one or more of RRH 118a and 118b, TRP 119a and 119b, and / or RSU 120a and 120b via wired or air interfaces 115b / 116b / 117b. The wired or air interfaces 115b / 116b / 117b can be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., RF, microwave, IR, UV, visible light, centimeter wave, millimeter wave, etc.). Any suitable RAT can be used to establish air interfaces 115b / 116b / 117b.

[0062] RRH 118a, 118b, TRP 119a, 119b and / or RSU 120a, 120b can communicate with one or more of WTRU 102c, 102d, 102e, 102f via air interface 115c / 116c / 117c, which can be any suitable wireless communication link (e.g., RF, microwave, IR, UV, visible light, centimeter wave, millimeter wave, etc.). Any suitable RAT can be used to establish air interface 115c / 116c / 117c.

[0063] WTRU 102 can communicate with each other via direct air interfaces 115d / 116d / 117d, or via sidelink communication such as any suitable wireless communication link (e.g., RF, microwave, IR, UV, visible light, centimeter wave, millimeter wave, etc.). Any suitable RAT can be used to establish air interfaces 115d / 116d / 117d.

[0064] Communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a and WTRU 102a, 102b, 102c in RAN 103 / 104 / 105 or RRH 118a, 118b, TRP 119a, 119b and / or RSU 120a and 120b and WTRU 102c, 102d, 102e and 102f in RAN 103b / 104b / 105b can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively. WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

[0065] Base stations 114a and WTRUs 102a, 102b, 102c and 102g in RAN 103 / 104 / 105, or RRHs 118a and 118b, TRPs 119a and 119b and / or RSUs 120a and 120b, and WTRUs 102c and 102d in RAN 103b / 104b / 105b, can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can, for example, use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively. Air interfaces 115 / 116 / 117 or 115c / 116c / 117c can implement 3GPP NR technology. LTE and LTE-A technologies may include LTE D2D and / or V2X technologies and interfaces (such as sidelink communication). Similarly, 3GPP NR technologies may include NR V2X technologies and interfaces (such as sidelink communication).

[0066] Base stations 114a and WTRUs 102a, 102b, 102c and 102g in RAN 103 / 104 / 105 or RRHs 118a and 118b, TRPs 119a and 119b and / or RSUs 120a and 120b and WTRUs 102c, 102d, 102e and 102f in RAN 103b / 104b / 105b can implement radio technologies such as IEEE 802.16 (e.g., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, Transition Standard 2000 (IS-2000), Transition Standard 95 (IS-95), Transition Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Evolution Enhanced Data Rate (EDGE), GSM EDGE (GERAN), etc.

[0067] For example, Figure 1ABase station 114c can be a wireless router, home node B, home eNode B, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area (such as a business premises, home, vehicle, train, antenna, satellite, factory, campus, etc.). Base station 114c and WTRU 102 (e.g., WTRU 102e) can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). Similarly, base station 114c and WTRU 102 (e.g., WTRU 102d) can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). Base station 114c and WTRU 102 (e.g., WRTU 102e) can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114c can have a direct connection to the Internet 110. Therefore, base station 114c does not need to access the Internet 110 via core network 106 / 107 / 109.

[0068] RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b can communicate with core network 106 / 107 / 109, which can be any type of network configured to provide voice, data, messaging, authorization and authentication, application and / or Voice over Internet Protocol (VoIP) services to one or more WTRU 102. For example, core network 106 / 107 / 109 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, and / or perform advanced security functions such as user authentication.

[0069] Although not in Figure 1A As shown, but it should be understood that RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or core network 106 / 107 / 109 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b. For example, in addition to being connected to RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b which can utilize E-UTRA radio technology, core network 106 / 107 / 109 can also communicate with another RAN (not shown) that uses GSM or NR radio technology.

[0070] Core networks 106 / 107 / 109 can also serve as gateways for WTRU 102 to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include circuit-switched telephone network services providing Common Old Style Telephone (POTS). The Internet 110 may include global systems and equipment of interconnected computer networks using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Other networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include any type of packet data network (e.g., IEEE 802.3 Ethernet) or another core network connected to one or more RANs, which may use the same RAT as RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b or a different RAT.

[0071] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may include multi-mode capability. For example, WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks via different wireless links. Figure 1A The WTRU 102g shown can be configured to communicate with a base station 114a that can employ cellular-based radio technology and a base station 114c that can employ IEEE 802 radio technology.

[0072] Although not in Figure 1A As shown, but it should be understood, user equipment can make a wired connection to the gateway. The gateway can be a residential gateway (RG). The RG can provide connectivity to the core network 106 / 107 / 109. It should be understood that many of the schemes contained herein are equivalently applicable to UEs acting as WTRUs and UEs connected to the network using wired connections. For example, schemes applicable to radio interfaces 115, 116, 117, and 115c / 116c / 117c are equivalently applicable to wired connections.

[0073] Figure 1B This is a system diagram of example RAN 103 and core network 106. As described above, RAN 103 can communicate with WTRUs 102a, 102b, and 102c via air interface 115 using UTRA radio technology. RAN 103 can also communicate with core network 106. Figure 1BAs shown, RAN 103 may include nodes-B 140a, 140b, and 140c, each of which may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 115. Each node-B 140a, 140b, and 140c may be associated with a specific cell (not shown) within RAN 103. RAN 103 may also include RNCs 142a and 142b. It should be understood that RAN 103 may include any number of nodes-B and Radio Network Controllers (RNCs).

[0074] like Figure 1B As shown, nodes B 140a and 140b can communicate with RNC 142a. Additionally, node B 140c can communicate with RNC 142b. Nodes B 140a, 140b, and 140c can communicate with their respective RNCs 142a and 142b via the Iub interface. RNCs 142a and 142b can communicate with each other via the Iur interface. Each of RNCs 142a and 142b can be configured to control the corresponding nodes B 140a, 140b, and 140c to which it is connected. Furthermore, each of RNCs 142a and 142b can be configured to perform or support other functions, such as outer-loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc.

[0075] Figure 1B The core network 106 shown may include a Media Gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. While each of the foregoing elements is depicted as part of the core network 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0076] RNC 142a in RAN 103 can connect to MSC 146 in core network 106 via IuCS interface. MSC 146 can connect to MGW 144. MSC 146 and MGW 144 can provide WTRU 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment.

[0077] RNC 142a in RAN 103 can also connect to SGSN 148 in core network 106 via IuPS interface. SGSN 148 can connect to GGSN 150. SGSN 148 and GGSN 150 can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices.

[0078] The core network 106 can also connect to other networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0079] Figure 1C This is a system diagram of example RAN 104 and core network 107. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with core network 107.

[0080] RAN 104 may include eNode-B 160a, 160b, and 160c, although it should be understood that RAN 104 may include any number of eNode-Bs. Each of eNode-B 160a, 160b, and 160c may include one or more transceivers for communicating with WTRU 102a, 102b, and 102c via air interface 116. For example, eNode-B 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a.

[0081] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink and / or downlink, etc. Figure 1C As shown, eNode-B 160a, 160b and 160c can communicate with each other via the X2 interface.

[0082] Figure 1C The core network 107 shown may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the foregoing elements is depicted as part of the core network 107, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0083] The MME 162 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can also provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM or WCDMA.

[0084] Service Gateway 164 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. Service Gateway 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. Service Gateway 164 can also perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when downlink data can be used for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0085] Service gateway 164 can also be connected to PDN gateway 166, which can provide WTRU 102a, 102b and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b and 102c and IP-enabled devices.

[0086] Core network 107 can facilitate communication with other networks. For example, core network 107 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. For example, core network 107 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between core network 107 and PSTN 108, or can communicate with it. Furthermore, core network 107 can provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0087] Figure 1DThis is a system diagram of example RAN 105 and core network 109. RAN 105 can communicate with WTRU 102a and 102b via air interface 117 using NR radio technology. RAN 105 can also communicate with core network 109. The non-3GPP interoperability function (N3IWF199) can communicate with WTRU 102c via air interface 198 using non-3GPP radio technology. N3IWF 199 can also communicate with core network 109.

[0088] RAN 105 may include gNode-B 180a and 180b. It should be understood that RAN 105 may include any number of gNode-Bs. Each gNode-B 180a and 180b may include one or more transceivers for communicating with WTRUs 102a and 102b via air interface 117. When using integrated access and backhaul connectivity, the same air interface may be used between the WTRU and the gNode-B, which may be via the core network 109 of one or more gNBs. gNode-B 180a and 180b may implement MIMO, MU-MIMO, and / or digital beamforming technologies. Therefore, for example, gNode-B 180a may use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a. It should be understood that RAN 105 may employ other types of base stations, such as eNode-Bs. It should also be understood that RAN 105 may employ more than one type of base station. For example, the RAN may use both eNode-Bs and gNode-Bs.

[0089] The N3IWF 199 may include a non-3GPP access point 180c. It should be understood that the N3IWF 199 may include any number of non-3GPP access points. The non-3GPP access point 180c may include one or more transceivers for communicating with the WTRU 102c via air interface 198. The non-3GPP access point 180c may communicate with the WTRU 102c via air interface 198 using the 802.11 protocol.

[0090] Each of the gNode-B 180a and 180b can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink and / or downlink, etc. Figure 1D As shown, for example, gNode-B 180a and 180b can communicate with each other via the Xn interface.

[0091] Figure 1DThe core network 109 shown may be a 5G core network (5GC). Core network 109 can provide various communication services to customers interconnected via a radio access network. Core network 109 includes entities that perform core network functions. As used herein, the terms "core network entity" or "network function" refer to any entity that performs one or more functions of the core network. It should be understood that such a core network entity may be a logical entity implemented in the form of computer-executable instructions (software), which are stored in a device or computer system (such as...) configured for wireless and / or network communications. Figure 1G The system 90 shown is stored in its memory and executed on its processor.

[0092] exist Figure 1D In the example, the 5G core network 109 may include Access and Mobility Management Functions (AMF) 172, Session Management Functions (SMF) 174, User Plane Functions (UPF) 176a and 176b, User Data Management Functions (UDM) 197, Authentication Server Functions (AUSF) 190, Network Openness Functions (NEF) 196, Policy Control Functions (PCF) 184, Non-3GPP Interoperability Functions (N3IWF) 199, and User Data Repository (UDR) 178. While each of the foregoing elements is depicted as part of the 5G core network 109, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator. It should also be understood that the 5G core network may not consist of all of these elements, may consist of additional elements, and may consist of multiple instances of each of these elements. Figure 1D The network functions are shown to be directly interconnected; however, it should be understood that they can communicate via routing agents such as diameter routing agents or message buses.

[0093] exist Figure 1D In the example, the connections between network functions are implemented through a set of interfaces or reference points. It should be understood that a network function can be modeled, described, or implemented as a set of services invoked or called by other network functions or services. Invocation of network function services can be achieved through direct connections between network functions, message exchange on a message bus, calling software functions, etc.

[0094] The AMF 172 can connect to RAN 105 via the N2 interface and can be used as a control node. For example, the AMF 172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. The AMF can forward user plane tunnel configuration information to RAN 105 via the N2 interface. The AMF 172 can receive user plane tunnel configuration information from the SMF via the N11 interface. The AMF 172 can typically route and forward NAS packets to / from WTRUs 102a, 102b, and 102c via the N1 interface. The N1 interface... Figure 1D Not shown in the image.

[0095] SMF 174 can connect to AMF 172 via interface N11. Similarly, SMF 174 can connect to PCF184 via interface N7 and to UPF 176a and 176b via interface N4. SMF 174 can be used as a control node. For example, SMF 174 can be responsible for session management, IP address allocation for WTRU 102a, 102b and 102c, management and configuration of traffic routing rules in UPF 176a and UPF 176b, and generation of downlink data notifications to AMF 172.

[0096] UPF 176a and UPF 176b can provide WTRU 102a, 102b, and 102c with access to packet data networks (PDNs) (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and other devices. UPF 176a and UPF 176b can also provide WTRU 102a, 102b, and 102c with access to other types of packet data networks. For example, other networks 112 can be any type of network, such as Ethernet or switched data packets. UPF 176a and UPF 176b can receive traffic routing rules from SMF 174 via the N4 interface. UPF 176a and UPF 176b can provide access to packet data networks by connecting to the packet data network using the N6 interface or by connecting to each other and to other UPFs via the N9 interface. In addition to providing access to packet data networks, UPF 176 can also be responsible for packet routing and forwarding, policy rule enforcement, quality of service processing of user plane traffic, and downlink packet buffering.

[0097] For example, the AMF 172 can also connect to the N3IWF 199 via the N2 interface. For example, the N3IWF facilitates connectivity between the WTRU 102c and the 5G core network 170 via a 3GPP-undefined radio ground docking technology. The AMF can interact with the N3IWF 199 in the same or similar manner as it interacts with the RAN 105.

[0098] PCF 184 can be connected to SMF 174 via N7 interface, to AMF 172 via N15 interface, and to Application Function (AF) 188 via N5 interface. N15 and N5 interfaces are not... Figure 1D As shown in the diagram, PCF 184 can provide policy rules to control plane nodes such as AMF 172 and SMF 174, allowing these rules to be executed. PCF 184 can send policies for WTRUs 102a, 102b, and 102c to AMF 172, enabling AMF to pass the policies to WTRUs 102a, 102b, and 102c via the N1 interface. The policies can then be executed or applied at WTRUs 102a, 102b, and 102c.

[0099] UDR 178 can act as a repository for authentication credentials and subscription information. The UDR can connect to network functions, allowing them to add, read, and modify data in the repository. For example, UDR 178 can connect to PCF 184 via interface N36. Similarly, UDR 178 can connect to NEF 196 via interface N37, and UDR 178 can connect to UDM 197 via interface N35.

[0100] The UDM 197 can be used as an interface between the UDR 178 and other network functions. The UDM 197 can authorize network functions to access the UDR 178. For example, the UDM 197 can connect to the AMF 172 via interface N8, and to the SMF 174 via interface N10. Similarly, the UDM 197 can connect to the AUSF 190 via interface N13. The UDR 178 and UDM 197 can be tightly integrated.

[0101] The AUSF 190 performs authentication-related operations and connects to the UDM 178 via the N13 interface and to the AMF 172 via the N12 interface.

[0102] The NEF 196 exposes the capabilities and services of the 5G core network 109 to the Application Function (AF) 188. This exposure can occur on the N33 API interface. The NEF can connect to the AF 188 via the N33 interface and can connect to other network functions to expose the capabilities and services of the 5G core network 109.

[0103] Application function 188 can interact with network functions in the 5G core network 109. Interaction between application function 188 and network functions can occur via a direct interface or via NEF 196. Application function 188 can be considered part of the 5G core network 109 or can be deployed outside the 5G core network 109 by an enterprise with business relationships with mobile network operators.

[0104] Network slicing is a mechanism that mobile network operators can use to support one or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types running across a single RAN. Network slicing enables operators to create customized networks optimized for different market scenarios that require different requirements, such as in terms of functionality, performance, and isolation.

[0105] 3GPP has designed the 5G core network to support network slicing. Network slicing is a powerful tool that network operators can use to support diverse groups of 5G use cases (e.g., massive IoT, critical communications, V2X, and enhanced mobile broadband), which require very different and sometimes extreme requirements. Without network slicing, the network architecture may not be flexible and scalable enough to effectively support a wider range of use case needs when each use case has its own set of performance, scalability, and availability requirements. Furthermore, the introduction of new network services should be more efficient.

[0106] Refer again Figure 1D In a network slicing scenario, WTRU 102a, 102b, or 102c can connect to AMF 172 via the N1 interface. AMF can logically be part of one or more slices. AMF can coordinate connections or communication between WTRU 102a, 102b, or 102c and one or more UPF 176a and 176b, SMF 174, and other network functions. Each of UPF 176a and 176b, SMF 174, and other network functions can be part of the same slice or different slices. When they are part of different slices, they can be isolated from each other because they can utilize different computing resources, security credentials, etc.

[0107] Core network 109 can facilitate communication with other networks. For example, core network 109 may include or be able to communicate with an IP gateway (such as an IP Multimedia Subsystem (IMS) server) that serves as an interface between 5G core network 109 and PSTN 108. For example, core network 109 may include or be able to communicate with a Short Message Service (SMS) service center that facilitates communication via Short Message Service. For example, 5G core network 109 can facilitate the exchange of non-IP data packets between WTRUs 102a, 102b, and 102c and servers or application functions 188. Furthermore, core network 170 can provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0108] This article describes and Figure 1A , 1C The core network entities shown in 1D and 1E are identified by the names provided to those entities in certain existing 3GPP specifications. However, it should be understood that these entities and functions may be identified by other names in the future, and some entities or functions may be combined in future 3GPP specifications (including future 3GPP NR specifications). Therefore, Figure 1A , 1B The specific network entities and functions described and illustrated in 1C, 1D and 1E are provided by way of example only, and it should be understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or in the future.

[0109] Figure 1E An example communication system 111 is illustrated, in which the systems, methods, and apparatuses described herein can be used. Communication system 111 may include radio transceiver units (WTRUs) A, B, C, D, E, F, a base station gNB 121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein can be applied to any number of WTRUs, base station gNBs, V2X networks, and / or other network elements. One or more, or all, of WTRUs A, B, C, D, E, and F may be outside the access network coverage 122. WTRUs A, B, and C form a V2X group, where WTRU A is the group leader and WTRUs B and C are group members.

[0110] If WTRUs A, B, C, D, E, and F are within the coverage area of ​​the access network (in... Figure 1E (Only B and F are shown under network coverage), then WTRUs A, B, C, D, E, and F can communicate with each other via gNB 121 through Uu interface 129b. If WTRUs A, B, C, D, E, and F are under or outside the access network coverage (e.g., in...), Figure 1E If A, C, D, and E are shown outside the network coverage, then WTRUA, B, C, D, E, and F can communicate directly with each other via side link (PC5 or NR PC5) interfaces 125a, 125b, and 128.

[0111] WTRUs A, B, C, D, E, and F can communicate with RSUs 123a or 123b via vehicle-to-network (V2N) 126 or sidelink interface 125b. WTRUs A, B, C, D, E, and F can communicate with V2X server 124 via vehicle-to-infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F can communicate with another UE via vehicle-to-person (V2P) interface 128.

[0112] Figure 1F Example apparatus or device WTRU 102 (such as the systems, methods and apparatus described herein) can be configured for wireless communication and operation. Figure 1A , 1B A block diagram of WTRU 102 (1C, 1D, or 1E). For example... Figure 1F As shown, example WTRU 102 may include a processor 118, transceiver 120, transmit / receive element 122, speaker / microphone 124, keyboard 126, display / touchpad / indicator 128, non-removable memory 130, removable memory 132, power supply 134, global positioning system (GPS) chipset 136, and other peripheral devices 138. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements. Furthermore, base stations 114a and 114b, and / or base stations 114a and 114b may represent nodes (such as, but not limited to, transceiver stations (BTS), node-B, site controllers, access points (APs), home node-B, evolved home node-B (eNodeB), home evolved node-B (HeNB), home evolved node-B gateway, next-generation node-B (gNode-B), and proxy nodes, etc.), which may be included in... Figure 1F Some or all of the elements described in the text and in this paper.

[0113] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, and transceiver 120 can be coupled to transmit / receive element 122. Although Figure 1F The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0114] The UE's transmit / receive element 122 can be configured to transmit data to the base station (e.g., via air interface 115 / 116 / 117). Figure 1A The base station 114a) transmits or receives signals from the base station, or transmits or receives signals to or from another UE via air interface 115d / 116d / 117d. For example, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. For example, the transmit / receive element 122 may be a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. The transmit / receive element 122 may be configured to transmit and receive both RF and optical signals. It should be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless or wired signals.

[0115] Furthermore, although the send / receive element 122 is in Figure 1F While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Therefore, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interfaces 115 / 116 / 117.

[0116] Transceiver 120 can be configured to modulate signals to be transmitted by transmit / receive element 122 and demodulate signals to be received by transmit / receive element 122. As described above, WTRU 102 can have multimode capability. Therefore, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate with different RRHs, TRPs, RSUs, or nodes via multiple RATs (e.g., NR and IEEE 802.11 or NR and E-UTRA), or using the same RAT via multiple beams.

[0117] The processor 118 of WTRU 102 can be coupled to and receive user input data from a speaker / microphone 124, keyboard 126, and / or display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, keyboard 126, and / or display / touchpad / indicator 128. Furthermore, the processor 118 can access and store information from any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. The processor 118 can access and store information from memory that is not physically located on WTRU 102 (such as on a server hosted in the cloud or on an edge computing platform or in a home computer (not shown).

[0118] The processor 118 may receive power from the power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0119] The processor 118 may also be coupled to a GPS chipset 136 configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interface 115 / 116 / 117 and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method.

[0120] The processor 118 can also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), Universal Serial Bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, etc. Modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.

[0121] WTRU 102 may be included in other devices or equipment, such as sensors, consumer electronics, wearable devices such as smartwatches or smart clothing, medical or electronic health devices, robots, industrial equipment, drones, vehicles such as cars, trucks, trains, or airplanes. WTRU 102 may be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces, such as interconnect interfaces that may include one of the peripheral devices 138.

[0122] Figure 1G This is a block diagram of an exemplary computing system 90, which can illustrate... Figure 1A , 1C One or more devices of the communication networks shown in 1D and 1E, such as certain nodes or functional entities in RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, other networks 112, or network services 113. The computing system 90 may include a computer or server and may be primarily controlled by computer-readable instructions, which may be in the form of software, regardless of where or by which such software is stored or accessed. Such computer-readable instructions may be executed within a processor 91 to enable the computing system 90 to function. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable the computing system 90 to operate in a wireless environment. The coprocessor 81 is an optional processor, distinct from the main processor 91, which can perform additional functions or assist the main processor 91. The processor 91 and / or the coprocessor 81 can receive, generate, and process data relating to the methods and apparatus disclosed herein.

[0123] In operation, processor 91 fetches, decodes, and executes instructions, and transfers information to and from other resources via the main data transfer path system (bus 80) of the computing system. This system bus connects the components within the computing system 90 and defines the medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for the operating system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0124] The memory coupled to the system bus 80 includes random access memory (RAM) 82 and read-only memory (ROM) 93. Such memory includes circuitry that allows for the storage and retrieval of information. ROM 93 typically contains stored data that cannot be easily modified. Data stored in RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 can be controlled by the memory controller 92. The memory controller 92 provides address translation functionality, translating virtual addresses into physical addresses when instructions are executed. The memory controller 92 also provides memory protection functionality, isolating processes within the system and separating system processes from user processes. Therefore, a program running in first mode can only access memory mapped by its own process's virtual address space; it cannot access memory within another process's virtual address space unless inter-process memory sharing has been established.

[0125] In addition, the computing system 90 may include a peripheral device controller 83, which is responsible for transmitting instructions from the processor 91 to peripheral devices such as a printer 94, a keyboard 84, a mouse 95, and a disk drive 85.

[0126] A display 86, controlled by a display controller 96, is used to display visual output generated by a computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touchpad. The display controller 96 includes electronic components that generate video signals to be sent to the display 86.

[0127] Furthermore, the computing system 90 may include communication circuitry, such as, for example, a wireless or wired network adapter 97, which can be used to connect the computing system 90 to an external communication network or device, such as... Figure 1A , 1B The computing system 90 can communicate with other nodes or functional entities in those networks, such as RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, WTRU 102, or other networks 112, to enable the computing system 90 to communicate with other nodes or functional entities in those networks. Communication circuitry, alone or in combination with the processor 91, can be used to perform the transmitting and receiving steps of certain means, nodes, or functional entities described herein.

[0128] It should be understood that any or all of the apparatuses, systems, methods, and processes described herein may be embodied in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor such as processor 118 or 91, cause the processor to perform and / or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer-executable instructions that execute on a processor of an apparatus or computing system configured for wireless and / or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media for storing information implemented in any non-transitory (e.g., tangible or physical) method or technology, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other storage technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other tangible or physical medium that can be used to store desired information and is accessible by a computing system.

[0129] 5G V2X use cases

[0130] With significant advancements in vehicle-to-everything (V2X) applications, the transmission of short messages containing basic vehicle status data for basic security can be expanded to include larger messages containing raw sensor data, vehicle intent data, coordination, and confirmation of future actions. For these advanced applications, the expected requirements for data rates, latency, reliability, communication range, and speed are even more stringent.

[0131] For enhanced V2X (eV2X) services, 3GPP has identified 25 use cases and related requirements in TR 22.886.

[0132] TS22.186 specifies a set of normative requirements, and these use cases are categorized into four use case groups: vehicle platooning, extended sensors, advanced driving, and remote driving.

[0133] TS22.186 specifies a detailed description of the performance requirements for each use case group.

[0134] Uu-based sidelink control for V2X in NR

[0135] In NR V2X, sidelink resource allocation modes 1 and 2 are approved. In mode 1, the base station schedules sidelink resources for the UE to use for sidelink transmission. The UE can use the allocated resources to perform broadcast, multicast, or unicast on the sidelink. In mode 2, the UE determines the sidelink resources for sidelink transmission within the sidelink resources configured by the base station or pre-configured sidelink resources.

[0136] Mode 1 allows the gNB to allocate sidelink resources between Uu and sidelink transports via the Uu interface used for both dedicated sidelink carriers and shared licensed carriers. When a carrier is shared between Uu and sidelink transports, they may occur in the same frame but in different time slots, or they may occur in the same time slot. In subsequent sections, the carrier multiplexed over Uu and sidelink transports is referred to as a shared carrier.

[0137] In Mode 1, the gNB can dynamically allocate resources for sidelink transmission, or the gNB can allocate resources for sidelink transmission by configuring authorization through Type 1 or Type 2.

[0138] Inter-UE multiplexing in NR

[0139] Downlink transmissions will conflict when some time and frequency resources of two or more downlink transmissions overlap. In some scenarios (e.g., if there is urgent data that needs to be transmitted with extremely low latency and no unscheduled resources are available), the gNB will perform such scheduling. In NR, when this happens, the gNB will discard the low-priority transmission and send the high-priority data. The gNB will then send a preemption indication to instruct the preempted UE(s)(s) to flush their(s) buffer(s).

[0140] DCI format 2_1 is used to notify the UE of one or more PRBs and one or more OFDM symbols within a time slot, for which the UE may assume there is no transmission intended for that UE. Within a DCI, it can carry multiple preemption indications, each of which is 14 bits. The interpretation of the bitmap is configurable. For example, each bit can represent one OFDM symbol in the full bandwidth portion and time domain, or two OFDM symbols in half the bandwidth portion and time domain.

[0141] Similar to downlink, in some scenarios, two scheduled uplink transmissions may also conflict. When uplink transmission conflicts occur, the performance of the scheduled low-priority uplink transmission may affect the performance of the scheduled high-priority uplink transmission. To address this issue, the gNB can send a cancellation indicator to cancel the scheduled low-priority uplink transmission, or the gNB can use a power-based mechanism to reduce the impact of the scheduled low-priority uplink transmission.

[0142] In NR V2X Mode 1 shared carrier scenarios, the gNB can allocate sidelink transmissions on a shared carrier with downlink (DL) and / or uplink (UL) transmissions on the Uu interface using dynamic scheduling, Type 1 configuration granting, or Type 2 configuration granting. For example, the gNB might schedule very low-latency or high-priority DL data transmissions on the Uu interface for a UE, which could overlap with a sidelink transmission already scheduled or configured for another UE. In this case, both transmissions may degrade or even fail. Therefore, mechanisms are needed to handle inter-UE conflicts between dynamically scheduled or configured sidelink transmissions and dynamically scheduled very low-latency or high-priority DL or UL transmissions.

[0143] For NR V2X Mode 1, the gNB can allocate sidelink transmissions using dynamic scheduling, Type 1 configuration granting, or Type 2 configuration granting. For example, the gNB might schedule very low-latency or high-priority data transmissions on a sidelink for a UE, which may overlap with sidelink transmissions already scheduled or configured for another UE. In this case, both transmissions may degrade or even fail. Therefore, mechanisms are needed to handle inter-UE conflicts between dynamically scheduled or configured sidelink transmissions and dynamically scheduled very low-latency or high-priority sidelink transmissions.

[0144] The publicly disclosed plan includes:

[0145] This disclosure includes schemes for handling inter-UE conflicts in NR V2X for the following use cases:

[0146] ● UE-to-UE conflict between dynamically scheduled broadcast-side links and dynamically scheduled Uu transmissions.

[0147] ● UE-to-UE conflict between dynamically scheduled unicast links and dynamically scheduled Uu transmissions.

[0148] ● UE-to-UE conflict between dynamically scheduled multicast links and dynamically scheduled Uu transmissions.

[0149] ● UE-to-UE conflicts between broadcast sidelinks based on configuration authorization and dynamically scheduled Uu transmissions.

[0150] ● UE-to-UE conflicts between configuration-authorized unicast side links and dynamically scheduled Uu transmissions.

[0151] ● UE-to-UE conflicts between configuration-authorized multicast side links and dynamically scheduled Uu transmissions.

[0152] ● UE-to-UE conflict between a dynamically scheduled side link and another dynamically scheduled side link.

[0153] ● UE-to-UE conflicts between sidelinks based on configuration authorization and sidelinks that are dynamically scheduled.

[0154] Publicly available UE conflict resolution mechanisms include:

[0155] ●Reduce the transmission power of preempted transmissions.

[0156] ●Reduce the antenna gain of the sender and / or receiver in the preempted transmission.

[0157] ●Increase the transmission power of the transmission that needs to preempt other transmissions.

[0158] ●Increase the antenna gain of the transmitter and / or receiver of the transmission that is trying to preempt other transmissions.

[0159] ●Seize the antenna panel from which the transmission has been seized.

[0160] ● Cancel the transmission that was preempted.

[0161] This disclosure includes the following solutions:

[0162] ● Configuration and signaling for UE monitoring and decoding sidelink cancellation indication (SL-CI).

[0163] ● Mechanism for handling inter-UE conflicts with duplicate sidelink transmissions.

[0164] ● Priority sorting rules for concurrent sidelink and uplink transmissions. Dynamically scheduled Uu transmissions preempt sidelink transmissions.

[0165] In NR V2X Mode 1, the Uu interface and sidelinks can operate on a shared carrier. The gNB can schedule DL or UL transmissions on the Uu interface and transmissions on the sidelinks based on system state. In some scenarios, resources scheduled for very low-latency or high-priority DL or UL transmissions (e.g., PDSCH and / or PUSCH) on the Uu interface can partially or completely overlap with resources allocated to sidelink transmissions in time and / or frequency, which have the following characteristics: Figure 2 The alternative scenarios are shown.

[0166] ●Scenario A: Downlink transmissions dynamically scheduled on the Uu interface (e.g.)

[0167] PDSCH may overlap or conflict with dynamically scheduled sidelink transmissions.

[0168] ●Scenario B: Uplink transmissions on the Uu interface that are dynamically scheduled (e.g.)

[0169] PUSCH may overlap or conflict with dynamically scheduled sidelink transmissions.

[0170] ●Scenario C: Downlink transmissions dynamically scheduled on the Uu interface (e.g.)

[0171] PDSCH may overlap / conflict with the configuration authorization sidelink transmission.

[0172] ●Scenario D: Uplink transmissions on the Uu interface that are dynamically scheduled (e.g.,

[0173] PUSCH may overlap / conflict with the configuration authorization sidelink transmission.

[0174] Figure 2 The sidelink transmission shown can be broadcast, multicast, or unicast, or any combination thereof. In this example, the Uu transmission can have a higher priority or lower latency requirement compared to the sidelink transmission. To ensure that higher priority data is transmitted / received to / from the Uu transmission, the sidelink transmission can be preempted.

[0175] The broadcast-side link transmission preempted by the dynamically scheduled Uu transmission.

[0176] This section describes a scheme for situations where dynamically scheduled Uu transmissions conflict with dynamically scheduled broadcast-side link transmissions. In broadcast scenarios, the Tx UE (sender UE) will not receive ACK / NACK feedback from one or more Rx UEs (receiver UEs). The Uu transmissions discussed in this paper can be either downlink or uplink transmissions.

[0177] Assume UE1 is dynamically scheduled by the gNB to transmit a broadcast transmission on a sidelink; and assume UE2 is dynamically scheduled by the gNB to have transmission or reception (e.g., PDSCH or PUSCH) on the Uu interface, where some or all of the resources allocated to UE2 overlap in time and frequency with the resources allocated to UE1. To handle inter-UE conflicts, we disclose that this broadcast sidelink transmission can be preempted, with the following alternative scenarios:

[0178] Use higher power Uu transmission preemption

[0179] In the first alternative scenario, UE1 will perform broadcast sidelink transmission regardless of whether it receives preemption.

[0180] To ensure the transmission / reception of higher-priority data to / from UE2, Uu transmissions can be performed at a higher power level compared to power levels used in scenarios without inter-UE conflicts. For example, if it is a downlink transmission, the gNB can increase the transmit power and / or beamforming antenna gain; if it is an uplink transmission, UE2 can be instructed to increase the transmit power. The Transmission Power Command (TPC) field in the scheduling DCI can be used to instruct UE2 to increase the transmit power; alternatively, a bit field in the scheduling DCI can be used to indicate to UE2 whether it is preempting other transmissions; or, the selection of a specific codeword in the codebook for codebook-based UL transmissions can indicate the increased transmit power, which UE2 can perform at maximum power or by applying a predefined / preconfigured transmit power offset if it is preempting other transmissions; or, the scheduling DCI can instruct UE2 using the priority level of the scheduled uplink transmission, each priority level can be associated with a predefined / preconfigured transmit power level and / or offset, and UE2 will set the transmit power level accordingly based on the indicated priority level.

[0181] After UE1 performs a broadcast sidelink transmission, it can monitor downlink signals / channels (e.g., PDCCH) that potentially carry indicators to determine whether UE1's transmission has been preempted before refreshing UE1's transmission buffer. Information regarding the timing of preemption monitoring can be configured to the UE at the symbol and / or time slot by Radio Resource Control (RRC), such as monitoring periodicity. If UE1 does not detect preemption, it will refresh its buffer; if UE1 detects preemption, it can retain the buffer and prepare for retransmission.

[0182] If a preemption indication is detected, UE1 can detect that transmission has been preempted. The preemption indication can be UE-specific or group-specific. This indication can be carried in a sequence, preamble, reference signal, or DCI. When a UE-specific indication is used, a UE-specific configuration is configured for the UE. When a group-specific indication is used, the same group-specific configuration is configured for multiple UEs. For a UE configured with a group-specific indication, if it has not been scheduled for transmission between two monitoring moments, the UE can skip the next monitoring moment. UE1 can then receive a separately scheduled DCI to schedule retransmissions, such as... Figure 3 As shown. Alternatively, UE1 can detect that the transmission has been preempted by detecting signaling that jointly indicates preemption and resources used for retransmission, such as... Figure 4 As shown. Alternatively, preemption can be implicitly indicated through retransmission scheduling; for example, when UE1 receives a retransmission schedule for a broadcast-side link transmission, it determines that the initial broadcast-side link transmission was preempted, as... Figure 5 As shown in the figure, retransmission scheduling can be intra-slot scheduling or inter-slot scheduling, depending on factors such as latency requirements.

[0183] For a UE receiving a retransmission of a broadcast message, the UE can soft-combine multiple retransmissions of the received message(s) to improve the probability of successfully decoding the data. If the UE uses a preempted transmission for soft combination, it can degrade the decoding of that combination. One or more preemption indications can be sent to the receiving UE to notify it not to soft-combine the preempted transmission with one or more other transmissions(s). For example, after detecting preemption from the gNB, UE1 can broadcast the preemption to the receiving UE, for example, by means of the Block Group Refresh Indicator (CBGFI) field in the Side Link Control Information (SCI) for retransmission. For example, for a preempted Block Group (CBG), UE1 can set a bit in the CBGFI bitmap to "1". Alternatively, it can do so via the New Data Indicator (NDI) field in the SCI for retransmission. For example, if the retransmission is due to preemption, UE1 can switch the value in the NDI field in the SCI for retransmission. If the retransmission is not due to preemption, UE1 will not switch the value in the NDI field. Alternatively, when UE1 performs a retransmission, it can use a different RV than the initial transmission (e.g., RV0 for the initial transmission and RV2 for the retransmission). Or, when UE1 performs a retransmission, it can use a different HARQ ID (e.g., HARQ ID 1 for the initial transmission and HARQ ID 4 for the retransmission). By doing so, the Rx UE will treat the retransmission as a new transmission and will not attempt to combine it with the initial transmission.

[0184] The UE is pre-configured or indicated to know which transmissions can be soft-combined. This document specifies example signaling used to indicate such information. How the UE performs soft combination and whether the UE must perform soft combination depends on the specific UE implementation. Typically, the UE will perform combination whenever there is an opportunity to improve performance.

[0185] When UE1 performs a retransmission, it can retransmit the entire TB or it can retransmit only a subset of the TB, such as preempted symbols, physical resource blocks (PRBs), or CBGs.

[0186] An example of a public process for detecting preemption is in Figure 6The diagram illustrates a sidelink UE that has an inter-UE conflict with a scheduled Uu transmission. The UE receives the scheduling of the broadcast sidelink transmission (601). The UE performs the broadcast sidelink transmission on the scheduled resource (602). In another case, the receiving UE may also receive a preemption indication from the gNB. The UE monitors for preemption indications for the Uu transmission (603). When preemption is detected (604), the UE will retransmit (605) the broadcast on the sidelink. When preemption is not detected, the UE will refresh the buffer used for the transmitted packets (606).

[0187] Preempt low-priority SL transmissions using adjusted transmission control parameters.

[0188] In the second alternative scenario, UE1 can monitor for preemption before executing a broadcast sidelink transmission. If preemption occurs, the gNB can send an indication instructing UE1 to adjust transmission control parameters, such as TX power, MCS, transport layer configuration (e.g., diversity scheme), beamforming / MIMO scheme, CBG adaptation, etc. One example is that the UE can reduce its transmit power (even to zero) across the entire transmission or a portion of the transmission (e.g., reducing the data RE without reducing the DMRS RE). For instance, by detecting this indication, UE1 will overwrite the old TPC and transmit the scheduled broadcast sidelink transmission with the new transmit power.

[0189] The new transmit power level or offset can be dynamically indicated to the UE; alternatively, the UE can be instructed to switch to a pre-configured low power level or offset. This indication can be transmitted via signaling through DCI, reference signal, preamble, or sequence.

[0190] In one scenario, the UE can be instructed to reduce the power level of all allocated resources, regardless of whether it fully or partially overlaps with conflicting Uu transmissions. In this example, the UE can be signaled a value indicating the new transmit power; for example, the UE can be instructed to reduce its transmit power by an offset equal to a certain number of dB; or, the UE can be shown the absolute transmit power level it needs to change to. For instance, the UE can be configured with multiple sequences, each associated with a value. The UE can determine the new transmit power based on which sequence and / or preamble is detected.

[0191] Alternatively, when reference signals such as DMRS or CSI-RS are used to indicate power reduction, the UE can be configured with different reference signal time and frequency configurations, each associated with a value. The UE can determine the new transmit power based on the time and frequency resources in which the reference signal was detected.

[0192] Alternatively, the UE can be configured with a reference signal (DMRS or CSI-RS) time and frequency configuration but with different reference signal sequences. For example, the UE can be configured with four different sequence initializers for generating the reference signal sequences, each initializer being associated with a value, as shown in Table 1. The UE can determine the indicated power control command based on the detected reference signal sequence.

[0193] Table 1 - Example initializer values ​​configured for the UE to determine the associated power control commands.

[0194]

[0195]

[0196] Alternatively, the gNB can instruct the UE via UE-specific DCI or via group common DCI using power control commands. Information regarding monitoring timing can be configured for the UE via RRC, such as the monitoring period, the symbols to be monitored, and / or time slots. Alternatively, the UE can only monitor time slots containing allocated resources.

[0197] In another scenario, the UE may be instructed to reduce the power level of a portion of the allocated resources, for example, reducing the power level of some symbols and / or PRBs (e.g., overlapping symbols and / or PRBs). UE-specific DCIs can be used to indicate power control commands and the time-domain and / or frequency-domain resources to which the UE needs to apply the power control command, and in some cases, to indicate which time slot these PIs apply to. For example, a new DCI format with a CRC scrambled with a UE-specific RNTI (e.g., RNTIp) can be introduced. Such a DCI may carry: a power control command field indicating power adjustment; fields indicating which time-domain resources the UE can consider preempted and to which the power adjustment is applied, such as a 14-bit bitmap where each bit represents one symbol or a 7-bit bitmap where each bit represents two symbols in a time slot; and / or fields indicating which frequency resources the UE can consider preempted and to which the power adjustment is applied, such as through a bitmap. When a UE detects a DCI that scrambles the configured RNTIP during its monitoring period, the UE can determine that it has been preempted and identify power adjustments, preempted time-domain resources, and / or frequency-domain resources. In addition to introducing a new DCI format, this indication can also be provided using an existing DCI format (e.g., DCI format 0_1). When a UE detects a DCI format 0_1 ​​where some fields are set to predefined values, the UE can determine that this DCI is intended to indicate a power control command resulting from inter-UE conflicts and identify the power to be adjusted and the preempted time and / or resources.

[0198] Alternatively, a group common DCI can be used to indicate power control commands and the time-domain and / or frequency-domain resources to which the UE needs to apply the power control commands. For example, a new DCI format with a CRC scrambled using a group-specific RNTI (e.g., an RNTIpg that can be configured to be applied to a group of UEs) can be introduced. Such a DCI can carry: multiple power control command fields indicating power adjustments for each UE within the group; fields indicating which time-domain resources the UE can consider preempted and to which power adjustments should be applied, such as a 14-bit bitmap where each bit represents one symbol or a 7-bit bitmap where each bit represents two symbols in a time slot; and / or fields indicating which frequency-domain resources the UE can consider preempted and to which power adjustments should be applied, such as through a bitmap. When a group is formed, the power control command bits for each UE can be configured in the group common DCI via an RRC message. When the UE detects a DCI with scrambled RNTIPg during its monitoring period, the UE can determine that it has been preempted and identify the power adjustment in the configured bits, the preempted time domain resources and / or frequency domain resources.

[0199] Alternatively, sequences, preambles, and reference signals can be used to indicate power control commands and the time-domain and / or frequency-domain resources to which the UE needs to apply the power control commands. Because more information needs to be carried, more sequence, preamble, or reference signal initializers can be configured for different assumptions. The UE can perform blind cross-correlation for more possible scenarios to detect and determine the information accordingly.

[0200] After UE1 performs a broadcast-side link transmission at a reduced power level, UE1 can perform a retransmission. UE1 can retransmit the entire TB, or UE1 can retransmit only the portion with reduced power applied, such as overlapping symbols, PRB, or CBG.

[0201] In one scenario, retransmission scheduling can be jointly indicated along with indications for reducing power, such as... Figure 7 As shown. For example, UE1 may receive a retransmission schedule (e.g., via DCI format 0_1) before it performs its scheduled initial transmission. In this case, UE1 can determine that the scheduled initial transmission has been preempted. UE1 will transmit the preempted initial transmission using a reduced power level and perform a retransmission as scheduled.

[0202] Alternatively, in another case, the scheduling of retransmissions can be indicated separately from the indication for reducing power, such as... Figure 8As shown. UE1 can first monitor to detect if it has been preempted. If the UE detects a power reduction indication (e.g., a published sequence, preamble, reference signal, or DCI), the UE determines that it has been preempted and reduces its transmission power. The UE can then monitor the retransmission schedule and perform retransmissions according to the schedule.

[0203] Furthermore, an instruction can be sent to the receiving UE to notify it not to perform soft recombination of data preempted during the initial transmission or all received data. Schemes disclosed in preemption during Uu transmission using higher power can also be applied here.

[0204] Figure 9 The present paper illustrates an example of a public procedure for detecting a power reduction indicator for a sidelink UE that has an inter-UE conflict with a scheduled Uu transmission. The UE receives a schedule for a broadcast sidelink transmission (901). The UE monitors to detect whether a power reduction indicator has been sent (902). When the UE detects a power reduction indicator (903), it performs a broadcast sidelink transmission at reduced power (904). If it does not detect a power reduction indicator (903), it performs a broadcast sidelink transmission as scheduled (908). The UE determines whether a retransmission schedule has been detected along with the detection result of the power reduction indicator (905). If yes, the UE transmits at normal power (906). If no, the UE monitors the retransmission schedule and retransmits at normal power (907). A cancellation indicator is used to preempt a low-priority SL transmission.

[0205] In the third alternative scenario, UE1 can monitor for preemption before executing a broadcast sidelink transmission. If preemption occurs, the gNB can send a cancellation indication, such as SL-CI (Sidelink Cancellation Indication), instructing UE1 to cancel the scheduled transmission. By detecting this indication, UE1 will not execute all or part of the scheduled transmission. If the cancellation indication is detected, the PHY can send an indication to the upper layer, such as a canceled MAC address.

[0206] In one scenario, a UE can be instructed to cancel transmissions on all allocated resources regardless of whether they fully or partially overlap with conflicting Uu transmissions; for example, a UE can cancel a transmission on an entire TB. Similar to detecting a power reduction indicator, a UE can detect a cancellation instruction by: receiving a UE-specific DCI; receiving a group-wide DCI; detecting a pre-configured reference signal; detecting a pre-configured preamble; or detecting a pre-configured sequence, such as a new reference signal carried by some REs from the physical signal. When multiple panels are used for transmission, the UE can be instructed to cancel transmissions on one or more panels. For example, if a UE is scheduled to broadcast using a panel in the front bumper aimed at the front and a panel in the rear bumper aimed at the rear, the UE can be instructed not to use the panel in the front bumper for broadcasting because it has been preempted. For example, the DCI indicating a power reduction indicator can carry a panel index field to indicate to the UE which panels have been preempted.

[0207] In another scenario, the UE can be instructed to cancel transmissions on a subset of the allocated resources, for example, canceling transmissions on overlapping symbols and / or PRBs, or canceling transmissions on CBGs that overlap with the canceled resources. Similar to a power reduction detection indication, a UE-specific DCI or a group-wide DCI can be used. For example, a new DCI format can be introduced where a group-specific RNTI is scrambled with CRC, for example, an RNTIpg can be configured for a group of UEs. Such a DCI can carry fields indicating which time-domain resources the UE can consider preempted and cancel transmissions, for example, a 14-bit bitmap where each bit represents one symbol or a 7-bit bitmap where each bit represents two symbols in a time slot; and / or fields indicating which frequency resources the UE can consider preempted and cancel transmissions, for example, via a bitmap.

[0208] When the UE detects a DCI that scrambles the configured RNTIPg during its monitoring period, the UE can determine that it has been preempted and cancel the transmission on the indicated time and / or frequency resources.

[0209] Alternatively, sequences, preambles, and reference signals can be used to indicate to the UE that it needs to cancel time-domain and / or frequency-domain resources for a scheduled transmission. For example, the UE can be configured with k different sequence initializers via an RRC used to generate the reference signal sequence, where each initializer is associated with some configurable time-domain and / or frequency-domain resources. An example is shown in Table 2, where each initializer represents a different time-domain resource (assuming symbol 0 is the first symbol in the time slot). The UE can be configured with all the initializers shown in the table, or a subset of the listed initializers. Based on the reference signal sequence detected through blind cross-correlation, the UE can determine the time-domain and / or frequency-domain resources required to cancel its transmission.

[0210] Table 2 shows the different initializer values ​​configured for the UE, used to determine the resources on which transmissions need to be cancelled.

[0211]

[0212]

[0213] After UE1 cancels a scheduled broadcast-side link transmission, UE1 may retransmit the entire TB or it may retransmit only the canceled portion, such as overlapping symbols, PRBs, or CBGs.

[0214] In such Figure 7 and Figure 8 Similar concepts disclosed in the power reduction indicator shown can be applied here. Retransmission scheduling can be indicated jointly with a cancellation indication. Alternatively, retransmission scheduling can be indicated separately from the cancellation indication. For example, a cancellation indication can be signaled via a group common DCI (e.g., a DCI with a CRC scrambled with RNTIPg) before the scheduled transmission; and after cancellation occurs, retransmission can be scheduled via a UE-specific DCI (e.g., a DCI with a CRC scrambled with C-SL-RNTI).

[0215] Furthermore, an indication can be sent to the receiving UE to notify that data preempted during the initial transmission or all received data will not be soft-combined. The scheme disclosed in the alternative case of preemption using a higher-power Uu transmission can also be applied here.

[0216] Figure 10The present paper illustrates an example of a public procedure for detecting a cancellation indication for a sidelink UE that has an inter-UE conflict with a scheduled Uu transmission. The UE receives the scheduling of the broadcast sidelink transmission (1001) and monitors whether a cancellation indication has been sent (1002). The UE monitors the cancellation indication (1002) and determines whether it has detected the cancellation indication (1003). If not detected, it performs the broadcast sidelink transmission as scheduled (1008). If the UE detects the cancellation indication, it cancels the transmission indicated in the cancellation indication (1004). The UE determines whether a retransmission schedule has been detected along with the cancellation indication (1005), and if so, the UE performs a retransmission (1006); if not, the UE monitors the retransmission schedule and performs a retransmission (1007).

[0217] The dynamically scheduled Uu transmission preempts the dynamically scheduled unicast link transmission.

[0218] This section outlines solutions for conflicts between dynamically scheduled Uu transmissions and dynamically scheduled unicast-side link transmissions. In unicast scenarios, the Tx UE will receive ACK / NACK feedback from the Rx UE. The Uu transmissions discussed in this paper can be either downlink or uplink transmissions.

[0219] Assume UE1 is dynamically scheduled by the gNB to transmit unicast transmissions on a sidelink as a Tx UE; UE2 is an Rx UE that will receive unicast sidelinks from UE1; and assume UE3 is dynamically scheduled by the gNB to have transmissions or receptions (e.g., PDSCH or PUSCH) on the Uu interface, where some or all of the resources allocated to UE3 overlap temporally with the resources allocated to UE1. To handle inter-UE conflicts, we disclose unicast sidelink transmissions that may be preempted under the following alternative scenarios.

[0220] Use higher power Uu transmission preemption

[0221] In the first alternative scenario, UE1 will perform unicast sidelink transmission regardless of whether it receives a preemption.

[0222] To ensure the transmission / reception of UE3, a similar scheme proposed in the case of dynamically scheduled broadcast side links is used, which can perform Uu transmission at a higher power level compared to the power level used in scenarios without inter-UE conflicts.

[0223] For Tx UEs, after UE1 performs a unicast sidelink transmission, it will monitor feedback sent by UE2 via PSFCH, such as ACK / NACK. UE1 can also monitor indications sent by gNB to determine whether its transmission has been preempted, where the timing of monitoring can be configured by RRC.

[0224] In one scenario, UE1 might receive an ACK from UE2 but not detect a preemption indication from the gNB. UE1 can then determine that the transmission was successful and can flush its buffer.

[0225] In another scenario, UE1 might receive an ACK from UE2 and detect a preemption indication from the gNB. UE1 can then determine that although it was preempted, the transmission was still successful, and it can flush its buffer.

[0226] In another scenario, UE1 might receive a NACK from UE2 and detect a preemption indication from the gNB. UE1 can then determine that the transmission failed due to preemption. UE1 can perform a retransmission and send preemption information to UE2 to instruct UE2 to refresh its buffer accordingly. The scheme disclosed in the alternative case of preemption using a higher-power Uu transmission in a broadcast scenario can also be applied here.

[0227] In another scenario, UE1 can receive a NACK from UE2 and detect a preemption indication from the gNB, where the gNB can send preemption indications to both the Tx UE and the Rx UE. UE1 can then determine that the transmission failed due to preemption. UE1 can then perform a retransmission without sending preemption information to UE2.

[0228] In another scenario, UE1 can receive NACK and preemption information from UE2, for example, via the CBGFI field in the SFCI. For instance, UE2 can receive a preemption indication from the gNB. It can correspondingly flush its buffer. UE2 can send a bitmap from the SFCI to UE1 to indicate the preempted resource. When UE1 receives such information, UE1 can determine that the transmission failed due to preemption. UE1 can then perform a retransmission.

[0229] When a conflict occurs between UEs, on the one hand, the gNB can allocate resources for retransmission to UE1 without receiving feedback from UE1. UE1 can determine whether to perform a retransmission based on feedback from the Rx UE. For example, if it receives an ACK from UE2, UE1 can ignore retransmission scheduling; or if it receives a NACK from UE2, UE1 can use the allocated resources to perform a retransmission. Alternatively, on the other hand, the gNB can allocate resources for retransmission based on feedback from UE1. UE1 can send an indication, such as an SR or BSR, to the gNB based on feedback from the Rx UE to indicate whether retransmission scheduling is required. For example, when UE1 receives an ACK from UE2, UE1 can indicate to the gNB that retransmission scheduling is not required. When UE1 receives a NACK from UE2, UE1 can indicate to the gNB that retransmission scheduling is required. Instructions can be explicit, for example, sending instruction 'A' means retransmission is required, and sending instruction 'B' means retransmission is not required; or instructions can be implicit, for example, sending instruction 'C' means retransmission is required, and not sending instruction 'C' means retransmission is not required.

[0230] When UE1 does perform a retransmission, it can retransmit the entire TB or it can retransmit only a subset of the TB, such as preempted symbols, PRBs, or CBGs.

[0231] Figure 11 Example of a public procedure for Tx UE to detect preemption for a sidelink UE with inter-UE conflict with a scheduled Uu transmission is shown. The UE receives the scheduling of the unicast sidelink transmission (1101). The UE performs the unicast sidelink transmission on the scheduled resource (1102). The UE monitors for ACK or NACK from the Rx UE (1103). The UE determines whether it has received ACK or NACK from the Rx UE (1104). The UE monitors for transmitted preemption indications (1105). The UE determines whether it has detected preemption (1106). If preemption is detected, the UE retransmits and sends the preemption information to the Rx UE (1108). If not, the Tx UE retransmits (1107). If the Tx UE does receive ACK or NACK, it sends and flushes its buffer (1109).

[0232] For Rx UEs, UE2 can attempt to decode the transmitted data and send feedback to UE1. When UE2 is unable to decode the data, it can send a NACK to UE1.

[0233] In one scenario, UE2 can receive retransmissions but not any preemption indication. For the same HARQ processing ID, UE2 can soft-combine the received retransmissions with the data in the buffer.

[0234] In another scenario, UE2 can receive retransmissions and preemption indications from UE1. UE2 can then flush its buffer and decode the retransmission. If the initial transmission was partially preempted, the UE can flush only the preempted portion of its buffer. For example, the UE can soft-combine the retransmission with the first portion of the soft buffer, but not with the second portion, which may correspond to the preempted resource; therefore, the UE can flush the second portion of the soft buffer.

[0235] In another scenario, UE2 can receive retransmissions from UE1 and receive preemption instructions from the gNB. UE2 can then flush its buffer and decode the retransmissions.

[0236] In another scenario, UE2 can receive a preemption indication from the gNB before sending HARQ feedback to UE1. UE2 can then flush its buffer and send the preemption information along with the HARQ feedback.

[0237] Figure 12 Example of a public procedure for Rx UE to detect preemption for a sidelink UE with inter-UE conflict with a scheduled Uu transmission is shown. The Rx UE receives a unicast sidelink preemption schedule (1201). The UE determines whether the received data has been successfully decoded (1202). If yes, the UE sends an ACK and flushes its buffer (1206). If no, the Rx UE determines whether preemption has been detected (1203). If yes, it flushes its buffer for the resource indicated as preempted and decodes the retransmission (1205). If no, the Rx UE decodes the retransmission via soft combination (1204).

[0238] For retransmission scheduling, such as Figure 3 , Figure 4 , Figure 5 The scheme shown for dynamically scheduled broadcast publics can also be applied here.

[0239] Use adjusted transmission control parameters to preempt low-priority SL transmissions.

[0240] In the second alternative scenario, the gNB can send an indication instructing UE1 to adjust its transmission control parameters before UE1 performs the scheduled initial unicast transmission. The concept of how to send power reduction indicators for dynamically scheduled broadcast-side links can also be applied here. The gNB can send the power reduction indicator only to the Tx UE, or the gNB can send the power reduction indicator to both the Tx UE and the Rx UE. For retransmission scheduling, such as... Figure 7 and Figure 8 The proposed scheme for dynamically scheduled broadcasts shown can also be applied here.

[0241] For a Tx UE, upon detecting a power reduction indicator, UE1 can rewrite the old TPC and transmit the scheduled unicast-side link with the new transmit power. It will then monitor feedback from UE2 via the PSFCH, such as ACK / NACK.

[0242] The Tx UE behavior and retransmission allocation methods disclosed in the alternative scenario of using higher-power Uu transmission preemption can also be applied here.

[0243] Figure 13 Example of a public procedure for a Tx UE to detect a power reduction indicator for a sidelink UE that has an inter-UE conflict with a scheduled Uu transmission is shown. The UE receives the scheduling of the unicast sidelink transmission (1301). The UE monitors whether a power reduction indicator has been sent (1302). The UE determines whether a power reduction indicator has been detected (1303). If yes, the UE performs the unicast sidelink transmission at reduced power and receives feedback from the Rx UE (1304). The UE determines whether it has received an ACK (1305). If yes, it sends and refreshes its buffer (1307). If no, the UE retransmits and sends preemption information to the Rx UE (1306). If the Tx UE does not detect the received power reduction indicator, it performs the unicast sidelink transmission as scheduled (1308).

[0244] For Rx UEs, UE2 can attempt to decode the transmitted data and send feedback to UE1. When UE2 is unable to decode the data, it can send a NACK to UE1.

[0245] The Rx UE behavior disclosed in the alternative scenario of using higher-power Uu transmission preemption can also be applied here.

[0246] Figure 14 Example of a public procedure for an Rx UE to detect a power reduction indicator for a sidelink UE with inter-UE conflicts to a scheduled Uu transmission is shown in the document. The Rx UE receives the scheduling of a unicast sidelink transmission (1401). The UE determines whether it has detected a power reduction indicator (1402). If yes, it determines whether the received data has been successfully decoded (1403). If yes, it sends an ACK and flushes its buffer (1404). If no, it flushes the buffer of the preempted resource and decodes the retransmission (1405). If the UE has not detected a power reduction indicator, it determines whether the received data has been successfully decoded (1406). If yes, it sends an ACK and flushes its buffer (1407). If no, the UE decodes the retransmission via soft combination (1408).

[0247] Use the cancel indicator to preempt low-priority SL transfers.

[0248] In the third alternative scenario, UE1 can monitor for preemption before performing a unicast sidelink transmission. If preemption occurs, the gNB can send a cancellation indication, thereby instructing UE1 to cancel the scheduled transmission.

[0249] The scheme for sending cancellation indications publicly available for dynamically scheduled broadcast-side links can also be applied here. The gNB can send a cancellation indication only to the Tx UE, or it can send cancellation indications to both the Tx UE and the Rx UE. For retransmission scheduling, such as... Figure 7 and Figure 8 The proposed scheme for dynamically scheduled broadcasts shown can also be applied here.

[0250] For Tx UEs, upon detecting a cancellation indication, UE1 will not perform all or part of the scheduled transmission as indicated, and will retransmit later.

[0251] In one scenario, UE1 can retransmit and send the preemption information to UE2, instructing UE2 to refresh its buffer accordingly. The scheme disclosed in the alternative case of preemption using a higher-powered Uu transmission can also be applied here.

[0252] In another scenario, the gNB can send a cancellation indication to both the Tx UE and the Rx UE. UE1 can then retransmit without sending a preemption message.

[0253] In another scenario, if UE1 detects a cancellation indication before sending an SCI (e.g., Phase 1) for a scheduled sidelink transmission, UE1 cannot send an SCI to UE2 (e.g., both Phase 1 and Phase 2 SCIs). Alternatively, if an SCI (e.g., Phase 1 SCI) has already been sent when the cancellation indication is detected, UE1 can send another indication to UE2 to ignore the sidelink transmission indicated by the previous SCI. This indication can be a reference signal, preamble, sequence, or SCI, for example, using the preemption indication field in a Phase 2 SCI.

[0254] When there is a time interval between the transmission of the first-stage SCI and the second-stage SCI, the examples provided for the above situations can be applied. In another example, the first-stage SCI and the second-stage SCI can be transmitted without any time interval between them; for example, the first-stage SCI and the second-stage SCI can be frequency-division multiplexed (FDM) and transmitted with data; or the first-stage SCI and the second-stage SCI can be transmitted in consecutive symbols, etc. In this case, the Tx UE (e.g., UE1) cannot detect and cancel the cancellation indication of the initial transmission. However, the Tx UE can monitor and detect cancellation indications for reserved retransmissions (e.g., retransmissions based on repetition or HARQ); or cancellation indications for reserved periodic transmissions. UE1 can send another indication to UE2 for ignoring sidelink transmissions indicated by the previous SCI, such as reserved retransmissions or reserved periodic transmissions. Such an indication (e.g., a preemption indication field) can be carried by the first-stage SCI or can be carried by the second-stage SCI.

[0255] For example, the preemption indication field in the second-stage SCI can be a single field, where '1' indicates that the scheduled sidelink transmission has been preempted; and '0' indicates that the scheduled sidelink transmission has not been preempted, and vice versa.

[0256] In one example, when a Tx UE detects that a scheduled sidelink transmission on the PSSCH has been preempted by another transmission, the Tx UE can discard the PSSCH transmission. The Tx UE can simply send the second-stage SCI (or a symbol carrying the second-stage SCI) and set the preemption indicator field to "1". When the Rx UE decodes the received second-stage SCI and determines that the preemption indicator field is set to "1", the Rx UE can determine that the associated PSSCH transmission has been preempted and will not soft-combine it with other transmissions in the same TB.

[0257] In another example, a Tx UE may discard both the second-stage SCI transmission and the associated PSSCH transmission. When an Rx UE fails to decode the second-stage SCI that should have been sent in the resource indicated by the first-stage SCI, the Rx UE will not be able to decode the associated PSSCH and will not soft-combine it with other transmissions in the same TB.

[0258] In yet another example, the Tx UE can discard both the transmission of the second-stage SCI and the associated PSSCH, and instead use the resources indicated by the first-stage SCI that should have been used to transmit the second-stage SCI to send the indication. This indication can be a pre-configured reference signal, a pre-configured preamble, or a pre-configured sequence. For example, the Rx UE can be configured with an initializer value, such as c. init,CIWhen an Rx UE detects that a pre-configured reference signal / sequence is being transmitted on a resource where the second-stage SCI should be sent, the Rx UE can determine that the associated PSSCH has failed and not soft-combine it with other transports in the same TB.

[0259] When a Tx UE detects that the transmission of the second-stage SCI is preempted by other transmissions, the Tx UE can discard both the second-stage SCI transmission and the associated PSSCH transmission.

[0260] The scheme disclosed here for unicast sidelink transmission can also be applied to broadcast sidelink transmission and multicast sidelink transmission.

[0261] When UE1 does perform a retransmission, it can retransmit the entire TB or it can retransmit only a subset of the TB, such as preempted symbols, PRBs, and / or CBGs.

[0262] Figure 15 Example of a public procedure for a Tx UE to detect a cancellation indication is shown for a sidelink UE that has an inter-UE conflict with a scheduled Uu transmission. The Tx UE receives the scheduling of a unicast sidelink transmission (1501). The UE monitors for a cancellation indication (1502). The UE determines whether it has detected a cancellation indication (1503). If not, the UE performs the unicast sidelink transmission as scheduled (1506). If yes, the UE cancels the transmission indicated in the cancellation indication (1504). The UE retransmits without sending preemption information to the Rx UE (1505).

[0263] In one scenario, for an Rx UE, UE2 can receive a cancellation indication from the gNB. Depending on when the cancellation indication is received, UE2 can either ignore the scheduled sidelink transmission or flush the buffer of the cancelled resource during decoding and retransmission.

[0264] In another scenario, UE2 can receive retransmissions and preemption indications from UE1. UE2 can then flush its buffer and decode the retransmissions.

[0265] In another scenario, UE2 may receive an indication from UE1 to ignore a scheduled sidelink transmission because it has been canceled by the gNB. UE2 can then ignore previously received SCIs and not attempt to decode the data. Alternatively, an indication from UE1 may suggest that some resources in the scheduled sidelink transmission have been preempted. UE2 can then flush its buffer and decode the retransmission.

[0266] Figure 16The document presents an example of a public procedure for an Rx UE to detect a cancellation indication for a sidelink UE that has an inter-UE conflict with a scheduled Uu transmission. The Rx UE receives a scheduling of a unicast sidelink transmission (1601). The UE determines whether a cancellation indication was detected before the scheduled transmission occurred (1602). If not, the Rx UE determines whether the received data was successfully decoded (1603). If yes, the UE sends an ACK and flushes its buffer (1604). If not, the UE sends a NACK and receives a retransmission (1605). The UE then decodes the retransmission via soft combination (1607). If a cancellation indication was detected before the scheduled transmission occurred (1602), the Rx UE ignores the scheduled unicast sidelink reception (1608) and receives a retransmission (1609). The dynamically scheduled Uu transmission preempts the dynamically scheduled multicast sidelink transmission.

[0267] This section discloses a solution to the conflict between dynamically scheduled Uu transmissions and dynamically scheduled multicast sidelink transmissions. In multicast scenarios, a Tx UE needs to send data to multiple Rx UEs and receive ACK / NACK from all or some of the Rx UEs. Since the channels between Tx and Rx UEs within a group may differ, for a single multicast transmission, some Rx UEs may successfully decode it, while others may not. The Uu transmission described in this paper can be a downlink transmission or a dual uplink transmission.

[0268] Assume UE1 is dynamically scheduled by the gNB to transmit multicast traffic on a sidelink as a Tx UE; UE2,1, UE2,2…UE2,k are Rx UEs that will receive multicast sidelink traffic from UE1; and assume UE3 is dynamically scheduled by the gNB to have transmission or reception (e.g., PDSCH or PUSCH) on the Uu interface, where some or all of the resources allocated to UE3 overlap temporally with the resources allocated to UE1. To handle inter-UE conflicts, multicast sidelink traffic can be preempted under the following alternative scenarios.

[0269] Use higher power Uu transmission preemption

[0270] In the first alternative scenario, UE1 will perform multicast sidelink transmission regardless of whether it receives a preemption.

[0271] To maintain the performance of transmitting / receiving higher priority data to / from UE3, a similar scheme proposed in the case of dynamically scheduled broadcast sidelinks is used, which can perform Uu transmission at a higher power level compared to the power level used in scenarios without inter-UE conflicts.

[0272] For Tx UEs, after UE1 performs multicast sidelink transmission, it will monitor feedback sent by Rx UEs via PSFCH, such as ACK / NACK. UE1 can also monitor indications sent by gNBs to determine if its transmission has been preempted, where the timing of monitoring can be configured by RRC.

[0273] When UE1 sends a multicast message, one beam can be used to multicast the message to all Rx UEs.

[0274] The Tx UE behavior disclosed in the alternative scenario of using higher-power Uu transmission preemption can also be applied here together with the feedback sent by the scheduled Rx UE.

[0275] When UE1 sends a multicast message, multiple beams can be used to multicast the message to Rx UEs in different directions, where the different beams are time-, frequency-, and / or spatially multiplexed. UE1 can monitor and detect whether each beam is preempted separately via explicit or implicit signaling. For example, a bitmap can be used to indicate which beams are preempted. Alternatively, if the beams are time-division multiplexed (TDM) and / or frequency-division multiplexed (FDM), the UE can determine preemption based on the preempted time and frequency resources. The procedures and behaviors for multicasting using a beam can also be applied here.

[0276] When UE1 performs a retransmission, it can retransmit the entire TB or only a subset of the TB, such as preempted symbols, PRBs, or CBGs. When multiple beams are used for multicast, UE1 can retransmit multicast messages on all beams or it can retransmit multicast messages on the preempted beam.

[0277] When a conflict occurs between UEs, the gNB can allocate resources for retransmission to UE1 without receiving feedback from UE1. Alternatively, the gNB can allocate resources for retransmission based on feedback from UE1. The same scheme proposed in the alternative case of detecting preemption after the initial transmission of unicast can also be applied here.

[0278] Figure 17Example of a public procedure for a Tx UE to detect preemption indication for a sidelink UE that has an inter-UE conflict with a scheduled Uu transmission is shown. The Tx UE receives the scheduling of a multicast sidelink transmission (1701). The Tx UE performs a multicast sidelink transmission on the scheduled resource using beams 1, 2, and 3 (1702). The Tx UE receives feedback from the Rx UE (1703). The Tx UE determines whether the transmission on the three beams was successful (1704). If yes, the Tx UE's transmission is successful and its buffer is flushed (1708). If no, the Tx UE determines whether it detected preemption (1705). If no, the Tx UE retransmits its transmission for the failed beam (1706). If yes, the Tx UE retransmits and sends preemption information about the failed beam (1707).

[0279] For an Rx UE that successfully decodes a multicast message, the Rx UE can ignore subsequent scheduling of retransmissions for failed UEs.

[0280] For Rx UEs that fail to decode messages, the disclosed Rx UE behavior for preempting the use of higher-power Uu transmission in unicast scenarios can also be applied here.

[0281] Figure 18 Example of a public procedure for Rx UE to detect preemption in a sidelink UE with inter-UE conflict with a scheduled Uu transmission is shown. The Rx UE receives the multicast sidelink reception schedule (1801). The Rx UE determines whether its received data has been successfully decoded (1802). If yes, if the UE is scheduled to send feedback, it sends an ACK, flushes its buffer, and ignores the retransmission schedule (1809). If no, the UE determines whether it has detected preemption (1803). If no, if it is scheduled to send HARQ feedback, it sends the preemption information along with the HARQ feedback and decodes the retransmission via soft combination (1807). If the UE does detect preemption (1803), the UE determines whether it is scheduled to send HARQ feedback (1804). If yes, the Rx UE sends the preemption information along with the HARQ feedback, flushes its buffer, and decodes the retransmission (1805). If the Rx UE determines that it is not scheduled to send HARQ feedback (1804), the Rx UE flushes its buffer and decodes and retransmits (1806).

[0282] For retransmission scheduling, such as Figure 3 , Figure 4 , Figure 5 The proposed scheme for dynamically scheduled broadcasts shown can also be applied here.

[0283] Preempt low-priority SL transmissions using adjusted transmission control parameters.

[0284] In the second alternative scenario, the gNB can send an indication instructing UE1 to adjust its transmission control parameters before UE1 performs the scheduled initial multicast transmission. The scheme for sending power reduction indicators publicly available for dynamically scheduled broadcast-side links can also be applied here. The gNB can send the power reduction indicator only to the Tx UE, or the gNB can send the power reduction indicator to both the Tx UE and the Rx UE. For retransmission scheduling, such as... Figure 7 and Figure 8 The proposed scheme for dynamically scheduled broadcasts shown can also be applied here.

[0285] The Tx UE behavior disclosed in the alternative scenario of using higher-power Uu transmission preemption in multicast scenarios can also be applied here.

[0286] When multiple beams are used to multicast messages to Rx UEs in different directions, UE1 can monitor and detect whether each beam is preempted separately. Assume three beams are used in the multicast. For example, if beam 1 is preempted while beams 2 and 3 are not, UE1 can reduce the transmission power only on beam 1. The procedures and behaviors for multicasting using a single beam can also be applied here.

[0287] Figure 19 Example of a public procedure for a Tx UE to detect a power reduction indicator for a sidelink UE that has inter-UE conflicts with a scheduled Uu transmission is shown. The Tx UE receives a schedule for multicast sidelink transmissions on beams 1, 2, and 3 (1901). The UE monitors whether a power reduction transmission has been sent (1902). The UE determines whether it has detected a power reduction indicator (1903). If not, the UE performs the multicast sidelink transmission as scheduled (1908). If yes, and the UE detects that beam 1 has been preempted, the UE reduces the power used for transmissions on beam 1 and performs transmissions on beams 2 and 3 as scheduled (1904). The Tx UE determines whether the multicast on beam 1 was successful (1905). If yes, the UE sends the transmission and refreshes its buffer (1907). If no, the UE retransmits and sends preemption information to the Rx UE (1906).

[0288] The Rx UE behavior disclosed in the alternative scenario of using higher-power Uu transmission preemption can also be applied here.

[0289] Figure 20Example of a public procedure for an Rx UE to detect a power reduction indicator for a sidelink UE with inter-UE conflicts with a scheduled Uu transmission is shown in the document. The Rx UE receives a schedule for a unicast sidelink transmission (2001). The UE determines whether it has detected a power reduction indicator (2002). If not, the UE determines whether its received data has been successfully decoded (2003). If not, the UE decodes the retransmission via soft combination (2005). If yes, if the UE is scheduled to send an ACK, it sends an ACK, flushes its buffer, and ignores the retransmission schedule (2004). If the Rx UE determines (2002) that it has not detected a power reduction indicator, the Rx UE determines whether its received data has been successfully decoded (2006). If yes, if the Rx UE is scheduled to send an ACK, it sends an ACK, flushes its buffer, and ignores the retransmission schedule (2007). If no, the Rx UE flushes its preempted resource buffer and decodes the retransmission (2008).

[0290] Use the adjusted transmission control parameters to cancel the indicator and preempt low-priority SL transmissions.

[0291] In the third alternative scenario, UE1 can monitor to detect whether it has been preempted before performing a multicast sidelink transmission. If preemption occurs, the gNB can send an indication to instruct UE1 to cancel the scheduled transmission and, in some cases, also to indicate the preemption to the UE receiving the SL.

[0292] The scheme for sending cancellation indications publicly available for dynamically scheduled broadcast-side links can also be applied here. The gNB can send a cancellation indication only to the Tx UE, or it can send a cancellation indication to both the Tx UE and the Rx UE. For retransmission scheduling, such as... Figure 7 and Figure 8 The proposed scheme for dynamically scheduled broadcasts shown can also be applied here.

[0293] For Tx UEs, upon detecting a cancellation indication, UE1 will not perform all or part of the scheduled transmission as indicated and will retransmit it later.

[0294] When UE1 sends a multicast message, a beam can be used to multicast the message to all Rx UEs.

[0295] The Tx UE behavior disclosed in the alternative scenario of using higher-power Uu transmission preemption in multicast scenarios can also be applied here.

[0296] In addition to the disclosed Tx UE behavior, if UE1 detects a cancellation indication before sending an SCI for a scheduled sidelink transmission, UE1 cannot send the SCI to the Rx UE. Alternatively, if the SCI has already been sent when the cancellation indication is detected, UE1 can send another indication to the receiving UE to ignore the sidelink transmission indicated by the previous SCI.

[0297] When UE1 sends multicast messages, multiple beams can be used to multicast Rx UE messages in different directions. UE1 can monitor and detect whether each beam is preempted separately. Assume three beams are used in the multicast. For example, if beam 1 is preempted while beams 2 and 3 are not, UE1 can cancel transmissions only on beam 1. The procedures and behaviors for multicast broadcasts using a single beam can also be applied here.

[0298] Figure 21 Example of a public procedure for a Tx UE to detect a cancellation indication for a sidelink UE that has an inter-UE conflict with a scheduled Uu transmission is shown. The Tx UE receives the scheduling of the multicast sidelink transmission (2101). The UE monitors whether a cancellation indication has been sent (2102). The UE determines whether it has detected a cancellation indication (2103). If not, the UE performs the multicast sidelink transmission as scheduled (2109). If yes, the UE cancels the transmission indicated in the cancellation indication (2104). The UE determines whether there is sufficient time to forward the cancellation indication to the Rx UE before the initial scheduled transmission (2105). If not, the Tx UE retransmits and sends preemption information to the Rx UE (2106). If yes, the Tx UE sends an indication to the Rx UE to ignore the scheduled multicast transmission (2107) and it retransmits (2108).

[0299] For Rx UEs, in one scenario, the Rx UE can receive a cancellation indication from the gNB and can ignore the scheduled sidelink transmission, or it can refresh the buffer of the cancelled resource during decoding and retransmission.

[0300] In another scenario, the Rx UE can receive retransmissions and preemption indications from UE1. The Rx UE can flush its buffer and decode the retransmissions.

[0301] In another scenario, the Rx UE can receive an indication from UE1 to ignore a scheduled sidelink transmission because it has been canceled by the gNB. The Rx UE can ignore previously received SCIs and not attempt to decode the data. Alternatively, an indication from UE1 can indicate that some resources in the scheduled sidelink transmission have been preempted. The Rx UE can flush its buffer and decode the retransmission.

[0302] Figure 22 Example of a public procedure for detecting cancellation indication for an Rx UE is shown for a sidelink UE with inter-UE conflict with a scheduled Uu transmission. The Rx UE receives scheduling for unicast sidelink reception (2201). The UE determines whether its received data has been successfully decoded (2202). If yes, the UE sends an ACK and flushes its buffer (2207). If no, the UE sends a NACK if it is scheduled to send feedback (2203). The UE determines whether it received preemption information along with retransmissions (2204). If no, the UE decodes the retransmissions via soft combination (2205). If yes, the Rx UE flushes its buffer for the preempted resource and decodes the retransmissions (2206).

[0303] Uu transport preempts sidelink transport based on configuration authorization

[0304] This section discloses a solution for the scenario where sidelink transmissions based on configuration authorization are preempted by dynamically scheduled Uu transmissions. The Uu transmissions in this paper can be either downlink or uplink transmissions.

[0305] When resources are allocated to a UE through configuration grants for sidelink transmissions, the allocated resources can be dedicated exclusively to that UE. For example, time and frequency resources may be allocated to only one UE as configuration grants. Simultaneously, the gNB will not schedule any other SL or Uu transmissions on these resources. Alternatively, the allocated resources can be shared with other UEs. For example, the gNB can schedule another high-priority Uu or SL transmission on these resources as needed. The same time and frequency resources can also be allocated to multiple UEs as configuration grants. If the allocated resources are dedicated to a single UE, the UE does not need to worry about inter-UE conflicts. However, when the allocated resources are shared with other UEs, the UE may experience inter-UE conflicts when using the configuration-granted resources to perform sidelink transmissions.

[0306] For example, in configuration grant type 1, the RRC configuration in the configuration grant can carry RRC parameters to indicate to the UE whether the configuration grant is shared with other UEs or dedicated to the UE itself. For example, the RRC parameter ConfiguredGrantShared can be used with possible values ​​"yes" and "no"; or the RRC parameter ConfiguredGrantSharingStatus can be used with possible values ​​"shared" and "dedicated".

[0307] In configuration authorization type 2, such indication can be provided by RRC or activated DCI. When using RRC, the scheme proposed for configuration authorization type 1 also applies to configuration authorization type 2. Alternatively, when using activated DCI, a new field can be introduced in the activated DCI for this purpose. Examples of shared status indicator fields are shown in Table 3. Alternatively, a bit can be used in this field, where '0' indicates that the activated resource is dedicated to the UE; and '1' indicates that the activated resource is shared with other transmissions.

[0308] In the various embodiments described herein, sidelink configuration authorization types 1 and 2 may be equivalent to Uu UL configuration authorization types 1 and 2; or Uu UL configuration authorization types 1 and 2 may be used as a baseline, but with potential enhancements.

[0309] Table 3. Shared Status Indicator Field in Activated DCI

[0310]

[0311] When a UE is configured / indicated to have a dedicated configuration authorization, it can directly transmit data on the configured CG resources when it has data to send. On the other hand, when a UE is configured / indicated to have a shared configuration authorization, it can apply the proposed inter-UE conflict handling scheme when it has data to send on the authorized resources.

[0312] In an alternative scenario, whenever it performs scheduling (where some of the resources overlap with resources at a configuration grant timing (e.g., configuration grant timing k), the gNB may send an indication (e.g., a cancellation indicator) to indicate a potential inter-UE conflict. This indication could be a preemption indication as disclosed in previous sections, a power reduction indicator, or a cancellation indication. Simultaneously, a UE with configuration grant may have data to transmit at configuration grant timing k; or the UE may not have data to transmit.

[0313] If any UE determines that it will send data at the configured authorization time k, the UE can (e.g., before performing a sidelink transmission) monitor and detect the indication sent by the gNB. The UE can then determine that it has been preempted and handle this issue of broadcast, multicast, and unicast using the procedures published for handling inter-UE conflicts between dynamically scheduled Uu transmissions and dynamically scheduled sidelink transmissions. In general, the schemes proposed for dynamically scheduled broadcast, multicast, and unicast can also be applied here.

[0314] In one example, when a Tx UE is configured to transmit multiple duplicates of the same TB using a configured authorized resource on a sidelink, and the Tx UE detects (e.g., by detecting and decoding a cancellation indicator) that one or more of these duplicates are preempted by other transmissions, the Tx UE cannot transmit the preempted duplicate(s) (e.g., duplicates overlapping with the cancelled resource), while still transmitting the unpreempted duplicate(s). The Tx UE can then monitor feedback from the Rx UE (e.g., ACK / NACK feedback) to determine if the transmission was successful. If the transmission fails, the Tx UE can send an indication to the gNB to request a retransmission schedule; for example, this indication could be a NACK feedback.

[0315] When all duplicates are preempted, the UE can discard all duplicate transmissions and send an indication to the gNB to request retransmission scheduling. An example of the disclosed procedure is... Figure 23 As shown in the diagram. The UE receives information about the configuration grant resources for sidelink transmission (2301). The UE determines whether the configuration grant is dedicated to the UE (2302). If yes, the UE uses the configuration grant when it has data to send (2311). If no, the UE determines whether it has data to send at the next configuration grant time (2303). If yes, the UE monitors and detects whether it has been preempted (2304). The UE monitors to detect preemption (2304). The UE determines whether preemption has been detected (2305). If no, the UE sends data at the next configuration grant time (2310). If preemption is detected (2305), the UE determines whether all duplicates have been preempted (2306). If yes, the UE sends an indication to the gNB to request resources for transmission (2309). If not all duplicates have been preempted (2306), the UE sends unpreempted duplicates at the next configuration grant time (2307). The UE determines whether the Rx UE has successfully received the transmission (2308). If not, the Tx UE sends an indication to the gNB to request resources for transmission (2309).

[0316] In another example, when the Tx UE detects that at least one duplicate transmission has been preempted by another transmission, the Tx UE can discard all duplicate transmissions and can send an indication to the gNB to request a retransmission schedule.

[0317] Alternatively, the UE can detect and confirm that there is no preemption at configuration grant time k. Then the UE can use the resources in configuration grant time k to perform sidelink transmissions.

[0318] An indication to the gNB to request retransmission scheduling on the side link (e.g., NACK feedback) can be sent on the PUCCH or PUSCH.

[0319] To enable the Rx UE to properly soft-combine repetitions of the same TB, the Tx UE can send an indication to the Rx UE to indicate which repetition has been preempted. Such an indication can be carried by the PSCCH associated with the PSSCH configured in the configuration grant. For example, an L-bit bitmap can be sent using the preemption indication field in the CG-SCI, where L equals the number of repetitions configured for the configuration grant. If the i-th bit (i = 1, 2, ..., L) in the bitmap is indicated as '0', the Rx UE can determine that the i-th repetition has been sent and can soft-combine it with other repetitions; if the i-th bit in the bitmap is indicated as '1', the Rx UE can determine that the i-th repetition has been preempted and cannot soft-combine it with other repetitions, and vice versa.

[0320] In yet another example, a Tx UE can be configured with multiple configuration grants. When a Tx UE determines to send data on a configuration grant (e.g., configuration grant A), and the Tx UE detects that it is being preempted by another transmission, it can discard the transmission on configuration grant A and perform the transmission on another configuration grant (e.g., configuration grant B). For example, configuration grant B could be the next available configuration grant among all configured CGs.

[0321] Alternatively, when a Tx UE determines to send data on a configuration grant (e.g., configuration grant A), and the Tx UE detects that it has been preempted by another transmission, it cannot send the preempted duplicate, but instead sends the unpreempted duplicate. If the Tx UE detects that no transmission has been received by Rx, it can perform a retransmission for another configuration grant (e.g., configuration grant B). For example, configuration grant B could be the next available configuration grant among all configuration CGs. To allow the Rx UE to soft-combine duplicates of the same TB across different configuration grants, the Tx UE can indicate the same HARQ process ID, where the NDI field does not switch for transmissions in configuration grant A and configuration grant B. If no UE determines to send data on configuration grant time k, this indication can become an invalid message and no UE will monitor or detect it.

[0322] In this alternative scenario, the gNB does not know when the UE will send at the configured CG timing, and therefore the gNB does not know whether it is a retransmission scheduled for a preempted side link transmission.

[0323] In one scenario (e.g., when a Uu UL transmission preempts a sidelink transmission), the gNB can monitor the received power level to determine if another transmission is in the channel. When the gNB detects another transmission, although it cannot decode it, it can determine that an inter-UE conflict exists. The gNB can then schedule retransmissions for the configured authorized UE. This approach can be applied to power-based inter-UE conflict handling schemes.

[0324] In another scenario, when a V2X Tx UE has data to transmit during a CG (Coordination Clock) and detects that it has been preempted, the UE can send an indication to the gNB (Gate NB) to request a retransmission schedule, instead of waiting for the next CG to retransmit. This indication could be an SR (Sequence Signal), a BSR (Browser Signal), a NACK (Non-Accept) feedback, a reference signal, a preamble, or a sequence. An example of the disclosed procedure is... Figure 24 As shown in the diagram. The Tx UE receives configuration grant resources for sidelink transmission (2401). The UE determines whether the configuration grant is dedicated to the UE (2402). If yes, the UE uses the configuration grant whenever it has data to send (2408). If no, the UE determines whether it has data to send at the next configuration grant time (2403). If yes, the UE sends data at the next configuration grant time (2404). The UE monitors to detect whether it has been preempted or received a preemption indication (2405). The UE determines whether it has detected preemption (2406). If yes, the UE sends an indication to the gNB to request resources for retransmission (2407).

[0325] In another alternative scenario, when the UE determines that it needs to transmit data on a configured CG timing (e.g., CG timing k), the UE can send an indication to the gNB notifying it that it has data to transmit. For example, this indication could be an SR, a BSR, a reference signal, a preamble, or a sequence. This indication can be sent on a PUCCH resource prior to the configured grant resource. The time offset between the PUCCH and the configured grant timing can be fixed or configurable. Alternatively, the indication can be sent on one or more dedicated symbols (e.g., the first symbol in the configured grant), or on some REs within the first symbol.

[0326] In this alternative scenario, if the gNB expects to schedule emergency transmissions using the same resources, the gNB knows that an inter-UE conflict will occur. The gNB can send an indication to indicate the inter-UE conflict, which can be a preemption indication, a power reduction indicator, or a cancellation indication, as disclosed in previous sections.

[0327] If the UE determines to send data on the configured authorized timing k, it can monitor and detect whether it has been preempted. If the UE detects preemption, it can handle this issue of broadcast, multicast, and unicast using the procedures published for handling inter-UE conflicts between dynamically scheduled Uu transmissions and dynamically scheduled sidelink transmissions. Generally, the schemes proposed for dynamically scheduled broadcast, multicast, and unicast can also be applied here. If the UE does not detect preemption, it can send data on CG timing k without waiting for a new scheduling.

[0328] Because the gNB is aware of conflicts between UEs, it can configure authorized sidelink scheduling for retransmissions for a UE without receiving feedback from the Tx UE. Alternatively, the gNB can schedule retransmissions based on feedback from the Tx UE, as is disclosed in dynamically scheduled multicast and unicast scenarios.

[0329] Simultaneously, when a UE with configuration authorization (e.g., UE1) sends an indication to the gNB to notify it that it has data to transmit, UE1 can also indicate the priority of the data to be transmitted. By doing so, the gNB can determine whether it will schedule another transmission on the same resource. For example, if UE1 indicates that it has urgent data to transmit on the configuration authorization, the gNB cannot schedule another transmission on the same resource. Alternatively, if UE1 indicates that it has regular data to transmit on the configuration authorization, the gNB can schedule another, more urgent transmission on the same resource and send an inter-UE conflict indication to UE1.

[0330] Examples of the public process are in Figure 25 As shown in the diagram. The UE receives configuration grant resources for sidelink transmission (2501). The UE determines whether the configuration grant is dedicated to the UE (2502). If so, the UE uses the configuration grant when it has data to send (2509). If so, the UE determines whether it has data to send at the next configuration grant time (2503). If so, the UE sends an indication to the gNB to indicate that the UE has data to send (2504). The UE sends data on the configuration grant (2505). The UE monitors and detects whether it has been preempted (2506). The UE determines whether it has detected preemption (2507). If so, the UE receives a retransmission schedule from the gNB and retransmits (2508).

[0331] The disclosed scheme can also be applied to conflict scenarios where UE1 and UE2 participate in sidelink communication and different entities make decisions on UuTX / RX authorization and sidelink TX / RX authorization.

[0332] The disclosed scheme can also be applied to conflicts between two Uu transmissions, for example, conflicts between two UL transmissions on a Uu interface.

[0333] Signaling of the side link cancellation indicator

[0334] Side link cancellation indicator monitoring

[0335] Because the gNB can determine when a sidelink transmission is preempted (e.g., a sidelink transmission scheduled by dynamic grant or a sidelink transmission performed on a configured grant resource), the Tx UE may need to monitor cancellation indicators (e.g., SL-CI) after the Tx UE receives a scheduling grant from the gNB or when the Tx UE determines that it will perform a sidelink transmission on a configured grant.

[0336] In one example, for a UE that is dynamically scheduled to have sidelink transmission, the UE can start monitoring SL-CI from the next time slot after the time slot carrying dynamic authorization.

[0337] Alternatively, in another example, the UE can be configured by the gNB to start from the k-slot following the DCI that carries the scheduling sidelink transmission. 偏移，1 SL-CI monitoring begins at each time slot. For example, k can be configured via RRC signaling. 偏移，1 Value. k can be configured for the UE through UE-specific RRC configuration. 偏移，1 For example, by configuring the RRC parameter SLCIMonitorOffset in the SearchSpace information element. Alternatively, k can be configured for the UE through cell-specific RR configuration. 偏移，1 For example, through the RRC parameter SLCIMonitorOffset configured in SIB, such as OSI.

[0338] Alternatively, in yet another example, the UE can be configured by the gNB to start from k slots prior to the time slot carrying sidelink transmissions scheduled by dynamic grant. 偏移，2 Monitoring of SL-CI begins in each time slot. (and k) 偏移，1 Similarly, k can be configured via RRC signaling. 偏移，2 For example, through UE-specific RRC configuration, or through cell-specific RRC configuration.

[0339] In one example, for a UE configured with configuration grants for sidelink transmission, the UE can be configured by the gNB to start from slot k after the slot that carries the previous configuration grant timing. 偏移，3 SL-CI monitoring begins in a time slot of k slots. Alternatively, in another example, the UE can be configured by the gNB to start monitoring from a time slot k before the time slot carrying the next configuration authorization timing. 偏移，4 SL-CI monitoring can begin in the next time slot of the previous time slot. Alternatively, in yet another example, the UE can begin SL-CI monitoring in the next time slot after the time slot carrying the previously configured authorization timing.

[0340] For configuration authorization type 1 and configuration type 2, k 偏移，3 or k 偏移，4The value can be configured by RRC, for example, through the RRC parameter SLCIMonitorOffset configured in the SLConfiguredGrantConfig information element.

[0341] In another approach, for configuration authorization type 2, a set of k can be configured in the SLConfiguredGrantConfig information element. 偏移，3 or k 偏移，4 Value. Activating DCI can carry fields (e.g., SL CI monitoring offset field) to indicate one of the candidate values ​​within the group to the UE.

[0342] In one example, for a UE with dynamic authorization scheduling and a UE configured with authorization, the UE can schedule the PSSCH in the slot k before the slot. 停止 Stop SL-CI monitoring in a time slot or symbol, where k 停止 This could be the minimum processing time for SL-CI and the time required to prepare an updated SCI (e.g., a second-stage SCI).

[0343] Alternatively, in another example, the UE can be configured via RRC to have a time window in which the UE needs to monitor SL-CI, for example, k mw Each time slot. The UE can start monitoring k times after the time slot. mw SL-CI monitoring is stopped in each time slot.

[0344] Determine the time range for the SL-CI reference.

[0345] After the UE detects the SL-CI, in order to understand the information it carries, the UE needs to determine the time region and frequency region referenced by the SL-CI.

[0346] For example, to determine the start of a time region, the UE can be indicated with a timing offset between the SL-CI and the referenced time region. In one example, the timing offset can be configured via RRC, for example, through the RRC parameter SLCITimeRegionOffset. The timing offset can be in symbols or in time slots. The scheme proposed for configuring the RRC parameter SLCIMonitorOffset can also be applied here.

[0347] In another example, the timing offset can be indicated by a DCI carrying the SL-CI. For example, the RRC can be configured with a set of timing offset values; and the DCI carrying the SL-CI can carry a field (e.g., an SL-CI time offset field) to indicate to the UE one of the candidate values ​​within that set.

[0348] In addition to the timing offset, the UE also needs to determine the duration of the time region. In one example, the duration can be explicitly configured by the RRC through the RRC parameter SLCITimeRegionDuration, for example, one time slot or two time slots. The timing duration can be in units of symbols, or the timing offset can also be in units of time slots. The scheme proposed for configuring the RRC parameter SLCIMonitorOffset can also be applied here.

[0349] In another example, the timing duration can be indicated by a DCI carrying the SL-CI. For example, the RRC can configure a set of timing duration values; and the DCI carrying the SL-CI can carry a field (e.g., an SL-CI duration field) to indicate to the UE one of the candidate values ​​within that set. Alternatively, the timing duration can be indicated by the DCI via start and length indicator value (SLIV) fields, which indicate one of the possible combinations of start and duration values ​​configured by the RRC. In the example above, the timing offset and duration are indicated separately. Alternatively, the timing offset and duration can be indicated jointly, for example, jointly by a DCI carrying the SL-CI. For example, the RRC can configure a set of combinations of timing offset values ​​and timing duration values; the DCI carrying the SL-CI can carry a field (e.g., an SL-CI time indicator field) to indicate to the UE one of the candidate combinations within that set.

[0350] In some cases, the Uu interface for sidelink transmission and SL-CI transmission can have different subcarrier spacings (SCS). In one example, the SCS of the sidelink transmission can be used as a reference SCS to determine the time zone; for example, timing offset and duration are indicated by the number of time slots or symbols on the sidelink. In another example, the SCS of the Uu interface can be used as a reference SCS to determine the time zone; for example, timing offset and duration are indicated by the number of time slots or symbols on the Uu interface.

[0351] Determine the frequency range of the SL-CI reference.

[0352] Additionally, the UE needs to determine the frequency region for SL-CI reference. In one example, the frequency region can be implicitly indicated; for example, the frequency region can be the entire sidelink BWP; or, the frequency region can be a frequency band shared by Uu services and sidelink services.

[0353] In another example, the frequency region can be explicitly indicated relative to the sidelink BWP. For instance, to determine the frequency region, the number of subchannel offsets can be configured for the UE relative to the lowest subchannel of the sidelink BWP, for example, via the RRC parameter SLCIFrequencyRegionOffset; and the number of subchannels occupied by the frequency region can be configured for the UE, for example, via the RRC parameter SLCIFrequencyRegionRange. In this example, the granularity of the RRC parameter is in the number of subchannels. The granularity of the RRC parameter can also be in the number of PRBs.

[0354] In yet another example, the frequency region can be explicitly indicated relative to the BWP on the Uu interface (e.g., the active UL BWP or the active DLBWP). For example, to determine the frequency region, the UE can be configured with a PRB offset amount relative to the lowest PRB of the active UL BWP; and the UE can be configured with the number of PRBs occupied by the frequency region.

[0355] Determine the actual time and frequency of resource cancellations.

[0356] Within the referenced time and frequency regions, gNB can use SL-CI to indicate the actual cancelled time and frequency resources.

[0357] In one example, the cancelled time resource and the cancelled frequency resource can be indicated separately. For instance, a DCI carrying SL-CI could contain two fields: a time resource cancellation indicator and a frequency resource cancellation indicator, to indicate the actual cancelled time and frequency resources, where these two fields can be b respectively. T The bitmap of the units digit and b F A bitmap for the unit digit. The sizes of the two bitmaps can be pre-specified, or b T The value of b F The values ​​can be configured by the gNB, for example, through the RRC parameters SLCITimePayloadSize and SLCIFrequencyPayloadSize respectively. The UE can then evenly divide the reference time region and the reference frequency region into b... T Each part and b F Each part is a separate section. For each part, if the associated bit in the bitmap is set to '1', the UE can determine that the transmission on that part has been canceled.

[0358] In another example, the cancelled time resources and the cancelled frequency resources can be jointly indicated. For example, a DCI carrying SL-CI could include a field called a sidelink cancellation indicator to indicate the actual cancelled time and frequency resources, where this field could be b TFA bitmap for the unit digit. The size of the bitmap can be specified in advance, or in bytes. TF The value can be configured by the gNB, for example, via the RRC parameter SLCIPayloadSize. The UE can evenly divide the reference time and frequency regions into b TF For example, the UE can uniformly divide the reference domain into n parts. T Multiply by n F There are n cells, where n is a cell. T ×n F =b TF To determine how to divide the reference region, the UE needs to know n. T The value of n F One of the values.

[0359] The UE can be configured with n T The value can be configured, for example, through the RRC parameter SLCINumberofTimeProtion.

[0360] Alternatively, the UE can be configured with the duration of each segment, for example, via the RRC parameter SLCITimeDurationPerProtion. The UE can... A definite n T Value. Then the UE can... A definite n F value.

[0361] For each part of the grid, if the associated bit in the bitmap is set to '1', the UE can determine that the transmission on that part has been canceled.

[0362] In the example above, the UE is indicated with time-granularity information. Alternatively, the UE can be indicated with frequency-granularity information from which the value n is derived. T The similar scheme disclosed for signal notification at the time granularity can also be applied to signal notification at the frequency granularity.

[0363] Inter-UE conflict handling with duplicate sidelink transmissions scheduled by the NB in ​​NR V2X mode 1.

[0364] For example, in V2X mode 1, a Tx UE can be scheduled by a gNB to send sidelink transmissions with multiple repetitions, such as... Figure 26 As shown.

[0365] The initial transmission and repetition can be sent in adjacent time slots as shown in the figure. Alternatively, the time interval between the initial transmission and repetition can be several time slots.

[0366] Please note, Figure 26An example of gNB scheduling sidelink transmissions with multiple repetitions is shown. The gNB can also schedule sidelink transmissions with multiple HARQ-based retransmissions. Alternatively, the gNB can schedule periodic sidelink transmissions. In the following content, we disclose a scheme using sidelink transmissions with multiple repetitions as an example. The disclosed scheme can also be applied to sidelink transmissions with multiple HARQ-based retransmissions and periodic sidelink transmissions. For example, by replacing the repetitions in the scheme with HARQ-based retransmissions, the disclosed scheme can also be applied to sidelink transmissions with multiple HARQ-based retransmissions.

[0367] Send SL-CI only before the initial transmission

[0368] In one example, the UE can assume that the SL-CI for the entire transmission (initial transmission and repetition) is only signaled once before the initial transmission. The Tx UE can monitor the SL-CI only before the initial transmission.

[0369] If the SL-CI is detected and the Tx UE determines that all initial transmissions and duplicates have been cancelled, the Tx UE may discard the scheduled initial transmissions and the scheduled duplicate transmissions. To indicate to the Rx that a transmission has been cancelled, the Tx UE may discard both the Phase 2 SCI and PSSCH transmissions; or, the Tx UE may discard the PSSCH transmission while still sending the Phase 2 SCI and setting the preemption indication field to '1' or '1111'; or, the Tx UE may discard both the Phase 2 SCI and associated PSSCH transmissions while using the resources that should have been used to send the Phase 2 SCI to send an indication that the transmission has been cancelled.

[0370] In one scenario, if SL-CI is detected and the Tx UE determines that one or more of the initial and duplicate transmissions have been cancelled, the Tx UE can discard all scheduled initial and duplicate transmissions. The Tx UE can use the scheme proposed above to send an indication to the Rx UE to indicate that all scheduled transmissions have been cancelled.

[0371] In another scenario, when the Tx UE determines that one or more of the initial transmission and repetitions have been cancelled, the Tx UE may discard only the transmissions overlapping with the cancelled resources. The Tx UE can indicate the discarded transmissions to the Rx UE using the preemption indication field in the Phase 2 SCI, which is a 4-bit bitmap, assuming the following conditions... Figure 26As shown. For example, suppose the Tx UE detects an SL-CI and determines that the first and third repetitions overlap with the canceled resource. The Tx UE can discard the transmissions of the first and third repetitions while still sending the initial transmission and the second repetition. The Tx UE will also set the preemption indication field in the associated second-stage SCI to '0101' and send it to the Rx UE.

[0372] When an Rx UE detects an indication sent by a Tx UE to cancel a scheduled sidelink transmission, the Rx UE cannot attempt to decode the corresponding PSSCH and will not soft-combine it with other transmissions in the same TB.

[0373] The SL-CI is sent before the initial transmission and during repetitions, and the Tx UE indicates preemption information in each repetition.

[0374] In another example, the SL-CI can be signaled by the gNB before the initial transmission and during the scheduled sidelink transmission (before the last repetition). The Tx UE can monitor the SL-CI before the initial transmission and continue monitoring until the last repetition is reached. Figure 27 The image shows an example where the SL-CI is sent by the gNB between the first and second repetitions of a scheduled sidelink transmission and indicates that the second repetition is canceled. It is also possible for an SL-CI to indicate that multiple repetitions are canceled.

[0375] In this example, the Tx UE can discard only the transmissions that overlap with the cancelled resource, such as the initial transmission or duplicates. Because cancellation may occur after the initial transmission, the Tx UE cannot use the Phase 2 SCI associated with the initial transmission to indicate preemption to the Rx UE.

[0376] The Tx UE can send an indication in each repetition to indicate whether the sidelink transmission has been preempted. This indication can be sent via a pre-configured reference signal (e.g., SL-DMRS), a pre-configured sequence, or control information.

[0377] For example, the Tx UE sends both the SCI (e.g., the second-stage SCI) and data in all repetitions. The SCI field (e.g., the preemption indication field) can be carried by the second-stage SCI associated with the PSSCH to indicate whether the sidelink transmission has been preempted.

[0378] The preemption indication field in the second phase can be 1 bit; for example, '0' indicates that the associated PSSCH was not canceled, and '1' indicates that the associated PSSCH was canceled. This field can be used to indicate only whether the associated PSSCH transmission was preempted.

[0379] use Figure 27As an example, the Tx UE will set the preemption indication field sent in the initial transmission, the first repetition, and the third repetition to '0'; and the Tx UE will set the preemption indication field sent in the second repetition to '1'.

[0380] The preemption indication field in the second phase can be a bitmap, where the length of the bitmap equals the total number of initial transmissions and repetitions. This field can be used to indicate whether PSSCH transmissions for all initial transmissions and repetitions have been preempted, for example, by setting the bit associated with the corresponding PSSCH in the bitmap to '1'. Based on the detected SL-CI, the Tx UE can set different values ​​for the bitmaps transmitted in different repetitions.

[0381] use Figure 27 As an example, the bitmap length is 4. Before sending the initial transmission and the first repetition, the Tx UE does not detect any preemption of PSSCH transmissions. Therefore, the Tx UE sets the preemption indication field sent in the initial transmission and the first repetition to '0000' and '0000', respectively. Before sending the second repetition, the Tx UE detects that the PSSCH in the second repetition has been preempted. The Tx UE sets the preemption indication field sent in the second repetition to '0010'. Before sending the third repetition, the Tx UE does not detect any further preemption. Then the Tx UE sets the preemption indication field sent in the second repetition to '0010'.

[0382] The SL-CI is sent before the initial transmission and during repetitions; the Tx UE only indicates preemption information in the last repetition.

[0383] Alternatively, the Tx UE can send an indication only in the last repetition to indicate whether the sidelink transmission has been preempted. This indication can be sent via a pre-configured reference signal (e.g., SL-DMRS), a pre-configured sequence, or control information.

[0384] For example, a Tx UE may send both an SCI (e.g., a second-stage SCI) and data in its last repetition. An SCI field (e.g., a preemption indication field) may be carried by the second-stage SCI to indicate whether the sidelink transmission has been preempted.

[0385] use Figure 27 As an example, the preemption message sent in the last repetition could be 4 bits.

[0386] In one approach, no dedicated SCI field is introduced for sending preemption information in the second-stage SCI. During the initial transmission, the Tx UE cannot indicate preemption information in the second-stage SCI. In the final repetition, the Tx UE can reuse existing fields from the second-stage SCI to indicate preemption information. For example, the Tx UE can reuse the first four bits of the MCS field carried in the second-stage SCI in the final repetition and set it to '0010' to indicate that the second repetition was preempted while other repetitions were not.

[0387] In another approach, a dedicated SCI field can be introduced for sending preemption information in the second-stage SCI, such as a 4-bit SCI field preemption indication field. Such a field can be carried by the second SCI sent in both the initial transmission and the last repetition. For example, before the initial transmission, the Tx UE does not detect any preemption. The Tx UE can set the preemption indication field in the initial transmission to '0000'. Before the last repetition, the Tx UE detects that the second repetition has been preempted. The Tx UE can set the preemption indication field in the last repetition to '0010'.

[0388] The three schemes disclosed here use the case where there is a time interval between the transmission of the first-stage SCI and the second-stage SCI as examples. In another scenario, the three disclosed schemes can also be applied when the first-stage SCI and the second-stage SCI can be transmitted without any time interval between them, such as... Figure 28 As shown. In this case, the SL-CI sent by the gNB to the Tx UE can be sent only before the initial transmission; or it can be sent before the initial transmission and during repetitions. The SL-CI sent by the Tx UE to the Rx UE to indicate preemption information can be sent only in the initial transmission; or it can be sent in both the initial transmission and all repetitions; or it can be sent in the initial transmission and only in the last repetition. The preemption information (e.g., the disclosed preemption indication field) can be carried by the first-stage SCI or it can be carried by the second-stage SCI.

[0389] When the first-stage SCI and the second-stage SCI are sent without any time interval between them, the disclosed scheme can be applied to sidelink transmissions with multiple repetitions, such as... Figure 28 As shown. The disclosed scheme can be applied to sidelink transmissions with multiple HARQ-based retransmissions; and it can also be applied to periodic sidelink transmissions.

[0390] Intra-UE priority ordering for simultaneous sidelink and uplink transmissions

[0391] In NR V2X, UEs can be scheduled to perform simultaneous sidelink and uplink transmissions, where the carriers for sidelink transmissions and uplink transmissions can be different carriers or shared carriers. In some scenarios (e.g., when the total transmit power exceeds the maximum power P),... CMAX The UE needs to prioritize these transmissions to adjust transmit power or even drop low-priority transmissions. In this section, we disclose the mechanism by which the UE prioritizes concurrent sidelink and uplink transmissions.

[0392] Priority ordering of indicator priority.

[0393] In one example, each transmission (e.g., a sidelink transmission or an uplink transmission) can be indicated with a priority. The priority value can be explicitly signaled by RRC, for example, through the RRC parameter TransmissionPriorityLevel, or pre-specified by the specification. For sidelink transmissions, TransmissionPriorityLevel can be configured within the information element configuring the resource pool (e.g., SLResourcePoolConfig).

[0394] In one example, a priority can be configured / pre-specified for the transport of SL-PSCCH, SL-PSSCH, and SL-PSFCH. For instance, SL-PSCCH, SL-PSSCH, and SL-PSFCH can share the same resource pool. Within the resource pool configuration, a priority is configured that is used for SL-PSCCH, SL-PSSCH, and SL-PSFCH.

[0395] In another example, SL-PSCCH, SL-PSSCH, and SL-PSFCH can share the same resource pool. Different priorities can be configured / pre-specified for the transmission of SL-PSCCH, SL-PSSCH, and SL-PSFCH. For example, within the resource pool configuration, RRC parameters SLPSCCHPriorityLevel, SLPSSCHPriorityLevel, and SLPSFCHPriorityLevel can be configured separately for the UE.

[0396] In yet another example, dedicated resource pools can be configured / pre-specified separately for SL-PSCCH, SL-PSSCH, and SL-PSFCH, with different priorities configured separately within the associated resource pool configuration.

[0397] Priorities can also be signaled by the DCI transmitted on the scheduling side link. For example, to indicate the priority of SL-PSSCH, a set of priority values ​​can be configured or pre-specified by the RRC; and the DCI performing the scheduling can carry a field (e.g., PSCCH Priority) to indicate one of the candidate values ​​in that set to the UE.

[0398] Priorities can also be implicitly derived. For example, the priority of SL-PSFCH can be equal to the priority indicated for SL-PSSCH.

[0399] For PSCCH, the first-stage SCI and the second-stage SCI can be assigned the same priority. Alternatively, the first-stage SCI and the second-stage SCI can be assigned different priorities, for example, by configuring SL1stSCIPriorityLevel and SL2ndSCIPriorityLevel separately through two RRCs.

[0400] For PSFCH, HARQ-ACK feedback and CSI feedback can be assigned the same priority. Alternatively, HARQ-ACK feedback and CSI feedback can be assigned different priorities, for example, by configuring SLHARQPriorityLevel and SLCSIPriorityLevel separately through two RRCs. When the UE has concurrent sidelink and uplink transmissions, the UE can prioritize transmissions with higher priority; for example, transmissions with lower priority values ​​can be given priority.

[0401] When sidelink transmissions and uplink transmissions have the same priority value, sidelink transmissions (except for SL CSI feedback), such as SL-PSCCH, SL-PSSCH, and SL HARQ feedback, can be given priority.

[0402] When SL CSI feedback and uplink transmissions have the same priority value, uplink transmissions (excluding CSI feedback on the uplink), such as SR, HARQ feedback, and PUSCH, can be given priority.

[0403] When SL CSI feedback and uplink CSI feedback have the same priority value, SL CSI feedback can be prioritized.

[0404] Alternatively, when sidelink and uplink transmissions have the same priority value, the UE can prioritize transmissions based on certain criteria. Some examples are shown below:

[0405] ● Channel conditions: To ensure performance, the UE can prioritize transmissions based on channel conditions. For example, the UE can prioritize transmissions with better channels. Therefore, it has a higher probability of being delivered.

[0406] ● Packet size: Because high-priority transmissions may preempt other transmissions, UEs can prioritize transmissions that require fewer resources to reduce potential preemption for other UEs. ● Remaining time before a UE must discard a packet: Two transmissions may have different processing timelines, and therefore may have different remaining times before a packet must be discarded. UEs can prioritize transmissions with shorter remaining times to reduce the packet drop rate.

[0407] Priority sorting without a priority indicator

[0408] In another example, sidelink transmissions can be classified as URLLC SL transmissions and eMBB SL transmissions, where the UE can determine the transmission category based on QoS requirements, service type, etc. Similarly, uplink transmissions can be classified as URLLC UL transmissions and eMBB UL transmissions.

[0409] The UE can prioritize transmissions according to the following priority ordering rules:

[0410] URLLC SL transmission (excluding SL CSI feedback) > URLLC UL transmission (excluding UL CSI feedback) > URLLC SL CSI feedback > URLLC UL CSI feedback > eMBB SL transmission (excluding SL CSI feedback) > eMBB UL transmission (excluding UL CSI feedback) > eMBB SL CSI feedback > eMBB UL CSI feedback.

[0411] Here, 'A>B' means that the transmission of A takes precedence over the transmission of B.

[0412] Note: All SL CSI feedbacks with the same priority as eMBB SL CSI feedbacks can be treated equally; and all UL CSI feedbacks with the same priority as eMBB UL CSI feedbacks can be treated equally. The priority ranking rule can then be:

[0413] URLLC SL transmission (excluding SL CSI feedback) > URLLC UL transmission (excluding UL CSI feedback) > eMBB SL transmission (excluding SL CSI feedback) > eMBB UL transmission (excluding UL CSI feedback) > SL CSI feedback > UL CSI feedback.

[0414] Dynamically scheduled sidelink transmissions preempt transmissions on the other sidelink.

[0415] In NR V2X mode 1, overlapping resources may be allocated to two dynamically scheduled sidelink transmissions, such as... Figure 29 As shown. For example, resources for sidelink transmission are dynamically allocated to UE1. Then, the gNB might determine to allocate some overlapping resources to UE2 and preempt UE1's transmission, for example, because UE2 may have more urgent data to send. Therefore, inter-UE collisions will occur. Inter-UE collisions may occur on shared carriers; or, they may occur on dedicated carriers. In this section, we disclose inter-UE collision handling schemes for such scenarios.

[0416] In an alternative scenario, the inter-UE conflict can be transparent to UE2. In order to indicate the inter-UE conflict to UE1, the gNB can send an indication to UE1, which can be a preemption indication, a power reduction indication, or a cancellation indication, as disclosed in previous sections.

[0417] For UE1, it can monitor and detect whether it is preempted by the gNB. When UE1 determines that it has been preempted, it can handle this issue of broadcast, multicast, and unicast using the procedures disclosed for handling inter-UE conflicts between dynamically scheduled Uu transmissions and dynamically scheduled sidelink transmissions. In general, the solutions proposed for dynamically scheduled broadcast, multicast, and unicast can also be applied here.

[0418] In another alternative scenario, the gNB can indicate an inter-UE conflict to UE2, letting UE2 know that it will preempt other transmissions. This can be done, for example, via a scheduled DCI with explicit bit fields, or implicitly through signaling. Once UE2 determines that it will preempt other transmissions, it can send an indication of the inter-UE conflict, which can be a preemption indication, a power reduction indicator, or a cancellation indication, as disclosed in previous sections. This indication can be a preamble, a sequence, a reference signal, a broadcast SCI, or the broadcast portion of a two-stage SCI.

[0419] For UE1, it can monitor and detect whether it is preempted by other V2X UEs. When UE1 determines that it has been preempted, it can handle this issue of broadcast, multicast, and unicast using the procedures disclosed for inter-UE conflict handling between dynamically scheduled Uu transmissions and dynamically scheduled sidelink transmissions. In general, the schemes proposed for dynamically scheduled broadcast, multicast, and unicast can also be applied here.

[0420] Sidelink transmissions based on configuration authorization are preempted by dynamically scheduled sidelink transmissions.

[0421] In NR V2X Mode 1, configuration grant resources can be allocated to the UE for sidelink transmission. Simultaneously, the gNB may dynamically allocate some overlapping resources to another UE, such as... Figure 30 As shown. For example, configuration grant resources for sidelink transmission are allocated to UE1. Then, the gNB may determine to allocate some overlapping resources for UE2 in time slot #2. Meanwhile, if UE1 also has data to transmit during the CG timing configured in time slot #2, an inter-UE conflict will occur. Inter-UE conflicts may occur on a shared carrier; or, it may occur on a dedicated carrier. In this section, we disclose an inter-UE conflict handling scheme for such scenarios.

[0422] In scenarios similar to inter-UE conflicts between two dynamically scheduled sidelink transmissions, potential inter-UE conflicts can be transparent to UE2, or potential inter-UE conflicts can be indicated to UE2.

[0423] On one hand, potential inter-UE conflicts can be transparent to UE2. The problem then becomes similar to the inter-UE conflict between configuration-authorized sidelinks and dynamic Uu transmissions. The solutions proposed for handling inter-UE conflicts between configuration-authorized sidelinks and dynamic Uu transmissions can also be applied here. Some examples include... Figure 24 and Figure 25 As shown.

[0424] On the other hand, gNB can send an indication to UE2 to indicate a potential inter-UE conflict, which has the following alternative scenarios.

[0425] gNB assumes that inter-UE conflicts will occur.

[0426] In the first alternative scenario, the gNB can send an inter-UE conflict indication to UE2, thereby notifying UE2 that other transmissions will be preempted. This can be done, for example, via a scheduled DCI with explicit bit fields or implicitly through signaling. Once UE2 determines that it will preempt other transmissions, UE2 can send an indication to indicate the inter-UE conflict, which can be a preemption indication, a power reduction indicator, or a cancellation indication, as disclosed in previous sections. This indication can be a preamble, a sequence, a reference signal, a broadcast SCI, or the broadcast portion of a two-stage SCI.

[0427] For UE1, when it determines to send data at the next configuration authorization time, it can monitor and detect whether it has been preempted by other V2X UEs. When UE1 determines that it has been preempted, it can use the procedures disclosed for inter-UE conflict handling between dynamically scheduled Uu transmissions and dynamically scheduled sidelink transmissions to handle this issue of broadcast, multicast, and unicast. In general, the solutions proposed for dynamically scheduled broadcast, multicast, and unicast can also be applied here.

[0428] In this alternative scenario, the gNB does not know when UE1 will send at the configured CG timing, and therefore the gNB does not know whether it needs to schedule retransmissions for preempted sidelink transmissions.

[0429] In one scenario, the gNB can monitor power levels to determine if other transmissions are occurring in the channel. When the gNB detects another transmission, although it cannot decode it, it can determine that an inter-UE collision exists. The gNB can then schedule retransmissions for the configured authorized UE. This approach can be applied to power-based inter-UE collision handling schemes.

[0430] In another scenario, when UE1 has data to send during a CG timing and detects that it has been preempted, UE1 can send an indication to the gNB to request a retransmission schedule instead of waiting for the next CG timing to retransmit. For example, the indication could be an SR, a BSR, a reference signal, a preamble, or a sequence.

[0431] The CG UE sends a wait-for-transmission indication at the next CG timing.

[0432] In the second alternative scenario, when UE1 determines that it needs to transmit data on a configured CG timing (e.g., CG timing k), it can send an indication to the gNB to notify it that there is data to transmit. For example, this indication could be an SR, or a BSR, or a reference signal, or a preamble, or a sequence.

[0433] In this alternative scenario, if the gNB needs to use the same resources to schedule some urgent transmissions for another UE (e.g., UE2), the gNB knows that an inter-UE conflict will occur. The gNB can send an inter-UE conflict indication to UE2, notifying UE2 that other transmissions will be preempted. This can be done, for example, via a scheduling DCI with explicit bit fields or implicitly signaled. Once UE2 determines that it will preempt other transmissions, UE2 can send an indication to indicate the inter-UE conflict, which can be a preemption indication, a power reduction indicator, or a cancellation indication, as disclosed in previous sections. This indication can be a preamble, a sequence, a reference signal, a broadcast SCI, or the broadcast portion of a two-stage SCI.

[0434] For UE1, it can monitor and detect whether it is preempted at CG time k. When the UE determines that it has been preempted, it can handle this issue of broadcast, multicast, and unicast using the procedures disclosed for inter-UE conflict handling between dynamically scheduled Uu transmissions and dynamically scheduled sidelink transmissions. In general, the schemes proposed for dynamically scheduled broadcast, multicast, and unicast also apply here. If UE1 does not detect that it has been preempted, the UE can send data at CG time k without waiting for a new schedule.

[0435] Because the gNB is aware of inter-UE conflicts, it can schedule retransmissions for UE1 without receiving feedback from UE1. Alternatively, the gNB can schedule retransmissions based on feedback from UE1, as is disclosed in dynamically scheduled multicast and unicast scenarios.

[0436] At the same time, when UE1 sends an indication to gNB, it can also indicate the priority of the data to be transmitted, as disclosed in the case of inter-UE conflict between configuration authorized sidelink and dynamic Uu transmission.

[0437] It should be understood that any methods and processes described herein may be embodied in the form of computer-executable instructions (i.e., program code) stored on a computer-readable storage medium, and when executed by a machine, such as a computer, server, M2M terminal device, M2M gateway device, etc., perform and / or implement the systems, methods, and processes described herein. Specifically, any of the foregoing steps, operations, or functions may be implemented in the form of such computer-executable instructions. Computer-readable storage media includes both volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, but such computer-readable storage media does not include signals. Computer-readable storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other storage technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other physical medium that can be used to store desired information and is accessible by a computing system.

[0438] In describing preferred embodiments of the subject matter of this disclosure, specific terminology has been used for clarity, as illustrated in the figures. However, the claimed subject matter is not intended to be limited to the specific terminology chosen so far, and it should be understood that each specific element includes all technical equivalents that operate in a similar manner to achieve a similar purpose.

[0439] Therefore, those skilled in the art will understand that the disclosed systems and methods may be embodied in other specific forms without departing from their spirit or essential characteristics. Thus, the embodiments disclosed herein are to be considered illustrative rather than restrictive in all respects. It is not exhaustive and does not limit the disclosure to the precise form disclosed. Modifications and variations are possible, or may be obtained, from practice of this disclosure without departing from its breadth or scope, in accordance with the foregoing teachings. Therefore, while particular configurations have been discussed herein, other configurations may also be employed. Numerous modifications and other embodiments (e.g., combinations, rearrangements, etc.) are implemented by this disclosure and are within the scope of those skilled in the art and are considered to fall within the scope of the disclosed subject matter and any equivalents thereof. Within the scope of the invention, features of the disclosed embodiments may be combined, rearranged, omitted, etc., to produce additional embodiments. Furthermore, certain features may sometimes be utilized as advantages without the corresponding use of other features. Therefore, the applicant(s) intend to include all such alternatives, modifications, equivalents, and variations within the spirit and scope of the disclosed subject matter.

[0440] Unless explicitly stated otherwise, references to elements in the singular form are not intended to mean "one and only one," but rather "one or more." Furthermore, in claims where phrases such as "at least one of A, B, or C" are used, the phrase is intended to mean that A may exist alone in an embodiment, B may exist alone in an embodiment, C may exist alone in an embodiment, or any combination of elements A, B, and C may exist in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

[0441] According to 335U.SC112(f), no element of any claim herein will be interpreted unless the element is explicitly stated using the phrase “means”. As used herein, the terms “comprising,” “including,” or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements may include not only those elements but also other elements not expressly listed or inherent to such a process, method, article, or apparatus. The scope of the invention is indicated by the appended claims rather than the foregoing description, and all variations in meaning and scope, and their equivalents, are intended to be included therein.

Claims

1. An apparatus comprising: one or more processors configured to: determine a first transmission associated with a sidelink resource in a wireless communication network, wherein the first transmission corresponds to a physical sidelink feedback channel (PSFCH) transmission for providing feedback for a physical sidelink shared channel (PSSCH) transmission; determine a second transmission associated with an uplink resource in the wireless communication network; determine that the first transmission and the second transmission at least partially overlap in time; determine a priority associated with the PSFCH transmission based on a priority associated with the PSSCH transmission; determine a radio resource control (RRC) configuration parameter associated with the second transmission associated with the uplink resource; determine which of the first transmission or the second transmission is a higher priority transmission based on a comparison of the priority associated with the PSFCH transmission and the RRC configuration parameter associated with the second transmission; and transmit one of the first transmission associated with the sidelink resource or the second transmission associated with the uplink resource based on the determined higher priority transmission. The priority associated with the PSSCH transmission is determined based on sidelink control information (SCI).

2. The apparatus of claim 1, wherein, The priority associated with the PSSCH transmission is explicitly indicated via the SCI.

3. The apparatus of claim 2, wherein, The PSSCH transmission is transmitted in a sidelink resource pool.

4. The apparatus of claim 1, wherein, The feedback provided in the PSFCH transmission comprises an acknowledgement (ACK) or a negative acknowledgement (NACK).

5. The apparatus of claim 1, wherein, The RRC configuration parameter is configured for a particular sidelink resource pool.

6. The apparatus of claim 1, wherein, The one or more processors are configured to provide hybrid automatic repeat request (HARQ) feedback through the PSFCH transmission.

7. The apparatus of claim 1, wherein, 8. A method for wireless communication performed by a user equipment (UE), comprising: receiving an indication associated with a first transmission associated with a sidelink resource in a wireless communication network, wherein the first transmission corresponds to a physical sidelink feedback channel (PSFCH) transmission for providing feedback for a physical sidelink shared channel (PSSCH) transmission; receiving an indication associated with a second transmission associated with an uplink resource in the wireless communication network; receiving an indication that the first transmission and the second transmission at least partially overlap in time; receiving an indication of a priority associated with the PSFCH transmission based on a priority associated with the PSSCH transmission; receiving an indication of a radio resource control (RRC) configuration parameter associated with the second transmission associated with the uplink resource; receiving an indication of a higher priority transmission associated with one of the first transmission or the second transmission, the higher priority determined based on a comparison of the priority associated with the PSFCH transmission and the RRC configuration parameter associated with the second transmission; and receiving the second transmission associated with the uplink resource before or after the first transmission associated with a sidelink in one of the cases based on the indication of the higher priority transmission. ​ 9. The method of claim 8, wherein, The priority associated with the PSSCH transmission is determined based on sidelink control information, SCI.

10. The method of claim 9, wherein, The priority associated with the PSSCH transmission is explicitly indicated via the SCI.

11. The method of claim 8, wherein, The PSSCH transmission is transmitted in a sidelink resource pool.

12. The method of claim 8, wherein, The feedback provided in the PSFCH transmission comprises an acknowledgement, ACK, or a non-acknowledgement, NACK.

13. The method of claim 8, wherein, The RRC configuration parameter is configured for a specific sidelink resource pool.

14. The method of claim 8, further comprising transmitting hybrid automatic repeat request, HARQ, feedback through the PSFCH transmission.

Images