Report processing method, device, network node and terminal

Abstract

An embodiment of the present disclosure provides a report processing method, an apparatus, a network node, and a terminal, the method including: obtaining a Radio Link Failure (RLF) report and a handover success report, determining a related relationship between the RLF report and the handover success report, and analyzing a radio link failure cause or a handover failure cause according to the determined related relationship between the RLF report and the handover success report.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This disclosure claims priority to Chinese Patent Application No. 202110895728.5, filed in China on August 5, 2021, the entire contents of which are incorporated herein by reference. The present disclosure relates to the field of wireless technologies, and in particular to a report processing method, apparatus, network node and terminal. [Background technology]

[0002] During a Dual Active Protocol Stack (DAPS) handover procedure, a radio link failure may occur at the source side, but handover to the target side may be successful. In this case, radio link failure information at the source side is recorded in a handover success report and transmitted between network nodes using an access and mobility indication message. Meanwhile, a radio link failure may occur at the target side after handover, but after a random access failure or random access success, radio link failure information at the target side is recorded in a Radio Link Failure (RLF) report and transmitted between network nodes using a failure indication message. The source side is a node to which the terminal connected before performing a DAPS handover, and the target side is a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover.

[0003] In a DAPS handover scenario, the source network node can receive a handover success report and an RLF report through an access and mobility indication message and a failure indication message, and can further analyze the handover success report and the RLF report. However, research has found that there is a problem in analyzing the failure type according to the received handover success report and the RLF report, in that the analysis result is inaccurate. Summary of the Invention [Problem to be solved by the invention]

[0004] SUMMARY OF THE INVENTION Embodiments of the present disclosure provide a report processing method, an apparatus, a network node, and a terminal for solving at least one of the technical problems described above. [Means for solving the problem]

[0005] In one embodiment of the present disclosure, there is provided a report processing method applied to a terminal device, comprising: generating a Radio Link Failure (RLF) report carrying a terminal identifier and a handover success report carrying a terminal identifier, the handover success report being generated by the terminal device after a Dual Active Protocol Stack (DAPS) handover is successful, and the RLF report being generated by the terminal after an RLF occurs after a DAPS handover is successful; and and transmitting the generated Radio Link Failure (RLF) report and the handover success report to a network device.

[0006] Another embodiment of the present disclosure includes a report processing method performed by a first network node, the method comprising: Obtaining a radio link failure (RLF) report and a handover success report; determining the RLF report and the handover success report as being related; and analyzing a radio link failure cause or a handover failure cause according to the RLF report and the handover success report having the determined association relationship.

[0007] Optionally, in the report processing method, obtaining a radio link failure (RLF) report and a handover success report includes: receiving a Radio Link Failure (RLF) report and a handover success report sent from a second network node via a first interface message, the second network node being a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node being a node to which the terminal connected before performing the DAPS handover, the RLF report being obtained by the second network node from another network node, the other network node being a network node to which the terminal reconnected after an RLF occurred after the DAPS handover was successful; Determining the RLF report and the handover success report that are related to each other includes: The method includes determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other.

[0008] Optionally, in the report processing method, determining a Radio Link Failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other includes: One of the first interface messages includes, if a radio link failure (RLF) report and a handover success report generated by different terminals are carried, determining that the RLF report and the handover success report generated by the same terminal are related to each other.

[0009] Optionally, in the report processing method, obtaining a radio link failure (RLF) report and a handover success report includes: respectively obtaining an RLF report via a second interface message and obtaining a handover success report via a third interface message; Determining the RLF report and the handover success report that are related to each other includes: Determine an RLF report corresponding to the first terminal identifier according to a first terminal identifier carried in the second interface message, and determine a handover success report corresponding to the second terminal identifier according to a second terminal identifier carried in the third interface message; If the first terminal identifier and the second terminal identifier are the same, determining the RLF report corresponding to the first terminal identifier and the handover success report corresponding to the second terminal identifier as the RLF report and the handover success report that are related to each other.

[0010] Optionally, in the report processing method, the first interface message, the second interface message, and the third interface message are at least one or more of a failure indication message, a handover report message, an access and mobility indication message, and a specific message, respectively.

[0011] Optionally, in the report processing method, obtaining a Radio Link Failure (RLF) report and a handover success report specifically includes: obtaining a radio link failure (RLF) report and a handover success report sent from a terminal, the RLF report carrying a terminal identifier and the handover success report carrying a terminal identifier; Determining the RLF report and the handover success report that are related to each other specifically includes: According to a terminal identifier carried in the RLF report and a terminal identifier carried in a handover success report, determining the RLF report and the handover success report having the same terminal identifier as the RLF report and the handover success report that are related to each other.

[0012] Another embodiment of the present disclosure includes a report processing method applied in a second network node, the method comprising: Obtaining a radio link failure (RLF) report and a handover success report; There is further provided a report processing method, which includes sending the associated RLF report and the handover success report to a first network node, so that a radio link failure cause or a handover failure cause is analyzed by the first network node according to the associated RLF report and the handover success report.

[0013] Optionally, in the report processing method, obtaining a handover success report specifically includes: receiving a handover success report sent from a terminal, the handover success report being generated by the terminal after a successful DAPS handover; Obtaining a Radio Link Failure (RLF) report specifically involves: The method includes receiving an RLF report sent from another network node, the RLF report being generated by the terminal after an RLF occurs after a Dual Active Protocol Stack (DAPS) handover is successful, the other network node being a network node to which the terminal reconnects after an RLF occurs after a DAPS handover is successful.

[0014] Optionally, in the report processing method, sending the associated RLF report and handover success report to the first network node specifically includes: identifying the RLF report and the handover success report that are related, the RLF report and the handover success report being generated by the same terminal; and transmitting the identified associated RLF report and the handover success report to a first network node.

[0015] An embodiment of the present disclosure includes a terminal including a memory, a transceiver, and a processor, The memory is for storing a computer program, and the transceiver is for transmitting and receiving data under the control of the processor, and the processor reads the computer program in the memory and performs the following: An operation of generating a Radio Link Failure (RLF) report carrying a terminal identifier and a handover success report carrying a terminal identifier, the handover success report being generated by the terminal device after a Dual Active Protocol Stack (DAPS) handover is successful, and the RLF report being generated by the terminal after an RLF occurs after a DAPS handover is successful; and A terminal is further provided for performing an operation of transmitting the generated Radio Link Failure (RLF) report and the handover success report to a network device.

[0016] An embodiment of the present disclosure provides a first network node, the network node including a memory, a transceiver, and a processor, The memory is for storing a computer program, and the transceiver is for transmitting and receiving data under the control of the processor, and the processor reads the computer program in the memory and performs the following: obtaining a radio link failure (RLF) report and a handover success report; determining the RLF report and the handover success report that are related to each other; and performing an operation of analyzing a radio link failure cause or a handover failure cause according to the RLF report and the handover success report having the determined association relationship.

[0017] Optionally, in the network node, the processor obtaining a radio link failure (RLF) report and a handover success report comprises: receiving a Radio Link Failure (RLF) report and a handover success report sent from a second network node via a first interface message, the second network node being a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node being a node to which the terminal connected before performing the DAPS handover, the RLF report being obtained by the second network node from another network node, the other network node being a network node to which the terminal reconnected after an RLF occurred after the DAPS handover was successful; Determining the RLF report and the handover success report that are related to each other includes: The method includes determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other.

[0018] Optionally, in the network node, the processor determining a Radio Link Failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other includes: One of the first interface messages includes, if a radio link failure (RLF) report and a handover success report generated by different terminals are carried, determining that the RLF report and the handover success report generated by the same terminal are related to each other.

[0019] Optionally, in the network node, the processor obtaining a radio link failure (RLF) report and a handover success report comprises: respectively obtaining an RLF report via a second interface message and obtaining a handover success report via a third interface message; Determining the RLF report and the handover success report that are related to each other includes: Determine an RLF report corresponding to the first terminal identifier according to a first terminal identifier carried in the second interface message, and determine a handover success report corresponding to the second terminal identifier according to a second terminal identifier carried in the third interface message; If the first terminal identifier and the second terminal identifier are the same, determining the RLF report corresponding to the first terminal identifier and the handover success report corresponding to the second terminal identifier as the RLF report and the handover success report that are related to each other.

[0020] Optionally, in the network node, the first interface message, the second interface message and the third interface message are at least one or more of a failure indication message, a handover report message, an access and mobility indication message and a specific message, respectively.

[0021] Optionally, in the network node, the processor obtaining a radio link failure (RLF) report and a handover success report specifically includes: obtaining a radio link failure (RLF) report and a handover success report sent from a terminal, the RLF report carrying a terminal identifier and the handover success report carrying a terminal identifier; Determining the RLF report and the handover success report that are related to each other specifically includes: According to a terminal identifier carried in the RLF report and a terminal identifier carried in a handover success report, determining the RLF report and the handover success report having the same terminal identifier as the RLF report and the handover success report that are related to each other.

[0022] An embodiment of the present disclosure includes a second network node, the second network node including a memory, a transceiver, and a processor, The memory is for storing a computer program, and the transceiver is for transmitting and receiving data under the control of the processor, and the processor reads the computer program in the memory and performs the following: obtaining a radio link failure (RLF) report and a handover success report; and sending the associated RLF report and the handover success report to a first network node, so that a radio link failure cause or a handover failure cause is analyzed by the first network node according to the associated RLF report and the handover success report.

[0023] Optionally, in the network node, the processor obtaining a handover success report specifically includes: receiving a handover success report sent from a terminal, the handover success report being generated by the terminal after a successful DAPS handover; Specifically, the processor obtaining a radio link failure (RLF) report includes: The method includes receiving an RLF report sent from another network node, the RLF report being generated by the terminal after an RLF occurs after a Dual Active Protocol Stack (DAPS) handover is successful, the other network node being a network node to which the terminal reconnects after an RLF occurs after a DAPS handover is successful.

[0024] Optionally, in the network node, the processor sending the associated RLF report and handover success report to the first network node specifically comprises: identifying the RLF report and the handover success report that are related, the RLF report and the handover success report being generated by the same terminal; and transmitting the identified associated RLF report and the handover success report to a first network node.

[0025] An embodiment of the present disclosure includes a report processing device applied to a terminal, comprising: a report generation module for generating a Radio Link Failure (RLF) report carrying a terminal identifier and a handover success report carrying a terminal identifier, the handover success report being generated by the terminal device after a Dual Active Protocol Stack (DAPS) handover is successful, and the RLF report being generated by the terminal after an RLF occurs after a DAPS handover is successful; and A report processing device is further provided, including a second sending module for sending the generated Radio Link Failure (RLF) report and the handover success report to a network device.

[0026] An embodiment of the present disclosure includes a report processing device applied to a first network node, comprising: a first report obtaining module for obtaining a radio link failure (RLF) report and a handover success report; a determining module for determining the RLF report and the handover success report that are related to each other; and an analysis module for analyzing a radio link failure cause or a handover failure cause according to the RLF report and the handover success report having the determined association relationship.

[0027] Optionally, in the report processing device, the first report acquisition module acquires a radio link failure (RLF) report and a handover success report, receiving a Radio Link Failure (RLF) report and a handover success report sent from a second network node via a first interface message, the second network node being a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node being a node to which the terminal connected before performing the DAPS handover, the RLF report being obtained by the second network node from another network node, the other network node being a network node to which the terminal reconnected after an RLF occurred after the DAPS handover was successful; The determining module determines the RLF report and the handover success report that are related to each other, The method includes determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other.

[0028] Optionally, in the report processing device, the determining module determines the Radio Link Failure (RLF) report and the handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other: One of the first interface messages includes, if a radio link failure (RLF) report and a handover success report generated by different terminals are carried, determining that the RLF report and the handover success report generated by the same terminal are related to each other.

[0029] Optionally, in the report processing device, the first report acquisition module acquires a radio link failure (RLF) report and a handover success report, respectively obtaining an RLF report via a second interface message and obtaining a handover success report via a third interface message; The determining module determines the RLF report and the handover success report that are related to each other, Determine an RLF report corresponding to the first terminal identifier according to a first terminal identifier carried in the second interface message, and determine a handover success report corresponding to the second terminal identifier according to a second terminal identifier carried in the third interface message; If the first terminal identifier and the second terminal identifier are the same, determining the RLF report corresponding to the first terminal identifier and the handover success report corresponding to the second terminal identifier as the RLF report and the handover success report that are related to each other.

[0030] Optionally, in the report processing device, the first interface message, the second interface message and the third interface message are at least one or more of a failure indication message, a handover report message, an access and mobility indication message and a specific message, respectively.

[0031] Optionally, in the report processing device, the first report acquisition module acquires a radio link failure (RLF) report and a handover success report, specifically: obtaining a radio link failure (RLF) report and a handover success report sent from a terminal, the RLF report carrying a terminal identifier and the handover success report carrying a terminal identifier; The determining module determines the RLF report and the handover success report that are related to each other, specifically: According to a terminal identifier carried in the RLF report and a terminal identifier carried in a handover success report, determining the RLF report and the handover success report having the same terminal identifier as the RLF report and the handover success report that are related to each other.

[0032] An embodiment of the present disclosure includes a report processing device applied in a second network node, comprising: a second report obtaining module for obtaining a radio link failure (RLF) report and a handover success report; There is further provided a report processing device, including: a first sending module for sending the associated RLF report and the handover success report to a first network node, so that a radio link failure cause or a handover failure cause is analyzed by the first network node according to the associated RLF report and the handover success report.

[0033] Optionally, in the report processing device, the second report obtaining module obtains the handover success report, specifically: receiving a handover success report sent from a terminal, the handover success report being generated by the terminal after a successful DAPS handover; The second report acquisition module specifically acquires the radio link failure (RLF) report. The method includes receiving an RLF report sent from another network node, the RLF report being generated by the terminal after an RLF occurs after a Dual Active Protocol Stack (DAPS) handover is successful, the other network node being a network node to which the terminal reconnects after an RLF occurs after a DAPS handover is successful.

[0034] Optionally, in the report processing device, the first sending module sending the associated RLF report and the handover success report to the first network node specifically includes: identifying the RLF report and the handover success report that are related, the RLF report and the handover success report being generated by the same terminal; and transmitting the identified associated RLF report and the handover success report to a first network node.

[0035] An embodiment of the present disclosure further provides a processor-readable storage medium storing a computer program, the computer program causing the processor to execute the report processing method described in any one of the above claims.

[0036] An embodiment of the present disclosure further provides a computer-readable storage medium storing a computer program, the computer program being for causing the computer to execute the report processing method described in any one of the above claims.

[0037] An embodiment of the present disclosure further provides a communication device having a computer program stored therein, the computer program causing the communication device to execute a report processing method described in any one of the above claims. [Effects of the Invention]

[0038] The beneficial effects of the present disclosure are as follows: By adopting the report processing method described in the embodiments of the present disclosure, when transmitting Radio Link Failure (RLF) reports and handover success reports between network nodes, the RLF reports and handover success reports belonging to the same terminal that are sent are associated with each other, so that the network node can accurately analyze the cause of the handover failure, thereby ensuring the accuracy of the network node's analysis of the failure type and effectively optimizing handover parameters. [Brief explanation of the drawings]

[0039] In order to more clearly explain the technical aspects of the embodiments of the present disclosure or the prior art, the following briefly introduces drawings that need to be used in the description of the embodiments or the prior art. It should be apparent that the drawings in the following description are only some embodiments described in the present disclosure, and those skilled in the art can obtain other drawings based on these drawings without paying creative labor.

[0040] [Figure 1] FIG. 2 is a schematic diagram illustrating a handover flow suitable for a method according to an embodiment of the present disclosure. [Figure 2] FIG. 10 is a schematic diagram illustrating another handover flow suitable for the method according to an embodiment of the present disclosure. [Figure 3] FIG. 1 is a schematic diagram showing a handover report message transmission flow. [Figure 4] FIG. 10 is a schematic diagram showing the flow of a report processing method according to the first embodiment of the present disclosure. [Figure 5] 1 shows an example of an implementation flow employing the method according to the embodiment of the present disclosure. [Figure 6] 10 shows a second implementation flow employing the method according to the embodiment of the present disclosure. [Figure 7] FIG. 10 is a schematic diagram showing the flow of a report processing method according to a second embodiment of the present disclosure. [Figure 8] FIG. 10 is a schematic diagram showing the flow of a report processing method according to a third embodiment of the present disclosure. [Figure 9]FIG. 1 is a schematic diagram illustrating the structure of a network node according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is a schematic diagram illustrating the structure of a network node according to another embodiment of the present disclosure. [Figure 11] FIG. 2 is a schematic diagram illustrating the structure of a terminal described in an embodiment of the present disclosure. [Figure 12] FIG. 1 is a schematic diagram illustrating a structure of a report processing device according to a first embodiment of the present disclosure. [Figure 13] FIG. 10 is a schematic diagram illustrating the structure of a report processing device according to a second embodiment of the present disclosure. [Figure 14] FIG. 10 is a schematic diagram illustrating the structure of a report processing device according to a third embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0041] Hereinafter, the technical aspects of the embodiments of the present disclosure will be clearly and completely described with reference to the drawings in the embodiments of the present disclosure, but it should be apparent that the described embodiments are only some embodiments of the present disclosure, and are not all embodiments. Based on the embodiments of the present disclosure, other embodiments obtained by those skilled in the art without paying creative labor shall all fall within the scope of protection of the present disclosure.

[0042] In the specification and claims of this disclosure, terms such as "first," "second," and the like are used to distinguish between similar objects and are not necessarily used to describe a particular order or chronology. Such terms are interchangeable under appropriate circumstances, with the understanding that the embodiments of the disclosure described herein may be practiced in orders other than those illustrated or described herein. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a procedure, method, system, product, or apparatus comprising a series of steps or units is not limited to including only those steps or units explicitly listed, but may also include other steps or units not explicitly listed or that are inherent to the procedure, method, product, or apparatus.

[0043] In the embodiments of the present disclosure, the term "and / or" describes a relationship between related objects and indicates three possible relationships. For example, A and / or B may indicate three cases: only A exists, both A and B exist, and only B exists. The symbol " / " generally indicates an "or" relationship between the related objects before and after it. In the embodiments of the present disclosure, the term "plurality" refers to two or more, as well as other quantifiers.

[0044] In the embodiments of the present disclosure, terms such as "exemplary" or "for example" are intended to illustrate or explain by way of example. In the embodiments of the present disclosure, any embodiment or design described with terms such as "exemplary" or "for example" should not be construed as being more preferred or advantageous over other embodiments or designs. Where appropriate, terms such as "exemplary" or "for example" are used to present related concepts in a concrete form.

[0045] The report processing method, device, network node, and terminal according to the embodiments of the present disclosure can be applied to a wireless communication system, which may be a system employing a fifth generation (5G) mobile communication technology (hereinafter, abbreviated as a 5G system), and as will be appreciated by those skilled in the art, a 5G New Radio (NR) system is merely an example and not a limitation.

[0046] In order to clearly explain the technical aspects of the report processing method described in the embodiments of the present disclosure, the handover flow applied to the report processing method described in the present disclosure will be described below.

[0047] The reporting method described in this disclosure is applicable to conventional handover flows and DAPS handover flows.

[0048] FIG. 1 shows a schematic diagram of a conventional handover flow procedure, which includes the following steps 1 to 4.

[0049] Step 1 is to transmit a handover request and a handover response between network node 1 and network node 2 to hand over a terminal (User Equipment (UE)) from network node 1 (source network node) to network node 2 (target network node).

[0050] Step 2 is that network node 1 sends a synchronous reconfiguration message to the UE to cause the UE to immediately perform handover, disconnect from network node 1, and randomly access network node 2.

[0051] Step 3 is to complete the random access between the UE and the network node 2 and send a handover complete message to the network node 2.

[0052] Step 4 is that network node 2 sends a context release message to network node 1 to inform network node 1 to release the UE context.

[0053] FIG. 2 shows a schematic diagram of the DAPS handover flow procedure, which includes the following steps 1 to 10.

[0054] Step 1 is that the source network node sends a handover request to the target network node while the data transmission link between the source network node and the UE is maintained.

[0055] Step 2 is for the target network node to send a request confirmation message to the source network node.

[0056] Step 3 is for the source network node to send a handover indication to the UE.

[0057] Step 4 is for the UE to perform an access procedure to the target network node.

[0058] Step 5 is that after the UE completes the Radio Resource Control (RRC) reconfiguration, it sends an RRC connection reconfiguration complete message to the target network node.

[0059] Through the above steps 1 to 5, the original data transmission link between the source network node and the UE is maintained. If the target network node receives a handover indication from the source network node and an RRC connection reconfiguration complete message from the UE, downlink Packet Data Convergence Protocol (PDCP) data packets (data employing new security context ciphering or integrity protection procedures) or control frames to be transmitted are buffered and transmitted to the UE via the configured link.

[0060] Steps 6 and 7 are for the UE to simultaneously maintain data transmission and reception between the source network node and the target network node.

[0061] Step 8 is that the target network entity sends a release indication to the UE to notify the UE of the completion of data transmission and requests the UE to release the data connection between the source network node and the UE.

[0062] Step 9 is for the UE to stop uplink transmission and downlink reception between the source network node and the UE, and begin to release the entire source side Master Cell Group (MCG) configuration.

[0063] Step 10 is for the UE to continue transmitting and receiving data only to and from the target network node.

[0064] 1 and 2, which employ the report processing method described in the embodiments of the present disclosure, the UE is a user equipment (UE), which may be a terminal-side device such as a mobile phone, a tablet personal computer (PC), a laptop computer, a personal digital assistant (PDA), a mobile internet device (MID), or a wearable device. It should be noted that the embodiments of the present disclosure do not limit the specific type of the user terminal 11.

[0065] The network nodes (including source network nodes, target network nodes, etc.) may be base stations, such as 5G and later version base stations (e.g., gNB, 5G NR NB, ng-eNB, etc.), or base stations in other communication systems, or may be referred to as Node B. It should be noted that the embodiments of the present disclosure only take 5G base stations as examples, and the specific type of network node is not limited.

[0066] In addition, in the handover flow of the embodiment shown in FIGS. 1 and 2, the terminal side records an RLF report and a handover success report. Wherein, when a handover failure or RLF occurs, the terminal records an RLF report. The RLF report is used to record at least two scenarios, namely, a handover failure and a radio link failure, and one RLF report can only represent the recording of one scenario.

[0067] Optionally, the RLF report may include: Measurement results of a serving cell in front of the terminal; Measurement results of neighboring cells after the terminal confirms a handover failure or a radio link failure; Terminal location information, The terminal's failed cell identification information, such as Cell Global Identity (CGI) / Physical Cell Identity (PCI) frequency point, and re-establishment cell identity of the terminal; A UE reporting timer, which is the time length elapsed from when the terminal last confirmed receipt of a handover initiation message until the connection failed; a connection failure cause being a handover failure or a radio link failure; The Cell Radio Network Temporary Identifier (C-RNTI) used when the terminal failed to connect, and Radio link failure sub-causes are T310 timeout, or random access problem, or RLC layer reaching maximum number of retransmissions, or Beam Failure Recovery Failure (BFRF); The length of time that has elapsed since the terminal confirmed the connection failure until the terminal reports the RLF report, and The tracking area code (TAC) of the cell where the connection failed, Bluetooth (BT) related recording results, and a Wireless Local Area Network (WLAN).

[0068] Optionally, the recording scenes of the handover success report include the following scenes: During a conventional handover procedure, when the value of the length of the T310 timer, the T312 timer or the T304 timer of the terminal exceeds a predetermined threshold, the terminal records a handover success report. During the DAPS handover procedure, the terminal records a handover success report when the length value of the T310 timer, the T312 timer, or the T304 timer exceeds a predetermined threshold or when an RLF occurs on the source link. The contents of the handover success report include measurement information of the trigger time, cell identification information, terminal location information, timer value, and the like. After the UE records the RLF report and / or the handover success report, it sends the RLF report and / or the handover success report to the network node via an RRC connection establishment complete message, an RRC connection reconfiguration complete message, an RRC connection re-establishment complete message, or an RRC recovery complete message, or the network node sends a request message to the UE, and the UE sends the RLF report and / or the handover success report to the network node via a response message.

[0069] In addition, to solve the problem of failure in the mobility procedure of the terminal, a Mobility Robustness Optimization (MRO) scheme may be adopted to assist in network optimization. Wherein, when a handover failure or RLF occurs, the terminal records an RLF report. After the handover failure, the terminal performs cell selection, and then re-accesses the network through RRC connection re-establishment or RRC connection establishment, and notifies the network that the RLF report is stored on the terminal side. When necessary, the network side obtains the RLF report from the terminal and uses it for network optimization on the network side.

[0070] The MRO feature is mainly used to find and solve parameter configuration problems in mobility procedures, and three failure types are defined, including premature handover, too late handover, and handover to the wrong cell. A late handover occurs when a terminal camps stably on a source cell for a certain period of time, and then a radio link failure occurs, and the terminal attempts to access another cell through RRC connection re-establishment. Premature handover refers to a situation where the terminal fails to access the target cell during the handover procedure, or succeeds in accessing the target cell but immediately experiences a radio link failure, and then the terminal attempts to access the source cell by re-establishing the RRC connection. A handover to an incorrect cell means that during a handover procedure, the terminal fails to access the target cell, or succeeds in accessing the target cell but a radio link failure occurs immediately, and the terminal then attempts to access another cell different from the handover target cell and the source cell by re-establishing an RRC connection.

[0071] Whether the UE can stably camp on the target cell after the handover is completed is the key to determining the above failure type. If the UE can stably camp on, even if a failure occurs, it is unrelated to the previous handover because the UE can stably camp on the target cell after the handover is completed. If the UE cannot stably camp on, it may be due to the previous handover, such as an irrational selection of the target cell.

[0072] Whether the terminal is stably camped on is determined using the UE report timer in the RLF report, and if the value is relatively small, it indicates that the terminal is not stably camped on, and if the value is relatively large, it indicates that the terminal is stably camped on after a handover. If the value is 0, it indicates that a handover has not occurred.

[0073] Since DAPS handover maintains the connection with the source cell during the handover procedure, the failure scenarios are more complex. The scenarios for DAPS handover that are too late, too early, and handover to the wrong cell are as follows:

[0074] DAPS handover too late: After the terminal has been stably camped on the source cell for a certain period of time, a radio link failure occurs, and the terminal then attempts to access another different cell via RRC connection re-establishment. After the terminal has been stably camped on the source cell for a certain period of time, the DASP handover is successful and the terminal can stably camp on the target cell, but a radio link failure occurs in the source cell during the DASP handover procedure.

[0075] Premature DAPS handover: In the DAPS handover, the target cell is successfully accessed, but a radio link failure occurs immediately, and the terminal then attempts to access the source cell by re-establishing an RRC connection. During the DAPS handover procedure, the terminal fails to access the target cell and successfully falls back to the source cell without an RLF occurring within a certain period of time.

[0076] DAPS handover to wrong cell: During a DAPS handover procedure, an RLF occurs in the connection with the source cell, and the terminal fails to access the target cell, so the terminal attempts to access another cell different from the handover target cell and the source cell by causing an RRC connection re-establishment. During the DAPS handover procedure, if the terminal successfully accesses the target cell but then a radio link failure occurs immediately, the terminal attempts to access another cell different from the handover target cell and the source cell by causing an RRC connection re-establishment. If a radio link failure occurs in the source cell during the DAPS handover procedure, it is recorded in the handover success report, and if the target side subsequently fails to access or if the target side succeeds in random access but an RLF occurs immediately, it is recorded in the RLF report.

[0077] According to the above MRO characteristics, the message flows between network nodes include failure indication messages, handover report messages, and access and mobility indication messages. Among them, the failure indication message is A UE may re-access the network after a handover failure or RLF failure. After a network node obtains the UE's RLF report, if the current network node is not the node where the failure occurred, it needs to transfer related information such as the RLF report between network nodes to the network node where the failure occurred, in order to facilitate analysis and optimization by the network node where the failure occurred.

[0078] Optionally, the failure indication message is triggered by an RRC re-establishment request or an RRC establishment on the air interface, where for an RRC re-establishment request, optionally information carried in the RRC re-establishment request and a UE RLF report are included, and for an RRC establishment, the UE RLF report is included.

[0079] For handover report messages, The network node where the failure occurs may send a handover report message after analyzing the failure indication message, and optionally, the sending procedure includes the following steps 1 to 7, as shown in FIG. 3.

[0080] Step 1 is a successful handover of the UE from network node 1 to network node 2.

[0081] Step 2 is that network node 2 experiences a radio link failure (RLF).

[0082] Step 3 is for the UE to record the RLF report.

[0083] Step 4 is that the UE successfully accesses the network node 3.

[0084] Step 5 is for the network node 3 to obtain the RLF report of the UE.

[0085] Step 6 is that after the UE successfully hands over to network node 3, an RLF occurs, the failed base station is network node 2, and a failure indication message is sent to network node 2.

[0086] Step 7 is that after network node 2 analyzes the failure indication message, it finds that the RLF failure is caused by network node 1's unreasonable selection of the target cell during handover, and the handover failure type corresponds to handover to an incorrect cell, and network node 3 should have been selected, so it sends a handover report message to network node 1 to notify it.

[0087] Optionally, the handover report message includes information content such as a report type, a handover source cell, a handover target cell, an RRC re-establishment cell, and a UE RLF report; The report type indicates the analysis results of the failed node, including premature handover, handover to the wrong cell, etc. The handover source cell contains a global cell identifier identity document (ID), The handover target cell contains a global cell identifier ID, The RRC re-establishment cell includes a global cell identifier ID, and if the report type is a handover to a wrong cell, includes indication information of the RRC re-establishment cell to notify the source cell that the cell should be selected as a target cell for handover; The UE RLF report is an optional item, and if the UE RLF report is included in the received failure indication message, the UE RLF report is included when transmitting the handover report message.

[0088] The Access and Mobility Indication message is used to convey relevant information such as handover success reports between network nodes.

[0089] According to the above, during a DAPS handover procedure, a radio link failure may occur at the source side, and a random access failure may occur at the handover target side, or a radio link failure may occur immediately after successful random access. The failure information at the source side is recorded in a handover success report and transmitted between network nodes using an access and mobility indication message, while the failure information at the target side is recorded in an RLF report and transmitted between network nodes using a failure indication message. Because the network node at the handover source side may have already released the UE's context information after the handover is completed, when it receives the handover success report and the RLF report via the access and mobility indication message and the failure indication message, it does not know whether these reports correspond to the same UE. If the handover success report corresponds to UE1 and the RLF report corresponds to UE2, UE1 may count one DAPS handover error as too late, and UE2 may count one DAPS handover error as too early. If the handover success report and the RLF report belong to the same UE, the UE may count it once as a handover error to a wrong cell.

[0090] As can be seen from the above analysis, when analyzing a DAPS handover error, the source side needs to determine whether the handover success report and the RLF report belong to the same user; otherwise, separate analyses of the handover success report and the RLF report will lead to inaccurate analysis results.

[0091] To solve the above problem, an embodiment of the present disclosure provides a report processing method. When transmitting a Radio Link Failure (RLF) report and a handover success report between network nodes, the RLF report and the handover success report belonging to the same terminal are associated with each other. This allows the network node to accurately analyze the cause of the handover failure, ensures the accuracy of the network node's analysis of the failure type, and effectively optimizes handover parameters.

[0092] The report processing method according to an embodiment of the present disclosure is executed by a first network node, as shown in FIG. 4, and includes the following steps S410 to S430.

[0093] S410 is to obtain a radio link failure (RLF) report and a handover success report.

[0094] S420 is to determine the RLF report and the handover success report that are related to each other.

[0095] S430 is to analyze a radio link failure cause or a handover failure cause according to the determined associated RLF report and the handover success report.

[0096] In the embodiments of the present disclosure, optionally, the second network node may be, but is not limited to, a target network node after handover of the target terminal, and the first network node may be, but is not limited to, a source network node before handover of the target terminal.

[0097] According to the report processing method described in the embodiments of the present disclosure, when the second network node sends a Radio Link Failure (RLF) report and a handover success report to the first network node, the second network node can associate them with a terminal, i.e., indicate that the Radio Link Failure (RLF) report and the handover success report are associated with the same terminal, so that the first network node can analyze the failure type according to the associated Radio Link Failure (RLF) report and the handover success report, ensure the accuracy of the network node's analysis of the failure type, avoid analyzing the wrong type, and perform effective handover parameter optimization.

[0098] In one embodiment, in step S410, obtaining a radio link failure (RLF) report and a handover success report includes: receiving a Radio Link Failure (RLF) report and a handover success report sent from a second network node via a first interface message, the second network node being a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node being a node to which the terminal connected before performing the DAPS handover, the RLF report being obtained by the second network node from another network node, the other network node being a network node to which the terminal reconnected after an RLF occurred after the DAPS handover was successful; In step S420, determining the RLF report and the handover success report that are related to each other includes: The method includes determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other.

[0099] Optionally, determining a Radio Link Failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other includes: One of the first interface messages includes, if a radio link failure (RLF) report and a handover success report generated by different terminals are carried, determining that the RLF report and the handover success report generated by the same terminal are related to each other.

[0100] By adopting this embodiment, the second network node can send an RLF report and a handover success report to the first network node via the same interface message (first interface message), and associate the simultaneously sent Radio Link Failure (RLF) report and handover success report with the target terminal.

[0101] In this embodiment, optionally, a radio link failure (RLF) report and a handover success report associated with the target terminal transmitted from the second network node may be received via at least one of the XN interface, the X2 interface, the NG interface, and the S1 interface.

[0102] Optionally, a radio link failure (RLF) report and a handover success report associated with the target terminal sent from the second network node may be received via at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message. Among them, the specific message is a message that is pre-configured and specifically used to instruct the transmission of a Radio Link Failure (RLF) report and a handover success report.

[0103] Optionally, in the case of receiving a radio link failure (RLF) report and a handover success report transmitted from a second network node via a first interface message, the first interface message may include a report list, the report list including RLF reports and handover success reports generated by different terminals, and the target terminal being one of the different terminals.

[0104] Specifically, the report list includes at least one column, and each column records RLF reports and handover success reports corresponding to the same terminal, and the RLF report and handover success report of the target terminal are recorded in one column in the report list.

[0105] In addition, since the handover success report and the RLF report are non-real-time reports, the second network node may cache the handover success report and the RLF report generated by multiple UEs, and then simultaneously send the handover success report and the RLF report associated with the same terminal in one interface message. If the first interface message includes reports of multiple UEs, the reports of the multiple UEs may be conveyed in the form of a report list, where each node of the list represents a report of one UE, and each UE report includes the associated handover success report and the RLF report.

[0106] According to the method in the embodiment of the present disclosure, in another embodiment, in step S410, obtaining a radio link failure (RLF) report and a handover success report includes: respectively obtaining an RLF report via a second interface message and obtaining a handover success report via a third interface message; In step S420, determining the RLF report and the handover success report that are related to each other includes: Determine an RLF report corresponding to the first terminal identifier according to a first terminal identifier carried in the second interface message, and determine a handover success report corresponding to the second terminal identifier according to a second terminal identifier carried in the third interface message; If the first terminal identifier and the second terminal identifier are the same, determining the RLF report corresponding to the first terminal identifier and the handover success report corresponding to the second terminal identifier as the RLF report and the handover success report that are related to each other.

[0107] By adopting this embodiment, the second network node transmits a Radio Link Failure (RLF) report and a handover success report to the first network node via different interface messages, respectively, and can include a terminal identifier in the interface messages transmitting the Radio Link Failure (RLF) report and the handover success report, respectively. Therefore, the Radio Link Failure (RLF) report and the handover success report generated by the same terminal and transmitted via different interface messages can be associated according to the terminal identifier included in the interface message.

[0108] Optionally, when obtaining an RLF report through a second interface message, the second interface message includes a first report list, and the first report list includes an RLF report of at least one terminal; When the handover success report is obtained through a third interface message, the third interface message includes a second report list, and the second report list includes a handover success report of at least one terminal.

[0109] When this embodiment is adopted, the interface message may include a report list for sending a handover success report or an RLF report for at least one terminal, and the interface message may be provided with a terminal identifier corresponding to each handover success report or RLF report for indicating a terminal associated with each handover success report or RLF report.

[0110] Optionally, in this embodiment, when the RLF report is obtained through the second interface message or the handover success report is obtained through the third interface message, the second interface message and the third interface message are at least one or more of a failure indication message, a handover report message, an access and mobility indication message, and a specific message, respectively. Optionally, the sending interfaces of the second interface message and the third interface message are at least one of an XN interface, an X2 interface, an NG interface, and an S1 interface, respectively.

[0111] According to the method in the embodiment of the present disclosure, in another embodiment, in step S410, obtaining a Radio Link Failure (RLF) report and a handover success report specifically includes: obtaining a radio link failure (RLF) report and a handover success report sent from a terminal, the RLF report carrying a terminal identifier and the handover success report carrying a terminal identifier; In step S420, determining the RLF report and the handover success report that are related to each other specifically includes: According to a terminal identifier carried in the RLF report and a terminal identifier carried in a handover success report, determining the RLF report and the handover success report having the same terminal identifier as the RLF report and the handover success report that are related to each other.

[0112] By adopting this embodiment, when the terminal records the handover success report and the RLF report, the terminal identifier is added and recorded, so there is no need to add the terminal identifier in the interface message transmitting the handover success report or the RLF report.

[0113] In this way, after receiving the handover success report and the RLF report, the source network node (first network node) determines the associated handover success report and the RLF report through association by the terminal identifier in the handover success report and the RLF report, and analyzes the handover failure type.

[0114] An example of the procedure for implementing the report transmission method according to the embodiment of the present disclosure when each of the above embodiments is adopted will be described below.

[0115] Because there are relatively many DAPS failure scenarios, the transmission of a Radio Link Failure (RLF) report or a handover success report may occur in various different implementation scenarios. In order to clearly explain the implementation procedure of the report transmission method described in the embodiments of the present disclosure, the most typical failure scenario in DAPS will be taken as an example, in which a Radio Link Failure occurs at a source network node during a DAPS handover procedure, and the terminal succeeds in random access to a target network node of the DAPS handover but immediately generates an RLF, and then recovers connection at another network node. A specific embodiment in which steps S410 to S430 of the present disclosure obtain a Radio Link Failure (RLF) report and a handover success report and determine the associated RLF report and the handover success report will be introduced in detail.

[0116] It should be noted that the report transmission method described in the embodiments of the present disclosure is not limited to being applicable only to DAPS handover procedures, but may also be applied to conventional handover procedures, and is not limited to being applicable only to the failure scenarios described below by way of example.

[0117] Embodiment 1 In embodiment 1, a form is adopted in which a radio link failure (RLF) report and a handover success report transmitted from a second network node are received via a first interface message, and the radio link failure (RLF) report and the handover success report are associated with each other.

[0118] In this embodiment, when the second network node sends a radio link failure (RLF) report and a handover success report through a first interface message, The second network node obtains a handover success report sent by the target terminal after the target terminal has successfully handed over from the first network node to the second network node; After an RLF occurs in the second network node and the target terminal connects to a third network node, the second network node acquires an RLF report of the target terminal, which is sent by the third network node through a failure indication message; Wherein, the second network node sends an RLF report and a handover success report associated with the target terminal to the first network node via a first interface message; The method includes associating the handover success report and the RLF report, and sending the RLF report and the handover success report of the target terminal to a first network node via a first interface message.

[0119] In this embodiment, after obtaining the handover success report and the RLF report respectively, the second network node associates the handover success report and the RLF report, and sends the RLF report and the handover success report of the target terminal to the first network node through the same interface message.

[0120] As shown in FIG. 5, the specific implementation procedure of this embodiment includes the following steps S510 to S580.

[0121] S510 is that the UE performs a DAPS handover from a first network node (source network node) to a second network node (target network node).

[0122] S520 is when a radio link failure occurs in the first network node (source network node), and the UE records a handover success report.

[0123] S530 is the successful completion of the DAPS handover.

[0124] S540 is a step in which the second network node (target network node) receives the UE information. Report and obtain a handover success report recorded by the UE; and optionally, UE information request message may be sent to the UE to request the UE to obtain the handover success report.

[0125] S550 is when a radio link failure occurs in the second network node (target network node), and the UE records an RLF report.

[0126] S560 is that the UE reconnects to another network node (third network node), and the third network node obtains the RLF report recorded by the UE.

[0127] S570 is the third network node sending an RLF report to the second network node (target network node) via a failure indication message.

[0128] In S580, the second network node (target network node) identifies the received RLF report, and identifies the RLF report and the handover success report belonging to the same terminal according to the previously obtained handover success report, and sends the identified RLF report and the handover success report belonging to the same terminal to the first network node (source network node) via the same interface message (first interface message), which is used to indicate that the sent RLF report and the handover success report belong to the same terminal.

[0129] Optionally, the second network node may identify whether the received RLF report and handover success report belong to the same terminal according to at least one of location information, a terminal identifier, a cell identifier, etc. in the RLF report and the handover success report.

[0130] Meanwhile, optionally, when an RLF report and a handover success report associated with the target terminal are sent to the second network node via a first interface message, the first interface message includes a report list, the report list includes an RLF report and a handover success report respectively associated with at least one terminal, and the target terminal is one of the at least one terminal.

[0131] Specifically, the report list includes at least one report node, and in each report node, RLF reports and handover success reports corresponding to the same terminal are recorded, and the RLF report and handover success report of the target terminal are recorded in one report node.

[0132] In addition, since the handover success report and the RLF report are non-real-time reports, the base station may cache the handover success report and the RLF report of multiple users and then simultaneously send the handover success report and the RLF report associated with the same terminal in one interface message. If the message includes reports of multiple UEs, the reports of the multiple UEs may be conveyed in the form of a report list, where each node of the list represents a report of one UE, and each UE report includes the associated handover success report and the RLF report.

[0133] In an embodiment of the present disclosure, optionally, when the RLF report and the handover success report are sent through the same interface message (first interface message), the sending interface of the first interface message is at least one of an XN interface, an X2 interface, an NG interface, and an S1 interface.

[0134] Alternatively, the first interface message may be an XN or X2 interface, and may be sent via an NG or S1 interface if there is no XN or X2 connection between the network side nodes.

[0135] Alternatively, in another embodiment, when the RLF report and the handover success report are sent via the same interface message (first interface message), the first interface message may be transmitted via at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message.

[0136] Embodiment 2 In embodiment 2, the first network node obtains the RLF report through a second interface message and obtains the handover success report through a third interface message, In a second aspect, the second interface message and the third interface message each include an identifier of the target terminal.

[0137] By adopting this embodiment, the second network node sending an RLF report to the first network node via a second interface message and sending a handover success report to the first network node via a third interface message includes: If the second network node receives a handover success report sent by the target terminal after the target terminal has successfully handed over from the first network node to the second network node, sending the handover success report to the first network node via a third interface message; If the target terminal reconnects to a third network node and the second network node acquires the RLF report of the target terminal sent by the third network node via a failure indication message, sending the RLF report to the first network node via a second interface message.

[0138] By adopting this embodiment, the handover success report and the RLF report are sent to the first network node through different interface messages, and after receiving the handover success report, there is no need to wait for the subsequent RLF report, but it can be sent immediately to the source network node, and the interface message sending the handover success report and the interface message sending the RLF report are associated with each other through the terminal identifiers they contain.

[0139] As shown in FIG. 6, the specific implementation procedure of this embodiment includes the following steps S610 to S690.

[0140] S610 is that the UE performs a DAPS handover from a first network node (source network node) to a second network node (target network node).

[0141] S620: A radio link failure occurs in the first network node (source network node), and the UE records a handover success report.

[0142] S630 is the successful completion of the DAPS handover.

[0143] S640 is a second network node (target network node) that receives UE information. Report and obtain a handover success report recorded by the UE; and optionally, UE information request message may be sent to the UE to request the UE to obtain the handover success report.

[0144] S650 is that after the second network node (target network node) obtains the handover success report, it immediately sends the handover success report to the first network node (source network node) via an interface message (third interface message).

[0145] S660 is when a radio link failure occurs in the second network node (target network node), and the UE records an RLF report.

[0146] S670 is that the UE reconnects to another network node (third network node), and the third network node obtains the RLF report recorded by the UE.

[0147] S680 is that the third network node sends an RLF report to the second network node (target network node) via a failure indication message.

[0148] S690 is that the second network node (target network node) sends an RLF report to the first network node (source network node) through an interface message (eg, a second interface message).

[0149] In this embodiment, in steps S650 and S690, when the second network node sends a handover success report and an RLF report to the first network node through an interface message, the sent interface message includes a UE identifier to identify that the handover success report and the RLF report correspond to the same terminal.

[0150] After the terminal is handed over from the source network node to the target network node, the source network node may have already deleted the user's context information, and the user's context information may no longer be obtained according to the UE identifier. However, according to the UE identifier included in the interface message, the second interface message sending the RLF report and the third interface message sending the handover success report can be associated to determine that the handover success report and the RLF report correspond to the same terminal.

[0151] Optionally, when sending the RLF report to the first network node via a second interface message, the second interface message includes a first report list, and the first report list includes the RLF report of at least one terminal; When sending a handover success report to the first network node through a third interface message, the third interface message includes a second report list, and the second report list includes a handover success report of at least one terminal; Here, the target terminal is one of the at least one terminal.

[0152] When this embodiment is adopted, the interface message may include a report list for sending a handover success report or an RLF report for at least one terminal, and the interface message may be provided with a terminal identifier corresponding to each handover success report or RLF report for indicating a terminal associated with each handover success report or RLF report.

[0153] In an embodiment of the present disclosure, optionally, when the second network node sends an RLF report to the first network node via a second interface message and sends a handover success report to the first network node via a third interface message, the second interface message and the third interface message may be transmitted via at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message.

[0154] In an embodiment of the present disclosure, optionally, when the second network node sends an RLF report through a second interface message and sends a handover success report through a third interface message, the sending interfaces of the second interface message and the third interface message are at least one of an XN interface, an X2 interface, an NG interface, and an S1 interface, respectively.

[0155] Alternatively, the second interface message and the third interface message may be respectively an XN interface or an X2 interface, and may be sent via an NG interface or an S1 interface if there is no XN interface or X2 connection between the network side nodes.

[0156] Comparing form 1 and form 2, both require the target network node to identify that the handover success report and the RLF report belong to the same terminal. Among them, form 2 allows the target network node to immediately send the handover success report to the source network node after receiving the handover success report without waiting for a subsequent RLF report, as compared with form 1. Optionally, according to this embodiment, the source network node is not necessarily limited to immediately performing handover analysis and optimization after receiving the handover success report, and may need to wait to check whether there is a subsequent RLF report.

[0157] Embodiment 3 In embodiment 3, a form is adopted in which the second network node sends an RLF report to the first network node via a second interface message and sends a handover success report to the first network node via a third interface message, and the RLF report and the handover success report each include an identifier of the target terminal.

[0158] Alternatively, the handover flow in the specific implementation of this embodiment may be the same as that of embodiment 2. Hereinafter, the specific embodiment of embodiment 3 will be described by continuing to use the implementation flow shown in FIG. 6.

[0159] As shown in FIG. 6, the specific implementation procedure of the third embodiment includes the following steps S610 to S690.

[0160] S610 is that the UE performs a DAPS handover from a first network node (source network node) to a second network node (target network node).

[0161] S620: A radio link failure occurs in the first network node (source network node), and the UE records a handover success report.

[0162] S630 is the successful completion of the DAPS handover.

[0163] S640 is a second network node (target network node) that receives UE information. Report and starting a handover process to obtain a handover success report recorded by the UE. In this embodiment, the handover success report recorded by the UE includes a terminal identifier, so that the handover success report obtained by the second network node includes a terminal identifier; Selectively, UE information request message may be sent to the UE to request the UE to obtain the handover success report.

[0164] S650 is that after the second network node (target network node) obtains the handover success report, it immediately sends the handover success report to the first network node (source network node) via an interface message (third interface message).

[0165] S660: When a radio link failure occurs in the second network node (target network node), the UE records an RLF report. In this embodiment, the RLF report recorded by the UE includes a terminal identifier.

[0166] S670 is that the UE reconnects to another network node (third network node), and the third network node obtains the RLF report recorded by the UE.

[0167] S680 is that the third network node sends an RLF report to the second network node (target network node) via a failure indication message.

[0168] S690 is that the second network node (target network node) sends an RLF report to the first network node (source network node) through an interface message (eg, a second interface message).

[0169] When the third embodiment is adopted, compared to the second embodiment, the terminal adds and records a terminal identifier when recording a handover success report and an RLF report, so there is no need to add a terminal identifier in the interface message transmitting the handover success report or the RLF report.

[0170] In this embodiment, after receiving the handover success report and the RLF report, the source network node determines the associated handover success report and the RLF report through association by the terminal identifier in the handover success report and the RLF report, and analyzes the handover failure type.

[0171] In the third embodiment, optionally, similar to the second embodiment, when the second network node sends an RLF report to the first network node through a second interface message, the second interface message includes a first report list, and the first report list includes an RLF report of at least one terminal; When the second network node sends a handover success report to the first network node through a third interface message, the third interface message includes a second report list, and the second report list includes a handover success report of at least one terminal; Here, the target terminal is one of the at least one terminal.

[0172] When this embodiment is adopted, the interface message may include a report list for sending a handover success report or an RLF report of at least one terminal, and each handover success report and each RLF report may include a corresponding terminal identifier for indicating a terminal associated with each handover success report or each RLF report.

[0173] In an embodiment of the present disclosure, optionally, as in embodiment 2, when an RLF report is sent to the first network node via a second interface message and a handover success report is sent to the first network node via a third interface message, the second interface message and the third interface message may be transmitted via at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message.

[0174] In an embodiment of the present disclosure, optionally, when the second network node sends an RLF report through a second interface message and sends a handover success report through a third interface message, the sending interfaces of the second interface message and the third interface message are at least one of an XN interface, an X2 interface, an NG interface, and an S1 interface, respectively.

[0175] Alternatively, the second interface message and the third interface message may be respectively an XN interface or an X2 interface, and may be sent via an NG interface or an S1 interface if there is no XN interface or X2 connection between the network side nodes.

[0176] By adopting any one of the above embodiments of the report transmission method described in the embodiments of the present disclosure, when transmitting Radio Link Failure (RLF) reports and handover success reports between network nodes, the RLF reports and handover success reports belonging to the same terminal that are sent are associated with each other, allowing the network node to jointly analyze the handover success reports and RLF reports belonging to the same terminal, thereby ensuring that the cause of handover failure can be accurately analyzed, ensuring the accuracy of the network node's analysis of the failure type, and effectively optimizing handover parameters.

[0177] Another embodiment of the present disclosure provides a report processing method applied to a second network node, and as shown in FIG. 7, the method includes the following steps S710 to S720.

[0178] S710 is to obtain a radio link failure (RLF) report and a handover success report.

[0179] S720 sends the associated RLF report and the handover success report to a first network node, so that the first network node analyzes a radio link failure cause or a handover failure cause according to the associated RLF report and the handover success report.

[0180] By adopting the method described in the embodiments of the present disclosure, when transmitting Radio Link Failure (RLF) reports and handover success reports between network nodes, the RLF reports and handover success reports belonging to the same terminal that are sent are associated with each other, so that the network node can accurately analyze the cause of the handover failure, thereby ensuring the accuracy of the network node's analysis of the failure type and effectively optimizing handover parameters.

[0181] In an embodiment of the present disclosure, optionally, the second network node is a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node is a node to which the terminal connected before performing the DAPS handover, the RLF report is obtained by the second network node from another network node, and the other network node is a network node to which the terminal reconnects after an RLF occurs after the DAPS handover is successful.

[0182] In the embodiment of the present disclosure, optionally, in step S710, obtaining a handover success report specifically includes: receiving a handover success report sent from a terminal, the handover success report being generated by the terminal after a successful DAPS handover; Obtaining a Radio Link Failure (RLF) report specifically involves: The method includes receiving an RLF report sent from another network node, the RLF report being generated by the terminal after an RLF occurs after a Dual Active Protocol Stack (DAPS) handover is successful, the other network node being a network node to which the terminal reconnects after an RLF occurs after a DAPS handover is successful.

[0183] Optionally, in the report processing method, in step S720, sending the associated RLF report and the handover success report to the first network node specifically includes: identifying the RLF report and the handover success report that are related, the RLF report and the handover success report being generated by the same terminal; and transmitting the identified associated RLF report and the handover success report to a first network node.

[0184] In an embodiment of the present disclosure, optionally, in step S720: 1. The method of claim 1, wherein the method comprises transmitting an RLF report and a handover success report associated with the terminal to a first network node via a first interface message; A form 2 in which an RLF report is transmitted to the first network node via a second interface message, and a handover success report is transmitted to the first network node via a third interface message, wherein the second interface message and the third interface message each include an identifier of a terminal; and form 3: transmitting an RLF report to the first network node via a second interface message and transmitting a handover success report to the first network node via a third interface message, wherein the RLF report and the handover success report each include an identifier of the terminal, and transmitting the associated RLF report and handover success report to the first network node in one of the forms.

[0185] When adopting the report processing method described in the embodiments of the present disclosure, if form 1 is adopted, the second network node can simultaneously transmit a Radio Link Failure (RLF) report and a handover success report to the first network node in the same interface message (first interface message), and can associate the simultaneously transmitted Radio Link Failure (RLF) report and handover success report with a terminal; When the second aspect is adopted, the second network node transmits a Radio Link Failure (RLF) report and a handover success report to the first network node via different interface messages, respectively, and the interface messages transmitting the Radio Link Failure (RLF) report and the handover success report can include an identifier of the target terminal, respectively. Therefore, according to the identifier of the target terminal included in the interface message, it is possible to associate the Radio Link Failure (RLF) report and the handover success report corresponding to the same target terminal in the interface message; When the third aspect is adopted, the second network node transmits a radio link failure (RLF) report and a handover success report to the first network node via different interface messages, respectively, and can include a terminal identifier in each of the transmitted radio link failure (RLF) report and handover success report. Therefore, the radio link failure (RLF) report and handover success report corresponding to the same terminal can be identified by the terminal identifier. When this embodiment is adopted, optionally, when the terminal generates a Radio Link Failure (RLF) report and a handover success report, the terminal writes an identifier of the terminal into the generated Radio Link Failure (RLF) report and handover success report, i.e., compared to the prior art, the transmission content of the air interface is changed to send a Radio Link Failure (RLF) report or a handover success report including the terminal identifier to the network node.

[0186] In an embodiment of the present disclosure, a radio link failure (RLF) report and a handover success report associated with the target terminal may be selectively sent to the first network node via at least one of an XN interface, an X2 interface, an NG interface, and an S1 interface.

[0187] In another embodiment, a radio link failure (RLF) report and a handover success report associated with the target terminal may be selectively sent to the first network node via at least one of a failure indication message, a handover report message, an access and mobility indication message and a specific message. Among them, the specific message is a message that is pre-configured and specifically used to instruct the transmission of a Radio Link Failure (RLF) report and a handover success report.

[0188] Another embodiment of the present disclosure further provides a report processing method applied to a terminal device, and as shown in FIG. 8, the method includes the following steps S810 to S820.

[0189] S810 is to generate a Radio Link Failure (RLF) report carrying a terminal identifier and a handover success report carrying a terminal identifier, wherein the handover success report is generated by the terminal device after a Dual Active Protocol Stack (DAPS) handover is successful, and the RLF report is generated by the terminal after an RLF occurs after a DAPS handover is successful.

[0190] S820 is to send the generated Radio Link Failure (RLF) report and handover success report to a network device.

[0191] When this embodiment is adopted, the terminal adds and records a terminal identifier when recording a handover success report and an RLF report, so there is no need to add the terminal identifier to the interface message transmitting the handover success report or the RLF report. In this way, when a Radio Link Failure (RLF) report and a handover success report are transmitted between network nodes, the RLF report and the handover success report of the same terminal are associated according to the terminal identifier in the handover success report and the terminal identifier in the RLF report, so that the network node can accurately analyze the cause of the handover failure, ensuring the accuracy of the analysis of the failure type by the network node and effectively optimizing handover parameters.

[0192] In the embodiments of the present disclosure, the information content included in the RLF report and the handover success report, and the specific procedures for transmitting the RLF report and the handover success report between network nodes can be referred to in the above detailed description in conjunction with Figures 1 to 3, and will not be described in detail here.

[0193] In one embodiment of the present disclosure, a report processing method is performed by a second network node, the method comprising: Sending a radio link failure (RLF) report and a handover success report associated with the target terminal to the first network node.

[0194] According to the report processing method described in the embodiment of the present disclosure, when the second network node sends a Radio Link Failure (RLF) report and a handover success report to the first network node, the second network node can associate them with a target terminal, i.e., indicate that the Radio Link Failure (RLF) report and the handover success report are associated with the same target terminal, so that the first network node can analyze the failure type according to the associated Radio Link Failure (RLF) report and the handover success report, ensure the accuracy of the network node's analysis of the failure type, avoid analyzing the wrong type, and perform effective handover parameter optimization.

[0195] In an embodiment of the present disclosure, optionally: 1. The method of claim 1, wherein the method comprises transmitting an RLF report and a handover success report associated with the target terminal to a first network node via a first interface message; A form in which an RLF report is sent to the first network node via a second interface message, and a handover success report is sent to the first network node via a third interface message, wherein the second interface message and the third interface message each include an identifier of the target terminal; and and (3) a form in which a radio link failure (RLF) report and a handover success report associated with the target terminal are sent to the first network node via a second interface message and a third interface message, respectively, the RLF report and the handover success report including an identifier of the target terminal.

[0196] In an embodiment of the present disclosure, optionally, the second network node is a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node is a node to which the terminal connected before performing the DAPS handover, the RLF report is obtained by the second network node from another network node, and the other network node is a network node to which the terminal reconnects after an RLF occurs after the DAPS handover is successful. When adopting the report processing method described in the embodiments of the present disclosure, if form 1 is adopted, the second network node can simultaneously send a radio link failure (RLF) report and a handover success report to the first network node in the same interface message (first interface message), and can associate the simultaneously sent radio link failure (RLF) report and handover success report with the target terminal.

[0197] When form 2 is adopted, the second network node transmits a radio link failure (RLF) report and a handover success report to the first network node via different interface messages, respectively, and can include an identifier of the target terminal in each of the interface messages transmitting the radio link failure (RLF) report and the handover success report. Therefore, according to the identifier of the target terminal included in the interface message, it is possible to associate the radio link failure (RLF) report and the handover success report corresponding to the same target terminal in the interface message.

[0198] When the third aspect is adopted, the second network node transmits a radio link failure (RLF) report and a handover success report to the first network node via different interface messages, respectively, and the transmitted radio link failure (RLF) report and handover success report can include an identifier of the target terminal, so that the radio link failure (RLF) report and handover success report of the same target terminal can be associated according to the identifier of the target terminal. When this embodiment is adopted, optionally, when the target terminal generates the radio link failure (RLF) report and handover success report, the target terminal writes the identifier of the target terminal into the generated radio link failure (RLF) report and handover success report. That is, compared with the prior art, the content of the message of the air interface is changed to transmit the radio link failure (RLF) report or handover success report including the identifier of the target terminal to the network node.

[0199] In an embodiment of the present disclosure, a radio link failure (RLF) report and a handover success report associated with the target terminal may be selectively sent to the first network node via at least one of an XN interface, an X2 interface, an NG interface, and an S1 interface.

[0200] In another embodiment, a radio link failure (RLF) report and a handover success report associated with the target terminal may be selectively sent to the first network node via at least one of a failure indication message, a handover report message, an access and mobility indication message and a specific message. Among them, the specific message is a message that is pre-configured and specifically used to instruct the transmission of a Radio Link Failure (RLF) report and a handover success report.

[0201] By adopting any one of the above embodiments of the report processing method described in the embodiments of the present disclosure, when transmitting Radio Link Failure (RLF) reports and handover success reports between network nodes, the RLF reports and handover success reports belonging to the same terminal that are sent are associated, so that the network node can jointly analyze the handover success reports and RLF reports belonging to the same terminal, thereby ensuring that the cause of handover failure can be accurately analyzed, ensuring the accuracy of the network node's analysis of the failure type, and effectively optimizing handover parameters.

[0202] Another embodiment of the present disclosure further provides a report processing method performed by a first network node, the method comprising: Obtaining a radio link failure (RLF) report and a handover success report associated with the target terminal; and analyzing a radio link failure cause or a handover failure cause according to the RLF report and the handover success report.

[0203] According to the report processing method described in the embodiment of the present disclosure, when the second network node sends a Radio Link Failure (RLF) report and a handover success report to the first network node, the second network node can associate them with a target terminal, i.e., indicate that the Radio Link Failure (RLF) report and the handover success report are associated with the same target terminal, so that the first network node can analyze the failure type according to the associated Radio Link Failure (RLF) report and the handover success report, ensure the accuracy of the network node's analysis of the failure type, avoid analyzing the wrong type, and perform effective handover parameter optimization.

[0204] Optionally, the report processing method further comprises: obtaining the RLF report and the handover success report associated with the target terminal transmitted from a second network node via a first interface message; A form in which the RLF report transmitted from a third network node is obtained via a second interface message, and the handover success report transmitted from a fourth network node is obtained via a third interface message, wherein the second interface message and the third interface message each include an identifier of the target terminal; The radio link failure (RLF) report and the handover success report associated with the target terminal are obtained in one of the following forms: obtaining the RLF report transmitted from the third network node via a second interface message; and obtaining the handover success report transmitted from the fourth network node via a third interface message, wherein the RLF report and the handover success report each include an identifier of the target terminal.

[0205] It should be noted that the above-mentioned second network node, third network node and fourth network node are network nodes that can send an RLF report or a handover success report to the first network node, respectively, and their names are only used to distinguish different network nodes, and specifically may be the same or different network nodes.

[0206] Optionally, in the report processing method, when the RLF report and the handover success report associated with the target terminal transmitted from a second network node via a first interface message are obtained, the first interface message includes a report list, the report list includes the RLF report and the handover success report respectively associated with at least one terminal, and the target terminal is one of the at least one terminal.

[0207] Optionally, in the report processing method, when an RLF report transmitted from a third network node is obtained through a second interface message, the second interface message includes a first report list, and the first report list includes an RLF report of at least one terminal; When obtaining a handover success report transmitted from a fourth network node through a third interface message, the third interface message includes a second report list, and the second report list includes a handover success report of at least one terminal; Here, the target terminal is one of the at least one terminal.

[0208] Optionally, in the report processing method, the first interface message, the second interface message, and the third interface message are transmitted via at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message.

[0209] Optionally, in the report processing method, the sending interfaces of the first interface message, the second interface message and the third interface message are at least one of an XN interface, an X2 interface, an NG interface and an S1 interface.

[0210] Optionally, in the report processing method, the first network node is a source network node of the target terminal, and the second network node is a target network node of the target terminal; or The first network node is a source network node of the target terminal, and the third network node and the fourth network node are: Source network node and a target network node; The network node is one of the source network node and the target network node.

[0211] It should be noted that in the embodiments of the present disclosure, with reference to Figures 5 and 6, an example is given in which the network node that sends the RLF report and the handover success report is the target network node, respectively. However, the application scenarios adopting the methods described in the embodiments of the present disclosure are not limited to the scenarios shown in Figures 5 and 6, and the network node that can send the RLF report or the handover success report to the source network node is not limited to the target network node, but may be any one of the network nodes listed above.

[0212] Optionally, in the report processing method, analyzing a radio link failure cause or a handover failure cause according to the RLF report and the handover success report having a determined association relationship may include: According to the RLF report and the handover success report, analyzing whether the cause of the radio link failure or the cause of the handover failure is a handover that is too late, a handover that is too early, or a handover to a wrong cell.

[0213] It should be noted that all descriptions of the report processing method performed by the first network node in the above embodiment are applicable to the embodiment of the report processing method performed by the second network node, and can achieve the same technical effects, but will not be described in detail here.

[0214] As shown in FIG. 9 , an embodiment of the present disclosure further provides a network node, which is a first network node, including a processor 900, a transceiver 910, a memory 920, and a program stored in the memory 920 and operable on the processor 900, wherein the transceiver 910 is connected to the processor 900 and the memory 920 via a bus interface, and the transceiver 910 is for transmitting and receiving data under the control of the processor 900; The processor 900 reads the program in the memory and obtaining a Radio Link Failure (RLF) report and a handover success report; determining the RLF report and the handover success report that are related to each other; and performing a procedure for analyzing a cause of a radio link failure or a handover failure according to the RLF report and the handover success report having the determined association relationship.

[0215] Optionally, in the network node, the processor 900 obtaining a radio link failure (RLF) report and a handover success report comprises: receiving a Radio Link Failure (RLF) report and a handover success report sent from a second network node via a first interface message, the second network node being a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node being a node to which the terminal connected before performing the DAPS handover, the RLF report being obtained by the second network node from another network node, the other network node being a network node to which the terminal reconnected after an RLF occurred after the DAPS handover was successful; Determining the RLF report and the handover success report that are related to each other includes: The method includes determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other.

[0216] Optionally, in the network node, the processor 900 determines a Radio Link Failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other, One of the first interface messages includes, if a radio link failure (RLF) report and a handover success report generated by different terminals are carried, determining that the RLF report and the handover success report generated by the same terminal are related to each other.

[0217] Optionally, in the network node, the processor 900 obtaining a radio link failure (RLF) report and a handover success report comprises: respectively obtaining an RLF report via a second interface message and obtaining a handover success report via a third interface message; Determining the RLF report and the handover success report that are related to each other includes: Determine an RLF report corresponding to the first terminal identifier according to a first terminal identifier carried in the second interface message, and determine a handover success report corresponding to the second terminal identifier according to a second terminal identifier carried in the third interface message; If the first terminal identifier and the second terminal identifier are the same, determining the RLF report corresponding to the first terminal identifier and the handover success report corresponding to the second terminal identifier as the RLF report and the handover success report that are related to each other.

[0218] Optionally, in the network node, the first interface message, the second interface message and the third interface message are at least one or more of a failure indication message, a handover report message, an access and mobility indication message and a specific message, respectively.

[0219] Optionally, in the network node, the processor 900 obtaining a Radio Link Failure (RLF) report and a handover success report specifically comprises: obtaining a radio link failure (RLF) report and a handover success report sent from a terminal, the RLF report carrying a terminal identifier and the handover success report carrying a terminal identifier; Determining the RLF report and the handover success report that are related to each other specifically includes: According to a terminal identifier carried in the RLF report and a terminal identifier carried in a handover success report, determining the RLF report and the handover success report having the same terminal identifier as the RLF report and the handover success report that are related to each other.

[0220] In FIG. 9, the bus architecture may include any number of interconnected buses and bridges, specifically connecting various circuits between one or more processors, such as processor 900, and memory, such as memory 920. The bus architecture may also connect various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be further described herein. The bus interface provides an interface. The transceiver 910 may include multiple elements, i.e., a transmitter and a receiver, and provides a means for communicating with various other devices over transmission media. These transmission media include wireless channels, wired channels, optical cables, and other transmission media. The processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 can store data used by the processor 900 to perform operations.

[0221] The processor 900 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), and the processor may employ a multi-core architecture.

[0222] It should be noted here that the above network node according to the embodiment of the present disclosure can implement all the method steps implemented by the first network node corresponding to the above method embodiment and can also achieve the same technical effects, but the same parts and beneficial effects as those of the method embodiment in this embodiment will not be repeated in detail here.

[0223] An embodiment of the present disclosure further provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements steps of a report processing method applied to the above network node (first network node). The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage devices (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs), etc.), optical storage devices (e.g., optical disks (compact disks (CDs), digital versatile disks (DVDs), Blu-ray (registered trademark) discs (BDs), holographic versatile disks (high-definition versatile discs (HVDs)), etc.), and semiconductor storage devices (e.g., read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), non-volatile memory (NAND FLASH), solid state disks or solid state drives (SSDs)), etc.

[0224] As shown in FIG. 10 , an embodiment of the present disclosure further provides a network node as a second network node, the network node including a processor 1000, a transceiver 1010, a memory 1020, and a program stored in the memory 1020 and operable on the processor 1000, wherein the transceiver 1010 is connected to the processor 1000 and the memory 1020 via a bus interface, and the transceiver 1010 is for transmitting and receiving data under the control of the processor 1000; The processor 1000 reads the program in the memory and obtaining a Radio Link Failure (RLF) report and a handover success report; and (b) performing a procedure of sending the associated RLF report and the handover success report to a first network node, so that a radio link failure cause or a handover failure cause is analyzed by the first network node according to the associated RLF report and the handover success report.

[0225] Optionally, in the network node, the processor 1000 obtaining a handover success report specifically comprises: receiving a handover success report sent from a terminal, the handover success report being generated by the terminal after a successful DAPS handover; Obtaining a Radio Link Failure (RLF) report specifically involves: The method includes receiving an RLF report sent from another network node, the RLF report being generated by the terminal after an RLF occurs after a Dual Active Protocol Stack (DAPS) handover is successful, the other network node being a network node to which the terminal reconnects after an RLF occurs after a DAPS handover is successful.

[0226] Optionally, in the network node, the processor 1000 sending the associated RLF report and the handover success report to the first network node specifically comprises: identifying the RLF report and the handover success report that are related, the RLF report and the handover success report being generated by the same terminal; and transmitting the identified associated RLF report and the handover success report to a first network node.

[0227] In FIG. 10, the bus architecture may include any number of interconnected buses and bridges, specifically connecting various circuits between one or more processors, such as processor 1000, and memory, such as memory 1020. The bus architecture may also connect various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be further described herein. The bus interface provides an interface. The transceiver 1010 may include multiple elements, i.e., a transmitter and a receiver, and provides a means for communicating with various other devices over transmission media. These transmission media include wireless channels, wired channels, optical cables, and other transmission media. The processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 can store data used by the processor 1000 to perform operations.

[0228] The processor 1000 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), and the processor may employ a multi-core architecture.

[0229] It should be noted here that the above network node according to the embodiment of the present disclosure can implement all the method steps implemented by the second network node corresponding to the above method embodiment and can also achieve the same technical effects, but the same parts and beneficial effects as those of the method embodiment in this embodiment will not be repeated in detail here.

[0230] An embodiment of the present disclosure further provides a computer-readable storage medium storing a computer program, which, when executed by a processor, realizes steps of a report processing method applied to the network node (second network node). The processor-readable storage medium may be any available medium or data storage device accessible by a processor, including, but not limited to, magnetic storage devices (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs), etc.), optical storage devices (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage devices (e.g., ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)), etc.

[0231] As shown in FIG. 11 , an embodiment of the present disclosure further provides a terminal including a processor 1100, a transceiver 1110, a memory 1120, and a program stored in the memory 1120 and operable on the processor 1100, wherein the transceiver 1110 is connected to the processor 1100 and the memory 1120 via a bus interface, and the transceiver 1110 is for transmitting and receiving data under the control of the processor 1100, and the processor 1100 reads the program in the memory to: a procedure for generating a Radio Link Failure (RLF) report carrying a terminal identifier and a handover success report carrying a terminal identifier, the handover success report being generated by the terminal device after a Dual Active Protocol Stack (DAPS) handover is successful, and the RLF report being generated by the terminal after an RLF occurs after a DAPS handover is successful; and and transmitting the generated Radio Link Failure (RLF) report and the handover success report to a network device.

[0232] In FIG. 11 , the bus architecture may include any number of interconnected buses and bridges, specifically connecting various circuits between one or more processors, such as processor 1100, and memory, such as memory 1120. The bus architecture may also connect various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be further described herein. The bus interface provides an interface. The transceiver 1110 may include multiple elements, i.e., a transmitter and a receiver, and provides a means for communicating with various other devices over a transmission medium. These transmission media include wireless channels, wired channels, optical cables, and the like. For various user devices, the user interface 1130 may be an interface to which necessary devices, external or internal, can be connected, including, but not limited to, a small keyboard, a display, a speaker, a microphone, a joystick, and the like.

[0233] The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1100 when performing operations.

[0234] Alternatively, the processor 1100 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), and the processor may employ a multi-core architecture.

[0235] An embodiment of the present disclosure further provides a computer-readable storage medium storing a computer program, which, when executed by a processor, realizes steps of the report processing method applied to the terminal. The processor-readable storage medium may be any available medium or data storage device accessible by a processor, including, but not limited to, magnetic storage devices (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage devices (e.g., CDs, DVDs, BDs, HVDs), and semiconductor storage devices (e.g., ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)).

[0236] An embodiment of the present disclosure further provides a report processing device executed by the first network node, and as shown in FIG. 12 , the report processing device 1200 includes: a first report obtaining module 1210 for obtaining a radio link failure (RLF) report and a handover success report; a determining module 1220 for determining the RLF report and the handover success report that are related to each other; and an analysis module 1230 for analyzing a radio link failure cause or a handover failure cause according to the determined associated RLF report and the handover success report.

[0237] Optionally, in the report processing device, the first report obtaining module 1210 obtains a radio link failure (RLF) report and a handover success report: receiving a Radio Link Failure (RLF) report and a handover success report sent from a second network node via a first interface message, the second network node being a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node being a node to which the terminal connected before performing the DAPS handover, the RLF report being obtained by the second network node from another network node, the other network node being a network node to which the terminal reconnected after an RLF occurred after the DAPS handover was successful; The determining module 1220 determines the RLF report and the handover success report that are related to each other, The method includes determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other.

[0238] Optionally, in the report processing device, a determining module 1220 determines a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other: One of the first interface messages includes, if a radio link failure (RLF) report and a handover success report generated by different terminals are carried, determining that the RLF report and the handover success report generated by the same terminal are related to each other.

[0239] Optionally, in the report processing device, the first report obtaining module 1210 obtains a radio link failure (RLF) report and a handover success report: respectively obtaining an RLF report via a second interface message and obtaining a handover success report via a third interface message; The determining module 1220 determines the RLF report and the handover success report that are related to each other, Determine an RLF report corresponding to the first terminal identifier according to a first terminal identifier carried in the second interface message, and determine a handover success report corresponding to the second terminal identifier according to a second terminal identifier carried in the third interface message; If the first terminal identifier and the second terminal identifier are the same, determining the RLF report corresponding to the first terminal identifier and the handover success report corresponding to the second terminal identifier as the RLF report and the handover success report that are related to each other.

[0240] Optionally, in the report processing device, the first interface message, the second interface message and the third interface message are at least one or more of a failure indication message, a handover report message, an access and mobility indication message and a specific message, respectively.

[0241] Optionally, in the report processing device, the first report obtaining module 1210 obtains the radio link failure (RLF) report and the handover success report, specifically: obtaining a radio link failure (RLF) report and a handover success report sent from a terminal, the RLF report carrying a terminal identifier and the handover success report carrying a terminal identifier; The determining module 1220 determines the RLF report and the handover success report that are related to each other, specifically: According to a terminal identifier carried in the RLF report and a terminal identifier carried in a handover success report, determining the RLF report and the handover success report having the same terminal identifier as the RLF report and the handover success report that are related to each other.

[0242] An embodiment of the present disclosure further provides a report processing device executed by a second network node, and as shown in FIG. 13 , the report processing device 1300 includes: a second report obtaining module 1310 for obtaining a radio link failure (RLF) report and a handover success report; and a first sending module 1320 for sending the associated RLF report and the handover success report to a first network node so that a radio link failure cause or a handover failure cause is analyzed by the first network node according to the associated RLF report and the handover success report.

[0243] Optionally, in the report processing device, the second report obtaining module 1310 obtains the handover success report, specifically: receiving a handover success report sent from a terminal, the handover success report being generated by the terminal after a successful DAPS handover; Specifically, the second report acquisition module 1310 acquires the radio link failure (RLF) report by: The method includes receiving an RLF report sent from another network node, the RLF report being generated by the terminal after an RLF occurs after a Dual Active Protocol Stack (DAPS) handover is successful, the other network node being a network node to which the terminal reconnects after an RLF occurs after a DAPS handover is successful.

[0244] Optionally, in the report processing device, the first sending module 1320 sending the associated RLF report and the handover success report to the first network node specifically includes: identifying the RLF report and the handover success report that are related, the RLF report and the handover success report being generated by the same terminal; and transmitting the identified associated RLF report and the handover success report to a first network node.

[0245] The embodiment of the present disclosure further provides a report processing device applied to a terminal, and as shown in FIG. 14, the report processing device 1400 includes: a report generation module 1410 for generating a Radio Link Failure (RLF) report carrying a terminal identifier and a handover success report carrying a terminal identifier, the handover success report being generated by the terminal device after a Dual Active Protocol Stack (DAPS) handover is successful, and the RLF report being generated by the terminal after an RLF occurs after a DAPS handover is successful; and and a second sending module 1420 for sending the generated Radio Link Failure (RLF) report and the handover success report to a network device.

[0246] It should be noted that the division into units in the embodiments of the present disclosure is merely a schematic division based on logical functions, and other division methods may be used in actual implementation. Furthermore, the functional units in the embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The integrated units may be implemented in the form of hardware or software functional units.

[0247] The integrated unit may be implemented in the form of a software functional unit and stored in a processor-readable storage medium when sold or used as an independent product. Based on this understanding, an essential part of the technical aspects of the present disclosure, a part that contributes to the prior art, or all or part of the technical aspects can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions that cause a computer device (which may be a personal computer, a server, a network device, etc.) or a processor to execute all or part of the steps of the methods described in each embodiment of the present disclosure. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0248] It should be noted that the embodiment of the report transmission device is a device that corresponds one-to-one to the embodiment of the above method, and all implementation forms in the embodiment of the above method are applicable to the embodiment of the report transmission device and can also achieve the same technical effects.

[0249] It should be noted that the division into units in the embodiments of the present disclosure is merely a schematic division based on logical functions, and other division methods may be used in actual implementation. Furthermore, the functional units in the embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The integrated units may be implemented in the form of hardware or software functional units.

[0250] The integrated unit may be implemented in the form of a software functional unit and stored in a processor-readable storage medium when sold or used as an independent product. Based on this understanding, an essential part of the technical aspects of the present disclosure, a part that contributes to the prior art, or all or part of the technical aspects can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions that cause a computer device (which may be a personal computer, a server, a network device, etc.) or a processor to execute all or part of the steps of the methods described in each embodiment of the present disclosure. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0251] Those skilled in the art will appreciate that embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product embodied in one or more computer-usable storage media (including, but not limited to, magnetic disk memory, optical memory, etc.) containing computer-usable program code.

[0252] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to form a machine, and the instructions executed by the processor of the computer or other programmable data processing device form an apparatus for implementing the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0253] These processor-executable instructions may be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, with the instructions stored in the processor-readable memory forming an article of manufacture that includes an instruction apparatus that implements the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0254] These processor-executable instructions may be loaded into a computer or other programmable data processing device and cause the computer or other programmable device to perform a series of operational steps to form a computer-implemented process, the instructions executing on the computer or other programmable device providing steps for implementing the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0255] It should be understood that the division of the modules described above is merely a division of logical functions, and that in actual implementation, all or some of the modules may be integrated into a single physical entity or physically separated. These modules may all be implemented by a processing element calling software, or all by hardware. Alternatively, some modules may be implemented by a processing element calling software, while other modules may be implemented by hardware. For example, the determination module may be an independently provided processing element or may be integrated into a chip of the device. Furthermore, the determination module may be stored in the memory of the device in the form of program code and executed by a processing element of the device when called. The implementation of other modules is similar to the determination module. Furthermore, these modules may all or some be integrated or implemented separately. The processing element described herein may be an integrated circuit capable of processing signals. In implementation, each step of the method or each module may be implemented using a hardware integrated logic circuit within a processor element or by using software instructions.

[0256] For example, each module, unit, sub-unit, or sub-module may be configured as one or more integrated circuits that implement the above method, such as one or more application specific integrated circuits (ASICs), one or more microprocessors (digital signal processors (DSPs)), or one or more field programmable gate arrays (FPGAs). As another example, when a certain module is implemented by a processing element calling a program code, the processing element may be a general-purpose processor such as a central processing unit (CPU) or another processor capable of calling a program code. As a further example, these modules may be integrated together or implemented in the form of a system-on-a-chip (SOC).

[0257] In the specification and claims of this disclosure, terms such as "first," "second," and the like are used to distinguish between similar objects and are not necessarily used to describe a particular order or chronology. Such terms are interchangeable under appropriate circumstances, with the understanding that the embodiments of the disclosure described herein may be practiced in orders other than those illustrated or described herein. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a procedure, method, system, product, or apparatus comprising a series of steps or units is not limited to including only those steps or units explicitly listed, but may also include other steps or units not explicitly listed or that are inherent to the procedure, method, product, or apparatus. It should be noted that "and / or" used in the specification and claims indicates at least one of the connected objects, for example, "A and / or B and / or C" includes seven cases: only A is present, only B is present, only C is present, both A and B are present, both B and C are present, both A and C are present, and all of A, B, and C are present. Similarly, "at least one of A and B" used in the specification and claims should be understood as "only A is present, only B is present, or both A and B are present."

[0258] Obviously, those skilled in the art can make various modifications and variations to the present disclosure without departing from the spirit and scope of the present disclosure. If these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and the scope of equivalent techniques, the present disclosure also includes these modifications and variations.

Claims

1. A report processing method applied to a terminal equipment (UE), comprising: the UE performing a DAPS handover from a first network node to a second network node; The UE records a handover success report when a radio link failure (RLF) occurs at the first network node; If the DAPS handover is successful and a radio link failure occurs at the second network node, the UE records a radio link failure (RLF) report; transmitting the generated Radio Link Failure (RLF) report and the handover success report to a network device; The handover success report carries a terminal identifier; The radio link failure (RLF) report carries the terminal identifier.

2. 1. A report processing method performed by a first network node, comprising: Obtaining a radio link failure (RLF) report and a handover success report; determining the RLF report and the handover success report as being related; and analyzing a radio link failure cause or a handover failure cause according to the determined associated RLF report and the handover success report; A report processing method, wherein both the handover success report and the RLF report carry a terminal identifier of a terminal device that has performed a DAPS handover.

3. Obtaining a radio link failure (RLF) report and a handover success report includes: receiving a Radio Link Failure (RLF) report and a handover success report sent from a second network node via a first interface message, the second network node being a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node being a node to which the terminal connected before performing the DAPS handover, the RLF report being obtained by the second network node from another network node, the other network node being a network node to which the terminal reconnected after an RLF occurred after the DAPS handover was successful; Determining the RLF report and the handover success report that are related to each other includes: The report processing method of claim 2 , further comprising determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other.

4. determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other; 4. The report processing method of claim 3, further comprising: if one of the first interface messages carries a radio link failure (RLF) report and a handover success report generated by different terminals, determining the RLF report and the handover success report generated by the same terminal as the RLF report and the handover success report that are related to each other.

5. Obtaining a radio link failure (RLF) report and a handover success report includes: respectively obtaining an RLF report via a second interface message and obtaining a handover success report via a third interface message; Determining the RLF report and the handover success report that are related to each other includes: According to a first terminal identifier carried in the second interface message, determine an RLF report corresponding to the first terminal identifier, and according to a second terminal identifier carried in the third interface message, determine a handover success report corresponding to the second terminal identifier; 3. The report processing method of claim 2, further comprising: if the first terminal identifier and the second terminal identifier are the same, determining the RLF report corresponding to the first terminal identifier and the handover success report corresponding to the second terminal identifier as the RLF report and the handover success report that are related to each other.

6. The report processing method of claim 3 , wherein the first interface message is at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message.

7. A report processing method as described in claim 5, wherein the second interface message and the third interface message are at least one or more of a failure instruction message, a handover report message, an access and mobility instruction message, and a specific message, respectively.

8. Obtaining the Radio Link Failure (RLF) report and the handover success report specifically includes: obtaining a radio link failure (RLF) report and a handover success report sent from a terminal, the RLF report carrying a terminal identifier and the handover success report carrying a terminal identifier; Determining the RLF report and the handover success report that are related to each other specifically includes: The report processing method of claim 2, further comprising: determining an RLF report and a handover success report having the same terminal identifier as the RLF report and the handover success report that are related to each other according to a terminal identifier carried in the RLF report and a terminal identifier carried in a handover success report.

9. A report processing method applied in a second network node, comprising: Obtaining a radio link failure (RLF) report and a handover success report; sending the associated RLF report and the handover success report to a first network node, so that a radio link failure cause or a handover failure cause is analyzed by the first network node according to the associated RLF report and the handover success report; A report processing method, wherein both the handover success report and the RLF report carry a terminal identifier of a terminal device that has performed a DAPS handover.

10. To obtain a successful handover report, specifically: receiving a handover success report sent from a terminal, the handover success report being generated by the terminal after a successful DAPS handover; Obtaining a Radio Link Failure (RLF) report specifically includes:

10. The report processing method of claim 9, comprising receiving an RLF report sent from another network node, the RLF report being generated by the terminal after an RLF occurs after a Dual Active Protocol Stack (DAPS) handover is successful, the other network node being a network node to which the terminal reconnects after an RLF occurs after a DAPS handover is successful.

11. The sending of the associated RLF report and handover success report to the first network node specifically includes: identifying the RLF report and the handover success report that are related, the RLF report and the handover success report being generated by the same terminal; and transmitting the identified associated RLF report and the handover success report to a first network node.

12. A terminal including a memory, a transceiver, and a processor, The memory is for storing a computer program, and the transceiver is for transmitting and receiving data under the control of the processor, and the processor reads the computer program in the memory and performs the following: performing a DAPS handover from the first network node to the second network node; recording a handover success report when a radio link failure (RLF) occurs in the first network node; If the DAPS handover is successful and a radio link failure occurs at the second network node, recording a radio link failure (RLF) report; transmitting the generated Radio Link Failure (RLF) report and the handover success report to a network device; The handover success report carries a terminal identifier; The radio link failure (RLF) report carries the terminal identifier.

13. a first network node, the network node including a memory, a transceiver, and a processor, The memory is for storing a computer program, and the transceiver is for transmitting and receiving data under the control of the processor, and the processor reads the computer program in the memory and performs the following: obtaining a radio link failure (RLF) report and a handover success report; determining the RLF report and the handover success report that are related to each other; and performing an operation of analyzing a radio link failure cause or a handover failure cause according to the determined associated RLF report and the handover success report; A network node, wherein both the handover success report and the RLF report carry a terminal identifier of a terminal device that has performed a DAPS handover.

14. The processor obtaining a radio link failure (RLF) report and a handover success report comprises: receiving a Radio Link Failure (RLF) report and a handover success report sent from a second network node via a first interface message, the second network node being a node to which the terminal connects after performing a Dual Active Protocol Stack (DAPS) handover, the first network node being a node to which the terminal connected before performing the DAPS handover, the RLF report being obtained by the second network node from another network node, the other network node being a network node to which the terminal reconnected after an RLF occurred after the DAPS handover was successful; Determining the RLF report and the handover success report that are related to each other includes: The network node according to claim 13, further comprising determining a radio link failure (RLF) report and a handover success report transmitted in one of the first interface messages as the RLF report and the handover success report that are related to each other.

15. a second network node, the second network node including a memory, a transceiver, and a processor, The memory is for storing a computer program, and the transceiver is for transmitting and receiving data under the control of the processor, and the processor reads the computer program in the memory and performs the following: obtaining a radio link failure (RLF) report and a handover success report; sending the associated RLF report and the handover success report to a first network node, so that a radio link failure cause or a handover failure cause is analyzed by the first network node according to the associated RLF report and the handover success report; A network node, wherein both the handover success report and the RLF report carry a terminal identifier of a terminal device that has performed a DAPS handover.

Images