CN113535525A

CN113535525A - Tracking message transmission method, electronic device and storage medium

Info

Publication number: CN113535525A
Application number: CN202010297254.XA
Authority: CN
Inventors: 刘君
Original assignee: Zeku Technology Beijing Corp Ltd
Current assignee: Zeku Technology Beijing Corp Ltd
Priority date: 2020-04-15
Filing date: 2020-04-15
Publication date: 2021-10-22

Abstract

The application discloses a transmission method of a trace message, electronic equipment and a storage medium. The method for sending the tracking message comprises the following steps: sending a tracking message generated by a target system to a receiving end through a first output interface of at least two output interfaces; wherein the first output interface is in a first state; when the first output interface is changed from a first state to a second state, sending a tracking message generated by the target system to the receiving end through the first output interface and a second output interface of the at least two output interfaces; wherein the first state represents that the output interface is not blocked; the second state is indicative of an output interface being blocked.

Description

Tracking message transmission method, electronic device and storage medium

Technical Field

The present application relates to the field of embedded systems, and in particular, to a method for transmitting a trace message, an electronic device, and a storage medium.

Background

The tracing technology is a common analyzing and debugging means in the embedded system, and can also be used for optimizing the system. The tester outputs the Trace message through a Trace output interface, and the debugging and testing System (DTS, Debug Test System) receives the Trace message at the corresponding input interface, thereby generating a Log (Log). Development engineers use specialized tools to analyze logs to discover and solve problems, and can also optimize the system.

Due to the rate limitation of the output interface, the requirement of ultra-high speed tracing cannot be effectively met, especially for ultra-high speed systems such as the fifth generation mobile communication technology (5G).

Disclosure of Invention

The embodiment of the invention provides a transmission method of a trace message, electronic equipment and a storage medium, which are used for at least solving the problem that an output interface in the related technology cannot meet the requirement of ultra-high-speed trace.

The technical scheme of the embodiment of the application is realized as follows:

in one aspect, an embodiment of the present application provides a method for sending a trace message, where the method includes:

sending a tracking message generated by a target system to a receiving end through a first output interface of at least two output interfaces; wherein the first output interface is in a first state;

when the first output interface is changed from a first state to a second state, sending a tracking message generated by the target system to the receiving end through the first output interface and a second output interface of the at least two output interfaces; wherein the content of the first and second substances,

the first state represents that the output interface is not blocked; the second state is indicative of an output interface being blocked.

On the other hand, an embodiment of the present application provides a method for receiving a trace message, where the method includes:

receiving a trace message through at least two input interfaces in one-to-one correspondence with at least two output interfaces of a target system; each tracking message is generated by the target system and is sent by the sending end through one of the at least two output interfaces;

and combining the tracking messages received by all the at least two input interfaces to obtain a log file about the target system.

In another aspect, an embodiment of the present application provides an electronic device, including:

the first sending unit is used for sending the tracking message generated by the target system to the receiving end through a first output interface of the at least two output interfaces; wherein the first output interface is in a first state;

a second sending unit, configured to send, to the receiving end, a trace message generated by the target system through the first output interface and a second output interface of the at least two output interfaces when the first output interface changes from a first state to a second state; wherein the content of the first and second substances,

a receiving unit, configured to receive a trace message through at least two input interfaces in one-to-one correspondence with at least two output interfaces of a target system; each tracking message is generated by the target system and is sent by the sending end through one of the at least two output interfaces;

and the merging unit is used for merging the tracking messages received by all the input interfaces in the at least two input interfaces to obtain a log file related to the target system.

In another aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory for storing a computer program operable on the processor, wherein the processor is configured to execute the above-mentioned trace message transmission method when the computer program is executed.

In another aspect, an embodiment of the present application provides a storage medium, on which a computer program is stored, where the computer program is executed by a processor to execute the above method for transmitting a trace message.

In the embodiment of the application, when the first output interface is not blocked, the trace message generated by the target system is sent to the receiving end through the first output interface. And under the condition that the first output interface is blocked, the tracking message generated by the target system is sent to the receiving end through the first output interface and the second output interface, more than two output interfaces in the system can be fully utilized, the automatic adaptation of the output interfaces is realized, the bandwidth tracked by the system can be effectively improved under the condition that the system does not have an ultra-high-speed output interface, the requirement on the system is reduced, the flexibility tracked by the system is improved, and the effect of avoiding the overflow of the tracking message is effectively achieved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

fig. 1 is a schematic architecture diagram of a tracking system provided in the related art;

fig. 2 is a flowchart illustrating a method for sending a trace message according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a method for receiving a trace message according to an embodiment of the present disclosure;

fig. 4 is a schematic flowchart of generating a log file according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a tracking system according to an embodiment of the present application;

fig. 6 is a schematic structural component diagram of an electronic device according to an embodiment of the present disclosure;

fig. 7 is a schematic structural component diagram of another electronic device provided in the embodiment of the present application;

fig. 8 is a schematic diagram of a hardware component structure of an electronic device according to an embodiment of the present application.

Detailed Description

The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description will be made of related technologies related to the embodiments of the present application.

Debug (Debug) refers to detecting, tracing, and eliminating software errors. Debugging is also used for performance testing and system level hardware debugging of embedded processor systems.

Trace (Trace) is an analysis and debugging tool, also known as Trace technology. It makes the activity of the processor or system visible externally in real time, or stores and retrieves the system activity for the application developer to view through the relevant program or external device.

The Mobile Industry Processor Interface (MIPI) alliance defines a Target System (TS) and a Debug and Test System (DTS).

TS refers to the system being debugged. TS may be a discrete device, such as a chip, or an aggregate of multiple discrete devices on a substrate or a group of substrates. The TS may also contain 0 to N independent debug and test targets.

DTS refers to a hardware and software combination system that provides debug visibility and control for system developers when connecting to TS. The system comprises:

a host computer: a workstation or other processing system runs debug or test software, and controls the debug and test controller.

A debugger: debug software, part of a debug and test system. It interacts with the debug and test controllers and provides a user interface for operating the debug and test controllers (e.g., controlling single steps, setting breakpoints, memory display/modification, trace reconstruction, etc.).

Fig. 1 is an architecture diagram of a tracking system provided in the related art, and as shown in fig. 1, a flow of sending a generated tracking message to a DTS by a TS in the related art includes:

tracing the source to the trace module: there are multiple Trace sources on the TS, each of which sends the generated Trace message to the Trace module, and the Trace module packages the Trace message, for example, the Trace module generates an STP Trace data stream based on a System Trace Protocol (STP).

Tracking module to selecting module: the Trace module sends an STP Trace data stream to the selection module.

Selecting a module to output interface: the selection module selects one output interface from output interfaces owned by the TS system based on different test scenes, and is used for sending an STP Trace data stream to the DTS, and the STP Trace data stream is used for generating a log file by the DTS. It should be noted that, in the related art, only one set output interface is used for transmission of one STP Trace data stream.

The process of generating the log file by the DTS according to the tracking message in the TS comprises the following steps:

input interface to multiplexing module: the DTS receives the STP Trace data stream through an input interface corresponding to an output interface for transmitting the STP Trace data stream, and transmits the STP Trace data stream to the multiplexing module. It should be noted that the input interface of the DTS corresponds to the input interface of the TS one by one.

Multiplexing module to log generation module: and the multiplexing module sends the STP Trace data stream received from a certain input interface to the log generation module for generating a log file. It should be appreciated that a development engineer may analyze the log file using specialized tools to discover and solve problems in the TS, and may also optimize the system.

In summary, in the related art, the TS can only output trace messages from one output interface to the DTS. Due to the rate limitation of a single interface, the requirement of ultra-high speed tracing, especially the ultra-high speed system such as 5G, cannot be effectively satisfied. Sending trace messages through only one output interface may result in trace messages being lost or some of the trace messages being restricted from being output.

Based on this, the following technical solutions of the embodiments of the present application are provided, where a first output interface of a TS is blocked, a trace message generated by a target system is sent to a receiving end through the first output interface and a second output interface, so that more than two output interfaces in the system can be fully utilized, automatic adaptation of the output interfaces is realized, and in the case that the system does not have an ultra-high speed output interface, the bandwidth of system tracking can be effectively improved, the requirement on the system is reduced, the flexibility of system tracking is improved, and the effect of avoiding overflow of the trace message is effectively achieved.

Next, the execution steps of the trace message transmission method are introduced, fig. 2 is a schematic flowchart of a method for sending a trace message according to an embodiment of the present application, and as shown in fig. 2, the flowchart includes the following steps:

step 201, a first output interface of at least two output interfaces is used for sending a tracking message generated by a target system to a receiving end; wherein the first output interface is in a first state.

Step 202, when the first output interface changes from the first state to the second state, sending a trace message generated by the target system to the receiving end through the first output interface and a second output interface of the at least two output interfaces; wherein the first state represents that the output interface is not blocked; the second state is indicative of an output interface being blocked.

The device carrier whose main execution body is the TS may be an electronic device such as a mobile terminal, a computer terminal, or a similar operation device, but is not limited thereto. For convenience of description, the execution body is hereinafter denoted by a transmitting end, which may be understood as a transmitting-end device.

It should be noted that, in this embodiment of the present application, the sending end includes at least two output interfaces, and these output interfaces may be used to output a trace message generated by the target system. According to the MIPI support for the output Interface and the input Interface, the output Interface may be a Universal Serial Bus (USB) Interface, or may also be a micro Secure Digital (micro SD) Interface, a High Definition Multimedia Interface (HDMI), a High speed Serial computer expansion Bus (PCIe) Interface, or a Digital display (DP, DisplayPort) Interface.

In step 201, in the case that the first output interface is not blocked (i.e. in the first state), the transmitting end transmits a trace message to the receiving end only through the first output interface.

It should be noted that the first output interface may be preset by the TS system, or may be set by a user. Preferably, the first output interface may be an output interface with the highest priority of output interfaces in the TS, and the priority may be defined according to different indexes, such as bandwidth of the interface, power consumption of the interface, or stability of the interface. In one embodiment, the first output interface is an output interface with a throughput rate meeting a set requirement.

It should also be noted that the first state represents that the output interface is not blocked. The definition that the output interface is not blocked can be set by the system or set by the user. For example, a state where the bandwidth usage of the output interface is less than 95% may be defined as no blocking of the output interface. It is more common to define a state where the bandwidth usage of the output interface is less than 100% as that the output interface is not blocked. In some possible embodiments, the case where the first output interface is not blocked may be a case where the bandwidth of the first output interface is sufficient to carry the entire trace message transmission requirement.

In step 202, when the first output interface changes from the non-blocking state (i.e., the first state) to the blocking state (i.e., the second state), the trace message generated by the TS is sent to the receiving end through the first output interface and the second output interface.

It should be appreciated that the purpose of performing step 202 is to address trace message overflow issues that may be faced when sending trace messages over a single output interface in the related art. When the sending end determines that the first output interface is blocked, the second output interface shares and transmits the tracking message which cannot be sent by the first output interface, so that the automatic adaptation of the output interface is realized, the system tracking bandwidth can be effectively improved under the condition that the system does not have a single ultra-high-speed output interface, the requirement on the system is reduced, and the effects of improving the system tracking flexibility and effectively avoiding the overflow of the tracking message are achieved.

In practical applications, when the target system is configured with at least three output interfaces, the second output interface has the highest priority among all the output interfaces in the first state.

Specifically, when the first output interface is in the blocked state, the second output interface is the output interface with the highest priority among all other output interfaces owned by the target system.

In step 202, it should be noted that, when the trace message generated by the target system is sent to the receiving end through the first output interface and the second output interface of the at least two output interfaces, the following procedure may be implemented:

when the target system generates a tracking message, determining a table item pointed by a first pointer in a set routing table;

and calling a sending function through a second pointer in the table entry pointed by the first pointer so as to enable a second output interface of the at least two output interfaces to send the tracking message generated by the target system to the receiving end.

Wherein, the first pointer is used for pointing to the corresponding table entry of the second output interface in the set routing table; each table entry in the set routing table corresponds to one of the at least two output interfaces, and at least a second pointer of the corresponding output interface is recorded; the second pointer is used for calling a sending function of the corresponding output interface.

The examples of the present application are further illustrated below with reference to table 1. Table 1 shows an example of setting a routing table provided in this embodiment of the present application, where the table entry includes an output interface, a state, a priority, a sending function pointer (i.e., a second pointer), and may further include a reserved entry, and the reserved entry may be set according to an application of the system.

The following describes the table entries in turn:

an output interface: representing any of all output interfaces supported by the system.

Priority: the priority of the corresponding output interface is indicated, and the sequence of the selected corresponding output interface can be indicated. The priority may be defined according to different criteria, such as the bandwidth of the interface, the power consumption of the interface or the stability of the interface. To enable fast traversal of the routing table, the table may be sorted according to an order of priority.

The state is as follows: representing the real-time status of the output interface. The selectable values of the state table entry need to be defined according to the specific situation of the system, including enable, close, block (i.e. the second state) and work (i.e. the first state). Preferably, the state is updated in time whenever the state of the interface changes.

Sending a function pointer: a transfer function pointer representing the output interface. Through the pointer, a sending function corresponding to the output interface can be called.

In some possible embodiments, the sender maintains a global working route pointer (i.e., a first pointer) through the routing module, where the pointer points to a route entry with the highest priority and whose status is working in the routing table. Whenever the routing module receives the trace message, it finds the corresponding sending function pointer (i.e. the second pointer) through this global working routing pointer, and then calls the function to send out the trace message.

TABLE 1

When the first output interface is blocked, the sending end determines the table entry pointed by the global working route pointer in the set route table.

Here, it should be understood that the blocking of the first output interface does not represent the first output interface stopping the sending of trace messages to the receiver. For example: when the routing module determines that the first output interface is in a blocking state, the routing module changes the trace message which is not allocated with the output interface into the trace message which is allocated with the second output interface to be sent, but the trace message which is allocated with the first output interface to be sent is still sent by the first output interface.

And the sending end calls a sending function through a second pointer in the table item pointed by the global working routing pointer and sends the tracking message generated by the target system to the receiving end through a second output interface.

It should be noted that, in the embodiment of the present application, one or more output interfaces are specifically selected to send the trace message, and the trace message is determined according to the states of the output interfaces. In practical application, the state of the output interface may change along with the working condition. Therefore, preferably, in some possible embodiments, the method for transmitting the trace message further includes:

monitoring whether each output interface of the at least two output interfaces is in the second state or not to obtain a monitoring result;

and updating the first pointer according to the monitoring result.

Specifically, the sending end monitors whether each output interface is in a blocking state or not to obtain a monitoring result, and updates the global working routing pointer according to the monitoring result. It should be appreciated that when an output interface is in a blocked state, the global working route pointer should avoid pointing to that output interface. It is readily appreciated that the global working route pointer will not point to an output interface whose state is off and enabled.

In practical application, the global working route pointer can be maintained by the output monitoring module in real time. The output monitoring module monitors the state of the output interfaces and, if any of the output interfaces changes state, updates the pointer accordingly. Preferably, the pointer is set to the routing table entry with the highest priority and the state is working (i.e., the first state).

For step 202, it should be further noted that, when the first output interface changes from the first state to the second state, the trace message that has not been assigned to the first output interface is instead sent through the second output interface, and the corresponding receiving end receives all the trace messages sent by the sending end through at least two input interfaces, so that the receiving end needs to combine the trace messages received by different input interfaces according to a set rule to generate a final log file. To facilitate the receiving end to merge the trace message, in some possible embodiments, the sending end may carry additional information to enable the receiving end to merge the trace message by:

the first method is as follows: and for each generated trace message, the sending end reads the current timestamp through the timestamp module and then adds the timestamp into each trace message.

Each trace message has a unique timestamp that is used to mark the time of generation of the corresponding trace message.

The second method comprises the following steps: generating an interface change message indicating the second output interface; and sending the interface change message through the first output interface, so that the receiving end combines the tracking messages sent by the at least two output interfaces according to the interface change message.

Specifically, when the first output interface changes from the first state to the second state, the transmitting end generates an interface change message indicating the corresponding second output interface. And the sending end sends the interface change message through the first output interface.

The examples of the present application are further illustrated below with reference to table 2. Table 2 shows a message format example of the interface change message provided in the embodiment of the present application.

TABLE 2

Output interface status

Time stamp

New output interface

In some possible embodiments, when the first output interface changes from the first state to the second state, the sending end stops configuring the trace message to the first output interface, and the first output interface needs to continue sending the configured trace message, and configures the interface change message to the first output interface, and inserts the interface change message at the end of the message queue currently configured by the first output interface. The entries in table 2 are introduced as follows:

and (3) outputting the interface state: indicating that this is a status packet for the output interface change.

Time stamping: timestamp information.

A new output interface: the newly selected output interface.

In addition, unlike the timestamp of the trace message, the timestamp information in the interface change message is the time when the interface change message was generated.

In practical applications, when the first output interface and the second output interface are used to send the trace message to the receiving end in the same direction, and the transmission rate required by the trace message cannot be carried, it is easy to think that the third output interface is continuously selected in the same way as the second output interface, so as to send the trace message to the receiving end together with the first output interface and the second output interface. If the transmission rate required by the trace message cannot be met, the fourth output interface is selected continuously, which is not described herein again. Here, whether one or more output interfaces satisfy the transmission rate of the trace message may be determined by monitoring the occupation status of the trace message buffer in the TS, or by monitoring the bandwidth occupation status of each output interface that is performing transmission, or by monitoring the difference between the total generation rate of the trace message and the total transmission bandwidth of one or more output interfaces that are performing transmission.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

Through the steps, the sending end solves the problem that the tracking message overflows or cannot be sent under the condition that the system does not have an ultra-high-speed output interface, improves the bandwidth of system tracking, reduces the requirement on the system, and achieves the effects of improving the flexibility of system tracking and effectively avoiding the overflow of the tracking message.

Fig. 3 is a schematic flowchart of a method for receiving a trace message according to an embodiment of the present application, where as shown in fig. 3, the flowchart includes the following steps:

step 301, receiving a trace message through at least two input interfaces corresponding to at least two output interfaces of a target system one to one; each trace message is generated by the target system and sent by the sender over one of the at least two output interfaces.

Step 302, merging the trace messages received by all the input interfaces of the at least two input interfaces to obtain a log file related to the target system.

The device carrier whose main execution body is DTS may be an electronic device such as a mobile terminal, a computer terminal, or a similar operation device, but is not limited thereto. For convenience of description, the following description refers to an execution body as a receiving end, which can be understood as a receiving end device.

It should be noted that, in this embodiment of the present application, the receiving end includes at least two input interfaces, and these input interfaces may be used to receive the trace message sent by the sending end. According to the support condition of the MIPI to the output interface and the input interface, the input interface can be a USB interface, a micro SD interface, an HDMI interface, a PCIe interface, a DP interface or the like.

In step 301, the receiving end receives a trace message on an input interface corresponding to an output interface of the target system. It should be noted that the receiving end can know which input interface has the trace message through polling or interrupt. It should be understood that, when the transmitting end transmits the trace message to the receiving end through at least two output interfaces, the receiving end receives the trace message through at least two input interfaces corresponding to at least two output interfaces of the target system one to one. Each received trace message is sent by the sender over one of the at least two output interfaces. Here, it is also possible for different sender-side interface configurations and output transmission cases to be sent by the third or fourth output interface.

Optionally, the receiving end generates a corresponding message set for each of the at least two input interfaces; the message set records the messages received by the corresponding input interfaces according to the receiving sequence; the received messages include at least trace messages.

Specifically, trace messages on each input interface may be generated as a separate data Stream (Stream) or stored in a separate log file. It should be appreciated that if the receiving end receives only one log file or Stream, then no merging is required. If the receiving end receives a plurality of Stream or Log files, the Stream or Log files are respectively corresponding to the output interfaces in the routing table of the receiving end, and the corresponding output interfaces can be found out according to the sequence numbers of the Steam or Log files.

In step 302, the receiving end merges the received data streams or logs to generate a final log file

It should be noted that, the receiving end merges the data stream or the log, and generates the log file by the following method:

the first method is as follows: and the receiving end writes all the received trace messages into the log file according to the time sequence based on the time stamps of the trace messages.

Specifically, the receiving end may analyze the timestamp of each received trace message, and merge the timestamps to generate a final log file according to the sequence.

The second method comprises the following steps: and merging the message sets corresponding to all the input interfaces in the at least two input interfaces to obtain the log file.

In some possible embodiments of the second method, in corresponding step 301, the received message at least includes a trace message, and the received message further includes an interface change message; the interface change message is generated by the sending end under the condition that the first output interface is changed from the first state to the second state, and is sent by the first output interface; the second output interface is indicated in the interface change message. The process of generating the final log file by the receiving end can be realized by the following steps:

sequentially reading messages in a first message set corresponding to a first input interface, and writing the read tracking messages into the log file according to a reading sequence; the first input interface corresponds to the first output interface.

And determining a second input interface corresponding to the second output interface when the interface change message is read from the first message set.

And sequentially reading the messages in the second message set corresponding to the second input interface, and writing the read tracking messages into the log file according to the reading sequence.

The embodiments of the present application are further illustrated below with reference to fig. 4. Fig. 4 is a schematic flowchart of generating a log file according to an embodiment of the present application. The process comprises the following steps:

a first set of messages, which may be Stream or log, corresponding to the first input interface is selected, and the read trace messages are written to a log file in read order. The first input interface corresponds to a first output interface of the transmitting end.

And reading the interface change message from the first message set, and determining a second input interface corresponding to the second output interface.

And confirming whether the last trace message in the second message set corresponding to the second input interface is the last trace message in all the trace messages sent by the sending end.

If so, ending the merging process and generating a final log file.

If not, determining the corresponding next input interface according to the next output interface indicated by the interface change message, repeating the process of reading the message set and writing the tracking message into the log file until the read tracking message is determined to be the last tracking message, and generating a final log file.

Through the steps, the receiving end solves the problem of how to combine the tracking messages received by a plurality of input interfaces, and can make full use of the tracking interfaces in the system, thereby improving the bandwidth tracked by the system

The embodiments of the present application are further described below with reference to fig. 5. Fig. 5 is a schematic architecture diagram of a tracking system provided in an embodiment of the present application.

It should be noted that the method embodiments provided in the embodiments of the present application may be executed in an electronic device such as a mobile terminal, a computer terminal, or a similar computing device. The embodiment of the present application can be executed on the tracking system architecture shown in fig. 5, as shown in fig. 5, the tracking system architecture includes: TS (i.e., the sending end electronics) and DTS (i.e., the receiving end electronics).

In the embodiment shown in fig. 5, the process of sending the generated trace message to the DTS by the TS includes:

tracing the source to the trace module: there are multiple Trace sources on the TS, each of which sends the generated Trace message to the Trace module, which packages the Trace message, e.g., the Trace module generates an STP Trace data stream based on SIP.

Tracking module to routing module: the Trace module sends an STP Trace data flow to the routing module.

Routing module to output interface: and the routing module selects at least one output interface from the output interfaces owned by the TS system based on the set routing table, and is used for sending an STP Trace data stream to the DTS, wherein the STP Trace data stream is used for generating a log file by the DTS. It should be noted that, in an embodiment, when the first output interface selected by the TS is in the blocking state, the routing module determines the second output interface, and the TS sends the STP Trace data stream to the DTS through the first output interface and the second output interface.

In some possible embodiments, the sender maintains a global working route pointer (i.e., a first pointer) through the routing module, where the pointer points to a routing table entry with the highest priority and whose status is working. Whenever the routing module receives the trace message, it finds the corresponding sending function pointer (i.e. the second pointer) through the global working routing pointer, and then calls the function to send out the trace message.

Optionally, the global working route pointer in the routing table is maintained by the output monitoring module in real time. The output monitoring module monitors the state of the output interfaces and, if any of the output interfaces changes state, updates the pointer accordingly. Preferably, the pointer is set to the routing table entry with the highest priority and the state is working (i.e., the first state).

Optionally, the TS reads a current timestamp from the timestamp module for each generated trace message, and adds the current timestamp to each trace message.

Optionally, in a case that the first output interface changes from the first state to the second state, the TS generates an interface change message indicating the second output interface; and sending the interface change message through the first output interface, so that the DTS combines the tracking messages sent by at least two output interfaces according to the interface change message.

input interface to merge module: the DTS receives the STP Trace data stream through at least one input interface corresponding to the output interface for transmitting the STP Trace data stream, and transmits the STP Trace data stream to the merging module. It should be noted that, when the TS sends the trace message to the DTS through at least two output interfaces, the DTS receives the trace message through at least two input interfaces corresponding to the at least two output interfaces of the TS one to one. Each trace message accepted is sent by the TS over the first or second output interface.

The merging module generates a log file: the merging module merges the data streams or the log files received from the plurality of input interfaces to generate the log file. It should be appreciated that a development engineer may analyze the log file using specialized tools to discover and solve problems in the TS, and may also optimize the system.

Alternatively, the process of generating the final log file by the DTS may be implemented by the following steps:

and sequentially reading the messages in the first message set corresponding to the first input interface corresponding to the first output interface, and writing the read tracking messages into the log file according to the reading sequence.

And under the condition that the interface change message is read from the first message set, determining a second input interface corresponding to the second output interface.

And repeating the process of reading the message set and writing the tracking message into the log file until the read tracking message is confirmed to be the last tracking message, and generating a final log file.

In order to implement the method for sending a trace message according to the embodiment of the present application, an embodiment of the present application further provides an electronic device, as shown in fig. 6, where the electronic device is used as a sending end of a trace message and is deployed with a TS, and the electronic device includes:

a first sending unit 601, configured to send a trace message generated by a target system to a receiving end through a first output interface of at least two output interfaces; wherein the first output interface is in a first state;

a second sending unit 602, configured to send, to the receiving end, a trace message generated by the target system through the first output interface and a second output interface of the at least two output interfaces when the first output interface changes from a first state to a second state; wherein the content of the first and second substances,

In one embodiment, the target system is configured with at least three output interfaces; the second output interface has a highest priority among all of the at least three output interfaces in the first state.

In an embodiment, when the second sending unit 602 sends the trace message generated by the target system to the receiving end through the first output interface and a second output interface of the at least two output interfaces, it is configured to:

calling a sending function through a second pointer in the table entry pointed by the first pointer so that a second output interface of the at least two output interfaces sends the tracking message generated by the target system to the receiving end; wherein the content of the first and second substances,

the first pointer is used for pointing to a corresponding table entry of the second output interface in the set routing table; each table entry in the set routing table corresponds to one of the at least two output interfaces, and at least a second pointer of the corresponding output interface is recorded; the second pointer is used for calling a sending function of the corresponding output interface.

In an embodiment, the electronic device further comprises a monitoring unit for:

and updating the first pointer according to the monitoring result.

In one embodiment, the electronic device further comprises:

a first generating unit, configured to generate an interface change message when the first output interface changes from a first state to a second state; the interface change message indicates the second output interface;

a third sending unit, configured to send the interface change message through the first output interface, so that the receiving end merges the trace messages sent by the at least two output interfaces according to the interface change message.

In practical applications, the first transmitting unit 601, the second transmitting unit 602, the monitoring unit, the first generating unit, and the third transmitting unit may be implemented by a processor in the electronic device, and of course, the processor needs to run a program stored in the memory to implement the functions of the above program modules.

In order to implement the method for receiving a trace message according to the embodiment of the present application, an embodiment of the present application further provides an electronic device, as shown in fig. 7, where the electronic device is used as a receiving end of the trace message and is deployed with a DTS, and the electronic device includes:

a receiving unit 701, configured to receive a trace message through at least two input interfaces in one-to-one correspondence with at least two output interfaces of a target system; each tracking message is generated by the target system and is sent by the sending end through one of the at least two output interfaces;

a merging unit 702, configured to merge the trace messages received by all the at least two input interfaces to obtain a log file about the target system.

In an embodiment, the merging unit 702 is configured to:

all trace messages received are written to the log file in chronological order based on the timestamp of the trace message.

In one embodiment, when the receiving unit 701 receives the trace message through at least two input interfaces corresponding to at least two output interfaces of the target system one to one, the electronic device further includes:

a second generating unit, configured to generate a corresponding message set for each of the at least two input interfaces; the message set records the messages received by the corresponding input interfaces according to the receiving sequence; the received message comprises at least a trace message;

the merging unit 702 is configured to:

and merging the message sets corresponding to all the input interfaces in the at least two input interfaces to obtain the log file.

In one embodiment, the received message further includes an interface change message; the interface change message is generated by the sending end under the condition that the first output interface is changed from the first state to the second state, and is sent by the first output interface; the second output interface is indicated in the interface change message;

the merging unit 702 is configured to, when merging message sets corresponding to all input interfaces of the at least two input interfaces to obtain a log file about the target system,:

sequentially reading messages in a first message set corresponding to a first input interface, and writing the read tracking messages into the log file according to a reading sequence; the first input interface corresponds to the first output interface;

determining a second input interface corresponding to the second output interface under the condition that the interface change message is read from the first message set;

In actual application, the receiving unit 701, the merging unit 702, and the second generating unit may be implemented by a processor in the electronic device, and of course, the processor needs to run a program stored in a memory to implement the functions of the above program modules.

It should be noted that, in the above-mentioned fig. 6 and fig. 7, the electronic device provided in the embodiment is only exemplified by the division of the above-mentioned program modules, and in practical applications, the above-mentioned processing distribution may be completed by different program modules according to needs, that is, the internal structure of the electronic device is divided into different program modules to complete all or part of the above-mentioned processing. In addition, the electronic device and the embodiment of the method for transmitting the trace message provided by the above embodiment belong to the same concept, and specific implementation processes thereof are described in the embodiment of the method for transmitting the trace message in detail, and are not described herein again.

Based on the hardware implementation of the program module, in order to implement the method of the embodiment of the present application, an embodiment of the present application further provides an electronic device. Fig. 8 is a schematic diagram of a hardware component structure of an electronic device 800 according to an embodiment of the present disclosure. The electronic device 800 shown in fig. 8 includes a processor 810, and the processor 810 can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 8, the electronic device 800 may also include a memory 820. From the memory 820, the processor 810 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.

Optionally, as shown in fig. 8, the electronic device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 830 may include a transmitter and a receiver, among others. The transceiver 830 may further include one or more antennas.

Optionally, the electronic device 800 may implement a corresponding process of the sending method of each trace message in the embodiment of the present application, or the electronic device 800 may implement a corresponding process of the receiving method of each trace message in the embodiment of the present application, and for brevity, details are not described here again.

The memory in the embodiments of the present application is used to store various types of data to support operations in an electronic device. Examples of such data include: any computer program for operating on an associated device.

It will be appreciated that the memory can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. Among them, the nonvolatile Memory may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic random access Memory (FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memories described in the embodiments of the present application are intended to comprise, without being limited to, these and any other suitable types of memory.

The method disclosed in the embodiments of the present application may be applied to a processor, or may be implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor described above may be a general purpose processor, a DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in a memory where a processor reads the programs in the memory and in combination with its hardware performs the steps of the method as previously described.

When the processor executes the program, corresponding processes in the methods of the embodiments of the present application are implemented, and for brevity, are not described herein again.

In an exemplary embodiment, the present application further provides a storage medium, i.e., a computer storage medium, specifically a computer readable storage medium, for example, including a memory storing a computer program, which is executable by a processor to perform the steps of the foregoing method. The computer readable storage medium may be Memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface Memory, optical disk, or CD-ROM.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, electronic device and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media that can store program code.

Alternatively, the integrated units described above in the present application may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as independent products. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or portions thereof that contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling an electronic device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media that can store program code.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for sending a trace message, the method comprising:

2. The method of claim 1, wherein the target system is configured with at least three output interfaces;

the second output interface has a highest priority among all of the at least three output interfaces in the first state.

3. The method according to claim 1 or 2, wherein when the trace message generated by the target system is sent to the receiving end through the first output interface and a second output interface of the at least two output interfaces, the method comprises:

4. The method of claim 3, further comprising:

and updating the first pointer according to the monitoring result.

5. The method according to any one of claims 1 to 4, wherein in case the first output interface changes from a first state to a second state, the method further comprises:

generating an interface change message; the interface change message indicates the second output interface;

and sending the interface change message through the first output interface, so that the receiving end combines the tracking messages sent by the at least two output interfaces according to the interface change message.

6. A method for receiving a trace message, the method comprising:

7. The method of claim 6, wherein merging trace messages received by all of the at least two input interfaces to obtain a log file about the target system comprises:

8. The method of claim 6, wherein when receiving trace messages via at least two input interfaces in one-to-one correspondence with at least two output interfaces of a target system, the method further comprises:

generating a corresponding message set for each input interface of the at least two input interfaces respectively; the message set records the messages received by the corresponding input interfaces according to the receiving sequence; the received message comprises at least a trace message;

the merging the trace messages received by all the at least two input interfaces to obtain a log file about the target system includes:

9. The method of claim 8, wherein the received message further comprises an interface change message; the interface change message is generated by the sending end under the condition that the first output interface is changed from the first state to the second state, and is sent by the first output interface; the second output interface is indicated in the interface change message;

when the message sets corresponding to all the input interfaces in the at least two input interfaces are merged to obtain the log file of the target system, the method includes:

10. An electronic device, comprising:

11. The electronic device of claim 10, further comprising:

12. An electronic device, comprising:

13. The electronic device according to claim 12, wherein when the receiving unit receives the trace message through at least two input interfaces in one-to-one correspondence with at least two output interfaces of the target system, the electronic device further comprises:

the merging unit is configured to:

14. The electronic device of claim 13, wherein the received message further comprises an interface change message; the interface change message is generated by the sending end under the condition that the first output interface is changed from the first state to the second state, and is sent by the first output interface; the second output interface is indicated in the interface change message;

the merging unit is configured to, when merging message sets corresponding to all input interfaces of the at least two input interfaces to obtain a log file about the target system,:

15. An electronic device, comprising: a processor and a memory for storing a computer program capable of running on the processor,

wherein the processor is configured to perform the steps of the method of any one of claims 1 to 5 or any one of claims 6 to 9 when running the computer program.

16. A storage medium having a computer program stored thereon, the computer program, when being executed by a processor, realizing the steps of the method of any one of claims 1 to 5 or of any one of claims 6 to 9.