Electronic examination and approval method and device combining position positioning

Abstract

The invention relates to an electronic examination and approval method and device combined with position positioning, and the method comprises the steps: distributing a plurality of examination and approval nodes for an execution process of a work ticket when a distribution terminal detects the operation of creating the work ticket by a worker in charge of work; when the distribution terminal detects that an operation responsible person triggers any approval node, a to-be-handled task is pushed to an approval terminal of an approver associated with the approval node, and the to-be-handled task is used for notifying the approver to arrive in an electronic fence associated with the approval node to perform on-site signing; when the approval terminal detects that an approver triggers an approval request based on the to-do task, a position verification request is sent to the positioning system, and a verification result fed back by the positioning system is obtained; and if the approval terminal determines that the approver is located in the electronic fence associated with the approval node based on the verification result, the electronic approval authority of the approver is unlocked, so that the approver executes electronic approval. The authenticity of electronic examination and approval is improved.

Description

Technical Field

[0001] This application relates to the field of big data technology, and in particular to an electronic approval method and apparatus that combines location positioning. Background Technology

[0002] In the field of safety production management of hazardous chemical enterprises, the approval management of operations (such as hot work, confined space entry, work at heights, and temporary power supply) is a critical link in ensuring operational safety, directly related to the enterprise's production safety and personnel safety. Currently, there are two main management models for operation approval in the industry, but both have obvious shortcomings and are difficult to meet safety management and compliance requirements.

[0003] On the one hand, some companies still rely on traditional paper documents for special operation approvals, requiring the work supervisor, monitor, safety officer, and approver to manually sign the paper documents for confirmation. Under this model, the approval process lacks effective supervision, making it highly susceptible to irregularities such as proxy signing and retroactive signing. Furthermore, paper documents cannot record the location information of personnel at the time of approval, nor can they verify whether the approver has arrived at the work site to complete on-site confirmation. This renders crucial information such as the implementation of safety measures and the results of work risk assessments meaningless, creating significant safety hazards.

[0004] On the other hand, some companies have introduced electronic approval systems to replace paper documents. While this has improved approval efficiency to some extent, it has not yet solved the core verification problem of whether the approver has actually arrived at the work site. Traditional electronic approval systems can only realize the online flow of the approval process, but cannot obtain and verify the real-time location of the approver at the time of approval. This means that the approver can still complete the online approval at a non-work site, and the authenticity of the electronic approval cannot be effectively guaranteed. Summary of the Invention

[0005] This application provides an electronic approval method and device that combines location positioning to solve the problem of the inability to guarantee the authenticity of work approvals.

[0006] Firstly, this application provides an electronic approval method incorporating location tracking, the method comprising:

[0007] When the allocation terminal detects that the work supervisor has created a work ticket, multiple approval nodes are allocated to the execution process of the work ticket. Each approval node is associated with an electronic fence and at least one approver. When the allocation terminal detects that the work supervisor has triggered any approval node, a pending task is pushed to the approval terminal of the approver associated with the approval node. The pending task is used to notify the approver that they need to go to the electronic fence associated with the approval node for on-site approval.

[0008] When the approval terminal detects that the approver has triggered an approval request based on the pending task, it sends a location verification request to the positioning system and obtains the verification result fed back by the positioning system. If the approval terminal determines based on the verification result that the approver is located within the electronic fence associated with the approval node, it unlocks the approver's electronic approval permission so that the approver can perform the electronic approval.

[0009] Optionally, after the allocation terminal assigns multiple approval nodes to the execution process of the work ticket, the method further includes:

[0010] The allocation terminal performs the following operations for each approval node:

[0011] Set a node ID for the approval node;

[0012] Based on the work location entered by the person in charge of the work at the approval node, the electronic fence to which the work location belongs is determined;

[0013] Based on the at least one approver input by the person in charge of the operation at the approval node, determine the approver identity identifier of each approver;

[0014] The node ID, the electronic fence, and the approver's identity are associated and sent to the positioning system. The positioning system combines the received association with the pre-stored mapping relationship between the approver's identity and the positioning device ID to form a binding relationship between the node ID, the electronic fence, the approver's identity, and the positioning device ID.

[0015] Optionally, when the allocation terminal detects that the task manager has triggered any approval node, pushing the pending task to the approval terminal of the approver associated with the approval node includes:

[0016] When the allocation terminal detects that the person in charge of the operation has triggered any approval node, it determines the node ID of the triggered approval node, the electronic fence where the approval node is located, and the approver's identity identifier associated with the approval node;

[0017] Based on the approver's identity identifier, a pending task is pushed to the approver's approval terminal, wherein the pending task includes the node ID to be triggered by the approver and the electronic fence to be reached.

[0018] Optionally, when the approval terminal detects that the approver has triggered an approval request based on the pending task, sending a location verification request to the positioning system includes:

[0019] When the approval terminal detects that the approver has triggered an approval request based on the pending task, it sends a location verification request containing the node ID and the approver's identity to the positioning system.

[0020] The positioning system is configured to locate the approver's location device ID from the binding relationship based on the approver's identity identifier, and obtain the approver's location information based on the location device ID. The positioning system also locates the corresponding electronic fence from the binding relationship based on the node ID, and determines whether the location information is within the electronic fence.

[0021] Optionally, if the approval terminal determines, based on the verification result, that the approver is located within the electronic fence associated with the approval node, then unlocking the approver's electronic approval permissions includes:

[0022] The verification result fed back by the positioning system is obtained through the approval terminal, wherein the verification result includes node ID, verification qualification information and the approver's identity identifier;

[0023] If it is determined based on the verification information that the approver is located within the electronic fence, then the corresponding node approval interface is found according to the node ID;

[0024] Based on the approver's identity identifier, the approver's electronic approval permissions are unlocked in the node approval interface.

[0025] Optionally, the verification result also includes the approver's location information and verification timestamp; after unlocking the approver's electronic approval permissions, the method further includes:

[0026] The verification result, the approver's location information, the verification timestamp, the node ID, and the approver's identity identifier are structurally integrated to form a structured data packet;

[0027] The structured data packet is encrypted and then added to a preset signature evidence chain to form an encrypted signature evidence chain with a time stamp. The encrypted signature evidence chain is used to provide an immutable technical evidence carrier for the work approval process.

[0028] Optionally, after sending a location verification request to the positioning system, the method further includes:

[0029] If the approval terminal determines based on the verification result that the approver is outside the electronic fence, it locks the electronic approval permission and issues a prompt on the node approval interface, wherein the prompt is used to inform the approver that they are not in the designated area and cannot complete the approval.

[0030] Secondly, this application provides an electronic approval device that incorporates location tracking, the device comprising:

[0031] The allocation module is used to allocate multiple approval nodes to the execution process of the work ticket when the allocation terminal detects that the work supervisor has created a work ticket. Each approval node is associated with an electronic fence and at least one approver. When the allocation terminal detects that the work supervisor has triggered any approval node, it pushes a pending task to the approval terminal of the approver associated with the approval node. The pending task is used to notify the approver that they need to go to the electronic fence associated with the approval node for on-site approval.

[0032] The approval module is used to send a location verification request to the positioning system and obtain the verification result fed back by the positioning system when the approval terminal detects that the approver has triggered an approval request based on the pending task; if the approval terminal determines that the approver is located within the electronic fence associated with the approval node based on the verification result, the approval module unlocks the approver's electronic approval permission so that the approver can perform electronic approval.

[0033] Thirdly, this application provides an electronic device, comprising: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor connected to the at least one bus; and at least one memory connected to the at least one bus.

[0034] Fourthly, this application also provides a computer storage medium storing computer-executable instructions for executing the electronic approval method combined with location positioning described in any of the preceding claims of this application.

[0035] Compared with the prior art, the technical solution provided in this application has the following advantages: After the allocation terminal detects the operation of the work supervisor creating a work ticket, it allocates multiple approval nodes to the work ticket execution process. Each approval node is associated with an electronic fence and at least one approver. When the work supervisor triggers any approval node, the pending task is pushed to the approval terminal of the corresponding approver. Through the association design of nodes, electronic fences, and approvers, this application clarifies that approvers must be present at the designated site to participate in the signing and approval process, avoiding the lack of on-site constraints in traditional approvals. At the same time, through the targeted push of pending tasks, it ensures that approvers are clearly aware of the on-site signing and approval requirements. After the approval terminal detects that the approver has triggered an approval request based on the pending task, it immediately sends a location verification request to the positioning system. Only when it is confirmed that the approver is within the corresponding electronic fence will the electronic approval permission be unlocked, and the approver can then perform the signing and approval operation. This eliminates behaviors that undermine authenticity, such as remote signing and proxy signing, and ensures that each electronic approval corresponds to the approver's actual on-site verification action, thus realizing the authenticity of electronic approvals. Attached Figure Description

[0036] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0037] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0039] Figure 1 A flowchart illustrating an electronic approval method incorporating location tracking, provided as an embodiment of this application;

[0040] Figure 2 A schematic diagram of the interface of the work ticket application form provided in this embodiment of the application;

[0041] Figure 3 A schematic diagram of the generated electronic fence provided for an embodiment of this application;

[0042] Figure 4 This is a schematic diagram of the approver's approval interface provided in an embodiment of this application;

[0043] Figure 5 A flowchart of an electronic approval process incorporating location tracking is provided as an embodiment of this application.

[0044] Figure 6 A schematic diagram of an electronic approval device combined with location positioning provided in an embodiment of this application;

[0045] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0047] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0048] The following will describe in detail an electronic approval method combining location positioning provided in this application embodiment, taking its application in a work ticket system as an example. Figure 1 As shown, the specific steps are as follows:

[0049] Step 101: When the allocation terminal detects that the work supervisor has created a work ticket, multiple approval nodes are allocated to the execution process of the work ticket. Each approval node is associated with an electronic fence and at least one approver. When the allocation terminal detects that the work supervisor has triggered any approval node, a pending task is pushed to the approval terminal of the approver associated with the approval node. The pending task is used to notify the approver that they need to go to the electronic fence associated with the approval node for on-site approval.

[0050] Step 102: When the approval terminal detects that the approver has triggered an approval request based on the pending task, it sends a location verification request to the positioning system and obtains the verification result fed back by the positioning system. If the approval terminal determines that the approver is located within the electronic fence associated with the approval node based on the verification result, it unlocks the approver's electronic approval permission so that the approver can execute the electronic approval.

[0051] In a work management scenario, the allocation terminal is the core scheduling hub of the entire approval process. When the work supervisor (such as a workshop foreman or construction project manager) logs into the system via a mobile app and initiates the creation of an electronic work ticket, the allocation terminal first guides the supervisor to complete the basic work information entry. The work supervisor then fills out the work ticket application form in detail according to the work ticket system's instructions. Figure 2This is a schematic diagram of the work permit application form. The basic work information must include the type of work (hot work, confined space entry, working at heights, temporary power supply, blind flange removal / installation, excavation, circuit closure, etc.), work location (must be precise to the specific area, such as the operating platform north of tank 035 in Workshop 1), planned start and end times, description of work content (e.g., replacing the safety valve on the top of the tank), hazardous chemical information (e.g., chemical name, physicochemical properties, hazardous characteristics, etc.), hazard identification and risk assessment (analysis of potential risks such as fire, explosion, poisoning, electric shock, etc., and corresponding control measures), and safety preparation (e.g., for hot work, details such as fire blanket installation, fire extinguisher configuration, and fire monitor arrangements must be provided). Additionally, the names and qualifications of the operator and supervisor must be filled in the relevant personnel fields (e.g., the operator must possess the corresponding special operation certificate, and the supervisor must possess on-site supervision qualifications), ensuring that the qualifications of personnel involved in the work meet safety regulations. The work in this application can be hazardous work such as chemical handling or engineering work, or it can be ordinary work.

[0052] After the basic work information is entered, the allocation terminal automatically assigns multi-level approval nodes to the work order execution process and establishes a connection between approval nodes, electronic fences, and approvers. Specifically, the allocation terminal defines an electronic fence for each approval node based on the specific work location entered in the information, achieving a one-to-one association between the approval node and the electronic fence. Simultaneously, each approval node is bound to at least one approver with the corresponding approval qualifications; some approval nodes require multiple approvers to complete the signing in sequence, forming a complete chain of responsibility for traceability.

[0053] For example, for hot work operations in tank areas, the system assigns three levels of approval nodes: The first approval node is the preliminary review node, which approves the work after the basic information is entered, and is approved by the person in charge of the area where the work site is located, mainly verifying whether the electronic fence area meets the work requirements. The second approval node is the professional approval node, which approves the work after the person in charge of the work has initially completed the work task, and is approved by the safety department, mainly verifying the effectiveness and compliance of safety risk control measures. The third approval node is the final approval node, which approves the work after the person in charge of the work has completed all the work tasks, and is approved by the final approver authorized by the company (such as the safety director), mainly verifying the completion status of the work.

[0054] When the work supervisor completes the work ticket creation and triggers any approval node, the allocation terminal immediately pushes the pending task to the approver associated with that node through the work management system. The pending task is delivered directly through the approver's approval terminal, and can also be accompanied by an SMS reminder. The pending task is marked with the node ID of the approval node, the electronic fence range corresponding to the work location, and the approver's identity identifier. For example, the workshop director might receive a pending task: "Director Zhang, you have a hot work task on the top of tank V102 in tank area A05, node ID DH-SC-20250901-001. You need to go to within 15 meters of the work site to complete the approval." This clearly defines the task requirements and also mandates that the approver must participate in the approval process on-site from the outset.

[0055] Once the approver sees the pending task on their approval terminal, they must wear the company-issued positioning device (such as a positioning card or an approval terminal with a positioning card) and enter the electronic fence area. Within this area, they must click the "Initiate Approval" button to trigger the approval request. Based on the approval request, the approval terminal will automatically send a location verification request to the company's personnel positioning system. The location verification request carries a node ID. The positioning system determines the approver's current location information based on the location verification request, identifies the electronic fence corresponding to the node ID, and then determines whether the approver's location information is within the electronic fence. It then generates a result indicating whether the verification passed or failed and sends it back to the approval terminal.

[0056] If the verification result received by the approval terminal is successful, the electronic approval permission is immediately unlocked. For example, the electronic signature button on the approval terminal changes from gray to operable. At this time, the approver can complete the signing after verifying that the safety measures are correct on-site. If the verification result is unsuccessful, the APP interface will pop up a prompt that you are not in the designated area of ​​the work site and cannot make the approval. At the same time, the signing function remains locked to prevent remote signing, proxy signing and other violations. This not only ensures the authenticity of the signing, but also ensures that each approval step meets the on-site verification requirements through the linkage between location and approval, thereby reducing the risk of work safety.

[0057] In this application, after detecting the work order creation operation by the work supervisor, the allocation terminal assigns multiple approval nodes to the work order execution process. Each approval node is associated with an electronic fence and at least one approver. When the work supervisor triggers any approval node, a pending task is pushed to the approval terminal of the corresponding approver. This application, through the association design of nodes, electronic fences, and approvers, clearly stipulates that approvers must be present at the designated site to participate in the signing and approval process, avoiding the lack of on-site constraints in traditional approvals. Simultaneously, the targeted push of pending tasks ensures that approvers are clearly aware of the on-site signing and approval requirements. After detecting that an approver has triggered an approval request based on a pending task, the approval terminal immediately sends a location verification request to the positioning system. Only when the approver is confirmed to be within the corresponding electronic fence is the electronic approval permission unlocked, allowing the approver to perform the signing and approval operation. This prevents remote signing and proxy signing, which undermine authenticity, ensuring that each electronic approval corresponds to the approver's actual on-site verification action, thus achieving the authenticity of electronic approvals.

[0058] As an optional implementation, after the allocation terminal assigns multiple approval nodes to the execution process of the work order, the method further includes: the allocation terminal performing the following operations for each approval node: setting a node ID for the approval node; determining the electronic fence to which the work location belongs based on the work location entered by the work supervisor at the approval node; determining the approver identity identifier for each approver based on at least one approver entered by the work supervisor at the approval node; and associating the node ID, electronic fence, and approver identity identifier and sending them to the positioning system, wherein the positioning system combines the received association relationship with the pre-stored mapping relationship between the approver identity identifier and the positioning device ID to form a binding relationship between the node ID, electronic fence, approver identity identifier, and positioning device ID.

[0059] After the allocation terminal assigns multiple approval nodes to the work ticket execution process, the allocation terminal first generates a unique node ID for each approval node. This node ID serves as the exclusive identifier for the approval node and is used throughout the entire approval process to avoid node confusion or process disorder when multiple jobs are running in parallel.

[0060] Next, the terminal obtains the work location entered by the person in charge of the work at the approval node, calls the preset electronic fence database, and automatically matches the electronic fence range corresponding to the work location. The electronic fence is defined with the work location as the core, covering the key areas that the approver needs to verify on-site, ensuring that the approver must arrive at the actual scene related to the work to meet the approval conditions. For example, a circular electronic fence with a radius of 15 meters covers the work location and the necessary surrounding areas. Figure 3 This is a schematic diagram of the generated electronic fence. Figure 3 The bolded lines indicate the boundaries of the electronic fence. The person in charge of the operation can determine whether the scope of the electronic fence is reasonable based on the image.

[0061] Subsequently, the distribution terminal extracts at least one approver information entered by the person in charge of the operation at this node, and generates a unique approver identity identifier for each approver, such as an employee number or ID card number, to ensure the uniqueness and compliance of the approver's identity.

[0062] Finally, the distribution terminal integrates the node ID, electronic fence information, and approver identity to form complete node association data, which is then sent to the positioning system in real time. The work ticket system used by the positioning system and the distribution terminal uses the same approver identity. The positioning system calls the pre-stored mapping relationship between the approver identity and the positioning device ID, and further binds the node ID, electronic fence, approver identity, and positioning device ID. This allows the positioning system to subsequently locate the positioning device worn by the approver based on the approver identity and retrieve the electronic fence based on the node ID.

[0063] As an optional implementation, in step 101, when the allocation terminal detects that the job manager has triggered any approval node, the pending tasks are pushed to the approval terminal of the approver associated with the approval node, including the following:

[0064] Step S11: When the distribution terminal detects that the person in charge of the work has triggered any approval node, determine the node ID of the triggered approval node, the electronic fence where the approval node is located, and the approver's identity identifier associated with the approval node;

[0065] Step S12: Push the pending task to the approver's approval terminal based on the approver's identity identifier. The pending task includes the node ID to be triggered by the approver and the electronic fence to be reached.

[0066] When the task manager's terminal triggers any approval node, the terminal extracts the node ID of the currently triggered node. This node ID was generated and associated with the node during the node creation phase. Then, based on the node ID, the terminal matches the pre-stored task location information and further calls the database built into the task ticket system to determine the 3D electronic fence where the current node is located. This electronic fence was demarcated and bound to the node ID when the task manager created the node. Finally, the terminal identifies the approver corresponding to the current approval node according to the preset approval process configuration and extracts the approver's unique approver identity identifier (such as employee number AQ012) from the unified identity authentication system. This identity identifier is completely consistent in the task ticket system and the positioning system, ensuring cross-system identity consistency, thereby completing the core information combination of node ID, electronic fence, and approver identity identifier.

[0067] Based on the obtained approver's identity identifier, the allocation terminal locates the approval terminal bound to that approver and then generates structured to-do tasks. The to-do tasks explicitly include the node ID to be approved, the specified geofence information, and can also include supplementary information such as the work type (e.g., hot work), and the planned start and end times of the work, ensuring that the approver is aware of the basic work details in advance. The node ID in the to-do task allows the approver to quickly query work details, and the geofence information indicates the specific location the approver needs to reach, such as the 15-meter area around reactor No. 035 in Workshop 1.

[0068] Once a task is generated, the distribution terminal sends it to the corresponding approver's terminal via a preset push channel. Furthermore, the approver's task interface displays a warning: "You must arrive at the work site and pass the location card verification before you can sign," further reinforcing the approver's understanding that on-site approval is required and avoiding operational errors associated with off-site approval.

[0069] The pending tasks in this application include node IDs to be triggered by the approver and electronic fences to be reached. The clear labeling of node IDs makes it easy for the approver to quickly locate the task, and the intuitive display of electronic fences reduces the communication link for the approver to inquire about the on-site location. The dual push mechanism of pending tasks and SMS reduces the probability of task omission and ensures that the approver can start on-site verification and approval operations in a timely manner, shortening the overall time of the approval process.

[0070] As an optional implementation, in step 102, when the approval terminal detects that the approver has triggered an approval request based on a pending task, sending a location verification request to the positioning system includes the following: when the approval terminal detects that the approver has triggered an approval request based on a pending task, a location verification request containing a node ID and the approver's identity identifier is sent to the positioning system, so that the positioning system can find the approver's positioning device ID from the binding relationship based on the approver's identity identifier, and obtain the approver's location information based on the positioning device ID. The positioning system can also find the corresponding electronic fence from the binding relationship based on the node ID and determine whether the location information is within the electronic fence.

[0071] After the approver views the pending tasks through the approval terminal, they go to the geofence area and click the "Initiate Approval" button to trigger the approval request. The approval terminal will immediately generate and send a location verification request to the company's personnel's positioning system according to preset logic. At this time, the location verification request sent by the approval terminal contains two core pieces of information: first, the node ID of the node to be approved, and second, the approver's identity identifier.

[0072] After receiving a location verification request, the positioning system will perform data matching and location determination based on the binding relationship between the stored node ID, electronic fence, approver identity identifier, and positioning device ID. The positioning system will quickly retrieve the corresponding positioning device ID from the binding relationship based on the approver identity identifier in the location verification request, and then obtain the approver's current location information in real time, such as latitude and longitude coordinates. Furthermore, based on the node ID in the request, the positioning system will search for the electronic fence range corresponding to that node from the binding relationship. Finally, the obtained approver location information will be compared with the electronic fence range to determine whether the approver is currently within the fence, providing a basis for unlocking subsequent approval permissions.

[0073] The specific process by which the positioning system obtains the current location information of the approver is as follows: Based on the determined positioning device ID, the positioning beacons in the work area (such as deployed at a density of 1 beacon per 15㎡ at key points in the work area) are triggered to scan the wireless signal of the positioning device, and the signal reception strength is captured and recorded in real time; the positioning beacon transmits the captured signal strength data to the positioning base station deployed at the highest point in the factory area, and the positioning base station transmits the data back to the positioning engine through the industrial ring network; the positioning engine calculates the distance between the positioning device and the beacon based on the attenuation model d=10^((RSSI-RSSI_1m) / 10n (n is the environmental calibration factor), and when at least 3 beacons capture the signal of the same positioning device, the real-time location information of the approver is obtained by solving the least squares method.

[0074] In this application, the accuracy of location verification is achieved by including the node ID and the approver's identity identifier in the location verification request, combined with the location system's call to the binding relationship. The node ID ensures that the location system can accurately match the electronic fence corresponding to the current approval, avoiding the problem of misjudging the compliance of the approver's location due to incorrect fence matching. The association between the approver's identity identifier and the location device ID eliminates the risk of others using the location device to fraudulently obtain compliance verification.

[0075] As an optional implementation, in step 102, if the approval terminal determines based on the verification result that the approver is located within the electronic fence associated with the approval node, then unlocking the approver's electronic approval permissions includes the following:

[0076] The verification results fed back by the positioning system are obtained through the approval terminal. The verification results include the node ID, verification qualification information and the approver's identity identifier.

[0077] If the approver is determined to be within the electronic fence based on the verification information, then the corresponding node approval interface is found according to the node ID.

[0078] Based on the approver's identity, unlock the approver's electronic approval permissions in the node approval interface.

[0079] Once the positioning system completes the location verification of the approver, it will send the verification result, including the node ID, verification pass information, and approver identity identifier, back to the approver's approval terminal in real time. The node ID is used to accurately locate the current work process awaiting approval, the verification pass information directly reflects whether the approver meets the location requirements for on-site signing, and the approver identity identifier ensures the uniqueness of the access control recipient.

[0080] The approval terminal extracts the verification pass information from the results and uses its built-in logic judgment module to determine that the current approver's location verification status is qualified. Based on this, the approval terminal uses the node ID as the core index to retrieve the electronic work ticket interface corresponding to that node from the database. The interface contains basic work information, risk assessment results, safety measure records, and other content previously filled in by the work supervisor, ensuring that the retrieved interface completely matches the work to be approved and avoiding node mismatch issues.

[0081] Once the interface loads, the approval terminal will initiate the permission unlocking logic based on the parsed approver's identity identifier: the system compares the approver's identity identifier with the preset list of operable roles on the node approval interface. After confirming that the approver has the approval authority for the current node, it unlocks the electronic approval function modules on the interface, including key operation entry points such as the approval opinion input box, the electronic signature confirmation button, and the approval result submission option. At the same time, it keeps functions outside the scope of the approver's authority (such as the signature bar of other approvers) locked to ensure that the approver can only operate the content corresponding to their own authority.

[0082] Figure 4 The diagram shows the approval interface for the approver. It can be seen that for the circuit breaker operation, the approval cannot be signed because the work area has not been reached.

[0083] This application achieves precise and scenario-based control of approval permissions through the parsing of structured verification results, precise matching of node interfaces, and identity-bound permission unlocking. On the one hand, it matches exclusive approval interfaces based on node IDs, ensuring that the content viewed by the approver is highly consistent with the review requirements of the current work process. Combined with identity identification, it locks the scope of operation, preventing unauthorized approvals and accidental operations on other nodes. On the other hand, only approvers who have passed location verification and whose identities match can operate the approval function, preventing violations such as remote signing and proxy signing. At the same time, the automated matching of interfaces and permissions reduces human error and shortens the time spent on approval operations. This not only ensures the compliance and authenticity of special work approvals but also improves the efficiency of the approval process.

[0084] As an optional implementation, the verification result also includes the approver's location information and verification timestamp; after unlocking the approver's electronic approval authority, the method further includes: structurally integrating the verification result, the approver's location information, the verification timestamp, the node ID, and the approver's identity identifier to form a structured data packet; encrypting the structured data packet and supplementing it to a preset signature evidence chain to form an encrypted signature evidence chain containing a time stamp, wherein the encrypted signature evidence chain is used to provide an immutable technical evidence carrier for the work approval process.

[0085] The verification results sent by the positioning system also include the approver's location and verification timestamp. The approver's location refers to their specific real-time location, such as latitude and longitude, and the verification timestamp is accurate to the second to ensure time accuracy. The node system integrates the verification results, the approver's location, and the verification timestamp in a structured manner to form a complete data set that associates the job identifier, personnel identity, location information, time information, and signature content. This data set is encrypted using a preset encryption algorithm to ensure that the data cannot be tampered with or stolen during storage and transmission. After encryption, the node system supplements it to a pre-created signature evidence chain. This evidence chain uses the node ID as the core index and stores the signature-related data of each approver in the order of the approval process. Previously, basic data such as node creation information and pending task push records had been stored. After this supplement, the evidence chain fully covers the key data of job application, location verification, and electronic signature, ultimately forming an encrypted signature evidence chain with a time stamp.

[0086] The encrypted signature evidence chain is used as an evidence chain in the work approval process. It can provide a traceable and tamper-proof technical evidence carrier for the work approval process. Each piece of data in the evidence chain is associated with a node ID and an approver's identity identifier. It can be quickly queried and retrieved through the node ID or the approver's identity identifier, meeting the needs of subsequent security traceability and compliance verification.

[0087] This application provides an overall flowchart of electronic approval that incorporates location tracking, such as... Figure 5 As shown, the steps include the following.

[0088] Step 501: The person in charge of the work initiates the work ticket application.

[0089] The person in charge of the work initiates a work ticket application in the work ticket system through the allocation terminal, and fills in the work ticket application form in detail as required. The content includes basic work information, as well as the names and qualification information of the worker and the supervisor. After the work ticket system detects the creation operation, it automatically assigns a unique work ticket ID to the current work ticket.

[0090] Step 502: Assign multiple approval nodes to the work ticket process and set node IDs. The node IDs are associated with the electronic fence and the approver's identity.

[0091] The allocation terminal assigns multiple approval nodes to the work order execution process, such as the initial review node, professional approval node, and final approval node, and sets a unique node ID for each approval node; based on the work location entered by the work supervisor at each approval node, the electronic fence corresponding to each node is matched from the preset electronic fence library; at the same time, at least one approver information entered at each node is extracted to determine the unique identity of each approver, forming a relationship between node ID, electronic fence and approver identity.

[0092] Step 503: Send the association relationship to the positioning system, and the positioning system establishes the binding relationship between node ID, electronic fence, approver identity identifier and positioning device ID.

[0093] The distribution terminal integrates the node ID of the approval node, the corresponding electronic fence, and the approver's identity into an associated data packet, which is then sent to the positioning system and saved through a secure data interface. The positioning system and the work ticket system use the same identity for the same approver and pre-store the mapping relationship between the approver's identity and the positioning device ID. After receiving the data packet, the system automatically associates and matches the data, ultimately forming a binding relationship between the node ID, electronic fence, approver's identity, and positioning device ID.

[0094] Step 504: The task manager triggers the approval node and pushes the pending tasks to the approver.

[0095] When the distribution terminal detects that the person in charge of the work has triggered any approval node, it retrieves the node ID, the corresponding electronic fence, and the identity of the associated approver. Based on the approver's identity, it locates the approval terminal bound to it, generates a task to be done, and clearly marks the node ID to be approved, the electronic fence range to be reached, and a warning message that requires on-site approval. Then, the task is pushed through the work ticket system to ensure that the approver is aware of the node information and on-site requirements.

[0096] Step 505: After the approver arrives at the site, the approval request is triggered, and the approval terminal sends a location verification request to the positioning system.

[0097] After viewing the pending tasks on the terminal, the approver arrives at the electronic fence area and then clicks the "Initiate Approval" button to trigger the approval request. The approval terminal immediately generates a location verification request, which contains the node ID of the current approval node and the approver's identity identifier. This request is transmitted to the positioning system through a preset encrypted channel. This request is used to instruct the positioning system to match the corresponding electronic fence based on the node ID and the positioning device based on the approver's identity identifier to obtain the approver's location.

[0098] Step 506: The positioning system determines the approver's location information and generates feedback results on whether the approver is within the electronic fence.

[0099] After receiving a location verification request, the positioning system searches for the corresponding positioning device ID from the binding relationship based on the approver's identity. It then triggers the positioning beacon in the work area to scan the positioning device's signal, captures the signal reception strength, and transmits it to the positioning base station. The base station then transmits the data back to the positioning engine through the industrial ring network. The positioning engine calculates the distance between the device and the beacon based on the signal attenuation model and uses triangulation to calculate the approver's real-time location coordinates. Simultaneously, it retrieves the corresponding electronic fence from the binding relationship based on the node ID, compares the location coordinates with the electronic fence range, and generates a result indicating successful verification (within the fence) or unsuccessful verification (outside the fence), which is then fed back to the approval terminal in real time.

[0100] Step 507: The approval terminal unlocks or locks permissions based on the verification results, and the approver completes the node approval.

[0101] If the verification result received by the approval terminal is qualified, the electronic approval function of the interface is unlocked, and the approver completes the signing after on-site verification; if the verification result is unqualified, the approval authority is locked, and a prompt is displayed that the approver cannot approve because the node is not within the designated fence, thus forcing the approver to go to the site for verification.

[0102] This application provides an electronic approval device that incorporates location tracking, such as... Figure 6 As shown, the device includes:

[0103] The allocation module 601 is used to allocate multiple approval nodes to the execution process of the work ticket when the allocation terminal detects that the work supervisor has created a work ticket. Each approval node is associated with an electronic fence and at least one approver. When the allocation terminal detects that the work supervisor has triggered any approval node, it pushes a pending task to the approval terminal of the approver associated with the approval node. The pending task is used to notify the approver that they need to go to the electronic fence associated with the approval node for on-site approval.

[0104] The approval module 602 is used to send a location verification request to the positioning system and obtain the verification result fed back by the positioning system when the approval terminal detects that the approver has triggered an approval request based on the pending task. If the approval terminal determines that the approver is located within the electronic fence associated with the approval node based on the verification result, the approver's electronic approval permission is unlocked so that the approver can execute the electronic approval.

[0105] Optionally, the device is also used for:

[0106] The allocation terminal performs the following operations for each approval node:

[0107] Set a node ID for the approval node;

[0108] Based on the work location entered by the person in charge of the work at the approval node, determine the electronic fence to which the work location belongs;

[0109] Based on the at least one approver entered by the person in charge of the work at the approval node, determine the approver identity of each approver;

[0110] After associating the node ID, electronic fence, and approver identity, the data is sent to the positioning system. The positioning system combines the received association with the pre-stored mapping relationship between the approver identity and the positioning device ID to form a binding relationship between the node ID, electronic fence, approver identity, and positioning device ID.

[0111] Optionally, the allocation module 601 is used for:

[0112] When the distribution terminal detects that the person in charge of the operation has triggered any approval node, it determines the node ID of the triggered approval node, the electronic fence where the approval node is located, and the approver's identity identifier associated with the approval node.

[0113] Based on the approver's identity, pending tasks are pushed to the approver's approval terminal. The pending tasks include the node ID to be triggered by the approver and the electronic fence to be reached.

[0114] Optionally, the approval module 602 is used for:

[0115] When the approval terminal detects that the approver has triggered an approval request based on the pending task, it sends a location verification request containing the node ID and the approver's identity to the positioning system.

[0116] This allows the positioning system to find the approver's positioning device ID from the binding relationship based on the approver's identity identifier, and obtain the approver's location information based on the positioning device ID. The positioning system also finds the corresponding electronic fence from the binding relationship based on the node ID and determines whether the location information is within the electronic fence.

[0117] Optionally, the approval module 602 is used for:

[0118] The verification results fed back by the positioning system are obtained through the approval terminal. The verification results include the node ID, verification qualification information and the approver's identity identifier.

[0119] If the approver is determined to be within the electronic fence based on the verification information, then the corresponding node approval interface is found according to the node ID.

[0120] Based on the approver's identity, unlock the approver's electronic approval permissions in the node approval interface.

[0121] Optionally, the verification result also includes the approver's location information and a verification timestamp; the device is also used for:

[0122] The verification results, the approver's location information, the verification timestamp, the node ID, and the approver's identity identifier are structurally integrated to form a structured data packet;

[0123] The structured data packet is encrypted and then added to the preset signature evidence chain to form an encrypted signature evidence chain with a time stamp. The encrypted signature evidence chain is used to provide an immutable technical evidence carrier for the work approval process.

[0124] Optionally, the device is also used for:

[0125] If the approval terminal determines that the approver is outside the electronic fence based on the verification result, it will lock the electronic approval permission and issue a prompt on the node approval interface. The prompt is used to inform the approver that they are not in the designated area and cannot complete the approval.

[0126] like Figure 7 As shown, this application provides an electronic device including a processor 701, a communication interface 702, a memory 703, and a communication bus 704, wherein the processor 701, the communication interface 702, and the memory 703 communicate with each other through the communication bus 704.

[0127] Memory 703 is used to store computer programs.

[0128] In one embodiment of this application, the processor 701, when executing a program stored in the memory 703, implements the electronic approval method combined with location positioning provided in any of the foregoing method embodiments.

[0129] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the electronic approval method combined with location positioning as provided in any of the foregoing method embodiments.

[0130] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0131] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0132] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0133] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. An electronic approval method incorporating location tracking, characterized in that, The method includes: When the allocation terminal detects that the work supervisor has created a work ticket, multiple approval nodes are allocated to the execution process of the work ticket. Each approval node is associated with an electronic fence and at least one approver. When the allocation terminal detects that the work supervisor has triggered any approval node, a pending task is pushed to the approval terminal of the approver associated with the approval node. The pending task is used to notify the approver that they need to go to the electronic fence associated with the approval node for on-site approval. When the approval terminal detects that the approver has triggered an approval request based on the pending task, it sends a location verification request to the positioning system and obtains the verification result fed back by the positioning system. If the approval terminal determines based on the verification result that the approver is located within the electronic fence associated with the approval node, it unlocks the approver's electronic approval permission so that the approver can perform the electronic approval.

2. The method according to claim 1, characterized in that, After the allocation terminal assigns multiple approval nodes to the execution process of the work ticket, the method further includes: The allocation terminal performs the following operations for each approval node: Set a node ID for the approval node; Based on the work location entered by the person in charge of the work at the approval node, the electronic fence to which the work location belongs is determined; Based on the at least one approver input by the person in charge of the operation at the approval node, determine the approver identity identifier of each approver; The node ID, the electronic fence, and the approver's identity are associated and sent to the positioning system. The positioning system combines the received association with the pre-stored mapping relationship between the approver's identity and the positioning device ID to form a binding relationship between the node ID, the electronic fence, the approver's identity, and the positioning device ID.

3. The method according to claim 1, characterized in that, When the allocation terminal detects that the task manager has triggered any approval node, the pending tasks are pushed to the approval terminal of the approver associated with the approval node, including: When the allocation terminal detects that the person in charge of the operation has triggered any approval node, it determines the node ID of the triggered approval node, the electronic fence where the approval node is located, and the approver's identity identifier associated with the approval node; Based on the approver's identity identifier, a pending task is pushed to the approver's approval terminal, wherein the pending task includes the node ID to be triggered by the approver and the electronic fence to be reached.

4. The method according to claim 2, characterized in that, When the approval terminal detects that the approver has triggered an approval request based on the pending task, sending a location verification request to the positioning system includes: When the approval terminal detects that the approver has triggered an approval request based on the pending task, it sends a location verification request containing the node ID and the approver's identity to the positioning system. The positioning system is configured to locate the approver's location device ID from the binding relationship based on the approver's identity identifier, and obtain the approver's location information based on the location device ID. The positioning system also locates the corresponding electronic fence from the binding relationship based on the node ID, and determines whether the location information is within the electronic fence.

5. The method according to claim 1, characterized in that, If the approval terminal determines, based on the verification result, that the approver is located within the electronic fence associated with the approval node, then unlocking the approver's electronic approval permissions includes: The verification result fed back by the positioning system is obtained through the approval terminal, wherein the verification result includes node ID, verification qualification information and the approver's identity identifier; If it is determined based on the verification information that the approver is located within the electronic fence, then the corresponding node approval interface is found according to the node ID; Based on the approver's identity identifier, the approver's electronic approval permissions are unlocked in the node approval interface.

6. The method according to claim 5, characterized in that, The verification result also includes the approver's location information and verification timestamp; After unlocking the approver's electronic approval permissions, the method further includes: The verification result, the approver's location information, the verification timestamp, the node ID, and the approver's identity identifier are structurally integrated to form a structured data packet; The structured data packet is encrypted and then added to a preset signature evidence chain to form an encrypted signature evidence chain with a time stamp. The encrypted signature evidence chain is used to provide an immutable technical evidence carrier for the work approval process.

7. The method according to claim 1, characterized in that, After sending a location verification request to the positioning system, the method further includes: If the approval terminal determines based on the verification result that the approver is outside the electronic fence, it locks the electronic approval permission and issues a prompt on the node approval interface, wherein the prompt is used to inform the approver that they are not in the designated area and cannot complete the approval.

8. An electronic approval device incorporating location positioning, characterized in that, The device includes: The allocation module is used to allocate multiple approval nodes to the execution process of the work ticket when the allocation terminal detects that the work supervisor has created a work ticket. Each approval node is associated with an electronic fence and at least one approver. When the allocation terminal detects that the work supervisor has triggered any approval node, it pushes a pending task to the approval terminal of the approver associated with the approval node. The pending task is used to notify the approver that they need to go to the electronic fence associated with the approval node for on-site approval. The approval module is used to send a location verification request to the positioning system and obtain the verification result fed back by the positioning system when the approval terminal detects that the approver has triggered an approval request based on the pending task; if the approval terminal determines that the approver is located within the electronic fence associated with the approval node based on the verification result, the approval module unlocks the approver's electronic approval permission so that the approver can perform electronic approval.

9. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the method described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method described in any one of claims 1-7.

Images