Method of creating signal message common files for mobile switching center

• US 5,930,709 A
• Filed: 10/31/1997
• Issued: 07/27/1999
• Est. Priority Date: 12/12/1996
• Status: Expired due to Term

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute, Korea Telecommunication Authority
• Inventors: Shin, Jae Wook, Park, Kwang Roh
• Primary Examiner(s): Kulik, Paul V.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/962,352
• Time in Patent Office: 634 Days
• Field of Search: 707/1, 707/3, 707/10, 455/412, 455/433, 455/435, 455/445, 455/560
• US Class Current: 455/435.1
• CPC Class Codes: H04W 88/14 Backbone network devices
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching

Abstract

A method of creating signal message common files for a mobile switching center which is capable of simplifying a process and effectively and directly creating a signal message common file is disclosed. The method includes the steps of registering a signal message descriptive file from an operator of each block, setting an environment for creating a signal message common file using a system formation material and a registered material information, checking whether there is an error during the above-described steps, and reporting the error to a manager or an operation when there is an error; receiving a signal message descriptive file using the environment set and creating a signal message common file which is to be updated in minimum with respect to the signal message updated using an updated signal message list and a block of a newly registered block; creating a signal message definition file which is matched with a characteristic of a corresponding language and processor using a signal message common file list which is created and should be updated and an execution module name list which is to be updated; and creating a signal message identifier file which is matched with a characteristic of a corresponding language and a processor using a signal message common file list which is created.

Claims

1. A method of creating signal message common files for a mobile switching center, comprising the steps of:

a first step (S1 through S9) for registering a signal message descriptive file from an operator of each block, setting an environment for creating a signal message common file using a system formation material and a registered material information, checking whether there is an error during the above-described steps, and reporting the error to a manager or an operator when there is an error;

a second step (S10 through S20) for receiving a signal message descriptive file using the environment set in the first step and creating a signal message common file which is to be updated in minimum with respect to the signal message updated using an updated signal message list and a block of a newly registered block;

a third step (S21 through S26) for creating a signal message definition file which is matched with a characteristic of a corresponding language and processor using a signal message common file list which is created in the second step and should be updated and an execution module name list which is to be updated; and

a fourth step (S27 through S32) for creating a signal message identifier file which is matched with a characteristic of a corresponding language and a processor using a signal message common file list which is created in the second step and should be updated.

2. The method of claim 1, wherein said first step includes the sub-steps of:

a first sub-step (S1) for extracting a directory shape information for a file which is needed for creating a signal message common file;

a second sub-step for making a block name list (S2) which is registered in the system, an execution module name list (S3) which is used for the system, and a processor name list (S4);

a third sub-step for extracting (S5) a newly registered block list and extracting (S6) a signal message list from the signal message descriptive file;

a fourth sub-step for extracting (S7) a system common file for checking the registered signal message and the common file; and

a fifth sub-step for checking (S8) whether an error is found during the sub-steps (S1 through S7) and informing (S9) a manager and an operator of an error message having an error message code.

3. The method of claim 1, wherein said second step includes the sub-steps of:

a first sub-step for inputting (S10) a signal message descriptive file based on a block name list (S2) when there is not an error in the first step;

a second sub-step for extracting (S11) a signal message name based on a signal message separator (#) from the inputted signal message descriptive file and extracting (S12) a signal message transmitting and receiving block from the signal message transmitting and receiving block field (.dr);

a third sub-step for judging (S13) whether the inputted signal message descriptive file (S10) is a block to be updated based on the presence thereof in the newly registered block list (S5) and judging (S14) whether the signal message list (S6) exists in order to judge whether a corresponding signal message is a signal message which is needed to be updated when there is a newly registered block list;

a fourth sub-step for making (S15) an execution module name list based on the execution module name list (S3) when the corresponding signal message exists in the list to be updated and the signal message is to be updated as a result of the third sub-step, making (S16) a processor name list based on the processor name list (S4), and setting (S17) a flag in order to indicate a state that there is a signal message common file which is needed to be updated together with the list making sub-step (S16);

a fifth sub-step for adding (S18) a signal message to the transmitting and receiving block extracted (S12) from the signal message transmitting and receiving block field (,dr) when the block is not the block to be updated after the flag setting (S17) and the signal message is not the signal message to be updated as a result of the judgement (S14); and

a sixth sub-step for judging (S19) whether the added signal message is the final signal message of the signal message descriptive file (S10), repeatedly performing the sub-steps (S11 through S18) with respect to the next signal message based on the signal message separator (#) when the signal message is not the final signal message, and judging (S20) whether the corresponding file is the final signal message when the signal is the final signal message.

4. The method of claim 1, wherein said third step includes the sub-steps of:

a first sub-step for judging (S21) whether a flat is set in order to indicate there is a signal message common file to be updated when the signal corresponds to the final signal message descriptive file as a result of the second step and judging as a condition that there is not a common file to be newly created when the flag is not set;

a second sub-step for sequentially inputting (S22) execution module names from the first name thereof based on the execution module name list (S15), which is to be updated, when the flag is set as a result of the judgement (S21) and judging (S23) whether a corresponding block corresponds to the block which is in the low level processor when the corresponding block is not the block which is in the high level processor;

a third sub-step for making (S24) for a signal message spec file so that the program which is made by a CHILL language is used for a compile when the corresponding block in the block which is in the high level processor and making (S25) a signal message head file so that a program which is programmed by a C-language is used for a compile when the corresponding block is the block which is in the low level processor; and

a fourth sub-step for judging (S26) whether the corresponding execution module is the final module based on the execution module name list (S15) after the sub-step S24 or S25 is completed and repeatedly performing the sub-steps S22 through S25 with respect to the next execution module when the module is not the final execution module as a result of the judgement (S26).

5. The method of claim 1, wherein said fourth step includes the sub-steps of:

a first sub-step for sequentially inputting (S27) the processor names from the first processor name based on the processor name list (S16), which is to be updated, in order to create a signal message identifier file among the signal message common files based on the signal message common file update list when the head file making sub-step (S25) is the final step and creating (S28) a signal message identifier spec file;

a second sub-step for judging (S29) a corresponding execution module name is an MP_-- PP in order to create a signal message identifier file which corresponds to the characteristic of each language and creating (S30) a signal message identifier head file when the module name is the MP_-- PP as a result of the judgement (S29);

a third sub-step for judging (S31) whether there is a final processor name based on the processor name list (S16), which is to be updated, when the signal message identifier file creating is completed with respect to one processor name and repeating the sub-steps S27 through S30 when the name is not the final processor name; and

a fourth sub-step for updating (S32) the signal message identifier with respect to the added signal message when the processor name is the final name as a result of the judgement (S31) and completing the signal message identifier file creating step.