WO2007064056A1

WO2007064056A1 - System and method for the construction of application manager for set top box

Info

Publication number: WO2007064056A1
Application number: PCT/KR2005/004322
Authority: WO
Inventors: Myung-Hwan Kim; Jaeseong Ko
Original assignee: Celrun Co., Ltd.
Priority date: 2005-12-02
Filing date: 2005-12-15
Publication date: 2007-06-07
Also published as: KR100720164B1

Abstract

Disclosed are a system for the construction of an application manager for a set top box and a construction method thereof. The system in accordance with the present invention is characterized in that the XML story DB is saved in the programmer's terminal and applications and the application manager are saved in the set top box. The application manager is characterized in that it can control and manage applications according to the story of the XML story DB saved in the programmer's terminal depending on situations. Accordingly, differently from the conventional type, since the story of the XML script with superior compatibility and changeability is constructed, with the data separated from the process, the application manager can be constructed simply by correcting and modifying. In accordance with the present invention, the application manager can be constructed easily because only the designing and correction of data are required. Because the history data can be saved and searched during the construction, bugs can be detected easily. In addition, the application manager can be modified easily when another application is loaded on the set top box.

Description

SYSTEM AND METHOD FOR THE CONSTRUCTION OF APPLICATION MANAGER FOR SET TOP BOX

Technical Field

[1] The present invention relates to a system and a method for the construction of an application manager for a set top box enabling easier designing and construction of the application manager of a set top box and easier correction of errors. Background Art

[2] As is generally known, a set top box refers to a "home telecommunication terminal" needed to use the so-called interactive TV, which is a next-generation interactive multimedia communications service including video on demand (VOD), video home shopping, network game, and so forth.

[3] It was named so because it was "a box located on a TV set". It is also called as

"subscriber signal conversion apparatus". The set top box is used, for example, to access the video transfer services provided by interactive TVs or telephone companies (e.g., "video dial tone" provided by an American telephone company) as connected to a TV monitor, etc. It receives telecommunications and video signals from a video server, etc. of a telephone company or a cable television (CATV) broadcasting station and converts them. For use in telephones and "data telecommunications services" such as PC telecommunications, various protocols including telephone interface and PC access interface are under consideration.

[4] The set top box requires various applications enabling the utilization of various contents. And, an "application manager", or an operation program, is needed to adequately control and manage the applications.

[5] Let's take an example for illustrating the function and role of the application manager. Suppose that a user executes an online game while watching TV. For the online game (hereinafter "AP3") to be executed, the Internet access application (hereinafter "API") has to be run and the TV application (hereinafter "AP2") has to be closed. The screen resolution has to be changed to 640x480 for the online game "AP3" to be executed. Thus, the application manager adequately manages and controls several applications to provide the service wanted by the user.

[6] Such an application manager is constructed by a procedure as illustrated in Fig. 1 and Fig. 2. Conventionally, the construction procedure has been encoded in machine language depending on the particular control situations for start, end, setup, etc. of applications. In such a construction, the execution history data and the execution module are mixed with each other. [7] The conventional construction of the application manager is carried out as illustrated in Fig. 1 and Fig. 2. Fig. 1 is a construction flowchart (Sl) of the conventional application manager for a set top box. Fig. 2 is a detailed flowchart of the application manager creation step (SlO) in Fig. 1. And, Fig. 3 shows an example of a menu map of a set top box.

[8] Let's examine the conventional designing and construction procedure of an application manager referring to Fig. 1 and Fig. 2. A programmer carries out an application manager creation step (SlO) comprising set top box's menu map creation (SI l) (see Fig. 3) → compiler creation (S12) → application loading (S13) → application control code input/save (S 14) using a terminal. Subsequently, the created application manager is loaded on a set top box which is connected to the programmer's terminal (S20). Then, by manipulating the set top box, menu-specific and on/off testing of the application manager is carried out to see if the application manager operates normally (S30). When an error (bug) occurs during the test, the location of the bug is searched (S40) and debugging is carried out (S50). This procedure can be carried out only through the programmer's terminal. The programmer reloads the debugged application manager on the set top box and performs a confirmation test. This procedure is repeated until no bug occurs.

[9] Accordingly, the conventional application manager creation procedure (SlO) requires a lot of time and effort. Besides, when another application is added to the set top box, another complier has to be created. Therefore, adaptability or flexibility of an application cannot be expected at all. Further, since the error correction (debugging) has to be preformed with the programmer's terminal, not with the set top box, the debugged application manager has to be reloaded on the set top box prior to the execution test.

[10] That is, in addition to the problem that the creation of the application manager is performed with machine language, bug search and debugging cannot be performed effectively. Consequently, a lot of time and cost are required for the development of applications.

Disclosure of Invention Technical Problem

[11] The present invention has been made to solve the afore-mentioned problems. An object of the present invention is to provide a system and a method for the construction of an application manager for a set top box in which, during the construction of the application manager for a set top box, an execution module-based application manager and applications are loaded on the set top box and an XML-based history DB comprising execution control history data in which the set top box's menu-specific and situation-specific application execution environments are defined is saved in the programmer's terminal, so that the programmer can easily construct the application manager by simply modifying the XML story DB.

[12] Another object of the present invention is to provide a system for the construction of an application manager for a set top box in which a history DB wherein all history data during the XML story DB construction step, set top box execution control step, bug reporting step, debugging step, etc. is equipped at the programmer's terminal, so that the programmer can easily understand the application manager construction procedure and necessary measures.

[13] Still another object of the present invention is to provide a system for the construction of an application manager for a set top box in which the application manager displays the history data saved in the history DB on the programmer's terminal, so that the programmer can find the bug more easily.

[14] Still another object of the present invention is to provide a system for the construction of an application manager for a set top box in which the application manager can search and load the XML engine from the OS source DB saved in the programmer's terminal, search and parse the XML story DB saved in the programmer's terminal and convert it into the execution-machine language.

[15] Still another object of the present invention is to provide a method for the construction of an application manager for a set top box in which, after debugging and XML story DB creation have been completed, the XML story DB is transplanted from the programmer's terminal to the application manager of the set top box.

[16] Other objects and particular advantages of the present invention will become apparent by the following detailed description. Technical Solution

[17] In order to attain the afore-said objects, the system for the construction of an application manager for a set top box according to the present invention comprises: a programmer's terminal equipped with an XML story DB comprising a set top box's control history data; and the set top box which is connected to the terminal and is equipped with an application manager that optimizes the specific applications of the set top box and the execution environment of each application by, when there is a control command input from the terminal, searching, parsing and loading the corresponding XML script from the XML story DB. Since the XML story DB is saved in the programmer's terminal separated from the application manager of the set top box, designing and construction of the application manager and error correction can be carried out by simply changing the XML story DB. That is, the XML story DB is saved in the programmer's terminal during designing and constructing the application manager. And, the set top box is equipped with the application manager which adequately controls various applications. Since the data and the set top box's application manager are separated from each other, addition of another application, data error (bug) correction, environment setup of a new application manager, and so forth can be performed more easily. Thus, simplification of applications, reduction of development period and joint development become possible.

[18] The terminal or the set top box may further comprise: a history DB in which all the history data during the construction step of the application manager are saved; or an OS source DB (153) in which the resource data of the terminal's operating system (e.g., Windows) are saved. Since the XML story data, which are the basic data in running the application manager, can be retrieved during the construction and control steps, problems occurring during the development can be found and analyzed.

[19] The application manager is characterized in that it comprises: a start module which searches and loads the XML start script from the XML story DB when the set top box receives a start command from the terminal; and a closure module which searches the XML closure script from the XML story DB and closes the applications according to the story defined in the XML closure script when the set top box receives a closure command from the terminal. The application manager is characterized in that it is run based on the XML story DB.

[20] And, preferably, the application manager further comprises: an XML parser module which parses the XML script and converts it into machine language; an XML engine loading module which searches the XML engine from the OS source DB and loads it on the XML parser module; and an execution module which controls the execution of the machine language converted by the XML parser module. Accordingly, since the XML engine is retrieved from the operating system (e.g., Windows) of the programmer's terminal and the XML script is parsed at the set top box, the application operating system can be simplified and there is no need of unnecessary file creation. In addition, it is sufficient to upgrade only the operating system of the programmer's terminal if the XML engine needs to be upgraded.

[21] Further, the application manager may comprise one or more module selected from: a check module which checks if there is a control command being executed or waiting to be executed and controls so that the control commands are executed in order; a save module which saves all the controls steps and construction and correction steps of the application manager in the history DB; and an output module which displays the content of the history DB on the terminal, including the save module. Thus, the application manager can be controlled reasonably, systematically and adequately and all the procedure can be saved in the history DB. Consequently, the afore-mentioned advantages including error detection can be attained. [22] And, preferably, the set top box further comprises a FIFO (First In, First Out) memory (RAM) which temporarily saves the control commands in order and processes them depending on the input order or function- specific priority.

[23] Preferably, the method for the construction of an application manager for a set top box in accordance with the present invention comprises:

[24] i) creating the control story of the applications of the set top box in XML script format and saving it in the XML story DB of the programmer's terminal (100); and

[25] ii) controlling search/loading/parsing/execution of the XML script corresponding to the control command input from the programmer's terminal to the set top box from the XML story DB and saving all the above procedure in the history DB and displaying them on the terminal.

[26] In the step ii), if an error (bug) occurs when the corresponding XML script has been executed, the history data displayed on the terminal is examined and the corresponding XML script is debugged and saved again in the XML story DB. The error correction procedure is stored in the history DB. Therefore, errors can be detected relatively easily and the debugging procedure is significantly simplified.

[27] Preferably, in the step ii), if an error (bug) has occurred when the corresponding

XML script has been executed, the operation of the set top box is stopped and the XML script in which the error exists is displayed on the terminal. Since the execution error and the corresponding XML script are displayed without having to ask the programmer, bug detection and debugging can be performed more easily.

[28] Lastly, following the step ii), if there is no error in the XML story DB any more, the

XML story DB saved in the terminal is loaded on the set top box. In this way, the construction of the application manager for a set top box is completed. Of course, following the loading, a final test is performed to re-evaluate and confirm the efficient operation of the set top box.

Advantageous Effects

[29] The present invention is advantageous in that there is no need of performing the construction of the application manager for a set top box in machine language, which is a hard code type language. Accordingly, any change of an application loaded on the set top box can be dealt with flexibly.

[30] Further, since the XML-based database and the module-based application manager are saved separately, the application manager can be constructed simply by modifying and correcting the database, resulting in easier programming.

[31] And, since the execution script is displayed in real time, it is easy to detect bugs.

Because all the procedure of XML story DB creation can be checked and the control status, etc. of the resultant XML story DB can be visibly understood, programming and designing can be performed more easily.

[32] In addition, since the resultant XML story DB can be extracted and transplanted in part to other set top boxes, construction of another application manager can be performed more efficiently. Brief Description of the Drawings

[33] Fig. 1 is the conventional construction flowchart of an application manager for a set top box.

[34] Fig. 2 is the detailed flowchart of the application manager creation step in Fig. 1.

[35] Fig. 3 illustrates an example of a menu map of a set top box.

[36] Fig. 4 illustrates the system for the construction of an application manager for a set top box according to the present invention.

[37] Fig. 5 illustrates the application manager in Fig. 4 in detail.

[38] Fig. 6 is the construction flowchart of an application manager for a set top box in accordance with the present invention.

[39] Fig. 7 is the operation flowchart of an application manager of a set top box in accordance with the present invention.

[40] Fig. 8 is the error correction control flowchart of an application manager of a set top box in accordance with the present invention. Mode for the Invention

[41] Hereunder are given the descriptions of the preferred embodiments of the present invention referring to the attached drawings. The following embodiments are exemplary ones and they do not limit the scope of the present invention. For the convenience of description, the same numerals are given to the identities that offer the same effects.

[42] Fig. 4 illustrates the system for the construction of an application manager for a set top box according to the present invention.

[43] Referring to Fig. 4, in the system for the construction of an application manager for a set top box according to the present invention (1), a programmer's terminal (100) and a set top box (200) are connected to each other by means of a known telecommunications means. A database (150) is constructed in the storage medium of the programmer's terminal (100), which can be a PC. The database (150) comprises an XML story DB (151), a history DB (152) and a source DB (153) of an OS (e.g., Windows) operating the programmer's terminal (100). In addition, a central process unit (CPU, 110), a memory (RAM, 120), a displayer (130), which can be a monitor, and an interface (140) which enables data transfer to and from the set top box (200) are provided.

[44] The set top box (200) is equipped with function-specific applications (230), a FIFO (First In, First Out) memory (RAM, 220), which is a temporary storage medium, and a module-based application manager (210) which enables data exchange with the interface (140) and searching and loading of a particular DB from the database (150).

[45] The XML story DB (151) is the technical feature of the present invention.

Depending on the menus or control environment of the set top box (200), the control history data for adequately controlling and managing applications as well as the execution order, execution condition, execution environment, etc. of applications are defined as XML script. As described above, if a user executes an online game while watching TV, the Internet access application (hereinafter "API") has to be run for the online game (hereinafter "AP3") to be executed. Also, the TV application (hereinafter "AP2") has to be closed and the screen resolution has to be changed to 640x480. The control story of applications is defined depending on the situation-specific and menu- specific control environments and conditions.

[46] The resultant XML story DB (151) cannot control and manage the set top box (200) by itself. That is, the application manager (210) is needed which searches the control command and the XML script corresponding to the execution environment from the XML story DB (151) and parsing (analyzing and converting) the searched XML script into machine language for execution at the set top box.

[47] Differently from the conventional ones, the application manager (210) in accordance with the present invention has an execution module structure in which no coded data are equipped inside, as illustrated in Fig. 5.

[48] Referring to Fig. 5, the application manager (210) in accordance with the present invention comprises a start module (211), a closure module (212), an XML engine loading module (213), an XML parser module (214), an execution module (215), a check module (216), a save module (217) and an output module (218).

[49] When the set top box (200) receives a start command from the programmer's terminal (100), the start module (211) searches the XML start script from the XML story DB (151) and loads it on the set top box (200). Accordingly, when the set top box (200) receives an operation start command from the programmer's terminal (100), the start module (211) searches the XML start script including the control story needed to start the set top box (200) and loads it on the set top box (200).

[50] As such, before the XML start script is loaded on the set top box (200), the XML engine loading module (213) searches the XML engine from the OS source DB (153) saved in the database (150) of the programmer's terminal (100) and loads it on the XML parser module (214). As described above, the XML parser module (214) parses (analyzes) the loaded XML start script and converts it into machine language. Depending on the story of the XML start script converted into machine language, the execution module (215) controls the execution of the corresponding application (230). [51] The check module (216) checks if there is a control command being executed or waiting to be executed and controls so that the control commands are executed in order. This is carried out based on the control data temporarily saved in the memory (RAM, 220) equipped in the set top box (200).

[52] The save module (217) saves all the controls steps and construction and correction steps of the application manager (210) in the history DB (152). The output module (218) displays the content of the history DB (152) on the displayer (130) of the terminal (100). Thus, not to mention the construction step of the XML story DB (151), the operation and control status of the application manager (210) can be checked in real time. Consequently, bug (error) detection can be carried out easily and debugging (error correction) can be performed immediately.

[53] The closure module (212) searches the XML closure script from the XML story DB (151) and closes the applications according to the story defined in the XML closure script when the set top box (200) receives a closure command from the terminal (100), thereby terminating the application manager (200).

[54] Such an application manager (210) has been developed by the present inventors. It is constructed such that a user can utilize it with a unique control command. Some examples of the control command are shown in Table 1.

[55] Table 1

[56] As shown in Table 1, the application manager (210) in accordance with the present invention is defined in the control module type with a unique control command. The programmer creates the XML story DB (151) using the language decoded by the application manager (210) as shown in Table 1. And, as explained above, each corresponding module of the application manager (210) enables the control of the set top box (200). [57] The method for the construction of an application manager for a set top box in accordance with the present invention is shown in Fig. 6. Fig. 6 is the construction flowchart (SlOO) of the application manager for a set top box in accordance with the present invention. Referring to Fig. 6, the construction procedure of the application manager (210) for a set top box in accordance with the present invention comprises programmer's development (SI lO) and transplantation (S 140) of the XML story DB (151).

[58] During the development step (Sl 10), the XML script, or the control story of the application corresponding to the menu map of the set top box (200) to be developed is created using the language and protocol defined in the afore-mentioned application manager (210) and saved (Si l l) in the XML story DB (151). The save step (Si l l) is carried out by the save module (217) into the history DB (152) of the terminal (100) (Sl 12). Following the step (Sl 12), the completed contents are displayed on the displayer (130) connected with the programmer's terminal (100) (S120).

[59] Subsequently, a control command is transmitted from the programmer's terminal

(100) to the set top box (200) to perform an operation test of the set top box (200) (Sl 13). Then, as described earlier, save at the history DB (152) (Sl 14) and display on the displayer (130) are carried out. When a bug is found in the XML script during the operation test, the programmer checks the control data displayed on the displayer (130), debugs the corresponding XML script (Sl 15) and saves the result in the XML story DB (151). In this process, the application manager (210) automatically saves all the procedure in the history DB (152) of the programmer's terminal (100) (Sl 16), while displaying them through the displayer (130) in real time. Following the debugging step (Sl 15), the programmer performs the operation test again to check if the application manager (210) operates normally. This procedure is repeated until all the errors are completely corrected. Accordingly, differently from the conventional technology, the operation test of the set top box (200) and debugging can be carried immediately by the automatic control action of the application manager (210) without the need of loading onto the set top box (200).

[60] After all the errors are corrected, the XML story DB (151) is loaded and transplanted to the set top box (200) as intended by the programmer. Then, the final test is performed (S 141) to check if the set top box (200) operates on its own after disconnecting the set top box (200) from the programmer's terminal (100). In this way, the construction of the application manager (210) for a set top box is completed.

[61] Hereinbelow is given a more specific description of the operation test of the set top box (200) during the construction step of the application manager, referring to Fig. 7 and Fig. 8.

[62] Fig. 7 is the operation flowchart of an application manager of a set top box in accordance with the present invention and Fig. 8 is the error correction control flowchart of an application manager of a set top box in accordance with the present invention.

[63] When the set top box (200) receives an operation start control command from the programmer's terminal (100), an initialization step (S210) for operating the application manager (210) begins. An operation step (S230) follows when each menu-specific operation command is received from the terminal (100) according to the menu map. Then, a set top box closure step (S240) follows when an operation stop control command is received from the terminal (100) (see Fig. 7).

[64] Referring to Fig. 7, in the initialization step (S210), the XML start script and the

XML engine is searched from the XML story DB (151) and the OS source DB (153) of the terminal (100) by the action of the start module (211) and the XML engine loading module (213) of the application manager (210) (S211). Then, the searched XML engine is loaded on the parser module (214) and the XML start script is parsed (analyzed) by the parser module (214), transformed into machine language and temporarily saved in the memory (RAM, 220) of the set top box (200) in order. In this process, the check module (216) of the application manager (210) manages and controls the execution waiting order and the operation of the application related with the parsed control story, and so forth in order to realize the optimum control environment.

[65] Next, the execution stories temporarily saved in the memory (220) are executed in order by FIFO (First In, First Out). This is managed by the execution module (215). When the execution step (S212) is completed, the set top box (200) is ready to operate and all the procedure is recorded and saved in the history DB (152) of the terminal (100) (S213).

[66] When the set top box (200) is ready to operate as described above, a control command is transmitted from the terminal (100) to the set top box (200) (S221) as shown in Fig. 8. The application manager (210) searches, parses and executes the XML script corresponding to the control command from the XML story DB (151) stored in the terminal (100) and determines if a bug exists (S222). If a bug is found, the control action of the application manager is stopped immediately and a bug occurrence script is displayed on the displayer. Consequently, the programmer can easily find a bug without much effort. After debugging is completed, the programmer saves the result in the XML story DB (151) (S224). Of course, all the afore-mentioned procedure is automatically saved in the history DB (152) of the terminal (100) (S225). If there is no bug, the next operation step (S230) follows.

[67] The operation step (S230) will be explained in more detail. When a control command from the menu map is received from the terminal (100) (S213), the XML script corresponding to the control command is searched and parsed as described earlier. Then, the check module (216) checks if it is a command defined in the application manager (210) saved in the set top box (200) and manages and controls the operation status, operation environment, etc. of the application corresponding to the control command. Further, it is checked if it is a blocked control command to determine if it is a controllable command (S232). If the control command is determined to be a controllable one, an execution command is saved in the memory (220) of the set top box (200) (S234). Then, the execution commands temporarily saved in the memory (220) are executed in order (S235). But, if the control command is determined to be an uncontrollable one, a new control command is saved in the XML story DB and the application manager (210) (S233) to provide new language and function to the application manager. Of course, all the above control procedure is automatically saved in the history DB (152).

[68] When the operation step (S230) is completed, the set top box closure step (S240) follows. When a closure control command is received from the terminal (100) (S241), the XML closure script is searched and parsed from the XML story DB (151) and the applications which are being executed are closed in order as defined in the story (S242). Of course, all the above set top box closure step (S240) is automatically saved in the history DB (152) (S236).

[69] The present invention can be carried out in variously modified forms. For example, the history DB (152) may be constructed inside the set top box (200) or may be connected at the outside of the programmer's terminal (100) as separate storage medium. And, the history DB (152) may be constructed such that it can be browsed by logging onto a website. This enables sharing of information with the set top box application developers, which contributes to the reduction of bugs.

Claims

[1] A system for the construction of an application manager for a set top box which comprises: a programmer's terminal (100) equipped with an XML (extensible markup language) story DB (database) (151) comprising control history data of a set top box (200); and the set top box (200) which is connected to the terminal (100) and is equipped with applications (230) for carrying out functions and an application manager (210) that optimizes execution environment of applications (230) by, when there is a control command input from the terminal (100), searching, parsing and loading XML script corresponding to the control command from the XML story DB (151), wherein the XML story DB (151) is saved in the programmer's terminal (100) as separated from the application manager (210) of the set top box (200), so that designing and construction of the application manager (210) and error correction thereof can be performed easily by simply modifying the XML story DB (151).

[2] The system for as set forth in claim 1, wherein the terminal (100) or the set top box (200) further comprises: a history DB (152) in which all history data generated during the construction of the application manager (210) is saved; and an OS source DB (153) in which resource data of a operating system (OS) of the terminal (100) is saved.

[3] The system as set forth in claim 2, wherein the application manager (210) further comprises: a start module (211) which searches and loads XML start script from the XML story DB (151) when the set top box (200) receives a start command from the terminal (100); and a closure module (212) which searches XML closure script from the XML story DB (151) and closes the applications according to a story defined in the XML closure script and then closes the set top box (200) when the set top box (200) receives a closure command from the terminal (100).

[4] The system as set forth in claim 2, wherein the application manager (210) further comprises: an XML parser module (214) which parses the XML script and converts it into machine language; an XML engine loading module (213) which searches XML engine from the OS source DB (153) and loads it on the XML parser module (214); and an execution module (215) which controls execution of the machine language converted by the XML parser module (214).

[5] The system for the construction as set forth in any of claims 1 to 4, wherein the application manager (210) further comprises a save module (217) which saves data generated during all controls steps, all construction steps and all correction steps of the application manager in the history DB (152), in combination with at least one module selected from: a check module (216) which checks if there is a control command being executed or waiting to be executed and controls so that the control commands are executed in order; and an output module (218) which displays content of the history DB (152) on a displayer (130) of the terminal (100) ,

[6] The system as set forth in any of claims 1 to 4, wherein the set top box (200) further comprises a FIFO (First In, First Out) memory (RAM) (220) which temporarily saves the control commands in order and processes them depending on input orders or function- specific priority.

[7] A method for the construction of an application manager for a set top box which comprises: i) creating control story of applications (230) of the set top box (200) in XML script format and saving it in a XML story DB (151) of a programmer's terminal (100); and ii) when a control command input is received from the programmer's terminal (100) to the set top box (200), searching, loading, parsing and executing XML script corresponding to the control command from the XML story DB (151) and saving all the procedures in a history DB (152) and displaying them on the terminal (100).

[8] The method as set forth in claim 7, wherein in the step ii), if an error (bug) occurs when the corresponding XML script has been executed, the history data displayed on the terminal (100) is examined and the corresponding XML script is debugged and saved again in the XML story DB (151) and error correction procedure is stored in the history DB (152).

[9] The method as set forth in claim 7, wherein in the step ii), if an error (bug) has occurred when the corresponding XML script has been executed, operation of the set top box (200) is stopped and the XML script in which the error exists is displayed on the terminal (100).

[10] The method as set forth in any of claims 7 to 9, wherein the step ii) is followed by load of the XML story DB (151), saved in the terminal (100), onto the set top box (100) in order to complete construction of the application manager, if no error is found in the XML story DB (151).