KR100784595B1 - Method for Managing Process State in Mobile Communication System - Google Patents

Abstract

The present invention relates to a process state management method in a mobile communication system, and in particular, a mobile communication to manage the state of multiple processes using the unique information received from the operating system and resource usage information managed by the operating system when the process is running. A process state management method in a system.

The process state management method in a mobile communication system according to an embodiment of the present invention includes the steps of: collecting and storing state information of managed target processes stored in an external storage device when the HLR is initially driven; Receiving and collecting and storing unique information and resource usage information from an operating system after restarting an interrupted process among the management target processes; Retrieving the state of the message queue based on the resource usage information of the managed target process and checking whether the resource is normally used in the managed target process; When the resource usage is not normally performed, the process includes stopping or restarting the corresponding management target process according to the number of abnormality detections of the resource usage information.

Description

Process state management method in mobile communication system {Method for Managing Process State in Mobile Communication System}

1 illustrates a typical HLR system.

2 illustrates in detail the process management block within the HLR system;

3 is a diagram illustrating a correlation between a process management block in an HLR, a managed process, and an operating system according to an embodiment of the present invention;

4 is a diagram illustrating a process management method in a mobile communication system according to an embodiment of the present invention.

5 is a diagram showing in more detail the process management method in the mobile communication system in FIG.

* Description of the symbols for the main parts of the drawings *

10: process management block

11: System Overload Information Collector

12: process status information collector

13: message handler

14: process driver

15: System resource usage information storage unit in the operating system                 

16: process shape information storage unit

17: operating process information storage unit in the operating system

The present invention relates to a process state management method in a mobile communication system, and in particular, a mobile communication to manage the state of multiple processes using the unique information received from the operating system and resource usage information managed by the operating system when the process is running. A process state management method in a system.

In general, a mobile communication home location register (HLR) system, as shown in FIG. 1, has an HLR system 100 that plays an HLR role in a mobile communication network configuration, and hardware and application software installed in the corresponding HLR system. An operator's work seat 20 for informing and controlling the operation status of the system (called "process") and resource usage of the system, and a printer 30 for outputting all logs generated during operation And the like.

The HLR system 100 is responsible for storing a large amount of subscriber information and providing subscriber information requested by an exchange or a VLR (Vister Location Register) .There are many application processes in the HLR system to perform such a role normally. . Since network elements, including HLR systems, are in principle unable to interrupt service, the state of the hardware or software automatically to minimize service downtime in the event of a service interruption due to a system failure, software malfunction, or abnormal termination. Provides the ability to monitor, control and recover in real time.

Among many application processes in the HLR system, the process management block 10 is an application process for monitoring software abnormally terminating or abnormal operation of the software inside the HLR system.

The process management block 10 performs a function of providing a process shape and state management function, an overload control function, and process state information. In addition, the process management block 10 is the only software having the authority to determine whether the application process is normal or abnormal and to control the state of the process according to the situation.

Thus, if the operator wants to control the state of the process, the operator's request is sent to the process management block 10 and processed. In addition, since the process state information used in the process management block 10 is important information for identifying the operation state of the HLR system to the operator of the HLR system or the operator of the mobile communication network management system, the state is changed in real time and provided to all the operators. do. In addition, the process management block 10 performs an overload control function to restore the HLR system to the service provision state as soon as possible when the process cannot operate normally due to a lack of system resources. In other words, the process management block 10 periodically manages the state of the process and the system load state, and handles process state management requests or process state information requests that occur aperiodically.

The above-described process management block 10 used a method of periodically sending and receiving messages with the application processes to manage the state of the application process. In this manner, when the process management block 10 transmits a designated message to the managed processes, the target processes transmit a response message to the process management block 10 in response. However, if an application process does not respond n or more times, the process management block 10 determines that the application process is not running or operates abnormally, and thus stops the execution of the application process and starts a new application process. I had to go through the process.

The above-mentioned method of sending and receiving messages uses system resources, so if the system is overloaded, or the application process cannot respond to the message due to the excessive amount of messages to process temporarily, Not only can not accurately determine the state of the, but also has a problem that it takes a considerable time to detect the interruption / abnormal state of the process.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned general problems, and an object thereof is to manage a state of multiple processes by using unique information received from an operating system and resource usage information managed by an operating system when a process is run. Accurately determine the state management of application processes in real time without load, and recover quickly when abnormal situations occur.

The process state management method in the mobile communication system according to an embodiment of the present invention for achieving the above object comprises the steps of: collecting and storing state information of the management target processes stored in the external storage device when the HLR is initially driven; Receiving and collecting and storing unique information and resource usage information from an operating system after restarting an interrupted process among the management target processes; Retrieving the state of the message queue based on the resource usage information of the managed target process and checking whether the resource is normally used in the managed target process; When the resource usage is not normally performed, the process includes stopping or restarting the corresponding management target process according to the number of abnormality detections of the resource usage information.

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

In the mobile communication system according to the present invention, the process management block for managing the process state collects information on the resource utilization rate as shown in FIG. System overload information collector 11 for monitoring whether the system is overloaded, process status information collector 12 that collects and changes status information about a process periodically, and exchanges information with a managed process and an operator task seat. And a process driver 14 capable of driving other application processes that are processes other than the process management block 10.

In addition, the process management block 10 is a system resource usage information storage unit 15 in the operating system for storing information that can determine the system overload, such as the resource utilization rate of the system and the management process by the system overload information collector 11 And a process shape information storage unit 16 which reads and stores shape information of processes stored in a predetermined space of the HLR system, and processes in an operating system (OS) received from managed objects for process state management. It further includes a drive process information storage unit 17 in the operating system for storing information.

3 illustrates a correlation between a process management block and a process to be managed and an operating system.

The process management block 10 performs process state management by using unique information. The shape information of application processes in the HLR stored in an external storage device, which is a hard disk in the HLR system, that is, as shown in Table 1, corresponding process unique values. Information about a process name, a process number, a message queue value, a process version, and the like, which are defined as follows, is read and stored in the process shape information storage unit 16 which is an internal memory space.

Process name Process number Message queue key Process version One AAA 8000 2000 2.0 2 BBB 8100 2001 2.5 3 CCC 8200 2002 1.2 4 DDD 8300 2003 1.9 5 EEE 9000 3000 3.1 6 FFF 9100 3001 1.0 7 GGG 9200 3002 2.2 8 HHH 9400 3003 5.4 9 III 9500 3004 2.8 10 JJJ 9600 3005 1.5

Here, Table 1 shows a part of the process configuration information stored in the storage device, and lists the software required to provide the HLR service. This information includes the name of each process, the message queue key that the process will use to run, the process number that the HLR system will recognize for itself, and the process version.

After storing the shape information in the process shape information storage unit 16, the process state information collector 12 of the process management block 10 executes the process shape list in the process shape information storage unit 16 as shown in Table 2. It is determined whether or not the registered management target process is running.

On the other hand, the method of determining whether to drive the registered management target process through the process shape list in the process shape information storage unit 16 is the drive process information in the operating system of the drive process information storage unit 17 in the operating system (Table 3) And process shape information (Table 2) stored in the process management block in the HLR system.

For example, if process 1 in the HLR system is running (drive process in the HLR system), and the corresponding process ID is 307 (drive information list in the operating system), the ID is 307 for process ID 1 in the process management block and is currently running. (exist, which means that it is registered in the operating process information list of the operating system).                     

However, if the process 2 in the HLR system is not running (the running process in the HLR system) and the process ID in the process management block does not exist in the operating information list in the operating system, the current operation is performed for the process ID of the information in the process management block. It indicates that it is not (none, meaning that it is not registered in the operating process information list of the operating system), and determines that the process to be managed is suspended.

Here, Table 2 shows a part of the process configuration / status information in the process management block, and the process related information includes the process name, the process number defined by the HLR system, the process ID assigned by the operating system, and the message queue information of the process (eg, , Message queue key, message queue ID, size and number of data remaining in message queue, message queue transmission / reception time, etc.).

Here, Table 3 shows some of the information of the currently running process stored in the operating system. The operating system stores information about processes currently running inside the system in a file format. This information includes all the information necessary for the operation of the process, such as the process ID, process name, process start time, process priority, process size, and process status that the operating system assigns to the process.

Process name Process number Process id Message queue key Message queue ID Last message received time in the message queue Last message send time in the message queue Process status One AAA 8000 307 2000 223 10:15:03 10:15:03 Exist 2 BBB 8100 2001 224 10:02:48 10:02:48 None 3 CCC 8200 581 2002 225 10:15:03 10:15:03 Exist 4 DDD 8300 894 2003 226 10:15:03 10:15:03 Exist 5 EEE 9000 2890 3000 227 10:15:03 10:15:03 Exist 6 FFF 9100 156 3001 228 10:15:03 10:15:03 Exist 7 GGG 9200 4928 3002 12 10:15:03 10:15:03 Exist 8 HHH 9400 3309 3003 13 10:15:03 10:15:03 Exist 9 III 9500 349 3004 14 10:14:03 10:14:53 Exist 10 JJJ 9600 303 3005 189 10:15:03 10:15:03 Exist

Process name Process id Process status Process start time One sched 112 SLEEP 07:03:56 2 FFF 156 SLEEP 11:12:31 3 JJJ 303 SLEEP 10:07:52 4 AAA 307 SLEEP 10:07:51 5 III 349 SLEEP 10:08:02 6 fdflush 1126 SLEEP 03:45:22 7 EEE 2890 SLEEP 09:43:36 8 DDD 894 RUNNING 09:43:36 9 HHH 3309 SLEEP 09:43:41 10 CCC 581 SLEEP 09:43:42 11 -csh 755 SLEEP 19:50:34 12 GGG 4928 SLEEP 10:08:03 ... ... ... ... ...

When the above-described management target process (process 2) is stopped, the corresponding application process is driven using the process driver 14, and then unique information about the process 2 is registered in the process management block 10.

The application process transmits a message including process-specific information, such as a unique process ID and a unique message queue ID, which are granted from the operating system to the process management block 10 immediately after the initialization operation for running the process ends and enters the normal operation state. do. The message processor 13 in the process management block receives this message and changes the corresponding data in the driving process information storage unit 17 in the same operating system.

The process state information collector 12 in the process management block periodically checks whether unique process IDs of managed objects stored in the process state information space are registered in the shape list of the driving process information storage unit 17 in the operating system. If the process unique ID of the management target process is not registered in the operating process information storage unit 17 of the operating system, it is determined that the process is stopped and restarts the process.

In addition, the process management block 10 periodically checks the status information of the message queue of managed processes from the system resource usage information storage unit 15 of the operating system as shown in Table 4 to check whether the process is processing a message normally. .

Here, Table 4 shows a part of information history of the message queue among the system resource usage information stored in the operating system. The operating system manages resources used by a process (eg, working memory, message queues, shared memory, semaphores, etc.) in real time and stores changed information in a specific space. Information about the message queue includes the message queue key assigned to the process, the message queue ID assigned to the message queue key by the operating system, the last time message received in the message queue, the last time message sent in the message queue, and the message sent to that message queue. Block, message size and number of messages left in the message queue, and user information of the message queue.

Message queue ID Message queue key Last message received time in the message queue Last message send time in the message queue Message size remaining in the message queue Message queue number One 12 3002 10:15:03 10:15:03 0 0 2 13 3003 10:15:03 10:15:03 0 0 3 14 3004 10:14:53 10:14:53 0 0 4 223 2000 10:15:03 10:15:03 0 0 5 224 2001 10:02:48 10:02:48 249 3 6 225 2002 10:15:03 10:15:03 40 One 7 226 2003 10:15:03 10:15:03 0 0 8 227 3000 10:15:03 10:15:03 0 0 9 228 3001 10:15:03 10:15:03 0 0 10 189 3005 10:15:03 10:15:03 0 0 ... ... ... ... ... ... ...

If the last send time of a message queue is different from the last send time of a previous cycle, the last receive time is the same as the last receive time of a previous cycle, and the number or size of messages not received in a message queue is above a certain level. It is determined that there is a problem with the operation of the process of receiving a message into the message queue and the process is stored in a special management process (not shown). The process management block 10 determines that an abnormality has occurred in the process operation when a process registered in the special management process counts the number of times of detecting abnormality in the usage information of the message queue at every cycle of checking the status of the process and detects abnormal operation abnormality for a predetermined number of times. Stop or restart a process with or without it.

Process state management method in a mobile communication system according to an embodiment of the present invention will be described with reference to the flowchart of FIG.

First, the process shape list stored in the external storage device and the data predefined for each process are read and collected and stored in the process shape information storage unit 16 (step S41).

The process state information collector 12 of the process management block 10 determines whether there is an interrupted process among the processes to be managed through the process shape list in the shape information storage unit 16 (step S42).

If there is an interrupted process among the management target processes, it is determined that the suspended process exists, and the process is restarted using the process driver 14 (step S43).

After the process state information collection is completed, resource usage information received from the operating system is collected and stored (step S44).

Thereafter, the process management block 10 periodically searches the resource usage information of the management target processes in the system resource usage information storage unit 15 of the operating system to check whether the process is processing the message normally (step S45). In this case, if the message queue last transmission time of the process is different from the last transmission time of the previous cycle to perform normal operation, the last reception time is the same as the last reception time of the previous cycle or the number of messages or messages not received in the message queue. If the size is above a certain level, the process is stored in a special management process (step S46).

Thereafter, the process management block 10 counts the number of times of detecting the use information abnormality of the message queue of the processes registered in the special management process list for each period of checking the status of the process (step S47). It is determined that an abnormality has occurred, and the process is stopped or restarted regardless of the presence or absence of the process (step S48).

FIG. 5 illustrates in more detail the process state management method in the mobile communication system according to the embodiment of the present invention.

First, the process management block 10 reads a list of managed process shapes stored in an external storage device and data predefined in each process in order to manage and recover a managed process during initialization (step S51), and stores process shape information. Collected and stored in the unit 16 (step S52). Here, the collected and stored data is registered in the shape list in the process of the shape information storage unit 16, and the data predefined in step S52 include a process ID (ID), a message queue value, a process version, and a process driving method. .

The process state information collector 12 of the process management block 10 determines whether there is an interrupted process among the processes to be managed through the process shape list in the shape information storage unit 16 (step S53). In this case, the method of determining whether the managed process is driven is determined based on whether unique information (unique ID) of a process registered in the process shape list in the shape information storage unit 16 exists in the drive process information storage unit 17 in the operating system. do.

If the unique process IDs of the management target processes stored in the shape information storage unit 16 do not exist in the operating process information storage unit 17 in the operating system, it is determined that there is an interrupted process, and the process driver 14 To restart the process (step S54). On the other hand, if the unique process IDs of the management target processes stored in the shape information storage unit 16 are present in the operating process information storage unit 17 in the operating system in step S53, it is determined that the suspended process does not exist and is assigned from the operating system. The received resource usage information is collected and stored (step S55).

Thereafter, the process management block 10 periodically checks the resource usage information of the management target processes in the system resource usage information storage unit 15 of the operating system to check whether the process is normally processing a message (step S56). In this case, if the message queue last transmission time of the process is different from the last transmission time of the previous cycle to perform normal operation, the last reception time is the same as the last reception time of the previous cycle or the number of messages or messages not received in the message queue. If the size is above a certain level, the process is stored in a special management process (step S57).

Thereafter, the process management block 10 counts the number of times of detecting the use information abnormality of the message queue of the processes registered in the special management process list for each period of checking the status of the process (step S58). It is determined that an abnormality has occurred, and the process is stopped or restarted regardless of the presence or absence of the process (step S59).

The message processor 13 transmits a message including process-specific information such as a unique process ID (process ID given from the operating system) and a unique message queue ID from an application process immediately after the initialization operation for starting the process is finished and enters the normal operation state. Receive (step S60) to process it.                     

To check the process status checking period during message processing (step S61), at this time, the period for checking the process status is set as small as possible. Subsequently, it is determined whether or not a message including the unique information of the operating system has been transmitted from the newly started process before the set state check period (step S62). When the message including the unique information is transmitted from the corresponding process, the corresponding unique information is determined. To change the process status information in the process status information collector 12 (step S63). However, if a message containing unique information is not transmitted from the process, another message is processed (step S64).

On the other hand, when the process status check cycle during the processing of the message in step S60 returns to the process status checking step of step S51 or less to check the status of each process, if there is a process that is interrupted or abnormal status, and the process after completion of the process It will repeat the process of processing.

Although the preferred embodiments of the present invention have been described in detail above, it will be understood by those skilled in the art that the present invention may be modified or modified in various ways. Therefore, changes of the embodiments of the present invention will not be able to escape the technical scope of the present invention.

As described above, the present invention manages the state of multiple processes by using unique information provided from an operating system and process resource usage information managed by the operating system when the process is running, and thus does not burden the system. By setting the cycle as small as possible, it is possible to accurately determine the state management of the application process close to real time and recover quickly when an abnormal situation occurs.

Claims (5)

Collecting and storing state information of managed objects stored in an external storage device when the HLR is initially driven; Receiving and collecting and storing unique information and resource usage information from an operating system after restarting an interrupted process among the management target processes; Retrieving the state of the message queue based on the resource usage information of the managed target process and checking whether the resource is normally used in the managed target process; If the resource usage is not normally performed, stopping or restarting the corresponding process to be managed according to the number of abnormality detections of the resource usage information. The method of claim 1, In the process of checking whether the resource is normally used in the managed process, If the resource usage is not normal, the message queue last transmission time of the process is different from the last transmission time of the previous cycle, but the final reception time is the same as the last reception time of the previous cycle or the number of messages or message size not received in the message queue. Is greater than or equal to a certain level, it is determined that an abnormality has occurred in the operation of the process of receiving a message to the corresponding message queue, and the process management method in the mobile communication system, characterized in that for storing the management process in a specific management process. The method of claim 1, When the number of abnormality detections of the resource usage information exceeds the reference number by checking the abnormality detection frequency of the resource usage information, it is determined that the abnormality has occurred in the message queue usage information of the managed process registered in the special management process. Process status management method in a mobile communication system, characterized in that to stop or restart the process. The method of claim 1, The process of stopping or restarting the process may include: receiving and processing a message including unique information from an external process; And when the message including the unique information is received from the newly driven process before the status checking period during the processing of the message, changing the process status information using the unique information received from the operating system. How to manage process status in communication systems. The method of claim 1, The resource usage information includes a message queue key assigned to a process, a message queue ID assigned to a message queue key by an operating system, a final message reception time of a message queue, a final message transmission time of a message queue, a block for transmitting a message to a corresponding message queue, Process size management method in a mobile communication system comprising the size and number of messages remaining in the message queue, and user information of the message queue.

Images