Transmission anomaly diagnosis method and apparatus, electronic device, and storage medium

Abstract

The present application relates to the technical field of communications, and specifically provides a transmission anomaly diagnosis method and apparatus, an electronic device, and a storage medium. The transmission anomaly diagnosis method comprises: when a data interaction message is transmitted between a plurality of devices by means of a target transmission connection, determining a device type corresponding to a device receiving the data interaction message; on the basis of a first recording rule corresponding to the device type, performing packet information extraction on protocol packets in the data interaction message to obtain a packet information set; on the basis of a second recording rule corresponding to the device type, performing link information extraction on the protocol packets in the data interaction message to obtain a link information set; and when it is determined that transmission anomaly occurs to the target transmission connection, performing transmission anomaly diagnosis on the basis of the packet information set and the link information set which correspond to the target connection. Therefore, transmission anomaly diagnosis is performed by means of diagnosis related information which is extracted and recorded in real time, so that the tedious steps of transmission anomaly diagnosis are simplified.

Description

Method, device, electronic device and storage medium for transmission abnormality diagnosis Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device, electronic device and storage medium for diagnosing transmission anomalies. Background Art

[0002] In a communication scenario, if a transmission connection experiences a transmission anomaly (for example, an abnormal disconnection of the transmission connection), the transmission anomaly is usually diagnosed through device logs.

[0003] In related technologies, because it is often difficult to determine the specific message exchange process between devices and the probability of transmission anomalies is usually low, multiple reproduction tests are usually conducted in conjunction with device logs. Packet capture tools are used to capture on-site information when an anomaly occurs (i.e., information related to message exchanges during transmission anomalies). Based on this on-site information and device logs, transmission anomaly diagnosis is performed. However, using this approach, transmission anomaly diagnosis is relatively cumbersome.

[0004] Summary of the Invention

[0005] The purpose of the embodiments of the present application is to provide a method, device, electronic device and storage medium for transmission anomaly diagnosis, so as to simplify the tedious operations of transmission anomaly diagnosis when performing transmission anomaly diagnosis.

[0006] On the one hand, an embodiment of the present application provides a method for transmission anomaly diagnosis, including: when transmitting data interaction messages between multiple devices through a target transmission connection, determining the device type corresponding to the device receiving the data interaction message; according to a first recording rule corresponding to the device type, extracting packet information for the protocol packet in the data interaction message to obtain a packet information set; according to a second recording rule corresponding to the device type, extracting link information for the protocol packet in the data interaction message to obtain a link information set; the link information set is used to determine the transmission link and processing node of the data interaction message; when it is determined that there is a transmission anomaly in the target transmission connection, transmission anomaly diagnosis is performed based on the packet information set and link information set corresponding to the target connection.

[0007] In one embodiment, according to the first recording rule corresponding to the device type, packet information is extracted for the protocol packet in the data interaction message to obtain a packet information set, including: parsing the data interaction message to obtain the packet structure information of each protocol packet in the data interaction message; the data interaction message contains at least one protocol packet; for each protocol packet and its corresponding packet structure information, the following steps are performed: according to the device type and the data packet header in the packet structure information, the protocol type of the protocol packet is determined; the protocol packet type in the packet structure information is obtained; if the protocol packet type is a specified type, the number of packets in the packet structure information is obtained, and a packet information set including the protocol type, the protocol packet type and the number of packets is generated; if the protocol packet type is a non-specified type, a packet information set including the data packet header and the protocol type is generated.

[0008] In one embodiment, the protocol type of the protocol packet is determined based on the device type and the data packet header in the packet structure information, including: if the device type is a business server, then determining whether each data packet header is empty; and determining the protocol type based on the judgment result; the packet structure information contains at least one data packet header; if the device type is a proxy server, obtaining the protocol sending and receiving fields contained in the data packet header, and obtaining the protocol type corresponding to the protocol sending and receiving fields.

[0009] In one embodiment, the method further includes: if the packet structure information includes a packet combination field, determining the fragment length of the protocol packet fragment received by the protocol packet according to the packet combination field; and adding the fragment length to the packet information set.

[0010] In one embodiment, according to the second recording rule corresponding to the device type, link information is extracted for the protocol package in the data interaction message to obtain a link information set, including: if the device type is a business server, when determining to execute the protocol package, obtaining the command keyword in the packet structure information; generating a link information set containing the command keyword; when determining to send a response message for the data interaction message, setting the message response keyword; and adding the message response keyword to the link information set.

[0011] In one embodiment, according to the second recording rule corresponding to the device type, link information is extracted for the protocol packet in the data interaction message to obtain a link information set, including: if the device type is a proxy server, determining the link transmission object and transmission channel of the data interaction message; generating a link information set based on the link transmission object and transmission channel.

[0012] In one embodiment, when it is determined that a transmission anomaly exists in a target transmission connection, before performing a transmission anomaly diagnosis based on a packet information set and a link information set corresponding to the target connection, the method further includes: determining whether there is a circular queue corresponding to the target transmission connection; the circular queue and the target transmission connection are one-to-one corresponding; if there is a circular queue, the packet information set and the link information set corresponding to each protocol packet of the data interaction message are added to the circular queue; if there is no circular queue, a circular queue corresponding to the target transmission connection is established, and the packet information set and the link information set corresponding to each protocol packet of the data interaction message are added to the circular queue.

[0013] In one embodiment, when it is determined that a transmission anomaly exists in a target transmission connection, a transmission anomaly diagnosis is performed based on the packet information set and link information set corresponding to the target connection, including: when it is determined that a transmission anomaly exists in the target transmission connection, the packet information set and link information set corresponding to the latest specified number of protocol packets are filtered out from a circular queue; and the transmission anomaly is diagnosed based on the filtered packet information set and link information set.

[0014] On the one hand, an embodiment of the present application provides a device for transmission anomaly diagnosis, including: a determination unit, for determining the device type corresponding to the device receiving the data interaction message when transmitting the data interaction message between multiple devices through a target transmission connection; an extraction unit, for extracting packet information for the protocol packet in the data interaction message according to a first recording rule corresponding to the device type, and obtaining a packet information set; an acquisition unit, for extracting link information for the protocol packet in the data interaction message according to a second recording rule corresponding to the device type, and obtaining a link information set; the link information set is used to determine the transmission link and processing node of the data interaction message; a diagnosis unit, for performing transmission anomaly diagnosis based on the packet information set and link information set corresponding to the target connection when determining that there is a transmission anomaly in the target transmission connection.

[0015] In one embodiment, the extraction unit is used to: parse the data interaction message to obtain the packet structure information of each protocol packet in the data interaction message; the data interaction message contains at least one protocol packet; for each protocol packet and its corresponding packet structure information, perform the following steps: determine the protocol type of the protocol packet based on the device type and the data packet header in the packet structure information; obtain the protocol packet type in the packet structure information; if the protocol packet type is a specified type, obtain the number of packets in the packet structure information, and generate a packet information set including the protocol type, protocol packet type and the number of packets; if the protocol packet type is a non-specified type, generate a packet information set including the data packet header and the protocol type.

[0016] In one embodiment, the extraction unit is used to: if the device type is a business server, determine whether each data packet header is empty; and determine the protocol type based on the judgment result; the packet structure information contains at least one data packet header; if the device type is a proxy server, obtain the protocol sending and receiving fields contained in the data packet header, and obtain the protocol type corresponding to the protocol sending and receiving fields.

[0017] In one embodiment, the extraction unit is further configured to: if the packet structure information includes a packet combination field, determine the fragment length of the protocol packet fragment received by the protocol packet according to the packet combination field; and add the fragment length to the packet information set.

[0018] In one embodiment, the acquisition unit is used to: if the device type is a business server, obtain the command keyword in the package structure information when determining to execute the protocol package; generate a link information set containing the command keyword; when determining to send a response message for the data interaction message, set the message response keyword; and add the message response keyword to the link information set.

[0019] In one embodiment, the obtaining unit is configured to: if the device type is a proxy server, determine a link transmission object and a transmission channel of the data interaction message; and generate a link information set according to the link transmission object and the transmission channel.

[0020] In one embodiment, the diagnostic unit is also used to: determine whether there is a circular queue corresponding to the target transmission connection; the circular queue and the target transmission connection are one-to-one corresponding; if there is a circular queue, the packet information set and link information set corresponding to each protocol packet of the data interaction message are added to the circular queue; if there is no circular queue, a circular queue corresponding to the target transmission connection is established, and the packet information set and link information set corresponding to each protocol packet of the data interaction message are added to the circular queue.

[0021] In one embodiment, the diagnostic unit is used to: when it is determined that there is a transmission anomaly in the target transmission connection, filter out the packet information set and link information set corresponding to the latest specified number of protocol packets from the circular queue; and diagnose the transmission anomaly based on the filtered packet information set and link information set.

[0022] On the one hand, an embodiment of the present application provides an electronic device, comprising: a processor; and a memory storing computer instructions, the computer instructions being used to enable the processor to execute the steps of the method provided in any of the various optional implementations of transmission abnormality diagnosis described above.

[0023] On the one hand, an embodiment of the present application provides a storage medium storing computer instructions, which are used to enable a computer to execute the steps of the method provided in any of the various optional implementations of transmission abnormality diagnosis described above.

[0024] In the transmission anomaly diagnosis method, device, electronic device and storage medium provided by the embodiment of the present application, when a data interaction message is transmitted between multiple devices through a target transmission connection, the device type corresponding to the device receiving the data interaction message is determined; according to the first recording rule corresponding to the device type, packet information is extracted for the protocol packet in the data interaction message to obtain a packet information set; according to the second recording rule corresponding to the device type, link information is extracted for the protocol packet in the data interaction message to obtain a link information set; the link information set is used to determine the transmission link and processing node of the data interaction message; when it is determined that there is a transmission anomaly in the target transmission connection, the transmission anomaly diagnosis is performed based on the packet information set and link information set corresponding to the target connection. In this way, during the message transmission process, the extraction and recording of diagnosis-related information are performed in real time, and when a transmission anomaly occurs, the transmission anomaly diagnosis can be performed directly by recording data, which simplifies the tedious steps of transmission anomaly diagnosis and improves the efficiency of transmission anomaly diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the specific implementation methods of this application or the technical solutions in related technologies, the following is a brief introduction to the drawings required for use in the specific implementation methods or related technical descriptions. Obviously, the drawings described below are some implementation methods of this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0026] FIG1 is a flow chart of a method for diagnosing transmission anomalies in an embodiment of the present application.

[0027] FIG2 is a schematic diagram of a request message forwarding in an embodiment of the present application.

[0028] FIG3 is a schematic diagram of a response message forwarding in an embodiment of the present application.

[0029] FIG4 is a structural block diagram of a device for transmitting abnormality diagnosis in an embodiment of the present application.

[0030] FIG5 is a schematic structural diagram of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0031] The technical solutions of the present application will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. In addition, the technical features involved in the different embodiments of the present application described below can be combined with each other as long as they do not conflict with each other.

[0032] First, some of the terms involved in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0033] Terminal device: can be a mobile terminal, fixed terminal or portable terminal, such as a mobile phone, station, unit, device, multimedia computer, multimedia tablet, Internet node, communicator, desktop computer, laptop computer, notebook computer, netbook computer, tablet computer, personal communication system device, personal navigation device, personal digital assistant, audio / video player, digital camera / camcorder, positioning device, television receiver, radio broadcast receiver, e-book device, gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. It is also foreseeable that the terminal device can support any type of user interface (such as wearable device), etc.

[0034] Server: It can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, and big data and artificial intelligence platforms.

[0035] OceanBase Communication Protocol: An application layer protocol built on top of the Transmission Control Protocol (TCP), OceanBase is the general term for communication protocols between clients, proxy servers (OBProxy), and business servers (OBServer). It includes the following three communication protocols: MySQL, OceanBase 2.0, and Compressed MySQL.

[0036] MySQL Protocol: This protocol is used for communication between clients and servers. It supports transparent encryption and compression using Secure Sockets Layer (SSL), capability negotiation and authentication when establishing a connection between the client and server, and, after the connection is established, the server accepts commands from the client and returns the results of its execution.

[0037] Compressed MySQL protocol: A communication protocol based on the MySQL protocol, which includes compressed MySQL protocol. Different compression algorithms can be used to compress the MySQL protocol.

[0038] OceanBase 2.0 protocol: also known as the OB2.0 protocol, has all the functions that can be achieved by the MySQL protocol and the Compressed MySQL protocol. In addition, it also has the following functions: capability negotiation, full-link tracking of execution requests, and data verification.

[0039] The technical concept of this application is described below.

[0040] In communication scenarios, when different devices exchange messages, protocol-related issues often lead to transmission anomalies. Common protocol-related issues include: some packets not being sent in the same 2.0 protocol packet, incorrect protocol header information, extra packets being sent during reply, and packet merging anomalies caused by not appending an empty packet after the MySQL packet.

[0041] Traditionally, when a transmission anomaly occurs, diagnosis is typically performed using device logs. Specifically, because it's often difficult to determine the specific message exchange process between devices, and the probability of a transmission anomaly occurring is typically low, multiple replication tests are typically conducted using device logs. Packet capture tools are used to capture on-site information when the anomaly recurs, and this information is used to diagnose the transmission anomaly.

[0042] However, this usually continuously increases the device logs, and requires the use of packet capture tools to capture on-site information. It is also necessary to correlate the device logs and on-site information to perform transmission anomaly diagnosis. Obviously, the transmission anomaly diagnosis operation is relatively cumbersome.

[0043] Based on the defects of the above-mentioned related technologies, the embodiments of the present application provide a method, device, electronic device and storage medium for transmission anomaly diagnosis, aiming to simplify the tedious operations of transmission anomaly diagnosis when performing transmission anomaly diagnosis.

[0044] An embodiment of the present application provides a method for diagnosing transmission anomalies, which can be applied to electronic devices. The present application does not limit the type of electronic device, and it can be any type of device suitable for implementation, such as a smartphone, tablet computer, etc., and the present application will not elaborate on this.

[0045] An application scenario includes a data transmission system and a monitoring device. The data transmission system includes a user device, a first device, and a second device. The monitoring system is used to monitor the data transmission system and diagnose transmission anomalies.

[0046] The device type of the first device is a proxy server. The device type of the second device is a service server.

[0047] The user equipment is used to send a message to the second device through the first device, and to receive a message returned by the second device through the first device.

[0048] The first device is used to convert a message sent by a user device and send the converted message to the second device, and is used to convert a message sent by the second device and send the converted message to the user device.

[0049] The second device is used to receive the message sent by the first device and to send the message to the first device.

[0050] A monitoring device is used to extract and record interaction information of data interaction messages received by the first device and / or the second device, obtain a packet information set and a link information set of the protocol packet in the data interaction message as a message interaction record, and when it is determined that a transmission anomaly exists in the target transmission connection, perform transmission anomaly diagnosis based on the latest message interaction record corresponding to the target transmission connection.

[0051] Optionally, the monitoring device may be a device outside the data transmission system, or may be the same device as the first device or the second device. The monitoring device may further include a data acquisition sub-device and an abnormality diagnosis sub-device, wherein there may be at least one data acquisition sub-device, and any data acquisition sub-device may be a device outside the data transmission system, or may be the same device as the first device or the second device. The abnormality diagnosis sub-device may be a device outside the data transmission system, or may be the same device as the first device or the second device.

[0052] As an example, if both the first device and the second device are data acquisition sub-devices, the first device and the second device extract and record the interaction information, and each sends the message interaction record to the anomaly diagnosis sub-device. Upon determining that a transmission anomaly exists in the target transmission connection, the anomaly diagnosis sub-device performs transmission anomaly diagnosis based on the latest message interaction record corresponding to the target transmission connection.

[0053] As another example, if the monitoring device and the first device are the same device, the first device can only extract and record information on the data interaction messages it receives, and when it determines that there is a transmission anomaly, it can diagnose the transmission anomaly based on the latest message interaction record recorded by itself.

[0054] As another example, if the monitoring device and the second device are the same device, the second device can only extract and record information on the data interaction messages it receives, and when it determines that there is a transmission anomaly, it can perform transmission anomaly diagnosis based on the latest message interaction record recorded by itself.

[0055] In an embodiment of the present application, transmission anomaly diagnosis can be performed in combination with the message interaction records corresponding to the first device and the second device respectively, or transmission anomaly diagnosis can be performed only based on the message interaction records corresponding to the first device or the second device.

[0056] The following describes a method for transmission abnormality diagnosis in an embodiment of the present application in combination with Figure 1 and the above-mentioned application scenario. Figure 1 is a flowchart of a method for transmission abnormality diagnosis in an embodiment of the present application, which is applied to the monitoring equipment in the above-mentioned application scenario. The specific implementation process of the method includes the following steps 100 to 103.

[0057] Step 100: When a data interaction message is transmitted between multiple devices via a target transmission connection, a device type corresponding to a device receiving the data interaction message is determined.

[0058] The target transmission connection is the connection between devices that currently transmit messages. Device types include proxy servers and service servers.

[0059] As an example, when data interaction messages are transmitted between devices in a data transmission system, if a first device receives a data interaction message from a user device or a second device, the device type is determined to be a proxy server.

[0060] As another example, when data interaction messages are transmitted between devices in a data transmission system, if a second device receives a data interaction message from a first device, the device type is determined to be a service server.

[0061] In one embodiment, data interaction messages received by the user equipment are not recorded. Therefore, if it is determined that the user equipment has received a data interaction message, the data recording is terminated, and only data interaction messages received by the proxy server and the service server are recorded.

[0062] Furthermore, if the monitoring device and the second device are the same device, and the monitoring device only monitors the second device for receipt of data interaction messages, that is, the device type of the monitoring device is always a service server, then step 100 may not be performed. Similarly, if the monitoring device and the first device are the same device, and the device type of the monitoring device is always a proxy server, then step 100 may not be performed.

[0063] Step 101: extracting packet information from protocol packets in a data interaction message according to a first recording rule corresponding to a device type to obtain a packet information set.

[0064] In one implementation, when executing step 101, the following steps S1011 to S1012 may be adopted.

[0065] S1011: Parse the data interaction message to obtain packet structure information of each protocol packet in the data interaction message.

[0066] The packet structure information includes the datagram header and protocol packet type, and may also include the number of packets of a specified protocol type. It should be noted that the smallest unit of communication between the proxy server (OBProxy) and the business server (OBServer) is the protocol packet (e.g., MySQL protocol packet). Therefore, monitoring is performed at the protocol packet granularity.

[0067] It should be noted that in the embodiments of this application, the packet structure of the protocol packet is designed based on the information requirements analysis for transmission anomaly diagnosis, so that the packet structure information contains various information required for anomaly diagnosis. Due to the different diagnostic requirements of the business server and the proxy server, corresponding packet structures are designed for the protocol packets of the business server and the proxy server respectively.

[0068] As an example, the packet structure information of the protocol packet in the data interaction message received by the service server is as follows:

[0069] In the above packet structure information, ObpCompressHeader obp_com_header_, Obp20Header obp20_header_, and ObpMysqHeader obp_mysql_header_ are three different datagram headers contained in the same packet structure. Obpcmd is used to identify the command keyword, pkt_type is used to identify the protocol packet type, processed is used to identify the message response keyword, and pkt_num_[] is used to determine the number of protocol packets of the specified type. rec_[] is a packet consolidation field used to determine the fragment length.

[0070] As another example, the packet structure information of the protocol packet in the data interaction message received by the proxy server is as follows:

[0071] S1012: For each protocol packet and its corresponding packet structure information, execute the following steps S1012-1 to S1012-4.

[0072] S1012-1: Determine the protocol type of the protocol packet according to the device type and the data message header in the packet structure information.

[0073] In one embodiment, the protocol type includes at least one of the following: MySQL protocol, Compressed MySQL protocol, and OceanBase 2.0 protocol.

[0074] In one implementation, when executing S1012-1, the following method may be used.

[0075] Method 1: If the device type is a service server, determine whether each data message header is empty; the packet structure information includes at least one data message header, and determine the protocol type based on the determination result.

[0076] In one implementation, the judgment results of whether each data message header is empty are determined, and a combination of the judgment results is obtained, corresponding to the set protocol type.

[0077] As an example, setting 0 indicates that the data packet header is empty, and setting 1 indicates that the data packet header is not empty. The data packet headers included in the packet structure information include ObpCompressHeader, Obp20Header, and ObpMysqHeader. If the combination of the judgment results corresponding to ObpCompressHeader, Obp20Header, and ObpMysqHeader is (0, 0, 1), the corresponding protocol type is set to MySQL protocol; if the combination of the judgment results is (1, 0, 1), the corresponding protocol type is set to Compressed MySQL protocol; if the combination of the judgment results is (1, 1, 1), the corresponding protocol type is set to OceanBase 2.0 protocol.

[0078] In this way, when there is a transmission anomaly in the future, the transmission anomaly diagnosis can be performed according to the protocol type, and the diagnosis result corresponding to the protocol type can be output.

[0079] Method 2: If the device type is a proxy server, obtain the protocol sending and receiving field contained in the data message header, and obtain the protocol type corresponding to the protocol sending and receiving field.

[0080] The protocol transceiver field may include a receive field and a send field, and may also include a protocol field. The receive field may include: recv ob20, recv compressed mysql, recv mysql; the send field may include: send ob20, send compressed mysql, send mysql; and the protocol field may include: -mysql.

[0081] As an example, the information contained in the data message header 1 is as follows: [2023....][...][Y0-...][CONNECITON](latest_protocol: send ob20{compressed_len_=123,compressed_seq_=0,uncompressed_len_=0, payload_len_=123,flag_=12,req_id_=1656112,pkt_seq_=0,ext_flags_=12}, |-mysql{len_=12,seq_=0,cmd=3}, |-mysql{len_=12,seq_=1,cmd=3}. recv ob20{compressed_len_=123,compressed_seq_=0,uncompressed_len_=0, payload_len_=123, flag_=12, req_id_=1656112, pkt_seq_=0, ext_flags_=12}, |-mysql{len_=12, seq_=0, pkt_type_=254}, |-mysql{cnt_=10, seq_=1, pkt_type_=123}.

[0082] Because the data packet header 1 contains send ob20 / recv ob20, the corresponding protocol type is determined to be the OceanBase 2.0 protocol. The MySQL message can be identified by using -mysql.

[0083] As another example, the data message header 2 includes the following information: [2023....][...][Y0-...][CONNECITON](latest_protocol: send compressed mysql{compressed_len_=123,compressed_seq_=0, uncompressed_len_=0}, -mysql{len_=12,seq_=0,cmd=3}, -mysql{len_=12,seq_=1,cmd=3}. recv compressed mysql{compressed_len_=123,compressed_seq_=0, uncompressed_len_=0}, -mysql{len_=12,seq_=0,pkt_type_=254}, |-mysql{cnt_=10,seq_=1,pkt_type_=123}).

[0084] Since data message header 2 contains "send compressed mysql / recv compressed mysql", the corresponding protocol type is determined to be the Compressed MySQL protocol, and the MySQL message can be identified by "-mysql".

[0085] As another example, the information included in the data message header 3 is as follows: [2023....][...][Y0-...][CONNECITON](latest_protocol: send mysql{len_=12,seq_=0,cmd=3}, send mysql{len_=12,seq_=1,cmd=3}, recv mysql{cnt_=10,seq_=2,pkt_type_=123}}, recv mysql{len_=12,seq_=3,pkt_type_=254}, recv mysql{cnt_=10,seq_=4,pkt_type_=123}).

[0086] Since data packet header 3 contains send mysql / recv mysql and -mysql, the corresponding protocol type is determined to be the MySQL protocol.

[0087] In this way, the protocol type can be determined in different ways for different types of devices.

[0088] S1012-2: Obtain the protocol packet type in the packet structure information.

[0089] As an example, the protocol packet type can be determined by the value of the protocol packet type field pkt_type in the packet structure information. The pkt_type value and its corresponding protocol packet type can include: 0->mysql packet; 1->okp; / / 2->error packet; 3->eof packet / / 4->row packet; 5->feild packet; / / 6->piece packet; 7->string packet; / / 8->prepare packet; 9->result header packet / / 10->prepare execute packet.

[0090] S1012-3: If the protocol packet type is a specified type, obtain the number of packets in the packet structure information, and generate a packet information set including the protocol type, protocol packet type, and number of packets.

[0091] The protocol packet of the specified type is a protocol packet that requires special processing. Optionally, the protocol packet of the specified type may include a row packet and a field packet. As an example, the field packet is: field[N]EOF row[N]{EOF OKP}.

[0092] For field and row packets, since the length of the field and row packets has no meaning, the datagram header (such as ObpMysqHeader) usually does not record the length of the field and row packets, but records the number of protocol packets of the specified type.

[0093] In actual applications, the protocol packet type and the specified type can be set according to the actual application scenario and are not restricted here.

[0094] In one embodiment, after determining the protocol type of the protocol packet, a packet information set including the protocol type is generated; the protocol packet type in the packet structure information is obtained, and the protocol packet type is added to the packet information set; after obtaining the number of packets in the packet structure information, the number of packets is added to the packet information set.

[0095] In actual applications, the order in which the protocol type, protocol packet type, and packet quantity are added to the packet information set, as well as the timing of generating the packet information set, can be set according to the actual application scenario and are not restricted here.

[0096] S1012-4: If the protocol packet type is a non-specified type, generate a packet information set including a data message header and a protocol type.

[0097] In one embodiment, after determining the protocol type of the protocol packet, a packet information set including the protocol type is generated; if the device type is a service server, when determining that the protocol packet is received, the data message header is obtained and added to the packet information set.

[0098] In one embodiment, after determining the protocol type of the protocol packet, a packet information set containing the protocol type is generated; if the device type is a proxy server, upon receiving the protocol packet sent by the user device or service server, the data packet header is obtained and added to the packet information set. As an example, a protocol recording module is added to the main state machine (ObMysqlSM) in the proxy server, and the packet information is extracted and recorded through ObMysqlSM to obtain a packet information set. For example, if an OceanBase 2.0 protocol packet contains three MySQL protocol packets, four message headers (data packet headers) can be obtained.

[0099] Furthermore, some interference information can be filtered according to the set filtering rules.

[0100] As an example, if it is determined that the proxy server uses OBProxyro to perform internal table queries, the relevant information is filtered out and not recorded.

[0101] Furthermore, if the received protocol packet is a fragment, the packet structure information may further include a packet merging field, which is used to indicate the fragment length of the protocol packet fragment received by the protocol packet.

[0102] In one implementation, if the packet structure information includes a packet combining field, the fragment length of the protocol packet fragment received by the protocol packet is determined according to the packet combining field; and the fragment length is added to the packet information set.

[0103] At the Transmission Control Protocol (TCP) network layer, when an upstream device (i.e., the device sending a message, such as a proxy server) sends a large protocol packet, it splits the large protocol packet into multiple protocol packets, namely protocol packet fragments (e.g., MySQL protocol packet fragments), and sends each protocol packet fragment to a downstream device (i.e., the device receiving the message, such as a service server). After receiving the protocol packet fragments, the downstream device determines the fragment length based on the packet merging field (e.g., the rec field) in the message protocol packet. It then reserves a buffer of a certain length based on the fragment length and fills the received protocol packet fragments into the buffer, thereby obtaining a complete large protocol packet and achieving protocol packet merging. This way, the fragment length can be used to preserve the scene of the packet merging.

[0104] Step 102: According to the second recording rule corresponding to the device type, link information is extracted from the protocol packet in the data interaction message to obtain a link information set; the link information set is used to determine the transmission link and processing node of the data interaction message.

[0105] It should be noted that the packet information set and the link information set can be the same set or different sets, and there is no limitation here.

[0106] In one implementation, when executing step 102, the following method may be used.

[0107] Method 1: If the device type is a service server, obtain the link information set according to the processing node of the protocol packet.

[0108] In one embodiment, when executing the first method, the following steps S102-11 to S102-14 may be adopted.

[0109] S102-11: If the device type is a service server, when determining to execute the protocol package, obtain the command keyword in the package structure information.

[0110] In one embodiment, the received protocol packet is added to an execution queue. When the protocol packet is determined to be executed, the protocol packet is taken out from the execution queue and executed to obtain a command keyword from the packet structure information in the protocol packet.

[0111] S102-12: Generate a link information set including a command keyword.

[0112] Furthermore, if the packet information set and the link information set are the same set, S102 - 12 may not be executed.

[0113] S102-13: When determining to send a response message to the data interaction message, set a message response keyword.

[0114] In one embodiment, after the data interaction message processing is completed, a response message is returned to the proxy server, and when the response message is returned, a message response keyword indicating a message response is set. For example, processed is set to 1, indicating a message response.

[0115] S102-14: Add the message response keyword to the link information set.

[0116] In this way, if the link information set does not contain the command keyword, it can be determined that the processing stage of the protocol package is: the received protocol packet has not been processed; if the link information set only contains the command keyword, it can be determined that the processing stage of the protocol package is: the protocol package is executed and has not yet responded; if the link information set contains the command keyword and the message response keyword, it can be determined that the processing stage of the protocol package is: the response message of the data interaction message has been sent.

[0117] Method 2: If the device type is a proxy server, a link information set is obtained according to the transmission link of the data interaction message.

[0118] In one embodiment, when executing the second method, the following steps S102-21 to S102-22 may be adopted.

[0119] S102-21: If the device type is a proxy server, determine the link transmission object and transmission channel of the data interaction message.

[0120] The following describes the message transmission links between devices in a data transmission system, with reference to Figure 2. Figure 2 is a schematic diagram of a request message forwarding process. In Figure 2, a client in a user device sends a protocol packet of a first protocol type (e.g., a MySQL protocol packet) to a proxy server. The proxy server performs protocol conversion on the protocol packet to obtain a protocol packet of a second protocol type, and then forwards the protocol packet of the second protocol type to a service server.

[0121] The following describes the message transmission links between devices in the data transmission system, with reference to Figure 3. Figure 3 is a schematic diagram of response message forwarding. In Figure 3, the service server sends a protocol packet of the second protocol type to the proxy server. The proxy server performs protocol conversion on the protocol packet of the second protocol type, obtains a protocol packet of the first protocol type, and then sends the protocol packet of the first protocol type to the client of the user device.

[0122] As an example, the protocol package of the first protocol type may be a MySQL protocol package, and the second protocol type may be any one of the following: MySQL protocol, Compressed MySQL protocol, and OceanBase 2.0 protocol.

[0123] In one embodiment, the link transmission objects include: a client object (ClientVC), a proxy object, and a business object (ServerVC). The client in the message transmission link is abstracted as a client object that can perform input and output (IO) operations; the proxy server and protocol conversion process in the message transmission link are abstracted as a proxy object that can perform IO operations; and the business server in the message transmission link is abstracted as a business object that can perform IO operations. The transmission connection of the message transmission link is abstracted as a transmission channel (ObVConnection). For example, ObVConnection can transfer data through ObMysqlTunnel.

[0124] S102-22: Generate a link information set according to the link transmission object and the transmission channel.

[0125] In this way, through the link information collection, every key link in the entire transmission link can be recorded, ensuring that protocol interaction problems in the entire transmission link will be tracked, which can greatly help subsequent abnormality diagnosis.

[0126] Furthermore, the packet information set and link information set corresponding to each protocol packet of the data interaction message may be added to the circular queue.

[0127] In one implementation, the following steps S102-31 to S102-33 may be adopted.

[0128] S102-31: Determine whether there is a circular queue corresponding to the target transmission connection.

[0129] The circular queue corresponds one-to-one to the target transport connection, or session. It records the packet information sets and link information sets of multiple protocol packets for the latest data exchange messages transmitted over the transport connection. The circular queue contains a specified number of slots (e.g., 32). Each slot can record the packet information set and link information set of a protocol packet.

[0130] For example, when setting the buffer for a transport connection, you can use the following code: #define REC_BUF_SIZE 32; ObPacketRecord rec_buf[REC_BUF_SIZE]; Total size: 32*32=1024byte.

[0131] According to the code, the buffer size is 1024 bytes, that is, for each transmission connection, an overhead of 1024 bytes will be added. rec_buf[REC_BUF_SIZE] is used to record the packet information set and link information set of all protocol packets stored in the buffer.

[0132] S102-32: If a circular queue exists, the packet information set and link information set corresponding to each protocol packet of the data interaction message are added to the circular queue.

[0133] S102-33: If the circular queue does not exist, a circular queue corresponding to the target transmission connection is established, and the packet information set and link information set corresponding to each protocol packet of the data interaction message are added to the circular queue.

[0134] In this way, the latest packet information set and link information set of multiple protocol packets can always be stored through the circular queue, so that when an exception occurs, the latest data can be quickly filtered out and the occupied storage space can be reduced.

[0135] Step 103: When it is determined that a transmission anomaly exists in the target transmission connection, a transmission anomaly diagnosis is performed based on the packet information set and the link information set corresponding to the target connection.

[0136] In one implementation, when executing step 103 , the following steps S1031 to S1032 may be adopted.

[0137] S1031: When it is determined that a transmission anomaly exists in the target transmission connection, the packet information set and link information set corresponding to the latest specified number of protocol packets are screened out from the circular queue.

[0138] In one implementation, the packet information sets and link information sets corresponding to the latest specified number (eg, 20) of protocol packets are screened out from the circular queue.

[0139] Furthermore, the packet information set and link information set corresponding to the filtered protocol packets may be printed to a transmission anomaly log (eg, OBProxy_diagnosis.log) in a specified format.

[0140] S1032: Diagnose transmission anomalies based on the filtered packet information set and link information set.

[0141] In an embodiment of the present application, the information requirements for transmission anomaly diagnosis are analyzed to determine the on-site information required for transmission diagnosis, and based on the analysis results, the protocol packet structure of the data interaction message received by devices of different device types is designed separately, so that when the data interaction message is transmitted between devices, the packet structure information of the protocol packet in the data interaction message can be extracted, and the transmission link is abstracted into a communication model, so that during the entire protocol interaction cycle, based on the communication model record, the data interaction message at each key node in the transmission link can be comprehensively recorded, thereby ensuring the effectiveness and comprehensiveness of the communication process record, and eliminating the need for recurrence testing and data packet capture after a transmission anomaly occurs, thereby simplifying the tedious steps of obtaining diagnostic information, effectively and quickly saving the protocol layer problem site, and realizing rapid diagnosis of the protocol layer problem. Furthermore, the protocol type can also be identified to support transmission anomaly diagnosis of multiple protocol types, thereby improving the accuracy and reliability of transmission anomaly diagnosis and enhancing the flexibility of protocol monitoring. Furthermore, the recorded data is stored in a circular queue, which reduces the occupied storage space, the time and tedious operations of data screening, ensures the effectiveness and timeliness of the recorded data, and simplifies the tedious operations of transmission anomaly diagnosis.

[0142] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0143] Based on the same inventive concept, the embodiments of this application also provide a device for diagnosing transmission anomalies. Since the principles of the above-mentioned device and equipment for solving the problem are similar to those of a method for diagnosing transmission anomalies, the implementation of the above-mentioned device can refer to the implementation of the method, and the repeated parts will not be repeated. The device can be applied to electronic devices. This application does not limit the type of electronic device. It can be any device type suitable for implementation, such as a smartphone, tablet computer, etc., and this application will not repeat them.

[0144] Refer to FIG4 , which is a block diagram of a transmission anomaly diagnosis device according to an embodiment of the present application. In some embodiments, the transmission anomaly diagnosis device according to the present application example includes:

[0145] A determining unit 401 is configured to determine a device type corresponding to a device receiving a data interaction message when a data interaction message is transmitted between multiple devices via a target transmission connection;

[0146] An extraction unit 402 is configured to extract packet information from protocol packets in a data interaction message according to a first recording rule corresponding to a device type to obtain a packet information set;

[0147] An obtaining unit 403 is configured to extract link information from a protocol packet in a data interaction message according to a second recording rule corresponding to a device type to obtain a link information set; the link information set is used to determine a transmission link and a processing node for the data interaction message;

[0148] The diagnosis unit 404 is configured to perform a transmission anomaly diagnosis based on a packet information set and a link information set corresponding to the target connection when determining that the target transmission connection has a transmission anomaly.

[0149] In one embodiment, the extraction unit 402 is used to: parse the data interaction message to obtain the packet structure information of each protocol packet in the data interaction message; the data interaction message contains at least one protocol packet; for each protocol packet and its corresponding packet structure information, perform the following steps: determine the protocol type of the protocol packet based on the device type and the data packet header in the packet structure information; obtain the protocol packet type in the packet structure information; if the protocol packet type is a specified type, obtain the number of packets in the packet structure information, and generate a packet information set including the protocol type, protocol packet type and the number of packets; if the protocol packet type is a non-specified type, generate a packet information set including the data packet header and the protocol type.

[0150] In one embodiment, the extraction unit 402 is used to: if the device type is a business server, determine whether each data packet header is empty; and determine the protocol type based on the judgment result; the packet structure information includes at least one data packet header; if the device type is a proxy server, obtain the protocol sending and receiving fields contained in the data packet header, and obtain the protocol type corresponding to the protocol sending and receiving fields.

[0151] In one embodiment, the extraction unit 402 is further configured to: if the packet structure information includes a packet combination field, determine the fragment length of the protocol packet fragment received by the protocol packet according to the packet combination field; and add the fragment length to the packet information set.

[0152] In one embodiment, the acquisition unit 403 is used to: if the device type is a business server, obtain the command keyword in the package structure information when determining to execute the protocol package; generate a link information set containing the command keyword; when determining to send a response message for the data interaction message, set the message response keyword; and add the message response keyword to the link information set.

[0153] In one embodiment, the obtaining unit 403 is configured to: if the device type is a proxy server, determine a link transmission object and a transmission channel of the data interaction message; and generate a link information set according to the link transmission object and the transmission channel.

[0154] In one embodiment, the diagnostic unit 404 is also used to: determine whether there is a circular queue corresponding to the target transmission connection; the circular queue and the target transmission connection are one-to-one corresponding; if there is a circular queue, the packet information set and link information set corresponding to each protocol packet of the data interaction message are added to the circular queue; if there is no circular queue, a circular queue corresponding to the target transmission connection is established, and the packet information set and link information set corresponding to each protocol packet of the data interaction message are added to the circular queue.

[0155] In one embodiment, the diagnostic unit 404 is used to: when it is determined that there is a transmission anomaly in the target transmission connection, filter out the packet information set and link information set corresponding to the latest specified number of protocol packets from the circular queue; and diagnose the transmission anomaly based on the filtered packet information set and link information set.

[0156] On the one hand, an embodiment of the present application provides an electronic device, comprising: a processor; and a memory storing computer instructions, the computer instructions being used to enable the processor to execute the steps of the method provided in any of the various optional implementations of transmission abnormality diagnosis described above.

[0157] On the one hand, an embodiment of the present application provides a storage medium storing computer instructions, which are used to enable a computer to execute the steps of the method provided in any of the various optional implementations of transmission abnormality diagnosis described above.

[0158] In the transmission anomaly diagnosis method, device, electronic device and storage medium provided by the embodiment of the present application, when a data interaction message is transmitted between multiple devices through a target transmission connection, the device type corresponding to the device receiving the data interaction message is determined; according to the first recording rule corresponding to the device type, packet information is extracted for the protocol packet in the data interaction message to obtain a packet information set; according to the second recording rule corresponding to the device type, link information is extracted for the protocol packet in the data interaction message to obtain a link information set; the link information set is used to determine the transmission link and processing node of the data interaction message; when it is determined that there is a transmission anomaly in the target transmission connection, the transmission anomaly diagnosis is performed based on the packet information set and link information set corresponding to the target connection. In this way, during the message transmission process, the extraction and recording of diagnosis-related information are performed in real time, and when a transmission anomaly occurs, the transmission anomaly diagnosis can be performed directly by recording data, which simplifies the tedious steps of transmission anomaly diagnosis and improves the efficiency of transmission anomaly diagnosis.

[0159] An embodiment of the present application provides an electronic device, including: a processor; and a memory storing computer instructions, wherein the computer instructions are used to enable the processor to execute a method in any of the above embodiments.

[0160] An embodiment of the present application provides a storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the method of any of the above embodiments.

[0161] FIG5 shows a schematic structural diagram of an electronic device 5000. Referring to FIG5, the electronic device 5000 includes a processor 5010 and a memory 5020, and optionally, may further include a power supply 5030, a display unit 5040, and an input unit 5050.

[0162] The processor 5010 is the control center of the electronic device 5000 , which connects various components using various interfaces and lines, and performs various functions of the electronic device 5000 by running or executing software programs and / or data stored in the memory 5020 .

[0163] In the embodiment of the present application, the processor 5010 executes the various steps in the above embodiment when calling the computer program stored in the memory 5020.

[0164] Optionally, the processor 5010 may include one or more processing units. Preferably, the processor 5010 may integrate an application processor and a modem processor, wherein the application processor primarily processes the operating system, user interface, and applications, and the modem processor primarily processes wireless communications. It is understood that the modem processor may not be integrated into the processor 5010. In some embodiments, the processor and memory may be implemented on a single chip. In some embodiments, they may also be implemented on separate chips.

[0165] The memory 5020 may mainly include a program storage area and a data storage area. The program storage area may store an operating system, various applications, etc., and the data storage area may store data created based on the use of the electronic device 5000. In addition, the memory 5020 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device.

[0166] The electronic device 5000 also includes a power supply 5030 (such as a battery) for supplying power to various components. The power supply can be logically connected to the processor 5010 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0167] The display unit 5040 can be used to display information input by the user or information provided to the user, as well as various menus of the electronic device 5000. In the embodiment of the present application, it is mainly used to display the display interface of each application in the electronic device 5000 and objects such as text and pictures displayed on the display interface. The display unit 5040 may include a display panel 5041. The display panel 5041 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.

[0168] The input unit 5050 can be used to receive information such as numbers or characters input by the user. The input unit 5050 may include a touch panel 5051 and other input devices 5052. The touch panel 5051, also known as a touch screen, can receive user touch operations on or near it (for example, operations performed by the user using a finger, a stylus, or any other suitable object or accessory on or near the touch panel 5051).

[0169] Specifically, the touch panel 5051 can detect user touch operations and the signals generated by the touch operations, convert these signals into touch point coordinates, send them to the processor 5010, and receive and execute commands sent by the processor 5010. In addition, the touch panel 5051 can be implemented using various types, such as resistive, capacitive, infrared, and surface acoustic wave. Other input devices 5052 can include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, a joystick, etc.

[0170] Of course, the touch panel 5051 can cover the display panel 5041. When the touch panel 5051 detects a touch operation on or near it, it transmits the information to the processor 5010 to determine the type of touch event. The processor 5010 then provides a corresponding visual output on the display panel 5041 based on the type of touch event. Although in Figure 5, the touch panel 5051 and the display panel 5041 are used as two independent components to implement the input and output functions of the electronic device 5000, in some embodiments, the touch panel 5051 and the display panel 5041 can be integrated to implement the input and output functions of the electronic device 5000.

[0171] The electronic device 5000 may further include one or more sensors, such as a pressure sensor, a gravity acceleration sensor, a proximity light sensor, etc. Of course, according to the needs of specific applications, the electronic device 5000 may also include other components such as a camera. Since these components are not the key components used in the embodiments of the present application, they are not shown in FIG5 and will not be described in detail.

[0172] Those skilled in the art will understand that FIG5 is merely an example of an electronic device and does not limit the electronic device. The electronic device may include more or fewer components than shown in the figure, or may combine certain components, or may include different components.

[0173] For the convenience of description, the above parts are divided into modules (or units) according to their functions and described separately. Of course, when implementing this application, the functions of each module (or unit) can be implemented in the same or multiple software or hardware.

[0174] Obviously, the above embodiments are merely examples for clarity of explanation and are not intended to limit the embodiments. Those skilled in the art will appreciate that other variations or modifications can be made based on the above description. It is not necessary and impossible to enumerate all embodiments here. Obvious variations or modifications arising therefrom remain within the scope of protection of this application.

Claims

1. A method for diagnosing transmission anomalies, the method comprising: When transmitting data interaction messages through a target transmission connection between multiple devices, determining the device type corresponding to the device that receives the data interaction message; According to the first recording rule corresponding to the device type, extracting packet information from the protocol packets in the data interaction message to obtain a packet information set; According to the second recording rule corresponding to the device type, extracting link information from the protocol packets in the data interaction message to obtain a link information set; the link information set is used to determine the transmission link and processing nodes of the data interaction message; When it is determined that there is a transmission anomaly in the target transmission connection, performing transmission anomaly diagnosis according to the packet information set and the link information set corresponding to the target connection.

2. The method according to claim 1, wherein the extracting packet information from the protocol packets in the data interaction message according to the first recording rule corresponding to the device type to obtain a packet information set comprises: Parsing the data interaction message to respectively obtain the packet structure information of each protocol packet in the data interaction message; the data interaction message contains at least one protocol packet; For each protocol packet and its corresponding packet structure information, respectively perform the following steps: Determining the protocol type of the protocol packet according to the device type and the data packet header in the packet structure information; Obtaining the protocol packet type in the packet structure information; If the protocol packet type is a specified type, obtaining the number of packets in the packet structure information and generating a packet information set including the protocol type, the protocol packet type, and the number of packets; If the protocol packet type is a non-specified type, generating a packet information set including the data packet header and the protocol type.

3. The method according to claim 2, wherein the determining the protocol type of the protocol packet according to the device type and the data packet header in the packet structure information comprises: If the device type is a service server, respectively determining whether each data packet header is empty; And determining the protocol type according to the judgment result; The packet structure information contains at least one data packet header; If the device type is a proxy server, obtaining the protocol transceiver field contained in the data packet header and obtaining the protocol type corresponding to the protocol transceiver field.

4. The method according to claim 2, the method further comprising: If the packet structure information contains a packet combining field, determining the fragment length of the protocol packet fragments received by the protocol packet according to the packet combining field; Adding the fragment length to the packet information set.

5. The method according to any one of claims 2-4, wherein the extracting link information from the protocol packets in the data interaction message according to the second recording rule corresponding to the device type to obtain a link information set comprises: If the device type is a service server, when determining to execute the protocol packet, obtaining the command keyword in the packet structure information; Generating a link information set including the command keyword; When determining to send a response message for the data interaction message, set a message response keyword; Add the message response keyword to the link information set.

6. The method according to any one of claims 2-4, wherein the extracting link information from the protocol packets in the data interaction message according to the second recording rule corresponding to the device type to obtain a link information set includes: If the device type is a proxy server, determine the link transmission object and the transmission channel of the data interaction message; Generate the link information set according to the link transmission object and the transmission channel.

7. The method according to any one of claims 1-4, before diagnosing a transmission anomaly according to the packet information set and the link information set corresponding to the target connection when it is determined that there is a transmission anomaly in the target transmission connection, the method further includes: Determine whether there is a circular queue corresponding to the target transmission connection; The circular queue and the target transmission connection are in one-to-one correspondence; If the circular queue exists, add the packet information set and the link information set corresponding to each protocol packet of the data interaction message to the circular queue; If the circular queue does not exist, establish a circular queue corresponding to the target transmission connection, and add the packet information set and the link information set corresponding to each protocol packet of the data interaction message to the circular queue.

8. The method according to claim 7, when it is determined that there is a transmission anomaly in the target transmission connection, diagnosing the transmission anomaly according to the packet information set and the link information set corresponding to the target connection includes: When it is determined that there is a transmission anomaly in the target transmission connection, filter out the packet information sets and the link information sets corresponding to the latest specified number of protocol packets from the circular queue; Diagnose the transmission anomaly according to the filtered packet information sets and link information sets.

9. A device for diagnosing transmission anomalies, the device includes: A determination unit, configured to determine the device type of the device that receives the data interaction message when transmitting the data interaction message between multiple devices through a target transmission connection; An extraction unit, configured to extract packet information from the protocol packets in the data interaction message according to the first recording rule corresponding to the device type to obtain a packet information set; An obtaining unit, configured to extract link information from the protocol packets in the data interaction message according to the second recording rule corresponding to the device type to obtain a link information set; The link information set is used to determine the transmission link and processing nodes of the data interaction message; A diagnosis unit, configured to diagnose a transmission anomaly according to the packet information set and the link information set corresponding to the target connection when it is determined that there is a transmission anomaly in the target transmission connection.

10. An electronic device, including: A processor; And A memory storing computer instructions for causing the processor to execute the method according to any one of claims 1-8.

11. A storage medium stores computer instructions for causing a computer to execute the method according to any one of claims 1-8.

Images