Method, device and equipment for flow of repair work order based on role-based access control

Abstract

The application discloses a kind of based on role access control's rush repair work order's flow method, device and equipment, it is related to network operation technical field.The method includes obtaining the location information of rush repair user, current time information and the electronic signature information of rush repair user;After determining that the electronic signature information is valid, according to the process node where the rush repair work order is located, the location matching degree, time matching degree and role matching degree of rush repair user are determined respectively;And determine the dynamic permission score representing the comprehensive trust degree of rush repair user;When dynamic permission score is greater than the dynamic authorization threshold generated in advance, the reporting permission of the rush repair work order of the rush repair user is unlocked;Rush repair work order data reported by rush repair user is obtained, rush repair work order data is sent to micro-service cloud, and the current process node is ended.The role trust of rush repair user is evaluated by synthesizing role, location and time, and the control granularity of rush repair personnel work order reporting permission is refined.

Description

Technical Field

[0001] This invention relates to the field of network operation and maintenance technology, specifically to a method, apparatus, and equipment for the flow of emergency repair work orders based on role-based access control. Background Technology

[0002] The workflow of emergency repair work orders is a key link in communication operation and maintenance management. With the popularization of mobile emergency repair operations and the application of cloud microservice architecture, in order to ensure the timeliness, on-site performance, and data consistency of the emergency repair process, on-site information is usually collected through mobile terminals and the work order data is uploaded to the back-end system to complete the workflow processing.

[0003] In the existing process of handling emergency repair work orders for communication faults, the control of work order submission permissions is usually achieved by directly assigning permissions to fixed roles. While this approach is easy to implement, it is difficult to take into account on-site constraints such as whether the repair personnel are actually present and whether they are working within the specified response time limit. The control over repair personnel is not detailed enough, which can easily lead to false submission of repair work orders and affect the normal execution of repair operations. Summary of the Invention

[0004] The purpose of this invention is to provide a method, apparatus, and equipment for the flow of emergency repair work orders based on role access control. By comprehensively evaluating the role credibility of emergency repair users based on role, location, and time, it solves the problem of insufficient fine-grained control over the existing permissions of emergency repair personnel to fill in work orders.

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

[0006] The first aspect of this application provides a method for handling emergency repair work orders based on role-based access control, applied to a mobile terminal, the method comprising:

[0007] Obtain the location information, current time information, and electronic signature information of the emergency repair user;

[0008] After determining that the electronic signature information is valid, based on the process node where the emergency repair work order is located, the location matching degree between the location information and the location of the faulty equipment corresponding to the process node, the time matching degree between the current time information and the specified response time corresponding to the process node, and the role matching degree between the role to which the emergency repair user belongs and the handling role corresponding to the process node are determined respectively.

[0009] The location matching degree, time matching degree and role matching degree are weighted and fused to determine the dynamic permission score that represents the overall trustworthiness of the emergency repair user;

[0010] When the dynamic permission score is greater than the pre-generated dynamic authorization threshold, the emergency repair user's permission to fill in the emergency repair work order is unlocked;

[0011] Obtain the emergency repair work order data filled in by the emergency repair user, and send the emergency repair work order data to the microservice cloud so that the microservice cloud can update the database, generate an emergency repair processing report, and end the current process node based on the emergency repair work order data.

[0012] In one feasible implementation, the method further includes: determining the validity of the electronic signature based on the electronic signature information, specifically including:

[0013] Obtain the electronic signature information of the emergency repair user; the electronic signature information includes the pressure value of each sampling point in the touch pressure data generated by the touch screen during the signing process, the average pressure value of this signature, the total number of sampling points touched by the signature trajectory, as well as the historical average signature time of the emergency repair user, the signature time of this signature, and the preset standard pressure fluctuation threshold.

[0014] Based on the pressure values ​​of each sampling point, the average pressure, the total number of sampling points, and the standard pressure fluctuation threshold, a first pressure calculation parameter is determined; the first pressure calculation parameter characterizes the degree of difference between the pressure fluctuation of this signature and the standard pressure fluctuation threshold.

[0015] Based on the historical average signature time and the current signature time, a first time calculation parameter is determined; the first time calculation parameter characterizes the reasonableness of the signature duration.

[0016] Based on the first pressure calculation parameter and the first time consumption calculation parameter, a comprehensive signature verification value for quantifying the validity of the signature is determined;

[0017] When the comprehensive signature verification value is not less than the preset verification threshold, and the number of abnormal pressure points exceeding the standard pressure fluctuation threshold meets the preset ratio condition, the electronic signature is determined to be valid.

[0018] In one feasible implementation, the time matching degree is determined in the following way:

[0019] Calculate the first difference between the current time information and the work order dispatch time. If the first difference is not greater than the specified response time, the time matching degree is a preset fixed value.

[0020] If the first difference is greater than the specified response time, then calculate the second difference between the preset fixed value and the time penalty coefficient multiplied by the timeout duration;

[0021] If the second difference is less than zero, the time matching degree is zero; otherwise, the time matching degree is the second difference.

[0022] In one feasible implementation, obtaining the emergency repair work order data submitted by the emergency repair user and sending the emergency repair work order data to the microservice cloud includes:

[0023] Send the emergency repair work order data to the microservice cloud;

[0024] Monitor the network packet loss rate during transmission. If the network packet loss rate is not less than a preset first packet loss threshold and the duration exceeds a preset time window, then interrupt data transmission.

[0025] When the network packet loss rate is detected to be no greater than the preset second packet loss rate threshold, the interrupted transmission is resumed, and the emergency repair work order data is sent to the microservice cloud.

[0026] In one feasible implementation, obtaining the emergency repair work order data submitted by the emergency repair user and sending the emergency repair work order data to the microservice cloud further includes:

[0027] The emergency repair work order data is divided into multiple data blocks, and the block verification value of each data block and the total verification value of the emergency repair work order data are generated.

[0028] The block verification value and the total verification value are sent to the microservice cloud along with the emergency repair work order data;

[0029] Receive the retransmission request for the target data block from the microservice cloud and resend the target data block;

[0030] The determination of the target data block includes: comparing the received total verification value with the total verification value through the microservice cloud; if the two are not equal, the target data block that failed to be received is determined by comparing the verification values ​​of each received block with the total verification value; the total verification value is determined by the verification values ​​of each data block received by the microservice cloud.

[0031] The second aspect of this application provides a method for handling emergency repair work orders based on role-based access control, applied to a microservice cloud platform. The method includes:

[0032] Receive emergency repair work order data sent by mobile terminals;

[0033] The process node ends when the database is updated based on the emergency repair work order data and an emergency repair processing report is generated.

[0034] In one feasible implementation, the database is updated based on the emergency repair work order data, and an emergency repair processing report is generated, including:

[0035] Extract fault description information, fault assessment information, and emergency repair work order identifier from the emergency repair work order data;

[0036] The extracted fault phenomenon description information and fault judgment information are written into the emergency repair order table of the database, and the status of the emergency repair work order is updated.

[0037] Update the status of damaged resources in the associated business resource table of the database according to the emergency repair work order identifier;

[0038] Extract the form fields from the emergency repair order table, as well as the text content extracted based on character recognition;

[0039] According to the preset text concatenation rules, the form fields and the text content are concatenated to generate an emergency repair report.

[0040] A third aspect of this application provides a workflow device for emergency repair work orders based on role-based access control, comprising:

[0041] The user information acquisition unit is used to acquire the location information, current time information, and electronic signature information of the emergency repair user.

[0042] The matching degree determination unit is used to determine, after determining that the electronic signature information is valid, the location matching degree between the location information and the location of the faulty equipment corresponding to the process node, the time matching degree between the current time information and the specified response time corresponding to the process node, and the role matching degree between the role of the emergency repair user and the handling role corresponding to the process node, according to the process node where the emergency repair work order is located.

[0043] The user trust measurement unit is used to perform weighted fusion of the location matching degree, time matching degree and role matching degree to determine the dynamic permission score that represents the overall trustworthiness of the emergency repair user.

[0044] The permission unlocking unit is used to unlock the emergency repair user's permission to fill in the emergency repair work order when the dynamic permission score is greater than the pre-generated dynamic authorization threshold.

[0045] The work order data sending unit is used to obtain the emergency repair work order data filled in by the emergency repair user, and send the emergency repair work order data to the microservice cloud so that the microservice cloud can update the database, generate an emergency repair processing report and end the current process node based on the emergency repair work order data.

[0046] The fourth aspect of this application provides a workflow device for emergency repair work orders based on role-based access control, including:

[0047] The work order data receiving unit is used to receive emergency repair work order data sent by the mobile terminal;

[0048] The node flow unit updates the database based on the emergency repair work order data, generates an emergency repair processing report, and terminates the process node.

[0049] A fifth aspect of this application provides an electronic device, including: a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the above-described method.

[0050] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0051] In this embodiment, after determining the validity of the electronic signature of the emergency repair user, the matching degree of role, location, and time with the current process node is used as an influencing factor to quantify the overall trustworthiness of the emergency repair user. While considering the authorized user role, precise authorization is achieved by process node and by spatiotemporal conditions, which refines the control granularity of the emergency repair user's work order filling permission, avoids off-site users or users who have exceeded the time limit from directly obtaining the ability to fill in the form, and improves the reliability of the generated emergency repair work order data. Attached Figure Description

[0052] 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:

[0053] Figure 1 A flowchart illustrating a method for handling emergency repair work orders based on role-based access control, provided in Embodiment 1 of this application;

[0054] Figure 2 This is a flowchart illustrating a method for handling emergency repair work orders based on role-based access control, as provided in Embodiment 2 of this application.

[0055] Figure 3 This is a schematic diagram of the structure of a role-based access control-based emergency repair work order processing device provided in Embodiment 3 of this application;

[0056] Figure 4 This is a schematic diagram of the structure of a role-based access control-based emergency repair work order processing device provided in Embodiment 4 of this application.

[0057] Figure 5 This is a schematic diagram of the structure of a computing device provided in Embodiment 5 of this application. Detailed Implementation

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

[0059] As will be known to those skilled in the art, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0060] The terms “comprising” and “having”, and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, product, or apparatus.

[0061] First, it should be noted that the transfer method in this application is an implementation scheme for end-to-cloud interaction. The transfer method will be introduced from the perspectives of mobile terminal and microservice cloud respectively.

[0062] Example 1:

[0063] Embodiment 1 of this application provides a method for the flow of emergency repair work orders based on role-based access control, applied to mobile terminals, to solve the problem that the existing control over the work order filling permissions of emergency repair personnel is not granular enough.

[0064] The subject executing this method can be any computing device capable of implementing the method, such as mobile phones, personal computers, smart wearable devices, smart robots, and so on.

[0065] Furthermore, the embodiments of this application do not limit the execution order of different steps. When using the method provided in the embodiments of this application, the execution order of different steps can be adjusted according to actual needs.

[0066] For ease of description, the following uses a role-based access control-based emergency repair work order processing device as the execution subject of this method to provide a detailed description of the method provided in this application embodiment.

[0067] like Figure 1 The diagram shown is a flowchart illustrating the specific implementation of a role-based access control-based emergency repair work order processing method according to an embodiment of this application, including the following steps 11-15:

[0068] Step 11: Obtain the location information, current time information, and electronic signature information of the emergency repair user.

[0069] The mobile terminal determines the location information of the currently logged-in emergency repair user by obtaining the actual location coordinates of the user, specifically the location coordinates corresponding to the time the terminal collects the data and processes the work order; and determines the current time information by obtaining the time when the emergency repair user collects the on-site data.

[0070] In one feasible implementation, in addition to acquiring location and time information, the mobile terminal in this embodiment also acquires environmental variables and service data collected by the repair user at the repair site. The environmental variables, besides the aforementioned location and real-time time information, may also include data related to the mobile terminal and the site context, such as the mobile terminal's signal strength. The service data, besides the aforementioned electronic signature information, also includes site content directly associated with the current repair work order, such as site images and fault descriptions collected by the repair user.

[0071] In addition, the mobile terminal can also collect on-site images and fault descriptions of faulty equipment, and use character recognition programs to identify on-site images to extract faulty equipment nameplate information, which is then added to the business data along with electronic signature touch pressure data.

[0072] On-site images refer to images taken of the faulty equipment, its surrounding environment, or the work site; fault descriptions refer to the on-site text descriptions filled in by the repair user on the terminal; faulty equipment nameplate information refers to the text content of the equipment extracted from the on-site images through a character recognition program, such as equipment name, equipment number, and other identification information.

[0073] Specifically, the mobile terminal can receive the work order identifier and the current process node information of the current emergency repair work order through the network session already established on the application side, and create a data object corresponding to the work order identifier in the local memory of the terminal, and write environment variables and business data into the data object for subsequent verification process to read.

[0074] Among them, process nodes refer to the business stages in the work order processing process, such as initiation, approval, execution, and acceptance.

[0075] In this implementation, data collection and classification are completed on the mobile terminal side, and the association between signature data, image data, work order context and other data and work order identifiers is established to avoid object mismatch in subsequent authorization calculation and work order filling; the unified organization of input data can be achieved based on terminal-side data collection to avoid the association break caused by independent processing of data from different sources.

[0076] Step 12: After determining that the electronic signature information is valid, based on the process node where the emergency repair work order is located, determine the location matching degree between the location information and the location of the faulty equipment corresponding to the process node, the time matching degree between the current time information and the specified response time corresponding to the process node, and the role matching degree between the role to which the emergency repair user belongs and the handling role corresponding to the process node.

[0077] In one feasible implementation, before performing this step, the validity of the electronic signature is determined based on the electronic signature information, specifically including the following steps 101-105:

[0078] Step 101: Obtain the electronic signature information of the emergency repair user; the electronic signature information includes the pressure value of each sampling point in the touch pressure data generated on the touch screen during the signing process, the average pressure value of this signature, the total number of sampling points touched by the signature trajectory, as well as the historical average signature time of the emergency repair user, the signature time of this signature, and the preset standard pressure fluctuation threshold.

[0079] Among them, touch pressure data refers to the sequence of pressure values ​​continuously recorded by the pressure-sensing screen of the mobile terminal during the signing process according to sampling points, such as the pressure changes corresponding to the starting, turning and ending stages of the signature.

[0080] Step 102: Based on the pressure values ​​of each sampling point, the average pressure, the total number of sampling points, and the standard pressure fluctuation threshold, determine the first pressure calculation parameter; the first pressure calculation parameter characterizes the degree of difference between the pressure fluctuation of this signature and the standard pressure fluctuation threshold.

[0081] First pressure calculation parameters The expression is:

[0082] ;

[0083] In the formula, Indicates the first The real-time pressure value of each sampling point refers to the actual pressure applied to the screen by a finger or stylus at a certain instant during the signature process; The average pressure value reflects the center value of the overall force level applied during this signature process; N represents the number of valid samples participating in the pressure fluctuation assessment, i.e., the total number of signature trajectory sampling points. This indicates the standard pressure fluctuation threshold.

[0084] From this, we obtain The numerical value is positively correlated with the degree to which the local pressure fluctuations of this signature deviate from historical habits.

[0085] Step 103: Based on the historical average signature time and the current signature time, determine the first time calculation parameter; the first time calculation parameter characterizes the rationality of the signature duration.

[0086] This step is used to further assess whether the signature duration is normal, by calculating the total signature time t of this signature and the historical average signature time. The absolute difference, divided by the historical average signature time. The first time-consuming calculation parameter is obtained, denoted as :

[0087] = ;

[0088] The total signing time represents the duration from the first touch to the final lift of the pen; the historical average signing time represents a reference time scale for the user's typical signing rhythm; thus, the... This is used to reflect the degree of deviation between the current signing rhythm and the historical rhythm.

[0089] Step 104: Based on the first pressure calculation parameter and the first time consumption calculation parameter, determine the comprehensive signature verification value for quantifying the validity of the signature.

[0090] Comprehensive signature verification value The expression is:

[0091] ;

[0092] In the formula, Represented by natural constant An exponential function with base 0. This is used to map the degree of deviation from pressure fluctuations into a decay term, indicating that the degree of pressure fluctuation anomaly is negatively correlated with credibility. This is used to map the degree of deviation in time consumption to a correction term, indicating that the degree to which the signature rhythm is close to historical habits is positively correlated with credibility.

[0093] Signature comprehensive verification value This characterizes the degree to which this signature simultaneously satisfies historical behavioral characteristics in terms of both force application mode and operational rhythm.

[0094] Step 105: When the comprehensive signature verification value is not less than the preset verification threshold and the number of abnormal pressure points exceeding the standard pressure fluctuation threshold meets the preset ratio condition, the electronic signature is determined to be valid.

[0095] The signature comprehensive verification value is compared with the verification threshold generated based on historical data, and the number of consecutive abnormal pressure points with pressure values ​​exceeding the preset standard threshold is counted. When the signature comprehensive verification value is not lower than the verification threshold and the number of consecutive abnormal pressure points is less than the preset proportion of the total number of signature trajectory sampling points, the signature is determined to be valid; otherwise, the canvas is cleared and a re-signing instruction is triggered. The preset proportion is a pre-set value.

[0096] In this implementation, the authenticity of the signature is quantified by the coordinated changes in pressure fluctuations and signature time. This transforms the traditional evaluation method that relies solely on static trajectory patterns into a constraint mechanism that simultaneously judges the dynamic generation process, making it more suitable for the business scenario of on-site signing on mobile terminals. The authenticity of the signature can be determined based on the joint calculation of pressure variance and time consumption, preventing forged signatures from directly entering the work order process.

[0097] Location matching degree measures the degree of correspondence between the location of the repair user and the location of the faulty equipment (such as a faulty base station). It is calculated by squared and negatively dividing the physical distance *d* between the repair user's location information and the coordinates of the faulty base station by twice the square of the maximum allowable repair radius *D*, and then calculating its natural exponent. The result is denoted as […]. :

[0098] =exp( );

[0099] Wherein, the physical distance d represents the proximity between the user's current location and the actual fault operation area; the maximum emergency repair radius D represents the on-site operation space range recognized by the system, and its value can be configured to a preset distance scale according to business rules; location matching degree The spatial constraint calculation results for emergency repair users serve as the basis for characterizing the reliability of authorization based on the location of the emergency repair user; distance is negatively correlated with the corresponding contribution of spatial constraints.

[0100] Time matching degree This is used to measure the timeliness of a user's arrival within the response cycle, and characterizes the time constraint calculation result of the emergency repair user; it is determined in the following way:

[0101] Calculate the first difference between the current time information and the work order dispatch time. If the first difference is not greater than the specified response time, then the time matching degree is... The first difference is a preset fixed value; if the first difference is greater than the specified response time, then the second difference is calculated between the preset fixed value and the time penalty coefficient multiplied by the timeout duration; if the second difference is less than zero, then the time matching degree... The time matching degree is zero; otherwise, it is zero. This is the second difference.

[0102] Here, the preset fixed value represents the maximum calculation benchmark value of the time dimension given when arriving on time within the specified response period, and the time penalty coefficient represents the attenuation ratio of the authorization score due to timeout. Its physical meaning is to map the scheduling response timeliness requirement to the time constraint in the permission assessment. When the second difference is less than zero, it is truncated to zero to avoid the timeout duration exceeding the preset safety threshold, which would cause the permission score to have an unexpected infinite negative bias.

[0103] To ensure consistency in the dimensions of the final dynamic permission score, the time penalty coefficient is set to the reciprocal of time to offset the time dimension of the timeout duration and ensure time matching. It is a dimensionless numerical value.

[0104] Role matching score measures the degree of role suitability, determining whether the emergency repair user possesses the target role required for the current process node. It also numerically represents whether the previous emergency repair user possessed the target role required for this process node: if so, the role matching score is calculated as follows: Take the first preset value; if it is not available, take the second preset value. The first preset value can represent the positive contribution when the character meets the node requirements, and the second preset value can represent the low contribution or no contribution when the character does not meet the requirements.

[0105] The above defines the location matching degree, which reflects the authenticity of on-site presence; the time matching degree, which reflects the timeliness of response; and the role matching degree, which reflects whether the role of the emergency repair user meets the responsibilities of the node business.

[0106] Step 13: Perform a weighted fusion of the location matching degree, time matching degree, and role matching degree to determine a dynamic permission score that represents the overall trustworthiness of the emergency repair user.

[0107] Role matching, location matching, and time matching are each assigned a corresponding weight to balance the actual impact of role compliance, on-site proximity, and response time in emergency repair operations. , , Multiply and sum to obtain the dynamic permission score. The sum of each weight can be set as a fixed normalized value.

[0108] .

[0109] In one feasible implementation, the calculation of dynamic permission scores can also be performed in the microservice cloud. Specifically, the mobile terminal can encapsulate the current location information, current time information, and current work order identifier into a structured message and send it to the authentication processing part of the microservice cloud through the established data transmission channel. The microservice cloud reads the coordinates of the faulty base station associated with the work order identifier, the work order dispatch time, the specified response time, and the current node role requirements from memory, and completes the calculation of dynamic permission scores according to the logic of steps 12 and 13 above.

[0110] Step 14: When the dynamic permission score is greater than the pre-generated dynamic authorization threshold, unlock the emergency repair user's permission to fill in the emergency repair work order.

[0111] If the dynamic permission score is greater than the dynamic authorization threshold generated based on historical authorization data, a temporary access credential will be issued to the mobile terminal through the microservice cloud to unlock the current emergency repair work order's submission permission; if it is not greater than the dynamic authorization threshold, the submission entry will not be unlocked.

[0112] The above approach incorporates three types of constraints—role, location, and time—into the assessment of emergency repair user credibility. A quantitative assessment mechanism enables precise authorization based on process nodes and spatiotemporal conditions, thereby transforming the problem of unauthorized access in the static role model into a dynamic authorization mechanism under on-site condition constraints. Dynamic access control is achieved through joint calculation of spatiotemporal constraints and role matching, preventing off-site users or users who have exceeded the time limit from directly obtaining the ability to fill in information.

[0113] When filling out an emergency repair work order, users can use a character recognition program to perform text recognition on the on-site images collected in step 11, and then add the identified information such as the nameplate of the faulty equipment to the emergency repair work order.

[0114] In step 11, the collected on-site images and character recognition results are incorporated into the business data, enabling information such as equipment nameplates that are easily missed or incorrectly filled in to be extracted from the images and supplemented into the work order context, thereby reducing the incompleteness problem of manual data entry. The complete collection of on-site business data can be achieved based on the collection of terminal-side environmental variables, image acquisition, and character recognition supplementation, avoiding the loss of key equipment information due to manual description alone.

[0115] Step 15: Obtain the emergency repair work order data filled in by the emergency repair user, and send the emergency repair work order data to the microservice cloud so that the microservice cloud can update the database, generate an emergency repair processing report, and end the current process node based on the emergency repair work order data.

[0116] After obtaining the emergency repair work order data submitted by the user, the emergency repair work order data is processed as follows:

[0117] The emergency repair work order data is divided into multiple data blocks, and a block check value and a total check value of the emergency repair work order data are generated for each data block. The block check value and the total check value are sent to the microservice cloud along with the emergency repair work order data.

[0118] Specifically, the mobile terminal organizes the emergency repair work order data into blocks and adds millisecond-level timestamps based on the data content filled in by the emergency repair user, generating a sequence of data blocks to be transmitted and its basic verification data.

[0119] The emergency repair work order data includes form fields and text content. Form fields refer to structured input items, such as fault symptoms and work order identifiers; text content refers to descriptive content entered on-site, such as fault descriptions and analysis explanations.

[0120] The mobile terminal serializes the emergency repair work order data into a transmittable data body and divides it into multiple data blocks according to a preset block division strategy. Each data block is written to the local transmission buffer with a millisecond-level timestamp attached, which is used for subsequent block verification calculation and retransmission location.

[0121] This embodiment splits the same emergency repair work order data into multiple locationable and verifiable data blocks, so that subsequent transmission anomalies can no longer only be retransmitted as a whole order, but can be handled for specific missing segments; verifiable transmission preparation of work order data can be achieved based on block organization, avoiding the complete failure of uploading the whole package under weak network conditions.

[0122] Among them, the block check value of each data block It can be calculated in the following ways:

[0123] ;

[0124] in, This indicates the first [item] extracted from the current emergency repair work order data. The data blocks formed by the actual transmitted content of a segment. Represents a block of computed data Cyclic redundancy check value, The millisecond-level timestamp is appended to this data block. This indicates that a modulo operation is performed on a preset prime number. The formula XORs the cyclic redundancy check value with a millisecond-level timestamp to reduce the possibility of duplicate local checks due to identical content in different data blocks. The XOR result is mapped to a modulo base within a stable numerical range to suppress collision risks under direct linear accumulation, ultimately yielding the block check value for each data block. .

[0125] The total checksum is obtained by summing all the block checksums to get the overall checksum of the sender, which is used for comparison with the recalculated result at the receiver. The specific calculation formula is as follows:

[0126] ;

[0127] in, This represents the total number of data blocks after the current work order has been split.

[0128] This embodiment does not perform a comprehensive judgment on the entire data, but incorporates the content characteristics and generation sequence of each data block into block-by-block verification to obtain a total verification basis that can be traced block by block. On this basis, if partial loss or disorder of sequence occurs during data transmission, the specific segment can be traced back through the block verification value.

[0129] This embodiment can achieve finer-grained data integrity constraints based on a combination of block check values ​​and total check values, avoiding the defect of data verification that can only detect errors but cannot locate them under weak network conditions.

[0130] To transmit emergency repair work order data, a data transmission channel is established between the mobile terminal and the microservice cloud. Based on the network status, the data block sequence is sent, monitored, and the results are verified to generate cloud-based data entry trigger conditions. The data transmission channel refers to the network connection between the mobile terminal and the microservice cloud used to upload emergency repair work order data blocks.

[0131] Based on the established network connection, the mobile terminal sends emergency repair work order data to the microservice cloud. During the data transmission process, the network packet loss rate is monitored. If the network packet loss rate is not less than a preset first packet loss threshold and the duration exceeds a preset time window, an offline cache degradation strategy is executed, data transmission is interrupted, and the data block, the corresponding block checksum, and the total checksum are encrypted and written to the local cache. When the network packet loss rate is detected to be not greater than a preset second packet loss threshold, the interrupted transmission resumes and uploads the cached data, continuing to send emergency repair work order data to the microservice cloud. The first packet loss threshold is greater than the second packet loss threshold.

[0132] This embodiment continuously monitors the network packet loss rate during transmission and uses different thresholds to correspond to two actions: downgrading to cache and resuming transmission. By using the state switching between the asynchronous message queue and the local cache, it achieves targeted processing for weak network scenarios, transforming upload failures caused by network fluctuations into a recoverable and resumable cached upload process. It can switch transmission strategies based on segmented judgment of packet loss rate to avoid forced real-time uploads when the network deteriorates, which would cause frequent data block failures.

[0133] After data transmission is completed, if the mobile terminal receives a retransmission request for the target data block from the microservice cloud, it will retransmit the target data block.

[0134] The determination of the target data block can be achieved by comparing the received total verification value with the total verification value generated by the mobile terminal through the microservice cloud. If the two are not equal, the target data block that failed to be received is determined by comparing the verification values ​​of each received block with the total verification value.

[0135] The above describes the data processing process on mobile terminals. Once the emergency repair user uploads the submitted emergency repair work order data to the microservice cloud via their mobile terminal, the current emergency repair user's process is complete, and they proceed to the next process node.

[0136] In this embodiment, after determining the validity of the electronic signature of the emergency repair user, the matching degree of role, location, and time with the current process node is used as an influencing factor to quantify the overall credibility of the emergency repair user. While considering the authorized user role, precise authorization is achieved by process node and spatiotemporal conditions, refining the control granularity of the emergency repair user's work order filling permission, preventing off-site users or users who have exceeded the time limit from directly obtaining the ability to fill in the form, and improving the reliability of the generated emergency repair work order data. Moreover, when judging the validity of the electronic signature, pressure fluctuation and signature time are used for authenticity verification, which solves the problem in the prior art that it is difficult to identify proxy signatures and forged signatures when only the signature image or trajectory is retained. Furthermore, by dividing the emergency repair work order data into multiple data blocks with additional millisecond-level timestamps, calculating the block verification value and the total verification value respectively, and triggering offline caching degradation strategy or breakpoint resume action based on the network packet loss rate during transmission, the system can maintain the verifiability, recoverability, and traceability of the work order data upload process in a weak network environment.

[0137] Example 2:

[0138] Embodiment 2 of this application provides another method for the flow of emergency repair work orders based on role-based access control, which is applied to microservice cloud.

[0139] The execution subject of this method can be any computing device capable of implementing the method, such as a server.

[0140] like Figure 2 The diagram shown is a flowchart illustrating the specific implementation of a role-based access control-based emergency repair work order processing method according to an embodiment of this application, including the following steps 21-22:

[0141] Step 21: Receive emergency repair work order data sent by the mobile terminal; wherein the emergency repair work order data is obtained based on the method described in Embodiment 1 above, and will not be repeated here.

[0142] After receiving the emergency repair work order data, the microservice cloud calculates the total verification value of the receiving end based on the verification values ​​corresponding to each database. It then compares the calculated total verification value of the receiving end with the total verification value sent by the mobile terminal. If the total verification value of the receiving end is equal to the total verification value, step 22 is executed. Otherwise, the difference between the total verification value and the total verification value of the receiving end is used to determine the unreceived block verification value and the corresponding target data block, and a retransmission request for the target data block is sent to the mobile terminal.

[0143] The retransmission request may include a work order identifier and a missing segment (target data block) identifier. After receiving the request, the mobile terminal extracts the corresponding data block from the local cache or the buffer to be sent and uploads it again. This embodiment can locate the missing segment based on the joint comparison of the total check value of the receiving end and the check value of the segment, avoiding the link waste and state chaos caused by retransmitting the entire order.

[0144] It should be noted that the mobile terminal sends a structured checklist containing the total number of blocks, the total checksum, and the expected checksum for each block before uploading the data block or simultaneously with the message.

[0145] Step 22: Update the database based on the emergency repair work order data and generate an emergency repair processing report, thus ending the process node. Specifically, this includes the following steps 2201-2202:

[0146] Step 2201: Extract fault phenomenon description information, fault judgment information, and emergency repair work order identifier from the emergency repair work order data.

[0147] In one specific implementation, a structured data domain for emergency repair work orders is constructed. This is a data set that can be directly mapped to business table fields for the current work order, such as fault symptoms, fault analysis, work order status, and work order identifier.

[0148] Step 2202: Write the extracted fault phenomenon description information and fault judgment information into the emergency repair order table of the database, and update the status of the emergency repair work order, specifically updating the status to pending acceptance.

[0149] Step 2203: Synchronously update the status of damaged resources in the associated business resource table of the database according to the emergency repair work order identifier.

[0150] The associated business resource table includes the associated impact business table and the impact optical path table. Synchronous update refers to locating the affected resource record to the corresponding entry and completing the status modification within the same transaction according to the work order identifier, so as to avoid the situation where the work order status has changed but the resource status has not been updated.

[0151] Step 2204: Extract the form fields from the emergency repair order table, as well as the text content extracted based on character recognition;

[0152] Step 2205: According to preset text concatenation rules, concatenate the form fields and the text content to generate an emergency repair report. The generated emergency repair report can then be pushed to the dispatch management terminal, triggering the current emergency repair work order to become an acceptance node and reclaiming the temporary access credentials of the emergency repair user.

[0153] Among them, form fields refer to structured work order fields that have been entered into the database, such as fault phenomena, fault analysis, and work order identification fields; text content refers to the text obtained from on-site images through character recognition and the descriptive content filled in by the terminal; text splicing rules refer to the preset format rules used to organize the report structure, such as outputting in the order of fields and inserting recognized text at fixed paragraph positions.

[0154] In this step, the emergency repair order table and the associated business resource table are included in the same database transaction operation, so that the fault description, fault assessment, work order status and the real-time status of the damaged resources are kept consistent and updated. The business table can be updated synchronously based on structured data fields and transaction writing, avoiding the disconnect between work order information and resource status, and ultimately solving the technical problem of inconsistent backend data caused by the lack of a unified database entry mechanism in the existing technology.

[0155] The system retrieves form fields from the emergency repair order form and text content extracted by a character recognition program. Based on preset text concatenation rules, it combines the form fields and text content to generate an emergency repair processing report and trigger subsequent status changes.

[0156] The microservice cloud reads the required form fields from the emergency repair order table and reads the text content extracted by the character recognition program from the corresponding text storage content. Based on the preset text concatenation rules, it generates a standard format emergency repair report.

[0157] After the emergency repair report is generated, it is pushed to the dispatch management terminal, triggering the change of the current emergency repair work order status to acceptance node, and at the same time revoking the previously issued temporary access credentials. The push can be packaged into a structured message by the microservice cloud according to the work order identifier and sent to the dispatch management terminal; revoking the temporary access credentials means that the terminal no longer retains the permission to fill in the work order.

[0158] This embodiment directly generates a standard format report from the structured fields already written to the database and the identified text content, ensuring that the report source is consistent with the work order data and reducing secondary processing errors; it can generate emergency repair reports based on the combination of form fields and identified text, avoiding delays and omissions caused by manual summarization.

[0159] The above describes the data processing process in the cloud for microservices.

[0160] Example 3:

[0161] To address the issue of insufficiently precise control over the access permissions of emergency repair personnel to fill out work orders, this embodiment also provides a work order circulation device based on role-based access control, based on the same inventive concept as Embodiment 1.

[0162] A schematic diagram of the specific structure of the device is shown below. Figure 3 As shown, it includes the following functional units 31-35:

[0163] User information acquisition unit 31 is used to acquire the location information, current time information, and electronic signature information of the emergency repair user.

[0164] The matching degree determination unit 32 is used to determine, after determining that the electronic signature information is valid, the location matching degree between the location information and the location of the faulty equipment corresponding to the process node, the time matching degree between the current time information and the specified response time corresponding to the process node, and the role matching degree between the role to which the emergency repair user belongs and the handling role corresponding to the process node, according to the process node where the emergency repair work order is located.

[0165] User trust measurement unit 33 is used to perform weighted fusion of the location matching degree, time matching degree and role matching degree to determine the dynamic permission score that represents the comprehensive trust level of the emergency repair user;

[0166] The permission unlocking unit 34 is used to unlock the emergency repair user's permission to fill in the emergency repair work order when the dynamic permission score is greater than the pre-generated dynamic authorization threshold.

[0167] The work order data sending unit 35 is used to obtain the emergency repair work order data filled in by the emergency repair user, and send the emergency repair work order data to the microservice cloud so that the microservice cloud can update the database, generate an emergency repair processing report and end the current process node based on the emergency repair work order data.

[0168] The apparatus in this embodiment further includes a signature validity determination unit, specifically used for: determining the validity of the electronic signature based on the electronic signature information, specifically including:

[0169] Obtain the electronic signature information of the user undergoing emergency repair; the electronic signature information includes the pressure value of each sampling point in the touch pressure data generated by the signature process on the touch screen, the average pressure value of this signature, the total number of sampling points touched by the signature trajectory, the historical average signature time of the user undergoing emergency repair, the current signature time, and a preset standard pressure fluctuation threshold; based on the pressure value of each sampling point, the average pressure value, the total number of sampling points, and the standard pressure fluctuation threshold, determine a first pressure calculation parameter; the first pressure calculation parameter characterizes the degree of difference between the pressure fluctuation of this signature and the standard pressure fluctuation threshold; based on the historical average signature time and the current signature time, determine a first time calculation parameter; the first time calculation parameter characterizes the reasonableness of the signature duration; based on the first pressure calculation parameter and the first time calculation parameter, determine a comprehensive signature verification value to quantify the validity of the signature; when the comprehensive signature verification value is not less than a preset verification threshold, and the number of abnormal pressure points exceeding the standard pressure fluctuation threshold meets a preset proportion condition, the electronic signature is determined to be valid.

[0170] Matching degree determination unit 32 determines the time matching degree in the following way:

[0171] Calculate the first difference between the current time information and the work order dispatch time. If the first difference is not greater than the specified response time, the time matching degree is a preset fixed value. If the first difference is greater than the specified response time, calculate the second difference between the preset fixed value and the time penalty coefficient multiplied by the timeout duration. If the second difference is less than zero, the time matching degree is zero; otherwise, the time matching degree is the second difference.

[0172] Work order data sending unit 35 is specifically used for:

[0173] The emergency repair work order data is sent to the microservice cloud; the network packet loss rate during the transmission process is monitored. If the network packet loss rate is not less than a preset first packet loss threshold and the duration exceeds a preset time window, the data transmission is interrupted; when the network packet loss rate is detected to be not greater than a preset second packet loss threshold, the interrupted transmission is started to continue sending the emergency repair work order data to the microservice cloud; the first packet loss threshold is greater than the second packet loss threshold.

[0174] The work order data sending unit 35 is also used for:

[0175] The emergency repair work order data is divided into multiple data blocks, and a block check value and a total check value for each data block are generated. The block check value and the total check value are sent to the microservice cloud along with the emergency repair work order data. A retransmission request for a target data block is received from the microservice cloud, and the target data block is retransmitted. The determination of the target data block includes: comparing the received total check value with the total check value through the microservice cloud; if the two are not equal, the target data block that failed to be received is determined by comparing the received block check values ​​with the total check value. The received total check value is determined by the check values ​​of each data block received by the microservice cloud.

[0176] Example 4:

[0177] Based on the same inventive concept as Embodiment 2, this embodiment also provides a workflow device for emergency repair work orders based on role access control.

[0178] A schematic diagram of the specific structure of the device is shown below. Figure 4 As shown, it includes the following functional units 41-42:

[0179] Work order data receiving unit 41 is used to receive emergency repair work order data sent by the mobile terminal;

[0180] The node flow unit 42 updates the database based on the emergency repair work order data, generates an emergency repair processing report, and ends the process node.

[0181] Node transfer unit 42 is specifically used for:

[0182] Extract fault description information, fault assessment information, and emergency repair work order identifier from the emergency repair work order data; write the extracted fault description information and fault assessment information into the emergency repair work order table of the database, and update the status of the emergency repair work order; update the status of damaged resources in the associated business resource table of the database according to the emergency repair work order identifier; extract form fields from the emergency repair work order table, and extract text content based on character recognition; concatenate the form fields and the text content according to preset text concatenation rules to generate an emergency repair processing report.

[0183] Based on the same inventive concept as the foregoing embodiments of this application, this application also provides a computing device.

[0184] like Figure 5 As shown, the computing device includes a memory 51 and a processor 52. The memory 51 can be configured to store various other data to support operation on the electronic device. Examples of such data include instructions for any application or method used to operate on the electronic device. The memory 51 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0185] The processor 52, coupled to the memory 51, is used to execute the computer program stored in the memory 51 to perform a method for processing emergency repair work orders based on role access control as described in the foregoing embodiments.

[0186] When the processor 52 executes the computer program to implement the role-based access control method for emergency repair work orders, after determining that the electronic signature of the emergency repair user is valid, the matching degree of role, location, and time with the current process node is used as an influencing factor to quantify the overall trustworthiness of the emergency repair user. While considering the authorized user role, precise authorization is achieved by process node and by spatiotemporal conditions, which refines the granularity of control over the emergency repair user's work order filling permissions, avoids off-site users or users who have exceeded the time limit from directly obtaining the ability to fill in the work order, and improves the reliability of the generated emergency repair work order data.

[0187] When the processor 52 executes the computer program in the memory 51, in addition to the functions described above, it can also perform other functions, as detailed in the descriptions of the preceding embodiments.

[0188] Furthermore, such as Figure 5 As shown, the computing device also includes other components such as a display 54, a communication component 53, a power supply component 55, and an audio component 56. Figure 5The diagram only shows some components and does not mean that the computing device includes only these components. Figure 5 The components shown.

[0189] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a computer, can implement the methods provided in the above embodiments.

[0190] 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. Those skilled in the art can understand and implement this without any creative effort.

[0191] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, 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 various embodiments or some parts of the embodiments.

[0192] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for processing emergency repair work orders based on role-based access control, characterized in that, Applied to a mobile terminal, the method includes: Obtain the location information, current time information, and electronic signature information of the emergency repair user; After determining that the electronic signature information is valid, based on the process node where the emergency repair work order is located, the location matching degree between the location information and the location of the faulty equipment corresponding to the process node, the time matching degree between the current time information and the specified response time corresponding to the process node, and the role matching degree between the role to which the emergency repair user belongs and the handling role corresponding to the process node are determined respectively. The location matching degree, time matching degree and role matching degree are weighted and fused to determine the dynamic permission score that represents the overall trustworthiness of the emergency repair user; When the dynamic permission score is greater than the pre-generated dynamic authorization threshold, the emergency repair user's permission to fill in the emergency repair work order is unlocked; Obtain the emergency repair work order data filled in by the emergency repair user, and send the emergency repair work order data to the microservice cloud so that the microservice cloud can update the database, generate an emergency repair processing report, and end the current process node based on the emergency repair work order data.

2. The method according to claim 1, characterized in that, The method further includes: determining the validity of the electronic signature based on the electronic signature information, specifically including: Obtain the electronic signature information of the emergency repair user; the electronic signature information includes the pressure value of each sampling point in the touch pressure data generated by the touch screen during the signing process, the average pressure value of this signature, the total number of sampling points touched by the signature trajectory, as well as the historical average signature time of the emergency repair user, the signature time of this signature, and the preset standard pressure fluctuation threshold. Based on the pressure values ​​of each sampling point, the average pressure, the total number of sampling points, and the standard pressure fluctuation threshold, a first pressure calculation parameter is determined; the first pressure calculation parameter characterizes the degree of difference between the pressure fluctuation of this signature and the standard pressure fluctuation threshold. Based on the historical average signature time and the current signature time, a first time calculation parameter is determined; the first time calculation parameter characterizes the reasonableness of the signature duration. Based on the first pressure calculation parameter and the first time consumption calculation parameter, a comprehensive signature verification value for quantifying the validity of the signature is determined; When the comprehensive signature verification value is not less than the preset verification threshold, and the number of abnormal pressure points exceeding the standard pressure fluctuation threshold meets the preset ratio condition, the electronic signature is determined to be valid.

3. The method according to claim 1, characterized in that, The time matching degree is determined in the following way: Calculate the first difference between the current time information and the work order dispatch time. If the first difference is not greater than the specified response time, the time matching degree is a preset fixed value. If the first difference is greater than the specified response time, then calculate the second difference between the preset fixed value and the time penalty coefficient multiplied by the timeout duration; If the second difference is less than zero, the time matching degree is zero; otherwise, the time matching degree is the second difference.

4. The method according to claim 1, characterized in that, Obtain the emergency repair work order data submitted by the user, and send the emergency repair work order data to the microservice cloud, including: Send the emergency repair work order data to the microservice cloud; Monitor the network packet loss rate during transmission. If the network packet loss rate is not less than a preset first packet loss threshold and the duration exceeds a preset time window, then interrupt data transmission. When the network packet loss rate is detected to be no greater than the preset second packet loss rate threshold, breakpoint resume is initiated to continue sending emergency repair work order data to the microservice cloud; the first packet loss threshold is greater than the second packet loss threshold.

5. The method according to claim 4, characterized in that, The process of obtaining the emergency repair work order data submitted by the user and sending the emergency repair work order data to the microservice cloud also includes: The emergency repair work order data is divided into multiple data blocks, and the block verification value of each data block and the total verification value of the emergency repair work order data are generated. The block verification value and the total verification value are sent to the microservice cloud along with the emergency repair work order data; Receive the retransmission request for the target data block from the microservice cloud and resend the target data block; The determination of the target data block includes: comparing the received total verification value with the total verification value through the microservice cloud; if the two are not equal, the target data block that failed to be received is determined by comparing the verification values ​​of each received block with the total verification value; the total verification value is determined by the verification values ​​of each data block received by the microservice cloud.

6. A method for processing emergency repair work orders based on role-based access control, characterized in that, Applied to microservices in the cloud, the method includes: Receive emergency repair work order data sent by the mobile terminal according to the transfer method described in claim 1; The database is updated based on the emergency repair work order data, and an emergency repair processing report is generated, thus ending the process node.

7. The method according to claim 6, characterized in that, The database is updated based on the emergency repair work order data, and an emergency repair processing report is generated, including: Extract fault description information, fault assessment information, and emergency repair work order identifier from the emergency repair work order data; The extracted fault phenomenon description information and fault judgment information are written into the emergency repair order table of the database, and the status of the emergency repair work order is updated. Update the status of damaged resources in the associated business resource table of the database according to the emergency repair work order identifier; Extract the form fields from the emergency repair order table, as well as the text content extracted based on character recognition; According to the preset text concatenation rules, the form fields and the text content are concatenated to generate an emergency repair report.

8. A workflow device for emergency repair work orders based on role-based access control, characterized in that, include: The user information acquisition unit is used to acquire the location information, current time information, and electronic signature information of the emergency repair user. The matching degree determination unit is used to determine, after determining that the electronic signature information is valid, the location matching degree between the location information and the location of the faulty equipment corresponding to the process node, the time matching degree between the current time information and the specified response time corresponding to the process node, and the role matching degree between the role of the emergency repair user and the handling role corresponding to the process node, according to the process node where the emergency repair work order is located. The user trust measurement unit is used to perform weighted fusion of the location matching degree, time matching degree and role matching degree to determine the dynamic permission score that represents the overall trustworthiness of the emergency repair user. The permission unlocking unit is used to unlock the emergency repair user's permission to fill in the emergency repair work order when the dynamic permission score is greater than the pre-generated dynamic authorization threshold. The work order data sending unit is used to obtain the emergency repair work order data filled in by the emergency repair user, and send the emergency repair work order data to the microservice cloud so that the microservice cloud can update the database, generate an emergency repair processing report and end the current process node based on the emergency repair work order data.

9. A workflow device for emergency repair work orders based on role-based access control, characterized in that, include: The work order data receiving unit is used to receive emergency repair work order data sent by the mobile terminal in accordance with the role-based access control-based emergency repair work order transfer method described in claim 1. The node flow unit updates the database based on the emergency repair work order data, generates an emergency repair processing report, and ends the process node.

10. An electronic device, characterized in that, include: A processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as claimed in any one of claims 1-7.

Images