OneM2M-ARC-2013-0365-Service_examples_and_evolution Service examples and evolution Group Name: WG2...

oneM2M-ARC-2013-0365-Service_examples_and_evolution

Service examples and evolutionGroup Name: WG2Source: Philip Jacobs, Cisco Systems, [email protected]; Joe Lenart, Hitachi CTA, [email protected] Date: 2013-08-29Agenda Item: Contributions


Service Extension Enabler1. Check module authentication2. Check node resources 3. Check interoperability with existing modules4. 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 module6. Add new service(s) due to new module to list of services 7. Modify API support to reflect new service capabilities8. 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?


What is a oneM2M service?

Service SUBCSF

SECCSF

GMG

CSF

DISCSF

DMRCSF

AID

CSF

CMDHCSF

DMGCSF

LOC

CSF

NSECSF

REG

CSF

SCACSF

SMGCSF

Application

Flows

#1 Used

Used Used Used Used - - - - - - - - Service#1.1Service#1.2Service#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


Example Service#1: Subscribe to a filter generated group with notification policy

• 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

Service#1.1

Service#1.2

Service#1.3

CSE


Application flows with CSE’s Subscription/Notification Resource

Service#1.1 App requests Sub/Notify resource to Create notification policyNot to be standardized example procedure initiated by Sub/Notify CSF:1.Sub/Notify CSF checks for system usage authorization with Security CSF2.Security CSF checks to see if App is OK, and returns OK response3.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 group2.Group Mgmt CSF asks Discovery CSF to identify group members3.Discovery CSF asks Data Mgmt CSF to check App’s rights against filtered resources, where OK Data Mgmt CSF returns filtered resources4.Discovery CSF returns group members per filter to Group CSF5.Group CSF returns filter generated group to Sub/Notify CSF6.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


Adding a new service n#:Subscribe to a filter generated group with notification policy including value criteria

Service SUBCSF

SECCSF

GMG

CSF

DISCSF

DMRCSF

AIDCSF

CMDHCSF

DMGCSF

LOC

CSF

NSECSF

REG

CSF

SCACSF

SMG

CSF

Analytics

CSF

Application

Flows

#1 Used

Used Used Used Used - - - - - - - - Service#1.1Service#1.2Service#1.3

#2

.

#m

#n Used

Used Used Used Used - - - - - - - - Used Service#n.1Service#n.2Service#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


Example Service#n: Subscribe to a filter generated group with notification policy including value criteria

Service#1.1

Service#1.2

Service#1.3

CSE

• 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


Application flows with CSE’s Subscription/Notification Resource for new service

#nService#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 CSF2.Security CSF checks to see if App is OK, and returns OK response3.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 group2.Group Mgmt CSF asks Discovery CSF to identify group members3.Discovery CSF asks Data Mgmt CSF to check App’s rights against filtered resources, where OK Data Mgmt CSF returns filtered resources4.Discovery CSF returns group members per filter to Group CSF5.Group CSF returns filter generated group to Sub/Notify CSF6.Sub/Notify CSF requests Analytics CSF to mark elements of group in Data Mgmt CSF when value > threshold7.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


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

OneM2M-ARC-2013-0365-Service_examples_and_evolution Service examples and evolution Group Name: WG2...

Documents

Transcript of OneM2M-ARC-2013-0365-Service_examples_and_evolution Service examples and evolution Group Name: WG2...