ISO/IEC FDIS 23093-2

Information technology — Internet of media things — Part 2: Discovery and communication API

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.

Technologies de l'information — Internet des objets media — Partie 2: API pour la découverte et la communication

General Information

• Status: Not Published
• ICS: 35.040.40 - Coding of audio, video, multimedia and hypermedia information
• Technical Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Drafting Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Current Stage: 5020 - FDIS ballot initiated: 2 months. Proof sent to secretariat
• Start Date: 10-Sep-2025
• Completion Date: 10-Sep-2025

Relations

• Revises: ISO/IEC 23093-2:2022 - Information technology — Internet of media things — Part 2: Discovery and communication API
• Effective Date: 28-Jan-2023

Standards Content (Sample)

FINAL DRAFT
International
Standard
ISO/IEC
FDIS
23093-2
ISO/IEC JTC 1/SC 29
Information technology — Internet
Secretariat: JISC
of media things —
Voting begins on:
2025-09-10
Part 2:
Discovery and communication API
Voting terminates on:
2025-11-05
Technologies de l'information — Internet des objets media —
Partie 2: API pour la découverte et la communication
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/IEC FDIS 23093­2:2025(en) © ISO/IEC 2025

FINAL DRAFT
International
Standard
ISO/IEC
FDIS
23093-2
ISO/IEC JTC 1/SC 29
Information technology — Internet
Secretariat: JISC
of media things —
Voting begins on:
Part 2:
Discovery and communication API
Voting terminates on:
Technologies de l'information — Internet des objets media —
Partie 2: API pour la découverte et la communication
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO/IEC 2025
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ISO/IEC FDIS 23093­2:2025(en) © ISO/IEC 2025

© ISO/IEC 2025 – All rights reserved
ii
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.2.2 MThing APIs .7
4.3 Return type class.10
4.3.1 MThingInfoType .10
4.3.2 MPEG21TerminalCapabilityType . 12

© ISO/IEC 2025 – All rights reserved
iii
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialised system for worldwide standardisation. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organisation to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other international organisations,
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).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
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 third edition cancels and replaces the second edition (ISO/IEC 23093-2:2022), which has been
technically revised.
The main changes are as follows:
— modification of the Introduction;
— addition of new APIs for discovery and communication.
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.

© ISO/IEC 2025 – All rights reserved
iv
Introduction
The ISO/IEC 23093 series provides an architecture and specifies APIs and compressed representation of
data flowing between media things (MThings).
The APIs for MThings facilitate the discovery of other MThings in the network, as well as the connection and
efficient exchange of data between MThings. The APIs also support transaction tokens to access valuable
functionalities, resources, and data from MThings.
MThing-related information comprises characteristics and discovery data, mission descriptions from system
designers and end-users, raw and processed sensed data and actuation information. The ISO/IEC 23093
series specifies input and output data formats for media sensors, actuators, storages, and analysers. In
addition, media analysers can process sensed data from media sensors to produce analysed data, which can
be cascaded to other media analysers to extract semantic information. Multiple MThings can be gathered
and operated autonomously using mission descriptions given by system designers and end-users.
This document contains the APIs to discover media things in the network, communication between media
things, and the APIs to facilitate transactions between media things.

© ISO/IEC 2025 – All rights reserved
v
FINAL DRAFT International Standard ISO/IEC FDIS 23093-2:2025(en)
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), 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); and,
— 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, 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 standardisation 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 of discovering MThings in the network by a required capability. Each MThing
supports the required capability and can send back its information. In the figure, an MThing broadcasts a
message using discoverMThingByCapability()to look for MSensors capable of capturing audio (Figure 1,

© ISO/IEC 2025 – All rights reserved
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 for 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 ReqMThing uses the capability “SENSOR_CAPTURE_AUDIO” of the MCamera1, other
MThings cannot access the corresponding capability.
Figure 1 — Discovering MThings by capabilities
Figure 2 — Connecting MThings based on a capability

© ISO/IEC 2025 – 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 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 2025 – 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 a user
wants to watch a video captured from a nearby camera (i.e. M
...

MUST BE USED MUST BE USED
FOR FINAL FOR FINAL
ISO/IEC JTC 1/SC 29/WG 7 N01157

ISO/IEC JTC 1/SC 29/WG 7
MPEG 3D Graphics Coding
Convenorship: AFNOR (France)
Document type: Output Document

rd
Title: Text of ISO/IEC FDIS 23093-2 3 edition Discovery and
communication API
Status: Approved
Date of document: 2025-05-15
Source: ISO/IEC JTC 1/SC 29/WG 7

Expected action: None
Action due date: None
No. of pages: (with the cover page)

Email of Convenor: [e-mail]

Committee URL:
INTERNATIONAL ORGANISATION FOR STANDARDISATION
ORGANISATION INTERNATIONALE DE NORMALISATION
ISO/IEC JTC 1/SC 29/WG 7 MPEG 3D GRAPHICS CODING

ISO/IEC JTC 1/SC 29/WG 7 N01157
Apr. 2025, Online
Title Text of ISO/IEC FDIS 23093-2 3rd edition Discovery and communication API
Source WG 7, MPEG 3D Graphics Coding, Sang-Kyun Kim (Myongji University)
Status Approved
Serial Number 25110
Date: 2025-05-15
ISO/IEC JTC 1/SC 29
Secretariat: JISC
Date: 2025-08-27
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 decouvertedécouverte et la communication

© FDIS stage
MUST BE USED MUST BE USED
FOR FINAL FOR FINAL
FINAL DRAFT International Standard ISO/IEC FDIS 23093-2:2025(en)

© ISO/IEC 2024 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
may be reproduced or utilisedutilized otherwise in any form or by any means, electronic or mechanical, including
photocopying, or posting on the Internetinternet 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
EmailE-mail: [e-mail]
Website: www.iso.org
Published in Switzerland
MUST BE USED
FOR FINAL
Contents Page
Foreword . viii
Introduction . ix
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 . 12
4.3 Return type class . 15

Foreword . vii
Introduction . viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 APIs . 1
MUST BE USED
FOR FINAL
© ISO/IEC 2025 – All rights reserved
vii
ISO/IEC DIS FDIS 23093-2:2024(E2025(en)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialised system for worldwide standardisation. National bodies that are members
of ISO or IEC participate in the development of International Standards through technical committees
established by the respective organisation to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organisations, 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).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of
(a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had received notice
of (a) patent(s) which may be required to implement this document. However, implementers are cautioned
that this may not represent the latest information, which may be obtained from the patent database available
at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for identifying
any or all such patent rights.
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 third edition cancels and replaces the firstsecond edition (ISO/IEC 23093-2:2022), which has been
technically revised.
The main changes are as follows:
— — modification of the Introduction;
— — addition of new APIs for discovery and communication.
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.
8 © ISO/IEC 2023 – All rights reserved
© ISO/IEC 2025 – All rights reserved
viii
Introduction
The ISO/IEC 23093 series provides an architecture and specifies APIs and compressed representation of data
flowing between media things (MThings).
The APIs for MThings facilitate the discovery of other MThings in the network, as well as the connection and
efficient exchange of data between MThings. The APIs also support transaction tokens to access valuable
functionalities, resources, and data from MThings.
MThing-related information comprises characteristics and discovery data, mission descriptions from system
designers and end-users, raw and processed sensed data and actuation information. The ISO/IEC 23093 series
specifies input and output data formats for media sensors, actuators, storages, and analysers. In addition,
media analysers can process sensed data from media sensors to produce analysed data, which can be cascaded
to other media analysers to extract semantic information. Multiple MThings can be gathered and operated
autonomously using mission descriptions given by system designers and end-users.
This document contains the APIs to discover media things in the network, communication between media
things, and the APIs to facilitate transactions between media things.
MUST BE USED
FOR FINAL
© ISO/IEC 2025 – All rights reserved
ix
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), 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); and,
— — 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, 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 standardisation 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 1Figure 1 shows the process of discovering MThings in the network by a required capability. Each
MThing supports the required capability and can send back its information. In the figure, an MThing
broadcasts a message using discoverMThingByCapability()to look for MSensors capable of capturing
audio (Figure 1(Figure 1,, item 1). Each MSensor (e.g. MMicrophone1, MMicrophone2, MCamera1) sends back
© ISO/IEC 2025 – All rights reserved
its information using sendBackMThingInfo(), which returns the data format MThingInfo specified in
ISO/IEC 23093-3 (Figure 1, item 2).
Figure 2Figure 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(Figure 2,, item 1). If the capability
“SENSOR_CAPTURE_AUDIO” is currently unavailable, the MThing (i.e. MMicrophone1) notifies “unavailable”
(Figure 2(Figure 2,, item 2). Then, the ReqMThing can ask for the availability of the specific capability again to
other MThings (Figure 2(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(Figure 2,, item 4), the ReqMThing can connect to
the camera and reserve its “SENSOR_CAPTURE_AUDIO” capability (Figure 2(Figure 2,, item 5). As long as the
ReqMThing uses the capability “SENSOR_CAPTURE_AUDIO” of the MCamera1, other MThings cannot access
the corresponding capability.
Figure 1 — Discovering MThings by capabilities
© ISO/IEC 2025 – All rights reserved
Figure 2 — Connecting MThings based on a capability
Figure 3Figure 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(Figure 3,, items 1 and 2) or a
designated capability (e.g. SENSOR_CAPTURE_AUDIO) (Figure 3(Figure 3,, items 3 and 4) using
disconnectMThing().
© ISO/IEC 2025 – All rights reserved
Figure 3 — Disconnecting an MThing
Figure 4Figure 4 shows the process where 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(Figure 4,, items 1 and 2) or a designated capability (e.g.
SENSOR_CAPTURE_AUDIO) is no longer available to MThing_01 (Figure 4(Figure 4,, items 3 and 4) using
alertDisconnection().
© ISO/IEC 2025 – All rights reserved
Figure 4 — Alerting disconnection to an MThing
© ISO/IEC 2025 – All rights reserved
Figure 5 — Transaction process between a user and an MThing
Figure 5Figure 5 shows a sequence diagram of a transaction process between a user and an MThing. Suppose
a user
...