@@ -4,11 +4,10 @@ LOM2M is a message oriented middleware implementing the oneM2M standard and its
Have a look to LOM2M [technical sheet](uploads/1c68a72e2a18adb196200f3676d3d5fe/LOM2M.pdf).
Most of the acronyms used in this wiki are oneM2M acronyms. To refer to those acronyms cf. oneM2M technical specifications.
Some of them are defined again here:
Most of the acronyms used in this wiki are oneM2M acronyms. To refer to those acronyms cf. oneM2M technical specifications. Some of them are defined again here:
| Acronym | Definition |
|------ | ------|
|---------|------------|
| IoT | Internet of Things |
| CSE | Common Service Entity |
| IN | Infrastructure Node |
...
...
@@ -17,7 +16,7 @@ Some of them are defined again here:
**Default configuration**:
| Config | Value |
|------ | ------|
|--------|-------|
| HTTP port | `8282` |
| Originator AE Admin | `admin:admin` |
| Remote CSE ID | `in-cse` |
...
...
@@ -29,55 +28,62 @@ Some of them are defined again here:
(These values can be changed at build time or dynamically on UNIX targets)
# Target deployment
The typical target deployment is a power constrained gateway (microcontroller).
Here are some example of memory usage regarding the target:
The typical target deployment is a power constrained gateway (microcontroller). Here are some example of memory usage regarding the target:
**MCU ESP8266**:
- ~500KB (sketch)
- ~50KB RAM
-\~500KB (sketch)
-\~50KB RAM
**UNIX based systems**:
- at least 5MB storage (executable size)
- at least 3MB RAM
**DOCKER container**:
- at least ~10MB for compressed image (precompiled)
LOM2M Dockerfile is based on alpine to run the compiled executable.
- at least \~10MB for compressed image (precompiled) LOM2M Dockerfile is based on alpine to run the compiled executable.
(These sizes may vary regarding to the enabled features)
# Resources
## Global Resources
-[Install & Launch](LOM2M/Install, configure and launch)
-[Features & Capabilities](LOM2M/Features and capabilities)
A continuous integration is enabled on the project.
It is configured to trigger different tasks regarding commits, merge requests, etc.
For more details about this configuration, cf.:
-[Gitlab configuration CI/CD](LOM2M/Gitlab configuration and CI-CD)
A continuous integration is enabled on the project. It is configured to trigger different tasks regarding commits, merge requests, etc. For more details about this configuration, cf.:
