ISO/IEC 23000-13:2014/Amd 1:2015

Information technology - Multimedia application format (MPEG-A) — Part 13: Augmented reality application format — Amendment 1: ARAF reference software and conformance

Technologies de l'information - Format des applications multimedias — Partie 13: Format pour les Applications de Realité Augmentée — Amendement 1: .

General Information

• Status: Withdrawn
• Publication Date: 27-Sep-2015
• Withdrawal Date: 27-Sep-2015
• ICS: 35.040 - Information coding
• 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: 9599 - Withdrawal of International Standard
• Completion Date: 28-Nov-2017

Relations

• Revised: ISO/IEC 23000-13:2017 - Information technology - Multimedia application format (MPEG-A) — Part 13: Augmented reality application format
• Effective Date: 05-Nov-2015
• Amends: ISO/IEC 23000-13:2014 - Information technology - Multimedia application format (MPEG-A) — Part 13: Augmented reality application format
• Effective Date: 25-Dec-2021
• Consolidated By: ISO 20769-2:2018 - Non-destructive testing — Radiographic inspection of corrosion and deposits in pipes by X- and gamma rays — Part 2: Double wall radiographic inspection
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 23000-13
First edition
2014-05-15
AMENDMENT 1
2015-10-01
Information technology - Multimedia
application format (MPEG-A) —
Part 13:
Augmented reality application format
AMENDMENT 1: ARAF reference
software and conformance
Technologies de l’information - Format des applications
multimedias —
Partie 13: Format pour les Applications de Realité Augmentée
AMENDEMENT 1: .
Reference number
ISO/IEC 23000-13:2014/Amd.1:2015(E)
©
ISO/IEC 2015

---------------------- Page: 1 ----------------------
ISO/IEC 23000-13:2014/Amd.1:2015(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, 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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO/IEC 2015 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 23000-13:2014/Amd.1:2015(E)
Contents Page
Foreword . iv
Introduction . iv
1 Scope . 1
2 Reference software . 1
2.1 Implementation details . 1
2.2 Implementation procedure for adding PROTOs in a library . 2
2.3 Utility Software . 3
3 Conformance . 4
Annex A (Informative) Interactive applications description . 6
A.1 ARQuiz . 6
A.1.1 Overview . 6
A.1.2 Playing the game . 6
A.2 AudioBook . 6
A.2.1 Overview . 6
A.2.2 Test the application . 7
A.3 CameraCalibration . 7
A.3.1 Overview . 7
A.3.2 Test the application . 7

© ISO/IEC 2015 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 23000-13:2014/Amd.1:2015(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. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
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).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO's adherence to the WTO principles in the Technical Barriers to Trade (TBT),
see the following URL: Foreword — Supplementary information.
Amendment 1 to ISO/IEC 23000-13:2014 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia
information.
 Part 1: Purpose for multimedia application formats
 Part 2: MPEG music player application format
 Part 3: MPEG photo player application format
 Part 4: Musical slide show application format
 Part 5: Media streaming application format
 Part 6: Professional archival application format
 Part 7: Open access application format
 Part 8: Portable video application format
 Part 9: Digital Multimedia Broadcasting application format
 Part 10: Surveillance application format
 Part 11: Stereoscopic video application format
iv © ISO/IEC 2015 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 23000-13:2014/Amd.1:2015(E)
 Part 12: Interactive music application format
 Part 13: Augmented reality application format
 Part 14: VOID
 Part 15: Multimedia Preservation Application Format
 Part 16: Publish/Subscribe Application Format
 Part 17: Multisensorial Media Application Format
 Part 18: Media Linking Application FormatPart
© ISO/IEC 2015 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 23000-13:2014/Amd.1:2015(E)
Introduction
Augmented Reality (AR) applications refer to a view of a real-world environment (RWE) whose elements are
augmented by content, such as graphics or sound, in a computer driven process. Augmented Reality
Application Format (ARAF) is a collection of a subset of the ISO/IEC 14496-11 (MPEG-4 part 11) Scene
Description and Application Engine standard, combined with other relevant MPEG standards (e.g. ISO/IEC
23005 - MPEG-V), designed to enable the consumption of 2D/3D multimedia content. Consequently, ISO/IEC
23000-13 focuses not on client or server procedures but on the data formats used to provide an augmented
reality presentation.
vi © ISO/IEC 2015 – All rights reserved

---------------------- Page: 6 ----------------------
FINAL DRAFT AMENDMENT ISO/IEC 23000-13:2014/Amd.1:2015(E)

Information technology — Multimedia application format
(MPEG-A) — Part 13: Augmented reality application format,
AMENDMENT 1: ARAF reference software and conformance
1 Scope
This part of ISO/IEC 23000 specifies the Reference Software and Conformance.
2 Reference software
The components of the ARAF reference software are implemented in one of the following manners:
 By using existing MPEG-4 scene elements;
 By creating a library that is loaded by a utility software.
The implementation is provided in the electronic attachment of this document.
2.1 Implementation details
Table 1 presents the PROTOs that are implemented using existing MPEG-4 elements as well as the name of
the file in which the implementation is included. The implementation is provided using the BT syntax (ISO/IEC
14496-11).
Table 1. ARAF Components implemented using existing MPEG-4 scene elements.
PROTO name Filename
Map Map.bt
MapMarker MapMarker.bt
MapOverlay MapOverlay.bt

Table 2 presents the PROTOs that are implemented by creating a library loaded by a utility software. This is a
C/C++ dynamic library acting as a GPAC module. It implements the PROTO by extending GPAC by using its
built-in external proto interface.
Table 2. ARAF Components implemented using a library
PROTO name Filename
ReferenceSignal reference_signal.zip
CameraCalibration reference_signal_reg.zip
ReferenceSignalDetection reference_signal_reg.zip
It should be noted that the CameraCalibration and ReferenceSignalDetection PROTOs share the same library.
The way how the implementation of the plugins was performed is described in the following sections.
© ISO/IEC 2015 – All rights reserved 1

---------------------- Page: 7 ----------------------
ISO/IEC 23000-13:2014/Amd.1:2015(E)
2.2 Implementation procedure for adding PROTOs in a library
First a new dynamic library project was added to the main GPAC solution. GPAC loads the modules using
predefined functions that need to be implemented in each module. Those functions are the following:
const u32 *QueryInterfaces();
GF_BaseInterface *LoadInterface(u32 InterfaceType);
void ShutdownInterface(GF_BaseInterface *ifce);

The function QueryInterface returns the types of extensions that are supported by the module, in the case of
a hardcoded proto it returns GF_HARDCODED_PROTO_INTERFACE.
The function LoadInterface and ShutdownInterface create and destroy an interface object. The interface
object for the hardcoded proto contains two functions:
Bool can_load_proto(const char* url);
Bool init(GF_HardcodedProto* itfs, GF_Compositor *compositor, GF_Node *node);

The function can_load_proto receives a URL as an argument which contains the URL to the PROTO
requested by the scene. If the module supports this PROTO, it returns positively.
The function init creates a new instance of the PROTO and returns positively on success.
The next step is to define the PROTO object by declaring a new structure. An example of the structure is
presented below.
struct ReferenceSignalNode
{
BASE_NODE
MFString *source;   /*exposedField*/
MFString *referenceResources; /*exposedField*/
SFBool *enabled;   /*exposedField*/
MFString *detectionHints;  /*exposedField*/
SFVec3f *translation;  /*exposedField*/
SFRotation *rotation;   /*exposedField*/
MFInt32 *onInputDetected;  /*eventOut*/
MFInt32 *onTranslationChanged; /*eventOut*/
MFInt32 *onRotationChanged; /*eventOut*/
SFInt32 *onError;   /*eventOut*/
};

However since this structure is not known to GPAC internally, it cannot fill in the values, instead it uses a
generic representation for the values in the proto. Therefore it is necessary to copy the values from the
generic representation in the structure one by one. This is done using the code presented below.
1. if (gf_node_get_field(node, 0, &field) != GF_OK) return GF_FALSE;
2. if (field.fieldType != GF_SG_VRML_MFSTRING) return GF_FALSE;
3. rc->source = (MFString *) field.far_ptr;

Line 1 uses the function gf_node_get_field to get the pointer to the value of the field. Line 2 makes sure that
the type of the field value returned corresponds to the expected one. Finally line 3 initializes the value.
The values of the n
...