JP2008102874A - Device and method of debugging - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a device and a method of debugging, wherein a software module for debugging is installed if necessary. <P>SOLUTION: A reproducing device (100) is provided with a control module (201) for controlling operations of a debugging device and a script engine (203) for executing a program. A state monitoring module (205) monitors states of the control module (201) and the script engine (203) and detects change of the states. State notification modules (204, 206, 207, 208, 209) transmit the change detected by the state monitoring module (205) to a network device (2) connected to the reproducing device (100) notify a user of the change. The state monitoring module (205) and the state notification modules (204, 206, 207, 208, 209) are installed from an external device (3) to the reproducing device (100). <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention generally relates to a debugging device and a debugging method, and more particularly to a debugging device and a debugging method capable of debugging content.

In the past, various debugging methods have been developed to find and eliminate software / hardware defects and errors. As an example of such a debugging method, a debug boot program stored in a ROM is started by setting a debug mode using a test terminal, and an external RAM via a communication circuit is executed by executing the debug boot program. The debugging program necessary for execution of the debugging command is stored in a predetermined area of the RAM according to the input of the debugging command, and the stored debugging program is executed by the user. There is a microcomputer debugging method for debugging a program (see, for example, Patent Document 1).
JP 2006-91996 A

  Incidentally, in recent years, next-generation DVDs (HD DVDs and the like) having a larger storage capacity than conventional DVDs have been proposed. Unlike the conventional DVD, the next generation DVD includes highly interactive content. Such content is created by a content author such as a studio using, for example, a script language and XML (Extensible Markup Language). Therefore, when creating a content having an interactive function, it is necessary to debug a program included in the content described in a script language or XML.

  The method of debugging content can be roughly divided into the following two methods. One is a method of debugging content on an emulator. In this method, an emulation environment (emulator) is constructed on a device (for example, a personal computer) different from an actual (commercially available) playback device, and contents are debugged in the emulation environment. The other is a method of debugging content by embedding a debugging function in the playback device itself.

  However, with the former method, it is difficult to ensure that the actual playback device and the emulator on the personal computer perform exactly the same operation. For example, due to differences in CPU performance between actual playback devices and emulators, video / graphics decoding performance, differences in application software (middleware) that operates script files and XML files, etc. There is a problem that operation differs between an actual playback device and an emulator.

  On the other hand, in the latter method, there is no difference in performance between apparatuses as in the former method. However, there is a difference in software between an actual playback device and a playback device in which a debugging function is incorporated. For example, there is a difference in function, processing timing, and the like between a program compiled for an actual playback device and a program compiled for a playback device having a debugging function.

  Conventionally, a method called remote debugging is also used in an embedded device such as a playback device. Remote debugging is a method of debugging by connecting a terminal equipped with dedicated software (debugging software) having a debugging function to a playback device. In order to perform remote debugging, the debugging software needs to use the development environment of the playback device, the internal API, and the like. For this reason, there is a problem that information related to the development environment of the playback device and the internal API must be disclosed to a third party (for example, a studio or the like) different from the manufacturer of the playback device.

  Therefore, an object of the present invention is to provide a debugging device that has the same hardware and software as a commercially available playback device and can install a software module for debugging as necessary, and a commercially available playback device. It is an object of the present invention to provide a debugging method in which a debugging software module can be installed in a debugging device equipped with the same hardware and software as necessary.

  In order to solve the above-described problem, according to one aspect of the present invention, there is provided a debugging device capable of reproducing content including a program for realizing an interactive function, for controlling the operation of the debugging device. A control module; a script engine that executes the program; a state monitoring module that monitors states of the control module and the script engine and detects a change in the state of the control module and the script engine; and the state monitoring module A status notification module that transmits the change detected by the display device to a display terminal connected to the debug device and notifies the user of the change, and the status monitoring module and the status notification module include the debug device. Debug from an external device connectable to Debug device is provided that is installed on location.

  According to another aspect of the present invention, there is provided a debugging method for debugging content including a program having an interactive function using a playback apparatus capable of playing back the content, the debugging for debugging the content A step of installing a mode module from an external device into the playback device; and a state of the content activation in the playback device is displayed on a display terminal connected to the playback device by the debug mode module to the user A debugging method comprising the step of notifying a state.

  According to the present invention, the same hardware and software as a commercially available playback device are installed, and a debug device that can install a software module for debugging as required, and the same playback device as a commercially available playback device. It is possible to provide a debugging method capable of installing a software module for debugging in a debugging device equipped with hardware and software as necessary.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  First, a debugging apparatus according to an embodiment of the present invention will be described with reference to FIG.

  FIG. 1 is a block diagram showing a schematic configuration of a debugging apparatus according to an embodiment of the present invention. This debugging device is realized by, for example, an HD DVD playback device (hereinafter simply referred to as “playback device”) 100. The playback device 100 operates in two modes, a normal mode and a debug mode.

  The playback apparatus 100 includes a disk drive unit 101, a network control unit 102, a media drive unit 103, a data processor unit 104, a memory unit 105, a separation unit (DMUX) 106, a video decoder unit 107, a sub-picture unit 108, and a graphic decoder unit 109. , An audio decoder unit 110, a video processor unit 111, digital / analog (D / A) conversion units 112 and 113, an MPU unit 114, a key input unit 115, a ROM unit 116, and the like.

  The playback apparatus 100 reads out and plays back information from an information storage medium such as an optical disk (HD DVD or the like) 1. The optical disc 1 is mounted on the disc drive unit 101 of the playback device 100. The disk drive unit 101 rotationally drives the loaded disk 1 and acquires information stored in the disk 1 using an optical pickup (not shown).

  The network control unit 102 is a control unit for communicating with the network device 2 connected to the playback device 100 via a network. The network device 2 is a device having a network function such as a personal computer. A web browser 118 is installed in the network device 2. The network connecting the playback device 100 and the network device 2 is, for example, the Internet, a LAN (Local Area Network), or the like. The network device 2 is not limited to a personal computer and may be a digital television having a Web browser function. The software installed in the network device 2 is not limited to the Web browser 118, and may be an application that can process a program described in HTML and JavaScript (registered trademark).

  The media drive unit 103 accesses the external device (storage medium) 3 connected to the media drive unit 103 and acquires information from the external device 3. The external device 3 is a device that can be connected to the playback apparatus 100 and stores a plug-in module (debug mode module) 117. The debug mode module 117 is installed in the memory unit 105 via the media drive unit 103 and the data processor unit 104. The external device 3 is a removable medium such as a USB device or a memory card, for example. The external device 3 may be an HDD or a personal computer.

  The USB device can be set valid or invalid for each device (device authentication function). For this reason, when a USB device is used as the external device 3, the security function of the playback apparatus 100 can be enhanced.

  As described above, the information acquired by the disk drive unit 101, the network control unit 102, or the media drive unit 103 is supplied to the data processor unit 104.

  The data processor unit 104 performs error correction processing on the supplied information and stores it in a buffer (not shown) in the data processor unit 104. The information stored in the buffer includes, for example, management information and moving image information. Management information is supplied to the memory unit 105, and moving image information is supplied to the separation unit 106.

  The memory unit 105 records the supplied management information. The memory unit 105 uses management information for reproduction control, data management, and the like.

  The separation unit 106 separates the supplied moving image information into video information, graphic unit information, audio information, and sub-picture information. Also, the separation unit 106 supplies video information, graphic unit information, audio information, and sub-picture information to the video decoder unit 107, sub-picture decoder unit 108, graphic decoder unit 109, and audio decoder unit 110, respectively. The sub-picture information refers to image information such as subtitles.

  The video decoder unit 107 performs a decoding process on the video information. Also, the sub picture decoder unit 108 performs a decoding process on the sub picture information. Further, the graphic decoder unit 109 performs a decoding process on the graphic unit information. The video information decoded by the video decoder 107, the sub-picture information decoded by the sub-picture decoder 108, and the graphic information decoded by the graphic decoder 109 are a video processor. Supplied to the unit 111. On the other hand, the audio information that has been decoded by the audio decoder unit 110 is supplied to the D / A converter 113.

  The video processor unit 111 performs superimposition processing on information supplied from the video decoder unit 107, the sub-picture decoder unit 108, and the graphic decoder unit 109. In addition, the video processor unit 111 supplies the superimposed information to the D / A converter 112.

  The D / A converter 112 converts the information supplied from the video processor 111 into an analog signal. The converted signal is output as a video signal to a video display device (not shown) connected to the playback device 100. The video display device may be, for example, a liquid crystal display, a plasma display, a CRT (Cathode-Ray Tube), or the like.

  The D / A converter 113 converts the audio information supplied from the audio decoder unit 110 into an analog signal, and outputs the converted analog signal as an audio signal to a sound reproduction device (not shown). The audio reproduction device may be, for example, a speaker.

  The MPU unit 114 functions as a control unit that controls a series of reproduction operations for the optical disc 1, the network device 2, and the external device 3 as described above. The MPU unit 114 receives operation information from the key input unit 115, and is connected to each unit (for example, the MPU unit 114 in FIG. 1 with an arrow) based on a program stored in the ROM unit 116. Control).

  Next, the debug mode module 117 will be described in more detail with reference to FIG.

  FIG. 2 is a block diagram showing a state after the debug mode module 117 is installed (uploaded) from the external device 3 to the playback apparatus 100 shown in FIG. More specifically, FIG. 2 shows the external device 3 storing the debug mode module 117, the playback device 100 in which the debug mode module 117 is installed from the external device 3, and the network device 2 connected to the playback device 100. Are displayed.

  The debug mode module 117 is a software module (plug-in module) having a function of debugging content (program) for realizing an interactive function for a user. The content for realizing the interactive function may be included as part of the content that can be played back by the playback device 100. The content for realizing the interactive function includes, for example, advanced content in the HD DVD standard. Further, the debug mode module 117 can be installed from the external device 3 to the playback apparatus 100 as needed (dynamically). Further, as shown in FIG. 2, the debug mode module 117 stored in the external device 3 includes an HTTP server module 117A, a debug terminal plug-in 117B, and a player plug-in 117C.

  The HTTP server module 117A includes a dynamic library having an HTTP server function. This dynamic library is used in a process being executed by the playback apparatus 100, and is executed as an independent thread (HTTP server thread) by the MPU unit 114 (FIG. 1) of the playback apparatus 100.

  The debug terminal plug-in 117B includes an HTML file, a JavaScript (registered trademark) file, a PNG / JPEG image file, and the like. These files are files delivered to the network device 2 via the HTTP server 204 (described later).

  The player plug-in 117C includes a script file, an XML file, and the like that are executed on the script engine 203 (described later).

  When the debug mode module 117 stored in the external device 3 is installed in the playback device 100, the HTTP server module 117A functions as the HTTP server 204, and the debug terminal plug-in 117B includes the GUI screen file 206 and the terminal script file. The player plug-in 117C functions as the state monitoring module 205, the player script file 208, and the data conversion module 209.

  Next, the playback apparatus 100 after the installation of the debug mode module 117 described above will be described from the viewpoint of software with reference to FIG. 2 together with FIG.

  As shown in FIG. 2, the playback apparatus 100 after the installation of the debug mode module 117 includes a control module 201, an advanced content application 202, a script engine 203, and a debug mode module 117. The debug mode module 117 includes an HTTP server 204, a GUI screen file 206, a terminal script file 207, a state monitoring module 205, a player script file 208, and a data conversion module 209. In FIG. 2, the debug mode module 117 installed in the playback apparatus 100 is surrounded by a broken line.

  When the playback device 100 is used in the normal mode, the control module 201, the advanced content application 202, and the script engine 203 are used. On the other hand, when the playback device 100 is used in the debug mode, each module included in the debug mode module 117 is used in addition to the modules used in the normal mode.

  First, modules used in the normal mode will be described.

  The control module 201 is an execution program stored in the ROM unit 116 (FIG. 1) of the playback device 100 and controls the playback device 100. More specifically, the control module 201 performs, for example, playback control of video images, state management necessary for advanced content, resource management, and the like. The control module 201 is executed on the MPU unit 114 at the same time when the playback device 100 is activated.

  The advanced content application 202 is supplied to the playback apparatus 100 from an information storage medium such as the optical disc 1. In this case, the advanced content application 202 is loaded from the optical disc 1 into the memory unit 105 via the disc drive unit 101, the data processor unit 104, and the separation unit 106. The advanced content application 202 has an interactive function for the user in addition to the conventional video image. The advanced content application 202 is created by a content author (content provider) such as a video studio in the same manner as video content. The advanced content application 202 includes a script file described using a script language (for example, ECMA script) and an XML file described using a markup language (for example, XML). The script file is executed by the script engine 203. The XML file is processed by an XML engine (not shown) in cooperation with the script engine.

  The execution module of the script engine 203 is stored in the ROM unit 116 of the playback device 100, and is executed by the MPU unit 114 after the playback device 100 is activated. The script engine 203 is a module that executes advanced content described in a script language. The script engine 203 issues various commands to the control module 201 such as a command for instructing playback / stop of video images and a command for instructing display of a content title list.

  Next, modules used in the debug mode will be described.

  The HTTP server 204 is a server for communicating with the network device 2 connected to the playback apparatus 100 via a network. The HTTP server 204 is executed as an independent thread by the MPU unit 114 of the playback device 100 and communicates with the network device 2 via the network control unit 102. The network device 2 includes a web browser 118 for transmitting various commands to the HTTP server 204 and displaying a response from the HTTP server 204 on the GUI screen.

  Note that when the playback device 100 itself has a Web browser function, it is not necessary to connect the network device 2 to the playback device 100. In this case, instead of the network device 2, a display terminal such as a TV monitor that displays a video signal output from the D / A conversion unit 112 via the video processor unit 111 as an image can be used. At this time, the contents of the HD DVD and the GUI screen for debugging can be displayed on the same screen of the display terminal as picture-in-picture (PIP) or displayed semi-transparently. Further, the contents of the HD DVD and the GUI screen for debugging work may be displayed on different display terminals.

  The status monitoring module 205 monitors the status of the control module 201 and the script engine 203 and detects a status change. The change in the state of the control module 201 includes, for example, a change in the video (content) playback state, a change in the usage rate of the CPU, a change in the usage rate of resources available for the content, and the like. The change in the video playback state includes, for example, start / stop of execution of the advanced application, start / stop of video video playback, title jump, chapter jump, and changes in playback time, subtitle, audio, or the like. On the other hand, examples of the state change of the script engine 203 include execution interruption at a breakpoint, step execution, exception occurrence, and the like. Further, the state monitoring module 205 determines whether an error has occurred during the reproduction of content (during execution of an advanced application).

  The GUI screen file 206 is a file distributed to the Web browser 118 of the network device 2 by the HTTP server 204, and includes, for example, an HTML file and an image file. The GUI screen file 206 constitutes a GUI screen that can notify the user (content author) of a change in the state of the playback device 100 detected by the state monitoring module 205.

  The terminal script file 207 is a file distributed to the Web browser 118 of the network device 2 by the HTTP server 204, similarly to the GUI screen file 206. The terminal script file 207 is composed of a file written in a script language that is executed on the Web browser 118.

  The player script file 208 is a file described in a script language, and controls the state of the playback device 100. The player script file 208 is read and executed by the script engine 203 via the control module 201 in response to the start / stop of the advanced application detected by the state monitoring module 205.

  The data conversion module 209 converts the state change detected by the state monitoring module 205 into a data format for transmission to the network device 2 (or the Web browser 118) via the HTTP server 204. In other words, the data conversion module 209 converts the state change into a data format that can be processed by the network device 2 (or the Web browser 118). This data format includes XML, JSON (JavaScript Object Notation) format, and the like.

  Note that the HTTP server 204, the GUI screen file 206, the terminal script file 207, the player script file 208, and the data conversion module 209 described above are transmitted to the network device 2 connected to the playback apparatus 100 by transmitting changes in the state of the playback apparatus 100. A function as a status notification module that transmits and notifies the user of the change is realized.

  In the above description, the debug mode module 117 is installed in the playback device 100 from the external device 3 as necessary. However, it is also possible to install the debug mode module 117 in the playback apparatus 100 in advance.

  As described above, according to the debugging device (reproducing device 100) according to an embodiment of the present invention, it is possible to debug content using a Web browser without preparing a terminal equipped with debugging software. It becomes. For this reason, a debugging environment using an existing network can be easily constructed, and the cost required for debugging can be reduced. Further, by performing debugging processing using a widely used Web browser, debugging processing by the content author can be simplified and development efficiency can be improved.

  In addition, according to the debugging device according to the embodiment of the present invention, the debug mode module (117) can be installed (uploaded) as a plug-in module on the original hardware and software for debugging. For this reason, it is not necessary to rebuild the firmware of the debugging device. In addition, the difference between the debugging operating environment and the actual operating environment is small as compared with the case where debugging is performed using a debugging device in which a debugging function is incorporated in advance. Therefore, more accurate debugging can be performed.

  Furthermore, according to the debugging device according to the embodiment of the present invention, it is possible to debug content by a third party such as a studio without exposing the API or the like of the debugging device to the third party.

  Further, according to the debugging device according to the embodiment of the present invention, the debugging device can be easily switched between the normal mode and the debugging mode. For this reason, for example, after debugging the content by setting the debug device to the debug mode, the debug device can be set to the normal mode and the content can be played to check whether the content operates normally. . Therefore, the efficiency of the debugging process can be improved.

  Next, a debugging method according to an embodiment of the present invention will be described with reference to FIG. This debugging method can be applied to the playback apparatus 100 shown in FIGS. 1 and 2, for example. Hereinafter, for convenience of explanation, a case where the debugging method according to the present embodiment is applied to the playback apparatus 100 will be described as an example.

  The debugging method shown in FIG. 3 roughly includes two processes, that is, a process for enabling the debug function and a debug process. These processes are performed on content for realizing an interactive function for the user. The content having an interactive function includes, for example, advanced content in the HD DVD standard. In addition, the debugging method according to the present embodiment is used by the content author when creating content. For example, it is used by studio employees when creating movie content.

  First, processing (steps S301 to S308) for enabling the debugging function will be described. The external device 3 storing the debug mode module 117 is connected to the playback apparatus 100 (step S301). When the external device 3 is connected to the playback apparatus 100, the control module 201 determines whether or not the debug mode module 117 is already installed (uploaded) in the playback apparatus 100 (step S302). This determination can be made based on whether or not a specific class of the ECMA script exists in the playback device 100, for example.

  If the debug mode module 117 is not installed in the playback apparatus 100 (NO in step S302), the debug mode module 117 is installed from the external device 3 into a specific memory area of the playback apparatus 100 (step S303). On the other hand, if the debug mode module 117 is already installed in the playback device 100 (YES in step S302), the process proceeds to step S304.

  Subsequently, the HTTP server 204 is activated (step S304). Further, the state monitoring module 205 is activated (step S305). In this state, the control module 201 determines whether it is the start timing of the advanced application (step S306). The process of step S306 is repeated until the start timing of the advanced application is reached.

  When the start timing of the advanced application is reached (YES in step S306), the player script file 208 in the debug mode module 117 is transferred to the script engine 203 together with the content of the advanced application (step S307). Thereafter, the advanced application is activated (step S308). Although not shown in FIG. 2, if the advanced application has already been activated in step S306, the process proceeds to step S310.

  Next, the debugging process (Steps S309 and S310) will be described. After starting the advanced application (step S308), the state monitoring module 205 determines whether an error has occurred (step S309). An error can occur, for example, during execution of a script file or an XML file. For example, in a display device such as a television connected to the playback device 100, an icon can be displayed at an unintended location on the display of the display device.

  When an error occurs (YES in step S309), the GUI screen of the web browser 118 that notifies the user (content author) of the error is displayed on the display of the network device 2, and the user displays the displayed GUI screen. An error is confirmed through the advanced application debugging work (step S310). For example, in a debugging operation, a script file or an XML file is corrected. In this case, for example, the file to be corrected is edited using a general-purpose editor or the like. The edited (modified) file is converted into a format defined by the advanced content specification. After this conversion, the modified file or the like is stored in an information storage medium such as the optical disc 1, and the advanced application is activated again.

  When the content to be debugged is played back from a hard disk drive (HDD) connected to the playback device 100, the script file or XML file stored in the HDD is directly edited from the network device 2 in debugging work ( Then the application is restarted.

  After the debugging operation (and compilation) in step S310, the process returns to step S308. On the other hand, when the advanced application process is completed without an error (NO in step S309), the debug process ends. In the above description, the state monitoring module 205 detects an error in step S309. However, when the user views the GUI screen displayed on the display of the network device 2, an operation different from the intended operation is performed. If it is determined that the error occurred, the operation can also be treated as an error.

  Next, a process for enabling or disabling the function of the debug mode module 117 installed in the playback apparatus 100, that is, a process for switching the playback apparatus 100 between the debug mode and the normal mode will be described with reference to FIG. To do.

  FIG. 4 is a flowchart for explaining processing for switching the playback device 100 in which the debug mode module 117 is installed between the debug mode and the normal mode. The process shown in FIG. 4 is started after the external device 3 is connected to the playback apparatus 100, the debug mode module 117 is installed from the external device 3, and the debugging process is completed. In other words, it is started after the processing of FIG. At the end of the debugging process, the playback device 100 operates in the debug mode.

  First, the control module 201 determines whether or not the external device 3 is connected to the playback device 100 (step S401). When the control module 201 determines that the external device 3 is connected to the playback device 100 (YES in step S401), the playback device 100 is maintained in the debug mode (step S402). More specifically, the control module 201 does not stop the operations of the HTTP server 204 and the state monitoring module 205. That is, the function of the debug mode module 117 in the playback device 100 is maintained valid. The processes in steps S401 and S402 are repeated until it is determined that the external device 3 is not connected to the playback apparatus 100.

  On the other hand, when the control module 201 determines that the external device 3 is not connected to the playback apparatus 100 (the connection between the external device 3 and the playback apparatus 100 has been disconnected) (NO in step S401), the playback apparatus. 100 is switched from the debug mode to the normal mode (step S403). More specifically, the control module 201 stops the operations of the HTTP server 204 and the state monitoring module 205. That is, the function of the debug mode module 117 in the playback device 100 is disabled. Accordingly, the playback device 100 is maintained in the normal mode (step S404).

  Next, the control module 201 determines whether or not the external device 3 is connected to the playback device 100 (step S405). If the control module 201 determines that the external device 3 is not connected to the playback device 100 (NO in step S405), the process returns to step S404. The processes in steps S404 and S405 are repeated until it is determined that the external device 3 is connected to the playback apparatus 100.

  On the other hand, when the control module 201 determines that the external device 3 is connected to the playback device 100 (YES in step S405), the playback device 100 is switched from the normal mode to the debug mode (step S406). More specifically, the control module 201 restarts the operations of the HTTP server 204 and the state monitoring module 205. That is, the function of the debug mode module 117 in the playback device 100 is enabled. After the playback device 100 is switched from the normal mode to the debug mode, the process returns to step S401.

  In the above description with reference to FIGS. 4 and 5, switching between the normal mode and the debug mode is performed based on whether or not the external device 3 is connected to the playback device 100. However, switching between the normal mode and the debug mode can be performed by another method. For example, it is possible to employ a method in which a hidden command corresponding to the normal mode and a hidden command corresponding to the debug mode are set in the playback apparatus 100 in advance. In this case, switching between the normal mode and the debug mode can be performed by transmitting the hidden command using a remote controller (not shown) that can transmit various instructions to the playback apparatus 100.

  In addition, the debug mode module 117 installed (uploaded) in the playback apparatus 100 can not only disable the function but also uninstall it as necessary.

  Note that the debugging method according to the embodiment of the present invention described above can also be realized by a program executable by a computer.

  As described above, according to the debugging method according to an embodiment of the present invention, it is possible to debug content using a Web browser without preparing a terminal equipped with dedicated software for debugging. For this reason, a debugging environment using an existing network can be easily constructed, and the cost required for debugging can be reduced. Further, by performing debugging processing using a widely used Web browser, debugging processing by the content author can be simplified and development efficiency can be improved.

  Further, according to the debugging method according to the embodiment of the present invention, the debug mode module (117) is installed (uploaded) as a plug-in module on the original hardware and software of the debug device (playback device 100) as necessary. can do. For this reason, it is not necessary to rebuild the firmware of the debugging device. In addition, the difference between the debugging operating environment and the actual operating environment is small as compared with the case where debugging is performed using a debugging device in which a debugging function is incorporated in advance. Therefore, more accurate debugging can be performed.

  Furthermore, according to the debugging method according to the embodiment of the present invention, it is possible to debug content by a third party such as a studio without exposing the API or the like of the debugging device to the third party.

  In addition, according to the debugging method according to the embodiment of the present invention, the debugging device can be easily switched between the normal mode and the debugging mode. For this reason, for example, after debugging the content by setting the debug device to the debug mode, the debug device can be set to the normal mode and the content can be played to check whether the content operates normally. . Therefore, the efficiency of the debugging process can be improved.

  Note that the present invention is not limited to the above-described embodiments as they are. In the implementation stage, the present invention can be embodied by changing the components without departing from the scope of the invention.

  Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

It is a block diagram which shows schematic structure of the debugging apparatus based on one Embodiment of this invention. It is a block diagram which shows the state after a debug mode module is installed in the debugging apparatus shown in FIG. 1 from an external device. 5 is a flowchart for explaining a debugging method according to an embodiment of the present invention; It is a flowchart for demonstrating the process which switches the debug apparatus in which the debug mode module was installed between debug mode and normal mode.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Disk, 2 ... Network device, 3 ... External device (external device), 100 ... HD DVD recording / reproducing apparatus, 101 ... Disk drive part, 102 ... Network control part, 103 ... Media drive part, 104 ... Data processor part , 105 ... Memory section, 106 ... Separation section (DMUX), 107 ... Video decoder section, 108 ... Sub picture decoder section, 109 ... Graphic decoder section, 110 ... Audio decoder section, 111 ... Video processor section, 112 ... D / A Conversion unit 113 ... D / A conversion unit 114 ... MPU unit 115 ... Key input unit 116 ... ROM unit 117 ... Debug mode module 117A ... HTTP server module 117B ... Debug terminal plug-in 117C ... Player plug In, 118 ... Web browser , 201 ... control module, 202 ... advanced content application, 203 ... script engine, 204 ... HTTP server, 205 ... status monitoring module, 206 ... GUI screen file, 207 ... terminal script file, 208 ... player script file, 209 ... data conversion module.

Claims (10)

A debugging device capable of reproducing content including a program for realizing an interactive function,
A control module for controlling the operation of the debugging device;
A script engine for executing the program;
A state monitoring module that monitors states of the control module and the script engine and detects a change in the state of the control module and the script engine;
A status notification module that transmits the change detected by the status monitoring module to a display terminal connected to the debug device and notifies the user of the change;
Comprising
The debug device, wherein the status monitoring module and the status notification module are installed in the debug device from an external device connectable to the debug device.   The status monitoring module monitors at least one of a change in the content playback state in the debug device, a CPU usage rate by the debug device, and a usage rate of resources available in the content. The debugging device described.   The debugging apparatus according to claim 1, wherein the status notification module transmits the change to the display terminal in data format that can be processed by a Web browser. The status notification module
A player script file for controlling the state of the debugging device;
A data conversion module that converts the change into data in a data format that can be processed by the display terminal when the state of the debug device changes;
An HTTP server module that transmits the data converted into the data format by the data conversion module to the display terminal;
A GUI screen file and a terminal script file distributed to the display terminal by the HTTP server module;
The debugging device according to claim 1, comprising:   The debug device can operate in one of a normal mode in which the functions of the status monitoring module and the status notification module are disabled, and a debug mode in which the functions of the status monitoring module and the status notification module are enabled. The debugging device according to claim 1. The debugging device includes:
After the status monitoring module and the status notification module are installed in the debug device, when the connection between the debug device and the external device is broken, the normal mode operates.
If the external device is connected to the debugging device after the state monitoring module and the status notification module are installed in the debugging device and the connection between the debugging device and the external device is disconnected, the debugging Work in mode,
The debugging device according to claim 5. A debugging method for debugging content including a program having an interactive function using a playback device capable of playing back the content,
Connecting an external device storing a debug mode module for debugging the content to the playback device;
Installing the debug mode module from the external device to the playback device;
Monitoring the state of the playback device during the content processing by the debug mode module, displaying the state on a GUI screen displayed on a display terminal connected to the playback device, and notifying the user of the state When,
A debugging method comprising: The connecting step includes:
8. The method according to claim 7, further comprising: connecting one selected from the group consisting of a USB device, a memory card, a hard disk drive, and a personal computer storing the debug mode module as the external device to the playback apparatus. Debugging method. Disabling the function of the debug mode module installed in the playback device when the connection between the external device and the playback device is broken;
The debugging method according to claim 7, further comprising: Enabling the function of the debug mode module installed in the playback device when the external device is reconnected to the playback device after the connection between the external device and the playback device is disconnected; ,
The debugging method according to claim 7, further comprising:

Images