Intelligent substation configuration file management method and system, medium and terminal

Abstract

The invention discloses an intelligent substation configuration file management method and system, a medium and a terminal, and the method comprises the steps: generating an access request when a user side accesses a system function of an intelligent substation, obtaining JWT information from a request header of the access request through an aspect layer created by an AOP architecture, then analyzing the JWT information, and sending the JWT information to a server; obtaining user registration information, an accessible interface list corresponding to the user side and an interface address of the request path; based on the user registration information, judging whether a user using the user side is registered or not; and if the user using the user side is registered and the accessible interface list corresponding to the user side contains the interface address of the request path, forwarding the access request to the MVC architecture for logic processing through the entry point configured by the aspect layer, so that the user side performs full-stage management and control on the configuration file through the MVC architecture. According to the invention, the management security is ensured by verifying the security of the user initiating the request and the interface address of the request path.

Description

Technical Field

[0001] The present invention relates to the field of configuration file management, and in particular to a configuration file management method, system, medium and terminal for a smart substation. Background Art

[0002] Existing intelligent station configuration file management and control technologies usually use technologies such as physical isolation of configuration files, access control lists (ACLs) and encrypted transmission. Physical isolation refers to isolating the network environment where configuration files are stored from the external network environment by physical means to prevent unauthorized access and data leakage, thereby avoiding the risk of intrusion or information leakage. ACL refers to an important security mechanism in computer networks, which is used to limit the access rights of users, processes or devices in the network. ACL is a list of instructions for router and switch interfaces, which is used to control the data packets entering and leaving the port. It can filter data packets on the interface according to the set conditions, allowing them to pass or discard them, thereby achieving access control to network resources. Encrypted transmission refers to the process of converting plaintext data into ciphertext data using encryption technology when user data is transmitted online, in order to prevent data from being stolen, tampered with and forged, and decrypting and restoring it at the receiving end.

[0003] Existing configuration file security control methods often rely on technologies such as physical isolation, ACL, and encrypted transmission, but these methods often have limitations. Physical isolation cannot prevent illegal operations by internal personnel, and the maintenance and management of ACL is complex and prone to errors. In addition, although encrypted transmission can protect the security of data during transmission, it is not enough to protect the security of configuration files during storage and access. At the same time, the security logic of smart substation configuration files is highly coupled with the business logic, making the system complex and difficult to maintain. Summary of the invention

[0004] The embodiments of the present invention provide a method, system, medium and terminal for managing configuration files of a smart substation, which pre-verify the identity of the user who initiates the access request and the security of the interface address of the request path, and prevent internal personnel from directly accessing the configuration file, so as to ensure the security of the configuration file management of the smart substation.

[0005] In order to solve the above technical problems, an embodiment of the present invention provides a method for managing a configuration file of a smart substation, comprising:

[0006] When the user terminal accesses the system function of the smart substation, an access request is generated, and the JWT information is obtained from the request header of the access request through the aspect layer, and then the JWT information is parsed to obtain the user registration information, the list of accessible interfaces corresponding to the user terminal, and the interface address of the request path; wherein the aspect layer is created using the AOP architecture;

[0007] Based on the user registration information, determining whether the user using the user terminal has registered;

[0008] If the user using the user terminal has registered and the list of accessible interfaces corresponding to the user terminal contains the interface address of the request path, the access request is forwarded to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer, so that the user terminal can perform full-stage control of the configuration file through the MVC architecture.

[0009] In implementing the embodiment of the present invention, when the user terminal accesses the system function of the smart substation, an access request is generated, and the JWT information is obtained from the request header of the access request by utilizing the aspect layer created by the AOP architecture, and then the JWT information is parsed to obtain the user registration information, the list of accessible interfaces corresponding to the user terminal, and the interface address of the request path, and based on the user registration information, it is determined whether the user using the user terminal has been registered. If the user using the user terminal has been registered and the list of accessible interfaces corresponding to the user terminal contains the interface address of the request path, indicating that the user requesting access is an internal personnel and this interface address complies with the specification or is safe, then the access request is forwarded to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer, so that the user terminal can perform full-stage management and control of the configuration file through the MVC architecture. Through the above means, users can access the MVC architecture and perform full-stage control of configuration files, that is, the combination of AOP and MVC is used to achieve secure management of configuration files, prevent internal personnel from directly accessing configuration files, and thus improve the security of configuration files. In addition, before forwarding the access request, it is first verified whether the user is a registered user and whether the interface address of the request path is the accessible interface corresponding to the user end, that is, the user requesting access has access rights and this interface address can be safely accessed. Therefore, under the premise of having access rights and the interface address to be accessed is safe, the configuration file is managed without the need for the network administrator to add access routes to the configuration file list separately, nor to check and maintain ACL, so as to solve the problems that may cause network congestion and data delay during peak hours, thereby improving the stability and reliability of the system. In addition, the aspect layer created using the AOP (aspect-oriented programming) architecture can separate non-business logic (such as security verification, logging, etc.) from business logic, thereby reducing code redundancy and improving the system's response speed and execution efficiency.

[0010] As a preferred solution, if the user using the client has registered and the list of accessible interfaces corresponding to the client contains the interface address of the request path, the access request is forwarded to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer, so that the client can perform full-stage control of the configuration file through the MVC architecture, specifically:

[0011] If the user using the client has registered and the list of accessible interfaces corresponding to the client contains the interface address of the request path, the access request is forwarded to the model layer, the view layer and the control layer in the MVC architecture respectively through the entry point pre-configured by the aspect layer, so that the model layer processes the management data and business logic of the configuration file, the view layer displays and maintains the relevant information of the configuration file, and the control layer processes various requests between the view layer and the model layer;

[0012] In response to the user terminal accessing the view layer, the view layer is used to comprehensively control each stage of the configuration file to achieve security management of the configuration file;

[0013] The various stages of the configuration file include generation, modification, review, storage, distribution, backup and recovery of the configuration file.

[0014] A preferred solution for implementing the embodiment of the present invention is that if the user using the user end has registered and the list of accessible interfaces corresponding to the user end contains the interface address of the request path, the access request is forwarded to the model layer, view layer and control layer in the MVC architecture respectively through the entry point pre-configured by the aspect layer, so that the model layer processes the management data and business logic of the configuration file, the view layer displays and maintains the relevant information of the configuration file, and the control layer processes various requests between the view layer and the model layer. That is, the aspect layer acts on the model layer, view layer and control layer in the MVC architecture by configuring the entry point to forward, process and respond to the request, thereby realizing the corresponding operation log recording, access permission management, and data encryption and decryption processing. It can also reduce code maintenance, effectively organize and optimize the program structure, so that each module can focus more on its core functions.

[0015] As a preferred solution, the view layer is also used to record and display in real time the operation logs generated during the maintenance of the configuration files.

[0016] The preferred solution of the embodiment of the present invention can facilitate tracking the change history of the configuration file and troubleshooting by recording and displaying the operation logs generated during the maintenance of the configuration file in real time.

[0017] As a preferred solution, judging whether the user using the user terminal has registered based on the user registration information is specifically:

[0018] If the user registration information contains a registration mark, it is determined that the user using the user terminal has registered;

[0019] If the registration mark number does not exist in the user registration information, it is determined that the user using the user terminal is not registered;

[0020] The registration identification number is generated by the system of the smart substation when the user successfully registers in the system of the smart substation.

[0021] According to the preferred solution of the embodiment of the present invention, by checking whether there is a registration mark number in the user registration information, the system can quickly determine whether the user has registered. The above mechanism simplifies the judgment process, reduces unnecessary calculations and data processing, and thus improves the response speed of the system.

[0022] As a preferred solution, if the user using the client has registered and the list of accessible interfaces corresponding to the client includes the interface address of the request path, the access request is forwarded to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer, so that the client performs full-stage control of the configuration file through the MVC architecture, and the method further includes:

[0023] The interface address of the request path is matched with the entry point pre-configured by the aspect layer.

[0024] A preferred solution for implementing the embodiment of the present invention is to match the interface address of the request path with the entry point pre-configured by the aspect layer before forwarding the access request to the MVC architecture, so as to ensure that the entry point pre-configured by the aspect layer can act on each layer of the MVC architecture, and the aspect layer is created using the AOP architecture. By utilizing the AOP technology, multiple cross-cutting concerns such as logging, transaction management, and security control can be dynamically woven into the three layers of the MVC architecture, thereby enhancing the flexibility and scalability of the system, thereby providing developers with a more efficient and reliable development environment, and reducing code coupling, making the system structure clearer, and improving system maintainability.

[0025] As a preferred solution, after forwarding the access request to the MVC architecture for logic processing through the entry point pre-configured by the aspect layer so that the user end performs full-stage control of the configuration file through the MVC architecture, it also includes:

[0026] The logic processing data and the full-stage control data are sent to the aspect layer, and then the received data is fed back to the front-end page through the aspect layer.

[0027] According to the preferred solution of the embodiment of the present invention, after the logic processing and full-stage control are completed, the relevant data is fed back to the front-end page through the aspect layer, so that the user can obtain the processing results and status information in real time. This real-time data feedback mechanism improves the user's operating experience.

[0028] In order to solve the same technical problem, an embodiment of the present invention further provides a smart substation configuration file management system, including:

[0029] The parsing module is used to generate an access request when the user terminal accesses the system function of the smart substation, and obtain JWT information from the request header of the access request through the aspect layer, and then parse the JWT information to obtain user registration information, the list of accessible interfaces corresponding to the user terminal, and the interface address of the request path; wherein the aspect layer is created using the AOP architecture;

[0030] A judgment module, used for judging whether the user using the user terminal has been registered based on the user registration information;

[0031] A forwarding control module is used to forward the access request to the MVC architecture for logical processing through an entry point pre-configured by the aspect layer if the user using the user terminal has registered and the interface address of the request path is included in the list of accessible interfaces corresponding to the user terminal, so that the user terminal can perform full-stage control of the configuration file through the MVC architecture.

[0032] As a preferred solution, the forwarding control module specifically includes:

[0033] a forwarding unit, configured to forward the access request to the model layer, the view layer and the control layer in the MVC architecture respectively through the entry point preconfigured by the aspect layer if the user using the user terminal has registered and the list of accessible interfaces corresponding to the user terminal contains the interface address of the request path, so that the model layer processes the management data and business logic of the configuration file, the view layer displays and maintains the relevant information of the configuration file, and the control layer processes various requests between the view layer and the model layer;

[0034] The phased control unit is used to respond to the user terminal's access to the view layer, and use the view layer to comprehensively control each stage of the configuration file to achieve secure management of the configuration file; wherein the various stages of the configuration file include generation, modification, review, storage, distribution, backup and recovery of the configuration file.

[0035] In order to solve the same technical problem, the present invention also provides a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the smart substation configuration file management method.

[0036] In order to solve the same technical problem, the present invention also provides a terminal, including a processor, a memory and a computer program stored in the memory; wherein the computer program can be executed by the processor to implement the smart substation configuration file management method. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 : A flow chart of a method for managing configuration files of a smart substation provided in Embodiment 1 of the present invention;

[0038] Figure 2 : A structural diagram of a smart substation configuration file management system provided in Example 1 of the present invention. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions 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.

[0040] Embodiment one:

[0041] Please refer to Figure 1 , is a smart substation configuration file management method provided by an embodiment of the present invention, the method includes steps S1 to S3, each step is specifically as follows:

[0042] Step S1, when the user terminal accesses the system function of the smart substation, an access request is generated, and the JWT information is obtained from the request header of the access request through the aspect layer, and then the JWT information is parsed to obtain the user registration information, the list of accessible interfaces corresponding to the user terminal, and the interface address of the request path.

[0043] In this embodiment, when a user accesses a system function, the AOP architecture is used to identify the JWT information in the request header in the access request, and the registration information of the user who initiates the access request is obtained by parsing the JWT information. The user interface permission configuration table includes information such as user registration information and which interface paths the user can access, which is used to determine whether the user who initiates the access request has been registered and the access rights of this interface address.

[0044] Among them, the aspect layer is created using the AOP architecture.

[0045] In this embodiment, a Springboot framework is built, and an MVC architecture is built under the Springboot framework. An aspect layer (aspect layer) is also created through the AOP architecture. Among them, the MVC architecture includes the creation of a model layer (Model layer), a view layer (View layer) and a control layer (Controller layer). The Model layer is mainly used to process the management data and business logic of the configuration files in the application, and acts on the database and server for data and file storage. The View layer is mainly used to display and maintain configuration file related information. The Controller layer is mainly used for various request processing between the View layer and the Model layer. Through the aspect layer, AOP and MVC are cleverly combined. This layer is responsible for managing and unifying the cross-cutting concerns that are common but scattered between the three layers of MVC, such as logging, transaction management, security control and other cross-cutting concerns.

[0046] Step S2: Based on the user registration information, determine whether the user using the user terminal has registered.

[0047] As a preferred solution, step S2 includes step S21 to step S22, and each step is specifically as follows:

[0048] Step S21: If there is a registration mark number in the user registration information, it is determined that the user using the user terminal has been registered.

[0049] In step S22, if the registration mark number does not exist in the user registration information, it is determined that the user using the user terminal is not registered.

[0050] The registration mark number is generated by the system server of the smart substation when the user successfully registers on the system server of the smart substation.

[0051] As a preferred solution, before executing step S2, step S01 is further included, and the specific details of the step are as follows:

[0052] Step S01, matching the interface address of the request path with the entry point pre-configured by the aspect layer.

[0053] In this embodiment, an Aop.class class is created, which acts as the aspect layer function. Aop.class acts on the Model layer, View layer, and Controller layer by configuring the entry point. Through the entry point, the request is forwarded, processed, and responded to, and the corresponding operation log record, access permission management, and data encryption and decryption processing are realized. It can also reduce code maintenance, effectively organize and optimize the program structure, so that each module can focus more on its core functions.

[0054] It should be noted that for the configuration rules, the access address is identified and determined through the @Pointacut annotation and its value attribute execution. The execution configuration needs to enter the request path of the Controller layer or Model layer. The entry point must be the relative path address of the logical file. The request path is such as: *com.microscd.controller.*; where * represents any character. When the server receives the access request, it will match the interface address of the request path with the configured entry point, so that the entry point can forward, process and respond to the request.

[0055] Specifically, when the user operates the system interface function, such as accessing the smart substation configuration file management list, the system will send a request to the server. The request address format is usually: http: / / ip+port / getList. Depending on the specific publishing method, it is not limited to the method of using only IP and port, and may be a domain name address. After the system server receives the request, it will first pass through the aspect layer created by the AOP architecture. The aspect layer processes the interface address getList of the request path, and judges whether this address is standardized or safe through the header in the request. After the judgment is passed, the request is forwarded to the MVC three-tier architecture. After logical processing, the data is sent to the aspect layer, and the aspect layer feeds the data back to the front-end page for response processing. Through the above operations, "forwarding, processing, and responding to requests through entry points" is realized.

[0056] Step S3, if the user using the client has registered and the list of accessible interfaces corresponding to the client contains the interface address of the request path, the access request is forwarded to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer, so that the client can perform full-stage management and control of the configuration file through the MVC architecture.

[0057] As a preferred solution, step S3 includes step S31 to step S32, and each step is specifically as follows:

[0058] Step S31, if the user using the client has registered and the list of accessible interfaces corresponding to the client contains the interface address of the request path, the access request is forwarded to the model layer, view layer and control layer in the MVC architecture through the entry point pre-configured by the aspect layer, so that the model layer processes the management data and business logic of the configuration file, the view layer displays and maintains the relevant information of the configuration file, and the control layer processes various requests between the view layer and the model layer.

[0059] Step S32, responding to the user's access to the view layer, using the view layer to comprehensively control each stage of the configuration file to achieve secure management of the configuration file.

[0060] Among them, the various stages of the configuration file include but are not limited to the generation, modification, review, storage, distribution, backup and recovery of the configuration file.

[0061] In this embodiment, the program is released through the combination of the MVC architecture and the AOP aspect layer. By accessing the View layer, users can comprehensively control the generation, modification, review, storage, distribution, backup, and recovery of configuration files, thereby achieving secure management of configuration files.

[0062] As a preferred solution, the view layer is also used to record and display the operation logs generated during the maintenance of the configuration files in real time, so as to track the change history of the configuration files and serve as a basis for troubleshooting when a failure occurs.

[0063] As a preferred solution, after executing step S3, step S4 is further included, and the specific details of the step are as follows:

[0064] Step S4, sending the logic processing data and the full-stage control data to the aspect layer, and then through the aspect layer, feeding back the received data to the front-end page for response processing.

[0065] Please refer to Figure 2 , is a schematic diagram of the structure of a smart substation configuration file management system provided by an embodiment of the present invention, the system includes a parsing module M1, a judgment module M2 and a forwarding control module M3, and the specific details of each module are as follows:

[0066] The parsing module M1 is used to generate an access request when the user accesses the system function of the smart substation, and obtain the JWT information from the request header of the access request through the aspect layer, and then parse the JWT information to obtain the user registration information, the list of accessible interfaces corresponding to the user, and the interface address of the request path; wherein the aspect layer is created using the AOP architecture;

[0067] The judging module M2 is used to judge whether the user using the user terminal has registered based on the user registration information;

[0068] The forwarding control module M3 is used to forward the access request to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer if the user using the user terminal has registered and the interface address of the request path is included in the list of accessible interfaces corresponding to the user terminal, so that the user terminal can perform full-stage control of the configuration file through the MVC architecture.

[0069] As a preferred solution, the forwarding control module M3 specifically includes a forwarding unit 31 and a phased control unit 32, and the specific details of each unit are as follows:

[0070] The forwarding unit 31 is used to forward the access request to the model layer, the view layer and the control layer in the MVC architecture respectively through the entry point pre-configured by the aspect layer if the user using the client has registered and the interface address of the request path is included in the list of accessible interfaces corresponding to the client, so that the model layer processes the management data and business logic of the configuration file, the view layer displays and maintains the relevant information of the configuration file, and the control layer processes various requests between the view layer and the model layer;

[0071] The phased control unit 32 is used to respond to the user's access to the view layer, and use the view layer to comprehensively control each stage of the configuration file to achieve secure management of the configuration file; wherein each stage of the configuration file includes generation, modification, review, storage, distribution, backup and recovery of the configuration file.

[0072] As a preferred solution, an intelligent substation configuration file management system provided in an embodiment of the present invention further includes a matching module M4 and a feedback module M5, and the specific details of each module are as follows:

[0073] The matching module M4 is used to forward the access request to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer if the user using the user terminal has registered and the interface address of the request path is included in the list of accessible interfaces corresponding to the user terminal, so that the interface address of the request path is matched with the entry point pre-configured by the aspect layer before the user terminal performs full-stage management of the configuration file through the MVC architecture.

[0074] Feedback module M5 is used to forward the access request to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer, so that the user end can perform full-stage control of the configuration file through the MVC architecture, and then send the logical processing data and full-stage control data to the aspect layer, and then feed back the received data to the front-end page through the aspect layer.

[0075] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0076] An embodiment of the present invention further provides a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute a smart substation configuration file management method described in embodiment 1.

[0077] An embodiment of the present invention further provides a terminal, including a processor, a memory, and a computer program stored in the memory; wherein the computer program can be executed by the processor to implement a smart substation configuration file management method described in Embodiment 1.

[0078] Preferably, the computer program can be divided into one or more modules / units (such as computer program, computer program), one or more modules / units are stored in the memory and executed by the processor to complete the present invention. One or more modules / units can be a series of computer program instruction segments that can complete specific functions, and the instruction segments are used to describe the execution process of the computer program in the terminal.

[0079] The processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor, or the processor can also be any conventional processor. The processor is the control center of the terminal, and various parts of the terminal are connected using various interfaces and lines.

[0080] The memory mainly includes a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function, etc., and the data storage area can store related data, etc. In addition, the memory can be a high-speed random access memory, or a non-volatile memory, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, and a flash card (Flash Card), etc., or the memory can also be other volatile solid-state storage devices.

[0081] It should be noted that the above-mentioned terminal may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that the above-mentioned terminal is merely an example and does not constitute a limitation on the terminal. It may include more or fewer components, or a combination of certain components, or different components.

[0082] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0083] The present invention provides a configuration file management method, system, medium and terminal for a smart substation. When a user terminal accesses a system function of a smart substation, an access request is generated, and JWT information is obtained from a request header of the access request by utilizing an aspect layer created by an AOP architecture. Then, the JWT information is parsed to obtain user registration information, a list of accessible interfaces corresponding to the user terminal, and an interface address of a request path. Based on the user registration information, it is determined whether the user using the user terminal has been registered. If the user using the user terminal has been registered and the list of accessible interfaces corresponding to the user terminal contains the interface address of the request path, indicating that the user requesting access is an internal person and the interface address complies with the specification or is safe, the access request is forwarded to an MVC architecture for logic processing through an entry point pre-configured by the aspect layer, so that the user terminal performs full-stage management and control of the configuration file through the MVC architecture. Through the above means, users can access the MVC architecture and perform full-stage control of configuration files, that is, the combination of AOP and MVC is used to achieve secure management of configuration files, prevent internal personnel from directly accessing configuration files, and thus improve the security of configuration files. In addition, before forwarding the access request, it is first verified whether the user is a registered user and whether the interface address of the request path is the accessible interface corresponding to the user end, that is, the user requesting access has access rights and this interface address can be safely accessed. Therefore, under the premise of having access rights and the interface address to be accessed is safe, the configuration file is managed without the need for the network administrator to add access routes to the configuration file list separately, nor to check and maintain ACL, so as to solve the problems that may cause network congestion and data delay during peak hours, thereby improving the stability and reliability of the system. In addition, the aspect layer created using the AOP (aspect-oriented programming) architecture can separate non-business logic (such as security verification, logging, etc.) from business logic, thereby reducing code redundancy and improving the system's response speed and execution efficiency.

[0084] The specific embodiments described above further illustrate the purpose, technical solutions and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. It is particularly pointed out that for those skilled in the art, any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for managing configuration files of a smart substation, characterized in that: include: When the user terminal accesses the system function of the smart substation, an access request is generated, and the JWT information is obtained from the request header of the access request through the aspect layer, and then the JWT information is parsed to obtain the user registration information, the list of accessible interfaces corresponding to the user terminal, and the interface address of the request path; wherein the aspect layer is created using the AOP architecture; Based on the user registration information, determining whether the user using the user terminal has registered; If the user using the user terminal has registered and the list of accessible interfaces corresponding to the user terminal contains the interface address of the request path, the access request is forwarded to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer, so that the user terminal can perform full-stage control of the configuration file through the MVC architecture.

2. A method for managing configuration files of a smart substation according to claim 1, characterized in that: If the user using the client has registered and the list of accessible interfaces corresponding to the client contains the interface address of the request path, the access request is forwarded to the MVC architecture for logical processing through the entry point pre-configured by the aspect layer, so that the client can perform full-stage control of the configuration file through the MVC architecture, specifically: If the user using the client has registered and the list of accessible interfaces corresponding to the client contains the interface address of the request path, the access request is forwarded to the model layer, the view layer and the control layer in the MVC architecture respectively through the entry point pre-configured by the aspect layer, so that the model layer processes the management data and business logic of the configuration file, the view layer displays and maintains the relevant information of the configuration file, and the control layer processes various requests between the view layer and the model layer; In response to the user terminal accessing the view layer, the view layer is used to comprehensively control each stage of the configuration file to achieve secure management of the configuration file; The various stages of the configuration file include generation, modification, review, storage, distribution, backup and recovery of the configuration file.

3. A method for managing configuration files of a smart substation according to claim 2, characterized in that: The view layer is also used to record and display the operation logs generated during the maintenance of the configuration files in real time.

4. A method for managing configuration files of a smart substation according to claim 1, characterized in that: The determining, based on the user registration information, whether the user using the user terminal has been registered is specifically: If the user registration information contains a registration mark, it is determined that the user using the user terminal has registered; If the registration mark number does not exist in the user registration information, it is determined that the user using the user terminal is not registered; The registration identification number is generated by the system of the smart substation when the user successfully registers in the system of the smart substation.

5. A method for managing configuration files of a smart substation according to claim 1, characterized in that: Before the method of forwarding the access request to the MVC architecture for logic processing through the entry point pre-configured by the aspect layer if the user using the client has registered and the interface address of the request path is included in the accessible interface list corresponding to the client, so that the client can perform full-stage control of the configuration file through the MVC architecture, it also includes: The interface address of the request path is matched with the entry point pre-configured by the aspect layer.

6. A method for managing configuration files of a smart substation according to claim 1, characterized in that: After forwarding the access request to the MVC framework for logic processing through the entry point pre-configured by the aspect layer so that the user end performs full-stage control of the configuration file through the MVC framework, it also includes: The logic processing data and the full-stage control data are sent to the aspect layer, and then the received data is fed back to the front-end page through the aspect layer.

7. A smart substation configuration file management system, characterized in that: include: The parsing module is used to generate an access request when the user terminal accesses the system function of the smart substation, and obtain JWT information from the request header of the access request through the aspect layer, and then parse the JWT information to obtain user registration information, the list of accessible interfaces corresponding to the user terminal, and the interface address of the request path; wherein the aspect layer is created using the AOP architecture; A judgment module, used for judging whether the user using the user terminal has been registered based on the user registration information; A forwarding control module is used to forward the access request to the MVC architecture for logical processing through an entry point pre-configured by the aspect layer if the user using the user terminal has registered and the interface address of the request path is included in the list of accessible interfaces corresponding to the user terminal, so that the user terminal can perform full-stage control of the configuration file through the MVC architecture.

8. The intelligent substation configuration file management system according to claim 7, characterized in that: The forwarding control module specifically includes: a forwarding unit, configured to forward the access request to the model layer, the view layer and the control layer in the MVC architecture respectively through the entry point preconfigured by the aspect layer if the user using the user terminal has registered and the list of accessible interfaces corresponding to the user terminal contains the interface address of the request path, so that the model layer processes the management data and business logic of the configuration file, the view layer displays and maintains the relevant information of the configuration file, and the control layer processes various requests between the view layer and the model layer; The phased control unit is used to respond to the user terminal's access to the view layer, and use the view layer to comprehensively control each stage of the configuration file to achieve secure management of the configuration file; wherein the various stages of the configuration file include generation, modification, review, storage, distribution, backup and recovery of the configuration file.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program; wherein, when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute a smart substation configuration file management method as described in any one of claims 1 to 6.

10. A terminal, characterized in that: It comprises a processor, a memory and a computer program stored in the memory; wherein the computer program can be executed by the processor to implement a smart substation configuration file management method as described in any one of claims 1 to 6.

Images