1、Information technology Coding of audio-visual objects Part 4: Conformance testing AMENDMENT 16: MPEG-J GFX conformanceAmendment 16:2009 (IDT) toNational Standard of CanadaCAN/CSA-ISO/IEC 14496-4-06(ISO/IEC 14496-4:2004, IDT)NOT FOR RESALE.PUBLICATION NON DESTINE LA REVENTE.CSA Standards Update Servi
2、ceAmendment 16:2009 toCAN/CSA-ISO/IEC 14496-4-06October 2009Title: Information technology Coding of audio-visual objects Part 4: Conformance testing AMENDMENT 16: MPEG-J GFX conformancePagination: 9 pages (iii preliminary and 6 text)To register for e-mail notification about any updates to this publi
3、cationgo to www.ShopCSA.caclick on E-mail Services under MY ACCOUNTclick on CSA Standards Update ServiceThe List ID that you will need to register for updates to this publication is 2418413.If you require assistance, please e-mail techsupportcsa.ca or call 416-747-2233.Visit CSAs policy on privacy a
4、t www.csagroup.org/legal to find out how we protect your personal information.Reference numberISO/IEC 14496-4:2004/Amd.16:2008(E)ISO/IEC 2008INTERNATIONAL STANDARD ISO/IEC14496-4Second edition2004-12-15AMENDMENT 162008-02-15Information technology Coding of audio-visual objects Part 4: Conformance te
5、sting AMENDMENT 16: MPEG-J GFX conformance Technologies de linformation Codage des objets audiovisuels Partie 4: Essai de conformit AMENDEMENT 16: Conformit au GFX MPEG-J ISO/IEC 14496-4:2004/Amd.16:2008(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licens
6、ing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO
7、Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been
8、 taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2008 All rights reserved. Unless otherwise specified, no part
9、of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56
10、CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org ii ISO/IEC 2008 All rights reservedAmendment 16:2009 toCAN/CSA-ISO/IEC 14496-4-06ISO 14496-4:2004/Amd.16:2008(E) ISO 2008 All rights reserved iiiForeword ISO (the International Organization for Sta
11、ndardization) 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 organiz
12、ation 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
13、, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards ado
14、pted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject o
15、f patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Amendment 16 to ISO/IEC 14495-4:2004 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia info
16、rmation. This amendment adds conformance of MPEG-J GFX as defined in ISO/IEC 14496-21:2006. Amendment 16:2009 toCAN/CSA-ISO/IEC 14496-4-06ISO/IEC 14496-4:2004/Amd.16:2008(E) ISO 2008 All rights reserved 1Information technology Coding of audio-visual objects Part 4: Conformance testing AMENDMENT 16:
17、MPEG-J GFX conformance Add the following to Clause 2 Normative References: ISO/IEC 14496-11:2005, Information technology Coding of audio-visual objects Part 11: Scene description and application engine ISO/IEC 14496-21:2006, Information technology Coding of audio-visual objects Part 21: MPEG-J Graph
18、ics Framework eXtensions (GFX) Replace subclause 4.6 on MPEG-J with the following: 4.6 MPEG-J 4.6.1 MPEG-J Conformance Points DEMUXMPEG-JApplicationMPEG-JDecodingBufferScene GraphManagerResourceManagerI/ODevicesNetworkManagerClassLoaderDMIFSceneGraphBIFSDecoderDecodingBuffers 1nMediaDecoders 1nCompo
19、sitionBuffers 1nCompositorand RendererVersion 1playerNW API SG API RM APILegendInterfaceControldataBackChannelChannelMD APIMPEG-JConformance PointFigure AMD16.1 MPEG-J Architecture with Conformance Point Amendment 16:2009 toCAN/CSA-ISO/IEC 14496-4-06ISO 14496-4:2004/Amd.16:2008(E) 2 ISO 2008 All rig
20、hts reservedThe architecture of MPEG-J is explained in ISO/IEC 14496-11 subclauses 10.1 and 10.2. MPEG-J data is defined and the delivery mechanism explained in ISO/IEC 14496-11 subclause 10.3. MPEG-J data is delivered as an elementary stream similar to video, audio and other elementary streams. Thi
21、s is de-multiplexed and stored in MPEG-J Decoding Buffers. These buffers feed the MPEG-J Decoder, which “decodes” it. In the case of classes (Java byte code), decoding means loading, while for the object and other data it means making the data available to the terminal. The MPEG-J Decoding Buffer co
22、nsists of MPEG-J Access Units. Each MPEG-J Access Unit contains either one class or one serialized object or one archive (a zip file) with a header. When this is decoded, the class file or the object data or the zip file is extracted and fed into the MPEG-J Class Loader as shown in Figure AMD16.1. B
23、itstream conformance point for MPEG-J is: MPEG-J Decoding At a bitstream conformance point, bitstreams will be acquired for use in testing. Terminal conformance point for MPEG-J is: MPEG-J Decoding Buffer MPEG-J API conformance Java Platform conformance An MPEG-J conformance point can be either an M
24、PEG-J bitstream conformance point or an MPEG-J Terminal conformance point. The MPEG-J bitstream conformance points deal with the syntactic aspects while the MPEG-J terminal conformance points address the semantics. 4.6.2 Bitstream Conformance Each bitstream shall meet the syntactic and semantic requ
25、irements specified in ISO/IEC 14496-1. This subclause describes a set of tests to be performed on bitstreams. In the description of the tests it is assumed that the tested bitstream contains no errors due to transmission or other causes. For each test the condition or conditions that must be satisfi
26、ed are given, as well as the prerequisites or conditions in which the test can be applied. Note that the application of these tests requires parsing of the bitstream to the appropriate levels. Parsing and interpretation of ODs is also required. In some cases of IPMP-protected data, de-scrambling may
27、 be required before the tests can be performed on non IPMP-related features. 4.6.2.1 MPEG-J Conformance 4.6.2.1.1 Conformance Requirements MPEG-J bitstreams shall comply with the specifications in subclause 10.3 of ISO/IEC 14496-11. The terminal shall strictly adhere to the syntax specified in subcl
28、ause 10.3.3. When the bitstream carries classes, these classes shall only use the classes, interfaces, or API (Application Programming Interface) calls from the following: 1. MPEG-J APIs defined in subclause 10.4 of ISO/IEC 14496-11 and in ISO/IEC 14496-21 (org.iso.*) for the relevant profile. Profi
29、les are defined in the subclause 7.9 of ISO/IEC 14496 11. 2. Java APIs supported by the underlying Java Platform for the relevant profile. These are (typically) in the java.* packages. 3. Classes or Interfaces carried in the bitstream. These classes shall obey the security rules defined in subclause
30、 10.2.5 of ISO/IEC 14496-11. Amendment 16:2009 toCAN/CSA-ISO/IEC 14496-4-06ISO 14496-4:2004/Amd.16:2008(E) ISO 2008 All rights reserved 34.6.2.1.2 Measurement procedure Syntax of the bitstream shall meet the requirements of subclause 10.3.3 of ISO/IEC 14496-11. The classes should compile with only t
31、he Java Platform APIs and the MPEG-J APIs relevant to that profile. MPEGlets and other Java classes that form the MPEG-J bitstreams shall be run through the reference MPEG-J implementation. This is a necessary but not a sufficient condition. Verification mechanism: The API implementations shall outp
32、ut a trace file for every bitstream. This trace file shall be compared to see if the behavior is the same in two implementations. This idea is similar to the dump format used for BIFS. Method packagename.classname.methodName with parameter parameter1parameter2 parameter3parametern was called where:
33、method_name is the name of the method and parameternis: value of the parameter - when it is a primitive data type the instance name - otherwise. E.g. a method foo(var1, var2) would print the trace Method org.iso.mpeg.mpegj.foo with parameter var1var2Exception packagename.exception_name was thrown (o
34、r) Exception packagename.exception_name was thrown or with parameter var14.6.2.1.3 Tolerance There is no tolerance for bitstream syntax checking. The diagnosis is pass or fail. 4.6.3 Terminal Conformance This subclause describes procedures to verify conformance of terminals. Each compliant decoder s
35、hall be able to decode all compliant ISO/IEC 14496-1 streams within the subset of the standard defined by the specified capabilities of the decoder. All tests are performed using error free bitstreams. To test for correct interpretation of syntax and semantics, test sequences covering a wide range o
36、f parameters shall be supplied to the decoder under test and its output sequence shall be compared with the known expected output as described for the specific test sequence or bitstream. The comparison can be done, for example, by performing subjective evaluation, by verification of the expected re
37、sult, or by comparing the timing performance. Such tests are necessary but not sufficient to prove conformance. They are helpful for discovering non-compliant implementations. Tests are expected to be used for testing ISO/IEC 14496 decoders, including video and audio decoding, as it is generally not
38、 practical to test system decoders (or ISO/IEC 14496-1 decoders) alone. Practical test results depend on successful (or expected) output of the entire ISO/IEC 14496 decoder (systems, video, audio and DMIF). 4.6.3.1 MPEG-J Conformance 4.6.3.1.1 Conformance Requirements Figure AMD16.1 shows the archit
39、ecture an MPEG-J Terminal and the conformance points. The terminal shall follow all the rules regarding: MPEG-J Session and Lifecycle specified in subclause 10.2 of ISO/IEC 14496-11. MPEG-J Decoding and Loading specified in subclause 10.3 of ISO/IEC 14496-11. Amendment 16:2009 toCAN/CSA-ISO/IEC 1449
40、6-4-06ISO 14496-4:2004/Amd.16:2008(E) 4 ISO 2008 All rights reserved Semantics of the timestamps specified in subclause 10.3.2 of ISO/IEC 14496-11. All the defined and normatively referred APIs defined in subclause 10.4 of ISO/IEC 14496-11 and in ISO/IEC 14496-21 shall be strictly followed. 4.6.3.1.
41、1.1 MPEG-J Decoding The Decoding process of MPEG-J data involves two steps: a. Recovering the access unit data (class, object, or zip file) from the bit stream. This is input to the MPEG-J Class Loader. b. Loading and Executing: If the data is a class file it is loaded according to the rules specifi
42、ed in subclause 10.3 of ISO/IEC 14496-11. If the data is a zip file the classes specified in the header are loaded according to the rules specified in subclause 10.3 of ISO/IEC 14496-11. If the data is neither a class nor a zip file, it is made available according to the rules specified in subclause
43、 10.3 of ISO/IEC 14496-11. 4.6.3.1.1.2 MPEG-J API conformance The terminal shall implement all the APIs that are defined or normatively referenced by ISO/IEC 14496-11 and ISO/IEC 14496-21 for the relevant profile. 4.6.3.1.1.3 Java Platform conformance The Terminal shall implement the Java Platform a
44、ccording to the profile. This is further elaborated in Annex A and in the Java Technology Test Suite Development Guide. 4.6.3.1.2 Measurement procedure The recovered MPEG-J data (classes, objects, or zip files) shall be compared bit-wise with the original data. This is tested with appropriately auth
45、ored MPEG-J bitstreams composed of MPEGlets and other Java classes. The terminal shall strictly adhere to the class/interface definitions in subclause 10.4 of ISO/IEC 14496-11 and in ISO/IEC 14496-21. E.g., the class/interface names, method signatures, variable (if any) names and types, constant nam
46、es and values shall be implemented as defined. This is tested with appropriately authored MPEG-J classes. Various appropriately authored MPEGlets are provided to test the various parts of the terminal implementation. There are also other Java test programs that are provided that simply exercise the
47、different APIs that are required to be implemented and checks the appropriate behaviour. These test the API method signatures and some preliminary behavioural testing. Passing these tests is also a necessary but not a sufficient condition. The measurement procedure for Java Platform conformance is d
48、escribed in detail in Annex E and in the Java Technology Test Suite Development Guide. Amendment 16:2009 toCAN/CSA-ISO/IEC 14496-4-06ISO 14496-4:2004/Amd.16:2008(E) ISO 2008 All rights reserved 54.6.3.1.2.1 GFX Feature List The test suite shall verify the different MPEG-J features listed below. Tabl
49、e AMD16.1 GFX Test Suite Information N Feature Reference of Test sequence and associated method 1 Resource manager (J2SE) GfxJp01.java, GfxJp01.mp4, GfxJp01.jar 2 Pluggable rendering engine (J2SE) GfxJp02.java, GfxJp02.mp4, GfxJp02.jar 3 Media API (J2SE) GfxJp03.java, GfxJp03.mp4, GfxJp03.jar 7 Resource Manager & Media API (J2ME) GfxJp07.java, GfxJp07.mp4, GfxJp07.jad,jar 8 Terminal Capability API (J2ME) GfxJp08.java, GfxJp08.mp4, GfxJp08.jad,jar 4.6.3.1.3 Bitstreams Each bitstre
