Controlling execution of a conditional mobility procedure in wireless communications

Abstract

An apparatus comprising means for controlling execution of a plurality of conditional mobility procedures, the conditional mobility procedures comprising a first conditional mobility procedure and a second conditional mobility procedure, the first conditional mobility procedure comprising a first configuration initiated by a first network node, the second conditional mobility procedure comprising a second configuration initiated by a second network node, wherein controlling execution of the plurality of conditional mobility procedures comprises controlling sequential execution of the first conditional mobility procedure and the second conditional mobility procedure based on the first configuration and the second configuration.

Description

Technical Field

[0001] Examples of this disclosure relate to controlling the execution of conditional mobility procedures in wireless communications. Some examples relate to controlling the execution of conditional mobility procedures during Evolved Universal Terrestrial Radio Access (E-UTRA)-5G New Radio (NR) Multi-Connectivity. Background Technology

[0002] Multiple Radio Dual Connectivity (MR-DC) is an example of multi-connectivity. MR-DC enables User Equipment (UE) with multiple receivers / transmitters to utilize resources provided by different nodes. During multi-connectivity, the UE stores its configuration.

[0003] Established multi-connection connections can be reconfigured by sending a reconfiguration message. In 3GPP systems, this reconfiguration message is called an RRC reconfiguration message.

[0004] In some cases, it may be necessary to provide improved reconfiguration message handling in multiple connections. Summary of the Invention

[0005] According to various, but not all, embodiments, an apparatus is provided that includes components for controlling the execution of a plurality of conditional mobility processes, including a first conditional mobility process and a second conditional mobility process, the first conditional mobility process including a first configuration initiated by a first network node, and the second conditional mobility process including a second configuration initiated by a second network node.

[0006] Controlling the execution of multiple conditional mobility processes includes: controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration.

[0007] In some, but not all, examples, the control of sequential execution is based on the dependency of the second configuration on the source configuration.

[0008] Furthermore, the first configuration can change the source configuration.

[0009] In some, but not all, examples, the apparatus includes a component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process, depending on whether the second configuration is a full configuration.

[0010] In some, but not all, examples, the apparatus includes a component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process and releasing the second configuration, depending on whether the second configuration is an incremental configuration relative to the source configuration.

[0011] In some, but not all, examples, the apparatus includes: a component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process and releasing the second configuration, depending on whether releasing the second configuration is acceptable, wherein whether releasing the second configuration is acceptable depends on the bearer mapping of the second configuration.

[0012] In some, but not all, examples, the apparatus includes a component for enabling sequential execution of the first and second configurations, depending on the second configuration containing the same configuration as the source configuration.

[0013] In some, but not all, examples, the apparatus includes a component for enabling sequential execution of the first and second configurations, depending on whether the second configuration contains the same configuration as the source configuration and satisfies user equipment capability partitioning conditions.

[0014] In some, but not all, examples, the second conditional mobility procedure involves multiple target configurations associated with different target nodes, and not all target nodes allow the sequential execution of the first and second conditional mobility procedures.

[0015] Furthermore, the device includes a component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process when permitted by a set of "N" target nodes that are most likely to satisfy the triggering conditions of the second conditional mobility process.

[0016] In some, but not all, examples, the second conditional mobility process is a conditional master node handover process triggered by a reconfiguration message initiated by the second network node.

[0017] The second network node is the source master node.

[0018] The reconfiguration messages from the second network node include:

[0019] - A set of one or more target configurations associated with different target master nodes;

[0020] - A set of one or more switching trigger conditions; and

[0021] -Including the second configuration of the target secondary cell group configuration.

[0022] The first conditional mobility process is a conditional primary / secondary cell change process triggered by a reconfiguration message initiated by the first network node.

[0023] In this network, the first node is a secondary node.

[0024] Furthermore, the reconfiguration message from the first network node includes a set of one or more primary and secondary cell configurations containing the first configuration.

[0025] According to various, but not all, embodiments, an apparatus is provided that includes components for controlling the execution of a plurality of conditional mobility processes, including a first conditional mobility process and a second conditional mobility process, the first conditional mobility process including a first configuration initiated by a first network node, and the second conditional mobility process including a second configuration initiated by a second network node.

[0026] Controlling the execution of multiple conditional mobility processes includes sending information to the user equipment for controlling the sequential execution of a first conditional mobility process and a second conditional mobility process based on a first configuration and a second configuration.

[0027] In some, but not all, examples, the device is configured to function as a second network node, and the device includes components for performing the following operations:

[0028] Send a request associated with the second conditional mobility procedure to the target network node;

[0029] Receive a response from the target network node including the second configuration; and

[0030] Based on this response, a second configuration and information for controlling the sequential execution of the first and second conditional mobility processes are sent to the user equipment.

[0031] In some, but not all, examples, the device is configured as a target network node associated with a second conditional mobility process, and the device includes components for performing the following operations:

[0032] Receive a request associated with the second conditional mobility procedure; and

[0033] Send a second configuration and information for controlling the sequential execution of the first and second conditional mobility processes to the second network node.

[0034] According to various, but not all, embodiments, an apparatus is provided that includes components for controlling the execution of a plurality of conditional mobility processes, including a first conditional mobility process and a second conditional mobility process, the first conditional mobility process including a first configuration initiated by a first network node, and the second conditional mobility process including a second configuration initiated by a second network node.

[0035] Controlling the execution of multiple conditional mobility processes includes receiving messages for controlling the sequential execution of a first conditional mobility process and a second conditional mobility process based on a first configuration and a second configuration.

[0036] According to various, but not all, embodiments, a method is provided that includes:

[0037] Controlling the execution of multiple conditional mobility processes, including a first conditional mobility process and a second conditional mobility process, wherein the first conditional mobility process includes a first configuration initiated by a first network node, and the second conditional mobility process includes a second configuration initiated by a second network node.

[0038] Controlling the execution of multiple conditional mobility processes includes: controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration.

[0039] According to various, but not all, embodiments, a computer program is provided that, when run by a computer, causes:

[0040] Controlling the execution of multiple conditional mobility processes, including a first conditional mobility process and a second conditional mobility process, wherein the first conditional mobility process includes a first configuration initiated by a first network node, and the second conditional mobility process includes a second configuration initiated by a second network node.

[0041] Controlling the execution of multiple conditional mobility processes includes: controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration.

[0042] According to various, but not all, embodiments, examples as claimed in the appended claims are provided. Attached Figure Description

[0043] Some examples will now be described with reference to the accompanying drawings, in which:

[0044] Figure 1 This article presents an example of the subject matter described in it;

[0045] Figure 2 This provides another example of the topic described in this article;

[0046] Figure 3 This provides another example of the topic described in this article;

[0047] Figure 4 This provides another example of the topic described in this article;

[0048] Figure 5 This provides another example of the topic described in this article;

[0049] Figure 6 This provides another example of the topic described in this article;

[0050] Figure 7 This provides another example of the topic described in this article;

[0051] Figure 8 This provides another example of the topic described in this article;

[0052] Figure 9 This provides another example of the topic described in this article;

[0053] Figure 10 This provides another example of the subject matter described in this article; and

[0054] Figure 11 This provides another example of the topic described in this article.

[0055] definition

[0056] 3GPP Third Generation Partnership Project

[0057] 5G fifth-generation cellular network standard

[0058] CHO conditional switching

[0059] CPC conditional PSCell change

[0060] E-UTRA Evolution Universal Terrestrial Radio Access

[0061] eNB eNodeB

[0062] gNB gNodeB

[0063] gNB-CU gNodeB Centralized Unit

[0064] gNB-DU gNodeB Distributed Unit

[0065] MCG Main Cell Group

[0066] MN master node

[0067] NR New Radio

[0068] PCell main cell

[0069] PSCell Primary and Secondary Communities

[0070] RAN (Radio Access Network)

[0071] RAT Radio Access Technology

[0072] RLC Radio Link Control

[0073] RLF radio link failure

[0074] RRC Radio Resource Control

[0075] SCell Auxiliary Community

[0076] SCG Auxiliary Community Group

[0077] SgNB auxiliary gNodeB

[0078] SN auxiliary node

[0079] SRB3 signal radio bearer 3

[0080] UE User Equipment Detailed Implementation

[0081] Figure 1 This is a schematic block diagram illustrating a wireless communication network system 1 configured for multiple connections. In at least some examples, system 1 is a network system defined by 3GPP.

[0082] Figure 1 System 1 includes UE 100, RAN including at least first node 102 and second node 104, and core network (NW) entity 108. Figure 1 The third node 112 and the fourth node 114 of the RAN are also shown, enabling the UE 100 to change nodes during mobility.

[0083] In this document, the term "node" refers to an access node. In System 1 as defined by 3GPP, a node is a base station. A base station implementing NR is called a gNB. A base station implementing E-UTRA is called an eNB.

[0084] Figure 2 An example of nodes 104 / 114 (e.g., gNBs) configured to implement a first radio access technology (RAT) (e.g., NR) is shown. In this example, node 104 has a decomposed (split) architecture. gNB 104 includes one or more distributed units (gNB-DUs) 20 and centralized units (gNB-CUs) 10. The apparatus 2 is configured to implement the functionality of at least a portion (such as gNB-CUs and / or one or more gNB-DUs) or the entire gNB of nodes 104, 114.

[0085] gNB-CU 10 is a logical node configured to host the Radio Resource Control (RRC) layer and other layers of gNB 120. gNB-CU 10 controls the operation of one or more gNB-DU 20s. gNB-DU 20 is a logical node configured to host the Radio Link Control Protocol (RLC), Media Access Control (MAC), and Physical (PHY) layers of the access node (gNB) 120. gNB-DU 20 communicates via a dedicated interface (F1) to the RRC layer hosted by gNB-CU.

[0086] One gNB-DU 20 can support one or more cells (not shown in the attached diagram). A cell is supported by only one gNB-DU 20.

[0087] Figure 3 An example of nodes 102 / 112 (e.g., eNBs) configured to implement a second RAT (e.g., E-UTRA) is shown. In this example, node 102 does not have a decomposed architecture. eNB 102 is a logical node configured to host the Radio Resource Control (RRC) layer and other layers of eNB 102. Device 2 is configured to implement at least a portion of the functionality of nodes 102, 112 (such as eNBs).

[0088] Refer again Figure 1 Nodes 102, 104, 112, and 114 are operatively coupled to each other via network interface 103. In one example implementation, network interface 103 includes an X2 interface.

[0089] UE 100 can be operatively coupled to node 102 via radio interface 101. In this example, radio interface 101 is a wireless interface. In one example implementation, radio interface 101 includes a Uu interface. During multiple connections, UE 100 can be simultaneously coupled to another node 104 via radio interface 105. In some examples, radio interfaces 101 and 105 include the same type of interface.

[0090] A node 102 to which UE 100 is operatively coupled can be configured to act as a primary node (MN). Another node 104 to which UE 100 is operatively coupled can be configured to act as a secondary node (SN).

[0091] exist Figure 1 In the diagram, the first node 102 is the first master node (MN1), the second node 104 is the first auxiliary node (SN1), the third node 112 is the second master node (MN2), and the fourth node 114 is the second auxiliary node (SN2). Figure 1 In this context, MN1 102 and SN1 104 are service (source) nodes.

[0092] At least MN 102 and 112 can be operatively coupled to core network entity 108 via interface 107. SN 104 and 114 can also be operatively coupled to core network entity 108. Figure 1 In this context, MN1102 and MN2112 are operatively coupled to different core network entities 108 via interface 107, or they may be operatively coupled to the same entity.

[0093] In the first example, MNs 102 and 112 are eNBs configured to implement E-UTRA. Core network entity 108 includes an evolved packet core (EPC) entity. Entity 108 may include a mobility management entity (MME) and / or a serving gateway (S-GW). Interface 107 includes an S1 interface.

[0094] In the second example, MNs 102 and 112 are gNBs configured to implement NR. Core network entity 108 includes a 5G core (5GC) entity. Entity 108 may include Access and Mobility Management Functions (AMF). Interface 107 includes an NG-C interface.

[0095] Below are examples of multiple connections. In most, but not all, of these examples, SN 104, 114 implements a different RAT than MN 102, 112.

[0096] One example is the E-UTRA-NR dual-connection (EN-DC), where the eNB acts as MN 102 / 112 and the gNB acts as SN104 / 114. This example is referenced in this specification. However, aspects of this disclosure also apply to other examples described below.

[0097] Another example is the next-generation RAN (NG-RAN) E-UTRA-NR dual connectivity (NGEN-DC), where the eNB (e.g., next-generation eNB: ng-eNB) acts as the MN and the gNB acts as the SN.

[0098] Another example of dual connectivity is NR-E-UTRA dual connectivity (NE-DC), where gNB acts as MN and ng-eNB acts as SN.

[0099] Another example of dual connectivity is NR-NR dual connectivity (NR-DC), where one gNB acts as the MN and the other as the SN. In another example of NR-DC, UE 100 is connected to two gNB-DUs, one serving the primary cell group (MCG) and the other serving the secondary cell group (SCG), and these two gNB-DUs are connected to the same gNB-CU, acting as both the MN and SN.

[0100] In at least some examples of multi-connectivity, nodes 102, 104, 112, and 114 include cell groups with one or more cells. A cell group includes one primary cell and zero or more secondary cells.

[0101] A cell refers to a geographical area with radio signals, i.e., covered by a base station, where a UE can connect and obtain service. Cells can be identified by a lower-level Physical Cell Identifier (PCI) and a higher-level Cell Identifier.

[0102] The primary cell is a cell operating on the primary frequency, where UE 100 performs the initial connection establishment procedure or initiates a connection re-establishment procedure, or the primary cell is a cell designated as the primary cell during handover. In at least some examples, the primary cell is a cell configured to provide non-access stratum (NAS) mobility information during connection establishment, re-establishment, or handover. The primary cell can be configured to provide security input during connection re-establishment or handover.

[0103] A secondary cell is a cell operating on a secondary frequency. It can be configured once an RRC connection is established and can be used to provide additional radio resources. A secondary cell (SCell) can be configured to form a group of serving cells together with a PCell.

[0104] In multi-connectivity, the cell group with MN 102 / 112 is the primary cell group (MCG). The cell group with SN 104 / 114 is the secondary cell group (SCG). An MCG consists of one primary cell (PCell) and zero or more secondary cells (SCells). An SCG consists of one primary-secondary cell (PSCell) and zero or more secondary cells (SCells). In at least some examples, both the MCG and SCG include at least one SCell in addition to either a PCell or a PSCell.

[0105] When multiple connections are established for the first time, UE 100 stores the configuration in memory. This configuration includes information identifying the MCG (which includes one PCell and zero or more SCells), the SCG (which includes one PSCell and zero or more SCells), and one or more bearers.

[0106] The configuration may include one or more of the following: information for measurement configuration; information for mobility control; radio resource configuration information (including radio bearer, MAC master configuration and physical channel configuration); and / or access stratum (AS) security configuration.

[0107] After the application (execution) configuration is completed, UE 100 can be configured to receive and transmit data on MCG and SCG bearers using the radio links provided by MN and SN.

[0108] Multi-connectivity can be reconfigured by sending a reconfiguration message that will be executed by UE 100. When executed, the stored configuration is updated. 3GPP standard 37.340 for multi-connectivity defines the reconfiguration message as an RRC reconfiguration message.

[0109] RRC reconfiguration messages initiated by the SN can be sent from either the PSCell or the SCell, or, in the case of repeated carrier aggregation, from both. RRC reconfiguration messages initiated by the MN can be sent from either the PCell or the SCell, or from both.

[0110] The examples in this disclosure relate to reconfiguration messages that enable the execution of mobility procedures. Mobility refers to the ability of UE 100 to move without service loss. A mobility procedure is a process used to ensure that UE 100 has an optimal configuration during mobility. Mobility procedures may involve configuration updates. The execution of a mobility procedure can be prompted at UE 100 by a reconfiguration message.

[0111] Examples of reconfiguration messages used in mobility procedures in multi-connectivity scenarios include, but are not limited to:

[0112] a) SN Modification (MN / SN Initiated) is used to modify, establish (add) or release (remove) bearer contexts (configurations / features), transfer bearers to or from SN 104, or modify other features of the UE context within the same SN 104. Examples include adding, modifying, or releasing SCG bearers and SCG RLC bearers with split bearers, and configuration changes to MCG bearers terminated by an SN. A bearer is a data tunnel associated with an endpoint in the RAN or core network. Modifications to a bearer may include changing the endpoint (e.g., from MN to SN), changing the mapping of Quality of Service (QoS) flows to radio bearers, changing the logical channel identifier, changing RLC bearer features (including timers), and changing the RLC mode (e.g., changing the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and RLC features).

[0113] b) SN change (initiated by MN / SN) is used to transfer the UE context from source SN 104 to target SN 114, and to change the SCG configuration in UE 100 from source SN 104 to target SN 114.

[0114] c) Inter-MN handover (with / without MN-initiated SN change), used to transfer context data from source MN 102 to target MN 112, while the context at SN 104 is either preserved or moved to another SN 114. During the inter-MN handover, target MN 112 can decide whether to preserve, modify, or release source SN 104.

[0115] Figure 4This is a message sequence diagram illustrating an example reconfiguration message that includes an SN-initiated mobility modification process without MN involvement. Since SN 104 remains unchanged, this is referred to as an intra-SN reconfiguration message.

[0116] If coordination with MN 102 is not required, this reconfiguration message can be used to modify the configuration of SN 104. This includes adding, modifying, and releasing SCG SCells, as well as changing PSCells, without altering SN 104. At least in the example described below, the reconfiguration message includes PSCell changes.

[0117] In operation 401, SN 104 sends an RRC reconfiguration message (“NR RRCConnectionReconfiguration”) to UE 100, prompting UE 100 to perform an SN modification mobility procedure. This RRC reconfiguration message may include a target SCG that is different from the current SCG but is still associated with the same SN 104.

[0118] This message can be sent on a bearer such as Signal Radio Bearer 3 (SRB3). UE 100 executes the RRC reconfiguration message to modify (e.g., replace / update) its stored configuration.

[0119] If UE 100 fails to comply with at least a portion of the configuration included in the RRC reconfiguration message, UE 100 may execute a reconfiguration failure procedure.

[0120] In operation 403, if indicated by SN 104, UE 100 performs access for a new target PSCell (“Random Access Procedure”). This procedure may include synchronization toward the target PSCell of SN 104. Performing access may include a RACH procedure (Random Access Channel Procedure).

[0121] In operation 405, UE 100 sends a reply (“NR RRCConnectionReconfigurationComplete”) to SN 104, reporting that the configuration of the reconfiguration message has been applied (e.g., reporting that UE 100 has modified its stored configuration to the new configuration enabled by the RRC reconfiguration message).

[0122] In at least some examples, the mobility process can be a conditional mobility process. A reconfiguration message can be considered a conditional reconfiguration message. This is in... Figure 5 As shown in the figure, Figure 5 An example of a conditional PSCell change (CPC) is shown. (Compared to...) Figure 4Similarly, the reconfiguration message shown is a SN-initiated SN modification mobility procedure without the participation of the MN.

[0123] Operation 501 includes the UE 100 sending measurements ("measurement report") to the SN 104. These measurements may include signal power and / or signal quality measurements, such as reference signal received power (RSRP) or reference signature received quality (RSRQ). After receiving the measurements from the UE 100, the source SN 104 may prepare multiple candidate target PSCs in the same SN 104 based on these measurements. The term "source" means the current serving node or cell. Preparing the candidate target PSCs may include reserving resources such as RACH resources (contention-free random access preambles), cell radio network temporary identifiers (C-RNTIs), or radio resources for guaranteed bit rate services.

[0124] Operation 503 includes the source PSC sending an RRC reconfiguration message ("RRC (connection) reconfiguration") to the UE 100 to prompt (trigger) the UE 100 to perform the CPC mobility procedure. This is also referred to as the CPC reconfiguration message in this document. This includes sending one or more CPC execution conditions to the UE 100, and sending the configuration of one or more prepared candidate PSCs to the UE 100. The CPC execution conditions may be offset-based and / or threshold-based, for example. The offset-based condition may be satisfied when Mt > Ms + offset, where Mt is the measurement of the target PSC, Ms is the measurement of the serving PSC, and offset is the configured offset. The threshold-based condition may be satisfied when Ms < threshold1 (Ms becomes worse than threshold1) and Mt > threshold2 (Mt becomes better than threshold2). Both the offset method and the threshold method may be applied simultaneously, and if at least one of them is satisfied, the CPC execution condition may be satisfied.

[0125] In operation 504, the UE 100 sends a reply ("RRC (connection) reconfiguration complete") to the SN 104 reporting that the reconfiguration has been applied. In Figure 5 it, the report that the reconfiguration has been applied is sent before the CPC execution condition is satisfied. The term "applied" here does not mean that the UE has completed executing the instructions of the RRC reconfiguration message (e.g., the CPC execution condition).

[0126] Operation 505 includes the UE 100 determining that the CPC execution condition is satisfied. For example, the UE 100 may determine that a specific cell of the SN 104 satisfies the execution condition, and may select that cell as the new PSC.

[0127] Operation 507 is similar to operation 403, and is executed depending on the conditions being met.

[0128] Operation 509 is similar to operation 504, but is sent to a new PSCell, indicating that the UE has completed the CPC execution process (e.g., UE 100 has executed operation 507).

[0129] Figure 6 This is a message sequence diagram illustrating an example inter-MN mobility handover process (with / without MN-initiated SN change). Figure 6 However, in not all examples, the switch includes changes between SNs.

[0130] When source MN1 102 initiates a handover, MN1 102 sends a request to target MN2 112 at operation 602. This request can be a handover request (HO-REQ) message. Target MN2 112 is determined by MN1 102 based on measurement reports from the UE. Target MN2 112 can be one of a group of one or more candidate MNs that sent the request to it.

[0131] If target MN2 112 decides to change the SN, the target MN can send an add request (e.g., an SgNB add request) to target SN2 114, as shown in operation 604. The (target) SN responds with an acknowledgment such as an SgNB / SN add request acknowledgment, as shown in operation 606. This acknowledgment may include a reconfiguration message indicating the new configuration (such as the target SCG configuration of SN2 114, including the target PSCell). This reconfiguration message may include an indication of whether a full configuration or an incremental SCG configuration will be provided to UE 100.

[0132] Incremental configuration depends on a reference source configuration stored in the UE 100, while full configuration does not depend on the source configuration. Incremental configuration provides the UE 100 with incremental (difference) updates only to the changed portions of the configuration. The UE 100 applies these portions on top of the existing source configuration (e.g., SCG configuration) to save time and bandwidth. In contrast, full configuration includes the entire configuration.

[0133] If the target MN decides to retain source SN1 104, it can instead send an add request to source SN1 104. Source SN1 104 can decide whether to retain or change its SCG configuration and can provide its confirmation to the target SCG configuration.

[0134] If the switch terminates multi-connection and reverts to single-connection operation, MN2 112 may not send add requests to SN and may not receive target SCG configuration.

[0135] Based on the above, there are several potential use cases for the target SCG configuration during handover:

[0136] - No target SCG configuration (e.g., switched to single connection);

[0137] - Full target SCG configuration;

[0138] - Incremental target SCG configuration; and / or

[0139] - The same instructions for SCG will be used.

[0140] At operation 608, MN2 112 sends a response to the handover request to MN1 102. This response may be a handover request confirmation message. The response may include the target SCG configuration and may include the forwarding address.

[0141] At operation 610, MN1 102 provides UE 100 with an RRC reconfiguration message that prompts UE 100 to perform a handover mobility procedure. This is also referred to herein as a CHO reconfiguration message. This may include performing target MCG and SCG configurations.

[0142] At operations 612 and 614, UE 100 synchronizes with target MN2 112, including the random access procedure and the report of applied configuration at operation 612. At operation 616, UE 100 synchronizes with target SN2 114 if necessary.

[0143] In at least some examples, the mobility switching process can be a conditional handover (CHO). Both CHO and CPC are mechanisms for improving mobility robustness but are used in different mobility scenarios.

[0144] By utilizing CHO, conditional handover configuration is provided over the network for a prepared target MN, along with CHO execution (triggering) conditions evaluated by the UE to trigger the handover (i.e., UE 100 triggers CHO execution when one of the CHO execution conditions is met), improving UE mobility between master nodes. CPC improves mobility robustness and accelerates UE mobility execution between PSCells while maintaining PCells.

[0145] CHO execution conditions may optionally include at least some of the conditions of the same type as the previously defined CPC execution conditions, and may optionally include one or more different conditions.

[0146] Some, but not all, examples of this disclosure relate to processing multiple conditional mobility processes, including a first conditional mobility process (e.g., CPC) and a second conditional mobility process (e.g., CHO), wherein the first conditional mobility process includes a first configuration (e.g., target SCG) initiated by a first network node (e.g., source SN) and the second conditional mobility process includes a second configuration (e.g., target SCG configuration) initiated by a second network node (e.g., source MN).

[0147] In 3GPP standard 37.340 Rel-16, simultaneous operation of CHO and CPC is not supported. The network ensures that CPC is not enabled when CHO is configured for UE100.

[0148] Since CPC configuration and CHO configuration are provided independently by MN 102 and SN 104, without restrictions, when UE 100 receives a CHO configuration, UE 100 may have a pending CPC configuration from SN 104 (without MN involvement), that is, UE 100 has at least one CPC configuration for a ready target PSCell and is evaluating CPC execution conditions, and vice versa. Figure 7 The scene is shown in the image.

[0149] -At time T1, Figure 7 The diagram shows that when UE 100 receives a CPC reconfiguration message from SN 104 (without MN involved), UE 100 is within MCG-1 of MN 102 and within a smaller SCG-1 sub-region of SN 104.

[0150] -At time T2, Figure 7 This illustrates that UE 100 has moved toward SCG-2 (different SN 114) and MCG2 (different MN / PCell 112), but the CPC execution (triggering) condition has not yet been met. At this time, the measurement report from UE 100 to MN1 102 has indicated the possible mobility from the source PCell (source MN 102) to the target PCell (target MN 112, MCG2). Therefore, at this time, UE 100 receives a CHO RRC reconfiguration message from MN 102 (without SN involved).

[0151] -At time T3. Figure 7 This shows that UE 100 has left SCG-1 and moved to SCG-2, but has not yet left MCG-1 or entered MCG-2. Time T3 is the point where the CPC execution (triggering) condition is met (the mobility criteria for reconfiguring from SCG-1 to SCG-2 have been met). Therefore, UE 100 changes its current (source) SCG.

[0152] - At time T4, the CHO execution conditions are met. However, because the source SCG configuration is no longer the same as during CHO preparation, the UE may not be able to apply the target SCG configuration of the CHO in all cases. This may lead to handover failure.

[0153] While the restriction prohibiting simultaneous CHO-CPC addresses the above situation, this restriction causes its own problems with CPC following CHO, as described below:

[0154] -UE 100 sends a measurement report to MN 102 indicating possible mobility from the source PCell (MN 102) to the target PCell (MN 112).

[0155] - The source node (MN 102) prepares one or more target PCells (including target MN 112) and sends a CHO command with associated CHO trigger conditions to UE 100. Because a CHO is configured for UE 100, SN 104 is not allowed to configure CPC for UE 100.

[0156] -UE 100 also moves from PSCell-1 to PSCell-2 and sends a measurement report to SN 104 via SRB3.

[0157] - Due to the pending CHO, SN 104 will not provide CPC commands for UE 100 due to this restriction.

[0158] When UE 100 moves out of the source PSCell during the CHO execution window, a secondary node RLF (S-RLF) may occur. When reporting an S-RLF to source MN 102, source MN 102 may need to send another RRC reconfiguration message to reconfigure the bearer mapped to an SCG to another SCG or MCG, or wait for the pending CHO to be executed. If source MN 102 does not take any action to wait for the CHO to be executed, there will be additional interruptions for the SGG bearer. If source MN 102 decides to send an RRC reconfiguration message, it may be unreliable because UE 100 has already moved out of the source PCell (MN 102's coverage area), and the reconfiguration may also affect the pending CHO.

[0159] The example provided below proposes a mechanism to eliminate the above-mentioned problems and allow simultaneous reception and evaluation of CHO and CPC commands, thereby enabling the execution of these commands in the order in which they occur without canceling any of them.

[0160] To allow conditional reconfigurations from two network nodes, 102 and 104, to coexist, any dependencies associated with these two configurations can be considered to avoid any configuration mismatches during execution. This is explained below.

[0161] - The RRC reconfiguration message sent to UE 100 typically contains an incremental configuration relative to the current configuration. UE 100 will apply the changes received in the RRC reconfiguration message to the current source configuration.

[0162] - For CHO when UE 100 has dual connectivity, target MN 112 prepares incremental target MCG / SCG configuration based on the current MCG of source MN 102 and the current SCG of source SN configuration at the time of CHO preparation.

[0163] - When both CPC and CHO are allowed simultaneously, and if CPC is performed before CHO, the source SCG configuration at the UE has been changed and is now different from the source SCG configuration prepared by the target MN for CHO. If CHO is subsequently performed, the UE applies the target SCG configuration of CHO by using the latest source SCG configuration (which is different from the source SCG configuration on which the target MN 112 has prepared its CHO target SCG settings) as a reference. This may lead to handover execution failure or subsequent failures due to configuration mismatch.

[0164] Based on the target CHO configuration, CPC can be allowed when the target SCG configuration of the CHO does not depend on the source SCG configuration of the UE 100, or when the target SCG configuration maintains the same configuration as the source SCG configuration. The table below summarizes the different use cases that CPC can be allowed before the CHO—in other words, enabling the sequential execution of the first and second conditional mobility procedures.

[0165]

[0166] In at least some examples, the network can instruct the UE 100 whether to allow the sequential execution of CHO and CPC.

[0167] In an example implementation based on the table above, CPC followed by CHO is not allowed in the following cases:

[0168] - The target SCG configuration is incremental, and releasing the target SCG configuration during CHO execution is unacceptable. Alternatively, if the target SCG configuration of the CHO is incremental, the ongoing CPC should be terminated.

[0169] - The target SCG configuration is the same as the source SCG configuration, but it does not meet the UE capability partitioning conditions.

[0170] In the above implementation, if CPC followed by CHO is not allowed, the ongoing CPC will be terminated. The term "termination" does not necessarily require UE 100 to stop evaluating CPC execution conditions. CPC evaluation may still continue, but if the CPC execution conditions are met earlier than the CHO, the CPC execution conditions are ignored (PSCell changes are not performed). In another embodiment, termination includes stopping the evaluation of CPC execution conditions.

[0171] In this example implementation, CPC followed by CHO is allowed in the following cases:

[0172] - No target SCG configuration (switch to single connection).

[0173] - The target SCG configuration is a full configuration that does not depend on the source configuration.

[0174] - The target SCG configuration is an incremental configuration, and it is acceptable to release the target SCG configuration during CHO execution.

[0175] - The target SCG configuration is the same as the source SCG configuration and meets the UE capability partitioning conditions.

[0176] The incremental SCG configuration scenario will now be described in more detail.

[0177] Releasing the target incremental SCG configuration means that UE 100 releases the SCG portion of the CHO configuration, but will still be allowed to apply the MCG portion of the CHO configuration and complete the handover. As a result of releasing the target SCG configuration, UE 100 will not attempt to apply the incremental SCG configuration because the CPC has changed the source configuration, so the incremental configuration may not work.

[0178] In some, but not all, examples, UE 100 can also release the source SCG configuration changed due to CPC, as well as the target SCG configuration. UE 100 will now have no SCG configuration. At an appropriate time, UE 100 can add a new SCG configuration.

[0179] When UE 100 releases the target SCG configuration, UE 100 can report to SN 104 / 114 that UE 100 has released the SCG configuration.

[0180] In another embodiment, UE 100 may not release the current source SCG configuration. Instead, if a CHO reconfiguration message is received after receiving a CPC reconfiguration message but before the CPC execution conditions are met, UE 100 may not execute the ongoing CPC. That is, UE 100 may stop monitoring for CPC execution conditions to be met.

[0181] Optionally, target MN 112 can perform a check on whether releasing the target SCG configuration is acceptable (i.e., the reduced handover is completed without requiring the target SCG to be acceptable). If acceptable, the ongoing CPC is allowed to proceed, followed by the CHO, without any SCG change. If unacceptable, the ongoing CPC can be terminated to ensure that UE 100 retains its source configuration, against which a new incremental target SCG configuration can be applied.

[0182] In at least some examples, the acceptability of a release depends on the bearer mapping configuration of the target SCG. Acceptability can depend on the target radio bearer mapping configuration between the MCG and SCG. If a segmented bearer is mapped to UE100 according to the target, a release can be allowed. A segmented bearer is defined as a radio bearer that has RLC bearers in both the MCG and SCG. If there are some bearers that are fully mapped to the SCG (referred to as SCG-only bearers, not segmented bearers), and if these bearers are time-sensitive during handover, a release can be disallowed because it is desirable not to interrupt bearer services between the MN and SN in this case. Bearers can have very high interruption time requirements, so releasing these bearers during handover could result in additional interruptions, which may be unacceptable. An example of a time-sensitive bearer is a bearer with interruption time requirements below a threshold.

[0183] The "same SCG" configuration scenario will now be described in more detail.

[0184] The term "same SCG" is defined as indicating the target SCG configuration that will maintain the current source SCG configuration. The term "same" means the same SCG, but the data contained in the configuration does not necessarily have to be the same in every respect; for example, it may indicate a security key change.

[0185] Even if the SCG is the same, in some cases, the use of UE capabilities after CPC and CHO may not follow the total UE capability. Therefore, if the network does not ensure that the allocation of UE capabilities is the same, in some cases, the second execution (e.g., CHO) may exceed the total UE capability and may lead to RLF.

[0186] UE capabilities refer to the information contained in the RRC UE capability information message. Examples of UE capability categories for E-UTRA include supported modulation schemes, the maximum number of layers used for spatial multiplexing, and the maximum number of bits that can be received / transmitted in a transmission time interval. Examples of UE capabilities for NR include support for a specific number of spatial multiplexing layers (MIMO layers) in the uplink / downlink, supported modulation schemes, etc.

[0187] During multi-connectivity operations, UE capabilities may require coordination between RATs (e.g., E-UTRA and NR). Such capabilities include, for example, the frequency band combinations (below 6 GHz) that UE 100 can use in the SCG, baseband processing capabilities, and maximum power. The allocation of UE capabilities between the MN and SN configurations depends on the serving MN 102. The MN can then provide the SN with the UE capabilities available for the SCG configuration, including a list of allowed multi-connectivity frequency band combinations and feature sets. The SN indicates the selected frequency band combinations and feature sets to the MN.

[0188] Therefore, to further improve reliability, an optional check is performed on resource reservations at the MCG and SCG to verify UE capabilities. This is referred to as the UE capability partitioning condition in this document. The UE capability partitioning condition can be checked as part of the add request procedure at target MN 112. Under this condition, the CPC configuration further needs to ensure that the UE capability partitioning between the MCG and SCG in the CPC configuration is substantially the same as the UE capability partitioning between the MCG and SCG in the CHO configuration.

[0189] This check can be performed by the target node of the CHO / CPC. This check ensures that the new CHO allocation between the modified SCG and the target MCG is within the UE's capabilities. If the check fails, the ongoing CPC should be terminated. If the check succeeds, CPC followed by CHO is allowed under the same SCG configuration.

[0190] In at least some examples, the above checks can be performed in the network. Furthermore, MN 102 sends information such as a message (e.g., part of a CHO reconfiguration message) to UE 100, which includes control parameters indicating whether CPC execution before CHO execution is allowed, and / or whether CHO execution before CPC execution is allowed, and / or whether a CHO with target SCG configuration release is allowed.

[0191] If CPC execution prior to CHO is permitted, UE 100 can evaluate both CPC and CHO conditions simultaneously, and UE 100 can continue evaluating CHO conditions after CPC execution. The term "sequential execution" in this document refers to enabling the coexistence of CPC and CHO without canceling one of them, and in at least some examples involves evaluating both CPC and CHO conditions simultaneously.

[0192] If CPC execution is permitted after a CHO, UE 100 is not required to cancel pending CPCs after the CHO execution. UE 100 can continue to evaluate CPC conditions after the CHO execution.

[0193] In some, but not all, examples, if it is necessary to release the target SCG configuration (e.g., because it is an incremental configuration), MN 102 can use a CHO reconfiguration message to indicate that if a CPC is executed before the CHO, the CHO configuration should be modified to release the SCG. The timing of CPC / CHO execution depends on which execution conditions are met first.

[0194] In the case of incremental configuration, control parameters can indicate whether CPC should be performed before CHO and the target SCG configuration should be released, or whether the ongoing CPC should be terminated to ensure that the target SCG configuration of CHO is successful.

[0195] In the full configuration, the control parameters allow for the sequential execution of CHO and CPC, including the sequential execution of the first SCG configuration and the second SCG configuration, without releasing the target SCG configuration.

[0196] In the absence of a target SCG configuration, control parameters can be omitted, or they can be sent in any way to indicate that sequential execution is allowed.

[0197] With the same SCG configuration, control parameters can indicate whether an ongoing CPC should be terminated to ensure the partitioning of UE capabilities.

[0198] In some, but not all, examples, the CHO reconfiguration message may contain multiple target CHO configurations for a prepared target MN. These multiple targets may each include different values ​​for the control parameters used for the sequential execution of CPC and CHO. In this case, the UE 100 may perform this sequential execution if permitted by the control parameters of the optimal "N" cells. "N" may be configured, for example, by MN 102 or 112. In one example, the term "optimal" refers to the target node most likely to satisfy the CHO execution conditions, such as the target node with the strongest radio measurements.

[0199] In examples where group "N" includes two or more targets MN, sequential execution is allowed if all targets MN in group N are allowed, but sequential execution is not allowed if at least one target MN in group N is not allowed.

[0200] Figure 8 This is an example message sequence diagram illustrating an example method 800 for controlling the sequential execution of multiple conditional mobility processes. This example relates to CPC and CHO processes, where the first network node is SN and the second network node is MN; however, it will be understood that this method can be applied to other types of conditional mobility processes and use cases.

[0201] In this method, the target network node (MN 112) of the CHO provides information on whether CPC is allowed for a given configuration and the prepared CHO configuration. Figure 8 However, in not all examples, CPC occurs before CHO.

[0202] Operation 802 involves sending a message from SN 104 to UE 100, prompting UE 100 to perform a CPC. This message can be a CPC reconfiguration message similar to Operation 503 described earlier. This message is initiated by source SN 104 without the involvement of MN.

[0203] UE 100 begins monitoring CPC execution conditions and may optionally reply to SN 104 (not shown) before the CPC execution conditions are met, reporting that a conditional reconfiguration message has been applied.

[0204] In one embodiment, source SN 104 may notify MN 102 that SN 104 has configured UE 100 with CPC (not shown) without MN's involvement. At this stage, SN 104 may not be able to confirm with MN 102 which SCG configuration UE 100 will ultimately adopt. In another embodiment, MN 102 remains unaware of the CPC.

[0205] Operation 804 involves sending a request associated with the CHO (e.g., a handover request) from MN 102 to the target MN 112. This request is similar to operation 602 described earlier. The decision to trigger the handover can be initiated by the source MN 102 based on UE measurements without the involvement of the SN.

[0206] If MN 102 is aware of the CPC, then MN 102 can send an indication (“SCG-Change-Possible”) to the target MN 112 that the CPC has been initiated by SN 104. This indication can be sent along with a switch request message. This indicates the possibility of an SCG change prior to the execution of the CHO.

[0207] Upon receiving a handover request, target MN 112 prepares to respond (e.g., a "handover request confirmation" message). This preparation may include messages from operations 604 and 606 described above (not shown here), enabling target MN 112 to obtain the target SCG configuration (if any) from source SN 104 or target SN 114 (depending on whether an SN change is required).

[0208] At operation 806, target MN 112 sends a response to the handover request (a "handover request confirmation" message) to MN 102. This is similar to operation 608. However, in method 800, in response, target MN 112 provides information (e.g., flags) for controlling the sequential execution of CHO-CPC, as well as the target SCG configuration for the CHO configuration. The flags can be Boolean flags.

[0209] This information may include a first flag (“CPC-Before-CHO-Allowed”). This first flag indicates whether CPC is allowed to continue before CHO execution (whether source SCG changes are allowed before CHO execution). The first flag allows CPC before CHO when the CHO configuration has no target SCG configuration or when the target SCG is fully configured.

[0210] This information may also include a second flag (“CHO-without-SCG”) indicating whether a switchover completion without a target SCG configuration is acceptable. This second flag enables the source MN 102 to determine whether to allow the release of the target SCG configuration.

[0211] Will be addressed later Figure 9 Describe an example of a third flag (“CPC-After-CHO”) used to allow CHO before CPC.

[0212] Upon receiving the flags, source MN 102 can determine one or more control parameters to send to UE 100 based on these flags. In one example implementation, a maximum of three control parameters are sent:

[0213] -First control parameter( Figure 8 = "CPC-Before-CHO" = Yes / No (e.g., Boolean flag). This is based at least on the first flag.

[0214] -Second control parameter ( Figure 8 = "CHO-Change-After-CPC" = "SCG Release" or "None" (e.g., a Boolean flag). This is based at least on the second flag.

[0215] -Third control parameter ( Figure 9 = "CPC-After-CHO" = Allowed / Disallowed (e.g., Boolean flag). This is based at least on the third flag.

[0216] The first control parameter determines whether the ongoing CPC can continue. If the first flag indicates a full target SCG configuration or no target SCG setting, the first control parameter allows CPC to proceed before CHO.

[0217] In one example, the first control parameter depends not only on the first flag but also on the second flag. With an incremental target SCG configuration, if the second flag allows SCG release (CHO without SCG), the first control parameter allows CPC before CHO. If the second flag does not allow SCG release, the first control parameter does not allow CPC before CHO.

[0218] Assuming that the ongoing CPC is allowed to continue, the second control parameter controls the execution of the CHO.

[0219] If the CHO configuration includes an incremental target SCG configuration, and if CPC is executed first, the second control parameter can have the value "SCG-Release," which indicates that the target SCG configuration is released during CHO execution. The value "SCG-Release" can be set when the second flag indicates that SCG release is acceptable. If there is no target SCG configuration, the second control parameter can have the value "None" or be omitted.

[0220] Will be addressed later Figure 9 Describe the third control parameter.

[0221] In the example above, three flags and three control parameters were identified. Alternatively, these flags could be combined into fewer flags and / or these control parameters could be combined into fewer control parameters.

[0222] In the example above, source MN 102 is responsible for determining each control parameter (e.g., a flag from target MN 112 to guide the determination) based on coordination between source MN 102 and target MN 112. In other examples, the UE is responsible for determining at least one control parameter based on a corresponding flag from target MN 112. In still other examples, the responsibility lies with target MN 112, in which case the flag from target MN 112 is actually the control parameter. Responsibility can even be distributed among entities.

[0223] At operation 808, source MN 102 sends a CHO reconfiguration message with CHO configuration (including target SCG configuration) to UE 100, similar to operation 610. However, in method 800, a CHO reconfiguration message with information for controlling the sequential execution of CHO-CPC is provided. This information may include a first control parameter (“CPC-Before-CHO”) and / or a second control parameter (“CHO-Change-after-CPC”).

[0224] At operation 810, the CPC execution conditions are met. Operation 812 includes CPC execution (e.g., similar to operations 507 and 509). If the first and second control parameters permit "CPC Before CHO" sequential execution, then operations 810 and 812 are executed before CHO.

[0225] If the second control parameter indicates no target SCG configuration (“CHO-Change-after-CPC=None”), operations 814 and 816 occur. At operation 814, the CHO execution condition is met. Operation 816 involves CHO execution (e.g., similar to operations 612, 614) without changing the SCG configuration.

[0226] If the second control parameter indicates that the target SCG configuration is released during CHO execution (“CHO-Change-after-CPC=SCG-Release”), operations 818 and 820 occur. At operation 818, the CHO execution conditions are met. UE 100 releases the target SCG configuration from the CHO configuration. Then, UE 100 can perform CHO execution (e.g., similar to operation 816). Operation 820 is similar to reporting operation 614, except that the report may include an indication that the target SCG configuration has been released.

[0227] although Figure 8 The diagram shows CPC execution prior to CHO, but it does not show cases where CPC execution conditions are met after operations 816 or 820. In some scenarios, CPC can still be executed after CHO. CPC can be executed after CHO if target MN 112 does not modify the current SCG configuration (as described as "same SCG") as part of the handover. This is because CHO execution does not modify the current SCG configuration, except for minor changes such as security key changes. In this case, UE100 can also continue pending CPC measurements and evaluations.

[0228] In the following Figure 9 The diagram shows the message sequence diagram of CPC execution following CHO execution. Figure 9 Example method 900 is shown. In general, the third flag and the third control parameter indicate whether CHO followed by CPC is allowed.

[0229] Operation 902 is a CPC reconfiguration request from SN 104 to UE 100 as per operation 802. Operation 904 is a handover request from MN 102 to target MN 112 as per operation 804.

[0230] Operations 906 and 908 are based on the add request and confirmation response of operations 604 and 606, for illustrative purposes, from Figure 8 These operations are omitted in the original text. In this example, the request and response are between the target MN 112 and the source SN 104, where the response indicates that the SCG configuration has not been changed ("same SCG" scenario). For example, the response could contain the same SCG configuration as the UE's current SCG configuration.

[0231] Operation 910 is a response to a switching request from target MN 112 to source MN 102 as per operation 806. However, in this case, a third flag indicates whether "CHO-After-CHO" is permitted.

[0232] The target MN 112 can determine the third flag by examining the UE capability classification conditions described above.

[0233] The third flag enables the source MN 102 to determine a third control parameter (“CPC-After-CHO”) based on the third flag. This third control parameter determines whether the ongoing CPC can continue after the CHO is executed, assuming that the CPC conditions are still being monitored during the CHO execution.

[0234] Operation 912 is a CHO reconfiguration message similar to operation 810. In method 900, a CHO reconfiguration message with information such as a third control parameter (“CPC-After-CHO”) is provided.

[0235] Operation 914 is a CHO execution similar to operation 816. At this point, the CPC execution conditions have not yet been met.

[0236] At operation 916, if CHO followed by CPC is permitted, the UE continues to evaluate the pending CPC. At operation 918, CPC execution is performed. If CHO followed by CPC is not permitted, operations 916 and 918 are omitted.

[0237] Figure 10 An example of controller 1600 is shown. Controller 1600 can be implemented as a controller circuit. Controller 1600 can be implemented solely in hardware, with some aspects in software (including separate firmware), or it can be a combination of hardware and software (including firmware).

[0238] like Figure 10 As shown, the controller 1600 can be implemented using instructions that implement hardware functions, for example, by using executable instructions of a computer program 1606 in a general-purpose or special-purpose processor 1602, which can be stored on a computer-readable storage medium (disk, memory, etc.) for execution by such processor 1602.

[0239] Processor 1602 is configured to read from and write to memory 1604. Processor 1602 may also include an output interface through which processor 1602 outputs data and / or commands; and an input interface through which data and / or commands are input to processor 1602.

[0240] Memory 1604 stores a computer program 1606, including computer program instructions (computer program code), which controls the operation of devices 2 and 100 when loaded into processor 1602. The computer program instructions of computer program 1606 enable the devices to execute... Figure 4-9 The logic and routines of the method are shown. Processor 1602 is able to load and execute computer program 1606 by reading memory 1604.

[0241] Therefore, devices 2 and 100 include:

[0242] At least one processor 1602; and

[0243] At least one memory 1604 including computer program code,

[0244] The at least one memory 1604 and the computer program code are configured, together with at least one processor 1602, to cause the device 2, 100 to perform at least the following:

[0245] A component that controls the execution of multiple conditional mobility processes, including a first conditional mobility process and a second conditional mobility process. The first conditional mobility process includes a first configuration initiated by a first network node, and the second conditional mobility process includes a second configuration initiated by a second network node.

[0246] Controlling the execution of multiple conditional mobility processes includes: controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration.

[0247] If device 2 is configured to act as a second network node (e.g., source MN 102), controlling the sequential execution of multiple conditional mobility processes may include performing at least some of the operations described in methods 800 and 900, which include at least some of the following:

[0248] - Receiving the first conditional mobility procedure (e.g., CPC) is an instruction initiated by a first network node (e.g., SN 104) (e.g., from source SN 104); and

[0249] - Initiating a second conditional mobility procedure (e.g., CHO) includes at least some of the following:

[0250] - Operation 804 / 904: Send a request (e.g., a handover request) associated with a second conditional mobility procedure (e.g., CHO) to a target network node (e.g., target MN 112), wherein the request may indicate that the first conditional mobility procedure was initiated by the first network node;

[0251] - Operation 806 / 910: Receive a response (e.g., a handover request confirmation) from the target network node including configuration information (e.g., CHO configuration) (which includes a second configuration (e.g., target SCG configuration)) and information for controlling the sequential execution of the first and second conditional mobility processes, wherein the information includes at least one flag (e.g., a first flag, a second flag, and a third flag) indicating whether the sequential execution of the first and second conditional mobility processes is permissible (e.g., before / after), or whether it is permissible and releases the second configuration; and

[0252] - Operation 808 / 912: Based on the response, send a second configuration (e.g., a CHO reconfiguration message) and at least one control parameter (e.g., a first control parameter, a second control parameter, and a third control parameter) to the user equipment, which includes information for controlling the sequential execution of the first conditional mobility process and the second conditional mobility process.

[0253] If device 2 is configured to act as a target network node (e.g., target MN 112), controlling the sequential execution of multiple conditional mobility processes may include at least some of the operations described in methods 800 and 900, which include at least some of the following:

[0254] - Operation 804 / 904: Receive the above request (e.g., a switch request);

[0255] - Operation 906: Send a request for the second configuration (e.g., add request) to the first network node (e.g., source SN 104) or the target secondary node (e.g., target SN 114);

[0256] - Operation 908: In response to the add request, receive an acknowledgment from the first network node / target secondary node, which includes an indication of a second configuration (e.g., target SCG configuration) or the use of an existing source configuration (e.g., the same SCG);

[0257] - Operation 806 / 910: Send a response (e.g., a switch request confirmation) to the second network node (source MN 102), as described above.

[0258] If the device is configured to function as UE 100, controlling the sequential execution of multiple conditional mobility procedures may include: the mobile device 100 receiving a message (e.g., from MN 102 or 112) for controlling the sequential execution of a first conditional mobility procedure and a second conditional mobility procedure based on a first configuration and a second configuration. The UE device 100 may include components for performing at least some of the additional operations described in methods 800 and 900, including at least some of the following operations:

[0259] - Receive a first reconfiguration message (e.g., a CPC reconfiguration message) that prompts the device to perform a first conditional mobility procedure;

[0260] - Monitor the conditions for the first conditional mobility process to be met;

[0261] - Receive a second reconfiguration message (e.g., a CHO reconfiguration message) that prompts the device to perform a second conditional mobility process, the second reconfiguration message including information for controlling the sequential execution of the first conditional mobility process and the second conditional mobility process, wherein the information includes at least one control parameter (e.g., a first control parameter, a second control parameter, and a third control parameter).

[0262] - Based on at least one control parameter, control the sequential execution of the first conditional mobility process and the second conditional mobility process; and

[0263] - When performing the second conditional mobility procedure and releasing the second configuration, a report indicating the completion of the second conditional mobility procedure (RRC reconfiguration completion message) is sent to the target master node, wherein the report includes an indication of releasing the second configuration during the execution of the second conditional mobility procedure.

[0264] As shown in Figure 1700, computer program 1606 can reach devices 2 and 100 via any suitable transmission mechanism 1700. This transmission mechanism 1700 can be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a storage device, a recording medium (such as an optical disc read-only memory (CD-ROM) or digital versatile optical disc (DVD) or solid-state storage), or an article of manufacture that includes or tangibly embodies computer program 1606. The transmission mechanism can be a signal configured to reliably transmit computer program 1606. Devices 2 and 100 can propagate or transmit computer program 1606 as computer data signals.

[0265] Computer program instructions can cause a computer (e.g., a device, a network node) to perform at least the following operations:

[0266] A component that controls the execution of multiple conditional mobility processes, including a first conditional mobility process and a second conditional mobility process. The first conditional mobility process includes a first configuration initiated by a first network node, and the second conditional mobility process includes a second configuration initiated by a second network node.

[0267] Controlling the execution of multiple conditional mobility processes includes: controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration.

[0268] Computer program instructions can be included in a computer program, a non-transitory computer-readable medium, a computer program product, or a machine-readable medium. In some, but not all, examples, computer program instructions can be distributed across more than one computer program.

[0269] Although memory 1604 is shown as a single component / circuit, it can be implemented as one or more separate components / circuits, some or all of which may be integrated / removable and / or provide permanent / semi-permanent / dynamic / cached storage.

[0270] Although processor 1602 is shown as a single component / circuit, it can be implemented as one or more separate components / circuits, some or all of which may be integrated / removable. Processor 132 may be a single-core or multi-core processor.

[0271] References to “computer-readable storage medium,” “computer program product,” “tangible computer program,” or “controller,” “computer,” “processor,” etc., should be understood to encompass not only computers with different architectures such as single / multiple processor architectures and serial (von Neumann) / parallel architectures, but also special-purpose circuits such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), signal processing devices, and other processing circuits. References to computer programs, instructions, code, etc., should be understood to encompass software for programmable processors, or firmware that may include programmable content such as hardware devices that may include instructions for processors, or configuration settings for fixed-function devices, gate arrays, or programmable logic devices, etc.

[0272] As used in this application, the term "circuit" may refer to one or more of the following:

[0273] (a) Hardware circuit implementation only (such as implementation of analog and / or digital circuits only);

[0274] (b) A combination of hardware circuitry and software, such as (if applicable):

[0275] (i) a combination of analog and / or digital hardware circuitry with software / firmware; and

[0276] (ii) Any part of a hardware processor having software (including digital signal processors, software, and memory, which work together to enable a device such as a mobile phone or server to perform various functions); and

[0277] (c) Hardware circuitry and / or processors, such as microprocessors or parts thereof, which require software (e.g., firmware) to operate, but may be absent when operation does not require software.

[0278] This definition of "circuit" applies to all uses of the term in this application, including its use in any claim. As another example, as used in this application, the term "circuit" also covers only the implementation of hardware circuitry or processors and their accompanying software and / or firmware. The term "circuit" also covers (e.g., and if applicable, baseband integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices).

[0279] Figure 4-9 The boxes shown may represent steps in the method and / or code segments in computer program 1606. The illustration of a particular order of boxes does not imply a required or preferred order for these boxes, but rather that the order and arrangement of the boxes may be changed. Furthermore, some boxes may be omitted.

[0280] Where a structural feature has been described, it can be replaced by a component that performs one or more functions for performing that structural feature, whether or not the function or these functions are explicitly described or implicitly described.

[0281] The examples described above demonstrate applications that implement components such as:

[0282] Automotive systems; telecommunications systems; electronic systems, including consumer electronics; distributed computing systems; media systems for generating or rendering media content, including audio, visual, and audiovisual content, as well as mixed, mediated, virtual, and / or augmented reality; personal systems, including personal medical systems or personal health / fitness systems; navigation systems; user interfaces, also known as human-machine interfaces; networks, including cellular, non-cellular, and optical networks; self-organizing networks; the Internet; the Internet of Things; virtualized networks; and related software and services.

[0283] The term “comprising” as used herein has an inclusive rather than exclusive meaning. That is, any statement “X includes Y” means that X may include only one Y or may include more than one Y. If the intention is to use “comprising” with an exclusive meaning, it will be made clear in the context by referring to “only one…” or by using “consisting of…”.

[0284] Various examples have been referenced in this description. Descriptions of features or functionalities for an example indicate that those features or functionalities exist in that example. Whether explicitly stated or not, the use of the terms "example," "for example," "may," or "can" in the text indicates that such a feature or functionality exists at least in the described example, whether or not it is described as an example, and that such a feature or functionality may, but is not required to, exist in some or all other examples. Therefore, "example," "for example," "may," or "can" refers to a specific instance of a class of examples. The properties of an instance may be properties of that instance alone, properties of the class of instances, or properties of subclasses of the class that include some but not all instances of that class. Therefore, it is implied that features described for one example but not for another can be used in other examples as part of a working composition, but are not necessarily required to be used in other examples.

[0285] Although examples have been described with reference to various illustrations in the preceding paragraphs, it should be understood that modifications can be made to the given examples without departing from the scope of the claims. For example, a conditional mobility procedure can originate from network nodes different from the SN and MN. These two network nodes can implement the same radio access technology. A second mobility procedure can change the cell configuration without handover. The network can be different from the network defined by 3GPP.

[0286] Although functions have been described with reference to certain features, these functions can be performed by other features, whether or not they are described.

[0287] Although features have been described with reference to some examples, these features may also exist in other examples, whether or not they are described.

[0288] The terms “one” or “the” as used herein have an inclusive rather than exclusive meaning. That is, any reference to “X includes one / the Y” indicates that “X may include only one Y” or “X may include more than one Y”, unless the context clearly indicates otherwise. If the intention to use “one” or “the” with an exclusive meaning is to do so, it will be clearly stated in the context. In some contexts, “at least one” or “one or more” may be used to emphasize an inclusive meaning, but the absence of these terms should not be construed as indicating any non-exclusivity.

[0289] The presence of a feature (or combination of features) in a claim is a reference to that feature (or combination of features) itself, and also a reference to a feature (equivalent feature) that achieves substantially the same technical effect. Equivalent features include, for example, features that are variations and achieve substantially the same result in substantially the same manner. Equivalent features include, for example, features that perform substantially the same function in substantially the same manner to achieve substantially the same result.

[0290] This description has referenced various examples using adjectives or adjective phrases to describe the characteristics of the examples. This description of the characteristics of the examples indicates that the characteristic is exactly the same as described in some examples, and substantially the same as described in others.

[0291] Although the foregoing description attempts to point out those features considered important, it should be understood that an applicant may seek protection by means of the claims for any patentable features or combinations thereof shown herein with reference to the accompanying drawings and / or the drawings, whether or not they have been emphasized.

Claims

1. An apparatus for communication, comprising components for controlling the execution of a plurality of conditional mobility processes, the conditional mobility processes including a first conditional mobility process and a second conditional mobility process, the first conditional mobility process including a first configuration initiated by a first network node, and the second conditional mobility process including a second configuration initiated by a second network node. in, Controlling the execution of the plurality of conditional mobility processes includes: controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration; The sequential execution is controlled based on the dependency of the second configuration on the source configuration. Furthermore, the first configuration can change the source configuration; The second conditional mobility process includes multiple target configurations associated with different target nodes, and not all of the target nodes allow the sequential execution of the first and second conditional mobility processes. Furthermore, the apparatus further includes a component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process when permitted by a set of "N" target nodes most likely to satisfy the triggering conditions of the second conditional mobility process.

2. The apparatus according to claim 1, comprising: A component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process, depending on whether the second configuration is a full configuration.

3. The apparatus according to claim 1 or 2, comprising: A component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process and releasing the second configuration, depending on whether the second configuration is an incremental configuration relative to the source configuration.

4. The apparatus according to claim 3, comprising: A component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process and releasing the second configuration, depending on whether releasing the second configuration is acceptable, wherein whether releasing the second configuration is acceptable depends on the bearer mapping of the second configuration.

5. The apparatus according to claim 1 or 2, comprising: A component for enabling the sequential execution of the first configuration and the second configuration, depending on whether the second configuration contains the same configuration as the source configuration.

6. The apparatus according to claim 5, comprising: A component for enabling the sequential execution of the first configuration and the second configuration, depending on whether the second configuration contains the same configuration as the source configuration and satisfies the user equipment capability partitioning conditions.

7. The apparatus according to claim 1 or 2, wherein, The second conditional mobility procedure is a conditional master node handover process triggered by a reconfiguration message initiated by the second network node. The second network node is the source master node. The reconfiguration message from the second network node includes: - A set of one or more target configurations associated with different target master nodes; - A set of one or more switching trigger conditions; and -Including the second configuration of the target secondary cell group configuration, The first conditional mobility process is a conditional primary / secondary cell change process triggered by a reconfiguration message initiated by the first network node. The first network node is a secondary node. Furthermore, the reconfiguration message from the first network node includes a set of one or more primary and secondary cell configurations containing the first configuration.

8. An apparatus for communication, comprising components for controlling the execution of a plurality of conditional mobility processes, the conditional mobility processes including a first conditional mobility process and a second conditional mobility process, the first conditional mobility process including a first configuration initiated by a first network node, and the second conditional mobility process including a second configuration initiated by a second network node. in, Controlling the execution of the plurality of conditional mobility processes includes: receiving a message for controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration; The sequential execution is controlled based on the dependency of the second configuration on the source configuration. Furthermore, the first configuration can change the source configuration; The second conditional mobility process includes multiple target configurations associated with different target nodes, and not all of the target nodes allow the sequential execution of the first and second conditional mobility processes. Furthermore, the apparatus further includes a component for enabling the sequential execution of the first conditional mobility process and the second conditional mobility process when permitted by a set of "N" target nodes most likely to satisfy the triggering conditions of the second conditional mobility process.

9. A method for communication, comprising: The system controls the execution of multiple conditional mobility processes, including a first conditional mobility process and a second conditional mobility process. The first conditional mobility process includes a first configuration initiated by a first network node, and the second conditional mobility process includes a second configuration initiated by a second network node. Controlling the execution of the plurality of conditional mobility processes includes: controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration; The sequential execution is controlled based on the dependency of the second configuration on the source configuration. Furthermore, the first configuration can change the source configuration; The second conditional mobility process includes multiple target configurations associated with different target nodes, and not all of the target nodes allow the sequential execution of the first and second conditional mobility processes. Furthermore, when permitted by a set of "N" target nodes most likely to satisfy the triggering conditions of the second conditional mobility process, the sequential execution of the first conditional mobility process and the second conditional mobility process is controlled.

10. A computer program product having stored computer-executable instructions thereon, which, when executed by a device, cause the device to perform: The system controls the execution of multiple conditional mobility processes, including a first conditional mobility process and a second conditional mobility process. The first conditional mobility process includes a first configuration initiated by a first network node, and the second conditional mobility process includes a second configuration initiated by a second network node. in, Controlling the execution of the plurality of conditional mobility processes includes: controlling the sequential execution of the first conditional mobility process and the second conditional mobility process based on the first configuration and the second configuration; The sequential execution is controlled based on the dependency of the second configuration on the source configuration. Furthermore, the first configuration can change the source configuration; The second conditional mobility process includes multiple target configurations associated with different target nodes, and not all of the target nodes allow the sequential execution of the first and second conditional mobility processes. Furthermore, when permitted by a set of "N" target nodes most likely to satisfy the triggering conditions of the second conditional mobility process, the sequential execution of the first conditional mobility process and the second conditional mobility process is controlled.

Images