2012
DOI: 10.1109/mic.2012.29
|View full text |Cite
|
Sign up to set email alerts
|

CoAP: An Application Protocol for Billions of Tiny Internet Nodes

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
255
0
2

Year Published

2013
2013
2022
2022

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 562 publications
(257 citation statements)
references
References 2 publications
0
255
0
2
Order By: Relevance
“…Interestingly, the solution in [29] does not directly use a specific NDN-type names for IoT (e.g./ndn/kcl.edu/strand_building/ 1st_floor/room_17/temperature) for each IoT resource but uses a more scalable and manageable generic and opportunistic search process using attributes of IoT data (e.g. ''traffic'') and following the format of IoT data annotations used by CoAP [11] and specified as CORE Link Formats [31]. If an immediate match is not found, the RD distributes the attribute-based search to all network elements acting as RDs before match(es) are found.…”
Section: Emerging Novel Networking and Routing Modelsmentioning
confidence: 99%
See 2 more Smart Citations
“…Interestingly, the solution in [29] does not directly use a specific NDN-type names for IoT (e.g./ndn/kcl.edu/strand_building/ 1st_floor/room_17/temperature) for each IoT resource but uses a more scalable and manageable generic and opportunistic search process using attributes of IoT data (e.g. ''traffic'') and following the format of IoT data annotations used by CoAP [11] and specified as CORE Link Formats [31]. If an immediate match is not found, the RD distributes the attribute-based search to all network elements acting as RDs before match(es) are found.…”
Section: Emerging Novel Networking and Routing Modelsmentioning
confidence: 99%
“…building or room names), location-based IoT routing [33] or the resource discovery-based solutions (e.g. a client's application level command GET ''/.wellknown/core'' that retrieves resources from a CoAP RD such as a gateway [11]) that need URL or IP address (i.e. DNS) to contact the RD [29].…”
Section: Identifying Iotsmentioning
confidence: 99%
See 1 more Smart Citation
“…Rather than introducing a new communications protocol to implement this functionality, this paper focuses on studying the applicability of a standard communication protocol for constrained devices -in particular, the Constrained Application Protocol (CoAP) that was introduced as a lightweight alternative to HTTP and optimized to work in constrained environments [5]. The research question addressed in this paper can be formulated as follows: Is it feasible to utilize CoAP as a transfer protocol for retrieving the information needed for monitoring and accounting purposes as metered on constrained devices?…”
Section: Introductionmentioning
confidence: 99%
“…Constrained devices can be categorized into (i) Class-0 devices ( 10 kByte of RAM and 100 kByte of ROM) only capable of engaging in simple communication scenarios with the help of a proxy or gateway, (ii) Class-1 devices (≈10 kByte of RAM and ≈100 kByte of ROM) powerful enough to directly communicate with their peers in the Internet via lightweight protocols, and (iii) Class-2 devices (≈50 kByte of RAM and ≈250 kByte of ROM) whose capabilities are sufficient to support full-fledged protocols used in conventional network nodes [3]. Among these three categories, Class-1 devices, being both inexpensive and capable of communicating with their peers in the Internet, are believed to play an important role in emerging IoT applications [5]. Class-1 devices therefore determine the main focus of this work.…”
Section: Introductionmentioning
confidence: 99%