WO2023011077A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2023011077A1
WO2023011077A1 PCT/CN2022/103435 CN2022103435W WO2023011077A1 WO 2023011077 A1 WO2023011077 A1 WO 2023011077A1 CN 2022103435 W CN2022103435 W CN 2022103435W WO 2023011077 A1 WO2023011077 A1 WO 2023011077A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
terminal device
report
shr
information
Prior art date
Application number
PCT/CN2022/103435
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
Priority claimed from CN202111676240.XA external-priority patent/CN115915202A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023011077A1 publication Critical patent/WO2023011077A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present application relates to the technical field of communication, and in particular to a communication method and device.
  • DAPS dual active protocol stack
  • the terminal device may experience user plane transmission interruption, such as a radio link failure (RLF) between the terminal device and the source network device during the DAPS handover process.
  • RLF radio link failure
  • the terminal device does not record the mobility parameters during the transmission interruption of the user plane, so that the network side cannot optimally handle the transmission interruption of the user plane.
  • the present application provides a communication method and device, which can record the duration of user plane transmission interruption during potential mobility failure, and lay a foundation for the network side to optimally handle the problem of user plane transmission interruption.
  • the embodiment of the present application provides a communication method, and the execution subject of the method may be a terminal device, or may be a chip applied in the terminal device.
  • the following description is made by taking the execution subject as a terminal device as an example.
  • the method includes: the terminal device receives indication information from the first network device. Wherein, the indication information indicates the first threshold. When the user plane transmission interruption duration during the handover process is greater than or equal to the first threshold, the terminal device records the first report. Wherein, the first report indicates the duration of user plane transmission interruption.
  • the indication information indicates the first threshold.
  • the terminal device records the first report when the user plane transmission interruption duration is greater than or equal to the first threshold.
  • the first report includes the user plane transmission interruption duration. Even if the terminal device successfully connects to the second network device, but the terminal device has a phenomenon of user plane transmission interruption during the handover process, the first report can also record the length of the user plane transmission interruption, preventing the terminal device from being unable to record the user plane transmission interruption in the prior art
  • the problem of mobility parameters also lays a foundation for the network side to determine the optimization parameters.
  • the user plane transmission interruption duration is the time interval from the user plane transmission interruption start identifier to the end identifier.
  • the start identifier of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the last data packet to the first network device.
  • the end device successfully received the last data packet from the first network device.
  • the termination flag of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the first data packet to the second network device.
  • the terminal device successfully receives the first data packet from the second network device.
  • the first network device is a network device that the terminal device accesses before the handover process
  • the second network device is a network device that the terminal device accesses after the handover process.
  • the user plane transmission interruption refers to the situation before the connection between the terminal device and the first network device is interrupted and the connection between the terminal device and the second network device fails.
  • the indication information also indicates a start identifier and/or an end identifier of the user plane transmission interruption, so as to instruct the terminal device to use the indicated identifier to determine the duration of the user plane transmission interruption.
  • the terminal device when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process, the terminal device records the first report, including: when the running duration of the first timer is greater than or equal to the first threshold case, the end device records the first report.
  • the running duration of the first timer indicates the user plane transmission interruption duration. That is to say, the start identifier of the first timer is the same as the start identifier of the user plane transmission interruption duration.
  • the terminal device uses the first timer to monitor the user plane transmission interruption duration.
  • the communication method in this embodiment of the present application further includes: the terminal device sends the first report to the first network device.
  • the first network device is a network device that the terminal device accesses before the handover process.
  • the first network device can optimally handle the problem of user plane transmission interruption based on the first report.
  • the first report also indicates at least one of the following:
  • the first item the reason that triggered the logging of the first report.
  • the second item is the start identifier of the user plane transmission interruption.
  • the third item is the stop flag of user plane transmission interruption.
  • the fourth item is the radio network temporary identifier CRNTI of the source cell.
  • the start identifier of user plane transmission interruption includes one of the following:
  • downlink out-of-synchronization occurs between the terminal device and the first network device.
  • the second item is that a radio link failure RLF occurs between the terminal device and the first network device.
  • the third item, the second timer starts.
  • the running duration of the second timer indicates the duration during which the terminal device detects that there is a physical layer problem with the first network device.
  • the fourth item, the third timer starts.
  • the running duration of the third timer indicates the duration between when the terminal device triggers the measurement report and when the terminal device and the first network device resume synchronization during the running of the second timer.
  • the terminal device successfully receives the duplicate data packet.
  • the termination flag of user plane transmission interruption includes one of the following:
  • the random access process between the terminal device and the second network device is completed.
  • the second item is that the terminal device sends a radio resource control RRC reconfiguration complete message to complete.
  • the third item is downlink synchronization between the terminal device and the second network device.
  • the fourth item, the second timer stops.
  • the fifth item, the third timer stops.
  • the first report also indicates at least one of the following:
  • the first item the number of repeatedly received data packets, is used to represent the degree of unreasonable data scheduling of the first network device.
  • the second item is the ratio of repeatedly received data packets, which represents the degree of unreasonable data scheduling of the first network device.
  • receiving the indication information by the terminal device includes: receiving an RRC reconfiguration message by the terminal device.
  • the RRC reconfiguration message includes indication information. That is to say, the terminal equipment receives the indication information by receiving the RRC reconfiguration message.
  • the terminal device receiving the indication information includes: the terminal device receiving the indication information before receiving the RRC reconfiguration message.
  • the indication information is carried in one of the following: an RRC establishment message, an RRC re-establishment message, an RRC recovery message, or a system message. That is to say, the indication information may be carried in different messages for transmission.
  • the embodiment of the present application provides a communication method, and the execution subject of the method may be the first network device, or may be a chip applied in the first network device.
  • the description below takes the execution subject as an example of the first network device.
  • the method includes: the first network device acquires indication information. Wherein, the indication information indicates the first threshold.
  • the first network device sends indication information to the terminal device. Wherein, the indication information is used for the terminal device to record the first report when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process, and the first report indicates the user plane transmission interruption duration.
  • the indication information indicates the first threshold.
  • the first network device sends indication information to the terminal device, so that the terminal device records the first report when the user plane transmission interruption duration is greater than or equal to the first threshold.
  • the first report includes the user plane transmission interruption duration.
  • the user plane transmission interruption duration is the time interval from the user plane transmission interruption start identifier to the end identifier.
  • the start identifier of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the last data packet to the first network device.
  • the end device successfully received the last data packet from the first network device.
  • the termination flag of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the first data packet to the second network device.
  • the terminal device successfully receives the first data packet from the second network device.
  • the first network device is a network device that the terminal device accesses before the handover process
  • the second network device is a network device that the terminal device accesses after the handover process.
  • the indication information also indicates a start identifier and/or a termination identifier of user plane transmission interruption.
  • the communication method in this embodiment of the present application further includes: the first network device receives the first report from the terminal device.
  • the first network device is a network device that the terminal device accesses before the handover process.
  • the acquiring the indication information by the first network device includes: determining the indication information by the first network device. That is to say, the indication information may be configured by the first network device.
  • the first network device acquiring the indication information includes: the first network device receiving the indication information from the second network device. That is to say, the indication information may be configured by the second network device.
  • the communication method in this embodiment of the present application further includes: the first network device sending reference information to the second network device.
  • the reference information is used to determine the indication information. That is to say, the first network device can provide the second network device with reference information, so that the second network device determines indication information based on the reference information.
  • the communication method in this embodiment of the present application further includes: the first network device receives first information from the second network device.
  • the first information indicates that the second network device supports the successful handover reporting SHR function.
  • the first network device sending the reference information to the second network device includes: the first network device sending the reference information to the second network device according to the first information, so as to avoid waste of transmission resources caused by transmission of the reference information.
  • the communication method in this embodiment of the present application further includes: the first network device sending the second information to the second network device.
  • the second information is used to request the second network device to feed back whether the SHR function is supported, so that the second network device feeds back the first information.
  • the first report also indicates at least one of the following:
  • the first item the reason that triggered the logging of the first report.
  • the second item is the start identifier of the user plane transmission interruption.
  • the third item is the stop flag of user plane transmission interruption.
  • the fourth item is the radio network temporary identifier CRNTI of the source cell.
  • the first network device receiving the indication information from the second network device includes: the first network device receiving a HO request confirmation message from the second network device, where the HO request confirmation message includes a radio resource control An RRC reconfiguration message, the indication information is carried in the RRC reconfiguration message.
  • the indication information is transmitted from the second network device to the first network device through the RRC reconfiguration message.
  • the first network device receiving the indication information from the second network device includes: the first network device receiving the HO request confirmation message from the second network device, wherein the HO request confirmation message includes RRC reconfiguration message, the indication information is carried outside the RRC reconfiguration message and in the HO request confirmation message.
  • the indication information is transmitted from the second network device to the first network device through the HO request confirmation message.
  • the first network device receiving the indication information from the second network device includes: before the first network device receives the HO request confirmation message, receiving the indication information from the second network device, so that the first network The device gets the indication information earlier.
  • the first network device sending indication information to the terminal device includes: the first network device sending an RRC reconfiguration message to the terminal device.
  • the first network device sending the indication information to the terminal device includes: before the first network device sends the RRC reconfiguration message, sending the indication information to the terminal device.
  • the indication information is carried in one of the following: an RRC establishment message, an RRC re-establishment message, an RRC recovery message, or a system message.
  • the embodiment of the present application provides a communication method, and the execution body of the method may be the second network device, or may be a chip applied in the second network device.
  • the following description is made by taking the execution subject as an example of the second network device.
  • the method includes: the second network device determines indication information. Wherein, the indication information indicates the first threshold.
  • the second network device sends indication information to the first network device.
  • the first network device is a network device that the terminal device accesses before the handover process
  • the second network device is a network device that the terminal device accesses after the handover process.
  • the first threshold is used for the terminal device to record a first report when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process, and the first report indicates the user plane transmission interruption duration.
  • the indication information indicates the first threshold, and is configured by the second network device.
  • the second network device sends indication information to the terminal device through the first network device, so that the terminal device records the first report when the user plane transmission interruption time is greater than or equal to the first threshold.
  • the first report includes the user plane transmission interruption duration.
  • the user plane transmission interruption duration is the time interval from the user plane transmission interruption start identifier to the end identifier.
  • the user plane transmission interruption duration is the time interval from the user plane transmission interruption start identifier to the end identifier.
  • the start identifier of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the last data packet to the first network device.
  • the end device successfully received the last data packet from the first network device.
  • the termination flag of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the first data packet to the second network device.
  • the terminal device successfully receives the first data packet from the second network device.
  • the first network device is a network device that the terminal device accesses before the handover process
  • the second network device is a network device that the terminal device accesses after the handover process.
  • the indication information also indicates a start identifier and/or a termination identifier of user plane transmission interruption.
  • the communication method in this embodiment of the present application further includes: the second network device receives reference information from the first network device.
  • the reference information is used to determine the indication information, so that the second network device determines the indication information based on the reference information.
  • the communication method in this embodiment of the present application further includes: the second network device sending the first information to the first network device.
  • the first information indicates that the second network device supports the successful handover reporting SHR function.
  • the second network device can proactively inform the first network device of its support status for the SHR function.
  • the communication method in this embodiment of the present application further includes: the second network device receiving second information from the first network device.
  • the second information is used to request the second network device to feed back whether to support the SHR function.
  • Sending the first information to the first network device by the second network device includes: sending the first information to the first network device by the second network device according to the second information.
  • the second network device sending the indication information to the first network device includes: before the second network device sends the HO request confirmation message, sending the indication information to the first network device.
  • the embodiment of the present application provides a communication method, and the execution subject of the method may be a terminal device, or may be a chip applied in the terminal device.
  • the following description is made by taking the execution subject as a terminal device as an example.
  • the method includes: when the terminal device detects a radio link failure RLF with the source cell during the DAPS handover process of the dual activation protocol stack, and completes the DAPS handover with the target cell, the terminal device determines the first Report.
  • the first report includes a report to be recorded indicated by a preset condition, or the first report includes a report to be reported indicated by a preset condition, and the preset condition includes at least one of the following: the first item, only record the successful handover report SHR , the second item, only record the RLF report, the third item, only report the SHR, and the fourth item, only report the RLF report.
  • the preset condition indicates a report to be recorded by the terminal device, or a report to be reported by the terminal device.
  • the terminal device determines the first report that meets the preset condition.
  • the terminal device only records one of the RLF report and the SHR report, or the terminal device only reports one of the RLF report and the SHR report.
  • the network side A report (such as the above SHR, or RLF report) can be obtained, thereby avoiding the problem of over-adjustment.
  • the communication method in this embodiment of the present application further includes: the terminal device receives a preset condition from the first network device.
  • the first network device is a network device that the terminal device accesses before the handover process.
  • the preset condition may be a condition configured by the network side for the terminal device.
  • the terminal device receiving the preset condition from the first network device includes: the terminal device receiving a radio resource control RRC reconfiguration message from the first network device.
  • the RRC reconfiguration message includes preset conditions. That is to say, the terminal device receives the preset condition by receiving the RRC reconfiguration message.
  • the communication method in this embodiment of the present application further includes: the terminal device sends the first report to the first network device.
  • the first network device is a network device that the terminal device accesses before the handover process, so that the first network device determines the network optimization parameter based on the first report.
  • the first report is a report recorded when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process, and the first report includes the user plane transmission interruption duration, so that the first network device Aiming at the problem of user plane transmission interruption, network optimization parameters are determined to optimally handle the problem of user plane transmission interruption.
  • the embodiment of the present application provides a communication method, and the execution body of the method may be the first network device, or may be a chip applied to the first network device.
  • the description below takes the execution subject as an example of the first network device.
  • the method includes: the first network device acquires a preset condition.
  • the preset conditions include at least one of the following: the first item, only record the successful handover report SHR, the second item, only record the radio link failure RLF report, the third item, only report the SHR, and the fourth item, only report the RLF Report.
  • the first network device sends the preset condition to the terminal device.
  • the preset condition is used to determine the first report when the terminal equipment detects that the radio link failure RLF between the source cell and the DAPS handover with the target cell is completed during the DAPS handover process of the dual activation protocol stack.
  • the first report includes a report indicated to be recorded in the preset condition, or the first report includes a report indicated to be reported in the preset condition.
  • the preset condition indicates a report to be recorded by the terminal device, or a report to be reported by the terminal device.
  • the terminal device determines the first report that meets the preset condition.
  • the preset condition is provided by the first network device for the terminal device.
  • the terminal device only records one of the RLF report and the SHR report, or the terminal device only reports one of the RLF report and the SHR report.
  • the network side A report (such as the above SHR, or RLF report) can be obtained, thereby avoiding the problem of over-adjustment.
  • the first network device acquiring the preset condition includes: the first network device receiving the preset condition from the second network device.
  • the terminal device switches from the first network device to the second network device. That is to say, the preset condition can be configured by the second network device.
  • the first network device receiving the preset condition from the second network device includes: the first network device receiving a handover HO request confirmation message from the second network device.
  • the HO request confirmation message includes a radio resource control RRC reconfiguration message, and the preset condition is carried in the RRC reconfiguration message.
  • the preset condition is transmitted from the second network device to the first network device through an RRC reconfiguration message.
  • the preset condition is transmitted from the second network device to the first network device through the HO request confirmation message.
  • the first network device receives the preset condition from the second network device, including: the preset condition from the second network device before the first network device receives the HO request confirmation message.
  • the first network device sending the preset condition to the terminal device includes: the first network device sending an RRC reconfiguration message to the terminal device.
  • the first network device sending the preset condition to the terminal device includes: before the first network device sends the RRC reconfiguration message, sending the preset condition to the terminal device.
  • the preset condition is carried in one of the following: an RRC establishment message, an RRC re-establishment message, an RRC recovery message, or a system message.
  • the communication method in this embodiment of the present application further includes: the first network device receives the first report from the terminal device.
  • the first report is a report recorded when the user plane transmission interruption duration is greater than or equal to a threshold during the handover process, and the first report includes the user plane transmission interruption duration.
  • the first information includes at least one of the following:
  • the first network device can know the status of the preset condition carried in the RRC reconfiguration message through the second information.
  • the third item is the threshold of the third timer.
  • the running duration of the third timer indicates the duration during which the terminal device detects that there is a physical layer problem with the first network device.
  • the fourth item is the threshold of the fourth timer.
  • the running duration of the fourth timer indicates the duration between when the terminal triggers the measurement report and when the terminal and the first network device resume synchronization during the running of the third timer.
  • the first information is carried in the handover HO request message.
  • the communication method in this embodiment of the present application further includes: the second network device sending third information to the first network device.
  • the third information indicates that the second network device supports the SHR function.
  • the communication method in this embodiment of the present application further includes: the second network device receives fourth information from the first network device.
  • the fourth information is used to query the support status of the SHR function by the second network device.
  • Sending the third information to the first network device by the second network device includes: sending the third information to the first network device by the second network device according to the fourth information.
  • the second information when the second network device accepts one or more of at least one condition, the second information further indicates at least one of the following:
  • the first item, the RRC reconfiguration message carries one or more of at least one condition.
  • the second item is the condition type that triggers the recording of SHR.
  • the third item triggers the threshold of recording SHR.
  • the embodiment of the present application provides a communication method, and the execution subject of the method may be a terminal device, or may be a chip applied in the terminal device.
  • the following description is made by taking the execution subject as a terminal device as an example.
  • the method includes: the terminal device receives a trigger condition from the first network device. Wherein, the trigger condition at least includes that a radio link failure RLF occurs between the terminal device and the first network device during the handover process. When the trigger condition is satisfied, the terminal device records the successful handover report SHR. Wherein, the SHR at least indicates the trigger condition.
  • the terminal device will record this situation, that is, the above SHR at least indicates the trigger condition that the terminal device satisfies, so as to indicate that the terminal device and the first network device.
  • the above SHR at least indicates the trigger condition that the terminal device satisfies, so as to indicate that the terminal device and the first network device.
  • the SHR at least indicates a trigger condition, including: the SHR at least indicates a cause of RLF, so as to indicate that RLF has occurred between the terminal device and the first network device.
  • the reasons for RLF include at least one of the following: beam failure recovery failure, random access failure, maximum number of retransmissions, listen before talk failure, RLF recovery failure, second timer timeout, Wherein, the running duration of the second timer indicates the duration during which the terminal device detects that there is a physical layer problem with the first network device.
  • the communication method in this embodiment of the present application further includes: the terminal device sends the SHR to the first network device.
  • the first network device is a network device accessed by the terminal device before the handover process, and the SHR is used to determine network optimization parameters.
  • the embodiment of the present application provides a communication method, and the execution body of the method may be the first network device, or may be a chip applied to the first network device.
  • the description below takes the execution subject as an example of the first network device.
  • the method includes: the first network device sends a trigger condition to the terminal device, wherein the trigger condition at least includes that a radio link failure RLF occurs between the terminal device and the first network device during the handover process, and the trigger condition is used for the terminal device to meet the trigger condition
  • the SHR indicates at least the triggering condition.
  • the first network device receives the SHR from the terminal device, and determines network optimization parameters according to the SHR.
  • the SHR at least indicates a trigger condition, including: the SHR at least indicates a cause of RLF, so as to indicate that RLF has occurred between the terminal device and the first network device.
  • the reasons for RLF include at least one of the following: beam failure recovery failure, random access failure, maximum number of retransmissions, listen before talk failure, RLF recovery failure, second timer timeout, Wherein, the running duration of the second timer indicates the duration during which the terminal device detects that there is a physical layer problem with the first network device.
  • the first information further includes random access information.
  • the failure of the random access causes RLF to occur between the terminal device and the first network device.
  • the embodiment of the present application provides a communication device, which may be a terminal device in any possible design of the above-mentioned first aspect or any one of the first aspects, or a chip that realizes the functions of the above-mentioned terminal device;
  • the communication device includes a corresponding module, unit, or means (means) for implementing the above method, and the module, unit, or means may be implemented by hardware, software, or by executing corresponding software on hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the receiving unit is configured to receive indication information from the first network device.
  • the indication information indicates the first threshold.
  • the processing unit is configured to record the first report when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process.
  • the first report indicates the duration of user plane transmission interruption.
  • the user plane transmission interruption duration is the time interval from the user plane transmission interruption start identifier to the end identifier.
  • the start identifier of user plane transmission interruption includes one of the following:
  • the termination flag of user plane transmission interruption includes one of the following:
  • the sending unit successfully sends the first data packet to the second network device.
  • the receiving unit successfully receives the first data packet from the second network device.
  • the indication information also indicates a start identifier and/or a termination identifier of user plane transmission interruption.
  • the processing unit when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process, the processing unit is configured to record the first report, which specifically includes: when the running duration of the first timer is greater than or equal to In the case of the first threshold, a first report is logged. Wherein, the running duration of the first timer indicates the user plane transmission interruption duration.
  • the sending unit is further configured to send the first report to the first network device.
  • the first network device is a network device accessed by the communication device before the handover process.
  • the first report also indicates at least one of the following:
  • the second item is the start identifier of the user plane transmission interruption.
  • the third item is the stop flag of user plane transmission interruption.
  • the fourth item is the radio network temporary identifier CRNTI of the source cell.
  • the start identifier of user plane transmission interruption includes one of the following:
  • downlink out-of-synchronization occurs between the communication device and the first network device.
  • the second item is that a radio link failure RLF occurs between the communication device and the first network device.
  • the fourth item, the third timer starts.
  • the running duration of the third timer indicates the duration between when the processing unit triggers the measurement report and when the communication device and the first network device resume synchronization during the running of the second timer.
  • the termination flag of user plane transmission interruption includes one of the following:
  • the random access process between the communication device and the second network device is completed.
  • the second item is that the sending unit sends a radio resource control RRC reconfiguration complete message to complete.
  • the third item is downlink synchronization between the communication device and the second network equipment.
  • the fourth item, the second timer stops.
  • the fifth item, the third timer stops.
  • the first item the number of duplicate packets received.
  • the embodiment of the present application provides a communication device, which can be the first network device in the above-mentioned second aspect or any possible design of the second aspect, or implement the functions of the above-mentioned first network device chip;
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the processing unit is used for obtaining the indication information.
  • the indication information indicates the first threshold.
  • the sending unit is configured to send indication information to the terminal device.
  • the indication information is used for the terminal device to record the first report when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process, and the first report indicates the user plane transmission interruption duration.
  • the user plane transmission interruption duration is the time interval from the user plane transmission interruption start identifier to the end identifier.
  • the start identifier of user plane transmission interruption includes one of the following:
  • the end device successfully sent the last data packet to the communicator.
  • the end device successfully received the last data packet from the communicator.
  • the termination flag of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the first data packet to the second network device.
  • the terminal device successfully receives the first data packet from the second network device.
  • the communication device is a network device that the terminal device accesses before the handover process
  • the second network device is a network device that the terminal device accesses after the handover process.
  • the indication information also indicates a start identifier and/or a termination identifier of user plane transmission interruption.
  • the receiving unit is configured to receive the first report from the terminal device.
  • the communication device is a network device that the terminal device accesses before the handover process.
  • the processing unit is configured to acquire the indication information, specifically including: determining the indication information.
  • the processing unit is configured to acquire the indication information, including: receiving the indication information from the second network device through the receiving unit.
  • the sending unit is configured to send reference information to the second network device.
  • the reference information is used to determine the indication information.
  • the receiving unit is further configured to receive the first information from the second network device.
  • the first information indicates that the second network device supports the successful handover reporting SHR function.
  • the sending unit is configured to send the reference information to the second network device, and specifically includes: sending the reference information to the second network device according to the first information.
  • the communication method in the embodiment of the present application further includes: the sending unit is further configured to send the second information to the second network device.
  • the second information is used to request the second network device to feed back whether the SHR function is supported, so that the second network device feeds back the first information.
  • the first report also indicates at least one of the following:
  • the first item the reason that triggered the logging of the first report.
  • the second item is the start identifier of the user plane transmission interruption.
  • the third item is the stop flag of user plane transmission interruption.
  • the fourth item is the radio network temporary identifier CRNTI of the source cell.
  • the receiving unit is further configured to receive indication information from the second network device, specifically including: receiving a handover HO request acknowledgment message from the second network device, wherein the HO request acknowledgment message includes a radio resource control RRC In the reconfiguration message, the indication information is carried in the RRC reconfiguration message.
  • the receiving unit is configured to receive indication information from the second network device, specifically including: receiving an HO request confirmation message from the second network device, wherein the HO request confirmation message includes an RRC reconfiguration message, indicating The information is carried outside the RRC reconfiguration message and in the HO request confirmation message.
  • the receiving unit is configured to receive the indication information from the second network device, specifically including: receiving the indication information from the second network device before receiving the HO request confirmation message.
  • the sending unit is configured to send indication information to the terminal device, specifically including: sending an RRC reconfiguration message to the terminal device.
  • the sending unit is configured to send indication information to the terminal device, specifically including: sending the indication information to the terminal device before sending the RRC reconfiguration message.
  • the indication information is carried in one of the following: an RRC establishment message, an RRC re-establishment message, an RRC recovery message, or a system message.
  • the embodiment of the present application provides a communication device, which can be the second network device in any possible design of the above third aspect or the third aspect, or implement the functions of the above second network device chip; the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the processing unit is used for determining the indication information.
  • the indication information indicates the first threshold.
  • the sending unit is configured to send indication information to the first network device.
  • the first network device is a network device that the terminal device accesses before the handover process
  • the communication device is a network device that the terminal device accesses after the handover process.
  • the first threshold is used for the terminal device to record a first report when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process, and the first report indicates the user plane transmission interruption duration.
  • the user plane transmission interruption duration is the time interval from the user plane transmission interruption start identifier to the end identifier.
  • the start identifier of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the last data packet to the first network device.
  • the end device successfully received the last data packet from the first network device.
  • the end device successfully sends the first data packet to the communicator.
  • the end device successfully receives the first data packet from the communicator.
  • the first network device is a network device that the terminal device accesses before the handover process
  • the communication device is a network device that the terminal device accesses after the handover process.
  • the indication information also indicates a start identifier and/or a termination identifier of user plane transmission interruption.
  • the receiving unit is further configured to receive reference information from the first network device. Wherein, the reference information is used to determine the indication information.
  • the sending unit is further configured to send the first information to the first network device.
  • the first information indicates that the communication device supports a successful handover report SHR function.
  • the receiving unit is further configured to receive second information from the first network device.
  • the second information is used to request the communication device to feedback whether to support the SHR function.
  • the sending unit is configured to send the first information to the first network device, and specifically includes: sending the first information to the first network device according to the second information.
  • the sending unit is configured to send indication information to the first network device, specifically including: sending a handover HO request confirmation message to the first network device.
  • the HO request confirmation message includes a radio resource control RRC reconfiguration message
  • the indication information is carried in the RRC reconfiguration message.
  • the sending unit is configured to send indication information to the first network device, specifically including: sending an HO request confirmation message to the first network device.
  • the HO request confirmation message includes the RRC reconfiguration message
  • the indication information is carried outside the RRC reconfiguration message and in the HO request confirmation message.
  • the sending unit is configured to send the indication information to the first network device, specifically including: sending the indication information to the first network device before sending the HO request confirmation message.
  • an embodiment of the present application provides a communication device, which may be a terminal device in any possible design of the fourth aspect or the fourth aspect, or a chip that realizes the functions of the terminal device above;
  • the communication device includes a corresponding module, unit, or means (means) for implementing the above method, and the module, unit, or means may be implemented by hardware, software, or by executing corresponding software on hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the processing unit is used to determine the first Report.
  • the first report includes a report to be recorded indicated by a preset condition, or the first report includes a report to be reported indicated by a preset condition, and the preset condition includes at least one of the following: the first item, only record the successful handover report SHR , the second item, only record the RLF report, the third item, only report the SHR, and the fourth item, only report the RLF report.
  • the receiving unit is configured to receive a preset condition from the first network device.
  • the first network device is a network device accessed by the communication device before the handover process.
  • the receiving unit is configured to receive a preset condition from the first network device, specifically including: receiving a radio resource control RRC reconfiguration message from the first network device.
  • the RRC reconfiguration message includes preset conditions.
  • the receiving unit is configured to receive the preset condition from the first network device, specifically including: receiving the preset condition from the first network device before receiving the RRC reconfiguration message.
  • the preset condition is carried in one of the following: an RRC establishment message, an RRC re-establishment message, an RRC recovery message, or a system message. That is to say, the preset conditions can be carried in different messages for transmission.
  • the preset conditions are pre-configured.
  • the sending unit is configured to send the first report to the first network device.
  • the first network device is a network device accessed by the communication device before the handover process.
  • the first report is a report recorded when the user plane transmission interruption duration is greater than or equal to a first threshold during the handover process, and the first report includes the user plane transmission interruption duration.
  • the embodiment of the present application provides a communication device, which may be the first network device in the fifth aspect or any possible design of the fifth aspect, or implement the functions of the first network device above chip; the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the processing unit is used for acquiring preset conditions.
  • the preset conditions include at least one of the following: the first item, only record the successful handover report SHR, the second item, only record the radio link failure RLF report, the third item, only report the SHR, and the fourth item, only report the RLF Report.
  • the sending unit is used for sending preset conditions to the terminal equipment.
  • the preset condition is used to determine the first report when the terminal device detects RLF with the source cell and completes the DAPS handover with the target cell during the DAPS handover process of the dual-activation protocol stack. Include the report indicated in the preset condition to record, or the first report includes the report indicated in the preset condition to report.
  • the processing unit is configured to acquire a preset condition, specifically including: determining the preset condition.
  • the processing unit is configured to acquire the preset condition, which specifically includes: receiving the preset condition from the second network device through the receiving unit.
  • the terminal equipment is switched from the communication device to the second network equipment.
  • the receiving unit is configured to receive a preset condition from the second network device, specifically including: receiving a handover HO request confirmation message from the second network device.
  • the HO request confirmation message includes a radio resource control RRC reconfiguration message
  • the preset condition is carried in the RRC reconfiguration message.
  • the receiving unit is configured to receive the preset condition from the second network device, specifically including: receiving the HO request confirmation message from the second network device.
  • the HO request confirmation message includes the RRC reconfiguration message
  • the preset condition is carried outside the RRC reconfiguration message and in the HO request confirmation message.
  • the receiving unit is configured to receive the preset condition from the second network device, specifically including: before receiving the HO request confirmation message, the preset condition from the second network device.
  • the sending unit is configured to send the preset condition to the terminal device, specifically including: sending an RRC reconfiguration message to the terminal device.
  • the sending unit is configured to send the preset condition to the terminal device, specifically including: sending the preset condition to the terminal device before sending the RRC reconfiguration message.
  • the preset condition is carried in one of the following: an RRC establishment message, an RRC re-establishment message, an RRC recovery message, or a system message.
  • the receiving unit is further configured to receive the first report from the terminal device.
  • the first report is a report recorded when the user plane transmission interruption duration is greater than or equal to a threshold during the handover process, and the first report includes the user plane transmission interruption duration.
  • the embodiment of the present application provides a communication device, which can be the second network device in the sixth aspect or any possible design of the sixth aspect, or implement the functions of the second network device above chip;
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the processing unit is used to determine the preset condition.
  • the preset conditions include at least one of the following: the first item, only record the successful handover report SHR, the second item, only record the radio link failure RLF report, the third item, only report the SHR, and the fourth item, only report the RLF Report.
  • the sending unit is configured to send the preset condition to the first network device.
  • the preset condition is used to determine the first report when the terminal equipment detects that the radio link failure RLF between the source cell and the DAPS handover with the target cell is completed during the DAPS handover process of the dual activation protocol stack.
  • the first report includes a report indicating recording in the preset condition, or the first report includes a report indicating reporting in the preset condition
  • the first network device is the network device that the terminal device accesses before the handover process
  • the communication device is the terminal device A network device connected after the handover process.
  • the sending unit is configured to send the preset condition to the first network device, specifically including: sending a handover HO request confirmation message to the first network device.
  • the HO request confirmation message includes a radio resource control RRC reconfiguration message
  • the preset condition is carried in the RRC reconfiguration message.
  • the sending unit is configured to send the preset condition to the first network device, specifically including: sending an HO request confirmation message to the first network device.
  • the HO request confirmation message includes the RRC reconfiguration message
  • the preset condition is carried outside the RRC reconfiguration message and in the HO request confirmation message.
  • the sending unit is configured to send the preset condition to the first network device, specifically including: sending the preset condition to the first network device before sending the HO request confirmation message.
  • this embodiment of the present application provides a communication device, which may be the first network device in any possible design of the seventh aspect or the seventh aspect, or a device that implements the functions of the first network device above chip; the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the receiving unit is used for receiving the successful handover report SHR and the radio link failure RLF report from the terminal equipment.
  • the SHR and RLF reports are reports determined when the terminal device detects RLF with the source cell and completes the DAPS handover with the target cell during the DAPS handover process of the dual-activation protocol stack.
  • the processing unit is used to determine the network optimization parameter according to the SHR, or the processing unit is used to determine the network optimization parameter according to the RLF report, or the processing unit is used to determine the network optimization parameter according to the SHR and the RLF report.
  • the processing unit when the processing unit is configured to determine the network optimization parameter according to the SHR, the processing unit is also configured to discard the RLF report.
  • the processing unit when the processing unit is configured to determine the network optimization parameter according to the RLF report, the processing unit is also configured to discard the SHR.
  • this embodiment of the present application provides a communication device, which can be the first network device in any possible design of the above-mentioned eighth aspect or the eighth aspect, or implement the functions of the above-mentioned first network device chip; the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the sending unit is configured to send the first information to the second network device.
  • the communication device is a network device connected before the handover process of the terminal device, and the second network device is a network device connected after the handover process.
  • the first information is used to indicate at least one condition that triggers recording of the successful handover report SHR.
  • the receiving unit is used for receiving the second information from the second network device.
  • the second information indicates whether the second network device accepts one or more of the at least one condition.
  • the first information includes at least one of the following:
  • the first item is the threshold of user plane transmission interruption duration.
  • the second item the threshold of the second timer.
  • the running duration of the second timer indicates the duration for which the terminal device does not access the second network device after receiving the radio resource control RRC reconfiguration message.
  • the third item is the threshold of the third timer.
  • the running duration of the third timer indicates the duration during which the terminal device detects that there is a physical layer problem with the communication device.
  • the fourth item is the threshold of the fourth timer.
  • the running duration of the fourth timer indicates the duration between when the terminal triggers the measurement report and when the terminal and the communication device resume synchronization during the running of the third timer.
  • the first information is carried in the handover HO request message.
  • the sending unit is configured to send the first information to the second network device, and specifically includes: sending the first information to the second network device before sending the HO request message.
  • the receiving unit is further configured to receive third information from the second network device.
  • the third information indicates that the second network device supports the SHR function.
  • the sending unit is configured to send the first information to the second network device, and specifically includes: sending the first information to the second network device according to the third information.
  • the sending unit is further configured to send fourth information to the second network device.
  • the fourth information is used to request the second network device to feed back whether to support the SHR function.
  • the second information when the second network device accepts one or more of at least one condition, the second information further indicates at least one of the following:
  • the first item, the RRC reconfiguration message carries one or more of at least one condition.
  • the second item is the condition type that triggers the recording of SHR.
  • the third item triggers the threshold of recording SHR.
  • an embodiment of the present application provides a communication device, which may be the second network device in any possible design of the above-mentioned ninth aspect or the ninth aspect, or implement the functions of the above-mentioned second network device chip;
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the receiving unit is configured to receive the first information from the first network device.
  • the first network device is a network device connected before the handover process of the terminal device, and the communication device is a network device connected after the handover process.
  • the first information is used to indicate at least one condition that triggers recording of the successful handover report SHR.
  • the sending unit is configured to send the second information to the first network device.
  • the second information is used to indicate whether the communication device accepts one or more of the at least one condition.
  • the first information includes at least one of the following:
  • the first item is the threshold of user plane transmission interruption duration.
  • the second item the threshold of the second timer.
  • the running duration of the second timer indicates the duration of the terminal device not accessing the communication device after receiving the RRC reconfiguration message.
  • the third item is the threshold of the third timer.
  • the running duration of the third timer indicates the duration during which the terminal device detects that there is a physical layer problem with the first network device.
  • the fourth item is the threshold of the fourth timer.
  • the running duration of the fourth timer indicates the duration between when the terminal triggers the measurement report and when the terminal and the first network device resume synchronization during the running of the third timer.
  • the first information is carried in the handover HO request message.
  • the receiving unit is configured to receive the first information from the first network device, specifically including: before receiving the HO request message, receiving the first information from the first network device.
  • the sending unit is further configured to send third information to the first network device.
  • the third information indicates that the communication device supports the SHR function.
  • the receiving unit is configured to receive fourth information from the first network device.
  • the fourth information is used to query the support status of the communication device for the SHR function.
  • the sending unit is configured to send the third information to the first network device, and specifically includes: sending the third information to the first network device according to the fourth information.
  • the second information when the communication device accepts one or more of at least one condition, the second information further indicates at least one of the following:
  • the third item triggers the threshold of recording SHR.
  • the embodiment of the present application provides a communication device.
  • the communication device may be a terminal device in any possible design of the above-mentioned tenth aspect or any of the tenth aspects, or a chip that realizes the functions of the above-mentioned terminal device;
  • the above-mentioned communication device includes corresponding modules, units, or means (means) for realizing the above-mentioned method, and the modules, units, or means may be implemented by hardware, software, or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit and a processing unit.
  • the receiving unit is configured to receive a trigger condition from the first network device.
  • the trigger condition at least includes that a radio link failure RLF occurs between the communication device and the first network device during the handover process.
  • the processing unit is configured to record a successful handover report SHR when the trigger condition is met. Wherein, the SHR at least indicates the trigger condition.
  • the SHR at least indicates the trigger condition, including: the SHR at least indicates the cause of the RLF.
  • the first information further includes random access information, and failure of the random access causes RLF to occur between the communication device and the first network device.
  • the embodiment of the present application provides a communication device, which can be the first network device in any possible design of the above-mentioned tenth aspect or the tenth aspect, or realize the function of the above-mentioned first network device
  • the chip; the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software on hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a receiving unit, a processing unit and a sending unit.
  • the sending unit is configured to send a trigger condition to the terminal device, wherein the trigger condition at least includes a radio link failure RLF between the terminal device and the communication device during the handover process, and the trigger condition is used when the terminal device satisfies the trigger condition
  • a successful handover report SHR is recorded, the SHR indicating at least a trigger condition.
  • the receiving unit is configured to receive the SHR from the terminal device.
  • a processing unit is configured to determine network optimization parameters according to the SHR.
  • an embodiment of the present application provides a communication device, including: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device performs any one of the above aspects Or a method executed by a terminal device in any possible design of any aspect.
  • the communication device may be the terminal device in the above first aspect or any possible design of the first aspect, or may be the terminal device in the above fourth aspect or any possible design of the fourth aspect, or may be the above-mentioned
  • the embodiment of the present application provides a chip, including a processing circuit and an input/output interface.
  • the input and output interface is used to communicate with modules other than the chip
  • the chip may be a chip that implements the function of the terminal device in the above first aspect or any possible design of the first aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above first aspect or any possible design of the first aspect.
  • the chip may be a chip that implements the function of the terminal device in the fourth aspect or any possible design of the fourth aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above fourth aspect or any possible design of the fourth aspect.
  • the chip may be a chip that implements the function of the terminal device in the above tenth aspect or any possible design of the tenth aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above tenth aspect or any possible design of the tenth aspect.
  • the communication device may be the first network device in the above second aspect or any possible design of the second aspect, or may be the first network device in the above fifth aspect or any possible design of the fifth aspect, Or it may be the first network device in the seventh aspect or any possible design of the seventh aspect, or it may be the first network device in the eighth aspect or any possible design of the eighth aspect, or it may be It is the first network device in any possible design of the eleventh aspect or the eleventh aspect above, or a chip that implements the functions of the first network device above.
  • the embodiment of the present application provides a communication device, including: a processor; the processor is coupled with a memory, and is used to read and execute instructions in the memory, so that the communication device performs any of the above-mentioned A method executed by the first network device in any possible design of one aspect or any aspect.
  • the communication device may be the first network device in the above second aspect or any possible design of the second aspect, or may be the first network device in the above fifth aspect or any possible design of the fifth aspect, Or it may be the first network device in the seventh aspect or any possible design of the seventh aspect, or it may be the first network device in the eighth aspect or any possible design of the eighth aspect, or it may be It is the first network device in any possible design of the eleventh aspect or the eleventh aspect above, or a chip that implements the functions of the first network device above.
  • the embodiment of the present application provides a chip, including a processing circuit and an input/output interface.
  • the input and output interface is used to communicate with modules other than the chip, for example, the chip may be a chip that implements the function of the first network device in the second aspect or any possible design of the second aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above second aspect or any possible design of the second aspect.
  • the chip may be a chip that implements the function of the first network device in the fifth aspect or any possible design of the fifth aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the fifth aspect above or any possible design of the fifth aspect.
  • the chip may be a chip that implements the function of the first network device in the seventh aspect or any possible design of the seventh aspect.
  • the processing circuit is used to run computer programs or instructions, so as to realize the method in the above seventh aspect or any possible design of the seventh aspect.
  • the chip may be a chip that implements the function of the first network device in the eighth aspect or any possible design of the eighth aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above eighth aspect or any possible design of the eighth aspect.
  • the chip may be a chip that implements the function of the first network device in any possible design of the above eleventh aspect or any one of the eleventh aspects.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above eleventh aspect or any possible design of the eleventh aspect.
  • the embodiment of the present application provides a communication device, including: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device performs any one of the above aspects Or a method executed by the second network device in any possible design of any aspect.
  • the communication device may be the second network device in the above third aspect or any possible design of the third aspect, or may be the second network device in the above sixth aspect or any possible design of the sixth aspect, Or it may be the second network device in the above ninth aspect or any possible design of the ninth aspect, or a chip that implements the functions of the above second network device.
  • the embodiment of the present application provides a communication device, including: a processor; the processor is coupled with a memory, and is used to read and execute instructions in the memory, so that the communication device performs any of the above-mentioned A method executed by the second network device in any possible design of the aspect or any aspect.
  • the communication device may be the second network device in the above third aspect or any possible design of the third aspect, or may be the second network device in the above sixth aspect or any possible design of the sixth aspect, Or it may be the second network device in the above ninth aspect or any possible design of the ninth aspect, or a chip that implements the functions of the above second network device.
  • the embodiment of the present application provides a chip, including a processing circuit and an input/output interface.
  • the input and output interface is used to communicate with modules other than the chip
  • the chip may be a chip that realizes the function of the second network device in any possible design of the above third aspect or the third aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above third aspect or any possible design of the third aspect.
  • the chip may be a chip that realizes the function of the second network device in the sixth aspect or any possible design of the sixth aspect.
  • the processing circuit is used to run computer programs or instructions, so as to realize the method in the sixth aspect above or any possible design of the sixth aspect.
  • the chip may be a chip that implements the function of the second network device in the ninth aspect or any possible design of the ninth aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above ninth aspect or any possible design of the ninth aspect.
  • the embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores instructions, and when it is run on a computer, the computer can execute any one of the above-mentioned aspects Methods.
  • an embodiment of the present application provides a computer program product containing instructions, which, when run on a computer, enable the computer to execute the method in any one of the above aspects.
  • an embodiment of the present application provides a communication system, where the communication system includes the terminal device, the first network device, and the second network device in any one of the foregoing aspects.
  • the communication system includes the terminal device and the first network device in any one of the foregoing aspects.
  • FIG. 1 is a schematic structural diagram of a mobile communication system applied in an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a communication method provided in an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 4 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 5a is a schematic flowchart of another communication method provided in the embodiment of the present application.
  • FIG. 5b is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 10 is a schematic flowchart of another communication method provided in the embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 12 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 13 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a communication system 1000 applied in an embodiment of the present application.
  • the communication system 1000 includes at least one network device (such as 110a and 110b in FIG. 1 ) and at least one terminal device 120 (such as 120a-120j in FIG. 1 ). Terminal devices are connected to network devices wirelessly.
  • FIG. 1 is only a schematic diagram.
  • the communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in FIG. 1 .
  • the network equipment can be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (transmission reception point, TRP), and a next-generation base station (next station) in the fifth generation (5th generation, 5G) mobile communication system.
  • generation NodeB, gNB the next-generation base station in the sixth generation (6th generation, 6G) mobile communication system, the base station in the future mobile communication system or the access node in the WiFi system, etc.; it can also be a module that completes some functions of the base station Or unit, for example, can be a centralized unit (central unit, CU) or a distributed unit (distributed unit, DU).
  • the CU here completes the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and also completes the function of the service data adaptation protocol (SDAP); the DU completes the functions of the base station
  • the functions of the radio link control layer and the medium access control (medium access control, MAC) layer can also complete the functions of part of the physical layer or all of the physical layer.
  • 3rd generation partnership project, 3GPP third generation partnership project
  • the network device may be a macro base station (such as 110a in Figure 1), a micro base station or an indoor station (such as 110b in Figure 1), or a relay node or a donor node.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the network device.
  • a network device is used as an example for description below.
  • a terminal device may also be called a terminal, a user equipment (user equipment, UE), a mobile station, a mobile terminal, and the like.
  • Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (internet of things, IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.
  • Network equipment and terminal equipment can be fixed or mobile.
  • Network equipment and terminal equipment can be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and artificial satellites in the air.
  • the embodiments of the present application do not limit the application scenarios of the network device and the terminal device.
  • the helicopter or drone 120i in FIG. 1 can be configured as a mobile base station.
  • those terminal equipment 120j connected to the wireless access network through Device 120i is a network device; but for network device 110a, 120i is a terminal device, that is, communication between 110a and 120i is performed through a wireless air interface protocol.
  • communication between 110a and 120i may also be performed through an interface protocol between base stations.
  • 120i is also a network device. Therefore, both network equipment and terminal equipment can be collectively referred to as communication devices, 110a and 110b in FIG. 1 can be referred to as communication devices with network device functions, and 120a-120j in FIG. 1 can be referred to as communication devices with terminal device functions .
  • Communication between network devices and terminal devices, between network devices and network devices, between terminal devices and terminal devices can be performed through licensed spectrum, or through license-free spectrum, or through licensed spectrum and license-free spectrum at the same time
  • Communication can be performed through a frequency spectrum below 6 gigahertz (GHz), or can be performed through a frequency spectrum above 6 GHz, and can also be performed using a frequency spectrum below 6 GHz and a frequency spectrum above 6 GHz at the same time.
  • GHz gigahertz
  • the embodiments of the present application do not limit the frequency spectrum resources used for wireless communication.
  • the functions of the network device may also be performed by modules (such as chips) in the network device, or may be performed by a control subsystem including the functions of the network device.
  • the control subsystem including network device functions may be the control center in the above application scenarios such as smart grid, industrial control, intelligent transportation, and smart city.
  • the functions of the terminal equipment may also be performed by a module (such as a chip or a modem) in the terminal equipment, or may be performed by a device including the functions of the terminal equipment.
  • the network device sends downlink signals or downlink information to the terminal device, and the downlink information is carried on the downlink channel; the terminal device sends uplink signals or uplink information to the network device, and the uplink information is carried on the uplink channel.
  • the terminal device needs to establish a wireless connection with the cell controlled by the network device.
  • a cell with which a terminal device has established a wireless connection is called the serving cell of the terminal device.
  • the terminal device may switch from the source cell to the target cell to ensure the connection between the terminal device and the network. continuity of communication.
  • the above process is called "handover".
  • the cell that the terminal device accesses before the handover occurs due to reasons such as movement, network reasons, service load adjustment, and device failure is called a source cell.
  • the network device corresponding to the source cell is called the source network device.
  • the cell that the terminal equipment accesses after handover occurs due to reasons such as movement, network reasons, business load adjustment, and equipment failure is called the target cell.
  • the network device corresponding to the target cell is called the target network device.
  • DAPS handover dual active protocol stack handover
  • the terminal equipment uses two protocol stacks. Wherein, one protocol stack is used for communicating with the source network device corresponding to the source cell, and the other protocol stack is used for communicating with the target network device corresponding to the target cell.
  • the DAPS handover process includes the following steps:
  • the terminal device determines a trigger event.
  • the trigger event may be that the signal quality of the source cell is lower than a preset value.
  • the terminal device executes S200, or during the process of executing S200, the terminal device performs user plane data transmission through the source network device and a user plane function (user plane function, UPF) network element.
  • a user plane function user plane function, UPF
  • the terminal device sends a measurement report to the source network device.
  • the source network device receives the measurement report from the terminal device.
  • the measurement report includes information such as the received quality of the reference signal of the source cell, the received quality of the reference signal of the neighboring cell, and the like.
  • the source network device determines a cell to be accessed. For example, the source network device may make a handover decision (handover decision) based on the measurement report and/or radio resource management (radio resource management, RRM) information, and determine the cell to be accessed.
  • handover decision based on the measurement report and/or radio resource management (radio resource management, RRM) information
  • RRM radio resource management
  • the source network device sends a DAPS handover request (handover request) message to the target network device.
  • the target network device receives the DAPS switching request message from the source network device.
  • the DAPS switching request message is used to request to switch the connection between the terminal device and the source network device to the target network device.
  • the target network device executes admission control (admission control), such as determining whether to establish a connection with the terminal device, if so, then execute S205:
  • the target network device sends a DAPS handover request acknowledgment (handover request acknowledge) message to the source network device.
  • the source network device receives the DAPS handover request confirmation message from the target network device.
  • the DAPS handover request confirmation message indicates whether the target network device accepts the DAPS handover.
  • the DAPS handover request confirmation message includes a message for handover configuration, such as a radio resource control reconfiguration (radio resource control reconfig, RRC Reconfig) message.
  • a radio resource control reconfiguration radio resource control reconfig, RRC Reconfig
  • the RRC reconfiguration message has a synchronous reconfigurationReconfigurationWithSync information element.
  • the RRC reconfiguration message has a mobility control information MobilityControlInfo information element.
  • both the ReconfigurationWithSync information element and the MobilityControlInfo information element include random access information. The random access information is used by the terminal device to perform random access.
  • the source network device sends an RRC reconfiguration message to the terminal device.
  • the terminal device receives the RRC reconfiguration message from the source network device.
  • the source network device does not read the content in the RRC reconfiguration message, nor does it modify the content in the RRC reconfiguration message, and directly transmits it transparently to the terminal device.
  • the terminal device reads the RRC reconfiguration message, and initiates a RACH process to the target network device corresponding to the target cell according to the random access information in the RRC reconfiguration message.
  • the target network device corresponding to the target cell performs a RACH process with the terminal device.
  • the terminal device does not disconnect from the source network device after receiving the RRC reconfiguration message.
  • the terminal device executes S208:
  • the terminal device sends an RRC reconfiguration complete message to the target network device.
  • the target network device receives the RRC reconfiguration complete message from the terminal device.
  • the target network device sends a handover success (HO success) message to the source network device.
  • the source network device receives a handover success message from the target network device.
  • the source network device after the source network device executes S209, it no longer transmits uplink data and downlink data with the terminal device.
  • the target network device sends a release message to the terminal device after performing S207.
  • the terminal device receives the release message from the target network device.
  • the release message indicates to release the connection between the terminal device and the source network device.
  • the terminal device releases the connection between itself and the source network device according to the release message.
  • the connection between the terminal device and the source network device is not released.
  • the terminal device releases the connection with the source network device to achieve zero millisecond interruption of user plane transmission, but the control plane signaling between the terminal device and the source network device no longer interact.
  • the user plane transmission between the terminal device and the network device is interrupted.
  • the terminal device is successfully handed over to the target network device, and the above situation is still classified as successful handover (successful handover) in relevant protocols.
  • the factors that lead to the interruption of user plane transmission include but are not limited to at least one of the following: the first item, the terminal device detects a radio link failure (radio link failure, RLF) in the connection between itself and the source cell; the second item , the scheduling of the source network device is unreasonable, causing the terminal device to receive repeated data packets.
  • RLF radio link failure
  • Wireless link failure report radio link failure report, RLF report
  • successful handover report successful handover report, SHR
  • MRO mobility robustness optimization
  • the terminal device reports the occurrence of abnormal parameters related to mobility to the network device.
  • the network device can independently analyze the mobility parameters reported by the terminal device to determine network optimization parameters.
  • the mobility parameter may be carried in the RLF report or SHR.
  • the terminal device when the terminal device fails to connect, the terminal device records the RLF report.
  • the terminal device when the terminal device fails to connect again, the terminal device clears the previously recorded RLF report and records the latest RLF report.
  • the RLF report includes at least one failure information as follows:
  • failed primary cell identity failed primary cell identity, failedPcellID
  • failedPcellID failed primary cell identity
  • connectionFailureType such as RLF or HOF
  • timer T312 expiration.
  • the timer T312 is a timer started after the terminal device sends the measurement report.
  • Reestablishment cell identity (reestablishment cell identity, reestablishmentCellId), that is, the information of the cell that initiates reestablishment after the connection fails.
  • Connection failure time that is, the time from the last time the terminal device receives the switching message to the connection failure.
  • timeSinceFailure The length of time to start recording when the connection fails (timeSinceFailure), generally refers to the length of time from the connection failure to the RLF report.
  • the introduction of the RLF report can refer to related protocols, such as the description in UEInformationResponse in 3GPP TS 38.331, and will not be repeated here.
  • SHR is to identify the potential mobility failure problem in the mobility success scenario, and introduces the report of the terminal equipment to record and report the parameters in the handover success process.
  • the SHR includes mobility related information for potentially failed successful handovers.
  • the source network device can combine the SHR and the context of the terminal device to optimize the mobility of the terminal device.
  • the SHR trigger condition includes at least one of the following:
  • the running duration of the timer T310 is greater than or equal to the threshold 1.
  • the running duration of the timer T310 indicates the duration for the terminal device to detect physical layer problems (physical layer problems) with the source network device.
  • the timer T310 is stopped.
  • the terminal device determines that a radio link failure occurs.
  • threshold 1 and threshold X are different thresholds. Typically, Threshold 1 is smaller than Threshold X.
  • the second item, the running duration of the timer T312 is greater than or equal to the threshold 2 .
  • the timer T312 is started during the operation of the timer T310.
  • the running duration of the timer T312 indicates the duration between when the terminal device triggers a measurement report and when the terminal device and the source network device resume synchronization during the running of the timer T312.
  • the terminal device determines that a radio link failure occurs.
  • threshold 2 and threshold Y are different thresholds. Typically, Threshold 2 is smaller than Threshold Y.
  • the running duration of the timer T304 is greater than or equal to the threshold 3 .
  • the running duration of the timer T304 indicates the duration of the terminal device not accessing the target network device after receiving the RRC reconfiguration message.
  • the terminal device starts the timer T304 when receiving the RRC reconfiguration message, and when the running time of the timer T304 is greater than or equal to the threshold Z, the terminal device determines that a handover failure occurs.
  • threshold 3 and threshold Z are different thresholds. Typically, Threshold 3 is smaller than Threshold Z.
  • threshold X, threshold Y, and threshold Z above can be configured by the cell RLF-TimersAndConstants, which are different from threshold 1, threshold 2, and threshold 3 configured in the SHR trigger condition.
  • the SHR trigger condition is carried in the RRC reconfiguration message.
  • the terminal device receives the SHR trigger condition by receiving the RRC reconfiguration message.
  • the terminal device records the SHR when it determines that the triggering condition of the SHR is met.
  • the terminal device sends the SHR to the source network device, so that the source network device determines network optimization parameters.
  • the potential mobility failure does not represent a real failure, but that the terminal device encounters a phenomenon of impending handover failure during the handover process, so the SHR is recorded. For example, if the configuration is within 20ms, the handover is successful if the terminal equipment can switch to the target cell, but if the threshold is 18ms, the terminal equipment will only succeed in handover after 19ms. This situation is a latent mobility failure.
  • the context of the terminal equipment may also be described as a user equipment (user equipment, UE) context.
  • the context of the terminal device includes authentication information of the terminal device, network capability information of the terminal device, and the like.
  • the user plane transmission between the terminal device and the network device may also be interrupted, such as the above-mentioned problem of potential mobility failure.
  • the terminal device is configured with an SHR trigger condition, but the terminal device determines that the SHR trigger condition is not satisfied, the terminal device does not record the SHR.
  • the configuration of the SHR trigger condition is not mandatory, and the network side may not configure the SHR trigger condition for the terminal device. In this way, the terminal device may not record the SHR, which causes the problem that the network side cannot optimally handle the transmission interruption of the user plane.
  • the embodiment of the present application provides a communication method, and the communication method of the embodiment of the present application (such as the first communication method, the second communication method, the third communication method, or the fourth communication method) can be applied to FIG. 1 The communication system shown.
  • the handover process is introduced by taking the above-mentioned DAPS handover process as an example.
  • the first network device is the network device that the terminal device accesses before the handover process, that is, the source network device
  • the second network device is The network device that the terminal device accesses after the handover process is the target network device.
  • the names of messages between network elements or the names of parameters in messages in the following embodiments of the present application are just examples, and may be other names in specific implementations. In this unified description, the following will not repeat them.
  • the first network device may be a source base station
  • the second network device may be a target base station
  • the first network device and the second network device may be the same network device.
  • the terminal device receives indication information from the first network device.
  • the indication information indicates the first threshold.
  • the terminal device records the first report.
  • the first report indicates the duration of user plane transmission interruption. In this way, the terminal device can also trigger the recording of the first report based on the user plane transmission interruption duration.
  • the first report includes the duration of user plane transmission interruption, even if the terminal device successfully accesses the second network device, but the terminal device has the phenomenon of user plane transmission interruption, the first report can also record the duration of user plane transmission interruption, avoiding existing The problem that the terminal equipment cannot record and report in this case also lays a foundation for the network side to determine the optimization parameters.
  • the first communication method 300 includes the following steps:
  • the first network device acquires indication information.
  • the indication information is used by the terminal device to determine the first threshold.
  • the first threshold is used to trigger the terminal device to record the first report.
  • the indication information may directly indicate the value of the first threshold.
  • the first threshold is 10 milliseconds
  • the indication information includes information of "10 milliseconds”.
  • the indication information may indirectly indicate the value of the first threshold. For example, there is a certain correspondence between characters and the value of the first threshold, as shown in Table 1-1.
  • the first threshold (unit: milliseconds) 1 5 2 10 3 15
  • the first threshold corresponding to the number “1” is 5 milliseconds
  • the first threshold corresponding to the number “2” is 10 milliseconds
  • the first threshold corresponding to the number “3” is 15 milliseconds. It should be understood that in Table 1-1, only the first threshold value of 5 milliseconds, 10 milliseconds, and 15 milliseconds is used as an example for introduction, and the first threshold value may also have other values, which are not limited in this embodiment of the present application .
  • only numbers (such as “1", "2", "3") have a corresponding relationship with the first threshold are introduced as examples. Of course, the corresponding relationship with the first threshold can also be letters, symbols, etc., which are not limited in this embodiment of the present application.
  • the terminal device can determine that the first threshold is 5 milliseconds according to Table 1-1 and the number carried in the indication information. In the case that the indication information carries the number "2", the terminal device can determine that the first threshold is 10 milliseconds according to Table 1 and the number carried in the indication information. In the case that the indication information carries the number "3", the terminal device can determine that the first threshold is 15 milliseconds according to Table 1-1 and the number carried in the indication information.
  • the indication information may indirectly indicate the value of the first threshold.
  • the indication information indicates the correspondence between the first threshold and the corresponding failure threshold, as shown in Table 1-2. If the failure threshold is 100 ms, the terminal device determines the first threshold according to the indication information and the failure threshold, as shown in Table 1-2.
  • Indications are percentages
  • the first threshold (unit: milliseconds) 50% 50 60% 60
  • the indication information indicates the first threshold.
  • the indication information may also indicate the first threshold in other ways, which is not limited in this embodiment of the present application.
  • the user plane transmission interruption duration may refer to the time interval from the user plane transmission interruption start identifier to the termination identifier.
  • the unit of the time interval includes any one of the following: millisecond (millisecond), symbol (symbol), time slot (slot) and so on.
  • the start identifier and/or end identifier may be predefined by the protocol.
  • the protocol predefined user plane transmission interruption duration is "the last data packet successfully transmitted between the terminal device and the first network device (for example, the successful reception of the last data packet from the first network device The last data packet of the network device, or the last data packet successfully sent to the first network device, or the data packet later in time between the above two)" to "Successful transmission between the terminal device and the second network device (such as the first data packet successfully received from the second network device, or the first data packet successfully sent to the second network device, or the data packet earlier in time between the above two)" time interval between.
  • the indication information may be used to indicate the start identifier and/or the end identifier used to determine the user plane transmission interruption duration.
  • the start identifier of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the last data packet to the first network device.
  • the terminal device successfully sends the last data packet to the first network device, and the specific process includes: the terminal device monitors the sending status of the data packet. After the terminal device monitors a data packet successfully sent to the first network device (for example, marked as data packet A), if the terminal device monitors a data packet successfully sent to the first network device (for example, marked as data packet B) , the terminal device determines that data packet A is not the last data packet sent successfully, and the terminal device continues to monitor whether the data packets after data packet B are successfully sent, and so on, until the terminal device monitors that it cannot continue to send data packets to the first network device Send subsequent data packets (such as denoted as data packet D, data packet E, data packet F, etc.).
  • the terminal device determines the data packet C' as the last data packet successfully sent by the terminal device to the first network device.
  • the data packet C and the data packet B may be the same data packet, or may be different data packets, such as a data packet sent after the data packet B.
  • the terminal device monitors a data packet (as denoted as data packet A) successfully sent to the first network device, if the terminal device monitors that it cannot continue to send subsequent data packets to the first network device (as denoted as data packet A).
  • packet B, data packet C, data packet D, etc. the terminal device determines that data packet A is the last data packet successfully sent by the terminal device to the first network device. It can also be understood that the subsequent adjacent data packets of the last data packet successfully sent by the terminal device to the first network device are data packets that failed to be sent.
  • the terminal device successfully receives the last data packet from the first network device.
  • the terminal device successfully receives the last data packet from the first network device, and the specific process includes: the terminal device monitors the receiving status of the data packet. After the terminal device monitors a successfully received data packet from the first network device (as denoted as data packet A), if the terminal device monitors a successfully received data packet from the first network device (as denoted as data packet B), the terminal device determines that data packet A is not the last data packet successfully received, and the terminal device continues to monitor whether the data packet after data packet B is successfully received, and so on, until the terminal device monitors that it can no longer continue to receive subsequent data Packets (such as denoted as data packet D, data packet E, data packet F, etc.).
  • the terminal device determines the data packet C' as the last data packet from the first network device successfully received by the terminal device.
  • the data packet C and the data packet B may be the same data packet, or may be different data packets, such as a data packet from the first network device successfully received after the data packet B.
  • the terminal device monitors a successfully received data packet (as marked as data packet A) from the first network device, if the terminal device monitors that it cannot continue to receive subsequent data packets (as marked as data packet B, data packet C, data packet D, etc.), then the terminal device determines that data packet A is the last data packet from the first network device successfully received by the terminal device. It can also be understood that the subsequent adjacent data packets of the last data packet from the first network device successfully received by the terminal device are data packets that fail to be received.
  • the termination flag of user plane transmission interruption includes one of the following:
  • the terminal device successfully sends the first data packet to the second network device.
  • the terminal device successfully receives the first data packet from the second network device.
  • the start identifier and the end identifier can be combined arbitrarily.
  • the user plane transmission interruption duration may refer to the duration between the terminal device successfully sending the last data packet to the first network device and the terminal device successfully sending the first data packet to the second network device.
  • the starting identifier indicated by the indication information is the aforementioned starting identifier 1a.
  • the termination identifier indicated by the indication information is the above termination identifier 1a.
  • the user plane transmission interruption duration may refer to the duration between the terminal device successfully sending the last data packet to the first network device and the terminal device successfully sending the first data packet to the second network device.
  • the starting identifier indicated by the indication information is the aforementioned starting identifier 1a.
  • the termination identifier indicated by the indication information is the above termination identifier 2a.
  • the user plane transmission interruption duration may refer to the duration between the terminal device successfully receiving the last data packet from the first network device and the terminal device successfully sending the first data packet to the second network device.
  • the starting identifier indicated by the indication information is the aforementioned starting identifier 2a.
  • the termination identifier indicated by the indication information is the above termination identifier 1a.
  • the user plane transmission interruption duration may refer to the duration between the terminal device successfully receiving the last data packet from the first network device and the terminal device successfully sending the first data packet to the second network device.
  • the starting identifier indicated by the indication information is the aforementioned starting identifier 2a.
  • the termination identifier indicated by the indication information is the above termination identifier 2a.
  • the start identifier of user plane transmission interruption includes one of the following:
  • a downlink out-of-sync (out-of-sync) occurs between the terminal device and the first network device.
  • RLF occurs between the terminal device and the first network device.
  • the terminal device determines that the timer T310 (or the timer T312) expires, it determines that RLF occurs with the first network device.
  • the process for the terminal device to determine that the RLF occurs may refer to related prior art, which will not be repeated here.
  • Start mark 3b start the second timer.
  • the running duration of the second timer indicates the duration during which the terminal device detects that there is a physical layer problem with the first network device.
  • the second timer may be the above-mentioned timer T310.
  • Start mark 4b start the third timer.
  • the running duration of the third timer indicates the duration between when the terminal triggers the measurement report and when the terminal device and the first network device resume synchronization during the running period of the third timer.
  • the third timer may be the above-mentioned timer T312.
  • the terminal device With the start identifier 5b, the terminal device has successfully received the repeated data packet.
  • the termination flag of the interrupt timer includes one of the following:
  • Termination flag 2b the terminal device sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to complete.
  • Termination flag 3b downlink synchronization between the terminal device and the second network device.
  • the sign 4b is terminated, and the second timer is stopped.
  • the sign 5b is terminated, and the third timer is stopped.
  • the start identifier and the end identifier can be combined arbitrarily.
  • the user plane transmission interruption duration may refer to the duration between the start of the second timer and the stop of the second timer.
  • the start identifier indicated by the indication information is the above start identifier 3b.
  • the termination identifier indicated by the indication information is the above termination identifier 4b.
  • the start identifier and the end identifier may also have other combinations, which will not be listed here. It is easy to understand that, the start identifier and the end identifier between the above first possible implementation manner and the second possible implementation manner may also be combined arbitrarily.
  • the user plane transmission interruption duration may refer to the duration between when the terminal device successfully sends the last data packet to the first network device and when the second timer stops.
  • the starting identifier indicated by the indication information is the aforementioned starting identifier 1a.
  • the termination identifier indicated by the indication information is the above termination identifier 4b.
  • the specific implementation process of S301 includes but is not limited to the following two methods (the following methods 1 and 2):
  • Mode 1 as shown in the dotted box where "mode 1" is located in Figure 4, the first network device executes S301a:
  • the first network device determines indication information.
  • the first network device determines the value of the first threshold.
  • the first network device starts from the above start identifiers 1a-2a (or start identifiers 1b-5b, or start identifiers 1a-2a and Among the start identifiers 1b to 5b), the start identifier indicated by the indication information is determined.
  • the indication information also indicates the termination identifier of the user plane transmission interruption
  • the first network device selects from the above termination identifiers 1a-2a (or termination identifiers 1b-5b, or termination identifiers 1a-2a and termination identifiers 1b-5b), Determine the termination identifier indicated by the indication information.
  • the second network device determines indication information.
  • the second network device determines the indication information autonomously.
  • the implementation process of S301b refer to the introduction of S301a.
  • the difference is that the execution subject of S301a is the first network device, and the execution subject of S301b is the second network device, which will not be repeated here.
  • the second network device sends indication information to the first network device.
  • the first network device receives the indication information from the second network device.
  • the indication information may be carried in the HO request confirmation message, or carried in other messages, or may be transmitted separately.
  • the indication information may be transmitted simultaneously with the HO request confirmation message, or may be transmitted before the HO request confirmation message, which is not limited in this embodiment of the present application.
  • the HO request confirmation message may be a DAPS handover request confirmation message, for details, please refer to the introduction of S205, which will not be repeated here.
  • the HO request confirmation message includes the RRC reconfiguration message.
  • the indication information is carried in the HO request confirmation message, and there are two implementation methods: in the first implementation manner, the indication information is carried in the RRC reconfiguration message; in the second implementation manner, the indication information is carried outside the RRC reconfiguration message, And carried in the HO request confirmation message.
  • the indication information may be carried in the SHR trigger condition, and may also be independent of the SHR trigger condition, such as the indication information is carried outside the SHR trigger condition, and carried In the RRC reconfiguration message, this embodiment of the present application does not limit it.
  • the introduction of the SHR triggering condition can refer to the introduction of the SHR in the explanation of terms, and will not be repeated here.
  • the second network device determines the indication information based on the reference information.
  • the communication method 300 in this embodiment of the present application further includes:
  • the first network device sends information A to the second network device.
  • the second network device receives information A from the first network device.
  • the information A includes reference information (as shown in the box of "mode 1" in Fig. 5a) and/or request information (as shown in the box of "mode 2" in Fig. 5a).
  • the introduction is made by taking information A including reference information as an example, and the reference information indicates the initial threshold determined by the first network device.
  • the reference information further indicates an initial identifier determined by the first network device, such as an initial start identifier, an initial end identifier, and the like.
  • the first network device determines what is indicated by the reference information from the aforementioned initial identifiers 1a-2a (or initial identifiers 1b-5b, or initial identifiers 1a-2a and initial identifiers 1b-5b), and uses The starting identifier for the second network device reference.
  • the reference information also indicates the start identifier that the user plane transmission is interrupted and used for reference by the second network device.
  • the first network device determines from the above-mentioned termination identifiers 1a ⁇ 2a (or termination identifiers 1b ⁇ 5b, or termination identifiers 1a ⁇ 2a and termination identifiers 1b ⁇ 5b) indicated by the reference information, and uses them in the second network The termination identifier for the device reference.
  • the reference information also indicates that the user plane transmission is interrupted and is used for a termination identifier referred to by the second network device.
  • the reference information may be carried in the HO request message, may also be carried in other messages, and may also be transmitted separately. In terms of transmission time, the reference information may be transmitted simultaneously with the HO request message, or may be transmitted before the HO request message, which is not limited in this embodiment of the present application.
  • the HO request message may be a DAPS handover request message, for details, please refer to the introduction of S203, which will not be repeated here.
  • the indication information in S301c is transmitted simultaneously with the HO request confirmation message.
  • the indication information in S301c may be transmitted simultaneously with the HO request confirmation message, or may be transmitted before the HO request confirmation message, which is not limited in the example of this application.
  • the specific implementation process of S301b includes: the second network device determines the indication information based on the reference information.
  • the reference information in S301b is consistent with the reference information in S301d.
  • the reference information indicates at least one initial threshold.
  • the second network device modifies an initial threshold indicated by the reference information, and uses the modified value as the first threshold.
  • the second network device may not make any modification, and use an initial threshold indicated by the reference information as the first threshold indicated by the indication information, which is not limited in this embodiment of the present application.
  • the reference information indicates at least two initial thresholds. The second network device selects an initial threshold from at least two initial thresholds indicated by the reference information as the first threshold.
  • the second network device modifies a certain start identifier indicated by the reference information, and uses the modified start identifier as the one indicated by the indication information. Start ID.
  • the second network device may not make any modification, and use an initial start identifier indicated by the reference information as the start identifier indicated by the indication information, which is not limited in this embodiment of the present application.
  • the second network device selects one of the at least two start identities indicated by the reference information as the start identities indicated by the indication information.
  • the second network device modifies a certain termination identifier indicated by the reference information, and uses the modified termination identifier as the termination identifier indicated by the indication information.
  • the second network device may not make any modification, and use an initial termination identifier indicated by the reference information as the termination identifier indicated by the indication information, which is not limited in this embodiment of the present application.
  • the second network device selects one of the at least two termination identities indicated by the reference information as the termination identifier indicated by the indication information.
  • the information A includes the request information as an example for introduction, and the request information requests the second network device to configure the indication information. That is to say, if the first network device does not execute S301a, the first network device requests the second network device to configure the indication information.
  • the specific implementation process of S301b includes: the second network device determines the indication information according to the request information. That is to say, the second network device configures the indication information only in response to the request information, so as to simplify the processing complexity of the second network device.
  • the communication method 300 in this embodiment of the present application further includes S301e and S301f.
  • the first network device may execute S301f first (as described in case 1), and the first network device may also execute S301e and S301f first.
  • the introduction of S301e and S301f is as follows:
  • the first network device sends the information X to the second network device.
  • the second network device receives the information X from the first network device.
  • the information X is used to request the second network device to feed back whether it supports the SHR function.
  • Supporting the SHR function can be understood as having at least one of the ability to receive the SHR, identify the SHR, send the SHR to other network devices, or read information in the SHR.
  • the first network device executes S301e before sending the HO request message.
  • the second network device sends information Y to the first network device.
  • the first network device receives information Y from the second network device.
  • the information Y indicates whether the second network device supports the SHR function.
  • the second network device executes S301e, it determines information Y according to information X and its own device capability, and then executes S301f.
  • the second network device may not be able to recognize the information X in S301e, and it may not carry any information indicating the SHR function in S301f, that is, if the information X in step S301f does not carry
  • the information supporting the SHR function may also be understood as that the second network device does not support the SHR function.
  • the first network device can know whether the second network device supports the SHR function. In the case that the information Y indicates that the second network device supports the SHR function, the first network device executes S301d or S301a, so as to configure the indication information. On the contrary, if the information Y indicates that the second network device does not support the SHR function, the first network device does not perform S301d and S301a, thereby avoiding wasting transmission resources.
  • the first network device may not execute S301e and S301f, but directly execute S301d or S301a.
  • the second network device supports the SHR function
  • the second network device if the second network device executes S301d, the second network device can successfully receive and identify information A, and determine the indication information based on information A.
  • the second network device does not support the SHR function
  • the second network device cannot recognize the information A.
  • the second network device does not execute SS301b and S301c, and the first network device does not execute S301a.
  • the first network device may execute S301f but not execute S301e. That is to say, the second network device actively provides whether it supports the SHR function to the first network device, so that the first network device knows whether the second network device supports the SHR function, and avoids waste of transmission resources caused by the transmission of information A.
  • the first network device may execute S301e and S301f. That is to say, the second network device executes S301f only in response to the request of the first network device, so as to simplify the processing complexity of the second network device.
  • the first network device sends indication information to the terminal device.
  • the terminal device receives the indication information from the first network device.
  • the indication information in S302 is consistent with the indication information in S301.
  • the indication information can be carried in the RRC reconfiguration message, and can also be carried in other messages (such as RRC Setup (RRCSetup) message, RRC Reestablishment (RRCReestablishment) message, RRC Recovery (RRCResume) message, or system message) can also be transmitted separately.
  • RRC Setup RRCSetup
  • RRCReestablishment RRC Reestablishment
  • RRCResume RRC Recovery
  • the indication information can be transmitted simultaneously with the RRC reconfiguration message, or can be transmitted before the RRC reconfiguration message, such as through an RRC establishment message, an RRC re-establishment message, an RRC recovery message, or a system message Transmission, which is not limited in this embodiment of the application.
  • the indication information in S302 is transmitted simultaneously with the RRC reconfiguration message.
  • the indication information in S302 may be transmitted simultaneously with the RRC reconfiguration message, or may be transmitted before the RRC reconfiguration message, which is not limited in the example of this application.
  • the terminal device When the user plane transmission interruption duration is greater than or equal to a first threshold during the handover process, the terminal device records a first report.
  • the first report indicates the duration of user plane transmission interruption.
  • the first report includes a preset number of bits, and the first report indicates the user plane transmission interruption duration by using the preset number of bits.
  • the first report also indicates at least one of the following:
  • the first item is the reason for triggering the recording of the first report, such as the user plane transmission interruption duration is greater than or equal to the first threshold, or the running duration of timer T310 is greater than or equal to the threshold corresponding to timer T310, or the running duration of timer T312 is greater than Or equal to the threshold corresponding to the timer T312.
  • the second item is the start identifier of the user plane transmission interruption.
  • the third item is the stop flag of user plane transmission interruption.
  • the fourth item is the wireless network temporary identifier (CRNTI) of the source cell.
  • the fifth item is the number of repeated received packets.
  • the terminal device receives repeated data packets, and records the number of repeatedly received data packets.
  • the sixth item is the proportion of data packets received repeatedly.
  • the terminal device receives repeated data packets (for example, marked as the first data packet) and non-repeated data packets (for example, marked as the second data packet), And record the number of first data packets (for example, denoted as x data packets) and the quantity of second data packets (for example, denoted as y data packets).
  • the ratio of repeated received data packets satisfies the following formula (1) or formula (2):
  • K represents the proportion of repeatedly received data packets
  • x represents the quantity of the first data packets
  • y represents the quantity of the second data packets.
  • K represents the proportion of repeatedly received data packets
  • x represents the quantity of the first data packets
  • y represents the quantity of the second data packets.
  • the above items 1 to 4 are applicable to the case where the start flag and end flag of user plane transmission interruption are implemented as the first possible implementation and the second possible implementation, see S301 for details The introduction will not be repeated here.
  • the fifth and sixth items above are applicable to the case where the user plane transmission interruption start identifier and end identifier are implemented as the second possible implementation manner, see the introduction of S301 for details, and will not be repeated here.
  • the number (or proportion) of repeatedly received data packets can represent the degree of unreasonable data scheduling of the first network device. For example, the higher the degree of unreasonable data scheduling of the first network device, the greater the number of repeatedly received data packets, and the higher the proportion of reconnected received data packets.
  • the first report may also have another name, such as SHR, which is not limited in this embodiment of the present application. In this embodiment of the application, only the first report is used as an example for introduction.
  • the specific implementation process of S303 may include but not limited to the following introduction: when the running duration of the first timer is greater than or equal to the first threshold, the terminal device records the first report.
  • the running duration of the first timer indicates the user plane transmission interruption duration. That is to say, the start identifier of the first timer is the same as the start identifier of the user plane transmission interruption duration. For example, when RLF occurs between the terminal device and the first network device, the first timer is started. The stop identifier of the first timer is the same as the termination identifier of the user plane transmission interruption duration. For example, when the terminal device successfully sends the first data packet to the second network device, the first timer stops. If the first timer has been running and the running time exceeds the first threshold, the terminal device records the first report.
  • the first timer may also be described by other names, such as an interruption timer (interruption timer), which is not limited in this embodiment of the present application.
  • the first threshold can also be described as an interruption timer threshold (interruption timer threshold).
  • the first threshold can also have other names. This is not limited.
  • the first timer and the first threshold are taken as examples for introduction.
  • the terminal device may also use other methods to record the user plane transmission interruption duration, for example, the terminal device itself records a duration, which is not limited in this embodiment of the present application.
  • the terminal device sends the first report to the first network device.
  • the first network device receives the first report from the terminal device.
  • the first report in S304 is consistent with the first report in S303.
  • the implementation process of S304 includes but not limited to the following three ways:
  • the terminal device directly sends the first report to the first network device.
  • the first network device directly receives the first report from the terminal device.
  • the implementation process of S304 includes two steps 1a and 2a:
  • Step 1a the terminal device sends a first report to the second network device.
  • the second network device directly receives the first report from the terminal device.
  • Step 2a the second network device sends the first report to the first network device.
  • the first network device receives the first report from the second network device.
  • the second network device may send the first report to the first network device through the interface between the second network device and the first network device, or the second network device may send the first report to the first network device through the core network device first report.
  • Mode 3 the implementation process of S304 includes two steps 1b and 2b:
  • Step 1b the terminal device sends a first report to the third network device.
  • the third network device directly receives the first report from the terminal device.
  • the third network device is a network device other than the first network device and the second network device.
  • the third network device supports the SHR function, and can perform information exchange with the terminal device.
  • SHR function For the introduction of the SHR function, refer to the introduction of the S301e, which will not be repeated here.
  • Step 2b the third network device sends the first report to the first network device.
  • the first network device receives the first report from the third network device.
  • the third network device may send the first report to the first network device through the interface between the third network device and the first network device, or the third network device may send the first report to the first network device through the core network device first report.
  • manner 1, manner 2, and manner 3 in S304 are only exemplary introductions to the transmission process of the first report.
  • the terminal device may also use other methods to provide the first report to the first network device, which is not limited in this embodiment of the present application.
  • the terminal device may not perform S304 after performing S303, that is, the terminal device does not send the first report.
  • the terminal device deletes the above-mentioned first report, so as to save storage resources of the terminal device.
  • the first network device determines network optimization parameters according to the first report.
  • the first network device may optimize the mobility of the terminal device in combination with the first report and the context of the terminal device, so as to obtain network optimization parameters, so as to optimally handle the problem of potential mobility failure.
  • the indication information indicates the first threshold
  • the terminal device records the first report when the user plane transmission interruption duration is greater than or equal to the first threshold.
  • the first report includes the user plane transmission interruption duration. Even if the terminal device successfully connects to the second network device, but the terminal device has a phenomenon of user plane transmission interruption during the handover process, the first report can also record the length of the user plane transmission interruption, avoiding the problem that the terminal device cannot record the report in the prior art, It also lays the foundation for determining the optimization parameters on the network side.
  • the interruption of user plane transmission between the terminal device and the network device can be described as, during the DAPS handover process, the transmission between the terminal device and the source network device
  • User plane transmission interruption can also be described as, during the DAPS handover process, the user plane transmission between the terminal device and the source network device is interrupted, and no user plane transmission is performed between the terminal device and the target network device.
  • the first communication method 300 in the embodiment of the present application may also be applicable to other scenarios, such as a dual-connectivity (DC) scenario, that is, a terminal device establishes communication connections with two network devices at the same time.
  • the above two network devices include a primary network device (such as a master station (master gNB, MgNB)) and a secondary network device (such as a secondary station (secondary gNB, SgNB)).
  • master gNB master station
  • MgNB master station
  • secondary gNB secondary gNB
  • the above-mentioned first network device may be the source master station
  • the second network device may be the target master station.
  • the specific implementation process please refer to the introduction of the communication method 300, which will not be repeated here.
  • the above-mentioned first network device may be a source secondary station, and the second network device may be a target secondary station.
  • the specific implementation process may refer to the introduction of the communication method 300 , which will not be repeated here.
  • the trigger condition of the first report is "duration of user plane transmission interruption during handover is greater than or equal to the first threshold" as an example for description.
  • the embodiment of the present application also provides a fifth communication method.
  • the terminal device receives a trigger condition from the first network device.
  • the trigger condition at least includes that RLF occurs between the terminal device and the first network device during the handover process.
  • the terminal device records the SHR.
  • the SHR at least indicates the trigger condition that the terminal device satisfies.
  • the terminal device will record this situation, that is, the above-mentioned SHR at least indicates the trigger condition that the terminal device satisfies, so as to indicate that the terminal device and the first network device.
  • the occurrence of RLF between them avoids the problem that the terminal equipment cannot record in this case in the prior art, and also lays a foundation for determining the optimization parameters on the network side.
  • the fifth communication method 1300 provided by the embodiment of the present application includes the following steps:
  • the first network device acquires a trigger condition.
  • the trigger condition includes at least one of the following:
  • the first item is that the duration of user plane transmission interruption is greater than or equal to the first threshold.
  • the interruption of user plane transmission and the first threshold reference may be made to the introduction of the first communication method 300 in the embodiment of the present application, which will not be repeated here.
  • the second item is that RLF occurs between the terminal device and the first network device during the handover process.
  • RLF occurs between the terminal device and the first network device during the handover process, which may also be replaced by: RLF occurs between the terminal device and the first network device before successful random access is completed between the terminal device and the second network device.
  • the determination process is as follows: the second trigger condition may be determined by the first network device or by the second network device, and then the second network device sends the first network device Send message 1.
  • the first network device receives information 1 from the second network device.
  • the information 1 indicates that the trigger condition includes that RLF occurs between the terminal device and the first network device during the handover process.
  • the message carried by the information 1 and the time of transmission refer to the introduction of the indication information in S301c, which will not be repeated here.
  • the trigger condition may also have other names, which are not limited in this embodiment of the present application.
  • the above trigger conditions may also include SHR trigger conditions, see the introduction of SHR trigger condition for details, and details will not be repeated here.
  • the first network device sends a trigger condition to the terminal device.
  • the terminal device receives the trigger condition from the first network device.
  • the trigger condition in S1302 is consistent with the trigger condition in S1301.
  • the terminal device records the SHR.
  • the SHR at least indicates the trigger condition that the terminal device satisfies, and can also be understood as the reason for triggering and recording the SHR.
  • the following is an introduction to the indication method of SHR:
  • the SHR may directly indicate the trigger condition met by the terminal device. For example, in the case that the duration of user plane transmission interruption is greater than or equal to the first threshold, the SHR directly indicates that the duration of user plane transmission interruption is greater than or equal to the first threshold. For another example, in the case that RLF occurs between the terminal device and the first network device during the handover process, the SHR directly indicates that RLF occurs between the terminal device and the first network device during the handover process.
  • the SHR may also indirectly indicate the trigger condition that the terminal device satisfies.
  • the corresponding relationship between various trigger conditions and numbers is shown in Table 2.
  • the SHR directly indicates the number "0".
  • the SHR directly indicates the number "1".
  • the duration of user plane transmission interruption is greater than or equal to the first threshold 1 RLF occurs between the terminal device and the first network device during handover
  • the SHR indicates the trigger condition that the terminal device satisfies.
  • the SHR can also indicate the trigger condition that the terminal device satisfies in other ways, which is not limited in this embodiment of the present application. .
  • the implementation process of S1303 is as follows:
  • the terminal device determines that the trigger condition is satisfied. In this case, the end device records the SHR. Wherein, the SHR indicates that RLF occurs between the terminal device and the first network device during the handover process.
  • the above trigger condition may also include the SHR trigger condition.
  • the terminal device executes S1303, the terminal device still records the SHR.
  • the SHR may indicate the reason for the occurrence of the RLF.
  • the reasons for RLF include at least one of the following:
  • the second timer expires.
  • the running duration of the second timer indicates the duration during which the terminal device detects that there is a physical layer problem with the first network device.
  • the second timer may be the above-mentioned timer T310.
  • the second item beam failure recovery failure.
  • the third item random access failure.
  • the fourth item is the maximum number of retransmissions.
  • a data packet at the radio link control (radio link control, RLC) layer reaches the maximum number of retransmissions, resulting in RLF.
  • LBT listen before talk
  • the introduction of LBT is as follows: on an unlicensed frequency band, channel availability cannot be guaranteed at all times. Before transmitting uplink data, the terminal device performs an idle channel assessment to ensure that the uplink data is transmitted when the channel is idle. If the LBT is successful, the terminal device transmits uplink data. If the LBT fails, the terminal device will give up transmitting the current uplink data, and then transmit the uplink data when the channel is idle.
  • the sixth item the backhaul link RLF recovery failure (backhaul (BH) RLF recovery failure).
  • the terminal device is an IAB mobile terminal (IAB mobile terminal, IAB-MT), if it receives the backhaul link adaptation protocol stack
  • the backhaul link RLF indication sent by the (backhaul adaptation protocol, BAP) entity determines that the cause of the RLF is BH RLF recovery failure.
  • the SHR may indicate one or more of the above six reasons, thereby indicating that RLF occurs between the terminal device and the first network device during the handover process.
  • the SHR also indicates random access information.
  • the random access information that causes RLF between the first network device and the first network device Exemplarily, the random access information indicated by the SHR includes at least one of the following:
  • the first item is the absolute frequency point position.
  • the absolute frequency point position indicates a reference point in the frequency domain, so as to improve resource allocation flexibility.
  • the absolute frequency point position may be Point A.
  • the second item is the frequency domain position of the physical random access channel (PRACH).
  • the PRACH is used for random access, that is, the terminal equipment accesses through the PRACH.
  • the frequency domain position of the PRACH is relative to the PRACH resource position indicated by the absolute frequency point position.
  • the frequency domain position of the PRACH is a preset number of RBs starting from the 15th resource block (resource block, RB), which can be understood as taking the absolute frequency position as the first RB and starting from the 15th RB The preset number of RBs all belong to the resource location where the PRACH is located.
  • the third item is the bandwidth of PRACH.
  • the bandwidth of the PRACH is 10 RBs, or other number of RBs, which is not limited in this embodiment of the present application.
  • the fourth item is the subcarrier spacing of PRACH.
  • the subcarrier spacing of the PRACH is 15 kHz, or 30 kHz, or other values, which is not limited in this embodiment of the present application.
  • the SHR may indicate one item of the above information, for example, the SHR indicates the bandwidth of the PRACH, or indicates the subcarrier spacing of the PRACH.
  • the SHR may indicate two items of the above information, for example, the SHR indicates the absolute frequency point position and the frequency domain position of the PRACH, or the SHR indicates the bandwidth and subcarrier spacing of the PRACH, or other combinations, which are not limited in this embodiment of the present application .
  • the information to be accessed at any time may also include other information, such as the number of PRACH transmission occasions of frequency-division multiplexing (FDM) at the same time, which is not limited in the embodiment of the present application .
  • FDM frequency-division multiplexing
  • the terminal device sends the SHR to the first network device.
  • the first network device receives the SHR from the terminal device.
  • the SHR in S1304 is consistent with the SHR in S1303.
  • the first network device determines network optimization parameters according to the SHR.
  • the terminal device records this situation, that is, the above-mentioned SHR at least indicates the trigger condition that the terminal device satisfies, so as to indicate that the terminal device RLF occurs between the device and the first network device, which avoids the problem that the terminal device cannot record in this case in the prior art, and also lays a foundation for the network side to determine optimization parameters.
  • the terminal device records the RLF report. If the terminal device is configured with SHR trigger conditions at the same time (see the introduction of SHR trigger conditions in the glossary section for details), and the SHR trigger conditions are met, the terminal device will also record SHR. That is to say, the terminal device records the RLF report and the SHR for the same mobility anomaly (such as the aforementioned RLF). Among them, some mobility parameters in the RLF report and the SHR are repeated.
  • the source network device determines the network optimization parameters based on the RLF report and the SHR respectively, and adjusts the same mobility parameter based on the network optimization parameters respectively determined by the RLF report and the SHR, As a result, the same mobility parameter is adjusted twice, which easily leads to the problem of over-adjustment.
  • the mobility parameter includes a handover threshold
  • the initial value of the handover threshold is XdB.
  • the source network device determines that the handover threshold is lowered by 0.5 dB based on the RLF report.
  • the source network device reduces the initial value XdB of the handover threshold by 0.5dB based on the network optimization parameters determined by the RLF report, so the handover threshold is adjusted to (X-0.5)dB.
  • the source network device determines that the handover threshold is reduced by 0.5 dB to meet the mobility index.
  • the source network device determines the adjusted value of the handover threshold (X-0.5) dB, and then reduces it by 0.5 dB again. In this way, the handover threshold is adjusted to (X-0.5-0.5) dB , causing the problem of over-adjustment.
  • the embodiment of the present application provides a second communication method and a third communication method.
  • the terminal device when the terminal device detects RLF with the source cell during the DAPS handover process and completes the DAPS handover with the target cell, the terminal device OK first report.
  • the first report includes a report to be recorded indicated by a preset condition, or the first report includes a report to be reported indicated by a preset condition.
  • the preset conditions include at least one of the following: the first item, only record the SHR; the second item, only record the RLF report; the third item, only report the SHR; the fourth item, only report the RLF report.
  • the terminal device records the first report that satisfies the preset condition.
  • the terminal device only records one of the RLF report and the SHR report, or the terminal device only reports the RLF report and the SHR report.
  • One kind of report the network side can obtain a report (such as the above-mentioned SHR or RLF report), so as to avoid the problem of over-adjustment.
  • the second communication method 600 includes the following steps:
  • the terminal device determines a first report.
  • the first report includes a report to be recorded indicated by a preset condition, or the first report includes a report to be reported indicated by a preset condition.
  • Preconditions include at least one of the following:
  • the first item only records the SHR.
  • the specific implementation process of only recording the SHR includes: when the RLF occurs, the terminal device records the RLF report. When the trigger condition of the SHR is met, the terminal device records the SHR. After a period of time, or while the terminal device is recording the SHR report, the terminal device deletes the RLF report.
  • the second item only records RLF reports.
  • the specific implementation process of only recording the RLF report includes: when the RLF occurs, the terminal device records the RLF report. When the trigger condition of the SHR is satisfied, the terminal device does not record the SHR.
  • the specific implementation process of only recording the RLF report includes: when the RLF occurs, the terminal device records the RLF report. When the trigger condition of the SHR is met, the terminal device records the SHR. The end device then deletes the SHR.
  • the third item only report SHR.
  • the end device records the SHR.
  • the terminal device may or may not record the RLF report, which is not limited in this embodiment of the present application.
  • the terminal device does not report the RLF report, or, after a period of time, the terminal device deletes the RLF report.
  • the fourth item only report the RLF report.
  • the end device records the RLF report.
  • the terminal device may or may not record the SHR, which is not limited in this embodiment of the present application.
  • the terminal device does not report the SHR, or, after a period of time, the terminal device deletes the SHR.
  • the preset condition may be preconfigured or received from the network side, which is not limited in this embodiment of the present application.
  • the communication method 600 in this embodiment of the present application further includes S602 and S603:
  • the first network device acquires a preset condition.
  • the preset condition in S602 is consistent with the preset condition in S601 , which will not be repeated here.
  • Mode 1 as shown in the dotted box where "mode 1" is located in Figure 7, the first network device executes S602a:
  • the first network device determines a preset condition.
  • the first network device determines whether to record only SHR, or whether to record only RLF report, or whether to report only SHR, or whether to report only RLF report.
  • Mode 2 as shown in the dotted line box of "mode 2" in Figure 7, the second network device executes S602b and S602c:
  • the second network device determines a preset condition.
  • the second network device determines the preset condition autonomously.
  • the implementation process of S602b refer to the introduction of S602a.
  • the difference is that the execution subject of S602a is the first network device, and the execution subject of S602b is the second network device, which will not be repeated here.
  • the second network device sends the preset condition to the first network device.
  • the first network device receives the preset condition from the second network device.
  • the preset condition may be carried in the HO request confirmation message, may also be carried in other messages, and may also be transmitted separately.
  • the preset condition may be transmitted simultaneously with the HO request confirmation message, or may be transmitted before the HO request confirmation message, which is not limited in this embodiment of the present application.
  • the HO request confirmation message includes the RRC reconfiguration message.
  • the preset condition is carried in the HO request confirmation message, and there are two implementations: in the first implementation, the preset condition is carried in the RRC reconfiguration message; in the second implementation, the preset condition is carried in the RRC In addition to the reconfiguration message, it is carried in the HO request confirmation message.
  • the first network device sends the preset condition to the terminal device.
  • the terminal device receives the preset condition from the first network device.
  • the preset condition in S603 is consistent with the preset condition in S602.
  • the preset condition may be carried in an RRC reconfiguration message, or may be carried in other messages (such as an RRC establishment message, an RRC re-establishment message, an RRC recovery message, or a system message), or Can be transferred separately.
  • the preset condition can be transmitted simultaneously with the RRC reconfiguration message, or can be transmitted before the RRC reconfiguration message, such as through RRC establishment message, RRC re-establishment message, RRC recovery message, or system message transmission. The embodiment of the application does not limit this.
  • the preset condition in S603 is transmitted simultaneously with the RRC reconfiguration message.
  • the preset condition in S603 can be transmitted simultaneously with the RRC reconfiguration message, or can be transmitted before the RRC reconfiguration message, which is not limited in the example of this application .
  • the second communication method 600 of the embodiment of the present application further includes S604 and S605:
  • the first report in S604 is consistent with the first report in S601.
  • the first network device determines network optimization parameters according to the first report.
  • the preset condition indicates a report to be recorded by the terminal device, or a report to be reported by the terminal device.
  • the terminal device determines the first report that meets the preset condition.
  • the terminal device only records one of the RLF report and the SHR report, or the terminal device only reports one of the RLF report and the SHR report.
  • the network side A report (such as the above SHR, or RLF report) can be obtained, thereby avoiding the problem of over-adjustment.
  • the first network device when the terminal device detects RLF with the source cell during DAPS handover and completes the DAPS handover with the target cell, the first network device Receive RLF reports and SHRs from end devices.
  • the RLF report and the SHR include mobility parameters of the same mobility anomaly.
  • the first network device determines the network optimization parameters according to the SHR, or the first network device determines the network optimization parameters according to the RLF report, or the first network device determines the network optimization parameters according to the SHR and the RLF report, so as to avoid the first network device based on the same mobility exception
  • the RLF report and SHR respectively determine the network optimization parameters, thus solving the problem of over-tuning.
  • the third communication method 800 provided by the embodiment of the present application includes the following steps:
  • the terminal device determines the RLF report and the SHR.
  • the RLF report and the SHR include mobility parameters in the RLF process, and the implementation process of S801 can refer to related prior art, and will not be repeated here.
  • the terminal device sends the RLF report and the SHR to the first network device.
  • the first network device receives the RLF report and the SHR from the terminal device.
  • the RLF report in S802 is consistent with the RLF report in S801
  • the SHR in S802 is consistent with the SHR in S801.
  • the first network device After executing S802, the first network device executes one of S803a, S803b, and S803c.
  • the descriptions of S803a, S803b and S803c are as follows:
  • the first network device determines network optimization parameters according to the SHR.
  • the first network device uses the SHR to determine the network optimization parameters, and does not use the RLF report to determine the network optimization parameters.
  • the initial value of the handover threshold is XdB.
  • the first network device determines based on the SHR that the handover threshold can be satisfied by reducing the handover threshold by 0.5 dB, and the network optimization parameter determined based on the SHR is -0.5 dB. Based on the initial value XdB of the handover threshold, the first network device reduces the handover threshold by 0.5dB, so the handover threshold is adjusted to (X-0.5)dB. Since the first network device does not use the RLF report to determine the network optimization parameters, there is no problem of over-adjustment.
  • the first network device determines network optimization parameters according to the RLF report.
  • the first network device uses the RLF report to determine the network optimization parameters, and does not use the SHR to determine the network optimization parameters.
  • the initial value of the handover threshold is XdB.
  • the first network device determines based on the RLF report that the handover threshold can be satisfied by reducing the handover threshold by 0.5 dB, and the network optimization parameter determined based on the RLF report is -0.5 dB. Based on the initial value XdB of the handover threshold, the first network device reduces the handover threshold by 0.5dB, so the handover threshold is adjusted to (X-0.5)dB. Since the first network device does not use the SHR to determine network optimization parameters, there is no problem of over-adjustment.
  • the first network device determines network optimization parameters according to the SHR and the RLF report.
  • the initial value of the handover threshold is XdB.
  • D represents the network optimization parameter
  • k 1 represents the weighting coefficient corresponding to the SHR
  • a represents the network optimization value determined based on the SHR
  • k 2 represents the weighting coefficient corresponding to the RLF report
  • b represents the network optimization value determined based on the RLF report.
  • the first network device determines the network optimization value a based on the SHR, and determines the network optimization value b based on the RLF report, and then, the first network device determines the network optimization parameter D based on formula (3).
  • the above formula (3) is only an exemplary calculation formula that the network optimization parameters satisfy.
  • the first network device can also determine the network optimization parameters based on SHR and RLF reports according to other calculation methods. The embodiment does not limit this.
  • the first network device determines the network optimization parameters according to the SHR, or the first network device determines the network optimization parameters according to the RLF report, or the first network device determines the network optimization parameters according to the RLF report, or the first network device
  • the network device determines the network optimization parameters based on the SHR and RLF reports, so as to avoid the phenomenon that the first network device determines the network optimization parameters based on the RLF report and the SHR of the same mobility anomaly, and adjusts the same mobility parameter twice, so as to solve the excessive adjustment problem.
  • the first network device when the first network device executes S803a, as shown in FIG. 9, the first network device also executes S804a:
  • the first network device discards the RLF report.
  • the RLF report in S804a is consistent with the RLF report in S802.
  • the first network device deletes the RLF report, so as to prevent the first network device from repeatedly using the RLF report to determine network optimization parameters.
  • the first network device may execute S803a first, and then execute S804a (as shown in FIG. 9 ), or execute S804a first, and then execute S803a (not shown in FIG. 9 ), or execute S803a and S804a (not shown in FIG. 9 ) at the same time. (not shown in FIG. 9 ), which is not limited in this embodiment of the present application.
  • the first network device when the first network device executes S803b, as shown in FIG. 10 , the first network device also executes S804b:
  • the first network device discards the SHR.
  • the SHR in S804b is consistent with the SHR in S802.
  • the first network device deletes the SHR, so as to prevent the first network device from repeatedly using the SHR to determine network optimization parameters.
  • the first network device may execute S803b first, and then execute S804b (as shown in FIG. 10 ), or execute S804b first, and then execute S803b (not shown in FIG. 10 ), or execute S803b and S804b (not shown in FIG. 10 ) at the same time. (not shown in FIG. 10 ), which is not limited in this embodiment of the present application.
  • the SHR may also be replaced by the first report in the first communication method 300 .
  • the first report in S601, the SHR in S801, S802, S803a, and S804c may be a report recorded when the user plane transmission interruption duration is greater than or equal to the first threshold during the handover process, and the first report includes
  • the duration of user plane transmission interruption refer to the introduction of the first communication method 300 for details, and details are not repeated here.
  • the target network device may or may not support the SHR feature. If the target network device does not support the SHR feature, the target network device does not support the terminal device to report the SHR.
  • the RRC reconfiguration message provided by the target network device to the source network device does not carry the SHR trigger condition. Since the source network device does not parse the RRC reconfiguration message, the source network device cannot know whether the target network device supports the SHR feature. How to make the source network device negotiate with the target network device whether to support the SHR feature is an urgent problem to be solved.
  • the embodiment of the present application provides a fourth communication method.
  • the first network device sends the first information to the second network device.
  • the first information is used to indicate at least one condition that triggers recording of the SHR.
  • the first network device receives second information from the second network device.
  • the second information indicates whether the second network device accepts one or more of the above at least one condition. In this way, the first network device can determine whether the second network device supports the SHR feature based on the second information.
  • the fourth communication method 1100 provided by the embodiment of the present application includes the following steps:
  • the first network device sends first information to the second network device.
  • the second network device receives the first information from the first network device.
  • the first information is used to indicate at least one condition that triggers recording of the SHR.
  • the first information includes at least one of the following:
  • the first item is the threshold of user plane transmission interruption duration.
  • For the introduction of the user plane transmission interruption duration refer to the description of S301, which will not be repeated here.
  • For the threshold of the user plane transmission interruption duration refer to the introduction of the first threshold in the first communication method 300, which will not be repeated here.
  • the second item the threshold of the first timer.
  • the running duration of the first timer indicates the duration for which the terminal device does not access the second network device after receiving the RRC reconfiguration message.
  • the first timer may be a timer T304.
  • the third item is the threshold of the second timer.
  • the running duration of the second timer indicates the duration during which the terminal device detects that there is a physical layer problem with the first network device.
  • the second timer may be a timer T310.
  • the fourth item is the threshold of the third timer.
  • the running duration of the third timer indicates the duration between when the terminal device triggers the measurement report and when the terminal device and the first network device resume synchronization during the running of the second timer.
  • the third timer may be a timer T312.
  • the first information may be carried in the HO request message, may also be carried in other messages, or may be transmitted separately.
  • the first information may be transmitted simultaneously with the HO request message, or may be transmitted before the HO request message, which is not limited in this embodiment of the present application.
  • the HO request message may be a DAPS handover request message, for details, please refer to the introduction of S203, which will not be repeated here.
  • the fourth communication method 1100 of the embodiment of the present application further includes S1103 and S1104:
  • the first network device sends information X to the second network device.
  • the second network device receives the information X from the first network device.
  • the information X is used to request the second network device to feed back whether it supports the SHR function.
  • the implementation process of S1103 refer to the introduction of S301e, which will not be repeated here.
  • the second network device sends information Y to the first network device.
  • the first network device receives information Y from the second network device.
  • the information Y indicates whether the second network device supports the SHR function.
  • S1104 refer to the introduction of S301f, and will not be repeated here.
  • the first network device can know whether the second network device supports the SHR function. In a case where the information Y indicates that the second network device supports the SHR function, the first network device performs S1101 to provide the second network device with the first information. On the contrary, when the information Y indicates that the second network device does not support the SHR function, the first network device does not perform S1101, so as to avoid wasting transmission resources.
  • the second network device sends second information to the first network device.
  • the first network device receives the second information from the second network device.
  • the second information indicates whether the second network device accepts one or more of the above at least one condition.
  • the second information when the second information indicates that the second network device does not accept one or more of the above at least one condition, the second information may further indicate a reason for the rejection. It should be understood that, in a case where the second information indicates that the second network device does not accept all the above at least one condition, the RRC reconfiguration message does not carry the condition for triggering the recording of the SHR.
  • the second information when the second network device accepts one or more of at least one condition carried in the first information, the second information further indicates at least one of the following:
  • the first item, the RRC reconfiguration message carries one or more of the above at least one condition. That is to say, the second network device explicitly informs the first network device of the carrying condition of the preset condition in the RRC reconfiguration message, such as whether the preset condition is carried in the RRC reconfiguration message, and the number of preset conditions carried.
  • the indication information carries information of one bit (bit) to indicate whether the preset condition is carried in the RRC reconfiguration message. For example, when the value of this bit is "1", it indicates that the RRC reconfiguration message carries the preset condition Set the condition, otherwise, when the value of this bit is "0", it means that the RRC reconfiguration message does not carry the preset condition.
  • the second item is the condition type that triggers the recording of SHR.
  • the condition type may refer to a user plane transmission interruption duration, a first timer, a second timer and a third timer.
  • the condition type indicated by the second information includes the user plane transmission interruption duration.
  • the condition type indicated by the second information includes the first timer.
  • the condition type indicated by the second information includes the second timer.
  • the condition type indicated by the second information includes the third timer.
  • the third item triggers the threshold of recording SHR.
  • the threshold indicated by the second information includes the threshold of user plane transmission interruption duration.
  • the threshold indicated by the second information includes the threshold of the first timer.
  • the threshold indicated by the second information includes the threshold of the second timer.
  • the threshold indicated by the second information includes the threshold of the third timer.
  • the second information may have other names, such as response messages, configuration confirmation messages, etc., which are not limited in this embodiment of the present application.
  • the second information is used as an example for introduction.
  • the second information may be transmitted simultaneously with the HO request confirmation message, or may be transmitted before the HO request confirmation message, which is not limited in this embodiment of the present application.
  • the HO request message may be a DAPS handover request message, for details, please refer to the introduction of S203, which will not be repeated here.
  • the second information is transmitted simultaneously with the HO request confirmation message, and in the case that the first information is transmitted before the HO request message, the second information can be confirmed with the HO request message
  • the message is transmitted at the same time, or before the HO request confirmation message, which is not limited in this embodiment of the present application.
  • the second network device accepts one or more of at least one condition carried in the first information, the second network device also performs S1105:
  • the second network device sends an RRC reconfiguration message to the first network device.
  • the first network device receives the RRC reconfiguration message from the second network device.
  • the RRC reconfiguration information carries one or more conditions.
  • the conditions carried in the RRC reconfiguration message belong to the conditions indicated in the first information, refer to the introduction of S1101 for details, and will not be repeated here.
  • a first network device sends first information to a second network device.
  • the first information is used to indicate at least one condition that triggers recording of the SHR.
  • the first network device receives second information from the second network device.
  • the second information indicates whether the second network device accepts one or more of the above at least one condition. In this way, the first network device can determine whether the second network device supports the SHR feature based on the second information.
  • the embodiment of the present application further provides a communication device, and the communication device may be the network element in the foregoing method embodiment, or a device including the foregoing network element, or may be a component applicable to the network element.
  • the communication device includes hardware structures and/or software modules corresponding to each function.
  • FIG. 14 shows a schematic structural diagram of a communication device 1400 .
  • the communication device 1400 includes a processing unit 1401 , a sending unit 1402 and a receiving unit 1403 .
  • the processing unit 1401 is configured to support the terminal device to execute S303 in FIG. 3 , S601 in FIG. 6 , S801 in FIG. 8 , and S1303 in FIG. 13 , And/or other processing operations that need to be performed by the terminal device in the embodiment of the present application.
  • the receiving unit 1403 is configured to support the terminal device to perform S302 in FIG. 3 , S603 in FIG. 6 , S1302 in FIG. 13 , and/or other receiving operations that the terminal device needs to perform in this embodiment of the application.
  • the sending unit 1402 is configured to support the terminal device to perform S304 in FIG. 3 , S604 in FIG. 6 , S802 in FIG. 8 , S1304 in FIG. 13 , and/or other sending operations that the terminal device needs to perform in this embodiment of the application.
  • the processing unit 1401 is configured to support the first network device to execute S301 and S305 in FIG. 3, S602 and S605 in FIG. S803a, S803b, S803c, S1301, S1305 in FIG. 13, and/or other processing operations that need to be performed by the first network device in this embodiment of the present application.
  • the receiving unit 1403 is configured to support the first network device to execute S304 in FIG. 3 , S604 in FIG. 6 , S802 in FIG. 8 , S1102 and S1105 in FIG. 11 , S1304 in FIG. 13 , and/or the embodiment of this application Other receiving operations that need to be performed by the first network device.
  • the sending unit 1402 is configured to support the first network device to execute S302 in FIG. 3 , S603 in FIG. 6 , S1101 in FIG. 11 , S1302 in FIG. 13 , and/or the first network device in the embodiment of this application needs to execute Other send operations.
  • the processing unit 1401 is configured to support other processing operations that need to be performed by the second network device.
  • the receiving unit 1403 is configured to support the second network device to perform S1101 in FIG. 11 , and/or other receiving operations that the second network device needs to perform in the embodiment of the present application.
  • the sending unit 1402 is configured to support the second network device to perform S1102 in FIG. 11 , and/or other sending operations that the second network device needs to perform in the embodiment of the present application.
  • the communication device 1400 may further include a storage unit 1404 for storing program codes and data of the communication device, and the data may include but not limited to original data or intermediate data.
  • the processing unit 1401 may be a processor or a controller, such as a CPU, a general processor, an application specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other Programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor can also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of DSP and a microprocessor, and so on.
  • the sending unit 1402 may be a communication interface, a transmitter, or a sending circuit, etc., wherein the communication interface is collectively referred to as, in a specific implementation, the communication interface may include multiple interfaces, for example, it may include: a terminal device (such as a first terminal device, the interface between the second terminal equipment) and/or other interfaces.
  • a terminal device such as a first terminal device, the interface between the second terminal equipment
  • the receiving unit 1403 may be a communication interface, a receiver or a receiving circuit, etc., wherein the communication interface is collectively referred to as, in a specific implementation, the communication interface may include multiple interfaces, for example, it may include: a terminal device and a network device (such as a first network device, a second network device) and/or other interfaces.
  • the communication interface may include multiple interfaces, for example, it may include: a terminal device and a network device (such as a first network device, a second network device) and/or other interfaces.
  • the sending unit 1402 and the receiving unit 1403 may be physically or logically implemented as the same unit.
  • the storage unit 1404 may be a memory.
  • the processing unit 1401 is a processor
  • the sending unit 1402 and the receiving unit 1403 are communication interfaces
  • the storage unit 1404 is a memory
  • the communication device involved in this embodiment of the present application may be as shown in FIG. 15 .
  • the communication device includes: a processor 1501 , a communication interface 1502 , and a memory 1503 .
  • the communication device may further include a bus 1504 .
  • the communication interface 1502, the processor 1501 and the memory 1503 can be connected to each other through the bus 1504;
  • the bus 1504 can be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus etc.
  • the bus 1504 can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 15 , but it does not mean that there is only one bus or one type of bus.
  • the embodiments of the present application further provide a computer program product carrying computer instructions, and when the computer instructions are run on the computer, the computer is made to execute the method described in the foregoing embodiments.
  • an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer executes the method described in the above-mentioned embodiments.
  • an embodiment of the present application further provides a chip, including: a processing circuit and a transceiver circuit, and the processing circuit and the transceiver circuit are used to implement the methods described in the foregoing embodiments.
  • the processing circuit is used to execute the processing action in the corresponding method
  • the transceiver circuit is used to execute the receiving/sending action in the corresponding method.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using 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 instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state drive (solid state drive, SSD)) wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state drive (solid state drive, SSD)
  • the disclosed system, device and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the modules is only a logical function division. In actual implementation, there may be other division methods.
  • multiple modules or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or modules may be in electrical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple devices. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Abstract

本申请提供了通信方法及装置，涉及无线通信技术领域，能够记录潜在移动性失败过程中的用户面传输中断时长。该方法包括：终端设备接收来自第一网络设备的指示信息。其中，指示信息指示第一阈值。当切换过程中用户面传输中断时长大于或等于第一阈值时，终端设备记录第一报告。其中，第一报告指示用户面传输中断时长。

Description

通信方法及装置
本申请要求于2021年08月04日提交国家知识产权局、申请号为202110891888.2、申请名称为“通信方法及装置”的中国专利申请的优先权，以及要求于2021年12月31日提交国家知识产权局、申请号为202111676240.X、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在双激活协议栈(dual active protocol stack，DAPS)切换过程中，终端设备与源网络设备之间仍能够进行用户面数据传输，以实现用户面传输的零毫秒中断。
然而，即使DAPS切换成功，终端设备也可能发生用户面传输中断的现象，如终端设备在DAPS切换过程中与源网络设备之间发生无线链路失败(radio link failure，RLF)。此种情况下，终端设备并不记录用户面传输中断过程中的移动性参数，导致网络侧无法优化处理用户面传输中断的问题。
发明内容
本申请提供一种通信方法及装置，能够记录潜在移动性失败过程中的用户面传输中断时长，为网络侧优化处理用户面传输中断的问题奠定基础。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，本申请实施例提供一种通信方法，该方法的执行主体可以是终端设备，也可以是应用于终端设备中的芯片。下面以执行主体是终端设备为例进行描述。该方法包括：终端设备接收来自第一网络设备的指示信息。其中，指示信息指示第一阈值。当切换过程中用户面传输中断时长大于或等于第一阈值时，终端设备记录第一报告。其中，第一报告指示用户面传输中断时长。
在本申请实施例通信方法中，指示信息指示第一阈值。终端设备在用户面传输中断时长大于或等于第一阈值的情况下，记录第一报告。其中，第一报告包括用户面传输中断时长。即使终端设备成功接入第二网络设备，但切换过程中终端设备存在用户面传输中断的现象，第一报告也能够记录用户面传输中断时长，避免现有技术中终端设备无法记录用户面传输中断的移动性参数的问题，也为网络侧确定优化参数奠定了基础。
在一种可能的设计中，用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
在一种可能的设计中，用户面传输中断的起始标识包括以下其中一项：
第一项，终端设备向第一网络设备成功发送最后一个数据包。
第二项，终端设备成功接收来自第一网络设备的最后一个数据包。
用户面传输中断的终止标识包括以下其中一项：
第一项，终端设备向第二网络设备成功发送首个数据包。
第二项，终端设备成功接收来自第二网络设备的首个数据包。
其中，第一网络设备是终端设备在切换过程前接入的网络设备，第二网络设备是终端设备在切换过程后接入的网络设备。
也就是说，用户面传输中断是指终端设备与第一网络设备之间的连接中断开始，且终端设备与第二网络设备之间的连接未成功之前的情况。
在一种可能的设计中，指示信息还指示用户面传输中断的起始标识和/或终止标识，以指示终端设备采用指示指示的标识来确定用户面传输中断时长。
在一种可能的设计中，在切换过程中用户面传输中断时长大于或等于第一阈值的情况下，终端设备记录第一报告，包括：在第一定时器的运行时长大于或等于第一阈值的情况下，终端设备记录第一报告。其中，第一定时器的运行时长指示用户面传输中断时长。也就是说，第一定时器的启动标识与用户面传输中断时长的起始标识相同。终端设备采用第一定时器来自监测用户面传输中断时长。
在一种可能的设计中，本申请实施例通信方法还包括：终端设备向第一网络设备发送第一报告。其中，第一网络设备是终端设备在切换过程前接入的网络设备。
如此，第一网络设备即可基于第一报告来优化处理用户面传输中断的问题。
在一种可能的设计中，第一报告还指示以下至少一项：
第一项，触发记录第一报告的原因。
第二项，用户面传输中断的起始标识。
第三项，用户面传输中断的停止标识。
第四项，源小区的无线网络临时标识CRNTI。
在一种可能的设计中，用户面传输中断的起始标识包括以下其中一项：
第一项，终端设备与第一网络设备之间出现下行失步。
第二项，终端设备与第一网络设备之间发生无线链路故障RLF。
第三项，第二定时器启动。其中，第二定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。
第四项，第三定时器启动。其中，第三定时器的运行时长指示在第二定时器运行期间，终端设备触发测量报告至终端设备与第一网络设备恢复同步之间的时长。
第五项，终端设备成功接收到重复的数据包。
用户面传输中断的终止标识包括以下其中一项：
第一项，终端设备与第二网络设备之间的随机接入过程完成。
第二项，终端设备发送无线资源控制RRC重配置完成消息完成。
第三项，终端设备与第二网络设备之间下行同步。
第四项，第二定时器停止。
第五项，第三定时器停止。
在一种可能的设计中，第一报告还指示以下至少一项：
第一项，重复接收的数据包的数量，以表征第一网络设备数据调度不合理的程度。
第二项，重复接收的数据包的比例，以表征第一网络设备数据调度不合理的程度。
在一种可能的设计中，终端设备接收指示信息，包括：终端设备接收RRC重配置消息。其中，RRC重配置消息包括指示信息。也就是说，终端设备通过接收RRC重配置消 息来接收指示信息。
在一种可能的设计中，终端设备接收指示信息，包括：终端设备在接收RRC重配置消息之前，接收指示信息。
在一种可能的设计中，指示信息承载于以下其中一项：RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息。也就是说，指示信息可以承载于不同的消息进行传输。
第二方面，本申请实施例提供一种通信方法，该方法的执行主体可以是第一网络设备，也可以是应用于第一网络设备中的芯片。下面以执行主体是第一网络设备为例进行描述。该方法包括：第一网络设备获取指示信息。其中，指示信息指示第一阈值。第一网络设备向终端设备发送指示信息。其中，指示信息用于终端设备在切换过程中用户面传输中断时长大于或等于第一阈值的情况下记录第一报告，第一报告指示用户面传输中断时长。
在本申请实施例通信方法中，指示信息指示第一阈值。第一网络设备向终端设备发送指示信息，以使终端设备在用户面传输中断时长大于或等于第一阈值的情况下，记录第一报告。其中，第一报告包括用户面传输中断时长。如此，即使终端设备成功接入第二网络设备，但切换过程中终端设备存在用户面传输中断的现象，第一报告也能够记录用户面传输中断时长，避免现有技术中终端设备无法记录用户面传输中断的移动性参数的问题，也为网络侧确定优化参数奠定了基础。
在一种可能的设计中，用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
在一种可能的设计中，用户面传输中断的起始标识包括以下其中一项：
第一项，终端设备向第一网络设备成功发送最后一个数据包。
第二项，终端设备成功接收来自第一网络设备的最后一个数据包。
用户面传输中断的终止标识包括以下其中一项：
第一项，终端设备向第二网络设备成功发送首个数据包。
第二项，终端设备成功接收来自第二网络设备的首个数据包。
其中，第一网络设备是终端设备在切换过程前接入的网络设备，第二网络设备是终端设备在切换过程后接入的网络设备。
在一种可能的设计中，指示信息还指示用户面传输中断的起始标识和/或终止标识。
在一种可能的设计中，本申请实施例通信方法还包括：第一网络设备接收来自终端设备的第一报告。其中，第一网络设备是终端设备在切换过程前接入的网络设备。
在一种可能的设计中，第一网络设备获取指示信息，包括：第一网络设备确定指示信息。也就是说，指示信息可以由第一网络设备配置。
在一种可能的设计中，第一网络设备获取指示信息，包括：第一网络设备接收来自第二网络设备的指示信息。也就是说，指示信息可以由第二网络设备配置。
在一种可能的设计中，本申请实施例通信方法还包括：第一网络设备向第二网络设备发送参考信息。其中，参考信息用于确定指示信息。也就是说，第一网络设备能够为第二网络设备提供参考信息，以使第二网络设备基于参考信息确定指示信息。
在一种可能的设计中，本申请实施例通信方法还包括：第一网络设备接收来自第二网络设备的第一信息。其中，第一信息指示第二网络设备支持成功切换报告SHR功能。第一网络设备向第二网络设备发送参考信息，包括：第一网络设备根据第一信息，向第二网络 设备发送参考信息，以避免参考信息的传输导致的传输资源浪费。
在一种可能的设计中，本申请实施例通信方法还包括：第一网络设备向第二网络设备发送第二信息。其中，第二信息用于请求第二网络设备反馈是否支持SHR功能，以使第二网络设备反馈第一信息。
在一种可能的设计中，第一报告还指示以下至少一项：
第一项，触发记录第一报告的原因。
第二项，用户面传输中断的起始标识。
第三项，用户面传输中断的停止标识。
第四项，源小区的无线网络临时标识CRNTI。
在一种可能的设计中，第一网络设备接收来自第二网络设备的指示信息，包括：第一网络设备接收来自第二网络设备的HO请求确认消息，其中，HO请求确认消息包括无线资源控制RRC重配置消息，指示信息承载于RRC重配置消息中。
也就是说，指示信息通过RRC重配置消息从第二网络设备传输到第一网络设备。
在一种可能的设计中，第一网络设备接收来自第二网络设备的指示信息，包括：第一网络设备接收来自第二网络设备的HO请求确认消息，其中，HO请求确认消息包括RRC重配置消息，指示信息承载于RRC重配置消息外，且在HO请求确认消息中。
也就是说，指示信息通过HO请求确认消息从第二网络设备传输到第一网络设备。
在一种可能的设计中，第一网络设备接收来自第二网络设备的指示信息，包括：第一网络设备接收HO请求确认消息之前，接收来自第二网络设备的指示信息，以使第一网络设备较早地获取指示信息。
在一种可能的设计中，第一网络设备向终端设备发送指示信息，包括：第一网络设备向终端设备发送RRC重配置消息。
在一种可能的设计中，第一网络设备向终端设备发送指示信息，包括：第一网络设备发送RRC重配置消息前，向终端设备发送指示信息。
在一种可能的设计中，指示信息承载于以下其中一项：RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息。
第三方面，本申请实施例提供一种通信方法，该方法的执行主体可以是第二网络设备，也可以是应用于第二网络设备中的芯片。下面以执行主体是第二网络设备为例进行描述。该方法包括：第二网络设备确定指示信息。其中，指示信息指示第一阈值。第二网络设备向第一网络设备发送指示信息。其中，第一网络设备是终端设备在切换过程前接入的网络设备，第二网络设备是终端设备在切换过程后接入的网络设备。第一阈值用于终端设备在切换过程中用户面传输中断时长大于或等于第一阈值的情况下记录第一报告，第一报告指示用户面传输中断时长。
在本申请实施例通信方法中，指示信息指示第一阈值，且由第二网络设备配置。第二网络设备通过第一网络设备向终端设备发送指示信息，以使终端设备在用户面传输中断时长大于或等于第一阈值的情况下，记录第一报告。其中，第一报告包括用户面传输中断时长。如此，即使终端设备成功接入第二网络设备，但终端设备存在用户面传输中断的现象，第一报告也能够记录用户面传输中断时长，避免现有技术中终端设备无法记录用户面传输中断的移动性参数的问题，也为网络侧确定优化参数奠定了基础。
在一种可能的设计中，用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
在一种可能的设计中，用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
在一种可能的设计中，用户面传输中断的起始标识包括以下其中一项：
第一项，终端设备向第一网络设备成功发送最后一个数据包。
第二项，终端设备成功接收来自第一网络设备的最后一个数据包。
用户面传输中断的终止标识包括以下其中一项：
第一项，终端设备向第二网络设备成功发送首个数据包。
第二项，终端设备成功接收来自第二网络设备的首个数据包。
其中，第一网络设备是终端设备在切换过程前接入的网络设备，第二网络设备是终端设备在切换过程后接入的网络设备。
在一种可能的设计中，指示信息还指示用户面传输中断的起始标识和/或终止标识。
在一种可能的设计中，本申请实施例通信方法还包括：第二网络设备接收来自第一网络设备的参考信息。其中，参考信息用于确定指示信息，以使第二网络设备基于参考信息确定指示信息。
在一种可能的设计中，本申请实施例通信方法还包括：第二网络设备向第一网络设备发送第一信息。其中，第一信息指示第二网络设备支持成功切换报告SHR功能。
也就是说，第二网络设备能够主动向告知第一网络设备自身对SHR功能的支持状况。
在一种可能的设计中，本申请实施例通信方法还包括：第二网络设备接收来自第一网络设备的第二信息。其中，第二信息用于请求第二网络设备反馈是否支持SHR功能。第二网络设备向第一网络设备发送第一信息，包括：第二网络设备根据第二信息，向第一网络设备发送第一信息。
也就是说，第二网络设备是基于第一网络设备的请求才向第一网络设备提供第一信息，以简化第二网络设备的处理复杂度。
在一种可能的设计中，第二网络设备向第一网络设备发送指示信息，包括：第二网络设备向第一网络设备发送HO请求确认消息。其中，HO请求确认消息包括无线资源控制RRC重配置消息，指示信息承载于RRC重配置消息中。
在一种可能的设计中，第二网络设备向第一网络设备发送指示信息，包括：第二网络设备向第一网络设备发送HO请求确认消息。其中，HO请求确认消息包括RRC重配置消息，指示信息承载于RRC重配置消息外，且在HO请求确认消息中。
在一种可能的设计中，第二网络设备向第一网络设备发送指示信息，包括：第二网络设备发送HO请求确认消息之前，向第一网络设备发送指示信息。
第四方面，本申请实施例提供一种通信方法，该方法的执行主体可以是终端设备，也可以是应用于终端设备中的芯片。下面以执行主体是终端设备为例进行描述。该方法包括：在终端设备执行双激活协议栈DAPS切换过程中，检测到与源小区之间的无线链路失败RLF，且完成与目标小区之间的DAPS切换的情况下，终端设备确定第一报告。其中，第一报告包括预设条件指示的待记录的报告，或第一报告包括预设条件指示的待上报的报告，预设条件包括以下至少一项：第一项，仅记录成功切换报告SHR，第二项，仅记录RLF 报告，第三项，仅上报SHR，第四项，仅上报RLF报告。
在本申请实施例通信方法中，预设条件指示了终端设备待记录的报告，或终端设备待上报的报告。终端设备确定满足预设条件的第一报告。如此，针对一次移动性异常，终端设备仅记录RLF报告和SHR中的一种报告，或终端设备仅上报RLF报告和SHR中的一种报告，相应的，网络侧针对一次移动性异常，也就能够获取到一个报告(如上述SHR，或RLF报告)，从而避免过度调整的问题。
在一种可能的设计中，本申请实施例通信方法还包括：终端设备接收来自第一网络设备的预设条件。其中，第一网络设备是终端设备在切换过程前接入的网络设备。也就是说，预设条件可以是网络侧为终端设备配置的条件。
在一种可能的设计中，终端设备接收来自第一网络设备的预设条件，包括：终端设备接收来自第一网络设备的无线资源控制RRC重配置消息。其中，RRC重配置消息包括预设条件。也就是说，终端设备通过接收RRC重配置消息来接收预设条件。
在一种可能的设计中，终端设备接收来自第一网络设备的预设条件，包括：终端设备接收RRC重配置消息之前，接收来自第一网络设备的预设条件，以使终端设备较早地获取到预设条件。
在一种可能的设计中，预设条件承载于以下其中一项：RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息。也就是说，预设条件可以承载于不同的消息进行传输。
在一种可能的设计中，预设条件是预配置的。
在一种可能的设计中，本申请实施例通信方法还包括：终端设备向第一网络设备发送第一报告。其中，第一网络设备是终端设备在切换过程前接入的网络设备，以使第一网络设备基于第一报告确定网络优化参数。
在一种可能的设计中，第一报告是在切换过程中用户面传输中断时长大于或等于第一阈值的情况下记录的报告，第一报告包括用户面传输中断时长，以使第一网络设备针对用户面传输中断问题确定网络优化参数，以优化处理用户面传输中断的问题。
第五方面，本申请实施例提供一种通信方法，该方法的执行主体可以是第一网络设备，也可以是应用于第一网络设备中的芯片。下面以执行主体是第一网络设备为例进行描述。该方法包括：第一网络设备获取预设条件。其中，预设条件包括以下至少一项：第一项，仅记录成功切换报告SHR，第二项，仅记录无线链路失败RLF报告，第三项，仅上报SHR，第四项，仅上报RLF报告。第一网络设备向终端设备发送预设条件。其中，预设条件用于终端设备执行双激活协议栈DAPS切换过程中，检测到与源小区之间的无线链路失败RLF，且完成与目标小区之间的DAPS切换的情况下确定第一报告，第一报告包括预设条件中指示记录的报告，或第一报告包括预设条件中指示上报的报告。
在本申请实施例通信方法中，预设条件指示了终端设备待记录的报告，或终端设备待上报的报告。终端设备确定满足预设条件的第一报告。并且，预设条件是由第一网络设备为终端设备提供的。如此，针对一次移动性异常，终端设备仅记录RLF报告和SHR中的一种报告，或终端设备仅上报RLF报告和SHR中的一种报告，相应的，网络侧针对一次移动性异常，也就能够获取到一个报告(如上述SHR，或RLF报告)，从而避免过度调整的问题。
在一种可能的设计中，第一网络设备获取预设条件，包括：第一网络设备确定预设条 件。也就是说，预设条件可以由第一网络设备配置。
在一种可能的设计中，第一网络设备获取预设条件，包括：第一网络设备接收来自第二网络设备的预设条件。其中，终端设备从第一网络设备切换至第二网络设备。也就是说，预设条件可以由第二网络设备配置。
在一种可能的设计中，第一网络设备接收来自第二网络设备的预设条件，包括：第一网络设备接收来自第二网络设备的切换HO请求确认消息。其中，HO请求确认消息包括无线资源控制RRC重配置消息，预设条件承载于RRC重配置消息中。
也就是说，预设条件通过RRC重配置消息从第二网络设备传输到第一网络设备。
在一种可能的设计中，第一网络设备接收来自第二网络设备的预设条件，包括：第一网络设备接收来自第二网络设备的HO请求确认消息。其中，HO请求确认消息包括RRC重配置消息，预设条件承载于RRC重配置消息外，且在HO请求确认消息中。
也就是说，预设条件通过HO请求确认消息从第二网络设备传输到第一网络设备。
在一种可能的设计中，第一网络设备接收来自第二网络设备的预设条件，包括：第一网络设备接收HO请求确认消息之前，来自第二网络设备的预设条件。
在一种可能的设计中，第一网络设备向终端设备发送预设条件，包括：第一网络设备向终端设备发送RRC重配置消息。
在一种可能的设计中，第一网络设备向终端设备发送预设条件，包括：第一网络设备发送RRC重配置消息前，向终端设备发送预设条件。
在一种可能的设计中，预设条件承载于以下其中一项：RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息。
在一种可能的设计中，本申请实施例通信方法还包括：第一网络设备接收来自终端设备的第一报告。
在一种可能的设计中，第一报告是在切换过程中用户面传输中断时长大于或等于阈值的情况下记录的报告，第一报告包括用户面传输中断时长。
第六方面，本申请实施例提供一种通信方法，该方法的执行主体可以是第二网络设备，也可以是应用于第二网络设备中的芯片。下面以执行主体是第二网络设备为例进行描述。该方法包括：第二网络设备确定预设条件。其中，预设条件包括以下至少一项：第一项，仅记录成功切换报告SHR，第二项，仅记录无线链路失败RLF报告，第三项，仅上报SHR，第四项，仅上报RLF报告。第二网络设备向第一网络设备发送预设条件。其中，预设条件用于终端设备执行双激活协议栈DAPS切换过程中，检测到与源小区之间的无线链路失败RLF，且完成与目标小区之间的DAPS切换的情况下确定第一报告，第一报告包括预设条件中指示记录的报告，或第一报告包括预设条件中指示上报的报告，第一网络设备是终端设备在切换过程前接入的网络设备，第二网络设备是终端设备在切换过程后接入的网络设备。
在本申请实施例通信方法中，预设条件指示了终端设备待记录的报告，或终端设备待上报的报告。终端设备确定满足预设条件的第一报告。并且，预设条件是由第二网络设备为终端设备配置的。如此，针对一次移动性异常，终端设备仅记录RLF报告和SHR中的一种报告，或终端设备仅上报RLF报告和SHR中的一种报告，相应的，网络侧针对一次移动性异常，也就能够获取到一个报告(如上述SHR，或RLF报告)，从而避免过度调 整的问题。
在一种可能的设计中，第二网络设备向第一网络设备发送预设条件，包括：第二网络设备向第一网络设备发送切换HO请求确认消息。其中，HO请求确认消息包括无线资源控制RRC重配置消息，预设条件承载于RRC重配置消息中。
在一种可能的设计中，第二网络设备向第一网络设备发送预设条件，包括：第二网络设备向第一网络设备发送HO请求确认消息。其中，HO请求确认消息包括RRC重配置消息，预设条件承载于RRC重配置消息外，且在HO请求确认消息中。
在一种可能的设计中，第二网络设备向第一网络设备发送预设条件，包括：第二网络设备发送HO请求确认消息之前，向第一网络设备发送预设条件。
第七方面，本申请实施例提供一种通信方法，该方法的执行主体可以是第一网络设备，也可以是应用于第一网络设备中的芯片。下面以执行主体是第一网络设备为例进行描述。该方法包括：第一网络设备接收来自终端设备的成功切换报告SHR和无线链路失败RLF报告。其中，SHR和RLF报告是终端设备执行双激活协议栈DAPS切换过程中，检测到与源小区之间的RLF，且完成与目标小区之间的DAPS切换的情况下确定的报告。第一网络设备根据SHR确定网络优化参数，或第一网络设备根据RLF报告确定网络优化参数，或第一网络设备根据SHR和RLF报告确定网络优化参数。
在本申请实施例通信方法中，第一网络设备获取SHR和RLF报告的情况下，第一网络设备根据SHR确定网络优化参数，或第一网络设备根据RLF报告确定网络优化参数，或第一网络设备根据SHR和RLF报告确定网络优化参数，以避免第一网络设备基于同一移动性异常的RLF报告和SHR分别确定网络优化参数，对同一移动性参数进行了两次调整的现象，从而解决过度调整的问题。
在一种可能的设计中，第一网络设备根据SHR确定网络优化参数的情况下，本申请实施例通信方法还包括：第一网络设备丢弃RLF报告，以避免第一网络设备重复采用RLF报告确定网络优化参数。
在一种可能的设计中，第一网络设备根据RLF报告确定网络优化参数的情况下，本申请实施例通信方法还包括：第一网络设备丢弃SHR，以避免第一网络设备重复采用SHR确定网络优化参数。
第八方面，本申请实施例提供一种通信方法，该方法的执行主体可以是第一网络设备，也可以是应用于第一网络设备中的芯片。下面以执行主体是第一网络设备为例进行描述。该方法包括：第一网络设备向第二网络设备发送第一信息。其中，第一网络设备是终端设备切换过程前接入的网络设备，第二网络设备是切换过程后接入的网络设备。第一信息用于指示触发记录成功记录报告SHR的至少一个条件。第一网络设备接收来自第二网络设备的第二信息。其中，第二信息指示第二网络设备是否接受至少一个条件中的一个或多个。
在本申请实施例通信方法中，第一网络设备向第二网络设备发送第一信息。其中，第一信息用于指示触发记录SHR的至少一个条件。然后，第一网络设备接收来自第二网络设备的第二信息。其中，第二信息指示第二网络设备是否接受上述至少一个条件中的一个或多个。这样一来，第一网络设备基于第二信息，即可确定第二网络设备是否支持SHR特性。
在一种可能的设计中，第一信息包括以下至少一项：
第一项，用户面传输中断时长的阈值。
第二项，第二定时器的阈值。其中，第二定时器的运行时长指示终端设备接收RRC重配置消息之后未接入第二网络设备的时长。
第三项，第三定时器的阈值。其中，第三定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。
第四项，第四定时器的阈值。其中，第四定时器的运行时长指示在第三定时器运行期间，终端触发测量报告至终端与第一网络设备恢复同步之间的时长。
在一种可能的设计中，第一信息承载于切换HO请求消息。也就是说，第一网络设备通过HO请求消息向第二网络设备发送第一信息。
在一种可能的设计中，第一网络设备向第二网络设备发送第一信息，包括：在第一网络设备发送HO请求消息之前，第一网络设备向第二网络设备发送第一信息，以使第二网络设备较早地获取到第一信息。
在一种可能的设计中，本申请实施例通信方法还包括：第一网络设备接收来自第二网络设备的第三信息。其中，第三信息指示第二网络设备支持SHR功能。第一网络设备向第二网络设备发送第一信息，包括：第一网络设备根据第三信息，向第二网络设备发送第一信息，以避免第一信息的传输所导致的传输资源浪费。
在一种可能的设计中，本申请实施例通信方法还包括：第一网络设备向第二网络设备发送第四信息。其中，第四信息用于请求第二网络设备反馈是否支持SHR功能，以使第二网络设备在支持SHR功能的情况下提供第三信息。
在一种可能的设计中，在第二网络设备接受至少一个条件中的一个或多个的情况下，第二信息还指示以下至少一项：
第一项，无线资源控制RRC重配置消息中携带至少一个条件中的一个或多个。
第二项，触发记录SHR的条件类型。
第三项，触发记录SHR的阈值。
也就是说，第一网络设备通过第二信息即可获知RRC重配置消息中携带预设条件的状况。
第九方面，本申请实施例提供一种通信方法，该方法的执行主体可以是第二网络设备，也可以是应用于第二网络设备中的芯片。下面以执行主体是第二网络设备为例进行描述。该方法包括：第二网络设备接收来自第一网络设备的第一信息。其中，第一网络设备是终端设备切换过程前接入的网络设备，第二网络设备是切换过程后接入的网络设备。第一信息用于指示触发记录成功切换报告SHR的至少一个条件。第二网络设备向第一网络设备发送第二信息。其中，第二信息用于指示第二网络设备是否接受至少一个条件中的一个或多个。
在一种可能的设计中，第一信息包括以下至少一项：
第一项，用户面传输中断时长的阈值。
第二项，第二定时器的阈值。其中，第二定时器的运行时长指示终端设备接收无线资源控制RRC重配置消息之后未接入第二网络设备的时长。
第三项，第三定时器的阈值。其中，第三定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。
第四项，第四定时器的阈值。其中，第四定时器的运行时长指示在第三定时器运行期 间，终端触发测量报告至终端与第一网络设备恢复同步之间的时长。
在一种可能的设计中，第一信息承载于切换HO请求消息。
在一种可能的设计中，第二网络设备接收来自第一网络设备的第一信息，包括：在第二网络设备接收HO请求消息之前，接收来自第一网络设备的第一信息。
在一种可能的设计中，本申请实施例通信方法还包括：第二网络设备向第一网络设备发送第三信息。其中，第三信息指示第二网络设备支持SHR功能。
在一种可能的设计中，本申请实施例通信方法还包括：第二网络设备接收来自第一网络设备的第四信息。其中，第四信息用于查询第二网络设备对SHR功能的支持状况。第二网络设备向第一网络设备发送第三信息，包括：第二网络设备根据第四信息，向第一网络设备发送第三信息。
在一种可能的设计中，在第二网络设备接受至少一个条件中的一个或多个的情况下，第二信息还指示以下至少一项：
第一项，RRC重配置消息中携带至少一个条件中的一个或多个。
第二项，触发记录SHR的条件类型。
第三项，触发记录SHR的阈值。
本申请实施例中，触发记录第一报告的条件可以是用户面传输中断时长，也可以是其他触发条件，例如SHR trigger condition中的触发条件。
第十方面，本申请实施例提供一种通信方法，该方法的执行主体可以是终端设备，也可以是应用于终端设备中的芯片。下面以执行主体是终端设备为例进行描述。该方法包括：终端设备接收来自第一网络设备的触发条件。其中，触发条件至少包括切换过程中终端设备与第一网络设备之间发生无线链路失败RLF。当满足触发条件时，终端设备记录成功切换报告SHR。其中，SHR至少指示触发条件。
也就是说，在切换过程中，若终端设备与第一网络设备之间发生RLF，则终端设备记录此情况，即上述SHR至少指示终端设备满足的触发条件，以指示终端设备与第一网络设备之间发生RLF，避免现有技术中此种情况下终端设备无法记录的问题，也为网络侧确定优化参数奠定了基础。
在一种可能的设计中，SHR至少指示触发条件，包括：SHR至少指示发生RLF的原因，以指示终端设备与第一网络设备之间发生了RLF。
在一种可能的设计中，RLF的原因包括以下至少一项：波束失败恢复失败，随机接入失败，重传次数达到最大次数，先听后说失败，RLF恢复失败，第二定时器超时，其中，第二定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。
在一种可能的设计中，第一信息还包括随机接入的信息。其中，随机接入的失败导致终端设备和第一网络设备发生RLF。
在一种可能的设计中，本申请实施例通信方法还包括：终端设备向第一网络设备发送SHR。其中，第一网络设备是终端设备在切换过程前接入的网络设备，SHR用于确定网络优化参数。
第十一方面，本申请实施例提供一种通信方法，该方法的执行主体可以是第一网络设备，也可以是应用于第一网络设备中的芯片。下面以执行主体是第一网络设备为例进行描述。该方法包括：第一网络设备向终端设备发送触发条件，其中，触发条件至少包括切换 过程中终端设备与第一网络设备之间发生无线链路失败RLF，触发条件用于终端设备在满足触发条件的情况下记录成功切换报告SHR，SHR至少指示触发条件。第一网络设备接收来自终端设备的SHR，根据SHR确定网络优化参数。
在一种可能的设计中，SHR至少指示触发条件，包括：SHR至少指示发生RLF的原因，以指示终端设备与第一网络设备之间发生了RLF。
在一种可能的设计中，RLF的原因包括以下至少一项：波束失败恢复失败，随机接入失败，重传次数达到最大次数，先听后说失败，RLF恢复失败，第二定时器超时，其中，第二定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。
在一种可能的设计中，第一信息还包括随机接入的信息。其中，随机接入的失败导致终端设备和第一网络设备发生RLF。
第十二方面，本申请实施例提供一种通信装置，该通信装置可以为上述第一方面或第一方面任一种可能的设计中的终端设备，或者实现上述终端设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，接收单元用于接收来自第一网络设备的指示信息。其中，指示信息指示第一阈值。处理单元用于当切换过程中用户面传输中断时长大于或等于第一阈值时，记录第一报告。其中，第一报告指示用户面传输中断时长。
在一种可能的设计中，用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
在一种可能的设计中，用户面传输中断的起始标识包括以下其中一项：
第一项，发送单元向第一网络设备成功发送最后一个数据包。
第二项，接收单元成功接收来自第一网络设备的最后一个数据包。
用户面传输中断的终止标识包括以下其中一项：
第一项，发送单元向第二网络设备成功发送首个数据包。
第二项，接收单元成功接收来自第二网络设备的首个数据包。
其中，第一网络设备是通信装置在切换过程前接入的网络设备，第二网络设备是通信装置在切换过程后接入的网络设备。
在一种可能的设计中，指示信息还指示用户面传输中断的起始标识和/或终止标识。
在一种可能的设计中，在切换过程中用户面传输中断时长大于或等于第一阈值的情况下，处理单元用于记录第一报告，具体包括：在第一定时器的运行时长大于或等于第一阈值的情况下，记录第一报告。其中，第一定时器的运行时长指示用户面传输中断时长。
在一种可能的设计中，发送单元还用于向第一网络设备发送第一报告。其中，第一网络设备是通信装置在切换过程前接入的网络设备。
在一种可能的设计中，第一报告还指示以下至少一项：
第一项，触发记录第一报告的原因。
第二项，用户面传输中断的起始标识。
第三项，用户面传输中断的停止标识。
第四项，源小区的无线网络临时标识CRNTI。
在一种可能的设计中，用户面传输中断的起始标识包括以下其中一项：
第一项，通信装置与第一网络设备之间出现下行失步。
第二项，通信装置与第一网络设备之间发生无线链路失败RLF。
第三项，第二定时器启动。其中，第二定时器的运行时长指示处理单元检测到与第一网络设备之间有物理层问题的时长。
第四项，第三定时器启动。其中，第三定时器的运行时长指示在第二定时器运行期间，处理单元触发测量报告至通信装置与第一网络设备恢复同步之间的时长。
第五项，接收单元成功接收到重复的数据包。
用户面传输中断的终止标识包括以下其中一项：
第一项，通信装置与第二网络设备之间的随机接入过程完成。
第二项，发送单元发送无线资源控制RRC重配置完成消息完成。
第三项，通信装置与第二网络设备之间下行同步。
第四项，第二定时器停止。
第五项，第三定时器停止。
在一种可能的设计中，第一报告还指示以下至少一项：
第一项，重复接收的数据包的数量。
第二项，重复接收的数据包的比例。
在一种可能的设计中，接收单元用于接收指示信息，具体包括：接收RRC重配置消息。其中，RRC重配置消息包括指示信息。
在一种可能的设计中，接收单元用于接收指示信息，具体包括：在接收RRC重配置消息之前，接收指示信息。
在一种可能的设计中，指示信息承载于以下其中一项：RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息。也就是说，指示信息可以承载于不同的消息进行传输。
第十三方面，本申请实施例提供一种通信装置，该通信装置可以为上述第二方面或第二方面任一种可能的设计中的第一网络设备，或者实现上述第一网络设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，处理单元用于获取指示信息。其中，指示信息指示第一阈值。发送单元用于向终端设备发送指示信息。其中，指示信息用于终端设备在切换过程中用户面传输中断时长大于或等于第一阈值的情况下记录第一报告，第一报告指示用户面传输中断时长。
在一种可能的设计中，用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
在一种可能的设计中，用户面传输中断的起始标识包括以下其中一项：
第一项，终端设备向通信装置成功发送最后一个数据包。
第二项，终端设备成功接收来自通信装置的最后一个数据包。
用户面传输中断的终止标识包括以下其中一项：
第一项，终端设备向第二网络设备成功发送首个数据包。
第二项，终端设备成功接收来自第二网络设备的首个数据包。
其中，通信装置是终端设备在切换过程前接入的网络设备，第二网络设备是终端设备在切换过程后接入的网络设备。
在一种可能的设计中，指示信息还指示用户面传输中断的起始标识和/或终止标识。
在一种可能的设计中，接收单元用于接收来自终端设备的第一报告。其中，通信装置是终端设备在切换过程前接入的网络设备。
在一种可能的设计中，处理单元用于获取指示信息，具体包括：确定指示信息。
在一种可能的设计中，处理单元用于获取指示信息，包括：通过接收单元接收来自第二网络设备的指示信息。
在一种可能的设计中，发送单元用于向第二网络设备发送参考信息。其中，参考信息用于确定指示信息。
在一种可能的设计中，接收单元还用于接收来自第二网络设备的第一信息。其中，第一信息指示第二网络设备支持成功切换报告SHR功能。发送单元用于向第二网络设备发送参考信息，具体包括：根据第一信息，向第二网络设备发送参考信息。
在一种可能的设计中，本申请实施例通信方法还包括：发送单元还用于向第二网络设备发送第二信息。其中，第二信息用于请求第二网络设备反馈是否支持SHR功能，以使第二网络设备反馈第一信息。
在一种可能的设计中，第一报告还指示以下至少一项：
第一项，触发记录第一报告的原因。
第二项，用户面传输中断的起始标识。
第三项，用户面传输中断的停止标识。
第四项，源小区的无线网络临时标识CRNTI。
在一种可能的设计中，接收单元还用于接收来自第二网络设备的指示信息，具体包括：接收来自第二网络设备的切换HO请求确认消息，其中，HO请求确认消息包括无线资源控制RRC重配置消息，指示信息承载于RRC重配置消息中。
在一种可能的设计中，接收单元用于接收来自第二网络设备的指示信息，具体包括：接收来自第二网络设备的HO请求确认消息，其中，HO请求确认消息包括RRC重配置消息，指示信息承载于RRC重配置消息外，且在HO请求确认消息中。
在一种可能的设计中，接收单元用于接收来自第二网络设备的指示信息，具体包括：接收HO请求确认消息之前，接收来自第二网络设备的指示信息。
在一种可能的设计中，发送单元用于向终端设备发送指示信息，具体包括：向终端设备发送RRC重配置消息。
在一种可能的设计中，发送单元用于向终端设备发送指示信息，具体包括：发送RRC重配置消息前，向终端设备发送指示信息。
在一种可能的设计中，指示信息承载于以下其中一项：RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息。
第十四方面，本申请实施例提供一种通信装置，该通信装置可以为上述第三方面或第三方面任一种可能的设计中的第二网络设备，或者实现上述第二网络设备功能的芯片；所 述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，处理单元用于确定指示信息。其中，指示信息指示第一阈值。发送单元用于向第一网络设备发送指示信息。其中，第一网络设备是终端设备在切换过程前接入的网络设备，通信装置是终端设备在切换过程后接入的网络设备。第一阈值用于终端设备在切换过程中用户面传输中断时长大于或等于第一阈值的情况下记录第一报告，第一报告指示用户面传输中断时长。
在一种可能的设计中，用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
在一种可能的设计中，用户面传输中断的起始标识包括以下其中一项：
第一项，终端设备向第一网络设备成功发送最后一个数据包。
第二项，终端设备成功接收来自第一网络设备的最后一个数据包。
用户面传输中断的终止标识包括以下其中一项：
第一项，终端设备向通信装置成功发送首个数据包。
第二项，终端设备成功接收来自通信装置的首个数据包。
其中，第一网络设备是终端设备在切换过程前接入的网络设备，通信装置是终端设备在切换过程后接入的网络设备。
在一种可能的设计中，指示信息还指示用户面传输中断的起始标识和/或终止标识。
在一种可能的设计中，接收单元还用于接收来自第一网络设备的参考信息。其中，参考信息用于确定指示信息。
在一种可能的设计中，发送单元还用于向第一网络设备发送第一信息。其中，第一信息指示通信装置支持成功切换报告SHR功能。
在一种可能的设计中，接收单元还用于接收来自第一网络设备的第二信息。其中，第二信息用于请求通信装置反馈是否支持SHR功能。发送单元用于向第一网络设备发送第一信息，具体包括：根据第二信息，向第一网络设备发送第一信息。
在一种可能的设计中，发送单元用于向第一网络设备发送指示信息，具体包括：向第一网络设备发送切换HO请求确认消息。其中，HO请求确认消息包括无线资源控制RRC重配置消息，指示信息承载于RRC重配置消息中。
在一种可能的设计中，发送单元用于向第一网络设备发送指示信息，具体包括：向第一网络设备发送HO请求确认消息。其中，HO请求确认消息包括RRC重配置消息，指示信息承载于RRC重配置消息外，且在HO请求确认消息中。
在一种可能的设计中，发送单元用于向第一网络设备发送指示信息，具体包括：发送HO请求确认消息之前，向第一网络设备发送指示信息。
第十五方面，本申请实施例提供一种通信装置，该通信装置可以为上述第四方面或第四方面任一种可能的设计中的终端设备，或者实现上述终端设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，在通信装置执行双激活协议栈DAPS切换过程中，检测到与源小区之间的无线链路失败RLF，且完成与目标小区之间的DAPS切换的情况下，处理单元用于确定第一报告。其中，第一报告包括预设条件指示的待记录的报告，或第一报告包括预设条件指示的待上报的报告，预设条件包括以下至少一项：第一项，仅记录成功切换报告SHR，第二项，仅记录RLF报告，第三项，仅上报SHR，第四项，仅上报RLF报告。
在一种可能的设计中，接收单元用于接收来自第一网络设备的预设条件。其中，第一网络设备是通信装置在切换过程前接入的网络设备。
在一种可能的设计中，接收单元用于接收来自第一网络设备的预设条件，具体包括：接收来自第一网络设备的无线资源控制RRC重配置消息。其中，RRC重配置消息包括预设条件。
在一种可能的设计中，接收单元用于接收来自第一网络设备的预设条件，具体包括：接收RRC重配置消息之前，接收来自第一网络设备的预设条件。
在一种可能的设计中，预设条件承载于以下其中一项：RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息。也就是说，预设条件可以承载于不同的消息进行传输。
在一种可能的设计中，预设条件是预配置的。
在一种可能的设计中，发送单元用于向第一网络设备发送第一报告。其中，第一网络设备是通信装置在切换过程前接入的网络设备。
在一种可能的设计中，第一报告是在切换过程中用户面传输中断时长大于或等于第一阈值的情况下记录的报告，第一报告包括用户面传输中断时长。
第十六方面，本申请实施例提供一种通信装置，该通信装置可以为上述第五方面或第五方面任一种可能的设计中的第一网络设备，或者实现上述第一网络设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，处理单元用于获取预设条件。其中，预设条件包括以下至少一项：第一项，仅记录成功切换报告SHR，第二项，仅记录无线链路失败RLF报告，第三项，仅上报SHR，第四项，仅上报RLF报告。发送单元用于向终端设备发送预设条件。其中，预设条件用于终端设备执行双激活协议栈DAPS切换过程中，检测到与源小区之间的RLF，且完成与目标小区之间的DAPS切换的情况下确定第一报告，第一报告包括预设条件中指示记录的报告，或第一报告包括预设条件中指示上报的报告。
在一种可能的设计中，处理单元用于获取预设条件，具体包括：确定预设条件。
在一种可能的设计中，处理单元用于获取预设条件，具体包括：通过接收单元接收来自第二网络设备的预设条件。其中，终端设备从通信装置切换至第二网络设备。
在一种可能的设计中，接收单元用于接收来自第二网络设备的预设条件，具体包括：接收来自第二网络设备的切换HO请求确认消息。其中，HO请求确认消息包括无线资源控制RRC重配置消息，预设条件承载于RRC重配置消息中。
在一种可能的设计中，接收单元用于接收来自第二网络设备的预设条件，具体包括： 接收来自第二网络设备的HO请求确认消息。其中，HO请求确认消息包括RRC重配置消息，预设条件承载于RRC重配置消息外，且在HO请求确认消息中。
在一种可能的设计中，接收单元用于接收来自第二网络设备的预设条件，具体包括：接收HO请求确认消息之前，来自第二网络设备的预设条件。
在一种可能的设计中，发送单元用于向终端设备发送预设条件，具体包括：向终端设备发送RRC重配置消息。
在一种可能的设计中，发送单元用于向终端设备发送预设条件，具体包括：发送RRC重配置消息前，向终端设备发送预设条件。
在一种可能的设计中，预设条件承载于以下其中一项：RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息。
在一种可能的设计中，接收单元还用于接收来自终端设备的第一报告。
在一种可能的设计中，第一报告是在切换过程中用户面传输中断时长大于或等于阈值的情况下记录的报告，第一报告包括用户面传输中断时长。
第十七方面，本申请实施例提供一种通信装置，该通信装置可以为上述第六方面或第六方面任一种可能的设计中的第二网络设备，或者实现上述第二网络设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，处理单元用于确定预设条件。其中，预设条件包括以下至少一项：第一项，仅记录成功切换报告SHR，第二项，仅记录无线链路失败RLF报告，第三项，仅上报SHR，第四项，仅上报RLF报告。发送单元用于向第一网络设备发送预设条件。其中，预设条件用于终端设备执行双激活协议栈DAPS切换过程中，检测到与源小区之间的无线链路失败RLF，且完成与目标小区之间的DAPS切换的情况下确定第一报告，第一报告包括预设条件中指示记录的报告，或第一报告包括预设条件中指示上报的报告，第一网络设备是终端设备在切换过程前接入的网络设备，通信装置是终端设备在切换过程后接入的网络设备。
在一种可能的设计中，发送单元用于向第一网络设备发送预设条件，具体包括：向第一网络设备发送切换HO请求确认消息。其中，HO请求确认消息包括无线资源控制RRC重配置消息，预设条件承载于RRC重配置消息中。
在一种可能的设计中，发送单元用于向第一网络设备发送预设条件，具体包括：向第一网络设备发送HO请求确认消息。其中，HO请求确认消息包括RRC重配置消息，预设条件承载于RRC重配置消息外，且在HO请求确认消息中。
在一种可能的设计中，发送单元用于向第一网络设备发送预设条件，具体包括：发送HO请求确认消息之前，向第一网络设备发送预设条件。
第十八方面，本申请实施例提供一种通信装置，该通信装置可以为上述第七方面或第七方面任一种可能的设计中的第一网络设备，或者实现上述第一网络设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，接收单元用于接收来自终端设备的成功切换报告SHR和无线链路失败RLF报告。其中，SHR和RLF报告是终端设备执行双激活协议栈DAPS切换过程中，检测到与源小区之间的RLF，且完成与目标小区之间的DAPS切换的情况下确定的报告。处理单元用于根据SHR确定网络优化参数，或处理单元用于根据RLF报告确定网络优化参数，或处理单元用于根据SHR和RLF报告确定网络优化参数。
在一种可能的设计中，处理单元用于根据SHR确定网络优化参数的情况下，处理单元还用于丢弃RLF报告。
在一种可能的设计中，处理单元用于根据RLF报告确定网络优化参数的情况下，处理单元还用于丢弃SHR。
第十九方面，本申请实施例提供一种通信装置，该通信装置可以为上述第八方面或第八方面任一种可能的设计中的第一网络设备，或者实现上述第一网络设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，发送单元用于向第二网络设备发送第一信息。其中，通信装置是终端设备切换过程前接入的网络设备，第二网络设备是切换过程后接入的网络设备。第一信息用于指示触发记录成功切换报告SHR的至少一个条件。接收单元用于接收来自第二网络设备的第二信息。其中，第二信息指示第二网络设备是否接受至少一个条件中的一个或多个。
在一种可能的设计中，第一信息包括以下至少一项：
第一项，用户面传输中断时长的阈值。
第二项，第二定时器的阈值。其中，第二定时器的运行时长指示终端设备接收无线资源控制RRC重配置消息之后未接入第二网络设备的时长。
第三项，第三定时器的阈值。其中，第三定时器的运行时长指示终端设备检测到与通信装置之间有物理层问题的时长。
第四项，第四定时器的阈值。其中，第四定时器的运行时长指示在第三定时器运行期间，终端触发测量报告至终端与通信装置恢复同步之间的时长。
在一种可能的设计中，第一信息承载于切换HO请求消息。
在一种可能的设计中，发送单元用于向第二网络设备发送第一信息，具体包括：发送HO请求消息之前，向第二网络设备发送第一信息。
在一种可能的设计中，接收单元还用于接收来自第二网络设备的第三信息。其中，第三信息指示第二网络设备支持SHR功能。发送单元用于向第二网络设备发送第一信息，具体包括：根据第三信息，向第二网络设备发送第一信息。
在一种可能的设计中，发送单元还用于向第二网络设备发送第四信息。其中，第四信息用于请求第二网络设备反馈是否支持SHR功能。
在一种可能的设计中，在第二网络设备接受至少一个条件中的一个或多个的情况下，第二信息还指示以下至少一项：
第一项，RRC重配置消息中携带至少一个条件中的一个或多个。
第二项，触发记录SHR的条件类型。
第三项，触发记录SHR的阈值。
第二十方面，本申请实施例提供一种通信装置，该通信装置可以为上述第九方面或第九方面任一种可能的设计中的第二网络设备，或者实现上述第二网络设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，接收单元用于接收来自第一网络设备的第一信息。其中，第一网络设备是终端设备切换过程前接入的网络设备，通信装置是切换过程后接入的网络设备。第一信息用于指示触发记录成功切换报告SHR的至少一个条件。发送单元用于向第一网络设备发送第二信息。其中，第二信息用于指示通信装置是否接受至少一个条件中的一个或多个。
在一种可能的设计中，第一信息包括以下至少一项：
第一项，用户面传输中断时长的阈值。
第二项，第二定时器的阈值。其中，第二定时器的运行时长指示终端设备接收无线资源控制RRC重配置消息之后未接入通信装置的时长。
第三项，第三定时器的阈值。其中，第三定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。
第四项，第四定时器的阈值。其中，第四定时器的运行时长指示在第三定时器运行期间，终端触发测量报告至终端与第一网络设备恢复同步之间的时长。
在一种可能的设计中，第一信息承载于切换HO请求消息。
在一种可能的设计中，接收单元用于接收来自第一网络设备的第一信息，具体包括：在接收HO请求消息之前，接收来自第一网络设备的第一信息。
在一种可能的设计中，发送单元还用于向第一网络设备发送第三信息。其中，第三信息指示通信装置支持SHR功能。
在一种可能的设计中，接收单元用于接收来自第一网络设备的第四信息。其中，第四信息用于查询通信装置对SHR功能的支持状况。发送单元用于向第一网络设备发送第三信息，具体包括：根据第四信息，向第一网络设备发送第三信息。
在一种可能的设计中，在通信装置接受至少一个条件中的一个或多个的情况下，第二信息还指示以下至少一项：
第一项，RRC重配置消息中携带至少一个条件中的一个或多个。
第二项，触发记录SHR的条件类型。
第三项，触发记录SHR的阈值。
第二十一方面，本申请实施例提供一种通信装置，该通信装置可以为上述第十方面或第十方面任一种可能的设计中的终端设备，或者实现上述终端设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元和处理单元。其中，接收单元，用于接收来自第一网络设备 的触发条件。其中，触发条件至少包括切换过程中通信装置与第一网络设备之间发生无线链路失败RLF。处理单元，用于当满足触发条件时，记录成功切换报告SHR。其中，SHR至少指示触发条件。
在一种可能的设计中，SHR至少指示触发条件，包括：SHR至少指示发生RLF的原因。
在一种可能的设计中，RLF的原因包括以下至少一项：波束失败恢复失败，随机接入失败，重传次数达到最大次数，先听后说失败，RLF恢复失败，第二定时器超时，其中，第二定时器的运行时长指示通信装置检测到与第一网络设备之间有物理层问题的时长。
在一种可能的设计中，第一信息还包括随机接入的信息，随机接入的失败导致通信装置和第一网络设备发生RLF。
在一种可能的设计中，发送单元，还用于向第一网络设备发送SHR。其中，第一网络设备是通信装置在切换过程前接入的网络设备，SHR用于确定网络优化参数。
第二十二方面，本申请实施例提供一种通信装置，该通信装置可以为上述第十方面或第十方面任一种可能的设计中的第一网络设备，或者实现上述第一网络设备功能的芯片；所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括接收单元、处理单元和发送单元。其中，发送单元，用于向终端设备发送触发条件，其中，触发条件至少包括切换过程中终端设备与通信装置之间发生无线链路失败RLF，触发条件用于终端设备在满足触发条件的情况下记录成功切换报告SHR，SHR至少指示触发条件。接收单元，用于接收来自终端设备的SHR。处理单元，用于根据SHR确定网络优化参数。
第二十三方面，本申请实施例提供了一种通信装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，使得该通信装置执行上述任一方面或任一方面任一种可能的设计中终端设备所执行的方法。该通信装置可以为上述第一方面或第一方面任一种可能的设计中的终端设备，或者可以为上述第四方面或第四方面任一种可能的设计中的终端设备，或者可以为上述第十方面或第十方面任一种可能的设计中的终端设备，或者实现上述终端设备功能的芯片。
第二十四方面，本申请实施例提供了一种通信装置，包括：处理器；所述处理器与存储器耦合，用于读取存储器中的指令并执行，以使该通信装置执行如上述任一方面或任一方面任一种可能的设计中的终端设备所执行的方法。该通信装置可以为上述第一方面或第一方面任一种可能的设计中的终端设备，或者可以为上述第四方面或第四方面任一种可能的设计中的终端设备，或者可以为上述第十方面或第十方面任一种可能的设计中的终端设备，或者实现上述终端设备功能的芯片。
第二十五方面，本申请实施例提供一种芯片，包括处理电路和输入输出接口。其中，输入输出接口用于与芯片之外的模块通信，例如，该芯片可以为实现上述第一方面或第一方面任一种可能的设计中的终端设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第一方面或第一方面任一种可能的设计中的方法。再如，该芯片可以为实现上述第四方面或第四方面任一种可能的设计中的终端设备功能的芯片。处理电路用于运行计 算机程序或指令，以实现以上第四方面或第四方面任一种可能的设计中的方法。又如，该芯片可以为实现上述第十方面或第十方面任一种可能的设计中的终端设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第十方面或第十方面任一种可能的设计中的方法。
第二十六方面，本申请实施例提供了一种通信装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，使得该通信装置执行上述任一方面或任一方面任一种可能的设计中第一网络设备所执行的方法。该通信装置可以为上述第二方面或第二方面任一种可能的设计中的第一网络设备，或者可以为上述第五方面或第五方面任一种可能的设计中的第一网络设备，或者可以为上述第七方面或第七方面任一种可能的设计中的第一网络设备，或者可以为上述第八方面或第八方面任一种可能的设计中的第一网络设备，或者可以为上述第十一方面或第十一方面任一种可能的设计中的第一网络设备，或者实现上述第一网络设备功能的芯片。
第二十七方面，本申请实施例提供了一种通信装置，包括：处理器；所述处理器与存储器耦合，用于读取存储器中的指令并执行，以使该通信装置执行如上述任一方面或任一方面任一种可能的设计中的第一网络设备所执行的方法。该通信装置可以为上述第二方面或第二方面任一种可能的设计中的第一网络设备，或者可以为上述第五方面或第五方面任一种可能的设计中的第一网络设备，或者可以为上述第七方面或第七方面任一种可能的设计中的第一网络设备，或者可以为上述第八方面或第八方面任一种可能的设计中的第一网络设备，或者可以为上述第十一方面或第十一方面任一种可能的设计中的第一网络设备，或者实现上述第一网络设备功能的芯片。
第二十八方面，本申请实施例提供一种芯片，包括处理电路和输入输出接口。其中，输入输出接口用于与芯片之外的模块通信，例如，该芯片可以为实现上述第二方面或第二方面任一种可能的设计中的第一网络设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第二方面或第二方面任一种可能的设计中的方法。再如，该芯片可以为实现上述第五方面或第五方面任一种可能的设计中的第一网络设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第五方面或第五方面任一种可能的设计中的方法。又如，该芯片可以为实现上述第七方面或第七方面任一种可能的设计中的第一网络设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第七方面或第七方面任一种可能的设计中的方法。又如，该芯片可以为实现上述第八方面或第八方面任一种可能的设计中的第一网络设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第八方面或第八方面任一种可能的设计中的方法。又如，该芯片可以为实现上述第十一方面或第十一方面任一种可能的设计中的第一网络设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第十一方面或第十一方面任一种可能的设计中的方法。
第二十九方面，本申请实施例提供了一种通信装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，使得该通信装置执行上述任一方面或任一方面任一种可能的设计中第二网络设备所执行的方法。该通信装置可以为上述第三方面或第三方面任一种可能的设计中的第二网络设备，或者可以为上述第六方面或第六方面任一种可能的设计中的第二网络设备，或者可以为上述第九方面或第九方面任一种可能的设计中的第二网络设备，或者实现上述第二网络设备功能的芯片。
第三十方面，本申请实施例提供了一种通信装置，包括：处理器；所述处理器与存储器耦合，用于读取存储器中的指令并执行，以使该通信装置执行如上述任一方面或任一方面任一种可能的设计中的第二网络设备所执行的方法。该通信装置可以为上述第三方面或第三方面任一种可能的设计中的第二网络设备，或者可以为上述第六方面或第六方面任一种可能的设计中的第二网络设备，或者可以为上述第九方面或第九方面任一种可能的设计中的第二网络设备，或者实现上述第二网络设备功能的芯片。
第三十一方面，本申请实施例提供一种芯片，包括处理电路和输入输出接口。其中，输入输出接口用于与芯片之外的模块通信，例如，该芯片可以为实现上述第三方面或第三方面任一种可能的设计中的第二网络设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第三方面或第三方面任一种可能的设计中的方法。再如，该芯片可以为实现上述第六方面或第六方面任一种可能的设计中的第二网络设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第六方面或第六方面任一种可能的设计中的方法。又如，该芯片可以为实现上述第九方面或第九方面任一种可能的设计中的第二网络设备功能的芯片。处理电路用于运行计算机程序或指令，以实现以上第九方面或第九方面任一种可能的设计中的方法。
第三十二方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述任一方面中任一项的方法。
第三十三方面，本申请实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述任一方面中任一项的方法。
第三十四方面，本申请实施例提供一种电路系统，电路系统包括处理电路，处理电路被配置为执行如上述任一方面中任一项的方法。
第三十五方面，本申请实施例提供一种通信系统，该通信系统包括上述各个方面中任一项中的终端设备、第一网络设备和第二网络设备。或者，该通信系统包括上述各个方面中任一项中的终端设备和第一网络设备。
其中，第十二方面至第三十五方面中任一种设计所带来的技术效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
附图说明
图1为本申请的实施例应用的移动通信系统的架构示意图；
图2为本申请实施例提供的一种通信方法的流程示意图；
图3为本申请实施例提供的再一种通信方法的流程示意图；
图4为本申请实施例提供的又一种通信方法的流程示意图；
图5a为本申请实施例提供的又一种通信方法的流程示意图；
图5b为本申请实施例提供的又一种通信方法的流程示意图；
图6为本申请实施例提供的又一种通信方法的流程示意图；
图7为本申请实施例提供的又一种通信方法的流程示意图；
图8为本申请实施例提供的又一种通信方法的流程示意图；
图9为本申请实施例提供的又一种通信方法的流程示意图；
图10为本申请实施例提供的又一种通信方法的流程示意图；
图11为本申请实施例提供的又一种通信方法的流程示意图；
图12为本申请实施例提供的又一种通信方法的流程示意图；
图13为本申请实施例提供的又一种通信方法的流程示意图；
图14为本申请实施例提供的一种通信装置的结构示意图；
图15为本申请实施例提供的再一种通信装置的结构示意图。
具体实施方式
图1是本申请的实施例应用的通信系统1000的架构示意图。如图1所示，该通信系统1000包括至少一个网络设备(如图1中的110a和110b)和至少一个终端设备120(如图1中的120a-120j)。终端设备通过无线的方式与网络设备相连。图1只是示意图，该通信系统中还可以包括其它网络设备，如还可以包括无线中继设备和无线回传设备，在图1中未画出。
网络设备可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、第五代(5th generation，5G)移动通信系统中的下一代基站(next generation NodeB，gNB)、第六代(6th generation，6G)移动通信系统中的下一代基站、未来移动通信系统中的基站或WiFi系统中的接入节点等；也可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)，也可以是分布式单元(distributed unit，DU)。这里的CU完成基站的无线资源控制协议和分组数据汇聚层协议(packet data convergence protocol，PDCP)的功能，还可以完成业务数据适配协议(service data adaptation protocol，SDAP)的功能；DU完成基站的无线链路控制层和介质访问控制(medium access control，MAC)层的功能，还可以完成部分物理层或全部物理层的功能，有关上述各个协议层的具体描述，可以参考第三代合作伙伴计划(3rd generation partnership project，3GPP)的相关技术规范。网络设备可以是宏基站(如图1中的110a)，也可以是微基站或室内站(如图1中的110b)，还可以是中继节点或施主节点等。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。为了便于描述，下文以网络设备为例进行描述。
终端设备也可以称为终端、用户设备(user equipment，UE)、移动台、移动终端等。终端设备可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端设备可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、无人机、直升机、飞机、轮船、机器人、机械臂、智能家居设备等。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
网络设备和终端设备可以是固定位置的，也可以是可移动的。网络设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对网络设备和终端设备的应用场景不做限定。
网络设备和终端设备的角色可以是相对的，例如，图1中的直升机或无人机120i可以 被配置成移动基站，对于那些通过120i接入到无线接入网的终端设备120j来说，终端设备120i是网络设备；但对于网络设备110a来说，120i是终端设备，即110a与120i之间是通过无线空口协议进行通信的。当然，110a与120i之间也可以是通过基站与基站之间的接口协议进行通信的，此时，相对于110a来说，120i也是网络设备。因此，网络设备和终端设备都可以统一称为通信装置，图1中的110a和110b可以称为具有网络设备功能的通信装置，图1中的120a-120j可以称为具有终端设备功能的通信装置。
网络设备和终端设备之间、网络设备和网络设备之间、终端设备和终端设备之间可以通过授权频谱进行通信，也可以通过免授权频谱进行通信，也可以同时通过授权频谱和免授权频谱进行通信；可以通过6千兆赫(gigahertz，GHz)以下的频谱进行通信，也可以通过6GHz以上的频谱进行通信，还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请的实施例对无线通信所使用的频谱资源不做限定。
在本申请的实施例中，网络设备的功能也可以由网络设备中的模块(如芯片)来执行，也可以由包含有网络设备功能的控制子系统来执行。这里的包含有网络设备功能的控制子系统可以是智能电网、工业控制、智能交通、智慧城市等上述应用场景中的控制中心。终端设备的功能也可以由终端设备中的模块(如芯片或调制解调器)来执行，也可以由包含有终端设备功能的装置来执行。
在本申请中，网络设备向终端设备发送下行信号或下行信息，下行信息承载在下行信道上；终端设备向网络设备发送上行信号或上行信息，上行信息承载在上行信道上。终端设备为了与网络设备进行通信，需要与网络设备控制的小区建立无线连接。与终端设备建立了无线连接的小区称为该终端设备的服务小区。当终端设备与该服务小区进行通信的时候，还会受到来自邻区的信号的干扰。
为了便于理解本申请实施例，下面先对本申请实施例中涉及的术语做简单说明。应理解，这些说明仅为便于理解本申请实施例，而不应对本申请构成任何限定。
1、切换(handover，HO)：
在无线通信系统中，当终端设备从一个小区移动到另一个小区，或由于网络原因、业务负荷量调整、设备故障等原因，终端设备可能从源小区切换到目标小区，以保障终端设备与网络之间通信的连续性。上述过程即称为“切换”。其中，终端设备由于移动、网络原因、业务负荷量调整、设备故障等原因，发生切换之前接入的小区，称为源小区。源小区对应的网络设备，称为源网络设备。终端设备由于移动、网络原因、业务负荷量调整、设备故障等原因，发生切换之后接入的小区，称为目标小区。目标小区对应的网络设备，称为目标网络设备。
2、为了提高系统的移动可靠性和鲁棒性，引入双激活协议栈切换(dual active protocol stack handover，DAPS HO)。在DAPS切换过程中，终端设备使用两个协议栈。其中，一个协议栈用于与源小区对应的源网络设备通信，另一个协议栈用于与目标小区对应的目标网络设备通信。参见图2，DAPS切换的处理过程包括如下步骤：
可选的，S200、终端设备确定触发事件。
示例性的，触发事件可以是源小区的信号质量低于预设值。
应理解，在终端设备执行S200之前，或执行S200的过程中，终端设备通过源网络设 备与用户面功能(user plane function，UPF)网元进行用户面数据传输。
可选的，S201、终端设备向源网络设备发送测量报告。相应的，源网络设备接收来自终端设备的测量报告。
其中，测量报告包括源小区的参考信号接收质量、邻小区的参考信号接收质量等信息。
S202、源网络设备确定待接入的小区。比如源网络设备可以基于测量报告和/或无线资源管理(radio resource management，RRM)信息做出切换决定(handover decision)，确定待接入的小区。
S203、源网络设备向目标网络设备发送DAPS切换请求(handover request)消息。相应的，目标网络设备接收来自源网络设备的DAPS切换请求消息。
其中，DAPS切换请求消息用于请求将终端设备与源网络设备之间的连接切换至目标网络设备。
S204、目标网络设备执行接入控制(admission control)，如确定是否与终端设备建立连接，若是，则执行S205：
S205、目标网络设备向源网络设备发送DAPS切换请求确认(handover request acknowledge)消息。相应的，源网络设备接收来自目标网络设备的DAPS切换请求确认消息。
其中，DAPS切换请求确认消息指示目标网络设备是否接受DAPS切换。
示例性的，DAPS切换请求确认消息包括用于切换配置的消息，比如无线资源控制重配置(radio resource control reconfig，RRC Reconfig)消息。在新空口(new radio，NR)中，RRC重配置消息具有同步的重配ReconfigurationWithSync信元。在长期演进(long term evolution，LTE)中，RRC重配置消息具有移动控制信息MobilityControlInfo信元。其中，ReconfigurationWithSync信元和MobilityControlInfo信元均包括随机接入信息。随机接入信息用于终端设备进行随机接入。
S206、源网络设备向终端设备发送RRC重配置消息。相应的，终端设备接收来自源网络设备的RRC重配置消息。
其中，S206中的RRC重配置消息可以参见S205中的介绍，此处不再赘述。
需要说明的是，源网络设备并不读取RRC重配置消息中的内容，也不对RRC重配置消息中的内容进行修改，直接透传给终端设备。
可选的，S207、终端设备读取RRC重配置消息，并根据RRC重配置消息中的随机接入信息向目标小区对应的目标网络设备发起RACH过程。相应的，目标小区对应的目标网络设备执行与终端设备之间的RACH过程。其中，RACH过程的详细介绍可以参见相关技术，此处不再赘述。在DAPS切换过程中，终端设备在收到RRC重配置消息后不与源网络设备断开连接。
在RACH过程结束之后，终端设备执行S208：
S208、终端设备向目标网络设备发送RRC重配置完成消息。相应的，目标网络设备接收来自终端设备的RRC重配置完成消息。
S209、目标网络设备向源网络设备发送切换成功(HO success)消息。相应的，源网络设备接收来自目标网络设备的切换成功消息。
作为一种实现方式，对于源网络设备而言，源网络设备执行S209之后，不再与终端 设备进行上行数据和下行数据的传输。
需要说明的是，在图2所示的DAPS切换过程中，目标网络设备在执行S207之后，向终端设备发送释放消息。相应的，终端设备接收来自目标网络设备的释放消息。其中，释放消息指示释放终端设备与源网络设备之间的连接。终端设备根据释放消息，再释放自身与源网络设备之间的连接。
也就是说，在DAPS切换过程中，终端设备与源网络设备之间的连接未释放。在终端设备与目标网络设备之间切换成功之后，终端设备才释放与源网络设备之间的连接，以实现用户面传输的零毫秒中断，但终端设备与源网络设备之间的控制面信令不再进行交互。
然而，在终端设备和目标网络设备之间的RACH过程成功之前，可能存在如下情况：终端设备与网络设备之间的用户面传输中断。但终端设备成功切换至目标网络设备，相关协议中仍将上述情况归类为成功切换(successful handover)。其中，导致用户面传输中断的因素包括但不限于以下至少一项：第一项，终端设备检测到自身与源小区之间的连接发生无线链路失败(radio link failure，RLF)；第二项，源网络设备调度不合理，导致终端设备接收到重复的数据包。
3、无线链路失败报告(radio link failure report，RLF report)、成功切换报告(successful handover report，SHR)
目前，系统支持移动鲁棒性优化(mobility robustness optimization，MRO)机制。MRO是网络自优化的一个重要机制。终端设备发生与移动性相关的异常情况(例如切换失败、在目标小区的无线链路失败等)时，向网络设备上报发生移动性相关的异常参数。网络设备可以对终端设备上报的移动性参数进行自主分析，确定网络优化参数。其中，移动性参数可以承载于RLF报告或SHR。
其中，当终端设备发生了连接失败，终端设备记录RLF report。当终端设备再次发生连接失败，终端设备清空之前记录的RLF report，记录最新的RLF report。示例性的，RLF报告包括如下至少一种失败信息：
1)失败的主小区标识(failed primary cell identity，failedPcellID)，即failedPcellID是终端设备检测到RLF的小区信息，或者切换失败的目标小区信息。
2)连接失败类型(connectionFailureType)，如RLF或者HOF或者定时器T312到期。其中，定时器T312是终端设备发送测量报告后启动的定时器。
3)前主小区标识(previous primary cell identity，previousPCellId)，即终端设备上一次收到切换消息的源小区信息。
4)重建立小区标识(reestablishment cell identity，reestablishmentCellId)，即连接失败后发起重建立的小区信息。
5)连接失败时间(timeConnFailure)，即终端设备最后一次收到切换消息到连接失败的时间。
6)连接失败时开始记录的时间长度(timeSinceFailure)，一般指连接失败到上报RLF report的时间长度。
示例性的，RLF report的介绍可以参考相关协议，如3GPP TS 38.331中的UEInformationResponse内的描述，此处不再赘述。
其中，SHR是为了识别移动性成功场景下的潜在移动性失败的问题，而引入终端设备 记录和上报切换成功过程中的参数的报告。SHR包括潜在失败的成功切换的移动性相关的信息。源网络设备可以结合SHR和终端设备的上下文，来对终端设备的移动性进行优化。
示例性的，SHR触发条件(SHR trigger condition)包括以下至少一项：
第一项，定时器T310的运行时长大于或等于阈值1。其中，定时器T310的运行时长指示终端设备检测到与源网络设备之间有物理层问题(physical layer problems)的时长。启动定时器T310之后，该定时器T310运行期间，如果无线链路恢复，则该定时器T310停止。该定时器T310的运行时长大于或等于阈值X时，终端设备确定发生无线链路失败。其中，阈值1和阈值X是不同的阈值。通常，阈值1小于阈值X。
第二项，定时器T312的运行时长大于或等于阈值2。其中，定时器T312在定时器T310的运行期间启动。定时器T312的运行时长指示在定时器T312的运行期间，终端设备触发测量报告至终端设备与源网络设备恢复同步之间的时长。该定时器T312的运行时长大于或等于阈值Y时，终端设备确定发生无线链路失败。其中，阈值2和阈值Y是不同的阈值。通常，阈值2小于阈值Y。
第三项，定时器T304的运行时长大于或等于阈值3。其中，定时器T304的运行时长指示终端设备接收RRC重配置消息之后未接入目标网络设备的时长。终端设备在接收到RRC重配置消息时启动定时器T304，定时器T304的运行时长大于或等于阈值Z时，终端设备确定发生切换失败。其中，阈值3和阈值Z是不同的阈值。通常，阈值3小于阈值Z。
需要说明的是，上述阈值X、阈值Y和阈值Z可以由信元RLF-TimersAndConstants配置，与SHR触发条件中配置的阈值1、阈值2和阈值3不同。
示例性的，SHR触发条件承载于RRC重配置消息中。如此，终端设备通过接收RRC重配置消息来接收SHR触发条件。终端设备在确定满足SHR触发条件的情况下，记录SHR。然后，终端设备向源网络设备发送SHR，以使源网络设备确定网络优化参数。
需要说明的是，潜在移动性失败并不代表真正的失败，而是终端设备在切换的过程中，遇到了临近切换失败的现象，所以记录了SHR。例如，配置的是20ms内，终端设备能切换到目标小区就是成功切换，但是若阈值为18ms，终端设备经过19ms才切换成功。这种情况就属于潜在移动性失败。其中，终端设备的上下文，也可以描述为用户设备(user equipment，UE)上下文。示例性的，终端设备的上下文包括终端设备的鉴权信息，终端设备的网络能力信息等。
然而，在切换成功的情况下，终端设备也可能存在与网络设备之间的用户面传输中断的情况，如上述潜在移动性失败的问题。即使终端设备配置了SHR触发条件，但终端设备确定不满足SHR触发条件，终端设备也不记录SHR。并且，SHR触发条件的配置是非强制性的，网络侧有可能不为终端设备配置SHR触发条件。如此，终端设备可能并未记录SHR，从而造成网络侧无法优化处理用户面传输中断的问题。
有鉴于此，本申请实施例提供通信方法，本申请实施例通信方法(如第一种通信方法、第二种通信方法、第三种通信方法、或第四种通信方法)可以应用于图1所示的通信系统。在本申请实施例提供的通信方法中，切换过程以上述DAPS切换过程为例进行介绍，第一网络设备是终端设备在切换过程前接入的网络设备，即源网络设备，第二网络设备是终端设备在切换过程后接入的网络设备，即目标网络设备。本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字。在 此统一说明，以下不再赘述。本申请实施例中，第一网络设备可以是源基站，第二网络设备可以是目标基站，第一网络设备和第二网络设备可以是同一个网络设备。
在本申请实施例提供的第一种通信方法中，终端设备接收来自第一网络设备的指示信息。其中，指示信息指示第一阈值。当切换过程中用户面传输中断时长大于或等于第一阈值时，终端设备记录第一报告。其中，第一报告指示用户面传输中断时长。这样一来，终端设备也就能够基于用户面传输中断时长，来触发第一报告的记录。由于第一报告包括用户面传输中断时长，所以，即使终端设备成功接入第二网络设备，但终端设备存在用户面传输中断的现象，第一报告也能够记录用户面传输中断时长，避免现有技术中此种情况下终端设备无法记录报告的问题，也为网络侧确定优化参数奠定了基础。
如图3所示，本申请实施例提供的第一种通信方法300包括如下步骤：
S301、第一网络设备获取指示信息。
其中，指示信息用于终端设备确定第一阈值。第一阈值用于触发终端设备记录第一报告，具体参见S303的描述，此处不再赘述。示例性的，指示信息可以直接指示第一阈值的取值。例如，第一阈值为10毫秒，指示信息包括“10毫秒”这一信息。或者，指示信息可以间接指示第一阈值的取值。例如，字符和第一阈值的取值之间存在一定的对应关系，如表1-1所示。
表1-1
指示信息为字符 第一阈值(单位：毫秒)
1 5
2 10
3 15
在表1-1中，数字“1”对应的第一阈值为5毫秒，数字“2”对应的第一阈值为10毫秒，数字“3”对应的第一阈值为15毫秒。应理解，在表1-1中，仅以第一阈值的取值为5毫秒、10毫秒、15毫秒为例进行介绍，第一阈值还可以有其他取值，本申请实施例对此不作限定。在表1-1中，仅以数字(如“1”、“2”、“3”)与第一阈值存在对应关系为例进行介绍，当然与第一阈值存在对应关系的还可以是字母、符号等，本申请实施例对此不作限定。
结合表1-1，在指示信息携带数字“1”的情况下，终端设备根据表1-1和指示信息中携带的数字，即可确定第一阈值为5毫秒。在指示信息携带数字“2”的情况下，终端设备根据表1和指示信息中携带的数字，即可确定第一阈值为10毫秒。在指示信息携带数字“3”的情况下，终端设备根据表1-1和指示信息中携带的数字，即可确定第一阈值为15毫秒。
或者，指示信息可以间接指示第一阈值的取值。例如，指示信息指示第一阈值和对应的失败阈值之间的对应关系，如表1-2所示。若失败阈值为100ms，终端设备根据指示信息和失败阈值确定第一阈值如表1-2所示。
表1-2
指示信息为百分比 第一阈值(单位：毫秒)
50％ 50
60％ 60
80％ 80
需要说明的是，上述仅是示例性的给出了指示信息指示第一阈值的方式，当然，指示信息也可以通过其他方式来指示第一阈值，本申请实施例对此不作限定。
用户面传输中断时长，可以指用户面传输中断起始标识至终止标识的时间间隔。示例性的，时间间隔的单位包括以下其中任一项：毫秒(millisecond)、符号(symbol)、时隙(slot)等。该起始标识和/或终止标识可以是协议预定义的，比如协议预定义用户面传输中断时长为“终端设备和第一网络设备之间成功传输的最后一个数据包(比如成功接收来自第一网络设备的最后一个数据包，或成功向第一网络设备发送的最后一个数据包，或者上述两者之间时间上靠后的数据包)”到“终端设备和第二网络设备之间成功传输的首个数据包(比如成功接收来自第二网络设备的首个数据包，或成功向第二网络设备发送的首个数据包，或者上述两者之间时间上靠前的数据包)”之间的时间间隔。或者，指示信息可以用于指示用于确定用户面传输中断时长的起始标识和/或终止标识。
示例性的，作为第一种可能的实现方式，用户面传输中断的起始标识包括以下其中一项：
起始标识1a，终端设备向第一网络设备成功发送最后一个数据包。示例性的，终端设备向第一网络设备成功发送最后一个数据包，具体过程包括：终端设备监控数据包的发送状态。在终端设备监控到向第一网络设备成功发送的一个数据包(如记为数据包A)之后，若终端设备又监控到向第一网络设备成功发送的数据包(如记为数据包B)，则终端设备确定数据包A不是成功发送的最后一个数据包，并且，终端设备继续监控数据包B之后的数据包是否发送成功，如此循环，直至终端设备监控到无法再继续向第一网络设备发送后续数据包(如记为数据包D、数据包E、数据包F等)。此种情况下，终端设备将数据包C，确定为终端设备向第一网络设备成功发送的最后一个数据包。其中，数据包C与数据包B可以是同一数据包，也可以是不同的数据包，如数据包B之后发送的数据包。反之，在终端设备监控到向第一网络设备成功发送的一个数据包(如记为数据包A)之后，若终端设备监控到无法再继续向第一网络设备发送后续数据包(如记为数据包B、数据包C、数据包D等)，则终端设备确定数据包A为终端设备向第一网络设备成功发送的最后一个数据包。也可以理解为，终端设备向第一网络设备成功发送的最后一个数据包的后续相邻数据包是发送失败的数据包。
起始标识2a，终端设备成功接收来自第一网络设备的最后一个数据包。示例性的，终端设备成功接收来自第一网络设备的最后一个数据包，具体过程包括：终端设备监控数据包的接收状态。在终端设备监控到成功接收的来自第一网络设备的一个数据包(如记为数据包A)之后，若终端设备又监控到成功接收的来自第一网络设备的数据包(如记为数据包B)，则终端设备确定数据包A不是成功接收的最后一个数据包，并且，终端设备继续监控数据包B之后的数据包是否接收成功，如此循环，直至终端设备监控到无法再接续接收后续数据包(如记为数据包D、数据包E、数据包F等)。此种情况下，终端设备将数据包C，确定为终端设备成功接收的来自第一网络设备的最后一个数据包。其中，数据包C与数据包B可以是同一数据包，也可以是不同的数据包，如数据包B之后成功接收的来自第一网络设备的数据包。反之，在终端设备监控到成功接收的来自第一网络设备的一个数据包(如记为数据包A)之后，若终端设备监控到无法再继续接收后续数据包(如记为 数据包B、数据包C、数据包D等)，则终端设备确定数据包A为终端设备成功接收的来自第一网络设备的最后一个数据包。也可以理解为，终端设备成功接收的来自第一网络设备的最后一个数据包的后续相邻数据包是接收失败的数据包。
用户面传输中断的终止标识包括以下其中一项：
终止标识1a，终端设备向第二网络设备成功发送首个数据包。
终止标识2a，终端设备成功接收来自第二网络设备的首个数据包。
应理解，在第一种可能的实现方式中，起始标识和终止标识可以任意组合。例如，用户面传输中断时长，可以是指，终端设备向第一网络设备成功发送最后一个数据包，与终端设备向第二网络设备成功发送首个数据包之间的时长。相应的，指示信息指示的起始标识为上述起始标识1a。指示信息指示的终止标识为上述终止标识1a。再如，用户面传输中断时长，可以是指，终端设备向第一网络设备成功发送最后一个数据包，与终端设备向第二网络设备成功发送首个数据包之间的时长。相应的，指示信息指示的起始标识为上述起始标识1a。指示信息指示的终止标识为上述终止标识2a。又如，用户面传输中断时长，可以是指，终端设备成功接收来自第一网络设备的最后一个数据包，与终端设备向第二网络设备成功发送首个数据包之间的时长。相应的，指示信息指示的起始标识为上述起始标识2a。指示信息指示的终止标识为上述终止标识1a。又如，用户面传输中断时长，可以是指，终端设备成功接收来自第一网络设备的最后一个数据包，与终端设备向第二网络设备成功发送首个数据包之间的时长。相应的，指示信息指示的起始标识为上述起始标识2a。指示信息指示的终止标识为上述终止标识2a。
示例性的，作为另一种可能的实现方式，用户面传输中断的起始标识包括以下其中一项：
起始标识1b，终端设备与第一网络设备之间出现下行失步(out-of-sync)。
起始标识2b，终端设备与第一网络设备之间发生RLF。示例性的，终端设备确定定时器T310(或定时器T312)超时时，确定与第一网络设备之间发生RLF。其中，终端设备确定发生RLF的过程可以参见相关现有技术，此处不再赘述。
起始标识3b，第二定时器启动。其中，第二定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。示例性的，第二定时器可以是上述定时器T310。
起始标识4b，第三定时器启动。其中，第三定时器的运行时长指示在上述第三定时器运行期间，终端触发测量报告至终端设备与第一网络设备恢复同步之间的时长。示例性的，第三定时器可以是上述定时器T312。
起始标识5b，终端设备成功接收到重复的数据包。
中断定时器的终止标识包括以下其中一项：
终止标识1b，终端设备与第二网络设备之间的随机接入过程完成。
终止标识2b，终端设备发送RRC重配置完成(RRCReconfigurationComplete)消息完成。
终止标识3b，终端设备与第二网络设备之间下行同步。
终止标识4b，第二定时器停止。
终止标识5b，第三定时器停止。
应理解，在第二种可能的实现方式中，起始标识和终止标识可以任意组合。例如，用 户面传输中断时长，可以是指，第二定时器启动，与第二定时器停止之间的时长。相应的，指示信息指示的起始标识为上述起始标识3b。指示信息指示的终止标识为上述终止标识4b。当然，在第二种可能的实现方式中，起始标识和终止标识还可以有其他的组合形式，此处不再一一列举。容易理解的是，上述第一种可能的实现方式和第二种可能的实现方式之间的起始标识和终止标识也可以任意组合。例如，用户面传输中断时长，可以是指，终端设备向第一网络设备成功发送最后一个数据包，与第二定时器停止之间的时长。相应的，指示信息指示的起始标识为上述起始标识1a。指示信息指示的终止标识为上述终止标识4b。当然，在上述两种可能的实现方式(即上述第一种可能的实现方式和第二种可能的实现方式)之间，起始标识和终止标识还可以有其他的组合形式，此处不再一一列举。
其中，S301的具体实现过程包括但不限于如下两种方式(下述方式1和方式2)：
方式1，如图4中“方式1”所在的虚线框所示，第一网络设备执行S301a：
S301a、第一网络设备确定指示信息。
示例性的，第一网络设备确定第一阈值的取值大小。
可选地，在指示信息还指示用户面传输中断的起始标识的情况下，第一网络设备从上述起始标识1a～2a(或起始标识1b～5b、或起始标识1a～2a和起始标识1b～5b)中，确定指示信息所指示的起始标识。在指示信息还指示用户面传输中断的终止标识的情况下，第一网络设备从上述终止标识1a～2a(或终止标识1b～5b、或终止标识1a～2a和终止标识1b～5b)中，确定指示信息所指示的终止标识。
方式2，如图4中“方式2”所在的虚线框所示，第二网络设备执行S301b和S301c：
S301b、第二网络设备确定指示信息。
示例性的，作为第一种可能的实现方式，第二网络设备自主确定指示信息。此种情况下，S301b的实现过程可以参见S301a的介绍，区别点在于，S301a的执行主体为第一网络设备，而S301b的执行主体为第二网络设备，此处不再赘述。
S301c、第二网络设备向第一网络设备发送指示信息。相应的，第一网络设备接收来自第二网络设备的指示信息。
示例性的，从承载的消息上来说，指示信息可以承载于HO请求确认消息中，也可以承载于其他消息，或者也可以单独传输。从传输的时间上来说，指示信息可以与HO请求确认消息同时传输，也可以在HO请求确认消息之前传输，本申请实施例对此不作限定。其中，HO请求确认消息可以是DAPS切换请求确认消息，具体可以参见S205的介绍，此处不再赘述。
需要说明的是，HO请求确认消息包括RRC重配置消息。指示信息承载于HO请求确认消息，可以有两种实现方式：第一种实现方式中，指示信息承载于RRC重配置消息中；第二种实现方式中，指示信息承载于RRC重配置消息外，且承载于HO请求确认消息中。进一步地，在指示信息承载于RRC重配置消息中的情况下，指示信息可以承载于SHR触发条件中，也可以是独立于SHR触发条件的，如指示信息承载于SHR触发条件之外，且承载于RRC重配置消息中，本申请实施例对此不作限定。其中，SHR触发条件的介绍可以参见名词解释部分中关于SHR的介绍，此处不再赘述。
在方式2的S301b中，作为第二种可能的实现方式，第二网络设备基于参考信息确定指示信息。如图5a所示，本申请实施例通信方法300还包括：
S301d、第一网络设备向第二网络设备发送信息A。相应的，第二网络设备接收来自第一网络设备的信息A。
其中，信息A包括参考信息(如图5a中“方式一”所在的方框所示)和/或请求信息(如图5a中“方式二”所在的方框所示)。
如图5a中“方式一”所在的方框所示，以信息A包括参考信息为例进行介绍，参考信息指示第一网络设备确定的初始阈值。可选地，参考信息还指示第一网络设备确定的初始标识，如初始的起始标识，初始的终止标识等。例如，第一网络设备从上述起始标识1a～2a(或起始标识1b～5b、或起始标识1a～2a和起始标识1b～5b)中，确定参考信息所指示的，且用于第二网络设备参考的起始标识。此种情况下，参考信息还指示用户面传输中断的，且用于第二网络设备参考的起始标识。再如，第一网络设备从上述终止标识1a～2a(或终止标识1b～5b、或终止标识1a～2a和终止标识1b～5b)中，确定参考信息所指示的，且用于第二网络设备参考的终止标识。此种情况下，参考信息还指示用户面传输中断的，且用于第二网络设备参考的终止标识。
示例性的，从承载的消息上来说，参考信息可以承载于HO请求消息中，也可以承载于其他消息，还可以单独传输。从传输的时间上来说，参考信息可以与HO请求消息同时传输，也可以在HO请求消息之前传输，本申请实施例对此不作限定。其中，HO请求消息可以是DAPS切换请求消息，具体可以参见S203的介绍，此处不再赘述。
应理解，在参考信息与HO请求消息同时传输的情况下，S301c中的指示信息与HO请求确认消息同时传输。在参考信息在HO请求消息之前传输的情况下，S301c中的指示信息可以与HO请求确认消息同时传输，也可以在HO请求确认消息之前传输，本申请实例对此不作限定。
在第二网络设备执行S301d的情况下，如图5a中“方式一”所在的方框所示，S301b的具体实现过程包括：第二网络设备基于参考信息确定指示信息。其中，S301b中的参考信息与S301d中的参考信息一致。例如，参考信息指示至少一个初始阈值。第二网络设备对参考信息指示的某一个初始阈值进行修改，并将修改后的数值作为第一阈值。当然，第二网络设备也可以不作修改，将参考信息指示的一个初始阈值作为指示信息指示的第一阈值，本申请实施例对此不作限定。再如，参考信息指示至少两个初始阈值。第二网络设备从参考信息指示的至少两个初始阈值中选择一个初始阈值，作为第一阈值。
可选的，在参考信息还指示至少一个初始的起始标识的情况下，第二网络设备对参考信息指示的某一个起始标识进行修改，并将修改后的起始标识作为指示信息指示的起始标识。当然，第二网络设备也可以不作修改，将参考信息指示的一个初始的起始标识作为指示信息指示的起始标识，本申请实施例对此不作限定。在参考信息还指示至少两个初始的起始标识的情况下，第二网络设备从参考信息指示的至少两个起始标识中选择一个标识，作为指示信息指示的起始标识。
可选的，在参考信息还指示至少一个初始的终止标识的情况下，第二网络设备对参考信息指示的某一个终止标识进行修改，并将修改后的终止标识作为指示信息指示的终止标识。当然，第二网络设备也可以不作修改，将参考信息指示的一个初始的终止标识作为指示信息指示的终止标识，本申请实施例对此不作限定。在参考信息还指示至少两个初始的终止标识的情况下，第二网络设备从参考信息指示的至少两个终止标识中选择一个标识， 作为指示信息指示的终止标识。
如图5a中“方式二”所在的方框所示，以信息A包括请求信息为例进行介绍，请求信息请求第二网络设备配置指示信息。也就是说，在第一网络设备不执行S301a的情况下，第一网络设备请求第二网络设备配置指示信息。在第二网络设备执行S301d的情况下，如图5a中“方式二”所在的方框所示，S301b的具体实现过程包括：第二网络设备根据请求信息确定指示信息。也就是说，第二网络设备是响应于请求信息，才配置指示信息的，以简化第二网络设备的处理复杂程度。
在一些实施例中，如图5b所示，本申请实施例通信方法300还包括S301e和S301f。其中，第一网络设备可以先执行S301f(如情况1的介绍)，第一网络设备也可以先执行S301e和S301f。其中，S301e和S301f的介绍如下：
S301e、第一网络设备向第二网络设备发送信息X。相应的，第二网络设备接收来自第一网络设备的信息X。
其中，信息X用于请求第二网络设备反馈是否支持SHR功能。支持SHR功能，可以理解为，具备接收SHR、识别SHR、向其它网络设备发送SHR、或读取SHR中信息的能力等的至少一种。
示例性的，第一网络设备在发送HO请求消息之前，执行S301e。
S301f、第二网络设备向第一网络设备发送信息Y。相应的，第一网络设备接收来自第二网络设备的信息Y。
其中，信息Y指示第二网络设备是否支持SHR功能。
示例性的，第二网络设备执行S301e之后，根据信息X和自身的设备能力，确定信息Y，然后，执行S301f。
作为又一种可能的实现方式，若第二网络设备不支持SHR功能，可能无法识别S301e中的信息X，在S301f中也可以不携带任何指示SHR功能的信息，即若步骤S301f中没有携带是否支持SHR功能的信息，也可以理解为第二网络设备不支持SHR功能。
通过上述S301e和S301f，或上述S301f，第一网络设备即可获知第二网络设备是否支持SHR功能。在信息Y指示第二网络设备支持SHR功能的情况下，第一网络设备执行S301d或S301a，从而配置指示信息。反之，在信息Y指示第二网络设备不支持SHR功能的情况下，第一网络设备不执行S301d和S301a，从而避免浪费传输资源。
需要说明的是，S301e和S301f均是可选的步骤。第一网络设备可以不执行S301e和S301f，而直接执行S301d或S301a。在第二网络设备支持SHR功能的情况下，若第二网络设备执行S301d，第二网络设备即可成功接收和识别信息A，基于信息A来确定指示信息，可以参见S301中方式2的第二种实现方式的介绍，此处不再赘述。在第二网络设备不支持SHR功能的情况下，第二网络设备无法识别信息A。此种情况下，第二网络设备不执行SS301b和S301c，第一网络设备也不执行S301a。由于S301e和S301f未执行，节省了传输资源的开销。作为一种方式，第一网络设备可以执行S301f，但不执行S301e。也就是说，第二网络设备主动向第一网络设备提供自身是否支持SHR功能，以使得第一网络设备获知第二网络设备是否支持SHR功能，避免信息A的传输导致的传输资源浪费。作为另一种方式，第一网络设备可以执行S301e和S301f。也就是说，第二网络设备是响应于第一网络设备的请求，才执行S301f，以简化第二网络设备的处理复杂程度。
S302、第一网络设备向终端设备发送指示信息。相应的，终端设备接收来自第一网络设备的指示信息。
其中，S302中的指示信息与S301中的指示信息一致。
示例性的，从承载的消息上来说，指示信息可以承载于RRC重配置消息中，也可以承载于其他消息(如RRC建立(RRCSetup)消息、RRC重建立(RRCReestablishment)消息、RRC恢复(RRCResume)消息、或系统消息)，还可以单独传输。进一步地，指示信息承载于RRC重配置消息中的情况，可以参见S301c的介绍，此处不再赘述。
示例性的，从传输的时间上来说，指示信息可以与RRC重配置消息同时传输，也可以在RRC重配置消息之前传输，如通过RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息传输，本申请实施例对此不作限定。
应理解，在S301c中的指示信息与HO请求确认消息同时传输的情况下，S302中的指示信息与RRC重配置消息同时传输。在S301c中的指示信息在HO请求确认消息之前传输的情况下，S302中的指示信息可以与RRC重配置消息同时传输，也可以在RRC重配置消息之前传输，本申请实例对此不作限定。
S303、当切换过程中用户面传输中断时长大于或等于第一阈值时，终端设备记录第一报告。
其中，第一报告指示用户面传输中断时长。示例性的，第一报告包括预设数量的比特，第一报告通过预设数量的比特来指示用户面传输中断时长。其中，用户面传输中断时长的定义可以参见S301的介绍，此处不再赘述。可选的，第一报告还指示以下至少一项：
第一项，触发记录第一报告的原因，如用户面传输中断时长大于或等于第一阈值，或定时器T310的运行时长大于或等于定时器T310对应的阈值，或定时器T312的运行时长大于或等于定时器T312对应的阈值。
第二项，用户面传输中断的起始标识。
第三项，用户面传输中断的停止标识。
第四项，源小区的无线网络临时标识(source cell radio network temporary identifier，CRNTI)。
第五项，重复接收的数据包的数量。示例性的，在用户面传输中断时长内或者DAPS切换过程中，终端设备接收重复的数据包，且记录重复接收的数据包的数量。
第六项，重复接收的数据包的比例。示例性的，在用户面传输中断时长内或者DAPS切换过程中，终端设备接收重复的数据包(如记为第一数据包)，以及未重复的数据包(如记为第二数据包)，且记录第一数据包的数量(如记为x个数据包)和第二数据包的数量(如记为y个数据包)。重复接收的数据包的比例满足如下公式(1)或公式(2)：
K＝x/y      公式(1)
其中，K表示重复接收数据包的比例，x表示第一数据包的数量，y表示第二数据包的数量。
K＝x/(x+y)     公式(2)
其中，K表示重复接收数据包的比例，x表示第一数据包的数量，y表示第二数据包的数量。
应理解，上述公式(1)和公式(2)仅是示例性的给出了重复接收的数据包的比例满 足的计算公式，当然，终端设备还可以根据其他计算方式，本申请实施例对此不作限定。
需要说明的是，上述第一项至第四项，适用于用户面传输中断的起始标识和终止标识实现为第一种可能的实现方式和第二种可能的实现方式的情况，详见S301的介绍，此处不再赘述。上述第五项和第六项，适用于用户面传输中断的起始标识和终止标识实现为第二种可能的实现方式的情况，详见S301的介绍，此处不再赘述。其中，重复接收的数据包的数量(或比例)，能够表征第一网络设备数据调度不合理的程度。例如，第一网络设备数据调度不合理程度越高，重复接收的数据包的数量越大，重接接收的数据包的比例也就越高。
应理解，第一报告，也可以有其他名称，如SHR，本申请实施例对此不作限定。在本申请实施例中，仅以第一报告为例进行介绍。
示例性的，S303的具体实现过程可以包括但不限于如下介绍：在第一定时器的运行时长大于或等于第一阈值的情况下，终端设备记录第一报告。
其中，第一定时器的运行时长指示用户面传输中断时长。也就是说，第一定时器的启动标识与用户面传输中断时长的起始标识相同。例如，当终端设备与第一网络设备之间发生RLF时，第一定时器启动。第一定时器的停止标识与用户面传输中断时长的终止标识相同。例如，当终端设备向第二网络设备成功发送首个数据包时，第一定时器停止。若第一定时器一直运行，且运行时长超过第一阈值，则终端设备记录第一报告。
应理解，第一定时器，也可以描述为其他名称，如中断定时器(interruption timer)，本申请实施例对此不作限定。相应的，在第一定时器描述为中断定时器的情况下，第一阈值也可以描述为中断定时器阈值(interruption timer threshold)，当然，第一阈值也可以有其他名称，本申请实施例对此不作限定。在本申请实施例中，均以第一定时器和第一阈值为例进行介绍。
需要说明的是，在本申请实施例中，仅以第一定时器的运行时长为例，来呈现用户面传输中断时长。当然，终端设备也可以采用其他方式来记录用户面传输中断时长，如终端设备自身记录一个时长，本申请实施例对此不作限定。
S304、终端设备向第一网络设备发送第一报告。相应的，第一网络设备接收来自终端设备的第一报告。
其中，S304中的第一报告与S303中的第一报告一致。
示例性的，S304的实现过程包括但不限于如下三种方式：
方式1，终端设备直接向第一网络设备发送第一报告。相应的，第一网络设备直接接收来自终端设备的第一报告。
方式2，S304的实现过程包括两个步骤1a和步骤2a：
步骤1a，终端设备向第二网络设备发送第一报告。相应的，第二网络设备直接接收来自终端设备的第一报告。
步骤2a，第二网络设备向第一网络设备发送第一报告。相应的，第一网络设备接收来自第二网络设备的第一报告。可选的，第二网络设备可以通过第二网络设备和第一网络设备之间的接口向第一网络设备发送第一报告，或者，第二网络设备可以通过核心网设备向第一网络设备发送第一报告。
方式3，S304的实现过程包括两个步骤1b和步骤2b：
步骤1b，终端设备向第三网络设备发送第一报告。相应的，第三网络设备直接接收来自终端设备的第一报告。
其中，第三网络设备是除第一网络设备和第二网络设备之外的网络设备。并且，第三网络设备支持SHR功能，且能够与终端设备进行信息交互。其中，支持SHR功能的介绍可以参见S301e的介绍，此处不再赘述。
步骤2b，第三网络设备向第一网络设备发送第一报告。相应的，第一网络设备接收来自第三网络设备的第一报告。可选的，第三网络设备可以通过第三网络设备和第一网络设备之间的接口向第一网络设备发送第一报告，或者，第三网络设备可以通过核心网设备向第一网络设备发送第一报告。
应理解，S304中的方式1、方式2和方式3仅是示例性的介绍了第一报告的传输过程。当然，终端设备还可以采用其他的方式，向第一网络设备提供第一报告，本申请实施例对此不作限定。另外，终端设备也可以执行S303之后，不执行S304，即终端设备不发送第一报告。可选地，在一段时间之后，终端设备删除上述第一报告，以节省终端设备的存储资源。
S305、第一网络设备根据第一报告，确定网络优化参数。
示例性的，第一网络设备可以结合第一报告和终端设备的上下文，来对终端设备的移动性进行优化，以得到网络优化参数，从而优化处理潜在移动性失败的问题。
在本申请实施例通信方法300中，指示信息指示第一阈值，终端设备在用户面传输中断时长大于或等于第一阈值的情况下，记录第一报告。其中，第一报告包括用户面传输中断时长。即使终端设备成功接入第二网络设备，但切换过程中终端设备存在用户面传输中断的现象，第一报告也能够记录用户面传输中断时长，避免现有技术中终端设备无法记录报告的问题，也为网络侧确定优化参数奠定了基础。
容易理解的是，在本申请实施例第一种通信方法300中，终端设备与网络设备之间的用户面传输中断，可以描述为，在DAPS切换过程中，终端设备与源网络设备之间的用户面传输中断，也可以描述为，在DAPS切换过程中，终端设备与源网络设备之间的用户面传输中断，且未与目标网络设备之间进行用户面传输。
应理解，本申请实施例第一种通信方法300也可以适用于其他场景，如双连接(dual－connectivity，DC)场景，即终端设备同时与两个网络设备建立通信连接。上述两个网络设备中包括一个主网络设备(如主站(master gNB，MgNB))和一个辅网络设备(如辅站(seconary gNB，SgNB))。在主网络设备发生切换的情况下，上述第一网络设备可以是源主站，第二网络设备可以是目标主站，具体实现过程可以参见通信方法300的介绍，此处不再赘述。在辅网络设备发生切换的情况下，上述第一网络设备可以是源辅站，第二网络设备可以是目标辅站，具体实现过程可以参见通信方法300的介绍，此处不再赘述。
需要说明的是，在本申请实施例第一种通信方法300中，仅以第一报告的触发条件为“切换过程中用户面传输中断时长大于或等于第一阈值”为例进行描述。
下面，本申请实施例还提供第五种通信方法。在本申请实施例提供的第五种通信方法中，终端设备接收来自第一网络设备的触发条件。其中，触发条件至少包括切换过程中终端设备与第一网络设备之间发生RLF。当满足触发条件时，终端设备记录SHR。其中，SHR至少指示终端设备满足的触发条件。这样一来，在切换过程中，若终端设备与第一网络设 备之间发生RLF，则终端设备记录此情况，即上述SHR至少指示终端设备满足的触发条件，以指示终端设备与第一网络设备之间发生RLF，避免现有技术中此种情况下终端设备无法记录的问题，也为网络侧确定优化参数奠定了基础。
如图13所示，本申请实施例提供的第五种通信方法1300包括如下步骤：
S1301、第一网络设备获取触发条件。
其中，触发条件包括以下至少一项：
第一项，用户面传输中断的时长大于或等于第一阈值。其中，用户面传输中断和第一阈值，可以参见本申请实施例第一种通信方法300的介绍，此处不再赘述。
第二项，终端设备在切换过程中与第一网络设备之间发生RLF。其中，终端设备在切换过程中与第一网络设备之间发生RLF，也可以替换为：终端设备和第二网络设备完成成功的随机接入之前，与第一网络设备之间发生RLF。
示例性的，对于第二项触发条件而言，确定过程如下：第二项触发条件可以由第一网络设备确定，也可以由第二网络设备确定，然后，第二网络设备向第一网络设备发送信息1。相应的，第一网络设备接收来自第二网络设备的信息1。其中，信息1指示触发条件包括终端设备在切换过程中与第一网络设备之间发生RLF。示例性的，信息1所承载的消息和传输的时间，可以参见S301c中关于指示信息的介绍，此处不再赘述。
示例性的，触发条件，也可以有其他名称，本申请实施例对此不作限定。示例性的，在记录SHR的场景下，上述触发条件也可以包括SHR触发条件，详见SHR trigger condition的介绍，此处不再赘述。
S1302、第一网络设备向终端设备发送触发条件。相应的，终端设备接收来自第一网络设备的触发条件。
其中，S1302中的触发条件与S1301中的触发条件一致。
示例性的，触发条件在第一网络设备和终端设备之间的传输状况，可以参见S302中关于指示信息的介绍，此处不再赘述。
S1303、当满足触发条件时，终端设备记录SHR。
其中，SHR至少指示终端设备满足的触发条件，也可以理解为，触发记录SHR的原因。下面，对SHR的指示方式进行介绍：
作为一种可能的实现方式，SHR可以直接指示终端设备满足的触发条件。例如，在用户面传输中断的时长大于或等于第一阈值的情况下，SHR直接指示用户面传输中断的时长大于或等于第一阈值。再如，在切换过程中终端设备与第一网络设备之间发生RLF的情况下，SHR直接指示切换过程中终端设备与第一网络设备之间发生RLF。
作为也一种可能的实现方式，SHR也可以间接指示终端设备满足的触发条件。例如，各项触发条件与数字之间的对应关系，如表2所示。例如，在用户面传输中断的时长大于或等于第一阈值的情况下，SHR直接指示数字“0”。再如，在切换过程中终端设备与第一网络设备之间发生RLF的情况下，SHR直接指示数字“1”。
表2
数字 触发条件
0 用户面传输中断的时长大于或等于第一阈值
1 终端设备在切换过程中与第一网络设备之间发生RLF
需要说明的是，上述仅是示例性的给出了SHR指示终端设备满足的触发条件的方式，当然，SHR也可以通过其他方式来指示终端设备满足的触发条件，本申请实施例对此不作限定。
示例性的，以第二项触发条件为例，S1303的实现过程如下：
在切换过程中，终端设备与第一网络设备之间发生RLF的情况下，终端设备确定满足该项触发条件。此种情况下，终端设备记录SHR。其中，SHR指示切换过程中终端设备与第一网络设备之间发生RLF。
应理解，在记录SHR的场景下，上述触发条件还可以包括SHR触发条件。相应的，终端设备执行S1303的情况下，终端设备仍记录SHR，详见相关技术的介绍，此处不再赘述。
在一些实施例中，针对SHR指示切换过程中终端设备与第一网络设备之间发生RLF的情况，SHR可以指示发生上述RLF的原因。示例性的，发生RLF的原因包括以下至少一项：
第一项，第二定时器超时。其中，第二定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。示例性的，第二定时器可以是上述定时器T310。
第二项，波束失败恢复失败。
第三项，随机接入失败。
第四项，重传达到最大次数。示例性的，无线链路控制(radio link control，RLC)层的数据包达到了最大重传次数，导致RLF。
第五项，先听后说(listen before talk，LBT)失败。示例性的，LBT的介绍如下：在非授权频段上，无法时刻保证信道的可用性。在传输上行数据之前，终端设备进行空闲信道评估，以确保信道空闲的情况下传输上行数据。若LBT成功，则终端设备传输上行数据。若LBT失败，则终端设备放弃传输本次上行数据，后续待信道空闲时再传输上行数据。
第六项，回传链路RLF恢复失败(backhaul(BH)RLF恢复失败)。示例性的，在接入回传一体化(integrated access and backhaul，IAB)场景中，终端设备为IAB移动终端(IAB mobile terminal，IAB-MT)，若其收到回传链路自适应协议栈(backhaul adaptation protocol，BAP)实体发送的回传链路RLF指示，确定RLF的原因为BH RLF恢复失败。
应理解，上述六项，仅是示例性的给出了RLF的原因。当然，RLF的原因还可以包括其他原因，本申请实施例对此不作限定。
如此，SHR可以指示上述六项原因中的一项或多项，从而指示切换过程中终端设备与第一网络设备之间发生RLF。
可选的，SHR还指示随机接入的信息。和第一网络设备之间导致RLF的随机接入信息示例性的，SHR指示的随机接入的信息包括以下至少一项：
第一项，绝对频点位置。其中，绝对频点位置指示了频域上的参考点，以提高资源分配灵活性。示例性的，绝对频点位置可以是Point A。
第二项，物理随机接入信道(physical random access channel，PRACH)的频域位置。其中，PRACH用于进行随机接入，即终端设备通过PRACH接入。PRACH的频域位置是相对于绝对频点位置所指示的PRACH资源位置。示例性的，PRACH的频域位置是从第15个资源块(resource block，RB)开始的预设数量的RB，可以理解为，以绝对频点位置 为首个RB，从第15个RB开始的预设数量的RB，均属于PRACH所在的资源位置。
第三项，PRACH的带宽。示例性的，PRACH的带宽为10个RB，或其他数量的RB，本申请实施例对此不作限定。
第四项，PRACH的子载波间隔。其中，PRACH的子载波间隔为15kHz，或30kHz，或其他数值，本申请实施例对此不作限定。
应理解，SHR可以指示上述信息中的一项，如SHR指示PRACH的带宽，或指示PRACH的子载波间隔。或者，SHR可以指示上述信息中的两项，如SHR指示绝对频点位置，以及PRACH的频域位置，或者，SHR指示PRACH的带宽和子载波间隔，或者其他组合，本申请实施例对此不作限定。
需要说明的是，仅以上述三项信息为例，对随机接入的信息进行介绍。当然，随时接入的信息还可以包括其他信息，如在同一时间上频分复用(frequency-division multiplexing，FDM)的PRACH传输时机(transmission occasion)的个数，本申请实施例对此不作限定。
可选的，S1304、终端设备向第一网络设备发送SHR。相应的，第一网络设备接收来自终端设备的SHR。
其中，S1304中的SHR与S1303中的SHR一致。
示例性的，S1304的实现过程可以参见S304的介绍，此处不再赘述。
可选的，S1305、第一网络设备根据SHR，确定网络优化参数。
示例性的，第一网络设备可以结合SHR和终端设备的上下文，来对终端设备的移动性进行优化，以得到网络优化参数，从而优化处理潜在移动性失败的问题。
在本申请实施例通信方法1300中，若终端设备在切换过程中，与第一网络设备之间发生RLF，则终端设备记录此情况，即上述SHR至少指示终端设备满足的触发条件，以指示终端设备与第一网络设备之间发生RLF，避免现有技术中此种情况下终端设备无法记录的问题，也为网络侧确定优化参数奠定了基础。
在终端设备的DAPS切换成功但与源网络设备发生RLF的场景下，终端设备记录RLF报告。假若终端设备同时配置了SHR触发条件(详见名词解释部分关于SHR触发条件的介绍)，且满足SHR触发条件的情况下，终端设备也记录SHR。也就是说，终端设备针对同一次移动性异常(如上述RLF)，记录了RLF报告和SHR。其中，RLF报告和SHR中的部分移动性参数是重复的。在终端设备向源网络设备发送RLF报告和SHR的情况下，源网络设备基于RLF报告和SHR分别确定网络优化参数，且基于RLF报告和SHR分别确定的网络优化参数对同一移动性参数进行调整，从而使得同一移动性参数调整了两次，容易导致过度调整的问题。示例性的，在移动性参数包括切换阈值的情况下，切换阈值的初始值为XdB。源网络设备基于RLF报告确定切换阈值降低0.5dB。如此，源网络设备基于RLF报告所确定的网络优化参数，在切换阈值的初始值XdB的基础上，降低了0.5dB，如此，切换阈值调整为(X-0.5)dB。源网络设备基于SHR确定切换阈值降低0.5dB即可满足移动性指标。如此，源网络设备基于SHR所确定的网络优化参数，确定切换阈值的调整值(X-0.5)dB的基础上，再次降低了0.5dB，如此，切换阈值调整为(X-0.5-0.5)dB，从而造成过度调整的问题。
有鉴于此，本申请实施例提供第二种通信方法和第三种通信方法。其中，在本申请实施例提供的第二种通信方法中，终端设备执行DAPS切换过程中，检测到与源小区之间的 RLF，且完成与目标小区之间的DAPS切换的情况下，终端设备确定第一报告。其中，第一报告包括预设条件指示的待记录的报告，或第一报告包括预设条件指示的待上报的报告。预设条件包括以下至少一项：第一项，仅记录SHR；第二项，仅记录RLF报告；第三项，仅上报SHR；第四项，仅上报RLF报告。这样一来，终端设备记录了满足预设条件的第一报告，换言之，针对一次移动性异常，终端设备仅记录RLF报告和SHR中的一种报告，或终端设备仅上报RLF报告和SHR中的一种报告，相应的，网络侧针对一次移动性异常，也就能够获取到一个报告(如上述SHR，或RLF报告)，从而避免过度调整的问题。
如图6所示，本申请实施例提供的第二种通信方法600包括如下步骤：
S601、在终端设备执行DAPS切换过程中，检测到与源小区之间的RLF，且完成与目标小区之间的DAPS切换的情况下，终端设备确定第一报告。
其中，第一报告包括预设条件指示的待记录的报告，或第一报告包括预设条件指示的待上报的报告。预设条件包括以下至少一项：
第一项，仅记录SHR。示例性的，仅记录SHR的具体实现过程包括：当发生RLF时，终端设备记录RLF报告。当满足SHR的触发条件的情况下，终端设备记录SHR。在一段时间之后，或终端设备记录SHR报告的同时，终端设备删除RLF报告。
第二项，仅记录RLF报告。示例性的，作为一种可能的实现方式，仅记录RLF报告的具体实现过程包括：当发生RLF时，终端设备记录RLF报告。当满足SHR的触发条件的情况下，终端设备不记录SHR。作为另一种可能的实现方式，仅记录RLF报告的具体实现过程包括：当发生RLF时，终端设备记录RLF报告。当满足SHR的触发条件的情况下，终端设备记录SHR。然后终端设备删除SHR。
第三项，仅上报SHR。此种情况下，终端设备记录SHR。终端设备可以记录RLF报告，也可以不记录RLF报告，本申请实施例对此不作限定。在终端设备记录RLF报告的情况下，终端设备不上报RLF报告，或者，在一段时间之后，终端设备删除RLF报告。
第四项，仅上报RLF报告。此种情况下，终端设备记录RLF报告。终端设备可以记录SHR，也可以不记录SHR，本申请实施例对此不作限定。在终端设备记录SHR的情况下，终端设备不上报SHR，或者，在一段时间之后，终端设备删除SHR。
其中，预设条件可以是预配置的，也可以是从网络侧接收的，本申请实施例对此不作限定。在预设条件是从网络侧接收的情况下，如图6所示，本申请实施例通信方法600还包括S602和S603：
S602、第一网络设备获取预设条件。
其中，S602中的预设条件与S601中的预设条件一致，此处不再赘述。
其中，S602的具体实现过程包括但不限于如下两种方式(下述方式1和方式2)：
方式1，如图7中“方式1”所在的虚线框所示，第一网络设备执行S602a：
S602a、第一网络设备确定预设条件。
示例性的，第一网络设备确定是否仅记录SHR，或是否仅记录RLF报告，或是否仅上报SHR，或是否仅上报RLF报告。
方式2，如图7中“方式2”所在的虚线框所示，第二网络设备执行S602b和S602c：
S602b、第二网络设备确定预设条件。
示例性的，第二网络设备自主确定预设条件。此种情况下，S602b的实现过程可以参 见S602a的介绍，区别点在于，S602a的执行主体为第一网络设备，而S602b的执行主体为第二网络设备，此处不再赘述。
S602c、第二网络设备向第一网络设备发送预设条件。相应的，第一网络设备接收来自第二网络设备的预设条件。
示例性的，从承载的消息上来说，预设条件可以承载于HO请求确认消息中，也可以承载于其他消息，还可以单独传输。从传输的时间上来说，预设条件可以与HO请求确认消息同时传输，也可以在HO请求确认消息之前传输，本申请实施例对此不作限定。
需要说明的是，HO请求确认消息包括RRC重配置消息。预设条件承载于HO请求确认消息，可以有两种实现方式：在第一种实现方式中，预设条件承载于RRC重配置消息中；在第二种实现方式中，预设条件承载于RRC重配置消息外，且承载于HO请求确认消息中。
S603、第一网络设备向终端设备发送预设条件。相应的，终端设备接收来自第一网络设备的预设条件。
其中，S603中的预设条件与S602中的预设条件一致。
示例性的，从承载的消息上来说，预设条件可以承载于RRC重配置消息中，也可以承载于其他消息(如RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息)，还可以单独传输。从传输的时间上来说，预设条件可以与RRC重配置消息同时传输，也可以在RRC重配置消息之前传输，如通过RRC建立消息、RRC重建立消息、RRC恢复消息、或系统消息传输，本申请实施例对此不作限定。
应理解，在S602c中的预设条件与HO请求确认消息同时传输的情况下，S603中的预设条件与RRC重配置消息同时传输。在S602c中的预设条件在HO请求确认消息之前传输的情况下，S603中的预设条件可以与RRC重配置消息同时传输，也可以在RRC重配置消息之前传输，本申请实例对此不作限定。
在一些实施例中，如图6所示，本申请实施例第二种通信方法600还包括S604和S605：
S604、终端设备向第一网络设备发送第一报告。相应的，第一网络设备接收来自终端设备的第一报告。
其中，S604中的第一报告与S601中的第一报告一致。
示例性的，S604的实现过程可以参见S304的介绍，此处不再赘述。
S605、第一网络设备根据第一报告，确定网络优化参数。
其中，S605的实现过程可以参见S305的介绍，此处不再赘述。
在本申请实施例通信方法600中，预设条件指示了终端设备待记录的报告，或终端设备待上报的报告。终端设备确定满足预设条件的第一报告。如此，针对一次移动性异常，终端设备仅记录RLF报告和SHR中的一种报告，或终端设备仅上报RLF报告和SHR中的一种报告，相应的，网络侧针对一次移动性异常，也就能够获取到一个报告(如上述SHR，或RLF报告)，从而避免过度调整的问题。
在本申请实施例提供的第三种通信方法中，终端设备执行DAPS切换过程中，检测到与源小区之间的RLF，且完成与目标小区之间的DAPS切换的情况下，第一网络设备接收来自终端设备的RLF报告和SHR。其中，RLF报告和SHR包括同一移动性异常的移动性参数。第一网络设备根据SHR确定网络优化参数，或第一网络设备根据RLF报告确定网 络优化参数，或第一网络设备根据SHR和RLF报告确定网络优化参数，以避免第一网络设备基于同一移动性异常的RLF报告和SHR分别确定网络优化参数，从而解决过度调整的问题。
如图8所示，本申请实施例提供的第三种通信方法800包括如下步骤：
S801、在终端设备执行DAPS切换过程中，检测到与源小区之间的RLF，且完成与目标小区之间的DAPS切换的情况下，终端设备确定RLF报告和SHR。
其中，RLF报告和SHR包括RLF过程中的移动性参数，S801的实现过程可以参见相关现有技术，此处不再赘述。
S802、终端设备向第一网络设备发送RLF报告和SHR。相应的，第一网络设备接收来自终端设备的RLF报告和SHR。
其中，S802中的RLF报告与S801中的RLF报告一致，S802中的SHR与S801中的SHR一致。
其中，S802的实现过程可以参见S304的介绍，此处不再赘述。
对于第一网络设备而言，第一网络设备执行S802之后，执行S803a、S803b和S803c中的一项。其中，S803a、S803b和S803c的说明如下：
S803a、第一网络设备根据SHR确定网络优化参数。
隐式的，可以理解为，第一网络设备使用SHR确定网络优化参数，且不使用RLF报告确定网络优化参数。
示例性的，仍以移动性参数包括切换阈值为例，切换阈值的初始值为XdB。第一网络设备基于SHR确定切换阈值降低0.5dB即可满足移动性指标，基于SHR所确定的网络优化参数为-0.5dB。第一网络设备在切换阈值的初始值XdB的基础上，降低了0.5dB，如此，切换阈值调整为(X-0.5)dB。由于第一网络设备未使用RLF报告确定网络优化参数，所以，也就不存在过度调整的问题。
S803b、第一网络设备根据RLF报告确定网络优化参数。
隐式的，可以理解为，第一网络设备使用RLF报告确定网络优化参数，且不使用SHR确定网络优化参数。
示例性的，仍以移动性参数包括切换阈值为例，切换阈值的初始值为XdB。第一网络设备基于RLF报告确定切换阈值降低0.5dB即可满足移动性指标，基于RLF报告所确定的网络优化参数为-0.5dB。第一网络设备在切换阈值的初始值XdB的基础上，降低了0.5dB，如此，切换阈值调整为(X-0.5)dB。由于第一网络设备未使用SHR确定网络优化参数，所以，也就不存在过度调整的问题。
S803c、第一网络设备根据SHR和RLF报告确定网络优化参数。
示例性的，仍以移动性参数包括切换阈值为例，切换阈值的初始值为XdB。第一网络设备基于SHR和RLF报告确定的网络优化参数满足如下公式：
D＝k 1×a+k 2×b    公式(3)
其中，D表示网络优化参数，k 1表示SHR对应的加权系数，a表示基于SHR确定的网络优化数值，k 2表示RLF报告对应的加权系数，b表示基于RLF报告确定的网络优化数值。示例性的，k 1＝k 2＝0.5。当然，加权系数k 1和加权系数k 2均可以有其他取值，本申请实施例对此不作限定。应理解，加权系数k 1和加权系数k 2的取值不同时为1，换言之，不存 在如下情况：k 1＝k 2＝1。
示例性的，第一网络设备基于SHR确定网络优化数值a，以及基于RLF报告确定网络优化数值b，然后，第一网络设备基于公式(3)，确定网络优化参数D。第一网络设备在切换阈值的初始值XdB的基础上，调整了DdB，如此，切换阈值调整为(X+D)dB。由于不存在如下情况：k 1＝k 2＝1的情况，且第一网络设备对切换阈值进行了一次调整，也就不存在过度调整的问题。
应理解，上述公式(3)仅是示例性的给出了网络优化参数满足的计算公式，当然，第一网络设备还可以根据其他计算方式，基于SHR和RLF报告来确定网络优化参数，本申请实施例对此不作限定。
在本申请实施例通信方法800中，第一网络设备获取SHR和RLF报告的情况下，第一网络设备根据SHR确定网络优化参数，或第一网络设备根据RLF报告确定网络优化参数，或第一网络设备根据SHR和RLF报告确定网络优化参数，以避免第一网络设备基于同一移动性异常的RLF报告和SHR分别确定网络优化参数，对同一移动性参数进行了两次调整的现象，从而解决过度调整的问题。
在一些实施例中，第一网络设备执行S803a的情况下，如图9所示，第一网络设备还执行S804a：
S804a、第一网络设备丢弃RLF报告。
其中，S804a中的RLF报告与S802中的RLF报告一致。
示例性的，第一网络设备删除RLF报告，以避免第一网络设备重复采用RLF报告确定网络优化参数。
需要说明的是，第一网络设备可以先执行S803a，再执行S804a(如图9所示)，也可以先执行S804a，再执行S803a(图9未示出)，还可以同时执行S803a和S804a(图9未示出)，本申请实施例对此不作限定。
在一些实施例中，第一网络设备执行S803b的情况下，如图10所示，第一网络设备还执行S804b：
S804b、第一网络设备丢弃SHR。
其中，S804b中的SHR与S802中的SHR一致。
示例性的，第一网络设备删除SHR，以避免第一网络设备重复采用SHR确定网络优化参数。
需要说明的是，第一网络设备可以先执行S803b，再执行S804b(如图10所示)，也可以先执行S804b，再执行S803b(图10未示出)，还可以同时执行S803b和S804b(图10未示出)，本申请实施例对此不作限定。
应理解，本申请实施例第二种通信方法600和第三种通信方法800中，SHR也可以替换为第一种通信方法300中的第一报告。也就是说，S601中的第一报告，S801、S802、S803a和S804c中的SHR，可以是在切换过程中用户面传输中断时长大于或等于第一阈值的情况下记录的报告，第一报告包括用户面传输中断时长，具体可以参见第一种通信方法300中的介绍，此处不再赘述。
在DAPS切换场景中，目标网络设备可能支持SHR特性，有可能不支持SHR特性。在目标网络设备不支持SHR特性的情况下，目标网络设备不支持终端设备上报SHR。目 标网络设备向源网络设备提供的RRC重配置消息也就不携带SHR触发条件。由于源网络设备对RRC重配消息不作解析，所以，源网络设备也就无法获知目标网络设备是否支持SHR特性。如何使得源网络设备与目标网络设备协商是否支持SHR特性，是亟待解决的问题。
有鉴于此，本申请实施例提供第四种通信方法，在本申请实施例提供的第四种通信方法中，第一网络设备向第二网络设备发送第一信息。其中，第一信息用于指示触发记录SHR的至少一个条件。然后，第一网络设备接收来自第二网络设备的第二信息。其中，第二信息指示第二网络设备是否接受上述至少一个条件中的一个或多个。这样一来，第一网络设备基于第二信息，即可确定第二网络设备是否支持SHR特性。
如图11所示，本申请实施例提供的第四种通信方法1100包括如下步骤：
S1101、第一网络设备向第二网络设备发送第一信息。相应的，第二网络设备接收来自第一网络设备的第一信息。
其中，第一信息用于指示触发记录SHR的至少一个条件。示例性的，第一信息包括以下至少一项：
第一项，用户面传输中断时长的阈值。其中，用户面传输中断时长的介绍可以参见S301的说明，此处不再赘述。用户面传输中断时长的阈值，可以参见第一种通信方法300中第一阈值的介绍，此处不再赘述。
第二项，第一定时器的阈值。其中，第一定时器的运行时长指示终端设备接收RRC重配置消息之后未接入第二网络设备的时长。示例性的，第一定时器可以是定时器T304。
第三项，第二定时器的阈值。其中，第二定时器的运行时长指示终端设备检测到与第一网络设备之间有物理层问题的时长。示例性的，第二定时器可以是定时器T310。
第四项，第三定时器的阈值。其中，第三定时器的运行时长指示在第二定时器运行期间，终端设备触发测量报告至终端设备与第一网络设备恢复同步之间的时长。示例性的，第三定时器可以是定时器T312。
示例性的，从承载的消息上来说，第一信息可以承载于HO请求消息中，也可以承载于其他消息，还可以单独传输。从传输的时间上来说，第一信息可以与HO请求消息同时传输，也可以在HO请求消息之前传输，本申请实施例对此不作限定。其中，HO请求消息可以是DAPS切换请求消息，具体可以参见S203的介绍，此处不再赘述。
在一些实施例中，如图12所示，第一网络设备执行S1101的情况下，本申请实施例第四种通信方法1100还包括S1103和S1104：
S1103、第一网络设备向第二网络设备发送信息X。相应的，第二网络设备接收来自第一网络设备的信息X。
其中，信息X用于请求第二网络设备反馈是否支持SHR功能。S1103的实现过程可以参见S301e的介绍，此处不再赘述。
S1104、第二网络设备向第一网络设备发送信息Y。相应的，第一网络设备接收来自第二网络设备的信息Y。
其中，信息Y指示第二网络设备是否支持SHR功能。S1104的实现过程可以参见S301f的介绍，此处不再赘述。
通过上述S1103和S1104，或上述S1104，第一网络设备即可获知第二网络设备是否 支持SHR功能。在信息Y指示第二网络设备支持SHR功能的情况下，第一网络设备执行S1101，从而为第二网络设备提供第一信息。反之，在信息Y指示第二网络设备不支持SHR功能的情况下，第一网络设备不执行S1101，从而避免浪费传输资源。
S1102、第二网络设备向第一网络设备发送第二信息。相应的，第一网络设备接收来自第二网络设备的第二信息。
其中，第二信息指示第二网络设备是否接受上述至少一个条件中的一个或多个。
示例性的，以第一信息包括四项条件为例进行介绍，例如，第二网络设备可以不接受第一信息中的全部条件。此种情况下，第二信息指示第二网络设备不接受上述至少一个条件中的全部条件。再如，第二网络设备可以接受第二项，但不接受其他项(如第一项、第三项和第四项)，此种情况下，第二信息指示第二网络设备接受上述四项条件中的一个，或者，第二信息指示第二网络设备不接受上述四项条件中的三个。应理解，第一信息具体携带哪一(些)预设条件，可以有多种情况，并且，针对第一信息中的每一条件，第二网络设备是否接受存在两种情况。如此，第二信息的指示内容，可以有多种情况，此处不再一一列举。
在一些实施例中，在第二信息指示第二网络设备不接受上述至少一个条件中的一个或多个的情况下，第二信息还可以指示拒绝原因。应理解，在第二信息指示第二网络设备不接受上述至少一个条件中的全部条件的情况下，RRC重配置消息中不携带触发记录SHR的条件。
在一些实施例中，在第二网络设备接受第一信息携带的至少一个条件中的一个或多个的情况下，第二信息还指示以下至少一项：
第一项，RRC重配置消息中携带上述至少一个条件中的一个或多个。也就是说，第二网络设备显式地告知第一网络设备RRC重配置消息中预设条件的携带状况，如RRC重配置消息中是否携带了预设条件，以及携带的预设条件数量。示例性的，指示信息携带一个比特(bit)的信息，以指示RRC重配置消息中是否携带了预设条件，如该比特的取值为“1”时，表征RRC重配置消息中携带了预设条件，反之，该比特的取值为“0”时，表征RRC重配置消息中未携带预设条件。或者，该比特的取值为“0”时，表征RRC重配置消息中携带了预设条件，反之，该比特的取值为“1”时，表征RRC重配置消息中未携带预设条件。应理解，在本申请实施例中，仅以一个比特的信息为例进行介绍，指示信息还可以通过更多的比特来指示RRC重配置消息中对预设条件的携带状况，本申请实施例对此不作限定。
第二项，触发记录SHR的条件类型。其中，条件类型可以是指用户面传输中断时长、第一定时器、第二定时器和第三定时器。例如，在RRC重配置消息中携带用户面传输中断时长的阈值的情况下，第二信息所指示的条件类型包括用户面传输中断时长。再如，在RRC重配置消息中携带第一定时器的阈值的情况下，第二信息所指示的条件类型包括第一定时器。又如，在RRC重配置消息中携带第二定时器的阈值的情况下，第二信息所指示的条件类型包括第二定时器。又如，在RRC重配置消息中携带第三定时器的阈值的情况下，第二信息所指示的条件类型包括第三定时器。
第三项，触发记录SHR的阈值。例如，在RRC重配置消息中携带用户面传输中断时长的阈值的情况下，第二信息所指示的阈值包括用户面传输中断时长的阈值。再如，在RRC 重配置消息中携带第一定时器的阈值的情况下，第二信息所指示的阈值包括第一定时器的阈值。又如，在RRC重配置消息中携带第二定时器的阈值的情况下，第二信息所指示的阈值包括第二定时器的阈值。又如，在RRC重配置消息中携带第三定时器的阈值的情况下，第二信息所指示的阈值包括第三定时器的阈值。
示例性的，从消息名称上来说，第二信息，可以有其他名称，如响应消息，配置确认消息等，本申请实施例对此不作限制。在本申请实施例中，仅以第二信息为例进行介绍。从传输的时间上来说，第二信息可以与HO请求确认消息同时传输，也可以在HO请求确认消息之前传输，本申请实施例对此不作限定。其中，HO请求消息可以是DAPS切换请求消息，具体可以参见S203的介绍，此处不再赘述。
应理解，在第一信息与HO请求消息同时传输的情况下，第二信息与HO请求确认消息同时传输，在第一信息在HO请求消息之前传输的情况下，第二信息可以与HO请求确认消息同时传输，也可以在HO请求确认消息之前传输，本申请实施例对此不作限定。
需要说明的是，在第二网络设备接受第一信息携带的至少一个条件中的一个或多个的情况下，第二网络设备还执行S1105：
S1105、第二网络设备向第一网络设备发送RRC重配置消息。相应的，第一网络设备接收来自第二网络设备的RRC重配置消息。
其中，RRC重配置信息中携带一个或多个条件。RRC重配置消息中携带的条件属于第一信息中指示的条件，具体参见S1101的介绍，此处不再赘述。
在本申请实施例通信方法1100中，第一网络设备向第二网络设备发送第一信息。其中，第一信息用于指示触发记录SHR的至少一个条件。然后，第一网络设备接收来自第二网络设备的第二信息。其中，第二信息指示第二网络设备是否接受上述至少一个条件中的一个或多个。这样一来，第一网络设备基于第二信息，即可确定第二网络设备是否支持SHR特性。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置可以为上述方法实施例中的网元，或者包含上述网元的装置，或者为可用于网元的部件。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
示例性的，图14示出了一种通信装置1400的结构示意图。该通信装置1400包括处理单元1401、发送单元1402和接收单元1403。
一种可能的示例中，以通信装置1400为终端设备为例，处理单元1401用于支持终端设备执行图3中的S303，图6中的S601，图8中的S801，图13中的S1303，和/或本申请实施例中终端设备需要执行的其他处理操作。接收单元1403用于支持终端设备执行图3中的S302，图6中的S603，图13中的S1302，和/或本申请实施例中终端设备需要执行的其他接收操作。发送单元1402用于支持终端设备执行图3中的S304，图6中的S604，图8中的S802，图13中的S1304，和/或本申请实施例中终端设备需要执行的其他发送操作。
再一种可能的示例中，以通信装置1400为第一网络设备为例，处理单元1401用于支持第一网络设备执行图3中的S301、S305，图6中的S602、S605，图8中的S803a、S803b、S803c，图13中的S1301、S1305，和/或本申请实施例中第一网络设备需要执行的其他处理操作。接收单元1403用于支持第一网络设备执行图3中的S304，图6中的S604，图8中的S802，图11中的S1102、S1105，图13中的S1304，和/或本申请实施例中第一网络设备需要执行的其他接收操作。发送单元1402用于支持第一网络设备执行图3中的S302，图6中的S603，图11中的S1101，图13中的S1302，和/或本申请实施例中第一网络设备需要执行的其他发送操作。
又一种可能的示例中，以通信装置1400为第二网络设备为例，处理单元1401用于支持第二网络设备需要执行的其他处理操作。接收单元1403用于支持第二网络设备执行图11中的S1101，和/或本申请实施例中第二网络设备需要执行的其他接收操作。发送单元1402用于支持第二网络设备执行图11中的S1102，和/或本申请实施例中第二网络设备需要执行的其他发送操作。
可选的，该通信装置1400还可以包括存储单元1404，用于存储通信装置的程序代码和数据，数据可以包括不限于原始数据或者中间数据等。
其中，处理单元1401可以是处理器或控制器，例如可以是CPU，通用处理器，专用集成电路(application specific integrated circuit，ASIC)，现场可编程逻辑门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
发送单元1402可以是通信接口、发送器或发送电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，例如可以包括：终端设备(如第一终端设备、第二终端设备)之间的接口和/或其他接口。
接收单元1403可以是通信接口、接收器或接收电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，例如可以包括：终端设备与网络设备(如第一网络设备、第二网络设备)之间的接口和/或其他接口。
发送单元1402和接收单元1403可以是物理上或者逻辑上实现为同一个单元。
存储单元1404可以是存储器。
当处理单元1401为处理器，发送单元1402和接收单元1403为通信接口，存储单元1404为存储器时，本申请实施例所涉及的通信装置可以为图15所示。
参阅图15所示，该通信装置包括：处理器1501、通信接口1502、存储器1503。可选的，通信装置还可以包括总线1504。其中，通信接口1502、处理器1501以及存储器1503可以通过总线1504相互连接；总线1504可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线1504可以分为地址总线、数据总线、控制总线等。为便于表示，图15中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可选的，本申请实施例还提供一种携带计算机指令的计算机程序产品，当该计算机指令在计算机上运行时，使得计算机执行上述实施例所介绍的方法。
可选的，本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储计算机指令，当该计算机指令在计算机上运行时，使得计算机执行上述实施例所介绍的方法。
可选的，本申请实施例还提供一种芯片，包括：处理电路和收发电路，处理电路和收发电路用于实现上述实施例所介绍的方法。其中，处理电路用于执行相应方法中的处理动作，收发电路用于执行相应方法中的接收/发送的动作。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD))、或者半导体介质(例如固态硬盘(solid state drive，SSD))等。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个设备上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘，硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (41)

  1. 一种通信方法，其特征在于，包括：
    终端设备接收来自第一网络设备的指示信息，其中，所述指示信息指示第一阈值；
    当切换过程中用户面传输中断时长大于或等于所述第一阈值时，所述终端设备记录第一报告，其中，所述第一报告指示所述用户面传输中断时长。
  2. 根据权利要求1所述的方法，其特征在于，所述用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
  3. 根据权利要求2所述的方法，其特征在于，所述用户面传输中断的起始标识包括以下其中一项：
    所述终端设备向所述第一网络设备成功发送最后一个数据包；
    所述终端设备成功接收来自所述第一网络设备的最后一个数据包；
    所述用户面传输中断的终止标识包括以下其中一项：
    所述终端设备向第二网络设备成功发送首个数据包；
    所述终端设备成功接收来自所述第二网络设备的首个数据包；
    其中，所述第一网络设备是所述终端设备在所述切换过程前接入的网络设备；
    所述第二网络设备是所述终端设备在所述切换过程后接入的网络设备。
  4. 根据权利要求3所述的方法，其特征在于，所述指示信息还指示所述用户面传输中断的起始标识和/或终止标识。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述在切换过程中用户面传输中断时长大于或等于所述第一阈值的情况下，所述终端设备记录第一报告，包括：
    在第一定时器的运行时长大于或等于所述第一阈值的情况下，所述终端设备记录所述第一报告，其中，所述第一定时器的运行时长指示所述用户面传输中断时长。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述第一网络设备发送所述第一报告，其中，所述第一网络设备是所述终端设备在所述切换过程前接入的网络设备。
  7. 根据权利要求1至6任一项所述的方法，其特征在于，所述第一报告还指示以下至少一项：
    触发记录所述第一报告的原因；
    所述用户面传输中断的起始标识；
    所述用户面传输中断的停止标识；
    源小区的无线网络临时标识CRNTI；
    重复接收的数据包的数量；
    重复接收的数据包的比例。
  8. 一种通信方法，其特征在于，包括：
    第一网络设备获取指示信息，其中，所述指示信息指示第一阈值；
    所述第一网络设备向终端设备发送所述指示信息，其中，所述指示信息用于所述终端设备在切换过程中用户面传输中断时长大于或等于所述第一阈值的情况下记录第一报告，所述第一报告指示所述用户面传输中断时长。
  9. 根据权利要求8所述的方法，其特征在于，所述用户面传输中断时长是用户面传输 中断起始标识至终止标识的时间间隔。
  10. 根据权利要求9所述的方法，其特征在于，所述用户面传输中断的起始标识包括以下其中一项：
    所述终端设备向所述第一网络设备成功发送最后一个数据包；
    所述终端设备成功接收来自所述第一网络设备的最后一个数据包；
    所述用户面传输中断的终止标识包括以下其中一项：
    所述终端设备向第二网络设备成功发送首个数据包；
    所述终端设备成功接收来自所述第二网络设备的首个数据包；
    其中，所述第一网络设备是所述终端设备在所述切换过程前接入的网络设备；
    其中，所述第二网络设备是所述终端设备在所述切换过程后接入的网络设备。
  11. 根据权利要求10所述的方法，其特征在于，所述指示信息还指示所述用户面传输中断的起始标识和/或终止标识。
  12. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述终端设备的所述第一报告，其中，所述第一网络设备是所述终端设备在所述切换过程前接入的网络设备。
  13. 根据权利要求8至12任一项所述的方法，其特征在于，所述第一网络设备获取指示信息，包括：所述第一网络设备确定所述指示信息。
  14. 根据权利要求8至12任一项所述的方法，其特征在于，所述第一网络设备获取指示信息，包括：
    所述第一网络设备接收来自第二网络设备的所述指示信息。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向所述第二网络设备发送参考信息，其中，所述参考信息用于确定所述指示信息。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述第二网络设备的第一信息，其中，所述第一信息指示所述第二网络设备支持成功切换报告SHR功能；
    所述第一网络设备向所述第二网络设备发送参考信息，包括：
    所述第一网络设备根据所述第一信息，向所述第二网络设备发送所述参考信息。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向所述第二网络设备发送第二信息，其中，所述第二信息用于请求所述第二网络设备反馈是否支持SHR功能。
  18. 根据权利要求8至17任一项所述的方法，其特征在于，所述第一报告还指示以下至少一项：
    触发记录所述第一报告的原因；
    所述用户面传输中断的起始标识；
    所述用户面传输中断的停止标识；
    源小区的无线网络临时标识CRNTI；
    重复接收的数据包的数量；
    重复接收的数据包的比例。
  19. 一种通信方法，其特征在于，包括：
    第二网络设备确定指示信息，其中，所述指示信息指示第一阈值；
    所述第二网络设备向第一网络设备发送所述指示信息，其中，所述第一网络设备是终端设备在切换过程前接入的网络设备，所述第二网络设备是所述终端设备在所述切换过程后接入的网络设备；所述第一阈值用于所述终端设备在所述切换过程中用户面传输中断时长大于或等于所述第一阈值的情况下记录第一报告，所述第一报告指示所述用户面传输中断时长。
  20. 根据权利要求19所述的方法，其特征在于，所述用户面传输中断时长是用户面传输中断起始标识至终止标识的时间间隔。
  21. 根据权利要求20所述的方法，其特征在于，所述用户面传输中断的起始标识包括以下其中一项：
    所述终端设备向所述第一网络设备成功发送最后一个数据包；
    所述终端设备成功接收来自所述第一网络设备的最后一个数据包；
    所述用户面传输中断的终止标识包括以下其中一项：
    所述终端设备向所述第二网络设备成功发送首个数据包；
    所述终端设备成功接收来自所述第二网络设备的首个数据包。
  22. 根据权利要求21所述的方法，其特征在于，所述指示信息还指示所述用户面传输中断的起始标识和/或终止标识。
  23. 根据权利要求19至22任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收来自所述第一网络设备的参考信息，其中，所述参考信息用于确定所述指示信息。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备向所述第一网络设备发送第一信息，其中，所述第一信息指示所述第二网络设备支持成功切换报告SHR功能。
  25. 根据权利要求24所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收来自所述第一网络设备的第二信息，其中，所述第二信息用于请求所述第二网络设备反馈是否支持SHR功能；
    所述第二网络设备向所述第一网络设备发送第一信息，包括：
    所述所述第二网络设备根据所述第二信息，向所述第一网络设备发送第一信息。
  26. 一种通信方法，其特征在于，包括：
    终端设备接收来自第一网络设备的触发条件，其中，所述触发条件包括切换过程中所述终端设备与所述第一网络设备之间发生无线链路失败RLF，或者，所述触发条件包括所述终端设备和第二网络设备完成成功的随机接入之前，与所述第一网络设备之间发生RLF；
    当满足所述触发条件时，所述终端设备记录成功切换报告SHR，其中，所述SHR指示触发原因，所述触发原因为所述终端设备被触发记录所述SHR的原因。
  27. 根据权利要求26所述的方法，其特征在于，所述触发原因包括所述切换过程中所述终端设备与所述第一网络设备之间发生RLF。
  28. 根据权利要求26或27所述的方法，其特征在于，所述触发条件是所述第一网络设备确定的。
  29. 根据权利要求26至28任一项所述的方法，其特征在于，所述SHR指示所述触发原因，包括：所述SHR至少指示发生所述RLF的原因。
  30. 根据权利要求29所述的方法，其特征在于，所述RLF的原因包括以下至少一项：波束失败恢复失败，随机接入失败，重传次数达到最大次数，先听后说失败，RLF恢复失败，第二定时器超时，其中，所述第二定时器的运行时长指示所述终端设备检测到与所述第一网络设备之间有物理层问题的时长。
  31. 根据权利要求26至30任一项所述的方法，其特征在于，所述第一信息还包括随机接入的信息，所述随机接入的失败导致所述终端设备和所述第一网络设备发生所述RLF。
  32. 根据权利要求26至31任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述第一网络设备发送所述SHR，其中，所述第一网络设备是所述终端设备在所述切换过程前接入的网络设备，所述SHR用于确定网络优化参数。
  33. 根据权利要求26至32任一项所述的方法，其特征在于，所述终端设备向所述第一网络设备发送所述SHR，包括：
    所述终端设备通过第三网络设备向所述第一网络设备发送所述SHR。
  34. 一种通信方法，其特征在于，包括：
    第一网络设备向终端设备发送触发条件，其中，所述触发条件包括切换过程中所述终端设备与所述第一网络设备之间发生无线链路失败RLF，或者，所述触发条件至少包括所述终端设备和第二网络设备完成成功的随机接入之前，与所述第一网络设备之间发生RLF，所述触发条件用于所述终端设备在满足所述触发条件的情况下记录成功切换报告SHR，所述SHR指示触发原因，所述触发原因为所述终端设备被触发记录所述SHR的原因；
    所述第一网络设备接收来自所述终端设备的所述SHR，根据所述SHR确定网络优化参数。
  35. 根据权利要求34所述的方法，其特征在于，所述触发原因包括所述切换过程中所述终端设备与所述第一网络设备之间发生RLF。
  36. 根据权利要求34或35所述的方法，其特征在于，所述触发条件是所述第一网络设备确定的。
  37. 根据权利要求34至36任一项所述的方法，其特征在于，所述第一网络设备接收来自所述终端设备的所述SHR，包括：
    所述第一网络设备通过第三网络设备接收来自所述终端设备的所述SHR。
  38. 一种通信装置，其特征在于，包括：处理器和存储器，所述存储器存储有指令，当所述指令被所述处理器执行时，使得所述通信装置执行如权利要求1至7、或权利要求8至18、或权利要求19至25、或权利要求26至33中任一项所述的方法，或权利要求34至37中任一项所述的方法。
  39. 一种芯片，其特征在于，所述芯片包括处理电路和输入输出接口，所述输入输出接口用于与所述芯片之外的模块通信，所述处理电路用于运行计算机程序或指令，以使得通信设备执行如权利要求1至7、或权利要求8至18、或权利要求19至25、或权利要求26至33中任一项所述的方法，或权利要求34至37中任一项所述的方法。
  40. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序，所述程序被处理器调用时，如权利要求1至7、或权利要求8至18、或权利要求19至25、 或权利要求26至33中任一项所述的方法被执行，或权利要求34至37中任一项所述的方法被执行。
  41. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机如执行权利要求1至7、或权利要求8至18、或权利要求19至25、或权利要求26至33中任一项所述的方法，或权利要求34至37中任一项所述的方法。
PCT/CN2022/103435 2021-08-04 2022-07-01 通信方法及装置 WO2023011077A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110891888 2021-08-04
CN202110891888.2 2021-08-04
CN202111676240.X 2021-12-31
CN202111676240.XA CN115915202A (zh) 2021-08-04 2021-12-31 通信方法及装置

Publications (1)

Publication Number Publication Date
WO2023011077A1 true WO2023011077A1 (zh) 2023-02-09

Family

ID=85155072

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/103435 WO2023011077A1 (zh) 2021-08-04 2022-07-01 通信方法及装置

Country Status (1)

Country Link
WO (1) WO2023011077A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021086249A1 (en) * 2019-11-01 2021-05-06 Telefonaktiebolaget Lm Ericsson (Publ) Dual active protocol stack handover reports
CN112867075A (zh) * 2019-11-08 2021-05-28 华为技术有限公司 移动性优化方法及相关装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021086249A1 (en) * 2019-11-01 2021-05-06 Telefonaktiebolaget Lm Ericsson (Publ) Dual active protocol stack handover reports
CN112867075A (zh) * 2019-11-08 2021-05-28 华为技术有限公司 移动性优化方法及相关装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on other SON aspects", 3GPP DRAFT; R2-2103733, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic Meeting; 20210412 - 20210420, 2 April 2021 (2021-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052175129 *

Similar Documents

Publication Publication Date Title
US20200396652A1 (en) Method, apparatus, computer program product and computer program for conditional handover
EP3014944B1 (en) Master base station-controlled response to detected failure of radio link between secondary base station and mobile station in dual connectivity wireless networks
CN108924949B (zh) 无线网络中的通信方法、装置和系统
EP3592097B1 (en) Radio link failure handling method and related product
JP5537702B2 (ja) Ｒｒｃ接続プロセスを改善する方法及び通信装置
US20210251032A1 (en) Communication method, apparatus, and system
WO2021238774A1 (zh) 通信方法及装置
JP2023535123A (ja) マスターセルグループのための方法および装置
US20230199578A1 (en) Managing configurations
WO2021062669A1 (zh) 一种通信方法及通信装置
WO2017193387A1 (zh) 异制式小区间切换的方法及装置
WO2023011077A1 (zh) 通信方法及装置
WO2019153285A1 (zh) Rlc实体的配置方法及相关设备
WO2021027900A1 (zh) 一种通信方法、终端及网络设备
CN115915202A (zh) 通信方法及装置
WO2023011612A1 (zh) 移动性管理的方法及通信装置
WO2023207229A1 (zh) 一种会话建立方法及装置
WO2024017029A1 (zh) 一种通信方法、装置、存储介质和芯片系统
US20230345323A1 (en) Data transmission method and apparatus
WO2024046294A1 (zh) 通信方法和装置
WO2023131280A1 (zh) 信息记录方法、通信装置、以及计算机存储介质
WO2021147003A1 (zh) 通信方法及装置
WO2020164073A1 (zh) 条件触发的配置方法及相关产品
WO2021056449A1 (zh) 一种会话切换方法、装置及相关设备
JP2023029326A (ja) ハンドオーバを処理するデバイス及び方法

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: 22851792

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE