A reporting method, apparatus, device and storage medium

Abstract

This disclosure provides a reporting method, apparatus, device, and storage medium. The method includes: recording information related to the MCG link failure in response to a Primary Cell Group Radio Link Failure (MCG RLF); and reporting the recorded information to a network device. The method of this disclosure results in shorter MCG link recovery time and higher efficiency.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to reporting methods, apparatus, devices and storage media. Background Technology

[0002] In communication systems, the introduction of Multi-Radio Dual Connectivity (MR-DC) technology enables terminal devices to access two cell groups simultaneously (i.e., accessing the Master Cell Group (MCG) through the primary base station and the Secondary Cell Group (SCG) through the secondary base station), thereby improving data throughput and UE mobility performance.

[0003] In related technologies, Radio Link Failure (RLF) may occur. When an MCG RLF occurs, if the SCG link is normal, the MCG link will be restored based on a fast MCG link recovery mechanism. This mechanism involves the SCG sending an MCGFailureInformation message to the primary base station to quickly switch the terminal device to a new primary cell (PCell) to restore the MCG link. However, if the SCG link is abnormal when an MCG RLF occurs, the terminal device needs to trigger a connection reconstruction process to restore the MCG link. The process of "triggering the connection reconstruction process to restore the MCG link" takes a relatively long time.

[0004] However, in the relevant technical methods, if the SCG link is always abnormal, the terminal device needs to trigger the connection reconstruction process to restore the MCG link every time an MCG RLF occurs, which results in long processing time and low efficiency. Summary of the Invention

[0005] The reporting method, apparatus, equipment, and storage medium disclosed herein aim to solve the technical problems of long time consumption and low efficiency in related technologies for MCG link recovery methods.

[0006] In a first aspect, embodiments of this disclosure provide a reporting method, which is executed by a terminal device, including:

[0007] In response to a primary cell group radio link failure (MCG RLF), information related to the MCG link failure is recorded.

[0008] Report the recorded information to the network device.

[0009] This disclosure provides a reporting method in which, in response to an MCG link failure occurring on a terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling the terminal device to record information related to MCG link failure and report this information to the network device, when the terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent the same reason from causing the terminal device to be unable to use the fast MCG link recovery mechanism to quickly restore the MCG link in the future. Consequently, when the terminal device experiences another MCG link failure, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0010] Secondly, embodiments of this disclosure provide a reporting method, which is executed by a network device, including:

[0011] The terminal device receives information reported by itself, which is information related to the MCG link failure recorded by the terminal device after an MCG RLF occurs.

[0012] Thirdly, embodiments of this disclosure provide a communication device configured in a terminal device, comprising:

[0013] The processing module is used to record information related to the MCG link failure in response to the occurrence of a primary cell group radio link failure (MCG RLF).

[0014] The transceiver module is used to report the recorded information to the network device.

[0015] Fourthly, embodiments of this disclosure provide a communication device configured in a network device, comprising:

[0016] The transceiver module is used to receive information reported by the terminal device, which is information related to the MCG link failure recorded by the terminal device after the MCG link failure occurs.

[0017] Fifthly, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0018] In a sixth aspect, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0019] In a seventh aspect, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0020] Eighthly, embodiments of this disclosure provide a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0021] Ninthly, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0022] In a tenth aspect, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the second aspect above.

[0023] Eleventhly, embodiments of this disclosure provide a communication system, which includes the communication devices described in the third aspect to the fourth aspect, or the communication devices described in the fifth aspect to the sixth aspect, or the communication devices described in the seventh aspect to the eighth aspect, or the communication devices described in the ninth aspect to the tenth aspect.

[0024] In a twelfth aspect, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the network device and / or the terminal device described above, wherein when the instructions are executed, the network device performs the method described in the first aspect, and / or the terminal device performs the method described in the second aspect.

[0025] In a thirteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the methods described in any one of the first to second aspects.

[0026] In a fourteenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting network devices in implementing the functions involved in the methods described in the first aspect, and / or supporting terminal devices in implementing the functions involved in the methods described in the second aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for source and slave nodes. The chip system may be composed of chips or may include chips and other discrete devices.

[0027] In a fifteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the methods described in any one of the first to second aspects. Attached Figure Description

[0028] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:

[0029] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure;

[0030] Figure 2 A flowchart illustrating a reporting method provided in another embodiment of this disclosure;

[0031] Figure 3 A flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0032] Figure 4 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0033] Figure 5 A flowchart illustrating a reporting method provided in another embodiment of this disclosure;

[0034] Figure 6 A flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0035] Figure 7 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0036] Figure 8 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0037] Figure 9 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0038] Figure 10 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0039] Figure 11 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0040] Figure 12 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0041] Figure 13 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0042] Figure 14 A schematic flowchart illustrating a reporting method provided in yet another embodiment of this disclosure;

[0043] Figure 15 This is a schematic diagram of the structure of a communication device provided in one embodiment of the present disclosure;

[0044] Figure 16 This is a schematic diagram of the structure of a communication device provided in another embodiment of the present disclosure;

[0045] Figure 17 This is a block diagram of a communication device provided in one embodiment of the present disclosure;

[0046] Figure 18 This is a schematic diagram of the structure of a chip provided in one embodiment of the present disclosure. Detailed Implementation

[0047] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this disclosure as detailed in the appended claims.

[0048] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0049] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the words “if” and “suppose” as used herein may be interpreted as “when”, “when”, or “in response to a determination”.

[0050] Embodiments of this disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.

[0051] To facilitate understanding, the terminology used in this application will be introduced first.

[0052] 1. Multi-Radio Dual Connectivity (MR-DC)

[0053] The terminal equipment establishes "dual connectivity" with both the master base station (MN) and the secondary base station (SN), simultaneously utilizing the resources of both the master cell group (MCG) and the secondary cell group (SCG). The master base station has a control connection with the core network.

[0054] 2. Radio Link Failure (RLF)

[0055] This occurs when interference or a very low received signal level prevents the mobile station from correctly decoding the information sent from the network, and the issue cannot be controlled through power control or handover (i.e., a radio link failure). In this situation, the mobile station either initiates call reconstruction or forcibly disconnects the link. Since forcibly disconnecting the link actually introduces a dropped call, it is essential to ensure that the mobile station only considers it a radio link failure when the communication quality is truly unacceptable.

[0056] 3. Primary Cell (PCell)

[0057] The cell used to initiate initial access under an MCG is called a PCell.

[0058] 4. Primary Secondary Cell (PSCell)

[0059] The cell that initiates initial access under SCG.

[0060] To better understand the reporting method disclosed in the embodiments of this application, the communication system to which the embodiments of this application are applicable is described below.

[0061] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown is an example including a network device 11 and a terminal device 12.

[0062] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems.

[0063] The network device 11 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network device 11 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This disclosure does not limit the specific technology or device form used in the network device. The network device provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0064] The terminal device 12 in this disclosure can be a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of this disclosure do not limit the specific technology or device form used in the terminal device.

[0065] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0066] The reporting method, apparatus, device, and storage medium provided in the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0067] Figure 2 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a terminal device, such as... Figure 2 As shown in a, the reporting method may include the following steps:

[0068] Step 201: In response to an MCG RLF, record information related to the MCG link failure.

[0069] In one embodiment of this disclosure, the recording of information related to MCG link failure may specifically include: recording first information, which may include at least one of the following:

[0070] Is the T316 timer configured?

[0071] Is the T316 timer currently timed out?

[0072] Is SCG transmission currently paused?

[0073] Is SCG currently active?

[0074] Is a PSCell being added currently in progress?

[0075] Is a PSCell change currently in progress?

[0076] Step 202: Report the recorded information to the network device.

[0077] In one embodiment of this disclosure, the terminal device specifically reports the information it has recorded (i.e., the first information mentioned above) to the network device based on the network device's request after the MCG link is restored.

[0078] Furthermore, this disclosure details the reasons for recording and reporting information related to MCG link failures:

[0079] As described in the background information above, when an MCG RLF occurs, if the SCG link communicates normally, the MCG link will be quickly restored based on the fast MCG link recovery mechanism. However, if the SCG link cannot communicate normally, a connection reconstruction process needs to be triggered. Specifically, the "information related to MCG link failure" in step 201 indicates whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, and a connection reconstruction process is required to restore the MCG link. Specifically, if the T316 timer is not configured, the T316 timer times out, SCG transmission is paused, the SCG is in an inactive state, a PSCell is being added, or a PSCell is being modified, it indicates that the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, and a connection reconstruction process is required to restore the MCG link.

[0080] The aforementioned "triggering connection reconstruction process" is generally time-consuming, leading to low MCG link recovery efficiency. Therefore, in one embodiment of this disclosure, once a terminal device determines that an MCG RLF has occurred, it records information related to the MCG link failure and reports it to the network device. This allows the network device to determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link when the terminal device is unable to do so and needs to trigger a connection reconstruction process. This enables the network device to optimize and adjust the terminal device accordingly, preventing future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0081] Furthermore, detailed descriptions of the specific implementation methods for steps 201-202 will be provided in subsequent embodiments.

[0082] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0083] Figure 3This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a terminal device, such as... Figure 3 As shown, the reporting method may include the following steps:

[0084] Step 301: In response to an MCG RLF, a connection reconstruction process should be triggered to record information related to the MCG link failure.

[0085] Figure 3 The corresponding embodiments are the same as those described above. Figure 2 The differences between the corresponding embodiments are as follows: Figure 2 The middle part records information related to the MCG link failure after the terminal device experiences an MCG link failure. Figure 3 The implementation method is as follows: when the terminal device experiences an MCG RLF and determines that the connection reconstruction process needs to be triggered, the terminal device records information related to the MCG link failure.

[0086] Furthermore, in one embodiment of this disclosure, the relevant information regarding the MCG link failure can be found in the description of the above embodiments.

[0087] Step 302: Report the recorded information to the network device.

[0088] In one embodiment of this disclosure, the terminal device reports its recorded information related to MCG link failure to the network device. The network device can then infer, based on the content of the information related to MCG link failure, the reason why the terminal device needs to trigger a connection reconstruction process to restore the MCG link after an MCG RLF occurs (i.e., the reason why the fast MCG link recovery mechanism cannot be used to restore the MCG link after an MCG RLF occurs). This allows the terminal device to be optimized and adjusted accordingly based on the reason, preventing the situation from recurring where "the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link due to the same reason".

[0089] For example, in one embodiment of this disclosure, if the information related to the MCG link failure reported by the terminal device to the network device (i.e., the first information reported by the terminal device to the network device) is:

[0090] The T316 timer is not configured;

[0091] SCG transmission is not currently paused;

[0092] SCG is currently inactive.

[0093] No PSCell is being added at present;

[0094] There are currently no changes being made to PSCell.

[0095] Therefore, based on the information reported by the terminal device, the network device can infer that the reason why the terminal device needs to trigger a connection reconstruction process to restore the MCG link after an MCG LF event is that the T316 timer is not configured and the SCG is currently in an inactive state. In this case, the network device can make corresponding optimizations to the terminal device, such as configuring the T316 timer and / or controlling the SCG to be in an active state. Then, when the terminal device experiences another MCG event, the fast MCG link recovery mechanism can be used directly to restore the MCG link, which is faster and more efficient.

[0096] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0097] Figure 4 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a terminal device, such as... Figure 4 As shown, the reporting method may include the following steps:

[0098] Step 401: Record the second information, which is the actual triggering reason for the current connection reconstruction process.

[0099] In one embodiment of this disclosure, as can be seen from the above content, the second information should essentially represent the actual reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link.

[0100] The second information may include at least one of the following:

[0101] The T316 timer is not configured;

[0102] T316 timer timed out;

[0103] SCG transmission paused;

[0104] SCG is in an inactive state;

[0105] Adding a PSCell in progress;

[0106] PSCell is undergoing changes.

[0107] Furthermore, when the actual triggering reasons for the current connection reconstruction process include multiple factors, in one embodiment of this disclosure, the terminal device can record all actual triggering reasons as second information. In another embodiment of this disclosure, the terminal device can select less than or equal to N factors from the actual triggering reasons and record them as second information, where N is a positive integer. The aforementioned N can be determined by the terminal device based on a protocol agreement, and / or by the terminal device based on instructions from the network device. The specific number of actual triggering reasons selected by the terminal device should be less than or equal to the total number of actual triggering reasons for the current connection reconstruction process.

[0108] It should be noted that, in one embodiment of this disclosure, the above-mentioned terminal device selecting less than or equal to N reasons to record as the second information can be specifically understood as follows: when the total number of actual triggering reasons of the current connection reconstruction process is less than N, less than N reasons can be selected from the actual triggering reasons of the current connection reconstruction process to record as the second information.

[0109] For example, suppose N is 4, and the actual triggering reason for the current connection reconstruction process is: T316 timer not configured and SCG is inactive. In this case, the total number of actual triggering reasons for the current connection reconstruction process is 2, which is less than the value of N (4). At this time, the terminal device cannot select 4 reasons as the second information from the actual triggering reasons of the current connection reconstruction process. The terminal device can select less than 4 reasons as the second information. For example, the terminal device can select "T316 timer not configured" as the second information, or the terminal device can select "T316 timer not configured and SCG is inactive" as the second information.

[0110] Furthermore, in one embodiment of this disclosure, when the terminal device selects less than or equal to N reasons from the actual triggering causes, it may arbitrarily select less than or equal to N reasons based on autonomous selection, and / or it may prioritize selecting less than or equal to N reasons with higher priority based on priority. Different reasons correspond to different priorities, and this correspondence between reasons and priorities may be agreed upon by a protocol or indicated by the network device. For example, the priority order among the reasons may be: T316 timer timeout > SCG pause transmission > PSCell addition or modification in progress > SCG in an inactive state.

[0111] It should also be noted that, in one embodiment of this disclosure, when the actual triggering reason for the current connection reconstruction process includes the T316 timer timeout, the terminal device should also record the timing duration of the T316 timer as second information.

[0112] Step 402: Report the second information to the network device.

[0113] In one embodiment of this disclosure, the terminal device reports second information to the network device, which can then determine, based on the content of the second information, the reason why the terminal device needs to trigger a connection reconstruction process to restore the MCG link after an MCG RLF occurs (i.e., the reason why the fast MCG link recovery mechanism cannot be used to restore the MCG link after an MCG RLF occurs). This allows the terminal device to be optimized and adjusted accordingly based on the reason, preventing the recurrence of situations where "the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link due to the same reason".

[0114] For example, in one embodiment of this disclosure, if the second information reported by the terminal device to the network device is:

[0115] The T316 timer timed out, and the timing duration of the T316 timer is 40 milliseconds (ms).

[0116] Therefore, based on the second information reported by the terminal device, the network device can infer that the reason why the terminal device needs to trigger the connection reconstruction process to restore the MCG link after an MCG RLF occurs is that the T316 timer timed out due to its short timing duration. At this time, the network device can make corresponding optimizations to the terminal device. For example, this optimization could be to configure a new timing duration for the T316 timer, longer than the original timing duration, and this new timing duration should be able to support the completion of the fast MCG link recovery mechanism. This ensures that if the terminal device subsequently experiences another MCG RLF, it can successfully restore the MCG link based on the fast MCG link recovery mechanism.

[0117] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0118] Figure 5 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a terminal device, such as... Figure 5 As shown, the reporting method may include the following steps:

[0119] Step 501: In response to the occurrence of MCG RLF, a connection reconstruction process shall be triggered, and the actual triggering reason of the current connection reconstruction process includes a specific reason. Record the third information, which includes the specific reason corresponding to the current connection reconstruction process.

[0120] In one embodiment of this disclosure, the specific reason may be determined by the terminal device based on a protocol agreement, and / or may be determined by the terminal device based on an instruction from the network device.

[0121] Furthermore, in one embodiment of this disclosure, the specific cause can be any one or more of the possible reasons that require triggering a connection reconstruction process to restore the MCG link after an MCG RLF occurs. For example, the specific cause may include at least one of: T316 timer timeout, SCG transmission pause, PSCell addition in progress, and PSCell modification in progress.

[0122] Furthermore, in one embodiment of this disclosure, only a specific reason is recorded if the actual triggering reason for the current connection reconstruction process includes that specific reason. For example, suppose the specific reasons include T316 timer timeout, SCG transmission paused, PSCell addition in progress, and PSCell modification in progress; and the actual triggering reason for the current connection reconstruction process is: T316 timer not configured, SCG transmission paused. In this case, only "SCG transmission paused" is recorded as third-party information.

[0123] Furthermore, when the current connection reconstruction process corresponds to multiple specific reasons, in one embodiment of this disclosure, the terminal device can record all the specific reasons corresponding to the current connection reconstruction process as third information. In another embodiment of this disclosure, the terminal device can select less than or equal to N reasons from the specific reasons corresponding to the current connection reconstruction process and record them as third information, where N is a positive integer. Here, N can be determined by the terminal device based on a protocol agreement, and / or by the terminal device based on an instruction from the network device. For detailed information related to this part, please refer to the descriptions in the above embodiments.

[0124] It should also be noted that, in one embodiment of this disclosure, when the specific reason corresponding to the current connection reconstruction process includes the T316 timer timeout, the terminal device should also record the timing duration of the T316 timer as third information.

[0125] Step 502: Report third-party information to the network device.

[0126] For details regarding step 502, please refer to the description in the above embodiments.

[0127] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0128] Figure 6 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a terminal device, such as... Figure 6 As shown, the reporting method may include the following steps:

[0129] Step 601: In response to an MCG RLF, a connection reconstruction process must be triggered, and the actual triggering reason for the current connection reconstruction process does not include a specific reason and no information is recorded.

[0130] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0131] Figure 7 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a terminal device, such as... Figure 7 As shown, the reporting method may include the following steps:

[0132] Step 701: In response to an MCG RLF, record information related to the MCG link failure.

[0133] Step 702: Record information related to the MCG link failure into an RLF report (such as VarRLF-Report).

[0134] Step 703: Report an RLF Report to the network device.

[0135] In one embodiment of this disclosure, after the terminal device restores the MCG link based on the connection reconstruction process, it will report an RLF Report to the network device based on the network device's request.

[0136] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0137] Figure 8 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a terminal device, such as... Figure 8 As shown, the reporting method may include the following steps:

[0138] Step 801: Send capability information to the network device, wherein the capability information is used to indicate whether the terminal device supports recording and reporting information related to the MCG link failure.

[0139] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0140] Figure 9 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a network device, such as... Figure 9 As shown, the reporting method may include the following steps:

[0141] Step 901: Receive information reported by the terminal device, which is information related to the MCG link failure recorded by the terminal device after the MCG RLF occurs.

[0142] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0143] Figure 10 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a network device, such as... Figure 10 As shown, the reporting method may include the following steps:

[0144] Step 1001: Receive information reported by the terminal device, wherein the information is information related to the MCG link failure recorded by the terminal device after an MCG RLF occurs and when it is determined to trigger a connection reconstruction process to restore the MCG link.

[0145] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0146] Figure 11 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a network device, such as... Figure 11 As shown, the reporting method may include the following steps:

[0147] Step 1101: Receive the second information reported by the terminal device, where the second information is the actual triggering reason for the current connection reconstruction process.

[0148] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0149] Figure 12 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a network device, such as... Figure 12 As shown, the reporting method may include the following steps:

[0150] Step 1201: Receive third information reported by the terminal device, the third information including a specific reason included in the actual triggering reason of the current connection reconstruction process.

[0151] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0152] Figure 13 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a network device, such as... Figure 13 As shown, the reporting method may include the following steps:

[0153] Step 1301: Send a request message to the terminal device, the request message being used to request the terminal device to report the information.

[0154] Step 1302: Receive the information reported by the terminal device through RLF Report.

[0155] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0156] Figure 14 This is a flowchart illustrating a reporting method provided in an embodiment of this disclosure. The method is executed by a network device, such as... Figure 14 As shown, the reporting method may include the following steps:

[0157] Step 1401: Receive capability information sent by the terminal device, wherein the capability information is used to indicate whether the terminal device supports recording and reporting information related to the MCG link failure.

[0158] In summary, in the method provided by this disclosure, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0159] Figure 15 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure, as shown below. Figure 14 As shown, the device may include:

[0160] The processing module is used to record information related to the MCG link failure in response to the occurrence of a primary cell group radio link failure (MCG RLF).

[0161] The transceiver module is used to report the recorded information to the network device.

[0162] In summary, in the communication device provided in this embodiment, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0163] Optionally, in one embodiment of this disclosure, the processing module is further configured to:

[0164] In response to determining that a connection reconstruction process needs to be triggered to restore the MCG link, information related to the MCG link failure is logged.

[0165] Optionally, in one embodiment of this disclosure, the processing module is further configured to:

[0166] Record first information, which includes at least one of the following:

[0167] Is the T316 timer configured?

[0168] Has the T316 timer timed out?

[0169] Is the SCG transmission in the secondary cell group suspended?

[0170] Is SCG in an active state?

[0171] Is the addition of PSCells to primary and secondary cells currently underway?

[0172] Is a PSCell change in progress?

[0173] Optionally, in one embodiment of this disclosure, the processing module is further configured to:

[0174] Record the second piece of information, which is the actual triggering reason for the current connection reconstruction process;

[0175] The actual triggering reasons include at least one of the following:

[0176] The T316 timer is not configured;

[0177] T316 timer timed out;

[0178] SCG transmission paused;

[0179] SCG is in an inactive state;

[0180] Adding a PSCell in progress;

[0181] PSCell is undergoing changes.

[0182] Optionally, in one embodiment of this disclosure, the processing module is further configured to:

[0183] Record third information, which includes the specific reason corresponding to the current connection reconstruction process;

[0184] The specific reason is at least partially the same as the actual triggering reason.

[0185] Optionally, in one embodiment of this disclosure, the apparatus is further configured to:

[0186] The actual triggering reason for the current connection reconstruction process does not include a specific cause and is not logged.

[0187] Optionally, in one embodiment of this disclosure, the device is further used for at least one of the following:

[0188] The specific reason is determined based on the protocol;

[0189] The specific reason is determined based on the indication from the network device.

[0190] Optionally, in one embodiment of this disclosure, the processing module is further configured to:

[0191] Record all of the actual triggering reasons as the second information; or, select less than or equal to N reasons from the actual triggering reasons and record them as the second information, where N is a positive integer, and the number of selected actual triggering reasons is less than or equal to the total number of actual triggering reasons in the current connection reconstruction process;

[0192] The specific reasons corresponding to the current connection reconstruction process include multiple factors, and the recorded third information includes:

[0193] Record all specific reasons corresponding to the current connection reconstruction process as the third information; or, select less than or equal to N reasons from the specific reasons corresponding to the current connection reconstruction process and record them as the third information, where N is a positive integer, and the number of selected specific reasons is less than or equal to the total number of specific reasons corresponding to the current connection reconstruction process.

[0194] Optionally, in one embodiment of this disclosure, the processing module is further configured to:

[0195] The terminal device autonomously selects less than or equal to N reasons; and / or

[0196] Select N reasons based on priority, where different reasons correspond to different priorities.

[0197] Optionally, in one embodiment of this disclosure, the apparatus is further configured to:

[0198] The N is determined based on the agreement; and / or

[0199] The N is determined based on the indications from the network device.

[0200] Optionally, in one embodiment of this disclosure, the processing module is further configured to:

[0201] The timing duration of the T316 timer is recorded as the second information;

[0202] The processing module is also used for:

[0203] The timing duration of the T316 timer is recorded as the third information.

[0204] Optionally, in one embodiment of this disclosure, the processing module is further configured to:

[0205] Information related to MCG link failures will be recorded in the RLF report.

[0206] Optionally, in one embodiment of this disclosure, the transceiver module is further configured to:

[0207] The RLF Report is reported to the network device based on the network device's request.

[0208] Optionally, in one embodiment of this disclosure, the apparatus is further configured to:

[0209] The network device sends capability information, which is used to indicate whether the terminal device supports recording and reporting information related to the MCG link failure.

[0210] Figure 16This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure, as shown below. Figure 16 As shown, the device may include:

[0211] The transceiver module is used to receive information reported by the terminal device, which is information related to the MCG link failure recorded by the terminal device after the MCG link failure occurs.

[0212] In summary, in the communication device provided in this embodiment, in response to an MCG RLF occurring on the terminal device, the terminal device records information related to the MCG link failure and reports the recorded information to the network device. This "information related to the MCG link failure" indicates whether the MCG link cannot be quickly restored using the fast MCG link recovery mechanism, and whether a connection reconstruction process needs to be triggered to restore the MCG link. Therefore, by enabling terminal devices to record information related to MCG link failure and report this information to the network device, when a terminal device needs to trigger a connection reconstruction process to restore the MCG link, the network device can determine the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link based on the information reported by the terminal. This allows for corresponding optimization and adjustments to the terminal device to prevent future occurrences of the same reason preventing the terminal device from using the fast MCG link recovery mechanism to quickly restore the MCG link. Consequently, when the terminal device experiences another MCG RLF, it will not need to trigger a connection reconstruction process to restore the MCG link; instead, it can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, resulting in shorter recovery time and higher efficiency.

[0213] Optionally, in one embodiment of this disclosure, the information is information related to the MCG link failure recorded by the terminal device after an MCG RLF occurs and when it is determined that a connection reconstruction process should be triggered to restore the MCG link.

[0214] Optionally, in one embodiment of this disclosure, the transceiver module is further configured to:

[0215] The terminal device receives first information, which includes at least one of the following:

[0216] Is the T316 timer configured?

[0217] Has the T316 timer timed out?

[0218] Is SCG transmission paused?

[0219] Is SCG in an active state?

[0220] Is a PSCell being added?

[0221] Is a PSCell change in progress?

[0222] Optionally, in one embodiment of this disclosure, the transceiver module is further configured to:

[0223] Receive the second information reported by the terminal device, which is the actual triggering reason for the current connection reconstruction process;

[0224] The actual triggering reasons include at least one of the following:

[0225] The T316 timer is not configured;

[0226] T316 timer timed out;

[0227] SCG transmission paused;

[0228] SCG is in an inactive state;

[0229] Adding a PSCell in progress;

[0230] PSCell is undergoing changes.

[0231] Optionally, in one embodiment of this disclosure, the transceiver module is further configured to:

[0232] Receive third information reported by the terminal device, the third information including a specific reason included in the actual triggering reason of the current connection reconstruction process;

[0233] The specific reason is at least partially the same as the actual triggering reason.

[0234] Optionally, in one embodiment of this disclosure, the apparatus is further configured to:

[0235] Indicate the specific reason to the terminal device.

[0236] Optionally, in one embodiment of this disclosure, the apparatus is further configured to:

[0237] Indicate the value of N to the terminal device, where N is a positive integer and is the maximum number of reasons that may be included in the second or third information.

[0238] Optionally, in one embodiment of this disclosure, the actual triggering reason for the current connection reconstruction process includes a T316 timer timeout, and the second information also includes the timing duration of the T316 timer;

[0239] The specific reason corresponding to the current connection reconstruction process includes a T316 timer timeout, and the third information also includes the timing duration of the T316 timer.

[0240] Optionally, in one embodiment of this disclosure, the transceiver module is further configured to:

[0241] Receive the information reported by the terminal device via RLF Report.

[0242] Optionally, in one embodiment of this disclosure, the apparatus is further configured to:

[0243] A request message is sent to the terminal device, the request message being used to request the terminal device to report the information.

[0244] Optionally, in one embodiment of this disclosure, the apparatus is further configured to:

[0245] The terminal device receives capability information sent by the terminal device, the capability information being used to indicate whether the terminal device supports recording and reporting information related to the MCG link failure.

[0246] Please see Figure 17 , Figure 17 This is a schematic diagram of the structure of a communication device 1700 provided in an embodiment of this application. The communication device 1700 can be a network device, a terminal device, a chip, chip system, or processor that supports the implementation of the above methods in a network device, or a chip, chip system, or processor that supports the implementation of the above methods in a terminal device. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0247] The communication device 1700 may include one or more processors 1701. The processor 1701 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0248] Optionally, the communication device 1700 may further include one or more memories 1702, on which a computer program 1704 may be stored. The processor 1701 executes the computer program 1704 to cause the communication device 1700 to perform the methods described in the above method embodiments. Optionally, the memory 1702 may also store data. The communication device 1700 and the memory 1702 may be provided separately or integrated together.

[0249] Optionally, the communication device 1700 may also include a transceiver 1705 and an antenna 1706. The transceiver 1705 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1705 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0250] Optionally, the communication device 1700 may further include one or more interface circuits 1707. The interface circuits 1707 are used to receive code instructions and transmit them to the processor 1701. The processor 1701 executes the code instructions to cause the communication device 1700 to perform the methods described in the above method embodiments.

[0251] In one implementation, the processor 1701 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or for transmitting or relaying signals.

[0252] In one implementation, processor 1701 may store computer program 1703, which runs on processor 1701 and causes communication device 1700 to perform the methods described in the above method embodiments. Computer program 1703 may be embedded in processor 1701, in which case processor 1701 may be implemented in hardware.

[0253] In one implementation, the communication device 1700 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), p-type metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0254] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 17 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0255] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0256] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0257] (3) ASIC, such as modem;

[0258] (4) Modules that can be embedded in other devices;

[0259] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0260] (6) Others, etc.

[0261] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 18 The diagram shows the structure of the chip. Figure 18 The chip shown includes a processor 1801 and an interface 1802. There can be one or more processors 1801, and multiple interfaces 1802.

[0262] Optionally, the chip also includes a memory 1803, which is used to store necessary computer programs and data.

[0263] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0264] This application also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0265] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0266] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0267] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., involved in this application are merely for the convenience of description and are not intended to limit the scope of the embodiments of this application, nor do they indicate the order of sequence.

[0268] At least one in this application can also be described as one or more, and multiple can be two, three, four or more, and this application does not impose any limitation. In the embodiments of this application, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order or size among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0269] The correspondences shown in the tables of this application can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this application is not limited to these values. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this application may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headings of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0270] The term "predefined" in this application can be understood as definition, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0271] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0272] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0273] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A reporting method, characterized by, The method is executed by a terminal device, and the method comprises: In response to occurrence of a master cell group radio link failure (MCG RLF), recording information related to the MCG link failure; Reporting the recorded information to a network device; The recording of the information related to the MCG link failure comprises: In response to determination that a connection reestablishment procedure is to be triggered to recover the MCG link, recording information related to the MCG link failure; The recording of the information related to the MCG link failure comprises: Recording second information, the second information being an actual trigger cause of a current connection reestablishment procedure; The actual trigger cause comprises at least one of: A T316 timer not being configured; A T316 timer expiring; SCG transmission being suspended; The SCG being in an inactive state; A PSCell addition being in progress; A PSCell change being in progress; In response to the actual trigger cause of the current connection reestablishment procedure comprising a plurality of trigger causes, the recording of the second information comprises: Selecting, from the actual trigger causes, less than or equal to N causes to record as the second information, N being a positive integer, and the number of selected actual trigger causes being less than or equal to the total number of actual trigger causes of the current connection reestablishment procedure; The selecting of less than or equal to N causes comprises: The terminal device autonomously selecting less than or equal to N causes; Selecting less than or equal to N causes based on priority, different causes corresponding to different priorities.

2. The method of claim 1, wherein, The recording of the information related to the MCG link failure comprises: Recording third information, the third information comprising a specific cause corresponding to the current connection reestablishment procedure; The specific cause being at least partially the same as the actual trigger cause.

3. The method of claim 2, wherein, The method further comprises at least one of: Determining the specific cause based on a protocol; Determining the specific cause based on an indication of the network device.

4. The method of claim 2, wherein, In response to the specific cause corresponding to the current connection reestablishment procedure comprising a plurality of trigger causes, the recording of the third information comprises: Recording all of the specific causes corresponding to the current connection reestablishment procedure as the third information; or selecting, from the specific causes corresponding to the current connection reestablishment procedure, less than or equal to N causes to record as the third information, N being a positive integer, and the number of selected specific causes being less than or equal to the total number of specific causes corresponding to the current connection reestablishment procedure.

5. The method of claim 1 or 4, wherein, The method further comprises at least one of: Determining the N based on a protocol agreement; Determining the N based on an indication of the network device.

6. The method of claim 2, wherein, In response to the actual trigger cause of the current connection reestablishment procedure comprising T316 timer expiration, the method further comprises: Recording a timing duration of the T316 timer as the second information; In response to the specific cause corresponding to the current connection reestablishment procedure comprising T316 timer expiration, the method further comprises: Recording a timing duration of the T316 timer as the third information.

7. The method of any one of claims 1-4, wherein, The recording of the information related to the MCG link failure comprises: Recording the information related to the MCG link failure into an RLF Report.

8. The method of claim 7, wherein, The reporting of the recorded information to the network device comprises: reporting, to a network device, the RLF Report based on a request of the network device.

9. The method of any one of claims 1-4, wherein, The method further includes: sending, to the network device, capability information indicating whether the terminal device supports recording and reporting the information related to the MCG link failure.

10. A reporting method, characterized by, The method is performed by a network device, and the method includes: receiving information reported by a terminal device, the information being recorded by the terminal device after occurrence of MCG RLF and being related to MCG link failure; The information is recorded by the terminal device after occurrence of MCG RLF and determination of triggering a connection reestablishment procedure to recover the MCG link. The receiving of the information reported by the terminal device includes: receiving second information reported by the terminal device, the second information being an actual trigger cause of a current connection reestablishment procedure; The actual trigger cause includes at least one of the following: T316 timer is not configured; T316 timer is timed out; SCG transmission is suspended; SCG is in an inactivated state; PSCell addition is in progress; PSCell change is in progress; In response to the actual trigger cause of the current connection reestablishment procedure including multiple trigger causes, the second information includes less than or equal to N trigger causes. The less than or equal to N trigger causes are determined by the terminal device autonomously, and the less than or equal to N trigger causes are selected by the terminal device based on priorities, different trigger causes corresponding to different priorities.

11. The method of claim 10, wherein, The receiving of the information reported by the terminal device includes: receiving third information reported by the terminal device, the third information including a specific trigger cause included in the actual trigger cause of the current connection reestablishment procedure; The specific trigger cause is at least partially the same as the actual trigger cause.

12. The method of claim 11, wherein, The method further includes: indicating the specific trigger cause to the terminal device.

13. The method of claim 11, wherein, The method further includes: indicating a value of N to the terminal device, N being a positive integer and N being a maximum number of trigger causes that can be included in the second information or the third information.

14. The method of claim 11, wherein, In response to the actual trigger cause of the current connection reestablishment procedure including T316 timer being timed out, the second information further includes a timing duration of the T316 timer; In response to the specific trigger cause corresponding to the current connection reestablishment procedure including T316 timer being timed out, the third information further includes the timing duration of the T316 timer.

15. The method of any one of claims 10-13, wherein, The receiving of the information reported by the terminal device includes: receiving the information reported by the terminal device through an RLF Report.

16. The method of claim 15, wherein, The method further includes: sending, to the terminal device, a request message for requesting the terminal device to report the information.

17. The method of any one of claims 10-13, wherein, The method further includes: receiving capability information sent by the terminal device, the capability information indicating whether the terminal device supports recording and reporting the information related to the MCG link failure.

18. A communications device, characterized by The apparatus is configured in a terminal device and includes: a processing module configured to record information related to MCG link failure in response to occurrence of MCG RLF (Master Cell Group Radio Link Failure). The transceiver module is configured to report the recorded information to a network device; The processing module is further configured to: In response to determining that a connection reestablishment procedure is to be triggered to recover the MCG link, record information related to the MCG link failure; The processing module is further configured to: Record second information, which is the actual trigger cause of the current connection reestablishment procedure; The actual trigger cause includes at least one of: T316 timer is not configured; T316 timer is timed out; SCG transmission is suspended; SCG is in an inactive state; PSCell addition is in progress; PSCell change is in progress; In response to the actual trigger cause of the current connection reestablishment procedure including multiple causes, the second information includes less than or equal to N causes from the actual trigger cause; The terminal device autonomously selects less than or equal to N causes; Less than or equal to N causes are selected based on priority, wherein different causes correspond to different priorities. The apparatus is configured in a network device, comprising: The transceiver module is configured to receive information reported by a terminal device, the information being information related to MCG link failure recorded by the terminal device after MCG RLF occurs; 19. A communications device, characterized by The information is information related to MCG link failure recorded by the terminal device after MCG RLF occurs and when it is determined that a connection reestablishment procedure is to be triggered to recover the MCG link; The transceiver module is configured to receive information reported by a terminal device, the information being information related to MCG link failure recorded by the terminal device after MCG RLF occurs; The second information is the actual trigger cause of the current connection reestablishment procedure; The actual trigger cause includes at least one of: T316 timer is not configured; T316 timer is timed out; SCG transmission is suspended; SCG is in an inactive state; PSCell addition is in progress; PSCell change is in progress; In response to the actual trigger cause of the current connection reestablishment procedure including multiple causes, the second information includes less than or equal to N causes from the actual trigger cause; The less than or equal to N causes are autonomously determined by the terminal device, and the less than or equal to N causes are selected by the terminal device based on priority, wherein different causes correspond to different priorities. The apparatus includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program stored in the memory to cause the apparatus to perform the method of any one of claims 1 to 9, or the processor executes the computer program stored in the memory to cause the apparatus to perform the method of any one of claims 10 to 17. Comprising:

20. A communications device, characterized by A processor and an interface circuit, wherein 21. A communications device, characterized by The interface circuit is configured to receive code instructions and transmit them to the processor; ​ ​ the processor is configured to execute the code instructions to perform the method of any one of claims 1 to 9, or to execute the code instructions to perform the method of any one of claims 10 to 17.

22. A computer readable storage medium storing instructions which, when executed, cause the method of any one of claims 1 to 9 to be implemented, or which, when executed, cause the method of any one of claims 10 to 17 to be implemented.

Images