This chapter gives an overview about possible combinations of optional components when implementing MEEP 8. The necessity to take dependencies into account makes it non-trivial to find the best combination for the own purpose.
Of course the combinations shown here are just samples and not part of the normative specification. The number of possible combinations is much higher and by far not limited to the combinations below. But those combinations are good examples for popular use cases, and many implementers may find here what they have in mind.
Use case: Single-Function Device
This profile set supports a single application model and is defined to cover use cases of small edge-node devices with a limited and focused set of functionality and where footprint must be minimized.
Example: Smart sensors.
These devices are typically connected directly to peripheral I/O and/or have limited networking capabilities, limited remote management capabilities, and are focused on the specific use case requirements.
The intent of this profile set is to describe the smallest possible memory footprint for very resource-constrained or low-cost embedded devices.
Typical hardware parameters are:
These devices run a single application dedicated to a specific function. The application's suite can be pre-installed or installed in a limited use-case-specific manner. The function may change over time, but is principally limited in scope and flexibility.
The following requirements apply to the single-function device application model:
The above requirements allows simplifying assumptions to be made. These are
javax.microedition.swm
) is
requiredSimplified application installation:
Since only one application can be present on the device and the device is controlled by a single trusted entity, application installation can be simplified. One of two ways is possible:
The MEEP 8 "Minimal Profile Set" includes the following APIs/functionality:
javax.microedition.midlet
A typical use case solution would include:
The minimal memory needed Minimum for a combination of a single-function device without or with very few optional packages is 128 kB RAM and 1 MB Flash.
The recommended memory for a combination of a single-function device without or with very few optional packages is 256 kB RAM and 2 MB Flash (including application(s)).
Use case: Device with IMP-NG compliant implementation
The intent of this profile set is to describe a runtime which is IMP-NG compliant and which allows execution of IMP-NG-based applications without modifications.
Typical hardware parameters are:
The MEEP 8 "IMP-NG Profile Set" includes the following APIs/ functionality:
javax.microedition.midlet
A typical use case solution would include:
Use case: Multi-Function Device
The multi-function model covers use cases where devices are more powerful, address more general use cases, and there can be one or more application suites installed and applications running at any time.
These devices typically are capable of running multiple applications, implement a wider and more flexible set of functionality, are connected to a variety of peripheral I/O, have full networking capabilities, and can be managed remotely (e.g. application provisioning and lifecycle control).
The intent of this profile set is to describe the base of a runtime which is applicable to a wide range of use cases.
Typical hardware parameters are:
The MEEP 8 "Standard Profile Set" includes the following APIs/ functionality:
A typical use case solution would include:
The minimal memory needed for "standard" combination of a multi-function device with some optional packages for basic functionality, e.g. in order to enable IMP-NG backward compatibility, is 512 kB RAM and 2 MB Flash.
The recommended memory for such a combination is 1 MB RAM and 3 MB Flash (including application(s)).
Use case: Complete MEEP 8 functionality for Multi-Function Device
The intent of the MEEP 8 Full Profile Set is to describe a runtime which includes all MEEP 8 APIs/functionality, including all optional functionality (as long as the packages are not mutually exclusive). Such a Profile Set is useful for defining the maximum functionality that can be implemented by a MEEP 8 implementation, for example for reference purposes or to describe a full MEEP 8 development platform.
Typical hardware parameters are:
The MEEP 8 "Full Profile Set" includes the following APIs/ functionality:
javax.microedition.midlet
The minimum for a "full" combination of a multi-function device with all or almost all optional packages implemented is 2 MB RAM and 4 MB Flash (including application(s)).
There is no recommended memory for this, but it is "the more the better", strongly dependent on the number and character of the applications.
Copyright (c) 2014, Oracle and/or its affiliates. All rights reserved.