Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. An Open Specification: Open Connectivity Foundation
  2. An Open Source Implementation for OCF members: IoTivity
  3. A membership driven certification program:  OCF certification

We analyzed a wide variety of Connected OCF's initial efforts to venture into the Connected Vehicle space involved analysis of 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. We Based on the above, we consolidated the list of use cases to , under the following broad categories.

  1. Home Energy Management
  2. Security System Interaction
  3. Vehicle Location
  4. Smart Home device status
  5. Vehicle Control from Smart Device
  6. Smart Device Control from Vehicle
  7. Electric Vehicle Time-of-Use Charging
  8. Entertainment
  9. Third party application service integrations based on the above use cases

While most of these use cases are realized through closed collaborative efforts, Samsung Open Source Group and Jaguar Land Rover Open Source Technology Center, followed an open collaboration model under the Genivi Alliance Incubator projects initiative. We Using completely open source software and commodity off-the-shelf hardware, we were able to realize the use cases in bold, with minimal resources and a short duration.

...

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/duo polies. 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.

 

RoleResponsibilitiesExpectations

Service Provider

(Cloud, Web, Network)

Hosts the web service   infrastructure backbone

Provides access via API and AppsEnable authenticated access to the infra.

Extending service into the IoT network.

Minimal/No changes in existing workflows.

More user engagement from multiple sources.

Customers

Consume Services & use 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.

Application Developers

Innovate and delight customers with

New {Web services & IoT devices} Apps

Maximize Asset Reuse

Simpler development

New revenue streams

Auto makers & Tier 1Manufacture at Scale

Compliance to standards (where applicable)

 Increased user adoption 

Feature Differentiation

...