5.1 OSGi Interworking Architecture

Figure 5.1-1: OSGi Interworking Architecture

OSGi Interworking is to interwork services provided by an OSGi based device or gateway to oneM2M entities which may be an AE or CSE. The OSGi services may include an OSGi defined DAL (Device Abstraction Layer) service, SDT (Smart Device Template) service, DMT (device management tree) admin service, other standardized services or proprietary services. The oneM2M-OSGi IPE bundle is in charge of the interworking of OSGi services to oneM2M resources and vice versa.

The IPE bundle maps the invocation of the OSGi services and changes of state of oneM2M resources. If the OSGi based device or gateway hosts a CSE bundle, the IPE interacts with the CSE bundle internally. The OSGi based device or gateway interacts with the other oneM2M entities through Mca or Mcc reference point. If the OSGi based device or gateway does not host a CSE bundle, the IPE interacts with the CSE through a network interface.

The principle of how the interworking should be done shall follow the definition in oneM2M TS-0033 [2] proximal IoT interworking. For devices described by HAIM (Home Appliance Information Model) in oneM2M TS-0023 [1], <flexContainer> resources shall be used to represent the OSGi services. oneM2M also allows the transparent interworking of OSGi services through <container> resources, <AE> resources and <node> resources as defined in oneM2M TS-0033 [2].