JPH11355273A - System and method for guarantee of information data by udp in network management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system for guaranteeing information data in generating an event from a network element(NE) by using a UDP/IP protocol. SOLUTION: A sequence number management part 103 interprets an NE identifier, a sequence number, event generation time information added to a header part of an event informed of by an UDP layer, monitors which kind of UDP event is generated when and at which NE, and monitors whether there are the sequence numbers left out by confirming continuity of the sequence numbers. A retransmission demand decision means 102 receives information transmitted by the sequence number management part 103 on how serious a problem with respect to continuity of the sequence numbers exists in which kind of event at which NE, and decides on the basis of a situation of the network and a CPU load situation if retransmission of a missed event kind is immediately demanded of the NE through a TCP/IP.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a network management system, and more particularly, to the generation of an event from an NE (Network Element) to a UDP (User Datagram Protocol).
l) It relates to a system that guarantees notification data when performing using l).

[0002]

2. Description of the Related Art Conventionally, network elements (Networ
k Element, referred to as “NE”), the occurrence of an event from a network management system (Network Management Sys
tem, referred to as “NMS”) as connectionless UDP (User Datagram Protocol) /
When using the IP (Internet Protocol) protocol,
Network congestion, NE side and NMS side CPU
There is a high possibility that the UDP packet is discarded due to the load, and the states of the NE and the NMS may be different.

As a workaround, when an abnormal state occurs, all information such as attribute values held in the NE is stored in the NMS.
Side, it is necessary to match the status, NE side, N
The time and load have been placed on the CPU processing on the MS side and the operation status of the network.

[0004] Further, in the case where the processing for adjusting the state is performed in a network where the UDP is discarded, or in the load state of the CPU on the NE side or the NMS side, the processing itself may cause further loss of UDP packets. There is.

[0005]

As described above, as described above, a network management system (N
equipment (NE: N)
Alarms, status change notifications, and attribute change notifications are sent from UDP (User Datagram Protocol) /
When an NMS is notified by an event notification by an IP (Internet Protocol) protocol, and the NMS manages various states of the NE by the event notification, the event notification by the UDP is transmitted to the network congestion, the NE or the NMS. However, if the information is discarded due to the load of the CPU processing, the consistency of information between the NE and the NMS cannot be guaranteed.

[0006] Further, when performing processing for adjusting the state in a network where the UDP is discarded, or in the load state of the CPU on the NE side and the NMS side, the CPU processing on the NE side and the NMS side and the operating state of the network include: There is a problem in that time and load are required, and the matching process itself may cause further loss of UDP packets.

Accordingly, the present invention has been made in view of the above problems, and has as its object to provide a system and method for guaranteeing notification data when an event from an NE is performed using the UDP / IP protocol. To provide.

[0008]

In order to achieve the above object, the present invention is directed to a network management system which manages various states of a network element by an event notification from the network element. If the event notification is discarded, the minimum necessary data is retransmitted from the network element at an appropriate timing by the TCP / IP protocol, thereby ensuring data consistency between the network element and the network management system. It is made possible.

[0009] The present invention is based on the network element U
Interpret the network element identification information, sequence number, and event occurrence time information added to the header part of the event transmitted by the DP / IP protocol and notified from the UDP layer, and determine which type of UDP event occurs in which network element and when. By monitoring whether or not the sequence number has occurred, by confirming the continuity of the sequence number, a sequence number management unit that monitors whether there is no omission in the sequence number, and when there is no continuity in the value of the sequence number, Receives information about which event type of which network element has had a problem with the continuity of the sequence number transmitted from the sequence number management means, and based on the network status and the CPU load status of the network management system, , The missing event type CP / IP protocol by either requiring immediate retransmission to the network element, including a retransmission request determining means for determining whether to suspend a retransmission request until the time when the retransmission condition is ready.

[0010]

Embodiments of the present invention will be described below. According to the preferred embodiment of the present invention, when the event notification by the UDP is discarded, the minimum necessary data is transmitted by the TCP (Transmission Control).
Protocol / IP (Internet Protocol) recollection is performed at an appropriate timing to ensure data consistency between the NE and the NMS.

[0011] A network management system (Network Management System, "NM
S), the device (Network Element,
“NE”), alarms, status change notifications, and attribute change notifications are sent from UDP (User Datagram Protocol) / IP
(Internet Protocol) is notified to the NMS by an event notification according to the protocol. In the NMS, when the various states of the NE are managed by the event notification, the NMS is notified.
If the event due to is discarded due to network congestion or the load on the CPU processing of the NE or NMS, N
In order to address the problem that the information consistency between E and NMS is not guaranteed, the present invention includes the following means.

That is, in a preferred embodiment of the present invention, the NE identification information, the sequence number, and the event occurrence added to the header of an event transmitted from the NE by the UDP / IP protocol and notified from the UDP layer. Sequence number management means for interpreting the time information, monitoring which type of UDP event has occurred in which NE and when, and confirming the continuity of the sequence numbers to monitor whether there are any missing sequence numbers; When the sequence number value has no continuity, information is transmitted from the sequence number management means, which NE and which event type has a problem with the sequence number continuity and how much, Based on the network status and the NMS CPU load status, Wherein the P / IP protocol N
Retransmission request determination means for determining whether to request retransmission immediately to E or to suspend the retransmission request until a condition for retransmission is satisfied. The sequence number management means determines the type of the event from the sequence number in the header portion of the event based on a sequence number rule indicating the correspondence between the predetermined sequence number range and the event type, and further determines the type of the event received last time. The sequence number of the held event of the same type is compared with the sequence number received this time to confirm the continuity. In the embodiment of the present invention, the functions of the sequence number management unit and the retransmission request determination unit can be realized by a program executed on the CPU of the NMS.

When the TCP layer receives the retransmission request from the retransmission request determination means, the TCP layer transmits the retransmission request to the corresponding network element via the IP layer, the lower layer, and the network using the TCP / IP protocol for the missing event type. Is sent, and the network element returns a response to the network element.

More specifically, in a preferred embodiment of the present invention, referring to FIG. 1, a sequence number management means (103) is added to a header portion of an event notified from the UDP layer (104). It interprets the sequence number and the event occurrence time, monitors which type of UDP event has occurred from which NE (109) and when, and monitors whether there is any omission in the continuity of the sequence number.
Further, the retransmission request determining means (102) receives the information transmitted from the sequence number managing means (103), indicating what degree of continuity of the sequence number has occurred in which type of event of which NE, After comprehensively determining the network status, NMS CPU load, etc., NE
Then, it is determined whether retransmission is requested by the TCP / IP protocol.

In the NMS, by monitoring and controlling the event in this way, when the event notification by the UDP is discarded, the minimum necessary data is transmitted to the TCP / TCP.
Re-collection can be performed at an appropriate timing by the IP protocol, and data consistency between the NE and the NMS can be guaranteed.

[0016]

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram showing an embodiment of the present invention;

FIG. 1 is a diagram showing the configuration of an embodiment of the present invention. Referring to FIG. 1, in one embodiment of the present invention, an NMS (100) managing a network (108) comprises:
It interprets the sequence number and the event occurrence time added to the header part of the event notified from the UDP layer (104), monitors which type of UDP event has occurred from which NE (109) and when, and monitors the sequence number. The sequence number management unit (103) monitors whether there is no omission in the continuity of the sequence number, and the degree of continuity of the sequence number in what kind of event of which NE transmitted from the sequence number management unit (103). The retransmission request determination unit (102) receives the information as to whether retransmission has been performed, determines comprehensively the network status, the CPU load of the NMS, etc., and then determines whether to request retransmission to the NE (109) by the TCP / IP protocol. ) And the content determined by the retransmission request determination unit (102) is displayed on a user interface such as a GUI (graphical user interface). And an NMS application (101).

The request from the NMS application (101) to the NE (109) is exchanged not by UDP but by the TCP protocol.
Inside the NMS, exchange between the NE (109) and the NMS (100) is performed through the TCP layer (105).

FIG. 2 is a diagram showing an example of the contents of a UDP message. FIG. 3 is a diagram illustrating an example of a sequence number rule. FIG. 6 is a diagram illustrating an example of a message notified to the retransmission request determination unit. FIG. 4 and FIG. 5 are diagrams showing the overall processing flow of an embodiment of the present invention. With reference to FIGS. 1 to 6, the overall operation of the present embodiment will be described below.

First, it is assumed that a failure has occurred in the NE (109) and an event of the report has been notified to the NMS (100) by the UDP protocol (step 401 in FIG. 4).

The event notification by UDP is transmitted to the management network (108), and the NMS managing the corresponding NE
Reported to (100). In the NMS (100), the corresponding event is not based on the TCP / IP protocol but is
Since it is based on the IP protocol, the event is distributed to the UDP layer (104 in FIG. 1) inside the NMS (FIG. 4).
Step 402), the UDP layer analyzes the inside of the packet and analyzes its contents.

The contents of a UDP packet are divided into a header part and a data part according to a predefined format. The UDP header part contains the message length of the packet itself and the identifier of the NE that notified the event (FIG. 2). Of 20
In addition to 4), a sequence number (205 in FIG. 2) and an event occurrence time (206 in FIG. 2) are stored.

Here, as shown in FIG. 3, the sequence number has a range of possible values for each event type, and the NE counts the count value each time an event of that type occurs. It is a number according to the rule of increasing one by one. When the value exceeds the range of values that can be taken for each event type, the count value returns to the initial value again, and the count is continued. The work of increasing the count value is performed by the NE.

The event occurrence time (205 in FIG. 2)
Is the date and time information (date,
The operation of recording this event occurrence time in the UDP header portion is also performed by the NE.

The NE identifier, sequence number, and event occurrence time are passed from the UDP layer (104) to the sequence number management unit (103 in FIG. 1), and the sequence number management unit (103) analyzes the contents. (Step 40 in FIG. 4)
3).

First, the sequence number management unit (103) determines the type of the event according to the sequence number rule (see FIG. 3) (step 404 in FIG. 4). The sequence numbers received this time are compared to confirm their continuity (step 405 in FIG. 4).

If the sequence numbers are continuous values, it is determined that there is no loss of UDP from the NE for the event type, no special processing is performed as a normal state, and the UDP layer (104) continues. Event waiting state.

However, if there is no continuity in the value of the sequence number, the sequence number management unit informs the retransmission request determination unit (102 in FIG. 1) of the identifier of the corresponding NE (5 in FIG. 6).
02), its event type (503 in FIG. 6), the number of unreported events (504 in FIG. 6) indicating the number of missing UDP events, and the previously notified event and the currently notified event Time interval information (505 in FIG. 6) indicating the time interval between the event and the event is notified (step 406 in FIG. 5).

The retransmission request determination unit (102) monitors the above information (see FIG. 6) from the sequence number management unit (103) as needed, and checks the information and the CP of the NMS (100) machine.
Taking into account the U load factor and the network load factor, TCP / IP identifies the missing event type according to a certain criterion.
It is determined whether the NE requests the retransmission immediately from the NE according to the protocol or whether the NE requests the NE to retransmit after a certain condition reaches a certain standard (step 407 in FIG. 5).

If it is determined that a retransmission request is to be made immediately, a retransmission request for the missing event type is immediately made to the TCP layer (105 in FIG. 1). Is stored in the retransmission request determination unit, and when the retransmission conditions are satisfied, the TCP layer (FIG. 1)
(105), a retransmission request is made for the missing event type (step 408 in FIG. 5).

When the TCP layer (105) receives the retransmission request,
The TCP layer (105) is composed of an IP layer (106) and lower layers (physical layers, etc.) (1
07) and the corresponding NE (1) via the management network (108).
09), TCP / I for the missing event type
Sends a message requesting retransmission in the P protocol,
The NE (109) returns the response to the NMS (100) (Step 409 in FIG. 5).

The NMS application (101 in FIG. 1) that has received the response updates the information of the corresponding event type handled by the application based on the information (step 410 in FIG. 5).

According to the processing flow described above, even if there is a missing UDP event notified by the NE, N
Since the process of matching the status inside the MS is performed, it is possible to minimize the mismatch of the status between the managing NMS and the managed NE.

Next, a description will be given using a specific example.

First, a communication failure A, a communication failure B, and a communication failure C occur at the NE No. 10 (NE identifier = 10; hereinafter, referred to as “NE10”). It is assumed that the report event of C is notified to the NMS by the UDP protocol (step 401 in FIG. 4).

The three communication failure event notifications by the UDP are transmitted to the management network and reported to the NMS managing the NE 10. In NMS, the corresponding event is TC
UDP / IP, not P / IP protocol
Since it is based on the protocol, the event is distributed to the UDP layer (104 in FIG. 1) inside the NMS (step 4 in FIG. 4).
02), the UDP layer analyzes the contents of the packet and analyzes the contents.

The contents of a UDP packet are divided into a header section and a data section according to a predefined format. The UDP header section contains the message length of the packet itself and the value of the identifier of the NE that notified the event (see FIG. 2 in 20
In addition to 4), a sequence number (205 in FIG. 2) and an event occurrence time (206 in FIG. 2) are stored.

In this case, the NE identifiers are A,
The event of B and C has a value of “10”, the sequence number is “0x01000001” for the event of A (x indicates hexadecimal display), the event of B is “0x01000002”, the event of C is “0x01000003”, As the event occurrence time, three UDP packets in which the event A is "Ta", the event B is "Tb", and the event C is "Tc" are interpreted.

The NE identifier, sequence number, and event occurrence time are sent from the UDP layer to the sequence number management unit (10 in FIG. 1).
The contents are passed to 3), and the sequence number management unit analyzes the contents (403 in FIG. 4). First, the sequence number management unit determines the type of the event according to the sequence number rule (FIG. 3) (step 404 in FIG. 4), and further compares the sequence number of the same type of event received last time with the sequence number received this time. The continuity is confirmed (step 405 in FIG. 4).

Events A, B and C are normally sent from NE10 to N
When notified to the MS, the sequence number management unit (103 in FIG. 1) first identifies the event from the NE 10 and confirms the sequence number of the event from the NE 10, and each of them is in the range of 0x01000000 to 0x01FFFFFF. Therefore, it is first recognized that these three event types are communication failures, and then it is checked whether there is any omission in the sequence numbers of the events A, B, and C.

In this case, since there is no omission, no special processing is performed as a normal state, and a state of waiting for an event from the UDP layer continues.

Next, the event A notified from the NE 10
A case in which the UDP packet of the event B of B and C is not notified to the NMS due to the congestion of the management network will be described. Events A and C are NE
When notified from NMS to NMS, first, the sequence number management unit identifies an event from NE10, and
Check the sequence number of the event from 10
0x01000000-0x01FFFFFF
It recognizes that the three event types are communication failures, and then checks whether there is any omission in the sequence numbers of events A and C.

In this case, the sequence number is "0x01000001" for the event of A and "0x01000003" for the event of C. Therefore, the sequence number management unit recognizes that there is a missing sequence number, and determines that there is a retransmission request. Part (Fig. 1
(102) is notified in a message format as shown in FIG.

In this case, the notified message is NE
The identifier (502 in FIG. 6) is “10” and the event type (5 in FIG. 6)
03) is “communication failure”, the number of unreported events (504 in FIG. 6)
Is “1”, and the time interval information (505 in FIG. 6) is
The time “Tc−Ta” is stored.

The retransmission request determination unit (102 in FIG. 1) monitors the information from the sequence number management unit as needed.
Taking into account the information, the CPU load factor of the NMS machine, and the network load factor, the event type missing according to a certain criterion is determined by the TCP / IP protocol.
It is determined whether a request for retransmission immediately from E is made or a request for retransmission to the NE after certain conditions reach a certain standard (step 407 in FIG. 5).

When it is determined that the CPU load factor of the NMS machine and the network load factor are not high, the retransmission request determination unit (102 in FIG. 1) immediately generates the NE 10 in the NE. When a request is transmitted by the TCP / IP protocol so as to retransmit all communication failure events, and when retransmission is suspended, the retransmission request determination unit memorizes the information, and when the retransmission conditions are satisfied. , A request is transmitted to the NE 10 by the TCP / IP protocol to retransmit all communication failure events occurring in the respective NEs.

NE 10 having received the retransmission request transmits the response to NM.
Return to S (step 409 in FIG. 5).

The NMS application (101 in FIG. 1) that has received the response updates information on a communication failure event handled by the application based on the information (step 410 in FIG. 5).

According to this processing flow, the U notified by the NE
Automatically NMS even if there is a missing DP event
Since the process of matching the states is performed internally, it is possible to minimize the mismatch of the states between the managing NMS and the managed NE.

Next, a second embodiment of the present invention will be described in detail with reference to the drawings.

First, a communication failure A, a communication failure B, and a communication failure C occur at NE No. 10 (NE identifier = 10: hereinafter, referred to as “NE10”). It is assumed that the report event of C is notified to the NMS by the UDP protocol (step 401 in FIG. 4).

The three communication failure event notifications by the UDP are transmitted to the management network and reported to the NMS managing the NE 10.

In the NMS, the corresponding event is not based on the TCP / IP protocol but is based on the UDP / IP protocol, so the UDP layer in the NMS (104 in FIG. 1)
Event (step 402 in FIG. 4), UDP
The layer analyzes the contents of the packet and analyzes the contents.

The contents of a UDP packet are divided into a header section and a data section according to a predefined format. The UDP header section contains the message length of the packet itself and the value of the identifier of the NE that notified the event (see FIG. 7 of 60
In addition to 4), an event type identifier (605 in FIG. 7) representing the event type, a sequence number (606 in FIG. 7), and an event occurrence time (607 in FIG. 7) are stored.

In this case, the NE identifiers are A,
The event of B and C has a value of “10”, the event type identifier has a value of “1” (701 in FIG. 8) indicating a communication failure, and the sequence number of the event of A is “0x00000001” and the event of B is “0x00000002”. , C event is “0x00000003”, and the event occurrence time is three UDPs of “A” for the A event, “Tb” for the B event, and “Tc” for the C event.
The packet will be interpreted.

The NE identifier, event type identifier, sequence number, and event occurrence time are passed from the UDP layer to the sequence number management unit (103 in FIG. 1), and the sequence number management unit (103 in FIG. 1) analyzes the contents. (Step 403 in FIG. 4).

First, a sequence number management unit (103 in FIG. 1)
Then, the type of the event is determined based on the event type identifier (step 404 in FIG. 4), and the sequence number of the event of the same type received last time is compared with the sequence number received this time to confirm its continuity (FIG. 4 step 405). When the events A, B, and C are normally notified from the NE 10 to the NMS, the sequence number management unit first identifies the event from the NE 10, and the value of the event type identifier from the NE 10 is "1". Recognizing that these three event types are communication failures, it is next checked whether there is any omission in the sequence numbers of events A, B, and C.

In this case, since there is no omission, no special processing is performed as a normal state, and an event waiting state from the UDP layer continues. Next, a case where the UDP packet of the event B among the events A, B, and C notified from the NE 10 is not notified to the NMS due to the congestion of the management network will be described.

When the events A and C are notified from the NE 10 to the NMS, first, the NE 10
Since the value of the event type identifier from the NE 10 is “1”, it is recognized that these three event types are communication failures, and then the sequence numbers of the events A and C are omitted. Check if there is any.

In this case, the sequence number is "0x00000001" for the event of A and "0x00000003" for the event of C. Therefore, the sequence number management unit (103 in FIG. 1) recognizes that the sequence number is missing. This is notified to the retransmission request determination unit (102 in FIG. 1) in a message format as shown in FIG.

In this case, the notified message is NE
The identifier (502 in FIG. 6) is “10” and the event type (5 in FIG. 6)
03) is “communication failure”, the number of unreported events (504 in FIG. 6)
Is “1”, and the time interval information (505 in FIG. 6) is
The time “Tc−Ta” is stored.

The retransmission request determination unit (102 in FIG. 1) monitors the information from the sequence number management unit as needed.
Taking into account the information, the CPU load factor of the NMS machine, and the network load factor, the event type missing according to a certain criterion is determined by the TCP / IP protocol.
It is determined whether a request for retransmission immediately from E is made or a request for retransmission to the NE after certain conditions reach a certain standard (step 407 in FIG. 5).

When it is determined that the CPU load factor of the NMS machine and the network load factor are not high, the retransmission request determining unit immediately retransmits all communication failure events occurring in the NE to the NE 10. When the request is transmitted according to the TCP / IP protocol and the retransmission is put on hold, the retransmission request determination unit memorizes the information,
When the conditions for retransmission are satisfied, T is transmitted to NE10 so that all communication failure events occurring in each NE are retransmitted.
The request is transmitted by the CP / IP protocol.

NE 10 having received the retransmission request transmits the response to NM.
Return to S (step 409 in FIG. 5).

The NMS application (101 in FIG. 1) that has received the response updates information on a communication failure event handled by the application based on the information. According to such a flow, even if there is a missing UDP event notified by the NE, the process of automatically adjusting the state inside the NMS is performed. Inconsistency between states can be prevented to a minimum.

[0066]

As described above, according to the present invention, the following effects can be obtained.

The first effect of the present invention is that the processing load of the NE and NMS can be reduced.

The reason for this is that, in the present invention, the sequence number management means monitors which NE has lost which type of event, and reports the monitoring result to the retransmission request determination means. Is TCP / TCP only for attributes related to the event type
Go to NE by IP protocol to get information, NMS
This is because the state is adjusted.

A second effect of the present invention is that loss of UDP packets can be minimized.

The reason for this is that, in the present invention, the retransmission request determination unit comprehensively determines the information from the sequence number management unit, estimates the state of the network and the NE,
This is to determine when it is optimal to match the states of the NE and the NMS by the TCP / IP protocol, including the load status of the S machine itself.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of an embodiment of the present invention.

FIG. 2 is a diagram for explaining one embodiment of the present invention;
FIG. 4 is a diagram illustrating an example of the content of a UDP message.

FIG. 3 is a diagram for explaining one embodiment of the present invention;
FIG. 4 is a diagram illustrating an example of a sequence number rule.

FIG. 4 is a flowchart (part 1) illustrating a processing flow according to an embodiment of the present invention;

FIG. 5 is a flowchart (part 2) illustrating a processing flow according to an embodiment of the present invention;

FIG. 6 is a diagram for explaining one embodiment of the present invention;
FIG. 9 is a diagram illustrating an example of a message format notified to a retransmission request determination unit.

FIG. 7 is a diagram for explaining one embodiment of the present invention;
FIG. 4 is a diagram illustrating an example of the content of a UDP message.

FIG. 8 is a diagram for explaining one embodiment of the present invention;
FIG. 4 is a diagram illustrating an example of a sequence number rule.

[Explanation of symbols]

 100 NMS 101 NMS Application 102 Retransmission Request Judgment Unit 103 Sequence Number Management Unit 104 UDP Layer 105 TCP Layer 106 IP Layer 107 Lower Layer 108 Management Network 109 NE 201 UDP Header Unit 202 UDP Data Unit 203 Message Length 204 NE Identifier 205 Sequence Number 206 Event occurrence time 301 Sequence number rule (alarm (communication failure)) 302 Sequence number rule (alarm (device failure)) 303 Sequence number rule (attribute change notification) 304 Sequence number rule (state change notification) 501 Management number 502 NE identifier 503 Event type 504 Number of unreported events 505 Time interval information 601 UDP header section 602 UDP data section 603 Message length 604 NE identifier 60 5 Event type identifier 606 Sequence number 607 Event occurrence time 701 Sequence number rule (alarm (communication failure)) 702 Sequence number rule (alarm (device failure)) 703 Sequence number rule (attribute change notification) 704 Sequence number rule (state change notification) )

Claims (8)

[Claims] 1. A network management system for managing a state of a network element according to an event notification from the network element, comprising:
When the event notification by the Datagram Protocol is discarded, a minimum necessary data is transmitted from the network element to the TCP (Transmission Control Protocol).
ocol) / IP (Internet Protocol) protocol, comprising means for controlling retransmission at an appropriate timing. 2. UDP / IP from the network element
Interpret the network element identification information, sequence number, and event occurrence time information added to the header of the event transmitted by the protocol and notified from the UDP layer, and determine which type of UDP event occurred in which network element and when. A sequence number management unit that monitors whether there is any omission in the sequence number by checking the continuity of the sequence number, and a sequence number of the event type of the network element transmitted from the sequence number management unit. And retransmits an event type with a missing sequence number to the network element according to the TCP / IP protocol, based on the network status and the CPU load status of the network management system. Requesting means for immediately requesting or requesting retransmission to be held until a condition for retransmission is satisfied. 3. The network management system according to claim 2, further comprising an application for displaying the content determined by said retransmission request determination means on a user interface. 4. The sequence number management means determines the type of the event from the sequence number based on a sequence number rule indicating a correspondence between a predetermined sequence number range and an event type. 3. The method according to claim 2, wherein a sequence number of an event of the same type received and held is compared with a sequence number received this time to confirm continuity.
The described network management system. 5. When the sequence number management means confirms the continuity of the sequence numbers and finds that the sequence numbers are continuous values, there is no loss of UDP from the network element for the event type. If it is determined that the sequence number has not been continuous and the sequence number value has no continuity,
The sequence number management means sends to the retransmission request determination means the identifier of the corresponding network element and its event type, the number of unreported events indicating how many missing UDP events, and 3. The network management system according to claim 2, further comprising means for controlling to notify a message including time interval information indicating a time interval between the event and the event notified this time. 6. An event type identifier for identifying an event type is further added to a header portion of the event notified from the UDP layer, and the sequence number management means uses the event type identifier to identify the type of the event. 3. The network management system according to claim 2, wherein the determination is made, and the continuity is confirmed by comparing the sequence number of the same type of event received last time with the sequence number received this time. 7. A network management system for managing a network, wherein the sequence number management means on the upper side of the UDP layer is added to a header part of an event transmitted from the network element by the UDP / IP protocol and notified from the UDP layer. By interpreting the network element identification information, sequence number, and event occurrence time information, monitoring which type of UDP event has occurred in which network element and when, and confirming the continuity of the sequence numbers, If there is no continuity in the value of the sequence number, the monitoring result information indicating the degree of continuity of the sequence number in which event type of which network element has been retransmitted. Send to request judgment means and resend In the request determination means, based on the network status and the CPU load status of the network management system,
The event type with missing sequence number is
It is determined whether to request retransmission immediately to the network element according to the IP protocol or hold the retransmission request until a retransmission condition is satisfied. The TCP layer of the network management system receives the retransmission request from the retransmission request determination unit. And the TCP layer sends a message requesting retransmission of a missing event type using the TCP / IP protocol to a corresponding network element via an IP layer, a lower layer, and a network. A method for guaranteeing notification data by UDP in a network management system, wherein a response is returned to a network element. 8. (a) UDP from network element
Interpret the network element identification information, sequence number, and event occurrence time information added to the header of the event transmitted by the / IP protocol and notified from the UDP layer, and when and what type of UDP event occurs in which network element Sequence number management means for monitoring whether there is any omission in the sequence number by monitoring whether or not the sequence number has been confirmed,
And (b) when there is no continuity in the value of the sequence number, the extent of the problem with the continuity of the sequence number for which event type of which network element is transmitted from the sequence number management means. Requesting retransmission of the missing event type to the network element by the TCP / IP protocol based on the network status and the CPU load status of the network management system, A recording medium which records a program for causing the means (a) and (b) of the retransmission request determination means to determine whether to hold the retransmission request until the condition is satisfied, on a computer constituting the network management system.