A Method and System for Controlling Editing Permissions of Nuclear Power Plant Isolation Information Based on Dynamic Negotiation

Abstract

This invention relates to the field of access control technology and proposes a method and system for controlling editing permissions of nuclear power plant isolation information based on dynamic negotiation. The method includes: receiving and verifying an editing request for target isolation information; upon successful verification, obtaining the user's identity identifier, login IP address, and target isolation information identifier, and generating a session identifier as a composite identifier for the current continuous editing state; querying the editing state records of the target isolation information; if no established continuous editing state exists, establishing the corresponding state and binding the session identifier and editing permission; if an established continuous editing state exists, reading the original session identifier and performing conflict detection with the current session identifier; if an editing conflict exists, performing negotiation release and session takeover processing to achieve permission configuration. This invention generates a unique composite session identifier for nuclear power plant isolation information and combines conflict detection, negotiation release, and session takeover mechanisms to achieve dynamically controlled transfer of editing permissions for the same information.

Description

Technical Field

[0001] This invention relates to the field of access control technology, specifically to a method and system for controlling the editing access of nuclear power plant isolation information based on dynamic negotiation. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] With the continuous advancement of informatization and digitalization in the nuclear power sector, an increasing number of operation and management tasks are being conducted through online process systems. While online systems offer significant advantages in improving information transmission efficiency, strengthening inter-departmental collaboration, and standardizing business processes, systematization and sharing are not the only requirements for operations directly related to nuclear safety, such as isolation management. During the isolation planning and editing phase, the accuracy of isolation boundaries, consistency of information entry, and clarity of responsibility all directly impact the formulation and implementation of subsequent isolation measures. Therefore, ensuring the safety, control, and accuracy of the isolation planning process while promoting online operations is particularly crucial for nuclear power operation and management.

[0004] In existing technologies, online editing of the same nuclear power plant isolation business information typically employs either an exclusive control method or a multi-user open editing method. While the exclusive control method can prevent multiple people from simultaneously modifying the same content, in practical applications, if the editor fails to exit in time, experiences an abnormal interruption, or has a poor handover, other personnel will be unable to continue processing the information, easily causing business stagnation. The multi-user open editing method, while facilitating collaborative operation, can easily lead to problems such as content overwriting, input conflicts, boundary confusion, and unclear responsibilities because multiple people can modify the same information simultaneously. It is evident that existing technologies fail to properly handle the editing control relationships of the same information in scenarios involving multiple participants. They cannot effectively prevent data chaos caused by simultaneous editing by multiple people, nor can they guarantee that state transitions, personnel handovers, and responsibility definitions during the editing process remain clear and controllable. Therefore, they cannot meet the safety, accuracy, and rigor requirements of nuclear power plant isolation management. Summary of the Invention

[0005] To address the aforementioned problems, this invention proposes a method and system for controlling editing permissions of nuclear power plant isolation information based on dynamic negotiation. By generating a unique composite session identifier for nuclear power plant isolation information and combining conflict detection, negotiation release, and session takeover mechanisms, the dynamic and controlled transfer of editing permissions for the same information is achieved.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: One or more embodiments provide a method for controlling editing permissions of nuclear power plant isolation information based on dynamic negotiation, including the following steps: The system retrieves and verifies edit requests for the target isolation information. Upon successful verification, it responds to the edit request by retrieving the user's identity and login IP address corresponding to the current edit request, as well as the identifier of the target isolation information. A session identifier is generated based on the user's identity identifier, login IP address, and target isolation information, serving as a composite identifier for the current continuous editing state; Query the editing status record of the target isolation information to determine whether there is an established continuous editing status; if there is no established continuous editing status, establish a continuous editing status corresponding to the current editing request, and bind the continuous editing status with the session identifier and the editing permissions of the target isolation information; When an established continuous editing state exists, the original session identifier corresponding to the established continuous editing state is read. Conflict detection is performed based on the original session identifier and the currently editing session identifier. If an editing conflict exists, negotiation release and session takeover processing are performed to implement permission configuration.

[0007] One or more embodiments provide a nuclear power plant isolation information editing permission control system based on dynamic negotiation, including: The request receiving module is configured to receive and verify editing requests for target isolation information. After successful verification, it responds to the editing request by obtaining the user identity and login IP address corresponding to the current editing request, as well as the identifier of the target isolation information. The composite identifier information generation module is configured to generate a session identifier based on the user's identity identifier, login IP address, and target isolation information, which serves as the composite identifier information for the current continuous editing state; The continuous editing status determination module is configured to query the editing status records of the target isolation information to determine whether a continuous editing status has been established; when no continuous editing status has been established, a continuous editing status corresponding to the current editing request is established, and the continuous editing status is bound to the session identifier and the editing permissions of the target isolation information; The negotiation release and session takeover module is configured to read the original session identifier corresponding to the established continuous editing state when an established continuous editing state exists, perform conflict detection based on the original session identifier and the currently editing session identifier, and perform negotiation release and session takeover processing when an editing conflict exists to implement permission configuration.

[0008] An electronic device includes a memory and a processor, as well as computer instructions stored in the memory and running on the processor. When the processor executes the computer instructions, the computer instructions perform the steps in the above-described method for controlling the editing permissions of nuclear power plant isolation information based on dynamic negotiation.

[0009] A computer-readable storage medium for storing computer instructions, which, when executed by a processor, complete the steps in the above-described method for controlling the editing permissions of nuclear power plant isolation information based on dynamic negotiation.

[0010] Compared with the prior art, the beneficial effects of the present invention are as follows: This invention constructs a composite session identifier system using "user identity identifier + login IP address + target isolation information identifier," establishing a stable mapping relationship between the editing entity, the terminal source, and the business object. Compared to relying solely on a single account or lock identifier, this method more accurately distinguishes real editing scenarios, improving the precision of access control. Furthermore, instead of a simple permanent exclusive lock mechanism, it introduces conflict detection, negotiated release, and session takeover mechanisms when a continuous editing state is detected. This prevents multiple users from simultaneously editing the same isolation information, thus avoiding content overwriting, boundary confusion, and unclear responsibility. It also avoids business interruptions caused by traditional exclusive locks due to personnel not logging out, abnormal client interruptions, or untimely handover. For nuclear power plant isolation management scenarios, this solution ensures that editing rights during the isolation planning process remain clear, unique, and controlled, guaranteeing that the operator, operation source, takeover time, and status changes in the editing chain can be recorded and traced, thereby improving the security, accuracy, and rigor of isolation information editing. Meanwhile, the dynamic negotiation mechanism makes the transfer of permissions verifiable and recoverable, adapting to the management requirements of multi-person collaboration, job handover, anomaly recovery and strict auditing in nuclear power business. Therefore, it is more suitable for application in isolated business systems with high security levels and strong process constraints.

[0011] The advantages of the present invention, as well as its additional advantages, will be described in detail in the following specific embodiments. Attached Figure Description

[0012] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute a limitation thereof.

[0013] Figure 1 This is a flowchart of the nuclear power plant isolation information editing permission control method based on dynamic negotiation according to Embodiment 1 of the present invention; Figure 2 This is a flowchart of the IP address acquisition method according to Embodiment 1 of the present invention; Detailed Implementation The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0014] It should be noted that the following detailed descriptions are exemplary and intended to provide further illustration of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0015] It should be noted that the terminology used herein is for describing particular embodiments only and is not intended to limit the exemplary embodiments of the present invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof. It should be noted that, without conflict, the various embodiments and features within those embodiments can be combined with each other. The embodiments will now be described in detail with reference to the accompanying drawings.

[0016] Example 1 In one or more of the technical solutions disclosed in the embodiments, such as Figures 1 to 2 As shown, the nuclear power plant isolation information editing permission control method based on dynamic negotiation can be implemented in a processor, including the following steps: Step 1: Obtain and verify the edit request for the target isolation information. After successful verification, respond to the edit request by obtaining the user identity and login IP address corresponding to the current edit request, as well as the identifier of the target isolation information. Step 2: Generate a session identifier based on the user's identity identifier, login IP address, and target isolation information, which serves as the composite identifier for the current continuous editing state; Step 3: Query the editing status record of the target isolation information to determine whether there is an established continuous editing status; if there is no established continuous editing status, establish a continuous editing status corresponding to the current editing request, and bind the continuous editing status with the session identifier and the editing permissions of the target isolation information; Step 4: When an established continuous editing state exists, read the original session identifier corresponding to the established continuous editing state, perform conflict detection based on the original session identifier and the currently editing session identifier, and when an editing conflict exists, perform negotiation release and session takeover processing to realize permission configuration. In the above implementation, a composite session identifier construction method of "user identity identifier + login IP address + target isolation information identifier" establishes a stable mapping relationship among the editing subject, terminal source, and business object. Compared with methods relying solely on a single account or single lock identifier, this method can more accurately distinguish real editing scenarios, thus improving the precision of access control. Furthermore, instead of employing a simple permanent exclusive lock mechanism, a conflict detection, negotiation release, and session takeover handling mechanism is introduced when a continuous editing state is detected. This prevents multiple people from simultaneously editing the same isolation information, which could lead to content overwriting, boundary confusion, and unclear responsibilities. It also avoids business stagnation caused by traditional exclusive locks due to personnel not logging out, abnormal client interruptions, or untimely handover. For nuclear power plant isolation management scenarios, this solution ensures that editing rights during the isolation planning process remain clear, unique, and controlled. It guarantees that the operator, operation source, takeover time, and status changes in the editing chain can be recorded and traced, thereby improving the security, accuracy, and rigor of isolation information editing. Meanwhile, the dynamic negotiation mechanism makes the transfer of permissions verifiable and recoverable, adapting to the management requirements of multi-person collaboration, job handover, anomaly recovery and strict auditing in nuclear power business. Therefore, it is more suitable for application in isolated business systems with high security levels and strong process constraints.

[0017] In this embodiment, an editing session refers to an editing interaction process with a continuous state established and maintained by the system for the user regarding the isolation information after the user initiates an editing request around specific isolation information, provided that the authorization verification is passed; A session identifier is an identification information used to uniquely identify an editing session, and is used to characterize the editing state established by a specific user on specific isolated information under a specific network identifier.

[0018] In some embodiments, before obtaining the edit request for the target isolation information in step 1, the system further includes a step of initializing the permission identifier for the initially created target isolation information. Specifically, when the first user initializes the creation of the target isolation entry, the system associates the first user's unique identity ID, the isolation entry's unique resource identifier ID, and the IP address of the current first user login to establish an initial continuous editing state and stores it in the edit lock record of the database. Permission initialization establishes the initial continuous editing state for the isolated target information. Subsequent edit requests determine whether the current request can enter, continue, replace, or take over this continuous editing state. When a subsequent edit request is received, the system reads the edit lock record and compares the information corresponding to the current edit request with the initial continuous editing state or its updated continuous editing state to determine whether the current edit request is a continuation of the existing editing state or a competition request for existing editing permissions.

[0019] A further technical solution includes an edit request verification process when an edit request is received. Specifically, when an edit request is received, an eligibility and permission verification is performed to verify whether the current user has the eligibility and permission to edit the type of the entry to which the target isolated information belongs. S1-1. If the user does not have editing privileges, the system will refuse the operation and the process will end. S1-2. If the user has the permission to edit, check the first locked status of the isolated information entry. S1-3. If the first locking state is unlocked and the user currently requesting the edit has editing privileges, the verification is successful; otherwise, the verification fails. The first lock state is set for isolation information and can be manually locked using the button in the settings. It indicates whether the current isolation information entry can be edited. After successful verification, the next steps are performed to further check whether the target isolation information is currently in a continuously editable state, in order to determine whether the current user can obtain editing control over the target isolation information.

[0020] In step 1, after the edit request is verified, the process of receiving an edit request for the target isolation information, responding to the edit request, and obtaining the user identity and login IP address corresponding to the current edit request, as well as the identifier of the target isolation information, includes the following steps: Step 11: Obtain the user identity identifier based on the authentication information corresponding to the obtained edit request; Step 12: Determine the identifier of the target isolation information based on the resource parameters carried in the edit request; Step 13: Obtain the login IP address based on the request header information and / or network connection information corresponding to the edit request; Step 14: Standardize the login IP address; output the user identity identifier, the target isolation information identifier, and the standardized login IP address.

[0021] In one specific implementation, the login IP is obtained through the Nginx-Gateway-business layer link: Step 131: The Nginx gateway layer transmits the client's real IP address by configuring X-Forwarded-For and X-Real-IP; Step 132: Process the forwarding request headers for the real IP address through the Gateway; Step 133: The business layer obtains the login IP of the current requester through code; A session identifier is generated based on the user's identity, login IP address, and target isolation information. Specifically, it can be generated as a globally unique identifier in the format "<User ID>_<Isolation Information ID>_<User IP>", for example, U1001_ISO2024_192.168.1.100. The session identifier constructed in this embodiment includes a composite session identifier that includes user identity, address, and target isolation information. This unique composite session identifier serves as a globally unique identifier for the current editing session.

[0022] In step 3, the editing status record of the target isolation information is queried to determine whether there is an established continuous editing status. Specifically, the database is queried to confirm whether there is an established continuous editing status for the current target isolation information. If so, the system records the session identifier of the old editing session. In step 4, when an established continuous editing state exists, the original session identifier corresponding to the established continuous editing state is read. Conflict detection is performed based on the original session identifier and the currently editing session identifier. If an editing conflict exists, negotiation release and session takeover processing are executed to implement permission configuration. Specifically, one implementation method for permission configuration includes the following steps: Step 41: When an established continuous editing state exists, read the original session identifier corresponding to the established continuous editing state, and jointly identify the editing subject, editing object and network access environment based on the current session identifier and the original session identifier to perform editing conflict detection; Specifically, when the target isolation information is in an occupied editing state, and the current session identifier corresponding to the current editing request is inconsistent with the original session identifier that occupies the target isolation information, it is determined that there is an editing conflict between the current editing request and the original continuous editing state; The current session identifier is compared with the original session identifier. If they match, it means that the current request is a continuation of the original continuous editing state and does not constitute an editing conflict.

[0023] An occupied edit state only indicates that someone or a session is already editing, but a new request does not necessarily constitute a conflict. For example, it might be a continuation of an existing session: the same user, the same isolation information, the same network environment, or simply a reconnection or page refresh. In this case, although the target isolation information is in an occupied edit state, the current request and the original session are essentially a continuation of the same continuous edit state and should not be considered a conflict.

[0024] Step 42: When an editing conflict is detected, send a negotiation release request to the original continuous editing state corresponding to the original session identifier, and receive the response result for the negotiation release request; Step 43: When the response result indicates that release is allowed, revoke the editing permission corresponding to the original continuous editing state and assign the editing permission to the current continuous editing state corresponding to the current session identifier to complete the session takeover; When the response indicates a refusal to release, maintain the editing permissions corresponding to the original continuous editing state and reject the current editing request; In some embodiments, in step 41, conflict detection includes multiple types, including conflicts caused by IP changes, continuation of the original session, network jitter, and edit-occupancy conflicts. When any detection is determined to be a conflict state, it is determined that a conflict state exists. In some implementations, an IP change scenario indicates that a user attempts to initiate an editing request for the same target isolation information through a new device, a new network location, or a new network access path. Furthermore, when the system detects that the login IP address in the current session identifier corresponding to the current editing request is inconsistent with the login IP address in the original session identifier corresponding to the original continuous editing state stored in the database, it determines that an IP change scenario exists and is a conflict state; otherwise, no IP conflict state occurs. In some embodiments, an edit occupancy conflict is determined when the target isolation information is in an already occupied edit state and the current session identifier is inconsistent with the original session identifier. Specifically, it receives the original IP address input corresponding to the current editing request and performs standardization processing on the original IP address to obtain the current standardized IP address; at the same time, it performs standardization processing on the original IP address corresponding to the original continuous editing state recorded in the database to obtain the original standardized IP address; when the current standardized IP address is different from the original standardized IP address, it is determined to be an IP change and an editing placeholder conflict state. The standardization of IP addresses includes at least one of the following: (1) When the original IP address contains X-Forwarded-For header information forwarded by a proxy server or gateway, extract the first comma-separated IP value as the real IP address; (2) When the original IP address is an IPv4 address format mapped from IPv6, remove the mapping prefix and retain the IPv4 address; for example, “::ffff:192.168.1.100”, the system removes the “::ffff:” prefix and retains the pure IPv4 format; (3) When the original IP address does not fall under the above circumstances, the original IP address is retained as the standardization result.

[0025] This embodiment eliminates the impact of factors such as proxy forwarding and address mapping on subsequent IP comparison results through standardized processing.

[0026] In some embodiments, the conflict detection process for the original session continuation judgment is as follows: query the isolated editing session table in the database, retrieve the active editing session record corresponding to the current user's identity, and if no active editing session record is found, immediately return to the ALLOW state to allow the current user's editing operation; otherwise, if an active editing session exists, compare the IP address of the active editing session with the IP address corresponding to the current editing request, and return to the conflict state when the two are completely consistent. In this embodiment, an active editing session record is a session record in the "editing" state.

[0027] When the system detects that the current standardized IP address is inconsistent with the original standardized IP address, it further determines whether there is a network type switch.

[0028] A further technical solution is to trigger the generation of a security audit event when the original IP address belongs to a preset internal network address range, while the current IP address does not belong to the internal network address range, such as a public network address, and write the security audit event to the security audit log table.

[0029] Optionally, security audit events preferably include at least: user identification, original IP address, current IP address, and the time of the event. Security audit events allow for the recording and tracking of editing activities involving switching between internal and external networks.

[0030] In some embodiments, network jitter fault tolerance determination of conflict state is performed. Specifically, the last operation timestamp corresponding to the active editing session is obtained, and the time difference between the last operation timestamp and the current time is calculated. When the time difference is less than a preset time threshold, the current IP change is determined to be a network instantaneous jitter and is not considered a conflict state; otherwise, it is determined to be a conflict state.

[0031] In some implementations, network transient jitter includes VPN reconnection, mobile network switching, or automatic reconnection after a brief link interruption.

[0032] When the time difference is greater than or equal to the preset time threshold, the system determines that the current IP change is a real device or location change and proceeds to the subsequent permission processing flow.

[0033] Furthermore, based on the conflict detection results for IP change scenarios, the corresponding session state decision results are output: Step 411: When the current standardized IP address is the same as the original standardized IP address, or when it is determined to be a momentary network jitter, maintain the original continuous editing state; Step 412: When the IP change is determined to be valid, it is determined to be an IP change conflict state, and the decision-making process of negotiation and release is initiated.

[0034] Furthermore, in step 43 above, during the process of negotiating release and / or session takeover, an audit log is generated. The audit log includes at least the original session identifier, the current session identifier, the processing result, and the processing time.

[0035] Step 42: When an editing conflict is detected, the process of sending a negotiated release request to the original persistent editing state corresponding to the original session identifier and receiving the response to the negotiated release request includes the following steps: Step 421: Send a negotiated release request to the client corresponding to the original continuous editing state through the long connection channel corresponding to the original session identifier; In some implementations, the long-lived connection channel is a WebSocket long-lived connection.

[0036] In some implementations, the negotiated release request carries release confirmation countdown information to prompt the user corresponding to the original continuous editing state to make a release response within a preset time.

[0037] Step 422: Receive the negotiation release response result: Receive the response result returned by the client corresponding to the original continuous editing state in response to the negotiation release request, including whether to allow release or refuse release; In some implementations, the response result includes any of the following: consent to release; refusal to release; or a timeout result indicating that no response result has been returned within a preset time.

[0038] When the client corresponding to the original continuous editing state returns a release consent message within a preset time, the system determines that the response result indicates that the release is allowed, that is, the editing permission of the currently isolated target information is allowed to be transferred. When the client corresponding to the original continuous editing state returns a rejection message, or fails to return a response within a preset time, the system determines that the response indicates a rejection.

[0039] This embodiment introduces a dynamic negotiation process. When editing conflicts are detected in the same nuclear power plant isolation information, instead of directly using rigid locking or forced overwriting, the system notifies the original editor in real time and confirms whether to release permissions within a preset time limit. This mechanism makes the transfer of editing permissions interactive, verifiable, and traceable. It avoids information overwriting, boundary confusion, and unclear responsibilities caused by multiple people editing simultaneously, and reduces business interruptions caused by abnormal locking, forgotten exit, or untimely handover under traditional exclusive locking mechanisms, thereby improving the continuity and collaborative efficiency of the isolation information editing process.

[0040] In step 43, when the response indicates that release is permitted, the editing permission corresponding to the original persistent editing state is revoked, and the editing permission is assigned to the current persistent editing state corresponding to the current session identifier, thereby completing the session takeover. That is, an atomic update is performed when release is permitted. The atomic update process includes at least the following: Update the session state corresponding to the original continuous editing state to the released state; Create a record of the current persistent edit state corresponding to the current session identifier; Write to the audit log corresponding to this negotiated release process.

[0041] By executing the above processes within the same database transaction, data consistency can be guaranteed between the release of the original continuous editing state, the establishment of the current continuous editing state, and the writing of audit records.

[0042] A further technical solution, the process of establishing a long connection based on the final permission configuration result, is as follows: The system checks whether the current session identifier matches the unique composite session identifier stored in the database: Step S4-1: If they match, then use the currently unique session identifier to establish a WebSocket long connection, enter the editing phase, and the process ends.

[0043] Step S4-2: If there is no consistency, determine whether a long-lived connection has been established using a unique identifier stored in the database. Step S4-2-1: If not, update the unique composite session identifier recorded in the data table, then establish a long connection to enter the editing process, and the process ends. Step S4-2-2: If applicable, first establish a long connection using the unique identifier, and then return the personnel information of the current applicant and the current editor. Further technical solutions, including methods for configuring permissions, also include a method for dynamically negotiating and substituting permissions: Step S5: Obtain the configuration information of whether the applicant of the current editing request has selected to substitute for obtaining editing permissions: Step S5-1: If no replacement is made, the process ends, and the established continuous editing state is maintained; Step S5-2: If replacement is selected, a notification of replacement and a confirmation message indicating whether the replacement is agreed upon are sent to the current editor via a WebSocket long connection. Step S5-2-1: If the current editor refuses to be replaced, send the current applicant a message indicating that the current editor has refused to be replaced and grants them editing privileges. The process then ends. Step S5-2-2: If the agreement is replaced, update the unique composite session identifier of the record and save the editing information performed by the current editor; Step S5-3: Send a message to the current editor that they have successfully exited and had their editing privileges revoked, and terminate the old long connection; Step S5-4: Send an editable notification message to the current applicant. The process ends here.

[0044] This embodiment dynamically monitors changes in login IP addresses and distinguishes between short-term network fluctuations and actual terminal changes by combining session state identification, recording and auditing abnormal network switching processes. Through this method, the system not only reduces the risk of misjudgment and accidental release caused by non-substantive anomalies such as momentary disconnections and network jitter, but also provides focused documentation for security-sensitive actions such as switching from the internal network to the public network, enhancing the system's ability to perceive and audit changes in the network environment during the editing process. For nuclear power plant isolation management scenarios, this technology helps meet the requirements of high-security-level services for network trustworthiness, access control, and accountability.

[0045] This embodiment employs an atomic operation mechanism during the permission transfer process, incorporating key processes such as terminating the old session, creating the new session, and logging into a unified transaction control system to ensure consistency and integrity across all steps. This avoids issues such as inconsistent session states, suspended permissions, data loss, or broken audit chains during permission handover, improving the system's reliability and rigor in abnormal scenarios. Combined with the aforementioned dynamic negotiation and security audit mechanisms, this solution achieves secure and stable transfer of editing permissions while ensuring that only a single entity can edit under controlled conditions at any given time. Therefore, it possesses high practical application value and technological advancement in nuclear power plant isolation information management.

[0046] Example 2 Based on Embodiment 1, this embodiment provides a nuclear power plant isolation information editing permission control system based on dynamic negotiation, including: The request receiving module is configured to receive and verify the edit request for the target isolation information. After successful verification, it responds to the edit request by obtaining the user identity and login IP address corresponding to the current edit request, as well as the identifier of the target isolation information. The composite identifier information generation module is configured to generate a session identifier based on the user's identity identifier, login IP address, and target isolation information, which serves as the composite identifier information for the current continuous editing state; The continuous editing status determination module is configured to query the editing status records of the target isolation information to determine whether a continuous editing status has been established; when no continuous editing status has been established, a continuous editing status corresponding to the current editing request is established, and the continuous editing status is bound to the session identifier and the editing permissions of the target isolation information; The negotiation release and session takeover module is configured to read the original session identifier corresponding to the established continuous editing state when an established continuous editing state exists, perform conflict detection based on the original session identifier and the currently editing session identifier, and perform negotiation release and session takeover processing when an editing conflict exists to implement permission configuration.

[0047] It should be noted that each module in this embodiment corresponds one-to-one with each step in embodiment 1, and their specific implementation process is the same, so it will not be repeated here.

[0048] Example 3 Based on Embodiment 1, this embodiment provides an electronic device, including a memory and a processor, as well as computer instructions stored in the memory and running on the processor. When the computer instructions are executed by the processor, they complete the steps in the nuclear power plant isolation information editing permission control method based on dynamic negotiation described in Embodiment 1.

[0049] Example 4 Based on Embodiment 1, this embodiment provides a computer-readable storage medium for storing computer instructions. When the computer instructions are executed by a processor, they complete the steps in the nuclear power plant isolation information editing permission control method based on dynamic negotiation described in Embodiment 1.

[0050] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. 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.

[0051] While the specific embodiments of the present invention have been described above in conjunction with the accompanying drawings, this is not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of the present invention are still within the scope of protection of the present invention.

Claims

1. A method for controlling editing permissions of nuclear power plant isolation information based on dynamic negotiation, characterized in that, Includes the following steps: The system retrieves and verifies edit requests for the target isolation information. Upon successful verification, it responds to the edit request by retrieving the user's identity and login IP address corresponding to the current edit request, as well as the identifier of the target isolation information. A session identifier is generated based on the user's identity identifier, login IP address, and target isolation information, serving as a composite identifier for the current continuous editing state; Query the editing status record of the target isolation information to determine whether there is an established continuous editing status; if there is no established continuous editing status, establish a continuous editing status corresponding to the current editing request, and bind the continuous editing status with the session identifier and the editing permissions of the target isolation information; When an established continuous editing state exists, the original session identifier corresponding to the established continuous editing state is read. Conflict detection is performed based on the original session identifier and the currently editing session identifier. If an editing conflict exists, negotiation release and session takeover processing are performed to implement permission configuration.

2. The nuclear power plant isolation information editing permission control method based on dynamic negotiation as described in claim 1, characterized in that, Before obtaining an edit request for the target isolation information, the system also includes a step of initializing the permission identifier for the initially created target isolation information. Specifically, when the first user initializes the creation of the target isolation entry, the system associates the first user's unique identity ID, the isolation entry's unique resource identifier ID, and the IP address of the currently logged-in first user to establish an initial continuous editing state, which is stored in the edit lock record in the database.

3. The method for controlling editing permissions of nuclear power plant isolation information based on dynamic negotiation as described in claim 1, characterized in that, When an edit request is received, an edit request verification process is also included. Specifically, when an edit request is received, an eligibility and permission verification is performed to verify whether the current user has the eligibility and permission to edit the type of the entry to which the target isolated information belongs. If the user does not have editing privileges, the system will refuse the operation and the process will end. If the user has the permission to edit, check the first locked state of the isolated information entry. The first locking state is unlocked, and the user currently requesting the edit has editing privileges; otherwise, the verification fails.

4. The nuclear power plant isolation information editing permission control method based on dynamic negotiation as described in claim 1, characterized in that, The process of implementing permission configuration includes the following steps: Step 41: When an established continuous editing state exists, read the original session identifier corresponding to the established continuous editing state, and jointly identify the editing subject, editing object and network access environment based on the current session identifier and the original session identifier to perform editing conflict detection; Step 42: When an editing conflict is detected, a negotiation release request is sent to the original continuous editing state corresponding to the original session identifier, and the response result for the negotiation release request is received; Step 43: When the response result indicates that release is allowed, revoke the editing permission corresponding to the original continuous editing state and assign the editing permission to the current continuous editing state corresponding to the current session identifier to complete the session takeover; When the response indicates a refusal to release, the editing permissions corresponding to the original continuous editing state are maintained, and the current editing request is rejected.

5. The nuclear power plant isolation information editing permission control method based on dynamic negotiation as described in claim 4, characterized in that, Conflict detection includes various types, including conflicts caused by IP changes, continuation of the original session, network jitter, and edit-occupancy conflicts. If any of the detections determines that a conflict exists, then a conflict is deemed to exist. IP Change Conflict Detection: When it is detected that the login IP address in the current session identifier corresponding to the current editing request is inconsistent with the login IP address in the original session identifier corresponding to the original continuous editing state stored in the database, it is determined that there is an IP change situation, which is an IP conflict state. Otherwise, no IP conflict occurred.

6. The nuclear power plant isolation information editing permission control method based on dynamic negotiation as described in claim 5, characterized in that, The conflict detection process for the original session continuation judgment is as follows: query the isolated editing session table in the database, retrieve the record corresponding to the current user's identity, and if no active editing session record is found, immediately return to the ALLOW state to allow the current user's editing operation; Otherwise, if an active editing session exists, the IP address of the active editing session is compared with the IP address corresponding to the current editing request. If the two are completely identical, a conflict state is returned. Alternatively, a network jitter tolerance judgment conflict state can be performed. Specifically, the last operation timestamp corresponding to the active editing session is obtained, and the time difference between the last operation timestamp and the current time is calculated. When the time difference is less than a preset time threshold, the current IP change is determined to be a network instantaneous jitter and is not considered a conflict state; otherwise, it is determined to be a conflict state.

7. The nuclear power plant isolation information editing permission control method based on dynamic negotiation as described in claim 4, characterized in that, When an editing conflict is detected, the process of sending a negotiated release request to the original persistent editing state corresponding to the original session identifier and receiving the response result to the negotiated release request includes the following steps: A negotiated release request is sent to the client corresponding to the original continuous editing state via the long connection channel corresponding to the original session identifier. Receive the response result returned by the client corresponding to the original continuous editing state in response to the negotiated release request, including allowing release or refusing release; When the client corresponding to the original continuous editing state returns a release consent message within a preset time, the system determines that the response indicates that release is allowed; When the client corresponding to the original continuous editing state returns a rejection message, or does not return a response result within the preset time, the system determines that the response result indicates a rejection of release.

8. A nuclear power plant isolation information editing permission control system based on dynamic negotiation, characterized in that, include: The request receiving module is configured to receive and verify the edit request for the target isolation information. After successful verification, it responds to the edit request by obtaining the user identity and login IP address corresponding to the current edit request, as well as the identifier of the target isolation information. The composite identifier information generation module is configured to generate a session identifier based on the user's identity identifier, login IP address, and target isolation information, which serves as the composite identifier information for the current continuous editing state; The continuous editing status determination module is configured to query the editing status records of the target isolation information to determine whether a continuous editing status has been established; when no continuous editing status has been established, a continuous editing status corresponding to the current editing request is established, and the continuous editing status is bound to the session identifier and the editing permissions of the target isolation information; The negotiation release and session takeover module is configured to read the original session identifier corresponding to the established continuous editing state when an established continuous editing state exists, perform conflict detection based on the original session identifier and the currently editing session identifier, and perform negotiation release and session takeover processing when an editing conflict exists to implement permission configuration.

9. An electronic device, characterized in that, It includes a memory and a processor, as well as computer instructions stored in the memory and running on the processor, which, when executed by the processor, perform the steps in the nuclear power plant isolation information editing permission control method based on dynamic negotiation as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, Used to store computer instructions, which, when executed by a processor, complete the steps in the nuclear power plant isolation information editing permission control method based on dynamic negotiation as described in any one of claims 1-7.

Images