zero configuration http-coap proxy implementation based on cgi
TRANSCRIPT
Zero Configuration HTTP-CoAP Proxy based on CGI
Jongsoo Jung, Jeehoon Lee, Haeyong Kim, Gyusang Shin, and Seontae Kim Embedded Software Research Department
Electronics and Telecommunications Research Institute (ETRI), Korea {jsjeong, zardu22, haekim, gsshin, stkim10}@etri.re.kr
Motivation
Power Meter
Applicants PIR Sensor Environment
sensor
Device
Interception Forward Reverse
Destination Actual CoAP
resource Proxy Proxy
Request target Actual CoAP
resource Actual CoAP
Resource Sub resource of
the proxy
Configuration No Client Proxy
URI mapping Homogeneous Not necessary
Embedded mapping or additional complex mapping
Proxies for HC Translation
Why CGI?
Internet Constrained
Network
HTTP Client HC Proxy CoAP Server
GET
http://{Proxy address}/cgi/coap/
{CoAP URI path}/sensor/temperature
GET
coap://{CoAP URI path}
/sensor/temperature
HTTP/1.1 200 OK … 20 (℃)
0x62450405…
(2.05 … 20 (℃))
HTTP, a de-facto REST protocol is widely used in computers, phones,
and tablets, currently.
Linux
Apache2
HC Proxy (CGI)
CoAP, an emerging REST protocol for constrained devices will realize
Internet of Things in the near future. Not compatible with each other
System Overview
If the proxy should be implemented for the actual embedded devices such as the border router, CGI will be an efficient solution because the CGI programming can be implemented lightly using C language.