Description:FIELD OF THE INVENTION

[0001] The present invention is a patent of addition for Indian Patent Application number IN 202311023941. The present invention generally relates to traffic management and more particularly relates to a system and method of generating a fee report for a toll-road thereof.

BACKGROUND

[0002] Toll roads play a significant role in modern transportation networks, offering improved road quality, reduced travel times, and maintenance of road infrastructure. However, the operation of toll-gates on these roads can give rise to various issues such as traffic congestion, accidents, security concerns, and toll evasion. The existing technologies so far have failed to explore these challenges and provide potential solutions.
[0003] Toll-road are those for which travellers are required to pay a fee or “toll” in order to use the road. This fee contributes to the maintenance, expansion, and enhancement of the road infrastructure. A toll-gate is the designated points along these toll-road where tolls are collected. Unfortunately, the toll-gate may inadvertently contribute to traffic jams and accidents. Long lines of vehicles waiting to pass through the toll-gate may lead to traffic congestion on both sides, especially during peak travel times. Moreover, sudden stops at the toll-gate may increase the risk of rear-end collisions, adding to the overall road safety concerns.
[0004] Traditional toll collection techniques often involve manual toll collection, where human toll collectors are stationed at the toll-gate to collect fees. While this provides employment opportunities, it comes with its own set of challenges. Toll collectors are exposed to various weather conditions, and their physical presence also poses security risks. Instances of theft and burglary targeting toll collectors have been reported, which not only endangers their lives but also disrupts the toll collection process.
[0005] Further, toll evasion is another issue prevalent at the toll-gate. Some drivers attempt to avoid paying tolls by taking alternate routes that lead away from the toll-road and then rejoining it after bypassing the toll-gate. This not only affects toll revenue collection but also contributes to congestion on these alternate routes, as well as increased wear and tear on local roads not designed to handle such traffic loads.
[0006] Furthermore, an inherent problem with existing toll systems is that all drivers, regardless of the distance they travel on the toll-road, are required to pay an equal toll fee. This can be perceived as unfair, as drivers who cover longer distances end up paying the same toll as those who cover shorter distances.
[0007] To address these challenges, there exists a need to find a technical solution for the above-mentioned technical problems.
SUMMARY

[0008] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention and nor is it intended for determining the scope of the invention.
[0009] According to one embodiment of the present disclosure, a method for traffic management. The method includes receiving, by a server, from a plurality of roadside receivers positioned at different geo-locations on a toll-road, a device state input corresponding to detection of at least one vehicle, wherein the plurality of roadside receivers comprises at least a first roadside receiver and a second roadside receiver. Further, the method includes determining, by the server, a distance travelled by the at least one vehicle between a geo-location corresponding to the first roadside receiver and a geo-location corresponding to the second roadside receiver based on the device state input received from the plurality of roadside receivers. Furthermore, the method includes generating, by the server, a fee report corresponding to the at least one vehicle based on the determined distance and a predetermined rule.
[0010] According to one embodiment of the present disclosure, a system for traffic management is disclosed. The includes a memory and at least one processor communicably coupled to the memory. The at least one processor is configured to receive from a plurality of roadside receivers positioned at different geo-locations on a toll road, a device state input corresponding to detection of at least one vehicle, wherein the plurality of roadside receivers comprises at least a first roadside receiver and a second roadside receiver. Further, the at least one processor is configured to determine a distance travelled by the at least one vehicle between a geo-location corresponding to the first roadside receiver and a geo-location corresponding to the second roadside receiver based on the device state input received from the plurality of roadside receivers. Furthermore, the at least one processor is configured to generate a fee report corresponding to the at least one vehicle based on the determined distance and a predetermined rule.
[0011] To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail in the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0013] Figure 1 illustrates a schematic block diagram depicting an environment for the implementation of a system for traffic management, according to an embodiment of the present invention;
[0014] Figure 2 illustrates another schematic detailed block diagram of modules/software components of the system, according to an embodiment of the present invention;
[0015] Figure 3 illustrates a flow chart of a method for traffic management, according to an embodiment of the present invention; and
[0016] Figure 4 illustrates an exemplary use case of the system, according to an embodiment of the present invention.
[0017] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

DETAILED DESCRIPTION

[0018] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the various embodiments and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.
[0019] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.
[0020] Reference throughout this specification to “an aspect,” “another aspect” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase “in an embodiment”, “in another embodiment” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0021] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by “comprises... a” does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.
[0022] The present disclosure aims to provide an integrated platform or an application that may be in communication with multiple devices installed in vehicles and is adapted to generate a fee report upon at least one vehicle passing through a toll gate. Further, the fee report is shared with a payment network or a payment gateway such that a user may consequently perform a transaction. Furthermore, the fee report corresponds to an amount the user is required to pay for driving the at least one vehicle on a toll-road, using the said platform/application.
[0023] Figure 1 illustrates a schematic block diagram depicting an environment for the implementation of a system 100 for generating a fee report, according to an embodiment of the present invention. For the sake of brevity, the system 100 for generating the fee report is hereinafter interchangeably referred to as the system 100.
[0024] In an embodiment, referring to Figure 1, the system 100 may be implemented between a server 102, a plurality of roadside receivers (RRs) 104a- 104b (hereinafter interchangeably referred to as the roadside receivers), a device 106 installed and in communication with at least one vehicle 108 (hereinafter interchangeably referred to as the vehicle), wherein the vehicle 108 may be moving or travelling on a toll-road 103.
[0025] In an embodiment, referring to Figure 1, the system 100 may include the vehicle 108 travelling on the toll-road 103 along with the device 106 installed in the vehicle 108. In some embodiments, the roadside receivers (RRs) 104a, 104b, and 104c installed in a vicinity of the toll-road 103 may detect and communicate with the device 106. Further, the RRs 104a, 104b, and 104c may transmit detected information to the server 102 for further processing. For the sake of brevity, only three RRs 104a, 104b, and 104c are depicted, it may be apparent that more than three RRs 104a, 104b, and 104c may be installed on the toll-road 103.
[0026] In an embodiment, the RRs 104a, 104b, and 104c may be installed alongside the toll-road 103. The RRs 104a, 104b, and 104c may be adapted to detect the device 106 installed in the vehicle 108, while the vehicle travels within a predefined range of the RRs 104a, 104b, and 104c. In an example, a first roadside receiver 104a may be adapted to detect the device 106 installed in the vehicle 108 within the predefined range. It may be apparent to an ordinary person skill in art to install more than one roadside receiver alongside the toll-road 103 within a predefined threshold distance (d). Thus, the installation of more than one roadside receiver alongside the toll-road 103, may be able to detect the device 106 installed in the vehicle 108, while the vehicle 108 travels throughout the toll-road 103. For instance, as the vehicle 108 approaches within the predefined range of the first roadside receiver 104a, thus, resulting in the first roadside receiver 104a detecting the device installed in the vehicle 108. Consequently, the server 102 in communication with the first roadside receiver 104a may receive a communication from the first roadside receiver 104a indicative of detection of the device 106 installed in the vehicle 108. Similarly, as the vehicle 108 approaches within the predefined range of each of the RRs 104a, 104b, and 104c, the server 102 may continuously receive the communication from a respective roadside receiver detecting the device 106. Thus, the server 102 in real-time may be aware of a location of the vehicle 108 travelling on the toll-road 103.
[0027] In an embodiment, the RRs 104a, 104b, and 104c may use wireless transmission to establish communication with the device 106 installed in the vehicle 108, such as, but not limited to, radio frequency identification (RFID) or Near Field Communication (NFC). In an example, the first roadside receiver 104a may be adapted to detect an identification signal via the wireless transmission from the device 106 installed in the vehicle 108, as the vehicle 108 passes or travels within the predefined range of the first roadside receiver 104b. In some embodiments, the RRs 104a, 104b, and 104c may be adapted to determine a device state input based on the detected identification signal. In an example, the device state input may indicate parameters associated with the device 106 installed in the vehicle 108 such as, but not limited to, an identification tag, a timestamp, and any other metadata associated with the device 106 installed in the vehicle 108. Thus, as the vehicle 108 travels on the toll-road 103 and approaches the RRs 104a, 104b, and 104c, each of the RRs 104a, 104b, and 104c may be adapted to detect the identification signal from the device 106 installed in the vehicle 108 within the predefined range to determine the device state input. Further, the RRs 104a, 104b, and 104c may be adapted to transmit the determined device state input to the server 102. The RRs 104a, 104b, 104c may be in communication with the server 102 via a wireless communication network. In an example, the wireless communication network may include wired networks, wireless networks, Ethernet AVB networks, or combinations thereof. The wireless network as appeared throughout the present disclosure may be a zig-bee network, a cellular telephone network such as 4G, 5G, an 802.11, 802.16, 802.20, 802.1Q, Wi-Fi, or a WiMax network. Further, the network may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols.
[0028] In an embodiment, the device 106 may be installed in the vehicle 108. The device 106 may indicate any logical circuitry implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Further, the device 106 may be adapted to transmit wireless signals including but not limited to, Radio Frequency Identification (RFID), Bluetooth, and Ultra-Wide Band (UWB) such that the RRs 104a, 104b, and 104c may be able to detect the device 106 installed in the vehicle 108 based on the transmitted wireless signals. Among other capabilities, the device 106 is adapted to fetch and execute computer-readable instructions and data stored in its memory. The device 106 may receive operating power via the vehicle 108 in which it is installed. Thus, the device 106 may provide the identification signal to the RRs 104a, 104b, and 104c related to the vehicle 104 in which it is installed. In the example, the identification tag may indicate a unique serial number associated with the device 106 installed in the vehicle 108.
[0029] In an example, the vehicle 108 initiates travelling on the toll-road 103 and is thus liable to pay “toll” or a toll-fee associated with travelling or using the toll-road 103. In the example, the toll-road 103 may be referred to any road interconnecting cities, intra-city for which the toll-fee are payable upon usage. Thus, the user may be required to pay the fees for travelling or driving the vehicle 108 on the toll-road 103. The toll-road 103 may be initiated from a particular juncture and may spread across miles, thus passing through cities and providing ease of commutation to the user. The toll-road 103 may include the toll gate 110. The toll gate 110 may indicate a physical location on the toll-road 103 where the vehicle 108 is required to pay the toll-fee or toll to pass through. In the example, the first roadside receiver 104a among the plurality of roadside receivers 104a, 104b, and 104c indicates an initial roadside receiver positioned at a geo-location on the toll-road 103. The geo-location may indicate a positional coordinate or position information of the plurality of roadside receivers 104a, 104b, and 104c. Accordingly, the geo-location of the first roadside receiver 104a may correspond to the beginning of the toll-road 103. Similarly, a second roadside receiver 104b among the plurality of roadside receivers 104a, 104b, and 104c may be positioned at the toll gate 110. Accordingly, the geo-location of the second roadside receiver 104b may correspond to the toll gate 110. In the example, the vehicle 108 travelling on the toll-road 103, upon passing through the toll gate 110 may be responsible for paying the toll-fee.
[0030] In an example, the fee report including the toll-fee may be generated upon the vehicle 108 passing through the toll gate 110 and consequently detected by the second roadside receiver 104b. In the example, the vehicle 108 before passing through the toll gate 110, travelled via the toll-road 103 and was accordingly detected by the first roadside receiver 104a at a first instance. The first instance may indicate an event at which the device 106 installed in the vehicle 108 is first detected upon arriving or travelling on the toll-road 103. Accordingly, the server 102 receives the device state input corresponding to the detection of the vehicle 108 by the first roadside receiver 104a. The server 102 may include (pre-stored) the geo-location of the first roadside receiver 104a. Consequently, the server 102 may be adapted to determine the starting point at which the vehicle initiated travelling on the toll-road 103. Further, in the example, as the vehicle 108 approaches in the predetermined range of the second roadside receiver 104b which is installed at the toll gate 110, the second roadside receiver 104b may be adapted to detect the device 106 installed in the vehicle 108. Thus, the server 102 may be adapted to receive the device state input corresponding to detection of the vehicle 108 from the second roadside receiver 104b. The server 102 includes (pre-stored) the geo-location of the second roadside receiver 104b. Consequently, the server 102 may be adapted to determine a distance travelled by the vehicle 108 on the toll-road 103 before crossing the toll gate 110. In the example, the distance may be calculated based on the starting point i.e., the first instance when the device 106 installed in the vehicle 108 was detected by the first roadside receiver 104a and a final instance when the device 106 was detected by the second roadside receiver 104b.
[0031] In the example, the server 102 may be configured with a predetermined rule corresponding to the toll-road 103. In a non-limiting example, the predetermined rule may indicate the fee associated with travelling on the toll-road 103, a variable fee in conjunction with the time-duration at which the toll-road 103 may be used for travelling, and alike. Thus, as the vehicle passes through the toll gate 110, the fee report is generated corresponding to the vehicle 108, such that the fee report provides the amount to be paid for travelling on the toll-road 103. In the example, the fee report is generated based on the determined distance and the predetermined rule. Further, the fee report may be sent as a notification to an application installed in a user device (not shown), a third-party application, and the vehicle 108. Furthermore, the generated fee report may be transmitted to a payment network such that the payment network enables financial transactions based on the generated fee report. Therefore, the user may be able to pay a true and correct amount, digitally, efficiently, and without human intervention upon usage of the toll-road 103. The forthcoming paragraphs discuss the implementation of the system in the server 102 in detail.
[0032] Figure 2 illustrates another schematic detailed block diagram of modules/software components of the system 100, according to an embodiment of the present invention.
[0033] In an embodiment, the system 100 may include the application 110a installed in the user device 110b and running on an operating system (OS) of the user device 110b that generally defines a first active user environment. The application 110a may be indicative of a software package that performs a specific function for an end user. The OS typically presents or displays the application through a graphical user interface (“GUI”) of the OS. Other applications may be running on the operating system of the user device 110b but may not be actively displayed. In an example, the user device 110b may be but is not limited to, a tablet PC, a Personal Digital Assistant (PDA), a smartphone, a palmtop computer, a laptop computer, a desktop computer, a server, a cloud server, a remote server, a communications device, a wireless telephone, or any other machine controllable through the wireless-network and capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. The application 110a installed in the user device 110b may be in communication with the server 102 via the wireless communication network. In an example, the wireless communication network may include wired networks, wireless networks, Ethernet AVB networks, or combinations thereof. The wireless network as appeared throughout the present disclosure may be a zig-bee network, a cellular telephone network such as 4G, 5G, an 802.11, 802.16, 802.20, 802.1Q, Wi-Fi, or a WiMax network. Further, the network may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols. In an alternative example, the user device 110b may be installed in the vehicle 108, thus providing the user of the vehicle 108 with the notification including the generated fee report.
[0034] In an embodiment, the server 102 may be a cloud IoT Core server which may be in communication with the RRs 104a, 104b, 104c and the application 110a installed in the user device 110b. In an example, the server 102 is adapted to generate the fee report using the device state input received from the RRs 104a, 104b, 104c. Further, the server 102 is adapted to identify which of the RRs 104a, 104b, 104c may be transmitting the device state input as each of the RRs 104a, 104b, 104c may be identified based on the unique identification number. The server 102 may be adapted to store in its memory the geo-location associated with the RRs 104a, 104b, 104c. The geo-location thus indicates the position information of the RRs 104a, 104b, 104c. In an example, the position information may indicate a placement coordinate such as a geographical location of the RRs 104a, 104b, 104c on the toll-road 103 and the identification number associated with each of the RRs 104a, 104b, 104c. Thus, the server 102 is adapted to determine the distance travelled by the vehicle 108 while travelling on the toll-road 103 based on the device state input being sent by the RRs 104a, 104b, 104c respectively and the associated geo-location.
[0035] Further, the server 102 may be adapted to provide the generated fee report in the form of the notification to the application 110a installed in the user device 110b. In an another example, the server 102 may be adapted to provide the generated fee report in the form of the notification to the third-party system 220.
[0036] Further, the server 102 may be adapted to receive and store a respective profile for the device 106 installed in the vehicle 108, via the application 110a. Thus, the server 102 may store information related to the device 106 such as, but not limited to, an identification tag associated with the device 106, a type of vehicle 108 in which the device 106 is installed, vehicle registration details, pollution certificate details, owner details, and any other user details. The server 102 may store information related to the device 106 as preconfigured information corresponding to the device 106. For example, upon manufacturing of the device 106, the server 102 may receive and store information related to the device 106.
[0037] In an example, the application 110a installed on the user device 110b may be used to provide and store the information related to the device 106, on the server. The application 110a may be connected to the server 102 upon inputting credentials associated with the respective profile. Upon connection, the application 110a may provide a view of the respective profile. Further, the credential may indicate a dedicated username and password corresponding to the respective profile. A user may be able to create the credentials for the respective profiles. Such that, the credentials are stored on the server 102 corresponding to the profile and upon inputting the credentials, the server 102 may be adapted to validate the credentials. In the example, upon successful validation of the credentials, the application 110a may be connected to the server 102 and the respective profile may be viewed on the user device 110b. The server 102 may be further adapted to send the notification associated with the device 106 to the application 110a.
[0038] In an embodiment, the server 102 may also transmit any interface such as, but not limited to, an HTML page which may be displayed on the user device 110b via the application 110a. The HTML page may be adaptive to display a list of devices associated with the profile and the generated fee report with respect to each of the device 106.
[0039] In an embodiment, the server 102 may include the modules/engines/units implemented with an AI module that may include a plurality of neural network layers. Examples of neural networks include, but are not limited to, convolutional neural network (CNN), deep neural network (DNN), recurrent neural network (RNN), and Restricted Boltzmann Machine (RBM). The learning technique is a method for training a predetermined target device (for example, a robot, or the server) using a plurality of learning data to cause, allow, or control the target device to make a determination or prediction. Examples of learning techniques include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. At least one of a plurality of CNN, DNN, RNN, RMB models and the like may be implemented to thereby achieve execution of the present subject matter’s mechanism through an AI model. A function associated with AI may be performed through the non-volatile memory, the volatile memory, and the processor. The processor may include one or a plurality of processors. At this time, one or a plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU). One or a plurality of processors control the processing of the input data in accordance with a predefined operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory. The predefined operating rule or artificial intelligence model is provided through training or learning. In one example, the server 102 with the AI module may be adapted to generate the fee report.
[0040] In an embodiment, referring to Figures 1 and 2, the server 102 may include, but is not limited to, a processor 202, memory 204, modules 206, and data 208. The modules 206 and the memory 204 may be coupled to the processor 202.
[0041] The processor 202 can be a single processing unit or several units, all of which could include multiple computing units. The processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 202 is adapted to fetch and execute computer-readable instructions and data stored in the memory 204. At this time, one or a plurality of processors may be a general purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU). One or a plurality of processors control the processing of the input data in accordance with a predefined operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory. The predefined operating rule or artificial intelligence model is provided through training or learning. A detailed explanation of each of the server 102 as shown in figures 1 and 2 will be explained in detail in the forthcoming paragraphs. Further, the working of the system 100 will be explained with respect to figures 1 and 2. The reference numerals are kept the same in the disclosure wherever applicable for ease of explanation.
[0042] The memory 204 may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and/or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The geo-location or the position information associated with the RRs 104a, 104b, and 104c may be stored in the memory 204.
[0043] The modules 206, amongst other things, include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement data types. The modules 206 may also be implemented as, signal processor(s), state machine(s), logic circuitries, and/or any other device or component that manipulates signals based on operational instructions.
[0044] Further, the modules 206 can be implemented in hardware, instructions executed by a processing unit, or by a combination thereof. The processing unit can comprise a computer, a processor, a state machine, a logic array, or any other suitable devices capable of processing instructions. The processing unit can be a general-purpose processor which executes instructions to cause the general-purpose processor to perform the required tasks or, the processing unit can be dedicated to performing the required functions. In another embodiment of the present disclosure, the processor 202 via the modules 206 is configured to execute machine-readable instructions (software) which perform the working of the system 100 within the scope of the present invention as described in forthcoming paragraphs.
[0045] In an embodiment, the modules 206 may include a device management module 210, a receiving module 212, a determining module 214, a generating module 216, and a transmitting module 218. The device management module 210, the receiving module 212, the determining module 214, the generating module 216, and the transmitting module 216 may be in communication with each other. The data 208 serves, amongst other things, as a repository for storing data processed, received, and generated by one or more of the modules 206.
[0046] Referring to Figure 1 and Figure 2, the device management module 210 may be adapted to manage the device 106 which may be communicating with the RRs 104a, 104b, and 104c. The device management module 210 may be adapted to map each end user information associated with the device 106 such as, but not limited to, the identification tag associated with the device 106, type of vehicle 108 in which the device 106 is installed, vehicle registration details, pollution certificate details, owner details, and any other user details. Further, the device management module 210 may be adapted to store the end user information in the memory 204. Further, the end-user information associated with the device 106 may be viewed on an end-user interface such as the application 110a installed in the user device 110b. In some embodiments, the device management module 210 may be adapted to receive via the application 110a installed on the user device 110b, the credentials of the respective profile associated with the device. Further, the device management module 210 may be adapted to determine whether the credentials are valid based on predefined rules. In an example, the predefined rules may indicate an information stored in the memory 204 of the server 102 such as but not limited to, the credentials stored, and respective profiles storing information related to the device 106. The device management module 210 may be in communication with the receiving module 212.
[0047] In an embodiment, the receiving module 212 may be adapted to receive the device state input corresponding to detection of the vehicle 108 from the RRs 104a, 104b, and 104c. In an example, the device state input indicates parameters associated with the device 106 installed in the vehicle 108. In the example, the device state input may include the identification tag, the timestamp, and metadata of the device 106 installed in the vehicle 108.
[0048] Further, the receiving module 212 may be adapted to identify the RRs 104a, 104b, and 104c sending the device state input. In an example, the RRs 104a, 104b, and 104c sending the device state input to the server 102 may be identified based on the unique identification number associated with each of the RRs 104a, 104b, and 104c and stored in the memory 204. In the example, the receiving module 212 may be adapted to obtain the corresponding geo-location of the RRs 104a, 104b, and 104c such that the geo-location indicates the placement coordinate and the identification number associated with the RRs 104a, 104b, and 104c. Further, in the example, the receiving module 212 may be configured to receive the device state input at the first instance from the first roadside receiver 104a. Similarly, the receiving module 212 may be configured to receive the device state input at the second instance from the second roadside receiver 104b. The device management module 210 and the receiving module 212 may be in communication with the determining module 214.
[0049] In some embodiments, the determining module 214 may be adapted to determine the distance travelled by the vehicle 108 between the geo-location corresponding to the first roadside receiver 104a and the geo-location corresponding to the second roadside receiver 104b based on the device state input received from the plurality of roadside receivers 104a, 104b, and 104c.
[0050] In some embodiments, the determining module 214 may be configured to obtain the corresponding geo-location of the first roadside receiver 104a and the corresponding geo-location of the second roadside receiver 104b. Further, the determining module 214 may be configured to compare the corresponding geo-location of the first roadside receiver 104a and the second roadside receiver 104b respectively. In an example, the comparison indicates a range or the distance between the first roadside receiver 104a and the second roadside receiver 104b.
[0051] The determining module 214 may be configured to obtain the predefined rules corresponding to the second roadside receiver 104b. In the example, the predefined rules may indicate the toll-fee associated with the toll-road 103. Furthermore, determining module 214 may be configured to determine the distance between the first roadside receiver 104a and the second roadside receiver 104b based on the predefined rules and the comparison. The device management module 210, the receiving module 212, and the determining module 214 may be in communication with the generating module 216.
[0052] In an embodiment, the generating module 216 may be configured to generate the fee report corresponding to the vehicle 108 based on the determined distance and the predetermined rule. The device management module 210, the receiving module 212, the determining module 214, and the generating module 216 may be in communication with the transmitting module 218.
[0053] In an embodiment, the transmitting module 218 may be configured to send the notification associated with the device 106, to the application 110a. In an example, the notification may include the generated fee report. In the example, Further, the transmitting module 216 may be adapted to provide the generated fee report to the vehicle 108 or/and the third-party system 220. In an example, the third-party system 220 may indicate any other platform or application which may be subscribed to the server 102 to receive the fee report.
[0054] Further, the transmitting module 218 may be configured to send the generated fee report to the payment network such that the payment network enables financial transactions based on the generated fee report. In an example, the user may be able to pay the fee using the payment network.
[0055] Figure 3 illustrates a process flow of a method 300 for traffic management, according to an embodiment of the present invention. The method 500 may be a computer-implemented method executed, for example, by the server 102 and the modules 206. For the sake of brevity, the constructional and operational features of the system 100 that are already explained in the description of Figure 1 and Figure 2 are not explained in detail in the description of Figure 3.
[0056] At step 302, the method 300 may include receiving, by the server 102, from the plurality of roadside receivers 104a, 104b, and 104c positioned at different geo-locations on the toll road 103, the device state input corresponding to detection of the vehicle 108. In an example, the plurality of roadside receivers 104a, 104b, and 104c comprises of the first roadside receiver 104a and the second roadside receiver 104b.
[0057] At step 304, the method 300 may include determining, by the server 102, the distance travelled by the vehicle 108 between the geo-location corresponding to the first roadside receiver 104a and the geo-location corresponding to the second roadside receiver 104b based on the device state input received from the plurality of roadside receivers 104a, 104b, and 104c.
[0058] At step 306, the method 300 may include generating, by the server 102, the fee report corresponding to the vehicle 108 based on the determined distance and the predetermined rule associated with the toll-road 103.
[0059] Figure 4 illustrates an exemplary use case of the system 100, according to an embodiment of the present invention.
[0060] In this scenario 400, the vehicle 108, to avoid the toll gate 110, temporarily diverts onto an alternative road 402 and later rejoins the toll-road 103 at a different point. As depicted in Figure 4, the vehicle 108 follows the route of the alternative road 402 and then merges back onto the toll-road 103. Although the second roadside receiver 104b situated at the toll gate 110 might not detect the vehicle 108 due to the vehicle 108 taking the alternative road 402 thus the vehicle 108 remains outside the predetermined range of the second roadside receiver 104b. However, upon rejoining the toll-road 103, a third roadside receiver 104c positioned on the toll-road 103 may detect the vehicle 108. Subsequently, the device state input may be transmitted to the server 102. Consequently, the third roadside receiver 104c captures the vehicle's presence during this second encounter and acts comparably to the second roadside receiver 104b. This ensures that the server 102 generates an accurate fee report, taking into account the vehicle's 108 journey on the toll-road 103 and its passage past the toll gate 110. In this manner, the vehicle 108 is unable to avoid paying the toll fee.
[0061] The present invention provides various advantages:
• The present invention provides toll gates without human intervention. Thus, reducing operational costs and hazards.
• The present invention ensures that every vehicle travelling on the toll-road pays a toll-fee.
• The present invention ensures traffic management as the barriers may be removed from the toll gates. Thus, reducing stoppages on the toll gates and subsequently, the traffic congestion may be reduced.
• The present invention ensures the user pays only for the distance covered on the toll-road.

[0062] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
[0063] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. , C , Claims:WE CLAIM:
1. A method (300), comprising:
receiving (302), by a server, from a plurality of roadside receivers positioned at different geo-locations on a toll road, a device state input corresponding to a detection of at least one vehicle, wherein the plurality of roadside receivers comprises at least a first roadside receiver and a second roadside receiver;
determining (304), by the server, a distance travelled by the at least one vehicle between a geo-location corresponding to the first roadside receiver and a geo-location corresponding to the second roadside receiver based on the device state input received from the plurality of roadside receivers; and
generating (306), by the server, a fee report corresponding to the at least one vehicle based on the determined distance and a predetermined rule.

2. The method (300) as claimed in claim 1, wherein the corresponding geo-location of each of the plurality of roadside receivers is prestored in the server.

3. The method (300) as claimed in claim 1, wherein determining the distance travelled by the at least one vehicle, comprises:
obtaining the corresponding geo-location of the first roadside receiver;
obtaining the corresponding geo-location of the second roadside receiver;
comparing the corresponding geo-location of the first roadside receiver and the second roadside receiver respectively, wherein the comparison indicates the range/distance between the first RR and the second RR;
obtaining the predefined rules corresponding to the second roadside receiver, wherein the predefined rules indicate a toll-fee associated with a toll-road corresponding to the geo-location of the second roadside receiver; and
determining the distance between the first roadside receiver and the second roadside receiver based on the predefined rules and the comparison.

4. The method (300) as claimed in claim 1, further comprising:
sending, by the server, the generated fee report to a payment network such that the payment network enables financial transaction based on the generated fee report.

5. The method (300) as claimed in claim 4, further comprising:
sending a notification to one of the third party, an application, and the at least one vehicle, wherein the notification comprises the generated fee report associated with the at least one vehicle.

6. The method (300) as claimed in claim 1, wherein the geo-location includes longitude, latitude, and altitude information.

7. The method (300) as claimed in claim 1, wherein the first roadside receiver indicates an initial roadside receiver adapted to detect the at least one vehicle at a first instance and the second roadside receiver indicates a toll-gate roadside receiver adapted to detect the at least one vehicle at a final instance.

8. A system (100) comprises:
a memory (204);
at least one processor (202) communicably coupled to the memory (204), the at least one processor (202) is configured to:
receive from a plurality of roadside receivers (104a-104c) positioned at different geo-locations on a toll road (103), a device state input corresponding to detection of at least one vehicle (108), wherein the plurality of roadside receivers (104a-104c) comprises at least a first roadside receiver and a second roadside receiver;
determine a distance travelled by the at least one vehicle (108) between a geo-location corresponding to the first roadside receiver and a geo-location corresponding to the second roadside receiver based on the device state input received from the plurality of roadside receivers; and
generate a fee report corresponding to the at least one vehicle (108) based on the determined distance and a predetermined rule.

9. The system (100) as claimed in claim 8, wherein the corresponding geo-location of each of the plurality of roadside receivers is prestored in the server.

10. The system (100) as claimed in claim 7, wherein to determine the distance travelled by the at least one vehicle, the at least one processor is configured to:
obtain the corresponding geo-location of the first roadside receiver;
obtain the corresponding geo-location of the second roadside receiver;
compare the corresponding geo-location of the first roadside receiver and the second roadside receiver respectively, wherein the comparison indicates the range/distance between the first RR and second RR;
obtain the predefined rules corresponding to the second roadside receiver, wherein the predefined rules indicate a toll-fee associated with a toll-road corresponding to the geo-location of the second roadside receiver; and
determine the distance between the first roadside receiver and the second roadside receiver based on the predefined rules and the comparison.

11. The system (100) as claimed in claim 8, the at least one processor is further configured to:
send the generated fee report to a payment network such that the payment network enables financial transaction based on the generated fee report.

12. The system (100) as claimed in claim 11, the at least one processor is further configured to:
send a notification to one of the third party, an application, and the at least one vehicle, wherein the notification comprises the generated fee report associated with the at least one vehicle.

13. The system (100) as claimed in claim 8, wherein the geo-location includes longitude, latitude, and altitude information.

14. The system (100) as claimed in claim 8, wherein the first roadside receiver indicates an initial roadside receiver adapted to detect the at least one vehicle at a first instance and the second roadside receiver indicates a toll-gate roadside receiver adapted to detect the at least one vehicle at a final instance.