...
The Open Connectivity Foundation
The Open Connectivity Foundation (OCF), founded in 2014, is a global consortium of leading more than 200 member companies, focused on creating a standard for interoperable devices and services was founded in 2014single open specification to help assure secure interoperability between devices for consumers, business, and industry. The OCF approach has three key deliverables:
a. An Open Specification:
...
b. An Open Source Reference Implementation
...
of the OCF
...
Specifications: IoTivity
c. A
...
vendor neutral certification program: OCF certification
OCF's initial efforts to venture into the Connected Vehicle space involved analysis of the Connected the "Connected Vehicle – Smart Home" crossover use cases based on consumer interests and strategy reports. We also took a look at the contemporary demonstrations shown in trade shows. Based on the above, we consolidated the list of use cases, consolidated the list of use cases under the following broad categories.
- Home Energy Management
- Security System Interaction
- Vehicle Location
- Smart Home device status
- Vehicle Control from Smart Device
- Smart Device Control from Vehicle
- Electric Vehicle Time-of-Use Charging
- Entertainment
- Third party application service integrations
While most of these solutions are realized through joint collaborative efforts between industry partners, there is, in general, a lack of open source alternatives which stifles innovation. Samsung Open Source Group and Jaguar Land Rover Open Source Technology Center, followed an open collaboration model under the Genivi Alliance Incubator projects initiative. One of the key objectives of this partnership was to use completely open source software and commodity off-the-shelf hardware, to realize realise the use cases (in bold), with minimal resources and time.
...
We understood that, for an IoT ecosystem to flourish, the architecture should be flexible enough for the key stakeholders to bring in their value proposition and make it easy for consumption by the rest of the ecosystem. Early adopters stand to gain significantly in such an ecosystem play and this typically tends to create ecosystem mono/duopolies. From the beginning, our goal was to identify the key stakeholders of the IoT ecosystem and provide an architecture that helps them integrate their existing solutions/software stacks, with as little friction as possible. We identified the following limited roles and expectations.
...
Service Provider
(Cloud, Web, Network)
...
Hosts the service infrastructure backbone
Enable authenticated access to the infra.
...
Minimal/No changes in existing business models (non-disruptive).
Support existing legacy services.
Extending service into the IoT network.
More user engagement from multiple sources.
...
Consume Services & IoT Devices
Provide credentials for privacy and security
...
Zero/Minimal Setup overhead
Ease of Use of Products & Services
Cost and Time savings with more personalization.
New experiences in doing day to day activities.
...
Innovate and delight customers with
New {Web services & IoT devices} Apps
...
Maximize Asset Reuse
Simpler development
New revenue streams
...
Compliance to standards (where applicable)
...
Service providers hosting the infrastructure expect minimal changes to the existing investments but like to enable new revenue streams by extending their services into the IoT network. Customers expect new services and experiences with zero setup overhead. Application developers are looking to leverage their existing assets and generate more user engagement. This is in addition to the expectations from Automakers and Suppliers.
6.6.3 How RVI models Vehicle Information as a Spec.
...