Hi Mimi,
About various versions of OMA-DM: v1.2 is widely deployed. v1.3 was just completed last year and there is no available implementation for now (as far as I know)
but it is compatible with v1.2. v2.0 is still a work under progress. There is also OMA LWM2M which will be published in the next months. The latter may be more useful for you.
Regarding your questions:
What is OMA's standard way of handling multiple configurations (e.g. sensor config) for a certain type of hardware?
When an OMA-DM device connects to an OMA-DM server, it provides its ID, manufacturer, model and various other info contained in the MO DevDetail. Usually, the
OMA-DM server knows all the devices and can determine the device characteristics from the provided infos. If you have various configuration for the same kind of devices, you must rely on other mechanism. For instance there is the DeviceCapability MO but it
may be too complicated for your use case. Also you can extend the DevDetail MO to provide proprietary info to the server.
Which OMA protocol will provide the conversation between the OMA DM and the Enterprise App that is talking to the hardware? Would it be the OMA Client-side API Framework? If so, what is the mechanism for OMA to query and get the hardware
configs from the board itself?
I assume the Enterprise App is running on the device. In this case, this is a bit out of scope of the OMA-DM protocol. Usually implementations use a centralized
database of settings accessed by both the OMA-DM client and the managed applications. Client-side API can be used for this indeed. But in this case, the OMA-DM client is the owner of the settings database. A more efficient way would be that the OMA-DM client
query the Enterprise App when it needs to access the hardware. This mechanism would be entierely dependent on your implementation. OMA-DM only standardize the interface between the client and the server (DM-1, DM-2 and DM-3 in the DM2.0 architecture diagram).
Hoping this helps,
David Navarro
From: m2m-iwg-bounces@xxxxxxxxxxx [mailto:m2m-iwg-bounces@xxxxxxxxxxx]
On Behalf Of Tam, Mimi K
Sent: Wednesday, April 24, 2013 10:09 PM
To: m2m Industry Working Group
Subject: Re: [m2m-iwg] Two Questions on OMA if I may
OMA DM 2.0 came out last month but I would still refer to 1.3 although in 2.0, there are several new features added.
I would refer to the new 2.0 Reference Architecture, however.
Thanks…Mimi
From:
m2m-iwg-bounces@xxxxxxxxxxx [mailto:m2m-iwg-bounces@xxxxxxxxxxx]
On Behalf Of Julien Vermillard
Sent: Wednesday, April 24, 2013 3:53 PM
To: m2m Industry Working Group
Subject: Re: [m2m-iwg] Two Questions on OMA if I may
Links are working for me.
Anyway I pointed to the 1.2 release because it's the most used, but it was succeeded by 1.3.
On Wed, Apr 24, 2013 at 8:29 PM, UOMo <uomo@xxxxxxxxxxx> wrote:
Julien,
Quite a few of these links on OMA-DM you suggested no longer seem to work.
Are there other more reliable locations for these documents? And if not, are you sure, the standard is even still supported by the organization it once worked on it???
_______________________________________________
m2m-iwg mailing list
m2m-iwg@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2m-iwg