ETSI M2M / TIA architecture harmonization

O. Elloumi

TR50.1 architecture, general observations• Intermediate node is the

equivalent of an ETSI M2M Gateway (G’ in particular, TBC), although not explicitely stated as such in the architecture specification

• Chaining of intermediate nodes is possible (not part of ETSI M2M R1)

• No horizontal service platform: Application server implements functions of NA and NSCL

• Smart Device is equivalent to D & D’ device, while Device is equivalent to legacy ‘d’ in ETSI M2M parlance.

– X interface is out of scope for ETSI

• Interfaces to AAA are not shown in ETSI Architecture, but are recognized as internal interfaces

High-level mapping

M2M CoreService

Capabilityplatform

SCs

NIP

NADDA

SCs

dIamIa

d(out of scope)

D‘DA

d GGAdIa

GIPSCs

dIa

mId

mId

Legacy case 1

Case 1

Case 2

Legacy case 2mId

d

DDAdIa

DIPSCs

Legacy case 3

(out of scope)

(out of scope)

mId

Delta for ETSI to take into account TIA

M2M CoreService

Capabilityplatform

SCs

NIP

NADDA

SCs

dIamIa

d(out of scope)

D‘DA

d GGAdIa

GIPSCs

dIa

mId

mId

Legacy case 1

Case 1

Case 2

Legacy case 2mId

d

DDAdIa

DIPSCs

Legacy case 3

(out of scope)

(out of scope)

mId

Delta:• G to G (in ETSI M2M this can be handled via the thenetwork)• D to D (not necessarily viaLAN/PAN)

Way forward on harmonization

• TIA TR50.1 architecture considers the need for multiple interconnected gateways as important aspect of the architecture to account for e.g. Smart Grid deployments

• TIA TR50.1 identifies the need for a convergence layer as a means to hide network specificities

• Intermediate node would connect multiple smart devices and intermediate nodes.• ETSI consider the M2M service platform as separate from the Application Server

(common agreement on this)• Next steps:

– Email discussion over the joint mailing list (Paul Russel to trigger a way forward discussion)

– Email discussion on definitions (Mitch to trigger email discussion on definitions alignment)

– May 11 conf. call (2 and ½), Victoria will send practical arrangements– June 7th conf. call (2 and ½) (decide for date and venue for the F2F meeting taking into

account the current progress)

Reference points mapping• A1: AAA <-> the application server.

• A2: AAA <-> the intermediate node.

• A3: AAA <-> the smart device controller.

• A4: AAA <-> the smart device.

• B1: application <-> intermediate node.

• B3: intermediate node <-> smart device controller.

• B5: application server <-> smart device.

• B6: intermediate node <-> intermediate node

• B7: smart device <-> smart device

• X: device <-> smart device controller. This reference point is outside the scope of this document.

• NSCL to MAS interface (internal in ETSI)

• Does not exist

• Does not exist

• Does not exist

• mId (Note: intermediate node is G’ equivalent)

• Does not exist in R1 (but is mId variant?)

• mId

• Does not exist in R1

• Considered out of scope

• Out of scope (position similar to TIA)

For further discussion: mIa and dIa have no equivalent in TIA TR50