KR20000038495A - Method for automatically producing sib application program used by ain - Google Patents

Abstract

PURPOSE: A method for automatically producing SIB application program used by AIN is provided so that a user can produce SIB application code by providing form based graphic interface. CONSTITUTION: A method for automatically producing SIB(Service Independent Building Block) application program used by AIN(Advanced Intelligent Network) includes several steps. A first step is to input SIB name for developing and in a second step, the information of SIB for developing receives and stores to the inside storage unit. If the input request for producing code exists, in a third step, SIB program code is automatically produced by using the stored value.

Description

Automatic generation method of SIB application program used in advanced intelligent network service creation environment

The present invention relates to a method for automatically generating a service independent building block (SIB) application used in an advanced intelligent network (AIN) service development environment, and in particular, a development time, a development cost, and a development effort of an SIB application. SIB application to reduce the cost of maintaining and maintaining the SIB application by reducing the cost, reducing the cost of maintaining and maintaining the SIB application by making it easier for end users who do not have the knowledge of intelligent networks and programming. A method for automatically generating a program

In the conventional intelligent network service development environment, a method for developing an SIB application requires a lot of development time, development cost, and development effort because a developer must code directly in a programming language such as C. In addition, only experts with expertise in intelligent networks and programming expertise could develop new SIBs. In addition, the SIB codes developed by the developers have a problem in that the cost of maintaining the SIB application is high because the structure is not uniform.

The present invention has been made to solve the problems of the prior art as described above, provides a form-based graphical interface that allows the user to enter the information of the SIB parameters, the user is developed using the graphical interface The purpose of the present invention is to provide information on parameters of a SIB to be input, and user input is converted into an internal storage format and stored, and to provide a method of automatically generating SIB application code using the stored values.

1 is an explanatory diagram showing an intelligent network service development environment to which the present invention is applied;

FIG. 2 is an explanatory diagram showing an operation model of the creation environment shown in FIG. 1;

3 is an explanatory diagram showing a structure of an automatic SIB application generator according to an embodiment of the present invention;

4 is a flowchart illustrating the overall flow of a method for automatically generating a SIB application program according to an embodiment of the present invention;

5 is a flowchart illustrating a SIB input data parameter definition method according to an embodiment of the present invention;

6 is a flowchart illustrating a method of defining an SIB input IPC parameter according to an embodiment of the present invention;

7 is a flowchart illustrating a SIB output data parameter definition method according to an embodiment of the present invention;

8 is a flowchart illustrating a SIB output IPC parameter definition method according to an embodiment of the present invention;

9 is a structural diagram showing a data structure for storing one user-defined SIB parameter in an internal storage according to an embodiment of the present invention;

10 is a structural diagram showing a data structure for storing a user-defined parameter set for each SIB type according to an embodiment of the present invention in an internal storage;

11 is a flowchart illustrating a resource file generation method according to an embodiment of the present invention;

12 is a flowchart illustrating a header file generation method according to an embodiment of the present invention;

13 is a flowchart illustrating a method of generating an implementation file according to an embodiment of the present invention.

According to the present invention for achieving the object as described above, in the method for automatically generating a Service Independent Building Block (SIB) application used in the next generation Advanced Network (AIN: Advanced Intelligent Network) service development environment, A first step of inputting a name of S-Ivy to be desired; A second process of receiving information of an SIB parameter to be developed and storing in an internal storage; A third step of automatically generating an SIB application code corresponding to a name of an SIB to be developed in the first step, using a value stored in the internal storage in the second step, if there is a code generation request input; Provided is a method for automatically generating an S Ivy application, characterized in that consisting of.

In addition, a computer-readable recording medium that records a program that can execute a method of automatically generating a service independent building block (SIB) application used in an advanced intelligent network (AIN) service development environment. A first process of inputting the name of the S-Ivy to be developed; A second process of receiving information of an SIB parameter to be developed and storing in an internal storage; A third step of inputting a parameter name, a parameter category and a data type in the internal storage when the SIB parameter input in the second step is an input data parameter; A fourth step of determining whether the data type stored in the third step is an enumerated data type; A fifth step of receiving an item corresponding to the enumerated type and storing it in an internal storage if the data type is an enumerated type and ending if the data type is not an enumerated type; A sixth step of inputting an IPC type and an IPC name after storing the inputted IC parameter in the second step, the IPC type and the IPC name; A seventh process of inputting a name and data type of an IPD (Inter Process Data) and storing the data in an internal storage; An eighth step of inputting a parameter name and a data type and storing it in an internal storage when the S-I parameter input in the second step is an output data parameter; A ninth process of inputting an IPC type and an IPC name and storing it in an internal storage when the S-I parameter input in the second process is an output IPC (Inter Process Communication) parameter; A tenth step of inputting a name and a data type of an IPD (Inter Process Data) and storing it in an internal storage; If there is a code generation input, a computer-readable recording medium having recorded thereon a program capable of executing an eleventh process of generating a resource file, a header file, and an implementation file is provided.

Also, a resource element area for generating a resource file in order to automatically generate an Sivy application program defined by a user on a computer; And a header and an implementation element area for generating a header file and an implementation file. A computer-readable recording medium having recorded thereon an S-I parameter is provided.

Further, more preferably, the resource element area is a resource type field used to determine which resource to express when a parameter is expressed in a parameter editor of an SIB application to be automatically generated, and a resource name indicating a resource name. Field, a resource identifier field indicating a unique value for identifying a resource, a starting position field indicating a starting position at which the resource is to be output, a width field indicating a width of the resource, and a resource characteristic field indicating a dependent characteristic of the resource. and; The header and implementation element areas include a parameter number field indicating how many parameters in a parameter set of a specific parameter type, a parameter category field indicating a category of a parameter, a parameter name field indicating a name of a parameter, and a data type of a parameter value. And a data type field representing the S-I parameter.

In the following, with reference to the accompanying drawings, a preferred embodiment according to the present invention will be described in detail.

The intelligent network service development environment is a kind of CASE (Computer Aided Software Engineering) tool that automatically creates the intelligent network service.

1 is an explanatory diagram of a service development environment (SCE) to which the present invention is applied. The service development environment includes a service specification step, a code generation step, and a service verification step. Steps are called creation environments and service verification steps are called verification environments.

The service specification step specifies a service to be developed as a combination of standardized parts, and a service independent building block (SIB) is most commonly used as a standardized part. SIB is a global viewpoint of intelligent network functions. It is a service-independent and reusable functional block that is being standardized by the International Organization for Standardization (ITU-T). In the service development environment to which the present invention is applied, the SIB is displayed as an icon of a graphic interface, and the user specifies a new service by combining the icons appropriately.

Next, the code generation step automatically converts the SIB combination resulting from the service specification step into a service logic program (SLP). The service logic program refers to service software to be executed on the intelligent network platform.

Finally, the service verification step is performed by running an automatically generated service logic program directly in the simulator or testbed.

FIG. 2 is an explanatory diagram showing an operation model of the generation environment shown in FIG. 1, wherein the generation environment includes a service generation coordinator and an SIB application program, and operates as a client-server model. Here the client becomes the service creation coordinator and the server becomes the SIB application. The client requests the server to perform a specific function, the server performs the requested function and returns the result to the client. At this time, communication between client and server uses COM (Common Object Model), a kind of ORB (Object Request Broker).

When developing a service based on SIB, SIB is a basic unit of service specification and code generation. In addition, the SIB becomes a basic unit when writing or reading a specified service to an external file. Therefore, the SIB application program should include the code for supporting the service specification function, the code generation function, and the function for reading and writing to an external file. If a new SIB is to be developed, such code must be developed.

The SIB code to support the service specification function should include the following functions. When a request from the service creation coordinator is received, it is displayed visually on the screen.When the user inputs a predetermined event by using a mouse, the SIB parameter editor should be displayed on the screen.The user inputs the parameter editor through the parameter storage. Convert it to a format and store it in internal storage such as memory.

In the SIB code for supporting the code generation function, upon receiving a request from the service generation coordinator, the service logic program is automatically generated using the parameter values stored in the internal storage.

In the SIB code to support writing to and reading from an external file, when receiving a request from the service creation coordinator, the parameter value stored in the internal storage is written to the external file or the value read from the external file is converted into the parameter internal storage format. Store in internal storage.

All the above functions should be included in the SIB application program, and the structure of the SIB application program having this function is shown in Table 1 below.

Disclosure property operation open (1) SIB identifier (2) SIB name (3) SIB mode (4) SIB visual properties related attributes-color, shape, size, position, font, font size, title (5) file name-service logic program to be recorded File Name-File name to write SIB information to or read from an external file. (1) Operation to output graphic on screen (2) SIB attribute management operation (3) Service logic program generation operation (4) Operation to write or read SIB information to external file (5) Communication operation Private (1) SIB parameter related attributes- SIB parameter count- Internal data structure to store SIB parameters- SIB parameter editor identifier (1) SIB parameter editing operation- SIB parameter editing output function- Interaction function with user- Function to convert and save user input value into internal storage format (2) Registration and deregistration operation

When the SIB application program having the structure as shown in [Table 1] is to be automatically generated, the SIB parameter related property, SIB parameter editing operation, service logic program generation operation, and operation to write or read SIB information to an external file are different for each SIB. The attributes and operations except for these are the same regardless of the type of SIB. Regardless of the type of SIB, the same properties and operations are easy to create automatically.However, the properties and operations that are different for each SIB require the user to input information about SIB parameters from the user, and automatically generate the SIB application using the user input. do. However, the service logic program generation operation is dependent on the intelligent network platform and cannot be automatically generated using only the user's input to the SIB parameter. Therefore, the service logic program generation operation automatically generates only the appearance (or interface) of the operation at the time of automatic generation, and the content (or body) of the actual operation should be automatically input by the developer to the programming language after the automatic generation.

Every SIB has a parameter, which has an input parameter and an output parameter. The SIB receives an input parameter and performs an SIB function, and then assigns an execution result to an output parameter. SIB parameter types include input data parameters, input IPC parameters, output data parameters, and output IPC parameters.

Input data parameters and output data parameters are required to perform the SIB function, and input IPC parameters and output IPC parameters are necessary for parallel execution between processes. The SIB may have one or more parameters, the parameters belong to one of the four types, the maximum and minimum number of parameters of each type is not limited, and the SIB may have all four types of parameters in some cases, or Or in some cases one, two or three types.

3 is an explanatory diagram showing a structure of an automatic SIB application generator according to an embodiment of the present invention.

The SIB application generator consists of a graphical interface, event handling, type-specific parameter definitions, and code generation.

The graphical interface interacts with the user, and the event handling function interprets the input event and invokes the function corresponding to the event. The type-specific parameter definition function displays the type-specific parameter definition dialog on the screen to interact with the user, and then converts the user's input into an internal storage format and stores it in an internal storage (eg, memory). The code generation feature automatically generates the code for the SIB application using the values stored in internal storage. The code for an autogenerated SIB application includes resource files, implementation files, and header files.

In the automatic generation of the SIB application program of FIG. 3, a user defines a parameter as follows. First select the SIB definition menu from the menu of the graphical interface, and then enter the name of the SIB to be defined (1). The name of the SIB entered by the user is used as the SIB application name to be automatically generated. After entering the SIB name, the user selects the type of parameter to be defined from the menu of the graphical interface (2). The event processing function interprets a user's input event and then calls a parameter definition function corresponding to the input event. The parameter definition function for each type outputs a dialog for inputting one parameter information on the screen (3). The dialog displayed on the screen defines one parameter. If the user wants to define several parameters, the operations (2) and (3) are repeated.

If the user selects an input data parameter in step (2), a dialog box for entering the parameter name, parameter category, and data type of the parameter value is displayed on the screen. In this case, the parameter name is directly input by the user, and the parameter category includes one or more of Service Support Data (SSD), Call Instance Data (CID), and Service Instance Data (SID) recommended in the ITU-T standard. To make a choice. The data type of the parameter value allows the user to select one of an integer data type, a string data type, a boolean data type, and an enumerated data type. After entering the parameter name, parameter category and data type of the parameter value, the user presses the OK button. If the user selects an enumeration type as the data type, a dialog box for inputting the items of the enumeration is displayed on the screen, and the user directly enters the items of the enumeration type and clicks the OK button (4). Then, a dialog is displayed on the screen asking whether to continue defining the enumerated item (5). Here, if the user presses the cancel button, the input data parameter definition is finished. If the user presses the confirm button, the operations (4) and (5) are repeated.

If the user selects the output data parameter in step (2), a dialog box for inputting the parameter name and data type of the parameter value is displayed on the screen. In this case, the parameter name is directly input by the user, and the data type allows the user to select one of integer type, string type, and Boolean type. After entering the parameter name and data type of the parameter value, the user presses the OK button.

If the user selects the input IPC parameter or the output IPC parameter in step (2), a dialog for inputting the IPC type and IPC name is displayed on the screen. Here, the IPC type allows the user to select one of the Point of Initiation (POI), Point of Return (POR), and Point of Synchronization (POS) recommended in the ITU-T standard. The IPC name is entered manually by the user. After entering the IPC type and IPC name, the user presses the OK button. Then, a dialog is displayed asking whether to define IPD (Inter Process Data) on the screen. IPD is the data used for interprocess communication and indicates the data necessary for communication or the message to be delivered to the other process. Here, if the user presses the cancel button, the IPC parameter definition is finished. If the user presses the OK button, a dialog box is displayed to enter the IPD name and data type of the IPD value on the screen. The IPD name is entered directly by the user, and the data type of the IPD value allows the user to select one of an integer type, a string type, and a Boolean type (6). After entering the IPD name and data type of the IPD value, the user presses the OK button (7). A dialog is displayed on the screen asking if the user wants to continue defining the IPD (8) .If the user presses the cancel button, the parameter definition is finished. A dialog box is displayed in which you can enter, and operations (6), (7) and (8) are repeated.

4 is a flowchart illustrating a method for automatically generating a SIB application program according to an embodiment of the present invention.

First, in step S401, a graphic interface is output on the screen, and in step S402, after waiting for user input, in step S403, it is determined whether the user selects the SIB definition menu.

As a result of the determination in step S403, when the user selects the SIB definition menu, in step S404, the user inputs the name of the SIB to be defined, and repeats from step S402.

As a result of the determination in step S403, if the user does not select the SIB definition menu, it is determined in step S405 whether the user selects the input data parameter menu.

As a result of the determination in step S405, when the user selects the input data parameter menu, it is determined in step S406 whether the SIB name is defined.

If the SIB name is defined as the determination result in step S406, after performing the input data parameter definition function in step S407, the process is repeated from step S402. If the SIB name is not defined, the SIB definition is made in step S421. After outputting a warning message to select a menu first, the process is repeated from step S402.

On the other hand, if the user did not select the input data parameter menu as a result of the determination in step S405, it is determined in step S408 whether the user selected the input IPC parameter menu.

As a result of the determination in step S408, if the user selects the input data parameter menu, it is determined in step S409 whether the SIB name is defined.

If the SIB name is defined as the determination result in step S409, after performing the input IPC parameter definition function in step S410, the process is repeated from step S402. If the SIB name is not defined, the process proceeds to step S421. .

On the other hand, if the user did not select the input data parameter menu as a result of the determination in step S408, it is determined in step S411 whether the user selected the output data parameter menu.

As a result of the determination in step S411, if the user selects the output data parameter menu, it is determined in step S412 whether the SIB name is defined.

If the SIB name is defined as the determination result in step S412, after performing the output data parameter definition function in step S413, the process is repeated from step S402. If the SIB name is not defined, the process proceeds to step S421. .

On the other hand, if the user did not select the output data parameter menu as a result of the determination in step S411, it is determined in step S414 whether the user selected the output IPC parameter menu.

As a result of the determination in step S414, if the user selects the output IPC parameter menu, it is determined in step S415 whether the SIB name is defined.

If the SIB name is defined as the determination result in step S415, after performing the output IPC parameter definition function in step S416, the process is repeated from step S402. If the SIB name is not defined, the process proceeds to step S421. .

On the other hand, if the user did not select the output IPC parameter menu as a result of the determination in step S414, it is determined in step S417 whether the user selected the code generation menu.

As a result of the determination in step S417, if the user selects the code generation menu, it is determined in step S418 whether the SIB name is defined.

If the SIB name is defined as the determination result in step S418, after performing the code generation function in step S419, the process is repeated from step S402. If the SIB name is not defined, the process proceeds to step S421.

On the other hand, if the user did not select the code generation menu as a result of the determination in step S417, it is determined in step S420 whether the user selected the end menu.

As a result of the determination in step S420, if the user selects the exit menu, the process ends. If the user does not select the exit menu, the process is repeated from step S402.

5 is a flowchart illustrating a SIB input data parameter definition method according to an embodiment of the present invention.

First, in step S501, after outputting the input data parameter definition dialog on the screen, in step S502, when the user inputs the name of the parameter, in step S503, the user selects one or more of the listed parameter categories, and in step S504 , The user selects one of the listed data types.

Next, after waiting for a user input in step S505, it is determined in step S506 whether the user selects a confirmation button.

As a result of the determination in step S506, if the user has not selected the confirmation button, it is determined in step S507 whether the user has selected the cancel button.

As a result of the determination in step S507, if the user selects the cancel button, the process ends. If the user does not select the cancel button, the process is repeated from step S505.

On the other hand, if the user selects the OK button as a result of the determination in step S506, in step S508, after storing the value input so far in the internal storage, whether or not the data type selected by the user in the step S509 is an enumerated type. Determine whether or not.

As a result of the determination in step S509, if the data type selected by the user is not an enumerated type, and the data type selected by the user is an enumerated type, in step S510, a dialog for inputting an enumerated item on the screen is outputted. In step S511, if the user inputs the enumerated item, in step S512, the user's input value is stored in the internal storage, and in step S513, a dialog asking whether to continue entering the enumerated item on the screen is output. do.

Subsequently, after waiting for user input in step S514, it is determined in step S515 whether the user selects a confirmation button.

As a result of the determination in step S515, if the user selects the confirmation button, the process is repeated from step S510. If the user does not select the confirmation button, it is determined in step S516 whether the user selects the cancel button.

As a result of the determination in step S516, if the user selects the cancel button, the process ends. If the user does not select the cancel button, the process is repeated from step S514.

FIG. 6 is a flowchart illustrating a method for defining SIB input IPC parameters according to an embodiment of the present invention.

First, in step S601, the input IPC parameter definition dialog is displayed on the screen, and in step S602, one of the IPC types listed by the user is selected, and in step S603, the user inputs an IPC name.

Next, after waiting for user input in step S604, it is determined in step S605 whether the user selects a confirmation button.

As a result of the determination in step S605, if the user does not select the confirmation button, in step S606 it is determined whether the user selects the cancel button.

As a result of the determination in step S606, if the user selects the cancel button, the process ends. If the user does not select the cancel button, the process is repeated from step S604.

On the other hand, if the user selects the OK button as a result of the determination in step S605, in step S607, after storing the value input by the user in the internal storage, in step S608, IPD (Inter Process Data) is defined on the screen. A dialog is displayed asking whether or not to

Subsequently, after waiting for user input in step S609, it is determined in step S610 whether the user selects a confirmation button.

As a result of the determination in step S610, if the user has not selected the confirmation button, in step S616 it is determined whether the user selects the cancel button.

As a result of the determination in step S616, if the user has selected the cancel button, the process ends. If the user has not selected the cancel button, the process is repeated from step S609.

On the other hand, if the user selects the OK button as a result of the determination in step S610, after outputting the IPD definition dialog on the screen in step S611, the user inputs the name of the IPD in step S612, and the user in step S613. Select one of the listed IPD data types.

Subsequently, after storing the value input by the user in the internal storage in step S614, in step S615, a dialog is outputted asking whether to continue defining the IPD on the screen, and the process is repeated from step S609.

7 is a flowchart illustrating a SIB output data parameter definition method according to an embodiment of the present invention.

First, in step S701, the output data parameter definition dialog is output to the screen. In step S702, when the user inputs the name of the parameter, in step S703, the user selects one of the listed data types.

Next, after waiting for user input in step S704, it is determined in step S705 whether the user selects a confirmation button.

As a result of the determination in step S705, if the user does not select the confirmation button, in step S707 it is checked whether the user selects the cancel button.

As a result of the determination in step S707, if the user selects the cancel button, the process ends. If the user does not select the cancel button, the process is repeated from step S704.

On the other hand, if the user selects the confirmation button as a result of the determination in step S705, the user ends the operation after storing the values input so far in the internal storage in step S706.

8 is a flowchart illustrating a SIB output IPC parameter definition method according to an embodiment of the present invention.

First, in step S801, the output IPC parameter definition dialog is output to the screen, then in step S802, the user selects one of the listed IPC types, and in step S803, the user inputs an IPC name.

Subsequently, after waiting for user input in step S804, it is determined in step S805 whether the user selects a confirmation button.

As a result of the determination in step S805, if the user does not select the confirmation button, it is determined in step S806 whether the user selects the cancel button.

As a result of the determination in step S806, if the user selects the cancel button, the process ends. If the user does not select the cancel button, the process is repeated from step S804.

On the other hand, if the user selects the OK button as a result of the determination in step S805, in step S807, after storing the value input by the user in the internal storage, in step S808, a dialog asks whether to define the IPD on the screen. Is output.

Subsequently, after waiting for user input in step S809, it is determined in step S810 whether the user selects a confirmation button.

As a result of the determination in step S810, if the user does not select the confirmation button, it is determined in step S811 whether the user selects the cancel button.

As a result of the determination in step S811, if the user selects the cancel button, the process ends. If the user does not select the cancel button, the process is repeated from step S809.

On the other hand, if the user selects the OK button as a result of the determination in step S810, in step S812, the IPD definition dialog is displayed on the screen. In step S813, when the user inputs the name of the IPD, in step S814, the user Select one of the listed IPD data types.

Subsequently, in step S815, the user's input value is stored in the internal storage, and in step S816, a dialog asking whether to continue the IPD definition on the screen is output, and then repeated from step S809.

FIG. 9 is a structural diagram showing a data structure for storing a user-defined SIB parameter in an internal storage according to an embodiment of the present invention. As shown in the figure, FIG.

The internal data structure is the resource type, resource name, resource identifier, starting position, width, resource characteristics, parameter number, parameter category, parameter name, data type, enum item count, pointer to enum item, pointer to next parameter It consists of fields.

The resource type indicates what resource to represent when the parameter is expressed in the parameter editor of the SIB application to be auto-generated, the resource name indicates the name of the resource, the resource identifier indicates a unique value to identify the resource, and The position indicates the starting position at which the resource is to be output, the width indicates the width of the resource, and the resource characteristic indicates a resource dependent characteristic. The parameter number indicates the number of parameters in the parameter set for each parameter type, the parameter category indicates the category of the parameter, and the parameter category includes the service support data (SSD), call instance data (CID), service instance data (SID), and point of interest (POI). Of Initiation, Point Of Return (POR), Point Of Synchronization (POS), Inter Process Data (IPD).

The parameter name indicates the name of the parameter, the data type indicates the data type of the parameter value, and the enum item number is used only when the data type is an enum type and indicates the number of enum items. A pointer to an enumeration item is a pointer to the data structure that stores the enumeration item and is used only when the data type is an enumeration. The pointer to the next parameter represents the pointer to the data structure of the next parameter, or NULL if there is no next parameter.

Among the fields of the data structure, resource type, resource name, resource identifier, start position, width, and resource characteristics are required to create a resource file. Resource identifiers, parameter numbers, parameter categories, parameter names, data types, enumeration item counts, and pointers to enumeration items are required for implementation file and header file generation.

FIG. 10 is a structural diagram illustrating a data structure for storing a user-defined parameter set for each SIB type in an internal storage according to an embodiment of the present invention.

Each user-defined SIB parameter is made of the data structure of FIG. 9 regardless of which parameter type it belongs to. However, when actually storing in the internal storage is stored by type. In this embodiment, the type-specific parameter set is stored in a linked list of the data structure of FIG. 9. If a SIB has four types of parameter sets, there are four linked lists. If there is only one type, there is one linked list. 10 is an explanatory diagram for explaining a format for storing a user-defined parameter set in an internal storage according to the present invention.

Meanwhile, the code generation function of FIG. 3 reads the data structure of FIG. 10 from internal storage, visits the nodes of the list one by one, and automatically generates them by the SIB application program. In order to generate the SIB application, the resource file is first generated automatically, then the header file is generated, and the implementation file is generated.

11 is a flowchart illustrating a method of generating a resource file according to an embodiment of the present invention.

First, in step S1101, it is determined whether or not there is a linked list storing the input data parameters.

As a result of the determination in step S1101, if there is a linked list storing the input data parameters, it is determined in step S1102 whether there is a node that has not been visited.

As a result of the determination in step S1102, if there is no node not visited, the flow proceeds to step S1105, and if there is a node not visited, the node not visited is visited in step S1103, and the resource file in step S1104. The resource type, resource name, resource identifier, start position, width, and resource characteristics are recorded in the following step, and then the process is repeated from step S1102.

On the other hand, if the linked list in which the input data parameter is stored does not exist as a result of the determination in step S1101, it is determined in step S1105 whether the linked list in which the input IPC parameter is stored exists.

As a result of the determination in step S1105, if there is a linked list storing the input IPC parameters, it is determined in step S1106 whether there is a node that has not been visited.

As a result of the determination in step S1106, if there is no node not visited, the flow proceeds to step S1109, and if there is a node not visited, in step S1107, after visiting the node not visited, in step S1108, the resource file The resource type, resource name, resource identifier, start position, width, and resource characteristics are recorded in the following step, and then the process is repeated from step S1106.

On the other hand, if the linked list in which the input IPC parameter is stored does not exist as a result of the determination in step S1105, it is determined in step S1109 whether the linked list in which the output data parameter is stored exists.

As a result of the determination in step S1109, if there is a linked list storing the output data parameters, it is determined in step S1110 whether there is a node that has not been visited.

As a result of the determination in step S1110, if there is no node not visited, the flow proceeds to step S1113, and if there is a node not visited, in step S1111, after visiting the node not visited, in step S1112, the resource file The resource type, resource name, resource identifier, start position, width, and resource characteristics are recorded in the message, and then the process is repeated from step S1110.

On the other hand, if the linked list storing the output data parameter does not exist as a result of the determination in step S1109, it is determined in step S1113 whether there is a linked list storing the output IPC parameter.

As a result of the determination in step S1113, if the linked list storing the output IPC parameter does not exist, the process terminates. To judge.

As a result of the determination in step S1114, if there is no node not visited, and terminates, and if there is a node not visited, in step S1115, after visiting the node not visited, in step S1116, the resource type in the resource file After recording the resource name, resource identifier, start position, width and resource characteristics, the process is repeated from step S1114.

12 is a flowchart illustrating a header file generation method according to an embodiment of the present invention.

First, in step S1201, a prototype declaration section is generated for a class constructor. In step S1202, a data declaration section for SIB identifier, SIB name, SIB mode, file name, and SIB visual property related attributes is generated. In S1203, a circular declaration portion for an operation that outputs a graphic on the screen is generated.

Subsequently, in step S1204, a prototype declaration unit for the SIB attribute management operation is generated, in step S1205, a prototype declaration unit for the service logic program generation operation is generated, and in step S1206, the operation writes or reads the SIB information to an external file. Create a prototype declaration for.

Then, in step S1207, a circular declaration portion for the communication operation is generated, in step S1208, a circular declaration portion for the SIB parameter editing operation is generated, and in step S1209, a circular declaration portion for the registration and deregistration operation is generated. .

Subsequently, after generating a data declaration section for the SIB parameter editor identifier in step S1210, it is determined in step S1211 whether a linked list storing the input data parameters exists.

As a result of the determination in step S1211, if there is a linked list storing the input data parameters, in step S1212, after generating a data declaration section for the total number of parameters belonging to this type, in step S1213, the whole belonging to this type A data structure declaration section capable of storing parameters is generated, and in step S1214, it is determined whether there is a node that has not been visited.

As a result of the determination at step S1214, if there is no node not visited, the flow proceeds to step S1217. If there is a node not visited, at step S1215, the node not visited is visited, and at step S1216, The value of the resource name and data type fields are examined to generate a data declaration section for the resource name, and the process is repeated from step S1214.

On the other hand, if the linked list in which the input data parameter is stored does not exist as a result of the determination in step S1211, it is determined in step S1217 whether the linked list in which the input IPC parameter is stored exists.

As a result of the determination in step S1217, if there is a linked list storing the input IPC parameters, in step S1218, a data declaration part for the total number of parameters belonging to this type is generated, and then in step S1219, all A data structure declaration section capable of storing parameters is generated, and in step S1220, it is determined whether there is a node that has not been visited.

As a result of the determination at step S1220, if there is no node not visited, the flow proceeds to step S1223, and if there is a node not visited, in step S1221, the node not visited is visited, and then in step S1222, The data declaration unit for the resource name is generated by examining the values of the resource name and data type fields, and the process is repeated from step S1220.

On the other hand, if the linked list in which the input IPC parameter is stored does not exist as a result of the determination in step S1217, it is determined in step S1223 whether the linked list in which the output data parameter is stored exists.

As a result of the determination in step S1223, if there is a linked list storing the output data parameters, in step S1224, after generating a data declaration section for the total number of parameters belonging to this type, in step S1225, the whole belonging to this type A data structure declaration section capable of storing parameters is generated, and in step S1226, it is determined whether there is a node that has not been visited.

As a result of the determination in step S1226, if there is no node not visited, the flow proceeds to step S1229, and if there is a node not visited, in step S1227, after visiting the node not visited, the node in step S1228 The value of the resource name and data type fields are checked from the data declaration unit for the resource name, and the process is repeated from step S1226.

On the other hand, if the linked list which stores the output data parameter does not exist as a result of the determination in step S1223, it is determined in step S1229 whether the linked list which stores the output IPC parameter exists.

As a result of the determination in step S1229, if the linked list storing the output IPC parameter does not exist, and the linked list storing the output IPC parameter exists, in step S1230, the total number of parameters belonging to this type is determined. After generating the data declaration unit for the data, in step S1231, a data structure declaration unit capable of storing all parameters belonging to this type is generated, and in step S1232, it is determined whether there is a node that has not been visited.

As a result of the determination in step S1232, if there is no node not visited, and the node not visited exists, in step S1233, after visiting the node not visited, in step S1234, the resource name and The data declaration unit for the resource name is generated by checking the value of the data type field, and is repeated from the step S1232.

13 is a flowchart illustrating a method of generating an implementation file according to an embodiment of the present invention.

First, in step S1301, a file include statement is generated, in step S1302, a message map is generated, and in step S1303, a class generator is generated.

Subsequently, in step S1304, after generating an operation to be outputted graphically on the screen, in step S1305, an SIB attribute management operation is generated, and in step S1306, a service logic program generation operation is generated. At this time, the body of the operation is not created.

Thereafter, in step S1307, after generating an operation for writing or reading the SIB information to an external file, in step S1308, a communication operation is generated, in step S1309, a SIB parameter editing operation is generated, and in step S1310, registration and registration are performed. Create a release operation and exit.

As described in detail above, the present invention provides a form-based graphic interface for inputting information of a service independent building block (SIB) parameter to a user in a next generation intelligent network service development environment. By inputting information about the parameters of the SIB to be developed, the user's input is converted into the internal storage format and stored, and providing a method of automatically generating the SIB application code using the stored values, thereby developing the SIB application. Reduce cost, effort and effort, make it easier for end-users who do not have expertise in intelligent networks and programming to define new SIBs, and reduce the maintenance costs of SIB applications by unifying the structure of SIB applications. There is.

The technical spirit of the present invention has been described above with reference to the accompanying drawings. However, the present invention has been described by way of example only, and is not intended to limit the present invention. In addition, it is obvious that any person skilled in the art may make various modifications and imitations without departing from the scope of the technical idea of the present invention.

Claims (27)

In a method for automatically generating a service independent building block (SIB) application used in an advanced intelligent network (AIN) service development environment, A first step of inputting a name of S-Ivy to be developed; A second process of receiving information of an SIB parameter to be developed and storing in an internal storage; A third step of automatically generating an SIB application code corresponding to a name of an SIB to be developed in the first step, using a value stored in the internal storage in the second step, if there is a code generation request input; Method for automatic generation of Sivy application, characterized in that consisting of. The method of claim 1, And a fourth step of invoking an appropriate operation corresponding to the S-I parameter input in the second step. The method according to claim 1 or 2, The second process, A first step of inputting a parameter name, a parameter category, and a data type if the inputted SMI parameter is an input data parameter, and storing it in an internal storage; A second step of determining whether the data type stored in the first step is an Enumerate Data Type; As a result of the determination of the second step, if the data type is an enumerated type, receiving the items corresponding to the enumerated type and storing in the internal storage, and if the data type is not an enumerated type comprises a third step comprising: How SBI application automatically generated. The method of claim 3, wherein The parameter category of the first step may be any one or more of Service Support Data (SSD), Call Instance Data (CID), and Service Instance Data (SID). The method of claim 3, wherein The data type of the first stage is any one of an integer data type, a string data type, a Boolean data type and an enumerated data type. Auto generation method. The method according to claim 1 or 2, The second process, A first step of inputting an IPC type and an IPC name if the inputted SIB parameter is an input IPC parameter and storing it in an internal storage; And a second step of inputting a name and data type of an IPD (Inter Process Data) and storing the data in an internal storage. The method of claim 6, The IPC type of the first step is any one of Point Of Initiation (POI), Point Of Return (POR) and Point Of Synchronization (POS). The method of claim 6, The data type of the second step is any one of the integer type (Integer Data Type), string type (String Data Type), Boolean data type (Boolean Data Type) characterized in that the automatic generation method of the S-Ivy application program. The method according to claim 1 or 2, The second process, And if the inputted Ivy parameter is an output data parameter, inputting a parameter name and a data type and storing it in an internal storage. The method of claim 9, And the data type of the first step is one of an integer data type, a string data type, and a Boolean data type. The method according to claim 1 or 2, The second process, A first step of inputting an IPC type and an IPC name if the inputted SIB parameter is an output IPC parameter and storing it in an internal storage; And a second step of inputting a name and data type of an IPD (Inter Process Data) and storing the data in an internal storage. The method of claim 11, The IPC type of the first step is any one of Point Of Initiation (POI), Point Of Return (POR) and Point Of Synchronization (POS). The method of claim 11, The data type of the second step is any one of the integer type (Integer Data Type), string type (String Data Type), Boolean data type (Boolean Data Type) characterized in that the automatic generation method of the S-Ivy application program. The method of claim 1, The third process, If there is a code generation input, a first step of generating a resource file; A second step of generating a header file; And a third step of generating an implementation file. The method of claim 14, The first step is, And extracting values of a resource type, a resource name, a resource identifier, a starting position, a width, and a resource characteristic field corresponding to the input parameter from the node, and recording the extracted values in a resource file to be automatically generated. How to automatically generate the Sivy application. The method of claim 15, The input parameter type is any one of an input data parameter, an input inter process communication (IPC) parameter, an output data parameter and an output IPC parameter. The method of claim 14, The second step, A first substep of generating a prototype declaration section and a data declaration section and writing them in a header file; A second sub-step of generating a declaration unit for data representing the total number of parameters belonging to the input parameter type and recording the declaration unit in a header file; A third sub-step of generating a data structure declaration unit capable of storing all parameters belonging to the input parameter type and writing the same in a header file; A fourth sub which extracts values of a resource name and data type field corresponding to an input parameter type from a node, generates a declaration section of data to store a user input value for a resource using the extracted values, and writes them to a header file Automatic generation method of Sivy application, characterized in that it comprises a step. The method of claim 17, The first sub-step, Prototype declarations for class constructors, on-screen operations, SBI attribute management operations, service logic program generation operations, operations for writing or reading SBI information to external files, communication operations, SBI parameter editing operations, and registration and deregistration operations. A first sub-sub step of generating a portion and writing to a header file; And a second sub-sub step of generating a data declaration for the Ivy identifier, the Ivy name, the Ivy mode, the file name, the Ivy visual property related attributes, and the Ivy Parameter Editor identifier and writing them to the header file. How to automatically generate the S-ivy application. The method of claim 17, The input parameter type of the second to fourth sub-steps is any one of an input data parameter, an input inter process communication (IPC) parameter, an output data parameter, and an output IPC parameter. . The method of claim 14, The third step, Write file include statements, message maps, class constructors, screen output operations, SB attribute management operations, service logic program generation operations other than the body part of the operation, and write SBI information to external files, And a sub-step of generating a reading operation, a communication operation, an SIB parameter editing operation, a registration and a deregistration operation, and recording the result in an implementation file. A computer-readable recording medium recording a program capable of executing a method for automatically generating a service independent building block (SIB) application used in an advanced intelligent network (AIN) service development environment, A first step of inputting a name of S-Ivy to be developed; A second process of receiving information of an SIB parameter to be developed and storing in an internal storage; A third step of inputting a parameter name, a parameter category and a data type in the internal storage when the SIB parameter input in the second step is an input data parameter; A fourth step of determining whether the data type stored in the third step is an enumerated data type; A fifth step of receiving an item corresponding to the enumerated type and storing it in an internal storage if the data type is an enumerated type and ending if the data type is not an enumerated type; A sixth step of inputting an IPC type and an IPC name after storing the inputted IC parameter in the second step, the IPC type and the IPC name; A seventh process of inputting a name and data type of an IPD (Inter Process Data) and storing the data in an internal storage; An eighth step of inputting a parameter name and a data type and storing it in an internal storage when the S-I parameter input in the second step is an output data parameter; A ninth process of inputting an IPC type and an IPC name and storing it in an internal storage when the S-I parameter input in the second process is an output IPC (Inter Process Communication) parameter; A tenth step of inputting a name and a data type of an IPD (Inter Process Data) and storing it in an internal storage; A computer-readable recording medium having recorded thereon a program capable of executing an eleventh process of generating a resource file, a header file, and an implementation file when there is a code generation input. On your computer, In order to automatically generate a user-defined Ivy application, A resource element region for generating a resource file; And And a header and an implementation element area for generating a header file and an implementation file. The method of claim 22, The resource element area is, As a resource type field used to determine which resource to express when a parameter is expressed in a parameter editor of an SIB application to be automatically generated; A resource name field indicating a resource name; A resource identifier field indicating a unique value for identifying a resource; A starting position field indicating a starting position at which the resource is to be output; A width field indicating the width of the resource; And A computer-readable recording medium having recorded an S-Ivy parameter comprising a resource feature field indicating a dependent feature of a resource. The method of claim 22, The header and implementation element area is A parameter number field indicating the number of parameters in a parameter set of a specific parameter type; A parameter category field indicating a category of parameters; A parameter name field indicating a name of the parameter; And And a data type field indicating a data type of the parameter value. The method of claim 24, The parameter categories include Service Support Data (SSD), Call Instance Data (CID), Service Instance Data (SID), Point Of Initiation (POI), Point Of Return (POR), Point Of Synchronization (POS), and Inter Process (IPD). And a computer-readable recording medium having recorded thereon an S-I parameter. The method of claim 24, The data type may be any one of an integer data type, a string data type, a Boolean data type, and an enumerated data type. Recordable media. The method of claim 24 or 26, The header and implementation element area is An enumeration item count field indicating the number of enumeration items when the data type is an enumeration; And And a pointer field for the enumeration item, the pointer to the data structure storing the enumeration item.