Universal Object Sharing Platform with Cloud APIs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing object-sharing technologies require significant capital investment and resource expenditure for developing proprietary hardware and software solutions, leading to redundant efforts and increased costs, as each company must create custom solutions for intelligent hardware, cloud connectivity, and mobile applications, posing a financial risk until market acceptance is confirmed.
Innovation Solution
A universal and open platform for object sharing that allows providers to quickly develop and deploy object-intelligence, cloud connectivity, and data analytics, eliminating redundant efforts by using a managed service with cloud-based services and APIs, enabling field support and integration with a pre-developed cloud platform, suitable for various vertical markets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each company develops proprietary hardware and software solutions for object sharing, then the object-sharing platform can be customized and adapted to specific market needs, but the development costs and time are significantly increased due to redundant efforts
Solution Approach 1:
The system is segmented into independent layers: a standardized hardware layer with embedded intelligence that can be used across different object types, and a software layer that provides object-specific functionality. This allows the hardware platform to be reused while software is customized for different vertical markets.
Solution Approach 2:
A universal hardware platform with embedded intelligence, cloud connectivity, and standard interfaces is developed that can serve multiple object types and vertical markets. This eliminates redundant hardware development while maintaining adaptability through software configuration and modular add-ons.
2Reliability
If proprietary intelligent hardware solutions are developed for each object type, then the object can communicate with cloud-based services and mobile applications, but the capital investment and resource expenditure are significantly increased
Solution Approach 1:
Instead of developing unique hardware for each object, a standardized hardware template or 'copy' is created that can be replicated across different object types. This template includes pre-integrated intelligence, sensors, and communication modules that ensure reliable cloud connectivity without requiring significant capital investment for each new object type.
Solution Approach 2:
The system uses a modular hardware architecture where standard components can be discarded and recovered across different object deployments. Common elements like processors, communication modules, and power management systems are reused across multiple object types, reducing overall capital investment.
3Adaptability or versatility
If multiple companies pursue the same object-sharing market with proprietary solutions, then each company can optimize for their specific business model, but the development cycles are extended due to redundant testing and debugging
Solution Approach 1:
The hardware platform is pre-configured with intelligence, cloud connectivity, and basic functionality before deployment. This preliminary preparation allows companies to skip extensive testing and debugging of core functions, reducing development cycles while maintaining the ability to customize business-specific features.
Solution Approach 2:
Common development tasks such as hardware testing, cloud integration, and security validation are merged into a shared validation process. This allows multiple companies to benefit from collective testing efforts while maintaining the flexibility to optimize for their specific business models through software configuration.
Data Source
AI summary
A system is configured to provide managed services for deployment of shared tangible objects by an operator. The system includes cloud resources provided by the system administrator. In one embodiment, the cloud resources include a sharable-object command module configured to communicate signals employed in activating shared tangible objects for use when the end user is successfully authorized by the device activation module. The system includes an API provided by the system administrator. The API is configured to facilitate a communication of object activation signals from the sharable-object command module to allow the end user to use the shared tangible object. The same API is employed to facilitate the communication of object activation signals for different types of shared tangible objects that can be provided in different vertical markets.