Information technology -- Internet of media things

Technologies de l'information -- Internet des objets media

General Information

Status
Published
Current Stage
4020 - DIS ballot initiated: 5 months
Start Date
07-Jan-2021
Completion Date
07-Jan-2021
Ref Project

Buy Standard

Draft
ISO/IEC DIS 23093-2 - Information technology -- Internet of media things
English language
17 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

DRAFT INTERNATIONAL STANDARD
ISO/IEC DIS 23093-2
ISO/IEC JTC 1/SC 29 Secretariat: JISC
Voting begins on: Voting terminates on:
2021-01-07 2021-04-01
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
ICS: 35.040.40
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
This document is circulated as received from the committee secretariat.
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/IEC DIS 23093-2:2021(E)
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 SUPPORTING DOCUMENTATION. ISO/IEC 2021
---------------------- Page: 1 ----------------------
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION
ORGANISATION INTERNATIONALE DE NORMALISATION
ISO/IEC DIS 23093-2:2021(E)
ISO/IEC JTC 1/SC 29/WG 7 MPEG 3D GRAPHICS CODING
ISO/IEC JTC 1/SC 29/WG 7 N00028
October 2020, Virtual
Title Text of ISO/IEC DIS 23093-2 IoMT Discovery and Communication API (2nd
edition)
Source WG 7, MPEG 3D Graphics Coding, Sang-Kyun Kim
Status Approved
Serial Number 19637
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2021

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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2021 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC DIS 23093-2:2021(E)
Contents Page

ISO/IEC JTC 1/SC 29/WG 7 N19637-28 ............................................ 2

Foreword ............................................................................................................................................................. iii

Introduction ....................................................................................................................................................... iv

1 Scope ........................................................................................................................................................ 1

2 Normative references ........................................................................................................................ 1

3 Terms and definitions ........................................................................................................................ 1

4 APIs ........................................................................................................................................................... 1

© ISO/IEC 2021 – All rights reserved ii
---------------------- Page: 3 ----------------------
ISO/IEC DIS 23093-2:2021(E)
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).

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 http://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.

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 compared to the previous edition are as follows:

Modification of 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 website.

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.
© ISO/IEC 2021 – All rights reserved iii
---------------------- Page: 4 ----------------------
ISO/IEC DIS 23093-2:2021(E)
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 provide means for supporting

transaction tokens in order 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 data formats of input and output for media sensors, media actuators, media storages, media

analysers, etc. Sensed data from media sensors can be processed by media analysers 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 communicate between

media things along with the APIs to facilitate transactions between media things.

The International Organization for Standardization (ISO) and the International Electrotechnical

Commission (IEC) draw attention to the fact that it is claimed that compliance with this document may

involve the use of patents.

ISO and the IEC take no position concerning the evidence, validity, and scope of these patent rights.

The holders of these patent rights have assured the 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 statements of the holders of these patents right are registered with ISO and IEC.

Information may be obtained from:
Company Address

Myongji University Industry and Academia 116 Myongji-ro, Cheoin-gu, Yongin, Gyeonggi-do 17058,

Cooperation Foundation Republic of Korea
Insignal Co., Ltd #1104, Byucksan Digital Valley 7st, 50 Digital-ro 33gil,
Guro-gu, Seoul, 08377, Republic of Korea

University-Industry Cooperation of Korea 76 Hanggongdaehak-ro, Deogyang-gu, Goyang-si,

Aerospace University Gyeonggi-do, 10540, Republic of Korea
9FL, Electronics Building, Worldcup bukro 54-gil Sangam,
Korea Electronics Technology Institute
Mapo, Seoul, Republic of Korea
Electronics and Telecommunications 218 Gajeong-ro, Yuseong-gu, Daejeon, Korea
Research Institute

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights other than those identified in this list. ISO and IEC shall not be held responsible for

identifying any or all such patent rights.
© ISO/IEC 2021 – All rights reserved iv
---------------------- Page: 5 ----------------------
ISO/IEC DIS 23093-2:2021(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 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:― , 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 terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/
4 APIs
4.1 General

This clause specifies APIs to discover MThings, and connect/disconnect communication between

MThings. In addition, APIs and return class types are specified to provide MThing information and

hardware descriptions.
Under preparation. Stage at time of publication: ISO/IEC DIS 23093-1:2019.
Under preparation. Stage at time of publication: ISO/IEC FDIS 23093-3:2019.
© ISO/IEC 2021 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC DIS 23093-2:2021(E)

An MThing can be discovered by its capabilities and/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 broadcasts

a message using discoverMThingByCapability()to look for MSensors that are capable of

capturing an 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. 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). 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
Under preparation. Stage at time of publication: ISO/IEC FDIS 23093-3:2019.
© ISO/IEC 2021 – All rights reserved 2
---------------------- Page: 7 ----------------------
ISO/IEC DIS 23093-2:2021(E)
Figure 2 — Connecting MThings based on a capability

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 are

going to be unavailable. The MCamera can alert 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().
© ISO/IEC 2021 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC DIS 23093-2:2021(E)
Figure 4 — Alerting disconnection to an MThing
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()through their

user interface of Apps, DApps, or Web (Figure 5, item 1) with desired media token defined by

tokenType (e.g. cryptocurrency or legal tender) and tokenName (e.g. Bitcoin or US dollar). The

© ISO/IEC 2021 – All rights reserved 4
---------------------- Page: 9 ----------------------
ISO/IEC DIS 23093-2:2021(E)

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 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 amount of 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

checkTransactionCompletion(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
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.