KR100783400B1 - Method for using manufacturer specific data of manufacturer information structure in digital video broadcasting - Google Patents

Abstract

The present invention relates to a method of utilizing manufacturer information in the DVB standard, and in particular, to improve the update of the software and the user interface by adding the manufacturer information to the specification for the Over the Air Software download function of the British digital TV. The purpose. To this end, the present invention comprises the first step of checking the detailed product model and version information of the software by using the model descriptor; A second step of confirming detailed version information of the software by using a version descriptor after executing the first step; A third step of allowing a user to request a service from a manufacturer through a contact phone list descriptor after executing the second step; After the third step, the fourth step of checking for errors in the software using the image checksum descriptor. Therefore, the present invention has the effect of defining additional information in the descriptor values 0x80 to 0xFF in the manufacturer information to improve the user interface for updating the downloaded software and for service in the event of a malfunction of the digital TV.

Description

METHOD FOR USING MANUFACTURER SPECIFIC DATA OF MANUFACTURER INFORMATION STRUCTURE IN DIGITAL VIDEO BROADCASTING}

1 is an exemplary view showing a conventional wireless software download method.

Figure 2 is an exemplary view showing the operation flow of the manufacturer information utilization method in the present invention DVB standard.

The present invention relates to a method of utilizing manufacturer information in the DVB standard, and in particular, DVB which improves the software update and user interface by adding the manufacturer information to the specification for the over the air software download function of the British digital TV. It relates to the use of manufacturer information in the specification.

Typically, software on digital TVs has been programmed at the time of product launch, and if upgrades are required, servicemen can update themselves by traveling out of business or by downloading software from the manufacturer's website or by mail. do.

Another method is an over-air software download method, which will be described below with reference to FIG. 1.

The software 2 of the digital TV is encoded in a protocol called an object carousel of the DSMCC (Digital System Multimedia Communication Control) standard (ISO13818-6).

The manufacturer of the digital TV encodes the software (2) according to the object carousel protocol and delivers it to the broadcasting station. The broadcasting station then multiplexes the software on its multiple channels (4) to transmit the digital broadcasting (3) together. send.                         

At this time, the manufacturer's digital TV 6 receives the digital broadcast and checks the software stream 8 to update the software stored in the flash ROM when update information is received.

The specification for the wireless software download method is based on the DVB specification and in more detail according to the specifications proposed by the manufacturer's group, which releases the product to the UK market.

In addition, the object carousel protocol is in accordance with the "Digital Terrestrial Television Multimedia and Hypermedia Experts Group (MHEG) -5 Specification v1.04.4" proposed by the UK DTT.

The manufacturer of the digital TV defines an undefined area of Download Server Initiate (DSI) as MIS (Manufacturer Information Structure) in the UK DTT object carousel protocol to execute the wireless software download method.

Here, the structure of the DSI will be described first.

Syntax No. of bytes downloadServerInitiate { dsmccMessageHeader () serverId 20 privateDataLength 2 for (i = 0; i <PrivateDataLength; I ++) { privateDataByte One } }

In the above structure, ServiceGateway information is contained in the privateDataByte area.

The structure of the ServiceGateway information is as follows.

Syntax bit Type Value Comment ServiceGatewayInfo () {   IOP :: IOR () + see Table 4-3   downloadTaps_count 8 uimsbf N1 software download taps   for (i = 0; i <NI; I ++) {     tap () 8 uimsbf +   }   serviceContextList_count 8 uimsbf N2 serviceContextList   for (i = 0; i <N2; i ++) {     serviceContextList_data_byte 8 uimsbf +   }   userInfoLength 16 uimsbf N3 0 in DTG, But used from now   for (i = 0; i <N3; i ++) { This will store MIS ()     userInfo_data_byte 8 uimsbf +   } }

Here, userInfo_data can be ignored in the current DTT compatible SET. The manufacturer of a digital TV uses MIS (Manufacturer Information Structure) in this area for over-the-air software download (OAD).

The structure of the MIS is as follows.

Syntax bit Type Value manufacturer_information_structure () {   manufacturer_information_tag 8 bslbf oxE0   manufacturer_data_length 16 uimsbf N   manufacturer_id 24 uimsbf 00E091   version_id 32 uimsbf     manufacturer specific data [N-7] }

In this case, the manufacturer specific data stores the information required by the manufacturer and inserts the information of the software to be currently performed.

In the wireless software download standard, it is proposed to store necessary information in a descriptor format in the manufacturer specific data field.

Currently, the information suggested by the standard is

Optional download slot descriptor (current download)

Optional next download slot descriptor

Optional download priority descriptor

Optional user information

Manufacturers can add manufacturer specific data using descriptor values 0x80-0xFF

It is an object of the present invention to provide a method of utilizing manufacturer information in the DVB standard in which a manufacturer defines additional information in descriptor values 0x80 to 0xFF for a specific purpose to improve software update and user interface.

The present invention for achieving the above object, the first step of checking the version information of the detailed product model and software using the model descriptor; A second step of confirming detailed version information of the software by using a version descriptor after executing the first step; A third step of allowing a user to request a service from a manufacturer through a contact phone list descriptor after executing the second step; After the third step, the fourth step of checking for errors in the software using the image checksum descriptor.                     

Hereinafter, an embodiment according to the present invention will be described in detail with reference to the accompanying drawings.

FIG. 2 is an operation flowchart illustrating a method of utilizing manufacturer information in the DVB standard of the present invention, and as shown therein, a first step (S1) of checking detailed product model and software version information using a model descriptor; A second step (S2) of confirming detailed version information of the software by using a version descriptor after executing the first step (S1); A third step (S3) of allowing a user to request a service from a manufacturer through a contact phone list descriptor after executing the second step (S2); An embodiment of the present invention will be described as consisting of a fourth step S4 of checking an error of software using the image checksum descriptor after executing the third step S3.

First, the structure of the model descriptor is as follows.

□ model descriptor ()

New format (00/06/10) Bits Value LGE_idtv_model_descriptor () { 0x80   descriptor_tag 8   descriptor_length 8 1 + N1 + 4   Modelnamelength 8 N1   Modelname [] N1 Ex) IDTV 32 1   version 32 EX) 0x00000001 }

Here, the descriptor tag (descriptor_tag) is 8 bits, the descriptor length (descriptor_length) is 8 bits, and the stored value is the model name length (Modelnamelength), the model name (Modelname []), and the number of bytes of the version, and the model The name length (Modelnamelength) is 8 bits, the value stored is the number of bytes of the model name (Modelname []), the model name (Modelname []) is N1 bits, and the value stored is, for example, IDTV 32 1, version (version) is 32 bits and the value stored is, for example, 0x00000001.

The model descriptor is used to define a model in more detail in addition to the IEEE OUI number when downloading the software, and stores product model and version information.

In addition, the structure of the version descriptor is as follows.

□ Version descriptor ()

NEW version format (2001/05, LP) Bits Value LGE_VersionNumber () {   SW_ReleaseVer 4 Release Version Number   SW_MajorVer 4 Major Version Number   SW_MinorVer 4 Minor Version Number   HW_ChangeVEr 4 Hardware change Version Number   EEPROM_VER 4 EEPROM Version Number   Reserved1, 2, 3 12 Reserved field }

Here, the release version (SW_ReleaseVer) is 4 bits, the value stored is the public version value, the major version (SW_MajorVer) is 4 bits, the value stored is the major version value, the minor version (SW_MinorVer) is 4 bits, and the stored value Is the minor version value, the hardware version (HW_ChangeVEr) is 4 bits, the value stored is the hardware version value, the YEPROM version is 4 bits, and the stored value is the Y version version, reserved (Reserved1, 2, 3) is 12 bits and is a reserved field.

The version descriptor is used to obtain detailed version information of the downloaded software. Since the version information in the initial area of the MIS (Manufacturer Information Structure) is difficult to cope with the market situation, the detailed version information of the software is obtained. Used to provide

In addition, the structure of the contact phone list descriptor is as follows.

□ Contact phone list descriptor ()

Bits Value LGE_contact_phonelist_descriptor () { 0x81   descriptor_tag 8   descriptor_length 8   Number_of_phone 8   For (I = 0; I <Number_of_phone; I ++) { This field is objected for providing additional telephone number information (ex) localixed service provider lists here this descriptor must not be exeeds 255 bytes     Phone_number []     Description []   }   nextindicator 8 Next list is exist or not, 0x01: exist next list, 0x00: end of phonelists }

Here, the descriptor tag (descriptor_tag) is 8 bits, the descriptor length (descriptor_length) is 8 bits, the phone number (Number_of_phone) is 8 bits, and the telephone number list is phone number information (Phone_number) of the local service provider (Description []). []), And the nexttindicator indicates whether there is another list of telephone numbers.

The contact phone list descriptor is used to provide the service provider's information to the user, and in any situation, the user can contact the manufacturer for software related information or to use the current information to contact the manufacturer in case of problems. do.

Finally, the structure of the image checksum descriptor is as follows.                     

Image Checksum descriptor ()

Bits Value LGE_image_checksum_descriptor () { 0x82   descriptor_tag 8   descriptor_length 8   Checksum_algorithm 8   Checksum_data [] This fields contains image checksum data After download image, use checksum_algorithm and must compare result with this value }

Here, the descriptor tag (descriptor_tag) is 8 bits, the descriptor length (descriptor_length) is 8 bits, the checksum algorithm (Checksum_algorithm) is 8 bits, and the checksum data (Checksum_data []) is the downloaded software calculated by the checksum algorithm. Checksum compared to the checksum of.

The image checksum descriptor is a descriptor necessary for confirming whether the software is properly transmitted or forged in the middle after downloading the software by performing the wireless software download method.

The checksum algorithm of the image checksum descriptor checks the software and, according to the type of algorithm, encrypts / decrypts the software to be transmitted. The checksum algorithm then compares the checksum data to verify that the software is transmitted without error and forgery.

As described in detail above, the present invention has the effect of defining additional information in the descriptor values 0x80 to 0xFF in the MIS to improve the user interface for updating the downloaded software and service in the event of a malfunction of the digital TV.

Claims (5)

A first step of checking detailed product model and version information of the software by using the model descriptor; A second step of confirming detailed version information of the software by using a version descriptor after executing the first step; A third step of allowing a user to request a service from a manufacturer through a contact phone list descriptor after executing the second step; And a fourth step of checking an error of software using an image checksum descriptor after executing the third step. The method of claim 1, wherein the model descriptor comprises: a descriptor tag declared as 8 bits; A descriptor length declared in 8 bits and storing the model name length, the model name and the number of bytes of the version; A model name length declared in 8 bits and storing the number of bytes of the model name; A model name for storing the model name; Method of utilizing manufacturer information in the DVB specification, characterized in that it consists of a version declared as 32-bit and storing the version value. 2. The system of claim 1, wherein the version descriptor comprises: a release version declared as 4 bits and storing a public version value; A major version declared in 4 bits and storing a major version value; A minor version declared in 4 bits and storing a minor version value; A hardware version declared in 4 bits and storing a hardware version value; An ypyrom version that is declared as 4 bits and stores an ypyrom version value; Method of utilizing manufacturer information in a DVB specification characterized by consisting of a reservation which is a reserved field declared as 12 bits. 2. The method of claim 1, wherein the contact phone list descriptor comprises: a descriptor tag declared with 8 bits; A descriptor length declared in 8 bits; A phone number declared in 8 bits; A telephone number list for providing telephone number information of a local service provider by a value stored in the phone number; Method of utilizing manufacturer information in the DVB standard, characterized by consisting of the next indicator indicating whether there is another list of telephone numbers. The method of claim 1, wherein the image checksum descriptor comprises: a descriptor tag declared with 8 bits; A descriptor length declared in 8 bits; A checksum algorithm declared with 8 bits; And a checksum data storing a checksum compared with a checksum of downloaded software calculated by the checksum algorithm.

Images