KR20020090512A - Method for processing circular import definition error of asn.1 compiler - Google Patents

Abstract

PURPOSE: A method for processing an error in a circular import definition of an ASN(Abstract Syntax Notation).1 compiler is provided to satisfactorily perform the generation of the object files of a call processing program by solving the error in the circular import definition when compiling an RRC.asn(Radio Resource Control.Abstract Syntax Notation) by using the ASN.1 compiler and a C compiler and to make a user generate an RRC message by the ASN.1. CONSTITUTION: When compiling the RRC.asn into an object file by using a work station of an UNIX environment, the ASN.1 compiler compiles the RRC.asn as a protocol standard related with the call processing and generates the header files of respective program modules and the C-coded files of the program modules(S100). The ASN.1 compiler generates a unified header file by using the header files of the program modules(S200). The C compiler generates an 'RRCASN.o' object file including the object files of the modules by compiling the unified header file(S300).

Description

How to handle cross reference definition error in ASSN.1 compiler {METHOD FOR PROCESSING CIRCULAR IMPORT DEFINITION ERROR OF ASN.1 COMPILER}

The present invention relates to a method of processing an Abstract Syntax Notation (ASN) .1 Compiler for a Circular Import definition error, and more particularly, to RRC.asn (the protocol specification of the third generation asynchronous system). A method for handling cross-reference definition errors of the AS.1 compiler that solves cross-reference definition errors when compiling Radio Resource Control.Abstract Syntax Notation) using the ASN.1 compiler and the C compiler.

As is well known, RRC.asn refers to a protocol specification related to call processing of 3rd generation asynchronous systems. Call processing related program modules are generated when compiled through ASN.1 compiler and C compiler.

The general RRC.asn program code compilation device was composed of a workstation 100 having an ASN.1 compiler 101 and a C compiler 102 under a Unix environment, as shown in FIG.

In this case, a method of compiling a conventional RRC.asn program code using the above-described general RRC.asn program code compilation device will be described with reference to FIGS. 1 and 2 as follows.

First, the ASN.1 compiler 101 receives and compiles RRC.asn, which is a protocol of call processing related protocol of 3rd generation asynchronous system, and compiles header files (* .h) for each program module and each program module. Generate files (* .c) coded in the star C language (S1). Here, each program module refers to call processing programs defined by RRC.asn, which is a call processing protocol standard, and includes, for example, a CN network module (CoreNetwork-IEs Module) and a terminal processing module (UserEquipment-IEs Module).

Thereafter, the C compiler 102 inputs header files (* .h) for each program module compiled by the ASN.1 compiler 101 and C coded files (* .c) for each program module. Receives and compiles each object file (RRCASN.o) to generate (S2).

At this time, the call processing program object file (RRCASN.o) generated by the second step S2 is downloaded to the call processing processor in the RNC (Radio Network Controller) of the third generation asynchronous system to perform call processing. do.

However, the above-described method of compiling the RRC.asn program code using the ASSN.1 compiler is encoded in the C files for each program module and header files (* .h) generated for each program module using the ASN.1 compiler. Cross-reference definition error occurs when compiling files (* .c) using C compiler. In this case, the cross-reference definition error occurs because, for example, the CN processing module in RRC.asn includes data defined in the terminal processing module and the terminal processing module includes data defined in the CN processing module. do. That is, when compiling each module using the ASN.1 compiler, the header file generated by the CN processing module includes the header file generated by the terminal processing module, and the header file generated by the terminal processing module is generated by the CN processing module. The inclusion of header files causes problems when compiling these header files with the C compiler.

Therefore, due to the above-described problem, C compilation is not progressed anymore, and thus the call processing program object file (RRCASN.o) cannot be generated, and thus, call processing related software of the third generation asynchronous system cannot be generated.

Accordingly, the present invention has been made to solve the above-mentioned problems, and an object of the present invention is to define a cross-reference when compiling RRC.asn, which is a protocol specification of a third generation asynchronous system, using the ASN.1 compiler and the C compiler. By solving the error, the object file of the call processing program can be created smoothly, and the AS.1 compiler's cross-reference definition error handling method can be used to allow the user to generate RRC messages by ASN.1. To provide.

In order to achieve the above object, the cross-reference definition error processing method of the present invention's AS.1 compiler uses RSN.asn as an object file by using the workstation 100 of the UNIX environment having the ASN.1 compiler and the C compiler. How to handle cross-reference definition errors when compiling with (RRCASN.o)

Step 100, the ASN.1 compiler compiles RRC.asn, a call processing related protocol standard, to generate header files (* .h) for each program module and C-coded files (* .c) for each program module ;

A step 200 of generating, by the ASN.1 compiler, an integrated header file using header files (* .h) for each program module; And

The C compiler compiles the integrated header file to generate a 'RRCASN.o' object file including an object file for each module.

1 is a view showing the configuration of a general RRC.asn program code compilation device,

2 is an operation flowchart showing a method of compiling RRC.asn program code using a conventional AS.1 compiler;

3 is an operation flowchart illustrating a cross-reference definition error processing method of an AS.1 compiler according to an embodiment of the present invention;

4 is an operation flowchart showing a detailed operation of step 200 (S200) in the cross-reference definition error processing method of the AS.1 compiler according to FIG. 3;

FIG. 5 is an operation flowchart showing a detailed operation of step 250 (S250) in the cross-reference definition error processing method of the ASCII compiler according to FIG. 4;

FIG. 6 is a reference diagram for explaining a cross-reference definition error processing method of the ASCII compiler according to FIG. 3. FIG.

<Explanation of symbols for the main parts of the drawings>

100: Workstation 101: ASN.1 Compiler

102: C compiler

Hereinafter, a method of processing cross-reference definition error of an AS.1 compiler according to an embodiment of the present invention will be described in detail by using the general RRC.asn program code compilation device shown in FIG. The description of the asn program code compilation device has been already described in the related art, and thus will be omitted.

3 is an operation flowchart illustrating a cross-reference definition error processing method of an AS.1 compiler according to an embodiment of the present invention.

First, the ASN.1 compiler 101 compiles the RRC.asn code, which is a call processing protocol standard, for each program module header files (* .h) and C program files for each program module (* .c). Generate them (S100).

Thereafter, the ASN.1 compiler 101 generates an integrated header file using header files (* .h) for each program module (S200).

Hereinafter, a detailed operation process of the above-described second step S200 will be described with reference to FIGS. 4 and 6.

First, as shown in FIG. 6, the ASN.1 compiler 101 sorts each header file in ascending order (S210), and then assigns an integer index to each header file, and then internal data of each header file. The data is generated using import data inside the module and a sub-index of each internal data is designated (S220). In FIG. 6, 'Index [i] [j]' means an integer index of each header file, and 'sub_Index [m] [n]' means a sub index within an integer index of each header file. In this case, 'i' in 'Index [i] [j]' means the number of internal data for each header file, and 'j' means indexes for header files having the same 'i' value.

Thereafter, the ASN.1 compiler 101 checks the sub-indexes of the aligned header files and the internal data to determine whether there is a cross-reference definition error (S230). Here, if there is a cross-reference definition error between each header file, the same as in FIG. 6 (b), and the internal data of 'Index [1] [0]' is' sub_Index [3] [1] 'and' Index [ 3] Internal data of header file whose internal data of [1] 'is' sub_Index [1] [0]', that is, header file with 'Index [1] [0]' is' Index [3] [1] ' This refers to a case where a cross-cyclic reference phenomenon occurs because the header file including the data and the header file with 'Index [3] [1]' includes internal data of the header file with 'Index [1] [0]'.

At this time, if there is no cross-reference definition error as shown in (a) of FIG. 6 in step S230 (NO) (NO), the ASN.1 compiler 101 duplicates among internal data of the respective header files. The internal data are deleted and attached to each header file to be integrated (S240). Here, the ASN.1 compiler 101 attaches each header file by attaching a header file having a small index value to the front of the header file having a large index value.

On the other hand, if there is a cross-reference definition error as shown in (b) of FIG. 6 in step 230 (Y230) (YES), the ASN.1 compiler 101 corrects the errors of the header files in which the cross-reference definition has occurred. At the same time, duplicated internal data are deleted, and each header file is attached and integrated (S250).

Hereinafter, a detailed operation process of the above-described 250th step S250 will be described with reference to FIGS. 5 and 6.

First, the ASN.1 compiler 101 attaches a header file having a small index value to a header file having a large index value among header files in which a cross-reference definition error occurs (S231). Referring to FIG. 6B, the header file of 'Index [1] [0]' is attached to the front of the header file of 'Index [3] [1]'.

Then, the ASN.1 compiler 101 determines the information element (IE) of the header file of 'Index [1] [0]' and the header file of 'Index [3] [1]' where a cross-reference definition error occurred. Rearrange (S232). The reason for this is to solve dependencies for each information element (IE) between two header files. In this case, the information element (IE) means attribute information of internal data in two header files. The definition must first be called before the information element is called.

Subsequently, the ASN.1 compiler 101 redefines the attach flag of the header file in which the cross-reference definition error occurs (S233). Here, the attach flag defined in each header file represents the number of internal data in the header file to which the attachment has been progressed, and the final integration requires that the number of internal data in each header file should be one until the final integration is achieved. You need to update the attach flag continuously.

Thereafter, the ASN.1 compiler 101 redefines the sub index of the attached header index while deleting the sub index of the duplicated internal data in the two header files (S234).

Subsequently, the ASN.1 compiler 101 replaces indices having sub-indexes of the attached header files among the integrated header files with indexes of the attached header files to reconstruct the indexes of the header files (S235). In other words, the same indexes as the sub-indexes of the attached header files among the sub-indexes in the other header files are changed to the indexes of the attached header files.

Then, the ASN.1 compiler 101 determines whether there are other header files for which a cross-reference definition error has occurred (S236).

At this time, if there are other header files for which a cross-reference definition error has occurred in step 236 (SES) (YES), the ASN.1 compiler 101 proceeds to step 231 (S231) and exists. If not (NO), the duplicate internal data are deleted and attached to each header file to be integrated (S237).

On the other hand, after the 200th step (S200), the C compiler 102 compiles the integrated header file to generate an 'RRCASN.o' object file containing the object file for each module (S300).

As described above, according to the method of processing cross-reference definition error of the AS.1 compiler according to the present invention, a cross-reference definition error is generated when compiling RRC.asn, which is a protocol standard of a third generation asynchronous system, using the ASN.1 compiler and the C compiler. By solving the problem, it not only facilitates the creation of the object files of the call processing program, but also has the excellent effect of allowing the user to generate the RRC message by ASN.1.

Claims (5)

In a method for handling cross-reference definition errors when compiling RRC.asn into an object file (RRCASN.o) using a workstation 100 in a Unix environment with an ASN.1 compiler and a C compiler, Step 100, the ASN.1 compiler compiles RRC.asn, a call processing related protocol standard, to generate header files (* .h) for each program module and C-coded files (* .c) for each program module ; A step 200 of generating, by the ASN.1 compiler, an integrated header file using header files (* .h) for each program module; And The C compiler compiles an integrated header file and generates a 'RRCASN.o' object file including an object file for each module. . The method of claim 1, The 200 step may include: a 210 step of the ASN.1 compiler sorting each header file in ascending order; A step 220 in which the ASN.1 compiler assigns an integer index to each header file, and then generates internal data of each header file using import data in a corresponding module, and simultaneously designates a sub-index of each internal data; Step 230, wherein the ASN.1 compiler checks sub-indexes of aligned header files and internal data to determine whether a cross-reference definition error exists; And If there is no cross-reference definition error in step 230, the ASN.1 compiler includes step 240 of attaching and integrating header files while deleting duplicate internal data. How to handle cross-reference definition errors. The method of claim 2, The method of attaching the header files by the ASN.1 compiler in step 240 may include attaching a header file having a small index value to the front of the header file having a large index value. How to handle reference definition errors. The method of claim 2, If there is a cross-reference definition error in step 230, the ASN.1 compiler corrects the errors of the header files for which the cross-reference definition has occurred, and simultaneously attaches and integrates the respective header files while deleting duplicate internal data. A method for handling cross-reference definition errors of an AS.1 compiler, further comprising step 250. The method of claim 4, wherein In step 250, the ASN.1 compiler attaches a header file having a small index value to a header file having a large index value among header files having a cross-reference definition error; Step 232, wherein the ASN.1 compiler rearranges information elements (IE) of header files in which a cross-reference definition error occurs; Step 233, wherein the ASN.1 compiler redefines attach flags of header files in which a cross-reference definition error occurs; Step 234, the ASN.1 compiler redefining the sub index of the attached header index while deleting the sub index of duplicate internal data; Step 235, the ASN.1 compiler reconstructing the indexes of the header files by replacing the indexes having sub-indexes of the attached header files with the indexes of the attached header files; Step 236, the ASN.1 compiler determining whether there are other header files in which a cross-reference definition error has occurred; And If there are other header files for which a cross-reference definition error has occurred in step 236, the ASN.1 compiler proceeds to step 231, and if none exists, attaches the respective header files while deleting duplicate internal data. A method for processing cross-reference definition errors of an AS.1 compiler, comprising: step 237;