Attendance processing methods and devices

Abstract

This specification provides an attendance processing method and apparatus. One attendance processing method includes: receiving an attendance query request sent by a client; the attendance query request includes the identity identifier of the driver / passenger and the vehicle identifier of the passenger vehicle; querying the attendance status of the driver / passenger and the vehicle status of the passenger vehicle based on the identity identifier and the vehicle identifier; performing attendance access judgment on the driver / passenger and the passenger vehicle based on the attendance status and the vehicle status, and sending the attendance access judgment result to the client; if the attendance access judgment result indicates access is approved, updating the attendance status and the vehicle status according to operation information sent by the client.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on September 23, 2020, with application number CN202011011715.9 and title "Attendance Processing Method and Apparatus". Technical Field

[0002] This document relates to the field of information processing technology, and in particular to an attendance processing method and apparatus. Background Technology

[0003] With the continuous development of passenger transport services, some factors that restrict the development of the passenger transport industry have gradually emerged. For example, in third-tier and lower-level cities, there are generally problems such as outdated information systems, small and scattered regional business volume, and diversified route operation modes. This makes the operation and management of passenger vehicles difficult and complex. In order to further promote the development of the passenger transport industry, it is necessary to optimize the management system of the passenger transport industry. Summary of the Invention

[0004] This specification provides one or more embodiments of an attendance processing method. The attendance processing method is applied to a server and includes: receiving an attendance query request sent by a client; the attendance query request includes the identity identifier of the driver / passenger and the vehicle identifier of the passenger vehicle. Based on the identity identifier and the vehicle identifier, querying the attendance status of the driver / passenger and the vehicle status of the passenger vehicle. Based on the attendance status and the vehicle status, performing an attendance access judgment on the driver / passenger and the passenger vehicle, and sending the attendance access judgment result to the client. If the attendance access judgment result indicates successful access, updating the attendance status and the vehicle status according to operation information sent by the client.

[0005] This specification provides one or more embodiments of an attendance processing method applied to a client, comprising: collecting image identification codes configured on passenger vehicles; identifying the image identification codes to obtain the identity identifiers of the driver and conductor, and the vehicle identifier of the passenger vehicle; generating an attendance query request carrying the identity identifiers and the vehicle identifier, and sending it to a server; receiving and displaying the attendance access judgment result sent by the server; and, if the attendance access judgment result indicates access is approved, obtaining the operation information of the driver and conductor and sending it to the server.

[0006] This specification provides one or more embodiments of an attendance processing device, running on a server, comprising: a request receiving module configured to receive an attendance query request sent by a client; the attendance query request includes the identity identifier of the driver / passenger and the vehicle identifier of the passenger vehicle; a query module configured to query the attendance status of the driver / passenger and the vehicle status of the passenger vehicle based on the identity identifier and the vehicle identifier; a judgment module configured to perform attendance access judgment on the driver / passenger and the passenger vehicle based on the attendance status and the vehicle status, and send the attendance access judgment result to the client; and an update module configured to update the attendance status and the vehicle status according to operation information sent by the client if the attendance access judgment result indicates access is approved.

[0007] This specification provides one or more embodiments of an attendance processing device, running on a client side, comprising: a data acquisition module configured to acquire image identification codes configured on passenger vehicles; an identification module configured to identify the image identification codes to obtain the identity identifiers of the driver and conductor and the vehicle identifier of the passenger vehicle; a request sending module configured to generate an attendance query request carrying the identity identifiers and the vehicle identifier and send it to a server; a judgment result receiving module configured to receive and display the attendance access judgment result sent by the server; and an operation information sending module configured to, if the attendance access judgment result indicates access approval, acquire the operation information of the driver and conductor and send it to the server.

[0008] This specification provides one or more embodiments of an attendance processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: receive an attendance query request sent by a client. The attendance query request includes the identity identifier of the driver / passenger and the vehicle identifier of the passenger vehicle. Based on the identity identifier and the vehicle identifier, the processor queries the attendance status of the driver / passenger and the vehicle status of the passenger vehicle. Based on the attendance status and the vehicle status, the processor performs an attendance access determination on the driver / passenger and the passenger vehicle, and sends the attendance access determination result to the client. If the attendance access determination result indicates successful access, the processor updates the attendance status and vehicle status according to operation information sent by the client.

[0009] This specification provides one or more embodiments of another attendance processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire image identification codes configured on passenger vehicles; identify the image identification codes to obtain the identity codes of the driver and passengers and the vehicle identification codes of the passenger vehicles; generate an attendance query request carrying the identity codes and the vehicle identification codes and send it to a server; receive and display the attendance access judgment results sent by the server; and, if the attendance access judgment results indicate that access is approved, acquire the operation information of the driver and passengers and send it to the server.

[0010] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions, which, when executed, implement the following process: receiving an attendance query request sent by a client. The attendance query request includes the identity identifier of the driver / passenger and the vehicle identifier of the passenger vehicle. Based on the identity identifier and the vehicle identifier, querying the attendance status of the driver / passenger and the vehicle status of the passenger vehicle. Based on the attendance status and the vehicle status, performing an attendance access judgment on the driver / passenger and the passenger vehicle, and sending the attendance access judgment result to the client. If the attendance access judgment result is that access is approved, updating the attendance status and vehicle status according to the operation information sent by the client.

[0011] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions that, when executed, implement the following process: acquiring image identification codes configured in passenger vehicles; recognizing the image identification codes to obtain the identity codes of the driver and passengers, and the vehicle identification code of the passenger vehicle; generating an attendance query request carrying the identity codes and the vehicle identification code and sending it to a server; receiving and displaying the attendance access judgment result sent by the server; and, if the attendance access judgment result indicates access is approved, acquiring the operation information of the driver and passengers and sending it to the server. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in one or more embodiments of this specification or in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 A flowchart illustrating an attendance processing method provided in one or more embodiments of this specification;

[0014] Figure 2 A flowchart illustrating an attendance processing method for a passenger check-in scenario, provided by one or more embodiments of this specification.

[0015] Figure 3 A flowchart illustrating another attendance processing method provided in one or more embodiments of this specification;

[0016] Figure 4 A flowchart illustrating another attendance processing method applied to a passenger check-in scenario, provided by one or more embodiments of this specification.

[0017] Figure 5 A schematic diagram of an attendance processing device provided for one or more embodiments of this specification;

[0018] Figure 6 A schematic diagram of another attendance processing device provided in one or more embodiments of this specification;

[0019] Figure 7 A schematic diagram of the structure of an attendance processing device provided for one or more embodiments of this specification;

[0020] Figure 8 This is a schematic diagram of another attendance processing device provided in one or more embodiments of this specification. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0022] This manual provides an example of an attendance processing method:

[0023] See attached document Figure 1 The attached diagram illustrates a processing flowchart of an attendance processing method provided in this embodiment. Figure 2 The diagram illustrates a process flow chart of an attendance processing method applied to a passenger check-in scenario, as provided in this embodiment.

[0024] The attendance processing method provided in this embodiment is executed by a server, while another attendance processing method embodiment provided in this specification is executed by a client. The attendance processing method applied to the server provided in this embodiment cooperates with the attendance processing method applied to the client provided in the following method embodiments during execution. Therefore, please refer to the corresponding content of the following method embodiments when reading this embodiment.

[0025] See attached document Figure 1 The attendance processing method provided in this embodiment specifically includes the following steps S102 to S108.

[0026] Step S102: Receive the attendance query request sent by the client.

[0027] This embodiment provides an attendance processing method applied to a server. In conjunction with the attendance processing method applied to a client provided in the following embodiment, it improves the efficiency of managing the attendance of drivers and conductors at a passenger station by utilizing the vehicle status of passenger vehicles. Specifically, based on a received attendance query request, the method queries the attendance status of the drivers and conductors and the vehicle status of the passenger vehicles contained in the query request. Then, based on the queried attendance status and vehicle status, it determines whether the drivers and conductors can perform attendance operations on the passenger vehicles. The determination result is sent to the client, and the attendance status of the drivers and conductors and the vehicle status of the passenger vehicles are updated based on the operation information received from the client, thereby improving the simplicity and accuracy of attendance tracking.

[0028] In practice, drivers and passengers scan a QR code configured based on the license plate number of the passenger vehicle using a third-party application (client) installed on their mobile terminals. After scanning the QR code, the client identifies the driver / passenger's identity and the vehicle identification of the passenger vehicle to which the vehicle information submitted by the driver / passenger belongs. It then generates an attendance query request carrying the identity and vehicle identification and sends it to the server. The attendance query request contains the driver / passenger's identity and the passenger vehicle's vehicle identification.

[0029] The attendance query request mentioned in this embodiment refers to the processing request submitted by the client during the attendance operation performed by the driver and passenger through the client; for example, when the driver and passenger want to scan a QR code to check in through a third-party application (client) installed on the mobile terminal, the third-party application sends a processing request to the server to query whether the current driver and passenger can check in for the passenger vehicle to which the vehicle information submitted by the driver and passenger belongs.

[0030] For example, when drivers and passengers want to scan a QR code to clock out using a third-party application (client) installed on their mobile devices, the third-party application sends a request to the server to query whether the passenger vehicle to which the driver / passenger belongs can be clocked out based on the vehicle information submitted by the driver / passenger.

[0031] For example, when driver A needs to sign in, the submitted passenger vehicle information belongs to passenger vehicle 1. The client sends an attendance query request to query the attendance status of driver A and the vehicle status of passenger vehicle 1.

[0032] To improve attendance efficiency and ensure attendance accuracy, this embodiment provides an optional implementation method that, before the step of receiving the attendance query request sent by the client is executed, further includes:

[0033] Obtain the identity information of the drivers and passengers of the target passenger transport unit, as well as the vehicle information of the passenger vehicles;

[0034] A driver and passenger table is constructed based on the identity identifiers contained in the identity information, and a passenger vehicle table is constructed based on the vehicle identifiers contained in the vehicle information.

[0035] For example, if Passenger Station A has 110 drivers and conductors and 50 passenger vehicles, construct a driver and conductor table containing the identity information of the 110 drivers and conductors, and construct a passenger vehicle table containing the vehicle information of the 50 passenger vehicles.

[0036] Step S104: Based on the identity identifier and the vehicle identifier, query the attendance status of the driver and passengers and the vehicle status of the passenger vehicle.

[0037] The attendance status of the drivers and attendants includes a signed-in status and an unsigned-in status. For example, if a query shows that driver M has no sign-in record but attendant N has a sign-in record, then driver M's attendance status is unsigned and attendant N's attendance status is signed-in.

[0038] The vehicle status of the passenger vehicle refers to whether the passenger vehicle has been checked in or checked out by the driver and passengers. The check-in status of the passenger vehicle is reflected in the fact that it is bound to the driver and passengers who performed the check-in operation on the passenger vehicle, and the vehicle status at this time is called the bound status. The check-out status of the passenger vehicle is reflected in the fact that it is unbound by the driver and passengers who performed the check-in operation on the passenger vehicle, and the vehicle status at this time is called the unbound status. Accordingly, when the vehicle status of the passenger vehicle is in the bound status, the driver and passengers who checked in on the passenger vehicle and the passenger vehicle have established a binding relationship through the check-in operation, that is, an attendance binding relationship.

[0039] For example, driver A performs a check-in operation on passenger vehicle 1. After the check-in operation is successful, driver A establishes an attendance binding relationship with passenger vehicle 1. After driver A finishes working on passenger vehicle 1, driver A needs to perform a check-out operation on passenger vehicle 1. After receiving the operation information of driver A's check-out operation on passenger vehicle 1, the attendance binding relationship established between driver A and passenger vehicle 1 is released.

[0040] To improve the comprehensiveness of attendance management, in one optional implementation of this embodiment, the personnel include drivers and attendants; one driver is allowed to sign in for the same passenger vehicle in any attendance cycle, and multiple attendants are allowed to sign in for the same passenger vehicle.

[0041] Accordingly, the attendance and access determination for the drivers and passengers and the passenger vehicles includes:

[0042] If the driver or conductor is a flight attendant, the attendance access judgment result of the attendance access judgment in the attendance cycle is "access approved".

[0043] For example, if driver M signs in passenger vehicle 4, attendant N can also sign in passenger vehicle 4. At this time, driver M and attendant N jointly establish an attendance binding relationship with passenger vehicle 4.

[0044] In practical implementation, to improve the accuracy of attendance management for personnel in the target passenger transport unit, it is necessary to determine whether the driver and conductor, as well as the passenger vehicle, in the attendance query request belong to the target passenger transport unit. Only when both the driver and conductor and the passenger vehicle exist in the target passenger transport unit can the attendance status of the driver and conductor and the vehicle status of the passenger vehicle be further queried. In one optional implementation provided in this embodiment, the attendance status of the driver and conductor and the vehicle status of the passenger vehicle are queried and determined in the following manner:

[0045] Determine whether the driver / passenger identification information contained in the attendance query request exists in the driver / passenger personnel table, and whether the passenger vehicle identification information contained in the attendance query request exists in the passenger vehicle table.

[0046] If so, grant the drivers and passengers attendance permissions to perform attendance operations for the passenger vehicles;

[0047] Query the attendance status of the drivers and conductors and the vehicle status of the passenger vehicles in the current attendance period in the attendance record table;

[0048] If not, send a prompt to the client prohibiting the driver / passenger from performing attendance operations;

[0049] In practical applications, attendance permissions for the driver / passenger to perform attendance operations on the passenger vehicle can only be granted if both the driver / passenger and the passenger vehicle exist in the driver / passenger table and the passenger vehicle's status can be queried. If it is determined that the driver / passenger is not in the driver / passenger table or the passenger vehicle is not in the passenger vehicle table, then attendance permissions for the driver / passenger to perform attendance operations on the passenger vehicle cannot be granted, and a notification prohibiting attendance operations will be sent to the client.

[0050] For example, both driver A and driver B belong to Passenger Station A. Driver A submits vehicle information for passenger vehicle 1 by scanning a QR code, while driver B submits vehicle information for passenger vehicle 2 by scanning a QR code. A query reveals that the identities of both drivers A and B exist in Passenger Station A's driver table, and the vehicle identifier for passenger vehicle 1 exists in Passenger Station A's vehicle table, but the vehicle identifier for passenger vehicle 2 does not exist in Passenger Station A's vehicle table. Therefore, driver A is granted attendance access to passenger vehicle 1, and their attendance status and the vehicle status of passenger vehicle 1 are queried. Driver B is denied attendance access to passenger vehicle 2, and a notification prohibiting driver B from performing attendance operations is sent to the client. Driver C of Bus Station A submitted vehicle information for passenger vehicle 3 by scanning a QR code. However, upon querying, it was found that driver C's identity was not listed in Bus Station A's driver and conductor table. Therefore, attendance access for passenger vehicle 3 was not granted to driver C, and a notification prohibiting driver C from performing attendance operations was sent to the client.

[0051] Step S106: Based on the attendance status and the vehicle status, perform attendance access judgment on the driver and the passenger vehicle, and send the attendance access judgment result to the client.

[0052] The attendance access judgment refers to determining whether the driver and passenger can establish or terminate the established attendance binding relationship with the passenger vehicle based on the attendance status and the vehicle status.

[0053] In one optional implementation method provided in this embodiment, attendance access judgment is performed in the following way:

[0054] Check the attendance record table to see if the attendance record of the driver or conductor exists in the current attendance period;

[0055] If they exist, check whether the passenger vehicle has established an attendance binding relationship with the driver and conductor; if yes, determine that the attendance access judgment result is access passed; if no, determine that the attendance access judgment result is access failed.

[0056] If it does not exist, check if the passenger vehicle has an attendance binding relationship; if it does, determine that the attendance access judgment result is access denied; if not, determine that the attendance access judgment result is access approved.

[0057] In specific implementation, the attendance record table is checked to see if the attendance record of the driver / passenger exists in the attendance period. If the attendance record of the driver / passenger exists in the attendance record table, the passenger vehicle is checked to see if it has an attendance binding relationship with the driver / passenger, that is, whether the passenger vehicle has a binding record with the driver / passenger. If yes, the attendance access judgment result is determined to be access passed; otherwise, the attendance access judgment result is determined to be access failed. If the attendance record of the driver / passenger does not exist in the attendance record table, the passenger vehicle is checked to see if it has an attendance binding relationship with other drivers / passengers, that is, whether the passenger vehicle has a binding record. If yes, the attendance access judgment result is determined to be access failed; otherwise, the attendance access judgment result is determined to be access passed.

[0058] For example, on a certain attendance record day, driver M submits vehicle information belonging to passenger vehicle 4 by scanning a code. If the attendance record table for that day shows no attendance record for driver M and no binding record for passenger vehicle 4, then the attendance access judgment result is determined to be access passed. If the attendance record table for that day shows no attendance record for driver M but a binding record for passenger vehicle 4, then the attendance access judgment result is determined to be access failed. If driver M has an attendance record and passenger vehicle 4 is bound to driver M's attendance record, then the attendance access judgment result is determined to be access passed. If driver M has an attendance record but passenger vehicle 4 is not bound record, then the attendance access judgment result is determined to be access failed.

[0059] For example, on a certain attendance record day, if flight attendant N submits vehicle information belonging to passenger vehicle 5 by scanning a code, then the attendance access judgment result is directly determined as access passed.

[0060] In practical applications, access approval means that drivers and passengers can perform check-in or check-out operations on the passenger vehicles to which the submitted vehicle information belongs. Drivers and passengers can only check in within the same attendance cycle if they have checked out using the current account. In one optional implementation of this embodiment, for check-in operations, the attendance access judgment is performed in the following way:

[0061] If, during the current attendance period, the query reveals that the driver and passenger personnel have no sign-in records and the passenger vehicle has no binding records, the attendance access judgment result is determined to be "access approved".

[0062] For example, if driver A submits vehicle information belonging to passenger vehicle 1 by scanning a code, and within the same attendance cycle, it is found that driver A has no sign-in record and passenger vehicle 1 has no binding record, then the attendance access judgment result is determined to be access passed, and driver A can perform the sign-in operation.

[0063] In one optional implementation of this embodiment, for operation information that is a sign-out operation, the attendance access judgment is performed in the following way:

[0064] If, during the current attendance period, a query reveals that the driver and conductor have attendance records and the passenger vehicle has an attendance binding relationship with the driver and conductor, then the attendance access judgment result is determined to be access passed.

[0065] If the initial check-out operation fails, the driver and passengers are allowed to perform a second check-out operation.

[0066] For example, driver A submits vehicle information belonging to passenger vehicle 1 by scanning a code. Within the same attendance cycle, it is found that driver A has a sign-in record and an attendance binding relationship is established with passenger vehicle 1. The attendance access judgment result is determined to be access passed, and driver A can perform a sign-out operation. If driver A fails the first sign-out operation, he / she can perform a second sign-out operation.

[0067] Step S108: If the attendance access judgment result is that access is approved, update the attendance status and the vehicle status according to the operation information sent by the client.

[0068] The operation information refers to the records of check-in or check-out operations submitted by the drivers and passengers.

[0069] In practical applications, it is necessary to update the attendance status of drivers and conductors and the vehicle status of passenger vehicles in real time to improve the accuracy of attendance and ensure the reliability of attendance operations performed by drivers and conductors.

[0070] The update can only be performed if the attendance access judgment result is "access approved," meaning the driver or passenger has performed a sign-in or sign-out operation. The updates to the attendance status and vehicle status differ depending on the type of operation.

[0071] After the client receives and displays the attendance access judgment, the driver and passenger will perform a sign-in or sign-out operation according to the operation prompts. The client will send the operation information of the driver and passenger to the server, and the server will update the attendance status of the driver and passenger and the vehicle status of the passenger vehicle based on the operation information.

[0072] In one optional implementation of this embodiment, the attendance status and the vehicle status are updated in the following manner:

[0073] If the operation type sent by the client is a check-in operation type, then an attendance binding relationship is established between the driver and the passenger vehicle to which the vehicle information submitted by the driver belongs.

[0074] Update the attendance status of the driver and conductor to "signed in" in the attendance record table; record the vehicle information of passenger vehicles that are linked to the attendance of the driver and conductor; and update the vehicle status of the passenger vehicles to "linked".

[0075] or,

[0076] If the operation type is a sign-out operation type, then the attendance binding relationship between the driver / passenger and the passenger vehicle to which the vehicle information submitted by the driver / passenger belongs is released.

[0077] Update the attendance status of the driver and conductor to "not checked in" in the attendance record table; and update the vehicle status of the passenger vehicle to "unbound".

[0078] The operation information includes at least one of the following: operation account, operation vehicle, operation time, and operation type.

[0079] For example, if driver A's check-in operation on passenger vehicle 1 is obtained, an attendance binding relationship between driver A and passenger vehicle 1 is established. Driver A's attendance status is updated to "checked in" in the attendance record table. The vehicle information of passenger vehicle 1 is recorded after driver A, and the vehicle status of passenger vehicle 1 is updated to "bound".

[0080] For example, if driver A's sign-out operation on passenger vehicle 1 is obtained, the attendance binding relationship between driver A and passenger vehicle 1 is removed, driver A's attendance record is updated to "not signed in" in the attendance record table, and the vehicle status of passenger vehicle 1 is updated to "unbound".

[0081] In specific implementation, after updating the attendance status and the vehicle status, the update result is fed back to the client. In an optional implementation provided in this embodiment, after updating the attendance status of the driver and passengers and the vehicle information of the passenger vehicle, the update result is sent to the client.

[0082] In practical applications, to prevent drivers and passengers from falsely signing in, vehicle operation information is used to determine the authenticity and validity of their sign-in operations. In one optional implementation of this embodiment, after updating the driver's / passenger's sign-in status to "signed in," the validity of the sign-in operation is determined based on the operation status of the passenger vehicle with which the driver / passenger's attendance is linked. Specifically, the determination is made in the following manner:

[0083] Obtain the operating trajectory of the passenger vehicle;

[0084] Based on the aforementioned operating trajectory, it is determined whether the passenger vehicle is in operation within a specific time period;

[0085] If so, the check-in operation of the driver and passengers is determined to be a valid operation;

[0086] If not, determine that the driver's check-in operation is invalid, and remove the attendance binding relationship between the driver / passenger and the passenger vehicle.

[0087] For example, if driver A checks in on passenger vehicle 1, to ensure that driver A's check-in is valid, the operating status of passenger vehicle A is obtained based on the vehicle's location function. If passenger vehicle 1 is in a closed state within a specific time, it is determined that driver A has performed an invalid operation, the attendance binding relationship between driver A and passenger vehicle 1 is removed, and driver A's invalid attendance is recorded.

[0088] The following is in conjunction with the appendix Figure 2 Taking the application of the attendance processing method provided in this embodiment in a passenger check-in scenario as an example, the attendance processing method provided in this embodiment will be further explained. (Refer to the appendix.) Figure 2 The attendance processing method applied to the sign-in processing scenario specifically includes steps S202 to S218.

[0089] Step S202: Receive the check-in query request sent by the client.

[0090] The attendance query request includes the driver's identification and the passenger vehicle's vehicle identification.

[0091] Step S204: Based on the identity identifier and the vehicle identifier, query to obtain that the driver's identity identifier belongs to the established driver and passenger table; and the passenger vehicle information exists in the established passenger vehicle table.

[0092] Step S206: Query the established attendance record table to find that the driver's attendance status is "not checked in" and the passenger vehicle's vehicle status is "not bound".

[0093] Step S208: Determine the attendance access judgment result as access passed.

[0094] Step S210: Send the attendance access judgment result to the client.

[0095] The attendance access judgment results include the driver's attendance status and the vehicle status of the passenger vehicle, and determine the attendance operation that the driver is allowed to perform as a sign-in operation.

[0096] Step S212: Receive the operation information sent by the client indicating that the driver is performing a check-in operation.

[0097] Step S214: Based on the operation information, establish an attendance binding relationship between the driver and the passenger vehicle.

[0098] Step S216: Based on the attendance binding relationship, update the driver's attendance status to "signed in" and the passenger vehicle's vehicle status to "bound" in the attendance record table, and send the update result to the client.

[0099] Step S218: Based on the attendance binding relationship, update the driver's attendance status to "signed in" and the passenger vehicle's vehicle status to "bound" in the attendance record table, and send the update result to the client.

[0100] In practice, the system obtains the operating trajectory of the passenger vehicle and its operational status. If the passenger vehicle does not have an operating trajectory within a specific time period, the driver's check-in operation is determined to be invalid, and the attendance binding relationship between the driver and the passenger vehicle is terminated. If the passenger vehicle has an operating trajectory within a specific time period, the driver's check-in operation is determined to be valid.

[0101] In summary, the attendance processing method, upon receiving an attendance query request, queries the attendance status of drivers and conductors and the vehicle status of passenger vehicles contained in the query request. Based on the queried attendance and vehicle statuses, it determines whether the drivers and conductors are eligible to perform attendance operations, sends the determination result to the client, and updates the attendance status of the drivers and conductors and the vehicle status of passenger vehicles based on the operation information sent by the client. This improves the simplicity and accuracy of attendance management, enhances its comprehensiveness, and ensures the effectiveness of drivers and conductors' attendance operations.

[0102] Another attendance processing method provided in this manual is illustrated in the following example:

[0103] See attached document Figure 3 The attached diagram illustrates a flowchart of another attendance processing method provided in this embodiment. (Refer to the attached diagram.) Figure 4 This embodiment illustrates a flowchart of another attendance processing method applied to passenger check-in scenarios.

[0104] The attendance processing method provided in this embodiment is executed by a client, and it works in conjunction with the attendance processing method described above, which is executed by a server. Therefore, the description is relatively simple. For relevant parts, please refer to the corresponding descriptions in the attendance method embodiments provided above. The method embodiments described below are merely illustrative.

[0105] See attached document Figure 3 The attendance processing method provided in this embodiment specifically includes the following steps S302 to S310.

[0106] Step S302: Collect the image identification code configured for passenger vehicles.

[0107] In practical applications, during the attendance processing, drivers and passengers first need to log in to the client and interact with a third-party application (client) for identity authentication. This authentication can be achieved through methods such as passwords, CA (Certificate Authority) authentication, or blockchain. After successful authentication, the driver or passenger submits their identity and vehicle information, which is then uploaded to the attendance processing platform by the client. Upon receiving the driver's and passenger's identity and vehicle information from the client, the attendance processing platform performs a query and generates a prompt that allows the driver or passenger to perform the attendance operation, which is then returned to the driver or passenger on the client.

[0108] This embodiment provides an attendance processing method applied to a client. In conjunction with the server-side attendance processing method provided in the previous embodiment, it improves the efficiency of driver and passenger attendance management at passenger stations by leveraging vehicle status. Specifically, by collecting driver and passenger identity information and vehicle information submitted by them, the method obtains the driver's / passenger's identity identifier and the vehicle identifier of the passenger vehicle to which the vehicle information belongs. It then generates an attendance query request for the driver / passenger and the passenger vehicle and sends it to the server. The server obtains the attendance access judgment result through the query and sends it to the client. The client displays the attendance access judgment result and obtains the driver / passenger's operation information, then sends the operation information back to the server. Finally, the client receives and displays the server's update results for the driver / passenger and the passenger vehicle, thereby improving the simplicity and accuracy of attendance processing and enhancing drivers' / passenger's awareness of the attendance process.

[0109] In practice, during the attendance processing for drivers and passengers, it is first necessary to configure different image identification codes for different passenger vehicles based on their license plate numbers, ensuring a one-to-one correspondence between passenger vehicles and image identification codes. When submitting attendance records, drivers and passengers obtain different vehicle information based on the different image identification codes. The image identification code refers to an image code carrying vehicle information, configured according to the different license plate numbers of passenger vehicles.

[0110] In one optional implementation of this embodiment, the image identification code of the passenger vehicle is configured according to the license plate number of the passenger vehicle.

[0111] For example, if passenger station A has 50 passenger vehicles, a unique image identification code is generated for each of the 50 vehicles based on their license plate numbers.

[0112] Step S304: Identify the image identification code to obtain the identity identification of the driver and passengers and the vehicle identification of the passenger vehicle.

[0113] In practical applications, drivers and passengers first log in to a third-party application (client) using their own accounts, and then scan the image identification code of the passenger vehicle through the third-party application. The third-party application obtains the driver's and passengers' identity information and the vehicle information corresponding to the image identification code by recognizing the driver's and passengers' account information and the image identification code, and further obtains the driver's and passengers' identity identifier and the vehicle identifier of the passenger vehicle.

[0114] In practice, drivers and passengers scan the image identification codes to identify the image identification codes that belong to different passenger vehicles according to different license plate numbers, and submit the driver's and passengers' identity information and the vehicle information of the passenger vehicle to the client. Based on the identity information and the vehicle information, the client obtains the driver's and passengers' identity identifier and the passenger vehicle's vehicle identifier.

[0115] For example, if driver A wants to check in at passenger vehicle 1, he can use a third-party application to scan the QR code configured according to the license plate number of passenger vehicle 1. The third-party application obtains the identity information of driver A and the vehicle information of passenger vehicle 1 by recognizing the QR code, and further obtains the identity identifier of driver A and the vehicle identifier of passenger vehicle 1.

[0116] Step S306: Generate an attendance query request carrying the identity identifier and the vehicle identifier and send it to the server.

[0117] In practice, the client obtains the identity identifier of the driver and the vehicle identifier of the passenger vehicle, generates an attendance query request carrying the identity identifier and the vehicle identifier, and sends the attendance query request to the server.

[0118] For example, after obtaining the identity of driver A and the vehicle identification of passenger vehicle 1 to which the vehicle information submitted by driver A via QR code belongs, the client generates an attendance query request carrying the identity of driver A and the vehicle identification of passenger vehicle 1 and sends it to the server.

[0119] Step S308: Receive and display the attendance access judgment result sent by the server.

[0120] In practical applications, the attendance query request is sent to the server. The server needs to query and judge to determine whether the driver and conductor can perform attendance operations on the passenger vehicle. After querying and judging, the query and judgment results are sent to the client and displayed to the driver and conductor by the client.

[0121] In practice, by querying, if the driver's identity is not in the driver's / passenger table of the target passenger transport unit where the driver / passenger is located, or the vehicle's identity is not in the passenger vehicle table of the target passenger transport unit, then the server sends a prompt prohibiting the driver / passenger from performing attendance operations. If the driver's / passenger's identity is in the driver's / passenger table and the vehicle's identity is in the passenger vehicle table, then, based on this, the server queries the attendance record table of the current attendance period for the driver / passenger's attendance status and the vehicle's vehicle status. If the driver / passenger's attendance status is "not checked in" and the vehicle's vehicle status is "unbound," the server will allow the driver / passenger to perform attendance operations on the passenger vehicle, and the attendance operation will be a check-in operation. The client receives the driver / passenger's "not checked in," the passenger vehicle's "unbound," and the check-in operation prompt and sends a notification to the driver / passenger. The server displays the following information: If the driver / passenger's attendance status is "checked in" and the passenger vehicle's status is "unbound," or if the driver / passenger's attendance status is "not checked in" and the passenger vehicle's status is "bound," the server determines that the driver / passenger cannot perform attendance operations on the passenger vehicle. The client receives and displays the driver / passenger's attendance status, the passenger vehicle's attendance status, and a notification that the driver / passenger cannot perform attendance operations on the passenger vehicle. If the driver / passenger's attendance status is "checked in" and the passenger vehicle has established an attendance binding relationship with the driver / passenger, and the passenger vehicle's status is "bound," the server allows the driver / passenger to perform attendance operations on the passenger vehicle, and the attendance operation is a check-out operation. The client receives the driver / passenger's "checked in," the passenger vehicle's "bound," and a check-out operation notification, and displays them to the driver / passenger.

[0122] To improve ease of use for drivers and passengers, this embodiment provides an optional implementation method for receiving the attendance access judgment result. For check-in and check-out operations, the main methods are as follows:

[0123] Receive the attendance access judgment result sent by the server; the attendance access judgment result includes the attendance status of the driver and conductor and the vehicle status of the passenger vehicle;

[0124] If the attendance access judgment result is access approved, and the attendance status is not checked in, and the vehicle status is not bound, then a check-in prompt will be displayed.

[0125] If the attendance access judgment result is that the access is approved, and the driver and passenger personnel have established an attendance binding relationship with the passenger vehicle, then an operation prompt for check-out will be displayed.

[0126] For example, if driver A submits vehicle information for passenger vehicle 1 by scanning a QR code, and a query shows that driver A's identity is in the driver list of the target passenger station to which driver A belongs, and passenger vehicle 1's vehicle identity is in the passenger vehicle list of the target passenger station, then the attendance record table for the current attendance period will be queried for driver A's attendance status and passenger vehicle 1's vehicle status. If driver A's attendance status is "not checked in" and passenger vehicle 1's vehicle status is "unbound," the client will receive and display driver A's "not checked in" status and passenger vehicle 1's "unbound" status, along with a prompt allowing driver A to check in; if driver A's attendance status is "checked in" and passenger vehicle 1's vehicle status is "unbound," the client will receive and display driver A's "not checked in" status and passenger vehicle 1's "unbound" status, along with a prompt allowing driver A to check in. If the vehicle status of vehicle 1 is unbound, or the attendance status of driver / passenger A is not checked in and the vehicle status of vehicle 1 is bound, then the client receives and displays the attendance status of driver / passenger A, the vehicle status of vehicle 1, and an operation prompt indicating that driver / passenger A cannot perform attendance operations on vehicle 1; if the attendance status of driver / passenger A is checked in, the vehicle status of vehicle 1 is bound, and driver / passenger A has established an attendance binding relationship with vehicle 1, then the client receives and displays the checked-in status of driver / passenger A, the bound status of vehicle 1, the attendance binding relationship between driver / passenger A and vehicle 1, and an operation prompt indicating that driver / passenger A is allowed to perform a check-out operation.

[0127] In practical applications, only one driver is allowed to sign in for the same passenger vehicle, while multiple attendants are allowed to sign in. In one optional implementation of this embodiment, the personnel include the driver and attendants; for the same passenger vehicle, only one driver is allowed to sign in during any attendance period, and multiple attendants are allowed to sign in for the same passenger vehicle.

[0128] For example, if, within an attendance cycle, driver M has already checked in for passenger vehicle 1, and after checking, attendant N's attendance status is found to be "not checked in," then attendant N is allowed to check in for passenger vehicle 1.

[0129] Step S310: If the attendance access judgment result is that the access is approved, obtain the operation information of the driver and passenger and send it to the server.

[0130] In practice, after the client displays the attendance judgment result to the driver and passenger, the driver and passenger perform a sign-in or sign-out operation based on the attendance access judgment result.

[0131] In one optional implementation of this embodiment, the operation type submitted by the driver / passenger is determined in the following manner:

[0132] Upon detecting a check-in operation submitted by the driver or passenger, the check-in operation information is obtained and sent to the server;

[0133] Upon detecting a sign-out operation submitted by the driver or passenger, the sign-out operation information is obtained and sent to the server;

[0134] The operation information includes at least one of the following:

[0135] Operation account, operation vehicle, operation time, and operation type.

[0136] In practical applications, in order to ensure that the drivers and passengers can clearly see whether their attendance operations are successful, and in order to improve the fairness of attendance management, in an optional implementation of this embodiment, after the client obtains the driver's and passengers' operation information and sends it to the server, it also needs to receive and display the update results sent by the server.

[0137] For example, if driver A receives information from the client that their attendance status is "not checked in," the vehicle status of passenger vehicle 1 is "unbound," and that a check-in operation can be performed on passenger vehicle 1, and then selects to perform the check-in operation, the client sends the operation information of driver A performing the check-in operation on passenger vehicle 1 to the server. After the server updates the attendance status of driver A and the vehicle status of passenger vehicle 1, it sends the update result to the client, which then displays it to driver A.

[0138] For example, if driver A receives information from the client that their attendance status is "checked in," the vehicle status of passenger vehicle 1 is "bound," and that a check-out operation can be performed on passenger vehicle 1, and then chooses to perform a check-out operation, the client sends the operation information of driver A performing a check-out operation on passenger vehicle 1 to the server. After the server updates the attendance status of driver A and the vehicle status of passenger vehicle 1, it sends the update result to the client, which then displays it to driver A.

[0139] The following is in conjunction with the appendix Figure 4 Taking the application of another attendance processing method provided in this embodiment in a passenger check-in scenario as an example, this embodiment will further explain another attendance processing method provided in this embodiment. (Refer to the appendix.) Figure 4 The attendance processing method applied to the sign-in processing scenario specifically includes steps S402 to S414.

[0140] Step S402: During the process of detecting the driver scanning the graphic identification code, the graphic identification code configured in the passenger vehicle is collected.

[0141] Step S404: Identify the image identification code scanned by the driver to obtain the driver's identity and the vehicle identification of the passenger vehicle.

[0142] Step S406: Generate a check-in query request based on the driver's identity and the passenger vehicle's vehicle identification.

[0143] Step S408: Send a check-in query request to the server.

[0144] Step S410: Receive the attendance access judgment result sent by the server, indicating that access has been granted.

[0145] Step S412: Obtain the driver's check-in operation and send the driver's check-in operation information to the server.

[0146] Step S414: Receive and display the update result sent by the server to the driver.

[0147] In summary, the attendance recording method collects the identity information of drivers and passengers, as well as the vehicle information submitted by them, to obtain the identity identifier of the drivers and passengers and the vehicle identifier of the passenger vehicle to which the vehicle information belongs. It then generates an attendance query request for the drivers and passengers and the passenger vehicle and sends it to the server. The server obtains the attendance access judgment result through the query and sends it to the client. The client displays the attendance access judgment result and obtains the operation information of the drivers and passengers, then sends the operation information back to the server. Finally, the client receives and displays the server's update results for the drivers and passengers and the passenger vehicle. This improves the simplicity of attendance tracking and enhances drivers' and passengers' awareness of the attendance process.

[0148] The following is an embodiment of an attendance processing device provided in this manual:

[0149] In the above embodiments, an attendance processing method is provided, and correspondingly, an attendance processing device is also provided, which will be described below with reference to the accompanying drawings.

[0150] See attached document Figure 5 The diagram shows a time attendance processing device provided in this embodiment.

[0151] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0152] This embodiment provides an attendance processing device, including:

[0153] The request receiving module 502 is configured to receive attendance query requests sent by the client; the attendance query request includes the identity identifiers of the driver and conductor and the vehicle identifiers of the passenger vehicles.

[0154] The query module 504 is configured to query the attendance status of the driver and passengers and the vehicle status of the passenger vehicle based on the identity identifier and the vehicle identifier.

[0155] The judgment module 506 is configured to perform attendance access judgment on the driver and passenger vehicle based on the attendance status and the vehicle status, and send the attendance access judgment result to the client.

[0156] The update module 508 is configured to update the attendance status and the vehicle status according to the operation information sent by the client when the attendance access judgment result is access passed.

[0157] Optionally, the attendance processing device further includes:

[0158] The information acquisition module is configured to acquire the identity information of the driver and passengers of the target passenger transport unit, as well as the vehicle information of the passenger vehicle.

[0159] The information table construction module is configured to construct a driver and passenger table based on the identity identifiers contained in the identity information, and to construct a passenger vehicle table based on the vehicle identifiers contained in the vehicle information.

[0160] Optionally, the query module 504 includes:

[0161] The information judgment submodule is configured to determine whether the driver and passenger identification information contained in the attendance query request exists in the driver and passenger personnel table, and whether the passenger vehicle identification information contained in the attendance query request exists in the passenger vehicle table.

[0162] If so, the permission opening unit is configured to grant the driver and passengers attendance permissions for the passenger vehicle.

[0163] The information query submodule is configured to query the attendance status of the drivers and passengers and the vehicle status of the passenger vehicles in the attendance record table during the current attendance period.

[0164] Optionally, the determination module 506 includes:

[0165] The attendance record query submodule is configured to query the attendance record table to see if the attendance record of the driver or conductor exists in the current attendance period;

[0166] If they exist, the binding relationship query unit is run. The binding relationship query unit is configured to query whether the passenger vehicle has established an attendance binding relationship with the driver and conductor. If so, the determination unit is run. The determination unit is configured to determine that the attendance access judgment result of the attendance access judgment is access passed.

[0167] If it does not exist, the vehicle binding relationship query unit is run. The vehicle binding relationship query unit is configured to query whether the passenger vehicle has an attendance binding relationship; if not, the determination unit is run.

[0168] Optionally, if the operation type in the operation information is a check-in operation, then the attendance access judgment includes:

[0169] The sign-in judgment submodule is configured to determine the attendance access judgment result as access passed if the driver and conductor have no sign-in record and the passenger vehicle has no binding record in the current attendance cycle.

[0170] Optionally, if the operation type in the operation information is a sign-out operation, then the attendance access judgment includes:

[0171] The sign-out judgment submodule is configured to determine the attendance access judgment result as access passed if, in the current attendance cycle, it is found that the driver and conductor have sign-in records and the passenger vehicle has an attendance binding relationship with the driver and conductor.

[0172] The secondary sign-out submodule is configured to allow the driver and passengers to perform a secondary sign-out operation if the initial sign-out operation fails.

[0173] Optionally, the update module 508 includes:

[0174] The sign-in update submodule is configured to establish an attendance binding relationship between the driver / passenger and the passenger vehicle to which the vehicle information submitted by the driver / passenger belongs if the operation type sent by the client is a sign-in operation.

[0175] Update the attendance status of the driver and conductor to "signed in" in the attendance record table; record the vehicle information of passenger vehicles that are linked to the attendance of the driver and conductor; and update the vehicle status of the passenger vehicles to "linked".

[0176] The sign-out update submodule is configured to, if the operation type is sign-out operation type, release the attendance binding relationship between the driver / passenger and the passenger vehicle to which the vehicle information submitted by the driver / passenger belongs;

[0177] Update the attendance status of the driver and conductor to "not checked in" in the attendance record table; and update the vehicle status of the passenger vehicle to "unbound".

[0178] The operation information includes at least one of the following: operation account, operation vehicle, operation time, and operation type.

[0179] Optionally, the attendance processing device further includes:

[0180] The update result sending module is configured to send the update result of the update to the client.

[0181] Optionally, the personnel include drivers and attendants; one driver is allowed to sign in for the same passenger vehicle in any attendance cycle, and multiple attendants are allowed to sign in for the same passenger vehicle.

[0182] Accordingly, the judgment module 506 includes:

[0183] The flight attendant access submodule is configured to, if the driver or conductor is a flight attendant, determine the attendance access judgment result of the attendance access judgment as access passed in the attendance cycle.

[0184] Optionally, if the operation type in the operation information is a check-in operation, the attendance processing device further includes:

[0185] The operation trajectory determination module is configured to obtain the operation trajectory of the passenger vehicle;

[0186] The operation status determination module is configured to determine whether the passenger vehicle is in operation within a specific time period based on the operation trajectory.

[0187] If so, the valid determination submodule is run, which is configured to determine that the driver's and passenger's check-in operation is a valid operation;

[0188] If not, the invalid determination submodule is run. The invalid determination submodule is configured to determine that the driver's and passenger's check-in operation is invalid and to remove the attendance binding relationship between the driver and passenger and the passenger vehicle.

[0189] Another embodiment of the attendance processing device provided in this manual is as follows:

[0190] In the above embodiments, another attendance processing method is provided, and correspondingly, another attendance processing device is also provided, which will be described below with reference to the accompanying drawings.

[0191] See attached document Figure 6 The diagram shows another attendance processing device provided in this embodiment.

[0192] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0193] This embodiment provides another attendance processing device, including:

[0194] The data acquisition module 602 is configured to acquire image identification codes of passenger vehicles.

[0195] The identification module 604 is configured to identify the image identification code to obtain the identity identification of the driver and passengers and the vehicle identification of the passenger vehicle;

[0196] The request sending module 606 is configured to generate an attendance query request carrying the identity identifier and the vehicle identifier and send it to the server;

[0197] The judgment result receiving module 608 is configured to receive and display the attendance access judgment result sent by the server;

[0198] The operation information sending module 610 is configured to obtain the operation information of the driver and passenger and send it to the server when the attendance access judgment result is access passed.

[0199] Optionally, the image identification code of the passenger vehicle is configured according to the license plate number of the passenger vehicle.

[0200] Optionally, the judgment result receiving module 608 includes:

[0201] The result receiving submodule is configured to receive the attendance access judgment result sent by the server; the attendance access judgment result includes the attendance status of the driver and conductor and the vehicle status of the passenger vehicle.

[0202] The sign-in display submodule is configured to display a sign-in prompt if the attendance access judgment result is access passed, the attendance status is not signed in, and the vehicle status is not bound.

[0203] The sign-out display submodule is configured to display a sign-out prompt if the attendance access judgment result is access passed and the driver and passenger have established an attendance binding relationship with the passenger vehicle.

[0204] Optionally, the operation information sending module 610 includes:

[0205] The sign-in information sending submodule is configured to, upon detecting a sign-in operation submitted by the driver or passenger, obtain the sign-in operation information of the sign-in operation and send it to the server;

[0206] The sign-out information sending submodule is configured to, upon detecting a sign-out operation submitted by the driver or passenger, obtain the sign-out operation information of the sign-out operation and send it to the server;

[0207] The operation information includes at least one of the following:

[0208] Operation account, operation vehicle, operation time, and operation type.

[0209] Optionally, the attendance processing device further includes:

[0210] The update result display module is configured to receive and display the update results sent by the server.

[0211] Optionally, the personnel include drivers and attendants; one driver is allowed to sign in for the same passenger vehicle in any attendance cycle, and multiple attendants are allowed to sign in for the same passenger vehicle.

[0212] The following is an example of an attendance processing device provided in this manual:

[0213] Corresponding to the attendance processing method described above, based on the same technical concept, one or more embodiments of this specification also provide an attendance processing device for executing the attendance processing method described above. Figure 7 This is a schematic diagram of the structure of an attendance processing device provided for one or more embodiments of this specification.

[0214] like Figure 7 As shown, attendance processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 701 and memory 702, with memory 702 storing one or more application programs or data. Memory 702 can be temporary or persistent storage. The application programs stored in memory 702 may include one or more modules (not shown), each module including a series of computer-executable instructions from the attendance processing device. Furthermore, processor 701 may be configured to communicate with memory 702, executing the series of computer-executable instructions stored in memory 702 on the attendance processing device. The attendance processing device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, one or more keyboards 706, etc.

[0215] In one specific embodiment, the attendance processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the attendance processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0216] Receive attendance query request sent by the client; the attendance query request includes the identity identifier of the driver and conductor and the vehicle identifier of the passenger vehicle;

[0217] Based on the identity identifier and the vehicle identifier, query the attendance status of the driver and passengers and the vehicle status of the passenger vehicle;

[0218] Based on the attendance status and the vehicle status, attendance access judgment is performed on the driver and passenger vehicle, and the attendance access judgment result is sent to the client.

[0219] If the attendance access judgment result is that access is approved, the attendance status and the vehicle status are updated according to the operation information sent by the client.

[0220] Optionally, the computer-executable instructions, when executed, may also include:

[0221] Obtain the identity information of the drivers and passengers of the target passenger transport unit, as well as the vehicle information of the passenger vehicles;

[0222] A driver and passenger table is constructed based on the identity identifiers contained in the identity information, and a passenger vehicle table is constructed based on the vehicle identifiers contained in the vehicle information.

[0223] Optionally, the computer-executable instructions, when executed, may also include:

[0224] The update result is sent to the client.

[0225] Optionally, the personnel include drivers and attendants; one driver is allowed to sign in for the same passenger vehicle in any attendance cycle, and multiple attendants are allowed to sign in for the same passenger vehicle.

[0226] Accordingly, the attendance and access determination for the drivers and passengers and the passenger vehicles includes:

[0227] If the driver or conductor is a flight attendant, the attendance access judgment result of the attendance access judgment in the attendance cycle is "access approved".

[0228] Optionally, if the operation type in the operation information is a check-in operation, the computer-executable instruction, when executed, also includes:

[0229] Obtain the operating trajectory of the passenger vehicle;

[0230] Based on the aforementioned operating trajectory, it is determined whether the passenger vehicle is in operation within a specific time period;

[0231] If so, the check-in operation of the driver and passengers is determined to be a valid operation;

[0232] If not, determine that the driver's check-in operation is invalid, and remove the attendance binding relationship between the driver / passenger and the passenger vehicle.

[0233] Another embodiment of the attendance processing device provided in this manual is as follows:

[0234] Corresponding to the other attendance processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another attendance processing device for performing the other attendance processing method described above. Figure 8 This is a schematic diagram of another attendance processing device provided in one or more embodiments of this specification.

[0235] like Figure 8 As shown, attendance processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and memories 802, with the memory 802 storing one or more application programs or data. The memory 802 can be temporary or persistent storage. The application programs stored in the memory 802 may include one or more modules (not shown), each module including a series of computer-executable instructions from the attendance processing device. Furthermore, the processor 801 may be configured to communicate with the memory 802, executing the series of computer-executable instructions stored in the memory 802 on the attendance processing device. The attendance processing device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0236] In one specific embodiment, the attendance processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the attendance processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0237] Collect image identification codes for passenger vehicles;

[0238] Identify the image identification code to obtain the identity identification of the driver and passengers, as well as the vehicle identification of the passenger vehicle;

[0239] Generate an attendance query request carrying the identity identifier and the vehicle identifier and send it to the server;

[0240] Receive and display the attendance access judgment results sent by the server;

[0241] If the attendance access judgment result is that access is approved, the operation information of the driver and passenger is obtained and sent to the server.

[0242] Optionally, the image identification code of the passenger vehicle is configured according to the license plate number of the passenger vehicle.

[0243] Optionally, the computer-executable instructions, when executed, may also include:

[0244] Receive and display the update results sent by the server.

[0245] Optionally, the personnel include drivers and attendants; one driver is allowed to sign in for the same passenger vehicle in any attendance cycle, and multiple attendants are allowed to sign in for the same passenger vehicle.

[0246] This specification provides an example of a storage medium as follows:

[0247] Corresponding to the attendance processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0248] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0249] Receive attendance query request sent by the client; the attendance query request includes the identity identifier of the driver and conductor and the vehicle identifier of the passenger vehicle;

[0250] Based on the identity identifier and the vehicle identifier, query the attendance status of the driver and passengers and the vehicle status of the passenger vehicle;

[0251] Based on the attendance status and the vehicle status, attendance access judgment is performed on the driver and passenger vehicle, and the attendance access judgment result is sent to the client.

[0252] If the attendance access judgment result is that access is approved, the attendance status and the vehicle status are updated according to the operation information sent by the client.

[0253] Optionally, the computer-executable instructions, when executed, also implement the following processes:

[0254] Obtain the identity information of the drivers and passengers of the target passenger transport unit, as well as the vehicle information of the passenger vehicles;

[0255] A driver and passenger table is constructed based on the identity identifiers contained in the identity information, and a passenger vehicle table is constructed based on the vehicle identifiers contained in the vehicle information.

[0256] Optionally, the computer-executable instructions, when executed, also implement the following processes:

[0257] The update result is sent to the client.

[0258] Optionally, the personnel include drivers and attendants; one driver is allowed to sign in for the same passenger vehicle in any attendance cycle, and multiple attendants are allowed to sign in for the same passenger vehicle.

[0259] Accordingly, the attendance and access determination for the drivers and passengers and the passenger vehicles includes:

[0260] If the driver or conductor is a flight attendant, the attendance access judgment result of the attendance access judgment in the attendance cycle is "access approved".

[0261] Optionally, if the operation type in the operation information is a check-in operation, the computer-executable instruction, when executed, also implements the following process:

[0262] Obtain the operating trajectory of the passenger vehicle;

[0263] Based on the aforementioned operating trajectory, it is determined whether the passenger vehicle is in operation within a specific time period;

[0264] If so, the check-in operation of the driver and passengers is determined to be a valid operation;

[0265] If not, determine that the driver's check-in operation is invalid, and remove the attendance binding relationship between the driver / passenger and the passenger vehicle.

[0266] Another embodiment of the storage medium provided in this specification is as follows:

[0267] In response to another attendance processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0268] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0269] Collect image identification codes for passenger vehicles;

[0270] Identify the image identification code to obtain the identity identification of the driver and passengers, as well as the vehicle identification of the passenger vehicle;

[0271] Generate an attendance query request carrying the identity identifier and the vehicle identifier and send it to the server;

[0272] Receive and display the attendance access judgment results sent by the server;

[0273] If the attendance access judgment result is that access is approved, the operation information of the driver and passenger is obtained and sent to the server.

[0274] Optionally, the image identification code of the passenger vehicle is configured according to the license plate number of the passenger vehicle.

[0275] Optionally, the computer-executable instructions, when executed, also implement the following processes:

[0276] Receive and display the update results sent by the server.

[0277] Optionally, the personnel include drivers and attendants; one driver is allowed to sign in for the same passenger vehicle in any attendance cycle, and multiple attendants are allowed to sign in for the same passenger vehicle.

[0278] It should be noted that the embodiments concerning storage media and the embodiments concerning user resource processing methods in this specification are based on the same inventive concept. Therefore, the specific implementation of these embodiments can refer to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0279] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0280] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0281] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the modules included therein for implementing various functions can also be considered structures within the hardware component. Alternatively, the modules for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0282] The systems, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0283] For ease of description, the above modules are described separately as various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0284] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0285] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A module that specifies the function in one or more boxes.

[0286] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction modules implemented in a process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0287] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0288] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0289] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0290] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0291] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0292] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0293] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0294] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. An attendance processing method, applied to a server, comprising: Based on the received attendance query request, the attendance status of the driver and conductor and the vehicle status of the passenger vehicle contained in the attendance query request are queried in the attendance record table; the vehicle status includes whether the passenger vehicle has been checked in or checked out by the driver and conductor. The system checks whether the attendance records of the driver and conductor exist in the attendance record table during the current attendance period. If not, it checks whether the passenger vehicle has an attendance binding relationship. If not, it confirms that the access is approved and sends the access approval result to the client. The attendance status and vehicle status are updated based on the operation information sent by the client.

2. The attendance processing method according to claim 1, further comprising, before receiving the attendance query request: Obtain the identity information of the drivers and passengers of the target passenger transport unit, as well as the vehicle information of the passenger vehicles; A driver and passenger table is constructed based on the identity identifiers contained in the identity information, and a passenger vehicle table is constructed based on the vehicle identifiers contained in the vehicle information.

3. The attendance processing method according to claim 2, wherein querying the attendance status of the driver and conductor and the vehicle status of the passenger vehicle contained in the attendance query request in the attendance record table according to the received attendance query request includes: Determine whether the driver / passenger identification information contained in the attendance query request exists in the driver / passenger personnel table, and whether the passenger vehicle identification information contained in the attendance query request exists in the passenger vehicle table. If so, grant the drivers and passengers attendance permissions to perform attendance operations for the passenger vehicles; The attendance record table is used to query the attendance status of the drivers and conductors and the vehicle status of the passenger vehicles in the current attendance period.

4. The attendance processing method according to claim 1, wherein the operation type in the operation information is a sign-in operation; If, during the current attendance period, a query reveals that the driver / passenger has no attendance record and the passenger vehicle has no binding record, it is determined that the driver / passenger can establish an attendance binding relationship with the passenger vehicle.

5. The attendance processing method according to claim 1, after the step of querying the attendance status of the driver and conductor and the vehicle status of the passenger vehicle contained in the attendance query request in the attendance record table according to the received attendance query request, it further includes: Based on the attendance status and the vehicle status, determine whether the driver and passenger can sever the established attendance binding relationship with the passenger vehicle; If so, determine the access approval result and send the access approval result to the client; The attendance status and vehicle status are updated based on the operation information sent by the client, which is a sign-out operation.

6. According to the attendance processing method of claim 5, if the current attendance cycle query shows that the driver and conductor have a sign-in record and the passenger vehicle has an attendance binding relationship with the driver and conductor, it is determined that the driver and conductor and the passenger vehicle can release the established attendance binding relationship; If the initial check-out operation fails, the driver and passengers are allowed to perform a second check-out operation.

7. The attendance processing method according to claim 5, wherein updating the attendance status and the vehicle status based on the operation information (operation type: sign-out) sent by the client includes: Remove the attendance binding relationship between the driver / passenger and the passenger vehicle to which the vehicle information submitted by the driver / passenger belongs; Update the attendance status of the driver and conductor to "not checked in" in the attendance record table; and update the vehicle status of the passenger vehicle to "unbound". The operation information includes at least one of the following: operation account, operation vehicle, operation time, and operation type.

8. The attendance processing method according to claim 1, wherein updating the attendance status and the vehicle status based on the operation information sent by the client includes: Establish an attendance binding relationship between the drivers and passengers and the passenger vehicles to which the vehicle information submitted by the drivers and passengers belongs; Update the attendance status of the driver and conductor to "signed in" in the attendance record table; record the vehicle information of passenger vehicles that are linked to the attendance of the driver and conductor; and update the vehicle status of the passenger vehicles to "linked". The operation information includes at least one of the following: operation account, operation vehicle, operation time, and operation type.

9. The attendance processing method according to claim 1, after the step of updating the attendance status and the vehicle status according to the operation information sent by the client is performed, it further includes: The update result is sent to the client.

10. The attendance processing method according to claim 1, wherein the personnel include drivers and attendants; one driver is allowed to sign in for the same passenger vehicle in any attendance cycle, and multiple attendants are allowed to sign in for the same passenger vehicle.

11. The attendance processing method according to claim 1, after the step of updating the attendance status and the vehicle status according to the operation information sent by the client is performed, it further includes: Obtain the operating trajectory of the passenger vehicle; Based on the operating trajectory, it is determined whether the passenger vehicle is in operation within a preset time period; If so, the check-in operation of the driver and passengers is determined to be a valid operation; If not, determine that the driver's check-in operation is invalid, and remove the attendance binding relationship between the driver / passenger and the passenger vehicle.

12. An attendance processing method, applied to a client-side application, comprising: Collect the identity information of the driver and passengers and the vehicle information submitted, and obtain the identity identifiers of the driver and passengers and the vehicle identifiers of the passenger vehicles; A time attendance query request carrying the identity identifier and the vehicle identifier is generated and sent to the server; the server determines access approval based on the attendance status of the driver and conductor and the vehicle status of the passenger vehicle found in the attendance record table, provided that there is no attendance record of the driver and conductor in the current attendance period and the passenger vehicle has no attendance binding relationship; the vehicle status includes whether the passenger vehicle has been checked in or checked out by the driver and conductor. Receive and display the access approval result sent by the server, obtain the driver's and passenger's operation information and send it to the server.

13. The attendance processing method according to claim 12, wherein collecting the identity information of the driver and passengers and the submitted vehicle information to obtain the identity identifier of the driver and passengers and the vehicle identifier of the passenger vehicle includes: Collect the image identification codes configured on the passenger vehicles; The image identification code is configured according to the license plate number of the passenger vehicle; The image identification code is identified to obtain the identity identifier and the vehicle identifier.

14. The attendance processing method according to claim 12, wherein receiving and displaying the access approval judgment result sent by the server includes: Receive the access approval result sent by the server; The judgment result includes the attendance status of the driver and conductor and the vehicle status of the passenger vehicle; Display the check-in prompts.

15. The attendance processing method according to claim 12, wherein obtaining the driver's operation information and sending it to the server includes: Upon detecting a check-in operation submitted by the driver or passenger, the check-in operation information is obtained and sent to the server; wherein the operation information includes at least one of the following: Operation account, operation vehicle, operation time, and operation type.

16. The attendance processing method according to claim 12 further includes: If the driver and conductor have already established an attendance tracking relationship with the passenger vehicle, a prompt to sign out will be displayed. Upon detecting a sign-out operation submitted by the driver or passenger, the sign-out operation information is obtained and sent to the server.

17. An attendance processing device, operating on a server, comprising: The query module is configured to query the attendance status of drivers and conductors and the vehicle status of passenger vehicles contained in the attendance query request in the attendance record table based on the received attendance query request; the vehicle status includes whether the passenger vehicle has been checked in or checked out by the drivers and conductors. The judgment module is configured to query the attendance record table to see if there is an attendance record for the driver or conductor in the current attendance period. If not, it queries whether the passenger vehicle has an attendance binding relationship. If not, it determines that the access is approved and sends the access approval judgment result to the client. The update module is configured to update the attendance status and the vehicle status based on the operation information sent by the client.

18. An attendance processing device, operating on a client side, comprising: The data collection module is configured to collect the identity information of the driver and passengers and the vehicle information submitted, and to obtain the identity identifier of the driver and passengers and the vehicle identifier of the passenger vehicle. The request sending module is configured to generate an attendance query request carrying the identity identifier and the vehicle identifier and send it to the server; the server determines access approval based on the attendance status of the driver and conductor and the vehicle status of the passenger vehicle found in the attendance record table, provided that there is no attendance record of the driver and conductor in the current attendance period and no attendance binding relationship of the passenger vehicle; the vehicle status includes whether the passenger vehicle has been checked in or checked out by the driver and conductor. The judgment result receiving module is configured to receive and display the access approval judgment result sent by the server, obtain the operation information of the driver and passengers, and send it to the server.

19. An attendance processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Based on the received attendance query request, the attendance status of the driver and conductor and the vehicle status of the passenger vehicle contained in the attendance query request are queried in the attendance record table; the vehicle status includes whether the passenger vehicle has been checked in or checked out by the driver and conductor. The system checks whether the attendance records of the driver and conductor exist in the attendance record table during the current attendance period. If not, it checks whether the passenger vehicle has an attendance binding relationship. If not, it confirms that the access is approved and sends the access approval result to the client. The attendance status and vehicle status are updated based on the operation information sent by the client.

20. An attendance processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Collect the identity information of the driver and passengers and the vehicle information submitted, and obtain the identity identifiers of the driver and passengers and the vehicle identifiers of the passenger vehicles; A time attendance query request carrying the identity identifier and the vehicle identifier is generated and sent to the server; the server determines access approval based on the attendance status of the driver and conductor and the vehicle status of the passenger vehicle found in the attendance record table, provided that there is no attendance record of the driver and conductor in the current attendance period and the passenger vehicle has no attendance binding relationship; the vehicle status includes whether the passenger vehicle has been checked in or checked out by the driver and conductor. Receive and display the access approval result sent by the server, obtain the driver's and passenger's operation information and send it to the server.

21. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Based on the received attendance query request, the attendance status of the driver and conductor and the vehicle status of the passenger vehicle contained in the attendance query request are queried in the attendance record table; the vehicle status includes whether the passenger vehicle has been checked in or checked out by the driver and conductor. The system checks whether the attendance records of the driver and conductor exist in the attendance record table during the current attendance period. If not, it checks whether the passenger vehicle has an attendance binding relationship. If not, it confirms that the access is approved and sends the access approval result to the client. The attendance status and vehicle status are updated based on the operation information sent by the client.

22. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Collect the identity information of drivers and passengers, as well as the vehicle information submitted, to obtain the identity identifiers of drivers and passengers and the vehicle identifiers of passenger vehicles; A time attendance query request carrying the identity identifier and the vehicle identifier is generated and sent to the server; the server determines access approval based on the attendance status of the driver and conductor and the vehicle status of the passenger vehicle found in the attendance record table, provided that there is no attendance record of the driver and conductor in the current attendance period and the passenger vehicle has no attendance binding relationship; the vehicle status includes whether the passenger vehicle has been checked in or checked out by the driver and conductor. Receive and display the access approval result sent by the server, obtain the driver's and passenger's operation information and send it to the server.

Images