METHODS FOR INTRA-UE UL-DL COLLISION HANDLING IN SINGLE CC UE CONFIGURATION IN GNB-ONLY SUBBAND FULL-DUPLEX (SBFD) NETWORK

BACKGROUND
Field

The present disclosure relates generally to communication systems, and more particularly, to techniques of methods and apparatuses for intra-UE UL-DL collision handling in a single component carrier UE configuration in a gNB-only Subband Full-duplex (SBFD) network.

Background

The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE. In certain configurations, the UE receives, from a base station, a carrier time division duplexing (TDD) configuration of time slots and symbols for a component carrier (CC). The UE receives, from the base station, one or more subband TDD configurations specific to a subband for the CC. The UE determines, according to the carrier TDD configuration and the subband TDD configurations, whether a collision exists between an uplink (UL) transmission and a downlink (DL) reception for each of the time slots and the symbols. The UE selects one of the UL transmission and the DL reception for one of more of the time slots and the symbols with the collision based on a UE-specific link direction configuration or a plurality of priority rules.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2 is a diagram illustrating a base station in communication with a UE in an access network.

FIG. 3 illustrates an example logical architecture of a distributed access network.

FIG. 4 illustrates an example physical architecture of a distributed access network.

FIG. 5 is a diagram showing an example of a DL-centric slot.

FIG. 6 is a diagram showing an example of an UL-centric slot.

FIG. 7 is a diagram illustrating example procedure between a UE and a base station.

FIG. 8 is a diagram illustrating examples of subband(s) in a CC.

FIG. 9 is a diagram illustrating an example of slot symbols of a half-duplex UE TDD configuration in a SBFD network.

FIG. 10 is a diagram illustrating examples of collisions between an UL transmission and a DL reception.

FIG. 11 is a diagram illustrating the priority rule related to a cell-specific semi-static UL transmission and a dynamic DL reception.

FIG. 12 is a diagram illustrating the priority rule related to a dynamic UL transmission and a cell-specific semi-static DL reception.

FIG. 13 is a diagram illustrating the priority rule related to a dynamic DL reception and a dedicated semi-static UL transmission.

FIG. 14 is a diagram illustrating the priority rule related to a dedicated semi-static DL reception and a dynamic UL transmission.

FIG. 15 is a diagram illustrating the priority rule related to a dynamic UL transmission and a dynamic DL reception.

FIG. 16 is a diagram illustrating the priority rule related to a cell-specific semi-static UL transmission and a dedicated or cell-specific semi-static DL reception.

FIG. 17 is a diagram illustrating the priority rule related to a dedicated semi-static UL transmission and a cell-specific semi-static DL reception.

FIG. 18 is a diagram illustrating the priority rule related to a dedicated semi-static UL transmission and a dedicated semi-static DL reception.

FIG. 19 is a flow chart of a method (process) for wireless communication of a UE.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunications systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example aspects, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through backhaul links 132 (e.g., SI interface). The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 through backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over backhaul links 134 (e.g., X2 interface). The backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102′ may have a coverage area 110′ that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102/UEs 104 may use spectrum up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102′ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

A base station 102, whether a small cell 102′ or a large cell (e.g., macro base station), may include an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band (e.g., 3 GHz-300 GHz) has extremely high path loss and a short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 108a. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 108b. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180/UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a location management function (LMF) 198, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the SMF 194 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services.

The base station may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

Although the present disclosure may reference 5G New Radio (NR), the present disclosure may be applicable to other similar areas, such as LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communications (GSM), or other wireless/radio access technologies.

FIG. 2 is a block diagram of a base station 210 in communication with a UE 250 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 275. The controller/processor 275 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 275 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 216 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 274 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 250. Each spatial stream may then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 250, each receiver 254RX receives a signal through its respective antenna 252. Each receiver 254RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functionality associated with various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial streams destined for the UE 250. If multiple spatial streams are destined for the UE 250, they may be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 210. These soft decisions may be based on channel estimates computed by the channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 210 on the physical channel. The data and control signals are then provided to the controller/processor 259, which implements layer 3 and layer 2 functionality.

The controller/processor 259 can be associated with a memory 260 that stores program codes and data. The memory 260 may be referred to as a computer-readable medium. In the UL, the controller/processor 259 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 259 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 210, the controller/processor 259 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 258 from a reference signal or feedback transmitted by the base station 210 may be used by the TX processor 268 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 268 may be provided to different antenna 252 via separate transmitters 254TX. Each transmitter 254TX may modulate an RF carrier with a respective spatial stream for transmission. The UL transmission is processed at the base station 210 in a manner similar to that described in connection with the receiver function at the UE 250. Each receiver 218RX receives a signal through its respective antenna 220. Each receiver 218RX recovers information modulated onto an RF carrier and provides the information to a RX processor 270.

The controller/processor 275 can be associated with a memory 276 that stores program codes and data. The memory 276 may be referred to as a computer-readable medium. In the UL, the controller/processor 275 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 250. IP packets from the controller/processor 275 may be provided to the EPC 160. The controller/processor 275 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

New radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)). NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and may include support for half-duplex operation using time division duplexing (TDD). NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) service.

A single component carrier bandwidth of 100 MHz may be supported. In one example, NR resource blocks (RBs) may span 12 sub-carriers with a sub-carrier bandwidth of 60 kHz over a 0.25 ms duration or a bandwidth of 30 kHz over a 0.5 ms duration (similarly, 50 MHz BW for 15 kHz SCS over a 1 ms duration). Each radio frame may consist of 10 subframes (10, 20, 40 or 80 NR slots) with a length of 10 ms. Each slot may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each slot may be dynamically switched. Each slot may include DL/UL data as well as DL/UL control data. UL and DL slots for NR may be as described in more detail below with respect to FIGS. 5 and 6.

The NR RAN may include a central unit (CU) and distributed units (DUs). A NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP), access point (AP)) may correspond to one or multiple BSs. NR cells can be configured as access cells (ACells) or data only cells (DCells). For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity and may not be used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals (SS) in some cases DCells may transmit SS. NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.

FIG. 3 illustrates an example logical architecture of a distributed RAN 300, according to aspects of the present disclosure. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be a central unit (CU) of the distributed RAN. The backhaul interface to the next generation core network (NG-CN) 304 may terminate at the ANC. The backhaul interface to neighboring next generation access nodes (NG-ANs) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term). As described above, a TRP may be used interchangeably with “cell.”

The TRPs 308 may be a distributed unit (DU). The TRPs may be connected to one ANC (ANC 302) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific ANC deployments, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

The local architecture of the distributed RAN 300 may be used to illustrate fronthaul definition. The architecture may be defined that support fronthauling solutions across different deployment types. For example, the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). The architecture may share features and/or components with LTE. According to aspects, the next generation AN (NG-AN) 310 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.

The architecture may enable cooperation between and among TRPs 308. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 302. According to aspects, no inter-TRP interface may be needed/present.

According to aspects, a dynamic configuration of split logical functions may be present within the architecture of the distributed RAN 300. The PDCP, RLC, MAC protocol may be adaptably placed at the ANC or TRP.

FIG. 4 illustrates an example physical architecture of a distributed RAN 400, according to aspects of the present disclosure. A centralized core network unit (C-CU) 402 may host core network functions. The C-CU may be centrally deployed. C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity. A centralized RAN unit (C-RU) 404 may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have distributed deployment. The C-RU may be closer to the network edge. A distributed unit (DU) 406 may host one or more TRPs. The DU may be located at edges of the network with radio frequency (RF) functionality.

FIG. 5 is a diagram 500 showing an example of a DL-centric slot. The DL-centric slot may include a control portion 502. The control portion 502 may exist in the initial or beginning portion of the DL-centric slot. The control portion 502 may include various scheduling information and/or control information corresponding to various portions of the DL-centric slot. In some configurations, the control portion 502 may be a physical DL control channel (PDCCH), as indicated in FIG. 5. The DL-centric slot may also include a DL data portion 504. The DL data portion 504 may sometimes be referred to as the payload of the DL-centric slot. The DL data portion 504 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE). In some configurations, the DL data portion 504 may be a physical DL shared channel (PDSCH).

The DL-centric slot may also include a common UL portion 506. The common UL portion 506 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion 506 may include feedback information corresponding to various other portions of the DL-centric slot. For example, the common UL portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion 506 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information.

As illustrated in FIG. 5, the end of the DL data portion 504 may be separated in time from the beginning of the common UL portion 506. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)). One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric slot and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

FIG. 6 is a diagram 600 showing an example of an UL-centric slot. The UL-centric slot may include a control portion 602. The control portion 602 may exist in the initial or beginning portion of the UL-centric slot. The control portion 602 in FIG. 6 may be similar to the control portion 502 described above with reference to FIG. 5. The UL-centric slot may also include an UL data portion 604. The UL data portion 604 may sometimes be referred to as the pay load of the UL-centric slot. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS). In some configurations, the control portion 602 may be a physical DL control channel (PDCCH).

As illustrated in FIG. 6, the end of the control portion 602 may be separated in time from the beginning of the UL data portion 604. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity). The UL-centric slot may also include a common UL portion 606. The common UL portion 606 in FIG. 6 may be similar to the common UL portion 506 described above with reference to FIG. 5. The common UL portion 606 may additionally or alternatively include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric slot and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS), even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

As discussed above, NR may utilize OFDM with a CP on the uplink and downlink and may include support for half-duplex operation using TDD. In certain configurations, carrier aggregation may apply such that multiple component carriers (CCs) may be assigned to a single user in the UE. The half-duplex UE may operate over in a TDD carrier which is partitioned between uplink and downlink on certain symbols (i.e., a CC with opposite link directions: DL only or UL only in different frequency subbands) or slots. Such a deployment can offer gains in: (1) lower latency, since the UE can do half-duplex Frequency Division Duplex (FDD) in the carrier, sparing the alignment delay to UL-DL and DL-UL switching points of TDD; and (2) UL coverage extension in FR2 by enabling longer uplink transmit durations for repetitions. For flexible scheduling and optimized allocations, the UE may need to be configured with the subband partitioning in frequency and the time location of partitioned symbols. Thus, there are some issues to be solved as to: (1) how the SBFD layout may be configured to the UE so as to minimize standardization effort; (2) how the relationship between the TDD configuration and the legacy TDD configuration may be; and (3) how dynamic scheduling decisions are supported as to the UE link direction or the SBFD layout itself. In addressing these issues, it is desired that common configurations for the UE (broadcasted as part of SIB) need to be backward compatible with the legacy UEs, and single frequency partition may be achieved. Further, a constraint may be imposed with the subband partitioning such that there is only a UL-subband in the legacy DL symbols/slots, as interference to adjacent carrier must be kept below bounds.

In certain configurations, the UE may be configured to have UL/DL allocation between time slots, and the UL/DL allocation requires a split of the UE resources between the two directions. Specifically, there are multiple different signaling mechanisms that provide information to the UE on whether the resources are used for the UL transmission or DL reception. One of the mechanisms is semi-static signaling through RRC, where the network (i.e., base station) may send configuration information to the UE by RRC signaling, such that the UE is configured with the information related to a certain UL/DL allocation (e.g., a certain set of OFDM symbols is assigned to DL UL transmissions). In certain configurations, the RRC-signaled pattern is expressed as a concatenation of up to two sequences of DL-flexible-UL, together spanning a configurable period. Further, the UE may be configured with 2 patterns, e.g., one cell-specific provided as part of system information and one dedicated signaled in a device-specific manner. The resulting pattern is obtained by combining these two where the dedicated pattern can further restrict the flexible symbols signaled in the cell-specific pattern to be either DL or UL.

Another signaling mechanism is dynamic slot-format indication, where the base station dynamically signals the UL/DL allocation to the UE using a slot-format indicator (SFI), in which the slot format may indicate the number of OFDM symbols that are DL, flexible or UL. In certain configurations, the SFI message is in the form of a RRC-configured SFI table, where each row in the table is constructed from a set of predefined DL/flexible/UL patterns with one slot duration. Upon receiving the SFI, the UE may use the value as an index in the SFI table to obtain the UL/DL allocation pattern for one or more slots.

FIG. 7 is a diagram illustrating an example transmission procedure between a UE and a base station. Specifically, the UE 710 as shown in FIG. 7 is a half-duplex UE. At operation 730, the UE 710 receives a SIB broadcasted by the base station 720. Specifically, the SIB includes a carrier TDD configuration (e.g., TDD-UL-DL-ConfigCommon) for a single CC of each of a plurality of serving cells in the UE 710 and a subband TDD configuration (e.g., TDD-UL-DLConfigSubbandCommon) for a subband in the single CC, such that the UE 710 may configure the subband based on the subband TDD configuration. In certain configurations, the base station 720 broadcasts the SIB to all UEs, including the UE 710 and other UEs, available in the system. When a legacy UE receives the SIB being broadcasted by the base station 720, the legacy UE may recognize the carrier TDD configuration (e.g., TDD-UL-DL-ConfigCommon) but not the subband TDD configuration (e.g., TDD-UL-DLConfigSubbandCommon). In certain configurations, the subband TDD configuration includes information specifying the frequency partition of the CC, such that the UE may partition the subband in the frequency band of the CC based on the subband TDD configuration. At operation 740, the UE 710 configures the subband based on the subband TDD configuration received from the base station 720.

FIG. 8 is a diagram illustrating examples of subbands in a CC. Specifically, the subband is specified by a plurality of resource block (RB) parameters, including startCRB (indicating the start of the common RB) and nrofRBs (indicating the number of the RBs being assigned for the subband). Thus, the subband is formed by a set of contiguous RBs within the CC configured as a UE channel. In one embodiment, the configured subband can be anywhere within the frequency band of the CC, including at the edge thereof. In an alternative embodiment, the subband can either be located at the edge of the CC or at the center of the frequency band of the CC. For example, as shown in FIG. 8(A), the frequency bandwidth of the CC is partitioned such that a configured subband 810 is located at the center of the frequency band of the CC, and two complementary subbands 820 are located at the edges of the frequency band. Further, two guardbands 830 are located between the configured subband 810 and the two complementary subbands 820. In certain configurations, the guardbands 830 are specified by an additional configuration parameter nrofGBRBs (indicating the number of the RBs of the guardbands). In one embodiment, the complementary subbands 820 are defined as the set of all remaining contiguous RBs below and above the configured subband 810. In an alternative embodiment, the complementary subbands 820 may be defined as the set of all remaining contiguous RBs below and above the configured subband, leaving out any required guardbands 830 (specified by nrofGBRBs).

As shown in FIG. 8(B), the frequency bandwidth of the CC may also be partitioned to have multiple configured subbands, including two even subbands 850 and an odd subband 860. Each of the subbands 850 and 860 is specified by the RB parameters, including startCRB and nrofRBs.

Referring back to FIG. 7, there are several different ways for the base station 720 to introduce, to the UE 710, the subband TDD configuration specific to the configured subband 810. In one embodiment, the subband TDD configuration in the SIB 730 (e.g., TDD-UL-DLConfigSubbandCommon) can be configured in the same way as TDD-UL-DLConfigCommon, i.e. a number of leading DL slots and symbols and a number of ending UL slots and symbols are specified along with a pattern length. In this case, any slots and symbols left in between are called “flexible” and can be flipped to DL or UL by subsequent UE-dedicated or group common dynamic SFI configurations. Two such patterns can be configured and applied back to back with special constraints on their total duration.

In another embodiment, at operation 750, the base station 720 may send a new UE dedicated subband TDD configuration 750 (e.g., TDD-UL-DLConfigSubbandDedicated) to the UE 710 by RRC signaling, which may leave the DL and UL symbols indicated by TDD-UL-DLConfigSubbandCommon unaltered, and specifies which “flexible” symbols should be flipped to DL or UL. In one embodiment, the dedicated TDD configuration can be configured as a number of leading DL slots and symbols and a number of ending UL slots and symbols are specified with regards to the length of flexible slots and symbols left by TDD-UL-DLConfigSubbandCommon. That is, the format of TDD-UL-DLConfigSubbandDedicated may be in a similar way as the format of TDD-UL-DLConfigDedicated for the CC. In another embodiment, the UE dedicated TDD format is semi-statically configured using slot format combinations based on a standardized SFI table.

In yet another embodiment, at operation 760, the base station 720 may further send a DCI subband TDD configuration in group common DCI_2_0 by dynamic SFI signaling to further refine the subband TDD configuration. In this case, there may be two options for the DCI subband TDD configuration 760. (1) No new field needs to be introduced in DCI_2_0. Specifically, a single index carried by DCI_2_0 and is used to read the slot format combination for the CC from a configured sequence of combinations and the slot format combination for the subband from another configured sequence of combinations. (2) A new field is introduced in DCI_2_0 to carry a separate index for the slot format combination applicable to the subband. In certain configurations, the dynamic SFI signaling of TDD configuration may override the existing TDD configuration(s).

Optionally, at operation 765, the base station 720 may send a separate TDD configuration for UE link direction to the UE 710 in order to indicate to the UE the direction(s) to be selected in each of the partitioned slots. This TDD configuration is dedicated to the UE 720 and may also be signaled through dynamic SFI indication. In certain configurations, there are two options for sending this TDD configuration. (1) The same field in DCI_2_0 may be utilized to provide the index to a sequence configured as a different field of the dedicated SFI configuration. (2) A separate field in DCI_2_0 may be used to provide the index to the dedicated SFI configuration.

Among the subband TDD configurations received at the operations 730, 750 and 760, each TDD configuration may include symbols related to the time slots for the subband. (e.g., the configured subband 810). Further, it should be noted that, although FIG. 7 shows that the UE 710 receives all of the subband TDD configurations received at the operations 730, 750 and 760, it is possible that the UE 710 may receive only one or more of the subband TDD configurations at the operations 730, 750 and 760.

At operation 770, upon receiving the TDD configuration(s), the UE 710 selects the UE link direction in the partitioned time slots by scheduling. Specifically, in determining the outcome of the selection of the UE link direction, the UE 710 relies upon the TDD configuration for UE link direction 765. Alternatively, in one embodiment, the UE may determine the outcome based on certain TDD collision rules applied between any given transmission and reception and only the subband and/or complementary subband it overlaps with. At operation 780, the UE 710 may perform DL reception and/or UL transmission with the base station 720 based on the configuration outcome.

FIG. 9 is a diagram illustrating an example of slot symbols of a half-duplex UE TDD configuration in a SBFD network. Specifically, in the example as shown in FIG. 9, the subbands as shown in FIG. 8(B) are used, including a plurality of even subbands 850 and an odd subband 860. Further, for simplicity, FIG. 9 shows only the slot level configuration and without special slots, and the symbols as shown in FIG. 9 use “U” as an UL symbol and “D” as a DL symbol.

As shown in FIG. 9, the half-duplex UE may be configured with a TDD format for the CC (i.e., the carrier TDD configuration) and a plurality of TDD formats for the configured subbands 850 and 860 (i.e., the subband TDD configurations), and another TDD configuration indicating the UE link direction selected by scheduling (or by a separate configuration) is also provided. Each of the TDD formats for the configured subbands 850 and 860 may be obtained by the UE at the operations 730 (as a subband TDD configuration in the SIB), 750 (as a dedicated subband TDD configuration) or 760 (as a DCI subband TDD configured by group common DCI). For the CC, the TDD patterns of the time slots are configured as D-F-F-F-U, indicating that the three middle slots are flexible. For the configured subbands, the TDD patterns of the time slots for the even subbands are configured as D-D-D-D-U, and the TDD patterns of the time slots for the odd subbands are configured as D-U-U-U-U. The TDD patterns for the UE link direction are configured as D-D-U-U-U. In this case, the outcome of the UE dedicated configurations is shown as D-D-U-U-U based on the TDD configuration indicating the UE link direction. Using the second, third and fourth time slots in the TDD patterns as an example, the even subbands 850 are configured for DL reception, and the odd subband 810 is configured for UL transmission.

In certain configurations, based on the TDD configuration pair applicable to the CC and the subbands as shown in FIG. 9, if a symbol indicated as downlink-downlink or uplink-uplink, the corresponding slot may be treated as non-partitioned. For example, in the first time slot of the TDD patterns as shown in FIG. 9, all the TDD patterns are configured for DL reception, and in the last time slot, all the TDD patterns are configured for UL transmission. Thus, in one embodiment, these time slots may be treated as non-partitioned. Specifically, when the symbol is treated as non-partitioned from the Frequency Domain Resource Assignment (FDRA) point of view, no guardband restriction should be applied on any RBs belonging to the CC.

In one embodiment, transmission and reception is only allowed to overlap with a subband on a symbol indicated as flexible if the transmission or reception is scheduled by DCI. In a further embodiment, unless being signaled otherwise, at least from the FDRA point of view, the symbol is treated as non-partitioned also if one of the following conditions hold: (1) the symbol indicated as flexible-flexible; (2) the symbol is indicated as downlink-flexible or flexible-downlink and DCI schedules reception over the symbol; and (3) the symbol is indicated as uplink-flexible or flexible-uplink and DCI schedules transmission over the symbol.

In an alternative embodiment, transmission and reception is also allowed to overlap with a subband on a symbol indicated as flexible if the transmission or reception is not scheduled by DCI. In a further embodiment, unless being signaled otherwise, at least from the FDRA point of view, the symbol is treated as non-partitioned also if one of the following conditions hold: (1) the symbol indicated as flexible-flexible; (2) the symbol is indicated as downlink-flexible or flexible-downlink and reception is scheduled (semi-statically or dynamically) over the symbol; and (3) the symbol is indicated as uplink-flexible or flexible-uplink and transmission is scheduled (semi-statically or dynamically) over the symbol.

In certain configurations, measurements are not confined within DL-only symbols and DL-subbands. In one embodiment, all measurements (CSI-IM, CSI-RS, UE-UE CLI) may span the entire DL BWP without measurement gap. In one embodiment, only UE-UE CLI measurements are not confined within DL-only symbols and DL-subbands. CSI measurements are always confined within DL-subbands. In one embodiment, only UE-UE CLI and CSI-IM measurements are not confined within DL-only symbols and DL-subbands.

In certain configurations, PRACH occasion mapping and validation is not influenced by any knowledge about the SBFD layout of the network. For example, an additional set of PRACH occasions may be provided to SBFD-aware UEs by the initial UL BWP. In one embodiment, the PRACH occasion belonging to this additional set in a PRACH slot is valid if: (1) it is within UL symbol or an UL subband (where the complementary subband may be flexible or downlink), or if (2) it does not precede an SSB block in the PRACH slot and starts at leas N_gap symbols after a last downlink symbol and at least N_gap symbols after a last SSB symbol, where N_gap is defined by the 3GPP specifications.

In certain configurations, dedicated semi-static TDD configurations through RRC signaling are less flexible then the dynamic TDD configuration allowed by SFI, and only the flexible indication through SFI table can deprioritize semi-static transmission and reception, while the flexible symbols in the dedicated TDD configuration cannot do so. Therefore, monitoring dynamic SFI signaling through group common DCI_2_0 is an essential feature. In certain scenarios when the SFI configuration does not change, it would be more efficient to signal the TDD format through semi-static RRC configuration. Thus, the UE may support semi-static RRC configuration of TDD format through slot format combinations based on a standardized SFI table. In one embodiment, the configuration is introduced in addition to the existing RRC IE TDD-UL-DL-ConfigDedicated, and must not collide with TDD-UL-DL-ConfigDedicated if it is provided. In one embodiment, the relevant rows of the standardized SFI table are enumerated as a value range. In one embodiment, the semi-static configuration can be overridden by dynamic SFI signaling. In one embodiment, transmission or reception over symbols indicated as being flexible using the proposed method is only carried out by the UE if the transmission or reception was scheduled by DCI.

In one embodiment, when the TDD collision rules are applied, certain link direction combinations between the carrier and the subband(s) may be excluded. Specifically, although FIG. 9 shows the symbols in blocks that align with each other in each of the time slots, the actual DL reception and UL transmission may require different expected periods of time, such that the symbols may not perfectly align with each other over time. Thus, collision may occur between any given UL transmission and DL reception in the subband(s) and/or the complementary subband(s) that has an overlap, or in the case where the requirements for a Tx-Rx or Rx-Tx turn around time cannot be met between the UL transmission and DL reception.

In one embodiment, TDD collision rules are applied between any given UL transmission and DL reception, and are applied only between the configured subband and/or complementary subband(s) it overlaps with. In other words. if collision occurs when there is an overlap with only the configured subband, only the TDD format configured for the subband is relevant for the collision, whereas if collision occurs when there is an overlap only with the complementary subband(s), only the TDD format configured for the CC is relevant for the collision. If both the configured subband and the complementary subband(s), both configurations need to be considered for collision.

FIG. 10 is a diagram illustrating examples of collisions between an UL transmission and a DL transmission. Specifically, as discussed, the collision between the UL transmission and the DL reception occurs when there is a time overlap on any symbol, or, in certain configurations, when the requirement of a transmission-reception or reception-transmission turn around time between the UL transmission and the DL reception is not met. As shown in FIG. 10(A), collision occurs when a CG PUSCH, which is a dynamic UL transmission indicated by SFI, has a time overlap with the dynamic PDSCH, which is a dynamic DL reception in a dynamic flexible (F′) symbol indicated by the SFI. It should be noted that the time overlap between the CG PUSCH (dynamic UL transmission) and the dynamic PDSCH (dynamic DL reception) does not have to be a complete overlap for each of the DL reception and/or the UL transmission. As shown in FIG. 10(B), collision also occurs when the requirement of the transmission-reception turn around time is not met between the CG PUSCH and the dynamic PDSCH. According to the current specification, both cases as shown in FIGS. 10(A) and (B) would result in error cases. On the other hand, the UE may introduce a plurality of prioritization rules to support the priority handling in order to determine the priority between the DL reception and the UL transmission. In this case the UE may proceed with the prioritized DL/UL transmission, and the deprioritized Tx/Rx may be cancelled as in current standard [11, TS 38.213]. For example, SRS on non-overlapping symbols is transmitted, and the UE processing timeline for Tx cancellation is expected, allowing partial cancellation capability.

In certain configurations, the UE may introduce the prioritization rules in order to prioritize one of the UL transmission and the DL reception that causes a collision in a time slot. In one embodiment, the collision resolution is treated by separate intra-UE prioritization rules. Examples of the prioritization rules will be introduced in details as follows. Specifically, the UL transmission and/or DL reception may be a dedicated or cell-specific semi-static UL/DL transmission, or a dynamic UL/DL transmission. In certain configurations, examples of the dynamic DL reception may include: DCI scheduling PDSCH (including SIB), or A-CSI-RS; examples of the dynamic UL transmission may include: DCI/RAR scheduling PUSCH, PUCCH:HARQ (including Msg4/MsgB HARQ), A-CSI, A-SRS, and Ordered-PRACH triggered by DCI; examples of dedicated semi-static DL reception may include: PDCCH in USS, SPS PDSCH, P/SP-CSI-RS, PRS (without a measuring gap); examples of dedicated semi-static UL transmission may include: CG-PUSCH, PUCCH:P/SP-CSI, SR, HARQ; examples of cell-specific semi-static DL reception may include: SSB or PDCCH in Type0/0A/1/2 CSS; and examples of cell-specific semi-static UL transmission may include: valid PRACH occasion, and MsgA PUSCH.

As discussed above, the introduction of the prioritization rules may solve the issue of lack of prioritization of dynamic scheduling between the TDD patterns. For example, in the scenario where the DCI schedules Tx/Rx over a F′ symbol collides with a semi-static Rx/Tx, response, such as the case as shown in FIG. 10(A), or in the scenario where back-to-back scheduling leaves no time for Rx-Tx turn-around, e.g., the case as shown in FIG. 10(B), the prioritization rules may solve the collision issues.

Further, it should be noted that the SSB arbitration (which is a cell-specific semi-static DL reception) must take into account that it is essential for synchronization. For example, in the case where PUSCH/PUCCH scheduled by DCI collides with SSB, the SSB may be prioritized. FIG. 10(C) shows a collision between the dynamic PUSCH (i.e., a dynamic UL transmission indicated by SFI) and the SSB (i.e., a cell-specific semi-static DL reception which may be flexible or non-provided). As a consequence, SSB is usually prioritized over the dynamic PUSCH or other UL transmissions, except when the prioritization is left to the UE implementation, as in the collision case with valid PRACH occasion.

FIG. 11 is a diagram illustrating the priority rule related to a cell-specific semi-static UL transmission and a dynamic DL reception. Specifically, in the priority rule 1100, when a dynamic DL reception, e.g., a PDSCH or CSI-RS scheduled by the DCI, collides with a cell-specific semi-static UL transmission, such as a valid PRACH occasion (including any guard intervals that precedes it according to the specification) or a MsgA PUSCH on any symbol (e.g., semi-static UL or flexible), as shown in FIG. 11(A), or if Tx-Rx or Rx-Tx turn around time between the UL/DL transmissions cannot be met, as shown in FIG. 11(B), then it is up to UE implementation whether the UE prioritize the PRACH transmission or the downlink reception. However, when the dynamic DL reception is a PDSCH reception with repetitions and the UE implementation rule indicates prioritizing the UL transmission (i.e., the PDSCH repetitions is deprioritized), the UE may allow the PDSCH repetitions to continue in the time slot.

FIG. 12 is a diagram illustrating the priority rule related to a dynamic UL transmission and a cell-specific semi-static DL reception. Specifically, in the priority rule 1200, when a dynamic UL transmission, such as PUSCH, PUCCH, SRS or PRACH scheduled by DCI, collides with a cell-specific semi-static DL reception, such as a PDCCH reception in Type0/0A/1/2 CSS on any symbol (e.g., semi-static DL or flexible), as shown in FIG. 12(A), or if the Tx-Rx or Rx-Tx turn around time between the dynamic UL transmission and the cell-specific semi-static DL reception cannot be met, as shown in FIG. 12(B), the UE may prioritize the dynamic UL transmission scheduled by DCI.

FIG. 13 is a diagram illustrating the priority rule related to a dynamic DL reception and a dedicated semi-static UL transmission, and FIG. 14 is a diagram illustrating the priority rule related to a dedicated semi-static DL reception and a dynamic UL transmission. Specifically, in the priority rules 1300 and 1400, when a dynamic UL transmission (e.g., DCI/RAR scheduling PUSCH, PUCCH:HARQ (including Msg4/MsgB HARQ), A-CSI, A-SRS, Ordered-PRACH triggered by DCI) collides with a dedicated semi-static DL reception (e.g., PDCCH in USS, SPS PDSCH, P/SP-CSI-RS, PRS) configured by higher layer on any symbol (semi-static DL or flexible), as shown in FIG. 13(A), or when a dynamic DL reception (e.g., DCI scheduling PDSCH, A-CSI-RS) scheduled by DCI collides with a dedicated semi-static UL transmission (e.g., CG PUSCH, PUCCH, P/SP-CSI, SR, HARQ) configured by higher layer on any symbol (semi-static UL or flexible), as shown in FIG. 14(A), or if Tx-Rx or Rx-Tx turn around time cannot be met between them, as shown in FIG. 13(B) and FIG. 14(B) the UE may prioritize the dynamic UL transmission or the dynamic DL reception scheduled by DCI over the dedicated semi-static DL reception or the dedicated semi-static UL transmission, respectively.

FIG. 15 is a diagram illustrating the priority rule related to a dynamic UL transmission and a dynamic DL reception. Specifically, in the priority rule 1500, when a dynamic UL transmission, such as the PUSCH, PUCCH transmission scheduled by DCI, collides with a dynamic DL reception, such as a PDSCH transmission scheduled by DCI on any symbol (DL or flexible), as shown in FIG. 15(A), or if Tx-Rx or Rx-Tx turn around time between the dynamic UL/DL transmissions cannot be met, as shown in FIG. 15(B), the UE may determine the prioritization based on the priority of the dynamic UL/DL transmissions. For example, one of the dynamic UL transmission and a dynamic DL reception may be assigned with a high priority, and the other has a low priority. In this case, the UE may prioritize the dynamic UL transmission/DL reception with the higher priority. On the other hand, if both the dynamic UL transmission/DL reception are assigned with the same priorities, the UE may determine that an error case has occurred.

It should be noted that, in certain configurations, if traffic priority is not used in the prioritization, the priority rule 1500 may be dropped, and the priority rules 1100, 1200, 1300 and 1400 may be restricted to the collision cases where there is a time overlap, e.g., cases as shown in FIGS. 11(A), 12(A), 13(A) and 14(A), and the turn around time collision cases, e.g., cases as shown in FIGS. 11(B), 12(B), 13(B) and 14(B), are excluded. This is due to the rationale that, if latency is not an issue, prioritization can be achieved by the time overlap cases more economically.

FIG. 16 is a diagram illustrating the priority rule related to a cell-specific semi-static UL transmission and a dedicated or cell-specific semi-static DL reception. Specifically, in the priority rule 1600, when a cell-specific semi-static UL transmission, such as a valid PRACH occasion (including any guard intervals that precedes it according to the specification) or a MsgA PUSCH, collides with a dedicated or cell specific semi-static DL reception (including SSB) scheduled by semi-static configuration on any symbol, as shown in FIG. 16(A), then it is up to UE implementation whether the UE prioritize the cell-specific semi-static UL transmission (e.g., PRACH or MsgA PUSCH) or the dedicated or cell-specific semi-static DL reception. Specifically, if the UE wants to transmit PRACH in a contention-based operation mode, the PRACH should have a higher priority than any other DL reception except for SSB reception, which may possibly be indispensable for synchronization. However, prioritizing all valid PRACH occasions would be inefficient when the UE does not have a need to send PRACH. Therefore, prioritization between the valid PRACH occasion and the dedicated or cell-specific DL reception should be up to the UE implementation concern and exclude the case of order PRACH triggered by DCI, which is a dynamic scheduling case. In this case, the base station (i.e., gNB) does not need to know which action the UE takes, as the base station will try to decode the valid PRACH occasion concurrently with the downlink transmission to the UE (or to any other UE). That is, the UL/DL concurrency is a given for the gNB.

In one embodiment, when the priority rule 1600 is applied, the collision is detected and prioritization is carried out according to the same rule (i.e. prioritizing one or the other according to UE implementation) if scheduling does not leave sufficient headroom for the Tx-Rx or Rx-Tx turn around of the UE in addition to any other gap that is necessary according to current standard, as shown in FIG. 16(B).

FIG. 17 is a diagram illustrating the priority rule related to a dedicated semi-static UL transmission and a cell-specific semi-static DL reception. Specifically, in the priority rule 1700, when a dedicated semi-static UL transmission collides with a cell-specific semi-static DL reception (e.g., PDCCH in Type0/0A/1/2 on CSS on any symbol), as shown in FIG. 17(A), or if Tx-Rx or Rx-Tx turn around time between the UL/DL transmission cannot be met, as shown in FIG. 17(B), the UE may prioritize the cell-specific semi-static DL reception (e.g., PDCCH) and cancel the dedicated semi-static UL transmission. In one embodiment, however, an exception may be applied when the dedicated semi-static UL transmission is assigned with a higher priority than the cell-specific semi-static DL reception. In this case, the UE may prioritize the dedicated semi-static UL transmission with the higher priority over the cell-specific semi-static DL reception.

FIG. 18 is a diagram illustrating the priority rule related to a dedicated semi-static UL transmission and a dedicated semi-static DL reception. Specifically, in the priority rule 1800, when a dedicated semi-static UL transmission collides with a dedicated semi-static DL reception on any symbol, as shown in FIG. 18(A), or if Tx-Rx or Rx-Tx turn around time cannot be met between the dedicated UL/DL transmissions, as shown in FIG. 18(B), the UE may determine the prioritization based on the priority of the dedicated semi-static UL/DL transmissions. For example, one of the dedicated semi-static UL transmission and the dedicated semi-static DL reception may be assigned with a high priority, and the other has a low priority. In this case, the UE may prioritize the dedicated semi-static UL transmission/DL reception with the higher priority. On the other hand, if both the dedicated semi-static UL transmission/DL reception are assigned with the same priorities, the UE may determine that an error case has occurred.

FIG. 19 is a flow chart of a method (process) for wireless communication of a UE. The method may be performed by a UE (e.g., the UE 710). At operation 1910, the UE receives, from a base station, a carrier TDD configuration of time slots and symbols for a CC. At operation 1920, the UE receives, from the base station, one or more subband TDD configurations specific to a subband for the CC. At operation 1930, the UE determines, according to the carrier TDD configuration and the subband TDD configurations, whether a collision exists between an UL transmission and a DL reception for each of the time slots and the symbols. At operation 1940, the UE selects one of the UL transmission and the DL reception for one of more of the time slots and the symbols with the collision based on a UE-specific link direction configuration or a plurality of priority rules.

In certain embodiments, the UE is configured to receive the one or more subband TDD configurations by: receiving, from the base station, a SIB including a common subband TDD configuration; receiving, from the base station, a dedicated subband TDD configuration by RRC signaling; or receiving, from the base station, a Downlink Control Information (DCI) subband TDD configuration by dynamic SFI signaling.

In certain embodiments, in response to both the carrier TDD configuration and the subband TDD configurations indicating one of the time slots or the symbols as the DL reception or the UL transmission, the UE treats the one of the time slots or the symbols as being non-partitioned.

In certain embodiments, each of the one or more subband TDD configurations is a dedicated TDD configuration, a cell-specific TDD configuration, or a dynamic TDD configuration indicated by a SFI table.

In certain embodiments, measurements are not confined within the DL reception on the CC and DL reception on the subband.

In certain embodiments, the collision is determined to exist between the UL transmission and the DL reception when: a time overlap exists between the UL transmission and the DL reception; or a requirement of a transmission-reception or reception-transmission turn around time between the UL transmission and the DL reception is not met.

It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

METHODS FOR INTRA-UE UL-DL COLLISION HANDLING IN SINGLE CC UE CONFIGURATION IN GNB-ONLY SUBBAND FULL-DUPLEX (SBFD) NETWORK

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATION(S)

Provisional Applications (1)