DT has the ambition to build a smart home ecosystem. We see an urgent need for standardization. DT wants to share its view on standardizing components of the Smart Home and our requirements to better support the service provider buisness model

1. Building a Smart Home Ecosystem
Urgent need for Standardization
Carsten Steigleder
December, 2012

2. The QIVICON Concept.
An open Partner Ecosystem based on the QIVICON Platform.
Partner Ecosystem
End-customer relationship Partner Partner Partner
Developer Developer Developer
Energy Health
Home automation Security Multimedia in-house Portal incl. Shop SDK/
distribution
eMobility
QIVICON Box
Backend Configuration &
Basic Client
QIVICON Platform
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 2

3. Use of Standards.
QIVICON believes in standards and builds on proven and
standardized components.
Textbox Headline Standards Landscape
WAN home
ACS 3 network
1 2 4
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 3

4. Standardization.
In DT’s view, standardization means …
Market Standardization  DT has the ambition to become a leading
Smart Home player

 De-facto standard
 Established through market power  Alone, DT is not strong enough

Industry alignment &  DT actively shares and discusses its
Ecosystem development requirements with the industry
Key market makers share, discuss and

  DT is committed to create global
align on requirements
involvement across different industries
Industry Standardization through  DT is actively involved in SDO work
Standards Developing Organizations
 Process of developing and creating
 DT investigates where and how to

consensus around technical standards achieve results in the area of Smart Home
most efficiently
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 4

5. Pain Points.
DT sees three areas in need for standardization. In-house
Communication Technologies is the most urgent area.
Prio A Prio B Prio C
In-house Communication
Device Profiles Data Formats
Technologies

 In-house communication 
 QIVICON gives developers 
 Data exchange within the home
technologies are not a access to device types and their / non-IP devices (e.g. PV,
differentiator functionalities – across different central heating, Combined heat
manufacturer and individual and power unit)

 The different and non- devices
compatible technologies hinder 
 Data exchange with the outside
the mass market development 
 Need for a common framework world (e.g. tariff information,
 Currently available that categorizes devices and smart meter, load curve)
 their functionalities (device
technologies do not meet our abstraction)
requirements
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 5

6. Shortcomings.
In-house protocols are a mess. The current situation is a constraint
to the development of the Smart Home market.
 Protocols do not meet basic requirements in terms of, e.g.
- Security: None fully met our security requirements
- Interoperability: Also within one technology not guaranteed
- Interference: Many protocols have significant interference issues with other wireless
technologies (e.g. WiFi, LTE 800)
 Potential partners do not know which protocol will become the prevalent standard and
therefore hesitate to invest
 The hardware remains expensive as protocol owners cooperate exclusively with single chip
manufacturer and protect their proprietary eco-systems
Missing of “Gold-Standard”, results in major barriers for mass-market adoption.
In the mid- and long-term, standardization is strongly needed.
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 6

7. Requirements.
The technology needs to not only meet basic technical
requirements, but also support the different business models.
Requirements supporting the different
Basic technical requirements
business models
Security
Security 
 Easy and consistent pairing procedures across different
Easy and consistent pairing procedures across different
 Main concerns of potential Smart Home customers
 Main concerns of potential Smart Home customers
OEMs
OEMs
are security and privacy.
are security and privacy. Pre/Remote-pairing

 Pre/Remote-pairing
 DT considers security and privacy to be one of its
 DT considers security and privacy to be one of its
key differentiators.
key differentiators. 
 Eco-system certification on top of technologies
Eco-system certification on top of technologies
 Smart Grid and Ambient Assisted Living use cases
 Smart Grid and Ambient Assisted Living use cases 
 Rights management for devices (e.g. device lock,
Rights management for devices (e.g. device lock,
require a high level of security
require a high level of security access to functionalities depending on role)
access to functionalities depending on role)
Interoperability
Interoperability Many requirements more

 Many requirements more
 Full interoperability within one technology among
 Full interoperability within one technology among
different manufacturers is crucial
different manufacturers is crucial
Latency
Latency
 Current wired solutions are the benchmark
 Current wired solutions are the benchmark
Approx. 50% of DT’s requirements met 0% of DT’s requirements met
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 7

8. Fram
General Approach. e
HGI work of
cont a
ribut joint
Re-thinking in-house communication technologies means … ion
… to look at the entire device lifecycle end-to-end …
Marketing De-
Development Production & Sales Configuration Operation commissioning
 Easy access to  Availability of  Platform  Inclusion &  Reliable & stable  Decommissioning
standards, chipset / certification configuration of performance supported
technologies software stack  Co-branding devices  Proven security  …
and requirement  Testing support  User guide
list  Sales support  Network
 Access to  Device … … Management
development certification
 Remote access
tools … to device
 Access to joined  Upgrading
test beds  Policy control
 …  Global usage
… and to involve all relevant players into the discussion.
Smart Home Platform Operator who Service Provider who develop and sell Equipment manufacturer who design
manage infrastructure, define local Smart Home products based on available and manufacture Smart Home devices
gateways and enable Smart Home service platforms (e.g. sensors, actuators)
provider
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 8

9. Device Profiles.
Developers want to access devices and their basic functionalities –
independent of the manufacturer and the individual device type.
Partners & Developers
 Making a device available to SW developing
partners, QIVICON adds the device and its
QIVICON: Platform, SDK and Home Base functionalities to the QIVICON SDK and
platform.
QIVICON Device Manag-
 HW providing partners provide this information
ement & Abstraction
during the hardware certification.
Homematic ZigBee Others  In alignment with the partners, QIVICON makes
available with its SDK a selected portfolio of
devices.
 QIVICON expects to continue structuring and
managing this device data for the near future.
 Once the number of device increases,
Devices & their functionalities standardization is urgently needed.
The Internet of Things requires a standardized device data framework with which platform
provider can manage, abstract and give access to devices and their functionalities.
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 9

10. Open Questions.
We are happy to discuss.
In-house Communication Technologies Device Profiles

 What is the best approach to make technology
What is the best approach to make technology 
 What is the best approach to develop such a
What is the best approach to develop such a
providers deliver better against our needs?
providers deliver better against our needs? standardized device data framework?
standardized device data framework?

 How to best interact with providers of in-house
How to best interact with providers of in-house 
 Device management and abstraction is where the
Device management and abstraction is where the
communication technologies (e.g. ZigBee Alliance,
communication technologies (e.g. ZigBee Alliance, QIVICON wonder happens. At the same time, we want
QIVICON wonder happens. At the same time, we want
ZWave Alliance, eQ-3)? Approach them directly or
ZWave Alliance, eQ-3)? Approach them directly or to prevent that every Smart Home platform provider
to prevent that every Smart Home platform provider
through SDOs?
through SDOs? creates its proprietary solution and multiples the work.
creates its proprietary solution and multiples the work.
How do we align and strike a balance?
How do we align and strike a balance?

 What is the best suited SDO for such a discussion?
What is the best suited SDO for such a discussion?
HGI, BBF, ETSI-M2M or others
HGI, BBF, ETSI-M2M or others 
 How can we create a DLNA certification for the Smart
How can we create a DLNA certification for the Smart
Home?
Home?

 If HGI is the best suited SDO, how do we cooperate
If HGI is the best suited SDO, how do we cooperate
with other SDOs such as BBF, OSGi, ETSI M2M?
with other SDOs such as BBF, OSGi, ETSI M2M? 
 With whom do we need to align (e.g. ETSI/M2M,
With whom do we need to align (e.g. ETSI/M2M,
Internet of Things)?
Internet of Things)?

 Who to involve in such a discussion?
Who to involve in such a discussion?

 How to best interact with device manufacturer?
How to best interact with device manufacturer?

 How useful is it when players aligned and defined a set
How useful is it when players aligned and defined a set
of common use cases and functional requirements?
of common use cases and functional requirements? 
 Approach them directly or through SDOs?
Approach them directly or through SDOs?

 How fast technology providers are able to deliver? How
How fast technology providers are able to deliver? How 
 What is the best suited SDO for such a discussion?
What is the best suited SDO for such a discussion?
long does it take to see first results?
long does it take to see first results? HGI, BBF and/or ETSI/M2M
HGI, BBF and/or ETSI/M2M

 Who to involve in such a discussion?
Who to involve in such a discussion?
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 10

11. Thank you:
Let’s get connected.
Deutsche Telekom AG
Products & Innovation - Connected Home
Carsten Steigleder
Business Development
Landgrabenweg 151, 53227 Bonn
E-Mail: carsten.steigleder@telekom.de
Twitter: @steigi007
For more information: www.qivicon.com
Building a Smart Home ecosystem - Urgent need for standardization Dec, 2012 11