the constrained application protocol (co ap) implementation-part4-1

12
Khamdamboy Urunov, a Ph.D. student. Special Communication Research Center., Graduate School of Financial Information Security., Kookmin University Seoul, South Korea Specification of Out Testing mechanism for Underwater Internet of Things (UIoT). Implementation & out testing programming schedule

Upload: hamdamboy-urunov

Post on 23-Jan-2018

22 views

Category:

Education


1 download

TRANSCRIPT

Page 1: The constrained application protocol (co ap) implementation-part4-1

Khamdamboy Urunov, a Ph.D. student.

Special Communication Research Center.,

Graduate School of Financial Information Security.,

Kookmin University

Seoul, South Korea

Specification of Out Testing mechanism for

Underwater Internet of Things (UIoT).

Implementation & out testing programming schedule

Page 2: The constrained application protocol (co ap) implementation-part4-1

Plan

1. Specification of Out Testing mechanism for Underwater Internet of Things

a. Protocol Specification parameters

b. Specification protocol with Security of authentication mechanism

2. Implementation Out testing mechanisma. Security of authentication mechanism

3. U_CoAP implementation (server part) based on Java

2

Page 3: The constrained application protocol (co ap) implementation-part4-1

• Communication service specification should generate service primitives for a

conversation between two machines.

3

1. Protocol Specification parameters

Communication service specification

Page 4: The constrained application protocol (co ap) implementation-part4-1

Data Transfer phase specification

4

1. Protocol Specification parameters (2)

Page 5: The constrained application protocol (co ap) implementation-part4-1

5

Data Transfer phase specification

1. Protocol Specification parameters (3)

Page 6: The constrained application protocol (co ap) implementation-part4-1

6

Data transmission parameters consist of several steps:

• rdt_data_request(data): compute checksum, make_pkt,

send(sndpkt).

• rdt_data_indication(rcvpkt):

• receiver receives the data and sends an ACK, In case of corrupted

data

reception, sends NACK.

• rdt_rcv(rcvpkt): (at sender)

• performs reception of packet (ACK or NACK)

• If ACK then send next data, if NACK then retransmit the data.

• rdt_send(ACK): receiver sends the ACK.

• rdt_send(NACK): receiver sends the NACK.

• isNACK(rcvpkt): checks for negative acknowledgment reception

• isACK(rcvpkt): checks for positive acknowledgment reception

• corrupt(rcvpkt): checks the packet for corrupted data

• Notcorrupt(rcvpkt): checks for non corruption

• extract(rcvpkt,data): extracts the data from received packet

• deliver data(data): delivers data to the upper layer

1. Protocol Specification parameters (4)

Page 7: The constrained application protocol (co ap) implementation-part4-1

7

Leaf Nodes (LN) Terrestrial IoT

Server (TIS)

DTN Gateway Cluster

Header (CH)

2. Implementation Out testing mechanism

Testing procedure: Out test is using checking process of communication possibility. In the diagram

Terrestrial IoT Server (TIS) is sending ping message to DTN Gateway, if conjunction is OK after that DTN

gateway to send CH again checking required in order to nice, last checking is CH and LN communication

surround whole system.

Page 8: The constrained application protocol (co ap) implementation-part4-1

8

2. Implementation Out testing mechanism (2)

Terrestrial IoT Network elements (using technical devices) like application program (using apps) connect to

underwater devices. Out testing parameters surround whole system elements and communication networks.

Page 9: The constrained application protocol (co ap) implementation-part4-1

9

2. Implementation Out testing mechanism (3)

Page 10: The constrained application protocol (co ap) implementation-part4-1

10

2. Implementation Out testing mechanism (3)

Page 11: The constrained application protocol (co ap) implementation-part4-1

U_CoAP implementation (server part)

based on Java

11

Page 12: The constrained application protocol (co ap) implementation-part4-1

• Thank you

12