Mobility management method and apparatus using same

Abstract

A method of providing mobility management is provided. The method includes receiving at least one reference configuration identifier and a candidate configuration; generating a complete configuration based on the at least one reference configuration identifier and the candidate configuration; and performing a cell handover to the candidate network node corresponding to the candidate configuration using the full configuration.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a method for mobility management applicable to a user equipment (UE), a source network node, and a network system. BACKGROUND

[0002] Layer 1 (L1) / Layer 2 (L2) triggered mobility (LTM) is introduced in 3rd Generation Partnership Project (3GPP) Release 18 (Rel-18). In the Rel-18 LTM framework, reference configurations (RCs) in LTM-config are introduced to reduce the signaling overhead caused by candidate configurations (CCs) for multiple candidate cells in LTM-candidate. In Rel-18, only one reference configuration is needed for intra-centralized unit (intra-CU) LTM. However, in inter-centralized unit (inter-CU) LTM in Release 19 (Rel-19), radio bearer configurations or measurement configurations can be different between centralized units (CUs). Therefore, improving the signaling efficiency of inter-CU LTM becomes a key challenge in the art. SUMMARY

[0003] The present disclosure relates to a method for mobility management applicable to a user equipment (UE), a source network node, and a network system.

[0004] The present disclosure relates to a method for mobility management applicable to a user equipment (UE), a source network node, and a network system.

[0005] In one embodiment of the present disclosure, the candidate configuration comprises a delta configuration relative to the at least one reference configuration identifier.

[0006] In one embodiment of the disclosure, the method further includes obtaining a reference configuration corresponding to the at least one reference configuration identifier; considering the reference configuration as a current UE configuration; and applying the delta configuration to obtain the complete configuration.

[0007] In one embodiment of the disclosure, the complete configuration includes at least one of a measurement configuration, mobility control information, a radio resource control (RRC) configuration, a packet data convergence protocol (PDCP) configuration, a radio link control (RLC) configuration, a medium access control (MAC) configuration, a physical layer (PHY) configuration, or a security configuration.

[0008] In one embodiment of the disclosure, the at least one reference configuration identifier is received through a mobility configuration message.

[0009] In one embodiment of the disclosure, the at least one reference configuration identifier is received through a cell handover command corresponding to the candidate network node.

[0010] In one embodiment of the disclosure, the at least one reference configuration identifier corresponds to a main reference configuration related to a plurality of candidate network nodes of the UE and a candidate reference configuration related to a part of the plurality of candidate network nodes, and the complete configuration is generated by combining the main reference configuration, the candidate reference configuration, and the candidate configuration.

[0011] In one embodiment of the disclosure, the method further includes selecting a reference configuration identifier corresponding to the candidate network node from the at least one reference configuration identifier, and the complete configuration is generated based on the reference configuration identifier and the candidate configuration.

[0012] In one embodiment of the disclosure, the method further includes receiving the configuration and determining whether the parameter is included in the configuration, and in response to the parameter being included in the configuration, generating the complete configuration based on the reference configuration identifier and the candidate configuration.

[0013] In one embodiment of the disclosure, the configuration includes the at least one reference configuration identifier and the candidate configuration.

[0014] In one embodiment of this disclosure, the complete configuration is applied by the UE in response to a conditional triggering event related to mobility operation, wherein the conditional triggering event includes at least one of the following: conditional handover (CHO), conditional lower-layer triggered mobility (C-LTM), or conditional policy-assisted configuration (CPAC).

[0015] In one embodiment of this disclosure, the step of generating a complete configuration based on at least one reference configuration identifier and a candidate configuration includes: obtaining a reference configuration corresponding to at least one reference configuration identifier, wherein the reference configuration is pre-configured to the UE; and combining the reference configuration and the candidate configuration to generate a complete configuration.

[0016] In one embodiment of this disclosure, at least one reference configuration identifier and candidate configuration are received via a low-level trigger configuration.

[0017] In one embodiment of this disclosure, at least one reference configuration identifier and a candidate configuration are received via a handover configuration.

[0018] This disclosure relates to a method for mobility management applicable to a source network node. The method includes: generating a reference configuration; transmitting the reference configuration to a candidate network node; receiving a candidate configuration and an indicator from the candidate network node; generating a mobility configuration message based on the reference configuration, the candidate configuration, and the indicator; and transmitting the mobility configuration message to a user equipment (UE).

[0019] In one embodiment of this disclosure, the candidate configuration includes an incremental configuration relative to the reference configuration.

[0020] This disclosure relates to a method for mobility management applicable to a network system. The method includes: generating a reference configuration by a source network node of the network system; generating a candidate configuration by a candidate network node of the network system, wherein the candidate configuration is transmitted from the candidate network node to the source network node; and transmitting the reference configuration and the candidate configuration by the source network node to a user equipment (UE) of the network system.

[0021] In one embodiment of this disclosure, the method further includes: combining a reference configuration and a candidate configuration by the UE to generate a complete configuration; and applying the complete configuration by the UE to perform a cell handover to a candidate network node.

[0022] In one embodiment of this disclosure, candidate configurations are generated by candidate network nodes based on reference configurations.

[0023] In one embodiment of the disclosure, the candidate configuration contains delta configuration relative to the reference configuration.

[0024] In order to make the foregoing more readily understood, the following detailed description, taken in conjunction with the accompanying drawings, illustrates several embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0025] The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments and, together with the description, serve to explain principles of the disclosure.

[0026] Figure 1 A schematic diagram illustrating LTM procedure is shown in accordance with one embodiment of the disclosure.

[0027] Figure 2 A schematic diagram illustrating LTM-configuration is shown in accordance with one embodiment of the disclosure.

[0028] Figure 3 A schematic diagram illustrating signaling overhead of candidate configuration is shown in accordance with one embodiment of the disclosure.

[0029] Figure 4 A schematic diagram illustrating CC commonality between different candidate cells is shown in accordance with one embodiment of the disclosure.

[0030] Figure 5 A flow diagram for generating complete CC in accordance with one embodiment of the disclosure.

[0031] Figure 6 A schematic diagram illustrating LTM in CU is shown in accordance with one embodiment of the disclosure.

[0032] Figure 7 A schematic diagram illustrating inter-CU LTM is shown in accordance with one embodiment of the disclosure.

[0033] Figure 8 A schematic diagram illustrating RC architecture is shown in accordance with one embodiment of the disclosure.

[0034] Figure 9 A schematic diagram illustrating M-RC architecture is shown in accordance with one embodiment of the disclosure.

[0035] Figure 10 A schematic diagram illustrating configuration model of M-RC is shown in accordance with one embodiment of the disclosure.

[0036] Figure 11 A flow diagram for generating complete CC is shown in accordance with one embodiment of the disclosure.

[0037] Figure 12 A signaling diagram for cell handover is shown in accordance with one embodiment of the disclosure.

[0038] Figure 13 A signaling diagram illustrating LTM recovery triggered by radio link failure (RLF) according to one embodiment of the disclosure.

[0039] Figure 14 A signaling diagram illustrating LTM recovery triggered by cell handover failure according to one embodiment of the disclosure.

[0040] Figure 15 A signaling diagram illustrating configuration procedure after LTM recovery according to one embodiment of the disclosure.

[0041] Figure 16 A signaling diagram illustrating generation of reference configuration and candidate configurations according to one embodiment of the disclosure.

[0042] Figure 17 A signaling diagram illustrating generation of RC according to one embodiment of the disclosure.

[0043] Figure 18 A signaling diagram illustrating generation of RC according to one embodiment of the disclosure.

[0044] Figure 19 A signaling diagram illustrating generation of M-RC and CC according to one embodiment of the disclosure.

[0045] Figure 20 A signaling diagram illustrating generation of M-RC and CC according to one embodiment of the disclosure.

[0046] Figure 21 A signaling diagram illustrating generation of RC and CC according to one embodiment of the disclosure.

[0047] Figure 22 A signaling diagram illustrating generation of RC and CC according to one embodiment of the disclosure.

[0048] Figure 23 A signaling diagram illustrating generation of RC and CC according to one embodiment of the disclosure.

[0049] Figure 24 A signaling diagram illustrating generation of RC and CC according to one embodiment of the disclosure.

[0050] Figure 25 A signaling diagram illustrating generation of RC and CC according to one embodiment of the disclosure.

[0051] Figure 26 A signaling diagram illustrating LTM-configuration according to one embodiment of the disclosure.

[0052] Figure 27 A signaling diagram illustrating configuration architecture according to one embodiment of the disclosure.

[0053] Figure 28A flow diagram illustrating generation of a complete CC is explained according to one embodiment of the disclosure.

[0054] Figure 29 A flow diagram illustrating generation of a complete CC is explained according to one embodiment of the disclosure.

[0055] Figure 30 A signaling diagram illustrating cell handover is explained according to one embodiment of the disclosure.

[0056] Figure 31 A signaling diagram illustrating generation of HR and CR lists is explained according to one embodiment of the disclosure.

[0057] Figure 32 A signaling diagram illustrating generation of HR and CR lists is explained according to one embodiment of the disclosure.

[0058] Figure 33 A signaling diagram illustrating generation of HR and CR lists is explained according to one embodiment of the disclosure.

[0059] Figure 34 A signaling diagram illustrating generation of HR and CR lists is explained according to one embodiment of the disclosure.

[0060] Figure 35 A signaling diagram illustrating generation of HR and CR lists is explained according to one embodiment of the disclosure.

[0061] Figure 36 A schematic diagram illustrating LTM-configuration is explained according to one embodiment of the disclosure.

[0062] Figure 37 A flow diagram illustrating generation of a complete CC is explained according to one embodiment of the disclosure.

[0063] Figure 38 A signaling diagram illustrating cell handover is explained according to one embodiment of the disclosure.

[0064] Figure 39 A schematic diagram illustrating HO-configuration is explained according to one embodiment of the disclosure.

[0065] Figure 40 A flow diagram illustrating generation of a complete CC is explained according to one embodiment of the disclosure.

[0066] Figure 41 A signaling diagram illustrating generation of a reference configuration is explained according to one embodiment of the disclosure.

[0067] Figure 42 A signaling diagram illustrating generation of RC and CC is explained according to one embodiment of the disclosure.

[0068] Figure 43 A signaling diagram illustrating generation of RC and CC is explained according to one embodiment of the disclosure.

[0069] Figure 44 A diagram illustrating HO-configuration according to one embodiment of the disclosure.

[0070] Figure 45 A flow diagram illustrating generation of complete CC according to one embodiment of the disclosure.

[0071] Figure 46 A flow diagram illustrating generation of complete CC according to one embodiment of the disclosure.

[0072] Figure 47 A diagram illustrating condition-configuration according to one embodiment of the disclosure.

[0073] Figure 48 A flow diagram illustrating generation of complete CC according to one embodiment of the disclosure.

[0074] Figure 49 A signaling diagram illustrating generation of reference configuration according to one embodiment of the disclosure.

[0075] Figure 50 A signaling diagram illustrating triggering of CHO, C-LTM or CPAC according to one embodiment of the disclosure.

[0076] Figure 51 A signaling diagram illustrating generation of RC and CC according to one embodiment of the disclosure.

[0077] Figure 52 A signaling diagram illustrating generation of RC and CC according to one embodiment of the disclosure.

[0078] Figure 53 A diagram illustrating condition-configuration according to one embodiment of the disclosure.

[0079] Figure 54 A diagram illustrating configuration architecture according to one embodiment of the disclosure.

[0080] Figure 55 A flow diagram illustrating generation of complete CC according to one embodiment of the disclosure.

[0081] Figure 56 A flow diagram illustrating generation of complete CC according to one embodiment of the disclosure.

[0082] Figure 57 A flow diagram illustrating a method of mobility management according to one embodiment of the disclosure.

[0083] Figure 58 A flow diagram illustrating a method of mobility management according to one embodiment of the disclosure.

[0084] Figure 59A flowchart of a method of mobility management is illustrated according to one embodiment of the disclosure.

[0085] Figure 60 A schematic diagram of a communication device is illustrated according to one embodiment of the disclosure. DETAILED DESCRIPTION

[0086] Reference will now be made in detail to the exemplary embodiments of the present application, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the description to refer to the same or like parts.

[0087] Figure 1 A schematic diagram 100 of LTM procedure is illustrated according to one embodiment of the disclosure. A network (also referred to as a network node, a base station (BS), a gNB, a CU, or a cell) can transmit a configuration (e.g., LTM-configuration) of one or more candidate cells to a UE, where the configuration can at least carry information including a configuration of each candidate target cell. The configuration can provide a configuration architecture to reduce configuration overhead by reducing redundant information for inter-cell CU LTM. In response to the configuration, the UE can transmit a measurement report (e.g., L1 measurement report) to the network. Based on the measurement report, the network can transmit a cell handover command (L2 signaling, e.g., medium access control (MAC) control element (CE)) to the UE to handover to a target cell. The cell handover command can at least carry information including information related to a target cell identifier (ID). After receiving the cell handover command, the UE can perform a cell handover to a target cell corresponding to the target cell ID information by applying a configuration of the target cell.

[0088] In Rel-18 LTM framework, a reference configuration (RC) in LTM-configuration is introduced to reduce the signaling overhead of candidate configuration (CC) among multiple candidate cells. Figure 2A diagram 200 illustrating LTM-configuration is explained according to one embodiment of the disclosure. The LTM-configuration can include an RC and a candidate list. The RC can include a radio resource control (RRC) configuration, where the RRC configuration can include information for measurement configuration, mobility control, radio resource configuration (including radio bearer (RB), MAC master configuration, or physical channel configuration), or security configuration. The candidate list can include one or more LTM-candidates, where each LTM-candidate corresponds to a candidate cell for LTM. The LTM-candidate can include information such as a candidate ID (e.g., candidate cell ID), CC, or a ConfigComplete message. In one embodiment, the LTM-configuration can be carried by a cell handover command.

[0089] Figure 3 A diagram 300 illustrating signaling overhead of candidate configuration is explained according to one embodiment of the disclosure. Assume that the candidate list includes LTM-candidate 1, LTM-candidate 2, and LTM-candidate 3, where each LTM-candidate can include a candidate cell ID (e.g., candidate cell 1, candidate cell 2, or candidate cell 3), a CC, and a ConfigComplete. Each CC can include a configuration of one or more measurement objectives (MOs) to be measured (e.g., a measObject list). If candidate cell 1 wants to configure MO A, MO B, MO C, and MO D to the UE, candidate cell 2 wants to configure MO A, MO B, MO C, and MO E to the UE, and candidate cell 3 wants to configure MO A, MO B, MO C, and MO F to the UE, MO A, MO B, and MO C will be redundant information in the candidate list.

[0090] To reduce the signaling overhead of CC, the RC can carry the commonality of CCs among different candidate cells. The same information can not need to be placed in different locations of the candidate list, and the signaling overhead can be reduced accordingly. Figure 4 A diagram 400 illustrating CC commonality among different candidate cells is explained according to one embodiment of the disclosure. Assume that candidate cell 1 wants to configure MO A, MO B, MO C, and MO D to the UE, candidate cell 2 wants to configure MO A, MO B, MO C, and MO E to the UE, and candidate cell 3 wants to configure MO A, MO B, MO C, and MO F to the UE, as shown in Figure 3As shown. Since MO A, MO B, and MO C are common across different candidate cells, MO A, MO B, and MO C can be included in the RC. For example, the RC (or the list of measObjects in the RC) can contain MO A, MO B, and MO C. MO A, MO B, and MO C can be removed from the CC (or the list of measObjects in the CC) of each LTM-candidate.

[0091] The UE can combine RC and CC to produce a complete CC (also known as a complete configuration). Figure 5 This is a flowchart illustrating the generation of a complete CC according to an embodiment of the present disclosure. In step S501, the UE may receive a cell handover command from the network. In step S502, the UE may determine a candidate cell indicated by the cell handover command (or indicated by the LTM-candidate in the cell handover command). In step S503, the UE may determine whether ConfigComplete is included in the LTM-candidate. If ConfigComplete is included in the LTM-candidate, the UE may proceed to step S504. If ConfigComplete is not included in the LTM-candidate, the UE may proceed to step S505.

[0092] In step S504, the UE can consider the complete candidate configuration as a CC associated with the indicated candidate cell. The UE can generate a complete CC using only the CC. In step S505, the UE can consider the complete candidate configuration as a combination of an RC and a CC associated with the indicated candidate cell. The UE can generate a complete CC by combining the RC with the CC associated with the indicated candidate cell. For example, if the target cell is... Figure 4 In candidate cell 3, the UE can combine the RC (e.g., MO A, MO B, and MO C) with the corresponding CC (e.g., MO F) of candidate cell 3. Therefore, the UE can obtain the complete CC containing the configurations of MO A, MO B, MO C, and MO F. In step S506, the UE can apply the complete CC of the indicated candidate cell to perform a cell handover to the indicated candidate cell.

[0093] In Rel-18, only one reference configuration is configured for LTM in the CU. Since only one CU is involved in LTM, one RC in LTM in the CU is sufficient. Figure 6A schematic diagram 600 illustrating the LTM in a CU is described according to an embodiment of this disclosure. The CU may represent Layer 3 (L3) of a communication system, containing an RRC entity and a Packet Data Convergence Protocol (PDCP) entity. A distributed unit (DU) may represent Layer 2 (L2) of a communication system, containing a radio link control (RLC) entity and a MAC entity. A transmission / reception point (TRP) may represent Layer 1 (L1) of a communication system, containing a physical layer (PHY) entity. Since cell 1 and cell 2 share the same CU, cell 1 and cell 2 may require similar MOs. The CU may be configured with measurement configuration, mobility control information, RRC configuration, PDCP configuration, RLC configuration, MAC configuration, PHY configuration, or security configuration information.

[0094] For inter-CU LTM, radio bearer configurations and / or measurement configurations may differ between different CUs. The commonality of candidate cell configurations between different CUs may be very small. For example, even for the same neighboring cells, different CUs may configure different parameters (e.g., nrofSS-BlocksToAverage or nrofCSI-RS-ResourcesToAverage for each CU) to form different MOs. Therefore, for some types of configurations, reference configurations may share limited commonality, and most configurations are different and provided through candidate configurations (CCs) in LTM-candidates. Figure 7 A schematic diagram 700 illustrating inter-CU LTM is shown according to an embodiment of this disclosure. CU 1 and CU 2, CU 3 and CU 4, and CU 5 and CU 6 belong to CU 1, CU 2, and CU 3, respectively.

[0095] Figure 8A schematic diagram 800 illustrating the RC architecture is provided according to an embodiment of this disclosure. Assume candidate cells 1-6 want to configure MOs as shown in Table 810. That is, the complete CC of candidate cell 1 includes MO A, MO B, MO C, and MO D. The complete CC of candidate cell 2 includes MO A, MO B, MO C, and MO E. The complete CC of candidate cell 3 includes MO F, MO G, MO H, and MO I. The complete CC of candidate cell 4 includes MO F, MO G, MO H, and MO I. The complete CC of candidate cell 5 includes MO J, MO K, and MO L. The complete CC of candidate cell 6 includes MO J, MO K, MO L, and MO M. MOs can be divided into RCs and multiple CCs, where each CC corresponds to a candidate cell. Redundancy information may be carried in the LTM configuration. For example, MO F, MO G, MO H, or MO I may be configured in both the CC of candidate cell 3 and the CC of candidate cell 4. MO J, MO K, or MO L may be configured in both the CC of candidate cell 5 and the CC of candidate cell 6.

[0096] To enjoy the signaling efficiency benefits of using the RC architecture while avoiding complex network signaling, multiple reference configurations (M-RCs) can be configured to the network system. For example, an M-RC (e.g., an M-RC with multiple RC-IDs) or one or more CCs can be configured to the UE via cell handover commands or mobility configuration messages (e.g., LTM-configuration, handover (HO) commands, or low-level triggered configuration). The MO of one or more candidate cells can be divided into M-RCs and CCs, where each CC corresponds to a candidate cell.

[0097] Figure 9A schematic diagram 900 illustrates an M-RC architecture according to an embodiment of this disclosure. Assume candidate cells 1-6 want to configure MOs as shown in Table 910. That is, the complete CC of candidate cell 1 includes MO A, MO B, MO C, and MO D. The complete CC of candidate cell 2 includes MO A, MO B, MO C, and MO E. The complete CC of candidate cell 3 includes MO F, MO G, MO H, and MO I. The complete CC of candidate cell 4 includes MO F, MO G, MO H, and MO I. The complete CC of candidate cell 5 includes MO J, MO K, and MO L. The complete CC of candidate cell 6 includes MO J, MO K, MO L, and MO M. MOs can be divided into M-RCs and one or more CCs. An M-RC can include RCs corresponding to RC-ID 1, RC-ID 2, and RC-ID 3, respectively, as shown in Table 920. The RC corresponding to RC-ID 1 can include MO A, MO B, and MO C. The RC corresponding to RC-ID 2 can include MO F, MO G, MO H, and MO I. The RC corresponding to RC-ID 3 may include MO J, MO K, and MO L. One or more CCs may include the CC corresponding to candidate cell ID 1, the CC corresponding to candidate cell ID 2, and the CC corresponding to candidate cell ID 6, as shown in Table 930. The CC corresponding to candidate cell ID 1 may include MO D. The CC corresponding to candidate cell ID 2 may include MO E. The CC corresponding to candidate cell ID 6 may include MO M.

[0098] Figure 10 A schematic diagram 1000 illustrating an M-RC configuration model according to an embodiment of this disclosure is provided. LTM-configuration may include a reference list (e.g., an RC list, an RC-ID list) and a candidate list (e.g., a CC list). The reference list may contain one or more LTM references, each LTM reference may contain an RC or an RC-ID. The candidate list may contain one or more LTM-candidates, wherein each LTM-candidate may contain a candidate ID, CC, configuration complete, or RC-ID.

[0099] In one embodiment, the RC-ID may be included in the LTM-candidate configuration. Figure 11 A flowchart illustrating the generation of a complete CC is described according to an embodiment of this disclosure. In step S1101, the UE may receive a cell handover command from the network. In step S1102, the UE may determine a candidate cell indicated by the cell handover command (i.e., indicated by the LTM-candidate in the cell handover command). In step S1103, the UE may determine whether Configuration Completion is included in the LTM-candidate. If Configuration Completion is included in the LTM-candidate, the UE may proceed to step S1104. If Configuration Completion is not included in the LTM-candidate, the UE may proceed to step S1105.

[0100] In step S1104, the UE can consider the complete candidate configuration as a CC associated with the indicated candidate cell. The UE can generate a complete CC using only the CC. In step S1105, the UE can consider the complete candidate configuration as a combination of the CC associated with the indicated candidate cell and the RC associated with the RC-ID. The UE can generate a complete CC by combining the RC with the CC associated with the indicated candidate cell. One combination method is that the UE can consider the CC as the current UE configuration and apply the RC associated with the RC-ID. In step S1106, the UE can apply the complete CC of the indicated candidate cell to perform a cell handover to the indicated candidate cell.

[0101] In one embodiment, the RC-ID may be included in the cell handover command. Figure 12 Signaling diagram 1200 for cell handover is illustrated according to an embodiment of this disclosure. The network may transmit LTM-configuration to the UE. The UE may perform channel measurements (e.g., L1 or L3 measurements) according to the LTM-configuration and may report the measurement results to the network. Based on the measurement results, the network may instruct the UE to perform cell handover by transmitting a cell handover command with RC-ID to the UE. After receiving the cell handover command, the UE may perform cell handover and obtain a complete CC from a reference configuration. Specifically, the UE may combine the CC associated with the indicated candidate cell and the RC associated with the RC-ID to generate a complete CC. One combination method may be that the UE may treat the CC as the current UE configuration and apply the RC associated with the RC-ID.

[0102] In one embodiment, if an LTM recovery occurs, the UE may not need to obtain the RC-ID. Figure 13 A schematic diagram 1300 illustrating LTM recovery triggered by a radio link failure (RLF) is provided according to an embodiment of this disclosure. After the UE receives the LTM configuration, if an RLF occurs, the UE can trigger a reconstruction procedure and perform cell selection to choose a suitable cell. If the suitable cell is a candidate cell configured in the LTM configuration, the UE will perform LTM recovery and trigger a cell handover to the candidate cell. When the UE performs the cell handover to the candidate cell, the UE can transmit a cell handover completion message to the candidate cell. Based on the above, the UE can trigger a cell handover without receiving a cell handover command from the network.

[0103] Figure 14A schematic diagram 1400 illustrating LTM recovery triggered by a cell handover failure is illustrated according to an embodiment of this disclosure. The network can transmit LTM-configuration to the UE. The UE can perform channel measurements (e.g., L1 or L3 measurements) according to the LTM-configuration and can report the measurement results to the network. Based on the measurement results, the network can instruct the UE to perform a cell handover by transmitting a cell handover command with RC-ID to the UE. After receiving the cell handover command, the UE can perform a cell handover to a candidate cell indicated by the cell handover command. If a cell handover failure occurs, the UE can trigger a reconstruction procedure and perform cell selection to select a suitable cell. If the candidate cell is selected as a suitable cell, the UE can trigger a cell handover to the candidate cell, which may be the same as or different from the candidate cell indicated by the cell handover command. When the UE successfully performs a cell handover to the candidate cell, the UE can transmit a cell handover completion message to the candidate cell.

[0104] Figure 15 Signaling diagram 1500 illustrates the configuration procedure after LTM recovery according to an embodiment of this disclosure. To obtain the complete candidate configuration when LTM recovery is triggered, the LTM recovery procedure needs to be improved. After a successful cell handover to a candidate cell, the UE can notify the candidate cell that the cell handover was triggered by LTM recovery by transmitting LTM recovery information to the candidate cell. The LTM recovery information can be carried by a cell handover completion message or a control message. Upon receiving the LTM recovery information, the candidate cell can configure relevant settings to the UE. For example, the candidate cell can transmit an RRC configuration message to the UE to configure relevant settings for the UE.

[0105] Figure 16 Signaling diagram 1600 illustrating the generation of reference configurations and candidate configurations according to one embodiment of this disclosure. Multiple reference configurations (M-RCs) may be generated by a source gNB and one or more candidate gNBs. In one embodiment, one or more candidate gNBs may generate M-RCs and CCs. In one embodiment, the source gNB may provide information to one or more candidate gNBs. One or more candidate gNBs may generate M-RCs and CCs based on the information. On the other hand, the RC used to perform LTM may be generated by the UE, the source gNB, or one or more candidate gNBs. In one embodiment, the RC-ID may be included in the LTM-candidate (or LTM-configuration) transmitted to the UE. The UE may determine the RC used to perform LTM based on the RC-ID. In one embodiment, the RC-ID may be included in the cell handover command transmitted to the UE. The UE may determine the RC used to perform LTM based on the RC-ID.

[0106] Figure 17Signaling diagram 1700 for generating an RC is illustrated according to an embodiment of this disclosure. After generating multiple reference configurations, the source gNB can generate an RC list containing the multiple reference configurations. The source gNB can transmit the RC list to the UE via an LTM-configuration (or an LTM-candidate within an LTM-configuration), wherein one or more reference configurations for one or more candidate gNBs can be included in the RC list. Furthermore, one or more RC-IDs for one or more candidate gNBs can be included in the LTM-configuration. That is, the mapping between each RC-ID and each candidate gNB is known to the UE. After receiving a cell handover command indicating a candidate gNB from the source gNB, the UE can select the RC corresponding to the candidate gNB from the RC list and generate a complete candidate configuration based on the selected RC. The UE can apply the complete candidate configuration to perform a cell handover to the candidate gNB.

[0107] Figure 18 Signaling diagram 1800 for generating an RC is illustrated according to an embodiment of this disclosure. After generating multiple reference configurations, a source gNB can generate an RC list containing the multiple reference configurations. The source gNB can transmit the RC list to one or more candidate gNBs, wherein one or more RC-IDs for the one or more candidate gNBs can be included in the RC list. The source gNB can transmit the RC list to the UE via LTM-configuration (or LTM-candidates in LTM-configuration). The source gNB can transmit the RC-ID of the corresponding candidate gNB to the UE via a cell handover command. After receiving the cell handover command, the UE can select an RC from the RC list based on the RC-ID and generate a complete candidate configuration based on the selected RC. The UE can apply the complete candidate configuration to perform a cell handover to a candidate gNB.

[0108] Figure 19 Signaling diagram 1900 illustrating the generation of M-RC and CC according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs. Upon receiving the cell handover request, one or more candidate gNBs may generate multiple reference configurations (M-RCs) and candidate configurations (CCs) for each candidate cell. One or more candidate gNBs may transmit the M-RCs and CCs to the source gNB via a cell handover request acknowledgment (ACK). The source gNB may generate an RC list, which may contain M-RCs. The source gNB may configure an RC-ID for each RC in the LTM-candidates. The source gNB may configure the CCs in the LTM-configuration. The source gNB may transmit the LTM-configuration with the RC list to the UE. After receiving a cell handover command indicating a candidate gNB from the source gNB, the UE may generate a complete configuration for the corresponding indicated candidate gNB based on the LTM-configuration with the RC list. The UE may apply the complete configuration to perform a cell handover to the candidate gNB.

[0109] In one embodiment, CC can be an incremental configuration (deltaconfiguration) relative to the corresponding RC (or RC-ID). If the UE determines that the reference configuration is the current UE configuration, the UE can apply the incremental configuration to obtain the complete configuration (or complete candidate configuration). That is, the UE can apply the incremental configuration to generate the complete configuration.

[0110] Figure 20 Signaling diagram 2000 illustrating the generation of M-RC and CC according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs. Upon receiving the cell handover request, one or more candidate gNBs may generate multiple reference configurations (M-RCs) and candidate configurations (CCs) for each candidate cell. One or more candidate gNBs may transmit the M-RCs and CCs to the source gNB via a cell handover request acknowledgment (ACK). The source gNB may generate an RC list, which may contain M-RCs. The source gNB may configure an RC-ID for each RC in the LTM-candidates. The source gNB may transmit the RC list to one or more candidate gNBs, wherein one or more RC-IDs for one or more candidate gNBs may be included in the RC list. If a candidate gNB wants to instruct a UE to perform a cell handover to a target gNB, the candidate gNB may transmit a cell handover command with the corresponding RC-ID of the target gNB to the UE. Alternatively, the source gNB may configure the CC in the LTM-configuration. The source gNB may transmit the LTM-configuration with the RC list to the UE.

[0111] After receiving a cell handover command indicating a candidate cell and its corresponding RC-ID from the source gNB, the UE can select an RC from the RC list based on the RC-ID, and the UE can generate a complete configuration for the corresponding indicated candidate gNB based on the selected RC. The UE can then apply the complete configuration to perform a cell handover to the candidate gNB.

[0112] Figure 21Signaling diagram 2100 illustrating the generation of RC and CC according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs, wherein the cell handover request may include a source-RC (S-RC, i.e., a reference configuration determined by the source gNB). Upon receiving the cell handover request, a candidate gNB may determine whether to use the S-RC. If a candidate gNB (e.g., candidate gNB 1) determines to use the S-RC, the candidate gNB may generate a CC corresponding to itself (or generate a CC for each candidate cell) based on the S-RC, wherein the CC may be an incremental configuration relative to the S-RC. The candidate gNB may confirm the transmission of an S-RC application indicator and one or more CCs to the source gNB via the cell handover request, wherein the S-RC application indicator may indicate that the S-RC has been used to generate the CC. If a candidate gNB (e.g., candidate gNB 2) determines that it will not use S-RC, the candidate gNB may generate multiple reference configurations (M-RC), and the candidate gNB may generate a CC corresponding to itself based on the M-RC (or generate a CC for each candidate gNB), where the CC may be an incremental configuration relative to the M-RC. The candidate gNB may transmit the M-RC and one or more CCs to the source gNB via a cell handover request confirmation.

[0113] The source gNB can generate an RC list, which may contain M-RCs and / or S-RCs. The source gNB can configure an RC-ID for each RC in the LTM-candidates. The source gNB can configure CCs in the LTM-configuration. The source gNB can transmit the LTM-configuration with the RC list to the UE. After receiving a cell handover command indicating a candidate gNB from the source gNB, the UE can generate a complete configuration for the indicated candidate gNB based on the LTM-configuration with the RC list. The UE can apply the complete configuration to perform a cell handover to the candidate gNB.

[0114] Figure 22Signaling diagram 2200 illustrating the generation of RC and CC according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs, wherein the cell handover request may include a source-RC (S-RC, i.e., a reference configuration determined by the source gNB). Upon receiving the cell handover request, a candidate gNB may determine whether to use the S-RC. If a candidate gNB (e.g., candidate gNB 1) determines to use the S-RC, the candidate gNB may generate a CC corresponding to itself (or generate a CC for each candidate cell) based on the S-RC, wherein the CC may be an incremental configuration relative to the S-RC. The candidate gNB may confirm the transmission of an S-RC application indicator and one or more CCs to the source gNB via the cell handover request, wherein the S-RC application indicator may indicate that the S-RC has been used to generate the CC. If a candidate gNB (e.g., candidate gNB 2) determines that it will not use S-RC, the candidate gNB may generate multiple reference configurations (M-RC), and the candidate gNB may generate a CC corresponding to itself based on the M-RC (or generate a CC for each candidate gNB), where the CC may be an incremental configuration relative to the M-RC. The candidate gNB may transmit the M-RC and one or more CCs to the source gNB via a cell handover request confirmation.

[0115] The source gNB can generate an RC list, which may contain M-RCs and / or S-RCs. The source gNB can configure an RC-ID for each RC in the LTM-candidates. The source gNB can transmit the RC list to one or more candidate gNBs, where one or more RC-IDs for the one or more candidate gNBs may be included in the RC list. If a candidate gNB wants to instruct the UE to perform a cell handover to a target gNB, the candidate gNB can transmit a cell handover command with the corresponding target gNB's RC-ID to the UE. Alternatively, the source gNB can configure the CC in the LTM-configuration. The source gNB can transmit an LTM-configuration with the RC list to the UE. After receiving a cell handover command from the source gNB indicating the candidate gNB and its corresponding RC-ID, the UE can select an RC from the RC list based on the RC-ID, and the UE can generate a complete configuration for the corresponding indicated candidate gNB based on the selected RC. The UE can apply the complete configuration to perform a cell handover to the candidate gNB.

[0116] In one embodiment, a single reference configuration (RC) for inter-CU situations may be generated by, for example, the source cell.

[0117] In one embodiment, the source gNB may take into account the CCs of other candidate gNBs to determine the RC. The candidate gNB may use the RC to regenerate the corresponding CC.

[0118] Figure 23Signaling diagram 2300 illustrating the generation of RC and CC according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs. Upon receiving the cell handover request, a candidate gNB may generate a candidate configuration (CC) corresponding to itself (or generate a CC for each candidate cell). The candidate gNB may transmit one or more CCs to the source gNB via a cell handover request acknowledgment (ACK). The source gNB may generate an RC based on the CCs received from each candidate gNB, and the source gNB may transmit RC information to one or more candidate gNBs. Upon receiving the RC information, the candidate gNB may generate (or regenerate, update) one or more CCs based on the RC, where the CCs may be incremental configurations relative to the RC. The candidate gNB may transmit one or more CCs to the source gNB. The source gNB may transmit the RC and CC to the UE via LTM-configuration.

[0119] In one embodiment, the source gNB may take into account the CCs of other candidate gNBs to determine the RC. The source gNB may use the RC to regenerate the corresponding CC for the candidate cells.

[0120] Figure 24 Signaling diagram 2400 illustrating the generation of RC and CC according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs. Upon receiving a cell handover command, a candidate gNB may generate a candidate configuration (CC) corresponding to itself (or generate a CC for each candidate cell). A candidate gNB may transmit one or more CCs to the source gNB via a cell handover request acknowledgment (ACK). The source gNB may generate an RC based on the CCs received from each candidate gNB. After the RC is generated, the source gNB may generate (or regenerate, update) a CC for each candidate cell. The source gNB may transmit the RC and CC to the UE via LTM-configuration.

[0121] In one embodiment, the source gNB can determine the RC and notify each candidate gNB of the RC. The candidate gNBs can then take the RC into consideration to generate a corresponding CC.

[0122] Figure 25Signaling diagram 2500 illustrating the generation of RC and CC according to an embodiment of this disclosure. A source gNB may generate an RC. For example, a source gNB may generate an RC by considering only the CC of its candidate cells. The source gNB may transmit an RC to one or more candidate gNBs via a cell handover request. Upon receiving a cell handover request with an RC, a candidate gNB may determine whether to use the RC. If a candidate gNB (e.g., candidate gNB 1) determines to use the RC, the candidate gNB may generate a CC corresponding to the candidate gNB itself (or generate a CC for each candidate cell) based on the RC, where the CC may be an incremental configuration relative to the RC. The candidate gNB may confirm the transmission of an RC application indicator and one or more CCs to the source gNB via the cell handover request, where the RC application indicator may indicate that the RC has been used to generate a CC. If a candidate gNB (e.g., candidate gNB 2) determines not to use the RC, the candidate gNB may generate a CC corresponding to the candidate gNB itself (or generate a CC for each candidate cell), where each CC may be a full configuration. The candidate gNB may confirm the transmission of one or more CCs to the source gNB via the cell handover request. The source gNB can transmit RC and CC to the UE via LTM-configuration.

[0123] In one embodiment, the source gNB or candidate gNB can generate only one CC for a candidate cell. In another embodiment, the source gNB or candidate gNB can generate multiple CCs for a candidate cell.

[0124] For certain configuration types that may be identical across different CUs, a reference configuration architecture with a single RC can help reduce signaling overhead for LTM between CUs. For example, a reference configuration architecture with a single RC can reduce signaling overhead for multicast / broadcast service (MBS) radio bearer (MRB) configurations. Therefore, when considering the different aspects of different configurations, a single reference configuration or multiple reference configurations alone may not be efficient in reducing signaling overhead. Single and multiple reference configuration architectures can be combined. A single reference configuration can also be called a home reference (HR). Multiple reference configurations can also be called child references (CRs).

[0125] Figure 26A schematic diagram 2600 illustrating an LTM-configuration is provided according to an embodiment of this disclosure. An LTM-configuration may include a primary reference (HR) and a list of child references (CRs). The CR list may contain one or more LTM-CRs, where each LTM-CR may contain a CR-ID and a corresponding child reference configuration (CRC). The HR or CR may contain RRC configurations, such as measurement configurations, mobility control, radio resource configurations (including RB, MAC master configuration, or physical channel configuration), or security configurations.

[0126] In one embodiment, if the configuration parameters are identical across all candidate cells (the configuration parameters are identical across N candidate cells, where N is a positive integer), the configuration parameters can be carried by the HR. If the configuration parameters are identical across a small number of candidate cells (the configuration parameters are identical across M candidate cells, where M is a positive integer less than N), the configuration parameters can be carried by the CR. If the configuration parameters are different across all candidate cells, the configuration parameters can be carried by the CC of each candidate cell. The complete configuration can be generated by combining the HR, CR, and CC.

[0127] Figure 27 A schematic diagram 2700 illustrates the configuration architecture according to an embodiment of this disclosure. Assume candidate cells 1-6 are configured with MO and MRB as shown in Table 2710. That is, the complete configuration of candidate cell 1 includes MO A, MO B, MO C, MO D, MRB A, MRB B, and MRB C. The complete configuration of candidate cell 2 includes MO A, MO B, MO C, MO E, MRB A, MRB B, and MRB C. The complete configuration of candidate cell 3 includes MO F, MO G, MO H, MO I, MRB A, MRB B, and MRB D. The complete configuration of candidate cell 4 includes MO F, MO G, MO H, MO I, MRB A, MRB B, and MRB D. The complete configuration of candidate cell 5 includes MO J, MO K, MO L, MRB A, MRB B, and MRB E. The complete configuration of candidate cell 6 includes MO J, MO K, MO L, MO M, MRB A, MRB B, and MRB E.

[0128] Table 2710 can be divided into HR, one or more CRs, and CC for each candidate cell. Specifically, since MRB A and MRBB are required for all candidate cells, MRB A and MRB B can be allocated in the HR configuration, and MRB A and MRB B can be removed from Table 2710. Since MO A, MO B, MO C, and MRB C are required for candidate cell 1 and candidate cell 2, MO A, MO B, MO C, and MRB C can be allocated in the CRs (i.e., CR 1) of the corresponding candidate cell 1 and candidate cell 2. Since MO F, MO G, MO H, MO I, and MRB D are required for candidate cell 3 and candidate cell 4, MO F, MO G, MO H, MO I, and MRB D can be allocated in the CRs (i.e., CR 2) of the corresponding candidate cell 3 and candidate cell 4. Since MO J, MO K, MO L, and MRB E are required by candidate cells 5 and 6, they can be allocated in the corresponding CRs (i.e., CR3) of candidate cells 5 and 6. Since MO D, MO E, and MO M are only required by candidate cells 1, 2, and 6, respectively, they can be allocated in the corresponding CCs of candidate cells 1, 2, and 6.

[0129] The UE can combine a primary reference configuration and a sub-reference configuration. In one embodiment, the CR configuration always exists for each UE. Figure 28 A flowchart illustrating the generation of a complete CC is described according to an embodiment of this disclosure. In step S2801, the UE may receive a cell handover command from the network. In step S2802, the UE may determine a candidate cell indicated by the cell handover command (or indicated by the LTM-candidate in the cell handover command). In step S2803, the UE may determine whether the configuration completion is included in the LTM-candidate. If the configuration completion is included in the LTM-candidate, the UE may proceed to step S2804. If the configuration completion is not included in the LTM-candidate, the UE may proceed to step S2805.

[0130] In step S2804, the UE can treat the complete candidate configuration as a CC associated with the indicated candidate cell. The UE can apply the CC as the current UE configuration. In step S2805, the UE can combine the HR and the CR associated with the CR-ID (e.g., the CR-ID corresponding to the indicated candidate cell) to generate the current configuration. In step S2806, the UE can apply the candidate configuration (CC) corresponding to the indicated candidate cell. That is, the UE can generate a complete CC by combining the current configuration with the CC. In step S2807, the UE can obtain the complete candidate configuration from step S2804 or step S2806.

[0131] In one embodiment, the CR configuration may not exist for the UE. The UE may not need to combine CRs to generate a complete configuration. Figure 29 A flowchart illustrating the generation of a complete CC is described according to an embodiment of this disclosure. In step S2901, the UE may receive a cell handover command from the network. In step S2902, the UE may determine a candidate cell indicated by the cell handover command (or indicated by the LTM-candidate in the cell handover command). In step S2903, the UE may determine whether the configuration completion is included in the LTM-candidate. If the configuration completion is included in the LTM-candidate, the UE may proceed to step S2904. If the configuration completion is not included in the LTM-candidate, the UE may proceed to step S2905.

[0132] In step S2904, the UE may consider the complete candidate configuration as the CC associated with the indicated candidate cell. The UE may apply the CC as the current UE configuration. In step S2905, the UE may determine whether the only-HR indicator is included in the LTM-candidate. If the only-HR is included in the LTM-candidate, the UE may proceed to step S2906. If the only-HR is not included in the LTM-candidate, the UE may proceed to step S2907.

[0133] In step S2906, the UE may consider only the HR as the current configuration. In step S2907, the UE may combine the HR and the CR associated with the CR-ID to generate the current configuration. In step S2908, the UE may apply the candidate configuration (CC) of the corresponding indicated candidate cell. That is, the UE can generate a complete CC by combining the current configuration and the CC. In step S2909, the UE may obtain the complete candidate configuration from step S2904 or step S2908.

[0134] In one embodiment, the CR-ID may be included in the LTM-candidate configuration. The UE may combine the HR and CR based on the indicated CR-ID to generate the current configuration (e.g., as shown in the figure). Figure 28 or Figure 29 (As shown).

[0135] In one embodiment, the CR-ID may be included in the cell handover command. The UE can perform a cell handover and obtain the complete candidate configuration after receiving the cell handover command. Figure 30Signaling diagram 3000 for cell handover is illustrated according to an embodiment of this disclosure. The serving cell can configure the HR, one or more CRs, or one or more CCs to the UE via LTM-configuration. The serving cell can transmit the CR-ID to the UE via a cell handover command. After receiving the cell handover command, the UE can generate a current configuration based on the HR and / or the CR associated with the CR-ID, and the UE can apply candidate configurations. For example, the UE can combine the current configuration with candidate configurations to obtain a complete candidate configuration. The UE can apply the complete candidate configuration to perform cell handover.

[0136] The source gNB may take into account the candidate configurations of each candidate cell to generate the HR. In one embodiment, the CR may be generated by each candidate gNB. In another embodiment, the CR may be generated by the source gNB.

[0137] Figure 31 Signaling diagram 3100 illustrating the generation of HR and RC lists according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs. Upon receiving the cell handover request, one or more candidate gNBs may generate a candidate configuration (CC) for each candidate cell. One or more candidate gNBs may confirm the transmission of the CC to the source gNB via the cell handover request. The source gNB may consider the CC of each candidate cell to generate an HR and may transmit the HR to one or more candidate gNBs. One or more candidate gNBs may determine one or more CRs and may generate a CC for each candidate gNB, wherein the CC may be an incremental configuration relative to the combination of the HR and the corresponding CR. One or more candidate gNBs may transmit one or more CRs and one or more CCs to the source gNB. The source gNB may generate a CR list based on the CRs, and the source gNB may configure a CR-ID for each CR in the CR list. The source gNB may transmit CR-ID information to one or more candidate gNBs. When a candidate gNB initiates a cell handover to a target cell (or candidate cell) with a corresponding CR-ID, the CR-ID can be included by the candidate gNB in ​​the cell handover command. The source gNB can transmit LTM-configuration with HR and CR lists to the UE.

[0138] Figure 32Signaling diagram 3200 illustrating the generation of HR and CR lists according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs. Upon receiving the cell handover request, one or more candidate gNBs may generate a candidate configuration (CC) for each candidate cell. One or more candidate gNBs may confirm the transmission of the CC to the source gNB via the cell handover request. The source gNB may consider the CC of each candidate cell to generate an HR. The source gNB may determine one or more CRs and may generate a CC for each candidate gNB. The source gNB may generate a CR list based on the CRs, and the source gNB may configure a CR-ID for each CR in the CR list. The source gNB may transmit CR-ID information to one or more candidate gNBs. When a candidate gNB initiates a cell handover to a target cell corresponding to the CR-ID, the CR-ID may be included by the candidate gNB in ​​the cell handover command. The source gNB may transmit an LTM-configuration with the HR and CR lists to the UE.

[0139] The source gNB may take into account the reference configuration of each candidate gNB to generate a HR. In one embodiment, the source gNB may generate one or more CRs based on the HR. In another embodiment, one or more candidate gNBs may generate one or more CRs based on the HR.

[0140] Figure 33 Signaling diagram 3300 illustrating the generation of HR and CR lists according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs. Upon receiving the cell handover request, one or more candidate gNBs may determine one or more RCs and may generate one or more CCs based on the RC of each candidate cell. One or more candidate gNBs may confirm the transmission of RCs and CCs to the source gNB via the cell handover request. The source gNB may consider the RC of each candidate cell to generate an HR and may generate one or more CRs based on the HR. The source gNB may generate a CR list based on the CRs, and the source gNB may configure a CR-ID for each CR in the CR list. The source gNB may transmit CR-ID information to one or more candidate gNBs. When a candidate gNB initiates a cell handover to a target cell corresponding to the CR-ID, the CR-ID may be included by the candidate gNB in ​​the cell handover command. The source gNB may transmit an LTM-configuration with the HR and CR lists to the UE.

[0141] Figure 34Signaling diagram 3400 illustrating the generation of HR and CR lists according to an embodiment of this disclosure. A source gNB may transmit a cell handover request to one or more candidate gNBs. Upon receiving the cell handover request, one or more candidate gNBs may determine one or more RCs and may generate one or more CCs based on the RC of each candidate cell. One or more candidate gNBs may confirm the transmission of RCs and CCs to the source gNB via the cell handover request. The source gNB may consider the RCs of each candidate cell to generate an HR and may transmit HR information to one or more candidate gNBs. One or more candidate gNBs may generate one or more CRs based on the HR and may transmit CR information to the source gNB, wherein the CR information may include CRs generated by one or more candidate gNBs. Upon receiving the CR information, the source gNB may generate a CR list based on the CR information, and the source gNB may configure a CR-ID for each CR in the CR list. The source gNB may transmit CR-ID information to one or more candidate gNBs. When a candidate gNB initiates a cell handover to a target cell corresponding to the CR-ID, the CR-ID may be included by the candidate gNB in ​​the cell handover command. The source gNB can transmit LTM-configuration with HR and CR lists to the UE.

[0142] In one embodiment, the source gNB may consider only the candidate configurations of each candidate cell belonging to the source gNB to generate a HR. One or more candidate gNBs may generate one or more CRs based on the HR.

[0143] Figure 35 Signaling diagram 3500 illustrating the generation of HR and CR lists according to one embodiment of this disclosure. After generating one or more CCs, the source gNB may generate an HR based on the CC of each candidate cell. The source gNB may only consider the candidate configurations of each candidate cell belonging to the source gNB to generate an HR. The source gNB may transmit a cell handover request to one or more candidate gNBs, wherein the cell handover request may include an HR. Upon receiving a cell handover request, the candidate gNB may determine whether to generate a CR based on the HR.

[0144] If a candidate gNB (e.g., candidate gNB 1) determines to generate a CR, the candidate gNB may generate a CR and CC for its own CR based on the HR (or generate CR and CC for each candidate gNB). The candidate gNB may confirm the transmission of one or more CRs and one or more CCs to the source gNB via a cell handover request. If a candidate gNB (e.g., candidate gNB 2) determines not to generate a CR, the candidate gNB may generate only a CC for its own CR based on the HR (or generate CC only for each candidate cell). The candidate gNB may confirm the transmission of one or more LTM-candidates to the source gNB via a cell handover request, wherein one or more CCs may be included in each LTM-candidate. In response to receiving one or more CRs, the source gNB may generate a CR list, wherein the CR list may contain one or more CRs. The source gNB may configure a CR-ID for each CR in the LTM-candidate. The source gNB may configure CCs in the LTM-configuration. The source gNB may transmit the LTM-configuration with the HR and CR list to the UE.

[0145] To simplify UE behavior, another implementation scheme for HR and CR is the RC-ID inventory scheme. Using this scheme, the UE does not need to distinguish between HR and CR. The UE can generate a complete configuration using a reference configuration based on the RC-ID inventory. Figure 36 A schematic diagram 3600 illustrating an LTM configuration is provided according to an embodiment of this disclosure. The LTM configuration may include a reference list and a candidate list. The reference list may contain one or more LTM references, and each LTM reference may contain an RC or an RC-ID. A list of RC-IDs containing multiple RC-IDs in LTM candidates or cell handover commands can be used to represent multiple combined RCs.

[0146] In one embodiment, the RC-ID list may be included in the LTM-candidate. In another embodiment, the RC-ID list may be included in the cell handover command. The embodiments provide flexible ways to combine reference configurations. For example, if the UE is not configured with an MRB, the UE may not combine reference configurations related to the MRB.

[0147] Figure 37 A flowchart illustrating the generation of a complete CC is described according to an embodiment of this disclosure. In step S3701, the UE may receive a cell handover command from the network. In step S3702, the UE may determine a candidate cell indicated by the cell handover command (or indicated by an LTM-candidate in the cell handover command). The LTM-candidate may contain a list of RC-IDs, and the RC-ID list may contain one or more RC-IDs. In step S3703, the UE may determine whether Configuration Complete is included in the LTM-candidate. If Configuration Complete is included in the LTM-candidate, the UE may proceed to step S3704. If Configuration Complete is not included in the LTM-candidate, the UE may proceed to step S3705.

[0148] In step S3704, the UE can consider the complete candidate configuration as a CC associated with the indicated candidate cell. The UE can generate a complete CC using only the CC. In step S3705, the UE can consider one or more RCs associated with RC-IDs in the RC list (i.e., the RC-ID list) as the current configuration. In step S3706, the UE can apply the candidate configuration (CC) corresponding to the indicated candidate cell. That is, the UE can generate a complete CC by combining the current configuration with the CC. In step S3707, the UE can obtain the complete candidate configuration from step S3704 or step S3706.

[0149] Figure 38 Signaling diagram 3800 for cell handover is illustrated according to an embodiment of this disclosure. The network can pre-configure one or more RCs to the UE via LTM-configuration. The network can transmit an RC-ID list to the UE via a cell handover command. After receiving the cell handover command, the UE can generate a current configuration using the RCs associated with the RC-ID list, and the UE can apply candidate configurations. For example, the UE can combine the current configuration (i.e., one or more RCs associated with the RC-ID list) with candidate configurations to obtain a complete candidate configuration. The UE can then perform cell handover using the complete candidate configuration.

[0150] In one embodiment, the complete configuration generated by the reference configuration architecture in this disclosure can be applied by the UE in response to a conditional triggering event related to mobility operation, wherein the conditional triggering event may include handover (HO), conditional handover (CHO), conditional lower-layer triggered mobility (C-LTM), or conditional policy-assisted configuration (CPAC).

[0151] One or more RCs and CCs can be included in the HO-config. Figure 39 A schematic diagram 3900 illustrating an embodiment of the present disclosure describes an HO-configuration. An HO-configuration may include a reference list and a target cellconfig list. The reference list may contain one or more HO references, and each HO reference may contain an RC or an RC-ID. The target cellconfig list may contain one or more target cell configurations, wherein each target cell configuration may contain a target cell ID, CC, configuration complete, or RC-ID.

[0152] Figure 40A complete CC flowchart is described according to an embodiment of this disclosure. In step S4001, the UE may receive a HO command from the network. In step S4002, the UE may determine the target cell indicated by the HO command (or indicated by the target cell configuration in the HO command). In step S4003, the UE may determine whether the configuration completion is included in the target cell configuration. If the configuration completion is included in the target cell configuration, the UE may execute step S4004. If the configuration completion is not included in the target cell configuration, the UE may execute step S4005.

[0153] In step S4004, the UE may consider the complete target cell configuration as a CC associated with the indicated target cell. The UE may generate the complete target cell configuration using only the CC. In step S4005, the UE may consider the complete target cell configuration as a combination of the CC associated with the indicated target cell and the RC associated with the RC-ID. The UE may generate the complete target cell configuration by combining the RC and the CC associated with the indicated target cell. In step S4006, the UE may apply the complete target cell configuration of the indicated target cell to perform a handover to the indicated target cell.

[0154] Figure 41 Signaling diagram 4100 for generating reference configurations is illustrated according to one embodiment of this disclosure. Multiple reference configurations may be generated by a source gNB and one or more target gNBs. In one embodiment, one or more target gNBs may generate M-RC and CC. In another embodiment, the source gNB may provide information to one or more target gNBs. One or more target gNBs may generate M-RC and CC based on the information. Alternatively, the RC used to perform HO may be generated by the UE, the source gNB, and one or more target gNBs.

[0155] Figure 42 Signaling diagram 4200 illustrating the generation of RCs and CCs is described according to an embodiment of this disclosure. A source gNB may transmit a HO request to one or more target gNBs. Upon receiving the HO request, one or more target gNBs may generate multiple RCs and candidate configurations (CCs) for each target cell. One or more target gNBs may confirm the transmission of RCs and CCs to the source gNB via the HO request. The source gNB may generate an RC list, which may contain RCs. The source gNB may transmit the RC list to one or more target gNBs, wherein one or more RC-IDs for one or more target gNBs may be included in the RC list. If a target gNB wants to instruct the UE to perform a HO to another target gNB, the target gNB may transmit a HO command with an RC-ID corresponding to the other target gNB to the UE. Alternatively, the source gNB may configure an RC-ID for each RC in the RC list. The source gNB may configure CCs in the HO configuration. The source gNB may transmit a HO command with the HO configuration carrying the RC list to the UE.

[0156] After receiving a HO command indicating the target gNB and its corresponding RC-ID from the source gNB, the UE can select an RC from the RC list based on the RC-ID, and the UE can generate a complete configuration corresponding to the target gNB based on the selected RC. The UE can then apply the complete configuration to execute the HO to the target gNB.

[0157] Figure 43 Signaling diagram 4300 illustrating the generation of RC and CC according to an embodiment of this disclosure. A source gNB may transmit a HO request to one or more target gNBs, wherein the HO request may include a source-RC (S-RC, i.e., a reference configuration determined by the source gNB). Upon receiving the HO request, a target gNB may determine whether to use the S-RC. If a target gNB (e.g., target gNB 1) determines to use the S-RC, the target gNB may generate a CC corresponding to itself based on the S-RC (or generate a CC for each target gNB), wherein the CC may be an incremental configuration relative to the S-RC. The target gNB may acknowledge transmitting an S-RC application indicator and one or more CCs to the source gNB via the HO request, wherein the S-RC application indicator may indicate that the S-RC has been used to generate the CC. If a target gNB (e.g., target gNB 2) determines not to use the S-RC, the target gNB may generate multiple reference configurations, and the target gNB may generate a CC corresponding to itself based on multiple RCs (or generate a CC for each target gNB), wherein the CC may be an incremental configuration relative to multiple RCs. The target gNB can request confirmation of the transmission of multiple RCs and one or more CCs to the source gNB via HO.

[0158] The source gNB can generate an RC list, which may contain multiple RCs. The source gNB can transmit the RC list to one or more target gNBs, where one or more RC-IDs for the one or more target gNBs may be included in the RC list. If a target gNB wants to instruct the UE to perform a HO to another target gNB, the target gNB can transmit a HO command with the corresponding RC-ID to the other target gNB to the UE. Alternatively, the source gNB can configure RC-IDs for each RC in the HO-target. The source gNB can configure CCs in the HO-configuration. The source gNB can transmit a HO command with the HO-configuration carrying the RC list and RC-IDs to the UE. After receiving the HO command indicating the target gNB and the corresponding RC-ID from the source gNB, the UE can select an RC from the RC list based on the RC-ID, and the UE can generate a complete configuration corresponding to the indicated target gNB based on the selected RC. The UE can then apply the complete configuration to perform the HO to the target gNB.

[0159] Figure 44A schematic diagram 4400 illustrating an embodiment of the present disclosure describes a HO-configuration. The HO-configuration may include a Home Reference (HR) and Sub-Reference (CR) list. The CR list may include one or more HO-CRs, where each HO-CR may include a CR-ID and a sub-reference configuration (CRC) corresponding to the CR-ID. The HR or CR may include RRC configurations, such as measurement configurations, mobility control, radio resource configurations (including RB, MAC master configuration, or physical channel configuration), or security configurations.

[0160] In one embodiment, if the configuration parameters are the same in every target cell (the configuration parameters are the same in N target cells, where N is a positive integer), the configuration parameters can be carried by the HR. If the configuration parameters are the same in a few target cells (the configuration parameters are the same in M ​​target cells, where M is a positive integer less than N), the configuration parameters can be carried by the CR. If the configuration parameters are different in every target cell, the configuration parameters can be carried by the CC for each target cell. The complete configuration can be generated by combining the HR, CR, and CC.

[0161] Figure 45 A flowchart illustrating the generation of a complete CC is described according to an embodiment of this disclosure. In step S4501, the UE may receive an HO command from the network. In step S4502, the UE may determine the target cell indicated by the HO command. In step S4503, the UE may determine whether the configuration completion is included in the target cell configuration of the HO command. If the configuration completion is included in the target cell configuration, the UE may execute step S4504. If the configuration completion is not included in the target cell configuration, the UE may execute step S4505.

[0162] In step S4504, the UE can consider the complete candidate configuration as a CC associated with the indicated target cell. The UE can generate a complete CC using only the CC. In step S4505, the UE can combine the HR and the CR associated with the CR-ID (e.g., the CR-ID corresponding to the indicated target cell) to generate the current configuration. In step S4506, the UE can apply the candidate configuration (CC) corresponding to the indicated target cell. That is, the UE can generate a complete CC by combining the current configuration with the CC. In step S4507, the UE can obtain the complete candidate configuration from step S4504 or step S4506.

[0163] Figure 46A flowchart illustrating the generation of a complete CC is described according to an embodiment of this disclosure. In step S4601, the UE may receive a HO command from the network. In step S4602, the UE may determine the target cell indicated by the HO command. In step S4603, the UE may determine whether the configuration completion is included in the target cell configuration of the HO command. If the configuration completion is included in the target cell configuration, the UE may execute step S4604. If the configuration completion is not included in the target cell configuration, the UE may execute step S4605.

[0164] In step S4604, the UE may consider the complete candidate configuration as a CC associated with the indicated target cell. The UE can generate a complete CC using only the CC. In step S4605, the UE may determine whether the only-HR indicator is included in the target cell configuration. If the only-HR is included in the target cell configuration, the UE may proceed to step S4606. If the only-HR is not included in the target cell configuration, the UE may proceed to step S4607.

[0165] In step S4606, the UE may consider only the HR as the current configuration. In step S4607, the UE may combine the HR and the CR associated with the CR-ID to generate the current configuration. In step S4608, the UE may apply the candidate configuration (CC) corresponding to the indicated target cell. That is, the UE can generate a complete CC by combining the current configuration with the CC. In step S4609, the UE may obtain the complete candidate configuration from step S4604 or step S4608.

[0166] One or more RCs and CCs can be included in the conditional-config of CHO, C-LTM, or CPAC. Figure 47 A schematic diagram 4700 illustrating condition-configuration is provided according to an embodiment of this disclosure. The condition-configuration may include a reference list and a candidate list. The reference list may include one or more condition references, and each condition reference may include an RC or an RC-ID. The candidate list may include one or more condition-candidates, wherein each condition-candidate may include a candidate ID (e.g., a candidate cell ID), CC, configuration complete, RC-ID, or execution condition.

[0167] Figure 48A flowchart illustrating the generation of a complete CC is described according to an embodiment of this disclosure. In step S4801, the UE may determine that one or more execution conditions associated with the target cell have been met. In step S4802, the UE may trigger a CHO, C-LTM, or CPAC to the target cell. In step S4803, the UE may determine whether configuration completion is included in the condition-candidates associated with the execution conditions. If configuration completion is included in the condition-candidates, the UE may execute step S4804. If configuration completion is not included in the condition-candidates, the UE may execute step S4805.

[0168] In step S4804, the UE may consider the complete target cell configuration as a CC associated with the indicated target cell. The UE can generate the complete target cell configuration using only the CC. In step S4805, the UE may consider the complete target cell configuration as a combination of the CC associated with the indicated target cell and the RC associated with the RC-ID. The UE can generate the complete target cell configuration by combining the RC and the CC associated with the indicated target cell. In step S4806, the UE may apply the complete target cell configuration of the indicated target cell to perform CHO, C-LTM, or CPAC to the target cell.

[0169] Figure 49 Signaling diagram 4900 illustrating the generation of reference configurations is described according to one embodiment of this disclosure. Multiple reference configurations may be generated by a source gNB and one or more candidate gNBs. In one embodiment, one or more candidate gNBs may generate multiple RCs and CCs. In one embodiment, the source gNB may provide information to one or more candidate gNBs. One or more candidate gNBs may generate multiple RCs and CCs based on the information. On the other hand, the RC used to perform CHO, C-LTM, or CPAC may be generated by the UE, the source gNB, or one or more candidate gNBs. In one embodiment, the RC-ID may be included in the conditional configuration.

[0170] Figure 50 Signaling diagram 5000 for triggering CHO, C-LTM, or CPAC is illustrated according to one embodiment of this disclosure. Multiple reference configurations may be generated by a source gNB and one or more candidate gNBs. After the multiple reference configurations are generated, the source gNB may generate an RC list, which may contain RCs. The source gNB may configure an RC-ID for each RC in the RC list. The source gNB may configure a CC into a conditional configuration. The source gNB may transmit the conditional configuration with the RC list to the UE. The UE or the source gNB may perform an execution condition evaluation and determine whether one or more execution conditions associated with the candidate cell have been met. If the execution conditions have been met, the UE may trigger a CHO, C-LTM, or CPAC to the candidate cell using the corresponding complete candidate configuration, which may be generated based on the conditional configuration with the RC list.

[0171] Figure 51 Signaling diagram 5100 illustrating the generation of RC and CC according to an embodiment of this disclosure. A source gNB may transmit a CHO, C-LTM, or CPAC request to one or more candidate gNBs. Upon receiving the request, one or more candidate gNBs may generate multiple RCs and candidate configurations (CCs) for each candidate cell. One or more candidate gNBs may transmit RCs and CCs to the source gNB via a CHO, C-LTM, or CPAC request confirmation. The source gNB may generate an RC list, which may contain RCs. The source gNB may configure an RC-ID for each RC in the condition-configured condition-candidates. The source gNB may transmit the RC list to one or more candidate gNBs, wherein one or more RC-IDs for one or more candidate gNBs may be included in the RC list. If a candidate gNB wants to instruct the UE to perform a CHO, C-LTM, or CPAC to the target gNB, the candidate gNB may transmit the CHO, C-LTM, or CPAC command along with the corresponding candidate gNB's RC-ID to the UE. On the other hand, the source gNB can configure CC into the conditional candidate, and the source gNB can transmit the conditional configuration with the RC list to the UE.

[0172] The UE or the source gNB can perform an execution condition assessment and determine whether one or more execution conditions associated with the candidate cell have been met. If the execution conditions have been met, the UE can trigger a CHO, C-LTM, or CPAC for the candidate cell using the corresponding full candidate configuration, which can be generated based on a condition-configuration with an RC list.

[0173] In one embodiment, the source gNB can provide information to one or more candidate gNBs. The one or more candidate gNBs can generate RC and CC based on the information.

[0174] Figure 52Signaling diagram 5200 illustrating the generation of RC and CC according to an embodiment of this disclosure. A source gNB may transmit a CHO, C-LTM, or CPAC request to one or more candidate gNBs, wherein the CHO, C-LTM, or CPAC request may include a source-RC (S-RC, i.e., a reference configuration determined by the source gNB). Upon receiving a CHO, C-LTM, or CPAC request, a candidate gNB may determine whether to use the S-RC. If a candidate gNB (e.g., candidate gNB 1) determines to use the S-RC, the candidate gNB may generate a CC corresponding to itself based on the S-RC (or generate a CC for each candidate gNB), wherein the CC may be an incremental configuration relative to the S-RC. The candidate gNB may acknowledge transmitting an S-RC application indicator and one or more CCs to the source gNB via a CHO, C-LTM, or CPAC request, wherein the S-RC application indicator may indicate that the S-RC has been used to generate CCs. If a candidate gNB (e.g., candidate gNB 2) determines that it will not use S-RC, the candidate gNB may generate multiple reference configurations, and the candidate gNB may generate a CC corresponding to itself based on multiple RCs (or generate a CC for each candidate gNB), where the CC may be an incremental configuration relative to multiple RCs. The candidate gNB may request confirmation of transmitting multiple RCs and one or more CCs to the source gNB via CHO, C-LTM, or CPAC.

[0175] The source gNB can generate an RC list, which may contain S-RCs or multiple RCs. The source gNB can transmit the RC list to one or more candidate gNBs, where one or more RC-IDs for the candidate gNBs may be included in the RC list. If a candidate gNB wants to instruct the UE to perform a CHO, C-LTM, or CPAC to another candidate gNB, the candidate gNB can transmit a CHO, C-LTM, or CPAC command with the corresponding RC-ID of the other candidate gNB to the UE. Alternatively, the source gNB can configure an RC-ID for each RC in the conditional candidates. The source gNB can configure CCs in the conditional configuration, and the source gNB can transmit the conditional configuration with the RC list to the UE.

[0176] The UE or the source gNB can perform an execution condition assessment and determine whether one or more execution conditions associated with the candidate cell have been met. If the execution conditions have been met, the UE can trigger a CHO, C-LTM, or CPAC for the candidate cell using the corresponding full candidate configuration, which can be generated based on a condition-configuration with an RC list.

[0177] Figure 53A schematic diagram 5300 illustrating a condition-configuration is provided according to an embodiment of this disclosure. The condition-configuration may include a primary reference (HR) and a list of sub-references (CRs). The CR list may include one or more condition-CRs (con-CRs), where each condition-CR may include a CR-ID and a corresponding sub-reference configuration (CRC). The HR or CR may include RRC configurations, such as measurement configurations, mobility control, radio resource configurations (including RB, MAC primary configuration, or physical channel configuration), or security configurations.

[0178] In one embodiment, if the configuration parameters are identical across all candidate cells (the configuration parameters are identical across N candidate cells, where N is a positive integer), the configuration parameters can be carried by the HR. If the configuration parameters are identical across a small number of candidate cells (the configuration parameters are identical across M candidate cells, where M is a positive integer less than N), the configuration parameters can be carried by the CR. If the configuration parameters are different across all candidate cells, the configuration parameters can be carried by the CC of each candidate cell. The complete configuration can be generated by combining the HR, CR, and CC.

[0179] Figure 54 A schematic diagram 5400 illustrating the configuration architecture is provided according to an embodiment of this disclosure. Assume that candidate cells 1-6 are to be configured with MO and MRB as shown in Table 5410. That is, the complete configuration of candidate cell 1 includes MO A, MO B, MO C, MO D, MRB A, MRB B, and MRB C. The complete configuration of candidate cell 2 includes MO A, MO B, MO C, MO E, MRB A, MRB B, and MRB C. The complete configuration of candidate cell 3 includes MO F, MO G, MO H, MO I, MRB A, MRB B, and MRB D. The complete configuration of candidate cell 4 includes MO F, MO G, MO H, MO I, MRB A, MRB B, and MRB D. The complete configuration of candidate cell 5 includes MO J, MO K, MO L, MRB A, MRB B, and MRB E. The complete configuration of candidate cell 6 includes MO J, MO K, MO L, MO M, MRB A, MRB B, and MRB E.

[0180] Table 5410 can be divided into HR, one or more CRs, and CC for each candidate cell. Specifically, since MRB A and MRBB are required for all candidate cells, MRB A and MRB B can be allocated in the HR configuration, and MRB A and MRB B can be removed from Table 5410. Since MO A, MO B, MO C, and MRB C are required for candidate cell 1 and candidate cell 2, MO A, MO B, MO C, and MRB C can be allocated in the CRs (i.e., CR 1) for the corresponding candidate cell 1 and candidate cell 2. Since MO F, MO G, MO H, MO I, and MRB D are required for candidate cell 3 and candidate cell 4, MO F, MO G, MO H, MO I, and MRB D can be allocated in the CRs (i.e., CR 2) for the corresponding candidate cell 3 and candidate cell 4. Since MO J, MO K, MO L, and MRB E are required by candidate cells 5 and 6, they can be allocated in the corresponding CRs (i.e., CR3) of candidate cells 5 and 6. Since MO D, MO E, and MO M are only required by candidate cells 1, 2, and 6, respectively, they can be allocated in the corresponding CCs of candidate cells 1, 2, and 6, respectively.

[0181] Figure 55 A flowchart for generating a complete CC is described according to an embodiment of this disclosure. In step S5501, the UE may determine that one or more execution conditions associated with the candidate cell have been met. In step S5502, the UE may trigger a CHO, C-LTM, or CPAC to the candidate cell. In step S5503, the UE may determine whether configuration completion is included in the condition-candidate of condition-configuration. If configuration completion is included in the condition-candidate, the UE may execute step S5504. If configuration completion is not included in the condition-candidate, the UE may execute step S5505.

[0182] In step S5504, the UE may consider the complete candidate configuration as a CC associated with the indicated candidate cell. The UE may generate a complete CC using only the CC. In step S5505, the UE may combine the HR and the CR associated with the CR-ID (e.g., the CR-ID corresponding to the indicated candidate cell) to generate the current configuration. In step S5506, the UE may apply the candidate configuration (CC) corresponding to the indicated candidate cell. That is, the UE can generate a complete CC by combining the current configuration with the CC. In step S5507, the UE may obtain the complete candidate configuration from either step S5504 or step S5506.

[0183] Figure 56A flowchart for generating a complete CC is described according to an embodiment of this disclosure. In step S5601, the UE may determine that one or more execution conditions associated with the candidate cell have been met. In step S5602, the UE may trigger a CHO, C-LTM, or CPAC to the candidate cell. In step S5603, the UE may determine whether configuration completion is included in the condition-candidate of condition-configuration. If configuration completion is included in the condition-candidate, the UE may execute step S5604. If configuration completion is not included in the condition-candidate, the UE may execute step S5605.

[0184] In step S5604, the UE may consider the complete candidate configuration as a CC associated with the indicated candidate cell. The UE may generate a complete CC using only the CC. In step S5605, the UE may determine whether the only-HR indicator is included in the conditional candidate. If the only-HR is included in the conditional candidate, the UE may proceed to step S5606. If the only-HR is not included in the conditional candidate, the UE may proceed to step S5607.

[0185] In step S5606, the UE may consider only the HR as the current configuration. In step S5607, the UE may combine the HR and the CR associated with the CR-ID to generate the current configuration. In step S5608, the UE may apply the candidate configuration (CC) of the corresponding indicated candidate cell. That is, the UE can generate a complete CC by combining the current configuration with the CC. In step S5609, the UE may obtain the complete candidate configuration from step S5604 or step S5608.

[0186] Figure 57 A flowchart illustrating a mobility management method according to an embodiment of this disclosure is provided, wherein the method may be implemented by a wireless communication device such as a UE. In step S571, at least one reference configuration identifier and a candidate configuration are received. In step S572, a complete configuration is generated based on the at least one reference configuration identifier and the candidate configuration. In step S573, the complete configuration is applied to perform a cell handover to a candidate network node corresponding to the candidate configuration.

[0187] Figure 58 A flowchart illustrating a mobility management method according to an embodiment of this disclosure is provided, wherein the method may be implemented by a wireless communication device such as a network node. In step S581, a reference configuration is generated. In step S582, the reference configuration is transmitted to a candidate network node. In step S583, a candidate configuration and an indicator are received from the candidate network node. In step S584, a mobility configuration message is generated based on the reference configuration, the candidate configuration, and the indicator. In step S585, the mobility configuration message is transmitted to a user equipment (UE).

[0188] Figure 59A flowchart illustrating a mobility management method according to an embodiment of this disclosure is provided, wherein the method may be implemented by a network system. In step S591, a reference configuration is generated by a source network node of the network system. In step S592, a candidate configuration is generated by a candidate network node of the network system, wherein the candidate configuration is transmitted from the candidate network node to the source network node. In step S593, the reference configuration and the candidate configuration are transmitted by the source network node to the user equipment (UE) of the network system.

[0189] Figure 60 A schematic diagram of a communication device 6000 is illustrated according to an embodiment of this disclosure, wherein the communication device 6000 is implementable. Figures 1-59 The methods described herein, along with exemplary embodiments and alternative variations thereof, are described. Communication device 6000 may include processor 6100, storage medium 6200, and transceiver 6300. Processor 6100 is coupled to storage medium 6200 and transceiver 6300.

[0190] The processor 6100 can be implemented using programmable units such as microprocessors, microcontrollers, digital signal processors (DSPs), and field-programmable gate arrays (FPGAs). The functionality of the processor 6100 can also be implemented using discrete electronic devices or ICs. It should be noted that the functionality of the processor 6100 can be implemented in hardware or software.

[0191] Storage medium 6200 may be, for example, any type of fixed or removable random access memory (RAM), read-only memory (ROM), flash memory, hard disk drive (HDD), solid state drive (SSD), or similar element, or a combination thereof, configured to record multiple modules or various applications that can be executed by processor 6100.

[0192] Transceiver 6300 can be configured to transmit and receive signals separately in radio frequency. Transceiver 6300 can also perform operations such as low-noise amplification, impedance matching, frequency mixing, up- or down-frequency conversion, filtering, and amplification. Transceiver 6300 may include one or more digital-to-analog (D / A) converters or analog-to-digital (A / D) converters configured to convert from analog signal format to digital signal format during up-chain signal processing and from digital signal format to analog signal format during down-chain signal processing. Transceiver 6300 may include an antenna array containing one or more antennas for transmitting and receiving omnidirectional or directional antenna beams.

[0193] This disclosure provides a method for improving the efficiency of inter-CU LTM signaling in a network system. Multiple reference configurations can be introduced into the network system. For example, a UE can configure multiple reference configurations. One or more measurement targets shared by multiple cells can be included in the reference configuration. After the UE receives an indication (e.g., an identifier of the reference configuration), the UE can select a reference configuration based on the indication and combine the reference configuration with other information to generate a complete configuration for performing cell handover to a candidate network node.

[0194] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for mobility management of user equipment, characterized in that, include: Receive at least one reference configuration identifier and a candidate configuration; A complete configuration is generated based on the at least one reference configuration identifier and the candidate configuration; as well as The complete configuration is applied to perform cell handover to a candidate network node corresponding to the candidate configuration.

2. The method of claim 1, wherein the candidate configuration includes an incremental configuration relative to the at least one reference configuration identifier.

3. The method according to claim 2, further comprising: Obtain the reference configuration corresponding to the at least one reference configuration identifier; The reference configuration is regarded as the current user equipment configuration; as well as Apply the incremental configuration to obtain the complete configuration.

4. The method of claim 1, wherein the complete configuration includes at least one of the following: measurement configuration, mobility control information, radio resource control (RRC) configuration, packet data convergence protocol (PDCP) configuration, radio link control (RLC) configuration, media access control (MAC) configuration, physical layer (PHY) configuration, or security configuration.

5. The method of claim 1, wherein the at least one reference configuration identifier is received via a mobility configuration message.

6. The method of claim 1, wherein the at least one reference configuration identifier is received via a cell handover command corresponding to the candidate network node.

7. The method of claim 1, wherein the at least one reference configuration identifier corresponds to a primary reference configuration associated with a plurality of candidate network nodes of the user equipment and a candidate reference configuration associated with a portion of the plurality of candidate network nodes, wherein the complete configuration is generated by combining the primary reference configuration, the candidate reference configuration, and the candidate configuration.

8. The method of claim 1, further comprising: A reference configuration identifier corresponding to the candidate network node is selected from the at least one reference configuration identifier, wherein the complete configuration is generated based on the reference configuration identifier and the candidate configuration.

9. The method of claim 8, further comprising: Receive the configuration and determine whether the parameters are included in the configuration; as well as In response to the parameter being included in the configuration, the complete configuration is generated based on the reference configuration identifier and the candidate configuration.

10. The method of claim 9, wherein the configuration includes the at least one reference configuration identifier and the candidate configuration.

11. The method of claim 1, wherein the complete configuration is applied by the UE in response to a condition-triggered event related to mobility operation, wherein the condition-triggered event includes at least one of the following: Conditional Handover (CHO), Conditional Low-Level Triggered Mobility (C-LTM), or Conditional Policy Assisted Configuration (CPAC).

12. The method of claim 1, wherein the step of generating the complete configuration based on the at least one reference configuration identifier and the candidate configuration comprises: Obtain a reference configuration corresponding to the at least one reference configuration identifier, wherein the reference configuration is pre-configured to the UE; as well as The reference configuration and the candidate configuration are combined to produce the complete configuration.

13. The method of claim 1, wherein the at least one reference configuration identifier and the candidate configuration are received via a low-level trigger configuration.

14. The method of claim 1, wherein the at least one reference configuration identifier and the candidate configuration are received via a handover configuration.

15. A method for mobility management applicable to source network nodes, characterized in that, include: Generate a reference configuration; Transmit the reference configuration to the candidate network nodes; Receive candidate configurations and indicators from the candidate network nodes; A mobility configuration message is generated based on the reference configuration, the candidate configuration, and the indicator; as well as The mobility configuration message is transmitted to the user equipment (UE).

16. The method of claim 15, wherein the candidate configuration includes an incremental configuration relative to the reference configuration.

17. A method for mobility management in a network system, characterized in that, include: The reference configuration is generated by the source network node of the network system; Candidate configurations are generated by candidate network nodes in the network system, wherein the candidate configurations are transmitted from the candidate network nodes to the source network node; as well as The reference configuration and the candidate configuration are transmitted from the source network node to the user equipment (UE) of the network system.

18. The method of claim 17, further comprising: The UE combines the reference configuration and the candidate configuration to generate a complete configuration; as well as The UE applies the complete configuration to perform cell handover to the candidate network node.

19. The method of claim 17, wherein the candidate configuration is generated by the candidate network node based on the reference configuration.

20. The method of claim 17, wherein the candidate configuration includes an incremental configuration relative to the reference configuration.

Images