unpublished © telemetry associates ltd. 2004 – smarthouseii-m4.ppt slide no 1 smarthouse logo...

Unpublished © Telemetry Associates Ltd. 2004 – SMARTHOUSEII-M4.ppt slide no 1 ‘SMARTHOUSE’ logo copyright Telemetry Associates Ltd.

SMARTHOUSE – Second Open Forum 30/11/2004

SMARTHOUSE II – OverviewSMARTHOUSE II – Overview

The Development of a Code of Practice for the European SMARTHOUSE under CENELEC

An Action Supported by EU/EFTA and Coordinated with e-Europe 2005

Ref: CENELEC/ENTR/000/2003-10

Stephen Pattenden

Unpublished © Telemetry Associates Ltd. 2004 – SMARTHOUSEII-M4.ppt slide no 2


SMARTHOUSE CODE of PRACTICESMARTHOUSE CODE of PRACTICE Evolved from SMH Phase I

Excellent work - detailed report - informative annexes

Need to deliver a powerful tool for the Smart House and all stakeholders that have influences on it

SMH Phase II

A code of practice for the Smart House

Supported by EU Commission,

ICTSB (ICTSB/SHSSWG)

Input from all the Stakeholders

Utilise all the standards and practical output from EU FP6 Projects esp D2

Managed by CENELEC under TC205 WG16 as a CENELEC Workshop Agreement



Objectives of Phase IIObjectives of Phase II Deliver a Forum for information and understanding

Prepare an Interim Report covering all influences

Prepare a Code of Practice.

(Beyond this work, the aim is to have the CoP accepted and used in the marketplace, for it to be maintained and regularly updated.)



Roadmap for the workRoadmap for the work The Contract between the EU Commission and CENELEC sets a

requirement for particular deliverables, milestones and performance indicators. For this contract these are the major deliverables:

1. Roadmap for the work 19th February 2004

2. Interim Report 19th September 2004

3. Final Report / Code of Practice 19th August 2005

Beyond this there is a requirement to establish the Forum that will meet in 2004 and 2005 (probably in June)

Lastly, this work is intended to achieve a deliverable that will assist the market place to accelerate its growth in the area of SMARTHOUSEs. This implies:

regular maintenance and upgrade of the CoP on a yearly basis into the future.



Roadmap - graphical viewRoadmap - graphical view

WE ARE HERE



Layout of CoPLayout of CoPThis Code of Practice is presented in five main parts.

1. This Introduction2. The Influences on the SmartHouse.

The reason for a SmartHouse and its value; the Consumer’s needs and requirements; and the Service Provider’s aims and objectives in meeting the consumer’s needs

3. The design of the SmartHouse System Architectures, the glue of the system The Wide Area and its Network Operators and delivery media The Home Networks and their Media Gateways; and Security

4. Installation The Installation Process

5. Product Development. Service and Application development Consumer Equipment User Interfaces



Section LayoutsSection Layouts The Introduction and each following section deliver material that provides:

At the highest level, anyone with some knowledge of what may be possible At the next level, any practitioner of the SmartHouse with details of best practice At the lowest level, experts in the area of the section, recommendations for implementing

the SmartHouse The five parts focus on the process of selecting from a wide range of possible options,

what standards and practices to use and how to use them in configuring and installing systems for the SmartHouse. Each subsection has a number of parts.

The first part is an introduction that outlines the major issues of the subsection The second part describes the issues in greater detail

provides a decision process that assists the system designer in reaching appropriate design choices in the form of recommendations.

Where decisions need to be made, then there are short descriptions of the issues. and references to appropriate standards, specifications and ongoing standards and

research work. Since there are many interactions and dependencies with other sections, these too are referenced.

Note 1. The final part may be a set of recommendations or examples that might be in tabular form



SectionsSections List of Sections

Consumers Section - Roy Brooker

Service Providers – Bruno Ziegler (EDF)

Architectures – Peter Colebrook i&i

Wide Area and Network Operators – Philippe Calvet (France Telecom)

Home Networks and their Media – Walter von Pattay (ISO/IEC / ZVEI)

The Residential Gateway – Milan Erbes (Independent Consultant/ETSI)

Security – Per Kaijser (Independent Consultant)

Installation – Luc Baranger (FFIE)

Home Equipment – Paolo Falcioni (WRAP)

User Interfaces – Stephen Pattenden (Telemetry Associates)



Architectures SectionArchitectures Section

Peter Colebrook of I&I Limited/BSI



Introduction, Issues, Introduction, Issues, RecommendationsRecommendations This section has a quick introduction to the aims of this section

It deals with some of the issues

It asks how we can arrive at recommendations and

Looks at some of the ways forward



SmartHouse Structure // ArchitectureSmartHouse Structure // Architecture

Architecture provides the framework for SmartHouse

Descriptions, Interoperability, Commercial and Trust



Sections and their RelevanceSections and their Relevance

Security is the overarching necessity

Everything fits within the Architectural framework.



Framework for SmartHouseFramework for SmartHouse Supports the services, networks and equipment in the (system) environment

of the SmartHouse

Architecture should provide methodologies that link the elements of the SmartHouse (networks, equipment, services, user interfaces and applications) together

Architecture must provide the means of interoperability between

systems in the SmartHouse

the systems involved in delivering services and operating applications in the SmartHouse

the “users” in the SmartHouse

This has implications



Implications for SmartHouse ArchitectureImplications for SmartHouse Architecture A SmartHouse Architecture needs to:

Provide the requirements for communication, interaction and interoperability between objects (i.e. provide the framework or glue)

Provide the description of “objects” in terms of

Ontology – the science of being, in the abstract (the description of things)

Taxonomy – the classification of things in relation to one another

Descriptors – a normalised way of describing the attributes of things

Provide the framework for all this including:

The Commercial transactional requirements

The Legal requirements involved in the communication, commercial transactions,

The establishment of trust and privacy and

The rights of individuals and of the holders of copyright.



Architecture IssuesArchitecture Issues Multiple Architectures already in Smarthouse environment

Almost all subsystems have

Residential Gateway and the SmartHouse Architecture

Developments from various industry sectors



Multiple ArchitecturesMultiple Architectures



Architecture and the GatewayArchitecture and the Gateway Most of the service traffic and all communication traffic may pass through the

Gateway

It is an ideal location for control processes

But there are issues of service aggregation and ownership of the gateway that need solving

What happens if there are multiple gateways?

What do we do about “legacy” gateways – Cable and DSL modems and routers, Set Top Boxes and so on. In many cases the consumer will have bought them.



Current DevelopmentsCurrent Developments Many sectorial interests:

IT/PC industry – DLNA (and MicroSoft Corporation)

Telecoms and ETSI – NGN@Home project

Service Providers and ISPs – no particular Architecture but much legacy equipment

Home Network consortia – all have their own architectures

Home Equipment sector – Both A/V and White Goods have work in progress (e.g. CECED CHAIN)

Utility sector – No particular architecture but active

Also much going on in FP6 projects

There is however no Architecture that really meets an overarching solution that interoperates with most other architectures.

mailto:NGN@Home



Recommendations?Recommendations? We don’t really have one using available standards

We can just carry on and point you to all the work that is in progress (But that is not an optimal solution)

We need to develop a usable architecture that is pragmatic and works.

CENELEC SmartHouse has put forward a bid to EU Commission to work on a Requirements Specification for what is needed to provide an overarching architecture for the SmartHouse.

We will be working closely with the RG Section because of the close relationship between Architecture and the RG.



SMARTHOUSE II – Home Residential GatewaySMARTHOUSE II – Home Residential Gateway

Milan Erbes

Residential Gateway Team Leader

ETSI NGN@Home WG Chairman



Existing Comms Cabled Infrastructure (HAN)

RG

SCT Access Network(s)

PSTN / ISDN

IP Data N/W

Other MM N/W (IMS)

Other NGN

Home Area Network (HAN) “Customer Premises” Access Core Networks

TE

Either one (not both) of these links may be provided

Session Control Interface (Signalling)

ETSI TISPAN NGN

BB Access Network(s)

Home Area Network

Home Area Network

Home Area Network

Home Area Network

Broadcast Audio Video N/W

Broadcast Access Network(s)

TE

TE

UE GW

Mobility Network (e.g. In-Car Network)

UE

TE

UE

UE

TE

Auto Area Network

Home Area Network

GW

UE

TE

Auto Area Network UE

NGN High-Level InterconnectionNGN High-Level Interconnection



FundamentalsFundamentals

There are four fundamental areas that are key to NGN@Home and shape the requirements for the residential gateway:

- Multiple Access Networks using both IP and non-IP native access

technologies)

- Multiple Home Area Networks - including the control domain, the

transport domain, and the applications environment)

- Multiple Services and Service Providers with multiple content

streams and formats

- Multiple End User Devices and Terminal Equipment connected

within the Home Area Network



New In-Home ServicesNew In-Home Services

• Home Related Services: Home Appliance Control & Automation (Energy Savings, Lighting, Shutters, Pool control), Remote Management, Entertainment, Healthcare, E-commerce, Security Communications

• Connected Office: VPN, Video Conferencing, VoIP• Remote Control: Remote Managing of Home appliances, Connecting to the home

network• Content: Music, Video Games, Banking, Billing, Info-channel, TV, Chatting, Video

telephony, Video Conferencing, Information Storage, Internet Radio, Messaging….• Mobility: Full collection of music and videos in car, Sync over WLAN, 3G or while

parked in your garage.• Emergency: Emergency calls from within house/home or even a car, rerouted

through Home RG to appropriate call center.

Standardized solutions will make it easier for creation and offer of new applications & services like:



RequirementsRequirements

Support man-to-man, man-to-machine, machine-to-machine communication modes.

Support higher numbers of service users (increased number of users and devices like intelligent house machines, Radio-Frequency ID tags, sensors etc..)

Support various types and modes of communication including end-to-end point-to-point and multipoint connections.

Support QoS ranging from best effort to priority service for business purposes.

Support Safe, Secure and Reliable communication in order to fully protect the Privacy of Users.

Support and Promote business opportunities so that anyone can easily set up a new business using the network.

Home Residential Gateway should:Home Residential Gateway should:



Basic AttributesBasic Attributes

Reliable end-to-end communications,

Simple setup install, configure, maintain and easy operation

Most homes do not have access to technical network management services.

Home network components need to be offered at consumer price points and capable of distribution through consumer electronics channels.

Technologies comprising home networks will be more heterogeneous than typical business LANs

Various service creation and new business opportunities

Home networks may suffer a greater range and variety of signal impairments than a typical business environment due to the ad hoc nature of the in-home electronic environment.



VehicleFirewal

l

PrimaryHome

Domain

SecondaryHome

Domain

Firewall

MultipleHome

Domains

Firewall

ExtendedHome Domain

Yacht

ExtendedHome Domain

Capable ofattaching anddetacting fromHome Network

Not capable ofattaching to Home

Network

Public Domain

WLANHot spots

HOTELShopping Mall etc

User'sPAN

Workplace Domain

User'sPAN

Multiple Home DomainsMultiple Home Domains



House IP back-bone network

Local Router 1

Provider 2Provider 1

Home network4TV/AV

Home network1 Non-IP

Operations & ControlNetwork

Local Router 2

Home Network Model

Provider 3

Residential Gateway Firewall, DRM,

Security....

Internet

Local Gateway1

Home network2

Home network3



Content Providers

ArchitectureArchitecture

Gateway

End Device

Agent

End Device

Agent

Policy Coordination Module

AccessProvider A

AccessProvider Z

HAN Module

Content ProvidersContent Providers

ConnectionModule

. . .

. . .Connection Module

Policy Coordination Module

HAN Module

RG Coordinates shared access to the

Internet for all it’s End Devices

ConnectionModule

•NAT•QoS•Security

1. Might be separate hardware (Hub, bridge, switch, access point) 2. Ties the various home networking media together (Ethernet, IEEE 1394, 802.11, HPNA, PLC, Bluetooth, USB, Cable…)3. Notifies the Policy Coordination Module of pertinent changes.

•IP Routing•Digital Rights•Multicast optimization

Coordinates changes amongst the other modules, makes appropriate adjustments to other Modules as needed. It handles:

xDSL, Cable, BWA, ETTH, FTTH…



Home RG StackHome RG Stack (example)(example)

Interface

EthernetStack

VPN

Multimedia

Voice

Access Network HAN

xDSL Cable xTTH Wi-Fi IEEE1394 USB Home PNABlue

ToothPowerLine 802.11a/b

PPPoE DHCP DNS NAT Bridging FireWallRIP

Traffic Prioritization, Class-Based Queuing, RSVP, VPN pass through,

RADIUS Authentication, Packet Filtering

VPN Security - PPTP; IPSec, L2TP, IKE, Security Library, Hardware Cryptography

MPEG2/ MPEG4 over RTP , SDP, RTP, RTCP, RTSP

SIP, H.323, Voice over DSL, Voice over Cable

Management Programmable

API’s

WEB Interface

Java, HTML…

Remote Software

Support & Upgrade

SNMP

Management



Key FunctionsKey Functions

Simultaneously connected to multiple and heterogeneous delivery networks

Access to content independent of the underlying hardware / transport mechanism

Subscription, a commercial relationship between the subscriber and the service provider

User Profile that is a set of information necessary to provide a user with a consistent, personalised service environment, irrespective of the user’s location or the terminal used

Nomadicity and Mobility

IP multimedia application that handles one or more media streams simultaneously such as audio, video and data. A multimedia application may involve multiple parties, multiple connections, and the addition or deletion of resources within a single IP multimedia session



General Model. The Home Residential Gateway Architecture targets at supporting a wide

range of services, from legacy telephony to new generation services, such as: audio, data, video broadcast, streaming services, interactive gaming.

Functional Architecture Model. A distributed functional architecture to support and control user sessions (identification, authentication), resource allocations, the traffic policing & enforcement, services and applications, between various entities within the home network like (Packets filtering, Packet marking, Resource allocation and Bandwidth reservation, Allocation and translation of IP addresses and port numbers, Throughput limitation, User Authentication, Usage metering…

End-to-end Quality of service

Service platforms (including APIs)

Network Management

Security& DRM/CA

Key RequirementsKey Requirements



Encompass CPEs

Be independent of access technology

Accommodate multiple administrative domains

Support varying services, such as real-time multimedia communications and VPN

TheThe QoS QoS Goals Goals and Functionsand Functions

Support convergence of connectionless and connection-oriented networks and technology

Support proactive (admission control) and reactive (congestion control) based mechanisms

The QoS architecture should:

Home Residential Gateway device supports a transparent bridging functionality for QoS messaging from/to home compliant applications

Enable home networking applications to establish prioritized data transmission among Hosts as well as between the Hosts and the Home Residential Gateway.

Ability to assign traffic priorities (differentiated media access) to specific applications

Ability to prioritize queuing in the Home Residential Gateway device in conjunction with the packet handling functionality.



SmartHouse IT SecuritySmartHouse IT Security

Per Kaijser

IT Security

Independent



ScopeScope

IT Security

Protection of the SmartHouse System and Information - not the SmartHouse itself

Similar to the protection of a computer, but

Always on line

Several services, some safety critical

Possibly many types of communications

Best practice for SmartHouse system designers



Aim of IT securityAim of IT security

Trust in the system

Privacy

Availability of services

Integrity of system and data



ThreatsThreats

Active and passive intruders

Unauthorized users of system or services

Unauthorized access to data in system and communications

Privacy

System and data integrity violation

Denial of service

Malicious software (virus)

New software, Updates, Downloades, Communications



Some Other IssuesSome Other Issues

Guidelines for remotely accessible services

Limitations on service commands

Man-Machine-Interface (MMI)

Mistakes must not lead to dangerous situations

Digital Rights Management (copyright)

A contractual rather than technical issue

Technically a content provider issue

Users must know their rights and limitations



Three Security ModelsThree Security Models

Owner Controlled Model (OCM)

Fully controlled by user

Difficult

Externally Supported Model (ESM)

Implementations at SmartHouse

Security Service Provider Model (SSP)

Access SmartHouse via SSP



Important Security ServicesImportant Security Services

Access Control

Protection against active and passive intruders

Different users have different access rights

Confidentiality

Protection of communications

Auditing

Registration of security relevant events

Virus protection



CoP RecommendationsCoP Recommendations

Selection of - Security Services (type and quality), and - Model according to Threats,

Needs,

Knowledge, and

Cost

Read and adopt User Security Guidelines

Checklist



Getting Involved in SmartHouseGetting Involved in SmartHouse SmartHouse is structured into 10 sections that have significant interactions.

Each Section has an active group of experts. (some more active than others).

The SmartHouse Code of Practice will be a useful and definitive reference for System Designers and all other stakeholders in the SmartHouse.

We want you to get involved and to influence the Code of Practice.

You are all registered to take part. Choose your section(s) and contribute. Make sure your sectors’ views are included.

All details are on www.cenelec.org and follow the SmartHouse link.

http://www.cenelec.org/



SmartHouse is for nowSmartHouse is for now The Code of Practice will need to work with existing equipment yet be able to

accommodate with future trends.

The SmartHouse must overall be safe and secure

The SmartHouse must be reliable

It has to meet future challenges.



Future Trends - Challenges Future Trends - Challenges Electronics, pervasive computers, communication without bounds -

distributed intelligence Systems, networks, integrity, self healing software (or ….) Entertainment, Media, Content - new paradigms The Home Equipment - what devices will be in the future home User Interfaces - how to talk to the devices, equipment, home Equipment and home management - your peace of mind. Resources and Energy (Kyoto/Malthus) Home working – Where does this take us? Physical Security - Safety, Wellbeing, Health, Accessibility Data Security - Content protection, Privacy, Certification Affects of all this on the consumer



Systems, networks, integrity, Systems, networks, integrity, The home and its environment will become a maze of systems and networks.

They must interoperate (need for a common architecture)

They must work safely together

But

There are many options

There are many potential media

There will be greatly increased system variability

So

We cannot easily ensure integrity, safety or security let alone privacy. There are so many things we can get wrong.

We need to develop systems and software that are self healing, self diagnosing and remotely managed. This is what the SmartHouse CoP is about: providing necessary information and highlighting gaps.

We are not there yet but

System error the house will reboot in 20 seconds

Checking the integrity of the security system

You have a fault in the security system –

House closing down

Ring 0870 333 4444 for support services

Closing down communication systems

Don’t panic

Don’t panic

Don’t panic

Don’t panic

Don’t panic

Don’t panic



That’s why we need a CENELEC SmartHouse Code of Practice

We should have it in place by August 2005

What for the future?



This SmartHouse – The PotentialThis SmartHouse – The Potential



Phase IIIPhase III



CENELEC CODE of PRACTICECENELEC CODE of PRACTICE

Thank you

Stephen Pattenden

Managing Editor, SmartHouse Code of Practice

Telemetry Associates [email protected]

[email protected]

unpublished © telemetry associates ltd. 2004 – smarthouseii-m4.ppt slide no 1 smarthouse logo...

Documents

smarthouse open forum

smarthouse code of practice

open forum report

european smarthouse

system designer slide

stephen pattenden slide

scene report

equipment providers