Method and apparatus for SON enhancement for CPAC process

Abstract

Embodiments of the present application relate to methods and apparatus for self-optimization (SON) enhancements for conditional primary-secondary cell group cell (PSCell) addition or change (CPAC) procedures. In accordance with an embodiment of the present application, a user equipment (UE) includes a transceiver and a processor coupled to the transceiver; and the processor is configured to perform at least one of: store failure-related information associated with a conditional primary-secondary cell group cell (PSCell) addition or change (CPAC) procedure, wherein the failure-related information includes at least one of: time information associated with the CPAC procedure; state information associated with one or two trigger events configured for a candidate PSCell of the CPAC process; configuration information related to the CPAC process; or identification information associated with the CPAC process; or transmitting the failure related information to a network via the transceiver.

Description

Technical Field

[0001] Embodiments of the present application generally relate to methods and apparatus for self-optimization (SON) enhancement of a conditional primary secondary cell group cell (PSCell) add or change (CPAC) procedure. Background Art

[0002] The next generation radio access network (NG-RAN) supports multi-radio dual connection (MR-DC) operation. In the MR-DC scenario, a user equipment (UE) with multiple transceivers can be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul. One node can provide new air interface (NR) access, and the other node can provide evolved universal terrestrial radio access (UTRA) (E-UTRA) or NR access. One node can act as a master node (MN), and the other node can act as a secondary node (SN). The MN and the SN are connected via a network interface (e.g., an Xn interface as specified in the third generation partnership project (3GPP) standard document), and at least the MN is connected to the core network. MR-DC includes NR-NR DC, EN-DC, NGEN-DC and / or NE-DC. The MN can be an eNB, ng-eNB or gNB. The SN can be an ng-eNB, en-gNB or gNB.

[0003] Currently, the conditional PSCell addition (CPA) process and the conditional PSCell change (CPC) process are supported. The CPAC process is a CPA process or a CPC process. According to the agreement of the 3GPP standard document, the CPAC process is defined as a PSCell addition or PSCell change performed by the UE when the execution conditions configured for CPAC are met. The UE starts evaluating the execution conditions when receiving the CPAC configuration information, and stops evaluating the execution conditions once the PSCell addition and / or change process is triggered or executed. Currently, in the 3GPP LTE system or the 5G system, the details of the SON enhancement for the CPAC process in the MR-DC scenario have not been discussed. Summary of the invention

[0004] Some embodiments of the present application provide a user equipment (UE). The UE includes a transceiver and a processor coupled to the transceiver; and the processor is configured to perform at least one of the following: storing failure-related information associated with a conditional primary auxiliary cell group cell (PSCell) addition or change (CPAC) process, wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; state information associated with one or two triggering events configured for a candidate PSCell of the CPAC process; configuration information related to the CPAC process; or identification information associated with the CPAC process; or transmitting the failure-related information to a network via the transceiver.

[0005] In some embodiments, the time information includes at least one of: the time elapsed between the start of execution of the last conditional reconfiguration toward a target PSCell and the reception of the latest conditional reconfiguration for the target PSCell; the time elapsed between the occurrence of a secondary cell group (SCG) failure when the UE is connected to a source PSCell and the reception of the latest conditional reconfiguration for the CPAC process; or the time elapsed between the start of execution of the last conditional reconfiguration toward the target PSCell and the SCG failure.

[0006] In some embodiments, the one or two trigger events include at least one of a first trigger event or a second trigger event, and wherein, in response to the start of the last conditional reconfiguration execution or the occurrence of the SCG failure, the status information includes at least one of the following: an indication for indicating whether the first trigger event is satisfied; an indication for indicating whether the second trigger event is satisfied; information about the first trigger event in response to satisfaction of the first trigger event; information about the second trigger event in response to satisfaction of the second trigger event; or the time duration between the satisfaction timing of the first trigger event and the satisfaction timing of the second trigger event.

[0007] In some embodiments, the first triggering event or the second triggering event includes at least one of the following: CondEvent A3; CondEvent A4; CondEvent A5; CondEvent B1; or CondEvent B2.

[0008] In some embodiments, the configuration information includes at least one of: a list of configured candidate PSCells for the CPAC process; one or two trigger events configured for a candidate PSCell within the list of configured candidate PSCells; an indication of whether the measured adjacent PSCell is the candidate PSCell; or one or more measurement configurations configured for the CPAC process.

[0009] In some embodiments, the one or more measurement configurations include measurement identifier (ID) information to be used for the CPAC process.

[0010] In some embodiments, the identification information includes at least one of: the type of PSCell change operation performed during the CPAC process; the type of PSCell add operation performed during the CPAC process; an indication indicating that the PSCell change operation is performed during the CPAC process; an indication indicating that the PSCell add operation is performed during the CPAC process; an indication indicating whether the last performed PSCell change operation was a conditional PSCell change (CPC) operation; or an indication indicating whether the last performed PSCell add operation was a conditional PSCell add (CPA) operation.

[0011] In some embodiments, the processor of the UE is configured to transmit at least one of the following via the transceiver: an indication indicating the occurrence of an SCG failure before the start of conditional reconfiguration execution toward a target PSCell; an indication indicating the occurrence of a master cell group (MCG) failure before the start of conditional reconfiguration execution toward the target PSCell; an indication indicating the occurrence of a failure during the conditional reconfiguration execution toward the target PSCell; or an indication indicating the occurrence of an RLF in the candidate PSCell shortly after completion of the conditional reconfiguration execution toward the target PSCell.

[0012] In some embodiments, the processor of the UE is configured to transmit, via the transceiver, an indication indicating an optional capability of the UE to store or transmit the failure-related information.

[0013] Some embodiments of the present application also provide a master node (MN). The MN includes a transceiver and a processor coupled to the transceiver; and the processor is configured to perform at least one of the following: receiving failure-related information associated with a conditional primary auxiliary cell group (PSCell) addition or change (CPAC) process from a user equipment (UE) via the transceiver, wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; state information associated with one or two triggering events configured for a candidate PSCell of the CPAC process; configuration information related to the CPAC process; or identification information associated with the CPAC process; performing a mobility robustness optimization (MRO) analysis or optimization operation on parameters related to the CPAC process; or transmitting the failure-related information to a secondary node (SN) via the transceiver.

[0014] In some embodiments, the time information includes at least one of: the time elapsed between the start of execution of the last conditional reconfiguration toward a target PSCell and the reception of the latest conditional reconfiguration for the target PSCell; the time elapsed between the occurrence of a secondary cell group (SCG) failure when the UE is connected to a source PSCell and the reception of the latest conditional reconfiguration for the CPAC process; or the time elapsed between the start of execution of the last conditional reconfiguration toward the target PSCell and the SCG failure.

[0015] In some embodiments, the one or two trigger events include at least one of a first trigger event or a second trigger event, and wherein, in response to the initiation of the last conditional reconfiguration execution or the occurrence of the SCG failure, the status information includes at least one of the following: an indication for indicating whether the first trigger event is satisfied; an indication for indicating whether the second trigger event is satisfied; information about the first trigger event in response to satisfaction of the first trigger event; information about the second trigger event in response to satisfaction of the second trigger event; or the time duration between the satisfaction timing of the first trigger event and the satisfaction timing of the second trigger event.

[0016] In some embodiments, the first triggering event or the second triggering event includes at least one of the following: CondEvent A3; CondEvent A4; CondEvent A5; CondEvent B1; or CondEvent B2.

[0017] In some embodiments, the configuration information includes at least one of: a list of configured candidate PSCells for the CPAC process; one or two trigger events configured for a candidate PSCell within the list of configured candidate PSCells; an indication of whether the measured adjacent PSCell is the candidate PSCell; or one or more measurement configurations configured for the CPAC process.

[0018] In some embodiments, the one or more measurement configurations include measurement identifier (ID) information to be used for the CPAC process.

[0019] In some embodiments, the identification information includes at least one of: the type of PSCell change operation performed during the CPAC process; the type of PSCell add operation performed during the CPAC process; an indication indicating that the PSCell change operation is performed during the CPAC process; an indication indicating that the PSCell add operation is performed during the CPAC process; an indication indicating whether the last performed PSCell change operation was a conditional PSCell change (CPC) operation; or an indication indicating whether the last performed PSCell add operation was a conditional PSCell add (CPA) operation.

[0020] In some embodiments, the processor of the MN is configured to receive at least one of the following from the UE via the transceiver: an indication indicating the occurrence of an SCG failure before the start of conditional reconfiguration execution toward a target PSCell; an indication indicating the occurrence of a failure during the conditional reconfiguration execution toward the target PSCell; or an indication indicating the occurrence of an RLF in the candidate PSCell shortly after completion of the conditional reconfiguration execution toward the target PSCell.

[0021] In some embodiments, the processor of the MN is configured to receive, from the UE via the transceiver, an indication indicating an optional capability of the UE to store or transmit the failure-related information.

[0022] In some embodiments, the SN is one of: the last serving SN of the UE; and the source SN of the UE of the CPAC process.

[0023] In some embodiments, the processor of the MN is configured to receive, from the SN via the transceiver, one of: one or more CPAC configurations; and a container associated with the one or more CPAC configurations.

[0024] In some embodiments, the one or more CPAC configurations include at least one of: a list of configured candidate PSCells for the CPAC process; one or two trigger events configured for a candidate PSCell within the list of configured candidate PSCells; one or more SCG measurement configurations configured for the CPAC process; or an upper limit on the total number of configured candidate PSCells.

[0025] In some embodiments, the one or more CPAC configurations and one of the containers are received in one of: an S-NODE modification required message; an SGNB modification required message; an S-NODE release request confirmation (ACK) message; an SGNB release request confirmation (ACK) message; an SN status transfer message; and a newly defined Xn or X2 message.

[0026] In some embodiments, the processor of the MN is configured to transmit the one of the one or more CPAC configurations and the container to the SN via the transceiver.

[0027] In some embodiments, the one or more CPAC configurations and the one of the containers are transmitted in one of: an SCG failure information report message; and a newly defined Xn or X2 message.

[0028] In some embodiments, the MN is a centralized unit (CU), and wherein the processor of the CU is configured to transmit, via the transceiver, the failure related information to at least one distributed unit (DU) managed by the CU.

[0029] Some embodiments of the present application also provide a source auxiliary node (SN). The source SN includes a transceiver and a processor coupled to the transceiver; and the processor is configured to perform at least one of the following: receiving failure-related information associated with a conditional primary auxiliary cell group (PSCell) addition or change (CPAC) process from a master node (MN) via the transceiver, wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; state information associated with one or two triggering events configured for a candidate PSCell of the CPAC process; configuration information related to the CPAC process; or identification information associated with the CPAC process; or performing a mobility robustness optimization (MRO) analysis or optimization operation on parameters related to the CPAC process.

[0030] In some embodiments, the time information includes at least one of: the time elapsed between the start of execution of the last conditional reconfiguration toward a target PSCell and the reception of the latest conditional reconfiguration for the target PSCell; the time elapsed between the occurrence of a secondary cell group (SCG) failure when a user equipment (UE) is connected to a source PSCell and the reception of the latest conditional reconfiguration for the CPAC process; or the time elapsed between the start of execution of the last conditional reconfiguration toward the target PSCell and the SCG failure.

[0031] In some embodiments, the one or two trigger events include at least one of a first trigger event or a second trigger event, and wherein, in response to the initiation of the last conditional reconfiguration execution or the occurrence of the SCG failure, the status information includes at least one of the following: an indication for indicating whether the first trigger event is satisfied; an indication for indicating whether the second trigger event is satisfied; information about the first trigger event in response to satisfaction of the first trigger event; information about the second trigger event in response to satisfaction of the second trigger event; or the time duration between the satisfaction timing of the first trigger event and the satisfaction timing of the second trigger event.

[0032] In some embodiments, the first triggering event or the second triggering event includes at least one of the following: CondEvent A3; CondEvent A4; CondEvent A5; CondEvent B1; or CondEvent B2.

[0033] In some embodiments, the configuration information includes at least one of: a list of configured candidate PSCells for the CPAC process; one or two trigger events configured for a candidate PSCell within the list of configured candidate PSCells; an indication of whether the measured adjacent PSCell is the candidate PSCell; or one or more measurement configurations configured for the CPAC process.

[0034] In some embodiments, the one or more measurement configurations include measurement identifier (ID) information to be used for the CPAC process.

[0035] In some embodiments, the identification information includes at least one of: the type of PSCell change operation performed during the CPAC process; the type of PSCell add operation performed during the CPAC process; an indication indicating that the PSCell change operation is performed during the CPAC process; an indication indicating that the PSCell add operation is performed during the CPAC process; an indication indicating whether the last performed PSCell change operation was a conditional PSCell change (CPC) operation; or an indication indicating whether the last performed PSCell add operation was a conditional PSCell add (CPA) operation.

[0036] In some embodiments, the failure-related information includes at least one of: an indication of the occurrence of an SCG failure before the start of conditional reconfiguration execution toward the target PSCell; an indication of the occurrence of a failure during the conditional reconfiguration execution toward the target PSCell; or an indication of the occurrence of an RLF in the candidate PSCell shortly after completion of the conditional reconfiguration execution toward the target PSCell.

[0037] In some embodiments, the processor of the source SN is configured to receive, via the transceiver, from a user equipment (UE), an indication indicating occurrence of a master cell group (MCG) failure prior to initiation of conditional reconfiguration execution towards a target PSCell.

[0038] In some embodiments, the processor of the source SN is configured to transmit, via the transceiver, to the MN one of: one or more CPAC configurations; and containers associated with the one or more CPAC configurations.

[0039] In some embodiments, the one or more CPAC configurations include at least one of: a list of configured candidate PSCells for the CPAC process; one or two trigger events configured for a candidate PSCell within the list of configured candidate PSCells; one or more SCG measurement configurations configured for the CPAC process; or an upper limit on the total number of configured candidate PSCells.

[0040] In some embodiments, the one or more CPAC configurations and one of the containers are transmitted in one of: an S-NODE modification required message; an SGNB modification required message; an S-NODE release request confirmation (ACK) message; an SGNB release request confirmation (ACK) message; an SN status transfer message; and a newly defined Xn or X2 message.

[0041] In some embodiments, the processor of the source SN is configured to receive one of the one or more CPAC configurations and the container from the MN via the transceiver.

[0042] In some embodiments, the one or more CPAC configurations and the one of the containers are received in one of: an SCG failure information report message; and a newly defined Xn or X2 message.

[0043] In some embodiments, the source SN is a centralized unit (CU), and wherein the processor of the CU is configured to transmit the failure related information via the transceiver to at least one distributed unit (DU) managed by the CU.

[0044] Some embodiments of the present application provide a method performed by a UE. The method includes: storing failure-related information associated with a conditional primary auxiliary cell group (PSCell) add or change (CPAC) process, wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; state information associated with one or two triggering events configured for a candidate PSCell of the CPAC process; configuration information associated with the CPAC process; or identification information associated with the CPAC process; and transmitting the failure-related information to a network.

[0045] Some embodiments of the present application provide a method performed by a MN. The method includes performing at least one of the following: receiving failure-related information associated with a conditional primary auxiliary cell group (PSCell) addition or change (CPAC) process from a user equipment (UE), wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; state information associated with one or two triggering events configured for a candidate PSCell of the CPAC process; configuration information related to the CPAC process; or identification information associated with the CPAC process; performing a mobility robustness optimization (MRO) analysis or optimization operation on parameters related to the CPAC process; or transmitting the failure-related information to a secondary node (SN).

[0046] Some embodiments of the present application provide a method performed by a source SN. The method includes performing at least one of the following: receiving failure-related information associated with a conditional primary auxiliary cell group (PSCell) addition or change (CPAC) process from a master node (MN), wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; state information associated with one or two triggering events configured for a candidate PSCell of the CPAC process; configuration information associated with the CPAC process; or identification information associated with the CPAC process; or performing a mobility robustness optimization (MRO) analysis or optimization operation on parameters associated with the CPAC process.

[0047] Some embodiments of the present application provide a device for wireless communication. The device includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement the above method performed by a network node (MN or source SN).

[0048] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] To describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented by reference to specific embodiments of the application illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered limiting of its scope.

[0050] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.

[0051] Figure 2 An exemplary flow chart illustrating transmission failure related information according to some embodiments of the present application.

[0052] Figure 3 An exemplary flow chart illustrating receiving failure-related information according to some embodiments of the present application.

[0053] Figure 4 A further exemplary flow chart illustrating receiving failure-related information according to some embodiments of the present application.

[0054] Figure 5 An exemplary flow chart illustrating CPAC failure information exchange in a network according to some embodiments of the present application.

[0055] Figure 6 An exemplary block diagram illustrating an apparatus for a CPAC process according to some embodiments of the present application.

[0056] Figure 7 A further exemplary block diagram illustrating an apparatus for a CPAC process according to some embodiments of the present application. DETAILED DESCRIPTION

[0057] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application, and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be implemented by different embodiments intended to be included in the spirit and scope of the present application.

[0058] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. For ease of understanding, embodiments are provided in specific network architectures and new service scenarios, such as 3GPP 5G, 3GPP LTE Release 8, etc. It is considered that, with the development of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems; and in addition, the terms stated in the present application may be changed, which should not affect the principles of the present application.

[0059] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.

[0060] like Figure 1 As shown in FIG. 1 , the wireless communication system 100 may be a dual-connectivity system 100, including at least one UE 101, at least one MN 102, and at least one SN 103. Specifically, for illustrative purposes, Figure 1 The dual-connectivity system 100 in FIG. 1 includes a UE 101, a MN 102, and a SN 103. Figure 1 A specific number of UE 101, MN 102, and SN 103 are depicted in FIG. 1 , but it is contemplated that any number of UE 101, MN 102, and SN 103 may be included in the wireless communication system 100.

[0061] refer to Figure 1 , UE 101 may be connected to MN 102 and SN 103 via a network interface (e.g., a Uu interface as specified in a 3GPP standard document). MN 102 and SN 103 may be connected to each other via a network interface (e.g., an Xn interface as specified in a 3GPP standard document for NR-NR DC or NGEN-DC or NE-DC, or an X2 interface as specified in a 3GPP standard document for EN-DC). MN 102 may be connected to MN 102 and SN 103 via a network interface (e.g., an Xn interface as specified in a 3GPP standard document for NR-NR DC or NGEN-DC or NE-DC, or an X2 interface as specified in a 3GPP standard document for EN-DC). Figure 1UE 102 may be configured to utilize resources provided by MN 102 and SN 103 to perform data transmission.

[0062] MN 102 may refer to a radio access node that provides a control plane connection to a core network. In an embodiment of the present application, in an E-UTRA-NR dual connectivity (EN-DC) scenario, MN 102 may be an eNB. In another embodiment of the present application, in a next generation E-UTRA-NR dual connectivity (NGEN-DC) scenario, MN 102 may be an ng-eNB. In yet another embodiment of the present application, in an NR-E-UTRA dual connectivity (NE-DC) scenario or an NR-NR dual connectivity (NR-DC) scenario, MN 102 may be a gNB.

[0063] MN 102 may be associated with a master cell group (MCG). MCG may refer to a set of serving cells associated with MN 102 and may include a primary cell (PCell) and optionally one or more secondary cells (SCells) of the MCG. PCell may provide control plane connectivity to UE 101.

[0064] SN 103 may refer to a radio access node that does not have a control plane connection to the core network but provides additional resources for UE 101. In an embodiment of the present application, in an EN-DC scenario, SN 103 may be an en-gNB. In another embodiment of the present application, in a NE-DC scenario, SN 103 may be an ng-eNB. In yet another embodiment of the present application, in an NR-DC scenario or a NGEN-DC scenario, SN 103 may be a gNB.

[0065] SN 103 may be associated with a secondary cell group (SCG). SCG may refer to a group of serving cells associated with SN 103 and may include a primary secondary cell (PSCell) and optionally one or more secondary cells (SCells). The Pcell of the MCG and the PSCell of the SCG may also be referred to as a special cell (SpCell).

[0066] In some embodiments of the present application, UE 101 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, and a modem), etc. In some other embodiments of the present application, UE 101 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals over a wireless network.

[0067] In some other embodiments of the present application, UE 101 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, UE 101 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal or a device, or described using other terms used in the art.

[0068] According to the 3GPP standard document, CPA initiated by MN is supported, and two types of CPC processes are supported: CPC process initiated by MN; or CPC process initiated by SN. "CPA" or "CPC" or "CPAC" in the present disclosure means conditional PSCell addition or conditional PSCell change in LTE-LTE DC situation and any MR-DC situation, including NR-NR DC, EN-DC, NGEN-DC and NE-DC. In the MN-initiated CPAC process, the MN determines a list of candidate PSCells for CPAC or generates execution conditions for CPAC; in the SN-initiated CPC process, the source SN determines a list of candidate PSCells for CPAC or generates execution conditions for CPAC.

[0069] The 3GPP standard document TS38.331 introduces some events for the CPAC process, for example, CondEventA3, CondEvent A4, CondEvent A5, CondEvent B1 and Event B2.

[0070] Generally speaking, a successful PSCell change report (e.g., SPC-report) will be introduced in 3GPP Release 18 to optimize PSCell change or CPAC related parameters, for example, if a physical layer problem is detected by the UE during an ongoing PSCell change procedure or an ongoing CPAC procedure. In order to report the SPC-report, the network configures a configuration for the UE to record or generate an SPC-report (e.g., successPSCellChange-Config IE (information element)), for example, via an RRCReconfiguration message (including a timer T304 related threshold (a threshold generated by the target PSCell, for example, thresholdPercentageT304), a timer T310 related threshold (a threshold generated by the source PSCell or source Pcell, for example, thresholdPercentageT310), or a timer T312 related threshold (a threshold generated by the source PSCell or source Pcell, for example, thresholdPercentageT312)). Based on the network configuration, the UE needs to record or generate successful PSCell change related parameters when at least one trigger condition is met. An SPC-Report may be generated and reported to the network, including the Cell Global Identifier (CGI) information of the source PSCell, the CGI information of the target PSCell, the cause value of a successful PSCell change report (eg, t304-Cause, t310-Cause, or t312-Cause), and measurement results.

[0071] Currently, the purpose of the SCG Failure Information procedure is to notify the E-UTRAN or NR MN about an SCG failure that the UE has experienced. SCG failure types include SCG radio link failure, failure of SCG reconfiguration with synchronization, SCG configuration failure of RRC message on signaling radio bearer (SRB) 3, SCG integrity check failure, and consistent uplink LBT failure on PSCell for operation with shared spectrum channel access. The SCG failure type, measurement results in the MCG and / or measurement results in the SCG may be included in the SCG Failure Information message. After the network receives the SCG Failure Information message, it may trigger the UE to perform an SN release or modification or change procedure. In the case of SCG failure, the following information may also be included in the SCG Failure Information message: previous PSCell ID (i.e., PCI); failed PSCell ID (i.e., PCI); time SCG failure and / or RA-information.

[0072] Currently, there is no mechanism for SON enhancement of the CPAC process in the MR-DC scenario. Embodiments of the present application are intended to address the above-mentioned problems. Some embodiments of the present application define information that needs to be reported to the network for MRO purposes taking into account different failure situations in the CPAC process. Some embodiments of the present application define signaling exchanges of CPAC failure-related information between RAN nodes (e.g., between MN and SN) or in a CU-DU split architecture.

[0073] More specifically, in some embodiments of the present application, failure-related information associated with the CPAC process, including at least one of time-related information associated with the CPAC process, status information associated with a CPAC triggering event or condition, and / or a type of conditional PSCell change or addition process, may be recorded by the UE and reported to the network (e.g., MN or SN) for MRO purposes.

[0074] In some embodiments of the present application, the source SN sends a container (e.g., SN mobility information IE) to the MN via an existing message (e.g., SN release request ACK message or SN status transfer message) or via a newly defined Xn or X2 message. In some other embodiments of the present application, the source SN may transmit the latest CPAC configuration to the MN via an existing message (e.g., SN release request ACK message or SN status transfer message) or via a newly defined Xn or X2 message. For MRO purposes, for example, after receiving failure-related information or an SCG failure information message from the UE, the MN may transmit the received latest CPAC configuration to the source SN via a newly defined Xn or X2 message or an SCG FAILURE INFORMATION REPORT message.

[0075] In some embodiments of the present application, failure-related information associated with the CPAC process is exchanged between the MN and the source SN or between the MN and the last serving SN. For example, in a CU-DU separation architecture, the BS-CU (e.g., gNB-CU) may transmit failure-related information associated with the CPAC process to the BS-DU (e.g., gNB-DU). Some embodiments of the present application introduce an optional capability of the UE to store or report failure-related information associated with the CPAC process. More details about the embodiments of the present application will be described in the following text in conjunction with the accompanying drawings.

[0076] In the CPAC process, after receiving the CPAC configuration or the conditional reconfiguration for the CPAC process, the UE decides whether or when to perform a CPAC execution (e.g., performing a PSCell change toward a target PSCell in which the corresponding CPC execution is satisfied, or performing a PSCell addition toward a target PSCell in which the corresponding CPA execution is satisfied). Failures in the CPAC process (e.g., SCG radio link failure, failure of CPAC execution, failure of CPAC execution, or failure of SCG reconfiguration with synchronization) will affect system performance, and the MRO function of the CPAC process should be considered. In some embodiments of the present application, auxiliary information (e.g., SCG failure-related information or failure-related information associated with the CPAC process that is beneficial to the MRO purpose) is provided in the CPAC process. Figures 2 to 4 The embodiments are described as follows.

[0077] Figure 2 An exemplary flow chart illustrating transmission failure related information according to some embodiments of the present application. Figure 2 The exemplary process 200 in the embodiment of the present invention may be performed by a UE (e.g., Figure 1 Although described with respect to a UE, it should be understood that other devices may be configured to perform similar Figure 2 The method of the method. Figure 2 In some other embodiments, without departing from the spirit and scope of the present disclosure, only the following operations are performed: Figure 2 Operation 201 or operation 202 shown in .

[0078] In such Figure 2 In the exemplary process 200 shown in FIG. 2 , in operation 201, the UE may store failure related information associated with the CPAC process. Figure 2 In the above, "failure" or "SCG failure" means SCG radio link failure (RLF), failure of CPAC execution, failure of CPAC execution, or failure of SCG reconfiguration with synchronization. Failure-related information associated with the CPAC process may also be referred to as "CPAC failure-related information" or "SCG failure-related information for the CPAC process", etc. The failure-related information associated with the CPAC process may include at least one of the following:

[0079] (1) Time information associated with the CPAC process;

[0080] (2) Status information associated with one or two triggering events configured for the candidate PSCell of the CPAC process;

[0081] (3) configuration information related to the CPAC process; or

[0082] (4) Identification information associated with the CPAC process.

[0083] In operation 202, the UE may send a request to a network (eg, a MN (eg, Figure 1 MN 102 as shown in ) or SN (e.g., as Figure 1 SN 103) shown in ) or a network node to which the UE is connected or reestablished after a failure transmits the failure related information. For example, the UE may transmit the failure related information to the MN via an SCG failure information message. Optionally, before operation 202, the UE transmits to the network an indication for indicating storage of failure related information associated with the CPAC process; the UE receives from the network a request for failure related information associated with the CPAC process; and then, in operation 202, the UE transmits the stored failure related information to the network.

[0084] In some embodiments, the time information associated with the CPAC process includes at least one of the following:

[0085] (1) The time between the start of the last conditional reconfiguration execution towards the target PSCell and the receipt of the latest conditional reconfiguration for the target PSCell, or the time between the execution of CPAC and the receipt of the latest conditional reconfiguration of the CPAC process;

[0086] (2) The time elapsed between the occurrence of an SCG failure when the UE is connected to the source PSCell and the receipt of the latest conditional reconfiguration of the CPAC procedure, e.g., the SCG failure may be a RLF in the source SCG; or the time elapsed between the occurrence of an SCG failure in the source SCG and the receipt of the latest conditional reconfiguration of the CPAC procedure; or

[0087] (3) The time elapsed between “the start of the last conditional reconfiguration execution toward the target PSCell” and “SCG failure”, or the time elapsed between “CPAC execution” and “failure of CPAC execution or occurrence of CPAC execution failure”. For example, the SCG failure may be a RLF in the target SCG, or a failure of CPAC execution or a CPAC execution failure. The failure of CPAC execution or the CPAC execution failure may include, for example, a failure of a PSCell change toward a target PSCell where a corresponding CPC execution is satisfied, or a failure of a PSCell addition toward a target PSCell where a corresponding CPA execution is satisfied, or a failure of SCG reconfiguration with synchronization occurs.

[0088] In some embodiments, one or two triggering events configured for a candidate PSCell include at least one of a triggering event (denoted as a "first triggering event" for simplicity) or another triggering event (denoted as a "second triggering event" for simplicity). In response to the initiation of the last conditional reconfiguration execution or the occurrence of an SCG failure, the state information associated with the one or two triggering events may include at least one of the following:

[0089] (1) an indication for indicating whether a first trigger event is satisfied;

[0090] (2) an indication for indicating whether a second triggering event is satisfied;

[0091] (3) information about a first triggering event in response to satisfaction of the first triggering event;

[0092] (4) information about a second triggering event in response to satisfaction of the second triggering event; or

[0093] (5) The time duration between the satisfaction timing of the first trigger event and the satisfaction timing of the second trigger event, for example, when both trigger events are satisfied.

[0094] In some embodiments, the first triggering event or the second triggering event may include at least one of the following: CondEvent A3; CondEvent A4; CondEvent A5; CondEvent B1; or CondEvent B2.

[0095] In some embodiments, the configuration information related to the CPAC process includes at least one of the following:

[0096] (1) A list of configured candidate PSCells for the CPAC process;

[0097] (2) one or two triggering events configured for a candidate PSCell in the list of configured candidate PSCells;

[0098] (3) an indication of whether the measured neighboring PSCell is a candidate PSCell; or

[0099] (4) One or more measurement configurations configured for the CPAC process In an embodiment, the one or more measurement configurations include measurement identifier (ID) information to be used for the CPAC process.

[0100] In some embodiments, the identification information associated with the CPAC process includes at least one of the following:

[0101] (1) The type of PSCell change operation performed during the CPAC process, or the type of CPC process;

[0102] (2) the type of PSCell addition operation performed during the CPAC process, or the type of CPA process;

[0103] (3) an indication for indicating that a PSCell change operation is to be performed during a CPAC procedure, or an indication for a CPC procedure;

[0104] (4) an indication for indicating that a PSCell addition operation is to be performed during a CPAC process, or an indication for a CPA process;

[0105] (5) an indication of whether the last PSCell change operation performed was a CPC operation; or

[0106] (6) An indication used to indicate whether the last PSCell addition operation performed was a CPA operation.

[0107] In some embodiments, the UE may transmit at least one of the following:

[0108] (1) An indication for indicating the occurrence of an SCG failure before the start of conditional reconfiguration execution toward a target PSCell;

[0109] (2) An indication for indicating the occurrence of an MCG failure before the start of conditional reconfiguration execution towards a target PSCell;

[0110] (3) an indication of the occurrence of a failure during execution of a conditional reconfiguration toward a target PSCell, or an indication of a CPAC execution failure; or

[0111] (4) An indication for indicating that RLF occurs in a candidate PSCell shortly after completion of conditional reconfiguration execution toward a target PSCell.

[0112] In some embodiments, the UE may transmit an indication indicating the UE's optional capability to store or transmit failure related information (i.e., CPAC failure related information). For example, in an embodiment of the present application, the UE is introduced to have an optional capability to store or report CPAC failure related information, and there are two potential options:

[0113] (1) Option 1: Optional with capability signaling. Even if the UE supports PSCell change or CPAC mechanism, storing or reporting CPAC failure related information is optional. This capability can be explicitly signaled by the UE to the network, that is, an optional UE capability for storing or reporting CPAC failure related information is introduced using signaling, for example, including an optional UE capability indication for storing or reporting CPAC failure related information in a UE Capability Information message.

[0114] (2) Option 2: Optional without capability signaling. Even if the UE supports PSCell change or CPAC mechanism, storing or reporting CPAC failure related information is optional, and the UE does not signal an explicit capability bit.

[0115] Figure 3 An exemplary flow chart illustrating receiving failure-related information according to some embodiments of the present application. Figure 3 The exemplary process 300 in the embodiment of the present invention may be performed by a MN (e.g., Figure 1 Although described with respect to a MN, it should be understood that other devices may be configured to perform similar Figure 3 The method of the method. Figure 3 In the context of "failure" or "SCG failure" means SCG RLF, failure of CPAC execution, failure of CPAC execution, or failure of SCG reconfiguration with synchronization. Figure 3 In some other embodiments, without departing from the spirit and scope of the present disclosure, only the following operations are performed: Figure 3 Operation 301 or operation 302 shown in .

[0116] In such Figure 3 In the exemplary process 300 shown in FIG. 1 , in operation 301, the MN receives a request from a UE (e.g., Figure 1 UE 101 shown in FIG. 101 ) or a network node to which the UE is connected or reestablished after a failure receives failure related information associated with the CPAC process, and the network node receives failure related information associated with the CPAC process from the UE. Failure related information associated with the CPAC process may also be referred to as "CPAC failure related information" or "SCG failure related information of the CPAC process", etc. The failure related information associated with the CPAC process may include at least one of the following:

[0117] (1) Time information associated with the CPAC process;

[0118] (2) Status information associated with one or two triggering events configured for the candidate PSCell of the CPAC process;

[0119] (3) configuration information related to the CPAC process; or

[0120] (4) Identification information associated with the CPAC process.

[0121] In operation 302, the MN may perform one of the following:

[0122] (1) Perform MRO analysis or optimization operations on parameters related to the CPAC process; and

[0123] (2) To SN (for example, Figure 1 Source SN 103 as shown in, or Figure 1 In some embodiments, the SN may be one of the following: the last serving SN of the UE; and the source SN of the UE in the CPAC process.

[0124] In some embodiments, the time information includes at least one of the following:

[0125] (1) The time elapsed between the start of the last conditional reconfiguration execution towards the target PSCell and the receipt of the latest conditional reconfiguration for the target PSCell, or the time elapsed between "CPAC execution" and "receipt of the latest conditional reconfiguration of the CPAC process";

[0126] (2) the time between the occurrence of an SCG failure and the receipt of the latest conditional reconfiguration of the CPAC procedure when the UE is connected to the source PSCell, for example, the SCG failure may be a RLF in the source SCG; or the time between the occurrence of an SCG failure in the source SCG and the receipt of the latest conditional reconfiguration of the CPAC procedure; or

[0127] (3) The time elapsed between the start of the last conditional reconfiguration execution toward the target PSCell and the SCG failure, or the time elapsed between "CPAC execution" and "failure of CPAC execution or occurrence of CPAC execution failure". For example, the SCG failure may be a RLF in the target SCG or a failure of CPAC execution or a CPAC execution failure. The failure of CPAC execution or the CPAC execution failure may include, for example, a failure of a PSCell change toward the target PSCell where the corresponding CPC execution is satisfied, or a failure of a PSCell addition toward the target PSCell where the corresponding CPA execution is satisfied, or a failure occurrence of a SCG reconfiguration with synchronization.

[0128] In some embodiments, the one or two triggering events include at least one of a triggering event (denoted as a “first triggering event” for simplicity) or another triggering event (denoted as a “second triggering event” for simplicity). In response to the initiation of the last conditional reconfiguration execution or the occurrence of an SCG failure, the state information includes at least one of the following:

[0129] (1) an indication for indicating whether a first trigger event is satisfied;

[0130] (2) an indication for indicating whether a second triggering event is satisfied;

[0131] (3) information about a first triggering event in response to satisfaction of the first triggering event;

[0132] (4) information about a second triggering event in response to satisfaction of the second triggering event; or

[0133] (5) The time duration between the satisfaction timing of the first trigger event and the satisfaction timing of the second trigger event, for example, when both trigger events are satisfied.

[0134] In some embodiments, the first triggering event or the second triggering event includes at least one of: CondEvent A3; CondEvent A4; CondEvent A5; CondEvent B1; or CondEvent B2.

[0135] In some embodiments, the configuration information includes at least one of the following:

[0136] (1) A list of configured candidate PSCells for the CPAC process;

[0137] (2) one or two triggering events configured for a candidate PSCell in the list of configured candidate PSCells;

[0138] (3) an indication of whether the measured neighboring PSCell is a candidate PSCell; or

[0139] (4) One or more measurement configurations configured for the CPAC process In some embodiments, the one or more measurement configurations include measurement ID information to be used for the CPAC process.

[0140] In some embodiments, the identification information associated with the CPAC process includes at least one of the following:

[0141] (1) The type of PSCell change operation performed during the CPAC process, or the type of CPC process;

[0142] (2) the type of PSCell addition operation performed during the CPAC process, or the type of CPA process;

[0143] (3) an indication for indicating that a PSCell change operation is to be performed during a CPAC procedure, or an indication for a CPC procedure;

[0144] (4) an indication for indicating that a PSCell addition operation is to be performed during a CPAC process, or an indication for a CPA process;

[0145] (5) an indication of whether the last PSCell change operation performed was a conditional PSCell change (CPC) operation; or

[0146] (6) An indication used to indicate whether the last PSCell add operation performed was a conditional PSCell add (CPA) operation.

[0147] In some embodiments, the MN may receive at least one of the following from the UE:

[0148] (1) An indication for indicating the occurrence of an SCG failure before the start of conditional reconfiguration execution toward a target PSCell;

[0149] (2) an indication of the occurrence of a failure during execution of a conditional reconfiguration toward a target PSCell, or an indication of a CPAC execution failure; or

[0150] (3) An indication for indicating that RLF occurs in a candidate PSCell shortly after completion of conditional reconfiguration execution toward a target PSCell.

[0151] In some embodiments, the MN may receive from the UE an indication indicating an optional capability of the UE to store or transmit failure related information.

[0152] In some embodiments, the MN may receive one of the following from the source SN: one or more CPAC configurations; and a container associated with the one or more CPAC configurations. The container may be represented by an information element (IE) (e.g., SN mobility information) or by an index. In an embodiment, the one or more CPAC configurations include at least one of the following:

[0153] (1) A list of configured candidate PSCells for the CPAC process;

[0154] (2) one or two triggering events configured for a candidate PSCell in the list of configured candidate PSCells;

[0155] (3) one or more SCG measurement configurations configured for the CPAC process; or

[0156] (4) An upper limit on the total number of configured candidate PSCells.

[0157] In some embodiments, one of the one or more CPAC configurations and containers is received in one of:

[0158] (1) S-NODE modification required messages;

[0159] (2) SGNB modifies the required message;

[0160] (3) S-NODE release request confirmation (ACK) message;

[0161] (4) SGNB release request confirmation (ACK) message;

[0162] (5) SN status transmission message; and

[0163] (6) Newly defined Xn or X2 messages.

[0164] In some embodiments, the MN may transmit one of one or more CPAC configurations and containers to the source SN or the last serving SN. In an embodiment, the one or more CPAC configurations or containers are transmitted in an SCG failure information report message or a newly defined Xn or X2 message. In an embodiment, after receiving the failure related information, the one or more CPAC configurations or containers are transmitted to the source SN or the last serving SN.

[0165] In some embodiments, the MN is a centralized unit (CU). The CU may transmit failure related information associated with the CPAC process to at least one distributed unit (DU) managed by the CU. Figure 5 The embodiments are described as follows.

[0166] Figure 4 A further exemplary flow chart illustrating receiving failure-related information according to some embodiments of the present application. Figure 4 The exemplary process 400 in the embodiment of the present invention may be performed by a source SN (e.g., Figure 1 Although described with respect to a source SN, it should be understood that other devices may be configured to perform similar Figure 4 The method of the method. Figure 4 In the context of "failure" or "SCG failure" means SCG RLF, failure of CPAC execution, failure of CPAC execution, or failure of SCG reconfiguration with synchronization. Figure 4 In some other embodiments, without departing from the spirit and scope of the present disclosure, only the following operations are performed: Figure 4 Operation 401 or operation 402 shown in .

[0167] In such Figure 4 In the exemplary process 400 shown in FIG. 4 , in operation 401, the source SN receives failure-related information associated with the CPAC process from the MN. The failure-related information associated with the CPAC process includes at least one of the following:

[0168] (1) Time information associated with the CPAC process;

[0169] (2) Status information associated with one or two triggering events configured for the candidate PSCell of the CPAC process;

[0170] (3) configuration information related to the CPAC process; or

[0171] (4) Identification information associated with the CPAC process.

[0172] In operation 402, the source SN performs a mobility robustness optimization (MRO) analysis or optimization operation on parameters related to the CPAC process.

[0173] In some embodiments, the time information includes at least one of the following:

[0174] (1) The time elapsed between the start of the last conditional reconfiguration execution towards the target PSCell and the receipt of the latest conditional reconfiguration for the target PSCell, or the time elapsed between "CPAC execution" and "receipt of the latest conditional reconfiguration of the CPAC process";

[0175] (2) the time elapsed between the occurrence of a secondary cell group (SCG) failure and the receipt of the latest conditional reconfiguration for the CPAC procedure when the user equipment (UE) is connected to the source PSCell, e.g., the SCG failure may be a RLF in the source SCG; or the time elapsed between "the occurrence of a SCG failure in the source SCG" and "the receipt of the latest conditional reconfiguration for the CPAC procedure"; or

[0176] (3) The time elapsed between the start of the last conditional reconfiguration execution toward the target PSCell and the SCG failure, or the time elapsed between "CPAC execution" and "failure of CPAC execution or occurrence of CPAC execution failure". For example, the SCG failure may be RLF in the target SCG or failure of CPAC execution or CPAC execution failure. The failure of CPAC execution or CPAC execution failure may include, for example, a failure of a PSCell change toward the target PSCell where the corresponding CPC execution is satisfied, or a failure of a PSCell addition toward the target PSCell where the corresponding CPA execution is satisfied, or a failure occurrence of a SCG reconfiguration with synchronization.

[0177] In some embodiments, the one or two triggering events include at least one of a triggering event (denoted as a “first triggering event” for simplicity) or another triggering event (denoted as a “second triggering event” for simplicity). In response to the initiation of the last conditional reconfiguration execution or the occurrence of an SCG failure, the state information includes at least one of the following:

[0178] (1) an indication for indicating whether a first trigger event is satisfied; an indication for indicating whether a second trigger event is satisfied;

[0179] (2) information about a first triggering event in response to satisfaction of the first triggering event;

[0180] (3) information about a second triggering event in response to satisfaction of the second triggering event; or

[0181] (4) The time duration between the satisfaction of the first trigger event and the satisfaction of the second trigger event, for example, when both trigger events are satisfied. Figure 2 , 3 In the embodiments of 4, the first or second trigger event may also be referred to as the first or second trigger condition, etc.

[0182] In some embodiments, the first triggering event or the second triggering event includes at least one of: CondEvent A3; CondEvent A4; CondEvent A5; CondEvent B1; or CondEvent B2.

[0183] In some embodiments, the configuration information related to the CPAC process includes at least one of the following:

[0184] (1) A list of configured candidate PSCells for the CPAC process;

[0185] (2) one or two triggering events configured for a candidate PSCell in the list of configured candidate PSCells;

[0186] (3) an indication of whether the measured neighboring PSCell is a candidate PSCell; or

[0187] (4) One or more measurement configurations configured for the CPAC process In some embodiments, the one or more measurement configurations include measurement identifier (ID) information to be used for the CPAC process.

[0188] In some embodiments, the identification information associated with the CPAC process includes at least one of the following:

[0189] (1) The type of PSCell change operation performed during the CPAC process, or the type of CPC process;

[0190] (2) the type of PSCell addition operation performed during the CPAC process, or the type of CPA process;

[0191] (3) an indication for indicating that a PSCell change operation is to be performed during a CPAC procedure, or an indication for a CPC procedure;

[0192] (4) an indication for indicating that a PSCell addition operation is to be performed during a CPAC process, or an indication for a CPA process;

[0193] (5) an indication of whether the last PSCell change operation performed was a conditional PSCell change (CPC) operation; or

[0194] (6) An indication used to indicate whether the last PSCell add operation performed was a conditional PSCell add (CPA) operation.

[0195] In some embodiments, the failure-related information includes at least one of the following:

[0196] (1) An indication for indicating the occurrence of an SCG failure before the start of conditional reconfiguration execution toward a target PSCell;

[0197] (2) an indication of the occurrence of a failure during execution of a conditional reconfiguration toward a target PSCell, or an indication of a CPAC execution failure; or

[0198] (3) An indication for indicating that RLF occurs in a candidate PSCell shortly after completion of conditional reconfiguration execution toward a target PSCell.

[0199] In some embodiments, the source SN may receive an indication from a user equipment (UE) indicating the occurrence of a master cell group (MCG) failure prior to the initiation of conditional reconfiguration execution towards a target PSCell.

[0200] In some embodiments, the source SN may transmit one of the following to the MN: one or more CPAC configurations; and containers associated with the one or more CPAC configurations. In an embodiment, the one or more CPAC configurations include at least one of the following:

[0201] (1) A list of configured candidate PSCells for the CPAC process;

[0202] (2) one or two triggering events configured for a candidate PSCell in the list of configured candidate PSCells;

[0203] (3) one or more SCG measurement configurations configured for the CPAC process; or

[0204] (4) An upper limit on the total number of configured candidate PSCells.

[0205] In some embodiments, one of the one or more CPAC configurations and containers is launched in one of the following:

[0206] (1) S-NODE modifies the required messages;

[0207] (2) SGNB modifies the required message;

[0208] (3) S-NODE release request ACK message;

[0209] (4) SGNB release request ACK message;

[0210] (5) SN status transmission message; and

[0211] (6) Newly defined Xn or X2 messages.

[0212] In some embodiments, the source SN may receive one of one or more CPAC configurations and containers from the MN. In an embodiment, the one or more CPAC configurations or containers are received in one of the following: an SCG failure information report message; and a newly defined Xn or X2 message.

[0213] In some embodiments, the source SN is a CU. The CU may transmit failure related information to at least one DU managed by the CU. Figure 5 The embodiments are described as follows.

[0214] The details described in all other embodiments of this application apply to Figures 2 to 4 The embodiments shown in any one of the embodiments. It should be understood by those skilled in the art that changes may be made without departing from the spirit and scope of the present disclosure. Figures 2 to 4 The sequence of operations in any of the exemplary processes 200 to 400 in the embodiment of the present invention may be eliminated or modified. Figures 2 to 4 Some of the operations in any of the exemplary processes 200 to 400 in.

[0215] The following text describes how Figures 2 to 4 Specific embodiments 1-1, 1-2 and 1-3 of the embodiments shown and described in the specification, wherein the UE and the network node (e.g., MN, source SN or target SN) perform the following operations.

[0216] Embodiment 1-1: The UE may store, record, record or generate time information and status information associated with a CPAC triggering event, or the UE may report time information and status information associated with a CPAC triggering event.

[0217] In Example 1-1, in the event of a CPAC execution failure, in order to enable the network to determine whether the CPAC execution conditions are properly configured, the UE needs to store or report the time elapsed between the CPAC execution toward the target PSCell (i.e., the execution of the CPAC process) and the timing when the corresponding latest CPAC configuration is received for the target PSCell. For example, if the time duration of this report is long, the network may understand that the CPAC configuration is inappropriate. The network may then trigger a traditional PSCell change process before CPAC execution, or may relax the CPAC execution conditions, for example, the network may reduce the reference signal received power (RSRP) trigger threshold or the reference signal received quality (RSRQ) trigger threshold or the signal to interference plus noise ratio (SINR) trigger threshold of the CPAC process, or the network may reduce the trigger time (TTT) value of the CPAC evaluation.

[0218] In embodiment 1-1, in the case where SCG failure occurs in the source SN before CPAC execution, in order to enable the network to decide whether the CPAC execution condition or the CPAC candidate PSCell is properly configured, the UE needs to store or report the time elapsed between "the occurrence of SCG failure in the source SCG" and "the timing when the latest CPAC configuration is received". For example, if the time duration of this report is long, the network can understand that the SCG failure may be caused by strict CPAC execution conditions, and then the network can relax the CPAC execution conditions.

[0219] In Embodiment 1-1, for time information, a new time IE (e.g., timeSinceCPACReconfig) may be introduced in, for example, an SCG failure information message or an RLF report. There may be the following two situations:

[0220] (1) In the event of a PSCell change failure or a PSCell addition failure during the CPAC process (i.e., a PSCell change or addition failure, or a CPAC execution failure, occurs when the UE attempts to access the target PSCell when it has a CPAC configuration), the UE may store, record, document or generate the time elapsed between "the start of the last conditional reconfiguration execution toward the target PSCell" and "the reception of the latest conditional reconfiguration for this target PSCell", that is, the time elapsed between "CPAC execution toward the target PSCell" and "the timing of receiving the corresponding latest CPAC configuration for the target PSCell".

[0221] (2) In the case where the UE experiences RLF in the source SCG after being configured with CPC configuration and before performing the CPC process (i.e., the RLF in the source PSCell occurs when it has CPC configuration), the UE may store, record, record or generate the time elapsed between "the occurrence of SCG failure in the source SCG" and "the receipt of the latest conditional reconfiguration of the CPC process when the UE is connected to the source PSCell".

[0222] In Example 1-1, there may be a situation where up to two trigger events or conditions are configured for a CPAC candidate PSCell. If two trigger events or conditions are configured for a CPAC candidate PSCell, CPAC execution is performed only when these two trigger events or conditions of the candidate PSCell are met. When a failure occurs (for example, CPAC execution failure in the target PSCell or RLF in the source SCG), this means that at least one trigger event or condition is not suitable. In order to let the network know more information for modifying the CPAC execution conditions, the following status information associated with the CPAC trigger event or condition may be stored at the moment of conditional reconfiguration execution or SCG radio link failure, and reported in a message, for example, an SCG failure information message or an RLF report:

[0223] (1) An indication of whether a triggering event (e.g., a first triggering event) of a CPAC candidate PSCell or a target PSCell is satisfied (e.g., CondEvent A3, A4, A5, B1, and / or B2);

[0224] (2) an indication of whether another triggering event (e.g., a second triggering event) of the CPAC candidate PSCell or the target PSCell is satisfied (i.e., CondEvent A3, A4, A5, B1, and / or B2);

[0225] (3) Information about the first triggering event: if the first triggering event of the CPAC candidate PSCell or the target PSCell is met, the firstTriggeredEvent IE is set to the execution condition or event that is first met in time (e.g., condFirstEvent);

[0226] (4) Information about the second triggering event, if the second triggering event of the CPAC candidate PSCell or the target PSCell is met, for example, then the firstTriggeredEvent IE is set to the execution condition or event that is met first in time (e.g., condSecondEvent); and / or

[0227] (5) The time duration between the satisfaction of the two triggering events or conditions configured for the CPAC candidate PSCell or target PSCell in which CPAC execution is triggered. The first or second triggering event may also be referred to as the first or second triggering condition, etc.

[0228] In addition, the UE may store or report the time elapsed between the start of the last conditional reconfiguration execution toward the target PSCell and the SCG failure. In 3GPP Release 17, the "timeSCGFailure IE" is introduced in the SCG Failure Information message to indicate the time elapsed from "the last execution of RRCR reconfiguration with reconfigurationWithSync of SCG" until "the occurrence of SCG failure". In Example 1-1, for the CPAC process, the timeSCGFailure IE in the SCG Failure Information message may be reused to indicate the time elapsed from "the last CPAC or conditional reconfiguration execution toward the target PSCell" until "the occurrence of SCG failure", that is, the time elapsed from "the last PSCell change performed toward the target PSCell" until "PSCell change failure or RLF occurs shortly after a successful PSCell change". Alternatively, in Example 1-1, a new IE in the SCG Failure Information message may be introduced to indicate the time elapsed from "the last CPAC or conditional reconfiguration execution toward the target PSCell" until "the occurrence of SCG failure".

[0229] In Embodiment 1-1, if it is a MN-initiated CPAC process, the MN may use the received time information and status information associated with the CPAC triggering event or condition for the purpose of MRO. In addition, the MN may send the time information and / or status information associated with the CPAC triggering event or condition to the last serving SN or source SN via a newly defined Xn or X2 message or an existing message (e.g., SCG FAILURE INFORMATION REPORT message), for example, for an SN-initiated CPAC process. Then, the last serving SN or source SN may use the received information for the purpose of MRO.

[0230] In Example 1-1, for the case where CPAC execution is successful, a new IE (e.g., timeSinceCPACReconfig) may be generated or reported in a successful PSCell change report (SPC-report). For example, the new IE may indicate the time elapsed between "the start of the last conditional reconfiguration execution toward the target PSCell" and "the receipt of the latest conditional reconfiguration of this target PSCell for the CPAC process." The time elapsed from "the last execution of RRCReconfiguration with reconfigurationWithSync for the PSCell" until "successful PSCell change", or the time elapsed between "the start of the last CPAC or conditional reconfiguration execution toward the target PSCell" and "successful PSCell change" may also be stored by the UE or reported, for example, via an SPC-report.

[0231] Embodiment 1-2: The UE may store or report CPAC-related configurations for MRO purposes.

[0232] Specifically, in Embodiment 1-2, in order to analyze whether the CPAC configuration is properly set, for example, whether the CPAC execution condition is properly configured, or whether the configured CPAC candidate PSCell (i.e., the candidate PSCell for the CPAC process) is suitable, it is beneficial to let the network know the configured CPAC configuration for MRO analysis, especially when the network does not have CPAC-related parameters, for example, when the context of the UE is released, or when the network is not involved in the CPAC process. There may be the following two solutions in Embodiment 1-2, namely, Solution 1 (UE-based solution) and Solution 2 (network-based solution).

[0233] Solution 1 refers to a UE-based solution. In Solution 1, the UE may store or report the latest configured CPAC configuration to the network. For example, a message sent by the UE to the network (e.g., an SCG failure information message or an RLF report) may include at least one of the following information:

[0234] (1) The most recently received CPAC execution conditions configured for any CPAC candidate PSCell (e.g., configurations associated with CondEventA3, A4, A5, B1 and / or B2, and / or TTT values), that is, one or two trigger events most recently received for any candidate PSCell in the list of configured candidate PSCells.

[0235] (2) The latest radio measurement result of the CPAC candidate PSCell. For example, the existing measResultSCG-Failure or measResultListNR or measResultNeighCells IE in the SCG Failure Information message or RLF report can be reused to indicate the latest radio measurement result.

[0236] (3) An indication for indicating whether the measured neighboring PSCell included in the measurement result is a CPAC candidate PSCell. For example, the existing measResultSCG-Failure or measResultListNR or measResultNeighCells IE or other IE in the SCG failure information message or RLF report may be reused to include the measurement result. The indication may be included in the IE to indicate whether the measured neighboring PSCell is configured as a CPAC candidate PSCell.

[0237] (4) A list of the latest configured CPAC candidate PSCells. For example, the list may include cell-related information of the latest configured CPAC candidate PSCells. The cell-related information may include a global cell identity and a tracking area code (TAC), for example, PLMN-Identity+CellIdentity+TAC; or the cell-related information may include a physical cell identity and a carrier frequency, for example, PCI+ARFCN. For example, some or all of the latest configured CPAC candidate PSCells may not be included in the measurement results. For CPAC candidate PSCells that are not included in the measurement results, for example, they are not included in the measResultSCG-Failure or measResultListNR or measResultNeighCells IE, another IE may be introduced to include its cell-related information.

[0238] (5) The latest measurement configuration, for example, the SCG measurement configuration of the CPAC process (for example, the measId to be used for the CPAC process).

[0239] In solution 1, if it is a MN-initiated CPAC process, the MN may use the received CPAC configuration for MRO purposes after receiving SCG failure-related information or failure-related information associated with the CPAC process. In addition, the MN may send the received CPAC configuration to the last serving SN or source SN via a newly defined Xn or X2 message or an existing message (e.g., SCG FAILURE INFORMATION REPORT message), for example, for an SN-initiated CPAC process. Then, when necessary, the last serving SN or source SN may use the received CPAC configuration for MRO analysis or optimization operations.

[0240] Solution 2 refers to a network-based solution. In Solution 2, in the event that an SCG failure occurs in the target PSCell shortly after successful CPAC execution, the CPAC configuration configured by the network cannot be reported by the UE because the UE releases the CPAC configuration after successful CPAC execution. On the other hand, the network may have released the context of the UE (e.g., including the CPAC configuration). In addition, there may be a situation where the context of the UE (e.g., the context of the UE associated with the source PSCell) is released in the MN when the MN receives information related to the SCG failure. Alternatively, there may be a situation where the context of the UE (e.g., the context of the UE associated with the source PSCell) is released in the source SN (i.e., S-SN) when the MN transmits information related to the SCG failure to the source SN. In order for the MN or the source SN to have sufficient CPAC configuration to analyze the failure, there may be the following two solutions, namely, Solution 2-1 and Solution 2-2.

[0241] Solution 2-1: Optionally, the source SN may send a container to the MN via an existing message (e.g., S-NODE modification required message, SGNB modification required message, S-NODE release request ACK message, SGNB release request ACK message, or SN status transfer message) or via a newly defined Xn or X2 message (e.g., reusing an existing SN mobility information IE to represent the container, or using an index to represent the container). The SN mobility information IE is used to describe information related to the CPAC process. The source SN may provide a container (e.g., SN mobility information or an index) to enable later analysis of the cause of the SCG failure.

[0242] In Solution 2-1, in a specific implementation, a container (e.g., SN mobility information or index) may be used to map or match the UE's context (e.g., parameters of the CPAC, including at least the latest configured CPAC execution conditions for each accepted CPAC candidate PSCell, the corresponding latest SCG measurement configuration of the CPAC (e.g., measId to be used for the CPAC), a list of configured CPAC candidate PSCells accepted by the candidate target SN, and / or an upper limit on the number of PSCells).

[0243] In solution 2-1, after the MN receives the SCG failure related information or the failure related information associated with the CPAC process or the SCG failure information message, in addition to the SCG failure related information (e.g., which is included in the SCG failure information message or the RLF report), the MN may send a container (e.g., SN mobility information or index) back to the S-SN, for example, via a newly defined Xn or X2 message or an existing SCG FAILURE INFORMATION REPORT message. Then, based on the container (e.g., SN mobility information or index), the S-SN may analyze the root cause and modify the CPAC related parameters if necessary.

[0244] Solution 2-2: Optionally, the source SN may send the following information to the MN via an existing message (e.g., S-NODE modification required message, SGNB modification required message, S-NODE release request ACK message, SGNB release request ACK message, or SN status transfer message) or via a newly defined Xn or X2 message:

[0245] (1) A list of the most recently configured CPAC candidate PSCells, for example, which is accepted by the candidate target SN; for example, the list may include cell-related information of the most recently configured CPAC candidate PSCells; and the cell-related information may include a global cell identity and a tracking area code (TAC), for example, PLMN-Identity+CellIdentity+TAC; or the cell-related information may include a physical cell identity and a carrier frequency, for example, PCI+ARFCN;

[0246] (2) the latest CPAC configuration configured for a CPAC candidate PSCell in the list of the latest configured CPAC candidate PSCells; for example, the latest CPAC configuration may include the latest configured CPAC execution conditions configured for any CPAC candidate PSCell (e.g., configurations associated with CondEvent A3, A4, A5, B1 and / or B2 configurations, and / or TTT values);

[0247] (3) the latest SCG measurement configuration for CPAC (e.g., the measId to be used for CPAC); and / or

[0248] (4) The upper limit of the number of PSCells.

[0249] In solution 2-2, after the MN receives the SCG failure related information or the failure related information associated with the CPAC process or the SCG failure information message, in addition to the SCG failure related information (e.g., which is included in the SCG failure information message or the RLF report), the MN may also send the following information to the source SN, for example, via a newly defined Xn or X2 message or an existing SCG failure information report message:

[0250] (1) A list of the most recently configured CPAC candidate PSCells, for example, which is accepted by the candidate target SN; for example, the list may include cell-related information of the most recently configured CPAC candidate PSCells; and the cell-related information may include a global cell identity and a tracking area code (TAC), for example, PLMN-Identity+CellIdentity+TAC; or the cell-related information may include a physical cell identity and a carrier frequency, for example, PCI+ARFCN;

[0251] (2) the latest CPAC configuration configured for a CPAC candidate PSCell in the list of the latest configured CPAC candidate PSCells; for example, the latest CPAC configuration may include the latest configured CPAC execution conditions configured for any CPAC candidate PSCell (e.g., configurations associated with CondEvent A3, A4, A5, B1 and / or B2 configurations, and / or TTT values);

[0252] (3) the latest SCG measurement configuration for CPAC (e.g., the measId to be used for CPAC); and / or

[0253] (4) The upper limit of the number of PSCells.

[0254] Then, based on the above information received from the MN, the source SN can analyze the root cause and modify the CPAC related parameters if necessary.

[0255] Embodiment 1-3: The UE may store, record, log or generate identification information for MRO purposes, or the UE may report identification information.

[0256] Specifically, in Embodiments 1-3, considering that the conventional PSCell change or addition process has a different configuration from the CPAC process, it is beneficial for the network to know the type of PSCell change or addition when performing MRO analysis or optimization operations. For example, in the case where an SCG failure occurs in the target PSCell shortly after successful CPAC execution, since the UE releases the CPAC configuration after successful CPAC execution, the UE cannot report any CPAC-specific parameters to the network. Therefore, the UE may store, record, document, or generate the type of the PSCell change or addition process, for example, the process in which the SCG failure occurs is a CPAC process, and the UE may then report this information. The UE may also store, record, document, or generate an indication of the type of the PSCell change or addition process, for example, an indication of whether an SCG failure occurs during the CPAC process, and the UE may then report this information.

[0257] In embodiments 1-3, in order to distinguish an SCG failure in a normal PSCell change process from an SCG failure in a CPC process (for example, failure means that a PSCell change failure or RLF occurs in the target PSCell shortly after a successful PSCell change), the UE may store, record, document, or generate the type of PSCell change when a failure occurs, or the UE may report the type of PSCell change. For example, the type of the PSCell change process is included in an SCG failure information message or an RLF report, for example, an IE used to indicate the CPC process type is included in the SCG failure information message or the RLF report. In another solution, an explicit indication is added to the SCG failure information message or the RLF report to indicate whether the last PSCell change performed before the SCG failure in the target PSCell was a CPC process, or to indicate whether the last PSCell change performed before the PSCell change failure was a CPC process, for example, an indication indicating whether the SCG failure occurred in the CPC process is included in the SCG failure information message or the RLF report.

[0258] In embodiments 1-3, in order to distinguish between an SCG failure in a normal PSCell addition process and an SCG failure in a CPA process, the UE may store, record, document or generate the type of PSCell addition when a failure occurs, for example, the type of the PSCell addition process is included in an SCG failure information message or an RLF report, or an IE used to indicate the type of CPA process is included in an SCG failure information message or an RLF report. The UE may then report this information. In another solution, an explicit indication is added to the SCG failure information message or the RLF report to indicate whether the last PSCell addition performed before the SCG failure was a CPA process, for example, an indication indicating whether the SCG failure occurred in a CPA process is included in an SCG failure information message or an RLF report. The UE may then report this information.

[0259] Some embodiments of the present application relate to storing or reporting information of failure situations in a CPAC process. Specifically, during a CPAC process, the following failure situations, namely, situations 1 to 4, may be considered for MRO purposes.

[0260] In case 1, the source SCG failure occurs before CPAC is executed. In case 1, the UE stores or reports an indication that the SCG failure occurs before CPAC is executed. The UE may also store or report the time elapsed from "receipt of the latest conditional reconfiguration of the CPAC process" to "occurrence of the source SCG failure", the status information associated with the CPAC triggering event or condition mentioned in Example 1-1, the CPAC-related configuration mentioned in Solution 1 in Example 1-2, and / or the identification information mentioned in Example 1-3.

[0261] In case 1, when the MN is available, the UE may send the above-mentioned SCG failure related information to the MN, for example, via an SCG failure information message.

[0262] In case 1, when MCG failure occurs when the source SCG fails, the UE may send SCG and MCG failure-related information (for example, including the above-mentioned SCG failure-related information, the time from "occurrence of SCG failure" to "occurrence of MCG failure", and the time from "occurrence of MCG failure" to "UE reporting failure-related information") to a third-party node where the UE is reconnected or reestablished, for example, via an RLF report.

[0263] In case 2, a CPAC execution failure occurs. In case 2, the UE stores or reports an indication indicating a CPAC execution failure. The UE may also store or report the time elapsed between "the start of the last conditional reconfiguration execution toward the target PSCell" and "the reception of the latest conditional reconfiguration for the target PSCell", the time elapsed between "the start of the last conditional reconfiguration execution toward the target PSCell" and "the occurrence of a CPAC execution failure", the status information associated with the CPAC triggering event or condition mentioned in Example 1-1, the CPAC-related configuration mentioned in Solution 1 in Example 1-2, and / or the identification information mentioned in Example 1-3.

[0264] In case 2, when the MN is available, the UE may send the above-mentioned SCG failure related information to the MN, for example, via an SCG failure information message.

[0265] In situation 2, when MCG failure occurs when CPAC execution fails, the UE may send SCG and MCG failure related information (for example, including the above-mentioned SCG failure related information, the time elapsed from CPAC execution failure to MCG failure, and the time elapsed from MCG failure to reporting failure related information), for example, via an RLF report to a third-party node where the UE is reconnected or reestablished.

[0266] In case 3, SCG failure occurs shortly after successful CPAC execution. In case 3, the UE stores or reports an indication of RLF occurring in the target PSCell shortly after CPAC execution. The UE may also store or report the type of PSCell change / addition process (i.e., it is a CPAC process), the time elapsed between "the start of the last conditional reconfiguration execution toward the target PSCell" and "the reception of the latest conditional reconfiguration for the target PSCell", and the time elapsed from "the start of the last conditional reconfiguration execution toward the target PSCell" to "the occurrence of RLF in the target SCG", the status information associated with the CPAC triggering event or condition mentioned in Example 1-1, and the identification information mentioned in Example 1-3. For CPAC-related configurations, Solution 2 (network-based solution) mentioned in Example 1-2 may be used.

[0267] In case 3, when the MN is available, the UE may send the above-mentioned SCG failure related information to the MN, for example, via an SCG failure information message.

[0268] In case 3, when MCG failure occurs when SCG fails shortly after successful CPAC execution, the UE may send SCG and MCG failure-related information (e.g., including the above-mentioned SCG failure-related information, the time elapsed from "occurrence of RLF in the target SCG" to "occurrence of MCG failure", and the time elapsed from "occurrence of MCG failure" to "UE reporting failure-related information") to a third-party node where the UE is reconnected or reestablished, for example, via an RLF report.

[0269] In case 4, MCG failure occurs before CPAC is executed. When MCG fails, the conditional reconfiguration evaluation of the CPAC process can be stopped. In case 4, the UE can store or report an indication of MCG failure before CPAC is executed. The UE can also store or report the time from the receipt of the latest conditional reconfiguration of CPAC to the MCG failure, the status information associated with the CPAC triggering event / condition mentioned in Example 1-1, the CPAC related configuration mentioned in Example 1-2, and the identification information mentioned in Example 1-3.

[0270] In case 4, when the source SN is available, the UE may send the above-mentioned MCG failure related information to the source SN, for example, via an MCG failure information message.

[0271] In situation 4, when SCG failure occurs when MCG fails, the UE may send SCG and MCG failure-related information (for example, including the above-mentioned MCG failure information, the time elapsed from MCG failure to SCG failure, and the time elapsed from SCG failure to reporting failure-related information), for example, via an RLF report to a third-party node where the UE is reconnected or reestablished.

[0272] In case 5, MCG failure occurs during CPAC execution. In case 5, there may be the following options, Option A and Option B.

[0273] In option A of case 5, when MCG failure occurs during CPAC execution, the UE may continue CPAC execution. Specifically, if CPAC is successful, the UE may send an MCG failure information message to the T-SN, for example, via SRB3 or a separate SRB1. The MCG failure information message may include the time elapsed from "receipt of the latest conditional reconfiguration of the CPAC process" to "CPAC execution", the time elapsed from "CPAC execution" to "occurrence of MCG failure", the time elapsed from "occurrence of MCG failure" to "CPAC execution success", and / or the time elapsed from "CPAC execution success" to "UE reports MCG failure information message". The MCG failure information message may also include status information associated with the CPAC triggering event or condition mentioned in Example 1-1, the CPAC-related configuration mentioned in Example 1-2, an indication for indicating MCG failure during the CPAC execution phase, and / or an indication for indicating the success of the CPAC process after the MCG failure.

[0274] In option A of case 5, if the CPAC process fails, the UE may send MCG and SCG failure related information to the third-party node where the UE reconnects or reestablishes. For example, the MCG and SCG failure related information may include the time elapsed from "receipt of the latest conditional reconfiguration of CPAC" to "CPAC execution", the time elapsed from "CPAC execution" to "MCG failure occurrence", the time elapsed from "MCG failure occurrence" to "CPAC execution failure occurrence", and / or the time elapsed from "CPAC execution failure occurrence" to "UE reports MCG and SCG failure related information". In addition, the MCG and SCG failure related information may include status information associated with the CPAC triggering event or condition mentioned in Example 1-1, the CPAC related configuration mentioned in Example 1-2, the identification information mentioned in Example 1-3, an indication of MCG failure during the CPAC execution phase, and / or an indication of CPAC process failure after MCG failure.

[0275] In option B of case 5, when an MCG failure occurs during CPAC execution, the UE may stop CPAC execution and perform RRC reconstruction or establishment. Specifically, the UE may send MCG failure-related information to a third-party node where the UE reconnects or reconstructs via an RLF report. For example, the MCG failure-related information may include the time elapsed from "receipt of the latest conditional reconfiguration of the CPAC process" to "CPAC execution", the time elapsed from "CPAC execution" to "occurrence of MCG failure", and / or the time elapsed from "occurrence of MCG failure" to "UE reporting MCG failure-related information". MCG failure-related information may also include status information associated with the CPAC triggering event or condition mentioned in Example 1-1, the CPAC-related configuration mentioned in Example 1-2, the identification information mentioned in Example 1-3, an indication for indicating an MCG failure during the CPAC execution phase, and / or an indication for indicating the stop of the CPAC process.

[0276] Figure 5 An exemplary flow chart illustrating the exchange of CPAC failure information in a network according to some embodiments of the present application. In a CU-DU split architecture, the CU and / or DU may perform MRO analysis or optimization operations based on received failure-related information or CPAC failure-related information associated with a CPAC process. The exemplary process 500 refers to a process for signaling CPAC failure-related information between RAN nodes (e.g., from a gNB-CU to a gNB-DU).

[0277] In operation 511, UE 501 having stored failure-related information associated with the CPAC process (which may also be referred to as CPAC failure-related information) and / or MCG failure-related information connects to a cell in a BS (e.g., MN 504). UE 501 may signal MN 504 as follows: Figures 2 to 4 UE 501 may send a message including the following to MN 504: Figures 2 to 4 If the MN 504 has a CU-DU separation architecture, the CU of the MN 504 may also send an F1 message (e.g., an access and mobility indication message) to at least one DU of the MN 504 managed by the CU of the MN 504, which includes the following: Figures 2 to 4Based on the received CPAC failure related information and / or MCG failure related information, the CU and / or DU of MN 504 should take it into consideration to optimize the CPAC process when necessary, for example, to decide whether or how to modify the CPAC related configuration (for example, RSRP or RSRQ or SINR thresholds for CPAC execution conditions, and / or TTT for CPAC evaluation), for example, for the CPAC process initiated by the MN.

[0278] In operation 512, the NG-RAN node may exchange CPAC failure related information for the CPAC process via an SCG failure information report message. For example, in operation 512, the MN 504 sends an Xn or X2 message (e.g., an SCG failure information report message) to a CU of another BS (e.g., the SN CU 503). For example, for an SN-initiated PSCell change or CPAC process, the SN may be the last serving SN or the source SN. The SCG failure information report message includes the following information: Figures 2 to 4 CPAC failure related information mentioned in the embodiments.

[0279] In operation 513, based on the received CPAC failure-related information, the SN CU 503 may take it into account to optimize the CPAC process when necessary, for example, to decide whether or how to modify the CPAC-related configuration (e.g., RSRP or RSRQ or SINR thresholds for CPAC execution conditions, and / or TTT for CPAC evaluation), for example, in the case where the failure is due to CPAC execution failure.

[0280] In operation 514, the SN CU 503 sends an F1 message (eg, access and mobility indication message) to at least one DU (eg, the SN DU 502 managed by the SN CU 503), including: Figures 2 to 4 For example, for the case where UE 501 experiences a random access problem indication from SCG MAC in SN DU 502 while timer T304 is running for SCG (i.e., when the failure type is randomAccessProblem included in an SCG Failure Information message or an SCG Failure Information Report message), SN CU 503 may send an F1 message (e.g., an Access and Mobility Indication message) to SN DU 502.

[0281] In operation 515, based on the received CPAC failure related information, the SN DU 502 should take it into consideration to optimize the CPAC process when necessary, for example, when the SN DU 502 is the DU of the target BS for CPAC execution, decide whether or how to modify the RACH configuration toward the target PSCell managed by the SN DU 502.

[0282] Figure 6 An exemplary block diagram illustrating an apparatus 600 for a CPAC process according to some embodiments of the present application.

[0283] like Figure 6 , the apparatus 600 may include at least one non-transitory computer-readable medium 602, at least one receiving circuit system 604, at least one transmitting circuit system 606, and at least one processor 608 coupled to the non-transitory computer-readable medium 602, the receiving circuit system 604, and the transmitting circuit system 606. The at least one processor 608 may be a CPU, a DSP, a microprocessor, etc. The apparatus 600 may be a network node (e.g., a MN or SN) configured to perform the methods described above or the like.

[0284] Although in this figure, elements such as at least one processor 608, receive circuitry 604, and transmit circuitry 606 are described in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present application, receive circuitry 604 and transmit circuitry 606 may be combined into a single device, such as a transceiver. In certain embodiments of the present application, apparatus 600 may further include an input device, a memory, and / or other components.

[0285] In some embodiments of the present application, the non-transitory computer-readable medium 602 may have computer-executable instructions stored thereon to cause the processor to implement the method for a network node (e.g., UE, MN, or SN) as described or illustrated above. For example, when executed, the computer-executable instructions cause the processor 608 to interact with the receiving circuit system 604 and the transmitting circuit system 606 to perform the method for a network node (e.g., UE, MN, or SN) as described or illustrated above.

[0286] Figure 7 A further exemplary block diagram illustrating an apparatus 700 for a CPC process according to some embodiments of the present application is shown. Figure 7, the device 700 (e.g., UE, MN, or SN) may include at least one processor 702 and at least one transceiver 704 coupled to the at least one processor 702. The transceiver 704 may include at least one separate receiving circuit system 706 and transmitting circuit system 708, or at least one integrated receiving circuit system 706 and transmitting circuit system 708. The at least one processor 702 may be a CPU, a DSP, a microprocessor, etc.

[0287] According to some other embodiments of the present application, when the device 700 is a UE, the processor 702 may be configured to perform at least one of the following: storing failure-related information associated with a conditional primary auxiliary cell group cell (PSCell) addition or change (CPAC) process, wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; status information associated with one or two trigger events configured for a candidate PSCell of the CPAC process; configuration information associated with the CPAC process; or identification information associated with the CPAC process; or transmitting the failure-related information to a network via the transceiver 704.

[0288] According to some embodiments of the present application, when the device 700 is an MN, the processor 702 is configured to perform at least one of the following: receiving failure-related information associated with a conditional primary auxiliary cell group (PSCell) addition or change (CPAC) process from a user equipment (UE) via the transceiver 704, wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; status information associated with one or two trigger events configured for a candidate PSCell of the CPAC process; configuration information related to the CPAC process; or identification information associated with the CPAC process; performing mobility robustness optimization (MRO) analysis or optimization operations on parameters related to the CPAC process; or transmitting the failure-related information to a secondary node (SN) via the transceiver 704.

[0289] According to some embodiments of the present application, when the device 700 is a source SN, the processor 702 is configured to perform at least one of the following: receiving failure-related information associated with a conditional primary auxiliary cell group (PSCell) addition or change (CPAC) process from a master node (MN) via the transceiver 704, wherein the failure-related information includes at least one of the following: time information associated with the CPAC process; status information associated with one or two trigger events configured for a candidate PSCell of the CPAC process; configuration information related to the CPAC process; or identification information associated with the CPAC process; or performing mobility robustness optimization (MRO) analysis or optimization operations on parameters related to the CPAC process.

[0290] The method of the present disclosure can be implemented on a programmed processor. However, the controller, flow chart and module can also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit components, an integrated circuit, a hardware electronic or logic circuit (such as a discrete element circuit), a programmable logic device, etc. In general, any device with a finite state machine capable of implementing the flow chart shown in the figure can be used to implement the processing functions of the present disclosure.

[0291] Although the present disclosure has been described with its specific embodiments, it is apparent that many alternatives, modifications and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added or replaced in other embodiments. In addition, all elements of each figure are not necessarily required for the operation of the disclosed embodiments. For example, a person of ordinary skill in the art will be able to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure as described herein are intended to be illustrative, not restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0292] In this document, the term "includes / including" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment comprising a series of elements not only includes the elements, but also includes other elements that are not clearly listed or inherent to such processes, methods, articles or equipment. In the absence of more constraints, the elements starting with "a / an" or the like do not exclude the presence of additional identical elements in the process, method, article or equipment comprising the elements. In addition, the term "another" is defined as at least the second or more. The term "having" and the like as used herein are defined as "including". For example, the expression of "A and / or B" or "at least one of A and B" may include any and all combinations of words listed together with the expression. For example, the expression "A and / or B" or "at least one of A and B" may include A, B or both A and B. The wording "first", "second" or the like is only used to clearly illustrate the embodiments of the present application, and is not used to limit the substantive content of the present application.

Claims

1. A user equipment UE, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to perform at least one of: Storing failure related information associated with a conditional primary secondary cell group cell PSCell addition or change CPAC process, wherein the failure related information includes at least one of the following: time information associated with the CPAC process; Status information associated with one or two triggering events configured for the candidate PSCell of the CPAC process; Configuration information related to the CPAC process; or Identification information associated with the CPAC process; or The failure-related information is transmitted to a network via the transceiver.

2. The UE according to claim 1, wherein the time information comprises at least one of the following: the time elapsed between the start of the last conditional reconfiguration execution towards a target PSCell and the receipt of the latest conditional reconfiguration for said target PSCell; the time elapsed between the occurrence of a secondary cell group (SCG) failure when the UE was connected to a source PSCell and the reception of the latest conditional reconfiguration for the CPAC procedure; or The time elapsed between the initiation of the last conditional reconfiguration execution towards the target PSCell and the SCG failure.

3. The UE according to claim 2, wherein the one or two triggering events include at least one of a first triggering event or a second triggering event, and wherein, In response to the initiation of the last conditional reconfiguration execution or the occurrence of the SCG failure, the status information includes at least one of the following: an indication for indicating whether the first triggering event is satisfied; an indication for indicating whether the second triggering event is satisfied; information regarding the first triggering event in response to satisfaction of the first triggering event; information regarding the second triggering event in response to satisfaction of the second triggering event; or The time duration between the satisfaction timing of the first triggering event and the satisfaction timing of the second triggering event.

4. The UE according to claim 1, wherein the configuration information comprises at least one of the following: a list of configured candidate PSCells for the CPAC process; one or two triggering events configured for a candidate PSCell in the list of configured candidate PSCells; An indication for indicating whether the measured neighboring PSCell is the candidate PSCell; or One or more measurement configurations configured for the CPAC process.

5. The UE according to claim 1, wherein the identification information includes at least one of the following: the type of PSCell change operation performed during the CPAC process; the type of PSCell add operation performed during the CPAC process; An instruction for instructing to perform the PSCell change operation during the CPAC process; An instruction for instructing to perform the PSCell addition operation during the CPAC process; an indication of whether the last PSCell change operation performed was a conditional PSCell change CPC operation; or An indication used to indicate whether the last performed PSCell add operation was a conditional PSCell add CPA operation.

6. The UE of claim 1, wherein the processor of the UE is configured to transmit, via the transceiver, at least one of: An indication for indicating the occurrence of an SCG failure prior to the initiation of conditional reconfiguration execution towards a target PSCell; An indication for indicating the occurrence of a master cell group MCG failure before the initiation of the conditional reconfiguration execution towards the target PSCell; an indication for indicating the occurrence of a failure during execution of said conditional reconfiguration towards said target PSCell; or An indication indicating that a RLF occurs in the candidate PSCell shortly after completion of execution of the conditional reconfiguration toward the target PSCell.

7. The UE of claim 1, wherein the processor of the UE is configured to transmit, via the transceiver, an indication indicating an optional capability of the UE to store or transmit the failure-related information.

8. A master node MN, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to perform at least one of: Receiving, via the transceiver, failure related information associated with a conditional primary secondary cell group (PSCell) addition or change (CPAC) procedure from a user equipment (UE), wherein the failure related information includes at least one of the following: time information associated with the CPAC process; Status information associated with one or two triggering events configured for the candidate PSCell of the CPAC process; Configuration information related to the CPAC process; or Identification information associated with the CPAC process; performing a mobility robustness optimization (MRO) analysis or optimization operation on parameters associated with the CPAC process; or The failure related information is transmitted to a secondary node SN via the transceiver.

9. The MN according to claim 8, wherein the time information includes at least one of the following: the time elapsed between the start of the last conditional reconfiguration execution towards a target PSCell and the receipt of the latest conditional reconfiguration for said target PSCell; the time elapsed between the occurrence of a secondary cell group (SCG) failure when the UE was connected to a source PSCell and the reception of the latest conditional reconfiguration for the CPAC procedure; or The time elapsed between the initiation of the last conditional reconfiguration execution towards the target PSCell and the SCG failure.

10. The MN according to claim 9, wherein the one or two triggering events include at least one of a first triggering event or a second triggering event, and wherein, In response to the initiation of the last conditional reconfiguration execution or the occurrence of the SCG failure, the status information includes at least one of the following: an indication for indicating whether the first triggering event is satisfied; an indication for indicating whether the second triggering event is satisfied; information regarding the first triggering event in response to satisfaction of the first triggering event; information regarding the second triggering event in response to satisfaction of the second triggering event; or The time duration between the satisfaction timing of the first triggering event and the satisfaction timing of the second triggering event.

11. The MN according to claim 8, wherein the configuration information includes at least one of the following: a list of configured candidate PSCells for the CPAC process; one or two triggering events configured for a candidate PSCell in the list of configured candidate PSCells; An indication for indicating whether the measured neighboring PSCell is the candidate PSCell; or One or more measurement configurations configured for the CPAC process.

12. The MN of claim 8, wherein the processor of the MN is configured to receive from the SN via the transceiver one of: One or more CPAC configurations; and A container associated with the one or more CPAC configurations.

13. The MN of claim 12, wherein the one or more CPAC configurations include at least one of: a list of configured candidate PSCells for the CPAC process; one or two triggering events configured for a candidate PSCell in the list of configured candidate PSCells; one or more SCG measurement configurations configured for the CPAC process; or The upper limit of the total number of configured candidate PSCells.

14. The MN of claim 12, wherein the processor of the MN is configured to transmit the one of the one or more CPAC configurations and the container to the SN via the transceiver.

15. A source auxiliary node SN, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to perform at least one of: Receiving, via the transceiver, failure related information associated with a conditional primary secondary cell group PSCell addition or change CPAC process from a master node MN, wherein the failure related information includes at least one of the following: time information associated with the CPAC process; Status information associated with one or two triggering events configured for the candidate PSCell of the CPAC process; Configuration information related to the CPAC process; or Identification information associated with the CPAC process; or A mobility robustness optimization (MRO) analysis or optimization operation is performed on parameters related to the CPAC process.

Images