ISO/IEC 23093-2:2022

INTERNATIONAL ISO/IEC
STANDARD 23093-2
Second edition
2022-03
Information technology — Internet of
media things —
Part 2:
Discovery and communication API
Technologies de l'information — Internet des objets media —
Partie 2: API pour la découverte et la communication
Reference number
© ISO/IEC 2022
© ISO/IEC 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2022 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 APIs . 1
4.1 General . 1
4.2 Abstract Class of MThing . 7
4.2.1 General . 7
4.3 Return type class. 10
4.3.1 MThingInfoType . 10
4.3.2 MPEG21TerminalCapabilityType .12
iii
© ISO/IEC 2022 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
This second edition cancels and replaces the first edition (ISO/IEC 23093-2:2019), which has been
technically revised.
The main changes are as follows:
— modification of the introduction;
— addition of new APIs for discovery and communication;
— addition of a transaction model using state channels.
A list of all parts in the ISO/IEC 23093 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
iv
© ISO/IEC 2022 – All rights reserved

Introduction
The ISO/IEC 23093 series provides an architecture and specifies APIs and compressed representation
of data flowing between media things.
The APIs for the media things facilitate discovering other media things in the network, connecting and
efficiently exchanging data between media things. The APIs also support transaction tokens to access
valuable functionalities, resources, and data from media things.
Media things related information consists of characteristics and discovery data, setup information from
a system designer, raw and processed sensed data, and actuation information. The ISO/IEC 23093 series
specifies input and output data formats for media sensors, media actuators, media storages, media
analysers, etc. Media analysers can process sensed data from media sensors to produce analysed data,
and the media analysers can be cascaded in order to extract semantic information.
This document contains the APIs to discover media things in the network and communication between
media things and the APIs to facilitate transactions between media things.
The International Organization for Standardization (ISO) and International Electrotechnical
Commission (IEC) draw attention to the fact that it is claimed that compliance with this document may
involve the use of a patent.
ISO and IEC take no position concerning the evidence, validity and scope of this patent right.
The holder of this patent right has assured ISO and IEC that they are willing to negotiate licences under
reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this
respect, the statement of the holder of this patent right is registered with ISO and IEC. Information may
be obtained from the patent database available at www.iso.org/patents.
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights other than those in the patent database. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.
v
© ISO/IEC 2022 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 23093-2:2022(E)
Information technology — Internet of media things —
Part 2:
Discovery and communication API
1 Scope
This document specifies the abstract class of a media thing (MThing), which is a basic component to
construct the Internet of media things. The MThing class contains the basic APIs to:
— discover other MThing(s) in the network;
— connect/disconnect MThing(s);
— support transactions (e.g. payments) using media tokens between MThings.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 23093-1, Information technology — Internet of media things — Part 1: Architecture
ISO/IEC 23093-3:2019, Information technology — Internet of media things — Part 3: Media data formats
and API
ISO/IEC 21000-7:2007, Information technology — Multimedia framework (MPEG-21) — Part 7: Digital
Item Adaptation
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 23093-1 apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
4 APIs
4.1 General
This clause specifies APIs to discover MThings, and connect/disconnect communication between
MThings. Besides, APIs and return class types are specified to provide MThing information and
hardware descriptions.
An MThing can be discovered by its capabilities or supported media token types. The discovered
MThing(s) can then relay its (their) information to the requester (i.e. another MThing).
Figure 1 shows the process to discover MThings in the network by a required capability. Each MThing,
which supports the required capability, can send back its information. In the figure, an MThing
© ISO/IEC 2022 – All rights reserved

broadcasts a message using discoverMThingByCapability()to look for MSensors capable of capturing
audio (Figure 1, item 1). Each MSensor (e.g. MMicrophone1, MMicrophone2, MCamera1) sends back
its information using sendBackMThingInfo(), which returns the data format MThingInfo specified in
ISO/IEC 23093-3 (Figure 1, item 2).
Figure 2 shows the process of connecting MThings with a capability. First, an MThing (i.e. ReqMThing)
can ask the availability of the specific capability (e.g. SENSOR_CAPTURE_AUDIO) with the function
isCapabilityAvailable() to another MThing (Figure 2, item 1). If the capability “SENSOR_CAPTURE_
AUDIO” is currently unavailable, the MThing (i.e. MMicrophone1) notifies “unavailable” (Figure 2,
item 2). Then, the ReqMThing can ask the availability of the specific capability again to other MThings
(Figure 2, item 3) with the binary representation of “MSensor” and “SENSOR_CAPTURE_AUDIO”.
Because the MCamera1 notifies the ReqMThing that its “SENSOR_CAPTURE_AUDIO” capability
is available (Figure 2, item 4), the ReqMThing can connect to the camera and reserve its “SENSOR_
CAPTURE_AUDIO” capability (Figure 2, item 5). As long as the capability “SENSOR_CAPTURE_AUDIO”
of the MCamera1 is used by the ReqMThing, other MThings cannot access the corresponding capability.
Figure 1 — Discovering MThings by capability
Figure 2 — Connecting MThings based on a capability
© ISO/IEC 2022 – All rights reserved

Figure 3 shows the process of disconnecting (i.e. releasing capabilities of) an MThing. The ReqMThing
can release either all of its reserved capabilities of the MCamera (Figure 3, items 1 and 2) or a designated
capability (e.g. SENSOR_CAPTURE_AUDIO) (Figure 3, items 3 and 4) using disconnectMThing().
Figure 3 — Disconnecting an MThing
Figure 4 shows the process where an MThing alerts other MThings that all or some of its capabilities
will be unavailable. The MCamera can warn the MThing_01 that either all of the capabilities reserved
by MThing_01 are unavailable (Figure 4, items 1 and 2) or a designated capability (e.g.
SENSOR_CAPTURE_AUDIO) is no longer available to MThing_01 (Figure 4, items 3 and 4) using
alertDisconnection().
Figure 4 — Alerting disconnection to an MThing
© ISO/IEC 2022 – All rights reserved

Figure 5 — Transaction process between a user and an MThing
Figure 5 shows a sequence diagram of a transaction process between a user and an MThing. Suppose
that a user wants to watch a video captured from a nearby camera (i.e. MCamera). The user asks a
cost per minute to watch a video taken by the MCamera using getVideoURL_CostPerMinute(). Using
the user interface of Apps, DApps, or Web (Figure 5, item 1), the user can send desired media token
defined by tokenType (e.g. cryptocurrency or legal tender) and tokenName (e.g. Bitcoin or US dollar).
The MCamera returns the cost per minute to let the user use the getVideoURL() function (Figure 5,
item 2). If the user wants to watch the video with the responded price, they ask for a wallet address
(Figure 5, item 3) of the desired MToken. Again, the MCamera responds with the proper wallet address
(Figure 5, item 4). The user sends some MTokens to the wallet address through a payment system
like a blockchain or a banking system (Figure 5, item 5) which returns a transaction ID (Figure 5,
item 6). With this transaction ID (i.e. tid), the user can confirm (Figure 5, item 8) whether the token
transaction was completed to the designated wallet address or not (Figure 5, item 7) using checkTransa
ctionCompletion(tid). Once the transaction is confirmed, the user can ask for the video stream service
to the MCamera using getVideoURL(tid) (Figure 5, item 9). The MCamera checks for the completion
of the token transaction using checkTransactionCompletion(tid) (Figure 5, item 10) and the amount
of MTokens received (Figure 5, item 11). The MCamera returns a video URL and streams the video
as much as the user paid (Figure 5, item 12). The details of APIs, getVideoURL_CostPerMinute() and
getVideoURL() are given in ISO/IEC 23093-3.
Figure 6 shows a sequence diagram of a transaction process between MThings. Suppose that a camera
(i.e. MCamera) wants to stream a captured video to a nearby display (i.e. MDisplay) and play it. The
MCamera asks a cost per minute to play a video on the MDisplay using setVideoURL_CostPerMinute()
(Figure 6, item 1) with desired media token defined by tokenType (e.g. cryptocurrency or legal tender) and
tokenName (e.g. Bitcoin or US dollar). The MDisplay returns the cost per minute to use the setVideoURL()
function (Figure 6, item 2). If the MCamera wants to play the video with the responded price, it asks for a
wallet address (Figure 6, item 3) of the desired MToken. Again, the MDisplay responses with the proper
wallet address (Figure 6, item 4). The MCamera sends some MTokens to the wallet address through a
payment system like a blockchain or a banking system (Figure 6, item 5) which returns a transaction
ID (Figure 6, item 6). With this transaction ID (i.e. tid), th
...