CN101056194A - A SNMP message transfer method and device - Google Patents
A SNMP message transfer method and device Download PDFInfo
- Publication number
- CN101056194A CN101056194A CN 200610036278 CN200610036278A CN101056194A CN 101056194 A CN101056194 A CN 101056194A CN 200610036278 CN200610036278 CN 200610036278 CN 200610036278 A CN200610036278 A CN 200610036278A CN 101056194 A CN101056194 A CN 101056194A
- Authority
- CN
- China
- Prior art keywords
- message
- sent
- server end
- snmp
- unit
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Images
Abstract
The invention discloses a simple network management protocol message sending method and device, includes the following method: store the messages to be sent from the client terminal in the message queue orderly, each message issuing device in client terminal corresponding to the server terminal respectively must implement the following steps: a) acquire a message from the queue; b) determine whether the acquired message is sent to the server terminal corresponding to this message issuing unit or not, if yes, send this message to the server terminal, goes to step c), otherwise, goes to step d); c) determine whether the server terminal received the sent message or not, if yes, goes to step d), otherwise, goes to step e); d) acquire a message from the queue in sequence, goes to step b); e) re-send this message and goes to step c). The invention may avoid the adverse influences of burst message to the network and equipment performances, improve the message transmission reliability, moreover, improve the maintainability of equipment.
Description
Technical field
The present invention relates to the communications field, relate to a kind of SNMP message transfer method and device specifically.
Background technology
(Simple Network Management Protocol is by the Internet engineering duty group (Internet Engineering Task Force, a cover NMP of IETF) working out SNMP) to Simple Network Management Protocol.According to snmp protocol, management work station can telemanagement all support the network equipment of this agreement, comprise the monitoring network state, revise network equipments configuration, receive network event warning etc.
SNMP has adopted the special shape of client end/server end model: agency/management station's model.To Network Management and maintenance is to finish by the interworking between snmp management station and SNMP agency.Each SNMP agency is responsible for replying the snmp management station to management information bank (Management InformationBase, MIB) the various inquiries of the information that defines.
SNMP agency and snmp management station communicate by the standard message in the snmp protocol, and each message all is an independent datagram, and SNMP adopts User Datagram Protoco (UDP), and (User DatagramProtocol is UDP) as host-host protocol.
In actual applications, the snmp management station is by obtaining request message Get-Request message retrieving information from the network equipment with SNMP agent functionality, the SNMP agency adopts and obtains response message Get-Response message response, obtain next request message Get-Next-Request and Get-Request and be used in combination the element that can be used for inquiring about specific table object, the employing of snmp management station is provided with request message Set-Request and comes the network equipment with SNMP agent functionality is carried out Remote configuration, for example the configuration device name, device attribute is set, interpolation or sweep equipment etc.
And when SNMP acts on behalf of non-request messages such as need sending network condition message and alarm information to the snmp management station, then adopt trap Trap message to send these message to the snmp management station.The Trap advice method is unreliable transmission, and the recipient need not to reply any confirmation after receiving a Trap notice, so the sender can't know whether the Trap notice is correctly received.
In actual applications, snmp protocol uses between the superior and the subordinate's telecommunicatioin network management usually, and the Upper NM Station system is a management station, and subordinate's network management system is the SNMP agency, is used for realizing the transmission of the message between the superior and the subordinate's network management system.Because this agreement is transmitted based on udp protocol, and udp protocol is a kind of insecure host-host protocol, the assurance mechanism that it does not provide data to transmit, if also promptly losing of datagram occur in the transmittance process from the transmit leg to recipient, agreement itself can not be made any detection or prompting; In addition, Trap message is not replied the message that is received yet and is confirmed.So when subordinate's network management system when higher level's network management system adopts SNMP to send trap message, will occur because of faults such as the superior and the subordinate's network management system communication abnormality, network congestion or the superior and the subordinate's network management system itself is unusual cause information drop-out the superior and the subordinate network management system can't detected situation, finally cause the problems such as data-bag lost of transmission.
In order to address this problem, prior art has mainly adopted following two kinds of methods:
First method is the mode that management station adopts SNMP Get-Request message automatic regular polling.The SNMP agency sends trap message to management station, when the communication between management station and the SNMP agency is broken down, the trap message that is sent does not arrive management station by expection, management station regularly sends the trap message that Get-Request message automatic regular polling SNMP agency is sent to the SNMP agency on one's own initiative, thereby solves the problem of information drop-out.
Second method is that management station adopts SNMP Set-Request message regularly to trigger the mode that SNMP acts on behalf of resend message.The SNMP agency sends trap message to management station, when the communication between management station and the SNMP agency is broken down, the trap message that is sent does not arrive management station by expection, management station sends Set-Request message trigger SNMP agency to the SNMP agency on one's own initiative and resends trap message, thereby solves the problem of information drop-out.
But,, but exist some problems although above-mentioned two kinds of methods have solved the problem of information drop-out to a certain extent.Poll and re-send request may according to management station recited above, the SNMP agency uses SNMP to send trap message to management station, because the unreliability of the UDP host-host protocol that unresponsive characteristic of trap message and SNMP are adopted, the SNMP agency can't confirm still whether management station receives message, and management station can't learn also whether the SNMP agency has sent certain message.Therefore, especially under the situation of management station and the interruption of SNMP agent communication, the SNMP agency is after management station has sent Trap message, management station thinks that also the SNMP agency does not also send message, can or trigger the message that SNMP acts on behalf of retransmits lost to the SNMP agents query, when SNMP acts on behalf of when many, can increase management station's complexity and load greatly; In addition, the SNMP agency also can be broken down because of the communication of not knowing, can still send message, particularly in the time of network congestion, has influenced the performance of network.
In order to solve above-mentioned owing to adopt the Trap mode to send the problem that unreliability has produced of message, prior art has adopted the mode of a kind of Inform-Request to transmit message again.
The Inform-Request mode also adopts the host-host protocol of UDP, but different with the trap mode is that the Inform-Request mode has response mechanism, when SNMP acts on behalf of after management station sends a piece of news by the Inform-Request mode, if management station correctly receives this message, just reply a confirmation to the SNMP agency, if management station does not receive this message, after after a while, SNMP agency can resend this message, till the answer that receives management station or the number of times that resends message surpass default repeating transmission number of times.By this message mode, the SNMP agency knows whether management station has successfully received message, guaranteed that message is sent to management station reliably, simultaneously, communicating by letter between management station and SNMP agency also can stop the transmission of message when breaking down, avoid ceaselessly sending message to management station.
Though the Inform-Request message mode has solved the integrity problem of Trap message mode, also still there are some problems in himself.
The response mechanism of Inform-Request send mode and message retransmission mechanism have increased network traffic data.Adopt the twice (because response message) of Trap mode during data traffic under the normal condition, under emergency case, for example when causing equipment to restart because of the supply of electric power problem, a large amount of message that the SNMP agent equipment can happen suddenly to each upper management station in a short period of time, increased the processing burden of management station greatly, the problem that Inform-Request message retransmits appears because can cause a large amount of Inform-Request message to can not get in time handling, caused the sharp increase of network traffics, simultaneously owing to need to handle a large amount of response messages and retransmit a large amount of message, also increase SNMP agency's work load greatly, influenced operation stability of equipment.
In addition, because the message retransmission mechanism of Inform-Request send mode, the message that can cause some to pass through after retransmitting can't arrive management station in order, so just is not suitable for the message sequencing is had the processing of the system of management station of dependence.
Summary of the invention
The technical problem that the present invention solves is to propose a kind of SNMP message transfer method and device, be applied in the network environment of user end to server end transmission SNMP message, the Inform-Request message mode that is used for reducing prior art is to equipment operation performance and network operation Effect on Performance, simultaneously also with solving the problem that message in the prior art can't arrive management station in order.
For addressing the above problem, the present invention proposes following technical scheme.
This scheme comprises a kind of SNMP message transfer method, comprising:
Message to be sent in the client is stored in the message queue in order, is provided with a plurality of message Dispatching Unit corresponding respectively in the client with server end:
A) the message Dispatching Unit obtains a message from message queue;
B) judge whether the described message of obtaining is to send to and described message Dispatching Unit corresponding server end, if send this message, execution in step c to pairing server end), otherwise, execution in step d);
C) judge whether described server end receives the message that is sent, if, execution in step d), otherwise, execution in step e);
D) from described message queue, obtain next message, execution in step b then in order);
E) resend described message, and execution in step c).
Wherein, step d) comprises step:
D1) judge whether the current message of obtaining is last message in the formation, if, stop message and send, otherwise, execution in step d2);
D2) from formation, obtain next message in order, and execution in step b).
Step e) comprises step particularly:
E1) judge whether the link of client and this server end is normal, if, execution in step e2), otherwise, wait for a default time, re-execute step e1);
E2) resend this message, and execution in step c).
Correspondingly, this programme also comprises the SNMP message conveyer, comprises memory cell and corresponding with each server respectively message Dispatching Unit, wherein:
Memory cell is used for storing in order message to be sent;
The message Dispatching Unit, be used for in the described memory cell, to be sently send to this server in order for the message with this message Dispatching Unit corresponding server end.
Wherein, the message Dispatching Unit further comprises message acquiring unit, judging unit, information receiving and transmitting unit and fault processing module again:
The message acquiring unit is used for obtaining message to be sent from memory cell in order;
Judging unit is used to judge that whether message that the message acquiring unit obtained be the message that sends to its corresponding server, if this message is sent to the information receiving and transmitting unit, otherwise the notification message acquiring unit obtains next message;
Information receiving and transmitting unit, the message that is used for receiving from judging unit send to and its corresponding server end, and judge whether server end receives the message that is sent, if, the notification message acquiring unit obtains next message, otherwise the notice fault processing unit is handled;
The communication check unit, link to each other with the information receiving and transmitting unit, whether the communication that is used for detecting between the client and server is normal, if communication is normal, the notification message Transmit-Receive Unit resends current message, otherwise, wait for a default time, continue to detect the communications status between the client and server.
In addition, the message Dispatching Unit comprises that also transmission finishes judging unit, link to each other with the message acquiring unit, before the message acquiring unit obtains next message, be used to judge whether the message of current transmission is last message in the formation, if stop from formation, to obtain message, otherwise, obtain next message in order.
Described information receiving and transmitting unit comprises the message authentication unit again: be used to judge whether to receive the response message that affirmation that server end replys receives message, if the judgment is Yes, determine that server end receives the message that is sent, otherwise, determine that server end does not receive the message that is sent.
Described message authentication unit comprises the answer confirmation unit again: be used to judge whether client receives the response message that affirmation that server end replys receives message, if the judgment is Yes, determine that server end receives the message that is sent, otherwise, the user end to server end repeats to send this message, judge client whether default repeat to send receive the response message that affirmation that server end replys receives message in the number of times, if the judgment is Yes, determine that server end receives the message that is sent, otherwise, determine that server end does not receive the message that is sent.
In the such scheme, described information receiving and transmitting unit all sends message by the mode of notice request to server end.
In the such scheme, the time order and function order that client generates according to message with message stores to be sent in the client in message queue.
Compared with prior art, the present invention is stored in all message to be sent in the public formation in order, respectively to each management station dispatch messages successively, has simplified the flow process of SNMP agency transmission message by the message Dispatching Unit; Simultaneously, because SNMP agency sends message to management station successively, can be to management station's a large amount of message that happens suddenly, avoided the influence of a large amount of shocking flash to the operation of SNMP agency and management station, also avoided the influence of a large amount of shocking flash to network performance; In addition, SNMP agency of the present invention sends message in strict accordance with the order of message to management station, and guarantee to send next message again after message is by correct the reception, can guarantee that message arrives management station in order, is suitable for the sequencing of message is had the processing of dependent management station; And the present invention can also be when the communication between SNMP agency and the management station be broken down, and suspending message sends, and fault is detected, and can recover the transmission of message after the fault recovery.
Description of drawings
Fig. 1 is a SNMP message transfer method flow chart of the present invention;
Fig. 2 is a SNMP message transfer method embodiment flow chart of the present invention;
Fig. 3 is a SNMP message conveyer structural representation of the present invention;
Fig. 4 is a SNMP message conveyer message Dispatching Unit structure chart of the present invention;
Fig. 5 is a SNMP message conveyer embodiment flow chart of the present invention.
Embodiment
With reference to the accompanying drawings embodiments of the invention are made detailed explanation below.
The present invention is mainly used in the network environment of user end to server end transmission snmp message in the SNMP network.Its main invention thinking is: message to be sent in the client is stored in the public formation successively in order, there is a message Dispatching Unit corresponding respectively with each and server end with it, as shown in Figure 1, these message Dispatching Unit are carried out following steps respectively:
A) the message Dispatching Unit obtains a message from message queue;
B) judge whether the described message of obtaining is to send to and described message Dispatching Unit corresponding server end, if send this message, execution in step c to pairing server end), otherwise, execution in step d);
C) judge whether described server end receives the message that is sent, if, execution in step d), otherwise, execution in step e);
D) from described message queue, obtain next message, execution in step b then in order);
E) resend described message, and execution in step c).
In actual applications, top client is presented as the SNMP agency, and server end is presented as the snmp management station.Be that above-mentioned steps of the present invention is applied in the specific implementation principle in the network management system below:
In the SNMP agent equipment, every message all has an orderly message serial number from small to large, and this serial number is that integer or character string etc. can be represented the data mode of sequencing, and is unique in this equipment global scope.Adopt this orderly serial number, just can identify the message of these all generations of equipment and the sequencing that message produces uniquely.
For to the such serial number of the distribution of messages of each generation, all the time an in store up-to-date overall current message serial number that generates in order in the SNMP agent equipment, when the SNMP agent equipment generates a new message, system just distributes to this newly-generated message as its serial number with the current message serial number of the overall situation, simultaneously, generate a new serial number again in order as new overall current message serial number.Also promptly, overall current message serial number is identifying the next serial number that is about to the message of generation all the time.Newly-generated message is stored in one in order and waits to send out in the message queue, is storing the message that is sent to management station in the formation.
Act on behalf of the situation that a plurality of management stations are arranged at a SNMP, among the SNMP agency message Dispatching Unit is arranged, be used for difference dispatch messages to a plurality of management stations.This message Dispatching Unit all has message dispatch thread corresponding with it to each management station, and each message dispatch thread is worked independently.
Certainly, in actual applications, this invention also can be applied to a plurality of SNMP agencies send situation from snmp message a to management station.Only in a plurality of SNMP agencies, all adopt this invention,, have only a management station at each SNNP agency.
In order to indicate SNMP agency situation to the dispatch messages of each management station, in the SNMP agency in store respectively with the proprietary current message serial number of corresponding management station of each management station.The proprietary current message serial number of this management station is used for representing that the message before this serial number and this serial number has all successfully sent to this management station.So what this serial number write down is a nearest serial number that successfully sends to the message of corresponding management station.
In order to guarantee that a message can successfully be sent to server end, the present invention adopts the message load mode of SNMP notice request (SNMP Inform-Request).The Inform-Request mode also adopts the host-host protocol of UDP, but different with the trap mode be that the Inform-Request mode has respond packet, it need reply a confirmation to the SNMP agency after the snmp management station receives an Inform message.In this way, the SNMP agency knows whether management station has successfully received message, thereby has guaranteed that message is sent to management station reliably.
In the process that message sends, continue to send message for fear of SNMP agency when the communication between SNMP agency and the management station is broken down to management station, when the message that is sent as SNMP agency is not correctly received by management station, the SNMP agency suspends the transmission message to management station, and this message dispatch thread enters resting state.
In addition, in order to guarantee that client can be recovered to send message to server end under the situation of the communication recovery between SNMP agency and the management station, the SNMP agency has one to detect between management station and the SNMP agency whether normal communication detection module of communication.Be in the process of resting state in this message dispatch thread, if the communication recovery that the communication check module detects between management station and the SNMP agency is normal, the SNMP agency just wakes the dispatch thread that this is in resting state up, recovers to send message to this management station.
According to above realization principle, be explanation below to a specific embodiment of the present invention.What this embodiment described is that the message dispatch thread that SNMP acts on behalf of sends message by SNMP Inform-Request mode respectively to management station, when communication failure appears in management station and SNMP agency, this message dispatch thread can be suspended transmission message, when fault recovery, this message dispatch thread can recover to send message again.For the situation that a plurality of management stations are arranged, each management station all has a message dispatch thread corresponding with it respectively in the SNMP agency, and these threads all work alone, and carry out identical flow process.
As shown in Figure 2, the concrete message transmission flow of each message dispatch thread is as follows:
10) from message queue to be sent, obtain the next message of the proprietary current message serial number correspondence of this management station.
Before beginning to send message, the proprietary current message serial number of management station has been determined the message to be sent that first is sent out.In a typical message transmitting process, this message dispatch thread is obtained first message in the formation in order, therefore, before this thread begins to send message, should preset a proprietary current message serial number of rational management station, make that the next message of this message serial number is first interior message of formation.Certainly, the present invention also supports to begin to obtain message from any one position of formation, and in this case, the message dispatch thread is only distributed the message of the back that begins from this message.
20) judge that whether the message obtained be to send to the management station corresponding with this thread, if, then send this message to this management station, and execution in step 30), otherwise, execution in step 40).
In the SNMP agency, the message to be sent that sends to all management stations all is stored in the formation, for all message to be sent, each message dispatch thread all will be filtered it before sending message, for not being the message that sends to this pairing management station of thread, all can be filtered, ignore and do not carry out handling, so, then further handle to sending the message of this pairing management station of thread.
In each message to be sent, all carry the transmission destination information, can judge by inquiring about this destination information whether this message is to send to the management station corresponding with certain each thread.
30) judge whether management station receives the message that is sent, if, execution in step 40), otherwise, execution in step 50);
Owing to adopt the send mode of Inform-Request to send message to management station, judge that a kind of method whether management station correctly receives the message that is sent is: whether the SNMP agency receives management station in the default time interval replys the affirmation of the Inform-Request message that sent, if, judge that then management station correctly receives the message that is sent, otherwise, judge that management station does not correctly receive the message that is sent.
In addition, judge that the another kind of method whether management station correctly receives the message that is sent is: whether the SNMP agency receives management station in the default time interval replys the affirmation of the Inform-Request message that sent, if, judge that then management station correctly receives the message that is sent, otherwise, the SNMP agency resends this message according to default repeating transmission number of times to management station, judge whether management station replys acknowledge message to the Inform-Request message that is sent in default repeating transmission number of times, if, judge that then management station correctly receives the message that is sent, otherwise, judge that management station does not correctly receive the message that is sent.
40) the proprietary current message serial number of this management station is set and equals the serial number that this successfully sends message, whether the next serial number of judging the proprietary current message serial number of management station equals overall current message serial number, if stop message and send, otherwise, re-execute step 10).
The next serial number of the proprietary current message serial number of management station equals overall current message serial number, the message that shows current transmission is interior last message of global scope in the SNMP agency, also be that the message transmission finishes, so suspending, this dispatch thread sends message, up to had new message to generate and etc. to be sent, the next serial number of the proprietary current message serial number of management station no longer equals overall current message serial number, and this dispatch thread restarts to send message.
50) judge whether the communication between management station and the SNMP agency is normal, if, execution in step 10), otherwise, wait for a default time interval, re-execute step 50), the communications status between management station and the SNMP agency detected again.
At this moment, because management station does not correctly receive the message that is sent, message dispatch thread notice starts the communications status between communication check unit detection management station and the SNMP agency, if the communication failure between management station and the SNMP agency causes management station can't correctly receive message, this message dispatch thread is suspended transmission message, and keeps detecting the communications status between management station and the SNMP agency at any time, in case recover, go to step 10) immediately, resend message.
Because this moment, current message was not correctly received by management station, so in step 30), the proprietary current message serial number of this management station does not change, so the message that is sent after going to step 10) after the communications status recovery remains the current message that is not correctly sent.
Meanwhile, the present invention also proposes a kind of SNMP message conveyer, as shown in Figure 3, mainly comprises memory cell and message Dispatching Unit, and wherein, each management station that is connected with this SNMP all has a message Dispatching Unit corresponding with it.As shown in Figure 4, the message Dispatching Unit further comprises message acquiring unit, judging unit, information receiving and transmitting unit and communication check unit again.
Below embodiment is specifically described.
Fig. 5 is the specific embodiment structural representation of this device, mainly comprise register, message queue to be sent, message acquiring unit, judging unit and, send and finish judging unit, information receiving and transmitting unit and communication check unit.
Register is used for depositing the proprietary current serial number of overall current message serial number and management station, the next serial number that is about to the message of generation of wherein overall current serial number sign, the proprietary current serial number of management station identifies a nearest serial number that successfully sends to the message of the management station corresponding with the message Dispatching Unit.
Message queue to be sent is used for storing message to be sent, each message to be sent that carries serial number information all according to the sequential storage of the current serial number of the overall situation in this message queue to be sent.
The message acquiring unit obtains the next message of the proprietary current message serial number correspondence of this management station from message queue to be sent.
Judging unit, be used to judge whether the message that the message acquiring unit is obtained is the message that sends to the management station corresponding with it, if, this message is sent to the information receiving and transmitting unit, otherwise, the proprietary current message serial number of this management station is set equals the serial number that this successfully sends message, whether notice transmission end judging unit message sends and finishes.
The information receiving and transmitting unit, be used for to send to the management station corresponding from the message that judging unit receives with it, and judge whether management station receives the message that is sent, this arbitration functions is finished by the message authentication unit in the information receiving and transmitting unit, if the judgment is Yes, the proprietary current message serial number of this management station is set equals the serial number that this successfully sends message, whether notice transmission end judging unit message sends and finishes, otherwise, the notifying communication detecting unit detect between SNMP agency and the management station communicate by letter whether normal.Judge and adopt the same procedure described in the embodiment of front to judge whether management station receives the message that is sent.
Send and finish judging unit, before the message acquiring unit obtains next message, be used to judge whether the next serial number of the proprietary current message serial number of management station equals overall current message serial number, if, stop from formation, to obtain message, otherwise the notification message acquiring unit obtains next message in order;
The communication check unit, link to each other with the information receiving and transmitting unit, whether the communication that is used for detecting between SNMP agency and the management station is normal, if communication is normal, the current again message of notification message acquiring unit sends, otherwise, wait for a default time, continue to detect the communications status between SNMP agency and the management station, recover up to communications status, the current again message of notification message acquiring unit sends.
The above only is a preferred implementation of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.
Claims (11)
1. a SNMP message transfer method is applied to it is characterized in that in the network environment of user end to server end transmission SNMP message,
Message to be sent in the client is stored in the message queue in order, is provided with a plurality of message Dispatching Unit corresponding respectively in the client with server end:
A) the message Dispatching Unit obtains a message from message queue;
B) judge whether the described message of obtaining is to send to and described message Dispatching Unit corresponding server end, if send this message, execution in step c to pairing server end), otherwise, execution in step d);
C) judge whether described server end receives the message that is sent, if, execution in step d), otherwise, execution in step e);
D) from described message queue, obtain next message, execution in step b then in order);
E) resend described message, and execution in step c).
2. SNMP message transfer method as claimed in claim 1 is characterized in that step d) comprises step:
D1) judge whether the current message of obtaining is last message of formation, if, then stop message and send, otherwise, execution in step d2);
D2) from described message queue, obtain next message in order, and execution in step b).
3. SNMP message transfer method as claimed in claim 1 is characterized in that, step e) comprises step particularly:
E1) judge whether the link of client and this server end is normal, if, execution in step e2), otherwise, wait for a default time, re-execute step e1);
E2) resend this message, and execution in step c).
4. SNMP message transfer method as claimed in claim 1, it is characterized in that, in step c), describedly judge whether server end receives the messages step that is sent and be: judge whether to receive the response message that affirmation that server end replys receives message, if, determine that server end receives the message that is sent, otherwise, determine that server end does not receive the message that is sent.
5. SNMP message transfer method as claimed in claim 1, it is characterized in that described message to be sent in the client is stored in the message queue in order is: the time order and function order that generates according to message with message stores to be sent in the client in message queue.
6. as each described SNMP message transfer method of claim 1 to 5, it is characterized in that described client sends message in the mode of notice request to server end.
7. a SNMP message conveyer is used for transmitting SNMP message at least one server end, it is characterized in that, comprises memory cell and at least one corresponding with each server respectively message Dispatching Unit, wherein:
Memory cell is used for storing in order message to be sent;
The message Dispatching Unit, is used for the message in the described memory cell is sent to corresponding server successively corresponding with each server end respectively linking to each other.
8. SNMP message conveyer as claimed in claim 7 is characterized in that, described message Dispatching Unit further comprises message acquiring unit, judging unit, information receiving and transmitting unit and fault processing module, wherein
The message acquiring unit is used for obtaining message to be sent from memory cell;
Judging unit is used to judge that whether message that the message acquiring unit obtained be the message that sends to its corresponding server, if, this message is sent to the information receiving and transmitting unit, otherwise, next message obtained by the message acquiring unit;
Information receiving and transmitting unit, the message that is used for receiving from judging unit send to and its corresponding server end, and judge whether server end receives the message that is sent, if, obtain next message by the message acquiring unit, otherwise, handle by fault processing unit;
The communication check unit links to each other with the information receiving and transmitting unit, and whether the communication that is used for detecting between the client and server is normal, if communication is normal, resend current message by the information receiving and transmitting unit, otherwise, wait for a default time, continue to detect the communications status between the client and server.
9. SNMP message conveyer as claimed in claim 8, it is characterized in that, also comprise sending and finish judging unit, link to each other with the message acquiring unit, before the message acquiring unit obtains next message, be used to judge whether the message of current transmission is last message in the formation, if, the message acquiring unit stops to obtain message from formation, otherwise, obtain next message in order.
10. SNMP message conveyer as claimed in claim 8 is characterized in that, described information receiving and transmitting unit also comprises the message authentication unit:
Be used to judge whether to receive the response message that affirmation that server end replys receives message, if the judgment is Yes, determine that server end receives the message that is sent, otherwise, determine that server end does not receive the message that is sent.
11. SNMP message conveyer as claimed in claim 10 is characterized in that, described message authentication unit also comprises the answer confirmation unit:
Be used to judge whether client receives the response message that affirmation that server end replys receives message, if the judgment is Yes, determine that server end receives the message that is sent, otherwise, the user end to server end repeats to send this message, judge client whether default repeat to send receive the response message that affirmation that server end replys receives message in the number of times, if the judgment is Yes, determine that server end receives the message that is sent, otherwise, determine that server end does not receive the message that is sent.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610036278XA CN101056194B (en) | 2006-06-30 | 2006-06-30 | A SNMP message transfer method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610036278XA CN101056194B (en) | 2006-06-30 | 2006-06-30 | A SNMP message transfer method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101056194A true CN101056194A (en) | 2007-10-17 |
| CN101056194B CN101056194B (en) | 2011-04-06 |
Family
ID=38795819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610036278XA Expired - Fee Related CN101056194B (en) | 2006-06-30 | 2006-06-30 | A SNMP message transfer method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101056194B (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945111A (en) * | 2010-09-21 | 2011-01-12 | 深圳市佳创视讯技术股份有限公司 | Method, device and system for acquiring and transmitting viewing data |
| CN102014416A (en) * | 2010-12-03 | 2011-04-13 | 中兴通讯股份有限公司 | Method and system for bidirectional detection of connection |
| CN102882697A (en) * | 2011-07-13 | 2013-01-16 | 北京佳讯飞鸿电气股份有限公司 | Message receiving method of multi-client end of network management system based on callback system |
| CN103001713A (en) * | 2012-11-23 | 2013-03-27 | 山东电力集团公司 | Method for preventing wireless radio frequency communication interference |
| CN104202769A (en) * | 2014-09-28 | 2014-12-10 | 中国联合网络通信集团有限公司 | Method and terminal for realizing business data reporting |
| CN104348874A (en) * | 2013-08-06 | 2015-02-11 | 中国电信股份有限公司 | Method and device for message transmission between cloud platform components |
| CN104767589A (en) * | 2015-03-12 | 2015-07-08 | 新浪网技术(中国)有限公司 | Message sending method and device |
| CN106453613A (en) * | 2016-10-31 | 2017-02-22 | 北京小米移动软件有限公司 | Message retransmission method and apparatus |
| CN106941461A (en) * | 2017-02-23 | 2017-07-11 | 江苏徐工信息技术股份有限公司 | A kind of method that utilization message queue optimizes server processing requests |
| CN108038007A (en) * | 2017-11-30 | 2018-05-15 | 中电福富信息科技有限公司 | A kind of orderly processing method of message based on Ignite and system |
| CN108616433A (en) * | 2018-05-04 | 2018-10-02 | 青岛海信智慧家居系统股份有限公司 | State synchronization method, device, gateway device and storage medium |
| CN109743142A (en) * | 2018-09-30 | 2019-05-10 | 比亚迪股份有限公司 | Information communication method and device |
| CN112134965A (en) * | 2020-11-24 | 2020-12-25 | 树根互联技术有限公司 | Issuing method and device of Internet of things instruction and electronic equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4330767B2 (en) * | 2000-06-26 | 2009-09-16 | 株式会社エヌ・ティ・ティ・ドコモ | Communication method and base station apparatus performing automatic retransmission request |
| DE10257450A1 (en) * | 2002-12-09 | 2004-07-15 | Siemens Ag | Networked application monitoring method in which an SNMP agent server is used in conjunction with a network management station to monitor the state of applications using a register database in a proxy server |
-
2006
- 2006-06-30 CN CN200610036278XA patent/CN101056194B/en not_active Expired - Fee Related
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945111A (en) * | 2010-09-21 | 2011-01-12 | 深圳市佳创视讯技术股份有限公司 | Method, device and system for acquiring and transmitting viewing data |
| CN102014416A (en) * | 2010-12-03 | 2011-04-13 | 中兴通讯股份有限公司 | Method and system for bidirectional detection of connection |
| CN102014416B (en) * | 2010-12-03 | 2014-07-16 | 中兴通讯股份有限公司 | Method and system for bidirectional detection of connection |
| CN102882697B (en) * | 2011-07-13 | 2015-08-26 | 北京佳讯飞鸿电气股份有限公司 | A kind of message receival method of the network management system multi-client based on callback mechanism |
| CN102882697A (en) * | 2011-07-13 | 2013-01-16 | 北京佳讯飞鸿电气股份有限公司 | Message receiving method of multi-client end of network management system based on callback system |
| CN103001713A (en) * | 2012-11-23 | 2013-03-27 | 山东电力集团公司 | Method for preventing wireless radio frequency communication interference |
| CN104348874A (en) * | 2013-08-06 | 2015-02-11 | 中国电信股份有限公司 | Method and device for message transmission between cloud platform components |
| CN104202769A (en) * | 2014-09-28 | 2014-12-10 | 中国联合网络通信集团有限公司 | Method and terminal for realizing business data reporting |
| CN104202769B (en) * | 2014-09-28 | 2018-03-23 | 中国联合网络通信集团有限公司 | A kind of method and device realized business datum and reported |
| CN104767589A (en) * | 2015-03-12 | 2015-07-08 | 新浪网技术(中国)有限公司 | Message sending method and device |
| CN104767589B (en) * | 2015-03-12 | 2018-08-14 | 新浪网技术(中国)有限公司 | A kind of method for sending information and device |
| CN106453613A (en) * | 2016-10-31 | 2017-02-22 | 北京小米移动软件有限公司 | Message retransmission method and apparatus |
| CN106453613B (en) * | 2016-10-31 | 2019-12-13 | 北京小米移动软件有限公司 | Message retransmission method and device |
| CN106941461A (en) * | 2017-02-23 | 2017-07-11 | 江苏徐工信息技术股份有限公司 | A kind of method that utilization message queue optimizes server processing requests |
| CN108038007A (en) * | 2017-11-30 | 2018-05-15 | 中电福富信息科技有限公司 | A kind of orderly processing method of message based on Ignite and system |
| CN108038007B (en) * | 2017-11-30 | 2022-04-05 | 中电福富信息科技有限公司 | Method and system for orderly processing messages based on Ignite |
| CN108616433A (en) * | 2018-05-04 | 2018-10-02 | 青岛海信智慧家居系统股份有限公司 | State synchronization method, device, gateway device and storage medium |
| CN108616433B (en) * | 2018-05-04 | 2021-02-23 | 青岛海信智慧家居系统股份有限公司 | State synchronization method, device, gateway equipment and storage medium |
| CN109743142A (en) * | 2018-09-30 | 2019-05-10 | 比亚迪股份有限公司 | Information communication method and device |
| CN112134965A (en) * | 2020-11-24 | 2020-12-25 | 树根互联技术有限公司 | Issuing method and device of Internet of things instruction and electronic equipment |
| CN112134965B (en) * | 2020-11-24 | 2021-02-26 | 树根互联技术有限公司 | Issuing method and device of Internet of things instruction and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101056194B (en) | 2011-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101056194A (en) | A SNMP message transfer method and device | |
| CN1086531C (en) | Multi-processor environments | |
| CN106330414B (en) | Message transmission method and device | |
| ATE324725T1 (en) | METHOD AND COMPUTER PROGRAM PRODUCT FOR EFFICIENTLY AND SECURELY SENDING SMALL DATA MESSAGES FROM A SENDER TO A LARGE NUMBER OF RECEIVING SYSTEMS | |
| CN1503513A (en) | Syste mand method for detecting lost messages transmitted between modules in a communication device | |
| CN101047481A (en) | Automatic retransmission requiring distribution feedback method in radio communication system | |
| CN101060485A (en) | Topology changed messages processing method and processing device | |
| CN1905490A (en) | Method and apparatus for preventing loop when RRPP and partial STP network damage recovery | |
| WO2013000282A1 (en) | Alarm information reporting method, apparatus and system | |
| CN1315288C (en) | Non-break switchover method of double-network communication system | |
| WO2013167092A2 (en) | Method, device and system for remote management of terminal peripheral | |
| JP2008059114A (en) | Automatic network monitoring system using snmp | |
| CN101668014B (en) | Communication method of manufacturing grid service center and resource nodes | |
| JP2008097326A (en) | Snmp sequence management method, manager device, and agent device | |
| CN110809262A (en) | Internet of things equipment operation and maintenance management method based on COAP protocol | |
| CN1617525A (en) | Method for guaranteeing general route package channel transmission reliability | |
| CN1870558A (en) | Loop detection method and system of intersection ring in elastic group ring | |
| CN1852183A (en) | Method and apparatus for detecting counter defect indication-path condition | |
| KR100608841B1 (en) | Method for transmitting mms message upon splitting and performing automatic re-transmission thereof | |
| CN105634894A (en) | Enhanced type CAN bus data resending method and device | |
| CN1956421A (en) | Reliable transmission method for web service message | |
| CN103428677A (en) | Method for sending grouped service data and method for receiving message sent by signaling channel | |
| CN1561041A (en) | Device and method of Ethernet interface thermal backup | |
| CN101800667A (en) | Alarm message transmitting method, network equipment and alarm system | |
| CN1567903A (en) | Ethernet gateway based on field bus and implementing method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110406 Termination date: 20160630 |