Cell handover management method, communication apparatus, storage medium, and program product

Abstract

Provided are a cell handover management method, a communication apparatus, a storage medium, and a program product. The cell handover management method is applied to a first node, and the method comprises: determining at least one first cell, and sending first information to a second node where each first cell among the at least one first cell is located. Each first cell is one of the candidate cells for a subsequent conditional primary secondary cell addition or change (SCPAC) configuration or a low-layer triggered mobility (LTM) configuration of a user equipment (UE). The first information is used to instruct the second node to update the SCPAC configuration or the LTM configuration related to the UE, or the first information is used to provide a reference for the second node to determine an LTM target cell to be accessed by the UE during a subsequent handover.

Description

Cell handover management methods, communication devices, storage media and software products

[0001] This disclosure claims priority to Chinese patent application No. 202411062344.5, filed on August 2, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to a cell handover management method, communication device, storage medium, and program product. Background Technology

[0003] In mobile communication networks, cell handover ensures that user equipment (UE) can smoothly transfer from the coverage area of ​​one base station (such as a cell) to the coverage area of ​​another base station during movement (i.e., cross-cell handover), or handover between different sectors of the same base station (i.e., intra-cell handover). Summary of the Invention

[0004] On one hand, this disclosure provides a cell handover management method applied to a first node. The cell handover management method includes: determining at least one first cell and sending first information to a second node where each of the at least one first cell is located. Each first cell is one of the candidate cells for subsequent conditional primary / secondary cell changes or additions to SCPAC configuration or lower-layer triggered mobility LTM configuration for a user equipment (UE). The first information is used to instruct the second node to update the SCPAC configuration or LTM configuration related to the UE, or the first information is used to provide a reference for the second node to determine the LTM target cell to which the UE will access for subsequent handover.

[0005] On the other hand, this disclosure provides a cell handover management method applied to a second node, which is the node where a first cell is located. The first cell is one of the candidate cells for subsequent conditional primary / secondary cell changes or additions to SCPAC configuration or lower-layer triggered mobility LTM configuration for a user equipment (UE). The cell handover management method includes: receiving first information sent by the first node, the first information being used to instruct the second node to update the SCPAC configuration or LTM configuration related to the UE, or the first information being used to provide a reference for the second node to determine the LTM target cell to which the UE will access for subsequent handover.

[0006] In another aspect, embodiments of this disclosure provide a cell handover management device applied to a first node. The cell handover management device includes: a processing module and a transmitting module;

[0007] The processing module is used to determine at least one first cell; the sending module is used to send first information to the second node where each of the at least one first cell is located. Each first cell is one of the candidate cells for subsequent conditional primary / secondary cell changes or additions to SCPAC configuration or low-layer triggered mobility LTM configuration for the user equipment (UE). The first information is used to instruct the second node to update the SCPAC configuration or LTM configuration related to the UE, or the first information is used to provide a reference for the second node to determine the LTM target cell to which the UE will access for subsequent handover.

[0008] In another aspect, embodiments of this disclosure provide a cell handover management device applied to a second node, the second node being the node where the first cell is located, and the first cell being one of the candidate cells for subsequent conditional primary / secondary cell changes or additions to SCPAC configuration or low-layer triggered mobility LTM configuration for the user equipment (UE). The cell handover management device includes: a receiving module;

[0009] The receiving module is used to receive first information sent by the first node. The first information is used to instruct the second node to update the SCPAC configuration or LTM configuration related to the UE, or the first information is used to provide a reference for the second node to determine the LTM target cell to which the UE will access in subsequent handovers.

[0010] In another aspect, embodiments of this disclosure provide a communication device. The communication device includes: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; when the processor executes the computer program, it implements the cell handover management method described above.

[0011] In another aspect, embodiments of this disclosure provide a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the cell handover management method described above.

[0012] In another aspect, embodiments of this disclosure provide a computer program product including computer program instructions that, when executed, implement the cell handover management method described above. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in this disclosure, the accompanying drawings used in some embodiments of this disclosure will be briefly described below. Obviously, the drawings described below are merely drawings of some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings.

[0014] Figure 1 is a schematic diagram of a communication system according to some embodiments.

[0015] Figure 2 is a flowchart illustrating a cell handover management method according to some embodiments.

[0016] Figure 3 is a schematic diagram of a cell handover management method according to some embodiments.

[0017] Figure 4 is a schematic diagram of another cell handover management method according to some embodiments.

[0018] Figure 5 is a schematic diagram of another cell handover management method according to some embodiments.

[0019] Figure 6 is a schematic diagram of another cell handover management method according to some embodiments.

[0020] Figure 7 is a schematic diagram of another cell handover management method according to some embodiments.

[0021] Figure 8 is a flowchart illustrating another cell handover management method according to some embodiments.

[0022] Figure 9 is a flowchart illustrating another cell handover management method according to some embodiments.

[0023] Figure 10 is a structural schematic diagram of a cell handover management device according to some embodiments.

[0024] Figure 11 is a structural schematic diagram of another cell handover management device according to some embodiments.

[0025] Figure 12 is a structural schematic diagram of another cell handover management device according to some embodiments. Detailed Implementation

[0026] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0027] It should be noted that in this disclosure, expressions such as "exemplarily" or "for example" are used to indicate that they are examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of expressions such as "exemplarily" or "for example" is intended to present the relevant concepts in a detailed manner.

[0028] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0029] In the description of this disclosure, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can mean: only A, A and B, and only B. Furthermore, "at least one" means one or more, and "more than one" means two or more.

[0030] Currently, within the 3rd generation partnership project (3GPP), 5G technology supports subsequent (continuous) cell changes or cell handovers for UEs. In 3GPP standard release 17 (Rel-17), for the addition and changes of primary and secondary cells (PSCells) in dual connectivity, the conditional PSCell change / addition (CPAC) function was introduced, namely the conditional PSCell change (CPC) function and the conditional PSCell addition (CPA) function.

[0031] The network side (such as the radio access network (RAN)) pre-configures CPAC for the user equipment (UE). This configuration includes candidate PSCells that can be added or changed, such as their resource configurations and radio bearer (RB) configurations, as well as measurement-related execution conditions for each candidate PSCell. Specifically, it configures the UE's requirements for PSCell cell signal quality measurement. When the UE's measured PSCell cell signal quality meets these requirements, the execution conditions for adding or switching to that PSCell are considered met. Based on the CPAC configuration, the UE continuously evaluates the signal quality of each PSCell, assessing whether the execution conditions for each PSCell are met. If the execution conditions for a PSCell are met, the UE directly switches from the source PSCell to that PSCell, or adds a connection to that PSCell if there is no existing PSCell connection. This avoids the network side needing to evaluate the cell quality measurement results reported by the UE and initiate PSCell handover / addition. Instead, the UE directly performs PSCell handover / addition based on its own measurement results, without the need for network-side assistance, thus greatly reducing the latency of PSCell handover / addition.

[0032] However, in the existing Rel-17, once a UE configured with CPAC completes its connection to the target PSCell, the CPAC configuration no longer applies to the target PSCell, and the UE needs to release the CPAC configuration. Therefore, unless the network reconfigures a new subsequent CPAC candidate cell configuration for the UE, the UE can only trigger PSCell changes or additions by the network through reporting cell measurement quality during subsequent mobility. Both methods—reconfiguring a new subsequent CPAC for the UE by the network, and directly triggering PSCell changes or additions based on cell measurements reported by the UE—still increase the latency for UE handover / addition to PSCells.

[0033] Therefore, the Subsequent Conditional PSCell Addition or Change (SCPAC) function was introduced in 3GPP Release 18. SCPAC handover is mainly used for continuous conditional handover between PSCells by the UE. For example, the network side pre-configures SCPAC for the UE. The SCPAC configuration includes: configuring some candidate PSCells that can be added or changed based on the current connection status, including the relevant resource configuration and RB configuration of the candidate PSCells, as well as the measurement-related execution conditions for each PSCell; and configuring candidate PSCells for subsequent changes for each PSCell, including the relevant resource configuration and RB configuration of the subsequent candidate PSCells, as well as the measurement-related execution conditions for each subsequent candidate PSCell. Furthermore, after the UE completes the connection to the target PSCell, it does not need to release the SCPAC configuration. Instead, the UE evaluates the signal quality of each subsequent candidate PSCell according to the configuration of the candidate PSCells corresponding to the currently connected PSCell in the SCPAC configuration. That is, it evaluates whether the execution conditions for continuing to have a subsequent PSCell are met. If they are met, the UE directly continues to switch to the subsequent PSCell according to its own measurement results, without the need for network-side assisted handover.

[0034] In other words, SCPAC allows a UE to actively add or change the connected PSCell cell when it moves, provided that specific conditions of a pre-configured candidate PSCell cell are met. This eliminates the need for the network side to rely on UE measurement reports to determine whether to trigger the addition or change of a PSCell cell. Furthermore, regarding SCPAC, the UE will continuously store multiple candidate PSCell cells and their corresponding triggering conditions (unless the network instructs the UE to release the SCPAC configuration). This allows the UE to trigger the addition and change of PSCell cells multiple times during movement.

[0035] Furthermore, in all handover types in 3GPP Release 17 and earlier, serving cell changes are triggered by Layer 3 (L3) measurements and executed via Layer 3 radio resource control (RRC) signaling to change the primary cell (PCell) and primary / secondary cell (PSCell). However, all cases require reconfiguration of upper layers (such as RRC or packet data convergence protocol) and / or resetting of lower layers (e.g., medium access control (MAC) and / or physical layer (PHY)), resulting in longer latency, greater overhead, and longer downtime than beam-level movements. 3GPP Release 18 introduced Layer 1 (L1) / Layer 2 (L2) based mobility, also known as lower-layer triggered mobility (LTM), to enable serving cell changes via L1 / L2 signaling while maintaining upper-layer configurations and / or minimizing lower-layer configuration changes. This helps reduce latency, overhead, and downtime during handover. LTM supports DU movement within distributed units (DUs) and between centralized units (CUs). During LTM, the user plane continues as much as possible (e.g., within a distributed unit) without resetting, maintaining connectivity with the target cell to avoid data loss and additional data recovery delays. In subsequent LTM handovers (SLTM), the UE continuously stores multiple candidate LTM cells and their corresponding measurement configurations (unless instructed by the network to release the LTM configuration). This allows the UE to report measurement values ​​from candidate LTM cells multiple times during movement, triggering multiple handovers to the connected cell via L1 / L2 signaling from the network.

[0036] In other words, LTM handover is a new handover mechanism introduced by 3GPP in Release 18. Unlike traditional RRC layer handover, LTM handover is mainly triggered through the physical layer (L1) and data link layer (L2), reducing the dependence on RRC configuration. Since it does not require reconfiguration of upper-layer parameters, LTM handover can significantly reduce handover latency and downtime.

[0037] However, subsequent (continuous) cell handovers or algorithm changes, such as SCPAC or SLTM, can easily lead to ping-pong handovers.

[0038] Because the network configures multiple candidate target cells for the UE at once, and the UE retains these configurations and continuously switches between multiple cells during subsequent mobility, the UE will switch to a target cell as long as a predefined trigger condition is met, since the multiple candidate target cells are pre-configured. At this time, the target cell has no way of knowing whether ping-pong has occurred and has no means to terminate ping-pong handover. Therefore, in subsequent (continuous) cell handover or change algorithms, ping-pong is more likely to occur and lasts longer, consuming a large amount of network resources and severely negatively impacting user service quality. Therefore, for subsequent (continuous) cell handover or change algorithms, such as SCPAC or SLTM, it is necessary to address the ping-pong phenomenon that may occur during continuous handover.

[0039] In summary, how to avoid the ping-pong phenomenon during cell handover for UEs and improve the management efficiency of cell handover has become an urgent technical problem to be solved.

[0040] To address the aforementioned technical problems, this disclosure provides a cell handover management method. This method determines candidate cells for the UE's SCPAC or LTM configuration and instructs the communication node of each candidate cell to update the UE-related SCPAC or LTM configuration, or provides a reference for the communication node of each candidate cell to determine the LTM cell the UE will subsequently access during handover. By updating the access configuration of each candidate cell for the UE, the threshold for the UE to subsequently access a candidate cell is increased, reducing frequent cell handovers and preventing ping-pong issues during cell handover.

[0041] In this embodiment of the disclosure, the network architecture of a mobile communication network (including but not limited to 3G, 4G, 5G, and future mobile communication networks (such as the evolution of fifth-generation mobile communication technology (5G-A) and sixth-generation mobile communication technology (6G)) may include at least a first communication node and a second communication node. It should be understood that, in this example, in the downlink, the first communication node may be a terminal-side device (e.g., including but not limited to a terminal), and the second communication node may be a network-side device (e.g., including but not limited to a base station). Of course, in the uplink, the first communication node may also be a network-side device, and the second communication node may also be a terminal-side device. In device-to-device communication between the two communication nodes, both the first and second communication nodes can be a base station or a terminal. The first and second communication nodes may be referred to as the first node and the second node, respectively.

[0042] For example, as shown in FIG1, FIG1 is a schematic diagram of a communication system according to some embodiments. The communication system includes a first node 101 and a second node 102. There may be one or more second nodes 102, and the present disclosure does not limit the number of second nodes.

[0043] The first node 101 can determine multiple candidate cells configured by the UE (such as candidate cells configured by SCPAC or candidate cells configured by LTM), and send information to the second node 102 where each candidate cell is located to indicate the updating of the cell access configuration (such as SCPAC configuration or LTM configuration) related to the UE, or send information to the second node 102 to provide a reference for the second node 102 to determine the candidate cells to which the UE will access in subsequent handovers.

[0044] It should be noted that, when the candidate cell is a candidate cell configured by SCPAC, the first node 101 can be the master node (MN), and the second node can be the secondary node (SN). MN and SN are used to describe two roles or functions in the dual connectivity (DC) scenario. In the embodiments of this disclosure, MN and SN can be at least one of the following: terminal, base station, core network element, server, service function (SF) block, and application function block.

[0045] In some embodiments, when the candidate cell is a candidate cell configured in LTM, if the UE is performing a cell handover across base stations, the first node 101 can be the first base station (e.g., the source base station), and the second node can be the second base station (e.g., the candidate base station). If the UE is performing a cell handover within a base station, the first node 101 can be the CU, and the second node can be the DU.

[0046] A base station (BS) can be a base station in LTE, Long Term Evolution Advanced (LTEA) or an evolved Node B (eNB or eNodeB), a base station device (gNB) in a 5G network, or a base station in a future communication system. Base stations can include various macro base stations, micro base stations, home base stations, wireless remote devices, reconfigurable intelligent surfaces (RISs), routers, relays, transmission and reception points (TRPs), wireless fidelity (WIFI) devices, and other network-side equipment.

[0047] A terminal can be a device with wireless transceiver capabilities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and so on. This disclosure does not limit the application scenarios. Terminals may also be referred to as users, user equipment (UE), access terminals, UE units, UE stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, UE terminals, wireless communication devices, UE agents, or UE devices, etc., and this disclosure does not limit these terms.

[0048] Core network elements can include various network functions, such as access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), unified data management (UDM), and location management function (LMF).

[0049] It should be noted that Figure 1 is only an exemplary framework diagram. The number of devices included in Figure 1 and the names of each device are not limited. In addition to the devices shown in Figure 1, the communication system may also include other devices, such as core network devices.

[0050] This disclosure does not limit the application scenarios. The system architecture and business scenarios described in this disclosure are for the purpose of more clearly illustrating the technical solutions of this disclosure and do not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0051] Figure 2 is a flowchart illustrating a cell handover management method according to some embodiments. As shown in Figure 2, the cell handover management method is applied to a first node and includes steps S201 to S202.

[0052] S201, The first node determines at least one first cell.

[0053] The first cell is one of the candidate cells corresponding to the UE's cell access configuration. The cell access configuration can be SCPAC configuration or LTM configuration.

[0054] In other words, the first cell is one of the candidate cells for the UE's SCPAC configuration or LTM configuration.

[0055] It should be noted that, in this embodiment of the disclosure, the first cell may be a cell involved in the SCPAC ping-pong phenomenon, or the first cell may be a cell involved in the LTM ping-pong phenomenon.

[0056] In other words, the cells involved in the SCPAC ping-pong phenomenon are those where the UE experiences ping-pong when switching access between multiple candidate cells configured based on SCPAC. Similarly, the cells involved in the LTM ping-pong phenomenon are those where the UE experiences ping-pong when switching access between multiple candidate cells configured based on LTM.

[0057] For example, the candidate cells configured for SCPAC include: cell A, cell B, and cell C. The UE accesses cell A at 8:11:31 AM, then switches from cell A to cell B at 8:12:21 AM, then switches from cell B to cell C at 8:12:38 AM, and finally switches from cell C to cell B at 8:12:57 AM. The initial access duration of the UE to cell A is 50 seconds, the access duration of the UE to cell B after switching from cell A is 17 seconds, and the access duration of the UE to cell B after switching from cell B to cell C is 19 seconds. If the duration threshold for determining whether the ping-pong phenomenon occurs is 25 seconds, then both cell B and cell C are cells involved in the SCPAC ping-pong phenomenon (i.e., cells with short access durations or frequent access).

[0058] In some embodiments, the first cell may be the SCPAC target cell after the UE switches access, or the first cell may be the LTM target cell after the UE switches access.

[0059] In other words, the SCPAC target cell is the cell that the UE accesses at the current time from the multiple candidate cells configured by the SCPAC (i.e., the candidate cell that the UE last accessed at the current time from the SCPAC configuration). Similarly, the LTM target cell is the cell that the UE accesses at the current time from the multiple candidate cells configured by the LTM (i.e., the candidate cell that the UE last accessed at the current time from the LTM configuration).

[0060] In some embodiments, the node identities of the first node and the second node where the first cell is located are also different for the first cell under different cell access configurations.

[0061] As one implementation, if the first cell is a candidate cell configured by the UE's SCPAC, the first node can be MN and the second node can be SN.

[0062] In some embodiments, when the first cell is a candidate cell in the LTM configuration of the UE, the node identities of the first node and the second node where the first cell is located are different for different cell handover scenarios (or ranges).

[0063] In a scenario where the UE is performing cell handover across base stations, the first node can be the first base station, and the second node can be the second base station. The first base station is the source base station, and the second base station is the candidate base station.

[0064] In other words, the first base station is the base station of the cell that the UE historically accessed before the current time, and the second base station is the base station of the cell that the UE accesses at the current time (or will access after the current time).

[0065] In a scenario where the UE is performing cell handover within a base station, the first node can be a CU and the second node can be a DU.

[0066] S202, The first node sends the first information to the second node where each first cell is located.

[0067] The first information is used to instruct the second node to update the cell access configuration related to the UE, that is, the first information is used to instruct the second node to update the SCPAC configuration or LTM configuration related to the UE.

[0068] In some embodiments, during the handover process of a UE in multiple candidate cells configured based on LTM, the first information can be used to provide a reference for the second node to determine the LTM target cell to which the UE will subsequently handover.

[0069] It should be noted that, in this embodiment of the disclosure, the first information may include at least one of the following: the UE's historical access information, information indicating the occurrence of the ping-pong phenomenon, the identifier of the first cell, the status identifier of the transmission configuration indication of the first cell, and information indicating the deletion of the cell access configuration of the first cell.

[0070] In other words, the first piece of information can also instruct the second node to delete the cell access configuration associated with the UE. Thus, by deleting the access configuration for a candidate cell configured for the UE, the UE will no longer consider this candidate cell during subsequent cell handovers, thereby avoiding frequent access to this candidate cell by the UE during the entire cell handover process and preventing the ping-pong phenomenon during cell handovers.

[0071] The UE's historical access information may include at least one of the following: the connection duration of the historical access cell, the cell identifier of the historical access cell, and the UE's historical mobility information.

[0072] In some embodiments, the method by which the first information exchanged between the first node and the second node is carried is also different for the first cell under different cell access configurations.

[0073] When the first cell is the LTM target cell determined by the first node from the candidate cells based on the LTM configuration, the first information is carried by the LTM cell handover notification message.

[0074] If the first cell is a cell involved in SCPAC ping-pong phenomenon or the SCPAC target cell accessed after UE handover, the first information is carried by the SN modification request message, or the first information is carried by the SN reconfiguration completion message.

[0075] The following section uses SCPAC ping-pong handover and LTM ping-pong handover as examples, along with detailed examples, to introduce the cell handover management method provided in the embodiments of this disclosure.

[0076] 1. In the SCPAC handover in a dual-connectivity scenario, as shown in Figure 3, the UE, MN, and SN (including the source SN and the candidate SN) can use the following steps one through eight to make the MN request the SN to change the SCPAC configuration in order to avoid the ping-pong phenomenon during PSCell changes.

[0077] Step 1: The UE, MN, and source SN maintain dual connectivity.

[0078] The UE is configured with SCPAC configuration issued by the network side (i.e., the network side has configured SCPAC for the UE). SCPAC contains configurations for multiple candidate PSCells that may be used for subsequent handover.

[0079] Step 2: The UE detects that there is a candidate PSCell in the SCPAC configuration that meets the execution conditions, and the UE decides to use the candidate PSCell as the target PSCell for the change.

[0080] The UE can directly enable the relevant resource configurations and RB configurations for the candidate PSCell in the SCPAC configuration.

[0081] In some embodiments, the UE may perform step three after completing the reconfiguration of radio resources for the candidate PSCell.

[0082] Step 3: The UE sends an RRC reconfiguration complete message to the MN.

[0083] The RRC reconfiguration completion message can carry the target PSCell identifier to notify the MN that the connection configuration to the target PSCell has been completed.

[0084] Step 4: MN sends an SN RECONFIGURATION COMPLETE message to the candidate SN (i.e., the target SN) where the target PSCell is located.

[0085] The SN reconfiguration complete message may include the target PSCell identifier to indicate the target SN, and the UE has completed the reconfiguration of the target PSCell.

[0086] It should be noted that the subsequent steps for the UE to complete actual access and data transmission in the target PSCell can be referred to the relevant descriptions in some technologies, and will not be described here in this embodiment.

[0087] Step 5: MN determines whether a ping-pong PSCell exists.

[0088] The MN can determine whether a ping-pong PSCell exists based on the UE history information (UHI) generated by the MN side. The UHI contains the UE's connection to the PSCell cell change history (i.e., the connection duration of the historical access cell and the cell identifier of the historical access cell), including the connection duration of the PSCell cell, which can be used by the MN to determine whether a ping-pong PSCell change has occurred.

[0089] In some embodiments, if MN detects a ping-pong phenomenon with PSCell changes, step six can be performed.

[0090] Step 6: Based on the candidate PSCell cells involving ping-pong, MN sends an SN Modification Request message (S-NODE MODIFICATION REQUEST) to at least one candidate SN containing a candidate PSCell cell involving ping-pong.

[0091] At least one candidate SN containing a candidate PSCell cell involving ping-pong can be a source SN, a target SN, or another candidate SN containing a candidate PSCell cell involving ping-pong. The SN modification request message is used to notify the SN that the SCPAC configuration needs to be modified.

[0092] Furthermore, the SN modification request message contains the UE's UHI and / or information indicating ping-pong (used to explicitly indicate to the SN that ping-pong has occurred).

[0093] It should be noted that in this embodiment, the MN first determines whether ping-pong has occurred. If ping-pong has occurred, the MN sends the UHI to the SN. This can avoid the SN frequently receiving the UE's PSCell change history information and reduce the interface load.

[0094] In some embodiments, the source SN can receive an SN update request message. When the SN update request message contains the UE's UHI, the source SN can determine whether there is a ping-pong cell among the candidate PSCells configured on this SN based on the PSCell cell change history of the UE connected to in the UHI.

[0095] If a ping-pong cell exists, the source SN can update its SCPAC configuration. For example, the source SN can delete the ping-pong PSCell candidate cell, or it can reconfigure the execution conditions of the PSCell candidate cell without deleting it.

[0096] In some embodiments, if the MN detection speed is fast, the MN can perform ping-pong detection in step four. After detecting the ping-pong phenomenon of PSCell change, the MN sends an SN reconfiguration completion message to the source SN and carries the UE's UHI in the SN reconfiguration completion message. The source SN can determine whether there is a ping-pong phenomenon of PSCell change and whether to perform SCPAC reconfiguration in this step based on the PSCell cell change history of the UE connected in the UHI carried in the SN reconfiguration completion message.

[0097] In other words, having the MN handle the ping-pong detection eliminates steps five and six mentioned above. Furthermore, in this step, the source SN receives the SN reconfiguration complete message.

[0098] It should be noted that the source SN can execute step seven after completing the response to the SN update request message.

[0099] Step 7: The source SN sends an SN modification request acknowledgment (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message to the MN.

[0100] If the SCPAC configuration is updated, the SN update request response message may include the updated SCPAC configuration for this SN.

[0101] If the SCPAC reconfiguration of the SN is triggered based on the optional method described by the MN undertaking ping-pong detection, then in this step, after the SN reconfigures the SCPAC configuration, it actively triggers an update request of the SN and sends an SN update request response message to the MN. The SN update request response message contains the updated SCPAC configuration of this SN.

[0102] Step 8: MN updates the SCPAC configuration on both the network side and the UE side.

[0103] According to the existing procedure, if a SN updates its candidate PSCell cell list, the MN notifies all candidate SNs of the latest candidate PSCell cells on that SN, and all other candidate SNs update their respective SCPAC configurations. The MN then sends the corresponding SCPAC configuration to the UE based on the updated SCPAC configurations on all candidate SNs.

[0104] If the SN does not update the candidate PSCell cell list, but only updates the resource configuration or execution conditions of some candidate PSCell cells, the MN only needs to send the updated SCPAC configuration to the UE without notifying other SNs.

[0105] 2. In the SCPAC handover in a dual-connectivity scenario, as shown in Figure 4, the UE, MN, and SN (including the source SN and the candidate SN) can make the MN indicate the cancellation of the candidate PSCell involving ping-pong through the following steps one to seven.

[0106] Step 1: The UE, MN, and source SN maintain dual connectivity.

[0107] Step 2: The UE detects that there is a candidate PSCell in the SCPAC configuration that meets the execution conditions, and the UE decides to use the candidate PSCell as the target PSCell for the change.

[0108] In some embodiments, the UE may perform step three after completing the reconfiguration of radio resources for the candidate PSCell.

[0109] Step 3: The UE sends an RRC reconfiguration complete message to the MN.

[0110] Step 4: MN sends an SN reconfiguration complete message to the candidate SN where the target PSCell is located.

[0111] Step 5: MN determines whether a ping-pong PSCell exists.

[0112] In some embodiments, if MN detects a ping-pong phenomenon with PSCell changes, step six can be performed.

[0113] Step 6: Based on the candidate PSCell cells involving ping-pong, MN sends an SN update request message or a conditional PSCell change cancellation message to at least one candidate SN containing a candidate PSCell cell involving ping-pong.

[0114] The SN update request message or conditional PSCell change cancellation message is used to notify the SN to delete the pinged PSCell. The SN update request message or conditional PSCell change cancellation message contains at least one candidate PSCell cell identifier on the SN that needs to be cancelled (deleted), and information indicating pinged (used to indicate to the SN that the reason for cancelling the candidate PSCell is that pinged has occurred).

[0115] In some embodiments, the SN may receive an SN update request message or a conditional PSCell change cancellation message. When the SN update request message or conditional PSCell change cancellation message contains at least one ping-pong candidate PSCell cell identifier on the SN that is indicated to be cancelled, the SN deletes the corresponding PSCell candidate cell and updates the SCPAC configuration, and records the ping-pong involved cell for optimizing the configuration of future candidate PSCell cells.

[0116] Step 7: MN updates the SCPAC configuration on both the network side and the UE side.

[0117] According to the existing procedure, the MN can notify other candidate SNs of the latest candidate PSCell cells on that SN, and all other candidate SNs will update their respective SCPAC configurations. Based on the updated SCPAC configurations on all candidate SNs, the MN sends the corresponding SCPAC configuration to the UE.

[0118] 3. In subsequent LTM handover in cross-base station scenarios, as shown in Figure 5, the UE, source base station, and candidate base station can use the following steps one to seven to enable the target base station (i.e., candidate base station) to make decisions on subsequent LTM handover based on the UE's historical information, thus avoiding ping-pong.

[0119] Step 1: The UE maintains a connection with one of the LTM cells of the source base station.

[0120] The UE is configured with LTM configuration issued by the network side (i.e., the network side has configured LTM configuration for the UE). The LTM contains the configuration of multiple candidate LTM cells that may be used for subsequent handover.

[0121] Step 2: The UE performs relevant quality measurements on at least one candidate LTM cell according to the LTM configuration.

[0122] Step 3: The UE sends a measurement report message to the source base station via Layer 1 signaling.

[0123] The measurement report message contains quality measurements of at least one candidate LTM cell, including the corresponding beam quality measurements.

[0124] Step 4: The source base station receives the measurement report and, based on the measurement report, decides and selects a candidate LTM cell that meets the conditions (such as best cell / beam quality conditions) as the target cell, and determines the target beam of the target cell.

[0125] If the source base station has previously received UHI from other base stations, or has previously received UE mobility history information (MHI) (i.e., the UE's historical mobility information) from the UE, the source base station can optimize the LTM handover cell decision based on the user's connected cell change history in the MHI or UHI information, thus avoiding ping-pong handover caused by the LTM handover cell decision.

[0126] It should be noted that, in this embodiment of the disclosure, the selected target LTM cell is located at other base stations (such as candidate base stations).

[0127] Step 5: The source base station sends a Layer 1 or Layer 2 cell handover command message to the UE.

[0128] The cell handover command message includes: the target LTM cell identifier and the target beam identifier (i.e., the transmission configuration indicator (TCI) status identifier, used to indicate a specific beam or transmission configuration). The cell handover command message is used to instruct the UE to directly enable the radio resource configuration of the candidate LTM cell in the LTM configuration, that is, to hand over to the target LTM cell and the corresponding target beam.

[0129] Step 6: The source base station sends an LTM cell handover notification message to the candidate base station.

[0130] The LTM cell handover notification message is used to indicate to a candidate base station that a UE will be handing over to the target LTM cell. The LTM cell handover notification message contains the target LTM cell identifier and the target beam TCI status identifier, as well as the UHI generated by the source base station and / or the MHI received from the UE.

[0131] It should be noted that both UHI and MHI contain the user's connection cell change history, and may also contain the connection beam change history, i.e., the TCI status identifier of the connection beam and the connection duration on that beam.

[0132] In some embodiments, the candidate base station may receive an LTM cell handover notification message, save UHI information and / or MHI information, and optimize the decision of the subsequent LTM cell handover based on the user's connection cell change history contained in the above information during subsequent UE movement, so as to avoid ping-pong handover caused by the decision of the subsequent LTM cell handover, or optimize the decision of the target beam for the subsequent LTM handover based on the connection beam change history contained in the information, so as to avoid ping-pong in beam handover.

[0133] In some embodiments, if the candidate base station is a CU / DU architecture base station, in this step, the CU of the candidate base station receives the LTM cell handover notification message sent by the source base station, and then the CU sends a CU-DU cell handover notification message to the target DU where the target LTM cell is located, indicating that a UE in the target DU will hand over to the target LTM cell. The CU-DU cell handover notification message includes the target LTM cell identifier and the target beam TCI status identifier, as well as UHI and / or MHI information received from the original base station. The UHI / MHI includes the user's connection cell change history, and may also include the connection beam change history, i.e., the TCI status identifier of the connection beam, and the connection duration on that beam. The target DU receives the message, saves the UHI and / or MHI information, and in subsequent UE movement, optimizes the subsequent LTM cell handover decision based on the user's connection cell change history contained in the above information, avoiding ping-pong handover caused by the subsequent LTM cell handover decision, or optimizes the target beam decision for subsequent LTM handover based on the connection beam change history contained in the above information, avoiding ping-pong handover.

[0134] It should be noted that in some embodiments, the candidate base station or target DU can also update the candidate LTM cell list based on UHI / MHI information, such as deleting some candidate LTM cells that have experienced ping-pong, or modifying the candidate beam information of some candidate cells, and triggering the LTM configuration update process.

[0135] Step 7: The UE completes access to the target LTM cell and releases the connection in the source LTM cell.

[0136] At the same time, candidate base stations can update the UHI recorded by this base station.

[0137] 4. When the base station is a CU / DU architecture base station and LTM handover occurs between different DUs within the same base station (i.e., inter-DU handover within the base station), as shown in Figure 6, the UE, source CU, source DU and candidate DU can use the following steps one to eight to enable the target DU (i.e. candidate DU) to make a decision on subsequent LTM handover based on the UE's historical information, thus avoiding ping-pong.

[0138] Step 1: The UE and the base station maintain a connection with the source DU.

[0139] The UE is configured with LTM configuration issued by the network side (i.e., the network side has configured LTM configuration for the UE). The LTM contains the configuration of multiple candidate LTM cells that may be used for subsequent handover.

[0140] Step 2: The UE performs relevant quality measurements on at least one candidate LTM cell according to the LTM configuration.

[0141] Step 3: The UE sends a measurement report message to the source base station via Layer 1 signaling.

[0142] The measurement report message contains quality measurements of at least one candidate LTM cell, including the corresponding beam quality measurements.

[0143] Step 4: The source DU receives the measurement report and, based on the measurement report, decides and selects a candidate LTM cell that meets the conditions (such as best cell / beam quality conditions) as the target cell, and determines the target beam of the target cell.

[0144] If the source DU has previously received a UHI from the CU or an MHI from the UE, the source DU can optimize the LTM handover cell decision based on the user's connected cell change history in the MHI or UHI information, thus avoiding ping-pong handover caused by the LTM handover cell decision.

[0145] It should be noted that, in this embodiment of the disclosure, the selected target LTM cell is located in other DUs (such as candidate DUs).

[0146] Step 5: The source DU sends a Layer 1 or Layer 2 cell handover command message to the UE.

[0147] The cell handover command message includes: the target LTM cell identifier and the target beam identifier (i.e., the transmission configuration indicator (TCI) status identifier, used to indicate a specific beam or transmission configuration). The cell handover command message is used to instruct the UE to directly enable the radio resource configuration of the candidate LTM cell in the LTM configuration, that is, to hand over to the target LTM cell and the corresponding target beam.

[0148] Step 6: The source DU sends a DU-CU cell handover notification message to the source CU.

[0149] The DU-CU cell handover notification message is used to indicate that a UE in the source CU will hand over to the target LTM cell. The DU-CU cell handover notification message contains the target LTM cell identifier and the target beam TCI status identifier.

[0150] Step 7: The source CU sends a CU-DU cell handover notification message to the candidate DU where the target LTM cell is located.

[0151] The CU-DU cell handover notification message is used to indicate that a UE in the candidate DU will hand over to the target LTM cell. The CU-DU cell handover notification message contains the target LTM cell identifier and the target beam TCI status identifier, as well as the UHI generated by the source CU and / or the MHI received from the UE.

[0152] It should be noted that both UHI and MHI contain the user's connection cell change history, and may also contain the connection beam change history, i.e., the TCI status identifier of the connection beam and the connection duration on that beam.

[0153] In some embodiments, the candidate DU may receive a CU-DU cell handover notification message, save UHI information and / or MHI information, and optimize the decision of the subsequent LTM handover cell based on the user's connection cell change history contained in the above information during subsequent UE movement, so as to avoid ping-pong handover caused by the decision of the subsequent LTM handover cell, or optimize the decision of the target beam for the subsequent LTM handover based on the connection beam change history contained in the information, so as to avoid ping-pong in beam handover.

[0154] It should be noted that in some embodiments, the candidate DU can also update the candidate LTM cell list based on UHI / MHI information, such as deleting some candidate LTM cells that have experienced ping-pong, or modifying the candidate beam information of some candidate cells, and sending the updated LTM configuration to the CU to trigger the LTM configuration update process.

[0155] Step 8: The UE completes access to the target LTM cell and releases the connection in the source LTM cell.

[0156] 4. When the base station is a CU / DU architecture base station and LTM handover occurs between different DUs within the same base station (i.e., inter-DU handover within the base station), as shown in Figure 7, the UE, CU, and DU can use the following steps one to four to make the CU instruct the DU to delete the LTM cell involving ping-pong.

[0157] Step 1: The UE maintains a connection with the base station (a CU / DU architecture base station) where a certain LTM cell is located.

[0158] The UE is configured with LTM configuration issued by the network side (i.e., the network side has configured LTM configuration for the UE). The LTM contains the configuration of multiple candidate LTM cells that may be used for subsequent handover.

[0159] Step 2: The base station where the LTM cell is located stores the UHI / MHI associated with the UE.

[0160] As in Examples 3 and 4 above, the base station can obtain the UHI / MHI associated with the UE.

[0161] In some embodiments, the CU of the base station can detect whether a ping-pong handover phenomenon (i.e., ping-pong phenomenon) occurs in an LTM-configured cell (i.e., a candidate cell configured by LTM) through UHI / MHI.

[0162] In some embodiments, if the CU detects a ping-pong phenomenon during LTM switching, the CU can execute step three.

[0163] Step 3: The CU sends a UE text modification request message to at least one candidate DU containing a candidate LTM cell that involves ping-pong.

[0164] The UE text update request message is used to notify the DU to delete the ping-pong LTM candidate cell. The UE text update request message contains at least one candidate LTM cell identifier on the DU that needs to be cancelled (deleted), and information indicating ping-pong (used to indicate to the DU that the reason for cancelling the candidate LTM cell is that ping-pong has occurred).

[0165] In some embodiments, the DU can receive a UE text update request message sent by the CU. When the UE text update request message contains at least one ping-pong candidate LTM cell identifier on the DU that is indicated to be canceled, the DU deletes the corresponding LTM candidate cell and records the ping-pong involved cell for optimizing the configuration of future candidate LTM cells.

[0166] Step 4: The DU sends a UE text update request response message (i.e., a UE context modification acknowledge message) to the CU.

[0167] It should be noted that in some embodiments, after the DU sends a UE text update request response message to the CU, the LTM configuration update process is triggered (i.e., reconfigure LTM configuration at RAN and UE).

[0168] This disclosure also provides a cell handover management method applied to a second node. The second node is the node where the first cell is located. As shown in Figure 8, the cell handover management method may include: S801.

[0169] S801, the second node receives the first information sent by the first node.

[0170] It should be noted that the descriptions of the first cell and the first information can be found in the above embodiments, and will not be repeated here.

[0171] The cell handover management method provided in this disclosure will be described below with reference to detailed embodiments. As shown in FIG9, the cell handover management method in this disclosure may include: S901 to S903.

[0172] S901, The first node determines at least one first cell.

[0173] It should be noted that the process of the first node determining at least one first cell can be referred to the description of the above embodiment S201, and will not be repeated here.

[0174] S902, the first node sends the first information to the second node where each first cell is located.

[0175] It should be noted that the process of the first node sending the first information to the second node where each first cell is located can be referred to the description of the above embodiment S202, and will not be repeated here.

[0176] S903, the second node receives the first information sent by the first node.

[0177] In summary, by identifying candidate cells for the UE's SCPAC or LTM configuration and instructing the communication nodes of each candidate cell to update the UE-related SCPAC or LTM configuration, or by providing a reference for each candidate cell's communication nodes to determine the LTM cell the UE will subsequently access during handover, the access configuration for the UE in each candidate cell is updated. This raises the threshold for the UE to re-access a candidate cell, reduces frequent cell handovers, and avoids the ping-pong phenomenon during cell handovers.

[0178] It is understood that, in order to achieve the above-mentioned functions, the cell handover management device includes the corresponding hardware structure and / or software modules for performing each function. Those skilled in the art should readily recognize that, based on the algorithm steps of the examples described in conjunction with the embodiments of this disclosure, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0179] This disclosure embodiment can divide the cell handover management device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one functional module. The integrated module can be implemented in hardware or software. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each function into a separate functional module.

[0180] Figure 10 is a schematic diagram of a cell handover management device according to some embodiments. The cell handover management device 1000 can be applied to a first node and execute the cell handover management method provided in the embodiments of methods S201-S202 described above. As shown in Figure 10, the cell handover management device 1000 includes: a processing module 1001 and a sending module 1002.

[0181] Processing module 1001 is used to determine at least one first cell. Sending module 1002 is used to send first information to a second node where each of the at least one first cell is located. Each first cell is one of the candidate cells for subsequent conditional primary / secondary cell changes or additions to SCPAC configuration or low-layer triggered mobility LTM configuration for the user equipment (UE). The first information is used to instruct the second node to update the SCPAC configuration or LTM configuration related to the UE, or to provide a reference for the second node to determine the LTM target cell to which the UE will access during subsequent handover.

[0182] In some embodiments, the first information includes at least one of the following: the UE's historical access information, information indicating the occurrence of ping-pong phenomenon, the identifier of the first cell, the status identifier of the transmission configuration indication of the first cell, and information indicating the deletion of the cell access configuration of the first cell.

[0183] In some embodiments, the UE's historical access information includes at least one of the following: connection duration of the historical access cell, cell identifier of the historical access cell, and historical movement information of the UE.

[0184] In some embodiments, the first cell is a cell involved in SCPAC ping-pong phenomenon, or the first cell is a cell involved in LTM ping-pong phenomenon.

[0185] In some embodiments, the first cell is the SCPAC target cell that the UE accesses after handover, or the first cell is the LTM target cell that the UE accesses after handover.

[0186] In some embodiments, when the first cell is a candidate cell configured by the UE's SCPAC, the first node is the primary node MN and the second node is the secondary node SN.

[0187] In some embodiments, when the first cell is a candidate cell in the LTM configuration of the UE, the first node is the first base station and the second node is the second base station.

[0188] In some embodiments, when the first cell is a candidate cell for the LTM configuration of the UE, the first node is the centralized unit (CU) of the first base station, and the second node is the distributed unit (DU) of the first base station.

[0189] In some embodiments, when the first cell is an LTM target cell determined by the first node from candidate cells based on LTM configuration, the first information is carried by the LTM cell handover notification message.

[0190] In some embodiments, when the first cell is a cell involved in SCPAC ping-pong or the SCPAC target cell accessed after UE handover, the first information is carried by the SN modification request message, or the first information is carried by the SN reconfiguration completion message.

[0191] Figure 11 is a schematic diagram of a cell handover management device according to some embodiments. The cell handover management device 1100 can be applied to a second node and execute the cell handover management method provided in the embodiment of method S801 described above. As shown in Figure 11, the cell handover management device 1100 includes: a receiving module 1101.

[0192] The receiving module 1101 is used to receive first information sent by the first node. The first information is used to instruct the second node to update the SCPAC configuration or LTM configuration related to the UE, or the first information is used to provide a reference for the second node to determine the LTM target cell to which the UE will access in subsequent handovers. The second node is the node where the first cell is located. The first cell is one of the candidate cells for subsequent conditional primary and secondary cell changes or additions to the SCPAC configuration or low-layer triggered mobility LTM configuration of the user equipment UE.

[0193] In some embodiments, the first information includes at least one of the following: the UE's historical access information, information indicating the occurrence of ping-pong phenomenon, the identifier of the first cell, the status identifier of the transmission configuration indication of the first cell, and information indicating the deletion of the cell access configuration of the first cell.

[0194] In some embodiments, the UE's historical access information includes at least one of the following: connection duration of the historical access cell, cell identifier of the historical access cell, and historical movement information of the UE.

[0195] In some embodiments, the first cell is a cell involved in SCPAC ping-pong phenomenon, or the first cell is a cell involved in LTM ping-pong phenomenon.

[0196] In some embodiments, the first cell is the SCPAC target cell that the UE accesses after handover, or the first cell is the LTM target cell that the UE accesses after handover.

[0197] In some embodiments, when the first cell is a candidate cell configured by the UE's SCPAC, the first node is the primary node MN and the second node is the secondary node SN.

[0198] In some embodiments, when the first cell is a candidate cell in the LTM configuration of the UE, the first node is the first base station and the second node is the second base station.

[0199] In some embodiments, when the first cell is a candidate cell for the LTM configuration of the UE, the first node is the centralized unit (CU) of the first base station, and the second node is the distributed unit (DU) of the first base station.

[0200] In some embodiments, when the first cell is an LTM target cell determined by the first node from candidate cells based on LTM configuration, the first information is carried by the LTM cell handover notification message.

[0201] In some embodiments, when the first cell is a cell involved in SCPAC ping-pong or the SCPAC target cell accessed after UE handover, the first information is carried by the SN modification request message, or the first information is carried by the SN reconfiguration completion message.

[0202] In implementing the functions of the integrated modules described above in hardware, this disclosure provides another possible structure for the cell handover management device involved in the above embodiments. As shown in FIG12, the cell handover management device 1200 includes: a processor 1202 and a bus 1204. In some embodiments, the cell handover management device may further include a memory 1201; in some embodiments, the cell handover management device may further include a communication interface 1203.

[0203] Processor 1202 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 1202 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. Processor 1202 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 1202 may also be a combination of functions implementing computing capabilities, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0204] The communication interface 1203 is used to connect with other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0205] The memory 1201 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0206] In one implementation, the memory 1201 can exist independently of the processor 1202. The memory 1201 can be connected to the processor 1202 via a bus 1204 and is used to store instructions or program code. When the processor 1202 calls and executes the instructions or program code stored in the memory 1201, it can implement the cell handover management method provided in this embodiment of the present disclosure.

[0207] In another implementation, the memory 1201 can also be integrated with the processor 1202.

[0208] Bus 1204 can be an extended industry standard architecture (EISA) bus, etc. Bus 1204 can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in Figure 12, but this does not mean that there is only one bus or one type of bus.

[0209] Some embodiments of this disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer program instructions that, when executed on a computer, cause the computer to perform the cell handover management method as described in any of the above embodiments.

[0210] Exemplary examples show that the aforementioned computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0211] This disclosure provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the cell handover management method described in any of the above embodiments.

[0212] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A cell handover management method, wherein, The method is performed by a first node, and the method comprises: determining at least one first cell, and sending first information to a second node in which each of the at least one first cell is located; wherein each of the first cell is one of candidate cells of a subsequent conditional primary and secondary cell change, SCPAC, configuration or low layer triggered mobility, LTM, configuration of a user equipment, UE, and the first information is used to instruct the second node to update the SCPAC configuration or the LTM configuration related to the UE, or the first information is used to provide a reference for the second node to determine a LTM target cell accessed by the UE after subsequent handover.

2. The method of claim 1, wherein, The first information comprises at least one of the following: historical access information of the UE, information indicating that a ping-pong phenomenon occurs, an identity of the first cell, a state identity of transmission configuration indication of the first cell, and information indicating to delete a cell access configuration of the first cell.

3. The method of claim 2, wherein, The historical access information of the UE comprises at least one of the following: a connection duration of a historically accessed cell, a cell identity of the historically accessed cell, and historical movement information of the UE.

4. The method of any one of claims 1-3, wherein, The first cell is a cell related to a ping-pong phenomenon.

5. The method of any one of claims 1-3, wherein, The first cell is a SCPAC target cell accessed by the UE after handover, or the first cell is a LTM target cell accessed by the UE after handover.

6. The method of claim 1, wherein, In a case where the first cell is a candidate cell of the SCPAC configuration of the UE, the first node is a master node, MN, and the second node is a secondary node, SN.

7. The method of claim 1, wherein, In a case where the first cell is a candidate cell of the LTM configuration of the UE, the first node is a first base station, and the second node is a second base station.

8. The method of claim 1, wherein, In a case where the first cell is a candidate cell of the LTM configuration of the UE, the first node is a centralized unit, CU, of the first base station, and the second node is a distributed unit, DU, of the first base station.

9. The method of claim 1, wherein, In a case where the first cell is a LTM target cell determined by the first node from the candidate cells based on the LTM configuration, the first information is carried by a LTM cell handover notification message.

10. The method of claim 1, wherein, In a case where the first cell is a cell related to a SCPAC ping-pong phenomenon or a SCPAC target cell accessed by the UE after handover, the first information is carried by a SN modification request message or a SN reconfiguration complete message.

11. A cell handover management method, wherein, The method is performed by a second node, the second node is a node in which a first cell is located, the first cell is one of candidate cells of a subsequent conditional primary and secondary cell change, SCPAC, configuration or low layer triggered mobility, LTM, configuration of a user equipment, UE, and the method comprises: receiving first information sent by a first node; wherein the first information is used to instruct the second node to update the SCPAC configuration or the LTM configuration related to the UE, or the first information is used to provide a reference for the second node to determine a LTM target cell accessed by the UE after subsequent handover.

12. The method of claim 11, wherein, The first information includes at least one of the following: historical access information of the UE, information indicating that a ping-pong phenomenon occurs, an identifier of the first cell, a state identifier of a transmission configuration indication of the first cell, and information indicating that a cell access configuration of the first cell is deleted.

13. The method of claim 12, wherein, The historical access information of the UE includes at least one of the following: a connection duration of a historically accessed cell, a cell identifier of a historically accessed cell, and historical movement information of the UE.

14. The method of any one of claims 11-13, wherein, The first cell is a cell related to a ping-pong phenomenon.

15. The method of any one of claims 11-13, wherein, The first cell is an SCPAC target cell accessed by the UE after a handover, or the first cell is an LTM target cell accessed by the UE after a handover.

16. The method of claim 11, wherein, In a case where the first cell is a candidate cell configured by the UE for SCPAC, the first node is a master node (MN) and the second node is a secondary node (SN).

17. The method of claim 11, wherein, In a case where the first cell is a candidate cell configured by the UE for LTM, the first node is a first base station and the second node is a second base station.

18. The method of claim 11, wherein, In a case where the first cell is a candidate cell configured by the UE for LTM, the first node is a centralized unit (CU) of the first base station and the second node is a distributed unit (DU) of the first base station.

19. The method of claim 11, wherein, In a case where the first cell is an LTM target cell determined by the first node from the candidate cells based on the LTM configuration, the first information is carried in an LTM cell handover notification message.

20. The method of claim 11, wherein, In a case where the first cell is a cell related to an SCPAC ping-pong phenomenon or an SCPAC target cell accessed by the UE after a handover, the first information is carried in an SN modification request message or an SN reconfiguration complete message.

21. A communications device comprising: a memory and a processor; the memory and the processor are coupled; the memory is configured to store instructions executable by the processor; the processor executes the instructions to perform the method according to any one of claims 1-20.

22. A computer readable storage medium, wherein, The computer readable storage medium stores computer instructions, when the computer instructions are executed on a computer, the computer executes the method according to any one of claims 1-20.

23. A computer program product, wherein, The computer program product includes computer program instructions, when the computer program instructions are executed, the method according to any one of claims 1-20 is implemented.

Images