1、Amendment 1:2002 toNational Standard of CanadaCAN/CSA-ISO/IEC 13818-6:02Amendment 1:2000 to International Standard ISO/IEC 13818-6:1998 has been adopted without modificationas Amendment 1:2002 to CAN/CSA-ISO/IEC 13818-6:02. This Amendment was reviewed by the CSA TechnicalCommittee on Information Tec
2、hnology (TCIT) under the jurisdiction of the Strategic Steering Committee onInformation Technology and deemed acceptable for use in Canada.March 2002Information technology Generic codingof moving pictures and associated audioinformation Part 6:Extensions for DSM-CCAMENDMENT 1Additions to support dat
3、a broadcastingTechnologies de linformation Codage gnrique des images animes etdes informations sonores associes Partie 6: Extensions pour DSM-CCAMENDEMENT 1Additions la diffusion de soutien de donnesReference numberISO/IEC 13818-6:1998/Amd.1:2000(E) ISO/IEC 2000ICS 35.040 Ref. No. ISO/IEC 13818-6:19
4、98/Amd.1:2000/Cor.1:2002(E) ISO/IEC 2002 All rights reserved Information technology Generic coding of moving pictures and associated audio information Part 6: Extensions for DSM-CC AMENDMENT 1 TECHNICAL CORRIGENDUM 1 Technologies de linformation Codage gnrique des images animes et des informations s
5、onores associes Partie 6: Extensions pour DSM-CC AMENDEMENT 1 RECTIFICATIF TECHNIQUE 1 Technical Corrigendum 1 to International Standard ISO/IEC 13818-6:1998/Amd.1:2000 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audio, picture, mult
6、imedia and hypermedia information. In item 8), replace semantics definition of the LLCSNAP() structure by the following definition: LLCSNAP() - This structure shall contain the datagram according to the ISO/IEC 8802-2 Logical Link Control (LLC) and ISO/IEC 8802-1a SubNetwork Attachment Point (SNAP)
7、specifications. In LLC Type 1 operation, unacknowledged connectionless mode, the LLC header is three bytes long and consists of a one byte Destination Service Access Point (DSAP) field, a one byte Source Service Access Point (SSAP) field, a one byte Control field. The values 0xAA in the LLC headers
8、DSAP and SSAP fields indicate that an IEEE 802.2 SNAP header follows. The Control value of 0x03 specifies an Unnumbered Information Command PDU. The SNAP header is five bytes long and consists of a three byte Organizationally Unique Identifier (OUI) field and a two byte Protocol Identifier. The SNAP
9、 OUI value 0x00-00-00 specifies the Protocol Identifier as an EtherType or routed non-OSI protocol. The SNAP OUI of 0x00-80-C2 indicates a Bridged Protocol. When the OUI is set Technical Corrigendum 1:2003 toNational Standard of CanadaCAN/CSA-ISO/IEC 13818-6:02 and Amendment 1:2002Technical Corrigen
10、dum 1:2002 to International Standard ISO/IEC 13818-6:1998 and Amendment 1:2000 hasbeen adopted without modification as Technical Corrigendum 1:2003 to CAN/CSA-ISO/IEC 13818-6:02 andAmendment 1:2002. This Technical Corrigendum was reviewed by the CSA Technical Committee on InformationTechnology (TCIT
11、) under the jurisdiction of the Strategic Steering Committee on Information Technology anddeemed acceptable for use in Canada. July 2003ISO/IEC 13818-6:1998/Amd.1:2000/Cor.1:2002(E) 2 ISO/IEC 2002 All rights reservedto 0x00-00-00 then the SNAP Protocol Identifier for IP is 0x08-00. For Internet Prot
12、ocol datagrams, the complete LLC/SNAP header is 0xAA-AA-03-00-00-00-08-00. In item 9), replace Table 9-4 by the following table: Table 9-4 DSM-CC Addressable Section Syntax No. ofbits Mnemonic DSMCC_addressable_section() table_id 8 uimsbf 0 1 error_detection_type 1 bslbf reserved 2 bslbfaddressable_
13、section_length 12 uimsbf deviceId70 8 uimsbf deviceId158 uimsreserved 2 bslbfpayload_scrambling_control 2 bslbf address_scrambling_contro bslbfLLCSNAP_flag 1 bslbf 1 1 section_number 8 uimsbflast_section_number 8 uimsbf deviceId2316 8 uimsbfdeviceId3124 uimsbfdeviceId3932 uimsbfdeviceId4740 uimsbfif
14、 ( LLCSNAP_flag = 1 ) LLCSNAP() else for (j=0;jN1;j+) datagram_data_byte 8 bslbf if (section_number = last_section_number) for (j=0;jN2;j+) stuffing_byte 8 bslbf if (error_detection_type = 1 ) checksum 32 uimsbf else CRC_32 32 rpchof ISO/IEC 13818-6:1998/Amd.1:2000/Cor.1:2002(E) ISO/IEC 2002 All rig
15、hts reserved 3In item 9), between the definition of the error_detection_type field and the definition of the deviceId field, add the following semantic definition of the addressable_section_length field: addressable_section_length - This 12 bit field specifies the number of remaining bytes in the DS
16、MCC_addressable_section immediately following this field up to the end of the DSMCC_addressable_section. The value in this field shall not exceed 4093 (indicating a section maximum data length of 4084 bytes, following the last_section_number field and up to the CRC_32/checksum field). In item 9), re
17、place semantic definition of the datagram_data_byte field by the following definition: datagram_data_byte - This 8 bit field shall contain a byte of the datagram. In item 9), replace semantic definition of the CRC_32 field by the following definition: CRC_32 - This 32-bit field shall be set as defin
18、ed in ISO/IEC 13818-1:2000 Annex A. This field is only present when error_detection_type is set to 0. In item 9), replace semantic definition of the checksum field by the following definition: checksum - A 32 bit checksum calculated over the entire DSMCC_addressable_section. The checksum shall be ca
19、lculated by treating the DSMCC_addressable_section as a sequence of 32-bit integers and performing ones complement addition over all the integers, most significant byte first, then taking the ones complement of the result. For the purpose of computing the checksum, the value of the checksum field sh
20、all be considered 0. If the message length is not a multiple of four bytes, the message shall be considered to be appended with zeroed bytes for the purpose of checksum calculation only. If the computed result is 0, then the result shall be set to 0xFFFFFFFF (the alternative value for a ones complem
21、ent representation of 0). In cases where a checksum is not desired, the value of this field shall be set to 0 to indicate the checksum has not been calculated. This feature is useful for networks where error detection is provided at a protocol layer lower than the MPEG-2 Transport Stream. This field
22、 is only present when error_detection_type is set to 1. In item 10), replace Table 9-7 by the following table: Table 9-7 DSM-CC Stream Types stream_type Description 0x00-0x09 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 defined 0x0A Multi-protocol Encapsulation 0x0B DSM-CC U-N Messages 0x0C DSM-CC Stream De
23、scriptors 0x0D DSM-CC Sections (any type, including private data) or DSM-CC Addressable Sections 0x0E - 0x7F ITU-T Rec. H.222.0 | ISO/IEC 13818-1:2000 reserved 0x80 - 0xFF User private Reference numberISO/IEC 13818-6:1998/Amd.1:2000(E)ISO/IEC 2000INTERNATIONALSTANDARDISO/IEC13818-6First edition1998-
24、09-01AMENDMENT 12000-10-15Information technology Generic codingof moving pictures and associated audioinformation Part 6:Extensions for DSM-CCAMENDMENT 1Additions to support data broadcastingTechnologies de linformation Codage gnrique des images animes etdes informations sonores associes Partie 6: E
25、xtensions pour DSM-CCAMENDEMENT 1Additions la diffusion de soutien de donnesISO/IEC 13818-6:1998/Amd.1:2000(E)PDF disclaimerThis PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall notbe edited unless the typefaces which a
26、re embedded are licensed to and installed on the computer performing the editing. In downloadingthis file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability inthis area.Adobe is a trademark of Adobe Systems Incorpora
27、ted.Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creationparameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In theunlikely event that a pro
28、blem relating to it is found, please inform the Central Secretariat at the address given below. ISO/IEC 2000All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronicor mechanical, including photocopying and micr
29、ofilm, without permission in writing from either ISO at the address below or ISOs member bodyin the country of the requester.ISO copyright officeCase postale 56 Gb7 CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail copyrightiso.chWeb www.iso.chii ISO/IEC 2000 All rights reservedISO/
30、IEC 13818-6:1998/Amd.1:2000(E) ISO/IEC 2000 All rights reserved iiiForewordISO (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 IECparticip
31、ate in the development of International Standards through technical committees established by therespective organization to deal with particular fields of technical activity. ISO and IEC technical committeescollaborate in fields of mutual interest. Other international organizations, governmental and
32、 non-governmental, inliaison with ISO and IEC, also take part in the work.International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.Draft Int
33、ernational Standards adopted 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 Amendme
34、nt may be the subject of patentrights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.Amendment 1 to International Standard ISO/IEC 13818-6:1998 was prepared by Joint Technical CommitteeISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audi
35、o, picture, multimedia and hypermediainformation.ISO/IEC 13818-6:1998/Amd.1:2000(E) ISO/IEC 2000 All rights reserved 1Information technology Generic coding of moving pictures andassociated audio information Part 6: Extensions for DSM-CCAMENDMENT 1: Additions to support data broadcasting1) Replace th
36、e semantic definition of DownloadInfoIndication moduleSize in subclause 7.3.2 with the following:“The moduleSize field is the length, in bytes, of the described module. A value of zero indicates that the modulesize is not specified.“2) Replace the last paragraph in subclause 9.2.1 with the following
37、:“MPEG-2 Systems, ISO/IEC 13818-1:2000, defines generic table section syntax that DSM-CC uses to provide re-assembly of Transport Stream packets into DSM-CC messages. This specification defines additional semantics onISO/IEC 13818-1:2000 sections to support additional DSM-CC requirements. Called DSM
38、CC_section andDSMCC_Addressable_section, the syntax is compatible with the generic section syntax so that compliant MPEG-2Systems decoders may be used.“3) In subclause 9.2.2, replace every occurrence of “private_section“ with “generic_section“4) In subclause 9.2.2, replace every occurrence of “priva
39、te_indicator“ with “complement_indicator“.5) Replace Table 9-3 with the following:“Table 9-3 DSM-CC table_id assignmentstable_id DSMCC Section Type0x00 - 0x37 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 defined0x38 - 0x39 ISO/IEC 13818-6 reserved0x3A DSM-CC Sections containing multi-protocol encapsulated d
40、ata0x3B DSM-CC Sections containing U-N Messages, except Download Data Messages0x3C DSM-CC Sections containing Download Data Messages0x3D DSM-CC Sections containing Stream Descriptors0x3E DSM-CC Sections containing private data0x3F DSM-CC Addressable Sections0x40 - 0xFE User private0xFF forbidden“6)
41、In subclause 9.2.2.1 replace the corresponding paragraphs with the following:“version_number - This field is a 5-bit field. If the value of the table_id field equals 0x3A or 0x3B, this field shall beset to zero. If the value of the table_id field equals 0x3C and a DownloadDataBlock Message is convey
42、ed, this fieldshall have the value of the least significant 5 bits of the moduleVersion field of the conveyed DownloadDataBlockMessage. If the value of the table_id field equals 0x3C and a DownloadDataRequest Message is conveyed, thisISO/IEC 13818-6:1998/Amd.1:2000(E) ISO/IEC 2000 All rights reserve
43、d2field shall be set to zero. If the value of table_id equals 0x3D, then this field shall be set as defined in ISO/IEC13818-1:2000. If the value of the table_id field equals 0x3E, then the value and use of this field are defined by theuser.current_next_indicator - This is a 1 bit flag. If the value
44、of the table_id field equals 0x3A, 0x3B or 0x3C, this bitshall be set to 1. Otherwise, this field shall be set as defined in ISO/IEC 13818-1:2000.section_number - This field is a 8-bit field. If the value of the table_id field equals 0x3A or 0x3B, this field shall beset to zero. If the value of the
45、table_id field equals 0x3C, this field shall have a value of the least significant 8 bits ofthe blockNumber field of the conveyed DownloadDataBlock or DownloadDataRequest Message. If the value of thetable_id field is not in the range of 0x3A to 0x3C, then this field shall be set as defined in ISO/IE
46、C 13818-1:2000.last_section_number - This field is a 8-bit field. This field specifies the number of the last section (that is, thesection with the highest section number) of the table of which this section is a part. (Note: This means that this fieldshall be set to the maximum value that is encoded
47、 in the section_number field for the same table_id,table_id_extension and version_number field).“7) Delete the footnote under Table 9-2.8) Add the following to subclause 9.2.2.1 after last_section_number:“LLCSNAP() - This structure shall contain the datagram according to the ISO/IEC 8802-2 Logical L
48、ink Control (LLC) andISO/IEC 8802-1a SubNetwork Attachment Point (SNAP) specifications. For more information, see subclause 9.2.5,Encapsulation within MPEG-2 Transport Streams.“9) Add the following subclauses after subclause 9.2.2:“9.2.3 DSM-CC Addressable SectionsThe DSMCC_addressable_section() for
49、mat is used to send a DSM-CC encapsulated datagram to a specific device or group ofdevices. This format embeds the deviceId of the target device into the section header to allow address filtering at the sectionlevel. It also supports scrambling mechanisms.The following table defines the format and semantics of the DSMCC_addressable_section:Table 9-4 Ad
