Determining transmissions to avoid

Abstract

Devices, methods, and systems are disclosed for determining transmissions to avoid. One method (600) includes receiving (602), at a first user equipment from a second user equipment, information indicating a second resource used by the second user equipment for a second transmission to a third user equipment. The method (600) includes determining (604) whether the second resource used by the second user equipment for the second transmission to the third user equipment overlaps a first resource used by the first user equipment for a first transmission to the third user equipment. The method (600) includes determining (606), based on a destination identifier, a logical channel prioritization procedure, or a combination thereof, whether to avoid the first transmission on the first resource in response to determining that the second resource overlaps the first resource.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Patent Application No. 63 / 026,403, filed May 18, 2020, entitled “Apparatus, methods, and systems for SL resource selection enhancement to avoid consecutive packet loss”, and U.S. Patent Application No. 63 / 026,425, filed May 18, 2020, entitled “Apparatus, methods, and systems for receiver assistance to avoid consecutive errors in sidelink”, both of which are incorporated herein by reference in their entirety. Technical Field

[0003] The subject matter disclosed in this article generally relates to wireless communication, and more specifically, to identifying transmissions to be avoided. Background Technology

[0004] In some wireless communication networks, half-duplex transmission can be used. Such transmissions may overlap and / or interfere with each other. Summary of the Invention

[0005] Methods for determining transmissions to be avoided are disclosed. Devices and systems also perform the functions of said methods. One embodiment of a method includes receiving information at a first user equipment (UE) from a second user equipment (BUE) indicating a second resource used by the BUE for a second transmission to a third user equipment (BUE). In some embodiments, the method includes determining whether the second resource used by the BUE for the second transmission to the BUE overlaps with a first resource used by the BUE for a first transmission to the BUE. In some embodiments, the method includes determining whether to avoid the first transmission on the first resource based on a destination identifier, a logical channel priority ordering procedure, or a combination thereof, in response to determining that the second resource overlaps with the first resource.

[0006] An apparatus for determining a transmission to be avoided includes a receiver receiving information from a second user equipment (User Equipment), the information indicating a second resource used by the second User Equipment to make a second transmission to a third User Equipment. In various embodiments, the apparatus includes a processor that: determines whether the second resource used by the second User Equipment to make the second transmission to the third User Equipment overlaps with a first resource used by the first User Equipment to make a first transmission to the third User Equipment; and, in response to determining that the second resource overlaps with the first resource, determines whether to avoid the first transmission on the first resource based on a destination identifier, a logical channel priority ordering procedure, or a combination thereof.

[0007] An embodiment of a method for triggering a change includes receiving trigger information at a first user equipment, the trigger information triggering a change in a resource allocator mode or a change in a communication protocol. In some embodiments, the method includes changing the resource allocator mode or changing the communication protocol in response to receiving the trigger information.

[0008] An apparatus for triggering a change includes a receiver receiving trigger information that triggers a change in a resource allocator mode or a change in a communication protocol. In various embodiments, the apparatus includes a processor that, in response to receiving the trigger information, changes the resource allocator mode or changes the communication protocol. Attached Figure Description

[0009] A more specific description of the embodiments briefly described above will be presented with reference to the specific embodiments illustrated in the accompanying drawings. It should be understood that these figures depict only some embodiments and therefore should not be considered as limiting the scope. The embodiments will be described and explained with additional specificity and detail using the accompanying drawings, in which:

[0010] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system used to determine transmissions to be avoided;

[0011] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used to determine transmissions to be avoided;

[0012] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used to determine transmissions to be avoided;

[0013] Figure 4 This is a timing diagram illustrating an embodiment of half-duplex transmission interference;

[0014] Figure 5 This is a schematic block diagram illustrating one embodiment of communication between user equipment;

[0015] Figure 6 This is a flowchart illustrating one embodiment of a method for determining transmissions to be avoided; and

[0016] Figure 7 This is a flowchart illustrating one embodiment of a method for triggering changes. Detailed Implementation

[0017] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, device, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, all of which are collectively referred to herein as “circuit,” “module,” or “system.” Furthermore, 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-transferable. The storage device may not embody signals. In one embodiment, the storage device employs only signals for accessing code.

[0018] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as hardware circuitry including custom-designed very large-scale integrated circuits (“VLSI”) or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices, such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0019] Modules can also be implemented in code and / or software for execution by various types of processors. An identified code module may, for example, contain one or more physical or logical blocks of executable code, which may be organized, for example, as objects, programs, or functions. However, the executable file of an identified module does not necessarily need to be physically located together, but may contain different instructions stored in different locations that, when logically combined, encompass the module and implement the stated purpose of the module.

[0020] In practice, a code module can be a single instruction, or many instructions, and can even be distributed across several different code segments in different programs, spanning several memory devices. Similarly, operational data can be identified and described within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be aggregated into a single dataset or distributed across different locations, including across different computer-readable storage devices. Where a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0021] Any combination of one or more computer-readable media may be used. The computer-readable media may be a computer-readable storage medium. The computer-readable storage medium may be a storage device for storing code. The storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, devices, or apparatuses, or any suitable combination thereof.

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

[0023] The code used to perform 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 regular programming languages ​​(such as the "C" programming language, etc.) 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 standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter context, 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 through an Internet service provider).

[0024] Throughout this specification, references to "an embodiment," "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. Therefore, unless expressly specified otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily all refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly specified otherwise, the terms "comprising," "including," "having," and variations thereof mean "comprising but not limited to." Unless expressly specified otherwise, the enumerated list of items does not imply that any or all items are mutually exclusive. Unless expressly specified otherwise, the terms "a / an" and "described" also mean "one or more."

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

[0026] The following describes aspects of embodiments with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It should be understood that each block of the schematic flowcharts and / or schematic block diagrams, as well as combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executable via the processor of the computer or other programmable data processing apparatus create components for implementing the functions / actions specified in one or more of the schematic flowcharts and / or schematic block diagram blocks.

[0027] The code may also be stored in a storage device that can direct a computer, other programmable data processing equipment or other means to function in a particular manner, such that the instructions stored in the storage device produce an article of writing containing instructions that implement functions / actions specified in one or more schematic flowcharts and / or schematic block diagrams.

[0028] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable device provides a process for implementing a function / action specified in one or more flowcharts and / or block diagrams.

[0029] The schematic flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each box in the schematic flowcharts and / or block diagrams may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function.

[0030] It should also be noted that in some alternative implementations, the functions marked in the boxes may not occur in the order indicated in the figures. For example, depending on the functions involved, two boxes shown consecutively may actually be executed substantially simultaneously, or the boxes may sometimes be executed in reverse order. Other steps and methods are conceivable that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated diagrams.

[0031] While various arrow and line types may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connection forms may be used only to indicate the logical flow of the depicted embodiment. For example, arrows may indicate wait or monitoring periods of unspecified duration between the listed steps of the depicted embodiment. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs the specified function or action, or a combination of dedicated hardware and code.

[0032] The description of the elements in each figure can be found in the elements of the subsequent figures. In all figures, the same numbers refer to the same elements, and alternative embodiments containing the same elements are also included.

[0033] Figure 1 An embodiment of a wireless communication system 100 for determining transmissions to be avoided is described. 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, but those skilled in the art will recognize that the wireless communication system 100 may contain any number of remote units 102 and network units 104.

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

[0035] Network unit 104 may be distributed across a geographical area. In some embodiments, network unit 104 may also be referred to as and / or may include one or more of the following: access point, access terminal, base station, base station, location server, core network (“CN”), radio network entity, Node-B, evolved node-B (“eNB”), 5G. The term Node-B (“gNB”), Home Node-B, Relay Node, Device, Core Network, Air Server, Radio Access Node, Access Point (“AP”), New Radio (“NR”), Network Entity, Access and Mobility Management Function (“AMF”), Unified Data Management (“UDM”), Unified Data Repository (“UDR”), UDM / UDR, Policy Control Function (“PCF”), Radio Access Network (“RAN”), Network Slice Selection Function (“NSSF”), Operations, Administration and Management (“OAM”), Session Management Function (“SMF”), User Plane Function (“UPF”), Application Function, Authentication Server Function (“AUSF”), Security Anchoring Functionality (“SEAF”), Trusted Non-3GPP Gateway Functionality (“TNGF”), or any other term used in the field. Network Unit 104 is typically a portion of a radio access network comprising one or more controllers communicatively coupled to one or more corresponding Network Units 104. Radio access networks are typically communicatively coupled to one or more core networks, which in turn may be coupled to other networks such as the Internet and the public switched telephone network, as well as other networks. These and other components of the radio access and core networks are not illustrated, but are generally well known to those skilled in the art.

[0036] In one implementation, the wireless communication system 100 is compatible with the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), wherein network unit 104 uses an OFDM modulation scheme for transmission on the downlink (“DL”) and remote unit 102 uses a single-carrier frequency division multiple access (“SC-FDMA”) or orthogonal frequency division multiplexing (“OFDM”) scheme for transmission on the uplink (“UL”). However, more generally, the wireless communication system 100 may implement another open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, or CDMA2000. ZigBee, Sigfoxx, and other protocols. This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0037] Network unit 104 can serve several remote units 102 within a service area (e.g., a cell or cell sector) via a wireless communication link. Network unit 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0038] In various embodiments, remote unit 102 may receive information at a first user equipment (UE) from a second user equipment (UE) indicating a second resource used by the second UE for a second transmission to a third UE. In some embodiments, remote unit 102 may determine whether the second resource used by the second UE for the second transmission to the third UE overlaps with a first resource used by the first UE for a first transmission to the third UE. In some embodiments, remote unit 102 may determine whether to avoid the first transmission on the first resource based on a destination identifier, a logical channel priority ordering procedure, or a combination thereof, in response to determining that the second resource overlaps with the first resource. Therefore, remote unit 102 may be used to determine the transmission to be avoided.

[0039] In some embodiments, remote unit 102 may receive triggering information at a first user equipment, the triggering information triggering a change in resource allocation procedure mode or a change in communication protocol. In some embodiments, remote unit 102 may change the resource allocation procedure mode or change the communication protocol in response to receiving the triggering information. Therefore, remote unit 102 can be used to trigger changes.

[0040] Figure 2An embodiment of a device 200 is depicted for use in determining transmissions to be avoided. Device 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may 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 touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include an input device 206 and / or display 208.

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

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

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

[0044] 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, a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic light-emitting diode (“OLED”) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include a wearable display, such as a smartwatch, smart glasses, a head-up display, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0045] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate auditory warnings or notifications (e.g., beeps or chimes). In some embodiments, display 208 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0046] In some embodiments, receiver 212 may receive information from a second user equipment indicating a second resource used by the second user equipment for a second transmission to a third user equipment. In various embodiments, processor 202 may: determine whether the second resource used by the second user equipment for the second transmission to the third user equipment overlaps with a first resource used by a first user equipment for a first transmission to the third user equipment; and, in response to determining that the second resource overlaps with the first resource, determine whether to avoid the first transmission on the first resource based on a destination identifier, a logical channel priority ordering procedure, resource conflicts due to half-duplex and / or hidden nodes, or a combination thereof.

[0047] In some embodiments, receiver 212 may receive trigger information that triggers a change in resource allocator mode or a change in communication protocol. In various embodiments, processor 202 may change resource allocator mode or change communication protocol in response to receiving trigger information.

[0048] Although only one transmitter 210 and one receiver 212 are described, 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. In one embodiment, the transmitters 210 and receivers 212 may be part of a transceiver.

[0049] Figure 3 An embodiment of a device 300 is depicted for use in determining transmissions to be avoided. Device 300 includes one embodiment of a network unit 104. Furthermore, 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 will be understood, processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0050] In some embodiments, sidelink resource selection enhancement for mode 2 can be performed by analyzing various factors associated with continuous packet loss. Factors associated with continuous packet loss may include: 1) half-duplex transmission, in which a first user equipment (“UE”) (UEA) and a second UE (UEB) transmit in the same time slot and cannot hear each other’s transmissions; 2) continuous negative acknowledgments (“NACK”) and / or discontinuous transmissions (“DTX”) received from the receiver (“RX”) UE; 3) congestion in the resource pool; and / or 4) interference at the receiver side due to hidden nodes.

[0051] Figure 4This is a timing diagram 400 illustrating an embodiment of half-duplex transmission interference. Timing diagram 400 is illustrated at time 402 and frequency 404. Furthermore, the timing of communication between a first transmitter UE 406 (UE1-TX), a second transmitter UE 408 (UE2-TX), and a receiver UE 410 (UE3-RX) is illustrated. When a transmission from the first transmitter UE 406 to the receiver UE 410 occurs simultaneously with a transmission from the second transmitter UE 408 to the receiver UE 410, the receiver UE 410 receives both transmissions simultaneously, and these two transmissions interfere with each other. However, the first transmitter UE 406 and the second transmitter UE 408 may be unaware of the interference because the transmitters are half-duplex devices that cannot receive data while transmitting data.

[0052] Figure 5 Figure 500 is a schematic block diagram 500 illustrating one embodiment of communication between user equipment. Figure 500 includes a transmitter (“TX”) UE 502 and an RX UE 504. TX UE 502 may transmit information to RX UE 504 indicating the source identifier (“ID”) of TX UE 502 and the destination ID (e.g., a destination ID configured from a higher layer in TX UE 502) for one or more transmissions to be performed by TX UE 502 on one or more resources. Furthermore, RX UE 504 may transmit information to TX UE 502 indicating the source ID of RX UE 504 and the destination ID (e.g., a destination ID configured from a higher layer in RX UE 504) for one or more transmissions to be performed by RX UE 504 on one or more resources.

[0053] As used herein, embodiments may be described with respect to the destination ID. However, it should be noted that the TX UE may alternatively use the source ID (e.g., Layer 1 (“L1”) and / or Layer 2 (“L2”)), destination ID, and / or destination group ID (e.g., L1 and / or L2) of the RX UE. As may be understood, the use of the destination ID (e.g., L1 and / or L2) and the source ID (e.g., L1 and / or L2) may refer to the same RX UE.

[0054] In the first embodiment, for resource exclusion in mode 2 (e.g., UE autonomous resource allocation mode), resource revaluation may take into account issues related to half-duplex transmissions to the destination.

[0055] In the first embodiment, the TX UE can avoid the half-duplex problem by excluding all overlapping frequency resources in the time resources indicated by the sensing results during the initial resource selection procedure (e.g., by decoding the side link control information (SCI) from other UEs).

[0056] In a first option of the first embodiment, when the initial resource selection (or reselection) is triggered, the higher layer may provide the destination ID along with other parameters (e.g., the priority of the transport block (“TB”), the T2 min, the packet delay budget (“PDB”), etc.) to the physical (“PHY”) layer for which candidate resource selection and resource exclusion procedures will be performed. In some embodiments, if other UEs have overlapping transmission time resources for transmission to the same destination ID, the TX UE avoids half-duplex transmission to the destination ID by excluding its own transmission time resources.

[0057] In some embodiments, the PHY layer provides the MAC layer with different groups of candidate resources, which show resources that should not be used (e.g., group A: not for destination ID X, group B: not for destination ID Y, and so on).

[0058] In various embodiments of the first option, half-duplex avoidance can be configured to be used only for high-priority services and can be configured for each logical channel (“LCH”). In some embodiments of the first option, half-duplex avoidance may be required if the priority TX transmitted by the TX UE is lower than the priority RX of one or more other UEs (e.g., the absolute priority of TX > the priority of RX from other UEs). In some embodiments of the first option, a sidelink (“SL”) priority threshold is defined, and half-duplex avoidance can be performed if the priority of TB is higher than the SL priority threshold. In various embodiments of the first option, half-duplex avoidance is required if the SL reference signal received power (“RSRP”) and / or received signal strength indication (“RSSI”) threshold of the RX UE is higher than a certain configured threshold. In some embodiments of the first option, half-duplex avoidance can be used based on the remaining PDB. In various embodiments of the first option, half-duplex avoidance can be used based on a combination of priority and RSRP.

[0059] In the second option of the first embodiment, if a new TB is transmitted in a configured-approved (“CG”) resource or a reserved resource at a certain time, the TX UE performs a logical channel priority (“LCP”) procedure and excludes destination IDs with source L2 IDs that have been reserved at the time for that time.

[0060] In various embodiments of the second option, half-duplex avoidance can be configured to be used only for high-priority services and can be configured for each logical channel (“LCH”). In some embodiments of the second option, half-duplex avoidance may be required if the priority TX transmitted by the TX UE is lower than the priority RX of one or more other UEs (e.g., the absolute priority of TX > the priority of RX from other UEs). In some embodiments of the second option, a sidelink (“SL”) priority threshold is defined, and half-duplex avoidance can be performed if the priority of TB is higher than the SL priority threshold. In various embodiments of the second option, half-duplex avoidance is required if the SL reference signal received power (“RSRP”) and / or received signal strength indication (“RSSI”) threshold of the RX UE is higher than a certain configured threshold. In some embodiments of the second option, half-duplex avoidance can be used based on the remaining PDB. In various embodiments of the second option, half-duplex avoidance can be used based on a combination of priority and RSRP.

[0061] In the third option of the first embodiment, a combination of the first and second options can be used. In the third option, both LCP and the candidate resource exclusion process can be used to avoid half-duplex interference issues related to transmission to the destination.

[0062] In a first embodiment, the TX UE may perform an evaluation (e.g., re-evaluation) of a selected (e.g., pre-selected) resource for a destination ID before or at a certain time (e.g., m-T3). If received sidelink control information (“SCI”) from other UEs overlaps in time resources with the same destination ID as the selected resource due to half-duplex, the TX UE triggers resource reselection if no resource from the identified candidate resource set is available for transmission to the destination ID.

[0063] In various embodiments of the first embodiment, half-duplex avoidance may be configured to be used only for high-priority services and may be configured for each logical channel (“LCH”). In some embodiments of the first embodiment, half-duplex avoidance may be required if the priority TX transmitted by the TX UE is lower than the priority RX of one or more other UEs (e.g., the absolute priority of TX > the priority of RX from other UEs). In some embodiments of the first embodiment, a sidelink (“SL”) priority threshold is defined, and half-duplex avoidance may be performed if the priority of the TB is higher than the SL priority threshold. In various embodiments of the first embodiment, half-duplex avoidance is required if the SL reference signal received power (“RSRP”) and / or received signal strength indication (“RSSI”) threshold of the RX UE is higher than a certain configured threshold. In some embodiments of the first embodiment, half-duplex avoidance may be used based on the remaining PDB. In various embodiments of the first embodiment, half-duplex avoidance may be used based on a combination of priority and RSRP.

[0064] In various embodiments, if an SCI is received after m-T3 and the SCI overlaps with the time resource of the first destination ID of the selected resource in the time resource, then if the priority of the selected resource is lower than the corresponding priority of other UEs, the TX UE does not transmit, or the TX UE may transmit a second TB with a second destination ID that does not overlap with the first destination ID in the selected resource.

[0065] In some embodiments, if SCI indications received from other UEs indicate overlap in transmissions to the same destination ID within a given time resource, the TX UE performs resource reselection.

[0066] In some embodiments, the TX UE may transmit a second TB belonging to a different destination ID in reserved resources after performing LCP.

[0067] In various embodiments, the TX UE avoids half-duplex interference only when there is more than one consecutive transmission overlap for the same destination ID and / or when one or more NACKs and / or DTXs are received.

[0068] In the second embodiment, for Mode 1, the TX UE LCP procedure may include a source ID and / or a destination ID to avoid half-duplex issues. In this embodiment, for Mode 1, if SL approval is received from the gNB, the TX UE selects the highest priority logical channel and destination ID based on the LCP procedure. During LCH and destination ID selection, the TX UE excludes the source ID or transmitted destination ID of the receiver in the time resources and / or time slots that may overlap in time resources as indicated in the SL approval by monitoring SCIs from other UEs, thus avoiding half-duplex interference.

[0069] In various embodiments of the second embodiment, half-duplex avoidance can be configured to be used only for high-priority services and can be configured for each logical channel (“LCH”). In some embodiments of the second embodiment, half-duplex avoidance may be required if the priority TX transmitted by the TX UE is lower than the priority RX of one or more other UEs (e.g., the absolute priority of TX > the priority of RX from other UEs). In some embodiments of the second embodiment, a sidelink (“SL”) priority threshold is defined, and half-duplex avoidance can be performed if the priority of TB is higher than the SL priority threshold. In various embodiments of the second embodiment, half-duplex avoidance is required if the SL reference signal received power (“RSRP”) and / or received signal strength indication (“RSSI”) threshold of the RX UE is higher than a certain configured threshold. In some embodiments of the second embodiment, half-duplex avoidance can be used based on the remaining PDB. In various embodiments of the second embodiment, half-duplex avoidance can be used based on a combination of priority and RSRP.

[0070] In some embodiments, the SL from the gNB is permitted to contain the destination ID, and the TX UE LCP procedure is not executed. The gNB ensures that no two TX UEs transmit the same destination ID in the same time slot.

[0071] In the third embodiment, the UEs exchange destination IDs. In the third embodiment, in a UE-to-UE interface (“PC5”) radio resource control (“RRC”) connection, the first UE (UEA) and the second UE (UEB) exchange configured destination IDs for use in the resource exclusion procedure. In one embodiment of the third embodiment, UEB informs UEA of a list of destination IDs, and UEA, in its resource exclusion procedure, excludes transmissions to those destination IDs or subsets of destination IDs where there is time resource overlap between UEA and UEB.

[0072] In some embodiments of the third embodiment, for transmissions from different UEs to the same destination ID, the TX UE will avoid overlap or trigger resource selection (or reselection) only if more than one consecutive time resource overlaps.

[0073] In the fourth embodiment, mode and / or link switching may occur. In the fourth embodiment, the TX UE may switch from mode 2 to mode 1 (e.g., gNB resource allocation) resource allocation based on one of the following: 1) the TX UE receives consecutive NACK or DTX, and therefore the TX UE transmits (or retransmits) TB using mode 1 resource allocation; and / or a channel busy ratio (“CBR”) measurement report, for which the TX UE performs any new transmission of TB (e.g., if the corresponding logical channel is configured for both mode 1 and mode 2) or performs any remaining blind retransmission of TB using mode 1 resource allocation.

[0074] In various embodiments, the TX UE can switch from PC5 to Uu (e.g., UE to network interface) based on continuous NACK, continuous DTX and / or CBR measurement reports.

[0075] Figure 6 This is a flowchart illustrating one embodiment of a method 600 for determining transmissions to be avoided. In some embodiments, method 600 is performed by a device, such as remote unit 102. In some embodiments, method 600 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0076] In various embodiments, method 600 includes receiving 602 information at a first user equipment from a second user equipment, the information indicating a second resource used by the second user equipment for a second transmission to a third user equipment. In some embodiments, method 600 includes determining 604 whether the second resource used by the second user equipment for the second transmission to the third user equipment overlaps with a first resource used by the first user equipment for a first transmission to the third user equipment. In some embodiments, method 600 includes determining 606 whether to avoid the first transmission on the first resource based on a destination identifier, a logical channel priority ordering procedure, or a combination thereof, in response to determining that the second resource overlaps with the first resource.

[0077] In some embodiments, the information from the second user equipment includes a destination identifier, a reserved resource, a conflicting resource, or a combination thereof. In some embodiments, in response to the destination identifier instructing a third user equipment, the first user equipment avoids the first transmission on the first resource. In various embodiments, in response to the first transmission having a lower priority than the second transmission having a lower priority, the first user equipment avoids the first transmission on the first resource.

[0078] In one embodiment, determining whether to avoid a first transmission on a first resource includes determining whether to avoid the first transmission on the first resource based on the priority of the first transmission, the priority of a second transmission, a logical channel, the priority of the logical channel, or a combination thereof. In some embodiments, the logical channel priority ordering procedure includes determining whether the first resource has been reserved before the second resource. In some embodiments, overlap is the result of time conflicts, frequency conflicts, or a combination thereof.

[0079] In various embodiments, in response to a second resource being reserved for a destination prior to a first resource, the first user equipment avoids a first transmission on the first resource to the destination. In one embodiment, in response to receiving information from the second user equipment indicating a second resource for a second transmission to a third user equipment before a time threshold, the first user equipment avoids the first transmission on the first resource. In some embodiments, method 600 further includes performing resource reselection of a third resource for a transmission to a third user equipment in response to determining that the second resource overlaps with the first resource.

[0080] In some embodiments, method 600 further includes transmitting information indicating a first resource used by a first user equipment for a first transmission to a third user equipment. In various embodiments, determining whether a second resource used by a second user equipment for a second transmission to a third user equipment overlaps with a first resource used by a first user equipment for a first transmission to a third user equipment includes determining whether more than one consecutive time resource used by a second user equipment for a second transmission to a third user equipment overlaps with more than one consecutive time resource used by a first user equipment for a first transmission to a third user equipment.

[0081] Figure 7 This is a flowchart illustrating one embodiment of a method 700 for triggering a change. In some embodiments, method 700 is executed by a device, such as remote unit 102. In some embodiments, method 700 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0082] In various embodiments, method 700 includes receiving 702 trigger information at a first user equipment, the trigger information triggering a change in a resource allocator mode or a change in a communication protocol. In some embodiments, method 700 includes changing 704 the resource allocator mode or changing the communication protocol in response to receiving the trigger information.

[0083] In some embodiments, the triggering information includes receiving two consecutive negative acknowledgments. In some embodiments, the triggering information includes receiving a channel busy ratio measurement report. In various embodiments, changing the resource allocation procedure mode includes changing from a second resource allocation procedure mode to a first resource allocation procedure mode.

[0084] In one embodiment, the first resource allocation procedure mode includes receiving side-link permission from the network device. In some embodiments, changing the communication protocol includes changing from a user equipment-to-user equipment communication protocol to a user equipment-to-network communication protocol.

[0085] In one embodiment, a method includes: receiving information from a second user equipment at a first user equipment, the information indicating a second resource used by the second user equipment for a second transmission to a third user equipment; determining whether the second resource used by the second user equipment for the second transmission to the third user equipment overlaps with a first resource used by the first user equipment for a first transmission to the third user equipment; and determining, in response to determining that the second resource overlaps with the first resource, whether to avoid the first transmission on the first resource based on a destination identifier, a logical channel priority ordering procedure, or a combination thereof.

[0086] In some embodiments, the information from the second user equipment includes a destination identifier, reserved resources, conflicting resources, or a combination thereof.

[0087] In some embodiments, in response to a destination identifier indicating a third user equipment, the first user equipment avoids the first transmission on the first resource.

[0088] In various embodiments, in response to a first priority of a first transmission being lower than a second priority of a second transmission, a first user equipment avoids the first transmission on a first resource.

[0089] In one embodiment, determining whether to avoid a first transmission on a first resource includes determining whether to avoid a first transmission on a first resource based on the priority of the first transmission, the priority of a second transmission, a logical channel, the priority of the logical channel, or a combination thereof.

[0090] In some embodiments, the logical channel priority sorting procedure includes determining whether a first resource has been reserved prior to a second resource.

[0091] In some embodiments, overlap is the result of time conflict, frequency conflict, or a combination thereof.

[0092] In various embodiments, in response to reserving a second resource for a destination prior to the first resource, the first user equipment avoids a first transmission to the destination on the first resource.

[0093] In one embodiment, in response to receiving information from a second user equipment indicating a second resource for which the second user equipment may use a second transmission to a third user equipment before a time threshold, the first user equipment avoids the first transmission on the first resource.

[0094] In some embodiments, the method further includes performing resource reselection of a third resource for transmission to a third user equipment in response to determining that the second resource overlaps with the first resource.

[0095] In some embodiments, the method further includes transmitting information indicating a first resource used by a first user equipment to make a first transmission to a third user equipment.

[0096] In various embodiments, determining whether a second resource used by a second user equipment for a second transmission to a third user equipment overlaps with a first resource used by a first user equipment for a first transmission to a third user equipment includes determining whether more than one consecutive time resource used by the second user equipment for the second transmission to the third user equipment overlaps with more than one consecutive time resource used by the first user equipment for the first transmission to the third user equipment.

[0097] In one embodiment, an apparatus includes a first user equipment, the apparatus further comprising: a receiver that receives information from a second user equipment indicating a second resource used by the second user equipment for a second transmission to a third user equipment; and a processor that: determines whether the second resource used by the second user equipment for the second transmission to the third user equipment overlaps with a first resource used by the first user equipment for a first transmission to the third user equipment; and, in response to determining that the second resource overlaps with the first resource, determines whether to avoid the first transmission on the first resource based on a destination identifier, a logical channel priority ordering procedure, or a combination thereof.

[0098] In some embodiments, the information from the second user equipment includes a destination identifier, reserved resources, conflicting resources, or a combination thereof.

[0099] In some embodiments, in response to a destination identifier indicating a third user equipment, the first user equipment avoids the first transmission on the first resource.

[0100] In various embodiments, in response to a first priority of a first transmission being lower than a second priority of a second transmission, a first user equipment avoids the first transmission on a first resource.

[0101] In one embodiment, the processor determining whether to avoid a first transmission on a first resource includes the processor determining whether to avoid the first transmission on the first resource based on the priority of the first transmission, the priority of a second transmission, a logical channel, the priority of the logical channel, or a combination thereof.

[0102] In some embodiments, the logical channel priority sorting procedure includes determining whether a first resource has been reserved prior to a second resource.

[0103] In some embodiments, overlap is the result of time conflict, frequency conflict, or a combination thereof.

[0104] In various embodiments, in response to reserving a second resource for a destination prior to the first resource, the first user equipment avoids a first transmission to the destination on the first resource.

[0105] In one embodiment, in response to receiving information from a second user equipment indicating a second resource for which the second user equipment may use a second transmission to a third user equipment before a time threshold, the first user equipment avoids the first transmission on the first resource.

[0106] In some embodiments, the processor performs resource reselection of a third resource for transmission to a third user equipment in response to determining that the second resource overlaps with the first resource.

[0107] In some embodiments, the method further includes a transmitter transmitting information indicating a first resource used by a first user equipment to make a first transmission to a third user equipment.

[0108] In various embodiments, the processor determining whether a second resource used by the second user equipment for a second transmission to a third user equipment overlaps with a first resource used by the first user equipment for a first transmission to the third user equipment includes the processor determining whether more than one consecutive time resource used by the second user equipment for the second transmission to the third user equipment overlaps with more than one consecutive time resource used by the first user equipment for the first transmission to the third user equipment.

[0109] In one embodiment, a method includes: receiving trigger information at a first user equipment, the trigger information triggering a change in a resource allocation procedure mode or a change in a communication protocol; and changing the resource allocation procedure mode or the communication protocol in response to receiving the trigger information.

[0110] In some embodiments, the triggering information includes receiving two consecutive negative acknowledgments.

[0111] In some embodiments, the triggering information includes a receive channel busy ratio measurement report.

[0112] In various embodiments, changing the resource allocator mode includes changing from a second resource allocator mode to a first resource allocator mode.

[0113] In one embodiment, the first resource allocation procedure mode includes receiving sidelink permission from a network device.

[0114] In some embodiments, changing the communication protocol includes changing from a user equipment-to-user equipment communication protocol to a user equipment-to-network communication protocol.

[0115] In one embodiment, a device includes user equipment, the device further comprising: a receiver that receives trigger information that triggers a change in a resource allocator mode or a change in a communication protocol; and a processor that changes the resource allocator mode or changes the communication protocol in response to receiving the trigger information.

[0116] In some embodiments, the triggering information includes the receiver receiving two consecutive negative acknowledgments.

[0117] In some embodiments, the triggering information includes a receiver receive channel busy ratio measurement report.

[0118] In various embodiments, the processor changing resource allocator mode includes the processor changing from a second resource allocator mode to a first resource allocator mode.

[0119] In one embodiment, the first resource allocation procedure mode includes the receiver receiving sidelink permission from the network device.

[0120] In some embodiments, processor changing communication protocols includes the processor changing from a user equipment-to-user equipment communication protocol to a user equipment-to-network communication protocol.

[0121] Other specific embodiments may be practiced. The described embodiments should be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations that exist within the equivalent meaning and scope of the claims are to be included within the scope of the claims.

Claims

1. A method for wireless communication, comprising: At a first user equipment (UE), information is received from a second UE, the information indicating a second resource used by the second UE to perform a second transmission to a third UE; Determine whether the second resource used by the second UE to perform the second transmission to the third UE overlaps with the first resource used by the first UE to perform the first transmission to the third UE; In response to determining that the second resource overlaps with the first resource, a decision is made based on the destination UE as to whether to avoid the first transmission on the first resource to the third UE; as well as In response to the fact that the destination UE is the third UE, it is determined to avoid performing the first transmission on the first resource to the third UE.

2. The method of claim 1, wherein the information from the second UE includes the identifier of the third UE, reserved resources, conflicting resources, or a combination thereof.

3. The method of claim 1, wherein determining whether to avoid the first transmission on the first resource to the third UE further comprises determining whether to avoid the first transmission on the first resource based on the priority of the first transmission, the priority of the second transmission, a logical channel, the priority of the logical channel, or a combination thereof.

4. The method of claim 1, wherein determining whether to avoid the first transmission on the first resource to the third UE further comprises determining whether to avoid the first transmission on the first resource based on a logical channel priority sorting procedure, wherein the logical channel priority sorting procedure includes determining whether the first resource has been reserved prior to the second resource.

5. The method of claim 1, wherein the overlap is the result of a time conflict, a frequency conflict, or a combination thereof.

6. The method of claim 3, wherein in response to the reservation of the second resource for the third UE prior to the first resource, the first UE avoids the first transmission to the third UE on the first resource.

7. The method of claim 1, wherein in response to receiving information from the second UE before a time threshold indicating that the second resource is to be used by the second UE for the second transmission to the third UE, the first UE avoids the first transmission on the first resource.

8. The method of claim 1, further comprising performing resource reselection of a third resource for transmission to the third UE in response to determining that the second resource overlaps with the first resource.

9. The method of claim 1, further comprising transmitting information indicating the first resource used by the first UE to perform the first transmission to the third UE.

10. The method of claim 1, wherein determining whether the second resource used by the second UE to perform the second transmission to the third UE overlaps with the first resource used by the first UE to perform the first transmission to the third UE includes determining whether more than one consecutive time resource used by the second UE to perform the second transmission to the third UE overlaps with more than one consecutive time resource used by the first UE to perform the first transmission to the third UE.

11. An apparatus for wireless communication, comprising a first user equipment (UE), the apparatus further comprising: A receiver receives information from a second UE, the information indicating a second resource used by the second UE to make a second transmission to a third UE; as well as Processor, which: Determine whether the second resource used by the second UE to perform the second transmission to the third UE overlaps with the first resource used by the first UE to perform the first transmission to the third UE; as well as In response to determining that the second resource overlaps with the first resource, and based on the fact that the destination UE is the third UE, it is determined to avoid performing the first transmission on the first resource to the third UE.

12. A processor for a first user equipment (UE) for wireless communication, the processor being configured to cause the first UE to: Receive information from the second UE, the information indicating a second resource used by the second UE for transmission from the second UE to the third UE; Determine whether the second resource used by the second UE for the transmission from the second UE to the third UE overlaps with the first resource used by the first UE for the transmission from the first UE to the third UE; and In response to determining that the second resource overlaps with the first resource, it is determined to avoid transmitting the first resource to the third UE based on the fact that the destination UE is the third UE.

Images