WO2023011239A1 - 报告处理方法、装置、网络节点及终端 - Google Patents

报告处理方法、装置、网络节点及终端 Download PDF

Info

Publication number
WO2023011239A1
WO2023011239A1 PCT/CN2022/107741 CN2022107741W WO2023011239A1 WO 2023011239 A1 WO2023011239 A1 WO 2023011239A1 CN 2022107741 W CN2022107741 W CN 2022107741W WO 2023011239 A1 WO2023011239 A1 WO 2023011239A1
Authority
WO
WIPO (PCT)
Prior art keywords
report
rlf
successful
network node
successful handover
Prior art date
Application number
PCT/CN2022/107741
Other languages
English (en)
French (fr)
Inventor
王睿炜
刘爱娟
Original Assignee
大唐移动通信设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Priority to US18/290,634 priority Critical patent/US20240259903A1/en
Priority to JP2024506837A priority patent/JP2024529544A/ja
Priority to EP22851953.4A priority patent/EP4383811A1/en
Priority to KR1020247007121A priority patent/KR20240038092A/ko
Publication of WO2023011239A1 publication Critical patent/WO2023011239A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H04W36/185—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection using make before break
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection

Definitions

  • the present disclosure relates to the field of wireless technology, and in particular to a report processing method, device, network node and terminal.
  • Dual Active Protocol Stack if the wireless link fails on the source side and then successfully switches to the target side, then the wireless link failure information on the source side will be recorded in the successful switching report , and use access and mobility indication (Access and mobility indication) messages to transmit between network nodes; it is also possible that a random access failure occurs on the target side after the handover or a wireless link failure occurs after the random access succeeds, then The radio link failure information on the target side will be recorded in a radio link failure (Radio Link Failure, RLF) report, and transmitted between network nodes using failure indication (failure indication) messages.
  • RLF Radio Link Failure
  • failure indication failure indication
  • the source-side network node in the DAPS handover scenario, it can receive the successful handover report and the RLF report through the Access and mobility indication message and the failure indication message, and then analyze the successful handover report and the RLF report. There is an issue that the analysis results of the successful switch report and the RLF report analysis failure type are inaccurate.
  • Embodiments of the present disclosure provide a report processing method, device, network node, and terminal, so as to solve at least one technical problem described above.
  • One embodiment of the present disclosure also provides a report processing method, wherein, applied to a terminal device, the method includes:
  • 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 the dual activation protocol stack DAPS handover is successful
  • the RLF report is generated by the terminal after RLF occurs after the DAPS handover is successful
  • the present disclosure also provides another implemented report processing method, wherein, performed by the first network node, the method includes:
  • the report processing method wherein acquiring a radio link failure RLF report and a successful handover report includes:
  • Radio link failure RLF report and a successful handover report sent by a second network node through a first interface message wherein the second network node is a node after the terminal performs a dual-activation protocol stack DAPS handover, and the first network node is the node before the terminal performs DAPS handover, the RLF report is obtained by the second network node from other network nodes, and the other network node is that the terminal has RLF after the DAPS handover is successful, and then reconnects to network node;
  • Determining the RLF report and the successful handover report having an association relationship includes:
  • one of the radio link failure RLF report and the successful handover report transmitted in the first interface message is determined as the RLF report and the successful handover report having an associated relationship ,include:
  • one of the first interface messages carries a radio link failure RLF report and a successful handover report generated by different terminals, then determine the RLF report and the successful handover report generated by the same terminal as the RLF report and the successful handover report that have an associated relationship. report on successful switchover.
  • the report processing method wherein, obtaining a radio link failure RLF report and a successful handover report includes:
  • Determining the RLF report and the successful handover report having an association relationship includes:
  • the first terminal identifier is the same as the second terminal identifier, determining the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier as the RLF report having an association relationship and the successful switch report.
  • the first interface message, the second interface message and the third interface message are respectively a failure indication message, a handover report message, an access and mobility At least one or more of an indication message and a specific message.
  • the report processing method wherein acquiring a radio link failure RLF report and a successful handover report specifically includes:
  • Determining the RLF report and the successful handover report having an association relationship specifically includes:
  • the RLF report and the successful handover report with the same terminal identifier are determined as the RLF report and the successful handover report having an associated relationship.
  • the present disclosure also provides another report processing method implemented, wherein, applied to the second network node, the method includes:
  • the report processing method wherein obtaining a successful handover report specifically includes:
  • the RLF report is generated by the terminal after the RLF occurs after the DAPS switch of the dual-activation protocol stack is successful.
  • the other network nodes are the RLF of the terminal after the DAPS switch is successful, and then reconnect to the network node.
  • the report processing method wherein sending the associated RLF report and the successful handover report to the first network node specifically includes:
  • An embodiment of the present disclosure also provides a terminal, which includes a memory, a transceiver, and a processor:
  • the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:
  • 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 the dual activation protocol stack DAPS handover is successful
  • the RLF report is generated by the terminal after RLF occurs after the DAPS handover is successful
  • An embodiment of the present disclosure also provides a network node, where the network node is a first network node, including a memory, a transceiver, and a processor:
  • the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:
  • the processor acquires a radio link failure RLF report and a successful handover report, including:
  • Radio link failure RLF report and a successful handover report sent by a second network node through a first interface message wherein the second network node is a node after the terminal performs a dual-activation protocol stack DAPS handover, and the first network node is the node before the terminal performs DAPS handover, the RLF report is obtained by the second network node from other network nodes, and the other network node is that the terminal has RLF after the DAPS handover is successful, and then reconnects to network node;
  • Determining the RLF report and the successful handover report having an association relationship includes:
  • the processor determines a radio link failure RLF report and a successful handover report transmitted in the first interface message as the RLF report and the Successful switch reports, including:
  • one of the first interface messages carries a radio link failure RLF report and a successful handover report generated by different terminals, then determine the RLF report and the successful handover report generated by the same terminal as the RLF report and the successful handover report that have an associated relationship. report on successful switchover.
  • the processor acquires a radio link failure RLF report and a successful handover report, including:
  • Determining the RLF report and the successful handover report having an association relationship includes:
  • the first terminal identifier is the same as the second terminal identifier, determining the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier as the RLF report having an association relationship and the successful switch report.
  • the network node wherein, the first interface message, the second interface message and the third interface message are respectively a failure indication message, a handover report message, an access and mobility indication At least one or more of message and specific message.
  • the network node wherein the processor obtains a radio link failure RLF report and a successful handover report, specifically includes:
  • Determining the RLF report and the successful handover report having an association relationship specifically includes:
  • the RLF report and the successful handover report with the same terminal identifier are determined as the RLF report and the successful handover report having an associated relationship.
  • An embodiment of the present disclosure also provides a network node, where the network node is a second network node, including a memory, a transceiver, and a processor:
  • the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:
  • the network node, wherein the processor obtains a successful handover report specifically includes:
  • the processor acquires a radio link failure RLF report, specifically including:
  • the RLF report is generated by the terminal after the RLF occurs after the DAPS switch of the dual-activation protocol stack is successful.
  • the other network nodes are the RLF of the terminal after the DAPS switch is successful, and then reconnect to the network node.
  • the network node, wherein the processor sends the associated RLF report and the successful handover report to the first network node specifically includes:
  • An embodiment of the present disclosure also provides a report processing device, wherein, applied to a terminal, the device includes:
  • a report generating module configured to generate a radio link failure RLF report and a successful handover report, wherein the RLF report carries a terminal identifier and the successful handover report carries a terminal identifier, and the successful handover report is that the terminal device is in a dual-activation protocol stack Generated after the DAPS handover is successful, the RLF report is generated by the terminal after the RLF occurs after the DAPS handover is successful;
  • the second sending module is configured to send the generated radio link failure RLF report and successful handover report to the network device.
  • An embodiment of the present disclosure also provides a report processing device, which is applied to a first network node for execution, and the device includes:
  • a first report obtaining module configured to obtain a radio link failure RLF report and a successful handover report
  • a determining module configured to determine the RLF report and the successful handover report having an association relationship
  • the analysis module is configured to analyze the cause of the radio link failure or the cause of the handover failure according to the determined RLF report and the successful handover report having an associated relationship.
  • the first report acquiring module acquires a radio link failure RLF report and a successful handover report, including:
  • Radio link failure RLF report and a successful handover report sent by a second network node through a first interface message wherein the second network node is a node after the terminal performs a dual-activation protocol stack DAPS handover, and the first network node is the node before the terminal performs DAPS handover, the RLF report is obtained by the second network node from other network nodes, and the other network node is that the terminal has RLF after the DAPS handover is successful, and then reconnects to network node;
  • the determining module determines the RLF report and the successful handover report having an association relationship, including:
  • the determining module determines a radio link failure RLF report and a successful handover report transmitted in the first interface message as the RLF report and the successful handover report having an association relationship.
  • Toggle reports including:
  • one of the first interface messages carries a radio link failure RLF report and a successful handover report generated by different terminals, then determine the RLF report and the successful handover report generated by the same terminal as the RLF report and the successful handover report that have an associated relationship. report on successful switchover.
  • the first report acquiring module acquires a radio link failure RLF report and a successful handover report, including:
  • the determining module determines the RLF report and the successful handover report having an association relationship, including:
  • the first terminal identifier is the same as the second terminal identifier, determining the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier as the RLF report having an association relationship and the successful switch report.
  • the first interface message, the second interface message and the third interface message are respectively a failure indication message, a handover report message, an access and mobility At least one or more of an indication message and a specific message.
  • the first report obtaining module obtains a radio link failure RLF report and a successful handover report, specifically including:
  • the determining module determines the RLF report and the successful handover report having an association relationship, specifically including:
  • the RLF report and the successful handover report with the same terminal identifier are determined as the RLF report and the successful handover report having an associated relationship.
  • An embodiment of the present disclosure also provides a report processing device, which is applied to a second network node for execution, and the device includes:
  • the second report obtaining module is used to obtain a wireless link failure RLF report and a successful handover report
  • the first sending module is configured to send the associated RLF report and the successful handover report to the first network node, so that the first network node analyzes the radio link failure according to the associated RLF report and the successful handover report The reason or the reason for the switching failure.
  • the second report acquiring module acquires a successful handover report, specifically includes:
  • the second report acquiring module acquires a wireless link failure RLF report, specifically including:
  • the RLF report is generated by the terminal after the RLF occurs after the DAPS switch of the dual-activation protocol stack is successful.
  • the other network nodes are the RLF occurred by the terminal after the DAPS switch is successful, and then reconnect to the network node.
  • the first sending module sends the associated RLF report and the successful handover report to the first network node, specifically including:
  • An embodiment of the present disclosure also provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to perform the report processing as described in the preceding item method.
  • An embodiment of the present disclosure further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is configured to cause the computer to execute the report processing method described in the preceding item.
  • An embodiment of the present disclosure further provides a communication device, wherein a computer program is stored in the communication device, and the computer program is used to make the communication device execute the report processing method described in the preceding item.
  • the network nodes transmit the radio link failure RLF report and the successful handover report
  • the RLF report and the successful handover report sent by the same terminal are associated, so that the network node It can correctly analyze the cause of handover failure, ensure the accuracy of failure type analysis by network nodes, and optimize handover parameters effectively.
  • FIG. 1 shows a schematic diagram of a switching process applicable to the method described in the embodiment of the present disclosure
  • FIG. 2 shows a schematic diagram of another switching process applicable to the method described in the embodiment of the present disclosure
  • FIG. 3 shows a schematic diagram of the handover report (handover report) message transmission process
  • FIG. 4 shows a schematic flowchart of the report processing method described in Embodiment 1 of the present disclosure
  • Fig. 5 shows one of the implementation processes of the method described in the embodiment of the present disclosure
  • FIG. 6 shows the second implementation process of the method described in the embodiment of the present disclosure
  • FIG. 7 shows a schematic flowchart of the report processing method described in Embodiment 2 of the present disclosure
  • FIG. 8 shows a schematic flowchart of the report processing method described in Embodiment 3 of the present disclosure
  • FIG. 9 shows a schematic structural diagram of a network node according to an embodiment of the present disclosure.
  • Fig. 10 shows a schematic structural diagram of a network node according to another embodiment of the present disclosure.
  • FIG. 11 shows a schematic structural diagram of a terminal according to an embodiment of the present disclosure
  • FIG. 12 shows a schematic structural diagram of the report processing device according to Embodiment 1 of the present disclosure
  • FIG. 13 shows a schematic structural diagram of the report processing device described in Embodiment 2 of the present disclosure
  • FIG. 14 shows a schematic structural diagram of the report processing device according to Embodiment 3 of the present disclosure.
  • words such as “exemplary” or “for example” are used as examples, illustrations or illustrations. Any embodiment or design described as “exemplary” or “for example” in the embodiments of the present disclosure shall not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present related concepts in a concrete manner.
  • the report processing method, device, network node, and terminal provided by the embodiments of the present disclosure may be applied in a wireless communication system.
  • the wireless communication system may be a system using the fifth generation (5th Generation, 5G) mobile communication technology (hereinafter referred to as the 5G system).
  • 5G fifth generation
  • NR New Radio
  • the report processing method described in the present disclosure can be applied to a traditional handover process and a DAPS handover process.
  • a schematic diagram of a traditional handover process the traditional handover process includes:
  • Step 1 a handover request and a handover response are transmitted between network node 1 and network node 2, so that a terminal (user equipment (User Equipment, UE)) is handed over from network node 1 (source network node) to network node 2 (target network node) ;
  • UE user equipment
  • Step 2 the network node 1 sends a synchronous reconfiguration message to the UE, so that the UE performs handover immediately, disconnects from the network node 1, and randomly accesses to the network node 2;
  • Step 3 the random access between the UE and the network node 2 is completed, and a handover completion message is sent to the network node 2;
  • Step 4 the network node 2 sends a context release message to the network node 1, notifying the network node 1 to release the UE context.
  • FIG. 2 is a schematic diagram of the DAPS handover process, the DAPS handover process includes:
  • Step 1 during the process of 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;
  • Step 2 the target network node sends a request confirmation message to the source network node
  • Step 3 the source network node sends a handover instruction to the UE
  • Step 4 the UE performs an access procedure to the target network node
  • Step 5 after the UE completes the radio resource control (Radio Resource Control, RRC) reconfiguration, it sends an RRC connection reconfiguration complete message to the target network node;
  • RRC Radio Resource Control
  • the target network node receives the handover instruction from the source network node, and also receives the RRC connection reconfiguration from the UE
  • the target network node receives the handover instruction from the source network node, and also receives the RRC connection reconfiguration from the UE
  • PDCP Packet Data Convergence Protocol
  • steps 6 and 7 the UE simultaneously maintains data transmission and reception with the source network node and the target network node;
  • Step 8 the target network entity sends a release instruction to the UE, notifying the UE to complete the data transmission, expecting the UE to release the data connection between the source network node and the UE;
  • Step 9 The UE stops the uplink transmission and downlink reception between the source network node and the UE, and starts to release the entire source-side master cell group (Master Cell Group, MCG) configuration.
  • MCG Master Cell Group
  • Step 10 The UE only maintains data sending and receiving with the target network node.
  • the UE is a user equipment (User Equipment, UE), for example: it can be a mobile phone, a tablet computer (Tablet Personal Computer), Terminal-side devices such as laptop computer (Laptop Computer), personal digital assistant (personal digital assistant, PDA), mobile Internet device (Mobile Internet Device, MID) or wearable device (Wearable Device).
  • UE User Equipment
  • Terminal-side devices such as laptop computer (Laptop Computer), personal digital assistant (personal digital assistant, PDA), mobile Internet device (Mobile Internet Device, MID) or wearable device (Wearable Device).
  • PDA personal digital assistant
  • Mobile Internet Device Mobile Internet Device
  • MID mobile Internet Device
  • wearable device wearable device
  • Network nodes can be base stations, such as base stations of 5G and later versions (for example: gNB, 5G NR NB, ng-eNB, etc.), or base stations in other communication systems, or called It is a node B. It should be noted that in the embodiments of the present disclosure, only a 5G base station is taken as an example, but a specific type of network node is not limited.
  • the terminal side records the RLF report and the successful handover report.
  • the terminal will record the RLF report when handover failure or RLF occurs.
  • the RLF report is used to record at least two scenarios: handover failure and wireless link failure, and one RLF report can only represent the record of one scenario.
  • the RLF report includes at least one of the following:
  • the terminal confirms the neighbor cell measurement results after handover failure or wireless link failure
  • Terminal failure cell identification information such as Cell Global Identity (CGI)/Physical Cell Identity (PCI) frequency point;
  • CGI Cell Global Identity
  • PCI Physical Cell Identity
  • the terminal reconstructs the cell identification information
  • UE reporting timer the duration from the last time the terminal confirms receiving the handover initiation message to the connection failure
  • C-RNTI Cell Radio Network Temporary Identifier
  • Sub-reasons for wireless link failure T310 timeout or random access problem or RLC layer reaches the maximum retransmission or beam recovery failure (Beam Failure Recovery Failure, BFRF);
  • TAC Tracking Area Code
  • WLAN Wireless Local Area Network
  • the recording scenarios of the successful handover report include:
  • the terminal In the traditional handover process, when the length value of the terminal T310 timer, T312 timer or T304 timer exceeds a predetermined threshold, the terminal records a successful handover report;
  • the terminal records a successful handover report
  • the content of the successful handover report records the measurement information at the trigger time, cell identification information, terminal location information and timer value, etc.
  • the UE After the UE has recorded the RLF report and/or the successful handover report, it sends the RLF report and/or the RLF report to the network node in the RRC connection establishment complete message, the RRC connection reconfiguration complete message, the RRC connection re-establishment complete message or the RRC recovery complete message or successfully switch reports.
  • the network node sends a request message to the UE, and the UE sends an RLF report and/or a successful handover report to the network node through a response message.
  • a mobility robustness optimization MRO
  • MRO Mobility Robustness Optimization
  • the terminal will record the RLF report when handover failure or RLF occurs. After the handover fails, the terminal selects a cell, and then re-connects to the network through RRC connection re-establishment or RRC connection establishment, and notifies the network that the RLF report is reserved on the terminal side, and the network side obtains the RLF report from the terminal when necessary, for network Side network optimization.
  • the MRO feature is mainly used to discover and solve parameter configuration problems in the mobility process, and defines three failure types, including handover too early, handover too late, and handover to the wrong cell. in:
  • Premature handover During the handover process, the terminal fails to access the target cell, or the terminal successfully accesses the target cell but the radio link fails soon, and the terminal re-establishes the RRC connection and tries to access the source cell;
  • the terminal fails to access the target cell, or the terminal successfully accesses the target cell but the radio link fails soon, and the terminal re-establishes an RRC connection and tries to access a cell different from the handover target cell and the source cell. other districts.
  • the terminal After the handover is completed, whether the terminal can stably camp on the target cell is the key to judging the above failure type. If the UE has been camped on stably, it has nothing to do with the previous handover if the failure occurs again, because after the handover is completed, the UE can camp on the target cell stably. If it does not reside stably, it may be caused by the previous handover, for example, the selection of the target cell is unreasonable.
  • the UE report timer in the RLF report To determine whether the terminal is camping stably, use the UE report timer in the RLF report to judge. If the value is relatively small, it means that the terminal is not camping stably. If it is relatively large, it means camping stably after handover. If it is 0, it means that no switching occurs.
  • the DASP handover succeeds and the terminal can stably camp in the target cell, but the radio link failure occurs in the source cell during the DAPS handover process.
  • the DAPS handover and access to the target cell succeeds, but the radio link fails soon, and the terminal re-establishes the RRC connection and tries to access the source cell.
  • the terminal fails to access the target cell, but falls back to the source cell successfully and no RLF occurs for a period of time.
  • RLF first occurs in the connection of the source cell, and then the terminal fails to access the target cell, and the terminal re-establishes the RRC connection and tries to access other cells different from the handover target cell and the source cell.
  • the access to the target cell is successful, but the radio link fails soon, and the terminal re-establishes the RRC connection and tries to access other cells different from the handover target cell and the source cell.
  • Radio link failure occurs in the source cell during the DAPS handover process, it will be recorded in the successful handover report. Subsequently, if the target side access fails or the target side random access succeeds but RLF occurs soon, it will be recorded in the RLF report.
  • the message flow between network nodes includes a failure indication message, a handover report message, and an Access and mobility indication message.
  • the UE may re-connect to the network after handover failure or RLF failure.
  • the network node obtains the RLF report of the UE, if the current network node is not the node where the failure occurred, it needs to forward the RLF report and other related information to the failed network among network nodes. Nodes, which facilitate the analysis and optimization of failed network nodes.
  • the failure indication message is triggered by an RRC re-establishment request or RRC establishment on the air interface.
  • RRC re-establishment request optionally, include the information carried in the RRC re-establishment request and the UE RLF report; for the RRC establishment, include the UE RLF report.
  • Step 1 the handover of UE from network node 1 to network node 2 is successful
  • Step 2 a radio link failure RLF occurs on network node 2;
  • Step 3 the UE records the RLF report
  • Step 4 the UE successfully accesses the network node 3;
  • Step 5 the network node 3 obtains the RLF report of the UE
  • Step 6 After the UE is handed over to the network node 3 successfully, RLF occurs, and the failed base station is the network node 2, and sends a failure indication message to the network node 2;
  • Step 7 After analyzing the failure indication message, network node 2 finds that the RLF failure is caused by the unreasonable target cell selected by network node 1. The handover failure type belongs to the failure to switch to the wrong cell. Network node 3 should be selected, and then send a handover report handover The report message notifies the network node 1.
  • the handover report message includes the following information:
  • Report type indicating the results of failed node analysis, including premature handover, handover to wrong cell, etc.
  • Handover target cell including global cell ID
  • RRC re-establishes the cell, including the global cell ID.
  • the report type When the report type is handover to a wrong cell, it includes the indication information of the RRC re-established cell, and informs the source cell that the cell should be selected as the target cell for the handover;
  • the UE RLF report optional content, if the received failure indication message includes the UE RLF report, the UE RLF report is also included when transmitting the handover report message.
  • the Access and mobility indication message is used to transmit relevant information such as a successful handover report between network nodes.
  • a radio link failure may occur at the source side, and a random access failure may also occur at the handover target side or a radio link failure may occur soon after the random access succeeds.
  • the failure information on the source side is recorded in the successful handover report and transmitted between network nodes using the Access and mobility indication message; the failure information on the target side is recorded in the RLF report and transmitted between network nodes using the failure indication message.
  • the network node on the handover source side may have released the context information of the UE after the handover is completed, so when receiving the successful handover report and the RLF report through the Access and mobility indication message and the failure indication message, it does not know whether these reports correspond to the same UE.
  • the successful handover report corresponds to UE1
  • the RLF report corresponds to UE2
  • UE1 may count as a DAPS handover too late error
  • UE2 may count as a handover premature error. If the successful handover report and the RLF report belong to the same UE, the UE may be counted as an error of handover to the wrong cell.
  • an embodiment of the present disclosure provides a report processing method.
  • this method when transmitting a wireless link failure RLF report and a successful handover report between network nodes, the transmitted RLF report and success report belonging to the same terminal are sent.
  • Handover reports are associated so that network nodes can correctly analyze the cause of handover failure, ensure the accuracy of network nodes’ analysis of failure types, and optimize handover parameters effectively.
  • the report processing method described in one embodiment of the present disclosure is executed by the first network node, and the method includes:
  • the second network node may be, but not limited to, a target network node that can only serve as a target terminal after switching
  • the first network node may be, but not limited to, a source network that can only serve as a target terminal before switching node.
  • the second network node when the second network node sends the radio link failure RLF report and the successful handover report to the first network node, it is associated with the terminal, that is, it can indicate the radio link failure RLF report and the The successful handover report is associated with the same terminal, so that the first network node performs failure type analysis according to the associated radio link failure RLF report and successful handover report, so as to ensure the accuracy of the failure type analysis by the network node and avoid analysis errors type, and can perform effective switching parameter optimization.
  • step S410 obtaining a radio link failure RLF report and a successful handover report includes:
  • Radio link failure RLF report and a successful handover report sent by a second network node through a first interface message wherein the second network node is a node after the terminal performs a dual-activation protocol stack DAPS handover, and the first network node is the node before the terminal performs DAPS handover, the RLF report is obtained by the second network node from other network nodes, and the other network node is that the terminal has RLF after the DAPS handover is successful, and then reconnects to network node;
  • step S420 determining the RLF report and the successful handover report having an association relationship includes:
  • determining a radio link failure RLF report and a successful handover report transmitted in the first interface message as the RLF report and the successful handover report having an associated relationship includes:
  • one of the first interface messages carries a radio link failure RLF report and a successful handover report generated by different terminals, then determine the RLF report and the successful handover report generated by the same terminal as the RLF report and the successful handover report that have an associated relationship. report on successful switchover.
  • the second network node sends the RLF report and the successful handover report to the first network node through the same interface message (the first interface message), and the radio link failure RLF report and the successful handover report sent at the same time can be compared with the target associated with the terminal.
  • the radio link failure RLF report and the successful handover report of the associated target terminal sent by the second network node may be received through at least one of the XN interface, the X2 interface, the NG interface and the S1 interface.
  • At least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message may be used to receive the radio link failure RLF report and Successful switch report.
  • the specific message is a preset message specifically used to instruct sending a radio link failure RLF report and a successful handover report.
  • the first interface message may include a report list, and the report list includes different The RLF report and the successful handover report generated by the terminal, the target terminal is one of different terminals.
  • the report list includes at least one column, and each column records the RLF report and the successful handover report corresponding to the same terminal, and the RLF report and the successful handover report of the target terminal are recorded in a column in the report list.
  • the second network node can cache the successful handover report and the RLF report generated by multiple UEs, and then simultaneously send the successful handover report and the RLF report associated with the same terminal in one interface message Report.
  • the reports of multiple UEs may be transmitted in the form of a report list, each node in the list represents a report of a UE, and each UE report includes an associated successful handover report and RLF reports.
  • step S410 obtaining a radio link failure RLF report and a successful handover report includes:
  • step S420 determining the RLF report and the successful handover report having an association relationship includes:
  • the first terminal identifier is the same as the second terminal identifier, determining the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier as the RLF report having an association relationship and the successful switch report.
  • the second network node can send the radio link failure RLF report and the successful handover report to the first network node respectively through different interface messages, and the interface messages for sending the radio link failure RLF report and the successful handover report respectively
  • the identification of the terminal is included, so that according to the identification of the terminal included in the interface message, the radio link failure RLF report and the successful handover report generated by the same terminal transmitted through different interface messages can be associated.
  • the second interface message includes a first report list, and the first report list includes an RLF report of at least one terminal;
  • the third interface message includes a second report list, and the second report list includes a successful handover report of at least one terminal.
  • the interface message may include a report list for sending a successful handover report or RLF report of at least one terminal, and in the interface message, each successful handover report or RLF report has a corresponding terminal identifier, which is used To indicate the terminal associated with each successful handover report or each RLF report respectively.
  • the second interface message and the third interface message are respectively a failure indication message and a handover report handover At least one or more of a report message, an access and mobility indication message, and a specific message.
  • the sending interfaces of the second interface message and the third interface message are respectively at least one of an XN interface, an X2 interface, an NG interface, and an S1 interface.
  • step S410 obtaining a radio link failure RLF report and a successful handover report specifically includes:
  • step S420 determining the RLF report and the successful handover report having an association relationship specifically includes:
  • the RLF report and the successful handover report with the same terminal identifier are determined as the RLF report and the successful handover report having an associated relationship.
  • the terminal when the terminal records the successful handover report and the RLF report, it adds the record of the terminal identifier, so there is no need to add the terminal identifier in the interface message sending the successful handover report or the RLF report.
  • the source network node (first network node) correlates the terminal identification in the successful handover report and the RLF report, determines the associated successful handover report and the RLF report, and performs handover failure type analysis.
  • a wireless link failure RLF report or a successful handover report may occur in a variety of different implementation scenarios.
  • the most typical failure scenario during the DAPS handover process, a wireless link failure occurs at the source network node, and the random access of the DAPS handover target network node succeeds, but RLF occurs soon, and the terminal resumes connection at another network node.
  • the scenario is taken as an example, and the specific implementation manner of steps S410 to S430 of the present disclosure, obtaining a radio link failure RLF report and a successful handover report, and determining the RLF report and the successful handover report with an association relationship are introduced in detail.
  • report transmission method described in the embodiment of the present disclosure is not limited to be applicable only to the DAPS handover process, but also can be applied to the traditional handover process, and is not limited to only being applicable to the failure scenarios illustrated below.
  • the first method is adopted, and the radio link failure RLF report and the successful handover report sent by the second network node are received through the first interface message, and the radio link failure RLF report is associated with the successful handover report.
  • the second network node when the second network node sends the radio link failure RLF report and the successful handover report through the first interface message, it also includes:
  • the second network node acquires a successful handover report sent after the target terminal is successfully handed over from the first network node to the second network node;
  • the second network node obtains the RLF report of the target terminal sent by the third network node through a failure indication message after the target terminal generates RLF at the second network node and connects to the third network node;
  • the second network node sends the RLF report and the successful handover report associated with the target terminal to the first network node through the first interface message, including:
  • the second network node correlates the successful handover report and the RLF report, and sends the RLF report and the successful handover report of the target terminal to the first network node through the same interface message.
  • the UE performs DAPS handover, and performs handover from the first network node (source network node) to the second network node (target network node);
  • a radio link failure occurs in the first network node (source network node), and the UE records a successful handover report;
  • the second network node (target network node) initiates a UE information acquisition process, and acquires a successful handover report recorded by the UE; optionally, an information request may be sent to the UE, requesting to acquire the successful handover report;
  • the UE reconnects to another network node (third network node), and the third network node obtains the RLF report recorded by the UE;
  • the third network node sends the RLF report to the second network node (target network node) through a failure indication message;
  • the second network node identifies the received RLF report, and according to the previously acquired successful handover report, identifies the RLF report and the successful handover report belonging to the same terminal, and sends the identified RLF report belonging to the same terminal.
  • the RLF report and the successful handover report are sent to the first network node (source network node) through the same interface message (first interface message), which is used to indicate that the sent RLF report and the successful handover report belong to the same terminal.
  • the second network node may identify whether the received RLF report and the successful handover report belong to the same terminal according to at least one item of location information, terminal identifier, and cell identifier in the RLF report and the successful handover report.
  • the first interface message includes a report list, and the report list includes An RLF report and a successful handover report respectively associated with at least one terminal are included, and the target terminal is one of the at least one terminal.
  • the report list includes at least one reporting node, and each reporting node records an RLF report and a successful handover report corresponding to the same terminal, and the RLF report and successful handover report of the target terminal are recorded in one of the reporting nodes.
  • the base station can cache the successful handover report and the RLF report of multiple users, and then send the successful handover report and the RLF report associated with the same terminal in one interface message at the same time.
  • the messages contains reports of multiple UEs
  • the reports of multiple UEs can be transmitted in the form of a report list, each node in the list represents a report of a UE, and each UE report contains the associated successful handover report and RLF report .
  • the sending interface of the first interface message is the XN interface, the X2 interface, the NG interface and the S1 interface at least one of the .
  • the first interface message is an XN or X2 interface, and may also be sent through an NG or S1 interface when there is no XN or X2 connection between nodes on the network side.
  • the first interface message may pass a failure indication message, a handover report message, an access and mobility indication At least one of a message and a specific message is transmitted.
  • the first network node obtains the RLF report through the second interface message, and obtains the successful handover report through the third interface message;
  • the second interface message and the third interface message respectively include the identifier of the target terminal.
  • the second network node sends the RLF report to the first network node through the second interface message, and sends the successful handover report to the first network node through the third interface message, including:
  • the second network node obtains a successful handover report sent after the target terminal is successfully handed over from the first network node to the second network node, then send a successful handover report to the first network node through a third interface message;
  • the third network node sends the RLF report of the target terminal through the failure indication message, and sends the report to the first network node through the second interface message RLF report.
  • the successful handover report and the RLF report are sent to the first network node through different interface messages, and can be sent to the source network node immediately after receiving the successful handover report, without waiting for the subsequent RLF report, and the successful handover report is sent
  • the reported interface message is associated with the interface message sending the RLF report through the included terminal identifier.
  • the UE performs DAPS handover, and performs handover from the first network node (source network node) to the second network node (target network node);
  • a radio link failure occurs in the first network node (source network node), and the UE records a successful handover report;
  • the second network node (target network node) initiates a UE information acquisition process, and acquires a successful handover report recorded by the UE; optionally, an information request may be sent to the UE, requesting to acquire the successful handover report;
  • the second network node After obtaining the successful handover report, the second network node (target network node) immediately sends the successful handover report to the first network node (source network node) through an interface message (third interface message);
  • the UE reconnects to other network nodes (third network node), and the third network node obtains the RLF report recorded by the UE;
  • the third network node sends the RLF report to the second network node (target network node) through a failure indication message;
  • the second network node sends the RLF report to the first network node (source network node) through an interface message (for example, a second interface message).
  • an interface message for example, a second interface message
  • the sent interface message includes a UE identifier, which is used to identify the successful handover Report and RLF report correspond to the same terminal.
  • the source network node may have deleted the user's context information, and the user's context information cannot be obtained according to the UE ID, but according to the UE ID included in the interface message, the RLF can be sent in association
  • the second interface message includes a first report list, and the first report list includes an RLF report of at least one terminal;
  • the third interface message includes a second report list, and the second report list includes a successful handover report of at least one terminal;
  • the target terminal is one of at least one terminal.
  • the interface message may include a report list for sending a successful handover report or RLF report of at least one terminal, and in the interface message, each successful handover report or RLF report has a corresponding terminal identifier, which is used To indicate the terminal associated with each successful handover report or each RLF report respectively.
  • the second network node when the second network node sends the RLF report to the first network node through the second interface message, and sends the handover success report to the first network node through the third interface message, the second interface message and The third interface message may be transmitted by at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message.
  • the sending interfaces of the second interface message and the third interface message are respectively At least one of the XN interface, the X2 interface, the NG interface and the S1 interface.
  • the second interface message and the third interface message are XN interface or X2 interface respectively, and may also be sent through NG interface or S1 interface when there is no XN interface or X2 connection between nodes on the network side.
  • both methods require the target network node to recognize that the successful handover report and the RLF report belong to the same terminal.
  • the target network node can immediately send the report to the source network node after receiving the successful handover report, without waiting for the subsequent RLF report; optionally, based on this embodiment, the source network node After receiving the successful handover report, it is not limited to immediately perform handover analysis and optimization, but needs to wait to confirm whether there is a subsequent RLF report.
  • the second network node uses Mode 3, 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, wherein the RLF report and The successful handover reports respectively include the identifiers of the target terminals.
  • the switching process during the specific implementation of this embodiment may be the same as that of the second embodiment.
  • the following continues the implementation process shown in FIG. 6 to illustrate the specific implementation of the third method:
  • the specific implementation process of the third embodiment includes steps:
  • the UE performs DAPS handover, and performs handover from the first network node (source network node) to the second network node (target network node);
  • a radio link failure occurs in the first network node (source network node), and the UE records a successful handover report;
  • the second network node initiates a UE information acquisition process to acquire a successful handover report recorded by the UE; wherein, in this embodiment, the successful handover report recorded by the UE includes the terminal identifier, so the The acquired successful handover report includes the terminal identifier;
  • an information request may be sent to the UE, requesting to obtain the successful handover report
  • the second network node After obtaining the successful handover report, the second network node (target network node) immediately sends the successful handover report to the first network node (source network node) through an interface message (third interface message);
  • a radio link failure occurs in the second network node (target network node), and the UE records the RLF report; in this embodiment, the terminal identifier is included in the RLF report recorded by the UE;
  • the UE reconnects to another network node (third network node), and the third network node obtains the RLF report recorded by the UE;
  • the third network node sends the RLF report to the second network node (target network node) through a failure indication message;
  • the second network node sends the RLF report to the first network node (source network node) through an interface message (for example, a second interface message).
  • an interface message for example, a second interface message
  • the record of the terminal ID is added, so there is no need to add the terminal ID in the interface message sending the successful handover report or the RLF report.
  • the source network node after receiving the successful handover report and the RLF report, correlates the terminal identification in the successful handover report and the RLF report, determines the associated successful handover report and RLF report, and analyzes the type of handover failure.
  • the second interface message includes the first report list , the first report list includes an RLF report of at least one terminal;
  • the third interface message includes a second report list, and the second report list includes at least one successful handover of the terminal Report;
  • the target terminal is one of at least one terminal.
  • the interface message may include a report list, which is used to send a successful handover report or an RLF report of at least one terminal, and each successful handover report and RLF report includes a corresponding terminal identifier, which is used to indicate that each The terminal to which the successful handover report or each RLF report is associated respectively.
  • the second 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.
  • the sending interfaces of the second interface message and the third interface message are respectively At least one of the XN interface, the X2 interface, the NG interface and the S1 interface.
  • the second interface message and the third interface message are XN interface or X2 interface respectively, and may also be sent through NG interface or S1 interface when there is no XN interface or X2 connection between nodes on the network side.
  • the network nodes when the network nodes transmit the radio link failure RLF report and the successful handover report, the RLF report and the successful handover report that belong to the same terminal are sent Correlating, so that the network node can jointly analyze the successful handover report and the RLF report belonging to the same terminal, to ensure that the cause of handover failure can be correctly analyzed, the network node can accurately analyze the failure type, and effectively optimize the handover parameters.
  • Another embodiment of the present disclosure provides a method for processing a report, which is applied to a second network node. As shown in FIG. 7 , the method includes:
  • S720 Send the associated RLF report and the successful handover report to the first network node, so that the first network node analyzes the cause of the radio link failure or the handover failure according to the associated RLF report and the successful handover report .
  • the network nodes transmit the radio link failure RLF report and the successful handover report
  • the RLF report and the successful handover report sent by the same terminal are associated, so that the network nodes can correctly Analyze the cause of handover failure, ensure the accuracy of failure type analysis by network nodes, and optimize handover parameters effectively.
  • the second network node is the node after the terminal performs the DAPS switching of the dual activation protocol stack
  • the first network node is the node before the terminal performs the DAPS switching
  • the RLF report is the The second network node obtains it from other network nodes
  • the other network nodes are the network nodes to which the terminal reconnects after RLF occurs after the DAPS handover succeeds.
  • step S710 obtain a successful handover report, specifically including:
  • the RLF report is generated by the terminal after the RLF occurs after the DAPS switch of the dual-activation protocol stack is successful.
  • the other network nodes are the RLF of the terminal after the DAPS switch is successful, and then reconnect to the network node.
  • the report processing method in step S720, sends the associated RLF report and the successful handover report to the first network node, specifically including:
  • step S720 the associated RLF report and the successful handover report are sent to the first network node in one of the following ways:
  • Mode 1 sending the RLF report and the successful handover report of the associated terminal to the first network node through the first interface message;
  • Mode 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 identification of the terminal;
  • Method 3 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 RLF report and the successful handover report include the terminal logo.
  • the second network node can send a radio link failure RLF report and a successful handover report to the first network node at the same time in the same interface message (first interface message), and
  • the radio link failure RLF report and the successful handover report sent at the same time can be associated with the terminal;
  • 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, and the interface messages for sending the radio link failure RLF report and the successful handover report respectively include The identification of the target terminal, so that according to the identification of the target terminal included in the interface message, the radio link failure RLF report and the successful handover report corresponding to the same target terminal in the interface message can be associated;
  • 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, and the sent radio link failure RLF report and successful handover report include respectively Terminal identification, so that according to the terminal identification, the radio link failure RLF report and the successful handover report corresponding to the same terminal can be identified;
  • the terminal identifier is written into the generated radio link failure RLF report and the successful handover report, that is, compared In the related technology, air interface transmission content is modified, and a wireless link failure RLF report or a successful handover report including the terminal identifier is sent to the network node.
  • the radio link failure RLF report and the successful handover report associated with the target terminal may be sent to the first network node through at least one of the XN interface, the X2 interface, the NG interface and the S1 interface.
  • the radio link associated with the target terminal may be sent to the first network node through at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message. Failed RLF report and successful switch report.
  • the specific message is a preset message specifically used to instruct sending a radio link failure RLF report and a successful handover report.
  • Another embodiment of the present disclosure further provides a report processing method, as shown in FIG. 8, which is applied to a terminal device, and the method includes:
  • RLF report carries the terminal identifier and the successful handover report carries the terminal identifier, and the successful handover report is after the terminal device successfully switches the dual-activation protocol stack DAPS Generated, the RLF report is generated after the terminal RLF occurs after the DAPS handover is successful;
  • the terminal when the terminal records the successful handover report and the RLF report, the record of the terminal identification is added, and there is no need to add the terminal identification in the interface message for sending the successful handover report or the RLF report, so that network nodes transmit wireless link
  • the failed RLF report and the successful handover report are reported, according to the terminal ID in the successful handover report and the terminal ID in the RLF report, the RLF report of the same terminal is associated with the successful handover report, so that the network node can correctly analyze the cause of the handover failure and ensure that the network The accuracy of the failure type analysis of the node, and the effective handover parameter optimization.
  • the content information included in the RLF report and the successful handover report respectively, and the specific process of transmitting the RLF report and the successful handover report between network nodes can be combined with FIG. 1 to FIG. 3 , and refer to the above detailed description, It will not be described in detail here.
  • the report processing method described in one embodiment of the present disclosure is executed by the second network node, and the method includes:
  • the second network node when the second network node sends the radio link failure RLF report and the successful handover report to the first network node, it is associated with the target terminal, that is, it can indicate the radio link failure RLF report and the successful handover report are associated with the same target terminal, so that the first network node performs failure type analysis according to the associated radio link failure RLF report and successful handover report, so as to ensure the accuracy of the failure type analysis by the network node and avoid analysis error types, and can effectively optimize the switching parameters.
  • the radio link failure RLF report and the successful handover report of the associated target terminal are sent to the first network node in one of the following ways:
  • Mode 1 sending an RLF report and a successful handover report associated with the target terminal to the first network node through the first interface message;
  • Mode 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 identification of the target terminal;
  • Mode 3 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 RLF report and the successful handover report respectively include the target The identity of the terminal.
  • the second network node is a node after the terminal performs a dual-activation protocol stack DAPS switching
  • the first network node is a node before the terminal performs DAPS switching
  • the RLF report is the The second network node obtains it from other network nodes
  • the other network nodes are the network nodes to which the terminal reconnects after RLF occurs after the DAPS handover succeeds.
  • the second network node can send a radio link failure RLF report and a successful handover report to the first network node at the same time in the same interface message (first interface message), and
  • the radio link failure RLF report and the successful handover report sent at the same time can be associated with the target terminal;
  • the second network node may send a radio link failure RLF report and a successful handover report to the first network node through different interface messages, and the interface messages for sending the radio link failure RLF report and the successful handover report respectively include The identification of the target terminal, so that according to the identification of the target terminal included in the interface message, the radio link failure RLF report and the successful handover report corresponding to the same target terminal in the interface message can be associated;
  • 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, and the sent radio link failure RLF report and successful handover report include respectively The identification of the target terminal, so according to the identification of the target terminal, the radio link failure RLF report and the successful handover report corresponding to the same target terminal can be made; adopting this embodiment, optionally, the radio link failure RLF report and the radio link failure report are generated at the target terminal When the handover report is successful, the identification of the target terminal is written into the generated radio link failure RLF report and the successful handover report. Route failure RLF report or successful handover report is sent to the network node.
  • the radio link failure RLF report and the successful handover report associated with the target terminal may be sent to the first network node through at least one of the XN interface, the X2 interface, the NG interface and the S1 interface.
  • the radio link failure RLF associated with the target terminal may be sent to the first network node through at least one of a failure indication message, a handover report message, an access and mobility indication message, and a specific message. Reports and Successful Switch Reports.
  • the specific message is a preset message specifically used to instruct sending a radio link failure RLF report and a successful handover report.
  • the network nodes when the network nodes transmit the radio link failure RLF report and the successful handover report, the RLF report and the successful handover report that belong to the same terminal are sent Correlating, so that the network node can jointly analyze the successful handover report and the RLF report belonging to the same terminal, to ensure that the cause of handover failure can be correctly analyzed, the network node can accurately analyze the failure type, and effectively optimize the handover parameters.
  • Another implementation manner of the embodiment of the present disclosure also provides a report processing method, executed by the first network node, the method including:
  • the cause of the radio link failure or the handover failure is analyzed.
  • the second network node when the second network node sends the radio link failure RLF report and the successful handover report to the first network node, it is associated with the target terminal, that is, it can indicate the radio link failure RLF report and the successful handover report are associated with the same target terminal, so that the first network node performs failure type analysis according to the associated radio link failure RLF report and successful handover report, so as to ensure the accuracy of the failure type analysis by the network node and avoid analysis error types, and can effectively optimize the switching parameters.
  • the radio link failure RLF report and the successful handover report of the associated target terminal are obtained through one of the following methods:
  • second network node, third network node, and fourth network node are respectively network nodes capable of sending an RLF report or a successful handover report to the first network node, and the names are only used to distinguish different network nodes. Specifically, they may be the same or different network nodes.
  • the second An interface message includes a report list
  • the report list includes an RLF report and a successful handover report respectively associated with at least one terminal
  • the target terminal is one of the at least one terminal.
  • the second interface message in the case where the RLF report transmitted by the third network node is obtained through the second interface message, the second interface message includes a first report list, and the first report The list includes at least one terminal's RLF report;
  • the third interface message includes a second report list, and the second report list includes a successful handover report of at least one terminal;
  • the target terminal is one of at least one terminal.
  • the first interface message, the second interface message and the third interface message respectively pass a failure indication message, a handover report message, an access and a mobility At least one of an indication message and a specific message is transmitted.
  • the sending interfaces of the first interface message, the second interface message and the third interface message are XN interface, X2 interface, NG interface and S1 interface at least one.
  • the first network node is a source network node of the target terminal
  • the second network node is a target network node of the target terminal
  • the first network node is a source network node of the target terminal
  • the third network node and the fourth network node are one of the following:
  • a network node other than a source network node and a destination network node is not limited to a source network node and a destination network node.
  • the network nodes that send the RLF report and the successful handover report are respectively used as target network nodes for illustration.
  • the method described in the embodiments of the present disclosure The application scenario is not limited to the scenarios shown in Figure 5 and Figure 6, and the network node that can send the RLF report or the successful handover report to the source network node is not limited to only the target network node, and can also be any of the network nodes listed above any of them.
  • the report processing method wherein, according to the determined associated RLF report and the successful handover report, analyzing the cause of the radio link failure or the cause of the handover failure includes:
  • the cause of the radio link failure or the handover failure is one of too late handover, too early handover, and handover to a wrong cell.
  • an embodiment of the present disclosure also provides a network node.
  • the network node is a first network node, including a processor 900, a transceiver 910, a memory 920, and a The program running on the processor 900; wherein, the transceiver 910 is connected with 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;
  • processor 900 is used to read the program in the memory and execute the following process:
  • the processor 900 acquires a radio link failure RLF report and a successful handover report, including:
  • Radio link failure RLF report and a successful handover report sent by a second network node through a first interface message wherein the second network node is a node after the terminal performs a dual-activation protocol stack DAPS handover, and the first network node is the node before the terminal performs DAPS handover, the RLF report is obtained by the second network node from other network nodes, and the other network node is that the terminal has RLF after the DAPS handover is successful, and then reconnects to network node;
  • Determining the RLF report and the successful handover report having an association relationship includes:
  • the processor 900 determines a radio link failure RLF report and a successful handover report transmitted in the first interface message as the RLF report and the RLF report having an association relationship.
  • one of the first interface messages carries a radio link failure RLF report and a successful handover report generated by different terminals, then determine the RLF report and the successful handover report generated by the same terminal as the RLF report and the successful handover report that have an associated relationship. report on successful switchover.
  • the processor 900 acquires a radio link failure RLF report and a successful handover report, including:
  • Determining the RLF report and the successful handover report having an association relationship includes:
  • the first terminal identifier is the same as the second terminal identifier, determining the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier as the RLF report having an association relationship and the successful switch report.
  • the network node wherein, the first interface message, the second interface message and the third interface message are respectively a failure indication message, a handover report message, an access and mobility indication At least one or more of message and specific message.
  • the network node wherein the processor 900 acquires a radio link failure RLF report and a successful handover report specifically includes:
  • the acquisition terminal sends a wireless link failure RLF report and a successful handover report, wherein the RLF report carries the terminal identifier and the successful handover report carries the terminal identifier;
  • Determining the RLF report and the successful handover report having an association relationship specifically includes:
  • the RLF report and the successful handover report with the same terminal identifier are determined as the RLF report and the successful handover report having an associated relationship.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 900 and various circuits of the memory represented by the memory 920 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein.
  • the bus interface provides the interface.
  • Transceiver 910 may be a plurality of elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical cables, and other transmission media.
  • the processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 can store data used by the processor 900 when performing operations.
  • the processor 900 may be a central processing unit (Central Processing Unit, CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • the above-mentioned network node provided by the embodiment of the present disclosure can realize all the method steps corresponding to the first network node in the above-mentioned method embodiment, and can achieve the same technical effect.
  • the same parts and beneficial effects as those in the method embodiment will be described in detail.
  • An embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored, wherein, when the computer program is executed by a processor, the steps of the report processing method applied to the above-mentioned network node (first network node) are realized .
  • the processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (Magneto-Optical Disk, MO) etc.
  • optical storage such as compact disc (Compact Disk, CD), digital video disc (Digital Versatile Disc, DVD), Blu-ray Disc (Blu-ray Disc, BD), high-definition universal disc (High-Definition Versatile Disc, HVD), etc.
  • semiconductor memory such as read-only memory (Read-Only Memory, ROM), erasable programmable read-only memory (Erasable Programmable ROM, EPROM), charged erasable programmable read-only memory (Electrically EPROM, EEPROM), non- Volatile memory (NAND FLASH), solid state disk (Solid State Disk or Solid State Drive, SSD)), etc.
  • an embodiment of the present disclosure also provides a network node.
  • the network node is a second network node, including a processor 1000, a transceiver 1010, a memory 1020, and a The program running on the processor 1000; wherein, the transceiver 1010 is connected with 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;
  • the processor 1000 is used to read the program in the memory, and execute the following process:
  • the network node, wherein the processor 1000 obtains a successful handover report specifically includes:
  • the RLF report is generated by the terminal after the RLF occurs after the DAPS switch of the dual-activation protocol stack is successful.
  • the other network nodes are the RLF of the terminal after the DAPS switch is successful, and then reconnect to the network node.
  • the network node, wherein the processor 1000 sends the associated RLF report and the successful handover report to the first network node specifically includes:
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1000 and various circuits of the memory represented by the memory 1020 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 1010 may be a plurality of elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical cables, and other transmission media.
  • the processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 can store data used by the processor 1000 when performing operations.
  • the processor 1000 can be a central processing unit (Central Processing Unit, CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • the above-mentioned network node provided by the embodiment of the present disclosure can realize all the method steps corresponding to the second network node in the above-mentioned method embodiment, and can achieve the same technical effect.
  • the same parts and beneficial effects as those in the method embodiment will be described in detail.
  • An embodiment of the present disclosure also provides a computer-readable storage medium on which a computer program is stored, wherein, when the computer program is executed by a processor, the steps of the report processing method applied to the above-mentioned network node (second network node) are realized .
  • the processor-readable storage medium can be any available medium or data storage device that can be accessed by a 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 memory (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.
  • magnetic storage e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.
  • optical storage e.g., CD, DVD, BD, HVD, etc.
  • semiconductor memory such as ROM
  • an embodiment of the present disclosure 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 through a bus interface, 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, execute The following process:
  • 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 the dual activation protocol stack DAPS handover is successful
  • the RLF report is generated by the terminal after RLF occurs after the DAPS handover is successful
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1100 and various circuits of the memory represented by the memory 1120 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein.
  • the bus interface provides the interface.
  • Transceiver 1110 may be a plurality of elements, including a transmitter and a receiver, providing means for communicating with various other devices over transmission media, including wireless channels, wired channels, fiber optic cables, etc. Transmission medium.
  • the user interface 1130 may also be an interface capable of connecting externally and internally to required equipment, and the connected equipment includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1100 when performing operations.
  • the processor 1100 may be a central processing unit (Central Processing Unit, CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable Logic device (Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • An embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored, wherein when the computer program is executed by a processor, the steps of the report processing method applied to the above-mentioned terminal are realized.
  • the processor-readable storage medium can be any available medium or data storage device that can be accessed by a 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 memory (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.
  • An embodiment of the present disclosure also provides a report processing apparatus, which is executed by a first network node.
  • the report processing apparatus 1200 includes:
  • the first report acquiring module 1210 is configured to acquire a radio link failure RLF report and a successful handover report;
  • a determining module 1220 configured to determine the RLF report and the successful handover report having an association relationship
  • the analysis module 1230 is configured to analyze the cause of the radio link failure or the cause of the handover failure according to the determined RLF report and the successful handover report having an associated relationship.
  • the report processing device wherein the first report obtaining module 1210 obtains a radio link failure RLF report and a successful handover report, including:
  • Radio link failure RLF report and a successful handover report sent by a second network node through a first interface message wherein the second network node is a node after the terminal performs a dual-activation protocol stack DAPS handover, and the first network node is the node before the terminal performs DAPS handover, the RLF report is obtained by the second network node from other network nodes, and the other network node is that the terminal has RLF after the DAPS handover is successful, and then reconnects to network node;
  • the determining module 1220 determines the RLF report and the successful handover report having an association relationship, including:
  • the determining module 1220 determines a radio link failure RLF report and a successful handover report transmitted in the first interface message as the RLF report and the Successful switch reports, including:
  • one of the first interface messages carries a radio link failure RLF report and a successful handover report generated by different terminals, then determine the RLF report and the successful handover report generated by the same terminal as the RLF report and the successful handover report that have an associated relationship. report on successful switchover.
  • the first report obtaining module 1210 obtains a radio link failure RLF report and a successful handover report, including:
  • the determining module 1220 determines the RLF report and the successful handover report having an association relationship, including:
  • the first terminal identifier is the same as the second terminal identifier, determining the RLF report corresponding to the first terminal identifier and the successful handover report corresponding to the second terminal identifier as the RLF report having an association relationship and the successful switch report.
  • the first interface message, the second interface message and the third interface message are respectively a failure indication message, a handover report message, an access and mobility At least one or more of an indication message and a specific message.
  • the first report obtaining module 1210 obtains a radio link failure RLF report and a successful handover report, specifically including:
  • the determining module 1220 determines the RLF report and the successful handover report having an association relationship, specifically including:
  • the RLF report and the successful handover report with the same terminal identifier are determined as the RLF report and the successful handover report having an associated relationship.
  • An embodiment of the present disclosure also provides a report processing apparatus, which is executed by a second network node.
  • the report processing apparatus 1300 includes:
  • the second report obtaining module 1310 is used to obtain a radio link failure RLF report and a successful handover report;
  • the first sending module 1320 is configured to send the associated RLF report and the successful handover report to the first network node, so that the first network node analyzes the wireless link according to the associated RLF report and the successful handover report Failure reason or switch failure reason.
  • the second report obtaining module 1310 obtains a successful handover report, specifically includes:
  • the second report acquiring module 1310 acquires a radio link failure RLF report, specifically including:
  • the RLF report is generated by the terminal after the RLF occurs after the DAPS switch of the dual-activation protocol stack is successful.
  • the other network nodes are the RLF of the terminal after the DAPS switch is successful, and then reconnect to the network node.
  • the report processing apparatus wherein the first sending module 1320 sends the associated RLF report and the successful handover report to the first network node, specifically includes:
  • An embodiment of the present disclosure also provides a report processing apparatus, as shown in FIG. 14 , which is applied to a terminal.
  • the report processing apparatus 1400 includes:
  • the report generating module 1410 is configured 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, and the successful handover report is the terminal device in the dual activation protocol Generated after stack DAPS switching is successful, the RLF report is generated by the terminal after RLF occurs after DAPS switching is successful;
  • the second sending module 1420 is configured to send the generated radio link failure RLF report and successful handover report to the network device.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is implemented in the form of a software function unit and sold or used as an independent product, it can be stored in a processor-readable storage medium.
  • the essence of the technical solution of the present disclosure or the part that contributes to the related technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • a processor processor
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .
  • this embodiment of the report transmission device is a one-to-one corresponding device with the above-mentioned method embodiment, and all the implementation methods in the above-mentioned method embodiment are applicable to the embodiment of the report transmission device, and can also achieve the same technical effect .
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is implemented in the form of a software function unit and sold or used as an independent product, it can be stored in a processor-readable storage medium.
  • the essence of the technical solution of the present disclosure or the part that contributes to the related technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • a processor processor
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .
  • the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Accordingly, the present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) having computer-usable program code embodied therein.
  • processor-executable instructions may also be stored in a processor-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the processor-readable memory produce a manufacturing product, the instruction device realizes the functions specified in one or more procedures of the flow chart and/or one or more blocks of the block diagram.
  • processor-executable instructions 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
  • the executed instructions provide steps for implementing the functions specified in the procedure or procedures of the flowchart and/or the block or blocks of the block diagrams.
  • the division of the above modules is only a division of logical functions, and may be fully or partially integrated into a physical entity or physically separated during actual implementation.
  • these modules can all be implemented in the form of calling software through processing elements; they can also be implemented in the form of hardware; some modules can also be implemented in the form of calling software through processing elements, and some modules can be implemented in the form of hardware.
  • the determining module may be a separate processing element, or may be integrated in a chip of the above-mentioned device.
  • it may be stored in the memory of the above-mentioned device in the form of program code, and a certain processing element of the above-mentioned device may Call and execute the functions of the modules identified above.
  • each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.
  • each module, unit, subunit or submodule may be one or more integrated circuits configured to implement the above method, for example: one or more specific integrated circuits (Application Specific Integrated Circuit, ASIC), or, one or Multiple microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA), etc.
  • ASIC Application Specific Integrated Circuit
  • DSP digital signal processor
  • FPGA Field Programmable Gate Array
  • the processing element may be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processors that can call program codes.
  • these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip

Landscapes

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

Abstract

本公开实施例提供一种报告处理方法、装置、网络节点及终端。所述方法包括：获取无线链路失败RLF报告和成功切换报告；确定具有关联关系的所述RLF报告和所述成功切换报告；根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。

Description

报告处理方法、装置、网络节点及终端
相关申请的交叉引用
本公开主张在2021年08月05日在中国提交的中国专利申请号No.202110895728.5的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及无线技术领域，特别涉及一种报告处理方法、装置、网络节点及终端。
背景技术
在双激活协议栈(Dual Active Protocol Stack，DAPS)切换过程中，可能在源侧发生无线链路失败之后又成功切换到目标侧，那么源侧的无线链路失败信息将记录在成功切换报告中，并使用接入和移动性指示(Access and mobility indication)消息在网络节点间进行传递；也可能在切换后的目标侧发生随机接入失败或者随机接入成功后又发生无线链路失败，那么目标侧的无线链路失败信息将记录在无线链路失败(Radio Link Failure，RLF)报告中，并使用失败指示(failure indication)消息在网络节点间进行传递。其中，源测为终端执行DAPS切换前的节点，目标测为终端执行双激活协议栈DAPS切换后的节点。
作为DAPS切换场景下的源侧的网络节点，可以通过Access and mobility indication消息和failure indication消息收到成功切换报告和RLF报告，进而对成功切换报告和RLF报告进行分析，经研究发现在根据接收的成功切换报告和RLF报告分析失败类型方面存在分析结果不准确的问题。
发明内容
本公开实施例提供一种报告处理方法、装置、网络节点及终端，用于解决上述记载的至少一个技术问题。
本公开其中一实施例还提供一种报告处理方法，其中，应用于终端设备， 所述方法包括：
生成无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
将生成的所述无线链路失败RLF报告和成功切换报告发送给网络设备。
本公开还提供另一实施的报告处理方法，其中，由第一网络节点执行，所述方法包括：
获取无线链路失败RLF报告和成功切换报告；
确定具有关联关系的所述RLF报告和所述成功切换报告；
根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的报告处理方法，其中，获取无线链路失败RLF报告和成功切换报告，包括：
通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，其中，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点；
确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理方法，其中，将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告，包括：
若一个所述第一接口消息中携带不同终端生成的无线链路失败RLF报告和成功切换报告，则将同一个终端生成的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理方法，其中，获取无线链路失败RLF报告和成 功切换报告，包括：
分别通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
根据所述第二接口消息中携带的第一终端标识，确定所述第一终端标识对应的RLF报告，以及根据所述第三接口消息中携带的第二终端标识，确定所述第二终端标识对应的成功切换报告；
若所述第一终端标识与所述第二终端标识相同，则将所述第一终端标识对应的RLF报告和所述第二终端标识对应的成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理方法，其中，所述第一接口消息、所述第二接口消息和所述第三接口消息分别为失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少一种或者多种。
可选地，所述的报告处理方法，其中，获取无线链路失败RLF报告和成功切换报告，具体包括：
获取终端发送的无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和所述成功切换报告中携带终端标识；
确定具有关联关系的所述RLF报告和所述成功切换报告，具体包括：
根据所述RLF报告中携带终端标识和成功切换报告中携带终端标识，将所述终端标识相同的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
本公开还提供另一实施的报告处理方法，其中，应用于第二网络节点，所述方法包括：
获取无线链路失败RLF报告和成功切换报告；
将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的报告处理方法，其中，获取成功切换报告，具体包括：
接收终端发送的成功切换报告，所述成功切换报告为所述终端在DAPS 切换成功后生成的；
获取无线链路失败RLF报告，具体包括：
接收其他网络节点发送的RLF报告，所述RLF报告为终端在双激活协议栈DAPS切换成功后又发生RLF后生成的，所述其他网络节点为终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。
可选地，所述的报告处理方法，其中，将相关联的RLF报告和成功切换报告发送给第一网络节点，具体包括：
识别具有关联关系的所述RLF报告和所述成功切换报告，所述具有关联关系的所述RLF报告和所述成功切换报告为同一个终端生成；
将识别出的具有关联关系的所述RLF报告和所述成功切换报告发送给第一网络节点。
本公开实施例还提供一种终端，其中，包括存储器、收发机和处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
生成无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
将生成的所述无线链路失败RLF报告和成功切换报告发送给网络设备。
本公开实施例还提供一种网络节点，所述网络节点为第一网络节点，其中，包括存储器、收发机和处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
获取无线链路失败RLF报告和成功切换报告；
确定具有关联关系的所述RLF报告和所述成功切换报告；
根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的网络节点，其中，所述处理器获取无线链路失败RLF报告和成功切换报告，包括：
通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，其中，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点；
确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的网络节点，其中，所述处理器将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告，包括：
若一个所述第一接口消息中携带不同终端生成的无线链路失败RLF报告和成功切换报告，则将同一个终端生成的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的网络节点，其中，所述处理器获取无线链路失败RLF报告和成功切换报告，包括：
分别通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
根据所述第二接口消息中携带的第一终端标识，确定所述第一终端标识对应的RLF报告，以及根据所述第三接口消息中携带的第二终端标识，确定所述第二终端标识对应的成功切换报告；
若所述第一终端标识与所述第二终端标识相同，则将所述第一终端标识对应的RLF报告和所述第二终端标识对应的成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的网络节点，其中，所述第一接口消息、所述第二接口消息和所述第三接口消息分别为失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少一种或者多种。
可选地，所述的网络节点，其中，所述处理器获取无线链路失败RLF报 告和成功切换报告，具体包括：
获取终端发送的无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识；
确定具有关联关系的所述RLF报告和所述成功切换报告，具体包括：
根据所述RLF报告中携带终端标识和成功切换报告中携带终端标识，将所述终端标识相同的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
本公开实施例还提供一种网络节点，所述网络节点为第二网络节点，其中，包括存储器、收发机和处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
获取无线链路失败RLF报告和成功切换报告；
将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的网络节点，其中，所述处理器获取成功切换报告，具体包括：
接收终端发送的成功切换报告，所述成功切换报告为所述终端在DAPS切换成功后生成的；
所述处理器获取无线链路失败RLF报告，具体包括：
接收其他网络节点发送的RLF报告，所述RLF报告为终端在双激活协议栈DAPS切换成功后又发生RLF后生成的，所述其他网络节点为终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。
可选地，所述网络节点，其中，所述处理器将相关联的RLF报告和成功切换报告发送给第一网络节点，具体包括：
识别具有关联关系的所述RLF报告和所述成功切换报告，所述具有关联关系的所述RLF报告和所述成功切换报告为同一个终端生成；
将识别出的具有关联关系的所述RLF报告和所述成功切换报告发送给第一网络节点。
本公开实施例还提供一种报告处理装置，其中，应用于终端，所述装置包括：
报告生成模块，用于生成无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
第二发送模块，用于将生成的所述无线链路失败RLF报告和成功切换报告发送给网络设备。
本公开实施例还提供一种报告处理装置，其中，应用于第一网络节点执行，所述装置包括：
第一报告获取模块，用于获取无线链路失败RLF报告和成功切换报告；
确定模块，用于确定具有关联关系的所述RLF报告和所述成功切换报告；
分析模块，用于根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的报告处理装置，其中，第一报告获取模块获取无线链路失败RLF报告和成功切换报告，包括：
通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，其中，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点；
确定模块确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理装置，其中，确定模块将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告，包括：
若一个所述第一接口消息中携带不同终端生成的无线链路失败RLF报告和成功切换报告，则将同一个终端生成的RLF报告和成功切换报告确定为具 有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理装置，其中，第一报告获取模块获取无线链路失败RLF报告和成功切换报告，包括：
分别通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
确定模块确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
根据所述第二接口消息中携带的第一终端标识，确定所述第一终端标识对应的RLF报告，以及根据所述第三接口消息中携带的第二终端标识，确定所述第二终端标识对应的成功切换报告；
若所述第一终端标识与所述第二终端标识相同，则将所述第一终端标识对应的RLF报告和所述第二终端标识对应的成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理装置，其中，所述第一接口消息、所述第二接口消息和所述第三接口消息分别为失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少一种或者多种。
可选地，所述的报告处理装置，其中，第一报告获取模块获取无线链路失败RLF报告和成功切换报告，具体包括：
获取终端发送的无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和所述成功切换报告中携带终端标识；
确定模块确定具有关联关系的所述RLF报告和所述成功切换报告，具体包括：
根据所述RLF报告中携带终端标识和成功切换报告中携带终端标识，将所述终端标识相同的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
本公开实施例还提供一种报告处理装置，其中，应用于第二网络节点执行，所述装置包括：
第二报告获取模块，用于获取无线链路失败RLF报告和成功切换报告；
第一发送模块，用于将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告， 分析无线链路失败原因或者切换失败原因。
可选地，所述的报告处理装置，其中，第二报告获取模块获取成功切换报告，具体包括：
接收终端发送的成功切换报告，所述成功切换报告为所述终端在DAPS切换成功后生成的；
第二报告获取模块获取无线链路失败RLF报告，具体包括：
接收其他网络节点发送的RLF报告，所述RLF报告为终端在双激活协议栈DAPS切换成功后又发生RLF后生成的，所述其他网络节点为终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。
可选地，所述的报告处理装置，其中，第一发送模块将相关联的RLF报告和成功切换报告发送给第一网络节点，具体包括：
识别具有关联关系的所述RLF报告和所述成功切换报告，所述具有关联关系的所述RLF报告和所述成功切换报告为同一个终端生成；
将识别出的具有关联关系的所述RLF报告和所述成功切换报告发送给第一网络节点。
本公开实施例还提供一种处理器可读存储介质，其中，所述处理器可读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行如上一项所述的报告处理方法。
本公开实施例还提供一种计算机可读存储介质，其中，所述计算机可读存储介质存储有计算机程序，所述计算机程序用于使所述计算机执行如上一项所述的报告处理方法。
本公开实施例还提供一种通信设备，其中，所述通信设备中存储有计算机程序，所述计算机程序用于使所述通信设备执行如上一项所述的报告处理方法。
本公开的有益效果是：
采用本公开实施例所述报告处理方法，网络节点之间在传输无线链路失败RLF报告和成功切换报告时，使所发送的属于同一终端的RLF报告和成功切换报告相关联，以使网络节点可以正确分析切换失败原因，保证网络节点对失败类型分析的准确性，进行有效的切换参数优化。
附图说明
为了更清楚地说明本公开实施例或相关技术中的技术方案，下面将对实施例或相关技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1表示适用于本公开实施例所述方法的一种切换流程的示意图；
图2表示适用于本公开实施例所述方法的另一种切换流程的示意图；
图3表示切换报告(handover report)消息传输流程的示意图
图4表示本公开实施例一所述报告处理方法的流程示意图；
图5表示采用本公开实施例所述方法的实施流程之一；
图6表示采用本公开实施例所述方法的实施流程之二；
图7表示本公开实施例二所述报告处理方法的流程示意图；
图8表示本公开实施例三所述报告处理方法的流程示意图；
图9表示本公开其中一实施例所述网络节点的结构示意图；
图10表示本公开另一实施例所述网络节点的结构示意图；
图11表示本公开实施例所述终端的结构示意图；
图12表示本公开实施例一所述报告处理装置的结构示意图；
图13表示本公开实施例二所述报告处理装置的结构示意图；
图14表示本公开实施例三所述报告处理装置的结构示意图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的 数据在适当情况下可以互换，以便这里描述的本公开的实施例，例如除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本公开实施例中术语“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。本公开实施例中术语“多个”是指两个或两个以上，其它量词与之类似。
在本公开实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本公开实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本公开实施例提供的报告处理方法、装置、网络节点及终端可以应用于无线通信系统中。该无线通信系统可以为采用第五代(5th Generation，5G)移动通信技术的系统(以下均简称为5G系统)，所述领域技术人员可以了解，5G新空口(New Radio，NR)系统仅为示例，不为限制。
为清楚说明本公开实施例所述报告处理方法的技术方案，以下先对本公开所述报告处理方法所应用的切换流程进行说明。
本公开所述报告处理方法可以应用于传统切换流程和DAPS切换流程。
如图1所示传统切换流程的过程示意图，该传统切换流程包括：
步骤1，网络节点1与网络节点2之间传输切换请求和切换响应，使终端(用户设备(User Equipment，UE))从网络节点1(源网络节点)切换至网络节点2(目标网络节点)；
步骤2，网络节点1向UE发送同步重配置消息，使UE立即执行切换，与网络节点1之间断开，向网络节点2随机接入；
步骤3，UE与网络节点2之间的随机接入完成，向网络节点2发送切换完成消息；
步骤4，网络节点2向网络节点1发送上下文释放消息，通知网络节点1释放UE上下文。
如图2所示为DAPS切换流程的过程示意图，该DAPS切换流程包括：
步骤1，在源网络节点与UE之间保持数据传输链路的过程中，源网络节点向目标网络节点发送切换请求；
步骤2，目标网络节点向源网络节点发送请求确认消息；
步骤3，源网络节点向UE发送切换指示；
步骤4，UE向目标网络节点执行接入过程；
步骤5，UE在完成无线资源控制(Radio Resource Control，RRC)重配后，向目标网络节点发送RRC连接重配完成消息；
通过上述的步骤1至步骤5，源网络节点与UE之间一直保持原来的数据传输链路；对于目标网络节点接收到来自源网络节点的切换指示，且又接收到来自UE的RRC连接重配完成消息后，则如果缓冲区中有待发的下行分组数据汇聚协议((Packet Data Convergence Protocol，PDCP)数据包(采用新的安全上下文加密或完整性保护处理的数据)或控制帧，将通过所配置的与UE之间的链路发送给UE。
步骤6和步骤7，UE同时与源网络节点和目标网络节点之间维持数据的发送和接收；
步骤8，目标网络实体向UE发送释放指示，通知UE完成数据传输，期望UE释放源网络节点与UE之间的数据连接；
步骤9：UE停止源网络节点与UE之间的上行发送和下行接收，并开始释放整个源侧的主小区组(Master Cell Group，MCG)配置。
步骤10：UE仅与目标网络节点之间维持数据的发送和接收。
采用本公开实施例所述报告处理方法的上述图1和图2所示实施方式的切换流程，UE为用户设备(User Equipment，UE)，例如：可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(personal digital assistant，PDA)、移动上网装置(Mobile Internet Device，MID)或可穿戴式设备(Wearable Device)等终端侧设备。需要说明的是，在本公开实施例中并不限定用户终端11的具体类型。
网络节点(包括源网络节点、目标网络节点等)可以是基站，如为5G及以后版本的基站(例如：gNB、5G NR NB、ng-eNB等)，或者其他通信系统中的基站，或者称之为节点B，需要说明的是，在本公开实施例中仅以5G基站为例，但是并不限定网络节点的具体类型。
另外，在上述图1和图2所示实施方式的切换流程，终端侧记录RLF报告和成功切换报告。
其中，终端在发生切换失败或者RLF的情况下，会记录RLF报告。RLF报告用于至少两种场景记录：切换失败及无线链路失败，其中一次RLF报告只能表示一种场景的记录。
可选地，RLF报告包括以下至少之一的内容：
终端上一个服务小区的测量结果；
终端确认切换失败或无线链路失败后邻区测量结果；
终端位置信息；
终端失败小区标识信息，如小区全球识别码(Cell Global Identity，CGI)/物理小区识别码(Physical Cell Identity，PCI)频点；
终端重建小区标识信息；
UE上报定时器：终端上一次确认接收切换发起消息到连接失败经历的时长；
连接失败原因，切换失败或者无线链路失败；
终端连接失败时使用的小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI)；
无线链路失败子原因，T310超时或随机接入问题或者RLC层达到最大重传或者波束恢复失败(Beam Failure Recovery Failure，BFRF)；
终端确认连接失败后到终端上报该RLF报告经历的时长；
连接失败小区的跟踪区域标识(Tracking Area Code，TAC)；
蓝牙(Blue Tooth，BT)相关记录结果；
无线局域网(Wireless Local Area Network，WLAN)。
可选地，成功切换报告的记录场景包括：
传统切换过程中，在终端T310定时器、T312定时器或者T304定时器 的长度值超过预定门限时，终端记录成功切换报告；
在DAPS切换过程中，在T310定时器、T312定时器或者T304定时器的长度值超过预定门限或者原侧链路发生了RLF时，终端记录成功切换报告；
成功切换报告的内容记录了触发时刻的测量信息，小区标识信息，终端位置信息和定时器值等；
UE记录了RLF报告和/或成功切换报告后，通过在RRC连接建立完成消息、RRC连接重配置完成消息、RRC连接重建立完成消息或者RRC恢复完成消息中，向网络节点发送该RLF报告和/或成功切换报告。或者，网络节点向UE发送请求消息，UE通过响应消息，向网络节点发送RLF报告和/或成功切换报告。
另外，为解决终端移动性过程中的失败问题，可以采用移动健壮性优化(Mobility Robustness Optimisation，MRO)方式，进行辅助网络优化。
其中，终端在发生切换失败或者RLF的情况下，会记录RLF报告。终端在切换失败后进行小区选择，再通过RRC连接重建立或者RRC连接建立重新接入网络，并通知网络在终端侧保留了RLF报告，网络侧在需要时向终端获取该RLF报告，用于网络侧的网络优化。
MRO特性主要用于发现和解决移动性过程中的参数配置问题，并定义了三种失败类型，该三种失败类型包括切换过早、切换过迟和切换到错误小区。其中：
切换过迟：终端在源小区稳定驻留一段时间后，发生了无线链路失败，终端通过RRC连接重建立试图接入一个不同的小区；
切换过早：在切换过程中终端接入目标小区失败，或者接入目标小区成功但是很快发生了无线链路失败，终端发生RRC连接重建立试图接入源小区；
切换到错误小区：在切换过程中终端接入目标小区失败，或者接入目标小区成功但是很快发生了无线链路失败，终端发生RRC连接重建立试图接入不同于切换目标小区和源小区的其他小区。
在切换完成后，终端是否可以稳定驻留在目标小区是上述失败类型判断的关键。如果稳定驻留了，再发生失败就和前一次切换没有关系，因为切换完成后，UE可以稳定驻留在目标小区了。如果没有稳定驻留，可能为前一次 切换导致，例如目标小区选择不合理等。
终端是否稳定驻留的判断，使用RLF报告中的UE上报定时器判断，如果为该值比较小，说明没有稳定驻留，如果比较大，说明切换后稳定驻留了。如果为0，说明没有切换发生。
DAPS切换由于在切换过程中源小区连接保持不断，因此失败的场景会更加复杂一些，DAPS涉及的切换过迟、切换过早和切换到错误小区的场景如下：
DAPS切换过迟：
终端在源小区稳定驻留一段时间后，发生了无线链路失败，终端通过RRC连接重建立试图接入一个不同的小区。
终端在源小区稳定驻留一段时间后，DASP切换成功并且可以稳定驻留目标小区，但是DAPS切换过程中源小区发生了无线链路失败。
DAPS切换过早：
DAPS切换接入目标小区成功但是很快发生了无线链路失败，终端发生RRC连接重建立试图接入源小区。
在DAPS切换过程中，终端接入目标小区失败，回退源小区成功并且一段时间内未发生RLF。
DAPS切换到错误小区：
在DAPS切换过程中，源小区连接先发生RLF，之后终端接入目标小区失败，终端发生RRC连接重建立试图接入不同于切换目标小区和源小区的其他小区。
在DAPS切换过程中，接入目标小区成功但是很快发生了无线链路失败，终端发生RRC连接重建立试图接入不同于切换目标小区和源小区的其他小区。
在DAPS切换过程中源小区如果发生了无线链路失败，将记录在成功切换报告中。后续如果目标侧接入失败或者目标侧随机接入成功但是很快发生RLF，将记录到RLF报告中。
根据上述的MRO特性，网络节点之间的消息流程，包括失败指示failure indication消息、切换报告handover report消息、接入和移动性指示Access and  mobility indication消息。
其中，对于失败指示failure indication消息：
UE在切换失败或者RLF失败后，可能重新接入网络，网络节点获取到UE的RLF报告后，如果当前网络节点不是发生失败的节点，需要在网络节点间转发RLF报告等相关信息给失败的网络节点，便于发生失败的网络节点进行分析和优化。
可选地，失败指示failure indication消息通过空口的RRC重建立请求触发或者RRC建立触发。对于RRC重建立请求，可选地，包括RRC重建立请求携带的信息以及UE RLF报告；对于RRC建立，包括UE RLF报告。
对于切换报告handover report消息：
产生失败的网络节点分析失败指示failure indication消息后，可能需要发送切换报告handover report消息，可选地，发送过程如图3所示，包括：
步骤1，UE从网络节点1切换到网络节点2的切换成功；
步骤2，网络节点2发生无线链路失败RLF；
步骤3，UE记录RLF报告；
步骤4，UE成功接入网络节点3；
步骤5，网络节点3获取UE的RLF报告；
步骤6，UE切换至网络节点3成功后，发生RLF，失败基站为网络节点2，向网络节点2发送失败指示failure indication消息；
步骤7，网络节点2分析failure indication消息后，发现RLF失败是由于网络节点1切换选择的目标小区不合理导致，切换失败类型属于切换到错误小区失，应该选择网络节点3，则发送切换报告handover report消息通知网络节点1。
可选地，该切换报告handover report消息包括以下信息内容：
报告类型，指示失败节点分析的结果，包括过早切换、切换到错误小区等；
切换源小区，包括全球小区标识身份标识号(Identity document，ID)；
切换目标小区，包括全球小区标识ID；
RRC重建立小区，包括全球小区标识ID，当报告类型为切换到错误小区 时，包括该RRC重建立小区的指示信息，通知源小区应该选择该小区作为切换的目标小区；
UE RLF报告，可选内容，如果接收的失败指示failure indication消息包括UE RLF报告，则在传输切换报告handover report消息时也包括UE RLF报告。
对于接入和移动性指示Access and mobility indication消息，用于在网络节点间传递成功切换报告等相关信息。
根据以上，在DAPS切换过程中，可能在源侧发生无线链路失败，切换的目标侧也可能发生随机接入失败或者随机接入成功后很快发生无线链路失败。源侧的失败信息记录在成功切换报告中并使用Access and mobility indication消息在网络节点间进行传递；目标侧的失败信息记录在RLF报告中并使用failure indication消息在网络节点间进行传递。切换源侧的网络节点在切换完成后可能已经释放了UE的上下文信息，因此通过Access and mobility indication消息和failure indication消息收到成功切换报告和RLF报告时，并不知道这些报告是否对应于同一个UE。如果成功切换报告对应于UE1，RLF报告对应于UE2，UE1可能统计为一次DAPS切换过迟错误，UE2可能统计为一次切换过早错误。如果成功切换报告和RLF报告属于同一个UE，该UE可能统计为一次切换到错误小区错误。
通过上面的分析可以看出，源侧进行DAPS切换错误分析时，需要确定成功切换报告和RLF报告是否属于同一个用户，否则对应成功切换报告和RLF报告单独分析会导致存在分析结果不准确的问题。
为解决上述问题，本公开实施例提供一种报告处理方法，采用该方法，网络节点之间在传输无线链路失败RLF报告和成功切换报告时，使所发送的属于同一终端的RLF报告和成功切换报告相关联，以使网络节点可以正确分析切换失败原因，保证网络节点对失败类型分析的准确性，进行有效的切换参数优化。
本公开其中一实施例所述报告处理方法，如图4所示，由第一网络节点执行，所述方法包括：
S410，获取无线链路失败RLF报告和成功切换报告；
S420，确定具有关联关系的所述RLF报告和所述成功切换报告；
S430，根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
本公开实施例中，可选地，第二网络节点可以为但不限于仅能够为目标终端切换后的目标网络节点，第一网络节点可以为但不限于仅能够为目标终端切换前的源网络节点。
本公开实施例所述报告处理方法，第二网络节点在向第一网络节点发送无线链路失败RLF报告和成功切换报告时，与终端相关联，也即能够指示该无线链路失败RLF报告和成功切换报告为与同一终端相关联，以使第一网络节点根据相关联的无线链路失败RLF报告和成功切换报告进行失败类型分析，保证网络节点对失败类型分析的准确性，避免分析出错误类型，并能够进行有效的切换参数优化。
其中一实施方式，在步骤S410，获取无线链路失败RLF报告和成功切换报告，包括：
通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，其中，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点；
其中，在步骤S420，确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告，包括：
若一个所述第一接口消息中携带不同终端生成的无线链路失败RLF报告和成功切换报告，则将同一个终端生成的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
采用该实施方式，第二网络节点通过同一接口消息(第一接口消息)向 第一网络节点发送RLF报告和成功切换报告，且同时发送的该无线链路失败RLF报告和成功切换报告能够与目标终端相关联。
该实施方式中，可选地，可以通过XN接口、X2接口、NG接口和S1接口中的至少之一，接收第二网络节点发送的关联目标终端的无线链路失败RLF报告和成功切换报告。
可选地，可以通过失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少之一，接收第二网络节点发送的关联目标终端的无线链路失败RLF报告和成功切换报告。
其中，特定消息为预先设定、特定用于指示发送无线链路失败RLF报告和成功切换报告的消息。
可选地，在通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告的情况中，所述第一接口消息中可以包括报告列表，所述报告列表中包括不同终端所生成的RLF报告和成功切换报告，所述目标终端为不同终端的其中之一。
具体地，所述报告列表中包括至少一列，每一列内记录对应同一终端的RLF报告和成功切换报告，所述目标终端的RLF报告和成功切换报告记录于所述报告列表中的一列中。
另外，由于成功切换报告和RLF报告为非实时的报告，第二网络节点可以缓存多个UE生成的成功切换报告和RLF报告，之后在一条接口消息中同时发送关联同一终端的成功切换报告和RLF报告。在第一接口消息中包含多个UE的报告时，可以采用报告列表形式传递多个UE的报告，列表的每个节点表示一个UE的报告，每个UE的报告内包含相关联的成功切换报告和RLF报告。
本公开实施例所述方法，另一实施方式，在步骤S410，获取无线链路失败RLF报告和成功切换报告，包括：
分别通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
在步骤S420，确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
根据所述第二接口消息中携带的第一终端标识，确定所述第一终端标识对应的RLF报告，以及根据所述第三接口消息中携带的第二终端标识，确定所述第二终端标识对应的成功切换报告；
若所述第一终端标识与所述第二终端标识相同，则将所述第一终端标识对应的RLF报告和所述第二终端标识对应的成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
采用该实施方式，第二网络节点可以通过不同接口消息，分别向第一网络节点发送无线链路失败RLF报告和成功切换报告，且发送无线链路失败RLF报告和成功切换报告的接口消息中分别包括终端的标识，这样根据接口消息中包括的终端的标识，可以关联通过不同接口消息传输的同一终端生成的无线链路失败RLF报告和成功切换报告。
可选地，在通过第二接口消息获取RLF报告的情况下，所述第二接口消息中包括第一报告列表，所述第一报告列表中包括至少一个终端的RLF报告；
在通过第三接口消息获取成功切换报告的情况下，所述第三接口消息中包括第二报告列表，所述第二报告列表中包括至少一个终端的成功切换报告。
采用该实施方式，接口消息中可以包括报告列表，用于发送至少一个终端的成功切换报告或RLF报告，且接口消息中，对应每一成功切换报告或RLF报告分别具有相对应的终端标识，用于指示每一成功切换报告或每一RLF报告所分别关联的终端。
另外，可选地，该实施方式中，通过第二接口消息获取RLF报告，或者通过第三接口消息获取成功切换报告时，第二接口消息和第三接口消息分别为失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少一种或者多种。可选地，第二接口消息和第三接口消息的发送接口分别为XN接口、X2接口、NG接口和S1接口中的至少之一。
本公开实施例所述方法，另一实施方式，在步骤S410，获取无线链路失败RLF报告和成功切换报告，具体包括：
获取终端发送的无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识；
在步骤S420，确定具有关联关系的所述RLF报告和所述成功切换报告， 具体包括：
根据所述RLF报告中携带终端标识和成功切换报告中携带终端标识，将所述终端标识相同的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
采用该实施方式，终端在记录成功切换报告和RLF报告时，增加终端标识的记录，因此无需在发送成功切换报告或RLF报告的接口消息中增加终端标识。
这样，源网络节点(第一网络节点)在接收成功切换报告和RLF报告后，通过成功切换报告和RLF报告中的终端标识进行关联，确定相关联的成功切换报告和RLF报告，并进行切换失败类型分析。
以下对采用上述各个方式时，本公开实施例所述报告传输方法的实施过程进行举例说明。
由于DAPS失败的场景比较多，无线链路失败RLF报告或成功切换报告的传输可能产生在多种不同实施场景中，为清楚说明本公开实施例所述报告传输方法的实施过程，以下将以DAPS中，最典型的失败场景：DAPS切换过程中在源网络节点发生无线链路失败，DAPS切换目标网络节点随机接入成功，但是很快发生了RLF，终端在另一网络节点恢复连接，以该场景为例，详细介绍本公开步骤S410至S430，获取无线链路失败RLF报告和成功切换报告，确定具有关联关系的所述RLF报告和所述成功切换报告的具体实施方式。
需要说明的是，本公开实施例所述报告传输方法，并不限于仅能够应用于DAPS切换过程，也可以应用于传统切换过程，且不限于仅能够应用于下述举例说明的失败场景。
实施方式一
在实施方式一中，采用方式一，通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，无线链路失败RLF报告与成功切换报告相关联。
采用该实施方式，第二网络节点通过第一接口消息发送无线链路失败RLF报告和成功切换报告时，还包括：
第二网络节点获取目标终端由第一网络节点切换至所述第二网络节点成功后发送的成功切换报告；
第二网络节点获取所述目标终端在所述第二网络节点发生RLF，连接到第三网络节点后，第三网络节点通过失败指示消息发送的所述目标终端的RLF报告；
其中，第二网络节点通过第一接口消息向第一网络节点发送关联目标终端的RLF报告和成功切换报告，包括：
关联所述成功切换报告和所述RLF报告，通过第一接口消息向第一网络节点发送所述目标终端的RLF报告和成功切换报告。
该实施方式中，第二网络节点在分别获取成功切换报告和RLF报告后，关联该成功切换报告和RLF报告，通过同一接口消息向第一网络节点发送目标终端的RLF报告和成功切换报告。
参阅图5所示，该实施方式的具体实施过程，包括步骤：
S510，UE执行DAPS切换，从第一网络节点(源网络节点)向第二网络节点(目标网络节点)进行切换；
S520，第一网络节点(源网络节点)发生无线链路失败，UE记录成功切换报告；
S530，DAPS切换成功；
S540，第二网络节点(目标网络节点)发起UE信息获取流程，获取UE记录的成功切换报告；可选地，可以向UE发送信息请求，请求获取该成功切换报告；
S550，第二网络节点(目标网络节点)发生无线链路失败，UE记录RLF报告；
S560，UE重新连接到其他网络节点(第三网络节点)，且第三网络节点获取UE记录的RLF报告；
S570，第三网络节点通过failure indication消息将RLF报告发给第二网络节点(目标网络节点)；
S580，第二网络节点(目标网络节点)识别所接收的RLF报告，以及根据之前获取的成功切换报告，识别出属于同一终端的RLF报告和成功切换报 告，将所识别出属于同一终端的RLF报告和成功切换报告，通过同一接口消息(第一接口消息)发送至第一网络节点(源网络节点)，用于表示所发送的该RLF报告和成功切换报告属于同一终端。
可选地，第二网络节点可以根据RLF报告和成功切换报告中的位置信息、终端标识和小区标识等中的至少一项识别出所接收的RLF报告和成功切换报告是否属于同一终端。
另一方面，可选地，在通过第一接口消息向第二网络节点发送关联目标终端的RLF报告和成功切换报告的情况下，所述第一接口消息中包括报告列表，所述报告列表中包括至少一个终端所分别相关联的RLF报告和成功切换报告，所述目标终端为至少一个终端的其中之一。
具体地，所述报告列表中包括至少一个报告节点，每一报告节点内记录对应同一终端的RLF报告和成功切换报告，所述目标终端的RLF报告和成功切换报告记录于其中一报告节点内。
另外，由于成功切换报告和RLF报告为非实时的报告，基站可以缓存多个用户的成功切换报告和RLF报告，之后在一条接口消息中同时发送关联同一终端的成功切换报告和RLF报告。在消息中包含多个UE的报告时，可以采用报告列表形式传递多个UE的报告，列表的每个节点表示一个UE的报告，每个UE的报告内包含相关联的成功切换报告和RLF报告。
本公开实施例中，可选地，在通过同一接口消息(第一接口消息)发送RLF报告和成功切换报告时，该第一接口消息的发送接口为XN接口、X2接口、NG接口和S1接口中的至少之一。
可选地，该第一接口消息为XN或者X2接口，在网络侧节点间没有XN或者X2连接时，也可以通过NG或者S1接口发送。
另一实施方式，可选地，通过同一接口消息(第一接口消息)发送RLF报告和成功切换报告时，第一接口消息可以通过失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少之一传输。
实施方式二
在实施方式二中，采用方式二，第一网络节点通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
其中所述第二接口消息和所述第三接口消息中分别包括所述目标终端的标识。
采用该实施方式，第二网络节点通过第二接口消息向第一网络节点发送RLF报告，以及通过第三接口消息向第一网络节点发送成功切换报告，包括：
若第二网络节点获取到目标终端由第一网络节点切换至所述第二网络节点成功之后发送的成功切换报告，则通过第三接口消息向第一网络节点发送成功切换报告；
若第二网络节点获取到所述目标终端在重新连接到第三网络节点，第三网络节点通过失败指示消息发送的所述目标终端的RLF报告，则通过第二接口消息向第一网络节点发送RLF报告。
采用该实施方式，成功切换报告和RLF报告通过不同的接口消息发送至第一网络节点，且在接收到成功切换报告后可以立即发送至源网络节点，不需要等待后续的RLF报告，发送成功切换报告的接口消息与发送RLF报告的接口消息通过所包括的终端标识相关联。
参阅图6所示，该实施方式的具体实施过程，包括步骤：
S610，UE执行DAPS切换，从第一网络节点(源网络节点)向第二网络节点(目标网络节点)进行切换；
S620，第一网络节点(源网络节点)发生无线链路失败，UE记录成功切换报告；
S630，DAPS切换成功；
S640，第二网络节点(目标网络节点)发起UE信息获取流程，获取UE记录的成功切换报告；可选地，可以向UE发送信息请求，请求获取该成功切换报告；
S650，第二网络节点(目标网络节点)获得该成功切换报告后，立即将该成功切换报告通过接口消息(第三接口消息)发送至第一网络节点(源网络节点)；
S660，第二网络节点(目标网络节点)发生无线链路失败，UE记录RLF报告；
S670，UE重新连接到其他网络节点(第三网络节点)，且第三网络节点 获取UE记录的RLF报告；
S680，第三网络节点通过failure indication消息将RLF报告发给第二网络节点(目标网络节点)；
S690，第二网络节点(目标网络节点)通过接口消息(如为第二接口消息)将RLF报告发送至第一网络节点(源网络节点)。
其中，该实施方式中，在步骤S650和S690，第二网络节点向第一网络节点通过接口消息发送成功切换报告和RLF报告时，所发送的接口消息中包括UE标识，用于标识该成功切换报告和RLF报告对应于同一终端。
由于终端从源网络节点切换至目标网络节点之后，源网络节点可能已经删除了用户的上下文信息，根据UE标识已经无法获得用户的上下文信息，但根据接口消息中包括的UE标识，可以关联发送RLF报告的第二接口消息和发送成功切换报告的第三接口消息，确定该成功切换报告和RLF报告对应于同一终端。
可选地，在通过第二接口消息向第一网络节点发送RLF报告的情况下，所述第二接口消息中包括第一报告列表，所述第一报告列表中包括至少一个终端的RLF报告；
在通过第三接口消息向第一网络节点发送成功切换报告的情况下，所述第三接口消息中包括第二报告列表，所述第二报告列表中包括至少一个终端的成功切换报告；
其中，所述目标终端为至少一个终端的其中之一。
采用该实施方式，接口消息中可以包括报告列表，用于发送至少一个终端的成功切换报告或RLF报告，且接口消息中，对应每一成功切换报告或RLF报告分别具有相对应的终端标识，用于指示每一成功切换报告或每一RLF报告所分别关联的终端。
本公开实施例中，可选地，第二网络节点通过第二接口消息向第一网络节点发送RLF报告，以及通过第三接口消息向第一网络节点发送成功切换报告时，第二接口消息和第三接口消息可以通过失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少之一传输。
本公开实施例中，可选地，第二网络节点在通过第二接口消息发送RLF 报告，通过第三接口消息发送成功切换报告时，该第二接口消息和第三接口消息的发送接口分别为XN接口、X2接口、NG接口和S1接口中的至少之一。
可选地，该第二接口消息和第三接口消息分别为XN接口或者X2接口，在网络侧节点间没有XN接口或者X2连接时，也可以通过NG接口或者S1接口发送。
对比方式一和方式二，两种方式都需要目标网络节点识别出成功切换报告和RLF报告属于同一个终端。其中，采用方式二，相较于方式一，目标网络节点在接收到成功切换报告后可以立即发送至源网络节点，不需要等待后续的RLF报告；可选地，基于该实施方式，源网络节点在接收成功切换报告后，不限于必须立即执行切换分析和优，需要等待确认后续是否还有RLF报告。
实施方式三
在实施方式三中，采用方式三，第二网络节点通过第二接口消息向第一网络节点发送RLF报告，以及通过第三接口消息向第一网络节点发送成功切换报告，其中所述RLF报告和所述成功切换报告中分别包括所述目标终端的标识。
可选地，该实施方式具体实施时的切换流程可以与实施方式二相同，以下继续以图6所示的实施流程，说明方式三的具体实施方式：
参阅图6所示，该实施方式三的具体实施过程，包括步骤：
S610，UE执行DAPS切换，从第一网络节点(源网络节点)向第二网络节点(目标网络节点)进行切换；
S620，第一网络节点(源网络节点)发生无线链路失败，UE记录成功切换报告；
S630，DAPS切换成功；
S640，第二网络节点(目标网络节点)发起UE信息获取流程，获取UE记录的成功切换报告；其中，该实施方式中，UE所记录的成功切换报告中包括终端标识，因此第二网络节点所获取的成功切换报告中包括终端标识；
可选地，可以向UE发送信息请求，请求获取该成功切换报告；
S650，第二网络节点(目标网络节点)获得该成功切换报告后，立即将 该成功切换报告通过接口消息(第三接口消息)发送至第一网络节点(源网络节点)；
S660，第二网络节点(目标网络节点)发生无线链路失败，UE记录RLF报告；该实施方式中，UE所记录的RLF报告中包括终端标识；
S670，UE重新连接到其他网络节点(第三网络节点)，且第三网络节点获取UE记录的RLF报告；
S680，第三网络节点通过failure indication消息将RLF报告发给第二网络节点(目标网络节点)；
S690，第二网络节点(目标网络节点)通过接口消息(如为第二接口消息)将RLF报告发送至第一网络节点(源网络节点)。
采用该实施方式三，相较于实施方式二，终端在记录成功切换报告和RLF报告时，则增加终端标识的记录，因此无需在发送成功切换报告或RLF报告的接口消息中增加终端标识。
采用该实施方式，源网络节点在接收成功切换报告和RLF报告后，通过成功切换报告和RLF报告中的终端标识进行关联，确定相关联的成功切换报告和RLF报告，并进行切换失败类型分析。
该实施方式三中，可选地，与实施方式二相同，在第二网络节点通过第二接口消息向第一网络节点发送RLF报告的情况下，所述第二接口消息中包括第一报告列表，所述第一报告列表中包括至少一个终端的RLF报告；
在第二网络节点通过第三接口消息向第一网络节点发送成功切换报告的情况下，所述第三接口消息中包括第二报告列表，所述第二报告列表中包括至少一个终端的成功切换报告；
其中，所述目标终端为至少一个终端的其中之一。
采用该实施方式，接口消息中可以包括报告列表，用于发送至少一个终端的成功切换报告或RLF报告，且每一成功切换报告和RLF报告中分别包括相对应的终端标识，用于指示每一成功切换报告或每一RLF报告所分别关联的终端。
本公开实施例中，可选地，与实施方式二相同，通过第二接口消息向第一网络节点发送RLF报告，以及通过第三接口消息向第一网络节点发送成功 切换报告时，第二接口消息和第三接口消息可以通过失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少之一传输。
本公开实施例中，可选地，第二网络节点在通过第二接口消息发送RLF报告，通过第三接口消息发送成功切换报告时，该第二接口消息和第三接口消息的发送接口分别为XN接口、X2接口、NG接口和S1接口中的至少之一。
可选地，该第二接口消息和第三接口消息分别为XN接口或者X2接口，在网络侧节点间没有XN接口或者X2连接时，也可以通过NG接口或者S1接口发送。
采用本公开实施例所述报告传输方法中上述的任一实施方式，网络节点之间在传输无线链路失败RLF报告和成功切换报告时，使所发送的属于同一终端的RLF报告和成功切换报告相关联，以使网络节点可以对属于同一终端的成功切换报告和RLF报告联合起来进行分析，保证能够正确分析切换失败原因，保证网络节点对失败类型分析的准确性，进行有效的切换参数优化。
本公开另一实施例提供一种报告处理方法，应用于第二网络节点，如图7所示，所述方法包括：
S710，获取无线链路失败RLF报告和成功切换报告；
S720，将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告，分析无线链路失败原因或者切换失败原因。
采用本公开实施例所述方法，网络节点之间在传输无线链路失败RLF报告和成功切换报告时，使所发送的属于同一终端的RLF报告和成功切换报告相关联，以使网络节点可以正确分析切换失败原因，保证网络节点对失败类型分析的准确性，进行有效的切换参数优化。
本公开实施例中，可选地，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。
本公开实施例中，可选地，在步骤S710，获取成功切换报告，具体包括：
接收终端发送的成功切换报告，所述成功切换报告为所述终端在DAPS切换成功后生成的；
获取无线链路失败RLF报告，具体包括：
接收其他网络节点发送的RLF报告，所述RLF报告为终端在双激活协议栈DAPS切换成功后又发生RLF后生成的，所述其他网络节点为终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。
可选地，所述的报告处理方法，在步骤S720，将相关联的RLF报告和成功切换报告发送给第一网络节点，具体包括：
识别具有关联关系的所述RLF报告和所述成功切换报告，所述具有关联关系的所述RLF报告和所述成功切换报告为同一个终端生成；
将识别出的具有关联关系的所述RLF报告和所述成功切换报告发送给第一网络节点。
本公开实施例中，可选地，在步骤S720，通过以下其中之一方式，将相关联的RLF报告和成功切换报告发送给第一网络节点：
方式一：通过第一接口消息向第一网络节点发送关联终端的RLF报告和成功切换报告；
方式二：通过第二接口消息向第一网络节点发送RLF报告，以及通过第三接口消息向第一网络节点发送成功切换报告，其中所述第二接口消息和所述第三接口消息中分别包括终端的标识；
方式三：通过第二接口消息向第一网络节点发送RLF报告，以及通过第三接口消息向第一网络节点发送成功切换报告，其中所述RLF报告和所述成功切换报告中分别包括所述终端的标识。
采用本公开实施例所述报告处理方法，采用方式一，第二网络节点可以在同一接口消息(第一接口消息)，同时向第一网络节点发送无线链路失败RLF报告和成功切换报告，且同时发送的该无线链路失败RLF报告和成功切换报告能够与终端相关联；
采用方式二，第二网络节点可以通过不同接口消息，分别向第一网络节点发送无线链路失败RLF报告和成功切换报告，且发送无线链路失败RLF 报告和成功切换报告的接口消息中分别包括目标终端的标识，这样根据接口消息中包括的目标终端的标识，可以关联接口消息中对应同一目标终端的无线链路失败RLF报告和成功切换报告；
采用方式三，第二网络节点可以通过不同接口消息，分别向第一网络节点发送无线链路失败RLF报告和成功切换报告，且在所发送的无线链路失败RLF报告和成功切换报告中分别包括终端标识，这样根据终端标识，可以识别对应同一终端的无线链路失败RLF报告和成功切换报告；
采用该实施方式，可选地，在终端生成无线链路失败RLF报告和成功切换报告时，则将终端的标识写入所生成的无线链路失败RLF报告和成功切换报告中，也即相较于相关技术，修改空口传输内容，将包括终端标识的无线链路失败RLF报告或成功切换报告，发送至网络节点。
本公开实施例中，可选地，可以通过XN接口、X2接口、NG接口和S1接口中的至少之一，向第一网络节点发送关联目标终端的无线链路失败RLF报告和成功切换报告。
另一实施方式，可选地，可以通过失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少之一，向第一网络节点发送关联目标终端的无线链路失败RLF报告和成功切换报告。
其中，特定消息为预先设定、特定用于指示发送无线链路失败RLF报告和成功切换报告的消息。
本公开实施例另一实施例还提供一种报告处理方法，如图8所示，应用于终端设备，所述方法包括：
S810，生成无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
S820，将生成的所述无线链路失败RLF报告和成功切换报告发送给网络设备。
采用该实施方式，终端在记录成功切换报告和RLF报告时，则增加终端标识的记录，无需在发送成功切换报告或RLF报告的接口消息中增加终端标 识，这样网络节点之间在传输无线链路失败RLF报告和成功切换报告时，根据成功切换报告中的终端标识和RLF报告中的终端标识，同一终端的RLF报告和成功切换报告相关联，以使网络节点可以正确分析切换失败原因，保证网络节点对失败类型分析的准确性，进行有效的切换参数优化。
本公开实施例中，RLF报告和成功切换报告中分别包括的内容信息，以及网络节点之间传输RLF报告和成功切换报告的具体过程，可以结合图1至图3，并参阅以上的详细描述，在此不再详细说明。
本公开其中一实施例所述报告处理方法，由第二网络节点执行，所述方法包括：
向第一网络节点发送关联目标终端的无线链路失败RLF报告和成功切换报告。
本公开实施例所述报告处理方法，第二网络节点在向第一网络节点发送无线链路失败RLF报告和成功切换报告时，与目标终端相关联，也即能够指示该无线链路失败RLF报告和成功切换报告为与同一目标终端相关联，以使第一网络节点根据相关联的无线链路失败RLF报告和成功切换报告进行失败类型分析，保证网络节点对失败类型分析的准确性，避免分析出错误类型，并能够进行有效的切换参数优化。
本公开实施例中，可选地，通过以下其中之一方式，向第一网络节点发送关联目标终端的无线链路失败RLF报告和成功切换报告：
方式一：通过第一接口消息向第一网络节点发送关联目标终端的RLF报告和成功切换报告；
方式二：通过第二接口消息向第一网络节点发送RLF报告，以及通过第三接口消息向第一网络节点发送成功切换报告，其中所述第二接口消息和所述第三接口消息中分别包括所述目标终端的标识；
方式三：通过第二接口消息向第一网络节点发送RLF报告，以及通过第三接口消息向第一网络节点发送成功切换报告，其中所述RLF报告和所述成功切换报告中分别包括所述目标终端的标识。
本公开实施例中，可选地，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点， 所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。采用本公开实施例所述报告处理方法，采用方式一，第二网络节点可以在同一接口消息(第一接口消息)，同时向第一网络节点发送无线链路失败RLF报告和成功切换报告，且同时发送的该无线链路失败RLF报告和成功切换报告能够与目标终端相关联；
采用方式二，第二网络节点可以通过不同接口消息，分别向第一网络节点发送无线链路失败RLF报告和成功切换报告，且发送无线链路失败RLF报告和成功切换报告的接口消息中分别包括目标终端的标识，这样根据接口消息中包括的目标终端的标识，可以关联接口消息中对应同一目标终端的无线链路失败RLF报告和成功切换报告；
采用方式三，第二网络节点可以通过不同接口消息，分别向第一网络节点发送无线链路失败RLF报告和成功切换报告，且在所发送的无线链路失败RLF报告和成功切换报告中分别包括目标终端的标识，这样根据目标终端的标识，可以使对应同一目标终端的无线链路失败RLF报告和成功切换报告；采用该实施方式，可选地，在目标终端生成无线链路失败RLF报告和成功切换报告时，则将目标终端的标识写入所生成的无线链路失败RLF报告和成功切换报告中，也即相较于相关技术，修改空口消息内容，将包括目标终端的标识的无线链路失败RLF报告或成功切换报告，发送至网络节点。
本公开实施例中，可选地，可以通过XN接口、X2接口、NG接口和S1接口中的至少之一，向第一网络节点发送关联目标终端的无线链路失败RLF报告和成功切换报告。
另一实施方式，可选地，可以通过失败指示消息、切换报告消息、接入和移动性指示消息和特定消息中的至少之一，向第一网络节点发送关联目标终端的无线链路失败RLF报告和成功切换报告。
其中，特定消息为预先设定、特定用于指示发送无线链路失败RLF报告和成功切换报告的消息。
采用本公开实施例所述报告处理方法中上述的任一实施方式，网络节点之间在传输无线链路失败RLF报告和成功切换报告时，使所发送的属于同一 终端的RLF报告和成功切换报告相关联，以使网络节点可以对属于同一终端的成功切换报告和RLF报告联合起来进行分析，保证能够正确分析切换失败原因，保证网络节点对失败类型分析的准确性，进行有效的切换参数优化。
本公开实施例另一实施方式还提供一种报告处理方法，由第一网络节点执行，所述方法包括：
获取关联目标终端的无线链路失败RLF报告和成功切换报告；
根据所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
本公开实施例所述报告处理方法，第二网络节点在向第一网络节点发送无线链路失败RLF报告和成功切换报告时，与目标终端相关联，也即能够指示该无线链路失败RLF报告和成功切换报告为与同一目标终端相关联，以使第一网络节点根据相关联的无线链路失败RLF报告和成功切换报告进行失败类型分析，保证网络节点对失败类型分析的准确性，避免分析出错误类型，并能够进行有效的切换参数优化。
可选地，所述的报告处理方法，其中，通过以下其中之一方式，获取关联目标终端的无线链路失败RLF报告和成功切换报告：
通过第一接口消息获取第二网络节点所传输、关联所述目标终端的所述RLF报告和所述成功切换报告；
通过第二接口消息获取第三网络节点传输的所述RLF报告，以及通过第三接口消息获取第四网络节点传输的所述成功切换报告，其中所述第二接口消息和所述第三接口消息中分别包括所述目标终端的标识；
通过第二接口消息获取第三网络节点传输的所述RLF报告，以及通过第三接口消息获取第四网络节点传输的所述成功切换报告，其中所述RLF报告和所述成功切换报告中分别包括所述目标终端的标识。
需要说明的是，上述的第二网络节点、第三网络节点和第四网络节点分别为能够向第一网络节点发送RLF报告或成功切换报告的网络节点，名称上仅用于区分不同网络节点，具体可以为相同或不同网络节点。
可选地，所述的报告处理方法，其中，在通过第一接口消息获取第二网络节点所传输、关联所述目标终端的所述RLF报告和所述成功切换报告的情 况下，所述第一接口消息中包括报告列表，所述报告列表中包括至少一个终端所分别相关联的RLF报告和成功切换报告，所述目标终端为至少一个终端的其中之一。
可选地，所述的报告处理方法，其中，在通过第二接口消息获取第三网络节点传输的RLF报告的情况下，所述第二接口消息中包括第一报告列表，所述第一报告列表中包括至少一个终端的RLF报告；
在通过第三接口消息获取第四网络节点传输的成功切换报告的情况下，所述第三接口消息中包括第二报告列表，所述第二报告列表中包括至少一个终端的成功切换报告；
其中，所述目标终端为至少一个终端的其中之一。
可选地，所述的报告处理方法，其中，所述第一接口消息、所述第二接口消息和所述第三接口消息分别通过失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少之一传输。
可选地，所述的报告处理方法，其中，所述第一接口消息、所述第二接口消息和所述第三接口消息的发送接口为XN接口、X2接口、NG接口和S1接口中的至少之一。
可选地，所述的报告处理方法，其中，所述第一网络节点为所述目标终端的源网络节点，所述第二网络节点为所述目标终端的目标网络节点；或者
所述第一网络节点为所述目标终端的源网络节点，所述第三网络节点和所述第四网络节点为以下其中之一：
源网络节点；
目标网络节点；
除源网络节点和目标网络节点之外的网络节点。
需要说明的是，本公开实施例中，结合图5和图6，以发送RLF报告和成功切换报告的网络节点分别为目标网络节点为例进行了说明，但采用本公开实施例所述方法的应用场景不限于仅能够为图5和图6所示场景，能够向源网络节点发送RLF报告或成功切换报告的网络节点并不限于仅能够为目标网络节点，也可以为上述所列举网络节点的其中任一个。
可选地，所述的报告处理方法，其中，根据确定的具有关联关系的所述 RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因，包括：
根据所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因为切换过迟、切换过早和切换到错误小区的其中之一。
需要说明的是，上述实施例中所有关于第一网络节点执行的报告处理方法的描述均适用于该第二网络节点执行的报告处理方法的实施例中，也能达到与之相同的技术效果，在此不再详细说明。
如图9所示，本公开实施例还提供一种网络节点，所述网络节点为第一网络节点，包括处理器900、收发机910、存储器920及存储在所述存储器920上并可在所述处理器900上运行的程序；其中，收发机910通过总线接口与处理器900和存储器920连接，收发机910，用于在处理器900的控制下接收和发送数据；
其中，所述处理器900用于读取存储器中的程序，执行下列过程：
获取无线链路失败RLF报告和成功切换报告；
确定具有关联关系的所述RLF报告和所述成功切换报告；
根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的网络节点，其中，所述处理器900获取无线链路失败RLF报告和成功切换报告，包括：
通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，其中，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点；
确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的网络节点，其中，所述处理器900将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的 所述RLF报告和所述成功切换报告，包括：
若一个所述第一接口消息中携带不同终端生成的无线链路失败RLF报告和成功切换报告，则将同一个终端生成的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的网络节点，其中，所述处理器900获取无线链路失败RLF报告和成功切换报告，包括：
分别通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
根据所述第二接口消息中携带的第一终端标识，确定所述第一终端标识对应的RLF报告，以及根据所述第三接口消息中携带的第二终端标识，确定所述第二终端标识对应的成功切换报告；
若所述第一终端标识与所述第二终端标识相同，则将所述第一终端标识对应的RLF报告和所述第二终端标识对应的成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的网络节点，其中，所述第一接口消息、所述第二接口消息和所述第三接口消息分别为失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少一种或者多种。
可选地，所述的网络节点，其中，所述处理器900获取无线链路失败RLF报告和成功切换报告，具体包括：
获取终端发送无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识；
确定具有关联关系的所述RLF报告和所述成功切换报告，具体包括：
根据所述RLF报告中携带终端标识和成功切换报告中携带终端标识，将所述终端标识相同的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
其中，在图9中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器900代表的一个或多个处理器和存储器920代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等 之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机910可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。处理器900负责管理总线架构和通常的处理，存储器920可以存储处理器900在执行操作时所使用的数据。
处理器900可以是中央处理器(Central Processing Unit，CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
在此需要说明的是，本公开实施例提供的上述网络节点，能够实现上述方法实施例对应第一网络节点所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
本公开实施例还提供一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现应用于上述网络节点(第一网络节点)的报告处理方法的步骤。所述处理器可读存储介质可以是处理器能够存取的任何可用介质或数据存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘((Magneto-Optical Disk，MO)等)、光学存储器(例如光盘(Compact Disk，CD)、数字视频光盘(Digital Versatile Disc，DVD)、蓝光光碟(Blu-ray Disc，BD)、高清通用光盘(High-Definition Versatile Disc，HVD)等)、以及半导体存储器(例如只读存储器(Read-Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、带电可擦可编程只读存储器(Electrically EPROM，EEPROM)、非易失性存储器(NAND FLASH)、固态硬盘(Solid State Disk或Solid State Drive，SSD))等。
如图10所示，本公开实施例还提供一种网络节点，所述网络节点为第二网络节点，包括处理器1000、收发机1010、存储器1020及存储在所述存储器1020上并可在所述处理器1000上运行的程序；其中，收发机1010通过总 线接口与处理器1000和存储器1020连接，收发机1010，用于在处理器1000的控制下接收和发送数据；
其中，所述处理器1000用于读取存储器中的程序，执行下列过程：
获取无线链路失败RLF报告和成功切换报告；
将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的网络节点，其中，所述处理器1000获取成功切换报告，具体包括：
接收终端发送的成功切换报告，所述成功切换报告为所述终端在DAPS切换成功后生成的；
获取无线链路失败RLF报告，具体包括：
接收其他网络节点发送的RLF报告，所述RLF报告为终端在双激活协议栈DAPS切换成功后又发生RLF后生成的，所述其他网络节点为终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。
可选地，所述的网络节点，其中，所述处理器1000将相关联的RLF报告和成功切换报告发送给第一网络节点，具体包括：
识别具有关联关系的所述RLF报告和所述成功切换报告，所述具有关联关系的所述RLF报告和所述成功切换报告为同一个终端生成；
将识别出的具有关联关系的所述RLF报告和所述成功切换报告发送给第一网络节点。
其中，在图10中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1000代表的一个或多个处理器和存储器1020代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1010可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。处理器1000负责管理总线架构和通常的处理，存储器1020可以存储处理器1000在执行操作 时所使用的数据。
处理器1000可以是中央处理器(Central Processing Unit，CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
在此需要说明的是，本公开实施例提供的上述网络节点，能够实现上述方法实施例对应第二网络节点所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
本公开实施例还提供一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现应用于上述网络节点(第二网络节点)的报告处理方法的步骤。所述处理器可读存储介质可以是处理器能够存取的任何可用介质或数据存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(MO)等)、光学存储器(例如CD、DVD、BD、HVD等)、以及半导体存储器(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(SSD))等。
如图11所示，本公开实施例还提供一种终端，包括处理器1100、收发机1110、存储器1120及存储在所述存储器1120上并可在所述处理器1100上运行的程序；其中，收发机1110通过总线接口与处理器1100和存储器1120连接，收发机1110，用于在处理器1100的控制下接收和发送数据，其中，所述处理器1100用于读取存储器中的程序，执行下列过程：
生成无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
将生成的所述无线链路失败RLF报告和成功切换报告发送给网络设备。
其中，在图11中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1100代表的一个或多个处理器和存储器1120代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路 等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1110可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括，这些传输介质包括无线信道、有线信道、光缆等传输介质。针对不同的用户设备，用户接口1130还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器1100负责管理总线架构和通常的处理，存储器1120可以存储处理器1100在执行操作时所使用的数据。
可选地，处理器1100可以是中央处理器(Central Processing Unit，CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
本公开实施例还提供一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现应用于上述终端的报告处理方法的步骤。所述处理器可读存储介质可以是处理器能够存取的任何可用介质或数据存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(MO)等)、光学存储器(例如CD、DVD、BD、HVD等)、以及半导体存储器(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(SSD))等。
本公开实施例还提供一种报告处理装置，由第一网络节点执行，如图12所示，该报告处理装置1200包括：
第一报告获取模块1210，用于获取无线链路失败RLF报告和成功切换报告；
确定模块1220，用于确定具有关联关系的所述RLF报告和所述成功切换报告；
分析模块1230，用于根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的报告处理装置，其中，第一报告获取模块1210获取无线 链路失败RLF报告和成功切换报告，包括：
通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，其中，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点；
确定模块1220确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理装置，其中，确定模块1220将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告，包括：
若一个所述第一接口消息中携带不同终端生成的无线链路失败RLF报告和成功切换报告，则将同一个终端生成的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理装置，其中，第一报告获取模块1210获取无线链路失败RLF报告和成功切换报告，包括：
分别通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
确定模块1220确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
根据所述第二接口消息中携带的第一终端标识，确定所述第一终端标识对应的RLF报告，以及根据所述第三接口消息中携带的第二终端标识，确定所述第二终端标识对应的成功切换报告；
若所述第一终端标识与所述第二终端标识相同，则将所述第一终端标识对应的RLF报告和所述第二终端标识对应的成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
可选地，所述的报告处理装置，其中，所述第一接口消息、所述第二接 口消息和所述第三接口消息分别为失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少一种或者多种。
可选地，所述的报告处理装置，其中，第一报告获取模块1210获取无线链路失败RLF报告和成功切换报告，具体包括：
获取终端发送的无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和所述成功切换报告中携带终端标识；
确定模块1220确定具有关联关系的所述RLF报告和所述成功切换报告，具体包括：
根据所述RLF报告中携带终端标识和成功切换报告中携带终端标识，将所述终端标识相同的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
本公开实施例还提供一种报告处理装置，由第二网络节点执行，如图13所示，该报告处理装置1300包括：
第二报告获取模块1310，用于获取无线链路失败RLF报告和成功切换报告；
第一发送模块1320，用于将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告，分析无线链路失败原因或者切换失败原因。
可选地，所述的报告处理装置，其中，第二报告获取模块1310获取成功切换报告，具体包括：
接收终端发送的成功切换报告，所述成功切换报告为所述终端在DAPS切换成功后生成的；
第二报告获取模块1310获取无线链路失败RLF报告，具体包括：
接收其他网络节点发送的RLF报告，所述RLF报告为终端在双激活协议栈DAPS切换成功后又发生RLF后生成的，所述其他网络节点为终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。
可选地，所述的报告处理装置，其中，第一发送模块1320将相关联的RLF报告和成功切换报告发送给第一网络节点，具体包括：
识别具有关联关系的所述RLF报告和所述成功切换报告，所述具有关联 关系的所述RLF报告和所述成功切换报告为同一个终端生成；
将识别出的具有关联关系的所述RLF报告和所述成功切换报告发送给第一网络节点。
本公开实施例还提供一种报告处理装置，如图14所示，应用于终端，该报告处理装置1400包括：
报告生成模块1410，用于生成无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
第二发送模块1420，用于将生成的所述无线链路失败RLF报告和成功切换报告发送给网络设备。
需要说明的是，本公开实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个处理器可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
需要说明的是，该报告传输装置实施例是与上述方法实施例一一对应的装置，上述方法实施例中所有实现方式均适用于该报告传输装置的实施例中，也能达到相同的技术效果。
需要说明的是，本公开实施例中对单元的划分是示意性的，仅仅为一种 逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个处理器可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域内的技术人员应明白，本公开的实施例可提供为方法、系统、或计算机程序产品。因此，本公开可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机可执行指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机可执行指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些处理器可执行指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的处理器可读存储器中，使得存储在该处理器可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程 或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些处理器可执行指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
需要说明的是，应理解以上各个模块的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且这些模块可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分模块通过处理元件调用软件的形式实现，部分模块通过硬件的形式实现。例如，确定模块可以为单独设立的处理元件，也可以集成在上述装置的某一个芯片中实现，此外，也可以以程序代码的形式存储于上述装置的存储器中，由上述装置的某一个处理元件调用并执行以上确定模块的功能。其它模块的实现与之类似。此外这些模块全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件可以是一种集成电路，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个模块可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指令完成。
例如，各个模块、单元、子单元或子模块可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)等。再如，当以上某个模块通过处理元件调度程序代码的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)或其它可以调用程序代码的处理器。再如，这些模块可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
本公开的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本公开的实施例，例如除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤 或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。此外，说明书以及权利要求中使用“和/或”表示所连接对象的至少其中之一，例如A和/或B和/或C，表示包含单独A，单独B，单独C，以及A和B都存在，B和C都存在，A和C都存在，以及A、B和C都存在的7种情况。类似地，本说明书以及权利要求中使用“A和B中的至少一个”应理解为“单独A，单独B，或A和B都存在”。
显然，本领域的技术人员可以对本公开进行各种改动和变型而不脱离本公开的精神和范围。这样，倘若本公开的这些修改和变型属于本公开权利要求及其等同技术的范围之内，则本公开也意图包含这些改动和变型在内。

Claims (22)

  1. 一种报告处理方法，应用于终端设备，所述方法包括：
    生成无线链路失败RLF报告和成功切换报告，其中，所述RLF报告中携带终端标识，所述成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
    将生成的所述无线链路失败RLF报告和所述成功切换报告发送给网络设备。
  2. 一种报告处理方法，由第一网络节点执行，所述方法包括：
    获取无线链路失败RLF报告和成功切换报告；
    确定具有关联关系的所述RLF报告和所述成功切换报告；
    根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
  3. 根据权利要求2所述的报告处理方法，其中，获取无线链路失败RLF报告和成功切换报告，包括：
    通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，其中，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点；
    确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
    将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
  4. 根据权利要求3所述的报告处理方法，其中，将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告，包括：
    若一个所述第一接口消息中携带不同终端生成的无线链路失败RLF报告和成功切换报告，则将同一个终端生成的RLF报告和成功切换报告确定为具 有关联关系的所述RLF报告和所述成功切换报告。
  5. 根据权利要求2所述的报告处理方法，其中，获取无线链路失败RLF报告和成功切换报告，包括：
    分别通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
    确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
    根据所述第二接口消息中携带的第一终端标识，确定所述第一终端标识对应的RLF报告，以及根据所述第三接口消息中携带的第二终端标识，确定所述第二终端标识对应的成功切换报告；
    若所述第一终端标识与所述第二终端标识相同，则将所述第一终端标识对应的RLF报告和所述第二终端标识对应的成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
  6. 根据权利要求3至5任一项所述的报告处理方法，其中，所述第一接口消息、所述第二接口消息和所述第三接口消息分别为失败指示消息、切换报告handover report消息、接入和移动性指示消息和特定消息中的至少一种或者多种。
  7. 根据权利要求2所述的报告处理方法，其中，获取无线链路失败RLF报告和成功切换报告，具体包括：
    获取终端发送的无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和所述成功切换报告中携带终端标识；
    确定具有关联关系的所述RLF报告和所述成功切换报告，具体包括：
    根据所述RLF报告中携带终端标识和成功切换报告中携带终端标识，将所述终端标识相同的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
  8. 一种报告处理方法，应用于第二网络节点，所述方法包括：
    获取无线链路失败RLF报告和成功切换报告；
    将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告，分析无线链路失败原因或者切换失败原因。
  9. 根据权利要求8所述的报告处理方法，其中，获取成功切换报告，具体包括：
    接收终端发送的成功切换报告，所述成功切换报告为所述终端在DAPS切换成功后生成的；
    获取无线链路失败RLF报告，具体包括：
    接收其他网络节点发送的RLF报告，所述RLF报告为终端在双激活协议栈DAPS切换成功后又发生RLF后生成的，所述其他网络节点为终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点。
  10. 根据权利要求8或9所述的报告处理方法，其中，将相关联的RLF报告和成功切换报告发送给第一网络节点，具体包括：
    识别具有关联关系的所述RLF报告和所述成功切换报告，所述具有关联关系的所述RLF报告和所述成功切换报告为同一个终端生成；
    将识别出的具有关联关系的所述RLF报告和所述成功切换报告发送给第一网络节点。
  11. 一种终端，包括存储器、收发机和处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    生成无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
    将生成的所述无线链路失败RLF报告和成功切换报告发送给网络设备。
  12. 一种网络节点，所述网络节点为第一网络节点，包括存储器、收发机和处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    获取无线链路失败RLF报告和成功切换报告；
    确定具有关联关系的所述RLF报告和所述成功切换报告；
    根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无 线链路失败原因或者切换失败原因。
  13. 根据权利要求12所述的网络节点，其中，所述处理器获取无线链路失败RLF报告和成功切换报告，包括：
    通过第一接口消息接收第二网络节点发送的无线链路失败RLF报告和成功切换报告，其中，所述第二网络节点为终端执行双激活协议栈DAPS切换后的节点，所述第一网络节点为终端执行DAPS切换前的节点，所述RLF报告为所述第二网络节点从其他网络节点中获取的，所述其他网络节点为所述终端在DAPS切换成功后又发生RLF，之后重新连接到的网络节点；
    确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
    将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
  14. 根据权利要求13所述的网络节点，其中，所述处理器将一个所述第一接口消息中传输的无线链路失败RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告，包括：
    若一个所述第一接口消息中携带不同终端生成的无线链路失败RLF报告和成功切换报告，则将同一个终端生成的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
  15. 根据权利要求12所述的网络节点，其中，所述处理器获取无线链路失败RLF报告和成功切换报告，包括：
    分别通过第二接口消息获取RLF报告，以及通过第三接口消息获取成功切换报告；
    确定具有关联关系的所述RLF报告和所述成功切换报告，包括：
    根据所述第二接口消息中携带的第一终端标识，确定所述第一终端标识对应的RLF报告，以及根据所述第三接口消息中携带的第二终端标识，确定所述第二终端标识对应的成功切换报告；
    若所述第一终端标识与所述第二终端标识相同，则将所述第一终端标识对应的RLF报告和所述第二终端标识对应的成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
  16. 根据权利要求12所述的网络节点，其中，所述处理器获取无线链路 失败RLF报告和成功切换报告，具体包括：
    获取终端发送的无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识；
    确定具有关联关系的所述RLF报告和所述成功切换报告，具体包括：
    根据所述RLF报告中携带终端标识和成功切换报告中携带终端标识，将所述终端标识相同的RLF报告和成功切换报告确定为具有关联关系的所述RLF报告和所述成功切换报告。
  17. 一种网络节点，所述网络节点为第二网络节点，包括存储器、收发机和处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    获取无线链路失败RLF报告和成功切换报告；
    将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告，分析无线链路失败原因或者切换失败原因。
  18. 根据权利要求17所述的网络节点，其中，所述处理器将相关联的RLF报告和成功切换报告发送给第一网络节点，具体包括：
    识别具有关联关系的所述RLF报告和所述成功切换报告，所述具有关联关系的所述RLF报告和所述成功切换报告为同一个终端生成；
    将识别出的具有关联关系的所述RLF报告和所述成功切换报告发送给第一网络节点。
  19. 一种报告处理装置，应用于终端，所述装置包括：
    报告生成模块，用于生成无线链路失败RLF报告和成功切换报告，所述RLF报告中携带终端标识和成功切换报告中携带终端标识，所述成功切换报告为所述终端设备在双激活协议栈DAPS切换成功后生成的，所述RLF报告为终端在DAPS切换成功后又发生RLF后生成的；
    第二发送模块，用于将生成的所述无线链路失败RLF报告和成功切换报告发送给网络设备。
  20. 一种报告处理装置，应用于第一网络节点，所述装置包括：
    第一报告获取模块，用于获取无线链路失败RLF报告和成功切换报告；
    确定模块，用于确定具有关联关系的所述RLF报告和所述成功切换报告；
    分析模块，用于根据确定的具有关联关系的所述RLF报告和所述成功切换报告，分析无线链路失败原因或者切换失败原因。
  21. 一种报告处理装置，应用于第二网络节点，所述装置包括：
    第二报告获取模块，用于获取无线链路失败RLF报告和成功切换报告；
    第一发送模块，用于将相关联的RLF报告和成功切换报告发送给第一网络节点，以使所述第一网络节点根据所述相关联的RLF报告和成功切换报告，分析无线链路失败原因或者切换失败原因。
  22. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序用于使所述计算机执行如权利要求1所述的报告处理方法，或者用于使所述计算机执行如权利要求2至7中任一项所述的报告处理方法，或者用于使所述计算机执行权利要求8至10中任一项所述的报告处理方法。
PCT/CN2022/107741 2021-08-05 2022-07-26 报告处理方法、装置、网络节点及终端 WO2023011239A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US18/290,634 US20240259903A1 (en) 2021-08-05 2022-07-26 Report processing method and device, network node, and user equipment
JP2024506837A JP2024529544A (ja) 2021-08-05 2022-07-26 レポート処理方法、装置、ネットワークノード及び端末
EP22851953.4A EP4383811A1 (en) 2021-08-05 2022-07-26 Report processing method and apparatus, network node and terminal
KR1020247007121A KR20240038092A (ko) 2021-08-05 2022-07-26 보고 처리 방법, 장치, 네트워크 노드 및 단말

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110895728.5 2021-08-05
CN202110895728.5A CN115942394A (zh) 2021-08-05 2021-08-05 报告处理方法、装置、网络节点及终端

Publications (1)

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

Family

ID=85155160

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/107741 WO2023011239A1 (zh) 2021-08-05 2022-07-26 报告处理方法、装置、网络节点及终端

Country Status (6)

Country Link
US (1) US20240259903A1 (zh)
EP (1) EP4383811A1 (zh)
JP (1) JP2024529544A (zh)
KR (1) KR20240038092A (zh)
CN (1) CN115942394A (zh)
WO (1) WO2023011239A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101314A (zh) * 2014-04-29 2015-11-25 北京三星通信技术研究有限公司 一种切换报告及rlf报告的发送方法和设备
CN109526010A (zh) * 2019-01-02 2019-03-26 广州汇智通信技术有限公司 一种通信系统切换优化方法和系统
WO2021086249A1 (en) * 2019-11-01 2021-05-06 Telefonaktiebolaget Lm Ericsson (Publ) Dual active protocol stack handover reports
WO2022141563A1 (en) * 2020-12-31 2022-07-07 Nec Corporation Methods for communication, terminal device, network device, and computer readable media

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101314A (zh) * 2014-04-29 2015-11-25 北京三星通信技术研究有限公司 一种切换报告及rlf报告的发送方法和设备
CN109526010A (zh) * 2019-01-02 2019-03-26 广州汇智通信技术有限公司 一种通信系统切换优化方法和系统
WO2021086249A1 (en) * 2019-11-01 2021-05-06 Telefonaktiebolaget Lm Ericsson (Publ) Dual active protocol stack handover reports
WO2022141563A1 (en) * 2020-12-31 2022-07-07 Nec Corporation Methods for communication, terminal device, network device, and computer readable media

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LENOVO, MOTOROLA MOBILITY: "SON Enhancements for DAPS Handover", 3GPP DRAFT; R2-2105805, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210519 - 20210527, 11 May 2021 (2021-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052007282 *

Also Published As

Publication number Publication date
JP2024529544A (ja) 2024-08-06
EP4383811A1 (en) 2024-06-12
KR20240038092A (ko) 2024-03-22
CN115942394A (zh) 2023-04-07
US20240259903A1 (en) 2024-08-01

Similar Documents

Publication Publication Date Title
US10334492B2 (en) Method, apparatus and system for key derivation
WO2018059299A1 (zh) 小区切换的方法、装置及系统和计算机存储介质
KR101546548B1 (ko) Ｒｒｃ 메시지 및 프로시져
US20090003256A1 (en) Mobile communication system and mbms service relevant information transfer method for use therewith
JP5787240B2 (ja) ハンドオーバ失敗の処理方法及びユーザ装置
US20220330056A1 (en) Communication Method and Apparatus
JP2023514365A (ja) 再確立方法および通信機器
WO2022082581A1 (zh) 通信方法及相关设备
WO2022083472A1 (zh) 中继选择和重选的方法、装置及终端
US20240179605A1 (en) Mobility management method and communication apparatus
WO2022152084A1 (zh) 小区切换方法、装置及存储介质
US20230156843A1 (en) Radio link failure information reporting and obtaining method, terminal, and network side device
WO2018228100A1 (zh) 一种网络接入方法和移动终端
CN114765791A (zh) 连接失败信息的处理方法、装置和系统
WO2023066392A1 (zh) 非公共网络处理方法、装置、设备及存储介质
WO2023011239A1 (zh) 报告处理方法、装置、网络节点及终端
WO2018027981A1 (zh) 通信方法、装置和系统
WO2023134763A1 (zh) 信息报告方法以及用户设备
CN101742578A (zh) 一种lte网络中实现信息跟踪激活的方法、装置
US20230388873A1 (en) Method and apparatus for determining daps handover failure type
US20210235531A1 (en) Control method in user equipment and user equipment
WO2023000876A1 (zh) 数据传输方法、装置、基站及终端
WO2023078340A1 (zh) 一种无线通信链路失败处理方法及装置
WO2023241622A1 (zh) 由用户设备执行的方法、用户设备以及信息报告方法
WO2023116392A1 (zh) 一种信息处理方法、装置及可读存储介质

Legal Events

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

Ref document number: 22851953

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18290634

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2024506837

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20247007121

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022851953

Country of ref document: EP

Effective date: 20240305