CN102186105B

CN102186105B - Digital television program playing system, method and digital television receiving terminal

Info

Publication number: CN102186105B
Application number: CN 201110099751
Authority: CN
Inventors: 张神力; 周奇
Original assignee: Shenzhen Skyworth Digital Technology Co Ltd
Current assignee: Shenzhen Skyworth Digital Technology Co Ltd
Priority date: 2011-04-20
Filing date: 2011-04-20
Publication date: 2013-03-13
Anticipated expiration: 2031-04-20
Also published as: CN102186105A

Abstract

The invention discloses a digital television program playing system, which comprises a server and at least one digital television receiving terminal, wherein the server sets video on demand (VOD) protocol specifications in advance, and transmits a VOD service list and additional information thereof to the digital television receiving terminal in a broadcasting way according to the OOD protocol specifications; and the digital television receiving terminal sets the VOD protocol specifications in advance, stores the VOD service list and the additional information thereof transmitted by the server into an on demand program database according to the VOD protocol specifications, matches a related program in the on demand program database according to a matched identifier input by a user, displays the related program to the user, receives a program on demand request from the user, acquires a television program from the server according to the program on demand request, and plays the acquired television program to the user. The digital television program playing system actively transmits the on demand program list and the additional information thereof to a set-top box, and the acquisition speed of the on demand program list is increased.

Description

The Play System of digital television program, method and receiving terminal for digital television

Technical field

The invention belongs to the digital television techniques field, relate in particular to Play System, method and the receiving terminal for digital television of digital television program.

Background technology

Along with the propelling of the integration of three networks, the Two-way of set-top box has become a kind of trend, and based on the professional high praise that also more and more is subject to people of video request program (VOD) that Two-way Network is transformed, the implementation method of various browsers and video request program is arisen at the historic moment.

Under the prior art, bi-directional set-top box is realized VOD service needed integrating browsing device; And the implementation method of different VOD needs integrated different browser.

The implementation method of existing VOD, set-top box is obtained program request the rendition list needs the forward end server to send program request the rendition list request of obtaining, issue the request program tabulation after the success of front end authentication, when concurrent number is too many, may cause network congestion, and network delay may to obtain program request the rendition list speed too slow, affect the user and experience greatly.

Under the prior art, the request program tabulation that issues shows at the set-top box end by browser, the request program limited amount that provides, and do not have locating function.

And also there is following shortcoming in prior art:

(1), the speed of obtaining program request the rendition list is slow, and might cause network congestion, greatly affect the user and experience.

(2), passively issue request program tabulation.

(3), when the request program tabulation issues, less than the excellent audio frequency and video fragment relevant with request program, be not easy to attract the user to watch request program.

(4), need the integrating browsing device, give the integrated complexity of having brought of software, and different browsers is difficult to accomplish compatibility to different VOD, give the integrated risk of having brought.

(5), the request program limited amount that provides, and do not have locating function.

In sum, how initiatively set-top box is issued the request program tabulation, improve the acquisition speed of request program tabulation, promote the user and experience, be one of direction of digital television techniques area research.

Summary of the invention

The purpose of the embodiment of the invention is to provide a kind of Play System, method and receiving terminal for digital television of digital television program, and that is intended to active issues the request program tabulation to set-top box, improves the acquisition speed of request program tabulation, promotes user's experience.

The embodiment of the invention is achieved in that a kind of Play System of digital television program, and described system comprises server and at least one receiving terminal for digital television;

Wherein, described server sets in advance the VOD protocol specification, and according to the VOD protocol specification VOD service lists and satellite information thereof is sent to described receiving terminal for digital television by the mode of broadcasting;

Described receiving terminal for digital television, set in advance the VOD protocol specification, and according to the VOD protocol specification VOD service lists and the satellite information thereof that described server sends is stored to the request program database, under described VOD protocol specification, the data structure of the data flow of transmitting between described server and described receiving terminal for digital television comprises that linkage descriptor, VOD service lists section, VOD business information section, price are with reference to descriptor, image data section and audio frequency and video fragment insertion information;

Described receiving terminal for digital television, also in described request program database, mate relevant program and be shown to the user according to the matching identification of user's input, and, receive user's play-on-demand program request, obtain TV programme according to described play-on-demand program request from described server and play to the user.

According to one preferred embodiment of the present invention, when described receiving terminal for digital television mates relevant program and is shown to the user according to user's matching identification in described request program database, comprise described VOD service lists and satellite information thereof are shown to the user, select program by the user according to described VOD service lists and satellite information thereof; And

The matching identification that directly receives user's input is mated relevant program in described request program database.

According to one preferred embodiment of the present invention, when described receiving terminal for digital television obtains VOD service lists and satellite information thereof from data flow, comprising:

Resolve and receive VOD service lists section, obtain the address information of VOD service lists and described server;

Resolve and receive VOD business information section, obtain the relevant information of VOD business;

Resolve and receive price with reference to descriptor, obtain professional way of paying, price relevant information;

Resolve and reception image data section, obtain corresponding image data;

Resolve and receive the audio frequency and video fragment and insert information, storage VOD business information section middle pitch video segment inserts the associated audio frequency and video sheet section business of information.

According to one preferred embodiment of the present invention, described receiving terminal for digital television, also be used for obtaining VOD service lists version number from data flow, the VOD service lists version number that obtains and the VOD service lists version number that is stored in the described request program database are compared, if inconsistent, then described VOD service lists is upgraded.

An also purpose of the embodiment of the invention is to provide a kind of player method of digital television program, and described method comprises:

Server and at least one receiving terminal for digital television are provided;

Described server, set in advance the VOD protocol specification, and according to the VOD protocol specification VOD service lists and satellite information thereof the mode by broadcasting is sent to described receiving terminal for digital television, under described VOD protocol specification, the data structure of the data flow of transmitting between described server and described receiving terminal for digital television comprises that linkage descriptor, VOD service lists section, VOD business information section, price are with reference to descriptor, image data section and audio frequency and video fragment insertion information;

Described receiving terminal for digital television sets in advance the VOD protocol specification, and according to the VOD protocol specification VOD service lists and the satellite information thereof that described server sends is stored to the request program database;

Described receiving terminal for digital television mates relevant program and is shown to the user according to the matching identification of user's input in described request program database;

Described receiving terminal for digital television receives user's play-on-demand program request, obtains TV programme according to described play-on-demand program request from described server and plays to the user.

According to one preferred embodiment of the present invention, when described receiving terminal for digital television mates relevant program and is shown to the user according to user's matching identification in described request program database, comprising:

Described VOD service lists and satellite information thereof are shown to the user, select program by the user according to described VOD service lists and satellite information thereof; And

According to one preferred embodiment of the present invention, when described receiving terminal for digital television obtains VOD service lists and satellite information thereof from data flow, may further comprise the steps:

Resolve and reception image data section, obtain corresponding image data;

According to one preferred embodiment of the present invention, described method is further comprising the steps of:

Described receiving terminal for digital television, from data flow, obtain VOD service lists version number, the VOD service lists version number that obtains and the VOD service lists version number that is stored in the described request program database are compared, if inconsistent, then described VOD service lists is upgraded.

An also purpose of the embodiment of the invention is to provide a kind of receiving terminal for digital television, and described receiving terminal for digital television comprises:

Memory module, be used for pre-stored VOD protocol specification, and according to the VOD protocol specification VOD service lists and the satellite information thereof that described server sends is stored to the request program database, under described VOD protocol specification, the data structure of the data flow of transmitting between described server and described receiving terminal for digital television comprises that linkage descriptor, VOD service lists section, VOD business information section, price are with reference to descriptor, image data section and audio frequency and video fragment insertion information;

Display module is used for mating relevant program and being shown to the user at described request program database according to the matching identification of user's input;

Playing module is used for receiving user's play-on-demand program request, obtains TV programme according to described play-on-demand program request from described server and plays to the user.

According to one preferred embodiment of the present invention, described receiving terminal for digital television also comprises:

Matching module is used for receiving the matching identification of user's input at the relevant program of described request program database coupling.

Acquisition module is used for resolving and reception VOD service lists section, obtains the address information of VOD service lists and described server; Resolve and receive VOD business information section, obtain the relevant information of VOD business; Resolve and receive price with reference to descriptor, obtain professional way of paying, price relevant information; Resolve and reception image data section, obtain corresponding image data; Resolve and receive the audio frequency and video fragment and insert information, storage VOD business information section middle pitch video segment inserts the associated audio frequency and video sheet section business of information.

The contrast module is used for obtaining VOD service lists version number from data flow, and the VOD service lists version number that obtains and the VOD service lists version number that is stored in the described request program database are compared; If inconsistent, then control described acquisition module described VOD service lists is upgraded.

By above-described embodiment, the present invention can initiatively issue the request program tabulation to set-top box, has improved the acquisition speed of request program tabulation, has promoted user's experience, is conducive to popularizing of the receiving terminal for digital television such as set-top box.

Description of drawings

Fig. 1 is the structure chart of the Play System of the digital television program that provides of the embodiment of the invention;

Fig. 2 is the corresponding relation figure of table_id and its section that identifies in the VOD protocol specification that provides of the embodiment of the invention;

Fig. 3 be linkage descriptor section_type, stream_type in the VOD protocol specification that provides of the embodiment of the invention corresponding relation with and the data type figure of sign;

Fig. 4 is VOD service lists section vod_service_type is different in the VOD protocol specification that provides of the embodiment of the invention value and the corresponding relation figure of VOD type of service;

Fig. 5 is the corresponding relation figure of VOD business information section vod_service_info_type numerical value and type in the VOD protocol specification that provides of the embodiment of the invention;

Fig. 6 is the corresponding relation figure of VOD business information section picture_format value and picture format in the VOD protocol specification that provides of the embodiment of the invention;

Fig. 7 be in the VOD protocol specification that provides of the embodiment of the invention price with reference to the corresponding relation figure of descriptor pay_mode value and way of paying;

Fig. 8 is the logical relation of data structure under the VOD protocol specification that provides of the embodiment of the invention and the structure chart of organizational form;

Fig. 9 is an example structure figure of the set-top box that provides of the embodiment of the invention;

Figure 10 is the flow chart that the set-top box that provides of the embodiment of the invention is resolved VOD service lists and satellite information thereof;

Figure 11 is the flow chart that the set-top box end that provides of the embodiment of the invention upgrades VOD service lists and satellite information thereof;

Figure 12 is the flow chart of the video request program that provides of the embodiment of the invention;

Figure 13 is the program request surface chart that the embodiment of the invention provides;

Figure 14 is the request program search interface figure that the embodiment of the invention provides;

Figure 15 is the flow chart of the player method of the digital television program that provides of the embodiment of the invention;

Figure 16 is the structure chart of the receiving terminal for digital television that provides of the embodiment of the invention.

Embodiment

In order to make purpose of the present invention, technical scheme and advantage clearer, below in conjunction with drawings and Examples, the present invention is further elaborated.Should be appreciated that specific embodiment described herein only in order to explain the present invention, is not intended to limit the present invention.

Fig. 1 shows the structure of the Play System of the digital television program that the embodiment of the invention provides, and described system comprises server 11 and at least one receiving terminal for digital television 12.

Wherein, described server 11 sets in advance the VOD protocol specification, and according to the VOD protocol specification VOD service lists and satellite information thereof is sent to described receiving terminal for digital television 12 by the mode of broadcasting;

Described receiving terminal for digital television 12 sets in advance the VOD protocol specification, and according to the self-defining VOD protocol specification of invention VOD service lists and the satellite information thereof that described server 11 sends is stored to the request program database;

Described receiving terminal for digital television 12 also mates relevant program and is shown to the user according to the matching identification of user's input in described request program database, and, receive user's play-on-demand program request, obtain TV programme according to described play-on-demand program request from described server 11 and play to the user.

Wherein, when described receiving terminal for digital television 12 mates relevant program and is shown to the user according to user's matching identification in described request program database, comprise described VOD service lists and satellite information thereof are shown to the user, select program by the user according to described VOD service lists and satellite information thereof; The matching identification that directly receives user's input is mated relevant program in described request program database.

Wherein, under described VOD protocol specification, the data structure of the data flow of transmitting between described server and described receiving terminal for digital television comprises that linkage descriptor, VOD service lists section, VOD business information section, price are with reference to descriptor, image data section and audio frequency and video fragment insertion information, specific descriptions see also hereinafter, wouldn't give unnecessary details herein.

In specific implementation process, when described receiving terminal for digital television obtains VOD service lists and satellite information thereof from data flow, comprising: resolve and receive VOD service lists section, obtain the address information of VOD service lists and described server; Resolve and receive VOD business information section, obtain the relevant information of VOD business; Resolve and receive price with reference to descriptor, obtain professional way of paying, price relevant information; Resolve and reception image data section, obtain corresponding image data; Resolve and receive the audio frequency and video fragment and insert information, storage VOD business information section middle pitch video segment inserts the associated audio frequency and video sheet section business of information, specifically describes to see also hereinafter, wouldn't give unnecessary details herein.

In specific implementation process, described receiving terminal for digital television also is used for obtaining VOD service lists version number from data flow, the VOD service lists version number that obtains and the VOD service lists version number that is stored in the described request program database are compared, if inconsistent, then described VOD service lists is upgraded.

The VOD service lists that in transport stream (TS), issues for standard and data structure, logical relation and the organizational form of satellite information thereof.The embodiment of the invention has defined the data structure of VOD protocol specification, comprise: link type (linkage_type) is the linkage descriptor of 0xFE (linkage_descriptor ()), VOD service lists section (vod_service_list_section ()), VOD business information section (vod_service_info_section ()), price is with reference to descriptor (price_reference_descriptor ()), image data section (picture_data_section ()) and audio frequency and video fragment are inserted information (av_segment_insert_info ()), and the embodiment of the invention describes take receiving terminal for digital television as set-top box as example.

Wherein, described link type (linkage_type) is that linkage descriptor (linkage_descriptor ()) link of 0xFE is professional to a VOD service lists; Wherein, transport stream identification in described linkage descriptor symbol (transport_stream_id), original network identification symbol (original_network_id) and task identifier (service_id) can business of unique identification in network, and this business is VOD service lists business; Wherein, described linkage descriptor is professional to this VOD service lists by transport stream identification symbol (transport_stream_id), original network identification symbol (original_network_id) and task identifier (service_id) link.

Wherein, described linkage descriptor (linkage_descriptor ()) also is used for providing the overall information of VOD service lists, comprising: VOD service lists version number (vod_list_version_number), compulsory mark (force_flag), VOD service lists segment table identifier (vod_service_list_section_table_id), segment type 1(section_type_1), the initial table identifier of VOD business information section (vod_service_info_section_start_table_id), VOD business information section sign-off table identifier (vod_service_info_section_end_table_id), segment type 2(section_type_2), the initial table identifier of image data section (picture_data_section_start_table_id), image data section sign-off table identifier (picture_data_section_end_table_id), segment type 3(section_type_3), VOD service lists number (vod_service_list_number), VOD service lists identifier (vod_service_list_id), sub-version number (sub_version_number).

Wherein, described VOD service lists section (vod_service_list_section ()) is used for providing the VOD service lists information that different VOD servers provides, and comprises following critical field: VOD service lists identifier (vod_service_list_id), sub-version number (sub_version_number), last VOD service lists identifier (last_vod_service_list_id), VOD server ip address (vod_server_ip), VOD server ip address for subsequent use (backup_vod_server_ip), the professional number (vod_service_number) of VOD, VOD task identifier (vod_service_id), VOD type of service (vod_service_type), VOD service priority (vod_service_priority), VOD Business Name byte (vod_service_name_byte).

Wherein, described VOD business information section (vod_service_info_section ()) is used for providing the information of VOD traffic aided, comprises following key message: VOD service lists identifier (vod_service_list_id), VOD task identifier (vod_service_id), descriptor (descriptor ()), VOD business information type (vod_service_info_type); Wherein, described VOD business information type (vod_service_info_type) is divided into again textual description, picture description, performer's tabulation, four kinds of different types of audio frequency and video fragment, and various type has again different data structures and critical field; Wherein, described textual description comprises following critical field: the duration (duration) of segmentation marker (segment_flag), business or segmentation, the text character (text_char) that provides textual description, segmentation number (segment_number), segment identifiers (segment_id); Wherein, described picture is described and comprised following critical field: image data segment table identifier (picture_data_section_table_id), picture identification symbol (picture_id), picture format (picture_format), picture size (picture_size), piece number (block_number) are used for providing the overall control information with the picture of VOD traffic aided; Wherein, described performer's tabulation comprises following critical field: performer's number (performer_number), performer's title byte (performer_name_byte), actor information byte (performer_info_byte); Wherein, described audio frequency and video fragment comprises following critical field: transport stream identification symbol (transport_stream_id), original network identification symbol (original_network_id), task identifier (service_id) are used for an audio frequency and video sheet of unique identification section business.

Wherein, described price provides the price of VOD business with reference to relevant information with reference to descriptor (price_reference_descriptor ()), comprise following key message: way of paying (pay_mode), the value different according to pay_mode, corresponding different way of paying and critical field; Wherein, described way of paying comprise impromptu pay-per-view (IPPV), impromptu (IPPT), the PPC Pay Per Channel (PPC) of on time paying; Wherein, described impromptu pay-per-view (IPPV) provides critical field and whenever sees once price count (price_point_per_view); Wherein, described impromptu on time pay (IPPT) price of providing the critical field per minute count (price_point_per_minute); Wherein, described PPC Pay Per Channel (PPC) price that provides each channel of critical field count (price_point_per_channel).

Wherein, described image data section (picture_data_section ()) is used for providing the image data with the VOD traffic aided, comprises following key message: the data byte (data_byte) of table identifier (table_id), picture identification symbol (picture_id), last picture identification symbol (last_picture_id), picture reality.

Wherein, described audio frequency and video fragment insert information (av_segment_insert_info ()) provide audio frequency and video sheet section business and VOD business or VOD traffic segment unique related information, comprise critical field: VOD service lists identifier (vod_service_list_id), VOD task identifier (vod_service_id), segment identifiers (segment_id).By above 3 identification fields that audio frequency and video sheet section business is unique related with business or VOD traffic segment.

More than provided the describe, in general terms of VOD protocol specification data structure, the below is described in detail with regard to the grammatical and semantic of each data structure respectively, and description sequentially is respectively: linkage descriptor (linkage_descriptor ()), VOD service lists section (vod_service_list_section ()), VOD business information section (vod_service_info_section ()), price is with reference to descriptor (price_reference_descriptor ()), image data section (picture_data_section ()), the audio frequency and video fragment is inserted information (av_segment_insert_info ()).

A, VOD protocol specification data structure one: linkage descriptor (linkage_descriptor ()), its form is:

The semantic description of each field is as follows in the defined linkage descriptor (linkage_descriptor ()):

Descriptor_tag: descriptor tag, the 8bit field is used for identifying different descriptors.Be 0x4A at this, represent that this descriptor is linkage descriptor.

Descriptor_length: descriptor length, the 8bit field provides the total length of descriptor.In the expression descriptor, the byte number of the data division that begins after this field.

Transport_stream_id: the transport stream identification symbol, the 16bit field in a transmission system, is used for identifying a unique transport stream.

Original_network_id: the original network identification symbol, the 16bit field is for the network identifier that provides the original transmitted system.

Service_id: task identifier, the 16bit field is used in the different business of transport stream sign.Service_id is corresponding with the program_number among the program_map_section.

Linkage_type: link type, the 8bit field is used for defining link type, for example with VOD service lists service chaining.In SI standard the inside, linkage_type is that 0x80-0xFE is that the user defines use.At this, definition linkage_type is 0xFE, expression and VOD service lists service chaining.Wherein, described VOD service lists business is by the transport_stream_id in the linkage descriptor, original_network_id and the unique appointment of service_id.

Vod_list_version_number:VOD service lists version number, the 5bit field, be used for providing the total version number of VOD service lists section, and VOD protocol specification data structure two: version number (version_number) field in the VOD service lists section (vod_service_list_section ()) is corresponding.When the information of VOD service lists section changed, vod_list_version_number added 1.On dutyly increase at 31 o'clock, be reset to 0.

Reserved: reserve, be used in the future expanded function use.Generally be encoded to " 1 ".

Force_flag: compulsory mark, 1bit field.Be used for pointing out when VOD service lists version number changes, whether to force to upgrade.When its value is " 1 ", when representing that monitoring VOD service lists version number changes, starts immediately VOD service lists and satellite information thereof and upgrade.When its value when " 0 ", when expression monitors VOD service lists version number and changes, can not start immediately VOD service lists and satellite information thereof and upgrade, but when start or user enter the program request interface, upgrade next time.

Vod_service_list_section_table_id:VOD service lists segment table identifier, the 8bit field is used for the affiliated table of sign VOD service lists section.In SI standard the inside, table_id is that 0x80-0xFE is that user's self-defining uses.At this, be defined as 0x80.Wherein, the corresponding relation of table_id and its section that identifies sees also shown in the form shown in Figure 2.

Section_type_1: segment type 1, the 8bit field is used for providing the data type under the VOD service lists section, and the stream_type of the ES described in the PMT of the VOD service lists business that links with linkage descriptor is corresponding.At this, be defined as 0xFF, corresponding, the stream_type that is used for the ES of description VOD service lists section in the PMT of the VOD service lists business that linkage descriptor links is 0xFF, represents that the data structure of this ES meets VOD protocol specification data structure two: the grammer of VOD service lists section (vod_service_list_section ()).The corresponding relation of section_type, stream_type with and the sign data type see also shown in the form shown in Figure 3.

The initial table identifier of vod_service_info_section_start_table_id:VOD business information section, the 8bit field when VOD business information section has a plurality of table, is used for providing the origin identification of table.Shown in the form among Fig. 2, at this, can be in the 0x90-0x9F scope value.With VOD protocol specification data structure three: the table identifier (table_id) of VOD business information section (vod_service_info_section ()) is corresponding, is used for providing the initial table identifier of VOD business information section.

Vod_service_info_section_end_table_id:VOD business information section sign-off table identifier, the 8bit field when VOD business information section has a plurality of table, is used for providing the end sign of table.Form as shown in Figure 2, at this, can be in the 0x90-0x9F scope value.With VOD protocol specification data structure three: the table identifier (table_id) of VOD business information section (vod_service_info_section ()) is corresponding, is used for providing the sign-off table identifier of VOD business information section.

Section_type_2: segment type 2, the 8bit field, be used for providing the affiliated data type of VOD business information section, referring to form shown in Figure 3, at this, be defined as 0xFE, corresponding, the stream_type that is used for the ES of description VOD business information section in the PMT of the VOD service lists business that linkage descriptor links is 0xFE, represents that the data structure of this ES meets VOD protocol specification data structure three: the grammer of VOD business information section (vod_service_info_section ()).

Picture_data_section_start_table_id: the initial table identifier of image data section, the 8bit field when the image data section has a plurality of table, is used for providing the origin identification of table.Form as shown in Figure 2, at this, can be in the 0xA0-0xBF scope value.With VOD protocol specification data structure five: the table identifier (table_id) of image data section (picture_data_section ()) is corresponding, is used for providing the initial table identifier of image data section.

Picture_data_section_end_table_id: image data section sign-off table identifier, the 8bit field when the image data section has a plurality of table, is used for providing the end sign of table.Form as shown in Figure 2, at this, can be in the 0xA0-0xBF scope value.With VOD protocol specification data structure five: the table identifier (table_id) of image data section (picture_data_section ()) is corresponding, is used for providing the sign-off table identifier of image data section.

Section_type_3: segment type 3, the 8bit field, be used for providing the affiliated data type of image data section, referring to form shown in Figure 3, at this, be defined as 0xFD, corresponding, the stream_type that is used for the ES of description image data section in the PMT of the VOD service lists business that linkage descriptor links is 0xFD, represents that the data structure of this ES meets VOD protocol specification data structure five: the grammer of image data section (picture_data_section ()).

Vod_service_list_number:VOD service lists number, the 24bit field, be used for providing the number of VOD service lists, and VOD protocol specification data structure two: last VOD service lists identifier (last_vod_service_list_id) field in the VOD service lists section (vod_service_list_section ()) is corresponding.

Vod_service_list_id:VOD service lists identifier, the 24bit field, be used for the different VOD service lists of sign in a VOD service lists business, and VOD protocol specification data structure two: VOD service lists identifier (vod_service_list_id) field in the VOD service lists section (vod_service_list_section ()) is corresponding.

Sub_version_number: sub-version number, the 5bit field, be used for providing the version number of the VOD service lists that vod_service_list_id identifies, and VOD protocol specification data structure two: sub-version number (sub_version_number) field in the VOD service lists section (vod_service_list_section ()) is corresponding.

Illustrate: when the VOD service lists is abundant, can add a plurality of linkage descriptor (linkage_descriptor ()) in NIT or BAT, link is professional to different VOD service lists.

B, VOD protocol specification data structure two: VOD service lists section (vod_service_list_section ()), its form is:

The semantic description of each field is as follows in the defined VOD service lists section (vod_service_list_section ()):

Table_id: table identifier, the 8bit field, be used for the affiliated table of sign VOD service lists section, be defined herein as 0x80, represent that this section belongs to VOD service lists section, and VOD protocol specification data structure one: VOD service lists segment table identifier (vod_service_list_section_table_id) field is corresponding in the linkage descriptor (linkage_descriptor ()).Specifically referring to form shown in Figure 2.

Section_syntax_indicator: section grammer designator, the 1bit field should put ' 1 '.

Reserved_future_use: keep following the use, keep following expansion and use.

Reserved: reserve, be used in the future expanded function use.Generally be encoded to ' 1 '.

Section_length: segment length, 12bit field, the byte length of this section that its expression begins from the next byte of this field.

Version_number: version number, the 5bit field is used for the total version number of sign VOD service lists section.With VOD protocol specification data structure one: VOD service lists version number (vod_list_version_number) field is corresponding in the linkage descriptor (linkage_descriptor ()).When the information of VOD service lists section changed, version_number added 1.On dutyly increase at 31 o'clock, be reset to 0.

Current_next_indicator: current follow-up designator, 1bit field.When by set, represent that current sublist just is used.When its reset, the expression sublist that passes not yet is used, and it is next with the sublist that is used.

Vod_service_list_id:VOD service lists identifier, the 24bit field, in a VOD service lists business, and table identifier (table_id=0x80) VOD service lists of unique identification together.From " 0x000001 ", VOD service lists of every increase, this value adds 1.With VOD protocol specification data structure one: VOD service lists identifier (vod_service_list_id) field is corresponding in the linkage descriptor (linkage_descriptor ()).

Sub_version_number: sub-version number, the 5bit field is for the version number that provides the uniquely identified VOD of vod_service_list_id institute service lists.With VOD protocol specification data structure one: sub-version number (sub_version_number) field is corresponding in the linkage descriptor (linkage_descriptor ()).When the uniquely identified VOD of vod_service_list_id institute service lists information changes, this value adds 1.On dutyly increase at 31 o'clock, be reset to 0.

Last_vod_service_list_id: last VOD service lists identifier, the 24bit field is used for interior last VOD service lists of table that label table identifier (table_id=0x80) identifies.With VOD protocol specification data structure one: VOD service lists number (vod_service_list_number) field is corresponding in the linkage descriptor (linkage_descriptor ()).

Section_number: segment number, the 8bit field is used for providing the segment number of the sublist that vod_service_list_id identifies, and the section_number of first in the sublist section is designated as " 0x00 ".One of every increase has the section of identical table_id and vod_service_list_id, and section_number just adds 1.

Last_section_number: last segment number, 8bit field, the segment number of last section (being the section of segment number maximum) of sublist that expression vod_service_list_id identifies.

The vod_server_ip:VOD server ip address, the 32bit field is for the IP address contents of describing the VOD server.For example: the VOD server ip address is 192.168.16.100, then is encoded in this field " 0xC0A81064 ".

Backup_vod_server_ip: VOD server ip address for subsequent use, the 32bit field is for the IP address contents of describing VOD server for subsequent use.For example: VOD server ip address for subsequent use is 192.168.16.101, then is encoded in this field " 0xC0A81065 ".

Attention: the business tine on VOD server and the VOD server for subsequent use is just the same, and, each VOD server correspondence a VOD service lists, and namely the middle uniquely identified VOD of the vod_service_list_id institute service lists of VOD service lists section (vod_service_list_section ()) is corresponding one by one in VOD server and the some fixing VOD service lists business.

The professional number of vod_service_number:VOD, the 16bit field is used for being given in the professional number of the uniquely identified VOD of vod_service_list_id institute service lists in the VOD service lists business.

The vod_service_id:VOD task identifier, the 16bit field is used for VOD business of the uniquely identified VOD of vod_service_list_id institute service lists unique identification in a VOD service lists business.

The vod_service_type:VOD type of service, the 8bit field, different values is used for identifying different VOD types of service.The corresponding relation of the value that vod_service_type is different and VOD type of service form as shown in Figure 4.

The vod_service_priority:VOD service priority, the 8bit field is for the priority level that provides vod_service_list_id and the uniquely identified VOD of vod_service_id institute business.

ISO 639-2_language_code:ISO 639-2 language codes, the 24bit field is used for indicating the language that VOD Business Name byte (vod_service_name_byte) field adopts.This field comprises one by 3 character codes of ISO 639-2 definition.ISO 639-2/B and ISO 639-2/T can use.Each character is encoded to 8 according to GB/T 15273.1-1994, and inserts successively 24 bit fields.

For example: 3 character codes " fre " of French may be encoded as: ' 0,110 0,110 0,111 0,010 0,110 0101 '.

Vod_service_name_length:VOD Business Name length, the 8bit field is take the length of byte follow-up VOD Business Name byte field as unit provides.

Vod_service_name_byte:VOD Business Name byte, the 8bit field is for the title that provides the VOD business.

The CRC32:CRC32 verification, the 32bit field has comprised the crc value of this section.

C, VOD protocol specification data structure three: VOD business information section (vod_service_info_section ()), its form is:

The semantic description of each field is as follows in the defined VOD business information section (vod_service_info_section ()):

Table_id: table identifier, the 8bit field, be used for the table under the sign VOD business information section, first table identifier is by VOD protocol specification data structure one: the initial table identifier of VOD business information section (vod_service_info_section_start_table_id) field is given in the linkage descriptor (linkage_descriptor ()).Rear continued adds 1 successively, and last table identifier (maximum) is by VOD protocol specification data structure one: VOD business information section sign-off table identifier (vod_service_info_section_end_table_id) field is given in the linkage descriptor (linkage_descriptor ()).Span is specifically referring to Fig. 2.

Reserved_future_use: keep following the use, keep following expansion and use.

Version_number: version number, the 5bit field is used for providing the version number of the table under the VOD business information section that is identified by table_id.When the information of the table under the VOD business information section changed, version_number added 1.On dutyly increase at 31 o'clock, be reset to 0.

Sub_table_id: the sublist identifier, the 24bit field with the table_id together sublist of a VOD business information of unique identification section, is encoded from " 0x000001 " in network, sublist of every increase, this value adds 1.

Sub_version_number: sub-version number, the 5bit field is for the version number of the sublist that provides table_id and the uniquely identified VOD of sub_table_id institute business information section.

Last_sub_table_id: last sublist identifier, the 24bit field is used for providing last sublist sign of the table under the VOD business information section that table_id identifies, has maximum sublist identifier.

Vod_service_list_id:VOD service lists identifier, 24bit field, VOD service lists of unique identification in VOD service lists business.With VOD protocol specification data structure two: VOD service lists identifier (vod_service_list_id) field is corresponding in the VOD service lists section (vod_service_list_section ()).

Section_number: segment number, the 8bit field is used for providing the segment number of table_id and sub_table_id institute uniquely identified sublist, and the section_number of first in the sublist section is designated as " 0x00 ".One of every increase has the section of identical table_id and sub_table_id, and section_number just adds 1.

Last_section_number: last segment number, 8bit field, the segment number of last section (being the section of segment number maximum) of expression table_id and sub_table_id institute uniquely identified sublist.

The vod_service_id:VOD task identifier, the 16bit field is used in VOD business of the uniquely identified VOD of vod_service_list_id institute service lists unique identification.With VOD protocol specification data structure two: VOD task identifier (vod_service_id) field is corresponding in the VOD service lists section (vod_service_list_section ()).

Vod_service_descriptor_length:VOD traffic descriptor length, the 12bit field is pointed out the total byte length of the descriptor that begins from the next byte of this field.

Descriptor (): descriptor, for the relevant information of describing the VOD business.At this, provide VOD protocol specification data structure four: price with reference to descriptor (price_reference_descriptor ()) as a reference.The user also can insert other existing descriptors according to the needs of using, and perhaps inserts the descriptor of other self-definings.

Vod_service_info_type:VOD business information type, the 4bit field is used for providing the dissimilar of VOD business information, and textual description, picture description, performer's tabulation, audio frequency and video fragment are specifically arranged.The corresponding relation of vod_service_info_type numerical value and type sees also form shown in Figure 5:

Segment_flag: segmentation marker, the 1bit field is used for providing the whether segmentation of vod_service_list_id and the uniquely identified VOD of vod_service_id institute business, represents segmentation for ' 1 ' time, represents not segmentation for ' 0 ' time.

Duration: duration, the 24bit field, the duration that is used for providing the duration (during the not segmentation of VOD business) of vod_service_list_id and the uniquely identified VOD of vod_service_id institute business or is used for providing vod_service_list_id, vod_service_id and the uniquely identified VOD of segment_id institute traffic segment.This field is by 64 BCD coding, when identifying respectively, minute, second.For example: 12:45:30 is encoded as " 0x124530 ".

ISO 639-2_language_code:ISO 639-2 language codes, the 24bit field is used for providing textual description or performer's title or actor information and describes the language that adopts.Concrete semantic referring to VOD protocol specification data structure two: the semanteme of ISO 639-2 language codes (ISO 639-2_language_code) field in the VOD service lists section (vod_service_list_section ()).

Vod_service_info_length:VOD business information length, the 8bit field provides after this field the character length by the textual description of vod_service_list_id and the uniquely identified VOD of vod_service_id institute business take byte as unit.

Text_char: text character, the 8bit field is for the textual description that provides VOD business or VOD traffic segment.Be generally brief business or traffic segment brief introduction.

Segment_number: the segmentation number, the 16bit field is for the segmentation number that provides vod_service_list_id and the uniquely identified VOD of vod_service_id institute business.

Segment_id: segment identifiers, the 16bit field, in vod_service_list_id and the uniquely identified VOD of vod_service_id institute business, segmentation of unique identification.

Segment_info_length: segment information length, the 8bit field provides after this field the character length by the textual description of vod_service_list_id, vod_service_id and the uniquely identified VOD of segment_id institute traffic segment take byte as unit.

Picture_data_section_table_id: image data segment table identifier, the 8bit field, the image data section that is used for sign and VOD traffic aided, and VOD protocol specification data structure five: middle table identifier (table_id) field of image data section (picture_data_section ()) is corresponding.Span is specifically referring to form shown in Figure 2.

Picture_id: picture identification symbol, 24bit field, and image data segment table identifier (picture_data_section_table_id) picture of unique identification together.With VOD protocol specification data structure five: picture identification symbol (picture_id) field is corresponding in the image data section (picture_data_section ()).

Picture_format: picture format, the 8bit field is for the form that provides picture.The corresponding relation of picture_format value and picture format sees also form shown in Figure 6.

Picture_size: picture size, the 32bit field is used for providing the byte number by picture_data_section_table_id and picture_id institute uniquely identified image data.

Block_number: piece number, the 8bit field, be used for providing by picture_data_section_table_id and picture_id institute uniquely identified image data and be encapsulated in VOD protocol specification data structure five: the segments of image data section (picture_data_section ()), and VOD protocol specification data structure five: last segment number (last_section_number) field in the image data section (picture_data_section ()) is corresponding.

Performer_number: performer's number, the 8bit field is for the number that provides featured performer.

Performer_name_length: performer's title length, the 8bit field provides the length of performer's title after this field take byte as unit.

Performer_name_byte: performer's title byte, the 8bit field is for the title that provides the performer.

Performer_info_length: actor information length, the 8bit field provides the afterwards length of actor information of this field take byte as unit.

Performer_info_byte: the actor information byte, the 8bit field, the information for providing the performer is generally the brief introduction of performer's role.

Wherein, transport_stream_id herein, original_network_id and service_id can business of unique identification, and this business provides the profile information of VOD business with the form of audio frequency and video fragment.More than three fields are a kind of business control informations, its effect is similar to linkage descriptor, is used for link to an audio frequency and video sheet section business.

D, VOD protocol specification data structure four: price is with reference to descriptor (price_reference_descriptor ()), and its form is:

Defined price is as follows with reference to the semantic description of each field in the descriptor (price_reference_descriptor ()):

Descriptor_tag: descriptor tag, the 8bit field is used for identifying different descriptors.Be defined herein as 0xFE(in SI standard the inside, provide 0x80-0xFE and be the private setting descriptor label of user's self-defining), represent this descriptor be price with reference to descriptor, be that price is with reference to the unique identification of descriptor.

Descriptor_length: descriptor length, the 8bit field provides the afterwards length of descriptor of this field take byte as unit.

Reserved: keep, be used in the future expanded function use.Generally be encoded to ' 1 '.

Pay_mode: way of paying, the 3bit field is used for providing professional way of paying.The corresponding relation of pay_mode value and way of paying sees also form shown in Figure 7:

Price_point_per_view: see that whenever price once counts, the 24bit field is used for providing impromptu pay-per-view IPPV(Impulse Pay Per View) see whenever that once needed price counts.The price of every some correspondence can have operator to define.

Price_point_per_minute: the price of per minute is counted, and the 24bit field is used for providing instant pay-per-view IPPT(Impulse Pay Per Time) see that whenever one minute needed price counts.

Price_point_per_channel: the price of each channel is counted, and the 24bit field is used for providing PPC Pay Per Channel PPC(Pay Per Channel) the needed price of each channel counts.

E, VOD protocol specification data structure five: image data section (picture_data_section ()), its form is:

The semantic description of each field is as follows in the defined image data section (picture_data_section ()):

Table_id: table identifier, the 8bit field, be used for the table under the sign picture data segment, first table identifier is by VOD protocol specification data structure one: the initial table identifier of image data section (picture_data_section_start_table_id) field is given in the linkage descriptor (linkage_descriptor ()).Rear continued adds 1 successively, and last table identifier (maximum) is by VOD protocol specification data structure one: image data section sign-off table identifier (picture_data_section_start_table_id) field is given in the linkage descriptor (linkage_descriptor ()).This value and with VOD protocol specification data structure three: image data segment table identifier (picture_data_section_table_id) field is unique corresponding in the VOD business information section (vod_service_info_section ()).Span is specifically referring to form shown in Figure 2.

Reserved_future_use: keep following the use, keep following expansion and use.

Version_number: version number, the 5bit field is used for providing the version number of the table under the image data section that is identified by table_id.When the information of the table under the image data section changed, version_number added 1.On dutyly increase at 31 o'clock, be reset to 0.

Picture_id: picture identification symbol, 24bit field, and table identifier (table_id) picture of unique identification together begin coding from " 0x000001 ", picture of every increase, this value adds 1.With VOD protocol specification data structure three: picture identification symbol (picture_id) field is unique corresponding in the VOD business information section (vod_service_info_section ()).

Sub_version_number: sub-version number, the 5bit field provides the version number of table_id and picture_id institute uniquely identified picture.When image data changed, sub_version_number added 1.On dutyly increase at 31 o'clock, be reset to 0.

Last_picture_id: last picture identification symbol, the 24bit field provides picture identification last in the table that is identified by table id, is maximum identifier in all pictures in the table that identifies of table_id.

Section_number: segment number, the 8bit field is used for providing the segment number of table_id and picture_id institute uniquely identified picture sublist, and the section_number of first in the sublist section is designated as " 0x00 ".One of every increase has the section of identical table_id and picture_id, and section_number just adds 1.

Last_section_number: last segment number, the 8bit field, the segment number of last section (being the section of segment number maximum) of expression table_id and picture_id institute uniquely identified picture sublist, and VOD protocol specification data structure three: middle piece number (block_number) field of VOD business information section (vod_service_info_section ()) is corresponding.

Data_byte: data byte, the 8bit field provides the real data of picture.

F, VOD protocol specification data structure six: the audio frequency and video fragment is inserted information (av_segment_insert_info ()), and its form is:

The semantic description of each field is as follows in the defined audio frequency and video fragment insertion information (av_segment_insert_info ()):

Vod_service_list_id:VOD service lists identifier, 24bit field, VOD service lists of unique identification in a VOD service lists business.

The vod_service_id:VOD task identifier, the 16bit field, in a VOD service lists business, vod_service_list_id and vod_service_id can VOD business of unique identification.

Segment_id: segment identifiers, the 16bit field, in network, the some concrete segmentation that vod_service_list_id, vod_service_id and segment_id can VOD business of unique identification.When in VOD protocol specification data structure three: when segmentation marker (segment_flag) field was ' 0 ' in the VOD business information section (vod_service_info_section ()), this field was invalid.

Logical relation and the organizational form of the VOD protocol specification data structure that provides in the embodiment of the invention be provided the below.

Six kinds of different data structures of VOD protocol specification have above been described, in transport stream (TS), the data such as above-mentioned six kinds of different data structures and existing PSI/SI data and picture, audio frequency and video organize together with certain logical relation, thereby form VOD service lists and satellite information thereof.

The logical relation of VOD protocol specification data structure and the structure of organizational form be as shown in Figure 8:

For logical relation and the organizational form of various data structures among Fig. 8, the below provides detailed description.

Structure S801 provides some critical fielies for control in the linkage descriptor (linkage_descriptor ()), and these control fields are used for providing the overall information of VOD service lists and satellite information thereof.Specifically comprise critical field: task identifier (service_id), VOD service lists version number (vod_list_version_number), VOD service lists segment table identifier (vod_service_list_section_table_id), segment type 1(section_type_1), the initial table identifier of VOD business information section (vod_service_info_section_start_table_id), VOD business information section sign-off table identifier (vod_service_info_section_end_table_id), segment type 2(section_type_2), the initial table identifier of image data section (picture_data_section_start_table_id), image data section sign-off table identifier (picture_data_section_end_table_id), segment type 3(section_type_3), VOD service lists number (vod_service_list_number), VOD service lists identifier (vod_service_list_id), sub-version number (sub_version_number).

Structure S802 Program Association Table (PAT) is used for providing the PID of the professional PMT of VOD service lists, specifically comprises critical field: the PID(PMT_PID of program number (Program_number), PMT).

Structure S803 Program Map Table (PMT) is used for providing type and the pid information thereof of the Basic Flow (ES) that VOD service lists business comprises, and specifically comprises critical field: VOD service lists stream type (stream_type=0xFF), VOD service lists PID(vod_service_list_PID), VOD business information stream type (stream_type=0xFE), VOD business information PID(vod_service_info_PID), image data stream type (stream_type=0xFD), image data PID(picture_data_PID).

Structure S804VOD service lists section (vod_service_list_section ()) is used for providing the key message of VOD service lists section, specifically comprises critical field: table identifier (table_id), version number (version_number), VOD service lists identifier (vod_service_listid), sub-version number (sub_version_number), last VOD service lists identifier (last_vod_service_list_id), VOD task identifier (vod_service_id).

Structure S805VOD business information section (vod_service_info_section ()) is used for providing the key message of VOD business information section, specifically comprises critical field: table identifier (table_id), VOD service lists identifier (vod_service_list_id), VOD task identifier (vod_service_id), image data segment table identifier (picture_data_section_table_id), picture identification symbol (picture_id), piece number (block_number), task identifier (service_id).

Structure S806 image data section (picture_data_section ()) is used for providing the key message of image data section, specifically comprises critical field: table identifier (table_id), picture identification symbol (picture_id), last segment number (last_section_number).

Structure S807 Program Association Table (PAT) specifically comprises critical field: the PID(PMT_PID of program number (Program_number), PMT) for the PID of the PMT that provides audio frequency and video sheet section business.

Structure S808 Program Map Table (PMT) is used for providing stream type and the pid information thereof of audio frequency and video sheet section business audio frequency and video, specifically comprises critical field: video segment stream type (stream_type=0xF0), video segment PID(video_segment_PID), audio fragment stream type (stream_type=0xF 1), audio fragment PID(audio_segment_PID).

Wherein, it is professional that task identifier (service_id) in the described structure S801 linkage descriptor (linkage_descriptor ()) is used for VOD service lists of sign, unique related with the program number (Program_number) in the structure S802 Program Association Table (PAT); Wherein, VOD service lists version number (vod_list_version_number) is unique related with the version number (version_number) in the structure S804 VOD service lists section (vod_service_list_section ()); Wherein, VOD service lists segment table identifier (vod_service_list_section_table_id) is unique related with the table identifier (table_id) in the structure S804VOD service lists section (vod_service_list_section ()); Wherein, segment type 1(section_type_1) unique related with the middle VOD service lists stream type (stream_type=0xFF) of structure S803 Program Map Table (PMT); Wherein, the initial table identifier of VOD business information section (vod_service_info_section_start_table_id) is unique related with the table identifier (table_id) in VOD business information section sign-off table identifier (vod_service_info_section_end_table_id) and the structure S805VOD business information section (vod_service_info_section ()); Wherein, segment type 2(section_type_2) unique related with the middle VOD business information stream type (stream_type=0xFE) of structure S803 Program Map Table (PMT); Wherein, the initial table identifier of image data section (picture_data_section_start_table_id) is unique related with image data section sign-off table identifier (picture_data_section_end_table_id) and the middle table identifier (table_id) of structure S806 image data section (picture_data_section ()); Wherein, segment type 3(section_type_3) unique related with the middle image data stream type (stream_type=0xFD) of structure S803 Program Map Table (PMT); Wherein, last VOD service lists identifier (last_vod_service_list_id) is unique related in VOD service lists number (vod_service_list_number) and the structure S804VOD service lists section (vod_service_list_section ()); Wherein, VOD service lists identifier (vod_service_list_id) is unique related with the middle VOD service lists identifier (vod_service_list_id) of structure S804VOD service lists section (vod_service_list_section ()); Wherein, sub-version number (sub_version_number) is unique related with the middle sub-version number (sub_version_number) of structure S 804VOD service lists section (vod_service_list_section ()).

Wherein, the PID(PMT_PID of the PMT in the described structure S802 Program Association Table (PAT)) be used for providing structure S803 Program Map Table (PMT) bag sign.

The sign of wherein, the VOD service lists PID(vod_service_list_PID in the described structure S803 Program Map Table (PMT)) wrapping for the transport stream (TS) that provides structure S804VOD service lists section (vod_service_list_section ()) place; The sign of wherein, VOD business information PID(vod_service_info_PID) wrapping for the transport stream (TS) that provides structure S805VOD business information section (vod_service_info_section ()) place; The sign of wherein, image data PID(picture_data_PID) wrapping for the transport stream (TS) that provides structure S806 image data section (picture_data_section ()) place.

Wherein, VOD service lists identifier (vod_service_list_id) is unique related with the middle VOD service lists identifier (vod_service_list_id) of structure S805VOD business information section (vod_service_info_section ()) in the described structure S804VOD service lists section (vod_service_list_section ()); Wherein, VOD task identifier (vod_service_id) is unique related with the middle VOD task identifier (vod_service_id) of structure S805VOD business information section (vod_service_info_section ()).

Wherein, image data segment table identifier (picture_data_section_table_id) is unique related with the middle table identifier (table_id) of structure S806 image data section (picture_data_section ()) in the described structure S805VOD business information section (vod_service_info_section ()); Wherein, picture identification symbol (picture_id) is unique related with the middle picture identification symbol of structure S806 image data section (picture_data_section ()) (picture_id); Wherein, last segment number (last_section_number) is unique related in piece number (block_number) and the structure S806 image data section (picture_data_section ()); Wherein, task identifier (service_id) is used for audio frequency and video sheet section business of sign, and is unique related with program number (Program_number) in the structure S807 Program Association Table (PAT).

Wherein, the PID(PMT_PID of PMT in the described structure S807 Program Association Table (PAT)) for the bag sign that provides structure S808 Program Map Table (PMT).

Wherein, described structure S808 Program Map Table (PMT) is used for providing stream type and the pid information thereof of audio frequency and video sheet section business audio frequency and video; Wherein, stream_type=0xF0 is used for providing the video segment stream type, video_segment_PID is used for providing video segment PID, stream_type=0xF1 and is used for providing audio fragment stream type, audio_segment_PID for providing audio fragment PID.

Based on logical relation shown in Figure 8 and organizational form, the embodiment of the invention can issue VOD service lists and satellite information thereof in transport stream (TS).Wherein, described VOD service lists and satellite information thereof are by transport stream identification symbol (transport_stream_id), original network identification accord with (original_network_id) in the structure S801 linkage descriptor (linkage_descriptor ()), the unique link of task identifier (service_id) is professional to a VOD service lists; Wherein, described VOD service lists business comprises 3 dissimilar Basic Flows; Wherein, described 3 dissimilar Basic Flows provide stream type and corresponding pid information by structure S803 Program Map Table (PMT); Wherein, the stream type of described 3 Basic Flows as shown in Figure 3, the stream_type that specifically meets the ES of VOD service lists (vod_service_list_section ()) syntactic structure is 0xFF, the stream_type that meets the ES of VOD business information section (vod_service_info_section ()) syntactic structure is 0xFE, and the stream_type that meets the ES of image data section (picture_data_section ()) syntactic structure is 0xFD; Wherein, the Basic Flow (ES) that VOD service lists PID(vod_service_list_PID in the described structure S803 Program Map Table (PMT)) identifies meets VOD protocol specification data structure two: the syntactic structure (counter structure S804) of VOD service lists section (vod_service_list_section ()); Wherein, the Basic Flow (ES) that VOD business information PID(vod_service_info_PID in the described structure S803 Program Map Table (PMT)) identifies meets VOD protocol specification data structure three: the syntactic structure (counter structure S805) of VOD business information section (vod_service_info_section ()); Wherein, the Basic Flow (ES) that image data PID(picture_data_PID in the described structure S803 Program Map Table (PMT)) identifies meets VOD protocol specification data structure five: the syntactic structure (counter structure S806) of image data section (picture_data_section ()).

Wherein, described structure S801 linkage descriptor gives the overall information of VOD service lists and satellite information thereof, specifically comprise: VOD service lists version number is used for providing the total version number of VOD service lists, has when renewal to use in VOD service lists and satellite information thereof; The corresponding stream_type=0xFF of VOD service lists segment table identifier and segment type 1(thereof); The corresponding stream_type=0xFE of the initial table identifier of VOD business information section and VOD business information section sign-off table identifier and segment type 2(thereof); The corresponding stream_type=0xFD of the initial table identifier of image data section and image data section sign-off table identifier and segment type 3(thereof); VOD service lists number is used for providing the total number of VOD service lists, the number of corresponding VOD server, the namely corresponding VOD service lists of VOD server; VOD service lists identifier and sub-version number are used for providing sign and the sub-version number thereof of VOD service lists, use when the VOD service lists is upgraded.

Wherein, there are some differences in the data structure of the TS bag that described structure S808 Program Map Table (PMT) middle pitch video segment PID identifies and the data structure of traditional audio frequency and video TS bag, specifically be, tradition audio frequency and video TS bag is that audio frequency and video Basic Flow (ES) is packaged into Packet Elementary Stream (PES), and Packet Elementary Stream (PES) is multiplexed transport stream (TS) bag that is packaged into again; And the audio frequency and video Basic Flow (ES) in the audio frequency and video sheet section business inserted VOD protocol specification data structure six defined audio frequency and video fragments and inserts information (av_segment_insert_info ()) when being packaged into Packet Elementary Stream (PES) before ES.The audio frequency and video fragment of inserting is inserted in the information (av_segment_inser_info ()) VOD service lists identifier (vod_service_list_id), VOD task identifier (vod_service_id) and segment identifiers (segment_id) can VOD business of unique identification or VOD traffic segment, thereby can audio frequency and video sheet section business is unique related with a VOD business or VOD traffic segment.

Based on above-mentioned logical relation and organizational form, the embodiment of the invention can issue VOD service lists and satellite information thereof in transport stream (TS).Wherein, described VOD service lists comprises following key message: VOD service lists identifier, VOD server ip address, VOD server ip address for subsequent use, the professional number of VOD, VOD task identifier, VOD type of service, VOD service priority, VOD Business Name byte; Wherein, described VOD type of service can 15 kinds of different types of service, specifically referring to Fig. 4; Wherein, described VOD service priority can identify 256(2 ⁸) plant different service priority.

Wherein, described VOD service lists satellite information comprises following key message: VOD service lists identifier, VOD task identifier, descriptor, VOD business information type; Wherein, described descriptor can be that VOD protocol specification data structure four defined prices also can be other descriptors with reference to descriptor (price_reference_descriptor ()); Wherein, described VOD business information type is divided into again textual description, picture description, performer's tabulation, four kinds of different types of audio frequency and video fragment, and various type has again different data structures and critical field; Wherein, described textual description comprises following critical field: the duration of segmentation marker, business or segmentation, the text character that provides textual description, segmentation number, segment identifiers; Wherein, described picture is described and comprised following critical field: image data segment table identifier, picture identification symbol, picture format, picture size, piece number are used for providing the overall control information with the picture of VOD traffic aided; Wherein, described performer's tabulation comprises following critical field: performer's number, performer's title byte, actor information byte; Wherein, described audio frequency and video fragment comprises following critical field: transport stream identification symbol, original network identification symbol, task identifier are used for an audio frequency and video sheet of unique identification section business.

Wherein, described price provides the price of VOD business with reference to relevant information with reference to descriptor (price_reference_descriptor ()), comprise following key message: way of paying, the value different according to pay_mode, corresponding different way of paying and critical field; Wherein, described way of paying comprise impromptu pay-per-view (IPPV), impromptu (IPPT), the PPC Pay Per Channel (PPC) of on time paying; Wherein, described impromptu pay-per-view (IPPV) provides critical field and sees that whenever price once counts; Wherein, described impromptu on time pay (IPPT) price of providing the critical field per minute is counted; Wherein, described PPC Pay Per Channel (PPC) price that provides each channel of critical field is counted.

Wherein, described picture is described and is used for describing an image data section (picture_data_section ()); Wherein, described image data section (picture_data_section ()) is used for providing the image data with the VOD traffic aided, comprises following key message: the data byte of table identifier, picture identification symbol, last picture identification symbol, picture reality.

Wherein, when described audio frequency and video sheet section business refers to that audio frequency and video fragment Basic Flow (ES) is packaged into transport stream (TS), before ES, inserted VOD protocol specification data structure six defined audio frequency and video fragments and inserted information (av_segment_insert_info ()).Wherein, described audio frequency and video fragment insert information (av_segment_insert_info ()) provide audio frequency and video sheet section business and VOD business or VOD traffic segment unique related information, comprise critical field: VOD service lists identifier, VOD task identifier, segment identifiers, by above 3 signs that audio frequency and video sheet section business is unique related with VOD business or VOD traffic segment.

Typically, in a real network, to issue VOD service lists business and satellite information thereof in a transport stream (TS) the inside, add VOD protocol specification data structure one defined linkage descriptor (linkage_descriptor ()) in the NIT of other transport stream (TS) or BAT, link is professional to described VOD service lists.Wherein, described VOD service lists business and satellite information thereof repeat to broadcast in transport stream (TS) with the form of data carousel.

Described set-top box is bi-directional set-top box, has the network retransmission function, compares with general bi-directional set-top box to have some special functional modules.Concrete structure as shown in Figure 9.

Described set-top box S901 is comprised of three modules, specifically comprises: set-top box general module S904, request program database S903, search engine S902.

Wherein, described set-top box general module S904 refers to the module that general bi-directional set-top box has, but integrating browsing device not.

Wherein, described request program database S903 is used for storage VOD service lists and satellite information thereof; Wherein, described VOD service lists and satellite information thereof comprise: VOD service lists, VOD price for traffic information, VOD business or the brief introduction of VOD traffic segment, picture description, performer's tabulation and performer's brief introduction, audio frequency and video fragment; Wherein, described VOD service lists and satellite information thereof are according to fixing data structure storage, and concrete data structure is referring to VOD protocol specification data structure; Wherein, described VOD service lists and satellite information thereof are stored in memory device; Wherein, described memory device is the built-in memory device of set-top box or external storage equipment.

Wherein, described search engine S902 is for the programme information of wanting in request program database S903 search subscriber to watch, according to given VOD service lists and the satellite information thereof of data structure that VOD protocol specification data structure provides, the user can carry out at the request program search interface search of following critical field: VOD Business Name, performer's title, VOD type of service.

Set-top box in the embodiment of the invention is described below resolves the flow process of VOD service lists and satellite information thereof.

In the logical relation and organizational form of VOD protocol specification data structure hereinbefore, can obtain a kind of transport stream (TS), this transport stream (TS) has comprised VOD service lists and satellite information thereof.

Set-top box with structure shown in Figure 9 is resolved VOD service lists and satellite information thereof, can form a request program database at the set-top box end.The flow process of set-top box parsing VOD service lists and satellite information thereof as shown in figure 10.

Step S1001: linkage_type is the linkage descriptor of 0xFE among monitoring NIT or the BAT, resolves each field of this descriptor, obtains the overall information of VOD service lists and satellite information thereof, starts the reception of VOD tabulation and satellite information thereof.

Set-top box resolves the VOD service lists and the satellite information suggestion is finished in the process of program searching.

In the process of program searching, link type (linkage_type) is the linkage descriptor (linkage_descriptor ()) of 0xFE among set-top box monitoring NIT or the BAT, and according to VOD protocol specification data structure one: the syntactic structure of linkage descriptor (linkage_descriptor ()) is resolved each field of this descriptor; Wherein, described linkage descriptor (linkage_descriptor ()) link is professional to a VOD service lists; Wherein, described VOD service lists business is by transport stream identification symbol (transport_stream_id), original network identification symbol (original_network_id) and three critical field unique identifications of task identifier (service_id) in the linkage descriptor; Wherein, in the physics frequency at the professional place of described VOD service lists and the linkage descriptor transport stream identification symbol (transport_stream_id) and original network identification to accord with (original_network_id) institute uniquely identified transport stream (TS) corresponding one by one; Wherein, the physics frequency at the professional place of described VOD service lists accords with (original_network_id) institute uniquely identified transport stream (TS) unique the providing of transmission system descriptor corresponding to network information table (NIT) by transport stream identification symbol (transport_stream_id) and original network identification in the linkage descriptor; Wherein, described transmission system descriptor has specific definition in the SI standard; Wherein, described transmission system descriptor can be line transmission system descriptor (cable_delivery_system_descriptor ()), sts satellite transmission system descriptor (satellite_delivery_system_descriptor ()), ground transmission system descriptor (terrestrial_delivery_system_descriptor ()).

The set-top box end obtains baseband transmission stream (TS) according to the parameter information frequency lockings such as frequency that provide in the described transmission system descriptor; Obtain baseband transmission stream (TS) afterwards, the set-top box end begins to carry out demultiplexing to be processed.Wherein, task identifier in the described linkage descriptor (service_id) can business of unique identification in the baseband transmission that obtains stream (TS), and this business is that the VOD service lists is professional; Described set-top box is at first resolved Program Association Table (PAT), task identifier in the described linkage descriptor (service_id) is unique related with the program number (Program_number) in the described Program Association Table (PAT), can obtain thus the PID(PMT_PID of VOD service lists business program mapping table); Resolve the Program Map Table (PMT) that described PMT_PID identifies, can obtain the PID of the Basic Flow (ES) that VOD service lists business comprises, and can obtain the stream type (stream_type) of described Basic Flow (ES); Wherein, the stream type (stream_type) of described Basic Flow (ES) and Basic Flow (ES) comprising: VOD service lists section (vod_service_list_section ()), and stream type is 0xFF; VOD business information section (vod_service_info_section ()), stream type is 0xFE; Image data section (picture_data_section ()), stream type is 0xFD; Wherein, the PID of described Basic Flow (ES) comprising: VOD service lists PID(vod_service_list_PID), VOD business information PID(vod_service_info_PID), image data PID(picture_data_PID); The sign of wherein, described VOD service lists PID(vod_service_list_PID) wrapping for the transport stream (TS) that provides VOD service lists section (vod_service_list_section ()) place; The sign of wherein, described VOD business information PID(vod_service_info_PID) wrapping for the transport stream (TS) that provides VOD business information section (vod_service_info_section ()) place; Wherein, described image data PID(picture_data_PID) be used for providing the sign that image data section (picture_data_section ()) place transport stream (TS) is wrapped.

Resolve described linkage descriptor (linkage_descriptor ()) and can also obtain the overall information of VOD service lists and satellite information thereof, comprising: VOD service lists version number (vod_list_version_number), compulsory mark (force_flag), VOD service lists segment table identifier (vod_service_list_section_table_id), segment type 1(section_type_1), the initial table identifier of VOD business information section (vod_service_info_section_start_table_id), VOD business information section sign-off table identifier (vod_service_info_section_end_table_id), segment type 2(section_type_2), the initial table identifier of image data section (picture_data_section_start_table_id), image data section sign-off table identifier (picture_data_section_end_table_id), segment type 3(section_type_3), VOD service lists number (vod_service_list_number), VOD service lists sign (vod_service_list_id), sub-version number (sub_version_number); Wherein, described VOD service lists version number is used for providing the total version number of VOD service lists, has when renewal to use in VOD service lists data; Wherein, described compulsory mark is a flag bit, be used for pointing out when VOD service lists version number changes, whether to force to upgrade, represent to force to upgrade for ' 1 ' time, upgrade when renewal or user enter the program request interface when representing that set-top box starts for ' 0 ' time next time; Wherein, described VOD service lists segment table identifier is used for the affiliated table of sign VOD service lists section; Wherein, described segment type 1 is used for providing the data type under the VOD service lists section, and is corresponding with the stream_type of VOD service lists section Basic Flow described in the professional PMT of VOD service lists, is fixed as 0xFF; Wherein, the described initial table identifier of VOD business information section and VOD business information section sign-off table identifier are respectively applied to provide initial table identifier and the sign-off table identifier of VOD business information section; Wherein, described segment type 2 is used for providing the data type under the VOD business information section, and is corresponding with the stream type of VOD business information section Basic Flow described in the professional PMT of VOD service lists, is fixed as 0xFE; Wherein, the initial table identifier of described image data section and image data section sign-off table identifier are used for providing initial table identifier and the sign-off table identifier of image data section; Wherein, described segment type 3 is used for providing the data type under the image data section, and is corresponding with the stream_type of image data section Basic Flow described in the professional PMT of VOD service lists, is fixed as 0xFD; Wherein, described VOD service lists number is used for providing the number of VOD service lists, and is corresponding with the VOD server, the corresponding VOD service lists of VOD server; Wherein, described VOD service lists identifier is used for VOD service lists of unique identification in VOD service lists business; Wherein, described sub-version number is used for providing the version number of the VOD service lists that VOD service lists identifier identifies.

Based on above parsing, obtained the overall information of VOD service lists and satellite information thereof; And obtained the pid information of VOD service lists, VOD business information, image data Basic Flow (ES), for follow-up reception storage VOD service lists and satellite information thereof provide relevant control information.

Above all information of obtaining are stored into the request program database of set-top box end, for the reception of VOD service lists and satellite information thereof provides relevant control information.

Step S1002: resolve and receive VOD service lists section, obtain VOD service lists and VOD server ip address relevant information.

The VOD service lists PID that obtains according to step S1001 can obtain VOD service lists segment data; Wherein, the syntactic structure of described VOD service lists section and semantic by VOD protocol specification data structure two: VOD service lists section (vod_service_list_section ()) provides, resolve transport stream (TS) bag that VOD service lists PID identifies according to this syntactic structure, can obtain complete VOD service lists.Wherein, described VOD service lists section (vod_service_list_section ()) has following critical field: table identifier (table_id), segment length (section_length), version number (version_number), VOD service lists identifier (vod_service_list_id), sub-version number (sub_version_number), last VOD service lists identifier (last_vod_service_list_id), segment number (section_number), last segment number (last_section_number), VOD server ip address (vod_server_ip), VOD server ip address for subsequent use (backup_vod_server_ip), the professional number (vod_service_number) of VOD, VOD task identifier (vod_service_id), VOD type of service (vod_service_type), VOD service priority (vod_service_priority), ISO 639-2 language codes (ISO 639-2_language_code), VOD Business Name length (vod_service_name_length), VOD Business Name byte (vod_service_name_byte), CRC32 verification (CRC32).

The semanteme of the critical field that wherein, comprises in the described VOD service lists section (vod_service_list_section ()) is specifically referring to VOD protocol specification data structure two: the semantic description of each field in the VOD service lists section (vod_service_list_section ()).

Wherein, described set-top box with structure shown in Figure 9 is according to VOD protocol specification data structure two: the defined syntactic structure of VOD service lists section (vod_service_list_section ()) receives also storage VOD service lists; Wherein, described VOD service lists is stored into the request program database of described set-top box end; Wherein, described VOD service lists is stored as unit take the VOD service lists identifier uniquely identified VOD of institute service lists in a VOD service lists business; Wherein, described VOD service lists is encapsulated in the VOD service lists section; Wherein, described VOD service lists section identifies by table identifier; Wherein, described table identifier and VOD protocol specification data structure one: VOD service lists segment table identifier (vod_service_list_section_table_id) field corresponding (this field is obtained by step S1001) in the linkage descriptor (linkage_descriptor ()) is fixed as 0x80; Wherein, described VOD service lists identifier and VOD protocol specification data structure one: VOD service lists identifier (vod_service_list_id) corresponding (this field is obtained by step S1001) in the linkage descriptor (linkage_descriptor ()); Wherein, described VOD service lists comprise the section number provided by last segment number field; Wherein, the number of described VOD service lists is provided by last VOD service lists identifier field, and VOD protocol specification data structure one: VOD service lists number (vod_service_list_number) field corresponding (this field is obtained by step S1001) in the linkage descriptor (linkage_descriptor ()); Wherein, version number in the described VOD service lists section is used for providing total version number of VOD service lists, when upgrading, VOD service lists and satellite information thereof use and VOD protocol specification data structure one: VOD service lists version number (vod_list_version_number) field corresponding (this field is obtained by step S1001) in the linkage descriptor (linkage_descriptor ()); Wherein, sub-version number in the described VOD service lists section is used for providing the sub-version number of VOD service lists, when upgrading, VOD service lists and satellite information thereof use and VOD protocol specification data structure one: sub-version number (sub_version_number) field corresponding (this field is obtained by step S1001) in the linkage descriptor (linkage_descriptor ()); Wherein, the VOD server ip address in the described VOD service lists section and VOD server ip address for subsequent use are respectively applied to identify a VOD server and a VOD server for subsequent use; Wherein, described VOD server for subsequent use is a backup of described VOD server, and the business tine on the VOD server is in full accord; Wherein, each VOD server and VOD server correspondence for subsequent use a VOD service lists, namely with a VOD service lists business in the VOD service lists section (vod_service_list_section ()) the uniquely identified VOD of vod_service_list_id institute service lists corresponding one by one; Wherein, described vod_service_list_id in a VOD service lists business in the uniquely identified VOD of the institute service lists number of VOD business provided by VOD service digital section; Wherein, the VOD task identifier can VOD business of unique identification in the uniquely identified VOD of the institute service lists in a VOD service lists business for described vod_service_list_id; Wherein, the type of service of the VOD business that described VOD task identifier identifies is provided by the VOD business type field, type of service form as shown in Figure 4; Wherein, the priority of the VOD business that described VOD task identifier identifies is provided by the VOD traffic priority field, and the VOD Business Name that priority is high can preferentially show at the program request interface; Wherein, the Business Name of the VOD business that identifies of described VOD task identifier is provided by VOD Business Name byte field; Wherein, the language that adopts of described VOD Business Name byte is provided by ISO 639-2 language codes field; Wherein, the length of described VOD Business Name byte is given by VOD Business Name length field.

Wherein, the correctness of described VOD service lists section (vod_service_list_section ()) is guaranteed by the CRC32 check field, does not pass through when the CRC32 verification, abandons the data segment of current reception, and again receives this section.

Control the reception of VOD service lists according to the control information that step S1001 obtains, and will receive the request program database that complete VOD service lists is stored into the set-top box end.

Step S1003: resolve and receive VOD business information section, obtain professional way of paying, price, the brief description of business, the information such as performer's tabulation and performer's introduction, and obtain and the picture of VOD traffic aided and control, the related information of audio frequency and video fragment.

The VOD business information PID that obtains according to step S1001 can obtain VOD business information segment data; Wherein, the syntactic structure of described VOD business information section and semantic by VOD protocol specification data structure three: VOD business information section (vod_service_info_section ()) provides, resolve transport stream (TS) bag that VOD business information PID identifies according to this syntactic structure, can obtain the relevant information of VOD business.

Wherein, described VOD business information section (vod_service_info_section ()) comprises following critical field: table identifier (table_id), segment length (section_length), version number (version_number), sublist identifier (sub_table_id), sub-version number (sub_version_number), last sublist identifier (last_sub_table_id), VOD service lists identifier (vod_service_list_id), segment number (section_number), last segment number (last_section_number), VOD task identifier (vod_service_id), VOD traffic descriptor length (vod_service_descriptor_length), descriptor (descriptor ()), VOD business information type (vod_service_info_type), segmentation marker (segment_flag), duration (duration), ISO 639-2 language codes (ISO 639-2_language_code), VOD business information length (vod_service_info_length), text character (text_char), segmentation number (segment_number), segment identifiers (segment_id), segment information length (segment_info_length), image data segment table identifier (picture_data_section_table_id), picture identification symbol (picture_id), picture format (picture_format), picture size (picture_size), piece number (block_number), performer's number (performer_number), performer's title length (performer_name_length), performer's title byte (performer_name_byte), actor information length (performer_info_length), actor information byte (performer_info_byte), transport stream identification symbol (transport_stream_id), original network identification symbol (original_network_id), task identifier (service_id), CRC32 verification (CRC32).

The semanteme of the critical field that wherein, comprises in the described VOD business information section (vod_service_info_section ()) is referring to VOD protocol specification data structure three: the semantic description of each field in the VOD business information section (vod_service_info_section ()).

Wherein, described set-top box with structure shown in Figure 9 is according to VOD protocol specification data structure three: the defined syntactic structure of VOD business information section (vod_service_info_section ()) receives also storage VOD service related information; Wherein, described VOD service related information is stored into the request program database of set-top box.

Wherein, described table identifier is used for the table under the sign VOD business information section, and VOD protocol specification data structure one: the initial table identifier of VOD business information section (vod_service_info_section_start_table_id) and VOD business information section sign-off table identifier (vod_service_info_section_end_table_id) field corresponding (these two fields are by step S1001 acquisition) in the linkage descriptor (linkage_descriptor ()); Wherein, described table identifier and sublist of sublist identifier field unique identification; Wherein, the number of sublist is given by last sublist identifier field in the table that identifies of described table identifier; Wherein, the version that described table identifier identifies is given by version number field, uses when VOD service lists and satellite information renewal thereof; Wherein, the version of described table identifier and sublist identifier institute uniquely identified sublist is given by the sub-version number field, uses when VOD service lists and satellite information renewal thereof; Wherein, described sublist comprises a plurality of sections, and present segment is by the segment number field identification, and the number of the section that comprises is given by last segment number field; Wherein, the length of the present segment that identifies of described segment number field is given by segment length field.

In specific implementation process, described VOD service related information is by VOD service lists identifier and the VOD task identifier is unique and a VOD traffic aided connection; Wherein, described VOD service lists identifier can be in a VOD service lists business VOD service lists of unique identification, and VOD protocol specification data structure two: VOD service lists identifier (vod_service_list_id) field corresponding (this field is obtained by step S1002) in the VOD service lists section (vod_service_list_section ()); Wherein, described VOD task identifier is VOD business of unique identification in the VOD service lists that VOD service lists identifier identifies, and VOD protocol specification data structure two: VOD task identifier (vod_service_id) field corresponding (this field is obtained by step S1002) in the VOD service lists section (vod_service_list_section ()).

In specific implementation process, described VOD service related information can be descriptor or different VOD business information types; Wherein, described descriptor be used for to be described the satellite information of VOD business, specifically can be VOD protocol specification data structure four defined prices with reference to descriptor (price_reference_descriptor ()), also can be other descriptors; Wherein, the length of described descriptor is given by VOD traffic descriptor length field; Wherein, described different VOD business information type is given by VOD business information type field, and the value that this field is different can identify different VOD business information types; Wherein, described VOD business information type can be that textual description, picture are described, the performer tabulates, four kinds of different types of audio frequency and video fragment, and various type has again different data structures and critical field.

In specific implementation process, described textual description provides following critical field: segmentation marker (segment_flag), duration (duration), ISO 639-2 language codes (ISO 639-2_language_code), VOD business information length (vod_service_info_length), text character (text_char), segmentation number (segment_number), segment identifiers (segment_id), segment information length (segment_info_length); Wherein, described segmentation marker field is used for providing the whether segmentation of VOD service lists identifier and the uniquely identified VOD of VOD task identifier institute business; Wherein, described duration field is used for providing the duration of VOD business or VOD traffic segment; Wherein, described text character field is used for providing the Short Description of VOD business or VOD traffic segment; Wherein, the language that adopts of the Short Description of described VOD business or VOD traffic segment is provided by ISO 639-2 language codes field; Wherein, the length of the professional Short Description of described VOD is given by VOD business information length field; Wherein, the length of described VOD traffic segment Short Description is given by the segment information length field; Wherein, the number of described VOD traffic segment is given by the segmentation number field; Wherein, described VOD traffic segment is by VOD service lists identifier, VOD task identifier and segment identifiers field unique identification.

In specific implementation process, described picture is described and is provided following critical field: image data segment table identifier (picture_data_section_table_id), picture identification symbol (picture_id), picture format (picture_format), picture size (picture_size), piece number (block_number); Wherein, described image data segment table identifier is used for the affiliated table of image data section at the picture place of sign and VOD traffic aided; Wherein, described image data section meets VOD protocol specification data structure five: the syntactic structure of image data section (picture_data_section ()); Wherein, described picture identification symbol is used for the picture of table unique identification under the image data section that image data segment table identifier identifies; Wherein, the form of described picture is given by the picture format field, and the value that this field is different provides different picture formats, can be I frame, JPG, GIF, BMP, different picture formats has different data structures, and the set-top box end is accordingly to the image data demonstration of decoding; Wherein, the data volume of described picture is given by the picture size field; Wherein, described picture is given by the piece number field at the number in image data section stage casing.

In specific implementation process, described performer's tabulation provides following critical field: performer's number (performer_number), ISO 639-2 language codes (ISO 639-2_language_code), performer's title length (performer_name_length), performer's title byte (performer_name_byte), actor information length (performer_info_length), actor information byte (performer_info_byte); Wherein, described performer's number field provides the number of VOD service lists identifier and the professional featured performer of the uniquely identified VOD of VOD task identifier institute; Wherein, described performer's title byte field is used for providing performer's title; Wherein, described performer's title length is given by performer's title length field; Wherein, described actor information byte field is used for providing the performer in the information brief introduction of VOD business figure; Wherein, the length of described information brief introduction is given by the actor information length field; Wherein, the language that adopts of described performer's title and information brief introduction is given by ISO 639-2 language codes.

In specific implementation process, described audio frequency and video fragment provides following critical field: transport stream identification symbol (transport_stream_id), original network identification symbol (original_network_id), task identifier (service_id), the effect of these three fields is equivalent to a linkage descriptor, and link is to an audio frequency and video sheet section business; Wherein, described transport stream identification symbol and original network identification symbol transport stream of unique identification (TS) in network; Wherein, the physics frequency point information of described transport stream (TS) is described in the transmission system descriptor of network information table (NIT) the second circulation.

In specific implementation process, described price with reference to the syntactic structure of descriptor by VOD protocol specification data structure four: price is given with reference to descriptor (price_reference_descriptor ()), and this descriptor provides following critical field: descriptor tag (descriptor_tag), descriptor length (descriptor_length), way of paying (pay_mode), whenever see once price count (price_point_per_view), the price of per minute count (price_point_per_minute), the price of each channel count (price_point_per_channel); Wherein, described descriptor tag is fixed as 0xFE at this, and identifying this descriptor is that price is with reference to descriptor; Wherein, way of paying and critical field that the value that described way of paying field is different is corresponding different; Wherein, described way of paying comprise impromptu pay-per-view (IPPV), impromptu (IPPT), the PPC Pay Per Channel (PPC) of on time paying; Wherein, described impromptu pay-per-view provides the price of whenever seeing once and counts; Wherein, the described impromptu price that provides per minute of on time paying is counted; Wherein, the PPC Pay Per Channel price that provides each channel is counted.Wherein, the length of described way of paying and critical field is given by the descriptor length field; Wherein, the described price corresponding price of counting is defined by operator.

In specific implementation process, the correctness of described VOD business information section (vod_service_info_section ()) is guaranteed by the CRC32 check field, does not pass through when the CRC32 verification, abandons the data segment of current reception, and again receives this section.

Control the reception of VOD business information section according to the relevant information that step S1001 and S1002 obtain, and will receive the request program database that complete VOD business information section is stored into the set-top box end.

Step S1004: resolve and reception image data section, obtain the image data with the VOD traffic aided.

The relevant information control of obtaining according to step S1001, S1002 and S1003 receives and the image data of VOD traffic aided.

The image data PID that obtains according to step S1001 can obtain image data; Wherein, described image data is encapsulated in the VOD protocol specification data structure five defined image data sections (picture_data_section ()), resolve transport stream (TS) bag that image data PID identifies according to the syntactic structure of described image data section, can obtain the image data with the VOD traffic aided.

Wherein, described image data section (picture_data_section ()) comprises following critical field: table identifier (table_id), segment length (section_length), version number (version_number), picture identification symbol (picture_id), sub-version number (sub_version_number), last picture identification symbol (last_picture_id), segment number (section_number), last segment number (last_section_number), data byte (data_byte), CRC32 verification (CRC32).

In specific implementation process, the semanteme of the critical field that comprises in the described image data section (picture_data_section ()) is referring to VOD protocol specification data structure five: the semantic description of each field in the image data section (picture_data_section ()).

In specific implementation process, described set-top box with structure shown in Figure 9 is according to VOD protocol specification data structure five: the defined syntactic structure of image data section (picture_data_section ()) receives and store picture data; Wherein, described image data is stored into the request program database of set-top box.

In specific implementation process, described table identifier is used for the table under the sign picture data segment, with VOD protocol specification data structure one: the initial table identifier of image data section (picture_data_section_start_table_id) and image data section sign-off table identifier (picture_data_section_start_table_id) field corresponding (these two fields are obtained by step S1001) in the linkage descriptor (linkage_descriptor ()), and with VOD protocol specification data structure three: image data segment table identifier (picture_data_section_table_id) field corresponding (this field is by step S1003 acquisition) in the VOD business information section (vod_service_info_section ()); Wherein, described picture identification symbol field and table identifier be picture of unique identification together, and VOD protocol specification data structure three: picture identification symbol (picture_id) field corresponding (this field is obtained by step S1003) in the VOD business information section (vod_service_info_section ()); Wherein, the hop count order that comprises of described picture is given by last segment number field; Wherein, described last segment number and VOD protocol specification data structure: piece number (block_number) field corresponding (this field is obtained by step S1003) in the VOD business information section (vod_service_info_section ()); Wherein, described image data present segment is by the segment number field identification; Wherein, the length of described image data present segment is given by segment length field; Wherein, the version of the table under the described image data section is given by version number field, uses when VOD service lists and satellite information renewal thereof; Wherein, the version of described picture is given by sub-version number, uses when VOD service lists and satellite information renewal thereof; Wherein, the number of pictures that comprises in the image data segment table that described table identifier identifies is given by last picture identification symbol field; Wherein, the real data of described picture is given by the data byte field.

In specific implementation process, the correctness of described image data section (picture_data_section ()) is guaranteed by the CRC32 check field, does not pass through when the CRC32 verification, abandons the data segment of current reception, and again receives this section.

Control the reception of picture data segment according to the relevant information that step S1001, S1002 and S1003 obtain, and will receive the request program database that complete image data is stored into the set-top box end.

Step S1005: receive and store the associated audio frequency and video sheet section business of relevant information in the VOD business information section.

The relevant information control of obtaining according to step step S1001, S1002 and S1003 receives relevant audio frequency and video fragment data with VOD business or VOD traffic segment.

In specific implementation process, the critical field that audio frequency and video fragment that described step S1003 obtains is described can an audio frequency and video sheet of unique identification section business; Wherein, the critical field of described audio frequency and video fragment description comprises: transport stream identification symbol (transport_stream_id), original network identification symbol (original_network_id), task identifier (service_id); Wherein, the effect of the critical field that described audio frequency and video fragment is described is equal to a linkage descriptor, and link is to an audio frequency and video sheet section business; Wherein, described transport stream identification symbol and original network identification symbol transport stream of unique identification (TS) in network; Wherein, the physics frequency point information of described transport stream (TS) is described in the transmission system descriptor of network information table (NIT) the second circulation.

In specific implementation process, described set-top box with structure shown in Figure 9 is carried out frequency locking and demodulation according to the physics frequency point information of obtaining, and obtains baseband transmission stream (TS); Wherein, the critical field task identifier during audio frequency and video fragment that described step S1003 obtains is described can business of unique identification in the described baseband transmission stream (TS) that obtains, and this business is audio frequency and video sheet section business; Wherein, the PID of the PMT of described audio frequency and video sheet section business is described by the Program Association Table (PAT) that described baseband transmission flows in (TS); Wherein, described Program Association Table (PAT) provides following key message: the PID(PMT_PID of program number (Program_number), PMT); Wherein, described program number is unique related with the critical field task identifier during the audio frequency and video fragment that described step S1003 obtains is described; Wherein, described PMT_PID is used for transport stream (TS) bag at sign audio frequency and video fragment business program mapping tables (PMT) place; Wherein, described Program Map Table (PMT) is used for providing stream type and the pid information thereof of audio frequency and video sheet section business audio frequency and video, specifically comprises critical field: video segment stream type (stream_type=0xF0), video segment PID(video_segment_PID), audio fragment stream type (stream_type=0xF1), audio fragment PID(audio_segment_PID); Wherein, described video segment PID is for the sign of transport stream (TS) bag that provides video-frequency basic flow (ES) place; Wherein, described audio fragment PID is for the sign of transport stream (TS) bag that provides audio frequency Basic Flow (ES) place; Wherein, there are some differences in the data structure of looking the audio transport stream packet bag that transport stream (TS) bag of looking audio frequency Basic Flow (ES) place that described video segment PID and audio fragment PID identify and tradition meet MPEG2 system layer standard; Wherein, described difference is: traditional audio frequency and video TS bag is that audio frequency and video Basic Flow (ES) is packaged into Packet Elementary Stream (PES), Packet Elementary Stream (PES) is multiplexed transport stream (TS) bag that is packaged into again, and the audio frequency and video Basic Flow (ES) in the audio frequency and video sheet section business is when being packaged into Packet Elementary Stream (PES), before ES, insert VOD protocol specification data structure six defined audio frequency and video fragments and insert information (av_segment_insert_info ()), again with multiplexed transport stream (TS) bag that is packaged into of Packet Elementary Stream (PES); Wherein, described audio frequency and video fragment insertion information (av_segment_insert_info ()) comprises following critical field: VOD service lists identifier (vod_service_list_id), VOD task identifier (vod_service_id), segment identifiers (segment_id); Wherein, described VOD service lists identifier VOD service lists of unique identification in a VOD service lists business; Wherein, described VOD task identifier VOD business of unique identification in the VOD service lists that VOD service lists identifier identifies; Wherein, described segment identifiers is VOD traffic segment of unique identification in VOD service lists identifier and the uniquely identified VOD of VOD task identifier institute business, when in VOD protocol specification data structure three: when being ' 0 ', this field is invalid for segmentation marker field in the VOD business information section (vod_service_info_section ()) (this field is obtained by step S403); Wherein, described VOD service lists identifier, VOD task identifier and segment identifiers can be in a VOD service lists business VOD business of unique identification or VOD traffic segment, thereby can audio frequency and video sheet section business is unique related with a VOD business or VOD traffic segment; Wherein, described VOD service lists identifier, VOD task identifier and segment identifiers are as audio frequency and video sheet section business and VOD business or the unique related label of VOD traffic segment (tag); Wherein, the audio frequency and video fragment that identified take described label (tag) of described audio frequency and video sheet section business is in unit is stored into described request program database with structure set-top box shown in Figure 9.

The set-top box end that the embodiment of the invention is described below to be provided upgrades the flow process of VOD service lists and satellite information thereof.

When the VOD of front end business had renewal, corresponding VOD service lists and satellite information thereof also had renewal; Concrete, the data of packaging V OD service lists and satellite information thereof have corresponding renewal in the transport stream (TS) that broadcasting issues, and namely the data content in VOD protocol specification data structure one to the six described data structure has corresponding renewal; Wherein, described renewal identifies by the variation of version number, when the VOD service lists has renewal, described VOD protocol specification data structure one: VOD service lists version number (vod_list_version_number) field can add ' 1 ' on original basis in the linkage descriptor (linkage_descriptor ()), and, described VOD protocol specification data structure one: when the VOD service lists that VOD service lists identifier (vod_service_list_id) field identifies in the linkage descriptor (linkage_descriptor ()) has renewal, its corresponding sub-version number (sub_version_number) field adds ' 1 ' on original basis, for not having the professional VOD service lists of upgrading of VOD, its corresponding sub-version number (sub_version_number) field does not change; Corresponding, the renewal of the VOD service lists that VOD service lists identifier identifies, version number's (version_number) field in the VOD service lists section (vod_service_list_section ()) at its place and and sub-version number (sub_version_number) field corresponding to this VOD service lists also corresponding variation will occur; Wherein, with VOD business information section (vod_service_info_section ()) that the described VOD service lists that changes is associated in version number (version_number) and sub-version number (sub_version_number) field also corresponding variation can occur; Wherein, corresponding variation also can occur in version number (version_number) and sub-version number (sub_version_number) field in the image data section (picture_data_section ()) that is associated with the described VOD service lists that changes.

For the renewal of front end VOD business, the set-top box end has corresponding renewal handling process; Wherein, the flow process of described set-top box end renewal VOD service lists and satellite information thereof specifically as shown in figure 11.

Step S1101: linkage_type is the linkage descriptor of 0xFE among monitoring NIT or the BAT, obtains VOD service lists version number (vod_list_version_number) and compulsory mark (force_flag); And obtain the VOD service lists version number (vod_list_version_number) that is stored in the set-top box request program database.

Set-top box monitors constantly that linkage_type is the linkage descriptor of 0xFE among NIT or the BAT, obtains VOD service lists version number (vod_list_version_number) and compulsory mark (force_flag) field in the described linkage descriptor; And obtain and be stored in the set-top box end points and broadcast VOD service lists version number (vod_list_version_number) in the program database.

VOD service lists version number and set-top box end points are broadcast the basis for estimation whether the VOD service lists version number in the program database will upgrade as VOD service lists and satellite information thereof among the step S1102 in the linkage descriptor that described set-top box is obtained.

Step S1102:VOD service lists version number relatively.

The relevant information that described set-top box with structure shown in Figure 9 is obtained according to step S1101 judges whether to carry out the mode of renewal and the renewal of VOD service lists; Wherein, the relevant information obtained of described step S1101 comprises: link type is VOD service lists version number and compulsory mark field in the linkage descriptor of 0xFE, be stored in the set-top box end points broadcasts VOD service lists version number field in the program database.

Wherein, described VOD service lists version number refers to that relatively from link type be the VOD service lists version number field obtained the linkage descriptor of 0xFE and be stored in the VOD service lists version number field that the set-top box end points broadcasts in the program database and compare; Wherein, the described VOD service lists result relatively of version number has two kinds, and a kind of is equal (version number is constant), and a kind of is not wait (version number's change).

Wherein, described set-top box with structure shown in Figure 9 according to VOD service lists version number relatively the result and judged whether to carry out the mode of renewal and the renewal of VOD service lists and satellite information thereof by the compulsory mark field information that step S1101 obtains; Wherein, described different update mode correspondence different treatment steps.

Wherein, described VOD service lists version number's comparative result equal (version number is constant) does not carry out the renewal of VOD service lists and satellite information thereof, turns to step S1105;

Wherein, described VOD service lists version number comparative result does not wait (version number's change), and the compulsory mark field is ' 0 ', turns to step S1103;

Wherein, described VOD service lists version number comparative result does not wait (version number's change), and the compulsory mark field is ' 1 ', turns to step S1104.

Step S1103: set-top box starts next time or the user enters the program request interface.

In step S1102, comparative result does not wait (version number's change) when described VOD service lists version number, and the compulsory mark field will be carried out the renewal of VOD service lists and satellite information thereof when being ' 0 '; Wherein, described renewal is not to upgrade immediately, but set-top box when starting next time or the user upgrade when entering the program request interface; Wherein, the content of described renewal and method are referring to step S1104.

Step S1104: start and upgrade, upgrade VOD service lists and satellite information thereof that sub-version number changes.

When the VOD service lists version number comparative result described in the step S1102 does not wait (version number's change), need to carry out the renewal of VOD service lists and satellite information thereof.

Wherein, described renewal is that the VOD service lists that only changes for sub-version number is carried out, and the VOD service lists that sub-version number does not change is not upgraded; Wherein, described VOD service lists refers to by the VOD service lists identifier uniquely identified VOD of institute service lists in a VOD service lists business; Wherein, described sub-version number refers to the version number of the VOD service lists identifier uniquely identified VOD of institute service lists; Wherein, described renewal refers to that VOD service lists and satellite information thereof that sub-version number changes need again to receive, and be stored into the request program database of set-top box end, replace and have VOD service lists and the satellite information thereof that same VOD service lists identifier identifies; Wherein, described VOD service lists and satellite information thereof refer to the VOD service lists that the VOD task identifier identifies and the satellite information that is associated with this VOD service lists; Wherein, described satellite information refers to the identification information of VOD service related information that VOD business information section provides, VOD price for traffic relevant information that price provides with reference to descriptor, image data information that the image data section provides, audio frequency and video sheet section business that audio frequency and video fragment insertion information provides.

Wherein, the acquisition of described VOD service lists and satellite information thereof is referring to Figure 10 and step explanation thereof.

Step S1105: upgrade and finish.

When VOD service lists version number comparative result among the step S1102 equates (version number is constant), do not carry out the renewal of VOD service lists and satellite information thereof, turn to this step, upgrade and finish;

The VOD service lists that sub-version number changes in step S1104 and satellite information thereof are upgraded and are finished, and when relevant information is stored into the request program database of set-top box end, turn to this step, upgrade and finish.

The flow process of video request program shown in Figure 12, it comprises step:

(1) front end broadcasting issues VOD service lists and satellite information thereof: front end encapsulates VOD service lists and satellite information thereof into transport stream (TS) according to the defined data structure of VOD protocol specification proposed by the invention, and issues by the mode of broadcasting; Wherein, the data structure of described VOD service lists and satellite information thereof provides definition by VOD protocol specification data structure; Wherein, the logical relation of described VOD protocol specification data structure and organizational form existing detailed description the in detail in structure shown in Figure 8 and structure explanation thereof.

(2) the set-top box termination is received and storage VOD service lists and satellite information thereof: bi-directional set-top box receives VOD service lists and satellite information thereof according to the defined data structure of VOD protocol specification, and these information is stored into the request program database of set-top box end; Wherein, described bi-directional set-top box has structure shown in Figure 9, and its module that comprises is shown in the structure explanation that Fig. 9 provides; Wherein, described reception VOD service lists and satellite information thereof and the flow and method that creates the request program database at the set-top box end are referring to flow process and the step explanation thereof shown in Figure 10 (set-top box is resolved the flow process of VOD service lists and satellite information thereof); Wherein, the renewal of described request program database is referring to flow process and the step explanation thereof shown in Figure 11 (the set-top box end upgrades the flow process of VOD service lists and satellite information thereof).

(3) broadcast in the program database at the set-top box end points and select or the screening program: the user need to watch request program, can directly call the service lists in the program request program database or filter out the user with the search engine that the information exchanges such as remote controller incoming traffic title, type of service, performer's title are crossed the set-top box end in the request program database and want the program watched.

Wherein, the method that described user directly calls the service lists in the program request program database refers to that the user is switched up and down by remote controller in program request interface display VOD service lists and satellite information thereof, selects program; Wherein, the demonstration ordering of described VOD service lists is according to VOD protocol specification data structure two: the value that VOD service priority (vod_service_priority) field identifies in the VOD service lists section (vod_service_list_section ()) sorts, numerical value is large comes the front, and what numerical value equated sorts according to the VOD Business Name; Wherein, described program request interface refers to show the interface of VOD service lists and satellite information thereof.Wherein, described program request interface as shown in figure 13.

In specific implementation process, the described search engine of crossing the set-top box end with information exchanges such as remote controller incoming traffic title, type of service, performer's titles filters out method that the user wants to watch program and refers to screen program at the request program search interface by remote controller incoming traffic title or type of service or performer's title in the request program database in the request program database; Wherein, described request program search interface as shown in figure 14.Wherein, described request program search interface comprises three alternative search keys, is respectively Business Name, type of service, performer's title; Wherein, described type of service can be searched in the request program database by remote controller incoming traffic type keyword, also can select the VOD type of service by the right and left key that switches remote controller; Wherein, described type of service comprises: film, and drama, TV play, news, performance, match, physical culture, juvenile, blue or green few, music, dancing, culture, art (not containing music, dancing), science, education, social, political, economy, amusement and other.Wherein, described search engine filters out the program that the user wants to watch in the request program database after, can show at the program request interface corresponding information comprise VOD Business Name and satellite information thereof; Wherein, described search engine can not find the user and wants the program watched in the request program database, have corresponding prompting.

In specific implementation process, the VOD service lists of described program request interface display and satellite information thereof refer to the relevant information of VOD Business Name and the current VOD business of choosing; Wherein, the relevant information of the described current VOD business of choosing comprises picture or audio frequency and video fragment, Business Name or traffic segment number, duration or segmentation duration, performer's title, pricing information; Wherein, described picture or audio frequency and video fragment are used for providing picture introduction or the excellent audio frequency and video fragment with the VOD traffic aided; Wherein, existing picture has again the audio frequency and video fragment in the satellite information of the described current VOD business of choosing, and can preferentially show the audio frequency and video fragment at the program request interface; Wherein, the textual description of described Business Name or traffic segment number and business or traffic segment is associated, when remote controller is chosen Business Name or traffic segment number and by acknowledgement key, can be seen the text profile of VOD business or VOD traffic segment; Wherein, described duration or segmentation duration will be seen the whether segmentation of the current VOD business of choosing; Wherein, described performer's title and performer's profile information are associated, when remote controller is chosen performer's title and by acknowledgement key, can be seen performer's profile information; Wherein, described performer's title can have a plurality of; Wherein, described pricing information provides the price relevant information of current VOD business.Wherein, the Business Name in the described VOD service lists and VOD server ip address and VOD server ip address for subsequent use are associated, for the program request of program provides relevant information.

(4) confirm play-on-demand program and send order request: the user confirms play-on-demand program, and the set-top box end sends order request to the VOD server.

After the user chose the program of wanting to see at the program request interface, the set-top box end sent order request to the VOD server; Wherein, the program chosen of described user and a VOD server ip address and VOD server ip address for subsequent use are associated; Wherein, described VOD server refers to the uniquely identified VOD of the VOD server ip address institute server of choosing program to be associated with the user; Wherein, when described VOD server was unavailable, described VOD server ip address for subsequent use began to enable; Wherein, described order request comprises VOD business that the user chooses and the relevant information of subscriber computer top box; Wherein, the relevant information of described subscriber computer top box refers to the information such as intelligent card numbers, sequence number.

(5) front end VOD server issues the program request parameter and broadcasts request program: VOD server response order request issues the relevant parameter information such as VOD business frequency, and broadcasts the program of user's program request to the set-top box end.

After described VOD server receives the order request of user's transmission, relevant information according to the subscriber computer top box that obtains is carried out authentication, the authentication success, described VOD server issues the relevant parameter information such as VOD business frequency to the set-top box end, and broadcast the program of user's program request, the forward end Subscriber Management System sends the charging relevant information simultaneously.

(6) the set-top box end obtains the program request parameter and carries out program and play: the information such as the program request parameter acquiring frequency that the set-top box end issues according to the VOD server, task identifier, PID, and carry out the program playback process according to these information.

Figure 15 shows the flow process of the player method of the digital television program that the embodiment of the invention provides.

In step S1501, provide server and at least one receiving terminal for digital television;

In step S1502, described server sets in advance the VOD protocol specification, and according to the VOD protocol specification VOD service lists and satellite information thereof is sent to described receiving terminal for digital television by the mode of broadcasting;

In step S1503, described receiving terminal for digital television sets in advance the VOD protocol specification, and according to the VOD protocol specification VOD service lists and the satellite information thereof that described server sends is stored to the request program database;

In step S1504, described receiving terminal for digital television mates relevant program and is shown to the user according to the matching identification of user's input in described request program database; And, receive user's play-on-demand program request;

In step S1505, described receiving terminal for digital television receives user's play-on-demand program request, obtains TV programme according to described play-on-demand program request from described server and plays to the user.

Wherein, when described receiving terminal for digital television mates relevant program and is shown to the user according to user's matching identification in described request program database, comprising:

Wherein, under described VOD protocol specification, the data structure of the data flow of transmitting between described server and described receiving terminal for digital television comprises that linkage descriptor, VOD service lists section, VOD business information section, price are with reference to descriptor, image data section and audio frequency and video fragment insertion information.

Wherein, when described receiving terminal for digital television obtains VOD service lists and satellite information thereof from data flow, may further comprise the steps:

Resolve and reception image data section, obtain corresponding image data;

Wherein, described method is further comprising the steps of:

Figure 16 shows the structure of the receiving terminal for digital television that the embodiment of the invention provides.

Memory module 1601 is used for pre-stored VOD protocol specification, and according to the VOD protocol specification VOD service lists and the satellite information thereof that described server sends is stored to the request program database;

Display module 1602 is used for mating relevant program and being shown to the user at described request program database according to the matching identification of user's input;

Playing module 1603 is used for receiving user's play-on-demand program request, obtains TV programme according to described play-on-demand program request from described server and plays to the user.

Wherein, described receiving terminal for digital television also comprises:

Matching module 1604 is used for receiving the matching identification of user's input at the relevant program of described request program database coupling.

Wherein, described receiving terminal for digital television also comprises:

Acquisition module 1605 is used for resolving and reception VOD service lists section, obtains the address information of VOD service lists and described server; Resolve and receive VOD business information section, obtain the VOD service related information; Resolve and receive price with reference to descriptor, obtain professional way of paying, price relevant information; Resolve and reception image data section, obtain corresponding image data; Resolve and receive the audio frequency and video fragment and insert information, storage VOD business information section middle pitch video segment inserts the associated audio frequency and video sheet section business of information.

Wherein, described receiving terminal for digital television also comprises:

Contrast module 1606 is used for obtaining VOD service lists version number from data flow, and the VOD service lists version number that obtains and the VOD service lists version number that is stored in the described request program database are compared; If inconsistent, then control described acquisition module described VOD service lists is upgraded.

The beneficial effect that technical solution of the present invention is brought:

Compare with system based on the Play System of above-described a kind of digital television program and the implementation method of method, receiving terminal for digital television and in the past video request program, have at least following beneficial effect:

(1), front end initiatively issues the rendition list and satellite information thereof by the mode of broadcasting, and these information are stored in the request program database of set-top box end, the user can directly see request program tabulation and satellite information thereof at the program request interface of set-top box end, broken when bi-directional set-top box obtains program request the rendition list in the past and need to send the request of obtaining program request the rendition list, front-end server sends request program tabulation and satellite information thereof by IP to set-top box, when concurrency was enough large, traditional mode may cause network congestion.Solution of the present invention has solved the problem of network congestion.

(2), broken the passive general layout that issues request program tabulation of traditional VOD server, change from passive to active.

(3), make up the request program database at the set-top box end, compare with traditional VOD, it is more convenient and swift to obtain the rendition list and satellite information thereof, has greatly improved user's experience.

(4) compare with traditional VOD, audio frequency and video sheet section business a kind of and VOD traffic aided connection is provided, audio frequency and video sheet section business is used for providing the wonderful of VOD business, thereby can more attract spectators.

(5), traditional VOD needs the integrating browsing device, the integrated of browser brought complexity to software development, and different browsers is difficult to accomplish compatibility to different VOD, gives the integrated very large risk of having brought.And the solution that the present invention proposes does not need the integrating browsing device, only need to just can obtain VOD tabulation and satellite information thereof according to the defined VOD protocol specification of the present invention data structure analyzing atransmission stream (TS), thereby finish video request program.Thereby make software integrated more easy, and reduced the integrated risk of bringing.

(6), technical scheme universality proposed by the invention is strong, is applicable to the transmission system of any channel coding method, comprises wired, ground, satellite.

(7), can provide the VOD of magnanimity professional, and user friendlyly search selection, the experience that brings searching programs on the Internet to the user.

The above only is preferred embodiment of the present invention, not in order to limiting the present invention, all any modifications of doing within the spirit and principles in the present invention, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.

Claims

1. the Play System of a digital television program is characterized in that, described system comprises server and at least one receiving terminal for digital television;

Described receiving terminal for digital television, set in advance the VOD protocol specification, according to the VOD protocol specification VOD service lists and the satellite information thereof that described server sends is stored to the request program database, under described VOD protocol specification, the data structure of the data flow of transmitting between described server and described receiving terminal for digital television comprises that linkage descriptor, VOD service lists section, VOD business information section, price are with reference to descriptor, image data section and audio frequency and video fragment insertion information;

2. the Play System of digital television program as claimed in claim 1, it is characterized in that, when described receiving terminal for digital television mates relevant program and is shown to the user according to user's matching identification in described request program database, comprise described VOD service lists and satellite information thereof are shown to the user, select program by the user according to described VOD service lists and satellite information thereof; And

3. the Play System of digital television program as claimed in claim 1 is characterized in that, when described receiving terminal for digital television obtains VOD service lists and satellite information thereof from data flow, comprising:

Resolve and reception image data section, obtain corresponding image data;

4. the Play System of digital television program as claimed in claim 1, it is characterized in that, described receiving terminal for digital television, also be used for obtaining VOD service lists version number from data flow, the VOD service lists version number that obtains and the VOD service lists version number that is stored in the described request program database are compared, if inconsistent, then described VOD service lists is upgraded.

5. the player method of a digital television program is characterized in that, described method comprises:

Server and at least one receiving terminal for digital television are provided;

6. the player method of digital television program as claimed in claim 5 is characterized in that, when described receiving terminal for digital television mates relevant program and is shown to the user according to user's matching identification in described request program database, comprising:

7. the player method of digital television program as claimed in claim 5 is characterized in that, when described receiving terminal for digital television obtains VOD service lists and satellite information thereof from data flow, may further comprise the steps:

Resolve and reception image data section, obtain corresponding image data;

8. the player method of digital television program as claimed in claim 5 is characterized in that, described method is further comprising the steps of:

9. a receiving terminal for digital television is characterized in that, described receiving terminal for digital television comprises:

Memory module, be used for pre-stored VOD protocol specification, and according to described VOD protocol specification VOD service lists and the satellite information thereof that server sends is stored to the request program database, under described VOD protocol specification, the data structure of the data flow of transmitting between described server and described receiving terminal for digital television comprises that linkage descriptor, VOD service lists section, VOD business information section, price are with reference to descriptor, image data section and audio frequency and video fragment insertion information;

10. receiving terminal for digital television as claimed in claim 9 is characterized in that, described receiving terminal for digital television also comprises:

11. receiving terminal for digital television as claimed in claim 9 is characterized in that, described receiving terminal for digital television also comprises:

12. receiving terminal for digital television as claimed in claim 11 is characterized in that, described receiving terminal for digital television also comprises: