Process control method and device based on communication fault repair, equipment and medium

Abstract

The application is applied to the technical field of process control, and discloses a process control method and device based on communication fault repair, equipment and medium. The method comprises the following steps: in a preset repair service process, a first mapping relationship between a user and a role is established; a second mapping relationship among a role, a process node and a permission is established; in response to an operation request of a target repair process initiated by the user, a current process node in which the target repair process is located is determined; a role to which the user belongs is determined based on the first mapping relationship; a permission possessed by the role in the current process node is determined based on the second mapping relationship; it is checked whether the operation request and the permission possessed by the current process node are successfully matched; and in the case of successful matching, the operation request is executed. In this way, the fine division of power according to the process node is realized, the overstepping operation can be effectively prevented, the standardization of process control is improved, and the repair efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of process control technology, specifically to a process control method, apparatus, equipment, and medium based on emergency repair of communication faults. Background Technology

[0002] With the rapid development of the communications industry, communication networks have become the core infrastructure for the normal operation of social production, daily life, public services, and various industries. Their stability and continuity directly affect social operational efficiency and user experience. Communication networks have wide coverage, complex equipment types, and dispersed nodes. During daily operation, they are susceptible to various factors such as natural disasters, equipment aging, human error, and network attacks, resulting in various communication failures such as line interruptions, equipment malfunctions, and signal anomalies. Timely repair work is necessary to reduce economic losses and user complaints caused by these failures.

[0003] To ensure uninterrupted communication services, it is often necessary to carry out emergency repairs on areas where communication failures occur.

[0004] Currently, existing communication fault repair processes mostly adopt traditional manual dispatching or simple process management models, without establishing a clear correspondence between users, roles, processes, and permissions. This leads to chaotic permission allocation, blurred boundaries of operation permissions for different roles, and problems such as unauthorized operations and permission omissions. Consequently, the standardization of communication fault repair process control is low, which in turn affects repair efficiency.

[0005] Therefore, in order to overcome the above-mentioned technical problems, the present invention provides a process control method, device, equipment, and medium based on emergency repair of communication faults. Summary of the Invention

[0006] The technical problem to be solved by this invention is how to improve the standardization of process control and thus improve emergency repair efficiency. The purpose is to provide a process control method, device, equipment and medium based on communication fault emergency repair, so as to improve the standardization of process control and thus improve emergency repair efficiency.

[0007] This invention is achieved through the following technical solution:

[0008] Firstly, a process control method based on emergency repair of communication faults, the method comprising: establishing a first mapping relationship between a user and a role in a preset emergency repair business process; establishing a second mapping relationship between a role, a process node, and permissions; responding to an operation request initiated by a user for a target emergency repair process, determining the current process node of the target emergency repair process; determining the role to which the user belongs based on the first mapping relationship; determining the permissions that the role has at the current process node based on the second mapping relationship; verifying whether the operation request and the permissions of the current process node successfully match; and executing the operation request if a successful match is found.

[0009] In some embodiments, determining the permissions of the role at the current process node based on the second mapping relationship includes: obtaining the geographical location of the user when the user's role is a preset emergency repair personnel role; and determining the permissions of the role at the current process node in the second mapping relationship when the geographical location is a preset emergency repair location.

[0010] In some embodiments, before responding to a user-initiated operation request for a target emergency repair process, the method further includes: acquiring the initial biometrics of the operator; performing a search operation on the initial biometrics in a preset biometric database; if the search is successful, determining that the operator is a staff member; then generating a dynamic verification code and acquiring the communication device corresponding to the staff member; sending the dynamic verification code to the communication device; acquiring the encoded data input by the operator; and if the encoded data is the same as the dynamic verification code, determining that the operator is a user.

[0011] In some embodiments, after executing the operation request, the method further includes: in response to a preset signature operation, obtaining signature behavior features; the signature behavior features include air pen lifting trajectory features, jitter features, pen falling trajectory features, and pressure timing features during signing; fusing the signature behavior features to obtain signature fusion features; determining whether the signer matches the user based on the signature fusion features; and canceling the user's operation request if the signer does not match the user.

[0012] In some embodiments, the signature operation is an operation of signing on a preset writing screen using a preset electronic pen; the acquisition of signature behavior features includes: during the signing process, acquiring pen tip position, pen tip pressure value, and pen tip state at preset intervals; the pen tip state is identification data used to indicate whether the pen tip of the electronic pen is in contact with the writing screen; acquiring the air pen lifting trajectory feature and pen falling trajectory feature based on the pen tip position and the pen tip state; extracting the jitter feature based on the pen tip position; and acquiring the pressure timing feature based on the pen tip pressure value.

[0013] In some embodiments, fusing the signature behavior features to obtain a signature fusion feature includes: performing linear mapping on the air pen lifting trajectory feature, the jitter feature, the pen falling trajectory feature, and the pressure timing feature to obtain multiple features to be fused; concatenating the features to be fused to obtain a concatenated feature; fusing the concatenated feature using a self-attention mechanism to obtain a first fusion feature; performing a residual connection between the signature behavior feature and the first fusion feature to obtain a second fusion feature; and normalizing the second fusion feature to obtain the signature fusion feature.

[0014] In some embodiments, determining whether the signer matches the user based on the signature fusion feature includes: obtaining the user signature feature corresponding to the user; calculating the similarity between the user signature feature and the signature fusion feature; determining that the signer matches the user if the similarity is greater than or equal to a preset similarity threshold; and / or determining that the signer does not match the user if the similarity is less than the preset similarity threshold.

[0015] Secondly, a process control device for emergency repair of communication faults, the device comprising: an establishment module configured to establish a first mapping relationship between a user and a role in a preset emergency repair business process; and to establish a second mapping relationship between a role, a process node, and permissions; a node determination module configured to determine the current process node of the target emergency repair process in response to an operation request initiated by a user; a role determination module configured to determine the role to which the user belongs based on the first mapping relationship; a permission determination module configured to determine the permissions possessed by the role at the current process node based on the second mapping relationship; a matching module configured to verify whether the operation request and the permissions possessed by the current process node are successfully matched; and an execution module configured to execute the operation request if a successful match is found.

[0016] Thirdly, an electronic device includes a processor and a memory storing program instructions, the processor being configured to execute the aforementioned process control method for emergency repair of communication faults when running the program instructions.

[0017] Fourthly, a storage medium stores program instructions that, when executed, perform the aforementioned process control method for emergency repair of communication faults.

[0018] Compared with existing technologies, this invention establishes a first mapping relationship between users and roles within a pre-defined emergency repair workflow, and a second mapping relationship between roles, workflow nodes, and permissions. Based on the first mapping relationship, the user's role is determined, and based on the second mapping relationship, the permissions of that role at the current workflow node are determined. The system verifies whether the operation request matches the permissions of the current workflow node, and executes the operation request if a match is found. This constructs a four-dimensional association system between users, roles, workflow nodes, and permissions within the emergency repair workflow. When a user initiates a target emergency repair operation request, the current workflow node of the target emergency repair process is determined. Based on the four-dimensional association system constructed by the first and second mapping relationships, the user's role is determined, and the system verifies whether the operation request matches the permissions of the current workflow node. If a match is found, the operation request is executed. This achieves refined control based on workflow nodes, allowing different roles to have differentiated operation permissions at different workflow nodes. This effectively prevents unauthorized operations, improves the standardization of workflow control, and ultimately increases emergency repair efficiency. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of the present invention and should not be considered as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort. In the drawings:

[0020] Figure 1 This is a flowchart illustrating a process control method for emergency repair of communication faults provided in an embodiment of this disclosure.

[0021] Figure 2 This is a schematic diagram of a multi-branch attention fusion model provided in an embodiment of this disclosure;

[0022] Figure 3 This is a schematic diagram of a process control device for emergency repair of communication failures provided in an embodiment of this disclosure;

[0023] Figure 4 This is a schematic diagram of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the embodiments and accompanying drawings. The illustrative embodiments and descriptions of the present invention are only used to explain the present invention and are not intended to limit the present invention.

[0025] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0026] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0027] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0028] In this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0029] Please see Figure 1 , Figure 1 This is a schematic flowchart illustrating a process control method for emergency repair of communication faults, as shown in an exemplary embodiment of this application. The method includes:

[0030] Step S101: In the preset emergency repair business process, establish the first mapping relationship between users and roles; establish the second mapping relationship between roles, process nodes and permissions.

[0031] Step S102: In response to the user's operation request for the target emergency repair process, determine the current process node of the target emergency repair process.

[0032] Step S103: Determine the user's role based on the first mapping relationship.

[0033] Step S104: Determine the permissions that the role has in the current process node based on the second mapping relationship.

[0034] Step S105: Verify whether the operation request matches the permissions of the current process node.

[0035] Step S106: If a match is successfully found, execute the operation request.

[0036] In this embodiment, a first mapping relationship is established between users and roles within a pre-defined emergency repair workflow. A second mapping relationship is established between roles, workflow nodes, and permissions. Based on the first mapping relationship, the user's role is determined, and based on the second mapping relationship, the permissions of that role at the current workflow node are determined. The system verifies whether the operation request matches the permissions of the current workflow node. If a match is successful, the operation request is executed. This constructs a four-dimensional association system between users, roles, workflow nodes, and permissions within the emergency repair workflow. When a user initiates a target emergency repair workflow operation request, the current workflow node of the target emergency repair workflow is determined. Based on the four-dimensional association system constructed using the first and second mapping relationships, the user's role is determined, and the system verifies whether the operation request matches the permissions of the current workflow node. If a match is successful, the operation request is executed. This achieves refined control based on workflow nodes, allowing different roles to have differentiated operation permissions at different workflow nodes. This effectively prevents unauthorized operations, improves the standardization of workflow control, and ultimately increases emergency repair efficiency.

[0037] It should be noted that the first mapping relationship describes the roles of several users in the emergency repair business process.

[0038] The second mapping relationship describes the permissions held by different roles at different process nodes in the emergency repair business process.

[0039] In some embodiments, the pre-defined emergency repair workflow includes roles such as: initiator, repair personnel, and approver. The defined workflow nodes include: emergency repair initiation node, emergency repair execution node, and emergency repair acceptance node. Different roles have different permissions at different workflow nodes.

[0040] For details, please refer to Table 1, which is an example table of the second mapping relationship.

[0041] Initiators Establish emergency repair work order none none Repair crew none View pending work orders, upload on-site photos, and click "Complete". none Approval personnel none none Acceptance and emergency repair

[0042] Table 1

[0043] In some embodiments, as shown in Table 1, when the process node is at the "Initiate Emergency Repair" node, the permissions of the initiator role include creating an emergency repair work order; the emergency repair personnel and the approver role do not have corresponding permissions. When the process node is at the "Execute Emergency Repair" node, the permissions of the emergency repair personnel role include viewing pending work orders, uploading on-site photos, and clicking "Execute Complete." The initiator role and the approver role do not have corresponding permissions. When the process node is at the "Accept Emergency Repair" node, the permissions of the approver role include accepting the emergency repair. The initiator role and the emergency repair personnel role do not have corresponding permissions.

[0044] It should be noted that the target emergency repair process is the repair process that the user wants to operate. Each role in an emergency repair process can correspond to the same or different users. Users can only perform authorized operations within their corresponding emergency repair process. The operation request is the user's request for the authorized operation they wish to perform within the target emergency repair process.

[0045] The current process node is the process node in which the target emergency repair process is located when the user initiates an operation request.

[0046] Furthermore, before responding to a user-initiated operation request for the target emergency repair process, the process also includes: obtaining the operator's initial biometrics; performing a search operation on the initial biometrics in a preset biometric database; if the search is successful, confirming the operator as a staff member; then generating a dynamic verification code and obtaining the communication device corresponding to the staff member; sending the dynamic verification code to the communication device; obtaining the coded data input by the operator; and if the coded data matches the dynamic verification code, confirming the operator as a user.

[0047] In this way, before responding to a user's request to perform an operation on the target emergency repair process, the system obtains the operator's initial biometric features. Then, it performs a search operation on the initial biometric features in a pre-set biometric database. If the search is successful, the operator is identified as a staff member, a dynamic verification code is generated, and the corresponding communication device is obtained. The dynamic verification code is then sent to the communication device, and the coded data input by the operator is retrieved. If the coded data matches the dynamic verification code, the operator is identified as a user. This implements a dual authentication mechanism of biometric verification and dynamic verification code secondary verification, which can effectively reduce the probability of unauthorized access by unauthorized personnel and improve the system's access security.

[0048] It should be noted that the operator is the person who initiates the operation request for the target emergency repair process.

[0049] It should be noted that the initial biometrics may include one or more of the following: fingerprint features, facial features, voiceprint features, etc.

[0050] It should be noted that the biometric database stores several preset reference biometric features corresponding to staff members. These reference biometric features may include one or more of the following: fingerprint features, facial features, voiceprint features, etc.

[0051] It should be noted that a search operation is performed on the initial biometric features in a pre-defined biometric database, that is, feature matching is performed on each reference biometric feature based on the initial biometric features. If a match is successful, the search is considered successful; if a match fails, the search is considered unsuccessful. In some embodiments, feature matching can be implemented using a similarity matching algorithm, or other matching algorithms, which are not limited here.

[0052] If the search is successful, it can be determined that the operator is one of several preset staff members, and thus identified as a staff member.

[0053] It should be noted that dynamic verification codes can be generated using existing random encryption algorithms, which will not be elaborated upon here.

[0054] It should be noted that after the dynamic verification code is sent to the staff's corresponding communication device, the system will switch to an encoding input interface for data entry. The staff can then input the received dynamic verification code. The encoded data is the dynamic verification code entered by the staff.

[0055] Furthermore, determining the user's role based on the first mapping relationship includes: performing a lookup operation in the first mapping relationship to determine the user's role.

[0056] Optionally, the permissions of a role in the current process node are determined based on the second mapping relationship, including: if the user's role is a preset emergency repair personnel role, obtaining the user's geographical location; if the geographical location is a preset emergency repair location, determining the permissions of the role in the current process node in the second mapping relationship.

[0057] In this way, when the user's role is the preset emergency repair personnel role, the system obtains the user's geographical location. If the geographical location matches the preset emergency repair location, the system determines the role's permissions at the current process node in the second mapping relationship. This implements a geographical location access verification mechanism for emergency repair personnel roles. Only when the user's role is the preset emergency repair personnel role and the real-time geographical location matches the preset emergency repair location, is it allowed to retrieve and determine the role's operation permissions at the current process node. This effectively avoids abnormal behaviors such as emergency repair personnel not being at the work site, remote unauthorized operation, and proxy work. At the same time as identity verification, it also realizes the verification of the emergency repair personnel role's on-site operation.

[0058] Optionally, the permissions of the role in the current process node are determined based on the second mapping relationship, including: if the user's role is a preset emergency repair personnel role, determining whether address identification information sent by a beacon device at a preset emergency repair location has been received; if address identification information has been received, determining the permissions of the role in the current process node in the second mapping relationship.

[0059] It should be noted that the beacon device is located at a preset emergency repair position. It periodically sends address identification information indicating its emergency repair location to the surrounding area.

[0060] In this way, based on the address identification information, it can be directly determined whether the user is at the preset repair location. Compared with directly obtaining the geographical location, this reduces the possibility of users spoofing their location and enables more accurate user location tracking.

[0061] It should be noted that determining the permissions a role possesses in the current process node within the second mapping relationship involves performing a lookup operation within the second mapping relationship to obtain the permissions corresponding to both the role and the current process node. These permissions are then defined as the permissions the role possesses in the current process node.

[0062] Furthermore, after executing the operation request, the process also includes: responding to a preset signature operation and obtaining signature behavior characteristics; the signature behavior characteristics include the air pen lifting trajectory characteristics, jitter characteristics, pen falling trajectory characteristics, and pressure timing characteristics during the signature; fusing the signature behavior characteristics to obtain signature fusion characteristics; determining whether the signer and the user match based on the signature fusion characteristics; and canceling the user's operation request if the signer and the user do not match.

[0063] In this way, by responding to the preset signature operation, the signature fusion feature is obtained by fusing the characteristics of the pen's trajectory in the air, jitter, pen's trajectory, and pressure timing during the signature. Then, based on the signature fusion feature, it is determined whether the signer and the user match. If they do not match, the user's operation request can be revoked. This can effectively prevent risks such as others impersonating the signer, signing on behalf of others, and unauthorized operation. It also prevents third parties from impersonating the signer and tampering with process records and business results in emergency repair business. This ensures that the main body operating the emergency repair business process is real and trustworthy, and that business data is secure and traceable, further strengthening the compliance and security of the entire emergency repair business process.

[0064] It should be noted that after each operation request is completed, the user is required to sign. This signing is done by using a preset electronic pen to sign on a preset writing screen.

[0065] Furthermore, signature behavior features are obtained, including: during the signing process, pen tip position, pen tip pressure value, and pen tip state are obtained at preset intervals; pen tip state is identification data used to indicate whether the pen tip of the electronic pen is in contact with the writing screen; pen lifting trajectory features and pen falling trajectory features are obtained based on pen tip position and pen tip state; jitter features are extracted based on pen tip position; and pressure timing features are obtained based on pen tip pressure value.

[0066] In this way, the pen tip position, pen tip pressure value and pen tip state can be collected periodically according to the preset time interval, thereby obtaining the features of pen lifting trajectory, pen falling trajectory, shaking features and pressure timing features in the air. This enables full-element, fine-grained quantitative collection of the signature dynamic process, providing a reliable and complete feature data source for subsequent feature fusion and signer identity matching, and improving the accuracy of signature identity verification.

[0067] It should be noted that the pen tip position is the position where the pen tip is projected onto the writing screen. In some embodiments, the pen tip position is (x, y), where x is the horizontal coordinate of the position where the pen tip is projected onto the writing screen, and y is the vertical coordinate of the position where the pen tip is projected onto the writing screen.

[0068] In some embodiments, a miniature camera or infrared sensor may be provided at the edge of the writing screen, and the electronic pen may be provided with preset optical markers, such as infrared LEDs (Light Emitting Diodes) or special reflective patterns. Images of the optical markers can be captured by the miniature camera, and then the pen tip position can be calculated using preset computer vision algorithms or triangulation methods.

[0069] It should be noted that pen tip pressure can be obtained in the following way: by acquiring the pen tip pressure value sent by the electronic pen. Specifically, the electronic pen can be an active stylus, meaning it integrates a pressure sensor. This sensor detects the pen tip pressure, obtains, and sends the pen tip pressure value.

[0070] It should be noted that the identifier data has two preset values. In some embodiments, the identifier data has two preset values: 0 and 1. When the identifier data is 0, it indicates that the pen tip is suspended in the air, that is, the pen tip is not in contact with the writing screen; when the identifier data is 1, it indicates that the pen tip has fallen, that is, the pen tip is in contact with the writing screen.

[0071] It should be noted that the labeling data can be determined by the pen tip pressure value. That is, when the pressure value is 0, 0 is designated as the labeling data. When the pressure value is not 0, 1 is designated as the labeling data.

[0072] The signature trajectory is the path of the electronic pen moving on the writing screen. It can represent not only the handwriting of the signature, but also the stroke order of the signature.

[0073] Furthermore, based on the pen tip position and pen tip state, the following steps are taken to obtain the aerial pen lifting trajectory features and pen falling trajectory features: determining the aerial position and pen falling position based on the pen tip state; connecting the aerial positions based on the acquisition order to obtain initial pen lifting trajectory data; normalizing the initial pen lifting trajectory data to obtain pen lifting trajectory data; extracting pen lifting trajectory information from the pen lifting trajectory data; merging the pen lifting trajectory information to obtain pen lifting trajectory features; connecting the pen falling positions based on the acquisition order to obtain initial pen falling trajectory data; normalizing the initial pen falling trajectory data to obtain pen falling trajectory data; and extracting pen falling trajectory features from the pen falling trajectory data.

[0074] It should be noted that the "air position" refers to the position of the pen tip when it is not in contact with the writing screen. The "pen placement position" refers to the position of the pen tip when it touches the writing screen.

[0075] It should be noted that extracting pen lifting trajectory information from pen lifting trajectory data means obtaining characteristic information of pen tip movement in the air, such as average speed of movement in the air, maximum acceleration, number of inflection points, and hovering time before pen touch, from the pen lifting trajectory data.

[0076] It should be noted that extracting stroke trajectory features from the stroke trajectory data involves using a pre-defined CNN (Convolutional Neural Network) and / or BiLSTM (Bidirectional Long Short-Term Memory) structure. Specifically, CNN can extract spatial geometric features from the stroke trajectory data, namely the spatial geometric features of stroke angles and inflection point positions. BiLSTM can extract temporal features from the stroke trajectory data, namely the temporal features of the start, middle, and end of the stroke. Stroke trajectory features include both spatial geometric features and temporal features.

[0077] Furthermore, the jitter features are extracted based on the pen tip position, including: determining the pen-falling position based on the pen tip state; concatenating the pen-falling positions according to the acquisition order to obtain initial pen-falling trajectory data; and performing wavelet decomposition or bandpass filtering on the pen-falling positions in the initial pen-falling trajectory data to obtain high-frequency components characterizing physiological micro-jitter. These high-frequency components are then identified as jitter features.

[0078] It should be noted that pressure timing features are obtained based on pen tip pressure values. That is, the pen tip pressure values ​​can be arranged according to the order in which they are obtained to obtain a pen tip pressure vector. This pen tip pressure vector is then determined as the pressure timing feature.

[0079] Furthermore, the signature behavior features are fused to obtain signature fusion features, including: performing linear mapping on the pen lifting trajectory features, jitter features, pen falling trajectory features, and pressure timing features respectively to obtain multiple features to be fused; splicing the features to be fused to obtain spliced ​​features; fusing the spliced ​​features using a self-attention mechanism to obtain a first fusion feature; performing a residual connection between the signature behavior features and the first fusion feature to obtain a second fusion feature; and normalizing the second fusion feature to obtain the signature fusion feature.

[0080] Thus, through a multi-level feature fusion architecture involving linear mapping, feature concatenation, self-attention fusion, residual connections, and normalization, a multi-stage progressive feature fusion logic is constructed. This architecture enables hierarchical deep fusion of four types of signature behavior features: air pen lifting trajectory features, jitter features, pen falling trajectory features, and pressure temporal features. This overcomes the limitations of simple, direct concatenation fusion, resulting in signature fusion features with stronger uniqueness, discriminability, and robustness, thereby improving the accuracy of subsequent signer-user identity matching.

[0081] In some embodiments, signature fusion features can be obtained by fusing signature behavior features through a preset multi-branch attention fusion model.

[0082] Specifically, such as Figure 2 As shown, Figure 2 This is a schematic diagram of a multi-branch attention fusion model. The multi-branch attention fusion model 200 includes multiple branch mapping layers, a splicing layer 201, an attention mechanism layer 202, a residual connection layer 203, and a normalization layer 204.

[0083] The branch mapping layers include a first branch mapping layer 205 corresponding to the air pen lifting trajectory feature, a second branch mapping layer 206 corresponding to the jitter feature, a third branch mapping layer 207 corresponding to the pen falling trajectory feature, and a fourth branch mapping layer 208 corresponding to the pressure timing feature. The air pen lifting trajectory feature is input into the first branch mapping layer for linear mapping to obtain the first feature to be fused. The jitter feature is input into the second branch mapping layer for linear mapping to obtain the second feature to be fused. The pen falling trajectory feature is input into the third branch mapping layer for linear mapping to obtain the third feature to be fused. The pressure timing feature is input into the fourth branch mapping layer for linear mapping to obtain the fourth feature to be fused. Then, the first, second, third, and fourth features to be fused are concatenated by a splicing layer to obtain a spliced ​​feature. The spliced ​​feature is input into an attention mechanism layer to fuse the spliced ​​feature using a self-attention mechanism to obtain the first fused feature. Then, the first fused feature and the signature behavior features (i.e., the air pen lifting trajectory feature, jitter feature, pen falling trajectory feature, and pressure timing feature) are input into a residual connection layer for residual connection to obtain the second fused feature. Finally, the second fusion feature is normalized through a normalization layer to obtain the signature fusion feature.

[0084] It should be noted that the multi-branch attention fusion model can be obtained by training a pre-set initial multi-branch attention fusion model using a contrastive learning algorithm. Specifically, the training signature behavior features corresponding to any user are used as positive samples, and the training signature behavior features corresponding to other users are used as negative samples. Then, a loss function is constructed with the objectives of maximizing the difference between the signature fusion features corresponding to positive samples and the signature fusion features corresponding to negative samples, and minimizing the difference among the signature fusion features corresponding to positive samples. This loss function is used to train the model parameters in the initial multi-branch attention fusion model, resulting in the multi-branch attention fusion model. This ensures that the outputs of the training signature behavior features corresponding to the same user are close to each other, while the outputs of the training signature behavior features corresponding to different users are far apart. The method for obtaining the training signature behavior features for each user is the same as the method for obtaining the signature behavior features described above, and will not be repeated here.

[0085] Furthermore, determining whether the signer and the user match based on the signature fusion features includes: obtaining the user signature features corresponding to the user; calculating the similarity between the user signature features and the signature fusion features; determining that the signer and the user match if the similarity is greater than or equal to a preset similarity threshold; and / or determining that the signer and the user do not match if the similarity is less than the preset similarity threshold.

[0086] In this way, by calculating the similarity between user signature features and signature fusion features, and matching the signer and the user based on this similarity, the accuracy and reliability of signature identity matching are guaranteed.

[0087] It should be noted that the user signature features corresponding to a user are the same as the user's training signature behavior features.

[0088] Furthermore, after executing an operation request, if the permission successfully matched by the operation request is a preset flow permission, the current process node of the target emergency repair process is changed to the next process node. This achieves a process transition, which facilitates the smooth progress of the target emergency repair process.

[0089] Combination Figure 3 As shown in the figure, this disclosure provides a process control device 300 for emergency repair of communication faults. The device includes: an establishment module 301, a node determination module 302, a role determination module 303, a permission determination module 304, a matching module 305, and an execution module 306.

[0090] Module 301 is configured to establish a first mapping relationship between users and roles in a preset emergency repair business process; and to establish a second mapping relationship between roles, process nodes, and permissions.

[0091] The node determination module 302 is configured to determine the current process node of the target emergency repair process in response to a user-initiated operation request for the target emergency repair process.

[0092] The role determination module 303 is configured to determine the user's role based on a first mapping relationship;

[0093] The permission determination module 304 is configured to determine the permissions that a role has in the current process node based on the second mapping relationship;

[0094] Matching module 305 is configured to verify whether the operation request is successfully matched with the permissions of the current process node.

[0095] Execution module 306 is configured to execute the operation request if a match is successful.

[0096] The communication fault repair process control device provided in this embodiment establishes a first mapping relationship between users and roles, and a second mapping relationship between roles, process nodes, and permissions within a preset repair process. Then, based on the first mapping relationship, the user's role is determined, and based on the second mapping relationship, the permissions of the role at the current process node are determined. The device verifies whether the operation request matches the permissions of the current process node, and if a match is successful, the operation request is executed. Thus, a four-dimensional association system between users, roles, process nodes, and permissions in the repair process is constructed through the first and second mapping relationships. When a user initiates a target repair process operation request, the current process node of the target repair process is determined. Based on the four-dimensional association system of users, roles, process nodes, and permissions constructed through the first and second mapping relationships, the user's role is determined, and the operation request matches the permissions of the current process node. If a match is successful, the operation request is executed. It achieves refined control based on process nodes, enabling different roles to have different operating permissions at different process nodes, effectively preventing unauthorized operations, thereby improving the standardization of process control and thus improving emergency repair efficiency.

[0097] Furthermore, the permission determination module determines the permissions of a role in the current process node based on the second mapping relationship in the following way: if the user's role is the preset emergency repair personnel role, the user's geographical location is obtained; if the geographical location is the preset emergency repair location, the permissions of the role in the current process node are determined in the second mapping relationship.

[0098] Furthermore, the process control device for emergency repair of communication faults also includes a user identification module. The user identification module is configured to, before responding to a user-initiated operation request for the target emergency repair process, acquire the operator's initial biometric features; perform a search operation on the initial biometric features in a preset biometric database; if the search is successful, identify the operator as a staff member; then generate a dynamic verification code and acquire the communication device corresponding to the staff member; send the dynamic verification code to the communication device; acquire the coded data input by the operator; and if the coded data matches the dynamic verification code, identify the operator as a user.

[0099] Furthermore, the process control device for emergency repair of communication faults also includes a signature verification module. The signature verification module is configured to, upon executing an operation request, respond to a preset signature operation and acquire signature behavior characteristics. These characteristics include air pen lifting trajectory features, jitter features, pen falling trajectory features, and pressure timing features. The signature behavior characteristics are then fused to obtain a signature fusion feature. Based on the signature fusion feature, it is determined whether the signer and user match. If the signer and user do not match, the user's operation request is revoked.

[0100] Furthermore, the signature operation is the operation of signing on a preset writing screen using a preset electronic pen; the signature verification module is configured to obtain signature behavior characteristics in the following ways: during the signing process, the pen tip position, pen tip pressure value, and pen tip state are obtained at preset intervals; the pen tip state is the identification data used to indicate whether the pen tip of the electronic pen is in contact with the writing screen; the pen lifting trajectory characteristics and pen falling trajectory characteristics are obtained based on the pen tip position and pen tip state; the jitter characteristics are extracted based on the pen tip position; and the pressure timing characteristics are obtained based on the pen tip pressure value.

[0101] Furthermore, the signature verification module is configured to fuse signature behavior features to obtain signature fusion features in the following manner: linearly mapping the air pen lifting trajectory features, jitter features, pen falling trajectory features, and pressure timing features to obtain multiple features to be fused; concatenating the features to be fused to obtain concatenated features; fusing the concatenated features using a self-attention mechanism to obtain a first fusion feature; performing a residual connection between the signature behavior features and the first fusion feature to obtain a second fusion feature; and normalizing the second fusion feature to obtain the signature fusion feature.

[0102] Furthermore, the signature verification module is configured to determine whether the signer and the user match based on the signature fusion features in the following manner: obtaining the user signature features corresponding to the user; calculating the similarity between the user signature features and the signature fusion features; determining that the signer and the user match if the similarity is greater than or equal to a preset similarity threshold; and / or determining that the signer and the user do not match if the similarity is less than the preset similarity threshold.

[0103] Combination Figure 4 As shown, this embodiment of the present disclosure provides an electronic device 400, including a processor 401 and a memory 402. Optionally, the device may further include a communication interface 403 and a bus 404. The processor 401, communication interface 403, and memory 402 can communicate with each other via the bus 404. The communication interface 403 can be used for information transmission. The processor 401 can call logical instructions in the memory 402 to execute the above-mentioned... Figure 1The process control method shown is based on emergency repair of communication faults.

[0104] Furthermore, the logical instructions in the aforementioned memory 402 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium.

[0105] The memory 402, as a storage medium, can be used to store software programs and computer-executable programs, such as program instructions / modules corresponding to the methods in this embodiment. The processor 401 executes functional applications and data processing by running the program instructions / modules stored in the memory 402, thus achieving the above-described functionality. Figure 1 The process control method shown is based on emergency repair of communication faults.

[0106] The memory 402 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 402 may include high-speed random access memory and may also include non-volatile memory.

[0107] In some embodiments, the electronic device may be equipped with a biometric acquisition module. This biometric acquisition module can acquire one or more of the following: fingerprint features, facial features, voiceprint features, etc.

[0108] The electronic device has a writing screen. It can also communicate with an electronic pen to respond to preset signature operations and acquire signature behavior characteristics when a user signs. These characteristics include air pen lifting trajectory features, jitter features, pen falling trajectory features, and pressure timing features. The signature behavior characteristics are then fused to obtain a signature fusion feature. Based on this signature fusion feature, it is determined whether the signer and user match. If the signer and user do not match, the user's operation request is revoked.

[0109] This disclosure provides a storage medium storing computer-executable instructions configured to execute the aforementioned process control method for emergency repair of communication faults.

[0110] The aforementioned storage media can be either transient computer-readable storage media or non-transitory computer-readable storage media. Non-transitory storage media include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and can also be transient storage media.

[0111] The foregoing description and accompanying drawings fully illustrate embodiments of this disclosure to enable those skilled in the art to practice them. Other embodiments may include structural, logical, electrical, procedural, and other changes. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the order of operation may vary. Parts and features of some embodiments may be included in or replace parts and features of other embodiments. Moreover, the terminology used in this application is for describing embodiments only and is not intended to limit the claims. As used in the description of embodiments and claims, the singular forms “a,” “an,” and “the” are intended to equally include the plural forms unless the context clearly indicates otherwise. Similarly, the term “and / or” as used in this application means including one or more of the associated listed items and all possible combinations thereof. Additionally, when used in this application, the term "comprise" and its variations "comprises" and / or "comprising" refer to the presence of stated features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof. Without further limitations, an element defined by the phrase "comprises a..." does not exclude the presence of other identical elements in the process, method, or apparatus that includes said element. In this document, each embodiment may focus on the differences from other embodiments, and similar or identical parts between embodiments can be referred to mutually. For methods, products, etc., disclosed in the embodiments, if they correspond to the method section disclosed in the embodiments, the relevant parts can be referred to the description of the method section.

[0112] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this disclosure. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0113] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than that shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. In the descriptions corresponding to the flowcharts and block diagrams in the accompanying drawings, the operations or steps corresponding to different blocks may also occur in a different order than disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. Each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

Claims

1. A process control method for emergency repair of communication faults, characterized in that, include: In the pre-defined emergency repair process, establish the initial mapping relationship between users and roles; Establish a second mapping relationship between roles, process nodes, and permissions; In response to a user-initiated operation request for a target emergency repair process, determine the current process node of the target emergency repair process; The user's role is determined based on the first mapping relationship; The permissions that the role has in the current process node are determined based on the second mapping relationship; Verify whether the operation request matches the permissions of the current process node. If a match is successfully found, the operation request is executed.

2. The method according to claim 1, characterized in that, Determining the permissions that the role has in the current process node based on the second mapping relationship includes: If the user's role is a preset emergency repair personnel role, determine whether the address identification information sent by the beacon device at the preset emergency repair location has been received; Upon receiving the address identification information, the permissions that the role has in the current process node are determined in the second mapping relationship.

3. The method according to claim 1, characterized in that, Prior to responding to a user-initiated operation request for the target emergency repair process, the method further includes: Acquire the operator's initial biometrics; Perform a search operation on the initial biometric features in the preset biometric database; If the search is successful, the operator is identified as a staff member; then a dynamic verification code is generated, and the communication device corresponding to the staff member is obtained; Send the dynamic verification code to the communication device; Obtain the coded data input by the operator; If the encoded data is the same as the dynamic verification code, the operator is identified as a user.

4. The method according to claim 1, characterized in that, After executing the operation request, the method further includes: In response to a preset signature operation, signature behavior features are obtained; the signature behavior features include air pen lifting trajectory features, shaking features, pen falling trajectory features and pressure timing features during the signature; By fusing the aforementioned signature behavior features, a signature fusion feature is obtained; Based on the signature fusion features, determine whether the signer matches the user; If the signer and the user do not match, the user's operation request is revoked.

5. The method according to claim 4, characterized in that, The signature operation is the act of signing on a preset writing screen using a preset electronic pen; the acquisition of signature behavior characteristics includes: During the signing process, the pen tip position, pen tip pressure value, and pen tip status are acquired at preset intervals; the pen tip status is identification data used to indicate whether the pen tip of the electronic pen is in contact with the writing screen. Based on the pen tip position and the pen tip state, the aerial pen lifting trajectory features and pen falling trajectory features are obtained; The jitter feature is extracted based on the pen tip position; The pressure timing features are obtained based on the pen tip pressure value.

6. The method according to claim 4, characterized in that, The process of fusing the signature behavior features to obtain signature fusion features includes: Linear mapping is performed on the air pen lifting trajectory feature, the shaking feature, the pen falling trajectory feature, and the pressure timing feature to obtain multiple features to be fused; By splicing together the features to be fused, the spliced ​​features are obtained; The splicing features are fused using a self-attention mechanism to obtain a first fused feature; The signature behavior feature is residually connected with the first fusion feature to obtain the second fusion feature; The second fusion feature is normalized to obtain the signature fusion feature.

7. The method according to claim 4, characterized in that, The step of determining whether the signer and the user match based on the signature fusion features includes: Obtain the user signature characteristics corresponding to the user; Calculate the similarity between the user signature features and the signature fusion features; If the similarity is greater than or equal to a preset similarity threshold, the signer is determined to match the user; and / or, if the similarity is less than the preset similarity threshold, the signer is determined to not match the user.

8. A process control device for emergency repair of communication faults, characterized in that, include: The module is configured to establish the initial mapping relationship between users and roles in a preset emergency repair business process. Establish a second mapping relationship between roles, process nodes, and permissions; The node determination module is configured to determine the current process node of the target emergency repair process in response to a user-initiated operation request for the target emergency repair process. The role determination module is configured to determine the role to which the user belongs based on a first mapping relationship; The permission determination module is configured to determine the permissions that the role has in the current process node based on the second mapping relationship; The matching module is configured to verify whether the operation request is successfully matched with the permissions of the current process node; The execution module is configured to execute the operation request if a match is successfully found.

9. An electronic device comprising a processor and a memory storing program instructions, characterized in that, The processor is configured to execute the process control method for emergency repair of communication faults as described in any one of claims 1 to 7 when running the program instructions.

10. A storage medium storing program instructions, characterized in that, When the program instructions are executed, they perform the process control method based on emergency repair of communication faults as described in any one of claims 1 to 7.

Images