WO2010139240A1 - 显示通讯数据包的实现方法、客户端、服务端及系统 - Google Patents

显示通讯数据包的实现方法、客户端、服务端及系统 Download PDF

Info

Publication number
WO2010139240A1
WO2010139240A1 PCT/CN2010/072981 CN2010072981W WO2010139240A1 WO 2010139240 A1 WO2010139240 A1 WO 2010139240A1 CN 2010072981 W CN2010072981 W CN 2010072981W WO 2010139240 A1 WO2010139240 A1 WO 2010139240A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
client
server
service thread
file
Prior art date
Application number
PCT/CN2010/072981
Other languages
English (en)
French (fr)
Inventor
魏霄鹏
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2010139240A1 publication Critical patent/WO2010139240A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks

Definitions

  • the invention relates to the field of communication, in particular to an implementation method, a client, a server and a system for visually displaying a communication data packet. Background technique
  • the communication log is lacking. In the operation, it is necessary to analyze and locate the problem according to the communication message. However, if the ordinary packet capture tool is used to capture the packet analysis, all the binary data streams are obtained, and each field cannot be displayed intuitively. Meaning and value. Summary of the invention
  • the technical problem to be solved by the present invention is to provide an implementation method, a client, a server and a system for displaying a communication data packet capable of visually displaying a communication data packet.
  • the present invention provides a method for displaying a communication data packet, the method comprising: the client sending a start tracking message carrying a service thread number to the server, indicating the server Starting to record a data packet transmitted by the service thread corresponding to the service thread number;
  • the client sends an end tracking message carrying the service thread number to the server, and instructs the server to stop recording the data packet transmitted by the service thread corresponding to the service thread number;
  • the client acquires the data packet recorded by the server and displays the data packet. Further, the step of the client acquiring the data packet recorded by the server and displaying the data packet includes:
  • the client receives the response message returned by the server according to the end tracking message, where the response message includes: a file name and a path of the trace file, where the trace file includes the data packet that is recorded;
  • the client obtains the tracking file from the server according to the file name and path of the trace file;
  • the client parses the trace file to generate a data packet carrying a data structure; the client displays the data packet carrying the data structure.
  • the step of the client acquiring the data packet recorded by the server and displaying the data packet includes:
  • the client obtains the recorded data packet from the server in real time to form a tracking file; the client parses the tracking file to generate a data packet carrying a data structure; and the client displays the data in real time.
  • a packet carrying a data structure is
  • step of the client parsing the trace file to generate a data packet carrying the data structure is specifically:
  • the client parses the trace file with an indented structure parsing file to generate a data packet with an indented structure.
  • the indentation structure is specifically: a tree structure or an indentation structure formed by an Extensible Markup Language (XML).
  • XML Extensible Markup Language
  • the invention also provides a client, the client comprising:
  • a first sending module configured to send a start tracking message carrying a service thread number to the server, instructing the server to start recording a data packet transmitted by the service thread corresponding to the service thread number;
  • a second sending module configured to send, to the server, an end tracking message carrying the service thread number, instructing the server to stop recording a data packet transmitted by the service thread corresponding to the service thread number;
  • An obtaining module configured to obtain the recorded data packet from the server
  • a display module configured to display the data packet.
  • the obtaining module includes:
  • a first receiving submodule configured to receive a response message that is returned by the server according to the end tracking message;
  • the response message includes: a file name and a path of the tracking file, where the tracking file includes the data packet that is recorded;
  • Obtaining a submodule configured to obtain the trace file from the server according to a file name and a path of the trace file
  • the parsing sub-module is configured to parse the trace file, generate a data packet carrying the data structure, and provide the data to the display module.
  • the acquiring module includes:
  • a second receiving submodule configured to receive the data packet recorded from the server in real time to form a tracking file
  • the parsing sub-module is configured to parse the trace file, generate a data packet carrying the data structure, and provide the data to the display module.
  • the parsing sub-module is further configured to parse the tracking file by using an indented structure parsing file to generate a data packet with an indented structure, and provide the data to the display module;
  • the indented structure is a tree structure, or an indented structure formed by XML.
  • the invention also provides a server, the server includes: a first receiving module, configured to receive a start tracking message that is sent by the client and carries a service thread number;
  • a first processing module configured to forward the start tracking message to a service thread corresponding to the service thread number, and record a data packet transmitted by the service thread;
  • a second receiving module configured to receive an end tracking message that is sent by the client and that carries the service thread number
  • a second processing module configured to forward the end tracking message to a service thread corresponding to the service thread number
  • a sending module configured to return the recorded data packet to the client according to the end tracking message, where the client displays the data packet.
  • the sending module includes: a first sending submodule or a second sending submodule, where:
  • the first sending submodule is configured to return a response message to the client according to the end tracking message, where the response message includes: a file name and a path of the trace file; the trace file includes the recorded data packet;
  • the second sending submodule is configured to transmit the recorded data packet to the client in real time.
  • the invention also provides a communication system, the system comprising:
  • a client configured to send a start trace message carrying a service thread number and an end trace message carrying the service thread number to the server; and further configured to receive the data packet returned by the server, and display the data packet;
  • a server configured to receive the start tracking message and the end tracking message sent by the client, and record, according to the service thread number, a data packet transmitted by a service thread corresponding to the service thread number; The client returns the packet.
  • the client sends a start tracking message to the server, where the tracking starts.
  • the message includes a service thread number, and the server forwards the start tracking message to the service thread according to the service thread number, and acquires the data packet transmitted by the service thread.
  • the client also sends an end trace message, and the end trace message also carries the service thread number, and the server distributes the end trace message to the service thread for processing; the client obtains the data packet from the server, and is intuitive on the interface. This improves the efficiency of on-site commissioning and maintenance.
  • FIG. 1 is a schematic flowchart of a method for implementing a client to display a communication data packet according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for a server to send a trace file according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a client according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a server end according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of an implementation system for displaying a communication data packet according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a processing start tracking message of the system shown in FIG. 5;
  • FIG. 7 is a schematic flow chart of the process end tracking message of the system shown in FIG. 5. detailed description
  • the present invention is directed to the prior art, the communication log is lacking, the general packet capture tool performs packet capture analysis, and the generated binary data stream cannot directly display the meaning and value of each field, and provides a visual display of communication data.
  • the package, the efficiency of on-site debugging and maintenance, shows the implementation method of the communication packet, the client, the server and the system.
  • an embodiment of the present invention shows a method for implementing a communication data packet, including: Step 11: A client sends a start tracking message carrying a service thread number to a server, and instructs the server to start recording the corresponding service thread number. The business thread transfers the packet.
  • the business thread can be the business thread to be tracked; a business thread is running when the system is running.
  • the data packet is received or sent at any time.
  • the server After receiving the start tracking message, the server records all the received or sent data packets of the service thread corresponding to the service thread number to be tracked in the start tracking message.
  • Step 12 The client sends an end trace message carrying the service thread number to the server, and indicates that the server stops recording the data packet transmitted by the service thread corresponding to the service thread number.
  • the server After receiving the end trace message, the server forwards the end trace message to the service thread corresponding to the service thread number it carries. The server stops recording the data packet and closes the file handle.
  • Step 13 The client obtains the data packet recorded by the server and visually displays the data packet.
  • the client may be a client that can display a web interface, or a client that can display an interface generated by an extensible markup language (Xml), and the client sends a start tracking message to the server.
  • the server opens the trace file according to the start trace message, and records all the received and sent data packets of the service thread corresponding to the service thread number (ie, the service thread to be tracked) according to the service thread number carried in the start trace message;
  • the server stops the record of the data packet; the client then obtains the data packet from the server and displays it visually.
  • the client can display the data packet in an indented manner, especially The tree structure, so that the information and meaning of the acquired data packet can be easily understood by the client, and each field of the communication data packet can be clearly displayed, which is advantageous for on-site positioning problems and improves the efficiency of on-site debugging and maintenance.
  • step 13 may specifically include:
  • Step 1311 The client receives a response message returned by the server according to the end tracking message, where the response message includes: a file name and a path of the trace file, and the trace file includes the data packet;
  • Step 1312 The client obtains the trace file from the server according to the file name and path of the trace file. For example, after the client receives the file name and path of the trace file, the client may obtain the trace file to the local file through a file transfer protocol (FTP) function.
  • FTP file transfer protocol
  • Step 1313 The client parses the trace file to generate a data packet carrying the data structure.
  • step 1314 the client displays the data packet carrying the data structure.
  • step 13 may further include:
  • Step 1321 The client obtains the data packet transmitted by the service thread to be tracked from the server in real time to form a tracking file.
  • Step 1322 The client parses the trace file to generate a data packet carrying the data structure.
  • Step 1323 The client displays the data packet carrying the data structure in real time.
  • the client can parse the trace file by using the indented structure parsing file, generate a data packet with the indented structure, and display the data packet carrying the indented structure.
  • the indented structure parsing file may select a parsing file of the business thread corresponding to the business thread number to be tracked, and the parsing file conforms to the business thread processing packet rule, and the parsing file may include: a packet ID, a length of the entire packet, Each parameter name, parameter type, parameter length (integer or string), whether to convert byte order, this parameter corresponds to the indentation level of the structure.
  • the indentation structure may be a tree type or an indentation structure generated by using an Xml markup language, and the data packet of the indented structure is displayed in a tree type on a web interface, and displayed on a local web interface, the interface Some filters are also set, and the recorded packets are selected based on these filters.
  • the client can also use other visual display methods, such as using a line-type parsing file to parse the trace file to obtain a data packet of a linear structure; or parsing the trace file by using a star parsing file to obtain a star structure.
  • Data packet; or use the ring type parsing file to parse the trace file; or other parsing file parses the trace file to obtain a data packet with a certain data structure, which is displayed on the client, such as displayed on the web interface of the client, so that Intuitive and clear understanding of the meaning of the acquired data packets, thereby improving the on-site debugging of the communication program and Maintenance work efficiency.
  • an embodiment of the present invention further provides a method for sending a trace file, including: Step 21: A server receives a start trace message that is sent by a client and carries a service thread number, according to a service thread number to be tracked. Forwarding the tracking message to the service thread corresponding to the service thread number, and acquiring the data packet transmitted by the service thread; the service thread may be the service thread to be tracked;
  • Step 22 The server receives the end tracking message that is sent by the client and carries the service thread number, and forwards the end tracking message to the service thread corresponding to the service thread number according to the service thread number;
  • Step 23 The server returns a data packet to the client according to the end tracking message.
  • the step 23 can be specifically:
  • the server generates a response message according to the end tracking message, and returns a response message to the client, where the response message includes a file name and a path of the trace file, and the trace file includes all the data packets transmitted by the service thread; or
  • the server returns the packet to the client in real time and stops returning the packet to the client when it receives the end trace message.
  • the implementation of the present invention further provides a client 30, including:
  • the first sending module 31 is configured to send, to the server, a start tracking message carrying the service thread number, and instruct the server to start recording the data packet transmitted by the service thread corresponding to the service thread number;
  • the second sending module 32 is configured to send, to the server, an end tracking message carrying the service thread number, and instruct the server to stop recording the data packet transmitted by the service thread corresponding to the service thread number;
  • An obtaining module 33 configured to acquire a data packet from a server;
  • the display module 34 is configured to visually display the data packet locally.
  • the first sending module 31 and the second sending module 32 may be a communication module of the client 30, and specifically may be a WEB communication module, configured to establish a connection with the server, and establish a TCP. /IP connection, and send a start tracking message to the server, and start to track the message to allow the filling of the business thread number, or to send the end tracking message, and the end of the tracking message is also allowed to fill in the business thread number;
  • the obtaining module 33 obtains the data packet from the server, and specifically, may include:
  • a first receiving submodule configured to receive a response message returned by the server according to the end tracking message, where the response message has a path and a file name of the tracking file, and the tracking file includes the data packet;
  • the obtaining sub-module is configured to obtain the trace file containing the data packet from the server according to the file name and path of the trace file; specifically, the trace file may be obtained locally through an FTP function or other special download tool;
  • a parsing sub-module configured to parse the trace file to generate a data packet carrying the data structure; the display module 34 displays the data packet carrying the data structure locally;
  • the obtaining module 33 may further include:
  • a second receiving submodule configured to receive a data packet from the server in real time to form a tracking file; and parse the submodule, and parse the tracking file to obtain a data packet carrying the data structure; and the display module 34 may parse the carried data structure
  • the packets are displayed locally in real time.
  • the parsing sub-module can select a parsing file corresponding to the business thread, the parsing file is written in advance, and is consistent with the thread processing packet rule, the parsing file includes, the packet ID, the length of the entire packet, each Parameter name, parameter type, parameter length (integer, string), whether to convert byte order, this parameter corresponds to the indentation level of the structure.
  • the parsing sub-module may further be: an indented structure parsing sub-module, configured to parse the trace file by using an indented structure parsing file, and obtain a data packet with an indented structure;
  • the display module 34 displays the parsed data packet with the indented structure locally.
  • the indented structure parsing file may select a parsing file of the business thread corresponding to the service thread number to be tracked, and the parsing file conforms to the service thread processing packet rule, and the parsing file may include: a packet ID, the entire packet Length, each parameter name, parameter type, parameter length (integer or string), whether to convert byte order, this parameter corresponds to the indentation level of the structure.
  • the indentation structure may be a tree type or an indentation structure generated by the Xml markup language.
  • the interface may also set some filtering conditions. The recorded packets are selected based on these filter conditions.
  • the parsing module can parse the trace file by using the line parsing file, obtain the data packet of the line structure, or parse the trace file by using the star parsing file to obtain the star type.
  • the client such as displayed on the web interface of the client, can intuitively and clearly understand the meaning of the acquired data packet, thereby improving the efficiency of on-site debugging and maintenance of the communication program.
  • the structure of the line type parsing file, the star parsing file or the ring parsing file may be similar to the structure of the above tree parsing file.
  • an embodiment of the present invention further provides a server 40, including:
  • the first receiving module 41 is configured to receive a start tracking message that is sent by the client and carries a service thread number.
  • the first processing module 42 is configured to forward the start tracking message to the service thread corresponding to the service thread number according to the service thread number, and record the data packet transmitted by the service thread;
  • the second receiving module 43 is configured to receive an end tracking message that is sent by the client and carries a service thread number.
  • the second processing module 44 is configured to forward the end tracking message to the end tracking message according to the end tracking message Processing in the business thread corresponding to the business thread number;
  • the sending module 45 is configured to return a data packet to the client according to the end tracking message.
  • the first receiving module 41 and the second receiving module 43 may be a communication module, configured to establish a connection with the client, such as a TCP/IP connection, and receive a start tracking message and an end tracking message sent by the client, and The start processing message is forwarded by the first processing module 42 to the corresponding service thread, and the second processing module 44 forwards the end tracking message to the corresponding service thread for processing.
  • the specific implementation of the sending module 45 may be specifically as follows:
  • a first sending submodule configured to return a response message to the client according to the end tracking message, where the response message includes: a file name and a path of the trace file; after the client obtains the file name and path, downloading the inclusion from the server a trace file of the data packet; or
  • the second sending sub-module is configured to transmit the data packet to the client in real time; after obtaining the data packet, the client parses and displays in real time.
  • an embodiment of the present invention further provides a communication system, including:
  • the client 30 is configured to send, to the server 40, a start tracking message carrying a service thread number and an end tracking message carrying a service thread number;
  • the server 40 is configured to receive a start tracking message and an end tracking message sent by the client 30, and record a data packet transmitted by the service thread corresponding to the service thread number according to the service thread number; and return the data packet to the client 30;
  • the server 40 may be a communication platform (IMPCOMM);
  • the client 30 also receives the data packets returned by the server 40 and visually displays the data packets locally.
  • the client 30 can be a web platform.
  • a client such as a WEB platform
  • a monthly service such as an IMP communication platform
  • the client sends a start tracking message, where the start tracking message contains the service thread number to be tracked;
  • the server receives the start tracking message, parses out the service thread number, and distributes the start tracking message to the service thread according to the service thread number;
  • the service thread receives the start tracking message, records all the received and sent data packets of the service thread, and the data packet is recorded in the tracking file;
  • the service thread returns a response message to the server, and the server returns a response message to the client, and the client interface displays a flag indicating that the tracking is successful.
  • the client establishes a communication connection with the server, and sends an end tracking message, and ends the tracking message carrying the thread number of the business thread to end the tracking;
  • the server receives the end tracking message, parses out the service thread number, and distributes the end tracking message to the service thread according to the service thread number;
  • the service thread receives the end trace message, stops writing the packet file, and closes the file handle;
  • the service thread returns a response message to the server, and the server returns a response message to the client;
  • the client removes the trace file from the server according to the file name and path in the response message
  • the client selects and loads the interface that matches the thread to display the parsing file, and the interface displays the network data packet of the tree structure, and the interface also provides setting filtering conditions and filtering the data packet.
  • the server does not generate the trace file locally, but transmits the data packet to the client in real time; the client receives the data packet in real time, and according to the pre-loaded parsing file in real time. Format, after parsing, real-time tree structure display.
  • the start tracking message includes: a message number and a message body, wherein the message body includes a service thread number to be tracked; and the end tracking message also includes: a message number and a message body, where the message body includes the end of the tracking Business thread number.
  • the client sends a start tracking message and an end tracking message to the server, where the start tracking message includes the service thread number to be tracked, and the server starts the tracking message according to the service thread number. Forwarded to the business thread for processing.
  • the client also sends an end trace message, and the end trace message also has a service thread number to end the trace, the server distributes the end trace message to the service thread for processing, and the server has a function of responding to the client request message;
  • the client parses the obtained trace file, parses the parsing file, decomposes the tree structure with indentation, and visually displays the parsed tree structure with the interface.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Debugging And Monitoring (AREA)

Description

显示通讯数据包的实现方法、 客户端、 服务端及系统 技术领域
本发明涉及一种通讯领域, 尤其涉及一种直观显示通讯数据包的实现 方法、 客户端、 服务端及系统。 背景技术
在业务软件开发中, 经常涉及到通讯平台与外部系统的通讯问题, 目 前可以在通讯平台上加载多个通讯接口来实现不同的对外通讯协议, 这些 通讯协议大量用到自定义的通讯协议。
但是实际运行中, 通讯程序的调试存在着很大的问题, 主要表现如下: 一、 通讯程序数据包跟踪工具欠缺, 导致在现场调试时, 没有有效的 手段和对方进行沟通。
二、 如果只是靠应用程序打印日志, 一些有用的信息在日志中没有体 现。
三、 通讯日志欠缺, 在运行中, 需要根据通讯消息进行问题分析和定 位, 但是如果用普通的抓包工具来抓包分析, 则得到的全是二进制数据流, 无法直观的显示每个字段的含义及值。 发明内容
本发明要解决的技术问题是提供一种能够直观显示通讯数据包的显示 通讯数据包的实现方法、 客户端、 服务端及系统。
为了达到上述目的, 本发明的技术方案是这样实现的:
本发明提供了一种显示通讯数据包的实现方法, 该方法包括: 客户端向服务端发送携带有业务线程号的开始跟踪消息, 指示服务端 开始记录所述业务线程号对应的业务线程传输的数据包;
所述客户端向所述服务端发送携带有所述业务线程号的结束跟踪消 息, 指示所述服务端停止记录所述业务线程号对应的业务线程传输的数据 包;
所述客户端获取所述服务端记录的所述数据包, 并显示所述数据包。 进一步地, 所述客户端获取所述服务端记录的所述数据包, 并显示所 述数据包的步骤包括:
所述客户端接收所述服务端根据所述结束跟踪消息返回的应答消息, 所述应答消息中包括: 跟踪文件的文件名和路径, 所述跟踪文件包括记录 的所述数据包;
所述客户端根据所述跟踪文件的文件名和路径从所述服务端获取所述 跟踪文件;
所述客户端对所述跟踪文件进行解析, 生成携带数据结构的数据包; 所述客户端显示所述携带数据结构的数据包。
进一步地, 所述客户端获取所述服务端记录的所述数据包, 并显示所 述数据包的步骤包括:
所述客户端实时从所述服务端获取记录的所述数据包, 形成跟踪文件; 所述客户端对所述跟踪文件进行解析, 生成携带数据结构的数据包; 所述客户端实时显示所述携带数据结构的数据包。
进一步地, 所述客户端对所述跟踪文件进行解析, 生成携带数据结构 的数据包的步骤具体为:
所述客户端利用缩进结构解析文件对所述跟踪文件进行解析, 生成带 缩进结构的数据包。
进一步地,所述缩进结构具体为:树型结构或者可扩展标记语言( XML ) 形成的缩进结构。 本发明还提供了一种客户端, 该客户端包括:
第一发送模块, 用于向服务端发送携带有业务线程号的开始跟踪消息, 指示服务端开始记录所述业务线程号对应的业务线程传输的数据包;
第二发送模块, 用于向所述服务端发送携带有所述业务线程号的结束 跟踪消息, 指示所述服务端停止记录所述业务线程号对应的业务线程传输 的数据包;
获取模块, 用于从所述服务端获取记录的所述数据包;
显示模块, 用于将所述数据包显示。
其中, 所述获取模块包括:
第一接收子模块, 用于接收所述服务端根据所述结束跟踪消息返回的 应答消息; 所述应答消息中包括: 跟踪文件的文件名和路径, 所述跟踪文 件包括记录的所述数据包;
获取子模块, 用于根据所述跟踪文件的文件名和路径从所述服务端获 取所述跟踪文件;
解析子模块, 用于对所述跟踪文件进行解析, 生成携带数据结构的数 据包, 并提供给所述显示模块显示。
进一步地, 所述获取模块包括:
第二接收子模块, 用于实时接收来自服务端记录的所述数据包, 形成 跟踪文件;
解析子模块, 用于对所述跟踪文件进行解析, 生成携带数据结构的数 据包, 并提供给所述显示模块显示。
所述解析子模块, 进一步用于利用缩进结构解析文件对所述跟踪文件 进行解析, 生成带缩进结构的数据包, 并提供给所述显示模块显示;
所述缩进结构为树型结构、 或者 XML形成的缩进结构。
本发明还提供了一种服务端, 该服务端包括: 第一接收模块, 用于接收客户端发送的携带有业务线程号的开始跟踪 消息;
第一处理模块, 用于将所述开始跟踪消息转发到所述业务线程号对应 的业务线程中处理, 记录所述业务线程传输的数据包;
第二接收模块, 用于接收所述客户端发送的携带有所述业务线程号的 结束跟踪消息;
第二处理模块, 用于将所述结束跟踪消息转发到所述业务线程号对应 的业务线程中处理;
发送模块, 用于根据所述结束跟踪消息向所述客户端返回记录的所述 数据包, 供所述客户端将所述数据包显示。
其中, 所述发送模块包括: 第一发送子模块、 或者第二发送子模块, 其中:
所述第一发送子模块, 用于根据所述结束跟踪消息向客户端返回应答 消息, 所述应答消息中包括: 跟踪文件的文件名和路径; 所述跟踪文件包 括记录的所述数据包;
所述第二发送子模块, 用于实时的把记录的所述数据包传送到客户端。 本发明还提供了一种通讯系统, 该系统包括:
客户端, 用于向服务端发送携带有业务线程号的开始跟踪消息和携带 有所述业务线程号的结束跟踪消息; 还用于接收服务端返回的数据包, 并 将所述数据包显示;
服务端, 用于接收所述客户端发送的所述开始跟踪消息和所述结束跟 踪消息, 并根据所述业务线程号, 记录所述业务线程号对应的业务线程传 输的数据包; 并向所述客户端返回所述数据包。
本发明的上述技术方案的有益效果如下:
上述方案中, 客户端通过向服务端发送开始跟踪消息, 其中开始跟踪 消息中包含有业务线程号, 服务端根据该业务线程号把开始跟踪消息转发 到该业务线程中处理, 获取该业务线程传输的数据包。 客户端还发送结束 跟踪消息, 同时结束跟踪消息中也带有该业务线程号, 服务端把结束跟踪 消息分发到该业务线程中处理; 客户端从服务端获取数据包, 并在界面上 直观的显示, 这样提高了现场调试和维护的工作效率。 附图说明
图 1为本发明的实施例客户端显示通讯数据包的实现方法流程示意图; 图 2为本发明的实施例服务端发送跟踪文件的方法流程示意图; 图 3为本发明的实施例客户端的结构示意图;
图 4为本发明的实施例服务端的结构示意图;
图 5为本发明的实施例显示通讯数据包的实现系统结构示意图; 图 6为图 5所示系统的处理开始跟踪消息的流程示意图;
图 7为图 5所示系统的处理结束跟踪消息的流程示意图。 具体实施方式
为使本发明要解决的技术问题、 技术方案和优点更加清楚, 下面将结 合附图及具体实施例进行详细描述。
本发明针对现有技术中, 通讯日志欠缺, 普通的抓包工具进行抓包分 析, 产生的二进制数据流, 无法直观的显示每个字段的含义及值的问题, 提供一种能够直观显示通讯数据包, 提高现场调试和维护的工作效率的显 示通讯数据包的实现方法、 客户端、 服务端及系统。
如图 1所示, 本发明的实施例显示通讯数据包的实现方法, 包括: 步骤 11 , 客户端向服务端发送携带有业务线程号的开始跟踪消息, 指 示服务端开始记录该业务线程号对应的业务线程传输的数据包。
该业务线程可以是要跟踪的业务线程; 一个业务线程在系统运行时, 会时刻接收或者发送数据包, 服务端在收到开始跟踪消息后, 会对该开始 跟踪消息中携带的要跟踪的业务线程号对应的业务线程所有接收或者发送 的数据包进行记录。
步骤 12, 客户端向服务端发送携带有业务线程号的结束跟踪消息, 指 示服务端停止记录业务线程号对应的业务线程传输的数据包。
服务端收到结束跟踪消息后, 会将该结束跟踪消息转发到其携带的业 务线程号对应的业务线程中处理, 服务端会停止记录数据包, 关闭文件句 柄。
步骤 13 , 客户端获取服务端记录的数据包, 并直观显示数据包。
该实施例中, 客户端可以为一个可以显示 Web界面的客户端, 也可以 为一个可以显示用可扩展标记语言(Xml )生成的界面的客户端, 该客户端 将开始跟踪消息发送给服务端, 服务端根据该开始跟踪消息打开跟踪文件, 并根据该开始跟踪消息中携带的业务线程号, 记录业务线程号对应的业务 线程(即要跟踪的业务线程)所有接收和发送的数据包; 在接收到结束跟 踪消息时, 服务端就会停止数据包的记录; 客户端再从该服务端获取这些 数据包并直观显示, 特别的, 客户端可以采用缩进结构的方式显示数据包, 特别是树型结构, 这样通过客户端就能很容易明白获取的数据包的信息及 含义, 可以清晰显示出通讯数据包的每一个字段, 利于现场定位问题, 提 高现场调试和维护的工作效率。
其中, 具体实现时, 上述步骤 13可具体包括:
步骤 1311 , 客户端接收服务端根据结束跟踪消息返回的应答消息, 该 应答消息中包括: 跟踪文件的文件名和路径, 跟踪文件包括数据包;
步骤 1312, 客户端根据跟踪文件的文件名和路径, 从服务端获取跟踪 文件, 例如该客户端接收到该跟踪文件的文件名和路径后, 可以通过文件 传输协议( FTP )函数获取跟踪文件到本地, 当然也可以通过专门的下载工 具将跟踪文件下载到本地;
步骤 1313 ,客户端对跟踪文件进行解析, 生成携带数据结构的数据包; 步骤 1314, 客户端显示携带数据结构的数据包。
另外, 步骤 13还可具体包括:
步骤 1321 ,客户端实时从服务端获取要跟踪的业务线程传输的数据包, 形成跟踪文件;
步骤 1322,客户端对跟踪文件进行解析, 生成携带数据结构的数据包; 步骤 1323 , 客户端实时显示所述携带数据结构的数据包。
在上述步骤 1313或者步骤 1322中, 客户端可利用缩进结构解析文件 对跟踪文件进行解析, 生成带缩进结构的数据包, 并将携带缩进结构的数 据包进行显示。
该缩进结构解析文件可以选择要跟踪的业务线程号对应的业务线程的 解析文件, 该解析文件符合该业务线程处理数据包规则, 该解析文件可以 包含: 数据包 ID, 整个数据包的长度, 各个参数名称, 参数类型, 参数长 度(整型或者字符串), 是否需要转换字节序, 该参数对应结构的缩进级别 等。 特别的, 该缩进结构可以是树型, 也可以是用 Xml标记语言生成的缩 进结构, 该缩进结构的数据包以树型显示在 Web界面上, 在本地 Web界面 上显示时, 界面还会设置一些过滤条件, 根据这些过滤条件选择记录的数 据包。
当然客户端也可以以其它直观显示的方式, 如可以利用线型解析文件 对跟踪文件进行解析, 获取线型结构的数据包; 或者利用星型解析文件对 跟踪文件进行解析, 获取星型结构的数据包; 或者利用环型解析文件对跟 踪文件进行解析; 或者其它解析文件对跟踪文件进行解析, 获取具有一定 数据结构的数据包, 显示在客户端, 如显示在客户端的 Web界面上, 这样 可以直观清楚地了解获取的数据包的含义, 从而提高通讯程序现场调试和 维护的工作效率。
需要说明的是: 这些线型解析文件、 星型解析文件或环型解析文件的 结构可以与上述树型解析文件的结构类似。
如图 2所示, 本发明的实施例还提供一种发送跟踪文件的方法, 包括: 步骤 21 ,服务端接收客户端发送的携带有业务线程号的开始跟踪消息, 根据要跟踪的业务线程号, 将开始跟踪消息转发到该业务线程号对应的业 务线程中处理, 获取业务线程传输的数据包; 该业务线程可以为要跟踪的 业务线程;
步骤 22,服务端接收客户端发送的携带有业务线程号的结束跟踪消息, 根据业务线程号, 将结束跟踪消息转发到该业务线程号对应的业务线程中 处理;
步骤 23 , 服务端根据结束跟踪消息向客户端返回数据包。
具体来讲, 该步骤 23可具体为:
服务端根据结束跟踪消息, 产生应答消息, 并向客户端返回应答消息, 该应答消息包括有跟踪文件的文件名和路径, 该跟踪文件包括有上述业务 线程传输的所有数据包; 或者
服务端实时向客户端返回数据包, 并在接收到结束跟踪消息时, 停止 向客户端返回数据包。
如图 3所示, 与上述图 1所述方法相应的, 本发明的实施列还提供一 种客户端 30, 包括:
第一发送模块 31 , 用于向服务端发送携带有业务线程号的开始跟踪消 息, 指示服务端开始记录业务线程号对应的业务线程传输的数据包;
第二发送模块 32, 用于向服务端发送携带有业务线程号的结束跟踪消 息, 指示服务端停止记录业务线程号对应的业务线程传输的数据包;
获取模块 33 , 用于从服务端获取数据包; 显示模块 34, 用于将数据包直观显示在本地。
其中, 该第一发送模块 31和第二发送模块 32具体实现时, 可以为客 户端 30的一通讯模块, 具体来讲, 可以为一 WEB通讯模块, 用于与服务 端建立连接, 可以建立 TCP/IP连接, 并向服务端发送开始跟踪消息, 并且 开始跟踪消息中允许填入业务线程号, 或者用来发送结束跟踪消息, 并且 结束跟踪消息中同样允许填入业务线程号;
获取模块 33从服务端获取数据包, 具体来讲, 可以包括:
第一接收子模块, 用于接收来自服务端根据结束跟踪消息返回的应答 消息, 其中, 应答消息中带有跟踪文件的路径和文件名, 该跟踪文件包括 有所述数据包;
获取子模块, 用于根据跟踪文件的文件名和路径, 从服务端获取包含 有数据包的该跟踪文件; 具体来讲, 可以通过 FTP函数或者其它专门下载 工具获取跟踪文件到本地;
解析子模块, 用于对跟踪文件进行解析, 生成携带数据结构的数据包; 所述显示模块 34将所述携带数据结构的数据包显示在本地;
或者该获取模块 33还可包括:
第二接收子模块, 用于实时接收来自服务端的数据包, 形成跟踪文件; 解析子模块, 可以解析所述跟踪文件, 获取携带数据结构的数据包; 显示模块 34可以将解析后的携带数据结构的数据包实时显示在本地。 该解析子模块可以选择与该业务线程对应的解析文件, 该解析文件是 提前写好的, 是符合该线程处理数据包规则的, 该解析文件包含, 数据包 ID, 整个数据包的长度, 各个参数名称, 参数类型, 参数长度(整型, 字 符串), 是否需要转换字节序, 该参数对应结构的缩进级别。
上述解析子模块还可具体为: 缩进结构解析子模块, 用于利用缩进结 构解析文件对所述跟踪文件进行解析, 获取带缩进结构的数据包; 所述显 示模块 34将解析后的所述带缩进结构的数据包显示在本地。
其中, 该缩进结构解析文件可以选择要跟踪的业务线程号对应的业务 线程的解析文件, 该解析文件符合该业务线程处理数据包规则, 该解析文 件可以包含: 数据包 ID, 整个数据包的长度, 各个参数名称, 参数类型, 参数长度(整型或者字符串), 是否需要转换字节序, 该参数对应结构的缩 进级别等。 特别的, 该缩进结构可以是树型, 也可以是用 Xml标记语言生 成的缩进结构, 该缩进结构的数据包以树型显示在 Web界面上时, 界面还 会设置一些过滤条件, 根据这些过滤条件选择记录的数据包。
当然客户端也可以以其它直观显示的方式, 如解析模块可以利用线型 解析文件对跟踪文件进行解析, 获取线型结构的数据包, 或者利用星型解 析文件对跟踪文件进行解析, 获取星型结构的数据包, 或者利用环型解析 文件对跟踪文件进行解析, 或者其它解析文件对跟踪文件进行解析, 获取 具有一定数据结构的数据包, 显示模块 34将该携带定数据结构的数据包显 示在客户端, 如显示在客户端的 Web界面上, 这样可以直观清楚地了解获 取的数据包的含义, 从而提高通讯程序现场调试和维护的工作效率。 其中, 这些线型解析文件、 星型解析文件或环型解析文件的结构可以与上述树型 解析文件的结构类似。
如图 4所示, 本发明的实施例还提供一种服务端 40, 包括:
第一接收模块 41 , 用于接收客户端发送的携带有业务线程号的开始跟 踪消息;
第一处理模块 42, 用于根据业务线程号, 将开始跟踪消息转发到该业 务线程号对应的业务线程中处理, 记录业务线程传输的数据包;
第二接收模块 43 , 用于接收客户端发送的携带有业务线程号的结束跟 踪消息;
第二处理模块 44, 用于根据结束跟踪消息, 将结束跟踪消息转发到该 业务线程号对应的业务线程中处理;
发送模块 45 , 用于根据结束跟踪消息向客户端返回数据包。
其中, 该第一接收模块 41和第二接收模块 43可以为一通讯模块, 用 于与客户端建立连接, 如 TCP/IP连接, 并接收客户端发送来的开始跟踪消 息和结束跟踪消息, 并由第一处理模块 42将该开始跟踪消息转发到相应的 业务线程中处理, 第二处理模块 44将该结束跟踪消息转发到相应的业务线 程中处理。
发送模块 45在具体实现时, 可以具体为:
第一发送子模块, 用于根据结束跟踪消息向客户端返回应答消息, 该 应答消息中包括: 跟踪文件的文件名和路径; 客户端获得该文件名和路径 后, 从该服务端下载该包含有所述数据包的跟踪文件; 或者
第二发送子模块, 用于实时的把数据包传送到客户端; 客户端获得数 据包后, 进行解析, 实时进行显示。
如图 5所示, 本发明的实施例还提供一种通讯系统, 包括:
客户端 30,用于向服务端 40发送携带有业务线程号的开始跟踪消息和 携带有业务线程号的结束跟踪消息;
服务端 40, 用于接收客户端 30发送的开始跟踪消息和结束跟踪消息, 并根据业务线程号, 记录业务线程号对应的业务线程传输的数据包; 并向 客户端 30返回所述数据包; 该服务端 40具体实现时, 可以是一个通讯平 台 (IMPCOMM );
该客户端 30还接收服务端 40返回的数据包, 并将所述数据包直观显 示在本地。 该客户端 30具体实现时, 可以为一 Web平台。
该系统实施例中, 上述图 3所述该客户端 30的所有特征均可适用于本 系统的实施例中, 上述图 4所述服务端 40的所有特征均可适用于本系统的 实施例中, 在此不再赘述。 下面结合图 6和图 7说明上述实施例的具体实现流程, 如图 6所示: 1 )客户端 (如 WEB平台 )与月良务端 (如 IMP通讯平台 )建立通讯连 接;
2 )客户端发送开始跟踪消息, 其中开始跟踪消息中包含要跟踪的业务 线程号;
3 )服务端接收该开始跟踪消息, 解析出业务线程号, 根据业务线程号 把该开始跟踪消息分发到业务线程中;
4 )业务线程接收到开始跟踪消息, 记录该业务线程所有的接收和发送 的数据包, 数据包记录入跟踪文件中;
5 )业务线程返回应答消息给服务端, 服务端返回应答消息给客户端, 客户端界面显示开始跟踪成功的标志。
如图 7所示:
6 )客户端与服务端建立通讯连接, 并发送结束跟踪消息, 结束跟踪消 息中携带有要结束跟踪的业务线程的线程号;
7 )服务端接收该结束跟踪消息, 解析出业务线程号, 根据业务线程号 把该结束跟踪消息分发到业务线程中;
8 )业务线程接收到结束跟踪消息,停止写数据包文件, 关闭文件句柄;
9 )业务线程返回应答消息给服务端, 服务端返回应答消息给客户端;
10 )客户端根据应答消息中的文件名和路径, 到服务端取下跟踪文件;
11 )客户端选择加载符合该线程的界面显示解析文件, 界面显示树型 结构的网络数据包, 界面同时可提供设置过滤条件, 过滤数据包。
下面再结合图 6和图 7说明上述实施例另一具体实现流程:
该具体实现流程与上述实现流程的区别在于, 服务端不在本地生成跟 踪文件, 而是实时的把该数据包传输给客户端; 客户端实时地接收数据包, 并实时根据事先加载好的解析文件的格式, 经过解析后, 实时用树型结构 显示出来。
上述的所有实施例中, 开始跟踪消息包括: 消息号和消息体, 其中消 息体中包含要跟踪的业务线程号; 而结束跟踪消息也包括: 消息号和消息 体, 其中消息体包含要结束跟踪的业务线程号。
需要说明的是, 在上文中以步骤的形式示出并描述了本发明的方法实 施例的技术方案, 这些步骤可以在诸如一组计算机可执行指令的计算机系 统中执行。 虽然在相关的附图中示出了逻辑顺序, 但是在某些情况下, 可 以以不同于此处的顺序执行所示出或描述的步骤。 另外, 在不冲突的情况
Figure imgf000015_0001
综上所述, 本发明的实施例, 客户端通过向服务端发送开始跟踪消息 和结束跟踪消息, 其中开始跟踪消息中包含要跟踪的业务线程号, 服务端 根据该业务线程号把开始跟踪消息转发到该业务线程中处理。 客户端还发 送结束跟踪消息, 同时结束跟踪消息中也带有要结束跟踪的业务线程号, 服务端把结束跟踪消息分发到该业务线程中处理, 同时服务端有回应客户 端请求消息的功能; 客户端把获取到的跟踪文件, 用解析文件进行解析, 分解出带缩进的树型结构, 并把解析好的树型结构用界面直观的显示出来。 通过将基于 WEB 界面应用程序与通讯平台相结合来显示通讯平台的网络 数据包, 相比于现有技术, 显示更直观, 且提高了现场调试和维护的工作 以上所述是本发明的优选实施方式, 应当指出, 对于本技术领域的普 通技术人员来说, 在不脱离本发明所述原理的前提下, 还可以作出若干改 进和润饰, 这些改进和润饰也应视为本发明的保护范围。

Claims

权利要求书
1. 一种显示通讯数据包的实现方法, 其特征在于, 该方法包括: 客户端向服务端发送携带有业务线程号的开始跟踪消息, 指示服务端 开始记录所述业务线程号对应的业务线程传输的数据包;
所述客户端向所述服务端发送携带有所述业务线程号的结束跟踪消 息, 指示所述服务端停止记录所述业务线程号对应的业务线程传输的数据 包;
所述客户端获取所述服务端记录的所述数据包, 并显示所述数据包。
2. 根据权利要求 1所述的实现方法, 其特征在于, 所述客户端获取所 述服务端记录的所述数据包, 并显示所述数据包的步骤包括:
所述客户端接收所述服务端根据所述结束跟踪消息返回的应答消息, 所述应答消息中包括: 跟踪文件的文件名和路径, 所述跟踪文件包括记录 的所述数据包;
所述客户端根据所述跟踪文件的文件名和路径从所述服务端获取所述 跟踪文件;
所述客户端对所述跟踪文件进行解析, 生成携带数据结构的数据包; 所述客户端显示所述携带数据结构的数据包。
3. 根据权利要求 1所述的实现方法, 其特征在于, 所述客户端获取所 述服务端记录的所述数据包, 并显示所述数据包的步骤包括:
所述客户端实时从所述服务端获取记录的所述数据包, 形成跟踪文件; 所述客户端对所述跟踪文件进行解析, 生成携带数据结构的数据包; 所述客户端实时显示所述携带数据结构的数据包。
4. 根据权利要求 2或 3所述的实现方法, 其特征在于, 所述客户端对 所述跟踪文件进行解析, 生成携带数据结构的数据包的步骤具体为:
所述客户端利用缩进结构解析文件对所述跟踪文件进行解析, 生成带 缩进结构的数据包。
5. 根据权利要求 4所述的实现方法, 其特征在于, 所述缩进结构具体 为: 树型结构或者可扩展标记语言 (XML )形成的缩进结构。
6. 一种客户端, 其特征在于, 该客户端包括:
第一发送模块, 用于向服务端发送携带有业务线程号的开始跟踪消息, 指示服务端开始记录所述业务线程号对应的业务线程传输的数据包;
第二发送模块, 用于向所述服务端发送携带有所述业务线程号的结束 跟踪消息, 指示所述服务端停止记录所述业务线程号对应的业务线程传输 的数据包;
获取模块, 用于从所述服务端获取记录的所述数据包;
显示模块, 用于将所述数据包显示。
7. 根据权利要求 6所述的客户端, 其特征在于, 所述获取模块包括: 第一接收子模块, 用于接收所述服务端根据所述结束跟踪消息返回的 应答消息; 所述应答消息中包括: 跟踪文件的文件名和路径, 所述跟踪文 件包括记录的所述数据包;
获取子模块, 用于根据所述跟踪文件的文件名和路径从所述服务端获 取所述跟踪文件;
解析子模块, 用于对所述跟踪文件进行解析, 生成携带数据结构的数 据包, 并提供给所述显示模块显示。
8. 根据权利要求 6所述的客户端, 其特征在于, 所述获取模块包括: 第二接收子模块, 用于实时接收来自服务端记录的所述数据包, 形成 跟踪文件;
解析子模块, 用于对所述跟踪文件进行解析, 生成携带数据结构的数 据包, 并提供给所述显示模块显示。
9. 根据权利要求 7或 8所述的客户端, 其特征在于, 所述解析子模块, 进一步用于利用缩进结构解析文件对所述跟踪文件进行解析, 生成带缩进 结构的数据包, 并提供给所述显示模块显示;
所述缩进结构为树型结构、 或者 XML形成的缩进结构。
10. 一种服务端, 其特征在于, 该服务端包括:
第一接收模块, 用于接收客户端发送的携带有业务线程号的开始跟踪 消息;
第一处理模块, 用于将所述开始跟踪消息转发到所述业务线程号对应 的业务线程中处理, 记录所述业务线程传输的数据包;
第二接收模块, 用于接收所述客户端发送的携带有所述业务线程号的 结束跟踪消息;
第二处理模块, 用于将所述结束跟踪消息转发到所述业务线程号对应 的业务线程中处理;
发送模块, 用于根据所述结束跟踪消息向所述客户端返回记录的所述 数据包, 供所述客户端将所述数据包显示。
11.根据权利要求 10所述的服务端, 其特征在于, 所述发送模块包括: 第一发送子模块、 或者第二发送子模块, 其中:
所述第一发送子模块, 用于根据所述结束跟踪消息向客户端返回应答 消息, 所述应答消息中包括: 跟踪文件的文件名和路径; 所述跟踪文件包 括记录的所述数据包;
所述第二发送子模块, 用于实时的把记录的所述数据包传送到客户端。
12. 一种通讯系统, 其特征在于, 该系统包括:
客户端, 用于向服务端发送携带有业务线程号的开始跟踪消息和携带 有所述业务线程号的结束跟踪消息; 还用于接收服务端返回的数据包, 并 将所述数据包显示;
服务端, 用于接收所述客户端发送的所述开始跟踪消息和所述结束跟 消息, 并根据所述 ^务线程号, 记录所述 务线程号对应的 务线程传 输的数据包; 并向所述客户端返回所述数据包。
PCT/CN2010/072981 2009-06-02 2010-05-20 显示通讯数据包的实现方法、客户端、服务端及系统 WO2010139240A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910086116.0 2009-06-02
CNA2009100861160A CN101577714A (zh) 2009-06-02 2009-06-02 显示通讯数据包的实现方法、客户端、服务端及系统

Publications (1)

Publication Number Publication Date
WO2010139240A1 true WO2010139240A1 (zh) 2010-12-09

Family

ID=41272501

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/072981 WO2010139240A1 (zh) 2009-06-02 2010-05-20 显示通讯数据包的实现方法、客户端、服务端及系统

Country Status (2)

Country Link
CN (1) CN101577714A (zh)
WO (1) WO2010139240A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101577714A (zh) * 2009-06-02 2009-11-11 中兴通讯股份有限公司 显示通讯数据包的实现方法、客户端、服务端及系统
CN105610604B (zh) * 2015-12-16 2019-03-22 网宿科技股份有限公司 Tcp传输数据的图形化分析方法和系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6016558A (en) * 1997-12-09 2000-01-18 Electronics And Telecommunications Research Institute Communication event/message tracing method for RPC-based distribution processing program
CN1848752A (zh) * 2005-04-04 2006-10-18 华为技术有限公司 一种业务数据包跟踪实现方法
CN1984133A (zh) * 2005-12-12 2007-06-20 腾讯科技(深圳)有限公司 一种形成结构树的方法
CN101296119A (zh) * 2008-06-10 2008-10-29 中兴通讯股份有限公司 一种消息跟踪系统及方法
CN101577714A (zh) * 2009-06-02 2009-11-11 中兴通讯股份有限公司 显示通讯数据包的实现方法、客户端、服务端及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6016558A (en) * 1997-12-09 2000-01-18 Electronics And Telecommunications Research Institute Communication event/message tracing method for RPC-based distribution processing program
CN1848752A (zh) * 2005-04-04 2006-10-18 华为技术有限公司 一种业务数据包跟踪实现方法
CN1984133A (zh) * 2005-12-12 2007-06-20 腾讯科技(深圳)有限公司 一种形成结构树的方法
CN101296119A (zh) * 2008-06-10 2008-10-29 中兴通讯股份有限公司 一种消息跟踪系统及方法
CN101577714A (zh) * 2009-06-02 2009-11-11 中兴通讯股份有限公司 显示通讯数据包的实现方法、客户端、服务端及系统

Also Published As

Publication number Publication date
CN101577714A (zh) 2009-11-11

Similar Documents

Publication Publication Date Title
CN111083161A (zh) 数据传输的处理方法及装置、物联网设备
US20210250329A1 (en) Telecommunication system and method for traversing an application layer gateway firewall during the establishment of an rtc communication connection between an rtc client and an rtc server
EP3300311A1 (en) Interaction method and apparatus for smart watch and wechat platform, and smart watch
JP2010534029A (ja) ネットワーク上の需要メータデータの読込方法、及びシステム
CN108833565B (zh) 一种监控服务器的方法、装置、服务器和存储介质
WO2007112311A3 (en) System and method for managing performance of communication lines of a communication network
JP2014531786A (ja) 協働環境におけるフロー制御のためのおよび信頼性のある通信のための方法
JP2005269037A (ja) 電子メールサーバ、電子メール端末及びプログラム
CN110769009A (zh) 用户身份认证方法及系统
US8490173B2 (en) Unauthorized communication detection method
WO2017000572A1 (zh) 基于因特网内容适配协议的通信方法、客户端和服务器
WO2017181817A1 (zh) 一种服务器测试方法、装置及系统、存储介质
WO2010139240A1 (zh) 显示通讯数据包的实现方法、客户端、服务端及系统
CN106302349B (zh) 基于libpcap的HTTP包分析方法及装置
JP2012216040A (ja) ログ管理システム、ログ解析装置、ログ解析方法、およびログ解析プログラム
CN108287874B (zh) 一种db2数据库管理方法及装置
CN104283849A (zh) 弹窗数据推送、展示方法及装置、系统
US9992309B2 (en) Communication device and communication method
CN108769291A (zh) 一种报文处理方法、装置及电子设备
CN101184002A (zh) 一种点对点流量深度监测方法和设备
JP2012185848A (ja) ウェブアプリケーションから印刷するための方法およびシステム、ならびに対応するコンピュータプログラムと、対応するコンピュータ読み出し可能な記憶媒体
WO2012136050A1 (zh) 业务信令跟踪方法、系统及装置
CN105516319B (zh) 管理http报文的方法和装置
WO2016058401A1 (zh) 一种超文本传输协议数据还原方法及装置
JP4839796B2 (ja) ネットワーク装置における通信処理

Legal Events

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

Ref document number: 10782944

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10782944

Country of ref document: EP

Kind code of ref document: A1