The present disclosure relates, in general, to communication system and more particularly, but not exclusively to a logistics transportation communication system and method thereof.
BACKGROUND
The logistics industry is an important part of the social economic system. The existing traditional logistics transportation model is unable to meet requirements of the present social economic systems due to high operating costs, low efficiency, severe fragmentation, and insufficient information. Some of the problems such as rational use and insufficient multi-transportability have hindered the development of the logistics industry. The most prominent problem is that the current operating scope of logistics companies generally involves only dedicated lines or regions, as the logistics companies are relatively independent of each other. According to the traditional existing logistics transportation, the circulation of goods in the society mainly depends on one-to-one relationship between trader and transporter, and transporter and vehicle owner. Therefore, the existing logistics transportation system does not use full potential of advanced connectivity for end-to-end delivery, internet services, advancement of technology, and not meeting the need of present social economic system.
Thus, there arises a need for an improved logistics transportation communication system for enabling all users of the logistics industry such as trader, transporter, broker, vehicle owner, vehicle driver, and support service devices to communicate and coordinate to provide end-to-end solution from booking to delivery of the goods in an efficient manner.
SUMMARY
Embodiments of the present disclosure relate to a logistics transportation system that enables real time interactions between one or more trader devices, one or more transporter devices, one or more broker devices, one or more vehicle owner devices, one or more vehicle driver devices, and one or more support service devices using an logistics transportation server to provide end-to-end solution from booking to delivery of the goods in an efficient manner.
Another aspect of the present disclosure relate to a method enabled by the logistics transportation system for establishing real time interactions between one or more trader devices, one or more transporter devices, one or more broker devices, one or more vehicle owner devices, one or more vehicle driver devices, and one or more support service devices

using an logistics transportation server and to provide end-to-end solution from booking to delivery of the goods in an efficient manner.
The system, and associated method of the present disclosure overcome one or more of the shortcomings of the prior art. Additional features and advantages may be realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of device or system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which:
Figure 1 illustrates an exemplary architecture of a logistics transportation system in accordance with embodiments of the present disclosure;
Figure 2 illustrates a block diagram illustrating the logistics transportation server of Figure 1 in accordance with embodiments of the present disclosure;
Figure 3 illustrates exemplary steps of a method performed by one or more devices included in the logistics transportation system in accordance with embodiments of the present disclosure;

Figure 4 is a flowchart illustrating a method enabled by the logistics transportation system from assigning the driver to the trip till delivery of goods in accordance with some embodiments of the present disclosure;
Figure 5 is a flowchart illustrating a method enabled by the logistics transportation system to detect one or more events during the driver's trip in accordance with some embodiments of the present disclosure; and
Figure 6 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
The figures depict embodiments of the disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the disclosure described herein.
DETAILED DESCRIPTION
Figure 1 illustrates an exemplary architecture of a logistics transportation system in accordance
with embodiments of the present disclosure.
As illustrated in Figure 1, the exemplary architecture of a logistics transportation system 100 comprises a plurality of components such as a logistics transportation server 102, application hosted at each of one or more trader devices 104-1, 104-2, .... 104-N (collectively referred to as trader devices 104), application hosted at each of one or more transporter devices 106-1, 106-2, .... 106-N (collectively referred to as transporter devices 106), application hosted at each of one or more broker devices 108-1, 108-2, .... 108-N (collectively referred to as broker devices 108), application hosted at each one or more vehicle owner devices 110-1, 110-2, .... 110-N (collectively referred to as vehicle owner devices 110), application hosted at each of one or more vehicle driver devices 112-1, 112-2, .... 112-N (collectively referred to as vehicle driver devices 112), application hosted at each of one or more support service devices 114-1, 114-2, .... 114-N (collectively referred to as support service devices 114), and a data repository 120. The logistics transportation server 102, the one or more trader devices 104, the one or more transporter devices 106, the one or more broker devices 108, the one or more vehicle owner devices 110, the one or more vehicle driver devices 112, the one or more support service

devices 114, and the data repository 120 are communicatively coupled via a network 130. The network 130 may be a LAN (local area network), WAN (wide area network), wireless network, point-to-point network, or another configuration. One of the most common types of network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network for communication between database client and database server. Other common Internet protocols used for such communication include HTTPS, FTP, AFS, and WAP and using secure communication protocols etc.
The logistics transportation server 102 may be adapted to receive, determine, record and /or transmit information for any number of users such as trader (either consignor or consignee), transporter, vehicle owner, broker, vehicle driver, and support services. The logistics transportation server 102 may store such information in, for example, the data repository 120. The logistics transportation server 102 comprises a processor 130, a memory 132, a user registration and management module 134, a real time payment management module 136, and a search module 138. The user registration and management module 134 is configured to register one or more devices associated with each user (e.g., trader, transporter, vehicle owner, broker, vehicle driver, and support services) with the logistics transportation server 102 by verifying one or more input parameters provided by the user. For example, the input parameters include, but not limited to identity information of individual and company, unique identity number associated with the user such as UTDAI number, GST number, license number, pan number and so on.
The search module 138 is configured to receive a request comprising one or more inputs from the user and retrieve a list of other users based on the request received. In one example, if the user is the trader, the application hosted in the trader device 104-N may receive one or more inputs such as a pickup location information, a drop location information, quantity of goods, load type, nature of goods, vehicle type, contract type, and so on and provide to the search module 138. In an exemplary embodiment, the application hosted in the trader device 104-N is configured to input at least one of location of transporter, the pickup location information, and the drop location information by drawing a custom shape (or) pattern on the trader device 104-N. The search module 138 is configured to retrieve the custom shape (or) pattern received from the trader device 104-N, estimate one or more boundary points on the geographical map corresponding to the custom pattern, and retrieve the list of transporters based on the one or more boundary points estimated. In one embodiment, the search module 138 is configured to

consider the search pattern of the trader and past search history of the trader along with the one or more inputs to provide the list of transporters. In other embodiment, the search module 138 is also configured to auto-populate one or more fields to be searched based on the historical search information associated with the user. The real time payment management module 136 is configured to receive payment made by the user and split the received payment in real time to one or more recipients involved.
Each of the one or more trader devices 104, the one or more transporter devices 106, the one or more broker devices 108, the one or more vehicle owner devices 110, the one or more vehicle driver devices 112, and one or more support service devices 114 may be a mobile device or a computing device including the functionality for communicating over the network 130. For example, the mobile device can be a conventional web-enabled personal computer in the home, mobile computer (laptop, notebook or subnotebook), Smart Phone (iOS, Android), personal digital assistant, wireless electronic mail device, tablet computer or other device capable of communicating both ways over the Internet or other appropriate communications network. The mobile device may comprise an integrated software application with a user interface that enables interaction with the logistics transportation server 102. In one embodiment, the mobile device is configured to download and install the software application using at least one of QR code, and bar code associated with the software application.
The one or more support service devices 114 are devices registered with logistics transportation server 102. Each of the one or more support service devices 114 includes an application provided by the logistics transportation server 102 to enable interaction with one or more users (e.g., trader, transporter, vehicle owner, broker, and vehicle driver). For example, the support services devices 114 are devices associated with support services such as hotel, petrol shop, restaurant, vehicle service center, insurance companies, repair shops, petrol pumps, tyre shops and so on.
Each vehicle associated with the one of transporter device 106-N, broker device 108-N, and vehicle owner device 110-N includes one or more sensors 190 that are mounted within the vehicle or incorporated in the wristband worn by the user such as the driver. The one or more sensors 190 are configured to monitor one or more parameters of the vehicle and/or driver and continuously (or) periodically send status of the one or more parameters to the logistics transportation server 102. In an example, the parameter include such as location of vehicle, fuel

tank status, status of vehicle, data from pressure sensor, weight, speed sensor, accelerometer sensor, gyroscope sensor, heart rate sensor, temperature sensor, camera sensor and so on.
The logistics transportation system 100 enables real time interactions between one or more trader devices 104, one or more transporter devices 106, one or more broker devices 108, one or more vehicle owner devices 110, one or more vehicle driver devices 112, and one or more support services 114 using the logistics transportation server 102 to provide end-to-end solution from booking to delivery of the goods in an efficient manner. The logistics transportation system 100 also monitors health status of vehicle and driver during the journey for delivery of goods and generate alerts or notifications in case of rerouting the journey and any deviations detected in the health status. The logistics transportation system 100 also enables real time payments to service providers involved in the goods delivery without any delay.
Figure 2 shows a block diagram illustrating the logistics transportation server 102 of Figure 1 in accordance with some embodiments of the present disclosure.
In an implementation, the logistics transportation server 102 may include the processor 130, the memory 132, and an I/O interface 202. The I/O interface 202 is coupled with the processor 130 and an I/O device (not shown). The I/O device is configured to receive inputs via the I/O interface 202 and transmit outputs for displaying in the I/O device via the I/O interface 202. The logistics transportation server 102 further comprises data 204 and modules 206. In one implementation, the data 204 and the modules 206 may be stored within the memory 132. In one example, the data 204 may include user profile 208, posts 212, order and transactions 214, agreements and responses 216 and other data. The user profile 206 includes information about unique login credentials such as unique login name and password of the user. The posts 212 includes one or more previous search pattern of the user, and past search history of the user. The order and transactions 214 includes information about previous orders and transactions made by the user. The agreements and responses 216 includes information about previous agreements including quotation related to the user and response such as confirmation on quotation included in agreements.
In one embodiment, the data 204 may be stored in the memory 132 in the form of various data structures. Additionally, the aforementioned data 204 can be organized using data models. The

other data may be also referred to as reference repository for storing recommended implementation approaches as reference data. The other data may also include temporary data and temporary files, generated by the other modules 260 for performing the various functions of the logistics transportation server 102.
The modules 206 may include, for example, the user registration and management module 134, the real time payment management module 136, the search module 138, a real time connection establishment module 232, a document generation module 234, a route optimization module 236, a risk analysis module 238, a user tracking and rating module 240, a report generation module 250, and other modules 260.
The user registration and management module 134 is configured to register a new user (e.g., trader, transporter, vehicle owner, broker, vehicle driver, support services and so on) to the logistics transportation server 102 by verifying one or more input parameters provided by the user. For example, the input parameter include, but not limited to identity proof of individual and company, unique identity number associated with the user such as UIDAI number, GST number, licence number, pan number, and so on . The user registration and management module 134 is also configured to assign the new user with unique login credentials such as unique login name and password and store as user data in the data repository 120. Upon successful registration, the user can perform one or more transactions based on requirements. In one example, if the user needs one or more services of a transporter (or) service provider, the user may be registered as a trader requiring one or more services offered by the service provider to perform one or more interactions with the service provider.
In one implementation, the user registration and management module 134 is configured to receive the unique login credentials associated with the user provided by the user and verify the received login credentials with previously stored user data located in the data repository 120. In another embodiment, the user registration and management module 134 is configured to register a new user such as for example, trader, transporter, and support service directly with the logistics transportation server 102. However, users like for example, broker, vehicle owner, and vehicle driver may be registered with logistics transportation server 102 only upon receiving a recommendation from the transporter devices 106 for registration with the logistics transportation server 102. The user registration and management module 134 is also configured to manage different types of account based on subscription level of the user registered with the

logistics transportation system 100. For example, the user registration and management module 134 manages different types of accounts such as trial account, basic and premium accounts of each user based on the subscription paid by the user. Based on the type of account, the user registration and management module 134 enables the user to access one or more features provided by the logistics transportation server 102.
The user registration and management module 134 is configured to enable the device associated with the user such as trader, transporter, broker, vehicle owner, who may be the owner of a company, to add one or more employees with the logistics transportation system 100. The login credentials associated with the owner of the company are stored in the memory 132 as 'super admin'. The user registration and management module 134 enables the user to perform one or more activities associated with the one or more employees. For example, the one or more activities include assigning work to the one or more employees, and one or more business other related activities. For example, a registered traderl who is owner of company can register employees empl and emp_2 with the logistics transportation system 100. The registered traderl can assign a first task taskl such as delivery of goods from place A to place B to empl and assign second task task_2 such as delivery of goods from place C to place D to emp_2. In another embodiment, the user registration and management module 134 is also configured to enable the user (e.g., trader, transporter, vehicle owner, broker, and vehicle driver) to maintain one single account even if the user is associated with or owns multiple organizations. Upon registration, the users may be able to perform search for identifying relevant service providers who can offer the required services.
In one embodiment, the search module 138 is configured to receive a request for identifying service providers who would be capable of transporting goods from one location to another location. The search module 138 retrieves a list of service providers who can transport goods to a consignee who is the recipient of the goods based on the inputs received. The request comprises one or more inputs received from the user. In one example, if the user is the trader, the trader may provide one or more inputs such as a pickup location information, a drop location information, quantity of goods, load type, nature of goods, vehicle type, contract type, and so on. In an exemplary embodiment, the trader is configured to input at least one of location of the transporter, the pickup location information and drop location information by drawing a custom shape (or) pattern on the user device. The search module 138 is configured to retrieve the custom shape (or) pattern inputted on the trader device 104-N, estimate one or more

boundary points on the geographical map corresponding to the custom pattern, and retrieve a list of transporters based on the one or more boundary points. In one embodiment, the search module 138 is configured to consider the search pattern of the user, past search history of the user along with the one or more inputs to provide the list of transporters. In other embodiment, the search module 138 is also configured to auto-populate one or more fields to be searched based on one or more historical search information associated with the user. Based on the list of transporters retrieved during the search, a secure connection is established between the trader device 104-N and the transporter devices 106.
In one embodiment, the real time connection establishment module 232 is configured to establish a secure communication link between any two user devices using the application provided by the logistics transportation server 102. For example, the real time connection establishment module 232 is configured to establish the secure communication link between the trader device 104-N and the transporter device 106-N when a search query is received from the trader device 104-N or when a quotation is sent from the transporter device 106-N to the trader device 104. In another example, the real time connection establishment module 232 is configured to establish the secure communication link between the transporter device 106-N and the vehicle owner device 110-N or broker device 108-N when a query is made by the transporter device 104-N.
The document generation module 234 is configured to generate an agreement between any two users. For example, the document generation module 234 is configured to generate the agreement between the transporter and the trader upon receiving a request to generate the agreement from either the application hosted at the trader device 104-N or at the transporter device 106-N. Once the agreement is generated, the application hosted at the trader device 104 -Nor at the transporter device 106-N is provided with an option to customize or modify the agreement based on negotiation reached between the trader and the transporter. Further, the document generation module 234 enables the application hosted at the trader device 104-N to automatically generate an invoice to the consignee (i.e., recipient of goods). Further, the document generation module 234 also enables the application hosted at the transporter device 106-N to automatically generate a consignment note document (or) vehicle receipt. Also, the document generation module 234 also enables the application hosted at the transporter device 106-N to automatically generate a transportation challan document after all the goods are loaded from all loading locations. Further, the document generation module 234 also enables

the application hosted at the transporter device 106-N to automatically generate a delivery receipt when the goods are received by the consignee. Furthermore, the document generation module 234 also enables the application hosted at the trader device 104-N (or) transporter device 106-N to automatically generate e-way bill after the goods are loaded into the vehicle. Also, the document generation module 234 enables the application hosted at the transporter device 106-N to automatically generate a broker slip when the vehicle for the trip is arranged by the broker device 108-N. Also, the document generation module 234 also enables the application hosted at the transporter device 106-N to automatically generate a shortage certificate document to the trader device 104-N when at least one of driver and consignee reports shortage of goods. Further, the one or more documents generated are stored in the data repository 120 and also in the memory 132 of the logistics transportation server 102.
The route optimization module 236 is configured to determine optimum routes for the transportation of goods from pickup location to the drop location. In one embodiment, the route optimization module 236 dynamically determines changes in the route based on one or more parameters. For example, the parameters include such as weather conditions, the driver's proximity to law enforcement, the driver's availability to accept another task and pick up another simultaneous load at a nearby loading site, heavy city traffic, relevant changes to destination site policies and procedures, or other data that may be derived from the driver activity or data derived from one or more support service devices 114.
The risk analysis module 238 is configured to estimate a liability score of a particular load delivery. The risk analysis module 238 is configured to calculate the liability score based on one or more details such as a pickup location information, a drop location information, a driver information, a vehicle information, potential damage due to weather and other factors that are usually involved in determining risk for load delivery. In one embodiment, the liability score estimated may be processed by one or more support service devices 114 to enable support service providers such as insurance agents to aid in allocating an appropriate insurance premium for the users. In one embodiment, the liability score is estimated based on one or more inputs received about breakdown such as accident, theft, loss and damage of goods due to any natural calamity, need to change driver or vehicle, stuck due to any natural calamity that occurs en route. In one aspect, the liability score is estimated based on the one or more inputs received from the application hosted in the driver device 112-N or sensors 190 mounted in the vehicle or in the wristband worn by the driver. In another embodiment, the liability score estimated

based on the information received from the driver device 112-N is sent to the application hosted at the vehicle owner device 110-N to eliminate delays during the transportation ensuring that the goods are delivered intime. In an exemplary embodiment, the risk analysis module 238 is configured to estimate the liability score based on one or more past history of each user involved in a particular goods delivery. Further, the liability score estimated is stored in at least one of the data repository 120 and the logistics transportation server 102.
The real time payment management module 136 is configured to enable payment received by user to one or more support services in real time. In one embodiment, the real time payment management module 136 enables a payment gateway to perform a real time split of the payment received from the user and transfer the payment to the one or more recipients involved. For example, if the payment is received from the transporter device 106-N to make the payment for the vehicle owner and if the vehicle was arranged by the broker, the real time payment management module 136 is configured to receive the payment, determine recipients based on the transaction performed or agreement, split the payment received, and transfer at least a part of the payment to the broker and remaining payment to the vehicle owner in real time. In another example, if the payment is received from the trader device 104-N to make the payment for the transporter, the real time payment management module 136 is configured to receive the payment, determine recipient based on the transaction performed or agreement, and transfer the payment to the transporter in real time without any delay. In another example, if the payment is received from the vehicle owner to make the payment for the driver, the real-time payment module is configured to receive the payment, determine recipient based on the transaction performed or agreement, and transfer the payment to the driver real time without any delay.
The user tracking and rating module 240 is configured to receive information from one or more sensors 190 installed in at least one of one or more vehicles and wristbands worn by the user (e.g., trader, transporter, broker, vehicle owner, and vehicle driver). Further, the user tracking and rating module 240 is also configured to receive information from the online maps integrated into the application installed in the device associated with the user. The user tracking and rating module 240 is configured to track the user based on the information received and rate the user automatically based on the information received. In an example, the information received from the vehicle assigned to the driver can be used to locate and notify the location of the driver with one or more users involved. Further, the information received can also be used

to rate the driver. If the information indicates that the driver has delayed the delivery of goods (or) taken a different route from the route suggested by the application, the user tracking and rating module 240 is configured to automatically rate the driver based on the delay involved. In one embodiment, the user tracking and rating module 240 is also configured to assign one or more reward points for the user based on the ratings. Further, the user tracking and rating module 240 is also configured to track expenses of the driver during the trip and rate the driver accordingly. Further, the user tracking and rating module 240 is configured to receive one or more information related to each user from the data repository 120. In one example, the one or more information includes the search pattern of the user, past search history of the user, time taken by the user to respond to any request received using the application hosted on a user device and so on. Based on the received information, the user tracking and rating module 240 rates the user accordingly.
The report generation module 250 is configured to generate a report based on one or more inputs received from at least one user (e.g., trader, transporter, vehicle owner, broker, vehicle driver, and support services). The report may include a list of posts, orders, previous agreements, previous trips, and previous routes related to the user. In one embodiment, the report generation module 250 is configured to automatically generate a report periodically (e.g., end of trip, daily, weekly, monthly, and yearly) and send the generated report to the one or more users. In another embodiment, the report generation module 250 is configured to generate a report when a request is received from one or more users. Further, the report generation module 250 also generates a customized report based on inputs received from at least one user. The generated report can be used for one or more business analytics such as costs saved for each trip, total trips taken, delayed deliveries, on time deliveries, cancelled trips, active trips, company wise reports, agreements pending, and so on.
Figure 3 illustrates exemplary steps of a method performed by one or more devices included in the logistics transportation system in accordance with embodiments of the present disclosure. As illustrated in Figure 3, the method comprises one or more steps implemented by one more module of the logistics transportation system 100. The method may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routine, programs, objects, components, data structures, procedures, units, and functions, which perform particular functions or implement particular abstract data types.

At step 310, a request including search for transporter is sent from the trader device 104-N to the logistics transportation server 102. In one embodiment, the application hosted at the trader device 104-N is configured to send a request comprising one or more inputs to the logistics transportation server 102. For example, the one or more inputs includes at least one of a pickup location information, a drop location information, quantity of goods, load type, nature of goods, vehicle type, contract type, and so on. In an exemplary embodiment, the application hosted in the trader devices 104-N is configured to receive input comprising at least one of location of trader, the one or more pick up location information, and the one or more drop location information by drawing a custom shape (or) pattern on trader device 104-N.
At step 315, a list of transporters based on the request is received and sent from the logistics transportation server 102 to the trader device 104-N. In one embodiment, the search module 138 of the logistics transportation server 102 is configured to retrieve the custom shape (or) pattern inputted on the trader device 104-N. The search module 138 is configured to estimate one or more boundary points on geographical map corresponding to the custom pattern and retrieve the list of transporters based on the one or more boundary points estimated.
At step 318, a list of enquiries is sent from the trader device 104-N to each of the transporter device 106-N included in the list of transporters. The application hosted at the trader device 104-N is configured to send the list of enquiries to each of the transporter devices 106 included in the list of transporters. In one embodiment, the list of enquiries can be at least one of multiple pickup locations, multiple drop locations, date and time of pick up, date and time of drop, freight terms, insurance information, delivery type, name of goods, packaging type, and so on.
At step 320, a quotation is sent from each of the transporter devices 106 to the trader device 104-N. In one embodiment, the application hosted at the transporter devices 106 is configured to send a quotation to the trader device 104-N based on the list of enquires received.
At step 325, a request including search for vehicle is sent from the transporter device 106-N to the logistics transportation server 102. In one embodiment, the application hosted at the transporter devices 106 is configured to automatically post a request to the logistics transportation server 102. The request for the logistics transportation server 102 is sent simultaneously when sending the quotation to the application hosted at the trader device 104-N, when the logistics transportation server 102 determines that the transporter does not have

any vehicle and is registered with the logistics transportation server 102 only as transporter. In another embodiment, the application hosted at the transporter device 106-N is configured to automatically post a request to the logistics transportation server 102. The request for the logistics transportation server 102 is sent simultaneously when sending the quotation to the application hosted the trader device 104-N when the logistics transportation server 102 determines that the one or more vehicles owned by transporter are not available based on enquiry received.
At step 332, a notification is sent from the logistics transportation server 102 to one of the vehicle owner devices 110 and the broker devices 108. In one embodiment, the logistics transportation server 102 is configured to send notification that includes a request to assign vehicle to one or more vehicle owner devices 110 and broker devices 108 registered with the logistics transportation server 102 and matching with one or more requirements of the transporter request.
At step 335, a quotation is sent from one of the vehicle owner devices 110 and the broker devices 108 to the transporter devices 106. In one embodiment, the application hosted at either vehicle owner devices 110 or broker devices 108 is configured to send quotation to the transporter devices 106.
At step 336, a secure communication link is established between one of the vehicle owner devices 110 (or) the broker devices 108, and the transporter devices 106. In one embodiment, the real time connection establishment module 232 is configured to establish the secure communication link between one of the vehicle owner devices 110 or the broker devices 108 and the transporter devices 106 to communicate and negotiate on the quotation sent.
At step 337 a secure communication link is established between the trader devices 104 and the transporter devices 106. In one embodiment, the secure communication link is established between the trader devices 104 and the transporter devices 106 enabling the trader and the transporter to communicate and negotiate on the quotation sent.
At step 338, an agreement is generated. In one embodiment, the document generation module 234 of the logistics transportation server 102 is configured to generate an agreement for an order or transaction generated between the transporter and the trader once the negotiation is

complete. The document generation module 234 receives a request for the agreement generation from either the application hosted at the trader devices 104 (or) at the transporter devices 106. The application hosted at the trader devices 104 (or) at the transporter devices 106 is configured to customize (or) modify the agreement based on negotiation and agreement reached between the trader and the transporter. The generation of the agreement between the trader and the transport will confirm the order from the trader to the transporter.
At step 340, a confirmation message is sent from the transporter devices 106 to one of the vehicle owner devices 110 or the broker devices 108. In one embodiment, the application hosted at the transporter devices 106 is configured to send confirmation messages that includes agreement for the quotation sent. In another embodiment, the document generation module 234 of the logistics transportation server 102 generates an internal agreement between one of the vehicle owner devices 110 or the broker devices 108, and the transporter devices 106 once a request for the agreement generation is sent from either the application hosted at the transporter devices 106..
At step 342, a vehicle and a driver is assigned. In one embodiment, the application hosted at the vehicle owner device 110 is configured to assign a vehicle for the transporter based on the request from the transporter device 106-N. In one embodiment, the driver is assigned based on the rating of the driver and proximity of the driver to the pickup location information, availability of the driver on the date of the trip. In another embodiment, the application hosted at the transporter device 106-N can directly assign a vehicle if the transporter owns one or more vehicles which are available to be assigned. In another embodiment, the driver is also assigned by verifying one or more parameters such as driver's license expiry date, behaviour pattern of driver, past trip history of the driver including the routes travelled, and so on related to the driver.
At step 344, a confirmation message is sent from one of the application hosted at the vehicle owner devices 110 and the broker devices 108 to the application hosted at the transporter device 106-N. In one embodiment, the application hosted at the vehicle owner device 110-N is configured to automatically send a confirmation message along with one or more details of the vehicle allotted to the transporter device 106-N.

At step 345, a notification is sent to the vehicle driver. In one embodiment, the application hosted at the vehicle driver device 112-N is configured to receive notification. The notification includes for example, one or more pickup locations and one or more drop locations information, date and time for pickup and delivery, and quantity of goods, nature of goods, type of goods, partial load delivery or full load delivery, incentive for the trip, a target expenditure for the trip and so on.
At step 350, a driver access support services and a real-time payment is initiated. In one embodiment, the application hosted in the driver device 112-N is configured to access one or more support services based on the notification from the one or more sensors 190. In one example, the application hosted in the driver device 112-N receives notification about nearby petrol shops located in the proximity of the vehicle upon receiving an alert/warning from the one or more sensors 190 about less fuel. In another embodiment, the driver can search for one or more support services using the application hosted at the driver device 112-N.
The drivers can search for support services located in the proximity that are on the route for that trip as per their requirement. For example, if the driver is looking for a support service such as a hotel, the driver will search for the hostels which are registered as support services. Further, the application hosted at the driver device 112-N may receive a list of support services that are registered with the logistics transportation sever 102 and are present on the particular route for the trip, thereby eliminating the delay in transportation, as one or more fake locations in the maps are not shown when the driver is performing search. Further, the application hosted at the driver device 112-N may receive information about one or more offers provided by each of the support services when the support services upload the one or more offers using the application hosted at the support service device 114-N.
Also, the application hosted at the driver device 112-N send a notification to the support services when the driver needs one or more services, thereby the logistics transportation server 102 determines estimated time required for the driver to reach the support service . Further, the logistics transportation server 102 send the estimated time determined to the support service devices 114, so that the support services are prepared to assist the driver and eliminating any delay that could otherwise occur due to lack of communication between the driver and support service. Further, the one or more users such as transporter, vehicle owner associated with the driver will be notified about the driver accessing a particular support service. Further, the

application hosted at the driver device 112-N is configured to initiate a payment for the accessed support services. Based on the payment initiated, the real-time payment module 136 is configured to enable a payment gateway to perform a real time split of the payment received from the user-initiated payment and transfer the payment to the one or more recipients involved. Further, any payments made by drivers to support services or any expenditure incurred during the trip is recorded by the logistics transportation sever 102 to eliminate any false expenditures by the driver that would result in an unnecessary increase in transportation cost. Further, upon the completion of the trip, if the payment is received from the trader to make the payment for the transporter, the real time payment management module 136 is configured to receive the payment and transfer the payment to the transporter real time without any delay. Further, if the payment is received from the transporter to make the payment for the vehicle owner, the real time payment management module 136 is configured to receive the payment, determine recipient based on the transaction performed or agreement, split the payment received, and transfer at least a part of the payment to the broker and remaining payment to the vehicle owner in real time.
Thus, the transportation communication system 100 enables real time interactions between one or more users, processing real time payment, and enhanced user experience, thereby enabling all users of the logistics industry such as trader, transporter, broker, vehicle owner, vehicle driver, and support services to communicate and coordinate to provide end-to-end solution from booking to delivery of the goods in an efficient manner.
Figure 4 is a flowchart illustrating a method enabled by the logistics transportation system 100 from assigning the driver to the trip till the delivery of goods in accordance with some embodiments of the present disclosure.
As illustrated in Figure 4, the method comprises one or more steps implemented by one more module of the logistics transportation system 100. The method may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routine, programs, objects, components, data structures, procedures, units, and functions, which perform particular functions or implement particular abstract data types.
The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement

the method. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.
At step 402, a notification is received by the vehicle driver device 112-N. In one embodiment, the application hosted at the vehicle driver device 112-N is configured to receive notification when at least one of transporter, broker, and/or vehicle owner assigns the driver for the trip. In one embodiment, the notification includes one or more pickup locations and one or more drop locations information. In an exemplary embodiment, the application hosted at the driver device 112-N provides an option to accept (or) reject the trip when a notification is received and when the driver is assigned for the trip by a user who is not an owner for the driver. Upon acceptance of the trip, the application hosted at the vehicle driver device 112-N receives more details such as pickup locations and drop locations, date and time for pickup and delivery, and quantity of goods, nature of goods, type of goods, partial load delivery or full load delivery, incentive for the trip, a target expenditure for the trip, and so on.
At step 404, send one or more sensor data from the driver on the day of the trip. The application hosted at the driver device 112-N is configured to receive data, on the date of trip, from the one or more sensors included in a wristband worn by the driver and send health information of the driver to the logistics transportation server 102. Further, the real time connection establishment module 232 generates an alert or notification to the one or more user device such transporter devices 106, the vehicle owner devices 110, and the broker devices 108. If the health information of the driver is not within acceptable range, the real time connection establishment module 232 will alert the transporter device 106, the broker device 108, or vehicle owner 110 about assigning another driver for the trip.
At step 406, enable the driver to start the trip. The application hosted at the driver device 112-N is configured to capture one or more images of the empty vehicle and vehicle mileometer reading using the application and verifies the captured images using one or more sensor data from the one or more sensors 190 installed in the vehicle. In another embodiment, as an additional step of verification, driver license details and vehicle registration details are verified by capturing the driver license and vehicle registration certificate by the one or more sensors 190 and comparing the captured images with the previously stored images stored in the data

repository 120. Upon verifying the captured images with the sensor data, and driver license details & vehicle registration details and receiving inputs on the application hosted at the driver device 112-N from the driver about packing materials, the application hosted at the driver device 112-N will receive an alert from the logistics transportation server 102 and enable the driver to start the trip. In another embodiment, the application hosted at the vehicle driver device 112-N is configured to send one or more notifications, using the real time connection establishment module 232, to the trader device 104-N, transporter device 106-N, the broker device 108-N, and the vehicle owner device 110-N when the driver starts the trip.
At step 408, validate weight of goods at each loading location. In one embodiment, as the driver reaches each loading location, in case of multiple loading locations, the logistics transportation server 102 send a notification to the application hosted at the trader device 104-N, transporter device 106-N, broker device 108-N, and vehicle owner device 110-N. The one or more sensors 190 installed in the vehicle will record weight of the present vehicle weight (i.e., Tare Weight in case of first loading location) and are compared with vehicle weight details entered by the trader in the application hosted at the trader device 104. The application hosted at the driver device 112-N will automatically match the weight recorded by the sensor 190 with the vehicle weight details entered by the trader and if there is any discrepancy, the application hosted the driver device 112-N will notify the trader device 104-N and the transport device 106-N to re-upload or decide which weight to consider as present vehicle weight for the trip. Further, the one or more sensors 190 will capture one or more images after the goods are loaded and send to the transporter device 106-N as a notification to confirm that the goods are loaded and packaged properly with the packaging supplies. Also, the one or more sensors 190 measure the weight of the vehicle after goods are loaded into the vehicle (i.e., Gross Weight) to determine weight of the loaded goods (i.e., Net Weight). Further, the net weight is compared with net weight inputted by the trader and if there is any discrepancy, the application hosted in the driver device 112-N will notify trader device 104-N and transport device 106-N to re-upload or decide which weight to consider as net weight for the trip.
At step 410, one or more documents are generated. The application hosted at the trader device 104-N is configured to generate an invoice to the consignee automatically using the document generation module of the logistics transportation server 102. Further, the application hosted at the trader device 104-N is configured to upload one or more trader related documents such as test/analysis reports, insurance copy, covering letter, and so on. Further, the application hosted

at the transporter device 106-N is configured to generate a consignment note (or) vehicle receipt automatically using the document generation module 234 of the logistics transportation server 102. Also, the application hosted at the transporter device 106-N is configured to generate a transportation challan automatically after all the goods are loaded from all loading locations using the document generation module of the logistics transportation server 102. Furthermore, the application hosted at the trader device 104-N or transporter device 106-N automatically generate e-way bill using the document generation module 234.
At step 412, one or more events are determined. The application hosted at the driver device 112-N (or) logistics transportation server 102 is configured to continuously (or) periodically monitor the one or more sensor data to determine one or more deviations. The one or more deviations includes, but not limited to, change in weight sensor data, change in temperature data, change in heart sensor data and so on. The application hosted at the driver device 112-N (or) the logistics transportation server 102 is configured to determine one or more deviations by comparing the one or more sensor data at a present instance with the one or more sensor data captured and stored in the data repository during start of the trip. The application hosted at the driver device 112-N (or) the logistics transportation server 102 is configured to determine one or more events based on the one or more deviations determined and is explained in more detail in Figure 5. The one or more events includes at least one of: theft of goods, accident, bad weather conditions, natural calamity, loss of goods, driver fallen sick, vehicle breakdown, and so on.
At step 414, validate weight of goods at each unloading location. In one embodiment, as the driver reaches each unloading location, in case of multiple unloading locations, the logistics transportation server 102 send a notification to the application hosted at the trader device 104-N, transporter device 106-N, broker device 108-N, and vehicle owner device 110-N. The one or more sensors 190 installed in the vehicle will record weight of the present vehicle weight and are compared with present vehicle weight details entered by the consignee. The application hosted at the driver device 112-N will automatically match the weight recorded by the one or more sensors 190 with the vehicle weight details entered by the consignee and if there is any discrepancy, the application hosted at the driver device 112-N will notify the trader device 104-N, and the transport device 106-N. Further, based on the discrepancy, the application hosted at the transporter device 106-N will automatically issue a shortage certificate to the trader device 104-N. The application hosted at the trader device 104-N will automatically send a claim

request to the insurance company based on the shortage certificate issued by the trader. Further, the consignee will verify the vehicle details, driver details, and quality of goods and update the details either in the application hosted at the driver device 112-N (or) at the application hosted at a consignee device.
At step 416, the notification is sent about delivery of goods. In one embodiment, the application hosted at the driver device 112-N (or) logistics transportation server 102 or consignee device is configured to notify the trader, transporter, and the vehicle owner or broker when the goods are received. In one embodiment, when the consignee device does not have application installed, the application hosted at the driver device 112-N is configured to send the notification about delivery of goods after the consignee inputs one or more unique identification number such as OTP, identification number provided by the logistics transportation server 102 to consignee device for a particular trip, and so on, associated with consignee on the driver device 112-N. Upon receiving the notification that the goods are received by the consignee, the application hosted at the transporter device 106-N will generate delivery receipts. The application hosted at the transporter device 106-N will send the delivery receipts as notification to the trader device 104-N for the final payment as per the payment agreed between the trader and the transporter. In another embodiment, the application hosted at the driver device 112-N (or) logistics transportation server 102 (or) consignee device is configured to notify the trader, transporter, and the vehicle owner when the goods are rejected by the consignee. Once the goods are rejected by the consignee, an alert will be sent to the application hosted at the trader device 102-N indicating reason for rejection.
Based on the alert generated, the trader device 104-N can communicate with the consignee device to negotiate and provide a final decision of the consignee. Upon receiving the final decision of the consignee device, the transporter device 106-N will be notified that the goods are rejected by the consignee. The application hosted at the transporter device 106-N will assign the vehicle and driver for the return trip. In one embodiment, the transporter device 106-N will assign the same vehicle and driver for the return trip, as of the original trip. In another embodiment, the application hosted at the trader device 104-N will send a request to another transporter to assign the vehicle and driver for the return trip, when the transporter assigned for the original trip is not available. After the driver and the vehicle are assigned for the return trip, and once goods are loaded into the vehicle and before the driver starts the return trip, the application hosted at the transporter device 106-N will generate a return consignment note

document. Further, the application hosted at the transporter device 106-N or trader device 104-N will generate e-way bill for the return trip after the goods are loaded into the vehicle, and before the driver starts the return trip.
Figure 5 is a flowchart illustrating a method enabled by the logistics transportation system 100 to detect one or more events during the driver's trip in accordance with some embodiments of the present disclosure.
As illustrated in figure 5, the flowchart 412 comprises one or more steps or blocks performed by one or more devices of the logistics transportation system 100 in accordance with an embodiment of the present disclosure.
The order in which the method 412 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.
At block 502, one or more sensor data is received. The logistics transportation server 102 is configured to receive one or more sensor data when a driver starts a trip and is stored in the data repository 120. In one embodiment, the one or more sensor data is collected from one or more sensors 190 located in a vehicle assigned to the driver and in a wristband worn by the driver. The one or more sensors 190 includes pressure sensor, weight, speed sensor, accelerometer sensor, gyroscope sensor, heart rate sensor, temperature sensor, camera sensor and so on. In an exemplary embodiment, the one or more sensor data is transmitted by the application hosted at the driver device 112-N and is received by the logistics transportation server 102 and is stored in the data repository 120.
At block 504, a first set of images are received. The logistics transportation server 102 is configured to receive a first set of images of the vehicle assigned to the driver. The first set of images includes one or more images of the vehicle such as front view, side view, top view, and bottom view, and back view of the vehicle when the goods are loaded into the vehicle. In one embodiment, the first set of images are received by the logistics transportation server 102 using

one or more sensors 190 placed in the vehicle. In another embodiment, the first set of images are captured by the application hosted at the driver device 112-N using the camera sensor of the driver device 112-N. In an exemplary embodiment, the first set of images transmitted by the application hosted at the driver device 112-N is received by the logistics transportation server 102 and is stored in the data repository 120.
At block 506, the one or more sensor data is monitored. The application hosted at the driver device 112-N (or) the logistics transportation server 102 is configured to continuously (or) periodically monitor the one or more sensors 190 to determine one or more deviations. The one or more deviations includes, but not limited to, change in weight sensor data, change in temperature data, change in heart sensor data and so on. The application hosted at the driver device 112-N (or) the logistics transportation server 102 is configured to determine one or more deviations by comparing the one or more sensor data at a present instance with the one or more sensor data captured and stored in the data repository 120 during the start of the trip.
At block 508, a second set of images are captured. The logistics transportation server 102 send a request to one or more sensors 190to capture a second set of images of one of the vehicles and the driver based on the one or more deviations. The second set of images includes one or more images of the vehicle such as front view, side view, top view, and bottom view, and back view of the vehicle based on the deviations. For example, if the deviation is detected in weight sensor data, the second set of images includes one or more images of the goods are captured when the vehicle is in transit. In another example, if the deviation is detected in heart rate sensor data, then the second set of images include one or more images of the driver. In an exemplary embodiment, the second set of images transmitted by the application hosted at the driver device 112-N is received by the logistics transportation server 102 and is stored in the data repository 120.
At block 510, the captured second set of images and one or more sensor data are analysed. The application hosted at the driver device 112-N (or) the logistics transportation server 102 is configured to determine one or more events by analyzing the first set of images and the second set of images and also by analyzing the one or more sensor data. For example, the one or more events includes at least one of theft of goods, accident, bad weather conditions, natural calamity, loss of goods, driver fallen sick, vehicle breakdown, and so on.

At block 512, one or more alerts are generated. The application hosted at the driver device 112-N (or) the logistics transportation server 102 is configured to generate one or more alerts to at least one of the trader devices 104, transporter devices 106, broker devices 108, the vehicle owner devicesllO, and support service devices 114 based on the one or more events. In one example, the one or more alerts may be an alert to assign at least another driver and another vehicle based on the one or more events. In another example, the one or more alerts may be an alert to automatically dial an emergency ambulance and share the current location of the vehicle to one or more emergency rescue teams. In another example, one or more alert may also include severity level associated with the one or more events. For example, if the alert is sent to the vehicle owner as vehicle breakdown with less severity, then the vehicle owner device 110-N can send a request to support service devices 114 registered as a vehicle repair shop.
In another example, if the alert is sent to the application hosted at the transporter device 106 as vehicle breakdown with high severity, and also notified about recommendation to a particular vehicle, then the transporter using the application hosted at the transporter device 106-N can choose either recommended vehicle (or) send a new request to assign a new vehicle. In an exemplary embodiment, the one or more alerts automatically send an insurance request in case one or more events are identified as one of an accident, theft, and loss and damage of goods. In another exemplary embodiment, when the one or more alerts includes alert to one of vehicle owner and transporter about natural calamity with high severity, then the route optimization module 236 of the logistics transportation server 102 send a notification to application hosted at the driver device 112-N to suggest at least one of change of route, reach nearby safest place provided by the support services. In one embodiment, the logistics transportation server 102 generates revised invoice and e-way bill based on one or more events using the document generation module 234. Further, based on the severity level associated with one or more events, the application hosted at the trader device 104-N, transporter device 106-N, broker device 108-N, vehicle owner device 110-N, and driver device 112-N automatically generates one or more documents such as first information report (FIR) , insurance claim report, and so on. The application hosted at the driver device 112-N also notifies the driver about the location of the nearest police station, hospital, and one or more support services. In one embodiment, the logistics transportation server 102 generates and transmits alerts generated to the application hosted at the driver device 112-N about one or more best possible routes to repair the vehicle is minimum possible time in case event is determined as breakdown of vehicle with one or

more repairs. In one embodiment, the logistics transportation server 102 generates and sends alerts to the application installed at the transporter device 106-N or at the vehicle owner device 110-N or the broker device 108-N about the estimated time for change of vehicle or repair of vehicle.
Thus, the transportation communication system 100 enables generating real time notification when one or more events associated with the vehicle and/or driver is detected, thereby enabling the entire logistic transportation system to function in an efficient manner.
Figure 6 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
In an embodiment, the computer system 602 may be logistics transportation system 100. The computer system 602 may include a central processing unit ("CPU" or "processor") 604. The processor 604 may comprise at least one data processor for executing program components for executing user or system-generated business processes. The processor 604 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.
The processor 604 may be disposed in communication with one or more input/output (I/O) devices (606 and 608) via I/O interface 610. The I/O interface 610 may employ communication protocols/methods such as, without limitation, audio, analog, digital, stereo, IEEE-1394, serial bus, Universal Serial Bus (USB), infrared, PS/2, BNC, coaxial, component, composite, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System For Mobile Communications (GSM), Long-Term Evolution (LTE) or the like), etc.
Using the I/O interface 610, the computer system 602 may communicate with one or more I/O devices. For example, the input device 606 may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, sensor (e.g., accelerometer, light sensor, GPS, gyroscope, proximity sensor, or the like), stylus, scanner, storage device, transceiver, video device/source, visors, etc. Output device 608 may be a printer, fax machine, video display (e.g.,

cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, or the like), audio speaker, etc. In some embodiments, a transceiver 609 may be disposed in connection with the processor 604. The transceiver may facilitate various types of wireless transmission or reception. For example, the transceiver may include an antenna operatively connected to a transceiver chip (e.g., Texas Instruments WiLink WL1283, Broadcom BCM4750IUB8, Infineon Technologies X-Gold 618-PMB9800, or the like), providing IEEE 802.11a/b/g/n, Bluetooth, FM, global positioning system (GPS), 2G/3G HSDPA/HSUPA communications, etc.
In some implementations, the processor 604 may be disposed in communication with a communication network 130 via a network interface 614. The network interface 614 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), Transmission Control Protocol/Internet Protocol (TCP/IP), token ring, IEEE 802.1 la/b/g/n/x, etc. Using the network interface 614 and the communication network 130, the computer system 602 can be the logistics transportation server 102 and is connected to the data repository 120, trader devices 104, transporter devices 106, broker devices 108, vehicle owner devices 110, driver devices 112, and support service devices 114.
The communication network 130 can be implemented as one of the several types of networks, such as intranet or any such wireless network interfaces. The communication network 130 may either be a dedicated network or a shared network, which represents an association of several types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other. Further, the communication network 130 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc.
In some embodiments, the processor 604 may be disposed in communication with a memory 616 e.g., RAM 618, and ROM 620, etc. as shown in Figure 6, via a storage interface 622. The storage interface 622 may connect to memory 616 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fiber channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive,

Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.
The memory 616 may store a collection of program or database components, including, without limitation, user/application 624, an operating system 626, a web browser 628, a mail client 630, a mail server 632, a user interface 634, and the like. In some embodiments, computer system 602 may store user/application data 624, such as the data, variables, records, etc. as described in this invention. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.
The operating system 626 may facilitate resource management and operation of the computer system 602. Examples of operating systems include, without limitation, Apple Macintosh TM OS X TM, UNIX TM, Unix-like system distributions (e.g., Berkeley Software Distribution (BSD), FreeBSD TM, Net BSD TM, Open BSD TM, etc.), Linux distributions (e.g., Red Hat TM, Ubuntu TM, K-Ubuntu TM, etc.), International Business Machines (IBM TM) OS/2 TM, Microsoft Windows TM (XP TM, Vista/7/8, etc.), Apple iOS TM, Google Android TM, Blackberry TM Operating System (OS), or the like. A user interface may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to the computer system 602, such as cursors, icons, check boxes, menus, windows, widgets, etc. Graphical User Interfaces (GUIs) may be employed, including, without limitation, Apple TM Macintosh TM operating systems' Aqua TM, IBM TM OS/2 TM, Microsoft TM Windows TM (e.g., Aero, Metro, etc.), Unix X-Windows TM, web interface libraries (e.g., ActiveX, Java, JavaScript, AJAX, HTML, Adobe Flash, etc.), or the like.
The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained

herein. Such alternatives fall within the scope and spirit of the disclosed embodiments. Also, the words "comprising," "having," "containing," and "including," and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.
Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., are non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.
Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the embodiments of the disclosure is intended to be illustrative, but not limiting, of the scope of the disclosure.
With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

We Claim:

1. A logistics transportation system for connecting one or more user devices, the system
comprising:
a first application hosted at a first user device configured to send a first request from a first user;
a logistics transportation server configured to retrieve a list of second users based on the first request received, wherein the first application is configured to send a second request in response to the retrieved list; and
a second application hosted at a second user device configured to send a quotation to the first application in response to the second request received, wherein the logistics transportation server is configured to establish a communication link between the first user device and the second user device when the quotation is sent to the first application.
2. The logistics transportation system as claimed in claim 1, wherein the second application is configured to allocate a vehicle and a driver to the first user when a confirmation is received from the first application for the quotation sent and when the second user device is registered as a transporter having one or more available vehicles, wherein the vehicle is allotted based on the first and second request received, wherein the driver is assigned based on rating of the drivers and proximity of the driver to the pickup location information, availability of the driver on the date of the trip, search pattern of driver, past trip history of the driver including the routes travelled, and so on.
3. The logistics transportation system as claimed in claim 1, wherein the first request includes at least one of a pickup location information, a drop location information, quantity of goods, load type, nature of goods, vehicle type, contract type, and so on, wherein at least one of: the location of the transporter, one or more pick up location information, one or more drop location information is inputted by drawing a custom pattern on the first application, and wherein the second request includes at least one of multiple pick up locations information, multiple drop locations information, date and time of pick up, date and time of drop, freight terms, insurance information, delivery type, name of goods, packaging type, and so on .
4. The logistics transportation system as claimed in claim 1, wherein the second application is configured to automatically post a request to the logistics transportation server

simultaneously when sending the quotation to the first application when the second user device is registered as a transporter.
5. The logistics transportation system as claimed in claim 4, further comprising:
a third application hosted on a third user device configured to:
receive a notification from the logistics transportation server in response to the request posted by the second application;
send a quotation to the second application based on the notification received; and allocate a vehicle and a driver to the second user when a confirmation is received from the second user application for the quotation sent, wherein the vehicle is allotted based on the request received from the second user device, wherein the driver is assigned based on rating of the drivers and proximity of the driver to the pickup location information, availability of the driver on the date of the trip, behaviour pattern of driver, past trip history of the driver including the routes travelled, and so on.
6. The logistics transportation system as claimed in claim 5, further comprising:
a fourth application hosted at a device associated with the driver configured to:
receive an alert when the driver is assigned with the vehicle;
receive one or more notifications from a fifth application hosted at one or more support services when the driver is navigating; and
initiate a dynamic real time payment for the one or more support services when the driver accesses the one or more support services, wherein the fourth application is also configured to:
receive one or more inputs from the driver to search for one or more support services when the drive is navigating.
7. The logistics transportation system as claimed in claim 6, wherein the one or more
support services are configured to:
register with the logistics transportation server using the fifth application for providing one or more services to the first user, the second user, the third user, and the driver; and
upload information about one or more offers provided to one or more users registered, wherein the uploaded information is accessed when the one or more users perform search to locate the one or more support services.

8. The logistics transportation system as claimed in claim 3, wherein the logistics
transportation server is configured to retrieve the list of second users by:
retrieve the custom pattern inputted on the first application;
estimate one or more boundary points on the geographical map corresponding to the custom pattern; and
retrieve the list of second users based on the one or more boundary points estimated,, wherein the list of second users retrieved is also based on search pattern of the first user, past search history of the first user, and the first request received.
9. The logistics transportation system as claimed in claim 1,, wherein the first user device is registered as a trader, wherein the third user device is registered as one of a vehicle owner and a broker, wherein the first request from the first application includes a request to retrieve a list of transporters, wherein the second request from the first application includes a list of enquires to one or more transporters from the retrieved list of transporters, wherein the request from the second application includes a request for the third user to assign a vehicle and a driver to the second user.
10. The logistics transportation system as claimed in claim 9, wherein the logistics transportation server comprises:
a document generation module that is configured to generate one or more documents for the one or more users, wherein the one or more documents includes at least one of: invoice, e-way bill, consignment note, delivery receipt, transport challan, broker slip, weighment slip, shortage certificate, and agreement.
11. The logistics transportation system as claimed in claim 5, further comprising:
one or more sensors incorporated in at least one of: wristband worn by the driver and the vehicle, wherein the one or more sensors include at least one of pressure sensor, weight sensor, speed sensor, accelerometer sensor, gyroscope sensor, heart rate sensor, temperature sensor, and camera sensor, wherein the application hosted at the logistics transportation server (or) at the driver device is configured to:
detect one or more deviations in the sensor data received from the one or more
sensor data;

determine one or more events based on the one or more deviations detected, wherein the one or more events include at least one of theft of goods, accident, bad weather conditions, natural calamity, loss of goods, vehicle breakdown, driver fallen sick and so on; and
generate one or more alerts based on the one or more events determined, wherein the one or more alerts include at least one of: assign new vehicle, assign new driver, send notification to at least one user, wherein the at least one user is a trader, a transporter, a vehicle owner, a broker, and support service.
12. The logistics transportation system as claimed in claim 1, wherein the logistics transportation server comprises:
a real-time payment module that is configured to:
receive payment from at least one user, wherein the at least one user is a trader, a transporter, a vehicle owner, a broker, and vehicle driver; determine recipients based on the payment received; split the payment received dynamically in real-time; and transfer the payment to one or more recipients of the payment in real-time.