SIMULTANEOUS LOAD ASSIGNMENT AND DELIVERY MANAGEMENT SYSTEM AND METHOD
Patent Information
- Application Number
- TR202614837
- Authority / Receiving Office
- TR · TR
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-08-31
- Publication Date
- 2026-09-21
Smart Images
Figure 00000024_0000 
Figure 00000025_0000 
Figure 00000026_0000
Abstract
Description
1 TARIFF SIMULTANEOUS LOAD ASSIGNMENT AND DELIVERY MANAGEMENT SYSTEM AND METHOD Technical Area The invention enables multiple clients through a server (1) and a database (2). 5 from the terminal to shared data records simultaneously or at approximately the same time The submitted change requests are protected by write locks implemented at the database level, and Data consistency will be maintained using atomic database operations. a computer-applied system and method that enables processing; especially Shipment acceptance, vehicle allocation and delivery verification in road freight transportation. It relates to the controlled and consistent execution of operations. 10 Previous Technique Today, road freight transportation and delivery processes are carried out electronically. Various computer-based systems are used for its management. In these systems, the origin and destination of the shipment to be transported are generally specified. Point, load quantity, load characteristics and similar information are available electronically on 15 creation of drivers, carriers or vehicles capable of carrying out the transportation operation determination; communication of the transportation request to the relevant parties and its acceptance; shipment the association of a driver or vehicle with the transportation process in an electronic environment Monitoring is ensured. In document number WO2018106730A1, information regarding the shipment is received, 20 Location, duty status, and transport capacity of carriers or drivers. Dynamic system for evaluating information and matching accordingly. Load matching methods and systems are explained. Document number US7353181B2 describes the location of the vehicles and available transport. Allocating transportation tasks to vehicles by taking capacity information into consideration 25 A system for its implementation is described. Documents numbered US11392881B2 and US10896401B2 describe the location of the cargo vehicles. monitoring information, receiving load requests, identifying candidate vehicles, and Computerized applications for matching shipments with vehicles. The systems and methods are explained. 30 2 Document number US20180068269A1 describes the evaluation of transportation requests. Identification of candidate carriers and assignment of transportation services to carriers electronically Computerized methods for directing traffic are explained. The documents in question are suitable for a shipment or transportation operation in an electronic environment. Various solutions regarding matching with the driver, carrier or vehicle are discussed in section 5 of the technique. This indicates that it is in its known state. Document number WO2016039882A1, verification related to a delivery. the code is transmitted to the user and the said code is provided during delivery A verification-based structure is described. Therefore, a delivery process The technique is also known to be associated with an electronic verification piece of information or a code. This is among the solutions offered in this situation. In addition, simultaneous access to shared data records in computer systems and data integrity is being preserved in cases where change requests are implemented. database transaction and locking mechanisms also It is known. For example, in document number US7177866B2, 15 entries are made into the database records. checking simultaneous processes and database operations. Techniques related to coordination are explained. The document in question is loaded. Not specific to transportation, but controlling simultaneous access in database operations. It demonstrates general computer techniques related to this. However, freight transportation using distributed drive terminals 20 in their systems, multiple acceptance requests for the same shipment can be processed simultaneously or If the requests reach the server around the same time, they are separated from each other. processing independently of the same shipment by multiple drivers or vehicles This can lead to associations. Similarly, regarding different posts In simultaneous acceptance procedures, the same vehicle registration is considered available. 25 In that case, the vehicle in question may be allocated to multiple shipments and vehicle availability will be checked. risk of inconsistency occurring between data and shipment assignment data It is located. Specifically, the suitability status of the dispatch record for assignment and the related vehicle record. Availability status is 30 independent of each other during simultaneous transactions. If read and updated, the records are updated through a control process. Due to potential competition situations that may arise between them, multiple processes can send the same post. or it may be possible to assess the same vehicle as being in usable condition. This 3 The situation involves creating multiple assignments for the same post, or using the same tool multiple times. allocation of excess shipments or comparisons between shipment and vehicle records This can lead to conflicting data situations. Similar data... The integrity problem also arises during the delivery phase of the transportation process. It can be delivered. The delivery code will be verified to confirm receipt of the shipment. the process of making the vehicle available again and delivery The code usage status update processes are independent of each other. If implemented, this would create a race between verification and update processes. situations may arise or only a portion of the records in question may be available. The update resulted in inconsistent data situations. 10 Simultaneous verification requests for the same delivery code can also be received. Multiple deliveries if the necessary simultaneity control is not ensured. This can lead to the risk of creating a closure. Therefore, only one simultaneous acceptance request relating to the same post can be processed. Converting to a valid driver-vehicle assignment, subject to availability of the relevant vehicle registration. 15 the situation is being assessed under controlled access and the same vehicle simultaneously preventing allocation to multiple shipments, shipment and vehicle records. ensuring that changes related to data integrity are carried out and transferred accordingly. the process involves delivery verification during the delivery phase, and related shipments, vehicles, and 20 that ensures the controlled and consistent completion of delivery code records. A computer-based technical solution is needed. Brief Description of the Invention The invention is based on multiple driver terminals (3) relating to the same dispatch record (4). Acceptance requests submitted simultaneously or around the same time, shipment record (4) and write applied at the database level on the related vehicle registration (5) 25 Controlled by using locks and the integrity of a single database transaction. a computer-applied synchronous load assignment that enables processing in this manner and It is a delivery management system and method. In inventions, in processes carried out simultaneously or in close proximity to each other Preventing the inconsistent updating of shipment and vehicle records, a 30 The post should only be associated with a single driver and vehicle, and the same vehicle... Preventing allocation to multiple posts simultaneously This is provided. The invention is also verified during the delivery phase and 4 data update operations are consistent within the integrity of the database operation. It ensures its implementation. Within the scope of the invention, a database is created upon receipt of an acceptance request to the server (1). the process is initiated and the shipment record associated with the acceptance request (4), simultaneously contradictory The current status of the post is 5, locked with a write lock that prevents changes. It is being checked. If the shipment is found to be suitable for assignment... The driver submitting the acceptance request is verified for authorization; then, the relevant driver is contacted. The associated vehicle registration (5) is locked with a write lock within the same database operation. The current availability of the vehicle is being checked. The shipment record (4) is suitable for assignment and the vehicle record (5) is available 10 If available; the shipment record (4) and the relevant driver and vehicle record (5) the association of the post record (4) from the state open to assignment to the state assigned transfer of vehicle registration (5) from available status to state reserved for transport operation The processes of passing through and creating the relevant status record are done with the shipment record (4). The write locks on the vehicle registration (5) are preserved and the same database operation 15 is carried out within its entirety. All of these processes If successfully completed, the data changes are made permanent; If any of the operations cannot be completed, then the same database operation Data changes within this scope are being reverted. Other simultaneous acceptance requests relating to the same posting record (4) are subject to the previous valid 20 After the transaction is completed, the current status of the shipment record (4) It is being re-evaluated. The submission is now eligible for assignment. If none are available, these requests will be processed by assigning a new driver or vehicle. It is finalized without being created. Thus, multiple instances of the same post can be made. Association with the driver or vehicle is prevented. 25 In addition, the availability status of the vehicle registration (5) is processed in the same database. It is controlled under write lock and the relevant operation of the said lock Thanks to its protection until completion, simultaneous transmission of different shipments is possible. (5) available for more than one transaction of the same vehicle registration in the acceptance procedures This is considered as such and its allocation to multiple posts is prevented. 30 Thus, shipment and vehicle registrations conflict with each other as a result of simultaneous transactions. This prevents the situation from escalating. The invention also enables the controlled delivery phase of the transportation process. This ensures the completion of the process. In this context, the driver assigned to the relevant shipment... a delivery code verification request via driver terminal (3) Upon transmission to the server (1), a database operation is initiated; the shipment record (4) and delivery code record associated with the shipment (6), simultaneous conflicting changes 5 It is locked with write locks that prevent writing. The message can be sent via locked records. the vehicle must be in a suitable condition for delivery, and the driver performing the transaction must be relevant. there must be a driver assigned to the shipment and the delivery code registration (6) must be valid This is verified. In an application, the delivery process also follows a predetermined process. This is carried out depending on whether the delivery location condition is met. 10 If these verifications are successful, the delivery code registration (6) to be used, shipment record (4) to be delivered bringing, making the vehicle registration associated with the shipment (5) available again and Creating a delivery status record, maintaining the integrity of the same database transaction. By carrying out the process within this framework, the transportation process is completed consistently. 15 Thus, between verification and delivery closing data updates. race conditions and partial data that may arise from simultaneous operations This prevents updates from occurring. A valid delivery will not be possible if any of the verifications fail. Closing is not being created; shipment record (4) is in delivered status 20 not transferred, vehicle registration (5) available again depending on delivery closing not being made and delivery code registration (6) successfully used It is not being passed on. However, regarding the failed verification attempt... number of attempts and / or security information in the delivery code record (6) or with it It is possible to keep or update an associated security record. The invention's 25 The working principles described above can be implemented as a system, or... also as a computer application method run by the server (1) It can be accomplished. DESCRIPTION OF THE FIGURES Figure 1: Simultaneous load assignment and delivery management system, the subject of the invention; server 30 (1), database (2), multiple driver terminals (3), shipment record (4), vehicle record (5), delivery code registration (6), consignee terminal (7) and receiver terminal (8) 6 Schematic of the overall system architecture showing data communication and relationship between them. It is the appearance. Figure 2: Simultaneous dispatch from multiple driver terminals (3) for the same dispatch or acceptance requests sent around the same time to the server (1) and database (2) controlled processing via; shipment record with (4) write lock 5 The system is locked and its current status is checked; the post is deemed suitable for assignment. If so, write lock the relevant vehicle registration (5) within the same database operation. by locking and checking availability; post record (4) only one driver and vehicle registration (5) associated with and other simultaneous acceptance 10 without creating a new assignment based on the current registration status of their requests Schematic of the synchronous load assignment workflow that enables its completion. It is the appearance. Figure 3: During the delivery phase of the transportation process, the driver assigned to the relevant shipment. Upon receiving a delivery code verification request transmitted via the driver terminal (3) initiation of the database transaction; shipment registration (4) and delivery 15 (6) the code record should be locked with write locks within the scope of the said transaction; Checking the delivery eligibility status of the shipment and the driver's authorization via locked records. and verification of delivery code validity; delivery also in an application. Check the location condition and, if verification is successful, the delivery code will be sent. record (6) used status, shipment record (4) delivered status and 20 delivery by restoring the vehicle registration associated with the shipment (5) to a new status. ensuring the closing is performed within the same database transaction integrity. This is a schematic view of the delivery closing process flow. It is a preferred method. In practice, after the delivery process is completed, to the receiving terminal (8) An informational notification may be sent. 25 REFERENCE NUMBERS 1. Server 2. Database 3. Driver terminal 4. Shipment record 30 5. Vehicle registration 6. Delivery code registration 7 7. Shipper terminal 8. Receiving terminal Detailed Description of the Invention The invention is based on the simultaneous or (3) of multiple driver terminals relating to the same dispatch. 5 Acceptance requests submitted around the same time will be processed in a controlled manner. The post should only be associated with one driver and one vehicle, preventing the same vehicle from being used simultaneously. to prevent the allocation of the process to multiple shipments and at the end of the transportation process, delivery is made in a controlled manner and data consistency is maintained. a computer-implemented synchronous load assignment that enables its completion and It relates to the delivery management system and method. 10 The overall system architecture of the invention is shown in Figure 1, and the system is fundamentally based on... at least one server (1), at least one that is in communication with the said server (1). database (2), multiple driver terminals (3), at least one load owner terminal (7) and includes at least one receiving terminal (8). In the database (2), transport operations at least one shipment record (4), at least one vehicle record (5) and 15 used in its management At least one delivery code record used to verify the delivery process (6) is being held. The consignee terminal (7) lists the origin, destination, and cargo of the shipment to be transported. The quantity, cargo characteristics and similar information are transmitted to the server (1) and the shipment record is created. (4) is the electronic terminal that enables the creation of the shipment. The receiving terminal (8) is the 20 It is an electronic terminal through which information regarding the delivery process can be transmitted to the recipient. The aforementioned notification made to the receiving terminal (8) is the delivery process a preferred practice, not mandatory for completion It is of this nature. Confirmation of the delivery process is sent to the relevant shipment as described below. This is done by the assigned driver via the driver terminal (3). 25 Driver terminal (3) connects the driver to the server (1) to perform the transport operation. It is an electronic terminal that enables data communication. Driver terminal (3), load The owner terminal (7) and the receiving terminal (8) can communicate data with the server (1). in the form of mobile terminals, computer terminals, or other types of electronic terminals This is feasible. The technical working principle of the invention is based on the fact that the terminals in question have a specific 30 depending on whether it is implemented on a hardware or user interface platform It is not. 8 Shipment record (4), the shipment to be transported and the transport of the said shipment It includes data on the current status of the process. Vehicle registration (5), transport the vehicle that can be used in the process and the vehicle's availability and / or usage status It includes the data related to the delivery code record (6). Creating and validating the verification information to be used in this stage. 5 monitoring use cases and failures in preferred applications. data for storing security information regarding verification attempts It includes. Managing simultaneous admission requests One of the basic technical working principles of the invention is 10 relating to the same posting record (4). Acceptance requests transmitted from multiple driver terminals (3), shipment and vehicle The records are processed while maintaining data consistency. This process flow is shown in Figure 2. It is shown schematically. After a shipment is presented to drivers for transport, multiple drivers terminal (3) transmitting the acceptance request for the same shipment to the server (1) 15 It is possible. These admission requests may be submitted simultaneously or in close succession. If the requests reach the server (1) at times independently of each other If processed, multiple transactions are not yet assigned to the same shipment record (4) the risk of it seeing it as eligible and creating multiple assignments for the same post It can occur. 20 In addition, acceptance processes for different shipments are carried out simultaneously. (5) during the execution of the same vehicle registration by more than one transaction If available, the same vehicle can be assigned to multiple shipments. There is also a risk of being lost. Within the scope of the invention, both the shipment record (4) and Controlled access applied to the relevant vehicle registration (5) this concurrency 25 It enables the prevention of problems at the database level. A database operation upon receipt of an acceptance request to the server (1) (transaction) is initiated and the shipment record associated with the acceptance request (4), database (2) with a write lock that prevents simultaneous conflicting changes. is locked. In a preferred application, this write lock applies to the relevant data. It is a row-level write lock applied to the base record and database It is protected until the process is complete. 9 After the shipment record (4) is locked, the server (1) locks the shipment record (4) It checks the current status of the shipment via [website address]. A new shipment has been sent. If the driver is not found to be eligible for assignment, the relevant acceptance request will be rejected. The process is concluded without creating a new driver or vehicle assignment. If the submission is found to be eligible for assignment, the server (1) will accept the request. check whether the transmitting driver is authorized to perform the operation in question. In the preferred application, this control is performed by the driver in the system. whether or not they have the appropriate driver role and active user status It includes verification. If the driver meets the necessary conditions, the vehicle registration associated with the relevant driver (5), 10 a system that prevents simultaneous conflicting changes within the same database operation It is locked with a write lock. The availability status of the vehicle registration (5) is the subject of This is checked via the current vehicle registration record, which is under write lock. In the preferred application, the vehicle is active and available, associated with the relevant driver. Its presence is confirmed. 15 In this way, the availability of the vehicle registration (5) is only checked beforehand and then unlocked. No updates are being made; the vehicle's availability is recorded as locked. is being evaluated and the write lock related data on the vehicle registration in question. The base is protected until the process is completed. Vehicle registration (5) required If the conditions are not met, the application will be rejected without any appointment being made. is being finalized. The shipment record (4) is suitable for assignment and the vehicle record (5) is available. If available, the shipment record (4), the relevant driver and vehicle record (5) It is associated with this process. Within this process, the status of the shipment record (4) is assigned. It is being switched from open status to assigned status and the relevant vehicle registration (5) is available 25 It is being transferred from a state to a state reserved for transportation. The shipment record (4) is associated with the relevant driver and vehicle record (5), shipment Changing the status of the registration (4), changing the availability status of the vehicle registration (5) the change and the status record regarding the said change in status creation, write locks on the shipment record (4) and vehicle record (5) 30 within the same database transaction integrity in which it is preserved is being carried out. The database operation in question involves locking the post record with a (4) write lock. and checking the current status, verifying driver's license, relevant (5) locking the vehicle registration with write lock in the same process and the locked vehicle Checking availability via registration, shipment-driver-vehicle the creation of the relationship, updating the post record (4), vehicle registration (5) 5 This includes updating and recording the relevant status change. If all of these processes are successfully completed, the database The transaction is being committed; the data within the scope of the transaction If any of the updates fail to complete successfully, the data The changes made within the scope of the base operation are being rolled back. Thus, 10 For example, even though the post appears to be assigned, the relevant vehicle is still... even though it appears available or the vehicle has been removed from the availability status, the shipment... Partial and contradictory data, such as the inability to establish a driver-vehicle relationship. These situations are prevented from occurring. In case of simultaneous acceptance, a single assignment will be created. 15 Acceptance from two or more driver terminals (3) relating to the same dispatch record (4). requests are transmitted to the server at the same time or close to each other (1) In this case, each of the requests in question accesses the same post record (4) can request. Due to the write lock applied on the post record (4), One of the acceptance requests is to perform a valid transaction on the shipment record (4) 20 other acceptance request or requests simultaneously and contradictorily on the same record The ability to make changes is prevented. Within the scope of the initial valid acceptance request. A relationship is established between the shipment record (4) and the driver and vehicle record (5), The post is changed from open to assigned status to assigned status and vehicle registration (5) It is being changed from a state of availability to a state reserved for transport. The 25 in question... The changes are persisted within the same database operation integrity. When the other pending acceptance request can access the shipment record (4), the shipment is updated. The situation is being re-evaluated. The first valid action was after assigning the shipment. The post is no longer eligible for assignment, so the pending process is halted. a new 30 before proceeding to the locking stage (5) of the record The process is concluded without creating an appointment. This ranking means that appointments are no longer necessary. Unnecessary lock on the tool source for an impossible delivery. It prevents its creation. 11 Simultaneous acceptance requests relating to the same shipment are written on the shipment record (4) It is serialized via the lock. Thus, after the first valid transaction is completed Then, other processes will view the current status of the locked record and make a second valid assignment. It is unable to create. Simultaneous transactions relating to different shipments using the same vehicle registration (5) 5 If requested, the process will be completed after their own shipment checks, and then the vehicle registration will be done jointly. (5) is in the queue. The first action to lock the vehicle registration is the vehicle being made available. It removes the status; the next step is to unlock the vehicle's current activity and It reassesses availability and if the vehicle is no longer available, a second attempt will be made. It does not create an assignment. 10 This allows multiple valid assignments for the same post, using the same tool for different posts. simultaneous second allocation, unnecessary vehicle locks and dispatch vehicle records between Conflicting data situations are prevented. The technical scope of the invention relates to a specific database management system, specific software. to its library, to a specific ORM structure, to a specific locking instruction, or to a specific 15 It is not related to an error code. Post status managed by the server. Within the scope of the invention, the stage of processing the shipment is in, the shipment record (4) by the server (1) through the current status information kept within is determined. 20 A request transmitted by the driver terminal (3) alone sends the data. It does not change the situation at the base. The request in question is submitted by the server (1) current status of the shipment record (4) and the party performing the transaction It is evaluated taking into account the authority granted. Acceptance, change of status or delivery transmitted by driver terminal (3) 25 If the request is not compatible with the current status of the shipment record (4), the word the subject of the request is valid on the database (2) by the server (1) It is not being converted into a change. This structure allows the current status of the shipment to be known only on the client terminal. This prevents changes based on interface or device data and 30 The current status of the shipment is managed via the server (1) and the database (2). 12 Managing simultaneous acceptance and cancellation processes. In one application of the invention, a request for acceptance from a driver terminal (3) for the shipment Attempting to cancel a message while it's being sent on the same page. It is possible. In this case, acceptance and 5 are made possible thanks to the write lock applied to the post record (4). Cancellation processes yielding independent and contradictory results on the same post. It is prevented from being created. Status valid on the shipment record (4) The status of the shipment is changed as a result of the first transaction that completes the change; The other process involves accessing the shipment record to see the current status of the shipment. It is being re-evaluated based on this. 10 Thus, in the database (2) there is both a cancelled and a valid version of the same post. conflicting situations arise showing that the driver and the vehicle are assigned to each other. This is being prevented. Generating and storing the delivery code. The transportation process must be completed by verifying that the shipment has been delivered in an authorized manner during the delivery phase (15). For verification purposes, at least one delivery code record associated with the shipment record (4) (6) is being created. In a preferred application, the delivery code is a one-time verification code. The delivery code registration (6) is as follows: the validity period of the said code, usage information regarding the status and failed verification attempts, one or more of 20 It can include more than that. In a preferred application, the delivery code is a cryptographically secure random code. It is generated using a number generator and, for example, as a six-digit number. can be produced. Directly in the open delivery code database (2) not stored; code, identifying information relating to the shipment and server (1) side 25 a one-way cryptographic verification value using a secretly held value It is converted and associated with the delivery code record (6). In the implementation, the validation value in question is a function based on HMAC-SHA-256. It can be obtained using... The verification value calculated from the code transmitted during verification is recorded as 30. The validation value is being compared; in a preferred application, this comparison is made. 13 A fixed-time system to reduce information leakage based on timing differences. This is achieved through a specific method. The technical working principle of the invention is defined by a particular code. It is not dependent on length or a specific cryptographic algorithm; six-digit code And HMAC-SHA-256 are preferred implementation examples. Verification of delivery process 5 The process flow for closing the delivery of the invention is shown in Figure 3. Transportation during the delivery phase of the process, the driver assigned to the relevant shipment Verification of the delivery code associated with the shipment via the driver terminal (3) A request is sent to the server (1). Upon receipt of the delivery code verification request by the server (1), a data 10 The transaction is initiated and the shipment record (4) and delivery code are used. record (6), which prevents simultaneous conflicting changes within the scope of the transaction in question. It is locked with write locks. This allows for multiple deliveries related to the same shipment or delivery code. verification request shipment status or delivery code usage status 15 This prevents them from changing things independently and ensures verification. possible incidents that may occur between the delivery closing processes following the steps Racing situations are being reduced. After the relevant records are locked, the server (1) can access the locked post record (4). It checks the current status of the shipment. Preferred application: 20 The delivery is only considered complete when the shipment's delivery process is finished. permission is granted if it is in a predetermined situation where it can be carried out. is provided. Server (1) also records the relevant shipment record of the driver who made the delivery request (4) It checks if there is a driver associated with it. Thus, the shipment is 25 Valid delivery of another unrelated driver terminal (3) Completion is prevented. In an application, the delivery process can also have a configurable delivery location condition. is connected to the current geographical location of the shipment obtained from the driver terminal (3). The distance between the registered delivery coordinates is calculated by the server (1) 30 and that distance has a predetermined or configurable maximum The distance threshold must not be exceeded. In one implementation, the threshold was set at 250 meters. 14 It can be determined and modified on the server side; the invention is at a fixed distance. It is not limited by its value. Checking the required shipment status and driver authorization conditions, and the delivery location. If the relevant location condition is met in the implementations where it is applied, it will be locked. Validity of delivery code checked via delivery code registration (6) 5 is being done. The code has expired, has been used previously, or lacks permission. the number of failed verification attempts given has been exceeded or transmitted If the verification information does not match the registered verification information, a valid Delivery closing is not being performed. 10 In this case, the shipment record (4) is not changed to delivered status, vehicle registration (5) is not made available again depending on delivery closing and Delivery code registration (6) is not successfully activated. However, in a preferred application, a failed validation attempt number of attempts and / or security information delivery code record (6) or 15 This can be recorded or updated in an associated security log. Recording or updating this security information requires a valid agreement. This does not mean that the delivery closing has been completed. Controlled closure of the delivery If all verification requirements are successfully met, the same data will be available on 20 Posts previously locked with write locks as part of the base operation Regarding delivery closure via registration (4) and delivery code registration (6) Updates are being implemented. Verification and delivery closure update processes are in the same database. Thanks to the process being carried out within the same controlled access scope, 25 simultaneously delivery verification requests include verification and update processes. This prevents the occurrence of a potential race gap. Successful. As a result of verification, the delivery code record (6) is set to used status. The shipment record (4) is brought to the delivered status, the vehicle record associated with the shipment (5) is made available again and the status of delivery of the shipment is recorded 30 A record is being created. Updates regarding the closure of this delivery will be made the same way. The database operation is performed within an integrity framework, and the operations are successfully completed. Once completed, the database transaction is committed. The preferred option, but not mandatory for delivery closure to occur. In one application, after the delivery is completed, to the receiving terminal (8) An informational notification may be sent. This notification will be delivered on 5th. This is not a confirmation determining the validity of the transaction; it is for informational purposes only. Thus, even though the delivery code appears to have been used, the shipment will still be delivered. remaining undelivered or, despite the shipment being delivered, the relevant such as the vehicle's availability not being updated due to delivery closure. This prevents the occurrence of partial and inconsistent data situations. 10 The shipment has been delivered once the delivery code has been used. the transition to the same state is carried out within the same controlled process, the same A second valid delivery closing will be issued if the delivery code is resent. It also prevents its creation. Delivery code record (6) is used. since it is kept and the shipment record (4) is now required before delivery 15 A resubmitted verification request because it was not found, a new valid delivery It is unable to create a closing order. A cancellation or delivery transaction can occur simultaneously with the delivery transaction on the same shipment record (4). If a different status change procedure is desired, the word The subject transactions are serialized via the write lock applied to the shipment record (4) 20 is brought in. After the first transaction that completes the current status change, the others The process will be re-evaluated based on the current status of the shipment record (4). The process is concluded without creating a contradictory situation. Implementation as a method The technical operating principles explained above through the system elements apply to server 25. (1) also as computer application method steps carried out by It can be accomplished. Accordingly, the simultaneous load assignment method involves a process where, upon receipt of an acceptance request, a Initiating the database operation, locking the post record with (4) write lock and checking the current status via the locked shipment record, acceptance request 30 Verification of the authority of the transmitting driver, the relevant vehicle registration (5) in the same database The process involves locking the device with a write lock and checking availability via the locked vehicle registration. 16 Verification of the status, shipment record (4) with the relevant driver and vehicle record (5) linking, updating shipment and vehicle statuses, and related statuses. the record creation processes within the same database operation current registration status of completion and other simultaneous admission requests It includes the steps to finalize it. 5 The method used during the delivery phase of the transportation process is the request for delivery code verification. upon receipt, a database operation is initiated, the shipment record (4) and Locking the delivery code record (6) with write locks, through locked records shipment status, driver authorization, and delivery code validity Verification, in implementations where delivery location control is applied, also 10 Verification of delivery location conditions and delivery upon successful verification. Code registration (6), shipment registration (4) and vehicle registration (5) are all processed in the same database. It includes the steps to update it in its entirety. A valid delivery closure in case of verification failure. not being created; however, failure in preferred practices 15 Security information and / or number of verification attempts It can be recorded. Technical results provided by the invention Thanks to the structure described above, there are multiple entries for the same post record (4) Simultaneous or near-simultaneous acceptance from the driver terminal (3) 20 Requests are processed in a controlled manner at the server (1) and database (2) levels. and only one acceptance request can be converted into a valid driver and vehicle assignment. is provided. Checking the current status of the post record by locking it with (4) write lock and the related vehicle registration (5) within the same database operation with write lock 25 By locking the account and verifying its availability through the locked record, both associating the same post with multiple drivers or vehicles, and the same The vehicle has multiple simultaneous operations on different shipments as a result of Allocation to the post is being prevented. The shipment record (4), vehicle record (5) and related status information are all in the same database 30 The process should be updated in its entirety, and in case of process failure, the relevant information should be provided. Thanks to the reversal of the changes, partial assignment, dual vehicle allocation and conflicting situations were avoided. 17 Shipment-vehicle statuses are generated at the database and server level. is being prevented. During the delivery phase of the transportation process, the shipment status and driver's authorization are checked. Validity of delivery code and delivery location in the transactions where it is applied. Verification in a controlled manner, provided that; then the delivery code registration 5 (6), shipment record (4) and vehicle record (5) are all in the same database process integrity. delivery closing thanks to its consistent completion within the scope race conditions and partial data resulting from concurrent operations The updates are carried out in a controlled manner. Thus, the invention enables simultaneous 10 in the acceptance and delivery phases of the freight transportation process. data inconsistencies and source conflicts that may arise from the processes System and computer systems that enable prevention at the base and server level. an integrated chain of technical processes that can be implemented as a practical method It reveals.
Claims
18 REQUESTS 1. The invention involves multiple drivers handling the same shipment in freight transportation processes. Simultaneous load that enables the management of acceptance requests transmitted from terminal (3) assignment and delivery management system; at least one server (1), the said server (1) At least one database in communication with (2), more than one driver 5 terminal (3), at least one shipment record (4) kept in the database (2) and at least one vehicle registration (5) includes; its feature is; server (1); Simultaneous from multiple driver terminals (3) relating to the same shipment record (4) or for each of the acceptance requests submitted in close succession, one data within the scope of the transaction base, the shipment record (4) is simultaneous contradictory 10 by locking the post record with a write lock that prevents changes (4) current will check the situation; If the posting record (4) is in a suitable condition for assignment, the request for acceptance will verify the authority of the transmitting driver; vehicle registration associated with the relevant driver (5) simultaneously within the same database operation 15 Locked vehicle registration (5) by locking with a write lock that prevents conflicting changes It will check the current availability of the vehicle via; the shipment record (4) is suitable for assignment and the vehicle record (5) is available If found, the shipment record (4) with the relevant driver and vehicle record (5) 20 The association of the post record (4) from the state open for assignment to the state assigned. transfer of vehicle registration (5) from available status to state reserved for transport operation the processes of passing through and creating the relevant status record, shipment record (4) and The write locks on the vehicle registration (5) are preserved and the same database operation is performed. will carry out all of these processes in their entirety; all of the said processes will be successfully completed. If completed, the data changes will be made permanent, and transactions will take 25 days. If either of them cannot be completed, within the scope of the same database operation. It will revert the data changes; and other simultaneous acceptance requests relating to the same post record (4), previous valid After the transaction is completed, the current status of the shipment record (4) will be updated. by checking, if the post is no longer eligible for assignment, a new 30 It is configured to complete the process without creating a driver or vehicle assignment. It is the fact that. 19 2. According to Request 1, the system has the following features: shipment registration (4) and vehicle registration (5) The rows where the applied write locks are applied to the relevant database records having write locks on the database at the level and those locks relating to the data The base must be protected until the process is complete.
3. The system is according to Request 1 or 2, and its feature is; the same vehicle registration (5) different 5 If the vehicle is to be used in simultaneous acceptance procedures for shipments, Checking the availability of the record (5) under write lock and the first after the vehicle registration (5) is removed from the available status by the valid transaction the other process is to re-register the vehicle registration (5) current availability status. will evaluate and if the vehicle is no longer available, the vehicle in question will be 10 It is configured in such a way that it will not create a new assignment using it.
4. It is a system according to claim 1, and its characteristic is; the process of assigning and transporting the shipment. the current status is determined by the server (1) and not by the driver terminal (3). Based on the current status of the shipment record (4) in the database (2) determination and status change requests transmitted from the driver terminal (3) 15 The topic is structured in such a way that it will be re-verified based on the current situation. It is the fact that.
5. According to claim 1, the system has the feature of being a driver on the same post record (4). a request for acceptance and a request for cancellation of the shipment transmitted from terminal (3) If processed simultaneously, the shipment record of the transactions in question (4) 20 It will be serialized via the write lock on it and the current status After the first transaction completes its change, the shipment record of the other transaction (4) The matter will be concluded based on the current situation, without creating a contradictory situation. It is structured in this way.
6. The system is defined in accordance with Claim 1, and its characteristic is that the transportation process takes place at the delivery stage of 25. The shipment record (4) must contain at least one delivery code record (6) associated with the server (1); a database operation upon receipt of a delivery code verification request will start; shipment record (4) and delivery code record (6), the said database process with write locks that prevent simultaneous conflicting changes within 30 will lock; and delivery process of shipment record (4) via locked records being in a predetermined situation where it can be carried out, delivery The driver who performed the operation is associated with the relevant shipment record (4) together verify that the delivery code registration (6) is valid. It is structured in this way. 5 7. The system, according to claim 6, has the characteristic of; the delivery process also includes the driver. delivery associated with the shipment with the current geographical location obtained from the terminal (3) the distance between the location is determined by the server (1) and the determined a predetermined or configurable maximum distance threshold It is structured in such a way that it will be carried out depending on whether it exceeds 10.
8. The system is based on claim 6 or 7, and its characteristic is that all necessary verifications have been completed. If successful, the delivery code registration (6) will be set to used status. (4) making the shipment record delivered, vehicle associated with the shipment making the record (5) available again and the status record of the delivery the creation processes of the shipment record (4) and delivery code record (6) 15 the integrity of the same database process where it was locked and the verifications were performed any of the verifications that will be carried out within it will fail in this case the shipment record (4) is changed to delivered status, vehicle record (5) Re-availability depending on delivery closing and delivery code The successful use of the record (6) will be prevented; failure 20 the number of verification attempts and / or security information related to the verification attempt in the delivery code record (6) or in a security record associated with it configured to allow saving or updating It is the fact that.
9. The system, according to request 8, has the following feature: delivery code 25 after successful verification. record (6) is used and shipment record (4) is delivered by retaining it, a second delivery code will be sent if the same delivery code is retransmitted. configured to prevent the creation of a valid delivery closure It is the fact that.
10. The invention relates to multiple drivers handling the same shipment in freight transportation processes. 30 Acceptance requests transmitted from terminal (3) to a server (1) and the said server (1) enables management through a database (2) that is in communication with (1). 21 It is a computer-based synchronous load assignment and delivery management method. feature; initiating a database operation upon receipt of an admission request; Simultaneous conflicting changes to the post record associated with the acceptance request (4) locking with a write lock that prevents and locked post record (4) 5 Checking the current status of the shipment; If the posting record (4) is in a suitable condition for assignment, the request for acceptance Verification of the transmitting driver's authority; vehicle registration associated with the relevant driver (5) simultaneously within the same database operation Locking with a write lock that prevents conflicting changes and locked vehicle registration 10 Checking the current availability of the vehicle via (5); the shipment record (4) is suitable for assignment and the vehicle record (5) is available If available, the shipment record (4) with the relevant driver and vehicle record (5) the association of the post record (4) from the state open to assignment to the state assigned transfer, vehicle registration (5) from available status to allocated status for transport operation 15 The processes of passing through and creating the relevant status record, shipment record (4) and The write locks on the vehicle registration (5) are preserved and the same database operation is performed. to be carried out in its entirety; If all of these processes are successfully completed, the data making the changes permanent, any of the transactions 20 If it cannot be completed, the data within the same database operation reversing the changes; and other simultaneous acceptance requests relating to the same post record (4), previous valid After the transaction is completed, the current status of the shipment record (4) is updated again. After checking, if the post is no longer eligible for assignment, a new 25 steps to finalize without creating a driver or vehicle assignment It includes.
11. The method according to claim 10, its feature is; to the shipment record (4) and vehicle record (5) The write locks applied are recorded at the row level in the relevant database records. database write locks are implemented and these locks are applied to the relevant data. 30 The base must be protected until the process is complete. 22 12. The method is according to claim 10 or 11, and its characteristic is that the same vehicle registration is (5) different If the vehicle is to be used in simultaneous acceptance procedures for shipments Checking the availability of the record (5) under write lock, the first valid the process of removing the vehicle registration from the (5) available status and other process By reassessing the current status of the vehicle registration (5), the vehicle is now available. The point is that if the situation is not like that, a new assignment cannot be created with the vehicle in question.
13. The method according to claim 10, its characteristic is that the transportation process takes place during the delivery phase. Creating a delivery code record (6) associated with the shipment record (4); a delivery Initiating a database operation upon receipt of a code validation request; shipment record (4) and delivery code record (6) within the scope of the transaction in question 10 locking with write locks that prevent simultaneous conflicting changes; and locked (4) delivery process can be carried out via the records of the shipment registration. being in a predetermined situation, carrying out the delivery process the driver must be the driver assigned to the relevant shipment and the delivery code must be recorded (6) It includes steps to verify its validity together. 15 14. The method according to claim 13, its characteristic is that the delivery process also involves the driver. delivery associated with the shipment with the current geographical location obtained from the terminal (3) The distance between the location is determined by the server (1) and the determined a predetermined or configurable maximum distance threshold It includes the step of verifying that it has not exceeded 20.
15. Method according to claim 13 or 14, characterized by the necessary validations. If all are successful, the delivery code registration (6) is in the used state. bringing, making the shipment record (4) delivered status, with the shipment Status of reactivation of the associated vehicle registration (5) and delivery. 25 creation of the registration, shipment registration (4) and delivery code registration (6) the integrity of the same database process where it was locked and the verifications were performed being performed within; any of the verifications failing If the shipment record (4) is not brought to the delivered status, the vehicle record (5) not being re-available depending on delivery closure and delivery The code registration (6) is not successfully used; failed 30 Delivery of verification attempt number and / or security information can be recorded in the code record (6) or in a related security record or can be updated; and after successful verification the delivery code record (6) used and the shipment record (4) kept in delivered condition 23 If the same delivery code is retransmitted in this way, a second valid delivery will be issued. This includes steps to prevent the closure from being established.
16. The system is based on either of the requirements 6-9, and its characteristic is; the explicit delivery code. (2) not directly stored in the database, delivery code and shipment Using identifying information and a value kept secret on the server (1) side, a single 5 Generation of a directional cryptographic verification value and delivery code registration (6) is associated with; calculated from the code transmitted in delivery code verification. Comparison of the verification value with the registered verification value and the said the comparison aims to reduce information leakage based on timing differences 10 This can be done using a fixed-time comparison method. It is structured.
17. A method according to either of claims 13-15, characterized by: explicit delivery. not directly storing the code in the database (2); delivery code with shipment using the related identifying information and a value kept secret on the server (1) side Generating a one-way cryptographic verification value and recording the delivery code (6) 15 association with; validation calculated from the code transmitted during validation. Comparison of the value with the registered verification value and the said the comparison aims to reduce information leakage based on timing differences the steps to be carried out using a fixed-time comparison method It includes. 20 30