IEC/ISO JTC1 /SC25/WG1 NWIP proposal : Home Network Lower Layer Protocol over UDP/IP for Household Appliances September 17 th 2003 Presentation by Akira

IEC/ISO 　 JTC1 　 /SC25/WG1

NWIPproposal :

Home Network Lower Layer Protocol over UDP/IP for Household Appliances

　 September 　 17 th 2003　　　　 Presentation by Akira Toba

ECHONET CONSORTIUM (http://www.echonet.gr.jp/English)THE JAPAN ELECTRICAL MANUFACTURER’S ASSOCIATION

TOSHIBA CORPORATION /TOSHIBA CARRIER CORPORATION

[email protected]

Copyright(C)1997-2003 ECHONET Consortium 2

Table of Contents

Purpose of New ProposalProposed Logical Specification

– Definition of Home Network Lower Layer

　– Overview of the protocol

Proposed Plug & Play Specification

Purpose of NEW PROPOSAL


Aim Various Home Network Standards in the World

However,very rare media that can be commonly used in the world ,due to the difference from each country’s radio law

Accommodate the common lower medium for Home Network for White Goods

Introducing UDP/IP Introducing UDP/IP

Introducing Bluetooth,or other global mediaIntroducing Bluetooth,or other global media


Main Merits for Introducing UDP/IP

Can be applied for various White Goods Home Network Standards all over the world

Wide application 　 on one platform (AV+White Goods,etc)

Easy to introduce new media

Can transfer Control data

Can transfer Text,AV data

( out of proposed range)

Work together with IP network appliances

Work together with BT PAN network appliances

　　　　 UDP/IP Layer　　　　 UDP/IP Layer

TCP/UDP applicationText data

Audio,Music,Picture Data

Use IP address

TCP/UDP applicationText data

Audio,Music,Picture Data

Use IP address

Home Network Mainly Control Data

Use Specific address

Home Network Mainly Control Data

Use Specific address

Fridge,oven range,aircon,TV,etc


PLC

Application Software

ServiceMiddleWare

DeviceObject

ServiceObject

ServiceAPI

Absorption of Protocol Differences

HomeNetwork Communication Control Block

Common Lower-level Communications Interface

Basic APIBasic API

LowPower RF

HBSIrDA

ControlLonTalk®

A B C D E

PLC RF TwistedPair Cable IR RF

・ Air Conditioner Class・ Power Sensor Class Etc.　　

・ Address resolution・ file transfer・ Energy Management　

media

CommunicationMiddle Ware

Lower level Communication

software

Individual Lower-level

Communications Interfaces

RF

F

BluetoothTM

・ Address resolution・ file transfer・ Energy Management　

Target Model –for ECHONET


Target Model　– for KONNEX

Ctrl = Controller Approach LT= Logical Tag (e.g. Code Wheel) PB = Push Button approach LTE= Logical Tag extended

CommonKernel

Standard Addressing

TP1 TP0 PL132 PL110 RF IR

RuntimeInterworking

Configuration

7

3

21

NETWORK

MANAGEMENT

TOOL

Common Logo

PC based Tool

LT LTEPBCtrl*)

Easy-Mode

Ether-net

System-Mode Auto-Mode

StandardConfiguration/EngineeringTool

Run Time (EIS)

AAuto-

Configuration

S E

Common Object definitions

Media CouplerBetween Media Bleutooth


Target Model -for CEBus

Netw

ork L

ayer M

anagem

ent

Application

Network

Datalink

Physical

TWISTED PAIR

POWER LINE

COAX

FIBER OPTIC

INFRARED

RFBluetooth

Protocol over UDP/IPOverview


Items for Proposal

Proposal Working Draft Main Contents

Layer Structure

Packet Format

Plug & Play Method

Software Internal Status Transition

Annex

Topology for Bluetooth

Interface Function for Upper Layer and Bluetooth Layer


Proposal layer

Power 1ine

Radio Communication

Twisted pair line

Infrared

　　　　　　　

Home Network Lower Layer Protocol

・・・・

Home Network Upper Layer ProtocolObject management

Crate message for sending,Analyze received message/etc

Application

IEEE802.3Ethernet

IEEE802.11b

・・・

UDP/IP

BluetoothTM

proposal layer

MeritCan be applied for various White Goods Home Network Standards all over the worldWide application 　 on one platformapparatus with IP protocol & without IP can co-exist Easy selection from various media defined under IP layer


Proposal layer as Annex

UDP/IP 　 Interface is defined as a common layerIEEE802.15.1 Interface is defined at Annex When new medium is introduced, area should be newly defined.

Home Network Lower Layer

IEEE802.15.1 (Lower Layer)

UDP/IPIEEE802.15.1 (Upper Layer)Specified by IEEE802.15.1

IEEE802.15.1 InterfaceSpecified by this proposal spec

as Annex

UDP/IP　Interface


Other specifications to be used IP v4 RFC 791 Internet ProtocolARP RFC 826 Address Resolution ICMP RFC 792 RFC 950UDP RFC 768 User Datagram ProtocolDHCP RFC1541 Dynamic Host Configuration Protocol

RFC1122 Requirements for Internet HostsBluetooth Specification Version1.1（ Core Specification）Bluetooth Specification Version1.1（ Profile Specification）Bluetooth Specification (Personal Area Networking Profile

Version1.0) Bluetooth Specification (Bluetooth Network Encapsulation

Protocol Version1.0)

Home Network Lower Layer Protocol over UDP/IP

Logical Specification


Definition of Home Network Lower Layer

Packet formats 　　　BNEP

Header

IP

Header

UDP

Header

Home Network

Frame etc.

BT

HeaderChecksum

CRC

　 UDP port number and IP multicast address

Register specific number IANA(Internet Assigned Number Authority)

　 Define Packet formats of both control packets and Home Network frame　　　　 Home Network frame, Initialize, ARP,,,

　 Plug & Play

　　　 Server mode / Auto mode (Distributed address auto-configuration)


Broadcast and multicast

　 Mapped on IP multicast packets

-Register specific address for HomeNetwork to IANA(Internet Assigned Number Authority)

　 Broadcast and multicast are defined on Bluetooth PAN profile

-NAP/GN route broadcast and multicast packets to the destination nodes


Protocol Stack

RF

Baseband

L2CAP

BNEP

UDP/IP

Home Network Lower Layer Protocol

in case of Bluetooth


CRCUser DataPayload headerPacket headerAccess code CRCUser DataPayload headerPacket headerAccess code・・・

HomeNetwork frame

HomeNetwork frame

HomeNetwork frame

UDP header

UDP headerIP header

HomeNetwork frameUDP headerIP headerBNEP header

HomeNetwork frameUDP headerIP headerBNEP headerL2CAP header

HomeNetworkAbsorption of Protocol Differences

UDP Layer

IP Layer

BluetoothBNEPLayer

BluetoothL2CAP Layer

BluetoothBaseband/Physical Layer

Packet Structure of HomeNetwork frame

in case of Bluetooth


Various AddressesNode ID

Address to specify a certain HomeNetwork node in the subnetLogical address transformed from HomeNetwork MAC addressPart of HomeNetwork address

HomeNetwork MAC addressAddress to specify a certain node on the HomeNetwork transmission media (e.g. IP/Bluetooth)Different from Bluetooth address

IP addressBluetooth Address

Use “Hardware address” on this specification

　　　　


HomeNetwork Node A(HomeNetwork MAC Address= MACa,

IP address = IPa,Hardware Address = Ha)

HomeNetwork Node C HomeNetwork Node B

(MAC ／ IP ARP request)(Target HomeNetwork MAC address ＝ MACa)

Node C wants to send packet to Node A(HomeNetwork MAC address=MACa)

(MAC ／ IP ARP reply)(Target IP address ＝ IPa 、 Target hardware address ＝ Ha)

Node C does not know the IP address of the Node A, and send ARP packets to it

(HomeNetwork frame)

Send HomeNetwork packet to the Node A

Register the addresses on internal address table

Address Resolution (1)


HomeNetwork Node A(HomeNetwork MAC Address= MACa,

IP address = IPa,Hardware Address = Ha)

HomeNetwork Node C HomeNetwork Node B

(Hardware /MAC ARP request)(Target Hardware Address = Ha

Node C wants to send packet to Node A(HomeNetwork MAC address=MACa)

(Hardware /MAC ARP reply)(Target IP address ＝ IPa 、 Target HomeNetwork MAC Address= MACa ,Target hardware address ＝ Ha)

Node C does not know the HomeNetwork MAC Address of the Node A, and send ARP packe

ts to it

(HomeNetwork frame)

Send HomeNetwork packet to the Node A

Register the addresses on internal address table

Address Resolution (2)


Packet type number Packets Mandatory / Option

0 HomeNetwork frame Mandatory for all nodes

1 MAC/IP ARP request Mandatory for all nodes

2 MAC/IP ARP reply Mandatory for all nodes

3 IP/MAC inverse ARP request Option (All nodes)

4 IP/MAC inverse ARP reply Mandatory for all nodes

5 Hardware/MAC inverse ARP request Option (All nodes)

6 Hardware/MAC inverse ARP reply Mandatory for all nodes

7 MAC address initialization request Mandatory for all nodes(No need for manual mode nodes)

8 MAC address initialization reply Mandatory for all nodes

9 MAC address server initialization reply Mandatory for address server

10 MAC address confirmation Mandatory for all nodes(No need for manual mode nodes)

11 MAC address confirmation request Mandatory for all nodes(No need for manual mode nodes)

12 MAC address confirmation reply Mandatory for all nodes

13 MAC address request to all nodes Mandatory for address server

14 MAC address reply Mandatory for all nodes

15 MAC address server discovery request Mandatory for address server

16 MAC address server notify Mandatory for address server

17 MAC address server discovery reply Mandatory for address server

Others For Future Reserved

Home Network Lower Layer Protocol over UDP/IP

Plug & Play Specification


Node Initial process

Process until acquisition of HomeNetwork MAC address and communication each node over HomeNetwork/UDP/IP network

Process until acquisition of HomeNetwork MAC address and communication each node over HomeNetwork/UDP/IP network

• Contents– Specify three Initial process modes by the way of acquisiti

on of HomeNetwork MAC address– Not specify the way of setting Initial process modes – Not recommend to mix Nodes of different initial mode in

the Subnet （ basically not mix in the Subnet ）


Initial Sequence Mode（１）Initial Sequence Mode

Manual-MODE （ M －MODE ）

Server Requirement- MODE （ SR －MODE ）

Auto-MODE

（ A －MODE ）

Acquisition of HomeNetwork MAC Address

Manual Address Server Hybrid

（ Distributed　 Address／Address Server）

Address Plug&Play

× ○ ○

Note Ease to Development of by Vendor

Recommend as Standard Mode


Initial Sequence Mode（２）

●Each Node must implement either Auto-Mode or Manual-Mode

●Not specify the way of setting modes and displaying mode setting


Manual-MODE

●Node uses manual-set HomeNetwork MAC address.

●There is no special description in the case of overlap address setting.


Server-Required-Mode

●This mode requires at least one address server in the subnet

●HomeNetwork MAC address is assigned to node by address server

●Initial process fails when the node can’t detect address server

●Address server tries to assign the same HomeNetwork MAC address if the device had been formerly assigned

●It’s recommended that address server assign temporary HomeNetwork MAC address that each node decided


Deciding process of Temporary HomeNetwork MAC Address 　

Request to clear HomeNetwork MAC address?( LowInit? )

Preserve the same HomeNetwork MAC Address as the one at the last time ?

Deciding Temporary HomeNetwork MAC Address

Use the HomeNetwork MAC address at the last time as Temporary HomeNetwork MAC

Address

Use lower 8bit of Hardware Address as Temporary HomeNetwork MAC Address

Y: 　 preserve

N: not preserve

N: not clear

Y ： destruction

END


Server Required Mode Sequence （１）

MAC address server CMAC=01

Initial Node XMAC=?

Node AMAC=02

Node BMAC=03

T6 time wait

T2 time wait

MAC Address Serverinitialization reply

（ assign MAC=4 ）

（ Target IP address = IPme ）


（ Target IP address = IPx ）HomeNetwork address is configured

( MAC=4)

MAC address initialization request



Server Required Mode Sequence （２）

(Target IP address = 　 IPme)

T6 time wait

T2 time wait

None of MAC Address Server reply　→ Initial failure

(Target IP address = 　 IPme)

MAC address initialization requestTemporary MAC=4

Node CMAC=01

Initial Node XMAC=?

Node AMAC=02

Node BMAC=03

MAC address initialization requestTemporary MAC=4


Auto Mode

●HomeNetwork MAC Address of Initial Node is assigned by address server when MAC Address Server exists in the Subnet

●Initial Node decides HomeNetwork MAC address by itself (by distributed mechanism)in the subnet when Initial Node can’t detect address server

● Temporary HomeNetwork MAC address that each node decided is the first candidate as HomeNetwork MAC address


Auto Mode Sequence （１）

T6time wait

T2time wait

（ Target IP address = IPc ）

（ Target IP address=IPx ）

（ Target IP address = IPx ）

MAC address confirmation

MAC address server CMAC=01

Initial Node XMAC=?

Node AMAC=02

Node BMAC=03

MAC address initialization reply（ Used MAC=2,3 ）

MAC address initialization reply （ Used MAC=3 ）

MAC address Server initialization reply（ assign MAC=4 ）




This packet includes

・ Address mapping table information

・ Detection master router information

(as well as another sequence )



MAC address is configured MAC=4


Auto Mode Sequence （２）

T6 time wait

T2 time wait

MAC address initialization reply

（ Used MAC=2,3, 4 ） MAC address initialization reply（ Used MAC=3 ）

MAC address initialization reply（ Used MAC=4 ）

T9 time wait

（ Target IP address= IPx ）






Acquisition of Used HomeNetwork MAC Address in Subnet （ Used MAC=2,3,4 ）

MAC address confirmation request

（ Temporary MAC=5 ）

MAC address confirmation request




MAC address initialization request （ Temporary MAC=5 ）

None of MAC Address confirmation replyHomeNetwork address is configured MAC=5

Node CMAC=04

Initial Node XTemporary MAC=?

Node AMAC=02

Node BMAC=03



Halt

Warm Start Cold Start

Startup wait

Normal operation

Temporary haltError

LowStart LowInit LowInitAll

Acquisition of HomeNetwork MAC addressEnd of initialization

Confirmation of HomeNetwork MAC addressEnd of initialization

LowRequestRun

LowSuspend LowWakeup

３２

１２

３

LowHaltLowStart

LowInit, LowInitAll

１２

３

LowHaltLowStart

LowInit, LowInitAll

LowInit, LowInitAllLowStart

１LowHalt

Error detection

Removal of cause １２

３

LowHaltLowStart

１２

３

LowHaltLowStart

LowInit, LowInitAll

Initialize Processing

Initializationnot possible

PowerOn

LowInit, LowInitAll

LowStop

IP address alteration

Disconnection BNEP

State Transitions in HomeNetwork Communications Processing Block

END

Thank you for your kind attention

Documents

IEC/ISO JTC1 /SC25/WG1 NWIP proposal : Home Network Lower Layer Protocol over UDP/IP for Household Appliances September 17 th 2003 Presentation by Akira