Vehicle Data Feed Server for Multi-Brand Real-Time Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle data collection and distribution methods are inefficient, primarily handled by individual automakers on a case-by-case basis, lacking a standardized and scalable solution for collecting and sharing data across multiple vehicle brands and user groups.
Innovation Solution
A vehicle data feed service platform is established to collect real-time data from network-connected vehicles and provide it to client groups with varying access levels, using a third-party managed system that consolidates data from multiple brands, enabling diverse applications such as concierge services, diagnostics, and fleet management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If individual automakers collect and share vehicle data on a case-by-case basis, then each automaker can control data access for its own vehicles, but the system lacks scalability and efficiency for multi-brand data sharing
Solution Approach 1:
The patent introduces a third-party server system that acts as an intermediary between multiple automakers and data clients. This central platform receives data from various vehicle brands and distributes it to authorized clients, enabling efficient multi-brand data sharing without requiring individual automaker-by-automaker arrangements. The intermediary handles authentication, data routing, and access control centrally, improving both productivity and adaptability.
Solution Approach 2:
The server system is designed as a universal platform that can handle data from multiple vehicle brands and serve multiple types of data clients simultaneously. It provides standardized interfaces for data collection, storage, and distribution that work across different automakers and client types (e.g., fleet operators, service centers, researchers), making the system highly adaptable and scalable.
2Adaptability or versatility
If a centralized platform collects data from multiple vehicle brands, then data sharing efficiency and scalability improve, but system complexity and security management challenges increase
Solution Approach 1:
The patent segments the centralized platform into distinct functional modules: data reception modules for different automakers, data storage modules organized by vehicle identifier, authentication modules for different client types, and distribution modules. This modular architecture reduces overall system complexity by allowing each component to be developed, maintained, and scaled independently while working together in a unified system.
Solution Approach 2:
The system implements local quality control by providing different levels of access and different data formats to different client types based on their specific needs. Fleet operators receive different data than service centers, and each client type gets authenticated and authorized according to its specific requirements, simplifying security management through differentiated access control.
3Reliability
If access levels are assigned to different user credentials for vehicle data, then data security and privacy are improved, but authentication and authorization complexity increases
Solution Approach 1:
The system performs preliminary authentication and authorization actions during client registration and data request initiation. User credentials are verified and access levels are determined before any data transfer occurs, preventing unauthorized access while maintaining a streamlined process. The authentication framework is established upfront and reused for subsequent data access requests.
Solution Approach 2:
The patent implements a credential copying mechanism where authorized clients can generate subordinate credentials that inherit parent credential permissions. This allows fleet operators to create user accounts for their employees with appropriate access levels without requiring separate authentication agreements with each user, simplifying the authentication system while maintaining security through hierarchical credential management.
Data Source
Figure 1A
Figure 1B
Figure 2A
AI summary
This application is directed to communicating vehicle data via a vehicle data feed server that is communicatively coupled to a plurality of vehicles. A plurality of credentials and associated access levels are stored in a database of the vehicle data feed server. The vehicle data feed server receives a plurality of real-time vehicle data flows from the vehicles. These real-time vehicle data flows are optionally associated with the credentials based on the associated access levels. Upon receiving from a user of a client device a user credential and a vehicle data request, the vehicle data feed server determines whether the user is authorized to access vehicle data that is associated with the user credential and includes a subset of the real-time vehicle data flows. The subset of the real-time vehicle data flows is forwarded to the client device when the user is authorized to access the vehicle data.