WO2015014085A1 - Procédé de conversion de protocole et convertisseur de protocole - Google Patents

Procédé de conversion de protocole et convertisseur de protocole Download PDF

Info

Publication number
WO2015014085A1
WO2015014085A1 PCT/CN2013/090648 CN2013090648W WO2015014085A1 WO 2015014085 A1 WO2015014085 A1 WO 2015014085A1 CN 2013090648 W CN2013090648 W CN 2013090648W WO 2015014085 A1 WO2015014085 A1 WO 2015014085A1
Authority
WO
WIPO (PCT)
Prior art keywords
snmp
message
value
request message
tra
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.)
Ceased
Application number
PCT/CN2013/090648
Other languages
English (en)
Chinese (zh)
Inventor
周强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2015014085A1 publication Critical patent/WO2015014085A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • 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/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • 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/02—Standardisation; Integration
    • H04L41/0226—Mapping or translating multiple network management protocols

Definitions

  • the present invention relates to the field of communications, and in particular, to a method for protocol conversion and a protocol converter. Background technique
  • the Simple Gateway Monitoring Protocol was greatly modified, especially the management information structure conforming to the Internet definition.
  • SMI Management Information
  • MIB Management Information Base
  • the improved SGMP protocol is the Simple Network Management Protocol (SNMP).
  • SNMP Simple Network Management Protocol
  • the request for Comments RRC
  • the SNMPV3 protocol introduces many concepts of security and multi-view isolation to solve the security problem and is widely used in many newly developed devices.
  • the compatibility with the previous SNMP V1/V2C protocol was not considered. Therefore, there are still a large number of network management systems and devices supporting only SNMP V1/V2C.
  • the device agent (Agent) that supports only the SNMP V3 protocol cannot access the NMS that supports only the SNMP V2C/V1 protocol.
  • the agent of the SNMP V3 protocol when the agent of the SNMP V3 protocol is connected to the management system that supports only the SNMP V1/V2C, the SNMP V3 protocol stack is developed through the network management system to access the device agent of the SNMP V3. This scenario cannot be met because the network management system cannot be modified to support SNMP V1/V2C devices.
  • the Agent by modifying the Agent to support the protocol stack of the SNMP VI/V2C, it is connected with the network management system that implements the V1/V2C, but it is difficult to redevelop the protocol stack by the agent of the device manufacturer.
  • the embodiment of the invention provides a method for protocol conversion, which aims to solve the problem of how to convert the SNMPV3 protocol into an SNMP VI protocol.
  • the first aspect a method for protocol conversion, the method includes: receiving a first simple network management protocol SNMP Trap message sent by a first device proxy, the first device proxy supporting an SNMP V3 protocol, the first SNMP Tra The message follows the SNMP V3 protocol; converting the first SNMP Tra message into a second SNMP Tra message, the second SNMP Tra message following an SNMP VI protocol; sending the second SNMP Tra message to the second A device agent, the second device agent supporting the SNMP VI protocol.
  • the converting the first SNMP Tra message into a second SNMP Tra message includes: using a specific trap type in the second SNMP Tra message The value of the field is set to the value of any bit in the SNMPTrapOID field in the first SNMP Tra message; the value of the SNMPTrap Enterprise field in the second SNMP Tra message is set to the SNMPTrapOID in the first SNMP Tra message The value of the other bit in the field except any one of the bits.
  • the method further includes:
  • the first SNMP Tra message is converted into a third SNMP Tra message,
  • the method includes: setting a value of a community name Community field in a third SNMP Trap message to a value of a context name contextname field in the first SNMP Tra message; setting a value of a PDU TYPE field and a Version field in the third SNMP Tra message to A fixed value corresponding to the SNMP V2C protocol.
  • the method further includes: receiving the first SNMP request message sent by the second device proxy; converting the first SNMP request message into the second SNMP request message; Two SNMP request messages are sent to the first device agent.
  • the method further includes: receiving a third SNMP request message sent by the third device proxy;
  • the converting the first SNMP request message into the second SNMP request message includes: Setting a value of a context name contextname field in the second SNMP request message to a value of a wirte community field or a read community field in the first SNMP request message;
  • the converting the third SNMP request message into the second SNMP request message includes: The value of the wirte community field or the value of the read community field in the third SNMP request message is set to the value of the context name in the second SNMP request message; the value of the Request ID in the third SNMP request message is Set to advance The value of the Request ID in the configured second SNMP request message.
  • the method further includes: setting a value of a wirte community field or a value of a read community field of the first SNMP request message or the third SNMP request message to a first a value of a context name in the response message corresponding to the SNMP request message; setting a value of the Request ID in the first SNMP request message or the third SNMP request message to a preset second SNMP request message The value of the Request ID in the response message.
  • a protocol converter includes: a first receiving unit, configured to receive a first simple network management protocol SNMP Trap message sent by a first device proxy, where the first device proxy supports SNMP V3 The protocol, the first SNMP Tra message follows the SNMP V3 protocol;
  • a first converting unit configured to convert the first SNMP Tra message into a second SNMP Trap message, where the second SNMP Trap message follows the SNMP VI protocol
  • a sending unit configured to send the second SNMP Trap message Sended to the second device proxy, the second device proxy supports the SNMP VI protocol.
  • the first converting unit is specifically configured to: set a value of a specific trap type field in the second SNMP Tra message to the first The value of any bit in the SNMPTrapOID field in the SNMP Tra message; setting the value of the SNMPTrap Enterprise field in the second SNMP Tra message to any one of the SNMPTrapOID fields in the first SNMP Tra message The value of the other bit bits.
  • the protocol converter further includes: a second converting unit, configured to convert the first SNMP Trap message into a third SNMP Tra message, The third SNMP Tra message follows the SNMP V2C protocol;
  • the sending unit is further configured to send the third SNMP Trap message to a third device proxy, where the third device proxy supports the SNMP V2C protocol.
  • the second converting unit includes: a first setting unit, configured to use the third SNMP Tra message The community name of the community name is set to the value of the context name contextname field in the first SNMP Tra message; the second setting unit is configured to set the value of the PDU TYPE field and the Version field in the third SNMP Tra message to SNMP V2C The fixed value corresponding to the protocol.
  • the protocol converter further includes: a second receiving unit, configured to receive a first SNMP request message sent by the second device proxy; and a third converting unit, configured to send the first SNMP request message Converting to the second SNMP request message; the sending unit is further configured to send the second SNMP request message to the first device proxy.
  • the protocol converter further includes: a third receiving unit, configured to receive, by the third device proxy, And a third conversion unit, configured to convert the third SNMP request message into the second SNMP request message.
  • the third converting unit includes: a third setting unit, configured to use the second SNMP request
  • the value of the context name contextname field in the message is set to the value of the wirte community field or the read community field in the first SNMP request message
  • the fourth setting unit is configured to set the value of the Request ID in the second SNMP request message.
  • the value of the Request ID in the first SNMP request message that is pre-configured.
  • the fourth conversion unit includes: a fifth setting unit, configured to use the third The value of the wirte community field or the value of the read community field in the SNMP request message is set to the value of the context name in the second SNMP request message; the sixth setting unit is configured to send the request in the third SNMP request message The value of the ID is set to the value of the Request ID in the second SNMP request message that is pre-configured.
  • the protocol converter further includes: a seventh setting unit, configured to: use a value of a wirte community field of the first SNMP request message or the third SNMP request message Or the value of the read community field is set to the value of the context name in the response message corresponding to the second SNMP request message; the eighth setting unit is configured to send the request in the first SNMP request message or the third SNMP request message The value of the ID is set to a value of the Request ID in the response message corresponding to the second SNMP request message set in advance.
  • the method for the protocol conversion and the protocol converter receive the first simple network management protocol SNMP Trap message sent by the first device proxy, and the first device proxy supports the SNMP V3 protocol,
  • the first SNMP Tra message follows the SNMP V3 protocol; converting the first SNMP Tra message into a second SNMP Tra message, the second SNMP Tra message following an SNMP VI protocol; sending the second SNMP Trap message to The second device proxy supports the SNMP VI protocol to implement conversion between the SNMP V3 protocol and the SNMP V1 protocol.
  • FIG. 1 is a schematic flow chart of a method for protocol conversion according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a method for protocol conversion according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a method for protocol conversion according to an embodiment of the present invention.
  • FIG. 3b is a schematic diagram of a method for protocol conversion according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a protocol converter according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a protocol converter according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a protocol converter according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for protocol conversion according to an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps:
  • Step 101 Receive a first simple network management protocol sent by the first device proxy.
  • the Tram message the first device proxy supports the SNMP V3 protocol, and the first SNMP Trap message follows the SNMP V3 protocol;
  • Step 102 Convert the first SNMP Tra message into a second SNMP Tra message, where the second SNMP Tra message follows an SNMP VI protocol.
  • the converting the first SNMP Tra message into the second SNMP Tra message includes: setting a value of a specific trap type field in the second SNMP Tra message to an SNMPTrapOID in the first SNMP Tra message The value of any bit in the field; the value of the SNMPTrap Enterprise field in the second SNMP Tra message is set to the value of the other bit in the SNMPTrapOID field of the first SNMP Tra message except any one of the bits. .
  • the field used to identify the Trap definition in the first SNMP Tra message that is, the SNMP Notify Type field is converted into the second SNMP Tra message to identify the Trap
  • the field of meaning that is, the snmp Notify Type field
  • the SNMPTrapOID field is converted into a field in the second SNMP Tra message for identifying the same enterprise, that is, a specific trap type field;
  • the SNMPTrapOID field is converted into the field snmp Trap Enterprise field in the second SNMP Tra message to identify the enterprise to which the Trap belongs.
  • Step 103 Send the second SNMP Trap message to the second device proxy, where the second device proxy supports the SNMP VI protocol.
  • the method further includes: converting the first SNMP Trap message into a third SNMP Tra message, where the third SNMP Tra message follows SNMP
  • the V2C protocol sends the third SNMP Trap message to a third device proxy, and the third device proxy supports the SNMP V2C protocol.
  • the converting the first SNMP Tra message into the third SNMP Tra message comprises: setting a value of a community name Community field in the third SNMP Tra message to a context name contextname in the first SNMP Tra message The value of the field; will be the third
  • the values of the PDU TYPE field and the Version field in the SNMP Tra message are set to SNMP.
  • the VB field of the Tra message has the same definition. You can directly assign the value of the VB field in the first SNMP Tra message to the value of the VB field in the third SNMP Tra message. Fill in the community name in the third SNMP Tra message with the context name contextname in the first SNMP Trap message.
  • the community name Community has the semantic meaning, but in the Trap message, the community name Community has no practical effect. Therefore, this semantic change does not have much influence in the actual role, and can be retained at the same time.
  • the method may further include: receiving a first SNMP request message sent by the second device proxy; converting the first SNMP request message into a first Two SNMP request messages; the second SNMP request message is sent to the first device proxy.
  • the converting the first SNMP request message into the second SNMP request message includes: setting a value of a context name contextname field in the second SNMP request message to a wirte in the first SNMP request message a value of the community field or the read community field; setting a value of the Request ID in the second SNMP request message to a value of the Request ID in the first configured SNMP request message.
  • the method may further include: receiving a third SNMP request message sent by the third device proxy; converting the third SNMP request message into the second SNMP request message.
  • the converting the third SNMP request message into the second SNMP request message includes: setting a value of a wirte community field or a value of a read community field in the third SNMP request message to a value of a context name in the second SNMP request message; setting a value of the Request ID in the third SNMP request message to a value of a Request ID in the second SNMP request message configured in advance.
  • the protocol converter converts the first SNMP request according to the first SNMP request.
  • the Request ID in the message or the third SNMP request message configures the Request ID of the third SNMP request message, and maintains the correspondence between the two Request IDs.
  • the method may further include: setting a value of a wirte community field or a value of a read community field of the first SNMP request message or the third SNMP request message to a second SNMP Setting a value of a context name in the response message corresponding to the request message; setting a value of the Request ID in the first SNMP request message or the third SNMP request message to a response corresponding to the second SNMP request message set in advance The value of the Request ID in the message. Specifically, if it is a Set message, the context name in the Set message returned by the first device proxy is filled in the write community, or the context name in the Get message returned by the first device proxy is filled in the read community, and the first device is transparently transmitted. The error status in the response message returned by the proxy, and the Request ID in the first SNMP request message or the third SNMP request message is obtained according to the Request ID in the second SNMP request message, and the Varible binding in the response message is transparently transmitted.
  • the method is configured to receive a first simple network management protocol SNMP Trap message sent by a first device proxy, where the first device proxy supports an SNMP V3 protocol, where the An SNMP Tra message follows the SNMP V3 protocol; converting the first SNMP Tra message into a second SNMP Tra message, the second SNMP Tra message following an SNMP VI protocol; sending the second SNMP Tra message to the The second device proxy supports the SNMP VI protocol, thereby implementing conversion between the SNMP V3 protocol and the SNMP VI protocol.
  • FIG. 2 it is a schematic diagram of a method for protocol conversion provided by an embodiment of the present invention.
  • the protocol converter converts the SNMP Tra message into an SNMP Trap message supported by the second device proxy, or the protocol converter
  • the SNMP Trap message is converted into an SNMP Tra message supported by the third device proxy, and the converted SNMP Tra message is sent to the first device proxy.
  • FIG. 3a is a schematic diagram of a method for protocol conversion according to an embodiment of the present invention.
  • the protocol converter receives the SNMP Trap message sent by the second device proxy, converts it into an SNMP Tra message supported by the first device proxy, and sends the converted SNMP Trap message to the first device proxy.
  • FIG. 3b is a schematic diagram of a method for protocol conversion according to an embodiment of the present invention.
  • the protocol converter receives the SNMP Trap message sent by the third device proxy, converts it into an SNMP Tra message supported by the first device proxy, and sends the converted SNMP Trap message to the first device proxy.
  • Receiving an SNMP Trap returned by the first device proxy The response message, the protocol converter converts the response message, and sends the converted response message to the third device proxy.
  • FIG. 2 The method for the protocol conversion between the communication messages in FIG. 2, FIG. 3a and FIG. 3b can be referred to the foregoing embodiment, and details are not described herein again.
  • FIG. 4 is a schematic structural diagram of a protocol converter according to an embodiment of the present invention.
  • the protocol converter 400 includes the following units:
  • the first receiving unit 401 is configured to receive a first simple network management protocol SNMP Tra message sent by the first device proxy, where the first device proxy supports an SNMP V3 protocol, and the first SNMP Tra message follows the SNMP V3 protocol;
  • a first converting unit 402 configured to convert the first SNMP Tra message into a second
  • the SNMP Tra message, the second SNMP Tra message follows the SNMP VI protocol.
  • the first converting unit 402 is specifically configured to: set a value of a specific trap type field in the second SNMP Trap message to a value of any one of the SNMPTrapOID fields in the first SNMP Tra message; setting a value of the SNMPTrap Enterprise field in the second SNMP Tra message to the SNMPTrapOID field in the first SNMP Tra message The value of the other bit of any bit.
  • the field used to identify the Trap definition in the first SNMP Tra message is converted into a field in the second SNMP Tra message for identifying the Trap definition, that is, the snmp Notify Type field;
  • the field used to identify the same enterprise in the first SNMP Tra message that is, the SNMPTrapOID field is converted into a field in the second SNMP Tra message for identifying the same enterprise, that is, a specific trap type field; and the first SNMP Tra message is used.
  • the field that identifies the enterprise to which the trap belongs that is, the SNMPTrapOID field is converted into the snmp Trap Enterprise field of the second SNMP Tra message to identify the enterprise to which the trap belongs.
  • the sending unit 403 is configured to send the second SNMP Tra message to the second device proxy, where the second device proxy supports the SNMP VI protocol.
  • the protocol converter receives the first simple network management protocol SNMP Trap message sent by the first device proxy, the first device proxy supports the SNMP V3 protocol, and the first SNMP Tra message Follow the SNMP V3 protocol; Converting the first SNMP Tra message into a second SNMP Tra message, the second SNMP Tra message following an SNMP VI protocol; sending the second SNMP Tra message to the second device proxy, the second device proxy
  • the SNMP VI protocol is supported to implement conversion between the SNMP V3 protocol and the SNMP VI protocol.
  • FIG. 5 is a structural diagram of a device of a protocol converter 500 according to an embodiment of the present invention.
  • the protocol converter 500 may further include: a first receiving unit 501, configured to receive a first simple network management protocol SNMP Tra message sent by the first device proxy, where the first device proxy supports the SNMP V3 protocol, The first SNMP Tra message follows the SNMP V3 protocol;
  • a first converting unit 502 configured to convert the first SNMP Tra message into a second
  • An SNMP Tra message the second SNMP Tra message follows the SNMP VI protocol; a sending unit 503, configured to send the second SNMP Trap message to the second device proxy, where the second device proxy supports an SNMP VI Agreement
  • a second converting unit 504 configured to convert the first SNMP Tra message into a third SNMP Tra message, where the third SNMP Tra message follows an SNMP V2C protocol;
  • the second converting unit 504 includes: a first setting unit 504a, configured to set a value of a community name Community field in the third SNMP Tra message to a context name contextname field in the first SNMP Tra message
  • the second setting unit 504b is configured to set a value of a PDU TYPE field and a Version field in the third SNMP Tra message to a fixed value corresponding to the SNMP V2C protocol.
  • the sending unit 503 is further configured to send the third SNMP Tra message to a third device proxy, where the third device proxy supports the SNMP V2C protocol.
  • the protocol converter may further include: a second receiving unit 505, configured to receive a first SNMP request message sent by the second device proxy;
  • the third converting unit 506 is configured to convert the first SNMP request message into a second SNMP request message.
  • the sending unit 503 is further configured to send the second SNMP request message to the first device proxy.
  • the protocol converter may further include: a third receiving unit 507, configured to receive a third SNMP request message sent by the third device proxy;
  • the fourth converting unit 508 is configured to convert the third SNMP request message into the second SNMP request message.
  • the third converting unit 506 includes: a third setting unit 506a, configured to set a value of a context name contextname field in the second SNMP request message to a wirte community field in the first SNMP request message. Or the value of the read community field; the fourth setting unit 506b is configured to set a value of the Request ID in the second SNMP request message to a value of the Request ID in the first configured SNMP request message.
  • the fourth converting unit 508 includes: a fifth setting unit 508a, configured to set a value of a wirte community field or a value of a read community field in the third SNMP request message to the second SNMP The value of the context name in the request message is set; the sixth setting unit 508b is configured to set a value of the Request ID in the third SNMP request message to a value of the Request ID in the second SNMP request message configured in advance.
  • the protocol converter converts the first SNMP request according to the first SNMP request.
  • the Request ID in the message or the third SNMP request message configures the Request ID of the third SNMP request message, and maintains the pair of the above two Request IDs. Should be related.
  • the protocol converter may further include: a seventh setting unit 509, configured to: use a value of a wirte community field of the first SNMP request message or the third SNMP request message Or the value of the read community field is set to the value of the context name in the response message corresponding to the second SNMP request message;
  • the eighth setting unit 510 is configured to set a value of the Request ID in the first SNMP request message or the third SNMP request message to a Request ID in a response message corresponding to the second SNMP request message set in advance Value.
  • the context name in the Set message returned by the first device proxy is filled in the write community, or the context name in the Get message returned by the first device proxy is filled in the read community, and the first device is transparently transmitted.
  • the error status in the response message returned by the proxy, and the Request ID in the first SNMP request message or the third SNMP request message is obtained according to the Request ID in the second SNMP request message, and the Varible binding in the response message is transparently transmitted.
  • a protocol converter receives the first simple network management protocol SNMP Trap message sent by the first device proxy, and the first device proxy supports the SNMP V3 protocol,
  • the first SNMP Tra message follows the SNMP V3 protocol; converting the first SNMP Tra message into a second SNMP Tra message, the second SNMP Tra message following an SNMP VI protocol; sending the second SNMP Tra message to
  • the second device proxy supports the SNMP VI protocol to implement conversion between the SNMP V3 protocol and the SNMP VI protocol.
  • FIG. 6 is a schematic structural diagram of a protocol converter according to an embodiment of the present invention.
  • FIG. 6 is a protocol converter 600 according to an embodiment of the present invention.
  • the embodiment of the present invention does not limit the specific implementation of the protocol converter.
  • the protocol converter 600 includes a processor 601, a communication interface 602, a memory 603, and a bus 604.
  • the processor 601, the communication interface 602, and the memory 603 complete communication with each other via the bus 604.
  • the communication interface 602 is configured to communicate with other devices than the protocol converter 600 described in the embodiment of the present invention;
  • the processor 601 is configured to execute a program stored in the memory 603, where the program may be an operating system program or an application.
  • the program can include program code, the program code including computer operating instructions.
  • the processor 601 may be a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.
  • the memory 603 is configured to store a program.
  • the memory 603 may include a random access memory (RAM) memory, and may also include a non-volatile memory, for example, at least one disk storage device.
  • RAM random access memory
  • the processor 601 is configured to invoke a program in the memory 603 and perform the following operations: receiving a first simple network management protocol SNMP Trap message sent by the first device proxy, the first device proxy supporting an SNMP V3 protocol, the first SNMP Tra message follows the SNMP V3 protocol; converting the first SNMP Tra message into a second SNMP Trap message, the second SNMP Tra message following an SNMP VI protocol; sending the second SNMP Trap message to the A device proxy that supports the SNMP VI protocol.
  • protocol converter 600 is independent of the first device agent or the second device agent, then message communication with the device agent or the second device agent is implemented via the communication interface 602.
  • the converting the first SNMP Tra message into the second SNMP Tra message includes: setting a value of a specific trap type field in the second SNMP Tra message to an SNMPTrapOID field in the first SNMP Tra message
  • the value of any bit in the second SNMP Tra message is set to the value of the other bit bits of the SNMPTrapOID field in the first SNMP Tra message except the any one of the bits.
  • the processor 601 is further configured to: convert the first SNMP Trap message into a third SNMP Tra message, where the third SNMP Tra message follows an SNMP V2C protocol; and the third SNMP Trap message is sent Sended to a third device proxy, the third device proxy supports the SNMP V2C protocol.
  • the converting the first SNMP Tra message into a third SNMP Tra includes: setting a value of a community name Community field in the third SNMP Tra message to a value of a context name contextname field in the first SNMP Tra message; setting a value of a PDU TYPE field and a Version field in the third SNMP Tra message Set to a fixed value corresponding to the SNMP V2C protocol.
  • the processor 601 is further configured to: receive a first SNMP request message sent by the second device proxy; convert the first SNMP request message into a second SNMP request message; The second SNMP request message is sent to the first device proxy.
  • the converting the first SNMP request message into the second SNMP request message includes: setting a value of a context name contextname field in the second SNMP request message to a wirte community in the first SNMP request message.
  • the processor 601 is further configured to: receive a third SNMP request message sent by the third device proxy; and convert the third SNMP request message into the second SNMP request message.
  • the processor 601 is further configured to: set a value of a wirte community field or a value of a read community field of the first SNMP request message or the third SNMP request message to a second SNMP Setting a value of a context name in the response message corresponding to the request message; setting a value of the Request ID in the first SNMP request message or the third SNMP request message to a response corresponding to the second SNMP request message set in advance The value of the Request ID in the message.
  • each embodiment in this specification is described in a progressive manner, each The same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments.
  • the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.
  • the method for protocol conversion and the protocol converter receive the first simple network management protocol SNMP Trap message sent by the first device proxy, and the first device proxy supports the SNMP V3 protocol.
  • the first SNMP Tra message follows the SNMP V3 protocol; converting the first SNMP Tra message into a second SNMP Trap message, the second SNMP Tra message following an SNMP VI protocol; and the second SNMP Trap
  • the message is sent to the second device proxy, and the second device proxy supports the SNMP VI protocol, thereby implementing conversion between the SNMP V3 protocol and the SNMP VI protocol.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as the cells may or may not be physical. Units can be located in one place, or they can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • the connection relationship between the modules indicates that there is a communication connection between them, and specifically, one or more communication buses or signal lines can be realized.
  • the present invention can be implemented by means of software plus necessary general hardware, and of course, dedicated hardware, dedicated CPU, dedicated memory, dedicated memory, Special components and so on.
  • functions performed by computer programs can be easily implemented with the corresponding hardware.
  • the specific hardware structure used to implement the same function can be various, such as analog circuits, digital circuits, or dedicated circuits. Circuits, etc.
  • software program implementation is a better implementation in more cases.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer.
  • U disk mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory, a disk or an optical disk, etc.
  • ROM read-only memory
  • RAM random access memory
  • a disk or an optical disk, etc. includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Communication Control (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé de conversion de protocole et un convertisseur de protocole. Ledit procédé consiste : à recevoir un premier message d'interruption SNMP envoyé par un premier agent de dispositif, ce premier agent de dispositif prenant en charge le protocole SNMPv3, et le premier message d'interruption SNMP suivant le protocole SNMPv3 ; à convertir le premier message d'interruption SNMP en un second message d'interruption SNMP, ce second message suivant le protocole SNMPv1 ; et à envoyer le second message d'interruption SNMP à un second agent de dispositif, ce second agent de dispositif prenant en charge le protocole SNMPv1. Par conséquent, la conversion entre le protocole SNMPv3 et le protocole SNMPv1 est terminée.
PCT/CN2013/090648 2013-07-29 2013-12-27 Procédé de conversion de protocole et convertisseur de protocole Ceased WO2015014085A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310323158.8A CN103401859B (zh) 2013-07-29 2013-07-29 一种协议转换的方法及协议转换器
CN201310323158.8 2013-07-29

Publications (1)

Publication Number Publication Date
WO2015014085A1 true WO2015014085A1 (fr) 2015-02-05

Family

ID=49565385

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/090648 Ceased WO2015014085A1 (fr) 2013-07-29 2013-12-27 Procédé de conversion de protocole et convertisseur de protocole

Country Status (2)

Country Link
CN (1) CN103401859B (fr)
WO (1) WO2015014085A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103401859B (zh) * 2013-07-29 2016-08-10 华为技术有限公司 一种协议转换的方法及协议转换器
CN106357590A (zh) * 2015-07-15 2017-01-25 艾默生网络能源系统北美公司 一种网络协议转换系统、网络协议转换器及其转换方法
CN107733669B (zh) * 2016-08-11 2023-03-14 中兴通讯股份有限公司 基于request ID的SNMP服务器管理方法及系统
CN106452839A (zh) * 2016-09-05 2017-02-22 杭州华为数字技术有限公司 一种消息上报方法及装置
CN108449312B (zh) * 2018-01-31 2021-01-22 北京奇艺世纪科技有限公司 一种协议转换方法、装置、系统及网关
CN112383408B (zh) * 2020-09-29 2023-04-11 武汉虹信科技发展有限责任公司 一种用于数据格式转换的管理平台端和数据格式转换方法

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001024445A2 (fr) * 1999-09-28 2001-04-05 Thomson Licensing S.A. SYSTEME ET PROCEDE PERMETTANT A DES MODEMS POUR PROTOCOLE DE GESTION DE RESEAU SIMPLE (SNMP) D'INTEROPERER AVEC DES MODEMS SNMP v1/v2c
US20020120730A1 (en) * 2001-02-27 2002-08-29 Goudzwaard Daniel John Reliability for simple network management protocol trap messages
CN1741461A (zh) * 2004-08-23 2006-03-01 华为技术有限公司 在网管系统中处理设备信息的方法及系统
CN101035133A (zh) * 2007-04-09 2007-09-12 华为技术有限公司 网络管理的方法、系统及设备
CN101043361A (zh) * 2006-06-16 2007-09-26 华为技术有限公司 一种基于snmp协议进行网络管理的方法和系统
CN101494561A (zh) * 2009-03-04 2009-07-29 中兴通讯股份有限公司 一种基于简单网络管理协议的网络管理方法和系统
CN103401859A (zh) * 2013-07-29 2013-11-20 华为技术有限公司 一种协议转换的方法及协议转换器

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080098103A1 (en) * 2006-10-18 2008-04-24 Mathi Packiam Methods and Apparatus for Tunneling Legacy Network Management Messages through SNMP (Simple Network Management Protocol)
CN101662391B (zh) * 2009-09-25 2011-08-17 迈普通信技术股份有限公司 基于简单网络管理协议版本3的以太网交换机集群管理方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001024445A2 (fr) * 1999-09-28 2001-04-05 Thomson Licensing S.A. SYSTEME ET PROCEDE PERMETTANT A DES MODEMS POUR PROTOCOLE DE GESTION DE RESEAU SIMPLE (SNMP) D'INTEROPERER AVEC DES MODEMS SNMP v1/v2c
US20020120730A1 (en) * 2001-02-27 2002-08-29 Goudzwaard Daniel John Reliability for simple network management protocol trap messages
CN1741461A (zh) * 2004-08-23 2006-03-01 华为技术有限公司 在网管系统中处理设备信息的方法及系统
CN101043361A (zh) * 2006-06-16 2007-09-26 华为技术有限公司 一种基于snmp协议进行网络管理的方法和系统
CN101035133A (zh) * 2007-04-09 2007-09-12 华为技术有限公司 网络管理的方法、系统及设备
CN101494561A (zh) * 2009-03-04 2009-07-29 中兴通讯股份有限公司 一种基于简单网络管理协议的网络管理方法和系统
CN103401859A (zh) * 2013-07-29 2013-11-20 华为技术有限公司 一种协议转换的方法及协议转换器

Also Published As

Publication number Publication date
CN103401859A (zh) 2013-11-20
CN103401859B (zh) 2016-08-10

Similar Documents

Publication Publication Date Title
US12052233B2 (en) Identity verification method for network function service and related apparatus
EP3878148B1 (fr) Gestion de noms de domaines entièrement qualifiée pour des interactions de service en 5g
CN102845123B (zh) 虚拟私云的连接方法及隧道代理服务器
JP6085891B2 (ja) アクセス制御方法およびシステム、ならびにアクセスポイント
JP7609361B2 (ja) 通信方法、関連する装置及びシステム
CN106790420B (zh) 一种多会话通道建立方法和系统
CN115989689B (zh) 用于边缘数据网络的用户装备认证和授权规程的方法和设备
US10601830B2 (en) Method, device and system for obtaining local domain name
CN103401859B (zh) 一种协议转换的方法及协议转换器
WO2019157968A1 (fr) Procédé, appareil, et système de communication
WO2015127603A1 (fr) Entité de service de gestion d'interfaces, entité fonctionnelle de services et procédé de gestion d'éléments de réseau
CN106535089B (zh) 机器对机器虚拟私有网络
CN111064742B (zh) 一种基于网络代理实现内网访问的方法、装置及相关设备
WO2014071841A1 (fr) Procédé, terminal, serveur, système et dispositif de synchronisation de paramètres de réseau sans fil
CN114024664B (zh) 安全通信方法、相关装置及系统
CN104243198A (zh) 一种基于网络配置协议的网络管理方法和系统
WO2012041029A1 (fr) Procédé et dispositif pour service de traitement de serveur
CN119697634B (zh) 基于5g vpdn的后路由组网方法、装置及设备
EP2466814B1 (fr) Procédé, serveur d'accès distant et système de configuration de la qualité de service
WO2012139463A1 (fr) Procédé et dispositif d'initialisation de dispositif terminal
WO2021136301A1 (fr) Procédé et appareil de communication
CN103167022B (zh) 一种数据包传输方法、相关设备及系统
JP5778862B2 (ja) クラウドベースのｉｄ管理（ｃ−ｉｄｍ）を実装するための方法および仮想ｉｄｍサーバー
CN103974245B (zh) 设备配置方法、设备及系统
CN118614099A (zh) 基于tls-psk的用于接入边缘数据网络的认证机制

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13890382

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13890382

Country of ref document: EP

Kind code of ref document: A1