Method and apparatus for MRO mechanism for pcell change with pscell change program

Abstract

Embodiments of the present application relate to methods and apparatus for a mobility robustness optimization (MRO) mechanism for primary cell (PCell) change with a primary secondary cell (PSCell) change procedure. In accordance with an embodiment of the present application, a source master node (MN) includes a transceiver, and a processor coupled to the transceiver; and the processor configured to transmit, via the transceiver, a configuration to a user equipment (UE), wherein the configuration is configured to store or report one of: a successful handover report (SHR) and a successful PSCell change (SPC) report; and a first report comprising information on successful completion of a PCell change with a PSCell change procedure, and wherein the configuration comprises at least one of: a first configuration for a set of trigger conditions associated with a primary cell group (MCG); or a second configuration for a set of trigger conditions associated with a secondary cell group (SCG).

Description

Technical Field

[0001] Embodiments of the present application generally relate to methods and apparatus for a mobility robustness optimization (MRO) mechanism for a primary cell (PCell) change with a primary secondary cell (PSCell) change procedure. Background Art

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

[0003] In general, a PCell change with a PSCell change procedure may occur in any MR-DC scenario, including NR-NR DC, EN-DC, NGEN-DC, and NE-DC. The PCell change with a PSCell change procedure may be a legacy PCell change with a legacy PSCell change procedure, or a legacy PCell change with a conditional PSCell addition or change (CPAC) procedure, or a conditional PCell change with a legacy PSCell change procedure, or a conditional PCell change with a CPAC procedure. In the PCell change with a PSCell change procedure, the PCell change includes an inter-MN PCell change and / or an intra-MN PCell change, and the PSCell change includes an inter-SN PSCell change and / or an intra-SN PSCell change. For example, a PCell change with a PSCell change procedure may be performed in an MR-DC with a 5GC, such as an inter-MN handover with an MN-initiated SN change procedure as defined in 3GPP TS 37.340.

[0004] Currently, in the 3GPP LTE system or the 5G system, details on the MRO mechanism for PCell change with PSCell change procedure have not been discussed. Summary of the invention

[0005] Some embodiments of the present application provide a source master node (MN). The source MN includes a transceiver, and a processor coupled to the transceiver; and the processor is configured to transmit a configuration to a user equipment (UE) via the transceiver, wherein the configuration is used to store or report one of the following: a successful handover report (SHR) and a successful primary secondary cell (PSCell) change (SPC) report; and a first report including information about the successful completion of a primary cell (PCell) change with a PSCell change procedure, and wherein the configuration includes at least one of the following: a first configuration for a set of trigger conditions associated with a primary cell group (MCG); or a second configuration for a set of trigger conditions associated with a secondary cell group (SCG).

[0006] In some embodiments, the SHR and the SPC report are two separate reports. In an embodiment, the SHR includes information related to a successful PCell change, and the SPC report includes information related to a successful PSCell change. In some other embodiments, the SHR includes the SPC report, i.e., the SPC report is part of the SHR. In an embodiment, the SHR includes both information related to a successful PCell change and information related to a successful PSCell change.

[0007] In some embodiments, the set of trigger conditions associated with the MCG includes at least one of: one or more trigger conditions for the SHR; or one or more trigger conditions for the first report.

[0008] In some embodiments, the set of trigger conditions associated with the SCG includes at least one of: one or more trigger conditions of the SPC report; or one or more trigger conditions of the first report.

[0009] In some embodiments, the configuration includes at least one of: one or more common trigger thresholds configured for both the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG; or one or more trigger thresholds configured separately for the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG.

[0010] In some embodiments, the processor of the source MN is configured to transmit an explicit or implicit indication to the UE via the transceiver to indicate that the one or more common trigger thresholds are configured for both the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG.

[0011] In some embodiments, the configuration includes at least one of the following: a threshold value related to timer T310 of the source PCell; a threshold value related to timer T310 of the source PSCell; a common threshold value related to timer T310 of the source PCell and the source PSCell; a threshold value related to timer T312 associated with the measurement identifier of the target PCell; a threshold value related to timer T312 associated with the measurement identifier of the target PSCell; a common threshold value related to timer T312 associated with the measurement identifier of the target PCell and the measurement identifier of the target PSCell; a threshold value related to timer T304 of the target PCell; a threshold value related to timer T304 of the target PSCell; or a common threshold value related to timer T304 of the target PCell and the target PSCell.

[0012] In some embodiments, the processor of the source MN is configured to receive a handover (HO) request acknowledgement (ACK) message including the configuration from the target MN via the transceiver.

[0013] In some embodiments, the processor of the source MN is configured to receive a first indication from a target MN via the transceiver, and the first indication indicates that the second configuration for the set of trigger conditions associated with the SCG needs to be configured.

[0014] In some embodiments, the processor of the source MN is configured to perform at least one of: generating the second configuration for the set of trigger conditions associated with the SCG; or transmitting a second indication to a source secondary node (SN) via the transceiver, wherein the second indication indicates that the source SN needs to configure the second configuration for the set of trigger conditions associated with the SCG.

[0015] In some embodiments, the processor of the source MN is configured to receive an SN release request confirmation (ACK) message or an SgNB release request ACK message from the source SN via the transceiver, wherein the SN release request ACK information or the SgNB release request ACK signal includes the second configuration.

[0016] In some embodiments, the processor of the source MN is configured to receive at least one of the following from the target MN via the transceiver: a cell radio network temporary identifier (C-RNTI) of the target PCell; an indication indicating that the SHR and the SPC report are related to the same PCell change with a PSCell change procedure; or first time information related to at least one of the SHR or the SPC report.

[0017] In some embodiments, the processor of the source MN is configured to receive at least one of the following from the target MN via the transceiver: a cell radio network temporary identifier (C-RNTI) of the target PCell; an indication indicating that the SHR and SCG failure-related information are related to the same PCell change with a PSCell change procedure; or second time information related to at least one of the SHR or the SCG failure-related information.

[0018] In some embodiments, the processor of the source MN is configured to: receive the SHR and the SPC report from a target MN via the transceiver; and determine whether the SHR and the SPC report are related to the same PCell change with a PSCell change procedure.

[0019] In some embodiments, the SHR is received before the SPC report, or the SHR is received together with the SPC report.

[0020] In some embodiments, at least one of the SHR or the SPC report includes first information, and the processor of the source MN is configured to determine whether the SHR and the SPC report are related to the same PCell change with a PSCell change procedure based on the first information.

[0021] In some embodiments, the first information includes at least one of: a C-RNTI of a target PCell; a C-RNTI of a source PCell; an indication indicating that the SHR and the SPC reports are related to the same PCell change with a PSCell change procedure; or first time information related to at least one of the SHR or the SPC report.

[0022] In some embodiments, the first time information includes at least one of: an absolute time when the SPC report is generated; or a time interval between an absolute time when the SHR is generated and the absolute time when the SPC report is generated.

[0023] In some embodiments, the processor of the source MN is configured to: start a first timer when receiving the SHR from the target MN; and when the SPC is received before expiration of the first timer, determine that the SHR and the SPC report are related to the same PCell change with a PSCell change procedure.

[0024] In some embodiments, the processor of the source MN is configured to: receive an SHR and SCG failure related information from a target MN via the transceiver; and determine whether the SHR and the SCG failure related information are related to the same PCell change with a PSCell change procedure.

[0025] In some embodiments, the SHR is received before the SCG fault related information, or the SHR and the SCG fault related information are received together.

[0026] In some embodiments, at least one of the SHR or the SCG failure-related information includes second information, and the processor of the source MN is configured to determine whether the SHR and the SCG failure-related information are related to the same PCell change with a PSCell change procedure based on the second information.

[0027] In some embodiments, the second information includes at least one of: a C-RNTI of a target PCell; a C-RNTI of a source PCell; an indication that the SHR and the SCG failure-related information are associated with the same PCell change with a PSCell change procedure; or second time information related to at least one of the SHR or the SCG failure-related information.

[0028] In some embodiments, the second time information includes at least one of the following: the absolute time when the SCG fault related information is generated; or the time interval between the absolute time when the SHR is generated and the absolute time when the SCG fault related information is generated.

[0029] In some embodiments, the processor of the source MN is configured to: start a second timer when the SHR is received from the target MN; and when the SCG failure-related information is received before the expiration of the second timer, determine that the SHR and the SCG failure-related information are related to the same PCell change with a PSCell change procedure.

[0030] Some embodiments of the present application also provide a target master node (MN). The target MN includes a transceiver, and a processor coupled to the transceiver; and the processor is configured to perform at least one of the following: transmitting a configuration to a source MN via the transceiver, wherein the configuration is used to store or report at least one of the following: a successful primary secondary cell (PSCell) change (SPC) report, or a first report including information about the successful completion of a primary cell (PCell) change with a PSCell change procedure; and wherein the configuration includes a second configuration for a set of trigger conditions associated with a secondary cell group (SCG); and transmitting a first indication to the source MN via the transceiver, wherein the first indication indicates that the second configuration for the set of trigger conditions associated with the SCG needs to be configured.

[0031] In some embodiments, the set of trigger conditions associated with the SCG includes at least one of: one or more trigger conditions of the SPC report; or one or more trigger conditions of the first report.

[0032] In some embodiments, the configuration further includes a first configuration for a set of trigger conditions associated with a master cell group (MCG), and the first configuration is used to store or report at least one of: a successful handover report (SHR), or the first report.

[0033] In some embodiments, the SHR and the SPC report are two separate reports. In an embodiment, the SHR includes information related to a successful PCell change, and the SPC report includes information related to a successful PSCell change. In some other embodiments, the SHR includes the SPC report, i.e., the SPC report is part of the SHR. In an embodiment, the SHR includes both information related to a successful PCell change and information related to a successful PSCell change.

[0034] In some embodiments, the set of trigger conditions associated with the MCG includes at least one of: one or more trigger conditions for the SHR; or one or more trigger conditions for the first report.

[0035] In some embodiments, the configuration includes at least one of: one or more common trigger thresholds configured for both the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG; or one or more trigger thresholds configured separately for the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG.

[0036] In some embodiments, the configuration includes at least one of the following: a timer T312-related threshold associated with the measurement identifier of the target PCell; a timer T312-related threshold associated with the measurement identifier of the target PSCell; a timer T312-related common threshold associated with the measurement identifier of the target PCell and the measurement identifier of the target PSCell; a timer T304-related threshold of the target PCell; a timer T304-related threshold of the target PSCell; or a timer T304-related common threshold of the target PCell and the target PSCell.

[0037] In some embodiments, the configuration is included in a handover (HO) request acknowledgement (ACK) message.

[0038] In some embodiments, the processor of the target MN is configured to transmit at least one of the following to the source MN via the transceiver: a cell radio network temporary identifier (C-RNTI) of the target PCell; an indication indicating that the SHR and the SPC report are related to the same PCell change with a PSCell change procedure; or first time information related to at least one of the SHR or the SPC report.

[0039] In some embodiments, the processor of the target MN is configured to transmit at least one of the following to the source MN via the transceiver: a cell radio network temporary identifier (C-RNTI) of the target PCell; an indication indicating that the SHR and SCG failure-related information are related to the same PCell change with a PSCell change procedure; or second time information related to at least one of the SHR or the SCG failure-related information.

[0040] In some embodiments, the processor of the target MN is configured to: receive the SHR and the SPC report from the UE via the transceiver; and determine whether the SHR and the SPC report are related to the same PCell change with a PSCell change procedure.

[0041] In some embodiments, the processor of the target MN is configured to: start a first timer when receiving the SHR from the UE; and when the SPC report is received before the first timer expires, determine that the SHR and the SPC report are related to the same PCell change with a PSCell change procedure.

[0042] In some embodiments, the processor of the target MN is configured to transmit the SHR and the SPC report to the source MN via the transceiver, and the SHR is transmitted before the SPC report or the SHR is transmitted together with the SPC report.

[0043] In some embodiments, at least one of the SHR or the SPC report includes first information, and the processor of the target MN is configured to determine whether the SHR and the SPC report are related to the same PCell change with a PSCell change procedure based on the first information.

[0044] In some embodiments, the first information includes at least one of: a C-RNTI of a target PCell; a C-RNTI of a source PCell; an indication indicating that the SHR and the SPC reports are related to the same PCell change with a PSCell change procedure; or first time information related to at least one of the SHR or the SPC report.

[0045] In some embodiments, the first time information includes at least one of: an absolute time when the SPC report is generated; or a time interval between an absolute time when the SHR is generated and the absolute time when the SPC report is generated.

[0046] In some embodiments, the processor of the target MN is configured to: receive an SHR and an SCG failure information message from the UE via the transceiver; and determine whether the SHR and the SCG failure information message are related to the same PCell change with a PSCell change procedure.

[0047] In some embodiments, the SHR is received before the SCG fault information message, or the SHR and the SCG fault information message are received together.

[0048] In some embodiments, the processor of the target MN is configured to: start a second timer when the SHR is received from the UE; and when the SCG failure information message is received before the expiration of the second timer, determine that the SHR and the SCG failure information message are related to the same PCell change with a PSCell change procedure.

[0049] In some embodiments, the processor of the target MN is configured to transmit the SHR and SCG fault-related information to the source MN via the transceiver, wherein the SHR is transmitted before the SCG fault-related information, or the SHR is transmitted together with the SCG fault-related information.

[0050] In some embodiments, at least one of the SHR or the SCG failure information message includes second information, and the processor of the target MN is configured to determine whether the SHR and the SCG failure information message are related to the same PCell change with a PSCell change procedure based on the second information.

[0051] In some embodiments, the second information includes at least one of: a C-RNTI of a target PCell; a C-RNTI of a source PCell; an indication that the SHR and the SCG fault information message are related to the same PCell change with a PSCell change procedure; or second time information related to at least one of the SHR or the SCG fault information message.

[0052] In some embodiments, the second time information includes at least one of the following: the absolute time when the SCG fault information message is generated; or the time interval between the absolute time when the SHR is generated and the absolute time when the SCG fault information message is generated.

[0053] Some embodiments of the present application also provide a source secondary node (SN). The source SN includes a transceiver, and a processor coupled to the transceiver; and the processor is configured to receive an indication from a source master node (MN) via the transceiver, wherein the indication indicates that the source SN needs to configure a second configuration for a set of trigger conditions associated with a secondary cell group (SCG).

[0054] In some embodiments, the set of trigger conditions associated with the SCG includes at least one of: one or more trigger conditions for a successful primary secondary cell (PSCell) change (SPC) report; or one or more trigger conditions for a first report including information regarding the successful completion of a primary cell (PCell) change with a PSCell change procedure.

[0055] In some embodiments, the processor of the source SN is configured to receive at least one of the following from the source MN via the transceiver: a cell radio network temporary identifier (C-RNTI) of the target PCell; an indication indicating that a successful switching report (SHR) and an SPC report are associated with the same PCell change with a PSCell change procedure; or first time information associated with at least one of the SHR or the SPC report.

[0056] In some embodiments, the SHR and the SPC report are two separate reports. In an embodiment, the SHR includes information related to a successful PCell change, and the SPC report includes information related to a successful PSCell change. In some other embodiments, the SHR includes the SPC report, i.e., the SPC report is part of the SHR. In an embodiment, the SHR includes both information related to a successful PCell change and information related to a successful PSCell change.

[0057] In some embodiments, the first time information includes at least one of: an absolute time when the SPC report is generated; or a time interval between an absolute time when the SHR is generated and the absolute time when the SPC report is generated.

[0058] In some embodiments, the processor of the source SN is configured to receive at least one of the following from the source MN via the transceiver: a cell radio network temporary identifier (C-RNTI) of a target PCell; an indication indicating that a successful switching report (SHR) and SCG failure-related information are related to a same PCell change with a PSCell change procedure; or second time information related to at least one of the SHR or the SCG failure-related information.

[0059] In some embodiments, the second time information includes at least one of the following: the absolute time when the SCG fault related information is generated; or the time interval between the absolute time when the SHR is generated and the absolute time when the SCG fault related information is generated.

[0060] In some embodiments, the processor of the source SN is configured to transmit an SN release request confirmation (ACK) message or an SgNB release request ACK message to the source MN via the transceiver, the message including the second configuration for the set of trigger conditions associated with the SCG.

[0061] In some embodiments, the second configuration includes at least one of: a threshold value related to timer T310 of the source PSCell; a threshold value related to timer T312 associated with the measurement identifier of the target PSCell; or a threshold value related to timer T304 of the target PSCell.

[0062] Some embodiments of the present application also provide a user equipment (UE). The UE includes a transceiver, and a processor coupled to the transceiver; and the processor is configured to receive a configuration from a source master node (MN) via the transceiver, wherein the configuration is used to store or report one of the following: a successful handover report (SHR) and a successful primary secondary cell (PSCell) change (SPC) report; and a first report including information about the successful completion of a primary cell (PCell) change with a PSCell change procedure, and wherein the configuration includes at least one of the following: a first configuration for a set of trigger conditions associated with a primary cell group (MCG); or a second configuration for a set of trigger conditions associated with a secondary cell group (SCG).

[0063] In some embodiments, the SHR and the SPC report are two separate reports. In an embodiment, the SHR includes information related to a successful PCell change, and the SPC report includes information related to a successful PSCell change. In some other embodiments, the SHR includes the SPC report, i.e., the SPC report is part of the SHR. In an embodiment, the SHR includes both information related to a successful PCell change and information related to a successful PSCell change.

[0064] In some embodiments, the set of trigger conditions associated with the MCG includes at least one of: one or more trigger conditions for the SHR; or one or more trigger conditions for the first report.

[0065] In some embodiments, the set of trigger conditions associated with the SCG includes at least one of: one or more trigger conditions of the SPC report; or one or more trigger conditions of the first report.

[0066] In some embodiments, the configuration includes at least one of: one or more common trigger thresholds configured for both the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG; or one or more trigger thresholds configured separately for the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG.

[0067] In some embodiments, the processor of the UE is configured to receive an explicit or implicit indication from the source MN via the transceiver indicating that the one or more common trigger thresholds are configured for both the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG.

[0068] In some embodiments, the configuration includes at least one of the following: a threshold value related to timer T310 of the source PCell; a threshold value related to timer T310 of the source PSCell; a common threshold value related to timer T310 of the source PCell and the source PSCell; a threshold value related to timer T312 associated with the measurement identifier of the target PCell; a threshold value related to timer T312 associated with the measurement identifier of the target PSCell; a common threshold value related to timer T312 associated with the measurement identifier of the target PCell and the measurement identifier of the target PSCell; a threshold value related to timer T304 of the target PCell; a threshold value related to timer T304 of the target PSCell; or a common threshold value related to timer T304 of the target PCell and the target PSCell.

[0069] In some embodiments, the processor of the UE is configured to: in response to at least one trigger condition of the SHR being satisfied before at least one trigger condition of the SPC report is satisfied, transmit the SHR or check whether the at least one trigger condition of the SPC report is satisfied before transmitting the SHR; and in response to at least one trigger condition of the SPC report being satisfied before at least one trigger condition of the SHR report is satisfied, check whether the at least one trigger condition of the SHR is satisfied before transmitting the SPC report.

[0070] In some embodiments, in response to transmitting the SHR, the processor of the UE is configured to store at least one of the following in the SPC report when at least one trigger condition of the SPC report is met: a cell radio network temporary identifier (C-RNTI) of the target PCell; an indication indicating that the SHR and the SPC report are related to the same PCell change with a PSCell change procedure; or first time information related to at least one of the SHR or the SPC report.

[0071] In some embodiments, the first time information includes at least one of: an absolute time when the SPC report is generated; or a time interval between an absolute time when the SHR is generated and the absolute time when the SPC report is generated.

[0072] In some embodiments, in response to checking whether the at least one trigger condition of the SPC report is met before transmitting the SHR, the processor of the UE is configured to: in response to the satisfaction of the at least one trigger condition of the SPC report and in response to the successful completion of the PCell change with the PSCell change procedure, transmit the SHR together with the SPC report; and in response to the non-satisfaction of the at least one trigger condition of the SPC report and in response to the successful completion of the PCell change with the PSCell change procedure, only transmit the SHR.

[0073] In some embodiments, in response to checking whether the at least one trigger condition of the SHR is met before transmitting the SPC report, the processor of the UE is configured to: transmit the SPC report together with the SHR in response to the satisfaction of the at least one trigger condition of the SHR and in response to the successful completion of the PCell change with the PSCell change procedure; and release the SPC report in response to at least one of the following: failure of a random access (RA) procedure to the target PCell, or failure of a RA procedure to the target PSCell.

[0074] In some embodiments, the processor of the UE is configured to store information about the successful completion of the PCell change with the PSCell change procedure in the first report in response to the satisfaction of at least one trigger condition within the set of trigger conditions associated with the MCG and the satisfaction of at least one trigger condition within the set of trigger conditions associated with the SCG.

[0075] In some embodiments, the processor of the UE is configured to transmit, via the transceiver, the first report in response to the successful completion of the PCell change with a PSCell change procedure.

[0076] In some embodiments, the first report is transmitted to a target MN, and the first report is communicated by the target MN to at least one of: the source MN; the target SN; or the source SN.

[0077] In some embodiments, the first report includes at least one of: information associated with the source PCell and the source PSCell; information associated with the target PCell and the target PSCell; a cause value of the first report; random access (RA) information toward the target PCell; or RA information toward the target PSCell.

[0078] Some embodiments of the present application provide a method performed by a source MN. The method includes transmitting a configuration to a user equipment (UE), wherein the configuration is used to store or report one of the following: a successful handover report (SHR) and a successful primary secondary cell (PSCell) change (SPC) report; and a first report including information about a successful completion of a primary cell (PCell) change with a PSCell change procedure, and wherein the configuration includes at least one of the following: a first configuration for a set of trigger conditions associated with a primary cell group (MCG); or a second configuration for a set of trigger conditions associated with a secondary cell group (SCG).

[0079] Some embodiments of the present application provide a method performed by a target MN. The method includes performing one of the following: transmitting a configuration to a source MN, wherein the configuration is used to store or report at least one of the following: a successful primary secondary cell (PSCell) change (SPC) report, or a first report including information about the successful completion of a primary cell (PCell) change with a PSCell change procedure; and wherein the configuration includes a second configuration for a set of trigger conditions associated with a secondary cell group (SCG); and transmitting a first indication to the source MN, wherein the first indication indicates that the second configuration for the set of trigger conditions associated with the SCG needs to be configured.

[0080] Some embodiments of the present application provide a method performed by a source SN. The method includes receiving an indication from a source master node (MN), wherein the indication indicates that the source SN needs to configure a second configuration for a set of trigger conditions associated with a secondary cell group (SCG).

[0081] Some embodiments of the present application provide a method performed by a UE. The method includes receiving a configuration from a source master node (MN) via the transceiver, wherein the configuration is used to store or report one of the following: a successful handover report (SHR) and a successful primary secondary cell (PSCell) change (SPC) report; and a first report including information about the successful completion of a primary cell (PCell) change with a PSCell change procedure, and wherein the configuration includes at least one of the following: a first configuration for a set of trigger conditions associated with a primary cell group (MCG); or a second configuration for a set of trigger conditions associated with a secondary cell group (SCG).

[0082] 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-mentioned method performed by a network node (source MN, target MN, or source SN) or a UE.

[0083] 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

[0084] In order 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 present application illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered to limit its scope.

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

[0086] Figures 2 to 5 An exemplary flow chart illustrating transmitting a SHR according to some embodiments of the present application.

[0087] Figure 6 An exemplary flow diagram illustrating transmitting a report including information regarding successful completion of a PCell change with a PSCell change procedure in accordance with some embodiments of the present application.

[0088] Figure 7 A block diagram illustrating an exemplary apparatus according to some embodiments of the present application. DETAILED DESCRIPTION

[0089] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application, but 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 that are intended to be included in the spirit and scope of the present application.

[0090] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3GPP 5G, 3GPP LTE Release 8, etc.). It is conceivable 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 listed in the present application may be changed, which should not affect the principles of the present application.

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

[0092] As in 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 one UE 101 shown, one MN 102 shown, and one SN 103 shown. Figure 1 A specific number of UEs 101, MNs 102, and SNs 103 are depicted in FIG. 1 , but it is contemplated that any number of UEs 101, MNs 102, and SNs 103 may be included in the wireless communication system 100.

[0093] refer to Figure 1 UE 101 may be connected to MN 102 and SN 103 via a network interface (e.g., a Uu interface specified in a 3GPP standard document). MN 102 and SN 103 may be connected to each other via a network interface, such as 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 SN 103 via a network interface (not specified in a 3GPP standard document). Figure 1 UE 102 may be configured to utilize resources provided by MN 102 and SN 103 to perform data transmission.

[0094] 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.

[0095] MN 102 may be associated with a Master Cell Group (MCG). MCG may refer to a group 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.

[0096] 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 to 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.

[0097] 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).

[0098] 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 onboard computer, a network device (e.g., a router, a switch, and a modem), or the like. 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 reception circuit system, or any other device capable of sending and receiving communication signals on a wireless network.

[0099] In some other embodiments of the present application, UE 101 includes a wearable device, such as a smart watch, a fitness bracelet, an optical head-mounted display, or the like. 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.

[0100] In 3GPP Rel-17, a Successful Handover Report (SHR) is introduced for MRO of PCell change procedures. The PCell change can be a legacy PCell change or handover or a conditional PCell change or conditional handover (CHO). In particular, the MRO function in NR can be enhanced to provide more robust mobility by reporting failure events observed during a successful handover from the source NG-RAN to the target NG-RAN through SHR. SHR is a report associated with a successful handover, which includes a set of measurements collected during the handover phase, i.e., measurements at the time of handover triggering, measurements at the end of handover execution, or measurements after handover execution. For example, when at least one of the following triggering conditions is met and / or the RA for the PCell is successful, the UE may store information related to a successful PCell change or generate a VarSuccessHO-Report / SHR:

[0101] (1) The ratio between the value of the elapsed time of timer T310 of the source PCell and the configured value of timer T310 configured for the source PCell when the UE was connected to the source PCell before performing the last PCell change / HO procedure is greater than the configured threshold (e.g., thresholdPercentageT310 configured by the source PCell before performing the last PCell change / HO procedure).

[0102] (2) If T312 associated with the measurement identifier of the target PCell is running when the execution of the PCell change / HO procedure is initiated, and if the ratio between the value of the elapsed time of timer T312 and the configured value of timer T312 (which is configured when the UE is connected to the source PCell before the last PCell change / HO procedure is performed) is greater than a configured threshold (e.g., thresholdPercentageT312 configured by the source PCell before the last PCell change / HO procedure is performed).

[0103] (3) The ratio between the value of the elapsed time of timer T304 of the target PCell and the configured value of timer T304 (i.e., which is included in the last applied RRCReconfiguration message, which includes the reconfigurationWithSync of the PCell change / HO procedure) is greater than the configured threshold (e.g., thresholdPercentageT304 configured by the target PCell before performing the last PCell change / HO procedure).

[0104] Information related to a successful PCell change is included in the SHR, such as at least one of the following: cell information of the source PCell, cell information of the target PCell, a cause value of the SHR (e.g., t304-cause, t310-cause, or t312-cause), measurement results of the source PCell and / or the target PCell when the HO is performed or successful, and RA information (e.g., RACH configuration of the target PCell). In general, the cell information includes a global cell identifier and a tracking area code of the cell, or a PCI and frequency information (e.g., ARFCN).

[0105] The availability of the SHR may be indicated by a handover complete message (RRCReconfigurationComplete) transmitted from the UE to the target NG-RAN node via RRC. The target NG-RAN node may obtain information of a successful handover report via the UE information request / response mechanism. In addition, the target NG-RAN node may then forward the SHR to the source NR-RAN node to indicate the failures experienced during a successful handover event.

[0106] After receiving the SHR, the receiving node can analyze whether its mobility configuration needs to be adjusted. Such adjustments may result in changes to the mobility configuration, such as changes to the RLM configuration or changes to the mobility thresholds between the source and the target. In addition, the target NG-RAN node in the performed handover may further optimize the dedicated RACH resources based on the measurements reported upon successful handover.

[0107] In 3GPP Rel-18, a successful PSCell change report (e.g., which may be named "SPC-Report", "SPC-report", "SPC Report", "SPC report" or the like) will be introduced to optimize PSCell change or CPAC related parameters, for example, if the UE detects a physical layer problem during an ongoing legacy PSCell change procedure or an ongoing CPAC procedure. In order to report the SPC-report, the configuration for the UE to record or generate the SPC-report (e.g., successPSCellChange-Config IE (information element)) is configured by the network, for example, via an RRCReconfiguration message, including a timer T304 related threshold (threshold, such as thresholdPercentageT304 generated by the target PSCell), a timer T310 related threshold (threshold, such as thresholdPercentageT310 generated by the source PSCell or the source PCell), or a timer T312 related threshold (threshold, such as thresholdPercentageT312 generated by the source PSCell or the source PCell). Based on the network configuration, when at least one trigger condition is met, the UE needs to record or generate successful PSCell change related parameters. 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 the successful PSCell change report (e.g., t304-cause, t310-cause, or t312-cause), and the measurement results.

[0108] In addition, the purpose of the SCG failure information procedure is to notify the E-UTRAN or NR MN of the SCG failure that the UE has experienced. SCG failure types include SCG radio link failure, SCG reconfiguration synchronization failure, SCG configuration failure of RRC messages on signaling radio bearer (SRB) 3, SCG integrity check failure, and consistent uplink LBT failure on the PSCell for shared spectrum channel access operations. 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. In the case of an SCG failure, the following information may also be included in the SCG failure information message: previous PSCell ID (ie PCI and ARFCN); faulty PSCell ID (ie PCI and ARFCN); time SCG failure and / or RA-information. After the network receives the SCG failure information message, it may trigger the UE to perform an SN release or modification or change procedure.

[0109] Currently, in the MR-DC scenario, there is no MRO mechanism for PCell change with PSCell change procedure. In this application, the PCell change with PSCell change procedure can be a normal PCell change with a normal PSCell change procedure, or a normal PCell change with a conditional PSCell addition or change (CPAC) procedure, or a conditional PCell change with a normal PSCell change procedure, or a conditional PCell change with a CPAC procedure. Considering the success case that is close to failure in the PCell change with PSCell change procedure (e.g., detecting potential problems during a successful PCell change with PSCell change), it is necessary to solve the problem of how to support MRO functionality, such as: (1) how the network is configured to store or report successful cell change related information of a successful PCell change that is close to failure with a PSCell change procedure; and (2) how the UE stores or reports successful cell change related information of a successful PCell change that is close to failure with a PSCell change procedure.

[0110] Embodiments of the present application are intended to solve the above-mentioned problems. Some embodiments of the present application reuse the procedures of SHR report and SPC-report report for a successful PCell change with a nearly failed PSCell change procedure. More specifically, in an embodiment, the source MN (i.e., S-MN) configures the SPC-report trigger condition. In another embodiment, the target MN (i.e., T-MN) configures the SPC-report trigger condition, and the trigger threshold is included in the HO request ACK message. In another embodiment, the source SN (i.e., S-SN) configures the SPC-report trigger condition. Regarding the behavior of the UE, in an embodiment, regardless of whether the SPC report is triggered or whether the PSCell change is successful, the UE will immediately send an SHR to the T-MN if triggered. In another embodiment, if the SHR is triggered first, the UE further checks whether the SPC-report is triggered. In another embodiment, if the SPC-report is triggered first, the UE further checks whether the SHR is triggered.

[0111] Some other embodiments of the present application introduce a novel procedure for storing or reporting successful PCell changes with PSCell change related information. In order to configure the trigger conditions, the configuration for storing or reporting successful PCell changes with PSCell change related information may consist of a set of trigger conditions associated with the MCG and another set of trigger conditions associated with the SCG. More specifically, in an embodiment, the S-MN configures the trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report. In another embodiment, the T-MN configures the trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report, and the trigger threshold is included in the HO request ACK message. In another embodiment, the S-SN configures the trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report. Regarding the behavior of the UE, in an embodiment, when at least one condition within the set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report and at least one condition within the set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report are met, the UE may generate or store a successful PCell change with PSCell change related information (e.g., information associated with the source SpCell, information related to the target SpCell). In another embodiment, when the PCell change with the PSCell change procedure is successful, the UE only sends the stored information (e.g., a successful PCell change with a PSCell change report) to the network (e.g., T-MN). And, the successful PCell change with a PSCell change report may be transmitted to the T-SN and / or S-MN and / or S-SN.

[0112] More details about the embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0113] Generally speaking, in order to configure an SHR with a near-failed successful PCell change of a PSCell change procedure, a trigger condition associated with the MCG is generated by the T-MN, such as a trigger condition related to T304 (associated with the target PCell) of the SHR (e.g., thresholdPercentageT304). Also, a trigger condition associated with the MCG is generated by the S-MN, such as a trigger condition related to T310 (associated with the source PCell) of the SHR (e.g., thresholdPercentageT310), or a trigger condition related to T312 (associated with the measurement identifier of the target PCell) of the SHR (e.g., thresholdPercentageT312).

[0114] In order to configure the SPC-report of the successful PCell change with the near failure of the PSCell change procedure, the T-SN generates a trigger condition associated with the SCG, such as the T304 (associated with the target PSCell) related trigger condition of the SPC-report, that is, the T304 related threshold for triggering the SPC-report is included in the "SN add request ACK message" or "SgNB release request ACK message" and "handover request ACK message". Then, the S-MN can send the T304 related threshold for triggering the SPC-report to the UE via the RRC message.

[0115] In the old case, for pure SPC-reporting in the MN-initiated PSCell change procedure, the MN configures T310 (associated with the source PSCell) and / or T312 (associated with the measurement identity of the target PSCell) related thresholds for triggering SPC-reporting. In the SN-initiated PSCell change procedure, the S-SN configures T310 (associated with the source PSCell) and / or T312 (associated with the measurement identity of the target PSCell) related thresholds for triggering SPC-reporting.

[0116] Differently, in some embodiments of the present application (represented as embodiment 1-1 for simplicity), when considering the MRO of a successful PCell change with a near-failed PSCell change procedure, the SHR reporting mechanism and the SPC reporting mechanism are reused. Figures 2 to 5 The examples are described below.

[0117] In some embodiments of the present application, the SHR and SPC reports are two separate reports. In an embodiment, the SHR includes information related to a successful PCell change, and the SPC report includes information related to a successful PSCell change. In some other embodiments of the present application, the SHR includes an SPC report, i.e., the SPC report is part of the SHR. In an embodiment, the SHR includes both information related to a successful PCell change and information related to a successful PSCell change.

[0118] In some embodiments of the present application, when the SHR and SPC reports are two separate reports, the configuration of the SHR is only the configuration of the SHR including information related to a successful PCell change, or the configuration of the SHR includes a configuration of a set of trigger conditions associated with a master cell group (MCG), that is, it is only used to store or report information related to a successful PCell change. In some other embodiments of the present application, when the SHR includes an SPC report, the configuration of the SHR is a configuration for storing or reporting both information related to a successful PCell change and information related to a successful PSCell change, which means that the configuration of the SHR includes a configuration of a set of trigger conditions associated with a master cell group (MCG) and a configuration of a set of trigger conditions associated with a secondary cell group (SCG).

[0119] Embodiment 1-1 reuses and combines SHR and SPC reports to configure trigger conditions for a successful PCell change with a near-failed PSCell change procedure. In order to configure SPC-reports in a successful PCell change with a near-failed PSCell change procedure, Embodiment 1-1 may use the following solutions (i.e., Solution 1, Solution 2, and Solution 3) to configure the set of trigger conditions associated with the SCG, for example, to configure T310 (associated with the source PSCell) and / or T312 (associated with the measurement identifier of the target PSCell) related thresholds for triggering SPC-reports. In Embodiment 1-1 (e.g., Solution 1, Solution 2, and Solution 3), "the set of trigger conditions associated with the SCG" or "SPC-report or threshold (condition) for triggering SPC-report" means that the configuration parameters are used to store or report information related to a successful PSCell change; "the set of trigger conditions associated with the MCG" or "SHR or threshold (condition) for triggering SHR" means that the configuration parameters are used to store or report information related to a successful PCell change. The SPC-report can be a separate report from the SHR, or a part of the SHR.

[0120] Solution 1

[0121] If it is the S-MN that configures the set of trigger conditions associated with the SCG, such as configuring the T310 / T312 related thresholds for triggering SPC reporting, then currently, the S-MN does not know whether the T-MN performs a PSCell change in a PCell change with a PSCell change procedure, because it is the T-MN that decides whether or how to change the PSCell (for example, whether to trigger a legacy PSCell change or a CPAC procedure). If it is the S-MN that configures the T310 / T312 related thresholds for triggering SPC-reporting, then the S-MN needs to know that the T-MN triggers the PSCell change, or the T-MN needs to notify the S-MN of the configuration of the T30 / T312 related thresholds for triggering SPC-reporting. In an embodiment of Solution 1, an indication may be included in the HO request ACK message (inside or outside the transparent container of the HO / PCell change) to indicate that the T310 or T312 related thresholds for triggering SPC-reporting need to be configured.

[0122] In Solution 1, in addition to the T310 or T312 related thresholds for triggering the SPC-report, since the S-MN also configures the set of trigger conditions associated with the MCG, for example, the S-MN also configures the T310 / T312 related thresholds for triggering the SHR, the following solutions may exist, namely Solution 1-1 and Solution 1-2.

[0123] Solution 1-1: A common T310-related threshold may be configured for both SHR and SPC-report, and / or a common T312-related threshold may be configured for both SHR and SPC-report. For example, "20%", "40%", "60%" or "80%" may be configured as a common T310-related threshold; "20%", "40%", "60%" or "80%" may be configured as a common T312-related threshold.

[0124] In some embodiments of solution 1-1, only one common trigger threshold, such as "40%" (i.e., the value of the common thresholdPercentageT310 associated with both the source PCell and the source PSCell), may be included in the RRC message to be sent to the UE (the value of the common thresholdPercentageT310 is configured by the source MN before the last reconfiguration is performed with the sync / PCell change with the PSCell change procedure). For example, an explicit or implicit indication also needs to be included in the RRC message to let the UE know that the trigger thresholds are configured for both the SHR and the SPC-report, i.e., an explicit or implicit indication to indicate that a common trigger threshold is configured for both the set of trigger conditions associated with the MCG (which is used to trigger the SHR) and the set of trigger conditions associated with the SCG (which is used to trigger the SPC-report). In this way, when the corresponding trigger condition is met, the UE can separately store relevant information or generate relevant variables.

[0125] In these embodiments of Solution 1-1, if only the threshold condition for triggering the SPC-report is met, the UE only stores or generates an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PSCell change. If only the threshold condition for triggering the SHR is met, the UE only stores or generates an SHR for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PCell change. If both the threshold condition for triggering the SHR and the threshold condition for triggering the SPC-report are met, the UE stores or generates an SHR and an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE stores or generates information related to a successful PCell change and information related to a successful PSCell change. In Solution 1-1, the stored or generated SHR and the stored or generated SPC report may be two separate reports, or the stored or generated SPC report may be encapsulated in the stored or generated SHR.

[0126] Specifically, in an embodiment, when a common trigger threshold (e.g., "40%" (i.e., the value of the common thresholdPercentageT310 associated with both the source PCell and the source PSCell)) is sent to the UE, the UE may store information related to a successful PCell change, or when "the ratio between the value of the elapsed time of the timer T310 of the source PCell and the configured value of the timer T310 configured for the source PCell when the UE was connected to the source PCell before performing the last PCell change procedure with a PSCell change procedure" is greater than, for example, "40%", the UE may generate a VarSuccessHO-report.

[0127] In another embodiment, when a common trigger threshold (e.g., "40%" (i.e., the value of the common thresholdPercentageT310 associated with both the source PCell and the source PSCell)) is sent to the UE, the UE may store information related to a successful PSCell change, or when "the ratio between the value of the elapsed time of the timer T310 of the source PSCell and the configured value of the timer T310 configured for the source PSCell when the UE was connected to the source PSCell before performing the last PCell change with the PSCell change procedure" is greater than, for example, "40%", the UE may generate a VarSPC-report.

[0128] In some other embodiments of solution 1-1, even if the values ​​of the T310-related thresholds for SHR and SPC-reports are the same, or even if the values ​​of the T312-related thresholds for SHR and SPC-reports are the same, two separate trigger thresholds with different IE names may be configured. For example, one threshold value "40%" configured as a T310-related threshold for SHR (e.g., thresholdPercentageT310forSHR or thresholdPercentageT310ofPCell) and another threshold value "40%" configured as a T310-related threshold for SPC-reports (e.g., thresholdPercentageT310forSPC or thresholdPercentageT310ofPSCell) may be included in the RRC message to be sent to the UE, i.e., an implicit indication indicating that the two trigger thresholds are separately configured for the set of trigger conditions associated with the MCG (which is used to trigger the SHR) and the set of trigger conditions associated with the SCG (which is used to trigger the SPC-report). In this way, the UE can understand the thresholds for triggering SHR and SPC-reporting based on the different IE names.

[0129] In these embodiments of Solution 1-1, if only the threshold condition for triggering the SPC-report is met, the UE only stores or generates an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PSCell change. If only the threshold condition for triggering the SHR is met, the UE only stores or generates an SHR for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PCell change. If both the threshold condition for triggering the SHR and the threshold condition for triggering the SPC-report are met, the UE stores or generates an SHR and an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE stores or generates information related to a successful PCell change and information related to a successful PSCell change. In Solution 1-1, the stored or generated SHR and the stored or generated SPC report may be two separate reports, or the stored or generated SPC report may be encapsulated in the stored or generated SHR.

[0130] Specifically, in an embodiment, when a threshold value "40%" of a T310-related threshold configured as SHR (e.g., thresholdPercentageT310forSHR or thresholdPercentageT310ofPCell) is sent to the UE, the UE may store information related to a successful PCell change, or when "the ratio between the value of the elapsed time of the timer T310 of the source PCell and the configured value of the timer T310 configured for the source PCell when the UE was connected to the source PCell before performing the last PCell change with a PSCell change procedure" is greater than "40%", the UE may generate a VarSuccessHO-report. For example, the value of thresholdPercentageT310forSHR or thresholdPercentageT310ofPCell is configured by the S-MN before performing the last reconfiguration with a sync / PCell change with a PSCell change procedure.

[0131] In another embodiment, when another threshold value "40%" of a T310-related threshold configured as an SPC-report (e.g., thresholdPercentageT310forSPC-Rport or thresholdPercentageT310ofPSCell) is sent to the UE, the UE may store information related to a successful PSCell change, or when "the ratio between the value of the elapsed time of the timer T310 of the source PSCell and the configured value of the timer T310 configured for the source PSCell when the UE was connected to the source PSCell before performing the last PCell change with the PSCell change procedure" is greater than, for example, "40%", the UE may generate a VarSPC-report. For example, the value of thresholdPercentageT310forSPC-Rport or thresholdPercentageT310ofPSCell is configured by the S-MN before performing the last reconfiguration with a sync / PCell change with a PSCell change procedure.

[0132] Solution 1-2: Different T310-related thresholds may be configured for SHR and SPC-reports, and / or different T312-related thresholds may be configured for SHR and SPC-reports. In order to enable the UE to understand the separate thresholds for triggering SHR and SPC-reports, different IE names may be defined for the triggering thresholds of SHR and SPC-reports. For example, "60%" of the T310-related threshold configured as SHR (e.g., defined as thresholdPercentageT310forSHR or thresholdPercentageT310ofPCell), and "40%" of the T310-related threshold configured as SPC-report (e.g., defined as thresholdPercentageT310forSPC-Report or thresholdPercentageT310ofPSCell) may be included in the RRC message to be sent to the UE, i.e., an implicit indication indicating that the two triggering thresholds are separately configured for the set of triggering conditions associated with the MCG (which is used to trigger the SHR) and the set of triggering conditions associated with the SCG (which is used to trigger the SPC-report). In this way, the UE can store or generate a report accordingly.

[0133] In solution 1-2, if only the threshold condition for triggering the SPC-report is met, the UE only stores or generates an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PSCell change. If only the threshold condition for triggering the SHR is met, the UE only stores or generates an SHR for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PCell change. If both the threshold condition for triggering the SHR and the threshold condition for triggering the SPC-report are met, the UE stores or generates an SHR and an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE stores or generates information related to a successful PCell change and information related to a successful PSCell change. In solution 1-2, the stored or generated SHR and the stored or generated SPC report may be two separate reports, or the stored or generated SPC report may be encapsulated in the stored or generated SHR.

[0134] Specifically, in some embodiments of solutions 1-2, when a threshold value "60%" of a T310-related threshold configured as SHR (e.g., thresholdPercentageT310forSHR or thresholdPercentageT310ofPCell) is sent to the UE, the UE may store information related to a successful PCell change, or when "the ratio between the value of the elapsed time of the timer T310 of the source PCell and the configured value of the timer T310 configured for the source PCell when the UE was connected to the source PCell before performing the last PCell change with a PSCell change procedure" is greater than, for example, "60%", the UE may generate a VarSuccessHO-report. For example, the value of thresholdPercentageT310forSHR or thresholdPercentageT310ofPCell is configured by the source MN before performing the last reconfiguration with a sync / PCell change with a PSCell change procedure.

[0135] In some other embodiments of solutions 1 to 2, when another threshold value "40%" of a T310-related threshold configured as an SPC-report (e.g., thresholdPercentageT310forSPC-Rport or thresholdPercentageT310ofPSCell) is sent to the UE, the UE may store information related to a successful PSCell change, or when the ratio between the value of the elapsed time of the timer T310 of the source PSCell and the configured value of the timer T310 configured for the source PSCell when the UE was connected to the source PSCell before performing the last PCell change with the PSCell change procedure is greater than, for example, "40%", the UE may generate a VarSPC-report. For example, the value of thresholdPercentageT310forSPC-Rport or thresholdPercentageT310ofPSCell is configured by the source MN before performing the last reconfiguration with a sync / PCell change with the PSCell change procedure.

[0136] Solution 2

[0137] If it is the T-MN that configures the set of trigger conditions associated with the SCG, for example, the T310 / T312 related thresholds for triggering the SPC-report, then the T-MN sends the set of trigger conditions associated with the SCG to the S-MN, for example, the T310 / T302 related thresholds for triggering the SPC-report are included in the HO request ACK message (inside or outside the transparent container of the HO / PCell change). Then, the S-MN may send the T310 / T312 related thresholds for triggering the SPC-report to the UE via an RRC message. The UE may store the relevant information or generate a success report accordingly based on the satisfied trigger conditions.

[0138] In some embodiments of Solution 2, if only the threshold condition for triggering the SPC-report is met, the UE only stores or generates an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PSCell change. If only the threshold condition for triggering the SHR is met, the UE only stores or generates an SHR for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PCell change. In some other embodiments of Solution 2, if both the threshold condition for triggering the SHR and the threshold condition for triggering the SPC-report are met, the UE stores or generates an SHR and an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE stores or generates information related to a successful PCell change and information related to a successful PSCell change. In Solution 2, the stored or generated SHR and the stored or generated SPC report may be two separate reports, or the stored or generated SPC report may be encapsulated in the stored or generated SHR.

[0139] Solution 3

[0140] If it is the S-SN that configures the set of trigger conditions associated with the SCG, such as configuring the T310 / T312 related thresholds for triggering SPC-reports, then the T-MN needs to indicate that the T310 / T3012 related thresholds for triggering SPC-reports need to be configured. For example, the T-MN indicates that the S-MN needs to configure the T310 / T312 related thresholds for triggering SPC-reports, and then, the S-MN indicates that the S-SN needs to configure the T30 / T312 related thresholds for triggering SPC-reports. In some embodiments of Solution 3, the indication may be included in the HO Request ACK message (outside the transparent container for HO / PCell change) to indicate that the S-MN configures the T310 / T312 related thresholds for triggering SPC-reports. In another embodiment, the indication may be included in the SN Release Request message or the SgNB Release Request message to indicate that the S-SN configures the T310 / T312 related thresholds for triggering SPC-reports. In some other embodiments of Solution 3, the T310 / T312 related threshold for triggering the SPC-report may be included in the SN release request ACK message or the SgNB release request ACK message. Then, the S-MN may send the T310 / T312 related threshold for triggering the SPC-report to the UE via an RRC message. The UE may store the relevant information or generate a success report accordingly based on the satisfied trigger condition.

[0141] In solution 3, for example, if only the threshold condition for triggering the SPC-report is met, the UE only stores or generates an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PSCell change. If only the threshold condition for triggering the SHR is met, the UE only stores or generates an SHR for a PCell change with a PSCell change procedure, i.e., the UE only stores or generates information related to a successful PCell change. If both the threshold condition for triggering the SHR and the threshold condition for triggering the SPC-report are met, the UE stores or generates an SHR and an SPC-report for a PCell change with a PSCell change procedure, i.e., the UE stores or generates information related to a successful PCell change and information related to a successful PSCell change. In solution 3, the stored or generated SHR and the stored or generated SPC report may be two separate reports, or the stored or generated SPC report may be encapsulated in the stored or generated SHR.

[0142] On the basis of Example 1-1, after the UE receives the configuration for storing or reporting SHR and / or SPC-report, the behavior of the UE is described in the following embodiments of the present application, namely, Example 1-2-1, Example 1-2-2 and Example 1-2-3. In Example 1-2-1, Example 1-2-2 and Example 1-2-3, "trigger conditions for (a) SHR" means a set of trigger conditions associated with MCG, and "trigger conditions for (a) SPC-report" means a set of trigger conditions associated with SCG.

[0143] Example 1-2-1

[0144] When the triggering condition of SHR is met, after the UE successfully accesses the target PCell (i.e., T304 for the target PCell stops), the UE may immediately send an SHR (e.g., including information related to the successful PCell change) to the T-MN, and the T-MN may transmit the SHR to the S-MN regardless of whether the SPC-report is triggered or whether the PSCell change is successful (e.g., when the SHR is triggered due to the satisfaction of the triggering condition configured by the source MN). Then, for example, the S-MN may transmit the SHR to the S-SN. In Embodiment 1-2-1, the SHR and the SPC-report may be two separate reports, or the SPC report may be part of the SHR or encapsulated in the SHR. In Embodiment 1-2-1, after the SHR is sent, there may be the following four different situations, namely, Case 1, Case 2, Case 3, and Case 4.

[0145] (1) Case 1: The triggering condition of the SPC-report is met and the UE successfully accesses the target PSCell. The UE may also send an SPC-report (e.g., including information related to the successful PSCell change) to the T-MN, the T-MN may transmit an SPC-report to the S-MN (e.g., when the SPC-report is triggered due to the satisfaction of the triggering condition configured by the source MN), and the S-MN may transmit an SPC-report to the S-SN (e.g., when the SPC-report is triggered due to the satisfaction of the triggering condition configured by the source SN). A specific example of Case 1 is described in Figures 2 to 5 The embodiments are described below.

[0146] (2) Case 2: The triggering condition of SPC-report is not met and the UE successfully accesses the target PCell. In this case, SPC-report is not generated or triggered.

[0147] (3) Case 3: The triggering condition of SPC-Report is met, but the UE cannot access the target PSCell. The UE may send an SCG failure information message to the T-MN, and the T-MN may transmit the SCG failure information to the S-MN. Then, for example, the S-MN may transmit the SCG failure related information to the S-SN.

[0148] (4) Case 4: The triggering condition of SPC-Report is not met, and the UE cannot access the target PSCell. The UE may send an SCG Failure Information message to the T-MN, and the T-MN may transmit the SCG Failure Information to the S-MN. Then, for example, the S-MN may transmit the SCG Failure related information to the source SN. Specific examples of cases 3 and 4 are described in Figures 2 to 5 The embodiments are described below.

[0149] Figure 2 An exemplary flow chart illustrating the transmission of an SHR according to some embodiments of the present application. The details described in all other embodiments of the present application are applicable to the Figure 2 The embodiments shown in . Those skilled in the art should understand that without departing from the spirit and scope of the present disclosure, Figure 2 The sequence of operations in the exemplary process 200 may be changed, and may be eliminated or modified. Figure 2 Some of the operations in the exemplary procedure 200 in FIG.

[0150] Specifically, the exemplary flowchart 200 can be referred to Figure 2 Case 1, Case 3 or Case 4 in different embodiments.

[0151] In case 1, Figure 2In the exemplary flow chart 200 shown in FIG. 2 , in operation 211, the UE 201 may successfully complete the RA procedure for the T-MN 203. In operation 212, the UE 201 may transmit an SHR to the T-MN 203.

[0152] Optionally, in operation 213, T-MN 203 may transmit the received SHR to S-MN 202. In operation 213A, S-MN 202 may further transmit the received SHR to S-SN 204.

[0153] In operation 214, UE 201 may successfully complete the T-SN ( Figure 2 In operation 215, UE 201 may transmit an SPC-report to T-MN 203.

[0154] Optionally, in operation 216, the T-MN 203 may determine whether the SHR and SPC-report are related to the same PCell change with PSCell change procedure.

[0155] Optionally, in operation 217, T-MN 203 may transmit an SPC-report to S-MN 202, and the details are described below in options 1 to 3 of case 1. In operation 218, S-MN 202 may determine whether the SHR and the SPC-report are related to the same PCell change with the PSCell change procedure.

[0156] Optionally, in operation 217A, S-MN 202 may further transmit an SPC-report to S-SN 204. In operation 218A, S-SN 204 may determine whether the SHR and the SPC-report are related to the same PCell change with the PSCell change procedure.

[0157] In case 1, the network node (e.g., T-MN and / or S-MN and / or S-SN) may first receive the SHR and then receive the SPC-report. Since the SHR and the SPC-report are used for the same PCell change with the PSCell change procedure, the network node needs to associate the SHR with the SPC-report when performing MRO analysis. In order to solve the problem of how to associate the SHR with the SPC-report for MRO, in case 1, Figure 2 The following options may exist in different embodiments, namely options 1 to 3 as follows.

[0158] Option 1: The C-RNTI of the target PCell and / or the C-RNTI of the source PCell may be included in the SHR transmitted or transmitted in operations 212, 213, and 213A, and the C-RNTI of the target PCell and / or the C-RNTI of the source PCell may be included in the SPC-report transmitted or transmitted in operations 215, 217, and 217A. After the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) receives the SHR and the SPC-report, based on the same C-RNTI, the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) may associate the SHR with the SPC-report, that is, may determine that the SHR and the SPC-report are related to the same PCell change with the PSCell change procedure.

[0159] Option 2: UE 201 may include an indication in the SPC-report to indicate that the latest SHR (if any) (e.g., in operation 212) is associated with the same PCell change with the PSCell change procedure at operation 215. For example, if necessary, when T-MN 203 transmits the SPC-report to S-MN 202 at operation 217, the indication in the SPC-report at operation 215 may also be transmitted to S-MN 202. If necessary, when S-MN 202 transmits the SPC-report to S-SN 204 at operation 217A, the indication may also be transmitted to S-SN 204. After the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) receives the SHR and the SPC-report, based on the indication, the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) may associate the SHR with the SPC-report, i.e., may determine that the SHR and the SPC-report are related to the same PCell change with the PSCell change procedure.

[0160] Option 3: UE 201 may include time information in the SHR, i.e., an absolute timestamp when the SHR is generated or transmitted, or generate or transmit the time elapsed from receiving the RRC message for the PCell change with the PSCell change to the SHR in operation 212. UE may include time information in the SPC-report, i.e., an absolute timestamp when the SPC-report is generated or transmitted, or generate or transmit the time elapsed from receiving the RRC message for the PCell change with the PSCell change to the SPC-report, or generate or transmit the time elapsed from generating or transmitting the SHR to generating or transmitting the SPC-report in operation 215. If necessary, when T-MN 203 transmits the SHR to S-MN 202 in operation 213, the time information in the SHR may be transmitted to S-MN 202, and if necessary, when S-MN 202 transmits the SHR to S-SN 204 in operation 213A, the time information may also be transmitted to S-SN 204. If necessary, when T-MN 203 transmits an SPC-report to S-MN 202 in operation 217, time information in the SPC-report may be transmitted to S-MN 202, and if necessary, when S-MN 202 transmits an SPC-report to S-SN 204 in operation 217A, time information may also be transmitted to S-SN 204.

[0161] In option 3, after the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) receives the SHR and SPC-report, based on the included time information, the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) may understand that the SHR and SPC-report are for the same PCell change with PSCell change procedure (e.g., the time elapsed between these two reports is less than a configured threshold).

[0162] In cases 3 and 4, Figure 2 In the exemplary flow chart 200 shown in FIG. 2 , in operation 211, UE 201 may successfully complete the RA procedure for T-MN 203. In operation 212, UE 201 may transmit an SHR to T-MN 203. Optionally, in operation 213, T-MN 203 may transmit the received SHR to S-MN 202. In operation 213A, S-MN 202 may further transmit the received SHR to S-SN 204.

[0163] In operation 214, the UE 201 performs the T-SN ( Figure 2The RA procedure of the UE 201 (not shown) may fail, or RLF may occur in the T-SN. In operation 215, the UE 201 may transmit SCG failure related information to the T-MN 203, for example, the information is included in an SCG failure information message.

[0164] Optionally, in operation 216, the T-MN 203 may determine whether the SHR and SCG failure related information is related to the same PCell change with the PSCell change procedure.

[0165] Optionally, in operation 217, T-MN 203 may transmit SCG failure related information to S-MN 202, and the details are described below in options a to c of Case 3 and Case 4. In operation 218, S-MN 202 may determine whether the SHR and SCG failure related information are related to the same PCell change with the PSCell change procedure.

[0166] Optionally, in operation 217A, S-MN 202 may further transmit SCG failure related information to S-SN 204. In operation 218A, S-SN 204 may determine whether the SHR and SCG failure related information are related to the same PCell change with the PSCell change procedure.

[0167] In Case 3 and Case 4, the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN) may first receive the SHR and secondly receive the SCG failure information message. Since the SHR and the SCG failure information message are for the same PCell change with the PSCell change procedure, the network node needs to associate the SHR with the SCG failure information message when performing the MRO analysis. In order to solve the problem of how to identify whether the SuccessHO-report and the SCG failure related information are associated with the same PCell change with the PSCell change procedure for the MRO analysis in Case 3 and Case 4, in Case 3 and Case 4, Figure 2 There may be the following options in different embodiments, namely options a to c as follows.

[0168] Option a: In operations 215, 217, and 217A, the C-RNTI of the target PCell and / or the C-CNTI of the source PCell may be included in the SCG failure information message. After the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) receives the SHR and the SCG failure related information, based on the same C-RNTI, the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) may associate the SHR with the SCG failure information, that is, it may be determined that the SHR and the SCG failure information are related to the same PCell change with the PSCell change procedure.

[0169] Option b: UE 201 may include an indication in the SCG Failure Information message in operation 215 to indicate that the latest SHR (if any) (e.g., in operation 212) is associated with the same PCell change with the PSCell change procedure. For example, if necessary, when T-MN 203 transmits SCG failure related information to S-MN 202, the indication may also be transmitted to S-MN 202. If necessary, when S-MN 202 transmits an SPC-Report to S-SN 204 in operation 217A, the indication may also be transmitted to S-SN 204. After the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) receives the SHR and the SCG failure-related information, based on the indication, the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) may associate the SHR with the SCG failure-related information, i.e., may determine that the SHR and the SCG failure-related information are related to the same PCell change with the PSCell change procedure.

[0170] Option c: UE 201 may include time information in the SHR, i.e., an absolute timestamp when the SHR is generated or transmitted, or a time elapsed from “the time when the RRC message for PCell change with PSCell change is received” to “the time when the SHR is generated or transmitted” in operation 212. UE 201 may include time information in the SCG fault information message, i.e., an absolute timestamp when the SCG fault information message is generated or transmitted, a time elapsed from “the time when the RRC message for PCell change with PSCell change is received” to “the time when the SCG fault information message is generated or transmitted”, or a time elapsed from “the time when the SHR is generated or transmitted” to “the time when the SCG fault information message is generated or transmitted”. If necessary, when T-MN 203 transmits an SHR to S-MN 202 in operation 213, time information in the SHR may be transmitted to S-MN 202, and if necessary, when S-MN 202 transmits an SHR to S-SN 204 in operation 213A, the time information may also be transmitted to S-SN 204. If necessary, when T-MN 203 transmits SCG fault-related information to S-MN 202 in operation 217, time information in the SCG fault-related information may be transmitted to S-MN 202, and if necessary, when S-MN 202 transmits SCG fault-related information to S-SN 204 in operation 217A, the time information may also be transmitted to S-SN 204.

[0171] In option c, after the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) receives the SHR and SCG failure-related information, based on the included time information, the network node (e.g., T-MN 203 and / or S-MN 202 and / or S-SN 204) can understand that the SHR and SCG failure-related information are for the same PCell change with the PSCell change procedure (e.g., the time elapsed between these two reports is less than a configured threshold).

[0172] Figure 3 Another exemplary flow chart illustrating the transmission of SHR according to some embodiments of the present application. The details described in all other embodiments of the present application are applicable to the transmission of SHR according to some embodiments of the present application. Figure 3 The embodiments shown in . Those skilled in the art should understand that without departing from the spirit and scope of the present disclosure, Figure 3 The sequence of operations in the exemplary process 300 may be changed, and may be eliminated or modified. Figure 3 Some of the operations in the exemplary procedure 300 in FIG.

[0173] Specifically, the exemplary flowchart 300 can be referred to Figure 3Case 1, Case 3 or Case 4 in different embodiments.

[0174] In case 1, Figure 3 In the exemplary flow chart 300 shown in FIG. 3 , in operation 311, UE 301 may successfully complete the RA procedure for T-MN 303. In operation 312, UE 301 may transmit an SHR to T-MN 303. In operation 313, T-MN 303 may start a timer (e.g., the timer duration may be equal to Tstore_UE_cntxt) upon receiving the SHR.

[0175] Optionally, in operation 314, T-MN 303 may transmit the received SHR to S-MN 302. In operation 314A, S-MN 302 may further transmit the received SHR to S-SN 304.

[0176] In operation 315, UE 301 may successfully complete the T-SN ( Figure 3 In operation 316, UE 301 may transmit an SPC-report to T-MN 303.

[0177] Optionally, in operation 317, the T-MN 303 may determine whether the SHR and SPC-report are related to the same PCell change with PSCell change procedure.

[0178] Optionally, in operation 318, T-MN 303 may transmit an SPC-report to S-MN 302, and the details are described below in Option 4 of Case 1. In operation 319, S-MN 302 may determine whether the SHR and SPC-report are related to the same PCell change with PSCell change procedure.

[0179] Optionally, in operation 318A, the S-MN 302 may further transmit an SPC-report to the S-SN 304. In operation 319A, the S-SN 304 may determine whether the SHR and the SPC-report are related to the same PCell change with the PSCell change procedure.

[0180] In case 1, to solve the problem on how to associate SHR with SPC-report for MRO, there may be option 4 as follows.

[0181] Option 4: After T-MN 303 receives the SHR in operation 312, T-MN 303 may start a timer in operation 313 (e.g., the timer duration may be equal to Tstore_UE_cntxt). If the SPC-report is received before the timer expires, T-MN 303 may understand that the SHR and the SPC-report are for the same PCell change with the PSCell change procedure. In option 4, if necessary, when T-MN 303 transmits the SPC-report to S-MN 302 in operation 318, an indication may also be transmitted by T-MN 303 to S-MN 302 to indicate that the latest SHR and SPC-report are associated with the same PCell change with the PSCell change procedure. If necessary, when S-MN 302 transmits the SPC-report to S-SN 304 in operation 318A, this indication may also be transmitted by S-MN 302 to S-SN 304. Based on this indication, the S-MN 302 and / or the S-SN 304 may associate the SHR with the SPC-report, ie, may determine that the SHR and the SPC-report are related to the same PCell change with the PSCell change procedure.

[0182] In cases 3 and 4, Figure 3 , in operation 311, UE 301 may successfully complete the RA procedure for T-MN 303. In operation 312, UE 301 may transmit an SHR to T-MN 303. In operation 313, T-MN 303 may start a timer upon receiving the SHR (e.g., the timer duration may be equal to Tstore_UE_cntxt). Optionally, in operation 314, T-MN 303 may transmit the received SHR to S-MN 302. In operation 314A, S-MN 302 may further transmit the received SHR to S-SN 304.

[0183] In operation 315, the UE 301 performs the T-SN ( Figure 3 RA procedure of the UE 301 (not shown) may fail, or RLF may occur in the T-SN. In operation 316, the UE 301 may transmit SCG failure related information to the T-MN 303, for example, the information is included in an SCG failure information message. Optionally, in operation 317, the T-MN 303 may determine whether the SHR and SCG failure related information are related to the same PCell change with the PSCell change procedure.

[0184] Optionally, in operation 318, T-MN 303 may transmit SCG failure related information to S-MN 302, and the details are described below in option d of case 3 and case 4. In operation 319, S-MN 302 may determine whether the SHR and SCG failure related information are related to the same PCell change with the PSCell change procedure.

[0185] Optionally, in operation 318A, the S-MN 302 may further transmit SCG failure related information to the S-SN 304. In operation 319A, the S-SN 304 may determine whether the SHR and the SCG failure related information are related to the same PCell change with the PSCell change procedure.

[0186] In Case 3 and Case 4, in order to solve the problem on how to identify whether the SuccessHO-report and SCG failure related information are associated with the same PCell change with PSCell change procedure for MRO analysis, there may be option d as follows.

[0187] Option d: After T-MN 303 receives the SHR in operation 312, T-MN 303 starts a timer (for example, the timer duration may be equal to Tstore_UE_cntxt). If the SCG failure information message is received before the timer expires, T-MN 303 may understand that the SHR and the SCG failure information message are for the same PCell change with the PSCell change procedure. In option d, if necessary, when T-MN 303 transmits SCG failure related information to S-MN 302 in operation 318, an indication indicating that the latest SHR is associated with the same PCell change with the PSCell change procedure may also be transmitted by T-MN 303 to S-MN 302. If necessary, when S-MN 302 transmits SCG failure related information to S-SN 304 in operation 318A, this indication may also be transmitted by S-MN 302 to S-SN 304. Based on the indication, the S-MN 302 and / or the S-SN 304 may associate the SHR with the SCG failure related information, ie, may determine that the SHR and the SCG failure related information are related to the same PCell change with the PSCell change procedure.

[0188] Figure 4 Another exemplary flow chart illustrating the transmission of SHR according to some embodiments of the present application. The details described in all other embodiments of the present application are applicable to the Figure 4 The embodiments shown in . Those skilled in the art should understand that without departing from the spirit and scope of the present disclosure, Figure 4 The sequence of operations in the exemplary process 400 may be changed, and may be eliminated or modified. Figure 4 Some of the operations in the exemplary procedure 400 in FIG.

[0189] Specifically, the exemplary flowchart 400 can be referred to Figure 4 Case 1, Case 3 or Case 4 in different embodiments.

[0190] In case 1, Figure 4 In the exemplary flow chart 400 shown in FIG. 4 , in operation 411, UE 401 may successfully complete the RA procedure for T-MN 403. In operation 412, UE 401 may transmit an SHR to T-MN 403. In operation 413, T-MN 403 may start a timer (e.g., the timer duration may be equal to Tstore_UE_cntxt) upon receiving the SHR.

[0191] In operation 414, UE 401 may successfully complete the T-SN ( Figure 4 In operation 415, UE 301 may transmit an SPC-report to T-MN 403.

[0192] Optionally, in operation 416, the T-MN 403 may determine whether the SHR and SPC-report are related to the same PCell change with PSCell change procedure.

[0193] Optionally, in operation 417, T-MN 403 may transmit both SHR and SPC-report to S-MN 402, and the details are described below in Option 5 of Case 1. In operation 418, S-MN 402 may determine whether SHR and SPC-report are related to the same PCell change with PSCell change procedure.

[0194] Optionally, in operation 417A, S-MN 402 may further transmit the SHR and SPC-report to S-SN 404. In operation 418A, S-SN 404 may determine whether the SHR and SPC-report are related to the same PCell change with PSCell change procedure.

[0195] In case 1, to solve the problem on how to associate SHR with SPC-report for MRO, there may be option 5 as follows.

[0196] Option 5: After T-MN 403 receives the SHR in operation 412, T-MN 403 may start a timer (e.g., the timer duration may be equal to Tstore_UE_cntxt), and if an SPC-report is received before the timer expires, T-MN 403 may understand that the SHR and the SPC-report are for the same PCell change with the PSCell change procedure. If necessary, for example, in operation 417, T-MN 403 may transmit the SHR together with the SPC-report to S-MN 402 in one Xn or X2 message. Since the SHR and the SPC-report are received in one message, S-MN 402 may associate the SHR with the SPC-report. Optionally, if necessary, S-MN 402 may transmit the SHR together with the SPC-report to S-SN 404 in one Xn message or X2. Since the SHR and the SPC-report are received in one message, S-SN 404 may associate the SHR with the SPC-report.

[0197] In cases 3 and 4, Figure 4 In the exemplary flow chart 400 shown in FIG. 4 , in operation 411, UE 401 may successfully complete the RA procedure for T-MN 403. In operation 412, UE 401 may transmit an SHR to T-MN 403. In operation 413, T-MN 403 may start a timer (e.g., the timer duration may be equal to Tstore_UE_cntxt) upon receiving the SHR.

[0198] In operation 414, the T-SN ( Figure 4 The RA procedure of the UE 301 (not shown) may fail, or RLF may occur in the T-SN. In operation 415, the UE 301 may transmit SCG failure related information to the T-MN 403, for example, the information is included in an SCG failure information message.

[0199] Optionally, in operation 416, the T-MN 403 may determine whether the SHR and SCG failure related information is related to the same PCell change with the PSCell change procedure.

[0200] Optionally, in operation 417, T-MN 403 may transmit both SHR and SCG failure related information to S-MN 402, and the details are described below in option e of case 3 and case 4. In operation 418, S-MN 402 may determine whether the SHR and SCG failure related information are related to the same PCell change with the PSCell change procedure.

[0201] Optionally, in operation 417A, S-MN 402 may further transmit SHR and SCG failure related information to S-SN 404. In operation 418A, S-SN 404 may determine whether the SHR and SCG failure related information are related to the same PCell change with the PSCell change procedure.

[0202] In Case 3 and Case 4, to solve the problem on how to identify whether the SuccessHO-report (or SHR) and SCG failure related information are associated with the same PCell change with PSCell change procedure for MRO analysis, there may be option e as follows.

[0203] Option e: After the T-MN 403 receives the SHR in operation 412, the T-MN 403 starts a timer (for example, the timer duration may be equal to Tstore_UE_cntxt). If the SCG fault information message is received before the timer expires, the T-MN 403 may understand that the SHR and the SCG fault information message are for the same PCell change with the PSCell change procedure, that is, the SHR may be associated with the SCG fault related information. In option e, if necessary, for example, in operation 417, the T-MN 403 may transmit the SHR together with the SCG fault related information to the S-MN 402 in one Xn or X2 message. Since the SHR and the SCG fault related information are received in one message, the S-MN 402 may associate the SHR with the SCG fault related information. Optionally, for example, in operation 417A, if necessary, the S-MN 402 may transmit the SHR together with the SCG fault related information to the S-SN 404 in one Xn or X2 message. Since the SHR and the SCG failure related information are received in one message, the S-SN 404 can associate the SHR with the SCG failure related information.

[0204] Figure 5 An additional exemplary flow chart illustrating the transmission of an SHR according to some embodiments of the present application. The details described in all other embodiments of the present application are applicable to the Figure 5 The embodiments shown in . Those skilled in the art should understand that without departing from the spirit and scope of the present disclosure, Figure 5 The sequence of operations in the exemplary process 500 may be changed, and may be eliminated or modified. Figure 5 Some of the operations in the exemplary procedure 500 in FIG.

[0205] Specifically, the exemplary flowchart 500 can be referred to Figure 5 Case 1, Case 3 or Case 4 in different embodiments.

[0206] In case 1, Figure 5 In the exemplary flow chart 500 shown in FIG. 5 , in operation 511, UE 501 may successfully complete the RA procedure for T-MN 503. In operation 512, UE 501 may transmit an SHR to T-MN 503. In operation 513, T-MN 503 may transmit the SHR to S-MN 502. In operation 514, S-MN 502 starts a timer upon receiving the SHR (e.g., the timer duration may be equal to Tstore_UE_cntxt).

[0207] In operation 515, UE 501 may successfully complete the T-SN ( Figure 5 In operation 516, UE 501 may transmit an SPC-report to T-MN 503. In operation 517, T-MN 503 may transmit the SPC-report to S-MN 502. If the SPC-report is received before the timer expires, S-MN 502 may understand that the SHR and the SPC-report are for the same PCell change with the PSCell change procedure, that is, in operation 518, S-MN 502 may associate the SHR with the SPC-report.

[0208] Optionally, in operation 513A, S-MN 502 may transmit an SHR to S-SN 504. In operation 514A, S-SN 504 may start a timer upon receiving the SHR (e.g., the timer duration may be equal to Tstore_UE_cntxt). In operation 517A, S-MN 502 may further transmit an SPC-report to S-SN 504. In operation 518A, if the SPC-report is received before the timer expires, SN 504 may determine that the SHR and the SPC-report are related to the same PCell change with the PSCell change procedure, i.e., S-SN 504 may associate the SHR with the SPC-report.

[0209] In cases 3 and 4, Figure 5 , in operation 511, UE 501 may successfully complete the RA procedure for T-MN 503. In operation 512, UE 501 may transmit an SHR to T-MN 503. In operation 513, T-MN 503 may transmit the SHR to S-MN 502. In operation 514, S-MN 502 starts a timer (e.g., the timer duration may be equal to Tstore_UE_cntxt) upon receiving the SHR to solve the problem of how to identify whether the SHR / SuccessHO-report and SCG failure related information are associated with the same PCell change with PSCell change procedure for MRO analysis in Case 3 and Case 4.

[0210] In operation 515, the UE 501 performs the T-SN ( Figure 5 514. In operation 516, UE 501 may transmit SCG failure related information to T-MN 503, for example, the information is included in an SCG failure information message. In operation 517, T-MN 503 may transmit SCG failure related information to S-MN 502. If the SCG failure related information is received before the timer expires, S-MN 502 may understand that the SHR and the SCG failure related information are for the same PCell change with the PSCell change procedure, that is, in operation 518, S-MN 502 may associate the SHR with the SCG failure related information.

[0211] Optionally, in operation 513A, the S-MN 502 may transmit the SHR to the S-SN 504. In operation 514A, the S-SN 504 may start a timer upon receiving the SHR (e.g., the timer duration may be equal to Tstore_UE_cntxt). In operation 517A, the S-MN 502 may transmit the SCG failure related information to the S-SN 504. In operation 518A, if the SCG failure related information is received before the timer expires, the S-MN 504 may determine that the SHR and the SCG failure related information are related to the same PCell change with the PSCell change procedure, i.e., the S-SN 504 may associate the SHR with the SPC-report.

[0212] Example 1-2-2

[0213] When the triggering condition of SHR is met (e.g., before T304 of the target PCell stops or expires), the UE further checks whether the triggering condition of SPC-report is met, e.g., before T304 of the target PSCell stops or until T304 of the target PSCell expires. The following sub-embodiments may exist in embodiment 1-2-2.

[0214] (1) In an embodiment, if the triggering condition of the SPC-report is met before T304 of the target PSCell stops (i.e., the RA to the target PSCell is successful), then:

[0215] a) When the PCell change with the PSCell change is successful (i.e., after both T304 of the target PCell and T304 of the target PSCell are stopped), the UE may send the SHR together with the SPC-report to the network node (e.g., the target MN). For example, the SHR and the SPC-report are sent to the network node in a tandem manner or in a parallel manner in one RRC message (if yes, the SHR and the SPC-report may be two separate reports, or the SPC report is a part of the SHR), or the SHR and the SPC-report are sent to the network node in two RRC messages separately (if yes, the SHR and the SPC-report may be two separate reports); or

[0216] b) When the RA to the target PCell fails (ie, T304 of the target PCell expires), the UE may release the stored

[0217] SHR or successful PCell change related information (eg VarSuccessHO-Report), and also releases the stored SPC-Report or successful PSCell change related information (eg VarSPC-Report).

[0218] (2) In another embodiment, if the triggering condition of the SPC-report is not met before T304 of the target PSCell stops, then:

[0219] a) When the PCell change with PSCell change is successful, the UE may only send a

[0220] SHR or successful PCell change related information (e.g., VarSuccessHO-report); or

[0221] b) When RA to the target PCell fails (ie, T304 of the target PCell expires), the UE may release the stored SHR or successful PCell change related information (eg, VarSuccessHO-Report).

[0222] (3) In another embodiment, if the triggering condition of the SPC-report is not met until T304 of the target PSCell expires, that is, the RA to the PSCell fails (because T304 of the target PSCell expires), but the RA to the target PCell succeeds, then:

[0223] a) Option X: The UE may release the stored SHR or successful PCell change related information (eg VarSuccessHO-Report). The UE sends SCG failure related information to the T-MN.

[0224] b) Option Y: The UE may send the stored successful PCell change related information (e.g., stored SHR) together with the SCG failure related information to the T-MN. If necessary, the T-MN sends the successful PCell change related information together with the SCG failure related information to the S-MN.

[0225] (4) In yet another embodiment, if the triggering condition of the SPC-report is not met until T304 of the target PSCell expires, that is, the RA to the PSCell fails (because T304 of the target PSCell expires), and the RA to the target PCell fails, then:

[0226] a) The UE may release the stored SHR or successful PCell change related information (eg VarSuccessHO-Report).

[0227] Optionally, the UE may send faulty PCell change related information and SCG failure related information to the network in an RLF report.

[0228] (5) In yet another embodiment, if the triggering condition of the SPC-report is met, but the RA to the PSCell fails (i.e., T304 of the target PSCell expires), then:

[0229] a) When the RA to the target PCell is successful, the UE may send only the stored successful PCell change related information (eg, stored SHR) to the network node (eg, the target MN), releasing the stored SPC-Report (if any).

[0230] Example 1-2-3

[0231] The UE first performs RA to the target PSCell. When RA to the target PCell fails and / or RA to the target PSCell fails, the SPC-report (if generated) is released. If the triggering condition of the SPC-report is met and the UE successfully accesses the target PSCell (i.e., T304 of the target PSCell stops), the UE further checks whether RA to the target PCell is successful and / or whether the triggering condition of SHR is met. The following sub-embodiments may exist in Embodiment 1-2-3. (1) In the embodiment, if the triggering condition of SHR is met, but RA to the target PCell fails, i.e., the PCell is changed

[0232] If the UE fails to change, the UE may release the stored PSCell change related information or SPC-report (e.g., VarSPC-report). In addition, the UE may release the stored PSCell change related information or SHR (e.g., VarSuccessHO-report).

[0233] (2) In another embodiment, if the triggering condition of SHR is not met and the RA to the target PCell fails, that is, the PCell change fails, then the UE may release the stored PSCell change related information or SPC-report (eg, VarSPC-report).

[0234] (3) In another embodiment, if the triggering condition of the SHR is met and the RA to the target PCell is successful, the UE may send the SHR together with the SPC-report to the network node (e.g., T-MN). For example, the SHR and the SPC-report are sent to the network node in a cascaded manner or in parallel in one RRC message (if yes, the SHR and

[0235] The SPC-report may be two separate reports, or the SPC-report may be part of the SHR), or the SHR and the SPC-report may be sent to the network node in two separate RRC messages (if so, the SHR and the SPC-report may be two separate reports).

[0236] (4) In yet another embodiment, if the triggering condition of the SHR is not met and the RA to the target PCell is successful, the UE sends an SPC-report to the network node (eg, T-MN).

[0237] In some embodiments of the present application, a new procedure for storing or reporting successful PCell changes with PSCell change related information is introduced.

[0238] In order to enable a network node to provide a configuration for storing or reporting a successful PCell change with a PSCell change, these embodiments introduce a UE capability for storing or reporting information related to a successful PCell change with a PSCell change. Regarding optional UE capabilities, there may be the following two options in different embodiments:

[0239] (1) Option A: Optional with capability signaling. Even if the UE supports PCell change with PSCell change mechanism, storing or reporting successful PCell change with PSCell change related information is optional. This capability may be explicitly signaled by the UE to the network node, i.e., an optional UE capability is introduced by signaling for storing or reporting a report containing information about the successful completion of the PCell change with PSCell change procedure (e.g., which may be referred to as "successful PCell change with PSCell change report" or the like). For example, an optional UE capability indication for storing or reporting successful PCell change with PSCell change related information is included in the UE capability.

[0240] UECapabilityInformation message.

[0241] (2) Option B: Optional without capability signaling. Storing or reporting successful PCell changes with PSCell change related information is optional, and no explicit capability bit is signaled by the UE.

[0242] In some embodiments of the present application, a configuration for storing or reporting a successful PCell change with a PSCell change may be sent by the S-MN to the UE. The configuration for storing or reporting a successful PCell change with a PSCell change may include a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report (e.g., at least including a T310-related threshold for the source PCell, a T312-related threshold associated with the measurement identifier of the target PCell, or a T304-related threshold of the target PCell), and another set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report (e.g., at least including a T310-related threshold for the source PSCell, a T312-related threshold associated with the measurement identifier of the target PSCell, or a T304-related threshold of the target PSCell). The following sub-embodiments may exist in these embodiments.

[0243] (1) In an embodiment, the S-MN may configure a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report. For example, the S-MN may configure a T310-related threshold for the source PCell or a T312-related threshold associated with the measurement identifier of the target PCell, and the T-MN may configure a T304-related threshold for the target PCell.

[0244] (2) In another embodiment, if the S-MN configures a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report. For example, the S-MN may configure a T310-related threshold for the source PSCell or a T312-related threshold associated with the measurement identifier of the target PSCell, similar to Solution 1 in Example 1-1, the S-MN needs to know that the T-MN triggers the PSCell change, or the T-MN needs to indicate that the T310 / T312-related threshold needs to be configured. For example, the indication may be included in the HO request ACK message (outside the transparent container of the HO / PCell change) to indicate that the source MN configures the T310-related threshold for the source PSCell or the T312-related threshold associated with the measurement identifier of the target PSCell.

[0245] a) For an example, a common trigger threshold (e.g., only one trigger threshold or two separate trigger thresholds with different IE names but the same value) may be configured for both the T310-related threshold of the source PSCell and the T310-related threshold of the source PCell, and the UE may be explicitly or implicitly indicated (e.g., with different IE names). For example, an explicit indication is included in an RRC message to let the UE know that the common trigger threshold is configured for both the T310-related threshold of the source PSCell used to trigger a successful PCell change with a PSCell change report and the T310-related threshold of the source PCell used to trigger a successful PCell change with a PSCell change report, that is, an explicit indication indicating that the common trigger threshold is configured for both "a set of trigger conditions associated with an MCG for triggering a successful PCell change with a PSCell change report" and "a set of trigger conditions associated with an SCG for triggering a successful PCell change with a PSCell change report". Another way is that, a threshold value "x" configured as the T310 related threshold value of the source PSCell (e.g., thresholdPercentageT310forSuccessfulPCellChangeWithPSCellChangeReport or ThresholdPercentageT310ofPCell) and another threshold value "x" configured as the T310 related threshold value of the source PSCell (e.g., thresholdPercentageT310forSuccessfulPCellChangeWithPSCellChangeReport or ThresholdPercentageT310ofPSCell) may be included in the RRC message to be sent to the UE, that is, an implicit indication for indicating that the two triggering thresholds are configured for "a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report" and "a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report".

[0246] b) For another example, one common trigger threshold (e.g., only one trigger threshold or two separate trigger thresholds with different IE names but the same value) may be configured for a T312-related threshold associated with the measurement identifier of the target PSCell and a T312-related threshold associated with the measurement identifier of the target PCell, and may be explicitly or implicitly indicated to the UE (e.g., with different IE names). For example, an explicit or implicit indication is included in an RRC message to let the UE know that the common trigger threshold is configured for both a T312-related threshold associated with the measurement identifier of the target PSCell for triggering a successful PCell change with a PSCell change report and a T312-related threshold associated with the measurement identifier of the target PCell for triggering a successful PCell change with a PSCell change report, i.e., an explicit indication indicating that the common trigger threshold is configured for both "a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report" and "a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report". Another way is that, a threshold value "y" configured as a T312-related threshold associated with the measurement identifier of the target PSCell (for example, thresholdPercentageT312forSuccessfulPCellChangeWithPSCellChangeReport or thresholdPercentageT312ofPSCell) and another threshold value "y" configured as a T312-related threshold associated with the measurement identifier of the target PCell (for example, thresholdPercentageT312forSuccessfulPCellChangeWithPSCellChangeReport or thresholdPercentageT312ofPCell) may be included in an RRC message to be sent to the UE, that is, an implicit indication for indicating that the two triggering thresholds are configured for "a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report" and "a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report".

[0247] c) For another example, different IE names may be used to configure different trigger thresholds for the T310-related threshold of the source PSCell and the T310-related threshold of the source PCell. For example, different IE names in the RRC message implicitly indicate to the UE that different trigger thresholds are configured for the T310-related threshold of the source PSCell and the T310-related threshold of the source PCell, that is, an implicit indication that different trigger thresholds are configured for both "a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report" and "a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report".

[0248] d) For additional examples, different triggering thresholds may be configured using different IE names for the T312-related threshold associated with the measurement identifier of the target PSCell and the T312-related threshold associated with the measurement identifier of the target PCell.

[0249] For example, different IE names in the RRC message implicitly indicate to the UE that different trigger thresholds are configured separately for the T312-related thresholds associated with the measurement identifier of the target PSCell and the T312-related thresholds associated with the measurement identifier of the target PCell, that is, an implicit indication for indicating that different trigger thresholds are configured for both "a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report" and "a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report".

[0250] (3) In another embodiment, if the T-MN configures a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report, for example, the T-MN may configure a T310-related threshold of the source PSCell or a T312-related threshold associated with the measurement identifier of the target PSCell, and the T310-related threshold of the source PSCell or the T312-related threshold associated with the measurement identifier of the target PSCell is included in the HO request ACK message (inside or outside the transparent container of the HO / PCell change).

[0251] (4) In another embodiment, if the S-SN configures a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report. For example, the S-SN may be a T310-related threshold of the source PSCell or a T312-related threshold associated with the measurement identifier of the target PSCell. In this embodiment, the T-MN indicates that the S-MN needs to configure a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report, and then, the S-MN indicates that the S-SN needs to configure a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report. For example, the indication may be included in the HO request ACK message (outside the transparent container of the HO / PCell change) to indicate the S-MN T310 / T312-related thresholds required for triggering a successful PCell change with a PSCell change report. Alternatively, an indication may be included in the SN Release Request message or the SgNB Release Request message to indicate that the source SN configures the T310-related threshold of the source PSCell or the T312-related threshold associated with the measurement identifier of the target PSCell for triggering a successful PCell change with a PSCell change report. The T310-related threshold of the source PSCell or the T312-related threshold associated with the measurement identifier of the target PSCell may be included in the SN Release Request ACK message or the SgNB Release Request ACK message.

[0252] (5) In an additional embodiment, a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report is generated by the T-SN, for example, the T304-related threshold of the target PSCell, i.e., the T304-related threshold of the target PSCell is included in the SN add request ACK message or the SgNB add request ACK message and the handover request ACK message (inside or outside the transparent container of the HO / PCell change).

[0253] In some embodiments of the present application, when at least one condition within a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report and at least one condition within a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report are met, the UE may generate or store a successful PCell change with PSCell change related information or a successful PCell change with a PSCell change report. Optionally, the network node explicitly or implicitly indicates to the UE how to trigger or generate a successful PCell change with a PSCell change report. For example, an indication may be sent to the UE to instruct the UE to generate or store a successful PCell change with a PSCell change report only when at least one condition within a set of trigger conditions associated with the MCG for triggering a successful PCell change with a PSCell change report and at least one condition within a set of trigger conditions associated with the SCG for triggering a successful PCell change with a PSCell change report are met.

[0254] In some embodiments of the present application, when the PCell change with PSCell change procedure is successful, the UE only sends the stored successful PCell change with PSCell change report to the network node. Specifically:

[0255] (1) First, the UE sends a message to the network node (e.g., T-MN) via an RRC reconfiguration / setup / recovery / reestablishment complete message.

[0256] Sending an indication of the availability of a successful PCell change with a PSCell change report;

[0257] (2) Then, the network node (eg, T-MN) may transmit a request (eg, UE Information Request message) message to the UE for requesting a successful PCell change with a PSCell change report or a successful PCell change with PSCell change related information.

[0258] (3) After receiving the request, the UE may transmit the stored information related to a successful PCell change with a PSCell change procedure, a successful PCell change with a PSCell change report, or a successful PCell change with PSCell change related information to a network node (e.g., T-MN), for example via a UE information response message.

[0259] (4) A successful PCell change with a PSCell change report or a successful PCell change with PSCell change related information or information related to a successful PCell change with a PSCell change procedure may include at least:

[0260] a) Information associated with the source SpCell, for example, cell information of the source PCell, cell information of the source PSCell, measurement results of the source PCell and / or source PSCell when an RRC message of a PCell with a PSCell change is received or a PCell change with a PSCell change procedure is successfully performed. In the present disclosure, the cell information includes a global cell identity and a tracking area code of the cell, or a PCI and frequency information (e.g., ARFCN).

[0261] b) Information associated with the target SpCell, for example, cell information of the target PCell, cell information of the target PSCell, measurement results of the target PCell and / or target PSCell upon receiving an RRC message of a PCell with a PSCell change or successfully performing a PCell change with a PSCell change procedure. In the present disclosure, the cell information includes a global cell identity and a tracking area code of the cell, or a PCI and frequency information (e.g., ARFCN).

[0262] c) Cause value of successful PCell change with PSCell change report, for example, the trigger conditions associated with MCG and SCG are met, or T310 / T312 / T304 related thresholds are met.

[0263] d) RA information towards the target PCell and / or target PSCell, for example, RACH configuration including time and / or frequency resources for the RA procedure.

[0264] In some embodiments of the present application, a successful PCell change with a PSCell change report may be transmitted directly or indirectly to a T-SN and / or an S-MN and / or an S-SN by a receiving network node (e.g., a T-MN) that receives a successful PCell change with a PSCell change report from a UE. For example, the T-MN may transmit a successful PCell change with a PSCell change report to the S-MN; the T-MN may transmit a successful PCell change with a PSCell change report to the T-SN; the S-MN may transmit a successful PCell change with a PSCell change report to the S-SN; and / or the T-SN may transmit a successful PCell change with a PSCell change report to the S-SN. The node receiving the successful PCell change with a PSCell change report may perform an MRO analysis and update a configuration related to the PCell change with a PSCell change procedure.

[0265] (1) In an embodiment, when the T-MN receives a successful PCell change with a PSCell change report, the T-MN may transmit the successful PCell change with a PSCell change report to the S-MN. For example, for a case where a successful PCell change with a PSCell change report is triggered due to the satisfaction of a "T310-related threshold of the source PCell configured by the S-MN" and a "T310-related threshold of the source PSCell configured by the S-MN", the S-MN may analyze the successful PCell change with a PSCell change report and / or decide whether / how to modify parameters related to the PCell change with a PSCell change procedure.

[0266] (2) In another embodiment, when the T-MN receives a successful PCell change with a PSCell change report, the T-MN may transmit the successful PCell change with a PSCell change report to the S-MN. The T-MN may also transmit the successful PCell change with a PSCell change report to the T-SN. For example, for a case where a successful PCell change with a PSCell change report is triggered due to satisfying the "T312-related threshold configured by the S-MN associated with the measurement identifier of the target PCell" and the "T304-related threshold configured by the T-SN for the target PSCell", the S-MN and the T-SN may analyze the successful PCell change with a PSCell change report and / or decide whether / how to modify parameters related to the PCell change with a PSCell change procedure. In the following Figure 6 Specific examples are described in the embodiments of the present invention.

[0267] Figure 6 An exemplary flow chart illustrating the transmission of a report containing information about the successful completion of a PCell change with a PSCell change procedure according to some embodiments of the present application. The details described in all other embodiments of the present application apply to Figure 6 The embodiments shown in . Those skilled in the art should understand that without departing from the spirit and scope of the present disclosure, Figure 6 The sequence of operations in the exemplary process 600 may be changed, and may be eliminated or modified. Figure 6 Some of the operations in the exemplary procedure 600 in FIG.

[0268] Specifically, in Figure 6, in operation 611, UE 601 may receive an RRC reconfiguration message (which includes a configuration for storing or reporting a successful PCell change with PSCell change related information) from S-MN 602. In operation 612, UE 601 may store or generate a successful PCell change with a PSCell change report. In operation 613, UE 601 may transmit a successful PCell change with a PSCell change report to T-MN 605. T-MN 605 may analyze the successful PCell change with the PSCell change report and / or decide whether / how to modify parameters related to the PCell change with the PSCell change procedure.

[0269] After operation 613, only a portion of operations 614 to 617 are performed in some embodiments, while all of operations 614 to 617 are performed in some other embodiments. Figure 6 There may be the following options in different embodiments, namely options (1) to (4) as follows. It should be considered that other options may also be implemented without departing from the spirit and scope of the present disclosure. Figure 6 The embodiments shown in .

[0270] Option (1): In operation 614, the T-MN 605 may transmit the received successful PCell change with a PSCell change report to the S-MN 602. The S-MN 602 may analyze the successful PCell change with the PSCell change report and / or decide whether / how to modify parameters related to the PCell change with the PSCell change procedure.

[0271] Option (2): In operation 614, the T-MN 605 may transmit the received successful PCell change with a PSCell change report to the S-MN 602. In operation 615, the T-MN 605 may transmit the received successful PCell change with a PSCell change report to the T-SN 604. The S-MN 602 and / or the T-SN 604 may analyze the successful PCell change with the PSCell change report and / or decide whether / how to modify parameters related to the PCell change with the PSCell change procedure.

[0272] Option (3): After operation 614, the S-MN 602 may transmit the received successful PCell change with a PSCell change report to the S-SN 603 in operation 617. The S-SN 603 may then analyze the successful PCell change with the PSCell change report and / or decide whether / how to modify parameters related to the PCell change with the PSCell change procedure.

[0273] Option (4): After operation 615, the T-SN 604 may transmit the received successful PCell change with a PSCell change report to the S-SN 603 in operation 616. The S-SN 603 may then analyze the successful PCell change with the PSCell change report and / or decide whether / how to modify parameters related to the PCell change with the PSCell change procedure.

[0274] Figure 7 A block diagram illustrating an exemplary apparatus 700 according to some embodiments of the present disclosure. As shown in FIG. 9 , the apparatus 700 may include at least one processor 706 and at least one transceiver 702 coupled to the processor 706. Although in this figure, elements such as at least one transceiver 702 and processor 706 are described in the singular, the plural may be contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present application, the transceiver 702 may be divided into two devices, such as a receive circuit system and a transmit circuit system. In some embodiments of the present application, the apparatus 700 may further include an input device, a memory, and / or other components.

[0275] In some embodiments of the present application, the device 700 may be a UE or a network node (eg, an S-SN, an S-MN, a T-SN and / or a T-MN). The transceiver 702 and the processor 706 may interact with each other to execute the above, for example, Figures 1 to 6 The operations of a UE or a network node described in any of .

[0276] In some embodiments of the present application, the device 700 may further include at least one non-transitory computer-readable medium. For example, in some embodiments of the present disclosure, the non-transitory computer-readable medium may store computer-executable instructions thereon to enable the processor 706 to implement the method described above with respect to the UE or the network node (e.g., S-SN, S-MN, T-SN and / or T-MN). For example, when the computer-executable instructions are executed, the processor 706 interacts with the transceiver 702 to perform Figures 1 to 6 The operations of the UE or network node described in.

[0277] Those of ordinary skill in the art will appreciate that the operations or steps of the methods described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the operations or steps of the methods may reside as one or any combination or group of codes and / or instructions on a non-transitory computer-readable medium that may be incorporated into a computer program product.

[0278] 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 containing a series of elements not only includes the elements, but also includes other elements that are not explicitly listed or inherent to the process, method, article or equipment. In the absence of more constraints, elements starting with "one" or the like do not exclude the presence of additional equivalent elements in the process, method, article or equipment containing 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 enumerated 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, but is not used to limit the essence of the present application.

Claims

1. A source master node MN, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to transmit a configuration to a user equipment (UE) via the transceiver, wherein the configuration is for storing or reporting one of: Successful handover report SHR and successful primary / secondary cell PSCell change report SPC; and a first report containing information on the successful completion of a primary cell PCell change with a PSCell change procedure, and Wherein the configuration includes at least one of the following: a first configuration for a set of trigger conditions associated with a master cell group MCG; or A second configuration for a set of trigger conditions associated with a secondary cell group SCG.

2. The source MN according to claim 1, wherein the configuration includes at least one of the following: one or more common trigger thresholds configured for both the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG; or One or more trigger thresholds that are separately configured for the set of trigger conditions associated with the MCG and the set of trigger conditions associated with the SCG.

3. The source MN of claim 1, wherein the processor of the source MN is configured to receive a first indication from a target MN via the transceiver, and wherein the first indication indicates that the second configuration for the set of trigger conditions associated with the SCG needs to be configured.

4. The source MN of claim 3, wherein the processor of the source MN is configured to perform at least one of the following: generating the second configuration for the set of trigger conditions associated with the SCG; or A second indication is transmitted to a source secondary node SN via the transceiver, wherein the second indication indicates that the source SN needs to configure the second configuration for the set of trigger conditions associated with the SCG.

5. The source MN of claim 1, wherein the processor of the source MN is configured to receive at least one of the following from a target MN via the transceiver: The cell radio network temporary identifier C-RNTI of the target PCell; An indication for indicating that the SHR and the SPC reports are related to the same PCell change with a PSCell change procedure; or First time information associated with at least one of the SHR or the SPC report.

6. The source MN of claim 1, wherein the processor of the source MN is configured to receive at least one of the following from a target MN via the transceiver: The cell radio network temporary identifier C-RNTI of the target PCell; An indication for indicating that the SHR and SCG fault related information is related to the same PCell change with a PSCell change procedure; or Second time information related to at least one of the SHR or the SCG fault related information.

7. A target master node MN, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to perform one of: transmitting a configuration to a source MN via the transceiver, wherein the configuration is used to store or report at least one of: a successful primary secondary cell (PSCell) change (SPC) report, or information about a successful completion of a primary cell (PCell) change with a PSCell change procedure; and wherein the configuration includes a second configuration for a set of trigger conditions associated with a secondary cell group (SCG); and A first indication is transmitted to the source MN via the transceiver, wherein the first indication indicates that the second configuration for the set of trigger conditions associated with the SCG needs to be configured.

8. The target MN according to claim 7, wherein the configuration further includes a first configuration for a set of trigger conditions associated with a master cell group MCG, and wherein the first configuration is used to store or report at least one of the following: a successful handover report SHR, or the first report.

9. The target MN of claim 7, wherein the processor of the target MN is configured to transmit, via the transceiver, at least one of the following to the source MN: The cell radio network temporary identifier C-RNTI of the target PCell; An indication for indicating that the SHR and the SPC reports are related to the same PCell change with a PSCell change procedure; or First time information associated with at least one of the SHR or the SPC report.

10. The target MN of claim 7, wherein the processor of the target MN is configured to transmit, via the transceiver, at least one of the following to the source MN: The cell radio network temporary identifier C-RNTI of the target PCell; An indication for indicating that the SHR and SCG fault related information is related to the same PCell change with a PSCell change procedure; or Second time information related to at least one of the SHR or the SCG fault related information.

11. A user equipment UE, comprising: Transceiver; and A processor coupled to the transceiver, wherein the processor is configured to receive a configuration from a source master node MN via the transceiver, wherein the configuration is used to store or report one of: Successful handover report SHR and successful primary / secondary cell PSCell change report SPC; and a first report containing information on the successful completion of a primary cell PCell change with a PSCell change procedure, and Wherein the configuration includes at least one of the following: a first configuration for a set of trigger conditions associated with a master cell group MCG; or A second configuration for a set of trigger conditions associated with a secondary cell group SCG.

12. The UE of claim 11, wherein the processor of the UE is configured to: In response to at least one trigger condition of the SHR being satisfied before at least one trigger condition of the SPC report is satisfied, transmitting the SHR or checking whether the at least one trigger condition of the SPC report is satisfied before transmitting the SHR; and In response to the at least one trigger condition of the SPC report being satisfied before the at least one trigger condition of the SHR report is satisfied, checking whether the at least one trigger condition of the SHR is satisfied before transmitting the SPC report.

13. The UE according to claim 12, wherein: In response to transmitting the SHR, the processor of the UE is configured to store at least one of the following in the SPC report when the at least one triggering condition of the SPC report is met: The cell radio network temporary identifier C-RNTI of the target PCell; An indication for indicating that the SHR and the SPC reports are related to the same PCell change with a PSCell change procedure; or First time information associated with at least one of the SHR or the SPC report.

14. The UE according to claim 12, wherein: In response to checking whether the at least one triggering condition of the SPC report is met before transmitting the SHR, the processor of the UE is configured to: responsive to satisfaction of the at least one triggering condition of the SPC report and responsive to the successful completion of the PCell change with PSCell change procedure, transmitting the SHR together with the SPC report; as well as In response to non-satisfaction of the at least one triggering condition reported by the SPC and in response to the successful completion of the PCell change with a PSCell change procedure, only the SHR is transmitted.

15. A UE according to claim 11, wherein the processor of the UE is configured to store information about the successful completion of the PCell change with the PSCell change procedure in the first report in response to the satisfaction of at least one trigger condition within the set of trigger conditions associated with the MCG and the satisfaction of at least one trigger condition within the set of trigger conditions associated with the SCG.

Images