Method and apparatus in communication node used for wireless communication

Abstract

The invention discloses a method and an apparatus in a communication node used for wireless communication. A communication node receives a first RRC message, the first RRC message comprising configuration information of a first cell; determining that SCG connection fails; wherein, as a response to the determination of the SCG connection failure, whether to send the first failure message depends on whether the first process is performed; whether the first failure message is sent or not depends on whether a first process is carried out or not comprises the following steps: sending the first failure message only when the first process is not carried out; the first failure message indicates that the SCG connection fails; the first process comprises applying the configuration information of the first cell, and the first cell is a candidate cell or a target cell of the MCG; neither the MCG nor the SCG is suspended.

Description

Technical Field

[0001] The present application relates to a transmission method and apparatus in a wireless communication system, and in particular to a method and apparatus for reporting failure information. Background Art

[0002] With the continuous development of wireless communications, the requirements for mobility, transmission delay and transmission capacity are becoming increasingly higher. Therefore, technologies such as dual connectivity and carrier aggregation have been introduced into the 3GPP standard to expand communication bandwidth. In R17, 3GPP allows the configuration information of CHO candidate cells to include both the target MCG and the target SCG. In R18, 3GPP further enhanced the dual connectivity scenario through the "Further NR mobility enhancements" research project (Work Item, WI), discussed carrying multiple candidate SCGs in a CHO conditional configuration to support the simultaneous evaluation of CHO and CPC, and completed the corresponding modifications to the protocol standardization.

[0003] Self-Organizing Networks (SON) include network self-configuration and self-optimization. To optimize mobility performance and achieve fast handover, existing protocols support user equipment (UE) to store relevant handover information during handover and report the stored information after the cell group handover is completed. Summary of the Invention

[0004] In the traditional solution, when the SCG fails to connect wirelessly, it will send an SCG failure message to report information about the SCG connection failure. However, researchers have found that the traditional solution is limited to the need for MCG to maintain a good connection status, which is not suitable for the existing needs for dual connection enhancement. In fast and changing switching scenarios, it is easy to cause the SCG failure information report to be lost, and / or there are problems such as low flexibility, power waste, and disadvantages in network optimization. Therefore, how to improve the flexibility and robustness of the SCG connection failure information reporting mechanism is a problem that needs to be solved and studied at present.

[0005] In response to the above problems, the present application provides a solution for reporting failure information. In the description of the above problems, the NR system is used as an example. The present application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) or future 6G systems, achieving technical effects similar to those of the NR system. Furthermore, although the present application provides a specific implementation method for continuous transmission scenarios, the present application can also be used in DRX or Cell-DRX scenarios to achieve technical effects similar to those of continuous transmission scenarios. Furthermore, although the present application provides a specific implementation method for the 3GPP system, the present application can also be used in non-3GPP system scenarios to achieve technical effects similar to those of the 3GPP system. Furthermore, although the original intention of the present application is for CHO-with candidate SCGs, the present application can also be used for CHO-with target SCG, CPA / C or conditional LTM, etc., to achieve technical effects similar to those of CHO-with candidate SCGs. Furthermore, although the original intention of this application is for the scenario of candidate cells, this application can also be used in the scenario of subsequent candidate cells to achieve similar technical effects as candidate cells. Furthermore, although this application mainly provides a specific implementation method for the triggering conditions for reporting storage information involving the RRC_CONNECTED state, this application can also be used in scenarios such as the RRC_IDLE state or the RRC_INACTIVE state to achieve similar technical effects as the configuration of trigger events for the storage information reporting process in the RRC_CONNECTED state. Furthermore, although the present application provides a specific implementation method for scenarios involving mobility management, this application can also be used in scenarios such as m-TRP and m-TA to achieve similar technical effects in scenarios involving mobility management. Furthermore, although the original intention of this application is for the Uu air interface, this application can also be used for the PC5 port to achieve similar technical effects as the Uu air interface. Furthermore, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the V2X (Vehicle-to-Everything) scenario, the communication scenario between the terminal and the relay, and the relay and the base station, to achieve similar technical effects in the terminal and base station scenario. Furthermore, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the IAB (Integrated Access and Backhaul) communication scenario, to achieve similar technical effects in the terminal and base station scenario.Furthermore, although the original intention of this application is for the terrestrial network (TN) scenario, this application is also applicable to the non-terrestrial network (NTN) communication scenario, achieving technical effects similar to those in the TN scenario. Furthermore, although the original intention of this application is for the traditional communication waveform transmission scenario, this application is also applicable to the transmission scenario that combines communication and perception waveforms, achieving technical effects similar to those in the traditional pass-through waveform transmission scenario. In addition, adopting a unified solution for different scenarios also helps reduce hardware complexity and cost.

[0006] As an embodiment, the interpretation of terminology in this application refers to the definition of 3GPP specification protocol TS36 series.

[0007] As an embodiment, the interpretation of the terms in this application refers to the definitions of the 3GPP specification protocol TS37 series.

[0008] As an embodiment, the interpretation of the terms in this application refers to the definition of the 3GPP specification protocol TS38 series.

[0009] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

[0010] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0011] receiving a first RRC message including configuration information of a first cell; and determining that an SCG connection fails;

[0012] In which, as a response to the determination of the SCG connection failure, whether to send a first failure message depends on whether the first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

[0013] As an embodiment, the problem to be solved by the present application includes: how to determine whether a first failure message occurs when the SCG connection fails.

[0014] As an embodiment, the characteristics of the above method include: as a response to the determination of the SCG connection failure, whether to send the first failure message depends on whether the first process is in progress.

[0015] As an embodiment, the benefits of the above method include: saving UE power.

[0016] As an embodiment, the benefits of the above method include: it is conducive to improving the flexibility of information transmission.

[0017] As an embodiment, the benefits of the above method include: improving the probability of successfully sending the first failure message.

[0018] As an embodiment, the benefits of the above method include: being conducive to configuring different UE behaviors for different scenarios.

[0019] As an embodiment, the problem to be solved by this application includes: when to send the first failure message.

[0020] As an embodiment, the characteristics of the above method include: sending the first failure message only when the first process is not in progress.

[0021] As an embodiment, the benefits of the above method include: shortening the information reporting time.

[0022] As an embodiment, the benefits of the above method include: reusing existing protocols.

[0023] As an embodiment, the problem to be solved by this application includes: content setting of the first failure message.

[0024] As an embodiment, the characteristics of the above method include: the first failure message indicates that the SCG connection fails.

[0025] As an embodiment, the benefits of the above method include: saving transmission resources.

[0026] As an embodiment, the problem to be solved by this application includes: how to determine the first process.

[0027] As an embodiment, the characteristics of the above method include: the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or a target cell of the MCG.

[0028] As an embodiment, the benefits of the above method include: being helpful in determining application scenarios.

[0029] As an embodiment, the problem to be solved by the present application includes: whether there is a restriction on sending the first failure message only when the first process is not in progress.

[0030] As an embodiment, the characteristics of the above method include: sending the first failure message only when the first process is not in progress and both the MCG and the SCG are not suspended.

[0031] As an embodiment, the benefits of the above method include: improving the robustness of information transmission.

[0032] According to one aspect of the present application, it is characterized in that whether to send the first failure message depends on whether the first process is in progress, including: when the first process is in progress, setting a first information block in a first UE variable; the first information block indicates that the SCG connection fails.

[0033] As an embodiment, the problem to be solved by the present application includes: when the first process is in progress, how to indicate that the SCG connection has failed.

[0034] As an embodiment, the characteristics of the above method include: when the first process is in progress, setting a first information block in the first UE variable; the first information block indicates that the SCG connection fails.

[0035] As an embodiment, the benefits of the above method include: saving signaling interaction.

[0036] As an embodiment, the benefits of the above method include: it is helpful to reduce the loss of important information.

[0037] According to one aspect of the present application, it is characterized in that the first failure message is sent as a response to the successful completion of the first process.

[0038] As an embodiment, the problem to be solved by this application includes: when to send the first failure message.

[0039] As an embodiment, the problem to be solved by the present application includes: when the first process is successfully completed, how to indicate that the SCG connection fails.

[0040] As an embodiment, the above method is characterized by: sending the first failure message as a response to the successful completion of the first process.

[0041] As an embodiment, the benefits of the above method include: it is helpful to reduce the storage of redundant information.

[0042] According to one aspect of the present application, it is characterized in that as a response to the successful completion of the first process, a second information block is set in the second UE variable; the second information block indicates that the SCG connection fails.

[0043] As an embodiment, the problem to be solved by the present application includes: when the first process is successfully completed, how to indicate that the SCG connection fails.

[0044] As an embodiment, the above method is characterized by: setting a second information block in a second UE variable as a response to the successful completion of the first process; the second information block indicates that the SCG connection has failed.

[0045] As an embodiment, the benefits of the above method include: being conducive to reducing new signaling design.

[0046] As an embodiment, the benefits of the above method include: being conducive to reusing existing protocols.

[0047] As an embodiment, the benefits of the above method include: being conducive to information optimization on the network side.

[0048] According to one aspect of the present application, it is characterized in that as a response to the failure of the first process, a third information block is set in a third UE variable; the third information block indicates that the SCG connection fails.

[0049] As an embodiment, the problem to be solved by the present application includes: when the first process fails, how to indicate that the SCG connection fails.

[0050] As an embodiment, the above method is characterized by: as a response to the failure of the first process, setting a third information block in a third UE variable; the third information block indicates that the SCG connection has failed.

[0051] As an embodiment, the benefits of the above method include: being conducive to reusing existing protocols.

[0052] As an embodiment, the benefits of the above method include: being conducive to information optimization on the network side.

[0053] According to one aspect of the present application, it is characterized by comprising:

[0054] In response to both the execution condition of the configuration information of the first cell and the execution condition of the configuration information of the second cell being satisfied, starting the first process;

[0055] Among them, the first RRC message includes the execution conditions of the configuration information of the first cell, the first RRC message includes the configuration information of the second cell and the execution conditions of the configuration information of the second cell, and the second cell is configured to the first cell; the second cell is a candidate cell or target cell of the SCG.

[0056] As an embodiment, the problem to be solved by the present application includes: when to start the first process.

[0057] As an embodiment, the above method is characterized by: starting the first process in response to both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being met.

[0058] As an embodiment, the problem to be solved by the present application includes: how to configure the execution conditions of the configuration information of the first cell and the second cell.

[0059] As an embodiment, the characteristics of the above method include: the first RRC message includes the execution conditions of the configuration information of the first cell, and the first RRC message includes the configuration information of the second cell and the execution conditions of the configuration information of the second cell.

[0060] As an embodiment, the problem to be solved by this application includes: the relationship between the second cell and the first cell.

[0061] As an embodiment, the features of the above method include: the second cell is configured to the first cell; the second cell is a candidate cell or a target cell of the SCG.

[0062] According to one aspect of the present application, it is characterized by comprising:

[0063] In response to both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being satisfied, applying the configuration information of the second cell;

[0064] Among them, the failure to apply the configuration information of the second cell triggers the determination of SCG connection failure.

[0065] As an embodiment, the problem to be solved by this application includes: when to apply the configuration information of the second cell.

[0066] As an embodiment, the above method is characterized by: in response to both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being met, applying the configuration information of the second cell.

[0067] As an embodiment, the benefits of the above method include: achieving fast connection of SCG.

[0068] As an embodiment, the problem to be solved by the present application includes: how to determine that the SCG connection fails.

[0069] As an embodiment, the above method is characterized by: failure to apply the configuration information of the second cell triggers the determination of SCG connection failure.

[0070] As an embodiment, the benefits of the above method include: facilitating rapid recovery of SCG.

[0071] As an embodiment, the benefits of the above method include: it is helpful to shorten the interruption time of communication.

[0072] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0073] Sending a first RRC message, where the first RRC message includes configuration information of the first cell;

[0074] In which, the receiver of the first RRC message determines that the SCG connection fails; as a response to the determination of the SCG connection failure, whether the receiver of the first RRC message sends a first failure message depends on whether the first process is in progress; whether the first failure message is sent depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection fails; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

[0075] According to one aspect of the present application, it is characterized in that whether the receiver of the first RRC message sends a first failure message depends on whether the first process is in progress, including: when the first process is in progress, setting a first information block in a first UE variable; the first information block indicates that the SCG connection fails.

[0076] According to one aspect of the present application, it is characterized in that, as a response to the successful completion of the first process, the recipient of the first RRC message sends the first failure message.

[0077] According to one aspect of the present application, it is characterized in that as a response to the successful completion of the first process, a second information block is set in the second UE variable; the second information block indicates that the SCG connection fails.

[0078] According to one aspect of the present application, it is characterized in that as a response to the failure of the first process, a third information block is set in a third UE variable; the third information block indicates that the SCG connection fails.

[0079] According to one aspect of the present application, it is characterized by comprising:

[0080] In response to both the execution condition of the configuration information of the first cell and the execution condition of the configuration information of the second cell being satisfied, the receiver of the first RRC message starts the first process;

[0081] Among them, the first RRC message includes the execution conditions of the configuration information of the first cell, the first RRC message includes the configuration information of the second cell and the execution conditions of the configuration information of the second cell, and the second cell is configured to the first cell; the second cell is a candidate cell or target cell of the SCG.

[0082] According to one aspect of the present application, it is characterized by comprising:

[0083] In response to both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being satisfied, the receiver of the first RRC message applies the configuration information of the second cell;

[0084] The failure to apply the configuration information of the second cell triggers the receiver of the first RRC message to determine that the SCG connection has failed.

[0085] The present application discloses a first node used for wireless communication, characterized by comprising:

[0086] A first receiver receives a first RRC message, where the first RRC message includes configuration information of a first cell;

[0087] The first processor determines that the SCG connection fails;

[0088] In which, as a response to the determination of the SCG connection failure, whether to send a first failure message depends on whether the first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

[0089] The present application discloses a second node used for wireless communication, characterized by comprising:

[0090] A second transmitter sends a first RRC message, where the first RRC message includes configuration information of the first cell;

[0091] In which, the receiver of the first RRC message determines that the SCG connection fails; as a response to the determination of the SCG connection failure, whether the receiver of the first RRC message sends a first failure message depends on whether the first process is in progress; whether the first failure message is sent depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection fails; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

[0092] As an embodiment, compared with the traditional solution, the present application has at least one of the following advantages:

[0093] -. It helps to reduce communication interruption caused by switching;

[0094] -. It is helpful to save storage resources;

[0095] -.It is conducive to improving cell handover performance;

[0096] -. It is conducive to network optimization and big data collection;

[0097] -.It is conducive to improving transmission capacity;

[0098] -. It is conducive to configuration optimization of conditional configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0099] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0100] Figure 1 A flow chart showing communication of a first node according to an embodiment of the present application is shown;

[0101] Figure 2 A schematic diagram showing a network architecture according to an embodiment of the present application is shown;

[0102] Figure 3 A schematic diagram illustrating an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application is shown;

[0103] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0104] Figure 5 shows a wireless signal transmission flow chart according to an embodiment of the present application;

[0105] Figure 6A flowchart of setting the first information block in the first UE variable according to an embodiment of the present application is shown;

[0106] Figure 7 A flowchart of sending the first failure message according to an embodiment of the present application is shown;

[0107] Figure 8 A flowchart of setting the second information block in the second UE variable according to an embodiment of the present application is shown;

[0108] Figure 9 A flowchart of setting a third information block in a third UE variable according to an embodiment of the present application is shown;

[0109] Figure 10 A flowchart of starting the first process according to an embodiment of the present application is shown;

[0110] Figure 11 A flowchart of determining SCG connection failure is shown, in which the configuration information application failure of the second cell triggers the SCG connection failure according to an embodiment of the present application;

[0111] Figure 12 A structural block diagram of a processing device used in a first node according to an embodiment of the present application is shown;

[0112] Figure 13 A structural block diagram of a processing device used in a second node according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0113] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other in any way.

[0114] Example 1

[0115] Example 1 illustrates a flow chart of communication of a first node according to an embodiment of the present application, as shown in the attached figure. Figure 1 As shown. Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal sequence between the steps represented.

[0116] In Example 1, the first node in the present application receives a first RRC message in step 101, and the first RRC message includes configuration information of the first cell; in step 102, it is determined that the SCG connection fails; wherein, as a response to the determination of the SCG connection failure, whether to send the first failure message depends on whether the first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection fails; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

[0117] As an embodiment, the first RRC message is UE-specific (UE-Specifc).

[0118] As an embodiment, the first RRC message is a cell common RRC message.

[0119] As an embodiment, the first RRC message is transmitted via a DCCH (Dedicated Control Channel).

[0120] As an embodiment, the first RRC message is transmitted via SCCH (Sidelink Control Channel).

[0121] As an embodiment, the first RRC message is transmitted via BCCH (Broadcast Control Channel).

[0122] As an embodiment, the first RRC message is transmitted via SRB1 (Signalling Radio Bearer 1).

[0123] As an embodiment, the first RRC message is transmitted via SRB3 (Signalling Radio Bearer 3).

[0124] As an embodiment, the first RRC message is transmitted via PDSCH (Physical Downlink Shared Channel).

[0125] As an embodiment, the first RRC message includes an RRCReconfiguration message.

[0126] As an embodiment, the first RRC message includes an RRCResume message.

[0127] As an embodiment, the first RRC message is an RRCReconfiguration message.

[0128] As an embodiment, the first RRC message is an RRCResume message.

[0129] As an embodiment, the first RRC message includes a conditionalReconfiguration message.

[0130] As an embodiment, the first RRC message includes an LTM-config message.

[0131] As an embodiment, the first RRC message is a conditionalReconfiguration message.

[0132] As an embodiment, the first RRC message is an LTM-config message.

[0133] As an embodiment, the first RRC message is an LTM-Candidate message.

[0134] As an embodiment, the first RRC message includes CellGroupConfig IE.

[0135] As an embodiment, the first RRC message includes a reconfigurationWithSync field.

[0136] As an embodiment, the first RRC message includes ServingCellConfig IE.

[0137] As an embodiment, the first RRC message only includes configuration information of the first cell.

[0138] As an embodiment, the first RRC message includes at least configuration information of the first cell.

[0139] As an embodiment, the configuration information of the first cell includes random access configuration information.

[0140] As an embodiment, the configuration information of the first cell includes measurement configuration information.

[0141] As an embodiment, the first RRC message includes the execution conditions of the first cell configuration information.

[0142] As an embodiment, the determination of SCG connection failure refers to: T304 for the SCG expires.

[0143] As an embodiment, the determination of SCG connection failure refers to: synchronous reconfiguration failure of the SCG (reconfiguration with sync failure of the SCG).

[0144] As an embodiment, determining that the SCG connection fails refers to detecting that an RLF (radio link failure) occurs in the SCG.

[0145] As an embodiment, determining that the SCG connection fails refers to: detecting that a BF (beam failure) occurs in the PSCell when the SCG is deactivated (deactivated).

[0146] As an embodiment, the determination of SCG connection failure refers to: SCG configuration failure (configuration failure).

[0147] As an embodiment, the determination of SCG connection failure refers to: when a lower layer signaling is received indicating that the SCG has failed.

[0148] As an embodiment, the determination of SCG connection failure refers to: failure to perform handover on the SCG.

[0149] As an embodiment, the determination of SCG connection failure refers to: failure to execute CPC or CPA on the SCG.

[0150] As an embodiment, the determination of SCG connection failure refers to: PSCell connection failure in the SCG.

[0151] As an embodiment, determining that the SCG connection fails triggers sending the first failure message.

[0152] As an embodiment, determining that the SCG connection fails and the first process is no longer in progress triggers sending of the first failure message.

[0153] As an embodiment, when it is determined that the SCG connection fails, whether to send the first failure information depends on whether the first process is in progress.

[0154] As an embodiment, when it is at least determined that the SCG connection fails, whether to send the first failure information depends on whether the first process is in progress.

[0155] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means that when the first process is in progress, the first failure message is not sent.

[0156] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means that when at least the first process is in progress, the first failure message is not sent.

[0157] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means: when the first process is in progress, the first failure message is sent.

[0158] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means: when at least the first process is in progress, the first failure message is sent.

[0159] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means that when the first process is not in progress, the first failure message is not sent.

[0160] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means that when at least the first process is not in progress, the first failure message is not sent.

[0161] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means: when the first process is not in progress, the first failure message is sent.

[0162] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means that when at least the first process is not in progress, the first failure message is sent.

[0163] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means: whether to initiate the SCG failure information (SCG Failure Information) process depends on whether the first process is in progress; the SCG failure information process includes sending the first failure message.

[0164] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, which means: when the first process is not in progress, the SCG failure information process is initiated; when the first process is in progress, the SCG failure information process is not initiated; the SCG failure information process includes sending the first failure message.

[0165] As an embodiment, the first process is a cell switching process.

[0166] As an embodiment, the first process is a PCell switching process.

[0167] As an embodiment, the first process is a handover process triggered by RRCReconfiguration including reconfigurationWithSync.

[0168] As an embodiment, the first process is a CHO process.

[0169] As an embodiment, the first process is an LTM cell switch process.

[0170] As an embodiment, the first process includes applying at least the configuration information of the first cell.

[0171] As an embodiment, the first process is to apply the configuration information of the first cell.

[0172] As an embodiment, the first process includes performing a random access process.

[0173] As an embodiment, the first process includes evaluating an execution condition.

[0174] As an embodiment, the first process includes: resetting the MAC entity of the MCG.

[0175] As an embodiment, the first process is a synchronous reconfiguration process, and the synchronous reconfiguration process includes applying the configuration information of the first cell. As an embodiment, the first process being performed means that T304 of the MCG is running.

[0176] As an embodiment, the first process being in progress means that the synchronous reconfiguration process of the MCG is in progress.

[0177] As an embodiment, the first process being performed means that the reconfigurationWithSync of MCG is being applied.

[0178] As an embodiment, the first process being in progress means that at least one action included in the first process is in progress; the first process not being in progress means that any action included in the first process is not in progress.

[0179] As an embodiment, the first process being in progress means that T304 of the MCG is running; the first process not being in progress means that T304 of the MCG is not running.

[0180] As an embodiment, the first process being in progress means that the synchronous reconfiguration process of the MCG is in progress; the first process not being in progress means that the synchronous reconfiguration process of the MCG is not in progress.

[0181] As an embodiment, the first process being in progress means that T311 of the MCG associated with the SCG is running.

[0182] As an embodiment, the first process being in progress means that the first process starts running and no instruction that the first process is not in progress is received.

[0183] As an embodiment, the first process being in progress means that the first process starts running and it is not determined that the first process is no longer in progress.

[0184] As an embodiment, sending the first failure message includes: setting the first failure message.

[0185] As a sub-embodiment of the above embodiment, the setting of the first failure message includes: setting the SCG connection failure type.

[0186] As a sub-embodiment of the above embodiment, the setting of the first failure message includes: setting the measurement result when the SCG connection fails.

[0187] As a sub-embodiment of the above embodiment, the setting of the first failure message includes: if the SCG is configured with a candidate configuration, setting a measurement result of the candidate configuration when the SCG connection fails.

[0188] As a sub-embodiment of the above embodiment, the setting of the first failure message includes: setting the measurement result of the neighboring cell when the SCG connection fails.

[0189] As a sub-embodiment of the above embodiment, the setting of the first failure message includes: setting locationInfo according to otherConfig configured in the MCG associated with the SCG.

[0190] As a sub-embodiment of the above embodiment, the setting of the first failure message includes: a field in the first failure message indicating that the SCG is configured as the MCG.

[0191] As a sub-embodiment of the above embodiment, the setting of the first failure message includes: a field in the first failure message indicating that the SCG is configured as a CHO-with candidate SCGs.

[0192] As an embodiment, the sending of the first failure message includes: suspending the SCG.

[0193] As an embodiment, sending the first failure message includes: resetting the MAC entity of the SCG.

[0194] As an embodiment, sending the first failure message includes: stopping the execution condition evaluation of the configuration information.

[0195] As a sub-embodiment of the above embodiment, the condition for stopping execution of the configuration information includes: stopping CPC condition evaluation.

[0196] As a sub-embodiment of the above embodiment, the condition for stopping execution of the configuration information includes: stopping CPA condition evaluation.

[0197] As a sub-embodiment of the above embodiment, the condition for stopping execution of the configuration information includes: stopping subsequent CPA / C condition evaluation.

[0198] As a sub-embodiment of the above embodiment, the condition for stopping execution of the configuration information includes: stopping CHO-with candidate SCGs condition evaluation.

[0199] As a sub-embodiment of the above embodiment, the condition for stopping execution of the configuration information includes: stopping SCG condition evaluation in the C-LTM.

[0200] As an embodiment, the sending of the first failure message includes: stopping T304 for the SCG.

[0201] As an embodiment, the sending of the first failure message includes: releasing the configured successPSCell-Config, if the SCG is configured.

[0202] As an embodiment, sending the first failure message includes: passing the first failure message to a lower layer.

[0203] As an embodiment, the first failure message indicating that the SCG connection has failed means that the first failure message is sent to indicate that the SCG connection has failed.

[0204] As an embodiment, the first failure message indicating the SCG connection failure means that the first failure message is set to indicate the SCG connection failure.

[0205] As an embodiment, the first failure message indicating the SCG connection failure means that the SCG connection failure triggers the initiation of the sending procedure of the first failure message.

[0206] As an embodiment, the first failure message indicating that the SCG connection has failed means that a field in the first failure message exists to indicate that the SCG connection has failed.

[0207] As an embodiment, the first failure message indicating that the SCG connection has failed means that a field in the first failure message is set to indicate that the SCG connection has failed.

[0208] As an embodiment, the first failure message indicating that the SCG connection has failed means that a field in the first failure message indicates the cell identifier of the PSCell in the SCG.

[0209] As an embodiment, the first failure message indicating that the SCG connection fails means that a field in the first failure message indicates the cell identifier of the candidate PSCell configured when the SCG connection fails.

[0210] As an embodiment, the first failure message indicating that the SCG connection has failed means that a field in the first failure message indicates the cause of the SCG connection failure.

[0211] As an embodiment, the first failure message indicating that the SCG connection fails means that: a field in the first failure message indicates the measurement result of the candidate cell configured when the SCG connection fails.

[0212] As an embodiment, the first failure message indicating that the SCG connection fails means that: the first failure message includes a first identity field, and the first identity field indicates that the SCG is in order to accompany the CHO.

[0213] As an embodiment, the name of the first identity domain includes CHO-WithSCG.

[0214] As an embodiment, the name of the first identity domain includes selectedPSCellForCHO-WithSCG.

[0215] As an embodiment, the first identity domain includes the cell identifier of the second candidate cell.

[0216] As an embodiment, the first identity domain includes the cell identifier of the first candidate cell.

[0217] As an embodiment, the first identity domain includes at least the cell identifier of the second candidate cell.

[0218] As an embodiment, the first identity field is set to True, indicating that the second candidate cell is configured to the first candidate cell.

[0219] As an embodiment, the first failure message includes SCGFailureInformation.

[0220] As an embodiment, the first failure message includes FailureInformation.

[0221] As an embodiment, the first failure message is SCGFailureInformation.

[0222] As an embodiment, the first failure message is SCGFailureInfomationNR.

[0223] As an embodiment, the first failure message is sent via MCG.

[0224] As an embodiment, the first failure message is sent via SRB1.

[0225] As an embodiment, the first failure message is sent via a sidelink (SL).

[0226] As an embodiment, the first failure message is sent through at least one cell outside the SCG.

[0227] As an embodiment, the first failure message is sent through at least one UE outside the SCG.

[0228] As an embodiment, the first RRC message includes a first configuration field, and the first configuration field includes the configuration information of the first cell.

[0229] As an embodiment, the first configuration domain is for conditional configuration.

[0230] As an embodiment, the first configuration domain is CHO.

[0231] As an embodiment, the first configuration domain is for LTM.

[0232] As an embodiment, the first configuration domain is for C-LTM.

[0233] As an embodiment, the first configuration domain is CHO-with target SCG.

[0234] As an embodiment, the first configuration domain is CHO-with candidate SCGs.

[0235] As an embodiment, the first configuration domain includes configuration information of a second cell, the second cell is configured to the first cell, the second cell is a candidate PSCell associated with the first cell, and the determination of the SCG connection failure depends on determining the second cell connection failure.

[0236] As an embodiment, the second cell is a target PSCell configured for the first cell.

[0237] As an embodiment, the second cell is the target cell or candidate cell of the SCG.

[0238] As an embodiment, the second cell is the current serving cell of the SCG.

[0239] As an embodiment, the first cell is a PCell, the second cell is a candidate PSCell configured for the first cell, and the first configuration domain is for CPA / C.

[0240] As an embodiment, the first cell is a candidate PCell, the second cell is a candidate PSCell configured for the first cell, and the first configuration domain is CHO-with candidate SCGs.

[0241] As an embodiment, the first cell is a candidate PCell, the second cell is a target PSCell configured for the first cell, and the first configuration domain is CHO-with target SCGs.

[0242] As an embodiment, the determining that the SCG connection failure depends on determining the second cell connection failure means that the determining that the second cell connection failure is used to determine the SCG connection failure.

[0243] As an embodiment, the second cell connection failure refers to: RLF occurs on the second cell.

[0244] As an embodiment, the second cell connection failure refers to: failure to initiate connection reestablishment on the second cell.

[0245] As an embodiment, the second cell connection failure means that the second cell is deactivated.

[0246] As an embodiment, the determination that the SCG connection failure depends on the second cell means that the configuration information of the second cell is not successfully applied to determine the SCG connection failure.

[0247] As an embodiment, the configuration information of the second cell is not successfully applied, which means that the configuration information of the second cell fails to be configured.

[0248] As an embodiment, the configuration information of the second cell is not successfully applied, which means that the random access process initiated to the second cell fails.

[0249] As an embodiment, the configuration information of the second cell is not successfully applied, which means that the scheduling information is not monitored on the designated time-frequency resources.

[0250] As an embodiment, the configuration information of the second cell is not successfully applied, which means that T304 corresponding to the second cell expires.

[0251] As an embodiment, the configuration information of the second cell is not successfully applied, which means that HOF occurs in the second cell.

[0252] As an embodiment, the first cell is a candidate cell.

[0253] As an embodiment, the first cell is determined by the first node based on measurement.

[0254] As an embodiment, the first cell is a C-LTM candidate cell.

[0255] As an embodiment, the first cell is a CHO candidate cell.

[0256] As an embodiment, the first cell is a subsequent candidate cell.

[0257] As an embodiment, the first cell is a target cell.

[0258] As an embodiment, the first cell is a target PCell.

[0259] As an embodiment, the first cell is indicated by the second node.

[0260] As an embodiment, the first cell is a candidate cell or a target cell of the MCG, and the MCG is associated with the SCG.

[0261] As an embodiment, the MCG and the SCG are not suspended, which means that when the first failure message is sent, the MCG and the SCG are not suspended.

[0262] As an embodiment, the MCG and the SCG are both not suspended, which means that the first failure message is sent only when the MCG and the SCG are both not suspended.

[0263] As an embodiment, the MCG and the SCG are both not suspended, which means: when at least the MCG and the SCG are both not suspended, the first failure message is sent.

[0264] As an embodiment, the MCG and the SCG are not suspended, which means that: when the first failure message is set, the SCG is not suspended; when the first failure message is sent, the MCG is not suspended.

[0265] As an embodiment, a first receiver receives a first RRC message, which includes configuration information of the first cell; a first processor determines that the SCG connection fails; as a response to the determination of the SCG connection failure, the first failure message is sent only when the MCG and the SCG are not suspended and the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell belongs to the MCG.

[0266] As an embodiment, a first receiver receives a first RRC message, which includes configuration information of the first cell and a second cell; the second cell is a candidate PSCell configured for the first cell, and the configuration information of the second cell is not successfully applied to determine that the SCG connection fails; as a response to the SCG connection failure, the first failure message is sent only when the MCG and the SCG are not suspended and the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell belongs to the MCG.

[0267] Example 2

[0268] Example 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached diagram. Figure 2 As shown. Figure 2The network architecture 200 of a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system is illustrated. The 5G NR / LTE / LTE-A network architecture 200 may be referred to as a 5G System (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 includes at least one of a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5G Core Network (5G Core Network) / EPC (Evolved Packet Core) 210, a Home Subscriber Server (HSS) / Unified Data Management (UDM) 220, and an Internet service 230. The 5GS / EPS may interconnect with other access networks, but for simplicity, these entities / interfaces are not shown. As shown, the 5GS / EPS provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination towards UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (transmitter receive node), or some other appropriate terminology. Node 203 provides an access point to the 5GC / EPC 210 for UE 201. Examples of UE 201 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.Node 203 connects to the 5GC / EPC 210 via the S1 / NG interface. The 5GC / EPC 210 includes the MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, the S-GW (Service Gateway) / UPF (User Plane Function) 212, and the P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that handles signaling between the UE 201 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF 212, which itself is connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 is connected to the Internet Services 230. The Internet Services 230 includes the operator's corresponding Internet Protocol services, which may include the Internet, Intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0269] As an embodiment, the UE201 corresponds to the first node in this application.

[0270] As an embodiment, the UE 201 is a user equipment (UE).

[0271] As an embodiment, the UE 201 is a base station (BS).

[0272] As an embodiment, the UE 201 is a relay device.

[0273] As an embodiment, the UE 201 is a gateway device.

[0274] As an embodiment, the node 203 corresponds to the second node in this application.

[0275] As an embodiment, the node 203 is a base station device.

[0276] As an embodiment, the node 203 is a user equipment.

[0277] As an embodiment, the node 203 is a relay device.

[0278] As an embodiment, the node 203 is a gateway device.

[0279] Typically, the UE 201 is a user equipment, and the node 203 is a base station device.

[0280] Typically, the UE 201 is a user equipment, and the node 203 is a user equipment.

[0281] Typically, the UE 201 is a base station device, and the node 203 is a base station device.

[0282] As an embodiment, the user equipment supports transmission of a non-terrestrial network (NTN).

[0283] As an embodiment, the user equipment supports transmission via a terrestrial network (Terrestrial Network).

[0284] As an embodiment, the user equipment supports dual connection (DC) transmission.

[0285] As an embodiment, the user equipment includes an aircraft.

[0286] As an embodiment, the user equipment includes a vehicle-mounted terminal.

[0287] As an embodiment, the user equipment includes a vessel.

[0288] As an embodiment, the user equipment includes an Internet of Things terminal.

[0289] As an embodiment, the user equipment includes a terminal of the Industrial Internet of Things.

[0290] As an embodiment, the user equipment includes a device that supports low-latency and high-reliability transmission.

[0291] As an embodiment, the user equipment includes a test device.

[0292] As an embodiment, the user equipment includes a signaling tester.

[0293] As an embodiment, the user equipment includes an IAB (Integrated Access and Backhaul)-MT.

[0294] As an embodiment, the user equipment supports dynamic switching using AI (Artificial Intelligence) or machine learning (Machine Learning).

[0295] As an embodiment, the user equipment supports generating a trained model using training data or generating part of the parameters in the trained model using trained data.

[0296] As an embodiment, the user equipment supports applying the first RRC message through training.

[0297] As an embodiment, the user equipment supports determining at least part of the information in the first RRC message through training.

[0298] As an embodiment, the user equipment is a terminal supporting Massive-MIMO.

[0299] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0300] As an embodiment, the base station device supports transmission of a terrestrial network.

[0301] As an embodiment, the base station equipment includes a base transceiver station (Base Transceiver Station, BTS).

[0302] As an embodiment, the base station device includes a Node B (NB).

[0303] As an embodiment, the base station device includes a gNB.

[0304] As an embodiment, the base station device includes an eNB.

[0305] As an embodiment, the base station device includes ng-eNB.

[0306] As an embodiment, the base station device includes an en-gNB.

[0307] As an embodiment, the base station device includes a CU (Centralized Unit).

[0308] As an embodiment, the base station device includes a DU (Distributed Unit).

[0309] As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).

[0310] As an embodiment, the base station device includes a macro cellular (Marco Cellular) base station.

[0311] As an embodiment, the base station device includes a micro cell base station.

[0312] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.

[0313] As an embodiment, the base station device includes a home base station (Femtocell).

[0314] As an embodiment, the base station device includes a flying platform device.

[0315] As an embodiment, the base station device includes a satellite device.

[0316] As an embodiment, the base station device includes a testing device.

[0317] As an embodiment, the base station equipment includes a signaling tester.

[0318] As an embodiment, the base station device includes a gateway device.

[0319] As an embodiment, the base station device includes an IAB-node.

[0320] As an embodiment, the base station device includes an IAB-donor.

[0321] As an embodiment, the base station device includes an IAB-donor-CU.

[0322] As an embodiment, the base station device includes an IAB-donor-DU.

[0323] As an embodiment, the base station device includes an IAB-DU.

[0324] As an embodiment, the base station device includes an IAB-MT.

[0325] As an embodiment, the base station device supports transmission based on Massive-MIMO.

[0326] As an embodiment, the base station device supports decompression of CSI using AI or deep learning.

[0327] As an embodiment, the base station device supports mobility management using AI or deep learning.

[0328] Example 3

[0329] Example 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached figure. Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture for control plane 300 is shown using three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. Layer 2 (L2 layer) 305, located above PHY 301, includes the MAC (Medium Access Control) sublayer 302, the RLC (Radio Link Control) sublayer 303, and the PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets and supports handover. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3) of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling. The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The radio protocol architecture in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355. However, the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for mapping between QoS flows and data radio bearers (DRBs) to support service diversity.

[0330] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0331] As an example, Figure 3The wireless protocol architecture in is applicable to the second node in this application.

[0332] As an embodiment, the first RRC message in this application is generated in the RRC306.

[0333] As an embodiment, the first failure message in the present application is generated in the RRC306.

[0334] As an embodiment, the first information block in the first UE variable in the present application is set in the RRC306.

[0335] As an embodiment, the first information block in the first UE variable in the present application is set in the MAC302 or MAC352.

[0336] As an embodiment, the second information block in the second UE variable in the present application is set in the RRC306.

[0337] As an embodiment, the second information block in the second UE variable in the present application is set in the MAC302 or MAC352.

[0338] As an embodiment, the third information block in the third UE variable in the present application is set in the RRC306.

[0339] As an embodiment, the third information block in the third UE variable in the present application is set in the MAC302 or MAC352.

[0340] Example 4

[0341] Example 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in the attached figure. Figure 4 shown. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0342] The first communication device 450 includes a controller / processor 459 , a memory 460 , a data source 467 , a transmit processor 468 , a receive processor 456 , a multi-antenna transmit processor 457 , a multi-antenna receive processor 458 , a transmitter / receiver 454 and an antenna 452 .

[0343] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 , and an antenna 420 .

[0344] During transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to the controller / processor 475 at the second communication device 410. The controller / processor 475 implements L2 layer functionality. During transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0345] During transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal via its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various L1 signal processing functions. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream, after the receive analog precoding / beamforming operations, from the time domain to the frequency domain using a fast Fourier transform (FFT). In the frequency domain, the receive processor 456 demultiplexes the physical layer data signal and reference signal, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. During transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 layer for L3 processing.

[0346] During transmission from the first communication device 450 to the second communication device 410, a data source 467 is used at the first communication device 450 to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission functionality at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding, while the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming. The transmit processor 468 then modulates the resulting spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding and beamforming operations in the multi-antenna transmit processor 457, the stream is provided to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a RF symbol stream before providing it to the antenna 452.

[0347] During transmission from the first communications device 450 to the second communications device 410, the functionality at the second communications device 410 is similar to the reception functionality at the first communications device 450 described for transmission from the second communications device 410 to the first communications device 450. Each receiver 418 receives RF signals via its corresponding antenna 420, converts the received RF signals into baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement L1 layer functionality. A controller / processor 475 implements L2 layer functionality. The controller / processor 475 may be associated with a memory 476 storing program codes and data. The memory 476 may be referred to as a computer-readable medium. During transmission from the first communications device 450 to the second communications device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0348] As an embodiment, the first communication device 450 corresponds to the first node in the present application; the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 at least: the first RRC message includes configuration information of the first cell; determines the SCG connection failure; wherein, as a response to the determination of the SCG connection failure, whether to send the first failure message depends on whether the first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended. As an embodiment, the first communication device 450 corresponds to the first node in the present application; the first communication device 450 includes: a memory storing a computer-readable instruction program, and the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: the first RRC message includes the configuration information of the first cell; determining that the SCG connection fails; wherein, as a response to the determination of the SCG connection failure, whether to send the first failure message depends on whether the first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection fails; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

[0349] As an embodiment, the second communication device 410 corresponds to the second node in the present application; the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 410 at least: sends a first RRC message, the first RRC message including configuration information of a first cell; wherein the recipient of the first RRC message determines that the SCG connection fails; as a response to the determination of the SCG connection failure, whether the recipient of the first RRC message sends a first failure message depends on whether a first process is in progress; whether the first failure message is sent depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, the first cell is a candidate cell or a target cell of the MCG; neither the MCG nor the SCG is suspended.

[0350] As an embodiment, the second communication device 410 corresponds to the second node in the present application; the second communication device 410 includes: a memory storing a computer-readable instruction program, and the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: sending a first RRC message, and the first RRC message includes configuration information of the first cell; wherein, the recipient of the first RRC message determines that the SCG connection fails; as a response to the determination of the SCG connection failure, whether the recipient of the first RRC message sends the first failure message depends on whether the first process is in progress; whether the first failure message is sent depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

[0351] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a first RRC message.

[0352] As an embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive a first RRC message.

[0353] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 is used to send a first failure message.

[0354] As an embodiment, at least one of the antenna 420, the receiver 418, the reception processor 470, and the controller / processor 475 is configured to receive a first failure message.

[0355] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0356] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0357] As an embodiment, the first communication device 450 is a user equipment.

[0358] As an embodiment, the first communication device 450 is a base station device.

[0359] As an embodiment, the first communication device 450 is a relay device.

[0360] As an embodiment, the second communication device 410 is a user equipment.

[0361] As an embodiment, the second communication device 410 is a base station device.

[0362] As an embodiment, the second communication device 410 is a relay device.

[0363] Example 5

[0364] Example 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached figure. Figure 5 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0365] for First node U01 In step S5101, a first RRC message is received, wherein the first RRC message includes configuration information of a first cell; in step S5102, it is determined that the SCG connection has failed; in step S5103, it is determined whether the first process is in progress; in step S5104, a first failure message is sent, wherein the first failure message indicates that the SCG connection has failed.

[0366] for Second node N02 , in step S5201, the first RRC message is sent.

[0367] for The third node N03 , in step S5301, a first failure message is received.

[0368] In Example 5, as a response to the determination of the SCG connection failure, whether to send a first failure message depends on whether a first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or a target cell of the MCG; neither the MCG nor the SCG is suspended.

[0369] As an embodiment, the first node is a UE.

[0370] As an embodiment, the first node is a UE supporting 3GPP R19.

[0371] As an embodiment, the first node is a UE supporting 6G.

[0372] As an embodiment, the first node U01 and the second node N02 are connected wirelessly.

[0373] As an embodiment, the first node U01 and the second node N02 are connected via a wired connection.

[0374] As an embodiment, the first node U01 and the second node N02 are connected via a Uu port.

[0375] As an embodiment, the first node U01 and the second node N02 are connected via an IAB port.

[0376] As an embodiment, the first node U01 and the second node N02 are connected via a PC5 interface.

[0377] As an embodiment, the third node N03 and the second node N02 are connected via a wireless interface.

[0378] As an embodiment, the third node N03 and the second node N02 are connected via a wired interface.

[0379] As an embodiment, the third node N03 and the second node N02 are connected via an Xn interface.

[0380] As an embodiment, the third node N03 and the second node N02 are connected via an X2 interface.

[0381] As an embodiment, the backhaul between the third node N03 and the second node N02 is ideal.

[0382] As an embodiment, the backhaul between the third node N03 and the second node N02 is non-ideal.

[0383] As an embodiment, the third node N03 is the second node N02.

[0384] As an embodiment, the third node N03 is not the second node N02.

[0385] As an embodiment, the third node N03 and the second node N02 belong to different CUs.

[0386] As an embodiment, the third node N03 and the second node N02 belong to the same CU.

[0387] As an embodiment, the third node N03 is a MN (Master Node).

[0388] As an embodiment, the third node N03 is a source MN, and the second node N02 is a source SN.

[0389] As an embodiment, the third node N03 is a maintaining base station of the first cell, and the second node N02 is a source MN.

[0390] As an embodiment, the third node N03 is a maintaining base station of the first cell, and the second node N02 is a source SN.

[0391] As an embodiment, the second node N02 is a base station maintaining the cell served by the first node U01.

[0392] As an embodiment, the third node N03 is a base station maintaining the candidate cell configured by the first node U01.

[0393] As an embodiment, the third node N03 is a maintaining base station of the target cell.

[0394] As an embodiment, in response to receiving the first failure message, the third node N03 forwards the first failure message to the second node.

[0395] As an embodiment, in response to receiving the first failure message, the third node N03 forwards at least part of the first information block in the first UE variable included in the first failure message to the second node N02.

[0396] As an embodiment, according to the instruction in the first failure message, the third node N03 forwards at least part of the information in the first failure message to the second node.

[0397] As an embodiment, according to an instruction in the first failure message, the third node N03 forwards at least part of the information in the first information block in the first failure message to the second node.

[0398] As an embodiment, the first node receives a first RRC message.

[0399] As an embodiment, the sender of the first RRC message is the maintaining base station of the first cell.

[0400] As an embodiment, the sender of the first RRC message is a base station maintaining a service cell of the first node.

[0401] As an embodiment, the sender of the first RRC message and the receiver of the first failure message are the same.

[0402] As an embodiment, the sender of the first RRC message and the receiver of the first failure message are different.

[0403] As an embodiment, after receiving the first RRC message, the first node starts to evaluate the execution conditions of the configuration information of the first cell.

[0404] As an embodiment, after receiving the first RRC message, the first node starts to apply the configuration information of the first cell.

[0405] As an embodiment, after receiving the first RRC message, the first node starts to evaluate the execution conditions of at least the configuration information of the first cell.

[0406] As an embodiment, after receiving the first RRC message, the first node starts to apply at least the configuration information of the first cell.

[0407] As an embodiment, the first node connects to the first cell after receiving the first RRC message.

[0408] As an embodiment, the connection is to perform a handover.

[0409] As an embodiment, the connection is to perform a switch.

[0410] As an embodiment, the connection is to perform initial access.

[0411] As an embodiment, the connection performs random access.

[0412] As an embodiment, the connection is a reconnection.

[0413] As an embodiment, the first node determines that the SCG connection fails.

[0414] As an embodiment, the first node determines that the SCG connection failure depends on the reception of the first RRC message.

[0415] As an embodiment, the first RRC message includes configuration information of at least the second cell.

[0416] As an embodiment, the first RRC message includes at least the configuration information of the second cell and the execution conditions of the configuration information of the second cell; after the first node receives the first RRC message, it starts to evaluate the execution conditions of at least the configuration information of the second cell.

[0417] As an embodiment, after receiving the first RRC message, the first node starts to apply the configuration information of the second cell.

[0418] As an embodiment, after receiving the first RRC message, the first node connects to the configuration information of the second cell.

[0419] As an embodiment, the second cell is a cell in the SCG.

[0420] As an embodiment, the second cell is the PSCell of the SCG.

[0421] As an embodiment, the SCG is a target SCG, and the second cell is a target PSCell.

[0422] As an embodiment, the SCG is a candidate SCG, and the second cell is a candidate PSCell.

[0423] As an embodiment, the first node generates an RLF on the second cell and determines that the SCG connection fails.

[0424] As an embodiment, the first node is not connected to the second cell, and it is determined that the SCG connection fails.

[0425] As an embodiment, the SCG is a current serving SCG, and after receiving the first RRC message, the first node determines that the SCG connection fails.

[0426] As an embodiment, the SCG is a current serving SCG, and after applying the configuration information of the first cell, the first node determines that the SCG connection fails.

[0427] As an embodiment, the first node determines whether the first process is in progress.

[0428] As an embodiment, determining whether the first process is in progress includes: determining that the first process is in progress.

[0429] As an embodiment, determining whether the first process is in progress includes: determining that the first process is not in progress.

[0430] As an embodiment, the first node determines whether the first process is in progress depending on whether a timer related to the first process is running.

[0431] As a sub-embodiment of the above embodiment, the timer related to the first process is T304.

[0432] As a sub-embodiment of the above embodiment, the timer related to the first process is a timer other than T304.

[0433] As an embodiment, the first node determines whether the first process is being performed depending on whether the configuration information of the first cell is applied.

[0434] As a sub-embodiment of the above embodiment, when the configuration information of the first cell is not applied, it is determined that the first process is not in progress.

[0435] As a sub-embodiment of the above embodiment, when the configuration information of the first cell is applied, the first node determines that the first process is in progress.

[0436] As an embodiment, the dotted box F5.1 is optional.

[0437] As an example, the dotted box F5.1 exists.

[0438] As an embodiment, the first node sends the first failure message.

[0439] As an embodiment, the first node determines that the SCG connection fails and sends the first failure message.

[0440] As an embodiment, the first node determines that the SCG connection fails and the MCG and the SCG are not suspended, and sends the first failure message.

[0441] As an embodiment, the first node determines that the SCG connection fails and determines that the first process is not in progress, and the first node sends the first failure message.

[0442] As an embodiment, the first node determines that the SCG connection fails and the MCG and the SCG are not suspended and determines that the first process is not in progress, and the first node sends the first failure message.

[0443] As an embodiment, the first node determines that the SCG connection fails and determines that the first process is in progress and the first process is successfully completed, and the first node sends the first failure message.

[0444] As an embodiment, the first node determines that the SCG connection fails and determines that the first process is in progress and the first process is successfully completed within a period of time, and the first node sends the first failure message.

[0445] As an embodiment, the dotted box F5.1 does not exist.

[0446] As an embodiment, the first node does not send the first failure message.

[0447] As an embodiment, the first node determines that the SCG connection fails and does not send the first failure message.

[0448] As an embodiment, the first node determines that the SCG connection fails and the first process is not in progress, and the first node does not send the first failure message.

[0449] As an embodiment, the first node determines that the SCG connection fails and the first process is in progress and the first process is successfully completed, and the first node does not send the first failure message.

[0450] As an embodiment, the first node determines that the SCG connection fails and the first process is in progress and the first process is successfully completed within a period of time, and the first node does not send the first failure message.

[0451] As an embodiment, the first node sets a first information block in the first UE variable.

[0452] As an embodiment, the first UE variable is set for the SCG connection failure.

[0453] As an embodiment, the first node determines that the SCG connection fails and sets a first information block in the first UE variable.

[0454] As an embodiment, the first node determines that the SCG connection fails and the first process is in progress, and sets a first information block in the first UE variable.

[0455] As an embodiment, the first node sets a second information block in the second UE variable.

[0456] As an embodiment, the second UE variable is set so that the first process is successfully completed.

[0457] As an embodiment, the first node determines that the SCG connection fails and the first process is in progress and the first process is successfully completed, and sets a second information block in the second UE variable.

[0458] As an embodiment, the first node determines that the SCG connection fails and the first process is in progress and the first process is successfully completed within a period of time, and sets a second information block in the second UE variable.

[0459] As an embodiment, the first node sets a third information block in the third UE variable.

[0460] As an embodiment, the setting of the third UE variable causes the first process to fail.

[0461] As an embodiment, the first node determines that the SCG connection fails and the first process is in progress and the first process fails, and sets a third information block in the third UE variable.

[0462] Example 6

[0463] Embodiment 6 illustrates a flowchart of setting the first information block in the first UE variable according to an embodiment of the present application, as shown in the attached Figure 6 shown.

[0464] In step S6101, determine that the SCG connection fails; in step S6102, determine whether the first process is in progress; in step S6103, when the first process is in progress, set the first information block in the first UE variable; in step S6104, when the first process is not in progress, send the first failure message.

[0465] In Example 6, whether to send the first failure message depends on whether the first process is in progress, including: when the first process is in progress, setting a first information block in a first UE variable; the first information block indicates that the SCG connection has failed.

[0466] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, including: when the first process is in progress, not sending the first failure message.

[0467] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, including: when the first process is in progress, not sending the first failure message and setting the first information block in the first UE variable.

[0468] As an embodiment, setting the first information block in the first UE variable refers to: setting the content of the first information block in the first UE variable.

[0469] As an embodiment, setting the first information block in the first UE variable means: setting at least the first information block in the first UE variable.

[0470] As an embodiment, the first information block is set in the first UE variable to indicate that the SCG connection fails.

[0471] As an embodiment, the first information block set in the first UE variable includes information included in the first failure message.

[0472] As an embodiment, the first information block set in the first UE variable includes at least part of the information included in the first failure message.

[0473] As an embodiment, the first UE variable is VarRLF-Report.

[0474] As an embodiment, the name of the first UE variable includes Var.

[0475] As an embodiment, the name of the first UE variable includes PSCell.

[0476] As an embodiment, the name of the first UE variable includes SCG.

[0477] As an embodiment, the first UE variable is not VarRLF-Report.

[0478] As an embodiment, the first UE variable is dedicated to the SCG.

[0479] As an embodiment, the first UE variable fails for the SCG connection.

[0480] As an embodiment, the first information block is RLF-Report.

[0481] As an embodiment, the first information block is not RLF-Report.

[0482] As an embodiment, the first information block is dedicated to the PSCell in the SCG.

[0483] As an embodiment, the first information block fails for the SCG connection.

[0484] As an embodiment, the SCG connection failure refers to detecting that the SCG connection failure occurs.

[0485] As an embodiment, the SCG connection failure refers to determining that the SCG connection failure occurs.

[0486] As an embodiment, the SCG connection failure refers to an SCG handover failure accompanied by CHO.

[0487] As an embodiment, the SCG connection failure refers to a cell connection failure in the SCG.

[0488] As an embodiment, the cell is the target PSCell when the SCG is detected to have a connection failure.

[0489] As an embodiment, the cell is the PSCell when the SCG is detected to have connection failure.

[0490] As an embodiment, the cell is the cell being served when the SCG is detected to have a connection failure.

[0491] As an embodiment, the connection failure refers to: radio link failure (RLF).

[0492] As an embodiment, the connection failure refers to handover failure (HOF).

[0493] As an embodiment, the connection failure refers to: connection reestablishment failure.

[0494] As an embodiment, the connection failure refers to: beam recovery failure.

[0495] As an embodiment, the first information block indicating that the SCG connection fails includes: the first information block indicating the cell identifier of the PSCell in the SCG.

[0496] As an embodiment, the cell identifier is a logical identifier.

[0497] As an embodiment, the cell identifier includes NCGI (NR Cell Global Identifier).

[0498] As an embodiment, the cell identifier includes a CGI (Cell Global Identifier).

[0499] As an embodiment, the cell identifier includes SNPN (Stand-alone Non-Public Network).

[0500] As an embodiment, the cell identifier includes a PLMN (Public Land Mobile Network).

[0501] As an embodiment, the cell identifier includes one of NCGI, CGI, and PLMN.

[0502] As an embodiment, the cell identifier includes PLMN and CGI.

[0503] As an embodiment, the cell identifier is a bit string.

[0504] As an embodiment, the cell identifier uniquely indicates any cell within a tracking area.

[0505] As an embodiment, the cell identifier uniquely indicates any one of the cells in multiple tracking areas.

[0506] As an embodiment, the cell identifier uniquely indicates any cell within a PLMN.

[0507] As an embodiment, the cell identifier uniquely indicates any one of the cells in multiple PLMNs.

[0508] As an embodiment, the cell identifier uniquely indicates any cell within a SNPN.

[0509] As an embodiment, the cell identifier uniquely indicates any one of the cells within multiple SNPNs.

[0510] As an embodiment, the cell identity includes a global cell identity (CellGlobal Identity) of the PSCell in the SCG.

[0511] As an embodiment, the cell identifier is the global cell identifier and tracking area code (Tracking Area Code) of the PSCell in the SCG.

[0512] As an embodiment, the cell identifier includes the PCI (Physical Cell Identity) of the PSCell in the SCG.

[0513] As an embodiment, the cell identifier is the PCI and carrier frequency (Carrier Frequency) of the PSCell in the SCG.

[0514] As an embodiment, if the global cell identifier and tracking area code of the PSCell in the SCG are available, the cell identifier is the global cell identifier and tracking area code of the PSCell in the SCG; otherwise, the cell identifier is the PCI of the PSCell in the SCG.

[0515] As an embodiment, the first information block indicating that the SCG connection fails includes: the first information block indicating measurement results available when the SCG connection fails.

[0516] As an embodiment, the first information block indicates the measurement results available when the SCG connection fails, which means: the first field of the first information block indicates the measurement results of the candidate cell when the SCG connection fails, if the configuration information of multiple candidate cells is available when the SCG connection fails.

[0517] As an embodiment, the first information block indicates that the measurement results available when the SCG connection fails, which means that the first field of the first information block indicates the measurement results of the neighboring cells when the SCG connection fails.

[0518] As an embodiment, the first information block indicates that the measurement results available when the SCG connection fails, which means that the first field of the first information block indicates the measurement results of the connected PSCell or source PSCell when the SCG connection fails.

[0519] As an embodiment, the measurement result includes one of an L1 or L3 measurement result.

[0520] As an embodiment, the measurement results include L1 and L3 measurement results.

[0521] As an embodiment, the measurement result includes SINR.

[0522] As an embodiment, the measurement result includes RSRP.

[0523] As an embodiment, the measurement result includes RSRQ.

[0524] As an embodiment, the measurement result includes RSSI.

[0525] As an embodiment, the measurement result includes at least one of SINR, RSRP, RSRQ, and RSSI.

[0526] As an embodiment, the measurement result depends on at least one of SS / PBCH or CSI-RS.

[0527] As an embodiment, the measurement result depends on the PRS.

[0528] As an embodiment, the measurement result relies on a dedicated reference signal.

[0529] As an embodiment, the first information block indicating that the SCG connection fails includes: the first information block includes a first time domain.

[0530] As an embodiment, the first time domain includes: the time interval from the last execution of switching to the SCG to the failure of the SCG connection.

[0531] As a sub-embodiment of the above embodiment, the start time of the first time domain depends on the time of the last switch to the SCG.

[0532] As a sub-embodiment of the above embodiment, the time of the last switching to the SCG refers to: the time when the configuration information of the SCG is received.

[0533] As a sub-embodiment of the above embodiment, the time of the last execution of switching to the SCG refers to: the time when the SCG configuration information begins to be applied.

[0534] As a sub-embodiment of the above embodiment, the time of the last execution switching to the SCG refers to the time when the execution condition of the configuration information of the SCG is met.

[0535] As a sub-embodiment of the above embodiment, the time of the last execution of switching to the SCG refers to: the time when the configuration information of the SCG is applied.

[0536] As a sub-embodiment of the above embodiment, the time of the last execution of switching to the SCG refers to: the time when the switching to the SCG is started.

[0537] As a sub-embodiment of the above embodiment, the time of the last switching to the SCG refers to: the time of initiating random access to the SCG.

[0538] As a sub-embodiment of the above embodiment, the time of the last switching to the SCG refers to the time when the random access process initiated to the SCG is completed.

[0539] As a sub-embodiment of the above embodiment, the deadline of the first time domain depends on the time when the SCG connection fails.

[0540] As a sub-embodiment of the above embodiment, the time when the SCG connection fails refers to: determining the time when the SCG connection fails.

[0541] As a sub-embodiment of the above embodiment, the time when the SCG connection fails refers to the time when the SCG is instructed to be deactivated.

[0542] As a sub-embodiment of the above embodiment, the time when the SCG connection fails refers to: the time when the configuration information of the SCG is instructed to be released.

[0543] As a sub-embodiment of the above embodiment, the time of the SCG connection failure refers to: the time of notifying the lower layer of the SCG connection failure message.

[0544] As an embodiment, the first information block indicating that the SCG connection fails includes: the first information block includes the first identity field, and the first identity field indicates that the SCG is for accompanying CHO switching.

[0545] As an embodiment, the first information block includes partial information of the first failure message.

[0546] As an embodiment, a field of the first information block includes all information of the first failure message.

[0547] As an embodiment, setting the first information block in the first UE variable depends on the first RRC configuration.

[0548] As an embodiment, when the first RRC configuration is set, the content of the UE variable is set.

[0549] As an embodiment, when the first RRC configuration is set, a first information block is set in the first UE variable.

[0550] As an embodiment, when the first RRC configuration is set, a first information block is set in at least the first UE variable.

[0551] As an embodiment, the first RRC configuration belongs to SON-Parameters.

[0552] As an embodiment, the first RRC configuration is set to supported.

[0553] As an embodiment, the first RRC configuration is otherConfig IE.

[0554] As an embodiment, the first RRC configuration belongs to otherConfig IE.

[0555] As an embodiment, the first RRC configuration is set to setup.

[0556] As an embodiment, the first RRC configuration is set to true.

[0557] Example 7

[0558] Example 7 illustrates a flowchart of sending the first failure message according to an embodiment of the present application, as shown in the attached Figure 7 shown.

[0559] In step S7101, it is determined that the SCG connection fails; in step S7102, the first process is successfully completed; in step S7103, the first failure message is sent.

[0560] In Example 7, the first failure message is sent as a response to the successful completion of the first process.

[0561] As an embodiment, when it is determined that the SCG connection fails, the first process is in progress.

[0562] As an embodiment, in response to determining that the SCG connection has failed, the first failure message is sent when the first process is successfully completed.

[0563] As an embodiment, as a response to determining that the SCG connection has failed, when the first process is in progress, a first timer is started, and when the first timer has not expired, the first failure message is sent as a response to the successful completion of the first process.

[0564] As an embodiment, the length of the first timer is a default length.

[0565] As an embodiment, the length of the first timer depends on the first signaling.

[0566] As an embodiment, the first signaling is an RRC layer signaling.

[0567] As an embodiment, the first signaling is a lower layer signaling.

[0568] As an embodiment, the first signaling includes a field set to the length of the first timer.

[0569] As an embodiment, the first signaling activates the configuration of the first timer.

[0570] As an embodiment, the start time of the first timer depends on the first signaling.

[0571] As an embodiment, the start condition of the first timer is set in the first signaling.

[0572] As an embodiment, the starting condition of the first timer is a default condition.

[0573] As an embodiment, the start time of the first timer depends on the time when the SCG connection failure is determined.

[0574] As an embodiment, the first timer is started in response to determining that the SCG connection has failed.

[0575] As an embodiment, when it is determined that the SCG connection fails, the first timer is started.

[0576] As an embodiment, the first timer is started after at least determining that the SCG connection has failed.

[0577] As an embodiment, when the first timer has not expired, the first process is successfully completed, which means that the first process is successfully completed while the first timer is running.

[0578] As an embodiment, when the first timer has not expired, the first process is successfully completed, which means that the first process is successfully completed before the first timer is instructed to stop.

[0579] As an embodiment, when the first timer has not expired, the first process is successfully completed, which means that the first process is successfully completed before the first timer triggers a stop condition.

[0580] As an embodiment, the first process being successfully completed means that the first process is determined to be successfully completed.

[0581] As an embodiment, stopping of the first timer depends on successful completion of the first process.

[0582] As an embodiment, the successful completion of the first process triggers the first timer to stop.

[0583] As an embodiment, when the first process is successfully completed, the first timer stops.

[0584] As an embodiment, the first timer stops when at least the first process is successfully completed.

[0585] As an embodiment, the first failure message is set after the first timer stops.

[0586] As an embodiment, the first failure message is sent after the first timer stops.

[0587] As an embodiment, in response to determining that the SCG connection fails, the first timer is started; in response to the first process being successfully completed, the first timer is stopped.

[0588] As an embodiment, as a response to determining that the SCG connection has failed, the first failure message is set; and as a response to the successful completion of the first process, the first failure message is sent.

[0589] As an embodiment, in response to determining that the SCG connection has failed, when the first process is successfully completed, the first failure message is set and sent.

[0590] As an embodiment, in response to determining that the SCG connection fails, the first timer is started and the first failure message is set; in response to the first process being successfully completed, the first timer is stopped and the first failure message is generated.

[0591] As an embodiment, in response to determining that the SCG connection has failed, the first timer is started; in response to the first process being successfully completed, the first timer is stopped and the first failure message is set, and the first failure message occurs.

[0592] As an embodiment, the second signaling is received in response to the successful completion of the first process, and the second signaling triggers the sending of the first failure message.

[0593] As an embodiment, the second signaling is an RRCReconfigurtion message.

[0594] As an embodiment, the second signaling is a Request message.

[0595] As an embodiment, the second signaling is a signaling of a lower layer of the RRC layer.

[0596] As an embodiment, the second signaling is a MAC sublayer message.

[0597] As an embodiment, the second signaling is a DCI.

[0598] As an embodiment, the second signaling triggering the sending of the first failure message means: after the second signaling is received, the first failure message is set.

[0599] As an embodiment, the second signaling triggering the sending of the first failure message means that the reception of the second signaling triggers the sending of the first failure message.

[0600] As an embodiment, the second signaling triggering the sending of the first failure message means that the second signaling requests the sending of the first failure message.

[0601] As an embodiment, the second signaling triggering the sending of the first failure message means that the second signaling instructs the sending of the first failure message.

[0602] As an embodiment, in response to the successful completion of the first process, a third signaling is sent, wherein the third signaling indicates that the first process is successfully completed and the SCG connection fails.

[0603] As an embodiment, the third signaling is an RRCReconfigurationComplete message.

[0604] As an embodiment, the third signaling is an RRC RestabilshmentComplete message.

[0605] As an embodiment, the third signaling is an RRCResumeComplete message.

[0606] As an embodiment, the third signaling is sent to indicate that the first process is successfully completed, and a field in the third signaling is used to indicate that the SCG connection fails.

[0607] As an embodiment, the first process is successfully completed, and a third signaling is sent, wherein the third signaling indicates that the first process is successfully completed and the SCG connection fails.

[0608] As an embodiment, the first process is successfully completed, and a third signaling is sent, wherein the third signaling indicates that there is available information related to the SCG connection failure. As an embodiment, a field in the third signaling is set to true to indicate that the SCG connection has failed.

[0609] As an embodiment, a field in the third signaling exists to indicate that the SCG connection fails.

[0610] As an embodiment, a field in the third signaling exists but is not set, which is used to indicate that the SCG connection fails.

[0611] Example 8

[0612] Embodiment 8 illustrates a flowchart of setting the second information block in the second UE variable according to an embodiment of the present application, as shown in the attached Figure 8 shown.

[0613] In step S8101, it is determined that the SCG connection fails; in step S8102, the first process is successfully completed; in step S8103, a second information block is set in a second UE variable.

[0614] In Example 8, as a response to the successful completion of the first process, a second information block is set in the second UE variable; the second information block indicates that the SCG connection has failed.

[0615] As an embodiment, when it is determined that the SCG connection fails, the first process is in progress.

[0616] As an embodiment, the successful completion of the first process triggers setting a second information block in the second UE variable.

[0617] As an embodiment, when the first process is successfully completed, a second information block is set in the second UE variable.

[0618] As an embodiment, when at least the first process is successfully completed, a second information block is set in the second UE variable.

[0619] As an embodiment, setting the second information block in the second UE variable depends on the first process being successfully completed and determining that the SCG connection fails.

[0620] As an embodiment, the first process is successfully completed and it is determined that the SCG connection fails, triggering the second UE variable to set the second information block.

[0621] As an embodiment, when the first process is successfully completed and it is determined that the SCG connection fails, the second information block is set in the second UE variable.

[0622] As an embodiment, when at least the first process is successfully completed and the SCG connection fails, the second information block is set in the second UE variable.

[0623] As an embodiment, setting the second information block in the second UE variable depends on the expiration of the first timer.

[0624] As an embodiment, expiration of the first timer triggers setting the second information block in the second UE variable.

[0625] As an embodiment, when the first timer expires, the second information block is set in the second UE variable.

[0626] As an embodiment, when at least the first timer expires, the second information block is set in the second UE variable.

[0627] As an embodiment, the second UE variable includes VarSuccessHO-Report.

[0628] As an embodiment, the second UE variable is VarSuccessHO-Report.

[0629] As an embodiment, the second UE variable is set to indicate that the first process is successfully completed.

[0630] As an embodiment, the second information block in the second UE variable is set to indicate that the SCG connection fails.

[0631] As an embodiment, part of the fields of the second information block in the second UE variable is set to indicate that the SCG connection fails.

[0632] As an embodiment, the second information block in the second UE variable is set to indicate that the SCG connection has failed, and the SCG is a candidate SCG for CPA / C configuration.

[0633] As an embodiment, the second information block in the second UE variable is set to indicate that the SCG connection has failed, and the SCG is a candidate SCG for CPA / C configuration accompanying CHO.

[0634] As an embodiment, the second information block is a SuccessHO-Report-r17.

[0635] As an embodiment, the second information block is a SuccessHO-Report-r19.

[0636] As an embodiment, the second information block is a SuccessHO-Report-r20.

[0637] As an embodiment, the second information block includes a second field, and the second field indicates the reason why the second information block is set.

[0638] As an embodiment, the second domain is shr-cause.

[0639] As an embodiment, the second domain is shr-cause-r19.

[0640] As an embodiment, the second field includes a plurality of candidate cause fields, and the candidate cause fields are set to true to indicate the reason why the second information block is set.

[0641] As a sub-embodiment of the above embodiment, the reason why the second information block is set includes: t304 reaches a configuration threshold.

[0642] As a sub-embodiment of the above embodiment, the reason why the second information block is set includes: t310 reaches a configuration threshold.

[0643] As a sub-embodiment of the above embodiment, the reason why the second information block is set includes: t312 reaches a configuration threshold.

[0644] As a sub-embodiment of the above embodiment, the reason why the second information block is set includes: source cell connection failure under DAPS configuration.

[0645] As a sub-embodiment of the above embodiment, the reason why the second information block is set includes: the SCG connection fails.

[0646] As an embodiment, the second information block includes a third field, and the third field includes relevant information about the SCG connection failure.

[0647] As a sub-embodiment of the above embodiment, the third field includes the cell identifier of the PSCell in the SCG.

[0648] As a sub-embodiment of the above embodiment, the third domain includes the cell identifier of at least the PSCell in the SCG.

[0649] As a sub-embodiment of the above embodiment, the third domain includes measurement results of at least PSCell in the SCG.

[0650] As a sub-embodiment of the above embodiment, the third field includes location information when the SCG connection fails, if the location information is available.

[0651] As an embodiment, the second information block includes a second time field, and the second time field indicates a time interval from determining that the SCG connection fails to being successfully completed to the first process.

[0652] As an embodiment, the start time of the second time domain is dependent on the time when the SCG connection fails.

[0653] As an embodiment, the deadline of the second time domain depends on the time when the first process is successfully completed.

[0654] As an embodiment, the successful completion of the first process means that: the first cell enters the RRC_CONNECT state.

[0655] As an embodiment, the first process being successfully completed means that the first process is determined to be successfully completed.

[0656] As an embodiment, the first process being successfully completed means that the first cell considers that the first process is successfully completed.

[0657] As an embodiment, the successful completion of the first process means that the transmission of the first uplink data to the first cell is completed.

[0658] As an embodiment, the first process being successfully completed means: receiving the RAR.

[0659] As an embodiment, the successful completion of the first process refers to: receiving the Msg4 message.

[0660] As an embodiment, the successful completion of the first process refers to: receiving a MsgB message.

[0661] As an embodiment, the successful completion of the first process means: notifying a lower layer that the successful completion of the first process.

[0662] As an embodiment, the successful completion of the first process means that the MCG is no longer suspended.

[0663] As an embodiment, the second information block includes the first identity field.

[0664] As an embodiment, the first process is successfully completed and a third signaling is sent, where the third signaling indicates that there is available information in the second UE variable.

[0665] As an embodiment, the third signaling includes a ueAssistanceInformation message.

[0666] As an embodiment, the third signaling is a ueAssistanceInformation message.

[0667] As an embodiment, the third signaling includes a field, a name of the field includes available, and the field indicates that the second UE variable has available information.

[0668] Example 9

[0669] Embodiment 9 illustrates a flowchart of setting the third information block in the third UE variable according to an embodiment of the present application, as shown in the attached Figure 9 shown.

[0670] In step S9101, it is determined that the SCG connection fails; in step S9102, the first process fails; in step S9103, a third information block is set in a third UE variable.

[0671] In Example 9, as a response to the failure of the first process, a third information block is set in a third UE variable; the third information block indicates that the SCG connection has failed.

[0672] As an embodiment, when it is determined that the SCG connection fails, the first process is in progress.

[0673] As an embodiment, the failure of the first process triggers setting a third information block in the third UE variable.

[0674] As an embodiment, when the first process fails, a third information block is set in the third UE variable.

[0675] As an embodiment, when at least the first process fails, a third information block is set in the third UE variable.

[0676] As an embodiment, the third UE variable is set to depend on the failure of the first process.

[0677] As an embodiment, the failure of the first process triggers the setting of the third UE variable.

[0678] As an embodiment, when the first process fails, the third UE variable is set.

[0679] As an embodiment, when at least the first process fails, the third UE variable is set.

[0680] As an embodiment, setting a third information block in the third UE variable depends on the failure of the first process and the failure of the SCG connection.

[0681] As an embodiment, when the first process fails and the SCG connection fails, a third information block is set in the third UE variable.

[0682] As an embodiment, when at least the first process fails and the SCG connection fails, a third information block is set in the third UE variable.

[0683] As an embodiment, as a response to the failure of the first process, the third UE variable is set; as a response to the failure of the SCG connection, a third information block is set in the third UE variable.

[0684] As an embodiment, the third information block only indicates that the SCG connection fails.

[0685] As an embodiment, the third information block indicates that the first process fails and the SCG connection fails.

[0686] As an embodiment, the third information block indicates that the first process failed; the first process failure includes the SCG connection failure.

[0687] As an embodiment, the third UE variable is used to store relevant information of the switching process.

[0688] As an embodiment, the third UE variable stores at least relevant information of the handover process failure.

[0689] As an embodiment, the third UE variable includes a VarRLF-Report.

[0690] As an embodiment, the third UE variable is a VarRLF-Report.

[0691] As an embodiment, the third UE variable is a VarRLF-Report, and the third information block is an rlf-Report.

[0692] As an embodiment, the third UE variable is a VarRLF-Report, and the third information block is a report dedicated to the SCG connection failure.

[0693] As an embodiment, the third UE variable is the first UE variable.

[0694] As an embodiment, the third UE variable is not the first UE variable.

[0695] As an embodiment, the third UE variable includes the first information block, and the first information block includes at least part of the information of the SCG connection failure.

[0696] As an embodiment, the third UE variable includes the first information block and the third information block, and the first information block and the third information block respectively include at least part of the information of the SCG connection failure.

[0697] As an embodiment, the third information block includes information carried in the first failure message.

[0698] As an embodiment, the third information block includes at least part of the information carried in the first failure message.

[0699] As an embodiment, the third information block includes the first identity field.

[0700] As an embodiment, the third information block includes a measurement result when the SCG connection fails.

[0701] As an embodiment, the third information block includes a first time domain.

[0702] As an embodiment, the third information block includes a third time field, and the third time field indicates a time interval from determining that the SCG connection fails to determining that the first process fails.

[0703] As an embodiment, the start time of the third time domain depends on the time when the SCG connection failure is determined.

[0704] As an embodiment, the deadline of the third time domain depends on the time when the first process fails.

[0705] As an embodiment, the time when the first process fails refers to: the time when the failure of the first process is determined.

[0706] As an embodiment, the time when the first process fails refers to: the time when T304 of the first cell expires.

[0707] As an embodiment, the time when the first process fails refers to the time when it is indicated that the first process fails.

[0708] As an embodiment, the time when the first process fails refers to: the time indicating the failure of the first process at a lower layer.

[0709] As an embodiment, the time when the first process fails refers to: the time when the configuration associated with the first process is released.

[0710] As an embodiment, the time when the first process fails refers to: the time when the connection reestablishment procedure is started.

[0711] As an embodiment, the time when the first process fails refers to: the time when T311 is started.

[0712] As an embodiment, the time when the first process fails refers to: the time when T311 expires.

[0713] As an embodiment, the third information block indicates the switching type.

[0714] As a sub-embodiment of the above embodiment, the switching type includes: CHO.

[0715] As a sub-embodiment of the above embodiment, the switching type includes: DAPS.

[0716] As a sub-embodiment of the above embodiment, the switching type includes: C-LTM.

[0717] As a sub-embodiment of the above embodiment, the switching type includes: CHO-withSCGs.

[0718] As a sub-embodiment of the above embodiment, the handover type includes: CHO with candidate PSCell.

[0719] As an embodiment, the third information block supports settings for fast recovery.

[0720] As a sub-embodiment of the above embodiment, the support for the setting for fast recovery means that the third information block includes configuration information of the configured candidate cells.

[0721] As a sub-embodiment of the above embodiment, the support for setting for fast recovery means that the third information block includes the cell identifier of the configured candidate cell.

[0722] As a sub-embodiment of the above embodiment, the third information block includes that the configured candidate cell is a candidate PCell.

[0723] As a sub-embodiment of the above embodiment, the third information block includes that the configured candidate cell is a candidate PSCell.

[0724] As a sub-embodiment of the above embodiment, the third information block includes that the configured candidate cell is a candidate PCell and an associated candidate PSCell.

[0725] As a sub-embodiment of the above embodiment, the support for the setting for fast recovery means that the third information block includes a fourth field, and the fourth field is set to true.

[0726] As a sub-embodiment of the above embodiment, the fourth field is noSuitableCellFound-r19.

[0727] As a sub-embodiment of the above embodiment, the fourth domain is noSuitablePCellFound-r19.

[0728] As a sub-embodiment of the above embodiment, the fourth field is noSuitablePCellFound-r20.

[0729] As a sub-embodiment of the above embodiment, the fourth field is noSuitablePSCellFound-r19.

[0730] As a sub-embodiment of the above embodiment, the fourth field is noSuitablePSCellFound-r20.

[0731] As an embodiment, the first process is successfully completed and a third signaling is sent, where the third signaling indicates that there is available information in the third UE variable.

[0732] As an embodiment, the third signaling includes a field, a name of the field includes available, and the field indicates that the third UE variable has available information.

[0733] Example 10

[0734] Example 10 illustrates a flowchart of starting the first process according to an embodiment of the present application, as shown in the attached Figure 10 shown.

[0735] In step S10101, the execution condition of the configuration information of the first cell is met; in step S10102, the execution condition of the configuration information of the second cell is met; in step 10103, the first process is started.

[0736] In Example 10, the first RRC message includes the execution conditions of the configuration information of the first cell, the first RRC message includes the configuration information of the second cell and the execution conditions of the configuration information of the second cell, and the second cell is configured to the first cell; the second cell is a candidate cell or target cell of the SCG.

[0737] As an embodiment, starting the first process depends on both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being met.

[0738] As an embodiment, the first process is started when both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell are met.

[0739] As an embodiment, the first process is started when at least the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell are both met.

[0740] As an embodiment, when the execution condition of the configuration information of the first cell is met, but the execution condition of the configuration information of the second cell is not met, the first process is not started.

[0741] As an embodiment, when the execution conditions of the configuration information of the first cell are met, but the execution conditions of the configuration information of the second cell are not met, when it is configured to allow only the configuration information of the first cell to be applied, the first process is started.

[0742] As an embodiment, starting the first process includes: starting the first process.

[0743] As an embodiment, starting the first process includes: turning on T304 of the first cell.

[0744] As an embodiment, starting the first process includes: starting T304 of the first cell and T304 of the second cell respectively.

[0745] As an embodiment, starting the first process includes: clearing stored UE variables.

[0746] As an embodiment, starting the first process includes: stopping other timers except T304.

[0747] As an embodiment, the starting of the first process includes: resuming the cell group transmission associated with the first cell if the cell group is suspended.

[0748] As an embodiment, the starting of the first process includes: resetting the MAC entities of the MCG and the SCG; the MCG is the cell group to which the first cell belongs, and the SCG is the cell group to which the second cell belongs.

[0749] As an embodiment, starting the first process includes: starting to perform downlink synchronization.

[0750] As an embodiment, starting the first process includes: starting to configure a lower layer using configuration information.

[0751] As an embodiment, the first process includes applying the configuration information of the first cell and applying the configuration information of the second cell.

[0752] As an embodiment, the first process is to apply the configuration information of the first cell.

[0753] As an embodiment, applying the configuration information of the first cell refers to: performing measurement on the first cell.

[0754] As an embodiment, applying the configuration information of the first cell refers to: performing switching to the first cell, and the first cell is a PCell.

[0755] As an embodiment, applying the configuration information of the first cell refers to: performing random access on the first cell.

[0756] As an embodiment, the first RRC message includes the execution conditions of the configuration information of the first cell, the first RRC message includes the configuration information of the second cell and the execution conditions of the configuration information of the second cell, the first cell is a candidate PCell, and the second cell is a candidate PSCell.

[0757] As an embodiment, the first RRC message includes the execution conditions of the configuration information of the first cell, the first RRC message includes the configuration information of the second cell and the execution conditions of the configuration information of the second cell, the second cell is configured to the first cell, and whether the configuration information of the second cell is applied depends on the execution conditions of the configuration information of the first cell.

[0758] As a sub-embodiment of the above embodiment, when the execution condition of the configuration information of the first cell is not met, the configuration information of the second cell is not applied.

[0759] As a sub-embodiment of the above embodiment, when at least the execution condition of the configuration information of the first cell is not satisfied, the configuration information of the second cell is not applied.

[0760] As a sub-embodiment of the above embodiment, when the execution condition of the configuration information of the first cell is met and the execution condition of the configuration information of the second cell is met, the configuration information of the second cell is applied.

[0761] As a sub-embodiment of the above embodiment, the first cell is a candidate PCell, and the second cell is a candidate PSCell of the first cell.

[0762] As an embodiment, the second cell is a candidate cell of an SCG.

[0763] As an embodiment, the second cell is a target cell of an SCG.

[0764] As an embodiment, the first cell is a candidate cell of an MCG, the second cell is a candidate cell of an SCG, and the SCG is configured to the MCG.

[0765] As an embodiment, the first cell is a target cell of an MCG, the second cell is a candidate cell of an SCG, and the SCG is configured to the MCG.

[0766] As an embodiment, the first cell is a target cell of an MCG, the second cell is a target cell of an SCG, and the SCG is configured to the MCG.

[0767] As an embodiment, the one SCG and the one MCG are independent of each other.

[0768] As a sub-embodiment of the above embodiment, the first cell is CHO.

[0769] As a sub-embodiment of the above embodiment, the first cell is for C-LTM.

[0770] As a sub-embodiment of the above embodiment, the second cell is for CPA / C.

[0771] As a sub-embodiment of the above embodiment, the second cell is for subsequent CPA / C.

[0772] Example 11

[0773] Embodiment 11 illustrates a flowchart of triggering the determination of SCG connection failure by the configuration information application failure of the second cell according to an embodiment of the present application, as shown in the attached figure. Figure 11 shown.

[0774] In step S11101, the execution condition of the configuration information of the first cell is met; in step S11102, the execution condition of the configuration information of the second cell is met; in step S11103, the configuration information of the second cell is applied; in step S11104, the failure to apply the configuration information of the second cell triggers the determination of SCG connection failure.

[0775] In Example 11, in response to both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being met, the configuration information of the second cell is applied; the failure to apply the configuration information of the second cell triggers the determination of SCG connection failure.

[0776] As an embodiment, the application of the configuration information of the second cell depends on the execution conditions of the configuration information of the first cell and the configuration information of the second cell being satisfied.

[0777] As an embodiment, when the execution conditions of the configuration information of the first cell and the configuration information of the second cell are both met, the configuration information of the second cell is applied.

[0778] As an embodiment, when at least the execution conditions of the configuration information of the first cell and the configuration information of the second cell are met, the configuration information of the second cell is applied.

[0779] As an embodiment, applying the configuration information of the second cell refers to: performing switching to the second cell.

[0780] As an embodiment, applying the configuration information of the second cell means: performing downlink synchronization on the second cell.

[0781] As an embodiment, applying the configuration information of the second cell refers to: performing a random access process on the second cell.

[0782] As an embodiment, the performing of the random access process includes: sending a preamble to the second cell on the configured time-frequency resources according to the configuration information.

[0783] As an embodiment, the performing of the random access process includes: performing monitoring of designated signaling according to the configuration information.

[0784] As an embodiment, the performing of the random access process includes: performing data reception according to the configuration information.

[0785] As an embodiment, the performing of the random access process includes: performing signaling transmission according to the configuration information.

[0786] As an embodiment, the failure to apply the configuration information of the second cell refers to: failure to switch to the second cell.

[0787] As an embodiment, the failure to apply the configuration information of the second cell refers to: failure to perform downlink synchronization.

[0788] As an embodiment, the failure to perform downlink synchronization means that the configured SSB is not searched.

[0789] As an embodiment, the failure to perform downlink synchronization means that the measurement result of the configured SSB does not meet the threshold.

[0790] As an embodiment, the failure to apply the configuration information of the second cell refers to: failure to perform a random access process in the second cell.

[0791] As an embodiment, the failure to perform the random access process refers to: failing to monitor the target scheduling signaling on the designated time-frequency resources.

[0792] As an embodiment, the failure to execute the random access process refers to: not receiving a contention resolution command.

[0793] As an embodiment, the failure to perform the random access process refers to: the timer started for the random access process expires.

[0794] As an embodiment, the failure to perform the random access process refers to: beam connection failure.

[0795] As an embodiment, as a response to the failure of applying the configuration information of the second cell, it is determined that the SCG connection fails.

[0796] As an embodiment, when the configuration information application of the second cell fails, it is determined that the SCG connection fails.

[0797] As an embodiment, when the configuration information application of at least the second cell fails, it is determined that the SCG connection fails.

[0798] Example 12

[0799] Example 12 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application; Figure 12 As shown in the attached Figure 12 In the embodiment, the processing device 1200 in the first node includes a first receiver 1201 and a first processor 1202.

[0800] A first receiver 1201 receives a first RRC message, where the first RRC message includes configuration information of a first cell;

[0801] The first processor 1202 determines that the SCG connection fails;

[0802] In Example 12, as a response to the determination of the SCG connection failure, whether to send a first failure message depends on whether a first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or a target cell of the MCG; neither the MCG nor the SCG is suspended.

[0803] As an embodiment, the sender of the first RRC message is MN.

[0804] As an embodiment, the sender of the first RRC message is SN.

[0805] As an embodiment, whether to send the first failure message depends on whether the first process is in progress, including: when the first process is in progress, setting a first information block in a first UE variable; the first information block indicates that the SCG connection fails.

[0806] As an embodiment, the first processor 1202 sends the first failure message in response to the successful completion of the first process.

[0807] As an embodiment, the first processor 1202, in response to the successful completion of the first process, sets a second information block in a second UE variable; the second information block indicates that the SCG connection has failed.

[0808] As an embodiment, the first processor 1202, in response to the failure of the first process, sets a third information block in a third UE variable; the third information block indicates that the SCG connection has failed.

[0809] As an embodiment, the first processor 1202, in response to both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being satisfied, starts the first process;

[0810] As an embodiment, the first RRC message includes an execution condition of the configuration information of the first cell, the first RRC message includes the configuration information of the second cell and the execution condition of the configuration information of the second cell, and the second cell is configured to the first cell;

[0811] As an embodiment, the second cell is a candidate cell or a target cell of the SCG.

[0812] As an embodiment, the first processor 1202 applies the configuration information of the second cell in response to both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being met;

[0813] As an embodiment, the failure to apply the configuration information of the second cell triggers the determination of the SCG connection failure.

[0814] As an embodiment, the first processor 1202 includes a first receiver 1201 .

[0815] As an embodiment, the first processor 1202 includes a first transmitter.

[0816] As an embodiment, the first processor 1202 includes a first receiver 1201 and a first transmitter.

[0817] As an embodiment, the first receiver 1201 includes the attached Figure 4 At least one of the antenna 452 or the receiver 454 or the multi-antenna receive processor 458 or the receive processor 456 or the controller / processor 459 or the memory 460 or the data source 467.

[0818] As an embodiment, the first receiver 1201 includes the attached Figure 4 At least an antenna 452 and a receiver 454.

[0819] As an embodiment, the first transmitter includes the attached Figure 4 At least one of the antenna 452 or transmitter 454 or multi-antenna transmit processor 457 or transmit processor 468 or controller / processor 459 or memory 460 or data source 467.

[0820] As an embodiment, the first transmitter includes the attached Figure 4 At least antenna 452 and transmitter 454.

[0821] Example 13

[0822] Example 13 illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application; Figure 13 As shown in the attached Figure 13 In the embodiment, the processing device 1300 in the second node includes a second transmitter 1301 and a second receiver 1302.

[0823] The second transmitter 1301 sends a first RRC message, where the first RRC message includes configuration information of the first cell;

[0824] In Example 13, the receiver of the first RRC message determines that the SCG connection has failed; as a response to the determination of the SCG connection failure, whether the receiver of the first RRC message sends a first failure message depends on whether a first process is in progress; whether the first failure message is sent depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or a target cell of the MCG; neither the MCG nor the SCG is suspended.

[0825] As an embodiment, the second receiver receives the first failure message; when the recipient of the first RRC message determines the response of the SCG connection failure, the first process is no longer in progress; the second node is an MN.

[0826] As an embodiment, whether the receiver of the first RRC message sends the first failure message depends on whether the first process is in progress, including: when the first process is in progress, setting a first information block in the first UE variable; the first information block indicates that the SCG connection fails.

[0827] As an embodiment, the recipient of the first RRC message sends the first failure message in response to the successful completion of the first process.

[0828] As an embodiment, the second receiver receives the first failure message; the recipient of the first RRC message sends the first failure message as a response to the successful completion of the first process; when the recipient of the first RRC message determines the response to the SCG connection failure, the first process is in progress; the second node is MN.

[0829] As an embodiment, in response to the successful completion of the first process, a second information block is set in the second UE variable; the second information block indicates that the SCG connection has failed.

[0830] As an embodiment, as a response to the failure of the first process, a third information block is set in a third UE variable; the third information block indicates that the SCG connection has failed.

[0831] As an embodiment, in response to both the execution conditions of the configuration information of the first cell and the execution conditions of the configuration information of the second cell being met, the receiver of the first RRC message starts the first process;

[0832] As an embodiment, the first RRC message includes the execution conditions of the configuration information of the first cell, the first RRC message includes the configuration information of the second cell and the execution conditions of the configuration information of the second cell, and the second cell is configured to the first cell; the second cell is a candidate cell or target cell of the SCG.

[0833] As an embodiment, in response to both the execution condition of the configuration information of the first cell and the execution condition of the configuration information of the second cell being met, the receiver of the first RRC message applies the configuration information of the second cell;

[0834] As an embodiment, the failure to apply the configuration information of the second cell triggers the receiver of the first RRC message to determine that the SCG connection has failed.

[0835] As an embodiment, the second transmitter 1301 includes the attached Figure 4At least one of the antenna 420 or transmitter 418 or multi-antenna transmit processor 471 or transmit processor 416 or controller / processor 475 or memory 476.

[0836] As an embodiment, the second transmitter 1301 includes the attached Figure 4 At least antenna 420 and transmitter 418 in.

[0837] As an embodiment, the second receiver 1302 includes the attached Figure 4 At least one of the antenna 420 or the receiver 418 or the multi-antenna receive processor 472 or the receive processor 470 or the controller / processor 475 or the memory 476.

[0838] As an embodiment, the second receiver 1302 includes the attached Figure 4 At least the antenna 420 and the receiver 418.

[0839] Those skilled in the art will appreciate that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software functional module. This application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in this application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system devices in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR node B) NR node B, TRP (Transmitter Receiver Point) and other wireless communication devices.

[0840] The above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first RRC message, where the first RRC message includes configuration information of a first cell; The first processor determines that the SCG connection fails; In which, as a response to the determination of the SCG connection failure, whether to send a first failure message depends on whether the first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

2. The first node according to claim 1, wherein: Whether to send the first failure message depends on whether the first process is in progress, including: when the first process is in progress, setting a first information block in a first UE variable; the first information block indicates that the SCG connection fails.

3. The first node according to claim 1 or 2, characterized in that include: The first handler sends the first failure message in response to the successful completion of the first process.

4. The first node according to claim 1 or 2, characterized in that: include: The first processor, in response to the first process being successfully completed, sets a second information block in a second UE variable; The second information block indicates that the SCG connection has failed.

5. The first node according to claim 1 or 2, characterized in that: include: The first processor, in response to the failure of the first process, sets a third information block in a third UE variable; The third information block indicates that the SCG connection has failed.

6. The first node according to any one of claims 1 to 5, characterized in that: include: The first processor, in response to both an execution condition of the configuration information of the first cell and an execution condition of the configuration information of the second cell being satisfied, starts the first process; Among them, the first RRC message includes the execution conditions of the configuration information of the first cell, the first RRC message includes the configuration information of the second cell and the execution conditions of the configuration information of the second cell, and the second cell is configured to the first cell; the second cell is a candidate cell or target cell of the SCG.

7. The first node according to claim 6, characterized in that include: the first processor, in response to both an execution condition of the configuration information of the first cell and an execution condition of the configuration information of the second cell being satisfied, applying the configuration information of the second cell; Among them, the failure to apply the configuration information of the second cell triggers the determination of SCG connection failure.

8. A second node used for wireless communication, characterized in that: include: The second processor sends a first RRC message, where the first RRC message includes configuration information of the first cell; In which, the receiver of the first RRC message determines that the SCG connection fails; as a response to the determination of the SCG connection failure, whether the receiver of the first RRC message sends a first failure message depends on whether the first process is in progress; whether the first failure message is sent depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection fails; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

9. A method in a first node for wireless communication, characterized in that: include: receiving a first RRC message, where the first RRC message includes configuration information of a first cell; Determine if SCG connection failed; In which, as a response to the determination of the SCG connection failure, whether to send a first failure message depends on whether the first process is in progress; whether to send the first failure message depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection has failed; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

10. A method used in a second node of wireless communication, characterized in that: include: Sending a first RRC message, where the first RRC message includes configuration information of the first cell; In which, the receiver of the first RRC message determines that the SCG connection fails; as a response to the determination of the SCG connection failure, whether the receiver of the first RRC message sends a first failure message depends on whether the first process is in progress; whether the first failure message is sent depends on whether the first process is in progress, including: sending the first failure message only when the first process is not in progress; the first failure message indicates that the SCG connection fails; the first process includes applying the configuration information of the first cell, and the first cell is a candidate cell or target cell of the MCG; neither the MCG nor the SCG is suspended.

Images