User Tools

Site Tools


routing_through_heterogeneous_transports

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
routing_through_heterogeneous_transports [2015/09/01 07:23]
Abhishek Sharma
routing_through_heterogeneous_transports [2016/04/28 11:01] (current)
Abhishek Sharma
Line 16: Line 16:
 Option Number: **65524 (Experimental,​ needs expert review before using vendor-specific option number)** Option Number: **65524 (Experimental,​ needs expert review before using vendor-specific option number)**
  
-Option ​Max Data Length: **20**+Option ​Minimum Data Length: **1** 
 + 
 +Option Maximum ​Data Length: **20**
  
 Option Data Format: **Binary** Option Data Format: **Binary**
  
-^  1 byte   ​^ ​ '​len_src'​ bytes  ^  1 byte    ^  '​len_dest'​ bytes     ​^ ​ 2 bytes    ^ +^  1 byte   ^  1 byte   ​^ ​ '​len_src'​ bytes  ^  1 byte    ^  '​len_dest'​ bytes     ​^ ​ 2 bytes    ^ 
-|  len_src ​ |  source_address ​  ​| ​ len_dest ​ |  destination_address ​ |  multicast_seq_no ​ |+|  message_type  ​|  len_src ​ |  source_address ​  ​| ​ len_dest ​ |  destination_address ​ |  multicast_seq_no ​ |
  
 ---- ----
  
-In the proposal, OIC devices are classified into categories:​\\+In the proposal, OIC devices are classified into categories:​\\
  
 1) **Gateway** (Use "​ROUTING=GW"​ during compilation)\\ 1) **Gateway** (Use "​ROUTING=GW"​ during compilation)\\
Line 31: Line 33:
  
 2) **End device** (Use "​ROUTING=EP"​ during compilation)\\ 2) **End device** (Use "​ROUTING=EP"​ during compilation)\\
-An end device will not forward CoAP packets across different connectivity,​ but can look out for resources or make there resources available across hops with the help of Gateway'​s. End devices are identified by their MAC / IP addresses and will be only visible to border Gateway and not notified to Gateway’s across mesh. End devices are given ID’s by border ​gateway’s which will be unique ​to a Gateway and not in entire mesh. However a “Gateway ID: ClientId” pair is guaranteed to be unique in mesh.  +An end device will not forward CoAP packets across different connectivity,​ but can look out for resources or make their resources available across hops with the help of Gateway'​s. End devices are identified by their MAC / IP addresses and will be only visible to border Gateway and will not be notified to Gateway’s across mesh. End devices are given ID’s by border ​Gateway’s which will be unique ​among respective ​Gateway's end devices ​and not in entire mesh. However a “Gateway ID: ClientId” pair is guaranteed to be unique in mesh. 
- +
-3) **Stand alone** (Use "​ROUTING=OFF"​ during compilation,​ also default mode)\\ +
-A stand alone device is any OIC device in the current form. i.e. it won't look out for resources or make there resources available across hops+
  
 {{ :​multi-hop-scenario.png?​500 |}} {{ :​multi-hop-scenario.png?​500 |}}
routing_through_heterogeneous_transports.1441092237.txt.gz · Last modified: 2015/09/01 07:23 by Abhishek Sharma