Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Mihini/M3DA Specification"
Line 10: | Line 10: | ||
* [[Media:M3DASecurityExtension.pdf | M3DA security extension]] | * [[Media:M3DASecurityExtension.pdf | M3DA security extension]] | ||
* [[Media:M3DABysantSerializer.pdf | M3DA serializer (Bysant)]] | * [[Media:M3DABysantSerializer.pdf | M3DA serializer (Bysant)]] | ||
− | * [ | + | * [http://download.eclipse.org/mihini/doc/agent/Device_Management.html Device management over M3DA] |
− | * [[Mihini/M3DA_Specification_Password_Negotiation| Initial security password negotiation]] | + | * [[Mihini/M3DA_Specification_Password_Negotiation | Initial security password negotiation]] |
Latest revision as of 09:32, 11 October 2013
The Mihini agent is a software component that acts as a mediator between an M2M server and the applications running on an embedded gateway. M3DA is a protocol optimized for the transport of binary M2M data. It is made available in the Mihini project both for means of Device Management, by easing the manipulation and synchronization of a device's data model, and for means of Asset Management, by allowing user applications to exchange typed data/commands back and forth with an M2M server, in a way that optimizes the use of bandwidth (see Bysant serializer specification).