Microservice-based fault indicator full-process access method and system

Abstract

The application discloses a micro-service-based fault indicator whole-process access method and system, belongs to the field of power electronics, and comprises the following steps: obtaining fault indicator information and power distribution terminal point number basic information that need to be accessed; performing verification according to the fault indicator information, the power distribution terminal point number basic information, and a pre-established parameter template and point number template; if the verification is passed, corresponding fault indicator models are established, and corresponding power distribution terminal information and power distribution terminal point number information are generated; and according to a micro-service calling request, the micro-service is called to execute corresponding steps based on the fault indicator models, the power distribution terminal information and the power distribution terminal point number information. The method can simplify operation steps, reduce waste of human and time costs, and improve the efficiency and accuracy of power distribution Internet of Things equipment access.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of power electronics, and particularly relates to a fault indicator full-process access method based on a micro-service architecture. BACKGROUND

[0002] With the construction of power distribution Internet of Things, fault indicator devices are massively accessed to distribution networks. These terminal devices with collection and edge computing capabilities save the working time of field maintenance personnel, but put forward high standards and high requirements for the power supply reliability and power supply service capability of urban distribution networks, and increase the difficulty of management of distribution network operation and maintenance personnel. The traditional fault indicator full-process access business has the following shortcomings:

[0003] 1. It needs operation and maintenance personnel to install related software on an office computer to realize it, and cannot realize WEB end maintenance function, and the operation is complicated and complex.

[0004] 2. It cannot realize subarea maintenance of cities and counties, does not conform to the use habit of users, and leads to low work efficiency of operation and maintenance personnel.

[0005] 3. When a problem occurs in a link in the fault indicator access process, the manual troubleshooting method is inefficient, difficult, high in cost, and difficult to guarantee timeliness. SUMMARY

[0006] In order to solve the problem of low efficiency of traditional power distribution Internet of Things system in accessing fault indicators, the application provides a fault indicator full-process access method based on a micro-service architecture, realizes online modeling, point building and debugging of terminal devices, and improves work efficiency and correctness.

[0007] In order to achieve the above technical purposes, the application adopts the following technical scheme.

[0008] On the one hand, the application provides a fault indicator full-process access method based on a micro-service, comprising:

[0009] obtaining fault indicator information and power distribution terminal point number basic information to be accessed;

[0010] According to the fault indicator information, the power distribution terminal point number basic information, and the pre-established parameter template and point number template, verification is performed. If the verification is passed, a micro-service is called to execute the corresponding steps according to a micro-service calling request;

[0011] The micro-service calling request includes a fault indicator model creation calling request, a corresponding fault indicator model is established by calling a micro-service, and corresponding power distribution terminal information and power distribution terminal point number information are generated.

[0012] Further, the microservice calling request further includes an upload device encryption certificate calling request, calling a microservice to upload the encryption certificate to a specified server address according to the selected fault indicator id number, the corresponding channel number, the encryption certificate corresponding to the channel number, and the stored server address.

[0013] Further, the microservice calling request further includes a data monitoring calling request, calling a microservice to monitor and access debugging of the fault indicator by using the power distribution terminal information and the power distribution terminal point number information.

[0014] Further, the fault indicator information includes name information and organizational relationship of the fault indicator; and the corresponding fault indicator model is established, including: creating or maintaining the fault indicator model in a real-time library and / or a commercial library according to the name information, the organizational relationship, and the corresponding belonging feeder PMS_ID of the fault indicator, including adding, modifying, and deleting the fault indicator model, and generating a unique and unchangeable fault indicator id number when adding.

[0015] Further, the parameter template is used to guide generation of the power distribution terminal information, and the point number template is used to guide generation of the power distribution terminal point number information.

[0016] Further, the power distribution terminal point number basic information includes a power distribution terminal address, a port number, a belonging manufacturer, a power distribution terminal point number template name, a parameter template name, and an RTU address.

[0017] Further, the power distribution terminal information includes a terminal id, a channel id, a channel number, a server address, and a corresponding fault indicator id number; and the power distribution terminal point number information includes remote signaling, remote measurement, custom remote signaling, custom remote measurement point number information, and a corresponding channel id that the fault indicator needs to access.

[0018] In a second aspect, the application provides a microservice-based fault indicator whole-process access system, including: a user WEB end and a background service end; the user WEB end is used to obtain fault indicator information that needs to be accessed, power distribution terminal point number basic information, and microservice calling requests;

[0019] The background service end is used to perform verification according to the fault indicator information, the power distribution terminal point number basic information, and pre-established parameter templates and point number templates; if the verification is passed, corresponding steps are executed by calling a microservice according to the microservice calling request.

[0020] The microservice calling request includes a fault indicator model creation calling request, calling a microservice to establish a corresponding fault indicator model, and generating corresponding power distribution terminal information and power distribution terminal point number information.

[0021] Further, the user WEB end is further used for selecting parameter templates and point number templates; the background service end is used for establishing corresponding fault indicator models in real-time libraries and commercial libraries and generating corresponding power distribution terminal information and power distribution terminal point number information through the port numbers and RTU addresses bound by the fault indicators needing to be accessed according to the fault indicator information, power distribution terminal point number basic information and the selected parameter templates and point number templates.

[0022] Further, the background service end is further used for batch verification, and the batch creation of fault indicator models is performed when the verification is passed.

[0023] Further, the user WEB end is further used for selecting fault indicators, downloading corresponding commissioning proof files, displaying basic information and real-time messages and adjusting the commissioning states of the corresponding power distribution terminals.

[0024] Further, the user WEB end is further used for selecting fault indicator id numbers, corresponding channel numbers, channel number corresponding encryption certificates and stored server addresses, so that the background service end uploads the encryption certificates to the specified server addresses.

[0025] Beneficial effects: the present application has the following remarkable advantages:

[0026] The present method can simplify operation steps, reduce the waste of manpower and time cost, improve the success rate of fault indicator modeling and point building, and avoid errors caused by omissions during personnel reporting due to the added verification step. BRIEF DESCRIPTION OF DRAWINGS

[0027] Figure 1 The flowchart of the present application;

[0028] Figure 2 The flowchart of creating fault indicator models in the embodiment of the present application;

[0029] Figure 3 The flowchart of modifying or deleting fault indicator models in the embodiment of the present application;

[0030] Figure 4 The flowchart of generating power distribution terminal point numbers in the embodiment of the present application;

[0031] Figure 5 The flowchart of batch modeling and point building in the embodiment of the present application;

[0032] Figure 6 The flowchart of uploading encryption certificates in the embodiment of the present application;

[0033] Figure 7 The flowchart of data monitoring in the embodiment of the present application;

[0034] Figure 8 Flowchart for accessing and debugging the fault indicator of the embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical solutions of the present application will be further described in combination with the drawings and embodiments.

[0036] Embodiment 1:

[0037] The full-process access method of the micro-service-based fault indicator, as shown in the figure, includes: obtaining fault indicator information and power distribution terminal point number basic information that need to be accessed; Figure 1

[0038] According to the fault indicator information, the power distribution terminal point number basic information, and the pre-established parameter template and point number template, verification is performed; if the verification is passed, the micro-service is called to perform the corresponding steps according to the micro-service calling request;

[0039] The micro-service calling request includes a fault indicator model creation calling request, the micro-service calls to establish the corresponding fault indicator model, and generates the corresponding power distribution terminal information and power distribution terminal point number information.

[0040] The power distribution terminal is an important part of the power distribution automation construction, which is used to collect real-time operation data of the power distribution network, detect and identify faults, and process and analyze the operating conditions of the switching device.

[0041] In specific embodiments, a modeling and point number information file is generated according to the obtained fault indicator information and power distribution terminal point number basic information that need to be accessed, and the modeling and point number information file is a table file including fault indicator information and power distribution terminal point number basic information; wherein the fault indicator information specifically includes city, county, power supply station, affiliated power station, affiliated feeder, and feeder PMS_ID (i.e. the ID of the feeder in the power management system), and the feeder PMS_ID is a mandatory field.

[0042] The power distribution terminal point number basic information specifically includes the power distribution terminal name, the power distribution terminal port number, the affiliated manufacturer, the RTU (remote terminal unit) address, the power distribution terminal point number template name, and the parameter template name; wherein the point number template name and the parameter template name must be consistent with the created template name. The combination of the port number and the RTU address cannot be repeated, and if the repetition occurs, a point number generation failure popup window will appear, and the port number and the RTU address combination needs to be changed.

[0043] According to the fault indicator information, the power distribution terminal point number basic information, and the pre-established parameter template and point number template, verification is performed, including: checking whether the mandatory field is filled, whether the affiliated manufacturer of the power distribution terminal is filled in a standard manner, and whether the parameter template name and the point number template name are consistent with the created template name.​

[0044] If the number of fault indicators to be accessed is more than one in a specific embodiment, the information of each fault indicator is acquired respectively; batch verification is performed according to the fault indicator information, the distribution terminal point number basic information, and the pre-established parameter template and point number template; and the fault indicator model is established in batch if the batch verification is passed.

[0045] In specific embodiments, the generated distribution terminal information includes but is not limited to distribution terminal id, channel id, channel number, server address, and corresponding fault indicator id; and the distribution terminal point number information includes remote signaling, remote measurement, custom remote signaling, custom remote measurement point number information, and corresponding channel id that the fault indicator needs to access.

[0046] The parameter template and the point number template need to be created and selected first, and can be flexibly configured on site. The parameter template is used to guide the generation of distribution terminal information, and the point number template is used to guide the generation of distribution terminal point number information. The creation of the parameter template needs to configure the medium voltage configuration information of the distribution network terminal table, the distribution network channel table, the distribution network communication terminal table, the distribution network Iec101 protocol table, and the distribution network Iec104 protocol table. If the relevant configuration information is not selected, no value is stored, and the parameter template is generated. The creation of the point number template needs to configure the remote signaling, remote measurement, custom remote signaling, and custom remote measurement (i.e. measurement point remote measurement) point number, and also needs to configure the table number, domain number, starting point number, and offset of each point number. After manual verification is successful, the point number template is generated.

[0047] The fault indicator information includes the name information and the organizational relationship of the fault indicator; and the establishment of the corresponding fault indicator model includes: creating or maintaining the fault indicator model in the real-time library and / or the commercial library according to the name information and the organizational relationship of the fault indicator and the corresponding belonging feeder PMS_ID, including adding, modifying, and deleting the fault indicator model. When adding, a unique and unchangeable fault indicator id number is generated. The organizational relationship is the organizational hierarchical relationship of the province-city-district-county-powersupply office-plant station-feeder-fault indicator corresponding to the fault indicator.

[0048] In specific embodiments, the microservice calling request includes an upload device encryption certificate calling request and a data monitoring calling request, etc., to upload the device encryption certificate and data monitoring of the device, and to access and debug the fault indicator.

[0049] Optionally, the microservice calling request further includes an upload device encryption certificate calling request, which calls the microservice to upload the encryption certificate to the specified server address according to the selected fault indicator id number, the corresponding channel number, and the encryption certificate corresponding to the channel number, and the stored server address.

[0050] The microservice calling request further includes a data monitoring calling request, and the microservice is called to monitor and access debugging of the fault indicator by using the power distribution terminal information and the power distribution terminal point number information.

[0051] Embodiment 2

[0052] Corresponding to the microservice-based fault indicator full-process access method provided in Embodiment 1, the present embodiment provides a microservice-based fault indicator full-process access system, which includes a user WEB end (as a microservice caller, located at the user side) and a background service end (as a microservice provider, located at the system side).

[0053] The user WEB end is configured to obtain fault indicator information to be accessed, power distribution terminal point number basic information, and a microservice calling request.

[0054] The background service end is configured to perform verification according to the fault indicator information, the power distribution terminal point number basic information, and pre-established parameter templates and point number templates, and if the verification is passed, to call the microservice to perform corresponding steps according to the microservice calling request.

[0055] The microservice calling request includes a fault indicator model creation calling request, and the microservice is called to establish a corresponding fault indicator model and generate corresponding power distribution terminal information and power distribution terminal point number information.

[0056] In specific embodiments, the interaction process between the user WEB end and the background service end is as follows:

[0057] The microservice caller fills in the fault indicator information and the power distribution terminal point number basic information.

[0058] The microservice provider performs verification according to the fault indicator information, the power distribution terminal point number basic information, and pre-established parameter templates and point number templates, and if the verification is passed, the microservice provider establishes a corresponding fault indicator model and generates corresponding power distribution terminal information and power distribution terminal point number information according to the microservice calling request for creating the fault indicator model sent by the microservice caller by clicking the new button to create the fault indicator model.

[0059] After the fault indicator model is created, a corresponding fault indicator model identifier is generated on the user WEB end page.

[0060] The microservice caller can send an upload device encryption certificate calling request, a data monitoring calling request, and a terminal access debugging calling request to the microservice provider by clicking the created fault indicator model identifier to upload the device encryption certificate, perform data monitoring, and perform terminal access debugging.

[0061] For the microservice provider, the microservice calling request of the microservice calling party is acquired, and corresponding background service is called according to the microservice calling request. The microservice calling request includes a fault indicator model creation calling request, a power distribution terminal point number generation calling request, a batch modeling point creation calling request, an equipment encryption certificate uploading calling request, a data monitoring calling request and a terminal access debugging calling request. The background service includes a fault indicator model creation service, a power distribution terminal point number generation service, a batch modeling point creation service, an equipment encryption certificate uploading service, a data monitoring service and a terminal access debugging service.

[0062] Embodiment 3

[0063] Based on the basis of embodiment 2, the microservice-based fault indicator whole-process access system provided in the embodiment is for the microservice calling party, and the microservice calling party sends a microservice calling request through a WEB terminal.

[0064] Specifically, the microservice calling party sends a fault indicator model creation calling request by clicking a new button to create a required fault indicator model, and generates a corresponding fault indicator model identifier on a page after the creation. The microservice calling party sends a power distribution terminal point number generation calling request to the microservice provider by clicking a fault indicator model identifier and a point number generation button to generate a required power distribution terminal point number. The microservice calling party sends a batch point modeling calling request to the microservice provider by clicking a related step button on a batch modeling point WEB display page to perform batch point modeling of a required equipment, and generates a corresponding fault indicator model identifier on a page after the processing. The microservice calling party sends an equipment encryption certificate uploading calling request, a data monitoring calling request and a terminal access debugging calling request to the microservice provider by clicking a created fault indicator model identifier to perform equipment encryption certificate uploading, data monitoring and terminal access debugging of the equipment.

[0065] For the microservice provider, the microservice calling request of the microservice calling party is acquired, and corresponding background service is called according to the microservice calling request. The microservice calling request includes a fault indicator model creation calling request, a power distribution terminal point number generation calling request, a batch modeling point creation calling request, an equipment encryption certificate uploading calling request, a data monitoring calling request and a terminal access debugging calling request. The background service includes a fault indicator model creation service, a power distribution terminal point number generation service, a batch modeling point creation service, an equipment encryption certificate uploading service, a data monitoring service and a terminal access debugging service.

[0066] In combination with Figure 2 , Figure 3 The processing process of creating a fault indicator model is described.

[0067] The user selects the feeder and "fault indicator" node on the navigation tree of the fault indicator model ("fault indicator model" same as "device model" in the drawing) WEB display page, and the background server returns the node model (i.e. "fault indicator model") information. The user clicks the add button, fills in the fault indicator model basic information, including indicator name, corresponding belonging feeder PMS_ID. The background server creates a fault indicator model according to the user input information at the same time in the real-time library and the commercial library, generates a unique and unchangeable fault indicator ID number (i.e. the device ID shown in the drawing).

[0068] For the fault indicator model that needs to be deleted or modified, the user selects the device node on the navigation tree of the fault indicator model WEB display page, and the background server returns the node model information. The user clicks the delete button, and the background server deletes the fault indicator model in the real-time library and the commercial library at the same time; the user clicks the modify button, fills in the fault indicator model basic information, including indicator name, corresponding belonging feeder PMS_ID, and the background server modifies the fault indicator model in the real-time library and the commercial library at the same time according to the user input information.

[0069] In combination Figure 4 The processing process of generating the distribution terminal point number is described:

[0070] The user selects the new medium-voltage distribution terminal point number template on the distribution terminal point number WEB display page, configures the point number of the remote signaling, remote measurement, custom remote signaling, and custom remote measurement of the point number template of the distribution terminal, and the table number, domain number, starting point number, and offset of each point number; selects the new medium-voltage distribution terminal parameter template, configures the generated terminal information, including the distribution network terminal table, distribution network channel table, distribution network communication terminal table, distribution network Iec101 protocol table, distribution network Iec104 protocol table, low-voltage terminal table, low-voltage channel table, low-voltage communication terminal table, low-voltage Iec101 protocol table, and low-voltage Iec104 protocol table. The user clicks the device node on the navigation tree of the distribution terminal point number WEB display page, fills in the point number basic information (including medium-voltage terminal address, port number, belonging manufacturer, point number template, parameter template, RTU address) of the device that needs to generate the point number, the already created point number template and parameter template, and clicks the point number generation button. The background server checks the filled point number basic information, mainly including that the filled information cannot be empty, the port number cannot exceed the range, and the combination of the port number and RTU address cannot be repeated. If the background check is correct, the distribution terminal point number is generated and written into the real-time library and the commercial library, and the WEB end progress bar timely displays the point number generation progress. If the background check is not passed, an error is prompted, the user clicks the distribution terminal point number query, inputs the terminal name or IP, the background server returns the corresponding terminal point number information of the query, the user clicks the clear point number button, the background deletes the point number information of the corresponding terminal, and the user rewrites the point number basic information and clicks the point number generation button.

[0071] In combination Figure 5 The process of handling the batch modeling point building is described as follows:

[0072] The user downloads the template table file on the batch modeling point building WEB display page, fills in the fault indicator information and power distribution terminal point number basic information, and clicks the upload button to upload the table file. The background server obtains the modeling and point number information file uploaded by the user, and caches the file data in the server. The user clicks the verification button, the modeling button, the point number button, and the re-building failed point number button in turn, and the background server reads the cached file data in turn to perform verification, modeling, point building, and re-point building on the data that fails in point building, and returns the result of each step to the WEB display page for display.

[0073] In combination Figure 6 The process of handling the uploaded device encryption certificate is described as follows:

[0074] The user selects the fault indicator node on the navigation tree of the device encryption certificate upload WEB display page, clicks the encryption certificate upload button, and the background server obtains the fault indicator id according to the device node, obtains the corresponding channel number and certificate upload situation according to the fault indicator id, and displays the information obtained by the background in a pop-up window. The user selects the certificate file and server address in the pop-up window, and clicks the start upload button, and the background server uploads the certificate file to the server address configured by the user.

[0075] In the specific embodiment, in combination Figure 7 , the user selects the device node on the navigation tree of the data monitoring WEB display page, and the background server starts to obtain the online state, telemetry data, remote signaling data, and measurement point telemetry data of the device, and refreshes and displays the data on the WEB display page in a timely manner.

[0076] In combination Figure 8 , the user selects the fault indicator node on the navigation tree of the terminal access debugging WEB display page, and the background server starts to obtain the terminal online state, remote signaling, telemetry, remote pulse, event occurrence time, measurement point name, type, point number, and data change process of the device, and refreshes and displays the fault indicator online state on the WEB display page in a timely manner, and real-time displays the remote signaling, telemetry, remote pulse, event occurrence time, measurement point name, type, point number, and data change process.

[0077] The user clicks the adjustment terminal operation state button, and the background server provides services of adjusting maintenance fault indicator debugging time, maintenance operation state, uploading operation proof file, etc. The user selects a navigation tree area, and the background server provides information of all devices in the area. The user clicks the export and operation proof viewing button, and the background server provides services of exporting all device information currently counted into a table, viewing and downloading the operation proof file of the device.

[0078] Those skilled in the art will appreciate that embodiments of the application can be provided as methods, systems, or computer program products. Accordingly, the application can be embodied in the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the application can be embodied in the form of a computer program product on one or more computer readable storage media (including, but not limited to, disk memory, CD-ROMs, optical storage media, etc.) having computer usable program code embodied thereon.

[0079] The application is described with reference to flowcharts according to the methods, devices (systems), and computer program products of embodiments of the application. It should be understood that each flow in the flowcharts can be implemented by computer program instructions. These computer program instructions can be provided to a computer, so that the computer executes the instructions to produce an action for implementing the functions specified in one flow or multiple flows in the flowcharts.

[0080] These computer program instructions can also be stored in a computer readable storage medium, which can guide the computer, so that the instructions stored in the computer readable storage medium produce an article of manufacture including instruction means, which implement the functions specified in one flow or multiple flows in the flowcharts. Figure 1

[0081] These computer program instructions can also be loaded into a computer, so that the computer executes a series of operation steps to complete the processing, so that the instructions executed by the computer provide steps for implementing the functions specified in one flow or multiple flows in the flowcharts. Figure 1

[0082] The above only describes the preferred embodiments of the application. It should be noted that for those skilled in the art, without departing from the technical principles of the application, a number of improvements and modifications can be made, which should be considered as the protection scope of the application.​​

Claims

1. A method for full-process access of a micro-service-based fault indicator, characterized in that, The method comprises the following steps: Obtaining fault indicator information and power distribution terminal point number basic information that need to be accessed; According to the fault indicator information, the power distribution terminal point number basic information, and a pre-established parameter template and a point number template, verification is performed; If the verification is passed, a microservice is called according to a microservice calling request to execute corresponding steps; The microservice calling request comprises a fault indicator model creation calling request, and the microservice is called to establish a corresponding fault indicator model and generate corresponding power distribution terminal information and power distribution terminal point number information; The fault indicator information comprises name information and organizational relationship of the fault indicator; The corresponding fault indicator model is established, which comprises the following steps: according to the name information, the organizational relationship and the corresponding belonging feeder PMS_ID of the fault indicator, a fault indicator model is created or maintained in a real-time library and / or a commercial library, including adding, modifying and deleting the fault indicator model, and a unique and unchangeable fault indicator ID is generated when the fault indicator model is added; wherein the organizational relationship is an organizational hierarchical relationship of the fault indicator corresponding to province-city-district-power supply bureau-station-feeder-fault indicator; A selected fault indicator is downloaded to download corresponding commissioning certificate files, display basic information and real-time messages, and adjust the commissioning state of the corresponding power distribution terminal. 2.The micro-service based fault indicator end-to-end access method according to claim 1, wherein, The microservice calling request further comprises an encrypted certificate uploading calling request, and the microservice is called to upload the encrypted certificate to a specified server address according to the selected fault indicator ID, the corresponding channel number, the encrypted certificate corresponding to the channel number and the stored server address. 3.The microservice-based fault indicator end-to-end access method according to claim 1, wherein, The microservice calling request further comprises a data monitoring calling request, and the microservice is called to monitor and access the fault indicator by using the power distribution terminal information and the power distribution terminal point number information. 4.The micro-service based fault indicator end-to-end access method according to claim 1, wherein, The parameter template is used to guide the generation of the power distribution terminal information, and the point number template is used to guide the generation of the power distribution terminal point number information.

5. The microservice-based fault indicator end-to-end access method according to claim 1, characterized in that, The power distribution terminal point number basic information comprises a power distribution terminal address, a port number, a manufacturer, a power distribution terminal point number template name, a parameter template name and an RTU address.

6. The microservice-based fault indicator end-to-end access method according to claim 1, characterized in that, The power distribution terminal information comprises a terminal ID, a channel ID, a channel number, a server address and a corresponding fault indicator ID; and the power distribution terminal point number information comprises remote signaling, remote measurement, custom remote signaling and custom remote measurement point number information that the fault indicator needs to access, and a corresponding channel ID.

7. A microservice-based fault indicator end-to-end access system, characterized in that, The method comprises the following steps: A user WEB terminal and a background service terminal are provided; The user WEB terminal is used to obtain fault indicator information, power distribution terminal point number basic information and microservice calling requests that need to be accessed; The background service terminal is used to perform verification according to the fault indicator information, the power distribution terminal point number basic information and a pre-established parameter template and a point number template; If the verification is passed, a microservice is called according to a microservice calling request to execute corresponding steps; The microservice calling request comprises a fault indicator model creation calling request, and the microservice is called to establish a corresponding fault indicator model and generate corresponding power distribution terminal information and power distribution terminal point number information; The user WEB terminal is further used to select a parameter template and a point number template; and The background server is used for establishing corresponding fault indicator models in real-time library and commercial library and generating corresponding power distribution terminal information and power distribution terminal point information through the port number and RTU address bound to the fault indicator needing to be accessed according to the fault indicator information, power distribution terminal point number basic information and selected parameter template and point number template. The user WEB end is also used for selecting a fault indicator, downloading corresponding commissioning certificate files, displaying basic information and real-time messages and adjusting a commissioning state of the corresponding power distribution terminal.

8. The microservice-based fault indicator end-to-end access system according to claim 7, characterized in that: The background server is also used for batch verification, and batch creation of fault indicator models if the verification is passed.

9. The microservice-based fault indicator end-to-end access system of claim 7, wherein: The user WEB end is also used for selecting a fault indicator id number, corresponding channel numbers and encrypted certificates corresponding to the channel numbers and stored server addresses, so that the background server uploads the encrypted certificates to the specified server addresses.

Images