Method and device for updating nameplate of management system

Abstract

The present application relates to a method and device for updating the nameplate of a management system. The method includes: receiving a nameplate data update request from a front-end device, where the nameplate data update request comes from a manual operation behavior on the front-end device interface, and the nameplate data is used to represent the work information of the staff; updating the nameplate data according to the data update request, and calling the front-end device to update the nameplate distribution interface, where the nameplate distribution interface at least includes grouping information and work sections corresponding to each nameplate data; converting the updated nameplate data into virtual data, and automatically reversing the virtual data according to a preset rule, where the reversing is used to change the attendance status of the staff corresponding to the indicated virtual data. The solution provided by the present application can solve the problem of data disorder in the railway electronic nameplate system caused by multi-user concurrent operations.

Description

Technical Field

[0001] This application relates to the technical field of data storage, and particularly to a method and device for updating the nameplates of a management system. Background Art

[0002] In the prior art, in order to facilitate the management of staff in the railway management system, an electronic nameplate system is often adopted. The system contains multiple lines, each line corresponds to multiple shifts, each shift has multiple staff members, and each staff member corresponds to a corresponding nameplate, and the nameplate includes the attendance or departure status of the staff. There are user manual adjustment operations and systematic automatic operations in the railway management system. In the user manual adjustment operation, the operator adjusts the order of the nameplates and the positions of the nameplates in the shift. In the system automatic operation, according to the attendance and departure status of the nameplate personnel, the position of the nameplate where the person is located is automatically adjusted, and the nameplates are sorted and arranged in a preset order.

[0003] For the existing railway electronic nameplate system, although the management in an electronic way is realized, at the same node, the phenomenon of simultaneous manual adjustment operations and automatic operations will occur. However, when two different threads modify the same record in the database at the same time, it will cause data overwrite problems due to concurrent data writing, thus making the railway electronic nameplate system. There is a situation where the position of the personnel nameplate does not match the actual nameplate position.

[0004] Therefore, in the prior art, there is a phenomenon that multi-user concurrent operations cause data disorder in the railway electronic nameplate system. Summary of the Invention

[0005] To solve or partially solve the problems existing in the related art, this application provides a method and device for updating the nameplates of a management system, which can solve the problem of data disorder in the railway electronic nameplate system caused by multi-user concurrent operations.

[0006] The first aspect of this application provides a method for updating the nameplates of a management system, including:

[0007] Receiving a nameplate data update request from a front-end device, the nameplate data update request comes from a manual operation behavior on the front-end device interface, and the nameplate data is used to represent the work information of the staff;

[0008] Updating the nameplate data according to the data update request, and calling the front-end device to update the nameplate distribution interface, and the nameplate distribution interface at least includes grouping information and working sections corresponding to each nameplate data;

[0009] Converting the updated nameplate data into virtual data, and automatically reversing the virtual data according to a preset rule, and the reversing is used to change the attendance status of the staff corresponding to the virtual data shown.

[0010] Optionally, obtaining a nameplate data update request from a front-end device previously included:

[0011] Reading the nameplate data of the entity nameplate and establishing virtual data of the entity nameplate;

[0012] Establishing a correspondence between the nameplate data and the virtual data so that the nameplate data and the virtual data of the same entity nameplate are in the same process node.

[0013] Optionally, updating the nameplate data according to the data update request includes:

[0014] In the case of receiving a nameplate data update request, establishing a foreground lock for the nameplate data, and the foreground lock is used to ensure that the nameplate data only accepts one nameplate data update request in the same process;

[0015] After establishing the foreground lock, establishing an operation lock for the nameplate data according to the nameplate update request, and the unlocking condition of the operation lock is that the nameplate data has not undergone a virtualization process.

[0016] Optionally, after establishing an operation lock for the nameplate data according to the nameplate update request, it includes:

[0017] After receiving a nameplate data update request from a front-end device, obtaining the expected value after the nameplate data is updated;

[0018] Judging whether it meets the unlocking condition of the operation lock according to the shown expected value;

[0019] In the case of meeting the unlocking condition of the operation lock, modifying the data value of the nameplate data to the shown updated expected value to update the nameplate data in the storage queue of the server.

[0020] Optionally, converting the updated nameplate data into virtual data includes:

[0021] Parsing the grouping information and working section corresponding to the updated nameplate data;

[0022] According to the grouping information and the working section, dividing the storage space corresponding to the shown virtual data, and storing the nameplate data into the subset corresponding to the divided storage space to obtain the virtual data corresponding to the nameplate data.

[0023] Optionally, automatically reversing the virtual data according to a preset rule for automatically reversing the virtual data includes:

[0024] Reading the staff dynamic table corresponding to the nameplate data, and the staff dynamic table includes the attendance time and leaving time of the staff;

[0025] Judging the attendance status of the personnel according to the attendance time and leaving time of the staff, and updating the virtual data according to the attendance status.

[0026] Optionally, the attendance status of a staff member is determined based on their attendance time and leaving time, including:

[0027] If the staff member has no attendance time but has a leaving time, it is determined that the staff member is in a leaving status;

[0028] If the staff member has an attendance time but no leaving time, it is determined that the staff member is in an attendance status;

[0029] If the staff member has an attendance time and the attendance time is greater than the leaving time, it is determined that the staff member is in an attendance status;

[0030] If the staff member has an attendance time and the attendance time is less than the leaving time, it is determined that the staff member is in a leaving status.

[0031] The second aspect of the present application provides a nameplate update device for a management system, including:

[0032] A receiving module, configured to receive a nameplate data update request from a front-end device. The nameplate data update request comes from a manual operation behavior on the front-end device interface, and the nameplate data is used to represent the work information of a staff member;

[0033] A first processing module, configured to update the nameplate data and call the front-end device to update the nameplate distribution interface. The shown nameplate distribution interface includes at least grouping information and work sections corresponding to each nameplate data;

[0034] A second processing module, configured to convert the updated nameplate data into virtual data, automatically reverse the virtual data according to a preset rule, and the reverse is used to change the attendance status of the staff member corresponding to the shown virtual data.

[0035] The third aspect of the present application provides an electronic device, including:

[0036] A processor; and

[0037] A memory, on which executable code is stored. When the executable code is executed by the processor, the processor executes the method as described above.

[0038] The fourth aspect of the present application provides a computer-readable storage medium, on which executable code is stored. When the executable code is executed by a processor of an electronic device, the processor executes the method as described above.

[0039] The technical solution provided by this application may include the following beneficial effects: By converting the nameplate data into virtual data and combining the actual position of the nameplate data with the virtual position of the virtualized data, the data storage process is visualized, facilitating manual operation intervention. At the same time, this application uses a pessimistic lock as the operation lock to lock the nameplate data. Only when the unlocking condition is met can the nameplate data be converted into virtual data, so that the source of the virtual data is single, supporting multi-user concurrent operations and realizing the isolation between manual operations and system automated operations.

[0040] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit this application. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] By describing the exemplary embodiments of this application in more detail in conjunction with the accompanying drawings, the above and other objects, features, and advantages of this application will become more apparent. Among them, in the exemplary embodiments of this application, the same reference numerals generally represent the same components.

[0042] Figure 1 is a schematic diagram of an interface of a railway management system for the front-end device interface shown in an embodiment of this application;

[0043] Figure 2 is a schematic diagram of the application environment of the nameplate update method of the management system shown in an embodiment of this application;

[0044] Figure 3 is a schematic flowchart of a nameplate update method of the management system shown in an embodiment of this application;

[0045] Figure 4 is a schematic flowchart of a method for locking nameplate data shown in an embodiment of this application;

[0046] Figure 5 is a schematic flowchart of a method for converting nameplate data into virtual data shown in an embodiment of this application;

[0047] Figure 6 is a schematic flowchart of an automatic nameplate inversion method shown in an embodiment of this application;

[0048] Figure 7 is another schematic flowchart of the automatic nameplate inversion method shown in an embodiment of this application

[0049] Figure 8 is a schematic structural diagram of a device for the nameplate update method of the management system shown in an embodiment of this application;

[0050] Figure 9 is a schematic structural diagram of an electronic device shown in an embodiment of this application. Detailed implementation manners

[0051] Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the embodiments of the present application are shown in the drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0052] The terms used in the present application are for the purpose of describing specific embodiments only and are not intended to limit the present application. The singular forms "a", "the", and "said" used in the present application and the appended claims are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0053] It should be understood that although the terms "first", "second", "third", etc. may be used in the present application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, the features defined with "first" and "second" may explicitly or implicitly include one or more of such features. In the description of the present application, "a plurality" means two or more unless otherwise specifically defined.

[0054] The embodiments of the present application provide a method and device for updating the nameplate of a management system. Specifically, the automatic nameplate update method of the embodiments of the present application can be executed by a computer device, where the computer device can be a terminal or a server or other devices.

[0055] First, some nouns or terms that appear in the process of describing the present application are explained as follows:

[0056] A nameplate, that is, a railway electronic nameplate, is used to indicate the position, attendance status, working hours, etc. of railway staff. Each railway staff corresponds to a nameplate. The position and sorting of the nameplates can indicate the carriage and working route where the staff works.

[0057] Nameplate data, that is, extracting the work-related data information of the staff on the nameplate and converting the relevant data information into a data format.

[0058] Automatic nameplate rearrangement: When a person represented by the nameplate has completed the attendance and checkout procedures in the business system, the position of the nameplate where the person is located should be adjusted and can be sorted in the order of the checkout arrival time.

[0059] Manual adjustment: The operator manually adjusts the sorting of nameplate data in the front-end device interface and the personnel position corresponding to the nameplate data.

[0060] Machine shift: The smallest grouping that performs the same set of work, that is, the smallest classification set of nameplate data.

[0061] Virtualization: Classify the nameplate data. The data that can be manually operated is real data, and the data after the system automatically reverses the nameplate is virtual data. For virtualized machine shifts, symbols are given in the display interface for distinction, which helps users visually distinguish.

[0062] Nameplate sorting: The virtual data is converted into real data by manually clicking the sorting button.

[0063] Operation lock: Use a forced lock for manual operations; use a pessimistic lock for system automatic operations (automatic nameplate reversal). All operations on the nameplate are locked to ensure the atomicity of a single operation and achieve the purpose of distributed deployment.

[0064] Automatic nameplate reversal: Two different processing mechanisms are used to process the nameplate reversal of real data and virtual data respectively, so that the real data is automatically converted into virtual data after the nameplate reversal, and the virtual data can be reversed multiple times.

[0065] In the prior art, in order to facilitate the management of staff in the railway management system, a railway electronic nameplate system is often used, such as Figure 1 shown. The system contains multiple lines (such as Line 1, Line 2, Line 3, etc., and each line is a queue), and each line corresponds to multiple nameplate routes (in the embodiments of the present application, the nameplate route can be the carriage between stations, and in Figure 1 it is shown as Carriage A, Carriage B, Carriage C, etc.). Each nameplate route includes at least one machine shift. The machine shift is the smallest working group of the staff. In this embodiment, the machine shifts are represented by digital numbers 1, 2, 3, 4. In the present application, there are multiple staff in each machine shift, and each staff corresponds to a corresponding nameplate, and there is a one-to-one correspondence between the nameplate and the staff. The nameplate includes the attendance or departure status of the staff, as well as basic information such as the position and age of the staff. The position of the nameplate data on the nameplate route includes the grouping information and working section corresponding to the nameplate data, where the grouping information corresponds to the machine shift information and the working section corresponds to the nameplate route information.

[0066] There are user manual adjustment operations and systematic automatic operations in the railway management system. In the user manual adjustment operation, the operator adjusts the nameplate order and the position of the nameplate in the machine shift. In the system automatic operation, according to the preset nameplate reversal rule, based on the attendance and departure status of the nameplate personnel, the nameplate position where the nameplate data is located is automatically adjusted and the nameplates are sorted and organized in the preset order.

[0067] In an embodiment of the present application, taking the automatic card flipping of nameplate 1 as an example, if nameplate 1 meets the card flipping rule and the staff corresponding to nameplate 1 will enter line 1 for work, the result of the automatic card flipping of nameplate 1 is that the nameplate data and virtual data corresponding to nameplate 1 are stored in the storage queue corresponding to line 1. After entering the storage queue, nameplate 1 returns to shift 1 according to the preset rule. At this time, the result of card flipping is that nameplate 1 returns to the corresponding position on shift 1 from storage queue 1 in the corresponding order.

[0068] For the existing railway electronic nameplate system, although the management in an electronic way is realized, at the same node, the phenomenon of simultaneous manual adjustment operations and automated operations will occur. However, when two different threads modify the same record in the database at the same time, it will cause data overwrite problems due to concurrent data writing, thus causing the railway electronic nameplate system. There will be a situation where the position of the personnel nameplate does not match the actual nameplate position.

[0069] In view of the above problems, the embodiment of the present application provides a method for updating nameplates of a management system, which can solve the problem of data disorder in the railway electronic nameplate system caused by multi-user concurrent operations.

[0070] The technical solutions of the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0071] See Figure 2 , Figure 2 An exemplary scenario diagram of an embodiment of the present application. As Figure 2 shown, the front-end device 11 is a WEB interface. The nameplate distribution interface and nameplate data are stored on the front-end device 11. A nameplate data update request is sent to the back-end device 12 according to the manual operation behavior on the front-end device 11. The nameplate distribution interface on the front-end device 11 is as Figure 1 shown. The manual operation behavior generally refers to the staff adjusting the position corresponding to the staff on the nameplate distribution interface. The nameplate data and virtual data are stored on the back-end device 12. An automatic card flipping algorithm based on virtual data and an algorithm for converting nameplate data into virtual data based on the nameplate data update request are run on the back-end device 12. When the back-end device 12 receives the nameplate data update request, an operation lock is constructed for the nameplate data according to the preset algorithm, thereby ensuring the uniqueness of the virtual data and further ensuring the isolation between the automated operations and manual operations in the system.

[0072] Moreover, the present application also provides an automatic card flipping method to realize the automatic update of nameplate data.

[0073] The embodiments of the present application provide a method, device, and storage medium for dynamically expanding attribute data. In practical applications, each functional module in the attribute data dynamic expansion device can be jointly implemented by the hardware resources of a device (such as a terminal device, a server, or a server cluster), such as computing resources of a processor, etc., and communication resources (such as various communication methods used to support the implementation of optical cables, cellular, etc.).

[0074] As Figure 3 shown, a nameplate update method for a management system includes:

[0075] S301, receiving a nameplate data update request from a front-end device. The nameplate data update request comes from the manual operation behavior of the front-end device interface, and the nameplate data is used to represent the work information of the staff.

[0076] In the embodiments of the present application, the nameplate data is the attribute data of the staff in the railway management system, specifically including the user's name, gender, age, attendance duration, carriage position, etc. Or it can also be other types of data, such as the input parameters or return values of an application protocol interface (API), other data exchanged between the front end and the back end of an application system, or other data exchanged between application systems, etc.

[0077] In the embodiments of the present application, the nameplate data can be obtained from other application systems, or it can also be generated by the user entering entity nameplate data. The present application does not limit the acquisition method of the target attribute data. Hereinafter, taking the user entry as an example for illustration, but the present application is not limited thereto.

[0078] In some embodiments, before step S301, obtaining a nameplate data update request from a front-end device includes: reading the nameplate data of the entity nameplate, and establishing virtual data of the entity nameplate; establishing a correspondence relationship between the nameplate data and the virtual data, so that the nameplate data and the virtual data of the same entity nameplate are in the same process node.

[0079] In this embodiment, by establishing a correspondence relationship between the nameplate data and the virtual data, the atomicity between the nameplate data operation and the virtual data operation can be maintained. In the subsequent process, the two can be converted into each other according to corresponding conditions, but under conditions that do not meet the relevant conditions, the nameplate data operation and the virtual data operation are independent of each other.

[0080] S302, updating the nameplate data according to the data update request, and calling the front-end device to update the nameplate distribution interface. The nameplate distribution interface includes at least the grouping information and work section corresponding to each nameplate data;

[0081] In step S302, the updated data includes: when receiving a nameplate data update request, establishing a foreground lock for the nameplate data, where the foreground lock is used to ensure that the nameplate data only accepts one nameplate data update request in the same process; after establishing the foreground lock, an operation lock for the nameplate data is established according to the nameplate update request, and the unlocking condition of the operation lock is that the nameplate data has not undergone a virtualization process.

[0082] Specifically, as Figure 4 It includes a method for locking nameplate data, specifically including:

[0083] S401 Set the foreground lock. After step S401 is completed, step S402 is carried out. Step S402: Delete the historical lock of this foreground; after step S402 is completed, step S403 is carried out. Step S403: Lock the nameplate data.

[0084] Among them, the data format for setting the foreground lock in step S401 is as follows:

[0085] Orgid (specific workshop):

[0086] termip (operation terminal IP)

[0087] Termip (operation terminal No)

[0088] Keyvalue (desired lock value).

[0089] Step S402: The data format for deleting the historical lock of this foreground is as follows:

[0090] Orgid (specific workshop):

[0091] termip (operation terminal IP)

[0092] Termip (operation terminal No.).

[0093] In step S403, the set operation lock is a pessimistic lock. This pessimistic lock uses the primary key conflict determination insert LOCK-NAMEPANEL, that is, when inserting records into the database concurrently, an Error code: 1062 will occur, which is commonly known as a primary key conflict. If no corresponding unlocking instruction is received, the nameplate data is not converted into virtual data. In the case of receiving the corresponding unlocking instruction, the nameplate data releases the database connection and converts the nameplate data into the corresponding virtual data to wait for the subsequent automatic nameplate change process.

[0094] The above judgment step also includes S404 other foreground requests. The data format of S404 other foreground requests includes:

[0095] Orgid (specific workshop):

[0096] termip (Operating Terminal IP)

[0097] Termip (Operating Terminal No.)

[0098] Keyvalue (Lock Value of the Current Client)

[0099] Groupids (For Which Routes to Operate)

[0100] Step S405, verify whether the lock is successful, virtual verification.

[0101] Figure 4 For the relevant implementation of the illustrated embodiment, set the foreground lock in S401. After step S401 is completed, proceed to step S402. Step S402: Delete the historical lock of this foreground; after step S402 is completed, proceed to step S403. Step S403: Lock. After locking, it is necessary to determine whether there are other foreground requests according to step S404, and step S405 to verify whether the lock is successful.

[0102] After completing step S405, after receiving the foreground data, check the lock value, and determine whether to proceed to the next step according to the lock value.

[0103] In one embodiment, after establishing an operation lock for the nameplate data according to the nameplate update request, it includes: after receiving the nameplate data update request from the front-end device, obtaining the expected value after the nameplate data is updated; judging whether it meets the unlocking condition of the operation lock according to the shown expected value; in the case of meeting the unlocking condition of the operation lock, modifying the data value of the nameplate data to the shown updated expected value to update the nameplate data in the storage queue of the server.

[0104] S303, convert the updated nameplate data into virtual data, automatically reverse the virtual data according to the preset rules, and the reverse is used to change the attendance status of the staff corresponding to the shown virtual data.

[0105] In one embodiment, converting the updated nameplate data into virtual data includes: parsing the grouping information and working section corresponding to the updated nameplate data; dividing the storage space corresponding to the shown virtual data according to the grouping information and working section, and storing the nameplate data into the subset corresponding to the divided storage space to obtain the virtual data corresponding to the nameplate data.

[0106] In this embodiment, the grouping information corresponding to the nameplate data is Figure 1 the route information in (i.e., Carriage A, Carriage B, Carriage C, etc.), and the working section is Figure 1The railway driving routes therein (such as Route 1, Route 2, Route 3, etc.). Group the nameplate data into sets according to the grouping information and working sections, and the grouped nameplate data corresponds to corresponding sets. Find the space of the virtual machine class set B on the virtual machine according to the set corresponding to the nameplate data, and check whether there are sub-items in set B (that is, judge whether new data can be added to the current flight). In the case of having sub-items, divide the remaining space and store the new data in the sub-items of set B.

[0107] Figure 5 is the implementation of the above related embodiments, including:

[0108] S501 Organize the virtual nameplate data of single shunting;

[0109] S502 Submit a request and verify the operation lock. Obtain the virtual machine class set B in the shunting

[0110] S503 Obtain the virtual machine class set B in the shunting, check whether there are sub-items in set B. In the case of having sub-items, S504 Database grouping, memory grouping

[0111] 504, Group and save.

[0112] The data format of S501 includes:

[0113] Parameter information A

[0114] Shunting ID groupid

[0115] Operation lock keyvalue

[0116] Workshop orgid.

[0117] The data format of S502 includes:

[0118] vchangevalue

[0119] Changevalue.

[0120] In one embodiment, automatically reverse the virtual data according to a preset rule, including: reading the staff dynamic table corresponding to the nameplate data, where the staff dynamic table includes the attendance time and departure time of the staff; judging the attendance status of the staff according to the attendance time and departure time of the staff, and updating the virtual data according to the attendance status.

[0121] Figure 6 is the flowchart of this embodiment, such as Figure 6As shown, the personnel dynamic table includes the attendance time, leaving time, attendance shift marking required, leaving shift marking required, attendance location, leaving time, leaving arrival time, etc. of the corresponding personnel. The attendance status of the personnel is judged according to the attendance time and leaving time of the staff, including: when the staff has no attendance time and has a leaving time, it is judged that the staff is in the leaving state; when the staff has an attendance time and no leaving time, it is judged that the staff is in the attendance state; when the staff has an attendance time and the attendance time is greater than the leaving time, it is judged that the staff is in the attendance state; when the staff has an attendance time and the attendance time is less than the leaving time, it is judged that the staff is in the leaving state.

[0122] Figure 7 It is a schematic flowchart of an automatic shift method, including:

[0123] S701, obtain the real route and virtual route, and judge the storage status of the virtual number.

[0124] Specifically, after receiving the instruction, the backend device first obtains the current route where the virtual data is located, determines the crew in the current route of the nameplate data, and judges whether there is a superior crew for the virtual data. If there is a superior crew, it means that this crew is not the smallest crew where the nameplate data is located. After there is no superior crew, judge the virtual attribute of the virtual data, and determine the relevant route information according to the nameplate data corresponding to the virtual data.

[0125] In the case of not meeting the preset conditions, modify the status of the nameplate.

[0126] Among them, judging the virtuality of the data is determined according to the fields of the virtual data and the nameplate data. In the embodiments of the present application, the virtual data and the real data are represented by y_jcyy_grouplococrew.vflag. When vflag = 0, the real field is the main one, groupid; when vflag = 1, the virtual field is the main one, vgroupid route shift setting, route type vflag, vchangevaluergroupid: combined crew route ID rparentid: combined crew superior ID

[0127] S702, judge whether the virtual data needs to be shifted.

[0128] Specifically, detect the shift switch, and judge whether the shift is enabled for this route; in the case where the shift is enabled for this route, judge whether this route supports shifting; in the case where this route supports shifting, detect the on-duty position of the personnel who meet the conditions, and in the case of meeting the detection conditions, judge that this virtual data needs to be shifted.

[0129] S703: Calculate the updated storage location of the virtual data.

[0130] When obtaining a flight crew that meets the conditions, determine whether the nameplate data has virtual attributes. If it does not have virtual attributes, modify the running status of the nameplate data. Calculating the storage location after virtual data update includes obtaining the turnover status corresponding to the virtual data and the virtual route for storing the virtual data.

[0131] In step S703, obtaining the turnover status corresponding to the virtual data includes: vchangevalueV1, changevalueV3 before update, and the flight crew ID ID1 of the update. Generate the updated vchangevalueV2 based on the above data before update.

[0132] In step S703, the virtual route for storing the virtual data: set vflag = 1 business (departure and arrival) time, vgroupid =? Departure time, vparentid =? Arrival time, vchangevalue = {V2} (departure, arrival). Generate the virtual route based on the above data: where id = {id1} and vchangevalue = {v1} and changevalue = {v3}.

[0133] After step S703, determine whether the turnover is successful. If it is successful, execute step S704: Notify the generated virtual route or the workshop route.

[0134] In step S704, determine whether the turnover is successful. If the turnover is successful, generate a turnover success notification.

[0135] The generation method of the turnover success notification includes generating a notification table, and the data format is as follows:

[0136] Primary key: section orgid + route ID or workshop orgid, modify changevalue = UUID.

[0137] Corresponding to the foregoing embodiment of the application function implementation method, the present application also provides a nameplate update device, an electronic device of a management system, and corresponding embodiments.

[0138] The technical solution provided by the present application may include the following beneficial effects: By converting the nameplate data into virtual data and combining the actual location of the nameplate data with the virtual location of the virtualized data, the present application makes the data storage process visual and facilitates manual operation intervention. At the same time, the present application uses a pessimistic lock as the operation lock to lock the nameplate data through the operation lock. Only when the unlocking condition is met can the nameplate data be converted into virtual data, so that the source of the virtual data is single, thereby supporting multi-user concurrent operations and realizing the isolation between manual operations and system automated operations.

[0139] Figure 8 It is a schematic structural diagram of a nameplate update device of a management system shown in an embodiment of the present application.

[0140] See Figure 8 , a nameplate update device of a management system, including:

[0141] A receiving module 801, configured to receive a nameplate data update request from a front-end device. The nameplate data update request comes from a manual operation behavior on the front-end device interface, and the nameplate data is used to represent the work information of the staff.

[0142] In one embodiment, updating the nameplate data according to the data update request includes:

[0143] When receiving the nameplate data update request, establish a foreground lock for the nameplate data. The foreground lock is used to ensure that the nameplate data only accepts one nameplate data update request in the same process;

[0144] After establishing the foreground lock, establish an operation lock for the nameplate data according to the nameplate update request. The unlocking condition of the operation lock is that the nameplate data has not undergone a virtualization process.

[0145] In one embodiment, after establishing the operation lock for the nameplate data according to the nameplate update request, it includes:

[0146] After receiving the nameplate data update request from the front-end device, obtain the expected value after the nameplate data is updated;

[0147] Judge whether it meets the unlocking condition of the operation lock according to the shown expected value;

[0148] When meeting the unlocking condition of the operation lock, modify the data value of the nameplate data to the shown updated expected value to update the nameplate data in the storage queue of the server.

[0149] A first processing module 802, configured to update the nameplate data and call the front-end device to update the nameplate distribution interface. The shown nameplate distribution interface at least includes grouping information and working sections corresponding to each nameplate data.

[0150] In one embodiment, before obtaining the nameplate data update request from the front-end device, it includes:

[0151] Read the nameplate data of the physical nameplate and establish virtual data of the physical nameplate;

[0152] Establish a correspondence relationship between the nameplate data and the virtual data, so that the nameplate data and the virtual data of the same physical nameplate are in the same process node.

[0153] In one embodiment, converting the updated nameplate data into virtual data includes:

[0154] Analyzing the grouping information and working sections corresponding to the updated nameplate data;

[0155] According to the grouping information and working sections, dividing the storage space corresponding to the virtual data, and storing the nameplate data into subsets corresponding to the divided storage space to obtain the virtual data corresponding to the nameplate data.

[0156] The second processing module 803 is used to convert the updated nameplate data into virtual data, and automatically reverse the virtual data according to a preset rule. The reverse is used to change the attendance status of the staff corresponding to the virtual data.

[0157] In one embodiment, automatically reversing the virtual data according to a preset rule includes:

[0158] Reading the staff dynamic table corresponding to the nameplate data, where the staff dynamic table includes the attendance time and leaving time of the staff;

[0159] Judging the attendance status of the staff according to the attendance time and leaving time of the staff, and updating the virtual data according to the attendance status.

[0160] In one embodiment, judging the attendance status of the staff according to the attendance time and leaving time of the staff includes: in the case where the staff has no attendance time but has a leaving time, judging that the staff is in a leaving status; in the case where the staff has an attendance time but no leaving time, judging that the staff is in an attendance status; in the case where the staff has an attendance time and the attendance time is greater than the leaving time, judging that the staff is in an attendance status; in the case where the staff has an attendance time and the attendance time is less than the leaving time, judging that the staff is in a leaving status.

[0161] Regarding the device in the above embodiment, the specific manners in which each module performs operations have been described in detail in the embodiment related to the method, and will not be elaborated here.

[0162] Figure 9 is a schematic structural diagram of an electronic device shown in an embodiment of the present application.

[0163] See Figure 9 , the electronic device 900 includes a memory 910 and a processor 920.

[0164] The processor 920 may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0165] The memory 910 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. Among them, the ROM may store static data or instructions required by the processor 920 or other modules of the computer. The permanent storage device may be a read-write storage device. The permanent storage device may be a non-volatile storage device that does not lose the stored instructions and data even when the computer is powered off. In some embodiments, the permanent storage device uses a mass storage device (such as a magnetic or optical disk, flash memory) as the permanent storage device. In some other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, optical drive). The system memory may be a read-write storage device or a volatile read-write storage device, such as dynamic random access memory. The system memory may store some or all of the instructions and data required by the processor during operation. In addition, the memory 910 may include any combination of computer-readable storage media, including various types of semiconductor storage chips (such as DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and magnetic disks and / or optical disks may also be used. In some embodiments, the memory 910 may include a removable storage device that is readable and / or writable, such as a compact disc (CD), read-only digital versatile disc (such as DVD-ROM, dual-layer DVD-ROM), read-only Blu-ray disc, super density disc, flash memory card (such as SD card, min SD card, Micro-SD card, etc.), magnetic floppy disk, etc. The computer-readable storage medium does not include carrier waves and instantaneous electronic signals transmitted wirelessly or by wire.

[0166] An executable code is stored on the memory 910, and when the executable code is processed by the processor 920, it may cause the processor 920 to execute some or all of the methods described above.

[0167] In addition, the method according to the present application can also be implemented as a computer program or a computer program product, which includes computer program code instructions for performing some or all of the steps in the above method of the present application.

[0168] Alternatively, the present application can also be implemented as a computer-readable storage medium (or a non-transitory machine-readable storage medium or a machine-readable storage medium), on which executable code (or a computer program or computer instruction code) is stored. When the executable code (or the computer program or computer instruction code) is executed by a processor of an electronic device (or a server, etc.), the processor is caused to execute some or all of the steps of the above method according to the present application.

[0169] The embodiments of the present application have been described above. The above description is exemplary and not exhaustive, and is also not limited to the disclosed embodiments. Many modifications and variations are obvious to those of ordinary skill in the art in the technical field without departing from the scope and spirit of the described embodiments. The selection of the terms used herein is intended to best explain the principles of the embodiments, the practical application, or the improvement of the technology in the market, or to enable other ordinary skill in the art in the technical field to understand the embodiments disclosed herein.

Claims

1. A nameplate update method for a management system, characterized in that, Including: Receiving a nameplate data update request from a front-end device, where the nameplate data update request comes from a manual operation behavior on the front-end device interface, and the nameplate data is used to represent the work information of the staff; Updating the nameplate data according to the nameplate data update request, and calling the front-end device to update the nameplate distribution interface, where the nameplate distribution interface at least includes grouping information and work sections corresponding to each nameplate data; The updating the nameplate data according to the nameplate data update request includes: when receiving the nameplate data update request, establishing a foreground lock for the nameplate data, where the foreground lock is used to ensure that the nameplate data only accepts one nameplate data update request in the same process; after establishing the foreground lock, establishing an operation lock for the nameplate data according to the nameplate update request, and the unlocking condition of the operation lock is that the nameplate data has not undergone a virtualization process; Converting the updated nameplate data into virtual data, and automatically reversing the virtual data according to a preset rule, where the reversing is used to change the attendance status of the staff corresponding to the virtual data.

2. The method according to claim 1, wherein Before the receiving the nameplate data update request from the front-end device, it includes: Reading the nameplate data of the physical nameplate and establishing virtual data of the physical nameplate; Establishing a correspondence between the nameplate data and the virtual data, so that the nameplate data and the virtual data of the same physical nameplate are in the same process node.

3. The method according to claim 1, characterized in that, After establishing the operation lock for the nameplate data according to the nameplate update request, it includes: After receiving the nameplate data update request from the front-end device, obtaining the expected value after the nameplate data is updated; Judging whether it meets the unlocking condition of the operation lock according to the expected value shown; When meeting the unlocking condition of the operation lock, modifying the data value of the nameplate data to the updated expected value shown to update the nameplate data in the storage queue of the server.

4. The method according to claim 1, wherein The converting the updated nameplate data into virtual data includes: Parsing the grouping information and work sections corresponding to the updated nameplate data; According to the grouping information and work sections, dividing the storage space corresponding to the virtual data, and storing the nameplate data into the subset corresponding to the divided storage space to obtain the virtual data corresponding to the nameplate data.

5. The method according to claim 1, wherein The automatically reversing the virtual data according to a preset rule includes: Reading the staff dynamic table corresponding to the nameplate data, where the staff dynamic table includes the attendance time and leaving time of the staff; Judging the attendance status of the staff according to the attendance time and leaving time of the staff, and updating the virtual data according to the attendance status.

6. The method according to claim 5, characterized in that, The judging the attendance status of the staff according to the attendance time and leaving time of the staff includes: When the staff has no attendance time and has a leaving time, judging that the staff is in a leaving status; When the staff has an attendance time and no leaving time, judging that the staff is in an attendance status; When the staff has an attendance time and the attendance time is greater than the leaving time, judging that the staff is in an attendance status; In the case where the staff member has a clock-in time and the clock-in time is less than the clock-out time, it is determined that the staff member is in the clock-out state.

7. A nameplate updating device for a management system, characterized in that, It includes: A receiving module, configured to receive a nameplate data update request from a front-end device, where the nameplate data update request comes from a manual operation behavior on the front-end device interface, and the nameplate data is used to represent the work information of the staff member; A first processing module, configured to update the nameplate data and call the front-end device to update the nameplate distribution interface, where the nameplate distribution interface at least includes grouping information and work sections corresponding to each nameplate data; The first processing module includes: being configured to establish a foreground lock for the nameplate data in the case of receiving the nameplate data update request, where the foreground lock is used to ensure that the nameplate data only accepts one nameplate data update request in the same process; after establishing the foreground lock, an operation lock for the nameplate data is established according to the nameplate update request, and the unlocking condition of the operation lock is that the module for which the nameplate data has not undergone the virtualization process; A second processing module, configured to convert the updated nameplate data into virtual data and automatically reverse the virtual data according to a preset rule, where the reverse is used to change the attendance state of the staff member corresponding to the virtual data.

8. An electronic device, characterized in that, It includes: A processor; And A memory, on which executable code is stored, and when the executable code is executed by the processor, the processor is caused to execute the method according to any one of claims 1-6.

9. A computer-readable storage medium, on which executable code is stored, and when the executable code is executed by a processor of an electronic device, the processor is caused to execute the method according to any one of claims 1-6.

Images