1. oneM2M-ARC-2013-0365-Service_examples_and_evolution Service examples and evolution Group Name: WG2 Source: Philip Jacobs, Cisco Systems, phjacobs@cisco.com; Joe Lenart, Hitachi CTA, joe.lenart@hitachi-cta.comphjacobs@cisco.com joe.lenart@hitachi-cta.com Meeting Date: 2013-08-29 Agenda Item: Contributions

2. oneM2M-ARC-2013-0365-Service_examples_and_evolution Service Extension Enabler 1.Check module authentication 2.Check node resources 3.Check interoperability with existing modules 4.Check policy and rights to determine how to handle conflicts e.g. Do not register new module or deregister existing module, etc. 5.Register new module 6.Add new service(s) due to new module to list of services 7.Modify API support to reflect new service capabilities 8.Modify inter-module communications to incorporate new module Editor’s Note: The above list is preliminary and is for FFS. Editor’s Note: How the Service Extension Enabler is associated with the APIs is FFS. Further study… first what is a oneM2M service and how does it relate to APIs?

3. oneM2M-ARC-2013-0365-Service_examples_and_evolution What is a oneM2M service? ServiceSUB CSF SEC CSF GMG CSF DIS CSF DM R CSF AI D CSF CMD H CSF DM G CSF LOC CSF NSE CSF REG CSF SCA CSF SMG CSF Applicatio n Flows #1Use d --------Service#1.1 Service#1.2 Service#1.3 #2. #m Services Offered A Service is expressed over an X or Y reference point as an API message referring to functions of one or more Common Service Functions (CSFs) Consider a service #1 “Subscribe to a filter generated group with notification policy” which uses 5 of 13 CSFs

4. oneM2M-ARC-2013-0365-Service_examples_and_evolution Example Service#1: Subscribe to a filter generated group with notification policy Discovery CSF Discovery CSF Group Mgmt CSF Security CSF Security CSF Sub/ Notify CSF Sub/ Notify CSF Each service is associated with 1 initiating CSF (shown green above) which orchestrates (not to be standardized) service request fulfillment with the other CSFs This example makes assumptions about CSF functionality which may be incorrect App Service#1.1 Service#1.2 Service#1.3 CSE Data Mgmt CSF Data Mgmt CSF

5. oneM2M-ARC-2013-0365-Service_examples_and_evolution Application flows with CSE’s Subscription/Notification Resource Service#1.1 App requests Sub/Notify resource to Create notification policy Not to be standardized example procedure initiated by Sub/Notify CSF: 1.Sub/Notify CSF checks for system usage authorization with Security CSF 2.Security CSF checks to see if App is OK, and returns OK response 3.Sub CSF creates notification policy resource Service#1.2 App requests Sub/Notify resource to set filter for group of target resources for notifications Not to be standardized example procedure initiated by Sub/Notify CSF: 1.Sub/Notify CSF asks Group Mgmt CSF to create group 2.Group Mgmt CSF asks Discovery CSF to identify group members 3.Discovery CSF asks Data Mgmt CSF to check App’s rights against filtered resources, where OK Data Mgmt CSF returns filtered resources 4.Discovery CSF returns group members per filter to Group CSF 5.Group CSF returns filter generated group to Sub/Notify CSF 6.Sub/Notify CSF subscribes App to Group Service#1.3 App requests Sub/Notify resource for notifications with group and policy to start 1.Sub/Notify CSF activates notification

6. oneM2M-ARC-2013-0365-Service_examples_and_evolution Adding a new service n#: Subscribe to a filter generated group with notification policy including value criteria Service SUB CSF SEC CSF GMG CSF DIS CSF DM R CSF AI D CSF CMD H CSF DM G CSF LOC CSF NSE CSF REG CSF SCA CSF SMG CSF Analytic s CSF Applicatio n Flows #1Use d -------- Service#1.1 Service#1.2 Service#1.3 #2. #m #nUse d -------- Service#n.1 Service#n.2 Service#n.3 Services Offered Consider that a new “Analytics” CSF becomes available on a CSE It allows a new service #n to become available “Subscribe to a filter generated group with notification policy including value criteria” which uses 6 of 14 CSFs

7. oneM2M-ARC-2013-0365-Service_examples_and_evolution Example Service#n: Subscribe to a filter generated group with notification policy including value criteria Discovery CSF Discovery CSF Group Mgmt CSF Security CSF Security CSF Sub/ Notify CSF Sub/ Notify CSF App Service#1.1 Service#1.2 Service#1.3 CSE Data Mgmt CSF Data Mgmt CSF Analytics CSF Analytics CSF Each service is associated with 1 initiating CSF (shown green above) which orchestrates (not to be standardized) service request fulfillment with the other CSFs This example makes assumptions about CSF functionality which may be incorrect

8. oneM2M-ARC-2013-0365-Service_examples_and_evolution Application flows with CSE’s Subscription/Notification Resource for new service #n Service#n.1 App requests Sub/Notify resource to Create notification policy Not to be standardized example procedure initiated by Sub/Notify CSF: 1.Sub/Notify CSF checks for system usage authorization with Security CSF 2.Security CSF checks to see if App is OK, and returns OK response 3.Sub CSF creates notification policy resource Service#n.2 App requests Sub/Notify resource to set filter for group of target resources for notifications with value criteria Not to be standardized example procedure initiated by Sub/Notify CSF: 1.Sub/Notify CSF asks Group Mgmt CSF to create group 2.Group Mgmt CSF asks Discovery CSF to identify group members 3.Discovery CSF asks Data Mgmt CSF to check App’s rights against filtered resources, where OK Data Mgmt CSF returns filtered resources 4.Discovery CSF returns group members per filter to Group CSF 5.Group CSF returns filter generated group to Sub/Notify CSF 6.Sub/Notify CSF requests Analytics CSF to mark elements of group in Data Mgmt CSF when value > threshold 7.Sub/Notify CSF subscribes App to Group including value criteria Service#n.3 App requests Sub/Notify resource for notifications with group, notification policy and value criteria to start Sub/Notify CSF activates notification

9. oneM2M-ARC-2013-0365-Service_examples_and_evolution Service Menu Resource Working Proposal Each CSE contains a service registry which lists the services it offers i.e. Service Menu Apps or other CSEs may read the service registry list The service registry documents dependencies – Application usage – CSE usage Services Extension Enabler maintains the service registry