AllJoyn-Interworking Discussion Group Name: TP WG2 ARC Source: Josef Blanz, Phil Hawkes, Qualcomm Inc., Meeting Date: Agenda Item: Alljoyn-Interworking (WI-0018)

Goals Quick recap of some AllJoyn concepts – Peer-to-peer paradigm, proximity – Advertisement/Discovery – Gateway Agent Concept Rationale for new proposed text in TR-0014 – Explanation of interworking concept AJ connector app interacting with oneM2M resources – Service Objects versus Services Frameworks Impact on resource structure © 2014 oneM2M Partners 2

AllJoyn: Peer-to-Peer Runs on local network (proximal network) Communicates Peer-to-Peer (Apps talk to Apps with help of AJ Routers) Enables Apps to advertise and discover each other

Things describe their capabilities I can send notifications I have control panel I can send notifications I have control panel I have Lighting Interface I can send notifications. I have control panel I have a clock interface I can send notifications. I have control panel I have a clock interface I display notifications. I have the clock interface! I display notifications. I have the clock interface! I display notifications. I have the clock interface! I display notifications. I have the clock interface! I display notifications. I have the clock interface! I display notifications. I have the clock interface! I can send and display notifications I can send notifications

Advertisement & Discovery Service Producers and Service Consumers (both are Apps) Exchange information via Service Objects Providers: Advertise Names / Do Announcements Consumer: Discover Names / Read Announcements Consumer will find Producer(s) & understand service objects One or more Interfaces: Methods (RPC) Properties (set, get) Signals (P→C)

Gateway Agent Plugin mechanism to connect AJ proximal network with cloud Already defined framework for controlling what can be exposed in both directions Best place for inserting a oneM2M IPE as a connector

AllJoyn-to-oneM2M mapping oneM2M Network AJ Gateway Agent with oneM2M AE = IPE AJ Network AJ App 2 AJ App 1 oneM2M IN CSE 3 Connector App Rsc 2 Rsc 1 oneM2M AE Y oneM2M AE Z Service Exposing App oneM2M Exposure AE 12 Consume AJ service Provide AJ service

AllJoyn-to-oneM2M mapping oneM2M Network AJ Gateway Agent with oneM2M AE=IPE & CSE AJ Network AJ App 2 AJ App 1 oneM2M IN CSE 3 Connector App Annc Rsc 2 Annc Rsc 1 oneM2M AE Y oneM2M AE Z Service Exposing App oneM2M Exposure AE 12 oneM2M CSE 1 Rsc srv 2 Rsc srv 1 Consume AJ service Provide AJ service oneM2M AE Z

AllJoyn-to-oneM2M mapping oneM2M Network AJ Gateway Agent with oneM2M AE=IPE & CSE AJ Network AJ App 2 AJ App 1 oneM2M IN CSE 3 Connector Apps AJ Network mirror App 2 mirror App 1 oneM2M AE 2 oneM2M AE 1 Service Exposing App oneM2M Exposure AE AB oneM2M CSE 1 Rsc srv B Rsc srv A Connector Apps AJ App B AJ App A Annc Rsc B Annc Rsc A Annc Rsc 2 Annc Rsc 1 oneM2M AE X oneM2M AE Y oneM2M AE Z mirror App B mirror App A Service Exposing App oneM2M AE B oneM2M AE A oneM2M Exposure AE 12 oneM2M CSE 1 Rsc srv 2 Rsc srv 1 Consume AJ service Provide AJ service

Impact on TR-0014 Need to add figure(s) as on previous slides to explain more details on principle of mapping between AJ and oneM2M Covers multiple – if not all – of the interworking scenarios defined in TR-0014 See separate contribution

AllJoyn-to-oneM2M mapping Need to develop resource structure to expose AJ service objects to oneM2M AEs – Re-use existing resource types versus new types Resource structure for provider-specific services needs to represent serv. objects – Methods (RPC) – Properties (just data, set & get) – Signals (Event, possible payload) Serv. Frameworks different from serv. objects

Service Objects vs Frameworks Uses Service Objects for exposure Uses Service Framework- specific API Examples: Notifications Control Panel Onboarding Configuration

Example: Notifications am Freeze r is open DVR is 90% full Message from LEE Simple interface for sending and receiving human-readable messages, optionally “rich” Able to assign priority types Able to configure preferences Supports interaction in response to notifications

Notification Serv. Framework Producer uses API function for sending a notification: Send( ntfcnObject) Also available: DeleteLastNtfcn( ntfcnType) Consumer provides a callback function to consume a notification: Receive( ntfcnObject) Another callback: Dismiss( msgId, appId) Serv. Frameworks use APIs (object models & RPCs) Simpler than underlying AJ Service Objects Purpose-specific (here notification related) Notifications are sent/received as a ntfcnObject which has a number of data members (text in one or more languages, Icons, audio URL, msgId,…) and a dismiss() function

Impact on Resource Structure For some services frameworks or for some app-specific services, new resource types may be needed; for other existing resource types may be sufficient

Impact on TR-0014 Need to reflect difference in AllJoyn Services Frameworks versus app-specific AllJoyn service providers in resource structure TBD for exposing/injecting services See separate contribution