An intelligent substation configuration file management method, system, medium and terminal

Abstract

The application discloses a kind of intelligent substation configuration file management method, system, medium and terminal, comprising: when user end accesses the system function of intelligent substation, generate access request, and obtain JWT information from the request header of access request by using the aspect layer created by AOP architecture, then parse JWT information, obtain user registration information, the accessible interface list of user end corresponding and the interface address of request path;Based on user registration information, judge whether the user using user end has been registered;If the user using user end has been registered and the interface address of request path is contained in the accessible interface list of user end corresponding, then by the point-in of aspect layer configuration, access request is forwarded to MVC architecture for logical processing, so that user end carries out whole stage management and control to configuration file by MVC architecture.The security of the user initiating the request and the interface address of the request path is verified to ensure management security.

Description

Technical Field

[0001] This invention relates to the field of configuration file management, and more particularly to a method, system, medium, and terminal for managing configuration files in intelligent substations. Background Technology

[0002] Existing intelligent station configuration file management technologies typically employ physical isolation of configuration files, Access Control Lists (ACLs), and encrypted transmission. Physical isolation refers to physically isolating the network environment storing configuration files from the external network environment to prevent unauthorized access and data leakage, thereby avoiding the risk of intrusion or information disclosure. ACLs are an important security mechanism in computer networks used to restrict access permissions for users, processes, or devices within the network. ACLs are instruction lists for router and switch interfaces, used to control data packets entering and leaving ports. They can filter data packets on the interface based on set conditions, allowing or discarding them, thus achieving access control over network resources. Encrypted transmission refers to the process of converting plaintext data into ciphertext data during network transmission to prevent data theft, tampering, and forgery, and then decrypting and restoring the data at the receiving end.

[0003] Existing configuration file security control methods often rely on technologies such as physical isolation, ACLs, and encrypted transmission, but these methods often have limitations. Physical isolation cannot prevent unauthorized operations by internal personnel, and ACLs are complex to maintain and manage and prone to errors. Furthermore, while encrypted transmission can protect the security of data transmission, it is insufficient to protect the security of configuration files during storage and access. In addition, the high degree of coupling between the configuration file security logic and business logic in smart substations leads to system complexity and difficulty in maintenance. Summary of the Invention

[0004] This invention provides a method, system, medium, and terminal for managing configuration files in smart substations. It pre-verifies the identity of the user initiating the access request and the security of the interface address of the request path, and prevents internal personnel from directly accessing the configuration files, thereby ensuring the security of configuration file management in smart substations.

[0005] To address the aforementioned technical problems, embodiments of the present invention provide a method for managing configuration files in intelligent substations, comprising:

[0006] When a user accesses the system functions of a smart substation, an access request is generated. The aspect layer then retrieves JWT information from the request header of the access request, parses the JWT information to obtain user registration information, a list of accessible interfaces corresponding to the user, and the interface address of the request path. The aspect layer is created using the AOP architecture.

[0007] Based on the user registration information, determine whether the user using the client has registered;

[0008] 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, then the access request is forwarded to the MVC architecture for logical processing through the pointcut pre-configured by the aspect layer, so that the client can perform full-stage control of the configuration file through the MVC architecture.

[0009] In implementing this embodiment of the invention, when a user terminal accesses the system functions of a smart substation, an access request is generated. The JWT information is obtained from the request header of the access request through the aspect layer created using the AOP architecture. The JWT information is then parsed to obtain user registration information, a list of accessible interfaces corresponding to the user terminal, and the interface address of the request path. Based on the user registration information, it is determined 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, it indicates that the user requesting access is an internal personnel and that this interface address conforms to specifications or security. Then, through a pre-configured pointcut by the aspect layer, the access request is forwarded to the MVC architecture for logical processing, enabling the user terminal to perform full-stage control of the configuration file through the MVC architecture. Through the above methods, users can manage configuration files at all stages by accessing the MVC architecture. This combines AOP (Aspect-Oriented Programming) with MVC to achieve secure configuration file management, preventing direct access by internal personnel and thus improving configuration file security. Furthermore, before forwarding access requests, it verifies whether the user is registered and whether the requested interface address is an accessible interface on the user's end. This ensures the requesting user has the necessary permissions and the interface address is secure, allowing configuration file management under the premise of access rights and secure interface address. This eliminates the need for network administrators to add access routes to the configuration file list or to check and maintain ACLs, thus mitigating potential network congestion and data latency during peak periods and improving system stability and reliability. In addition, the aspect layer created using AOP can separate non-business logic (such as security verification and logging) from business logic, reducing code redundancy and improving system response speed and execution efficiency.

[0010] As a preferred embodiment, 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, then the access request is forwarded to the MVC architecture for logical processing through a pointcut pre-configured by the aspect layer. This allows the client to perform full-stage control over 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, then through the pointcut pre-configured by the aspect layer, the access request is forwarded to the model layer, view layer, and controller layer in the MVC architecture, 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 controller layer processes various requests between the view layer and the model layer.

[0012] In response to the user's access to the view layer, the view layer is used to comprehensively manage each stage of the configuration file, thereby achieving secure management of the configuration file.

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

[0014] In a preferred embodiment of the present invention, if the user on the client has registered and the list of accessible interfaces corresponding to the client contains the interface address of the request path, then through the pointcut pre-configured by the aspect layer, the access request is forwarded to the model layer, view layer, and controller layer in the MVC architecture, respectively. This allows the model layer to process the management data and business logic of the configuration file, the view layer to display and maintain the relevant information of the configuration file, and the controller layer to process various requests between the view layer and the model layer. In other words, the aspect layer, by configuring pointcuts, acts on the model layer, view layer, and controller layer in the MVC architecture to forward, process, and respond to requests, thereby realizing corresponding operation log recording, access permission management, and data encryption / decryption processing. This also reduces code maintenance, effectively organizes and optimizes the program structure, and allows each module to focus more on its core functions.

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

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

[0017] As a preferred embodiment, determining whether a user using the client has registered based on the user registration information specifically involves:

[0018] If the user registration information contains a registration identifier, it is determined that the user using the client has registered.

[0019] If the user registration information does not contain a registration identifier, it is determined that the user using the client has not registered.

[0020] The registration identifier is generated by the smart substation system when the user successfully registers with the system.

[0021] In a preferred embodiment of the present invention, by checking whether a registration identifier exists in the user registration information, the system can quickly determine whether a user has registered. The above mechanism simplifies the judgment process, reduces unnecessary calculations and data processing, and thus improves the system's response speed.

[0022] As a preferred embodiment, before the step of forwarding the access request to the MVC architecture for logical processing through a pre-configured pointcut in the aspect layer, if the user using the client has registered and the accessible interface list corresponding to the client contains the interface address of the request path, so that the client can perform full-stage control of the configuration file through the MVC architecture, further includes:

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

[0024] In a preferred embodiment of the present invention, before forwarding the access request to the MVC architecture, the interface address of the request path is matched with the pointcut pre-configured by the aspect layer. This ensures that the pointcut pre-configured by the aspect layer can act on each layer of the MVC architecture. Furthermore, the aspect layer is created using the AOP architecture. By utilizing 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, enhancing the system's flexibility and scalability. This provides developers with a more efficient and reliable development environment, reduces code coupling, makes the system structure clearer, and improves system maintainability.

[0025] As a preferred embodiment, after forwarding the access request to the MVC architecture for logical processing through the pre-configured entry point of the aspect layer, so that the user terminal can perform full-stage control of the configuration file through the MVC architecture, the method further includes:

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

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

[0028] To address the same technical problem, embodiments of the present invention also provide an intelligent substation configuration file management system, comprising:

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

[0030] The judgment module is used to determine, based on the user registration information, whether the user using the client has registered;

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

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

[0033] The forwarding unit is configured to forward the access request to the model layer, view layer, and controller layer of the MVC architecture through a pre-configured entry point in the aspect layer if the user using the user terminal has registered and the accessible interface list corresponding to the user terminal contains the interface address of the request path. This allows the model layer to process the management data and business logic of the configuration file, the view layer to display and maintain the relevant information of the configuration file, and the controller layer to process various requests between the view layer and the model layer.

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

[0035] To address the same technical problem, the present invention also provides a computer-readable storage medium comprising a stored computer program; wherein, when the computer program is executed, it controls the device containing the computer-readable storage medium to execute the aforementioned intelligent substation configuration file management method.

[0036] To address 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 aforementioned intelligent substation configuration file management method. Attached Figure Description

[0037] Figure 1 : This is a flowchart illustrating a method for managing configuration files in an intelligent substation according to Embodiment 1 of the present invention;

[0038] Figure 2 This is a schematic diagram of the structure of an intelligent substation configuration file management system provided in Embodiment 1 of the present invention. Detailed Implementation

[0039] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0040] Example 1:

[0041] Please refer to Figure 1 This invention provides a method for managing configuration files in an intelligent substation, comprising steps S1 to S3, the specific details of which are as follows:

[0042] Step S1: When the user terminal accesses the system functions of the smart substation, an access request is generated. The JWT information is obtained from the request header of the access request through the aspect layer. 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 system functions, the AOP architecture is used to identify the JWT information in the request header of the access request. By parsing the JWT information, the registration information of the user who initiated the access request is obtained. The user interface permission configuration table contains information such as the user's registration information and which interface paths the user can access, which is used to determine whether the user who initiated the access request has been registered and the access permissions of this interface address.

[0044] The aspect layer is created using the AOP architecture.

[0045] In this embodiment, a Spring Boot framework is built, and an MVC architecture is constructed within it. An AOP (Aspect-Oriented Programming) layer is also created. The MVC architecture comprises a Model layer, a View layer, and a Controller layer. The Model layer primarily handles the management of configuration files and business logic within the application, and operates on the database and server for data and file storage. The View layer primarily displays and maintains configuration file-related information. The Controller layer handles various request processing between the View and Model layers. The Aspect layer cleverly combines AOP and MVC, managing and unifying the common but dispersed cross-cutting concerns across the three MVC layers, such as logging, transaction management, and security controls.

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

[0047] As a preferred embodiment, step S2 includes steps S21 to S22, each of which is detailed below:

[0048] Step S21: If the user registration information contains a registration identifier, it is determined that the user using the client has registered.

[0049] If the user registration information does not contain a registration identifier, then it is determined that the user using the client has not registered.

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

[0051] As a preferred embodiment, before performing step S2, step S01 is also included, which is as follows:

[0052] Step S01: Match the interface address of the request path with the pointcut pre-configured by the aspect layer.

[0053] In this embodiment, an Aop.class class is created, which serves as the aspect layer functionality. Aop.class operates on the Model, View, and Controller layers by configuring pointcuts. Through pointcuts, requests are forwarded, processed, and responses are handled, enabling corresponding operation logging, access control, and data encryption / decryption. This also reduces code maintenance, effectively organizes and optimizes the program structure, allowing each module to focus more on its core functionality.

[0054] It's important to note that the configuration rules use the `@Pointcut` annotation and its `value` attribute `execution` to identify and determine the accessed address. The `execution` configuration specifies the request path to the Controller or Model layer to be intercepted. The intercept point must be a relative path to the logic file, such as `*com.microscd.controller.*`, where `*` represents any character. When the server receives the access request, it matches the interface address of the request path with the configured intercept point, allowing that intercept point to forward, process, and respond to the request.

[0055] Specifically, when a user operates on the system interface, such as accessing the intelligent substation configuration file management list, the system sends a request to the server. The request address format is typically: http: / / ip+port / getList. However, depending on the publishing method, it may not be limited to using only IP and port; it could also be a domain name address. After receiving the request, the system server first processes it through the aspect layer created using the AOP architecture. The aspect layer processes the interface address getList in the request path, checking the header to determine if the address is compliant and secure. If the check is successful, the request is forwarded to the MVC three-tier architecture. After logical processing, the data is sent back to the aspect layer, which then feeds the data back to the front-end page for response processing. Through the above operations, the system achieves "request forwarding, processing, and response processing through pointcuts."

[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, then the access request is forwarded to the MVC architecture for logical processing through the pointcut pre-configured by the aspect layer, so that the client can perform full-stage control of the configuration file through the MVC architecture.

[0057] As a preferred embodiment, step S3 includes steps S31 to S32, each of which is detailed below:

[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, then through the pointcut pre-configured by the aspect layer, the access request is forwarded to the model layer, view layer and controller layer in the MVC architecture, 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 controller layer processes various requests between the view layer and the model layer.

[0059] Step S32: Respond to the client's access to the view layer, and use the view layer to comprehensively manage each stage of the configuration file, thereby achieving secure management of the configuration file.

[0060] The various stages of the configuration file process 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 deployed by combining the MVC architecture and the AOP aspect layer. Users can access the View layer to fully 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 file in real time, so as to track the change history of the configuration file and serve as a basis for troubleshooting when a fault occurs.

[0063] As a preferred embodiment, after performing step S3, step S4 is also included, which is as follows:

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

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

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

[0067] The judgment module M2 is used to determine whether a user using the client has registered based on the user registration information.

[0068] The forwarding control module M3 is used to forward access requests to the MVC architecture for logical processing through a pre-configured pointcut in the aspect layer if the user using the client has registered and the client's list of accessible interfaces contains the interface address of the request path. This allows the client to perform full-stage control over 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, with each unit as follows:

[0070] Forwarding unit 31 is used to forward access requests to the model layer, view layer and controller layer in the MVC architecture through the pointcut pre-configured by the aspect layer if the user using the user terminal has registered and the accessible interface list corresponding to the user terminal contains the interface address of the request path. This allows the model layer to handle the management data and business logic of the configuration file, the view layer to display and maintain the relevant information of the configuration file, and the controller layer to handle various requests between the view layer and the model layer.

[0071] The phased control unit 32 is used to respond to user access to the view layer. It uses the view layer to comprehensively control each stage of the configuration file and realize the secure management of the configuration file. The various stages of the configuration file include the generation, modification, review, storage, distribution, backup and recovery of the configuration file.

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

[0073] The matching module M4 is used to forward the access request to the MVC architecture for logical processing through a pre-configured pointcut in the aspect layer if the user using the client has registered and the client's list of accessible interfaces contains the interface address of the request path. This allows the client to match the interface address of the request path with the pre-configured pointcut in the aspect layer before the client performs full-stage control of the configuration file through the MVC architecture.

[0074] The feedback module M5 is used to forward access requests to the MVC architecture for logical processing through the entry points pre-configured by the aspect layer. After the user end performs full-stage control of the configuration file through the MVC architecture, it sends the logical processing data and full-stage control data to the aspect layer. Then, the aspect layer feeds back the received data to the front-end page.

[0075] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the system described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0076] This invention also provides a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is running, it controls the device where the computer-readable storage medium is located to execute the intelligent substation configuration file management method described in Embodiment 1.

[0077] This 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 intelligent 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 a computer program, a computer program), and one or more modules / units are stored in memory and executed by a processor to complete the present invention. One or more modules / units can be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in a terminal.

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

[0080] The memory mainly consists of a program storage area and a data storage area. The program storage area can store the operating system, applications required for at least one function, etc., while the data storage area can store related data. Furthermore, the memory can be high-speed random access memory, or non-volatile memory, such as plug-in hard drives, smart media cards (SMC), secure digital cards (SD), and flash cards, or other volatile solid-state storage devices.

[0081] It should be noted that the above-mentioned terminal may include, but is not limited to, processors and 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 combine certain components, or different components.

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

[0083] This invention provides a method, system, medium, and terminal for managing configuration files in intelligent substations. When a user terminal accesses the system functions of an intelligent substation, an access request is generated. Using an aspect layer created with an AOP architecture, JWT information is obtained from the request header. The JWT information is then parsed to obtain user registration information, a list of accessible interfaces corresponding to the user terminal, and the interface address of the request path. Based on the user registration information, it is determined whether the user has registered. If the user has registered and the list of accessible interfaces corresponding to the user terminal contains the interface address of the request path, it indicates that the requesting user is an internal personnel and that the interface address conforms to specifications or security. Then, through a pre-configured entry point in the aspect layer, the access request is forwarded to the MVC architecture for logical processing, enabling the user terminal to perform full-stage control of the configuration file through the MVC architecture. Through the above methods, users can manage configuration files at all stages by accessing the MVC architecture. This combines AOP (Aspect-Oriented Programming) with MVC to achieve secure configuration file management, preventing direct access by internal personnel and thus improving configuration file security. Furthermore, before forwarding access requests, it verifies whether the user is registered and whether the requested interface address is an accessible interface on the user's end. This ensures the requesting user has the necessary permissions and the interface address is secure, allowing configuration file management under the premise of access rights and secure interface address. This eliminates the need for network administrators to add access routes to the configuration file list or to check and maintain ACLs, thus mitigating potential network congestion and data latency during peak periods and improving system stability and reliability. In addition, the aspect layer created using AOP can separate non-business logic (such as security verification and logging) from business logic, reducing code redundancy and improving system response speed and execution efficiency.

[0084] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. In particular, it should be noted that any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention for those skilled in the art.

Claims

1. A method for managing configuration files in an intelligent substation, characterized in that, include: When a user accesses the system functions of a smart substation, an access request is generated. The aspect layer then retrieves JWT information from the request header of the access request, parses the JWT information to obtain user registration information, a list of accessible interfaces corresponding to the user, and the interface address of the request path. The aspect layer is created using the AOP architecture. Based on the user registration information, determine whether the user using the client has registered; If the user using the client is registered and the accessible interface list corresponding to the client contains the interface address of the request path, then the access request is forwarded to the MVC architecture for logical processing through the pre-configured entry point of 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 is registered and the accessible interface list corresponding to the client contains the interface address of the request path, then the access request is forwarded to the model layer, view layer, and controller layer of the MVC architecture through the pre-configured entry point of the aspect layer, so that the model layer processes the configuration file management data and business logic, the view layer displays and maintains the relevant information of the configuration file, and the controller layer processes various requests between the view layer and the model layer. Responding to the client's access to the view layer, the controller layer comprehensively manages each stage of the configuration file, achieving secure management of the configuration file. The stages of the configuration file include configuration file generation, modification, review, storage, distribution, backup, and recovery.

2. The intelligent substation configuration file management method as described in claim 1, characterized in that, The view layer is also used to record and display operation logs generated during the maintenance of configuration files in real time.

3. The intelligent substation configuration file management method as described in claim 1, characterized in that, The step of determining whether a user using the client has registered based on the user registration information specifically involves: If the user registration information contains a registration identifier, it is determined that the user using the client has registered. If the user registration information does not contain a registration identifier, it is determined that the user using the client has not registered. The registration identifier is generated by the smart substation system when the user successfully registers with the system.

4. The intelligent substation configuration file management method as described in claim 1, characterized in that, Before the step of forwarding the access request to the MVC architecture for logical processing via a pre-configured pointcut in the aspect layer, if the user using the client has registered and the accessible interface list corresponding to the client contains the interface address of the request path, so that the client can perform full-stage control of the configuration file through the MVC architecture, the following steps are also included: The interface address of the request path is matched with the pointcut pre-configured by the aspect layer.

5. The intelligent substation configuration file management method as described in claim 1, characterized in that, After forwarding the access request to the MVC architecture for logical processing via a pre-configured entry point in the aspect layer, so that the user terminal can perform full-stage control of the configuration file through the MVC architecture, the method further includes: The logic processing data and the full-stage control data are sent to the aspect layer, and then the aspect layer feeds back the received data to the front-end page.

6. A smart substation configuration file management system, characterized in that, include: The parsing module is used to generate an access request when a user terminal accesses the system functions of a smart substation. It then obtains JWT information from the request header of the access request through the aspect layer, and parses the JWT information to obtain user registration information, a list of accessible interfaces corresponding to the user terminal, and the interface address of the request path. The aspect layer is created using the AOP architecture. The judgment module is used to determine, based on the user registration information, whether the user using the client has registered; The forwarding control module is configured to, if the user using the client has registered and the accessible interface list corresponding to the client contains the interface address of the request path, forward the access request to the MVC architecture for logical processing through a pre-configured entry point in the aspect layer, so that the client can perform full-stage control of the configuration file through the MVC architecture. The forwarding control module includes a forwarding unit and a phased control unit. The forwarding unit is configured to, if the user using the client has registered and the accessible interface list corresponding to the client contains the interface address of the request path, forward the access request to the MVC architecture for logical processing through a pre-configured entry point in the aspect layer. The entry point is to forward the access request to the model layer, view layer, and control layer in the MVC architecture, 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 management unit is used to respond to the user's access to the view layer, and to use the view layer to comprehensively manage each stage of the configuration file, so as to realize the secure management of the configuration file; wherein, each stage of the configuration file includes the generation, modification, review, storage, distribution, backup and recovery of the configuration file.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program; wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform a smart substation configuration file management method as described in any one of claims 1 to 5.

8. A terminal, characterized in that, It includes 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 5.

Images