Broadband Forum Machine-to-Machine (M2M) Solutions

Contact:

Robin Mersh, Broadband Forumrmersh@broadband-forum.org

Broadband ForumEngineering smarter & faster connections

Architecting a connected lifestyle– Defining best practices for global networks

– Enabling multi-service and content delivery

– Establishing technology migration strategies

– Engineering critical device & service management tools– Engineering critical device & service management tools

– Redefining Broadband

� Who are we?– Industry consortium made up of approximately 200 service

providers, vendors, consultants, academia and test labs

– Predominant broadband industry forum since 1994

– Engineer technology solutions to help service providers achieve standards based, economical and effective broadband deployments

Broadband Forum – Home Group

� Focus on Home Networking devices functionality, capability and connectivity.

� Proven scalable protocol solutions connecting the central office to customer premise.

� Enabling new services with recent Technical � Enabling new services with recent Technical Reports.

� Strong interoperability track record, regular test events for its protocols since 2005.

� Consistent and growing liaison relationships with other SDOs (3GPP, ETSI. etc)

3

Broadband Home – Device Management

TR-069 – CPE Wan Management Protocol (CWMP)

�Industry leading device management solution.

�Evolving TR-069 family of extensive and modular manageable ‘objects’ covering wide range of devices and functionality.

�Referenced by many industry bodies such as 3GPP, ATIS, ETSI and ITU-T.ITU-T.

– Approved as a European standard in 2010 by ETSI.

– Currently referenced in ETSI M2M architecture as a protocol for device management that runs over the “mId” reference point.

– Ongoing work between the Broadband Forum and ETSI M2M to develop new Object model work.

�Well over 70 Million devices connected.

�Ratified by DSL (now Broadband) Forum in May 2004, amended in 2006 and 2007 and recent M2M driven amendments.

4

TR-069 Architectural Framework

OSS/BSS

Policy

Managed LAN DeviceScope of CPE WAN Management

Protocol (CWMP):ACS Southbound Interface

5

� Management Functions– Bootstrap– Service Provisioning– Firmware and Software Module Management– Diagnostics– Fault and Performance Monitoring– Large and growing set of defined object models

Call Center

Auto-Configuration Server (ACS)

Managed Internet Gateway Device

Managed LAN Device

Managed LAN DeviceACS Northbound Interface

TR-069 recent M2M activity

TR-069a3 – CWMP enhanced with Execution

Environment support.

�Software Module Management to support embedded applications.

�Open design for mapping to multiple Execution environments (OSGi, OMA, etc).

�New RPC and Software Module Data Model support required.

6

TR-069a3 Software Module Management

CWM

Services Gatewaymanages

managesmanages

manages

Operating System, Drivers, HG Core

CWMP

Mgmt Agent Execution Environment

Module Module Module ModuleTR-069

ACS

TR-069 recent M2M activity

TR-069a4 – CWMP enhanced with Proxy

management for LAN devices that do not

support CWMP.

�TR-069 extended to proxied devices managed via a non-TR-069 protocol. non-TR-069 protocol. �Requires devices to connect to a CWMP CPE Proxier.�Based on industry study of IP (UPnP-DM) and non-IP (Zwave) local management technologies.�Design includes Embedded and Virtual Device solutions.

8

TR-069a4 Remote Management of non-TR-069 Devices

TR-069 “Proxying” Managed Device

ACS

Non-TR-069 “Proxied” Managed Device

CWMP RPC to Proxy Service on TR-069 Device

Local Protocol command to non-TR-069 Device

Local Protocol Success Response

CWMP RPC Response

� Proxy management agnostic to the local protocol– UPnP DM/DLNA, Zwave, ZigBee etc.– Layer 2 protocols (e.g. HomePlug OAM, etc.)– Any proprietary local protocols known by the proxying device

� TR-069 accesses proxied devices through TR-069 managed objects– ACS sends management commands to proxying device– TR-069 device converts TR-069 commands to local protocol– Once proxied device has successfully executed commands, TR-069 device

sends CWMP messages to ACS

Broadband forum M2M Next activities:Identify GAPs Critical for Service Delivery

� Continue work on current BBF specifications for Management Plane.– Potential BBF management specifications for a standard

North-Bound Interface (NBI) for interfacing to new services.

� Analyze Control Plane as key enabler to service delivery to provide connectivity to growing ecosystem of devices.

BBF and M2M Ecosystem

�

End-to-End Arch

Other SDOs/Fora

ETSI OMA

ETSI

Coordination

Partnership?

IP/MPLS & Core

...

OMA

Broadband Forum

Broadband Home Marketing/Strategy

Content Delivery

Cloud Service

Enterprise Networking

11

�TR-069/PD-174

�Strategic roadmap/

timeline; M2M-relatedWhite Papers;Questionnaire;

Interest Request;Use Cases; etc.

Operations & NWM

M2M Applications

M2M Integration

ETSIM2M

Energy Eff. / Smart Grid (?)

IP/MPLS & Core

�OD-278

...

OMADMGap Analysis

M2M Management

Adjacent Emergent Broadband Services

Relationships

�OD-282

Motivation: M2M Value and Value ChainKey M2M Stakeholders

Network Operator

Mobile or Fixed Network OSS M2M M2M GW of the Provider

Provisioning

Self-Service

B2B Gateway

M2M Application providerM2M Application providerM2M Application ProviderOur Data ! Application User

M2M Service Provider

12

Network OSS(existing networks)

M2MPlatform

M2M GW of the Provider or its Partners

B2B Gateway

Tariff/Charging

Resource Mgt.

M2MDevices

M2MDevices

Access Network Connections

ChargingBilling

Device Owner

Carrier’s Network Customer Network

M2MDevices

M2MDevices

Proxy/GW

M2M Activity : Ongoing TR-069 Work

� OD-278 to study a set of M2M use cases in order to verify extended verticle scenarios impact to TR-069, identify new object models and potentially identify GAPS.

� Identify overlapping or related standardization work in other fora/SDOs involving device management and object model work.

� Current analysis:– M2M (local) area networks: new constraints, e.g. large

number of devices, autonomy capabilities, heterogeneity

– system architecture in relation to ETSI TC M2M.

– Data modeling � potential model extensions

– Protocols � potential protocol extensions

13

MM Plane: Identify Gaps in BBF Specs

� Currently, gaps to be analyzed in OD-278 within BB Home– Protocols– Data model

M2M Applicatione.g. Facility Mgt, HealthCareM2M Application

e.g. Facility Mgt, HealthCare

A1

M2M Applicatione.g. Facility Mgt, HealthCare

Auto-Configuration Server (ACS)

Managed LAN Device

ACS NBI

Signaling/

interaction/

coordination

Application

data/control

flow

App Proxy

Mgt Proxy

M2M Management

A2

A3 A4

A5

CP1 CP2

CP3

CP4 CP5

System Model14

management flow(TR-069, OD-278)

control plane flow(OD-282, NBI)

M2M activity – OD-282 Control Plane

� Horizontal solution for enabling end device communi cation for countless Vertical Services.

� Build on recent work to enable services in the Smar t Home.

– Devices enabled with Execution Environment to provide embedded applications to enable services.

– Devices enabled with Proxy Management able to provision and manage growing ecosystem of M2M/IoT devices.

� “Missing piece” essential to Service Providers to p rovide device connectivity for new M2M related services.

� Analysis Phase centered on problem statement, looki ng for synergy in other SDO (20+ liaisons) M2M work.

� Build on the Broadband Forum competency and leaders hip in large scale device communication solutions.

15

Control Plane

OD-282 Control Plane to provide:

� End device addressing– Device home network address in Service Provider network– Provides scalable access and individual addressing for all devices,

both IP and Non-IP– Each device individually addressed and accessible to embedded and

cloud applications– Discovery of Control Plane Routers and Applications

� Connection to non-IP and legacy devices– Access to existing devices (and gateways) on existing network

technologies, requiring no modifications.– Not management plane – “Real time” command communications.

� Device Abstraction– Provides access to all devices using a common protocol and common

objects, enabling an extensible ecosystem.– Access by embedded and cloud applications.

OD-282 ETSI integration discussion

� Broadband forum and ETSI M2M Working Group joint meeting in September to discuss alignment and synergy with ETSI M2M architecture.

� Broadband forum potentially utilize ETSI security and bootstrap details where required for secure connections to control plane routersrouters

� OD-282 Control Plane could possibly fit into M2M architecture as a ‘service capability layer’ similar to TR-069?

� Control Plane provides access and individual addressing for all devices, both IP and Non-IP

– Providing a common control plane access to existing devices on existing networks

– Protocol operating on the mId (and potentially dIa) reference points

Thank you