CN106921716B

CN106921716B - Method and device for debugging network communication process of embedded equipment

Info

Publication number: CN106921716B
Application number: CN201511001560.XA
Authority: CN
Inventors: 马立铭; 李辰号
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2015-12-28
Filing date: 2015-12-28
Publication date: 2020-07-31
Anticipated expiration: 2035-12-28
Also published as: CN106921716A

Abstract

The embodiment of the application relates to the technical field of computers, in particular to a method and a device for debugging a network communication process of embedded equipment, which are used for solving the problems that the existing debugging method cannot be suitable for debugging the embedded equipment which does not provide the setting of proxy service parameters, or a business system is unstable due to the fact that debugging logic is added in an intrusive mode in an application program. The method comprises the following steps: the router receives a network request message sent by the embedded equipment; and respectively converting the destination address and the source address of the network request message into the IP address of the third-party debugging machine and the IP address of the router, and then sending the IP address and the source address to the third-party debugging machine. Because the router is added in the debugging system, the original function of setting the proxy parameter in the embedded equipment to send the network request to the third-party debugging machine is transferred to the router to be realized, so that the proxy parameter does not need to be set in the embedded equipment, and the debugging logic does not need to be added besides the service logic, thereby solving the problems.

Description

Method and device for debugging network communication process of embedded equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for debugging a network communication process of an embedded device.

Background

With the development of mobile internet and home digital entertainment ecology, the application development requirements for embedded systems (mobile phones, flat panels, internet televisions, etc.) are more and more vigorous. Network communication generally exists between an application program or a Web page based on an embedded system and a corresponding server, and in order to ensure the realization of the network communication function of the application program, the network communication process of embedded equipment, the application program on the embedded equipment and the like needs to be debugged in the development process. Debugging of the network communication process mainly refers to viewing network request data and network response data of the communication process.

A debugging system for debugging an embedded device is generally composed of the embedded device, a third party debugging machine, and a network server (i.e., a remote server corresponding to an application). This is because, limited by the display output conditions of the embedded device itself or the application program, it is not feasible to view data directly on the embedded device, and the data needs to be output to a third party debugging machine for presentation in some way.

The existing network communication network method for debugging embedded devices generally has the following two methods:

the first is debugging by actively setting proxy parameters (such as IP and port of proxy server or a pac UR L file) in the embedded device:

step 11: setting proxy parameters: starting proxy server software on a third-party debugging machine, and recording a port number occupied by the proxy server software; then setting proxy service parameters in the embedded equipment, namely setting the IP address of the third party debugging machine as the address of a proxy server of the embedded equipment, and taking the recorded port number as an embedded proxy port;

step 12: the embedded equipment sends a network request message to a network server;

at this time, since the third-party debugging machine is set as the proxy server of the embedded device in step 1, the network request message sent in step 2 is all forwarded to the third-party debugging machine, and the proxy server software started on the third-party debugging machine serves as a "man-in-the-middle" to contact with the outside.

Step 13: and the proxy server software on the third-party debugging machine intercepts the network request message, sends the network request message to a network server, and displays network communication data in the network request message, thereby achieving the purpose of debugging.

After step 13, the network server returns a network response to the network request message to the third-party debugging machine.

Step 14: and the proxy server software on the third-party debugging machine intercepts and captures the network response sent by the network server aiming at the network request message, sends the network response to the embedded equipment, and displays the network communication data in the network response, thereby achieving the purpose of debugging.

The process from step 12 to step 14 is also shown in fig. 1. In fig. 1, C represents an embedded device, M represents a third party debugging machine, and S represents a network server.

And the second method comprises the following steps: the method comprises the following steps of implanting redundant codes (irrelevant to service and codes for realizing debugging logic) special for debugging in an application program or a Web page in advance and enabling the codes to be online along with the service logic:

when debugging is needed, the following steps are executed:

step 21: opening a debugging switch in an APP installed in the embedded equipment or a Web page running in a browser;

step 22: the APP or Web page carries out normal communication with the server on one hand, and on the other hand, sends data to a third-party debugging machine through the debugging logic;

step 23: the third party debugging machine receives and displays the received information.

The process from step 21 to step 23 is also shown in fig. 2. C, M, S in fig. 2 has the same meaning as in fig. 1.

However, for the first debugging method, it is necessary to set related proxy parameters on the embedded device, but since the embedded system is closed compared with the computer operating system of the x86 system, it is very likely that a function or an entry for actively setting proxy service parameters is not provided (for example, Android system 4.0 and the following systems do not support input of proxy parameters), and thus, this method has limitations. For the second debugging method, it needs to add debugging logic, and this addition is intrusive to normal business logic (no debugging logic should exist in APP or Web page), and increases unstable factors of business system.

Therefore, two existing debugging methods have the problems that the existing debugging methods cannot be applied to the debugging of embedded devices which do not provide the setting of proxy service parameters, or the business system is unstable due to the fact that debugging logic is added in an intrusive mode in an application program, and therefore a new debugging method is urgently needed to overcome the defects.

Disclosure of Invention

The embodiment of the application provides a method and a device for debugging a network communication process of embedded equipment, which are used for solving the problems that the existing debugging method cannot be suitable for debugging the embedded equipment which does not provide the setting proxy service parameters, or a debugging logic is added in an intrusive mode in an application program to cause instability of a service system.

A method for debugging a network communication process of an embedded device comprises the following steps:

the router receives a network request message sent by embedded equipment, wherein the source address of the network request message is the IP address of the embedded equipment, and the destination address of the network request message is the IP address of a network server and is used for requesting the network server to provide network service;

respectively converting the destination address and the source address of the network request message into the IP address of a third-party debugging machine and the IP address of the router;

and sending the network request message with the source address and the destination address converted to a third-party debugging machine so as to enable the third-party debugging machine to display the network request data in the network request message.

the embedded equipment determines the IP address of the network server;

generating a network request message by taking the determined IP address of the network server as a destination address and the IP address of the embedded equipment as a source address, wherein the network request message is used for requesting the network server to provide network service;

and sending the generated network request message to a network server through a router, wherein the router converts a source address and a destination address of the network request message and then sends the network request message to a third-party debugging machine.

the third party debugging machine receives a network request message sent by embedded equipment through a router, wherein the source address of the network request message is the IP address of the router, and the destination address of the network request message is the IP address of the third party debugging machine and is used for requesting a network server to provide network service;

analyzing the received network request message to obtain network request data;

and displaying the network request data.

An apparatus for debugging a network communication process of an embedded device, comprising:

the network server comprises a receiving unit, a sending unit and a receiving unit, wherein the receiving unit is used for receiving a network request message sent by embedded equipment, the source address of the network request message is the IP address of the embedded equipment, and the destination address of the network request message is the IP address of the network server and is used for requesting the network server to provide network service;

a conversion unit, configured to convert a destination address and a source address of the network request packet into an IP address of a third-party debugging machine and an IP address of the router, respectively;

and the sending unit is used for sending the network request message with the source address and the destination address converted to the third-party debugging machine so as to enable the third-party debugging machine to display the network request data in the network request message.

a determining unit for determining an IP address of the network server;

a message generating unit, configured to generate a network request message by using the IP address of the network server determined by the determining unit as a destination address and using the IP address of the embedded device as a source address, where the network request message is used to request the network server to provide a network service;

and the sending unit is used for sending the generated network request message to a network server through a router, wherein the router converts a source address and a destination address of the network request message and then sends the network request message to a third-party debugging machine.

the receiving unit is used for receiving a network request message sent by the embedded equipment through a router, wherein the source address of the network request message is the IP address of the router, and the destination address of the network request message is the IP address of the third-party debugging machine and is used for requesting the network server to provide network service;

the analysis unit is used for analyzing the received network request message to obtain network request data;

and the display unit is used for displaying the network request data.

In the scheme of the embodiment of the application, because the router is added in the debugging system, the original function of setting the proxy parameter in the embedded device to send the network request to the third-party debugging machine is transferred to be realized in the router, so that the proxy parameter does not need to be set in the embedded device, and the debugging logic does not need to be added outside the service logic, thereby solving the problem that the existing debugging method cannot be suitable for debugging the embedded device which does not provide the proxy service parameter, or the service system is unstable due to the fact that the debugging service logic is added in an application program.

Drawings

FIG. 1 is a schematic diagram of a debugging process of a first debugging method provided in the background of the present application;

FIG. 2 is a schematic diagram of a debugging process of a first debugging method provided in the background of the present application;

fig. 3 is a schematic diagram illustrating an application of a NAT technology in the prior art according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a debugging system for debugging a network communication process of an embedded device according to an embodiment of the present application;

fig. 5 is a schematic diagram of a method for debugging a network communication process of an embedded device according to an embodiment of the present application;

FIG. 6 is a schematic workflow diagram of a middleware mechanism provided in an embodiment of the present application;

fig. 7 is a schematic diagram illustrating a change of a source address and a destination address of a network request/response message during a communication process according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a first apparatus for debugging a network communication process of an embedded device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a second apparatus for debugging a network communication process of an embedded device according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a third apparatus for debugging a network communication process of an embedded device according to an embodiment of the present application.

Detailed Description

In order to solve the problem that the existing debugging method cannot be applied to the debugging of embedded equipment which does not provide the setting of proxy service parameters, or the problem that a service system is unstable due to the fact that debugging logic is added in an application program in an intrusive mode, the embodiment of the application provides a novel system, method and device for debugging the network communication process of the embedded equipment.

In order to clearly describe the solution of the embodiment of the present application, first, concepts and meanings of a Network Address Translation (NAT) technology, a man-in-the-middle, and an OpenSS L in the prior art related to the solution of the embodiment of the present application are explained, then, a system and a debugging principle for debugging a Network communication process of an embedded device provided by the embodiment of the present application are described, and finally, a debugging method and apparatus provided by the present application are described in detail through each embodiment.

First, related concepts

NAT: is a technique for rewriting a source address or a destination address when an IP packet passes through a router or a firewall. NAT is applied to routers as a conversion scheme of private IP and public IP that occurs to solve the shortage of IPv4 addresses. As shown in fig. 3, the IP message includes a Source Address (SA) and a Destination Address (DA), and when the request message is sent from the internal network to the external network, the SA is changed after being processed by the NAT, and when the response message replied by the external network is received by the internal network, the DA is changed after being processed by the NAT.

The middle person: in the fields of cryptography and computer security, Man-in-the-middle (MITM) refers to a role that creates independent contacts with both ends of a communication, respectively, and exchanges data it receives so that both ends of the communication think they are talking directly to each other over a private connection, but in fact the entire conversation is completely controlled by the Man-in-the-middle.

OpenSS L OpenSS L is a powerful Secure socket layer cryptographic library, and implements basic encryption and decryption functions including Secure Sockets L layer (SS L) and Transport layer Security (Transport L layer Security, T L S) protocols.

Secondly, the system for debugging the network communication process of the embedded device and the debugging principle thereof

Fig. 4 is a schematic structural diagram of a system for debugging a network communication process of an embedded device according to the present application. The system comprises an embedded device C, a router R, a third party debugging machine M and a network server S;

compared with the existing debugging system, the router R is added, which is specially designed for the debugging system and can set a matching rule and convert a network address (a destination address of a message), and the function of the router R is different from that of a common router.

Normally, C sends a network request message to S, which is performed through the timing sequence 1-4-5-8 shown in fig. 4, R forwards the request faithfully according to the IP address of S requested by C, and the response of S returns to C after passing through R.

When debugging is needed, the NAT rule of R is set on C in advance, the network request message sent from C to S is intercepted and the destination address is changed when passing through R, that is, the destination address of the network request message is mainly converted/rewritten from the IP address of S to the IP address of M, so that the network request message is led into M. Therefore, M can replace S and serve C as a server side of C, all requests sent by C are changed to M without perception, and C becomes a 'middle man'.

After intercepting the network request message sent by R, M can forward the network request message to S as it is, S intercepts the request forwarded by M and sends the network response message to M, and M then forwards the network response message of S to C. The sequence of this process is 1-2-3-4-5-6-7-8 shown in fig. 4, and since both the network request message and the network response flow through M, M can acquire complete network communication process data and then present it on the display output device of M. At this time, the debugging personnel can check the network request data and the network response data in the communication process on the M to perform subsequent related debugging work.

After intercepting the network request message sent by C, M can also simulate S to send a network response message to C instead of forwarding the network request message to S. The sequence of this process is 1-2-3-8 shown in fig. 4, and since both the network request message and the network response flow through M, M can acquire complete network communication process data and then present the data on the display output device of M. At this time, the debugging personnel can check the network request data and the network response data in the communication process on the M to perform subsequent related debugging work.

It should be noted that the NAT rule for setting R on C is different from the NAT rule in the prior art: in the NAT rule set on C in the prior art, C rewrites only the source address and does not rewrite the destination address for the received network request message, whereas in the NAT rule set on C in the present application, on one hand, C rewrites the source address for the received network request message and on the other hand, rewrites the destination address for the received network request message, that is, the function of rewriting the destination address of C is exerted for the debugging process of the network communication process. Moreover, the prior art NAT rule is used for the translation of private network IP address and public network IP address, but in this application, C, R and M belong to the communication between the inside of the router, and do not relate to the public network, and the NAT translation of R does not relate to the translation of private network IP address and public network IP address.

In addition, according to the requirement of debugging, in the embodiment of the present application, other parameters may also be set on C, for example: whether to record a log in the C, an applicable protocol, a white list of the C to be debugged (NAT rules are only applicable to the IP in the white list) or a black list (NAT rules are not applicable to the IP in the black list), etc. The method for setting the NAT rule is to use a program to connect with C, and control the parameters of C through the interface of C.

The debugging system can be in a distributed deployment form or a central deployment form. The difference between distributed and central deployments is mainly: in the distributed system, M is the developer's own computer, and each is debugged with its own computer. In the central type, M is a server at the cloud end, and people share the server for debugging.

Embodiments of the method and apparatus for debugging a network communication process of an embedded device provided by the present application are described in detail below by embodiments:

as shown in fig. 5, which is a flowchart of a method for debugging a network communication process of an embedded device according to an embodiment of the present application, the method includes the following steps:

step 501: the embedded equipment determines the IP address of the network server;

after the network service to be provided is determined, the IP address of one network server can be selected from the IP addresses of the network servers providing the network service as the determined IP address of the network server.

Step 502: the embedded equipment generates a network request message by taking the determined IP address of the network server as a destination address and the IP address of the embedded equipment as a source address;

the network request message is used for requesting the network server to provide network service;

the network request message is an IP message.

Step 503: the embedded equipment sends the generated network request message to a network server through a router;

here, the embedded device is intended to send the network request message to the network server through the router, and the subsequent router converts the destination address of the network request message into the IP address of the third-party debugging device, so that the router will send the network request message subjected to the address conversion to the third-party debugging device, and the subsequent third-party debugging device can send the network request message to the network server.

Step 504: the router receives the network request message sent by the embedded equipment;

preferably, in order to ensure the accuracy and the safety of debugging and prevent the network request message which is not the embedded device to be debugged from being erroneously forwarded to the third-party debugging machine, an address white list or an address black list of the embedded device to be debugged can be preset in the router;

at this time, if the address white list of the embedded device to be debugged is set, after this step 504 and before the following step 506, it is determined whether the source address of the network request message belongs to the address white list of the embedded device to be debugged; if yes, go to step 506; if the result of the determination is negative, then a normal forwarding operation is performed, and the normal forwarding operation belongs to the prior art and is not described herein again.

If the address blacklist of the embedded device to be debugged is set, after the step 504 and before the following step 506, judging whether the source address of the network request message belongs to the address blacklist of the embedded device to be debugged; if the determination result is negative, go to step 506; if the determination result is yes, a normal forwarding operation is performed, and the normal forwarding operation belongs to the prior art and is not described herein again.

Step 505: the router converts the destination address and the source address of the network request message into the IP address of a third-party debugging machine and the IP address of the router respectively;

in this step 505, the NAT rule in this application is formed by the translation of the destination address of the network request message and the IP address of the third party debugging machine, and the translation of the source address of the network request message and the IP address of the router.

Here, the white list address or the black list address may not be set, step 505 is performed on all the network request messages, or the white list or the black list may be set. When the white list or the black list of the address of the embedded equipment to be debugged is not set, the IP address of the debugging machine of the third party is a main parameter of the NAT rule of the application; when setting the white list or the black list of the address of the embedded equipment to be debugged, the IP address of the debugging machine of the third party and the white list or the black list of the address of the embedded equipment to be debugged are necessary parameters of the NAT rule of the application; the following describes the determination/acquisition of the white list of the IP address of the third-party debugging machine and the address of the embedded device to be debugged:

the third party debugging machine can send a destination address adjusting instruction containing the IP address of the third party debugging machine and the IP address of the embedded device to the router for setting. When the third-party debugging machine sends an instruction to the router, knowing the IP address of the third-party debugging machine, the IP address of the embedded equipment needs to be acquired, and the acquisition of the IP address of the embedded equipment has the following two modes:

the first mode is as follows: directly inputting the IP address of the C in the M, namely receiving the IP address of the embedded equipment input by a user; and taking the IP address of the embedded equipment input by the user as the IP address of the embedded equipment contained in the destination address adjusting instruction.

The second mode is as follows: the method comprises the steps that a two-dimension code is generated in a third-party debugging machine, the content of the two-dimension code is a Web service address specially used for binding the embedded equipment and the third-party debugging machine, the embedded equipment scans the two-dimension code and then accesses the third-party debugging machine, and the third-party debugging machine acquires an IP address of the embedded equipment when intercepting an access request of the embedded equipment. The specific process is also the following steps 1) to 5):

step 1): generating a two-dimensional code on a third-party debugging machine, wherein the content of the two-dimensional code is a Web service address which is specially used for binding the embedded equipment and the third-party debugging machine;

step 2): the embedded equipment scans the two-dimensional code displayed on the third-party debugging machine;

step 3): the embedded equipment sends an access request message to the third-party debugging machine to access the Web service address;

step 4): a third party debugging tester receives an access request message sent by embedded equipment;

step 5): and the third party debugging machine takes the source address in the received access request message as the IP address of the embedded equipment contained in the destination address adjusting instruction sent to the router.

Then, the router can receive the destination address adjusting instruction sent by the third party debugging machine; and respectively taking the IP address of the third party debugging machine and the IP address of the embedded equipment contained in the destination address adjusting instruction as the IP address of the third party debugging machine for address conversion and the address white list of the embedded equipment to be debugged.

Further, considering that after the NAT rule of the present application is in effect, the embedded source IP address is replaced with the IP address of the router, which results in that the third-party debugging machine cannot distinguish the network request messages from different embedded devices, because both the destination address and the source address of the network request message are converted into the IP address of the third-party debugging machine and the IP address of the router by the router.

In order to enable a third-party debugging machine to distinguish different embedded devices, in the application, an independent debugging port is opened to distinguish the embedded devices when the embedded devices are bound with the third-party debugging machine, that is, one NAT rule describes an IP address of one embedded device and an address of the third-party debugging machine, and a corresponding debugging port is also arranged, so that the IP address of the embedded device corresponds to the debugging port, the third-party debugging machine can correspondingly obtain the IP address of the embedded device through the debugging port, and different embedded devices are distinguished.

Of course, when there is no need to distinguish different embedded devices or there is only one embedded device, the independent debugging port can be opened for debugging.

Specifically, when the NAT rule of the present application is set (before the NAT rule becomes effective), a debugging port parameter is added to the NAT rule, and accordingly, an independent process is started on the debugging port in the third-party debugging machine, a service is provided for the embedded device corresponding to the NAT rule, and the IP address of the embedded device is also recorded at this time, so that the problem that the embedded device cannot be distinguished by the third-party debugging machine at the service end after the NAT rule becomes effective can be solved. The detailed interaction process for distinguishing different embedded devices is realized as follows:

the first step is as follows: the embedded equipment sends a binding request message to the third party debugging machine;

the source address of the binding request message is the IP address of the embedded device, and the destination address is the IP address of the third party debugging machine.

Preferably, the binding request message may further include an application layer protocol supported by the embedded device;

the second step is that: a third party debugging machine receives a binding request message sent by the embedded equipment;

the third step: a third party debugging machine allocates a debugging port for the embedded equipment;

the third party debugging machine can start an independent process on the debugging port subsequently, and provides service for the embedded equipment from which the binding request message comes specially; and the third party debugging machine also carries the allocated debugging port number in a destination address adjusting instruction and sends the destination address adjusting instruction to the router, and the router records the corresponding relation among the IP address of the embedded equipment, the third party debugging machine and the debugging port number.

The fourth step: the third party debugging machine binds and stores the port number of the debugging port and the IP address of the embedded equipment;

if the binding request message includes an application layer protocol supported by the embedded device, in the third step and the fourth step, the third-party debugging machine allocates different debugging ports for different application layer protocols supported by the embedded device, and binds and stores the port number of the debugging port, the IP address of the embedded device and the application layer protocol.

At this time, the third party debugging machine can start an independent process on each debugging port, and is specially used for providing service for an application layer protocol of the embedded equipment from which the binding request message comes; and the third party debugging machine also carries the allocated debugging port number and the corresponding application layer protocol in a destination address adjusting instruction and sends the destination address adjusting instruction to the router, and the router records the corresponding relation among the IP address of the embedded equipment, the application layer protocol, the third party debugging machine and the debugging port number.

The fifth step: the third party debugging machine sends a binding response message to the embedded equipment, wherein the binding response message contains a binding result;

and a sixth step: and the embedded equipment receives the binding response message sent by the third party debugging machine.

Here, the binding may be ended when the binding result is that the binding is successful. And when the binding result is unsuccessful, re-executing the first step until the binding is successful.

At this time, in order to enable the third party debugging machine to distinguish different embedded devices, after the step 504 and before the step 505, determining a port number of a debugging port allocated by the third party debugging machine to the embedded device, where the third party debugging machine allocates different debugging ports to different embedded devices; and carrying a debugging port number in the network request message, wherein the third-party debugging machine allocates different debugging ports for different embedded devices.

Preferably, the network request message is considered to be different in the application layer protocol, for example: using a HyperText Transfer Protocol (HTTP) Protocol, a File Transfer Protocol (FTP), and a Simple Mail Transfer Protocol (SMTP), in order to facilitate the debugging of the network communication process using different application layer protocols, after step 504, before determining a port number of a debugging port allocated by a third-party debugging machine for the embedded device, the router also determines an application layer Protocol used by the network request packet;

at this time, determining the port number of the debugging port allocated to the embedded device by the third-party debugging machine specifically includes:

and determining a debugging port number allocated by a third-party debugging machine to the embedded equipment when the network request message is sent by using the determined application layer protocol, wherein the third-party debugging machine allocates different debugging ports to the same embedded equipment when the network request message is sent by using different application layer protocols.

Here, the third party debugging machine allocates different debugging ports to the application layer protocols supported by different embedded devices, for example, assuming that there are embedded devices C1 and C2, where the application layer protocols supported by C1 are HTTP, FTP and SNMP, and the application layer protocols supported by C2 are HTTP and FTP, the third party debugging machine allocates port numbers P1, P2 and P3 to the HTTP, FTP and SNMP of C1, respectively; the application layer protocols supported for C2 are assigned port numbers P4 and P5 for HTTP and FTP, respectively.

Step 506: the router sends the network request message with the source address and the destination address converted to a third party debugging machine;

if the router carries the debug port number in the network request message in the above step, in this step 506, the router sends the network request message that has the source address and the destination address converted and carries the debug port number.

Step 507: a third party debugging machine receives a network request message sent by embedded equipment through a router;

because the router performs address translation, the source address of the network request message received in step 507 is the IP address of the router, and the destination address is the IP address of the third party debugging machine;

step 508: the third party debugging tester analyzes the received network request message to obtain network request data;

if the received network request message includes the debug port number in this step 508, after this step 508 and before the following step 509, the third party debugging machine further searches the IP address of the embedded device bound by the debug port number included in the received network request message by using the binding relationship between the stored port number and the IP address of the embedded device;

in fig. 7, there are two embedded devices, which are C1 and C2, respectively, if the port number of the debug port allocated by the third party debug machine M for C1 is P1, and the port number of the debug port allocated for C2 is P2, then the binding relationship recorded in the third party debug machine M is the binding relationship between P1 and C1-IP (IP address of C1), and the binding relationship between P2 and C2-IP (IP address of C2).

When the embedded device is found, the sender of the received network request message is determined to be the embedded device represented by the IP address of the found embedded device, that is, the data from different embedded devices is identified.

Step 509: and the third party debugging machine displays the network request data.

If the IP address of the embedded device bound by the debugging port number included in the received network request message is found before step 509, in this step 509, the network request data and the found IP address of the embedded device may be correspondingly displayed. The network request data from different embedded devices can be separately displayed, so that a plurality of embedded devices can be simultaneously accessed and debugged, debugging personnel can conveniently distinguish the embedded devices, and the communication process of the embedded devices can be checked in a targeted manner.

After the above step 507, the third party debugging machine may process the received network request packet by using any one of the following two manners:

the first processing mode is as follows:

and forwarding the received network request message to a network server for normal data transceiving.

The specific implementation modes comprise the following two types:

implementation 111): sending the network request message to a network server; after receiving the network request message, the network server returns a network response message aiming at the network request message to a third-party debugging machine, and the third-party debugging machine receives the network response message sent by the network server; analyzing the network response message to obtain network response data; displaying the network response data;

implementation 112): through the mechanism of expanding service logic in the form of middleware, the middleware of each layer completes some processing works according to the passed message information (network request message and network response message), and hands over the work to the next middleware for continuous processing by executing a next method, and the work flow is shown as figure 6; the mechanism of the middleware can make the expansion of the processing logic very convenient and flexible.

Specifically, when the first processing mode is used, 2 pieces of middleware are created in the third-party debugging machine: agent middleware and parse response middleware; the proxy middleware is used for sending the network request message to a network server; the analysis response middleware is used for analyzing the received network response message and displaying the analyzed network response data;

at this time, the third party debugging machine can transmit the network request message to the agent middleware to trigger the agent middleware to send the network request message to the network server; then, receiving a network response message sent by the network server; and transmitting the network response message to an analysis response middleware to trigger the analysis response middleware to analyze the received network response message and display the analyzed network response data.

Fig. 7 shows a specific example of the change of the source address and the destination address of the network request/response message in the communication process in the first processing manner.

Two R are shown in fig. 7, which can be regarded as that one R in fig. 4 is functionally split into 2R, and the split into two R is for convenience of explaining the change of the source address and the destination address, and the essence of fig. 7 is the same as that in fig. 4. In FIG. 7, C1-IP indicates the IP address of the embedded device C1, S-IP indicates the IP address of the network server, P1 indicates the debugging port number allocated to C1 on M, R-IP indicates the IP address of the router R, M-IP indicates the IP address of the third party debugging machine M, and the network communication process of the embedded device C2 is similar to that of C1 and is not shown for the sake of simplicity and clarity of FIG. 7. The network communication process between M and S in fig. 7 is implemented by using the prior art NAT translation, and the two boxes with oblique lines are intended to emphasize the difference between the NAT translation in the present application and the NAT translation in the prior art.

When the third-party debugging machine forwards the received network request message, the network request message may be specifically sent to the router, and the router sends the received network request message sent by the third-party debugging machine to the network server at a pre-configured network transmission rate.

Here, in the debugging method of the present application, the router may perform fine control on the network transmission rate, and can better control network communication and simulate various scenarios compared to the existing debugging method, for the following specific reasons:

in order to develop, debug and test the embedded system application or Web page, an agent tool is usually used, however, the traditional agent tool is designed to meet the internet access requirement of the user, and the purpose of the application developer using the agent is to debug the network communication process. In the prior art, the function of auxiliary development and debugging is basically added on the basis of the traditional agent tool.

Analyzing the traditional proxy tool from the perspective of TCP/IP network layering, which only works at the application layer, belonging to the layer farthest from the bottom layer of network communication, it is obvious that controlling network communication at the application layer is not the best choice. For example, when debugging is applied, the network speed is often controlled to simulate a weak network environment, however, the application layer proxy has no capability to limit the network speed, and can only approximate the limitation of the network speed by a method of delaying output response. The problem is solved in a network layer, the network layer has the capability of controlling the network speed, and other fine control related to the network communication process can be realized in the network layer.

The four most important layers in the TCP/IP protocol are from bottom to top: data link layer, network layer, transport layer, application layer. Routers are devices that run at the network layer, while traditional proxy servers run at the application layer. The network layer of the router operation is lower relative to the application layer, and network communication can be effectively controlled. Besides the network speed control, routing control, customized DNS, customized firewall rules and the like can be carried out.

The fine control of the network speed refers to that the average rate, the highest rate and the lowest rate of the uplink and the downlink of the network can be set; the network speed of a certain specific device can be set, and the network speed of all devices can also be set; the network environment such as GPRS, 3G, 4G and the like can be simulated by setting parameters.

The second processing mode is as follows:

reserving the received network request message, simulating a network server to generate a network response message aiming at the network request message, and sending the simulated network response message to the embedded equipment through a router;

the specific implementation modes comprise the following two types:

implementation 211): determining an application layer protocol used by a received network request message; selecting an application layer protocol matched with the determined application layer protocol from the configured application layer protocols; simulating a network server to generate a network response message for the embedded equipment by using the selected application layer protocol; sending the generated network response message to the embedded equipment through a router; analyzing the generated network response message to obtain network response data; and displaying the network response data.

Implementation 212): using the form of middleware, the same basic idea as the implementation 112) described above. The method specifically comprises the following steps: three pieces of middleware are created for each application layer protocol in a third party debugging machine: simulating data middleware, proxy middleware and analysis response middleware, and placing the three middleware in the container of the created application layer service framework; for example, aiming at an application layer protocol FTP, an application layer service framework 1 is created, three middleware, namely simulation data middleware, agent middleware and analysis response middleware are placed in the application layer service framework, and a service is specially provided for a network request message using the application layer protocol FTP; aiming at a reference layer protocol HTTP, an application layer service framework 2 is created, three middleware, namely simulation data middleware, agent middleware and analysis response middleware are placed in the application layer service framework, and the application layer service framework is specially used for providing service for a network request message using an application layer protocol FTP.

The application layer service framework is used for determining an application layer protocol used by the received network request message and selecting the application layer protocol matched with the determined application layer protocol from the configured application layer protocols;

the simulation data middleware is used for skipping the proxy middleware according to a preset simulation data interception rule to directly generate a network response message; the agent middleware is used for reconstructing a request for the network server and forwarding and sending a response message of the network server to the embedded equipment according to the received request message; the analysis response middleware is used for analyzing the generated network response message to obtain network response data, and the network response data is displayed in a third-party debugging machine;

at the moment, transmitting the received network request message to an analog data middleware, trying to match the received network request message by the analog data middleware, and triggering the analog data middleware to generate a network response message if the received network request message is matched with a preset analog data interception rule;

if the simulation data middleware does not match the received network request message, continuing to transmit the request message to the proxy middleware to trigger the proxy middleware to reconstruct the request for the network server and transmit the response message of the remote server to the embedded equipment;

and transmitting the network response message sent by the simulation data middleware or the proxy middleware to the analysis response middleware to trigger the analysis response middleware to analyze the network response message and display the network response data obtained by analysis.

The second processing method realizes intercepting and deep controlling of requests and responses of the network, for example, according to a certain description of a developer, intercepting a specific network request and responding with specified data. On the other hand, compared with the traditional mode that the third party debugging machine is used as the proxy server, the expansibility of the protocol is improved, because: for embedded equipment, the identity of the third-party debugging machine is a normal network server, and what protocol needs to be supported in the network server can be configured, so that the expansibility is high.

Further, in consideration of network security, a network communication process is usually encrypted in business, which also increases difficulty in development and debugging of an application program or a Web page in an embedded system, and in the debugging process, a host that acquires or intercepts encrypted content is not a real server, and needs to intercept a request in a man-in-the-middle manner (i.e., a third party debugging machine in this application) to perform debugging work, so that the problem of trust of an embedded device to the untrusted third party debugging machine needs to be solved.

To this end, the present application provides a method for determining a third party debugging machine as a trusted third party debugging machine, including the following steps 301 to 313:

301, utilizing OpenSS L to sign and generate a root certificate, and storing the root certificate in a trusted third party debugging machine;

step 302: the embedded equipment sends a downloading request message to a trusted third party debugging machine;

step 303: a third party debugging machine receives a downloading request message sent by embedded equipment;

step 304: the third party debugging machine provides downloading service of the root certificate for the embedded equipment;

step 305: the embedded equipment downloads the root certificate by using a downloading service provided by a trusted third party debugging machine;

step 306: the embedded equipment installs the downloaded root certificate;

step 307: the embedded equipment sends an encryption request message to a third party debugging tester through a router, wherein the header of the encryption request message contains a domain name;

step 308: a third party debugging tester receives an encryption request message sent by the embedded equipment;

step 309: the third party debugging machine utilizes the root certificate to sign and send a corresponding domain name certificate for the domain name;

step 310: and the third party debugging machine sends an encrypted response message to the embedded equipment, wherein the encrypted response message carries the domain name certificate.

Step 311: the embedded equipment receives an encrypted response message sent by a third party debugging machine;

step 312: the embedded equipment identifies the domain name certificate by using the installed root certificate;

step 313: when the embedded equipment identifies the domain name certificate, the third party debugging machine which sends the encrypted response message is used as a trusted third party debugging machine;

therefore, the problem of trust of the embedded equipment to the untrustworthy third party debugging machine is solved.

After trust, each time the embedded device communicates with the trusted third party debugging machine, a password negotiation process is performed, the negotiated password is a symmetric password, the embedded device is encrypted by using the symmetric password, and the third party debugging machine is decrypted by using the symmetric password, which can specifically refer to the HTTPS communication process introduced in the following website: http:// www.cnblogs.com/ttltry-air/archive/2012/08/20/2647898. html.

On the basis of establishing trust, for encrypted communication (such as an HTTPS protocol), the present application also implements plaintext parsing of encrypted network communication data, and the specific process is similar to the above steps 501 to 509, except that:

after the step 502 and before the step 503, the embedded device encrypts the generated network request message by using the negotiated symmetric password to obtain an encrypted network request message;

the above step 503 is replaced by: and the embedded equipment sends the encrypted network request message to a network server through a router.

In the above step 507, the third party debugging machine receives the encrypted network request message sent by the embedded device through the router, and after the above step 507 and before the step 508, the third party debugging machine further decrypts the received encrypted network request message by using the negotiated symmetric password to obtain the decrypted network request message;

the above step 508 is replaced by: and the third party debugging machine analyzes the decrypted network request message to obtain network request data.

In addition, the third party debugging machine serves as a man-in-the-middle to forward the network request message of the embedded device to the network server, and after the network server returns the network response message, because the third party debugging machine is a network request initiator, the third party debugging machine can naturally decrypt the received network response message in a ciphertext form to obtain network response plaintext data.

The encrypted request and response data are all analyzed by a third party debugging machine in clear text.

In addition, the embodiment of the application can achieve the best implementation effect in the following hardware and software configurations:

hardware: RouterBOARD (MikroTik routing motherboard developed based on RouterOS) or other hardware platforms carrying RouterOS systems;

software: js, which is adept at handling I/O-intensive concurrent requests.

In the scheme of the embodiment of the application, the original process of setting parameters in the embedded device is moved to the router for setting through the NAT rule conversion function, the unaware network communication parameter setting is completed, the setting requirement of the embedded device is minimized, and almost all networking embedded systems can be supported.

Furthermore, the debugging port is arranged on the third-party debugging machine and the corresponding process is started, so that the third-party debugging machine can distinguish a plurality of embedded devices, and the plurality of embedded devices can be simultaneously debugged.

In addition, the function that the router runs on a network layer is combined, so that the network communication process of the embedded equipment is effectively controlled; and the application layer protocol configurable function of the third-party debugging machine is combined, the extension type of various protocol supports in the application layer is improved, and the support of the application layer protocol adopted by the received network request message is better.

Finally, when the network request message is processed, the service logic is expanded in a middleware mode, and the convenient and flexible deep control of network communication is realized.

Based on the same inventive concept, the embodiment of the present application further provides three apparatuses for debugging a network communication process of an embedded device, where a schematic structural diagram of the apparatus for debugging a network communication process of an embedded device is shown in fig. 8, and the apparatus includes: a receiving unit 81, a converting unit 82, and a transmitting unit 83; wherein:

a receiving unit 81, configured to receive a network request message sent by an embedded device, where a source address of the network request message is an IP address of the embedded device, and a destination address of the network request message is an IP address of a network server, and the network request message is used to request the network server to provide a network service;

a conversion unit 82, configured to convert a destination address and a source address of the network request packet into an IP address of a third party debugging machine and an IP address of the router, respectively;

the sending unit 83 is configured to send the network request message with the source address and the destination address converted to the third-party debugging machine, so that the third-party debugging machine displays the network request data in the network request message.

Preferably, the apparatus further comprises:

a judging unit 84, configured to judge whether a source address of a network request packet belongs to an address white list of an embedded device to be debugged after the receiving unit receives the network request packet sent by the embedded device and before the sending unit sends the network request packet with the source address and the destination address converted to a third-party debugging machine, and trigger the sending unit if the source address of the network request packet belongs to the address white list of the embedded device to be debugged;

the sending unit 83 is specifically configured to send the network request message with the source address and the destination address converted to the third party debugging machine.

Preferably, the apparatus further comprises:

a first determining unit 85, configured to determine, after the receiving unit receives the network request packet sent by the embedded device, a port number of a debugging port allocated to the embedded device by a third-party debugging machine before the sending unit sends the network request packet with the source address and the destination address converted to the third-party debugging machine, where the third-party debugging machine allocates different debugging ports to different embedded devices;

the conversion unit 82 is further configured to carry a debugging port number in the network request message;

the sending unit 83 is specifically configured to send a network request packet with a source address and a destination address converted and a debugging port number carried therein.

Preferably, the apparatus further comprises:

a second determining unit 86, configured to determine, after the receiving unit receives the network request packet sent by the embedded device, an application layer protocol used by the network request packet before the first determining unit determines the port number of the debug port allocated by the third-party debug machine to the embedded device;

the first determining unit 85 specifically determines a debugging port number allocated by a third-party debugging machine to the embedded device when the network request packet is sent by using the determined application layer protocol, where the third-party debugging machine allocates different debugging ports to the same embedded device when different application layer protocols are used for sending the network request packet.

Preferably, the apparatus further comprises:

the third determining unit 87 is configured to obtain the IP address of the third party debugging machine and the white list of the addresses of the embedded devices to be debugged in the following manner: receiving a destination address adjusting instruction sent by a third party debugging machine, wherein the destination address adjusting instruction comprises an IP address of the third party debugging machine and an IP address of the embedded equipment; and respectively taking the IP address of the third party debugging machine and the IP address of the embedded equipment contained in the destination address adjusting instruction as the IP address of the third party debugging machine for address conversion and the address white list of the embedded equipment to be debugged.

Preferably, the receiving unit 81 is further configured to receive a network request message sent by a third party debugging machine;

the sending unit 83 is further configured to send the received network request message sent by the third party debugging machine to the network server at a preconfigured network transmission rate.

A schematic structural diagram of a second apparatus for debugging a network communication process of an embedded device provided in an embodiment of the present application is shown in fig. 9, and includes: a determining unit 91, a message generating unit 92 and a sending unit 93; wherein:

a determining unit 91 configured to determine an IP address of the network server;

a message generating unit 92, configured to generate a network request message by using the IP address of the network server determined by the determining unit as a destination address and using the IP address of the embedded device as a source address, where the network request message is used to request the network server to provide a network service;

and a sending unit 93, configured to send the generated network request packet to a network server through a router, where the router converts a source address and a destination address of the network request packet and sends the converted network request packet to a third-party debugging machine.

Preferably, the apparatus further comprises:

a scanning unit 94, configured to scan a two-dimensional code displayed on the third-party debugging machine before the sending unit sends the generated network request packet to a network server through a router, where content of the two-dimensional code is a Web service address that is specially used for binding the embedded device and the third-party debugging machine;

the sending unit 93 is further configured to send an access request message for accessing the Web service address to the third party debugging machine, so that the third party debugging machine takes a source address in the access request message as an IP address of the embedded device included in the destination address adjustment instruction sent to the router.

Preferably, the sending unit 93 is further configured to send a binding request message to the third-party debugging machine before sending the generated network request message to the network server through the router, so that the third-party debugging machine allocates a debugging port to the embedded device, and binds the port number of the debugging port and the IP address of the embedded device;

the device further comprises:

a receiving unit 95, configured to receive a binding response message sent by the third party debugging machine, where the binding response message includes a binding result.

Preferably, the sending unit 93 is further configured to send a download request message to a trusted third party debugging machine before sending the generated network request message to a network server through a router;

the device further comprises: a download unit 96, an installation unit 97, a reception unit 95, and an identification unit 98;

a downloading unit 96, configured to download the root certificate using a downloading service provided by the trusted third party debugging machine;

the installation unit 97 is configured to install the downloaded root certificate;

the sending unit 93 is further configured to send an encryption request packet to a third party debugging tester through a router, where a header of the encryption request packet includes a domain name;

the receiving unit 95 is configured to receive an encrypted response packet sent by a third party debugging machine, where the encrypted response packet carries a domain name certificate, and the domain name certificate is a certificate issued by the third party debugging machine for the domain name by using a root certificate;

the identification unit 98 is configured to identify the domain name certificate by using the root certificate installed by the installation unit, and when the domain name certificate is identified, use the third party debugging machine that sends the encrypted response packet as a trusted third party debugging machine.

A schematic structural diagram of a third apparatus for debugging a network communication process of an embedded device provided in the embodiment of the present application is shown in fig. 10, and includes: a receiving unit 101, an analyzing unit 102, and a display unit 103; wherein:

a receiving unit 101, configured to receive a network request message sent by an embedded device through a router, where a source address of the network request message is an IP address of the router, and a destination address of the network request message is an IP address of a third-party debugging machine, and the network request message is used to request a network server to provide a network service;

the analyzing unit 102 is configured to analyze the received network request packet to obtain network request data;

a display unit 103, configured to display the network request data.

Preferably, the apparatus further comprises: a sending unit 104, configured to send a destination address adjustment instruction to a router before a receiving unit receives a network request packet sent by an embedded device through the router, where the destination address adjustment instruction includes an IP address of a third-party debugging machine and an IP address of the embedded device, and is used to instruct the router to modify a destination address of the network request packet received from the embedded device into an IP address of the third-party debugging machine.

Preferably, the apparatus further comprises: a first determining unit 105, configured to obtain an IP address of the embedded device by any one of: the first method is as follows: receiving an IP address of the embedded equipment input by a user; the second method comprises the following steps: receiving an access request message of embedded equipment, wherein the access request message is sent by the embedded equipment after scanning a two-dimensional code displayed on the third-party debugging machine, and the content of the two-dimensional code is a Web service address specially used for binding the embedded equipment and the third-party debugging machine; and taking the source address in the received access request message as the IP address of the embedded device.

Preferably, the receiving unit 101 is further configured to receive a binding request message sent by an embedded device before receiving a network request message sent by the embedded device through a router;

the device further comprises: an allocation unit 106, a binding unit 107, a sending unit 104 and a searching unit 108;

the distribution unit 106 is configured to distribute a debugging port for the embedded device;

the binding unit 107 is configured to bind the port number of the allocated debug port and the IP address of the embedded device;

the sending unit 104 is configured to send a binding response message to the embedded device, where the binding response message includes a binding result;

the searching unit 108 is configured to, after the receiving unit receives the network request message sent by the embedded device through the router and before the display unit displays the network request data, search, by using the binding relationship between the port number stored in the binding unit and the IP address of the embedded device, the IP address of the embedded device bound by the debugging port number included in the received network request message;

the display unit 103 is specifically configured to correspondingly display the network request data and the found IP address of the embedded device.

Preferably, the binding request message further includes an application layer protocol supported by the embedded device;

the allocating unit 106 is specifically configured to allocate different debugging ports to different application layer protocols supported by the embedded device;

the binding unit 107 is specifically configured to bind and store the port number of the allocated debug port, the IP address of the embedded device, and the application layer protocol.

Preferably, the receiving unit 101 is further configured to receive a download request message sent by the embedded device;

the device further comprises: a service providing unit 109, an issuing unit 110, and a transmitting unit 104;

a service providing unit 109, configured to provide a download service of a root certificate for the embedded device;

the receiving unit 101 is further configured to receive an encryption request packet sent by the embedded device, where a header of the encryption request packet includes a domain name;

an issuing unit 110, configured to issue a corresponding domain name certificate for the domain name by using the root certificate;

a sending unit 104, configured to send an encryption response to the third party debugging machine, where the encryption response carries a domain name certificate;

the receiving unit 101 is specifically configured to receive an encrypted network request packet sent by an embedded device through a router.

Preferably, the apparatus further comprises:

the sending unit 104 is configured to send a network request message to a network server after the receiving unit receives the network request message sent by the embedded device through the router;

the receiving unit 101 is further configured to receive a network response packet sent by the network server;

the analyzing unit 102 is further configured to analyze the network response packet to obtain network response data;

the display unit 103 is further configured to display the network response data.

Preferably, the apparatus further comprises: a second determination unit 111, a selection unit 112, a simulation unit 113, and a transmission unit 104;

the second determining unit 111 is configured to determine, after the receiving unit receives the network request packet sent by the embedded device through the router, an application layer protocol used by the received network request packet;

the selecting unit 112 is configured to select an application layer protocol matching the determined application layer protocol from the configured application layer protocols;

the simulation unit 113 is configured to simulate, by using the selected application layer protocol, a network server to generate a network response packet for the embedded device;

the sending unit 104 is configured to send the generated network response packet to the embedded device through a router;

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for debugging a network communication process of an embedded device is characterized by comprising the following steps:

2. The method of claim 1, wherein after receiving the network request message sent by the embedded device, the router sends the network request message with the source address and the destination address converted to the third party debugging machine, and the method further comprises: judging whether the source address of the network request message belongs to an address white list of the embedded equipment to be debugged;

sending the network request message with the source address and the destination address converted to a third party debugging machine, which specifically comprises the following steps:

and if the source address of the network request message belongs to the address white list of the embedded equipment to be debugged, sending the network request message with the source address and the destination address converted to a third-party debugging machine.

3. The method according to claim 1 or 2, wherein before the router transmits the network request message with the source address and the destination address converted after receiving the network request message transmitted by the embedded device, the method further comprises:

determining a port number of a debugging port allocated to the embedded equipment by a third-party debugging machine, wherein the third-party debugging machine allocates different debugging ports to different embedded equipment;

carrying a debugging port number in the network request message;

transmitting a network request message in which a source address and a destination address are converted, the method comprising:

and sending a network request message which converts the source address and the destination address and carries the debugging port number.

4. The method of claim 3, wherein after the router receives the network request message sent by the embedded device, before determining the port number of the debug port allocated to the embedded device by the third-party debug machine, the method further comprises:

determining an application layer protocol used by the network request message;

determining a port number of a debugging port allocated to the embedded device by a third-party debugging machine, including:

5. The method of claim 2, wherein the IP address of the third party debugging machine and the white list of the addresses of the embedded devices to be debugged are obtained by:

receiving a destination address adjusting instruction sent by a third party debugging machine, wherein the destination address adjusting instruction comprises an IP address of the third party debugging machine and an IP address of the embedded equipment;

and respectively taking the IP address of the third party debugging machine and the IP address of the embedded equipment contained in the destination address adjusting instruction as the IP address of the third party debugging machine for address conversion and the address white list of the embedded equipment to be debugged.

6. The method of claim 1, wherein the method further comprises:

receiving a network request message sent by a third party debugging machine;

and sending the received network request message sent by the third-party debugging machine to a network server at a pre-configured network transmission rate.

7. A method for debugging a network communication process of an embedded device is characterized by comprising the following steps:

the embedded equipment determines the IP address of the network server;

8. The method of claim 7, wherein before sending the generated network request message to a network server through a router, the method further comprises:

scanning a two-dimensional code displayed on the third-party debugging machine, wherein the content of the two-dimensional code is a Web service address specially used for binding the embedded equipment and the third-party debugging machine;

and sending an access request message to the third-party debugging machine, wherein the access request message is used for accessing the Web service address, so that the third-party debugging machine takes the source address of the access request message as the IP address of the embedded equipment contained in the destination address adjusting instruction sent to the router.

9. The method of claim 7, wherein before sending the generated network request message to a network server through a router, the method further comprises:

sending a binding request message to the third-party debugging machine so that the third-party debugging machine allocates a debugging port for the embedded equipment and binds the port number of the debugging port with the IP address of the embedded equipment;

and receiving a binding response message sent by the third party debugging machine, wherein the binding response message contains a binding result.

10. The method of claim 9, wherein the binding request message further includes an application layer protocol supported by the embedded device, so that a third party debugging machine allocates different debugging ports for different application layer protocols supported by the embedded device and binds port numbers of the debugging ports and the IP address and the application layer protocol of the embedded device.

11. The method of claim 7, wherein before sending the generated network request message to a network server through a router, the method further comprises:

sending a downloading request message to a trusted third party debugging machine;

downloading the root certificate using a download service provided by the trusted third party debugging machine;

installing the downloaded root certificate;

sending an encryption request message to a third party debugging tester through a router, wherein the header of the encryption request message contains a domain name;

receiving an encrypted response message sent by a third party debugging tester, wherein the encrypted response message carries a domain name certificate, and the domain name certificate is a certificate issued by the third party debugging tester for the domain name by using a root certificate;

identifying the domain name certificate using the installed root certificate;

and when the domain name certificate is identified, the third party debugging machine which sends the encrypted response message is used as a trusted third party debugging machine.

12. A method for debugging a network communication process of an embedded device is characterized by comprising the following steps:

analyzing the received network request message to obtain network request data;

and displaying the network request data.

13. The method of claim 12, wherein before the third party debugging machine receives the network request message sent by the embedded device through the router, the method further comprises:

and sending a destination address adjusting instruction to the router, wherein the destination address adjusting instruction comprises the IP address of the third party debugging machine and the IP address of the embedded equipment and is used for indicating the router to modify the destination address of the received network request message from the embedded equipment into the IP address of the third party debugging machine.

14. The method of claim 13, wherein the third party debug machine determines the IP address of the embedded device by any of:

the first method is as follows:

receiving an IP address of the embedded equipment input by a user;

taking the IP address of the embedded equipment input by the user as the IP address of the embedded equipment contained in the destination address adjusting instruction;

the second method comprises the following steps:

receiving an access request message sent by embedded equipment, wherein the access request message is sent by the embedded equipment after scanning a two-dimensional code displayed on the third-party debugging machine, and the content of the two-dimensional code is a Web service address specially used for binding the embedded equipment and the third-party debugging machine;

and taking the source address in the received access request message as the IP address of the embedded equipment contained in the destination address adjusting instruction.

15. The method of claim 12, wherein the network request message includes a debug port number, and before the third party debug machine receives the network request message sent by the embedded device through the router, the method further comprises:

receiving a binding request message sent by the embedded equipment;

distributing a debugging port for the embedded equipment;

binding and storing the port number of the distributed debugging port and the IP address of the embedded equipment;

sending a binding response message to the embedded equipment, wherein the binding response message contains a binding result;

after receiving a network request message sent by an embedded device through a router and before displaying the network request data, the method further comprises:

searching the IP address of the embedded equipment bound by the debugging port number contained in the received network request message by using the binding relation between the stored port number and the IP address of the embedded equipment;

displaying the network request data, including:

and correspondingly displaying the network request data and the searched IP address of the embedded equipment.

16. The method of claim 15, wherein the binding request message further includes an application layer protocol supported by the embedded device;

allocating a debug port for the embedded device, comprising:

allocating different debugging ports for different application layer protocols supported by the embedded equipment;

binding and storing the port number of the allocated debugging port and the IP address of the embedded device, wherein the binding and storing comprises the following steps:

and binding the port number of the distributed debugging port, the IP address of the embedded equipment and an application layer protocol.

17. The method of claim 12, wherein the method further comprises:

receiving a downloading request message sent by embedded equipment;

providing a download service of a root certificate for the embedded device;

receiving an encryption request message sent by the embedded equipment, wherein the header of the encryption request message comprises a domain name;

issuing a corresponding domain name certificate for the domain name by using the root certificate;

and sending an encrypted response message to the embedded equipment, wherein the encrypted response message carries the domain name certificate.

18. The method of claim 12, wherein after the third party debugging machine receives the network request message sent by the embedded device through the router, the method further comprises:

sending the network request message to a network server;

receiving a network response message sent by the network server;

analyzing the network response message to obtain network response data;

and displaying the network response data.

19. The method of claim 12, wherein after the third party debugging machine receives the network request message sent by the embedded device through the router, the method further comprises:

determining an application layer protocol used by a received network request message;

selecting an application layer protocol matched with the determined application layer protocol from the configured application layer protocols;

simulating a network server to generate a network response message for the embedded equipment by using the selected application layer protocol;

sending the generated network response message to the embedded equipment through a router;

analyzing the generated network response message to obtain network response data;

and displaying the network response data.

20. An apparatus for debugging a network communication process of an embedded device, applied to a router, includes:

21. The apparatus of claim 20, wherein the apparatus further comprises:

the judging unit is used for judging whether the source address of the network request message belongs to an address white list of the embedded equipment to be debugged or not after the receiving unit receives the network request message sent by the embedded equipment and before the sending unit sends the network request message with the source address and the destination address converted to the third-party debugging machine, and triggering the sending unit if the source address of the network request message belongs to the address white list of the embedded equipment to be debugged;

the sending unit is specifically configured to send the network request message with the source address and the destination address converted to the third party debugging machine.

22. The apparatus of claim 20 or 21, wherein the apparatus further comprises:

the first determining unit is used for determining the port number of a debugging port allocated to the embedded equipment by a third-party debugging machine before the transmitting unit transmits the network request message with the source address and the destination address converted to the third-party debugging machine after the receiving unit receives the network request message transmitted by the embedded equipment, wherein the third-party debugging machine allocates different debugging ports to different embedded equipment;

the conversion unit is further configured to carry a debugging port number in the network request message;

the sending unit is specifically configured to send a network request packet with a source address and a destination address converted and a debug port number carried therein.

23. The apparatus of claim 22, wherein the apparatus further comprises:

the second determining unit is used for determining an application layer protocol used by the network request message before the first determining unit determines the port number of the debugging port distributed by the third-party debugging machine for the embedded equipment after the receiving unit receives the network request message sent by the embedded equipment;

the first determining unit specifically determines a debugging port number allocated by a third-party debugging machine to the embedded device when the network request message is sent by using the determined application layer protocol, wherein the third-party debugging machine allocates different debugging ports to the same embedded device when different application layer protocols are used for sending the network request message.

24. The apparatus of claim 21, wherein the apparatus further comprises:

the third determining unit is used for obtaining the IP address of the third-party debugging machine and the address white list of the embedded equipment to be debugged in the following modes: receiving a destination address adjusting instruction sent by a third party debugging machine, wherein the destination address adjusting instruction comprises an IP address of the third party debugging machine and an IP address of the embedded equipment; and respectively taking the IP address of the third party debugging machine and the IP address of the embedded equipment contained in the destination address adjusting instruction as the IP address of the third party debugging machine for address conversion and the address white list of the embedded equipment to be debugged.

25. The apparatus of claim 20, wherein the receiving unit is further configured to receive a network request message sent by a third party debugging machine;

the sending unit is further configured to send the received network request message sent by the third-party debugging machine to the network server at a preconfigured network transmission rate.

26. The device for debugging the network communication process of the embedded equipment is characterized by being applied to the embedded equipment and comprising the following steps:

a determining unit for determining an IP address of the network server;

27. The apparatus of claim 26, wherein the apparatus further comprises:

the scanning unit is used for scanning a two-dimensional code displayed on the third-party debugging machine before the sending unit sends the generated network request message to a network server through a router, and the content of the two-dimensional code is a Web service address which is specially used for binding the embedded equipment and the third-party debugging machine;

the sending unit is further configured to send an access request message for accessing the Web service address to the third-party debugging machine, so that the third-party debugging machine takes a source address in the access request message as an IP address of the embedded device included in the destination address adjustment instruction sent to the router.

28. The apparatus of claim 26, wherein the sending unit is further configured to send a binding request message to the third party debugging machine before sending the generated network request message to a network server through a router, so that the third party debugging machine allocates a debugging port for the embedded device and binds a port number of the debugging port with an IP address of the embedded device;

the device further comprises:

and the receiving unit is used for receiving a binding response message sent by the third-party debugging machine, wherein the binding response message contains a binding result.

29. The apparatus of claim 26, wherein the sending unit is further configured to send a download request message to a trusted third party debugging machine before sending the generated network request message to a network server through a router;

the device further comprises: the device comprises a downloading unit, an installing unit, a receiving unit and an identifying unit;

a downloading unit for downloading the root certificate using a downloading service provided by the trusted third party debugging machine;

the installation unit is used for installing the downloaded root certificate;

the sending unit is further configured to send an encryption request message to a third party debugging machine through a router, where a header of the encryption request message includes a domain name;

the receiving unit is used for receiving an encrypted response message sent by a third party debugging machine, wherein the encrypted response message carries a domain name certificate, and the domain name certificate is a certificate issued by the third party debugging machine for signing the domain name by using a root certificate;

and the identification unit is used for identifying the domain name certificate by using the root certificate installed by the installation unit, and taking the third party debugging machine which sends the encrypted response message as a trusted third party debugging machine when identifying the domain name certificate.

30. The utility model provides a device of network communication process of debugging embedded equipment which characterized in that is applied to the machine of third party debugging, includes:

and the display unit is used for displaying the network request data.

31. The apparatus of claim 30, wherein the apparatus further comprises: the sending unit is used for sending a destination address adjusting instruction to the router before the receiving unit receives a network request message sent by the embedded device through the router, wherein the destination address adjusting instruction comprises an IP address of a third-party debugging machine and an IP address of the embedded device and is used for indicating the router to modify the destination address of the received network request message from the embedded device into the IP address of the third-party debugging machine.

32. The apparatus of claim 31, wherein the apparatus further comprises: a first determining unit, configured to obtain an IP address of the embedded device by any one of the following methods: the first method is as follows: receiving an IP address of the embedded equipment input by a user; the second method comprises the following steps: receiving an access request message of embedded equipment, wherein the access request message is sent by the embedded equipment after scanning a two-dimensional code displayed on the third-party debugging machine, and the content of the two-dimensional code is a Web service address specially used for binding the embedded equipment and the third-party debugging machine; and taking the source address in the received access request message as the IP address of the embedded equipment contained in the destination address adjusting instruction.

33. The apparatus of claim 30, wherein the receiving unit is further configured to receive a binding request packet sent by an embedded device before receiving a network request packet sent by the embedded device through a router;

the device further comprises: the device comprises a distribution unit, a binding unit, a sending unit and a searching unit;

the distribution unit is used for distributing debugging ports for the embedded equipment;

the binding unit is used for binding and storing the port number of the distributed debugging port and the IP address of the embedded equipment;

the sending unit is used for sending a binding response message to the embedded equipment, and the binding response message contains a binding result;

the searching unit is used for searching the IP address of the embedded device bound by the debugging port number contained in the received network request message by utilizing the binding relation between the port number stored by the binding unit and the IP address of the embedded device before the display unit displays the network request data after the receiving unit receives the network request message sent by the embedded device through the router;

the display unit is specifically configured to correspondingly display the network request data and the found IP address of the embedded device.

34. The apparatus of claim 33, wherein the binding request message further includes an application layer protocol supported by the embedded device;

the distribution unit is specifically configured to distribute different debugging ports to different application layer protocols supported by the embedded device;

the binding unit is specifically configured to bind and store the allocated port number of the debug port, the IP address of the embedded device, and the application layer protocol.

35. The apparatus according to claim 30, wherein the receiving unit is further configured to receive a download request message sent by the embedded device;

the device further comprises: the system comprises a service providing unit, an issuing unit and a sending unit;

the service providing unit is used for providing a downloading service of the root certificate for the embedded equipment;

the receiving unit is further configured to receive an encryption request packet sent by the embedded device, where a header of the encryption request packet includes a domain name;

the issuing unit is used for issuing a corresponding domain name certificate for the domain name by using the root certificate;

a sending unit, configured to send an encrypted response packet to the embedded device, where the encrypted response packet carries a domain name certificate;

the receiving unit is specifically configured to receive an encrypted network request packet sent by the embedded device through the router.

36. The apparatus of claim 30, wherein the apparatus further comprises:

the sending unit is used for sending the network request message to the network server after the receiving unit receives the network request message sent by the embedded equipment through the router;

the receiving unit is further configured to receive a network response packet sent by the network server;

the analysis unit is further configured to analyze the network response packet to obtain network response data;

the display unit is further configured to display the network response data.

37. The apparatus of claim 30, wherein the apparatus further comprises: the device comprises a second determining unit, a selecting unit, a simulating unit and a sending unit;

the second determining unit is used for determining an application layer protocol used by the received network request message after the receiving unit receives the network request message sent by the embedded device through the router;

the selection unit is used for selecting an application layer protocol matched with the determined application layer protocol from the configured application layer protocols;

the simulation unit is used for simulating a network server to generate a network response message for the embedded equipment by using the selected application layer protocol;

the sending unit is configured to send the generated network response packet to the embedded device through a router;

the display unit is further configured to display the network response data.