ACME oneM2M CSE

An open source CSE Middleware for Education.

Version 0.11.3

Introduction

This oneM2M compliant CSE implements a subset of the oneM2M standard (see http://www.onem2m.org). The intention is to provide an easy to install, extensible, and easy to use and maintainable CSE for educational purposes.

Documentation

Please consult the following pages for further instructions.

• Installation
• Configuration
• Running
  • Console
  • Docker
  • Notification Server
• Web & Rest UI
• Importing Resources
• Operation
• ACMEScript
  • Commands
  • Macros
  • Meta Tags
• Supported Resource Types and Functionalities
  • Limitations
• Roadmap
• Development
• Contributing
  • Acknowledgements
• FAQ

Changes

Please see the Changelog for the detailed list of changes.

Highlights in this release

• <crossResourceSubscription> and <semanticDescriptor> resource types support.
• Support for semantic queries and semantic discovers.
• [wifilient] and [dataCollect] management object specializations support.
• Support for blocking UPDATE notification event type.
• Various improvements: Support for expirationCounter and notification statistics (<subscription> and <crossResourceSubscription>).
• Added CORS (Cross-Origin Resource Sharing) support for http binding.
• Various new commands and macros for scripting interpreter and the console.
• Improved definition of enumeration values for validation.
• Changed subscription notification handling to asynchronous.
• Improved request timeouts, especially for the http binding.
• Improved internal handling of requests sent by the CSE itself.
• And, as usual, many improvements, bug fixes, and performance improvements.

Acknowledgements

Please see Acknowledgements.

License

BSD 3-Clause License for the CSE and its native components and modules. Please see the individual licenses of the used third-party components.

Optimization

• When create new resource, it is always insert all the request before do validation which not make sense. It can be optimize using cache system where request data saved in cache and when resource is validate, then insert to DB
• Return only non null field. But when initiate resource. Handle retrieving expected data if key not found, then set it to None
• Very often get resource and only use a couple of the attribute? (But there's a validation when initiate Resource object. Maybe just don't validate when in that case?)
• in StoragePostgres, there's a loop query call. Use pgsql instead.
• In getSubscription, only retrieve specific attribute just as legacy does