TDD uplink configuration in downlink fragmented ca using single lo

Abstract

In a system, apparatus, method, and non-transitory computer readable medium for enabling time division duplex (TDD) configuration in downlink (DL) fragmented carrier aggregation (CA) using a single local oscillator (LO), a first apparatus may be caused to, transmit first apparatus capability information to a second apparatus, the first apparatus capability information including local oscillator (LO) frequency placement corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA), and perform time duplex division (TDD) uplink (UL) transmission using at least one carrier component of an NCIB CA connection established with a second apparatus based on the LO frequency placement.

Description

[0001] TDD UPLINK CONFIGURATION IN DOWNLINK FRAGMENTED CA USING SINGLE LO

[0002] BACKGROUND

[0003] Field

[0004] [1] Various example embodiments relate to methods, apparatuses, systems, and / or non-transitory computer readable media for enabling time division duplex (TDD) configuration in downlink (DL) fragmented carrier aggregation (CA) using a single local oscillator (LO).

[0005] Description of the Related Art

[0006] [2] A 5thgeneration mobile network (5G) standard, referred to as 5G New Radio (NR), is being developed to provide higher capacity, higher reliability, and lower latency communications than the 4G long term evolution (LTE) standard.

[0007] [3] The 5G NR standard provides user equipment (UE) devices (hereinafter referred to as UE devices or UEs) with the ability to perform carrier aggregation (CA) using fragmented carriers, which is non-contiguous (NC) intra-band CA, but received at the UE using less receiver chains than for typical non-contiguous intra-band CA reception. The UE devices are assigned fragmented and / or non-contiguous carrier component (CC) pairs by a network and may use a single LO for downlink (DL) reception of the two component carriers, while the uplink (UL) transmissions may use a separate LO for the UL transmissions or the same LO as the DL transmissions. If there is uplink on more than one of the fragmented carriers, the UE devices may use even more LO’s if not able to use the same shared LO, used by the fragmented carrier pair.

[0008] SUMMARY

[0009] [4] At least one example embodiment relates to a first apparatus.

[0010] [5] In at least one example embodiment, the first apparatus may include a memory storing computer readable instructions, and processing circuitry configured to execute the computer readable instructions to cause the first apparatus to, transmit first apparatus capability information to a second apparatus, the first apparatus capability information including local oscillator (LO) frequency placement corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA), and perform time duplex division (TDD) uplink (UL) transmission using at least one carrier component of an NCIB CA connection established with a second apparatus based on the LO frequency placement.

[0011] [6] Some example embodiments provide that the first apparatus capability information includes at least one of: a number of LOs supported by the first apparatus, resource block (RB) preference information associated with the at least one LO, preference for uplink RB placement closest to the LOs frequency placement, or any combinations thereof.

[0012] [7] Some example embodiments provide that the first apparatus is further caused to, receive connection configuration information from the second apparatus, the connection configuration information indicating parameters for the NCIB CA connection in a TDD band of operation and a selection of a number of LOs to be used for the NCIB CA connection.

[0013] [8] Some example embodiments provide that the parameters for the NCIB CA connection include indication of at least two NCIB carrier components for use in a downlink (DL) NCIB CA connection and the UL RB allocation preference of the first apparatus corresponding to a UL response on one DL carrier component of the at least two NCIB carrier components also having UL allocations.

[0014] [9] Some example embodiments provide that the first apparatus is further caused to, determine the selected number of LOs and the LO frequency placement based on the indication of the at least two NCIB carrier components, and determine first apparatus extended capability information associated with the NCIB CA connection.

[0015]

[0010] Some example embodiments provide that the first apparatus is further caused to, transmit first apparatus assistance information to the second apparatus in response to the connection configuration information, the first apparatus assistance information including the determined selected number of LOs and the LO frequency placement, and perform the TDD UL transmission based on the determined selected number of LOs and the LO frequency placement.

[0016]

[0011] Some example embodiments provide that the connection configuration information indicates the selection of a single LO to be used for the NCIB CA connection and the UL transmission, and the first apparatus is further caused to, perform the TDD UL transmission, complying to the UL RB allocation preference, with the second apparatus based on the single LO, and receive downlink (DL) data from the second apparatus based on the single LO.

[0017]

[0012] Some example embodiments provide that the connection configuration information indicates the selection of a first LO to be used for TDD UL transmissions and a second LO to be used for TDD DL transmissions on the NCIB CA connection, and the first apparatus is further caused to, perform the TDD UL transmission with the second apparatus using the one carrier component of the NCIB CA connection based on the first LO, and perform TDD DL reception with the second apparatus using every carrier component of the NCIB CA connection based on the second LO.

[0018]

[0013] At least one example embodiment relates to a first apparatus.

[0019]

[0014] In at least one example embodiment, the first apparatus may include a memory storing computer readable instructions, and processing circuitry configured to execute the computer readable instructions to cause the first apparatus to, receive second apparatus capability information from a second apparatus, the second apparatus capability information including local oscillator (LO) configuration of the second apparatus corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA), and receive time duplex division (TDD) uplink (UL) transmission from the second apparatus using at least one carrier component of an NCIB CA connection established with the second apparatus based on the LO configuration.

[0020]

[0015] Some example embodiments provide that the LO configuration includes at least one of: a number of LOs supported by the second apparatus, resource block (RB) preference information associated with the at least one LO, preference for uplink RB placement closest to a LOs frequency placement of the second apparatus, or any combinations thereof.

[0021]

[0016] Some example embodiments provide that the first apparatus is further caused to, determine connection configuration information based on the LO configuration, the connection configuration information indicating parameters for the NCIB CA connection in a TDD band of operation and a selection of a number of LOs to be used for the NCIB CA connection, and transmit the connection configuration information to the second apparatus.

[0022]

[0017] Some example embodiments provide that the parameters for the NCIB CA connection include indication of at least two NCIB carrier components for use in a downlink (DL) NCIB CA connection and the UL RB allocation preference of the second apparatus corresponding to a UL response on one DL carrier component of the at least two NCIB carrier components also having UL allocations.

[0023]

[0018] Some example embodiments provide that the first apparatus is further caused to, determine at least two NCIB carrier components for use in the NCIB CA connection, and determine the number of LOs to be used for the NCIB CA connection based on a carrier bandwidth associated with the at least two NCIB carrier components, a maximum power reduction (MPR) level associated with the carrier bandwidth, and an additional maximum power reduction (A-MPR) level associated with the carrier bandwidth.

[0024]

[0019] Some example embodiments provide that the first apparatus is further caused to, determine whether a single LO or two LOs is to be used for the NCIB CA connection based on a distance between closest edges of the at least two NCIB carrier components to a center of the carrier bandwidth and a distance threshold.

[0025]

[0020] Some example embodiments provide that the first apparatus is further caused to, determine a UL RB allocation of the second apparatus in one NCIB carrier component of the at least two NCIB carrier components based on the UL RB preference information associated with the at least one LO and distances between the at least two NCIB carrier components and a center of the carrier bandwidth.

[0026]

[0021] Some example embodiments provide that the first apparatus is further caused to, receive second apparatus assistance information from the second apparatus in response to the connection configuration information, the second apparatus assistance information including indication of a selected number of LOs and a determined LO frequency placement, and receive the TDD UL transmission based on the selected number of LOs and the determined LO frequency placement.

[0027]

[0022] At least one example embodiment relates to a method of operating a first apparatus.

[0028]

[0023] In at least one example embodiment, the method may include, transmitting first apparatus capability information to a second apparatus, the first apparatus capability information including local oscillator (LO) frequency placement corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA), and performing time duplex division (TDD) uplink (UL) transmission using at least one carrier component of an NCIB CA connection established with a second apparatus based on the LO frequency placement.

[0024] Some example embodiments provide that the first apparatus capability information includes at least one of a number of LOs supported by the first apparatus, resource block (RB) preference information associated with the at least one LO, preference for uplink RB placement closest to the LOs frequency placement, or any combinations thereof.

[0029]

[0025] Some example embodiments provide that the method may further include receiving connection configuration information from the second apparatus, the connection configuration information indicating parameters for the NCIB CA connection in a TDD band of operation and a selection of a number of LOs to be used for the NCIB CA connection.

[0030]

[0026] Some example embodiments provide that the parameters for the NCIB CA connection include indication of at least two NCIB carrier components for use in a downlink (DL) NCIB CA connection and the UL RB allocation preference of the first apparatus corresponding to a UL response on one DL carrier component of the at least two NCIB carrier components also having UL allocations, and the method may further include determining the selected number of LOs and the LO frequency placement based on the indication of the at least two NCIB carrier components, determining first apparatus extended capability information associated with the NCIB CA connection, transmitting first apparatus assistance information to the second apparatus in response to the connection configuration information, the first apparatus assistance information including the determined selected number of LOs and the LO frequency placement, and performing the TDD UL transmission based on the determined selected number of LOs and the LO frequency placement.

[0031]

[0027] At least one example embodiment relates to a first apparatus.

[0032]

[0028] In at least one example embodiment, the first apparatus may include means for transmitting first apparatus capability information to a second apparatus, the first apparatus capability information including local oscillator (LO) frequency placement corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA), and performing time duplex division (TDD) uplink (UL) transmission using at least one carrier component of an NCIB CA connection established with a second apparatus based on the LO frequency placement.

[0033]

[0029] Some example embodiments provide that the first apparatus capability information includes at least one of a number of LOs supported by the first apparatus, resource block (RB) preference information associated with the at least one LO, preference for uplink RB placement closest to the LOs frequency placement, or any combinations thereof.

[0034]

[0030] Some example embodiments provide that the first apparatus further includes means for, receiving connection configuration information from the second apparatus, the connection configuration information indicating parameters for the NCIB CA connection in a TDD band of operation and a selection of a number of LOs to be used for the NCIB CA connection.

[0035]

[0031] Some example embodiments provide that the parameters for the NCIB CA connection include indication of at least two NCIB carrier components for use in a downlink (DL) NCIB CA connection and the UL RB allocation preference of the first apparatus corresponding to a UL response on one DL carrier component of the at least two NCIB carrier components also having UL allocations.

[0036]

[0032] Some example embodiments provide that the first apparatus further includes means for, determining the selected number of LOs and the LO frequency placement based on the indication of the at least two NCIB carrier components, and determining first apparatus extended capability information associated with the NCIB CA connection.

[0037]

[0033] Some example embodiments provide that the first apparatus further includes means for, transmitting first apparatus assistance information to the second apparatus in response to the connection configuration information, the first apparatus assistance information including the determined selected number of LOs and the LO frequency placement, and performing the TDD UL transmission based on the determined selected number of LOs and the LO frequency placement.

[0038]

[0034] Some example embodiments provide that the connection configuration information indicates the selection of a single LO to be used for the NCIB CA connection and the UL transmission, and the first apparatus further includes means for, performing the TDD UL transmission, complying to the UL RB allocation preference, with the second apparatus based on the single LO, and receiving downlink (DL) data from the second apparatus based on the single LO.

[0039]

[0035] Some example embodiments provide that the connection configuration information indicates the selection of a first LO to be used for TDD UL transmissions and a second LO to be used for TDD DL transmissions on the NCIB CA connection, and the first apparatus further includes means for, performing the TDD UL transmission with the second apparatus using the one carrier component of the NCIB CA connection based on the first LO, and performing TDD DL reception with the second apparatus using every carrier component of the NCIB CA connection based on the second LO.

[0040]

[0036] At least one example embodiment relates to a first apparatus.

[0041]

[0037] In at least one example embodiment, the first apparatus may include means for, receiving second apparatus capability information from a second apparatus, the second apparatus capability information including local oscillator (LO) configuration of the second apparatus corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA), and receiving time duplex division (TDD) uplink (UL) transmission from the second apparatus using at least one carrier component of an NCIB CA connection established with the second apparatus based on the LO configuration.

[0042]

[0038] Some example embodiments provide that the LO configuration includes at least one of: a number of LOs supported by the second apparatus, resource block (RB) preference information associated with the at least one LO, preference for uplink RB placement closest to a LOs frequency placement of the second apparatus, or any combinations thereof.

[0043]

[0039] Some example embodiments provide that the first apparatus further includes means for, determining connection configuration information based on the LO configuration, the connection configuration information indicating parameters for the NCIB CA connection in a TDD band of operation and a selection of a number of LOs to be used for the NCIB CA connection, and transmitting the connection configuration information to the second apparatus.

[0044]

[0040] Some example embodiments provide that the parameters for the NCIB CA connection include indication of at least two NCIB carrier components for use in a downlink (DL) NCIB CA connection and the UL RB allocation preference of the second apparatus corresponding to a UL response on one DL carrier component of the at least two NCIB carrier components also having UL allocations.

[0045]

[0041] Some example embodiments provide that the first apparatus further includes means for, determining at least two NCIB carrier components for use in the NCIB CA connection, and determining the number of LOs to be used for the NCIB CA connection based on a carrier bandwidth associated with the at least two NCIB carrier components, a maximum power reduction (MPR) level associated with the carrier bandwidth, and an additional maximum power reduction (A-MPR) level associated with the carrier bandwidth.

[0046]

[0042] Some example embodiments provide that the first apparatus further includes means for, determining whether a single LO or two LOs is to be used for the NCIB CA connection based on a distance between closest edges of the at least two NCIB carrier components to a center of the carrier bandwidth and a distance threshold.

[0047]

[0043] Some example embodiments provide that the first apparatus further includes means for, determining a UL RB allocation of the second apparatus in one NCIB carrier component of the at least two NCIB carrier components based on the UL RB preference information associated with the at least one LO and distances between the at least two NCIB carrier components and a center of the carrier bandwidth.

[0048]

[0044] Some example embodiments provide that the first apparatus further includes means for, receiving second apparatus assistance information from the second apparatus in response to the connection configuration information, the second apparatus assistance information including indication of a selected number of LOs and a determined LO frequency placement, and receiving the TDD UL transmission based on the selected number of LOs and the determined LO frequency placement.

[0049] BRIEF DESCRIPTION OF THE DRAWINGS

[0050]

[0045] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate one or more example embodiments and, together with the description, explain these example embodiments. In the drawings:

[0051]

[0046] FIG. 1A illustrates a wireless communication system according to at least one example embodiment;

[0052]

[0047] FIG. IB illustrates an example of fragmented carriers in different frequency bands;

[0053]

[0048] FIGS. 1C to ID illustrate examples of Additional Maximum Power Reduction (A- MPR) and MPR effects on fragmented CA;

[0054]

[0049] FIGS. IE to IF illustrate examples of LO settings according to the related art;

[0055]

[0050] FIG. 2 illustrates a block diagram of an example RAN node according to at least one example embodiment;

[0056]

[0051] FIG. 3 illustrates a block diagram of an example UE device according to at least one example embodiment;

[0052] FIG. 4 illustrates an example flowchart for performing TDD configuration in DL fragmented CA according to some example embodiments; and

[0057]

[0053] FIGS. 5 A to 5D illustrate four example LO configurations according to some example embodiments.

[0058] DETAILED DESCRIPTION

[0059]

[0054] Various example embodiments will now be described more fully with reference to the accompanying drawings in which some example embodiments are shown.

[0060]

[0055] Detailed example embodiments are disclosed herein. However, specific structural and functional details disclosed herein are merely representative for purposes of describing the example embodiments. The example embodiments may, however, be embodied in many alternate forms and should not be construed as limited to only the example embodiments set forth herein.

[0061]

[0056] It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the example embodiments. As used herein, the term “and / or,” includes any and all combinations of one or more of the associated listed items.

[0062]

[0057] It will be understood that when an element is referred to as being “connected,” or “coupled,” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected,” or “directly coupled,” to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between,” versus “directly between,” “adjacent,” versus “directly adjacent,” etc.).

[0063]

[0058] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the example embodiments. As used herein, the singular forms “a,” “an,” and “the,” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and / or “including,” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0064]

[0059] It should also be noted that in some alternative implementations, the functions / acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functionality / acts involved.

[0065]

[0060] Specific details are provided in the following description to provide a thorough understanding of the example embodiments. However, it will be understood by one of ordinary skill in the art that example embodiments may be practiced without these specific details. For example, systems may be shown in block diagrams in order not to obscure the example embodiments in unnecessary detail. In other instances, well-known processes, structures and techniques may be shown without unnecessary detail in order to avoid obscuring example embodiments.

[0066]

[0061] Also, it is noted that example embodiments may be described as a process depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. A process may be terminated when its operations are completed, but may also have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

[0067]

[0062] Moreover, as disclosed herein, the term “memory” may represent one or more devices for storing data, including random access memory (RAM), magnetic RAM, core memory, and / or other machine readable mediums for storing information. The term “storage medium” may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and / or other machine readable mediums for storing information. The term “computer-readable medium” may include, but is not limited to, portable or fixed storage devices, optical storage devices, wireless channels, and various other mediums capable of storing, containing or carrying instruction(s) and / or data.

[0063] Furthermore, example embodiments may be implemented by hardware circuitry and / or software, firmware, middleware, microcode, hardware description languages, etc., in combination with hardware (e.g., software executed by hardware, etc.). When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the desired tasks may be stored in a machine or computer readable medium such as a non-transitory computer storage medium, and loaded onto one or more processors to perform the desired tasks.

[0068]

[0064] A code segment may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0069]

[0065] As used in this application, the term “circuitry” and / or “hardware circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementation (such as implementations in only analog and / or digital circuitry); (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware, and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and (c) hardware circuit(s) and / or processor(s), such as microprocessor s) or a portion of a microprocessor s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. For example, the circuitry more specifically may include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, application-specific integrated circuit (ASIC), etc.

[0070]

[0066] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0071]

[0067] While the various example embodiments of the present disclosure are discussed in connection with the 5G wireless communication standard for the sake of clarity and convenience, the example embodiments are not limited thereto, and one of ordinary skill in the art would recognize the example embodiments may be applicable to other wireless communication standards, such as the 4G standard, a Wi-Fi standard, a future 6G standard, a future 7G standard, etc.

[0072]

[0068] Various example embodiments are directed towards enabling TDD configuration in DL fragmented CA using a single LO. More specifically, one or more example embodiments reduce the unwanted UL transmission emissions and / or reduce the near-far problem associated with fragmented CA and / or NCIB CA due to the usage of inefficient and / or suboptimal LOs and / or resource blocks (RBs). Additionally, at least one example embodiment may provide increased and / or improved UL transmission power and / or increased resource efficiency by decreasing the levels of Maximum Power Reduction (MPR) and / or Additional MPR (A-MPR) applied to a UE device’s UL transmissions caused by suboptimal LO configuration and / or suboptimal RB allocation.

[0073]

[0069] FIG. 1A illustrates a wireless communication system according to at least one example embodiment. FIG. IB illustrates an example of fragmented carriers in different frequency bands. FIGS. 1C to ID illustrate examples of Additional Maximum Power Reduction (A-MPR) and MPR effects on fragmented CA. FIGS. IE to IF illustrate examples of LO settings according to the related art.

[0074]

[0070] Referring now to FIG. 1A, a wireless communication system includes a core network 100, a Data Network 105, a first radio access network (RAN) node 110, a second RAN node 140, a first user equipment device (e.g., UE device or UE, etc.) 120, and / or a second UE device 130, etc., but the example embodiments are not limited thereto and e.g., the example embodiments may include a greater or lesser number of constituent elements. For example, the wireless communication system may include three or more RAN nodes, one UE device, or three or more UE devices, additional base stations, servers, routers, access points, gateways, etc.

[0071] The RAN node 110, the UE device 120, and / or the UE device 130 may be connected over a first wireless network, such as a cellular wireless access network (e.g., a 3G wireless access network, a 4G-Long Term Evolution (LTE) network, a 5G-New Radio (e.g., 5G) wireless network, a 6G wireless network, a WiFi network, etc.). The first wireless network may include the core network 100 and / or the Data Network 105. The RAN node 110 may connect to other RAN nodes (not shown), as well as to the core network 100 and / or the Data Network 105, over a wired and / or wireless network. The core network 100 and the Data Network 105 may connect to each other over a wired and / or wireless network. The Data Network 105 may refer to the Internet, an intranet, a wide area network, etc. Additionally, the RAN node 140 may belong to a second wireless network.

[0075]

[0072] According to some example embodiments, the RAN node 110 may act as a relay node (e.g., an integrated access and backhaul (IAB) node) and may communicate with the UE devices 120 and / or 130, etc., in combination with at least one base station (and / or access point (AP), router, etc.) (not shown) of the same or a different radio access technology (e.g., WiFi, etc.).

[0076]

[0073] The UE devices 120 and / or 130 may be any one of, but not limited to, a mobile device, a smartphone, a tablet, a laptop computer, a wearable device, an Internet of Things (loT) device, a sensor (e.g., thermometers, humidity sensors, pressure sensors, motion sensors, accelerometers, etc.), actuators, robotic devices, robotics, drones, connected medical devices, eHealth devices, smart city related devices, a security camera, autonomous devices (e.g., autonomous cars, etc.), a desktop computer and / or any other type of stationary or portable device capable of operating according to, for example, the 5G NR communication standard, and / or other wireless communication standard(s). The UE devices 120 and / or 130 may be configurable to transmit and / or receive data in accordance to strict latency, reliability, and / or accuracy requirements, such as URLLC communications, TSC communications, etc., but the example embodiments are not limited thereto.

[0077]

[0074] The wireless communication system further includes a plurality of TRPs (e.g., a base station, a wireless access point, etc.), such as RAN nodes 110, 140, etc. The RAN nodes 110, 140, etc., may operate according to an underlying cellular and / or wireless radio access technology (RAT), such as 5G NR, LTE, Wi-Fi, etc. For example, the RAN nodes 110, 140, etc., may be a 5G gNB node, a LTE eNB node, or a LTE ng-eNB node, etc., but the example embodiments are not limited thereto. The RAN nodes 110, 140, etc. may provide wireless network services to one or more UE devices within one or more cells (e.g., cell service areas, broadcast areas, serving areas, coverage areas, etc.) surrounding the respective physical location of the RAN node.

[0078]

[0075] For example, the RAN nodes 110, 140, etc. may be configured to operate in a multi-user (MU) multiple input multiple out (MIMO) mode and / or a massive MIMO (mMIMO) mode, wherein the RAN nodes 110, 140, etc. transmit a plurality of beams (e.g., radio channels, datastreams, streams, etc.) in different spatial domains and / or frequency domains using a plurality of antennas (e.g., antenna panels, antenna elements, an antenna array, etc.) and beamforming and / or beamsteering techniques. For example, as shown in FIG. 1A, the RAN nodes 110 and 140 may each transmit and / or receive transmissions using two or more beams, but the example embodiments are not limited thereto, and for example, one or more of the RAN nodes may include a greater or lesser number of beams, etc.

[0079]

[0076] According to at least one example embodiment, the UE devices 120, 130, etc., may include multiple antenna panels (e.g., may be a multi-panel UE device, etc.), and may transmit and / or receive to a plurality of RAN nodes (e.g., TRPs), such as the RAN node 110, etc., using the same time-frequency resources and / or using resources overlapping in time, but the example embodiments are not limited thereto.

[0080]

[0077] According to at least one example embodiment, the RAN nodes 110, 120, etc., may be connected to at least one core network element (not shown) residing on the core network 100, such as a core network device, a core network server, access points, switches, routers, nodes, etc., but the example embodiments are not limited thereto. The core network 100 may provide network functions, such as an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a unified data management (UDM), a user plane function (UPF), an authentication server function (AUSF), an application function (AF), and / or a network slice selection function (NSSF), etc., and / or equivalent functions, but the example embodiments are not limited thereto.

[0081]

[0078] According to some example embodiments, the RAN node 110 (e.g., the first wireless network) and the RAN node 140 (e.g., the second wireless network) may operate within different frequency segments, e.g., non-contiguous and / or fragmented segments, of the same radio spectrum. For example, as shown in FIG. IB, the frequency spectrum of band n25 in Toronto is shared by two different wireless operators with both operators having non-contiguous subsets of the n25 frequency spectrum. For the frequency spectrum of band n7 in Toronto, there are three different wireless operators having noncontiguous subsets of the n7 frequency spectrum. Additionally, for the frequency spectrum of band n66 in Toronto, four different wireless operators have non-contiguous subsets of the n66 frequency spectrum.

[0082]

[0079] However, as shown in FIGS. 1C to ID, when UE devices, such as the UE devices 120, 130, etc., operate on a radio spectrum which is shared by multiple operators, there may be undesirable emissions problems caused by the sharing of the radio spectrum. More specifically, FIG. 1C illustrates two examples of an output spectrum of an UL in band nl, with the center frequency of the UL (e.g., the LO frequency) further from the allocated spectrum for the UL and closer to the allocated spectrum for the UL. FIG. ID shows two graphs illustrating the relation between RB allocation and the level and / or amount of MPR required to reduce in-band distortion (EVM), wherein the X-axes correspond to the placement of RBs and the Y-axes correspond to the number of RBs.

[0083]

[0080] For example, as shown in FIG. 1C, a power amplifier of the UE devices 120, 130, etc., may create intermodulation distortion (IMD), especially when the active subcarriers for the UE device’s TDD UL transmission is located far from the center frequency, also referred to as the LO frequency, of the UL channel. As shown in FIG. 1C, the IMD product may interfere with the radio resources of a “victim network,” which may be the radio spectrum of a different network operator, a protected radio spectrum (e.g., radio spectrum reserved for satellite communication, public service and / or governmental use, military use, etc.), but the example embodiments are not limited thereto. In order to decrease unwanted IMD and / or EVM, the core network 100 and / or the RAN node 110 may issue instructions to the UE devices 120, 130, etc., to apply MPR and / or A-MPR reductions in the transmission power of the UE devices 120, 130, etc. However, because the application of MPR and / or A-MPR settings on the TX power of the UE devices 120 and / or 130 result in the reduction of its maximum output power, it is desirable to reduce the unwanted IMD and / or EVM onto adjacent frequency regions without the application of MPR and / or A-MPR settings.

[0084]

[0081] As shown in FIG. 1C and ID, reduction in IMD on adjacent frequency regions may be achieved by selecting RBs placed closer to the LO frequency of the UL transmission. For example, in FIG. 1C, when the “wanted signal,” e.g., the RBs for the UL transmission of a UE device is close to and / or on the LO frequency, the frequency of the IMD is closer to the frequency of the wanted signal, thereby decreasing and / or eliminating the need for A-MPR restrictions. Additionally, as shown in FIG. ID, when the allocated RBs for the UL transmission are placed closer to the LO frequency, the amount and / or level of MPR required is reduced.

[0085]

[0082] Referring to FIGS. IE and IF, in the conventional art, the above problems in NCIB CA may be addressed by allocating two separate LOs, one LO designated for the UL channel (e.g., CC1 of FIG. IE, which follows the downlink frequency of CC1), and the other LO designated for the DL channel (e.g., CC2 of FIG. IE, which is not used for the uplink operation, or the edge of CC1 in FIG. IF, when there is only one LO for the downlink operation shared with the uplink operation). However, this approach causes reductions in the transmission speeds achievable by the UE device due to delays in the settling of hardware components within the UE device, such as the settling of the oscillator, etc., particularly when frequent switching is performed between the LOs due to switching between UL mode and DL mode, etc. Accordingly, it is a further desire of the example embodiments to provide a method of using a single LO for both TDD UL transmission and DL reception with decreased and / or no MPR and / or A-MPR restrictions, in order to increase the transmission power, reduce network resource usage, reduce IMD and / or EVM, etc., which will be discussed in further detail in connection with FIGS. 4 to 5D.

[0086]

[0083] While certain components of a wireless communication network are shown as part of the wireless communication system of FIG. 1A, the example embodiments are not limited thereto, and the wireless communication network may include components other than that shown in FIG. 1 A, which are desired, necessary, and / or beneficial for operation of the underlying networks within the wireless communication system, such as access points, switches, routers, nodes, servers, gateways, etc.

[0087]

[0084] FIG. 2 illustrates a block diagram of an example RAN node according to at least one example embodiment. The RAN node of FIG. 2 may correspond to the RAN nodes 110 and 140 of FIG. 1 A, but the example embodiments are not limited thereto.

[0088]

[0085] Referring to FIG. 2, a RAN node 200 may include processing circuitry, such as at least one processor 210, at least one communication bus 220, a memory 230, at least one core network interface 240, and / or at least one wireless antenna array 250, etc., but the example embodiments are not limited thereto. For example, the core network interface 240 and the wireless antenna array 250 may be combined into a single network interface, etc., or the RAN node 200 may include a plurality of wireless antenna arrays, a plurality of core network interfaces, etc., and / or any combinations thereof. The memory 230 may include various special purpose program code including computer executable instructions which may cause the RAN node 200 to perform the one or more of the methods of the example embodiments.

[0089]

[0086] In at least one example embodiment, the processing circuitry may include at least one processor (and / or processor cores, distributed processors, networked processors, etc.), such as the at least one processor 210, which may be configured to control one or more elements of the RAN node 200, and thereby cause the RAN node 200 to perform various operations. The processing circuitry (e.g., the at least one processor 210, etc.) is configured to execute processes by retrieving program code (e.g., computer readable instructions) and data from the memory 230 to process them, thereby executing special purpose control and functions of the entire RAN node 200. Once the special purpose program instructions are loaded into, (e.g., the at least one processor 210, etc.), the at least one processor 210 executes the special purpose program instructions, thereby transforming the at least one processor 210 into a special purpose processor.

[0090]

[0087] In at least one example embodiment, the memory 230 may be a non-transitory computer-readable storage medium and may include a random access memory (RAM), a read only memory (ROM), and / or a permanent mass storage device such as a disk drive, or a solid state drive. Stored in the memory 230 is program code (i.e., computer readable instructions) related to operating the RAN node 200, such as the methods discussed in connection with FIGS. 4 to 5D, the at least one core network interface 240, and / or at least one wireless antenna array 250, etc. Such software elements may be loaded from a non- transitory computer-readable storage medium independent of the memory 230, using a drive mechanism (not shown) connected to the RAN node 200, or via the at least one core network interface 240, and / or at least one wireless antenna array 250, etc.

[0091]

[0088] In at least one example embodiment, the communication bus 220 may enable communication and data transmission to be performed between elements of the RAN node 200. The bus 220 may be implemented using a high-speed serial bus, a parallel bus, and / or any other appropriate communication technology. According to at least one example embodiment, the RAN node 200 may include a plurality of communication buses (not shown), such as an address bus, a data bus, etc.

[0089] The RAN node 200 may operate as, for example, a 4G RAN node, a 5G RAN node, etc., and may be configured to schedule time domain resource allocations (TDRAs), e.g., orthogonal frequency division multiplexing (OFDM) symbols, physical resource blocks (PRBs), resource elements, etc., for UE devices connected to the RAN node 200, but the example embodiments are not limited thereto.

[0092]

[0090] For example, the RAN node 200 may allocate time-frequency resources of a carrier (e.g., resource blocks with time and frequency dimensions) based on operation on the time domain (e.g., time division duplexing) and / or the frequency domain (e.g., frequency division duplexing). In the time domain context, the RAN node 200 will allocate a carrier (or subbands of the carrier) to one or more UEs (e.g., UEs 120, 130, etc.) connected to the RAN node 200 during designated upload (e.g., uplink (UL)) time periods and designated download (e.g., downlink (DL)) time periods, or during designated special (S) time periods which may be used for UL and / or DL, but the example embodiments are not limited thereto.

[0093]

[0091] When there are multiple UEs connected to the RAN node 200, the carrier is shared in time such that each UE is scheduled by the RAN node 200, and the RAN node 200 allocates each UE with their own uplink time and / or downlink time. In the frequency domain context and / or when performing spatial domain multiplexing of UEs (e.g., MU MIMO, etc.), the RAN node 200 will allocate separate frequency subbands of the carrier to UEs simultaneously served by the RAN node 200, for uplink and / or downlink transmissions. Data transmission between the UE and the RAN node 200 may occur on a radio frame basis in both the time domain and frequency domain contexts. The minimum resource unit for allocation and / or assignment by the RAN node 200 to a particular UE device corresponds to a specific downlink / uplink time interval (e.g., one OFDM symbol, one slot, one minislot, one subframe, etc.) and / or a specific downlink / uplink resource block (e.g., twelve adjacent subcarriers, a frequency subband, etc.).

[0094]

[0092] For the sake of clarity and consistency, the example embodiments will primarily be described as using the time domain, but the example embodiments are not limited thereto.

[0095]

[0093] Additionally, the RAN node 200 may transmit scheduling information via physical downlink common channel (PDCCH) information to the one or more UE devices located within the cell servicing area of the RAN node 200, which may configure the one or more UE devices to transmit (e.g., UL transmissions via physical uplink control channel (PUCCH) information and / or physical uplink shared channel information (PUSCH), etc.) and / or receive (e.g., DL transmissions via PDCCH and / or physical downlink shared channel information (PDSCH), etc.) data packets to and / or from the RAN node 200. Additionally, the RAN node 200 may transmit control messages to the UE device using downlink control information (DCI) messages via physical (PHY) layer signaling, medium access control (MAC) layer control element (CE) signaling, radio resource control (RRC) signaling, etc., but the example embodiments are not limited thereto.

[0096]

[0094] The RAN node 200 may also include at least one core network interface 240, and / or at least one wireless antenna array 250, etc. The at least one wireless antenna array 250 may include an associated array of radio units (not shown) and may be used to transmit the wireless signals in accordance with a radio access technology, such as 4G LTE wireless signals, 5G NR wireless signals, etc., to at least one UE device, such as UE 130, etc. According to some example embodiments, the wireless antenna array 250 may be a single antenna, or may be a plurality of antennas, etc. For example, the wireless antenna array 250 may be configured as a grid of beams (GoB) which transmits a plurality of beams in different directions, angles, frequencies, and / or with different delays, etc., but the example embodiments are not limited thereto.

[0097]

[0095] The RAN node 200 may communicate with a core network (e.g., backend network, backhaul network, backbone network, Data Network, etc.) of the wireless communication network via a core network interface 240. The core network interface 240 may be a wired and / or wireless network interface and may enable the RAN node 200 to communicate and / or transmit data to and from to network devices on the backend network, such as a core network gateway (not shown), a Data Network (e.g., Data Network 105), such as the Internet, intranets, wide area networks, telephone networks, VoIP networks, etc.

[0098]

[0096] While FIG. 2 depicts an example embodiment of a RAN node 200, the RAN node is not limited thereto, and may include additional and / or alternative architectures that may be suitable for the purposes demonstrated. For example, the functionality of the RAN node 200 may be divided among a plurality of physical, logical, and / or virtual network elements, such as a centralized unit (CU), a distributed unit (DU), a remote radio head (RRH), and / or a remote radio unit (RRU), etc. Additionally, the RAN node 200 may operate in standalone (SA) mode and / or non-standalone (NSA) mode using interfaces (not shown) such as X2, Xn, etc., between the RAN node 200 and other RAN nodes of the wireless network, interfaces, such as SI, NG, etc., between the RAN node 200 and the core network (e.g., core network 100), interfaces between network functions of the RAN node 200 operating in a distributed and / or virtual RAN mode (not shown), such as Fl, El, etc., and / or interfaces between the physical layer (e.g., a baseband unit, etc.) and the radio layer (e.g., a RRH, core network interface 240, etc.) (not shown), such as CPRI, eCPRI, etc., but the example embodiments are not limited thereto.

[0099]

[0097] FIG. 3 illustrates a block diagram of an example UE device according to at least one example embodiment. The example UE device 300 of FIG. 3 may correspond to the UE devices 120 and / or 130 of FIG. 1A, but the example embodiments are not limited thereto, and the UE device(s) may employ alternative architectures, etc.

[0100]

[0098] Referring to FIG. 3, a UE 300 may include processing circuitry, such as at least one processor 310, at least one communication bus 320, a memory 330, a plurality of wireless antennas and / or wireless antenna panels 340, at least one input / output (UO) device 370 (e.g., a keyboard, a touchscreen, a mouse, a microphone, a camera, a speaker, etc.), and / or a display panel 380 (e.g., a monitor, a touchscreen, etc.), but the example embodiments are not limited thereto. According to some example embodiments, the UE 300 may include a greater or lesser number of constituent components, and for example, the UE 300 may also include at least one battery (not shown), etc., but the example embodiments are not limited thereto. Additionally, the UE 300 may further include one or more sensors 350, such as proximity sensors (e.g., an infra-red proximity sensor, a capacitive proximity sensor, etc.), location sensors (e.g., GPS, GLONASS, Beidou, Galileo, etc.), other sensors (e.g., thermometers, humidity sensors, pressure sensors, motion sensors, accelerometers, etc.), actuators, etc. Additionally, the I / O device 360 and / or the display panel 370, etc., of UE 300 may be optional.

[0101]

[0099] In at least one example embodiment, the processing circuitry may include at least one processor (and / or processor cores, distributed processors, networked processors, etc.), such as the at least one processor 310, which may be configured to control one or more elements of the UE 300, and thereby cause the UE 300 to perform various operations. The processing circuitry (e.g., the at least one processor 310, etc.) is configured to execute processes by retrieving program code (e.g., computer readable instructions) and data from the memory 330 to process them, thereby executing special purpose control and functions of the entire UE 300. Once the special purpose program instructions are loaded into the processing circuitry (e.g., the at least one processor 310, etc.), the at least one processor 310 executes the special purpose program instructions, thereby transforming the at least one processor 310 into a special purpose processor.

[0102] £1001 In at least one example embodiment, the memory 330 may be a non-transitory computer-readable storage medium and may include a random access memory (RAM), a read only memory (ROM), and / or a permanent mass storage device such as a disk drive, or a solid state drive. Stored in the memory 330 is program code (i.e., computer readable instructions) related to operating the UE 300, such as the methods discussed in connection with FIGS. 4 to 5D, etc. Such software elements may be loaded from a non-transitory computer-readable storage medium independent of the memory 330, using a drive mechanism (not shown) connected to the UE 300, or via the plurality of wireless antennas 340, etc. Additionally, the memory 330 may store network configuration information, such as system information, resource block scheduling, etc., for communicating with at least one RAN node, e.g., RAN node 110, etc., accessing a wireless network, etc., but the example embodiments are not limited thereto.

[0103] £1011 In at least one example embodiment, the at least one communication bus 320 may enable communication and data transmission / reception to be performed between elements of the UE 300, and / or monitor the status of the elements of the UE 300 (e.g., monitor the transmission power levels, monitor the interference levels, monitor channel quality levels, etc.). The bus 320 may be implemented using a high-speed serial bus, a parallel bus, and / or any other appropriate communication technology. According to at least one example embodiment, the UE 300 may include a plurality of communication buses (not shown), such as an address bus, a data bus, etc.

[0104] £102£ The UE 300 may also include a plurality of wireless antenna panels 340, but is not limited thereto. The plurality of wireless antenna panels 340 may include a plurality of associated radio units (not shown) and may be used to transmit wireless signals in accordance with at least one desired radio access technology, such as 4G LTE, 5G NR, Wi-Fi, etc. Additionally, the plurality of wireless antenna panels 340 may be configured to transmit and / or receive data communications to one or more RAN nodes (and / or TRPs, e.g., RAN node 110, etc.), but the example embodiments are not limited thereto. The plurality of wireless antenna panels 340 may be located at the same or different physical locations on the body of the UE 300, may have the same or different orientations, may operate in the same or different frequency ranges, may operate in accordance with the same or different radio access technology, etc. According to some example embodiments, the plurality of wireless antenna panels 340 may be a single antenna, or may be a plurality of antennas, etc.

[0105] £1031 While FIG. 3 depicts an example embodiment of a UE 300, the UE device is not limited thereto and may include additional and / or alternative architectures that may be suitable for the purposes demonstrated.

[0106] H041 FIG. 4 illustrates an example flowchart for performing TDD configuration in DL fragmented CA according to some example embodiments, but the example embodiments are not limited thereto. FIGS. 5 A to 5D illustrate four example LO configurations according to some example embodiments.

[0107]

[0105] Referring now to FIG. 4, according to at least one example embodiment, in operation S410, a UE device, such as UE 120 of FIG. 1A, etc., may determine its UE capability information, including its extended capabilities for fragmented and / or NCIB CA pairs. For example, the extended capability information may indicate LO settings and / or RB preference information associated with the NCIB CA in TDD, but is not limited thereto. For example, the extended capability information may include information indicating whether the UE is capable of using one LO placement for both UL and DL in TDD for fragmented carriers, whether the UE is capable of using 2 LOs in TDD for fragmented carriers (e.g., a first LO for UL and a second LO for DL, etc.), but is not limited thereto. As another example, the RB preference information may indicate whether the UE has a preference on filling the allocation of RBs for UL (e.g., filling the RBs in the order of the carrier’s distance to LO, RBs to LO, etc.), whether the UE has a preference for uplink RB placement closest to the LOs frequency placement, etc., but is not limited thereto.

[0108] 11061 In operation S420, the UE 120 and the RAN node 110 may establish the NCIB CA connection in TDD mode based on the UE capability information. For example, the UE capability information may include information regarding band combinations supported by the UE device, information regarding whether the UE device supports a traditional NCIB CA configuration of the downlink and / or a NCIB CA configuration using fragmented CA, etc., but the example embodiments are not limited thereto. In operation S430, the RAN node 110 transmits connection configuration information (e.g., a radio resource control (RRC) configuration message and / or RRC reconfiguration message, etc.) to the UE device 120. The connection configuration information may include settings and / or parameters for the NCIB CA connection, settings and / or parameters for the TDD UL, and a selection of the number of LOs to be used by the UE device 120 for the NCIB CA connection. For example, the RAN node 110 may indicate that a single LO is to be shared for the NCIB CA DL connection and TDD UL based on the UE capability information and the allocated carrier components (CCs) of the NCIB CA connection.

[0109]

[0107] Referring now to FIG. 5A, assuming that the NCIB CA connection is established using a pair of non-contiguous CC fragments, e.g., CC1 and CC2, when the RAN node 110 determines that the distance between CC1 and CC2 are equal (e.g., equidistant, etc.) from the center of the frequency spectrum allocated to the UE 120, or in other words, the allocated LO of the UE device 120, the RAN node 110 may assign and / or allocate RBs associated with either CC1 or CC2 to the UE device 120 for UL transmission and both for DL reception, but will not assign and / or allocate RBs in both CC1 and CC2 for the uplink, thereby increasing the efficiency of the usage of radio resources and allowing the RAN node 110 to assign the unallocated RBs in either CC1 or CC2 to another UE device, such as UE device 130, etc. Further, because the UE device 120 uses a single LO for both UL and DL, the UE device 120 increases the processing speed, thereby improving latency times in comparison to UE devices which switches LO locations for UL and DL, respectively. Additionally, in order to decrease the amount of EVM and / or IMD, the RAN node 110 may assign and / or allocate uplink RBs in the selected CC which are closest to the LO frequency of the UE device 120 and / or the center of the frequency spectrum allocated to the UE device 120.

[0110]

[0108] Referring now to FIG. 5B, in a circumstance where the distances between the noncontiguous CC fragments to the LO frequency are unequal, the RAN node 110 may determine which one of the CC fragments is closest to the LO frequency, assigns which one of the CC to use for TDD UL by the UE device 120, and allocates RBs associated with the CC fragment closest to the LO frequency to the UE device 120. As shown in FIG. 5B, because the LO frequency is within the frequency range of CC1, the RAN node 110 may allocate the RBs closest to the LO frequency within CC1 to the UE device 120, but the example embodiments are not limited thereto.

[0111] £1091 Similar to FIG. 5B, when there are a plurality of non-contiguous CC pairs assigned to the NCIB CA connection between the UE device 120 and the RAN node 110 (as shown in FIG. 5C), the RAN node 110 may determine the CC among the plurality of CC fragment pairs closest to the LO frequency, and may assign the closest CC to the uplink operation of the UE device 120. More specifically, the RAN node 110 may assign the RBs closest to the LO frequency within the closest CC to the UE device 120, but the example embodiments are not limited thereto.

[0112]

[0110] Returning to FIG. 4, in operation S440, the UE device 120 may transmit UE assistance information in response to the connection configuration information. The UE assistance information may include preferences of whether the UE prefers to use the DL LO used for the downlink NCIB CA fragmented carrier pair or a separate LO for the uplink transmission. Additionally, the UE device 120 may repeat the transmission of the UE capability information and / or may transmit updates (e.g., dynamic updates, etc.) to the UE capability information, such as whether the UE device does not have any additional LOs to use, etc., but the example embodiments are not limited thereto.

[0113] Hill In operation S450, the UE device 120 may optionally transmit a connection configuration complete message (e.g., a RRC Reconfiguration complete message, etc.) to the RAN node 110, however the example embodiments are not limited thereto, and for example, the connection configuration complete message may be included in the UE assistance information and / or may be omitted, etc.

[0114] 11121 In operation S460, the UE device 120 may transmit UL data to one of the CC with RBs allocated closest to the LO. Additionally, the UE device 120 may receive DL data from the RAN node 110 using the allocated RBs of the NCIB CA connection.

[0115] 11131 In operation S470, the RAN node 110 may determine that the amount of EVM and / or IMD caused by the usage of a single LO in the carrier bandwidth associated with the selected NCIB CC pair(s) is above a desired threshold, or in other words, the MPR level and / or the A-MPR level associated with the uplink RB allocation is above a desired MPR threshold and / or a desired A-MPR threshold, the RAN node 110 may initiate a reconfiguration of the NCIB CA connection with the UE device 120. For example, as shown in FIG. 5D, if the RAN node 110 determines that an assigned CC, e.g., CC1, carrying the UL is moving away from the single LO, or in other words, the distance between the assigned CC and the single LO exceeds a desired distance threshold, the RAN node 110 may determine that the MPR impact is above the desired MPR threshold and therefore may re-configure the UE device 120 to use separate LOs for UL and DL.

[0116] £1141 In operation S480, the RAN node 110 may transmit connection configuration information to the UE device 120. The connection configuration information may instruct the UE device 120 to use separate LOs for UL and DL, information indicating at least two NCIB CCs for use in the NCIB CA connection, and / or the RB allocation of the UE device corresponding to the at least two NCIB CCs, etc., but the example embodiments are not limited thereto.

[0117] £1151 In operation S490, the UE device 120 may transmit UE assistance information to the RAN node 110. Similar to operation S440, the UE assistance information may include the preferences of whether the UE prefers to use the DL LO used for the downlink NCIB CA fragmented carrier pair or a separate LO for the uplink transmission, etc., which may have been updated, modified, and / or changed since the time that operation S440 was performed. Additionally, the UE device 120 may repeat the transmission of the UE capability information and / or may transmit updates (e.g., dynamic updates, etc.) to the UE capability information, such as whether the UE device does not have any additional LOs to use, etc., but the example embodiments are not limited thereto. As shown in FIG. 5D, the UE 120 may allocate a DL LO at the center of the frequency spectrum allocated to the UE 120, and may set an UL LO based on the assigned CC, but the example embodiments are not limited thereto.

[0118]

[0116] Optionally, in operation S500, the UE device 120 may also transmit a connection configuration complete message (e.g., a RRC Reconfiguration complete message, etc.) to the RAN node 110, however the example embodiments are not limited thereto, and for example, the connection configuration complete message may be included in the UE assistance information and / or may be omitted, etc.

[0119] £1171 In operation S510, the UE device 120 may transmit UL data to the RAN node 110 using the allocated uplink RBs of the NCIB CA connection associated with the UL LO frequency and may receive DL data from the RAN node 110 using the allocated downlink RBs associated with the DL LO frequency and the fragmented carrier pair, etc.

[0120] £118£ This written description uses examples of the subject matter disclosed to enable any person skilled in the art to practice the same, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the subject matter is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims.

Claims

WHAT IS CLAIMED IS:

1. A first apparatus comprising: a memory storing computer readable instructions; and processing circuitry configured to execute the computer readable instructions to cause the first apparatus to, transmit first apparatus capability information to a second apparatus, the first apparatus capability information including local oscillator (LO) frequency placement corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA), and perform time duplex division (TDD) uplink (UL) transmission using at least one carrier component of an NCIB CA connection established with a second apparatus based on the LO frequency placement.

2. The first apparatus of claim 1, wherein the first apparatus capability information includes at least one of: a number of LOs supported by the first apparatus, resource block (RB) preference information associated with the at least one LO, preference for uplink RB placement closest to the LOs frequency placement, or any combinations thereof.

3. The first apparatus of any one of claims 1 to 2, wherein the first apparatus is further caused to: receive connection configuration information from the second apparatus, the connection configuration information indicating parameters for the NCIB CA connection in a TDD band of operation and a selection of a number of LOs to be used for the NCIB CA connection.

4. The first apparatus of any one of claims 1 to 3, wherein the parameters for the NCIB CA connection include indication of at least two NCIB carrier components for use in a downlink (DL) NCIB CA connection and the UL RB allocation preference of the first apparatus corresponding to a UL response on one DL carrier component of the at least two NCIB carrier components also having UL allocations.

265. The first apparatus of any one of claims 1 to 4, wherein the first apparatus is further caused to: determine the selected number of LOs and the LO frequency placement based on the indication of the at least two NCIB carrier components; and determine first apparatus extended capability information associated with the NCIB CA connection.

6. The first apparatus of any one of claims 1 to 5, wherein the first apparatus is further caused to: transmit first apparatus assistance information to the second apparatus in response to the connection configuration information, the first apparatus assistance information including the determined selected number of LOs and the LO frequency placement; and perform the TDD UL transmission based on the determined selected number of LOs and the LO frequency placement.

7. The first apparatus of any one of claims 1 to 6, wherein the connection configuration information indicates the selection of a single LO to be used for the NCIB CA connection and the UL transmission; and the first apparatus is further caused to, perform the TDD UL transmission, complying to the UL RB allocation preference, with the second apparatus based on the single LO, and receive downlink (DL) data from the second apparatus based on the single LO.

8. The first apparatus of any one of claims 1 to 7, wherein the connection configuration information indicates the selection of a first LO to be used for TDD UL transmissions and a second LO to be used for TDD DL transmissions on the NCIB CA connection; and the first apparatus is further caused to, perform the TDD UL transmission with the second apparatus using the one carrier component of the NCIB CA connection based on the first LO, and perform TDD DL reception with the second apparatus using every carrier component of the NCIB CA connection based on the second LO.

9. A first apparatus comprising: a memory storing computer readable instructions; and processing circuitry configured to execute the computer readable instructions to cause the first apparatus to, receive second apparatus capability information from a second apparatus, the second apparatus capability information including local oscillator (LO) configuration of the second apparatus corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA), and receive time duplex division (TDD) uplink (UL) transmission from the second apparatus using at least one carrier component of an NCIB CA connection established with the second apparatus based on the LO configuration.

10. The first apparatus of claim 9, wherein the LO configuration includes at least one of a number of LOs supported by the second apparatus, resource block (RB) preference information associated with the at least one LO, preference for uplink RB placement closest to a LOs frequency placement of the second apparatus, or any combinations thereof.

11. The first apparatus of any one of claims 9 to 10, wherein the first apparatus is further caused to: determine connection configuration information based on the LO configuration, the connection configuration information indicating parameters for the NCIB CA connection in a TDD band of operation and a selection of a number of LOs to be used for the NCIB CA connection; and transmit the connection configuration information to the second apparatus.

12. The first apparatus of any one of claims 9 to 11, wherein the parameters for the NCIB CA connection include indication of at least two NCIB carrier components for use in a downlink (DL) NCIB CA connection and the UL RB allocation preference of the second apparatus corresponding to a UL response on one DL carrier component of the at least two NCIB carrier components also having UL allocations.

13. The first apparatus of any one of claims 9 to 12, wherein the first apparatus is further caused to: determine at least two NCIB carrier components for use in the NCIB CA connection; and determine the number of LOs to be used for the NCIB CA connection based on a carrier bandwidth associated with the at least two NCIB carrier components, a maximum power reduction (MPR) level associated with the carrier bandwidth, and an additional maximum power reduction (A-MPR) level associated with the carrier bandwidth.

14. The first apparatus of any one of claims 9 to 13, wherein the first apparatus is further caused to: determine whether a single LO or two LOs is to be used for the NCIB CA connection based on a distance between closest edges of the at least two NCIB carrier components to a center of the carrier bandwidth and a distance threshold.

15. The first apparatus of any one of claims 9 to 14, wherein the first apparatus is further caused to: determine a UL RB allocation of the second apparatus in one NCIB carrier component of the at least two NCIB carrier components based on the UL RB preference information associated with the at least one LO and distances between the at least two NCIB carrier components and a center of the carrier bandwidth.

16. The first apparatus of any one of claims 9 to 15, wherein the first apparatus is further caused to: receive second apparatus assistance information from the second apparatus in response to the connection configuration information, the second apparatus assistance information including indication of a selected number of LOs and a determined LO frequency placement; and receive the TDD UL transmission based on the selected number of LOs and the determined LO frequency placement.

17. A method of operating a first apparatus, the method comprising:29transmitting first apparatus capability information to a second apparatus, the first apparatus capability information including local oscillator (LO) frequency placement corresponding to at least one LO associated with non-contiguous (NC) intra-band (IB) carrier aggregation (CA); and performing time duplex division (TDD) uplink (UL) transmission using at least one carrier component of an NCIB CA connection established with a second apparatus based on the LO frequency placement.

18. The method of claim 17, wherein the first apparatus capability information includes at least one of a number of LOs supported by the first apparatus, resource block (RB) preference information associated with the at least one LO, preference for uplink RB placement closest to the LOs frequency placement, or any combinations thereof.

19. The method of any one of claims 17 to 18, further comprising: receiving connection configuration information from the second apparatus, the connection configuration information indicating parameters for the NCIB CA connection in a TDD band of operation and a selection of a number of LOs to be used for the NCIB CA connection.

20. The method of any one of claims 17 to 19, wherein the parameters for the NCIB CA connection include indication of at least two NCIB carrier components for use in a downlink (DL) NCIB CA connection and the UL RB allocation preference of the first apparatus corresponding to a UL response on one DL carrier component of the at least two NCIB carrier components also having UL allocations; and the method further includes, determining the selected number of LOs and the LO frequency placement based on the indication of the at least two NCIB carrier components, determining first apparatus extended capability information associated with the NCIB CA connection, transmitting first apparatus assistance information to the second apparatus in response to the connection configuration information, the first apparatus assistance30information including the determined selected number of LOs and the LO frequency placement, and performing the TDD UL transmission based on the determined selected number of LOs and the LO frequency placement.31

Images