KR100480287B1 - Customizing method of database in embedded system - Google Patents

Abstract

The present invention is connected to a console terminal (Console Terminal) having a transmission module for transmitting and receiving data through a network, and a transmission module for transmitting and receiving data to and from the outside, in response to the command received by the transmission module function corresponding to the command A method for customizing a database of an embedded system operating a system having an agent module to perform, a file storage module storing a database and a data file composed of information on maintenance and operation, the agent module comprising: A first step of converting the database stored as a binary data file into a text file in response to a script file generation command provided from the console terminal, and storing the database in an internal memory area of the file storage module; In the internal memory area In a second process of transmitting the loaded script file to the console terminal, the agent module loads the received script file into the internal memory area in response to receiving a modified script file and a database recovery command from the console terminal, and 2 Restoring the database by restoring the data into a binary data file, and the received script file includes a third process of modifying the console terminal.

Description

CUSTOMIZING METHOD OF DATABASE IN EMBEDDED SYSTEM}

The present invention relates to a method of operating a plurality of embedded systems commonly connected to a network, and more particularly, to a control method of easily customizing and updating a database of a plurality of embedded systems. .

Embedded systems (hereinafter referred to as "EMS") are intelligent systems that can operate independently and are designed to perform specific functions for each product. Specific functions of the EMS are executed by application software designed to perform operations of the corresponding functions of the EMS. The EMS performs its own function as the application software programmed for the operation and operation purpose is loaded. Examples of EMS include large systems such as exchanges from small systems such as set top boxes, Internet phones (web phones), and voice over internet protocol gateways (VOIPs) which are well known.

 In this case, according to the type and function of the system, the EMS has information required for the operation of the system in the form of a database in addition to the application software. Like application software, these databases can be created on an external maintenance terminal (for example, a computer that is an external console terminal), loaded into the system, or created automatically by application software loaded on the system. . The database can also be modified by the operational status of the system and the needs of the user.

The database is divided into a default database including configuration information for determining a system operation configuration, and an operation database that is automatically modified by a processor during operation of the system. The default database is not loaded from an external console terminal, but is loaded from an internal flash memory or created by itself, and an operation database refers to a database that is automatically modified during system operation. The default database and operational databases are generally produced in the form of a binary file and loaded into the system for operation, modification, backup and recovery. However, to back up the database being used by the EMS to an external console terminal (ie, a computer), modify the database, and to load the EMS again, a separate editing tool (eg MIB: Management) to handle the database backed up by the EMS is required. Information Base).

That is, when a database mounted and operated in the EMS is backed up or modified from an external computer, or when the modified database is loaded into the EMS, the database must be processed in the form of a binary file that is operated in the system. Therefore, a separate editing tool (eg, MIB) is needed to handle the database, and a specialized knowledge for handling the separate editing tool is required.

In addition, in an environment in which a plurality of EMSs are connected through a network such as the Internet and operate in conjunction with the same functions for the purpose of redundancy, capacity expansion, load distribution, etc., a system user may modify each database of the system equally. It was inconvenient to modify all of the systems in the system, or to modify the database of one system, back it up, and reload the rest of the systems.

Accordingly, an object of the present invention is to provide a method for easily modifying, backing up, and loading a database used in an EMS.

delete

Another object of the present invention is a method for easily modifying, backing up, and loading an EMS database by converting the database stored in the form of a binary file inside the EMS into a script file having an ASCII form by external control. In providing.

Another object of the present invention is to process the modified database to be applied to all the systems required by modifying the database of one EMS to a database commonly applied between all systems or some systems when at least one EMS works in conjunction To provide a way to.

delete

delete

delete

delete

delete

delete

delete

delete

The present invention for achieving the above object is connected to a console terminal (Console Terminal) having a transmission module for transmitting and receiving data through a network and a transmission module for transmitting and receiving data with the outside, in response to a command received by the transmission module A method for customizing a database of an embedded system that operates the system with an agent module that performs a function corresponding to the command, and a file storage module that stores a database and data file configured with maintenance and operation information. The method according to claim 1, wherein the agent module converts the database stored as a binary data file into a text file in response to a script file generation command provided from the console terminal, and stores the database in a text file. Step 1, and the agent A second process of the module transmitting a script file stored in the internal memory area to the console terminal, and the agent module storing the received script file in response to receiving a modified script file and a database recovery command from the console terminal. The database is loaded into a memory area and restored to a binary data file to recover the database, and the received script file includes a third process of modifying the console terminal. A transmission module connected to the console terminal having a transmission module for transmitting and receiving data through the network, an agent module for transmitting and receiving data through the network, an agent module performing a function corresponding to the command in response to a command received from the transmission module, and maintaining and A database of information about operations and A method of customizing a database of at least one embedded system for operating a system with a file storage module for storing a data file, the agent module modifies an internal database under control of a console terminal connected through the network, and in binary form. The first process of creating a database of the database as an ASCII script file and storing it in the file storage module, and the agent module in response to the input of the copy list of the other embedded system transmitted from the console terminal And a second process of transmitting the stored database script file and the loading recovery command to the embedded system corresponding to the copy list. Hereinafter, a database customization of an EMS according to an exemplary embodiment of the present invention is provided. It will be described in detail with reference to the attached drawings for explanation of the operation. In addition, in describing the present invention, if it is determined that a detailed description of components that are too obvious to those skilled in the art may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. 1 is a network connection state diagram illustrating a connection state between EMSs for explaining a preferred embodiment of the present invention. 1, a console terminal 104 having a data communication interface function and a plurality of EMSs 112, 114 to 114n (where n is an integer such as 1,2,3, etc.) are connected to the network 102. have. This network 102 can be the Internet, and EMS1 112 is connected to a console terminal 108 which is another maintenance terminal capable of direct data communication. Each of the two console terminals 104 and 108 is provided with data transmission modules 106 and 110 for transmitting and receiving commands or data by connecting to the outside, and a plurality of EMSs 112 and 114 to 114n are also shown. Although not provided with the data transmission module.

The console terminals 104, 108 are external computers for managing the EMSs 112, 114-114n, which generate application software (i.e., applications) and databases for the operations of the EMSs 112, 114-114n. Then, the generated application software and database are loaded into the EMSs 112 and 114 to 114n. The data transmission modules 106 and 108 may be used to perform such a function, and the data transmission modules 106 and 108 may use a communication module such as a telnet or an FTP module.

delete

2 is a block diagram of an EMS for explaining a preferred embodiment according to the present invention. 1 and 2, the illustrated EMS includes a transport module 116, an agent module 118, a database module 120, and a file storage module 122. The transport module 116 includes a network 102. Or the console terminal 108 to transmit and receive commands and data. The agent module 118 performs a function corresponding to the received command in response to a command received from the outside through the transmission module 116. The module 120 has application software and a database designed for a specific purpose. The file storage module 122 stores a file under the control of the agent module 118.

The EMS configured as described above operates by receiving an external application software and a database. At this time, the database may be generated by itself without being loaded from the outside, and such a database is called a default database. Also, a database modified during operation of the system is called an operation database, and these default databases and operation databases are stored in the database module 120.

3 is a flowchart illustrating a database customization process operated by an EMS according to an exemplary embodiment of the present invention. 3 illustrates a control process between a maintenance terminal (MAS) and EMS1 112 and EMS2 114. At this time, the maintenance terminal represents the console terminal of FIG.

Hereinafter, a method for customizing a database of EMSs according to an exemplary embodiment of the present invention will be described with reference to FIGS. 1 through 3, in steps S302 to S322, by connecting the console terminal 104 and EMS1 112 shown in FIG. 1. Shows database customization process.

When a system user inputs a connection command of EMS1 112 using an external keyboard to back up, modify, and restore a database inside EMS1 112 through the console terminal 104, the console terminal 104 enters EMS1 ( 112) is connected to enable data transmission and reception (S302). Such a connection can be easily connected using telnet or FTP and is well known in the art.

The console terminal 104 connected to the EMS1 112 backs up the operation database or the default database operating in the EMS1 112 in response to a user's request, and then generates and transfers a script file of the database to modify the database. Is transmitted to the EMS1 112 (S304). The script file generation command and the transfer command are input to the agent module 118 through the transfer module 116 in the EMS1 112.

Agent module 118 of EMS1 (112) transmits a signal in response to the script file generation command and the transfer command to the console terminal 104 (S306), the database in the form of binary data stored in the database module 120 Converts to an ASCII script file and stores it in the file storage module 122 (S308). Since the database script file stored in the file storage module 122 is in the form of an ASCII file, a user can easily modify it with a general text editor without having a separate software tool. Because ASCII files are text files that are not binary files consisting of 0s and 1s, and are text files that contain text, numbers, and symbols of human readable language. to be. The agent module 118 transmits the database script file (that is, the database converted into the ASCII file) stored in the file storage module 122 to the external console terminal 104 (S310). This is for backup of database script files. The console terminal 104 may directly back up the script file or may use a file transfer protocol such as FTP. When the console terminal 104 receives the database script file from the EMS1 112, the console terminal 104 terminates the connection by blocking a data communication path with the EMS1 112 (S320). The console terminal 104 requests the user's database. Modify the script file and store it in the internal memory area (S322). The database script file backed up from the EMS1 112 is simply used for backup purposes, but the user can directly modify the database and apply it to the EMS. At this time, since the database script file is a simple ASCII file, it can be easily modified with a general text editor (for example, notepad).

delete

delete

By loading the database scripter file backed up from one EMS to the other EMS by the above process, the database running in the EMS can be easily copied to another system.

The console terminal 104 is connected to the EMS1 via the network 102 of the Internet by driving the transmission module 106 to load the modified database script file into the EMS1 or the EMS2 in response to a user's request (S324). It is connected to the EMS2 (114) (S326). In an embodiment of the present invention, another EMS connected to the console terminal 104 is limited to EMS1 112 and EMS2 114, but connection with a plurality of EMSs is also possible. The console terminal 104 transmits the modified database script file stored in the internal memory area to the connected EMS1 112 (S328). At this time, the console terminal 104 restores the modified database script file stored in the file storage module 122 and the command to save the modified database script file in the file storage module 122 to the default database and the operation database. The EMS1 112 receives the modified database script file, stores it in the file storage module 122, loads it, converts it into a binary database, and restores the default database and the operation database. (S330). EMS1 112 also stores the recovered databases in database module 120. Similarly, if console terminal 104 transmits the modified database script file stored in an internal memory area to connected EMS2 114 (S332). After receiving and storing the modified database script file, EMS2 114 restores the default database and the operation database by loading the modified database script file (S334). The console terminal 104 blocks the connection with the EMS1 112 and the EMS2 114 after the modified database script file transfer is completed (S336, S338).

As described above, the present invention converts the binary database in the EMS into an ASCII script file so that the user can process the ASCII script file, even though the user does not use professional knowledge and a separate editing tool. You can easily manage the database of EMS.

4 is a flowchart illustrating an operation database up-date control of EMSs according to an exemplary embodiment of the present invention. FIG. 4 illustrates a process of modifying a database once to apply a modified database to all necessary systems when a plurality of EMSs operate in a network and interwork with all systems or some systems. 1, 2 and 4, the console terminal 104 is connected to the EMS1 112 in order to transmit and receive data in response to the user's connection request (S402). Such a connection can be easily connected using Telnet or FTP as described above. The console terminal 104 transmits a database modification editing command to the EMS1 112 in response to a user's request (S404). The agent module 118 of the EMS1 112 transmits the database of the database module 120 to the console terminal 104 through the transmission module 116 in response to the correction editing command (S405). The console terminal 104 modifies the database in response to the user's request (S408). More preferably, as described above in the process of FIG. 3, the script file generation command of the database may be transmitted to receive and modify the script file converted into the ASCII form. Console terminal 104 generates a list of other EMS to copy the database by the user's selection and transmits to the EMS1 (112) (S410). Here, the list of EMSs is information such as the IP address of the EMSs and information for connecting other EMSs connected on the network 102. EMS1 112 stores the EMS list received from console terminal 104 (S412). Console terminal 104 modifies the database received from EMS1 112, and sends the modified database to EMS1 112. (S414). At this time, the console terminal 104 preferably transmits the script file generation command to the EMS1 112. The agent module 118 in the EMS1 112 receives the modified database and generates the script file. In response to the command, the modified database is generated as an ASCII script file and stored in the file storage module 122 (S416). The agent module 118 of the EMS1 112 stores the EMS list stored in the process S412. By referring to the list, it forms a communication path with EMSi 130 and EMSj 140 (where i, j are integers such as 1,2,3, etc.) in the list, and stores the database script file stored in the file storage module 122. The transmission is transmitted to the EMSi 130 and the EMSj 140, respectively (S418 and S420). At this time, the EMS1 112 transmits not only the database script file to the EMSi 130 and the EMSj 140, but also a storage and recovery command of the database script file. If the EMS1 112 does not transmit all the database script files for the EMSs in the EMS list, the EMS1 112 repeats the process of transmitting the database script files and transmits the database script files to all the EMSs in the EMS list. EMSi 130 and EMSj 140 store the received database script file (that is, the modified database), and load the database script file to recover the existing database (S419, S421). In this case, the recovery process is as described above with reference to FIG. 3. The agent module 118 of the EMS1 112 transmits a result report indicating that the database script file transfer is completed to the console terminal 104 (S422). If the result report is received, 104 ends the connection with the EMS1 (S424). It is to be understood that the foregoing description and the accompanying drawings are intended to represent the preferred embodiments of the invention only. It should be apparent to those skilled in the art that various modifications and variations of the present invention are apparent without departing from the scope and spirit of the invention as set forth in the appended claims.

delete

delete

delete

delete

delete

As described above, the present invention converts a database of binary codes in an embedded system into an ASCII script file with a simple configuration, thereby allowing a user to easily backup, modify, and load the database without a separate tool. This has the advantage of not having to use a separate tool to modify the database. In addition, when multiple embedded systems connected to the network operate in conjunction, the database of one embedded system is converted into an ASCII script file and modified, and the embedded system modified with the database is modified to multiple embedded systems connected to the network. By sending a database to modify the database of all embedded systems collectively, users can easily manage multiple embedded systems.

1 is a network connection state diagram showing a connection state between embedded systems for explaining a preferred embodiment according to the present invention.

Figure 2 is a block diagram of an embedded system for explaining a preferred embodiment according to the present invention.

3 is a flowchart illustrating a database customization process operated by an embedded system according to an exemplary embodiment of the present invention.

4 is a flow chart of up-date control of operating database of embedded systems according to an exemplary embodiment of the present invention.

<Code Description of Main Parts of Drawing>

102: network, 104, 108: maintenance terminal,

106,110: transmission module, 112, 114: embedded system

Claims (8)

An agent that is connected to a console terminal having a transmission module for transmitting and receiving data through a network, the transmission module for transmitting and receiving data with the outside, and an agent that performs a function corresponding to the command in response to a command received by the transmission module. In the database customization method of the embedded system to operate the system with a module, a file storage module for storing a database and data files consisting of information on maintenance and operation, A first process of the agent module converting the database stored as a binary data file into a text file in response to a script file generation command provided from the console terminal and storing the database in a text file in the internal memory area of the file storage module; , Transmitting, by the agent module, a script file stored in the internal memory area to the console terminal; The agent module loads the received script file into the internal memory area in response to receiving a modified script file and a database recovery command from the console terminal, restores the database to a binary data file, and restores the database. The received script file includes a third process of modifying at the console terminal. delete delete The method of claim 1, wherein the third process is And restoring the database to a default state by restoring the script file loaded in the internal memory area into a binary data file. delete A transmission module connected to a console terminal having a transmission module for transmitting and receiving data through a network, and a transmission module for transmitting and receiving data through the network, an agent module performing a function corresponding to the command in response to a command received from the transmission module; In the database customization method of at least one embedded system for operating the system with a file storage module for storing a database and data file consisting of information on maintenance and operation, The first step of the agent module to modify the internal database under the control of the console terminal connected through the network, to generate a binary database as an ASCII database script file and to store it in the file storage module and, And the second step of the agent module transmitting the stored database script file and the loading recovery command to the embedded system corresponding to the copy list in response to the input of the copy list of the other embedded system transmitted from the console terminal. Database customization method for embedded systems. delete delete