Downlink data transmission exception identification method and device and computer device

Abstract

The application relates to a downlink data transmission anomaly identification method, device and computer equipment. The method comprises the following steps: monitoring the data identifier of a downlink data packet received by a terminal; when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to a target data identifier, obtaining the data parameter of a continuous abnormal downlink data packet received by the terminal; the abnormal downlink data packet is a downlink data packet with a data identifier that does not conform to the target data identifier; if the data parameter satisfies a preset abnormality judgment condition, it is confirmed that downlink data transmission is abnormal, and an abnormality recovery instruction is generated; the abnormality recovery instruction is used for triggering the terminal to start a recovery mechanism. By using the method, accurate judgment on whether downlink data transmission is abnormal can be realized, so that the terminal can be triggered to start the recovery mechanism in time, the waiting time is reduced, and the transmission efficiency of downlink data is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a downlink data transmission anomaly identification method and device, computer equipment and storage medium. BACKGROUND

[0002] PDCP (Packet Data Convergence Protocol) is a layer below the RRC (Radio Resource Control) in the wireless protocol stack, which provides header compression and decompression, user plane / control plane data transmission, encryption and integrity protection, etc. for the upper layer. Among them, the PDCP downlink user plane data needs to be transmitted in strict order, but in the actual data transmission process, due to temporary network failure or large transmission line loss, the UE (User Equipment) received PDCP data packet is not the PDCP data packet that the UE is waiting for, so the UE will reorder the received PDCP data packet. If the sequence number difference between the PDCP data packet received by the UE and the PDCP data packet waiting for is large, the UE will discard the PDCP data packet with large difference, causing temporary interruption of data transmission. If the UE receives the PDCP data packet with large difference in sequence number and waiting sequence number, it will discard the received PDCP data packet, resulting in no effective PDCP data packet received by the UE for a long time, causing data failure at the application layer.

[0003] The existing technical solution is to trigger the upper layer recovery mechanism to recover if it is detected that the terminal has not received data for a period of time, but the waiting time is long, which greatly reduces the data transmission efficiency.

[0004] Therefore, the existing PDCP downlink data transmission method has the problem of long waiting time for recovery, which leads to low data transmission rate. SUMMARY

[0005] Therefore, it is necessary to provide a downlink data transmission anomaly identification method, device, computer equipment and storage medium to solve the technical problem of long waiting time for recovery in the existing PDCP downlink data transmission method, which leads to low data transmission rate.

[0006] A downlink data transmission anomaly identification method, the method comprising:

[0007] Monitoring the data identifier of the downlink data packet received by the terminal;

[0008] when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining a data parameter of the continuous abnormal downlink data packet received by the terminal; the abnormal downlink data packet is the downlink data packet whose data identifier does not conform to the target data identifier;

[0009] if the data parameter satisfies a preset abnormality judgment condition, confirming that the downlink data transmission is abnormal, and generating an abnormality recovery instruction; the abnormality recovery instruction is used to trigger the terminal to start a recovery mechanism.

[0010] In one of the embodiments, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining the data parameter of the continuous abnormal downlink data packet received by the terminal, comprises:

[0011] When it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining the number of the continuous abnormal downlink data packet received by the terminal as the data parameter of the continuous abnormal downlink data packet received by the terminal.

[0012] In one of the embodiments, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining the number of the continuous abnormal downlink data packet received by the terminal, comprises:

[0013] When it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, starting a preset first counter, and counting by using the first counter; every time it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, performing an adding one operation on the first counter.

[0014] Obtaining a count value accumulated by the first counter currently as the number of the continuous abnormal downlink data packet received by the terminal.

[0015] In one of the embodiments, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining the data parameter of the continuous abnormal downlink data packet received by the terminal, comprises:

[0016] When it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining the number of the system frame corresponding to the continuous abnormal downlink data packet received by the terminal as the data parameter of the continuous abnormal downlink data packet received by the terminal.

[0017] In one of the embodiments, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining the number of the system frame corresponding to the continuous abnormal downlink data packet received by the terminal, comprises:

[0018] when the data identifier of the downlink data packet received by the terminal is detected not to conform to the target data identifier, starting a preset second counter, and counting by using the second counter; and performing an increment operation on the second counter every time a system frame containing a downlink data packet whose data identifier does not conform to the target data identifier is detected;

[0019] obtaining a count value accumulated by the second counter currently as a number of system frames corresponding to the continuous abnormal downlink data packets received by the terminal.

[0020] In one of the embodiments, the method further comprises: if the data identifier of the downlink data packet received by the terminal is detected to conform to the target data identifier during the counting of the first counter / second counter and under the condition that the data parameter does not satisfy the abnormality determination condition, determining that the downlink data transmission is normal, and performing a zero-clearing operation on the first counter and the second counter.

[0021] In one of the embodiments, the method further comprises: obtaining a data parameter threshold corresponding to the data parameter;

[0022] comparing the data parameter with a preset data parameter threshold, and determining that the data parameter satisfies the abnormality determination condition if the data parameter exceeds the data parameter threshold.

[0023] An abnormality identification device for downlink data transmission, the device comprising:

[0024] a monitoring module configured to monitor a data identifier of a downlink data packet received by a terminal;

[0025] a data parameter obtaining module configured to, when the data identifier of the downlink data packet received by the terminal is detected not to conform to a target data identifier, obtain a data parameter of a continuous abnormal downlink data packet received by the terminal; the abnormal downlink data packet is a downlink data packet whose data identifier does not conform to the target data identifier;

[0026] an instruction generating module configured to, if the data parameter satisfies a preset abnormality determination condition, confirm that there is an abnormality in downlink data transmission, and generate an abnormality recovery instruction; the abnormality recovery instruction is used to trigger the terminal to start a recovery mechanism.

[0027] A computer device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0028] monitoring a data identifier of a downlink data packet received by a terminal;

[0029] When it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, then the data parameter of the continuous abnormal downlink data packet received by the terminal is acquired; the abnormal downlink data packet is the downlink data packet whose data identifier does not conform to the target data identifier;

[0030] If the data parameter satisfies the preset abnormality determination condition, it is confirmed that the downlink data transmission is abnormal, and an abnormality recovery instruction is generated; the abnormality recovery instruction is used to trigger the terminal to start the recovery mechanism.

[0031] A computer readable storage medium, which stores a computer program, the computer program is executed by a processor to implement the following steps:

[0032] The data identifier of the downlink data packet received by the terminal is monitored;

[0033] When it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, then the data parameter of the continuous abnormal downlink data packet received by the terminal is acquired; the abnormal downlink data packet is the downlink data packet whose data identifier does not conform to the target data identifier;

[0034] If the data parameter satisfies the preset abnormality determination condition, it is confirmed that the downlink data transmission is abnormal, and an abnormality recovery instruction is generated; the abnormality recovery instruction is used to trigger the terminal to start the recovery mechanism.

[0035] The above downlink data transmission abnormality identification method, device, computer equipment and storage medium, by monitoring the data identifier of the downlink data packet received by the terminal, in order to acquire the data parameter of the continuous abnormal downlink data packet received by the terminal when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier; wherein the abnormal downlink data packet is the downlink data packet whose data identifier does not conform to the target data identifier, and whether the acquired data parameter satisfies the preset abnormality determination condition is determined, when the data parameter satisfies the abnormality determination condition, it is confirmed that the downlink data transmission is abnormal, an abnormality recovery instruction is generated, and the terminal is triggered to start the recovery mechanism. The method directly determines the abnormality of the downlink data transmission by using the data parameter of the continuous abnormal downlink data packet, can realize accurate determination of whether the downlink data transmission is abnormal, so that the terminal can be triggered to start the recovery mechanism in time, reduce the waiting time, improve the transmission efficiency of the downlink data, and avoid the problem that in the traditional method, the transmission abnormality is not detected, and only a fixed time is set, and the recovery mechanism is triggered only when no data is received within the fixed time, the waiting time is long, and the data transmission rate is low. BRIEF DESCRIPTION OF DRAWINGS

[0036] Figure 1 It is a schematic diagram of PDCP downlink data transmission in one embodiment;

[0037] Figure 2 This is a schematic diagram of PDCP downlink data transmission in an application example;

[0038] Figure 3a This is a schematic diagram of PDCP downlink data transmission in an application example;

[0039] Figure 3b This is a schematic diagram of PDCP downlink data transmission in an application example;

[0040] Figure 3c This is a schematic diagram of PDCP downlink data transmission in an application example;

[0041] Figure 4 This is a flowchart illustrating a method for identifying downlink data transmission anomalies in one embodiment;

[0042] Figure 5 This is a flowchart illustrating the steps for obtaining the number of consecutive abnormal downlink data packets in one embodiment.

[0043] Figure 6 This is a flowchart illustrating the steps for obtaining the number of system frames corresponding to consecutive abnormal downlink data packets in one embodiment.

[0044] Figure 7 This is a flowchart illustrating the process of determining PDCP downlink data transmission anomalies in an application example.

[0045] Figure 8 This is a flowchart illustrating the process of determining that there are no abnormalities in PDCP downlink data transmission in an application example.

[0046] Figure 9 This is a structural block diagram of a downlink data transmission anomaly identification device in one embodiment;

[0047] Figure 10 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0049] like Figure 1 The diagram shows a schematic of PDCP downlink data transmission. In 5G network transmission, when the sequence number of the PDCP data packet received by the UE (User Equipment) is 6515, the next one to be received should be 6516. In the diagram, RX_NEXT represents the sequence number of the next PDCP data packet that the UE expects to receive.

[0050] In order to more clearly understand the PDCP downlink data transmission method, the following will be described in conjunction with application examples, and the specific process is as follows:

[0051] In the NSA network (representing the network mode of 5G non-independent networking), after a RLF (Radio Link Failure, radio link failure), the UE performs re-registration, and then the network requires RRC (Radio Resource Control, also known as Radio Resource Management (RRM) or Radio Resource Allocation (RRA)) re-establishment (rrcConnectionReestablishment). After the re-establishment of the radio resource control layer of LTE (Long Term Evolution, a communication standard), the NR (New Radio) performs reconfiguration of the NR RRC through the air interface, which includes the re-establishment of the PDCP, as shown in the following procedure, which is the log procedure of the NR RRC reconfiguration.

[0052]

[0053]

[0054] As shown in Figure 2 , if the last PDCP sequence number received by the UE in the NR channel before the PDCP re-establishment is 21349, the next PDCP PDU that the UE waits for will be 21350, i.e. RX_NEXT is 21350. During the PDCP re-establishment, according to the chapter "5.1.2 PDCP entity re-establishment" of the protocol 38.323, the AM DRB (AM, Acknowledged Mode, Data Radio Bearer) does not need to reset the value of RX_NEXT, i.e. the PDCP receiving end still needs to receive the RX_NEXT before the PDCP re-establishment. Among them, AM represents the acknowledged mode, which is one of the three data transmission modes of the RLC layer, i.e. when the receiving end receives the data sent by the sending end and sends an ACK to the sending end for confirmation, the sending end can continue to send data, which can better guarantee the integrity of data transmission.

[0055] However, after the PDCP re-establishment, the network may send PDCP data packets to the UE from 0, as shown in Figure 3a . From the first registration to LTE to the subsequent addition of NR, the PDCP data packets sent by the network are continuous, as shown in Figure 3b and 3cAs shown, the transmitted PDCP data packet sequence numbers are 1, 2, … 12 and 416, 417 … 423, but none of them is the data packet expected by the UE. At this time, since the sequence numbers of the PDCP data packets transmitted by the network and the data packets expected by the UE are quite different, the UE will discard all the received data packets, resulting in no data at the upper layer.

[0056] In one embodiment, as shown, a downlink data transmission exception identification method is provided, wherein the downlink transmission exception of PDCP (Packet Data Convergence Protocol) of LTE (Long Term Evolution) and NR (New Radio) can be monitored by adding a downlink exception monitoring function (DEM) at the PDCP layer to implement the method. The embodiment takes the method applied to a terminal as an example. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction of the terminal and the server. In the embodiment, the method includes the following steps: Figure 4 Step S402, monitoring the data identifier of the downlink data packet received by the terminal.

[0057] Wherein, the downlink data packet represents the data packet sent to the terminal by the PDCP layer.

[0058] Wherein, the data identifier is an identifier representing the uniqueness of the downlink data packet, for example, the data identifier can be the sequence number of the downlink data packet.

[0059] In a specific implementation, during data transmission, the PDCP layer saves the received PDCP service data unit in the PDCP downlink buffer queue, then compresses, encrypts, and adds a PDCP sequence number (SN) header to the PDCP service data unit to form a PDCP PDU (Protocol Data Unit), which is used as a downlink data packet. The sequence number is the data identifier of the downlink data packet. Finally, the PDCP layer sends the downlink data packet carrying the data identifier to the terminal, so that the data identifier of the downlink data packet received by the terminal can be monitored.

[0060] Step S404, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, the data parameters of the continuous abnormal downlink data packet received by the terminal are obtained; wherein, the abnormal downlink data packet is the downlink data packet whose data identifier does not conform to the target data identifier.

[0061]

[0062] ​The target data identifier indicates a data identifier of a downlink data packet expected to be received by the terminal, and is determined according to a data identifier of a downlink data packet received by the terminal last time.

[0063] The data parameter can be a number of continuous abnormal downlink data packets received by the terminal, or a number of system frames corresponding to the continuous abnormal downlink data packets received by the terminal.

[0064] In a specific implementation, because the data transmission of the PDCP downlink user plane has a strict transmission sequence, the data identifier of the downlink data packet received by the terminal last time is first acquired, and the target data identifier is obtained according to a preset identifier calculation relationship and the data identifier last time. For example, the determination method of the target data identifier can be represented as: target data identifier = last time data identifier + d, where d represents a difference value of data identifiers of adjacent downlink data packets. If a sequence number is used as the data identifier of the downlink data packet, the difference d of the sequence numbers of adjacent downlink data packets is 1, and the sequence number of the downlink data packet expected to be received by the terminal is equal to the sequence number of the downlink data packet received by the terminal last time + 1. For example, if the downlink data packet received last time has a sequence number of 1300, the downlink data packet has a sequence number of 1301, and the downlink data packet with the sequence number of 1301 is the downlink data packet expected to be received by the terminal.

[0065] However, in an actual transmission process, the downlink data packet received by the terminal is not necessarily the downlink data packet expected to be received, and therefore, the downlink data packet received by the terminal needs to be monitored. If it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, the downlink data packet with the data identifier not conforming to the target data identifier is regarded as an abnormal downlink data packet, and a preset counter is started to count, and a count value accumulated by the counter is used as the data parameter of the continuous abnormal downlink data packet received by the terminal.

[0066] In step S406, if the data parameter satisfies a preset abnormality determination condition, it is confirmed that the downlink data transmission is abnormal, and an abnormality recovery instruction is generated. The abnormality recovery instruction is used to trigger the terminal to start a recovery mechanism.

[0067] The abnormality determination condition can be that the data parameter exceeds a preset data parameter threshold.

[0068] Further, in an embodiment, the step of determining whether the data parameter satisfies the preset abnormality determination condition includes: acquiring a data parameter threshold corresponding to the data parameter; and comparing the data parameter with the preset data parameter threshold. If the data parameter exceeds the data parameter threshold, it is determined that the data parameter satisfies the abnormality determination condition.

[0069] In a specific implementation, condition 1: if the number of consecutive abnormal downlink data packets is taken as the data parameter, the determining step includes: obtaining a number threshold of consecutive abnormal downlink data packets as an abnormal data packet number threshold, comparing the actual obtained abnormal data packet number of consecutive abnormal downlink data packets with the abnormal data packet number threshold, and if the actual obtained abnormal data packet number exceeds the abnormal data packet number threshold, determining that the number of obtained consecutive abnormal downlink data packets meets the preset abnormal determination condition.

[0070] And / or, condition 2: if the number of consecutive abnormal downlink data packets corresponding to system frames is taken as the data parameter, the determining step includes: obtaining a number threshold of consecutive abnormal downlink data packets corresponding to system frames as an abnormal frame number threshold, comparing the actual obtained abnormal frame number of consecutive abnormal downlink data packets corresponding to system frames with the abnormal frame number threshold, and if the abnormal frame number exceeds the abnormal frame number threshold, determining that the number of consecutive abnormal downlink data packets corresponding to system frames meets the preset abnormal determination condition.

[0071] If the number of consecutive abnormal downlink data packets received by the terminal exceeds the abnormal data packet number threshold, denoted as condition 1, and the number of consecutive abnormal downlink data packets corresponding to system frames received by the terminal, denoted as condition 2, when either condition 1 or condition 2 is met or both conditions are met, it is determined that the PDCP downlink data transmission is abnormal, the terminal generates an abnormal recovery instruction, and the terminal starts the recovery mechanism to normally transmit the downlink data packets from the expected downlink data packets.

[0072] In the above downlink data transmission abnormality identification method, the data identifier of the downlink data packet received by the terminal is monitored, so that when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, the data parameter of the consecutive abnormal downlink data packet received by the terminal is obtained; wherein the abnormal downlink data packet is the downlink data packet whose data identifier does not conform to the target data identifier, and it is determined whether the obtained data parameter meets the preset abnormal determination condition, when the data parameter meets the abnormal determination condition, it is determined that the downlink data transmission is abnormal, an abnormal recovery instruction is generated, and the terminal starts the recovery mechanism. This method uses the data parameter of the consecutive abnormal downlink data packet to directly determine the abnormality of the downlink data transmission, which can accurately determine whether the downlink data transmission is abnormal, so that the terminal can be triggered to start the recovery mechanism in time, the waiting time is reduced, the transmission efficiency of the downlink data is improved, and the problem of long waiting time and low data transmission rate in the traditional method of not detecting the transmission abnormality and only triggering the recovery mechanism when no data is received within a fixed time is avoided.

[0073] In one embodiment, the step S404 further includes: when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining the number of the continuous abnormal downlink data packets received by the terminal as the data parameter of the continuous abnormal downlink data packets received by the terminal.

[0074] Further, in one embodiment, as shown in Figure 5 when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, the step of obtaining the number of the continuous abnormal downlink data packets received by the terminal specifically includes:

[0075] S502, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, starting a preset first counter and counting by using the first counter; and each time it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, performing an increment operation on the first counter.

[0076] S504, obtaining the counting value accumulated by the first counter currently as the number of the continuous abnormal downlink data packets received by the terminal.

[0077] In the embodiment, the number of the continuous abnormal downlink data packets received by the terminal is obtained as the data parameter of the continuous abnormal downlink data packets received by the terminal, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, the preset first counter is started, and the counting value accumulated by the first counter is obtained as the number of the continuous abnormal downlink data packets received by the terminal, so as to accurately determine the PDCP lower layer data transmission according to the number of the continuous abnormal downlink data packets received by the terminal and the corresponding data parameter threshold, and provide a basis for triggering the terminal to start the abnormal recovery mechanism.

[0078] In one embodiment, the step S404 further includes: when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtaining the number of the continuous abnormal downlink data packets received by the terminal as the data parameter of the continuous abnormal downlink data packets received by the terminal.

[0079] Further, in one embodiment, as shown in Figure 6 when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, the step of obtaining the number of the continuous abnormal downlink data packets received by the terminal specifically includes:

[0080] Step S602, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, a preset second counter is started, and the second counter is counted; each time it is monitored that the data identifier of the contained downlink data packet does not conform to the target data identifier, the second counter is added by one.

[0081] Step S604, the count value accumulated by the second counter is obtained as the number of the system frame corresponding to the continuous abnormal downlink data packet received by the terminal.

[0082] In the embodiment, the number of the system frame corresponding to the continuous abnormal downlink data packet received by the terminal is obtained as the data parameter of the continuous abnormal downlink data packet received by the terminal, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, the preset second counter is started, and the count value accumulated by the second counter is obtained as the number of the system frame corresponding to the continuous abnormal downlink data packet received by the terminal, so as to accurately determine the PDCP lower layer data transmission according to the number of the system frame corresponding to the continuous abnormal downlink data packet received by the terminal and the corresponding data parameter threshold, and provide a basis for triggering the terminal to start the abnormal recovery mechanism.

[0083] In one embodiment, the above method further comprises: if the data identifier of the downlink data packet received by the terminal conforms to the target data identifier in the counting process of the first counter / second counter and under the condition that the data parameter does not satisfy the abnormal determination condition, it is determined that the downlink data transmission is normal, and the first counter and the second counter are cleared.

[0084] In the specific implementation, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, the preset first counter and / or the second counter are started to count, wherein the first counter and the second counter are both used to count the data parameter of the continuous abnormal downlink data packet, therefore, if the data identifier of the downlink data packet received by the terminal conforms to the target data identifier in the counting process of the first counter / second counter, the abnormal downlink data packet will not be continuous, the counting rule of the first counter and the second counter is broken, and if the data parameter accumulated by the first counter / second counter does not satisfy the abnormal determination condition at the same time, that is, the data parameter is less than the preset data parameter threshold, it is determined that the data transmission process of the downlink data packet sent by the PDCP to the terminal is normal, and the first counter and the second counter are both cleared. When it is monitored again that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier in the process of monitoring the data identifier of the downlink data packet received by the terminal, the first counter / second counter is restarted to count, and so on, so as to realize the real-time identification and processing of the downlink data transmission abnormality.

[0085] In the embodiment, the first counter and the second counter are both cleared when the data identifier of the downlink data packet received by the terminal meets the target data identifier during the counting of the first counter / second counter and under the condition that the data parameter does not meet the abnormality determination condition, so that the first counter / second counter can start counting from 0 when the data identifier of the downlink data packet received by the terminal does not meet the target data identifier next time.

[0086] In one embodiment, after the abnormality recovery instruction is generated in the step S406, the first counter and the second counter are cleared.

[0087] In the embodiment, the first counter and the second counter are both cleared when the data identifier of the downlink data packet received by the terminal meets the target data identifier during the counting of the first counter / second counter and under the condition that the data parameter does not meet the abnormality determination condition, so that the first counter / second counter can start counting from 0 when the data identifier of the downlink data packet received by the terminal does not meet the target data identifier next time.

[0088] To make the technical solutions provided by the embodiments of the present application clearer, the following will combine Figure 7 and Figure 8 to describe the solutions, Figure 7 is a flowchart for determining the abnormality of PDCP downlink data transmission in an application example, and the specific process is as follows:

[0089] In the process of monitoring the PDCP downlink data transmission, when the PDCP downlink PDU (protocol data unit, equivalent to a downlink data packet) sequence number (equivalent to a data identifier) does not meet RX_NEXT (equivalent to a target data identifier), DEM (i.e., an abnormality monitoring function added in the PDCP layer) controls to start a counter c.

[0090] When the counting value accumulated by the counter meets any one of the abnormality determination conditions, it is determined that the PDCP downlink transmission is abnormal, DEM starts an abnormality recovery mechanism through the upper layer, and resets the counter. The condition 1 and the condition 2 are respectively that the number of continuous abnormal data packets received by the terminal exceeds a preset threshold of the number of abnormal data packets, and the number of continuous abnormal downlink data packets received by the terminal exceeds a preset threshold of the number of abnormal frames.

[0091] Figure 8 is a flowchart for determining the abnormality of PDCP downlink data transmission in an application example, and the specific process is as follows:

[0092] During the monitoring of PDCP downlink data transmission, when the sequence number (equivalent to data identifier) ​​of the PDCP downlink PDU (protocol data unit, equivalent to downlink data packet) is found to be inconsistent with RX_NEXT (equivalent to target data identifier), the DEM (i.e., the anomaly monitoring function added under the PDCP layer) controls the start of counter c.

[0093] If the accumulated count value of the counter does not meet either condition 1 or condition 2, then it is determined that there is no abnormality in the PDCP downlink data transmission, and the counter c is reset. Conditions 1 and 2 are the same. Figure 7 Conditions 1 and 2 are the same, and will not be repeated here.

[0094] It should be understood that, although Figures 4-8 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figures 4-8 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0095] In one embodiment, such as Figure 9 As shown, a downlink data transmission anomaly identification device is provided, comprising: a monitoring module 902, a data parameter acquisition module 904, and an instruction generation module 906, wherein:

[0096] Monitoring module 902 is used to monitor the data identifier of downlink data packets received by the terminal;

[0097] The data parameter acquisition module 904 is used to acquire the data parameters of the continuously abnormal downlink data packets received by the terminal when it is detected that the data identifier of the downlink data packets received by the terminal does not conform to the target data identifier; the abnormal downlink data packets are downlink data packets whose data identifiers do not conform to the target data identifier.

[0098] The instruction generation module 906 is used to confirm that there is an anomaly in the downlink data transmission if the data parameters meet the preset anomaly judgment conditions, and to generate an anomaly recovery instruction; the anomaly recovery instruction is used to trigger the terminal to start the recovery mechanism.

[0099] In an embodiment, the data parameter obtaining module 904 is further configured to, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtain the number of the continuous abnormal downlink data packets received by the terminal as the data parameter of the continuous abnormal downlink data packets received by the terminal.

[0100] In an embodiment, the data parameter obtaining module 904 is further configured to, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, start a preset first counter and count by using the first counter; each time it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, perform an increment operation on the first counter; and obtain the current accumulated count value of the first counter as the number of the continuous abnormal downlink data packets received by the terminal.

[0101] In an embodiment, the data parameter obtaining module 904 is further configured to, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, obtain the number of the system frames corresponding to the continuous abnormal downlink data packets received by the terminal as the data parameter of the continuous abnormal downlink data packets received by the terminal.

[0102] In an embodiment, the data parameter obtaining module 904 is further configured to, when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, start a preset second counter and count by using the second counter; each time it is monitored that the system frame containing the downlink data packet whose data identifier does not conform to the target data identifier, perform an increment operation on the second counter; and obtain the current accumulated count value of the second counter as the number of the system frames corresponding to the continuous abnormal downlink data packets received by the terminal.

[0103] In an embodiment, the apparatus further comprises:

[0104] The clearing module is configured to, if it is monitored that the data identifier of the downlink data packet received by the terminal conforms to the target data identifier during the counting process of the first counter / second counter and under the condition that the data parameter does not satisfy the abnormality determination condition, determine that the downlink data transmission is normal, and clear the first counter and the second counter.

[0105] In an embodiment, the apparatus further comprises:

[0106] The threshold obtaining module is configured to obtain a data parameter threshold corresponding to the data parameter.

[0107] The comparison module is configured to compare the data parameter with a preset data parameter threshold, and determine that the data parameter satisfies the abnormality determination condition if the data parameter exceeds the data parameter threshold.

[0108] It should be noted that the downlink data transmission abnormality identification device of the present application corresponds to the downlink data transmission abnormality identification method of the present application. The technical features and advantages described in the embodiments of the downlink data transmission abnormality identification method are applicable to the embodiments of the downlink data transmission abnormality identification device. For specific content, please refer to the description in the method embodiments. Here, no further description is given, and this is hereby declared.

[0109] In addition, each module in the downlink data transmission abnormality identification device described above can be implemented wholly or partially by software, hardware, and combinations thereof. Each module described above can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory in the computer device in software form, so as to be called and executed by the processor to perform the operations corresponding to each module.

[0110] In one embodiment, a computer device is provided, which can be a terminal, and its internal structure diagram can be as shown in Figure 10 The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected through a system bus. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operating system and the computer program in the non-volatile storage medium to run. The communication interface of the computer device is configured to perform wired or wireless communication with an external terminal. The wireless communication can be achieved through WIFI, a carrier network, NFC (Near Field Communication), or other technologies. The computer program is executed by the processor to implement a downlink data transmission abnormality identification method. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer overlaid on the display screen, or a key, trackball, or touchpad arranged on the shell of the computer device. The input device can also be an external keyboard, touchpad, or mouse, etc.

[0111] Those skilled in the art can understand that Figure 10 the structure shown in the above description is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0112] In one embodiment, a computer device is provided, comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0113] monitoring a data identifier of a downlink data packet received by a terminal;

[0114] when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to a target data identifier, obtaining a data parameter of a continuous abnormal downlink data packet received by the terminal; the abnormal downlink data packet is a downlink data packet whose data identifier does not conform to the target data identifier;

[0115] if the data parameter satisfies a preset abnormality determination condition, confirming that there is an abnormality in downlink data transmission, and generating an abnormality recovery instruction; the abnormality recovery instruction is used to trigger the terminal to start a recovery mechanism.

[0116] In one embodiment, a computer device is also provided, comprising a memory and a processor, the memory storing a computer program, and the processor implementing the steps in the above method embodiments when executing the computer program.

[0117] In one embodiment, a computer readable storage medium is provided, storing a computer program thereon, and the computer program is executed by a processor to implement the following steps:

[0118] monitoring a data identifier of a downlink data packet received by a terminal;

[0119] when it is monitored that the data identifier of the downlink data packet received by the terminal does not conform to a target data identifier, obtaining a data parameter of a continuous abnormal downlink data packet received by the terminal; the abnormal downlink data packet is a downlink data packet whose data identifier does not conform to the target data identifier;

[0120] if the data parameter satisfies a preset abnormality determination condition, confirming that there is an abnormality in downlink data transmission, and generating an abnormality recovery instruction; the abnormality recovery instruction is used to trigger the terminal to start a recovery mechanism.

[0121] In one embodiment, a computer readable storage medium is provided, storing a computer program thereon, and the computer program is executed by a processor to implement the steps in the above method embodiments.

[0122] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to memory, storage, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration but not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0123] Any combination of the technical features of the above embodiments can be made. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described, but as long as the combination of the technical features does not exist, it should be considered as the scope of the present application.

[0124] The above embodiments only express several implementation manners of the present application, and the description is more specific and detailed, but it should not be understood as a limitation on the scope of the patent. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, some modifications and improvements can be made, which are all within the protection scope of the present application. Therefore, the protection scope of the patent of the present application should be subject to the appended claims.

Claims

1. A method for identifying downlink data transmission anomalies, characterized in that, The method includes: The data identifier of the downlink data packets received by the monitoring terminal; When it is detected that the data identifier of the downlink data packet received by the terminal does not match the target data identifier, the number of consecutive abnormal downlink data packets received by the terminal and the number of corresponding system frames are obtained as data parameters; the abnormal downlink data packets are downlink data packets whose data identifiers do not match the target data identifier. If the number of consecutive abnormal downlink data packets and the corresponding number of system frames both exceed their respective thresholds, then an abnormality in downlink data transmission is confirmed, and an abnormality recovery instruction is generated; the abnormality recovery instruction is used to trigger the terminal to start the recovery mechanism.

2. The method according to claim 1, characterized in that, When it is detected that the data identifier of the downlink data packet received by the terminal does not match the target data identifier, the number of consecutive abnormal downlink data packets received by the terminal is obtained, including: When it is detected that the data identifier of the downlink data packet received by the terminal does not match the target data identifier, a preset first counter is started and counted; each time the data identifier of the downlink data packet received by the terminal does not match the target data identifier, the first counter is incremented by one. The current accumulated count value of the first counter is obtained as the number of consecutive abnormal downlink data packets received by the terminal.

3. The method according to claim 1, characterized in that, When it is detected that the data identifier of the downlink data packet received by the terminal does not match the target data identifier, the number of system frames corresponding to the consecutive abnormal downlink data packets received by the terminal is obtained, including: When it is detected that the data identifier of the downlink data packet received by the terminal does not match the target data identifier, a preset second counter is started and counted; for each system frame in which the data identifier of the included downlink data packet does not match the target data identifier, the second counter is incremented by one. The current accumulated count value of the second counter is obtained and used as the number of system frames corresponding to the continuous abnormal downlink data packets received by the terminal.

4. The method according to any one of claims 1 to 3, characterized in that, Also includes: If, during the counting process of the first counter / second counter, the number of consecutive abnormal downlink data packets and the number of corresponding system frames both exceed their respective number thresholds, and the data identifier of the downlink data packet received by the terminal matches the target data identifier, then the downlink data transmission is determined to be normal, and the first counter and the second counter are cleared.

5. The method according to any one of claims 1 to 3, characterized in that, The downlink data packet represents a data packet sent from the PDCP layer to the terminal; The target data identifier represents the data identifier of the downlink data packet that the terminal expects to receive, and the target data identifier is determined based on the data identifier of the downlink data packet previously received by the terminal.

6. A downlink data transmission anomaly identification device, characterized in that, The device includes: The monitoring module is used to monitor the data identifiers of downlink data packets received by the terminal; The data parameter acquisition module is used to acquire the number of consecutive abnormal downlink data packets received by the terminal and the number of corresponding system frames as data parameters when it is detected that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier; the abnormal downlink data packet is the downlink data packet whose data identifier does not conform to the target data identifier. The instruction generation module is used to confirm that there is an anomaly in the downlink data transmission if the number of consecutive abnormal downlink data packets and the number of corresponding system frames both exceed their respective number thresholds, and to generate an anomaly recovery instruction; the anomaly recovery instruction is used to trigger the terminal to start the recovery mechanism.

7. The apparatus according to claim 6, characterized in that, The data parameter acquisition module is also used to start a preset first counter and use the first counter to count when it is detected that the data identifier of the downlink data packet received by the terminal does not match the target data identifier. If the data identifier of the downlink data packet received by the terminal does not match the target data identifier, the first counter is incremented by one. The current accumulated count value of the first counter is obtained as the number of consecutive abnormal downlink data packets received by the terminal.

8. The apparatus according to claim 6, characterized in that, The data parameter acquisition module is further configured to, when it is detected that the data identifier of the downlink data packet received by the terminal does not conform to the target data identifier, start a preset second counter and use the second counter to count; for each system frame in which the data identifier of the included downlink data packet does not conform to the target data identifier is detected, increment the second counter by one; and obtain the current accumulated count value of the second counter as the number of system frames corresponding to the continuous abnormal downlink data packets received by the terminal.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images