KR20080079343A - Server of monitoring for middleware server in mobile communication network and methokd thereof - Google Patents

Server of monitoring for middleware server in mobile communication network and methokd thereof Download PDF

Info

Publication number
KR20080079343A
KR20080079343A KR1020060128394A KR20060128394A KR20080079343A KR 20080079343 A KR20080079343 A KR 20080079343A KR 1020060128394 A KR1020060128394 A KR 1020060128394A KR 20060128394 A KR20060128394 A KR 20060128394A KR 20080079343 A KR20080079343 A KR 20080079343A
Authority
KR
South Korea
Prior art keywords
queue
server
middleware server
waiting
monitoring
Prior art date
Application number
KR1020060128394A
Other languages
Korean (ko)
Inventor
김광희
김원주
Original Assignee
주식회사 케이티프리텔
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 케이티프리텔 filed Critical 주식회사 케이티프리텔
Priority to KR1020060128394A priority Critical patent/KR20080079343A/en
Publication of KR20080079343A publication Critical patent/KR20080079343A/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/56—Queue scheduling implementing delay-aware scheduling
    • H04L47/562—Attaching a time tag to queues
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5601—Transfer mode dependent, e.g. ATM
    • H04L2012/5678—Traffic aspects, e.g. arbitration, load balancing, smoothing, buffer management
    • H04L2012/5681—Buffer or queue management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The present invention relates to a server for monitoring a middleware server in a mobile communication network and a method thereof.

According to the present invention, the monitoring server that checks the queue status of the middleware server in the mobile communication network is the reference value of the number of service requests waiting in the same queue after a specific time when the number of service requests waiting in the queue of the middleware server exceeds the threshold Check again for excess. At this time, if the number of service requests waiting in the same queue exceeds the reference value as a result of re-checking, the middleware server is recognized as a failure and an alarm is generated.

Therefore, due to the processing performance of the middleware server and the temporary congestion of service requests due to the sudden drop in the number of service requests, it is possible to distinguish between a case where it is recognized as a failure and a case where the failure is not a real failure. It is possible to accurately determine the performance of the middleware server without degrading the performance of the middleware server for monitoring by checking again without waiting for the arrival to prevent congestion of the queued request counts.

Description

Server and method for monitoring middleware server in mobile communication network

1 is a diagram schematically illustrating the overall configuration of monitoring a middleware server of a conventional mobile communication network.

2 is a block diagram showing the configuration of a server for monitoring a middleware server of a mobile communication network according to an embodiment of the present invention,

FIG. 3 is a block diagram illustrating a detailed configuration of the queue waiting request number checking unit of FIG. 2.

4 is a diagram schematically illustrating a method of monitoring a middleware server of a mobile communication network according to an embodiment of the present invention.

5 is a diagram illustrating in detail a method of monitoring a middleware server of a mobile communication network according to an embodiment of the present invention.

6 is a view for comparing the check method of the queue wait request number according to the embodiment of the present invention and the conventional check method of the queue wait request number.

The present invention relates to a server for monitoring a middleware server in a mobile communication network and a method thereof. More particularly, the present invention relates to a monitoring server and a method for checking a queue state of a middleware server.

In general, a middleware server functions as an intermediary for connecting systems having different protocols and is usually implemented as an application program.

In general, since a service using a mobile communication network is very extensive, the service is divided into functions and separately constructed as a server providing a corresponding service, and each server is managed by a middleware server.

1 is a diagram schematically illustrating the overall configuration of monitoring a middleware server of a conventional mobile communication network.

As shown in FIG. 1, the middleware manager 14 mounted on the middleware server 10 includes a plurality of servers 12 (eg, A server, B server, and C server) 12 that provide mobile communication services classified by functions. Connection between the clients 20 (eg, Client 1, Client 2,..., Client N) 20 that desires the service provided by each server 12 is mediated. At this time, the number of requests to each server of each client 20 waits for a predetermined time in the server-specific queue 16 and is released.

Here, the server 30 monitoring the middleware server 10 monitors the performance of the middleware server 10 by checking whether the number of requests waiting for the server-specific queue 16 exceeds a specific reference value.

The server 30 monitoring the middleware server 10 operates a so-called “early warning system” that notifies the manager and operator by SMS, mail, or telephone when the number of requests waiting in the queue 16 exceeds a certain threshold. .

Taking this “early warning system” as an example, it is assumed that the threshold for alarming corresponds to the case where there are 90 requests waiting for the queue 16. In addition, A server 12 is capable of 10 processes in multiple operations, and the processing performance of A server 12 is regarded as 0.1 second per case.

At this time, when the monitoring server 30 checks the number of requests waiting for the corresponding queue 16 of the server 12, when 100 clients 20 call the service of the server A 12, the corresponding queue 16 It is determined that 100 requests are pending, and an alarm is triggered because 10 thresholds have been exceeded.

However, after 1 second, the number of requests waiting for the queue 16 is all resolved, and the client 20 is normally in a service state. That is, the server A 12 can resolve the number of ten service requests in one second, and thus, even though an alarm is sounded, all 100 waiting requests are processed after one second.

Therefore, there is a problem that an alarm occurs even in a normal case where there is no problem on the middleware server.

In addition, there is no distinction between an alarm occurrence due to a temporary congestion of waiting requests in the queue and an alarm occurrence when an actual abnormality occurs, thereby causing confusion in management.

Accordingly, an aspect of the present invention is to provide a monitoring server and a method for accurately monitoring a queue state of a middleware server so that an alarm sounds when an actual service delay occurs without increasing the load of the middleware server.

Monitoring server according to the characteristics of the present invention in order to achieve the problem as described above,

In the monitoring server that checks the queue status of the middleware server in the mobile communication network, if the number of service requests queued in the middleware server queue exceeds the threshold, whether the number of service requests queued in the same queue after a specific time elapses A queue waiting request number checking unit for checking again; And an alarm generator for recognizing a failure of the middleware server and generating an alarm when the number of service requests queued to the same queue exceeds a reference value as a result of the check again.

Monitoring method according to a feature of the invention,

A monitoring method in which a monitoring server checks a queue state of a middleware server in a mobile communication network, the monitoring method comprising: checking, by the monitoring server, the number of service requests waiting in each queue of the middleware server; Checking whether the number of service requests queued to each of the checked queues exceeds a reference value and re-checking whether the number of service requests waiting for the same queue exceeds the reference value after a specific time when the number of service requests queued to the checked queue exceeds the reference value; And recognizing a failure of the middleware server when the reference value is exceeded as a result of the reconfirmation.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

In addition, when a part is said to "include" a certain component, this means that it may further include other components, except to exclude other components unless otherwise stated.

In addition, the term module described herein refers to a unit for processing a specific function or operation, which may be implemented in hardware or software, or a combination of hardware and software.

Now, a server and a method for monitoring a middleware server in a mobile communication network according to an embodiment of the present invention will be described in detail with reference to the drawings.

2 is a block diagram showing the configuration of a server for monitoring the middleware server of the mobile communication network according to an embodiment of the present invention, Figure 3 is a block diagram showing the detailed configuration of the queue wait request number confirmation unit of FIG.

According to FIG. 2, the monitoring server 300 includes a middleware server interface unit 320, a queue waiting request number checking unit 340, and an alarm generating unit 360.

The middleware server interface unit 320 is connected to the middleware server 100 to perform an interfacing function for exchanging requests and corresponding information between the middleware server 100 and the monitoring server 300.

The queue waiting request count checking unit 340 checks whether the number of requests waiting for each queue 160 of the middleware server 100 exceeds a reference value, and if it exceeds, checks whether the request count exceeds the reference value again after 1 second to 2 seconds. do.

In this case, when the configuration of the queue waiting request number checking unit 340 is described in detail, the first queue waiting request number checking module 342, the threshold value determination module 344, and the second queue waiting request number checking module 346 are described. ).

The first queue wait request number check module 342 checks the number of queue wait requests of the middleware server 100 at predetermined intervals. In this case, the predetermined period may be selected within a range of minimizing the load of the middleware server 100. According to an embodiment, a minute unit is preferable and it can select from the range which belongs specifically within 3 to 5 minutes.

The threshold value determination module 344 determines whether the number of queue wait requests checked by the first queue wait request number check module 342 exceeds the threshold. In this case, the reference value means a maximum value of the number of requests that can wait in the queue 160 according to the processing performance of the number of requests for each server (A server, B server, C server) 120 of the middleware server 100 in advance. Is set to. At this time, each server 120 is divided into service functions such as a service subscription function and an additional service setting function of the mobile communication network.

When the second queue wait request number check module 346 exceeds the reference value as a result of the determination by the determination module 342, the second queue waiting request check module 346 performs another check on the corresponding queue 160. At this time, the check period has a value within a preset period of the first queue waiting request number check module 342 and the number of requests for each server (A server, B server, C server) 120 of the middleware server 100. This value considers processing performance. According to the embodiment, the unit of seconds is preferred, and specifically, it may be selected within the range of 1 second to 2 seconds. That is, when the request processing performance of the corresponding server 120 is made in units of seconds, the number of requests that can be quickly resolved according to the processing performance is to be excluded from the range of exceeding the reference value.

Here, if the threshold value determination module 344 determines that the threshold value is exceeded even when the second queue wait request count check module 346 checks the queue wait request number check, it determines that there is a failure in the performance of the middleware server 100. Alert generation is requested to the alert generator 400.

The alarm generator 400 continuously alerts the number of requests waiting for each queue 160 of the middleware server 100 when the number of requests waiting for the queue waiting request confirmation unit 340 exceeds the reference value. Occurs.

Then, the monitoring method according to the configuration as described above will be described.

4 is a diagram schematically illustrating a method of monitoring a middleware server of a mobile communication network according to an embodiment of the present invention.

According to FIG. 4, the monitoring server 300 of FIG. 2 or 3 requests the queue waiting state check to the middleware server 100 of FIG. 2 (S101).

In addition, the monitoring server 300 checks the number of service requests of the client (200 of FIG. 2) waiting in each queue of the middleware server 100 (S103).

The monitoring server 300 checks again after a specific time when the number of service requests of the client 200 waiting in each queue checked in step S103 exceeds a reference value (S105).

At this time, if the number of pending requests in the queue exceeds the reference value, the middleware server 100 recognizes the failure and generates an alarm (S107).

5 is a diagram illustrating in detail a method of monitoring a middleware server of a mobile communication network according to an embodiment of the present invention.

According to FIG. 5, the monitoring server 300 requests the middleware server 100 to check a queue waiting state at a predetermined cycle (S201), so that the monitoring server 300 waits for each queue 160 of the middleware server 100. The number of service requests is checked (S203). Here, the predetermined period may be in minutes according to the embodiment.

At this time, the monitoring server 300 determines whether the number of service requests of the client 200 waiting in each queue 160 checked in step S203 exceeds a reference value (S205).

If it is determined that the reference value is not exceeded, steps S201, S203, and S205 are repeated.

As a result of the determination, if the reference value is exceeded, it is determined whether the number of service requests of the client 200 waiting for the same queue after the specific time passes exceeds the reference value (S207). Here, the specific time is a value in consideration of the processing performance of each server 120 of the middleware server 100 may be a second unit in an embodiment.

At this time, if the reference value is also exceeded, it is recognized that the number of requests waiting in each queue 160 is stagnant and generates an alarm (S209).

In addition, if the reference value is not exceeded, the number of requests waiting in each queue 160 is recognized as a temporary congestion, and the steps S201, S203, and S205 are repeated after a predetermined period.

6 is a diagram for comparing a check method of the number of queue wait requests according to an embodiment of the present invention and a check method of a conventional queue wait request number.

First, FIG. 6A is a graph illustrating a monitoring measurement result according to a conventional method of checking the number of queue waiting requests.

Here, the check period of the number of queue wait requests is made in units of 5 minutes. At this time, the reference value of the queue waiting request number for the alarm is "100".

According to FIG. 6A, when the check period of the number of queue wait requests is 10 minutes (P101), it can be seen that the number of queue wait requests drops rapidly after 1 second. In this case, it is not a real fault, but it is a case of alarming due to a fault.

In addition, if the check period of the queue wait request number corresponds to 30 to 45 minutes (P103), even though the queue wait request count is congested for more than 15 minutes, since the check cycle is 5 minutes, the first check period is 30 minutes later. There is a situation where the number of queued requests is congested until 35 minutes are reached. In this case, the service is clearly delayed, and the client side can feel the delay.

Therefore, according to the conventional check method of the number of queue wait requests, the case where it is not a real failure and a real disabled person is not distinguished, and in the case of a real disabled person, the congestion of the number of queue wait requests continues until a check cycle arrives. Couldn't solve it.

6B is a graph illustrating a monitoring measurement result according to a check method of the number of queue waiting requests according to an embodiment of the present invention.

In FIG. 6B, the check period of the number of queue wait requests is made in units of 5 minutes. At this time, the reference value of the queue waiting request number for the alarm is "100".

According to FIG. 6B, since the reference value is exceeded in the 10-minute check period P105, a check is performed again after 1 to 2 seconds, but since the number of queue waiting requests is reduced to within the reference value, no alarm is generated.

In addition, in the 30-minute check period P107, the reference value is also exceeded, so it is checked again after 1 to 2 seconds, and since the number of queue waiting requests still exceeds the reference value, it is determined as an actual failure and an alarm is generated.

Therefore, according to an exemplary embodiment of the present invention, a case in which a disability is recognized as a disability and a case in which a disability is actual as a 30-minute check period may be distinguished. In addition, in the case of the 30-minute check cycle, the check is performed again without waiting for the check cycle to arrive so that the congestion of the queue wait request counts does not continue.

The embodiments of the present invention described above are not implemented only through the apparatus and the method, but may be implemented through a program for realizing a function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded. Implementation may be easily implemented by those skilled in the art from the description of the above-described embodiments.

The scope of the present invention is not limited to the above-described embodiments, but various modifications and improvements of those skilled in the art using the basic concept of the present invention as defined in the following claims are also within the scope of the present invention.

As described above, according to the exemplary embodiment of the present invention, the performance of the middleware server can be accurately determined without degrading the performance of the middleware server for monitoring.

Claims (8)

A monitoring server for checking a queue state of a middleware server in a mobile communication network, A queue waiting request number checking unit for re-confirming whether or not the number of service requests waiting in the same queue is exceeded after a specific time elapses when the number of service requests waiting in the queue of the middleware server exceeds a reference value; And The alarm generation unit for recognizing the failure of the middleware server and generating an alarm when the number of service requests waiting in the same queue exceeds the reference value as a result of the check again Monitoring server comprising a. The method of claim 1, The queue waiting request number confirmation unit, A first queue waiting request number checking module for checking a queue waiting request number of the middleware server at a predetermined period; A threshold value determination module for determining whether the number of queue wait requests of the middleware server checked by the first queue wait request number check module exceeds a reference value; And And a second queue wait request count check module for checking the number of queue wait requests for the same queue after a specific time elapses when the threshold value is exceeded as determined by the determination module. The monitoring server for determining whether the threshold value exceeded the alarm generation unit to generate an alarm when the threshold value exceeds the threshold value as checked by the second queue wait request number check module. The method according to claim 1 or 2, The predetermined period is a minute unit and the monitoring time, characterized in that the second unit. The method of claim 3, The specific time, Monitoring server, characterized in that set to a value corresponding to the processing time of the number of queue waiting requests of the middleware server. In the monitoring method for the monitoring server checks the queue status of the middleware server in the mobile communication network, Checking, by the monitoring server, the number of service requests queued to each queue of the middleware server; Reconfirming whether the number of service requests waiting for the same queue exceeds the reference value after a specific time when the number of service requests queued to each of the checked queues exceeds the reference value; And Generating an alarm by recognizing a failure of the middleware server when the reference value is exceeded as a result of the reconfirmation; Monitoring method comprising a. The method of claim 5, Prior to the checking step, Requesting the middleware server to check each queue waiting state of the middleware server at predetermined intervals Monitoring method further comprising a. The method of claim 6, Reconfirming step, And reconfirming whether or not the number of service requests exceeding the threshold is exceeded for a queue in which the number of service requests exceeding the threshold after the specific time, which is the second within the preset period, is a minute. The method of claim 7, wherein The specific time, And a value corresponding to a processing time of the number of queue waiting requests of the middleware server.
KR1020060128394A 2006-12-15 2006-12-15 Server of monitoring for middleware server in mobile communication network and methokd thereof KR20080079343A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020060128394A KR20080079343A (en) 2006-12-15 2006-12-15 Server of monitoring for middleware server in mobile communication network and methokd thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020060128394A KR20080079343A (en) 2006-12-15 2006-12-15 Server of monitoring for middleware server in mobile communication network and methokd thereof

Publications (1)

Publication Number Publication Date
KR20080079343A true KR20080079343A (en) 2008-09-01

Family

ID=40020282

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020060128394A KR20080079343A (en) 2006-12-15 2006-12-15 Server of monitoring for middleware server in mobile communication network and methokd thereof

Country Status (1)

Country Link
KR (1) KR20080079343A (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012033237A1 (en) * 2010-09-07 2012-03-15 현대자동차주식회사 System testing method
WO2013049006A2 (en) * 2011-09-26 2013-04-04 Visa International Service Association Monitoring and limiting requests to access system resources
US9354996B2 (en) 2010-06-28 2016-05-31 Hyundai Motor Company System test apparatus
CN110738782A (en) * 2019-10-24 2020-01-31 名创优品（横琴）企业管理有限公司 cashier queuing analysis method and system
WO2024058294A1 (en) * 2022-09-15 2024-03-21 쿠팡 주식회사 Electronic device operation method for processing information, and electronic device for supporting same

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9354996B2 (en) 2010-06-28 2016-05-31 Hyundai Motor Company System test apparatus
WO2012033237A1 (en) * 2010-09-07 2012-03-15 현대자동차주식회사 System testing method
CN103109276A (en) * 2010-09-07 2013-05-15 现代自动车株式会社 System testing method
KR101438990B1 (en) * 2010-09-07 2014-09-05 현대자동차주식회사 System testing method
CN103109276B (en) * 2010-09-07 2016-01-20 现代自动车株式会社 System detection method
WO2013049006A2 (en) * 2011-09-26 2013-04-04 Visa International Service Association Monitoring and limiting requests to access system resources
WO2013049006A3 (en) * 2011-09-26 2013-07-04 Visa International Service Association Monitoring and limiting requests to access system resources
US9313215B2 (en) 2011-09-26 2016-04-12 Visa International Service Association Monitoring and limiting requests to access system resources
CN110738782A (en) * 2019-10-24 2020-01-31 名创优品（横琴）企业管理有限公司 cashier queuing analysis method and system
WO2024058294A1 (en) * 2022-09-15 2024-03-21 쿠팡 주식회사 Electronic device operation method for processing information, and electronic device for supporting same

Similar Documents

Publication Publication Date Title
US8010840B2 (en) Generation of problem tickets for a computer system
US20110119372A1 (en) Message management and suppression in a monitoring system
US9584617B2 (en) Allocating cache request in distributed cache system based upon cache object and marker identifying mission critical data
JP5418250B2 (en) Abnormality detection apparatus, program, and abnormality detection method
US20090024722A1 (en) Proxying availability indications in a failover configuration
US7586956B1 (en) Intelligent event notification processing and delivery at a network switch
JP2012521607A (en) Distributed application monitoring
KR20080079343A (en) Server of monitoring for middleware server in mobile communication network and methokd thereof
EP3264723A1 (en) Method, related apparatus and system for processing service request
CN110740072A (en) fault detection method, device and related equipment
CN112286770A (en) Alarm notification method, device, computer equipment and storage medium
EP2541418A1 (en) Method for increasing reliability in monitoring systems
JP2006501717A (en) Telecom network element monitoring
EP3680780B1 (en) Cluster system, control method, and corresponding computer program
US7523206B1 (en) Method and system to dynamically apply access rules to a shared resource
CN112448987A (en) Fusing degradation triggering method and system and storage medium
JP2004206634A (en) Monitoring method, operation monitoring device, monitoring system, and computer program
US11811834B2 (en) Lawfully intercepting traffic and providing the traffic to a content destination based on content destination availabilities and priorities
CN107025148B (en) Mass data processing method and device
US11223578B2 (en) System and control method to direct transmission of event data to one of a plurality of reception queues
KR102560230B1 (en) Automatic processing and distribution method of monitoring policy based on cloud-based client operation analysis results
JP2000148539A (en) Fault detecting method, computer system, constitutional device, and recording medium
KR20000018954A (en) Processing management method of a hlr(home location register) system in mobile communications
US20240080239A1 (en) Systems and methods for arbitrated failover control using countermeasures
KR100623554B1 (en) Intrusion Tolerant Technologies of DNS and DHCP Server for Survival of Internet Service

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E601 Decision to refuse application