Methods, devices, and systems for resolving directional conflicts in a sub-band full duplex system

Abstract

The present disclosure describes methods, systems, and devices for resolving direction conflicts in a sub-band full duplex (SBFD) telecommunication system. The method includes obtaining a first communication occasion and a second communication occasion, the first communication occasion and the second communication occasion being configured or scheduled in opposite directions to overlap in a time domain or have a gap in the time domain that is less than a threshold value; determining whether to cancel at least a portion of the first communication occasion or to cancel at least a portion of the second communication occasion; in response to determining to cancel at least a portion of the second communication occasion, canceling the at least a portion of the second communication occasion and performing the first communication occasion; and in response to determining to cancel at least a portion of the first communication occasion, canceling the at least a portion of the first communication occasion and performing the second communication occasion.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications. Specifically, this disclosure relates to methods, apparatus, and systems for resolving directional conflicts in sub-band full-duplex (SBFD) telecommunications systems. Background Technology

[0002] Wireless communication technology is propelling the world towards an increasingly interconnected and networked society. High-speed, low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations). Next-generation networks promise to provide high-speed, low-latency, and ultra-reliable communication capabilities, meeting the needs of various industries and users.

[0003] With the rapid development of cellular mobile communication systems, Subband Full-Duplex (SBFD) technology may be a crucial feature for further improving the efficiency and performance of next-generation mobile communication technologies. SBFD can utilize different frequency resources to achieve full-duplex operation. SBFD can improve communication coverage and reduce communication latency because, although downlink (DL) and / or uplink (UL) resources cannot be accessed simultaneously, they are available at any time with proper configuration. Current technologies present problems / issues related to the implementation of SBFD. One such problem / issue may include directional conflict, in which different cells are configured or scheduled to have channels and / or signals with different link directions at a specific time.

[0004] This disclosure can solve at least one of the issues / problems associated with existing systems, particularly issues / problems related to direction conflicts, and this disclosure describes various embodiments that improve the efficiency and / or performance of wireless communication. Summary of the Invention

[0005] This document relates to methods, systems, and apparatuses for wireless communication, and more specifically, to methods, systems, and apparatuses for resolving direction conflicts in subband full-duplex (SBFD) telecommunications systems. Various embodiments of this disclosure enable the handling of direction conflicts in SBFD systems, which can reduce the implementation complexity of gNBs, improve resource utilization efficiency, and enhance the latency performance of Ultra-Reliable Low Latency Communication (URLLC) services.

[0006] In one embodiment, this disclosure describes a method for wireless communication. The method includes: obtaining a first communication opportunity and a second communication opportunity by a user equipment (UE), the first and second communication opportunities being configured or scheduled to overlap in the time domain or having an interval of less than a threshold between the first and second communication opportunities in the time domain, wherein the first and second communication opportunities are 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 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.

[0007] In one embodiment, this disclosure describes a method for wireless communication. The method includes: scheduling a first communication timing and a second communication timing by a base station to overlap in the time domain or have an interval of less than a threshold between the first and second communication timings in the time domain, wherein the first and second communication timings are configured for communication between a user equipment (UE) and the base station in opposite directions; executing the first communication timing by the base station in response to determining that at least a portion of the second communication timing is cancelled; and executing the second communication timing by the base station in response to determining that at least a portion of the first communication timing is cancelled.

[0008] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to perform the methods described above.

[0009] In some other embodiments, a device for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to perform the methods described above.

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

[0011] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0012] Figure 1A An example of a wireless communication system including a wireless network node and one or more user devices is shown.

[0013] Figure 1B An example of a cell configuration for a network node (e.g., a base station) is shown.

[0014] Figure 1C An example of cell configuration for user equipment is shown.

[0015] Figure 1D An example of cell configuration for another user equipment is shown.

[0016] Figure 2 An example of a network node is shown.

[0017] Figure 3 An example of a user device is shown.

[0018] Figure 4A A flowchart of a method for wireless communication is shown.

[0019] Figure 4B A flowchart of another method for wireless communication is shown.

[0020] Figure 5A A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0021] Figure 5B A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0022] Figure 5C A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0023] Figure 6 A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0024] Figure 7A A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0025] Figure 7B A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0026] Figure 8A A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0027] Figure 8B A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0028] Figure 9 A schematic diagram of another exemplary embodiment for wireless communication is shown. Detailed Implementation

[0029] This disclosure will now be described in detail below with reference to the accompanying drawings, which form a part of this disclosure and illustrate specific examples of embodiments by way of illustration. However, it should be noted that this disclosure may be embodied in various different forms, and therefore the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0030] Throughout the specification and claims, terms may have suggestive or implied meanings in the context, in addition to their expressly stated meanings. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include, in whole or in part, exemplary embodiments or combinations of embodiments.

[0031] Generally, terms can be understood at least in part from their use in context. For example, terms used herein, such as “and,” “or,” or “and / or,” can include a variety of meanings, which can depend at least in part on the context in which these terms are used. Typically, “or,” when used in an associative list, such as A, B, or C, means A, B, and C in an inclusive sense, and A, B, or C in an exclusive sense. Furthermore, the terms “one or more” or “at least one,” as used herein, can be used, at least in part on context, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can also be understood to convey either a singular or a plural usage, at least in part on context. Furthermore, the terms “based on” or “determined by” can be understood as not necessarily intended to convey an exclusive set of factors, but rather to allow for the existence of additional factors that are not necessarily explicitly described, which, too, depends at least in part on the context.

[0032] This disclosure describes methods and apparatus for resolving direction conflicts in subband full-duplex (SBFD) telecommunications systems.

[0033] Next-generation (NG) mobile communication systems are propelling the world towards an increasingly interconnected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and radio access network nodes (including but not limited to radio base stations). NG networks promise to provide high-speed, low-latency, and ultra-reliable communication capabilities, meeting the needs of various industries and users.

[0034] With the rapid evolution of cellular mobile communication systems, more and more cells will operate at higher frequencies. Subband full-duplex (SBFD) technology may be a crucial feature for further improving the efficiency and performance of next-generation mobile communication technologies. SBFD technology can utilize different frequency resources to achieve full-duplex operation. In some implementations, half-duplex mode (i.e., transmitting or receiving only at specific times) can be used to avoid increasing implementation complexity.

[0035] In some implementations, SBFD systems can be implemented differently from traditional Frequency Division Duplex (FDD) systems, where no specific frequency resources are dedicated to downlink and / or uplink. In other implementations, SBFD systems can be implemented to some extent similarly as Time Division Duplex (TDD) systems, where a frequency resource can be used for downlink transmission, uplink transmission, or both downlink and uplink transmission in a TDD manner. In some other implementations, unlike FDD / TDD systems, different frequency resources used in SBFD systems can have different downlink / uplink (DL / UL) time slot configurations and / or can be in the same frequency band. SBFD systems can improve communication coverage and / or reduce communication latency because, although DL and / or UL resources may not be accessible simultaneously in some cases, DL and / or UL resources can be available at any time through appropriate configuration.

[0036] Figure 1AA wireless communication system 100 is illustrated, comprising a wireless network node 118 (also referred to as a network base station 118) and one or more user equipment (UE) devices 110. The wireless network node may include a network base station, which may be a nodeB (NB, e.g., gNB) in a mobile telecommunications context. Each UE may wirelessly communicate with the wireless network node 118 via one or more radio channels 115. For example, a first UE 110 may wirelessly communicate with the wireless network node 118 via a channel including multiple radio channels during a specific time period. The network base station 118 may send 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 embodiment, the higher-layer signaling may include Radio Resource Control (RRC) messages.

[0037] In some embodiments, the SBFD system can treat different subbands as different cells, i.e., SBFD based on carrier-aggregation (CA) (CA-SBFD). Figure 1B The diagram illustrates a cell configuration 150 at a base station (e.g., a gNB), where, for CA-SBFD, the gNB can operate simultaneously on cell 1 (151, cell 1) and cell 2 (152, cell 2), or simultaneously on cell 1 and cell 3 (153, cell 3), and the UE can be configured with two cells or one cell. In some other implementations supporting in-band full duplex at the gNB (i.e., the same time / frequency domain resources can be used for both downlink and uplink simultaneously), the gNB can operate simultaneously on cell 1, cell 2, and cell 3. For example... Figure 1B As shown, 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, if two cells (via DL / UL configuration signaling or scheduling signaling) share the same DL / UL configuration, the UE can be configured to have one cell or two cells.

[0039] In some other implementations, the UE can be configured with two cells with different DL / UL configurations to take advantage of the benefits of SBFD (e.g., reduced latency, enhanced coverage). Due to the limited self-interference mitigation capability (i.e., UL interference to DL) on the UE side, the UE may not operate simultaneously in both cells when the two cells have different link directions. That is, the UE may not transmit and receive in both cells simultaneously, otherwise strong self-interference may hinder the reception of DL signals.

[0040] Figure 1C Cell configuration 160 for a first UE (UE1) is shown, wherein UE1 is configured with two cells, namely cell 1 and cell 2, which do not overlap with each other. Figure 1C It is shown that cell 1 and cell 2 are continuous in the frequency domain, but in some implementations, cell 1 and cell 2 may be continuous or discontinuous in the frequency band.

[0041] Figure 1D Cell configuration 170 for a second UE (UE2) is shown, where UE2 is configured with two cells, namely, cell 2 and cell 3, which are either fully or partially overlapping. Given that cell 3 is configured with a larger bandwidth, UE2 can enjoy higher DL throughput than UE1. In some implementations, for CA-SBFD on a carrier with a small bandwidth (e.g., 5 MHz bandwidth), it may be important and desirable to support overlapping cells in the frequency domain, considering that the small bandwidth may make it impossible to divide the carrier into smaller bandwidths due to the need for sufficient frequency resources for the Synchronization Signal Block (SSB).

[0042] In some other implementations, CA-SBFD can operate on one continuous carrier or several discontinuous carriers in the frequency band, and / or the above descriptions of these two scenarios can be unified.

[0043] Directional conflicts may occur in certain situations when different cells are configured or scheduled to utilize channels and / or signals with different link directions at specific times (e.g., utilizing different frequency resources / cells in the frequency domain and simultaneously in the time domain). The timing of a directional conflict may also include situations where, although two communication opportunities may not completely overlap in the time domain, they are configured / scheduled with a time-domain interval less than a threshold. For example, but not limited to, this threshold could be a few milliseconds (ms) (e.g., 1 ms or 0.5 ms).

[0044] This disclosure describes various embodiments for resolving / handling direction conflicts in SBFD or CA-SBFD systems under certain circumstances. Without a direction conflict handling mechanism, a gNB may have to avoid direction conflicts through configuration and / or scheduling; this approach is undesirable because it can significantly increase the implementation complexity of the gNB and reduce resource utilization efficiency. For example, if resources in two cells overlap in the time domain, resources in the other cell cannot be used even if resources in one cell are not in use. Simultaneously, when direction conflicts are not allowed, high-priority services may not be effectively prioritized, which degrades the latency performance of ultra-reliable low-latency communication (URLLC) services.

[0045] Figure 2 An example of an electronic device 200 implementing a network base station is shown. The example electronic device 200 may include wireless transmitting / receiving (Tx / Rx) circuitry 208 for transmitting / receiving communications with a UE and / or other base stations. The electronic device 200 may also include network interface circuitry 209 (e.g., optical or wired interconnect, Ethernet, and / or other data transmission media / protocols) for communicating between the base station and other base stations and / or the core network. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with operators, etc.

[0046] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include one or more processors 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for use by one or more processors 221 to perform functions of the network node. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0047] Figure 3An example of an electronic device (e.g., a user equipment (UE)) implementing terminal device 300 is shown. UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. UE 300 may include a communication interface 302, system circuitry 304, input / output interfaces (I / O) 306, display circuitry 308, and storage device 309. Display circuitry 308 may include a user interface 310. System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. System circuitry 304 may be implemented, for example, using one or more systems on a chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System circuitry 304 may be part of an implementation of any desired functionality in UE 300. In this regard, system circuitry 304 may include logic that facilitates, for example, decoding and playing music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (as an example, for internet connections); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0048] refer to Figure 3The communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316, which processes signal transmission and reception via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver, including modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaper, an analog-to-digital converter (ADC), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may conform to any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), channels, bit rates, and encodings. As a specific example, 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 originating from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0049] refer to Figure 3 System circuitry 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute instructions 326 to achieve the desired functionality of UE 300. Parameters 328 can provide and specify configuration and operational options for instructions 326. Memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that UE 300 will send or has received via communication interface 302. In various embodiments, system power for UE 300 may be provided by power storage devices such as batteries or transformers.

[0050] This disclosure describes various embodiments for resolving / handling orientation conflicts in SBFD or CA-SBFD systems under certain circumstances, which may be partially or wholly described above. Figures 2 to 3 The various embodiments of this disclosure can implement direction conflict handling in an SBFD system, which can reduce the implementation complexity of gNB, improve resource utilization efficiency, and / or improve the latency performance of URLLC services.

[0051] refer to Figure 4A This 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 a first communication opportunity and a second communication opportunity by a user equipment (UE), the first and second communication opportunities being configured or scheduled to overlap in the time domain or having an interval of less than a threshold between the first and second communication opportunities in the time domain, wherein the first and second communication opportunities are configured to communicate in opposite directions between the UE and a base station; step 420: 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 at least a portion of the second communication opportunity; step 430: 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 / or step 440: 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.

[0052] In various embodiments of this disclosure, the term "cancel" or "cancellation" in this context may mean discarding a transmission or reception in the original time / frequency; and / or changing (or rescheduling) the transmission or reception to other time / frequency resources.

[0053] In various embodiments of this disclosure, the term "UE perform" a communication timing may refer to the UE executing a communication timing: when the communication timing is an uplink timing, the UE sends the communication timing to the base station; and / or when the communication timing is a downlink timing, the UE receives the communication timing from the base station.

[0054] refer to Figure 4BThis 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 a first communication opportunity and a second communication opportunity by a base station to overlap in the time domain, or having an interval of less than a threshold between the first and second communication opportunities in the time domain, wherein the first and second communication opportunities are configured for communication between the user equipment (UE) and the base station in opposite directions; step 470: executing the first communication opportunity by the base station in response to determining that at least a portion of the second communication opportunity is cancelled; and / or step 480: executing the second communication opportunity by the base station in response to determining that at least a portion of the first communication opportunity is cancelled.

[0055] In various embodiments of this disclosure, the term "perform" a communication timing by the base station can mean that the base station executes a communication timing: when the communication timing is an uplink timing, the base station receives a communication timing from the UE; and / or when the communication timing is a downlink timing, the base station sends a communication timing to the UE.

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

[0057] In some other embodiments, the first information of the first communication timing includes at least one of the following: configuration type information indicating whether the first communication timing is a first configuration type or a second configuration type; priority information indicating the priority of the first communication timing; communication direction information indicating whether the first communication timing is a downlink timing or an uplink timing; an uplink cancellation indication indicating that the first communication timing is canceled when the first communication timing is an uplink timing; or a downlink preemption indication or downlink deactivation indication indicating that the first communication timing is canceled when the first communication timing is a downlink timing; and / or, the second information of the second communication timing includes at least one of the following: configuration type information indicating whether the second communication timing is a first configuration type or a second configuration type; priority information indicating the priority of the second communication timing; communication direction information indicating whether the second communication timing is a downlink timing or an uplink timing; an uplink cancellation indication indicating that the second communication timing is canceled when the second communication timing is an uplink timing; or a downlink preemption indication or downlink deactivation indication indicating that the second communication timing is canceled when the second communication timing is a downlink timing.

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

[0059] In various embodiments of this disclosure, “RRC D” derived from the radio resource control downlink and “RRC U” derived from the radio resource control uplink can refer to the semi-static configuration of downlink and uplink channels / signals that are independent of dynamic signaling. For example, but not limited to, RRC D can 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, RRC U can be a Sounding Reference Signal (SRS), a Physical Random Access Channel (PRACH), a Configure 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 State Report (BSR), or a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) for SPS-PDSCH.

[0060] In various embodiments of this disclosure, "Dynamic D" and "Dynamic U" can refer to dynamically scheduled downlink and uplink channels / signals, respectively. "Dynamic D" and "Dynamic U" are different from RRC D / U and require dynamic signaling to trigger. For example, but not limited to, Dynamic D can be a dynamically scheduled PDSCH or an aperiodic CSI-RS (A-CSI-RS). For example, but not limited to, Dynamic U can be a dynamically scheduled PUSCH, an aperiodic SRS, a PUCCH / PUSCH for A-CSI, or a HARQ-ACK for a dynamically scheduled PDSCH.

[0061] In various embodiments of this disclosure, different channels / signals can be assigned various levels of priority, 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".

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

[0063] In various embodiments, dynamic D / U in one cell and dynamic U / D in another cell may conflict in direction. The following describes in detail various scenarios of the first and second communication timings.

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

[0065] In some other embodiments, in response to control signaling or control signaling resources scheduling a first communication opportunity that overlaps with the 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 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 embodiments, the control signaling may include a CORESET or SS (scheduling signaling) opportunity.

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

[0067] In such Figure 5A In one scenario 500, a high-priority "Dynamic D" in one cell can overlap with a low-priority "Dynamic U" in another cell in the time domain. For example, but not limited to, the high-priority Dynamic D can be URLLC PDSCH 525 in time slot (t2) of cell 1, and the low-priority Dynamic U can be enhanced Mobile Broadband (eMBB) PUSCH 536 in time slot (t2) of cell 2. In some implementations, eMBB PDCCH 531 can schedule / signalize eMBB PUSCH 536, and / or URLLC PDCCH 521 in a high-priority CORESET or SS can schedule / signalize URLLC PDSCH 525. In this scenario 500, the high-priority "Dynamic D" can take precedence, and the low-priority "Dynamic U" can be discarded, canceled, delayed, postponed, or deferred.

[0068] like Figure 5A As shown, a pre-configured high-priority PDCCH 521 (e.g., URLLC PDCCH) timing (e.g., CORESET and / or SS) can prioritize high-priority PDCCH reception 525 when a direction conflict occurs with a low-priority PUSCH 536 (e.g., eMBB PUSCH). Then, when both the low-priority PUSCH timing and the high-priority PDCCH timing and corresponding PDSCH overlap, discarding the low-priority PUSCH can also resolve conflicts between the low-priority PUSCH and the high-priority PDSCH.

[0069] Note that PDSCH and / or corresponding HARQ-ACK scheduled by PDCCH during high-priority PDCCH timing can be automatically granted high priority without using the priority indication in PDCCH.

[0070] Another option is to discard the high-priority PDCCH opportunity and prioritize the low-priority PUSCH when the gNB ensures that there is no high-priority PDCCH transmission during the high-priority PDCCH opportunity and then schedules the low-priority PUSCH that overlaps with the high-priority PDCCH opportunity.

[0071] Figure 5B Another scenario 550 is illustrated, where a directional conflict exists only between the high-priority PDSCH and the low-priority PUSCH. Cancellation can begin at a duration 552 after the high-priority PDCCH ends. In some implementations, the duration 552 can 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 / discarded / delayed.

[0072] Figure 5C Another scenario 580 is shown, where a directional conflict exists only between the high-priority PDSCH and the low-priority PUSCH. Unlike the implementation in scenario 550, in scenario 580, cancellation begins at time point (582) at the start of the high-priority PDSCH 525. Therefore, for example, within the low-priority PUSCH 535, the first portion 538 is not cancelled, and only the second portion 539, starting at time point 582, is cancelled / discarded / delayed.

[0073] In some implementations, in order to achieve the timing for cancellation, there should be a predefined non-zero interval between the PDCCH that schedules / signals the high-priority PDSCH and the high-priority PDSCH.

[0074] In such Figure 6In another scenario 600, a high-priority "Dynamic U" in one cell overlaps with a low-priority "Dynamic D" in another cell in the time domain. For example, but not limited to, the high-priority Dynamic U could be URLLC PUSCH 635 in time slot (t2) of cell 2, and the low-priority Dynamic D could be Enhanced Mobile Broadband (eMBB) PDSCH 626 in time slot (t2) of cell 1. In some implementations, eMBB PDCCH 621 can be scheduled / signaled to eMBB PDSCH 626, and / or URLLC PDCCH 631 can be scheduled / signaled to URLLC PUSCH 635. In this scenario 600, the high-priority "Dynamic U" (e.g., URLLC PUSCH) can take precedence, and the low-priority "Dynamic D" (e.g., eMBB PDSCH) can be discarded, canceled, delayed, postponed, or deferred. In some implementations, there is a duration 602 between the start of the cancellation of URLLC PDCCH 631 and eMBB PDSCH 626. Duration 602 may include PDCCH blind detection (BD) time and / or PDSCH reception cancellation time.

[0075] In various embodiments, directional conflicts may occur between the RRC D / U in one cell and the dynamic U / D in another cell. The following describes in detail various scenarios of the first and second communication timings.

[0076] In some implementations, the first communication timing is a first configuration type and a downlink timing; the second communication timing is a second configuration type and an uplink timing; the first communication timing has a higher priority than the second communication timing; in response to the UE not receiving an uplink cancellation indication: the UE determines to cancel or postpone the first communication timing; and / or in response to the UE receiving an uplink cancellation indication: the UE determines to cancel the second communication timing.

[0077] In some other implementations, the first communication timing is a first configuration type and a downlink timing; the second communication timing is a second configuration type and an uplink timing; the first communication timing has the same priority as the second communication timing; in response to the UE not receiving an uplink cancellation indication: the UE determines to cancel or postpone the first communication timing; and / or in response to the UE receiving an uplink cancellation indication: the UE determines to cancel the second communication timing.

[0078] In some other implementations, the first communication timing is a first configuration type and a downlink timing; the second communication timing is a second configuration type and an uplink timing; the first communication timing has a higher priority than the second communication timing; in response to the UE receiving a downlink preemption indication for the first communication timing: the UE determines to cancel the first communication timing; and / or in response to the UE receiving a downlink deactivation indication for the first communication timing: the UE determines to deactivate the first communication timing; and / or in response to the UE not receiving a downlink preemption indication or a downlink deactivation indication for the first communication timing: the UE determines to cancel or postpone the second communication timing.

[0079] In some other implementations, the first communication timing is a first configuration type and a downlink timing; the second communication timing is a second configuration type and an uplink timing; the first communication timing has a lower priority than the second communication timing; and / or the UE determines to cancel or postpone the first communication timing.

[0080] In some other implementations, the UE discards the negative acknowledgment signal for the first communication opportunity that is canceled or postponed; or the UE feeds back a negative acknowledgment signal for the first communication opportunity that is canceled or postponed.

[0081] In some other implementations, the first communication timing is a first configuration type and an uplink timing; the second communication timing is a second configuration type and a downlink timing; the first communication timing has a lower priority than the second communication timing; and / or the UE determines to cancel or postpone the first communication timing.

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

[0083] In some other implementations, the first communication opportunity is a first configuration type; the second communication opportunity is a second 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 first communication opportunity.

[0084] In some other implementations, the first communication timing is a first configuration type and an uplink timing; the second communication timing is a second configuration type and a downlink timing; the first communication timing has the same priority as the second communication timing; and / or the UE determines to cancel or postpone the first communication timing.

[0085] In such Figure 7AIn another scenario 700, a high-priority RRC D (e.g., SP 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, but not limited to, the high-priority RRC D could be the SPS timing of URLLC (721, 722, 723) in each downlink slot in cell 1, and the low-priority dynamic U could be eMBB PUSCH / PUCCH 735. In some implementations, eMBBPDCCH 731 can schedule / signalize eMBB PUSCH / PUCCH 735.

[0086] In some implementations, low-priority dynamic Us can be discarded, canceled, delayed, postponed, or deferred. RRC D data / signals can arrive during the interval between UL authorization and dynamic U (e.g., time point 761, where URLLC data arrival can be sent at the next SPS timing due to the satisfied timeline), which allows time to cancel the dynamic U.

[0087] In some other implementations, a cancellation / drop / delay / postponement of dynamic U can be performed in response to receiving a UL Cancellation Indication (732 UL CI). When dynamic U is cancelled according to UL CI 732, the UE can receive RRC D. When dynamic U cannot be cancelled according to UL CI due to a timeline (e.g., at time point 762, where URLLC data arrival may not be sent at the next SPS timing due to an unmet timeline), the UE can send dynamic U, and the gNB can postpone DL data. When UL CI is not present, the UE can send dynamic U and / or may not receive high-priority "RRC D" (e.g., SPS) because DL data may not be present at, for example, a high-priority "RRC D" timing.

[0088] In another scenario where RRC D and Dynamic U share the same priority, the above implementation can be similarly applied to RRC D and Dynamic U with the same priority.

[0089] In some other implementations, high-priority RRC Ds can be cancelled or deactivated. Alternatively, high-priority RRC Ds can be delayed, postponed, or postponed.

[0090] exist Figure 7BIn some other implementations, RRC D can be cancelled in response to receiving DL signaling (e.g., DL preemption indication (782, DL PI, DL Preemption Indication) or deactivation (e.g., for SPS)). Dynamic U transmission can be permitted when RRC D is cancelled or deactivated in a cell. Otherwise, RRC D can take precedence. In some implementations, the downlink cancellation timing may be much shorter than the uplink cancellation timing, making the DL PI very close to the next SPS timing for URLLC. For example, the UE can prepare for dynamic U after receiving scheduling signaling; the UE can perform UL transmission T ms after receiving DL PI / deactivation 782; and / or the UE can cancel or postpone UL transmission if it does not receive DL PI / deactivation. In this scenario, T can be a very small duration, very close to 0 or less than 1 millisecond, because the UL channel / signal is already prepared. Therefore, this implementation can reduce the likelihood of delaying high-priority RRC D (e.g., URLLC data) because the cancellation time of RRC D is shorter compared to some other implementations.

[0091] In another scenario, a low-priority "RRC D" (e.g., SPS) in one cell may overlap with a high-priority "Dynamic U" in the time domain. In some implementations, the UE may transmit Dynamic U and discard the received RRC D, and send back a NACK (negative acknowledgment) for the discarded RRC D (e.g., SPS) (if present). In some other implementations, optionally, since NACK is deterministic information, the UE may discard NACK to save overhead.

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

[0093] 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, if overlapping high-priority data exists in the CG PUSCH, the UE may assume that the dynamic D is a discontinuous transmission (DTX) or erroneous reception. Otherwise, i.e., when there is no overlap or conflict, the UE receives the dynamic D.

[0094] In another scenario, RRC D / U in one cell and dynamic U / D in another cell can have the same priority and overlap in the time domain. In some implementations, the UE can always send dynamic U / D and cancel RRC D / U. In some other implementations for overlapping RRC D and dynamic U in the time domain, the UE can operate similarly to the scenario described above using DL or UL cancellation. For some other implementations for overlapping RRC U and dynamic D in the time domain, the UE can prioritize dynamic D, or implement it in a manner similar to the scenario described above, depending on the UE implementation.

[0095] In various embodiments, directional conflicts may occur between RRC D / U in one cell and RRC U / D in another cell. The following describes in detail various scenarios of the first and second communication timings.

[0096] In some implementations, the first communication timing is a first configuration type and a downlink timing; the second communication timing is a first configuration type and an uplink timing; the first communication timing has a higher priority than the second communication timing; and / or the UE determines to cancel or postpone the second communication timing.

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

[0098] In some other implementations, the first communication timing is a first configuration type and a downlink timing; the second communication timing is a first configuration type and an uplink timing; the first communication timing has a higher priority than the second communication timing; in response to receiving an uplink cancellation indication for the second communication timing, the UE determines to cancel or postpone the second communication timing; and / or in response to not receiving an uplink cancellation indication for the second communication timing, the UE determines to cancel or postpone the first communication timing.

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

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

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

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

[0103] In some other implementations, the first communication timing is a first configuration type and an uplink timing; the second communication timing is a first configuration type and a downlink timing; the first communication timing has a higher priority than the second communication timing; and / or the UE determines to cancel or postpone the second communication timing.

[0104] In some other implementations, the first communication opportunity is a first configuration type; the second communication opportunity is 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.

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

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

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

[0108] In such Figure 8A In another scenario 800, a high-priority RRC D (e.g., SPS) in one cell may overlap with a low-priority RRC U (e.g., CG PUSCH) in the time domain. For example, but not limited to, the RRC D may be an SPS timing for URLLC (821, 822, and 823), and / or the 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).

[0109] In some implementations, an RRC D timing in one cell can always cancel an RRC U timing in another cell. While this implementation may be simple, it may not be very efficient, considering that short-cycle, high-priority SPS timings in the case of intermittent DL URLLC data profiles can unnecessarily block many RRC U transmissions. Therefore, in some other implementations, there may be pre-configured cancellation rules for specific RRC D+RRCU combinations.

[0110] In some other implementations, DL PI and / or UL CI can be used to dynamically indicate which should be cancelled. In one implementation, in response to receiving an SPS DL PI or deactivation 852, high-priority RRC D 823 can be cancelled, such as... Figure 8A As shown. DL PI or deactivation 852 can indicate the absence of DL data. When RRC D 823 is cancelled, the UE can send a low-priority RRC U (e.g., 835); otherwise, the UE receives a high-priority RRC D. In some implementations, the deactivation signaling of an SPS can deactivate only a limited number of subsequent SPSs.

[0111] In some other implementations of scheduling multiple RRC U timings, such as Figure 8A As shown, RRC Uconf1 831 in timing t0 is canceled, and the UE can choose RRC Uconf2 841 in timing t0 if RRC Uconf2 841 is available. Configuring multiple low-priority CG configurations may not be cost-effective.

[0112] Some of the above embodiments can avoid delays in high-priority DL data due to the potentially short processing intervals of DL PIs. Some of the above embodiments can be signaling consumption methods because, due to a lack of knowledge about UL data arrivals at the gNB (e.g., CG-PUSCH) or explicit UL transmissions (e.g., SRS), w DL PIs or activation / deactivation signaling may be frequently sent across all RRC U opportunities. It is desirable that SPS deactivation differs from a specific mechanism that deactivates all subsequent SPS opportunities until a reactivation signaling is received. Here, SPS deactivation can only deactivate one SPS opportunity, thus saving reactivation signaling.

[0113] In such Figure 8BIn some other embodiments shown, a low-priority RRC U (e.g., 835) can be cancelled upon receiving UL CI 865 of CG-PUSCH or upon deactivation. When RRC U 835 is cancelled, the UE receives RRC D 823; otherwise, the UE sends RRC U. There is a cost associated with this embodiment: cancelling the uplink timing (e.g., RRC U 835) may take longer; and therefore, SPS can be cancelled if UL CI 865 is not received in time. For example, as... Figure 8B As shown, RRC U conf1 (835) in timing t2 is canceled, and the UE can choose RRC U conf2 (845) in timing t2 if RRC U conf2 (845) is available.

[0114] In some other implementations with multiple RRC U configuration sets, the RRC D timing (821) in t0 can be cancelled when the RRC D timing overlaps with the configuration timing of any RRC U and no cancellation signaling is received, such as... Figure 8B As shown; and therefore, all RRC U configurations are available. For example, in some cases where the gNB wants to use the RRC D timing (821) in t0, RRC U conf1 (831) in t0 can be cancelled. Alternatively, in some other implementations, the RRC D timing may not be cancelled when certain conditions are met. For example, when at least one RRC U configuration does not overlap with RRC D, the RRC D timing can be retained, and the RRC U configuration with a timing that overlaps with the RRC D timing can be cancelled, for example, RRC U conf2 841 does not overlap with RRC D 821, and therefore RRC U conf1 831 is cancelled and RRC D 821 is retained.

[0115] In some other implementations, it may be effective in eliminating signaling overhead because UL CI is sent when there is DL URLLC data that is assumed to have sparse service characteristics, which may cause some DL URLLC data to be delayed as described above.

[0116] In some other implementations, RRC D or RRC U can be cancelled based on whether DL PI and UL CI are received, or whether DL PI and UL CI are not received. For example, when DL PI is configured and received, the UE can cancel RRC D and send RRC U; and when UL CI is configured and received, the UE can cancel RRC U and receive RRC D. When neither DL PI nor UL CI is received, i.e., by default, in some implementations, RRC U can be cancelled by default and RRC D can be received; and / or in some implementations, RRC U can be sent by default and RRC D can be cancelled.

[0117] In some other implementations, priorities for RRC D and / or RRC U can be dynamically indicated (e.g., via reactivation), and then one with lower priority or indicated as having lower priority can be canceled. Several methods can be used when there is no DL data for SPS and UL data for CG PUSCH is present. In one method, reactivation of SPS and CG can indicate low priority for SPS and high priority for CG, respectively. In another method, only reactivation of SPS indicates low priority (below CG) for SPS for one or more times, and in some implementations, this can override the high priority of the higher-level configuration of SPS in these times. In yet another method, only reactivation of CG indicates higher priority (above SPS) for CG for one or more times, and in some implementations, this can override the low priority of the higher-level configuration of CG in these times.

[0118] In some other implementations, when DL data for SPS is available but UL data for CG PUSCH is not available, similar implementations / methods described above with the opposite instructions can be performed.

[0119] In such Figure 9 In another scenario 900 shown, a high-priority RRC U in one cell may overlap with a low-priority RRC D in another cell in the time domain. For example, but not limited to, the RRC U may be a CG timing 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).

[0120] In some implementations, an RRC U timing in one cell can always cancel an RRC D timing in another cell.

[0121] In some other implementations, similar methods / implementations described above can be achieved.

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

[0123] In some implementations, pre-configured cancellation rules can be implemented for specific RRC D and RRC U configurations.

[0124] In some other implementations, dynamic indications can be used to indicate which has a lower (or higher) priority, or to indicate which to cancel (or retain). In one implementation, in response to receiving a DL PI or deactivation from an SPS, the UE can cancel RRC D and send RRC U; otherwise, the UE can cancel RRC U and receive RRC D.

[0125] In another implementation, in response to receiving a UL CI or deactivation of a CG, the UE can cancel RRC U and receive RRC D; otherwise, the UE can cancel RRC D and send RRC U.

[0126] In another implementation, both DL PI and UL CI can be implemented: in response to receiving DL PI, the UE can cancel RRC D and send RRC U; in response to receiving UL CI, the UE can cancel RRC U and receive RRC D; otherwise, when neither DL PI nor UL CI is received, this can be implemented at the discretion of the UE.

[0127] Various embodiments of this disclosure can be summarized as follows. When transmission or reception in one cell overlaps with reception or transmission in another cell in the time domain, whether the UE performs transmission or reception in one cell can be determined by the DL signaling received by the UE to cancel or deactivate reception or transmission in the other cell.

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

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

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

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

[0132] In some other embodiments, when a dynamic user (U) has a higher or equal priority than an RRC D (RRCD), a dynamic user in one cell can cancel the RRC D in another cell. This can either cancel the feedback to the RRC D or set the feedback to the RRC D to a predefined value.

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

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

[0135] In some other embodiments, dynamic prioritization of RRC U and / or RRC D can be performed under various conditions. Under one condition, when RRC D is indicated as higher priority by the gNB and / or RRC U is indicated as lower priority, the UE performs RRC D reception and discards RRC U transmission. Under another condition, when RRC D is indicated as lower priority by the gNB and / or RRC U is indicated as higher priority, the UE performs RRC U transmission and discards RRC D reception. Priority indication is effective only for one or more instances; other instances may have priorities configured by higher-layer signaling. Priority indication overrides priorities configured by higher layers. When no dynamic priority indication is received for RRC D and / or RRC U, the priorities configured by higher layers are used.

[0136] In some other embodiments, when a channel / signal triggered or scheduled by the PDCCH and / or the corresponding HARQ-ACK shares the same priority as the PDCCH; or when a channel / signal triggered or scheduled by the PDCCH and / or the corresponding HARQ-ACK may have a different priority than the PDCCH, a CORESET and / or SS configured for the UE is used to transmit a PDCCH with a priority of one or higher than a threshold.

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

[0138] In various embodiments of this disclosure, "cancel" can also mean discarding a transmission or reception in the original time / frequency. The transmission or reception can be changed to other time / frequency resources. In various embodiments of this disclosure, a cell can be generalized as a frequency and / or time resource.

[0139] This disclosure describes methods, apparatus, and computer-readable media for wireless communication. This disclosure solves the problem of resolving / handling direction conflicts in sub-band full-duplex (SBFD) telecommunications systems. The methods, apparatus, and computer-readable media described in this disclosure can improve the performance of wireless communication by resolving direction conflicts in SBFD telecommunications systems, thereby improving efficiency and overall performance. The methods, apparatus, and computer-readable media described in this disclosure can improve the overall efficiency of wireless communication systems.

[0140] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable using this solution should be included or included in any single implementation thereof. Rather, the language referring to these features and advantages is to be understood as indicating that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, throughout this specification, discussions of these features and advantages, as well as similar language, may refer to, but are not necessarily, the same embodiment.

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

Claims

1. A method for wireless communication, comprising: A first communication opportunity and a second communication opportunity are obtained by a user equipment (UE), the first communication opportunity and the second communication opportunity being configured or scheduled to overlap in the time domain or have an interval of less than a threshold in the time domain between the first communication opportunity and the second communication opportunity, wherein the first communication opportunity and the second communication opportunity are configured to communicate in opposite directions between the UE and the base station. The UE determines, based on first information of the first communication timing and second information of the second communication timing, whether to cancel at least a portion of the first communication timing or at least a portion of the second communication timing. In response to determining at least a portion of canceling the second communication timing, the UE cancels at least a portion of the second communication timing and executes the first communication timing; and In response to determining that at least a portion of the first communication timing is to be cancelled, the UE cancels at least a portion of the first communication timing and executes the second communication timing. The UE is performing a sub-band full-duplex (SBFD) operation.

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

3. The method according to claim 1, wherein: The first information at the first communication timing includes at least one of the following: Configuration type information indicates whether the first communication event is a first configuration type or a second configuration type. Priority information indicates the priority of the first communication opportunity. Communication direction information indicates whether the first communication opportunity is a downlink opportunity or an uplink opportunity. Uplink cancellation indication, indicating that the first communication opportunity is cancelled when the first communication opportunity is an uplink opportunity, or A downlink preemption indication or a downlink deactivation indication indicates that the first communication opportunity is cancelled if the first communication opportunity is a downlink opportunity; and The second information at the second communication timing includes at least one of the following: Configuration type information indicates whether the second communication timing is a first configuration type or a second configuration type. Priority information, indicating the priority of the second communication opportunity. Communication direction information indicates whether the second communication timing is a downlink timing or an uplink timing. Uplink cancellation indication, indicating that the second communication opportunity is cancelled when the second communication opportunity is an uplink opportunity, or Downlink preemption indication or downlink deactivation indication indicates that the second communication opportunity is canceled when the second communication opportunity is a downlink opportunity.

4. The method according to claim 3, wherein: The first configuration type indicates the timing of communication for a semi-static configuration; and The second configuration type indicates the timing of dynamically scheduled communication.

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

6. The method according to claim 5, wherein: In response to control signaling or control signaling resources that schedule the first communication opportunity that overlaps with the second communication opportunity, the UE cancels at least a portion of the second communication opportunity at the beginning of the control signaling or control signaling resources, and In response to control signaling or control signaling resources that schedule 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.

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

8. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the second configuration type and the uplink timing; 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 whether to cancel or postpone the first communication opportunity; and In response to the UE receiving the uplink cancellation indication: The UE determines when to cancel the second communication.

9. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the second configuration type and the uplink timing; 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 whether to cancel or postpone the first communication opportunity; and In response to the UE receiving the uplink cancellation indication: The UE determines when to cancel the second communication.

10. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the second configuration type and the uplink timing; 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 when to cancel the first communication opportunity; In response to the UE receiving a downlink deactivation indication for the first communication timing: The UE determines to deactivate the first communication opportunity; and In response to the UE not receiving the downlink preemption indication or the downlink deactivation indication for the first communication opportunity: The UE determines whether to cancel or postpone the second communication opportunity.

11. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the second configuration type and the uplink timing; The first communication opportunity has a lower priority than the second communication opportunity; and The UE determines whether to cancel or postpone the first communication opportunity.

12. The method of claim 11, wherein: The UE discards the negative acknowledgment signal for the cancellation or postponement of the first communication opportunity; or The UE provides a negative acknowledgment signal in response to the cancellation or postponement of the first communication opportunity.

13. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the uplink opportunity; The second communication timing is the second configuration type and downlink timing; The first communication opportunity has a lower priority than the second communication opportunity; and The UE determines whether to cancel or postpone the first communication opportunity.

14. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the uplink opportunity; The second communication timing is the second configuration type and downlink timing; The first communication opportunity has a higher priority than the second communication opportunity; and The UE determines whether the second communication timing is a discontinuous transmission or an erroneous reception.

15. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type; The second communication timing is the second configuration type; The first communication opportunity has the same priority as the second communication opportunity; and The UE determines whether to cancel or postpone the first communication opportunity.

16. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the uplink opportunity; The second communication timing is the second configuration type and downlink timing; The first communication opportunity has the same priority as the second communication opportunity; and The UE determines whether to cancel or postpone the first communication opportunity.

17. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the first configuration type and the uplink timing; The first communication opportunity has a higher priority than the second communication opportunity; and The UE determines whether to cancel or postpone the second communication opportunity.

18. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the first configuration type and the uplink timing; 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 determines to cancel or postpone the first communication opportunity; and In response to not receiving the downlink preemption indication and the downlink deactivation indication for the first communication opportunity, the UE determines to cancel or postpone the second communication opportunity.

19. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the first configuration type and the uplink timing; 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; and In response to not receiving the uplink cancellation indication for the second communication opportunity, the UE determines to cancel or postpone the first communication opportunity.

20. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the first configuration type and the uplink timing; 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 determines 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; and 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 determines to cancel or postpone the second communication opportunity.

21. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the first configuration type and the uplink timing; The first communication opportunity has a higher priority than the second communication opportunity; and In response to the reactivation of the first communication opportunity and the second communication opportunity to indicate that the first communication opportunity has a lower priority than the second communication opportunity, the UE determines to cancel or postpone the first communication opportunity.

22. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the first configuration type and the uplink timing; The first communication opportunity has a higher priority than the second communication opportunity; and 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 determines to cancel or postpone the first communication opportunity.

23. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the downlink opportunity; The second communication timing is the first configuration type and the uplink timing; The first communication opportunity has a higher priority than the second communication opportunity; and 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.

24. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the uplink opportunity; The second communication timing is the first configuration type and downlink timing; The first communication opportunity has a higher priority than the second communication opportunity; and The UE determines whether to cancel or postpone the second communication opportunity.

25. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type; The second communication opportunity is the first configuration type; The first communication opportunity has the same priority as the second communication opportunity; and The UE determines whether to cancel or postpone the second communication opportunity based on the cancellation rules.

26. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the uplink opportunity; The second communication timing is the first configuration type and downlink timing; 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; and In response to not receiving the downlink preemption indication and the downlink deactivation indication for the second communication opportunity, the UE determines to cancel or postpone the first communication opportunity.

27. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the uplink opportunity; The second communication timing is the first configuration type and downlink timing; 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 determines to cancel or postpone the first communication opportunity; and In response to not receiving the uplink cancellation indication for the first communication opportunity, the UE determines to cancel or postpone the second communication opportunity.

28. The method according to any one of claims 1 to 4, wherein: The first communication opportunity is the first configuration type and the uplink opportunity; The second communication timing is the first configuration type and downlink timing; 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 determines 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; and In response to not receiving the uplink cancellation indication for the first communication opportunity and not receiving the downlink preemption indication and the downlink deactivation indication for the second communication opportunity, the UE determines to cancel or postpone the second communication opportunity.

29. A method for wireless communication, comprising: The base station schedules a first communication opportunity and a second communication opportunity to overlap in the time domain or have an interval in the time domain between the first communication opportunity and the second communication opportunity that is less than a threshold, wherein the first communication opportunity and the second communication opportunity are configured for communication between the user equipment (UE) and the base station in opposite directions. In response to determining that at least a portion of the second communication timing is to be cancelled, the base station executes the first communication timing; and In response to determining that at least a portion of the first communication opportunity has been cancelled, the base station executes the second communication opportunity. The base station performs sub-band full-duplex (SBFD) operation.

30. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 29.

31. A computer-readable storage medium on which code is stored, the code, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 29.

Images