JP4717915B2 - Broadcast receiving apparatus and method for controlling broadcast receiving apparatus - Google Patents

Description

  The present invention relates to a broadcast receiving apparatus and a broadcast receiving apparatus control method for performing preview display of print data before printing out print data generated from structured document data for printing described in a markup language. .

  Conventionally, there exists an information processing apparatus that generates print data based on structured print document data described in a markup language. A typical example of such an information processing apparatus is a printing apparatus (printer) compatible with digital television broadcasting.

  There is so-called data broadcasting in Japanese digital television broadcasting. Then, it has been standardized by ARIB (Radio Industry Association) so that a print service (hereinafter referred to as data broadcast printing) can be provided using this data broadcast framework.

  There are roughly two types of data broadcasting printing. In the first method, the digital television broadcast receiver receives the substance of the print content included in the data broadcast data multiplexed and transmitted on the broadcast wave, and transfers it to the printer. The printer generates print data using the substance of the received print content. Hereinafter, this method is referred to as a print file method. In the second method, the digital television broadcast receiver receives address information indicating the storage destination of the print content and transfers the address information to the printer. The printer that has received the address information acquires the substance of the print content based on the address information, and generates print data. Hereinafter, this method is referred to as a print URI method.

  Japanese data broadcasting is required to use a page description language (markup language) for data broadcasting called BML (Broadcast Markup Language), which is formulated based on XML (extensible Markup Language). For data broadcast printing, ARIB conforms to XHTML (extensible HyperText Markup Language) -Print and CSS (Cascading Style Sheet) Print Profile as encoding of a document for printing. Here, XHTML-Print defines the elements and attributes of print data. The CSS Print Profile (hereinafter referred to as CSSPP) defines the print data layout, font size, and the like. That is, the print content data includes structured document data for printing such as an XHTML file and a CSS file. Depending on the contents of the print content, mono media data such as a JPEG file or a PNG file whose path is described in the XHTML file is also included. Hereinafter, when referred to as print content data, a description will be given as a data group including at least print structured document data.

In both the print file method and the print URI method described above, the printer generates final print data. This is also defined by the standard. That is, the printer interprets the XHTML file and the CSS file and performs a rendering process for generating bitmap data. Therefore, in principle, a digital television broadcast receiver such as a digital television does not have a function of interpreting print content and generating image data. Therefore, when the user desires to display an outline of the print data on the screen of the digital television and confirm (hereinafter referred to as a preview), the printer creates the print image data and transmits the print image data to the digital television. (See Patent Document 1).
JP 2000-112691 A

  BML browser applications and HTML browser applications (hereinafter simply referred to as browsers) installed in current digital television broadcast receivers display BML contents in normal data broadcasting and HTML contents in the general Internet, respectively. Is possible.

  However, it has been difficult for these browsers to display structured document data for printing encoded by XHTML-Print or CSSPP. The reason is that, in order to interpret and render an XHTML file for preview processing, a lot of memory and CPU power are required. A digital television broadcast receiver is also equipped with a memory and CPU, but more memory and CPU power are required to perform the preview process, which is not realistic.

  Also, as a second reason, even when trying to display structured document data encoded with XHTML-Print and CSSPP using a BML browser or HTML browser, these browsers appropriately display elements and attributes depending on the printing process. Cannot be interpreted. As a result, the layout and display differ from the actual print data, and the preview is not established.

  Furthermore, in the method shown in Patent Document 1, it is necessary to generate image data such as a BMP image and a JPEG image after the printer generates print data even when only previewing is performed. Accordingly, the processing time and processing load increase, and the encoder and memory for generating data are also required for the printer.

  The present invention has been made to solve the above-described problem, and before printing out print data generated from structured document data for printing described in a markup language in printing of digital broadcast data broadcasting. An object of the present invention is to provide a broadcast receiving apparatus and a control method for the broadcast receiving apparatus for appropriately displaying a preview of the print data using the browser function of the broadcast receiving apparatus.

In order to achieve the above object, a broadcast receiving apparatus of the present invention is a broadcast receiving apparatus that is connected to a printing apparatus via a network and is capable of receiving a data broadcast, and is included in the received data broadcast data Printing structured document data or URI information indicating the storage destination of the structured printing document data to be transmitted to the printing apparatus, and printing to the printing apparatus using the structured printing document data Issuing means for issuing a command for instructing generation of preview structured document data, and structured document data described in HTML for accessing the print preview structured document data generated by the printing apparatus Control means for starting a browser application capable of interpreting the print data, and structured document data for print preview notified in advance from the printing apparatus. Storage means for storing an address indicating the storage destination of the print preview image, and using the address stored by the browser application in the storage means, the print preview structured document data is acquired, interpreted, and rendered as a print preview image It possesses a display means for displaying on the display unit, a print preview structured document data generated is indicated in the printing device by the issuing means, specialized in printing included in the printing structured document data The described description content is structured document data that has been changed to the description content corresponding to the display in the browser application .

In order to achieve the above object, a control method for a broadcast receiving apparatus according to the present invention is a control method for a broadcast receiving apparatus capable of receiving a data broadcast while being connected to a printing apparatus via a network. A transmission step of transmitting to the printing apparatus URI structured information for storing the structured document data for printing or the structured document data for printing included in the received data broadcasting data; An issuance step for issuing a command instructing generation of structured document data for print preview using the structured document data, and HTML for accessing the structured document data for print preview generated by the printing apparatus. Control step of starting a browser application capable of interpreting structured document data described in the above, and notification from the printing device in advance A storage step of storing in the storage unit an address indicating the storage destination of the structured document data for print preview, and the browser application using the address stored in the storage unit in the storage step get the structured document data, interpret have a, a display step of displaying on the display unit the print preview image drawn by printing preview structuring produced in the printing device in the issuing step is instructed The document data is structured document data in which the description content specialized for printing included in the structured document data for printing is changed to the description content corresponding to the display in the browser application .

  As described above, according to the present invention, in printing a digital broadcast data broadcast, before printing out print data generated from structured document data for printing described in a markup language, a broadcast receiving apparatus It is possible to appropriately display the preview of the print data using the browser function.

Example 1
[Preview content data generation processing]
Hereinafter, embodiments according to the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing an environment for data broadcast printing in the present embodiment. A digital television broadcast receiver 101 (hereinafter referred to as a DTV) as a display device and a digital television printer 102 (hereinafter referred to as a DTV printer) as an information processing device are communicably connected by a home network 108. The home network 108 can be connected to the Internet 105 via the router 103. That is, the DTV 101 and the DTV printer 102 can access the Web server 106 via the Internet 105. Further, the DTV printer 102 can acquire the printing content 107 stored in the Web server 106.

  The DTV 101 can receive the digital broadcast transmitted from the broadcast station 109 via the antenna 104. Further, as described above, the DTV 101 can acquire the print content data 110 transmitted using the digital broadcast data broadcast. Further, the print content data 110 can be transferred to the DTV printer 102 via the home network 108.

  Next, the configuration of the DTV 101 will be described with reference to FIG. FIG. 2 is a functional block diagram for explaining the internal structure of the DTV 101.

  The DTV 101 includes a CPU 201 that controls the entire DTV and a memory 202 that is used for storing and operating control programs. The CPU 201 and the memory 202 are connected to the remote control I / F 211 and the network I / F 212 via the internal bus 210. A remote control I / F 211 is an interface for performing communication with a remote control device (not shown). A network I / F 212 is an interface for communicating with the DTV printer 102 and the router 103 via the home network 108 described above.

  A broadcast wave received by the antenna 104 is input to the tuner 203. The tuner 203 selectively outputs a broadcast wave having a frequency specified by a channel selection operation or the like to the demodulation circuit 204. The demodulating circuit 204 demodulates the input broadcast wave into MPEG-2 TS (Transport Stream). MPEG-2 TS is a data stream in which video, audio, data, and the like are encoded and multiplexed. The separation circuit 205 separates the MPEG-2 TS into packetized encoded data such as video PES (Packetized Elementary Stream) and audio PES. The separation circuit 205 also separates section data such as SI (Service Information) used for generating caption data and EPG included in the TS.

  The PES and section data separated by the separation circuit 205 are respectively input to the decoder unit. The decoder unit includes a video decoder 206 that decodes the video PES into a video signal and an audio decoder 207 that decodes the audio PES into an audio signal. Further, a data decoder 208 for decoding the section data is provided.

  The video signal and audio signal decoded by the decoder unit are subjected to image processing and audio processing, respectively, and output to an output unit 209 such as a monitor or a speaker. The decrypted data is stored and managed in a memory, and is output to the output unit 209 by a predetermined operation. For example, when the user performs a subtitle display operation, the subtitle data is combined with the video signal and output. When the user performs an operation for displaying data broadcast, the content for data broadcast decoded by the data decoder 208 is interpreted by a predetermined application. Then, it is displayed on the output unit 209 as a data broadcast screen.

  Next, the configuration of the DTV printer 102 in this embodiment will be described. FIG. 3 is a functional block diagram for explaining the internal configuration of the DTV printer 102. The configuration of the DTV printer 102 connected to the DTV 101 via the network 108 is roughly divided into a network controller 301 and a printer controller 302.

  The network controller 301 has a CPU 311 for controlling the control, a buffer memory for temporarily storing received data, and a DRAM 312 used as a work memory. In addition, the network management apparatus includes a NIC 315 that is a network interface controller that performs communication with devices connected to the network 108. Furthermore, it has a program ROM 313 in which an execution program is stored and a font ROM 314 in which font data is stored. And it has serial IO316 used for communication with the printer controller 302 mentioned later. These functional blocks are connected by an internal bus of the network controller 301.

  Next, the configuration of the printer controller 302 will be described. The printer controller 302 includes a P-CPU 321 that is a printer controller CPU that performs control. In addition, a buffer memory for temporarily storing received data and a P-DRAM 322 used as a work memory are provided. In addition, a P-ROM 323 storing an execution program is provided. A P-SIO 324 is a serial IO on the printer controller side for communicating with the network controller 301. These blocks are connected to the printer engine controller 325 by an internal bus. The printer engine controller 325 is a controller for controlling various drivers and motors related to the driving of the printer. A head driver 326 for driving the inkjet head 27 is controlled by the printer engine controller 325. The engine controller 325 controls a motor driver 329 for driving a carriage motor 329 for moving the head and a motor driver 330 for driving a paper feed motor 331 for conveying paper.

  As described in the background art, in data broadcasting printing defined by ARIB, the DTV printer 102 interprets the structured document data for printing described in the markup language format and generates print data. . Therefore, taking the DTV printer 102 shown in FIG. 3 as an example, the flow of the printing process will be briefly described. Of the two types of data broadcast printing, the flow of print processing using the print file method is described here.

  First, print content data that is the substance of the print content acquired by the DTV 101 is transmitted from the DTV 101 to the DTV printer 102 via the network 108.

  The network controller 301 of the DTV printer 102 stores the transmitted print content data in the DRAM 312 and then interprets the XHTML-Print file and the CSSPP file, which are structured document data included in the print content data. Then, after interpreting these files, a rendering process for generating print image data is performed.

  The print image data generated by the network controller 301 is transferred to the printer controller 302 via the serial IO. In order to print the transmitted print image data, the printer controller 302 drives the printer and performs print output under the control of the printer engine controller 325.

  4 and 5 are flowcharts illustrating the execution procedure of the print file method and the print URI method in data broadcast printing.

  FIG. 4 is a flowchart for explaining the print file system for data broadcast printing in this embodiment. When the DTV 101 that has acquired the substance of the print content data from the data for data broadcasting is ready for printing, it issues a print request JOB to the DTV printer 102 (step S401). The DTV printer 102 that has received the print request JOB sets a data sink area for receiving the print content data if the print content data can be received. Then, status information indicating that printing is possible is returned to the DTV 101 together with the data sink information (step S402).

  The DTV 101 that has received the information indicating that printing is possible transfers the print content data to the DTV printer 102 (step S403). The printing content data is transferred by HTTP POST processing.

  The DTV printer 102 stores the received print content data in the data sink area and starts print processing using the print content data. Details of the printing process will be described later.

  Next, FIG. 5 is a flowchart for explaining the print URI system for data broadcast printing in this embodiment. In the print URI method, the DTV 101 does not acquire the substance of the printing content data, but acquires address information (URI: Uniform Resource Indicator) indicating the storage destination of the printing content data from the data for data broadcasting. When ready for printing, the DTV 101 transmits the acquired URI information to the DTV printer 102 as a print request JOB (step S501). The DTV printer 102 that has received the print request JOB acquires the substance (structured document data and attached monomedia data) of the print content data indicated by the URI based on the URI information if the print request is possible. (Step S502). This acquisition process is performed by an HTTP GET process. When the DTV printer 102 acquires the substance of the print content data (step S503), the DTV printer 102 starts print processing. Details of the printing process will be described later.

  Here, an outline of the structured document data for printing (XHTML-Print and CSS Print Profile) included in the printing content data in the present embodiment will be described.

  XHTML-Print as the first structured document data prescribes the elements and attributes of print data, and is basically a format that conforms to the XHTML Basic specification, but can be used in comparison with XHTML Basic. The feature is that the types of various elements are limited. For example, the frame element is not supported and nesting of table elements is prohibited. Furthermore, the types of fonts that can be used are limited. Of course, since XHTML-Print is positioned as print data, it does not include descriptions having application-like elements such as forms and scripts.

  CSS Print Profile (CSSPP) as the second structured document data defines the layout and font size of print data. CSSPP conforms to the specification of CSS Level 2, but the types of styles that can be used are limited compared to CSS Level 2. Another feature is that it has been expanded so that a layout for printing can be specified. The layout is basically “position: static” as in the case of HTML CSS, but it is also possible to specify an absolute position by specifying “position: absolute” for the block element. However, regarding the size designation, since the resolution of each manufacturer's printer is not constant, designation in units of pixels is not possible. Therefore, it is possible to specify only absolute values such as “cm” and “mm” independent of the resolution. In addition, as a unique extended function, it is possible to specify a paper size, a page number, a header, a footer, and the like.

  Next, details of the printing process that is a feature of the present invention will be described with reference to the drawings. FIG. 6 shows a processing procedure of software processing executed by the network controller 301. Each function indicated by a circle will be described as corresponding to a software module.

  In the present embodiment, it is assumed that the interpretation and rendering of structured document data described in a markup language performed by the data processing described above is executed by software. The present invention is not limited to software processing. Each function of the software module described below can be implemented by hardware. Each module does not have to have an independent software structure. In FIG. 6, only one process is associated with one module in order to simplify the description.

  The print content data transmitted from the DTV 101 is received by the interface module 601. Then, the received print content data is passed to the subsequent parsing processing module 602. Although not shown, the interface module 601 also has a function of acquiring the internal status of the printer from the print controller 302 and transmitting it to the DTV 101 as printer status information. Similarly, the interface module 601 has a function of transmitting commands from the DTV 101 and commands from the network controller 301 to the printer controller 302.

  Of course, the interface module 601 can also obtain a URI indicating the storage location of the print content data from the DTV 101 and receive the substance of the print content data based on the URI.

  The parsing process 602 is a module that analyzes the syntax of structured document data such as an XHTML-Print file or a CSSPP file. Moreover, the process which extracts the designation | designated regarding a layout as a result of the analysis is also performed.

  A layout process 603 is a module that creates page layout information for making a print object physical page data based on the syntax information analyzed by the parsing process 602. For example, the page break position for making page data by reflecting the style information obtained by interpreting the CSSPP file in the text described in the XHTML-Print file or the image file specified in the XHTML-Print file. Create information for. At this time, the CSSPP file is referred to in the generation of the layout.

  A font process 604 is a module that mainly creates and manages font data specified by a CSSPP file. The font process 604 is also called to acquire font information when generating page layout information executed in the layout process 603.

  The rendering process 605 executes a process of converting an object given as numerical data such as vector data into image data by calculation. The rendering process 605, for example, decodes JPEG format data into RGB bitmap data, or executes an enlargement / reduction process for adjusting to a size specified by the layout information.

  The banding process 606 divides the entire drawing area of one page into a plurality of areas (bands), for example. The banding process 606 is a process for enabling the subsequent rasterization process 607 to execute drawing in band units.

  The rasterizing process 607 is a process for generating image data for printing using text included in the drawing area divided in band units in the banding process 606, image data rendered in the rendering process 605, and the like. By the rasterizing process 607, the final print data generation is completed.

  The print image data generated in the rasterizing process 607 is transferred to the printer controller 302 shown in FIG. 3 and subjected to a predetermined process.

  Here, before describing the CSSPP file and XHTML-Print file description change processing 608, the processing on the printer controller 302 side will be described.

  FIG. 7 is a diagram illustrating software processing executed by the printer controller 302. Note that each module indicated by a circle other than the printer engine 704 is assumed to correspond to software processing. Note that the printer engine in this embodiment is a system using an inkjet serial printer. The printer controller 302 in this printer does not perform advanced image processing or the like, and develops print image data on the memory of the printer controller 302. The expanded print image data is converted into a data format that can be processed by the printer engine, and printing is executed.

  A printer control execution process 701 is a module that executes various controls performed by the printer controller 302. Also, control for transmitting / receiving printer status information to / from the network controller 301 is executed.

  The image processing 702 is a module that receives the print image data generated by the rasterization processing 607 of the network controller 301 and executes image processing according to the output format of the printer engine. The image processing to be executed includes processing for converting multi-value RGB image data into binary CMYK image data.

  The output control 703 is a module that performs output control so that the print image data output from the image processing module 702 has an output format corresponding to the print processing executed by the printer engine 704.

  The printer engine 704 is a functional module corresponding to the head driver 326 and the motor driver in FIG.

  Now, referring back to FIG. 6, the process for changing the structured document data for printing, which is a characteristic process of the present invention, will be described.

  Reference numeral 608 denotes a description change processing module that changes the description contents of the two structured document data for printing, CSSPP and XHTML-Print. As described above, the print content data used in data broadcast printing includes two structured document data, XHTML-Print and CSSPP. These are each described in a markup language, but have a structure specialized for printing. For this reason, there is a problem that even if these are displayed with a normal HTML browser, the layout may be corrupted or not even displayed. This is because an ordinary HTML browser engine cannot interpret a structure specialized for XHTML-Print or CSSPP-specific printing.

  Therefore, the description change processing module 608 executes processing for changing the description contents of CSSPP and XHTML-Print specialized for printing so that the print page preview display can be appropriately performed by the HTML browser. Hereinafter, processing of the parsing processing 602, the layout processing 603, and the description change processing module 608 will be described using an example.

  FIG. 8 is a diagram for explaining the processing contents of the parsing process 602 for extracting page layout information from the CSSPP file and the description changing process 608 for changing the description contents of the CSSPP file and the XHTML-Print file based on the layout information. . Here, a description will be given assuming that a copy of the received CSSPP file and XHTML-Print file is generated and a description change process is performed on the generated copy file.

  In the CSSPP file, “@page” designation is a description item unique to printing. In general, since printing is output in units of pages, a special box called “page box” is used. The page box is composed of a “page area” and a “margin”. By specifying “@page” corresponding to this page box, values such as the size, orientation, and margin of the page box can be specified. FIG. 8 shows that a page area having a margin of 3 mm is specified for A4 size vertically placed paper.

  Also, style sheet descriptions can be divided by output destination. FIG. 8 shows that “screen” for display and “print” for printing are specified with different font sizes for the text.

  In the parsing process 602, layout information is extracted by analyzing the CSSPP file. First, the size and orientation of the page box and margin information described above are extracted from the “@page” designation. Next, the font size information is extracted for the print from the “@media” designation. The extracted information is transferred to the description change (CSS & XHTML Change) processing 608 together with the CSSPP file.

  In the description change process 608, a CSSPP file description change process is executed to make the CSSPP file into a CSS Level 2 compliant file that can be interpreted by the HTML browser engine.

  In the case of FIG. 8, in order to change CSSPP to CSS Level 2 (hereinafter referred to as CSS2), the information of the page box specialized for printing is changed to a display corresponding to browser display. Specifically, the page box information is deleted and a new box area designation description is added. In CSS2, the descriptions of “@page” and “@media” are deleted, and the box area is specified by the newly defined “all”. The box area is limited to a page width of 210 mm and a margin of 3 mm in the horizontal direction, but there is no limit in the vertical direction. This is assumed to be displayed by an HTML browser. Further, because of the CSS2 for print preview, the font size relating to the print media remains 9pt.

  As described above, when the description of the CSS file is changed, it is necessary to change the corresponding XHTML-Print file. Therefore, the XHTML-Print file is also passed to the description change process 608.

  When the CSS file is changed as shown in FIG. 8, in order to make the XHRML-Print file into the XHTML Basic file format, it is necessary to enclose the entire XHTML description in a box area by “all” of CSS2. Therefore, in FIG. 8, “all” is described in the class attribute using the div element after the body element as XHTML Basic. Since there is no restriction on nesting (nesting) of the div element, there is no problem even if the div element is added to the XHTML-Print file.

  In this way, the description change process 608 changes the CSSPP file to a CSS2 compatible description using the layout information extracted in the parsing process 602. In addition, the XHTML-Print file is changed to a description corresponding to XHTML Basic in accordance with the change of the CSSPP file.

  Further, the description change processing 608 executes processing for inserting a description indicating the page break position into the CSSPP file and the XHTML-Print file for print preview display. In the case of XHTML-Print and CSSPP, a page-break-before that executes a page break immediately before an element including the property is prepared as a property for performing settings related to page break control. In addition, page-break-after that executes a page break immediately after an element including a property and page-break-inside that is executed in the middle of an element including a property are also provided.

  These all specify page breaks in the print output on paper, and are therefore only applied when printing is performed. Therefore, this property cannot be interpreted by an HTML browser engine having no page concept. Naturally, there is no description indicating the page break position in the data displayed by the HTML browser.

  Therefore, in the description change process 608, the page break position is detected using the page break related properties extracted by the parser process 602. Further, information for displaying the page break position in the browser is added to the XHTML file and the CSS file. Accordingly, even if an XHTML file compatible with XHTML Basic that does not have the concept of a page and CSS2 are displayed on the HTML browser, the user can visually recognize the position where the page breaks.

  There are also CSSPP files that do not use page break-related properties. In that case, a page break position may be calculated from the page unit layout information by the layout processing 603, and the above-described page break display description may be added to the position.

  FIG. 9 is an example of a CSS file and an XHTML file that have been subjected to the description change processing relating to the page break position described above. A border property is described in the CSS file in the CSS2 format for the purpose of displaying a horizontal ruled line indicating the page break position to the user at the detected page break position. In addition, in the XHTML file in the XHTML Basic format, a description for indicating “page break” as text information is added at the position of the horizontal ruled line. As a result, the horizontal ruled line and the text “page break” are displayed in the preview image of the print data displayed on the HTML browser as shown in the display example on the browser.

  Returning to FIG. 6, the description will be continued. By the description change processing 608 described above, the CSSPP file and the XHTML-Print file are changed to structured document data for preview conforming to CSS2 and XHTML Basic. In the HTTP server process 609, the CPU 311 of the network controller 301 executes a process of uploading the structured document data for preview and related monomedia data to an HTTP server (not shown) installed in the DTV printer 102. In the following description, the term “preview content data” will be described as a data group including at least preview structured document data.

  As described above, the preview content data is generated by changing the description content of the print structured document data to the preview structured document data. Unlike the prior art, the preview image is not generated based on the print data generated by the rendering process, so that the processing time required for the preview can be greatly shortened. In addition, since it is not necessary to perform rendering processing or image data storage, hardware resources such as a memory can be sufficiently utilized with existing resources for generating preview content data.

[Preview content data display processing]
Next, processing for displaying a print preview on the DTV 101 will be described. In DTV, in addition to BML browsers for displaying data broadcasts, an increasing number of models are equipped with general-purpose HTML browsers. Conventionally, there are many devices that provide these two types of browsing functions by mounting an application independent of the BML browser. However, recently, due to the necessity of increasing the efficiency of internal resources of devices, a configuration in which a BML browser and an HTML browser are operated by a single core engine is becoming available. Accordingly, an environment for seamlessly operating BML content and HTML content is being prepared.

  If a browser compliant with HTML is installed, structured document data corresponding to XHTML Basic and CSS2 can be displayed. Therefore, the preview content data generated by the above-described description change processing can be displayed via the HTML browser installed in the DTV 101.

  FIG. 10 is a conceptual diagram showing an application layer mounted on the DTV 101. The uppermost layer is a browser application layer, to which the browser 1001 corresponds. A script engine 1002, HTML / XHTML 1003, BML 1004, and plug-in 1005 correspond to the browser engine layer that is the next layer. The HTTP 1006 corresponds to the interface layer which is the next layer. The OS 1007 corresponds to the lowest layer.

  The BML 1004 is a browser engine corresponding to the data broadcasting BML. The BML1004 browser engine can display data broadcasts formulated by ARIB.

  HTML / XHTML 1003 is a browser engine corresponding to HTML and XHTML which are Internet contents. Therefore, this engine can display normal Internet content. Furthermore, an engine such as a script 1002 for executing various scripts and a plug-in 1005 corresponding to the plug-in is provided.

  In the DTV 101 of this embodiment, it is possible to display BML content for data broadcasting and display of Internet content with one browser application.

  FIG. 11 is a processing flow of preview display processing in the present embodiment. This processing flow describes both the processing on the DTV 101 side and the processing on the DTV printer 102 side. In any device, this processing is executed by CPUs (201, 311) that are mounted in each device and control each device. Hereinafter, this processing flow will be described.

  First, in a state where the data broadcast content is displayed on the browser, the user performs an operation of pressing the “preview” button displayed on the browser screen by operating the remote control device or the like. With this operation, the DTV 101 receives an input of a preview instruction (step S1101). FIG. 12 shows a state where the data broadcast content is displayed on the browser using the BML engine. In addition, buttons corresponding to four colors (the preview button is yellow) are displayed on the screen.

  Upon receiving the preview instruction, the CPU 201 of the DTV 101 transmits to the DTV printer 102 a URI indicating the substance of the print content data transmitted along with the data broadcast or the storage destination of the print content data (step S1102). . At this time, a preview instruction command for issuing an instruction to the DTV printer 102 is issued so that the DTV printer 102 executes the print preview process.

  The DTV printer 102 that has received the preview instruction command and the URI indicating the substance of the printing content data or the storage destination of the printing content data from the DTV 101 receives the input of the preview instruction command (step S1103). Although not specifically shown as a control step, when an entity file of print content data is received, generation of preview content data is started using the entity file. Further, in the case of a print URI format that receives a URI indicating a storage location of print content data, a process of acquiring a substance file of the print content data is performed by the process described with reference to FIG.

  Subsequently, the DTV printer 102 performs analysis processing of the acquired XHTML-Print file and CSSPP file based on the preview instruction command input in step S1103 (step S1104). The processing in this step corresponds to the parsing processing 602 shown in FIG.

  After the analysis, the DTV printer 102 executes a description change process for the XHTML-Print file and the CSSPP file (step S1105). The processing in this step corresponds to the description change processing 608 shown in FIG.

  Next, the DTV printer 102 uploads the preview content data (data group including the preview XHTML file and the CSS file) generated by the description change processing in step S1105 to the HTTP server of the DTV printer 102 (step S1106). The processing in this step corresponds to the HTTP server processing 609 shown in FIG.

  The DTV 101 starts an HTML browser engine after receiving an input of a preview instruction from the user in step S1101 (step S1107). This is performed in order to interpret the preview content data generated by the DTV printer 102 and display it on the browser.

  After starting the HTML browser engine 1003, the DTV 101 accesses the HTTP server to acquire the preview content data uploaded to the HTTP server in step S1106 (step S1108). Specifically, the file path of the XHTML file that is the preview content data, that is, the URI is accessed.

  Note that a URI for accessing the preview content data is determined in advance between the DTV 101 and the DTV printer 102. Various methods are conceivable as the arrangement method. In this embodiment, a URI for accessing preview content data is set in advance in the DTV printer 102 and shipped. When the DTV printer 102 and the DTV 101 are connected via a network, the URI is notified to the DTV 101 together with various setting values of the DTV printer 102. The DTV 101 stores the notified URI in an arbitrary memory area. In step S1108, when the DTV 101 accesses the HTTP server, the stored URI is used. Of course, when a print preview instruction is issued from the DTV 101, the DTV printer 102 holds the generated XHTML file on the HTTP server in association with the URI.

  Subsequently, the DTV 101 acquires preview content data (step S1109). At this time, if an attribute for designating mono media such as a JPEG image is described in the XHTML file, the designated mono media is also acquired. Finally, the HTML browser engine processes the acquired preview content data to display a print preview on the browser (step S1110).

  FIG. 13 is a diagram illustrating a case where a print preview is displayed on the browser 1001. A browser screen 1301 is displayed on the monitor of the DTV 101, and a preview generated based on the acquired print preview content data is displayed in the browser screen 1301. The user can confirm the displayed print preview and then press the “print” button displayed on the browser by operating the remote controller or the like. When the DTV 101 issues a print instruction command to the DTV printer 102, print data is generated using the print content data (data group including the XHTML-Print file and the CSSPP file) that has already been transmitted to the DTV printer 102.

  As described above, in the system including the DTV 101 and the DTV printer 102, the DTV printer 102 generates preview content data from the print content data. This preview content data can be displayed with XHTML and CSS specialized for printing on the browser installed in the DTV 101, and information such as page break position is added to meet the demand for print preview. It is a thing. The DTV 101 can provide an appropriate print preview image to the user by acquiring the XHTML generated by the DTV printer 102 and uploaded to the HTTP server and displaying the XHTML on the HTML browser.

  That is, when printing data broadcast of a digital broadcast, before printing out print data generated from the structured document data for printing described in a markup language, the print data preview is performed using the browser function of the digital television. Display can be performed.

  In this embodiment, the configuration of the DTV printer 102, in particular, the configuration shown in FIG. 6 is all expressed by software modules, but the present invention is not limited to this. Configurations such as the parsing process 602 and the description change process can also be implemented as hardware.

  In the DTV 101 of this embodiment, the HTML / XHTML browser engine 1003 and the BML browser engine 1004 are configured to use a common browser 1001, respectively, but the present invention is not limited to this configuration. The present invention can be applied even when each browser is implemented so as to correspond to each browser engine.

  In the first embodiment described above, when a print preview instruction command is issued from the DTV 101, the DTV printer 102 executes a process of converting print content data into preview content data.

  However, even when a printing instruction command is issued from the DTV 101, it is possible to prompt the user to confirm the preview before actually executing the printing process by the DTV printer 102. In this case, a preview XHTML file and CSS file are generated based on the print XHTML-Print file and CSSPP file, and are displayed on the browser of the DTV 101. Thereafter, when an instruction command indicating that printing may be performed with the preview content is input to the DTV printer 102, processing for generating print data from the received XHTML-Print file and CSSPP file for printing is executed. That's fine.

  By comprising in this way, the case where the printed matter which a user does not want can be suppressed.

It is the conceptual diagram which showed the environment of the data broadcast printing in the Example of this invention. It is a functional block diagram for demonstrating the internal structure of DTV101 in the Example of this invention. FIG. 2 is a functional block diagram for explaining an internal configuration of a DTV printer in an embodiment of the present invention. It is a flowchart explaining the print file system of the data broadcast printing in the Example of this invention. It is a flowchart explaining the print URI system of the data broadcast printing in the Example of this invention. It is a figure explaining the process performed with the network controller 301 in the Example of this invention. FIG. 6 is a diagram illustrating processing executed by the printer controller 302 according to the embodiment of this invention. It is a figure explaining the processing content of the description change process 608 in the Example of this invention. It is a figure which shows the example of the CSS file and XHTML file to which the description change process in the Example of this invention was performed. It is a conceptual diagram which shows the application layer mounted in DTV101 in the Example of this invention. It is a processing flowchart of the print preview display process in the embodiment of the present invention. It is a figure which shows the state which displayed the data broadcast content in the Example of this invention on the browser using the BML engine. It is a figure which shows the case where the print preview in the Example of this invention is displayed on the browser.

Explanation of symbols

101 DTV (display device)
102 DTV printer (information processing device, printing device)
108 Network 201 CPU
301 Network Controller 302 Printer Controller 602 Parse Processing Module 603 Layout Processing Module 608 Description Change Processing Module 609 HTTP Server Module 1001 Browser 1003 HTML / XHTML Browser Engine 1004 BML Browser Engine

Claims (2)

A broadcast receiving device connected to a printing device via a network and capable of receiving data broadcasts,
Sending means for sending the printing structured document data included in the received data broadcasting data or URI information indicating the storage destination of the printing structured document data to the printing apparatus;
Issuing means for issuing a command for instructing the printing apparatus to generate print preview structured document data using the print structured document data;
Control means for starting a browser application capable of interpreting structured document data described in HTML to access structured document data for print preview generated by the printing apparatus;
Storage means for storing an address indicating a storage destination of structured document data for print preview notified in advance from the printing apparatus;
Display means for displaying the print preview image drawn by interpreting and drawing the structured document data for print preview using the address stored in the storage means by the browser application;
I have a,
In the structured document data for print preview instructed to be generated by the printing device by the issuing means, the description content specialized for printing included in the structured document data for printing corresponds to the display in the browser application. The broadcast receiving apparatus is structured document data changed to the described contents . A method for controlling a broadcast receiving apparatus that is connected to a printing apparatus via a network and is capable of receiving a data broadcast,
A transmission step of transmitting to the printing apparatus URI information indicating the storage destination of the structured document data for printing or the structured document data for printing included in the received data broadcasting data;
Issuing a command for instructing the printing apparatus to generate print preview structured document data using the print structured document data;
A control step of starting a browser application capable of interpreting structured document data described in HTML in order to access structured document data for print preview generated by the printing apparatus;
A storage step of storing, in the storage unit, an address indicating a storage destination of the structured document data for print preview notified in advance from the printing apparatus;
The browser application uses the address stored in the storage unit in the storage step to acquire the print preview structured document data, and displays the print preview image drawn by interpretation on the display unit; and
I have a,
In the structured document data for print preview instructed to be generated by the printing apparatus in the issuing step, the description content specialized for printing included in the structured document data for printing is displayed on the browser application. A control method for a broadcast receiving apparatus, characterized in that the structured document data is changed to corresponding description contents .

Images