Managing configuration for reestablishing radio connection

Abstract

A method is disclosed in a user equipment (UE) for managing configurations received from a radio access network (RAN) having a first network node and a second network node, the first network node supporting a first configuration and a second configuration for communicating with the RAN, the second network node supporting the first configuration but not the second configuration. The UE receives (1502A) from the first network node (i) the first configuration and (ii) the second configuration; determines (1504A) that the UE is to reestablish a radio connection with the RAN to communicate with the RAN via the second network node; releases (1506A) the second configuration; and communicates (1508A) with the second network node in accordance with the first configuration.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically to the configuration at the management user equipment (UE) and radio access network (RAN). Background Technology

[0002] The background description provided in this disclosure is for the purpose of presenting the general context of this disclosure. Within the scope described in this background section, the work of the supposed inventors, and aspects of the description that may not conform to the prior art at the time of application, are neither expressly nor impliedly acknowledged as prior art to this disclosure.

[0003] In telecommunications systems, the Packet Data Convergence Protocol (PDCP) sublayer of the radio protocol stack provides services such as user plane data transmission, encryption, and integrity protection. For example, the PDCP layer, defined for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface (see 3GPP specification TS 36.323) and New Radio (NR) (see 3GPP specification TS 38.323), provides the ordering of Protocol Data Units (PDUs) in the uplink direction (from the user equipment (UE) to the base station) and the downlink direction (from the base station to the UE). Furthermore, the PDCP sublayer provides Signaling Radio Bearers (SRBs) to the Radio Resource Control (RRC) sublayer. The PDCP sublayer also provides Data Radio Bearers (DRBs) to the Serving Data Adaptation Protocol (SDAP) sublayer or protocol layers such as the Internet Protocol (IP) layer, Ethernet layer, and Internet Control Message Protocol (ICMP). Generally, the UE and base station can use SRBs to exchange RRC messages and Non-Access Stratum (NAS) messages, and can use DRBs to transmit data on the user plane.

[0004] UEs can use several types of SRBs and DRBs. When operating in dual connectivity (DC), the cell associated with the base station operating as the primary node (MN) defines the primary cell group (MCG), while the cell associated with the base station operating as the secondary node (SN) defines the secondary cell group (SCG). The so-called SRB1 resource carries RRC messages, which in some cases include NAS messages on the dedicated control channel (DCCH), and the SRB2 resource supports RRC messages or NAS messages including recorded measurement information, which also pass through the DCCH but have a lower priority than the SRB1 resource. More generally, the SRB1 and SRB2 resources allow the UE and MN to exchange MN-related RRC messages and embed SN-related RRC messages, and can also be referred to as the MCG SRB. The SRB3 resource allows the UE and SN to exchange SN-related RRC messages and can be referred to as the SCG SRB. Separate SRBs allow the UE to exchange RRC messages directly with the MN via lower-layer resources of the MN and SN. Furthermore, a DRB that terminates at MN and uses only the low-level resources of MN can be called an MCG DRB, a DRB that terminates at SN and uses only the low-level resources of SN can be called an SCG DRB, and a DRB that terminates at MCG and uses the low-level resources of MN, SN, or both MN and SN can be called a split DRB.

[0005] In some scenarios, a UE can simultaneously utilize the resources of multiple nodes (e.g., components of a base station or distributed base station) interconnected via backhaul in a radio access network (RAN). This type of connection is called Multiple Radio Dual Connectivity (MR-DC) when these network nodes support different radio access technologies (RATs). When a UE operates in an MR-DC, one base station operates as the MN covering the primary cell (PCell), while another base station operates as the SN covering the primary secondary cell (PSCell). The UE communicates with both the MN (via the PCell) and the SN (via the PSCell). In other scenarios, the UE utilizes the 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 might determine to hand over the UE to a second base station and initiate a handover process. In other scenarios, a UE can simultaneously utilize the resources of RAN nodes (e.g., components of a single base station or distributed base station) interconnected via backhaul to other network elements.

[0006] Documents 3GPP TS 36.300 v16.0.0, 38.300 v16.0.0, and 38.401 v16.1.0 describe procedures related to handover or "reconfiguration with sync" scenarios. These procedures involve message passing (e.g., RRC signaling and preparation) between the RAN node and the UE. Whether in single-connectivity (SC), DC, or other types of multi-connectivity operations, the UE can perform a handover procedure to switch from one cell to another. The UE can switch from the serving base station's cell to the target cell of the target base station, or from the serving base station's first distributed unit (DU) cell to the target cell of a second DU within the same base station, depending on the scenario.

[0007] Document 3GPP TS 37.340 v16.0.0 describes certain procedures for a UE to change its PSCell in a DC scenario. These procedures involve message passing (e.g., RRC signaling and preparation) between the RAN node and the UE. The UE can perform a PSCell change from the serving SN to the target PSCell of the target SN, or a PSCell change from the source distributed unit (DU) of the base station to the target DU of the same base station, depending on the scenario.

[0008] Recently, 3GPP has been discussing and standardizing new technologies, including Release 16 (Rel-16) specifications such as 3GPP specifications 38.331v16.0.0 and 36.331v16.0.0. These new technologies include the Dual Active Protocol Stack (DAPS) handover procedure and the DAPS PSCell change procedure, used to achieve 0 millisecond (ms) user data interruption during handover and PSCell change, respectively. Typically, the length of the interruption experienced at the UE depends on the time difference between when the radio link connection at the source cell is released and when the radio link connection at the target cell is established. Achieving a 0ms user data interruption is possible if the release time is not earlier than the establishment time. When performing DAPS handover and DAPS PSCell change, using DAPS, the UE can communicate with the source cell while establishing a radio link connection at the target cell, and subsequently cease communication with the source cell after establishing a radio link connection at the target cell.

[0009] In some scenarios, the RAN can provide the UE with a DAPS power coordination configuration (e.g., daps-PowerCoordinationInfo-r16) for the UE to perform DAPS handover or DAPS PSCell change. The DAPS power coordination configuration typically indicates the maximum power the UE can transmit on the source PCell and the maximum power 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 DAPS handover. After 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 the RAN may misprocess the DAPS power coordination configuration, causing the UE to unnecessarily limit its maximum uplink power. Therefore, in some scenarios (e.g., cell edge scenarios), the RAN may fail to receive transmissions from the UE, and the UE may encounter radio link failures, leading to service interruption.

[0010] In some cases, when a radio link failure is detected while the UE is communicating with the source base station of the RAN using the configuration, the UE can suspend the configuration and initiate an RRC connection re-establishment process with the target base station of the RAN. However, in some scenarios, communication errors may occur between the UE and the target base station when the UE attempts to restore the configuration with the target base station, for example, when the target base station does not support the configuration that is supported by the source base station. Summary of the Invention

[0011] In general, the UE and one or more base stations operating in the RAN implement the techniques disclosed herein for preparing the UE to perform a DAPS procedure (i.e., DAPS handover, DAPS PSCell change). For example, using these techniques, the RAN can provide the UE with a DAPS power coordination configuration to limit the maximum power 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 according to 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 in response to (a) successful execution of the DAPS procedure, (b) receiving a DAPS release indicator from the RAN after successful execution of the DAPS procedure, or (c) failure to successfully execute the DAP procedure.

[0012] In some implementations, the source base station of the RAN can provide advanced configurations to the UE. For example, advanced configurations enable the UE to use one or more advanced functions or features deployed to the RAN (e.g., related to 5G, 6G technologies). One of the advanced configurations might be related to DAPS. However, the target base station may not support the advanced configuration. Therefore, when the UE initiates an RRC re-establishment procedure with the target base station (e.g., after detecting a radio link failure with the source base station), the UE can (i) release the advanced configuration to reduce the chance of communication problems with the target base station, or (ii) suspend the advanced configuration after performing the re-establishment procedure. If the UE suspends the advanced configuration, the UE can resume or release the advanced configuration in response to receiving a reconfiguration message from the target base station indicating whether the target base station supports or does not support the advanced configuration.

[0013] An example embodiment of these technologies is a method in a UE for managing a power coordination configuration during the execution of a DAPS procedure. The method is implemented using processing hardware and includes: receiving a power coordination configuration from the RAN for the UE to apply in order to constrain uplink power when communicating with the RAN's source and target cells; initiating a DAPS procedure based on the power coordination configuration; and releasing the power coordination configuration in response to the detection of a triggering condition.

[0014] Another example embodiment of these technologies is a method in the RAN for managing power coordination configurations when a UE performs a DAPS procedure. The method is implemented using processing hardware and includes: determining that the UE will perform a DAPS procedure to connect to a target cell according to the power coordination configuration and to disconnect from the source cell after connecting to the target cell; sending the power coordination configuration to the UE to constrain uplink power when communicating with the source and target cells; and releasing the power coordination configuration in response to detecting a triggering condition.

[0015] Another example embodiment of these technologies is a method in a UE for managing configurations received from a radio access network (RAN), the RAN having a first network node supporting a first configuration and a second configuration for communication with the RAN, and a second network node supporting the first configuration but not the second configuration. The method is implemented using processing hardware and includes: receiving the first and second configurations from the first network node; determining that the UE wants to re-establish a radio connection with the RAN to communicate with the RAN via the second network node; suspending the second configuration; and communicating with the second network node according to the first configuration.

[0016] Another example embodiment of these technologies is a method for managing configurations in a first network node operating in a RAN. The method is implemented using processing hardware and includes: communicating with a UE via a first radio interface based on a first configuration associated with a first set of functions and a second configuration associated with a second set of functions; determining that the UE intends to communicate with a second network node operating in the RAN via a second radio interface; and in a first case, transmitting the first and second configurations to the second network node in response to determining that a condition is met, and in a second case, transmitting the first configuration to the second network node and preventing the second configuration from being transmitted to the second network node in response to determining that a condition is not met.

[0017] Another example embodiment of these technologies is a method for managing configurations in a second network node operating in a RAN that also includes a first network node. The method is implemented using processing hardware and includes: performing a process for re-establishing a radio connection via a second radio interface with a UE that previously communicated with the first network node via a first radio interface, based on a first configuration associated with a first set of functions and a second configuration associated with a second set of functions; receiving the first configuration and the second configuration from the first network node; and in a first case, retaining the first configuration and the second configuration in response to determining that a condition is met, and in a second case, retaining the first configuration and releasing the second configuration in response to determining that a condition is not met.

[0018] Another embodiment of these technologies is a base station that includes processing hardware and is configured to implement one of the methods described above.

[0019] Another embodiment of these technologies is a UE that includes processing hardware and is configured to implement one of the methods described above. Attached Figure Description

[0020] Figure 1A This is a block diagram of an example system in which the RAN and UE can implement the technology for managing configuration disclosed herein during the execution of DAPS handover procedures, DAPS PSCell change procedures, or RRC reconstruction procedures.

[0021] Figure 1B Among them, centralized units (CU) and distributed units (DU) can be Figure 1A A block diagram of an example base station operating in the system;

[0022] Figure 2 yes Figure 1A The UE can be based on its relationship with Figure 1A A block diagram of an example protocol stack for base station communication;

[0023] Figure 3A and Figure 3BThis is a message passing diagram of an example scenario in which the RAN prepares the UE for the DAPS handover process by providing the UE with DAPS power coordination configuration;

[0024] Figure 4A and Figure 4B This is a message passing diagram of an example scenario in which the RAN prepares the DAPS PSCell change process for the UE by providing the DAPS power coordination configuration to the UE;

[0025] Figure 5A and Figure 5B This is a message passing diagram of an example scenario in which the UE performs an RRC reconstruction procedure on the RAN and releases or retains (one or more) advanced configurations in response to initiating the RRC reconstruction procedure or after initiating the RRC reconstruction procedure;

[0026] Figure 6A This is a flowchart of an example scenario in which the UE stops applying and releases the DAPS power coordination configuration in response to a message received from the RAN;

[0027] Figure 6B This is a flowchart of another example scenario in which the UE stops and releases the DAPS power coordination configuration after performing a random access procedure on the RAN;

[0028] Figure 6C This is a flowchart of another example scenario in which the UE stops and releases the DAPS power coordination configuration after determining that the DAPS operation with the RAN has failed;

[0029] Figure 7 This is a flowchart of an example scenario in which the RAN provides the UE with the DAPS power coordination configuration and then releases the DAPS power coordination configuration;

[0030] Figure 8 This is a flowchart of an example scenario where the UE releases advanced configuration in response to the RRC reconstruction process;

[0031] Figure 9 This is a flowchart illustrating an example scenario where the RAN releases advanced configurations in response to the RRC rebuild process;

[0032] Figure 10 This is a flowchart illustrating an example of a source base station in the RAN sending an interface message, excluding advanced configuration, to a target base station in the RAN.

[0033] Figure 11 This is a flowchart of another example scenario in which the RAN releases advanced configurations in response to the RRC rebuild process;

[0034] Figure 12This is a flowchart of an example method in which the source base station of the RAN sends interface messages, including or excluding advanced configurations, to the target base station of the RAN to support a scenario where the user equipment can release or retain advanced configurations.

[0035] Figure 13 This is a flowchart of an example method in which the target base station of the RAN receives an interface message from the source base station of the RAN and retains or releases advanced configuration in response to the interface message;

[0036] Figure 14A This is a flowchart of an example method for the UE to manage power coordination configuration when performing the DAPS procedure on the RAN;

[0037] Figure 14B This is a flowchart of an example method in which the RAN manages power coordination configuration when performing the DAPS procedure on the UE;

[0038] Figure 15A This is a flowchart of an example method in which the UE manages a first configuration (supported by the first and second network nodes of the RAN) and a second configuration (supported by the first network node but not by the second network node) when performing a reconstruction process on the second network node;

[0039] Figure 15B This is a flowchart illustrating an example method where the first network node of the RAN manages the first and second configurations when the UE needs to communicate with the second network node of the RAN; and

[0040] Figure 15C This is a flowchart of an example method in which the second network node of the RAN manages the configuration received from the first network node of the RAN. Detailed Implementation

[0041] Figure 1A An example wireless communication system 100 is described, which can implement the configuration processing techniques of this disclosure, for example, when performing a DAPS handover procedure, a DAPS PSCell change procedure, or an RRC reconstruction procedure. The wireless communication system 100 includes a UE 102 and a RAN 105 (e.g., base stations 104, 106A, 106B) connected to a core network (CN) 110. Base stations 104, 106A, and 106B can be any suitable type of base station(s), such as an evolved Node B (eNB), a next-generation eNB (ng-eNB), or a 5G Node B (gNB). As a more specific example, base station 104 can be an eNB or a gNB, and base stations 106A and 106B can be gNBs.

[0042] Base station 104 supports cell 124, base station 106A supports cell 126A, and base station 106B supports cell 126B. Cell 124 partially overlaps with cells 126A and 126B, allowing UE 102 to communicate with base station 104 while simultaneously being within range of communication with either base station 106A or 106B (or within range of detecting or measuring signals from either base station 106A or 106B). This overlap enables UE 102 to handover between cells (e.g., from cell 124 to cell 126A or 126B) or base stations (e.g., from base station 104 to base station 106A or 106B) before experiencing a radio link failure, for example. Furthermore, this overlap allows for various dual connectivity (DC) scenarios discussed below. For example, UE 102 can communicate with base station 104 (operating as MN) and base station 106A (operating as SN) in the DC, and after the handover is completed, it can communicate with base station 106B (operating as MN). As another example, UE 102 can communicate with base station 104 (operating as MN) and base station 106A (operating as SN) in the DC, and after the SN change is completed, it can communicate with base station 104 (operating as MN) and base station 106B (operating as SN).

[0043] More specifically, when UE 102 is in a DC with base stations 104 and 106A, base station 104 operates as a primary eNB (MeNB), primary ng-eNB (Mng-eNB), or primary gNB (MgNB), and base station 106A operates as a secondary gNB (SgNB) or secondary ng-eNB (Sng-eNB). In implementations and scenarios where UE 102 is in an SC with base station 104 but can operate in a DC, base station 104 operates as a MeNB, Mng-eNB, or MgNB, and base station 106A operates as a candidate SgNB (C-SgNB) or candidate Sng-eNB (C-Sng-eNB). Although various scenarios are described below where base station 104 operates as an MN and base station 106A (or 106B) operates as an SN or T-SN, in different scenarios, any one of base stations 104, 106A, and 106B can generally operate as an MN, SN, or T-SN. Therefore, in some implementations, base stations 104, 106A, and 106B can implement similar group functions and each supports MN, SN, and T-SN operations.

[0044] In operation, UE 102 may use radio bearers (e.g., DRB or SRB) that terminate at different times to MN (e.g., base station 104) or SN (e.g., base station 106A). For example, after handover to base station 106B, UE 102 may use radio bearers (e.g., DRB or SRB) that terminate at different times to base station 106B. UE 102 may apply one or more security keys when communicating on radio bearers in the uplink (from UE 102 to the base station) and / or downlink (from the base station to UE 102) directions.

[0045] Base station 104 includes processing hardware 130, which may include one or more general-purpose processors (e.g., central processing unit (CPU)) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors and / or dedicated processing units. Figure 1A In the example implementation, the processing hardware 130 includes a base station RRC controller 132 configured to manage or control RRC configuration and RRC procedures. For example, the base station RRC controller 132 may be configured to support RRC message passing associated with DAPS handover procedures and DAPS PSCell change procedures, reconstruction procedures, recovery procedures, and / or support necessary operations when the base station 104 operates as an MN, as described below.

[0046] Base station 106A includes processing hardware 140, which may 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 dedicated processing units. Figure 1A In the example implementation, the processing hardware 140 includes a base station RRC controller 142 configured to manage or control RRC configuration and RRC procedures. For example, the base station RRC controller 142 may be configured to support RRC message passing associated with DAPS handover procedures and DAPS PSCell change procedures, reconstruction procedures, recovery procedures, and / or support necessary operations when the base station 106A operates as an SN or target SN (T-SN), as described below. Although Figure 1A Although not shown, base station 106B may include processing hardware similar to processing hardware 140 of base station 106A.

[0047] UE 102 includes processing hardware 150, which may 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 dedicated processing units. Figure 1AIn the example implementation, the processing hardware 150 includes a UE RRC controller 152 configured to manage or control the RRC configuration RRC process. For example, the UE RRC controller 152 may be configured to support RRC message passing associated with DAPS handover procedures and DAPS PSCell change procedures and / or reconstruction procedures, according to any of the implementations discussed below.

[0048] CN 110 can be either the Evolved Packet Core (EPC) 111 or the 5th Generation Core (5GC) 160, both of which are... Figure 1A The following describes the process. Base station 104 can be an eNB supporting an S1 interface for communication with EPC 111, an ng-eNB supporting an NG interface for communication with 5GC 160, or a gNB supporting an NR radio interface and an NG interface for communication with 5GC 160. Base stations 106A and 106B can each be an EN-DC gNB (en-gNB) with an S1 interface to EPC 111, an en-gNB not connected to EPC 111, a gNB supporting an NR radio interface and an NG interface to 5GC 160, or an ng-eNB supporting an EUTRA radio interface and an NG interface to 5GC 160. To directly exchange messages with each other in the scenarios discussed below, base stations 104, 106A, and 106B can support X2 or Xn interfaces.

[0049] Among other components, EPC 111 may include a Serving Gateway (S-GW) 112 and a Mobility Management Entity (MME) 114. S-GW 112 is typically configured to transmit user plane packets related to audio calls, video calls, internet traffic, etc., while MME 114 is configured to manage authentication, registration, paging, and other related functions. 5GC 160 includes a User Plane Function (UPF) 162 and Access and Mobility Management (AMF) 164 and / or Session Management Function (SMF) 166. UPF 162 is typically configured to transmit user plane packets related to audio calls, video calls, internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging, and other related functions, and SMF 166 is configured to manage PDU sessions.

[0050] Typically, the wireless communication network 100 may include any suitable number of base stations supporting NR cells and / or EUTRA cells. For example, base station 104 and base station 106A may also support cells 122 and 123, respectively. More specifically, EPC 111 or 5GC160 may connect to any suitable number of base stations supporting NR cells and / or EUTRA cells. Although the examples below specifically refer to particular CN types (EPC, 5GC) and RAT types (5G NR and EUTRA), in general, the techniques disclosed herein can also be applied to other suitable radio access and / or core network technologies, such as sixth-generation (6G) radio access and / or 6G core networks or 5G NR-6G DC.

[0051] As described above, the wireless communication system 100 can support various procedures (e.g., DAPS switching, DAPS PSCell change, reconstruction, etc.) and operating modes (e.g., SC or DC). Example operations of various procedures that can be implemented in the wireless communication system 100 will now be described.

[0052] In some implementations, the wireless communication system 100 supports a conventional handover preparation process (i.e., a non-DAPS handover preparation process). In one scenario, for example, base station 104 can perform a non-DAPS handover preparation process to configure UE 102 to hand over from cell 124 of base station 104 to cell 126A of base station 106A. In this scenario, base station 104 and base station 106A operate as a source base station (S-BS) or source MN (S-MN) and a target base station (T-BS) or target MN (T-MN), respectively. During the non-DAPS handover preparation process, base station 104 sends a handover request (T-MN) message to base station 106A. In response to the handover request message, base station 106A includes the configuration parameters for configuring radio resources for UE 102 in a handover command message, includes the handover command message in a handover request acknowledgement message, and sends the handover request acknowledgement message to base station 104. Subsequently, base station 104 transmits a handover command message to UE 102 and then interrupts (or stops) transmitting data to or receiving data from UE 102.

[0053] Upon receiving the handover command message, UE 102 hands over to base station 106A via cell 126A and communicates with base station 106A using the configuration parameters in the handover command message. Specifically, in response to the handover command message, UE 102 disconnects from cell 124 (or base station 104), performs a random access procedure to base station 106A via cell 126A, and transmits a handover complete message to base station 106A via cell 126A.

[0054] In some implementations, the wireless communication system 100 supports a DAPS handover preparation process. For example, in one scenario, base station 104 may perform a DAPS handover preparation process to configure UE 102 to hand over from cell 124 of base station 104 to cell 126B of base station 106B. In this scenario, base station 104 and base station 106B operate as S-BS or S-MN and T-BS or T-MN, respectively. During the DAPS handover preparation process, base station 104 sends a handover request message to base station 106B. In some implementations, base station 104 may explicitly request a DAPS handover in the handover request message, for example, by including a DAPS indicator in the handover request message. In response to the handover request message, and in order to accept the DAPS handover request, base station 106B includes configuration parameters for configuring radio resources for UE 102 in a handover command, includes the handover command message in a handover request confirmation message, and sends the handover request confirmation message to base station 104. In some implementations, base station 106B may indicate DAPS handover in the handover command message, for example, by including one or more DAPS configurations or DAPS indicators in the handover command message, or by including the indicators in the handover request confirmation message. Then, base station 104 transmits the handover command message to UE 102.

[0055] Upon receiving the handover command message, UE 102 performs a DAPS handover procedure to switch to base station 106B via cell 126B and communicates with base station 106B using the configuration parameters in the handover command message. Specifically, in response to the handover command message, although UE 102 disconnects from cell 124 (or base station 104) during a non-DAPS handover, UE 102 maintains its connection with base station 104 via cell 124 during the DAPS handover, performs a random access procedure to base station 106B via cell 126B, and transmits a handover completion message to base station 106B via cell 126B.

[0056] During DAPS handover, while maintaining the connection with base station 104 via cell 124, UE 102 actually has two links: a source MCG link with base station 104 and a target MCG link with base station 106B. UE 102 can continue to receive data from base station 104 (i.e., downlink data) until UE 102 receives an instruction from base station 106B to release the source MCG link with base station 104. UE 102 can continue to transmit data to base station 104 (e.g., new uplink data transmission or PDCP SDU retransmission) until UE 102 successfully completes the random access procedure with base station 106B or receives an instruction from base station 106B to release the MCG link with base station 104.

[0057] In some implementations, the wireless communication system 100 supports DC operation during the handover preparation process described above. In one scenario, for example, after UE 102 connects to base station 104, and base station 104 performs an SN addition procedure to add base station 106A as an SN, thereby configuring UE 102 to operate in DC with base stations 104 and 106A, base stations 104 and 106A operate as MN and SN, respectively. Subsequently, MN 104 can initiate a non-DAPS or DAPS handover preparation procedure to hand over UE 102 to T-MN 106B.

[0058] In some implementations, the wireless communication system 100 supports a conventional PSCell change preparation procedure (i.e., a non-DAPS PSCell change preparation procedure). In one scenario, for example, UE 102 is initially in a DC with MN 104 (e.g., via PCell 124) and SN 106A (via PSCell 123). SN 106A can provide UE 102 with a T-PSCell 126A configuration. UE 102 stops communicating with SN 106A via PSCell 123 and attempts to connect to T-PSCell 126A after receiving the T-PSCell 126A configuration. In another scenario, for example, when UE 102 is in a DC with MN 104 and SN 106A, MN 104 determines to change UE 102's SN from base station 106A (which may be referred to as the source SN or S-SN) to base station 106B (which may be referred to as the target SN or T-SN) as part of a non-DAPS PSCell change process. UE 102 stops communicating with S-SN 106A via PSCell 123 and, after receiving the configuration of T-PSCell 126B, attempts to connect to T-SN 106B via T-PSCell 126B.

[0059] In some implementations, the wireless communication system 100 supports DAPS PSCell changes. In one scenario, for example, UE 102 is initially in a DC with MN 104 (e.g., via PCell 124) and SN 106A (via PSCell 123). SN 106A can provide UE 102 with a T-PSCell 126A configuration. UE 102 continues to communicate with SN 106A via PSCell 123 while attempting to connect to T-PSCell 126A after receiving the T-PSCell 126A configuration. After T-PSCell 126A begins operating as UE 102's PSCell 126A, UE 102 stops communicating with SN 106A via PSCell 123. In another scenario, for example, when UE 102 is in a DC with MN 104 and SN 106A, MN 104 determines to change UE 102's SN from base station 106A (which may be referred to as the source SN or S-SN) to base station 106B (which may be referred to as the target SN or T-SN) as part of a DAPS PSCell change process. UE 102 continues to communicate with S-SN 106A via PSCell 123 and, after receiving the configuration of T-PSCell 126B, attempts to connect to T-SN 106B via T-PSCell 126B. After T-PSCell 126B begins operating as UE 102's PSCell 126B, UE 102 stops communicating with S-SN 106A via PSCell 123.

[0060] In different configurations or scenarios of the wireless communication system 100, base station 104 can operate as a MeNB, Mng-eNB, or MgNB; base station 106B can operate as a MeNB, Mng-eNB, MgNB, SgNB, or Sng-eNB; and base station 106A can operate as an SgNB or Sng-eNB. UE 102 can communicate with base station 104 and base stations 106A or 106B via the same radio access technology (RAT), such as EUTRA or NR, or via a different RAT.

[0061] When base station 104 is a MeNB and base station 106A is an SgNB, UE 102 can be in an EUTRA-NR DC (EN-DC) with MeNB 104 and SgNB 106A. When base station 104 is a Mng-eNB and base station 106A is an SgNB, UE 102 can be in a Next Generation (NG) EUTRA-NR DC (NGEN-DC) with Mng-eNB 104 and SgNB 106A. When base station 104 is a MgNB and base station 106A is an SgNB, UE 102 can be in an NR-NR DC (NR-DC) with MgNB 104 and SgNB 106A. When base station 104 is a MgNB and base station 106A is an Sng-eNB, UE 102 can be in an NR-EUTRA DC (NE-DC) with MgNB 104 and Sng-eNB 106A.

[0062] Figure 1B An example distributed implementation of any one or more of base stations 104, 106A, and 106B is depicted. In this implementation, base station 104, 106A, or 106B includes a centralized unit (CU) 172 and one or more distributed units (DUs) 174. CU 172 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 said one or more general-purpose processors and / or dedicated processing units. For example, CU 172 may include... Figure 1A The processing hardware 130 or 140 may include a base station RRC controller (e.g., RRC controller 142) configured to manage or control one or more RRC configurations and / or RRC procedures when the base station (e.g., base station 106A) is operating as an SN.

[0063] Each of DU 174 also includes processing hardware, which may 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 dedicated processing units. For example, the processing hardware may include a MAC controller configured to manage or control one or more Media Access Control (MAC) operations or procedures (e.g., random access procedures), and an RLC controller configured to manage or control one or more Radio Link Control (RLC) operations or procedures when the base station (e.g., base station 106A) operates as an MN or SN. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0064] Figure 2An example Dual Active Protocol Stack (DAPS) 200 is shown in a simplified manner for UE 102 to communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106A, or 106B).

[0065] In example stack 200, the EUTRA physical layer (PHY) 202A provides a transport channel to the EUTRA MAC sublayer 204A, which in turn provides a logical channel to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A then provides an RLC channel to the EUTRA PDCP sublayer 208, and in some cases, also to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides a transport channel to the NR MAC sublayer 204B, which in turn provides a logical channel to the NR RLC sublayer 206B. The NR RLC sublayer 206B then provides an RLC channel to the NR PDCP sublayer 210. In some implementations, UE 102 supports, for example... Figure 2 The EUTRA and NR stacks shown are designed to support handover between EUTRA and NR base stations and / or support DC on the EUTRA and NR interfaces. Furthermore, as... Figure 2 As shown in the figure, UE 102 can support the layering of NR PDCP sublayer 210 on EUTRA RLC sublayer 206A.

[0066] EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 receive packets that can be referred to as Service Data Units (SDUs) (e.g., from the Internet Protocol (IP) layer, layered directly or indirectly on PDCP layers 208 or 210), and output packets that can be referred to as Protocol Data Units (PDUs) (e.g., to RLC layers 206A or 206B). Except where the difference between SDU and PDU is relevant, for simplicity, this disclosure refers to both SDU and PDU as “packets”.

[0067] For example, on the control plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide SRBs to exchange RRC messages. On the user plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide DRBs to support data exchange.

[0068] In a scenario where UE 102 operates in EUTRA / NR DC (EN-DC), where base station 104A operates as a MeNB and base station 106A operates as an SgNB, wireless communication system 100 can provide UE 102 with a bearer terminated using EUTRA PDCP sublayer 208, or a bearer terminated using NR PDCP sublayer 210. In various scenarios, wireless communication system 100 can also provide UE 102 with a bearer terminated using only NR PDCP sublayer 210. The MN-terminated bearer can be an MCG bearer or a separate bearer. The SN-terminated bearer can be an SCG bearer or a separate 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.

[0069] Figure 3A and Figure 3B This corresponds to the DAPS handover scenario where the base station initiates the DAPS handover process for the UE. Figure 4A and Figure 4B This corresponds to the DAPS PSCell change scenario where the base station initiates the DAPS PSCell change process for the UE. Although Figure 3A , Figure 3B , Figure 4A and Figure 4B The accompanying description specifically refers to UE 102 and base stations 104, 106A and / or 106B of FIG1, but it should be understood that the following technologies may be implemented by other components and / or in systems different from the wireless communication system 100 of FIG1.

[0070] First refer to Figure 3A According to DAPS handover scenario 300A, base station 104 operates as the source MN (S-MN) for UE 102, and base station 106B operates as the target MN (T-MN) for UE 102. Both base station 104 and base station 106B can be referred to as MNs in both SC and DC scenarios.

[0071] Initially, UE 102 communicates 302A data (e.g., uplink (UL) data PDUs and / or downlink (DL) data PDUs) with S-MN 104 using S-MN configuration. In some scenarios, UE 102 communicates 302A data with S-MN 104 in SC, or with S-MN 104 in DC (as MN operation) and Figure 3A The SN (e.g., base station 106A), not shown in the diagram, communicates 302A data.

[0072] Later, S-MN 104 determines 304A to initiate a DAPS handover so that T-MN 106B and UE 102 can communicate, for example, blindly or in response to the detection of a suitable event. For example, the determination in event 304A may occur in response to S-MN 104 receiving one or more measurement report results from UE 102 that are higher (or lower) than one or more predetermined thresholds, or calculating a filtering result higher (or lower) than the predetermined threshold (based on said measurement result(s)). In another example, a suitable event could be that UE 102 is moving toward T-MN 106B. In yet another example, a suitable event could be that S-MN 104 generates or obtains one or more measurement results based on measurements of signals received from UE 102 that are higher (or lower) than one or more predetermined thresholds.

[0073] After determining that DAPS handover has been initiated (304A), S-MN 104 sends a 312A handover request message to T-MN 106B. In some implementations, the handover request message includes the S-MN configuration. In response, T-MN 106B generates a 314A handover command message for DAPS handover, which includes the T-MN configuration (including the DAPS power coordination configuration, such as DAPS-PowerCoordinationInfo-r16IE or DAPS-Configuration-r16IE), includes the handover command message in a handover request confirmation message, and sends a 316A handover request confirmation message to S-MN 104. Subsequently, S-MN 104 transmits a 318A handover command message to UE 102. The handover command message also includes one or more random access configurations required for UE 102 to hand over to T-MN 106B, and in some implementations, includes additional fields or IEs, such as mobility fields or IEs for the PCell of T-MN 106B (e.g., mobilityControlInfo field, reconfigurationWithSync field, MobilityControlInfo IE, ReconfigurationWithSync IE), which may include some or all of the random access configurations. In some implementations, T-MN 106B may include DAPS power coordination configurations in the mobility fields or IEs.

[0074] In some implementations, the T-MN 106B may include one or more DAPS configurations (e.g., one or more daps-Config fields or one or more daps-HO fields) in the handover command message, which indicate one or more specific DRBs as one or more DAPS bearers. These DAPS configurations enable the UE 102 to use DAPS (e.g., DAPS 200) to communicate with the S-MN 104 (using the configuration in the S-MN configuration) and the T-MN 106B (using the configuration in the T-MN configuration during and after a successful DAPS handover).

[0075] Therefore, in response to receiving the 318A handover command message, UE 102 (e.g., PHY 202) applies (i.e., uses) the 352A DAPS power coordination configuration and continues communication with S-MN 104 using the S-MN configuration, while UE 102 attempts to hand over to T-MN 106B according to the handover command message. In some implementations, RRC controller 152 can send the DAPS power coordination configuration parameters from the DAPS power coordination configuration to PHY 202, which in turn applies the DAPS power coordination configuration parameters.

[0076] When attempting a DAPS handover, UE 102 initiates a 322A random access procedure to T-MN 106B via a target cell (e.g., PCell126B) covered by T-MN 106B, for example, by using one or more random access configurations in the handover command message received from S-MN 104 in event 318A. After acquiring access to the channel, UE 102 transmits a 324A handovercomplete message to T-MN 106B via the target cell during or after the successful completion of the random access procedure. After T-MN 106B recognizes UE 102 during the random access procedure (i.e., UE 102 successfully resolves the random access contention) or receives the 324A handovercomplete message, UE 102 communicates 326A control signals and data (e.g., UL data PDU or DL ​​data PDU) with T-MN 106B via the target cell using the configuration indicated in the handover command message. T-MN 106B sends a 328A handover success message to S-MN 104. After receiving the handover success message, S-MN 104 stops 330A communication with UE 102.

[0077] The one or more DAPS configurations and / or DAPS power coordination configurations enable UE 102 to continue communicating with S-MN 104 while simultaneously communicating with T-MN 106B. Because UE 102 no longer needs to use DAPS to continue communicating with S-MN 104 after a successful DAPS handover, UE 102 can stop applying the DAPS power coordination configuration (354A) and release it. In this way, UE 102 will not unnecessarily limit its maximum uplink power according to the DAPS power coordination configuration when communicating with T-MN 106B, thereby reducing the chance of radio link failure with T-MN 106B. In some implementations, T-MN 106B may send an RRC reconfiguration message (332A) including a DAPS release indicator to UE 102 before, after, or simultaneously with the transmission of the 328A handover success message, for example via the target cell (e.g., PCell 126B). In response to an RRC reconfiguration message or a DAPS release indicator, UE 102 can stop applying the DAPS power coordination configuration (354A) and release the DAPS power coordination configuration. In some implementations, UE 102 can stop applying the DAPS power coordination configuration (354A) and release the DAPS power coordination configuration after successfully executing the 322A random access procedure. In some implementations, the RRC controller 152 can send an indication to UE 102's PHY 202, causing PHY 202 to stop applying the 354A DAPS power coordination configuration.

[0078] In some implementations, T-MN 106B can also release the 356ADAPS power coordination configuration because UE 102 no longer needs to use the DAPS power coordination configuration and / or UE 102 has released the 354ADAPS power coordination configuration. That is, 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.

[0079] Following event 354A, UE 102 may transmit a 334ARRC reconfiguration complete message to T-MN 106B and cease communication with S-MN 104 (i.e., UL and / or DL ​​communication) via 336A. In some implementations, in response to a DAPS release indicator, the RF chip, receiver, or transceiver of UE 102 used for communication with S-MN 104 during DAPS handover may enter a low-power mode, a sleep mode, or be completely powered off (if the DAPS handover is an inter-frequency DAPS handover).

[0080] 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 a value thereof) that UE 102 can use for uplink communication with S-MN 104 during DAPS handover (interchangeably referred to as "CP1"), the maximum total transmission power (or a value thereof) that UE 102 can use for uplink communication with T-MN 106B during DAPS handover (interchangeably referred to as "CP2"), and / or the uplink power sharing mode used by UE 102 during DAPS handover (interchangeably referred to as "CP3"). In some implementations, the DAPS power coordination configuration parameters may be included in fields or IEs of the DAPS power coordination configuration. For readability purposes in this disclosure, "configuration" (e.g., DAPS power coordination configuration) refers to one or more parameters included in the configuration. Furthermore, the terms "parameter" or "multiple parameters" as used herein also refer to one or more values ​​corresponding to said parameter(s).

[0081] After UE 102 (e.g., PHY 202) applies the DAPS power coordination configuration during DAPS handover, UE 102 (e.g., PHY 202) can determine (or manage or coordinate) its uplink transmission power to S-MN 104 and its uplink transmission power to T-MN 106B according to the DAPS power coordination configuration (e.g., according to 3GPP specification 38.213v16.1.0 or 36.213v16.1.0). In some implementations, if the uplink power sharing mode specified in CP3 is a first mode (e.g., semi-static mode 1), then UE 102 manages its uplink transmission power to not exceed CP1 while transmitting 320A to S-MN 104, and not exceed CP2 while transmitting 326A to T-MN 106B. In other implementations, if the uplink power sharing mode is the second mode (e.g., semi-static mode 2 or dynamic mode), and the first uplink transmission to S-MN 104 partially or completely overlaps with the second uplink transmission to T-MN 106B, then the uplink transmission power managed by UE 102 for the first and second uplink transmissions does not exceed CP1 and CP2, respectively. If the uplink power sharing mode is the second mode and the first uplink transmission to S-MN 104 does not overlap with the second uplink transmission to T-MN 106B, then the uplink transmission power managed by UE 102 for the first and second uplink transmissions does not exceed the corresponding maximum total transmission power values, except for those included in the DAPS power coordination configuration.

[0082] In some implementations, S-MN 104 and T-MN 106B can provide these corresponding maximum total transmission power values ​​to UE 102 in the corresponding non-DAPS configuration(s). In some implementations, S-MN 104 can send the non-DAPS configuration(s) to UE 102 in one or more broadcast messages (e.g., one or more system information blocks and / or dedicated messages (e.g., RRC reconfiguration messages)), and T-MN 106B can send the non-DAPS configuration(s) to UE 102 in a handover command message or one or more broadcast messages (e.g., one or more system information blocks on PCell 126B).

[0083] In some implementations, T-MN 106B receives configuration constraints for DAPS handover from S-MN 104 in a handover request message. T-MN 106B can generate a DAPS power coordination configuration based on the configuration constraints. In one implementation, S-MN 104 can generate preferred power coordination configuration parameters and include them in the configuration constraints, and T-MN 106B can then include such preferred parameters in the DAPS power coordination configuration. In one implementation, S-MN 104 can determine the preferred parameters based on the UE capabilities of UE 102. For example, UE capabilities can indicate or include the UE power level and / or one or more DAPS power sharing modes supported by UE 102. If the UE capabilities include or otherwise indicate supported uplink power sharing modes, S-MN 104 can set the preferred uplink sharing mode to one of the supported uplink power sharing modes. If UE 102 is configured to implement all uplink sharing modes supported by RAN 105, S-MN 104 may select a specific preferred uplink sharing mode based on one or more of the following preferred power coordination configuration parameters: UE power level (interchangeably referred to as "PCP1") and / or regulatory requirements (interchangeably referred to as "PCP2").

[0084] Similarly, in another implementation, T-MN 106B may 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 S-MN 104 and / or the UE capabilities of UE 102. If the UE capabilities include or otherwise indicate supported uplink power sharing modes(s), T-MN 106B may set the uplink sharing mode to one of the supported uplink power sharing modes(s) or the preferred uplink sharing mode provided by S-MN 104. If UE 102 is configured to implement all uplink sharing modes supported by RAN 105, T-MN 106B may select a specific uplink sharing mode based on the same preferred power coordination configuration parameters provided by PCP1, PCP2, and / or S-MN 104.

[0085] In some implementations, after successfully completing the 322A random access procedure, UE 102 stops transmitting and retransmitting UL data PDUs and / or control signals to S-MN 104 on one or more Physical Uplink Control Channels (PUCCHs). In other implementations, UE 102 stops transmitting new UL data PDUs to S-MN 104, but continues to retransmit one or more UL data PDUs to S-MN 104 if requested by S-MN 104 after the successful completion of the 322A random access procedure, until event 336A occurs. In such implementations, UE 102 may continue DL communication with S-MN 104 (i.e., receiving control signals, reference signals, DL PDUs, etc.), and / or transmit control signals (e.g., HARQ acknowledgments, HARQ negative acknowledgments, and / or channel state information) to S-MN 104 on one or more PUCCHs, until event 332A occurs or the DAPS release timer at UE 102 expires. In some implementations, T-MN 106B may configure a timer value for the DAPS release timer in the handover command message in event 314A or in the RRC reconfiguration message in event 332A. Upon receiving the handover command message 318A or the RRC reconfiguration message 332A, UE 102 starts the DAPS release timer. When the DAPS release timer expires, UE 102 stops communication between 336A and S-MN 104. In other implementations, if T-MN 106B does not include the timer value in the handover command message or RRC reconfiguration message, UE 102 uses a predetermined timer value. T-MN 106B may include the predetermined timer value in the handover success message; this predetermined timer value may be the same as the timer value in the RRC reconfiguration message or a larger value than the timer value in the handover command message.

[0086] 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. UE 102 can use these multiple configuration parameters to communicate with T-MN 106B via the target PCell 126B. The multiple configuration parameters can configure zero or one or more radio bearers, including one or more SRBs (e.g., SRB1, SRB2, and / or SRB4) and / or one or more DRBs. For example, UE 102 can exchange RRC messages with T-MN 106B via one or more SRBs (i.e., one or more SRBs of the target PCell) and communicate data with T-MN 106B via one or more DRBs.

[0087] In some implementations, the MN configuration (i.e., S-MN configuration or T-MN configuration) may include a CellGroupConfigIE. The MN configuration may be an RRCReconfiguration message, RRCReconfiguration-IE, or CellGroupConfig IE conforming to 3GPP TS 38.331, or an RRCConnectionReconfiguration message or RRCConnectionReconfiguration-IE conforming to 3GPP TS 36.331. In some implementations, the MN configuration may include configuration within a CellGroupConfig IE, RRCReconfiguration-IE, or RRCConnectionReconfiguration-IE.

[0088] In some implementations, S-MN 104 comprises CU 172 and one or more DU 174, such as Figure 1BAs shown. The one or more DUs 174 can generate an S-MN configuration or at least a portion of an S-MN configuration and send the S-MN configuration (or a portion thereof) to the CU 172. The CU 172 can generate the remaining portion of the S-MN configuration if the DU 174 generates only a portion of the S-MN configuration. In one implementation, the one or more DUs 174 can communicate with the UE 102 via a portion of the S-MN configuration, and the CU 172 can communicate with the UE 102 via the remaining portion of the S-MN configuration. For example, the S-MN configuration (or a portion thereof) generated by the DU 174 may include one or more random access configurations, physical downlink control channel (PDCCH) configurations, PUCCH configurations, etc. The remaining portion of the S-MN configuration generated by the CU 172 may include SRB configurations, DRB configurations, security configurations, and / or measurement configurations. In other implementations, DU 174 may include a cell group configuration (e.g., CellGroupConfigIE) in the S-MN configuration, and CU 172 may include a radio bearer configuration (RadioBearerConfigIE) in the S-MN configuration.

[0089] Similarly, in some implementations, T-MN 106B consists of CU 172 and one or more DU 174, such as Figure 1B As shown, UE 102 can perform a 322A random access procedure on at least one of DU 174(one or more). DU 174 generates configurations (e.g., one or more random access configurations, PDCCH configurations, PUCCH configurations) and sends these configurations to CU 172. CU 172 can include other configurations (e.g., SRB configurations, DRB configurations, security configurations, and / or measurement configurations) in the handover command message. In other implementations, DU 174 can generate a cell group configuration (e.g., CellGroupConfig IE) and send the cell group configuration to CU 172, which in turn can include radio bearer configurations (e.g., RadioBearerConfig IE) and the cell group configuration in the handover command message.

[0090] In some implementations, if S-MN 104 is a gNB, the handover command message can be an RRCReconfiguration message, the handover completion message can be an RRCReconfigurationComplete message, and the RRC reconfiguration message and the RRC reconfiguration completion message can be RRCReconfiguration message and RRCReconfigurationComplete message, respectively.

[0091] In some implementations, if S-MN 104 is an eNB or ng-eNB, the handover command message can be an RRCConnectionReconfiguration message, the handover completion message can be an RRCConnectionReconfigurationComplete message, and the RRC reconfiguration message and the RRC reconfiguration completion message can be RRCConnectionReconfiguration message and RRCConnectionReconfigurationComplete message, respectively.

[0092] Turn now Figure 3B According to DAPS handover scenario 300B, base station 104 performs S-MN operation for UE 102, and base station 106B performs T-MN operation for UE 102, similar to... Figure 3A DAPS switching scene 300A. Although in Figure 3A UE 102 successfully performed a DAPS handover to T-MN 106B before stopping and releasing the power coordination configuration, but in Figure 3B UE 102 failed to perform DAPS handover.

[0093] Initially, UE 102 communicates 302B data with S-MN 104 using S-MN configuration, similar to event 302A. Later, S-MN 104 determines that 304B initiates DAPS handover so that T-MN 106B and UE 102 can communicate, similar to event 304A.

[0094] After determining that DAPS handover is initiated at 304B, S-MN 104 sends a 312B handover request message to T-MN 106B. T-MN 106B generates a 314B handover command message for DAPS handover, which includes the T-MN configuration containing the DAPS power coordination configuration. T-MN 106B sends a 316B handover command message to S-MN 104 in a handover request acknowledgement message, and S-MN 104 transmits a 318B handover command message to UE 102, which are similar to events 312A, 314A, 316A, and 318A, respectively.

[0095] In response to receiving the 318B handover command message, UE 102 applies the 352B DAPS power coordination configuration and continues to communicate with S-MN 104 using the 320B S-MN configuration. At the same time, UE 102 attempts to hand over to T-MN 106B according to the handover command message, which is similar to events 352A and 320A respectively.

[0096] After UE 102 applies the DAPS power coordination configuration 352B or continues communication with S-MN 104 via 320B, UE 102 determines that the DAPS handover failed via 321B, meaning that UE 102 failed to perform a DAPS handover to T-MN 106B using a random access procedure similar to 322A (e.g., for a specific duration). In response to the determination at event 321B, UE 102 stops applying the DAPS power coordination configuration via 354B and releases the DAPS power coordination configuration. In some implementations, RRC controller 152 may send an indication to UE 102's PHY 202 to stop applying the DAPS power coordination configuration. In some implementations, UE 102 releases the T-MN configuration received in event 318B in response to the determination at event 321B.

[0097] If the radio link between UE 102 and S-MN 104 is available (i.e., no radio link failure has occurred on the radio link between UE 102 and S-MN 104), UE 102 can transmit, for example, a 342B failure information message (e.g., FailureInformation) indicating a DAPS handover failure of T-MN 106B to S-MN 104 via SRB1. In some implementations, UE 102 can then perform a 348BRRC re-establishment procedure on cell 126B or another cell having T-MN 106B. If the radio link between UE 102 and S-MN 104 is unavailable, UE 102 does not transmit a failure information message to S-MN 104. To perform the RRC re-establishment procedure, UE 102 transmits an RRC re-establishment request message to T-MN 106B, and T-MN 106B in turn transmits an RRC re-establishment message to UE 102. UE 102 can transmit an RRC re-establishment complete message to T-MN 106B in response to an RRC re-establishment message.

[0098] Because UE 102 has stopped applying the DAPS power coordination configuration in 354B and released the DAPS power coordination configuration, when communicating with S-MN 104 (e.g., when transmitting a 342B failure information message to S-MNB 104) and / or when communicating with T-MN 106B (e.g., during or after performing a 348B RRC reconstruction procedure on T-MN 106B), UE 102 will advantageously not unnecessarily limit its maximum uplink power according to the DAPS power coordination configuration (e.g., CP1 and / or CP2).

[0099] In some implementations, T-MN 106B may release the 356B DAPS power coordination configuration at some point after generating a handover command message or transmitting a handover command message to S-MN 104. In some implementations, if UE 102 fails to successfully hand over to T-MN 106B for a period of time, T-MN 106B may release the DAPS power coordination configuration. In other implementations, T-MN 106B may release the DAPS power coordination configuration in response to the RRC rebuild procedure.

[0100] In some implementations, UE 102 may perform the RRC reconstruction procedure for S-MN 104 via cell 122 or cell 124 instead of for T-MN 106B. Therefore, since UE 102 has stopped applying the DAPS power coordination configuration to 354B and released the DAPS power coordination configuration, UE 102 will not be restricted by the DAPS power coordination configuration parameter CP1 during and after performing the RRC reconstruction procedure for S-MN 104.

[0101] In some implementations, if T-MN 104 is a gNB, the RRC Re-establishment Request message, RRC Re-establishment message, and RRC Re-establishment Complete message can be RRCReestablishmentRequest message, RRCReestablishment message, and RRCReestablishmentComplete message, respectively. If T-MN 106B is an eNB or ng-eNB, the RRC Re-establishment Request message, RRC Re-establishment message, and RRC Re-establishment Complete message can be RRCConnectionReestablishmentRequest message, RRCConnectionReestablishment message, and RRCConnectionReestablishmentComplete message, respectively.

[0102] although Figure 3A and Figure 3BDAPS handover scenarios 300A and 300B concerning UE 102 between two base stations (e.g., base stations 104 and 106B) are described. However, in some implementations, DAPS handover scenarios 300A and 300B can be implemented within a single base station (e.g., S-MN 104) concerning UE 102. In such scenarios, messages exchanged between S-MN 104 and T-MN 106B (e.g., events 312A, 312B, 316A, 316B, 328A) can be omitted, and events performed or otherwise involving T-MN 106B (e.g., events 314A, 314B, 322A, 324A, 326A, 332A, 356A, 356B, 334A, 348B) can be performed or otherwise involve S-MN 104.

[0103] Now for reference Figure 4A According to DAPS PSCell, scenario 400A is changed, base station 104 acts as the MN operation of UE 102, base station 106A acts as the S-SN operation of UE 102, and base station 106B acts as the T-SN operation of UE 102.

[0104] Initially, UE 102 in DC communicates 402A data with MN 104 via PCell 124 using MN configuration, and communicates 402A data with S-SN 106A via PSCell 126A using S-SN configuration.

[0105] Later, MN 104 determines that 404A initiates a DAPS PSCell change involving an SN change (i.e., a DAPS SN addition or change procedure initiated by MN) so that T-SN 106B and UE 102 can communicate via T-PSCell 126B, for example, blindly or in response to the detection of a suitable event (similar to regarding...). Figure 3A The events described, or in response to an SN Change Required message received from S-SN 106A.

[0106] In response to the determination at event 404A, MN 104 sends a 412ASN Addition Request message to T-SN 106B. In response, T-SN 106B generates a 414A T-SN configuration for DAPS PSCell change and sends a 416AT-SN configuration to MN 104 in an SN Addition Request Acknowledge message. In other implementations, in response to the determination at event 404A, MN 104 may send an SN Release Request message (or alternatively, an SN Modification Request message) to S-SN 106A to request S-SN 106A to perform the DAPS PSCell change or continue communication with UE 102, respectively. Then, S-SN 106A may send an SN Release Request Acknowledge message or an SN Modification Request Acknowledge message to MN 104 in response to the SN Release Request message or the SN Modification Request message, respectively. In other embodiments, MN 104 may not send an SN Release Request message (or, alternatively, an SN Modification Request message) to S-SN 106A, allowing S-SN 106A to continue communicating with UE 102 if S-SN 106A is unaware of the DAPS SN change and therefore behaves normally. In yet another embodiment, if MN 104 makes a determination at event 404A in response to a Required SN Change message, MN 104 may send an SN Change Confirm message to S-SN 106A to request S-SN 106A to perform a DAPS PSCell change or continue communicating with UE 102.

[0107] In response to receiving the 416AT-SN configuration from T-SN 106B, MN 104 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 the RRC container message 417A to UE 102. In response to receiving the 417ADAPS power coordination configuration, UE 102 applies the 452ADAPS power coordination configuration. In some implementations, RRC controller 152 may send the DAPS power coordination configuration parameters from the DAPS power coordination configuration to PHY 202 of UE 102, and PHY 202 may then apply the DAPS power coordination configuration parameters. In response to receiving the 417ARRC container message, UE 102 also transmits an RRC container response message 418A to MN 104, which includes an RRC reconfiguration complete message. In some implementations, MN104 may send a 419ASN Reconfiguration Complete message to T-SN 106B in response to an RRC container response message. Events 404A, 412A, 414A, 416A, 417A, 452A, 418A, and 419A are in... Figure 4A This is collectively referred to as DAPS PSCell Change Preparation Process 460A.

[0108] In some implementations, instead of generating the DAPS power coordination configuration at event 417A, MN 104 receives the DAPS power coordination configuration from the SN Add Request Confirmation message from T-SN 106B. In one such implementation, T-SN 106B may generate the DAPS power coordination configuration (e.g., DAPS-PowerCoordinationInfo-r16 IE or DAPS-Configuration-r16 IE) and include it in the T-SN configuration or SN Add Request Confirmation message. In other implementations, S-SN 106A may generate the DAPS power coordination configuration, and the DA sends the DAPS power coordination configuration to MN 104 in a Need for SN Change message or SN Modification Request Confirmation message.

[0109] In some implementations, T-SN 106B may send an SN Add Request Confirmation message or a T-SN configuration indicating that one or more specific DRBs are one or more DAPS PSCell change configurations (e.g., one or more daps-Config fields) to MN 104, which may then include the one or more DAPS PSCell change configurations in an RRC container message. The DAPS PSCell change configuration enables UE 102 to use DAPS (e.g., DAPS 200) for the one or more DAPS bearers to communicate with S-SN 106A (using S-SN configuration) and T-SN 106B (during and after a successful DAPS PSCell change). Therefore, in response to receiving the 417ARRC container message, UE 102 and S-SN 106A continue to communicate with each other via 420A using the S-SN configuration (i.e., in the DC with MN 104), while UE 102 attempts to perform DAPS PSCell changes to T-SN 106B via T-PSCell 126B according to the T-SN configuration.

[0110] When attempting to perform a DAPS PSCell change, UE 102 initiates a random access procedure 422A via T-PSCell 126B and T-SN 106B, for example, by using one or more random access configurations in the T-SN configuration. After T-SN 106B recognizes UE 102 during the random access procedure (e.g., UE 102 succeeds in contention resolution), UE 102 communicates 426A with MN 104 in the DC via PCell 124 and with T-SN 106B via T-PSCell 126B using the configuration in the T-SN configuration, while continuing to communicate with S-SN 106A via PSCell 126A.

[0111] Upon receiving the RRC container response message, MN 104 sends a 428A UEContext Release message to S-SN 106A. S-SN 106A stops communication between 430A and UE 102 in response to or after receiving the UEContext Release message. Alternatively, if S-SN 106A does not receive DL data packets from CN 110 (e.g., S-GW 112 or UPF 162), S-SN 106A stops communication between 430A and UE 102.

[0112] The DAPS PSCell change configuration and / or DAPS power coordination configuration enable UE 102 to continue communicating with S-SN 106A while simultaneously communicating with T-SN 106B. Since UE 102 no longer needs to use DAPS to continue communicating with S-SN 106A after successfully executing the DAPS PSCell change, UE 102 can stop applying the DAPS power coordination configuration in 454A and release the DAPS power coordination configuration. In this way, UE 102 will not unnecessarily limit its maximum uplink power according to the DAPS power coordination configuration when communicating with T-SN 106B, thereby reducing the risk of radio link failure with T-SN 106B. In some implementations, T-SN 106B can transmit an RRC reconfiguration message including a DAPS release indicator to UE 102, for example, via an SRB (e.g., SRB3) between UE 102 and T-SN 106B or via MN 104. In response to an RRC reconfiguration message, UE 102 can stop applying the 454A DAPS power coordination configuration and release the DAPS power coordination configuration. In some implementations, RRC controller 152 can send an indication to UE 102's PHY 202 to stop applying the 454A DAPS power coordination configuration.

[0113] In some implementations, T-SN 106B may also release the 456 ADAPS power coordination configuration because UE 102 no longer needs to use the DAPS power coordination configuration and / or UE 102 has released the DAPS power coordination configuration. That is, T-SN 106B may release the DAPS power coordination configuration after including it in the T-SN configuration in event 414A.

[0114] Following event 454A, UE 102 may transmit an RRC reconfiguration complete message 434A to T-SN 106B via an SRB (e.g., SRB3) between UE 102 and T-SN 106B or via MN 104, and cease communication between UE 102 and S-SN 106A. In some implementations, in response to a DAPS release indicator, the RF chip, receiver, or transceiver of UE 102 used for communication with S-SN 106A during a DAPSPSCell change may enter a low-power mode, a sleep mode, or be completely powered off (if the DAPSPSCell change is an inter-frequency DAPSPSCell change).

[0115] 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 a value thereof) that UE 102 can use for uplink communication with S-SN 106A during a DAPS PSCell change (interchangeably referred to as "CP4"), the maximum total transmission power (or a value thereof) that UE 102 can use for uplink communication with T-SN 106B during a DAPS PSCell change (interchangeably referred to as "CP5"), and / or the uplink power sharing mode used by UE 102 during a DAPS PSCell change (interchangeably referred to as "CP6"). In some implementations, the DAPS power coordination configuration parameters may be included in fields or IEs of the DAPS power coordination configuration.

[0116] After UE 102 (e.g., PHY 202) applies the DAPS power coordination configuration during a DAPS PSCell change, UE 102 (e.g., PHY 202) can determine (or manage or coordinate) its uplink transmission power to S-SN 106A and its uplink transmission power to T-SN 106B according to the DAPS power coordination configuration (e.g., according to 3GPP specification 38.213v16.1.0 or 36.213v16.1.0). In some implementations, if the uplink power sharing mode specified in CP6 is a first mode (e.g., semi-static mode 1), then UE 102 manages its uplink transmission power to not exceed CP4 while transmitting 420A to S-SN 106A, and not exceed CP5 while transmitting 426A to T-SN 106B. In other implementations, if the uplink power sharing mode is the second mode (e.g., semi-static mode 2 or dynamic mode), and the first uplink transmission to S-SN 106A partially or completely overlaps with the second uplink transmission to T-SN 106B, then the uplink transmission power managed by UE 102 for the first and second uplink transmissions does not exceed CP4 and CP5, respectively. If the uplink power sharing mode is the second mode and the first uplink transmission to S-SN 106A does not overlap with the second uplink transmission to T-MN 106B, then the uplink transmission power managed by UE 102 for the first and second uplink transmissions does not exceed the corresponding maximum total transmission power values, except for those included in the DAPS power coordination configuration.

[0117] In some implementations, S-SN 106A and T-SN 106B may provide these corresponding maximum total transmission power values ​​to UE 102 in the respective non-DAPS configuration(s) via SRB 3 or via MN 104. In some implementations, S-SN 106A may send the non-DAPS configuration(s) to UE 102 in a dedicated message (e.g., an RRC reconfiguration message), and T-SN 106B may send the non-DAPS configuration(s) to UE 102 in a dedicated message (e.g., an RRC reconfiguration message). In other implementations, MN 104 may provide the maximum total transmission power values ​​directly to UE 102 in the non-DAPS configuration(s) in a dedicated message (e.g., an RRC reconfiguration message).

[0118] In some implementations, T-SN 106B receives configuration constraints for DAPS PSCell changes from MN 104 in an SN Add Request message. T-SN 106B can generate a DAPS power coordination configuration based on the configuration constraints. In one implementation, MN 104 can generate preferred power coordination configuration parameters and include them in the configuration constraints. In another implementation, MN 104 can receive preferred power coordination configuration parameters from S-SN 106A and include them in the configuration constraints. In any case, T-SN 106B can include such preferred parameters in the DAPS power coordination configuration. In one implementation, MN 104 or S-SN 106A can determine preferred parameters based on the UE capabilities of UE 102. For example, UE capabilities can indicate or include the UE power level and / or one or more DAPS power sharing modes supported by UE 102. If the UE capabilities include or otherwise indicate supported uplink power sharing modes, MN 104 can set the preferred uplink sharing mode to one of the supported uplink power sharing modes. If UE 102 is configured to implement all uplink sharing modes supported by RAN 105, then MN 104 or S-SN 106A can be configured according to the above. Figure 3A The PCP1 parameter and / or at least one of the PCP2 parameters are described to select a specific preferred uplink sharing mode.

[0119] Similarly, in another implementation, MN 104 or T-SN 106B may determine some or all of the DAPS power coordination configuration parameters in the DAPS power coordination configuration based on preferred power coordination configuration parameters and / or the UE capabilities of UE 102. If the UE capabilities include or otherwise indicate supported uplink power sharing modes(s), MN 104 or T-SN 106B may set the uplink sharing mode to one of the supported uplink power sharing modes(s) or the preferred uplink sharing mode provided by MN 104 or S-SN 106A. If UE 102 is configured to implement all uplink sharing modes supported by RAN 105, T-SN 106B may select a specific uplink sharing mode based on PCP1, PCP2, and / or the same preferred power coordination configuration parameters provided by MN 104 or S-SN 106A.

[0120] In some implementations, after successfully completing the 422A random access procedure, UE 102 may begin transmitting UL data PDUs to T-SN 106B via cell 126B, stop transmitting and retransmitting UL data PDUs to S-SN 106A, stop transmitting control signals to S-SN 106A on one or more PUCCHs, stop transmitting new UL data PDUs to S-SN 106A while continuing to retransmit one or more UL data PDUs to S-SN 106A, continue DL communication with S-SN 106A, and / or maintain transmission of control signals to S-SN 106A until event 432A occurs or the DAPS release timer at UE 102 expires, as described above regarding... Figure 3A In some implementations, T-SN 106B may configure a timer value for the DAPS release timer in an RRC reconfiguration message or in the T-SN configuration. In other implementations, MN 104 configures a timer value for the DAPS release timer in an RRC container message. Upon receiving the timer value, UE 102 starts the DAPS release timer to count the timer value. When the DAPS release timer expires, UE 102 stops communication between 436A and S-SN 106A. In other implementations, if MN 104 or T-SN 106B does not provide a timer value to UE 102, UE 102 uses a predetermined timer value.

[0121] In some implementations, T-SN 106B includes multiple configuration parameters in the T-SN configuration to configure radio resources for UE 102 to communicate with T-SN 106B via T-PSCell 126B. These multiple configuration parameters can configure the physical layer, media access control (MAC) layer, and radio link control bearer. DAPS PSCell change configurations can be associated with or specific to a radio bearer (e.g., DRB). For example, T-SN 106B can include DAPS PSCell change configurations in the RB configuration (e.g., RadioBearerConfig IE, DRB-ToAddModList IE, or DRB-ToAddMod IE) in the SN Add Request Confirmation message at event 416A, and MN 104 can include the RB configuration in the RRC container message at event 417A. S-SN 106A can also configure a specific DRB and transmit the RB configuration for that specific DRB to UE 102.

[0122] In some implementations, T-SN 106B may not configure a SCell for UE 102 in the T-SN configuration. T-SN 106B may later transmit one or more RRC reconfiguration messages to UE 102 to configure one or more SCells of T-SN 106B. In response, UE 102 may transmit an RRC reconfiguration complete message to T-SN 106B via T-PSCell 126B or for each SCell configured in the one or more RRC reconfiguration messages.

[0123] In some implementations, the SN configuration (i.e., S-SN configuration or T-SN configuration) may include a CellGroupConfigIE. The SN configuration may be an RRCReconfiguration message, RRCReconfiguration-IE, or CellGroupConfig IE conforming to 3GPP TS 38.331, or an RRCConnectionReconfiguration message or RRCConnectionReconfiguration-IE conforming to 3GPP TS 36.331. In some implementations, the SN configuration may include configuration within a CellGroupConfig IE, RRCReconfiguration-IE, or RRCConnectionReconfiguration-IE.

[0124] If S-SN 106A is a gNB, the T-SN configuration or RRC reconfiguration message can be an RRCReconfiguration message, and the RRC reconfiguration completion message can be an RRCReconfigurationComplete message as defined in 3GPP TS 38.331. If S-SN 106A is an ng-eNB, the T-SN configuration or RRC reconfiguration message can be an RRCConnectionReconfiguration message, and the RRC reconfiguration completion message can be an RRCConnectionReconfigurationComplete message as defined in 3GPP TS 36.331.

[0125] Turn now Figure 4B According to DAPS PSCell, scenario 400B is modified so that base station 104 operates as the MN for UE 102, base station 106A operates as the S-SN, and base station 106B operates as the T-SN for UE 102, similar to... Figure 4A The DAPS PSCell changes scene 400A. Despite... Figure 4A UE 102 successfully performed the DAPS PSCell change to T-SN106B before stopping and releasing the power coordination configuration, but in Figure 4B UE 102 failed to successfully execute the DAPS PSCell change.

[0126] Initially, UE 102 in DC communicates 402B data with MN 104 via PCell 124 using MN configuration, and communicates 402B data with S-SN 106A via PSCell 126A using S-SN configuration, similar to event 402A.

[0127] Subsequently, MN 104, S-SN 106A, and T-SN 106B jointly perform the 460B DAPS PSCell change preparation procedure, similar to event 460A. UE 102 and S-SN 106A continue to communicate with each other via 420B using the S-SN configuration (i.e., in the DC with MN 104), similar to event 420A, while UE 102 attempts to perform a DAPS PSCell change to T-SN 106B via T-PSCell 126B based on the T-SN configuration received in event 460B.

[0128] After UE 102 applies the DAPS power coordination configuration during the SN change process in event 460B, or continues communication between 420B and S-SN 106A using the S-SN configuration, UE 102 determines that the DAPS PSCell change in 421B failed; that is, UE 102 failed to execute the DAPS PSCell change up to T-SN 106B, for example, within a certain time period. In response to the determination at event 421B, UE 102 stops applying the DAPS power coordination configuration in 454B and releases the DAPS power coordination configuration. In some embodiments, RRC controller 152 may send an indication to UE 102's PHY 202 to stop applying the DAPS power coordination configuration. In some embodiments, UE 102 releases the T-SN configuration received in event 460B in response to the determination at event 421B.

[0129] If the radio link between UE 102 and S-SN 106A is available (i.e., no radio link failure has occurred on the radio link between UE 102 and S-SN 106A) and the SRB (e.g., SRB3) between UE 102 and S-SN 106A is unavailable, then UE 102 may, for example, transmit a failure information message (e.g., FailureInformation) to MN 104 at event 452B via the SRB (e.g., SRB1) or transmit an SCG failure information message (e.g., SCGFailureInformation) to MN 104 at event 472B, indicating that the DAPS PSCell change for T-SN 106B has failed. In one implementation, after receiving a failure information message 452B from UE 102 in an RRC container message (e.g., ULInformationTransferMRDC), MN 104 extracts the failure information message from the RRC container message and sends it as 453B to S-SN 106A in an RRC Transfer message. In another implementation, MN 104 does not send the failure information message to S-SN 106A.

[0130] If the radio link between UE 102 and S-SN 106A is available and the SRB (e.g., SRB3) between UE 102 and S-SN 106A is available, UE 102 can transmit a failure information message indicating the failure of the DAPS PSCell change for T-SN 106B to S-SN 106A via the available SRB at event 455B. In response, S-SN 106A can send an SN message (e.g., a request for SN modification message) to MN 104 to notify MN 104 of the DAPS PSCell change failure.

[0131] If the radio link between UE 102 and S-SN 106A is unavailable, UE 102 can transmit a 472B SCG failure message to MN 104 to notify MN 104 of the DAPS PSCell change failure.

[0132] Because UE 102 has stopped applying the DAPS power coordination configuration on 454B and released the DAPS power coordination configuration, UE 102 will advantageously not unnecessarily limit its maximum uplink power according to the DAPS power coordination configuration when communicating with MN 104 (e.g., when transmitting a failure information message or an SCG failure information message) and / or when communicating with S-SN106A (e.g., when transmitting a failure information message).

[0133] In some implementations, T-SN 106B may release the 456B DAPS power coordination configuration after generating or transmitting the T-SN configuration to MN 104. In some implementations, T-SN 106B may release the DAPS power coordination configuration if UE 102 fails to successfully execute the DAPS PSCell change to T-SN 106B for a period of time. In other implementations, MN 104 may release the DAPS power coordination configuration in response to receiving a 452B failure information message or in response to receiving an SN message from S-SN 106A notifying of a failed DAPSPSCell change.

[0134] although Figure 4A and Figure 4BThe text describes DAPS PSCell change scenarios 400A and 400B occurring between two SNs (e.g., base stations 106A and 106B) relating to UE 102. However, in some implementations, DAPS PSCell change scenarios 400A and 400B can be implemented within a single SN (e.g., S-SN 106A) relating to UE 102. In such a scenario, messages exchanged between MN 104 and T-SN 106B (e.g., events 412A, 416A, 419A) can be omitted, and events performed or otherwise involving T-SN 106B (e.g., 414A, 419A, 422A, 426A, 432A, 456A, 434A, 460B) can be performed or otherwise involve S-SN 106A.

[0135] Figure 5A and Figure 5B This corresponds to an RRC reconstruction scenario where UE 102 initiates an RRC reconstruction process with the target base station. In such a scenario, the source base station has provided UE 102 with one or more advanced configurations. As used herein, these advanced configurations enable UE 102 to utilize one or more advanced functions or features deployed to the RAN (e.g., related to 5G, 6G technologies). For example, advanced configurations may correspond to Rel-16 functions conforming to Rel-16 specifications (e.g., 3GPP specifications 38.331v16.0.0 and 36.331v16.0.0) and / or functions from future developments (e.g., Rel-17 specifications, Rel-18 specifications, etc.). However, the target base station does not support these advanced functions and instead supports one or more non-advanced configurations. As used herein, one or more non-advanced configurations enable UE 102 to utilize non-advanced functions (e.g., corresponding to Rel-N, where N is an integer equal to or less than 15), such as those deployed in RAN 105 according to Rel-15 specifications or earlier specifications (e.g., Rel-14 specifications, Rel-13 specifications, etc.). Although Figure 5A and Figure 5B The accompanying description specifically refers to UE 102 of Figure 1 and base stations 104 and 106B, but it should be understood that the following techniques may be implemented by other components and / or systems besides the wireless communication system 100 of Figure 1.

[0136] First refer to Figure 5AAccording to RRC reconstruction scenario 500A, base station 104 operates as the S-MN for UE 102, and base station 106B operates as the T-MN for UE 102. Base station 104 and base station 106B can be the MN in both SC and DC scenarios. UE 102 is in a connected state (e.g., RRC_CONNECTED) and communicates with either S-MN 104 or T-MN 106B of RAN 105.

[0137] Initially, UE 102 communicates 502A data with S-MN 104 using the S-MN configuration, similar to event 302A. In some implementations, the S-MN configuration is a complete and self-contained configuration (i.e., full configuration) to configure (one or more) non-advanced configurations to UE 102.

[0138] Subsequently, S-MN 104 determines, for example, the UE capability to configure said one or more advanced configurations for UE 102 based on the indication of UE 102, such as supporting one or more advanced configurations. In some implementations, said one or more advanced configurations may be considered as "delta" configurations (i.e., one or more configurations that supplement the configurations included in the S-MN configuration). In addition to non-advanced functions or features implemented by the S-MN configuration, said one or more advanced configurations enable UE 102 to utilize advanced functions or features also deployed in RAN 105.

[0139] In response to the determination at event 504A, S-MN 104 transmits message 506A to UE 102, including at least one RRC reconfiguration message comprising the aforementioned advanced configuration(s). In response to each of the aforementioned RRC reconfiguration messages, UE 102 applies the aforementioned advanced configuration(s) at 508A and transmits message 510, "RRC reconfiguration complete," to S-MN 104. As a result, UE 102 and S-MN 104 can communicate with each other using the aforementioned advanced configuration(s).

[0140] After applying the aforementioned advanced configuration(s) or transmitting the RRC reconfiguration complete message, UE 102 determines a failure on the radio link between UE 102 and S-MN 104 (e.g., radio link failure or MCG integrity check failure) in event 512A, and initiates an RRC reconstruction procedure with T-MN 106B in response to this failure. In response to the determination and / or initiation of the RRC reconstruction procedure in event 512A, UE 102 retains the non-advanced configuration in the S-MN configuration in event 514A and releases the aforementioned advanced configuration(s) in event 516A. During the retention of the S-MN configuration, UE 102 reserves an opportunity for S-MN 104 to later configure the aforementioned advanced configuration(s) to UE 102 based on the S-MN configuration if necessary. Subsequently, UE 102 performs the 548A RRC reconstruction procedure with T-MN 106B, similar to event 348B. Because UE 102 released the aforementioned advanced configuration(s) in event 516A as a precaution, UE 102 reduces communication errors between UE 102 and T-MN 106B if T-MN 106B does not support advanced features.

[0141] In some implementations, instead of initiating an RRC reconstruction procedure, UE 102 may initiate an RRC recovery procedure with T-MN 106B in response to a determination that 512A has failed. During the RRC recovery procedure, T-MN 106B may request a full configuration from S-MN 104A, whereby the full configuration includes both the S-MN configuration and the aforementioned advanced configuration(s). Therefore, UE 102 does not need to release the aforementioned advanced configuration(s) from 516A as a precaution, because in such implementations, T-MN 106B supports the aforementioned advanced configuration(s).

[0142] In some implementations, before or during the RRC rebuild process of event 548A, T-MN 106B can receive interface messages (e.g., Retrieve UE Context Response messages or Handover Request messages) including the S-MN configuration from S-MN 104. In one such implementation, in response to receiving an RRC re-establishment request message from UE 102 during the RRC rebuild process, T-MN 106B sends a Retrieve UE Context Request message to S-MN 104, and S-MN 104 in turn sends a Retrieve UE Context Response message including the S-MN configuration to T-MN 106B. Because UE 102 retains the S-MN configuration in event 514A, UE 102 and T-MN 106B can communicate using the S-MN configuration after successfully executing the 548A RRC rebuild process.

[0143] In some implementations, the advanced configuration(s) include one or more Rel-16 configurations. For example, the Rel-16 configuration(s) may include configurations related to features such as Multiple-Input Multiple-Output (MIMO), power saving, sidelinks, Minimized Drive Test (MDT), Self-Optimizing Network (SON), Industrial Internet of Things (IIoT), Ultra-Reliable Low-Latency Case (URLLC), NR Unlicensed (NR-U), DC and / or Carrier Aggregation (CA) enhancements, RRC Positioning, Integrated Access and Backhaul (IAB), DAPS, Conditional Handover (CHO), and / or Conditional PSCell Change (CPC). In another example, the Rel-16 configuration(s) may include one or more Rel-16 physical layer configurations, one or more Rel-16 MAC layer configurations, one or more Rel-16 RLC layer configurations, one or more Rel-16 PDCP configurations, and / or one or more Rel-16 Service Data Adaptation Protocol (SDAP) configurations. UE 102 can release the Rel-16 physical layer configuration(s) to avoid communication problems with T-MN 106B which does not support Rel-16 physical configuration.

[0144] Other examples of the Rel-16 configuration(s) include DAPS power coordination configurations (e.g., daps-PowerCoordinationInfo-r16, daps-Configuration-r16), recorded measurement configurations (e.g., LoggedMeasurementConfiguration-r16-IE), sidelink configurations (e.g., sl-ConfigDedicatedNR-r16, sl-ConfigDedicatedEUTRA-r16, sl-AssistanceConfigEUTRA-r16, or sl-AssistanceConfigNR-r16), IAB configurations (e.g., bap-Config), reference time interest reporting configurations (e.g., referenceTimeInterestReporting-r16), measurement gap configurations (e.g., needForGapsConfigNR), in-device coexistence (IDC) configurations (e.g., idc-AssistanceConfig), Bluetooth configurations (e.g., btNameList-r16), wireless local area network (WLAN) configurations (e.g., wlanNameList-r16), and transmission configurations. Sensor configuration (e.g., sensorNameList-r16), location configuration (e.g., obtainCommonLocationConfig-r16), at least one enabled preference configuration (e.g., drx-PreferenceConfig-r16, maxBW-PreferenceConfig-r16, maxCC-PreferenceConfig-r16, maxMIMO-LayerPreferenceConfig-r16, minSchedulingOffsetPreferenceConfig-r16, releasePreferenceConfig-r16), reference time reporting configuration (e.g., referenceTimeInterestReporting-r16), on-demand SIB request configuration (e.g., onDemandSibRequestConfig), CHO configuration (e.g., conditionalReconfiguration), MCG link fast recovery configuration (e.g., t316), and / or DAPS bearer configuration (e.g., DRB-ToAddMod including daps-Config-r16 with a TRUE value).

[0145] Other examples of the Rel-16 configuration(s) include path loss configurations (e.g., pathlossReferenceRSToAddModList-r16), one or more LTE configurations (e.g., lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16), MIMO configurations (e.g., maxMIMO-Layers-r16), scheduling offset configurations (e.g., minimumSchedulingOffsetK0-r16), and physical resource block (PRB) bundling configurations (e.g., prb-BundlingTypeFor). DCI-Format1-2-r16), (one or more) rate matching group configurations (e.g., rateMatchPatternGroup1ForDCI-Format1-2-r16, rateMatchPatternGroup2ForDCI-Format1-2-r16), (one or more) reference signal configurations (e.g., aperiodicZP-CSI-RS-ResourceSetsToAddModListForDCI-Format1-2-r16, aperiodicZP-CSI-RS-ResourceSetsToReleaseL), istForDCI-Format1-2-r16), (one or more) time domain allocation configurations (e.g., pdsch-TimeDomainAllocationListForDCI-Format1-2-r16, pdsch-TimeDomainAllocationListForDCI-Format1-2-r16, pdsch-TimeDomainAllocationList-v1620, pdsch-TimeDomainAllocationList-r16), configurable field configurations (e.g., configurableFieldForDCI-Format1-2), (one or more) resource allocation configurations (e.g., resourceAllocationType1GranularityForDCI-Format1-2-r16, resourceAllocationForDCI-Format1-2-r16), interleaving configurations (e.g., vrb-ToPRB-InterleaverForDCI-Format1-2-r16), demodulation reference signal configurations (e.g., dmrs-DownlinkForPDSCH-MappingTypeAForDCI-Format1-2-r16),The following are configurations for DCI: dmrs-DownlinkForPDSCH-MappingTypeBForDCI-Format1-2-r16, reference configuration (e.g., referenceOfSLIVForDCI-Format1-2-r16), modulation and coding scheme table configuration (e.g., mcs-TableForDCI-Format1-2-r16), priority indicator configuration (e.g., priorityIndicatorForDCI-Format1-2-r16, priorityIndicatorForDCI-Format1-1-r16), data scrambling configuration (e.g., dataScramblingIdentityPDSCH2-r16), and / or repetition scheme configuration (e.g., repetitionSchemeConfig-r16).

[0146] In some implementations, one or more advanced configurations include one or more Rel-17 configurations. For example, the one or more Rel-17 configurations include configurations for MIMO, power saving, sidelinks, dynamic spectrum sharing, URLLC, NR-U, DC / CA enhancement, IAB, DAPS, conditional SN addition or change (CSAC), multicast, small data transmission, SON, MDT, multiple SIMs, and / or RAN slicing.

[0147] In some implementations, at event 516A, UE 102 may release some of the one or more advanced configurations(s) and retain the remaining advanced configurations(s), instead of releasing all of the one or more advanced configurations(s). For example, UE 102 may retain recorded measurement configurations, sidelink configurations, IAB configurations, multicast configurations, and / or multiSIM configurations. In some implementations, UE 102 may respond to an RRC reconfiguration procedure (e.g., similar to the one described below). Figure 5B The RRC reconfiguration process described in Event 520B releases the retained (one or more) advanced configurations.

[0148] In some implementations, the S-MN configuration includes non-advanced configurations. In one implementation, UE 102 may release at least one non-advanced configuration in the S-MN configuration and retain the remaining non-advanced configurations in event 516A. For example, UE 102 may release configurations in OtherConfig IE and / or OtherConfig-v1540 IE, special cell configurations (e.g., spCellConfig), (one or more) SCell configurations (e.g., sCellConfigCommon and / or sCellConfigDedicated), overheating configurations (e.g., overheatingAssistanceConfig), and / or delay budget reporting configurations (e.g., delayBudgetReportingConfig).

[0149] In some implementations, before determining a failure in the radio link between UE 102 and S-MN 104 at 512A, UE 102 (e.g., in a UE assistance information message) transmits a preferred configuration (or an indication thereof) to S-MN 104. In some implementations, S-MN 104 may transmit an RRC reconfiguration message to UE 102 including an enabled configuration, enabling UE 102 to transmit the preferred configuration to S-MN 104 according to the enabled configuration. In response to receiving the RRC reconfiguration message, UE 102 transmits an RRC reconfiguration complete message to S-MN 104. In event 516A, UE 102 may release the preferred configuration and enable configuration. When releasing the preferred configuration, UE 102 behaves as if UE 102 did not transmit the preferred configuration (or an indication thereof) to S-MN 104.

[0150] In some implementations, the enabling configuration may be a reference time reporting configuration, an IDC configuration, an overheating configuration (e.g., an OverheatingAssistance IE or an overheatingAssistanceConfig field), a power-saving configuration (e.g., a PowerPrefIndicationConfig IE), or an enabling preference configuration. In some implementations, S-MN 104 may optionally transmit the enabling configuration to T-MN 106B in an interface message, and T-MN 106B may optionally release the enabling configuration in response to the RRC re-establishment process at event 548A. After transmitting an RRC re-establishment message to UE 102 at event 548A or receiving an RRC re-establishment complete message from UE 102, T-MN 106B may transmit an RRC reconfiguration message to UE 102 including a second enabling configuration, so that UE 102 can transmit a preferred configuration to T-MN 106B. The second enabling configuration may be the same as or different from the enabling configuration provided by S-MN 104. In response to the RRC reconfiguration message, UE 102 transmits an RRC reconfiguration complete message to T-MN 106B.

[0151] UE 102 may transmit the preferred configuration for various reasons in different scenarios and implementations. In one implementation, UE 102 may transmit the preferred configuration if it is dissatisfied with the configuration parameters in the S-MN configuration used by UE 102 to communicate with S-MN 104 (i.e., the configuration parameters do not meet UE 102's preferences as defined in the preferred configuration). In another implementation, UE 102 may transmit the preferred configuration even if it is satisfied with the configuration parameters, to limit S-MN 104 from changing the configuration parameters to configuration parameters that UE 102 may not prefer. In yet another implementation, UE 102 may transmit the preferred configuration if it has experienced a heating condition (e.g., due to heavy application processing), detected low battery power, or otherwise determined to save power, such as in response to a heating configuration received from S-MN 104. In this way, UE 102 may transmit the preferred configuration for power saving purposes (even if UE 102 has not experienced a heating condition), for heating purposes, or both.

[0152] In some implementations, UE 102 may indicate, in a preferred configuration, a preferred maximum number of SCells, a preferred maximum number of MIMO layers, and / or a maximum aggregate bandwidth supported by the UE capability, which is less than the corresponding maximum number of (one or more) SCells, (one or more) MIMO layers, and / or the maximum aggregate bandwidth.

[0153] In some implementations, UE 102 may indicate in a preferred configuration that UE 102 is experiencing an IDC problem. In other implementations, UE 102 may indicate in a preferred configuration a preferred minimum scheduling offset (e.g., minSchedulingOffsetPreference), release preference (e.g., releasePreference), or reference time information interest (e.g., referenceTimeInfoInterest) for cross-timeslot scheduling.

[0154] Turn now Figure 5B According to the RRC reconstruction scenario 500B, base station 104 performs S-MN operation for UE 102, and base station 106B performs T-MN operation for UE 102, similar to... Figure 5A RRC reconstruction scenario 500A. Although in Figure 5A UE 102 releases the aforementioned (one or more) advanced configurations, but... Figure 5B UE 102 retains the aforementioned advanced configuration(s). UE 102 may then suspend the aforementioned advanced configuration(s) and later resume or release the aforementioned advanced configuration(s), as discussed further below.

[0155] Initially, UE 102 communicates 502B data with S-MN 104 using S-MN configuration, similar to event 502A. Later, S-MN 104 determines that 504B is configured as one or more advanced configurations for UE 102, similar to event 504A.

[0156] In response to the determination of event 504B, S-MN 104 transmits at least one RRC reconfiguration message (506B) including the aforementioned advanced configuration(s), similar to event 506A, to UE 102. In response to each of the aforementioned at least one RRC reconfiguration message, UE 102 applies the aforementioned advanced configuration(s) (508B) and transmits a 510BRRC reconfiguration complete message (510BRRC) to S-MN 104, similar to events 506A and 508A, respectively. As a result, UE 102 and S-MN 104 can communicate with each other using the aforementioned advanced configuration(s).

[0157] After applying the aforementioned advanced configuration(s) or transmitting the RRC reconfiguration complete message, UE 102 determines a failure of 512B on the radio link between UE 102 and S-MN 104, and initiates an RRC reconstruction procedure with T-MN 106B in response to the failure, similar to event 512A. In response to the determination and / or initiation of the RRC reconstruction procedure in event 512B, UE 102 retains the non-advanced configuration in the 514B S-MN configuration, similar to event 514A. However, contrary to event 516A, UE 102 retains the aforementioned advanced configuration(s) of 516B in response to the determination and / or initiation of the RRC reconstruction procedure in event 512B. Subsequently, UE 102 performs the 548B RRC reconstruction procedure with T-MN 106B, similar to event 548A.

[0158] To limit communication errors between UE 102 and T-MN 106B, especially if T-MN 106B does not support advanced features, UE 102 responds by determining the failure in event 512B or initiating an RRC rebuild process and suspending the use of the aforementioned advanced configuration(s) in event 518B.

[0159] After suspending the use of the aforementioned advanced configuration(s) in 518B, UE 102 performs a 520BRRC reconfiguration procedure on T-MN 106B. T-MN 106B can perform the 520BRRC reconfiguration procedure on UE 102 by transmitting an RRC reconfiguration message to UE 102, for example, after transmitting an RRC rebuild message or after receiving an RRC rebuild complete message from UE 102 in event 548B. In response, UE 102 transmits an RRC reconfiguration complete message to T-MN 106B. The RRC reconfiguration message and the RRC reconfiguration complete message can be similar to... Figure 3AThe aforementioned features are described in [the document]. Based on the received RRC reconfiguration message, UE 102 can resume using or release the aforementioned advanced configuration(s)(s) in event 522B. That is, the RRC reconfiguration message can indicate whether T-MN 106B supports one or more advanced features. In some implementations, T-MN 106B can indicate the release of the aforementioned advanced configuration(s)(s) in the RRC reconfiguration message, and UE 102 can release the aforementioned advanced configuration(s)(s) in response to the release indication(s). In some implementations, T-MN 106B can include a release indication for each of the aforementioned advanced configuration(s)(s) in the RRC reconfiguration message. In other implementations, T-MN 106B can include some or all of the release indications for the aforementioned advanced configuration(s)(s) in the RRC reconfiguration message. In other implementations, T-MN 106B can indicate the restoration of the aforementioned advanced configuration(s)(s) in the RRC reconfiguration message, and UE 102 can resume using the aforementioned advanced configuration(s)(s) in response to the restoration indication(s).

[0160] although Figure 5A and Figure 5B RRC reconstruction scenarios 500A and 500B are described between two base stations (e.g., base stations 104 and 106B) relating to UE 102. However, in some implementations, RRC reconstruction scenarios 500A and 500B can be implemented within a single base station (e.g., S-MN 104) relating to UE 102. In such a scenario, UE 102 performs the RRC reconstruction and RRC reconfiguration procedures on S-MN 104 instead of on T-MN 106B.

[0161] Figure 6A This is a flowchart depicting an example method 600A implemented in a user equipment (e.g., UE 102) for applying and later releasing a DAPS power coordination configuration when switching from a source base station (e.g., S-MN104, S-SN 106A) to a target base station (e.g., T-MN 106B, T-SN 106B).

[0162] In block 602A, the user equipment receives a first message from the source base station, which includes a DAPS power coordination configuration for DAPS operation with the source and target base stations (e.g., in either event 318A or 417A). Based on the DAPS operation, the user equipment (e.g., via DAPS 200) can perform a DAPS handover or a DAPS PSCell change. In some implementations, the first message may be a handover command message or an RRC container message.

[0163] In box 604A, the user equipment applies DAPS power coordination configuration to communicate with the source and target base stations (e.g., in either event 352A or 452A). Based on the DAPS power coordination configuration, the user equipment limits its respective maximum total transmitted uplink power when communicating with the source and target base stations.

[0164] In block 606A, the user equipment receives a second message from the target base station indicating the release of DAPS operation (e.g., in either event 332A or 432A). Therefore, the target base station explicitly provides the user equipment with the second message instructing the user equipment to cease communication with the source base station and continue communication with the target base station. In some implementations, the second message may be an RRC reconfiguration message.

[0165] In box 608A, in response to receiving the second message, the user equipment disconnects from the source base station (i.e., stops communication with the source base station), stops applying the DAPS power coordination configuration, and releases the DAPS power coordination configuration (e.g., in any of events 336A, 354A, 436A, 454A). During the release of the DAPS power coordination configuration, when the user equipment communicates with the target base station after successfully performing a DAPS handover or a DAPS PSCell change, it will no longer continue to limit its maximum uplink power according to the DAPS power coordination configuration. Because the DAPS power limit has been removed, the user equipment can increase its uplink power to its maximum uplink power, and the user equipment can reduce the chance of radio link failure with the target base station.

[0166] Figure 6B This is a flowchart depicting another example method 600B implemented in a user equipment (e.g., UE 102) for applying and later releasing a DAPS power coordination configuration during handover from a source base station (e.g., S-MN104, S-SN 106A) to a target base station (e.g., T-MN 106B, T-SN 106B). Although in Figure 6A In response to an explicit message from the target base station (e.g., an RRC reconfiguration message), the user equipment releases the DAPS power coordination configuration, but... Figure 6B After performing a random access procedure on the target base station, UE 102 releases the DAPS power coordination configuration.

[0167] In box 602B, the user equipment receives a first message from the source base station, the first message including a DAPS power coordination configuration for DAPS operation with the source base station and the target station (e.g., in either event 318A or 417A), similar to box 602A.

[0168] In box 604B, the user equipment applies DAPS power coordination configuration to communicate with the source base station and the target base station (e.g., in either event 352A or 452A), similar to box 604A.

[0169] In box 606B, the user equipment performs a random access procedure to the target base station in response to the first message (e.g., in either event 322A or 422A).

[0170] In box 608B, after performing the random access procedure, the user equipment stops applying the DAPS power coordination configuration and releases the DAPS power coordination configuration (e.g., in either event 354A or 454A).

[0171] In box 610B, the user equipment receives a second message (e.g., event 332A or 432A) indicating the release of DAPS operation, similar to box 606A.

[0172] In box 612B, the user equipment disconnects from the source base station in response to the second message (i.e., stops communicating with the source base station) (e.g., in either event 336A or 436A), thereby successfully performing DAPS operation.

[0173] Figure 6C This is a flowchart depicting another example method 600C implemented in a user equipment (e.g., UE 102) for applying and releasing the DAPS power coordination configuration when switching from a source base station (e.g., S-MN104, S-SN 106A) to a target base station (e.g., T-MN 106B, T-SN 106B). Although in Figure 6A and Figure 6B The user equipment successfully performed a DAPS handover or DAPS PSCell change to the target base station, but... Figure 6C The user equipment failed to successfully perform DAPS switching or DAPSPSCell change.

[0174] In box 602C, the user equipment receives a first message from the source base station, the first message including a DAPS power coordination configuration for DAPS operation with the source base station and the target station (e.g., in either event 318B or 460B), similar to boxes 602A and 602B.

[0175] In box 604C, the user equipment applies DAPS power coordination configuration to communicate with the source base station and the target base station (e.g., in either event 352B or 460B), similar to boxes 604A and 604B.

[0176] In box 606C, the user equipment determines that it failed to perform DAPS operation (e.g., radio link failure) (e.g., in either event 321B or 421B). That is, the user equipment failed to perform DAPS handover to the target base station or DAPSPSCell change.

[0177] In box 608C, in response to a failure determination, the user equipment (UE) stops applying the DAPS power coordination configuration and releases the DAPS power coordination configuration (e.g., in either event 354B or 454B). In this way, if, for example, the UE later performs an RRC reconstruction procedure against the source or target source base station, the UE is not limited by the maximum uplink power specified in the DAPS power coordination configuration during and after the RRC reconstruction procedure against the source or target source base station. Because the UE can increase its uplink power beyond the maximum uplink power indicated in the DAPS power coordination configuration, the UE can reduce the chance of radio link failure with the source or target base station.

[0178] Figure 7 It describes the implementation in the RAN (e.g., RAN 105) for providing information about Figure 6A , Figure 6B and Figure 6C The flowchart describes an example method 700 in which a user equipment (e.g., UE 102) provides a DAPS power coordination configuration and later releases the DAPS power coordination configuration.

[0179] In block 702, the RAN transmits a first message to the user equipment (UE) including a DAPS power coordination configuration for DAPS operation with the RAN's source and target base stations (e.g., in any of events 318A, 318B, 417A, 460B). Based on the DAPS operation, the UE (e.g., via DAPS 200) can perform a DAPS handover or a DAPS PSCell change. In some implementations, the first message may be a handover command message or an RRC container message. The first message may also include multiple configuration parameters to configure radio resources, allowing the UE to communicate with the RAN using these configuration parameters during and after a successful DAPS handover or DAPSPSCell change.

[0180] In block 704, after transmitting the first message, the RAN releases the DAPS power coordination configuration (e.g., in any of events 356A, 356B, 456A, 456B). In some embodiments, the RAN releases the DAPS power coordination configuration after transmitting the first and second messages (e.g., an RRC reconfiguration message) to the user equipment to request the user equipment to disconnect from the source base station (e.g., in any of events 332A, 432A). In another embodiment, the RAN releases the DAPS power coordination configuration after transmitting the first message to the user equipment and after receiving a third message (e.g., a failure information message) from the user equipment (e.g., in event 342B). In some embodiments, the RAN may retain multiple configuration parameters provided to the user equipment in the first message.

[0181] Figure 8 This is a flowchart depicting an example method 800 in a user equipment (e.g., UE 102) to release advanced configurations provided by a RAN, such as a source base station (e.g., S-MN104) of the RAN (e.g., RAN 105), in response to initiating an RRC reconstruction process with a target base station (e.g., T-MN 106B) of the RAN.

[0182] In box 802, the user equipment can communicate with the source base station of the RAN using both non-advanced and advanced configurations (e.g., after event 508A). Therefore, the user equipment can use a first set (or more) of functions or features corresponding to the non-advanced configuration and a second set (or more) of functions or features corresponding to the advanced configuration when communicating with the source base station, since the source base station supports both sets (or more) of functions. The first set (or more) of functions or features may be based on the Rel-15 specification or earlier specifications (e.g., Rel-14, Rel-13, etc.) deployed in the RAN, while the second set (or more) of functions or features may be more advanced functions or features, for example, functions or features based on the Rel-16 specification (e.g., 3GPP specifications 38.331v16.0.0 and 36.331v16.0.0) or future specifications (e.g., Rel-17, Rel-18, etc.).

[0183] In block 804, the user equipment initiates an RRC reconstruction procedure (e.g., in event 512A). In some implementations, the user equipment may initiate an RRC reconstruction procedure with the target base station in response to the detection of a radio link failure with the source base station.

[0184] In box 806, the user equipment retains the non-advanced configuration and releases the advanced configuration in response to the RRC reconstruction process (e.g., in either event 514A or 516A). When releasing the advanced configuration, if the target base station does not support one or more advanced functions or features corresponding to the advanced configuration, the user equipment reduces the probability of communication errors between the user equipment and the target base station.

[0185] Figure 9 It is described in the RAN (e.g., RAN 105) to release information about Figure 8 A flowchart describing an example method 900 for advanced configuration configured at a user equipment (e.g., UE 102).

[0186] In box 902, the RAN communicates with the user equipment using both non-advanced and advanced configurations (e.g., after event 510A).

[0187] In box 904, the RAN performs an RRC reconstruction procedure for the UE (e.g., in event 548A). As mentioned above... Figure 8 As discussed herein, in some implementations, a failure of the radio link with the source base station of the RAN can trigger the user equipment to initiate an RRC reconstruction process between the user equipment and the target base station of the RAN.

[0188] In box 906, in response to the RRC reconnection process, the RAN retains the non-advanced configuration and releases the advanced configuration. Accordingly, after reconnecting to the RAN, the user equipment can use the non-advanced configuration to communicate with the RAN and avoids using the advanced configuration when communicating with the RAN. This reduces the probability of communication errors between the user equipment and the target base station, for example, if the target base station does not support one or more advanced functions or features corresponding to the advanced configuration.

[0189] Figure 10 This is a flowchart depicting an example method 1000 implemented in a source base station (e.g., S-MN 104) of a RAN (e.g., RAN 105) to transmit interface messages, excluding advanced configuration, to a target base station (e.g., T-MN 106B) of the RAN. Although Figure 10 An example method 1000 is described that occurs between two base stations (e.g., a source base station and a target base station) with respect to a user equipment (e.g., UE 102), but in some implementations, the example method 1000 may be implemented within a single distributed base station with respect to the user equipment (e.g., between a source DU and a target DU belonging to the same CU).

[0190] In box 1002, the source base station communicates with the user equipment using both non-advanced and advanced configurations (e.g., after event 510A).

[0191] In box 1004, the source base station determines that it includes non-advanced configurations and excludes advanced configurations in the interface message. For example, if the source base station knows in advance that the target base station does not support one or more advanced functions or features corresponding to the advanced configuration, the source base station may exclude the advanced configuration. In some implementations, the interface message may be a Retrieve UE Context Response message or a Handover Request message.

[0192] In box 1006, before or during the RRC reconstruction process between the user equipment and the target base station (e.g., as... Figure 9 As described in box 904, the source base station transmits an interface message to the target base station. Because the interface message does not include advanced configuration, the target base station will not receive the advanced configuration, and therefore, if the target base station does not support the advanced features corresponding to the advanced configuration, it does not need to expend resources to release the advanced configuration.

[0193] Figure 11 It describes the implementation in the target base station (e.g., T-MN 106B) of the RAN (e.g., RAN 105) to release the advanced configuration configured by the source base station (e.g., S-MN 104) at the user equipment (e.g., UE 102).

[0194] In box 1102, the target base station performs an RRC reconstruction procedure for the user equipment (e.g., in...). Figure 9 (as described in box 904) (e.g., in event 548A).

[0195] In box 1104, during the RRC reconstruction process, the target base station receives both the non-advanced configuration and the advanced configuration configured at the user equipment from the source base station. In some implementations, the target base station receives the non-advanced configuration and the advanced configuration before performing the RRC reconstruction process on the user equipment. Thus, although... Figure 10 The source base station does not provide advanced configurations to the target base station, but Figure 11 The source base station provides advanced configurations to the target base station.

[0196] However, the target base station may not support one or more advanced functions or features corresponding to the advanced configuration. Therefore, in block 1106, the target base station retains the non-advanced configuration and releases the advanced configuration in response to the RRC reconstruction process. Thus, if the target base station does not support the advanced functions corresponding to the advanced configuration, the target base station reduces the chance of communication errors between the user equipment and the target base station.

[0197] Figure 12This is a flowchart depicting an example method 1200 implemented in a source base station (e.g., S-MN 104) for generating interface messages, including or excluding advanced configuration, to be sent to a target base station (e.g., T-MN 106B). In this way, the source and target base stations can coordinate whether the target base station receives the advanced configuration to support scenarios where user equipment can release or retain the advanced configuration. Although... Figure 12 An example method 1200 is described that occurs between two base stations (e.g., a source base station and a target base station) with respect to a user equipment, but in some implementations, the example method 1200 may be implemented within a single distributed base station with respect to a user equipment (e.g., between a source DU and a target DU belonging to the same CU).

[0198] In box 1202, the source base station communicates with the user equipment (e.g., UE 102) using non-advanced configuration and advanced configuration (e.g., after event 510A).

[0199] In box 1204, the source base station determines to transmit an interface message, including the context of the user equipment, to the target base station. In some implementations, the interface message may include non-advanced configuration information for the user equipment to communicate with the source base station.

[0200] In box 1206, the source base station determines whether the interface message belongs to a category that enables advanced functionality for its user equipment (i.e., the user equipment retains advanced configuration). If so, the source base station includes the advanced configuration in the interface message (e.g., a handover request message) so that the target base station can communicate with the user equipment using the advanced configuration in response to receiving the interface message. Otherwise, if the source base station determines in box 1210 that the interface message belongs to a category that does not support advanced functionality for its user equipment (i.e., the user equipment has suspended or released advanced configuration), the source base station does not include the advanced configuration in the interface message because the target base station will not need the advanced configuration to communicate with the user equipment.

[0201] In some implementations, the source base station determines that the user equipment can support advanced features or retain advanced configurations during, after, or in response to a handover or RRC recovery process. Alternatively, the source base station determines that the user equipment does not support advanced features or does not retain advanced configurations during, after, or in response to a handover, RRC recovery, or RRC reconstruction process.

[0202] In some implementations, the source base station determines that the user equipment supports certain advanced features (i.e., first advanced features) or retains certain advanced configurations (i.e., first advanced configurations) during, after, or in response to the handover, RRC recovery, or RRC reconstruction process, but does not support other advanced features (i.e., second advanced features) or does not retain other advanced configurations (i.e., second advanced configurations).

[0203] In box 1212, the source base station sends an interface message to the target base station, enabling the target base station to be configured with advanced configuration (after box 1208) or not configured with advanced configuration (after box 1210).

[0204] Figure 13 This is a flowchart depicting an example method 1300 implemented in a target base station (e.g., T-MN 106B) for retaining or releasing advanced configurations received from a source base station (e.g., S-MN 104). In this manner, the target base station can manage advanced configurations to support scenarios where user equipment can release or retain advanced configurations. Although... Figure 13 An example method 1300 is described that occurs between two base stations (e.g., a source base station and a target base station) with respect to a user equipment, but in some implementations, the example method 1300 may be implemented within a single distributed base station with respect to a user equipment (e.g., between a source DU and a target DU belonging to the same CU).

[0205] In box 1302, the target base station receives interface messages from the source base station, including non-advanced configuration and advanced configuration.

[0206] In box 1304, the target base station retains the non-advanced configurations contained in the interface message. Whether the target base station also retains the advanced configurations included in the interface message depends on whether the interface message belongs to a category that enables its user equipment to support advanced functions (i.e., the user equipment retains the advanced configurations).

[0207] In box 1306, if the target base station determines that the interface message belongs to a category that enables advanced features to be supported for its user equipment (i.e., the user equipment retains advanced configuration), then the target base station retains the advanced feature configuration in box 1308. In this way, if the source base station has already provided advanced configuration to the user equipment (e.g., UE 102), the target base station can use the retained advanced configuration to communicate with the user equipment. Otherwise, if the target base station determines in box 1306 that the interface message belongs to a category that does not support advanced features for its user equipment (i.e., the user equipment has suspended or released advanced configuration), then the target base station does not need to retain the advanced configuration to communicate with the user equipment, and therefore releases the advanced configuration in box 1310.

[0208] In some implementations, the target base station determines that the user equipment can support advanced features or retain advanced configurations during, after, or in response to a handover or RRC recovery process. Alternatively, the target base station determines that the user equipment does not support advanced features or retains advanced configurations during, after, or in response to a handover, RRC recovery, or RRC reconstruction process.

[0209] In some implementations, the target base station determines that the user equipment supports certain advanced functions (i.e., first advanced functions) or retains certain advanced configurations (i.e., first advanced configurations) during, after, or in response to the handover, RRC recovery, or RRC reconstruction process, but does not support other advanced functions (i.e., second advanced functions) or does not retain other advanced configurations (i.e., second advanced configurations).

[0210] Next, Figure 14A An example method 1400A for managing power coordination configuration during the execution of the DAPS procedure is illustrated, which can be implemented in a suitable UE (e.g., UE 102).

[0211] In box 1402A, the UE receives power coordination configuration from the RAN for the UE to apply to constrain uplink power when communicating with the source and target cells of the RAN (e.g., events 318A, 318B, 460A, 460B).

[0212] In box 1404A, the UE initiates the DAPS procedure based on the power coordination configuration (e.g., events 320A, 320B, 420A, 420B).

[0213] In block 1406A, in response to the detection of 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 it connects to the target cell during a DAPS procedure. In other implementations, the UE releases the power coordination configuration when it receives an indication from the RAN via the target cell that it wants to release the power coordination configuration. In still other implementations, the UE releases the power coordination configuration when it fails to connect to the target cell during a DAPS procedure.

[0214] Next, Figure 14B An example method 1400B for managing power coordination configuration when performing a DAPS procedure on a UE (e.g., UE 102) is illustrated, which can be implemented in a suitable RAN (e.g., RAN 105).

[0215] In box 1402B, the RAN determines, based on the power coordination configuration, whether the UE should perform the DAPS procedure to connect to the target cell, and disconnects from the source cell after connecting to the target cell (e.g., events 304A, 304B, 460A, 460B).

[0216] In box 1404B, the RAN transmits power coordination configuration to the UE for the UE to use in order to constrain uplink power when communicating with the source cell and the target cell (e.g., events 318A, 318B, 460A, 460B).

[0217] In block 1406B, in response to the detection of 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 it determines that the UE is connected to the RAN via a target cell after performing a DAPS procedure. In other implementations, the RAN causes the UE to release the power coordination configuration when it transmits an indication to the UE via the target cell that the UE wants to release the power coordination configuration.

[0218] Next, Figure 15A An example method 1500A for managing configurations received from a RAN having a first network node and a second network node, which can be implemented in a suitable UE (e.g., UE 102), is illustrated. The first network node supports a first configuration and a second configuration for communicating with the RAN, and the second network node supports the first configuration but does not support the second configuration. In some implementations, the first configuration relates to a first set of functions, and the second configuration relates to a second set of functions that are more advanced than the first set of functions (e.g., DAPS, MIMO, power saving, sidelink, MDT, SON, IIoT, URLLC, NR-U, DC, CA, RRC positioning, IAB, CHO, CPC, etc.).

[0219] In box 1502A, the UE receives a first configuration and a second configuration from the first network node (e.g., events 502A, 502B, 506A, 506B).

[0220] In box 1504A, the UE determines that it wants to re-establish a radio connection with the RAN in order to communicate with the RAN via a second network node (e.g., events 512A, 512B).

[0221] In box 1506A, the UE suspends the second configuration (e.g., events 516A, 518B).

[0222] In box 1508A, the UE communicates with the second network node according to the first configuration (e.g., events 548A, 548B).

[0223] Next, Figure 15BAn example method 1500B for managing the configuration in a first network node operating in a RAN (e.g., RAN 105) is illustrated.

[0224] In block 1502B, the first network node communicates with the UE (e.g., UE 102) via a first radio interface (e.g., block 1202) according to a first configuration associated with a first set of functions and a second configuration associated with a second set of functions. In some implementations, the second set of functions (e.g., DAPS, MIMO, power saving, sidelink, MDT, SON, IIoT, URLLC, NR-U, DC, CA, RRC positioning, IAB, CHO, CPC, etc.) are more advanced than the first set of functions.

[0225] In box 1504B, the first network node determines that the UE wants to communicate with the second network node operating in the RAN via the second radio interface (e.g., box 1204).

[0226] In block 1506B, in a first case, the first network node transmits a first configuration and a second configuration to the second network node in response to determining that a condition is met (e.g., blocks 1208, 1212). In some embodiments, the first network node transmits the first configuration and the second configuration to the second network node when it determines that the second network supports a second set of functions. In other embodiments, the first network node transmits the first configuration and the second configuration to the second network node when it determines that it needs to transmit handover preparation information to the second network node. In still other embodiments, the first network node transmits the first configuration and the second configuration to the second network node when it determines that it needs to transmit an indication to the second network node that the UE wants to restore radio connectivity through a second radio interface.

[0227] In block 1508B, in the second case, the first network node, in response to determining that the condition is not met, transmits the first configuration to the second network node and prevents the second configuration from being transmitted to the second network node (e.g., blocks 1210, 1212). In some embodiments, when the first network node determines that it needs to transmit an indication to the second network node that the UE wants to re-establish the radio connection through the second radio interface, the first network node transmits the first configuration to the second network node and prevents the second configuration from being transmitted to the second network node.

[0228] Next, Figure 15C An example method 1500C is illustrated for managing the configuration in a second network node operating in a RAN (e.g., RAN 105) that also includes a first network node.

[0229] In block 1502C, the second network node performs a process (e.g., events 548A, 548B) to re-establish a radio connection with a UE (e.g., UE 102) that previously communicated with the first network node via the first radio interface, based on a first configuration associated with the first set of functions and a second configuration associated with the second set of functions. In some implementations, the second set of functions (e.g., DAPS, MIMO, power saving, sidelink, MDT, SON, IIoT, URLLC, NR-U, DC, CA, RRC positioning, IAB, CHO, CPC, etc.) is more advanced than the first set of functions.

[0230] In box 1504C, the second network node receives a first configuration and a second configuration from the first network node (e.g., box 1302).

[0231] In block 1506C, in a first case, the second network node retains the first and second configurations in response to determining that a condition is met (e.g., block 1308). In some embodiments, the second network node retains the first and second configurations when it determines that the second network supports the second set of functions. In other embodiments, the second network node retains the first and second configurations when it determines that the first network node has transmitted handover preparation information to the second network node. In still other embodiments, the second network node retains the first and second configurations when it determines that the first network node has transmitted an indication to the second network node that the UE wants to restore radio connectivity through the second radio interface.

[0232] In block 1508C, in the second case, the second network node retains the first configuration and releases the second configuration in response to determining that the condition is not met (e.g., block 1310). In some implementations, when the second network node determines that the first network node has transmitted to the second network node an instruction from the UE to re-establish the radio connection via the second radio interface, the second network node retains the first configuration and releases the second configuration.

[0233] The following descriptions can be applied to the descriptions above.

[0234] User equipment (e.g., UE 102) in which the technologies of this disclosure can be implemented can be any suitable device capable of wireless communication, such as a smartphone, tablet, laptop, mobile game console, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle, or other personal media device such as a smartwatch, wireless hotspot, femtocell, or broadband router. Furthermore, in some cases, the user equipment can be embedded in electronic systems, such as a head unit in a vehicle or an advanced driver assistance system (ADAS). Further still, the user equipment can operate as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user equipment may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0235] In this disclosure, certain embodiments are described as including logic or multiple components or modules. A module can be a software module (e.g., code or machine-readable instructions stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing a specific operation and can be configured or arranged in a particular manner. A hardware module may include dedicated circuitry or logic permanently configured (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), digital signal processor (DSP), etc.) to perform a specific operation. A hardware module may also include programmable logic or circuitry (e.g., encapsulated within a general-purpose processor or other programmable processor) that is temporarily configured by software 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 based on cost and time considerations.

[0236] When implemented in software, these technologies can be provided as part of an operating system, libraries used by multiple applications, specific software applications, etc. The software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0237] Upon reading this disclosure, those skilled in the art will understand the additional and alternative structural and functional designs for addressing mobility between base stations using the principles disclosed herein. Therefore, while specific embodiments and applications have been shown and described, it should be understood that the disclosed embodiments are not limited to the precise constructions and components disclosed herein. Various modifications, alterations, and variations can be made to the arrangement, operation, and details of the methods and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims, as will be apparent to those skilled in the art.

[0238] Example 1. A method in a user equipment (UE) for managing a power coordination configuration during a dual-activity protocol stack (DAPS) procedure, the method comprising: receiving a power coordination configuration from a radio access network (RAN) by processing hardware for the UE to apply to constrain uplink power while communicating with a source cell and a target cell of the RAN; initiating the DAPS procedure by the processing hardware according to the power coordination configuration; and releasing the power coordination configuration by the processing hardware in response to detecting a triggering condition.

[0239] Example 2. According to the method of Example 1, wherein the triggering condition includes: connecting to the target cell during the execution of the DAPS procedure.

[0240] Example 3. The method according to Example 1 or 2, wherein the triggering condition includes receiving an indication from the RAN via the target cell that the UE wants to release the power coordination configuration.

[0241] Example 4. The method according to Example 1, wherein the triggering condition includes: failing to connect to the target cell during the execution of the DAPS procedure.

[0242] Example 5. The method according to Example 4 further includes: re-establishing a radio connection between the UE and the RAN.

[0243] Example 6. The method according to Example 4 or 5 further includes: transmitting an indication to the RAN via the source cell that the UE failed to connect to the target cell.

[0244] Example 7. The method according to any one of the preceding examples, wherein: the DAPS process is a DAPS switching process.

[0245] Example 8. According to the method of Example 7, wherein the DAPS handover process causes the UE to switch between: (i) a first MN and a second MN when the UE is operating in an SC; (ii) a first SN and a second SN when the UE is operating in a DC; (iii) a source cell of the MN and a target cell of the MN when the UE is operating in an SC; or (iv) a first distributed element (DU) of a distributed base station and a second DU of the distributed base station.

[0246] Example 9. The method according to any one of Examples 1-6, wherein: the DAPS process is a DAPS primary / secondary cell (PSCell) change process.

[0247] Example 10. According to the method of Example 9, wherein the DAPS PSCell change process causes the UE to switch between: (i) a first SN and a second SN; (ii) a source cell of the SN and a target cell of the SN; or (iii) a first distributed unit (DU) of the distributed base station and a second DU of the distributed base station.

[0248] Example 11. A method in a RAN for managing a power coordination configuration when performing a DAPS procedure on a UE, the method comprising: determining, by processing hardware, 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; transmitting the power coordination configuration to the UE by the processing hardware for the UE to apply to constrain uplink power when communicating with the source cell and the target cell; and releasing the power coordination configuration in response to detecting a triggering condition.

[0249] Example 12. The method according to Example 11, wherein the triggering condition includes: determining that the UE connects to the RAN via the target cell after performing the DAPS procedure.

[0250] Example 13. The method according to Example 11 or 12, wherein the triggering condition includes: transmitting an indication to the UE via the target cell that the UE wants to release the power coordination configuration.

[0251] Example 14. The method according to any one of Examples 11-13, wherein transmitting the power coordination configuration includes transmitting the power coordination configuration to the UE in a handover command message or an RRC container message.

[0252] Example 15. The method according to any one of Examples 11-14 further includes: after transmitting the power coordination configuration, the processing hardware releases the power coordination configuration at the RAN.

[0253] Example 16. The method according to Example 15, wherein releasing the power coordination configuration includes releasing the power coordination configuration in response to receiving a failure information message from the UE.

[0254] Example 17. The method according to any one of Examples 11-16, wherein: the DAPS process is a DAPS switching process.

[0255] Example 18. The method according to any one of Examples 11-16, wherein: the DAPS process is a DAPS primary / secondary cell (PSCell) change process.

[0256] Example 19. A method in a user equipment (UE) for managing configurations received from a radio access network (RAN) having a first network node and a second network node, the first network node supporting a first configuration and a second configuration for communicating with the RAN, the second network node supporting the first configuration but not supporting the second configuration, the method comprising: receiving the first configuration and the second configuration from the first network node by processing hardware; determining by the processing hardware that the UE wants to re-establish a radio connection with the RAN to communicate with the RAN via the second network node; suspending the second configuration by the processing hardware; and communicating with the second network node by the processing hardware according to the first configuration.

[0257] Example 20. The method according to Example 19, wherein suspending the second configuration includes: releasing the second configuration by the processing hardware before re-establishing the radio connection with the second network node.

[0258] Example 21. The method according to Example 20, wherein releasing the second configuration includes: in response to detecting a communication failure with the first network node, the processing hardware releases the second configuration.

[0259] Example 22. The method according to Example 20, wherein releasing the second configuration includes: in response to determining that a radio connection with the second network node is to be re-established, the processing hardware releases the second configuration.

[0260] Example 23. The method according to any one of Examples 19-22 further includes: after re-establishing the radio connection with the second network node, the processing hardware communicating with the second network node using the first configuration.

[0261] Example 24. The method according to Example 19, wherein pausing the second configuration includes: retaining the second configuration by the processing hardware before re-establishing the radio connection with the second network node; and pausing the second configuration by the processing hardware after re-establishing the radio connection with the second network node.

[0262] Example 25. The method according to any one of Examples 19-24, wherein determining that the UE wants to re-establish a radio connection with the second network node occurs after a communication failure with the first network node is detected.

[0263] Example 26. The method according to Example 25, wherein suspending the second configuration includes: retaining the second configuration by the processing hardware before re-establishing the radio connection with the second network node; and suspending the second configuration by the processing hardware in response to detecting the communication failure.

[0264] Example 27. The method according to any one of Examples 24-26 further includes: receiving a reconfiguration message from the second network node by the processing hardware, indicating that the second network node supports the second configuration; and restoring the second configuration in response to the processing hardware determining that the reconfiguration message includes an indication to restore the second configuration.

[0265] Example 28. The method according to any one of Examples 24-26 further includes: receiving a reconfiguration message from the second network node by the processing hardware; and releasing the second configuration in response to the processing hardware determining that the reconfiguration message includes an indication to release the second configuration.

[0266] Example 29. The method according to any one of Examples 19-28, wherein the second configuration includes a power coordination configuration.

[0267] Example 30.UE, which includes processing hardware and is configured to implement the method according to any one of Examples 1-10 or 19-29.

[0268] Example 31. A method for managing configurations in a first network node operating in a radio access network (RAN), the method comprising: communicating with a user equipment (UE) via a first radio interface by processing hardware based on a first configuration associated with a first set of functions and a second configuration associated with a second set of functions; determining by the processing hardware that the UE intends to communicate with a second network node operating in the RAN via a second radio interface; and in a first case, transmitting the first configuration and the second configuration to the second network node in response to determining that a condition is met, and in a second case, transmitting the first configuration to the second network node and preventing the second configuration from being transmitted to the second network node in response to determining that the condition is not met.

[0269] Example 32. The method according to Example 31, wherein determining that the condition is met includes: determining that the second network supports the second set of functions.

[0270] Example 33. According to the method of Example 31, determining that the condition is met includes: determining that the first network node is to transmit handover preparation information to the second network node.

[0271] Example 34. The method according to Example 31, wherein determining that the condition is met includes: determining that the first network node is to transmit to the second network node an indication that the UE is to resume radio connection through the second radio interface.

[0272] Example 35. The method according to Example 31, wherein determining that the condition is not met includes: determining that the first network node is to transmit to the second network node an indication that the UE is to re-establish a radio connection through the second radio interface.

[0273] Example 36. The method according to any one of Examples 31-35, wherein the second set of functions is more advanced than the first set of functions.

[0274] Example 37. The method according to Example 36, wherein the second set of functions includes DAPS functionality.

[0275] Example 38. A method for managing configuration in a second network node operating in a radio access network (RAN) that also includes a first network node, the method comprising: performing, by processing hardware, a process for re-establishing a radio connection via a second radio interface with a user equipment (UE) that previously communicated with the first network node via a first radio interface, based on a first configuration associated with a first set of functions and a second configuration associated with a second set of functions; receiving the first configuration and the second configuration from the first network node; and in a first case, retaining the first configuration and the second configuration in response to determining that a condition is met, and in a second case, retaining the first configuration and releasing the second configuration in response to determining that the condition is not met.

[0276] Example 39. The method according to Example 38, wherein determining that the condition is met includes: determining that the second network supports the second set of functions.

[0277] Example 40. The method according to Example 38, wherein determining that the condition is met includes: determining that the first network node has transmitted handover preparation information to the second network node.

[0278] Example 41. The method according to Example 38, wherein determining that the condition is met includes: determining that the first network node has transmitted to the second network node an indication that the UE wants to restore radio connectivity through the second radio interface.

[0279] Example 42. The method according to Example 38, wherein determining that the condition is not met includes: determining that the first network node has transmitted to the second network node an indication that the UE wants to re-establish the radio connection through the second radio interface.

[0280] Example 43. The method according to any one of Examples 38-42, wherein the second set of functions is more advanced than the first set of functions.

[0281] Example 44. The method described in Example 44, wherein the second set of functions includes DAPS functionality.

[0282] Example 45. A base station including processing hardware and configured to implement the method according to any one of Examples 11-18 or 31-44.

Claims

1. A method in a user equipment (UE) for managing configurations received from a radio access network (RAN) having a first network node and a second network node, wherein the first network node supports a first configuration and a second configuration for communicating with the RAN, and the second network node supports the first configuration but does not support the second configuration, the method comprising: The UE receives from the first network node (i) the first configuration, which configures the UE to utilize a first set of functions, and (ii) the second configuration, which supplements the first configuration and configures the UE to utilize a second set of additional functions, including at least one of a sidelink configuration or a reference time report configuration. The UE communicates with the first network node according to the first configuration; The UE determines that it wants to re-establish a radio connection with the RAN via the second network node; The second configuration is released by the UE; and According to the first configuration, the UE communicates with the second network node.

2. The method of claim 1, wherein the UE releases the second configuration before re-establishing the radio connection with the second network node.

3. The method of claim 2, wherein in response to detecting a communication failure with the first network node, the UE releases the second configuration.

4. The method of claim 2, wherein in response to determining that the UE wants to rebuild the radio connection with the second network node, the UE releases the second configuration.

5. The method according to any one of claims 1-4, further comprising: After the radio connection with the second network node is re-established, the UE communicates with the second network node using the first configuration.

6. The method according to any one of claims 1-4, wherein after the UE detects a communication failure with the first network node, the UE determines that the UE wants to re-establish a radio connection with the second network node.

7. A UE comprising processing hardware and configured to implement the method according to any one of claims 1-6.

8. A method for managing configuration in a first network node operating in a radio access network (RAN), the method comprising: According to (i) a first configuration that configures the UE to utilize a first set of functions and (ii) a second configuration that supplements the first configuration and configures the UE to utilize a second set of additional functions including at least one of a sidelink configuration or a reference time report configuration, the first network node communicates with the user equipment UE. The first network node determines that the UE needs to communicate with the second network node operating in the RAN; and In response to determining that the second network node does not support the second set of additional functions, the first configuration is transmitted to the second network node and the second configuration is prevented from being transmitted to the second network node.

9. The method of claim 8, wherein determining that the second network node does not include the second set of additional functions includes at least one of the following: It is determined that the first network node needs to transmit handover preparation information to the second network node; or It is determined that the first network node needs to transmit an instruction from the second network node that the UE wants to restore the radio connection.

10. A method for managing configuration in a second network node operating in a radio access network (RAN), the radio access network further comprising a first network node, the method comprising: The process of re-establishing a radio connection with the UE, which previously communicated with the first network node, is performed by the second network node according to (i) a first configuration that configures the user equipment UE to utilize a first set of functions and (ii) a second configuration that supplements the first configuration and configures the UE to utilize a second set of additional functions including at least one of a sidelink configuration or a reference time report configuration. The second network node receives the first configuration and the second configuration from the first network node; In response to the determination that the conditions are met, the first configuration and the second configuration are retained; and In response to the determination that the condition is not met, the first configuration is retained and the second configuration is released.

11. The method of claim 10, wherein determining that the condition is satisfied comprises at least one of the following: It is determined that the second network supports the second set of functions; It is determined that the first network node has transmitted handover preparation information to the second network node; or It is determined that the first network node transmitted an instruction from the second network node that the UE wanted to restore the radio connection.

12. A base station comprising processing hardware and configured to implement the method according to any one of claims 8-11.

Images