Patent Description:
This background description is provided for the purpose of generally presenting the context of the disclosure.

In telecommunication systems, the Packet Data Convergence Protocol (PDCP) sublayer of the radio protocol stack provides services such as transfer of user-plane data, ciphering, integrity protection, etc. For example, the PDCP layer defined for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface (see 3GPP specification TS <NUM>) and New Radio (NR) (see 3GPP specification TS <NUM>) provides sequencing of protocol data units (PDUs) in the uplink direction (from a user device, also known as a user equipment (UE), to a base station) as well as in the downlink direction (from the base station to the UE). Further, the PDCP sublayer provides services for signaling radio bearers (SRBs) to the Radio Resource Control (RRC) sublayer. The PDCP sublayer also provides services for data radio bearers (DRBs) to a Service Data Adaptation Protocol (SDAP) sublayer or a protocol layer such as an Internet Protocol (IP) layer, an Ethernet protocol layer, and an Internet Control Message Protocol (ICMP) layer. Generally speaking, the UE and a base station can use SRBs to exchange RRC messages as well as non-access stratum (NAS) messages, and can use DRBs to transport data on a user plane.

UEs can use several types of SRBs and DRBs. When operating in dual connectivity (DC), the cells associated with the base station operating as the master node (MN) define a master cell group (MCG), and the cells associated with the base station operating as the secondary node (SN) define the secondary cell group (SCG). So-called SRB1 resources carry RRC messages, which in some cases include NAS messages over the dedicated control channel (DCCH), and SRB2 resources support RRC messages that include logged measurement information or NAS messages, also over the DCCH but with lower priority than SRB1 resources. More generally, SRB1 and SRB2 resources allow the UE and the MN to exchange RRC messages related to the MN and embed RRC messages related to the SN, and also can be referred to as MCG SRBs. SRB3 resources allow the UE and the SN to exchange RRC messages related to the SN, and can be referred to as SCG SRBs. Split SRBs allow the UE to exchange RRC messages directly with the MN via lower layer resources of the MN and the SN. Further, DRBs terminated at the MN and using the lower-layer resources of only the MN can be referred as MCG DRBs, DRBs terminated at the SN and using the lower-layer resources of only the SN can be referred as SCG DRBs, and DRBs terminated at the MCG but using the lower-layer resources of the MN, the SN, or both the MN and the SN can be referred to as split DRBs.

The UE in some scenarios can concurrently utilize resources of multiple nodes (e.g., base stations or components of a distributed base station) of a radio access network (RAN), interconnected by a backhaul. When these network nodes support different radio access technologies (RATs), this type of connectivity is referred to as Multi-Radio Dual Connectivity (MR-DC). When a UE operates in MR-DC, one base station operates as the MN that covers a primary cell (PCell), and the other base station operates as the SN that covers a primary secondary cell (PSCell). The UE communicates with the MN (via the PCell) and the SN (via the PSCell). In other scenarios, the UE utilizes resources of one base station at a time. One base station and/or the UE determines that the UE should establish a radio connection with another base station. For example, one base station can determine to hand the UE over to the second base station, and initiate a handover procedure. The UE in other scenarios can concurrently utilize resources of a RAN node (e.g., a single base station or a component of a distributed base station), interconnected to other network elements by a backhaul.

Documents 3GPP TS <NUM> v16. <NUM>, <NUM> v16. <NUM>, and <NUM> v16. <NUM> describe certain procedures related to handover or "reconfiguration with sync" scenarios. These procedures involve messaging (e.g., RRC signaling and preparation) between RAN nodes and a UE. UEs can perform handover procedures to switch from one cell to another, whether in single connectivity (SC) or DC or other type of multi-connectivity operation. The UE may hand over from a cell of a serving base station to a target cell of a target base station, or from a cell of a first distributed unit (DU) of a serving base station to a target cell of a second DU of the same base station, depending on the scenario.

Document 3GPP TS <NUM> v16. <NUM> describes certain procedures for a UE to change PSCells in DC scenarios. These procedures involve messaging (e.g., RRC signaling and preparation) among RAN nodes and the UE. The UE may perform PSCell change from a PSCell of a serving SN to a target PSCell of a target SN, or from a PSCell of a source distributed unit (DU) of a base station to a PSCell of a target DU of the same base station, depending on the scenario.

More recently, 3GPP has been discussing and standardizing new technologies including for Release <NUM> (Rel-<NUM>) specifications such as 3GPP specifications <NUM> v16. <NUM> and <NUM> v16. The new technologies include dual active protocol stack (DAPS) handover and DAPS PSCell change procedures for achieving <NUM> user data interruption during handover and PSCell change, respectively. Generally, the length of interruption experienced at the UE depends on a time difference between the time when a radio link connection at a source cell is released and the time when a radio link connection at a target cell is established. If the release time is no earlier than the established time, achieving <NUM> user data interruption is possible. Using a DAPS, the UE can simultaneously communicate with the source cell while establishing a radio link connection at the target cell, and subsequently stop communicating with the source cell after establishing a radio link connection at the target cell, when performing DAPS handover and DAPS PSCell change.

In some cases, the RAN can provide a DAPS power coordination configuration (e.g., daps-PowerCoordinationInfo-r16) to the UE for the UE to perform a DAPS handover or DAPS PSCell change. The DAPS power coordination configuration generally indicates the maximum power that the UE can transmit on the source PCell and the maximum power that the UE can transmit on the target PCell. The DAPS power coordination configuration can also indicate the power control mode used by the UE during a DAPS handover. Upon receiving the DAPS power coordination configuration, the UE configures its lower layer (e.g., physical layer) to apply the DAPS power coordination configuration. However, in some of these scenarios, the UE and/or RAN may mishandle the DAPS power coordination configuration, causing the UE to unnecessarily restrict its maximum uplink power. As a result, in some scenarios, such as cell edge scenarios, the RAN may not receive transmissions from the UE, and the UE can encounter radio link failure, which causes service interruption.

In some cases, upon detecting a radio link failure while communicating with a source base station of the RAN using a configuration, the UE may suspend the configuration and initiate an RRC connection re-establishment procedure with a target base station of the RAN. However, in some scenarios, as the UE attempts to resume the configuration with the target base station, communication errors between the UE and the target base station may occur, such as when the target base station does not support the configuration otherwise supported by the source base station. In a submission entitled "<NPL>), the authors discuss proposals for how to enable UE capability sharing between source and target eNBs during DAPS HO. In a submission entitled "<NPL>, the authors discuss proposals for how to enable UE capability sharing between source and target eNBs during a DAPS based enhanced MBB HO procedure.

Generally speaking, a UE and one or more base stations operating in a RAN implement the techniques of this disclosure to prepare the UE to perform a DAPS procedure (i.e., DAPS handover, DAPS PSCell change). Using these techniques, for example, the RAN can provide a DAPS power coordination configuration to the UE to restrict the maximum power that the UE can transmit on the source PCell and the target PCell while performing the DAPS procedure. To prevent the UE from unnecessarily communicating with the target PCell in accordance with the DAPS power coordination configuration after the UE successfully performs the DAPS procedure, the UE releases the DAPS power coordination configuration. The UE can release the DAPS power coordination configuration (a) in response to successfully performing the DAPS procedure; (b) in response to receiving a DAPS release indicator from the RAN after successfully performing the DAPS procedure, or (c) in response to failing to successfully perform the DAPS procedure.

According to a first aspect of the present invention, there is provided a method as set out in claim <NUM>.

According to a second aspect of the present invention, there is provided a method as set out in claim <NUM>.

According to a third aspect of the present invention, there is provided a UE as set out in claim <NUM>.

According to a fourth aspect of the present invention, there is provided a base station as set out in claim <NUM>.

<FIG> depicts an example wireless communication system <NUM> that can implement configuration handling techniques of this disclosure, such as when performing DAPS handover, DAPS PSCell change, or RRC re-establishment procedures. The wireless communication system <NUM> includes a UE <NUM>, as well as RAN <NUM> (e.g., base stations <NUM>, 106A, 106B) that are connected to a core network (CN) <NUM>. The base stations <NUM>, 106A, 106B can be any suitable type, or types, of base stations, such as an evolved node B (eNB), a next-generation eNB (ng-eNB), or a <NUM> Node B (gNB), for example. As a more specific example, the base station <NUM> can be an eNB or a gNB, and the base stations 106A and 106B can be gNBs.

The base station <NUM> supports a cell <NUM>, the base station 106A supports a cell 126A, and the base station 106B supports a cell 126B. The cell <NUM> partially overlaps with both of cells 126A and 126B, such that the UE <NUM> can be in range to communicate with base station <NUM> while simultaneously being in range to communicate with base station 106A or 106B (or in range to detect or measure the signal from both base stations 106A or 106B, etc.). The overlap can make it possible for the UE <NUM> to hand over between cells (e.g., from cell <NUM> to cell 126A or 126B) or base stations (e.g., from base station <NUM> to base station 106A or base station 106B) before the UE <NUM> experiences radio link failure, for example. Moreover, the overlap allows the various dual connectivity (DC) scenarios discussed below. For example, the UE <NUM> can communicate in DC with the base station <NUM> (operating as an MN) and the base station 106A (operating as an SN) and, upon completing a handover, can communicate with the base station 106B (operating as an MN). As another example, the UE <NUM> can communicate in DC with the base station <NUM> (operating as an MN) and the base station 106A (operating as an SN) and, upon completing an SN change, can communicate with the base station <NUM> (operating as an MN) and the base station 106B (operating as an SN).

More particularly, when the UE <NUM> is in DC with the base station <NUM> and the base station 106A, the base station <NUM> operates as a master eNB (MeNB), a master ng-eNB (Mng-eNB), or a master gNB (MgNB), and the base station 106A operates as a secondary gNB (SgNB) or a secondary ng-eNB (Sng-eNB). In implementations and scenarios where the UE <NUM> is in SC with the base station <NUM> but is capable of operating in DC, the base station <NUM> operates as an MeNB, an Mng-eNB, or an MgNB, and the base station 106A operates as a candidate SgNB (C-SgNB) or a candidate Sng-eNB (C-Sng-eNB). Although various scenarios are described below in which the base station <NUM> operates as an MN and the base station 106A (or 106B) operates as an SN or T-SN, any of the base stations <NUM>, 106A, 106B generally can operate as an MN, an SN or a T-SN in different scenarios. Thus, in some implementations, the base station <NUM>, the base station 106A, and the base station 106B can implement similar sets of functions and each support MN, SN, and T-SN operations.

In operation, the UE <NUM> can use a radio bearer (e.g., a DRB or an SRB) that at different times terminates at an MN (e.g., the base station104) or an SN (e.g., the base station 106A). For example, after handover to the base station 106B, the UE <NUM> can use a radio bearer (e.g., a DRB or an SRB) that at different times terminates at the base station 106B. The UE <NUM> can apply one or more security keys when communicating on the radio bearer, in the uplink (from the UE <NUM> to a base station) and/or downlink (from a base station to the UE <NUM>) direction.

The base station <NUM> includes processing hardware <NUM>, which can include one or more general-purpose processors (e.g., central processing units (CPUs)) and a computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processor(s), and/or special-purpose processing units. The processing hardware <NUM> in the example implementation in <FIG> includes a base station RRC controller <NUM> that is configured to manage or control RRC configurations and RRC procedures. For example, the base station RRC controller <NUM> can be configured to support RRC messaging associated with DAPS handover and DAPS PSCell change procedures, re-establishment procedures, resume procedures, and/or to support the necessary operations when the base station <NUM> operates as an MN, as discussed below.

The base station 106A includes processing hardware <NUM>, which can include one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions executable on the general-purpose processor(s), and/or special-purpose processing units. The processing hardware <NUM> in the example implementation of <FIG> includes a base station RRC controller <NUM> that is configured to manage or control RRC configurations and RRC procedures. For example, the base station RRC controller <NUM> can be configured to support RRC messaging associated with DAPS handover and DAPS PSCell change procedures, re-establishment procedures, resume procedures, and/or to support the necessary operations when the base station 106A operates as an SN or target SN (T-SN), as discussed below. While not shown in <FIG>, the base station 106B can include processing hardware similar to the processing hardware <NUM> of the base station 106A.

The UE <NUM> includes processing hardware <NUM>, which can include one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions executable on the general-purpose processor(s), and/or special-purpose processing units. The processing hardware <NUM> in the example implementation of <FIG> includes a UE RRC controller <NUM> that is configured to manage or control RRC configurations RRC procedures. For example, the UE RRC controller <NUM> can be configured to support RRC messaging associated with DAPS handover and DAPS PSCell change procedures and/or re-establishment procedures, in accordance with any of the implementations discussed below.

The CN <NUM> can be an evolved packet core (EPC) <NUM> or a fifth-generation core (5GC) <NUM>, both of which are depicted in <FIG>. The base station <NUM> can be an eNB supporting an S1 interface for communicating with the EPC <NUM>, an ng-eNB supporting an NG interface for communicating with the 5GC <NUM>, or a gNB that supports the NR radio interface as well as an NG interface for communicating with the 5GC <NUM>. The base stations 106A, 106B can each be an EN-DC gNB (en-gNB) with an S1 interface to the EPC <NUM>, an en-gNB that does not connect to the EPC <NUM>, a gNB that supports the NR radio interface and an NG interface to the 5GC <NUM>, or a ng-eNB that supports an EUTRA radio interface and an NG interface to the 5GC <NUM>. To directly exchange messages with each other during the scenarios discussed below, the base stations <NUM>, 106A, and 106B can support an X2 or Xn interface.

Among other components, the EPC <NUM> can include a Serving Gateway (S-GW) <NUM> and a Mobility Management Entity (MME) <NUM>. The S-GW <NUM> is generally configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME <NUM> is configured to manage authentication, registration, paging, and other related functions. The 5GC <NUM> includes a User Plane Function (UPF) <NUM> and an Access and Mobility Management (AMF) <NUM>, and/or Session Management Function (SMF) <NUM>. The UPF <NUM> is generally configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF <NUM> is configured to manage authentication, registration, paging, and other related functions, and the SMF <NUM> is configured to manage PDU sessions.

Generally, the wireless communication network <NUM> can include any suitable number of base stations supporting NR cells and/or EUTRA cells. For example, base station <NUM> and base station 106A can also support cells <NUM> and <NUM>, respectively. More particularly, the EPC <NUM> or the 5GC <NUM> can be connected to any suitable number of base stations supporting NR cells and/or EUTRA cells. Although the examples below refer specifically to specific CN types (EPC, 5GC) and RAT types (<NUM> NR and EUTRA), in general the techniques of this disclosure can also apply to other suitable radio access and/or core network technologies such as sixth generation (<NUM>) radio access and/or <NUM> core network or <NUM> NR-<NUM> DC, for example.

As indicated above, the wireless communication system <NUM> can support various procedures (e.g., DAPS handover, DAPS PSCell change, re-establishment, etc.) and modes of operation (e.g., SC or DC). Example operation of various procedures that can be implemented in the wireless communication system <NUM> will now be described.

In some implementations, the wireless communication system <NUM> supports a legacy handover preparation procedure (i.e., a non-DAPS handover preparation procedure). In one scenario, for example, the base station <NUM> can perform a non-DAPS handover preparation procedure to configure the UE <NUM> to handover from a cell <NUM> of the base station <NUM> to a cell 126A of the base station 106A. In this scenario, the base station <NUM> and the base station 106A operate as a source base station (S-BS) or a source MN (S-MN), and a target base station (T-BS) or a target MN (T-MN), respectively. In the non-DAPS handover preparation procedure, the base station <NUM> sends a Handover Request message to the base station 106A. In response to the Handover Request message, the base station 106A includes configuration parameters configuring radio resources for the UE <NUM> in a handover command message, includes the handover command message in a Handover Request Acknowledge message, and sends the Handover Request Acknowledge message to the base station <NUM>. In turn, the base station <NUM> transmits the handover command message to the UE <NUM> and subsequently discontinues (or stops) transmitting data to or receiving data from the UE <NUM>.

Upon receiving the handover command message, the UE <NUM> hands over to the base station 106A via cell 126A and communicates with the base station 106A by using the configuration parameters in the handover command message. Particularly, in response to the handover command message, the UE <NUM> disconnects from the cell <NUM> (or the base station <NUM>), performs a random access procedure with the base station 106A via the cell 126A, and transmits a handover complete message to the base station 106A via the cell 126A.

In some implementations, the wireless communication system <NUM> supports a DAPS handover preparation procedure. In one scenario for example, the base station <NUM> can perform a DAPS handover preparation procedure to configure the UE <NUM> to hand over from a cell <NUM> of the base station <NUM> to a cell 126B of the base station 106B. In this scenario, the base station <NUM> and the base station 106B operate as an S-BS or an S-MN, and a T-BS or a T-MN, respectively. In the DAPS handover preparation procedure, the base station <NUM> sends a Handover Request message to the base station 106B. In some implementations, the base station <NUM> can explicitly request DAPS handover in the Handover Request message, e.g., by including a DAPS indicator in the Handover Request message. In response to the Handover Request message, and to accept the request for DAPS handover, the base station 106B includes configuration parameters configuring radio resources for the UE <NUM> in a handover command, includes the handover command message in a Handover Request Acknowledge message, and sends the Handover Request Acknowledge message to the base station <NUM>. In some implementations, the base station 106B can indicate DAPS handover in the handover command message, e.g., by including DAPS configuration(s) or a DAPS indicator in the handover command message, or can include an indicator in the Handover Request Acknowledge message. In turn, the base station <NUM> transmits the handover command message to the UE <NUM>.

Upon receiving the handover command message, the UE <NUM> performs the DAPS handover procedure to hand over to the base station 106B via cell 126B and communicates with the base station 106B by using the configuration parameters in the handover command message. Particularly, in response to the handover command message, whereas in the non-DAPS handover procedure the UE <NUM> disconnects from the cell <NUM> (or the base station <NUM>), the UE <NUM> in the DAPS handover procedure maintains the connection to the base station <NUM> via cell <NUM>, performs a random access procedure with the base station 106B via cell 126B, and transmits a handover complete message to the base station 106B via cell 126B.

In maintaining the connection to the base station <NUM> via cell <NUM> in the DAPS handover procedure, the UE <NUM> effectively has two links, i.e., a source MCG link with the base station <NUM> and a target MCG link with the base station 106B. The UE <NUM> can continue receiving data (i.e., downlink data) from the base station <NUM> until the UE <NUM> receives an indication from the base station 106B to release the source MCG link with the base station <NUM>. The UE <NUM> can continue transmitting data (e.g., new uplink data transmission or retransmission of PDCP SDUs) to the base station <NUM> until the UE <NUM> either successfully completes the random access procedure with the base station 106B or receives the indication from the base station 106B to release the MCG link with the base station <NUM>.

In some implementations, in the handover preparation procedure scenarios above, the wireless communication system <NUM> supports DC operation. In one scenario, for example, after the UE <NUM> connects to the base station <NUM>, and the base station <NUM> performs an SN addition procedure to add the base station 106A as an SN, thereby configuring the UE <NUM> to operate in DC with the base stations <NUM> and 106A. At this point, the base stations <NUM> and 106A operate as an MN and an SN, respectively. Later on, the MN <NUM> can initiate the non-DAPS or DAPS handover preparation procedures to hand over the UE <NUM> to the T-MN 106B.

In some implementations, the wireless communication system <NUM> supports a legacy PSCell change preparation procedure (i.e., a non-DAPS PSCell change preparation procedure). In one scenario, for example, the UE <NUM> is initially in DC with the MN <NUM> (e.g., via PCell <NUM>) and the SN 106A (via a PSCell <NUM>). The SN 106A can provide a configuration for the T-PSCell 126A, for the UE <NUM>. The UE <NUM> stops communicating with the SN 106A via PSCell <NUM> and attempts to connect to the T-PSCell 126A after receiving the configuration for the T-PSCell 126A. In another scenario, for example, while the UE <NUM> is in DC with the MN <NUM> and the SN 106A, the MN <NUM> determines to change the SN of the UE <NUM> from the base station 106A (which may be referred to as the source SN or S-SN) to the base station 106B (which may be referred to as the target SN or T-SN) as part of the non-DAPS PSCell change procedure. The UE <NUM> stops communicating with the S-SN 106A via PSCell <NUM> and attempts to connect to the T-SN 106B via T-PSCell 126B after receiving the configuration for the T-PSCell 126B.

In some implementations, the wireless communication system <NUM> supports DAPS PSCell change. In one scenario, for example, the UE <NUM> is initially in DC with the MN <NUM> (e.g., via PCell <NUM>) and the SN 106A (via a PSCell <NUM>). The SN 106A can provide a configuration for the T-PSCell 126A, for the UE <NUM>. The UE <NUM> continues communicating with the SN 106A via PSCell <NUM> while attempting to connect to the T-PSCell 126A after receiving the configuration for the T-PSCell 126A. After the T-PSCell 126A begins to operate as the PSCell 126A for the UE <NUM>, the UE <NUM> stops communicating with the SN 106A via PSCell <NUM>. In another scenario, for example, while the UE <NUM> is in DC with the MN <NUM> and the SN 106A, the MN <NUM> determines to change the SN of the UE <NUM> from the base station 106A (which may be referred to as the source SN or S-SN) to the base station 106B (which may be referred to as the target SN or T-SN) as part of the DAPS PSCell change procedure. The UE <NUM> continues communicating with the S-SN 106A via PSCell <NUM> while attempting to connect to the T-SN 106B via T-PSCell 126B after receiving the configuration for the T-PSCell 126B. After the T-PSCell 126B begins to operate as the PSCell 126B for the UE <NUM>, the UE <NUM> stops communicating with the S-SN 106A via PSCell <NUM>.

In different configurations or scenarios of the wireless communication system <NUM>, the base station <NUM> can operate as an MeNB, an Mng-eNB, or an MgNB, the base station 106B can operate as an MeNB, an Mng-eNB, an MgNB, an SgNB, or an Sng-eNB, and the base station 106A can operate as an SgNB or an Sng-eNB. The UE <NUM> can communicate with the base station <NUM> and the base station 106A or 106B via the same radio access technology (RAT), such as EUTRA or NR, or via different RATs.

When the base station <NUM> is an MeNB and the base station 106A is an SgNB, the UE <NUM> can be in EUTRA-NR DC (EN-DC) with the MeNB <NUM> and the SgNB 106A. When the base station <NUM> is an Mng-eNB and the base station 106A is an SgNB, the UE <NUM> can be in next generation (NG) EUTRA-NR DC (NGEN-DC) with the Mng-eNB <NUM> and the SgNB 106A. When the base station <NUM> is an MgNB and the base station 106A is an SgNB, the UE <NUM> can be in NR-NR DC (NR-DC) with the MgNB <NUM> and the SgNB 106A. When the base station <NUM> is an MgNB and the base station 106A is an Sng-eNB, the UE <NUM> can be in NR-EUTRA DC (NE-DC) with the MgNB <NUM> and the Sng-eNB 106A.

<FIG> depicts an example, distributed implementation of any one or more of the base stations <NUM>, 106A, 106B. In this implementation, the base station <NUM>, 106A, or 106B includes a centralized unit (CU) <NUM> and one or more distributed units (DUs) <NUM>. The CU <NUM> includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions executable on the general-purpose processor(s), and/or special-purpose processing units. For example, the CU <NUM> can include the processing hardware <NUM> or <NUM> of <FIG>. The processing hardware can include a base station RRC controller (e.g., RRC controller <NUM>) configured to manage or control one or more RRC configurations and/or RRC procedures when the base station (e.g., base station 106A) operates as an SN.

Each of the DUs <NUM> also includes processing hardware that can include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and/or special-purpose processing units. For example, the processing hardware can include a medium access control (MAC) controller configured to manage or control one or more MAC operations or procedures (e.g., a random access procedure), and a radio link control (RLC) controller configured to manage or control one or more RLC operations or procedures when the base station (e.g., base station 106A) operates as an MN or an SN. The process hardware can also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

<FIG> illustrates, in a simplified manner, an example dual active protocol stack (DAPS) <NUM> according to which the UE <NUM> can communicate with an eNB/ng-eNB or a gNB (e.g., one or more of the base stations <NUM>, 106A, 106B).

In the example stack <NUM>, a physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to the EUTRA PDCP sublayer <NUM> and, in some cases, to the NR PDCP sublayer <NUM>. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides RLC channels to the NR PDCP sublayer <NUM>. The UE <NUM>, in some implementations, supports both the EUTRA and the NR stack as shown in <FIG>, to support handover between EUTRA and NR base stations and/or to support DC over EUTRA and NR interfaces. Further, as illustrated in <FIG>, the UE <NUM> can support layering of NR PDCP <NUM> over EUTRA RLC 206A.

The EUTRA PDCP sublayer <NUM> and the NR PDCP sublayer <NUM> receive packets (e.g., from an Internet Protocol (IP) layer, layered directly or indirectly over the PDCP layer <NUM> or <NUM>) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206A or 206B) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as "packets.

On a control plane, the EUTRA PDCP sublayer <NUM> and the NR PDCP sublayer <NUM> can provide SRBs to exchange RRC messages, for example. On a user plane, the EUTRA PDCP sublayer <NUM> and the NR PDCP sublayer <NUM> can provide DRBs to support data exchange.

In scenarios where the UE <NUM> operates in EUTRA/NR DC (EN-DC), with the base station <NUM> operating as an MeNB and the base station 106A operating as an SgNB, the wireless communication system <NUM> can provide the UE <NUM> with an MN-terminated bearer that uses EUTRA PDCP sublayer <NUM>, or an MN-terminated bearer that uses NR PDCP sublayer <NUM>. The wireless communication system <NUM> in various scenarios can also provide the UE <NUM> with an SN-terminated bearer, which uses only the NR PDCP sublayer <NUM>. The MN-terminated bearer can be an MCG bearer or a split bearer. The SN-terminated bearer can be an SCG bearer or a split bearer. The MN-terminated bearer can be an SRB (e.g., SRB1 or SRB2) or a DRB. The SN-terminated bearer can be an SRB or a DRB.

<FIG> and <FIG> correspond to DAPS handover scenarios in which a base station initiates a DAPS handover procedure for a UE. <FIG> and <FIG> correspond to DAPS PSCell change scenarios in which a base station initiates a DAPS PSCell change procedure for a UE. While <FIG>, <FIG>, <FIG>, and <FIG> and the accompanying descriptions refer specifically to the UE <NUM> and base stations <NUM>, 106A, and/or 106B of <FIG>, it is understood that the following techniques may be implemented by other components and/or in systems other than the wireless communication system <NUM> of <FIG>.

Referring first to <FIG>, according to a DAPS handover scenario 300A, the base station <NUM> operates as a source MN (S-MN) for the UE <NUM>, and the base station 106B operates as a target MN (T-MN) for the UE <NUM>. The base station <NUM> and base station 106B can be referred to as the MNs both in SC and DC scenarios.

Initially, the UE <NUM> communicates 302A data (e.g., uplink (UL) data PDUs and/or downlink (DL) data PDUs) with the S-MN <NUM> by using an S-MN configuration. In some scenarios, the UE <NUM> communicates 302A data in SC with the S-MN <NUM>, or communicates 302A data in DC with the S-MN <NUM> (operating as an MN) and an SN (e.g., the base station 106A) not shown in <FIG>.

Later in time, the S-MN <NUM> determines 304A to initiate DAPS handover for the T-MN 106B and the UE <NUM> to communicate, e.g., blindly or in response to detecting a suitable event. For example, the determination in event 304A can occur in response to the S-MN <NUM> receiving one or more measurement report results from the UE <NUM> that are above (or below) one or more predetermined thresholds, or calculating a filtered result (from the measurement result(s)) that is above (or below) a predetermined threshold. In another example, the suitable event can be that the UE <NUM> is moving toward the T-MN 106B. In yet another example, the suitable event can be one or more measurement results, generated or obtained by the S-MN <NUM> based on measurements of signals received from the UE <NUM>, being above (or below) one or more predetermined thresholds.

After determining 304A to initiate DAPS handover, the S-MN <NUM> sends 312A a Handover Request message to the T-MN 106B. In some implementations, the Handover Request message includes the S-MN configuration. In response, the T-MN 106B generates 314A a handover command message for DAPS handover that includes a T-MN configuration including a DAPS power coordination configuration (e.g., a DAPS-PowerCoordinationInfo-r16 IE or DAPS-Configuration-r16 IE), includes the handover command message in a Handover Request Acknowledge message, and sends 316A the Handover Request Acknowledge message to the S-MN <NUM>. In turn, the S-MN <NUM> transmits 318A the handover command message to the UE <NUM>. The handover command message also includes one or more random access configurations needed by the UE <NUM> to handover to the T-MN 106B, and in some implementations, includes additional fields or IEs, such as a mobility field or IE for a PCell of the T-MN 106B (e.g., mobilityControlInfo field, a reconfigurationWithSync field, MobilityControlInfo IE, a ReconfigurationWithSync IE), which can include some or all of the random access configurations. In some implementations the T-MN 106B can include the DAPS power coordination configuration in the mobility field or IE.

In some implementations, the T-MN 106B can include, in the handover command message, DAPS configuration(s) (e.g., daps-Config field(s) or a daps-HO field(s)) indicating particular DRB(s) as DAPS bearer(s). The DAPS configuration(s) enables the UE <NUM> to use a DAPS (e.g., DAPS <NUM>) for the DAPS bearer(s) to communicate with the S-MN <NUM> (using configurations in the S-MN configuration) and T-MN 106B (using configurations in the T-MN configuration during and after a successful DAPS handover).

As such, in response to receiving 318A the handover command message, the UE <NUM> (e.g., PHY <NUM>) applies (i.e., uses) 352A the DAPS power coordination configuration, and continues 320A communicating with the S-MN <NUM> using the S-MN configuration while the UE <NUM> attempts to handover to the T-MN 106B in accordance with the handover command message. In some implementations, the RRC controller <NUM> can send DAPS power coordination configuration parameters in the DAPS power coordination configuration to the PHY <NUM>, which in turn applies the DAPS power coordination configuration parameters.

In attempting to perform the DAPS handover, the UE <NUM> initiates 322A a random access procedure with the T-MN 106B via a target cell (e.g., PCell 126B) covered by the T-MN 106B, e.g., by using one or more random access configurations in the handover command message received from the S-MN <NUM> at event 318A. After gaining access to a channel, the UE <NUM> transmits 324A a handover complete message to the T-MN 106B via the target cell during or after successfully completing the random access procedure. After the T-MN 106B identifies the UE <NUM> during the random access procedure (i.e., the UE <NUM> succeeds in the random access contention resolution) or receives 324A the handover complete message, the UE <NUM> communicates 326A control signals and data (e.g., UL data PDUs or DL data PDUs) with the T-MN 106B via the target cell by using configurations indicated in the handover command message. The T-MN 106B sends 328A a Handover Success message to the S-MN <NUM>. After receiving the Handover Success message, the S-MN <NUM> stops 330A communicating with the UE <NUM>.

The DAPS configuration(s) and/or the DAPS power coordination configuration enable the UE <NUM> to continue communicating with the S-MN <NUM> while simultaneously communicating with the T-MN 106B. Because the UE <NUM> no longer needs to use the DAPS to continue communicating with the S-MN <NUM> after successfully performing the DAPS handover, the UE <NUM> can stop 354A applying the DAPS power coordination configuration and release the DAPS power coordination configuration. In this way, the UE <NUM> will not unnecessarily restrict its maximum uplink power according to the DAPS power coordination configuration when communicating with the T-MN 106B, thereby decreasing the chances of radio link failure with the T-MN 106B. In some implementations, the T-MN 106B can send 332A an RRC reconfiguration message that includes a DAPS release indicator to the UE <NUM>, e.g., via the target cell (e.g., PCell 126B), before, after, or simultaneously while transmitting 328A the Handover Success message. In response to the RRC reconfiguration message or the DAPS release indicator, the UE <NUM> can stop 354A applying the DAPS power coordination configuration and release the DAPS power coordination configuration. In some implementations, the UE <NUM> can stop 354A applying the DAPS power coordination configuration and release the DAPS power coordination configuration after successfully performing 322A the random access procedure. In some implementations, the RRC controller <NUM> can send an indication to the PHY <NUM> of the UE <NUM>, causing the PHY <NUM> to stop applying 354A the DAPS power coordination configuration.

In some implementations, the T-MN 106B can also release 356A the DAPS power coordination configuration, because the UE <NUM> no longer needs to use the DAPS power coordination configuration and/or the UE <NUM> released 354A the DAPS power coordination configuration. That is, the T-MN 106B can release the DAPS power coordination configuration after including the DAPS power coordination configuration in the handover command message in event 316A.

Subsequent to event 354A, the UE <NUM> can transmit 334A an RRC reconfiguration complete message to the T-MN 106B and stop 336A communicating (i.e., UL and/or DL communication) with the S-MN <NUM>. In some implementations, in response to the DAPS release indicator, a RF chip, receiver, or a transceiver of the UE <NUM> used to communicate with the S-MN <NUM> during the DAPS handover can enter into low power consumption mode, sleep mode, or be turned off entirely if the DAPS handover is an inter-frequency DAPS handover.

In some implementations, the DAPS power coordination configuration includes one or more of the following DAPS power coordination configuration parameters: the maximum total transmission power (or value thereof) that the UE <NUM> can use for uplink communication with the S-MN <NUM> during DAPS handover (interchangeably referred to as "CP1"), the maximum total transmission power (or value thereof) that the UE <NUM> can use for uplink communication with the T-MN 106B during DAPS handover (interchangeably referred to as "CP2"), and/or an uplink power sharing mode that the UE <NUM> uses during DAPS handover (interchangeably referred to as "CP3"). The DAPS power coordination configuration parameters can be included in fields or IEs of the DAPS power coordination configuration, in some implementations. For ease of readability throughout this disclosure, a "configuration" (e.g., DAPS power coordination configuration) refers to one or more parameters included in the configuration. Further, "parameter" or "parameters" as described herein also refers to value(s) corresponding to the parameter(s).

After the UE <NUM> (e.g., PHY <NUM>) applies the DAPS power coordination configuration during the DAPS handover, the UE <NUM> (e.g., PHY <NUM>) can determine (or manage or coordinate) its uplink transmission power for transmissions to the S-MN <NUM> and its uplink transmission power for transmissions to the T-MN 106B according to the DAPS power coordination configuration, e.g., pursuant to 3GPP specification <NUM> v16. <NUM> or <NUM> v16. In some implementations, if the uplink power sharing mode as designated in CP3 is a first mode (e.g., semi-static mode <NUM>), the UE <NUM> manages its uplink transmission power to not exceed CP1 while transmitting 320A to the S-MN <NUM>, and to not exceed CP2 while transmitting 326A to the T-MN 106B. In other implementations, if the uplink power sharing mode is a second mode (e.g., semi-static mode <NUM> or dynamic mode), and a first uplink transmission to the S-MN <NUM> partially or completely overlaps with a second uplink transmission to the T-MN 106B, the UE <NUM> manages uplink transmission power of the first uplink transmission and the second uplink transmission to not exceed CP1 and CP2, respectively. If the uplink power sharing mode is the second mode and the first uplink transmission to the S-MN <NUM> does not overlap with the second uplink transmission to the T-MN 106B, the UE <NUM> manages uplink transmission power of the first uplink transmission and the second uplink transmission to not exceed respective maximum total transmission power values other than those included in the DAPS power coordination configuration.

In some implementations, the S-MN <NUM> and T-MN 106B can provide these respective maximum total transmission power values to the UE <NUM> in respective non-DAPS configuration(s). The S-MN <NUM> can send non-DAPS configuration(s) to the UE <NUM> in broadcast message(s) (e.g., system information block(s) and/or a dedicated message (e.g., RRC reconfiguration message)), and the T-MN 106B can send non-DAPS configuration(s) to the UE <NUM> in the handover command message, or broadcast message(s) (e.g., system information block(s)) on PCell 126B), in some implementations.

In some implementations, the T-MN 106B receives a configuration restriction for the DAPS handover from the S-MN <NUM> in the Handover Request message. The T-MN 106B can generate the DAPS power coordination configuration according to the configuration restriction. In one implementation, the S-MN <NUM> can generate and include preferred power coordination configuration parameters in the configuration restriction, and in turn the T-MN 106B can include such preferred parameters in the DAPS power coordination configuration. In one implementation, the S-MN <NUM> can determine the preferred parameters based on the UE capability of the UE <NUM>. For example, the UE capability can indicate or include a UE power class and/or DAPS power sharing mode(s) supported by the UE <NUM>. If the UE capability includes or otherwise indicates supported uplink power sharing mode(s), the S-MN <NUM> can set the preferred uplink sharing mode to one of the supported uplink power sharing mode(s). If the UE <NUM> is configured to implement all uplink sharing modes supported by the RAN <NUM>, the S-MN <NUM> can select a particular preferred uplink sharing mode according to one or more of the following preferred power coordination configuration parameters: UE power class (interchangeably referred to as "PCP1") and/or regulation requirements (interchangeably referred to as "PCP2").

Similarly, in another implementation, the T-MN 106B can determine some or all of the DAPS power coordination configuration parameters in the DAPS power coordination configuration based on the preferred power coordination configuration parameters provided by the S-MN <NUM>, and/or the UE capability of the UE <NUM>. If the UE capability includes or otherwise indicates supported uplink power sharing mode(s), the T-MN 106B can set the uplink sharing mode to one of the supported uplink power sharing mode(s) or the preferred uplink sharing mode provided by the S-MN <NUM>. If the UE <NUM> is configured to implement all uplink sharing modes supported by the RAN <NUM>, the T-MN 106B can select a particular uplink sharing mode according to PCP1, PCP2, and/or the same preferred power coordination configuration parameters provided by the S-MN <NUM>.

In some implementations, after successfully completing 322A the random access procedure, the UE <NUM> stops transmitting and retransmitting UL data PDUs and/or control signals on physical uplink control channel(s) (PUCCH(s)) to the S-MN <NUM>. In other implementations, the UE <NUM> stops transmitting new UL data PDUs to the S-MN <NUM> but continues to retransmit UL data PDU(s) to the S-MN <NUM> if requested by the S-MN <NUM> after successfully completing 322A the random access procedure, until event 336A occurs. In such implementations, the UE <NUM> can continue DL communicating (i.e., receiving control signals, reference signals, DL PDUs, etc.) with the S-MN <NUM> and/or transmit control signals (e.g., HARQ acknowledgement, HARQ negative acknowledgement and/or channel state information) on PUCCH(s) to the S-MN <NUM> until event 332A occurs or a DAPS release timer at the UE <NUM> expires. The T-MN 106B can configure the timer value for the DAPS release timer in the handover command message in event 314A or the RRC reconfiguration message in event 332A, in some implementations. Upon receiving 318A the handover command message or receiving 332A the RRC reconfiguration message, the UE <NUM> starts the DAPS release timer. When the DAPS release timer expires, the UE <NUM> stops 336A communicating with the S-MN <NUM>. In other implementations, the UE <NUM> uses a predetermined timer value if the T-MN 106B does not include the timer value in the handover command message or the RRC reconfiguration message. The T-MN 106B can include the predetermined timer value in the Handover Success message, which can be the same timer value as that in the RRC reconfiguration message, or a larger value than that in the handover command message.

In some implementations, the T-MN configuration includes multiple configuration parameters (e.g., corresponding to physical layer, MAC layer, and/or RLC layer configurations) to configure radio resources. The UE <NUM> can use these multiple configuration parameters to communicate with the T-MN 106B via target PCell 126B. The multiple configuration parameters can configure zero, one, or more radio bearers, including SRB(s) (e.g., SRB1, SRB2 and/or SRB4) and/or DRB(s). For instance, the UE <NUM> can exchange RRC messages with the T-MN 106B via the SRB(s) (i.e., SRB(s) for the target PCell), and communicate data with the T-MN 106B via the DRB(s).

In some implementations, the MN configuration (i.e., the S-MN configuration or T-MN configuration) can include a CellGroupConfig IE. The MN configuration can be an RRCReconfiguration message, RRCReconfiguration-IEs, or the CellGroupConfig IE conforming to 3GPP TS <NUM>, or an RRCConnectionReconfiguration message or RRCConnectionReconfiguration-IEs conforming to 3GPP TS <NUM>. In some implementations, the MN configuration can include configurations in the CellGroupConfig IE, RRCReconfiguration-IEs, or RRCConnectionReconfiguration-IEs.

In some implementations, the S-MN <NUM> consists of CU <NUM> and one or more DUs <NUM> as shown in <FIG>. The DU(s) <NUM> can generate the S-MN configuration or at least a portion of the S-MN configuration, and send the S-MN configuration (or portion) to the CU <NUM>. The CU <NUM> can generate the remainder of the S-MN configuration if the DU <NUM> only generated a portion of the S-MN configuration. The DU(s) <NUM> can communicate with the UE <NUM> via the portion of the S-MN configuration, and the CU <NUM> can communicate with the UE <NUM> via the remainder of the S-MN configuration, in one implementation. For example, the S-MN configuration (or portion) generated by the DU <NUM> can include one or more random access configurations, a physical downlink control channel (PDCCH) configuration, a PUCCH configuration, etc. The remainder of the S-MN configuration generated by the CU <NUM> can include an SRB configuration, a DRB configuration, a security configuration, and/or a measurement configuration. In other implementations, the DU <NUM> can include a cell group configuration (e.g., CellGroupConfig IE) in the S-MN configuration, and the CU <NUM> can include a radio bearer configuration (RadioBearerConfig IE) in the S-MN configuration.

Similarly, in some implementations, the T-MN 106B consists of CU <NUM> and one or more DUs <NUM> as shown in <FIG>. The UE <NUM> can perform 322A the random access procedure with at least one of the DU(s) <NUM>. The DU <NUM> generates some configurations (e.g., one or more random access configurations, a PDCCH configuration, a PUCCH configuration) and sends the configurations to the CU <NUM>. The CU <NUM> can include other configurations (e.g., an SRB configuration, a DRB configuration, a security configuration, and/or a measurement configuration) in the handover command message. In other implementations, the DU <NUM> can generate a cell group configuration (e.g., CellGroupConfig IE) and send the cell group configuration to the CU <NUM>, which in turn can include a radio bearer configuration (e.g., RadioBearerConfig IE) and the cell group configuration in the handover command message.

In some implementations, if the S-MN <NUM> is a gNB, the handover command message can be an RRCReconfiguration message, the handover complete message can be an RRCReconfigurationComplete message, and the RRC reconfiguration message and the RRC reconfiguration complete message can be an RRCReconfiguration message and an RRCReconfigurationComplete message, respectively.

In some implementations, if the S-MN <NUM> is an eNB or an ng-eNB, the handover command message can be an RRCConnectionReconfiguration message, the handover complete message can be an RRCConnectionReconfigurationComplete message, and the RRC reconfiguration message and the RRC reconfiguration complete message can be an RRCConnectionReconfiguration message and an RRCConnectionReconfigurationComplete message, respectively.

Turning now to <FIG>, according to a DAPS handover scenario 300B, the base station <NUM> operates as an S-MN for the UE <NUM>, and the base station 106B operates as a T-MN for the UE <NUM>, similar to the DAPS handover scenario 300A of <FIG>. Whereas in <FIG> the UE <NUM> successfully performs a DAPS handover to the T-MN 106B prior to stopping and releasing the power coordination configuration, in <FIG> the UE <NUM> fails to successfully perform the DAPS handover.

Initially, the UE <NUM> communicates 302B data with the S-MN <NUM> by using an S-MN configuration, similar to event 302A. Later in time, the S-MN <NUM> determines 304B to initiate DAPS handover for the T-MN 106B and the UE <NUM> to communicate, similar to event 304A.

After determining 304B to initiate DAPS handover, the S-MN <NUM> sends 312B a Handover Request message to the T-MN 106B, the T-MN 106B generates 314B a handover command message for DAPS handover that includes a T-MN configuration including a DAPS power coordination configuration, the T-MN 106B sends 316B the handover command message in a Handover Request Acknowledge message to the S-MN <NUM>, and the S-MN <NUM> transmits 318B the handover command message to the UE <NUM>, similar to events 312A, 314A, 316A, and 318A, respectively.

In response to receiving 318B the handover command message, the UE <NUM> applies 352B the DAPS power coordination configuration, and continues 320B communicating with the S-MN <NUM> using the S-MN configuration while the UE <NUM> attempts to handover to the T-MN 106B in accordance with the handover command message, similar to events 352A and 320A, respectively.

After the UE <NUM> either applies 352B the DAPS power coordination configuration or continues 320B communicating with the S-MN <NUM>, the UE <NUM> determines 321B a DAPS handover failure, i.e., the UE <NUM> fails to perform DAPS handover to the T-MN 106B using a random access procedure similar to 322A, e.g., within a certain time duration. In response to the determination at event 321B, the UE <NUM> stops 354B applying the DAPS power coordination configuration and releases the DAPS power coordination configuration. In some implementations, the RRC controller <NUM> can send an indication to the PHY <NUM> of the UE <NUM>, causing the PHY <NUM> to stop applying the DAPS power coordination configuration. In some implementations, the UE <NUM> releases the T-MN configuration received in event 318B in response to the determination at event 321B.

If a radio link between the UE <NUM> and the S-MN <NUM> is available (i.e., no radio link failure occurs on the radio link between the UE <NUM> and the S-MN <NUM>), the UE <NUM> can transmit 342B to the S-MN <NUM>, e.g., via SRB1, a failure information message (e.g., FailureInformation) indicating the DAPS handover failure with respect to the T-MN 106B. The UE <NUM> can then perform 348B an RRC re-establishment procedure on cell 126B or another cell with the T-MN 106B, in some implementations. If the radio link between the UE <NUM> and the S-MN <NUM> is not available, the UE <NUM> does not transmit the failure information message to the S-MN <NUM>. To perform the RRC re-establishment procedure, the UE <NUM> transmits an RRC re-establishment request message to the T-MN 106B, which in turn transmits an RRC re-establishment message to the UE <NUM>. The UE <NUM> can transmit an RRC re-establishment complete message to the T-MN 106B in response to the RRC re-establishment message.

Because the UE <NUM> has stopped 354B applying the DAPS power coordination configuration and released the DAPS power coordination configuration, the UE <NUM> advantageously will not unnecessarily restrict its maximum uplink power according to the DAPS power coordination configuration (e.g., CP1 and/or CP2) when communicating with the S-MN <NUM>, such as when transmitting 342B the failure information message to the S-MNB <NUM>, and/or when communicating with the T-MN 106B, such as during or after performing 348B the RRC re-establishment procedure with the T-MN 106B.

In some implementations, the T-MN 106B can release 356B the DAPS power coordination configuration some time after generating or transmitting the handover command message to the S-MN <NUM>. In some implementations, the T-MN 106B can release the DAPS power coordination configuration if the UE <NUM> does not successfully handover to the T-MN 106B within a time duration. In other implementations, the T-MN 106B can release the DAPS power coordination configuration in response to the RRC re-establishment procedure.

In some implementations, the UE <NUM> can perform the RRC re-establishment procedure with the S-MN <NUM> via cell <NUM> or cell <NUM> instead of with the T-MN 106B. Thus, because the UE <NUM> has stopped 354B applying the DAPS power coordination configuration and released the DAPS power coordination configuration, the UE <NUM> is also not restricted by the DAPS power coordination configuration parameter CP1 during and after performing the RRC re-establishment procedure with the S-MN <NUM>.

In some implementations, if the T-MN <NUM> is a gNB, the RRC re-establishment request message, the RRC re-establishment message, and the RRC re-establishment complete message can be an RRCReestablishmentRequest message, an RRCReestablishment message, and an RRCReestablishmentComplete message, respectively. If the T-MN 106B is an eNB or an ng-eNB, the RRC re-establishment request message, the RRC re-establishment message, and the RRC re-establishment complete message can be an RRCConnectionReestablishmentRequest message, an RRCConnectionReestablishment message, and an RRCConnectionReestablishmentComplete message, respectively.

Although <FIG> and <FIG> depict the DAPS handover scenarios 300A and 300B occurring between two base stations (e.g., the base stations <NUM>, 106B) with respect to the UE <NUM>, in some implementations, the DAPS handover scenarios 300A and 300B can be carried out within a single base station (e.g., the S-MN <NUM>) with respect to the UE <NUM>. In such scenarios, messages exchanged between the S-MN <NUM> and T-MN 106B (e.g., events 312A, 312B, 316A, 316B, 328A) can be omitted, and the events performed or otherwise involving the T-MN 106B (e.g., events 314A, 314B, 322A, 324A, 326A, 332A, 356A, 356B, 334A, 348B) can be performed or otherwise involve the S-MN <NUM>.

Referring now to <FIG>, according to a DAPS PSCell change scenario 400A, the base station <NUM> operates as an MN for the UE <NUM>, the base station 106A operates as an S-SN for the UE <NUM>, and the base station 106B operates as a T-SN for the UE <NUM>.

Initially, the UE <NUM> in DC communicates 402A data with the MN <NUM> via PCell <NUM> by using an MN configuration, and with the S-SN 106A via PSCell 126A by using an S-SN configuration.

Later in time, the MN <NUM> determines 404A to initiate DAPS PSCell change involving an SN change (i.e., MN-initiated DAPS SN addition or change procedure) for the T-SN 106B and the UE <NUM> to communicate via a T-PSCell 126B, e.g., blindly or in response to detecting a suitable event, similar to those described with respect to <FIG>, or in response to an SN Change Required message received from the S-SN 106A.

In response to the determination at event 404A, the MN <NUM> sends 412A an SN Addition Request message to the T-SN 106B. In response, the T-SN 106B generates 414A a T-SN configuration for a DAPS PSCell change, and sends 416A the T-SN configuration in an SN Addition Request Acknowledge message to the MN <NUM>. In other implementations, in response to the determination at event 404A, the MN <NUM> can send an SN Release Request message (or alternatively, an SN Modification Request message) to the S-SN 106A, to request the S-SN 106A to perform DAPS PSCell change or to continue communicating with the UE <NUM>, respectively. The S-SN 106A can then send an SN Release Request Acknowledge message or an SN Modification Request Acknowledge message to the MN <NUM> in response to the SN Release Request message or SN Modification Request message, respectively. In other implementations, the MN <NUM> may not send the SN Release Request message (or alternatively, the SN Modification Request message) to the S-SN 106A, causing the S-SN 106A to continue communicating with the UE <NUM> as the S-SN 106A is unaware of the DAPS SN change and therefore behaves as usual. In yet other implementations, if the MN <NUM> made the determination at event 404A in response to the SN Change Required message, the MN <NUM> can send an SN Change Confirm message to the S-SN 106A, to request the S-SN 106A to perform DAPS PSCell change or to continue communicating with the UE <NUM>.

In response to receiving 416A the T-SN configuration from the T-SN 106B, the MN <NUM> generates a DAPS power coordination, and includes both the T-SN configuration and the DAPS power coordination configuration in an RRC container message, and transmits 417A the RRC container message to the UE <NUM>. In response to receiving 417A the DAPS power coordination configuration, the UE <NUM> applies 452A the DAPS power coordination configuration. In some implementations, the RRC controller <NUM> can send DAPS power coordination configuration parameters in the DAPS power coordination configuration to the PHY <NUM> of the UE <NUM>, which in turn applies the DAPS power coordination configuration parameters. In response to receiving 417A the RRC container message, the UE <NUM> also transmits 418A an RRC container response message including an RRC reconfiguration complete message to the MN <NUM>. In some implementations, the MN <NUM> can send 419A an SN Reconfiguration Complete message to the T-SN 106B in response to the RRC container response message. The events 404A, 412A, 414A, 416A, 417A, 452A, 418A, and 419A are collectively referred to in <FIG> as the DAPS PSCell change preparation procedure 460A.

In some implementations, rather than generating the DAPS power coordination configuration at event 417A, the MN <NUM> receives the DAPS power coordination configuration from the T-SN 106B in the SN Addition Request Acknowledge message. In one such implementation, the T-SN 106B can generate and include the DAPS power coordination configuration (e.g., a DAPS-PowerCoordinationInfo-r16 IE or DAPS-Configuration-r16 IE) in the T-SN configuration or in the SN Addition Request Acknowledge message. In other implementations, the S-SN 106A can generate and send the DAPS power coordination configuration to the MN <NUM> in the SN Change Required message or in an SN Modification Request Acknowledge message.

In some implementations, the T-SN 106B can send DAPS PSCell change configuration(s) (e.g., daps-Config field(s)) indicating particular DRB(s) are DAPS bearer(s) in the SN Addition Request Acknowledge message or in the T-SN configuration to the MN <NUM>, which in turn can include the DAPS PSCell change configuration(s) in the RRC container message. The DAPS PSCell change configuration enables the UE <NUM> to use a DAPS (e.g., DAPS <NUM>) for the DAPS bearer(s) to communicate with the S-SN 106A (using the S-SN configuration) and T-SN 106B (during and after a successful DAPS PSCell change). As such, in response to receiving 417A the RRC container message, the UE <NUM> and the S-SN 106A continue 420A communicating with each other (i.e., in DC with the MN <NUM>) by using the S-SN configuration while the UE <NUM> attempts to perform DAPS PSCell change to the T-SN 106B via T-PSCell 126B in accordance with the T-SN configuration.

In attempting to perform the DAPS PSCell change, the UE <NUM> initiates 422A a random access procedure with the T-SN 106B via T-PSCell 126B, e.g., by using one or more random access configurations in the T-SN configuration. After the T-SN 106B identifies the UE <NUM> during the random access procedure (e.g., the UE <NUM> succeeds the contention resolution), the UE <NUM> communicates 426A in DC with the MN <NUM> via PCell <NUM> and T-SN 106B via T-PSCell 126B by using configurations in the T-SN configuration, while continuing to communicate with the S-SN 106A via PSCell 126A.

The MN <NUM> can send 428A a UE Context Release message to the S-SN 106A after receiving 418A the RRC container response message. The S-SN 106A stops 430A communicating with the UE <NUM> in response to or after receiving the UE Context Release message. Alternatively, the S-SN 106A stops 430A communicating with the UE <NUM> if the S-SN 106A does not receive DL data packets from the CN <NUM> (e.g., S-GW <NUM> or UPF <NUM>).

The DAPS PSCell change configuration(s) and/or the DAPS power coordination configuration enable the UE <NUM> to continue communicating with the S-SN 106A while simultaneously communicating with the T-SN 106B. As the UE <NUM> no longer needs to use the DAPS to continue communicating with the S-SN 106A after successfully performing the DAPS PSCell change, the UE <NUM> can stop 454A applying the DAPS power coordination configuration and release the DAPS power coordination configuration. In this way, the UE <NUM> will not unnecessarily restrict its maximum uplink power according to the DAPS power coordination configuration when communicating with the T-SN 106B, thereby reducing the risk of radio link failure with the T-SN 106B. In some implementations, the T-SN 106B can transmit 432A an RRC reconfiguration message that includes a DAPS release indicator to the UE <NUM>, e.g., via an SRB (e.g., SRB3) between the UE <NUM> and the T-SN 106B or via the MN <NUM>. In response to the RRC reconfiguration message, the UE <NUM> can stop 454A applying the DAPS power coordination configuration and release the DAPS power coordination configuration. In some implementations, the RRC controller <NUM> can send an indication to the PHY <NUM> of the UE <NUM>, causing the PHY <NUM> to stop applying 454A the DAPS power coordination configuration.

In some implementations, the T-SN 106B can also release 456A the DAPS power coordination configuration, because the UE <NUM> no longer needs to use the DAPS power coordination configuration and/or the UE <NUM> released the DAPS power coordination configuration. That is, the T-SN 106B can release the DAPS power coordination configuration after including the DAPS power coordination configuration in the T-SN configuration in event 414A.

Subsequent to event 454A, the UE <NUM> can transmit 434A an RRC reconfiguration complete message to the T-SN 106B via the SRB (e.g., SRB3) between the UE <NUM> and the T-SN 106B or via the MN <NUM>, and stop 436A communicating with the S-SN 106A. In some implementations, in response to the DAPS release indicator, a RF chip, receiver, or a transceiver of the UE <NUM> used to communicate with the S-SN 106A during the DAPS PSCell change can enter into low power consumption mode, sleep mode, or be turned off entirely if the DAPS PSCell change is an inter-frequency DAPS PSCell change.

In some implementations, the DAPS power coordination configuration includes one or more of the following DAPS power coordination configuration parameters: the maximum total transmission power (or value thereof) that the UE <NUM> can use for uplink communication with the S-SN 106A during DAPS PSCell change (interchangeably referred to as "CP4"), the maximum total transmission power (or value thereof) that the UE <NUM> can use for uplink communication with the T-SN 106B during DAPS PSCell change (interchangeably referred to as "CP5"), and/or an uplink power sharing mode that the UE <NUM> uses during DAPS PSCell change (interchangeably referred to as "CP6"). The DAPS power coordination configuration parameters can be included in fields or IEs of the DAPS power coordination configuration, in some implementations.

After the UE <NUM> (e.g., PHY <NUM>) applies the DAPS power coordination configuration during the DAPS PSCell change, the UE <NUM> (e.g., PHY <NUM>) can determine (or manage or coordinate) its uplink transmission power for transmissions to the S-SN 106A and its uplink transmission power for transmissions to the T-SN 106B according to the DAPS power coordination configuration, e.g., according to 3GPP specification <NUM> v16. <NUM> or <NUM> v16. In some implementations, if the uplink power sharing mode as designated in CP6 is a first mode (e.g., semi-static mode <NUM>), the UE <NUM> manages its uplink transmission power to not exceed CP4 while transmitting 420A to the S-SN 106A, and to not exceed CP5 while transmitting 426A to the T-SN 106B. In other implementations, if the uplink power sharing mode is a second mode (e.g., semi-static mode <NUM> or dynamic mode), and a first uplink transmission to the S-SN 106A partially or completely overlaps with a second uplink transmission to the T-SN 106B, the UE <NUM> manages uplink transmission power of the first uplink transmission and the second uplink transmission to not exceed CP4 and CP5, respectively. If the uplink power sharing mode is the second mode and the first uplink transmission to the S-SN 106A does not overlap with the second uplink transmission to the T-MN 106B, the UE <NUM> manages uplink transmission power of the first uplink transmission and the second uplink transmission to not exceed respective maximum total transmission power values other than those included in the DAPS power coordination configuration.

In some implementations, the S-SN 106A and T-SN 106B can provide these respective maximum total transmission power values to the UE <NUM> in respective non-DAPS configuration(s) via SRB <NUM> or via MN <NUM>. The S-SN 106A can send non-DAPS configuration(s) to the UE <NUM> in a dedicated message (e.g., RRC reconfiguration message), and the T-SN 106B can send non-DAPS configuration(s) to the UE <NUM> in a dedicated message (e.g., RRC reconfiguration message), in some implementations. In other implementations, the MN <NUM> can directly provide maximum total transmission power values to the UE <NUM> in non-DAPS configuration(s) in a dedicated message (e.g., RRC reconfiguration message).

In some implementations, the T-SN 106B receives a configuration restriction for the DAPS PSCell change from the MN <NUM> in the SN Addition Request message. The T-SN 106B can generate the DAPS power coordination configuration according to the configuration restriction. In one implementation, the MN <NUM> can generate and include preferred power coordination configuration parameters in the configuration restriction. In another implementation, the MN <NUM> can receive the preferred power coordination configuration parameters from the S-SN 106A and include them in the configuration restriction. In any event, the T-SN 106B can include such preferred parameters in the DAPS power coordination configuration. In one implementation, the MN <NUM> or the S-SN 106A can determine the preferred parameters based on the UE capability of the UE <NUM>. For example, the UE capability can indicate or include a UE power class and/or DAPS power sharing mode(s) supported by the UE <NUM>. If the UE capability includes or otherwise indicates supported uplink power sharing mode(s), the MN <NUM> can set the preferred uplink sharing mode to one of the supported uplink power sharing mode(s). If the UE <NUM> is configured to implement all uplink sharing modes supported by the RAN <NUM>, the MN <NUM> or S-SN 106A can select a particular preferred uplink sharing mode according to at least one of the PCP1 and/or PCP2 parameters described above with respect to <FIG>.

Similarly, in another implementation, the MN <NUM> or the T-SN 106B can determine some or all of the DAPS power coordination configuration parameters in the DAPS power coordination configuration based on the preferred power coordination configuration parameters and/or the UE capability of the UE <NUM>. If the UE capability includes or otherwise indicates supported uplink power sharing mode(s), the MN <NUM> or T-SN 106B can set the uplink sharing mode to one of the supported uplink power sharing mode(s) or the preferred uplink sharing mode provided by the MN <NUM> or the S-SN 106A. If the UE <NUM> is configured to implement all uplink sharing modes supported by the RAN <NUM>, the T-SN 106B can select a particular uplink sharing mode according to PCP1, PCP2, and/or the same preferred power coordination configuration parameters provided by the MN <NUM> or the S-SN 106A.

In some implementations, after successfully completing 422A the random access procedure, the UE <NUM> can start transmitting UL data PDUs to the T-SN 106B via the cell 126B, stop transmitting and retransmitting UL data PDUs to the S-SN 106A, stop transmitting control signals on PUCCH(s) to the S-SN 106A, stop transmitting new UL data PDUs to the S-SN 106A while continuing to retransmit UL data PDU(s) to the S-SN 106A, continue DL communication with the S-SN 106A, and/or keep transmitting control signals to the S-SN 106A until event 432A occurs or the DAPS release timer at the UE <NUM> expires, as described above with respect to <FIG>. The T-SN 106B can configure the timer value for the DAPS release timer in the RRC reconfiguration message or in the T-SN configuration, in some implementations. In other implementations, the MN <NUM> configures a timer value for the DAPS release timer in the RRC container message. Upon receiving the timer value, the UE <NUM> starts the DAPS release timer to count the timer value. When the DAPS release timer expires, the UE <NUM> stops 436A communicating with the S-SN 106A. In other implementations, the UE <NUM> uses a predetermined timer value if the MN <NUM> or T-SN 106B does not provide the timer value to the UE <NUM>.

In some implementations, the T-SN 106B includes multiple configuration parameters in the T-SN configuration to configure radio resources for the UE <NUM> to communicate with the T-SN 106B via the T-PSCell 126B. The multiple configuration parameters can configure physical layer, medium access control (MAC) layer, and radio link control bearers. The DAPS PSCell change configuration can be associated or specific to a radio bearer (e.g., DRB). For example, the T-SN 106B can include the DAPS PSCell change configuration in an RB configuration (e.g., RadioBearerConfig IE, DRB-ToAddModList IE or DRB-ToAddMod IE) in the SN Addition Request Acknowledge message at event 416A, and the MN <NUM> can include the RB configuration in the RRC container message at event 417A. The S-SN 106A can also configure the particular DRB and transmit an RB configuration configuring the particular DRB to the UE <NUM>.

In some implementations, the T-SN 106B may not configure an SCell for the UE <NUM> in the T-SN configuration. The T-SN 106B can later transmit RRC reconfiguration message(s) to the UE <NUM> to configure SCell(s) of the T-SN 106B. In response, the UE <NUM> can transmit an RRC reconfiguration complete message to the T-SN 106B via the T-PSCell 126B or a configured SCell for each of the RRC reconfiguration message(s).

In some implementations, the SN configuration (i.e., the S-SN configuration or T-SN configuration) can include a CellGroupConfig IE. The SN configuration can be an RRCReconfiguration message, RRCReconfiguration-IEs, or the CellGroupConfig IE conforming to 3GPP TS <NUM>, or an RRCConnectionReconfiguration message or RRCConnectionReconfiguration-IEs conforming to 3GPP TS <NUM>. In some implementations, the SN configuration can include configurations in the CellGroupConfig IE, RRCReconfiguration-IEs, or RRCConnectionReconfiguration-IEs.

If the S-SN 106A is a gNB, the T-SN configuration or the RRC reconfiguration message can be an RRCReconfiguration message, and the RRC reconfiguration complete message can be an RRCReconfigurationComplete message as defined in 3GPP TS <NUM>. If the S-SN 106A is an ng-eNB, the T-SN configuration or the RRC reconfiguration message can be an RRCConnectionReconfiguration message, and the RRC reconfiguration complete message can be an RRCConnectionReconfigurationComplete message as defined in 3GPP TS <NUM>.

Turning now to <FIG>, according to a DAPS PSCell change scenario 400B, the base station <NUM> operates as an MN for the UE <NUM>, the base station 106A operates as an S-SN, and the base station 106B operates as a T-SN for the UE <NUM>, similar to the DAPS PSCell change scenario 400A of <FIG>. Whereas in <FIG> the UE <NUM> successfully performs a DAPS PSCell change to the T-SN 106B prior to stopping and releasing the power coordination configuration, in <FIG> the UE <NUM> fails to successfully perform the DAPS PSCell change.

Initially, the UE <NUM> in DC communicates 402B data with the MN <NUM> via PCell <NUM> by using an MN configuration, and with the S-SN 106A via PSCell 126A by using an S-SN configuration, similar to event 402A.

Later in time, the MN <NUM>, S-SN 106A, and T-SN 106B collectively perform 460B a DAPS PSCell change preparation procedure, similar to event 460A. The UE <NUM> and the S-SN 106A continue 420B communicating with each other (i.e., in DC with the MN <NUM>), similar to event 420A, by using the S-SN configuration while the UE <NUM> attempts to perform DAPS PSCell change to the T-SN 106B via T-PSCell 126B in accordance with a T-SN configuration received in event 460B.

After the UE <NUM> either applies the DAPS power coordination configuration during the SN change procedure in event 460B, or continues 420B communicating with the S-SN 106A by using the S-SN configuration, the UE <NUM> determines 421B a DAPS PSCell change failure, i.e., the UE <NUM> fails to perform DAPS PSCell change to the T-SN 106B, e.g., within a certain time duration. In response to the determination at event 421B, the UE <NUM> stops 454B applying the DAPS power coordination configuration and releases the DAPS power coordination configuration. In some implementations, the RRC controller <NUM> can send an indication to the PHY <NUM> of the UE <NUM>, causing the PHY <NUM> to stop applying the DAPS power coordination configuration. In some implementations, the UE <NUM> releases the T-SN configuration received in event 460B in response to the determination at event 421B.

If a radio link between the UE <NUM> and the S-SN 106A is available (i.e., no radio link failure occurs on the radio link between the UE <NUM> and the S-SN 106A) and an SRB (e.g., SRB3) between the UE <NUM> and the S-SN 106A is not available, the UE <NUM> can transmit, to the MN <NUM>, e.g., via an SRB (e.g., SRB1), either a failure information message (e.g., FailureInformation) at event 452B or an SCG failure information message (e.g., SCGFailureInformation) at event 472B indicating the DAPS PSCell change failure with respect to the T-SN 106B. In one implementation, after receiving 452B the failure information message from the UE <NUM> in an RRC container message (e.g., ULInformationTransferMRDC), the MN <NUM> extracts the failure information message from the RRC container message and sends 453B the failure information message to the S-SN 106A in an RRC Transfer message. In another implementation, the MN <NUM> does not send the failure information message to the S-SN 106A.

If a radio link between the UE <NUM> and the S-SN 106A is available and an SRB (e.g., SRB3) between the UE <NUM> and the S-SN 106A is available, the UE <NUM> can transmit, to the S-SN 106A via the available SRB, the failure information message indicating the DAPS PSCell change failure with respect to the T-SN 106B at event 455B. In response, the S-SN 106A can send an SN message (e.g., SN Modification Required message) to the MN <NUM> to inform the MN <NUM> of the DAPS PSCell change failure.

If the radio link between the UE <NUM> and the S-SN 106A is not available, the UE <NUM> can transmit 472B the SCG failure information message to the MN <NUM> to inform the MN <NUM> of the DAPS PSCell change failure.

Because the UE <NUM> has stopped 454B applying the DAPS power coordination configuration and released the DAPS power coordination configuration, the UE <NUM> advantageously will not unnecessarily restrict its maximum uplink power according to the DAPS power coordination configuration when communicating with the MN <NUM>, such as when transmitting the failure information message or the SCG failure information message, and/or when communicating with the S-SN 106A, such as when transmitting the failure information message.

In some implementations, the T-SN 106B can release 456B the DAPS power coordination configuration after generating or transmitting the T-SN configuration to the MN <NUM>. In some implementations, the T-SN 106B can release the DAPS power coordination configuration if the UE <NUM> does not successfully perform DAPS PSCell change to the T-SN 106B within a time duration. In other implementations, the MN <NUM> can release the DAPS power coordination configuration in response to receiving 452B the failure information message or in response to receiving the SN message from the S-SN 106A informing the DAPS PSCell change failure.

Although <FIG> and <FIG> depict the DAPS PSCell change scenarios 400A and 400B occurring between two SNs (e.g., the base stations 106A, 106B) with respect to the UE <NUM>, in some implementations, the DAPS PSCell change scenarios 400A and 400B can be carried out within a single SN (e.g., the S-SN 106A) with respect to the UE <NUM>. In such scenarios, messages exchanged between the MN <NUM> and T-SN 106B (e.g., events 412A, 416A, 419A) can be omitted, and events performed or otherwise involving the T-SN 106B (e.g., 414A, 419A, 422A, 426A, 432A, 456A, 434A, 460B) can be performed or otherwise involve the S-SN 106A.

<FIG> is a flow diagram depicting an example method 500A implemented in a user device (e.g., UE <NUM>) for applying and later releasing a DAPS power coordination configuration when switching from a source base station (e.g., S-MN <NUM>, S-SN 106A) to a target base station (e.g., T-MN 106B, T-SN 106B).

At block 502A, a user device receives, from a source base station, a first message including a DAPS power coordination configuration for DAPS operation with the source base station and a target station (e.g., in any one of events 318A, 417A). In accordance with the DAPS operation, the user device (e.g., via DAPS <NUM>) can perform a DAPS handover or DAPS PSCell change. The first message can be a handover command message or an RRC container message, in some implementations.

At block 504A, the user device applies the DAPS power coordination configuration for communicating with the source base station and the target base station (e.g., in any one of events 352A, 452A). In accordance with the DAPS power coordination configuration, the user device restricts respective maximum total transmission uplink power when communicating with the source base station and the target base station.

At block 506A, the user device receives, from the target base station, a second message indicating release of the DAPS operation (e.g., in any one of events 332A, 432A). Accordingly, the target base station explicitly provides the second message to the user device to indicate that the user device should stop communicating with the source base station, and continue communicating with the target base station. The second message can be an RRC reconfiguration message, in some implementations.

At block 508A, in response to receiving the second message, the user device disconnects from the source base station (i.e., stops communicating with the source base station), stops applying the DAPS power coordination configuration, and releases the DAPS power coordination configuration (e.g., in any one of events 336A, 354A, 436A, 454A). In releasing the DAPS power coordination configuration, the user device will not continue to restrict its maximum uplink power according to the DAPS power coordination configuration when communicating with the target base station after successfully performing the DAPS handover or DAPS PSCell change. Because DAPS power restrictions have been removed, the user device can increase its uplink power up to its maximum uplink power, and the user device can reduce the chances of radio link failure with the target base station.

<FIG> is a flow diagram depicting another example method 500B implemented in a user device (e.g., UE <NUM>) for applying and later releasing a DAPS power coordination configuration when switching from a source base station (e.g., S-MN <NUM>, S-SN 106A) to a target station (e.g., T-MN 106B, T-SN 106B). Whereas in <FIG> the user device releases the DAPS power coordination configuration in response to an explicit message (e.g., RRC reconfiguration message) from the target base station, in <FIG> the UE <NUM> releases the DAPS power coordination configuration after performing a random access procedure with the target base station.

At block 502B, a user device receives, from a source base station, a first message including a DAPS power coordination configuration for DAPS operation with the source base station and a target station (e.g., in any one of events 318A, 417A), similar to block 502A.

At block 504B, the user device applies the DAPS power coordination configuration for communicating with the source base station and the target base station (e.g., in any one of events 352A, 452A), similar to block 504A.

At block 506B, the user device performs a random access procedure with the target base station in response to the first message (e.g., in any one of events 322A, 422A).

At block 508B, after performing the random access procedure, the user device stops applying the DAPS power coordination configuration and releases the DAPS power coordination configuration (e.g., in any one of events 354A, 454A).

At block 510B, the user device receives a second message indicating release of the DAPS operation (e.g., event 332A or 432A), similar to block 506A.

At block 512B, the user device disconnects from the source base station (i.e., stops communicating with the source base station) in response to the second message (e.g., in any one of events 336A, 436A), thereby successfully performing the DAPS operation.

<FIG> is a flow diagram depicting another example method 500C implemented in a user device (e.g., UE <NUM>) for applying and releasing a DAPS power coordination configuration when switching from a source base station (e.g., S-MN <NUM>, S-SN 106A) to a target station (e.g., T-MN 106B, T-SN 106B). Whereas in <FIG> the user device successfully performs a DAPS handover or DAPS PSCell change to the target base station, in <FIG> the user device fails to successfully perform the DAPS handover or DAPS PSCell change.

At block 502C, a user device receives, from a source base station, a first message including a DAPS power coordination configuration for DAPS operation with the source base station and a target station (e.g., in any one of events 318B, 460B), similar to blocks 502A and 502B.

At block 504C, the user device applies the DAPS power coordination configuration for communicating with the source base station and the target base station (e.g., in any one of events 352B, 460B), similar to blocks 504A and 504B.

At block 506C, the user device determines a failure (e.g., a radio link failure) while performing the DAPS operation (e.g., in any one of events 321B, 421B). That is, the user device fails to perform either DAPS handover or DAPS PSCell change to the target base station.

At block 508C, in response to determining the failure, the user device stops applying the DAPS power coordination configuration and releases the DAPS power coordination configuration (e.g., in any one of events 354B, 454B). In this way, if the user device later performs an RRC re-establishment procedure with the source base station or the target source base station for example, the user device is not restricted by the maximum uplink power as designated in the DAPS power coordination configuration during and after performing the RRC re-establishment procedure with the source base station or the target base station. Because the user device can increase its uplink power beyond the maximum uplink power indicated in the DAPS power coordination configuration, the user device can decrease the chances of radio link failure with the source base station or the target base station.

<FIG> is a flow diagram depicting an example method <NUM> implemented in a RAN (e.g., RAN <NUM>) for providing a DAPS power coordination configuration to a user device (e.g., UE <NUM>) described with respect to <FIG>, and <FIG>, and later releasing the DAPS power coordination configuration.

At block <NUM>, a RAN transmits, to a user device, a first message including a DAPS power coordination configuration for DAPS operation with a source base station and a target base station of the RAN (e.g., in any one of events 318A, 318B, 417A, 460B). In accordance with the DAPS operation, the user device (e.g., via DAPS <NUM>) can perform a DAPS handover or DAPS PSCell change. The first message can be a handover command message or an RRC container message, in some implementations. The first message can also include multiple configuration parameters to configure radio resources, so that the user device can use these multiple configuration parameters to communicate with the RAN during and after successfully performing the DAPS handover or DAPS PSCell change.

At block <NUM>, after transmitting the first message, the RAN releases the DAPS power coordination configuration (e.g., in any one of events 356A, 356B, 456A, 456B). In some implementations, the RAN releases the DAPS power coordination configuration after transmitting, to the user device, the first message and a second message (e.g., RRC reconfiguration message) to request the user device to disconnect from the source base station (e.g., in any one of events 332A, 432A). In another implementation, the RAN releases the DAPS power coordination configuration after transmitting the first message to the user device and after receiving a third message (e.g., a failure information message) from the user device (e.g., in event 342B). In some implementations, the RAN may retain the multiple configuration parameters provided to the user device in the first message.

Next, <FIG> illustrates an example method 700A for managing a power coordination configuration when performing a DAPS procedure, which can be implemented in a suitable UE such as the UE <NUM>.

At block 702A, the UE receives, from a RAN, a power coordination configuration for application by the UE to constrain uplink power when communicating with a source cell and a target cell of the RAN (e.g., events 318A, 318B, 460A, 460B).

At block 704A, the UE initiates the DAPS procedure in accordance with the power coordination configuration (e.g., events 320A, 320B, 420A, 420B).

At block 706A, in response to detecting a trigger condition, the UE releases the power coordination configuration (e.g., events 354A, 354B, 454A, 454B). In some implementations, the UE releases the power coordination configuration when the UE connects to the target cell when performing the DAPS procedure. In other implementations, the UE releases the power coordination configuration when the UE receives, from the RAN via the target cell, an indication the UE is to release the power coordination configuration. In yet other implementations, the UE releases the power coordination configuration when the UE fails to connect to the target cell when performing the DAPS procedure.

Next, <FIG> illustrates an example method 700B for managing a power coordination configuration when performing a DAPS procedure with a UE (e.g., UE <NUM>), which can be implemented in a suitable RAN such as the RAN <NUM>.

At block 702B, the RAN determines that the UE is to perform the DAPS procedure to connect to a target cell and disconnect from a source cell after connecting to the target cell in accordance with the power coordination configuration (e.g., events 304A, 304B, 460A, 460B).

At block 704B, the RAN transmits, to the UE, the power coordination configuration for application by the UE to constrain uplink power when communicating with the source cell and the target cell (e.g., events 318A, 318B, 460A, 460B).

At block 706B, in response to detecting a trigger condition, the RAN causes the UE to release the power coordination configuration (e.g., events 332A, 332B, 432A, 432B). In some implementations, the RAN causes the UE to release the power coordination configuration when the RAN determines that the UE is connected to the RAN via the target cell after performing the DAPS procedure. In other implementations, the RAN causes the UE to release the power coordination configuration when the RAN transmits, to the UE via the target cell, an indication the UE is to release the power coordination configuration.

The following description may be applied to the description above.

A user device in which the techniques of this disclosure can be implemented (e.g., the UE <NUM>) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (IoT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc..

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

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

Claim 1:
A method performed by a user equipment, UE, for managing a power coordination configuration when performing a dual active protocol stack, DAPS, procedure, the method comprising:
receiving (318B), by the UE and from a source base station of a radio access network, RAN, a power coordination configuration for application by the UE to constrain uplink power when communicating with a source cell and a target cell of the RAN;
initiating (352B), by the UE, the DAPS procedure in accordance with the power coordination configuration; and
in response to detecting a failure when performing the DAPS procedure, releasing (354B), by the UE, the power coordination configuration.