Service instance communication state visualization method

Abstract

The invention discloses a service instance communication state visualization method, which comprises the following steps: acquiring an ARXML configuration file between processes to be monitored, and analyzing the ARXML configuration file to generate a configuration file in a Json format; selecting a service interface needing to be monitored from the configuration file in the Json format; generating a topological graph according to the service interface needing to be monitored and the reference relationship between the service interface needing to be monitored and the service instance; and displaying the communication state of the service instance through the topological graph. According to the method, the topological graph corresponding to the service instance needing to be monitored is generated, so that a user can consult and detect the communication state of the service instance needing to be monitored in real time and timely discover and maintain the communication problem, and the convenience and the maintenance efficiency are improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method for visualizing the communication status of a service instance. Background Art

[0002] SOME / IP (Scalable service-oriented MiddlewarE over IP) is a concept introduced by in-vehicle Ethernet communication, located above layer 4 (transport layer) of the OSI 7-layer model. In the in-vehicle network based on the CAN bus, the communication process is signal-oriented (except for diagnostic communication). This is a communication process implemented according to the sender's needs. When the sender finds that the value of the signal has changed or the sending cycle has arrived, it will send information without considering whether the receiver has any needs. SOME / IP is different. It will only be sent when the receiver has a need. The advantage of this method is that there will not be too much unnecessary data on the bus, thereby reducing the load.

[0003] Due to the complexity of the SOME / IP protocol, during the AUTOSAR software development and testing process, it often happens that after the SOME / IP client sends a message, the server does not respond, or the server responds to the client's Find request, but the client never has a Subscribe request. Because it is impossible to check the communication status of the service instance in real time, it is impossible to determine whether the communication connection fails or the message content is wrong.

[0004] Currently, no method has been proposed to visualize the communication status of service instances. Summary of the invention

[0005] The main purpose of this application is to provide a service instance communication status visualization to solve the problem in the prior art that the communication status of the service instance cannot be checked in real time.

[0006] In order to achieve the above objectives, in a first aspect, the present application provides a method for visualizing the communication status of a service instance, comprising:

[0007] Get the ARXML configuration file between the processes to be monitored, parse the ARXML configuration file, and generate a configuration file in Json format;

[0008] Select the service interface to be monitored from the Json format configuration file;

[0009] Generate a topology graph based on the service interface to be monitored and the reference relationship between the service interface to be monitored and the service instance;

[0010] The communication status of service instances is displayed through topology graphics.

[0011] In a possible implementation, the ARXML configuration file is parsed to generate a configuration file in Json format, including:

[0012] Parse all process information, service instance information and service interface information from the ARXML configuration file;

[0013] Generate a configuration file in Json format based on the correspondence between all process information, service instance information and service interface information.

[0014] In a possible implementation, the method further includes:

[0015] The ARXML configuration file is detected. If the ARXML configuration file does not meet the preset conditions, a prompt message is generated, wherein the prompt message is used to prompt the user that the ARXML configuration file is parsed incorrectly.

[0016] In a possible implementation, the service interface to be monitored is selected from the configuration file in Json format, including:

[0017] Parse the service interface information from the Json format configuration file and display it;

[0018] In response to a trigger operation performed by a user on a service interface in the service interface information in a display page, a service interface that needs to be monitored is displayed.

[0019] In a possible implementation, a topology graph is generated according to a service interface to be monitored and a reference relationship between the service interface to be monitored and a service instance, including:

[0020] Parse the corresponding process information, service instance, and service deployment information from the Json-formatted configuration file based on the service interface that needs to be monitored;

[0021] A topology graph is generated according to the correspondence between the service interface to be monitored and the process information, the correspondence between the service interface to be monitored and the service instance, and the correspondence between the service interface to be monitored and the service deployment information.

[0022] In a possible implementation, the communication status of the service instance is displayed through a topology graph, including:

[0023] Use the Wireshark packet capture tool to capture communication packets through the mirror port of the switch connected;

[0024] The communication message is stored in the pcap file format and the pcap format file is parsed to obtain the data type and direction, so that the topology graph can display the communication status of the service instance based on the data type and direction.

[0025] In a possible implementation, the method further includes:

[0026] Updates the communication status of the service instance in the topology graph.

[0027] In a possible implementation, updating the communication status of the service instance in the topology graph includes:

[0028] Capture communication messages regularly;

[0029] Filtering service subscription type messages and service provision type messages from communication messages;

[0030] Parse the Entry Array field in the service subscription type message and the service provision type message to obtain the service information;

[0031] Determine whether the service information is within the monitoring range;

[0032] If the service information is within the monitoring range, the communication status of the service instance in the topology graph is updated.

[0033] In a possible implementation, the method further includes:

[0034] If the service information is not within the monitoring range, return to the step of executing the periodic capture of communication messages.

[0035] In a possible implementation, the method further includes:

[0036] Get the message list;

[0037] Deserialize the message content in the message list and determine whether the message content is abnormal.

[0038] In a second aspect, an embodiment of the present invention provides a service instance communication status visualization device, including:

[0039] The file generation module is used to obtain the ARXML configuration file between the processes to be monitored, parse the ARXML configuration file, and generate a configuration file in Json format;

[0040] The interface selection module is used to select the service interface to be monitored from the configuration file in Json format;

[0041] A graph generation module is used to generate a topology graph based on the service interface to be monitored and the reference relationship between the service interface to be monitored and the service instance;

[0042] The visualization module is used to display the communication status of service instances through topology graphics.

[0043] In a third aspect, an embodiment of the present invention provides a terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of any of the above service instance communication status visualization methods are implemented.

[0044] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of any of the above service instance communication status visualization methods are implemented.

[0045] The embodiment of the present invention provides a method for visualizing the communication status of a service instance, including: first obtaining an ARXML configuration file between processes to be monitored, parsing the ARXML configuration file, generating a configuration file in Json format, then selecting a service interface to be monitored from the configuration file in Json format, and then generating a topology graph based on the service interface to be monitored, the reference relationship between the service interface to be monitored and the service instance, so as to display the communication status of the service instance through the topology graph. By generating a topology graph corresponding to the service instance to be monitored, the application enables the user to check and detect the communication status of the service instance to be monitored in real time, and timely discover and maintain communication problems, thereby improving convenience and maintenance efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The drawings constituting a part of this application are used to provide a further understanding of this application, so that other features, purposes and advantages of this application become more obvious. The schematic embodiment drawings and their descriptions of this application are used to explain this application and do not constitute an improper limitation on this application. In the drawings:

[0047] Figure 1 It is a flow chart of an implementation method of a service instance communication status visualization method provided by an embodiment of the present invention;

[0048] Figure 2 It is a schematic diagram of the association relationship between a service interface and a service instance provided by an embodiment of the present invention;

[0049] Figure 3 It is a structural diagram of a device for visualizing the communication status of a service instance provided by an embodiment of the present invention;

[0050] Figure 4 It is a flow chart of a method for updating the communication status of a service instance provided by an embodiment of the present invention;

[0051] Figure 5 is a structural diagram of a device for visualizing communication status of a service instance provided by another embodiment of the present invention;

[0052] Figure 6is a schematic diagram of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0054] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in sequences other than those illustrated or described herein.

[0055] It should be understood that in various embodiments of the present invention, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0056] It should be understood that in the present invention, "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products or apparatuses.

[0057] It should be understood that in the present invention, "plurality" refers to two or more than two. "And / or" is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "Contains A, B and C", "Contains A, B, C" means that A, B, and C are all included, "Contains A, B or C" means that one of A, B, and C is included, and "Contains A, B and / or C" means that any one, any two, or any three of A, B, and C are included.

[0058] It should be understood that in the present invention, "B corresponding to A", "B corresponding to A", "A corresponds to B" or "B corresponds to A" means that B is associated with A and B can be determined based on A. Determining B based on A does not mean determining B based only on A, but B can also be determined based on A and / or other information. A and B match when the similarity between A and B is greater than or equal to a preset threshold.

[0059] Depending on the context, "if" as used herein may be interpreted as "when" or "when" or "in response to determining" or "in response to detecting."

[0060] The technical solution of the present invention is described in detail with specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0061] In order to make the purpose, technical solutions and advantages of the present invention more clear, specific embodiments will be described below in conjunction with the accompanying drawings.

[0062] In one embodiment, Figure 1 As shown, a method for visualizing the communication status of a service instance is provided, comprising the following steps:

[0063] Step S101: Obtain an ARXML configuration file between processes to be monitored, parse the ARXML configuration file, and generate a configuration file in Json format.

[0064] After obtaining the ARXML configuration file between the processes to be monitored, you need to import the ARXML configuration file between the processes to be monitored into the tool, and then parse the ARXML configuration file to generate a configuration file in Json format.

[0065] Among them, the ARXML configuration file is parsed to generate a configuration file in Json format. Specifically, all process information, service instance information and service interface information are first parsed from the ARXML configuration file, and then the configuration file in Json format is generated according to the correspondence between all process information, service instance information and service interface information.

[0066] The ARXML configuration file needs to be tested, that is, the ARXML configuration file is tested. If the ARXML configuration file does not meet the preset conditions, a prompt message is generated, wherein the prompt message is used to prompt the user that the ARXML configuration file is parsed incorrectly. The preset conditions include but are not limited to syntax requirements, file type requirements, etc.

[0067] Step S102: Select the service interface to be monitored from the configuration file in the Json format.

[0068] For selecting the service interface that needs to be monitored from the configuration file in Json format, the service interface information must first be parsed from the configuration file in Json format and displayed, and then in response to the trigger operation performed by the user on the service interface in the service interface information in the display page, the service interface that needs to be monitored is displayed.

[0069] After the service interface information is parsed, it is displayed on the tool display page. Users can select the service interface to be monitored in the service interface information column on the tool display page. This visual operation is convenient and improves the user experience.

[0070] Step S103: Generate a topology graph based on the service interface to be monitored and the reference relationship between the service interface to be monitored and the service instance.

[0071] To generate a topology graph based on the service interface that needs to be monitored and the reference relationship between the service interface that needs to be monitored and the service instance, it is necessary to first parse the corresponding process information, service instance, and service deployment information from the Json format configuration file based on the service interface that needs to be monitored. Then, based on the correspondence between the service interface that needs to be monitored and the process information, the correspondence between the service interface that needs to be monitored and the service instance, and the correspondence between the service interface that needs to be monitored and the service deployment information, generate a topology graph.

[0072] According to the selected service interface, the tool parses the corresponding process information, service instance (Required, Provide), service deployment information (Service Interface Id, Method id, Event id, etc.) from the above Json format configuration file, and generates the following according to the reference relationship between process information, service instance (Required, Provide), and service deployment information (ServiceInterface Id, Method id, Event id, etc.): Figure 2 The topology diagram shown.

[0073] pass Figure 2 As shown in the topology diagram, different service interfaces are associated with different service instances, such as service interface 1 is associated with service instance 1 and service instance 2. In addition, different service interfaces are configured with corresponding events and methods, such as service interface 1 is associated with event group 1 and event group 2, and method 1 and method 2.

[0074] Step S104: Display the communication status of the service instance through a topology graph.

[0075] To display the communication status of a service instance through a topology graph, you need to use the mirror port of the switch connected to the Wireshark packet capture tool to capture the communication packets, then store the communication packets in pcap file format and parse the pcap format file to obtain the data type and direction, so that the topology graph can display the communication status of the service instance based on the data type and direction.

[0076] Among them, Wireshark is a network packet capture and analysis software. The function of network packet capture and analysis software is to intercept network packets and display the most detailed network packet information as possible. Wireshark uses WinPCAP as an interface to directly exchange data packets with the network card. It provides a universal packet capture interface and can obtain data packets from different types of network interfaces (including Ethernet, Token Ring, ATM, etc.).

[0077] The traffic mirror port of the switch is a means of monitoring network traffic. It monitors the network by forwarding the data traffic of one or more source ports on the switch to a designated port. The designated port is called a "mirror port" or "destination port". Without seriously affecting the normal throughput of the source port, the network traffic can be monitored and analyzed through the mirror port. The internal network data of the enterprise can be monitored and managed, and the fault can be quickly located when the network fails.

[0078] The communication status of the service instance includes: server status: whether the service provides someip-sd messages, such as identification through offerService messages in someip-sd sent periodically; client and event group status: client subscription event group status, whether the event group in the server has been subscribed; event (method) status: whether the communication method is called (Event, Method).

[0079] Specifically, Figure 3 As shown, you can first enable the monitoring function in the tool, and then use the Wireshark packet capture tool to connect to the traffic mirror port (mirror port) of the switch to enable SOME / IP communication packet capture.

[0080] Connect the SOME / IP client (AP client) and server (AP server) to the common port of the switch to start communication. Use the Wireshark packet capture tool to capture communication packets in real time. The Wireshark packet capture tool stores the communication data packet file in .pcap format.

[0081] The monitoring tool periodically (configurable) reads and parses the .pcap file, determines the data direction and type according to the source IP, destination IP, source port, destination port, message type, Service Interface Id, Method id, Event id and other information in the message, and makes color markings on the service instances, event groups and methods in the topology graph.

[0082] The present application can also update the communication status of the service instance in the topology graph. Specifically, updating the communication status of the service instance in the topology graph includes: periodically capturing communication messages; filtering out service subscription type messages and service provision type messages from the communication messages; parsing the EntryArray field in the service subscription type messages and service provision type messages to obtain service information; determining whether the service information is within the monitoring range; if the service information is within the monitoring range, updating the communication status of the service instance in the topology graph; if the service information is not within the monitoring range, returning to execute the step of periodically capturing communication messages.

[0083] like Figure 4 As shown, monitoring is turned on, and then communication messages are captured periodically, such as messages related to SOME / IP, and then service subscription type messages and service provision type messages are filtered out from the communication messages; the Entry Array field in the service subscription type messages and the service provision type messages is parsed to obtain the service information of the service subscription type messages and the service information of the service provision type messages, such as Service ID and Instance ID. Then the service information of the service subscription type messages and the service information of the service provision type messages are matched, and the matched service information is monitored to determine whether the service information is within the monitoring range. If the service information is within the monitoring range, the communication status of the service instance in the topology graph is updated; if the service information is not within the monitoring range, return to the step of executing the periodic capture of communication messages.

[0084] This application also provides other monitoring functions for message content, such as obtaining a message list, then deserializing the message content in the message list, and determining whether the message content is abnormal.

[0085] Specifically, the monitoring tool can view the SOME / IP message list and deserialize the message content. It can also view the message details to determine whether the message content on both the SOME / IP client and server sides is normal. Referring to the data type defined by the service, the message data can be converted into an understandable format, including: attribute name, type, and value.

[0086] The embodiment of the present invention provides a method for visualizing the communication status of a service instance, including: first obtaining an ARXML configuration file between processes to be monitored, parsing the ARXML configuration file, generating a configuration file in Json format, then selecting a service interface to be monitored from the configuration file in Json format, and then generating a topology graph based on the service interface to be monitored, the reference relationship between the service interface to be monitored and the service instance, so as to display the communication status of the service instance through the topology graph. By generating a topology graph corresponding to the service instance to be monitored, the application enables the user to check and detect the communication status of the service instance to be monitored in real time, and timely discover and maintain communication problems, thereby improving convenience and maintenance efficiency.

[0087] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0088] The following is an embodiment of the device of the present invention. For details not described in detail, reference may be made to the corresponding method embodiments described above.

[0089] Figure 5 A schematic diagram of the structure of a service instance communication status visualization device provided by an embodiment of the present invention is shown. For the convenience of description, only the parts related to the embodiment of the present invention are shown. A service instance communication status visualization device includes a file generation module 501, an interface selection module 502, a graphic generation module 503 and a visualization module 504, which are as follows:

[0090] The file generation module 501 is used to obtain the ARXML configuration file between the processes to be monitored, parse the ARXML configuration file, and generate a configuration file in Json format;

[0091] The interface selection module 502 is used to select the service interface to be monitored from the configuration file in Json format;

[0092] A graph generation module 503 is used to generate a topology graph based on the service interface to be monitored and the reference relationship between the service interface to be monitored and the service instance;

[0093] The visualization module 504 is used to display the communication status of the service instance through a topology graph.

[0094] In a possible implementation, the file generation module 501 is further used to parse all process information, service instance information and service interface information from the ARXML configuration file;

[0095] Generate a configuration file in Json format based on the correspondence between all process information, service instance information and service interface information.

[0096] In a possible implementation, the device further includes: a file detection module, which is used to detect the ARXML configuration file, and if the ARXML configuration file does not meet the preset conditions, generate a prompt message, wherein the prompt message is used to prompt the user that the ARXML configuration file is parsed incorrectly.

[0097] In a possible implementation, the interface selection module 502 is further used to parse the service interface information from the configuration file in Json format and display it;

[0098] In response to a trigger operation performed by a user on a service interface in the service interface information in a display page, a service interface that needs to be monitored is displayed.

[0099] In a possible implementation, the graph generation module 503 is further used to parse the corresponding process information, service instance, and service deployment information from the configuration file in Json format according to the service interface to be monitored;

[0100] A topology graph is generated according to the correspondence between the service interface to be monitored and the process information, the correspondence between the service interface to be monitored and the service instance, and the correspondence between the service interface to be monitored and the service deployment information.

[0101] In a possible implementation, the visualization module 504 is further used to capture communication packets using a mirror port of a switch connected by a Wireshark packet capture tool;

[0102] The communication message is stored in the pcap file format and the pcap format file is parsed to obtain the data type and direction, so that the topology graph can display the communication status of the service instance based on the data type and direction.

[0103] In a possible implementation manner, the device further includes: a state updating module, which is used to update the communication state of the service instance in the topology graph.

[0104] In a possible implementation, the state update module is also used to capture communication messages at a regular interval;

[0105] Filtering service subscription type messages and service provision type messages from communication messages;

[0106] Parse the Entry Array field in the service subscription type message and the service provision type message to obtain the service information;

[0107] Determine whether the service information is within the monitoring range;

[0108] If the service information is within the monitoring range, the communication status of the service instance in the topology graph is updated.

[0109] In a possible implementation, the device further includes: a return execution module, which is used to return to the step of periodically capturing communication messages if the service information is not within the monitoring range.

[0110] In a possible implementation, the device further includes: a message content processing module, the message content processing module is used to obtain a message list;

[0111] Deserialize the message content in the message list and determine whether the message content is abnormal.

[0112] The embodiment of the present invention provides a device for visualizing the communication status of a service instance, which is specifically used to: first obtain an ARXML configuration file between processes to be monitored, parse the ARXML configuration file, generate a configuration file in Json format, then select the service interface to be monitored from the configuration file in Json format, and then generate a topology graph based on the service interface to be monitored, the reference relationship between the service interface to be monitored and the service instance, so as to display the communication status of the service instance through the topology graph. This application generates a topology graph corresponding to the service instance to be monitored, so that the user can check and detect the communication status of the service instance to be monitored in real time, and timely discover and maintain communication problems, thereby improving convenience and maintenance efficiency.

[0113] Figure 6 is a schematic diagram of a terminal provided by an embodiment of the present invention. Figure 6 As shown, the terminal 6 of this embodiment includes: a processor 601, a memory 602, and a computer program 606 stored in the memory 602 and executable on the processor 601. When the processor 601 executes the computer program 606, the steps in the above-mentioned embodiments of the method for visualizing the communication status of each service instance are implemented, for example Figure 1 Alternatively, when the processor 601 executes the computer program 606, the functions of each module / unit in the above-mentioned embodiments of the apparatus for visualizing the communication status of each service instance are realized, for example Figure 5 Functionality of modules / units 501-504 is shown.

[0114] The present invention also provides a readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, it is used to implement a method for visualizing the communication status of a service instance provided in the above-mentioned various embodiments, including:

[0115] Get the ARXML configuration file between the processes to be monitored, parse the ARXML configuration file, and generate a configuration file in Json format;

[0116] Select the service interface to be monitored from the Json format configuration file;

[0117] Generate a topology graph based on the service interface to be monitored and the reference relationship between the service interface to be monitored and the service instance;

[0118] The communication status of service instances is displayed through topology graphics.

[0119] In a possible implementation, the ARXML configuration file is parsed to generate a configuration file in Json format, including:

[0120] Parse all process information, service instance information and service interface information from the ARXML configuration file;

[0121] Generate a configuration file in Json format based on the correspondence between all process information, service instance information and service interface information.

[0122] In a possible implementation, the method further includes:

[0123] The ARXML configuration file is detected. If the ARXML configuration file does not meet the preset conditions, a prompt message is generated, wherein the prompt message is used to prompt the user that the ARXML configuration file is parsed incorrectly.

[0124] In a possible implementation, the service interface to be monitored is selected from the configuration file in Json format, including:

[0125] Parse the service interface information from the Json format configuration file and display it;

[0126] In response to a trigger operation performed by a user on a service interface in the service interface information in a display page, a service interface that needs to be monitored is displayed.

[0127] In a possible implementation, a topology graph is generated according to a service interface to be monitored and a reference relationship between the service interface to be monitored and a service instance, including:

[0128] Parse the corresponding process information, service instance, and service deployment information from the Json-formatted configuration file based on the service interface that needs to be monitored;

[0129] A topology graph is generated according to the correspondence between the service interface to be monitored and the process information, the correspondence between the service interface to be monitored and the service instance, and the correspondence between the service interface to be monitored and the service deployment information.

[0130] In a possible implementation, the communication status of the service instance is displayed through a topology graph, including:

[0131] Use the Wireshark packet capture tool to capture communication packets through the mirror port of the switch connected;

[0132] The communication message is stored in the pcap file format and the pcap format file is parsed to obtain the data type and direction, so that the topology graph can display the communication status of the service instance based on the data type and direction.

[0133] In a possible implementation, the method further includes:

[0134] Updates the communication status of the service instance in the topology graph.

[0135] In a possible implementation, updating the communication status of the service instance in the topology graph includes:

[0136] Capture communication messages regularly;

[0137] Filtering service subscription type messages and service provision type messages from communication messages;

[0138] Parse the Entry Array field in the service subscription type message and the service provision type message to obtain the service information;

[0139] Determine whether the service information is within the monitoring range;

[0140] If the service information is within the monitoring range, the communication status of the service instance in the topology graph is updated.

[0141] In a possible implementation, the method further includes:

[0142] If the service information is not within the monitoring range, return to the step of executing the periodic capture of communication messages.

[0143] In a possible implementation, the method further includes:

[0144] Get the message list;

[0145] Deserialize the message content in the message list and determine whether the message content is abnormal.

[0146] Among them, the readable storage medium can be a computer storage medium or a communication medium. The communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The computer storage medium can be any available medium that can be accessed by a general or special-purpose computer. For example, a readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application-specific integrated circuit (ASIC). In addition, the ASIC can be located in a user device. Of course, the processor and the readable storage medium can also exist in a communication device as discrete components. The readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0147] The present invention also provides a program product, which includes an execution instruction, and the execution instruction is stored in a readable storage medium. At least one processor of a device can read the execution instruction from the readable storage medium, and at least one processor executes the execution instruction so that the device implements a method for visualizing the communication status of a service instance provided by various embodiments described above, including:

[0148] Get the ARXML configuration file between the processes to be monitored, parse the ARXML configuration file, and generate a configuration file in Json format;

[0149] Select the service interface to be monitored from the Json format configuration file;

[0150] Generate a topology graph based on the service interface to be monitored and the reference relationship between the service interface to be monitored and the service instance;

[0151] The communication status of service instances is displayed through topology graphics.

[0152] In a possible implementation, the ARXML configuration file is parsed to generate a configuration file in Json format, including:

[0153] Parse all process information, service instance information and service interface information from the ARXML configuration file;

[0154] Generate a configuration file in Json format based on the correspondence between all process information, service instance information and service interface information.

[0155] In a possible implementation, the method further includes:

[0156] The ARXML configuration file is detected. If the ARXML configuration file does not meet the preset conditions, a prompt message is generated, wherein the prompt message is used to prompt the user that the ARXML configuration file is parsed incorrectly.

[0157] In a possible implementation, the service interface to be monitored is selected from the configuration file in Json format, including:

[0158] Parse the service interface information from the Json format configuration file and display it;

[0159] In response to a trigger operation performed by a user on a service interface in the service interface information in a display page, a service interface that needs to be monitored is displayed.

[0160] In a possible implementation, a topology graph is generated according to a service interface to be monitored and a reference relationship between the service interface to be monitored and a service instance, including:

[0161] Parse the corresponding process information, service instance, and service deployment information from the Json-formatted configuration file based on the service interface that needs to be monitored;

[0162] A topology graph is generated according to the correspondence between the service interface to be monitored and the process information, the correspondence between the service interface to be monitored and the service instance, and the correspondence between the service interface to be monitored and the service deployment information.

[0163] In a possible implementation, the communication status of the service instance is displayed through a topology graph, including:

[0164] Use the Wireshark packet capture tool to capture communication packets through the mirror port of the switch connected;

[0165] The communication message is stored in the pcap file format and the pcap format file is parsed to obtain the data type and direction, so that the topology graph can display the communication status of the service instance based on the data type and direction.

[0166] In a possible implementation, the method further includes:

[0167] Updates the communication status of the service instance in the topology graph.

[0168] In a possible implementation, updating the communication status of the service instance in the topology graph includes:

[0169] Capture communication messages regularly;

[0170] Filtering service subscription type messages and service provision type messages from communication messages;

[0171] Parse the Entry Array field in the service subscription type message and the service provision type message to obtain the service information;

[0172] Determine whether the service information is within the monitoring range;

[0173] If the service information is within the monitoring range, the communication status of the service instance in the topology graph is updated.

[0174] In a possible implementation, the method further includes:

[0175] If the service information is not within the monitoring range, return to the step of executing the periodic capture of communication messages.

[0176] In a possible implementation, the method further includes:

[0177] Get the message list;

[0178] Deserialize the message content in the message list and determine whether the message content is abnormal.

[0179] In the embodiments of the above-mentioned devices, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in the present invention may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0180] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention.

Claims

1. A method for visualizing the communication status of a service instance, characterized in that: include: Obtain the ARXML configuration file between the processes to be monitored, parse the ARXML configuration file, and generate a configuration file in Json format; Select the service interface to be monitored from the configuration file in the Json format; Generate a topology graph according to the service interface to be monitored and the reference relationship between the service interface to be monitored and the service instance; The communication status of the service instance is displayed through the topology graph.

2. A method for visualizing the communication status of a service instance according to claim 1, characterized in that: The ARXML configuration file is parsed to generate a configuration file in Json format, including: Parse all process information, service instance information and service interface information from the ARXML configuration file; The configuration file in the Json format is generated according to the correspondence between all the process information, the service instance information and the service interface information.

3. A method for visualizing the communication status of a service instance according to claim 1, characterized in that: The method further comprises: The ARXML configuration file is detected, and if the ARXML configuration file does not meet the preset conditions, a prompt message is generated, wherein the prompt message is used to prompt a user that the ARXML configuration file is parsed incorrectly.

4. A method for visualizing the communication status of a service instance according to claim 1, characterized in that: The selecting the service interface to be monitored from the configuration file in the Json format includes: Parse the service interface information from the configuration file in the Json format and display it; In response to a trigger operation performed by a user on a service interface in the service interface information in a display page, a service interface that needs to be monitored is displayed.

5. A method for visualizing the communication status of a service instance according to claim 1, characterized in that: The generating a topology graph according to the service interface to be monitored and the reference relationship between the service interface to be monitored and the service instance includes: Parse the corresponding process information, service instance, and service deployment information from the configuration file in the Json format according to the service interface that needs to be monitored; The topology graph is generated according to the correspondence between the service interface to be monitored and the process information, the correspondence between the service interface to be monitored and the service instance, and the correspondence between the service interface to be monitored and the service deployment information.

6. A method for visualizing the communication status of a service instance according to claim 1, characterized in that: The displaying of the communication status of the service instance by means of the topology graph includes: Use the Wireshark packet capture tool to capture communication packets through the mirror port of the switch connected; The communication message is stored in a pcap file format and the pcap format file is parsed to obtain the data type and direction, so that the topology graph displays the communication status of the service instance based on the data type and direction.

7. A method for visualizing the communication status of a service instance according to claim 1, characterized in that: The method further comprises: The communication status of the service instances in the topology graph is updated.

8. A method for visualizing the communication status of a service instance according to claim 7, characterized in that: The updating of the communication status of the service instance in the topology graph includes: Capture communication messages regularly; Filtering out service subscription type messages and service provision type messages from the communication messages; Parse the Entry Array field in the service subscription type message and the service provision type message to obtain the service information; Determining whether the service information is within the monitoring range; If the service information is within the monitoring range, the communication status of the service instance in the topology graph is updated.

9. A method for visualizing the communication status of a service instance according to claim 8, characterized in that: The method further comprises: If the service information is not within the monitoring range, return to the step of periodically capturing communication messages.

10. A method for visualizing the communication status of a service instance according to claim 1, characterized in that: The method further comprises: Get the message list; Deserialize the message content in the message list, and determine whether the message content is abnormal.

Images