Page 966 - Unleashing the potenti al of the Internet of Things
P. 966
7 Unleashing the potential of the Internet of Things
The sensor network management protocol message should include a request ID field. If this field
does not use the same format with an SNMP message, then the sensor network gateway also
maintains mapping information between the request ID from the SNMP message and request ID
from the sensor network management protocol message.
8.4 Translation from a sensor network management protocol to an SNMP message
Figure 5 shows the operational procedure of the sensor network gateway when it receives a sensor
network management protocol message from a sensor network management protocol agent.
ALG database
Keys Contents
Lookup Sequence
number ... ... ... ... ...
Sensor network management protocol message
Header VarBindList
Source Destination ... Sequence ... ...
sensor ID sensor ID number Name Value ... Source Destination ... ... Request ID ... Name Value Name Value ...
IP address IP address
... Source Destination ... ... Request ID ... Name Value Name Value ...
IP address IP address
First VarBind
VarBindList
SNMP common
header SNMP PDU
UDP
IP header header SNMP message
H.641(12)_F05
Figure 5 – Translation from a sensor network management
protocol message to an SNMP message
When the sensor network gateway receives a sensor network management protocol message from a
sensor node, it extracts the sequence number and looks up the original SNMP message from the
ALG database. Then it creates a new SNMP message. It copies the destination IP address of the
original SNMP message into the source IP address field. It then copies the source IP address of the
original SNMP message into the destination IP address field. Then it copies the request ID and the
first VarBind. It copies the VarBindList from the sensor network management protocol message into
the VarBindList of the new SNMP message. When it copies the OID in the VarBindList, base OID
should be added (see clause 9 and Appendix I).
952 Rec. ITU-T Y.4701/H.641 (02/2012)