Defining the Border Between P1451.0 and P1451.5

Myung Leelee@ccny.cuny.edu

CUNY/Samsung

PHY 1 PHY 2 PHY 3

MAC 1 MAC 3

MAC 3 - SAP

LLMPLAM Protocol

Datagram Protocol StreamingData Protocol

TriggerProtocol Management Protocol

NLMPNetwork Protocol

LM - SAP

CommandService

ReplyProtocol

MAC 2MAC 1

MAC 1 - SAP MAC 2 - SAP

NCAP or TBIM Application

P1451.0

P1451.5

Security & Encryption

ND - SAP NM - SAP

P1451.5Management

(This is above the communications stack and is not part of the 7 layer model)

Physical

Data Link

Network

TransportSession

Presentation

Application

SAP: Service Access PointLLMP: LAM Layer Management ProtocolNLMP: Network Layer Management ProtocolLD: LAM DataLM: LAM ManagementND: Network DataNM: Network Management

LD - SAP

P1451.0 Application

IEEE P1451.0 + P1451.5 Protocol Stack— Option 1: With Routing Protocol

PHY 1 PHY 2 PHY 3

MAC 1 MAC 3

MAC 3 - SAP

LLMPLAM Protocol

Datagram Protocol StreamingData Protocol

TriggerProtocol Management Protocol

LM - SAP

CommandService

ReplyProtocol

MAC 2MAC 1

MAC 1 - SAP MAC 2 - SAP

NCAP or TBIM Application

P1451.0

P1451.5

Security & Encryption

P1451.5Management

(This is above the communications stack and is not part of the 7 layer model)

Physical

Data Link

NetworkTransportSession

Presentation

Application

SAP: Service Access PointLLMP: LAM Layer Management ProtocolLD: LAM DataLM: LAM Management

LD - SAP

P1451.0 Application

IEEE P1451.0 + P1451.5 Protocol Stack— Option 2: Without Routing Protocol

Our view on dot0* and dot5 • Network Layer

– Should multi-hop routing protocol be included in wireless NCAPs and transducers (option 1):

• The routing protocol belongs to dot5 instead of dot0 since only dot5 needs routing functions.

• As routing is the major function of the network layer, and routing is highly related to other functions of the network layer (e.g. addressing), we suggest putting the whole network layer to dot5.

– If multi-hop routing is not considered in 1451 family (option 2):

• The network layer of dot5 can belong to dot0.* IEEE P1451.0 Common TEDS Study Group — Final Report

Our view on dot0 and dot5 (cont.)

• Management– Different MAC may need different management

• Ex. Channel scan for wireless MAC/PHY

• Standard services offered by the Data Link Layer– Can be part of dot5 (instead of part of dot0)

because some services are not common to all dotXs (e.g. dot2).