1 / 6

Exploring the Resource Directory Concept in CoRE for M2M Web Architecture

The Resource Directory (RD) is a key concept in the Constrained Application Protocol (CoAP) providing a structured approach to manage and discover Machine-to-Machine (M2M) resources. Leveraging past projects such as the EU SENSEI project (2008-2010), this draft outlines definitions for the RD architecture, RESTful interfaces, and various methods of resource registration, updating, and lookup. It also addresses common issues, necessary terminologies, and strategies for differentiating between multiple RDs to enhance the efficiency of resource discovery in constrained environments.

trapper
Télécharger la présentation

Exploring the Resource Directory Concept in CoRE for M2M Web Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CoRE Resource Directory draft-shelby-core-resource-directory-00 Z. Shelby, S. Krco CoRE WG, IETF-81 Quebec City

  2. Background Not a new concept (think search engine) EU project SENSEI (2008-2010) http://www.sensei-project.eu Developed an M2M web resource architecture “Resource Directory” was a main concept CoRE hack fests Resource directories were deployed to make testing easier Also see draft-bormann-core-simple-server-discovery-00

  3. Architecture

  4. RD REST Interface Discovery GET coap://ff02::1/.well-known/rd?rt=core-rd 2.05 Content </rd>;rt=core-rd Registration POST coap://{RD}/rd Etag: 0x40 2.01 Created Location: /rd/{end-point} Update PUT coap://{RD}/rd/{end-point} Validation GET coap://{EP}/.well-known/core Etag: 0x40 Deletion DELETE coap://{RD}/rd/{end-point} Lookup GET coap://{RD}/rd?rt=TemperatureC

  5. New Link-Format Attributes Two new link-format attributes defined Resource Instance (ins=) Distinguishes between resources with the same Resource Type (rt=) Max length of 63 octets Export Flag (exp) Existence of flag allows an RD or other entity to export link to e.g. Another RD or search engine DNS-SD

  6. Known Issues Terminology section needed Host, End-point, Resource Entry, RD, etc. How to differentiate between multiple RDs in discovery? Use ins= attribute to differentiate between RDs How to tell the RD about the host? Add a “Host ID” attribute to registration Could be host name, device serial #, HIT etc. People seem to confuse host, end-point and resource Explain that end-point is an logical concept that the RD uses to handle updates and deletes Clarify that RD stores the source IP address and port or registration Define how observe can be used on RD resources

More Related