ETSI TS 118 121 V2.0.1 (2020-03)

TECHNICAL SPECIFICATION
oneM2M;
oneM2M and AllJoyn® Interworking
(oneM2M TS-0021 version 2.0.1 Release 2A)

oneM2M TS-0021 version 2.0.1 Release 2A 2 ETSI TS 118 121 V2.0.1 (2020-03)

Reference
RTS/oneM2M-000021v2A
Keywords
interworking, IoT, M2M
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 3 ETSI TS 118 121 V2.0.1 (2020-03)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Conventions . 7
5 Architecture Model. 7
5.1 Reference model . 7
5.2 Composition of the IPE . 8
6 Architecture Aspect . 9
6.1 Introduction . 9
6.2 oneM2M resource mapping structure . 9
6.3 AllJoyn IPE registration . 13
6.4 AllJoyn service discovery . 14
6.5 AllJoyn service mapping . 14
6.5.1 AllJoyn service categorization . 14
6.5.2 AllJoyn base service mapping . 14
6.5.3 Other framework service mapping . 15
6.5.4 AllJoyn app-specific service mapping . 15
6.6 AllJoyn access control mapping . 15
7 Interworking Procedures . 15
7.1 Introduction . 15
7.2 IPE initial configuration . 15
7.2.1 Introduction. 15
7.2.2 IPE registration and AllJoyn service discovery . 15
7.2.3 AllJoyn Service Resource creation . 16
7.2.4 Subscription creation . 18
7.2.4.1 Subscription creation by AE/CSE(s) acting as service producers . 18
7.2.4.2 Subscription creation by entities acting as service consumers . 19
7.3 IPE interworking . 20
7.3.1 Introduction. 20
7.3.2 AllJoyn services consumed by AE/CSE(s) . 21
7.3.3 AllJoyn services produced by oneM2M AE/CSE(s) via the IPE . 21
7.3.4 AllJoyn services addition and deletion . 22
Annex A (informative): oneM2M and AllJoyn technical comparison . 23
A.1 API styles . 23
A.2 Service Discovery/Advertisement . 26
Annex B (normative): resource specializations . 27
B.1 Introduction . 27
B.2 Resource Type svcObjWrapper . 27
B.3 Resource Type svcFwWrapper . 28
B.4 Resource Type allJoynApp . 29
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 4 ETSI TS 118 121 V2.0.1 (2020-03)
B.5 Resource Type allJoynSvcObject . 32
B.6 Resource Type allJoynInterface . 34
B.7 Resource Type allJoynMethod . 36
B.8 Resource Type allJoynMethodCall . 37
B.9 Resource Type allJoynProperty . 39
Annex C (normative): AllJoyn interface mapping to oneM2M resource structure . 42
C.1 Notification service . 42
C.1.1 Notification interface . 42
C.1.2 Notification Producer interface . 43
C.1.3 Dismisser interface . 44
C.2 Control Panel service. 45
C.2.1 Container interface . 45
C.2.2 Property interface . 46
C.2.3 LabelProperty interface . 48
C.2.4 Action interface . 49
C.2.5 NotificationAction interface . 51
C.2.6 Dialog interface . 52
C.2.7 ListProperty interface . 55
C.3 Configuration service . 59
C.3.1 Config interface . 59
History . 62

ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 5 ETSI TS 118 121 V2.0.1 (2020-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M).
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 6 ETSI TS 118 121 V2.0.1 (2020-03)
1 Scope
The present document specifies the oneM2M and AllJoyn interworking technologies that enable AllJoyn Applications
and oneM2M entities produce/consume services.
Clause 5 defines the interworking architecture model that describes where the AllJoyn IPE is hosted and how the IPE is
composed with.
Clause 6 defines the architecture aspects that mainly describes AllJoyn services to oneM2M resource mapping structure
and rules. Furthermore, this explains the IPE registration and AllJoyn service discovery by the IPE.
Clause 7 defines the IPE interworking procedures that consists of the initial setup and the service interworking
procedures.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 118 101: "oneM2M; Functional Architecture (oneM2M TS-0001)".
[2] ETSI TS 118 104: "oneM2M; Service Layer Core Protocol Specification (oneM2M TS-0004)".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] oneM2M Drafting Rules.
NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.
[i.2] AllJoyn System Description.
[i.3] oneM2M TR-0014: "oneM2M and AllJoyn Interworking".
[i.4] D-Bus Tutorial.
NOTE: Available at http://dbus.freedesktop.org/doc/dbus-tutorial.html#objects.
[i.5] AllJoyn Gateway Agent High Level Description(HLD).
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 7 ETSI TS 118 121 V2.0.1 (2020-03)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
AllJoyn application: application that either produces an AllJoyn service or consumes an AllJoyn service
AllJoyn consumer application: role of an AllJoyn application that consumes AllJoyn services provided by other
AllJoyn applications
AllJoyn producer application: role of an AllJoyn application that produces AllJoyn services consumed by other
AllJoyn applications
AllJoyn service resources: resources created as children of an resource representing an AllJoyn IPE for the
purpose of exposing services between AllJoyn Consumer/Producer Applications and AE/CSE entities
3.2 Symbols
Void.
3.3 Abbreviations
Void.
4 Conventions
The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be
interpreted as described in the oneM2M Drafting Rules [i.1].
5 Architecture Model
5.1 Reference model
The architecture model followed in the present document is based on the architecture model in annex F of ETSI
TS 118 101 [1] that describes how interworking between oneM2M CSEs and non-oneM2M systems using specialized
Interworking Proxy application Entities (IPE). The present document describes the AllJoyn IPE that supports the
following reference model.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 8 ETSI TS 118 121 V2.0.1 (2020-03)
AE
AllJoyn Application
AllJoyn Protocol
AllJoyn IPE
Mca
Mca
Mcc/Mcc’
CSE CSE
ASN/MN/IN MN/IN
Figure 5.1-1: AllJoyn interworking reference model
This reference model describes how the oneM2M AEs can interwork with AllJoyn applications. By the IPE, AllJoyn
services are exposed as oneM2M resources and stored in a CSE. AEs access the exposed AllJoyn service resources by
the oneM2M APIs.
5.2 Composition of the IPE
The AllJoyn IPE consists of AE and AllJoyn application. To provide the interworking functions to other oneM2M
entities, the IPE registers to a CSE and communicate with other AllJoyn applications using AllJoyn protocols. The IPE
registration is mandatory in oneM2M systems which is not defined in AllJoyn system. AllJoyn discovery and session
establishment are needed for the IPE to communicate with other AllJoyn applications.
In figure 5.2-1, AllJoyn Application on the AllJoyn device and AllJoyn IPE is either AllJoyn Consumer or Producer
Application. Depending on the interworking service scenario, AllJoyn Consumer and/or Producer Application is hosted
on AllJoyn devices and AllJoyn IPEs. For example, when a AllJoyn service is consumed by oneM2M entities, an
AllJoyn devices hosts AllJoyn Producer Application and AllJoyn IPE hosts AllJoyn Consumer Application. In other
case, if a oneM2M entity provides data to be consumed by AllJoyn Consumer Application on an AllJoyn device, then
the AllJoyn IPE hosts AllJoyn Producer Application and the AllJoyn device hosts AllJoyn Consumer Application.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 9 ETSI TS 118 121 V2.0.1 (2020-03)
AllJoyn Application
AllJoyn Device
AllJoyn
Protocol
AllJoyn Application
AE
AllJoyn IPE
Mca
CSE
Figure 5.2-1: Composition of the AllJoyn IPE
6 Architecture Aspect
6.1 Introduction
oneM2M and AllJoyn have different architecture aspects (annex A oneM2M and AllJoyn technical comparison). The
present document specifies the interworking functions for those differences in the following aspects:
• oneM2M resource mapping structure;
• AllJoyn IPE registration;
• AllJoyn service discovery;
• AllJoyn service mapping;
• AllJoyn access control mapping.
6.2 oneM2M resource mapping structure
In this clause, the overall resource mapping structure for exposing service between AllJoyn Applications(either
Producer or Consumer) and oneM2M entities is introduced. Since it is difficult to put the resource tree into a single
figure that remains well-readable, the description is split up in multiple figures, In this description, not all specified
attributes of the used resource types and not all possible child resources are depicted to keep the figures readable, For
example resources which may be used to subscribe to some of the depicted resources are not shown.
The resource mapping structure uses some specializations of the resource. Each of this specialization is
detailed in annex B.
The use of each of the resources within the resource mapping structure for consuming or producing services is defined
in detail in clause 7.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 10 ETSI TS 118 121 V2.0.1 (2020-03)
Resource Type /
Naming value of l abe ls
Specialization
variable
1. .n
variable “AllJoyn-IPE”
1 “Iwked-Technology:AllJoyn”,
svcObjects fixed
“Iwked-Entity-Type:SvcObjects
[svcObjWrapper]
“Iwked-Technology:AllJoyn”,
svcFrameWorks fixed
“Iwked-Entity-Type:SvcFrameWorks”
[svcFwWrapper]
0. .n Not including
variable
“AllJoyn-IPE”
Figure 6.2-1: AllJoyn interworking resource mapping, part 1
In figure 6.2-1, the first part of the resource mapping structure for AllJoyn interworking is depicted. The
resource of a CSE that is used for connecting to an AllJoyn proximal network is the root of the resource mapping
structure.
The IPE responsible for AllJoyn interworking - see the reference model described in clause 5 - will register with that
CSE and will create an resource which represents the IPE. This resource shall include the string "AllJoyn-
IPE" in the labels attribute. All other relevant AllJoyn interworking resources will be hosted as children or descendants
of this resource. For convenience, this is termed "IPE" in what follows. In figure 6.2-1 the multiplicity of
the resource is defined to be equal to 1.n. Since it is assumed that the CSE represented by the
resource depicted in figure 6.2-1 supports AllJoyn interworking, at least one resource representing an AllJyon
IPE shall exist. When the IPE registers with an ASN-CSE or an MN-CSE, the multiplicity shall be 1. This does not
imply that no other application can register with that CSE. It is only meant to define that only one will act as an
IPE for AllJoyn interworking on this CSE. As depicted in figure 6.2-1, other resources - not including the string
"AllJoyn-IPE" in the value of the labels attribute can occur with multiplicity 0.n. On the other hand, when the IPE
registers with IN-CSE, the multiplicity shall be 1.n to allow interworking with multiple different AllJoyn proximal
networks. In figure 6.2-1, and in the following figures two specializations of called "svcObjWrapper"
and "svcFwWrapper" are used. These specializations of do not contain any custom attributes. They
serve only as wrappers for other resources in order to structure the resource tree allowing subscriptions to be made to
that part of the tree. See annex B for further details on the [svcObjwrapper] and [svcFwWrapper] specialization of
.
Two child resources of the resource representing the IPE are depicted in figure 6.2-1:
• A resource with a fixed name "svcObjects": It serves as a wrapper for hosting resources that are used to expose
services based on the AllJoyn service object model, see also oneM2M TR-0014 [i.3] for details on AllJoyn
service objects. Service Objects in AllJoyn contain one or more AllJoyn interfaces that are used to interact
with services. The resource structure under this [svcObjWrapper] resource called "svcObjects" allows for
direct interaction with AllJoyn interfaces via corresponding resources.
• A resource with a fixed name "svcFrameWorks": It serves as a wrapper for hosting resources that are used to
expose services based on some higher level AllJoyn service frameworks, see also oneM2M TR-0014 [i.3] for
details on AllJoyn service frameworks. AllJoyn service frameworks typically offer a simpler API to
programmers for making use of services compared to operating directly on the AllJoyn interfaces within
AllJoyn service objects. An example for such a service framework is the Lighting Services Framework (LSF)
in AllJoyn. The resource structure under this [svcFwWrapper] resource called "svcFrameWorks" allows use of
functions in selected AllJoyn service frameworks via corresponding resources.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 11 ETSI TS 118 121 V2.0.1 (2020-03)
Naming Resource Type value of labels
“Iwked-Technology:AllJoyn”,
svcObjects fixed
“Iwked-Entity-Type:SvcObjects”
[svcObjWrapper]
0.n “Iwked-Technology:AllJoyn”,
variable
[allJoynApp]
“Iwked-Entity-Type:App”
[allJoynApp]
direction
“Iwked-Technology:AllJoyn”,
1.n

“Iwked-Entity-Type:
[allJoynSvcObject] variable
[allJoynSvcObject]
ServiceObject”
objectPath
enabled
1.n
“Iwked-Technology:AllJoyn”,
[allJoynInterface] variable
“Iwked-Entity-Type:Interface”
[allJoynInterface]
Figure 6.2-2: AllJoyn interworking resource mapping, part 2
In figure 6.2-2, the second part of the AllJoyn interworking resource mapping is depicted. It describes the structure of
resources hosted under the [svcObjWrapper] resource named "svcObjects".
For each AllJoyn application providing a service that is supposed to be exposed by the IPE via resources under the
"svcObjects" [svcObjWrapper] resource and for all external services that shall be injected into the AllJoyn proximal
network by the IPE, a separate child resource is created which is a [allJoynApp] specialization of . The
details of this [allJoynApp] specialization of are defined in annex B.
The [allJoynApp] specialization of contains a custom attribute direction, which indicates whether the
service is exposed from the AllJoyn side to the oneM2M side (value equal to "allJoynToOneM2m") or vice versa (value
equal to "oneM2mToAllJoyn"). At most one of the [allJoynApp] child resources under the "svcObjects"
[svcObjWrapper] resource can have a direction set to "oneM2mToAllJoyn". For that particular [allJoynApp] - if present
- the IPE acts as a service producer application at the AllJoyn side. It is the IPE's responsibility to create the
[allJoynApp] resources under the "svcObjects" [svcObjWrapper] resource including:
• One [allJoynApp] specialization of resource for each AllJoyn application providing a service
that is supposed to be exposed by the IPE towards oneM2M entities. The name of each of these [allJoynApp]
specialization shall be set to the unique Well-Known-Name (WKN) [i.2] of the corresponding AllJoyn
application. The value for the direction attribute shall be set to "allJoynToOneM2m".
• One [allJoynApp] specialization of resource representing the IPE itself as an AllJoyn
Producer Application hosted by the IPE - in case the IPE supports exposure of services provided by oneM2M
AEs to AllJoyn applications. The name of this [allJoynApp] specialization of shall be set to
the Well-Known-Name (WKN) of the IPE on the AllJoyn bus. The value for the direction attribute shall be set
to "oneM2mToAllJoyn".
Each [allJoynApp] resource will contain one or more [allJoynSvcObject] child resources, which are specializations of
resources representing AllJoyn service objects. Details of the [allJoynSvcObject] specialization of
are defined in annex B. The [allJoynSvcObject] specialization of contain two custom
attributes:
• objectPath: This is a string equal to the AllJoyn object path for the represented AllJoyn service object.
• enabled: This is a flag indicating whether the resource representing the corresponding AllJoyn service object is
currently enabled for service exposure. This is needed since the structure in this resource needs to be created in
multiple steps (creation of children and children of children in this resource structure). During initialization of
the resource structure under a specific [allJoynSvcObject] resource, the attribute enabled shall be set to False
as it is not ready for use. Once the initialization is complete and the resource structure can be used for service
interactions, the enabled flag shall be set to True.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 12 ETSI TS 118 121 V2.0.1 (2020-03)
The naming of [allJoynSvcObject] is up to the IPE. It would seem logical to derive names from the object path of the
corresponding AllJoyn service object, but due to characters like a slash "/" appearing in object paths, it is not possible to
use the exact same string as a name for the corresponding [allJoynSvcObject] resource.
Each AllJoyn service object contains one or more interfaces. This is reflected in the AllJoyn interworking resource
structure by the presence of one or more [allJoynInterface] specializations of under each
[allJoynSvcObject] resource. Details of the [allJoynInterface] specializations of resources are defined
in annex B. The basic structure under each [allJoynInterface] resource is depicted in figure 6.2-3.
Naming Resource Type value of “labels”

“Iwked-Technology:AllJoyn”,
[allJoynInterface] variable
“Iwked-Entity-Type:Interface”
allJoynInterface
interf a ceIntro sp ectXml R e f
0.n
“Iwked-Technology:AllJoyn”,

variable
[allJoynMethod]
“Iwked-Entity-Type:Method”
allJoynMethod
0.n
“Iwked-Technology:AllJoyn”,

variable
[allJoynMethodCall]
“Iwked-Entity-Type:MetodCall”
allJoynMethodCall
0.1
input
0.1
callStatus
0.1
output
0.n
“Iwked-Technology:AllJoyn”,
[allJoynProperty] variable
“Iwked-Entity-Type:Property”
allJoynProperty
currentValue
0.1
requestedValue
0.n
“Iwked-Technology:AllJoyn”,
variable

“Iwked-Entity-Type:Signal Name”
0.n

Figure 6.2-3: AllJoyn interworking resource mapping, part 3
[allJoynInterface] specializations of contain one custom attribute interfaceIntrospectXmlRef which
refers to the AllJoyn interface definition in XML. AllJoyn interfaces consist of methods, properties and signals. In the
AllJoyn interworking resource structure, methods are represented by [allJoynMethod] resources which are a
specialization of . Properties are represented by [allJoynProperty] resources which are a specialization
of . Signals are represented by regular resources. All specializations of
resources are defined in annex B. [allJoynMethod] resources shall be named with the same string as the method is
named in the AllJoyn interface definition. [allJoynProperty] resources shall be named with the same string as the
property is named in the AllJoyn interface definition.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 13 ETSI TS 118 121 V2.0.1 (2020-03)
Since different calling instances of AllJoyn interface methods need to be distinguishable in terms of input, output and
call status, the interworking resource structure for methods includes zero or more [allJoynMethodCall] resources used
to represent individual calling instances of a method. For each call of a method, the consumer of the service needs to
create a new instance of a [allJoynMethodCall] resource. In cases where the corresponding AllJoyn method requires
inputs, the input attribute needs to be present and contain a valid serialization of input parameters to the method call.
The entity which acts on creation of a new [allJoynMethodCall] resource - i.e. the IPE in case of a service exposed from
AllJoyn to oneM2M or another AE in case of exposing a service from oneM2M to AllJoyn - needs to perform the
requested method call and populate the callStatus attribute with corresponding status information. Upon completion of
the action taken, the ouput attribute shall get populated with the corresponding output of the method call - if any. Note
that some AllJoyn methods do not return an output upon completion of a call.
AllJoyn properties are represented by [allJoynProperty] resources. The attribute currentValue is representing the current
value of the property. When the property is capable of being changed, the attribute requestedValue shall be used to
request a change to a new value. Upon completion of such a change request, the IPE or the service providing AE will
update the new value of the property in the attribute currentValue.
Naming Resource Type value of labels
“Iwked-Technology:AllJoyn”,
svcF ra meWor ks fixed
[svcFwWrapper] “Iwked-Entity-Type:SvcFrameWorks”
0.n
[name of specific AllJoyn
variable

specific to service FW service frame work]

Figure 6.2-4: AllJoyn interworking resource mapping, part 4
For exposure of AllJoyn service frameworks using higher level APIs that are not directly interacting with AllJoyn
service objects and interfaces, separate resources are used under the [svcFwWrapper] resource named
"svcFrameWorks". For each supported service framework with a higher level API, a separate specialization of a
resource shall be created as a child resource under "svcFrameWorks" in which the labels attribute
includes a string equal to the name of the service framework. An example for an AllJoyn service framework that could
be exposed in this part of the resource structure is the "Lighting Services Framework" (LSF).
Since each service framework will have different services and methods associated with it, a separate definition of the
resource structure for that service framework is needed. Supported service frameworks are FFS.
6.3 AllJoyn IPE registration
To start oneM2M-AllJoyn interworking, the IPE shall perform AE registration procedure to the a CSE specified in
ETSI TS 118 101 [1]. To stop using the interworking function, IPE shall perform AE de-registration procedure.
The IPE shall be represented as the resource as follows.
Table 6.3-1: Attribute values of IPE resource
Attribute Value Description
resourceType Enumeration value for the AE resource type
"2"
labels "AllJoyn-IPE" IPE for AllJoyn interworking

For each AllJoyn proximal network, only one IPE handles interworking between oneM2M entities and AllJoyn
Applications. An ASN-CSE or MN-CSE shall accept at most one AllJoyn IPE. However, an IN-CSE may accept more
than one AllJoyn IPE registration(s) to allow multiple AllJoyn proximity network interworking.
After the registration, the IPE may perform AllJoyn service discovery.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 14 ETSI TS 118 121 V2.0.1 (2020-03)
6.4 AllJoyn service discovery
After the IPE registration, the IPE performs AllJoyn service discovery. The IPE may provide the following AllJoyn
service discovery modes:
• Advertisement-based discovery mode: This modes utilizes AllJoyn multicast service advertisement. When the
IPE gets service advertisements from AllJoyn service provider applications in an AllJoyn proximal network,
the IPE can expose those services in oneM2M system without oneM2M AE's request.
• Pre-configured (IPE initiated) discovery mode: This mode utilizes AllJoyn multicast service discovery.
Interested AllJoyn services are pre-configured in the IPE (e.g. by M2M Service Provider), so the discovery is
performed automatically once the IPE registration is complete.
• On-demand (AE initiated) discovery mode: This mode utilizes AllJoyn multicast service discovery. Interested
Alljoyn services are requested by oneM2M AEs, so the discovery is performed upon AE's service discovery
request.
Selection of supported mode(s) is implementation specific.
After the successful AllJoyn service discovery, the discovered services - if and only if allowed by the AllJoyn side
(e.g. in line with provisioned policies on an AllJoyn Gateway Agent) - shall be exposed as oneM2M resources. When
new services are discovered on the AllJoyn side after initial service discovery has already been completed by the IPE,
the IPE can add those additional services to the set of exposed services by means of dynamically creating the
corresponding resources on the CSE at which the IPE is registered. See clause 7 for more details.
6.5 AllJoyn service mapping
6.5.1 AllJoyn service categorization
AllJoyn services can be categorized into:
• AllJoyn framework services (pre-defined by AllJoyn service framework).
• App-specific services (implemented using application developer defined AllJoyn interfaces).
AllJoyn framework services are pre-defined and can be sub-categorized into two: base services (e.g. Notification,
Control Panel) and the other framework services (e.g. Lighting service framework). The base services have relatively
simple interface member composition so they can be easily mapped with the resource structure defined in clause 6.2
under the [svcObjWrapper] specialization of . For a subset of the AllJoyn base services, a normative
resource mapping is specified in annex C. Selected other AllJoyn framework services - i.e. not the base services - shall
be exposed using separate resource structures and this is FFS.
6.5.2 AllJoyn base service mapping
The list of AllJoyn base services [i.2]:
• OnBoarding.
• Configuration.
• Notification.
• ControlPanel.
• Audio Streaming.
The present document specifies base services mapping for Configuration, Notification, ControlPanel. See annex C for
the AllJoyn base services mapping.
For Configuration, Notification or ControlPanel services which are discovered on the AllJoyn side and are intended to
be exposed to the oneM2M side, the mapping specified in annex C is normative.
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 15 ETSI TS 118 121 V2.0.1 (2020-03)
OnBoarding service is intended to support AllJoyn network onboarding (Wi-Fi connection support) for the device that
does not have user interface. This is out of scope for oneM2M interworking.
Audio Streaming is also out of scope since oneM2M system does not support in-band streaming feature.
6.5.3 Other framework service mapping
For example, AllJoyn Lighting Services Framework mapping can be specified as described in the figure 6.2-4.
However, this is not specified in the present document.
6.5.4 AllJoyn app-specific service mapping
rd
App-specific services implement AllJoyn interface(s) defined by 3 party developers. In the AllJoyn system, the
introspection feature can be used to deliver interface information of an AllJoyn Producer Application to AllJoyn
Consumer Applications. Mapping for AllJoyn app-specific services shall follow the resource mapping structure in
clause 6.2 and the resource specializations in annex B.
6.6 AllJoyn access control mapping
AllJoyn security 1.0 feature supports authentication and encryption, but not authorization.
AllJoyn security 2.0 feature supports permission management (authorization), which is similar to oneM2M access
control mechanism, as well as authentication and encryption.
NOTE: The present document does not specify AllJoyn security 2.0 interworking.
7 Interworking Procedures
7.1 Introduction
The interworking procedures describe the following:
• how does the IPE initially creates necessary resources for oneM2M-AllJoyn interworking (clause 7.2);
• how does the IPE performs interworking between the oneM2M system and AllJoyn networks depending on
the service exposure direction (clause 7.3).
7.2 IPE initial configuration
7.2.1 Introduction
The initial configuration of the IPE consists of registration with its Registrar CSE and resource creation procedures. As
part of registration, an resource is created to represent the AE part of the IPE. After that, AllJoyn-specific
resources to support interaction between oneM2M AE/CSE(s) and AllJoyn Consumer and/or Producer Applications as
well as necessary resources are created by the IPE.
The IPE shall process incoming notifications from the oneM2M CSEs which have been triggered by the created
resources and react to them by executing the appropriate actions to the interworked AllJoyn Consumer
and/or Producer Applications. Accordingly, the IPE shall react to messages received from interworked AllJoyn
Consumer and/or Producer Applications that are relevant to the exposed services and do any necessary changes to the
resources defined for AllJoyn interworking within the oneM2M CSE.
7.2.2 IPE registration and AllJoyn service discovery
For the interworking, firstly the IPE shall perform IPE registration (see clause 6.3). The 'labels' attribute shall include
the string "AllJoyn-IPE".
ETSI
oneM2M TS-0021 version 2.0.1 Release 2A 16 ETSI TS 118 121 V2.0.1 (2020-03)
If the IPE is set to advertisement-based or pre-configured discovery mode (see clause 6.4), the AE in the IPE shall
create and expose resources corresponding to the exposed services (see clause 6.2) once the AllJoyn Application in the
IPE completes AllJoyn service discovery and session establishment with AllJoyn Producer Applications referring its
AllJoyn service objects.
If the IPE is set to on-demand discovery mode (see clause 6.4), the IPE shall perform the same procedure above
(i.e. advertisement-based or pre-configured discovery mode) when it receives a Notify request for on-demand discovery
(see clause 10.2.6.2 of ETSI TS 118 101 [1]) by its Registrar CSE and then create and expose resources corresponding
to the exposed services.
Which resources are created for service exposure from AllJoyn Producer Application to oneM2M AE/CSE(s) is
described in more detail in the clauses 7.2.3 and 7.2.4.
If the IPE supports exposure of services provided by other oneM2M AE/CSE(s) to AllJoyn Consumer Applications, the
IPE shall create one instance of an [allJoynApp] specialization of the resource representing the AllJoyn
Producer Application inside the IPE itself (see clause 6.2). Other AE/CSE(s) providing services that are meant to be
exposed to AllJoyn Consumer Applications on AllJoyn devices shall use that [allJoynApp] resource representing the
AllJoyn Producer Application part inside the IPE itself as the parent of any [allJoynInterface] resources they may create
for offering a service(s) to the AllJoyn Consumer Applications. The particular [allJoynApp] resource representing the
AllJoyn Producer Application inside the IPE itself shall be identified by the value of the direction attribute which is set
t
...