Enhancement of non-collocated carrier aggregation

Abstract

Apparatuses, systems, and methods for enhanced non-collocated carrier aggregation in cellular systems (e.g., LTE systems, 5G NR systems, and higher systems) are disclosed. A method may include establishing a cellular link with a network node; and transmitting signaling including capability information indicating support for carrier aggregation (CA) of the first component carrier (CC) and the second CC. The method may further include receiving physical downlink shared channel (PDSCH) signaling on the first CC and the second CC, and measuring a relative time difference (RTD) between the first CC and the second CC. The method may also include sending a report including the measured RTD to a network node; and receiving, from the network node, a first downlink (DL) signaling on the first CC and a second DL signaling on the second CC. One of the first DL signaling or the second DL signaling may include an adjusted set of OFDM symbols that is adjusted based on the measured RTD such that degraded OFDM symbols are avoided.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communication, and more particularly, to apparatus, systems, and methods for enhanced non-collocated carrier aggregation in cellular systems (e.g., LTE systems, 5G NR systems, etc.). BACKGROUND

[0002] The use of wireless communication systems is rapidly increasing. In recent years, wireless devices such as smartphones, wearable or accessory devices, and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated, complex applications that utilize these functions.

[0003] Long Term Evolution (LTE) is currently the technology of choice for most wireless network operators worldwide, providing mobile broadband data and high-speed Internet access to their subscriber base. LTE was first proposed in 2004 and first standardized in 2008. Since then, as the use of wireless communication systems has grown exponentially, the demand for wireless network operators to support higher capacity for higher density of mobile broadband users has also risen. As a result, research into a new radio access technology began in 2015, and in 2017, the first release of the Fifth Generation New Radio (5G NR) was standardized.

[0004] 5G-NR (also referred to simply as NR) provides higher capacity for higher density of mobile broadband users compared to LTE, while also supporting device-to-device, ultra-reliable, and massive machine-type communications, as well as lower latency and / or lower battery consumption. In addition, NR can allow for more flexible UE scheduling compared to current LTE. As a result, continued development of 5G-NR is ongoing to take advantage of higher throughput possible at higher frequencies. Thus, improvements in this area are desirable. SUMMARY

[0005] Embodiments relate to wireless communication, and more particularly, to apparatus, systems, and methods for enhanced non-collocated carrier aggregation in cellular systems (e.g., LTE systems, 5G NR systems, etc.).

[0006] In some embodiments, a method can include establishing a cellular link with a network node and transmitting signaling to the network node, the signaling including capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC. The method can further include receiving physical downlink shared channel (PDSCH) signaling on the first CC and the second CC from the network node and measuring a relative time difference (RTD) between a start of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current time slot of the first CC and a start of a first OFDM symbol in a current time slot of the second CC. Alternatively, the method can include measuring an RTD between a start of a first OFDM symbol in a current time slot of the first CC and an end of a last OFDM symbol in a previous time slot of the second CC. The method can also include transmitting a report including the measured RTD to the network node and receiving first downlink (DL) signaling on the first CC and second DL signaling on the second CC from the network node. According to some embodiments, one of the first DL signaling or the second DL signaling can include an adjusted set of OFDM symbols. Additionally or alternatively, the adjusted set of OFDM symbols can be adjusted based at least in part on the measured RTD such that a degraded OFDM symbol is avoided.

[0007] According to some examples, the method can further include determining a measurement reference point for the first CC or the second CC. Additionally, according to some embodiments, the measurement reference point can correspond to a CC that is another one of the first CC or the second CC associated with the adjusted set of OFDM symbols. In some embodiments, the determination can be based on one or more reference signal received power (RSRP) metrics, one or more reference signal received quality (RSRQ) metrics, one or more maximum average aggregate throughput metrics associated with the first CC and the second CC. In some embodiments, the determination can be based on which of the first CC or the second CC is associated with a primary cell (PCell). Additionally or alternatively, the determination can be based at least in part on an indication received from the network node.

[0008] In some embodiments, the measured RTD can be less than or equal to a maximum receive timing difference (MRTD), and the MRTD can be greater than a cyclic prefix (CP). Thus, the UE can be able to support an increased power imbalance between the first CC and the second CC when the measured RTD is less than or equal to the MRTD. According to further embodiments, the method can include determining a degraded OFDM symbol associated with the first CC or the second CC based on the measured RTD. In some embodiments, the degraded OFDM symbol can be corrupted due to a phase jump when no analog gain change occurs at a beginning of at least one of the first CC or the second CC. In some embodiments, the method can be performed by a Type 3a user equipment (UE) or a Type 3b UE.

[0009] In some embodiments, a method can include establishing a radio resource control (RRC) connection with a user equipment (UE), and receiving signaling from the UE including capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC. The method can further include transmitting physical downlink shared channel (PDSCH) signaling on the first CC and the second CC to the UE, and receiving a report from the UE including a measured relative time difference (RTD). In some embodiments, the measured RTD can be an RTD between a beginning of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current time slot of the first CC and a beginning of a first OFDM symbol in a current time slot of the second CC, or an RTD between the beginning of the first OFDM symbol in the current time slot of the first CC and an end of a last OFDM symbol in a previous time slot of the second CC. The method can further include comparing the measured RTD to one or more signaling metrics associated with the first CC and the second CC, and transmitting first downlink (DL) signaling on the first CC and second DL signaling on the second CC to the UE. According to some embodiments, one of the first DL signaling or the second DL signaling can include an adjusted set of OFDM symbols. Additionally or alternatively, the adjusted set of OFDM symbols can be adjusted to avoid a degraded OFDM symbol, and can be based at least in part on the comparison of the measured RTD to the one or more signaling metrics.

[0010] According to further embodiments, the method can include transmitting signaling to the UE including an indication of an alignment of a shared low noise amplifier (LNA) with the first CC or the second CC. Additionally or alternatively, the method can include configuring at least one control resource set (CORESET) located after the first OFDM symbol for receiving a physical downlink control channel (PDCCH). In some embodiments, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the measured RTD is less than a cyclic prefix (CP) that is less than X microseconds (ps), where X is a value that can correspond to a maximum receive timing difference (MRTD). Additionally or alternatively, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the CP is less than the measured RTD that is less than X ps. In some embodiments, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the measured RTD is greater than X ps.

[0011] In some embodiments, if the measured RTD is less than the CP (which is less than X ps), the method can further include scheduling the adjusted PDSCH signaling using available symbols in the slot (e.g., within a range of sym0-sym13). Additionally or alternatively, if the CP is less than the measured RTD (which is less than X ps), the method can further include scheduling the adjusted PDSCH signaling using symbols from a range of sym1-sym13 or from symbols in a range of sym0-sym12 (e.g., excluding the first symbol or the last symbol in the slot of one of the CCs). In some embodiments, if the measured RTD is greater than X ps, the method can further include refraining from scheduling the adjusted PDSCH signaling. According to further embodiments, up to four multiple-input multiple-output (MIMO) layers can be supported on the first CC and / or the second CC.

[0012] The techniques described herein can be implemented in and / or used with a number of different types of devices, including but not limited to any of the drones (UAVs), drone controllers (UACs), UTM servers, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0013] This summary is intended to provide a brief overview of some of the subject matter described in this document. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following DETAILED DESCRIPTION, Figures, and Claims. BRIEF DESCRIPTION OF DRAWINGS

[0014] A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0015] FIG. 1A An example wireless communication system in accordance with some embodiments is illustrated.

[0016] FIG. 1B An example of a base station and an access point in communication with a user equipment (UE) device in accordance with some embodiments is illustrated.

[0017] FIG. 2 An example block diagram of a base station in accordance with some embodiments is illustrated.

[0018] FIG. 3 An example block diagram of a server in accordance with some embodiments is illustrated.

[0019] FIG. 4 An example block diagram of a UE in accordance with some embodiments is illustrated.

[0020] FIG. 5 An example block diagram of cellular communication circuitry in accordance with some embodiments is illustrated.

[0021] FIG. 6 A communication flow diagram of an example method for enhanced non-collocated carrier aggregation in accordance with some embodiments is illustrated.

[0022] FIG. 8A to FIG. 8B 、 FIG. 9A to FIG. 9B and FIG. 10A to FIG. 10B Example aspects of enhanced non-collocated carrier aggregation related to dynamic PDSCH scheduling in accordance with some embodiments are illustrated.

[0023] FIGS. 8-10 illustrate example aspects of enhanced non-collocated carrier aggregation related to dynamic PDSCH scheduling in accordance with some embodiments.

[0024] While the features described herein can be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting in any way, but rather are intended to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0025] Acronyms

[0026] Various acronyms are used throughout this disclosure. Definitions of the most commonly occurring acronyms that can appear in this disclosure are provided below:

[0027] • 3GPP: Third Generation Partnership Project

[0028] • UE: User Equipment

[0029] • RF: Radio Frequency

[0030] • DL: Downlink

[0031] • UL: Uplink

[0032] • LTE: Long Term Evolution

[0033] • NR: New Radio

[0034] • 5GS: 5G System

[0035] • 5GMM: 5GS Mobility Management

[0036] • 5GC / 5GCN: 5G Core Network

[0037] • gNB: Next Generation Node B

[0038] • RS: Reference Signal

[0039] • CC: Component Carrier

[0040] • TRP: Transmission and Reception Point

[0041] • CA: Carrier Aggregation

[0042] • MRTD: Maximum Receive Timing Difference

[0043] • CP: Cyclic Prefix

[0044] • RTD: Relative Time Difference

[0045] • OFDM: Orthogonal Frequency Division Multiplexing

[0046] • PDSCH: Physical Downlink Shared Channel

[0047] • PDCCH: Physical Downlink Control Channel

[0048] • SSB: Synchronization Signal Block

[0049] • PBCH: Physical Broadcast Channel

[0050] • CSI-RS: Channel State Information Reference Signal

[0051] • TRS: Total Radiated Sensitivity

[0052] • LNA: Low Noise Amplifier

[0053] • RSRP: Reference Signal Received Power

[0054] • RSRQ: Reference Signal Received Quality

[0055] • PCell: Primary Cell

[0056] • SCell: Secondary Cell

[0057] • FDD: Frequency Division Duplex

[0058] • TDD: Time Division Duplex

[0059] • CORESET: Control Resource Set

[0060] • DM-RS: Demodulation Reference Signal

[0061] Terms

[0062] The following is a glossary of terms used in the disclosure:

[0063] Memory Medium - any one or all of volatile and non-volatile memory devices. The term "memory medium" is intended to include any and all tangible computer-readable media, and is intended to cover both memory media and physical transmission media. The term "memory medium" is intended to include both distribution and storage media. Examples of physical storage media include Compact Discs (CDs), Digital Versatile Discs (DVDs), floppy disks, and memory sticks. Physical transmission media include physical media that convey programs to a computer system, such as the Internet, wireline, optical, radio frequency (RF), or other physical transmission media. The term "memory medium" is intended to include both memory media and physical transmission media.

[0064] Carrier Medium - a memory medium as described above, and a physical transmission medium such as a bus, network, and / or other physical transmission medium which conveys signals such as electrical, electromagnetic, or digital signals.

[0065] Programmable hardware element - includes various hardware devices including a plurality of programmable function blocks connected via a programmable interconnect. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). The programmable function blocks can range from fine-grained (combinatorial logic or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements can also be referred to as "configurable logic devices."

[0066] Computer system (or computer) - any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, internet appliance, personal digital assistant (PDA), television system, grid

[0067] User equipment (UE) (or "UE device") - any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone ™ , Android ™ -based phones), portable gaming devices (e.g., Nintendo DS ™ , PlayStation Portable ™ , Gameboy Advance ™ , iPhone ™ ), laptops, wearable devices (e.g., smartwatches, smartglasses), PDAs, portable Internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. In general, the term "UE" or "UE device" can be broadly defined to encompass any electronic, computing, and / or telecommunication device (or combination of devices) which is easily transported by a user and capable of wireless communication.

[0068] Base station - the term "base station" has the full breadth of its ordinary meaning and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0069] Processing element (or processor) - refers to various elements or combinations of elements that are capable of performing a function of a device such as a user equipment or a cellular network device. Processing elements can include, for example: a processor and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (application specific integrated circuit), programmable hardware elements such as an FPGA (field programmable gate array), and any of various combinations thereof.

[0070] Channel - a medium used to convey information from a transmitter (sender) to a receiver. It should be noted that the characteristics of the term "channel" can differ according to different wireless protocols, and thus the term "channel" as used herein can be taken to mean used in a manner consistent with the type of device to which the term is referenced to comply with standards. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel can be 22 MHz wide, while a Bluetooth channel can be 1 MHz wide. Other protocols and standards can include different definitions of a channel. Also, some standards can define and use multiple types of channels, e.g., different channels for uplink or downlink and / or different channels for different uses such as data, control information, etc.

[0071] Band - the term "band" has the full breadth of its ordinary meaning, and at least includes a segment of the spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0072] Wi-Fi - the term "Wi-Fi" (or WiFi) has the full breadth of its ordinary meaning, and at least includes a wireless communication network or RAT in which a device can communicate through wireless LAN (WLAN) access points. Most modern Wi-Fi networks (or WLAN networks) are based on IEEE 802.11 standards and marketed under the name "Wi-Fi." Wi-Fi (WLAN) networks differ from cellular networks.

[0073] 3GPP access - refers to an access (e.g., radio access technology) specified by 3GPP standards. These accesses include, but are not limited to, LTE, LTE-A, and / or 5G NR. In general, 3GPP access refers to various types of cellular access technologies.

[0074] Non-3GPP access - refers to any access (e.g., radio access technology) that is not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP accesses can be categorized into two categories, “trusted” and “untrusted”: Trusted non-3GPP accesses can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP accesses interwork with the EPC / 5GC via a network entity such as an Evolved Packet Data Gateway and / or 5G NR Gateway. Generally, non-3GPP access refers to various types of non-cellular access technologies.

[0075] Automatically - with reference to performance of an action or operation by a computer system (e.g., software executing on the computer system) or device (e.g., circuitry, programmable hardware elements, ASIC, etc.) without the direct specification or execution of the action or operation by a user. Thus, the term “automatically” is in contrast to manual performance or specification of operations where the user initiates or specifies each of the operations, or in cases where the user merely initiates the performance of the operation, but is not involved in the execution of the operation. For example, a user that selects each field and specifies their

[0076] Approximately - refers to a value that is close to or precise. For example, approximately can refer to a value that is within 1% to 10% of a precise (or desired) value. It should be noted, however, that the actual threshold (or tolerance) can be application dependent. For example, in some embodiments, “approximately” can mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold can be, e.g., 2%, 3%, 5%, etc., depending on the desires or requirements of a particular application.

[0077] Concurrent - refers to execution or performance in parallel, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency can be implemented using "strong" or strict parallelism, where tasks are performed in parallel (at least in part) on respective computing elements; or using "weak parallelism," where tasks are performed in an interleaved manner (e.g., through time-multiplexing of execution threads).

[0078] Various components can be described as being "configured to" perform one or more tasks. In such contexts, "configured to" is broadly synonymous with "having structure that" performs the one or more tasks during operation. Thus, a component can be configured to perform a task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module) even when the component is not currently performing that task (e.g., when the two modules are not connected). In some contexts, "configured to" can be broadly synonymous with "having circuitry that" performs the one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing that task. Generally, circuitry forming structure corresponding to "configured to" can include hardware circuitry.

[0079] For ease of description, various components can be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to." A component configured to perform one or more tasks is expressly intended to invoke 35 U.S.C. § 112(f) interpretation of that component.

[0080] FIG. 1A and FIG. 1B : communication system

[0081] FIG. 1A A simplified example wireless communication system is illustrated in accordance with some embodiments. Note that FIG. 1A The system of FIG. 1 is merely one example of a possible system, and features of the present disclosure can be implemented in any of various systems, as desired.

[0082] As shown, the example wireless communication system includes a base station 102A that communicates with one or more wireless devices, such as user equipment 106A, 106B, etc. 106N, and accessory devices, such as user equipment 107A, 107B, via a transmission medium. Each of the user equipment can be referred to herein as a "user equipment" (UE). Thus, the user equipment 106 and 107 are referred to as UEs or UE devices.

[0083] The base station (BS) 102A can be a base transceiver station (BTS) or cell site ("cellular base station"), and can include hardware that enables wireless communication with the UEs 106A through 106N and UEs 107A and 107B.

[0084] The communication area (or coverage area) of a base station can be referred to as a "cell." Base stations 102A and UEs 106 / 107 can be configured to communicate

[0085] As illustrated, base station 102A can also be equipped to communicate with a network 100 (e.g., with a core network of a cellular service provider, a telecommunication network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among various possibilities). Thus, base station 102A can facilitate communication between and among user equipment and / or user equipment and network 100. In particular, cellular base station 102A can provide UEs 106 / 107 with various telecommunication capabilities such as voice, SMS, and / or data services.

[0086] Base station 102A, as well as other similar base stations (such as base stations 102B,..., 102N) operating according to similar or different cellular communication standards can thus be provided as a network of cells that can provide continuous or

[0087] Thus, although base station 102A can serve as a "serving cell" for UEs 106 / 107 as exemplified in FIG. 1, each UE 106 / 107 can also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which can be provided by base stations 102B-102N and / or any other base stations), which can be referred to as "neighboring cells." Such cells can also be capable of facilitating communication between and among user equipment and / or user equipment and network 100. Such cells can include "macro" cells, "micro" cells, "pico" cells, and / or any of various other granularities of service area sizes. For example, base stations 102A-102B exemplified in FIG. 1 can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.

[0088] In some embodiments, the base station 102A can be a next generation base station, e.g., a 5G New Radio (5G NR) base station or "gNB." In some embodiments, the gNB can be connected to a traditional evolved packet core (EPC) network and / or to an NR core (NRC) network. Further, a gNB cell can include one or more transition and reception points (TRPs). Further, a UE capable of operating according to 5G NR can be connected to one or more TRPs within one or more gNBs.

[0089] Note that the UE 106 / 107 can be capable of communicating using multiple wireless communication standards. For example, the UE 106 / 107 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., UMTS (associated with, e.g., a WCDMA or TD-SCDMA air interface), LTE, LTE-A, 5G NR, HSPA, etc.). If desired, the UE 106 / 107 can also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, e.g. GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0090] Note that the accessory device 107A / 107B can include cellular communication capabilities and thus be capable of communicating directly with a cellular base station 102A via a cellular RAT. However, because the accessory device 107A / 107B can be one or more of communication, output power, and / or battery limited, the accessory device 107A / 107B can in some instances selectively utilize a UE 106A / 106B as a proxy for communication purposes with the base station 102A and thus with the network 100. In other words, the accessory device 107A / 107B can selectively use the cellular communication capabilities of its companion device (e.g., UE 106A / 106B) for cellular communication. The limitation on the communication capabilities of the accessory device 107A / 107B can be permanent, e.g., due to limitations in output power or supported RATs, or temporary, e.g., due to various conditions such as a current battery state, inability to access a network, or poor reception.

[0091] FIG. 1BA user equipment 106 (e.g., one of devices 106A-106N) and an accessory device (or user equipment) 107 (e.g., one of devices 107A or 107B) that communicate with base stations 102 and access points 112, and each other, are illustrated in accordance with some embodiments. The UE 106 / 107 can be a device with cellular and non-cellular (e.g., Bluetooth, Wi-Fi, etc.) communication capabilities, such as a mobile phone, a wearable device, a handheld device, a computer or tablet, or almost any type of wireless device. The accessory device 107 can be a wearable device such as a smart watch. The accessory device 107 can include cellular communication capabilities and be capable of communicating directly with a base station 102 as shown. When the accessory device 107 is configured to communicate directly with a base station, it can be said to be in an “autonomous mode.” In addition, the accessory device 107 can also be capable of communicating with another device (e.g., UE 106), called a proxy device, intermediary device, or companion device, using a short-range communication protocol; for example, the accessory device 107 can be “paired” with the UE 106 in accordance with some embodiments, which can include establishing a communication channel and / or a trusted communication relationship with the UE 106. In some cases, the accessory device 107 can use the cellular functionality of the proxy device to communicate cellular voice and / or data with the base station 102. In other words, the accessory device 107 can provide voice and / or data packets intended for the base station 102 over a short-range link to the UE 106, and the UE 106 can use its cellular functionality to send (or relay) the voice and / or data to the base station on behalf of the accessory device 107. Similarly, voice and / or data packets sent by the base station and intended for the accessory device 107 can be received by the cellular functionality of the UE 106 and then relayed to the accessory device over a short-range link. As noted above, the UE 106 can be a mobile phone, a tablet, or any other type of handheld device, a media player, a computer, a laptop, or almost any type of wireless device. Note that when the accessory device 107 is configured to communicate indirectly with the base station 102 using the cellular functionality of an intermediary device or proxy device, it can be said to be in a “relayed mode.”

[0092] The UE 106 / 107 can include a processor configured to execute program instructions stored in memory. The UE 106 / 107 can perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 / 107 can include programmable hardware elements such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

[0093] The UEs 106 / 107 can include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UEs 106 can be configured to communicate using, for example, LTE / High-EUTRA, or 5G NR and / or LTE, High-EUTRA, using a single shared radio, or 5G NR using a single shared radio. The shared radio can be coupled to a single antenna, or can be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Generally, the radio can include any combination of bulk and analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio can implement one or more receive and transmit chains using the aforementioned hardware. For example, the UEs 106 / 107 can share one or more portions of receive and / or transmit chains between multiple wireless communication technologies, such as those discussed above.

[0094] In some embodiments, the UEs 106 / 107 can include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, the UEs 106 / 107 can include one or more radios shared between multiple wireless communication protocols, as well as one or more radios used by a single wireless communication protocol exclusively. For example, the UEs 106 / 107 can include a shared radio for communicating using either of LTE or 5G NR (or LTE or lxRTT or LTE), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are possible.

[0095] FIG. 2 : block diagram of a base station

[0096] FIG. 2 An example block diagram of a base station 102 according to some embodiments is illustrated. Note that FIG. 3 The base station of FIG. 2 is merely one example of a possible base station. As shown, the base station 102 can include a processor 204, which can execute program instructions for the base station 102. The processor 204 can also be coupled to a memory management unit (MMU) 240, which can be configured to translate virtual addresses into real addresses. The MMU 240 can also be configured to perform memory protection, address translation, and data caching. In some embodiments, the MMU 240 can be omitted.

[0097] The base station 102 can include at least one network port 270. The network port 270 can be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in FIG. 1 and FIG. 2

[0098] The network port 270 (or an additional network port) can also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network can provide mobility related services and / or other services to a plurality of devices, such as the UE devices 106. In some cases, the network port 270 can couple to the telephone network via the core network, and / or the core network can provide the telephone network (e.g., among other UE devices served by the cellular service provider).

[0099] In some embodiments, the base station 102 can be a next generation base station, such as a 5G New Radio (5G NR) base station, or “gNB.” In such embodiments, the base station 102 can connect to a traditional evolved packet core (EPC) network and / or to a NR core (NRC) network. Further, the base station 102 can be considered a 5G NR cell and can include one or more transition and reception points (TRPs). Further, a UE capable of operating according to 5G NR can be connected to one or more TRPs within one or more gNBs.

[0100] The base station 102 can include at least one antenna 234, and possibly multiple antennas. The at least one antenna 234 can be configured to operate as a wireless transceiver and can be further configured to communicate with UE devices 106 via radio 230. The antenna 234 is in communication with the radio 230 through a communication chain 232. The communication chain 232 can be a receive chain, a transmit chain, or both. The radio 230 can be configured to communicate via various wireless communication standards including, but not limited to, 5G NR, LTE, LTE-A, UMTS, Wi-Fi, etc.

[0101] ​The base stations 102 can be configured to use multiple wireless communication standards for wireless communications. In some instances, the base stations 102 can include multiple radios that can enable the base stations 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base stations 102 can include an LTE radio for performing communications according to LTE and a 5G NR radio for performing communications according to 5G NR. In this case, the base stations 102 can be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base stations 102 can include a multi-mode radio capable of performing communications according to any of a plurality of wireless communication technologies, such as 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, and so on.

[0102] As further described later herein, the BS 102 can include hardware and software components for implementing or supporting implementation of the features described herein. The processor 204 of the base station 102 can be configured to implement or support implementation of parts, or all, of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 204 can be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or additionally) the processor 204 of the BS 102, in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 can be configured to implement or support implementation of parts or all of the features described herein.

[0103] Further, as described herein, the processor 204 can be composed of one or more processing elements. In other words, one or more processing elements can be included in the processor 204. Thus, the processor 204 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 204. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the one or more processors 204.

[0104] Further, as described herein, the radio 230 can be composed of one or more processing elements. In other words, one or more processing elements can be included in the radio 230. Thus, the radio 230 can include one or more integrated circuits (ICs) that are configured to perform the functions of the radio 230. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the radio 230.

[0105] FIG. 3 : block diagram of a server

[0106] FIG. 3 Example block diagrams of server 104 according to some implementation schemes are shown. Note that... FIG. 3 The server shown is merely one example of a possible server. As illustrated, server 104 may include processor 344 capable of executing program instructions for server 104. Processor 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from processor 344 and translate these addresses into locations in memory (e.g., memory 364 and read-only memory (ROM) 354), or to other circuitry or devices.

[0107] Server 104 can be configured to provide access to network functions to multiple devices, such as base station 102, UE device 106 and / or UTM 108, for example, as further described herein.

[0108] In some implementations, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some implementations, server 104 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network.

[0109] As further described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. Processor 344 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 344 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in combination with one or more of other components 354, 364, and / or 374, processor 344 of server 104 may be configured to implement or support some or all of the features described herein.

[0110] Furthermore, as described herein, processor 344 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 344. Therefore, processor 344 may include one or more integrated circuits (ICs) configured to perform the functions of processor 344. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 344.

[0111] FIG. 4 : Block diagram of a UE

[0112] FIG. 4 An example simplified block diagram of a communication device 106 / 107 according to some embodiments is illustrated. Note that FIG. 4 The block diagram of the communication device is just one example of a possible communication device. The communication device 106 / 107 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., laptop, notebook, or portable computing device), a wearable device, a tablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or combinations of devices, among other devices, according to embodiments. As shown, the communication device 106 / 107 can include a set of components 400 configured to perform core functionality. For example, the set of components can be implemented as a system on a chip (SOC), which can include portions for various purposes. Alternatively, the set of components 400 can be implemented to be separate from or within one or more other components or groups of components for various purposes. The set of components 400 can be coupled (e.g., communicatively; directly or indirectly) to various other circuitry of the communication device 106.

[0113] For example, the communication device 106 / 107 can include various types of memory (e.g., including NAND flash 410), an input / output interface such as a connector I / F 420 (e.g., for connecting to a computer system; a dock; a charging station; an input device such as a microphone, camera, keyboard; an output device such as a speaker; etc.), a display 460 (which can be integrated with or external to the communication device 106 / 107), and wireless communication circuitry 430. The wireless communication circuitry 430 can include cellular modems 434 such as for 5G NR, LTE, etc., and short-to-medium range wireless communication logic 436 (e.g., Bluetooth ™ and WLAN circuitry). In some embodiments, the communication device 106 / 107 can include wired communication circuitry (not shown), such as a network interface card for Ethernet, for example.

[0114] The wireless communication circuitry 430 can be communicatively (e.g., directly or indirectly) coupled to one or more antennas, such as antennas 435a, 435b, and 435c (e.g., 435a-435c) as shown. The wireless communication circuitry 430 can include local area network (LAN) logic 432, cellular modem 434, and / or short-range communication logic 436. The LAN logic 432 can be used to enable the UE device 106 / 107 to perform LAN communications, such as Wi-Fi communications over an 802.11 network, and / or other WLAN communications. The short-range communication logic 436 can be used to enable the UE device 106 / 107 to perform communications according to a short-range RAT, such as Bluetooth or UWB communications. In some scenarios, the cellular modem 434 can be a lower-power cellular modem capable of performing cellular communications according to one or more cellular communication technologies.

[0115] In some embodiments, the cellular modem 434 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR), as described further below. Further, in some embodiments, the cellular modem 434 can include a single transmit chain that can be switched between radios dedicated to a particular RAT. For example, a first radio can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain as well as a transmit chain shared with additional radios, such as a second radio that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain as well as the shared transmit chain.

[0116] The communication device 106 / 107 can also include one or more user interface elements and / or be configured for use with one or more user interface elements. The user interface elements can include any of a variety of elements, such as a display 460 (which can be a touchscreen display), a keyboard (which can be a discrete keyboard or can be implemented as part of the touchscreen display), a mouse, a microphone, and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0117] The communication devices 106 / 107 can further include one or more smart cards 445 having SIM (Subscriber Identity Module) functionality, such as one or more UICC (Universal Integrated Circuit Card) cards 445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 / 107 can include at least two SIMs. Each SIM can execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM can be a single smart card, which can be embedded, e.g., soldered onto a circuit board in the UE 106 / 107, or each SIM 410 can be implemented as a removable smart card. Thus, a SIM can be one or more removable smart cards, such as UICC cards sometimes referred to as “SIM cards,” and / or a SIM 410 can be one or more embedded cards, such as embedded UICCs (eUICCs) sometimes referred to as “eSIMs” or “eSIM cards.” In some embodiments, such as when a SIM includes an eUICC, one or more of the SIMs can implement embedded SIM (eSIM) functionality; in such embodiments, a single one of the SIMs can execute multiple SIM applications. Each SIM can include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality can be stored in the memory and executed by the processor. In some embodiments, the UE 106 / 107 can include a combination of removable smart cards and fixed / non-removable smart cards, such as one or more eUICC cards implementing eSIM functionality, as needed. For example, the UE 106 / 107 can include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also contemplated.

[0118] As described above, in some embodiments, the UE 106 / 107 can include two or more SIMs. Including two or more SIMs in the UE 106 / 107 can allow the UE 106 / 107 to support two different phone numbers, and can allow the UE 106 / 107 to communicate on two or more corresponding respective networks. For example, a first SIM can support a first RAT such as LTE, and a second SIM 410 can support a second RAT such as 5G NR. Of course other implementations and RATs are possible. In some embodiments, when the UE 106 / 107 includes two SIMs, the UE 106 / 107 can support dual card dual active (DSDA) functionality. The DSDA functionality can allow the UE 106 / 107 to simultaneously connect to two networks (and use two different RATs), or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality can also allow the UE 106 / 107 to simultaneously receive a voice call or data traffic on either phone number. In certain embodiments, the voice call can be a packet-switched communication. In other words, the voice call can be received using Voice over LTE (VoLTE) technology and / or Voice over NR (VoNR) technology. In some embodiments, the UE 106 / 107 can support dual card dual standby (DSDS) functionality. The DSDS functionality can allow either of the two SIMs in the UE 106 / 107 to standby for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some embodiments, the DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that executes multiple SIM applications for different carriers and / or RATs.

[0119] As shown, the SOC 400 can include a processor 402, which can execute the program instructions of the communication device 106, and a display circuit 404, which can perform graphics processing and provide display signals to the display 460. The processor 402 can also be coupled to a memory management unit (MMU) 440, which can be configured to receive addresses from the processor 402 and translate those addresses to locations in memory (e.g., a memory 406, a read only memory (ROM) 450, a NAND flash memory 410), and / or to other circuits or devices, such as the display circuit 404, the short-to-medium range wireless communication circuit 429, the cellular communication circuit 430, the connector I / F 420, and / or the display 460. The MMU 440 can be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 can be included as a portion of the processor 402.

[0120] As described above, the communication device 106 can be configured to communicate using wireless and / or wired communication circuitry. The communication device 106 can be configured to perform the methods for reducing positioning reference signals (PRS) of devices for capacity as described further herein, for example, in 5G NR systems and beyond.

[0121] As described herein, the communication device 106 / 107 can include hardware and software components for implementing the above-described features of the communication device 106 / 107 to communicate a scheduling profile for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 402 of the communication device 106 / 107 can be configured to implement part or all of the features described herein. Alternatively (or in addition), the processor 402 can be configured as a programmable hardware element, such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or in addition) the processor 402 of the communication device 106, in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, can be configured to implement part or all of the features described herein.

[0122] Further, as described herein, the processor 402 can include one or more processing elements. Thus, the processor 402 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 402. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the one or more processors 402.

[0123] Further, as described herein, the cellular communication circuitry 430 and the short-to-medium range wireless communication circuitry 429 can each include one or more processing elements. In other words, one or more processing elements can be included in the cellular communication circuitry 430 and, similarly, one or more processing elements can be included in the short-to-medium range wireless communication circuitry 429. Thus, the cellular communication circuitry 430 can include one or more integrated circuits (ICs) that are configured to perform the functions of the cellular communication circuitry 430. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the cellular communication circuitry 430. Similarly, the short-to-medium range wireless communication circuitry 429 can include one or more ICs that are configured to perform the functions of the short-to-medium range wireless communication circuitry 429. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the short-to-medium range wireless communication circuitry 429.

[0124] FIG. 5 : block diagram of cellular communication circuit

[0125] FIG. 5 An example simplified block diagram of a cellular communication circuit is illustrated in accordance with some embodiments. Note that FIG. 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. The cellular communication circuit 530 (which can be a cellular modem circuit 434) can be included in a communication device, such as the communication devices 106 / 107 described above, in accordance with embodiments. As described above, the communication devices 106 / 107 can be user equipment (UE) devices, mobile devices or mobile stations, wireless devices or wireless stations, desktop or computing devices, mobile computing devices (e.g., laptops, notebooks, or portable computing devices), tablet computers, wearable devices, and / or combinations of devices, among other devices.

[0126] The cellular communication circuit 530 can be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 535a-535c (which can be the antennas 435a-435c in FIG. 4). In some embodiments, the cellular communication circuit 530 can include (and / or be coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components for multiple RATs) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown, the cellular communication circuit 530 can include modem 510 and modem 520. Modem 510 can be configured for communication in accordance with a first RAT (e.g., such as LTE or LTE-A), and modem 520 can be configured for communication in accordance with a second RAT (e.g., such as 5G NR). FIG. 4 FIG. 5

[0127] As shown, modem 510 can include one or more processors 512 and memory 516 in communication via bus 514. Modem 510 can be in communication with radio frequency (RF) front end 530. RF front end 530 can include circuitry to transmit and receive radio signals. For example, RF front end 530 can include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, receive circuitry 532 can be in communication with downlink (DL) front end 550, which can include circuitry to receive radio signals via antenna 535a.

[0128] ​​Similarly, modem 520 can include one or more processors 522 and memory 526 in communication via bus 524. Modem 520 can be in communication with RF front end 540. RF front end 540 can include circuitry to transmit and receive radio signals. For example, RF front end 540 can include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 can be in communication with DL front end 560, which can include circuitry to receive radio signals via antenna 535b.

[0129] In some embodiments, switch 570 can couple transmit circuitry 534 to uplink (UL) front end 572. In addition, switch 570 can couple transmit circuitry 544 to UL front end 572. UL front end 572 can include circuitry to transmit radio signals via antenna 535c. Thus, when cellular communication circuitry 530 receives instructions to transmit according to a first RAT (e.g., supported via modem 510), switch 570 can be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including transmit circuitry 534 and UL front end 572). Similarly, when cellular communication circuitry 530 receives instructions to transmit according to a second RAT (e.g., supported via modem 520), switch 570 can be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including transmit circuitry 544 and UL front end 572).

[0130] In some embodiments, cellular communication circuitry 530 can be configured to perform methods for reducing positioning reference signals (PRS) of devices for capacity as described further herein, e.g., in 5G NR systems and beyond.

[0131] As described herein, modem 510 can include hardware and software components for implementing the above-described features or for time-division multiplexing of UL data for NSA NR operation and various other techniques described herein. For example, processor 512 can be configured to implement parts or all of the features described herein by executing program instructions stored in a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 512 can be configured as programmable hardware elements, such as an FPGA (field programmable gate array) or as an ASIC (application specific integrated circuit). Alternatively (or in addition) the processor 512, in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 535a-535c can be configured to implement parts or all of the features described herein.

[0132] Further, as described herein, the processor 512 can include one or more processing elements. Thus, the processor 512 can include one or more integrated circuits (ICs) configured to perform the functions of the processor 512. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of the processor 512.

[0133] As described herein, the modem 520 can include hardware and software components for implementing the above features for positioning reference signals (PRS) for devices that reduce capacity, e.g., in 5G NR systems and beyond, as well as various other techniques described herein. The processor 522 can be configured to implement parts or all of the described features by executing program instructions stored in a memory medium, e.g., a non-transitory computer-readable memory medium. Alternatively (or in addition), the processor 522 can be configured as programmable hardware elements, such as by being programmed with one or more FPGAs. Alternatively (or in addition) the processor 522 can be configured as ASIC. Alternatively (or in addition) the processor 522 can be configured to implement portions or all of the described features in conjunction with one or more other components 540, 542, 544, 550, 570, 572, 535a-535c.

[0134] Further, as described herein, the processor 522 can include one or more processing elements. Thus, the processor 522 can include one or more integrated circuits (ICs) configured to perform the functions of the processor 522. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of the processor 522.

[0135] In-band non-collocated carrier aggregation

[0136] In recent years, in-band collocated carrier aggregation (CA) has been discussed and researched. More specifically, in in-band collocated CA, it has been assumed that transmit (Tx) antennas are collocated to ensure that a maximum receive timing difference (MRTD) of component carriers is less than a given threshold. However, in some instances, due to the spectrum range specified for in-band collocated CA operation, Tx antenna collocation can be cost-inefficient or infeasible. For example, due to a phased manner spectrum allocation can be associated with a frequency range of 3300-4200 MHz (as one example), there can not be enough space to collocate a later transmitted Tx antenna in a manner that collocates with an earlier transmitted Tx antenna.

[0137] However, in a non-collocated scenario, a larger received time difference value (RTD) between component carriers can be observed, which can correspond to a larger relative received time difference between two signals received on component carriers. Moreover, power imbalance between aggregated component carriers can increase compared to collocated CA. In view of this, in-band non-collocated CA techniques can be improved to provide beneficial enhancements. For example, it can be beneficial to describe a method for enhanced in-band non-collocated CA, such that degrading OFDM symbols (potentially due to CA) can be avoided and, thus, efficiency of CA in non-collocated scenarios can be improved. Therefore, a new type of scheduling and reporting strategy needs to be considered for enhancing support for in-band non-collocated CA.

[0138] In some scenarios, a component carrier (CC) from a base station (e.g., BS 102) can be aggregated with one or more other CCs from at least one other remote radio unit (RRU) or other base station to increase bandwidth. This aggregation of CCs can be referred to as non-collocated CA due to non-collocated antennas associated with the BS and the RRU. The CC from the base station and the CCs from one or more of the RRUs can belong to the same operating frequency band, such as 3300-4200 MHz. In this case, the aggregation of CCs can be referred to as in-band non-collocated CA.

[0139] Additionally, according to some embodiments, the CC from the BS 102 and the CCs from one or more of the RRUs can belong to different spectral blocks. For example, the CC from the base station 102 can belong to a spectral block in the frequency range 3900-4000 MHz. Moreover, the CCs from the RRUs can belong to one of the spectral blocks such as 3400-3440 MHz or 3560-3600 MHz. In the case of non-collocated CA, the power imbalance between the CCs supporting this CA can be as high as 25 decibels (dB). Additionally, the UE 106 can also observe a larger time difference of arrival.

[0140] Currently, in-band collocated requirements (e.g., minimum RF requirements in TS 38.101 and demodulation performance in TS 38.101) can be defined for a UE considering only a 6 dB power imbalance between aggregated carriers. Therefore, the 6 dB power imbalance can correspond to BS antennas that are very close (e.g., collocated). However, there can be no need to support in-band non-collocated CA (e.g., BS antennas that are not very close, which can be considered as non-collocated).

[0141] Accordingly, it can be desirable to provide methods for enhanced intra-band non-collocated CA scenarios. For example, one possible enhancement can include a UE sending capability information to a BS about the UE. The capability information can indicate a set of parameters that the UE supports for aggregation of non-collocated CCs. The BS can then activate, deactivate, or adjust scheduling of the non-collocated CCs based on the capability information. Accordingly, performance of non-collocated CA can be improved.

[0142] Additionally, intra-band CA can be a cost-effective improvement for operators if one or more antenna collocation conditions are relaxed. For example, in recent studies, at least two issues were observed with respect to intra-band non-collocated CA scenarios. First, a large power imbalance between component carriers (CCs) up to 25 dB was observed (as one approximate example). In addition, a large time difference of arrival between CCs was observed by a UE. For example, a maximum receive timing difference (MRTD) greater than 3 ps was observed (as one approximate example). Accordingly, new power imbalance and MRTD constraints considerations or requirements can be needed to enable methods of enhanced intra-band non-collocated CA. Moreover, new network configuration and physical (PHY) layer scheduling strategies can help maximize aggregated throughput in such scenarios.

[0143] Further, for scheduling purposes, it can be desirable to consider different types of UEs and report them to the network. For example, a Type 1 CA UE can support a power imbalance between aggregated CCs up to 6 dB, and support an MRTD less than or equal to 3 ps (as one example, and as described in existing minimum requirements in TS 38.133 and TS 38.101). As another example, a Type 2 CA UE can support a 25 dB power imbalance between aggregated CCs and an MRTD less than or equal to 33 ps (as one example and as described in new RF and minimum requirements in TS 38.133 and TS 38.101). According to some scenarios involving Type 1 and Type 2 UEs, up to two MIMO layers can be supported on each CC.

[0144] Alternatively, a Type 3 UE can support a larger power imbalance between aggregated CCs and MRTD between 3 ps and 33 ps (as one example and as discussed in new RF and minimum requirements in TS 38.133 and TS 38.101). Further, according to some scenarios involving Type 3 UEs, up to four MIMO layers can be supported on each CC. In some embodiments, depending on the capabilities, a Type 3 UE can also be able to fall back to operate as a Type 2 UE.

[0145] Additionally, for Type 3 UEs, it can be beneficial to constrain the MRTD such that it is greater than the cyclic prefix (CP) (e.g., to remain within the CP). While this can limit network deployment in some aspects, it can be desirable to keep the MRTD greater than the CP from a feature success perspective. Thus, to maintain MRTD greater than the CP, it can be desirable to have RTD reporting with appropriate periodicity. More specifically, when a UE measures an RTD less than a parameter X μs (e.g., a specified MRTD), the network can determine to schedule PDSCH signaling for Type 3a / 3b UEs. According to some embodiments, the comparison such as the value of RTD < X μs should be substantially less than the OFDM symbol time. In other words, the measured RTD and / or the specified MRTD (e.g., the parameter "X") should be substantially less than the OFDM symbol time scale.

[0146] Additionally, it should be allowed to degrade to the first OFDM symbol (e.g., symO) or the last OFDM symbol (e.g., sym13). For example, it can be beneficial to protect the OFDM symbols of a preferred or more efficient CC (e.g., a CC with higher RSRP, RSRQ, etc.) over a less desirable or less efficient CC (e.g., a CC with lower RSRP, RSRQ, etc.) and allow the OFDM symbols of the latter to degrade / destroy while maintaining higher efficiency or fidelity on the protected CC. In some embodiments, the OFDM symbols affected (e.g., degraded / destroyed) can depend on the relative RTD between the two carriers. Thus, it can be beneficial to describe a method for enhanced intra-band non-collocated CA such that the degraded OFDM symbols can be avoided, thereby improving the efficiency of CA in non-collocated scenarios.

[0147] FIG. 6 - method for enhanced in-band non-contiguous carrier aggregation

[0148] FIG. 6 A communication flow diagram is illustrated for an example method for enhanced non-collocated carrier aggregation according to some embodiments. More specifically, FIG. 6 A communication flow diagram is illustrated for an example method for enhanced non-collocated carrier aggregation according to some embodiments. More specifically, FIG. 6Aspects of the method of FIG. 10 can be implemented by a wireless device such as a UE 106, for example, communicating with a network via one or more base stations (e.g., BS 102), as shown in and described with respect to the FIGs., or more generally in combination with any of the computer systems or devices shown in the FIGs. and other circuits, systems, devices, elements, or FIG. 6 Aspects of the method of FIG. 10 can be implemented by a network node such as a BS 102, for example, communicating with a UE 106, as shown in and described with respect to the FIGs., or more generally in combination with any of the computer systems or devices shown in the FIGs. and other circuits, systems, devices, elements, or components shown in the FIGs. and other devices, as desired. For example, one or more processors (or processing elements) of a UE (e.g., processor 302, a baseband processor, a processor associated with communication circuitry, etc., among various possibilities) can cause the UE to perform some or all of the illustrated method elements. For example, one or more processors (or processing elements) of a BS (e.g., processor 404, a baseband processor, a processor associated with communication circuitry, etc.) can cause the BS to perform some or all of the illustrated method elements. In some embodiments, the UE can communicate directly with the base station, and the base station can in turn communicate with an access mobility function (AMF) of a 5GC serving a PLMN associated with a terrestrial network (TN). Note that while at least some elements of the method are described using terminology related to the use of communication techniques and / or features associated with 3GPP specification documents, such description is not intended to limit the present disclosure, and aspects of the method can be used in any suitable wireless communication system, as desired. In various embodiments, some of the illustrated elements of the method can be performed simultaneously, can be executed in a different order than illustrated, can be substituted with other method elements, or can be omitted, as desired. Additional method elements can also be executed as desired. As shown, the method can operate as follows.

[0149] At 602, the UE can establish a cellular link with a network node (e.g., a BS), according to some embodiments. Additionally or alternatively, the cellular link can operate according to 5G NR. For example, the wireless device can establish a session with an AMF entity of a cellular network through one or more gNBs providing radio access to the cellular network. As another possibility, the cellular link can operate according to LTE. For example, the wireless device can establish a session with a mobility management entity of a cellular network through an eNB providing radio access to the cellular network. According to various embodiments, other types of cellular links are possible, and the cellular network can also or alternatively operate according to another cellular communication technology (e.g., UMTS, etc.).

[0150] Establishing the wireless link can include establishing an RRC connection with the serving cellular base station in accordance with at least some embodiments. Establishing the first RRC connection can include configuring various parameters for communicating between the wireless device and the cellular base station, establishing environmental information for the wireless device, and / or any of various other possible features, e.g., involving establishing an air interface for the wireless device for cellular communication with a cellular network associated with the cellular base station. After establishing the RRC connection, the wireless device can operate in an RRC connected state. In some instances, the RRC connection can also be released (e.g., after a period of inactivity with respect to data communication), in which case the wireless device can operate in an RRC idle state or an RRC inactive state. In some instances, the wireless device can perform a handover (e.g., when in an RRC connected mode) or a cell reselection (e.g., when in an RRC idle mode or an RRC inactive mode) to a new serving cell, e.g., due to wireless device mobility, changing wireless medium conditions, and / or any of various other possible reasons.

[0151] At 604, the UE can send capability information to the network node in accordance with some embodiments. More specifically, the UE can send signaling to the network including capability information indicating support for CA of the first CC and the second CC. As previously discussed, for intra-band non-collocated CA, a larger RTD between the aggregated component carriers can be observed due to the increased spacing of the antennas compared to collocated antennas. Further, the power imbalance between the component carriers to be aggregated can be significantly larger than the power imbalance related to collocated CCs. These two parameters can be important aspects in the scenario of intra-band non-collocated CA. Thus, if the UE is not capable of supporting the RTD and / or the power imbalance, the non-collocated CA can not be guaranteed even if it is scheduled by the network device. Thus, the network device can need to know the UE's capability with respect to non-collocated CA when performing CA scheduling. Thus, it can be beneficial for the UE to indicate to the network whether the UE is capable of supporting carrier aggregation with a particular RTD and / or a particular power imbalance level.

[0152] According to some embodiments, the capability information can include a UE capability parameter "intraBandNonColocatedCADL-r18" that can indicate that the UE 106 supports a first set of parameters and / or a second set of parameters for aggregation of non-colocated CCs. According to some embodiments, the capability information can indicate a capability to support a maximum RTD between aggregated component carriers that is no less than a predetermined RTD threshold. Additionally or alternatively, the capability information can indicate a capability to support a maximum power imbalance between aggregated component carriers that is no less than a predetermined power imbalance threshold. In some embodiments, the capability information can indicate that at least one component carrier supports up to four MIMO layers. In some embodiments, in addition to reporting a capability to support intra-band non-colocated CA, the UE can report or include in the report an indication of a capability to be compatible with legacy types of carrier aggregation (e.g., supported by Type 1 or Type 2 UEs).

[0153] At 606, according to some embodiments, the UE can receive downlink signaling on the plurality of CCs. More specifically, the UE can receive physical downlink shared channel (PDSCH) signaling on the first CC and the second CC from the network node. For example, the PDSCH signaling can be received on the first component carrier and the second component carrier via respective OFDM symbols (e.g., from number 0 (sym0) to 13 (sym13)) in a slot. As briefly mentioned with respect to the scenario of intra-band non-colocated carrier aggregation of multiple component carriers, according to some embodiments, certain OFDM symbols can be degraded in the course of carrier aggregation.

[0154] According to some examples, the UE can further determine an alignment of a shared low noise amplifier (LNA) with the first CC or the second CC. More specifically, the UE can determine which of the first CC or the second CC is "protected" or "locked." For example, to perform RTD measurements, the UE can need to determine which carrier (e.g., the first carrier or the second carrier) to utilize to designate a reference point from which to measure the RTD. In other words, the UE can need to determine or align a CC (associated with the reference point) based on which to measure the RTD between it (e.g., the determined or selected / aligned CC) and the other CC. As one example, if the UE determines to use a reference point associated with the first CC, it can determine that the first OFDM symbol (e.g., sym0) of the first CC is protected, whereas the sym0 of the second CC (e.g., unprotected or unaligned) can be affected by degradation or corruption. Alternatively, according to some embodiments, if the UE determines to use a reference point associated with the second CC, the OFDM sym0 of the second CC can be protected, whereas the sym0 of the first CC can be degraded / corrupted.

[0155] Additionally, determining which CC to protect or align with (e.g., selecting which CC and associating with a measurement reference point) can be based on one or more reference signal received power (RSRP) metrics, one or more reference signal received quality (RSRQ) metrics, one or more maximum average aggregate throughput metrics associated with the first CC and / or the second CC. In some embodiments, the determination can be based on which of the first CC or the second CC is associated with a primary cell (PCell). In some embodiments, once the UE has made a determination as to which carrier the shared LNA will align with (e.g., which carrier will be protected), the UE can send an indication of the determination to the network so that the network can schedule and / or adjust subsequent PDSCH signaling according to the indicated determination.

[0156] Additionally or alternatively, the determination of which carrier to protect can be based on an indication received by the UE from a network node. For example, according to some embodiments, after receiving the RTD report from the UE, the network can make a determination as to which carrier the shared LNA will align with (e.g., which carrier will be protected). In some embodiments, the determination of which carrier to protect by the network can be based on a similar or identical formula, inequality, or metric as used by the UE. Thus, the network can schedule and / or adjust subsequent PDSCH signaling according to the indicated determination.

[0157] In 608, according to some embodiments, the UE can measure the RTD between the CCs. More specifically, the UE can measure the RTD between the start of the first orthogonal frequency-division multiplexing (OFDM) symbol in the first slot of the first CC and the start of the first OFDM symbol in the first slot of the second CC. Alternatively, the UE can measure the RTD between the start of the first OFDM symbol in the first slot of the first CC and the end of the last OFDM symbol in the previous slot of the second CC. In some embodiments, the UE can measure a negative delay corresponding to a negative RTD (-RTD). For example, if the UE measures the RTD between the start of sym0 of the first CC and the start of the first OFDM symbol in the slot of the second CC (e.g., the start of sym0 of the second CC), the RTD can be considered a negative RTD relative to the reference point associated with the first CC. Alternatively, according to some embodiments, the UE can measure a positive RTD (+RTD). For example, if the UE measures the RTD between the start of sym0 of the first CC and the end of the last OFDM symbol in the previous slot of the second CC (e.g., the end of the leftmost sym13 of the second CC), the RTD can be considered a positive RTD relative to the reference point associated with the first CC.

[0158] In some embodiments, the UE can determine a degraded OFDM symbol on the first CC or the second CC based on the measured RTD. Additionally or alternatively, the UE can determine that the degraded OFDM symbol is to be excluded in subsequent downlink signaling received from the network. Further, the UE can determine that the degraded OFDM symbol is corrupted due to a phase jump when no analog gain change occurs at the beginning of at least one of the first CC or the second CC.

[0159] At 610, the UE can transmit an RTD report to the network, according to some embodiments. More specifically, the UE can transmit a report including the measured RTD to the network node. According to some embodiments, the report can include the -RTD measurement value or the +RTD measurement value. As an alternative, according to some embodiments, the UE can report to the network only whether the measured RTD is greater than a predetermined RTD threshold, instead of reporting the measured RTD and saving signaling overhead. In other words, according to some embodiments, the UE can perform a comparison or calculation related to the measured RTD value and one or more specified parameters (e.g., MRTD, CP, "X" μs, etc.).

[0160] At 612, the network can compare the measured RTD to a signaling metric, according to some embodiments. More specifically, the network can compare the measured RTD to one or more signaling metrics associated with the first CC and the second CC. In some embodiments, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the measured RTD is less than a cyclic prefix (CP) that is less than X microseconds (μs), where X is a value that can correspond to a maximum receive timing difference (MRTD). Additionally or alternatively, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the CP is less than the measured RTD that is less than X μs. In some embodiments, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the measured RTD is greater than X μs. In other words, the network can determine that the measured RTD is not less than a predetermined RTD threshold corresponding to enhanced intra-band non-contiguous CA. Thus, according to some embodiments, if the condition is satisfied, this can indicate that the CA is usable based on the current network environment. According to some embodiments, the network node can further indicate the one or more signaling metrics to the UE so that the UE can perform similar comparisons or calculations related to the intra-band non-contiguous CA.

[0161] In some embodiments, in response to determining that the measured RTD is greater than a predetermined RTD threshold for Type 3 CA when reporting capabilities compatible with legacy types of CA, the network node can schedule a legacy type of CA. For example, the network node can activate a non-collocated component carrier of Type 2 CA and schedule two MIMO layers on that component carrier. Thus, scheduling can be performed for Type 3 CA or fall back to a legacy type of CA (e.g., Type 2 CA) based on different network environments. Thus, scheduling can be dynamically changed according to network environments.

[0162] As described above, the network node can perform CA scheduling based on the measured RTD from the UE. However, according to other embodiments, the network node can perform CA scheduling based on a maximum RTD rather than the measured RTD from the wireless device. More specifically, in some embodiments, the network node can determine the maximum RTD based on a network deployment related to the network node. For example, the maximum RTD can be determined based on historical reporting of measured RTDs of a plurality of UEs or wireless devices within the network environment. Alternatively, the maximum RTD can be determined based on other parameters of the network deployment. Thus, according to some embodiments, in response to determining that the maximum RTD is not less than a predetermined RTD threshold, the network node can schedule a new type of CA.

[0163] In 614, according to some embodiments, the UE can receive downlink signaling including adjusted OFDM symbols from the network. More specifically, the UE can receive first downlink signaling (e.g., downlink control information (DCI), PDSCH, PDCCH, etc.) on a first CC and second downlink signaling on a second CC from the network node. In some embodiments, one of the first or second DL signaling can include a set of adjusted OFDM symbols. Additionally or alternatively, the set of adjusted OFDM symbols can be adjusted based at least in part on the measured RTD such that a degraded OFDM symbol associated with one of the CCs (e.g., the first or second CC) is avoided. In other words, adjusting the OFDM symbols can correspond to a mapping of PDCCH (as one example) to a different set of OFDM symbols and RBs such that a degraded OFDM symbol and RB can be avoided.

[0164] For example, in some embodiments, if the measured RTD is less than the CP, which is less than the maximum RTD parameter “X” ps, the adjusted downlink signaling can be scheduled such that it uses the available symbols in the time slot (e.g., ranging from sym0 - sym13). Additionally or alternatively, if the CP is less than the measured RTD, which is less than “X” ps, the adjusted downlink signaling can be adjusted such that it uses the sym1 - sym13 range or the sym0 - sym12 range (e.g., excluding the first symbol or the last symbol in the time slot of one of the CCs). In some embodiments, if the measured RTD is greater than “X” ps, the network can determine to avoid scheduling the adjusted PDSCH signaling. In other words, the adjusted downlink signaling can occupy a reduced number of OFDM symbols on the first CC or the second CC based on the comparison of the measured RTD to various signaling metric inequalities to avoid a degraded OFDM symbol.

[0165] More specifically, if degradation to the first OFDM symbol sym0 or the last OFDM symbol sym13 is allowed (e.g., as indicated by the UE capability response), the network can be able to use dynamic downlink scheduling to avoid the degraded OFDM symbol. Thus, the network can also need to configure at least one control resource set (CORESET) located between sym1 and sym12 for receiving a physical downlink control channel (PDCCH). Additionally, a channel state information reference signal (CSI-RS) and / or a tracking reference signal (TRS) should not occupy the OFDM symbol that can be degraded, such as sym0 or sym13. However, since a synchronization signal block (SSB) and a physical broadcast channel resource (PBCH) do not occupy sym0 or sym13, they should not be affected by the above degradation of sym0 or sym13.

[0166] According to some embodiments, a network node can transmit a measurement object (MO) to a UE, which can indicate a non-collocated frequency to be aggregated with a serving frequency of the UE. The non-collocated frequency can correspond to the second component carrier described above (e.g., CC2), and the serving frequency can correspond to the first component carrier described above (e.g., CC1). Further, according to some embodiments, the network node can indicate the non-collocated frequency to the UE by other means than the MO.

[0167] In some embodiments, the measured RTD can be less than or equal to a maximum receive timing difference (MRTD), and the MRTD can be greater than a cyclic prefix (CP). Thus, the UE can be able to support increased power imbalance between the first CC and the second CC when the measured RTD is less than or equal to the MRTD. According to further embodiments, the reduced number of OFDM symbols can exclude a degraded OFDM symbol on the first CC or the second CC, and the degraded OFDM symbol can be corrupted due to a phase jump when no analog gain change occurs at the beginning of a slot of the first CC or the second CC. In some embodiments, the method can be performed by a Type 3a user equipment (UE) or a Type 3b UE. According to further embodiments, up to four multiple-input multiple-output (MIMO) layers can be supported on the first CC and / or the second CC.

[0168] The embodiments described above can be suitably applied to a new radio (NR) network architecture. Further, according to some embodiments, for a dual connectivity network architecture in which a legacy network (e.g., LTE) and NR are connected, the capability to support a new type of carrier aggregation can include at least one component carrier for the legacy network supporting up to two MIMO layers, and at least one component carrier for the NR supporting up to four MIMO layers. Additionally or alternatively, scheduling the new type of carrier aggregation can include scheduling two MIMO layers on the at least one component carrier for the legacy network, and scheduling four MIMO layers on the at least one component carrier for the NR. In the case of dual connectivity, a first component carrier can correspond to a component carrier for the legacy network, and a second component carrier can correspond to a component carrier for the NR, or vice versa. Further, the dual connectivity can include, but is not limited to, EN-DC (Evolved Universal Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity).

[0169] FIG. 7A to FIG. 7B - relative time difference measurement in enhanced in-band non-contiguous carrier aggregation

[0170] FIG. 7A And FIG. 7B Exemplary aspects of enhanced non-collocated carrier aggregation including relative time difference measurements are illustrated in accordance with some embodiments. More specifically, FIG. 7A And 7B Exemplary component carriers CC1 and CC2, and respective OFDM symbols in a slot (e.g., numbered from 0 (sym0) to 13 (sym13)) of downlink signaling received at a UE from a network are illustrated. As previously discussed, according to some embodiments, in the context of in-band non-collocated carrier aggregation of CC1 and CC2, certain OFDM symbols can be degraded during the carrier aggregation process.

[0171] And FIG. 6 related to at least a portion of the method described inFIG. 7A A negative RTD (-RTD) measurement with respect to reference point A is illustrated. In some embodiments, reference point A can correspond to the start of the first Orthogonal Frequency-Division Multiplexing (OFDM) symbol in the first (e.g., current) slot of the first CC (e.g., the start of symO of CC1). Thus, when the UE measures the RTD between the start of symO of CC1 and the start of the first OFDM symbol in the first (e.g., current) slot of the second CC (e.g., the start of symO of CC2), the RTD can be considered a -RTD with respect to reference point A. In other words, FIG. 7A A first case corresponding to a negative delay (e.g., -RTD) between component carriers is illustrated. According to some embodiments, point A can correspond to a reference point associated with CC1, and thus CC1 can be considered “protected” or “locked.” In other words, according to some embodiments, because the UE is using reference point A associated with CC1, it can determine that the first OFDM symbol (e.g., symO) of the selected CC1 is protected, while the symO of CC2 can be subject to degradation or corruption. Alternatively, according to some embodiments, if reference point A is associated with CC2, the OFDM symO of CC2 can be protected, while the symO of CC1 can be degraded / corrupted.

[0172] Also related to at least a portion of the method described in FIG. 6 FIG. 7B A positive RTD (+RTD) measurement with respect to reference point A is illustrated. Similar to FIG. 7A , reference point A can correspond to the start of symO of CC1, and the UE can measure the RTD between the start of symO of CC1 and the end of the last OFDM symbol in a previous slot of the second CC (e.g., the leftmost sym13 of CC2). Thus, when the UE measures the RTD between the start of symO of CC1 and the end of the last OFDM symbol in a previous slot of the second CC (e.g., the end of the leftmost sym13 of CC2), the RTD can be considered a +RTD with respect to reference point A. In other words, FIG. 9B ​A second case corresponding to a positive delay (e.g., +RTD) between component carriers is illustrated. According to some embodiments, point A can correspond to a reference point associated with CC1, and thus CC1 can be considered to be “protected” or “locked.” In other words, according to some embodiments, because the UE is using reference point A associated with CC1, the UE can determine to protect the first OFDM symbol (e.g., sym0) of the selected CC1, while the leftmost sym13 of CC2 (e.g., from a previous time slot) can be affected by degradation or corruption. Alternatively, according to some embodiments, if reference point A is associated with CC2, then the leftmost OFDM sym13 of CC2 can be protected, while sym0 of CC1 can be degraded / corrupted.

[0173] As noted above, the UE’s measurement of RTD can depend on a reference point A, which can correspond to a carrier that is “locked” or “protected.” This determination or selection of which component carrier is protected can be based on a policy. For example, according to some embodiments, a policy can be utilized to select which carrier will be used to indicate the reference point A. In other words, a carrier alignment policy can be used to indicate which carrier is protected and used as the reference for “point A.” Thus, another carrier (e.g., unprotected) can be indicated as the carrier affected by OFDM symbol degradation / corruption. As briefly mentioned, when the analog gain change of a shared low noise amplifier (LNA) of a collocated antenna does not start exactly at the beginning of a time slot, degradation or corruption can be due to a phase jump.

[0174] According to some embodiments, the UE can decide or determine which carrier the shared LNA will be aligned to (e.g., which carrier is protected). For example, the UE can make this determination or selection based on RSRP, RSRQ, or other signal-based metrics, maximum average aggregated throughput, or the UE can always align to a carrier associated with a primary cell (PCell) rather than a secondary cell. Alternatively, in some embodiments, the network can indicate to the UE which carrier the shared LNA should be aligned to.

[0175] FIG. 8 to FIG. 10 - Dynamic PDSCH scheduling techniques

[0176] FIGS. 8-10 illustrate exemplary aspects of enhanced non-collocated carrier aggregation related to dynamic PDSCH scheduling, according to some embodiments. More specifically, FIGS. 8-10 illustrate potential mappings of PDCCH and CORESET (as one example, for receiving PDCCH) across carrier resource blocks (RBs) relative to their respective time slots, according to some embodiments. Additionally, FIGS. 8-10 illustrate mappings of PDSCH demodulation reference signals (DM-RS) across subcarriers relative to their respective symbols (syms), according to some embodiments.

[0177] For example, according to some embodiments, FIG. 8A to FIG. 8B A first case or scenario for dynamic PDSCH scheduling is illustrated in a case where a degradation to a first OFDM symbol (e.g., sym0) or a degradation to a last OFDM symbol (sym13) is allowed and a measured RTD is less than a CP (which is less than a maximum RTD parameter “X” ps). FIG. 8A Example configurations of PDCCH and CORESET across carrier RBs with respect to their respective slots are illustrated. More specifically, FIG. 8A Examples of how a plurality of PDCCH and CORESET for a plurality of slots can be configured for carrier RBs are illustrated for both a first component carrier and a second component carrier (e.g., CC1 and CC2) and corresponding to a first BWP (e.g., BWP 1) and a subcarrier spacing (SCS) of 30 kHz. For example, FIG. 8A Two PDCCH associated with a first slot (e.g., between slots 0 and 1) configured for a portion of RBs between 0 and 50 and a portion of RBs between 100 and 150 are illustrated according to some embodiments. Additionally, FIG. 8A Two PDCCH associated with a second slot (e.g., between slots 1 and 2) configured for a portion of RBs around RB 100 and a portion of RBs at or around RB 0 are illustrated according to some embodiments. Additionally, FIG. 8A CORESET for the first slot and the second slot can be configured for RBs at least from 0 to about RB 200. Thus, in other words, at least one CORESET can be configured between sym1 and sym12 for PDCCH according to some embodiments. Additionally, FIG. 8A Examples of how a physical downlink shared channel (PDSCH) can be configured with respect to slots for carrier RBs are illustrated according to some embodiments.

[0178] FIG. 8B A first case or scenario (also corresponding to FIG. 8A Mapping of PDSCH DM-RS across subcarriers with respect to their respective symbols is illustrated according to some embodiments. More specifically, FIG. 8B Examples of how a plurality of PDSCH DM-RS and their respective symbols can be configured across subcarriers are illustrated for both a first component carrier and a second component carrier (e.g., CC1 and CC2). For example, FIG. 8B A first PDSCH DM-RS associated with a third symbol (e.g., sym2, ranging from sym2 to sym3) of a slot configured across subcarriers 0 to 12 is illustrated according to some embodiments. Additionally, FIG. 8BA second PDSCH DM-RS associated with an eleventh symbol (e.g., sym12, ranging from the eleventh symbol to the twelfth symbol) of a slot configured across subcarriers 0 to 12 is illustrated in accordance with some embodiments. Thus, in this first case, the adjusted downlink signaling can be scheduled such that it can use the available symbols in the slot (e.g., ranging from sym0-sym13). Accordingly, and as briefly discussed above, in accordance with some embodiments, FIG. 8A and FIG. 8B both CC1 and CC2 would apply (e.g., accurately describe) in scenarios where a degradation to the first OFDM symbol (e.g., sym0) or a degradation to the last OFDM symbol (sym13) is allowed and the measured RTD is less than the CP (which is less than the maximum RTD parameter “X” μs).

[0179] Additionally, FIG. 8B An example of how a PDSCH can be configured with respect to subcarriers and symbols in accordance with some embodiments is illustrated.

[0180] In accordance with some embodiments, FIG. 9A to FIG. 9B A second case or scenario for dynamic PDSCH scheduling in cases where a degradation to the first OFDM symbol (e.g., sym0) or a degradation to the last OFDM symbol (sym13) is allowed and the CP is less than the measured RTD (which is less than the maximum RTD parameter “X” μs) is illustrated. More specifically, FIG. 9A Adjusted downlink signaling of an interfered object CC (as opposed to a protected CC such as CC1) is illustrated that is adjusted such that it uses the sym1-sym13 range (e.g., excluding the first symbol in the slot of the interfered object CC). In other words, based on a comparison of the measured RTD to various signaling metric inequalities, the adjusted downlink signaling of the interfered object CC (e.g., CC2) can be occupied or configured with a reduced number of OFDM symbols (as opposed to what can be occupied or configured by FIG. 8A and FIG. 8B a protected CC1), to avoid the degraded OFDM symbol.

[0181] Thus, and in relation to the second case or scenario where the CP is less than the measured RTD (which is less than the maximum RTD parameter “X” μs), FIG. 9A An example configuration of PDCCH and CORESET across a carrier RB with respect to their respective slots is illustrated. More specifically, FIG. 9AAn example is illustrated of how a plurality of PDCCH and CORESETs for a plurality of slots can be configured for a carrier RB for an interfered object component carrier (e.g., CC2) and corresponding to a first BWP (e.g., BWP 1) and a subcarrier spacing (SCS) of 30 kHz. For example, FIG. 9A An example is illustrated of two PDCCHs associated with a first slot (e.g., between slots 0 and 1) configured for a portion of RBs between 0 and 50 and a portion of RBs between 100 and 150, according to some embodiments. Additionally, FIG. 9A An example is illustrated of two PDCCHs associated with a second slot (e.g., between slots 1 and 2) configured for a portion of RBs around RB 100 and a portion of RBs at or around RB 0, according to some embodiments. Moreover, FIG. 9A An example is illustrated of a CORESET for the first slot and the second slot can be configured for RBs at least from 0 to about RB 200. Importantly, according to some embodiments, since the adjusted downlink signaling for this interfered object CC is adjusted such that it uses the sym1-sym13 range (e.g., excluding the first symbol in the slot of the interfered object CC), thus FIG. 9A An example is illustrated of carrier RBs from 0 to about 250 associated with the first symbol in a slot can correspond to unused or avoided RBs associated with the degraded first symbol (e.g., sym0) in the first slot and the second slot of the interfered object CC. Additionally, FIG. 9A An example is illustrated of how a PDSCH can be configured with respect to a slot relative to carrier RBs, according to some embodiments.

[0182] FIG. 9B An example is illustrated of a first PDSCH DM-RS associated with a third symbol (e.g., sym2, ranging from sym2 to sym3) of a slot configured across subcarriers 0 to 12, according to some embodiments. Additionally, FIG. 9B An example is illustrated of a second PDSCH DM-RS associated with an eleventh symbol (e.g., sym 12, ranging from sym11 to sym 12) of a slot configured across subcarriers 0 to 12, according to some embodiments. Thus, according to some embodiments, in this second scenario or case where the CP is less than the measured RTD (which is less than the maximum RTD parameter “X” ps), FIG. 9B An example is illustrated of an unused or avoided first symbol across subcarriers 0 to 12 corresponding to the first symbol (e.g., sym0) associated with the degraded OFDM symbol of the interfered object CC (e.g., CC2). Additionally, while FIG. 9A and FIG. 9BConfiguration of the interfered object carrier CC2 is described, as briefly discussed above, but in accordance with some embodiments, FIG. 8A and FIG. 8B will apply (e.g., accurately describe) to the protected carrier (e.g., CC1) in this second scenario. Moreover, FIG. 9B An example is illustrated of how PDSCH can be configured with respect to subcarriers and symbols in accordance with some embodiments. In other words, FIG. 9A to FIG. 9B An example is illustrated of a technique for dynamic PDSCH scheduling in which the first symbol (e.g., sym0) in a slot is avoided or unused, which results in a reduced or fewer number of symbols (e.g., 13 instead of 14) for the scheduled PDSCH.

[0183] FIG. 10A to FIG. 10B A secondary aspect is illustrated related to the second case or scenario described in FIG. 9A to FIG. 9B In accordance with some embodiments, for example, FIG. 10A to FIG. 10B An auxiliary scenario is illustrated for dynamic PDSCH scheduling in the case where a degradation to the first OFDM symbol (e.g., sym0) or a degradation to the last OFDM symbol (sym13) is allowed and the CP is less than the measured RTD, which is less than the maximum RTD parameter “X” ps. More specifically, FIG. 10A Adjusted downlink signaling of the interfered object CC (as opposed to the protected CC such as CC1) is illustrated that is adjusted such that it uses the sym0-sym12 range (e.g., excluding the last symbol in the slot of the interfered object CC). In other words, based on the comparison of the measured RTD to the various signaling metric inequalities, the adjusted downlink signaling of the interfered object CC (e.g., CC2) can be occupied or configured with a reduced number of OFDM symbols (as opposed to what can be occupied or configured by FIG. 8A and FIG. 8B the protected CC1), to avoid the degraded OFDM symbol.

[0184] Accordingly, and related to the second case or scenario in which the CP is less than the measured RTD, which is less than the maximum RTD parameter “X” ps, FIG. 10A An example configuration of PDCCH and CORESET across carrier RBs with respect to their respective slots is illustrated. More specifically, FIG. 10A An example is illustrated of how multiple PDCCH and CORESET for multiple slots can be configured for a carrier RB for an interfered object component carrier (e.g., CC2) and corresponding to a first BWP (e.g., BWP 1) and a subcarrier spacing (SCS) of 30 kHz. For example, FIG. 10ATwo PDCCHs associated with a first slot (e.g., between slots 0 and 1) configured for a portion of RBs between 0 and 50 and a portion of RBs between 100 and 150 are illustrated in accordance with some embodiments. Additionally, FIG. 10A Two PDCCHs associated with a second slot (e.g., between slots 1 and 2) configured for a portion of RBs around RB 100 and a portion of RBs at or around RB 0 are illustrated in accordance with some embodiments. Moreover, FIG. 10A CORESETs for the first and second slots can be configured for RBs at least from 0 to about RB 200 in accordance with some embodiments. Importantly, since the adjusted downlink signaling for the interfered object CC is adjusted such that it uses the sym0-sym12 range (e.g., excluding the last symbol in the slot of the interfered object CC) in accordance with some embodiments, FIG. 10A It is also illustrated that carrier RBs from 0 to about 250 can correspond to RBs that are unused or avoided due to their association with the degraded OFDM last symbol (e.g., sym13) in the first and second slots of the interfered object CC. Additionally, FIG. 10A An example of how a PDSCH can be configured with respect to slots relative to carrier RBs is illustrated in accordance with some embodiments.

[0185] FIG. 10B A first PDSCH DM-RS associated with a third symbol (e.g., sym2, range sym2 to sym3) of a slot configured across subcarriers 0 to 12 is illustrated in accordance with some embodiments. Additionally, FIG. 10B A second PDSCH DM-RS associated with an eleventh symbol (e.g., sym 12, range sym11 to sym12) of a slot configured across subcarriers 0 to 12 is illustrated in accordance with some embodiments. Thus, in this secondary scenario related to a case where the CP is less than the measured RTD (which is less than the maximum RTD parameter “X” μs), FIG. 10B An unused or avoided symbol (e.g., last symbol) across subcarriers 0 to 12 corresponding to the last symbol (e.g., sym13, range thirteenth symbol to fourteenth symbol) associated with the interfered object CC (e.g., CC2) is illustrated in accordance with some embodiments. Additionally, and as briefly discussed above, in accordance with some embodiments, FIG. 8A And FIG. 8B The protected carrier (e.g., CC1) in this secondary scenario will apply (e.g., be accurately described). Moreover, FIG. 10B An example of how a PDSCH can be configured with respect to symbols relative to subcarriers is illustrated in accordance with some embodiments. In other words,FIG. 10A to FIG. 10B Techniques are illustrated for dynamic PDSCH scheduling where the last symbol in a slot (e.g., sym13) is avoided or unused, which results in a reduced or fewer number of symbols for a scheduled PDSCH (e.g., 13 instead of 14).

[0186] Additional information

[0187] According to some embodiments related to intra-band non-collocated CA, the UE capability parameter “intraBandNonColocatedCADL-r18” can indicate that the UE supports intra-band / inter-band non-collocated CA operation for frequency division duplex (FDD)-FDD or time division duplex (TDD)-TDD with additional requirements (discussed in TS 38.101 together with demodulation requirements) and can support MRTD < 33 ps according to TS 38.133. (e.g., Type 2 UE).

[0188] According to some embodiments, if the capability is not reported, the UE can support FDD-FDD or TDD-TDD intra-band / inter-band operation with MRTD < 3 ps (e.g., Type 1 UE). In some embodiments, the UE capability parameter “intraBandNonColocatedCADL-r18” can indicate the level including associated parameters and can be signaled per band combination.

[0189] In some embodiments, if there is no UE capability parameter “intraBandNonColocatedCADL-r18” in the capability information, this can indicate that the UE 106 supports a first set of parameters for aggregation of non-collocated CCs. For example, the set of parameters for aggregation of non-collocated CCs can include a first set of parameters for aggregation of non-collocated CCs. The first set can include a first threshold for power imbalance between non-collocated CCs and a second threshold for maximum receive time difference (MRTD) between non-collocated CCs. In some embodiments, the first threshold for power imbalance can be equal to 6 dB and the second threshold for MRTD can be equal to 3 ps.

[0190] Alternatively, in some embodiments, the set of parameters for aggregation of non-collocated CCs can include a second set of parameters for aggregation of non-collocated CCs. The second set includes a third threshold for power imbalance and a fourth threshold for MRTD. The third threshold can be higher than the first threshold and the fourth threshold can be higher than the second threshold. In some embodiments, the third threshold for power imbalance can be equal to 25 dB and the fourth threshold for MRTD can be equal to 33 ps.

[0191] In some embodiments, a first set of parameters for aggregation of non-collocated CCs can be associated with existing minimum radio frequency (RF) requirements in TS 38.101 and existing demodulation performance in TS 38.101. In some embodiments, a second set of parameters for aggregation of non-collocated CCs can be associated with new minimum RF requirements to be introduced in TS 38.101 in order to test the reference sensitivity requirement in the presence of an interferer that is 25 dB higher than the wanted signal. Some reference sensitivity degradation should be allowed to occur. In such embodiments, the UE 106 can use separate RF chains to receive the aggregated carriers.

[0192] In some embodiments, additionally or alternatively, the second set of parameters for aggregation of non-collocated CCs can be associated with new demodulation performance to be introduced in TS 38.101 in order to verify a 25 dB power imbalance between the wanted signal and the aggregated carrier on the adjacent channel. In some embodiments, a UE that supports the first set of parameters for aggregation of non-collocated CCs can be referred to as a Type-1 UE. In some embodiments, a UE that supports the second set of parameters for aggregation of non-collocated CCs can be referred to as a Type-2 UE.

[0193] In some embodiments, with the assistance of additional information reporting such as reference signal received power (RSRP), it can be beneficial to increase the opportunity for the base station 102 to schedule Type-1 UEs. The RSRP can be reported for the serving cell and the target cell, respectively. Thus, the base station 102 can be able to use this information for scheduling and activation or deactivation of CCs associated with secondary cells (Scells). However, more frequency reporting can be needed and thus there can be a greater signaling overhead burden.

[0194] To reduce the signaling overhead, the measurement results can include a first reference signal received power (RSRP) of a strongest cell among the serving cell and at least one candidate secondary cell, and an indication of a RSRP difference between the first RSRP and a second RSRP. The second RSRP can be for a cell among the serving cell and the at least one candidate secondary cell. The cell can be different from the strongest cell. In other words, the UE 106 can report the RSRP of the strongest cell and the RSRP difference between the RSRP of the strongest cell and the RSRP of other cells. In some embodiments, the granularity of the RSRP difference and the range of the RSRP difference can be predefined. In some embodiments, the granularity of the RSRP difference can be 1 dB and the range of the RSRP difference can be 0 dB to 30 dB. For example, Table 1 below shows an example of RSRP difference reporting. In Table 1, the RSRP difference is also referred to as differential RSRP.

[0195] Table 1

[0196] Reported value Measured quantity Unit DIFFRSRP_0 -30 ≥ ΔRSRP dB DIFFRSRP_1 -29 ≥ ΔRSRP > -30 dB DIFFRSRP_2 -28 ≥ ΔRSRP > -29 dB DIFFRSRP_3 -27 ≥ ΔRSRP > -28 dB DIFFRSRP_4 -26 ≥ ΔRSRP > -27 dB DIFFRSRP_5 -25 ≥ ΔRSRP > -26 dB DIFFRSRP_6 -24 ≥ ΔRSRP > -25 dB …… …… … DIFFRSRP_25 -5 ≥ ΔRSRP > -6 dB DIFFRSRP_26 -4 ≥ ΔRSRP > -5 dB DIFFRSRP_27 -3 ≥ ΔRSRP > -4 dB DIFFRSRP_28 -2 ≥ ΔRSRP > -3 dB DIFFRSRP_29 -1 ≥ ΔRSRP > -2 dB DIFFRSRP_30 0 ≥ ΔRSRP > -1 dB

[0197] In some embodiments, the measurement results further include a system frame number (SFN) and a frame timing difference (SFTD) between the serving cell and one of the at least one candidate secondary cell.

[0198] In some embodiments, if the capability information indicates that the UE 106 supports the first set of parameters, the RSRP difference value can be lower than a fifth threshold for the power imbalance, and the SFTD can be lower than a sixth threshold for the MRTD. Accordingly, the BS 102 can send the first signaling to the UE 106 for activating the non-collocated CCs.

[0199] In some embodiments, the fifth threshold can be equal to or greater than the first threshold for the power imbalance and less than the third threshold for the power imbalance. For example, the fifth threshold can be equal to 6 dB or slightly greater than 6 dB.

[0200] In some embodiments, the sixth threshold can be equal to or greater than the second threshold for the MRTD and less than the fourth threshold for the MRTD. For example, the sixth threshold can be equal to 3 μβ or slightly greater than 3 μβ.

[0201] In some embodiments, if the capability information indicates whether the UE 106 supports the second set of parameters, and if the RSRP difference value is higher than the first threshold for the power imbalance and lower than the third threshold for the power imbalance, or the SFTD is higher than the second threshold for the MRTD and lower than the fourth threshold for the MRTD, the BS 102 can send the first signaling to the UE 106 for activating the non-collocated CCs.

[0202] In some embodiments, to further reduce the signaling overhead, the measurement results can not include the RSRP difference value and the SFTD. Instead, the measurement results can include a first flag. The first flag can indicate that the RSRP difference value is lower than a fifth threshold for the power imbalance and the SFTD is lower than a sixth threshold for the MRTD. The fifth threshold can be equal to or greater than the first threshold. The sixth threshold for the MRTD can be equal to or greater than the second threshold for the MRTD. Alternatively, the measurement results can include a second flag. The second flag can indicate that the RSRP difference value is higher than the fifth threshold for the power imbalance or the SFTD is higher than the sixth threshold for the MRTD.

[0203] In some embodiments, the set of parameters for aggregation of non-collocated CCs can include: a first set of parameters for aggregation of non-collocated CCs, the first set including a first threshold for power imbalance between non-collocated CCs and a second threshold for maximum receive time difference (MRTD) between non-collocated CCs; or a second set of parameters for aggregation of non-collocated CCs, the second set including a third threshold for power imbalance and a fourth threshold for MRTD, the third threshold being higher than the first threshold and the fourth threshold being higher than the second threshold.

[0204] In some embodiments, the signaling for activating or deactivating non-collocated CCs can include: transmitting, in accordance with a determination that the capability information indicates whether the UE supports the second set of parameters and that the RSRP difference is higher than the first threshold for power imbalance and lower than the third threshold for power imbalance or the SFTD is higher than the second threshold for MRTD and lower than the fourth threshold for MRTD, first signaling for activating the non-collocated CCs.

[0205] In some embodiments, the measurement result can include: a first flag indicating that the RSRP difference is lower than a fifth threshold for power imbalance and the SFTD is lower than a sixth threshold for MRTD, the fifth threshold being equal to or greater than the first threshold for power imbalance and less than the third threshold for power imbalance, the sixth threshold being equal to or greater than the second threshold for MRTD and less than the fourth threshold for MRTD; or a second flag indicating that the RSRP difference is higher than the fifth threshold for power imbalance or the SFTD is higher than the sixth threshold for MRTD.

[0206] In some embodiments, the signaling for activating or deactivating non-collocated CCs can include: transmitting, in accordance with a determination that the measurement result includes the first flag, first signaling for activating the non-collocated CCs; and transmitting, in accordance with a determination that the measurement result includes the second flag, second signaling for deactivating the non-collocated CCs.

[0207] Example embodiments

[0208] In some embodiments, a method can include establishing a cellular link with a network node and transmitting signaling to the network node, the signaling including capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC. The method can further include receiving physical downlink shared channel (PDSCH) signaling on the first CC and the second CC from the network node and measuring a relative time difference (RTD) between a start of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current time slot of the first CC and a start of a first OFDM symbol in a current time slot of the second CC. Alternatively, the method can include measuring an RTD between a start of a first OFDM symbol in a current time slot of the first CC and an end of a last OFDM symbol in a previous time slot of the second CC. The method can also include transmitting a report including the measured RTD to the network node and receiving first downlink (DL) signaling on the first CC and second DL signaling on the second CC from the network node. According to some embodiments, one of the first DL signaling or the second DL signaling can include an adjusted set of OFDM symbols. Additionally or alternatively, the adjusted set of OFDM symbols can be adjusted based at least in part on the measured RTD such that a degraded OFDM symbol is avoided.

[0209] According to some examples, the method can further include determining a measurement reference point for the first CC or the second CC. Additionally, according to some embodiments, the measurement reference point can correspond to a CC that is another one of the first CC or the second CC associated with the adjusted set of OFDM symbols. In some embodiments, the determination can be based on one or more reference signal received power (RSRP) metrics, one or more reference signal received quality (RSRQ) metrics, one or more maximum average aggregate throughput metrics associated with the first CC and the second CC. In some embodiments, the determination can be based on which of the first CC or the second CC is associated with a primary cell (PCell). Additionally or alternatively, the determination can be based at least in part on an indication received from the network node.

[0210] In some embodiments, the measured RTD can be less than or equal to a maximum receive timing difference (MRTD), and the MRTD can be greater than a cyclic prefix (CP). Thus, the UE can be able to support an increased power imbalance between the first CC and the second CC when the measured RTD is less than or equal to the MRTD. According to further embodiments, the method can include determining a degraded OFDM symbol associated with the first CC or the second CC based on the measured RTD. In some embodiments, the degraded OFDM symbol can be corrupted due to a phase jump when no analog gain change occurs at a beginning of at least one of the first CC or the second CC. In some embodiments, the method can be performed by a Type 3a user equipment (UE) or a Type 3b UE.

[0211] In some embodiments, a method can include establishing a radio resource control (RRC) connection with a user equipment (UE), and receiving signaling from the UE including capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC. The method can further include transmitting physical downlink shared channel (PDSCH) signaling on the first CC and the second CC to the UE, and receiving a report from the UE including a measured relative time difference (RTD). In some embodiments, the measured RTD can be an RTD between a beginning of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current time slot of the first CC and a beginning of a first OFDM symbol in a current time slot of the second CC, or an RTD between the beginning of the first OFDM symbol in the current time slot of the first CC and an end of a last OFDM symbol in a previous time slot of the second CC. The method can further include comparing the measured RTD to one or more signaling metrics associated with the first CC and the second CC, and transmitting first downlink (DL) signaling on the first CC and second DL signaling on the second CC to the UE. According to some embodiments, one of the first DL signaling or the second DL signaling can include an adjusted set of OFDM symbols. Additionally or alternatively, the adjusted set of OFDM symbols can be adjusted to avoid a degraded OFDM symbol, and can be based at least in part on the comparison of the measured RTD to the one or more signaling metrics.

[0212] According to further embodiments, the method can include transmitting signaling to the UE including an indication of an alignment of a shared low noise amplifier (LNA) with the first CC or the second CC. Additionally or alternatively, the method can include configuring at least one control resource set (CORESET) located after the first OFDM symbol for receiving a physical downlink control channel (PDCCH). In some embodiments, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the measured RTD is less than a cyclic prefix (CP) that is less than X microseconds (ps), where X is a value that can correspond to a maximum receive timing difference (MRTD). Additionally or alternatively, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the CP is less than the measured RTD that is less than X ps. In some embodiments, the comparison of the RTD to the one or more signaling metrics can be performed according to an inequality that the measured RTD is greater than X ps.

[0213] In some embodiments, if the measured RTD is less than the CP (which is less than X ps), the method can further include scheduling the adjusted PDSCH signaling using available symbols in the slot (e.g., within a range of symo - symi3). Additionally or alternatively, if the CP is less than the measured RTD (which is less than X ps), the method can further include scheduling the adjusted PDSCH signaling using symbols from a range of symi - symi3 or from symbols in a range of symo - symi2 (e.g., excluding the first or last symbol in the slot of one of the CCs). In some embodiments, if the measured RTD is greater than X ps, the method can further include refraining from scheduling the adjusted PDSCH signaling. According to further embodiments, up to four multiple-input multiple-output (MIMO) layers can be supported on the first CC and / or the second CC.

[0214] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0215] Embodiments of the present disclosure can be implemented in any of various forms. For example, some embodiments can be implemented as a computer-implemented method, a computer-readable memory medium, or a computer system. Other embodiments can be implemented using one or more custom-designed hardware devices such as ASICs. Still other embodiments can be implemented using one or more programmable hardware elements such as FPGAs.

[0216] In some embodiments, a non-transitory computer-readable storage medium can be configured such that it stores program instructions and / or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, such as any of the method embodiments described herein, or any combination of method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets.

[0217] In some embodiments, a device (e.g., UE 106) can be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or any combination of method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device can be implemented in any of a variety of forms.

[0218] Any of the methods described herein for operating a user equipment (UE) can be the basis for a corresponding method for operating a base station by interpreting each message / signal X received by the UE in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station.

[0219] While the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be construed to include all such variations and modifications.

Claims

1. A method comprising: establishing a cellular link with a network node; sending, to the network node, signaling comprising capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC; receiving, from the network node, physical downlink shared channel (PDSCH) signaling on the first CC and the second CC; measuring a relative time difference (RTD) between at least one of the following associated with the PDSCH signaling: a start of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current time slot of the first CC and a start of a first OFDM symbol in a current time slot of the second CC, or a start of a first OFDM symbol in a current time slot of the first CC and an end of a last OFDM symbol in a previous time slot of the second CC; sending, to the network node, a report comprising the measured RTD; and receiving, from the network node, first downlink (DL) signaling on the first CC and second DL signaling on the second CC, wherein one of the first DL signaling or the second DL signaling comprises an adjusted set of OFDM symbols, and wherein the adjusted set of OFDM symbols is adjusted based at least in part on the measured RTD such that a degraded OFDM symbol is avoided.

2. The method of claim 1, further comprising: determining a measurement reference point of the first CC or the second CC, wherein the measurement reference point corresponds to a CC other than one of the first CC or the second CC associated with the adjusted set of OFDM symbols.

3. The method of claim 2, wherein, the determining is based at least in part on at least one of: one or more reference signal received power (RSRP) metrics associated with the first CC and the second CC; one or more reference signal received quality (RSRQ) metrics associated with the first CC and the second CC; one or more maximum average aggregated throughput metrics associated with the first CC and the second CC; or which of the first CC or the second CC is associated with a primary cell (PCell).

4. The method of claim 2, wherein, the determining is based at least in part on an indication received from the network node.

5. The method of claim 1, wherein, a user equipment (UE) is capable of supporting an increased power imbalance between the first CC and the second CC when the measured RTD is less than or equal to a maximum receive timing difference (MRTD).

6. The method of claim 5, wherein, the MRTD is greater than a cyclic prefix (CP).

7. The method of claim 1, further comprising: determining whether the degraded OFDM symbol is associated with the first CC or the second CC based on the measured RTD.

8. The method of claim 7, further comprising: determining that the degraded OFDM symbol is corrupted due to a phase jump when no analog gain change occurs at a start of at least one of the first CC or the second CC.

9. The method of claim 1, wherein, The method is performed by a Type 3a user equipment (UE) or a Type 3b UE.

10. A method comprising: establishing a radio resource control (RRC) connection with a user equipment (UE); receiving, from the UE, signaling comprising capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC; transmitting, to the UE, physical downlink shared channel (PDSCH) signaling on the first CC and the second CC; receiving, from the UE, a report comprising a measured relative time difference (RTD) between at least one of the following associated with the PDSCH signaling: a start of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current slot of the first CC and a start of a first OFDM symbol in a current slot of the second CC, or a start of a first OFDM symbol in a current slot of the first CC and an end of a last OFDM symbol in a previous slot of the second CC; comparing the measured RTD to one or more signaling metrics associated with the first CC and the second CC; transmitting, to the UE, first downlink (DL) signaling on the first CC and second DL signaling on the second CC, wherein one of the first DL signaling or the second DL signaling comprises an adjusted set of OFDM symbols, and wherein the adjusted set of OFDM symbols is adjusted to avoid a degraded OFDM symbol and is based at least in part on the comparison of the measured RTD to the one or more signaling metrics.

11. The method of claim 10, further comprising: transmitting, to the UE, signaling comprising an indication of an alignment of a shared low noise amplifier (LNA) with the first CC or the second CC.

12. The method of claim 10, further comprising: configuring at least one control resource set (CORESET) positioned after a first OFDM symbol in at least one of the first CC or the second CC for receiving a physical downlink control channel (PDCCH).

13. The method of claim 10, wherein, the comparison of the RTD to one or more signaling metrics comprises determining which of the following inequalities is satisfied: the measured RTD is less than a cyclic prefix (CP), the CP being less than X microseconds (ps), where X is a value corresponding to a maximum receive timing difference (MRTD); the CP is less than the measured RTD, the measured RTD being less than X ps; or the measured RTD is greater than X ps.

14. The method of claim 13, wherein: if the measured RTD is less than the CP, the CP being less than X ps, the method further comprises scheduling the adjusted PDSCH signaling within available symbols in a slot corresponding to a range between sym0 and syml3; if the CP is less than the measured RTD, the measured RTD is less than X μs, then the method further comprises scheduling the adjusted PDSCH signaling within available symbols in a slot, the available symbols excluding a first symbol or a last symbol corresponding to one of a range between sym1 - sym13 or sym0 - sym12, respectively; or if the measured RTD is greater than X μs, then the method further comprises refraining from scheduling the adjusted PDSCH signaling.

15. The method of claim 10, wherein, At least one of the first CC or the second CC supports up to four multiple-input multiple-output (MIMO) layers.

16. The method of claim 10, wherein, The UE is a Type 3a UE or a Type 3b UE.

17. An apparatus, the apparatus comprising: at least one processor configured to cause a user equipment (UE) to: establish a cellular link with a network node; send, to the network node, signaling comprising capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC; receive, from the network node, physical downlink shared channel (PDSCH) signaling on the first CC and the second CC; measure a relative time difference (RTD) between at least one of: a start of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current slot of the first CC and a start of a first OFDM symbol in a current slot of the second CC, or a start of a first OFDM symbol in a current slot of the first CC and an end of a last OFDM symbol in a previous slot of the second CC; send, to the network node, a report comprising the measured RTD; and receive, from the network node, first downlink (DL) signaling on the first CC and second DL signaling on the second CC, wherein one of the first DL signaling or the second DL signaling comprises an adjusted set of OFDM symbols, and wherein the adjusted set of OFDM symbols is adjusted based at least in part on the measured RTD such that a degraded OFDM symbol is avoided.

18. The apparatus of claim 17, wherein, the at least one processor is further configured to cause the UE to: determine a measurement reference point of the first CC or the second CC, wherein the measurement reference point corresponds to a CC that is other than one of the first CC or the second CC that is associated with the adjusted set of OFDM symbols.

19. The apparatus of claim 18, wherein, the determination is based at least in part on at least one of: one or more reference signal received power (RSRP) metrics associated with the first CC and the second CC; one or more reference signal received quality (RSRQ) metrics associated with the first CC and the second CC; one or more maximum average aggregate throughput metrics associated with the first CC and the second CC; or which of the first CC or the second CC is associated with a primary cell (PCell).

20. The apparatus of claim 18, wherein, The determining is based at least in part on an indication received from the network node.

21. The apparatus of claim 17, wherein, A user equipment (UE) can support an increased power imbalance between a first CC and a second CC when a measured RTD is less than or equal to a maximum receive timing difference (MRTD).

22. The apparatus of claim 17, the apparatus further comprising: a radio operably coupled to the at least one processor.

23. An apparatus, the apparatus comprising: at least one processor configured to cause a network node to: establish a radio resource control (RRC) connection with a user equipment (UE); receive, from the UE, signaling including capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC; transmit, to the UE, physical downlink shared channel (PDSCH) signaling on the first CC and the second CC; receive, from the UE, a report including a measured relative time difference (RTD) between at least one of the following associated with the PDSCH signaling: a start of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current time slot of the first CC and a start of a first OFDM symbol in a current time slot of the second CC, or a start of a first OFDM symbol in a current time slot of the first CC and an end of a last OFDM symbol in a previous time slot of the second CC; compare the measured RTD to one or more signaling metrics associated with the first CC and the second CC; transmit, to the UE, first downlink (DL) signaling on the first CC and second DL signaling on the second CC, wherein one of the first DL signaling or the second DL signaling includes an adjusted set of OFDM symbols, and wherein the adjusted set of OFDM symbols is adjusted to avoid a degraded OFDM symbol and is based at least in part on the comparison of the measured RTD to the one or more signaling metrics.

24. The apparatus of claim 23, wherein, the at least one processor is further configured to cause the network node to: transmit, to the UE, signaling including an indication of an alignment of a shared low noise amplifier (LNA) with the first CC or the second CC.

25. The apparatus of claim 23, wherein, the at least one processor is further configured to cause the network node to: configure at least one control resource set (CORESET) located after a first OFDM symbol in at least one of the first CC or the second CC for receiving a physical downlink control channel (PDCCH).

26. The apparatus of claim 23, wherein, the comparison of the RTD to one or more signaling metrics includes determining which of the following inequalities is satisfied: the measured RTD is less than a cyclic prefix (CP), the CP being less than X microseconds (ps), where X is a value corresponding to a maximum receive timing difference (MRTD); the CP is less than the measured RTD, the measured RTD being less than X ps; or the measured RTD is greater than X ps.

27. The apparatus of claim 26, wherein: if the measured RTD is less than the CP, the CP is less than X μβ, the at least one processor is further configured to cause the network node to schedule the adjusted PDSCH signaling within available symbols in a slot corresponding to a range between symO and symi3; if the CP is less than the measured RTD, the measured RTD is less than X μβ, the at least one processor is further configured to cause the network node to schedule the adjusted PDSCH signaling within available symbols in a slot, the available symbols excluding a first symbol or a last symbol corresponding to one of a range between symi-symi3 or symO-symi2, respectively; or if the measured RTD is greater than X μβ, the at least one processor is further configured to cause the network node to refrain from scheduling the adjusted PDSCH signaling.

28. The apparatus of claim 23, wherein, support for up to four multiple-input multiple-output (MIMO) layers on at least one of the first CC or the second CC.

29. A non-transitory computer-readable storage medium storing program instructions executable by one or more processors to cause a user equipment (UE) to: establish a cellular link with a network node; send, to the network node, signaling including capability information indicating support for carrier aggregation (CA) of a first component carrier (CC) and a second CC; receive, from the network node, physical downlink shared channel (PDSCH) signaling on the first CC and the second CC; measure a relative time difference (RTD) between at least one of: a start of a first orthogonal frequency-division multiplexing (OFDM) symbol in a current slot of the first CC and a start of a first OFDM symbol in a current slot of the second CC, or a start of a first OFDM symbol in a current slot of the first CC and an end of a last OFDM symbol in a previous slot of the second CC; send, to the network node, a report including the measured RTD; and receive, from the network node, first downlink (DL) signaling on the first CC and second DL signaling on the second CC, wherein one of the first DL signaling or the second DL signaling includes an adjusted set of OFDM symbols, and wherein the adjusted set of OFDM symbols is adjusted based at least in part on the measured RTD such that a degraded OFDM symbol is avoided.

30. The non-transitory computer-readable storage medium of claim 29, wherein, the program instructions are further executable to cause the UE to: determine a measurement reference point of the first CC or the second CC, wherein the measurement reference point corresponds to a CC other than one of the first CC or the second CC associated with the adjusted set of OFDM symbols.

Images