ETSI TS 102 006 V1.2.1 (2002-10)
`
`Technical Specification
`
`Digital Video Broadcasting (DVB);
`Specification for System Software Update in DVB Systems
`
`European B roadcasting Union
`
`U nion Européenne de R adio-Télévision
`
`EBU·UER
`
`1
`
`LGE 1013
`
`

`

`2
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`Reference
`RTS/JTC-DVB-125-2
`
`Keywords
`broadcasting, data, digital, DVB, video
`
`ETSI
`
`650 Route des Lucioles
`F-06921 Sophia Antipolis Cedex - FRANCE
`
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Siret N° 348 623 562 00017 - NAF 742 C
`Association à but non lucratif enregistrée à la
`Sous-Préfecture de Grasse (06) N° 7803/88
`
`Important notice
`
`Individual copies of the present document can be downloaded from:
`http://www.etsi.org
`
`The present document may be made available in more than one electronic version or in print. In any case of existing or
`perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
`In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
`within ETSI Secretariat.
`
`Users of the present document should be aware that the document may be subject to revision or change of status.
`Information on the current status of this and other ETSI documents is available at
`http://portal.etsi.org/tb/status/status.asp
`
`If you find errors in the present document, send your comment to:
`editor@etsi.org
`
`Copyright Notification
`
`No part may be reproduced except as authorized by written permission.
`The copyright and the foregoing restriction extend to reproduction in all media.
`
`© European Telecommunications Standards Institute 2002.
`© European Broadcasting Union 2002.
`All rights reserved.
`
`DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members.
`TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
`3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
`
`ETSI
`
`2
`
`

`

`3
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`Contents
`
`Intellectual Property Rights ................................................................................................................................5
`
`Foreword.............................................................................................................................................................5
`
`Introduction ........................................................................................................................................................5
`
`1
`
`2
`
`3
`3.1
`3.2
`
`4
`
`5
`5.1
`5.2
`
`Scope ........................................................................................................................................................7
`
`References ................................................................................................................................................7
`
`Definitions and Abbreviations..................................................................................................................7
`Definitions ..........................................................................................................................................................7
`Abbreviations .....................................................................................................................................................8
`
`Void..........................................................................................................................................................8
`
`Profiles and types of system software update services.............................................................................8
`Signalling ...........................................................................................................................................................8
`Data carriage ......................................................................................................................................................9
`
`6
`6.1
`6.1.1
`
`Network (SI) signalling ............................................................................................................................9
`Linkage Descriptor for Systems Software Update ...........................................................................................10
`SSU Scan Linkage Descriptor ....................................................................................................................10
`
`7
`7.1
`
`PSI signalling .........................................................................................................................................11
`Data Broadcast Id Descriptor selector byte definition for System Software Update ........................................12
`
`8
`8.1
`8.1.1
`8.1.2
`8.1.3
`8.2
`8.2.1
`8.3
`
`Standard Data Carousel layout for System Software Update services....................................................13
`Structure of the Standard Update Carousel ......................................................................................................13
`DownloadServerInitiate message (DSI)......................................................................................................14
`DownloadInfoIndication message (DII) .....................................................................................................16
`DownloadDataBlock message (DDB) ........................................................................................................17
`Standard Data Carousel Descriptors.................................................................................................................17
`SSU Module Type Descriptor.....................................................................................................................17
`Time availability guidelines for simple SSU services. .....................................................................................17
`
`9
`9.1
`9.2
`9.3
`9.4
`9.4.1
`9.4.2
`9.4.3
`9.4.4
`9.4.5
`9.5
`9.5.1
`9.5.2
`9.5.2.1
`9.5.2.2
`9.5.2.3
`9.5.2.4
`9.5.2.5
`9.5.2.6
`9.5.2.7
`9.5.2.8
`9.5.2.9
`9.5.2.10
`9.5.2.11
`9.5.2.12
`
`Update Notification Table ......................................................................................................................18
`Description .......................................................................................................................................................18
`PSI, SI and related UNT signalling ..................................................................................................................18
`Description of the Update Notification Table ..................................................................................................19
`Semantics of the UNT ......................................................................................................................................20
`Fields description........................................................................................................................................21
`compatibilityDescriptor ..............................................................................................................................21
`platform_loop_length..................................................................................................................................22
`target_descriptor_loop()..............................................................................................................................22
`operational_descriptor_loop().....................................................................................................................23
`SSU UNT descriptors.......................................................................................................................................24
`Descriptor identification and location.........................................................................................................24
`Descriptor coding........................................................................................................................................24
`target_smartcard_descriptor ..................................................................................................................24
`target_MAC_address_descriptor...........................................................................................................25
`target_IP_address_descriptor ................................................................................................................25
`target_IPv6_address_descriptor ............................................................................................................25
`target_serial_number_descriptor ...........................................................................................................26
`update_descriptor ..................................................................................................................................26
`SSU_location_descriptor.......................................................................................................................27
`SSU_subgroup_association_descriptor .................................................................................................28
`scheduling_descriptor ...........................................................................................................................28
`telephone_descriptor (Informative) .......................................................................................................29
`SSU_event_name_descriptor ................................................................................................................31
`message_descriptor ...............................................................................................................................31
`
`ETSI
`
`3
`
`

`

`4
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`9.5.2.13
`9.6
`9.6.1
`9.6.2
`9.6.2.1
`9.6.2.2
`9.7
`9.8
`
`private_data_specifier_descriptor (Informative) ...................................................................................32
`SSU Data Carousel descriptors ........................................................................................................................32
`Descriptor identification and location.........................................................................................................32
`Descriptor coding........................................................................................................................................33
`subgroup_association_descriptor ..........................................................................................................33
`Compatibility descriptor........................................................................................................................33
`Interworking requirements for operators ..........................................................................................................33
`Interworking requirements for receivers ..........................................................................................................34
`
`Annex A (informative):
`
`Locating the appropriate System Software Update service .......................35
`
`Annex B (informative):
`
`Recommendations for transferring System Software Update service
`data from receiver manufacturer to network operator..............................36
`
`Annex C (normative):
`
`Use of the UNT descriptors ...........................................................................37
`
`C.1
`
`compatibilityDescriptor..........................................................................................................................37
`
`C.2 Target loop .............................................................................................................................................37
`
`C.3 Common loop and operational loop .......................................................................................................37
`
`Annex D (informative):
`
`Bibliography ...................................................................................................38
`
`History ..............................................................................................................................................................39
`
`ETSI
`
`4
`
`

`

`5
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`Intellectual Property Rights
`
`IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
`pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
`in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
`respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
`server (http://webapp.etsi.org/IPR/home.asp).
`
`Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
`can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
`server) which are, or may be, or may become, essential to the present document.
`
`Foreword
`
`This Technical Specification (TS) has been produced by Joint Technical Committee (JTC) Broadcast of the European
`Broadcasting Union (EBU), Comité Européen de Normalisation ELECtrotechnique (CENELEC) and the European
`Telecommunications Standards Institute (ETSI).
`
`NOTE: The EBU/ETSI JTC Broadcast was established in 1990 to co-ordinate the drafting of standards in the
`specific field of broadcasting and related fields. Since 1995 the JTC Broadcast became a tripartite body
`by including in the Memorandum of Understanding also CENELEC, which is responsible for the
`standardization of radio and television receivers. The EBU is a professional association of broadcasting
`organizations whose work includes the co-ordination of its members' activities in the technical, legal,
`programme-making and programme-exchange domains. The EBU has active members in about 60
`countries in the European broadcasting area; its headquarters is in Geneva.
`
`European Broadcasting Union
`CH-1218 GRAND SACONNEX (Geneva)
`Switzerland
`Tel:
`+41 22 717 21 11
`Fax: +41 22 717 24 81
`
`Founded in September 1993, the DVB Project is a market-led consortium of public and private sector organizations in
`the television industry. Its aim is to establish the framework for the introduction of MPEG-2 based digital television
`services. Now comprising over 200 organizations from more than 25 countries around the world, DVB fosters
`market-led systems, which meet the real needs, and economic circumstances, of the consumer electronics and the
`broadcast industry.
`
`The present document incorporates both the simple and the extended profiles of the former DVB Data Download
`Specification, TS 102 006-1, therefore TS 102 006-1 V1.1.1 has been withdrawn and replaced by the present document.
`
`Introduction
`
`The present document defines agreements on which to base interoperability for system software update services and
`receivers. These have been selected to minimize interdependencies between the parties involved. In particular:
`
`-
`
`-
`
`-
`
`It defines the signalling information that can be used to locate the transport stream containing the system
`software update service in a network via the NIT or BAT as appropriate.
`
`It defines the signalling information used to locate the system software update service in a transport stream
`(via the PMT).
`
`It defines the options for transmitting the actual system software update service in either a proprietary data
`transfer format, or a standardized 2-layer DVB data carousel (called standard update carousel from here on).
`
`ETSI
`
`5
`
`

`

`6
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`-
`
`-
`
`It defines a Update Notification Table (UNT) that can be used to enhance the system software update
`functionality in an upward compatible way. The table provides a standard mechanism for carrying additional
`information, e.g. update scheduling information, extensive selection and targeting information, action
`notification, filtering descriptors.
`
`It defines a recommended format for exchanging the system software update data from receiver manufacturer
`to the network (or multiplex) operator for subsequent transmission. In case multiple receiver manufacturers
`share the same standard update carousel this format allows such a multi-vendor carousel to be composed from
`individual manufacturers contributions in a simple way.
`
`The present document has to be seen in context with ETR 162 [3] and EN 300 468 [4] because it describes additional
`descriptors used for system software update.
`
`ETSI
`
`6
`
`

`

`7
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`1
`
`Scope
`
`Receiver software is increasingly complex. In order to guarantee the functionality of a receiver as well as increasing its
`functionality once deployed in the field a software update service is required. The present document specifies a standard
`mechanism for signalling a software update service and the means to carry the data for such a software update service.
`It builds on [1], [3] and [4] for signalling and [2] for data carriage.
`
`The present document does not define the mandatory character of this protocol in a specific context, and it does not
`exclude the use of proprietary mechanisms for doing a software update. This allows a network to support horizontal
`market model receivers (e.g. MHP receivers). Equally it allows receivers requiring a software update service to be
`deployed in a network independent way.
`
`2
`
`References
`
`The following documents contain provisions which, through reference in this text, constitute provisions of the present
`document.
`
`• References are either specific (identified by date of publication and/or edition number or version number) or
`non-specific.
`
`• For a specific reference, subsequent revisions do not apply.
`
`• For a non-specific reference, the latest version applies.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`[8]
`
`ISO/IEC 13818-6: "Information technology; Generic coding of moving pictures and associated
`audio information; Part 6: Extensions for DSM-CC" 1998-09-01.
`
`ETSI EN 301 192 (V1.2.1): "Digital Video Broadcasting (DVB); DVB specification for data
`broadcasting".
`
`ETSI ETR 162: "Digital Video Broadcasting (DVB); Allocation of Service Information (SI) codes
`for DVB systems".
`
`ETSI EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI)
`in DVB systems".
`
`IEEE 802-1990: "IEEE Standards for Local and Metropolitan Area Networks: Overview and
`Architecture" (http://standards.ieee.org/catalog/olis/802-1990.pdf).
`
`ISO/IEC 8859-1: "Information technology; 8-bit single-byte coded graphic character sets;
`Part 1: Latin alphabet No. 1".
`
`ISO 639-2: "Codes for the representation of names of languages; Part 2: Alpha-3 code".
`
`ETSI TS 101 197-1: "Digital Video Broadcasting (DVB); DVB SimulCrypt; Part 1: Head-end
`architecture and synchronization".
`
`3
`
`Definitions and Abbreviations
`
`3.1
`
`Definitions
`
`For the purposes of the present document, the following terms and definitions apply:
`
`(Receiver) manufacturer: organization which assume prime responsibility for updating the software of a receiver once
`deployed in the field
`
`NOTE: Depending on legal arrangements this can also apply to service providers and other entities.
`
`ETSI
`
`7
`
`

`

`8
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`system software update: update of receiver software transmitted over the DVB systems
`
`3.2
`
`Abbreviations
`
`For the purposes of the present document, the following abbreviations apply:
`
`BAT
`DDB
`DII
`DSI
`bslbf
`DSM-CC
`DVB
`EBU
`ISO
`LSB
`MHP
`MPEG
`MSB
`NIT
`OUI
`PAT
`PID
`PMT
`PSI
`SI
`SSU
`TS
`uimsbf
`UNT
`
`Bouquet Association Table
`Download Data Block
`Download Info Indication
`Download Server Initiate
`bit string, left bit first
`Digital Storage Media - Command and Control
`Digital Video Broadcasting
`European Broadcasting Union
`International Organization for Standardization
`Least Significant Bit
`Multimedia Home Platform
`Moving Pictures Expert Group
`Most Significant Bit
`Network Information Table
`Organization Unique Identifier
`Program Association Table
`Packet IDentifier
`Program Map Table
`Program Specific Information
`Service Information
`System Software Update
`Transport Stream
`unsigned integer most significant bit first
`Update Notification Table
`
`4
`
`Void
`
`5
`
`Profiles and types of system software update
`services
`
`5.1
`
`Signalling
`
`The present document defines two profiles for software update services with respect to signalling of the service:
`
`-
`
`-
`
`Simple profile software update services: these are based on the description in clauses 7 and 8 using signalling
`in NIT/BAT and PMT, and do not require the Update Notification Table as per clause 9.
`
`Update Notification Table enhanced profile software update services: these are based on the description in
`clauses 7, 8 and 9. In this case the UNT carries scheduling, targeting or other selection criteria which cannot be
`carried in NIT/BAT or PMT.
`
`Consequently also two profiles of receivers exist:
`
`-
`
`-
`
`Receivers supporting only the simple profile.
`
`Receivers supporting the UNT enhanced profile.
`
`ETSI
`
`8
`
`

`

`9
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`In order for compatibility to be guaranteed service operators and receivers need to comply to the following "backward
`compatibility" rules:
`
`-
`
`-
`
`Service operators shall at least support the simple profile.
`
`Receivers shall at least support the simple profile.
`
`NOTE: Since the simple profile service is a subset of the UNT enhanced profile service this implies no significant
`complexity on either service operator or receiver.
`
`5.2
`
`Data carriage
`
`The present document allows two different formats of system software update data carriage in the broadcast stream:
`
`1)
`
`Proprietary format streams.
`
`2)
`
`Standard update carousel (potentially shared between manufacturers)
`
`In case of 1) it is the responsibility of the receiver manufacturers potentially sharing the update service to identify their
`organization's stream, or the stream can be uniquely identified as being specific to a receiver manufacturer through the
`data_broadcast_id_descriptor.
`
`In case of 2) the standard carousel contains the identification of the receiver manufacturer.
`
`6
`
`Network (SI) signalling
`
`The linkage descriptor with the linkage type of 0x09 (system software update service) conveys the location of the
`transport stream carrying a system software update service within a network or bouquet respectively. This descriptor
`shall be carried in the first loop of the NIT or in the first loop of a specifically identified BAT (called system software
`update BAT from here on).
`
`The system software update BAT is identified by the system software update bouquet_id 0xFF00, and if the
`country_availability_descriptor is used, the country code applicable should be 902 (all countries). This allows a receiver
`to quickly identify it. If the system software update BAT is carried in the transport stream of a network it shall be the
`same as in any other transport stream of that network carrying the system software update BAT.
`
`NOTE: The preferred positioning of this descriptor is in the NIT. On large networks which operate in an
`partitioned way (typical for satellite) it may be prohibitive to carry this descriptor in the NIT (e.g. due to
`size constraints of the NIT), in which case carriage in the system software update BAT is appropriate.
`
`If OUIs (plus additional selector bytes) are listed in the linkage_descriptor the list of OUIs shall be complete in that it
`shall convey information about all software upgrades conveyed on the respective service. This allows a receiver to
`conclusively detect that it may not have to further explore a service. A specific OUI with value 0x00015A has been
`reserved by DVB. This OUI might be used for other purposes despite the System Software Update described in the
`present document. Within the scope of the present document it is used to signal that the data_broadcast_id_descriptor
`does not signal any specific OUI. In that case further selection information shall be carried either in the standard data
`carousel or the Update Notification Table as referenced in the descriptor. If the DVB OUI is used only this single OUI
`shall be contained in the loop of the data_broadcast_id descriptor. There can be multiple descriptors in the NIT or
`system software update BAT to allow multiple system software update services to be identified. It is specifically not the
`intention to remove this descriptor from the NIT or BAT in case of temporary absence of the service. For this purpose
`specific organization identification (OUI) shall not be removed from this descriptor in case of temporary absence of a
`system software update service for receivers of identified organization.
`
`ETSI
`
`9
`
`

`

`10
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`6.1
`
`Linkage Descriptor for Systems Software Update
`
`Table 1: Syntax for the private data bytes for linkage type 0x09
`
`Syntax
`System_software_update_link_structure(){
` OUI_data_length
`
`for (i=0; i<N; i++){
`
`
` OUI
`
`
`
`selector_length
`
`
`
`for (j=0; j<N; j++){
`
`
`
`
`
`
`
`selector_byte
`
`
`
`}
`
`}
`
`for (i=0; i<N; i++){
`
`
`
`
`
`private_data_byte
`
`}
`}
`
`No. of bits
`
`8
`
`24
`8
`
`8
`
`8
`
`Identifier
`
`uimsbf
`
`bslbf
`uimsbf
`
`uimsbf
`
`uimsbf
`
`Semantics of the private data bytes for linkage type 0x09:
`
`OUI_data_length: this field specifies the total length in bytes of the following OUI-loop.
`
`OUI: this is a 24-bit field containing an IEEE OUI (as described in IEEE 802-1990 [5]) of the organization providing a
`system software update service on the transport-stream/service. DVB has defined OUI 0x00015A to signal that the
`stream is from any OUI.
`
`selector_length: this 8-bit field specifies the total length in bytes of the following selector field.
`
`selector_byte: this field provides information additional to the OUI that can be used by a receiver to locate and identify
`the system software update service, e.g. model type or ranges. The syntax and semantics of the selector field are defined
`by the organization owning the OUI.
`
`private_data_byte: this is an 8-bit field, the value of which is privately defined.
`
`6.1.1
`
`SSU Scan Linkage Descriptor
`
`This linkage descriptor defines a pointer to a transport stream carrying a system software update BAT or NIT with
`detailed signaling information about system software update services. The linkage type for this descriptor shall be 0x0A
`and may be inserted into a BAT or NIT.
`
`It is different from a linkage descriptor of type 0x09 in the sense that this descriptor does not contain any OUI specific
`data. It may be exploited by the receiver to quickly acquire the multiplex carrying the system software update BAT or
`NIT without the need of scanning all multiplexes. The use of the linkage descriptor of type 0x0A is therefore
`complementary to the use of the linkage descriptor of type 0x09 in the NIT or system software update BAT.
`
`The table_type field indicates whether the SSU Scan Linkage Descriptor points to a NIT or BAT on the target transport
`stream.
`
`The use of this descriptor is optional.
`
`ETSI
`
`10
`
`

`

`11
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`Table 2: Syntax for the Linkage Descriptor of type 0x0A
`
`Syntax
`
`linkage_descriptor(){
`
`descriptor_tag
`
`descriptor_length
`
`transport_stream_id
`
`original_network_id
`
`service_id
`
`linkage_type
`
`if (linkage_type =0x0A){
`
`
`table_type
`
`}
`}
`
`No. of bits
`
`8
`8
`16
`16
`16
`8
`
`8
`
`
`
`Identifier
`
`uimsbf
`uimsbf
`uimsbf
`uimsbf
`uimsbf
`uimsbf
`
`bslbf
`
`
`
`Semantics for the linkage descriptor of type 0x0A:
`
`transport_stream_id: this is a 16-bit field which identifies the TS containing the system software update BAT or NIT
`
`original_network_id: this 16-bit field gives the label identifying the network_id of the originating delivery system of
`system software update BAT or NIT indicated.
`
`service_id: this is a 16-bit field which is not relevant, and shall be set to 0x0000.
`
`linkage_type: this is an 8-bit field specifying the type of linkage, and shall be set to 0x0A.
`
`table_type: this is an 8-bit field containing a flag pointing either to the system software update BAT or NIT
`
`Value
`0x00
`0x01
`0x02
`0x03 – 0xFF
`
`Table 3: Table_type flag
`
`Description
`
`not defined
`NIT
`BAT
`reserved for future use
`
`7
`
`PSI signalling
`
`The PMT of the transport stream carrying system software update data shall contain the data_broadcast_id descriptor
`with the data broadcast id of 0x000A to indicate the elementary stream used for the system software update service.
`
`The descriptor is considered essential for the location of a system software update service in all of the following cases:
`
`•
`
`•
`
`•
`
`The descriptor provides an entry point to a proprietary stream.
`
`The descriptor provides the entry point to a standard two-layer data carousel without further reference from a
`table.
`
`The descriptor provides the reference to a Update Notification Table.
`
`In these cases this descriptor shall be present on a "semi-static" basis; i.e. the identification of the system software
`update service operator shall not be removed from the PMT if there is presently no system software update service, but
`it is expected that there will be in the near future.
`
`The descriptor may contain specific OUIs (plus selector bytes), in which case the list of OUIs (plus selector bytes) shall
`be complete.
`
`ETSI
`
`11
`
`

`

`12
`
`ETSI TS 102 006 V1.2.1 (2002-10)
`
`A specific OUI with value 0x00015A has been reserved by DVB. This OUI might be used for other purposes despite
`the System Software Update described in the present document. Within the scope of the present document it is used to
`signal that the data_broadcast_id_descriptor does not signal any specific OUI. In that case further selection information
`shall be carried either in the standard data carousel or the Update Notification Table as referenced in the descriptor. If
`the DVB OUI is used only this single OUI shall be contained in the loop of the data_broadcast_id descriptor. There can
`be multiple descriptors in the NIT or system software update BAT to allow multiple system software update services to
`be identified. So it is specifically not the intention to remove this descriptor from the NIT or BAT in case of temporary
`absence of the service. For the same purpose specific organization identification shall not be removed from this
`descriptor in case of temporary absence of a system software update service for receivers of identified organization.
`
`Where a separate standard update carousel is used for each OUI (plus applicable selector bytes), the
`data_broadcast_id_descriptor in the PMT shall contain the single OUI (plus selector bytes) for each component. This
`allows vendor unique identification of proprietary format streams and provides for additional convenience for the
`receiver in the process to identify the appropriate elementary stream in case there is only one applicable option.
`
`It should be noted that the data_broadcast_id_descriptor for a system software update service is defining a single
`elementary stream. A single program can encompass multiple elementary streams and thus multiple system software
`update streams (carousels), each of which shall be described by its own data_broadcast_id_descriptor. A system
`software update stream can also be carried as a component of another service, which may simplify network
`management.
`
`7.1
`
`Data Broadcast Id Descriptor selector byte definition for
`System Software Update
`
`data_broadcast_id: this field shall be set to 0x000A to indicate a system software update service (see ETR 162 [3]).
`
`selector_byte: the selector bytes shall convey the system_software_update_info structure which is defined as follows.
`
`Table 4: Syntax for the system_software_update_info structure
`
`Syntax
`
`system_software_update_info(){
` OUI_data_length
`
`for (i=0; i<N; i++){
`
` OUI
`
`
`reserved
`
`
`update_type
`
`
`reserved
`
`
`update_versioning_flag
`
`
`update_version
`
`
`selector_length
`
`
`for (j=0; j<N; j++){
`
`
`
`selector_byte
`
`
`}
`
`}
`
`for (i=0; i<N; i++){
`
`
`private_data_byte
`
`}
`}
`
`No. of bits
`
`8
`
`24
`4
`4
`2
`1
`5
`8
`
`8
`
`Identifier
`
`uimsfb
`
`bslbf
`
`
`
`
`
`uimsbf
`
`uimsbf
`
`
`8
`
`
`uimsbf
`
`Semantics of the id_selector bytes for data_broadcast_id 0x000A:
`
`OUI_data_length: this field specifies the total length in