Abstract
In this work we discuss architectural alternatives for the design of a proxy that interconnects IoT domains running CoAP with the rest of the Internet including micro datacenters and other domains building scalable hierarchical architectures. We assume that the CoAP domain is terminated by an IoT proxy with cache, and we investigate several design alternatives, assuming that the proxy autonomously maintains data freshness. Our analysis indicates that multicast and observe-based proxies perform better than the default POST/GET approach in terms of successful data transmission, round trip delay and energy consumption, with the multicast option having a slight advantage.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
