KR0121310B1 - Software package generating method of base station in mobile communication system - Google Patents

Abstract

The software package generating method of base station in mobile communication system provides features of: managing software generally by each version; generating software packages to make each library files, header files, database-related files, static data(PLD) files, geometry last files and package files be managed by each independent directory. Therefore, by subdividing directories with their features, efficient general software management is possible.

Description

Software Package Generating Method of Base Station in Mobile Communication System

1 is a structural diagram of a mobile communication system base station comprehensive software of FIG.

2 is a flowchart of a software package generation method in a mobile communication system base station according to the present invention.

The present invention relates to a method for generating a software package, and more particularly, to a method for generating a base station software package of a mobile communication system.

In the mobile communication system base station (hereinafter, the base station is composed of three subsystems of a base transceiver subsystem, a control station (base station controller subsystem) and an operating station (base station controller subsystem), a plurality of blocks are provided. Since the software is composed of several types, there are many kinds of source programs related to each block, library files related to the source programs, and a plurality of executable files that execute code the source programs.

However, in the past, a software project was managed without a certain management principle such as managing this in one directory, managing source files in each directory, and managing only executable files in a common directory.

First of all, when multiple versions are generated, when the relevant modules are subjected to a comprehensive system test or distributed as a package, versions may differ between different blocks, causing errors in system operation.

Second, by managing the common data files in a single directory, when a new version occurs, you have no choice but to manage the version in a coarse way.

Third, various files can be mixed without any distinction, which can cause a lot of inconvenience and confusion for developers or general managers.

Accordingly, an object of the present invention is to provide a method for generating a software package that enables efficient total software management by allowing respective programs to be separated by characteristics in generating a mobile communication system base station software package.

In order to achieve the above object, the present invention provides a first step of creating a common data file and rejecting a file header of another developer while rejecting a file editing function of another developer using a tool called comvi (1); A second method of verifying a file error using a tool called ckdb (2) to titrate various relation data schema definition files and registering the file in a common relation definition directory (db) using a tool called srcreg (4). step; a third step of creating a relation data file while verifying a file error using a tool called ckdg (3), and registering the file in a common relation data directory dg using a tool called srcreg (4); A fourth step of generating, by a tool called relcg (5), a relation data header file used for each block by using the relation data schema definition file registered in the db directory in the second step; The DB schema file and the DB source file are generated by executing a tool called mkdg (6) by inputting relation data files registered in the db and dg directories in the second and third steps, respectively, and mkpld (7 A fifth step of generating a static data (PLD) by using a tool called) to register static data (PLD), registering it in a pkg directory which is a package directory, and releasing it to a target system; Create and compile block source file in common block source directory (src) using srcreg (4) tool, and make Makefile input file for source program and compile using tool called kcsmf (10). Step 6; A seventh step of creating a library file, compiling it into a library file, and registering it in a common library directory (lib) using the srcreg (4) tool; Compiles all block source files to generate block-specific executables, and registers the generated executables in a directory (pkg) and releases them to the target system.

Hereinafter, with reference to the accompanying drawings will be described an embodiment of the present invention;

1 is a structural diagram of a mobile communication system base station comprehensive software.

Since the mobile communication system base station software is a large software, there is a common library or common data files and block source files in one version.

Thus, the comprehensive management version manages the comprehensive software for each version, but manages library files, header files, database related files, static data (PLD) files, formation list files, and package files in separate directories.

In relation to FIG. 1, the directory version consists of nine directories.

The lib directory consists of various library files created by developers and link-related files managed by versions.

Software data of mobile communication system base station is classified into static data determined according to installation system and capacity and dynamic data generated dynamically during operation. Among them, static data is different from other data because different data are installed in each system. It is called PLD (Program Loading Data) because it loads the data directly to the target system.

However, this type of PLD is loaded directly into the system, and also needs to be referenced in each block program, so two types are required.

PLD-related data can be separated only by data type and data value. Both PLDs need it, and block programs only need the data type for data references.

However, not every data type is required in each block program, only a partial data type required for each block execution is called relation data.

Therefore, if PLD related data is managed separately from data type and data value, comprehensive management of base station software can be simplified.

By receiving the static data type and the static data value separately from each other and generating the PLD and the block relation data type using software development tools, the indetermination between the two data will be guaranteed.

Among the data related to such PLD, relation schema definition files are managed in the db directory, and the relation data values to be entered are managed in the dg directory.

PLD is created by executing software tool with relation data schema definition file in db directory and relation data value managed in dg directory, and many intermediate files are generated during execution.

So the directory that creates the PLD is managed separately from the dgpool directory.

The include directory consists of all data header files that are referred to block by block or system unit in each block, but includes message-related header files used for communication between different blocks that frequently occur in a communication system, and when referring to a PLD. There is a relation data header file to use.

So the message header file and the relation data header file are configured in include / msg and include / rel, respectively.

In the src directory, a directory is created for each block to manage source programs in block units so that the general manager compiles in the src directory, and the library sources created by the developer are also managed in the libsrc directory in src.

In the conf directory, the shape list of each block is created in a file so that it can be used for reference related to the whole shape.In the pkg directory, each block generated by executing the compiler in the src directory and the PLD created in dgpool To create a package.

The work directory is used for work in testing all temporary files or software development tools in the overall management.

2 is a flowchart of a software package generation method in a mobile communication system base station according to the present invention.

Comprehensive management of mobile communication system control station software is composed of the above-described overall software structure, and the software package is produced in the workflow as shown in FIG.

Software developers and general managers develop software using the following procedures.

Developers write various common data files for use during development. Integrity is important because files are commonly referred to by several subsystems or blocks.

That is, since a developer who edits a common file must reject the file editing function of another developer, the CMS (CDMA Mobile System) base station software implements this function using a tool called comvi (1).

A developer creates various relation data schema definition files based on PLD static data and creates relation data files in parallel with common data file creation, and verifies the error of the file using ckdb (2) and ckdg (3) tools. And register it in the comprehensive directory using a tool called srcreg (4).

Once the common files have been registered, the super administrator uses the tool relcg (5) to create relation data header files for each block using the relation data schema definition file registered in the db directory. Create a DB schema file and a DB source file by executing a tool called mkdg (6) with the registered relation data file as input.

The mkpld (7) tool is used to run the compiler to generate (8) the PLD, register it in the pkg directory, which is a package directory (13), and release it on the target system.

The developer develops a source program related to each block including various generated header files, and the library library function can be compiled (9) and made into a library file by using the srcreg (4) tool. Once registered, other developers develop block source programs by referencing their available libraries in the lib directory.

After compiling the block source program and performing unit tests on the target system, the developer uses the srcreg (4) tool to generate Makefile input files for the source program and compile using the tool kcsmf (10). Compile (11) to generate an executable file for each block (12), register the generated executable file (13) in the pkg directory, release (13) the target system, and perform a comprehensive test.

As described above, the PLD-related data can be divided into data types and data values, thereby allowing referencing of different paths while maintaining integrity. Therefore, a program developer can access two types of data with a single input operation. It can be effective.

In addition, by separating each common file into a version unit, a general data type definition file, a message file, and a PLD related data type file, the developer's approach becomes clear and it is possible to clarify the version problem that occurs during the comprehensive system test.

In addition, by managing each software by its characteristics, it can be localized when problems occur during development, and the general manager can simplify the representation of the shape and save package production time.

Mobile communication system base station software project As a whole, it is possible to contribute to shorter development period by enabling more efficient project management during software development.

Claims (1)

In the method of generating a mobile communication system base station software package, a first step of creating a common data file and rejecting the file editing function of another developer using a tool called comvi (1) and registering it in a common header file directory (include) s1, s2); A second method of creating various relation data schema definition files while verifying file errors using a tool called ckdb (2), and registering these files in a common relation definition directory (db) using a tool called srcreg (4). Steps s3 and s4; The third step (s5, s5,) is to create a relation data file while verifying a file error using a tool called ckdg (3), and register the file in a common relation data directory (db) using a tool called srcreg (4). s6); A fourth step (s7) of generating, using a tool called relcg (5), a relation data header file used for each block by using the relation data schema definition file registered in the db directory in the second step; The database schema file and the database source file are generated by executing mkdg (6) by inputting relation data files registered in the db and dg directories in the second and third steps, respectively. A fifth step (s8, s9, s10) of driving a compiler using a tool (7) to generate static data (PLD), registering in a pkg directory as a package directory, and releasing it to a target system; Create and compile block source files in common block source directory (src) using srcreg (4) tool, and create Makefile input file for source program and compilation using kcsmf (10) tool. 6 steps (s11, s12, s13, s14); A seventh step (s15, s12, s, 16) of creating a library file, compiling it into a library file, and registering it in a common library directory lib using the srcreg (4) tool; Compiles all block source files to generate block-specific executable files, and registers the generated executable files in a directory (pkg), and performs a sixth step (s17, s18) to release to the target system How to create.