KR100283994B1 - HLR data management device in personal communication exchange system - Google Patents

Abstract

The present invention relates to an apparatus for managing data of a home location center (HLR) in a personal communication exchange system.

This invention comprises an active data collector for collecting a count value from an active subscriber database; Active performance data collecting means for collecting performance data via an active data collector or directly from a subscriber database; Standby performance data collection means which is activated when processor utilization data is requested from the active performance data collecting means through the IPC, and transmits its processor utilization rate to the active performance data collecting means; A standby data collector for delivering the count value collected from the standby subscriber database to the active data collector via IPC; Event collecting means for collecting information on an event and an alarm generated while performing predetermined procedures; And receiving performance data from the active performance data collecting means by scanning through a socket connected at predetermined time intervals, receiving and managing event and alarm information from the active event collecting means, and managing the management information to a higher operation maintenance center. This includes the transmitting agent.

Description

Apparatus for managing HLR data in a PCS system

The present invention relates to an apparatus for managing data of a home location center (HLR) in a personal communication exchange system.

With the development of mobile communication technology, personal communication system (PCS) has been introduced to satisfy human desire to communicate freely with anyone at any time, anywhere, and provides commercial services. This personal communication system manages the operation of the entire system in the operation and maintenance center. As such, the subscriber information processing device (HLR) that stores the subscriber's information among the objects managed by the operation and maintenance center is the most important management object, and thus requires redundancy. And in order to manage the performance and event data of the dual subscriber information processing apparatus it is necessary to introduce a management agent (Agent) to manage more actively.

Accordingly, the present invention has been proposed to meet the above necessity, and an object thereof is to provide an HLR data management apparatus in a personal communication exchange system capable of collecting and managing redundant HLR data.

In order to achieve the above object, an apparatus of the present invention includes an active data collector for collecting a count value from an active subscriber database; Active performance data collecting means for collecting performance data through the active data collector or directly from a subscriber database; Standby performance data collecting means which is activated when processor utilization data is requested from the active performance data collecting means through the IPC to transfer its processor utilization rate to the active performance data collecting means; A standby data collector for delivering a count value collected from a standby subscriber database to the active data collector via IPC; Event collecting means for collecting information on an event and an alarm generated while performing predetermined procedures; And receiving performance data from the active performance data collecting means by scanning through a socket connected at predetermined time intervals, receiving and managing event and alarm information from the active event collecting means, and managing the management information to a higher operation maintenance center. Characterized in that it comprises a management agent for transmitting.

1 is a block diagram showing the configuration of a typical personal communication system suitable for application of the present invention;

2 is a block diagram of an HLR management system according to the present invention;

3 is a conceptual diagram illustrating communication between a performance data collection process and a management agent according to the present invention;

4 is a schematic diagram illustrating a socket message type passed to a performance data collection process;

5 is a format diagram showing the structure of a socket message;

6 is a schematic diagram illustrating an IPC message type;

7 is a format diagram showing a structure of an IPC message;

8A and 8B illustrate a procedure of processing while the performance data collection process is started;

9 is a flowchart illustrating processing when communication is requested from a management agent.

* Explanation of symbols for main parts of the drawings

100: personal communication exchange (PCX / VLR)

101: public telephone network (PSTN) 102: common line signaling network

103a: cell 110: subscriber information processing device (HLR)

120: OMC 130: Short Message Center (SMC)

140: voice mailing system (VMS) 150: billing center (CAMA)

160: base station controller (BSC) 170: base station transceiver (BTS)

180a, 180b: mobile phone (MS)

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

1 is a block diagram showing the configuration of a typical personal communication system suitable for applying the present invention. As shown in FIG. 1, the personal communication system is a base station transceiver (BTS: 170) distributed in a service area and forming a micro cell or macro cell 103a, and a base station controller (BSC: 160) for managing the base station transceivers. ), Personal communication switch (PCX / VLR: 100) to which the base station controller is connected, voicemail system (VMS: 140), short message center (SMC: 130), subscriber information processing device (HLR: 110), operation preservation center (OMC) 120, the billing center (CAMA) 150 is configured to enable communication between the mobile telephone 180a and the landline telephone 104 or during the mobile telephone period.

In this case, the personal communication switch 100 has a visitor registration (VLR) function, and is connected to a public telephone network (PSTN) 101 and a common line signal network 102. The common line signal network 102 is connected to a short message center (SMC: 130), a voice mailbox system (VMS: 140), and a subscriber information processing device (HLR: 110), and an operation preservation center (OMC: 120) and subscriber information. The processing unit (HLR) 110, the personal communication switch (PCX / VLR: 100), and the base station controller (BSC: 160) are connected to the TMN Q3.

Referring to FIG. 1, the personal communication switch 100 and the subscriber information processing device 110 are connected through the common line signal network 102, and the protocol defines not only basic call processing information but also information flow for various additional services. It is defined as PAP (PCS Application Part) based on IS-41.C, and the protocol between the personal communication switch 100 and the base station controller 160 is an open structure that is easy to evolve and provide various wireless access methods. A-interface protocol based on TIA / EIA / IS-634. The interface between the operation maintenance center 120 and the system unit elements uses a TMN based Q3 interface to efficiently manage other network components.

The PCX / VLR switch 100 is divided into a central control subsystem, a network control subsystem, and a matching exchange subsystem, each of which includes a main processor (MP), a peripheral processor (PP), and peripheral devices. The personal communication switch 100 performs an ASS-W for providing a call processing function by connecting a wireless base station to a conventional TDX-10 series switch, and performs a function of storing and managing information for a mobile subscriber and a routing function. The LRS is added and the location of the VLR is located in the upper part of the exchange system (CIPCU) for mobile call processing and mobility management function processing, and is capable of communicating via high-speed IPC. In such a personal communication system, authentication and encryption functions, location registration and handover functions are required for PCS mobile call processing and mobility management.

2 is a block diagram of an HLR management system according to the present invention. Referring to FIG. 2, the HLR management system includes a manager 210: a manager, a management agent 220: an agent, an active subscriber information processing device (HLR_A: 230), and a standby subscriber information processing device (HLR_B: 240). The active and standby subscriber information processing apparatus 230 or 240 is composed of a performance data collection process (hLRAgent_ifd: 231, 241), an event collection process (hLRAgent_efd: 232, 242), and a data collector (dc: data collector, 233, 243). Here, the dotted line indicates a standby state, the duplicated HLR_A 230 and the HLR_B 240 have the same data, and the data collectors 233 and 243 are connected by IPC.

The manager 210 is located in an operation and maintenance center (OMC) and is interfaced with a management agent (AGENT: 220) and TMN-Q3 based on the OSI hierarchy to receive data of a management target at predetermined time intervals or as necessary. .

The manager receives a report from the management agent based on the time set by the manager, and the management agent (AGENT: 220) and the performance data collection process 231 of the active state based on the internally set time (eg, 1 second). It communicates with PAP (PCS Application Part) based on IS-41.C, DB, processor usage rate and subscriber information periodically to update management object instance of management agent. By having two different periods in this way (the management agent has a short period), the management agent can cause the QoS (Quality-of-Service) alerting period reported to the manager to be taken asynchronously. Will be.

At this time, the performance data collection process 231 takes the information about the DB and PAP from the data collector 233, and processes the processor utilization rate and the subscriber information by itself. The event collection process 232 detects all events and alarms occurring in the HLR equipment and delivers them to the management agent 220 so that the administrator can know them. The management agent 220 and the HLR_A 230 and the HLR_B 240 are connected through the IEEE 802.3 interface, and the HLR_A 230 and the HLR_B 240 are implemented on the OMNI platform of DGM & S.

3 is a conceptual diagram illustrating communication between a performance data collection process (hLRAgent_ifd) and a management agent according to the present invention. Referring to FIG. 3, when the management agent's scanning process (dtsscand: 310) requests the performance data from the performance data collection process 231 or 241 at regular intervals, the performance data collection process 231 or 241 may be a TCP socket ( Pass the data through Socket.

At this time, the transmitted data includes data for each control message type (hLRPAPCurrentData: 301), data access information data (hLRDBCurrentData: 302), and processor utilization rate (processor current data) according to the PAP (PCS Application Part) protocol based on IS-41.C. 303), subscriber information (hLRDATA: 304), and the like.

Here, the subscriber information (hLRDATA: 304) is a management object reflecting the characteristics of the HLR and is an instance created to view the subscriber information from the operator's position.

In the embodiment of the present invention, since there are 26 PAP instances 301, one database instance 302, two processor utilization instances 303, and one subscriber information instance 304, all 30 instances. If you open a port with a TCP socket, you will waste HLR and management hardware resources. In order to eliminate such waste, the embodiment of the present invention implements a scan process (dtsscand: 310) for communicating with the performance data collection process 231 or 241 inside the management agent, and then opens only one socket and periodically stores each data. Scan and read each data sequentially and update the value of each instance.

4 is a schematic diagram illustrating a socket message type delivered to a performance data collection process, and FIG. 5 is a format diagram illustrating a structure of a socket message.

The communication between the management agent (220 in FIG. 2) and the HLR (230,240) is a method using a TCP socket and an IPC method, and the IPC method is divided into a named pipe or a FIFO and OMNI IPC, which is a system V series. Can be. Here, OMNI IPC is an IPC method provided by DGM & S 'OMNI platform, which is a kind of message queue.

Referring to FIG. 4, when the HLR_DATA_REQ message is received from the management agent's scan process 310, the performance data collection process 231 or 241 transmits an HLR_DATA_RESULT message including subscriber data, and when the HLR_PROCESSOR_DATA_REQ message is received, the processor Send an HLR_PROCESSOR_DATA_RESULT message containing the usage rate. When the HLR_DB_DATA_REQ message is received, the HLR_DB_DATA_RESULT message containing the database information is transmitted. When the HLR_PAP_DATA_REQ message is received, the HLR_PAP_DATA_RESULT is transmitted. When the HLR_MMC_DATA_REQ message is received, the HLR_MMC_DATA_RESULT message is transmitted.

That is, the PAP instance 301 of FIG. 3 is passed from the performance data collection process 231 or 241 to the scan process 310 by the HLR_PAP_DATA request and result message, and the database instance 302 is attached to the HLR_DB_DATA request and result message. Is transferred from the performance data collection process 231 or 241 to the scan process 310, and the processor utilization instance 303 is transferred from the performance data collection process 231 or 241 to the scan process 310 by an HLR_PROCESSOR_DATA request and result message. The subscriber information instance 304 is communicated from the performance data collection process 231 or 241 to the scan process 310 by HLR_DB_DATA request and result message.

As such, the data format of the message transmitted through the socket between the management agent's scanning process 310 and the performance data collection process 231 or 241 is shown in FIG. 5, type and data length. ), Consisting of data.

6 is a schematic diagram showing an IPC message type, and FIG. 7 is a format diagram showing the structure of an IPC message.

Referring to FIG. 6, the hLRPAP of the performance data collection process 231 or 241 sends an IPC_COUNTER_REQ message to the data collector 233 or 243, and accordingly the data collector 233 or 243 sends an IPC_COUNTER_RET message to the hLRPAP. The hLRDB sends an IPC_COUNTER_REQ message to the data collector 233 or 243, and accordingly the data collector 233 or 243 sends an IPC_COUNTER_RET message to the hLRDB.

The active performance data collection process (ACTIVE hLRAgent_ifd: 231) requests the processor utilization information through the IPC_PROCESSOR_REQ message to the standby performance data collection process (STDBY hLRAgent_ifd: 241). STDBY hLRAgent_ifd) transmits the IPC_PROCESSOR_RET message to the active hLRAgent_ifd and adds it together. On the other hand, hLRData of the performance data collection process collects the data requested by the inquiry from the HLR database. As described above, the format of the message transmitted through the IPC is a header hdr, an index or a processor type (pro_type), a count value (Count_t), or a process utilization rate (proc_util), and a header ( hdr consists of a destination index (dest_index), a destination (destination), and a message type.

In this manner, the performance data collection process (hLRAgent_ifd: 231 or 241) communicates with the scan process (dtsscand: 310) by a socket and the data collector (data collector) 233 or 243 by IPC.

8A and 8B are procedures for processing performance data collection process 231 or 241 as they are started, and FIG. 9 is for processing when communication is required from management agent 220 after startup (ie, data is required). It is a procedure. 8A and 8B, in operation 801, the user determines his state as active or standby at startup, and performs operations 803 to 807 when restarting in operation 802. In step 803, if the state variable is ACTIVE, the state becomes ACTIVE in step 804. In step 805, if the state variable is STANDBY, the state becomes standby in step 806. ) If not in the active and standby state, the state is set to an idle state in step 807.

In step 808, the queue is initialized, and in step 809, a socket is connected. After checking whether the socket connection is successful in step 810, if the failure is notified, an event occurrence is reported in step 811. If the socket connection is successful, the database DB is connected in step 812. Subsequently, if the database connection fails in step 813, an event occurrence is reported in step 814. If the database connection is successful, the communication standby state is maintained in step 815.

As described above, the performance data collection process waits for communication after completing the startup. If communication is requested by the scan process 310 at predetermined time intervals, steps 821 to 832 are performed as shown in FIG. 9. That is, polling is necessary because the required data must be taken sequentially.

If communication is requested in step 821 by the scan process dssscand 310, the scan process polls (ie, scans) the process to obtain the data required in step 822. If the poll fails, the event is reported in step 824. If polling is successful, it is determined whether the IPC communication is performed in step 825. If IPC communication is performed, IPC communication is performed according to the IPC message format shown in FIG. 7 (step 826). .

If the result of the determination in step 825 is not IPC communication, it is determined in step 829 that the socket is used. If the socket is socket, the socket communication is performed in step 830. If the socket communication fails in step 831, the event is reported in step 832.

The event generated in this way is collected by the event collection process (hLRAgent_efd: 232 or 242), and delivered to the management agent (Agent: 220).

As described above, the present invention prevents the loss of important data by duplexing and managing HLR data, and the management agent requires communication by collecting and managing the performance and event data of the duplicated HLR at regular intervals. There is an effect that can actively manage the management state while saving resources.

Claims (1)

An active data collector for collecting a count value from an active subscriber database; Active performance data collecting means for collecting performance data through the active data collector or directly from a subscriber database; Standby performance data collecting means which is activated when processor utilization data is requested from the active performance data collecting means through the IPC to transfer its processor utilization rate to the active performance data collecting means; A standby data collector for delivering a count value collected from a standby subscriber database to the active data collector via IPC; Event collecting means for collecting information on an event and an alarm generated while performing predetermined procedures; And Receives performance data from the active performance data collection means by scanning through a socket connected at predetermined time intervals, receives and manages event and alarm information from the active event collection means, and transmits the management information to a higher operation maintenance center. HLR data management device in a personal communication exchange system, characterized in that it comprises a management agent.

Images