Method and apparatus for managing conditional configuration upon addition or release of a bearer

Abstract

To manage the configuration, the UE receives (702), by processing hardware and from a radio access network, RAN, a conditional configuration information including i) a conditional configuration related to a base station operating in the RAN, and ii) a condition to be fulfilled before the UE applies the configuration. The UE receives (704), by processing hardware and from the RAN, a message including an indication that the UE is to add, modify, or release a radio bearer (RB), and in response to receiving the message, determines, by the processing hardware, to ignore (706) the conditional configuration.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 62 / 975,902, filed February 13, 2020, entitled “Managing a Conditional Configuration Upon Addition or Release of a Bearer,” the entire disclosure of which is expressly incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to wireless communications, and more specifically, to managing conditional configurations when adding, modifying, or releasing radio bearers to a user equipment (UE). Background Technology

[0004] The purpose of providing this background description is to present the overall context of this disclosure. To the extent described in this background section, the work of the currently named inventors, and aspects of the description that may not conform to the prior art at the time of submission, are neither explicitly nor implicitly acknowledged as prior art to this disclosure.

[0005] 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, also known as the 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) and Data Radio Bearers (DRBs) to the Radio Resource Control (RRC) sublayer. 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.

[0006] 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), and 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 logged 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 uses only the low-level resources of MN can be called an MCG DRB, a DRB that uses only the low-level resources of SN can be called an SCG DRB, and a DRB that uses low-level resources of MCG or SCG can be called a separate DRB.

[0007] In some scenarios, a UE can simultaneously utilize the resources of multiple RAN nodes (e.g., components of a base station or distributed base station) interconnected via backhaul. 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 primary node (MN) covering the primary cell (PCell), while another base station operates as the secondary node (SN) covering the primary secondary cell (PSCell). The UE communicates with the MN (via the PCell) and the SN (via the PSCell). In other scenarios, the UE utilizes 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 procedure.

[0008] 3GPP Technical Specifications (TS) 36.300 and 38.300 describe the procedures for handover (or synchronous reconfiguration) scenarios. These procedures involve message passing between RAN nodes (e.g., RRC signaling and preparation), which typically results in delays, further increasing the likelihood of handover. These procedures do not involve conditions associated with the UE and can be referred to as “immediate” handover procedures. 3GPP documents R2-1914640 and R2-1914834 propose procedures for conditional handover scenarios.

[0009] 3GPP specification TS 37.340 (v16.0.0) describes the procedures for a UE to add or change a serial number (SN) in a DC scenario. These procedures involve message passing between radio access network (RAN) nodes (e.g., RRC signaling and preparation). This message passing typically results in delays, which in turn increases the likelihood of the SN addition or SN change procedure failing. These procedures do not involve conditions checked at the UE and can be referred to as “immediate” SN addition and SN change procedures.

[0010] In both single-connectivity (SC) and DC operations, the UE can also perform a handover procedure to switch from one cell to another. Depending on the scenario, the UE can switch from a cell of a first base station to a cell of a second base station, or from a cell of a first distributed element (DU) of a base station to a cell of a second DU of the same base station. 3GPP specifications 36.300v16.0.0 and 38.300v16.0.0 describe a handover procedure involving several steps (RRC signaling and preparation) between RAN nodes, which introduces delays during the handover process and thus increases the risk of handover failure. This procedure does not involve conditions checked at the UE and can be referred to as an "immediate" handover procedure.

[0011] Recently, "conditional" procedures (i.e., conditional SN or PSCell addition / change and conditional handover) have been considered for SN or PSCell addition / change and handover. Unlike the "immediate" procedures discussed above, these procedures do not add or change the SN or PSCell, or perform a handover, until the UE determines that a condition is met. As used herein, the term "condition" can refer to a single detectable state or event (e.g., a specific signal quality metric exceeding a threshold), or a logical combination of such states or events (e.g., "condition A and condition B," or "(condition A or condition B) and condition C," etc.).

[0012] To configure the conditional process, the RAN provides the UE with conditions and configuration (e.g., a set of random access preambles, etc.) that, when met, enable the UE to communicate with the appropriate base station or via the appropriate cell. For example, for the conditional addition of a base station as an SN or a candidate cell as a PSCell, the RAN provides the UE with the conditions to be met before the UE can add the base station as an SN or the candidate cell as a PSCell, and the configuration to enable the UE to communicate with the base station or PSCell after the conditions are met.

[0013] In some scenarios, the UE receives a conditional configuration as a fully configured set from a first base station. A UE with a conditional configuration can add, modify, or release a Data Radio Bearer (DRB) in response to an RRC message (e.g., RRC reconfiguration) received from the first base station. For example, a UE with a conditional configuration adds a new DRB in response to an RRC message (e.g., RRC reconfiguration) received from the first base station. Later, the UE detects the conditions for connecting to a candidate cell configured by the conditional configuration. In response to this detection, the UE connects to the candidate cell and communicates with a second base station on the candidate cell using the conditional configuration. However, the conditional configuration does not include any configuration for the new DRB, requiring the UE to release the new DRB. Ultimately, due to the release of the new DRB, any service on the new DRB is disconnected. Summary of the Invention

[0014] According to the technology disclosed herein, the UE receives conditional configurations associated with the base station for procedures such as conditional handover (CHO), conditional PSCell addition or change (CPAC), or conditional SN addition or change (CSAC). When the RAN determines to add, modify, or release a DRB, the UE can determine whether it should release the conditional configuration or retain it.

[0015] In some cases, the UE receives an RRC reconfiguration message from the MN and / or SN with an explicit indication that the UE wants to release a conditional configuration. The same RRC reconfiguration may include an indication that the UE wants to add, modify, or release a DRB. In other implementations, the RAN provides these two indications in two corresponding messages, each of which may be an RRC reconfiguration message.

[0016] In other cases, the UE receives an instruction regarding whether it wants to add, modify, or release a DRB, and in view of this instruction, uses it as an implicit indication that the UE should retain or release the conditional configuration based on whether the conditional configuration is still valid. For example, if the instruction is to add or modify a DRB, the UE can determine that the conditional configuration is invalid and thus can release the conditional configuration. If the instruction is to release a DRB, the UE can determine that the conditional configuration is valid and therefore can retain the conditional configuration.

[0017] In other cases, the UE receives an RRC reconfiguration message with a second conditional configuration from the MN and / or SN. The same RRC reconfiguration may include an indication from the UE to add, modify, or release a DRB. In other implementations, the RAN provides these two indications in two corresponding messages, each of which may be an RRC reconfiguration message. In some implementations, the second conditional configuration may be a complete and self-contained configuration (i.e., a full configuration). On the other hand, in other cases, the second conditional configuration may include an "incremental" configuration, or one or more configurations that extend a previously received conditional configuration. In this case, the UE 102 may communicate with the MN and / or SN using the incremental conditional configuration and the first conditional configuration. The UE then updates the first conditional configuration with the second conditional configuration, which may include releasing the first conditional configuration and storing the second conditional configuration. In some implementations, the UE compares the second conditional configuration with the first conditional configuration to determine if there is any inconsistency between the first and second conditional configurations. If there is an inconsistency between the first and second conditional configurations, the UE may release the first conditional configuration and store the second conditional configuration. If the configuration of the second condition is consistent with the configuration of the first condition, the UE can retain the configuration of the first condition.

[0018] Example embodiments of these technologies are methods for configuration management in a UE. This method can be executed by processing hardware and includes receiving conditional configuration information from the RAN, the conditional configuration information including (i) conditional configurations associated with a base station operating in the RAN, and (ii) conditions to be satisfied before the UE applies the conditional configuration. The method also includes receiving a message from the RAN including an indication that the UE wants to add, modify, or release a radio bearer (RB), and in response to receiving the message, determining to ignore the conditional configuration.

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

[0020] Another example embodiment of these technologies is a method for configuring a UE in a RAN. This method can be implemented using processing hardware and includes transmitting to the UE (i) a conditional configuration associated with a base station operating in the RAN, and (ii) conditions to be satisfied by the UE before applying the conditional configuration during the conditional process. The method also includes receiving an interface message from the core network (CN), determining, in response to the interface message, to add, modify, or release a radio bearer (RB), and transmitting a message including an indication that the UE intends to add, modify, or release an RB.

[0021] Another example embodiment of these technologies is a RAN that includes processing hardware and is configured to perform the methods described above. Attached Figure Description

[0022] Figure 1A This is a block diagram of an example system in which the radio access network (RAN) and user equipment can implement the techniques of this disclosure to manage conditional processes associated with a master node (MN) or a secondary node (SN);

[0023] Figure 1B This is another block diagram of an example system in which the radio access network (RAN) and user equipment can implement the techniques of this disclosure to manage conditional processes associated with the MN or SN;

[0024] Figure 1C This is a block diagram of an example base station, where centralized units (CUs) and distributed units (DUs) can be... Figure 1A or Figure 1B Operating within the system;

[0025] Figure 2 This is a block diagram of an example protocol stack. Based on this protocol stack, Figure 1A The UE communicates with the base station;

[0026] Figure 3A This is a message passing illustration of an example scenario based on the technology disclosed herein, wherein, Figure 1A SN via Figure 1A The MN of 1B initiates a conditional PSCell Add or Change (CPAC) configuration procedure to configure the candidate secondary node (C-SN) configuration, and the UE ignores the C-SN configuration in response to the addition, modification or release of the data radio bearer (DRB).

[0027] Figure 3B It is similar to Figure 3A The example scenario is illustrated in the message passing diagram, but in this case, the SN directly initiates the CPAC configuration process to the UE;

[0028] Figure 3C Is with Figure 3A and 3B The message passing diagram is similar to the example scenario, but in this case, in response to the addition, modification or release of the DRB, the base station configures the UE to release the C-SN configuration;

[0029] Figure 3D It is similar to Figure 3A and 3B Another example of the scenario is illustrated in the message passing diagram, but in response to the addition, modification, or release of the DRB, the base station configures the UE to release the C-SN configuration;

[0030] Figure 3E It is similar to Figure 3A and 3B Another example of the scenario is illustrated in the message passing diagram, but in response to the addition, modification, or release of the DRB, the base station configures the UE to release the C-SN configuration;

[0031] Figure 3F It is similar to Figure 3A and 3B The example scenario is illustrated in the message passing diagram, but in response to the addition, modification or release of the DRB, the base station updates the first C-SN configuration in the UE with the second C-SN configuration;

[0032] Figure 3G It is similar to Figure 3A and 3B Another example of the scenario is illustrated in the message passing diagram, but in this case, in response to the addition, modification or release of the DRB, the base station updates the first C-SN configuration in the UE with the second C-SN configuration;

[0033] Figure 3H It is similar to Figure 3A and 3B Another example of the scenario is illustrated in the message passing diagram, but in this case, in response to the addition, modification or release of the DRB, the base station updates the first C-SN configuration in the UE with the second C-SN configuration;

[0034] Figure 4A This is a message passing illustration of an example scenario based on the technology disclosed herein, wherein Figure 1A Alternatively, the MN of 1B may initiate a Conditional SN Addition or Modification (CSAC) configuration procedure to configure the candidate secondary node (C-SN) configuration, and the UE may ignore the C-SN configuration in response to the addition, modification or release of the DRB.

[0035] Figure 4B Is with Figure 4A The message passing diagram is similar to the example scenario, but in this case, in response to the addition, modification or release of the DRB, the base station configures the UE to release the C-SN configuration;

[0036] Figure 4C It is similar to Figure 4A The example scenario is illustrated in the message passing diagram, but in response to the addition, modification or release of the DRB, the base station updates the first C-SN configuration in the UE with the second C-SN configuration;

[0037] Figure 5A This is a message passing illustration of an example scenario based on the technology disclosed herein, wherein Figure 1AAlternatively, the MN of 1B may initiate a conditional handover (CHO) procedure to configure the candidate primary node (C-MN) configuration, and the UE may ignore the C-MN configuration in response to the addition, modification or release of the DRB.

[0038] Figure 5B It is similar to Figure 5A The example scenario illustrates message passing, but in response to the addition, modification, or release of the DRB, the base station configures the UE to release the C-MN configuration;

[0039] Figure 5C It is similar to Figure 5A The example scenario is illustrated in the message passing diagram, but in response to the addition, modification or release of the DRB, the base station updates the first C-MN configuration in the UE with the second C-NN configuration;

[0040] Figure 6A This is a message passing illustration of an example scenario based on the technology disclosed herein, wherein Figure 1A Alternatively, the MN of 1B initiates a CHO procedure to configure the candidate primary cell (C-PCell) configuration within the C-MN, where the C-MN is the MN, and the UE ignores the C-MN configuration in response to the addition, modification, or release of the DRB.

[0041] Figure 6B Is with Figure 6A The message passing diagram is similar to that of the example scenario, but in this case, the base station configures the UE to release the C-MN configuration in response to the addition, modification or release of the DRB.

[0042] Figure 6C It is similar to Figure 6A The example scenario illustrates message passing, but in response to the addition, modification, or release of the DRB, the base station updates the first C-MN configuration in the UE with the second C-MN configuration;

[0043] Figure 7A This is a flowchart of an example method for managing conditional configurations after receiving an instruction to add, modify, or release a DRB, which can be implemented in the UE of this disclosure;

[0044] Figure 7B This is a flowchart of another example method for managing conditional configurations after receiving an indication to add, modify, or release a DRB, which can be implemented in the UE of this disclosure;

[0045] Figure 7C This is a flowchart of yet another example method for managing conditional configurations after receiving an indication to add, modify, or release a DRB, which can be implemented in the UE of this disclosure;

[0046] Figure 7DThis is a flowchart of an example method for managing the configuration of a condition after receiving an instruction to add, modify, or release a DRB and receiving the configuration of a second condition as an update to the configuration of the first condition, which can be implemented in the UE of this disclosure.

[0047] Figure 8A This is a flowchart of an example method for managing conditional configurations after determining whether to add, modify, or release a DRB, which can be implemented in the MN disclosed herein;

[0048] Figure 8B This is a flowchart of another example method for managing conditional configurations after determining whether to add, modify, or release a DRB, which can be implemented in the MN disclosed herein;

[0049] Figure 8C This is a flowchart of yet another example method that can be implemented in the MN of this disclosure for managing conditional configurations after determining whether to add, modify, or release a DRB; and

[0050] Figure 8D This is a flowchart of another example method for managing the configuration of a conditional configuration, which can be implemented in the MN of this disclosure, after determining whether to add, modify, or release a DRB and determining to update the configuration of the first conditional configuration with the configuration of the second conditional. Detailed Implementation

[0051] As discussed in detail below, when a UE operates in a DC such as an MR-DC or SC, the UE and / or one or more base stations manage the conditional configuration of procedures such as Conditional Handover (CHO), Conditional PSCell Addition or Change (CPAC), or Conditional SN Addition or Change (CSAC). When the RAN notifies the UE that it wants to add, modify, or release a DRB, the UE determines whether it should also release the conditional configuration. Before discussing the technologies that the UE can implement to make this determination, refer to... Figure 1A -C is used to consider example communication systems that incorporate these technologies.

[0052] First refer to Figure 1A Example wireless communication system 100 includes UE 102, base station (BS) 104A, base station 106A, and core network (CN) 110. Base stations 104A and 106A can operate in RAN 105 connected to the same core network (CN) 110. For example, CN 110 can be implemented as evolved packet core (EPC) 111 or fifth generation (5G) core (5GC) 160.

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

[0054] like Figure 1A As shown, base station 104A supports cell 124A, and base station 106A supports cell 126A. Cells 124A and 126A can partially overlap, allowing UE 102 to communicate with base stations 104A and 106A, which operate as primary node (MN) and secondary node (SN), respectively, in the DC. To directly exchange messages during DC scenarios and other scenarios discussed below, MN 104A and SN 106A can support X2 or Xn interfaces. Typically, CN 110 can connect to any suitable number of base stations supporting NR cells and / or EUTRA cells. See below for reference. Figure 1B This section discusses an example configuration for connecting the EPC 110 to an additional base station.

[0055] Base station 104A is equipped with processing hardware 130, which may include one or more general-purpose processors, such as a CPU, and a non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. In the example embodiment, processing hardware 130 includes a conditional configuration controller 132 configured to manage the conditional configuration of one or more conditional processes (e.g., CHO, CPAC, or CSAC) when base station 104A operates as an MN.

[0056] Base station 106A is equipped with processing hardware 140, which may further include one or more general-purpose processors, such as a CPU, and a non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. In the example embodiment, processing hardware 140 includes a conditional configuration controller 142 configured to manage the conditional configuration of one or more conditional processes (e.g., CHO, CPAC, or CSAC) when base station 106A operates as an SN.

[0057] Still referencing Figure 1A UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors, such as a CPU, and a non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. In the example embodiment, processing hardware 150 includes a UE conditional configuration controller 152 configured to manage conditional configuration of one or more conditional processes.

[0058] More specifically, the conditional configuration controllers 132, 142, and 152 can implement at least some of the techniques discussed with reference to the message and flowchart below to receive conditional configurations, release conditional configurations in response to some event, apply conditional configurations, etc. Although Figure 1A While conditional configuration controllers 132 and 142 are illustrated as separate components, in at least some scenarios, base stations 104A and 106A can have similar implementations and operate as MN or SN nodes in different scenarios. In these embodiments, each of base stations 104A and 106A can implement conditional configuration controller 132 and conditional configuration controller 142 to support MN and SN functions, respectively.

[0059] In operation, UE 102 can use radio bearers (RBs) (e.g., DRBs or SRBs) that terminate at different times at MN 104A or SN 106A. When communicating on the radio bearers in the uplink (from UE 102 to BS) and / or downlink (from base station to UE 102) directions, UE 102 can apply one or more security keys. In some cases, the UE can use different RATs to communicate with base stations 104A and 106A. While the examples below may specifically involve particular RAT types, 5G NR, or EUTRA, in general, the techniques disclosed herein can also be applied to other suitable radio access and / or core network technologies.

[0060] Figure 1B An example wireless communication system 100 is depicted, in which communication devices can implement these technologies. The wireless communication system 100 includes a UE 102, base stations 104A, 104B, 106A, 106B, and a core network (CN) 110. The UE 102 is initially connected to base station 104A. Base stations 104B and 106B may have similar processing hardware to base station 106A. The UE 102 is initially connected to base station 104A.

[0061] In some scenarios, base station 104A can perform immediate SN addition to configure UE 102 to operate in dual connectivity (DC) with both base station 104A (via PCell) and base station 106A (via PSCell, different from cell 126A). Base stations 104A and 106A operate as the MN and SN of UE 102, respectively. In some cases, UE 102 can operate using MR-DC connectivity modes, for example, communicating with base station 104A using 5G NR and with base station 106A using EUTRA, or communicating with base station 104A using EUTRA and with base station 106A using 5G NR.

[0062] At a certain point, when UE 102 is in DC with MN 104A and S-SN 106A, MN 104A can perform an immediate SN change to change UE 102's SN from base station 106A (source SN or "S-SN") to base station 104B (target SN or "T-SN"). In another scenario, SN 106A can perform an immediate PSCell change to change UE 102's PSCell to cell 126A. In one implementation, SN 106A can transmit the configuration for changing the PSCell to cell 126A to UE 102 via a signaling radio bearer (SRB) (e.g., SRB3) for immediate PSCell change. In another implementation, SN 106A can transmit the configuration for changing the PSCell to cell 126A to UE 102 via MN 104A for instant PSCell change. MN 104A can transmit the configuration of immediately changing PSCell to cell 126A to UE 102 via SRB1.

[0063] In other scenarios, base station 104A can perform a conditional SN addition procedure to first configure base station 106B as the C-SN of UE 102, i.e., a conditional SN addition or change (CSAC). In this case, UE 102 can be in the SC with base station 104A, or in the DC with both base stations 104A and 106A. If UE 102 is in the DC with both base stations 104A and 106A, MN 104A can determine to perform the conditional SN addition procedure in response to a request received from base station 106A, or in response to one or more measurements received from UE 102 or obtained by MN 104A from measurements of signals received from UE 102. Contrary to the immediate SN addition case discussed above, UE 102 does not immediately attempt to connect to C-SN 106B. In this scenario, base station 104A again operates as MN, but base station 106B initially operates as a C-SN instead of an SN.

[0064] More specifically, when UE 102 receives the configuration from C-SN 106B, UE 102 does not connect to C-SN 106B until UE 102 has determined that a certain condition is met (in some cases, UE 102 may consider multiple conditions, but for convenience, the following discussion only involves a single condition). When UE 102 determines that the condition has been met, UE 102 connects to C-SN 106B, causing C-SN 106B to begin operating as SN 106B for UE 102. Therefore, although base station 106B operates as a C-SN rather than an SN, base station 106B has not yet connected to UE 102 and therefore has not yet served UE 102. In some implementations, UE 102 may disconnect from SN 106A to connect to C-SN 106B.

[0065] In other scenarios, UE 102 connects to MN 104A (via PCell) and SN 106A (via a PSCell different from cell 126A, and not in...) Figure 1A (As shown in the diagram) In the DC. SN 106A can perform a conditional PSCell Add or Change (CPAC) to configure a candidate PSCell (C-PSCell) 126A for UE 102. If UE 102 is configured to use a Signaling Radio Bearer (SRB) (e.g., SRB3) to exchange RRC messages with SN 106A, SN 106A can, for example, transmit the configuration of C-PSCell 126A to UE 102 via the SRB in response to one or more measurement results, which may be received from UE 102 via the SRB or via MN 104A, or may be obtained by SN 106A from measurements of signals received from UE 102. When SN 106A transmits the configuration of C-PSCell 126A to UE 102 via MN 104A, MN 104A receives the configuration of C-PSCell 126A. In contrast to the immediate PSCell change discussed above, UE 102 does not immediately disconnect from the PSCell and attempt to connect to C-PSCell 126A.

[0066] More specifically, when UE 102 receives the configuration for C-PSCell 126A, UE 102 does not connect to C-PSCell 126A until UE 102 has determined that a certain condition is met (in some cases, UE 102 may consider multiple conditions, but for convenience, the following discussion only involves a single condition). When UE 102 determines that the condition is met, UE 102 connects to C-PSCell 126A, causing C-PSCell 126A to begin operating as UE 102's PSCell 126A. Therefore, although cell 126A operates as C-PSCell instead of PSCell, SN 106A may not yet be connected to UE 102 via cell 126A. In some implementations, UE 102 can disconnect from the PSCell to connect to C-PSCell 126A.

[0067] In some scenarios, the condition associated with CSAC or CPAC may be signal strength / quality, which UE 102 detects on C-PSCell 126A of SN106A or on C-PSCell 126B of C-SN 106B, and which exceeds a certain threshold or otherwise corresponds to an acceptable measurement. For example, UE 102 determines that the condition is met when one or more measurements obtained by UE 102 on C-PSCell 126A are higher than a threshold configured by MN 104A or SN 106A or a predetermined or pre-configured threshold. When UE 102 determines that the signal strength / quality on C-PSCell 126A of SN 106A is sufficiently good (again, measured relative to one or more quantization thresholds or other quantization metrics), UE 102 may perform a random access procedure with SN 106A on C-PSCell 126A to connect to SN 106A. Once UE102 successfully completes the random access procedure on C-PSCell 126A, C-PSCell 126A becomes UE102's PSCell 126A. SN 106A can then begin data (user plane data or control plane data) communication with UE102 via PSCell 126A. In another example, UE102 determines that a condition is met when one or more measurements obtained by UE102 on C-PSCell 126B exceed a threshold configured by MN 104A or C-SN 106B, or exceed a predetermined or pre-configured threshold. When UE102 determines that the signal strength / quality on C-PSCell 126B of C-SN 106B is sufficiently good (again, measured relative to one or more quantization thresholds or other quantization metrics), UE102 can perform a random access procedure with C-SN 106B on C-PSCell 126B to connect to C-SN 106B. Once UE 102 successfully completes the random access procedure on C-PSCell 126B, C-PSCell 126B becomes UE 102's PSCell 126B, and C-SN 106B becomes SN 106B. SN 106B can then begin data (user plane data or control plane data) communication with UE 102 via PSCell 126B.

[0068] In various configurations of the wireless communication system 100, base station 104A can be implemented as a primary eNB (MeNB) or primary gNB (MgNB), and base station 106A or 106B can be implemented as a secondary gNB (SgNB) or candidate SgNB (C-SgNB). UE 102 can communicate with base station 104A and base station 106A or 106B (106A / B) via the same RAT (such as EUTRA or NR) or different RATs. When base station 104A is a MeNB and base station 106A is an SgNB, UE 102 can be in an EUTRA-NR DC (EN-DC) with both the MeNB and SgNB. In this scenario, MeNB 104A may or may not configure base station 106B as the C-SgNB of UE 102. In this scenario, SgNB 106A can configure cell 126A as the C-PSCell of UE 102. When base station 104A is a MeNB and base station 106A is a C-SgNB for UE 102, UE 102 can be in the SC with the MeNB. In this scenario, MeNB 104A may or may not configure base station 106B as another C-SgNB for UE 102.

[0069] In some cases, the MeNB, SeNB, or C-SgNB is implemented as an ng-eNB instead of an eNB. When base station 104A is the primary ng-eNB (Mng-eNB) and base station 106A is the SgNB, UE 102 can be in a Next Generation (NG) EUTRA-NR DC (NGEN-DC) with both the Mng-eNB and the SgNB. In this scenario, MeNB 104A may or may not configure base station 106B as a C-SgNB for UE 102. In this scenario, SgNB 106A can configure cell 126A as a C-PSCell for UE 102. When base station 104A is an Mng-NB and base station 106A is a C-SgNB for UE 102, UE 102 can be in an SC with the Mng-NB. In this scenario, Mng-eNB 104A may or may not configure base station 106B as another C-SgNB for UE 102.

[0070] When base station 104A is a MgNB and base stations 106A / B are SgNBs, UE 102 can be in an NR-NR DC (NR-DC) with both the MgNB and SgNB. In this scenario, MeNB 104A may or may not configure base station 106B as a C-SgNB for UE 102. In this scenario, SgNB 106A can configure cell 126A as a C-PSCell for UE 102. When base station 104A is a MgNB and base station 106A is a C-SgNB for UE 102, UE 102 can be in an SC with the MgNB. In this scenario, MgNB 104A may or may not configure base station 106B as another C-SgNB for UE 102.

[0071] When base station 104A is a MgNB and base stations 106A / B are secondary ng-eNBs (Sng-eNBs), UE 102 can be in an NR-EUTRA DC (NE-DC) with both the MgNB and the Sng-eNB. In this scenario, MgNB 104A may or may not configure base station 106B as a C-Sng-eNB for UE 102. In this scenario, Sng-eNB 106A can configure cell 126A as a C-PSCell for UE 102. When base station 104A is a MgNB and base station 106A is a candidate Sng-eNB (C-Sng-eNB) for UE 102, UE 102 can be in an SC with the MgNB. In this scenario, MgNB 104A may or may not configure base station 106B as another C-Sng-eNB for UE 102.

[0072] Base stations 104A, 106A, and 106B can connect to the same core network (CN) 110, which can be an evolved packet core (EPC) 111 or a fifth-generation core (5GC) 160. Base station 104A can be implemented as 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 base station supporting an NR radio interface and an NG interface for communication with 5GC 160. Base station 106A can be implemented as 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. For direct message exchange during the scenarios discussed below, base stations 104A, 106A, and 106B can support X2 or Xn interfaces.

[0073] like Figure 1BAs illustrated, base station 104A supports cell 124A, base station 104B supports cell 124B, base station 106A supports cell 126A, and base station 106B supports cell 126B. Cells 124A and 126A can partially overlap, as can cells 124A and 124B, allowing UE 102 to communicate with base station 104A (operating as MN) and base station 106A (operating as SN) in the DC, and to communicate with base station 104A (operating as MN) and SN 106B after completing the SN change. More specifically, when UE 102 is in the DC with base stations 104A and 106A, base station 104A operates as a MeNB, MNg-eNB, or MgNB, and base station 106A operates as an SgNB or SNg-eNB. Cells 124A and 126B can partially overlap. When UE 102 and base station 104A are in SC, base station 104A operates as MeNB, MNg-eNB, or MgNB, and base station 106B operates as C-SgNB or C-Sng-eNB. When UE 102, base station 104A, and base station 106A are in DC, base station 104A operates as MeNB, MNg-eNB, or MgNB, base station 106A operates as SgNB or SNg-eNB, and base station 106B operates as C-SgNB or C-Sng-eNB.

[0074] Typically, the wireless communication network 100 may include any suitable number of base stations supporting NR cells and / or EUTRA cells. More specifically, the EPC 111 or 5GC 160 may connect to any suitable number of base stations supporting NR cells and / or EUTRA cells. Although the examples below specifically relate to particular CN types (EPC, 5GC) and RAT types (5G NR and EUTRA), generally, 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.

[0075] Figure 1CAn example distributed implementation of a base station, such as base station 104A, 104B, 106A, or 106B, is depicted. The base station in this implementation may include a centralized unit (CU) 172 and one or more distributed units (DUs) 174. CU 172 is equipped with processing hardware, which may include one or more general-purpose processors, such as CPUs, and a non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. In one example, CU 172 is equipped with processing hardware 130. In another example, CU 172 is equipped with processing hardware 140. When base station 106A operates as a SN or candidate SN (C-SN), the processing hardware 140 in the example implementation includes a (C-)SN RRC controller 142 configured to manage or control one or more RRC configurations and / or RRC processes. Base station 106B may have the same or similar hardware as base station 106A. DU 174 is also equipped with processing hardware, which may include one or more general-purpose processors, such as a CPU, and a non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. In some examples, when base station 106A operates as an MN, SN, or candidate SN (C-SN), the processing hardware in example embodiments includes a Media Access Control (MAC) controller configured to manage or control one or more MAC operations or procedures (e.g., random access procedures), and a Radio Link Control (RLC) controller configured to manage or control one or more RLC operations or procedures. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0076] Figure 2A simplified illustration of an example radio protocol stack 200 is provided, according to which UE 102 can communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104A, 104B, 106A, and 106B). 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 provides an RLC channel to the EUTRA PDCP sublayer 208, and in some cases, a channel 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, in turn, 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. Additionally, as... Figure 2 As shown in the figure, UE 102 can support the layering of NR PDCP sublayer 210 on EUTRA RLC sublayer 206A.

[0077] 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 SDUs and PDUs is relevant, for simplicity, this disclosure refers to both SDUs and PDUs as “packets”.

[0078] 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.

[0079] In the scenario where UE 102 operates in EUTRA / NR DC (EN-DC), 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 by the MN using EUTRA PDCP sublayer 208, or a bearer terminated by the MN using NR PDCP sublayer 210. In various scenarios, wireless communication system 100 can also provide UE 102 with a bearer terminated by the SN, which uses 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.

[0080] Next, refer to Figure 3A-6C Several example scenarios are discussed regarding the configuration of conditional conditions in the process of UE and / or base station management. In each scenario, RAN 105 determines to add, modify, or release an RB, such as a DRB. As a result, UE 102 may ignore the configuration of the first conditional condition, which may include updating the configuration of the first conditional condition with the configuration of the second conditional condition. In some implementations, RAN 105 may include an explicit indication to release the configuration of the conditional condition. In other implementations, UE 102 may receive an indication that UE 102 wants to add, modify, or release a DRB, and may use this indication as an implicit indication that UE 102 should release the configuration of the conditional condition. In other implementations, UE 102 may receive the configuration of the second conditional condition, which may be a full configuration or an incremental configuration that expands the configuration of the first conditional condition. UE 102 can then update the configuration of the first conditional condition based on the configuration of the second conditional condition. For example, if the configuration of the second conditional condition is a full configuration, UE 102 may replace the configuration of the first conditional condition with the configuration of the second conditional condition.

[0081] More specifically, first refer to Figure 3AIn scenario 300A, base station 104A operates as MN 302, and base station 106A operates as SN. Initially, UE 102 is in MR-DC with MN 104A and SN 106A. Depending on a certain SN configuration, UE 102 communicates UL PDU and / or DL ​​PDU with SN 106A via PSCell (i.e., a cell different from cell 126A). SN 106A then determines 304 that it should generate the first C-SN configuration for Conditional PSCell Add-or-Change (CPAC). SN 106A may make this determination based on one or more measurement results received from UE 102 via MN 104A, received directly from the UE (e.g., via a signaling radio bearer (SRB) established between UE 102 and SN 106A or via a physical control channel), or obtained by SN 106A from measurements of signals, control channels, or data channels received from UE 102, or another suitable event. More intelligently, SN 106A may derive or estimate that UE 102 is moving towards the coverage area of ​​cell 126A based on uplink signals received from UE 102 or location measurement results(s) received from UE 102. In response to this determination, SN 106A generates 304 First C-SN Configuration.

[0082] In example scenario 300A, SN 106A then transmits 306, the first C-SN configuration, to MN 104A. MN 104A then transmits 308, the first C-SN configuration, to UE 102. In some implementations, SN 106A generates a first conditional configuration including the first C-SN configuration at event 304, and generates a first RRC reconfiguration message including the first conditional configuration. SN 106A may assign a first configuration identifier / identifier (ID) to identify the first conditional configuration or the first C-SN configuration, and include the first configuration ID in the first conditional configuration. Then, at event 306, SN 106A transmits the first RRC reconfiguration message to MN 104A. MN 104A then transmits the first RRC reconfiguration message including the first conditional configuration to UE 102 at event 308. In other implementations, MN 104A generates a first conditional configuration including the first C-SN configuration, and generates a first RRC reconfiguration message including the first conditional configuration. SN 106A can assign a first configuration ID that identifies the first conditional configuration or the first C-SN configuration, and can include the first configuration ID in the first conditional configuration. At event 308, MN 104A transmits a first RRC reconfiguration message to UE 102 that includes the first conditional configuration.

[0083] In some implementations, in response to the aforementioned first RRC reconfiguration message, UE 102 may transmit a 310 first RRC reconfiguration complete message to MN 104A. In response to the first RRC reconfiguration complete message, MN 104A may transmit a 312 SN message (e.g., an SN reconfiguration complete message or an SN modification confirmation message) to SN 106A. Events 302-312 may collectively define the CPAC configuration procedure 320A.

[0084] In one implementation, to transmit the first RRC reconfiguration message, MN 104A transmits a first RRC container message including the first RRC reconfiguration to UE 102. In response, in one implementation, UE 102 transmits a first RRC container response message to MN 104A to transmit a 310 first RRC reconfiguration complete message. In response to either the first RRC container response message or the first RRC reconfiguration complete message, MN 104A may send a 312SN message to SN 106A. At event 312, MN 104A may include the first RRC reconfiguration complete message in the SN message. In another implementation, UE 102 does not generate an RRC container response message to wrap the first RRC reconfiguration complete message.

[0085] In this example scenario and the scenarios discussed below, the base station can generate a conditional configuration that includes, in addition to a cell-related candidate base station configuration (e.g., a C-SN configuration or C-MN configuration for CPAC or CSAC), one or more conditions (“triggering conditions”) that must be met before the UE applies the candidate base station configuration. The base station can transmit a message including the conditional configuration, which includes only the candidate base station configuration, or alternatively, the conditional configuration includes (i) the candidate base station configuration and (ii) at least one triggering condition. The base station may also include a configuration identifier / identifier (ID) that identifies the conditional configuration or the candidate base station configuration. In this example scenario, MN 104A or SN106A can transmit a first RRC reconfiguration message including a first conditional configuration, which includes only the first C-SN configuration, or alternatively, the first conditional configuration includes (i) the first C-SN configuration and (ii) at least one triggering condition. Additionally, MN 104A or SN 106A may include a configuration ID in the first conditional configuration to identify the first C-SN configuration or the first conditional configuration.

[0086] Subsequently, MN 104A receives a first interface message 316 from CN 110 (e.g., MME 114 or AMF 164). In response to the first interface message, MN 104A determines 318 to add, modify, or release the DRB. MN 104A may send a second interface message to CN 110 in response to the first interface message. In one embodiment, MN 104A determines to add a new DRB in response to the first interface message. In another embodiment, MN 104A determines to modify or release an existing DRB configured for UE 102 in response to the first interface message. For example, MN 104A may determine to modify the DRB by modifying or releasing radio resources used for the DRB. Radio resources may include one or more RLC bearer or Quality of Service (QoS) mapping configurations (e.g., adding a new QoS flow and mapping that new QoS flow to an existing DRB or releasing an existing QoS flow). In one embodiment, the DRB may be an SN-terminated DRB. In another embodiment, the DRB may be an MN-terminated DRB utilizing the radio resources of SN 106A. In response to a second RRC reconfiguration message, UE 102 may release or modify radio resources (i.e., release or modify DRBs). In the following description, "add, modify, or release a DRB" may mean "add a new DRB" or "modify or release an existing DRB".

[0087] In some implementations, the first interface message and the second interface message can be NG application protocol messages as defined in 3GPP specification 38.413. For example, the first interface message can be a PDU session resource establishment request message, a PDU session resource modification request message, a PDU session resource release request message, or an initial context establishment request message, and the second interface message can be a PDU session resource establishment response message, a PDU session resource modification response message, a PDU session resource release response message, or an initial context establishment response message. In other implementations, the first interface message and the second interface message can be S1 application protocol messages as defined in 3GPP specification 36.413. For example, the first interface message can be an E-RAB establishment request message, an E-RAB modification request message, an E-RAB release command message, or an initial context establishment request message, and the second interface message can be an E-RAB establishment response message, an E-RAB modification response message, an E-RAB release response message, or an initial context establishment response message.

[0088] In response to confirmation 318, MN 104A sends a 352 SN Request message to SN 106A to request SN 106A to add, modify, or release the DRB. In response to the SN Request message, SN 106A adds, modifies, or releases the DRB and sends a 354 SN Request Confirmation message. MN 104A transmits a 356 Second RRC Reconfiguration message (Add, Modify, or Release DRB) to UE 102. In response to adding, modifying, or releasing the DRB, UE 102 ignores the 382 First C-SN Configuration message. In response to the Second RRC Reconfiguration message, UE 102 transmits a 358 Second RRC Reconfiguration Complete message.

[0089] As described below, the second RRC reconfiguration message can be generated by MN 104A or SN 106A. In some embodiments, SN 106A can generate a radio bearer configuration (e.g., RadioBearerConfig) IE for adding, modifying, or releasing the DRB, and include the radio bearer configuration in the SN request acknowledgment message. MN 104A can generate the second RRC reconfiguration message and include the radio bearer configuration in the second RRC reconfiguration message. In other embodiments, MN 104A can generate a radio bearer configuration (e.g., RadioBearerConfig) IE for adding, modifying, or releasing the DRB, and include the radio bearer configuration in the second RRC reconfiguration message.

[0090] In other implementations, SN 106A may generate a cell group configuration (e.g., CellGroupConfig IE or SCG-ConfigPartSCG-r12 IE) that modifies the DRB (i.e., the existing DRB configured for UE 102). SN 106A includes the cell group configuration in a second RRC reconfiguration message. Then, SN 106A includes the second RRC reconfiguration message in an SN request confirmation message. In this case, MN 104A generates a second RRC container message including the second RRC reconfiguration message and transmits the second RRC container message 356 to UE 102. UE 102 may transmit a second RRC container response message 568 including a second RRC reconfiguration completion message 568 to MN 104A, and further, MN 104A may send the second RRC reconfiguration completion message to SN 106A, for example, in the SN reconfiguration completion message. Neither the second RRC reconfiguration nor the second RRC container message configured UE 102 to release MR-DC, so that UE 102 remains in MR-DC with MN 104A and SN 106A.

[0091] In the above embodiments, neither the second RRC reconfiguration message nor the second RRC container message includes the C-SN configuration release field / IE that instructs UE 102 to release the first C-SN configuration. In other words, neither MN104A nor SN 106A includes the C-SN configuration release field / IE in the second RRC reconfiguration message or the second RRC container message.

[0092] In some implementations, the SN request message is an SN modification request message, and the SN request confirmation message is an SN modification request confirmation message.

[0093] When SN 106A is implemented as an ng-eNB, the first and second RRC reconfiguration messages (if generated by SN 106A) are RRCConnectionReconfiguration messages, and the first and second RRC reconfiguration completion messages are RRCConnectionReconfigurationComplete messages. When SN 106A is implemented as a gNB, the first and second RRC reconfiguration messages (if generated by SN 106A) are RRCReconfiguration messages, and the first and second RRC reconfiguration completion messages are RRCReconfigurationcomplete messages. When MN 104A is implemented as an eNB or ng-eNB, the RRC container message is an RRCConnectionReconfiguration message, and the RRC container response message is RRCConnectionReconfigurationComplete. When MN 104A is implemented as a gNB, the RRC container message is an RRCReconfiguration message, and the RRC container response message is RRCReconfigurationComplete message.

[0094] When the MN 104A is implemented as an eNB or ng-eNB, the first and second RRC reconfiguration messages (if generated by the MN 104A) are RRCConnectionReconfiguration messages, and the first and second RRC reconfiguration completion messages are RRCConnectionReconfigurationComplete messages. When the MN 104A is implemented as a gNB, the first and second RRC reconfiguration messages (if generated by the MN 104A) are RRCReconfiguration messages, and the first and second RRC reconfiguration completion messages are RRCReconfigurationComplete messages.

[0095] Continue to refer to Figure 3AIn some implementations, the first C-SN configuration may be a complete and self-contained configuration (i.e., a full configuration). The first C-SN configuration may include a full configuration indication (information element (IE) or field) that identifies the first C-SN configuration as a full configuration. In this case, UE 102 can directly use the first C-SN configuration to communicate with SN 106A without relying on the SN configuration. On the other hand, in other cases, the first C-SN configuration may include a "delta" configuration, or one or more configurations that extend a previously received SN configuration. In this case, UE 102 can use both the incremental C-SN configuration and the SN configuration to communicate with SN 106A.

[0096] The first C-SN configuration may include multiple configuration parameters for UE 102 to apply when communicating with SN 106A via C-PSCell 126A. These multiple configuration parameters can assign zero or more candidate secondary cells (PSCells) of C-PSCell 126A and SN 106A to UE 102. These multiple configuration parameters can configure radio resources for UE 102 to communicate with SN 106A via zero or more PSCells of C-PSCell 126A and SN 106A. These multiple configuration parameters can configure zero or more radio bearers. The one or more radio bearers may include SRBs and / or one or more DRBs.

[0097] The SN configuration may include multiple configuration parameters for UE 102 to communicate with SN 106A via PSCell and zero or more secondary cells (SCells) of SN 106A. These configuration parameters can configure radio resources for UE 102 to communicate with SN 106A via PSCell and zero or more SCells of SN 106A. The configuration parameters can also configure zero or more radio bearers. One or more radio bearers may include SRBs and / or one or more DRBs.

[0098] In some implementations, SN 106A may include CPAC configuration in an SN modification confirmation message received from MN 104A in response to an SN modification request message, and send the SN modification request confirmation message to MN 104A during event 306. In other implementations, SN 106A may include CPAC configuration in a request SN modification message, and send a request SN modification message to MN 104A during event 306. SN 106A may indicate that the SN modification request confirmation message or the request SN modification message is for CPAC, such that MN 104A can determine that the SN modification request confirmation message or the request SN modification message includes CPAC configuration. In other implementations, SN 106A does not indicate CPAC in the SN modification request confirmation message or the request SN modification message, such that the CPAC configuration from SN 106A is transparent to MN 104A (in other words, allowing MN 104A to simply tunnel the CPAC configuration to UE 102 without processing the CPAC configuration).

[0099] In some implementations, the first C-SN configuration may include a CellGroupConfig IE configuring zero or more C-SCells of C-PSCell 126A and SN106A. In one implementation, the first C-SN configuration may include a radio bearer configuration. In another implementation, the first C-SN configuration may not include a radio bearer configuration. For example, the radio bearer configuration may be a RadioBearerConfig IE, a DRB-ToAddModList IE, or an SRB-ToAddModList IE, a DRB-ToAddMod IE, or an SRB-ToAddMod IE. In various implementations, the first C-SN configuration may be an RRCReconfiguration message conforming to 3GPP TS 38.331, an RRCReconfiguration-IEs, or a CellGroupConfig IE. The complete configuration indication may be a field or IE conforming to 3GPP TS 38.331. In other implementations, the first C-SN configuration may include an SCG-ConfigPartSCG-r12 IE, which configures zero or one C-SCells of C-PSCell 126A and SN106A. In some implementations, the first C-SN configuration is an RRCConnectionReconfiguration message, RRCConnectionReconfiguration-IEs, or ConfigPartSCG-r12 IE conforming to 3GPP TS 36.331. The complete configuration indication may be a field or IE conforming to 3GPP TS 36.331.

[0100] In some implementations, the SN configuration may include a CellGroupConfigIE configuring the PSCell, and may configure zero or one or more SCells of SN 106A. In one implementation, the SN configuration may be an RRCReconfiguration message, RRCReconfiguration-IEs, or CellGroupConfigIE conforming to 3GPP TS38.331. In other implementations, the SN configuration may include an SCG-ConfigPartSCG-r12 IE configuring the PSCell, and may configure zero or one or more SCells of SN 106A. In one implementation, the SN configuration may be an RRCConnectionReconfiguration message, RRCConnectionReconfiguration-IEs, or ConfigPartSCG-r12 IE conforming to 3GPP TS36.331.

[0101] In some scenarios, during event 308, UE 102 may receive one or more conditions in a conditional configuration (discussed in the singular throughout this disclosure for convenience). UE 102 may use one or more conditions to determine whether to connect to C-PSCell 126A. If UE 102 determines that the condition is met, then UE 102 connects to C-PSCell 126A. That is, the condition (or “trigger condition”) triggers UE 102 to connect to C-PSCell 126A or perform the first C-SN configuration. However, if UE 102 does not determine that the condition is met, then UE 102 does not connect to C-PSCell 126A.

[0102] Still referencing Figure 3A In some cases, SN 106A may include CU 172 and one or more DU 174, such as Figure 1CAs illustrated, the UE communicates with SN 106A via a first DU 174 operating PSCell 302. In response to determination 304, CU 172 may send a UE context establishment request message to a second DU 174 operating C-PSCell 126A. In response to the UE context establishment request message, the second DU 174 may generate a first C-SN configuration or a portion thereof, and send the first C-SN configuration or a portion thereof to CU 172 in a UE context establishment response message. When the second DU 174 generates a portion of the first C-SN configuration, CU 172 may generate the remainder of the first C-SN configuration. If the first DU 174 also operates C-PSCell 126A, CU 172 may send a UE context modification request message to the first DU 174. In response to a UE context modification request message, the first DU 174 may generate a first C-SN configuration or a portion thereof, and send the first C-SN configuration or a portion thereof to the CU 172 in a UE context modification response message. When the first DU 174 generates a portion of the first C-SN configuration, the CU 172 may generate the remainder of the first C-SN configuration.

[0103] Now for reference Figure 3B Scenario 300B involves CPAC without SN change, i.e., a conditional change of the SN's PSCell when the UE is already in the DC with both the MN and SN. In this scenario, base station 104A operates as the MN and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figure 3A and Figure 3B The differences between the scenarios.

[0104] The CPAC configuration process 320B is typically similar to Figure 3A The CPAC configuration process is 320A. However, in scenario 300B, SN106A directly transmits 307, including the first RRC reconfiguration message with the first conditional configuration, to UE 102, instead of... Figure 3AIn scenario 300A, SN 106A transmits a first RRC reconfiguration message to UE 102 via MN 104A, as SN 106A does. In some implementations, SN 106A configures a first SRB for UE 102 via MN 104A and transmits the first RRC reconfiguration message to UE 102 via the first SRB. For example, SN 106A transmits an SRB configuration configuring the first SRB (e.g., SRB3) to MN 104A, and MN 104A transmits the SRB configuration to the UE via a second SRB (e.g., SRB1) between MN 104A and UE 102. In some implementations, in response to the first RRC reconfiguration message, UE 102 may transmit a first RRC reconfiguration complete message (309) to SN 106A via the first SRB, instead of transmitting a first RRC reconfiguration complete message (310) to MN 104A as in scenario 300A.

[0105] When SN 106A is implemented as an ng-eNB, the first RRC reconfiguration message in event 307 is an RRCConnectionReconfiguration message, and the first RRC reconfiguration completion message in event 309 is an RRCConnectionReconfigurationComplete message. When SN 106A is a gNB, the first RRC reconfiguration message in event 307 is an RRC reconfiguration message, and the first RRC reconfiguration completion message in event 309 is an RRCReconfigurationComplete message.

[0106] Now for reference Figure 3C Scenario 300C involves CPAC without SN change, i.e., a conditional change of the SN's PSCell when the UE is already in the DC with both the MN and SN. In this scenario, base station 104A operates as the MN, and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figures 3A-3B and Figure 3C The differences between the scenarios.

[0107] In scenario 300C, in response to the SN request message (event 352), SN 106A determines 353 to release the first C-SN configuration. In response to this determination, SN 106A generates a C-SN configuration release field / IE, which instructs UE 102 to release the first C-SN configuration. SN 106A sends an SN request confirmation message including the C-SN configuration release field / IE to MN 104A. MN 104A includes the C-SN configuration release field / IE in a second RRC reconfiguration message for adding, modifying, or releasing a DRB, and transmits a second RRC reconfiguration message to UE 102. In response to the C-SN configuration release field / IE, UE 102 releases 383 the first C-SN configuration. The C-SN configuration release field / IE may include a first configuration ID, allowing UE 102 to use the C-SN configuration release field / IE (or the first configuration ID) to identify and release the first C-SN configuration or a first conditional configuration including the first C-SN configuration.

[0108] In some implementations, SN 106A may include a C-SN configuration release field / IE in the second RRC reconfiguration message, radio bearer configuration, or cell group configuration generated by SN 106A.

[0109] Now for reference Figure 3D Scenario 300D involves CPAC without SN change, i.e., a conditional change of the SN's PSCell when the UE is already in the DC with both the MN and SN. In this scenario, base station 104A operates as the MN, and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figures 3A-3C and Figure 3D The differences between the scenarios.

[0110] In scenario 300D, in response to determination 353, SN 106A generates a second RRC reconfiguration message for adding, modifying, or releasing a DRB, and includes a C-SN configuration release field / IE in the second RRC reconfiguration message. SB 106A sends a SN request confirmation message 384 to MN 104A in response to the SN request message. SN request confirmation message 384 and SN request confirmation message 354 can be the same message with different content. Then, SN 106A transmits the second RRC reconfiguration message 357 directly to UE 102, for example via a first SRB (e.g., SRB3). In response to the second RRC reconfiguration message, UE 102 transmits a second RRC reconfiguration complete message 359 to SN 106A, for example via the first SRB. SN 106A can send the second RRC reconfiguration message before, during, or after transmitting the SN request confirmation message (event 384). SN 106A can receive a second RRC reconfiguration complete message before, during, or after transmitting the SN request confirmation message (event 384).

[0111] Now for reference Figure 3E Scenario 300E involves CPAC without SN change, i.e., a conditional change of the SN's PSCell when the UE is already in the DC with both the MN and SN. In this scenario, base station 104A operates as the MN, and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figures 3A-3C and Figure 3E The differences between the scenarios.

[0112] In scenario 300E, in response to determination 353, SN 106A generates a third RRC reconfiguration message including the C-SN configuration release field / IE. Then, SN 106A transmits the third RRC reconfiguration message 367 directly to UE 102, for example via a first SRB (e.g., SRB3). In response to the third RRC reconfiguration message, UE 102 transmits a third RRC reconfiguration complete message 369 to SN 106A, for example via the first SRB. SN 106A may send the third RRC reconfiguration message before, during, or after transmitting the SN request confirmation message (event 354). SN 106A may receive a second RRC reconfiguration complete message before, during, or after transmitting the SN request confirmation message (event 354).

[0113] When SN 106A is implemented as an ng-eNB, the third RRC reconfiguration message is an RRCConnectionReconfiguration message, and the third RRC reconfiguration completion message is an RRCConnectionReconfigurationComplete message. When SN 106A is implemented as a gNB, the third RRC reconfiguration message is an RRCReconfiguration message, and the third RRC reconfiguration completion message is an RRCReconfigurationComplete message.

[0114] Now for reference Figure 3F Scenario 300F involves CPAC without SN change, i.e., a conditional change of the SN's PSCell when the UE is already in the DC with both the MN and SN. In this scenario, base station 104A operates as the MN, and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figures 3A-3C and Figure 3F The differences between the scenarios.

[0115] In scenario 300F, in response to the SN request message (event 352), SN 106A determines 363 to update the first C-SN configuration. In response to this determination, SN 106A generates an SN request confirmation message including the second C-SN configuration and sends a 364 SN request confirmation message to MN 104A. MN 104A transmits a 376 second RRC reconfiguration message, which adds, modifies, or releases the DRB and includes the second C-SN configuration. In response to the second RRC reconfiguration message, UE 102 updates the first C-SN configuration with the second C-SN configuration 385. The second RRC reconfiguration message at event 376 is similar to the second RRC reconfiguration message at event 366 in scenario 300C, except that the second RRC reconfiguration at event 366 releases the first C-SN configuration.

[0116] In some implementations, SN 106A generates a second conditional configuration including the second C-SN configuration at event 363, and generates a second RRC reconfiguration message including the second conditional configuration. At event 364, SN 106A includes the second RRC reconfiguration in an SN request confirmation message. SN 106A may assign a second configuration ID to identify the second conditional configuration or the second C-SN configuration, and include the second configuration ID in the second conditional configuration. SN 106A assigns a second configuration ID with the same value as the first configuration ID, or assigns a second configuration ID with a different value than the first configuration ID. In other implementations, at event 364, SN 106A includes the second conditional configuration in the SN request confirmation message. MN104A generates a second RRC reconfiguration message including the second conditional configuration. In other implementations, at event 364, SN 106A includes the second conditional configuration in the SN request confirmation message. In event 364, MN 104A or SN 106A generates a fourth RRC reconfiguration message including the second conditional configuration, and includes the fourth RRC reconfiguration message in the SN request confirmation message. Then, in event 376, MN 104 generates a second RRC reconfiguration message including the fourth RRC reconfiguration message and transmits the second RRC reconfiguration message. In the second RRC reconfiguration completion message, UE 102 may or may not include the fourth RRC reconfiguration completion message in response to the fourth RRC reconfiguration message. In this case, the second RRC reconfiguration message may be an RRC container message, and the second RRC reconfiguration completion message may be an RRC container response message, similar to the above description.

[0117] In some implementations, UE 102 replaces the first C-SN configuration with a second C-SN configuration; that is, UE 102 releases the first C-SN configuration and stores the second C-SN configuration. In other implementations, UE 102 replaces the first conditional configuration with a second conditional configuration; that is, UE 102 releases the first conditional configuration and stores the second conditional configuration. In one implementation, MN 104A or SN 106A may include a C-SN configuration release field / IE in the second RRC reconfiguration message or the fourth RRC reconfiguration message to release the first C-SN configuration (or the first conditional configuration). In another implementation, neither MN 104A nor SN 106A includes a C-SN configuration release field / IE, but releases the first C-SN configuration (or the first conditional configuration) in the second RRC reconfiguration message or the fourth RRC reconfiguration message. In this case, the second configuration ID in the second conditional configuration has the same value as the first configuration ID in the first conditional configuration, allowing UE 102 to identify the first C-SN configuration or the first conditional configuration to be replaced.

[0118] Optionally, UE 102 may detect (or determine) that condition 334 will later be met for connection to C-PSCell 126A, and in response to this detection, initiate a random access procedure on C-PSCell 126A. For convenience, this discussion may refer to conditions or configurations in the singular, but it will be understood that multiple conditions may exist, and a conditional configuration may include one or more configuration parameters to specify conditions or multiple conditions. UE 102 then performs the random access procedure 336 with SN 106A via C-PSCell 126A, for example, by using one or more random access configurations in a second C-SN configuration. During or after the random access configuration, UE 102 may transmit a 338RRC reconfiguration complete message via C-PSCell 126A to connect to C-PSCell 126A. Alternatively, UE 102 can send a 338RRC reconfiguration complete message to MN104A, and MN104A can then send an RRC reconfiguration complete message to SN 106A. If UE 102 successfully completes the random access procedure, UE 102 communicates with SN 106A via C-PSCell 126A using the configuration in the C-SN configuration 342. If SN106A recognizes UE 102 during the random access procedure, SN106A communicates with UE 102 via C-PSCell 126A. UE 102 can disconnect from the PSCell to perform the random access procedure, i.e., connect to C-PSCell 126A.

[0119] In some implementations, the random access procedure may be a four-step random access procedure or a two-step random access procedure. In other implementations, the random access procedure may be a contention-based random access procedure or a contention-free random access procedure. After UE 102 successfully completes the random access procedure 336, C-PSCell 126A begins to operate as PSCell 126A, and UE 102 begins to operate in the DC via PCell 124A and MN 104A and via PSCell 126A and SN 106A 342. Specifically, UE 102 communicates with SN 106A via C-PSCell 126A (i.e., the new PSCell 126A) according to the second C-SN configuration for CPAC 342.

[0120] In some cases, SN 106A may include CU 172 and one or more DU 174, such as Figure 1CAs illustrated, the UE communicates with the SN 302 via the first DU 174 operating PSCell. In response to determination 363, CU 172 may send a UE context establishment request message or a UE context modification request message to the second DU 174 operating C-PSCell 126A. In response to the UE context establishment request message or the UE context modification request message, the second DU 174 may generate a second C-SN configuration or a portion thereof, and send the second C-SN configuration or a portion thereof to CU 172 in a UE context establishment response message or a UE context modification response message. When the second DU 174 generates a portion of the second C-SN configuration, CU 172 may generate the remainder of the second C-SN configuration. UE 102 performs a random access procedure 336 with the second DU 172, and the second DU 174 may identify UE 102 during the random access procedure. If the second DU 174 can identify UE 102 during the random access procedure, the second DU 174 can send an indication (e.g., a downlink data delivery status message) to the CU 172. During or after the random access procedure, the second DU 174 can receive a 338RRC reconfiguration complete message from UE 102 via the C-PSCell. Furthermore, the second DU 174 can include the RRC reconfiguration complete message in an F1 Application Protocol (F1AP) message (e.g., a UL RRC messaging message) and send an F1AP message to the CU 172. In response to the F1AP message or the RRC reconfiguration complete message 338, the CU 172 communicates with the UE 342 via the second DU 174. The CU 172 can send a UE context release command message to the first DU 174, instructing the first DU 174 to release the UE context of UE 102 in response to the indication received in the F1AP message or from MN 104A, or the RRC reconfiguration complete message 338. In response to a UE context release command message, the first DU 174 releases the UE context of UE 102 and sends a UE context release complete message. In response to this indication (e.g., a downlink data delivery status message) or an RRC reconfiguration complete message 338, the CU 172 may begin transmitting DL PDUs (e.g., PDCP PDUs) to UE 102 via C-PSCell 126A of either the first DU 174 or the second DU 174. If the first DU 174 operates via C-PSCell 126A, the second DU 174 and the first DU 174 can be the same DU 174. Otherwise, the second DU 174 and the first DU 174 are different DUs.

[0121] Example implementations of the second C-SN configuration can be similar to the first C-SN configuration. Example implementations of the second conditional configuration can be similar to the first conditional configuration. In some implementations, MN 104A or SN 106A may include the condition to be evaluated by UE 102 or a new condition in the second conditional configuration or the second RRC reconfiguration message. At event 334, UE 102 reuses the condition or uses the new condition in the second conditional configuration or the second RRC reconfiguration message. In other implementations, neither MN 104A nor SN 106A includes the condition evaluated by UE 102 in the second conditional configuration or the second RRC reconfiguration message, such that UE 102 reuses the condition in the first conditional configuration or the first RRC reconfiguration message at event 334.

[0122] Now for reference Figure 3G Scenario 300G involves CPAC without SN change, i.e., a conditional change of the SN's PSCell when the UE is already in the DC with both the MN and SN. In this scenario, base station 104A operates as the MN, and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numbers. The following discussion... Figure 3D-3F and Figure 3G The differences between the scenarios.

[0123] In scenario 300G, in response to determination 363, SN 106A generates a second RRC reconfiguration message for adding, modifying, or releasing a DRB, and includes a second conditional configuration in the second RRC reconfiguration message. Then, SN 106A directly transmits the second RRC reconfiguration message 377 to UE 102 via the first SRB. In response to the second RRC reconfiguration message, UE 102 transmits a second RRC reconfiguration complete message 379 to SN 106A via the first SRB. SN 106A may send the second RRC reconfiguration message before, during, or after transmitting the SN request confirmation message (event 384). SN 106A may receive the second RRC reconfiguration complete message before, during, or after transmitting the SN request confirmation message (event 384).

[0124] Now for reference Figure 3H Scenario 300H involves CPAC without SN change, i.e., a conditional change of the SN's PSCell when the UE is already in the DC with both the MN and SN. In this scenario, base station 104A operates as the MN, and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figure 3F-3G and Figure 3H The differences between the scenarios.

[0125] In scenario 300H, in response to determination 363, SN 106A generates a third RRC reconfiguration message including the second conditional configuration. Then, SN 106A transmits the third RRC reconfiguration message 367 directly to UE 102, for example via a first SRB (e.g., SRB3). In response to the third RRC reconfiguration message, UE 102 transmits a third RRC reconfiguration complete message 369 to SN 106A, for example via the first SRB. SN 106A may send the third RRC reconfiguration message before, during, or after transmitting the SN request confirmation message (event 354). SN 106A may receive the second RRC reconfiguration complete message before, during, or after transmitting the SN request confirmation message (event 354).

[0126] Next reference Figure 4A -C discusses several example scenarios involving CSAC.

[0127] First refer to Figure 4A Scenario 400A involves CSAC, where, when the UE is already in the DC with the MN and SN, the PSCell of the SN is conditionally changed to the C-PSCell of the C-SN. In this scenario, base station 104A operates as the MN, base station 106A operates as the SN, and base station 106B operates as the C-SN. At the beginning of this scenario, UE 102 operates in the DC with MN 104A and SN 106A 402, and communicates UL PDU and / or DL ​​PDU with MN 104A via PCell, and communicates UL PDU and / or DL ​​PDU with SN 106A via PSCell (i.e., cells other than cell 126A). Events 402, 416, 418, 452, 454, 456, 458, and 482 are similar to events 302, 316, 318, 352, 354, 356, 358, and 382. The following discussion... Figure 3A and Figure 4A The differences between the scenarios.

[0128] MN 104A determines that it should configure base station 106B as the C-SN of the CSAC, such that the SN of UE 102 will change from SN 106B to C-SN 106B. For example, MN 104A may determine this based on multiple measurement results from UE 102, or in response to an indication from SN 106A that SN 106A requires a conditional SN change (e.g., a request SN change message). More intelligently, MN 104A or SN 106A may derive or estimate that UE 102 is moving towards the coverage area of ​​cell 126B or base station 106B based on uplink signals received from UE 102 or multiple location measurement results received from UE 102, allowing MN 104A to make a determination, or SN 106A to send an indication to MN 104A. In response to this determination, MN 104A sends a 405 SN Request Message for CSAC to C-SN 106A. In response to receiving the 405 SN Request Message, C-SN 106B determines 406 that it should generate a first C-SN configuration for CSAC for UE 102. C-SN 106B transmits a 407 SN Request Confirmation Message to MN 104A including the first C-SN configuration for CSAC. The first C-SN configuration may include configurations for C-PSCells (e.g., C-PSCell 126B) and for zero or more C-SCells. In some implementations, MN 104A may include the first C-SN configuration message in an RRC container message. MN 104A then includes the first C-SN configuration or RRC container message for CSAC in a first conditional configuration field / IE and transmits a 408 first RRC reconfiguration message to UE 102 including the first conditional configuration field / IE. In some implementations, in response to the first RRC reconfiguration message, UE 102 transmits a 410 first RRC reconfiguration complete message to MN 104A. In response to the first RRC reconfiguration complete message, MN 104A may transmit a 412 SN message (e.g., an SN reconfiguration complete message or an SN change confirmation message) to C-SN 106B. Events 402-412 collectively define the CSAC configuration procedure 450.

[0129] In this example scenario, the MN 104A can transmit a first RRC reconfiguration message that includes a first conditional configuration, which includes only a first C-SN configuration, or alternatively, the first conditional configuration includes (i) the first C-SN configuration and (ii) at least one triggering condition. Additionally, the MN 104A can include a configuration ID in the first conditional configuration to identify either the first C-SN configuration or the first conditional configuration.

[0130] In some implementations, in event 407, C-SN 106B includes radio bearer configuration for conditional configuration in the SN request acknowledgment message, and in event 408, MN 104A may further include radio bearer configuration in the first RRC reconfiguration message. As described above, MN 104A may include radio bearer configuration at the level of the first RRC reconfiguration message, at the level of the first conditional configuration, or at the level of the RRC container message.

[0131] When transmitting a 408 First RRC Reconfiguration Message to UE 102, MN 104A can specify a condition that must be met before UE 102 applies the First C-SN Configuration for CSAC. MN 104A can specify this condition at the level of the First RRC Reconfiguration Message, the level of the RRC Container Message, the level of the First Conditional Configuration, or the level of the First C-SN Configuration for CSAC. In the First Conditional Configuration, MN 104A may, for example, include a First Configuration ID to identify the First C-SN Configuration for CSAC.

[0132] In some implementations, the SN request message 405 may be an SN add request message, and the SN request confirmation message 407 may be an SN add request confirmation message. In other implementations, the SN request message 405 may be an SN modify request message, and the SN request confirmation message 407 may be an SN modify request confirmation message. In some implementations, MN 104A instructs base station 106B in the SN request message 405 to request base station 106A to operate as the C-SN of UE 102. UE 102 may determine or identify that the first conditional configuration includes a first C-SN configuration, such that UE 102 may apply the first C-SN configuration for CSAC to communicate with C-SN 106B.

[0133] In some implementations, C-SN 106B specifies one or more conditions (“triggering conditions”) in the C-SN configuration for CSAC. In other implementations, MN 104A includes the C-SN configuration and one or more conditions in the first conditional configuration or the first RRC reconfiguration message. At event 407, MN 104A can generate the first conditional configuration for UE 102A or receive the first conditional configuration from C-SN 106B.

[0134] In some implementations, in response to the first interface message or determination 418, MN 104A may determine to release the first C-SN configuration. In response to this determination, MN 104A may send a conditional SN request message to instruct C-SN 106B to release the first C-SN configuration, and in response, send a conditional SN request confirmation message to MN 104A. In some implementations, the conditional SN request message may be an SN release request message, and the conditional SN request confirmation message may be an SN release request confirmation message. In other implementations, the conditional SN request message may be an SN modification request message, and the conditional SN request confirmation message may be an SN modification request confirmation message.

[0135] In some implementations, the C-SN configuration includes a CellGroupConfig IE that configures zero or more C-SCells of C-PSCell126B and C-SN 106B. In one implementation, the C-SN configuration may be an RRCReconfiguration message, RRCReconfiguration-IEs, or a CellGroupConfig IE conforming to 3GPP TS 38.331. In other implementations, the C-SN configuration includes an SCG-ConfigPartSCG-r12 IE that configures C-PSCells and may configure zero or more C-SCells of C-SN 106B. In one implementation, the C-SN configuration is an RRCConnectionReconfiguration message, RRCConnectionReconfiguration-IEs, or a ConfigPartSCG-r12 IE conforming to 3GPP TS 36.331.

[0136] In some implementations, C-SN 106B may include CU 172 and one or more DU 174, such as Figure 1C As shown. CU 172 receives an SN request message from MN 104A and sends an SN request confirmation message. In response to the SN request message, CU 172 may send a UE context establishment request message to DU 174. In response to the UE context establishment request message, DU 174 may generate a first C-SN configuration or a portion thereof (e.g., the identifier of UE 102, a dedicated random access preamble, or a random access configuration), and send the first C-SN configuration or a portion thereof to CU 172 in a UE context establishment response message. When DU 174 generates a portion of the first C-SN configuration, CU 172 may generate the remainder of the first C-SN configuration.

[0137] Now for reference Figure 4B Scenario 400B involves CSAC, i.e., when the UE is already in the DC with both the MN and SN, it conditionally changes from the PSCell of the SN to the C-PSCell of the C-SN. In this scenario, base station 104A operates as the MN, and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figure 4A and Figure 4B The differences between the scenarios.

[0138] In scenario 400B, if the second RRC reconfiguration does not include the C-SN configuration release field / IE indicating to UE 102 to release the C-SN configuration, then UE 102 does not release the first C-SN configuration in response to the second RRC reconfiguration message (event 456). In response to the first interface message or determination 418, MN 104A determines 457 to release the first C-SN configuration. In response to determination 457, MN 104A may send a conditional SN request message 460 to instruct C-SN 106B to release the first C-SN configuration, and C-SN 106B may send a conditional SN request confirmation message 462 to MN 104A as a response. In response to determination 457, MN 104A generates a third RRC reconfiguration message including the C-SN configuration release field / IE and transmits the third RRC reconfiguration message 464 to UE 102. In response to the C-SN configuration release field / IE, UE 102 releases the first C-SN configuration (481) and sends the third RRC reconfiguration message (466) to complete the third RRC reconfiguration. Events 416, 418, 452, 454, 456, and 458 collectively define the DRB reconfiguration procedure 495. Events 457, 460, 462, 464, 481, and 466 collectively define the conditional configuration release procedure 496. The DRB reconfiguration procedure 495 and the conditional configuration release procedure 496 can be executed in any order or in parallel.

[0139] In some implementations, MN 104A includes the C-SN configuration release field / IE in the second RRC reconfiguration message for adding, modifying, or releasing the DRB. Therefore, MN 104A does not transmit a third RRC reconfiguration message, and UE 102 does not transmit a third RRC reconfiguration complete message. In response to the C-SN configuration release field / IE in the second RRC reconfiguration message, UE 102 releases the first C-SN configuration (481).

[0140] The C-SN configuration release field / IE may include a first configuration ID, enabling UE 102 to use the C-SN configuration release field / IE (or the first configuration ID) to identify and release a first C-SN configuration or a first conditional configuration that includes the first C-SN configuration.

[0141] In some implementations, the MN 104A may include a C-SN configuration release field / IE in the radio bearer configuration, cell group configuration, or second or third RRC reconfiguration message. In some implementations, the conditional SN request message may be an SN release request message, and the conditional SN request confirmation message may be an SN release request confirmation message. In other implementations, the conditional SN request message may be an SN modification request message, and the conditional SN request confirmation message may be an SN modification request confirmation message.

[0142] When the MN 104A is implemented as an eNB or ng-eNB, the third RRC reconfiguration message is an RRCConnectionReconfiguration message, and the third RRC reconfiguration completion message is an RRCConnectionReconfigurationComplete message. When the MN 104A is implemented as a gNB, the third reconfiguration message is an RRCReconfiguration message, and the third RRC reconfiguration completion message is an RRCReconfigurationComplete message.

[0143] Now for reference Figure 4C Scenario 400C involves CSAC, i.e., when the UE is already in the DC with both the MN and SN, it conditionally changes from the PSCell of the SN to the C-PSCell of the C-SN. In this scenario, base station 104A operates as the MN, and base station 106A operates as the SN. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figure 3F , 4A -4B and Figure 4C The differences between the scenarios.

[0144] In response to the first interface message or confirmation 418, MN 104A confirms 459 to update the first C-SN configuration. In response to confirmation 459, MN 104A may send 461 a conditional SN request message to instruct C-SN 106B to update the first C-SN configuration, and in response, C-SN 106B may send a conditional SN request confirmation message to MN 104A including the second C-SN configuration. In response to the conditional SN request confirmation message, MN 104A generates a second conditional configuration field / IE including the second C-SN configuration and includes the second conditional configuration in a third RRC reconfiguration message. Then, MN 104A transmits 465 a third RRC reconfiguration message to UE 102. UE 102 updates 483 the first C-SN configuration or the first conditional configuration with the second C-SN configuration or the second conditional configuration, and in response to the third RRC reconfiguration message, transmits 467 a third RRC reconfiguration complete message. Events 459, 461, 463, 465, 483, and 466 together define the conditional reconfiguration procedure 497. The DRB reconfiguration procedure 495 and the conditional reconfiguration procedure 497 can be executed in any order or in parallel.

[0145] The second C-SN configuration may include configurations for C-PSCell (e.g., C-PSCell 126B) and for zero or one or more C-SCells. In some implementations, MN 104A may include the second C-SN configuration message in an RRC container message. MN 104A then includes the second C-SN configuration or RRC container message for CSAC in a second conditional configuration field / IE, and transmits a first RRC reconfiguration message including the second conditional configuration field / IE to UE 102. In some implementations, in response to the third RRC reconfiguration message, UE 102 transmits a third RRC reconfiguration complete message to MN 104A. In response to the third RRC reconfiguration complete message, MN 104A may transmit an SN message (e.g., an SN reconfiguration complete message) to C-SN 106B.

[0146] In some implementations, MN 104A includes the second C-SN configuration in the second RRC reconfiguration message for adding, modifying, or releasing a DRB, similar to the third RRC reconfiguration message. Therefore, MN 104A does not transmit the third RRC reconfiguration message, and UE 102 does not transmit the third RRC reconfiguration complete message. In response to the second RRC reconfiguration message, UE 102 updates the first C-SN configuration or the first conditional configuration with the second C-SN configuration or the second conditional configuration.

[0147] When the MN 104A is implemented as an ng-eNB, the third RRC reconfiguration message is an RRCConnectionReconfiguration message, and the third RRC reconfiguration completion message is an RRCConnectionReconfigurationComplete message. When the MN 104A is implemented as a gNB, the third RRC reconfiguration message is an RRCReconfiguration message, and the third RRC reconfiguration completion message is an RRCReconfigurationComplete message.

[0148] In some implementations, the conditional SN request message can be an SN add request message, and the conditional SN request confirmation message can be an SN add request confirmation message. In other implementations, the conditional SN request message can be an SN modify request message, and the conditional SN request confirmation message can be an SN modify request confirmation message. In some implementations, MN 104A can include SN configuration in the SN add request message. In other implementations, MN 104A may not include SN configuration in the SN add request message. In one implementation, MN 104A can include a cell identifier associated with the first C-SN configuration in the conditional SN request message, such that C-SN 106B can use the cell identifier to identify the first C-SN configuration based on the cell identifier and update the first C-SN configuration with the second C-SN configuration. In another implementation, MN 104A can include the first C-SN configuration in the conditional SN request message, such that C-SN 106B can identify the first C-SN configuration and update the first C-SN configuration with the second C-SN configuration.

[0149] In some implementations, UE 102 replaces the first C-SN configuration with a second C-SN configuration; that is, UE 102 releases the first C-SN configuration and stores the second C-SN configuration. In other implementations, UE 102 replaces the first conditional configuration with a second conditional configuration; that is, UE 102 releases the first conditional configuration and stores the second conditional configuration. In one implementation, MN 104A may include a C-SN configuration release field / IE for releasing the first C-SN configuration in the second RRC reconfiguration message or the third RRC reconfiguration message. In another implementation, MN 104A does not include the C-SN configuration release field / IE for releasing the first C-SN configuration in the second RRC reconfiguration message and the third RRC reconfiguration message. In this case, the second configuration ID in the second conditional configuration has the same value as the first configuration ID in the first conditional configuration, allowing UE 102 to identify the first C-SN configuration or the first conditional configuration to be replaced.

[0150] Optionally, UE 102 may detect that condition 434 is met for connecting to C-PSCell 126B, and in response to this detection, initiate a random access procedure on C-PSCell 126B. For convenience, this discussion may refer to conditions or configurations in the singular, but it will be understood that multiple conditions may exist, and a conditional configuration may include one or more configuration parameters to specify conditions or multiple conditions. In any case, UE 102 performs the random access procedure 436 with C-SN 106B via C-PSCell 126B using the random access configuration included in the second C-SN configuration. In response to event 434 or 436, UE 102 in the DC may disconnect from SN 106A (i.e., the PSCell and all SCells of SN 106A, if configured). In response to event 434 or 436, UE 102 may send a 438RRC reconfiguration complete message to MN 104A. Before or after event 436, or while UE 102 is performing the 436 random access procedure, UE 102 may transmit a 438 RRC reconfiguration complete message. In response to the RRC reconfiguration complete message 438, MN 104A may transmit a 440 SN message (e.g., an SN reconfiguration complete message) to C-SN 106B.

[0151] In some implementations, the random access procedure may be a four-step random access procedure or a two-step random access procedure. In other implementations, the random access procedure may be a contention-based random access procedure or a contention-free random access procedure. After UE 102 successfully completes the 436 random access procedure, C-SN 106B begins operating as SN 106B, and UE 102 begins operating in the DC with MN 104A and SN 106B 442. Specifically, UE 102 communicates with SN 106B via C-PSCell 126B (i.e., the new PSCell 126B) according to the second C-SN configuration for CSAC 442.

[0152] In some implementations, C-SN 106B identifies UE 102 if it finds the identifier of UE 102 in the Media Access Control (MAC) Protocol Data Unit (PDU) received from UE 102 during the random access procedure (Event 436). C-SN 106B includes the identifier of UE 102 in the second C-SN configuration. In other implementations, C-SN 106B identifies UE 102 if it receives a dedicated random access preamble from UE 102 during the random access procedure. C-SN 106B includes the dedicated random access preamble in the second C-SN configuration.

[0153] In some implementations, C-SN 106B may include CU 172 and one or more DU 174, such as Figure 1CAs illustrated, CU 172 receives an SN request message and a conditional SN request message from MN 104A, and in response, sends an SN request confirmation message and a conditional SN request confirmation message to MN 104A. In response to the conditional SN request message, CU 172 may send a UE context establishment request message or a UE context modification request message to DU 174. In response to the UE context establishment request message or the UE context modification request message, DU 174 may generate a second C-SN configuration or a portion thereof (e.g., the identifier of UE 102, a dedicated random access preamble, a random access configuration), and send the C-SN configuration or a portion thereof to CU 172 in the UE context establishment response message or the UE context modification response message. When DU 174 generates a portion of the second C-SN configuration, CU 172 may generate the remainder of the second C-SN configuration. In one implementation, DU 174 may perform a random access procedure (event 436) with UE 102 and identify UE 102 during the random access procedure. In response to this identification, DU 174 communicates with UE 102 using a second C-SN configuration or a portion thereof. If DU 174 can identify UE 102 during the random access procedure, DU 174 may send an indication (e.g., a downlink data delivery status message) to CU 172. In another embodiment, DU 174 may perform a random access procedure (event 436) with UE 102 and forward the identifier of UE 102 received in the MAC PDU during the random access procedure to CU 172. CU 172 identifies UE 102 based on the identifier of UE 102. In response to this identification, CU 172 and DU 174 communicate with UE 102 using the remainder of the second C-SN configuration and a portion thereof, respectively.

[0154] If C-SN 106B (or DU 174) identifies UE 102 on C-PSCell 126B during event 436, then C-SN 106B (or DU 174) begins transmitting multiple downlink control information (DCI) commands, multiple reference signals, or data on the Physical Downlink Control Channel (PDCCH) to UE 102 via C-PSCell 126B and / or one or more C-SCells (if configured in the second C-SN configuration), according to some configuration parameters in the second C-SN configuration. If C-SN 106B (or DU 174) identifies UE 102 on C-PSCell 126B during event 436, C-SN 106B (or DU 174) may, according to some configuration parameters in the second C-SN, receive signals, probe reference signals, or data on the Physical Uplink Control Channel (PUCCH) from UE 102 via C-PSCell 126B and / or one or more C-SCells (if configured in the second C-SN configuration). According to some configuration parameters in the second C-SN configuration, UE 102 receives, via C-PSCell 126B and / or one or more C-SCells (if configured in the C-SN configuration), multiple DCI commands, reference signals, or data on the PDCCH from C-SN 106B (or DU 174). Based on certain configuration parameters in the second C-SN configuration, UE 102 can transmit signals, probe reference signals, or data on PUCCH(s) to C-SN106B (or DU 174) via C-PSCell 126B and one or more C-SCells (if configured in the C-SN configuration). In response to this identification, C-SN 106B becomes SN 106B, and it is determined that C-PSCell 126B becomes PSCell 126B, and one or more C-SCells become one or more scells. In response to an indication received from MN 104A (e.g., a downlink data delivery status message), SN message 440, or RRC reconfiguration complete message 438, CU 172 can begin transmitting DL PDUs (e.g., PDCP PDUs) to UE 102 via DU 174.

[0155] As described above, before C-PSCell 126B becomes suitable for UE 102, MN 104A and C-SN 106B pre-configure the C-PSCell (e.g., C-PSCell 126B) to UE 102 during events 461 and 463. When the C-PSCell becomes suitable for UE 102 (i.e., UE 102 detects the corresponding condition), UE 102 performs a random access procedure with the C-PSCell to quickly change the PSCell (i.e., change the SN). In contrast to the immediate SN change procedure, the conditional SN change technique discussed in this disclosure significantly reduces the latency associated with DC configuration.

[0156] Example implementations of the second C-SN configuration can be similar to the first C-SN configuration. Example implementations of the second conditional configuration can be similar to the first conditional configuration. In some implementations, MN 104A may include new conditions or conditions to be evaluated by UE 102 in the second conditional configuration or the second RRC reconfiguration message. At event 434, UE 102 uses the new conditions in the second conditional configuration or the second RRC reconfiguration message or uses the existing conditions. In other implementations, at event 434, MN 104A does not include conditions for UE 102 to evaluate in the second conditional configuration or the second RRC reconfiguration message, such that UE 102 reuses the conditions in the first conditional configuration or the first RRC reconfiguration message.

[0157] Next, refer to Figures 5A-6C The discussion involves several example scenarios involving conditional switching (CHO).

[0158] Figure 5A The illustration depicts scenario 500A involving conditional handover. In this scenario, for conditional handover, base station 104A operates as the MN, and base station 104B operates as the candidate base station (C-MN). Events 516 and 518 are similar to events 316 and 318.

[0159] In this scenario, UE 102 communicates with MN 104A according to the MN configuration 502. UE 102 can be in the SC with MN 104A, or in the DC with MN 104A and SN 106A. MN 104A determines 504 that it should request a first C-MN configuration for UE 102. The first C-MN configuration configures the candidate PCell (C-PCell) 124B of C-MN 104B. MN 104A can make this determination based on one or more measurements received directly from the UE (e.g., via an SRB established between UE 102 and MN 104A or via a physical control channel), or by one or more measurements obtained by MN 104A from measurements received from, for example, signals, control channels, or data channels from UE 102, or another suitable event. More intelligently, based on uplink signals received from UE 102 or multiple positioning measurement results received from UE 102, MN 104A can deduce or estimate that UE 102 is moving towards the coverage area of ​​cell 124B or C-MN 104B. In response to this determination, MN 104A sends a 506 conditional handover request message to C-MN 104B.

[0160] In response to the conditional handover request message, C-MN 104B generates a first C-MN configuration (508). C-MN 104B then sends a conditional handover request confirmation message (510) including the first C-MN configuration to MN 104A. MN 104A includes the first C-MN configuration in the first conditional configuration and sends a first RRC reconfiguration message (512) including the first conditional configuration to UE 102. In response to the first RRC reconfiguration message (512), UE 102 can send a first RRC reconfiguration complete message (514) to MN 104A. Events 502-514 can collectively define the conditional handover procedure (550).

[0161] In some implementations, the conditional handover request message may be a handover request message, and the conditional handover request confirmation message may be a handover request confirmation message as defined in 3GPP specifications 36.423 or 38.423. MN 104A may include a conditional handover request indication in the handover request message. In some implementations, MN 104A may include MN configuration in the handover request message. In other implementations, MN 104A may not include MN configuration in the handover request message.

[0162] In this example scenario, MN 104A can transmit a first RRC reconfiguration message including a first conditional configuration, which includes only the first C-MN configuration, or alternatively, the first conditional configuration includes (i) the first C-MN configuration and (ii) at least one triggering condition. In some implementations, MN 104A can assign a first configuration ID to identify the first conditional configuration or the first C-MN configuration, and include the first configuration ID in the first conditional configuration. Additionally, MN 104A can include a configuration ID in the first conditional configuration to identify the first C-MN configuration or the first conditional configuration.

[0163] Subsequently, MN 104A receives a first interface message 516 from CN 110 (e.g., MME 114 or AMF 164). In response to the first interface message, MN 104A determines 518 to add, modify, or release the DRB. MN 104A may send a second interface message to CN 110 in response to the first interface message. In one embodiment, MN 104A determines to add a new DRB in response to the first interface message. In another embodiment, MN 104A determines to modify or release an existing DRB configured for UE 102 in response to the first interface message. For example, MN 104A may determine to modify the DRB by modifying or releasing radio resources used for the DRB. Radio resources may include one or more RLC bearer or Quality of Service (QoS) mapping configurations (e.g., adding a new QoS flow and mapping that new QoS flow to an existing DRB or releasing an existing QoS flow). In one embodiment, the DRB may be an MN-terminated DRB. In another embodiment, the DRB may be an SN-terminated DRB utilizing the radio resources of SN 106A. In response to a second RRC reconfiguration message, UE 102 may release or modify radio resources. In the following description, "add, modify, or release DRB" may mean "add a new DRB" or "modify or release an existing DRB".

[0164] In response to determination 518, MN 104A transmits a second RRC reconfiguration message 530 (adding, modifying, or releasing the DRB) to UE 102. In response to the second RRC reconfiguration message (adding, modifying, or releasing the DRB), UE 102 ignores the first C-MN configuration 582. In response to the second RRC reconfiguration message, UE 102 transmits a second RRC reconfiguration complete message 532. In the second RRC reconfiguration, MN 104A does not include the C-MN configuration release field / IE that instructs UE 102 to release the first C-MN configuration.

[0165] As described below, the second RRC reconfiguration message can be generated by MN 104A. In some implementations, MN104A can generate radio bearer configurations (e.g., RadioBearerConfig) IEs that add, modify, or release DRBs. MN104A can generate the second RRC reconfiguration message and include the radio bearer configuration in the second RRC reconfiguration message.

[0166] In other implementations, MN 104A can generate a cell group configuration (e.g., CellGroupConfigIE or RadioResourceConfigDedicatedIE) that modifies the DRB (i.e., modifies the existing DRB configured for UE 102). MN 104A includes the cell group configuration in the second RRC reconfiguration message.

[0167] Similar to the C-SN configuration discussed above, the first C-MN configuration can be a complete and self-contained configuration (i.e., a full configuration). In the first C-MN configuration, C-MN 104B may include a full configuration indication (information element (IE) or field) indicating that the first C-MN configuration is a complete and self-contained configuration (i.e., a full configuration). If UE 102 is connected to C-MN 104B, UE 102 can directly use the first C-MN configuration to communicate with C-MN 104B without referring to a previously received MN configuration. In other embodiments, the first C-MN configuration may include one or more configurations on top of the MN configuration (i.e., an incremental configuration). If UE 102 is connected to C-MN 104B, UE 102 can use both the first C-MN configuration and the MN configuration to communicate with C-MN 104B.

[0168] The first C-MN configuration may include multiple configuration parameters for UE 102 to communicate with C-MN 104B via C-PCell 124B. These configuration parameters can configure radio resources for UE 102 to communicate with C-MN 104B via zero or more candidate secondary cells (C-SCells) of C-PCell 124B and C-MN 104B. The multiple configuration parameters can configure zero or more radio bearers. The one or more radio bearers may include (multiple) SRBs and / or (multiple) DRBs. The (multiple) SRBs may include SRB1 and / or SRB2.

[0169] In some implementations, C-MN 104B may be pre-configured to generate a complete configuration for the C-MN configuration, and a complete configuration indication may be included in the C-MN configuration. In other implementations, if C-MN 104B determines that MN 104A is from a different manufacturer, C-MN 104B may determine to generate a complete configuration for the C-MN configuration, and a complete configuration indication may be included in the C-MN configuration. In other implementations, if C-MN 104B cannot generate an incremental configuration for the C-MN configuration based on the MN configuration received in the conditional handover request message 506, C-MN 104B may determine that it should generate a complete configuration for the C-MN configuration, and a complete configuration indication may be included in the C-MN configuration. For example, MN 104A may indicate that the MN configuration is not up-to-date, preventing C-MN 104B from using the MN configuration to generate an incremental configuration for the C-MN configuration. In a further implementation, MN 104A may instruct C-MN 104B to generate a complete configuration for the C-MN configuration, and a complete configuration indication may be included in the C-MN configuration. In another implementation, if C-MN 104B determines that MN 104A operates from the same manufacturer or is pre-configured to do so, C-MN 104B may determine that it should generate an incremental C-MN configuration in a conditional switch request confirmation message during the conditional switch process.

[0170] Similar to incremental C-SN configuration, incremental C-MN configuration is not a complete configuration and does not include a complete configuration indication. UE102 cannot communicate with C-MN 104B using only the incremental C-MN configuration; UE102 must also reference the MN configuration stored in UE102. The incremental C-MN configuration may include one or more configuration parameters for UE102 to communicate with C-MN 104B via C-PCell 124B. Multiple configuration parameters can configure radio resources for UE102 to communicate with C-MN 104B via zero or one or more C-SCells of C-PCell 124B and C-MN 104B. Multiple configuration parameters may or may not configure zero or one or more radio bearers. One or more radio bearers may include SRBs and / or (multiple) DRBs. Multiple configuration parameters may or may not include measurement configurations and / or security configurations.

[0171] The MN configuration may include multiple configuration parameters for UE 102 to communicate with MN 104A via zero or more secondary cells (SCcells) of PCell 124A and MN 104A. These configuration parameters can configure radio resources for UE 102 to communicate with MN 104A via zero or more SCcells of PCell 124A and MN 104A. The configuration parameters can also configure zero or more radio bearers. One or more radio bearers may include (multiple) SRBs and / or (multiple) DRBs. The (multiple) SRBs may include SRB1 and / or SRB2.

[0172] MN 104A can include the conditions to be evaluated by UE102 in the first conditional configuration or the first RRC reconfiguration message.

[0173] Furthermore, similar to the C-SN configuration, the first C-MN configuration may include a CellGroupConfig IE configuring the C-PCell 124B, and may configure zero or one or more C-SCells of the C-MN 104B. In one embodiment, the first C-MN configuration may be an RRCReconfiguration message, RRCReconfiguration-IEs, or CellGroupConfigIE conforming to 3GPP TS38.331. The complete configuration indication may be a field or IE conforming to 3GPP TS38.331. In other embodiments, the first C-MN configuration may include a RadioResourceConfigDedicated IE and / or MobilityControlInfo IE configuring the C-PCell 124B, and may or may not include an SCellToAddModList IE configuring one or more C-SCells of the C-MN 104B. In one embodiment, the first C-MN configuration may be an RRCConnectionReconfiguration message or RRCConnectionReconfiguration-IEs conforming to 3GPP TS 36.331. The full configuration instruction can be a field conforming to 3GPP TS 36.331 or an IE.

[0174] In some implementations, the MN configuration may include a CellGroupConfig IE configuring PCell 124A, and may configure zero or one or more SCcells of MN 104A. In one implementation, the MN configuration is an RRCReconfiguration message, RRCReconfiguration-IEs, or a CellGroupConfig IE conforming to 3GPP TS38.331. In other implementations, the MN configuration may include a RadioResourceConfigDedicated IE and / or a MobilityControlInfo IE configuring PCell 124A, and may or may not include an SCellToAddModList IE configuring one or more SCcells of MN 104A.

[0175] If MN 104A is implemented as a gNB, the first and second RRC reconfiguration messages and the first and second RRC reconfiguration completion messages can be RRCReconfiguration messages and RRCConnectionReconfigurationComplete messages, respectively. If MN 104A is implemented as an eNB or ng-eNB, the first and second RRC reconfiguration messages and the first and second RRC reconfiguration completion messages can be implemented as RRCReconfiguration messages and RRCConnectionReconfigurationComplete messages, respectively.

[0176] In some implementations, C-MN 104B may include CU 172 and one or more DU 174, such as Figure 1B As shown. CU 172 receives a conditional handover request message from MN 104A and sends a conditional handover request confirmation message. In response to the conditional handover request message, CU 172 may send a UE context establishment request message to DU 174. In response to the UE context establishment request message, DU 174 may generate a first C-MN configuration or a portion thereof, and send the first C-MN configuration or a portion thereof to CU 172 in a UE context establishment response message. When DU 174 generates a portion of the first C-MN configuration, CU 172 may generate the remainder of the first C-MN configuration.

[0177] Now for reference Figure 5BScenario 500B involves conditional handover. In this scenario, for conditional handover, base station 104A operates as the MN, and base station 104B operates as the candidate base station (C-MN). In this scenario, events similar to those discussed above are labeled with the same reference numbers. The following discussion... Figure 5A and Figure 5B The differences between the scenarios.

[0178] In scenario 500B, in response to the first interface message or determination 518, MN 104A determines 557 to release the first C-MN configuration. In response to determination 557, MN 104A may send a conditional handover cancellation message 560 to instruct C-MN 104B to release the first C-MN configuration and generate a C-MN configuration release field / IE, which instructs UE 102 to release the first C-MN configuration or the first conditional configuration. In some implementations, MN 104A may send the conditional handover cancellation message before, during, or after transmitting the second RRC reconfiguration message. In response to determination 518, MN 104A transmits a second RRC reconfiguration message to UE 102, 530, to add, modify, or release a DRB and including the C-MN configuration release field / IE. In response to the C-MN configuration release field / IE, UE 102 releases 581 the first C-MN configuration or the first conditional configuration. The C-MN configuration release field / IE may include a first configuration ID, enabling UE 102 to use the C-MN configuration release field / IE (or the first configuration ID) to identify and release a first C-MN configuration or a first conditional configuration that includes the first C-MN configuration.

[0179] In some implementations, MN 104A may include C-MN configurations to release the field / IE in the second RRC reconfiguration message, radio bearer configuration, or cell group configuration generated by MN 104A. In some implementations, the conditional handover cancellation message may be a handover cancellation message as defined in 3GPP specifications 36.423 or 38.423. In one implementation, MN 104A may include a cell identifier associated with the first C-MN configuration in the handover cancellation message, such that C-MN 104B can use the cell identifier to identify the first C-MN configuration based on the cell identifier. For example, the cell identifier may be the cell global identifier (CGI) or physical cell identifier of the cell configured in the first C-MN configuration. In another implementation, MN 104A may not include the cell identifier, but may include a conditional handover release indication in the handover cancellation message. In response to the conditional handover release indication, C-MN 104B releases all(multiple) C-MN configurations(including the first C-MN configuration) configured for UE 102. In another implementation, MN 104A includes neither a cell identifier nor a conditional handover release indication. In response to the handover cancellation message, C-MN 104B releases all (including the first) C-MN configurations configured for UE 102.

[0180] Now for reference Figure 5C Scenario 500C involves conditional handover. In this scenario, for conditional handover, base station 104A operates as the MN, and base station 104B operates as the candidate base station (C-MN). In this scenario, events similar to those discussed above are labeled with the same reference numbers. The following discussion... Figures 5A-5B and Figure 5C The differences between the scenarios.

[0181] In scenario 500C, in response to the first interface message or confirmation 518, MN 104A determines 559 to update the first C-MN configuration. In response to confirmation 559, MN 104A may send a conditional handover request message 562 to C-MN 104B. In response to the conditional handover request message, C-MN 104B generates a second C-MN configuration 564 to configure the C-PCell (e.g., C-PCell 124B or another C-PCell). C-MN 104B sends a conditional handover request confirmation message 566 to MN 104A including the second C-MN configuration. After receiving the conditional handover request confirmation message 518, MN 104A generates a second conditional configuration field / IE including the second MN configuration and transmits a second RRC reconfiguration message 530 to UE 102, which adds, modifies, or releases the DRB and includes the second conditional configuration field / IE. In response to the second RRC reconfiguration message, UE 102 updates the first C-MN configuration at 583 with the second C-MN configuration. The second RRC reconfiguration message at event 531 is similar to the second RRC reconfiguration message at event 530 in this scenario, except that the second RRC reconfiguration at event 531 includes the second C-MN configuration.

[0182] In some implementations, MN 104A may assign a second configuration ID that identifies the second conditional configuration or the second C-MN configuration, and include the second configuration ID in the second conditional configuration.

[0183] In some implementations, the conditional handover request message 562 may be a handover request message, and the conditional handover request confirmation message 566 may be a handover request confirmation message as defined in 3GPP specifications 36.423 or 38.423. MN 104A may include a conditional handover request indication in the handover request message. In some implementations, MN 104A may include an MN configuration in the handover request message. In other implementations, MN 104A may not include an MN configuration in the handover request message. In one implementation, MN 104A may include a cell identifier associated with the first C-MN configuration in the handover request message, such that C-MN 104B can use the cell identifier to identify the first C-MN configuration based on the cell identifier and update the first C-MN configuration with a second C-MN configuration. In another implementation, MN 104A may include the first C-MN configuration in the handover request message, such that C-MN 104B can identify the first C-MN configuration and update the first C-MN configuration with a second C-MN configuration.

[0184] In some implementations, UE 102 replaces the first C-MN configuration with a second C-MN configuration; that is, UE 102 releases the first C-MN configuration and stores the second C-MN configuration. In other implementations, UE 102 replaces the first conditional configuration with a second conditional configuration; that is, UE 102 releases the first conditional configuration and stores the second conditional configuration. In one implementation, MN 104A may include a C-MN configuration release field / IE for releasing the first C-MN configuration in the second RRC reconfiguration message. In another implementation, MN 104A does not include a C-MN configuration release field / IE for releasing the first C-MN configuration in the second RRC reconfiguration message. In this case, the second configuration ID in the second conditional configuration has the same value as the first configuration ID in the first conditional configuration, allowing UE 102 to identify the first C-MN configuration or the first conditional configuration to be replaced based on the second configuration ID.

[0185] Later, UE 102 may detect that condition 534 (or more conditions) for connecting to C-PCell 124B is met, and in response to this detection, initiate random access procedure 534 on C-PCell 124B. For convenience, this discussion may refer to conditions or configurations in the singular, but it will be understood that multiple conditions may exist, and conditional configurations may include one or more configuration parameters to specify conditions or multiple conditions. In response to this initiation, UE 102 may perform random access procedure 536 with C-MN 104B via C-PCell 124B using the random access configuration in the second C-MN configuration. In response to the initiation or detection, UE 102 may disconnect from PCell 124A of MN 104A. In response to the second C-MN configuration, UE 102 may transmit conditional handover completion message 538 to C-MN 104B via C-PCell 124B during / after random access procedure 536.

[0186] After UE 102 successfully completes the random access procedure 536 or transmits the conditional handover completion message 538, UE 102 may communicate with C-MN 104B via C-PCell 124B (i.e., the new PCell 124B) according to the second C-MN configuration 542. UE 102 may transmit the conditional handover completion message 538 during or after the random access procedure.

[0187] In some implementations, the random access procedure may be a four-step random access procedure or a two-step random access procedure. In other implementations, the random access procedure may be a contention-based random access procedure or a contention-free random access procedure. In some implementations, UE 102 may transmit a conditional handover completion message in message 3 of a four-step random access procedure or in message A of a two-step random access procedure.

[0188] Similar to the scenarios discussed above, C-MN 104B can, for example, use a MAC PDU to determine the identifier of UE102.

[0189] Example implementations of the second C-MN configuration can be similar to the first C-MN configuration. Example implementations of the second conditional configuration can be similar to the first conditional configuration. In some implementations, MN 104A may include the condition or a new condition to be evaluated by UE 102 in the second conditional configuration. At event 534, UE 102 uses the new condition in the second conditional configuration or reuses the condition. In other implementations, MN 104A does not include the condition to be evaluated by UE 102 in the second conditional configuration or the second RRC reconfiguration message, such that UE 102 reuses the condition in the first conditional configuration at event 534.

[0190] In some implementations, C-MN 104B may include CU 172 and one or more DU 174, such as Figure 1BAs shown. CU 172 receives a conditional handover request message from MN 104A and sends a conditional handover request confirmation message. In response to the conditional handover request message, CU 172 may send a UE context establishment request message or a UE context modification request message to DU 174. DU 174 may generate a second C-MN configuration or a portion thereof, and send the second C-MN configuration or a portion thereof to CU 172 in a UE context establishment response message or a UE context modification response message. When DU 174 generates a portion of the second C-MN configuration, CU 172 may generate the remainder of the second C-MN configuration. In one implementation, DU 174 may perform a 536 random access procedure with UE 102 and identify UE 102 during the random access procedure. In response to this identification, DU 174 communicates with UE 102 using the second C-MN configuration or a portion thereof. If DU 174 can identify UE 102 during the random access procedure, DU 174 can send an indication (e.g., a downlink data delivery status message) to CU 172. In another embodiment, DU 174 can perform a random access procedure 536 with UE 102 and forward the identifier of UE 102 received in the MAC PDU during the random access procedure to CU 172. CU 172 identifies UE 102 based on the identifier of UE 102. In response to this identification, CU 172 and DU 174 communicate with UE 102 using the remainder of the second C-MN configuration and a portion of the second C-MN configuration, respectively. In response to an indication (e.g., a downlink data delivery status message) received from MN 104A or an RRC reconfiguration complete message 538, CU 172 can begin transmitting DL PDUs (e.g., PDCP PDUs) to UE 102 via DU 174.

[0191] If, at event 536, C-MN 104B (or DU 174) identifies UE 102 on C-PCell 124B, then C-MN 104B (i.e., becomes MN 104B) (or DU 174) begins transmitting downlink control information (DCI) commands, reference signals, or data on (multiple) physical downlink control channels (PDCCHs) to UE 102 via C-PCell 124B and / or one or more C-SCells (if configured in the second C-MN configuration), according to some configuration parameters in the second C-MN configuration. If, in event 536, C-MN 104B (or DU 174) identifies UE102 on C-PCell 124B, then C-MN 104B (or DU 174) may, according to some configuration parameters in the second C-MN configuration, receive from UE102 via C-PCell 124B and / or one or more C-SCcells (if configured in the C-MN configuration) multiple signals, multiple probe reference signals, or data on PDCCH. According to some configuration parameters in the second C-MN configuration, UE102 may receive from C-MN 104B (or DU 174) via C-PCell 124B and / or one or more C-SCcells (if configured in the second C-MN configuration) multiple DCI commands, multiple reference signals, or data on PDCCH. Based on certain configuration parameters in the second C-MN configuration, UE 102 can transmit multiple signals, multiple probe reference signals, or data on the PUCCH to C-MN 104B (or DU 174) via C-PCell 124B and one or more C-SCcells (if configured in the second C-MN configuration). In response to this identification, C-MN 104B becomes MN 104B, and it is determined that C-PCell 124B becomes PCell 124B, and one or more C-SCells become one or more SCells.

[0192] Now for reference Figure 6A Scenario 600A involves conditional handover, where base station 104 operates as an MN, which includes cell 124A operating as a C-PCell conditional handover. Events 616 and 618 are similar to events 316 and 318.

[0193] In this scenario, UE 102 communicates with MN 104A according to the MN configuration 602. UE 102 can be in the SC with MN 104A, or in the DC with MN 104A and SN 106A. MN 104A determines 604 that it should request a first C-MN configuration for UE 102. The first C-MN configuration configures the C-PCell 124A of MN 104A. MN 104A can make this determination based on one or more measurements received directly from the UE (e.g., via an SRB established between UE 102 and MN 104A or via a physical control channel), or one or more measurements obtained by MN 104A from measurements received by, for example, signals, control channels, or data channels from UE 102, or another suitable event. More intelligently, based on uplink signals received from UE 102 or multiple positioning measurement results received from UE 102, MN 104A can derive or estimate that UE 102 is moving toward the coverage area of ​​cell 124A.

[0194] MN 104A generates a first C-MN configuration and includes it in a first conditional configuration, and sends a first RRC reconfiguration message 612, including the first conditional configuration, to UE 102. In response to the first RRC reconfiguration message 612, UE 102 can send a first RRC reconfiguration complete message 614 to MN 104A. Events 602-614 can collectively define the conditional handover procedure 650.

[0195] In this example scenario, MN 104A can transmit a first RRC reconfiguration message including a first conditional configuration, which includes only the first C-MN configuration, or alternatively, the first conditional configuration includes (i) the first C-MN configuration and (ii) at least one triggering condition. In some implementations, MN 104A can assign a first configuration ID to identify the first conditional configuration or the first C-MN configuration, and include the first configuration ID in the first conditional configuration. Additionally, MN 104A can include a configuration ID in the first conditional configuration to identify the first C-MN configuration or the first conditional configuration.

[0196] Subsequently, MN 104A receives a first interface message 616 from CN 110 (e.g., MME 114 or AMF 164). In response to the first interface message, MN 104A determines 618 to add, modify, or release the DRB. MN 104A may send a second interface message to CN 110 in response to the first interface message. In one embodiment, MN 104A determines to add a new DRB in response to the first interface message. In another embodiment, MN 104A determines to modify or release an existing DRB configured for UE 102 in response to the first interface message. For example, MN 104A may determine to modify the DRB by modifying or releasing radio resources used for the DRB. Radio resources may include one or more RLC bearer or Quality of Service (QoS) mapping configurations (e.g., adding a new QoS flow and mapping that new QoS flow to an existing DRB or releasing an existing QoS flow). In one embodiment, the DRB may be an MN-terminated DRB. In another embodiment, the DRB may be an SN-terminated DRB utilizing the radio resources of SN 106A. In response to a second RRC reconfiguration message, UE 102 may release or modify radio resources. In the following description, "add, modify, or release DRB" may mean "add a new DRB" or "modify or release an existing DRB".

[0197] In response to confirmation 6, MN 104A transmits a second RRC reconfiguration message 630 (Adding, Modifying, or Releasing the DRB) to UE 102. In response to adding, modifying, or releasing the DRB, UE 102 ignores the first C-MN configuration 682. In response to the second RRC reconfiguration message, UE 102 transmits a second RRC reconfiguration complete message 632. In the second RRC reconfiguration, MN 104A does not include the C-MN configuration release field / IE that instructs UE 102 to release the first C-MN configuration.

[0198] As described below, the second RRC reconfiguration message can be generated by MN 104A. In some implementations, MN 104A can generate radio bearer configurations (e.g., radio bearer configurations) IEs that add, modify, or release DRBs. MN 104A can generate the second RRC reconfiguration message and include the radio bearer configuration in the second RRC reconfiguration message.

[0199] In other implementations, MN 104A can generate a cell group configuration (e.g., CellGroupConfigIE or RadioResourceConfigDedicatedIE) for modifying the DRB (i.e., the existing DRB configured for UE102). MN 104A includes the cell group configuration in the second RRC reconfiguration message.

[0200] The first C-MN configuration may include multiple configuration parameters for UE 102 to communicate with MN 104A via C-PCell 124A. These configuration parameters can configure radio resources for UE 102 to communicate with MN 104A via C-PCell 124A and zero or more candidate secondary cells (C-SCells) of MN 104A. The multiple configuration parameters can configure zero or more radio bearers. The one or more radio bearers may include (multiple) SRBs and / or (multiple) DRBs. The (multiple) SRBs may include SRB1 and / or SRB2. MN 104A may include the conditions to be evaluated by UE 102 in the first conditional configuration or the first RRC reconfiguration message.

[0201] In some implementations, MN 104A may include CU 172 and one or more DU 174, such as Figure 1B As shown. The UE communicates with MN 104A via the first DU 174 operating PCell 302. In response to determination 604, CU 172 may send a UE context establishment request message to DU 174. In response to the UE context establishment request message, the second DU 174 may generate a first C-MN configuration or a portion thereof, and send the first C-MN configuration or a portion thereof to CU 172 in a UE context establishment response message. When the second DU 174 generates a portion of the first C-MN configuration, CU 172 may generate the remainder of the first C-MN configuration. If the first DU 174 also operates C-PSCell 126A, CU 172 may send a UE context modification request message to the first DU 174. In response to the UE context modification request message, the first DU 174 may generate a first C-MN configuration or a portion thereof, and send the first C-MN configuration or a portion thereof to CU 172 in a UE context modification response message. When the first DU 174 generates a portion of the first C-MN configuration, the CU172 can generate the remainder of the first C-MN configuration.

[0202] Now for reference Figure 6B Scenario 600B involves conditional handover. In this scenario, base station 104A operates as the MN, which includes cell 124A as a C-PCell operation for conditional handover. In this scenario, events similar to those discussed above are labeled with the same reference numerals. The following discussion... Figure 6A and Figure 6B The differences between the scenarios.

[0203] In scenario 600B, in response to the first interface message or determination 618, MN 104A determines 657 to release the first C-MN configuration. In response to determination 657, MN 104A may generate a C-MN configuration release field / IE, which instructs UE 102 to release the first C-MN configuration or the first conditional configuration. In response to determination 618, MN 104A transmits a second RRC reconfiguration message 629 to UE 102 for adding, modifying, or releasing a DRB and including the C-MN configuration release field / IE. In response to the C-MN configuration release field / IE, UE 102 releases 681 the first C-MN configuration or the first conditional configuration. The C-MN configuration release field / IE may include a first configuration ID, allowing UE 102 to use the C-MN configuration release field / IE (or the first configuration ID) to identify and release the first C-MN configuration or the first conditional configuration including the first C-MN configuration.

[0204] In some implementations, MN 104A may include a C-MN configuration release field / IE in the second RRC reconfiguration message, radio bearer configuration, or cell group configuration generated by MN 104A. In response to determining that the first C-MN configuration is being released, MN 104A may release all(multiple) C-MN configurations(including the first C-MN configuration) configured for UE 102.

[0205] Now for reference Figure 6C Scenario 600C involves conditional handover. In this scenario, base station 104A performs an MN operation including cell 124A, which in turn performs a C-PCell operation for conditional handover. Events similar to those discussed above in this scenario are labeled with the same reference numerals. The following discussion... Figures 6A-6B and Figure 6C The differences between the scenarios.

[0206] In scenario 600C, in response to the first interface message or determination 618, MN 104A determines 659 to update the first C-MN configuration. In response to determination 559, MN 104A may generate a second C-MN configuration for configuring a C-PCell (e.g., C-PCell 124A or another C-PCell). MN 104A generates a second conditional configuration field / IE that includes the second C-MN configuration and transmits a second RRC reconfiguration message 631, which adds, modifies, or releases a DRB and includes the second conditional configuration field / IE, to UE 102. In response to the second RRC reconfiguration message, UE 102 updates the first C-MN configuration 683 with the second C-MN configuration. The second RRC reconfiguration message at event 631 is similar to the second RRC reconfiguration message at event 630 in this scenario, except that the second RRC reconfiguration at event 631 includes the second C-MN configuration.

[0207] In some implementations, MN 104A may assign a second configuration ID that identifies the second conditional configuration or the second C-MN configuration, and include the second configuration ID in the second conditional configuration.

[0208] In some implementations, UE 102 replaces the first C-MN configuration with a second C-MN configuration; that is, UE 102 releases the first C-MN configuration and stores the second C-MN configuration. In other implementations, UE 102 replaces the first conditional configuration with a second conditional configuration; that is, UE 102 releases the first conditional configuration and stores the second conditional configuration. In one implementation, MN 104A may include a C-MN configuration release field / IE for releasing the first C-MN configuration in the second RRC reconfiguration message. In another implementation, MN 104A does not include a C-MN configuration release field / IE for releasing the first C-MN configuration in the second RRC reconfiguration message. In this case, the second configuration ID in the second conditional configuration has the same value as the first configuration ID in the first conditional configuration, allowing UE 102 to identify the first C-MN configuration or the first conditional configuration to be replaced based on the second configuration ID.

[0209] Later, UE 102 can detect that condition 634 has been met for connecting to C-PCell 124A (or more conditions), and in response to this detection, initiate random access procedure 634 on C-PCell 124A. For convenience, this discussion may refer to conditions or configurations in the singular, but it will be understood that multiple conditions may exist, and conditional configurations may include one or more configuration parameters to specify conditions or multiple conditions. In response to this initiation, UE 102 can perform random access procedure 636 with MN 104A via C-PCell 124A using the random access configuration in the second C-MN configuration. In response to the initiation or detection, UE 102 can disconnect from another PCell of MN 104A (i.e., the initial PCell). In response to the second C-MN configuration, UE 102 can transmit conditional handover completion message 638 to MN 104A via C-PCell 124A during / after random access procedure 636.

[0210] After UE 102 successfully completes the random access procedure 636 or transmits the conditional handover completion message 538, UE 102 may communicate with MN 104A via C-PCell 124A (i.e., the new PCell 124A) according to the second C-MN configuration 642. UE 102 may transmit the conditional handover completion message 638 during or after the random access procedure.

[0211] In some implementations, the random access procedure may be a four-step random access procedure or a two-step random access procedure. In other implementations, the random access procedure may be a contention-based random access procedure or a contention-free random access procedure. In some implementations, UE 102 may transmit a conditional handover completion message in message 3 of a four-step random access procedure or in message A of a two-step random access procedure.

[0212] Similar to the scenario discussed above, MN 104A can, for example, use a MAC PDU to determine the identity of UE102.

[0213] Example implementations of the second C-MN configuration can be similar to the first C-MN configuration. Example implementations of the second conditional configuration can be similar to the first conditional configuration. In some implementations, MN 104A may include the condition or a new condition to be evaluated by UE 102 in the second conditional configuration. At event 634, UE 102 reuses the condition or uses the new condition in the second conditional configuration. In other implementations, MN 104A does not include the condition to be evaluated by UE 102 in the second conditional configuration or the second RRC reconfiguration message, such that UE 102 reuses the condition in the first conditional configuration at event 634.

[0214] In some implementations, MN 104A may include CU 172 and one or more DUs 174, such as Figure 1B As shown. The UE communicates with the SN 602 via the first DU 174 operating the PCell. In response to determination 659, CU 172 may send a UE context establishment request message or a UE context modification request message to the second DU 174. DU 174 may generate a second C-MN configuration or a portion thereof, and send the second C-MN configuration or a portion thereof to CU 172 in a UE context establishment response message or a UE context modification response message. When the second DU 174 generates a portion of the second C-MN configuration, CU 172 may generate the remainder of the second C-MN configuration. In one embodiment, the second DU 174 may perform 636 a random access procedure with UE 102 and identify UE 102 during the random access procedure. In response to this identification, the second DU 174 communicates with UE 102 using the second C-MN configuration or a portion thereof. If the second DU 174 can identify UE 102 during the random access procedure, the second DU 174 can send an indication (e.g., a downlink data delivery status message) to the CU 172. In another embodiment, the second DU 174 can perform a random access procedure 636 with UE 102 and forward the identifier of UE 102 received in the MAC PDU during the random access procedure to the CU 172. The CU 172 identifies UE 102 based on the identifier of UE 102. In response to this identification, the CU 172 and the second DU 174 communicate with UE 102 using the remainder of the second C-MN configuration and a portion of the second C-MN configuration, respectively. In response to an indication (e.g., a downlink data delivery status message) received from MN 104A or an RRC reconfiguration complete message 638, the CU 172 can begin transmitting DLPDUs (e.g., PDCP PDUs) to UE 102 via the second DU 174. If the first DU 174 operates on C-PCell 124A, then the second DU 174 is the same DU as the first DU 174. Otherwise, the second DU 174 is a different DU from the first DU 174.

[0215] If, at event 636, MN 104A (or the second DU 174) identifies UE 102 on C-PCell 124A (i.e., becomes PCell 124A), then MN 104A begins to transmit, according to some configuration parameters in the second C-MN configuration, multiple downlink control information (DCI) commands, multiple reference signals, or data on the Physical Downlink Control Channel (PDCCH) to UE 102 via C-PCell 124A and / or one or more C-SCells (if configured in the second C-MN configuration). If, at event 636, MN 104A (or the second DU 174) identifies UE 102 on C-PCell 124A, then, according to some configuration parameters in the second C-MN configuration, MN 104A (or the second DU 174) can receive multiple signals, multiple probe reference signals, or data on PUCCH from UE 102 via C-PCell 124A and / or one or more C-SCells (if configured in the second C-MN configuration). According to some configuration parameters in the second C-MN configuration, UE 102 receives multiple DCI commands, multiple reference signals, or data on PDCCH from MN 104A (or the second DU 174) via C-PCell 124A and / or one or more C-SCells (if configured in the second C-MN configuration). UE 102 may transmit multiple signals, multiple probe reference signals, or data on the PUCCH to C-MN 104A (or second DU 174) via C-PCell 124A and one or more C-SCells (if configured in the second C-MN configuration) according to some configuration parameters in the second C-MN configuration. In response to this identification, C-PCell 124A becomes PCell 124A, and one or more C-SCells become one or more SCells.

[0216] To further clarify, please refer to the following... Figures 7A-8D Discussion in Figure 1A and 1B Several example methods that can be implemented by the devices operating in the system.

[0217] First refer to Figure 7A Example method 700A for managing conditional configurations can be found in, for example... Figure 1A and 1B In a suitable UE such as UE102, it is implemented as a set of instructions stored on a computer-readable medium and executable by processing hardware (e.g., one or more processors). For convenience, method 700A is discussed below with reference to UE 102.

[0218] Method 700A begins at block 702, where UE 102 receives conditional configurations for the conditional procedure, such as PAC ( Figure 3A -H event 320A or 320B), CSAC ( Figure 4A -C event 450) or CHO ( Figure 5A -C event 550, Figure 6A -C event 650). Next, in block 704, UE 102 receives RRC messages for adding, modifying, or releasing the DRB ( Figure 3A -H events 356, 357, 366, 376, or 377, Figure 4A -C event 456, Figure 5A -C events 529, 530, or 531, Figure 6A -C events 629, 630, or 631). RRC messages may not include instructions to release conditional configurations.

[0219] At block 706, in response to receiving an RRC message instructing UE 102 to add, modify, or release a DRB ( Figure 3A -H events 382, ​​383, or 385, Figure 4A -C events 481, 482, or 483, Figure 5A Events 581, 582, or 583 of type -C Figure 6A In events 681, 682, or 683 of -C, UE 102 ignores the conditional configuration. Specifically, UE 102 determines that it should not apply the conditional configuration to the candidate base station. In some implementations, UE 102 releases the conditional configuration by removing the corresponding configuration parameters and one or more conditions from UE 102's memory.

[0220] Figure 7B The diagram illustrates another example method 700B for managing conditional configurations, which can be used in situations such as... Figure 1A and 1B Implemented in suitable UEs such as UE 102. Like Figure 7A In method 700A, UE 102 receives conditional configuration (block 702) for the conditional procedure, such as CPAC ( Figure 3A -H event 320A or 320B), CSAC ( Figure 4A -C event 450) or CHO ( Figure 5A -C event 550, Figure 6A -C event 650). UE 102 also receives RRC messages that may not include an indication to release conditional configurations ( Figure 3A -B's event 356 Figure 4A Event 456 Figure 5A Event 530 Figure 6A Event 630)(block 712).

[0221] In block 714, UE 102 determines whether the RRC message includes an indication to UE 102 to add, modify, or release a DRB. If the RRC message includes an indication to UE 102 to add, modify, or release a DRB, then UE 102 can determine that the conditional configuration is invalid (block 716). Accordingly, UE 102 ignores or releases the conditional configuration. Figure 3A -H events 382, ​​383, or 385, Figure 4A -C events 481, 482, or 483, Figure 5A Events 581, 582, or 583 of type -C Figure 6A -C events 681, 682, or 683).

[0222] If the RRC message does not include an indication to UE 102 to add, modify, or release a DRB, then UE 102 can determine that the conditional configuration is valid (block 718). Accordingly, UE 102 retains the conditional configuration.

[0223] Figure 7C The diagram illustrates yet another example method 700C for managing conditional configurations, which can be used in situations such as... Figure 1A and 1B Implemented in suitable UEs such as UE 102. Like Figure 7B In method 700B, UE 102 receives conditional configuration (block 702) for a conditional procedure, such as CPAC ( Figure 3A -H event 320A or 320B), CSAC ( Figure 4A -C event 450) or CHO ( Figure 5A -C event 550, Figure 6A -C event 650). Furthermore, as in method 700B, UE102 receives an RRC message that may not include an indication to release the conditional configuration ( Figure 3A -B's event 356 Figure 4A Event 456 Figure 5A Event 530 Figure 6A Event 630 (block 712), and determine whether the RRC message includes an indication to add, modify or release DRB for UE 102 (block 714).

[0224] If the RRC message includes an indication to UE 102 to add or modify the DRB, UE 102 can determine that the conditional configuration is invalid (block 716). Accordingly, UE 102 ignores or releases the conditional configuration. Figure 3A -H events 382, ​​383, or 385, Figure 4A -C events 481, 482, or 483, Figure 5A Events 581, 582, or 583 of type -C Figure 6A -C events 681, 682, or 683).

[0225] If the RRC message includes an indication to UE 102 to release the DRB, then UE 102 can determine that the conditional configuration is valid (block 718). Accordingly, UE 102 retains the conditional configuration.

[0226] Figure 7D The illustration shows an example method 700D for managing conditional configurations after receiving an instruction to add, modify, or release a DRB, and receiving a second conditional configuration as an update to the first conditional configuration. This method can be used in applications such as... Figure 1A and 1B A suitable UE implementation, such as UE 102, is a set of instructions stored on a computer-readable medium and executable by processing hardware (e.g., one or more processors). For convenience, method 700D will be discussed below with reference to UE 102.

[0227] In block 701, UE 102 communicates with the base station using several configurations, which may be conditional configurations. Then, at block 702, UE 102 receives conditional configurations for the conditional process, such as CPAC (…). Figure 3A -H event 320A or 320B), CSAC ( Figure 4A -C event 450) or CHO ( Figure 5A -C event 550, Figure 6A -C event 650). UE102 also receives RRC messages that may not include an indication to release conditional configurations ( Figure 3F -H events 356, 376, or 377, Figure 4C Event 465, Figure 5C Event 531, Figure 6C Event 631)(block 712).

[0228] Then, UE 102 can update one of its configurations based on the RRC message. Figure 3F -H Event 385 Figure 4C Event 483 Figure 5C Event 583 Figure 6C(Event 683). For example, the RRC message may include a new conditional configuration (block 722). In block 724, UE 102 may compare the new conditional configuration with the current configuration. If the new conditional configuration is consistent with one of the current configurations, UE 102 may determine that the current configuration is valid (block 718) and may retain the current configuration. On the other hand, if the new conditional configuration is inconsistent with each of the current configurations, UE 102 may determine that the current configuration is invalid (block 716). UE 102 may then update one of the current configurations with the new conditional configuration by replacing the current configuration with the new conditional configuration. In some implementations, UE 102 may determine that the new conditional configuration is consistent with one of the current configurations when the new conditional configuration is the same as the current configuration. If the new conditional configuration includes a new or modified DRB from the current configuration, then the new conditional configuration is inconsistent with the current configuration. In other implementations, when the new conditional configuration is an incremental configuration that expands upon one of the current configurations, UE 102 can determine that the new conditional configuration is consistent with one of the current configurations.

[0229] Figure 8A This is a flowchart of an example method 800A for managing conditional configurations after determining whether to add, modify, or release a DRB. This method can be implemented in the MN of this disclosure as, for example, a set of instructions stored on a computer-readable medium and executable by processing hardware (e.g., one or more processors). For convenience, method 800A is discussed below with reference to MN 104A.

[0230] Method 800A begins at block 802, where MN 104A transmits the configuration of conditions for the conditional process, such as CPAC ( Figure 3A -H event 320A or 320B), CSAC ( Figure 4A -C event 450) or CHO ( Figure 5A -C event 550, Figure 6A -C event 650). Next, in block 804, MN 104A receives interface messages from CN 110 ( Figure 3A Event 316 of -H Figure 4A Event 416 of -C Figure 5A Event 516 of -C Figure 6A -C event 616). MN 104A can respond to interface messages to determine the addition, modification, or release of the DRB ( Figure 3A -H Event 318 Figure 4A -C Event 418 Figure 5A -C Event 518 Figure 6A -C event 618), and can determine the release of conditional configuration ( Figure 4B Event 457 Figure 5B Event 557 Figure 6B Event 657)(block 806). Then, MN 104A can transmit RRC messages for adding, modifying, or releasing the DRB ( Figure 3A -H events 356, 357, 366, 376, or 377, Figure 4A -C event 456, Figure 5A -C events 529, 530, or 531, Figure 6A -C events 629, 630, or 631). RRC messages may not include instructions to release conditional configurations.

[0231] Figure 8B The diagram illustrates another example method 800B for managing conditional configurations, which can be used in situations such as... Figure 1A and 1B Implemented in a suitable MN such as MN 104A. As in Figure 8A In method 800A, MN 104A transmits the conditional configuration of the conditional process (block 802), such as CPAC ( Figure 3A -H event 320A or 320B), CSAC ( Figure 4A -C event 450) or CHO ( Figure 5A -C event 550, Figure 6A -C event 650). Next, in block 804, MN 104A receives interface messages from CN110 ( Figure 3A Event 316 of -H Figure 4A Event 416 of -C Figure 5A Event 516 of -C Figure 6A -C event 616). In response to receiving the interface message, MN 104A can transmit an RRC message to UE 102 ( Figure 3A -H events 356, 357, 366, 376, or 377, Figure 4A -C event 456, Figure 5A -C events 529, 530, or 531, Figure 6A -C events 629, 630, or 631 (block 812). RRC messages may include instructions for UE 102 to add, modify, or release DRBs.

[0232] If the RRC message includes an indication to add, modify, or release a DRB for UE 102, then MN 104A can determine the release of conditional configurations. Figure 4B Event 457 Figure 5B Event 557 Figure 6BEvent 657 (block 816). For example, MN 104A may include an explicit indication in an RRC message or a second RRC message that UE 102 wants to release the conditional configuration. Otherwise, MN 104 may determine to retain the conditional configuration (block 818).

[0233] Figure 8C The diagram illustrates yet another example method 800C for managing conditional configurations, which can be used in, for example... Figure 1A and 1B Implemented in a suitable MN such as MN 104A. As in Figure 8B In method 800B, MN 104A transmits the conditional configuration of the conditional process (block 802), such as CPAC ( Figure 3A -H event 320A or 320B), CSAC ( Figure 4A -C event 450) or CHO ( Figure 5A -C event 550, Figure 6A -C event 650). Next, in block 804, MN 104A receives interface messages from CN110 ( Figure 3A Event 316 of -H Figure 4A Event 416 of -C Figure 5A Event 516 of -C Figure 6A -C event 616). In response to receiving the interface message, MN 104A can transmit an RRC message to UE 102 ( Figure 3A -H events 356, 357, 366, 376, or 377, Figure 4A -C event 456, Figure 5A -C events 529, 530, or 531, Figure 6A -C events 629, 630, or 631 (block 812). RRC messages may include instructions for UE 102 to add, modify, or release DRBs.

[0234] If the RRC message includes an indication to add or modify the DRB for UE 102, then MN 104A can determine to release the conditional configuration. Figure 4B Event 457 Figure 5B Event 557 Figure 6B Event 657 (block 816). For example, MN 104A may include an explicit indication in the RRC message or a second RRC message that UE 102 wants to release the conditional configuration. Otherwise, if the RRC message includes an indication for UE 102 to release the DRB, MN 104 may determine to retain the conditional configuration (block 818).

[0235] Figure 8DAn example method 800D is illustrated for managing the configuration of a condition after receiving an instruction to add, modify, or release a DRB and receiving a configuration of a second condition as an update to the configuration of the first condition. This method can be implemented in the MN of this disclosure as a set of instructions stored on a computer-readable medium and executable by, for example, processing hardware (e.g., one or more processors). For convenience, method 800D is discussed below with reference to MN 104A.

[0236] In block 801, MN 104A communicates with UE 102 using several configurations, which may be conditional configurations. Then, in block 802, MN 104A transmits conditional configurations for conditional procedures, such as CPAC (…). Figure 3A -H event 320A or 320B), CSAC ( Figure 4A -C event 450) or CHO ( Figure 5A -C event 550, Figure 6A -C event 650).

[0237] In block 822, MN 104A can be configured according to the new conditional settings ( Figure 4C Event 459 Figure 5C Event 559 Figure 6C Event 659) determines one of the updated configurations. In block 824, MN 104A can compare the new conditional configuration with the current configuration. If the new conditional configuration is consistent with one of the current configurations, MN 104A can determine that the current configuration is valid and can retain the current configuration (block 818). On the other hand, if the new conditional configuration is inconsistent with each of the current configurations, MN 104A can determine that the current configuration is invalid and can release at least one current configuration (block 816). In some implementations, MN 104A can determine that the new conditional configuration is consistent with one of the current configurations when the new conditional configuration is the same as the current configuration. If the new conditional configuration includes a new or modified DRB from the current configuration, the new conditional configuration is inconsistent with the current configuration. In other implementations, MN 104A can determine that the new conditional configuration is consistent with one of the current configurations when the new conditional configuration is an incremental configuration that expands upon one of the current configurations.

[0238] The following description can be applied to the description above.

[0239] In some implementations, "ignore" can be replaced by "discard" or "release". When the UE ignores, discards, or releases the candidate base station configuration or the conditional configuration, the UE determines that the candidate base station configuration or the conditional configuration is invalid. If the candidate base station configuration or the conditional configuration is invalid, the UE will not use the candidate base station configuration or the conditional configuration for the conditional process or operation.

[0240] User equipment (e.g., UE 102) that can implement the technologies disclosed herein 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, wearable device such as a smartwatch, wireless hotspot, femtocell base station, or broadband router. Furthermore, in some cases, the user equipment can be embedded in electronic systems, such as a vehicle's onboard unit or an advanced driver assistance system (ADAS). Additionally, 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.

[0241] Embodiments of the technology described in this disclosure may include any number of the following aspects, individually or in combination:

[0242] 1. A method for configuration management in a user equipment (UE), the method comprising: receiving conditional configuration information from a radio access network (RAN) by processing hardware, the conditional configuration information including (i) conditional configurations associated with a base station operating in the RAN, and (ii) conditions to be satisfied before the UE applies the conditional configuration; receiving a message from the RAN by the processing hardware, the message including an indication that the UE wants to add, modify, or release a radio bearer (RB); and, in response to receiving the message, determining by the processing hardware to ignore the conditional configuration.

[0243] 2. The method according to aspect 1, wherein receiving the message includes: receiving from the RAN by processing hardware a radio connection reconfiguration message that does not include an indication that the UE wants to release a conditional configuration, wherein determining to ignore the conditional configuration is in response to receiving the radio connection reconfiguration message.

[0244] 3. The method according to any of the foregoing aspects further includes: in response to receiving an instruction from the UE to add, modify, or release an RB, the processing hardware determines whether the conditional configuration is valid; wherein determining to ignore the conditional configuration is in response to determining that the conditional configuration is invalid.

[0245] 4. The method according to any of the foregoing aspects, wherein determining whether the conditional configuration is valid includes: in a first case, in response to receiving an indication from the UE to add or modify an RB, the processing hardware determines that the conditional configuration is not valid; and in a second case, in response to receiving an indication from the UE to release an RB, the processing hardware determines that the conditional configuration is valid.

[0246] 5. The method according to any of the foregoing aspects, wherein receiving the message includes: receiving a radio connection reconfiguration message from the RAN by processing hardware, the radio connection reconfiguration message including a conditional configuration release indicator instructing the UE to release a conditional configuration.

[0247] 6. The method according to any of the foregoing aspects, wherein: the radio connection reconfiguration message is a first radio connection reconfiguration message, and the indication that the UE wants to add, modify or release an RB is included in a second radio connection reconfiguration message.

[0248] 7. The method according to any of the foregoing aspects, wherein the conditional configuration is a first conditional configuration, wherein receiving the message includes receiving a radio connection reconfiguration message including a second conditional configuration from the RAN by the processing hardware, and further includes updating the first conditional configuration by the processing hardware with the second conditional configuration.

[0249] 8. The method according to any of the foregoing aspects, wherein updating the configuration of the first condition with the configuration of the second condition comprises: applying the configuration of the second condition as an incremental configuration to the configuration of the first condition by processing hardware.

[0250] 9. The method according to any of the foregoing aspects, wherein: the radio connection reconfiguration message is a first radio connection reconfiguration message, and the indication that the UE wants to add, modify or release an RB is included in a second radio connection reconfiguration message.

[0251] 10. The method according to any of the foregoing aspects, wherein updating the configuration of the first condition with the configuration of the second condition includes: releasing the configuration of the first condition by the processing hardware; and storing the configuration of the second condition by the processing hardware.

[0252] 11. The method according to any of the foregoing aspects, wherein receiving the radio connection reconfiguration message includes receiving a second conditional configuration from the RAN by processing hardware, the second conditional configuration including an identifier identical to the identifier of the first conditional configuration, for the processing hardware to identify the configuration of the condition to be replaced.

[0253] 12. The method according to any of the foregoing aspects, wherein the UE operates in multiple radio dual connectivity (MR-DC), and wherein the message is received from a base station operating as a master node (MN) to support MR-DC at the UE.

[0254] 13. The method according to any of the foregoing aspects, wherein the UE operates in MR-DC, and wherein the message is received from a base station operating as a secondary node (SN) to support MR-DC at the UE.

[0255] 14. The method according to any of the foregoing aspects, wherein the conditional configuration is performed for the candidate primary secondary cell (C-PSCell) of the SN during a conditional PSCell add or change (CPAC) configuration process.

[0256] 15. The method according to any of the foregoing aspects, wherein the conditional configuration is performed on a candidate secondary node (C-SN) during a conditional SN addition or change (CSAC) configuration process.

[0257] 16. The method according to any of the foregoing aspects, wherein the UE operates in single connection (SC), and wherein the message is received from a base station operating as an MN.

[0258] 17. The method according to any of the foregoing aspects, wherein a second conditional configuration is received from the MN.

[0259] 18. The method according to any of the foregoing aspects, wherein the conditional configuration is performed for the candidate master node (C-MN) during a conditional switching (CHO) process.

[0260] 19. The method according to any of the foregoing aspects, wherein the conditional configuration is performed for the candidate primary cell (C-PCell) of MN during the CHO process.

[0261] 20. A user equipment (UE) including processing hardware and configured with a method according to any of the foregoing aspects.

[0262] 21. A method for configuring a user equipment (UE) in a radio access network (RAN), the method comprising: transmitting to the UE by processing hardware (i) a conditional configuration associated with a base station operating in the RAN, and (ii) conditions to be satisfied by the UE before applying the conditional configuration during the conditional process; receiving an interface message from a core network (CN) by the processing hardware; determining, in response to the interface message, to add, modify, or release a radio bearer (RB); and transmitting by the processing hardware a message including an indication that the UE intends to add, modify, or release an RB.

[0263] 22. The method according to aspect 21, wherein transmitting the message includes: transmitting a radio connection reconfiguration message by processing hardware that does not include an indication that the UE wants to release the conditional configuration.

[0264] 23. The method according to aspect 21 or aspect 22, wherein transmitting the message includes: transmitting a radio connection reconfiguration message by processing hardware, the radio connection reconfiguration message including an instruction for the UE to release a conditional configuration release indicator.

[0265] 24. The method according to any one of aspects 21-23, further comprising: in response to determining that an RB is added, modified, or released, the processing hardware determines whether the conditional configuration is valid; wherein transmitting the conditional configuration release indicator is in response to determining that the conditional configuration is not valid.

[0266] 25. The method according to any one of aspects 21-24, wherein determining whether the conditional configuration is valid includes: in a first case, in response to determining that an RB is added or modified, the processing hardware determines that the conditional configuration is not valid; and in a second case, in response to determining that an RB is released, the processing hardware determines that the conditional configuration is valid.

[0267] 26. The method according to any one of aspects 21-25 further includes: in response to determining that the conditional configuration is not valid, the processing hardware determines to release the conditional configuration.

[0268] 27. The method according to any one of aspects 21-26, wherein the conditional configuration is a first conditional configuration, and wherein transmitting the message includes transmitting a radio connection reconfiguration message including a second conditional configuration by processing hardware.

[0269] 28. The method according to any one of aspects 21-27 further includes: determining, by processing hardware, to update the configuration of the first condition with the configuration of the second condition.

[0270] 29. The method according to any one of aspects 21-28, wherein determining to update the configuration of the first condition with the configuration of the second condition includes: determining by processing hardware whether the configuration of the second condition is consistent with the configuration of the first condition; and in response to determining that the configuration of the second condition is inconsistent with the configuration of the first condition, determining by processing hardware to update the configuration of the first condition with the configuration of the second condition.

[0271] 30. The method according to any one of aspects 21-29, wherein the message is sent to the UE.

[0272] 31. The method according to any one of aspects 21-30, wherein the RAN operates in multiple radio dual connectivity (MR-DC), and wherein the message is from a base station operating as a master node (MN) to a base station operating as a secondary node (SN).

[0273] 32. The method according to any one of aspects 21-31, wherein the RAN operates in multiple radio dual connectivity (MR-DC), and wherein the conditional configuration is performed for candidate primary secondary cells (C-PSCells) of the SN during a conditional PSCell add or change (CPAC) configuration process.

[0274] 33. The method according to any one of aspects 21-32, wherein the RAN operates in multiple radio dual connectivity (MR-DC), wherein the conditional configuration is performed for candidate secondary nodes (C-SNs) during a conditional SN addition or change (CSAC) configuration process.

[0275] 34. The method according to any one of aspects 21-33, wherein the RAN operates in single connectivity (SC), and wherein the message originates from a base station operating as an MN.

[0276] 35. The method according to any one of aspects 21-34 further includes transmitting a second conditional configuration from the MN.

[0277] 36. The method according to any one of aspects 21-35, wherein the conditional configuration is performed for the candidate master node (C-MN) during a conditional switching (CHO) process.

[0278] 37. The method according to any one of aspects 21-36, wherein the conditional configuration is performed for the candidate primary cell (C-PCell) of MN during the CHO process.

[0279] 38. A base station including processing hardware and configured to implement the method according to any one of aspects 21-37.

[0280] Some embodiments described in this disclosure include 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 certain operations and can be configured or arranged in some manner. A hardware module may include permanently configured dedicated circuitry or logic (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 certain operations. A hardware module may also include programmable logic or circuitry (e.g., covered by a general-purpose processor or other programmable processor) 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., software-configured) may be driven by cost and time considerations.

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

Claims

1. A method for configuration management in a user equipment (UE), the method comprising: Receive a first message from the radio access network RAN, the first message including (i) a configuration of a first condition associated with a base station operating in the RAN, and (ii) a condition to be satisfied before the UE applies the configuration of the first condition; The UE receives a second message from the RAN, the second message including an indication that the UE wants to update the configuration of the first condition based on the configuration of the second condition or an indication that the UE wants to release the configuration of the first condition. as well as In response to receiving the second message, update the configuration of the first condition with the configuration of the second condition or release the configuration of the first condition.

2. The method according to claim 1, wherein, Receiving the second message includes: The UE receives a radio connection reconfiguration message from the RAN, the radio connection reconfiguration message including a conditional configuration release indicator instructing the UE to release the first conditional configuration.

3. The method according to claim 1 or 2, further comprising: The UE receives an instruction from the RAN to add, modify, or release a radio bearer (RB), or an instruction to release a conditional configuration.

4. The method according to claim 3, wherein: The radio connection reconfiguration message is a first radio connection reconfiguration message, and the indication that the UE wants to add, modify, or release an RB is included in a second radio connection reconfiguration message.

5. The method according to claim 1, wherein, Receiving the second message includes receiving a radio connection reconfiguration message from the RAN that includes the configuration of the second condition, and / or The receiving of the radio connection reconfiguration message includes receiving the configuration of the second condition from the RAN, wherein the configuration of the second condition includes an identifier identical to the identifier of the configuration of the first condition, for the UE to identify the configuration of the condition to be replaced; and, Updating the configuration of the first condition with the configuration of the second condition includes: Apply the configuration of the second condition as an incremental configuration to the configuration of the first condition; or Release the configuration of the first condition and store the configuration of the second condition.

6. The method according to any one of claims 1, 2, 4, and 5, wherein: The UE operates in a multi-radio dual-connection MR-DC and receives the second message from a base station operating as a master node MN to support the MR-DC at the UE; or The UE operates in MR-DC and receives the second message from a base station operating as a secondary node SN to support MR-DC at the UE; or The first conditional configuration is for the candidate primary secondary cell C-PSCell of the SN during the process of adding or changing the CPAC configuration of the conditional PSCell. or The first conditional configuration is applied to the candidate secondary node C-SN during the process of adding or changing the CSAC configuration of the conditional SN.

7. The method according to any one of claims 1, 2, 4, and 5, wherein, The UE operates in a single-connection SC, and wherein the second message is received from a base station operating as an MN; and / or Wherein, the configuration of the second condition is received from the MN; and / or The first conditional configuration is either for the candidate primary node C-MN during the conditional handover CHO process, or for the candidate primary cell C-PCell of the MN during the CHO process.

8. A user equipment (UE) comprising processing hardware and configured with the method according to any one of the preceding claims.

9. A method for configuring a user equipment (UE) in a radio access network (RAN), the method comprising: A first message is transmitted to the UE, the first message including (i) a configuration of a first condition associated with a base station operating in the RAN, and (ii) a condition to be satisfied before the UE applies the configuration of the first condition during the condition application process. as well as A second message is transmitted to the UE, the second message including an indication that the UE wants to update the configuration of the first condition based on the configuration of the second condition or an indication that the UE wants to release the configuration of the first condition.

10. The method according to claim 9, wherein, The transmission of the second message includes: A radio connection reconfiguration message is transmitted to the UE, the radio connection reconfiguration message including a conditional configuration release indicator that instructs the UE to release the first conditional configuration.

11. The method according to claim 9 or 10, further comprising: Add, modify, or release radio bearers (RBs); as well as The UE is given an instruction to add, modify, or release an RB, or an instruction to release a conditional configuration.

12. The method according to claim 9, wherein, Transmitting the second message includes transmitting a radio connection reconfiguration message including the configuration of the second condition, and, Updating the configuration of the first condition with the configuration of the second condition includes: Determine whether the configuration of the second condition is consistent with the configuration of the first condition; and In response to determining that the configuration of the second condition is inconsistent with the configuration of the first condition, the configuration of the first condition is updated with the configuration of the second condition.

13. The method according to any one of claims 9, 10, and 12, wherein: The RAN operates in a multi-radio dual-connection MR-DC, and the second message is sent from the base station operating as the master node MN to the base station operating as the secondary node SN. or The RAN operates in a multi-radio dual-connection MR-DC, and the first conditional configuration is for the candidate primary secondary cell C-PSCell of the SN during the conditional PSCell addition or CPAC configuration change process. or The first conditional configuration is applied to the candidate secondary node C-SN during the process of adding or changing the CSAC configuration of the conditional SN.

14. The method according to any one of claims 9, 10, and 12, wherein, The RAN operates in a single-connection SC, and wherein the second message originates from a base station operating as an MN; and / or further includes transmitting a second conditional configuration from the MN; and / or The first conditional configuration is either for the candidate primary node C-MN during the conditional handover CHO process, or for the candidate primary cell C-PCell of the MN during the CHO process.

15. A base station including processing hardware and configured to implement the method of any one of claims 9-14.

Images