[go: up one dir, main page]

WO2024031272A1 - 一种上报方法、装置、设备及存储介质 - Google Patents

一种上报方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2024031272A1
WO2024031272A1 PCT/CN2022/110948 CN2022110948W WO2024031272A1 WO 2024031272 A1 WO2024031272 A1 WO 2024031272A1 CN 2022110948 W CN2022110948 W CN 2022110948W WO 2024031272 A1 WO2024031272 A1 WO 2024031272A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal device
mcg
mcg link
connection reestablishment
Prior art date
Application number
PCT/CN2022/110948
Other languages
English (en)
French (fr)
Inventor
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280002779.3A priority Critical patent/CN115516916A/zh
Priority to PCT/CN2022/110948 priority patent/WO2024031272A1/zh
Publication of WO2024031272A1 publication Critical patent/WO2024031272A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to reporting methods, devices, equipment and storage media.
  • the Multi-Radio Dual Connectivity (MR-DC) technology is introduced to allow terminal equipment to access two cell groups at the same time (that is, access the Master Cell Group (Master Cell Group) through the main base station). , MCG), access the secondary cell group (Secondary Cell Group, SCG)) through the secondary base station to improve the data throughput rate and the mobility performance of the UE.
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • MCG wireless link failure Radio Link Failure, RLF
  • RLF Radio Link Failure
  • MCG RLF Radio Link Failure
  • the fast MCG link recovery mechanism is: sending MCGFailureInformation (MCG failure information) message to the main base station through SCG, so that the terminal device can be quickly switched to a new primary cell (Primary Cell, PCell) to restore the MCG link.
  • MCG failure information MCG failure information
  • PCell Primary Cell
  • the terminal device needs to trigger the connection reestablishment process to restore the MCG link every time an MCG RLF occurs, which results in a long time and low efficiency.
  • the reporting method, device, equipment and storage medium proposed in this disclosure are to solve the technical problems in the related art that the MCG link recovery method is time-consuming and low in efficiency.
  • embodiments of the present disclosure provide a reporting method, which is executed by a terminal device and includes:
  • a reporting method In response to an MCG RLF occurring in a terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • embodiments of the present disclosure provide a reporting method, which is executed by a network device and includes:
  • 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.
  • an embodiment of the present disclosure provides a communication device, which is configured in a terminal device and includes:
  • a processing module configured to record information related to the MCG link failure in response to the occurrence of a primary cell group radio link failure MCG RLF;
  • the transceiver module is configured to report the recorded information to the network device.
  • an embodiment of the present disclosure provides a communication device, which is configured in a network device and includes:
  • the transceiver module is configured to receive information reported by the terminal device.
  • the information is the information related to the MCG link failure recorded by the terminal device after the MCG RLF occurs.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the second aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication system, which includes the communication device described in the third aspect to the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect to The communication device according to the sixth aspect, or the system includes the communication device according to the seventh aspect to the communication device according to the eighth aspect, or the system includes the communication device according to the ninth aspect to the tenth aspect. the above-mentioned communication device.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned network device and/or the above-mentioned terminal device.
  • the network device is caused to execute the above-mentioned The method described in the first aspect, and/or causing the terminal device to perform the method described in the second aspect.
  • the present disclosure also provides a computer program product including a computer program, which, when run on a computer, causes the computer to execute the method described in any one of the above first to second aspects.
  • the present disclosure provides a chip system.
  • the chip system includes at least one processor and an interface, and is used to support a network device to implement the functions involved in the method described in the first aspect, and/or to support a terminal device.
  • Implement the functions involved in the method described in the second aspect for example, determine or process at least one of the data and information involved in the above method.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data of the source secondary node.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in any one of the above first to second aspects.
  • Figure 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure
  • Figure 2 is a schematic flowchart of a reporting method provided by another embodiment of the present disclosure.
  • Figure 3 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 4 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 5 is a schematic flowchart of a reporting method provided by another embodiment of the present disclosure.
  • Figure 6 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 7 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 8 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 9 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 10 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 11 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 12 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 13 is a schematic flow chart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 14 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 15 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 16 is a schematic structural diagram of a communication device provided by another embodiment of the present disclosure.
  • Figure 17 is a block diagram of a communication device provided by an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • the words "if” and “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
  • the terminal equipment establishes "Dual Connectivity" with the master base station (Master Node, MN) and the secondary base station (Secondary Node, SN), and uses the master cell group (Master Cell Group, MCG) and the secondary cell group (Secondary Cell Group) at the same time , SCG) resources. Among them, there is a control connection between the main base station and the core network.
  • the mobile station either initiates call reestablishment or forcibly disconnects the link. Since forcibly disconnecting the link actually introduces a call drop process, it must be ensured that the mobile station considers the wireless link failure only when the communication quality is truly unacceptable.
  • PCell Primary Cell
  • PCell The cell used to initiate initial access under MCG.
  • PSCell Primary Secondary Cell
  • FIG. 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure.
  • the communication system may include but is not limited to one network device and one terminal device.
  • the number and form of devices shown in Figure 1 are only for examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more devices may be included. Network equipment, two or more terminal devices.
  • the communication system shown in Figure 1 includes a network device 11 and a terminal device 12 as an example.
  • LTE long term evolution
  • 5th generation fifth generation
  • 5G new radio (NR) system 5th generation new radio
  • the network device 11 in the embodiment of the present disclosure is an entity on the network side that is used to transmit or receive signals.
  • the network device 11 may be an evolved base station (evolved NodeB, eNB), a transmission reception point (TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or other base stations in future mobile communication systems. Base stations or access nodes in wireless fidelity (WiFi) systems, etc.
  • the embodiments of the present disclosure do not limit the specific technologies and specific equipment forms used by network equipment.
  • the network equipment provided by the embodiments of the present disclosure may be composed of a centralized unit (CU) and a distributed unit (DU).
  • the CU may also be called a control unit (control unit).
  • CU-DU is used.
  • the structure can separate the protocol layers of network equipment, such as base stations, and place some protocol layer functions under centralized control on the CU. The remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the
  • the terminal device 12 in the embodiment of the present disclosure may be an entity on the user side for receiving or transmitting signals, such as a mobile phone.
  • Terminal equipment can also be called terminal equipment (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal equipment (mobile terminal, MT), etc.
  • the terminal device can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the terminal equipment.
  • FIG. 2 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 2a, the reporting method may include the following steps:
  • Step 201 In response to the occurrence of MCG RLF, record information related to the MCG link failure.
  • recording information related to MCG link failure may specifically include: recording first information, and the first information may include at least one of the following:
  • Step 202 Report the recorded information to the network device.
  • the terminal device reports its recorded information (ie, the above-mentioned first information) to the network device based on the request of the network device.
  • the "information related to MCG link failure" in the above step 201 can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reconstruction process needs to be triggered to restore the MCG link.
  • the T316 timer when the T316 timer is not configured, the T316 timer times out, SCG transmission is suspended, SCG is in an inactive state, PSCell addition is currently in progress, or PSCell change is currently in progress, it means that the fast MCG link cannot be restored at present. mechanism to quickly restore the MCG link, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the above-mentioned "triggering the connection reestablishment process” generally takes a long time, which will lead to low recovery efficiency of the MCG link.
  • the terminal device will record the information related to the MCG link failure and report it to the network device, so that when the terminal device currently occurs
  • the network device side can determine based on the information related to the MCG link failure reported by the terminal.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 3 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 3, the reporting method may include the following steps:
  • Step 301 In response to the occurrence of MCG RLF, trigger the connection reestablishment process and record information related to MCG link failure.
  • the difference between the embodiment corresponding to Figure 3 and the embodiment corresponding to Figure 2 is that in Figure 2, after MCG RLF occurs in the terminal device, information related to MCG link failure is recorded.
  • the embodiment of Figure 3 is: when an MCG RLF occurs on the terminal device and it is determined to trigger the connection reestablishment process, the terminal device only records information related to the MCG link failure.
  • Step 302 Report the recorded information to the network device.
  • the terminal device reports the recorded information related to the MCG link failure to the network device, and the network device can infer based on the content of the information related to the MCG link failure.
  • the reason why the terminal device needs to restore the MCG link by triggering the connection reestablishment process after MCG RLF occurs that is, the reason why the fast MCG link recovery mechanism cannot be used to restore the MCG link after MCG RLF occurs), so that the subsequent MCG link can be restored based on this reason
  • the information related to MCG link failure reported by the terminal device to the network device is:
  • T316 timer is not configured
  • the network device can infer that the reason why the terminal device needs to trigger the connection reestablishment process to restore the MCG link after MCG RLF occurs is that the T316 timer is not configured and the SCG is currently in an inactive state.
  • the network device can make corresponding optimization adjustments to the terminal device.
  • the optimization adjustments can include, for example, configuring the T316 timer to the terminal device, and/or controlling the SCG to be in an active state.
  • the fast MCG link recovery mechanism can be directly used to restore the MCG link, which is shorter in time and more efficient.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 4 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 4, the reporting method may include the following steps:
  • Step 401 Record second information, which is the actual triggering reason of the current connection reestablishment process.
  • the second information essentially represents: the actual reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link.
  • the second information may include at least one of the following:
  • T316 timer is not configured
  • SCG is in an inactive state
  • the terminal device may record all the actual triggering reasons as the second information.
  • the terminal device may select reasons less than or equal to N from the actual triggering reasons to record as the second information, where N is a positive integer.
  • N may be agreed by the terminal device based on the protocol, and/or may also be determined by the terminal device based on instructions from the network device, and the number of actual triggering reasons specifically selected by the terminal device should be less than or equal to the current connection. The total number of actual triggering reasons for the reconstruction process.
  • the above-mentioned terminal device selects less than or equal to N reasons to record as the second information. Specifically, it can be understood as: when the total number of actual triggering reasons of the current connection reestablishment process When the number is less than N, then less than N reasons can be selected from the actual triggering reasons of the current connection reestablishment process and recorded as the second information.
  • the terminal device cannot select 4 reasons as the second information from the actual triggering reasons of the current connection reestablishment process.
  • the terminal device can select less than 4 reasons as the second information.
  • Second information for example, the terminal device can choose to use "T316 timer not configured” among the actual triggering reasons of the current connection reestablishment process as the second information, or the terminal device can choose to use the actual triggering reason of the current connection reestablishment process as the second information.
  • the two reasons "T316 timer is not configured and SCG is in an inactive state" are used as the second information.
  • the terminal device when the terminal device selects less than or equal to N reasons from the actual triggering reasons, the terminal device may arbitrarily select less than or equal to N reasons based on independent selection, and/or , or it may be that the terminal device preferentially selects reasons less than or equal to N with higher priority based on priority. Different reasons correspond to different priorities. The correspondence between the reasons and the priorities may be agreed upon by the protocol or indicated by the network device. For example, the priority order between various reasons can be: T316 timer timeout > SCG suspends transmission > PSCell is being added or changed > SCG is in an inactive state.
  • the terminal device when the actual triggering cause of the current connection reestablishment process includes the timeout of the T316 timer, the terminal device should also record the timing duration of the T316 timer as the second information.
  • Step 402 Report the second information to the network device.
  • the terminal device reports the second information to the network device, and the network device can determine based on the content of the second information that the terminal device needs to trigger the connection after MCG RLF occurs.
  • the reason for rebuilding the process to restore the MCG link that is, the reason why the fast MCG link recovery mechanism cannot be used to restore the MCG link after MCG RLF occurs), so that the terminal equipment can be optimized and adjusted accordingly based on this reason to prevent subsequent "due to The same reason leads to the situation where the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link.
  • the second information reported by the terminal device to the network device is:
  • the T316 timer times out, and the duration of the T316 timer is 40 milliseconds (ms).
  • the network device can infer based on the second information reported by the terminal device that the reason why the terminal device needs to trigger the connection reestablishment process to restore the MCG link after the MCG RLF occurs is: the T316 timer expires due to the short timing length. The server times out. At this time, the network device can make corresponding optimization adjustments to the terminal device.
  • the optimization adjustment can be as follows: configuring a new timing duration for the T316 timer. The new timing duration is greater than the original timing duration of the T316 timer, and the new timing duration is longer than the original timing duration of the T316 timer.
  • the timing length should be able to support the completion of the fast MCG link recovery mechanism to ensure that after subsequent MCG RLF occurs on the terminal device, the MCG link can be successfully restored based on the fast MCG link recovery mechanism.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG. 5 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 5, the reporting method may include the following steps:
  • Step 501 In response to the occurrence of MCG RLF, the connection reestablishment process is triggered, and the actual triggering reason of the current connection reestablishment process includes a specific reason, and third information is recorded.
  • the third information includes the specific reason corresponding to the current connection reestablishment process.
  • the specific reason may be determined by the terminal device based on the protocol agreement, and/or it may also be determined by the terminal device based on instructions from the network device.
  • the specific reason may specifically be any one or more of all possible reasons that cause the MCG link to be restored by triggering the connection reestablishment process after the MCG RLF occurs.
  • the specific reason may include at least one of: T316 timer timeout, SCG transmission pause, PSCell addition in progress, and PSCell change in progress.
  • the specific reasons include T316 timer timeout, SCG transmission pause, PSCell addition in progress, PSCell change in progress; and, the actual triggering reasons of the current connection reestablishment process are: T316 timer not configured, SCG transmission pause. At this time, only "SCG transmission pause" is recorded as the third information.
  • the terminal device may use all the specific reasons corresponding to the current connection reestablishment process as third information. In another embodiment of the present disclosure, the terminal device may select less than or equal to N reasons from the specific reasons corresponding to the current connection reestablishment process to record as the third information, where N is a positive integer.
  • the above-mentioned N may be agreed upon by the terminal device based on the protocol, and/or may also be determined by the terminal device based on instructions from the network device. For specific details related to this part of the content, please refer to the above embodiment description.
  • the terminal device when the specific reason corresponding to the current connection reestablishment process includes the T316 timer timeout, the terminal device should also record the timing length of the T316 timer as the third information.
  • Step 502 Report the third information to the network device.
  • step 502 please refer to the description of the above embodiment.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 6 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 6, the reporting method may include the following steps:
  • Step 601 In response to the occurrence of MCG RLF, the connection reestablishment process is triggered, and the actual triggering reason of the current connection reestablishment process does not include a specific reason, and no information is recorded.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 7 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 7, the reporting method may include the following steps:
  • Step 701 In response to the occurrence of MCG RLF, record information related to the MCG link failure.
  • Step 702 Record the information related to the MCG link failure into an RLF report (Report) (such as VarRLF-Report).
  • RLF report Report
  • Step 703 Report the RLF Report to the network device.
  • the terminal device restores the MCG link based on the connection reestablishment process, it will report the RLF Report to the network device based on the request of the network device.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 8 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 8, the reporting method may include the following steps:
  • Step 801 Send capability information to the network device, where the capability information is used to indicate whether the terminal device supports recording and reporting the information related to MCG link failure.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 9 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 9, the reporting method may include the following steps:
  • Step 901 Receive information reported by the terminal device.
  • the information is information related to the MCG link failure recorded by the terminal device after the MCG RLF occurs.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 10 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 10, the reporting method may include the following steps:
  • Step 1001 Receive information reported by the terminal device.
  • the information is the information related to the MCG link failure recorded when the terminal device determines to trigger the connection reestablishment process to restore the MCG link after the MCG RLF occurs.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 11 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 11, the reporting method may include the following steps:
  • Step 1101 Receive second information reported by the terminal device, where the second information is the actual triggering reason for the current connection reestablishment process.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 12 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 12, the reporting method may include the following steps:
  • Step 1201 Receive third information reported by the terminal device, where the third information includes a specific reason included in the actual triggering reason of the current connection reestablishment process.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 13 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 13, the reporting method may include the following steps:
  • Step 1301 Send a request message to the terminal device, where the request message is used to request the terminal device to report the information.
  • Step 1302 Receive the information reported by the terminal device through RLF Report.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 14 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 14, the reporting method may include the following steps:
  • Step 1401 Receive capability information sent by the terminal device, where the capability information is used to indicate whether the terminal device supports recording and reporting the information related to MCG link failure.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 15 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure. As shown in Figure 14, the device may include:
  • a processing module configured to record information related to the MCG link failure in response to the occurrence of a primary cell group radio link failure MCG RLF;
  • the transceiver module is configured to report the recorded information to the network device.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and will report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • the processing module is also used to:
  • connection reestablishment process In response to determining that the connection reestablishment process is to be triggered to restore the MCG link, information related to the MCG link failure is recorded.
  • the processing module is also used to:
  • first information where the first information includes at least one of the following:
  • the processing module is also used to:
  • the actual triggering reasons include at least one of the following:
  • T316 timer is not configured
  • SCG is in an inactive state
  • the processing module is also used to:
  • the specific cause is at least partially the same as the actual triggering cause.
  • the device is also used for:
  • the device is also used for at least one of the following:
  • the specific cause is determined based on indications from the network device.
  • the processing module is also used to:
  • N is a positive integer, and the selected actual triggering The number of reasons is less than or equal to the total number of actual triggering reasons for the current connection reestablishment process;
  • the third information recorded includes:
  • the processing module is also used to:
  • the terminal device independently selects less than or equal to N reasons; and/or
  • the device is also used for:
  • the N is determined based on instructions from the network device.
  • the processing module is also used to:
  • the processing module is also used to:
  • the timing duration of the T316 timer is recorded as the third information.
  • the processing module is also used to:
  • the transceiver module is also used to:
  • the device is also used for:
  • Figure 16 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure. As shown in Figure 16, the device may include:
  • the transceiver module is configured to receive information reported by the terminal device.
  • the information is the information related to the MCG link failure recorded by the terminal device after the MCG RLF occurs.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and will report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reconstruction process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • the information is information related to MCG link failure recorded by the terminal device after MCG RLF occurs and when it is determined to trigger the connection reestablishment process to restore the MCG link. .
  • the transceiver module is also used to:
  • the transceiver module is also used to:
  • the actual triggering reasons include at least one of the following:
  • T316 timer is not configured
  • SCG is in an inactive state
  • the transceiver module is also used to:
  • the specific cause is at least partially the same as the actual triggering cause.
  • the device is also used for:
  • the device is also used for:
  • N is a positive integer
  • N is the maximum number of reasons that can be included in the second information or the third information.
  • the second information in response to the actual triggering reason of the current connection reestablishment process including T316 timer timeout, the second information also includes the timing duration of the T316 timer;
  • the third information In response to the specific reason corresponding to the current connection reestablishment process including T316 timer timeout, the third information also includes the timing duration of the T316 timer.
  • the transceiver module is also used to:
  • the device is also used for:
  • the device is also used for:
  • Receive capability information sent by the terminal device where the capability information is used to indicate whether the terminal device supports recording and reporting the information related to MCG link failure.
  • FIG 17 is a schematic structural diagram of a communication device 1700 provided by an embodiment of the present application.
  • the communication device 1700 may be a network device, a terminal device, a chip, a chip system, or a processor that supports a network device to implement the above method, or a chip, a chip system, or a processor that supports a terminal device to implement the above method. Processor etc.
  • the device can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • Communication device 1700 may include one or more processors 1701.
  • the processor 1701 may be a general-purpose processor or a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data.
  • the central processor can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.) and execute computer programs. , processing data for computer programs.
  • the communication device 1700 may also include one or more memories 1702, on which a computer program 1704 may be stored.
  • the processor 1701 executes the computer program 1704, so that the communication device 1700 performs the steps described in the above method embodiments. method.
  • the memory 1702 may also store data.
  • the communication device 1700 and the memory 1702 can be provided separately or integrated together.
  • the communication device 1700 may also include a transceiver 1705 and an antenna 1706.
  • the transceiver 1705 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver 1705 may include a receiver and a transmitter.
  • the receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function;
  • the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.
  • the communication device 1700 may also include one or more interface circuits 1707.
  • the interface circuit 1707 is 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 method described in the above method embodiment.
  • the processor 1701 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the processor 1701 may store a computer program 1703, and the computer program 1703 runs on the processor 1701, causing the communication device 1700 to perform the method described in the above method embodiment.
  • the computer program 1703 may be solidified in the processor 1701, in which case the processor 1701 may be implemented by hardware.
  • the communication device 1700 may include a circuit, which may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processor and transceiver described in this application can be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits RFICs, mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS n-type metal oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • 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 not be limited by FIG. 17 .
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • the communication device may be a chip or a chip system
  • the schematic structural diagram of the chip shown in FIG. 18 refer to the schematic structural diagram of the chip shown in FIG. 18 .
  • the chip shown in Figure 18 includes a processor 1801 and an interface 1802.
  • the number of processors 1801 may be one or more, and the number of interfaces 1802 may be multiple.
  • the chip also includes a memory 1803, which is used to store necessary computer programs and data.
  • This application also provides a readable storage medium on which instructions are stored. When the instructions are executed by a computer, the functions of any of the above method embodiments are implemented.
  • This application also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs.
  • the computer program When the computer program is loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program may be stored in or transferred from one computer-readable storage medium to another, for example, the computer program may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • At least one in this application can also be described as one or more, and the plurality can be two, three, four or more, which is not limited by this application.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc.
  • the technical features described in “first”, “second”, “third”, “A”, “B”, “C” and “D” are in no particular order or order.
  • the corresponding relationships shown in each table in this application can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which are not limited by this application.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables may also be other names understandable by the communication device, and the values or expressions of the parameters may also be other values or expressions understandable by the communication device.
  • 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. wait.
  • Predefinition in this application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本公开提出一种上报方法、装置、设备及存储介质，所述方法包括：响应于发生主小区组无线链路失败MCG RLF后，记录与MCG链路失败相关的信息；向网络设备上报记录的所述信息。本公开的方法使得MCG链接恢复所需耗时较短，且效率较高。

Description

一种上报方法、装置、设备及存储介质 技术领域
本公开涉及通信技术领域，尤其涉及上报方法、装置、设备及存储介质。
背景技术
在通信系统中，通过引入多无线电双连接(Multi-Radio Dual Connectivity，MR-DC)技术，以便让终端设备能够同时接入两个小区组(即通过主基站接入主小区组(Master Cell Group，MCG)、通过辅基站接入辅小区组(Secondary Cell Group，SCG))，以此来提高数据吞吐率和UE的移动性能。
相关技术中，可能会发生MCG无线链路失败(Radio Link Failure，RLF)，其中，当发生MCG RLF时，若SCG的链路正常，则会基于快速MCG链路恢复机制来恢复MCG链接，该快速MCG链路恢复机制为：通过SCG向主基站发送MCGFailureInformation(MCG失败信息)消息，以便可以快速将终端设备切换到一个新的主小区(Primary Cell，PCell)来恢复MCG链接。以及，若发生MCG RLF时SCG的链路不正常，则此时终端设备即需要触发连接重建流程以恢复MCG链接，其中，“触发连接重建流程来恢复MCG链接”的过程所需时间较长。
但是，相关技术的方法中，若SCG的链路一直不正常，则终端设备每次发生MCG RLF后，均需要需要触发连接重建流程来恢复MCG链接，导致耗时较长，且效率较低。
发明内容
本公开提出的上报方法、装置、设备及存储介质，以解决相关技术中的MCG链接恢复方法的耗时较长，且效率较低的技术问题。
第一方面，本公开实施例提供一种上报方法，该方法被终端设备执行，包括：
响应于发生主小区组无线链路失败MCG RLF后，记录与MCG链路失败相关的信息；
向网络设备上报记录的所述信息。
本公开中，提供了一种上报方法，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
第二方面，本公开实施例提供一种上报方法，该方法被网络设备执行，包括：
接收终端设备上报的信息，所述信息为所述终端设备在发生MCG RLF后记录的与MCG链路失败相关的信息。
第三方面，本公开实施例提供一种通信装置，该装置被配置在终端设备中，包括：
处理模块，用于响应于发生主小区组无线链路失败MCG RLF后，记录与MCG链路失败相关的信息；
收发模块，用于向网络设备上报记录的所述信息。
第四方面，本公开实施例提供一种通信装置，该装置被配置在网络设备中，包括：
收发模块，用于接收终端设备上报的信息，所述信息为所述终端设备在发生MCG RLF后记录的与 MCG链路失败相关的信息。
第五方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十一方面，本公开实施例提供一种通信系统，该系统包括第三方面所述的通信装置至第四方面所述的通信装置，或者，该系统包括第五方面所述的通信装置至第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置至第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置至第十方面所述的通信装置。
第十二方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述网络设备和/或上述终端设备所用的指令，当所述指令被执行时，使所述网络设备执行上述第一方面所述的方法，和/或，使所述终端设备执行上述第二方面所述的方法。
第十三方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面的任一方面所述的方法。
第十四方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持网络设备实现第一方面至所述的方法所涉及的功能，和/或，支持终端设备实现第二方面所述的方法所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存源辅节点必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十五方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面的任一方面所述的方法。
附图说明
本公开上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中：
图1为本公开实施例提供的一种通信系统的架构示意图；
图2为本公开另一个实施例所提供的上报方法的流程示意图；
图3为本公开再一个实施例所提供的上报方法的流程示意图；
图4为本公开又一个实施例所提供的上报方法的流程示意图；
图5为本公开另一个实施例所提供的上报方法的流程示意图；
图6为本公开再一个实施例所提供的上报方法的流程示意图；
图7为本公开又一个实施例所提供的上报方法的流程示意图；
图8为本公开又一个实施例所提供的上报方法的流程示意图；
图9为本公开又一个实施例所提供的上报方法的流程示意图；
图10为本公开又一个实施例所提供的上报方法的流程示意图；
图11为本公开又一个实施例所提供的上报方法的流程示意图；
图12为本公开又一个实施例所提供的上报方法的流程示意图；
图13为本公开又一个实施例所提供的上报方法的流程示意图；
图14为本公开又一个实施例所提供的上报方法的流程示意图；
图15为本公开一个实施例所提供的通信装置的结构示意图；
图16为本公开另一个实施例所提供的通信装置的结构示意图；
图17是本公开一个实施例所提供的一种通信装置的框图；
图18为本公开一个实施例所提供的一种芯片的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”及“若”可以被解释成为“在……时”或“当……时”或“响应于确定”。
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的要素。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。
为了便于理解，首先介绍本申请涉及的术语。
1、多无线电双连接(Multi-Radio Dual Connectivity，MR-DC)
终端设备和主基站(Master Node，MN)、辅基站(Secondary Node，SN)建立“双连接(Dual Connectivity)”，同时使用主小区组(Master Cell Group，MCG)和辅小区组(Secondary Cell Group，SCG)的资源。其中，主基站与核心网存在控制连接。
2、无线链路失败(Radio Link Failure，RLF)
这是由于系统存在干扰或接收电平很低，导致移动台无法正确解码网络的发送来的信息，且无法通过功率控制或切换来控制时(既所谓的无线链路故障)，当出现这种情况时移动台或者启动呼叫重建，或者强行拆链。由于强行拆链实际上引入了一次掉话的过程，因而必须保证只有在通信质量确实无法接受时，移动台才认为是无线链路故障。
3、主小区(Primary Cell，PCell)
MCG下用于发起初始接入的小区称为PCell。
4、主辅小区(Primary Secondary Cell，PSCell)
在SCG下发起初始接入的小区。
为了更好的理解本申请实施例公开的一种上报方法，下面首先对本申请实施例适用的通信系统进行描述。
请参见图1，图1为本公开实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络设备和一个终端设备，图1所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络设备，两个或两个以上的终端设备。图1所示的通信系统以包括一个网络设备11、一个终端设备12为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term  evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本公开实施例中的网络设备11是网络侧的一种用于发射或接收信号的实体。例如，网络设备11可以为演进型基站(evolved NodeB，eNB)、发送接收点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本公开的实施例对网络设备所采用的具体技术和具体设备形态不做限定。本公开实施例提供的网络设备可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将网络设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的终端设备12可以是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
下面参考附图对本公开实施例所提供的上报方法、装置、设备及存储介质进行详细描述。
图2为本公开实施例所提供的一种上报方法的流程示意图，该方法由终端设备执行，如图2a所示，该上报方法可以包括以下步骤：
步骤201、响应于发生MCG RLF后，记录与MCG链路失败相关的信息。
其中，在本公开的一个实施例之中，该记录与MCG链路失败相关的信息具体可以为：记录第一信息，该第一信息可以包括以下至少一种：
T316定时器是否配置；
T316定时器当前是否超时；
SCG传输当前是否被暂停；
SCG当前是否处于激活态；
当前是否正在进行PSCell添加；
当前是否正在进行PSCell改变。
步骤202、向网络设备上报记录的信息。
在本公开的一个实施例之中，终端设备具体是在恢复了MCG链路后，基于网络设备的请求向网络设备上报其记录的信息(即上述的第一信息)。
以及，对本公开中之所以要记录和上报与MCG链路失败相关的信息的原因进行详述：
通过上述背景技术的内容可知，当发生MCG RLF后，若SCG链路正常通信，则会基于快速MCG链路恢复机制来快速恢复MCG链接，而若SCG链路无法正常通信时，就需要触发连接重建流程。其中，上述步骤201中的“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。具体的，当T316定时器未配置、T316定时器超时、SCG传输被暂停、SCG处于非激活态、当前正在进行PSCell添加、或者当前正在进行PSCell改变时，则说明当前无法基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。
其中，上述的“触发连接重建流程”的过程一般耗时较长，从而会导致MCG链接的恢复效率低。基于此，在本公开的一个实施例之中，一旦当终端设备确定其在发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息并上报至网络设备，以便当终端设备当前出现“无法基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路”的情形时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
此外，关于步骤201-202的具体实施方式的详细内容会在后续实施例进行介绍。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图3为本公开实施例所提供的一种上报方法的流程示意图，该方法由终端设备执行，如图3所示，该上报方法可以包括以下步骤：
步骤301、响应于发生MCG RLF后，要触发连接重建流程，记录与MCG链路失败相关的信息。
图3对应的实施例与上述图2对应的实施例的区别为：图2中是当终端设备发生MCG RLF之后，即记录与MCG链路失败相关的信息。而图3的实施例为：当终端设备发生MCG RLF后，且确定要触发连接重建流程时，终端设备才记录MCG链路失败相关的信息。
以及，在本公开的一个实施例之中，关于该与MCG链路失败相关的信息的相关介绍可以参考上述实施例描述。
步骤302、向网络设备上报记录的信息。
其中，在本公开的一个实施例之中，终端设备通过向网络设备上报其记录的与MCG链路失败相关的信息，则网络设备即可基于该与MCG链路失败相关的信息的内容推测出导致终端设备在发生MCG RLF后，需要通过触发连接重建流程来恢复MCG链接的原因(即在发生MCG RLF后无法使用快速MCG链路恢复机制来恢复MCG链接的原因)，以便后续可以基于该原因来对应优化调整终端设备，防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况。
示例的，在本公开的一个实施例之中，若终端设备向网络设备上报的与MCG链路失败相关的信息(即终端设备向网络设备上报的第一信息)为：
T316定时器未配置；
SCG传输当前未被暂停；
SCG当前处于非激活态；
当前未在进行PSCell添加；
当前未在进行PSCell改变。
由此，网络设备基于终端设备上报的信息可以推测出导致终端设备在发生MCG RLF后，需要通过触发连接重建流程来恢复MCG链接的原因为：T316定时器未配置、SCG当前处于非激活态。此时， 网络设备可以对终端设备进行对应的优化调整，该优化调整如可以为：向终端设备配置T316定时器，和/或，控制SCG处于激活态。则后续当终端设备再次发生MCG时，即可直接使用快速MCG链路恢复机制来恢复MCG链接，耗时较短且效率较高。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图4为本公开实施例所提供的一种上报方法的流程示意图，该方法由终端设备执行，如图4所示，该上报方法可以包括以下步骤：
步骤401、记录第二信息，该第二信息为当前的连接重建流程的实际触发原因。
其中，在本公开的一个实施例之中，参考上述内容可知该第二信息实质表示的应当是：导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的实际原因。
该第二信息可以包括以下至少一种：
T316定时器未配置；
T316定时器超时；
SCG传输暂停；
SCG处于非激活态；
正在进行PSCell添加；
正在进行PSCell改变。
进一步地，当当前的连接重建流程的实际触发原因包括多个时，在本公开的一个实施例之中，终端设备可以将全部的实际触发原因都记录为第二信息。在本公开的另一个实施例之中，终端设备可以从实际触发原因中选择小于或等于N个原因记录为第二信息，N为正整数。上述的N可以是终端设备基于协议约定的，和/或，也可以是终端设备基于网络设备的指示确定的，以及，终端设备具体所选择的实际触发原因的数量应当是小于或等于当前的连接重建流程的实际触发原因的总个数的。
需要说明的是，在本公开的一个实施例之中，上述的终端设备选择小于或等于N个原因记录为第二信息具体可以理解为：当当前的连接重建流程的实际触发原因的总个数小于N时，则可以从当前的连接重建流程的实际触发原因中选择小于N个原因记录为第二信息。
示例的，假设N的值为4个，而当前的连接重建流程的实际触发原因为：T316定时器未配置、SCG处于非激活态，则此时，当前的连接重建流程的实际触发原因的总个数为2，小于N的取值4，此时，终端设备无法从当前的连接重建流程的实际触发原因中选择出4个原因作为第二信息，则终端设备可以选择小于4个原因作为第二信息，如，终端设备可以选择将当前的连接重建流程的实际触发原因中的“T316定时器未配置”该一个原因作为第二信息，或者，终端设备可以选择将当前的连接重建流程的实际触发原因中的“T316定时器未配置和SCG处于非激活态”该两个原因作为第二信息。
进一步地，在本公开的一个实施例之中，终端设备在从实际触发原因中选择小于或等于N个原因时，可以是终端设备基于实现自主选择任意选择小于或等于N个原因，和/或，也可以是终端设备基于优先级来优先选择优先级较高的小于或等于N个原因。其中，不同原因对应不同的优先级，该原因与优先级的对应关系可以是协议约定的，也可以是网络设备指示的。示例的，各个原因之间的优先级先后顺序可以为：T316定时器超时>SCG暂停传输>正在进行PSCell添加或改变>SCG处于非激活态。
还需要说明的是，在本公开的一个实施例之中，当当前的连接重建流程的实际触发原因中包括T316定时器超时时，则终端设备还应将T316定时器的定时时长记录为第二信息。
步骤402、向网络设备上报第二信息。
其中，在本公开的一个实施例之中，终端设备通过向网络设备上报第二信息，则网络设备即可基于该第二信息的内容确定出导致终端设备在发生MCG RLF后，需要通过触发连接重建流程来恢复MCG链接的原因(即在发生MCG RLF后无法使用快速MCG链路恢复机制来恢复MCG链接的原因)，以便后续可以基于该原因来对应优化调整终端设备，防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况。
示例的，在本公开的一个实施例之中，若终端设备向网络设备上报的第二信息为：
T316定时器超时，且该T316定时器的定时时长为40毫秒(ms)。
由此，网络设备即可基于终端设备上报的第二信息推测出导致终端设备在发生MCG RLF后，需要通过触发连接重建流程来恢复MCG链接的原因为：T316定时器由于定时时长较短导致定时器超时。此时，网络设备可以对终端设备进行对应的优化调整，该优化调整如可以为：为T316定时器配置一新的定时时长，该新的定时时长大于T316定时器的原定时时长，且该新的定时时长应当能够支持完成快速MCG链路恢复机制，以此确保后续终端设备再发生MCG RLF后，可以成功基于快速MCG链路恢复机制来恢复MCG链接。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图5为本公开实施例所提供的一种上报方法的流程示意图，该方法由终端设备执行，如图5所示，该上报方法可以包括以下步骤：
步骤501、响应于发生MCG RLF后，要触发连接重建流程，且当前的连接重建流程的实际触发原因包括特定原因，记录第三信息，该第三信息包括当前的连接重建流程对应的特定原因。
其中，在本公开的一个实施例之中，该特定原因可以是终端设备基于协议约定确定的，和/或，也可以是终端设备基于网络设备的指示确定的。
以及，在本公开的一个实施例之中，该特定原因具体可以是在发生MCG RLF后，导致需要通过触发连接重建流程才能恢复MCG链路的所有可能原因中的任一个或任多个。示例的，该特定原因例如可以包括：T316定时器超时、SCG传输暂停、正在进行PSCell添加、正在进行PSCell改变中的至少一种。
以及，在本公开的一个实施例之中，只有当当前的连接重建流程的实际触发原因中包括有特定原因时，才仅对该特定原因进行记录。示例的，假设特定原因包括T316定时器超时、SCG传输暂停、正在进行PSCell添加、正在进行PSCell改变；以及，当前的连接重建流程的实际触发原因为：T316定时器未配置、SCG传输暂停。此时，则仅将“SCG传输暂停”记录为第三信息。
进一步地，当当前的连接重建流程对应的特定原因包括多个时，在本公开的一个实施例之中，终端设备可以将当前的连接重建流程对应的全部特定原因为第三信息。在本公开的另一个实施例之中，终端设备可以从当前的连接重建流程对应的特定原因中选择小于或等于N个原因记录为第三信息，N为正整数。其中，上述的N可以是终端设备基于协议约定的，和/或，也可以是终端设备基于网络设备的指 示确定的。其中，关于与该部分内容相关的具体详细介绍可以参考上述实施例描述。
还需要说明的是，在本公开的一个实施例之中，当当前的连接重建流程对应的特定原因中包括T316定时器超时时，则终端设备还应将T316定时器的定时时长记录为第三信息。
步骤502、向网络设备上报第三信息。
其中，关于步骤502的相关介绍可以参考上述实施例描述。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图6为本公开实施例所提供的一种上报方法的流程示意图，该方法由终端设备执行，如图6所示，该上报方法可以包括以下步骤：
步骤601、响应于发生MCG RLF后，要触发连接重建流程，且当前的连接重建流程的实际触发原因不包括特定原因，不记录信息。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图7为本公开实施例所提供的一种上报方法的流程示意图，该方法由终端设备执行，如图7所示，该上报方法可以包括以下步骤：
步骤701、响应于发生MCG RLF后，记录与MCG链路失败相关的信息。
步骤702、将与MCG链路失败相关的信息记录至RLF报告(Report)(如VarRLF-Report)中。
步骤703、向网络设备上报RLF Report。
其中，在本公开的一个实施例之中，具体是终端设备基于连接重建流程恢复了MCG链路后，会基于网络设备的请求向网路设备上报RLF Report。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后 续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图8为本公开实施例所提供的一种上报方法的流程示意图，该方法由终端设备执行，如图8所示，该上报方法可以包括以下步骤：
步骤801、向所述网络设备发送能力信息，所述能力信息用于指示所述终端设备是否支持记录和上报所述与MCG链路失败相关的信息。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图9为本公开实施例所提供的一种上报方法的流程示意图，该方法由网络设备执行，如图9所示，该上报方法可以包括以下步骤：
步骤901、接收终端设备上报的信息，所述信息为所述终端设备在发生MCG RLF后记录的与MCG链路失败相关的信息。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图10为本公开实施例所提供的一种上报方法的流程示意图，该方法由网络设备执行，如图10所示，该上报方法可以包括以下步骤：
步骤1001、接收终端设备上报的信息，所述信息为所述终端设备在发生MCG RLF后且确定要触发连接重建流程来恢复MCG链路时记录的与MCG链路失败相关的信息。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后 续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图11为本公开实施例所提供的一种上报方法的流程示意图，该方法由网络设备执行，如图11所示，该上报方法可以包括以下步骤：
步骤1101、接收终端设备上报的第二信息，所述第二信息为当前的连接重建流程的实际触发原因。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图12为本公开实施例所提供的一种上报方法的流程示意图，该方法由网络设备执行，如图12所示，该上报方法可以包括以下步骤：
步骤1201、接收终端设备上报的第三信息，所述第三信息包括当前的连接重建流程的实际触发原因中所包括的特定原因。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图13为本公开实施例所提供的一种上报方法的流程示意图，该方法由网络设备执行，如图13所示，该上报方法可以包括以下步骤：
步骤1301、向所述终端设备发送请求消息，所述请求消息用于请求所述终端设备上报所述信息。
步骤1302、接收所述终端设备通过RLF Report上报的所述信息。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的 情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图14为本公开实施例所提供的一种上报方法的流程示意图，该方法由网络设备执行，如图14所示，该上报方法可以包括以下步骤：
步骤1401、接收所述终端设备发送的能力信息，所述能力信息用于指示所述终端设备是否支持记录和上报所述与MCG链路失败相关的信息。
综上所述，本公开实施例提供的方法之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
图15为本公开实施例所提供的一种通信装置的结构示意图，如图14所示，装置可以包括：
处理模块，用于响应于发生主小区组无线链路失败MCG RLF后，记录与MCG链路失败相关的信息；
收发模块，用于向网络设备上报记录的所述信息。
综上所述，在本公开实施例提供的通信装置之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
可选的，在本公开的一个实施例之中，所述处理模块还用于：
响应于确定要触发连接重建流程来恢复MCG链路，记录与MCG链路失败相关的信息。
可选的，在本公开的一个实施例之中，所述处理模块还用于：
记录第一信息，所述第一信息包括以下至少一种：
T316定时器是否配置；
T316定时器是否超时；
辅小区组SCG传输是否被暂停；
SCG是否处于激活态；
是否正在进行主辅小区PSCell添加；
是否正在进行PSCell改变。
可选的，在本公开的一个实施例之中，所述处理模块还用于：
记录第二信息，所述第二信息为当前的连接重建流程的实际触发原因；
所述实际触发原因包括以下至少一种：
T316定时器未配置；
T316定时器超时；
SCG传输暂停；
SCG处于非激活态；
正在进行PSCell添加；
正在进行PSCell改变。
可选的，在本公开的一个实施例之中，所述处理模块还用于：
记录第三信息，所述第三信息包括所述当前的连接重建流程对应的特定原因；
所述特定原因与所述实际触发原因至少部分相同。
可选的，在本公开的一个实施例之中，所述装置还用于：
响应于当前的连接重建流程的实际触发原因不包括特定原因，不记录信息。
可选的，在本公开的一个实施例之中，所述装置还用于以下至少一种：
基于协议确定所述特定原因；
基于网络设备的指示确定所述特定原因。
可选的，在本公开的一个实施例之中，所述处理模块还用于：
将全部的所述实际触发原因记录为所述第二信息；或者，从所述实际触发原因中选择小于或等于N个原因记录为第二信息，N为正整数，以及，所选择的实际触发原因的数量小于或等于当前的连接重建流程的实际触发原因的总个数；
响应于所述当前的连接重建流程对应的特定原因包括多个，所述记录第三信息，包括：
将当前的连接重建流程对应的全部特定原因记录为所述第三信息；或者，从所述当前的连接重建流程对应的特定原因中选择小于或等于N个原因记录为第三信息，N为正整数，以及，所选择的特定原因的数量小于或等于当前的连接重建流程对应的特定原因的总个数。
可选的，在本公开的一个实施例之中，所述处理模块还用于：
所述终端设备自主选择小于或等于N个原因；和/或
基于优先级选择小于或等于N个原因，其中，不同原因对应不同优先级。
可选的，在本公开的一个实施例之中，所述装置还用于：
基于协议约定确定所述N；和/或
基于网络设备的指示确定所述N。
可选的，在本公开的一个实施例之中，所述处理模块还用于：
将所述T316定时器的定时时长记录为所述第二信息；
所述处理模块还用于：
将所述T316定时器的定时时长记录为所述第三信息。
可选的，在本公开的一个实施例之中，所述处理模块还用于：
将与MCG链路失败相关的信息记录至RLF报告(Report)中。
可选的，在本公开的一个实施例之中，所述收发模块还用于：
基于网络设备的请求向所述网络设备上报所述RLF Report。
可选的，在本公开的一个实施例之中，所述装置还用于：
向所述网络设备发送能力信息，所述能力信息用于指示所述终端设备是否支持记录和上报所述与MCG链路失败相关的信息。
图16为本公开实施例所提供的一种通信装置的结构示意图，如图16所示，装置可以包括：
收发模块，用于接收终端设备上报的信息，所述信息为所述终端设备在发生MCG RLF后记录的与MCG链路失败相关的信息。
综上所述，在本公开实施例提供的通信装置之中，响应于终端设备发生MCG RLF后，该终端设备会记录与MCG链路失败相关的信息；并会向网络设备上报记录的信息。其中，该“与MCG链路失败 相关的信息”可以体现出当前是否是不能基于快速MCG链路恢复机制来快速恢复MCG链接，而是需要触发连接重建流程来恢复MCG链路。由此，通过使得终端设备记录与MCG链路失败相关的信息且向网络设备上报该与MCG链路失败相关的信息，以便当终端设备当前需要通过触发连接重建流程来恢复MCG链路时，网络设备侧可以基于终端上报的与MCG链路失败相关的信息确定出“导致当前无法使用快速MCG链路恢复机制来快速恢复MCG链接的原因”，进而对终端设备进行相应的优化调整，以防止后续再出现“由于相同的原因导致终端设备无法使用快速MCG链路恢复机制来快速恢复MCG链接”的情况；则当终端设备下次再发生MCG RLF时，就不用再通过触发连接重建流程来恢复MCG链接，而是可以直接使用快速MCG链路恢复机制来快速恢复MCG链接，从而使得MCG链接恢复所需耗时较短，且效率较高。
可选的，在本公开的一个实施例之中，所述信息为所述终端设备在发生MCG RLF后且确定要触发连接重建流程来恢复MCG链路时记录的与MCG链路失败相关的信息。
可选的，在本公开的一个实施例之中，所述收发模块还用于：
接收终端设备上报的第一信息，所述第一信息包括以下至少一种：
T316定时器是否配置；
T316定时器是否超时；
SCG传输是否被暂停；
SCG是否处于激活态；
是否正在进行PSCell添加；
是否正在进行PSCell改变。
可选的，在本公开的一个实施例之中，所述收发模块还用于：
接收终端设备上报的第二信息，所述第二信息为当前的连接重建流程的实际触发原因；
所述实际触发原因包括以下至少一种：
T316定时器未配置；
T316定时器超时；
SCG传输暂停；
SCG处于非激活态；
正在进行PSCell添加；
正在进行PSCell改变。
可选的，在本公开的一个实施例之中，所述收发模块还用于：
接收终端设备上报的第三信息，所述第三信息包括当前的连接重建流程的实际触发原因中所包括的特定原因；
其中，所述特定原因与所述实际触发原因至少部分相同。
可选的，在本公开的一个实施例之中，所述装置还用于：
向所述终端设备指示所述特定原因。
可选的，在本公开的一个实施例之中，所述装置还用于：
向所述终端设备指示N的取值，N为正整数，N为所述第二信息或第三信息中可包括的原因的最大个数。
可选的，在本公开的一个实施例之中，响应于所述当前的连接重建流程的实际触发原因包括T316定时器超时，所述第二信息中还包括所述T316定时器的定时时长；
响应于所述当前的连接重建流程对应的特定原因包括T316定时器超时，所述第三信息中还包括所述T316定时器的定时时长。
可选的，在本公开的一个实施例之中，所述收发模块还用于：
接收所述终端设备通过RLF Report上报的所述信息。
可选的，在本公开的一个实施例之中，所述装置还用于：
向所述终端设备发送请求消息，所述请求消息用于请求所述终端设备上报所述信息。
可选的，在本公开的一个实施例之中，所述装置还用于：
接收所述终端设备发送的能力信息，所述能力信息用于指示所述终端设备是否支持记录和上报所述与MCG链路失败相关的信息。
请参见图17，图17是本申请实施例提供的一种通信装置1700的结构示意图。通信装置1700可以是网络设备，也可以是终端设备，也可以是支持网络设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1700可以包括一个或多个处理器1701。处理器1701可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1700中还可以包括一个或多个存储器1702，其上可以存有计算机程序1704，处理器1701执行所述计算机程序1704，以使得通信装置1700执行上述方法实施例中描述的方法。可选的，所述存储器1702中还可以存储有数据。通信装置1700和存储器1702可以单独设置，也可以集成在一起。
可选的，通信装置1700还可以包括收发器1705、天线1706。收发器1705可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1705可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1700中还可以包括一个或多个接口电路1707。接口电路1707用于接收代码指令并传输至处理器1701。处理器1701运行所述代码指令以使通信装置1700执行上述方法实施例中描述的方法。
在一种实现方式中，处理器1701中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1701可以存有计算机程序1703，计算机程序1703在处理器1701上运行，可使得通信装置1700执行上述方法实施例中描述的方法。计算机程序1703可能固化在处理器1701中，该种情况下，处理器1701可能由硬件实现。
在一种实现方式中，通信装置1700可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是网络设备或者终端设备，但本申请中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图17的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、 网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图18所示的芯片的结构示意图。图18所示的芯片包括处理器1801和接口1802。其中，处理器1801的数量可以是一个或多个，接口1802的数量可以是多个。
可选的，芯片还包括存储器1803，存储器1803用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本申请实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本申请实施例保护的范围。
本申请还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本申请还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。
本申请中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本申请不做限制。在本申请实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本申请中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本申请并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本申请中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种上报方法，其特征在于，所述方法被终端设备执行，所述方法包括：
    响应于发生主小区组无线链路失败MCG RLF后，记录与MCG链路失败相关的信息；
    向网络设备上报记录的所述信息。
  2. 如权利要求1所述的方法，其特征在于，所述记录与MCG链路失败相关的信息，包括：
    响应于确定要触发连接重建流程来恢复MCG链路，记录与MCG链路失败相关的信息。
  3. 如权利要求1或2所述的方法，其特征在于，所述记录与MCG链路失败相关的信息，包括：
    记录第一信息，所述第一信息包括以下至少一种：
    T316定时器是否配置；
    T316定时器是否超时；
    辅小区组SCG传输是否被暂停；
    SCG是否处于激活态；
    是否正在进行主辅小区PSCell添加；
    是否正在进行PSCell改变。
  4. 如权利要求2所述的方法，其特征在于，所述记录与MCG链路失败相关的信息，包括：
    记录第二信息，所述第二信息为当前的连接重建流程的实际触发原因；
    所述实际触发原因包括以下至少一种：
    T316定时器未配置；
    T316定时器超时；
    SCG传输暂停；
    SCG处于非激活态；
    正在进行PSCell添加；
    正在进行PSCell改变。
  5. 如权利要求4所述的方法，其特征在于，所述记录与MCG链路失败相关的信息，包括：
    记录第三信息，所述第三信息包括所述当前的连接重建流程对应的特定原因；
    其中，所述特定原因与所述实际触发原因至少部分相同。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    响应于当前的连接重建流程的实际触发原因不包括特定原因，不记录信息。
  7. 如权利要求5所述的方法，其特征在于，所述方法还包括以下至少一种：
    基于协议确定所述特定原因；
    基于网络设备的指示确定所述特定原因。
  8. 如权利要求4或5所述的方法，其特征在于，响应于所述当前的连接重建流程的实际触发原因包括多个，所述记录第二信息，包括：
    将全部的所述实际触发原因记录为所述第二信息；或者，从所述实际触发原因中选择小于或等于N个原因记录为第二信息，N为正整数，以及，所选择的实际触发原因的数量小于或等于当前的连接重建流程的实际触发原因的总个数；
    响应于所述当前的连接重建流程对应的特定原因包括多个，所述记录第三信息，包括：
    将当前的连接重建流程对应的全部特定原因记录为所述第三信息；或者，从所述当前的连接重建流程对应的特定原因中选择小于或等于N个原因记录为第三信息，N为正整数，以及，所选择的特定原因的数量小于或等于当前的连接重建流程对应的特定原因的总个数。
  9. 如权利要求8所述的方法，其特征在于，所述选择小于或等于N个原因，包括：
    所述终端设备自主选择小于或等于N个原因；
    基于优先级选择小于或等于N个原因，其中，不同原因对应不同优先级。
  10. 如权利要求8所述的方法，其特征在于，所述方法还包括以下至少一种：
    基于协议约定确定所述N；
    基于网络设备的指示确定所述N。
  11. 如权利要求4或5所述的方法，其特征在于，响应于所述当前的连接重建流程的实际触发原因包括T316定时器超时，所述方法还包括：
    将所述T316定时器的定时时长记录为所述第二信息；
    响应于所述当前的连接重建流程对应的特定原因包括T316定时器超时，所述方法还包括：
    将所述T316定时器的定时时长记录为所述第三信息。
  12. 如权利要求1-11任一所述的方法，其特征在于，所述记录与MCG链路失败相关的信息，包括：
    将与MCG链路失败相关的信息记录至RLF报告(Report)中。
  13. 如权利要求12任一所述的方法，其特征在于，所述向网络设备上报记录的所述信息，包括：
    基于网络设备的请求向所述网络设备上报所述RLF Report。
  14. 如权利要求1-11任一所述的方法，其特征在于，所述方法还包括：
    向所述网络设备发送能力信息，所述能力信息用于指示所述终端设备是否支持记录和上报所述与MCG链路失败相关的信息。
  15. 一种上报方法，其特征在于，所述方法被网络设备执行，所述方法包括：
    接收终端设备上报的信息，所述信息为所述终端设备在发生MCG RLF后记录的与MCG链路失败相关的信息。
  16. 如权利要求15所述的方法，其特征在于，所述信息为所述终端设备在发生MCG RLF后且确定要触发连接重建流程来恢复MCG链路时，记录的与MCG链路失败相关的信息。
  17. 如权利要求15或16所述的方法，其特征在于，所述接收终端设备上报的信息，包括：
    接收终端设备上报的第一信息，所述第一信息包括以下至少一种：
    T316定时器是否配置；
    T316定时器是否超时；
    SCG传输是否被暂停；
    SCG是否处于激活态；
    是否正在进行PSCell添加；
    是否正在进行PSCell改变。
  18. 如权利要求15所述的方法，其特征在于，所述接收终端设备上报的信息，包括：
    接收终端设备上报的第二信息，所述第二信息为当前的连接重建流程的实际触发原因；
    所述实际触发原因包括以下至少一种：
    T316定时器未配置；
    T316定时器超时；
    SCG传输暂停；
    SCG处于非激活态；
    正在进行PSCell添加；
    正在进行PSCell改变。
  19. 如权利要求18所述的方法，其特征在于，所述接收终端设备上报的信息，包括：
    接收终端设备上报的第三信息，所述第三信息包括当前的连接重建流程的实际触发原因中所包括的特定原因；
    所述特定原因与所述实际触发原因至少部分相同。
  20. 如权利要求19所述的方法，其特征在于，所述方法还包括：
    向所述终端设备指示所述特定原因。
  21. 如权利要求18或19所述的方法，其特征在于，所述方法还包括：
    向所述终端设备指示N的取值，N为正整数，N为所述第二信息或第三信息中可包括的原因的最大个数。
  22. 如权利要求18或19所述的方法，其特征在于，响应于所述当前的连接重建流程的实际触发原因包括T316定时器超时，所述第二信息中还包括所述T316定时器的定时时长；
    响应于所述当前的连接重建流程对应的特定原因包括T316定时器超时，所述第三信息中还包括所述T316定时器的定时时长。
  23. 如权利要求15-22任一所述的方法，其特征在于，所述接收终端设备上报的信息，包括：
    接收所述终端设备通过RLF Report上报的所述信息。
  24. 如权利要求23所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送请求消息，所述请求消息用于请求所述终端设备上报所述信息。
  25. 如权利要求15-22任一所述的方法，其特征在于，所述方法还包括：
    接收所述终端设备发送的能力信息，所述能力信息用于指示所述终端设备是否支持记录和上报所述与MCG链路失败相关的信息。
  26. 一种通信装置，其特征在于，所述装置被配置于终端设备中，包括：
    处理模块，用于响应于发生主小区组无线链路失败MCG RLF后，记录与MCG链路失败相关的信息；
    收发模块，用于向网络设备上报记录的所述信息。
  27. 一种通信装置，其特征在于，所述装置被配置于网络设备中，包括：
    收发模块，用于接收终端设备上报的信息，所述信息为所述终端设备在发生MCG RLF后记录的与MCG链路失败相关的信息。
  28. 一种通信装置，其特征在于，所述装置包括处理器和存储器，其中，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至14中任一项所述的方法，或所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求15至25所述的方法。
  29. 一种通信装置，其特征在于，包括：处理器和接口电路，其中
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求1至14中任一项所述的方法，或用于运行所述代码指令以执行如权利要求15至25所述的方法。
  30. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至14中任一项所述的方法被实现，或当所述指令被执行时，使如权利要求15至25所述的方法被实现。
PCT/CN2022/110948 2022-08-08 2022-08-08 一种上报方法、装置、设备及存储介质 WO2024031272A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280002779.3A CN115516916A (zh) 2022-08-08 2022-08-08 一种上报方法、装置、设备及存储介质
PCT/CN2022/110948 WO2024031272A1 (zh) 2022-08-08 2022-08-08 一种上报方法、装置、设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110948 WO2024031272A1 (zh) 2022-08-08 2022-08-08 一种上报方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024031272A1 true WO2024031272A1 (zh) 2024-02-15

Family

ID=84513839

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110948 WO2024031272A1 (zh) 2022-08-08 2022-08-08 一种上报方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN115516916A (zh)
WO (1) WO2024031272A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118338348A (zh) * 2023-01-12 2024-07-12 夏普株式会社 无线链路失败报告方法以及用户设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071597A (zh) * 2020-07-31 2022-02-18 大唐移动通信设备有限公司 一种信息处理方法、装置、设备及可读存储介质
WO2022075626A1 (ko) * 2020-10-08 2022-04-14 삼성전자 주식회사 무선 통신에서의 링크 관리 방법 및 장치

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831254B (zh) * 2018-08-08 2021-11-16 维沃移动通信有限公司 连接失败恢复的方法和设备
CN110839301B (zh) * 2018-08-16 2021-09-10 维沃移动通信有限公司 一种无线链路失败的信息处理方法、终端及网络设备
DE102020201797A1 (de) * 2019-02-13 2020-08-13 Apple Inc. Wiederherstellung nach master-zellgruppen-fehler für drahtlose vorrichtungen mit dual-konnektivität
CN113453273A (zh) * 2020-03-26 2021-09-28 夏普株式会社 无线链路失败报告方法以及用户设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071597A (zh) * 2020-07-31 2022-02-18 大唐移动通信设备有限公司 一种信息处理方法、装置、设备及可读存储介质
WO2022075626A1 (ko) * 2020-10-08 2022-04-14 삼성전자 주식회사 무선 통신에서의 링크 관리 방법 및 장치

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 36.331, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V16.6.0, 29 September 2021 (2021-09-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 1091, XP052056891 *

Also Published As

Publication number Publication date
CN115516916A (zh) 2022-12-23

Similar Documents

Publication Publication Date Title
WO2024026800A1 (zh) 一种侧行链路sl波束失败恢复方法/装置/设备及存储介质
WO2024031373A1 (zh) 一种确定触发连续lbt失败的方法及装置
WO2024031274A1 (zh) 成功切换报告shr的记录上报方法和装置
WO2024031275A1 (zh) 无线接入技术rat中成功切换报告shr的记录上报方法和装置
CN114342483B (zh) 接入控制方法及装置
WO2024026801A1 (zh) 一种侧行链路sl波束配置方法、装置、设备及存储介质
WO2023225830A1 (zh) 中继连接方法及装置
WO2024031272A1 (zh) 一种上报方法、装置、设备及存储介质
WO2024060234A1 (zh) 信息上报方法和装置
WO2024060143A1 (zh) 一种上报方法/装置/设备及存储介质
WO2024060233A1 (zh) 信息上报方法和装置
WO2024036519A1 (zh) 一种侧行链路pdcp复用的激活方法及装置
WO2024197487A1 (zh) 一种连续先听后说lbt失败的处理方法及其装置
WO2023201756A1 (zh) 一种用于基于条件的移动性的信息的处理方法及装置
WO2023206034A1 (zh) 混合自动重传请求harq反馈的处理方法及其装置
WO2024031381A1 (zh) Sps pdsch的发送接收方法及其装置
WO2024060154A1 (zh) 一种上报方法/装置/设备及存储介质
WO2024092661A1 (zh) 模型的标识方法及装置
WO2024045042A1 (zh) 一种能力交互触发方法/装置/设备及存储介质
US20240114483A1 (en) Paging processing method, communication apparatus, and storage medium
WO2024159543A1 (zh) 一种传输实体的控制方法及其装置
WO2024168479A1 (zh) 混合自动重传请求harq进程使能配置方法及装置
WO2024000207A1 (zh) 一种定时提前报告tar的触发方法、装置、设备及存储介质
WO2023201755A1 (zh) 一种移动性管理的配置方法及装置
WO2023240419A1 (zh) 一种接入控制的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22954252

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE