1. Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, lijing80@huawei.com Meeting Date: 2016.03.14---2016.03.18 Agenda Item:

2. Strategy member: 10, Principle member: 4, Contributing associates: 12, Supporters: 144 OSGi Technology: Provides specifications, reference implementations, test suites and certification. Adoption of the component-based platform reduces time-to-market and development costs because it enables integration of pre-built and pre-tested modules. Reduces maintenance costs and provides aftermarket opportunities because networks are used to dynamically update or deliver services and applications in the field. Suitable for building network gateway. Service Provider Manufacturer Software Technology OSGi Alliance: Non-profit corporation founded in March 1999. Worldwide consortium to create open specifications that enable the modular assembly of software built with Java technology. Member company include leading service providers, infrastructure/network operators, utilities, enterprise software vendors, gateway suppliers, consumer device suppliers and research institutions. OSGi : most famous Java modular technical specifications

3. OSGi IoT Expert Group : extend OSGi Specifications to address software infrastructure in IoT. IOTEG areas of concern include: The support application developers to create IoT services Targeting embedded and cloud environments where they intersect with endpoint devices Data processing and management in IoT gateways Cross-industry and cross-protocol device connectivity on sensors and IoT gateways Support the development and deployment of device abstraction layer The virtualization of IoT services Connectivity to the cloud for endpoint devices (and the interoperation with existing management systems and protocols) Enable and enforce IoT end-to-end security Development of the specifications and APIs entails the creation of supporting documentation, reference implementations, and compliance tests. Reference :IoT EG Introduction - https://www.osgi.org/about-us/working-groups/internet-of-things/

4. OSGi IoT Requirement : provides solutions for IoT use cases Device Abstractions Device Drivers Messaging Orchestration Resource Management Power Management Real Time Remote Management Data/Eventing Management Identity Management Universal OSGi Adaptive Deployment Contextual Information Trusted Computing Platform Security Management Education & Tooling Cloud Network Connectivity 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 141.Device Abstraction 142.Device Abstraction Layer Functions 113. Event Admin Service 137. REST Management Service 110. Initial Provisioning 103.Device Access 144.Resource Monitoring Life cycle management of Bundle ID Service ID of Device 134.Subsystem Service 50. Conditional Permission Admin Service ImplementedNot implemented Reference : OSGi RFP174 - https://github.com/osgi/design/blob/master/rfps/rfp-0174-IoT-Requirements.pdf

5. oneM2M and OSGi Interworking - Recommended Solution OSGi Framework Device Manageme nt Bundle Event Admin Service Bundle Interworking Proxy Entity Bundle … OSGi Compliance System ASN/MN/IN CSE MN/IN CSE AE Mca Mcc/Mcc’ Mca OSGi Interworking Proxy Entity Bundle oneM2M AE OSGi Internal Interface Device Management/Event Adapter/… Recommended Solution: 1.Consider oneM2M and OSGi to be 2 separate Systems 2.Add Interworking Proxy Entity Bundle in OSGi 3.Implement oneM2M AE in IPE, communicate with oneM2M network through Mca reference point 4.Implement OSGi device management, event, … client, communicate with OSGi through OSGi internal interface 5.Convert Device Model, event format,… between oneM2M and OSGi in IPE System Design Idea: add a Interworking Proxy Entity Bundle in OSGi IPE Bundle Overview:

6. System Design Idea: By abstracting away a physical lamp behind an OSGi lamp service interface, the device-specific access protocols are hidden to the developer, and the lifecycle is managed by OSGi. OSGi Abstract Device Model : Thing as a Service Basic Concept of OSGi Device Abstract Device Model: Device - represents the device in the OSGi service registry. Described with a set of service properties and provides basic management operations. Function - atomic functional entity like switch or sensor, provides a set of properties and operations. FunctionEvent - asynchronous event. Posted through EventAdmin service and notifies for Function property change. FunctionData - data structure which carries Function property value with extra metadata. PropertyMetadata and OperationMetadata - contain metadata about the Function properties and operations. Reference : OSGi Residential Release 6 Specification - https://www.osgi.org/developer/downloads/release-6/release-6-download/

7. TV1 FirmwareversionSoftwareVersion volume Power … … Function interface 1 oneM2M Module ClassOSGi Device Abstraction Functions NameDate TypeNameData Type buttonSwitchbooleanBooleanControlboolean keypadintegerMultiLevelControlinteger lockstringCustom FunctionString ………… 1.oneM2M Module Class focus on the business 2.OSGi Device Abstraction Functions Layer Functions focus on the software implementation 3.Every oneM2M Module Class can map to a OSGi pre- defined or custom Device Abstraction Function OSGi Abstract Device Model : Compatible with oneM2M Function interface n OSGi Device Structure example PropertyFunctions oneM2M Device Structure example TV 1 Firmwareversion SoftwareVersionvolume Power …… PropertyModule Abstract device structure designs are basically the same.

8. OSGi EventAdmin Service : Standard Subscription & Notification Model can adapt any protocol System Design Idea: By using the EventAdmin service, an IoT application bundle can be totally agnostic about the underlying eventing protocol. OSGi IPE Bundle oneM2M AE Event Admin Service Adapter Convert OSGi subscribe Request to oneM2M's oneM2M Subscription and Notification CSE as Event Broker Convert oneM2M event to OSGi’s Event Admin Service Custom Service Control Bundle OSGi IPE Bundle oneM2M AE Event Admin Service Adapter Convert oneM2M subscribe Request to OSGi's oneM2M Subscription and Notification CSE Convert OSGi event to oneM2M’s Event Admin Service as Event Broker Custom Service Control Bundle Subscription and Notification Interworking Procedure : Reference : OSGi Residential Release 6 Specification - https://www.osgi.org/developer/downloads/release-6/release-6-download/

9. Conclusion OSGi has set up IoT Expert Group to define the technical requirements and specifications to address information technology software infrastructure in Internet of Things scenarios. And the most common services used in building IoT applications are already implemented in current OSGi specification. OSGi provides developers not only with a complete modular development infrastructure, but also predefined standardized modules which enable the most common services in IoT domain, such as the device abstraction, data processing, event admin service, etc. OSGi can be defined as a stand-alone and complete IoT system interworking with oneM2M like OIC and AllJoyn. Since both oneM2M and OSGi specification have different but largely complementary application scope. In the IoT domain, it is highly beneficial that these two systems can be interworked in a synergetic way allowing deployments to take advantage from enriched features resulting from this combined effort. We propose to create a new work item to study the complete interworking solution.