Energy saving in communication equipment

Abstract

A user equipment capable of operating with dual-mode connectivity with a primary node and a secondary node detects a low battery condition of the UE's battery (2302). In response, the user equipment prevents the UE from operating with the SN in DC mode, such that the UE and the MN are configured to operate with single connectivity (2304).

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly, to using dual connectivity (DC) and single connectivity (SC) when a communication device battery experiences a low-battery condition. Background Art

[0002] In some cases, a user equipment (or user device, often denoted by the abbreviation "UE") can operate in DC with a master node (MN) and a secondary node (SN). The MN and SN are base stations that can operate according to the same radio access technology (RAT) or according to different RATs in a multi-radio DC (MR-DC) configuration. Depending on the type of core network (CN), two configurations in which the MN supports Evolved Universal Terrestrial Radio Access (EUTRA) and the SN supports 5G New Radio (NR) are called EN-DC and NGEN-DC. The configuration in which the MN supports NR and the SN supports EUTRA is called NE-DC. In yet another configuration, NR-NRDC, both the MN and the SN support NR. For example, various DC configurations are described in the Third Generation Partnership Project (3GPP) standard TS 37.340 v.15.4.0.

[0003] The MN can provide control plane connectivity and user plane connectivity to the CN, while the SN typically provides the user plane connectivity. The cell associated with the MN defines a master cell group (MCG), and the cell associated with the SN defines a secondary cell group (SCG). The UE and the base stations MN and SN can use signaling radio bearers (SRBs) to exchange radio resource control (RRC) messages and non-access stratum (NAS) messages. The UE can use several types of SRBs when operating in DC. SRB1 and SRB2 resources allow the UE and MN to exchange RRC messages related to the MN and embed RRC messages related to the SN, and can be called MCG SRBs. SRB3 resources allow the UE and SN to exchange RRC messages related to the SN, and can be called SCG SRBs. Separate SRBs allow the UE to exchange RRC messages directly with the MN by using the radio resources of the MN, the SN, or both the MN and the SN. In addition, the UE and the base stations MN and SN use data radio bearers (DRBs) to transmit data on the user plane. A DRB that terminates at an MN and uses only the lower layer resources of the MN may be referred to as an MCG DRB, a DRB that terminates at an SN and uses only the lower layer resources of the SN may be referred to as an SCG DRB, and a DRB that terminates at an MCG but uses the lower layer resources of both the MN and the SN may be referred to as a split DRB.

[0004] A UE operating with both the mobile node and the network subnet (SN) in DC mode typically consumes more power than when operating in SC mode. Furthermore, when the mobile node and the network subnet (SN) operate according to different RATs, the UE may need to operate two separate chipsets. When the battery is low, DC operation can consume significant power, causing the UE to be unable to make emergency calls or shut down completely. Summary of the Invention

[0005] According to the techniques of the present disclosure, a UE detects a low battery condition (e.g., a remaining battery level below a threshold level) of the battery and prevents the UE from operating in DC with the MN and SN. However, the UE can operate in SC with the MN (i.e., a base station operating as the MN in a DC scenario). Because the UE is not connected to the SN, the UE reduces power consumption. After the UE determines that the low battery condition no longer applies (e.g., the battery is receiving a charge from a power source), the UE enables DC operation with the MN and SN.

[0006] In some embodiments, the UE sends an explicit indication (e.g., a UE Capability Information message) to the MN to inform the MN whether the UE has enabled or disabled DC. In some embodiments, the UE includes a DC band combination, a DC support indicator, or a list of DC supported bands in the radio access capability IE of the UE Capability Information message to indicate that the UE has enabled DC. To indicate that the UE has disabled DC, the UE excludes this information in the UE Capability Information message.

[0007] Alternatively, the UE may implicitly inform the MN about the current state of DC at the UE. In some embodiments, the UE suspends measurement reporting for the SN's carrier frequency or suspends measurements altogether. In other embodiments, the UE sends "artificial" measurement reports that simulate low signal strength and / or low signal quality of the SN's carrier frequency to the MN, regardless of whether the signal strength and / or signal quality are actually low. In this way, the UE prevents the MN from configuring the UE to use the SN's carrier frequency in DC.

[0008] When a UE uses different chipsets (e.g., modems) to communicate with a mobile node and a network service provider (SN) using different corresponding RATs or using the same RAT, the UE can disable DC operation by shutting down one of the chipsets used to support the SN's RAT. In another embodiment, the UE deactivates the chipet used to support the SN's RAT without shutting down the chipet to stop monitoring one or more carrier frequencies of the SN. In this way, the UE prevents itself from operating in DC with the SN while remaining able to monitor one or more carrier frequencies of the mobile node. Thus, the UE retains SC capability.

[0009] In addition to enabling or disabling DC operation, in some embodiments, the UE also enables or disables MN carrier aggregation (CA) in response to detecting the same low battery condition of the battery or another (e.g., more severe) low battery condition of the battery. In some embodiments, the UE includes the MN CA band combination in the radio access capability IE of the UE capability information message to indicate that the UE has enabled CA. To indicate that the UE has disabled CA, the UE excludes this information in the UE capability information message. In some embodiments, the UE disables DC when the battery charge level reaches a certain threshold level, and then disables CA when the battery charge level reaches another lower threshold level. In other embodiments, the UE disables DC and CA when the battery charge level reaches the same threshold level.

[0010] In some embodiments, to avoid interruptions in data usage (e.g., dropped calls, lower data rates), if the UE detects a predetermined operating condition (e.g., the UE is currently engaged in a voice or video call, the UE's screen is on, the UE's power saving features have been disabled), the UE postpones disabling DC operation due to a low battery condition.

[0011] In an exemplary scenario, a UE operating in EN-DC or NGEN-DC detects a low battery condition and, in response, disables DC operation. The UE transmits a UE Capability Information message to the master Evolved Node B (MeNB) or master Next Generation eNB (Mng-eNB), depending on the configuration, indicating that the UE has disabled DC capability for NR connections. The UE uses EUTRA SRB1 to send the UE Capability Information message to the base station.

[0012] Alternatively, instead of sending a UE Capability Information message to explicitly indicate that the UE has disabled DC capability, the UE may prevent the MeNB (or Mng-eNB in the case of NGEN-DC configuration) from obtaining measurements on the frequency carriers of the SgNB, thereby preventing NR connections to the SgNB. The UE may prevent the MeNB or Mng-eNB from obtaining measurements on the frequency carriers of the SgNB by suspending measurement reporting of the SN carrier frequency, suspending measurements entirely, or sending "artificial" measurement reports that simulate low signal strength and / or low signal quality of the SgNB's carrier frequency to the MeNB (Mng-eNB in the case of NGEN-DC) (regardless of whether the signal strength and / or signal quality are actually low).

[0013] In another exemplary scenario, a UE operating in NE-DC or NR-NR DC detects a low battery condition of the UE's battery and, in response, disables DC operation. The UE then sends a UE Capability Information message to the MgNB (indicating that the UE has disabled DC capability) using NR SRB1, or alternatively, prevents the MgNB from acquiring measurements on the frequency carriers of the Sng-eNB or SgNB.

[0014] In some embodiments, the UE sends an indication of SCG failure or MCG failure to the MN to prevent the MN from performing the process of recovering from the SCG failure or MCG failure. By detecting the SCG failure or MCG failure and suspending the corresponding SCG transmission and MCG transmission, the UE effectively disables the DC capability.

[0015] In some implementations, the UE sends an artificial measurement report to the MN or SN to cause the MN or SN to initiate SN release. The artificial measurement report simulates low signal strength and / or low signal quality of the SN's carrier frequency, regardless of whether the signal strength and / or signal quality are actually low. By releasing the SN, the UE effectively disables the DC capability.

[0016] An exemplary embodiment of these techniques is a method in a UE capable of operating in DC with a mobile node and a network node, the UE being operable using processing hardware to perform the method. The method includes detecting a low battery condition in a battery of the UE. In response to detecting the low battery condition, the method prevents the UE from operating in DC with the network node, such that the UE and the mobile node are configured to operate in SC.

[0017] Another exemplary embodiment of these techniques is a UE having processing hardware configured to implement the above-described method. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a block diagram of an exemplary wireless communication network in which a UE capable of operating in DC with a MN and a SN determines whether to operate in DC in view of a low battery condition of a battery of the UE;

[0019] Figure 2 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE of FIG. 1 for determining whether the UE should disable DC capability and (optionally) CA capability in view of a low battery condition of a battery;

[0020] Figure 3 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE of a battery for determining whether the UE should disable DC capability in view of one low battery condition of the battery, and determining whether the UE should disable CA capability in view of another low battery condition of the battery;

[0021] Figure 4 is a messaging diagram for an exemplary scenario in which a UE prevents a MN from initiating an SN add procedure by using an explicit indication that the UE has disabled DC capability;

[0022] Figure 5 is a messaging diagram for an exemplary scenario in which a UE operating in an idle or inactive state of the RRC protocol disables DC capability in response to detecting a low battery condition of the battery;

[0023] Figure 6 is a messaging diagram for an exemplary scenario in which a UE operating in a connected state of the RRC protocol defers disabling DC capability after detecting a low charge condition of a battery;

[0024] Figure 7 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE of FIG. 1 for determining whether the UE should disable DC capability and (optionally) CA capability in response to detecting a predetermined operating condition before detecting a low battery condition of a battery;

[0025] Figure 8 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE of FIG. 1 for determining whether the UE should disable DC capability and (optionally) CA capability in response to detecting a low battery condition of a battery before detecting a predetermined operating condition;

[0026] Figure 9 Yes, you can Figure 1 Flowchart of another exemplary method implemented in a UE for determining whether the UE should disable DC capability and (optionally) CA capability in response to detecting a predetermined operating condition before detecting a low battery condition of a battery;

[0027] Figure 10 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE for determining whether the UE should disable DC capability in response to detecting a low battery condition of a battery before detecting a certain operating condition, and determining whether the UE should disable CA capability in view of detecting another low battery condition of the battery before detecting the certain operating condition;

[0028] Figure 11 is a message passing diagram of an exemplary scenario in which, in response to the UE detecting a low battery condition of a battery, a UE operating in an idle or inactive state of the RRC protocol prevents a MN from initiating an SN addition procedure by not providing measurement reports about the SN;

[0029] Figure 12is a message transfer diagram of an exemplary scenario, in which a UE operating in the connected state of the RRC protocol prevents a MN from initiating a SN adding procedure by not providing measurement reports related to the SN.

[0030] Figure 13 is a message passing diagram for an exemplary scenario, in which the UE prevents the MN from initiating the SN addition procedure by sending an indication of SCG failure to the MN;

[0031] Figure 14 is a message passing diagram for an exemplary scenario, in which the UE prevents the MN from initiating the SN addition procedure by sending an indication of MCG failure to the MN;

[0032] Figure 15 is a message passing diagram for an exemplary scenario, where the UE enables the MN to initiate SN release by providing an “artificial” measurement report related to the SN;

[0033] Figure 16 is a message passing diagram for an exemplary scenario, where the UE causes the SN to initiate SN release by providing an “artificial” measurement report related to the SN;

[0034] Figure 17 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE of FIG. 1 for determining whether the UE should disable 5G NR operation for DC and (optionally) CA capability based on detection of a low battery condition of a battery;

[0035] Figure 18 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE of FIG. 1 for determining whether a UE operating in a connected state of the RRC protocol should disable 5G NR operation for DC in view of detecting a low battery condition of a battery;

[0036] Figure 19 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE for determining whether a UE operating in an idle or inactive state of the RRC protocol should disable 5G NR operation for DC in view of detecting a low battery condition of a battery;

[0037] Figure 20 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE of FIG. 1 for determining whether the UE should disable 5G NR operation in DC based on a low battery condition of the battery, and determining whether the UE should disable CA capability based on another low battery condition of the battery;

[0038] Figure 21is a flow chart of an exemplary scenario in which, upon detecting a low battery condition of a battery, the UE releases one or more carrier frequencies of the SN;

[0039] Figure 22 is a flow chart of an exemplary scenario in which the UE prevents the MN from initiating the SN Addition procedure in view of an "artificial" measurement report and an indication of an SCG failure; and

[0040] Figure 23 Yes, you can Figure 1 Flowchart of an exemplary method implemented in a UE for preventing the UE from operating in DC due to a low battery condition of the battery. DETAILED DESCRIPTION

[0041] Figure 1 An exemplary wireless communication network 100 is depicted in which a UE 102 equipped with a battery 103 is capable of operating in DC with a MN 104 and a SN 106, or in SC with either the MN 104 or the SN 106. To more efficiently utilize the power of the battery 103, the UE 102 (which may be any suitable device capable of wireless communication, as described below) may implement the techniques described below to disable the DC capability in certain circumstances while continuing to use SC. As discussed in detail below, the UE 102 explicitly or implicitly indicates to the MN 104 that the UE 102 has disabled the DC capability.

[0042] More specifically, the UE 102 is equipped with processing hardware 110, which may include one or more general-purpose processors (such as central processing units (CPUs)) and non-transitory computer-readable memory for storing machine-readable instructions that can be executed on one or more general-purpose processors and / or special-purpose processing units. The processing hardware 110 in the exemplary embodiment includes an EUTRA module 114 and an NR module 116. The EUTRA module 114 can be an RF chip (such as a modem) that is configured to modulate the carrier frequency of a base station with EUTRA capabilities to encode digital information for transmission and demodulate the carrier frequency to decode transmission information from the base station with EUTRA capabilities. Similarly, the NR module 116 can be an RF chip (such as a modem) that is configured to handle communications with a base station with NR capabilities. Therefore, the UE 102 is capable of communicating with the MN 104 and the SN 106 via different RATs (such as EUTRA and NR), respectively.

[0043] In another embodiment, the processing hardware 110 includes only the EUTRA module 114, the MN 104 and the SN 106 are both eNBs, and the UE 102 communicates with the MN 104 and the SN 106 via the same RAT (EUTRA). In yet another exemplary embodiment, the processing hardware 110 includes only the NR module 116, the MN 104 and the SN 106 are both gNBs, and the UE 102 communicates with the MN 104 and the SN 106 via 5G NR. In another embodiment, the MN 104 is a gNB and the SN 106 is a 6G base station that provides radio resources on a carrier frequency greater than 100 GHz or even in the THz range. More generally, each of the MN 104 and the SN 106 can operate according to any suitable RAT, and the UE 102 can include corresponding single-RAT or dual-RAT capabilities.

[0044] The processing hardware 110 further includes a DC controller 118 that is configured, in part, to determine when the UE 102 should operate in DC or only in SC. The DC controller 118 can make this determination based on the state of the battery 103, in some cases one or more other operating conditions (such as whether the screen of the UE 102 (not shown to avoid clutter) is currently on, whether the UE 102 is currently in an audio or video call, whether the user of the UE 102 has activated a power saving feature, etc.), and in some cases the temperature level of one or more components of the UE 102 or the processing hardware 110.

[0045] The DC controller 118 can receive an indication of the current state of the battery 103 from the power management module 120. The indication can be, for example, a periodic report indicating the current charge level of the battery 103 (e.g., 90%, 55%, 8%), a real-time indication that the charge level has reached a certain threshold, or any other suitable value or set of values. For example, the power management module 120 can operate as a component of the operating system (OS) of the UE 102 or as a firmware component. In addition, in some embodiments, the power management module 120 determines the initial capacity of the battery 103, the rate at which the charge level of the battery 103 is changing, the rate at which the UE 102 is currently consuming charge, the total capacity of the battery 103, and / or other metrics that the DC controller 118 can use to determine whether the UE 102 should operate in DC or limit the UE 102 to SC.

[0046] In some embodiments, the processing hardware 110 includes a thermal management module 122 configured to determine the temperature of one or more of the various components of the processing hardware 110 discussed above. The thermal management module 122 may include any suitable type of temperature sensor. The DC controller 118 may receive an indication of the temperature of the UE 102 from the thermal management module 122. The indication may be, for example, a periodic report indicating the current temperature of the battery 103, the NR EUTRA module 114, the NR module 116, and / or the DC controller 118 (e.g., 90°F, 96°F, 75°F, 26°C), a real-time indication that a temperature level has reached a certain threshold, or any other suitable value or set of values.

[0047] Furthermore, in some cases, the power management module 120 determines that the UE 102 is connected to a power source, such as an alternating current (AC) power charger or a direct current (DC) power external battery, a "power bank" portable charger, or a wireless charger. In one exemplary embodiment, the power management module 120 may determine that the low battery condition does not apply even if the current charge level of the battery 103 is below a certain threshold. In other words, in this case, the power management module 120 determines that the power source is likely to restore the charge level of the battery 103 in the near future.

[0048] In operation, the DC controller 118 may detect a low battery condition of the battery 103 by using one or more reports from the power management module 120. For example, the DC controller 118 may detect a low battery condition of the battery 103 by comparing the remaining charge level to a certain threshold level stored in a memory of the UE 102. The threshold level may correspond to a certain remaining battery capacity (e.g., a percentage or value of the remaining charge or capacity of the battery, such as 10%).

[0049] As discussed in more detail below, the DC controller 118 can disable the DC capability in response to detecting a low charge condition of the battery 103. However, disabling the DC capability can prevent the UE 102 and the SN 106 from operating in DC, so that the UE 102 and the MN 104 can operate in SC. The DC controller 118 can generate an indication and send it to the MN 104, such as by suspending measurement reporting of the carrier frequency of the SN 106, suspending measurements entirely, or sending an "artificial" measurement report that simulates low signal strength and / or low signal quality of the carrier frequency of the SN 106 to the MN 104 (regardless of whether the signal strength and / or signal quality are actually low), or alternatively, prevent the MN 104 from acquiring measurements of the frequency carrier of the SN 106. In some embodiments, the UE 102 can completely disable the EUTRA module 114 or the NR module 116, or disable the frequency measurement functionality of the modules without completely disabling the modules.

[0050] The UE 102 is capable of operating with the MN 104 covering an MCG 124 consisting of one or more cells, and the SN 106 covering an SCG 126 consisting of one or more cells. In some scenarios discussed below, the UE may detect an SCG failure or an MCG failure and, in response to detecting the SCG failure or the MCG failure, send an indication of the SCG failure or the MCG failure to the MN 104.

[0051] In different configurations of the network 100, the MN 104 can be implemented as a master eNB (MeNB) or a master gNB (MgNB) node, the SN 106 can be implemented as a secondary eNB (SeNB) or a secondary gNB (SgNB) node, and the UE 102 communicates with the MN 104 and the SN 106 via the same RAT (such as EUTRA or NR) or different RATs (such as EUTRA and NR). In some cases, the MeNB or SeNB is implemented as an ng-eNB instead of an eNB. The MN 104 and the SN 106 can be connected to a core network 110. For example, the core network (CN) 110 can be a 5G core network (5GC) or an evolved packet core (EPC). Some of these exemplary configurations will be discussed in more detail below.

[0052] Next, refer to Figure 2-17 , discusses several exemplary methods and scenarios corresponding to different DC configurations and / or different UE implementations. Each method discussed below can be implemented using hardware, software, firmware, or any suitable combination of hardware, software, and firmware.

[0053] Figure 2 Depicted is an exemplary method 200 for determining whether a UE 102 should disable DC capabilities and (optionally) CA capabilities in view of a low battery condition.

[0054] Method 200 begins at block 202, where UE 102 determines whether a low battery condition has occurred in battery 103. For example, DC controller 118 may process one or more reports from power management 120 to determine whether the remaining charge of battery 103 is above a certain level, whether the rate at which UE 102 consumes power is above a certain level, etc. (see discussion above). If UE 102 does not detect a low battery condition, then at block 204, UE 102 enables the DC capability when it was previously disabled. In another scenario, when the DC capability was already enabled, UE 102 maintains the DC capability enabled. However, if UE 102 detects a low battery condition, then if the DC capability was previously enabled, UE 102 disables the DC capability at block 208. In another scenario, when the DC capability was already disabled, UE 102 maintains the DC capability disabled.

[0055] In some embodiments, in addition to enabling or disabling DC capability, UE 102 also enables or disables MN CA capability based on a low battery condition of battery 103. Specifically, if UE 102 does not detect a low battery condition, then if the MN CA capability was previously disabled, then at block 206, UE 102 enables the MN CA capability. In another scenario, if the MN CA capability was already enabled, then UE 102 maintains the MN CA capability enabled. Thus, according to method 200, when battery 103 has sufficient charge, UE 102 transmits and receives data at a higher rate using MN CA. However, if UE 102 detects a low battery condition, then if the MN CA capability was previously enabled, then UE 102 disables the MN CA capability at block 210. If the MN CA capability was already disabled, then UE 102 maintains the MN CA capability disabled.

[0056] Despite Figure 2 The method 200 is shown as being complete after either block 206 or block 210 , but in general, the UE 102 may perform the method 200 in an iterative manner, for example, by “looping back” to block 202 after performing block 206 or block 210 .

[0057] Figure 3 An exemplary method 300 is depicted for determining whether the UE 102 should disable DC capabilities in view of one low battery condition of the battery and determining whether the UE should disable CA capabilities in view of another low battery condition of the battery.

[0058] Method 300 begins at block 302 where a process similar to Figure 2At block 202 of the UE 102, the UE 102 determines whether a low battery condition has occurred in the battery 103 (e.g., a remaining battery level is below a first threshold level). If the UE 102 does not detect a low battery condition, then at block 304, if the DC capability was previously disabled, the UE 102 enables the DC capability. In another scenario, if the DC capability was already enabled, the UE 102 maintains the DC capability enabled. However, if the UE 102 detects a low battery condition, then if the DC capability was previously enabled, the UE 102 disables the DC capability at block 308. In another scenario, if the DC capability was already disabled, the UE 102 maintains the DC capability disabled.

[0059] In some embodiments, in addition to enabling or disabling DC capability, UE 102 enables MN CA capability for the same low battery condition, but disables MN CA capability for a different low battery condition (e.g., a remaining battery level below a second threshold level that is lower than the first threshold level). Specifically, if UE 102 does not detect the same low battery condition, then if the MN CA capability was previously disabled, UE 102 enables MN CA capability at block 306. In another scenario, if the MN CA capability was already enabled, UE 102 keeps the MN CA capability enabled. However, if UE 102 detects a different low battery condition at block 309, then if the MN CA capability was already enabled, then UE 102 disables the MN CA capability at block 310. In another scenario, if the MN CA capability was previously disabled, then UE 102 keeps the MN CA capability disabled. If, at block 309, UE 102 does not detect a different low battery condition, then if the MN CA capability was previously disabled, then UE 102 enables MN CA capability at block 306. In another scenario, if the MN CA capability is already enabled, the UE 102 keeps the MN CA capability enabled.

[0060] Despite Figure 3 The method 300 is shown to be complete after either block 306 or block 310, but generally, the UE 102 may perform the method 300 in an iterative manner, for example, by "looping back" to block 302 or block 309, respectively, after performing block 306 or 310.

[0061] Figure 4 An exemplary messaging diagram 400 is depicted for an exemplary scenario in which the UE 102 prevents the MN 104 from initiating an SN add procedure by using an explicit indication that the UE 102 has disabled DC capability.

[0062] At the start of the scenario, UE 102 performs a first NAS procedure (402) with CN 110 via MN 104. If the UE operates in EN-DC and therefore communicates with CN 110 implemented as EPC, the first NAS procedure may be, for example, a first attach procedure or a first tracking area update procedure as defined in 3GPP TS 24.301.

[0063] To begin the first attach procedure, UE 102 sends an Attach Request message to the Mobility Management Entity (MME) of CN 110 and, in response, receives an Attach Accept message from the MME. UE 102 then sends an Attach Complete message to the MME. As another example, to begin the first Tracking Area Update procedure, UE 102 sends a Tracking Area Update Request message to the MME and, in response, receives a Tracking Area Update Accept message from the MME. UE 102 then sends a Tracking Area Update Complete message to the MME in response to the Tracking Area Update Accept message.

[0064] If UE 102 is operating in NGEN-DC, NR-NR DC, or NE-DC and is therefore communicating with CN 110 implemented as a 5GC, the first NAS procedure may be a registration procedure defined in 3GPP TS 24.501. To begin the first registration procedure, UE 102 sends a Registration Request message to the Access and Mobility Management Function (AMF) of CN 110 and, in response, receives a Registration Accept message from the AMF. UE 102 then sends a Registration Complete message to the AMF.

[0065] exist Figure 4 In the scenario of FIG. 4 , UE 102 generates a clear indication (e.g., a first UE capability information message) to inform MN 104 that UE 102 supports DC capability. MN 104 may send the indication to CN 110. In some embodiments, UE 102 sends 404 the indication during the first NAS procedure. In other embodiments, UE 102 sends 404 the indication after completing the first NAS procedure.

[0066] In some embodiments, UE 102 indicates in a NAS message of the first NAS procedure (e.g., an attach request message, an attach complete message, a registration request message, or a registration complete message) that UE 102 is capable of DC. Then, CN 110 (e.g., MME or AMF) may indicate to MN 104 that UE 102 is capable of DC.

[0067] As a more specific example, in one embodiment, when generating a first UE capability information message, UE 102 generates one or more radio access capability information elements (IEs) (e.g., UE-EUTRA capability IE, UE-MRDC capability IE and / or UE-NR capability IE) (hereinafter referred to as radio access capability IEs), and includes at least one DC band combination in the radio access capability IE of the first UE capability information message to indicate that UE 102 has enabled DC.

[0068] In another embodiment, the UE 102 includes a DC support indicator and / or a list of DC supported frequency bands in the radio access capability IE of the first UE capability information message to indicate that the UE 102 has enabled DC. In some embodiments, the UE 102 may include the DC band combination and the DC support indicator and / or a list of DC supported frequency bands in the same radio access capability IE (i.e., the first radio access capability IE).

[0069] One of the radio access capability IEs may be a UE-EUTRA capability IE or a UE-NR capability IE. For example, if the MN 104 is an E-UTRA base station (e.g., eNB or ng-eNB), the radio access capability IE is a UE-EUTRA capability IE. In order to indicate to the MN 104 that the UE 102 supports EN-DC capability, the DC support indicator may be an EN-DC support indicator (e.g., en-DC-r15), and the DC supported band list may be supportedBandListEN-DCNR-r15. In order to indicate to the MN 104 that the UE 102 supports NG EN-DC capability, the UE 102 may reuse the DC support indicator and the DC supported band list for EN-DC. Alternatively, the DC support indicator may be a specific NG EN-DC support indicator (e.g., ng-en-DC-r15), and the DC supported band list may be specific to NR in NG EN-DC (e.g., supportedBandListNG EN-DCNR-v1560).

[0070] As another example, if MN 104 is a 5G NR base station implemented as a gNB, one of the radio access capability IEs is a UE-NR capability IE. To indicate to MN 104 that UE 102 supports NE-DC capability, the DC support indicator can be a specific NE-DC support indicator (e.g., ne-DC), and the DC supported band list can be specific to EUTRA in NE-DC (e.g., supportedBandListNE-DCEUTRA). Alternatively, the DC supported band list can be generic for EUTRA (e.g., supportedBandListEUTRA), regardless of the DC configuration. To indicate to MN 104 that UE 102 supports NR-NR DC capability, the DC support indicator can be a specific NR-DC support indicator (e.g., nr-DC), and the DC supported band list can be specific to NR in NR-DC (e.g., supportedBandListNR-DC-v1560 or supportedBandCombinationList). Alternatively, the DC supported band list can be generic for NR (e.g., supportedBandListNR) regardless of the DC configuration.

[0071] In some cases, UE 102 may implement a combination of the above techniques. For example, UE 102 may include a DC band combination in a first radio access capability IE of a first UE capability information message, and additionally include a DC support indicator and / or a DC supported band list in a radio access capability IE different from the first radio access capability IE of the first UE capability information message (i.e., a second radio access capability IE) to indicate that UE 102 has enabled DC. In another example, UE 102 may include a DC support indicator and / or a DC supported band list in a first radio access capability IE of the first UE capability information message to indicate that UE 102 has enabled DC, and additionally include a DC band combination in a second radio access capability IE of a UE capability information message different from the first UE capability information message (i.e., a third UE capability information message). UE 102 sends the first UE capability information message or the third UE capability information message to MN 104 during or after the first NAS procedure.

[0072] Upon receiving the explicit indication (such as the first UE capability information message and / or the third UE capability information message (if sent), the MN 104 (if necessary) configures resources for the UE 102 to exchange EUTRA RRC messages or user plane data (e.g., when operating in EN-DC or NGEN-DC), or to exchange NR RRC messages or user plane data (e.g., when operating in NE-DC or NR-NR DC) with the MN 104. The MN 104 also configures the UE 102 to communicate with the SN 106. Therefore, the UE 102 is able to communicate with the MN 104 and the SN 106 in DC.

[0073] After MN 104 configures UE 102 to operate in DC, UE 102 detects a low battery condition of battery 103 (406), similar to Figure 2 and Figure 3 In response, UE 102 disables DC capability (408), similar to Figure 2 and Figure 3 208 and 308 in FIG.

[0074] By disabling the DC capability, UE 102 prevents the UE and SN 106 from operating in DC, so that UE 102 and MN 104 can only operate in SC.

[0075] In order to inform MN 104 that UE 102 has disabled DC capability, UE 102 performs a second NAS procedure (410) with CN 110 via MN 104. The second NAS procedure is similar to the first NAS procedure described above in that, if the UE operates in EN-DC and therefore communicates with CN 110 implemented as EPC, the second NAS procedure may be an attach procedure or a tracking area update procedure.

[0076] If the UE 102 operates in NGEN-DC, NR-NR DC, or NE-DC, the second NAS procedure may be a registration procedure.

[0077] During or after the second NAS procedure, for example, UE 102 generates a clear indication (e.g., a second UE capability information message) to inform MN 104 that UE 102 will no longer use DC (412). MN 102 may send the indication to CN 110. In some embodiments, UE 102 sends the indication (412) during the second NAS procedure. In other embodiments, UE 102 sends the indication (412) after completing the second NAS procedure.

[0078] In some embodiments, UE 102 indicates in a NAS message of the second NAS procedure (e.g., an attach request message, an attach complete message, a registration request message, or a registration complete message) that UE 102 will no longer use DC. Then, CN 110 (e.g., the MME or AMF discussed above) can indicate to MN 104 that UE 102 will no longer use DC.

[0079] For example, when generating the second UE capability information message, the UE 102 generates a first radio access capability IE of a radio access capability IE (e.g., a UE-EUTRA capability IE, a UE-MRDC capability IE, and / or a UE-NR capability IE), and excludes the DC band combination in the first radio access capability IE of the second UE capability information message to indicate that the UE 102 has disabled DC. Alternatively, the UE 102 completely excludes the first radio access capability IE in the second UE capability information message.

[0080] In other embodiments, the UE 102 excludes the DC support indicator or the DC supported band list in the second radio access capability IE of the radio access capability IE of the second UE capability information message to indicate that the UE 102 has disabled DC. Alternatively, the UE 102 completely excludes the second radio access capability IE in the second UE capability information message.

[0081] In other embodiments, the UE 102 excludes the DC-band combination in the first radio access capability IE of the second UE capability information message, and the UE 102 also does not include a DC support indicator or a DC-supported band list in the second radio access capability IE to indicate that the UE 102 has disabled DC. Alternatively, the UE 102 completely excludes the first radio access capability IE and the second radio access capability IE in the second UE capability information message.

[0082] In some cases, as opposed to the same UE capability information message (i.e., the second UE capability information message), the UE 102 may send the first and second radio access capability IEs in different UE capability information messages to the MN 104. For example, the UE 102 excludes the DC support indicator or the DC supported band list in the second radio access capability IE in the second UE capability information message, and the UE 102 also does not include the DC band combination in the first radio access capability IE of the fourth UE capability information message to indicate that the UE 102 has disabled DC. Alternatively, the UE 102 completely excludes the first radio access capability IE and the second radio access capability IE in different UE capability information messages.

[0083] Upon receiving the explicit indication, MN 104 prevents initiation of an SN add procedure with SN 106 (414), while continuing to support SC between UE 102 and MN 104. For example, MN 104 does not configure resources for UE 102 to communicate with SN 106, but (if necessary) configures resources for UE 102 to exchange EUTRA RRC messages and user plane data (e.g., when MN 104 is an eNB or ng-eNB), or to exchange NR RRC messages and user plane data (e.g., when MN 104 is a gNB) with MN 104. Therefore, UE 102 can communicate only with MN 104 (i.e., not with SN 106).

[0084] UE 102 may also enable MN CA during or after the first NAS procedure.To inform MN 104 that UE 102 has enabled MN CA, UE 102 includes at least one MN CA band combination in the first radio access capability IE or the second radio access capability IE of the first UE capability information message.

[0085] UE 102 may disable MN CA during or after the second NAS procedure. To notify MN 104 that UE 102 has disabled the MN CA capability, UE 102 excludes at least one MN CA band combination from the first radio access capability IE or the second radio access capability IE of the second UE in the second UE capability information message and / or the fourth UE capability information message (if sent). Alternatively, UE 102 completely excludes the first radio access capability IE and the second radio access capability IE from the second UE capability information message and / or the fourth UE capability information message (if sent).

[0086] In some embodiments, UE 102 sends a first UE capability information message (404) in response to a first UE capability query message received from MN 104. UE 102 may receive the first UE capability query message during or after the first NAS procedure. After receiving an indication from CN 110 that UE 102 is capable of DC, MN 104 may send the first UE capability query message to UE 102. UE 102 sends a third UE capability information message to MN 104 in response to a third UE capability query message received from MN 104. UE 102 may receive the third UE capability query message during or after the first NAS procedure. After receiving an indication from CN 110 that UE 102 is capable of DC, MN 104 may send the third UE capability query message to UE 102.

[0087] Similarly, for example, UE 102 may send a second UE capability information message to MN 104 during or after the second NAS procedure in response to a second UE capability query message received by MN 104. MN 104 may send a second UE capability query message to UE 102 after receiving an indication from CN 110 that UE 102 will no longer use DC. For example, UE 102 may send a fourth UE capability information message to MN 104 during or after the second NAS procedure in response to a fourth UE capability query message received from MN 104. MN 104 may send a fourth UE capability query message to UE 102 after receiving an indication from CN 110 that UE 102 will no longer use DC. In these examples, the first, second, third, and fourth UE capability query messages and the first, second, third, and fourth UE capability information messages are RRC messages, but in general, UE 102 and MN 104 may use any suitable messages to query and report UE capabilities.

[0088] After UE 102 disables the DC capability, the user may charge battery 103 or replace battery 103 so that the low battery condition of battery 103 no longer applies (e.g., battery 103 can receive a charge from a power source). DC controller 118 may determine that the remaining charge level is equal to or above the same threshold level that previously caused DC controller 118 to disable the DC capability, or at a different threshold level (i.e., a second threshold level stored in a memory of UE 102). In any case, at some point, DC controller 118 may determine that UE 102 can again operate in DC. In this case, DC controller 118 may again perform the first NAS procedure (402) to re-enable the DC capability and (optionally) re-enable the MN CA capability.

[0089] In some embodiments, the UE 102 may perform a NAS detach procedure or a NAS deregistration procedure, and then perform a second NAS procedure to disable the DC capability. The UE 102 may perform a NAS detach procedure or a NAS deregistration procedure, and then perform a first NAS procedure to re-enable the DC capability. In other embodiments, the UE 102 does not perform a NAS detach procedure or a NAS deregistration procedure to disable or re-enable the DC capability.

[0090] Furthermore, in some embodiments, the UE 102 may postpone disabling DC operation in view of the current RRC state (e.g., idle, connected, inactive) of the UE 102. To avoid dropping calls or otherwise interrupting ongoing data sessions when the UE 102 is in a connected state, the UE 102 may postpone disabling DC operation in view of the connection state (e.g., EUTRA-RRC_CONNECTED when the MN is an eNB or ng-eNB, NR-RRC CONNECTED when the MN is a gNB). Figure 5-6 As shown in , UE 102 may consider such RRC status and / or other conditions to determine the moment to disable DC.

[0091] First reference Figure 5 , UE 102 operating in an idle or inactive state of the RRC protocol disables DC capability in response to detecting a low battery condition. At the beginning of this scenario, UE 102 performs a first NAS procedure (502) with CN 110 via MN 104, similar to Figure 4 Event 402 in the scenario. Also similar to Figure 4 At event 404, UE 102 generates a clear indication that UE 102 supports DC capability during or after the first NAS procedure and sends the indication to MN 104 (504). Upon receiving the clear indication, MN 104 configures the necessary resources for UE 102 to communicate with MN 104 and SN 106 in DC.

[0092] After MN 104 configures UE 102 for DC operation, UE 102 operates in an idle state (e.g., EUTRA-RRC_IDLE, NR-RRC IDLE) or an inactive state (e.g., EUTRA-RRC INACTIVE, NR-RRC INACTIVE) (505). In some cases, if there is no data activity between MN 104, SN 106, and UE 102, MN 104 configures UE 102 to enter an idle or inactive state. UE 102 then detects a low battery condition of battery 103 (506), similar to Figure 4 Event 406 in .

[0093] In response, UE 102 disables the DC capability (508), similar to event 408, except that in this scenario, UE 102 disables the DC capability due to the idle or inactive state and the low charge condition of battery 103. By disabling the DC capability, UE 102 prevents the UE and SN 106 from operating in DC, so that UE 102 and MN 104 can only operate in SC.

[0094] Despite Figure 5 In the exemplary scenario of FIG. 5 , UE 102 is operating in an idle state or an inactive state (505) before detecting a low battery condition (506), but in other embodiments, UE 102 may detect a low battery condition (506) before operating in an idle state or an inactive state (505). In any event, UE 102 need not postpone disabling the DC capability because a user of UE 102 may not experience an interruption in data usage while UE 102 is in an idle state or an inactive state.

[0095] To inform MN 104 that UE 102 has disabled DC capability, UE 102 performs a second NAS procedure (510) with CN 110 via MN 104, similar to event 410. Events 512 and 514 are also similar to events 412 and 414 discussed above.

[0096] After the UE 102 disables the DC capability, the DC controller 118 may determine that the remaining power level is at or above the same threshold level that previously caused the DC controller 118 to disable the DC capability, or at a different threshold level. In any case, the DC controller 118 may determine at some point that the UE 102 can operate in DC again. In response, as described above, if the UE 102 is in an idle state or an inactive state, the UE 102 may perform a first NAS procedure (402) to re-enable the DC capability and (optionally) re-enable the MN CA capability (if disabled). If the UE 102 is in a connected state, the UE 102 may postpone the first NAS procedure until the UE 102 is in an idle state or an inactive state. In some embodiments, the UE 102 may need to perform a NAS detach procedure or a NAS deregistration procedure to disable or re-enable the DC capability. If the UE 102 is in an idle state or an inactive state, the UE 102 performs a NAS detach procedure or a NAS deregistration procedure. If the UE 102 is in the connected state, the UE 102 may postpone the NAS detach procedure or the NAS deregistration procedure until the UE 102 is in the idle state or inactive state. In other words, the UE 102 may postpone disabling or re-enabling the DC capability and (optionally) the MN CA capability until the UE 102 is in the idle state or inactive state.

[0097] against Figure 4 Some exemplary embodiments of the scenario description may be applicable to Figure 5 scene.

[0098] and Figure 5 In contrast to the scenario Figure 6The UE 102 in scenario 600 initially operates in the connected state of the RRC protocol and, therefore, postpones disabling the DC capability after detecting a low battery condition.

[0099] UE 102 first performs a first NAS procedure (602) with CN 110 via MN 104, similar to Figure 5 During or after the first NAS procedure, UE 102 generates a clear indication to inform MN 104 that UE 102 supports DC capability and sends the indication to MN 104 (604), similar to Figure 5 Event 504 in the scene.

[0100] Upon receiving the explicit indication, MN 104 configures the necessary resources for UE 102 (if necessary) to communicate with MN 104 and SN 106 in DC.

[0101] After the MN 104 configures the UE 102 for DC operation, the UE 102 operates in a connected state (e.g., EUTRA-RRC_CONNECTED, NR-RRC CONNECTED) (605).

[0102] Then, UE 102 detects a low battery condition of battery 103 (606), similar to Figure 5 , except that the UE 102 detects a low battery condition in view of the connection state.

[0103] In response, UE 102 determines whether a predetermined operating condition is met (607). If the predetermined operating condition is not met (e.g., UE 102 is not engaged in a voice or video call, the screen of UE 102 is off, or a power saving feature of UE 102 has been activated), UE 102 disables the DC capability (608), similar to Figure 5 , except that UE 102 disables the DC capability in view of the connected state and the absence of a predetermined operating condition. However, if the predetermined operating condition is met (e.g., UE 102 is engaged in a voice or video call, the screen of UE 102 is on, or a power saving feature of UE 102 has been disabled), UE 102 defers disabling the DC capability (609) until the operating condition no longer applies. Figure 6 In the exemplary scenario, the UE 102 operates in a connected state ( 605 ) before detecting a low battery condition ( 606 ), but in other embodiments, the UE 102 may detect a low battery condition ( 606 ) before operating in a connected state ( 605 ).

[0104] To inform MN 104 that UE 102 has disabled DC capability, similar to Figure 5 At event 510 in the case of , UE 102 performs a second NAS procedure (610) with CN 110 via MN 104. Events 612 and 614 are also similar to events 512 and 514 discussed above.

[0105] After UE 102 disables DC, DC controller 118 may determine that the remaining power level is equal to or above the same threshold level that previously caused DC controller 118 to disable DC capability, or at a different threshold level. In any case, DC controller 118 may determine at some point that UE 102 can operate in DC again. In response, if the predetermined operating conditions are not met, UE 102 may perform a first NAS procedure to re-enable DC capability and (optionally) re-enable MN CA capability (if disabled) (602). If the predetermined operating conditions are met, UE 102 postpones re-enabling DC capability and (optionally) MN CA capability (if disabled) until the predetermined operating conditions no longer apply. In some embodiments, UE 102 may need to perform a NAS detach procedure or a NAS deregistration procedure to disable or re-enable DC capability. If the predetermined operating conditions are not met, UE 102 performs a NAS detach procedure or a NAS deregistration procedure. If the predetermined operating conditions are met, UE 102 may postpone the NAS detach procedure or the NAS deregistration procedure. In other words, UE 102 may postpone disabling or re-enabling the DC capability and (optionally) the MN CA capability until predetermined operating conditions are not met.

[0106] against Figure 4 and Figure 5 Some exemplary embodiments of the scenario description can be applied to Figure 6 scene.

[0107] Next, Figure 7-10 Methods of determining whether a UE should disable DC capabilities and (optionally) CA capabilities in response to detecting predetermined operating conditions and a low battery condition are described.

[0108] Figure 7 An exemplary flow diagram 700 is depicted of an exemplary method for determining whether the UE 102 should disable DC capabilities and (optionally) CA capabilities in response to detecting a predetermined operating condition prior to detecting a low battery condition.

[0109] Method 700 begins at block 701, where UE 102 determines whether a predetermined operating condition is satisfied. If UE 102 determines that the predetermined operating condition is satisfied, UE 102 then continues (e.g., aperiodically, periodically) to determine whether the predetermined operating condition is not satisfied. If UE 102 determines that the predetermined operating condition is not satisfied, then at block 702, UE 102 determines whether a low battery condition of battery 103 has occurred, similar to Figure 2 202 in the scenario of FIG. 702. The operating condition detected at block 701 may be a single operating condition (e.g., the screen is on) or may include a combination of more than one operating condition (e.g., the screen is on and a power saving feature of UE 102 has been activated). Blocks 704, 706, 708, and 710 are similar to blocks 204, 206, 208, and 210 discussed above. Thus, if the predetermined operating condition is met, UE 102 defers disabling the DC capability until the operating condition no longer applies.

[0110] Figure 8 An exemplary flow diagram 800 is depicted of an exemplary method in which, prior to detecting an operating condition, the UE 102 determines whether the UE 102 should disable DC capabilities and (optionally) CA capabilities in light of detecting a low battery condition.

[0111] Method 800 begins at block 802 where the UE 102 determines whether a low battery condition of the battery 103 has occurred.

[0112] If the UE 102 does not detect a low battery condition, the UE 102 determines whether a predetermined operating condition is satisfied at block 803. If the UE 102 determines that the predetermined operating condition is satisfied, the UE 102 continues to determine whether the predetermined operating condition is not satisfied. If the UE 102 determines that the predetermined operating condition is not satisfied, then at block 804, the UE 102 enables the DC capability if it was previously disabled, similar to Figure 7 704. Block 806 is also similar to block 706 discussed above.

[0113] However, if the UE 102 detects a low battery condition at block 802, the UE 102 determines whether the predetermined operating condition is met at block 807. If the UE 102 determines that the predetermined operating condition is met, the UE 102 proceeds to determine whether the predetermined operating condition is not met. If the UE 102 determines that the predetermined operating condition is not met, then at block 808, if the DC capability was previously enabled, the UE 102 disables the DC capability, similar to Figure 7708. Block 810 is also similar to block 710 discussed above. The operating conditions detected at blocks 803 and 807 can be the same or different operating conditions, or can include a combination of more than one operating condition. For example, the operating condition that causes UE 102 to postpone enabling DC capabilities is a voice call (e.g., to prevent dropped calls), while the operating condition that causes UE 102 to postpone disabling DC capabilities is a more data-intensive activity (such as a video call).

[0114] Figure 9 An exemplary flow diagram 900 is depicted of another exemplary method for determining whether the UE 102 should disable DC capability and (optionally) CA capability in response to detecting a predetermined operating condition prior to detecting a low battery condition.

[0115] Method 900 begins at block 901 where UE 102 determines whether a predetermined operating condition is satisfied, similar to Figure 7 If the UE 102 determines that the predetermined operating condition is satisfied, the UE 102 proceeds to determine whether the predetermined operating condition is not satisfied. If the UE 102 determines that the predetermined operating condition is not satisfied, the UE 102 determines at block 902 whether a low battery condition of the battery 103 has occurred (e.g., by comparing the remaining battery level with a specific threshold level), similar to Figure 3 302 of the box.

[0116] If the UE 102 does not detect a low battery condition, then at block 904, the UE 102 enables the DC functionality if the DC capability was previously disabled, similar to Figure 7 704. Block 906 is also similar to block 706 discussed above.

[0117] However, if the UE 102 detects a low battery condition, then similar to Figure 7 At block 708, the UE 102 disables the DC capability if the DC capability was previously enabled.

[0118] In some implementations, in addition to disabling the DC capability, the UE 102 enables the MN CA capability in response to the same low battery condition at block 902, but disables the MN CA capability in response to a different low battery condition (e.g., the remaining battery level is below a second threshold level that is lower than the first threshold level). Specifically, if the UE 102 does not detect the same low battery condition, then if the MN CA capability was previously disabled, then at block 906, the UE 102 enables the MN CA capability, similar to block 706 discussed previously. If the UE 102 detects a different low battery condition at block 909, then the UE 102 disables the MN CA capability at block 910, similar to block 710 discussed above.

[0119] Figure 10 An exemplary flowchart 1000 is depicted for determining whether the UE 102 should disable DC capabilities in response to detecting a low battery condition of the battery prior to detecting a predetermined operating condition, and determining whether the UE 102 should disable CA capabilities in light of detecting another low battery condition of the battery prior to detecting the predetermined operating condition.

[0120] Method 1000 begins at block 1002 where UE 102 determines whether a low battery condition has occurred in battery 103 (e.g., by comparing the remaining battery level to a particular threshold level), similar to Figure 9 Frame 902.

[0121] If the UE 102 does not detect a low battery condition, then at block 1003, the UE 102 determines whether a predetermined operating condition is satisfied, similar to Figure 8 The operating condition detected at block 1003 may be the same or a different operating condition than the operating condition detected at block 803. Blocks 1004 and 1006 are also similar to blocks 804 and 806 discussed above.

[0122] However, if the UE 102 detects a low battery condition at block 1002, the UE 102 determines at block 1001 whether a predetermined operating condition is satisfied, similar to Figure 8 The operating condition detected at block 1001 may be the same or different operating condition than the operating condition detected at block 807. Block 1008 is also similar to block 808 discussed above. The operating conditions detected at blocks 1003 and 1001 may be the same or different operating conditions, or may include a combination of more than one operating condition.

[0123] In some implementations, in addition to disabling the DC capability, if the UE 102 does not detect a different low battery condition (e.g., the remaining battery level is lower than a second threshold level that is lower than the first threshold level) at block 1009, the UE 102 determines whether a predetermined operating condition is met at block 1007. If the UE 102 determines that the predetermined operating condition is met, the UE 102 proceeds to determine whether the predetermined operating condition is not met. If the UE 102 determines that the predetermined operating condition is not met, then at block 1006, if the MN CA capability was previously disabled, the UE 102 enables the MN CA capability, similar to block 806 discussed above.

[0124] However, if UE 102 detects a different low battery condition at block 1009, UE 102 determines at block 1005 whether the predetermined operating condition is met. If UE 102 determines that the predetermined operating condition is met, UE 102 proceeds to determine whether the predetermined operating condition is not met. If UE 102 determines that the predetermined operating condition is not met, then at block 1010, if the MN CA capability was previously enabled, UE 102 disables the MN CA capability, similar to block 810 discussed above. As with the operating conditions detected at blocks 1003 and 1001, the operating conditions detected at blocks 1007 and 1005 may be the same or different operating conditions relative to each other, or may include a combination of more than one operating condition.

[0125] Figures 11 to 12 Depicts a scenario where UE 102 prevents MN 104 from initiating the SN addition procedure by not providing measurement reports related to SN 106. Figure 2-3 on the contrary, Figure 2-3 A scenario is described in which UE 102 prevents MN 104 from initiating the SN add procedure by providing a clear indication.

[0126] Figure 11 A messaging diagram 1100 is depicted in which, in response to the UE 102 detecting a low battery condition, the UE 102 prevents the MN 104 from initiating an SN addition procedure by not providing measurement reports related to the SN 106 .

[0127] At the beginning of the scenario, UE 102 is operating in an idle state or inactive state (1103), similar to Figure 5 Events 1104 and 1106 are also similar to events 506 and 508 discussed above. Thus, UE 102 operates in SC with MN 104 on the carrier frequency of MN 104 (1108).

[0128] UE 102 may notify MN 104 that UE 102 has disabled DC capability to prevent MN 104 from configuring UE 102 to connect to SN 106. In some implementations, UE 102 implicitly notifies MN 104 by not generating a measurement report of the carrier frequency of SN 106 (or by not measuring the carrier frequency of SN 106 at all) (1112). The measurement report may enable MN 104 to configure UE 102 to connect to SN 106 in DC. If UE 102 disables DC capability, UE 102 may still be able to measure the carrier frequency of SN 106. Alternatively, if UE 102 disables DC capability, UE 102 may disable measurement of the carrier frequency of SN 106. Furthermore, in some embodiments, if UE 102 disables DC capability, UE 102 implicitly notifies MN 104 (1112) in response to MN 104 sending 1110 a measurement configuration in an RRC message for a carrier frequency of SN 106 to UE 102. Thus, UE 102 prevents MN 104 from initiating an SN add procedure with SN 106 while continuing to support SC between UE 102 and MN 104 (1113).

[0129] An exemplary embodiment of the UE 102 is described below with respect to disabling the DC capability of the UE 102. In one embodiment, when the MN 104 sends a measurement configuration (1110) for the carrier frequency of the SN 106 to the UE 102, the UE 102 generates and sends an "artificial" measurement report that simulates a low signal strength and / or low signal quality of the carrier frequency of the SN 106 to the MN 104, regardless of whether the signal strength and / or signal quality is actually low. In another embodiment, the UE 102 sends an explicit indication to the MN 104 to inform the MN 104 that the UE 102 supports the DC capability, as described in reference to FIG. Figure 4-6 As described above, UE 102 neither generates measurement results nor sends the "artificial" reports described above. In this manner, regardless of the implementation, UE 102 prevents MN 104 from configuring UE 102 to use SN 106's carrier frequency in DC. More specifically, UE 102 does not notify MN 104 of the measurement of SN 106's carrier frequency. Alternatively, UE 102 notifies MN 104 of the low signal strength and / or low signal quality of SN 106's carrier frequency when, in fact, the quality of SN 106's carrier frequency is high enough to configure UE 102 to use SN 106's carrier frequency in DC.

[0130] Implicitly notifying MN 104 that UE 102 has disabled DC capability can also prevent the following scenario: UE 102 sends SN measurement results to MN 104 so that when maintaining a low battery state of battery 103, MN 104 configures UE 102 to be in DC (i.e., connect SN 106) after UE 102 transitions from an idle state or an inactive state to a connected state. When the UE is in the connected state, MN 104 can send a measurement configuration in an RRC message to configure the carrier frequency on which UE 102 measures SN 106. In the case where UE 102 does not implicitly notify MN 104, MN 104 configures UE 102 to be in DC with SN 106 despite the low battery condition.

[0131] When UE 102 detects that the low battery condition no longer applies, UE 102 enables DC capability (1114). To inform MN 104 that UE 102 has enabled DC capability, UE 102 measures the carrier frequency of SN 106, generates a measurement report message (1116), and sends the measurement report message to MN 104 (1118). To this end, if the measurement report message is to be sent to MN 104 or to SN 106 via MN 104, UE 102 may use SRB1 to send the measurement report message to MN 104. Alternatively, if the measurement report message is to be sent to SN 106, UE 102 may use SRB3 to send the measurement report message to SN 106.

[0132] An exemplary embodiment of UE 102 is described below with respect to enabling DC capability for UE 102. In some embodiments, in response to MN 104 sending a measurement configuration (e.g., MeasConfig) in an RRC message for a carrier frequency of SN 106 to UE 102 (1110 or 1115), UE 102 sends a measurement report message to MN 104 (1118). The measurement configuration may include a carrier frequency configuration for configuring the carrier frequency of SN 106 to be measured. MN 104 may include the measurement configuration in an RRC message or in a system information block (SIB). MN 104 sends the RRC message to UE 102 via an SRB or broadcasts the SIB to UE 102. In a specific embodiment, if MN 104 is an E-UTRA base station (e.g., eNB or ng-eNB) and SN 106 is a 5G NR base station (e.g., gNB), the carrier frequency configuration is a 5G NR carrier frequency configuration (e.g., CarrierFreqListNR-r15), the SIB may be SystemInformationBlockType24, and the RRC message may be an RRCConnectionReconfiguration message, an RRCConnectionResume message, an RRCConnectionRelease message, or a new RRC message for configuring UE 102 to perform measurements in an idle or inactive state. In response, UE 102 measures the 5G NR carrier frequency configured in the 5G NR carrier frequency configuration and reports the measurement result back to MN 104 in the measurement report message.

[0133] In another embodiment, if both MN 104 and SN 106 are 5G NR base stations (e.g., gNBs), the measurement configuration is MeasConfig, the SIB is an existing SIB (e.g., SIB4) or a new SIB, and the RRC message is an RRCReconfiguration message, an RRCResume message, an RRCRelease message, or a new RRC message for configuring UE 102 to perform measurements in an idle or inactive state. MN 104 sends an RRC message or broadcasts an SIB to UE 102 on a first 5G NR carrier frequency (e.g., in frequency range 1 (FR1)). MeasConfig configures SN 106 for a second 5G NR carrier frequency (e.g., in FR1 or frequency range 2 (FR2)). In response, UE 102 measures the second 5G NR carrier frequency and reports the measurement results back to MN 104 in a measurement report message.

[0134] Assuming that the measurement report message indicates that the signal strength or quality of the carrier frequency of SN 106 is suitable for DC (e.g., satisfies a certain threshold), UE 102 enables MN 104 to initiate 1119 an SN add procedure with SN 106. In some embodiments, the measurement report message may be a MeasurementReport message, a UEInformationResponse message, or an RRC message, which is defined as including measurement results measured during an idle state or an inactive state.

[0135] Figure 12 Depicted is a messaging diagram 1200 for preventing the MN 104 from initiating an SN addition procedure by a UE 102 operating in a connected state of the RRC protocol by not providing measurement reports related to the SN 106 .

[0136] At the beginning of the scene, something like Figure 6 At event 605 in the scenario described above, UE 102 operates in a connected state (1204). Therefore, UE 102 operates in SC with MN 104 on the carrier frequency of MN 104 (1205). Events 1206, 1208, 1210, 1212, 1213, 1214, 1215, 1216, and 1218 are also similar to events 1104, 607, 1110, 1112, 1113, 1114, 1115, 1116, and 1118 described above.

[0137] An exemplary embodiment of UE 102 is described below with respect to enabling DC capability for UE 102. In some embodiments, in response to MN 104 sending a measurement configuration (e.g., MeasConfig) for the carrier frequency of SN 106 to UE 102 (1210 or 1215), UE 102 sends a measurement report message (1218) to MN 104. The measurement configuration may include a carrier frequency configuration for configuring the carrier frequency of SN 106 to be measured. MN 104 may include the measurement configuration in an RRC message or in an SIB. MN 104 sends the RRC message to UE 102 via an SRB or broadcasts the SIB to UE 102. In a specific embodiment, if both MN 104 and SN 106 are 5G NR base stations (e.g., gNBs), the RRC message may be an RRCReconfiguration message, an RRCResume message, or an RRCRelease message, and the SIB may be an existing SIB (e.g., SIB4) or a new SIB. MN 104 sends an RRC message to UE 102 on a first 5G NR carrier frequency (e.g., in frequency range 1 (FR1)). The measurement configuration configures a second 5G NR carrier frequency (e.g., in FR1 or frequency range 2 (FR2)) for SN 106. In response, UE 102 measures the second 5G NR carrier frequency and reports the measurement results back to MN 104 in a measurement report message. In some embodiments, the measurement report message can be a MeasurementReport message, a UEInformationResponse message, or an RRC message, which is defined as including measurement results measured in an idle state or an inactive state.

[0138] In another embodiment, if MN 104 is an E-UTRA base station (e.g., eNB or ng-eNB) and SN 106 is a 5G NR base station (e.g., gNB), the SIB may be SystemInformationBlockType24, and the RRC message may be an RRCConnectionReconfiguration message, an RRCConnectionResume message, an RRCConnectionRelease message, or a new RRC message for configuring UE 102 to perform measurements in an idle or inactive state. MN 104 sends an RRC message or broadcasts an SIB on an E-UTRA carrier frequency to UE 102. The measurement configuration configures the 5G NR carrier frequency for SN 106. In response, UE 102 measures the 5G NR carrier frequency and reports the measurement results back to MN 104 in a measurement report message.

[0139] Assuming the measurement report message indicates that the signal strength or quality of the carrier frequency of SN 106 is suitable for DC (eg, meets a threshold), UE 102 enables MN 104 to initiate an SN add procedure with SN 106 ( 1219 ), similar to event 1119 .

[0140] Figure 13 A messaging diagram 1300 depicts an exemplary scenario in which the UE 102 prevents the MN 104 from initiating an SN add procedure by sending an indication of an SCG failure to the MN 104.

[0141] At the beginning of the scenario, UE 102 is operating in DC with MN 104 on the carrier frequency of MN 104 and with SN 106 on the carrier frequency of SN 106 (1302). UE 102 disables DC capability (1306) in response to event (1304). Event 1304 is similar to event 406 discussed above.

[0142] UE 102 then detects an SCG failure and, in response to disabling DC capability (1306), suspends SCG transmission for all SRBs and DRBs configured to use resources provided by SN 106. In other words, if UE 102 detects event 1304, UE 102 reports that an SCG failure has occurred, even if UE 102 is still able to communicate with SN 106. UE 102 generates an indication of an SCG failure to notify MN 104 that UE 102 will no longer use DC (1307). In some embodiments, UE 102 indicates in an SCG failure message that UE 102 will no longer use DC. The SCG failure message can be an SCG failure information message, an SCG failure information NR message, or an SCG failure information EUTRA message. UE 102 sends the SCG failure message to MN 104 via an SRB (e.g., SRB1). The SCG failure message can include a first failure type and / or a second failure type. For example, the first failure type may be set to, for example, t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, synchReconfigFailure-SCG, scg-reconfigFailure, or srb3-IntegrityFailure, and the second failure type may be set to an indication of a low battery condition of the battery 103. By sending an indication of the SCG failure to the MN 104, the UE 102 may cause the MN 104 to initiate a release (SN release or DC release) of the SN 106 (1313) while continuing to support SC between the UE 102 and the MN 104. In this case, the UE 102 prevents the MN 104 from performing a procedure for recovering from the SCG failure.

[0143] In some embodiments, the UE 102 may include in the SCG failure message "artificial" measurement results that simulate to the MN 104 or SN 106 low signal strength and / or low signal quality of the carrier frequency of the SN 106, regardless of whether the signal strength and / or signal quality is actually low, or even if the signal strength and / or signal quality is actually high or sufficient for communication. In other embodiments, the UE 102 excludes from the SCG failure message measurement results that indicate to the MN 104 or SN 106 high signal strength and / or high signal quality of the carrier frequency of the SN 106. In other embodiments, the UE 102 excludes from the SCG failure message any measurement results.

[0144] In some cases, MN 104 may send an RRC reconfiguration message to UE 102 in response to the SCG failure message. MN 104 instructs UE 102 in the RRC reconfiguration message to release SN 106. In response to the RRC reconfiguration message, UE 102 releases the configuration for communicating with SN 106 (e.g., SCG configuration or cell group configuration).

[0145] In some embodiments, similar to event 1210, if UE 102 is configured to measure at least one carrier frequency of SN 106 (or another SN) in response to a measurement configuration received from MN 104 or SN 106 (or another SN), UE 102 may stop measuring one or more of the at least one carrier frequency of SN 106 when disabling DC capability (1306). UE 102 may also continue to measure the remaining at least one second carrier frequency in response to another measurement configuration received from MN 104 or SN 106 (or another SN). In other embodiments, if UE 102 is configured to measure the carrier frequency of SN 106 (or another SN) in response to a measurement configuration received from MN 104 or SN 106 (or another SN), UE 102 may still continue to measure at least one carrier frequency of SN 106 after disabling DC capability (1306). In this case, UE 102 does not send a measurement report indicating high signal strength and / or signal quality of at least one carrier frequency to MN 104, or UE 102 sends one or more artificial measurement reports for at least one carrier frequency to MN 104, as described above. In other embodiments, UE 102 may stop measuring all carrier frequencies in the at least one carrier frequency when disabling DC capability (1306). In another embodiment, when disabling DC capability, UE 102 disables one or more RF chains / chips used to receive at least one carrier frequency of SN 106, thereby reducing power consumption. The at least one carrier frequency may or may not include a carrier frequency / multiple carrier frequencies in the at least one second carrier frequency.

[0146] Events 1314, 1315, 1316, and 1318 are similar to events 1114, 1115, 1116, and 1118 discussed above. In some embodiments, the low battery condition of event 1314 may be the same low battery condition as in event 1304 (e.g., the remaining battery level is below a first threshold level), or a different low battery condition (e.g., the remaining battery level is below a second threshold level that is higher or lower than the first threshold level). If UE 102 is configured to measure the carrier frequency of SN 106 (or another SN) in response to a measurement configuration (1315) received from MN 104 or SN 106 (or another SN), UE 102 begins measuring the carrier frequency. UE 102 may generate a measurement report message (1316) including the measurement result and send the measurement report message to MN 104 (1318). Therefore, if the measurement report message indicates that UE 102 has high signal strength and / or high signal quality on the carrier frequency (i.e., UE 102 is within the coverage area of SN 106 (or another SN)), MN 104 can configure UE 102 to connect to SN 106 (or another SN).

[0147] In some embodiments, if the temperature of the UE 102 (or one of the components of the processing hardware of the UE 102, such as the DC controller 118, the power management module 120, the EUTRA module 114, and / or the NR module 116) measured by the thermal management module exceeds a low power condition (e.g., the temperature level is above a third threshold level), the UE 102 does not send a measurement report message (1318) to the MN 104. If the temperature of the UE 102 does not exceed a low power condition (e.g., the temperature level is below the third threshold level), the UE 102 may send a measurement report message to the MN 104 (1318).

[0148] Event 1319 is similar to event 1119 discussed above. MN 104 may perform a process for recovering from an SCG failure or configuring an SCG for SN 106 or another SN (not shown to avoid confusion). To this end, MN 104 may send an RRC reconfiguration message to UE 102 using a DRB to resume previously suspended SCG transmission. In response, UE 102 resumes SCG transmission using the DRB to transmit data to MN 104. UE 102 may also send an RRC reconfiguration complete message to MN 104 in response to the RRC reconfiguration message. If MN 104 is an E-UTRA base station (e.g., an eNB or ng-eNB), the RRC reconfiguration message may be an RRC Connection Reconfiguration message, and the RRC reconfiguration complete message may be an RRC Connection Reconfiguration Complete message. If the MN 104 is a 5G NR base station (e.g., gNB), the RRC reconfiguration message may be an RRC Reconfiguration message, and the RRC reconfiguration complete message may be an RRC Reconfiguration Complete message.

[0149] Figure 14 A messaging diagram 1400 depicts an exemplary scenario in which the UE 102 prevents the MN 104 from initiating an SN add procedure by sending an indication of an MCG failure to the MN 104.

[0150] At the beginning of the scene, something like Figure 13 At event 1302 in the scenario of FIG, UE 102 operates in DC with MN 104 on the carrier frequency of MN 104 and with SN 106 on the carrier frequency of SN 106 (1402). Events 1404 and 1406 are also similar to events 1304 and 1306 discussed above.

[0151] In response to disabling the DC capability (1406), the UE 102 then detects an MCG failure and suspends MCG transmission for all SRBs and DRBs that are configured to use resources provided by the MN 104. In other words, if the UE 102 detects event 1404, the UE 102 reports that an MCG failure has occurred, even though the UE 102 may still be able to communicate with the MN 104. The UE 102 generates an indication of an MCG failure to inform the MN 104 that the UE 102 will no longer use DC (1407). In some embodiments, the UE 102 indicates in an RRC Reestablishment Request message that the UE 102 will no longer use DC. The UE 102 sends an RRC Reestablishment Request message to the MN 104 in an SRB (e.g., SRB0). The RRC Reestablishment Request message may indicate a failure type, which may be a reconfigurationFailure, a handoverFailure, an otherFailure, or an indication of a low battery condition of the battery 103. If the MN 104 is an E-UTRA base station (e.g., eNB or ng-eNB), the RRC Reestablishment Request message is an RRC ConnectionReestablishment Request message. If the MN 104 is a 5G NR base station (e.g., gNB), the RRC Reestablishment Request message is an RRC Reestablishment Request message.

[0152] In response to sending the RRC Reestablishment Request message to MN 104, UE 102 may receive an RRC Reestablishment message (1408) from MN 104. If MN 104 is an E-UTRA base station (e.g., eNB or ng-eNB), the RRC Reestablishment message is an RRC ConnectionReestablishment message, and UE 102 may receive the RRC Reestablishment message in SRB0 from MN 104. If MN 104 is a 5G NR base station (e.g., gNB), the RRC Reestablishment message is an RRC Reestablishment message, and UE 102 may receive the RRC Reestablishment message in SRB1 from MN 104.

[0153] In response to receiving the RRC Reestablishment message from MN 104, UE 102 may send an RRC Reestablishment Complete message to MN 104, for example, in SRB1 (1409). If MN 104 is an E-UTRA base station (e.g., an eNB or ng-eNB), the RRC Reestablishment Complete message is an RRC Connection Reestablishment Complete message. If MN 104 is a 5G NR base station (e.g., a gNB), the RRC Reestablishment Complete message is an RRC Reestablishment Complete message. By sending the RRC Reestablishment Complete message to MN 104, UE 102 may enable MN 104 to initiate the release of SN 106 (e.g., preventing MN 104 from performing procedures for recovering from an MCG failure) (1413), similar to event 1313 discussed above.

[0154] Events 1414, 1415, 1416, and 1418 are similar to events 1314, 1315, 1316, and 1318 discussed above.

[0155] Furthermore, event 1419 is similar to event 1319 discussed above. MN 104 may perform a process for recovering from an MCG failure (not shown to avoid clutter). To this end, MN 104 may send an RRC reconfiguration message to UE 102 using a DRB to resume previously suspended MCG transmission. In response, UE 102 resumes MCG transmission using the DRB to transmit data to MN 104. UE 102 may also send an RRC reconfiguration complete message to MN 104 in response to the RRC reconfiguration message. If MN 104 is an E-UTRA base station (e.g., an eNB or ng-eNB), the RRC reconfiguration message may be an RRCConnectionReconfiguration message, and the RRC reconfiguration complete message may be an RRCConnectionReconfigurationComplete message. If MN 104 is a 5G NR base station (e.g., a gNB), the RRC reconfiguration message may be an RRCReconfiguration message, and the RRC reconfiguration complete message may be an RRCReconfigurationComplete message.

[0156] Figure 15 A messaging diagram 1500 depicts an exemplary scenario in which the UE 102 enables the MN 104 to initiate a SN release by providing an “artificial” measurement report related to the SN 106 .

[0157] At the beginning of the scenario, UE 102 operates in DC with MN 104 on at least one carrier frequency of MN 104 and with SN 106 on at least one carrier frequency of SN 106 (1502), similar to Figure 14 Event 1402 in the scenario of . Event 1504 is also similar to event 1404 discussed above.

[0158] In response to detecting a low charge condition of the battery 103, the UE 102 may inform the MN 104 that the UE 102 has disabled the DC capability to prevent the MN 104 from configuring the UE 102 to connect to the SN 106. In some embodiments, the UE 102 implicitly informs the MN 104 by generating an "artificial" measurement report message (1505) and sending it to the MN 104 (1507), which simulates to the MN 104 a low signal strength and / or low signal quality of the carrier frequency of the SN 104, regardless of whether the signal strength and / or signal quality is actually low, or even if the signal strength and / or signal quality is actually high or sufficient for communication, similar to Figure 11 1112 in the scenario of FIG. 1113 . Thus, similar to events 1313 and 1413 discussed above, UE 102 causes MN 104 to initiate release of SN 106 ( 1513 ). In response, MN 104 may send an RRC message to UE 102 ( 1515 ) to configure UE 102 to release SN 106 (i.e., release all of the at least one second carrier frequency). In response, UE 102 may send an RRC response message (not shown to avoid clutter) to MN 104. If MN 104 is an E-UTRA base station (e.g., an eNB or ng-eNB), the RRC message may be an RRC Connection Reconfiguration message, and the RRC response message may be an RRC RRC Connection Reconfiguration Complete message. If MN 104 is a 5G NR base station (e.g., a gNB), the RRC message may be an RRC Reconfiguration message, and the RRC response message may be an RRC Reconfiguration Complete message. In some scenarios (not shown to avoid clutter), as described above, before or after sending the RRC message (1515) to the UE 102, the MN 104 may send an SN Release Request message to the SN 106 in response to the MN 104 initiating the release of the SN 106. In such a scenario, the SN 106 may send an SN Release Acknowledge message to the MN 104 in response.

[0159] In other embodiments, UE 102 implicitly notifies MN 104 by generating and sending an "artificial" measurement report message to MN 104, which simulates low signal strength and / or low signal quality of some (i.e., one or more, but not all) of SN 106's carrier frequencies, regardless of whether the signal strength and / or signal quality are actually low. Thus, the "artificial" measurement report message triggers MN 104 to initiate the release of some (i.e., one or more, but not all) of SN 106's carrier frequencies. In one such embodiment, MN 104 determines to release some of SN 106's carrier frequencies for US 102. In response to receiving the "artificial" measurement report message from UE 102, MN 104 sends an SN Request message (1509) to SN 106, requesting SN 106 to release some of the carrier frequencies. In response to the SN Request message, SN 106 generates an RRC message indicating the release of some of the carrier frequencies. In response to the SN Request message, SN 106 sends an SN Request Acknowledge message including an RRC message to MN 104 (1511). MN 104 then sends the RRC message to UE 102 (1515). UE 102 then releases some of the carrier frequencies of SN 106 in response to the RRC message. UE 102 may send an RRC Response message in response to the RRC message. MN 104 may forward the RRC Response message to SN 106. By not communicating with SN 106 on some of the carrier frequencies of SN 106 (i.e., communicating with SN 106 on the remaining carrier frequencies of SN 106), UE 102 reduces heat generated by a chip used to support the RAT of SN 106.

[0160] In some embodiments, UE 102 may indicate some (i.e., one or more, but not all) of the carrier frequencies of SN 106 in a prioritized manner in an "artificial" measurement report message and send the "artificial" measurement report message to MN 104. For example, if the carrier frequencies of SN 106 include unlicensed carrier frequencies and licensed carrier frequencies, UE 102 may indicate the unlicensed carrier frequencies in a first "artificial" measurement report message and send the first "artificial" measurement report message to MN 104. The first "artificial" measurement report message may cause MN 104 to configure UE 102 to release the unlicensed carrier frequencies. If the low battery condition is still met after UE 102 releases the unlicensed carrier frequencies, UE 102 may indicate the licensed carrier frequencies in a second "artificial" measurement report message and send the second "artificial" measurement report message to MN 104. The second "artificial" measurement report message may cause MN 104 to configure UE 102 to release the unlicensed carrier frequencies.

[0161] As another example, UE 102 may indicate a higher carrier frequency over a lower carrier frequency for SN 106. For example, if the carrier frequency of SN 106 includes carrier frequencies in a certain range, such as FR2 (e.g., above 6 GHz or 7.125 GHz) and another range, such as FR1 (e.g., below 6 GHz or 7.125 GHz), the UE may indicate carrier frequencies in range FR2 before indicating carrier frequencies in range FR1. For example, if the carrier frequency of SN 106 includes a first carrier frequency in FR2 and a second carrier frequency in FR1, UE 102 may indicate the first carrier frequency in a first "artificial" measurement report message and send the first "artificial" measurement report message to MN 104. The first "artificial" measurement report message may cause MN 104 to configure UE 102 to release the first carrier frequency. If the low battery condition is still met after UE 102 releases the first carrier frequency, UE 102 indicates the second carrier frequency in a second “artificial” measurement report message and sends the second “artificial” measurement report message to MN 104. The second “artificial” measurement report message may cause MN 104 to configure UE 102 to release the second carrier frequency.

[0162] As another example, UE 102 may prioritize one or more carrier frequencies of SN 106 whose use causes UE 102 to generate more heat. For example, if the carrier frequencies of SN 106 include a first carrier frequency, the use of which causes the UE to generate more heat than the use of a second carrier frequency, UE 102 may indicate the first carrier frequency in a first "artificial" measurement report message and send the first "artificial" measurement report message to MN 104. The first "artificial" measurement report message may cause MN 104 to configure UE 102 to release the first carrier frequency. If the low battery condition is still met after UE 102 releases the first carrier frequency, UE 102 may indicate the second carrier frequency in a second "artificial" measurement report message and send the second "artificial" measurement report message to MN 104. The second "artificial" measurement report message may cause MN 104 to configure UE 102 to release the second carrier frequency.

[0163] In some embodiments of the UE 102 configured to release the SN 106, the DC controller 118 releases at least one of the carrier frequencies of the SN 106 (1506) in response to detecting a low battery condition (1504) rather than in response to receiving an RRC message (1515). In such embodiments, the UE 102 may release the carrier frequencies of the SN 106 in a prioritized manner. For example, if the carrier frequencies of the SN 106 include one or more unlicensed carrier frequencies and licensed carrier frequencies, the UE 102 may release the one or more unlicensed carrier frequencies before releasing the one or more licensed carrier frequencies. As another example, the UE 102 may prioritize releasing a higher carrier frequency of the SN 106 before releasing a lower carrier frequency. For example, if the carrier frequencies of the SN 106 include carrier frequencies within a certain range, such as FR2 (e.g., above 6 GHz or 7.125 GHz), and carrier frequencies within another range, such as FR1 (e.g., below 6 GHz or 7.125 GHz), the UE 102 may release carrier frequencies within the range FR2 before releasing carrier frequencies within the range FR1. As another example, the UE 102 may prioritize releasing some (e.g., one or more) of those carrier frequencies of the SN 106 whose use causes the UE 102 to generate more heat.

[0164] In another embodiment, in response to detecting the low battery condition (1504), the DC controller 118 sends a channel quality indicator (CQI) on a physical uplink control channel (PUCCH), wherein the CQI simulates low channel quality of at least one carrier frequency of the SN 106 to the MN 104, regardless of whether the channel quality is actually low, or even if the signal strength and / or signal quality is actually high or sufficient for communication. For example, zero or another predefined value (or range of values) indicates low channel quality. After the UE 102 determines that the low battery condition no longer applies, the DC controller 118 sends the CQI to the MN 104 to indicate the actual channel quality of at least one of the carrier frequencies of the SN 106.

[0165] Therefore, MN 104 may send an RRC message to UE 102 (1515) to configure UE 102 to release SN 106 in response to the RRC message. Then, in response to the RRC message, UE 102 disables DC operation with SN 106 (ie, releases SN 106) (1506).

[0166] Events 1514, 1516, and 1518 are similar to events 1414, 1416, and 1418 discussed above.

[0167] When UE 102 is within the coverage of SN 106 (e.g., UE 102 meets the threshold for DC) based on the signal strength or quality of at least one carrier frequency indicated in the measurement report message (1518), UE 102 may enable MN 104 to initiate an SN add procedure with SN 106. In some implementations, UE 102 sends the measurement report message (1518) to MN 104 so that MN 104 may initiate a procedure for adding at least one carrier frequency back to SN 106 for communication with SN 106. In response, MN 104 sends an SN Request message (e.g., an SN Addition Request message or an SN Modification Request message) (1517) to SN 106 to request SN 106 to configure UE 102 to receive downlink transmissions from SN 106 on the at least one carrier frequency. In response to the SN Request message, SN 106 generates an RRC message that configures UE 102 to receive downlink transmissions from SN 106 on the at least one carrier frequency, and sends an SN Request Acknowledge message (e.g., an SN Addition Request Acknowledge message or an SN Modification Request Acknowledge message) including the RRC message to MN 104 (1519). In response, MN 104 sends an RRC message to UE 102 (1521). UE 102 may then receive downlink transmissions from SN 106 on the at least one carrier frequency according to the RRC message. UE 102 may send an RRC Response message (e.g., an RRC Reconfiguration Complete message) to MN 104 in response to the RRC message (e.g., an RRC Reconfiguration message) (1523). MN 104 may forward the RRC Response message to SN 106 (1525).

[0168] Figure 16 A messaging diagram 1600 depicts an exemplary scenario in which the UE 102 enables the SN 106 to initiate an SN release by providing an “artificial” measurement report related to the SN 106 .

[0169] At the beginning of this scenario, UE 102 operates with MN 104 on at least one carrier frequency of MN 104 and with SN 106 on at least one carrier frequency of SN 106 in DC (1602), similar to Figure 15Event 1502 of the scenario. Event 1604 is similar to event 1504 discussed above.

[0170] In response to detecting a low battery condition of battery 103, UE 102 may inform SN 106 that UE 102 has disabled DC capability to prevent SN 106 from configuring UE 102 to connect to SN 106. UE 102 implicitly informs SN 106, or both MN 104 and SN 106 (i.e., with MN 104), by generating an “artificial” measurement report message (1605) and sending it to SN 106 via MN 104 (1607). Figure 15 16). In contrast to the implicit notification of MN 104 as described in , this "artificial" measurement report message simulates low signal strength and / or low signal quality of the carrier frequency of SN 106 to SN 104, regardless of whether the signal strength and / or signal quality are actually low, or even if the signal strength and / or signal quality are actually high or sufficient for communication. UE 102 may send the "artificial" measurement report message to SN 106 by using the radio resources of MN 104 or the radio resources of SN 106, such as SRB (e.g., SRB3). Thus, the "artificial" measurement report message triggers the SN 106 to initiate the release of SN 106 (1613). In response, SN 106 may send an SN Release Required message (1609) to MN 104, and MN 104 may send an RRC message (1611) to UE 102 to configure UE 102 to release SN 106 in response to the SN Release Required message. In some scenarios (not shown to avoid clutter), before or after sending the RRC message to UE 102 (1611) as described above, MN 104 may send an SNReleaseConfirm message to SN 106 in response to the SN Release Required message. In such a scenario, UE 102 may send an RRC Response message to MN 104 in response. If MN 104 is an E-UTRA base station (e.g., eNB or ng-eNB), the RRC message may be an RRC ConnectionReconfiguration message, and the RRC Response message may be an RRC ConnectionReconfigurationComplete message. If MN 104 is a 5G NR base station (e.g., gNB), the RRC message may be an RRCReconfiguration message, and the RRC Response message may be an RRC ReconfigurationComplete message.

[0171] In other embodiments, UE 102 implicitly notifies SN 106 by generating and sending an "artificial" measurement report message to SN 106 that simulates low signal strength and / or low signal quality for some (i.e., one or more, but not all) of SN 106's carrier frequencies, regardless of whether the signal strength and / or signal quality are actually low. Thus, the "artificial" measurement report message triggers SN 106 to initiate the release of some (i.e., one or more, but not all) of SN 106's carrier frequencies. In one such embodiment, SN 106 determines to release some of SN 106's carrier frequencies for UE 102. In response to receiving the "artificial" measurement report message from UE 102, SN 106 generates an RRC message indicating the release of some of the carrier frequencies. SN 106 sends the RRC message to UE 102 via MN 104 using radio resources of MN 104 or radio resources of SN 106, such as an SRB (e.g., SRB3). Then, UE 102 releases some carrier frequencies of SN 106 in response to the RRC message, thereby reducing heat generated by a chip used to support the RAT of SN 106. As described above, if UE 102 receives the RRC message from MN 104, UE 102 transmits an RRC response message to MN 104. If UE 102 receives the RRC message from SN 106 by using SRB, UE 102 may transmit an RRC response message (e.g., RRC Reconfiguration Complete message) to SN 106 by using radio resources of SN 106 in response to the RRC message (e.g., RRC Reconfiguration message).

[0172] Therefore, SN 106 may send an RRC message to UE 102 to configure UE 102 to release SN 106 in response to the RRC message (1611). UE 102 then disables DC operation with SN 106 (i.e., releases SN 106) in response to the RRC message (1606), similar to Figure 15 Event 1506.

[0173] Events 1614, 1616, and 1618 are similar to events 1514, 1516, and 1518 discussed above.

[0174] When UE 102 is within the coverage of SN 106 (e.g., UE 102 meets the threshold of DC) according to the signal strength or quality of at least one carrier frequency indicated in the measurement report message (1618), UE 102 may enable MN 104 to initiate an SN add procedure with SN 106. In some embodiments, UE 102 sends the measurement report message (1618) to SN 106 via MN 104 by using radio resources of MN 104 or radio resources of SN 106, such as SRB (e.g., SRB3), so that SN 106 may initiate adding back at least one carrier frequency of SN 106 for communication with SN 106. Accordingly, SN 106 may configure UE 102 to receive transmissions from SN 106 on the at least one carrier frequency. SN 106 may send an RRC message (e.g., an RRC Reconfiguration message) to UE 102 in response to the measurement report message to configure UE 102 to receive transmissions from SN 106 on the at least one carrier frequency. In response, UE 102 may send an RRC response message (e.g., an RRC Reconfiguration Complete message) to SN 106 (1620).

[0175] In some embodiments, if the UE 106 is configured by the SN 106 to use a DRB, such as an SCG type bearer or an SCG split type bearer, the RRC message may reconfigure the DRB to an MCG type bearer. The UE 102 may then communicate data with the MN 104 using the DRB in response to the RRC message.

[0176] Figure 17 Depicted is an example method 1700 for determining whether a UE 102 should disable 5G NR operation for DC and (optionally) CA capabilities in view of detecting a low battery condition.

[0177] Method 1700 begins at block 1702 where UE 102 determines whether a low battery condition has occurred in battery 103, similar to Figure 2202. If the UE 102 does not detect a low battery condition, then at block 1704, the UE 102 enables 5G NR operation for DC when 5G NR operation was previously disabled. In another scenario, when 5G NR operation is already enabled, the UE 102 maintains 5G NR operation for DC enabled. Examples of 5G NR operation include transmitting uplink transmissions on 5G NR to the SN 106 (e.g., transmitting uplink reference signals such as sounding reference signals (SRS), transmissions on the PUCCH, transmissions on the PUSCH), receiving downlink transmissions on 5G NR from the SN 106 (e.g., receiving reference signals such as channel state information reference signals (CSI-RS) and / or synchronization signal blocks (SSBs), transmissions on the PDCCH, transmissions on the PDSCH), and / or measuring at least one 5G NR carrier frequency of the SN 106.

[0178] However, if UE 102 detects a low battery condition, then if 5G NR operation was previously enabled, UE 102 disables 5G NR operation for DC at block 1708. For example, UE 102 may stop receiving downlink transmissions via 5G NR from SN 106, stop sending uplink transmissions via 5G NR to SN 106, stop measuring at least one 5G NR carrier frequency, and / or continue measuring at least one 5G NR carrier frequency. In another scenario, when 5G NR operation is already disabled, UE 102 maintains 5G NR operation for DC disabled. In an embodiment, UE 102 turns off or deactivates a 5G NR RF chip configured to communicate with SN 106, which is implemented as a gNB, to disable 5G NR operation for DC, thereby reducing power consumption. Blocks 1706 and 1710 are similar to blocks 206 and 210 discussed above.

[0179] Figure 18 An exemplary method 1800 is depicted for determining whether a UE 102 operating in a connected state of the RRC protocol should disable 5G NR operation for DC in view of detecting a low battery condition.

[0180] Method 1800 begins at block 1801, where UE 102 operates in a connected state, such that UE 102 can operate in SC with MN 104 on the carrier frequency of MN 104. At block 1802, UE 102 determines whether a low battery condition has occurred in battery 103, similar to block 1702 discussed above. Blocks 1804 and 1806 are also similar to blocks 1704 and 1708 discussed above.

[0181] In some implementations, in addition to enabling 5G NR operation for DC, the UE 102 enables 5G NR measurement at block 1808. The UE 102 then sends a measurement report message including 5G NR measurement results based on the 5G NR measurement at block 1810 on a carrier used for communication with the SN 106 implemented as a gNB.

[0182] In some implementations, in addition to disabling 5G NR operation for DC, the UE 102 disables 5G NR measurements at block 1812. Accordingly, the UE 102 prohibits sending a measurement report message including 5G NR measurement results to the MN 104 at block 1814. Thus, the UE 102 prevents the MN 104 from initiating an SN add procedure with the SN 106 implemented as a gNB, while continuing to support SC between the UE 102 and the MN 104.

[0183] Despite Figure 18 The method 1800 is shown to be complete after block 1810 or block 1814, but in general, the UE 102 may perform the method 1800 in an iterative manner, for example, by "looping back" to block 1801 after performing block 1810 or block 1814.

[0184] Figure 19 An exemplary method 1900 is depicted for determining whether a UE 102 operating in an idle or inactive state of the RRC protocol should disable 5G NR operation for DC in view of detecting a low battery condition.

[0185] like Figure 19 As shown in FIG, prior to detecting a low battery condition of the battery at block 1902, the UE 102 is operating in an idle or inactive state at block 1901. As such, the UE 102 may not yet be operating in a connected state and, therefore, may not be operating in SC with the MN 104 on the carrier frequency of the MN 104. Similar to block 1802 discussed above, the UE 102 determines at block 1902 whether a low battery condition of the battery 103 has occurred. Blocks 1902, 1904, 1906, 1908, 1910, 1912, and 1914 are also similar to blocks 1802, 1804, 1806, 1808, 1810, 1812, and 1814 discussed above.

[0186] As shown, after UE 102 enables 5G NR operation for DC at box 1904 and disables 5G NR operation for DC at box 1906, UE 102 is in a connected state at boxes 1907 and 1909, respectively.

[0187] Figure 20Depicted is an example method 2000 for preventing a UE 102 from operating in DC due to a low battery condition.

[0188] Method 2000 begins at block 2002, where, similar to block 1702 discussed above, UE 102 determines whether a low battery condition has occurred (e.g., a remaining battery level is below a first threshold level) in battery 103. Blocks 2004, 2006, and 2008 are also similar to blocks 1704, 1706, and 1708 discussed above.

[0189] However, if at block 2009 UE 102 detects a different low battery condition (eg, the remaining battery level is below a second threshold level that is lower than the first threshold level), then at block 2010 UE 102 disables MN CA capability, similar to block 1710 discussed above.

[0190] Figure 21 An exemplary method 2100 is depicted in which, upon detecting a low battery condition of the battery 103 , the UE 102 releases one or more carrier frequencies of the SN 106 .

[0191] Method 2100 begins at block 2102, where UE 102 operates with MN 104 on at least one first carrier frequency of MN 104 in DC and with SN 106 on a second carrier frequency of SN 106, similar to events 1502 and 1602 discussed above.

[0192] UE 102 determines at block 2104 whether a low battery condition (e.g., a remaining battery level is below a first threshold level) of battery 103 has occurred, similar to events 1504 and 1604 discussed above. If UE 102 does not detect a low battery condition, UE 102 continues to determine whether a low battery condition has occurred.

[0193] If UE 102 detects a low battery condition, UE 102 sends an “artificial” measurement report message to MN 104 and / or SN 106 at block 2106, which simulates to MN 104 and / or SN 106 low signal strength and / or low signal quality of at least one second carrier frequency of said SN 106, regardless of whether the signal strength and / or signal quality is actually low, similar to events 1507 and 1607 discussed above. As a result, UE 102 suspends SCG transmission on at least one second carrier frequency of SN 106.

[0194] UE 102 determines at block 2108 whether a low battery condition has occurred for battery 103, similar to events 1504 and 1604 discussed above. The low battery condition may be the same low battery condition as in block 2104 (e.g., the remaining battery level is below a first threshold level), or a different low battery condition (e.g., the remaining battery level is below a second threshold level that is lower than the first threshold level). If UE 102 does not detect a low battery condition, UE 102 continues to determine whether a low battery condition has occurred.

[0195] If UE 102 detects a low battery condition, UE 102 sends another “artificial” measurement report message to MN 104 and / or SN 106 at box 2110, which simulates to MN 104 and / or SN 106 a low signal strength and / or low signal quality of at least another second carrier frequency of SN 106 among the remaining second carrier frequencies, regardless of whether the signal strength and / or signal quality is actually low, similar to events 1507 and 1607 discussed above.

[0196] In some embodiments, if the UE 102 continues to detect a low battery condition at block 2110, the UE 102 may send another “artificial” measurement report message (i.e., a third “artificial” measurement report message) to the MN 104 and / or SN 106, which simulates low signal strength and / or low signal quality of the remaining second carrier frequencies to the MN 104 and / or SN 106, regardless of whether the signal strength and / or signal quality are actually low. In some embodiments, if the UE 102 continues to detect a low battery condition at block 2110, the UE 102 may iteratively send the third “artificial” measurement report message to the MN 104 and / or SN 106 to indicate low signal strength and low signal quality of the remaining second carrier frequencies one by one until the UE 102 takes into account all remaining second carrier frequencies.

[0197] Block 2112 is similar to events 1506 and 1606 and block 1708 discussed above. In an embodiment, UE 102 may stop measuring some or all of the 5G NR carrier frequencies configured by the measurement configuration received from MN 104 or SN 106. Thus, UE 102 may consume less power (or even no power) by disabling DC operation (e.g., by turning off or deactivating one of the chips used to support the RAT of SN 106). In addition, UE 102 may reduce (or prevent) heating from the chip used to support the RAT of SN 106.

[0198] Despite Figure 21The illustrated method 2100 is complete after block 2110 , but in general, the UE 102 may perform the method 2100 in an iterative manner, for example by “looping back” to block 2102 after performing block 2110 .

[0199] Figure 22 An exemplary method 2200 is depicted in which the UE 102 prevents the MN 104 from initiating an SN add procedure in view of an "artificial" measurement report and an indication of an SCG failure.

[0200] Method 2200 begins at block 2202, where, similar to block 2102 discussed above, UE 102 operates with MN 104 on at least one first carrier frequency of MN 104 in DC and with SN 106 on at least one second carrier frequency of SN 106.

[0201] Blocks 2204, 2206, 2208, 2210, and 2212 are similar to blocks 2104, 2106, 2108, 2210, and 2212 discussed above.

[0202] The UE 102 generates an indication of SCG failure (eg, an SCG failure message) or an indication of MCG failure (eg, an RRC reestablishment request message) at block 2214 to inform the MN 104 that the UE 102 will no longer use DC, similar to events 1307 and 1407, respectively.

[0203] Despite Figure 22 The illustrated method 2200 is complete after block 2212 , but in general, the UE 102 may perform the method 2200 in an iterative manner, for example, by “looping back” to block 2202 after performing block 2212 .

[0204] Figure 23 Depicted is an example method 2300 for preventing a UE 102 from operating in DC due to a low battery condition.

[0205] Method 2300 begins at block 2302, where UE 102 detects a low battery state of battery 103 ( Figure 2-22 In response to detecting a low battery condition, the UE 102 blocks the UE 102 and the SN 106 from operating in DC at block 2304, so that the UE 102 and the MN 104 can only operate in SC. Specifically, as Figure 2-22As described in blocks or events 208, 308, 408, 508, 608, 609, 708, 808, 908, 1008, 1106, 1206, 1207, 1306, 1406, 1506, 1606, 1708, 1806, 1906, 2008, 2112, and 2212 of UE 102, at block 2304, UE 102 prevents UE 102 from operating in DC with SN 106 by disabling DC capability. In some embodiments, as Figure 2-3 , 8-10, 17 and 20, or events 210, 310, 710, 810, 910, 1010, 1710 and 2010, the UE 102 at block 2304 prevents the UE 102 from operating in DC with the SN 106 by also disabling the MN CA capability.

[0206] The following additional considerations apply to the preceding discussion.

[0207] "Carrier frequency" may be interchanged with "cell", "secondary cell (SCell)" or "primary secondary cell (PSCell)". A cell or SCell may be a frequency division duplex (FDD) cell or a time division duplex (TDD) cell. In the case of a TDD cell, the UE may be configured by the SN to receive downlink transmissions on the carrier frequency of the TDD cell, but may or may not be configured to send uplink transmissions on the carrier frequency of the TDD cell. In the case of an FDD cell, the UE may be configured by the SN to receive downlink transmissions on the downlink carrier frequency of the FDD cell, but may or may not be configured to send uplink transmissions on the uplink carrier frequency of the FDD cell.

[0208] The user equipment (e.g., UE 102) in which the technology of the present disclosure may be implemented may be any suitable device capable of wireless communication, such as a smartphone, tablet computer, laptop computer, mobile game console, point of sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or another personal media device, wearable device (such as a smart watch), wireless hotspot, femtocell or broadband router. In addition, in some cases, the user equipment may be embedded in an electronic system such as a head unit or an advanced driver assistance system (ADAS) of a vehicle. Further, the user equipment may be operated as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user equipment may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0209] In this disclosure, certain embodiments are described as including logic or multiple components or modules. A module can be a software module (e.g., code or machine-readable instructions stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and can be configured or arranged in a certain manner. A hardware module can include dedicated circuitry or logic that is permanently configured to perform certain operations (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or application-specific integrated circuit (ASIC), digital signal processor (DSP)). A hardware module can also include programmable logic or circuitry that is temporarily configured by software to perform certain operations (e.g., as contained in a general-purpose processor or other programmable processor). The decision to implement a hardware module as a dedicated and permanently configured circuit or as a temporarily configured circuit (e.g., configured by software) is driven by cost and time considerations.

[0210] When implemented in software, the techniques may be provided as part of the operating system, as a library used by multiple applications, as a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

[0211] After reading this disclosure, those skilled in the art will recognize additional and alternative structural and functional designs for handling DC based on a low battery condition of a user device's battery, using the principles disclosed herein. Therefore, while specific embodiments and applications have been shown and described, it should be understood that the disclosed embodiments are not limited to the precise configurations and components disclosed herein. It will be apparent to those skilled in the art that various modifications, changes, and variations may be made to the arrangement, operation, and details of the methods and apparatus disclosed herein without departing from the spirit and scope of the appended claims.

[0212] Aspect 1. A method in a user equipment (UE), wherein the user equipment is capable of operating with a master node (MN) and a secondary node (SN) in dual-mode connectivity (DC), the method comprising: detecting a low battery condition of a battery of the UE by processing hardware; and in response to detecting the low battery condition of the battery: preventing the UE from operating with the SN in DC by the processing hardware, so that the UE and the MN are configured to operate in single connectivity.

[0213] Aspect 2. The method according to aspect 1, wherein preventing the UE from operating in DC comprises sending an indication from the UE to the MN that the UE has disabled DC.

[0214] Aspect 3. The method according to aspect 2, further comprising, before detecting the low power condition of the battery: sending an indication that the UE has enabled DC from the UE to the MN.

[0215] Aspect 4. The method according to aspect 2 or 3, wherein sending an indication that the UE has disabled DC or an indication that the UE has enabled DC includes sending a UE capability information message from the UE to the MN.

[0216] Aspect 5. A method according to aspect, wherein sending the UE capability information message includes: generating a radio access capability information element (IE); and including a DC band combination in the radio access capability IE to indicate that the UE has enabled DC, or not including a DC band combination in the radio access capability IE to indicate that the UE has disabled DC.

[0217] Aspect 6. A method according to Aspect 4, wherein sending the UE capability information message includes: generating a radio access capability IE; and including at least one of a DC support indicator or a list of DC supported frequency bands in the radio access capability IE to indicate that the UE has enabled DC, or not including a DC support indicator or a list of DC supported frequency bands in the radio access capability IE to indicate that the UE has disabled DC.

[0218] Aspect 7. A method according to Aspect 4, wherein sending the UE capability information message includes: including a radio access capability IE in the UE capability information message to indicate that the UE has enabled DC, or not including a radio access capability IE in the UE capability information message to indicate that the UE has disabled DC.

[0219] Aspect 8. The method according to aspect 1, wherein preventing the UE from operating in DC comprises: suspending measurement of the carrier frequency of the SN.

[0220] Aspect 9. The method according to aspect 1 or 8, wherein preventing the UE from operating in DC includes: suspending reporting of measurements on the carrier frequency of the SN.

[0221] Aspect 10. A method according to aspect 1, wherein the MN operates by using a first radio access technology (RAT) and the second SN operates by using a second RAT, and wherein preventing the UE from operating in DC includes: disabling a chip for supporting the UE to communicate according to the second RAT.

[0222] Aspect 11. The method according to any one of the preceding aspects, further comprising: disabling MN carrier aggregation (CA) in response to detecting a low power condition of the battery.

[0223] Aspect 12. The method according to aspect 11 further comprises: generating a radio access capability IE; and including an MN CA band combination in the radio access capability IE to indicate that the UE has enabled MN CA, and not including an MN CA band combination in the radio access capability IE to indicate that the UE has disabled MN CA.

[0224] Aspect 13. The method according to aspect 11, wherein the low battery condition of the battery includes a first threshold level and a second threshold level, and wherein: in response to detecting that the battery battery level is lower than the first threshold level, the UE is prevented from operating in DC, and in response to the battery battery level being lower than a second threshold level lower than the first threshold level, MN CA is disabled.

[0225] Aspect 14. The method according to any one of the preceding aspects further comprises, after preventing the UE from operating in DC: in response to determining that the low battery condition no longer applies, enabling the UE to operate in DC with the SN.

[0226] Aspect 15. The method according to any one of the preceding aspects, wherein detecting the low battery condition of the UE comprises determining that a battery level of the UE is lower than a threshold level.

[0227] Aspect 16. The method according to aspect 15 further comprises, after detecting the low battery condition: in response to detecting by the processing hardware that a battery of the UE is receiving charge from a power source, determining that the low battery condition no longer applies.

[0228] Aspect 17. The method according to aspect 15 further comprises, after detecting the low battery condition: in response to detecting by the processing hardware that the battery level of the UE is higher than the threshold level, determining that the low battery condition no longer applies.

[0229] Aspect 18. The method according to Aspect 1 further includes, in response to detecting a low battery condition of the battery: determining that the UE is currently in a connected state according to a protocol for controlling radio resources; in a first instance, in response to determining that the operating condition is not met, immediately preventing the UE from operating in DC; and in a second instance, in response to determining that the operating condition is met, postponing preventing the UE from operating in DC until the operating condition is met.

[0230] Aspect 19. A method according to aspect 18, wherein the operating condition is one of the following: (i) the UE is currently participating in a voice or video call, (ii) the screen of the UE is in an on state, or (iii) the energy saving feature of the UE has been disabled.

[0231] Aspect 20. A UE comprising processing hardware and configured to implement the method according to any one of aspects 1 to 19.

[0232] Aspect 21. A UE capable of operating in dual-mode connectivity (DC) with a master node (MN) and a secondary node (SN), the UE comprising: a battery; a controller; and a memory coupled to the controller and configured to store computer-executable instructions, which, when executed by the controller, cause the controller to perform the following operations: detect a low battery condition of the battery of the UE; and in response to detecting the low battery condition of the battery, prevent the UE from operating in DC with the SN, so that the UE and MN are configured to operate in single connectivity.

[0233] Aspect 22. The UE according to Aspect 21, wherein the memory is further configured to store a predetermined threshold level corresponding to a predetermined remaining battery capacity; and the instructions, when executed by the controller, cause the controller to detect a low battery condition of the battery by comparing the state of the battery with the predetermined threshold level.

[0234] Aspect 23. The UE according to Aspect 21 further includes: a first module, which supports communication with the MN by using a first radio access technology (RAT); a second module, which supports communication with the SN by using a second RAT, wherein the instruction, when executed by the controller, causes the controller to prevent the UE and the SN from operating in DC by enabling the first module and disabling the second module.

[0235] Aspect 24. The UE according to aspect 21, wherein the instructions, when executed by the controller, cause the controller to prevent the UE from operating in DC with the SN by sending an indication to the MN that the UE has disabled DC.

[0236] Aspect 25: The UE according to aspect 21, wherein the instructions, when executed by the controller, cause the controller to prevent the UE from operating in DC with the SN by sending a failure indication of a secondary cell group (SCG) associated with the SN to the MN.

[0237] Aspect 26: The UE according to aspect 21, wherein the instructions, when executed by the controller, cause the controller to prevent the UE and the SN from operating in DC by sending a failure indication of a master cell group (MCG) associated with the MN to the MN.

[0238] Aspect 27. The UE according to aspect 21, wherein the instructions, when executed by the controller, cause the controller to: detect that the UE is connected to a power source; and in response to detecting that the UE is connected to the power source, enable the UE to operate in DC with the SN.

[0239] Aspect 28. A method in a user equipment (UE), wherein the UE is capable of operating with a master node (MN) and a secondary node (SN) in dual-mode connectivity (DC), the method comprising: detecting a low battery condition of a battery of the UE by processing hardware; and in response to detecting the low battery condition of the battery: preventing the UE from operating with the SN in DC by the processing hardware, so that the UE and the MN are configured to operate in single connectivity.

[0240] Aspect 29. The method according to aspect 28, wherein preventing the UE from operating in DC comprises sending a failure indication of a secondary cell group (SCG) associated with the SN from the UE to the MN.

[0241] Aspect 30. The method according to aspect 29, wherein sending the failure indication of the SCG comprises: sending an SCG failure message from the UE to the MN.

[0242] Aspect 31. The method according to aspect 30, wherein the SCG fault message includes a measurement result, and the measurement result includes a signal strength or a signal quality of a carrier frequency of the SN.

[0243] Aspect 32. The method according to aspect 30 further comprises: receiving an RRC reconfiguration message from the MN in response to the SCG failure message; and releasing the configuration for communicating with the SN in response to the RRC reconfiguration message.

[0244] Aspect 33. The method according to aspect 29, wherein sending the fault indication of the SCG comprises: including a fault type indicator corresponding to the low charge condition of the battery in the indication.

[0245] Aspect 34. A method according to aspect 29, wherein sending the fault indication of the SCG includes: including a fault type indicator set to t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, synchReconfigFailure-SCG, scg-reconfigFailure or srb3-IntegrityFailure in the indication.

[0246] Aspect 35. The method of aspect 28, wherein preventing the UE from operating in DC comprises sending a failure indication of a master cell group (MCG) associated with the MN from the UE to the MN.

[0247] Aspect 36. The method according to aspect 35, wherein sending the failure indication of the MCG includes: sending an RRC re-establishment request message from the UE to the MN.

[0248] Aspect 37. The method according to aspect 36, wherein the RRC re-establishment request message includes a measurement result, and the measurement result includes a signal strength or signal quality of a carrier frequency of the SN.

[0249] Aspect 38. The method according to Aspect 36 further includes: receiving an RRC reconstruction message from the MN in response to the RRC reconstruction request message; and sending an RRC reconstruction completion message to the MN in response to the RRC reconstruction message; and enabling the MN to initiate the release of the SN in response to the RRC reconstruction completion message.

[0250] Aspect 39. The method according to aspect 35, wherein sending the fault indication of the MCG comprises: including a fault type indicator corresponding to the low charge condition of the battery in the indication.

[0251] Aspect 40. The method according to aspect 35, wherein sending the fault indication of the MCG comprises: including a fault type indicator set to reconfigurationFailure, handoverFailure, or otherFailure in the indication.

Claims

1. A method in a user equipment capable of operating with dual-mode connectivity with a primary node and a secondary node, the method comprising: detecting, by processing hardware of the user equipment, a low battery condition of a battery of the user equipment; as well as In response to detecting, by the processing hardware of the user device, the low battery condition of the battery: Preventing, by the processing hardware of the user device, the user device and the secondary node from operating in dual-mode connectivity such that the user device and the primary node are configured to operate in single connectivity, wherein preventing includes providing simulated signal strength measurements to at least one of the primary node and the secondary node.

2. The method according to claim 1, wherein Preventing the user equipment from operating in dual mode connectivity comprises suspending measurements of a carrier frequency of the secondary node.

3. The method according to claim 1, wherein Preventing the user equipment from operating in dual mode connectivity comprises suspending reporting of measurements on a carrier frequency of the secondary node.

4. The method according to claim 1, wherein The primary node operates using a first radio access technology (RAT) and the secondary node operates using a second RAT, and wherein preventing the user equipment from operating with dual-mode connectivity comprises: A chip of the user equipment that supports communication according to the second RAT is disabled.

5. The method according to claim 1, further comprising: In response to detecting the low battery condition of the battery, master node carrier aggregation is disabled.

6. The method according to claim 5, wherein: The low charge condition of the battery comprises a first threshold level and a second threshold level, and wherein: responsive to detecting that the charge level of the battery is below the first threshold level, preventing the user equipment from operating in dual mode connectivity, and In response to detecting that the charge level of the battery is below a second threshold level that is lower than the first threshold level, master node carrier aggregation is disabled.

7. The method according to any one of claims 1 to 6, further comprising, after preventing the user equipment from operating in dual mode connectivity: In response to determining that the low battery condition no longer applies, the user equipment is enabled to operate in dual-mode connectivity with the secondary node.

8. The method according to claim 1, wherein Detecting the low battery condition of the user equipment includes determining that a charge level of the battery of the user equipment is below a threshold level.

9. The method of claim 8, further comprising, after detecting the low battery condition: In response to detecting, by the processing hardware, that a battery of the user device is receiving a charge from a power source, it is determined that the low battery condition no longer applies.

10. The method of claim 8, further comprising, after detecting the low battery condition: In response to detecting, by the processing hardware, that the charge level of the battery of the user device is above the threshold level, it is determined that the low battery condition no longer applies.

11. The method of claim 1 , further comprising, in response to detecting a low battery condition of the battery: determining, according to a protocol for controlling radio resources, that the user equipment is currently in a connected state; In a first instance, in response to determining that the operating condition is not satisfied, immediately preventing the user equipment from operating in the dual mode connectivity; and In a second example, in response to determining that the operating condition is satisfied, preventing the user equipment from operating with the dual mode connectivity is deferred until the operating condition is satisfied.

12. The method according to claim 11, wherein The operating conditions are one of the following: (i) the user device is currently participating in a voice or video call, (ii) the screen of the user device is turned on, or (iii) The energy saving feature of the user equipment has been disabled.

13. A user equipment comprising processing hardware and configured to implement the method according to any one of claims 1 to 12.

14. A user equipment capable of operating with a primary node and a secondary node in dual-mode connectivity, the user equipment comprising: Battery; Controller; as well as a memory coupled to the controller and configured to store computer-executable instructions that, when executed by the controller, cause the controller to: detecting a low battery condition of a battery of the user device; as well as In response to detecting the low charge condition of the battery, the controller of the user device prevents the user device from operating in dual-mode connectivity with the secondary node, such that the user device and the primary node are configured to operate in single connectivity, wherein preventing includes providing a simulated signal strength measurement to at least one of the primary node and the secondary node.

15. The user equipment according to claim 14, wherein: The memory is further configured to store a predetermined threshold level corresponding to a predetermined remaining battery capacity; and The instructions, when executed by the controller, further cause the controller to detect a low battery condition of the battery by comparing the status of the battery to the predetermined threshold level.

16. The user equipment according to claim 14, further comprising: a first module that supports communication with the master node using a first radio access technology (RAT); a second module, the second module supporting communication with the secondary node using a second RAT, Wherein, the instructions, when executed by the controller, further cause the controller to prevent the user equipment from operating with the secondary node in dual-mode connectivity by enabling the first module and disabling the second module.

17. The user equipment according to claim 14, wherein: The instructions, when executed by the controller, further cause the controller to prevent the user equipment from operating in dual mode connectivity with the secondary node by sending an indication to the primary node that the user equipment has disabled dual mode connectivity.

18. The user equipment according to claim 14, wherein: The instructions, when executed by the controller, cause the controller to: detecting that the user device is connected to a power source; and In response to detecting that the user equipment is connected to the power source, the user equipment is enabled to operate in dual-mode connectivity with the secondary node.

Images