Techniques for dynamic configuration of user equipment types

Abstract

This application relates to devices and assemblies, including apparatuses, systems, and methods for dynamically configuring a type capability of a UE.

Description

Technical Field

[0001] This application relates generally to communication networks, and more particularly to techniques for configuration in co-located and non-co-located scenarios. Background Technology

[0002] A Transmitting and Receiving Point (TRP) describes a point in a network topology from which signals are transmitted or received. A TRP can be a collection of antennas used to transmit and receive signals in a wireless communication system. For example, a base station (BS) in a cellular network can be a TRP.

[0003] Co-located transmission refers to a scenario where multiple transmission points (e.g., TRPs) are located at the same physical location (e.g., a base station (e.g., an eNodeB in LTE)). On the other hand, non-co-located transmission refers to a scenario where the transmission points (e.g., TRPs) are not located at the same physical location.

[0004] Signals transmitted simultaneously from non-co-located transmitting points can be received at different times at the receiver. Furthermore, signals transmitted at the same power from non-co-located transmitting points may have different power levels at the receiver. Therefore, a receiver capable of receiving signals from non-co-located transmitting points may need to be equipped with technology that tolerates power imbalances and timing misalignments between the received signals. Attached Figure Description

[0005] Figure 1 Examples of network environments based on some implementation schemes are provided.

[0006] Figure 2 Examples of network environments based on some implementation schemes are provided.

[0007] Figure 3 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0008] Figure 4 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0009] The diagram illustrates the operational flow / algorithm structure according to some implementation schemes.

[0010] Figure 6 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0011] Figure 7 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0012] Figure 8 Examples of user equipment based on some implementation schemes are shown.

[0013] Figure 9 Examples of network nodes according to some implementation schemes are shown. Detailed Implementation

[0014] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, and / or techniques, are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of some embodiments. However, it will be apparent to those skilled in the art that various aspects may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the aspects with unnecessary detail. For the purposes of this document, the phrase “A or B” means (A), (B), or (A and B), and the phrase “based on A” means “at least partially based on A,” for example, it can be “based solely on A” or it can be “partially based on A.”

[0015] The following is a glossary of terms that may be used in this disclosure.

[0016] As used herein, the term "circuit" means, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), and / or digital signal processors (DSPs) configured to provide the described functionality. In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for executing the functionality of that program code. In these aspects, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0017] As used herein, the term "processor circuit" means, is part of, or includes the following: circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations; or recording, storing, or transmitting digital data. The term "processor circuitry" may also refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device capable of executing or otherwise operating computer-executable instructions (such as program code); a software module; or a functional process.

[0018] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces; for example, a bus, I / O interface, peripheral component interface, or network interface card.

[0019] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. The terms "user equipment" or "UE" may be considered synonymous and may refer to a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0020] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0021] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computer, storage, or network resources provided by physical hardware components. "Virtualized resource" can refer to computer, storage, or network resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0022] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of sending and receiving information.

[0023] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0024] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0025] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0026] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single piece of content within an information element or a data element that contains content. An information element may include one or more additional information elements.

[0027] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include a user equipment (UE) 104 communicatively coupled to a base station (BS) 108 of a radio access network (RAN) 110. In some implementations, base station 108 is a next-generation node B (gNB) providing one or more 3GPP New Radio (NR) cells. In other implementations, base station 108 is an evolved Node B (eNB) providing one or more Long Term Evolution (LTE) cells. The air interface through which UE 104 and base station 108 communicate may be compatible with 3GPP Technical Specifications (TS), such as those defining fifth-generation (5G) NR or later system standards (e.g., sixth-generation (6G) standards). Base station 108 may provide user plane and control plane protocol termination to UE 104.

[0028] UE 104 may provide information 120 to BS 108. Information 120 may include features or functions supported by the UE. BS 108 may use information 120 to schedule or allocate resources based on the features and functions supported by UE 104.

[0029] BS 108 can transmit configuration 130 to UE 104. Configuration 130 can allocate resources to UE 104 or determine parameters associated with transmission or reception at UE 104.

[0030] UE 104 supports carrier aggregation (CA). Using CA, UE 104 can simultaneously transmit or receive using multiple carriers (also called component carriers (CC)). Information 120 may indicate whether UE 104 supports (or does not support) carrier aggregation. Information 120 may also include information associated with the supported component carriers, such as carrier frequencies.

[0031] UE 104 can support Multiple-Input Multiple-Output (MIMO) transmission or reception. In MIMO transmission, UE 104 can use one or more antennas or antenna ports to transmit. An antenna port can be a logical definition that includes one or more physical antennas for transmitting information. In MIMO reception, UE 104 can use one or more antennas or antenna ports to receive. Information 120 may include a field indicating whether UE 104 supports MIMO transmission or reception. Information 120 may include information associated with the number of antennas (or antenna ports) supported by UE 104 for uplink transmission or downlink reception.

[0032] BS 108 can use MIMO for transmitting or receiving. In some instances, BS 108 can use Transmit / Receive Points (TRPs) 116 and 118. TRP 116 or 118 can be a point in the network that transmits or receives signals. BS 108 can be associated with one or more TRPs (e.g., TRPs 116 and 118). BS 108 can use multiple TRPs to improve reliability, coverage, or network capacity.

[0033] A transmitter (e.g., UE 104 or BS 108) can transmit different data streams on different antenna ports. For example, a transmitter with two antenna ports can assign one data stream to one antenna port and another data stream to the other antenna port. Each data stream can be referred to as a MIMO layer or simply a layer.

[0034] In some implementations, BS 108 can combine carrier aggregation with multiple TRPs. For example, BS 108 can transmit signals from one TRP on a component carrier and from a different TRP on another component carrier. Similarly, UE 104 can receive signals from one TRP on a component carrier and from a different TRP on another component carrier.

[0035] In some instances, UE 104 may support reception only when TRP is co-located. In other instances, UE 104 may support reception when TRP is not co-located.

[0036] In some implementations, signal 120 may include UE type information. The UE type may indicate whether the UE supports non-co-located carrier aggregation, for example, when different components are transmitted from different TRPs.

[0037] In some implementations, information 120 may instruct the UE to switch between a co-located carrier aggregation configuration and a non-co-located carrier aggregation configuration. In some instances, UE 104 may dynamically switch its configuration based on determined co-located conditions, non-co-located conditions, or indications from BS 108. In some instances, BS 108 may determine the co-located or non-co-located conditions and configure UE 104 accordingly.

[0038] Figure 2 A network environment 200 according to some implementation schemes is illustrated. UE 104 can support co-located and non-co-located carrier aggregation.

[0039] UE 104 may be referred to as a Type 1 UE when it supports co-located carrier aggregation. In co-located carrier aggregation, the power imbalance of signals received at the UE from different TRPs will not exceed a predefined threshold. Alternatively or additionally, component carriers may be referred to as co-located when the maximum receive timing difference (MRTD) is less than a predefined timing threshold.

[0040] For example, a reference signal 220 transmitted from TRP 116 on component carrier C1 may have a received power P1 at UE 104. Similarly, a reference signal 230 transmitted from TRP 118 on component carrier C2 may have a received power P2 at UE 104. If the absolute value of P1 minus P2 (|P1-P2|) is less than a predefined power threshold (e.g., 6 dB), then TRPs 116 and 118 are considered co-located.

[0041] The MRTD can be associated with the timing difference between signals received at UE 104. For example, consider that reference signals 220 and 230 are simultaneously transmitted to UE 104. Furthermore, consider that reference signal 220 is received at UE 104 on component carrier C1 at time T1, and reference signal 230 is received at UE 104 on component carrier C2 at time T2. MRTD can be defined as the absolute value of T1 minus T2 (|T1 – T2|). When MRTD is less than a predefined timing threshold (e.g., 3 microseconds (µs)), TRPs 116 and 118 can be considered co-located.

[0042] The number of layers supported on each component carrier can be associated with whether the component carriers are co-located. In one example, in carrier aggregation, when component carriers are co-located, the maximum number of MIMO layers supported by each component carrier may not exceed a carrier threshold, for example, four layers per component carrier. In one example, the maximum number of layers in dual connectivity may not exceed a dual connectivity threshold. For example, the dual connectivity threshold could be four layers on NR component carriers. In another example, the dual connectivity threshold could be two layers on Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) component carriers.

[0043] UE 104 may be referred to as a Type 2 UE when it supports non-co-located carrier aggregation. In non-co-located carrier aggregation, the power imbalance of signals received at the UE from different TRPs does not exceed a predefined threshold. Alternatively or additionally, component carriers may be referred to as non-co-located when the maximum received timing difference (MRTD) is less than a predefined timing threshold. In one example, the predefined power threshold may be 25 dB, and the predefined timing threshold may be 33 microseconds (µs). When component carriers are non-co-located, the maximum number of MIMO layers supported by each component carrier may not exceed a carrier threshold, for example, 2 layers per component carrier used for carrier aggregation or dual connectivity.

[0044] The number of layers, maximum supported power imbalance, or MRTD can be referred to as UE type capability. For example, UE type 1 capability may include support for power imbalance up to 6 dB, MRTD up to 3 µs, up to 4 MIMO layers per component carrier used for carrier aggregation, up to 4 MIMO layers on NR component carriers used for dual connectivity, and up to 2 MIMO layers on E-UTRA component carriers used for dual connectivity. Similarly, UE type 2 capability may include support for power imbalance up to 25 dB, MRTD up to 33 µs, and 2 MIMO layers per component carrier used for both carrier aggregation and dual connectivity.

[0045] In one example, an operator may allocate in-band n77 or n78 for NR non-co-located carrier aggregation. In another example, an operator may allocate inter-band 42 (E-UTRA band) and n77 or n78 for E-UTRA and NR non-co-located dual connectivity (EN-DC, e.g., dual connectivity with one connection on E-UTRA component carriers in band 42 and one connection via NR component carriers in bands n77 or n78). UE type 2 or UEs with UE type 2 capabilities can utilize these allocated resources for NR non-co-located carrier aggregation or non-co-located EN-DC.

[0046] In some instances, the signal received from the TRP at UE 104 may satisfy the co-location condition even when the TRP is not co-located, for example, by having a power imbalance less than a threshold (e.g., 6 dB) or an MRTD less than a threshold (e.g., 3 µs). It is desirable to utilize Type 1 capabilities to configure Type 2 UEs, where the Type 1 capability is, for example, the number of MIMO layers associated with carrier aggregation or dual connectivity for a Type 1 UE.

[0047] In one implementation, the UE may report its UE type, such as a Type 1 UE or a Type 2 UE. For example, UE Capability Information (UCI) may include fields associated with the UE type. The UE may report the UE capabilities associated with its UE type. For example, a Type 2 UE may also report whether it supports Type 1 capabilities, such as support for the number of layers used for carrier aggregation and dual connectivity when the TRP is determined to be co-located (e.g., power imbalance less than a threshold of 6 dB or MRTD less than a threshold of 3 µs).

[0048] In one implementation, a Type 2 UE may include two sets of capabilities, such as Type 2 capabilities and Type 1 capabilities. For example, Type 2 capabilities may include up to two MIMO layers per component carrier under non-co-located conditions (e.g., power imbalance up to 25 dB or MRTD up to 33 µs). Type 1 capabilities may include up to four MIMO layers for NR component carriers and up to two MIMO layers for E-UTRA component carriers under co-located conditions (e.g., power imbalance less than 6 dB or MRTD less than 3 µs).

[0049] A Type 1 UE may include only one set of capabilities, such as Type 1 capabilities. For example, a Type 1 UE may support up to four MIMO layers for NR component carriers and two MIMO layers for E-UTRA component carriers under co-location conditions. A Type 1 UE may not require non-co-location resources for scheduling.

[0050] In one example, both a Type 1 UE and a Type 2 UE can report support for both Type 1 and Type 2 capabilities. The network (e.g., BS 108) can consider such a UE as a Type 2 UE that supports both Type 1 and Type 2 capabilities as described above.

[0051] The network can use Time Alignment Error (TAE) to determine co-location or non-co-location conditions. TAE can be associated with MRTD. The network can determine TAE via a random access procedure. The UE's TAE can be associated with the UE's timing advance parameters.

[0052] In one implementation, the UE can report a Type 3 UE. A Type 3 UE can indicate that the UE supports both Type 1 and Type 2 capabilities similar to those described above.

[0053] Figure 3 An operational flow / algorithm structure 300 according to some implementation schemes is illustrated. The operational flow / algorithm structure 300 is an example of the UE's ability to dynamically switch UE types. The operational flow / algorithm structure 300 may be implemented by the UE (e.g., UE 104 or UE 800) or components therein (e.g., processing circuitry 804).

[0054] The operation flow / algorithm structure 300 may include: at 310, a transmission type indication. The UE may report its type to the base station. For example, the UE may report whether it is a Type 1 UE or a Type 2 UE. The report may indicate whether the UE supports both Type 1 and Type 2 capabilities.

[0055] The UE can determine its capability configuration. This capability configuration may include the number of transmit or receive antennas for carrier aggregation or dual connectivity support, or the number of MIMO layers for carrier aggregation or dual connectivity support, as well as other parameters. The UE's transmitter radio frequency (RF) chain or receiver RF chain can be configured based on this capability configuration.

[0056] In some implementations, the UE may transmit a capability report. This capability report may indicate whether the UE's capability configuration is based on Type 1 or Type 2 capabilities. The capability report may include a field indicating an index of the type capability. The capability report may be a separate message or may be included in the same message that includes the type indication.

[0057] The operation flow / algorithm structure 300 may include: at 320, determining the configuration. The UE may be configured based on default capabilities (e.g., type 2 capabilities). The UE may report its current configuration to the base station. For example, 310 the report may indicate the current UE type capabilities used to configure the UE.

[0058] The operation flow / algorithm structure 300 may include: at 330, receiving a co-location indication. The UE may receive a message from the base station indicating whether the co-location condition or the non-co-location condition is met.

[0059] Consider a UE that supports both Type 1 and Type 2 capabilities and is configured based on Type 2 capability. Based on the TAE performance in the network, the BS can determine whether co-location conditions are met. If co-location conditions are not met, for example, power imbalance is not less than 6 dB or MRTD is not less than 3 µs, the base station can schedule the UE based on Type 2 capability. However, if co-location conditions are met, for example, power imbalance is less than 6 dB or MRTD is less than 3 µs, the network can transmit an indication to the UE that co-location conditions are met.

[0060] Consider a UE that supports both Type 1 and Type 2 capabilities and is configured based on Type 1 capabilities. Based on the TAE performance in the network, the BS can determine whether co-location conditions are met. If co-location conditions are met, for example, power imbalance less than 6 dB or MRTD less than 3 µs, the base station can schedule the UE based on Type 1 capabilities. However, if non-co-location conditions are met, for example, power imbalance greater than 6 dB and less than 25 dB or MRTD greater than 3 µs and less than 33 µs, the network can transmit an indication to the UE that non-co-location conditions are met.

[0061] The base station can use Radio Resource Control (RRC) signaling to transmit co-location condition information to the UE.

[0062] The operation flow / algorithm structure 300 may include: at 340, switching configurations. The UE can change its configuration based on a co-location indication.

[0063] For example, a UE configured based on a Type 2 capability associated with non-co-location conditions can receive an indication from the base station that co-location conditions are met (e.g., power imbalance less than 6 dB or MRTD or TAE less than 3 µs). The UE can then perform hardware preparation and reconfiguration based on Type 1 capabilities.

[0064] During reconfiguration, the UE may not expect to receive downlink control information from the base station, such as downlink or uplink scheduling. The UE can suspend or stop monitoring the downlink control channel, such as the Physical Downlink Control Channel (PDCCH), for a predefined time period. This predefined time period can be configured by the network, specified by 3GPP specifications, or based on UE category or UE capabilities. The UE can start a timer based on a reference time. For example, the UE can start a timer at 330 when it receives a co-location indication from the base station. The duration of the timer can be based on the predefined time period, and the UE can suspend PDCCH monitoring before the timer expires.

[0065] Figure 4An operational flow / algorithm structure 400 according to some implementation schemes is illustrated. The operational flow / algorithm structure 400 is an example of the UE's ability to dynamically switch UE types. The operational flow / algorithm structure 400 may be implemented by the UE (e.g., UE 104 or UE 800) or components therein (e.g., processing circuitry 804).

[0066] The operation flow / algorithm structure 400 may include: at 410, a transmission type indication. The UE may transmit a type indication to the base station. The type indication may indicate the UE type, for example, a type 1 UE, a type 2 UE, or a type 3 UE. A type 3 UE may indicate that the UE is capable of dynamically switching between type 1 capabilities and type 2 capabilities.

[0067] The operation flow / algorithm structure 400 may include: at 420, receiving a trigger event. The UE may receive a configuration message from the base station. The configuration message may include an indication of the trigger event. The trigger event may be associated with a measurement and a threshold associated with the measurement. For example, the measurement may be associated with a measurement of receive timing difference (RTD). The trigger event may also indicate an RTD threshold associated with the RTD measurement. The measurement may be associated with a measurement of reference signal received power (RSRP), and the trigger event may also indicate an RSRP threshold. The measurement may be associated with a measurement of channel state information (CSI), and the trigger event may also indicate a CSI threshold.

[0068] The operation flow / algorithm structure 400 may include: at 430, detecting a triggering event. The UE can consistently monitor events. For example, the UE can measure the RTD and compare it to an RTD threshold. The UE can measure the relative RSRP between the primary serving cell (PCell) and the secondary serving cell (SCell) and compare it to an RSRP threshold, or the UE can measure the CSI and compare it to a CSI threshold. When the measurement exceeds the threshold, the UE can detect a triggering event. When the measurement is below the threshold, the UE can detect a triggering event. For example, when the RTD (or MRTD) is less than the threshold, a UE configured based on Type 2 capability can detect a triggering event. In one example, the UE can evaluate the RTD threshold = cyclic prefix - relative RTD to determine whether a triggering event has been detected.

[0069] In another example, the UE can evaluate 6dB minus the relative RSRP measurement between the PCell and SCell (ΔRSRP), for example, 6dB - ΔRSRP. If the evaluation value is positive, this indicates that the power imbalance is less than 6dB, for example, the co-location condition is met. If the evaluation value is negative, this indicates that the power imbalance is greater than 6dB, for example, the non-co-location condition is met.

[0070] The operation flow / algorithm structure 400 may include: at 440, executing a reconfiguration procedure. Two options may be available for implementing the reconfiguration operation.

[0071] In Option 1, the UE can transmit a report to itself. The report can indicate that the UE has detected a triggering event. The report can include detailed information about the triggering event, the measured parameter, the threshold associated with the measurement, and the value associated with the evaluation at the UE. For example, the report can indicate a value relative to RSRP or a value relative to RTD. The UE can transmit the report on a Media Access Control (MAC) Control Element (CE) message.

[0072] The network (e.g., a base station) can transmit configuration messages to configure the UE based on Type 1 or Type 2 capabilities. The base station can transmit configuration messages via RRC signaling.

[0073] The UE can configure its hardware, such as the receive radio chain, based on configuration messages from the base station. During reconfiguration, the UE may not expect to receive downlink control information from the base station, such as downlink or uplink scheduling. The UE can suspend or stop monitoring the downlink control channel, such as the PDCCH, for a predefined time period. The predefined time period can be configured by the network, specified by 3GPP specifications, or based on UE category or UE capabilities. For example, the UE can start a timer when it receives a configuration message from the base station. The duration of the timer can be based on the predefined time period, and the UE can suspend PDCCH monitoring before the timer expires. After reconfiguration is complete or the timer expires, the UE can expect the base station to schedule the UE according to the capabilities associated with the reconfiguration.

[0074] In Option 2, the UE can perform hardware preparation and reconfiguration based on the detected triggering event. For example, if the UE is currently configured based on Type 1 capabilities and the UE detects a triggering event indicating that non-co-location conditions are met, the UE can reconfigure its hardware based on Type 2 capabilities associated with non-co-location carrier aggregation or dual connectivity. Similarly, if the UE is currently configured based on Type 2 capabilities and the UE detects a triggering event indicating that co-location conditions are met, the UE can reconfigure its hardware based on Type 1 capabilities associated with co-location carrier aggregation or dual connectivity.

[0075] The UE can report corresponding events to the network (e.g., a base station). The report may include detailed information about the triggering event, the measured parameter, the threshold associated with the measurement, and the value associated with the evaluation at the UE. For example, the report may indicate a value relative to RSRP or relative to RTD. The UE may transmit the report on a Media Access Control (MAC) Control Element (CE) message.

[0076] During reconfiguration, the UE may not expect to receive downlink control information from the base station, such as downlink or uplink scheduling. The UE can suspend or stop monitoring the downlink control channel, such as the PDCCH, for a predefined time period. This predefined time period can be configured by the network, specified by 3GPP specifications, or based on the UE category or UE capabilities. For example, the UE can start a timer when it receives a configuration message from the base station. The duration of the timer can be based on the predefined time period, and the UE can suspend PDCCH monitoring before the timer expires. After reconfiguration is complete or the timer expires, the UE can expect the base station to schedule the UE according to the capabilities associated with the reconfiguration.

[0077] Figure 5 An operational flow / algorithm structure 500 according to some implementation schemes is illustrated. The operational flow / algorithm structure 500 is an example of the operation of base station 108. The operational flow / algorithm structure 500 may be implemented by a network node (e.g., network node 900) or a component therein (e.g., processor 904).

[0078] The operation flow / algorithm structure 500 may include: at 510, receiving a type indication. The base station may receive a type indication from the UE. The type indication may be associated with the type of the UE (e.g., type 1 UE, type 2 UE, or type 3 UE). The type indication may indicate the type capabilities configured for the UE, such as type 1 capability or type 2 capability. The type indication may be transmitted via an uplink control element (UCE) (e.g., via a MAC CE).

[0079] The operation flow / algorithm structure 500 may include: at 520, determining co-location conditions. The base station can monitor and evaluate whether the UE meets the co-location carrier aggregation or dual connectivity conditions, for example, power imbalance less than 6dB or TAE or MRTD less than 3us. The base station can monitor and evaluate whether the UE meets the non-co-location carrier aggregation or dual connectivity conditions, for example, power imbalance less than 25dB or TAE or MRTD less than 33us.

[0080] The base station can receive measurement reports from the UE or perform measurements on signals (e.g., reference signals) received from the UE. For example, the base station can use signals transmitted by the UE to perform TAE or RTD measurements during random access.

[0081] The operation flow / algorithm structure 500 may include: at 530, determining whether to transmit a co-location indication. The base station determines whether to transmit a co-location indication to the UE. For example, if the UE indicates to the base station at 530 via a type indication that it is configured based on co-location type capability (e.g., type 1 capability), and the base station determines that the UE meets the non-co-location conditions, then the base station may determine to transmit an indication to the UE to indicate non-co-location.

[0082] In another example, if the UE indicates to the base station at 530 via a type indication that it is configured based on a non-co-location type capability (e.g., type 2 capability), and the base station determines that the UE meets the co-location conditions, then the base station may determine to transmit an indication to the UE to indicate co-location.

[0083] In one example, if the colocation conditions determined by the base station are aligned with the UE configuration based on the type capabilities (e.g., type 1 or type 2 capabilities) associated with the type indication, the base station can schedule the UE according to the UE's type capabilities.

[0084] The operation flow / algorithm structure 500 may include: at 540, transmitting a co-location indication. The base station may transmit the co-location indication to the UE. The co-location indication may implicitly or explicitly instruct the UE to dynamically reconfigure its hardware or software settings according to the co-location conditions associated with the co-location indication. The base station may transmit the co-location indication to the UE via RRC signaling.

[0085] When transmitting a co-location indication, the base station may expect the UE to perform a reconfiguration procedure. During reconfiguration, the base station may transmit downlink control information to the UE, such as downlink or uplink scheduling. The base station may suspend or stop transmitting downlink control channels (e.g., PDCCH) for a predefined time period. The predefined time period may be specified by 3GPP specifications or based on UE category or UE capabilities. For example, the base station may start a timer when transmitting the co-location indication to the UE. The duration of the timer may be based on the predefined time period, and the base station may suspend PDCCH transmission before the timer expires. After the timer expires, the base station may schedule the UE according to the capabilities associated with the co-location indication.

[0086] Figure 6 An operational flow / algorithm structure 600 according to some implementation schemes is illustrated. The operational flow / algorithm structure 600 is an example of the operation of base station 108. The operational flow / algorithm structure 600 may be implemented by a network node (e.g., network node 900) or a component therein (e.g., processor 904).

[0087] The operation flow / algorithm structure 600 may include, at 610, a reception type indication. The base station may receive a type indication from the UE. The type indication may be associated with the type of the UE (e.g., type 1 UE, type 2 UE, or type 3 UE). The type indication may indicate a type 3 UE. A type 3 UE may indicate that the UE can dynamically switch between type 1 capability and type 2 capability.

[0088] The operation flow / algorithm structure 600 may include: at 620, transmitting a configuration including a trigger event. The base station may transmit a configuration message including the trigger event to the UE. The trigger event may be associated with a co-location condition. The configuration message may configure the UE to monitor or evaluate the trigger event. The trigger event may include a measurement and a threshold associated with the measurement. The measurement may include a measurement of the relative RSRP between PCell and SCell, a measurement of RTD, or a measurement of CSI.

[0089] The operation flow / algorithm structure 600 may include: at 630, receiving an event indication. The base station may receive the event indication from the UE. The event indication may be associated with the detection of a triggering event at the UE. The event indication may include an identifier associated with the event. The event indication may include detailed information about the triggering event. For example, the event indication may include information related to a measured parameter, a threshold associated with the measurement, or a value associated with an evaluation at the UE. For example, the event indication may indicate a value relative to RSRP or a value relative to RTD. The base station may receive the indication via MAC CE.

[0090] The operation flow / algorithm structure 600 may include: at 640, determining that the UE has detected a trigger event. Based on the event indication, the base station can determine that the UE has detected a trigger event.

[0091] The operation flow / algorithm structure 600 may include: at 650, suspending UE scheduling. Based on determining that the UE has detected a trigger event, the base station may suspend UE scheduling. For example, trigger event detection may enable the UE to reconfigure its hardware or software based on different types of capabilities. During UE reconfiguration, the base station may suspend sending downlink control information to the UE.

[0092] In some instances, the base station can determine co-location or non-co-location conditions. Based on the determined co-location or non-co-location conditions, the base station can determine the UE type or type capability and send messages to the UE to configure the UE accordingly. In other instances, a triggering event can indicate that the UE has initiated a reconfiguration process.

[0093] Based on co-location conditions or type indications, the base station can determine the UE's configuration capabilities. Configuration capabilities may include the number of transmit or receive antennas, the number of MIMO layers supported for carrier aggregation, or the number of MIMO layers supported for dual connectivity. The base station can schedule the UE based on these configuration capabilities.

[0094] Figure 7 An operational flow / algorithm structure 700 according to some implementation schemes is illustrated. The operational flow / algorithm structure 700 is an example of the UE's ability to dynamically switch UE types. The operational flow / algorithm structure 700 may be implemented by the UE (e.g., UE 104 or UE 800) or components therein (e.g., processing circuitry 804).

[0095] The operation flow / algorithm structure 700 may include: at 710, generating a message indicating the type of UE that supports carrier aggregation operation or dual connectivity operation under co-location or non-co-location conditions.

[0096] The operation process / algorithm structure 700 may include: at 710, sending a message to the base station.

[0097] The UE may have a co-location condition-based configuration, such as a power imbalance of less than 6 dB or an MRTD of less than 3 µs. The UE may receive an indication associated with the condition from the network. The condition may be associated with a non-co-location condition. The UE may determine that the network indication is not associated with the configuration. The UE may switch its configuration to a non-co-location capability-based configuration, such as a power imbalance of less than 25 dB or an MRTD of less than 33 µs.

[0098] The UE may have a configuration based on non-co-location conditions, such as a power imbalance of less than 25 dB or an MRTD of less than 33 µs. The UE may receive an indication associated with the condition from the network. The condition may be associated with co-location conditions. The UE may determine that the network indication is not associated with the configuration. The UE may switch to a configuration based on co-location capabilities, such as a power imbalance of less than 6 dB or an MRTD of less than 3 µs.

[0099] Reconfiguration may include changing transmit or receive parameters, including reconfiguring the hardware or software associated with transmitter or receive operation. For example, a UE may reconfigure the radio frequency hardware associated with transmitter or receiver circuitry.

[0100] While the UE is undergoing reconfiguration, the UE may not expect to receive downlink control information from the base station. The UE can suspend monitoring of the downlink control channel. Monitoring the downlink control channel can refer to receiving or decoding the downlink control channel. The downlink control channel can be a PDCCH.

[0101] The base station can configure the UE using one or more triggering events associated with one or more co-located or non-co-located conditions. The UE can detect the triggering events.

[0102] For example, the UE may have a co-location condition-based configuration. This configuration may include up to four MIMO layers per component carrier, a maximum power imbalance of 6 dB, or a maximum MRTD of 3 µs. Detection of a triggering event can indicate the presence of a non-co-location condition. When the conditions associated with the triggering event are different from the conditions associated with the configuration, the UE can be reconfigured to a configuration that matches the associated event. In the example above, the UE can be reconfigured to a configuration associated with a non-co-location condition, such as up to two MIMO layers per component carrier, a maximum power imbalance of 25 dB, or a maximum MRTD of 33 µs.

[0103] In another example, the UE may have a configuration based on non-co-location conditions. This configuration may include up to two MIMO layers per component carrier, a maximum power imbalance of 25 dB, or a maximum MRTD of 33 µs. Detection of a triggering event can indicate the presence of co-location conditions. When the conditions associated with the triggering event and the conditions associated with the configuration are different, the UE can be reconfigured to a configuration matching the associated event. In the example above, the UE can be reconfigured to a configuration associated with co-location conditions, such as up to four MIMO layers per component carrier, a maximum power imbalance of 6 dB, or a maximum MRTD of 3 µs.

[0104] In some instances, the UE may receive a network indication. This network indication may be associated with co-location conditions. For example, the network (e.g., a base station) may determine, based on measurement reports received from the UE or by performing its own measurements, that carrier aggregation or dual connectivity at the UE satisfies co-location conditions. Based on the determination that the measurements associated with the UE satisfy the co-location conditions, the network may generate and transmit a network indication to the UE.

[0105] In other instances, network indications may be associated with non-co-location conditions. For example, a network (e.g., a base station) may determine, based on measurement reports received from the UE or by performing its own measurements, that carrier aggregation or dual connectivity at the UE meets non-co-location conditions (or does not meet co-location conditions, e.g., power imbalance not less than 6 dB or MRTD not less than 3 µs). Based on the determination that the measurements associated with the UE meet non-co-location conditions, the network may generate and transmit a network indication to the UE.

[0106] The UE can configure itself based on network indications. For example, when a network indication is associated with co-location conditions, the UE can use configurations associated with co-location conditions, such as a maximum of 4 MIMO layers per component carrier, a maximum power imbalance of 6 dB between aggregated CCs, or a maximum 3 µs MRTD between aggregated CCs. In another example, when a network indication is associated with non-co-location conditions, the UE can use configurations associated with non-co-location conditions, such as a maximum of 2 MIMO layers per component carrier, a maximum power imbalance of 25 dB between aggregated CCs, or a maximum 33 µs MRTD between aggregated CCs.

[0107] Figure 8 An example of a UE 800 according to some implementation schemes is shown. UE 800 may be similar to... Figure 1 It is compatible with UE 104 and is essentially interchangeable with it.

[0108] UE 800 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, XR device, glasses, industrial wireless sensors (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltmeter / ammeter, or actuator), video surveillance / monitoring device (e.g., camera or camcorder), wearable device (e.g., smartwatch), or Internet of Things device.

[0109] UE 800 may include a processor 804, RF interface circuitry 808, memory / storage device 812, user interface 816, sensor 820, drive circuitry 822, power management integrated circuit (PMIC) 824, antenna structure 826, and battery 828. The components of UE 800 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 8 The block diagram is intended to show a high-level view of some of the components of the UE 800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0110] The components of UE 800 can be coupled to various other components via one or more interconnects 832, which can represent any type of interface circuitry (e.g., processor interface or memory interface), input / output, bus (local, system, or extension), transmission line, trace, or optical connector, allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0111] Processor 804 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 804A, central processing unit circuitry (CPU) 804B, and graphics processing unit circuitry (GPU) 804C. Processor 804 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 812) to cause UE 800 to perform the operations described herein.

[0112] In some implementations, the baseband processor circuit 804A can access the communication protocol stack 836 in the memory / storage device 812 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 804A can access the communication protocol stack 836 to: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 808.

[0113] The baseband processor circuit 804A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0114] Memory / storage device 812 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 836) that can be executed by one or more processors in processor 804 to cause UE 800 to perform the various operations described herein. Memory / storage device 812 includes any type of volatile or non-volatile memory that can be distributed throughout UE 800. In some embodiments, some memory / storage devices in memory / storage device 812 may be located on processor 804 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 812 may be located external to processor 804 but accessible via a memory interface. Memory / storage device 812 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0115] RF interface circuitry 808 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 800 to communicate with other devices via a radio access network. RF interface circuitry 808 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0116] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 826, and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which down-converts the RF signal into a baseband signal, which is then provided to the baseband processor of processor 804.

[0117] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can then amplify the RF signal using a power amplifier before it is radiated across the air interface via antenna 826.

[0118] In various implementations, the RF interface circuit 808 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0119] Antenna 826 may include antenna elements to convert electrical signals into radio waves for propagation through the air, and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 826 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input multiple-output (MIMO) communication. Antenna 826 may include a microstrip antenna, patch antenna, phased array antenna, or a printed antenna fabricated on the surface of one or more printed circuit boards. Antenna 826 may have one or more panels designed for a specific frequency band, including bands in FR1 or FR2.

[0120] User interface circuitry 816 includes various input / output (I / O) devices designed to enable users to interact with UE 800. User interface 816 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced through the operation of UE 800.

[0121] Sensor 820 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEM) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other similar audio capture devices.

[0122] The driving circuitry 822 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 800. The driving circuitry 822 may include individual drivers that allow other components to interact with or control various I / O devices that may exist within or be connected to the UE 800. For example, the driving circuitry 822 may include circuitry for facilitating the coupling of a Universal Integrated Circuit Card (UICC) or a Universal Subscriber Identity Module (USIM) to the UE 800. Furthermore, the driving circuitry 822 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings from sensor circuitry 820 and controlling and allowing access to sensor circuitry 820; a driver for obtaining actuator positioning of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0123] The PMIC 824 manages the power supplied to various components of the UE 800. Specifically, relative to the processor 804, the PMIC 824 controls power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0124] In some implementations, the PMIC 824 may be controlled or otherwise incorporated into various power-saving mechanisms of the UE 800, including DRX, as discussed herein.

[0125] Battery 828 can power UE 800, but in some examples, UE 800 may be installed and deployed in a fixed location and may have a power source coupled to the power grid. Battery 828 may be a lithium-ion battery, a metal-air battery (such as zinc-air batteries, aluminum-air batteries, lithium-air batteries, etc.). In some specific implementations, such as in vehicle-based applications, battery 828 may be a typical lead-acid automotive battery.

[0126] Figure 9 A network node 900 is illustrated according to some implementation schemes. The network node 900 may be similar to or interchangeable with a base station 108, a device implementing a network hop, an integrated access and backhaul (IAB) node, a network control repeater, or a server in a core network or external data network.

[0127] Network node 900 may include processor 904, RF interface circuitry 908 (if implemented as an access node), core node (CN) interface circuitry 912, memory / storage device circuitry 916, and antenna structure 926.

[0128] The components of network node 900 can be coupled to various other components through one or more interconnects 932.

[0129] The processor 904, RF interface circuit 908, memory / storage device circuit 916 (including communication protocol stack 910), antenna structure 926, and interconnection section 932 can be similar to those described above. Figure 8 Similar-named elements are shown and described.

[0130] The CN interface circuit 912 can provide connectivity to a core network (e.g., a 5GC using a fifth-generation core network (5GC) compatible network interface protocol, such as Carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from network node 900 via fiber optic or wireless backhaul. The CN interface circuit 912 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 912 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0131] In some implementations, network node 900 may be coupled to transmit-receive point (TRP) using antenna structure 926, CN interface circuitry, or other interface circuitry.

[0132] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and disposed of to minimize the risk of unintentional or unauthorized access or use, and users should be clearly informed of the nature of authorized use.

[0133] For one or more aspects, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below in the Embodiments section.

[0134] Example Further exemplary aspects are provided in the following sections.

[0135] Example 1 includes a method implemented by a user equipment (UE), the method comprising: generating a message indicating a user equipment (UE) type that supports carrier aggregation operation or dual connectivity operation under co-location and non-co-location conditions; and sending the message to a base station.

[0136] Example 2 includes the method according to Example 1 or other embodiments herein, wherein the UE type has a first capability and a second capability, and the method further includes: determining a configuration corresponding to the first capability; receiving a network indication associated with co-location conditions or non-co-location conditions from a base station (BS); and switching the configuration corresponding to the second capability.

[0137] Example 3 includes the method according to Example 1 or 2 or other examples herein, the method further comprising: suspending monitoring of the downlink control channel for a certain period of time from a reference time associated with receiving the network indication.

[0138] Example 4 includes the method according to any one of Examples 1 to 3 or other embodiments herein, wherein the first capability is based on a co-location condition, the second capability is based on a non-co-location condition, and the network indication is associated with the non-co-location condition.

[0139] Example 5 includes the method according to any one of Examples 1 to 4 or other embodiments herein, wherein the first capability is associated with support for up to four multiple-input multiple-output (MIMO) layers for a first component carrier (CC), a power imbalance of less than or equal to 25 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 33 microseconds (µs).

[0140] Example 6 includes the method according to any one of Examples 1 to 5 or other embodiments herein, wherein the second capability is associated with support for up to two multiple-input multiple-output (MIMO) layers for a first component carrier (CC), a power imbalance of less than or equal to 6 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 3 microseconds between the first CC and the second CC.

[0141] Example 7 includes the method according to any one of Examples 1 to 6 or other embodiments herein, wherein the co-location condition includes a power imbalance between a first aggregated component carrier (CC) and a second aggregated CC less than a first power threshold or a maximum relative receive timing difference (MRTD) between the first aggregated CC and the second aggregated CC less than a first time threshold; and the non-co-location condition includes the power imbalance between the first aggregated CC and the second aggregated CC less than a second power threshold or the MRTD between the first aggregated CC and the second aggregated CC less than a second time threshold.

[0142] Example 8 includes the method according to any one of Examples 1 to 7 or other embodiments herein, wherein the first power threshold is 6 dB, the first time threshold is 3 μs, the second power threshold is 25 dB, and the second time threshold is 33 μs.

[0143] Example 9 includes the method according to any one of Examples 1 to 8 or other embodiments herein, wherein the first capability is based on a non-co-located condition, the second capability is based on a co-located condition, and the network indication is associated with the co-located condition.

[0144] Example 10 includes the method according to any one of Examples 1 to 9 or other embodiments herein, wherein the first capability is associated with support for up to two multiple-input multiple-output (MIMO) layers for a first component carrier (CC), a power imbalance of less than or equal to 6 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 3 microseconds between the first CC and the second CC.

[0145] Example 11 includes the method according to any one of Examples 1 to 10 or other embodiments herein, wherein the second capability is associated with support for up to four multiple-input multiple-output (MIMO) layers for a first component carrier (CC), a power imbalance of less than or equal to 25 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 33 microseconds (µs).

[0146] Example 12 includes the method according to any one of Examples 1 to 11 or other embodiments herein, wherein the co-location condition includes a power imbalance between a first aggregated component carrier (CC) and a second aggregated CC less than a first power threshold or a maximum relative receive timing difference (MRTD) between the first aggregated CC and the second aggregated CC less than a first time threshold; and the non-co-location condition includes the power imbalance between the first aggregated CC and the second aggregated CC less than a second power threshold or the MRTD between the first aggregated CC and the second aggregated CC less than a second time threshold.

[0147] Example 13 includes the method according to any one of Examples 1 to 12 or other embodiments herein, wherein the first power threshold is 6 dB, the first time threshold is 3 μs, the second power threshold is 25 dB, and the second time threshold is 33 μs.

[0148] Example 14 includes the method according to any one of Examples 1 to 13 or other embodiments herein, the method further comprising: determining a configuration corresponding to a first capability; receiving a configuration including a triggering event from a BS; detecting the triggering event; and performing a reconfiguration procedure associated with a second capability.

[0149] Example 15 includes the method according to any one of Examples 1 to 14 or other embodiments herein, wherein the reconfiguration procedure includes: transmitting to the BS an event indication associated with the detection of the triggering event; receiving from the BS a network indication associated with a co-location condition or a non-co-location condition; and reconfiguring based on the network indication.

[0150] Example 16 includes the method according to any one of Examples 1 to 15 or other embodiments herein, wherein the reconfiguration procedure includes: reconfiguring based on the triggering event; and transmitting to the BS an event indication associated with detecting the triggering event.

[0151] Example 17 includes the method according to any one of Examples 1 to 16 or other examples herein, the method further comprising: suspending monitoring of the downlink control channel for a certain period of time from a reference time associated with the reconfiguration procedure.

[0152] Example 18 includes the method according to any one of Examples 1 to 17 or other embodiments herein, wherein the triggering event includes a measurement and a corresponding threshold.

[0153] Example 19 includes the method according to any one of Examples 1 to 18 or other examples herein, wherein the measurement includes a receive timing difference (RTD) measurement, a relative reference signal received power (RSRP) measurement, or a channel state information (CSI) measurement.

[0154] Example 20 includes the method according to any one of Examples 1 to 19 or other embodiments herein, wherein the UE type has a first capability associated with co-location conditions and a second capability associated with non-co-location conditions, and the method further includes: receiving from a base station (BS) a network indication associated with co-location conditions or non-co-location conditions; and associating a configuration with: the first capability being associated with co-location conditions based on the network indication; or the second capability being associated with non-co-location conditions based on the network indication.

[0155] Example 21 includes a method comprising: receiving from a user equipment (UE) a message including a UE type, the UE type indicating that the UE supports carrier aggregation operation or dual connectivity operation under co-location and non-co-location conditions; determining conditions associated with the co-location or non-co-location conditions; and determining, based on the conditions or the UE type, to transmit a network indication to the UE.

[0156] Example 22 includes the method according to Example 21 or other embodiments herein, the method further comprising: determining a time alignment error (TAE) associated with the UE.

[0157] Example 23 includes the method according to Example 21 or 22 or other examples herein, wherein the determination of the conditions is based on the TAE.

[0158] Example 24 includes the method according to any one of Examples 21 to 23 or other embodiments herein, the method further comprising: determining the capability of the UE based on the message; determining transmission parameters based on the capability of the UE; and scheduling the UE based on the capability of the UE or the transmission parameters.

[0159] Example 25 includes the method according to any one of Examples 21 to 24 or other embodiments herein, wherein the transmission parameters include the number of multiple-input multiple-output (MIMO) layers supported on the component carriers, the maximum power imbalance between the first component carrier (CC) and the second CC, or the maximum relative receive time difference (MRTD) between the first CC and the second CC.

[0160] Example 26 includes the method according to any one of Examples 21 to 25 or other embodiments herein, the method further comprising: determining the capability of the UE based on the UE type; determining that the condition is not associated with the capability of the UE; transmitting a network indication to the UE; and suspending scheduling of the UE for a certain period of time.

[0161] Example 27 includes the method according to any one of Examples 21 to 26 or other embodiments herein, wherein the network indication is included in Radio Resource Control (RRC) signaling.

[0162] Example 28 includes a method comprising: receiving from a user equipment (UE) a message including a UE type, the UE type indicating that the UE supports carrier aggregation operation or dual connectivity operation under co-location and non-co-location conditions; transmitting to the UE a configuration including triggering events associated with the co-location or non-co-location conditions; and receiving an event indication from the UE.

[0163] Example 29 includes the method according to Example 28 or other embodiments herein, the method further comprising: determining, based on the event indication, that the triggering event was detected by the UE; and suspending the scheduling of the UE for a certain period of time.

[0164] Example 30 includes the method according to Example 28 or 29 or other embodiments herein, the method further comprising: determining a co-location condition or a non-co-location condition based on the event indication.

[0165] Example 31 includes the method according to any one of Examples 28 to 30 or other embodiments herein, wherein the triggering event includes a measurement or a threshold associated with the measurement.

[0166] Example 32 includes the method according to any one of Examples 28 to 31 or other examples herein, wherein the measurement includes a receive timing difference (RTD) measurement, a relative reference signal received power (RSRP) measurement, or a channel state information (CSI) measurement.

[0167] Another embodiment may include an apparatus comprising one or more elements for performing the methods described or associated with any one of embodiments 1 to 31 or any other methods or processes described herein.

[0168] Another embodiment may include the methods, techniques or processes described or associated with any one of embodiments 1 to 32 or any part or component thereof.

[0169] Another embodiment may include an apparatus comprising: one or more processors; and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described or associated with any one or more of embodiments 1 to 32.

[0170] Another embodiment includes signals described or associated with any one of embodiments 1 to 32, or a portion or component thereof.

[0171] Another embodiment may include datagrams, information elements, packets, frames, segments, PDUs, or messages as described or associated with any one of embodiments 1 to 32 or any part or component thereof, or otherwise described in this disclosure.

[0172] Another embodiment may include a signal encoded with data as described or associated with any one of embodiments 1 to 32 or a portion or component thereof, or otherwise described in this disclosure.

[0173] Another embodiment may include signals encoded as datagrams, IEs, packets, frames, segments, PDUs, or messages as described or associated with any one of embodiments 1 to 32 or any part or component thereof, or otherwise described in this disclosure.

[0174] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process described or associated with any one or a portion thereof according to Embodiments 1 to 32.

[0175] Another embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process described or associated with any one or a portion thereof according to Embodiments 1 to 32.

[0176] Another embodiment may include signals in a wireless network as shown and described herein.

[0177] Another embodiment may include a method for communicating in a wireless network as shown and described herein.

[0178] Another embodiment may include a system for providing wireless communication as shown and described herein.

[0179] Another embodiment may include a device for providing wireless communication as shown and described herein.

[0180] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the various aspects to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice in various aspects.

[0181] Although the foregoing aspects have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the foregoing disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method, the method comprising: Generate a message indicating the type of user equipment (UE) that supports carrier aggregation operation or dual connectivity operation under co-location and non-co-location conditions; as well as The message is sent to the base station.

2. The method of claim 1, wherein the UE type has a first capability associated with the co-location condition and a second capability associated with the non-co-location condition, and the method further comprises: Receive network indication associated with the co-location condition or the non-co-location condition from the base station (BS); as well as Associate the configuration with the following items: The first capability is associated with the network indication and co-location conditions; or The second capability is associated with the network indication and non-co-located conditions.

3. The method according to claim 2, wherein the method further comprises: Monitoring of the downlink control channel is suspended for a certain period of time, starting from a reference time associated with receiving the network indication.

4. The method of claim 2, wherein the first capability is associated with support for up to four multiple-input multiple-output (MIMO) layers for a first component carrier (CC), a power imbalance of less than or equal to 6 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 3 microseconds (µs).

5. The method of claim 2, wherein the second capability is associated with support for up to two multiple-input multiple-output (MIMO) layers for the first component carrier (CC), a power imbalance of less than or equal to 25 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 33 microseconds between the first CC and the second CC.

6. The method according to claim 2, wherein: The co-location conditions include a power imbalance between the first aggregated component carrier (CC) and the second aggregated CC being less than a first power threshold, or a maximum relative receive timing difference (MRTD) between the first aggregated CC and the second aggregated CC being less than a first time threshold; and The non-co-located condition includes the power imbalance between the first aggregated CC and the second aggregated CC being less than a second power threshold, or the MRTD between the first aggregated CC and the second aggregated CC being less than a second time threshold.

7. The method of claim 1, wherein the UE type has a first capability and a second capability, and the method further comprises: Determine the configuration corresponding to the first capability; Receive network indications associated with co-location or non-co-location conditions from the base station (BS); as well as Switch the configuration corresponding to the second capability.

8. The method according to claim 7, wherein the method further comprises: Monitoring of the downlink control channel is suspended for a certain period of time, starting from a reference time associated with receiving the network indication.

9. The method of claim 7, wherein the first capability is based on co-location conditions, the second capability is based on non-co-location conditions, and the network indication is associated with the non-co-location conditions.

10. The method of claim 9, wherein the first capability is associated with support for up to four multiple-input multiple-output (MIMO) layers for a first component carrier (CC), a power imbalance of less than or equal to 6 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 3 microseconds (µs).

11. The method of claim 9, wherein the second capability is associated with support for up to two multiple-input multiple-output (MIMO) layers for the first component carrier (CC), a power imbalance of less than or equal to 25 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 33 microseconds between the first CC and the second CC.

12. The method of claim 9, wherein: The co-location conditions include a power imbalance between the first aggregated component carrier (CC) and the second aggregated CC being less than a first power threshold, or a maximum relative receive timing difference (MRTD) between the first aggregated CC and the second aggregated CC being less than a first time threshold; and The non-co-located condition includes the power imbalance between the first aggregated CC and the second aggregated CC being less than a second power threshold, or the MRTD between the first aggregated CC and the second aggregated CC being less than a second time threshold.

13. The method of claim 12, wherein the first power threshold is 6 dB, the first time threshold is 3 μs, the second power threshold is 25 dB, and the second time threshold is 33 μs.

14. The method of claim 7, wherein the first capability is based on a non-co-located condition, the second capability is based on a co-located condition, and the network indication is associated with the co-located condition.

15. The method of claim 14, wherein the first capability is associated with support for up to two multiple-input multiple-output (MIMO) layers for a first component carrier (CC), a power imbalance of less than or equal to 25 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 33 microseconds between the first CC and the second CC.

16. The method of claim 14, wherein the second capability is associated with support for up to four multiple-input multiple-output (MIMO) layers for the first component carrier (CC), a power imbalance of less than or equal to 6 dB between the first CC and the second CC, or a maximum relative receive timing difference (MRTD) of less than or equal to 3 microseconds (µs).

17. The method of claim 14, wherein: The co-location conditions include a power imbalance between the first aggregated component carrier (CC) and the second aggregated CC being less than a first power threshold, or a maximum relative receive timing difference (MRTD) between the first aggregated CC and the second aggregated CC being less than a first time threshold; and The non-co-located condition includes the power imbalance between the first aggregated CC and the second aggregated CC being less than a second power threshold, or the MRTD between the first aggregated CC and the second aggregated CC being less than a second time threshold.

18. The method of claim 17, wherein the first power threshold is 6 dB, the first time threshold is 3 μs, the second power threshold is 25 dB, and the second time threshold is 33 μs.

19. The method according to claim 1, wherein the method further comprises: Determine the configuration corresponding to the primary capability; Receive configuration, including trigger events, from the BS; Detect the triggering event; as well as Perform the reconfiguration procedures associated with the second capability.

20. The method of claim 19, wherein the reconfiguration procedure comprises: Transmit an event indication associated with the detection of the triggering event to the BS; Receive network indications associated with co-location or non-co-location conditions from the BS; as well as Reconfigure based on the network instructions.

21. The method of claim 19, wherein the reconfiguration procedure comprises: Reconfiguration is performed based on the triggering event; as well as The BS is sent an event indication associated with the detection of the triggering event.

22. The method of claim 19, further comprising: Monitoring of the downlink control channel is suspended for a certain period of time, starting from a reference time associated with the reconfiguration procedure.

23. The method of claim 19, wherein the triggering event comprises a measurement and a corresponding threshold.

24. The method of claim 23, wherein the measurement includes a received timing difference (RTD) measurement, a relative reference signal received power (RSRP) measurement, or a channel state information (CSI) measurement.

25. A network element, the network element comprising: The memory is used to store information associated with co-address conditions and non-co-address conditions; and Processing circuitry, the processing circuitry being coupled to the memory to: Receive a message from the user equipment (UE) including the UE type, the UE type indicating that the UE supports carrier aggregation operation or dual connectivity operation under the co-location condition and the non-co-location condition; Determine the conditions associated with co-location or non-co-location conditions; as well as Based on the conditions or the UE type, it is determined whether to transmit a network instruction to the UE.

26. The network element of claim 25, wherein the processing circuitry is further configured to: Determine the time alignment error (TAE) associated with the UE.

27. The network element of claim 26, wherein the determination of the condition is based on the TAE.

28. The network element of claim 25, wherein the processing circuitry is further configured to: The capabilities of the UE are determined based on the message; Based on the capabilities of the UE, the transmission parameters are determined; and The UE is scheduled based on its capabilities or transmission parameters.

29. The network element of claim 28, wherein the transmission parameters include multiple multiple-input multiple-output (MIMO) layers supported on component carriers, maximum power imbalance between the first component carrier (CC) and the second CC, or maximum relative receive time difference (MRTD) between the first CC and the second CC.

30. The network element of claim 25, wherein the processing circuitry is further configured to: Determine the capabilities of the UE based on the UE type; It is determined that the condition is not associated with the capability of the UE; Transmit network instructions to the UE; and The scheduling of the UE is suspended for a certain period of time.

31. The network element of claim 30, wherein the network indication is included in Radio Resource Control (RRC) signaling.

32. One or more computer-readable media having instructions that, when executed by one or more processors, cause network elements to: Receive a message from the user equipment (UE) including the UE type, which indicates that the UE supports carrier aggregation operation or dual connectivity operation under co-location and non-co-location conditions; Transmit to the UE a configuration including trigger events associated with co-location conditions or non-co-location conditions; and Receive event indications from the UE.

33. One or more computer-readable media according to claim 32, wherein the instructions, when executed, further cause the network element to: Based on the event indication, it is determined that the UE detected the triggering event; and The scheduling of the UE is suspended for a certain period of time.

34. One or more computer-readable media according to claim 32, wherein the instructions, when executed, further cause the network element to: The co-location condition or non-co-location condition is determined based on the event indication.

35. One or more computer-readable media according to claim 32, wherein the triggering event includes a measurement or a threshold associated with the measurement.

36. One or more computer-readable media according to claim 35, wherein the measurement includes a receive timing difference (RTD) measurement, a relative reference signal received power (RSRP) measurement, or a channel state information (CSI) measurement.

Images