Historical information used for subsequent CPAC processes

Abstract

Example embodiments of this disclosure relate to network nodes, methods, apparatus, and computer-readable media for historical information in subsequent CPAC processes. In this solution, the MN can determine the SCG UHI associated with at least one previous conditional CPAC phase in a subsequent CPAC process; and send the SCG UHI associated with at least one previous CPAC phase, or a UHI determined based on the SCG UHI associated with at least one previous CPAC phase, to the target SN of the current CPAC phase. With this solution, the SN of any CPAC phase in a subsequent CPAC process can obtain sufficient and accurate historical information.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to network nodes, methods, apparatus, and computer-readable media for the processing of historical information in subsequent Conditional Primary and Secondary Cell Group (SCG) Cell Addition or Change (CPAC) procedures. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] The User History Information (UHI) mechanism for traditional CPAC procedures has been defined in 3GPP Release 18 (R18), but it is not fully applicable to subsequent CPAC procedures. Therefore, further research is needed on a history information mechanism for subsequent CPAC procedures. Summary of the Invention

[0004] This disclosure relates to MNs, SNs, network nodes, methods, apparatuses, and computer-readable media for historical information in subsequent CPAC processes. With this solution, secondary nodes (SNs) at any CPAC stage in a subsequent CPAC process can obtain sufficient and accurate historical information.

[0005] In some implementations, a master node (MN) is provided. The MN includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the MN: determines the SCG UHI associated with at least one previous conditional CPAC stage in a subsequent CPAC process; and sends the SCG UHI associated with at least one previous CPAC stage, or the UHI determined based on the SCG UHI associated with at least one previous CPAC stage, to the target SN of the current CPAC stage in the subsequent CPAC process.

[0006] In some implementations, a SN is provided. The SN includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the SN: receives from the MN an SCG UHI associated with at least one previous CPAC stage in a subsequent CPAC process, or a UHI determined based on an SCG UHI associated with at least one previous CPAC stage, wherein the SN is the target SN of the current CPAC stage in the subsequent CPAC process; and performs one of the following: storing or updating a latest SCG UHI based on the received SCG UHI or the received UHI; or storing or updating a latest UHI based on the received SCG UHI or the received UHI.

[0007] In some implementations, an SN is provided. The SN includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the SN: receives from the MN a request or subscription for an SCG UHI associated with the SN, the SN being the source SN for the initial CPAC phase in a subsequent CPAC process; and sends the SCG UHI associated with the SN to the MN.

[0008] In some implementations, a network node is provided. The network node includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the network node: detects at least one ping-pong event during a subsequent CPAC process; and records the occurrence of at least one ping-pong event, wherein the subsequent CPAC process is a subsequent CPAC process initiated by an MN or an inter-SN subsequent CPAC process initiated by an SN, and the network node is an MN, or wherein the subsequent CPAC process is an intra-SN subsequent CPAC process initiated by an SN, and the network node is an SN.

[0009] In some implementations, a method is provided that is executed by the MN. The method includes: determining the SCG UHI associated with at least one previous conditional CPAC phase in a subsequent CPAC process; and sending the SCG UHI associated with at least one previous CPAC phase, or the UHI determined based on the SCG UHI associated with at least one previous CPAC phase, to the target SN of the current CPAC phase in the subsequent CPAC process.

[0010] In some implementations, a method is provided performed by the SN. The method includes: receiving from the MN an SCG UHI associated with at least one previous CPAC stage in a subsequent CPAC process, or a UHI determined based on an SCG UHI associated with at least one previous CPAC stage, wherein the SN is the target SN of the current CPAC stage in the subsequent CPAC process; and performing one of the following: storing or updating a latest SCG UHI based on the received SCG UHI or the received UHI; or storing or updating a latest UHI based on the received SCG UHI or the received UHI.

[0011] In some implementations, a method is provided that is executed by the SN. This method includes: receiving from the MN a request or subscription for an SCG UHI associated with the SN, the SN being the source SN for the initial CPAC phase in a subsequent CPAC process; and sending the SCG UHI associated with the SN to the MN.

[0012] In some implementations, a method is provided that is executed by a network node. The method includes: detecting at least one ping-pong event during a subsequent CPAC process; and recording the occurrence of at least one ping-pong event, wherein the subsequent CPAC process is a subsequent CPAC process initiated by an MN or an inter-SN subsequent CPAC process initiated by an SN, and the network node is an MN; or wherein the subsequent CPAC process is an intra-SN subsequent CPAC process initiated by an SN, and the network node is an SN.

[0013] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured such that the processor of the MN: determines an SCG UHI associated with at least one previous conditional CPAC stage in a subsequent CPAC process; and transmits the SCG UHI associated with at least one previous CPAC stage, or a UHI determined based on the SCG UHI associated with at least one previous CPAC stage, to a target SN in the current CPAC stage of the subsequent CPAC process.

[0014] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured such that the processor of the SN: receives from the MN an SCG UHI associated with at least one previous CPAC stage in a subsequent CPAC process, or a UHI determined based on an SCG UHI associated with at least one previous CPAC stage, wherein the SN is the target SN of the current CPAC stage in the subsequent CPAC process; and performs one of the following: storing or updating a latest SCG UHI based on the received SCG UHI or the received UHI; or storing or updating a latest UHI based on the received SCG UHI or the received UHI.

[0015] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured such that the processor of the SN: receives from the MN a request or subscription for an SCG UHI associated with the SN, the SN being the source SN in the initial CPAC phase of a subsequent CPAC process; and transmits the SCG UHI associated with the SN to the MN.

[0016] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured such that the processor of a network node: detects at least one ping-pong event during a subsequent CPAC process; and records the occurrence of at least one ping-pong event, wherein the subsequent CPAC process is a subsequent CPAC process initiated by an MN or an inter-SN subsequent CPAC process initiated by an SN, and the network node is an MN; or wherein the subsequent CPAC process is an intra-SN subsequent CPAC process initiated by an SN, and the network node is an SN.

[0017] The method described in this paper and some implementations of MN also include: determining the SCG UHI associated with at least one previous CPAC stage based on the stored SCG UHI.

[0018] The method described herein and some implementations of MN also include: receiving an SCG UHI associated with at least one previous CPAC stage from the target SN of a previous CPAC stage in a subsequent CPAC process.

[0019] The methods described herein and some implementations of MN also include sending a request or subscription to the target SN of a previous CPAC stage in a subsequent CPAC process for an SCG UHI associated with at least one previous CPAC stage.

[0020] The methods described in this paper and some implementations of MN also include: associating the MCG UHI with the SCG UHI associated with at least one previous CPAC stage to determine the UHI.

[0021] The methods described herein and some implementations of MN also include sending an SCG UHI associated with the source SN of the initial CPAC phase in the subsequent CPAC process, or a UHI determined based on the SCG UHI associated with the source SN of the initial CPAC phase, to the target SN of the initial CPAC phase in the subsequent CPAC process.

[0022] The methods described in this paper and some implementations of MN also include: associating the MCG UHI with the SCG UHI associated with the source SN in the initial CPAC phase to determine the UHI.

[0023] The methods described herein and some implementations of MN also include: sending a request or subscription to the source SN of the initial CPAC phase in a subsequent CPAC process for an SCG UHI associated with the source SN of the initial CPAC phase in a subsequent CPAC process; and receiving the SCG UHI associated with the source SN of the initial CPAC phase in a subsequent CPAC process from the source SN of the initial CPAC phase.

[0024] The method described in this paper and some implementations of MN also include: determining the time the UE stays in the target PSCell in a specific CPAC phase based on the time length between the time when MN receives the RRC reconfiguration completion message indicating the execution of a subsequent conditional PSCell change (CPC) after a specific CPAC and the time when MN receives the RRC reconfiguration completion message indicating the execution of a specific CPAC.

[0025] The methods described in this paper and some implementations of MN also include: providing SCG UHI or UHI from the central unit (CU) of MN to the distributed unit (DU) of MN.

[0026] In the methods described herein and some implementations of the SN, the SN is the target SN of a previous CPAC stage in a subsequent CPAC process, and also includes sending an SCG UHI associated with at least one previous CPAC stage to the MN.

[0027] In the methods described herein and some implementations of the SN, the SN is the target SN of a previous CPAC stage in a subsequent CPAC process, and also includes: receiving a request or subscription from the MN for an SCG UHI associated with at least one previous CPAC stage.

[0028] The method described in this paper and some implementations of SN also include: sending the latest SCG UHI to MN.

[0029] The methods described in this paper and some implementations of the SN also include: sending the latest SCG UHI to the MN when one of the following is executed: PSCell Add or Conditional PSCell Add (CPA) execution or PSCell Change or CPC execution.

[0030] The methods described in this paper and some implementations of the SN also include: receiving requests or subscriptions from the MN for the latest SCG UHI.

[0031] The methods described in this paper and some implementations of the SN also include: providing the received SCG UHI or UHI from the CU of the SN to the DU of the SN.

[0032] In the methods described herein and some implementations of the SN, the SN is the target SN of the initial CPAC phase in the subsequent CPAC process, and also includes: receiving from the MN an SCG UHI associated with the source SN of the initial CPAC phase in the subsequent CPAC process, or a UHI determined based on the SCG UHI associated with the source SN of the initial CPAC phase.

[0033] In the methods described in this paper and some implementations of the SN, the SN is the target SN of the initial CPAC phase in the subsequent CPAC process, and also includes: updating the time the UE remained in the source PSCell of the initial CPAC phase when the UE successfully accesses the target PSCell of the initial CPAC phase. In some implementations, this time is updated as: the time value received from the MN via the SN add request message plus the time from receiving the SN add request message from the MN to receiving the SN reconfiguration completion message from the MN.

[0034] In some implementations of the methods and network nodes described herein, the network node is an MN, and further includes: detecting at least one ping-pong event based on one of the following: a UHI or SCG UHI stored by the MN, a UHI or SCG UHI received from the UE, an SCG UHI received from the latest serving SN, or at least one RRC reconfiguration completion message from the UE, the at least one RRC reconfiguration completion message indicating the identifier of the selected conditional reconfiguration applied by the UE during the execution of CPA or CPC.

[0035] In some implementations of the methods and network nodes described in this paper, the network node is an MN, and further includes: sending an indication to an SN that at least one ping-pong event has occurred, wherein the SN is the latest serving SN in a subsequent CPAC process, the source SN of the initial CPAC phase, the target SN of the initial CPAC phase, the source SN of any subsequent CPC phase, or the target SN of any subsequent CPC phase.

[0036] In some implementations of the methods and network nodes described herein, the network node is an SN, and further includes: detecting at least one ping-pong event based on one of the following: a UHI or SCG UHI received from an MN, a UHI or SCG UHI received from a UE, an SCG UHI stored by the SN, or at least one RRC reconfiguration completion message received from a UE, which indicates the identifier of the selected conditional reconfiguration applied by the UE during the execution of a CPA or CPC.

[0037] Some implementations of the methods and network nodes described herein also include determining that at least one ping-pong event has occurred based on one of the following: the time duration between the time point when the UE enters the PSCell and the time point when the UE re-enters the PSCell is less than a first threshold; the time duration between receiving two RRC reconfiguration completion messages indicating the same identifier is less than a second threshold; or the UE enters the second PSCell from the first PSCell and returns to the first PSCell, wherein the time duration during which the UE remains in the second PSCell is less than a third threshold.

[0038] In some implementations of the methods, MN, and SN described herein, the request or subscription is sent during the preparation phase for the subsequent CPAC process, or after receiving a Radio Resource Control (RRC) reconfiguration completion message indicating the execution of the initial CPAC.

[0039] In some implementations of the methods, MN, and SN described in this paper, the SCG UHI, or UHI, associated with the source SN of the initial CPAC phase in the subsequent CPAC process includes: historical information related to the source PSCell of the initial CPAC phase.

[0040] In some implementations of the methods, MN, and SN described herein, the SCG UHI, or UHI, associated with at least one previous CPAC stage in the subsequent CPAC process includes: historical information related to the source PSCell of the initial CPAC stage, and historical information related to the target PSCell of each of the at least one previous CPAC stage preceding the current CPAC stage.

[0041] In some implementations of the methods, MN, and SN described herein, historical information related to the target PSCell of a specific CPAC phase in at least one previous CPAC phase includes: the identifier of the target PSCell of the specific CPAC phase, and the time the UE remained in the target PSCell of the specific CPAC phase.

[0042] In some implementations of the methods, MN, and SN described in this paper, historical information related to the source PSCell in the initial CPAC phase includes: the identifier of the source PSCell in the initial CPAC phase, and the time the UE remains in the source PSCell in the initial CPAC phase.

[0043] In some implementations of the methods, MN, and SN described herein, at least one previous CPAC phase includes an initial CPAC phase, and the current CPAC phase includes a first subsequent CPC phase.

[0044] In some implementations of the methods, MN, and SN described herein, at least one previous CPAC phase includes an initial CPAC phase and subsequent CPC phases from the first subsequent CPC phase to the (X-1)th subsequent CPC phase, and the current CPAC phase includes the Xth subsequent CPC phase, where X is an integer not less than 2.

[0045] In the methods described in this paper, and in some implementations of MN and SN, the initial CPAC phase includes either the initial CPA phase or the initial CPC phase. Attached Figure Description

[0046] Figure 1 Examples of wireless communication systems in which some embodiments of the present disclosure may be implemented are illustrated;

[0047] Figure 2A The illustration shows a schematic diagram of an example communication network in which some embodiments of the present disclosure may be implemented;

[0048] Figures 2B-2C The illustration shows a subsequent CPAC process between SNs initiated by an example MN according to some example embodiments of the present disclosure;

[0049] Figure 3 The diagram illustrates a signaling process for the initial CPAC phase in a subsequent CPAC process, according to some example embodiments of the present disclosure.

[0050] Figure 4 The diagram illustrates a signaling process for a subsequent CPC phase in a subsequent CPAC process according to some example embodiments of the present disclosure;

[0051] Figure 5The illustration depicts a process for recording SCG UHI by MN during a subsequent CPAC process, according to some example embodiments of the present disclosure;

[0052] Figure 6 Examples of devices suitable for implementing embodiments of the present disclosure are illustrated;

[0053] Figure 7 Examples of processors suitable for implementing some embodiments of the present disclosure are illustrated;

[0054] Figure 8 The diagram illustrates a flowchart of an example method implemented at MN according to various aspects of this disclosure;

[0055] Figure 9 The illustration shows a flowchart of an example method implemented at the target SN according to various aspects of this disclosure;

[0056] Figure 10 The diagram illustrates a flowchart of an example method implemented at the source SN according to various aspects of this disclosure; and

[0057] Figure 11 The illustration shows a flowchart of an example method implemented at a network node according to some embodiments of the present disclosure.

[0058] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0059] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0060] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the embodiments(s) described may include a particular feature, structure, or characteristic, but not every embodiment necessarily must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same(s) embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that in conjunction with other embodiments (whether explicitly described or not) such a feature, structure, or characteristic may affect such a feature, structure, or characteristic within the scope of their knowledge.

[0061] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that selection can be made from a number of functional alternatives used, and that these selections are not necessarily better, smaller, higher, or otherwise preferred than other selections.

[0062] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are also intended to include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing,” when used herein, specify the presence of said features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and variations thereof should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “A only” or “B only” or “both A and B.” Other explicit and implicit definitions may be included below.

[0063] Figure 1Examples of wireless communication systems 100 that may be implemented in some embodiments of this disclosure are illustrated. Wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network (CN) 106, and a packet data network 108. Wireless communication system 100 may support various radio access technologies. In some implementations, wireless communication system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an Advanced LTE (LTE-A) network. In some other implementations, wireless communication system 100 may be a 5G network, such as a New Radio (NR) network. In other implementations, wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. Wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0064] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. The network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RAN), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0065] Network entity 102 may provide a geographic coverage area 112 for which it may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0066] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0067] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 It is shown in the middle. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., CN 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network device). Alternatively or additionally, UE 104 can support communication with other network entities 102 or UE 104, which can act as relays in the wireless communication system 100.

[0068] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link (SL). For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0069] Network entity 102 may support communication with CN 106, or with another network entity 102, or both. For example, network entity 102 may interface with CN 106 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via CN 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0070] In some implementations, network entity 102 can be configured in a decomposed architecture that can utilize a protocol stack physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0071] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0072] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0073] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, while RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by a different one of CU, DU, or RU).

[0074] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can connect to one or more DUs via mid-range communication links (e.g., F1, F1c, F1-u), while the DUs can connect to one or more RUs via front-end communication links (e.g., open front-end (FH) interfaces). In some implementations, the mid-range or front-end communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, supported by corresponding network entities 102 communicating via such communication links.

[0075] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with CN 106.

[0076] CN 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session with CN 106 via network entity 102 (e.g., Protocol Data Unit (PDU) session, etc.). CN 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session can be one example of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0077] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0078] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0079] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0080] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technique. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital technique. It should be understood that for the first digital technique (e.g., quantity) associated with the first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0081] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0082] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15 kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30 kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ =2), which includes a 60 kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0083] Subsequent conditional PSCell addition or modification (subsequent CPAC) is defined as a conditional PSCell addition or modification process executed after a PSCell addition, PSCell modification, or SCG release. This process is based on a pre-configured subsequent CPAC configuration of (multiple) candidate PSCells without requiring CPC / CPA reconfiguration and re-initiation. The UE retains the configured subsequent CPAC configuration and evaluates the execution conditions of the candidate PSCells after the completion of the PSCell addition or PSCell modification. Intra-SN subsequent CPAC and inter-SN subsequent CPAC initiated by the MN or SN are supported.

[0084] The following principles apply to subsequent CPACs:

[0085] - For subsequent CPAC initiated by MN, MN first triggers candidate cell preparation for the subsequent CPAC process and generates execution conditions for CPA execution and initial CPC execution.

[0086] - For subsequent CPAC initiated by the SN, the source SN first triggers candidate cell preparation for the subsequent CPAC process and generates execution conditions for the initial CPC execution.

[0087] - For both MN and SN-initiated subsequent CPACs, when the candidate SN prepares (multiple) candidate SCG configurations for (multiple) candidate PSCells, the candidate SN generates the following execution conditions for the subsequent CPAC.

[0088] - Subsequent CPAC configurations include configurations for (multiple) candidate PSCells, execution conditions for both the initial CPAC execution and subsequent subsequent CPAC executions, and may include MCG configurations (which will be applied when the CPAC execution is triggered), reference configurations, and security update configurations.

[0089] - Subsequent CPAC configurations for CPC candidate PSCells between CPAs or (multiple) SNs are provided in MN format. Subsequent CPAC configurations for CPC candidate PSCells within (multiple) SNs are provided in either MN or SN format.

[0090] - For a UE, subsequent CPAC configurations for all CPC candidate PSCells (including inter-SN and / or intra-SN) are provided in the same format, i.e., MN format or SN format. If the configured CPC candidate PSCells include at least one inter-SN CPC candidate PSCell, the subsequent CPAC configurations may be provided in MN format only. If only intra-SN CPC candidate PSCells are configured, the subsequent CPAC configurations may be provided in either MN or SN format.

[0091] Each candidate PSCell configuration can be provided as an incremental configuration on top of a reference configuration, which is used to form the complete candidate cell configuration. Only one reference configuration is supported.

[0092] The MN generates the MCG portion of the reference configuration (if any), while the SN (source or candidate) generates the SCG portion of the reference configuration. The MN can request the SCG reference configuration from any of the involved SNs.

[0093] - If the network wishes to use the current service PSCell as a candidate PSCell for subsequent CPAC, the network explicitly configures the subsequent CPAC configuration for that PSCell.

[0094] - After a PCell change between MNs, the network always explicitly releases the subsequent CPAC configuration for the candidate PSCell.

[0095] - When the SCG is released, the UE releases the stored subsequent CPAC configuration in SN format.

[0096] - The candidate PSCell configuration used for CPA can be used for subsequent CPC execution, but the candidate PSCell has different execution conditions.

[0097] - The subsequent CPAC configuration that is retained after the SCG is released, with the subsequent CPAC configuration having (multiple) CPA execution conditions, can be used for subsequent CPA execution.

[0098] Figure 2A The illustration shows a schematic diagram of an example communication network 200 in which some embodiments of the present disclosure can be implemented. For example... Figure 2AAs shown, the communication network 200 may include MN 210, multiple SNs 220-1 to 220-N, and UE 230.

[0099] In this disclosure, it is assumed that UE 230 may undergo subsequent CPAC procedures, for example, due to the movement of UE 230. For example, UE 230 may be served by the first PSCell of the first SN, then transferred to the second PSCell of the second SN, then transferred to the third PSCell of the third SN, and so on. For ease of description, it is assumed that SN 220-1 is the source SN of the initial CPAC phase in the subsequent CPAC procedures.

[0100] It should be understood that Figure 2A The number of devices, their connections, and types shown are for illustrative purposes only and do not imply any limitation. This environment may include any suitable number of devices (such as SNs) suitable for implementing embodiments of this disclosure.

[0101] It should be understood that the subsequent CPAC process can be initiated by either MN or SN.

[0102] Figures 2B-2C The illustration shows a subsequent CPAC process between SNs initiated by an example MN according to some example embodiments of the present disclosure. Figure 2B The diagram illustrates preparation phase 201. Figure 2C The diagram illustrates the initial assessment and implementation phase, as well as the subsequent assessment and implementation phase 202. Figures 2B-2C The subsequent CPAC process between SNs initiated by MN can involve the following steps 1-28.

[0103] 1 / 2 / 3 / 4. The MN initiates a subsequent CPAC between SNs by requesting (multiple) candidate SNs to allocate resources for the UE through the SN addition process, indicating that the request is for a subsequent CPAC. The MN also provides candidate cells recommended by the MN for (multiple) candidate SNs via the latest measurement results for the selection and configuration of (multiple) SCG cells, provides a list of candidate PSCells proposed to (multiple) other candidate SNs, and provides an upper limit on the number of PSCells that can be prepared by the candidate SNs. Within the list of cells indicated by the measurement results indicated by the MN, the candidate SN determines the list of (multiple) PSCells to be prepared (considering the maximum number indicated by the MN), and for each prepared PSCell, the candidate SN determines other SCG SCells, and includes the NR in the SN addition request confirmation message with the (multiple) prepared PSCell IDs. RRCReconfigurationThe message provides the MN with the new corresponding SCG radio resource configuration. For each prepared PSCell, the candidate SN also determines the execution conditions for subsequent CPAC execution within the list of candidate PSCells proposed to (multiple) other candidate SNs. If data forwarding is required, the candidate SN provides the MN with a data forwarding address. The candidate SN can also propose data forwarding to the MN or (multiple) other candidate SNs for subsequent CPAC. The candidate SN includes an indication of full or incremental RRC configuration. The candidate SN can accept or reject each candidate cell listed in the measurement results indicated by the MN; that is, it cannot configure any alternative candidates.

[0104] The MN can select one of the candidate SNs (multiple candidate SNs) and request a reference configuration as part of the SN addition process. Once obtained, the MN provides the reference configuration to the other candidate SNs (multiple candidate SNs).

[0105] Note 1: If the UE is configured with SN-1 in dual connectivity operation, the MN will use the SN modification procedure initiated by the MN instead of the SN addition procedure to start subsequent CPAC operations.

[0106] Note 2: If the UE is configured with SN-1 in dual connectivity operation, the MN can trigger an SN modification process initiated by the MN (to the source SN) to retrieve the current SCG configuration or request a reference configuration for subsequent CPAC, and allow the provision of data forwarding related information prior to step 1.

[0107] Note 3: If applicable, the MN stores the data forwarding addresses and data forwarding proposals provided from all (multiple) candidate SNs.

[0108] 5. For SNs terminating bearers using MCG resources, the MN provides Xn-U DL TNL address information to (multiple) candidate SNs in the Xn-U address indication message.

[0109] 6 / 7. If the list of prepared PSCells received from (multiple) candidate SNs in steps 2 and 4 differs from the proposed list of PSCells, then MN initiates an SN modification process toward all (multiple) candidate SNs to notify them of the updated list of prepared PSCells in (multiple) other candidate SNs.

[0110] 8. MN sends to UE RRCReconfiguration The message, RRCReconfiguration The message includes subsequent CPAC configuration, that is, RRCReconfiguration Information list and associated execution conditions for subsequent CPACs, where each RRCReconfiguration The message contains the information received from one of the candidate SNs (multiple candidate SNs) in steps 2 and 4. RRCReconfiguration The message contains the SCG configuration and possible MCG configuration. Additionally, RRCReconfiguration The message may also include an updated MCG configuration, for example, for configuring the required conditional measurements.

[0111] 9. The UE application received in step 3 RRCReconfiguration The message stores subsequent CPAC configurations and uses... RRCReconfigurationComplete The UE responds to the MN with a message. If the UE cannot comply... RRCReconfiguration If the message includes a portion of the configuration, it will execute the reconfiguration failure process.

[0112] 11. The UE begins evaluating the execution conditions. If the execution conditions of a candidate PSCell are met, the UE applies the corresponding application to the selected candidate PSCell. RRCReconfiguration Message, and send MN RRCReconfigurationComplete The message, the MN RRCReconfigurationComplete The message includes information for the selected candidate PSCell. RRCReconfigurationComplete The message, and information that allows MN to identify the selected candidate PSCell's SN. If a new sk counter is selected, then RRCReconfigurationComplete The message may also include the sk counter value associated with the selected candidate PSCell.

[0113] 12. MN completes reconfiguration via SN message (including) RRCReconfigurationComplete (Information) Notify the SN of the selected candidate PSCell that the UE has successfully completed the reconfiguration process.

[0114] 13. The UE performs the orientation applied in step 12. RRCReconfiguration Synchronization of the PSCell indicated in the message. The UE sends the MN. RRCReconfigurationComplete The message and the order in which the random access procedure toward the SCG is executed are not defined. Successful completion of the RRC connection reconfiguration procedure does not require a successful RA procedure toward the SCG.

[0115] 14. If the PDCP termination point is changed to an SN for a bearer using RLC AM, and the RRC full configuration is not in use, the MN sends an SN state transition message.

[0116] 15. For SN termination bearers or QoS flows moving from MN, depending on the characteristics of the respective bearer or QoS flow, MN may take actions to minimize service disruptions due to the activation of MR-DC (data forwarding).

[0117] 16. If data forwarding is required, the MN may send an Xn-U address indication message to the selected candidate SN. The SN may decide, where applicable, to terminate the bearer for the SN, perform early data forwarding, and send an early state transition message to the source MN.

[0118] Note 4: A separate Xn-U address indication procedure can be initiated to provide a different forwarding address for the prepared subsequent CPAC. In this case, the MN and candidate SN implement the process to ensure that (if any) early state transition messages from the selected SN are forwarded to the correct other candidate SN.

[0119] 18. The UE begins evaluating the execution conditions. If the execution conditions of a candidate PSCell are met, the UE applies the corresponding application to the selected candidate PSCell. RRCReconfiguration Message, and send MN RRCReconfigurationComplete The message, the MN RRCReconfigurationComplete The message includes information for the selected candidate PSCell. RRCReconfigurationComplete The message, and information that allows MN to identify the selected candidate PSCell's SN. If a new sk counter is selected, then RRCReconfigurationComplete The message may also include the sk counter value associated with the selected candidate PSCell.

[0120] 19. MN reconfiguration completion message via SN (including) RRCReconfigurationComplete (Information) Notify the SN of the selected candidate PSCell that the UE has successfully completed the reconfiguration process.

[0121] 20. The UE performs the orientation applied in step 19. RRCReconfiguration Synchronization of the PSCell indicated in the message. The UE sends the MN. RRCReconfigurationComplete The message and the order in which the random access procedure toward the SCG is executed are not defined. Successful completion of the RRC connection reconfiguration procedure does not require a successful RA procedure toward the SCG.

[0122] 21 / 22 / 23. The MN triggers an SN modification procedure initiated by the MN to notify the last serving SN to stop providing user data to the UE, switch to the ready state, and, where applicable, allow the provision of a new data forwarding address. If applicable, the MN triggers an Xn-U address indication procedure to notify the last serving SN of the SN address of the selected candidate PSCell to begin final data forwarding.

[0123] 24 / 25. If the PDCP termination point is changed for a bearer using RLC AM, and the RRC fully configured is not in use, the SN sends an SN state transition message to the MN, which then sends the message to the SN of the selected candidate PSCell when necessary.

[0124] 26. If applicable, data forwarding from the last serving SN occurs. It can be initiated by the SN when the last serving receives the earlier data forwarding address in step 4a.

[0125] 27. If data forwarding is required, the MN may send an Xn-U address indication message to the selected candidate SN. The SN may decide, where applicable, to terminate the bearer for the SN, perform early data forwarding, and send an early state transition message to the source MN.

[0126] Note 5: A separate Xn-U address indication procedure can be initiated to provide a different forwarding address for the prepared subsequent CPAC. In this case, the MN and the selected SN implement the mechanism to ensure that (if any) early state transition messages from the selected SN are forwarded to the correct other candidate SNs.

[0127] although Figures 2B-2C This involves a subsequent CPAC procedure initiated by the MN, but in some other examples, the subsequent CPAC procedure can be initiated by the SN for inter-SN subsequent CPAC configuration and inter-SN CPC execution. This procedure is initiated with an SN change request and then follows the steps described above for a subsequent CPAC initiated by the MN.

[0128] This disclosure relates to UHI. As long as the UE remains in the MR-DC, the MN stores and associates UE historical information from the MN and (multiple) SNs, forwarding the UE historical information and optional UE historical information from the UE to its connecting SN. The SN then uses the obtained information for dual-connectivity operations. The SN is responsible for collecting SCG UE historical information and providing the collected information to the MN.

[0129] If the UE remains in a PSCell for a duration exceeding the maximum value of the Time Stay parameter, the SN can store the PSCell information along with consecutive entries using the same PSCell identifier. The total dwell time in that PSCell is the sum of the dwell times for all consecutive PSCells with the same identifier.

[0130] The SN shall provide the MN with the collected SCG UE historical information (if available) according to the following procedure:

[0131] - SN release, and the process of SN-initiated SN change.

[0132] - If requested by MN during this process, then the SN modification process initiated by MN.

[0133] - If subscribed during SN addition, then when PSCell changes, the SN will initiate an SN modification process.

[0134] When the target NG-RAN node receives an SCG UHI from the source NG-RAN node via a handover request message for CHO, the target NG-RAN node updates the time the UE has remained in the cell (i.e., the source PSCell) of the latest PSCell entry when the UE successfully accesses the candidate cell of the target NG-RAN node. The updated value of the time the UE has remained in the source PSCell is equal to the value received from the source NG-RAN node during the handover preparation period plus the time from receiving the handover request message from the source NG-RAN node to receiving the RRC reconfiguration complete message from the UE.

[0135] Currently, in Release 18, the UHI mechanism for legacy CPAC procedures is specified as follows: when the target SN receives the SCG UHI from the MN via an SN Add Request message for CPC, the target SN updates the time the UE has remained in the cell (i.e., the source PSCell) of the latest PSCell entry when the UE successfully accesses the target SN's candidate cell. The updated value of the time the UE has remained in the latest PSCell is equal to the value received from the MN via the SN Add Request message plus the time from receiving the SN Add Request message from the MN to receiving the SN reconfiguration completion message from the MN. The UHI mechanism for legacy CPAC procedures does not function correctly for subsequent CPAC procedures. For example, the target SN of a subsequent CPC or one of the other candidate SNs(s) of a subsequent CPC may not be able to obtain the latest, complete, and valid SCG UHI. Taking the target SN of the first subsequent CPC as an example, in the preparation phase of the subsequent CPAC process, the target SN of the first subsequent CPC only obtains the UHI associated with the source PSCell of the initial CPAC. However, in fact, before the first subsequent CPC phase, the initial CPAC is successfully completed, but the target SN of the first subsequent CPC cannot know the UHI associated with the target PSCell of the initial CPAC (i.e., the source PSCell of the first subsequent CPC).

[0136] Embodiments of this disclosure relate to subsequent CPAC processes, which may include at least one of the following: an initial CPAC phase, a first subsequent CPC phase, a second subsequent CPC phase, ..., a (X-1)th subsequent CPC phase, an Xth subsequent CPC phase, etc. For example, the initial CPAC phase may be an initial CPA phase or an initial CPC phase in a subsequent CPAC process.

[0137] In some implementations, for the initial CPAC phase of a subsequent CPAC process, the current UHI mechanism used in traditional CPAC procedures can be reused through some updates. When the target SN of the initial CPAC receives the SCG UHI from MN 210 via an SN Add Request message for subsequent CPAC procedures, the target SN of the initial CPAC updates the time that UE 230 has remained in the source PSCell of the initial CPAC when the UE successfully accesses the target PSCell of the initial CPAC. The updated value of the time the UE has remained in the source PSCell of the initial CPAC phase is equal to the value received from MN 210 via the SN Add Request message plus the time from receiving the SN Add Request message from MN 210 to receiving the SN reconfiguration completion from MN 210.

[0138] For example, MN 210 can send an SN Add Request message to the target SN in the initial CPAC phase of a subsequent CPAC process, and the SN Add Request message may include SCG UHI, such as historical information related to the source PSCell in the initial CPAC phase.

[0139] In some implementations, for the initial CPAC phase in the subsequent CPAC process, MN 210 can determine the SCG UHI based on the stored / recorded SCG UHI, and MN 210 can also send the SCG UHI to the target SN of the initial CPAC phase in the subsequent CPAC process.

[0140] For example, during the initial CPAC phase, an SN reconfiguration completion message is sent from MN 210 to the target SN of the initial CPAC phase (e.g., Figure 2C Step 12) may include SCG UHI, for example, historical information related to the source PSCell in the initial CPAC phase.

[0141] In some other implementations, MN 210 may send a request or subscription for a UHI to the source SN of the initial CPAC phase in a subsequent CPAC process, and then the source SN of the initial CPAC phase in a subsequent CPAC process may send an SCG UHI to MN 210. Furthermore, MN 210 may send the received SCG UHI to the target SN of the initial CPAC phase in a subsequent CPAC process; or MN 210 may store and associate the stored / recorded MCG UHI and the received SCG UHI to determine the UHI (such as associating the UHI), and send the UHI to the target SN of the initial CPAC phase in a subsequent CPAC process. In some examples, the target SN of the initial CPAC phase in a subsequent CPAC process may also store or update the latest SCG UHI or the latest UHI based on the received SCG UHI or the received UHI.

[0142] Figure 3 The diagram illustrates a signaling process 300 for the initial CPAC phase in a subsequent CPAC process, according to some example embodiments of this disclosure. (See reference...) Figure 2A Assuming the source SN (S-SN) of the initial CPAC phase in the subsequent CPAC process is SN 220-1, and the target SN (T-SN) of the initial CPAC phase in the subsequent CPAC process is SN 220-2. Process 300 involves UE 230, MN 210, S-SN 220-1 of the initial CPAC phase in the subsequent CPAC process, and T-SN 220-2 of the initial CPAC phase in the subsequent CPAC process (i.e., T-SN 1, for example, Figure 2B or Figure 2C SN-1 as described in [the text].

[0143] In some examples, during the preparation phase for a subsequent CPAC process, or after MN 210 receives an RRC reconfiguration complete message (at 310) indicating the triggering or execution of the initial CPAC, MN 210 may send a message to the source SN 220-1 of the initial CPAC to subscribe to the SCG UHI (e.g., the indication for subscribing to the SCG UHI is included in a new message sent from MN 210 to the source SN 220-1 of the initial CPAC). Figure 3 An example is given: after MN 210 receives an RRC reconfiguration complete message (at 310) indicating the triggering or execution of the initial CPAC, MN 210 may send (at 322) a message to the source SN 220-1 of the initial CPAC to subscribe to the SCG UHI (e.g., the indication for subscribing to the SCG UHI may be included in a message sent from MN 210 to the source SN 220-1 of the initial CPAC, which may be a newly defined message or an existing message). When the PSCell changes or the CPC execution is performed, the source SN 220-1 of the initial CPAC may send (at 330) the latest SCG UHI to MN 210 via a message (e.g., a new message or an existing message).

[0144] In some other examples, after MN 210 receives an RRC reconfiguration complete message (at 310) indicating the triggering or execution of the initial CPAC, MN 210 may request (at 324) an SCG UHI from the source SN 220-1 of the initial CPAC via a message (e.g., an indication for requesting the SCG UHI is included in a message sent from MN 210 to the source SN 220-1 of the initial CPAC, which may be a newly defined message or an existing message). Upon receiving the request message from MN 210, the source SN 220-1 of the initial CPAC may send (at 330) the latest SCG UHI to MN 210 via a message (e.g., a new message or an existing message).

[0145] Then, MN 210 can, for example, send the latest received SCG UHI (e.g., including the time UE 230 has been in the source PSCell of the initial CPAC) to the target SN 220-2 of the initial CPAC via an SN reconfiguration completion message (at 340), an SN state transition message (at 362), an Xn-U address indication message (at 364), or a newly introduced message. Alternatively, MN 210 stores and associates ( Figure 3 (Not shown) The MCG UHI recorded by MN 210 and the SCG UHI received from the source SN 220-1 of the initial CPAC, and MN 210 may send the associated UHI and optional UHI received from UE230 to the target SN 220-2 of the initial CPAC, for example via an SN reconfiguration completion message (at 340) or an SN state transition message (at 362) or an Xn-U address indication message (at 364) or a newly introduced message.

[0146] It is understandable that step 310 can correspond to Figure 2C Steps 11 and 340 in the above steps may correspond to updates made via SCG UHI received from UE 230, or associated UHI, or optional UHI. Figure 2C Steps 12 and 350 can correspond to Figure 2C Steps 13 and 362 in the text can correspond to Figure 2C Step 14, which involves updating via SCG UHI received from UE 230, or associated UHI, or optional UHI, and step 364, can correspond to updating via SCG UHI received from UE 230, or associated UHI, or optional UHI. Figure 2C Step 16.

[0147] It should be understood that the procedure 300 for the initial CPAC phase in subsequent CPAC processes is for illustrative purposes only and is not limited in any way. For example, it may include some additional steps, such as Figure 2C Step 15 in the process may omit one of steps 322 or 324. For example, the SCG UHI received from UE 230, or the associated UHI or optional UHI, may be included in only one of steps 340, 362 or 364.

[0148] In some examples, the SCG UHI or UHI (e.g., sent to the target SN of the initial CPAC phase in a subsequent CPAC process or received from the source SN of the initial CPAC phase in a subsequent CPAC process), or associated UHI or optional UHI received from the UE, may include historical information related to the source PSCell of the initial CPAC phase. For example, it may include the identifier (ID) of the source PSCell of the initial CPAC phase, and the time that the UE 230 remained in the source PSCell of the initial CPAC phase. For example, the ID of the source PSCell of the initial CPAC phase may include the Physical Cell Identifier (PCI) and carrier frequency information (e.g., Absolute Radio Frequency Channel Number (ARFCN)), and / or CGI information (e.g., PLMN identifier, cell identifier, and TrackingAreaCode). For example, the time that UE 230 remains in the source PSCell during the initial CPAC phase can be represented as "Time 1". "Time 1" can be updated by the target SN 220-2 during the initial CPAC phase. "Time 1" is equal to the value included in the SN Add Request message sent from MN 210 to the target SN 220-2 of the initial CPAC, plus the time from receiving the SN Add Request message to receiving the RRC reconfiguration completion message from MN 210 (e.g., ...). Figure 2C Step 12 in Figure 3 The time (step 340) in the initial CPAC phase indicates the triggering or execution of the RRC reconfiguration completion. For example, the time that UE 230 remains in the source PSCell during the initial CPAC phase can be represented as "Time 1". "Time 1" can be stored and recorded by MN 210. "Time 1" is equal to the value included in the SN Add Request message sent from MN 210 to the target SN 220-2 of the initial CPAC, plus the time from sending the SN Add Request message to receiving the RRC reconfiguration completion (e.g., step 340) from UE 230. Figure 2C The time of step 11) in the RRC reconfiguration completion indicates the triggering or execution of the initial CPAC.

[0149] In some other implementations, the subsequent CPAC process may also include one or more subsequent CPC phases, such as a first subsequent CPC phase, a second subsequent CPC phase, ..., a (X-1)th subsequent CPC phase, an Xth subsequent CPC phase, etc. For any subsequent CPC phase, MN 210 may determine the SCG UHI associated with at least one previous CPAC phase in the subsequent CPAC process, and MN 210 may also send the SCG UHI associated with at least one previous CPAC phase in the subsequent CPAC process, or a UHI determined based on the SCG UHI associated with at least one previous CPAC phase in the subsequent CPAC process, to the target SN of the subsequent CPC phase. In some examples, the target SN of the subsequent CPC phase in the subsequent CPAC process may also store or update the latest SCG UHI or the latest UHI based on the received SCG UHI or the received UHI.

[0150] In some example embodiments, MN 210 may send a request or subscription for SCG UHI to the target SN of a previous CPAC stage in a subsequent CPAC process. MN 210 may receive SCG UHI from the target SN of a previous CPAC stage in a subsequent CPAC process. Furthermore, MN 210 may send the received SCG UHI to the target SN of the current CPAC stage in a subsequent CPAC process; or MN 210 may store and associate MCG UHI and the received SCG UHI to generate (or determine) a UHI, and send the UHI to the target SN of the current CPAC stage in a subsequent CPAC process; or MN 210 may send an optional UHI received from the UE to the target SN of the current CPAC stage in a subsequent CPAC process. A previous CPAC stage in a subsequent CPAC process is a CPAC stage that occurs before or after the current CPAC stage in a subsequent CPAC process, and at least one previous CPAC stage in a subsequent CPAC process includes at least one CPAC stage that occurs before or after the current CPAC stage in a subsequent CPAC process.

[0151] In some example embodiments, MN 210 may send a request or subscription for SCG UHI to the target SN of the current CPAC stage in a subsequent CPAC process. MN 210 may receive SCG UHI from the target SN of the current CPAC stage in a subsequent CPAC process. Furthermore, MN 210 may send the received SCG UHI to the target SN of the next CPAC stage in a subsequent CPAC process; or MN 210 may store and associate MCG UHI and the received SCG UHI to generate (or determine) a UHI, and send the UHI to the target SN of the next CPAC stage in a subsequent CPAC process; or MN 210 may send an optional UHI received from the UE to the target SN of the next CPAC stage in a subsequent CPAC process. The current CPAC stage in a subsequent CPAC process is a CPAC stage that occurs before or after the next CPAC stage in a subsequent CPAC process, and at least one previous CPAC stage in the subsequent CPAC process includes at least one CPAC stage that occurred before or after the next CPAC stage in a subsequent CPAC process.

[0152] In some examples, for a first subsequent CPC phase, at least one previous CPAC phase in the subsequent CPAC process includes the initial CPAC phase in the subsequent CPAC process.

[0153] For example, for the first subsequent CPC phase: for example, modifying the request confirmation message via SN (e.g., Figure 2C Step 22) or SN state transition message (e.g., Figure 2C In step 24), or during the SN modification process initiated by the SN when the SCG UHI changes, MN 210 receives the SCG UHI from the target SN of the initial CPAC (e.g., including the time UE 230 remained in the source PSCell of the initial CPAC and the time UE 230 remained in the target PSCell of the initial CPAC). Then, for example via an SN state transition message (e.g., Figure 2C Step 25 in the process), or the Xn-U address indication message (e.g., Figure 2C In step 27), or via an SN reconfiguration completion message or a newly introduced message, MN 210 may send the received SCGUHI to the target SN of the first subsequent CPC. Alternatively, for example via an SN state transition message, or an Xn-U address indication message, or an SN reconfiguration completion message or a newly introduced message, MN 210 stores and associates the MCG UHI recorded by MN 210 with the SCGUHI received from the target SN of the initial CPAC, and MN 210 may send the associated UHI and optional UHI received from UE 230 to the target SN of the first subsequent CPC.

[0154] SCG UHI or UHI (e.g., sent to the target SN of the first subsequent CPC phase in the subsequent CPAC process or received from the target SN of the initial CPAC phase in the subsequent CPAC process), or associated UHI or optional UHI received from the UE, may include: historical information related to the source PSCell of the initial CPAC phase, and historical information related to the target PSCell of the initial CPAC phase (or historical information related to the source PSCell of the first subsequent CPC phase). For example, historical information related to the source PSCell of the initial CPAC phase may include: the ID of the source PSCell of the initial CPAC phase, and the time the UE 230 remained in the source PSCell of the initial CPAC phase. For example, historical information related to the target PSCell of the initial CPAC phase may include: the ID of the target PSCell of the initial CPAC phase, and the time the UE 230 remained in the target PSCell of the initial CPAC phase. For example, historical information related to the source PSCell of the first subsequent CPC phase may include: the ID of the source PSCell of the first subsequent CPC phase, and the time the UE 230 remained in the source PSCell of the first subsequent CPC phase. For example, the ID of a cell (e.g., the target PSCell in the initial CPAC phase or the source PSCell in the first subsequent CPC phase) may include PCI and carrier frequency information (e.g., ARFCN), and / or CGI information (e.g., PLMN identifier, cell identifier, and TrackingAreaCode). For example, an RRC reconfiguration completion message (e.g., Figure 2C Step 11) includes enabling MN 210 to identify the target PSCell selected by UE 230 during the initial CPAC phase. For example, if MN 210 re-encodes or stores the SCG UHI, the time UE 230 remains in the target PSCell during the initial CPAC phase, or the time UE 230 remains in the source PSCell during the first subsequent CPC phase, can be determined by: MN 210 receiving an RRC reconfiguration complete message indicating the execution of the initial CPAC (e.g., Figure 2C The time point of step 11) in the middle is when MN 210 receives the RRC reconfiguration completion message indicating the execution of the first subsequent CPC (e.g., Figure 2C The time between step 18) in the process. That is, the time UE230 stays in the target PSCell in the initial CPAC phase, or the time UE230 stays in the source PSCell in the first subsequent CPC phase, is equal to the time MN 210 receives the RRC reconfiguration complete message indicating the execution of the first subsequent CPC (e.g., Figure 2CIn step 18), the time point minus ("-") MN 210 receives an RRC reconfiguration complete message indicating the execution of the initial CPAC (e.g., Figure 2C The time point of step 11 in the process.

[0155] For example, in the second subsequent CPC phase: for example via an SN modification request confirmation message or an SN state transition message, or via an SN modification process initiated by the SN when the SCG UHI changes, MN 210 receives the SCG UHI from the target SN of the first subsequent CPC (e.g., including the time UE 230 spent in the source PSCell of the initial CPAC, the time spent in the target PSCell of the initial CPAC, and the time UE 230 spent in the target PSCell of the first subsequent CPC). Then, for example via an SN state transition message, or an Xn-U address indication message, or an SN reconfiguration completion message or a newly introduced message, MN 210 can send the received SCG UHI to the target SN of the second subsequent CPC. Alternatively, for example via an SN state transition message, or an Xn-U address indication message, or an SN reconfiguration completion message or a newly introduced message, MN 210 stores and associates the MCG UHI recorded by MN 210 with the SCG UHI received from the target SN of the first subsequent CPC, and MN 210 may send the associated UHI and optional UHI received from UE 230 to the target SN of the second subsequent CPC.

[0156] SCG UHI or UHI (e.g., sent to the target SN of the second subsequent CPC phase in the subsequent CPAC process or received from the target SN of the first subsequent CPC phase in the subsequent CPAC process), or associated UHI or optional UHI received from the UE, may include: historical information related to the source PSCell of the initial CPAC phase, historical information related to the target PSCell of the initial CPAC phase (or historical information associated with the source PSCell of the first subsequent CPC phase), and historical information related to the target PSCell of the first subsequent CPC phase (or historical information related to the source PSCell of the second subsequent CPC phase). For example, historical information related to the source PSCell of the initial CPAC phase may include the ID of the source PSCell of the initial CPAC phase and the time that the UE 230 remained in the source PSCell of the initial CPAC phase. For example, historical information related to the target PSCell of the initial CPAC phase may include: the ID of the target PSCell of the initial CPAC phase and the time that the UE 230 remained in the target PSCell of the initial CPAC phase. For example, historical information related to the source PSCell of the first subsequent CPC phase may include: the ID of the source PSCell of the first subsequent CPC phase, and the time the UE 230 remained in the source PSCell of the first subsequent CPC phase. For example, historical information related to the target PSCell of the first subsequent CPC phase may include: the ID of the target PSCell of the first subsequent CPC phase, and the time the UE 230 remained in the target PSCell of the first subsequent CPC phase. For example, historical information related to the source PSCell of the second subsequent CPC phase may include: the ID of the source PSCell of the second subsequent CPC phase, and the time the UE 230 remained in the source PSCell of the second subsequent CPC phase. For example, a cell identifier (ID) (e.g., source PSCell in the initial CPAC phase, target PSCell in the initial CPAC phase, source PSCell in the first subsequent CPC phase, target PSCell in the first subsequent CPC phase, and source PSCell in the second subsequent CPC phase) may include PCI and carrier frequency information (e.g., ARFCN), and / or CGI information (e.g., PLMN identifier, cell identifier, and TrackingAreaCode).For example, if MN 210 re-encodes or stores SCG UHI, the time UE 230 spends in the target PSCell of the first subsequent CPC phase, or the time UE 230 spends in the source PSCell of the second subsequent CPC phase, can be determined by the time between the time MN 210 receives the RRC reconfiguration completion message indicating the execution of the first subsequent CPC and the time MN 210 receives the RRC reconfiguration completion message indicating the execution of the second subsequent CPC. In other words, the time UE 230 spends in the target PSCell of the first subsequent CPC phase, or the time UE 230 spends in the source PSCell of the second subsequent CPC phase, is equal to the time MN 210 receives the RRC reconfiguration completion message indicating the execution of the second subsequent CPC minus ("-") the time MN 210 receives the RRC reconfiguration completion message indicating the execution of the first subsequent CPC.

[0157] For example, for subsequent CPC stages X, such as X=2, 3, ... Figure 4 The illustration shows a signaling diagram of process 400 for the Xth subsequent CPC phase in a subsequent CPAC process, according to some example embodiments of this disclosure. (See diagram for example.) Figure 4 As shown, process 400 involves UE 230, MN 210, target SN 402 of the (X-1)th subsequent CPC phase in the subsequent CPAC process, and target SN 404 of the Xth subsequent CPC phase in the subsequent CPAC process. (See reference) Figure 2A The target SN402 of the (X-1)th subsequent CPC phase can be one of SNs 220-2 to 220-N, and the target SN404 of the Xth subsequent CPC phase can be a different SN among SNs 220-2 to 220-N.

[0158] Specifically, based on a subscription (at 410) or a request (i.e., requesting SCG UHI from the target SN 402 of the (X-1)th subsequent CPC via an SN modification request message (at 430)), for example, when the Xth subsequent CPC executes successfully, after receiving the SN modification request message from MN 210 (at 430), an indication for requesting SCG UHI from the target SN 402 of the (X-1)th subsequent CPC can be included in the SN modification request message (at 430), which notifies the target SN 402 of the (X-1)th subsequent CPC to stop providing user data to the UE 230. The target SN 402 of the (X-1)th subsequent CPC can update the latest SCG UHI (including the time the UE 230 has remained in the source PSCell of the initial CPAC, the time the UE 230 has remained in the target PSCell of the initial CPAC, ... and the UE 230 stays in the target PSCell of the (X-1) subsequent CPC for a period of time. The target SN 402 of the (X-1) subsequent CPC can send the latest SCG UHI to MN 210, for example, via an SN modification request confirmation message (at 435), or an SN state transition message (at 450), or a newly introduced message. Or it can be subscribed to (i.e., the target SN 402 of the (X-1) subsequent CPC is subscribed to, for example, during the SN addition process. When the PSCell is changed or the CPC is executed, the target SN 402 of the (X-1) subsequent CPC can provide the latest SCG UHI to MN 210, for example, via an SN modification process initiated by the SN when the SCG UHI is changed, or via an SN modification request confirmation message (at 435), or an SN state transition message (at 450), or a newly introduced message.

[0159] After MN 210 receives the latest SCG UHI from the latest service SN / target SN 402 of the (X-1)th subsequent CPC, MN 210 may send the received latest SCG-UHI to the target SN 404 of the Xth subsequent CPC, for example via an SN reconfiguration complete message (at 460), or an SN state transition message (at 462), or an Xn-U address indication message (at 464), or a newly introduced message (not shown). Alternatively, MN 210 stores and associates the MCG UHI recorded by MN 210 and the SCG UHI received from the latest serving SN / target SN 402 of the (X-1)th subsequent CPC, and MN 210 may send the associated UHI and optional UHI received from UE 230 to the latest serving SN / target SN 404 of the Xth subsequent CPC, for example via an SN reconfiguration completion message (at 460), or an SN state transition message (at 462), or an Xn-U address indication message (at 464), or a newly introduced message (not shown).

[0160] It should be understood that Figure 4 The steps shown are for illustrative purposes only and are not intended to limit anything. For example, the order of the steps may be changed, some steps may be combined, one or more steps may be omitted, or one or more steps may be included. This disclosure does not impose any limitations.

[0161] In some example embodiments, for the Xth subsequent CPC stage, MN 210 may determine the SCG UHI based on its stored / recorded SCG UHI, and MN 210 may also send the SCG UHI to the target SN of the Xth subsequent CPC stage in the subsequent CPAC process.

[0162] Figure 5 The diagram illustrates a signaling diagram of process 500 for the Xth subsequent CPC stage in a subsequent CPAC process, according to some example embodiments of this disclosure, where X is an integer greater than "1". For example... Figure 5 As shown, process 500 involves UE 230, MN 210, target SN 402 of the (X-1)th subsequent CPC phase in the subsequent CPAC process, and target SN 404 of the Xth subsequent CPC phase in the subsequent CPAC process. (See reference) Figure 2A The target SN 402 of the (X-1)th subsequent CPC phase can be one of SNs 220-2 to 220-N, and the target SN 404 of the Xth subsequent CPC phase can be a different SN among SNs 220-2 to 220-N.

[0163] like Figure 5As shown, for the (X-1)th subsequent CPC phase in the subsequent CPAC process, where X is an integer greater than "1", MN210 can store and record the latest SCG UHI at 512, for example, after receiving an RRC reconfiguration complete message indicating the triggering or execution of the (X-1)th subsequent CPC from UE 230 at 510, and then MN 210 can send the latest SCG UHI to the target SN 402 of the (X-1)th subsequent CPC phase in the subsequent CPAC process, for example, in the SN reconfiguration complete message or other messages (e.g., SN state transition message, or Xn-U address indication message or new introduction message not shown) at 514. Alternatively, MN210 stores and associates the MCG UHI and SCG UHI recorded by MN210, and MN210 may send the associated UHI and optional UHI received from UE230 to the target SN402 in the (X-1) subsequent CPC phase, for example in the SN reconfiguration completion message or other messages at 514 (e.g., SN state transition message, or Xn-U address indication message or new introduction message not shown).

[0164] For example, MN 210 can determine the time that UE 230 remains in the target PSCell of the (X-3)th subsequent CPC stage based on the time length between the time when MN 210 receives the RRC reconfiguration completion message indicating the triggering or execution of the (X-1)th subsequent CPC and the time when MN 210 receives the RRC reconfiguration completion message indicating the triggering or execution of the (X-2)th subsequent CPC, where X is an integer greater than "2".

[0165] like Figure 5 As shown, for the Xth subsequent CPC phase in the subsequent CPAC process, MN 210 can store and record the latest SCG UHI at 522, for example, after receiving the RRC reconfiguration complete message indicating the triggering or execution of the Xth subsequent CPC from UE 230 at 520, and then MN 210 can send the latest SCG UHI to the target SN 404 of the Xth subsequent CPC phase in the subsequent CPAC process, for example, in the SN reconfiguration complete message or other messages (e.g., SN state transition message, or Xn-U address indication message or new introduction message not shown) at 524. Alternatively, MN 210 stores and associates the MCG UHI and SCG UHI recorded by MN 210, and MN 210 may send the associated UHI and optional UHI received from UE 230 to the target SN 404 in the Xth subsequent CPC phase, for example in the SN reconfiguration completion message at 524 or other messages (e.g., SN state transition message, or Xn-U address indication message or new introduction message not shown).

[0166] For example, MN 210 can determine the time that UE 230 stays in the target PSCell of the (X-1)th subsequent CPC stage based on the time length between the time when MN 210 receives the RRC reconfiguration completion message indicating the triggering or execution of the Xth subsequent CPC and the time when MN 210 receives the RRC reconfiguration completion message indicating the triggering or execution of the (X-1)th subsequent CPC.

[0167] Specifically, the SCG UHI or UHI (e.g., the target SN sent to the Xth subsequent CPC phase in the subsequent CPAC process or received from the target SN of the (X-1)th subsequent CPC phase in the subsequent CPAC process), or associated UHI, or optional UHI received from UE 230, may include: historical information related to the source PSCell of the initial CPAC phase, and historical information related to the target PSCell of each of at least one previous CPAC phase preceding the Xth subsequent CPC phase. In other words, the SCG UHI, or associated UHI, or optional UHI received from UE 230 may include: historical information related to the source PSCell of the initial CPAC phase, and a list of historical information related to the target PSCell of each of at least one previous CPAC phase preceding the Xth subsequent CPC phase. Historical information related to the target PSCell of each of the at least one previous CPAC stages preceding the Xth subsequent CPC stage may include: historical information related to the target PSCell of the initial CPAC stage (or historical information related to the source PSCell of the first subsequent CPC stage), historical information related to the target PSCell of the first subsequent CPC stage (or historical information related to the source PSCell of the second subsequent CPC stage), ..., historical information related to the target PSCell of the (X-1)th subsequent CPC stage (or historical information related to the source PSCell of the Xth subsequent CPC stage).

[0168] For example, for the Xth subsequent CPC phase, the SCG UHI, or associated UHI, or optional UHI received from UE 230 may include: {[ID of the source PSCell of the initial CPC, time UE 230 stays in the source PSCell of the initial CPC], [ID of the target PSCell of the initial CPC, time UE 230 stays in the target PSCell of the initial CPC], [ID of the target PSCell of the first subsequent CPC, time UE 230 stays in the target PSCell of the first subsequent CPC], [ID of the target PSCell of the second subsequent CPC, time UE 230 stays in the target PSCell of the second subsequent CPC], ..., [ID of the target PSCell of the (X-1)th subsequent CPC, time UE 230 stays in the target PSCell of the (X-1)th subsequent CPC]}. Alternatively, for the Xth subsequent CPC phase, the SCG UHI, or associated UHI, or optional UHI received from the UE, may include: {[ID of the source PSCell of the initial CPC, time UE 230 stays in the source PSCell of the initial CPC], [ID of the source PSCell of the first subsequent CPC, time UE 230 stays in the source PSCell of the first subsequent CPC], [ID of the source PSCell of the second subsequent CPC, time UE 230 stays in the source PSCell of the second subsequent CPC], [ID of the source PSCell of the third subsequent CPC, time UE 230 stays in the source PSCell of the third subsequent CPC], ..., [ID of the source PSCell of the Xth subsequent CPC, time UE 230 stays in the source PSCell of the Xth subsequent CPC]}. For example, a cell ID (e.g., the source PSCell in the initial CPAC phase, the target PSCell in the initial CPAC phase, the source PSCell in the first subsequent CPC phase, the target PSCell in the first subsequent CPC phase, ..., the source PSCell in the Xth subsequent CPC phase) may include PCI and carrier frequency information (e.g., ARFCN), and / or CGI information (e.g., PLMN identifier, cell identifier, and TrackingAreaCode).

[0169] According to the reference Figure 5In the discussion, the target SN in the Xth subsequent CPC phase can receive, for example, SCG UHI or UHI recorded by MN 210. It should be understood that for the initial CPAC phase and the first subsequent CPC phase, MN 210 can record SCG UHI or UHI and send it to the corresponding target SN. For example, the SCG UHI or UHI sent to the target SN in the initial CPAC phase during the subsequent CPAC process may include: the ID of the source PSCell in the initial CPAC phase, and the time the UE 230 remained in the source PSCell in the initial CPAC phase. For example, the SCG UHI or UHI of the target SN sent to the first subsequent CPC phase in the subsequent CPAC process may include: the ID of the source PSCell in the initial CPAC phase, and the time the UE 230 remained in the source PSCell of the initial CPAC phase; and the ID of the target PSCell of the initial CPAC phase (i.e., the source PSCell of the first subsequent CPC phase), and the time the UE 230 remained in the target PSCell of the initial CPAC phase (i.e., the source PSCell of the first subsequent CPC phase). Details can be found in the embodiments described above regarding the initial CPAC phase and the first subsequent CPC phase in the subsequent CPAC process, which will not be repeated here for the sake of brevity.

[0170] It should be understood that the above example embodiments are for illustrative purposes only and are not intended to limit anything. For example, some of the above information may be combined, some information may be omitted, and some information may be modified. This disclosure does not limit this aspect.

[0171] In some cases, the MN or SN can be in a CU-DU split architecture. In some examples, MN 210 may include the CU of MN 210 and at least one DU of MN 210. For example, the CU of MN 210 may provide historical information to one of the at least one DU of MN 210, such as stored or recorded SCG UHI, SCG UHI received from the SN, mobility history information (MHI) generated by UE 230 received from UE 230, associated UHI, etc. In some examples, SN 220 (e.g., any SN from SN 220-1 to 220-N) may include the CU and DU of SN 220. For example, the CU of SN 220 may provide historical information to the DU of SN 220, such as stored or recorded SCG UHI, SCG UHI or associated UHI received from MN 210, MHI generated by UE 230 received from UE 230, MHI generated by UE 230 received from MN 210, etc.

[0172] It should be understood that, although reference Figures 2B-2C Some embodiments have been described, but this disclosure is not limited to the subsequent CPAC process between SNs initiated by MN. For example, the subsequent CPAC process in this disclosure may be a subsequent CPAC process initiated by MN (e.g., a subsequent CPAC process between SNs initiated by MN or a subsequent CPAC process within SN initiated by MN), or a subsequent CPAC process between or within SNs initiated by SN.

[0173] The Ping-Pong Incident During the Subsequent CPAC Process

[0174] One of the functions of Mobility Robustness Optimization (MRO) is to detect one or more ping-pong events (or situations) occurring during subsequent CPAC procedures. A ping-pong event during a subsequent CPAC procedure is defined as follows: the UE successfully executes a CPA execution / PCell add to the first PSCell, then the UE successfully executes a CPC execution / PCell change from the first PSCell to the second PSCell, but within a predefined finite time, the UE successfully executes a CPC execution / PCell change back from the second PSCell to the first PSCell; or, the UE successfully executes a CPC execution / PCell change from the first PSCell to the second PSCell, but within a predefined finite time, the UE successfully executes a CPC execution / PCell change back from the second PSCell to the first PSCell.

[0175] A ping-pong event can occur more than once in subsequent CPAC procedures, for example, after the UE receives an RRCReconfiguration message for subsequent CPAC procedures (e.g., which includes the configuration for subsequent CPAC procedures).

[0176] In this disclosure, network nodes, which may be MN or SN, can detect at least one ping-pong event during a subsequent CPAC process and record or store the occurrence of at least one ping-pong event during the subsequent CPAC process.

[0177] In some implementations, during a subsequent CPAC process initiated by the MN or during an inter-SN subsequent CPAC process initiated by the SN, the MN may detect at least one ping-pong event during the subsequent CPAC process.

[0178] Specifically, for subsequent CPAC processes initiated by MN (e.g., subsequent CPAC processes between SNs initiated by MN or subsequent CPAC processes within SNs initiated by MN) or subsequent CPAC processes between SNs initiated by SN, MN can collect statistical data on the occurrence of ping-pong in the subsequent CPAC process, and MN or MN's CU can analyze the occurrence of ping-pong in the subsequent CPAC process.

[0179] In some example embodiments, the MN may detect at least one ping-pong event during a subsequent CPAC process based on at least one of the following: a UHI associated with the MN, or an SCG UHI stored by the MN, a UHI or SCG UHI received from the UE, an SCG UHI received from the latest service SN, or at least one RRC reconfiguration completion message from the UE, which indicates that the UE applies the same identifier of the selected conditional reconfiguration when executing CPA or CPC.

[0180] In some example embodiments, the MN may determine that at least one ping-pong event has occurred if at least one of the following is satisfied: the time duration between the time the UE enters the PSCell and the time the UE re-enters the PSCell is less than a first threshold; the time duration between receiving two RRC reconfiguration completion messages indicating the same identifier or indicating CPAC execution toward the same cell is less than a second threshold; or the UE enters the second PSCell from the first PSCell and returns to the first PSCell, wherein the time the UE stays in the second PSCell is less than a third threshold. The first threshold, second threshold, or third threshold may be defaulted to or configured by the OAM or core network node for the MN.

[0181] For example, based on the SCG UHI stored by the MN, or based on the UHI associated by the MN, or based on the SCG-related historical information received from the UE (i.e., the mobility history information received from the UE), or based on the SCG UHI received from the latest service SN (e.g., the latest source SN of the initial CPAC or the latest source SN of any subsequent CPC), for example, based on the duration of time between the time the UE enters the PSCell (e.g., the first PSCell) and the time the UE re-enters / returns to the PSCell (e.g., the first PSCell), or the duration of time the UE stays in the first PSCell, or the duration of time the UE stays in the second PSCell, or the duration of time the UE returns to the first PSCell, if the UE leaves the second PSCell and then returns to the first PSCell within a predefined finite time, or if the duration of time between the time the UE enters the PSCell (e.g., the first PSCell) and the time the UE re-enters / returns to the PSCell (e.g., the first PSCell) is shorter than the predefined finite time, or if the UE stays in the second PSCell for a shorter predefined time, the MN can detect it as a ping-pong event. The predefined finite time can be assigned to the MN by default or by the OAM or core network nodes.

[0182] For example, based on an RRC reconfiguration completion message received from the UE, where the RRC reconfiguration completion message indicates the ID of the selected conditional reconfiguration applied by the UE during the execution of CPA or CPC (e.g., including information that enables the MN to identify the selected target PSCell SN, i.e., including the ID of the target PSCell selected by the UE for CPAC execution, i.e., the CondReconfigId corresponding to the target PSCell), for example, based on the time duration between receiving two RRC reconfiguration completion messages for the same target PSCell (e.g., both messages include the same ID of the same target PSCell selected by the UE for CPAC execution, which is the CondReconfigId corresponding to the target PSCell, e.g., both messages include the ID of the first target PSCell selected by the UE for CPAC execution, and / or based on the time duration between receiving an RRC reconfiguration completion message for the first PSCell and receiving an RRC reconfiguration completion message for the second PSCell, and / or based on the time duration between receiving an RRC reconfiguration completion message for the second PSCell and receiving an RRC reconfiguration completion message for the return to the first PSCell). The time duration between the RRC reconfiguration completion messages for the first PSCell, and / or based on the time duration between receiving the RRC reconfiguration completion message for the first PSCell (e.g., including the ID of the first target PSCell selected by the UE for CPAC execution, i.e., the CondReconfigId corresponding to the first target PSCell) and receiving the RRC reconfiguration completion message for returning to the first PSCell (e.g., including the ID of the first target PSCell selected by the UE for CPAC execution, i.e., the CondReconfigId corresponding to the second target PSCell), if the UE leaves the second PSCell and then returns to the first PSCell within a predefined finite time, or if the time duration between receiving the RRC reconfiguration completion message for the first PSCell and receiving the RRC reconfiguration completion message for returning to the first PSCell is shorter than a predefined limit time, or if the UE stays in the second PSCell for a shorter predefined time, the MN may detect it as a ping-pong event. The predefined finite time may be defaulted to or configured to the MN by the OAM or core network node.

[0183] In some examples, the MN may send an indication of the occurrence of at least one ping-pong event to at least one SN, where one of the SNs may be the latest serving SN in a subsequent CPAC process, the source SN of the initial CPAC phase, the target SN of the initial CPAC phase, the source SN of any subsequent CPC phase, or the target SN of any subsequent CPC phase.

[0184] For example, the MN can indicate the occurrence of potential ping-pong events(s) to the initial source SN (e.g., the source SN in the initial CPAC phase) and / or the latest serving SN, such as for subsequent CPAC procedures initiated by the SN between SNs. For example, the initial source SN is the node to which the source PSCell of the initial CPAC phase belongs. For example, the latest serving SN is the node to which the latest serving PSCell of the initial CPAC phase belongs, or the node to which the source PSCell of the initial CPAC phase belongs, or the node to which the target PSCell of the initial CPAC phase belongs, or the node to which the latest serving PSCell of the subsequent CPC phase belongs, or the node to which the source PSCell of the subsequent CPC phase belongs, or the node to which the target PSCell of the subsequent CPC phase belongs.

[0185] For example, the MN can send information related to the occurrence of the ping-pong event to the initial source SN (i.e., the node to which the source PSCell belongs in the initial CPAC phase) and / or the corresponding SN (e.g., the node to which the first PSCell belongs, or the node to which the second PSCell belongs).

[0186] For example, after receiving (e.g., from the MN or UE) an indication of the occurrence of a potential ping-pong event, the CU of the SN can indicate the occurrence of the potential ping-pong event to the SN's (multiple) relevant DUs (e.g., source DUs and / or candidate target DUs). For example, the SN can be the initial source SN (i.e., the node to which the source PSCell belongs in the initial CPAC phase) or the latest serving SN (e.g., the node to which the latest serving PSCell belongs in the initial CPAC phase, or the node to which the source PSCell belongs in the initial CPAC phase, or the node to which the target PSCell belongs in the initial CPAC phase, or the node to which the latest serving PSCell belongs in the subsequent CPC phase, or the node to which the source PSCell belongs in the subsequent CPC phase, or the node to which the target PSCell belongs in the subsequent CPC phase).

[0187] In some other implementations, during a subsequent CPAC process initiated by the SN within the SN, the SN can detect at least one ping-pong event during the subsequent CPAC process.

[0188] Specifically, for subsequent CPAC processes initiated by an SN within an SN, the SN that initiated the subsequent CPAC process can collect statistical data on the occurrence of ping-pong in the subsequent CPAC process, and the SN or its CU can analyze the occurrence of ping-pong in the subsequent CPAC process.

[0189] In some example embodiments, the SN may detect at least one ping-pong event during a subsequent CPAC process based on at least one of the following: a UHI or SCG UHI received from the MN, a UHI or SCG UHI received from the UE, an SCG UHI stored by the SN, or at least one RRC reconfiguration completion message received from the UE, the at least one RRC reconfiguration completion message indicating the same identifier of the selected conditional reconfiguration applied by the UE during the execution of CPA or CPC.

[0190] In some example embodiments, the SN can determine that at least one ping-pong event has occurred if at least one of the following is satisfied: the time duration between the time the UE enters the PSCell and the time the UE re-enters the PSCell is less than a first threshold; the time duration between receiving two RRC reconfiguration completion messages indicating the same identifier or indicating execution to the CPAC of the same cell is less than a second threshold; or the UE enters the second PSCell from the first PSCell and returns to the first PSCell, wherein the time the UE stays in the second PSCell is less than a third threshold. The first threshold, second threshold, or third threshold may be defaulted to or configured by the OAM or core network node to the MN.

[0191] For example, based on the UHI / SCG UHI received from the MN, or based on the SCG-related historical information received from the UE (i.e., mobility history information received from the UE), or based on the SCG UHI stored / recorded by the MN itself, such as the duration between the time point when the UE enters the PSCell (e.g., the first PSCell) and the time point when the UE re-enters / returns to the PSCell (e.g., the first PSCell), or the duration of time the UE stays in the first PSCell, or the duration of time the UE stays in the second PSCell, or the duration of time the UE returns to the first PSCell, if the UE leaves the second PSCell and then returns to the first PSCell within a predefined finite time, or if the duration between the time point when the UE enters the PSCell (e.g., the first PSCell) and the time point when the UE re-enters / returns to the PSCell (e.g., the first PSCell) is shorter than the predefined finite time, or if the UE stays in the second PSCell for a shorter predefined time, the MN can detect it as a ping-pong event. The predefined finite time can be defaulted to or configured to the MN by the OAM or core network node.

[0192] For example, based on an RRC reconfiguration completion message received from the UE, where the RRC reconfiguration completion message indicates the ID of the selected conditional reconfiguration applied by the UE during the execution of CPA or CPC (e.g., including information that enables the MN to identify the selected target PSCell SN, i.e., including the ID of the target PSCell selected by the UE for CPAC execution, i.e., the CondReconfigId corresponding to the target PSCell), for example, based on the time duration between receiving two RRC reconfiguration completion messages for the same target PSCell (e.g., both messages include the same ID of the same target PSCell selected by the UE for CPAC execution, which is the CondReconfigId corresponding to the target PSCell, e.g., both messages include the ID of the first target PSCell selected by the UE for CPAC execution, and / or based on the time duration between receiving an RRC reconfiguration completion message for the first PSCell and receiving an RRC reconfiguration completion message for the second PSCell, and / or based on the time duration between receiving an RRC reconfiguration completion message for the second PSCell and receiving an RRC reconfiguration completion message for returning to the first PSCell). The duration between the RRC reconfiguration completion messages for the PSCell and / or based on the duration between receiving the RRC reconfiguration completion message for the first PSCell (e.g., including the ID of the first target PSCell selected by the UE for CPAC execution, i.e., the CondReconfigId corresponding to the first target PSCell) and receiving the RRC reconfiguration completion message for returning to the first PSCell (e.g., including the ID of the first target PSCell selected by the UE for CPAC execution, i.e., the CondReconfigId corresponding to the second target PSCell), if the UE leaves the second PSCell and then returns to the first PSCell within a predefined finite time, or if the duration between receiving the RRC reconfiguration completion message for the first PSCell and receiving the RRC reconfiguration completion message for returning to the first PSCell is shorter than a predefined limit time, or if the UE stays in the second PSCell for a shorter predefined time, the SN can detect it as a ping-pong event. The predefined finite time can be defaulted, or can be configured to the SN by the MN, or can be configured by the core network node.

[0193] In some examples, after a potential ping-pong event is detected, the CU of the SN can indicate the occurrence of the potential ping-pong event to the (multiple) relevant DUs of the SN (e.g., the (multiple) relevant DUs include at least one of the following: source DU, target DU, and candidate target DU).

[0194] Therefore, since ping-pong events can occur during subsequent CPAC processes, a definition of a ping-pong event is provided, along with a solution for detecting ping-pong events on the network side. Based on this, the occurrence of (multiple) ping-pong events can be detected; for example, this can be used for further consideration.

[0195] It should be understood that the above example embodiments are for illustrative purposes only and are not intended to limit anything. For example, some of the above information may be combined, some information may be omitted, and some information may be modified. This disclosure does not limit this aspect.

[0196] Figure 6 An example of a device 600 suitable for implementing embodiments of the present disclosure is illustrated. Device 600 may be an example of an MN, source SN, or target SN as described herein. Device 600 may support wireless communication with MN 210, SN 220-1 to 220-N (including SN402, SN404), or any combination thereof. Device 600 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 602, memory 604, transceiver 606, and optional I / O controller 608. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0197] Processor 602, memory 604, transceiver 606, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 602, memory 604, transceiver 606, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0198] In some implementations, processor 602, memory 604, transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 602 and memory 604 coupled to processor 602 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 604 by processor 602).

[0199] For example, according to the examples disclosed herein, processor 602 may support wireless communication at device 600. Processor 602 may be configured to operate to support components used for the functions described in this disclosure.

[0200] Processor 602 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 602 may be configured to use a memory controller to operate a memory array. In other implementations, the memory controller may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory (e.g., memory 604) to cause device 600 to perform various functions of this disclosure.

[0201] Memory 604 may include random access memory (RAM) and read-only memory (ROM). Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 602, cause device 600 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 602, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 604 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0202] I / O controller 608 can manage input and output signals for device 600. I / O controller 608 can also manage peripheral devices not integrated into device M02. In some implementations, I / O controller 608 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 608 can utilize an operating system such as iOS®, ANDROID®, MS WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 608 can be implemented as part of a processor, such as processor 602. In some implementations, a user can interact with device 600 via I / O controller 608 or via hardware components controlled by I / O controller 608.

[0203] In some implementations, device 600 may include a single antenna 610. However, in other implementations, device 600 may have more than one antenna 610 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions concurrently. Transceiver 606 may communicate bidirectionally via one or more antennas 610, wired or wireless links, as described herein. For example, transceiver 606 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 606 may also include a modem for modulating packets, providing modulated packets to one or more antennas 610 for transmission, and demodulating packets received from one or more antennas 610. Transceiver 606 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0204] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 610 for transmitting the amplified signal into the air or wireless medium.

[0205] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 610 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0206] Figure 7An example of a processor 700 suitable for implementing some embodiments of the present disclosure is illustrated. Processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. Processor 700 may optionally include at least one memory 704, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 700 may optionally include one or more arithmetic logic units (ALUs) 706. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0207] Processor 700 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., processor chipset-local or included memory (e.g., processor 700)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0208] Controller 702 can be configured to manage and coordinate various operations of processor 700 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 700 to support various operations according to the examples described herein. For example, controller 702 can operate as a control unit of processor 700, generating control signals that manage the operation of various components of processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0209] Controller 702 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 704 and determine subsequent instructions(s) to be executed, such that processor 700 supports various operations according to the examples described herein. Controller 702 can be configured to track the memory addresses of instructions associated with memory 704. Controller 702 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 702 can be configured to interpret instructions and determine control signals to be output to other components of processor 700, such that processor 700 supports various operations according to the examples described herein. Additionally or alternatively, controller 702 can be configured to manage data flow within processor 700. Controller 702 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 700.

[0210] Memory 704 may include one or more caches (e.g., memory local to processor 700 or included in processor 700) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 704 may reside within or on the processor chipset (e.g., locally to processor 700). In other implementations, memory 704 may reside outside the processor chipset (e.g., remotely from processor 700).

[0211] Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 700, cause processor 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 702 and / or processor 700 may be configured to execute computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions. For example, processor 700 and / or controller 702 may be coupled to or coupled to memory 704, and processor 700, controller 702, and memory 704 may be configured to perform the various functions described herein. In some examples, processor 700 may include multiple processors, and memory 704 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0212] One or more ALU 706s can be configured to support various operations as described in the examples herein. In some implementations, one or more ALU 706s may reside within or on the processor chipset (e.g., processor 700). In some other implementations, one or more ALU 706s may reside outside the processor chipset (e.g., processor 700). One or more ALU 706s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 706s can receive input operands and opcodes that determine the operation to be performed. One or more ALU 706s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 706s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 706s to handle conditional operations, comparisons, and bitwise operations.

[0213] Based on the examples disclosed herein, processor 700 may support wireless communication. Processor 700 may be configured or operable to support components used in some embodiments of this disclosure.

[0214] Figure 8 A flowchart illustrating a method 800 performed by a UE according to various aspects of this disclosure is shown. The operation of method 800 can be implemented by the device or its components described herein. For example, the operation of method 800 can be performed by… Figure 2A The MN 210 is executed. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described functions. Alternatively or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0215] At 810, the method may include: determining the SCG UHI associated with at least one previous conditional CPAC stage in a subsequent CPAC process. The operation of 810 can be performed according to the examples described herein. In some implementations, aspects of the operation of 810 may be derived from references... Figure 2A The MN 210 is executed.

[0216] At 820, the method may include: sending an SCG UHI associated with at least one previous CPAC stage, or a UHI determined based on an SCG UHI associated with at least one previous CPAC stage, to the target SN of the current CPAC stage in a subsequent CPAC process. The operation of 820 can be performed according to the examples described herein. In some implementations, aspects of the operation of 820 may be derived from references... Figure 2A The MN 210 is executed.

[0217] Figure 9 A flowchart illustrating a method 900 performed by an SN according to various aspects of this disclosure is shown. Operation of method 900 may be implemented by a device or components thereof described herein. For example, operation of method 900 may be performed by a target SN (such as SN220-2 to 220-N or SN 402 / 404). In some implementations, the device may execute an instruction set to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0218] At 910, the method may include: receiving from MN an SCG UHI associated with at least one previous CPAC stage in a subsequent CPAC process, or a UHI determined based on an SCG UHI associated with at least one previous CPAC stage, wherein SN is the target SN of the current CPAC stage in the subsequent CPAC process. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be performed by the target SN of the CPAC stage in the subsequent CPAC process, as described with reference to the figure above.

[0219] At 920, the method may include performing one of the following: storing or updating the latest SCG UHI based on the received SCG UHI or the received UHI; or storing or updating the latest UHI based on the received SCG UHI or the received UHI. The operation at 920 may be performed according to the examples described herein. In some implementations, aspects of the operation at 920 may be performed by the target SN in the CPAC phase of the subsequent CPAC process described with reference to the above figure.

[0220] Figure 10 A flowchart illustrating a method 1000 performed by an SN according to various aspects of this disclosure is shown. Operation of method 1000 may be implemented by the device or its components described herein. For example, operation of method 1000 may be performed by… Figure 2AThe source SN220-1 is executed. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described functions. Alternatively or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0221] At 1010, the method may include: receiving from the MN a request or subscription for an SCG UHI associated with the SN, where the SN is the source SN for the initial CPAC phase in a subsequent CPAC process. The operation at 1010 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1010 may be derived from references... Figure 2A The source SN 220-1 is executed.

[0222] At point 1020, the method may include sending an SCG UHI associated with the SN to the MN. The operation at point 1020 can be performed according to the examples described herein. In some implementations, aspects of the operation at point 1020 can be found in the references. Figure 2A The source SN 220-1 is executed.

[0223] Figure 11 A flowchart illustrating method 1100 performed by a network node according to various aspects of this disclosure is shown. Operation of method 1100 may be implemented by the device or components thereof described herein. For example, operation of method 1100 may be performed by an MN or SN. In some implementations, the device may execute an instruction set to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the described functions.

[0224] At 1110, the method may include: detecting at least one ping-pong event during a subsequent CPAC process, wherein the subsequent CPAC process is a subsequent CPAC process initiated by the MN or an inter-SN subsequent CPAC process initiated by the SN, and the network node is the MN; or wherein the subsequent CPAC process is an intra-SN subsequent CPAC process initiated by the SN, and the network node is the SN. The operation at 1110 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1110 may be performed by the MN or SN as described above.

[0225] At 1120, the method may include recording the occurrence of at least one ping-pong event. The operation at 1120 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1120 may be performed by MN or SN as described above.

[0226] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0227] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0228] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0229] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0230] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0231] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A master node MN, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the MN: Identify the SCG user history information UHI associated with at least one previous CPAC stage in the subsequent conditional primary and secondary cell group SCG cell PSCell addition or modification CPAC process. as well as Send the SCG UHI associated with the at least one previous CPAC phase, or the UHI determined based on the SCG UHI associated with the at least one previous CPAC phase, to the target auxiliary node SN of the current CPAC phase in the subsequent CPAC process.

2. The MN of claim 1, wherein the at least one processor is configured such that the MN determines the SCG UHI associated with the at least one previous CPAC stage by: Based on the stored SCG UHI, determine the SCG UHI associated with the at least one previous CPAC stage.

3. The MN of claim 1, wherein the at least one processor is configured such that the MN determines the SCG UHI associated with the at least one previous CPAC stage by: Receive the SCG UHI associated with the at least one previous CPAC stage from the target SN of the previous CPAC stage in the subsequent CPAC process.

4. The MN of claim 3, wherein the at least one processor is further configured such that the MN: Send a request or subscription to the target SN of the previous CPAC phase in the subsequent CPAC process for the SCG UHI associated with the at least one previous CPAC phase.

5. The MN of claim 1, wherein the at least one processor is further configured such that the MN: The UHI is determined by associating the MCG UHI with the SCG UHI associated with the at least one previous CPAC stage.

6. The MN of claim 1, wherein the at least one processor is further configured such that the MN: Send to the target SN of the initial CPAC phase in the subsequent CPAC process an SCG UHI associated with the source SN of the initial CPAC phase in the subsequent CPAC process, or a UHI determined based on the SCG UHI associated with the source SN of the initial CPAC phase.

7. The MN of claim 6, wherein the at least one processor is further configured such that the MN: The MCG UHI is associated with the SCG UHI associated with the source SN of the initial CPAC phase to determine the UHI.

8. The MN of claim 6, wherein the at least one processor is further configured such that the MN: Send a request or subscription to the source SN of the initial CPAC phase in the subsequent CPAC process for the SCG UHI associated with the source SN of the initial CPAC phase in the subsequent CPAC process; and Receive the SCG UHI associated with the source SN of the initial CPAC phase in the subsequent CPAC process from the source SN of the initial CPAC phase.

9. The MN of claim 6, wherein the SCG UHI associated with the source SN in the initial CPAC phase of the subsequent CPAC process, or the UHI comprising: Historical information related to the source PSCell of the initial CPAC phase.

10. The MN of claim 1, wherein the SCG UHI associated with the at least one previous CPAC stage in the subsequent CPAC process, or the UHI comprising: Historical information related to the source PSCell in the initial CPAC phase, and Historical information related to the target PSCell of each of the at least one previous CPAC phase preceding the current CPAC phase.

11. The MN of claim 10, wherein the historical information associated with the target PSCell of a specific CPAC stage in the at least one previous CPAC stage includes: The identifier of the target PSCell in the specific CPAC phase, and The time that the user equipment (UE) remains in the target PSCell during the specific CPAC phase.

12. The MN of claim 11, wherein the at least one processor is further configured such that the MN: The time the UE remains in the target PSCell of the specific CPAC stage is determined based on the time between the time when the MN receives the RRC reconfiguration completion message indicating the execution of the subsequent conditional PSCell CPC change after the specific CPAC and the time when the MN receives the RRC reconfiguration completion message indicating the execution of the specific CPAC.

13. The MN of claim 9 or 10, wherein the historical information associated with the source PSCell in the initial CPAC phase includes: The identifier of the source PSCell in the initial CPAC phase, and The time the UE remains in the source PSCell during the initial CPAC phase.

14. The MN of claim 1, wherein the at least one previous CPAC phase includes an initial CPAC phase, and the current CPAC phase includes a first subsequent CPC phase.

15. The MN of claim 1, wherein the at least one previous CPAC phase includes an initial CPAC phase and subsequent CPC phases from a first subsequent CPC phase to a (X-1)th subsequent CPC phase, and the current CPAC phase includes an Xth subsequent CPC phase, where X is an integer not less than 2.

16. An auxiliary node SN, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the SN: Receive from the master node MN the SCG user history information UHI associated with at least one previous CPAC stage in the subsequent conditional primary and secondary cell group (SCG) cell PSCell addition or modification CPAC process, or the UHI determined based on the SCG UHI associated with the at least one previous CPAC stage, wherein the SN is the target SN of the current CPAC stage in the subsequent CPAC process. as well as Perform one of the following: Store or update the latest SCG UHI based on the received SCG UHI or the received UHI; or Store or update the latest UHI based on the received SCG UHI or the received UHI.

17. The SN of claim 16, wherein the at least one processor is configured such that the SN: Send the latest SCG UHI to the MN.

18. A network node, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the network node: Detect at least one ping-pong event during the subsequent addition or modification of the CPAC in the SCG cell of the conditional primary and secondary cell group; and Record the occurrence of at least one of the ping-pong events. The subsequent CPAC process is either a subsequent CPAC process initiated by the master node MN or an inter-SN subsequent CPAC process initiated by the slave node SN, and the network node is the MN, or The subsequent CPAC process is an intra-SN subsequent CPAC process initiated by the SN, and the network node is the SN.

19. The network node of claim 18, wherein the at least one processor is configured such that the network node: The occurrence of the at least one ping-pong event is determined based on one of the following: The time interval between the time when the UE enters the PSCell and the time when the UE re-enters the PSCell is shorter than a first threshold. If the time duration between receiving two RRC reconfiguration complete messages indicating the same identifier is less than a second threshold, or The UE moves from the first PSCell to the second PSCell and returns to the first PSCell, wherein the duration of the UE staying in the second PSCell is shorter than a third threshold.

20. The network node of claim 18, wherein the network node is the MN, and wherein the at least one processor is configured such that the network node: Send an indication of the occurrence of the at least one ping-pong event to the SN, wherein the SN is the latest serving SN in the subsequent CPAC process, the source SN of the initial CPAC phase, the target SN of the initial CPAC phase, the source SN of any subsequent CPC phase, or the target SN of any subsequent CPC phase.

Images