Transmission based on the type of conflict

Abstract

Apparatus, method, and system for conflict-based type of transmission are disclosed. A method (400) includes determining (402) that a first transmission resource corresponding to a first user equipment preempts a second transmission resource corresponding to a second user equipment as a result of a conflict between the first transmission resource and the second transmission resource in a shared resource pool. The method (400) includes: in response to the type of conflict being a periodic conflict or a series conflict, transmitting (404) a request for resource reselection and activation from the second user equipment; or, in response to the type of conflict being a one-time conflict, transmitting a request for resource reselection from the second user equipment.

Description

[0001] Cross - reference to related applications

[0002] This application claims priority to U.S. Patent Application Serial No. 62 / 909,885, filed on October 3, 2019, by Karthikeyan Ganesan, entitled "APPARATUSES, METHODS, AND SYSTEMS FOR EFFICIENT LOW LATENCY V2X TRANSMISSION", which is hereby incorporated by reference in its entirety. Technical Field

[0003] The subject matter disclosed herein generally relates to wireless communications and, more particularly, to collision - based types of transmissions. Background Art

[0004] The following abbreviations are defined herein, at least some of which are referenced in the following description: 3rd Generation Partnership Project (“3GPP”), 5th Generation (“5G”), QoS for NR V2X communication (“5QI / PQI”), Authentication, Authorization and Accounting (“AAA”), Acknowledgement (“ACK”), Application Function (“AF”), Authentication and Key Agreement (“AKA”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Application Server (“AS”), Application Service Provider (“ASP”), Autonomous Uplink (“AUL”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Background Data (“BD”), Background Data Transfer (“BDT”), Beam Failure Detection (“BFD”), Beam Failure Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Channel Busy Ratio (“CBR”), Contention-Based Random Access (“CBRA”), Component Carrier (“CC”), Clear Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Configured Grant (“CG”), Closed Loop (“CL”), Coordinated Multi-Point (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Cyclic Redundancy Check (“CRC”), Channel State Information (“CSI”), Channel State Information-Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Discrete Fourier Transform Spread (“DFTS”), Downlink Control Information (“DCI”), Downlink Feedback Information (“DFI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”), Dedicated Short Range Communication (“DSRC”), Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Extensible Authentication Protocol (“EAP”), Effective Isotropic Radiated Power (“EIRP”), European Telecommunications Standards Institute (“ETSI”), Frame-Based Equipment (“FBE”), Frequency Division Duplexing (“FDD”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”),Frequency Division Orthogonal Cover Code (“FD - OCC”), frequency range 1–6 GHz below the band and / or 410 MHz to 7125 MHz (“FR1”), frequency range 2–24.25 GHz to 52.6 GHz (“FR2”), General Geographic Area Description (“GAD”), Guaranteed Bit Rate (“GBR”), Group Leader (“GL”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), General Public Subscription Identifier (“GPSI”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat reQuest (“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hashed Expected Response (“HXRES”), Identity or Identifier (“ID”), Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Intelligent Transport System Application Object Identifier (“ITS - AID”), Key Management Function (“KMF”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), Licensed Assisted Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network (“LAN”), Load - Based Equipment (“LBE”), Listen - Before - Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel Priority (“LCP”), Log - Likelihood Ratio (“LLR”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Media Access Control (“MAC”), Media Access Control Control Element (“MAC CE”), Multimedia Broadcast Multicast Service (“MBMS”), Maximum Bit Rate (“MBR”), Minimum Communication Range (“MCR”), Modulation and Coding Scheme (“MCS”), Master Information Block (“MIB”), Multimedia Internet Keying (“MIKEY”), Multiple - Input Multiple - Output (“MIMO”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”), Mobile Originated (“MO”), Massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine - Type Communication (“MTC”), Multi - User Shared Access (“MUSA”), Non - Access Stratum (“NAS”), Narrow Band (“NB”), Negative Acknowledgment (“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”), Network Exposure Function (“NEF”), Network Function (“NF”)Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), Unlicensed NR (“NR-U”), Network Repository Function (“NRF”), Network Scheduling Mode (“NS Mode”) (e.g., Network Scheduling Mode for V2X communication resource allocation - Mode-1 in NR V2X and Mode-3 in LTE V2X), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operation, Administration, and Maintenance System or Operation and Maintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Open Loop (“OL”), Other System Information (“OSI”), Power Angle Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE-to-UE Interface (“PC5”), Policy and Charging Control (“PCC”), Primary Cell (“PCell”), Policy Control Function (“PCF”), Physical Cell Identifier (“PCI”), Packet Delay Budget (“PDB”), Physical Downlink Control Channel (“PDCCH”), Packet Data Convergence Protocol (“PDCP”), Packet Data Network Gateway (“PGW”), Physical Downlink Shared Channel (“PDSCH”), Pattern Division Multiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”), Preemption Indication (“PI”), Public Land Mobile Network (“PLMN”), PC5 QoS Class Identifier (“PQI”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Proximity Service (“ProSe”), Positioning Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary and Secondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel (“PSFCH”), Provider Service Identifier (“PSID”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QoS Class Identifier (“QCI”), Quasi-Co-Location (“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Serving RAT (“RAT-1”) (serving Uu), Other RAT (“RAT-2”) (not serving Uu), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”)Random Access Response (“RAR”), Resource Block Assignment (“RBA”), Resource Element Group (“REG”), Radio Link Control (“RLC”), RLC Acknowledged Mode (“RLC-AM”), RLC Unacknowledged Mode / Transparent Mode (“RLC-UM / TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Resource Pool (“RP”), Reference Signal (“RS”), Remaining Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Spread Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Received Signal Strength Indicator (“RSSI”), Road Side Unit (“RSU”), Round Trip Time (“RTT”), Receive (“RX”), Receiver User Equipment (“RX UE”), Standalone (“SA”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Subcarrier Spacing (“SCS”), Service Data Unit (“SDU”), Security Anchor Function (“SEAF”), Sidelink Feedback Content Information (“SFCI”), Serving Gateway (“SGW”), System Information Block (“SIB”), System Information Block Type 1 (“SIB1”), System Information Block Type 2 (“SIB2”), Subscriber Identity / Identity Module (“SIM”), Signal-to-Interference plus Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Sidelink Synchronization Signal (“SLSS”), Session Management (“SM”), Session Management Function (“SMF”), Special Cell (“SpCell”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSIRS (“S-CSI RS”), Sidelink PRS (“S-PRS”), Sidelink SSB (“S-SSB”), Synchronization Signal Block (“SSB”), Subscription Concealed Identifier (“SUCI”), Scheduled User Equipment (“SUE”), Supplementary Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Tracking Area (“TA”), TA Identifier (“TAI”), TA Update (“TAU”), Timing Advance Timer (“TAT”), Transport Block (“TB”), Transport Block Size (“TBS”), Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”)Time Division Orthogonal Cover Code (“TD-OCC”), Temporary Mobile Subscriber Identity (“TMSI”), Time of Flight (“ToF”), Transmission Power Control (“TPC”), Transmission and Reception Point (“TRP”), Transmission Time Interval (“TTI”), Transmission (“TX”), Transmitter User Equipment (“TX UE”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User Entity / Device (Mobile Terminal) (“UE”) (e.g., V2X UE), UE Autonomous Mode (UE autonomously selects V2X communication resources - e.g., Mode 2 in NR V2X and Mode 4 in LTE V2X. The UE autonomous selection may or may not be based on resource sensing operations), Uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), User Plane (“UP”), UP Function (“UPF”), Uplink Pilot Time Slot (“UpPTS”), Ultra-Reliable and Low-Latency Communication (“URLLC”), UE Routing Selection Policy (“URSP”), Vehicle-to-Vehicle (“V2V”), Vehicle-to-Everything (“V2X”), V2X UE (e.g., UE capable of in-vehicle communication using 3GPP protocols), Access AMF (“vAMF”), V2X Encryption Key (“VEK”), V2X Group Key (“VGK”), V2X MIKEY Key (“VMK”), Access NSSF (“vNSSF”), Access PLMN (“VPLMN”), V2X Service Key (“VTK”), Wide Area Network (“WAN”) and Worldwide Interoperability for Microwave Access (“WiMAX”).

[0005] In some wireless communication networks, conflicts may occur. Summary of the Invention

[0006] A transmission method based on the type of conflict is disclosed. Apparatuses and systems also perform the functions of these methods. One embodiment of the method includes determining that a first transmission resource corresponding to a first user equipment preempts a second transmission resource corresponding to a second user equipment as a result of a conflict between the first transmission resource and the second transmission resource in a shared resource pool. In some embodiments, the method includes transmitting, from the second user equipment, a request for resource reselection and activation in response to the type of conflict being a periodic conflict or a series conflict; or transmitting, from the second user equipment, a request for resource reselection in response to the type of conflict being a one-time conflict.

[0007] An apparatus for conflict-based type of transmission includes a processor that determines a conflict between a first transmission resource corresponding to a first user equipment and a second transmission resource corresponding to a second user equipment as a result of a conflict between the first transmission resource and the second transmission resource in a shared resource pool. In various embodiments, the apparatus includes a transmitter that: in response to the type of conflict being a periodic conflict or a series conflict, transmits a request for resource reselection and activation from the second user equipment; or, in response to the type of conflict being a one-time conflict, transmits a request for resource reselection from the second user equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more specific description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the drawings. It is understood that these drawings depict only some embodiments and are not to be considered limiting of the scope, and the embodiments will be described and explained with additional specificity and detail by using the drawings, in which:

[0009] Figure 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for conflict-based type of transmission;

[0010] Figure 2 is a schematic block diagram illustrating an embodiment of an apparatus that can be used for conflict-based type of transmission;

[0011] Figure 3 is a schematic block diagram illustrating an embodiment of an apparatus that can be used for conflict-based type of transmission; and

[0012] Figure 4 is a flowchart illustrating an embodiment of a method for conflict-based type of transmission. DETAILED DESCRIPTION

[0013] As will be understood by those skilled in the art, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects that are generally referred to herein as a "circuit", "module", or "system". In addition, the embodiments can take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code hereinafter referred to as code. The storage device can be tangible, non-transitory, and / or non-transmissive. The storage device may not embody a signal. In certain embodiments, the storage device merely employs a signal for accessing the code.

[0014] Some of the functional units described in this specification may be marked as modules to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit including custom very large scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0015] A module may also be implemented in code and / or software for execution by various types of processors. The identified module of code may, for example, include one or more physical or logical blocks of executable code which may, for example, be organized as objects, procedures, or functions. However, the executable files of the identified module need not be physically located together, but may include different instructions stored in different locations which, when logically joined together, include the module and implement the stated purpose of the module.

[0016] In fact, a code module may be a single instruction or many instructions and may even be distributed over several different code segments, different programs, and across several memory devices. Similarly, in this context, the operational data may be identified and illustrated within a module and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed at different locations including on different computer-readable storage devices. In the case where a module or portions of a module are implemented in software, the software portions are stored on one or more computer-readable storage devices.

[0017] Any combination of one or more computer-readable media may be utilized. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0018] More specific examples (a non-exhaustive list) of storage devices will include the following: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0019] The code for performing the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages such as Python, Ruby, Java, Smalltalk, C++, etc., and conventional procedural programming languages such as the "C" programming language, and / or machine languages such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the last scenario, the remote computer can be connected to the user's computer via any type of network including a local area network ("LAN") or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0020] References in this specification to "one embodiment", "an embodiment", or similar language mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, unless otherwise explicitly stated, the appearances of the phrases "in one embodiment", "in an embodiment", and similar language throughout the specification may, but do not necessarily, all refer to the same embodiment, but rather mean "one or more but not all embodiments". Unless otherwise explicitly stated, the terms "comprises", "comprising", "has", and their variants mean "including but not limited to". Unless otherwise explicitly specified, an enumerated listing of items does not imply that any or all of the items are mutually exclusive. Unless otherwise explicitly specified, the terms "a", "an", and "the" also refer to "one or more".

[0021] Furthermore, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0022] Aspects of the embodiments will now be described with reference to the schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed via the processor of the computer or other programmable data processing device create means for implementing the functions / operations specified in the block or blocks of the schematic flowchart and / or schematic block diagram.

[0023] The code can also be stored in a storage device that can direct a computer, other programmable data processing device, or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including the instructions that implement the functions / actions specified in the block or blocks of the schematic flowchart and / or schematic block diagram.

[0024] The code can also be loaded onto a computer, other programmable data processing device, or other device to cause a series of operational steps to be performed on the computer, other programmable device, or other device to produce a computer-implemented process, such that the code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the block or blocks of the flowchart and / or block diagram.

[0025] The schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to different embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams can represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function(s).

[0026] It should also be noted that in some alternative implementations, the functions noted in the blocks may not occur in the order noted in the figures. For example, depending on the functions involved, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order. Other steps and methods that are conceivable are equivalent in function, logic, or effect to one or more blocks or portions of the figures shown.

[0027] Although various arrow types and line types may be employed in flowcharts and / or block diagrams, they are understood not to limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiments. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between the enumerated steps of the depicted embodiments. It will also be noted that each block of the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or by a combination of dedicated hardware and code.

[0028] The description of the elements in each figure may refer to the elements of the previous figure. In all figures, the same reference numerals refer to the same elements, including alternative embodiments of the same element.

[0029] Figure 1 Embodiments of a wireless communication system 100 for conflict-based type transmissions are depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 a specific number of remote units 102 and network units 104 are depicted, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0030] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, laptop computer, personal digital assistant (“PDA”), tablet computer, smart phone, smart TV (e.g., a TV connected to the Internet), set-top box, game console, security system (including security cameras), in-vehicle computer, network device (e.g., router, switch, modem), airborne vehicle, drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, fitness band, optical head-mounted display, etc. Additionally, the remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. The remote unit 102 may communicate directly with one or more of the network unit 104 via UL communication signals. In certain embodiments, the remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0031] Network element 104 can be distributed over a geographical area. In some embodiments, network element 104 may also be referred to as an access point, access terminal, base, base station, Node - B, eNB, gNB, home Node - B, relay node, device, core network, air server, radio access node, AP, NR, network entity, AMF, UDM, UDR, UDM / UDR, PCF, RAN, NSSF, AS, NEF, key management server, KMF, or any other term used in the art. Network element 104 is generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is generally communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network and so on. These and other elements of the radio access and core networks are not shown, but are generally well known to those of ordinary skill in the art.

[0032] In one embodiment, wireless communication system 100 complies with the standardized NR protocol in 3GPP, where network element 104 uses an OFDM modulation scheme for transmission on the DL, and remote unit 102 uses an SC - FDMA scheme or an OFDM scheme for transmission on the UL. However, more generally, wireless communication system 100 may implement some other open or proprietary communication protocols, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfoxx, and other protocols. The present disclosure is not intended to be limited to embodiments of any particular wireless communication system architecture or protocol.

[0033] Network element 104 can serve multiple remote units 102 within a service area such as a cell or cell sector via a wireless communication link. Network element 104 transmits DL communication signals to serve remote units 102 in the time, frequency, and / or spatial domain.

[0034] In various embodiments, remote unit 102 may determine that a first transmission resource corresponding to a first user equipment (e.g., remote unit 102) pre - empts a second transmission resource corresponding to a second user equipment (e.g., remote unit 102) as a result of a conflict between the first transmission resource and the second transmission resource in a shared resource pool. In some embodiments, remote unit 102 may transmit a request for resource reselection and activation from the second user equipment in response to the conflict type being a periodic conflict or a series of conflicts; or, transmit a request for resource reselection from the second user equipment in response to the conflict type being a one - time conflict. Thus, remote unit 102 can be used for transmissions based on the type of conflict.

[0035] Figure 2 FIG. 2 depicts an embodiment of an apparatus 200 that can be used for a type of transmission for conflict. The apparatus 200 includes an embodiment of a remote unit 102. Additionally, the remote unit 102 can include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touch screen. In certain embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 can include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or display 208.

[0036] In one embodiment, the processor 202 can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 202 can be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), a co-processing unit, a field-programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0037] In one embodiment, the memory 204 is a computer-readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 can include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 can include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0038] In one embodiment, input device 206 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 206 includes a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 206 includes two or more different devices such as a keyboard and a touch panel.

[0039] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, display 208 may include a wearable display such as a smart watch, smart glasses, a head-up display, etc. In addition, display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0040] In some embodiments, the display 208 includes one or more speakers for generating sounds. For example, the display 208 can generate an audible alarm or notification (e.g., a buzzer or beep). In some embodiments, the display 208 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or part of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 208 can be positioned near the input device 206.

[0041] The processor 202 may determine that the first transmission resource corresponding to the first user equipment preempts the second transmission resource corresponding to the second user equipment as a result of a conflict between the first transmission resource and the second transmission resource in the shared resource pool. In various embodiments, the transmitter 210 may: in response to the type of conflict being a periodic conflict or a series conflict, transmit a request for resource reselection and activation from the second user equipment; or, in response to the type of conflict being a one-time conflict, transmit a request for resource reselection from the second user equipment.

[0042] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitters 210 and receivers 212 may be of any suitable type of transmitter and receiver. In one embodiment, the transmitters 210 and receivers 212 may be part of a transceiver.

[0043] Figure 3 An embodiment of an apparatus 300 that may be used for conflict-based types of transmissions is depicted. The apparatus 300 includes an embodiment of a network unit 104. Additionally, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may generally be similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively. The transmitter 310 may perform the various transmissions described herein and the receiver 312 may receive the various messages described herein.

[0044] In various embodiments, SL preemption may be used to enable high-priority packet delivery by a UE in congested scenarios where it may be difficult to find candidate resources within the packet delivery budget.

[0045] In some embodiments, a UE that receives a preemption indication from another UE may need to perform resource reselection. In such embodiments, the mechanism for resource reselection for the preempted UE may need to consider the periodic or aperiodic traffic types allocated via the configured grant process and / or the dynamic grant process by NR mode 1 and mode 2 operations.

[0046] In certain embodiments, multi-carrier and multi-panel support may be used, where the number of supported simultaneous SL carriers may depend on the number of dedicated TX and / or RX chains available for side-link communication and / or power sharing.

[0047] In various embodiments, the number of TX and / or RF chains may be greater than the number of SL carriers. In some embodiments, if high-priority traffic is to be transmitted, carrier reselection may be performed, and the preempted UE may also trigger carrier reselection. In certain embodiments, if carrier reselection is performed, resources reserved for retransmissions in previous SL carriers may be released for other UEs.

[0048] In some embodiments, during simultaneous SL transmissions, power sharing may exist among the SL carriers, and in certain embodiments, the transmit power may be insufficient to meet the QoS configured in a given communication range (e.g., MCR).

[0049] As used herein, Mode 1 may refer to an embodiment in which the BS scheduling is to be used by the UE for SL transmission of SL resources. Additionally, as used herein, Mode 2 may refer to an embodiment in which the UE determines (e.g., the BS does not schedule) SL transmission resources within SL resources configured by the BS and / or the network or pre-configured SL resources.

[0050] In various embodiments, the definition of SL resource allocation Mode 2 may cover: a) the UE autonomously selects SL resources for transmission; b) the UE assists in selecting SL resources for other UEs (e.g., may be part of a), c), or d)); c) the UE is configured with a grant of NR configuration for SL transmission (e.g., as type-1); and / or d) the UE schedules SL transmissions of other UEs.

[0051] In some embodiments, resource allocation Mode 2 may support reserving at least SL resources for blind retransmission. In certain embodiments, sensing and resource reselection may include sensing and / or resource reselection related processes supported by resource allocation Mode 2. In various embodiments, the sensing process may be defined as decoding SCI from other UEs and / or SL measurements. In some embodiments, decoding the SCI may provide information about the SL resources indicated by the UE transmitting the SCI. In certain embodiments, if the corresponding SCI is decoded, the sensing process uses L1 SL RSRP measurements based on SL DMRS.

[0052] In various embodiments, the resource reselection process may use the results of the sensing process to determine resources for SL transmission.

[0053] As used herein, the terms eNB and / or gNB may be used for the base station, but may be replaced by any other radio access node (e.g., BS, eNB, gNB, AP, and / or NR). Additionally, although the various embodiments described herein may be described in the context of 5G NR, the embodiments described herein may be applicable to other mobile communication systems supporting a serving cell and / or a carrier configured for sidelink communication (e.g., via the PC5 interface).

[0054] Table 1 shows various embodiments for handling resource conflicts by summarizing TX UE behavior based on the type of conflict between UEs. In all scenarios of Table 1, the TX UE is the preempted UE that needs resource selection and / or reselection to find new candidate resources to transmit the preempted resources.

[0055] Table 1

[0056]

[0057]

[0058]

[0059] In various embodiments, if there is a resource conflict between mode 1 and mode 2 on a shared resource pool, the TX UE behavior can depend on the type of conflict between UEs, which can be: a periodic or series of conflicts of resources that can cause an initial transmission and / or a reserved transmission, and in another embodiment, a one-time conflict between them. In some embodiments, after receiving and decoding signaling for a preemption indication or a reservation indication that also indicates the priority of packet transmission, lower-priority V2X and / or SL UEs can perform resource selection and / or reselection based on the type of conflict and the TX UE behavior can depend on the operating mode (e.g., mode 1 or mode 2).

[0060] In certain embodiments, if a TX UE in high-priority mode 2 CG resources pre-empts a transmitting mode 1 CG resource and there is a periodic or series of resource conflicts between them, the TX UE signals the gNB for resource selection and / or reselection for low-priority traffic.

[0061] In various embodiments, the TX UE can be triggered to transmit UE assistance information via L3 signaling (e.g., RRC signaling) to notify the gNB of the conflict of CG resources and / or indicate whether there is a conflict with initial and / or reserved resources. In some embodiments, if a resource conflict occurs for all or part of the CG resources, the gNB can activate another CG resource, the gNB can deactivate the previous CG resource, and / or the gNB can activate another resource based on the assistance information regarding the conflict. In certain embodiments, the UE can implicitly deactivate the CG resource and / or notify the gNB in the assistance information regarding the need to activate another CG resource. In various embodiments, the UE assistance information is in an RRC message, which can be an event triggered by the TX-UE after receiving a resource reservation and / or preemption indication, and / or can be transmitted periodically by the TX-UE. In some embodiments, other L1 signaling can be used to provide information to the gNB via uplink transmission.

[0062] In certain embodiments, the TX UE performs an SR or BSR transmission after receiving, for example, a resource reservation request or a preemption indication and / or assistance information for resource selection and / or reselection via a MAC CE as part of L1 and / or L2 signaling.

[0063] In various embodiments, for certain mode 1 and mode 2 of a shared resource pool, there is a one-time or single resource conflict between UEs, and the TX UE signals the gNB for resource selection and / or reselection for low-priority traffic.

[0064] In some embodiments, the TX UE transmits SL HARQ-NACK feedback to the gNB in the UL-PUCCH resource to indicate the need for transmission and / or retransmission resources.

[0065] In certain embodiments, mode 2 operation can be utilized to transmit mode 1 preemption resources, where the T2 value is selected based on the remaining PDB budget, and optionally an ACK can be transmitted in the SL HARQ feedback sent to the gNB. The ACK can be sent before mode 2 transmission and / or retransmission without waiting for the SL ACK and / or NACK feedback from the RX UE.

[0066] In various embodiments where the V2X UE and / or SL UE autonomously select resources, if a high-priority mode 1 grant preempts a low-priority mode 2 V2X UE and / or SL UE and there is a one-time or single-shot resource conflict between them, resource selection and / or reselection can be triggered by the mode 2 V2X UE and can be based on the remaining PDB budget (e.g., the shorter the remaining PDB, the higher the priority assigned to the preempting packet (lower numerically) to increase the priority of the preempting packet.

[0067] In some embodiments, for mode 1 resource conflicts (e.g., between UEs), the TX UE can receive and / or decode a PI from another UE before or at the same time as processing or generating an SCI based on a first DCI grant. In certain embodiments, there may be a one-time or single-shot resource conflict between UEs, and then the TX UE signals to the gNB for resource selection and / or reselection for mode 1 grants. In various embodiments, in response to there being a shared resource pool between mode 1 and mode 2, due to different V2X priority levels and low-latency V2X packet transmissions, mode 1 inter-UE resource conflicts can occur in separate resource pools allocated for mode 1.

[0068] In some embodiments, the TX UE may not generate and transmit an SCI for low-priority traffic, and the TX UE can transmit SL HARQ-NACK to the gNB in the PUCCH resource.

[0069] In certain embodiments, mode 1 preemption resources can be transmitted and / or retransmitted using mode 2 operation, and optionally an ACK sent to the gNB can be transmitted. The ACK can be sent before mode 2 transmission and / or retransmission without waiting for the SL ACK and / or NACK feedback from the RX UE.

[0070] In various embodiments, for mode 2 resource conflicts (e.g., within a UE), the sensing operation for monitoring and / or decoding the SCI can occur in each time slot and if the UE receives a resource selection and / or reselection trigger, and if there are any V2X packets for transmission, the UE can select an appropriate T1 value based on its processing capabilities, and within the T1 value, the TX UE can perform a resource exclusion and / or candidate resource set selection process and can report it to the MAC layer. The MAC layer can randomly select a resource for transmission from the set within the PDB.

[0071] In some embodiments, the TX UE can generate another trigger for resource selection and / or reselection for higher-priority V2X packets while processing the current resource selection and / or reselection trigger within the T1 value.

[0072] In certain embodiments, the MAC selects candidate resources for high-priority packet transmission based on the resource set selected by the PHY, and the resource selection and / or reselection can be triggered for the lowest-priority packet transmission with the remaining PDB budget.

[0073] In various embodiments, the priority of the pre-emptive packet can be increased based on the remaining PDB budget (e.g., the shorter the remaining PDB, the higher the priority assigned to the pre-emptive packet (lower numerically)).

[0074] In some embodiments, if the TX UE or gNB does not find a resource in the same SL component carrier or SL BWP, the TX UE or gNB can trigger carrier selection and / or reselection or BWP selection and / or reselection to find a resource within the remaining PDB for pre-empting the UE, where the BWP can be in the same SL component carrier of different SL component carriers and / or configured with the same or different parameter sets as the previous one.

[0075] In certain embodiments: 1) not all V2X and / or SL UE packet priorities can emit a pre-emption indication; 2) the quality of resource selection can be for reliable transmission and / or reception; and / or 3) there can be a handover criterion for configured grant type 1.

[0076] In various embodiments, the gNB can emit information about the SL-LCH priority, PQI value, PDB value, latency value, and / or CBR threshold for SL-UE pre-emption in the SIB and / or in a dedicated RRC configuration message, such that not all V2X and / or SLUE-generated traffic priorities can emit a pre-emption indication.

[0077] In some embodiments, in an autonomous resource selection method (e.g., NR mode 2), if the candidate resource set SA of the TX UE is less than 20% of the total resources based on a certain RSRP and / or RSSI threshold, the TX UE may adjust the RSRP and / or RSSI threshold and may perform candidate resource selection. In certain embodiments, to ensure lower latency and reliable packet transmission and / or reception, the gNB may configure the RSRP and / or RSSI threshold, or may be configured and / or pre-configured for candidate resource selection based on PQI, PDB, latency, and / or CBR values.

[0078] In various embodiments, the gNB may signal via configuration and / or via configuration in RRC signaling when to use SL configuration grant type 1 resources (e.g., without grant) for V2X transmission, and / or the corresponding resource selection method (e.g., random and / or partial sensing). Separate configuration grant type 1 resources and / or resource pools may be configured for specific destination group IDs to minimize conflicts.

[0079] In some embodiments, if the latency and / or PDB of V2X packet transmission is less than or equal to the T1 value (e.g., T1 is the UE physical layer processing time), the TX UE may select to transmit V2X and / or SL packets via the configured grant type 1 resource pool. In such embodiments, the TX-UE may transmit a resource reservation request and / or a preemption indication for the configured grant type 1 resource pool in advance. In certain embodiments, the TX UE may perform random resource selection and / or partial sensing (e.g., based on decoding of one or several previous time slots) on the configured grant type 1 resource pool and the corresponding sensing and resource selection method, which may be configured and / or pre-configured and the gNB may signal random resource selection and / or partial sensing.

[0080] In various embodiments, execution of sidelink carrier selection and / or reselection and / or BWP selection and / or reselection may be caused by one of the following: 1) the number of TX and / or RF chains < the maximum number of supported SL carriers or BWPs; 2) TX power budget issues due to power sharing constraints among multiple sidelink carriers caused by simultaneous transmission; and / or 3) TX power budget constraints provided to the RX UE within the MCR due to insufficient transmit power.

[0081] In some embodiments, before carrier selection and / or reselection, resources reserved for blind or HARQ transmissions and / or retransmissions of transport blocks (TBs) in the current SL carrier or BWP can be released for other UEs. In certain embodiments, for NR mode 1, the TX UE can transmit UE assistance information to the gNB and / or transmit SL-HARQ-ACK feedback in the configured UL-PUCCH resources, which indicates the released reserved resources to schedule other SL and / or V2X UEs. In various embodiments, for NR mode 2, the TX UE can indicate the release of reserved resources by transmitting an independent PSCCH resource or setting the reserved interval field in the SCI to zero using the last data transmission (e.g., PSCCH+PSSCH) to all surrounding UEs with a broadcast destination ID.

[0082] In certain embodiments, in the V2X autonomous resource selection method (e.g., NR mode 2), the steps can include a sensing operation of monitoring and decoding the SCI and / or resource exclusion. In such embodiments, candidate resource selection can occur for each individual sidelink component carrier or SL-BWP, and the higher layer can provide the V2X service type to the SL component carrier mapping information.

[0083] In some embodiments, higher-priority V2X UEs and / or SL UEs can trigger resource selection and / or reselection in one or more sidelink component carriers and / or SL BWPs simultaneously, and can start the resource exclusion and candidate resource selection process in one or more carriers or BWPs after receiving the resource selection and / or reselection trigger (e.g., the resource selection and / or reselection trigger for each BWP and / or CC). In such embodiments, if the candidate resource is first found within the PDB, the TX-UE can select to transmit only in a given sidelink component carrier or SL BWP.

[0084] In various embodiments, if sidelink component carriers or SL BWPs within the same frequency band are close to each other - which can occur in wider bandwidth operations at millimeter wave frequencies, and there is not enough guard separation in frequency between the carriers or SL BWPs, this can lead to a half-duplex problem, which means that if a UE transmits and / or receives on a carrier or SL BWP, the same UE cannot receive and / or transmit on an adjacent carrier or SL BWP in the same time slot. Such embodiments can cause problems for low-latency V2X and / or SL operations, where many time slots cannot be used to schedule urgent sidelink transmissions.

[0085] In some embodiments, the gNB, configuration, and / or pre-configuration may configure the TX UE with RRC signaling regarding SL carrier groups and / or SL BWP groups from multiple supported SL carriers or SL BWPs, and the UE may be configured with separate sensing operations for each individual SL carrier or SL BWP, but there may be joint resource exclusion and / or joint candidate resource selection on the configured SL carrier groups and / or SL BWP groups.

[0086] In some embodiments, the gNB, configuration, and / or pre-configuration may configure the TX UE with RRC signaling regarding SL carrier groups and / or SL BWP groups from multiple supported SL carriers or SL BWPs, and the configuration message may only indicate to perform the joint candidate resource selection process among the SL carrier groups or SL BWP groups. In such embodiments, during the sensing operation, resource exclusion may occur for each individual SL carrier or SL BWP.

[0087] In various embodiments, configuration messages from the TX-UE, RSU, and / or S-UE may be transmitted via PC5 RRC signaling regarding the embodiments for use by the RX UEs in the group for unicast and / or multicast transmissions.

[0088] In some embodiments, the V2X UE may be equipped with multiple distributed antenna panels and / or beams, and these may be directional in nature and combined with millimeter wave frequencies. The directivity may determine the desired boresight angle (e.g., azimuth, elevation, or both) and the maximum gain axis (e.g., maximum radiated power) for the transmission beam (e.g., for reference). In some embodiments, the range may be conditional on the indicated directivity (e.g., the QoS parameter indicating the angular direction (e.g., the direction of the boresight angle with a certain (e.g., reference) beamwidth for (e.g., reference) transmission) requires the minimum distance in the beam to be fulfilled). In various embodiments, based on the directivity parameters, the UE L1 and / or L2 may determine the spatial domain transmission filter to be used to meet the desired directivity and range characteristics of the transmission. In some embodiments, the spatial domain transmission filter may include determining one or more antenna panels, arrays, and / or sub-arrays from the set of antenna panels and / or arrays at the UE, and / or may transmit precoded antenna element weights for use. In some embodiments, the precoding may be digital precoding or a combination of digital and analog precoding (e.g., hybrid precoding).

[0089] In various embodiments, to select the best resources for multicast transmission for beam scanning or multi-beam operation in NR mode 2, gNB signaling, configuration, or pre-configuration may provide details about antenna panel groups or beam groups, where a group may be formed by multiple antenna panels, beams, arrays, and / or sub-arrays. In such embodiments, one or more groups may be formed for V2X UEs based on the transmission type and / or carrier frequency.

[0090] In certain embodiments, the UE may be configured with sensing operations, including monitoring and / or decoding SCI and / or measuring RSRP and / or RSSI from PSCCH and / or PSSCH, which may be performed for individual antenna panels or beams equipped in the V2X UE. In such embodiments, there may be joint resource exclusion and / or joint candidate resource selection from the configured groups.

[0091] In some embodiments, the configuration message may only indicate the process of performing joint candidate resource selection and sensing operations from the configured groups. In such embodiments, resource exclusion may occur for each individual antenna panel, beam, array, and / or sub-array.

[0092] In various embodiments, the configuration message may be used to indicate joint sensing, joint resource exclusion, and / or joint candidate selection from multiple groups or from a single group.

[0093] Figure 4 FIG. 400 is a flowchart illustrating an embodiment of a method 400 for transmission based on the type of conflict. In some embodiments, method 400 is performed by a device such as remote unit 102. In certain embodiments, method 400 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0094] In various embodiments, method 400 includes determining 402 that a first transmission resource corresponding to a first user equipment preempts a second transmission resource corresponding to a second user equipment as a result of a conflict between the first transmission resource and the second transmission resource in a shared resource pool. In some embodiments, method 400 includes transmitting 404 a request for resource reselection and activation from the second user equipment in response to the type of conflict being a periodic conflict or a series of conflicts; or, transmitting a request for resource reselection from the second user equipment in response to the type of conflict being a one-time conflict.

[0095] In certain embodiments, the type of conflict is a periodic conflict. In some embodiments, the type of conflict is a series of conflicts. In various embodiments, the first transmission resource is a grant resource configured in mode 2, and the second transmission resource is a grant resource configured in mode 1.

[0096] In one embodiment, the first transmission resource has a higher priority than the second transmission resource. In certain embodiments, requests for resource reselection and activation are directed to configured grant resources. In some embodiments, method 400 further includes transmitting user equipment assistance information indicating the duration of the conflict, the resources of the conflict, or a combination thereof.

[0097] In various embodiments, method 400 further includes transmitting a scheduling request, a buffer status report, or a combination thereof in response to determining that the first transmission resource pre-empts the second transmission resource. In one embodiment, the first transmission resource is a mode 2 dynamic resource and the second transmission resource is a mode 1 dynamic resource. In certain embodiments, the first transmission resource is a mode 2 dynamic resource and the second transmission resource is a mode 1 configured grant resource.

[0098] In some embodiments, the first transmission resource is a mode 2 configured grant resource and the second transmission resource is a mode 1 dynamic resource. In various embodiments, the first transmission resource is a mode 1 configured grant resource and the second transmission resource is a mode 2 dynamic resource. In one embodiment, the first transmission resource is a mode 1 resource and the second transmission resource is a mode 1 resource.

[0099] In certain embodiments, the request includes a sidelink hybrid automatic repeat request negative acknowledgment. In some embodiments, the sidelink hybrid automatic repeat request negative acknowledgment is transmitted on a physical uplink control channel. In various embodiments, method 400 further includes retransmitting the second transmission resource using mode 2 operation, wherein the pre-empted second transmission resource is mode 1 operation.

[0100] In one embodiment, method 400 further includes transmitting an affirmative feedback message. In certain embodiments, in response to the second user equipment operating in mode 1, the request for resource reselection transmitted is from the second user equipment to the network element.

[0101] In one embodiment, a method includes: determining that a first transmission resource corresponding to a first user equipment pre-empts a second transmission resource corresponding to a second user equipment as a result of a conflict between the first transmission resource and the second transmission resource in a shared resource pool; and in response to the type of conflict being a periodic conflict or a series conflict, transmitting, from the second user equipment, a request for resource reselection and activation; or, in response to the type of conflict being a one-time conflict, transmitting, from the second user equipment, a request for resource reselection.

[0102] In certain embodiments, the type of conflict is a periodic conflict.

[0103] In some embodiments, the type of conflict is a series conflict.

[0104] In various embodiments, the first transmission resource is a licensed resource configured in mode 2, and the second transmission resource is a licensed resource configured in mode 1.

[0105] In one embodiment, the first transmission resource has a higher priority than the second transmission resource.

[0106] In certain embodiments, the request for resource reselection and activation is for a configured licensed resource.

[0107] In some embodiments, the method further includes transmitting user equipment assistance information indicating the duration of the conflict, the resources of the conflict, or a combination thereof.

[0108] In various embodiments, the method further includes: in response to determining that the first transmission resource pre-empts the second transmission resource, transmitting a scheduling request, a buffer status report, or a combination thereof.

[0109] In one embodiment, the first transmission resource is a mode 2 dynamic resource, and the second transmission resource is a mode 1 dynamic resource.

[0110] In certain embodiments, the first transmission resource is a mode 2 dynamic resource and the second transmission resource is a mode 1 configured licensed resource.

[0111] In some embodiments, the first transmission resource is a mode 2 configured licensed resource, and the second transmission resource is a mode 1 dynamic resource.

[0112] In various embodiments, the first transmission resource is a mode 1 configured licensed resource, and the second transmission resource is a mode 2 dynamic resource.

[0113] In one embodiment, the first transmission resource is a mode 1 resource and the second transmission resource is a mode 1 resource.

[0114] In certain embodiments, the request includes a sidelink hybrid automatic repeat request negative acknowledgment.

[0115] In some embodiments, the sidelink hybrid automatic repeat request negative acknowledgment is transmitted on a physical uplink control channel.

[0116] In various embodiments, the method further includes retransmitting the second transmission resource using mode 2 operation, wherein the pre-empted second transmission resource is in mode 1 operation.

[0117] In one embodiment, the method further includes transmitting an affirmative feedback message.

[0118] In certain embodiments, in response to the second user equipment operating in mode 1, the request for resource reselection transmitted is from the second user equipment to a network element.

[0119] In one embodiment, a device includes: a processor that determines a conflict between a first transmission resource corresponding to a first user equipment and a second transmission resource corresponding to a second user equipment as a result of a conflict between the first transmission resource and the second transmission resource in a shared resource pool; and a transmitter: the transmitter transmits, in response to the type of conflict being a periodic conflict or a series conflict, a request for resource reselection and activation from the second user equipment; or, in response to the type of conflict being a one-time conflict, transmits a request for resource reselection from the second user equipment.

[0120] In certain embodiments, the type of conflict is a periodic conflict.

[0121] In some embodiments, the type of conflict is a series conflict.

[0122] In various embodiments, the first transmission resource is a licensed resource configured in mode 2, and the second transmission resource is a licensed resource configured in mode 1.

[0123] In one embodiment, the first transmission resource has a higher priority than the second transmission resource.

[0124] In certain embodiments, the request for resource reselection and activation is for a configured licensed resource.

[0125] In some embodiments, the transmitter transmits user equipment assistance information indicating the duration of the conflict, the resources of the conflict, or a combination thereof.

[0126] In various embodiments, in response to determining that the first transmission resource pre-empts the second transmission resource, the transmitter transmits a scheduling request, a buffer status report, or a combination thereof.

[0127] In one embodiment, the first transmission resource is a mode 2 dynamic resource and the second transmission resource is a mode 1 dynamic resource.

[0128] In certain embodiments, the first transmission resource is a mode 2 dynamic resource and the second transmission resource is a licensed resource configured in mode 1.

[0129] In some embodiments, the first transmission resource is a licensed resource configured in mode 2, and the second transmission resource is a mode 1 dynamic resource.

[0130] In various embodiments, the first transmission resource is a licensed resource configured in mode 1, and the second transmission resource is a mode 2 dynamic resource.

[0131] In one embodiment, the first transmission resource is a mode 1 resource and the second transmission resource is a mode 1 resource.

[0132] In certain embodiments, the request includes a side link hybrid automatic repeat request negative acknowledgment.

[0133] In some embodiments, the sidelink hybrid automatic repeat request negative acknowledgment is transmitted in the physical uplink control channel.

[0134] In various embodiments, the transmitter retransmits the second transmission resource by mode 2 operation, and the preempted second transmission resource is mode 1 operation.

[0135] In one embodiment, the transmitter transmits an acknowledgment message.

[0136] In certain embodiments, in response to the second user equipment operating in mode 1, the request for resource reselection transmitted is from the second user equipment to the network element.

[0137] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. Accordingly, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A method performed by a user equipment (UE), comprising: Determining that the first transmission resource preempts the second transmission resource based on a conflict between the first transmission resource corresponding to a first UE and the second transmission resource corresponding to a second UE in a shared resource pool; Transmitting, in response to the conflict type being a periodic conflict or a series conflict, a request for resource reselection and activation from the second UE; Or Transmitting, in response to the conflict type being a one-time conflict, the request for resource reselection from the second UE; Performing a retransmission on the second resource using mode 2 operation, wherein the preempted second resource is mode 1 operation.

2. The method according to claim 1, wherein, The first transmission resource is a licensed resource configured in mode 2, and the second transmission resource is a licensed resource configured in mode 1.

3. The method according to claim 1, wherein The first transmission resource has a higher priority than the second transmission resource.

4. The method according to claim 1, wherein, The request for resource reselection is for deactivation of a first configured licensed resource and activation of a second configured licensed resource.

5. The method according to claim 1, further comprising transmitting a scheduling request (SR), a buffer status report (BSR), or both, in response to determining that the first transmission resource preempts the second transmission resource.

6. The method according to claim 1, wherein The first transmission resource is a mode 2 dynamic resource, and the second transmission resource is a mode 1 dynamic resource.

7. The method according to claim 1, wherein The first transmission resource is a mode 2 dynamic resource and the second transmission resource is a mode 1 configured licensed resource.

8. The method according to claim 1, wherein The first transmission resource is a mode 2 configured licensed resource, and the second transmission resource is a mode 1 dynamic resource.

9. The method according to claim 1, wherein, The first transmission resource is a mode 1 configured licensed resource, and the second transmission resource is a mode 2 dynamic resource.

10. The method according to claim 1, wherein, The first transmission resource is a mode 1 resource and the second transmission resource is a mode 1 resource.

11. The method according to claim 1, wherein, The request includes a sidelink hybrid automatic repeat request (HARQ) negative acknowledgment (NACK).

12. The method according to claim 11, wherein, The sidelink HARQ-NACK is transmitted in a physical uplink control channel (PUCCH).

13. The method according to claim 1, further comprising transmitting UE assistance information indicating the duration of the conflict, the resources of the conflict, or both.

14. The method according to claim 13, further comprising transmitting an affirmative feedback message.

15. A second user equipment (UE), comprising: At least one memory; And At least one processor, the at least one processor being coupled to the at least one memory and configured to cause the second UE to: Determine that the first transmission resource preempts the second transmission resource based on a conflict between the first transmission resource corresponding to a first UE and the second resource corresponding to a second UE in a shared resource pool; Transmit a request for resource reselection and activation in response to the conflict type being a periodic conflict or a series conflict; Or Transmit a request for resource reselection in response to the conflict type being a one-time conflict; Perform a retransmission on the second resource using mode 2 operation, wherein the preempted second resource is mode 1 operation.

16. The second UE according to claim 15, wherein, The first transmission resource is a licensed resource configured in mode 2, and the second transmission resource is a licensed resource configured in mode 1.

17. The second UE according to claim 15, wherein, The first transmission resource has a higher priority than the second transmission resource.

18. The second UE according to claim 15, wherein, The request for resource reselection is used for deactivation of the licensed resource configured in the first configuration and activation of the licensed resource configured in the second configuration.

19. The second UE according to claim 15, further comprising transmitting a scheduling request (SR), a buffer status report (BSR), or both, in response to determining that the first transmission resource pre-empts the second transmission resource.

20. The second UE according to claim 15, wherein, The first transmission resource is a mode 2 dynamic resource, and the second transmission resource is a mode 1 dynamic resource.

Images