Report processing method, apparatus, network node, and terminal

Abstract

Embodiments of the present application provide a report processing method, device, network node and terminal. The method comprises: obtaining a radio link failure (RLF) report and a successful handover report; determining the RLF report and the successful handover report having an association relationship; and analyzing a radio link failure cause or a handover failure cause according to the determined RLF report and the successful handover report having the association relationship. With the method, the RLF report and the successful handover report of the same terminal are associated when the network nodes transmit the RLF report and the successful handover report, so that the network node can correctly analyze the handover failure cause, ensure the accuracy of the network node in analyzing the failure type, and perform effective handover parameter optimization.

Description

Technical Field

[0001] This invention relates to the field of wireless technology, and in particular to a report processing method, apparatus, network node, and terminal. Background Technology

[0002] During a Dual Active Protocol Stack (DAPS) handover, a radio link failure may occur on the source side, followed by a successful handover to the target side. In this case, the radio link failure information on the source side will be recorded in the successful handover report and transmitted between network nodes using Access and Mobility Indication (AMI) messages. Alternatively, a random access failure may occur on the target side after the handover, or a radio link failure may occur after successful random access. In this case, the radio link failure information on the target side will be recorded in the Radio Link Failure (RLF) report and transmitted between network nodes using Failure Indication (FIN) messages. Here, the source side refers to the node before the terminal performs the DAPS handover, and the target side refers to the node after the terminal performs the Dual Active Protocol Stack (DAPS) handover.

[0003] As a source network node in a DAPS handover scenario, it can receive successful handover reports and RLF reports through Access and Mobility Indication messages and Failure Indication messages. It can then analyze the successful handover reports and RLF reports. However, research has found that there are inaccurate analysis results in terms of analyzing failure types based on the received successful handover reports and RLF reports. Summary of the Invention

[0004] This invention provides a report processing method, apparatus, network node, and terminal to solve at least one of the technical problems described above.

[0005] One embodiment of the present invention provides a report processing method, wherein the method is executed by a first network node, the method comprising:

[0006] Obtain wireless link failure RLF reports and successful handover reports;

[0007] Identify the related RLF reports and the successful handover reports;

[0008] Based on the identified related RLF reports and successful handover reports, analyze the reasons for wireless link failure or handover failure.

[0009] Optionally, the report processing method, wherein obtaining the radio link failure (RLF) report and the successful handover report includes:

[0010] The terminal receives a Radio Link Failure (RLF) report and a successful handover report from a second network node via a first interface message. The second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) handover, and the first network node is the node before the terminal performs the DAPS handover. The RLF report is obtained by the second network node from other network nodes, which are the network nodes that the terminal reconnected to after a successful DAPS handover and an RLF occurred.

[0011] Determining the correlation between the RLF report and the successful handover report includes:

[0012] The radio link failure RLF report and the successful handover report transmitted in a first interface message are identified as the RLF report and the successful handover report that are related.

[0013] Optionally, the report processing method, wherein determining the radio link failure RLF report and the successful handover report transmitted in a first interface message as having a correlation between the RLF report and the successful handover report, includes:

[0014] If a first interface message carries a radio link failure RLF report and a successful handover report generated by different terminals, then the RLF report and the successful handover report generated by the same terminal are identified as having an association relationship.

[0015] Optionally, the report processing method, wherein obtaining the radio link failure (RLF) report and the successful handover report includes:

[0016] The RLF report is obtained through the second interface message, and the successful handover report is obtained through the third interface message.

[0017] Determining the correlation between the RLF report and the successful handover report includes:

[0018] Based on the first terminal identifier carried in the second interface message, determine the RLF report corresponding to the first terminal identifier, and based on the second terminal identifier carried in the third interface message, determine the successful handover report corresponding to the second terminal identifier.

[0019] If the first terminal identifier is the same as the second terminal identifier, then the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier are determined to be the RLF report and the successful handover report that are related.

[0020] 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 the following: failure indication message, handover report message, access and mobility indication message, and specific message.

[0021] Optionally, the report processing method, wherein obtaining the radio link failure (RLF) report and the successful handover report specifically includes:

[0022] Obtain the Radio Link Failure (RLF) report and the Successful Handover report sent by the terminal, wherein the RLF report carries the terminal identifier and the Successful Handover report carries the terminal identifier;

[0023] Determining the correlation between the RLF report and the successful handover report specifically includes:

[0024] Based on the terminal identifier carried in the RLF report and the terminal identifier carried in the successful handover report, RLF reports and successful handover reports with the same terminal identifier are identified as having an association relationship.

[0025] The present invention also provides another embodiment of the report processing method, wherein the method is applied to a second network node, the method comprising:

[0026] Obtain wireless link failure RLF reports and successful handover reports;

[0027] The associated RLF report and successful handover report are sent to the first network node so that the first network node can analyze the cause of the wireless link failure or the cause of the handover failure based on the associated RLF report and successful handover report.

[0028] Optionally, the report processing method, wherein obtaining a successful switch report specifically includes:

[0029] The receiving terminal sends a successful handover report, which is generated by the terminal after a successful DAPS handover.

[0030] Obtain a Radio Link Failure (RLF) report, specifically including:

[0031] The terminal receives RLF reports sent by other network nodes. The RLF reports are generated after the terminal successfully switched to the dual active protocol stack (DAPS) and then experienced another RLF. The other network nodes are the network nodes that the terminal reconnected to after the terminal successfully switched to DAPS and then experienced another RLF.

[0032] Optionally, the report processing method, wherein sending the associated RLF report and successful handover report to the first network node, specifically includes:

[0033] Identify the related RLF report and the successful handover report, wherein the related RLF report and the successful handover report are generated by the same terminal;

[0034] The identified RLF report and the successful handover report with the relevant relationship are sent to the first network node.

[0035] Another embodiment of the present invention provides a report processing method, which is applied to a terminal device, the method comprising:

[0036] Generate a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated by the terminal device after a successful handover to the Dual Activated Protocol Stack (DAPS). The RLF report is generated by the terminal after a successful handover to DAPS followed by an RLF.

[0037] The generated wireless link failure RLF report and successful handover report are sent to the network device.

[0038] This invention also provides a network node, which is a first network node, comprising a memory, a transceiver, and a processor.

[0039] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0040] Obtain wireless link failure RLF reports and successful handover reports;

[0041] Identify the related RLF reports and the successful handover reports;

[0042] Based on the identified related RLF reports and successful handover reports, analyze the reasons for wireless link failure or handover failure.

[0043] Optionally, in the network node, the processor acquires radio link failure (RLF) reports and successful handover reports, including:

[0044] The terminal receives a Radio Link Failure (RLF) report and a successful handover report from a second network node via a first interface message. The second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) handover, and the first network node is the node before the terminal performs the DAPS handover. The RLF report is obtained by the second network node from other network nodes, which are the network nodes that the terminal reconnected to after a successful DAPS handover and an RLF occurred.

[0045] Determining the correlation between the RLF report and the successful handover report includes:

[0046] The radio link failure RLF report and the successful handover report transmitted in a first interface message are identified as the RLF report and the successful handover report that are related.

[0047] Optionally, in the network node, the processor determines the radio link failure (RLF) report and the successful handover report transmitted in a first interface message as having a correlation, including:

[0048] If a first interface message carries a radio link failure RLF report and a successful handover report generated by different terminals, then the RLF report and the successful handover report generated by the same terminal are identified as having an association relationship.

[0049] Optionally, in the network node, the processor acquires radio link failure (RLF) reports and successful handover reports, including:

[0050] The RLF report is obtained through the second interface message, and the successful handover report is obtained through the third interface message.

[0051] Determining the correlation between the RLF report and the successful handover report includes:

[0052] Based on the first terminal identifier carried in the second interface message, determine the RLF report corresponding to the first terminal identifier, and based on the second terminal identifier carried in the third interface message, determine the successful handover report corresponding to the second terminal identifier.

[0053] If the first terminal identifier is the same as the second terminal identifier, then the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier are determined to be the RLF report and the successful handover report that are related.

[0054] 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 the following: failure indication message, handover report message, access and mobility indication message, and specific message.

[0055] Optionally, in the network node, the processor acquiring radio link failure (RLF) reports and successful handover reports specifically includes:

[0056] Obtain the Radio Link Failure (RLF) report and Successful Handover report sent by the terminal, wherein the RLF report carries the terminal identifier and the Successful Handover report carries the terminal identifier;

[0057] Determining the correlation between the RLF report and the successful handover report specifically includes:

[0058] Based on the terminal identifier carried in the RLF report and the terminal identifier carried in the successful handover report, RLF reports and successful handover reports with the same terminal identifier are identified as having an association relationship.

[0059] This invention also provides a network node, which is a second network node, comprising a memory, a transceiver, and a processor.

[0060] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0061] Obtain wireless link failure RLF reports and successful handover reports;

[0062] The associated RLF report and successful handover report are sent to the first network node so that the first network node can analyze the cause of the wireless link failure or the cause of the handover failure based on the associated RLF report and successful handover report.

[0063] Optionally, in the network node, the processor obtaining a successful handover report specifically includes:

[0064] The receiving terminal sends a successful handover report, which is generated by the terminal after a successful DAPS handover.

[0065] The processor acquires the Radio Link Failure (RLF) report, specifically including:

[0066] The terminal receives RLF reports sent by other network nodes. The RLF reports are generated after the terminal successfully switched to the dual active protocol stack (DAPS) and then experienced another RLF. The other network nodes are the network nodes that the terminal reconnected to after the terminal successfully switched to DAPS and then experienced another RLF.

[0067] Optionally, the network node, wherein the processor sends the associated RLF report and successful handover report to the first network node, specifically includes:

[0068] Identify the related RLF report and the successful handover report, wherein the related RLF report and the successful handover report are generated by the same terminal;

[0069] The identified RLF report and the successful handover report with the relevant relationship are sent to the first network node.

[0070] This invention also provides a terminal, which includes a memory, a transceiver, and a processor:

[0071] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0072] Generate a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated by the terminal device after a successful handover to the Dual Activated Protocol Stack (DAPS). The RLF report is generated by the terminal after a successful handover to DAPS followed by an RLF.

[0073] The generated wireless link failure RLF report and successful handover report are sent to the network device.

[0074] This invention also provides a report processing apparatus, which is applied to a first network node for execution. The apparatus includes:

[0075] The first report acquisition module is used to acquire wireless link failure (RLF) reports and successful handover reports.

[0076] The determination module is used to determine the RLF report and the successful handover report that have a relationship;

[0077] The analysis module is used to analyze the reasons for wireless link failure or handover failure based on the determined correlation between the RLF report and the successful handover report.

[0078] This invention also provides a report processing apparatus, which is applied to a second network node for execution. The apparatus includes:

[0079] The second report acquisition module is used to acquire wireless link failure (RLF) reports and successful handover reports.

[0080] The first sending module is used to send the associated RLF report and successful handover report to the first network node, so that the first network node can analyze the cause of wireless link failure or handover failure based on the associated RLF report and successful handover report.

[0081] This invention also provides a report processing device, which is applied to a terminal, and the device includes:

[0082] The report generation module is used to generate a radio link failure (RLF) report and a successful handover report. The RLF report carries the terminal identifier and the successful handover report carries the terminal identifier. The successful handover report is generated by the terminal device after a successful handover of the dual active protocol stack (DAPS). The RLF report is generated after an RLF occurs after a successful handover of DAPS.

[0083] The second sending module is used to send the generated wireless link failure (RLF) report and successful handover report to the network device.

[0084] This invention also provides a processor-readable storage medium storing a computer program for causing the processor to execute the report processing method described above.

[0085] This invention also provides a computer-readable storage medium storing a computer program for causing the computer to perform the report processing method described above.

[0086] This invention also provides a communication device, wherein the communication device stores a computer program, the computer program being used to cause the communication device to perform the reporting processing method as described above.

[0087] The beneficial effects of this invention are:

[0088] By employing the report processing method described in this embodiment of the invention, when network nodes transmit Radio Link Failure (RLF) reports and successful handover reports, the RLF reports and successful handover reports belonging to the same terminal are associated, so that network nodes can correctly analyze the reasons for handover failure, ensure the accuracy of the network nodes' failure type analysis, and effectively optimize handover parameters. Attached Figure Description

[0089] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0090] Figure 1 A schematic diagram illustrating a switching process applicable to the method described in the embodiments of this application;

[0091] Figure 2 A schematic diagram illustrating another switching process applicable to the method described in the embodiments of this application;

[0092] Figure 3 This diagram illustrates the message transmission process for the handover report.

[0093] Figure 4 This is a flowchart illustrating the report processing method described in Embodiment 1 of the present invention;

[0094] Figure 5 This indicates one of the implementation processes of the method described in the embodiments of the present invention;

[0095] Figure 6 This indicates the second implementation process of the method described in the embodiments of the present invention;

[0096] Figure 7 This is a flowchart illustrating the report processing method described in Embodiment 2 of the present invention;

[0097] Figure 8 This is a flowchart illustrating the report processing method described in Embodiment 3 of the present invention;

[0098] Figure 9 This is a schematic diagram showing the structure of a network node according to one embodiment of the present invention;

[0099] Figure 10 This is a schematic diagram illustrating the structure of a network node according to another embodiment of the present invention;

[0100] Figure 11 This is a schematic diagram of the structure of the terminal described in an embodiment of the present invention;

[0101] Figure 12 This is a schematic diagram of the report processing device according to Embodiment 1 of the present invention;

[0102] Figure 13 This is a schematic diagram of the report processing device described in Embodiment 2 of the present invention;

[0103] Figure 14This is a schematic diagram of the report processing device described in Embodiment 3 of the present invention. Detailed Implementation

[0104] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0105] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the application described herein may be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0106] In this application's embodiments, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. In this application's embodiments, the term "multiple" refers to two or more, and other quantifiers are similar.

[0107] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0108] The report processing method, apparatus, network node, and terminal provided in this application embodiment can be applied to wireless communication systems. This wireless communication system can be a system employing fifth-generation (5G) mobile communication technology (hereinafter referred to as a 5G system). Those skilled in the art will understand that the 5G NR system is merely an example and not intended to be limiting.

[0109] To clearly illustrate the technical solution of the report processing method described in the embodiments of this application, the switching process applied in the report processing method described in this application will be explained first below.

[0110] The report processing method described in this application can be applied to both traditional switchover processes and DAPS switchover processes.

[0111] like Figure 1 The diagram shown illustrates the traditional handover process, which includes:

[0112] Step 1: Network node 1 and network node 2 transmit a handover request and a handover response, enabling the terminal UE to hand over from network node 1 (source network node) to network node 2 (target network node);

[0113] Step 2: Network node 1 sends a synchronization reconfiguration message to the UE, causing the UE to immediately perform a handover, disconnect from network node 1, and randomly connect to network node 2.

[0114] Step 3: Random access between the UE and network node 2 is completed, and a handover completion message is sent to network node 2;

[0115] Step 4: Network Node 2 sends a context release message to Network Node 1, notifying Network Node 1 to release the UE context.

[0116] like Figure 2 The diagram shown illustrates the DAPS handover process, which includes:

[0117] Step 1: While maintaining the data transmission link between the source network node and the UE, the source network node sends a handover request to the target network node.

[0118] Step 2: The target network node sends a request confirmation message to the source network node;

[0119] Step 3: The source network node sends a handover instruction to the UE;

[0120] Step 4: The UE performs an access procedure to the target network node;

[0121] Step 5: After completing the RRC reconfiguration, the UE sends an RRC connection reconfiguration complete message to the target network node;

[0122] Through steps 1 to 5 above, the original data transmission link between the source network node and the UE is maintained. When the target network node receives the handover indication from the source network node and also receives the RRC connection reconfiguration completion message from the UE, if there are pending downlink packet data convergence protocol (PDCP) data packets (data processed with new security context encryption or integrity protection) or control frames in the buffer, they will be sent to the UE through the configured link between the target network node and the UE.

[0123] In steps 6 and 7, the UE simultaneously maintains data transmission and reception with both the source network node and the target network node;

[0124] Step 8: The target network entity sends a release instruction to the UE, notifying the UE to complete the data transmission and expecting the UE to release the data connection between the source network node and the UE;

[0125] Step 9: The UE stops uplink transmission and downlink reception between the source network node and the UE, and begins to release the entire source-side MCG configuration.

[0126] Step 10: The UE maintains data transmission and reception only with the target network node.

[0127] The above-described report processing method using the embodiments of the present invention Figure 1 and Figure 2 The handover process in the illustrated implementation refers to a User Equipment (UE), such as a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), or wearable device. It should be noted that the specific type of user terminal 11 is not limited in this embodiment.

[0128] Network nodes (including source network nodes, target network nodes, etc.) can be base stations, such as 5G and later versions of base stations (e.g., gNB, 5G NR NB, ng-eNB, etc.), or base stations in other communication systems, or referred to as node B. It should be noted that in this application embodiment, only 5G base stations are used as examples, but the specific type of network node is not limited.

[0129] In addition, in the above Figure 1 and Figure 2The handover process in the illustrated implementation involves the terminal side recording an RLF report and a successful handover report.

[0130] In the event of a handover failure or RLF (Radio Link Failure), the terminal will record an RLF report. RLF reports are used to record at least two scenarios: handover failure and radio link failure, with each RLF report representing only one scenario.

[0131] Optionally, an RLF report may include at least one of the following:

[0132] Measurement results of the last serving cell on the terminal;

[0133] After the terminal confirms a handover failure or wireless link failure, the neighboring cell measurement results are displayed.

[0134] Terminal location information;

[0135] Terminal failure cell identification information, such as Cell Global Identity (CGI) / Physical Cell Identity (PCI) frequency;

[0136] The terminal reconstructs the cell identification information;

[0137] UE reporting timer: The time elapsed from the last time the terminal acknowledged receiving the handover initiation message to the connection failure;

[0138] The connection failed due to either a failed handover or a failed wireless link.

[0139] C-RNTI used when terminal connection fails;

[0140] The reasons for wireless link failure include T310 timeout, random access issues, RLC layer reaching maximum retransmission, or beam recovery failure (BFRF).

[0141] The time elapsed from when the terminal confirms the connection failure to when the terminal reports the RLF report;

[0142] Tracking Area Code (TAC) of a cell that failed to connect;

[0143] Bluetooth (BT) related record results;

[0144] Wireless Local Area Network (WLAN).

[0145] Optionally, the recording scenarios for successfully switching reports include:

[0146] During traditional handover, the terminal records a successful handover report when the length value of the terminal's T310 timer, T312 timer, or T304 timer exceeds a predetermined threshold.

[0147] During DAPS handover, if the length value of timer T310, timer T312 or timer T304 exceeds the predetermined threshold or if an RLF occurs on the original link, the terminal records a successful handover report.

[0148] The successful switch report records the measurement information at the trigger time, cell identification information, terminal location information, and timer value, etc.

[0149] After recording the RLF report and / or successful handover report, the UE sends the RLF report and / or successful handover report to the network node via an RRC connection establishment completion message, RRC connection reconfiguration completion message, RRC connection re-establishment completion message, or RRC recovery completion message. Alternatively, the network node sends a request message to the UE, and the UE sends the RLF report and / or successful handover report to the network node via a response message.

[0150] In addition, to address failures during terminal mobility, Mobility Robustness Optimisation (MRO) can be used to assist in network optimization.

[0151] In the event of a handover failure or an RLF (Recurrent Leak) error, the terminal records an RLF report. After a handover failure, the terminal performs cell selection and then re-establishes or re-accesses the network via RRC (Recurrent Connection Re-establishment) or RRC connection re-establishment, notifying the network that the RLF report has been retained on the terminal side. The network side retrieves this RLF report from the terminal when needed for network optimization.

[0152] MRO (Mobility Recovery Overhaul) features are primarily used to identify and resolve parameter configuration issues during mobility operations, and define three failure types: premature handover, delayed handover, and handover to the wrong cell. Among these:

[0153] Handover Too Late: After the terminal has been stably camped in the source cell for a period of time, a radio link failure occurs, and the terminal attempts to access a different cell by re-establishing the connection via RRC.

[0154] Premature handover: During the handover process, the terminal fails to access the target cell, or successfully accesses the target cell but soon experiences a radio link failure, and the terminal initiates RRC connection re-establishment to attempt to access the source cell;

[0155] Switching to the wrong cell: During the handover process, the terminal fails to access the target cell, or successfully accesses the target cell but soon experiences a radio link failure. The terminal initiates an RRC connection re-establishment to attempt to access a cell that is different from the target cell and the source cell.

[0156] After the handover is complete, whether the terminal can stably camp on the target cell is crucial for determining the above-mentioned failure type. If it camps stably, subsequent failures are unrelated to the previous handover, because the UE can stably camp on the target cell after the handover. If it does not camp stably, it may be due to the previous handover, such as an inappropriate target cell selection.

[0157] The stability of the terminal's camp is determined using the UE reporting timer in the RLF report. A small value indicates no stable camping, while a large value indicates stable camping after handover. A value of 0 indicates no handover occurred.

[0158] Because the source cell connection remains continuous during DAPS handover, the failure scenarios are more complex. The scenarios involving DAPS handover that are too late, too early, or handover to the wrong cell are as follows:

[0159] DAPS switchover too late:

[0160] After the terminal has been stably camped in the source cell for a period of time, a radio link failure occurs. The terminal attempts to access a different cell by re-establishing the connection via RRC.

[0161] After the terminal has been stably camped in the source cell for a period of time, the DASP handover is successful and it can stably camp in the target cell. However, a radio link failure occurred in the source cell during the DAPS handover process.

[0162] DAPS switchover too early:

[0163] The DAPS handover to the target cell was successful, but a radio link failure occurred shortly afterward, and the terminal initiated an RRC connection re-establishment attempt to access the source cell.

[0164] During DAPS handover, the terminal failed to access the target cell, successfully returned to the source cell, and no RLF occurred for a period of time.

[0165] DAPS switched to the wrong cell:

[0166] During DAPS handover, the source cell connection first experiences an RLF (Relational Link Failure), then the terminal fails to access the target cell, and the terminal initiates an RRC (Relational Link Re-establishment) to attempt to access a cell different from both the target and source cells.

[0167] During DAPS handover, the terminal successfully accessed the target cell but soon experienced a radio link failure. The terminal initiated an RRC connection re-establishment attempt to access a cell different from both the target and source cells.

[0168] If a radio link failure occurs in the source cell during DAPS handover, it will be recorded in the successful handover report. Subsequently, if the target side access fails or the target side random access is successful but an RLF occurs shortly afterward, it will be recorded in the RLF report.

[0169] Based on the aforementioned MRO characteristics, the message flow between network nodes includes failure indication messages, handover report messages, and access and mobility indication messages.

[0170] Specifically, for the failure indication message:

[0171] After a UE fails to handover or experiences an RLF failure, it may reconnect to the network. When a network node receives the UE's RLF report, if the current network node is not the one that experienced the failure, it needs to forward the RLF report and other relevant information between network nodes to the failed network node so that the failed network node can analyze and optimize the data.

[0172] Optionally, the failure indication message is triggered by an RRC re-establishment request or an RRC establishment request over the air interface. For an RRC re-establishment request, it may optionally include information carried in the RRC re-establishment request and the UE RLF report; for an RRC establishment request, it may include the UE RLF report.

[0173] Regarding the handover report message:

[0174] After generating a failure indication message for a failed network node analysis, it may be necessary to send a handover report message. Optionally, the sending process is as follows: Figure 3 As shown, it includes:

[0175] Step 1: The UE successfully switched from network node 1 to network node 2.

[0176] Step 2, Network Node 2 experiences a Radio Link Failure (RLF);

[0177] Step 3, UE records RLF report;

[0178] Step 4: The UE successfully accesses network node 3;

[0179] Step 5: Network node 3 obtains the UE's RLF report;

[0180] Step 6: After the UE successfully switches 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.

[0181] Step 7: After analyzing the failure indication message, network node 2 finds that the RLF failure is due to the unreasonable target cell selected by network node 1 for handover. The handover failure type is handover to the wrong cell, and network node 3 should be selected. Therefore, a handover report message is sent to network node 1 to notify network node 1.

[0182] Optionally, the handover report message includes the following information:

[0183] The report type indicates the results of the analysis of the failed node, including premature handover, handover to the wrong cell, etc.

[0184] Switching source cell, including global cell identifier ID;

[0185] Switch to the target cell, including the global cell identifier ID;

[0186] RRC cell re-establishment includes the global cell identifier ID. When the report type is handover to the wrong cell, it includes the indication information of the RRC cell re-establishment, notifying the source cell that it should select this cell as the target cell for handover.

[0187] UE RLF report, optional. If the received failure indication message includes a UE RLF report, then the UE RLF report should also be included when transmitting the handover report message.

[0188] The Access and Mobility Indication (AMI) message is used to transmit information such as successful handover reports between network nodes.

[0189] Based on the above, during DAPS handover, a radio link failure may occur on the source side, and a random access failure or a successful random access followed by a radio link failure may also occur on the target side. Failure information on the source side is recorded in the successful handover report and transmitted between network nodes using Access and Mobility Indication (RMI) messages; failure information on the target side is recorded in the RLF report and transmitted between network nodes using Failure Indication (FIN) messages. The network node on the source side may have already released the UE's context information after the handover is complete. Therefore, when receiving the successful handover report and RLF report via Access and Mobility Indication (RMI) and Failure Indication (FIN) messages, it is unclear whether these reports correspond to the same UE. If the successful handover report corresponds to UE1 and the RLF report corresponds to UE2, UE1 may be recorded as a DAPS handover too late error, and UE2 may be recorded as a handover too early error. If the successful handover report and the RLF report belong to the same UE, that UE may be recorded as having a handover to the wrong cell error.

[0190] The above analysis shows that when performing DAPS handover error analysis on the source side, it is necessary to determine whether the successful handover report and the RLF report belong to the same user. Otherwise, analyzing the successful handover report and the RLF report separately will lead to inaccurate analysis results.

[0191] To address the aforementioned issues, this invention provides a report processing method. This method associates RLF reports and successful handover reports sent between network nodes that belong to the same terminal when transmitting RLF reports and successful handover reports. This allows network nodes to correctly analyze the reasons for handover failures, ensuring the accuracy of failure type analysis and enabling effective optimization of handover parameters.

[0192] The report processing method described in one embodiment of the present invention, such as Figure 4 As shown, the method, executed by the first network node, includes:

[0193] S410, acquire wireless link failure RLF report and successful handover report;

[0194] S420, determine the related RLF report and the successful handover report;

[0195] S430, based on the determined related RLF report and the successful handover report, analyze the cause of wireless link failure or handover failure.

[0196] In this embodiment of the invention, optionally, the second network node can be, but is not limited to, the target network node after the target terminal is switched, and the first network node can be, but is not limited to, the source network node before the target terminal is switched.

[0197] In the report processing method described in this embodiment of the invention, when the second network node sends a Radio Link Failure (RLF) report and a successful handover report to the first network node, it associates the RLF report with the terminal. That is, it can indicate that the RLF report and the successful handover report are associated with the same terminal, so that the first network node can perform failure type analysis based on the associated RLF report and successful handover report, ensuring the accuracy of the failure type analysis by the network node, avoiding the analysis of incorrect types, and enabling effective optimization of handover parameters.

[0198] In one implementation, step S410 involves acquiring a radio link failure (RLF) report and a successful handover report, including:

[0199] The terminal receives a Radio Link Failure (RLF) report and a successful handover report from a second network node via a first interface message. The second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) handover, and the first network node is the node before the terminal performs the DAPS handover. The RLF report is obtained by the second network node from other network nodes, which are the network nodes that the terminal reconnected to after a successful DAPS handover and an RLF occurred.

[0200] In step S420, determining the related RLF report and the successful handover report includes:

[0201] The radio link failure RLF report and the successful handover report transmitted in a first interface message are identified as the RLF report and the successful handover report that are related.

[0202] Optionally, determining the radio link failure (RLF) report and the successful handover report transmitted in a first interface message as related RLF reports and successful handover reports includes:

[0203] If a first interface message carries a radio link failure RLF report and a successful handover report generated by different terminals, then the RLF report and the successful handover report generated by the same terminal are identified as having an association relationship.

[0204] In this implementation, the second network node sends an RLF report and a successful handover report to the first network node through the same interface message (first interface message), and the simultaneously sent radio link failure RLF report and successful handover report can be associated with the target terminal.

[0205] In this embodiment, optionally, the radio link failure (RLF) report and successful handover report of the associated target terminal sent by the second network node can be received through at least one of the XN interface, X2 interface, NG interface and S1 interface.

[0206] Optionally, the radio link failure (RLF) report and successful handover report of the associated target terminal sent by the second network node can be received through at least one of the following: failure indication message, handover report message, access and mobility indication message, and specific message.

[0207] Among them, the specific message is a pre-set message specifically used to indicate the sending of radio link failure (RLF) reports and successful handover reports.

[0208] Optionally, when receiving a Radio Link Failure (RLF) report and a successful handover report sent by a second network node through a first interface message, the first interface message may include a report list, which includes RLF reports and successful handover reports generated by different terminals, and the target terminal is one of the different terminals.

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

[0210] Furthermore, since successful handover reports and RLF reports are not real-time reports, the second network node can cache successful handover reports and RLF reports generated by multiple UEs, and then send the successful handover reports and RLF reports associated with the same terminal simultaneously in a single interface message. When the first interface message contains reports from multiple UEs, the reports from multiple UEs can be transmitted in the form of a report list, where each node in the list represents a report from one UE, and each UE's report contains associated successful handover reports and RLF reports.

[0211] In another embodiment of the method described in this invention, step S410, acquiring a radio link failure (RLF) report and a successful handover report, includes:

[0212] The RLF report is obtained through the second interface message, and the successful handover report is obtained through the third interface message.

[0213] In step S420, the related RLF report and the successful handover report are determined, including:

[0214] Based on the first terminal identifier carried in the second interface message, determine the RLF report corresponding to the first terminal identifier, and based on the second terminal identifier carried in the third interface message, determine the successful handover report corresponding to the second terminal identifier.

[0215] If the first terminal identifier is the same as the second terminal identifier, then the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier are determined to be the RLF report and the successful handover report that are related.

[0216] Using this implementation, the second network node can send a Radio Link Failure (RLF) report and a successful handover report to the first network node through different interface messages. The interface messages that send the RLF report and the successful handover report include the terminal's identifier. In this way, based on the terminal identifier included in the interface message, the RLF report and the successful handover report generated by the same terminal and transmitted through different interface messages can be associated.

[0217] Optionally, when obtaining an RLF report through a second interface message, the second interface message includes a first report list, which includes RLF reports from at least one terminal.

[0218] When a successful handover report is obtained through a third interface message, the third interface message includes a second report list, which includes a successful handover report for at least one terminal.

[0219] In this implementation, the interface message may include a report list for sending a successful handover report or RLF report of at least one terminal, and each successful handover report or RLF report in the interface message has a corresponding terminal identifier to indicate the terminal associated with each successful handover report or each RLF report.

[0220] Alternatively, in this embodiment, when obtaining an RLF report via a second interface message or a successful handover report via a third interface message, the second interface message and the third interface message are at least one or more of the following: a failure indication message, a handover report message, an access and mobility indication message, and a specific message. Optionally, the sending interfaces for the second interface message and the third interface message are at least one of the following: an XN interface, an X2 interface, an NG interface, and an S1 interface.

[0221] In another embodiment of the method described in this invention, step S410, acquiring the Radio Link Failure (RLF) report and the successful handover report, specifically includes:

[0222] Obtain the Radio Link Failure (RLF) report and Successful Handover report sent by the terminal, wherein the RLF report carries the terminal identifier and the Successful Handover report carries the terminal identifier;

[0223] In step S420, the related RLF report and the successful handover report are determined, specifically including:

[0224] Based on the terminal identifier carried in the RLF report and the terminal identifier carried in the successful handover report, RLF reports and successful handover reports with the same terminal identifier are identified as having an association relationship.

[0225] Using this implementation, the terminal adds a terminal identifier record when recording successful handover reports and RLF reports, so there is no need to add the terminal identifier in the interface message when sending successful handover reports or RLF reports.

[0226] In this way, after receiving the successful handover report and the RLF report, the source network node (first network node) associates the terminal identifiers in the successful handover report and the RLF report to determine the associated successful handover report and RLF report, and performs handover failure type analysis.

[0227] The following provides examples illustrating the implementation process of the report transmission method described in the embodiments of the present invention when using the above-mentioned methods.

[0228] Since there are many scenarios of DAPS failure, the transmission of radio link failure RLF reports or successful handover reports may occur in various different implementation scenarios. In order to clearly explain the implementation process of the report transmission method described in the embodiments of the present invention, the following will take the most typical failure scenario in DAPS as an example: a radio link failure occurs at the source network node during DAPS handover, the DAPS handover target network node is successfully accessed randomly, but an RLF occurs soon afterward, and the terminal restores the connection at another network node. Taking this scenario as an example, the specific implementation of steps S410 to S430 of the present invention, which involves obtaining radio link failure RLF reports and successful handover reports, and determining the specific implementation of the RLF reports and successful handover reports that have a correlation, will be described in detail.

[0229] It should be noted that the report transmission method described in the embodiments of the present invention is not limited to being applied only to the DAPS handover process, but can also be applied to the traditional handover process, and is not limited to being applied only to the failure scenarios illustrated below.

[0230] Implementation Method 1

[0231] In Implementation Method 1, Method 1 is adopted, where the wireless link failure RLF report and the successful handover report sent by the second network node are received through the first interface message, and the wireless link failure RLF report is associated with the successful handover report.

[0232] In this implementation method, when the second network node sends a Radio Link Failure (RLF) report and a successful handover report via the first interface message, it further includes:

[0233] The second network node obtains a successful handover report sent after the target terminal successfully switches from the first network node to the second network node;

[0234] After the second network node obtains the target terminal's RLF report after it connects to the third network node, the third network node sends the target terminal's RLF report via a failure indication message.

[0235] The second network node sends an RLF report and a successful handover report of the associated target terminal to the first network node via the first interface message, including:

[0236] The successful handover report and the RLF report are associated, and the target terminal's RLF report and successful handover report are sent to the first network node through the first interface message.

[0237] In this embodiment, after the second network node obtains the successful handover report and the RLF report respectively, it associates the successful handover report and the RLF report with the first network node and sends the target terminal's RLF report and successful handover report to the first network node through the same interface message.

[0238] See Figure 5 As shown, the specific implementation process of this embodiment includes the following steps:

[0239] S510, the UE performs a DAPS handover, switching from the first network node (source network node) to the second network node (target network node);

[0240] S520, the first network node (source network node) experienced a radio link failure, and the UE recorded a successful handover report;

[0241] S530, DAPS switchover successful;

[0242] S540, the second network node (target network node) initiates a UE information acquisition process to obtain a successful handover report recorded by the UE; optionally, it may send an information request to the UE to request the successful handover report.

[0243] S550, a radio link failure occurred at the second network node (target network node), and the UE recorded an RLF report;

[0244] S560, the UE reconnects to another network node (the third network node), and the third network node obtains the RLF report recorded by the UE;

[0245] S570, the third network node sends the RLF report to the second network node (target network node) via a failure indication message;

[0246] S580, the second network node (target network node) identifies the received RLF report and, based on the previously acquired successful handover report, identifies the RLF report and successful handover report belonging to the same terminal, and sends the identified RLF report and successful handover report belonging to the same terminal to the first network node (source network node) through the same interface message (first interface message) to indicate that the sent RLF report and successful handover report belong to the same terminal.

[0247] Optionally, the second network node can identify whether the received RLF report and successful handover report belong to the same terminal based on at least one of the location information, terminal identifier, and cell identifier in the RLF report and successful handover report.

[0248] On the other hand, optionally, when sending the RLF report and successful handover report of the associated target terminal to the second network node through the first interface message, the first interface message includes a report list, which includes the RLF report and successful handover report associated with at least one terminal respectively, and the target terminal is one of the at least one terminal.

[0249] Specifically, the report list includes at least one report node, and each report node records the RLF report and successful handover report corresponding to the same terminal. The RLF report and successful handover report of the target terminal are recorded in one of the report nodes.

[0250] Furthermore, since successful handover reports and RLF reports are not real-time reports, the base station can cache successful handover reports and RLF reports from multiple users, and then send the successful handover reports and RLF reports associated with the same terminal simultaneously in a single interface message. When a message contains reports from multiple UEs, the reports from multiple UEs can be transmitted in the form of a report list, where each node in the list represents a report from one UE, and each UE's report contains the associated successful handover report and RLF report.

[0251] In this embodiment of the invention, optionally, when sending an RLF report and a successful handover report through the same interface message (first interface message), the sending interface of the first interface message is at least one of the XN interface, X2 interface, NG interface and S1 interface.

[0252] Optionally, the first interface message can be an XN or X2 interface. When there is no XN or X2 connection between network-side nodes, it can also be sent through an NG or S1 interface.

[0253] In another implementation, optionally, when sending an RLF report and a successful handover report through the same interface message (first interface message), the first interface message may be transmitted through at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message.

[0254] Implementation Method 2

[0255] In the second implementation method, the first network node obtains the RLF report through the second interface message and obtains the successful handover report through the third interface message.

[0256] The second interface message and the third interface message each include the identifier of the target terminal.

[0257] In this implementation, the second network node sends an RLF report to the first network node via a second interface message, and sends a successful handover report to the first network node via a third interface message, including:

[0258] If the second network node receives a successful handover report sent after the target terminal successfully switches from the first network node to the second network node, then the second network node sends a successful handover report to the first network node through the third interface message.

[0259] If the second network node obtains the target terminal's RLF report sent by the third network node via a failure indication message after the target terminal reconnects to the third network node, then the third network node sends the RLF report to the first network node via the second interface message.

[0260] In this implementation, the successful handover report and the RLF report are sent to the first network node through different interface messages. After receiving the successful handover report, it can be sent to the source network node immediately without waiting for the subsequent RLF report. The interface message for sending the successful handover report and the interface message for sending the RLF report are associated with the included terminal identifier.

[0261] See Figure 6 As shown, the specific implementation process of this embodiment includes the following steps:

[0262] S610, the UE performs a DAPS handover, switching from the first network node (source network node) to the second network node (target network node);

[0263] S620, the first network node (source network node) experienced a radio link failure, and the UE recorded a successful handover report;

[0264] S630, DAPS switch successful;

[0265] S640, the second network node (target network node) initiates a UE information acquisition process to obtain a successful handover report recorded by the UE; optionally, it may send an information request to the UE to request the successful handover report.

[0266] S650, after the second network node (target network node) receives the successful handover report, it immediately sends the successful handover report to the first network node (source network node) through an interface message (third interface message);

[0267] S660, a radio link failure occurred at the second network node (target network node), and the UE recorded an RLF report;

[0268] S670, the UE reconnects to another network node (the third network node), and the third network node obtains the RLF report recorded by the UE;

[0269] S680, the third network node sends an RLF report to the second network node (target network node) via a failure indication message;

[0270] S690, the second network node (target network node) sends the RLF report to the first network node (source network node) through an interface message (such as the second interface message).

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

[0272] Since the user's context information may have been deleted by the source network node after the terminal switches from the source network node to the target network node, the user's context information can no longer be obtained based on the UE identifier. However, based on the UE identifier included in the interface message, the second interface message that sends the RLF report and the third interface message that sends the successful handover report can be associated to determine that the successful handover report and the RLF report correspond to the same terminal.

[0273] Optionally, when sending an RLF report to the first network node via a second interface message, the second interface message includes a first report list, which includes RLF reports from at least one terminal.

[0274] When a successful handover report is sent to the first network node via a third interface message, the third interface message includes a second report list, which includes a successful handover report of at least one terminal.

[0275] The target terminal is one of at least one terminal.

[0276] In this implementation, the interface message may include a report list for sending a successful handover report or RLF report of at least one terminal, and each successful handover report or RLF report in the interface message has a corresponding terminal identifier to indicate the terminal associated with each successful handover report or each RLF report.

[0277] In this embodiment of the invention, optionally, when the second network node sends an RLF report to the first network node through a second interface message and sends a successful handover report to the first network node through a third interface message, the second interface message and the third interface message can be transmitted through at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message.

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

[0279] Optionally, the second interface message and the third interface message can be sent via the XN interface or the X2 interface, respectively. When there is no XN interface or X2 connection between network-side nodes, they can also be sent via the NG interface or the S1 interface.

[0280] Comparing Method 1 and Method 2, both methods require the target network node to identify that the successful handover report and the RLF report belong to the same terminal. Specifically, with Method 2, compared to Method 1, the target network node can immediately send the successful handover report to the source network node after receiving it, without waiting for subsequent RLF reports. Optionally, based on this implementation, the source network node, after receiving the successful handover report, is not required to immediately perform handover analysis and optimization; it needs to wait to confirm whether there will be any further RLF reports.

[0281] Implementation Method 3

[0282] In Implementation Method 3, the second network node sends an RLF report to the first network node via a second interface message and a successful handover report to the first network node via a third interface message. The RLF report and the successful handover report each include the identifier of the target terminal.

[0283] Optionally, the switching process in this implementation can be the same as in implementation two. The following will continue with... Figure 6 The implementation process shown illustrates the specific implementation method of Method 3:

[0284] See Figure 6 As shown, the specific implementation process of this third embodiment includes the following steps:

[0285] S610, the UE performs a DAPS handover, switching from the first network node (source network node) to the second network node (target network node);

[0286] S620, the first network node (source network node) experienced a radio link failure, and the UE recorded a successful handover report;

[0287] S630, DAPS switch successful;

[0288] S640, the second network node (target network node) initiates a UE information acquisition process to obtain a successful handover report recorded by the UE; wherein, in this embodiment, the successful handover report recorded by the UE includes a terminal identifier, therefore the successful handover report obtained by the second network node includes a terminal identifier.

[0289] Optionally, an information request can be sent to the UE to request the successful handover report;

[0290] S650, after the second network node (target network node) receives the successful handover report, it immediately sends the successful handover report to the first network node (source network node) through an interface message (third interface message);

[0291] S660, a radio link failure occurs at the second network node (target network node), and the UE records an RLF report; in this embodiment, the RLF report recorded by the UE includes the terminal identifier;

[0292] S670, the UE reconnects to another network node (the third network node), and the third network node obtains the RLF report recorded by the UE;

[0293] S680, the third network node sends an RLF report to the second network node (target network node) via a failure indication message;

[0294] S690, the second network node (target network node) sends the RLF report to the first network node (source network node) through an interface message (such as the second interface message).

[0295] Compared to implementation method two, this third implementation method adds a terminal identifier record when the terminal records a successful handover report and an RLF report. Therefore, it is not necessary to add the terminal identifier in the interface message that sends the successful handover report or RLF report.

[0296] In this implementation method, after receiving the successful handover report and RLF report, the source network node associates them with the terminal identifier in the successful handover report and RLF report, determines the associated successful handover report and RLF report, and performs handover failure type analysis.

[0297] In this third embodiment, optionally, as in 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 RLF reports from at least one terminal.

[0298] When the second network node sends a successful handover report to the first network node through a third interface message, the third interface message includes a second report list, which includes a successful handover report of at least one terminal.

[0299] The target terminal is one of at least one terminal.

[0300] In this implementation, the interface message may include a report list for sending a successful handover report or RLF report for at least one terminal, and each successful handover report and RLF report includes a corresponding terminal identifier to indicate the terminal associated with each successful handover report or each RLF report.

[0301] In this embodiment of the invention, optionally, as in Embodiment 2, when sending an RLF report to the first network node via a second interface message and a successful handover report to the first network node via a third interface message, the second interface message and the third interface message can 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.

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

[0303] Optionally, the second interface message and the third interface message can be sent via the XN interface or the X2 interface, respectively. When there is no XN interface or X2 connection between network-side nodes, they can also be sent via the NG interface or the S1 interface.

[0304] In any of the above-described embodiments of the report transmission method of this invention, when network nodes transmit radio link failure (RLF) reports and successful handover reports, they associate the RLF reports and successful handover reports belonging to the same terminal. This allows network nodes to analyze the successful handover reports and RLF reports belonging to the same terminal together, ensuring that the cause of handover failure can be correctly analyzed, ensuring the accuracy of the network node's failure type analysis, and enabling effective optimization of handover parameters.

[0305] Another embodiment of the present invention provides a report processing method applied to a second network node, such as... Figure 7 As shown, the method includes:

[0306] S710, acquire wireless link failure RLF reports and successful handover reports;

[0307] S720, the associated RLF report and successful handover report are sent to the first network node so that the first network node can analyze the cause of the wireless link failure or the cause of the handover failure based on the associated RLF report and successful handover report.

[0308] Using the method described in this embodiment of the invention, when network nodes transmit Radio Link Failure (RLF) reports and successful handover reports, the RLF reports and successful handover reports sent by the same terminal are associated, so that network nodes can correctly analyze the reasons for handover failure, ensure the accuracy of the network nodes' failure type analysis, and effectively optimize handover parameters.

[0309] In this embodiment of the invention, optionally, the second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) switch, the first network node is the node before the terminal performs the DAPS switch, and the RLF report is obtained by the second network node from other network nodes, wherein the other network nodes are the network nodes that the terminal reconnects to after the DAPS switch successfully occurs and an RLF occurs.

[0310] In an embodiment of the present invention, optionally, obtaining a successful handover report in step S710 specifically includes:

[0311] The receiving terminal sends a successful handover report, which is generated by the terminal after a successful DAPS handover.

[0312] Obtain a Radio Link Failure (RLF) report, specifically including:

[0313] The terminal receives RLF reports sent by other network nodes. The RLF reports are generated after the terminal successfully switched to the dual active protocol stack (DAPS) and then experienced another RLF. The other network nodes are the network nodes that the terminal reconnected to after the terminal successfully switched to DAPS and then experienced another RLF.

[0314] Optionally, the report processing method, in step S720, sends the associated RLF report and successful handover report to the first network node, specifically includes:

[0315] Identify the related RLF report and the successful handover report, wherein the related RLF report and the successful handover report are generated by the same terminal;

[0316] The identified RLF report and the successful handover report with the relevant relationship are sent to the first network node.

[0317] In this embodiment of the invention, optionally, in step S720, the associated RLF report and successful handover report are sent to the first network node in one of the following ways:

[0318] Method 1: Send the associated terminal's RLF report and successful handover report to the first network node via the first interface message;

[0319] Method 2: Send an RLF report to the first network node through a second interface message, and send a successful handover report to the first network node through a third interface message, wherein the second interface message and the third interface message respectively include the terminal identifier;

[0320] Method 3: Send an RLF report to the first network node via a second interface message, and send a successful handover report to the first network node via a third interface message, wherein the RLF report and the successful handover report respectively include the identifier of the terminal.

[0321] Using the report processing method described in the embodiments of the present invention, in mode one, the second network node can simultaneously send a wireless link failure RLF report and a successful handover report to the first network node in the same interface message (first interface message), and the simultaneously sent wireless link failure RLF report and successful handover report can be associated with the terminal.

[0322] Using method two, the second network node can send a wireless link failure RLF report and a successful handover report to the first network node through different interface messages. The interface messages that send the wireless link failure RLF report and the successful handover report include the identifier of the target terminal. In this way, based on the identifier of the target terminal included in the interface message, the wireless link failure RLF report and the successful handover report corresponding to the same target terminal in the interface message can be associated.

[0323] Using method three, the second network node can send a wireless link failure RLF report and a successful handover report to the first network node through different interface messages. The wireless link failure RLF report and the successful handover report sent include the terminal identifier. In this way, the wireless link failure RLF report and the successful handover report corresponding to the same terminal can be identified based on the terminal identifier.

[0324] Optionally, when the terminal generates a wireless link failure RLF report and a successful handover report, the terminal's identifier is written into the generated wireless link failure RLF report and successful handover report. That is, compared with the prior art, the air interface transmission content is modified so that the wireless link failure RLF report or successful handover report including the terminal identifier is sent to the network node.

[0325] In this embodiment of the invention, optionally, a radio link failure (RLF) report and a successful handover report of the associated target terminal can be sent to the first network node through at least one of the XN interface, X2 interface, NG interface and S1 interface.

[0326] Alternatively, in another implementation, a radio link failure (RLF) report and a successful handover report for the associated target terminal may be 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.

[0327] Among them, the specific message is a pre-set message specifically used to indicate the sending of radio link failure (RLF) reports and successful handover reports.

[0328] Another embodiment of the present invention also provides a report processing method, such as... Figure 8 As shown, applied to a terminal device, the method includes:

[0329] S810, Generate a Radio Link Failure (RLF) Report and a Successful Handover Report. The RLF Report carries the terminal identifier and the Successful Handover Report carries the terminal identifier. The Successful Handover Report is generated by the terminal device after a successful handover of the Dual Activated Protocol Stack (DAPS). The RLF Report is generated by the terminal after a successful handover of DAPS followed by an RLF.

[0330] S820 sends the generated Radio Link Failure (RLF) report and Successful Handover report to the network device.

[0331] In this implementation, when the terminal records a successful handover report and an RLF report, it adds a terminal identifier record, eliminating the need to add the terminal identifier to the interface message sending the successful handover report or RLF report. This allows network nodes to associate the RLF report and successful handover report of the same terminal based on the terminal identifier in the successful handover report and the terminal identifier in the RLF report when transmitting radio link failure RLF reports and successful handover reports. This enables network nodes to correctly analyze the reasons for handover failures, ensuring the accuracy of failure type analysis and allowing for effective optimization of handover parameters.

[0332] In this embodiment of the invention, the content information included in the RLF report and the successful handover report, as well as the specific process of transmitting the RLF report and the successful handover report between network nodes, can be combined with... Figures 1 to 3 Please refer to the detailed description above; further details will not be provided here.

[0333] The report processing method according to one embodiment of the present invention is executed by a second network node, and the method includes:

[0334] Send a radio link failure (RLF) report and a successful handover report for the associated target terminal to the first network node.

[0335] In the report processing method described in this embodiment of the invention, when the second network node sends a Radio Link Failure (RLF) report and a successful handover report to the first network node, it associates the RLF report with the target terminal. That is, it can indicate that the RLF report and the successful handover report are associated with the same target terminal, so that the first network node can perform failure type analysis based on the associated RLF report and successful handover report, ensuring the accuracy of the failure type analysis by the network node, avoiding the analysis of incorrect types, and enabling effective optimization of handover parameters.

[0336] In this embodiment of the invention, optionally, a radio link failure (RLF) report and a successful handover report for the associated target terminal are sent to the first network node in one of the following ways:

[0337] Method 1: Send the associated target terminal's RLF report and successful handover report to the first network node via the first interface message;

[0338] Method 2: Send an RLF report to the first network node via a second interface message, and send a successful handover report to the first network node via a third interface message, wherein the second interface message and the third interface message respectively include the identifier of the target terminal;

[0339] Method 3: Send an RLF report to the first network node via a second interface message, and send a successful handover report to the first network node via a third interface message, wherein the RLF report and the successful handover report respectively include the identifier of the target terminal.

[0340] In this embodiment of the invention, optionally, the second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) handover, the first network node is the node before the terminal performs the DAPS handover, and the RLF report is obtained by the second network node from other network nodes, which are the network nodes that the terminal reconnected to after a successful DAPS handover and an RLF occurred. Using the report processing method described in this embodiment of the invention, specifically in mode one, the second network node can simultaneously send a wireless link failure RLF report and a successful handover report to the first network node in the same interface message (first interface message), and the simultaneously sent wireless link failure RLF report and successful handover report can be associated with the target terminal.

[0341] Using method two, the second network node can send a wireless link failure RLF report and a successful handover report to the first network node through different interface messages. The interface messages that send the wireless link failure RLF report and the successful handover report include the identifier of the target terminal. In this way, based on the identifier of the target terminal included in the interface message, the wireless link failure RLF report and the successful handover report corresponding to the same target terminal in the interface message can be associated.

[0342] In method three, the second network node can send a Radio Link Failure (RLF) report and a successful handover report to the first network node through different interface messages. The RLF report and successful handover report include the identifier of the target terminal. Thus, based on the identifier of the target terminal, RLF reports and successful handover reports corresponding to the same target terminal can be generated. Optionally, in this implementation, when the target terminal generates the RLF report and successful handover report, the identifier of the target terminal is written into the generated RLF report and successful handover report. That is, compared to the prior art, the air interface message content is modified to send the RLF report or successful handover report including the identifier of the target terminal to the network node.

[0343] In this embodiment of the invention, optionally, a radio link failure (RLF) report and a successful handover report of the associated target terminal can be sent to the first network node through at least one of the XN interface, X2 interface, NG interface and S1 interface.

[0344] Alternatively, in another implementation, a radio link failure (RLF) report and a successful handover report for the associated target terminal may be 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.

[0345] Among them, the specific message is a pre-set message specifically used to indicate the sending of radio link failure (RLF) reports and successful handover reports.

[0346] In any of the above-described embodiments of the report processing method of this invention, when network nodes transmit radio link failure (RLF) reports and successful handover reports, they associate the RLF reports and successful handover reports belonging to the same terminal. This allows network nodes to analyze the successful handover reports and RLF reports belonging to the same terminal together, ensuring that the cause of handover failure can be correctly analyzed, ensuring the accuracy of the network node's failure type analysis, and enabling effective optimization of handover parameters.

[0347] Another embodiment of the present invention also provides a report processing method, executed by a first network node, the method comprising:

[0348] Obtain the radio link failure (RLF) report and successful handover report of the associated target terminal;

[0349] Based on the RLF report and the successful handover report, analyze the reasons for the wireless link failure or the handover failure.

[0350] In the report processing method described in this embodiment of the invention, when the second network node sends a Radio Link Failure (RLF) report and a successful handover report to the first network node, it associates the RLF report with the target terminal. That is, it can indicate that the RLF report and the successful handover report are associated with the same target terminal, so that the first network node can perform failure type analysis based on the associated RLF report and successful handover report, ensuring the accuracy of the failure type analysis by the network node, avoiding the analysis of incorrect types, and enabling effective optimization of handover parameters.

[0351] Optionally, in the report processing method, the radio link failure (RLF) report and successful handover report of the associated target terminal are obtained through one of the following methods:

[0352] The RLF report and the successful handover report transmitted by the second network node and associated with the target terminal are obtained through the first interface message;

[0353] The second interface message is used to obtain the RLF report transmitted by the third network node, and the third interface message is used to obtain the successful handover report transmitted by the fourth network node, wherein the second interface message and the third interface message respectively include the identifier of the target terminal;

[0354] The second interface message obtains the RLF report transmitted by the third network node, and the third interface message obtains the successful handover report transmitted by the fourth network node, wherein the RLF report and the successful handover report respectively include the identifier of the target terminal.

[0355] It should be noted that the second, third, and fourth network nodes mentioned above are network nodes that can send RLF reports or successful handover reports to the first network node, respectively. The names are only used to distinguish different network nodes, and they can be the same or different network nodes.

[0356] Optionally, in the report processing method, when the RLF report and the successful handover report transmitted by the second network node and associated with the target terminal are obtained through the first interface message, the first interface message includes a report list, which includes RLF reports and successful handover reports associated with at least one terminal, and the target terminal is one of at least one terminal.

[0357] Optionally, in the report processing method, when obtaining the RLF report transmitted by the third network node through the second interface message, the second interface message includes a first report list, and the first report list includes RLF reports from at least one terminal.

[0358] When a successful handover report transmitted by a fourth network node is obtained through a third interface message, the third interface message includes a second report list, which includes a successful handover report of at least one terminal.

[0359] The target terminal is one of at least one terminal.

[0360] 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.

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

[0362] Optionally, in the report processing method, the first network node is the source network node of the target terminal, and the second network node is the target network node of the target terminal; or

[0363] The first network node is the source network node of the target terminal, and the third network node and the fourth network node are one of the following:

[0364] Source network node;

[0365] Target network node;

[0366] Network nodes other than the source network node and the target network node.

[0367] It should be noted that, in the embodiments of the present invention, in combination with Figure 5 and Figure 6 The example illustrates the application of the method described in this invention, using the network nodes that send RLF reports and successful handover reports as the target network nodes. However, the application scenarios of the method described in this embodiment are not limited to those that can only be used for... Figure 5 and Figure 6 In the scenario shown, the network node that can send an RLF report or a successful handover report to the source network node is not limited to the target network node, but can also be any of the network nodes listed above.

[0368] Optionally, the report processing method, wherein analyzing the cause of radio link failure or handover failure based on the determined correlated RLF report and the successful handover report includes:

[0369] Based on the RLF report and the successful handover report, the cause of the radio link failure or handover failure is analyzed to be one of the following: handover too late, handover too early, or handover to the wrong cell.

[0370] It should be noted that all descriptions of the report processing method executed by the first network node in the above embodiments are applicable to the embodiments of the report processing method executed by the second network node, and can achieve the same technical effect. Therefore, they will not be described in detail here.

[0371] like Figure 9 As shown, this embodiment of the invention also 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 executable on the processor 900; wherein, the transceiver 910 is connected to the processor 900 and the memory 920 through a bus interface, and the transceiver 910 is used to receive and send data under the control of the processor 900;

[0372] The processor 900 is used to read the program from the memory and execute the following processes:

[0373] Obtain wireless link failure RLF reports and successful handover reports;

[0374] Identify the related RLF reports and the successful handover reports;

[0375] Based on the identified related RLF reports and successful handover reports, analyze the reasons for wireless link failure or handover failure.

[0376] Optionally, in the network node, the processor 900 acquires radio link failure (RLF) reports and successful handover reports, including:

[0377] The terminal receives a Radio Link Failure (RLF) report and a successful handover report from a second network node via a first interface message. The second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) handover, and the first network node is the node before the terminal performs the DAPS handover. The RLF report is obtained by the second network node from other network nodes, which are the network nodes that the terminal reconnected to after a successful DAPS handover and an RLF occurred.

[0378] Determining the correlation between the RLF report and the successful handover report includes:

[0379] The radio link failure RLF report and the successful handover report transmitted in a first interface message are identified as the RLF report and the successful handover report that are related.

[0380] Optionally, in the network node, the processor 900 determines the radio link failure (RLF) report and the successful handover report transmitted in a first interface message as having a correlation, including:

[0381] If a first interface message carries a radio link failure RLF report and a successful handover report generated by different terminals, then the RLF report and the successful handover report generated by the same terminal are identified as having an association relationship.

[0382] Optionally, in the network node, the processor 900 acquires radio link failure (RLF) reports and successful handover reports, including:

[0383] The RLF report is obtained through the second interface message, and the successful handover report is obtained through the third interface message.

[0384] Determining the correlation between the RLF report and the successful handover report includes:

[0385] Based on the first terminal identifier carried in the second interface message, determine the RLF report corresponding to the first terminal identifier, and based on the second terminal identifier carried in the third interface message, determine the successful handover report corresponding to the second terminal identifier.

[0386] If the first terminal identifier is the same as the second terminal identifier, then the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier are determined to be the RLF report and the successful handover report that are related.

[0387] 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 the following: failure indication message, handover report message, access and mobility indication message, and specific message.

[0388] Optionally, in the network node, the processor 900 acquires radio link failure (RLF) reports and successful handover reports, specifically including:

[0389] Acquire the terminal's Radio Link Failure (RLF) report and successful handover report, wherein the RLF report carries the terminal identifier and the successful handover report carries the terminal identifier;

[0390] Determining the correlation between the RLF report and the successful handover report specifically includes:

[0391] Based on the terminal identifier carried in the RLF report and the terminal identifier carried in the successful handover report, RLF reports and successful handover reports with the same terminal identifier are identified as having an association relationship.

[0392] Among them, Figure 9In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 900) and memory (memory 920). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 910 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. 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 during operation.

[0393] The processor 900 can 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). The processor can also adopt a multi-core architecture.

[0394] It should be noted that the network node provided in this embodiment of the invention can implement all the method steps implemented by the first network node in the above method embodiment, and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0395] This invention also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of the reporting processing method applied to the aforementioned network node (first network node). The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD), etc.).

[0396] like Figure 10As shown, this embodiment of the invention also provides a network node, which is a second network node, including a processor 1000, a transceiver 1010, a memory 1020, and a program stored in the memory 1020 and executable on the processor 1000; wherein, the transceiver 1010 is connected to the processor 1000 and the memory 1020 through a bus interface, and the transceiver 1010 is used to receive and send data under the control of the processor 1000;

[0397] The processor 1000 is used to read the program from the memory and execute the following processes:

[0398] Obtain wireless link failure RLF reports and successful handover reports;

[0399] The associated RLF report and successful handover report are sent to the first network node so that the first network node can analyze the cause of the wireless link failure or the cause of the handover failure based on the associated RLF report and successful handover report.

[0400] Optionally, in the network node, the processor 1000 obtains a successful handover report, specifically including:

[0401] The receiving terminal sends a successful handover report, which is generated by the terminal after a successful DAPS handover.

[0402] Obtain a Radio Link Failure (RLF) report, specifically including:

[0403] The terminal receives RLF reports sent by other network nodes. The RLF reports are generated after the terminal successfully switched to the dual active protocol stack (DAPS) and then experienced another RLF. The other network nodes are the network nodes that the terminal reconnected to after the terminal successfully switched to DAPS and then experienced another RLF.

[0404] Optionally, in the network node, the processor 1000 sends the associated RLF report and successful handover report to the first network node, specifically including:

[0405] Identify the related RLF report and the successful handover report, wherein the related RLF report and the successful handover report are generated by the same terminal;

[0406] The identified RLF report and the successful handover report with the relevant relationship are sent to the first network node.

[0407] Among them, Figure 10In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1000) and memory (memory 1020). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1010 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. 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 during operation.

[0408] The processor 1000 can 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). The processor can also adopt a multi-core architecture.

[0409] It should be noted that the network node provided in this embodiment of the invention can implement all the method steps implemented by the second network node in the above method embodiment, and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0410] This invention also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of the reporting processing method applied to the aforementioned network node (second network node). The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD), etc.).

[0411] like Figure 11As shown, this embodiment of the invention also provides a terminal, including a processor 1100, a transceiver 1110, a memory 1120, and a program stored in the memory 1120 and executable 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 used to receive and send data under the control of the processor 1100, wherein the processor 1100 is used to read the program in the memory and execute the following processes:

[0412] Generate a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated by the terminal device after a successful handover to the Dual Activated Protocol Stack (DAPS). The RLF report is generated by the terminal after a successful handover to DAPS followed by an RLF.

[0413] The generated wireless link failure RLF report and successful handover report are sent to the network device.

[0414] Among them, Figure 11 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1100 and memory represented by memory 1120 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1110 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 1130 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

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

[0416] Optionally, the processor 1100 can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0417] This invention also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of the report processing method applied to the aforementioned terminal. The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs), etc.).

[0418] This invention also provides a report processing device, executed by a first network node, such as... Figure 12 As shown, the report processing device 1200 includes:

[0419] The first report acquisition module 1210 is used to acquire wireless link failure (RLF) reports and successful handover reports.

[0420] The determination module 1220 is used to determine the RLF report and the successful handover report that have an association relationship;

[0421] Analysis module 1230 is used to analyze the reasons for wireless link failure or handover failure based on the determined RLF report and the successful handover report that have a certain correlation.

[0422] Optionally, in the report processing apparatus, the first report acquisition module 1210 acquires radio link failure (RLF) reports and successful handover reports, including:

[0423] The terminal receives a Radio Link Failure (RLF) report and a successful handover report from a second network node via a first interface message. The second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) handover, and the first network node is the node before the terminal performs the DAPS handover. The RLF report is obtained by the second network node from other network nodes, which are the network nodes that the terminal reconnected to after a successful DAPS handover and an RLF occurred.

[0424] The determining module 1220 determines the associated RLF report and the successful handover report, including:

[0425] The radio link failure RLF report and the successful handover report transmitted in a first interface message are identified as the RLF report and the successful handover report that are related.

[0426] Optionally, in the report processing apparatus, the determining module 1220 determines the radio link failure RLF report and the successful handover report transmitted in a first interface message as having a correlation, including:

[0427] If a first interface message carries a radio link failure RLF report and a successful handover report generated by different terminals, then the RLF report and the successful handover report generated by the same terminal are identified as having an association relationship.

[0428] Optionally, in the report processing apparatus, the first report acquisition module 1210 acquires radio link failure (RLF) reports and successful handover reports, including:

[0429] The RLF report is obtained through the second interface message, and the successful handover report is obtained through the third interface message.

[0430] The determining module 1220 determines the associated RLF report and the successful handover report, including:

[0431] Based on the first terminal identifier carried in the second interface message, determine the RLF report corresponding to the first terminal identifier, and based on the second terminal identifier carried in the third interface message, determine the successful handover report corresponding to the second terminal identifier.

[0432] If the first terminal identifier is the same as the second terminal identifier, then the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier are determined to be the RLF report and the successful handover report that are related.

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

[0434] Optionally, in the report processing apparatus, the first report acquisition module 1210 acquires radio link failure (RLF) reports and successful handover reports, specifically including:

[0435] Obtain the Radio Link Failure (RLF) report and the Successful Handover report sent by the terminal, wherein the RLF report carries the terminal identifier and the Successful Handover report carries the terminal identifier;

[0436] The determination module 1220 determines the associated RLF report and the successful handover report, specifically including:

[0437] Based on the terminal identifier carried in the RLF report and the terminal identifier carried in the successful handover report, RLF reports and successful handover reports with the same terminal identifier are identified as having an association relationship.

[0438] This invention also provides a report processing device, executed by a second network node, such as... Figure 13 As shown, the report processing device 1300 includes:

[0439] The second report acquisition module 1310 is used to acquire wireless link failure RLF reports and successful handover reports;

[0440] The first transmitting module 1320 is used to send the associated RLF report and successful handover report to the first network node, so that the first network node can analyze the cause of wireless link failure or handover failure based on the associated RLF report and successful handover report.

[0441] Optionally, in the report processing apparatus, the second report acquisition module 1310 acquires a successful switching report, specifically including:

[0442] The receiving terminal sends a successful handover report, which is generated by the terminal after a successful DAPS handover.

[0443] The second report acquisition module 1310 acquires wireless link failure (RLF) reports, specifically including:

[0444] The terminal receives RLF reports sent by other network nodes. The RLF reports are generated after the terminal successfully switched to the dual active protocol stack (DAPS) and then experienced another RLF. The other network nodes are the network nodes that the terminal reconnected to after the terminal successfully switched to DAPS and then experienced another RLF.

[0445] Optionally, in the report processing apparatus, the first sending module 1320 sends the associated RLF report and successful handover report to the first network node, specifically including:

[0446] Identify the related RLF report and the successful handover report, wherein the related RLF report and the successful handover report are generated by the same terminal;

[0447] The identified RLF report and the successful handover report with the relevant relationship are sent to the first network node.

[0448] This invention also provides a report processing device, such as... Figure 14 As shown, the report processing device 1400, applied to a terminal, includes:

[0449] The report generation module 1410 is used to generate a wireless link failure (RLF) report and a successful handover report. The RLF report carries a terminal identifier and the successful handover report carries a terminal identifier. The successful handover report is generated by the terminal device after a successful handover of the dual active protocol stack (DAPS). The RLF report is generated by the terminal after a successful handover of DAPS followed by an RLF.

[0450] The second sending module 1420 is used to send the generated wireless link failure (RLF) report and successful handover report to the network device.

[0451] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

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

[0453] It should be noted that this report transmission device embodiment corresponds one-to-one with the above method embodiments. All implementation methods in the above method embodiments are applicable to this report transmission device embodiment and can achieve the same technical effect.

[0454] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

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

[0456] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0457] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations 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, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0458] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0459] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0460] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A report processing method, characterized in that, The method, executed by the first network node, includes: Obtain a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated after the terminal successfully performs a Dual Activated Protocol Stack (DAPS) handover, and the RLF report is generated after the terminal successfully performs a DAPS handover and then experiences an RLF. Identify the related RLF reports and the successful handover reports; Based on the identified related RLF reports and successful handover reports, analyze the reasons for wireless link failure or handover failure.

2. The report processing method according to claim 1, characterized in that, Obtain radio link failure RLF reports and successful handover reports, including: The terminal receives a Radio Link Failure (RLF) report and a successful handover report from a second network node via a first interface message. The second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) handover, and the first network node is the node before the terminal performs the DAPS handover. The RLF report is obtained by the second network node from other network nodes, which are the network nodes that the terminal reconnected to after a successful DAPS handover and an RLF occurred. Determining the correlation between the RLF report and the successful handover report includes: The radio link failure RLF report and the successful handover report transmitted in a first interface message are identified as the RLF report and the successful handover report that are related.

3. The report processing method according to claim 2, characterized in that, Identifying the radio link failure RLF report and the successful handover report transmitted in a first interface message as having a correlation with each other includes: If a message from the first interface carries a Radio Link Failure (RLF) report and a successful handover report generated by different terminals, then the RLF report and the successful handover report generated by the same terminal are identified as having an association.

4. The report processing method according to claim 1, characterized in that, Obtain radio link failure RLF reports and successful handover reports, including: The RLF report is obtained through the second interface message, and the successful handover report is obtained through the third interface message. Determining the correlation between the RLF report and the successful handover report includes: Based on the first terminal identifier carried in the second interface message, determine the RLF report corresponding to the first terminal identifier, and based on the second terminal identifier carried in the third interface message, determine the successful handover report corresponding to the second terminal identifier. If the first terminal identifier is the same as the second terminal identifier, then the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier are determined to be the RLF report and the successful handover report that are related.

5. The report processing method according to any one of claims 2 to 3, characterized in that, The first interface message is at least one or more of the following: failure indication message, handover report message, access and mobility indication message.

6. The report processing method according to claim 4, characterized in that, The second interface message and the third interface message are at least one or more of the following: failure indication message, handover report message, and access and mobility indication message.

7. The report processing method according to claim 1, characterized in that, Obtain radio link failure (RLF) reports and successful handover reports, specifically including: Acquire the wireless link failure (RLF) report and successful handover report sent by the terminal; Determining the correlation between the RLF report and the successful handover report specifically includes: Based on the terminal identifier carried in the RLF report and the terminal identifier carried in the successful handover report, RLF reports and successful handover reports with the same terminal identifier are identified as having an association relationship.

8. A report processing method, characterized in that, Applied to a second network node, the method includes: Obtain a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated after the terminal successfully performs a Dual Activated Protocol Stack (DAPS) handover, and the RLF report is generated after the terminal successfully performs a DAPS handover and then experiences an RLF. The associated RLF report and successful handover report are sent to the first network node so that the first network node can analyze the cause of the wireless link failure or the cause of the handover failure based on the associated RLF report and successful handover report.

9. The report processing method according to claim 8, characterized in that, Obtain a successful switchover report, which includes: The receiving terminal sends a successful handover report, which is generated by the terminal after a successful DAPS handover. Obtain a Radio Link Failure (RLF) report, specifically including: The terminal receives RLF reports sent by other network nodes. The RLF reports are generated after the terminal successfully switched to the dual active protocol stack (DAPS) and then experienced another RLF. The other network nodes are the network nodes that the terminal reconnected to after the terminal successfully switched to DAPS and then experienced another RLF.

10. The report processing method according to claim 8 or 9, characterized in that, Send the associated RLF report and successful handover report to the first network node, specifically including: Identify the related RLF report and the successful handover report, wherein the related RLF report and the successful handover report are generated by the same terminal; The identified RLF report and the successful handover report with the relevant relationship are sent to the first network node.

11. A report processing method, characterized in that, Applied to a terminal, the method includes: Generate a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated by the terminal after a successful handover to the Dual Active Protocol Stack (DAPS). The RLF report is generated by the terminal after a successful handover to DAPS followed by an RLF. The generated wireless link failure RLF report and successful handover report with correlation are sent to the network device.

12. A network node, wherein the network node is a first network node, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Obtain a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated after the terminal successfully performs a Dual Activated Protocol Stack (DAPS) handover, and the RLF report is generated after the terminal successfully performs a DAPS handover and then experiences an RLF. Identify the related RLF reports and the successful handover reports; Based on the identified related RLF reports and successful handover reports, analyze the reasons for wireless link failure or handover failure.

13. The network node according to claim 12, characterized in that, The processor acquires radio link failure (RLF) reports and successful handover reports, including: The terminal receives a Radio Link Failure (RLF) report and a successful handover report from a second network node via a first interface message. The second network node is the node after the terminal performs a dual-activation protocol stack (DAPS) handover, and the first network node is the node before the terminal performs the DAPS handover. The RLF report is obtained by the second network node from other network nodes, which are the network nodes that the terminal reconnected to after a successful DAPS handover and an RLF occurred. Determining the correlation between the RLF report and the successful handover report includes: The radio link failure RLF report and the successful handover report transmitted in a first interface message are identified as the RLF report and the successful handover report that are related.

14. The network node according to claim 13, characterized in that, The processor identifies the Radio Link Failure (RLF) report and the Successful Handover report transmitted in a first interface message as having a correlation with each other, including: If a message from the first interface carries a Radio Link Failure (RLF) report and a successful handover report generated by different terminals, then the RLF report and the successful handover report generated by the same terminal are identified as having an association.

15. The network node according to claim 12, characterized in that, The processor acquires radio link failure (RLF) reports and successful handover reports, including: The RLF report is obtained through the second interface message, and the successful handover report is obtained through the third interface message. Determining the correlation between the RLF report and the successful handover report includes: Based on the first terminal identifier carried in the second interface message, determine the RLF report corresponding to the first terminal identifier, and based on the second terminal identifier carried in the third interface message, determine the successful handover report corresponding to the second terminal identifier. If the first terminal identifier is the same as the second terminal identifier, then the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier are determined to be the RLF report and the successful handover report that are related.

16. The network node according to claim 12, characterized in that, The processor acquires radio link failure (RLF) reports and successful handover reports, specifically including: Acquire the wireless link failure (RLF) report and successful handover report sent by the terminal; Determining the correlation between the RLF report and the successful handover report specifically includes: Based on the terminal identifier carried in the RLF report and the terminal identifier carried in the successful handover report, RLF reports and successful handover reports with the same terminal identifier are identified as having an association relationship.

17. A network node, wherein the network node is a second network node, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Obtain a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated after the terminal successfully performs a Dual Activated Protocol Stack (DAPS) handover, and the RLF report is generated after the terminal successfully performs a DAPS handover and then experiences an RLF. The associated RLF report and successful handover report are sent to the first network node so that the first network node can analyze the cause of the wireless link failure or the cause of the handover failure based on the associated RLF report and successful handover report.

18. The network node according to claim 17, characterized in that, The processor sends the associated RLF report and successful handover report to the first network node, specifically including: Identify the related RLF report and the successful handover report, wherein the related RLF report and the successful handover report are generated by the same terminal; The identified RLF report and the successful handover report with the relevant relationship are sent to the first network node.

19. A terminal, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Generate a Radio Link Failure (RLF) report and a Successful Handover report. The RLF report carries the terminal identifier, and the Successful Handover report carries the terminal identifier. The Successful Handover report is generated by the terminal after a successful handover to the Dual Activated Protocol Stack (DAPS). The RLF report is generated by the terminal after a successful handover to DAPS followed by an RLF. The generated wireless link failure RLF report and successful handover report with correlation are sent to the network device.

20. A report processing device, characterized in that, Applied to a first network node, the device includes: The first report acquisition module is used to acquire radio link failure (RLF) reports and successful handover reports. The RLF report carries the terminal identifier, and the successful handover report carries the terminal identifier. The successful handover report is generated by the terminal after a successful handover of the dual active protocol stack (DAPS), and the RLF report is generated after an RLF occurs again after a successful handover of DAPS. The determination module is used to determine the RLF report and the successful handover report that have a relationship; The analysis module is used to analyze the reasons for wireless link failure or handover failure based on the determined correlation between the RLF report and the successful handover report.

21. A report processing device, characterized in that, Applied to a second network node, the device includes: The second report acquisition module is used to acquire radio link failure (RLF) reports and successful handover reports. The RLF report carries the terminal identifier, and the successful handover report carries the terminal identifier. The successful handover report is generated by the terminal after a successful handover of the dual active protocol stack (DAPS), and the RLF report is generated after a successful handover of DAPS followed by an RLF. The first sending module is used to send the associated RLF report and successful handover report to the first network node, so that the first network node can analyze the cause of wireless link failure or handover failure based on the associated RLF report and successful handover report.

22. A report processing device, characterized in that, Applied to a terminal, the device includes: The report generation module is used to generate a radio link failure (RLF) report and a successful handover report. The RLF report carries the terminal identifier and the successful handover report carries the terminal identifier. The successful handover report is generated after the terminal successfully hands over to the dual active protocol stack (DAPS). The RLF report is generated after the terminal successfully hands over to DAPS and then experiences an RLF. The second sending module is used to send the generated wireless link failure RLF report and successful handover report with correlation to the network device.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that causes the computer to perform the report processing method according to any one of claims 1 to 7, or to perform the report processing method according to any one of claims 8 to 10, or to perform the report processing method according to claim 11.

Images