Providing data management as-a-service
US-2021349657-A1 · Nov 11, 2021 · US
US12362964B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12362964-B2 |
| Application number | US-202318120760-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 13, 2023 |
| Priority date | May 19, 2022 |
| Publication date | Jul 15, 2025 |
| Grant date | Jul 15, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for collecting telematics data from telematics devices are provided. A fleet management server includes a first and second data store operable to store a first and second set of telematics data associated with a first and second group of telematics devices. A plurality of gateway servers includes a first and second group of gateway servers in communication with the first and second group of telematics devices. The first and second group of gateway servers include at least one common gateway server. A unified downloader is operable to establish a communication channel between each gateway server in the first and second group of gateway servers and the unified downloader such that a single communication channel is established to each common gateway server. The communication channels can be multiplexed and transport asynchronous streams of telematics data. An event bus registers event records for the fleet management and gateway servers.
Opening claim text (preview).
The invention claimed is: 1. A method for collecting telematics data from a plurality of telematics devices, the method comprising: providing, at a plurality of fleet management servers, a plurality of data stores, each data store associated with at least one telematics device, each data store operable to store a set of telematics data associated with the at least one telematics device; detecting, at a gateway server, a connection by a telematics device to the gateway server; registering, at an event bus in communication with the gateway server, an event record indicating that the telematics device is connected to the gateway server; for each fleet management server having at least one data store associated with the telematics device: receiving, at the fleet management server, the event record from the event bus; updating, at the fleet management server, a mapping of the plurality of telematics devices to the plurality of gateways based on the event record; identifying, at the fleet management server, the gateway server in communication with the telematics device based on the mapping; receiving, at the fleet management server, a set of telematics data associated with the telematics device from the gateway server; and storing, at the at least one data store, the set of telematics data associated with the telematics device. 2. The method of claim 1 , further comprising: identifying, based on the mapping, at least one gateway server connected to the fleet management system that is not connected to any telematics devices associated with any data stores at the fleet management system; and terminating a communication channel between the fleet management server and the gateway server. 3. The method of claim 1 , further comprising: determining whether the fleet management server is connected to the gateway server; and in response to determining that that the fleet management server is not connected to the gateway server, establishing a communication channel between the fleet management server and the gateway server. 4. The method of claim 3 , wherein the communication channel is multiplexed so that telematics data associated with at least two data stores at the fleet management server are receivable through the same communication channel. 5. The method of claim 1 , wherein the event record comprises a timestamp representing when the connection by the telematics device to the gateway server was established. 6. The method of claim 1 , wherein the gateway server is a second gateway server, the event record is a second event record, and the method further comprises: prior to detecting the connection by the telematics device to the second gateway server, detecting, at a first gateway server, a connection by the telematics device to the first gateway server; registering, at the event bus, a first event record indicating that the telematics device is connected to the first gateway server; and identifying, at the fleet management server, the second gateway server in communication with the telematics device based on the first and second event records. 7. The method of claim 1 , further comprising: receiving, at each fleet management server, a plurality of event records from the event bus, each event record indicating that one telematics device is connected to one gateway server. 8. The method of claim 1 , further comprising: prior to receiving the set of telematics data associated with the telematics device from the gateway server at the fleet management server, determining that the at least one data store has permission to receive the set of telematics data associated with the telematics device based on another event record registered at the event bus. 9. The method of claim 1 , wherein the plurality of telematics devices is installed in a plurality of vehicles, and the telematics data comprises vehicle data collected from the plurality of vehicles. 10. A non-transitory computer readable medium having instructions stored thereon executable by at least one processor to implement a method for collecting telematics data from a plurality of telematics devices, the method comprising: providing, at a plurality of fleet management servers, a plurality of data stores, each data store associated with at least one telematics device, each data store operable to store a set of telematics data associated with the at least one telematics device; detecting, at a gateway server, a connection by a telematics device to the gateway server; registering, at an event bus in communication with the gateway server, an event record indicating that the telematics device is connected to the gateway server; for each fleet management server having at least one data store associated with the telematics device: receiving, at the fleet management server, the event record from the event bus; updating, at the fleet management server, a mapping of the plurality of telematics devices to the plurality of gateways based on the event record; identifying, at the fleet management server, the gateway server in communication with the telematics device based on the mapping; receiving, at the fleet management server, a set of telematics data associated with the telematics device from the gateway server; and storing, at the at least one data store, the set of telematics data associated with the telematics device. 11. A system for collecting telematics data from a plurality of telematics devices, the system comprising: a plurality of fleet management servers comprising a plurality of data stores, each data store associated with at least one telematics device, each data store operable to store a set of telematics data associated with the at least one telematics device; a plurality of gateway servers in communication with the plurality of telematics devices; and an event bus in communication with the plurality of gateway servers and the plurality of fleet management servers, the event bus operable to register a plurality of event records; wherein, in operation: a gateway server detects a connection by a telematics device to the gateway server; the event bus registers an event record indicating that the telematics device is connected to the gateway server; for each fleet management server having at least one data store associated with the telematics device, the fleet management server: receives the event record from the event bus; updates a mapping of the plurality of telematics devices to the plurality of gateways based on the event record; identifies the gateway server in communication with the telematics device based on the mapping; receives a set of telematics data associated with the telematics device from the gateway server; and stores the set of telematics data associated with the telematics device at the at least one data store. 12. The system of claim 11 , wherein in operation, the fleet management server: identifies, based on the mapping, at least one gateway server connected to the fleet management system that is not connected to any telematics devices associated with any data stores at the fleet management system; and terminates a communication channel between the fleet management server and the gateway server. 13. The system of claim 11 , wherein in operation, the fleet management server: determines whether the fleet management server is connected to the gateway server; and in response to determining that that the fleet management server is not connected to the gateway server, establishes a communication channel between the fleet management server and the gateway server. 14. The system of claim 13 , wherein the communication ch
the transportation system being a vehicle · CPC title
Arrangements for connecting between networks having differing types of switching systems, e.g. gateways · CPC title
Grouping or aggregating service requests, e.g. for unified processing · CPC title
Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54) · CPC title
Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.