1. Proposed design principles for modelling interworked devices
ARC
Proposed design principles for modelling interworked devices
Group Name: ARC
Source: Joerg Swetina, NEC
Meeting Date:
Agenda Item: TBD

2. Backgroud It’s agreed in TP29
Devices should be represented in oneM2M uniformly for both oneM2M native device (ADN\ASN\MN) and oneM2M legacy device(NoDN)
Is it possible to stick to this agreement?
This contribution looks at some pros and cons and lists some open questions
It proposes to use both, <AE>s and specialized <flexContainer>s to represent AEs

3. Data provided via the IPE
An IPE is responsible for (the oneM2M view of) a complete area network, including NoDN devices.
Not specific to an individual device are:
Management information of the area network - if the area network is managed through the IPE and not through an external entity!
Network services (broadcast-like, telegrams to all..) if they exist
Specific to each individual device:
Management information of the NoDN devices
One or more Application Entities (i.e. service logic that is individually addressable) on the device.

4. Current state of the art (I)
Application Entity: represents an instantiation of Application logic for end-to-end M2M solutions
Node: logical entity that is identifiable in the oneM2M System
<node> resources are always child-resources of some CSEBase
<node> resources contain management information as child-resources (specializations of <mgmtObj>). E.g.:
[areaNwkInfo] (describes the list of Nodes attached to the area NW)
[areaNwkDeviceInfo], [deviceInfo], [firmware] … for individual devices
where the managed entity is an NoDN, the managed entities' <mgmObj> resources are hosted by the CSE of the node to which the managed entity is attached ???
An optional nodelink may exist from the <AE> to the <node> resource of the node on which the AE resides.
Note: In TS-0023 also mgmtLink exists from the <flexContainer> of a Device model to a [deviceInfo] resource that is a child of a <node> resource which one ?? hosted on the same hosting CSE of the <flexContainer>

5. Current state of the art (II)
An <AE> resource – of some AE on a ASN, ADN and NoDN – contains service related data as child-resources:
as (hierarchy of) <container>s and/or
specializations of <flexContainer>s.
Note that a ASN, ADN NoDN may contain multiple AEs on the same node!
<AE> representation of AE requires certain mandatory attributes:
Application Entity Identifier (AE-ID) uniquely identifies an AE within the M2M System. AE-ID is unique within that M2M Service Provider domain.
AE-ID-Stem is assigned by the Registrar CSE of the AE or
AE-ID-Stem is assigned by the M2M-SP. (unique within the M2M-SP Domain)
Application Identifier (App-ID) uniquely identifies an M2M Application There are two types of App-ID:
registration authority defined App-ID (registered App-ID) – which is globally unique Format: R{authority ID}.{reverseDNS}.{applicationName}
non-registered App-ID. Format: N{non-registered-App-ID}

6. Service subscription - is it an issue?
If AEs on a NoDN are represented by <AE>s can the IPE use its own <m2mServiceSubscriptionProfile> for registering allowed AEs ?
<m2mServiceSubscriptionProfile> resource on CSEBase contains child-resources: <serviceSubscribedNode>
<serviceSubscribedNode> contains
a list of deviceIdentifiers that uniquely identify the device
A list of ruleLinks to <serviceSubscribedAppRule>s
<serviceSubscribedAppRule> resource on CSEBase represents a rule that defines allowed App-ID and AE-ID combinations that are acceptable for registering an AE on a Registrar CSE

7. How do we represent a oneM2M native device?
Application Entity (AE) is the entity that executes all user defined logics
Multiple AEs can exist per device
Application is responsible for exposing the services and functions of a device
Application is linked to <node> resource to indicate the execution environment that application is running on.
Sub-Devices not forseen
CSEBase
AccessControlPolicy
Services provided by the application
Application Entity AE
[flex] Container AE
subscription AE
Common Service
[flex] container
remoteCSE
container
Services provided by the common service entity
contentInstance
subscription
flexContainer
node
device
mgmtObj

8. How can we represent an interworked device using <AE>s ?
IPE-<AE>
has child resources for Network services
Has nodeink to the IPE-<node> resource representing the area network
<node> of IPE
Links via areaNwInfo.listOfDevices and areaNwkDeviceInfo.devId to the <node>s of interworked devices
<AE>s of interworked devices
Have nodelink to their respective <node>
MISSING: Links from the IPE-<AE> to its interworked <AE>s
CSEBase
AccessControlPolicy
Network Services provided by the IPE
IPE
IPE-AE
[flex] Container
IPE-node
subscription
[flex] container AE
node AE AE
node

9. How can we represent an interworked device using <flexContainer>s ?
AEs of NoDN devices are mapped by IPE into customized child-resource <flexContainers> of the IPE-<AE>
The <flexContainer>s are linked to <mgmtObj> resources that are
child-resources under the IPE-<node> ? or
The IPE creates <node> resources not linked to any <AE> ?
or <flexContainer>s link to <node>s ?
CSEBase
AccessControlPolicy
AEs of devices
IPE-AE
moduleClasses
Sub-devices
flexContainer
flexContainer
flexContainer
flexContainer
flexContainer
flexContainer
flexContainer
IPE-node
device
mgmtObj
mgmtObj
mgmtObj

10. Questions
Assuming that interworked AEs can be represented both as <AE>s and customized <flexContainers>:
If AEs on a NoDN are represented by <AE>s
can the IPE use its own <m2mServiceSubscriptionProfile> for registering <AE>s ?
How can we link the <AE>s to the IPE-<AE> ?
if no AE of a NoDN is represented by an <AE> resource
can the IPE create a <node> resource for that device?
can that <node> be referenced by a <flexContainer> that represents the AE ?
How can <flexContainer>s that represent AEs be differentiated from <flexContainer>s that represent network services
Where are XSDs stored?