Method, device and system for resolving directional conflicts in a sub-band full duplex system - Patents.com

Abstract

The present disclosure describes a method, system, and device for resolving directional conflicts in a sub-band full duplex (SBFD) telecommunications system. The method includes obtaining a first communication opportunity and a second communication opportunity configured or scheduled in opposite directions to overlap in the time domain or to have a gap in the time domain less than a threshold, determining whether to cancel at least a portion of the first communication opportunity or to cancel at least a portion of the second communication opportunity, in response to determining to cancel at least a portion of the second communication opportunity, canceling at least a portion of the second communication opportunity and executing the first communication opportunity, and in response to determining to cancel at least a portion of the first communication opportunity, canceling at least a portion of the first communication opportunity and executing the second communication opportunity.

Description

[Technical field]

[0001] The present disclosure relates generally to wireless communications. In particular, the present disclosure relates to a method, device, and system for resolving directional conflicts in a sub-band full duplex (SBFD) telecommunications system. [Background technology]

[0002] Wireless communication technologies are moving the world towards an increasingly connected and networked society. High speed and low latency wireless communications depend on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations). New generation networks are expected to deliver high speed, low latency, and ultra-reliable communication capabilities to meet requirements from various industries and users.

[0003] With the rapid evolution of cellular mobile communication systems, sub-band full duplex (SBFD) technology may be an important feature to further improve the efficiency and performance of new generation mobile communication technologies. Sub-band full duplex technology may enable sub-band full duplex with different frequency resources. Since downlink (DL) resources and / or uplink (UL) resources are not simultaneously accessible but are available at any time through appropriate configuration, SBFD can increase communication coverage and reduce communication latency. In current technology, there are challenges / problems associated with implementing SBFD. One of the challenges / problems may include directional conflicts, in which different cells are configured or scheduled with channels and / or signals having different link directions in certain cases.

[0004] The present disclosure may address at least one of the problems / challenges associated with existing systems, in particular, problems / challenges related to directional conflicts, and describes various embodiments, thus improving the efficiency and / or performance of wireless communications. Summary of the Invention [Means for solving the problem]

[0005] This document relates to methods, systems, and devices for wireless communications, and more particularly, to methods, systems, and devices for resolving directional contention in sub-band full duplex (SBFD) telecommunications systems. Various embodiments of the present disclosure can enable handling of directional contention in SBFD systems, which can reduce implementation complexity of gNBs, increase resource utilization efficiency, and improve latency performance of Ultra-Reliable Low Latency Communications (URLLC) traffic.

[0006] In one embodiment, the present disclosure describes a method for wireless communication. The method includes: obtaining, by a user equipment (UE), a first communication opportunity and a second communication opportunity configured or scheduled to overlap in a time domain or to have a gap between the first communication opportunity and the second communication opportunity in the time domain that is less than a threshold, the first communication opportunity and the second communication opportunity being configured to communicate in opposite directions between the UE and a base station; determining, by the UE, whether to cancel at least a portion of the first communication opportunity or to cancel at least a portion of the second communication opportunity based on first information of the first communication opportunity and second information of the second communication opportunity; canceling, by the UE, at least a portion of the second communication opportunity and executing the first communication opportunity in response to determining to cancel at least a portion of the first communication opportunity; and canceling, by the UE, at least a portion of the first communication opportunity and executing the second communication opportunity in response to determining to cancel at least a portion of the first communication opportunity.

[0007] In one embodiment, the present disclosure describes a method for wireless communication, the method including: scheduling, by a base station, a first communication opportunity and a second communication opportunity to overlap in a time domain or to have a gap between the first communication opportunity and the second communication opportunity in the time domain that is less than a threshold, the first communication opportunity and the second communication opportunity being configured for a user equipment (UE) for communication in opposite directions between the UE and the base station; executing, by the base station, the first communication opportunity in response to determining to cancel at least a portion of the second communication opportunity; and executing, by the base station, the second communication opportunity in response to determining to cancel at least a portion of the first communication opportunity.

[0008] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and a processing circuit in communication with the memory, the processing circuit being configured, when the instructions are executed, to perform the above-described method.

[0009] In some other embodiments, a device for wireless communication may include a memory storing instructions and a processing circuit in communication with the memory, the processing circuit being configured, when executing the instructions, to perform the methods described above.

[0010] In some other embodiments, a computer readable medium comprises instructions that, when executed by a computer, cause the computer to perform the above-described method.

[0011] These and other aspects and their implementations are described in more detail in the drawings, description, and claims. The present invention provides, for example, the following: (Item 1) 1. A method for wireless communication, the method comprising: obtaining, by a user equipment (UE), a first communication opportunity and a second communication opportunity, the first communication opportunity and the second communication opportunity being configured or scheduled to overlap in a time domain or to have a gap in the time domain between the first communication opportunity and the second communication opportunity that is less than a threshold, the first communication opportunity and the second communication opportunity being configured to communicate in opposite directions between the UE and a base station; determining, by the UE, whether to cancel at least a portion of the first communication opportunity or cancel at least a portion of the second communication opportunity based on first information of the first communication opportunity and second information of the second communication opportunity; canceling, by the UE, at least the portion of the second communication opportunity and executing the first communication opportunity in response to determining to cancel at least the portion of the second communication opportunity; canceling, by the UE, at least the portion of the first communication opportunity and implementing the second communication opportunity in response to determining that at least the portion of the first communication opportunity should be cancelled. A method comprising: (Item 2) 1. A method for wireless communication, the method comprising: scheduling, by a base station, a first communication opportunity and a second communication opportunity, the first communication opportunity and the second communication opportunity overlapping in a time domain or having a gap in the time domain between the first communication opportunity and the second communication opportunity that is less than a threshold, the first communication opportunity and the second communication opportunity being configured for a user equipment (UE) for communication in opposite directions between the UE and the base station; executing, by the base station, the first communication opportunity in response to determining to cancel at least a portion of the second communication opportunity; executing, by the base station, the second communication opportunity in response to determining to cancel at least a portion of the first communication opportunity; A method comprising: (Item 3) the first communication opportunity is configured in a first cell and the second communication opportunity is configured in a second cell; or 3. The method according to claim 1, wherein the first communication opportunity is configured in a first frequency resource, and the second communication opportunity is configured in a second frequency resource. (Item 4) The first information of the first communication opportunity includes: Configuration type information indicating whether the first communication opportunity is a first configuration type or a second configuration type; priority level information indicating a priority level of the first communication opportunity; communication direction information indicating whether the first communication opportunity is a downlink opportunity or an uplink opportunity; an uplink cancellation indication, when the first communication opportunity is an uplink opportunity, indicating that the first communication opportunity should be cancelled; or a downlink preemption indication or a downlink deactivation indication indicating that the first communication opportunity should be cancelled when the first communication opportunity is a downlink opportunity; At least one of The second information of the second communication opportunity includes: Configuration type information indicating whether the second communication opportunity is a first configuration type or a second configuration type; priority level information indicating a priority level of the second communication opportunity; communication direction information indicating whether the second communication opportunity is a downlink opportunity or an uplink opportunity; an uplink cancellation indication, when the second communication opportunity is an uplink opportunity, indicating that the second communication opportunity should be cancelled; or a downlink preemption indication or a downlink deactivation indication instructing that the second communication opportunity should be cancelled when the second communication opportunity is a downlink opportunity; The method according to any one of items 1 to 2, comprising at least one of the following: (Item 5) the first configuration type indicates a semi-statically configured communication opportunity; 5. The method of claim 4, wherein the second configuration type indicates a dynamically scheduled communication opportunity. (Item 6) the first communication opportunity is of the second configuration type and is the downlink opportunity; the second communication opportunity is of the second configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; The UE comprises: the entirety of the second communication opportunity; or At least the portion of the second communication opportunity that overlaps with the first communication opportunity in the time domain. The method according to any one of items 1 to 5, wherein the method determines to cancel one of the above. (Item 7) In response to control signaling or control signaling resources scheduling the first communication opportunity that overlaps with the second communication opportunity, the UE cancels the at least the portion of the second communication opportunity at a start of the control signaling or control signaling resources; 7. The method of claim 6, wherein in response to the control signaling or control signaling resources scheduling the first communication opportunity that does not overlap with the second communication opportunity, the UE cancels the at least the portion of the second communication opportunity for a duration after the end of the control signaling. (Item 8) the first communication opportunity is of the second configuration type and is the uplink opportunity; the second communication opportunity is of the second configuration type and is the downlink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; The UE comprises: the entirety of the second communication opportunity; or At least the portion of the second communication opportunity that overlaps with the first communication opportunity in the time domain. The method according to any one of items 1 to 5, wherein the method determines to cancel one of the above. (Item 9) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the second configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; In response to the UE not receiving an uplink cancellation indication, the UE determines to cancel or postpone the first communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to the UE receiving the uplink cancellation indication, the UE decides to cancel the second communication opportunity. (Item 10) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the second configuration type and is the uplink opportunity; the first communication opportunity has the same priority as the second communication opportunity; In response to the UE not receiving an uplink cancellation indication, the UE determines to cancel or postpone the first communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to the UE receiving the uplink cancellation indication, the UE decides to cancel the second communication opportunity. (Item 11) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the second configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; In response to the UE receiving a downlink preemption indication for the first communication opportunity, the UE determines to cancel the first communication opportunity; In response to the UE receiving a downlink deactivation indication for the first communication opportunity, the UE determines to deactivate the first communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to the UE not receiving the downlink preemption indication or the downlink deactivation indication for the first communication opportunity, the UE decides to cancel or postpone the second communication opportunity. (Item 12) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the second configuration type and is the uplink opportunity; the first communication opportunity has a lower priority than the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein the UE decides to cancel or postpone the first communication opportunity. (Item 13) the UE ceases to transmit a negative acknowledgment signal for the cancelled or postponed first communication opportunity; or Item 13. The method of item 12, wherein the UE feeds back the negative acknowledgment signal regarding the canceled or postponed first communication opportunity. (Item 14) the first communication opportunity is of the first configuration type and is the uplink opportunity; the second communication opportunity is of the second configuration type and is the downlink opportunity; the first communication opportunity has a lower priority than the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein the UE decides to cancel or postpone the first communication opportunity. (Item 15) the first communication opportunity is of the first configuration type and is the uplink opportunity; the second communication opportunity is of the second configuration type and is the downlink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein the UE determines discontinuous transmission or erroneous reception of the second communication opportunity. (Item 16) the first communication opportunity is of the first configuration type; the second communication opportunity is of the second configuration type; the first communication opportunity has the same priority as the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein the UE decides to cancel or postpone the first communication opportunity. (Item 17) the first communication opportunity is of the first configuration type and is the uplink opportunity; the second communication opportunity is of the second configuration type and is the downlink opportunity; the first communication opportunity has the same priority as the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein the UE decides to cancel or postpone the first communication opportunity. (Item 18) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the first configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein the UE decides to cancel or postpone the second communication opportunity. (Item 19) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the first configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; In response to receiving a downlink preemption indication or a downlink deactivation indication for the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to not receiving the downlink preemption indication and the downlink deactivation indication for the first communication opportunity, the UE decides to cancel or postpone the second communication opportunity. (Item 20) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the first configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; In response to receiving an uplink cancellation indication for the second communication opportunity, the UE determines to cancel or postpone the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to not receiving the uplink cancellation instruction for the second communication opportunity, the UE decides to cancel or postpone the first communication opportunity. (Item 21) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the first configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; In response to receiving a downlink preemption indication or a downlink deactivation indication for the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity; In response to receiving an uplink cancellation indication for the second communication opportunity, the UE determines to cancel or postpone the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to not receiving the downlink preemption indication or the downlink deactivation indication for the first communication opportunity and not receiving the uplink cancellation indication for the second communication opportunity, the UE decides to cancel or postpone the second communication opportunity. (Item 22) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the first configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to the first communication opportunity and the second communication opportunity being reactivated to indicate that the first communication opportunity has a lower priority than the second communication opportunity, the UE decides to cancel or postpone the first communication opportunity. (Item 23) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the first configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to the first communication opportunity being reactivated to indicate that the first communication opportunity has a lower priority than the second communication opportunity, the UE decides to cancel or postpone the first communication opportunity. (Item 24) the first communication opportunity is of the first configuration type and is the downlink opportunity; the second communication opportunity is of the first configuration type and is the uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to the second communication opportunity being reactivated to indicate that the second communication opportunity has a higher priority than the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity. (Item 25) the first communication opportunity is of the first configuration type and is the uplink opportunity; the second communication opportunity is of the first configuration type and is the downlink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein the UE decides to cancel or postpone the second communication opportunity. (Item 26) the first communication opportunity is of the first configuration type; the second communication opportunity is of the first configuration type; the first communication opportunity has the same priority as the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein the UE decides to cancel or postpone the second communication opportunity according to a cancellation rule. (Item 27) the first communication opportunity is of the first configuration type and is the uplink opportunity; the second communication opportunity is of the first configuration type and is the downlink opportunity; the first communication opportunity has the same priority as the second communication opportunity; In response to receiving a downlink preemption indication or a downlink deactivation indication for the second communication opportunity, the UE determines to cancel or postpone the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to not receiving the downlink preemption indication and the downlink deactivation indication for the second communication opportunity, the UE decides to cancel or postpone the first communication opportunity. (Item 28) the first communication opportunity is of the first configuration type and is the uplink opportunity; the second communication opportunity is of the first configuration type and is the downlink opportunity; the first communication opportunity has the same priority as the second communication opportunity; In response to receiving an uplink cancellation indication for the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to not receiving the uplink cancellation instruction for the first communication opportunity, the UE decides to cancel or postpone the second communication opportunity. (Item 29) the first communication opportunity is of the first configuration type and is the uplink opportunity; the second communication opportunity is of the first configuration type and is the downlink opportunity; the first communication opportunity has the same priority as the second communication opportunity; In response to receiving an uplink cancellation indication for the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity; In response to receiving a downlink preemption indication or a downlink deactivation indication for the second communication opportunity, the UE determines to cancel or postpone the second communication opportunity; 6. The method according to any one of items 1 to 5, wherein in response to not receiving the uplink cancellation instruction for the first communication opportunity and not receiving the downlink preemption instruction and the downlink deactivation instruction for the second communication opportunity, the UE decides to cancel or postpone the second communication opportunity. (Item 30) 30. A wireless communication device comprising a processor and a memory, the processor configured to read a code from the memory and to perform a method according to any one of items 1 to 29. (Item 31) 30. A computer program product comprising computer readable program medium code stored thereon, the computer readable program medium code, when executed by a processor, causing the processor to perform a method according to any one of items 1 to 29. [Brief description of the drawings]

[0012] [Figure 1A] FIG. 1A illustrates an example of a wireless communication system including a wireless network node and one or more user equipments.

[0013] [Figure 1B] FIG. 1B illustrates an example of a cell configuration for a network node (eg, a base station).

[0014] [Figure 1C] FIG. 1C illustrates an example of a cell configuration for user equipment.

[0015] [Figure 1D] FIG. 1D illustrates an example of a cell configuration for another user equipment.

[0016] [Diagram 2] FIG. 2 illustrates an example of a network node.

[0017] [Diagram 3] FIG. 3 illustrates an example of a user equipment.

[0018] [Figure 4A]FIG. 4A illustrates a flow diagram of a method for wireless communication.

[0019] [Figure 4B] FIG. 4B illustrates a flow diagram of another method for wireless communication.

[0020] [Figure 5A] FIG. 5A shows a schematic diagram of an example embodiment for wireless communication.

[0021] [Figure 5B] FIG. 5B shows a schematic diagram of another exemplary embodiment for wireless communication.

[0022] [Figure 5C] FIG. 5C shows a schematic diagram of another exemplary embodiment for wireless communication.

[0023] [Figure 6] FIG. 6 shows a schematic diagram of another exemplary embodiment for wireless communication.

[0024] [Figure 7A] FIG. 7A shows a schematic diagram of another exemplary embodiment for wireless communication.

[0025] [Figure 7B] FIG. 7B shows a schematic diagram of another exemplary embodiment for wireless communication.

[0026] [Figure 8A] FIG. 8A shows a schematic diagram of another exemplary embodiment for wireless communication.

[0027] [Figure 8B] FIG. 8B shows a schematic diagram of another exemplary embodiment for wireless communication.

[0028] [Figure 9]FIG. 9 shows a schematic diagram of another exemplary embodiment for wireless communication. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] The present disclosure will now be described in detail below with reference to the accompanying drawings, which form a part hereof and which show, by way of illustration, specific examples of embodiments. It should be noted, however, that the present disclosure may be embodied in a variety of different forms, and thus, the subject matter embraced or claimed is not intended to be construed as being limited to any of the embodiments described below.

[0030] Throughout this specification and the claims, terms may have subtle meanings that are suggested or implied in the context beyond the explicitly stated meaning. Similarly, the phrases "in one embodiment" or "in some embodiments" used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" used herein do not necessarily refer to the same implementation, and the phrases "in another implementation" or "in other implementations" used herein do not necessarily refer to different implementations. For example, the claimed subject matter is intended to include combinations of example embodiments or implementations in whole or in part.

[0031] Generally, terms may be understood at least in part from their use in context. For example, terms such as "and", "or", or "and / or" as used herein may include various meanings that may depend at least in part on the context in which such terms are used. Typically, "or" when used to relate a list such as A, B, or C is intended to mean A, B, and C, which are used here in an inclusive sense, and A, B, or C, which are used here in an exclusive sense. In addition, the terms "one or more" or "at least one" as used herein may be used to describe any feature, structure, or characteristic in a singular sense, or may be used to describe a combination of features, structures, or characteristics in a plural sense, depending at least in part on the context. Similarly, terms such as "a", "an", or "the" may be understood to convey the use of the singular or to convey the use of the plural, depending at least in part on the context. In addition, the terms "based on" or "determined by" may be understood as not intended to convey a necessarily exclusive set of factors, and may instead allow for the existence of additional factors not necessarily explicitly listed, depending at least in part on the context.

[0032] The present disclosure describes methods and devices for resolving directional conflicts in sub-band full duplex (SBFD) telecommunications systems.

[0033] New generation (NG) mobile communication systems are moving the world towards an increasingly connected and networked society. High speed and low latency wireless communications depend on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to wireless base stations). New generation networks are expected to deliver high speed, low latency, and ultra-reliable communication capabilities to meet requirements from various industries and users.

[0034] With the rapid evolution of cellular mobile communication systems, more and more cells will operate at higher frequencies. With the rapid evolution of cellular mobile communication systems, sub-band full duplex (SBFD) technology can be an important feature to further improve the efficiency and performance of new generation mobile communication technologies. Sub-band full duplex technology can enable sub-band full duplex on different frequency resources. In some implementations, in order to avoid the increase in implementation complexity, only half-duplex mode, i.e., transmission or reception at a certain time, may be utilized.

[0035] In some implementations, the SBFD system may be implemented differently from a conventional frequency division duplex (FDD) system, in which there are no specific frequency resources dedicated to the downlink and / or uplink. In some other implementations, the SBFD system may be implemented to some extent similarly to a time division duplex (TDD) system, in which one frequency resource may be used for TDD downlink transmission, uplink transmission, or both downlink and uplink transmission. In some other implementations, unlike FDD / TDD systems, different frequency resources for the SBFD system may have different downlink / uplink (DL / UL) slot configurations and / or may be in the same frequency band. Because DL and / or UL resources are available at any time through appropriate configuration, although they may not be simultaneously accessible under some circumstances, the SBFD system may increase communication coverage and reduce communication latency.

[0036] FIG. 1A illustrates a wireless communication system 100 including a wireless network node 118 and one or more user equipments (UEs) 110. The wireless network node may include a network base station, which may be a Node B (NB, e.g., gNB) in a mobile telecommunications context. Each of the UEs may wirelessly communicate with the wireless network node via one or more radio channels 115 for downlink / uplink communication. For example, a first UE 110 may wirelessly communicate with the wireless network node 118 via a channel including multiple radio channels for a certain period of time. The network base station 118 may transmit higher layer signaling to the UE 110. The higher layer signaling may include configuration information for communication between the UE and the base station. In one implementation, the higher layer signaling may include a radio resource control (RRC) message.

[0037] In some embodiments, the SBFD system may consider different "sub-bands" as different cells, i.e., carrier aggregation (CA)-based SBFD (CA-SBFD). FIG. 1B illustrates a cell configuration 150 at a base station (e.g., gNB), where the gNB may operate simultaneously for cell 1 (151, cell1) and cell 2 (152, cell2) or for cell 3 (153, cell3) for CA-SBFD, and the UE may be configured with either two cells or one cell. In some other implementations where in-band full duplex is supported at the gNB (i.e., the same time / frequency domain resources may be used for both downlink and uplink at the same time), the gNB may operate simultaneously for cell 1, cell 2, and cell 3. As illustrated in FIG. 1B, cell 3 overlaps with cell 1 and cell 2 in the frequency domain; and / or cell 1 and cell 2 do not overlap in the frequency domain.

[0038] In some implementations, a UE may be configured with either one cell or two cells if the two cells share the same DL / UL configuration (either via DL / UL configuration signaling or scheduling signaling).

[0039] In some other implementations, a UE may be configured with two cells having different DL / UL configurations to take advantage of the benefits of SBFD (e.g., reduced latency, extended communication coverage). Due to limited self-interference (i.e., UL to DL interference) mitigation capability at the UE side, the UE may not operate in two cells at the same time if the two cells have different link directions, i.e., the UE may not transmit and receive in two cells at the same time, respectively, otherwise strong self-interference may block reception of DL signals.

[0040] FIG. 1C illustrates a cell configuration 160 for a first UE (UE1), where UE1 is configured with two non-overlapping cells, namely cell 1 and cell 2. Although FIG. 1C illustrates that cell 1 and cell 2 are contiguous in the frequency domain, in some implementations, cell 1 and cell 2 may be either contiguous or non-contiguous in the frequency band. FIG. 1D illustrates a cell configuration 170 for a second UE (UE2), where UE2 is configured with two fully or partially overlapping cells, namely cell 2 and cell 3. UE2 may enjoy a higher DL throughput than UE1, considering that cell 3 is configured with a larger bandwidth. In some implementations, for CA-SBFD in carriers with small bandwidth (e.g., 5 MHz bandwidth), support for cell overlap in the frequency domain may be important and desirable, considering that the small bandwidth may make it impossible to split the carrier into smaller bandwidths, since sufficient frequency sources may be required for synchronization signal blocks (SSBs).

[0041] In some other implementations, CA-SBFD may operate with either one contiguous carrier in the band or several non-contiguous carriers, and / or may unify the above description of these two scenarios.

[0042] When different cells are configured or scheduled with channels and / or signals having different link directions at a particular opportunity (e.g., using different frequency resources / cells in the frequency domain and at the same time in the time domain), directional conflicts may occur under certain circumstances. Opportunities for directional conflicts may not completely overlap in the time domain, but may also include two communication opportunities being configured / scheduled to have a gap in the time domain between the two communication opportunities that is less than a threshold. For example, but not limited to, the threshold may be a few milliseconds (ms) (e.g., 1 ms or 0.5 ms).

[0043] The present disclosure describes various embodiments for resolving / handling directional conflicts in SBFD or CA-SBFD systems under certain circumstances. Without a directional conflict handling mechanism, the gNB may have to avoid directional conflicts via configuration and / or scheduling, which is undesirable as it may dramatically increase the implementation complexity of the gNB and reduce resource utilization efficiency. For example, even if resources in one cell are not used, resources in another cell cannot be used if the resources in the two cells overlap each other in the time domain. On the other hand, when directional conflicts are not allowed, high priority traffic may not be prioritized efficiently, which reduces the latency performance of Ultra-Reliable Low Latency Communication (URLLC) traffic.

[0044] 2 illustrates an example of an electronic device 200 implementing a network base station. The example electronic device 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with UEs and / or other base stations. The electronic device 200 may also include network interface circuitry 209 for allowing the base station to communicate with other base stations and / or core networks, e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols. The electronic device 200 may include an input / output (I / O) interface 206 for communicating with an operator, etc., as needed.

[0045] The electronic device 200 may also include system circuitry 204. The system circuitry 204 may include a processor 221 and / or memory 222. The memory 222 may include an operating system 224, instructions 226, and parameters 228. The instructions 226 may configure one or more of the processors 124 to perform the functions of a network node. The parameters 228 may include parameters to support execution of the instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0046] FIG. 3 illustrates an example of an electronic device implementing a terminal device 300 (e.g., user equipment (UE)). The UE 300 may be a mobile device, e.g., a smartphone or a mobile communication module located in a vehicle. The UE 300 may include a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and a storage 309. The display circuit may include a user interface 310. The system circuit 304 may include any combination of hardware, software, firmware, or other logic / circuitry. The system circuit 304 may be implemented, for example, using one or more systems on chips (SoCs), application specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. The system circuit 304 may be part of an implementation of any desired functionality in the UE 300. In that regard, the system circuitry 304 may include logic to facilitate, by way of example, the decoding and playback of music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV, the execution of applications, the acceptance of user input, the storage and retrieval of application data, the establishment, maintenance, and termination of data connections, for example for a cellular telephone call or an Internet connection, the establishment, maintenance, and termination of a wireless network connection, Bluetooth connection, or other connection, and the display of relevant information on a user interface 310. The user interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Further examples of I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0047] 3, the communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that handles the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. A transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, wave shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and coding. As one specific example, the communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), 5G standards, and / or 6G standards. However, the techniques described below are applicable to other wireless communication technologies, whether emanating from the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.

[0048] 3, the system circuitry 304 may include one or more processors 321 and memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to perform desired functions for the UE 300. The parameters 328 may provide and specify configuration and operational options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that the UE 300 transmits or receives via the communication interface 302. In various implementations, system power for the UE 300 may be provided by a power storage device such as a battery or a transformer.

[0049] The present disclosure describes various embodiments for resolving / handling directional contention in an SBFD system or CA-SBFD system under certain circumstances that may be implemented in part or in whole on the network base stations and / or user equipment described above in Figures 2-3. Various embodiments in the present disclosure may enable handling of directional contention in an SBFD system, thereby reducing gNB implementation complexity, increasing resource utilization efficiency, and / or improving latency performance for URLLC traffic.

[0050] 4A, the present disclosure describes various embodiments of a method 400 for wireless communication. The method may include some or all of the following steps: Step 410: Obtaining, by a user equipment (UE), a first communication opportunity and a second communication opportunity configured or scheduled to overlap in a time domain or to have a gap between the first communication opportunity and the second communication opportunity in a time domain that is less than a threshold, where the first communication opportunity and the second communication opportunity are configured to communicate in opposite directions between the UE and a base station; Step 420: Selecting, by the UE, a communication opportunity based on first information of the first communication opportunity and second information of the second communication opportunity; step 430: in response to determining that at least a portion of the second communication opportunity should be canceled, by the UE, canceling at least a portion of the second communication opportunity and executing the first communication opportunity; and / or step 440: in response to determining that at least a portion of the first communication opportunity should be canceled, by the UE, canceling at least a portion of the first communication opportunity and executing the second communication opportunity.

[0051] In various embodiments of the present disclosure, the term "cancel" or "canceling" in this context may mean ceasing transmission or reception at the original time / frequency; and / or the transmission or reception may be changed (or rescheduled) to other time / frequency resources.

[0052] In various embodiments of the present disclosure, the term a UE "executes" a communication opportunity can also mean that the UE executes the communication opportunity: when the communication opportunity is an uplink opportunity, the UE transmits the communication opportunity to a base station; and / or when the communication opportunity is a downlink opportunity, the UE receives the communication opportunity from the base station.

[0053] With reference to Figure 4B, the present disclosure describes various embodiments of a method 450 for wireless communication. The method may include some or all of the following steps: step 460: scheduling, by a base station, a first communication opportunity and a second communication opportunity to overlap in the time domain or to have a gap between the first communication opportunity and the second communication opportunity in the time domain that is less than a threshold, where the first communication opportunity and the second communication opportunity are configured for a user equipment (UE) for communication in opposite directions between the UE and the base station; step 470: executing, by the base station, the first communication opportunity in response to determining to cancel at least a portion of the second communication opportunity; and / or step 480: executing, by the base station, the second communication opportunity in response to determining to cancel at least a portion of the first communication opportunity.

[0054] In various embodiments of the present disclosure, the term a base station "performs" a communication opportunity may mean that the base station performs the communication opportunity, and when the communication opportunity is an uplink opportunity, the base station receives the communication opportunity from the UE, and / or when the communication opportunity is a downlink opportunity, the base station transmits the communication opportunity to the UE.

[0055] In some implementations, the first communication opportunity is configured in a first cell and the second communication opportunity is configured in a second cell, or the first communication opportunity is configured in a first frequency resource and the second communication opportunity is configured in a second frequency resource.

[0056] In some other implementations, the first information of the first communication opportunity includes at least one of the following: configuration type information indicating whether the first communication opportunity is a first configuration type or a second configuration type; priority level information indicating a priority level of the first communication opportunity; communication direction information indicating whether the first communication opportunity is a downlink opportunity or an uplink opportunity; an uplink cancellation indication indicating that the first communication opportunity should be cancelled when the first communication opportunity is an uplink opportunity, or a downlink preemption indication or a downlink deactivation indication indicating that the first communication opportunity should be cancelled when the first communication opportunity is a downlink opportunity. and / or the second information of the second communication opportunity includes at least one of the following: configuration type information indicating whether the second communication opportunity is of a first configuration type or a second configuration type, priority level information indicating a priority level of the second communication opportunity, communication direction information indicating whether the second communication opportunity is a downlink opportunity or an uplink opportunity, an uplink cancellation indication instructing that the second communication opportunity should be canceled when the second communication opportunity is an uplink opportunity, or a downlink preemption indication or a downlink deactivation indication instructing that the second communication opportunity should be canceled when the second communication opportunity is a downlink opportunity.

[0057] In some other implementations, the first configuration type indicates semi-statically configured communication opportunities and / or the second configuration type indicates dynamically scheduled communication opportunities.

[0058] In various embodiments of the present disclosure, "RRC D" which may be derived from radio resource control downlink and "RRC U" which may be derived from radio resource control uplink may be referred to as semi-statically configured downlink and uplink channels / signals, respectively, which do not rely on dynamic signaling. For example, but not limited to, RRC D may be a channel state information reference signal (CSI-RS), a control resource set (CORESET) / search space for the physical downlink control channel (PDCCH), a synchronization signal block (SSB), or a semi-persistent scheduling physical downlink shared channel (SPS-PDSCH). For example, but not limited to, the RRC U may be a sounding reference signal (SRS), a physical random access channel (PRACH), a configuration grant physical uplink shared channel (CG PUSCH), a periodic physical uplink control channel (PUCCH) for channel state information (CSI) (i.e., persistent / semi-persistent (P / SP) CSI), a scheduling request (SR), a buffer status report (BSR), or a hybrid automatic repeat request-acknowledgement (HARQ-ACK) for SPS-PDSCH.

[0059] In various embodiments of the present disclosure, "Dynamic D" and "Dynamic U" may also be referred to as dynamically scheduled downlink and uplink channels / signals, respectively, which are different from "RRC D / U" and require dynamic signaling to trigger. For example, but not limited to, Dynamic D may be dynamically scheduled PDSCH, aperiodic CSI-RS (A-CSI-RS). For example, but not limited to, Dynamic U may be dynamically scheduled PUSCH, aperiodic SRS, PUCCH / PUSCH for A-CSI, HARQ-ACK of dynamically scheduled PDSCH.

[0060] In various embodiments of the present disclosure, various levels of priority may be assigned to different channels / signals, including, for example, high priority "RRC D", high priority "RRC U", low priority "RRC D", low priority "RRC U", high priority "Dynamic D", high priority "Dynamic U", low priority "Dynamic D", and / or low priority "Dynamic U".

[0061] In some implementations, the priority level may be referred to as priority level information indicating the priority level of the second communication opportunity. In some implementations, a higher value of the priority level may indicate a higher priority, for example, a communication opportunity at priority level 3 has a higher priority than another communication opportunity at priority level 1. In some other implementations, a higher value of the priority level may indicate a lower priority, for example, a communication opportunity at priority level 3 has a lower priority than another communication opportunity at priority level 1.

[0062] In various embodiments, a directional conflict may occur between a dynamic D / U in one cell and a dynamic U / D in another cell. Various scenarios having a first communication opportunity and a second communication opportunity are described in detail below.

[0063] In some implementations, the first communication opportunity is of a second configuration type and is a downlink opportunity, and the second communication opportunity is of a second configuration type and is an uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; and the UE decides to cancel one of the following: the entire second communication opportunity, or at least a portion of the second communication opportunity that overlaps with the first communication opportunity in the time domain.

[0064] In some other implementations, in response to the control signaling or control signaling resources scheduling a first communication opportunity that overlaps with a second communication opportunity, the UE cancels at least a portion of the second communication opportunity at the start of the control signaling or control signaling resources, and / or in response to the control signaling or control signaling resources scheduling a first communication opportunity that does not overlap with the second communication opportunity, the UE cancels at least a portion of the second communication opportunity for a duration after the end of the control signaling. In some implementations, the control signaling may include a CORESET or SS opportunity.

[0065] In some other implementations, the first communication opportunity is of a second configuration type and is an uplink opportunity, and the second communication opportunity is of a second configuration type and is a downlink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; and the UE decides to cancel one of the following: the entire second communication opportunity, or at least a portion of the second communication opportunity that overlaps with the first communication opportunity in the time domain.

[0066] In one scenario 500 shown in FIG. 5A, a high priority "Dynamic D" in one cell may overlap in the time domain with a low priority "Dynamic U" in another cell. For example, without limitation, the high priority Dynamic D may be a URLLC PDSCH 525 in time slot (t2) in cell 1, and the low priority Dynamic U may be an enhanced mobile broadband (eMBB) PUSCH 535 in time slot (t2) in cell 2. In some implementations, the eMBB PDCCH 531 may schedule / signal the eMBB PUSCH 535 and / or the URLLC PDCCH 521 in a high priority CORESET or SS may schedule / signal the URLLC PDSCH 525. Under this scenario 500, the high priority "Dynamic D" may take precedence and the low priority "Dynamic U" may be canceled, cancelled, delayed, postponed, or deferred.

[0067] 5A, a preconfigured high priority PDCCH 521 (e.g., URLLC PDCCH) opportunity (e.g., CORESET and / or SS) may prioritize high priority PDCCH reception 525 when a directional conflict with a low priority PUSCH 535 (e.g., eMBB PUSCH) occurs. The cessation of the low priority PUSCH may then also resolve the conflict between the low priority PUSCH and the high priority PDSCH when the low priority PUSCH overlaps with both the high priority PDCCH opportunity and the corresponding PDSCH.

[0068] It should be noted that the PDSCH and / or corresponding HARQ-ACK scheduled by the PDCCH in a high priority PDCCH opportunity may be automatically given high priority instead of using a priority indication in the PDCCH.

[0069] Another alternative is for the gNB to abandon the high priority PDCCH opportunity in favor of a low priority PUSCH since the gNB ensures that there is no high priority PDCCH transmission in the high priority PDCCH opportunity, and then the gNB schedules the low priority PUSCH that overlaps with the high priority PDCCH opportunity.

[0070] 5B illustrates another scenario 550 where there is only directional contention between a high priority PDSCH and a low priority PUSCH. The cancellation may begin at a duration 552 after the end of the high priority PDCCH. In some implementations, the duration 552 may be the sum of the PDCCH blind detection (BD) time and the cancellation time. For example, within the low priority PUSCH 535, the first portion 536 is not cancelled and only the second portion 537 is cancelled / aborted / delayed.

[0071] 5C illustrates another scenario 580 in which there is only directional contention between a high priority PDSCH and a low priority PUSCH. Unlike the implementation under scenario 550, under scenario 580, cancellation begins at the start of the high priority PDSCH 525 (582). Thus, for example, within the low priority PUSCH 535, the first portion 538 is not cancelled, and only the second portion 539 starting at time 582 is cancelled / aborted / delayed.

[0072] In some implementations, there must be a predefined non-zero gap between the PDCCH that schedules / signals the high priority PDSCH and the high priority PDSCH to allow time for cancellation.

[0073] In another scenario 600 shown in FIG. 6, a high priority "dynamic U" in one cell overlaps in the time domain with a low priority "dynamic D" in another cell. For example, without limitation, the high priority dynamic U may be a URLLC PUSCH 635 in time slot (t2) in cell 2, and the low priority dynamic D may be an enhanced mobile broadband (eMBB) PDSCH 626 in time slot (t2) in cell 1. In some implementations, the eMBB PDCCH 621 may schedule / signal the eMBB PDSCH 626 and / or the URLLC PDCCH 631 may schedule / signal the URLLC PUSCH 635. Under this scenario 600, the high priority "dynamic U" (e.g., URLLC PUSCH) may be prioritized and the low priority "dynamic D" (e.g., eMBB PDSCH) may be discontinued, cancelled, delayed, postponed, or deferred. In some implementations, there is a duration 602 between the start of the cancellation of the URLLC PDCCH 631 and the eMBB PDSCH 626. The duration 602 may include a PDCCH blind detection (BD) time and / or a PDSCH reception cancellation time.

[0074] In various embodiments, a directional conflict may occur between an RRC D / U in one cell and a dynamic U / D in another cell. Various scenarios having a first communication opportunity and a second communication opportunity are described in detail below.

[0075] In some implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, the second communication opportunity is of a second configuration type and is an uplink opportunity, the first communication opportunity having a higher priority than the second communication opportunity, and in response to the UE not receiving an uplink cancellation instruction, the UE decides to cancel or postpone the first communication opportunity, and / or in response to the UE receiving an uplink cancellation instruction, the UE decides to cancel the second communication opportunity.

[0076] In some other implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, the second communication opportunity is of a second configuration type and is an uplink opportunity, the first communication opportunity has the same priority as the second communication opportunity, and in response to the UE not receiving an uplink cancellation instruction, the UE decides to cancel or postpone the first communication opportunity, and / or in response to the UE receiving an uplink cancellation instruction, the UE decides to cancel the second communication opportunity.

[0077] In some implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, and the second communication opportunity is of a second configuration type and is an uplink opportunity, the first communication opportunity having a higher priority than the second communication opportunity, and in response to the UE receiving a downlink preemption indication for the first communication opportunity, the UE decides to cancel the first communication opportunity, and / or in response to the UE receiving a downlink deactivation indication for the first communication opportunity, the UE decides to deactivate the first communication opportunity, and / or in response to the UE not receiving a downlink preemption indication or a downlink deactivation indication for the first communication opportunity, the UE decides to cancel or postpone the second communication opportunity.

[0078] In some other implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, the second communication opportunity is of a second configuration type and is an uplink opportunity, the first communication opportunity has a lower priority than the second communication opportunity, and / or the UE decides to cancel or postpone the first communication opportunity.

[0079] In some other implementations, the UE discontinues the negative acknowledgment signal for the canceled or postponed first communication opportunity, or the UE feeds back the negative acknowledgment signal for the canceled or postponed first communication opportunity.

[0080] In some other implementations, the first communication opportunity is of a first configuration type and is an uplink opportunity, the second communication opportunity is of a second configuration type and is a downlink opportunity, the first communication opportunity has a lower priority than the second communication opportunity, and / or the UE decides to cancel or postpone the first communication opportunity.

[0081] In some other implementations, the first communication opportunity is of a first configuration type and is an uplink opportunity, the second communication opportunity is of a second configuration type and is a downlink opportunity, the first communication opportunity has a higher priority than the second communication opportunity, and / or the UE determines discontinuous transmission or erroneous reception of the second communication opportunity.

[0082] In some other implementations, the first communication opportunity is of a first configuration type and the second communication opportunity is of a second configuration type, the first communication opportunity has the same priority as the second communication opportunity, and / or the UE decides to cancel or postpone the first communication opportunity.

[0083] In some other implementations, the first communication opportunity is of a first configuration type and is an uplink opportunity, the second communication opportunity is of a second configuration type and is a downlink opportunity, the first communication opportunity has the same priority as the second communication opportunity, and / or the UE decides to cancel or postpone the first communication opportunity.

[0084] In another scenario 700 shown in Figure 7A, a high priority RRC D (e.g., SPS or CORESET / SS) in one cell overlaps in the time domain with a low priority "Dynamic U" (e.g., dynamically scheduled PUSCH) in another cell. For example, without limitation, the high priority RRC D may be an SPS opportunity for URLLC (721, 722, 723) in each downlink slot in cell 1, and the low priority Dynamic U may be the eMBB PUSCH / PUCCH 735. In some implementations, the eMBB PDCCH 731 may schedule / signal the eMBB PUSCH / PUCCH 735.

[0085] In some implementations, the low priority dynamic U may be aborted, cancelled, delayed, postponed or deferred. RRC D data / signaling may arrive during the interval between the UL grant and the dynamic U (e.g., at the point 761 where the URLLC data arrival may be transmitted at the next SPS opportunity due to a filled timeline), which allows time to cancel the dynamic U.

[0086] In some other implementations, canceling / canceling / delaying / postponing the dynamic U may be a performance in response to receiving a UL Cancellation Indication (732 UL CI). When the dynamic U is cancelled by the UL CI 732, the UE may receive RRC D. If the dynamic U cannot be cancelled by the UL CI due to a timeline (e.g., at time 762, which may not be transmitted in the next SPS opportunity due to a timeline where ULLC data arrival is not met), the UE may transmit the dynamic U and the gNB may postpone the DL data. When the UL CI is not present, the UE may transmit the dynamic U and / or may not receive the high priority "RRC D" (e.g., SPS), for example, because there may be no DL data in the high priority "RRC D" opportunity.

[0087] In another scenario where RRC D and Dynamic U share the same priority, the above implementation may be similarly applicable to RRC D and Dynamic U having the same priority.

[0088] In some other implementations, the high priority RRCD may be cancelled or deactivated, or the high priority RRCD may be delayed, postponed or deferred.

[0089] In some other implementations of FIG. 7B, RRC D may be cancelled in response to receiving DL signaling, e.g., DL preemption indication (782, DL PI) or deactivation (e.g., in the case of SPS). When RRC D is cancelled or deactivated in one cell, dynamic U transmission may be allowed. Otherwise, RRC D may be prioritized. In some implementations, cancelling a downlink opportunity may be much shorter than cancelling an uplink opportunity, so that the DL PI may be very close to the next SPS opportunity for URLLC. For example, the UE may prepare dynamic U after receiving scheduling signaling, the UE may perform UL transmission T ms after receiving DL PI / deactivation 782, and / or the UE may cancel or postpone UL transmission if it does not receive DL PI / deactivation. In this scenario, T may be of very short duration, which may be very close to 0 or as small as less than 1 ms, since the UL channel / signal is already waiting. Therefore, this implementation may reduce the possibility of delaying high priority RRC D (eg, URLLC data) due to a short cancellation time of RRC D, compared to some other implementations.

[0090] In another scenario, a low priority "RRC D" (e.g., SPS) in one cell may overlap in the time domain with a high priority "Dynamic U" in another cell. In some implementations, the UE may transmit Dynamic U, abort RRC D reception, and feed back a NACK (if present) for the aborted RRC D (e.g., SPS). In some other implementations, if necessary, the UE may abort the NACK to save overhead since the NACK is deterministic information.

[0091] In another scenario, a low priority "RRC U" (e.g., CG PUSCH) in one cell may overlap in the time domain with a high priority dynamic D in another cell. In some implementations, the UE may discontinue RRC U and receive dynamic D.

[0092] In another scenario, a high priority "RRC U" (e.g., CG PUSCH) in one cell may overlap with a low priority dynamic D in another cell in the time domain. In some implementations, the UE may assume discontinuous transmission (DTX) of dynamic scheduling D or erroneous reception of dynamic scheduling D if there is overlapping high priority data in the CG PUSCH. Otherwise, i.e., if there is no overlap or conflict, the UE receives dynamic scheduling D.

[0093] In another scenario, RRC D / U in one cell and dynamic U / D in another cell may have the same priority and overlap in the time domain. In some implementations, the UE may always transmit dynamic U / D and cancel RRC D / U. In some other implementations for RRC D and dynamic U overlapping in the time domain, the UE may cancel DL or UL and operate similarly to the scenario described above. In some other implementations for RRC D and dynamic U overlapping in the time domain, the UE may prioritize dynamic D or implement similarly to the scenario described above for the UE implementation.

[0094] In various embodiments, a directional conflict may occur with respect to RRC D / U in one cell and RRC U / D in another cell. Various scenarios having a first communication opportunity and a second communication opportunity are described in detail below.

[0095] In some implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, the second communication opportunity is of a first configuration type and is an uplink opportunity, the first communication opportunity has a higher priority than the second communication opportunity, and / or the UE decides to cancel or postpone the second communication opportunity.

[0096] In some other implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, the second communication opportunity is of a first configuration type and is an uplink opportunity, the first communication opportunity has a higher priority than the second communication opportunity, and in response to receiving a downlink preemption indication or a downlink deactivation indication for the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity, and / or in response to not receiving a downlink preemption indication and a downlink deactivation indication for the first communication opportunity, the UE decides to cancel or postpone the second communication opportunity.

[0097] In some other implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, the second communication opportunity is of a first configuration type and is an uplink opportunity, the first communication opportunity has a higher priority than the second communication opportunity, and in response to receiving an uplink cancellation instruction for the second communication opportunity, the UE decides to cancel or postpone the second communication opportunity, and / or in response to not receiving an uplink cancellation instruction for the second communication opportunity, the UE decides to cancel or postpone the first communication opportunity.

[0098] In some other implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, the second communication opportunity is of a first configuration type and is an uplink opportunity, the first communication opportunity having a higher priority than the second communication opportunity, and in response to receiving a downlink preemption indication or a downlink deactivation indication for the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity, in response to receiving an uplink cancellation indication for the second communication opportunity, the UE decides to cancel or postpone the second communication opportunity, and / or in response to not receiving a downlink preemption indication or a downlink deactivation indication for the first communication opportunity and not receiving an uplink cancellation indication for the second communication opportunity, the UE decides to cancel or postpone the second communication opportunity.

[0099] In some other implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, and the second communication opportunity is of a first configuration type and is an uplink opportunity, and in response to the first communication opportunity and the second communication opportunity being reactivated to indicate that the first communication opportunity has a higher priority than the second communication opportunity and / or the first communication opportunity has a lower priority than the second communication opportunity, the UE determines to cancel or postpone the first communication opportunity.

[0100] In some other implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity and the second communication opportunity is of a first configuration type and is an uplink opportunity, and in response to the first communication opportunity being reactivated to indicate that the first communication opportunity has a higher priority than the second communication opportunity and / or the first communication opportunity has a lower priority than the second communication opportunity, the UE determines to cancel or postpone the first communication opportunity.

[0101] In some other implementations, the first communication opportunity is of a first configuration type and is a downlink opportunity, the second communication opportunity is of a first configuration type and is an uplink opportunity, and the first communication opportunity has a higher priority than the second communication opportunity, and / or in response to the second communication opportunity being reactivated to indicate that the second communication opportunity has a higher priority than the first communication opportunity, the UE determines to cancel or postpone the first communication opportunity.

[0102] In some other implementations, the first communication opportunity is of a first configuration type and is an uplink opportunity, the second communication opportunity is of a first configuration type and is a downlink opportunity, the first communication opportunity has a higher priority than the second communication opportunity, and / or the UE decides to cancel or postpone the second communication opportunity.

[0103] In some other implementations, the first communication opportunity is of a first configuration type and the second communication opportunity is of a first configuration type, the first communication opportunity has the same priority as the second communication opportunity, and / or the UE determines to cancel or postpone the second communication opportunity according to a cancellation rule.

[0104] In some other implementations, the first communication opportunity is of a first configuration type and is an uplink opportunity, the second communication opportunity is of a first configuration type and is a downlink opportunity, the first communication opportunity has the same priority as the second communication opportunity, and in response to receiving a downlink preemption indication or a downlink deactivation indication for the second communication opportunity, the UE decides to cancel or postpone the second communication opportunity, and / or in response to not receiving a downlink preemption indication and a downlink deactivation indication for the second communication opportunity, the UE decides to cancel or postpone the first communication opportunity.

[0105] In some other implementations, the first communication opportunity is of a first configuration type and is an uplink opportunity, the second communication opportunity is of a first configuration type and is a downlink opportunity, the first communication opportunity has the same priority as the second communication opportunity, and in response to receiving an uplink cancellation instruction for the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity, and / or in response to not receiving an uplink cancellation instruction for the first communication opportunity, the UE decides to cancel or postpone the second communication opportunity.

[0106] In some other implementations, the first communication opportunity is of a first configuration type and is an uplink opportunity, the second communication opportunity is of a first configuration type and is a downlink opportunity, the first communication opportunity has the same priority as the second communication opportunity, and in response to receiving an uplink cancellation indication for the first communication opportunity, the UE decides to cancel or postpone the first communication opportunity, in response to receiving a downlink preemption indication or a downlink deactivation indication for the second communication opportunity, the UE decides to cancel or postpone the second communication opportunity, and / or in response to not receiving an uplink cancellation indication for the first communication opportunity and not receiving a downlink preemption indication and a downlink deactivation indication for the second communication opportunity, the UE decides to cancel or postpone the second communication opportunity.

[0107] In another scenario 800 shown in Figure 8A, a high priority RRC D (e.g., SPS) in one cell may overlap in the time domain with a low priority RRC U (e.g., CG PUSCH) in another cell. For example, but not limited to, RRC D may be an SPS opportunity for URLLC (821, 822, and 823) and / or RRC U may include a first RRC U configuration (831, 835, RRC U conf1) and / or a second RRC U configuration (841, 845, RRC U conf2).

[0108] In some implementations, an RRC D opportunity in one cell may always cancel an RRC U opportunity in another cell. This implementation may be simple, but may not be very efficient considering that high priority SPS opportunities with short periodicity may unnecessarily block many RRC U transmissions for sporadic DL URLLC data profiles. Therefore, in some other implementations, there may be pre-configured cancellation rules for a particular RRC D+RRC U combination.

[0109] In some other implementations, the DL PI and / or UL CI may be used to dynamically indicate which should be cancelled. In one implementation, the high priority RRC D 823 may be cancelled in response to receiving a DL PI or SPS deactivation 852 as shown in FIG. 8A. The DL PI or deactivation 852 may indicate that there is no DL data. If the RRC D 823 is cancelled, the UE may transmit a low priority RRC U (e.g., 835), otherwise the UE receives a high priority RRC D. In some implementations, the deactivation of the SPS signaling may deactivate only a limited number of subsequent SPS.

[0110] In some other implementations where multiple RRC U opportunities are scheduled, as shown in Figure 8A, RRC U conf1 831 at opportunity t0 may be cancelled and the UE may select RRC U conf2 841 at opportunity t0, if available. Configuring multiple low priority CG configurations may not be cost effective.

[0111] Some of the above implementations may avoid delays of high priority DL data since short processing gaps of DL PI are possible. Some of the above implementations may be signaling consuming methods since w DL PI or activation / deactivation signaling may be frequently transmitted in every RRC U opportunity due to lack of knowledge of UL data arrival (e.g., CG-PUSCH) or deterministic UL transmission (e.g., SRS) at the gNB. SPS deactivation is expected to differ from a specific mechanism, which may deactivate all of the subsequent SPS opportunities until reactivation signaling is received. Here, SPS deactivation deactivates only one SPS opportunity, and reactivation signaling is saved.

[0112] In some other implementations shown in FIG. 8B, the low priority RRC U (e.g., 835) may be cancelled when receiving UL CI 865 or deactivation of CG-PUSCH. When RRC U 835 is cancelled, the UE receives RRC D 823, otherwise the UE transmits RRC U. There is a cost associated with this implementation, and cancelling an uplink opportunity (e.g., RRC U 835) may take time to cancel, and thus the SPS may be cancelled when UL CI 865 is not received in time. For example, as shown in FIG. 8B, RRC Uconf1 (835) at opportunity t2 may be cancelled, and the UE may select RRC Uconf2 (845) at opportunity t2 if available.

[0113] In some other implementations having multiple sets of RRC U configurations, as shown in FIG. 8B, the RRC D opportunity (821) at t0 may be cancelled when the RRC D opportunity overlaps with any RRC U configuration opportunity and cancellation signaling has not been received, so that all RRC U configurations may be available. For example, under certain circumstances where the gNB wants to use the RRC D opportunity (821) at t0, the RRC U conf1 (831) at t0 may be cancelled. Alternatively, in some other implementations, the RRC D opportunity may not be cancelled when some conditions are met. For example, when at least one RRC U configuration does not overlap with RRC D, the RRC D opportunity may be retained and the RRC U configurations having an opportunity that overlaps with the RRC D opportunity are cancelled, e.g., RRC U conf2 841 does not overlap with RRC D 821, therefore, RRC U conf1 831 is cancelled and RRC D 821 is retained.

[0114] In some other implementations, when there is DL URLLC data that is assumed to have sparse traffic characteristics that may cause delay of some DL URLLC data as described above, UL CI is transmitted, which may be efficient in terms of cancellation signaling overhead.

[0115] In some other implementations, depending on whether a DL PI, a UL CI, or nothing is received, either RRC D or RRC U may be cancelled. For example, if a DL PI is configured and received, the UE may cancel RRC D and transmit RRC U, and if a UL CI is configured and received, the UE may cancel RRC U and receive RRC D. If nothing is received, i.e., in the default situation, in some implementations the default may be to cancel RRC U and receive RRC D and / or in some implementations the default may be to transmit RRC U and cancel RRC D.

[0116] In some other implementations, the priority of RRC D and / or RRC U may be dynamically indicated (e.g., via reactivation), and then the one with low priority or indicated as low priority may be revoked. In a situation where there is no DL data for SPS and there is UL data for CG PUSCH, several methods may be used. In one method, reactivation of SPS and CG may indicate low priority for SPS and high priority for CG, respectively. In another method, reactivation of SPS only indicates low priority for SPS (lower than CG) for one or several occasions, which in some implementations may override higher layer configured high priority SPS on these occasions. In another method, reactivation of CG only indicates high priority for CG (higher than SPS) for one or several occasions, which in some implementations may override higher layer configured low priority CG on these occasions.

[0117] In some other implementations, if DL data for SPS is present and UL data for CG PUSCH is not present, a similar implementation / method as above with opposite indications may be performed.

[0118] 9, an RRC U with a higher priority in one cell may overlap with an RRC D with a lower priority in another cell in the time domain. For example, but not limited to, the RRC U may be a CG opportunity for URLLC (921, 922, and 923) and / or the RRC D may include a first RRC D configuration (931, 935, RRC D conf1) and / or a second RRC D configuration (941, 945, RRC D conf2).

[0119] In some implementations, an RRC U opportunity in one cell may always cancel an RRC D opportunity in another cell.

[0120] In some other implementations, methods / implementations similar to those described above may be implemented.

[0121] In another scenario, RRC D and RRC U in the two cells may share the same priority.

[0122] In some other implementations, pre-configured revocation rules for specific RRC D and RRC U configurations may be implemented.

[0123] In some other implementations, the dynamic indication may be used to indicate which has lower (or higher) priority or which should be cancelled (or retained). In one implementation, in response to receiving a DL PI or deactivating an SPS, the UE may cancel RRC D and transmit RRC U; otherwise, the UE may cancel RRC U and receive RRC D.

[0124] In another implementation, in response to receiving a UL CI or deactivating a CG, the UE may cancel RRC U and receive RRC D; otherwise, the UE may cancel RRC D and transmit RRC U.

[0125] In another implementation, both DL PI and UL CI may be implemented, and in response to receiving DL PI, the UE may cancel RRC D and transmit RRC U, and in response to receiving UL CI, the UE may cancel RRC U and receive RRC D, and when nothing is received otherwise, it may be left to the UE to implement.

[0126] Various embodiments of the present disclosure may be summarized as follows: Whether a UE performs transmission or reception in one cell may be determined by DL signaling received by the UE to cancel or deactivate reception or transmission in another cell when the transmission or reception in one cell overlaps with the reception or transmission in another cell in the time domain.

[0127] In some embodiments, canceling dynamic U in one cell allows reception of RRC D in another cell when dynamic U has a lower priority than RRC D or has the same priority as RRC D. When dynamic U is not canceled (e.g., due to insufficient time for cancellation or absence of DL cancellation signal), transmission of dynamic U is performed. Some embodiments of the present disclosure may prioritize the high priority RRC D in the case of low priority dynamic U and high priority RRC D.

[0128] In some other embodiments, canceling or deactivating RRC D reception in one cell enables transmission of dynamic U in another cell when dynamic U has a lower priority than RRC D.

[0129] In some other embodiments, canceling or deactivating RRC D reception in one cell allows RRC U transmission in another cell when RRC D is configured or predefined or dynamically indicated as a higher priority and / or RRC U is configured or predefined or dynamically indicated as a lower priority. Some embodiments of the present disclosure may cancel channels / signals having a higher priority.

[0130] In some other embodiments, canceling or deactivating RRC U transmission in one cell allows RRC D reception in another cell when RRC D is configured or predefined or dynamically indicated as a higher priority and / or RRC U is configured or predefined or dynamically indicated as a lower priority. When cancellation or deactivation signaling is not received, the UE performs RRC U transmission and stops RRC D reception when RRC U and RRC D overlap in the time domain. When cancellation or deactivation signaling is not received and a condition is met, the UE performs reception of RRC D and stops RRC U transmission when RRC U and RRC D overlap in the time domain, which may include at least one of the following: multiple configurations provided for RRC U, one or more configurations that do not overlap with RRC D, or any configuration of RRC D. Some embodiments of the present disclosure may prioritize lower priority channels / signals.

[0131] In some other embodiments, dynamic U in one cell may cancel RRC D in another cell when dynamic U has higher or same priority compared to RRC D. The feedback regarding RRC D is canceled or set to a predefined value.

[0132] In some other embodiments, if RRC D has a higher priority than RRC U or RRC D has the same priority as RRC U, RRC D in one cell always revokes RRC U in another cell when RRC D and RRC U overlap in the time domain.

[0133] In some other embodiments, if RRC D has a lower priority than RRC U or RRC D has the same priority as RRC U, when RRC D and RRC U overlap in the time domain, RRC U in one cell always cancels RRC D in another cell.

[0134] In some other embodiments, dynamically indicating the priority of RRC U and / or RRC D may be performed under various conditions. Under one condition, the UE performs RRC D reception and stops RRC U transmission when RRC D is indicated by the gNB as a higher priority and / or RRC U is indicated as a lower priority. Under another condition, the UE performs RRC U transmission and stops RRC D reception when RRC D is indicated by the gNB as a lower priority and / or RRC U is indicated as a higher priority. The priority indication may be valid only for one or some occasions, and other occasions may have a priority configured by higher layer signaling. The priority indication overrides the priority configured by higher layers. When no dynamic priority indication for RRC D and / or RRC U is received, the higher layer configured priority is used.

[0135] In some other embodiments, one CORESET and / or SS configured for a UE is used to transmit a PDCCH having a certain priority level or a priority level higher than a threshold when the PDCCH and / or the channels / signals triggered or scheduled by the corresponding HARQ-ACK share the same priority level as the PDCCH or when the PDCCH and / or the channels / signals triggered or scheduled by the corresponding HARQ-ACK may have a different priority level than the PDCCH.

[0136] In some other embodiments, when the UE receives a CORESET and / or SS in one cell, the UE may cancel transmission of an uplink channel / signal in another cell. Specifically, when the CORESET / SS opportunity does not overlap with an uplink channel / signal and there is a downlink channel / signal triggered or scheduled by a PDCCH transmitted in the CORESET / SS opportunity, the cancellation begins Q ms after the end of the CORESET and / or SS, or at the beginning of a channel / signal triggered or scheduled by a PDCCH transmitted in the CORESET / SS. Q is a positive number. When the CORESET / SS opportunity overlaps with an uplink channel / signal, the cancellation begins at the beginning of the CORESET / SS opportunity.

[0137] In various embodiments of the present disclosure, "canceling" may also mean ceasing transmission or reception in the original time / frequency. The transmission or reception may be changed to another time / frequency resource. In various embodiments of the present disclosure, a cell may be generalized as a frequency resource and / or a time resource.

[0138] The present disclosure describes a method, an apparatus, and a computer-readable medium for wireless communication. The present disclosure addressed problems associated with resolving / handling directional conflicts in sub-band full duplex (SBFD) telecommunication systems. The method, device, and computer-readable medium described in the present disclosure may facilitate the execution of wireless communication by resolving directional conflicts in SBFD telecommunication systems, thus improving efficiency and overall performance. The method, device, and computer-readable medium described in the present disclosure may improve the overall efficiency of the wireless communication system.

[0139] References to features, advantages, or similar language throughout this specification do not imply that all of the features and advantages that may be realized by the solution should or are included in any single implementation thereof. Rather, language referring to features and advantages is understood to mean that the particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the solution. Thus, descriptions of features and advantages, and similar language throughout this specification may, but do not necessarily, refer to the same embodiment.

[0140] Moreover, the described features, advantages, and characteristics of the solution may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize in light of the description herein that the solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the solution.

Claims

1. 1. A method for wireless communication, the method comprising: a user equipment (UE) obtaining a first communication opportunity and a second communication opportunity, the first communication opportunity and the second communication opportunity being configured or scheduled to overlap in a time domain or to have a gap in the time domain between the first communication opportunity and the second communication opportunity that is less than a threshold, the first communication opportunity and the second communication opportunity being configured to communicate in opposite directions between the UE and a base station; determining, based on first information of the first communication opportunity and second information of the second communication opportunity, whether to cancel at least a portion of the first communication opportunity or to cancel at least a portion of the second communication opportunity; in response to determining to cancel at least the portion of the second communication opportunity, the UE canceling at least the portion of the second communication opportunity and executing the first communication opportunity; in response to determining to cancel at least the portion of the first communication opportunity, the UE cancels at least the portion of the first communication opportunity and executes the second communication opportunity. Including, The method, wherein the first communication opportunity and the second communication opportunity share a same configuration type.

2. the first communication opportunity is configured in a first cell and the second communication opportunity is configured in a second cell; or 2. The method of claim 1, wherein the first communication opportunity is configured in a first frequency resource and the second communication opportunity is configured in a second frequency resource.

3. The first information of the first communication opportunity is Configuration type information indicating whether the first communication opportunity is a first configuration type or a second configuration type; priority level information indicating a priority level of the first communication opportunity; communication direction information indicating whether the first communication opportunity is a downlink opportunity or an uplink opportunity; an uplink cancellation indication indicating that the first communication opportunity should be cancelled when the first communication opportunity is the uplink opportunity; or when the first communication opportunity is the downlink opportunity, a downlink preemption indication or a downlink deactivation indication indicating that the first communication opportunity should be cancelled. and The second information of the second communication opportunity is Configuration type information indicating whether the second communication opportunity is a first configuration type or a second configuration type; priority level information indicating a priority level of the second communication opportunity; communication direction information indicating whether the second communication opportunity is a downlink opportunity or an uplink opportunity; an uplink cancellation indication indicating that the second communication opportunity should be cancelled when the second communication opportunity is the uplink opportunity; or when the second communication opportunity is the downlink opportunity, a downlink preemption indication or a downlink deactivation indication indicating that the second communication opportunity should be cancelled. The method of claim 1 , comprising at least one of:

4. the first configuration type indicates a semi-statically configured communication opportunity; The method of claim 3 , wherein the second configuration type indicates a dynamically scheduled communication opportunity.

5. the first communication opportunity is of a second configuration type and is a downlink opportunity; the second communication opportunity is of the second configuration type and is an uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; The UE, The entire second communication opportunity, or At least the portion of the second communication opportunity that overlaps with the first communication opportunity in the time domain. The method according to any one of claims 1 to 4, further comprising deciding to cancel one of the following:

6. the first communication opportunity is of a second configuration type and is an uplink opportunity; the second communication opportunity is of the second configuration type and is a downlink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; The UE, The entire second communication opportunity, or At least the portion of the second communication opportunity that overlaps with the first communication opportunity in the time domain. The method according to any one of claims 1 to 4, further comprising deciding to cancel one of the following:

7. the first communication opportunity is of a first configuration type and is a downlink opportunity; the second communication opportunity is of the first configuration type and is an uplink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; The method according to any of claims 1 to 4, wherein the UE decides to cancel or postpone the second communication opportunity.

8. the first communication opportunity is of a first configuration type and is an uplink opportunity; the second communication opportunity is of the first configuration type and is a downlink opportunity; the first communication opportunity has a higher priority than the second communication opportunity; The method according to any of claims 1 to 4, wherein the UE decides to cancel or postpone the second communication opportunity.

9. the first communication opportunity is of a first configuration type; the second communication opportunity is of the first configuration type; the first communication opportunity has the same priority as the second communication opportunity; The method according to any of claims 1 to 4, wherein the UE decides to cancel or postpone the second communication opportunity according to a cancellation rule.

10. An apparatus, comprising: A memory that stores instructions a processor in communication with the memory; Equipped with When the processor executes the instructions, the processor: obtaining a first communication opportunity and a second communication opportunity, the first communication opportunity and the second communication opportunity being configured or scheduled to overlap in a time domain or to have a gap in the time domain between the first communication opportunity and the second communication opportunity that is less than a threshold, the first communication opportunity and the second communication opportunity being configured to communicate in opposite directions between the device and a base station; determining whether to cancel at least a portion of the first communication opportunity or cancel at least a portion of the second communication opportunity based on first information of the first communication opportunity and second information of the second communication opportunity; in response to determining that at least the portion of the second communication opportunity should be cancelled, cancelling at least the portion of the second communication opportunity and executing the first communication opportunity; in response to determining that at least the portion of the first communication opportunity should be cancelled, cancelling at least the portion of the first communication opportunity and implementing the second communication opportunity; configured to cause the apparatus to perform The apparatus, wherein the first communication opportunity and the second communication opportunity share a same configuration type.

11. the first communication opportunity is configured in a first cell and the second communication opportunity is configured in a second cell; or 11. The apparatus of claim 10, wherein the first communication opportunity is configured in a first frequency resource and the second communication opportunity is configured in a second frequency resource.

12. The first information of the first communication opportunity is Configuration type information indicating whether the first communication opportunity is a first configuration type or a second configuration type; priority level information indicating a priority level of the first communication opportunity; communication direction information indicating whether the first communication opportunity is a downlink opportunity or an uplink opportunity; an uplink cancellation indication indicating that the first communication opportunity should be cancelled when the first communication opportunity is the uplink opportunity; or when the first communication opportunity is the downlink opportunity, a downlink preemption indication or a downlink deactivation indication indicating that the first communication opportunity should be cancelled. and The second information of the second communication opportunity is Configuration type information indicating whether the second communication opportunity is a first configuration type or a second configuration type; priority level information indicating a priority level of the second communication opportunity; communication direction information indicating whether the second communication opportunity is a downlink opportunity or an uplink opportunity; an uplink cancellation indication indicating that the second communication opportunity should be cancelled when the second communication opportunity is the uplink opportunity; or when the second communication opportunity is the downlink opportunity, a downlink preemption indication or a downlink deactivation indication indicating that the second communication opportunity should be cancelled. The apparatus of claim 10 , comprising at least one of:

13. A non-transitory computer program product comprising a computer-readable program medium storing instructions that, when executed by a processor in a device, obtaining a first communication opportunity and a second communication opportunity, the first communication opportunity and the second communication opportunity being configured or scheduled to overlap in a time domain or to have a gap in the time domain between the first communication opportunity and the second communication opportunity that is less than a threshold, the first communication opportunity and the second communication opportunity being configured to communicate in opposite directions between the device and a base station; determining whether to cancel at least a portion of the first communication opportunity or cancel at least a portion of the second communication opportunity based on first information of the first communication opportunity and second information of the second communication opportunity; in response to determining that at least the portion of the second communication opportunity should be cancelled, cancelling at least the portion of the second communication opportunity and executing the first communication opportunity; in response to determining that at least the portion of the first communication opportunity should be cancelled, cancelling at least the portion of the first communication opportunity and implementing the second communication opportunity; and configured to cause the processor to execute The non-transient computer program product, wherein the first communication opportunity and the second communication opportunity share a same configuration type.

14. the first communication opportunity is configured in a first cell and the second communication opportunity is configured in a second cell; or 14. The non-transient computer program product of claim 13, wherein the first communication opportunity is configured on a first frequency resource and the second communication opportunity is configured on a second frequency resource.

Images