WO2021136175A1 - 设备管理方法、装置、通信设备及存储介质 - Google Patents

设备管理方法、装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2021136175A1
WO2021136175A1 PCT/CN2020/140173 CN2020140173W WO2021136175A1 WO 2021136175 A1 WO2021136175 A1 WO 2021136175A1 CN 2020140173 W CN2020140173 W CN 2020140173W WO 2021136175 A1 WO2021136175 A1 WO 2021136175A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
network
message
address
intranet
Prior art date
Application number
PCT/CN2020/140173
Other languages
English (en)
French (fr)
Inventor
罗良桂
冯均豪
叶祖铨
Original Assignee
京信网络系统股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 京信网络系统股份有限公司 filed Critical 京信网络系统股份有限公司
Publication of WO2021136175A1 publication Critical patent/WO2021136175A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • 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

Definitions

  • the present invention relates to the field of communication technology, and in particular to an equipment management method, device, communication equipment and storage medium.
  • a centralized networking method needs to be adopted, for example, this kind of networking method needs to be used in some backhaul networks.
  • IP Internet Protocol
  • a backhaul site usually only allocates one transmitted monitoring IP to multiple communication devices in a centralized network, so that the network manager can perform monitoring on these communication devices. Monitoring and operation and maintenance.
  • the current commonly used method is to implement the network address translation (NAT) function or add NAT on the communication equipment connected to the backhaul network. Then, the data packets sent by other communication devices at the site to the network management system are sent to the network management system after passing through the NAT-capable device or NAT device, so that the network management system can monitor other communication devices using private network IP addresses.
  • NAT network address translation
  • this method usually needs to record the IP addresses and User Datagram Protocol (UDP) ports of different communication devices after NAT on the network management, and it needs to maintain a large number of heartbeat messages and processing between the communication devices and the network management.
  • the data of each communication device must be processed at the same time for multiple communication devices in the centralized network, and NAT devices are usually added.
  • the technical problem to be solved by this application is to solve the problem that the large workload of the existing network management affects the performance of the network system.
  • embodiments of the present application provide a device management method, device, communication device, and storage medium.
  • a device management method includes:
  • the method is applied to a gateway device, the gateway device is deployed between a network management device and an intranet device cluster, the gateway device and the network management device communicate based on a predetermined data transmission protocol, and the gateway device communicates with the The intranet device clusters communicate based on a predetermined network management protocol; the method includes:
  • the destination device identifier is the device identifier of the gateway device itself, responding to the first management message to perform a management operation corresponding to the first management message;
  • the first private network corresponding to the target device identifier is determined according to the correspondence between the device identifier of the intranet device and the corresponding private network IP address IP address; and according to the first private network IP address, the first management message is converted into a second management message that conforms to the predetermined network management protocol, and the destination IP address of the second management message is all The first private network IP address; and the second management message is sent to the first intranet device corresponding to the first private network IP address, so that the first intranet device executes the communication with the second Management operations corresponding to management messages.
  • a device management device is provided, the device is applied to a gateway device, the gateway device is deployed between a network management device and an intranet device cluster, and the connection between the gateway device and the network management device is based on predetermined data
  • the communication is carried out by a transmission protocol, and the communication between the gateway device and the intranet device cluster is based on a predetermined network management protocol; the device includes:
  • the receiving module is configured to receive a first management message sent by the network management device based on the predetermined data transmission protocol, wherein the destination IP address of the first management message is the public network IP address of the gateway device, and The first management message carries the target device identifier;
  • the determining module is used to determine whether the target device identifier is the device identifier of the gateway device itself;
  • a response module configured to respond to the first management message when the target device identifier is the device identifier of the gateway device itself, so as to perform a management operation corresponding to the first management message;
  • the response module is also used to determine the connection with the target device according to the correspondence between the device identity of the intranet device and the corresponding private network IP address when the target device identity is not the device identity of the gateway device itself.
  • the sending module is configured to send the second management message to the first intranet device corresponding to the first private network IP address, so that the first intranet device executes the correspondence with the second management message Management operations.
  • a communication device in a third aspect, includes:
  • Memory used to store program instructions
  • the processor is configured to call the program instructions stored in the memory, and execute the steps included in any one of the device management methods in the first aspect according to the obtained program instructions.
  • a computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to make a computer execute the device management method described in the first aspect Steps included.
  • a computer program product containing instructions, which when the computer program product runs on a computer, causes the computer to execute the device management methods described in the foregoing various possible implementation manners.
  • the gateway device can monitor, manage, and maintain multiple intranet devices (such as intranet switches) that use private network IP addresses because of the integrated protocol conversion and message aggregation capabilities. It is the protocol conversion of the management instructions of the network management equipment and then issued to each intranet device. Each intranet device can be managed individually, and it can also be used for parameter setting, parameter query, software upgrade, etc. of multiple intranet devices. Batch processing. In this way, based on the protocol exchange capability of the gateway device, the management load of the network management device on each intranet device can be reduced to a large extent. The service sharing of the network management device by the gateway device can reduce the processing load of the network management device.
  • intranet devices such as intranet switches
  • the operating performance of the network management equipment can be improved, and at the same time, multiple internal network equipment based on the internal network IP address communication under the networking application can be managed, which can reduce the overall operating cost, thereby expanding the application scope of the entire system and improving the operation of the system performance.
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the application
  • FIG. 2 is a schematic diagram of the architecture of a device management system provided by an embodiment of the application
  • FIG. 3 is a flowchart of a device management method provided by an embodiment of the application.
  • FIG. 4 is another flowchart of a device management method provided by an embodiment of the application.
  • FIG. 5 is another flowchart of a device management method provided by an embodiment of the application.
  • Fig. 6a is a structural block diagram of a device management apparatus provided by an embodiment of the application.
  • FIG. 6b is another structural block diagram of the device management apparatus provided by an embodiment of the application.
  • FIG. 7 is a schematic structural diagram of a communication device provided by an embodiment of the application.
  • some existing network architectures need to adopt a centralized networking method.
  • many 4G small base stations need to use the 1588v2 protocol for synchronization.
  • many current backhaul networks do not support the 1588v2 protocol, so these backhaul networks need to adopt a centralized networking method, that is, many switches and at least one 1588 synchronization source are used at the same backhaul site, and then the 1588 synchronization source data is centralized
  • the network switch network is passed to the 4G small base station.
  • operators usually allocate only one monitoring IP for transmission to multiple switches in a centralized network so that the network manager can monitor and operate and maintain these switches.
  • the current commonly used method is to implement NAT function or add NAT equipment on the switch equipment connected to the backhaul network, and then send to other switches under the site
  • the data packets of the network management system are sent to the network management system after passing through the switch or NAT device with the NAT function, so that the network management system can monitor other switches using the private network IP address.
  • This method usually needs to record the IP addresses and UDP ports of different switches after NAT on the network management, and it needs to maintain a large number of heartbeat messages between the switches and the network management and process the data of each switch. At the same time, it needs to realize the centralized network. To deal with multiple switches, usually additional NAT equipment is required.
  • the embodiment of the present application provides a device management solution for converging protocol conversion.
  • a protocol conversion and convergence processing module is used.
  • the protocol conversion and convergence processing module can be centrally deployed in the switch, or can be deployed independently
  • the protocol conversion and aggregation processing module supports protocol conversion functions, message aggregation, and batch processing functions. It is used to solve the monitoring and management problem of the existing network management equipment on the switch that uses the private network IP address for centralized networking, and to realize the function of protocol conversion and aggregation processing module on the existing network equipment, without the need for additional NAT equipment to connect the private network of the switch.
  • the network IP address is converted into a public network IP address.
  • the clock synchronization module necessary for the network performs protocol forwarding, data consolidation and distribution and unified processing functions for the data between the equipment management device and the switch, so that the network management system can manage and It presents a large-scale networking protocol forwarding processing module and multiple switch devices, and can realize single processing and batch processing of switches (such as batch software upgrades, parameter settings and queries, etc.), so that the entire system can not only traverse the NAT network, but also reduce The requirements for network IP and bandwidth achieve the purpose of improving the performance of the entire network system and reducing the overall operating cost, expanding the scope of application of the entire system.
  • Figure 2 is an application scenario to which the technical solution of the embodiment of this application can be applied.
  • it includes a network management device, two gateway devices (ie, gateway device 1, gateway device 2), and Multiple intranet devices (namely, intranet device 1, intranet device 2, intranet device 3, intranet device 4, intranet device 5, and intranet device 6).
  • the gateway device 1, the gateway device 2 and the network management device are based on public network transmission, that is, the gateway device 1 and the gateway device 2 communicate with the network management device based on the pre-allocated public network IP address.
  • Gateway device 1 and gateway device 2 are configured with multiple intranet devices.
  • gateway device 1 is configured with intranet device 1, intranet device 2, and intranet device 3, and gateway device 2 is configured with intranet device 4, Intranet device 5, intranet device 6, each gateway device and its configured intranet device communicate based on the private network IP address.
  • the gateway device 1, the gateway device 2 and the network management device communicate based on the TR069 (Technical Report 069, TR069) protocol or other data transmission protocols.
  • TR069 Technical Report 069, TR069
  • the gateway device 1, the gateway device 2 and the respective following The internal network devices communicate based on the Simple Network Management Protocol (SNMP) protocol, that is, the transmission protocol between the internal network and the public network is different.
  • SNMP Simple Network Management Protocol
  • a protocol conversion and convergence processing module is proposed, which is deployed in the gateway device 1 and the gateway device 2 in FIG. 1.
  • the gateway device 1 and gateway device 2 at this time can be switch devices.
  • the gateway device 1 and gateway device 2 can be Other types of devices, such as other devices that support protocol conversion and message aggregation processing, are not limited in the embodiment of the present application.
  • the message sent by the network management device to each intranet device can be forwarded through the gateway device through protocol conversion.
  • the message sent by each intranet device to the network management device is also forwarded after the gateway device passes through the protocol conversion. To the network management equipment.
  • the gateway device integrates the capabilities of protocol conversion and message aggregation processing, it can monitor, manage and maintain multiple intranet devices (such as intranet switches) that use private network IP addresses, specifically, the network management After protocol conversion, the management instructions of the equipment are issued to each intranet device. Each device can be managed individually, or the parameter settings, parameter queries, and software upgrades of multiple intranet devices can be processed in batches.
  • the heartbeat between all internal network equipment and network management equipment can be centrally maintained through the network management equipment. In this way, based on the protocol conversion capability of the gateway device, the management service of the network management equipment to the internal network equipment cluster can be shared, which can reduce the network management to a large extent.
  • the management load of the equipment on each internal network device, and the service sharing of the network management equipment through the gateway device can improve the operating performance of the network management equipment, and at the same time, it can realize the multiple internal network equipment based on the private network IP address communication under the networking application. Management can reduce overall operating costs, thereby expanding the scope of application of the entire system and improving the operating performance of the system.
  • Each of the aforementioned devices may have a unique device identifier (for example, a serial number of the device), and the unique device identifier of each device is used to distinguish each device.
  • the above-mentioned network management equipment may be a computer or a server, for example, a personal computer, a large and medium-sized computer, a computer cluster, etc.; the gateway equipment 1, 2 may be a switch or other communication equipment that supports protocol conversion; the internal network equipment 1-6 is, for example, Switches, routers, etc., are not limited in the embodiment of the present application.
  • Figure 2 is a device management system provided by an embodiment of this application.
  • the device management system includes a network management device, a gateway device, and an intranet device cluster composed of multiple intranet devices.
  • the gateway device and the network management device communicate based on a predetermined data transmission protocol, the predetermined data transmission protocol is, for example, the TR069 protocol, and the gateway device and the intranet device cluster communicate based on a predetermined network management protocol, the predetermined network management protocol
  • the predetermined network management protocol For example, it is the SNMP protocol, that is, the communication protocol between the gateway device and the network management device and the intranet device cluster is different.
  • the gateway device in the embodiment supports protocol conversion to support data interaction between the network management device and the intranet device through the protocol conversion function.
  • the communication between the gateway device and the network management device is based on the public network IP address
  • the communication between the gateway device and the internal network device is based on the private network IP address, so through the protocol conversion function of the gateway device, the public network can be used.
  • the communication between the device with the IP address and the device with the private network IP address thereby expanding the application of the system.
  • an embodiment of the present application provides a device management method.
  • the device management method includes a communication method between a network management device and a gateway device, a communication method between a gateway device and an intranet device, and a network management method.
  • the three parts of the communication method between the device and the internal network device are described separately for ease of understanding.
  • FIG. 3 shows the communication flow between the network management device and the gateway device in the device management method in the embodiment of the present application.
  • the process shown in Figure 3 is described as follows.
  • Step 301 The gateway device sends a first registration request message to the network management device.
  • the gateway device Before the gateway device communicates with the network management device, the gateway device needs to register with the network management device. Registration can be regarded as the authentication authority to the network management device. When registering, the gateway device can send a registration request to the network management device, for example, sending a first registration request message.
  • the first registration request message carries the public network IP address of the gateway device and the device identifier of the gateway device, and the device of the gateway device The identifier is used to uniquely identify the gateway device, such as the device serial number.
  • Step 302 After receiving the first registration request message sent by the gateway device, the network management device may register the public network IP address and device identifier of the gateway device according to the first registration request message to complete the registration of the gateway device.
  • Step 303 The network management device sends a registration response message to the gateway device.
  • the network management device can first perform permission authentication. When it is determined that the gateway device has the registration permission, it can register, that is, the registration is successful. When it is determined that the gateway device does not have the registration permission, it does not need to register. , That is, registration failed. After successfully completing the registration of the gateway device, the network management device can respond to the gateway device registration, for example, generate a corresponding first registration response message. The first registration response message is after the network management device successfully registers the gateway device according to the first registration request message. Generate a feedback message and feed back the first registration response message to the gateway device to inform the gateway device that its registration is successful. Similarly, when the registration fails, the network management device may also provide a registration failure feedback to the gateway device, so that the gateway device knows that it has not successfully registered in time.
  • Step 304 The gateway device sends a heartbeat message to the network management device.
  • the gateway device can periodically or periodically send a heartbeat message to the network management device.
  • the heartbeat message carries the device identification of the gateway device.
  • the heartbeat message maintains the online status of the communication between the gateway device and the network management device.
  • Step 305 The network management device sends a first management message to the gateway device, where the first management message carries the public network IP address and the device identifier of the gateway device.
  • the network management device can manage the gateway device. Specifically, the network management device can perform device management on the gateway device by sending a management message to the gateway device. For example, the network management device may send a first management message to the gateway device.
  • the first management message carries the public network IP address of the gateway device and the device identification of the gateway device.
  • the gateway device and the network management device are based on the public network. Network communication, so the destination IP address of the first management message is the public network IP address of the gateway device.
  • the network management device can query and set related parameters in the gateway device, or notify some of the gateway device Functions are upgraded, and so on.
  • Step 306 After receiving the first management message, the gateway device responds to the first management message to perform a corresponding management operation.
  • the gateway device may, for example, set some parameters in the gateway device, or query some parameters in the gateway device and then feed back to the network management device, or perform some function upgrades, and so on.
  • the network management device can manage the gateway device.
  • FIG. 4 shows the communication flow between the network management device, the gateway device, and the intranet device (for example, the first intranet device) in the device management method in the embodiment of the present application.
  • the process shown in Figure 4 is described as follows.
  • Step 401 The first intranet device sends a second registration request message to the gateway device, where the second registration request message carries the device identification of the first intranet device, for example, the first device identification.
  • the data interaction between the first intranet device and the network management device can be converted and sent through the gateway device after protocol conversion.
  • the prerequisite for data interaction between the first intranet device and the network management device is also to register with the network management device.
  • the first intranet device and the network management device since the first intranet device and the network management device perform relay communication through the gateway device, when the first intranet device registers with the network management device, it may first send the first intranet device carrying the first intranet device to the gateway device.
  • a second registration request message identified by a device is used to initiate a registration request to the network management device after being relayed by the gateway device through the second registration request message.
  • the gateway device that is, the first intranet device It may include only one intranet device or multiple intranet devices at the same time.
  • the first device identifier is the device identifier corresponding to each of the multiple intranet devices.
  • Step 402 The gateway device performs protocol conversion, and converts the second registration request message into a registration request message conforming to the communication protocol between the network management device and the gateway device (for example, the aforementioned TR069 protocol), and the converted registration request message carries the information of the gateway device.
  • the public network IP address and the first device identifier are examples of the gateway device.
  • the method for the first intranet device to register is to register and forward through the protocol conversion capability of the gateway device, that is, the gateway device will first perform protocol conversion on the second registration request message sent by the first intranet device, and Since the first intranet device needs to be registered, the converted registration request message carries the first device identifier corresponding to the first intranet device.
  • Step 403 The gateway device sends the converted registration request message to the network management device to request registration for the first intranet device.
  • the gateway device may uniformly protocol the registration request messages sent by multiple internal network devices. Conversion to obtain a converted registration request message.
  • the converted registration request message is called a batch registration request message.
  • the batch registration request message carries multiple device IDs corresponding to multiple intranet devices, that is, corresponding
  • the foregoing first device identifier includes multiple device identifiers, so that multiple intranet devices can be registered in batches, which can reduce the number of messages (such as registration request messages) transmitted between the gateway device and the network management device, and at the same time Reduce the registration response messages fed back by the network management device after registering to improve network performance.
  • Step 404 After receiving the converted registration request message, the network management device registers the public network IP address of the gateway device and the first device identifier of the first internal network device according to the converted registration request message, so as to complete the first internal network registration. Registration of network equipment.
  • step 404 the registration and registration response process of the network management device to the first intranet device can be referred to the foregoing steps 302 to 303. Implementation, I will not repeat the introduction here.
  • Step 405 The gateway device sends an online query message to the first intranet device.
  • Step 406 The first intranet device sends an online feedback message to the gateway device.
  • the online query message is a query message used to request the online status of the first intranet device.
  • the first intranet device When the first intranet device is online, it needs to send an online feedback message to the gateway device so that the gateway device knows that it is online; If an intranet device is offline, then it is unable to return an online feedback message. Therefore, if an online feedback message from an intranet device is not received, it can be considered that the intranet device is offline, that is, it is no longer in a communication state.
  • the gateway device can dynamically mark the presence status of each intranet device.
  • Step 407 The gateway device sends a heartbeat message to the network management device, where the heartbeat message carries the device identifier of the gateway device and the first device identifier of the first intranet device.
  • the device ID included in the heartbeat message can be used to indicate which devices are currently online.
  • the device ID 1, device ID 2, and device ID 3 included in the heartbeat message can indicate that they are connected to device ID 1, device ID 2, and device ID.
  • the three devices corresponding to the identifier 3 are currently online, that is, the first device identifier may refer to multiple device identifiers corresponding to multiple intranet devices in the online state.
  • the gateway device can send its own heartbeat message and the heartbeat message of the intranet device together, then the heartbeat message can carry the device identification of the gateway device and the device identification of the online intranet device at the same time, or in another In an implementation manner, the gateway device may also send its own heartbeat message and the heartbeat messages of all online intranet devices separately.
  • the gateway device can query the online status of each intranet device, so the heartbeat messages of each intranet device can be combined into a heartbeat message in batches and sent to the network management device at one time, that is, only the gateway device and the network management device are maintained. There is no need to maintain the heartbeat between the network management device and each intranet device separately. Because the sending of heartbeat messages is relatively frequent, and the data volume of heartbeat messages is generally small, this kind of batch transmission of multiple internal The heartbeat message method of network equipment can minimize the number of heartbeat messages to be transmitted to avoid network congestion and save transmission resources as much as possible. At the same time, it can also reduce the processing load of network management equipment frequently processing heartbeat messages, thereby improving the processing performance of network management equipment .
  • the gateway device can uniformly report the network status of each intranet device to the network management device by uniformly maintaining the heartbeat, eliminating the need for the network management device to separately query the online status of each intranet device, which improves the processing performance of the network management device.
  • Step 408 The network management device sends a second management message to the gateway device, where the second management message carries the public network IP address of the gateway device and the first device identifier of the first intranet device.
  • the protocol conversion function converts the second management message, for example, into the third management message in the following text.
  • Step 409 The gateway device determines the first private network IP address corresponding to the first device identifier according to the correspondence between the device identifier of the internal network device and the corresponding private network IP address, and compares the second private network IP address with the first private network IP address.
  • the management message performs protocol conversion to obtain the third management message after conversion.
  • the device identifier carried in the third management message becomes the first device identifier
  • the third management message is a message conforming to the transmission protocol (such as the SNMP protocol) between the gateway device and the first intranet device.
  • Step 410 The gateway device sends the third management message obtained after the conversion to the first intranet device through the private network IP address.
  • Step 411 After receiving the third management message, the first intranet device can parse the third management message based on the local protocol stack, and then can perform management operations corresponding to the third management message, such as setting parameters And so on.
  • the network management device can manage the internal network device based on the second management message (the converted third management message), and the management process is the same as the network management device in step 305-step 305 in FIG. 3 above.
  • the process of the first management message to manage the gateway device is similar, which can be understood by reference.
  • Step 501 Receive a first management message sent by a network management device based on a predetermined data transmission protocol, where the destination IP address of the first management message is the public network IP address of the gateway device, and the first management message carries the destination device identifier.
  • the gateway device can receive the management message issued by the network management device, for example, the management message is called the first management message, and the first management message may be a management message for the gateway device itself , It may also be a management message for internal network equipment.
  • the first management message may be a management message for independent management of a single device, or it may be a management message for batch management of multiple devices.
  • Step 502 Switch to the protocol conversion and convergence processing working mode according to the detected network environment.
  • the gateway device may have a network environment detection function, and can automatically determine the network environment to which it belongs based on the protocol type of the received message. For example, when it is detected that the network management device uses the SNMP protocol to communicate with the switch, it is considered that the switch is in In a non-NAT network environment, set the module to the working mode of non-protocol conversion and aggregation processing. Otherwise, set the module to the working mode of protocol conversion and aggregation processing. In the working mode of protocol conversion and aggregation processing, the protocol conversion processing is supported. And message aggregation processing. In this way, the entire system has better versatility, and the gateway device can automatically recognize whether it is in a NAT network environment, and adjust the processing mode according to the network type, so that the switch can be simultaneously compatible with network management communications using different protocols.
  • Step 503 Determine whether the target device identifier is the device identifier of the gateway device itself.
  • the first management message may be a management message for the gateway device itself, or it may be a management message for other intranet devices. Therefore, the gateway device needs to be based on the management message carried in the first management message.
  • the destination device identifier determines whether it is a management message for itself.
  • Step 504 When the target device identifier is the device identifier of the gateway device itself, respond to the first management message to perform a management operation corresponding to the first management message.
  • the gateway device needs to respond to the first management message to perform the correspondence with the first management message.
  • Management operations such as completing the query parameters and setting parameters indicated by the network management equipment.
  • the operation response information can be fed back to the network management device to inform the network management device of its own completion status for various operations.
  • Step 505 When the target device identifier is not the device identifier of the gateway device itself, determine the first private network IP corresponding to the target device identifier according to the correspondence between the device identifier of the intranet device and the corresponding private network IP address address.
  • the corresponding relationship between the private network IP address of each intranet device under it and the corresponding device identification can be stored in the gateway device in advance.
  • the device identification of the intranet device is included in the first management message, it can be based on this
  • the corresponding relationship is used to determine which intranet device the first management message is for. For example, it is determined based on the correspondence relationship that the private network IP address corresponding to the target device identifier in the first management message is the first private network IP address, and the internal network device corresponding to the first private network IP address is, for example, the first internal network device .
  • the first private network IP address may include only one private network IP address, that is, the first management message is only for one internal network device, so that the independence of a single internal network device can be realized. Management control; or, the first private network IP address may only include multiple private network IP addresses, that is, the first management message can be directed to multiple internal network devices at the same time, so that batch management and control of multiple internal network devices can be realized. Improve management efficiency.
  • Step 506 According to the first private network IP address, the first management message is converted into a second management message conforming to a predetermined network management protocol, and the destination IP address of the second management message is the first private network IP address.
  • the gateway device can forward the message based on the protocol conversion function to convert it into a second management message that conforms to the protocol stack of the first intranet device to facilitate the first intranet
  • the device can correctly parse the second management message.
  • Step 507 Send the second management message to the first internal network device corresponding to the first private network IP address, so that the first internal network device performs the management operation corresponding to the second management message.
  • the first intranet device After receiving the second management message, the first intranet device parses the second management message based on its own protocol stack, and then can perform the management operation corresponding to the second management message to complete the network management device's access to the first management message. Management of internal network equipment.
  • the technical solutions provided by the embodiments of this application can solve the problem of monitoring and management of switches that use private network IP addresses for centralized networking by existing network managers, and realize the functions of protocol conversion and aggregation processing modules on existing networking equipment without additional Add NAT equipment to convert the private network IP address of the switch into a public network IP address.
  • the clock synchronization module necessary for the network performs protocol forwarding, data consolidation and distribution and unified processing functions for the data between the equipment management device and the switch, so that
  • the network management system can manage and present large-scale networking protocol forwarding processing modules and multiple switch devices at the same time, and can realize single processing and batch processing of switches (such as batch software upgrades, parameter settings and queries, etc.), making the entire system not only It can traverse the NAT network while reducing the network IP and bandwidth requirements, achieving the purpose of improving the performance of the entire network system and reducing the overall operating cost, and expanding the application scope of the entire system.
  • an embodiment of the present application provides a device management device, which can be applied to the gateway device in the foregoing method embodiment, and the device management device is, for example, the gateway device in the foregoing method embodiment, or It is the hardware structure, software module, or hardware structure plus software module in the gateway device.
  • the device management apparatus may be implemented by a chip system, which may be composed of a chip, or may include a chip and other discrete devices. As shown in FIG. 6a, the device management apparatus includes a receiving module 601, a determining module 602, a response module 603, and a sending module 604. among them:
  • the receiving module 601 is configured to receive a first management message sent by a network management device based on a predetermined data transmission protocol, where the destination IP address of the first management message is the public network IP address of the gateway device, and the first management message carries the destination device logo
  • the determining module 602 is used to determine whether the target device identifier is the device identifier of the gateway device itself;
  • the response module 603 is configured to respond to the first management message when the target device identifier is the device identifier of the gateway device itself, so as to perform a management operation corresponding to the first management message;
  • the response module 603 is also used to determine the first private network corresponding to the target device ID according to the correspondence between the device ID of the intranet device and the corresponding private network IP address when the target device ID is not the device ID of the gateway device itself.
  • Network IP address and according to the first private network IP address, the first management message is converted into a second management message conforming to the predetermined network management protocol, and the destination IP address of the second management message is the first private network IP address;
  • the sending module 604 is configured to send the second management message to the first intranet device corresponding to the first private network IP address, so that the first intranet device performs the management operation corresponding to the second management message.
  • the target device identifier includes the device identifiers of multiple intranet devices
  • the response module 603 is configured to:
  • the first management message is converted into a plurality of second management messages conforming to the predetermined network management protocol, wherein the destination IP address of each second management message Is a different first private network IP address;
  • Sending the second management message to the first intranet device corresponding to the first private network IP address includes:
  • Each second management message obtained by the conversion is sent to each intranet device corresponding to the first private network IP address carried in each second management message.
  • the device management apparatus in this embodiment of the present application further includes a registration module 605, configured to:
  • the receiving module 604 Before the receiving module 604 receives the first management message sent by the network management device based on the predetermined data transmission protocol, it sends a first registration request message to the network management device, where the first registration request message carries the public network IP address of the gateway device and the device identifier of the gateway device And receiving a first registration response message sent by the network management device, where the first registration response message is a feedback message generated by the network management device after successfully registering the gateway device according to the first registration request message.
  • the registration module 605 is also used to:
  • the receiving module 604 Before the receiving module 604 receives the first management message sent by the network management device based on the predetermined data transmission protocol, it receives the second registration request message sent by the first intranet device based on the predetermined network management protocol, where the second registration request message carries the first intranet The first device identifier of the device;
  • the device management apparatus in this embodiment of the present application further includes a status query module 606, configured to:
  • the network online status is marked for each intranet device; among them, the intranet device that sent the online feedback message is marked as online, and the intranet device that has not sent the online feedback message is marked as offline.
  • the device management apparatus in this embodiment of the present application further includes a heartbeat maintenance module 607 for:
  • the status query module 606 marks the network online status for each intranet device, it generates a heartbeat message.
  • the heartbeat message includes the device identification of the gateway device and the device identification of the intranet device that is currently online;
  • the response module 603 is also used to:
  • the protocol conversion and convergence processing working mode supports protocol conversion processing and message convergence processing.
  • the division of modules in the embodiments of this application is illustrative, and it is only a logical function division. In actual implementation, there may be other division methods.
  • the functional modules in the various embodiments of this application can be integrated into one process. In the device, it can also exist alone physically, or two or more modules can be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.
  • the embodiments of the present application provide a communication device, the communication device is, for example, a router, a switch, a gateway device, or the like.
  • the communication device includes at least one processor 701 and a memory 702 connected to the at least one processor.
  • the specific connection medium between the processor 701 and the memory 702 is not limited in the embodiment of the present application.
  • FIG. 7 In this example, the processor 701 and the memory 702 are connected through a bus 700 as an example.
  • the bus 700 is represented by a thick line in FIG. .
  • the bus 700 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only a thick line is used in FIG. 7 to represent it, but it does not mean that there is only one bus or one type of bus.
  • the communication device in the embodiment of the present application may further include a communication interface 703.
  • the communication interface 703 is, for example, a network port.
  • the computing device may transmit data through the communication interface 703, for example, receive data packets or messages sent by other communication devices, or , Can send data packets or messages to other communication devices.
  • the memory 702 stores instructions that can be executed by at least one processor 701, and the at least one processor 701 can execute the steps included in the aforementioned device management method by executing the instructions stored in the memory 702.
  • the processor 701 is the control center of the communication device. It can use various interfaces and lines to connect to various parts of the entire computing device. By running or executing instructions stored in the memory 702 and calling data stored in the memory 702, the computing device The various functions and processing data of the computer, so as to monitor the computing equipment as a whole.
  • the processor 701 may include one or more processing units, and the processor 701 may integrate an application processor and a modem processor, where the application processor mainly processes operating systems and application programs, and the modem processor Mainly deal with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 701.
  • the processor 701 and the memory 702 may be implemented on the same chip, and in some embodiments, they may also be implemented on separate chips.
  • the processor 701 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, Implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the device management method disclosed in combination with the embodiments of the present application may be directly embodied as executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory 702 as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules.
  • the memory 702 may include at least one type of storage medium, and the memory 702 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 702 in the embodiment of the present application may also be a circuit or any other device capable of realizing a storage function for storing program instructions and/or data.
  • the communication device also includes a basic input/output system (I/O system) 704 to help transfer information between various devices in the communication device, and a large-scale system for storing the operating system 705, application programs 706, and other program modules 707. Capacity storage device 708.
  • I/O system basic input/output system
  • the basic input/output system 704 includes a display 709 for displaying information and an input device 710 such as a mouse and a keyboard for the user to input information.
  • the display 709 and the input device 710 are both connected to the processor 701 through a basic input/output system 704 connected to the system bus 700.
  • the basic input/output system 704 may also include an input and output controller for receiving and processing input from multiple other devices such as a keyboard, a mouse, or an electronic stylus. Similarly, the input and output controller also provides output to a display screen, printer or other type of output device.
  • the mass storage device 708 is connected to the processor 701 through a mass storage controller (not shown) connected to the system bus 700.
  • the mass storage device 708 and its associated computer readable medium provide non-volatile storage for the server package. That is, the mass storage device 708 may include a computer-readable medium (not shown) such as a hard disk or a CD-ROM drive.
  • the communication device package may also be connected to a remote computer on the network through a network such as the Internet to run. That is, the communication device can be connected to the network 711 through the communication interface 703 connected to the system bus 700, or it can also be connected to other types of networks or remote computer systems (not shown) by using the communication interface 703.
  • the code corresponding to the device management method introduced in the foregoing embodiment can be solidified into the chip, so that the chip can execute the steps of the foregoing device management method during operation.
  • Designing and programming is a technique well known to those skilled in the art, and will not be repeated here.
  • the embodiments of the present application also provide a computer-readable storage medium, the computer-readable storage medium stores computer instructions, when the computer instructions run on the computer, the computer executes the device management method as described above. step.
  • the device management method provided in this application is applied to gateway devices, and reduces the workload of the network management device through the service sharing of the gateway device to the network management device, and improves the performance of the network system, and has strong industrial applicability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种设备管理方法、装置、通信设备及存储介质，属于通信技术领域，用于降低网管设备的工作负荷，提升网络系统性能。所述方法包括：接收网管设备发送的第一管理报文，第一管理报文的目的IP地址为网关设备的公网IP地址；确定第一管理报文携带的目的设备标识是否为网关设备自身的设备标识；若是，响应第一管理报文，以执行与第一管理报文对应的管理操作；若否，确定与目的设备标识对应的第一私网IP地址；并根据第一私网IP地址将第一管理报文转换为符合预定网络管理协议的第二管理报文；以及将第二管理报文发送给第一私网IP地址对应的第一内网设备，以使第一内网设备执行与第二管理报文对应的管理操作。

Description

设备管理方法、装置、通信设备及存储介质
本申请要求于2019年12月30日提交中国专利局、申请号为201911399631.4、发明名称为“设备管理方法、装置、通信设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种设备管理方法、装置、通信设备及存储介质。
背景技术
在现有的一些网络架构中需要采用集中组网的方式，例如在一些回传网络中需要用到该种组网方式。一般来说，处于节省空间和网际协议(Internet Protocol，IP)资源的考虑，通常一个回传站点只分配一个传输的监控IP给到集中组网的多台通信设备，以便网管对这些通信设备进行监控和操作维护。在这种组网应用中，要实现网管对该站点下其它通信设备的监控，目前常用的方法是在连接回传网络的通信设备上实现网络地址转换(Network Address Translation，NAT)功能或增加NAT设备，然后该站点下其它通信设备发往网管的数据包经过具有NAT功能的设备或NAT设备之后再发往网管，实现网管对采用私网IP地址的其它通信设备的监控。
然而，这种方法通常需要在网管上记录不同通信设备经过NAT之后的IP地址和用户数据报协议(User Datagram Protocol，UDP)端口，并且需要维护大量通信设备与网管之间的心跳报文以及处理每台通信设备的数据，同时要实现对集中组网中的多台通信设备进行处理，通常要额外增加NAT设备，这些存在的问题，都会从一定程度上加剧网管的工作负荷，从而影响系统性能。
发明内容
(一)要解决的技术问题
本申请要解决的技术问题是解决现有的网管的工作负荷大影响网络系统性能的问题。
(二)技术方案
为了解决上述技术问题，本申请实施例提供了一种设备管理方法、装置、通信设备及存储介质。
第一方面，提供一种设备管理方法，所述方法包括：
所述方法应用于网关设备，所述网关设备部署于网管设备和内网设备集群之间，所述网关设备与所述网管设备之间基于预定数据传输协议进行通信，所述网关设备与所述内网设备集群之间基于预定网络管理协议进行通信；所述方法包括：
接收所述网管设备基于所述预定数据传输协议发送的第一管理报文，其中，所述第一管理报文的目的IP地址为所述网关设备的公网IP地址，所述第一管理报文携带目的设备标识；
确定所述目的设备标识是否为所述网关设备自身的设备标识；
在所述目的设备标识为所述网关设备自身的设备标识时，响应所述第一管理报文，以执行与所述第一管理报文对应的管理操作；
在所述目的设备标识不为所述网关设备自身的设备标识时，根据内网设备的设备标识与对应私网IP地址之间的对应关系，确定与所述目的设备标识对应的第一私网IP地址；并根据所述第一私网IP地址将所述第一管理报文转换为符合所述预定网络管理协议的第二管理报文，所述第二管理报文的目的IP地址为所述第一私网IP地址；以及将所述第二管理报文发送给所述第一私网IP地址对应的第一内网设备，以使所述第一内网设备执行与所述第二管理报文对应的管理操作。
第二方面，提供一种设备管理装置，所述装置应用于网关设备中，所述网关设备部署于网管设备和内网设备集群之间，所述网关设备与所述网管设备之间基于预定数据传输协议进行通信，所述网关设备与所述内网设备集群之间基于预定网络管理协议进行通信；所述装置包括：
接收模块，用于接收所述网管设备基于所述预定数据传输协议发送的第一管理报文，其中，所述第一管理报文的目的IP地址为所述网关设备的公网IP地址，所述第一管理报文携带目的设备标识；
确定模块，用于确定所述目的设备标识是否为所述网关设备自身的设备标识；
响应模块，用于在所述目的设备标识为所述网关设备自身的设备标识时，响应所述第一管理报文，以执行与所述第一管理报文对应的管理操作；
所述响应模块，还用于在所述目的设备标识不为所述网关设备自身的设备标识时，根据内网设备的设备标识与对应私网IP地址之间的对应关系，确定与所述目的设备标识对应的第一私网IP地址；并根据所述第一私网IP地址将所述第一管理报文转换为符合所述预定网络管理协议的第二管理报文，所述第二管理报文的目的IP地址为所述第一私网IP地址；
发送模块，用于将所述第二管理报文发送给所述第一私网IP地址对应的第一内网设备，以使所述第一内网设备执行与所述第二管理报文对应的管理操作。
第三方面，提供一种通信设备，所述通信设备包括：
存储器，用于存储程序指令；
处理器，用于调用所述存储器中存储的程序指令，按照获得的程序指令执行第一方面中任一所述的设备管理方法包括的步骤。
第四方面，提供一种计算可读存储介质，所述计算可读存储介质存储有计算机可执行指令，所述计算机可执行指令用于使计算机执行第一方面中任一所述的设备管理方法包括的步骤。
第五方面，提供一种包含指令的计算机程序产品，当所述计算机程序产品在计算机上运行时，使得计算机执行上述各种可能的实现方式中所描述的设备管理方法。
(三)有益效果
本申请实施例提供的上述技术方案与现有技术相比具有如下优点：
在本申请实施例中，网关设备由于集成了协议转换和消息汇聚处理的能力，可以对多个采用私网IP地址的内网设备(例如内网交换机)进行监控、管理和维护，具体来说是将网管设备的管理指令进行协议转换之后再下发给各个内网设备，可以对各个内网设备进行单台管理，也可以对多个内网设备的参数设置、参数查询、软件升级等进行批量处理，这样，基于网关设备的协议换换能力，可以在较大程度上减少网管设备对各个内网设备的管理负荷，通过网关设备对网管设备的业务分担，可以降低网管设备的处理负荷，进而提高网管设备的运行性能，同时可以实现对组网应用下的多个基于内网IP地址通信的内网设备进行管理，可以降低总体运营成本，从而拓展整个系统的应用范围，提升系统的运行性能。
附图说明
图1为本申请实施例提供的应用场景的示意图；
图2为本申请实施例提供的设备管理系统的架构示意图；
图3为本申请实施例提供的设备管理方法的流程图；
图4为本申请实施例提供的设备管理方法的另一流程图；
图5为本申请实施例提供的设备管理方法的另一流程图；
图6a为本申请实施例提供的设备管理装置的结构框图；
图6b为本申请实施例提供的设备管理装置的另一结构框图；
图7为本申请实施例提供的通信设备的结构示意图。
具体实施方式
如前所述的，在现有的一些网络架构中需要采用集中组网的方式，例如，随着4G小基站商用进度的加快，很多4G小基站都要采用1588v2协议同步。然而当前很多回传网络并不支持1588v2协议，因此这些回传网络需要采用集中组网的 方式，即在同一回传站点会用到很多交换机和至少一个1588同步源，然后1588同步源数据通过集中组网交换机网络传递给4G小基站。但是运营商出于节省空间和IP资源的考虑，通常一个回传站点只分配一个传输的监控IP给到集中组网的多台交换机，以便网管对这些交换机进行监控和操作维护。在这种组网应用中，要实现网管对该站点下其它交换机的监控，目前常用的方法是在连接回传网络的交换机设备上实现NAT功能或增加NAT设备，然后该站点下其它交换机发往网管的数据包经过具有NAT功能的交换机或NAT设备之后再发往网管，实现网管对采用私网IP地址的其他交换机的监控。这种方法通常需要在网管上记录不同交换机经过NAT之后的IP地址和UDP端口，并且需要维护大量交换机与网管之间的心跳报文以及处理每台交换机的数据，同时要实现对集中组网中的多台交换机进行处理，通常要额外增加NAT设备，这些存在的问题，都会从一定程度上加剧网管的工作负荷，从而影响性能，同时增加运营商的设备成本。
鉴于此，本申请实施例提供一种融合协议转换的设备管理方案，在该方案中，采用了协议转换和汇聚处理模块，该协议转换和汇聚处理模块可以集中部署在交换机中，或者可以独立部署作为一个单独的网络设备存在，该协议转换和汇聚处理模块支持协议转换功能和消息汇聚、批量处理功能。用于解决现有网管设备对采用私网IP地址进行集中组网的交换机的监控管理问题，在现有组网设备上实现协议转换及汇聚处理模块的功能，无需额外增加NAT设备将交换机的私网IP地址转换成公网IP地址，同时，在组网所必须时钟同步模块对设备管理装置与交换机之间的数据进行协议转发、数据合并分发和统一处理功能，使得在网管系统可以同时管理和呈现规模组网的协议转发处理模块和多台交换机设备，并且可以实现对交换机单台处理和批量处理(比如批量软件升级、参数设置和查询等)，使得整个系统不仅能够穿越NAT网络，同时减少对网络IP和带宽要求，达到提高整个网络系统的性能和降低总体运营成本的目的，拓展了整个系统的应用范围。
请参见图1所示，图2为本申请实施例的技术方案能够适用的一种应用场景，在该应用场景中，包括网管设备、两个网关设备(即网关设备1、网关设备2)和多个内网设备(即内网设备1、内网设备2、内网设备3、内网设备4、内网设备5、内网设备6)。其中，网关设备1、网关设备2与网管设备之间基于公网传输，即，网关设备1、网关设备2在与网管设备进行通信时是基于预先分配的公网IP地址进行通信的。网关设备1、网关设备2下均配置有多个内网设备，可见网关设备1下配置有内网设备1、内网设备2、内网设备3，网关设备2下配置有内网设备4、内网设备5、内网设备6，各个网关设备和其配置的内网设备之间基于私网IP地址进行通信。在一种可能的传输场景中，网关设备1、网关设备2与网管设备之间基于TR069(Technical Report 069，TR069)协议或者其它数据传输协议进行通信， 网关设备1、网关设备2与各自下面的内网设备之间基于简单网络管理协议(Simple Network Management Protocol，SNMP)协议进行通信，也就是说，内网和公网之间的传输协议不同。
在本申请实施例中，如前所述的，提出了协议转换和汇聚处理模块，该模块部署在图1中的网关设备1、网关设备2中。当协议转换和汇聚处理模块集中部署在交换机中时，此时的网关设备1、网关设备2可以是交换机设备，当协议转换和汇聚处理模块独立进行部署时，网关设备1、网关设备2可以是其它类型的设备，例如是支持协议转换和消息汇聚处理的其它设备，本申请实施例不做限制。在该应用场景中，网管设备发送给各个内网设备的消息可以经由网关设备通过协议转换之后转发，同理地，各个内网设备发送给网管设备的消息也是经由网关设备通过协议转换后再转发给网管设备。
也就是说，网关设备由于集成了协议转换和消息汇聚处理的能力，可以对多个采用私网IP地址的内网设备(例如内网交换机)进行监控、管理和维护，具体来说是将网管设备的管理指令进行协议转换之后再下发给各个内网设备，可以对各个设备进行单台管理，也可以对多个内网设备的参数设置、参数查询、软件升级等进行批量处理，另外还可以通过网管设备集中维护所有内网设备与网管设备之间的心跳，这样，基于网关设备的协议转换能力，可以分担网管设备对内网设备集群的管理业务，这样可以在较大程度上减少网管设备对各个内网设备的管理负荷，通过网关设备对网管设备的业务分担，可以提高网管设备的运行性能，同时可以实现对组网应用下的多个基于私网IP地址通信的内网设备进行管理，可以降低总体运营成本，从而拓展整个系统的应用范围，提升系统的运行性能。
上述的各个设备可以具有唯一的设备标识(例如设备的序列号)，各个设备具有的唯一设备标识是用于区分各个设备的。上述的网管设备可以是计算机或者服务器，例如可以是个人计算机、大中型计算机、计算机集群等；网关设备1、2可以是交换机或者是其它支持协议转换的通信设备；内网设备1-6例如是交换机、路由器，等等，本申请实施例不做限制。
为进一步说明本申请实施例提供的技术方案，下面结合附图以及具体实施方式对此进行详细的说明。虽然本申请实施例提供了如下述实施例或附图所示的方法操作步骤，但基于常规或者无需创造性的劳动在所述方法中可以包括更多或者更少的操作步骤。在逻辑上不存在必要因果关系的步骤中，这些步骤的执行顺序不限于本申请实施例提供的执行顺序。
首先请参见2所示的，图2为本申请实施例提供的一种设备管理系统，在该设备管理系统中包括网管设备、网关设备和由多个内网设备组成的内网设备集群，其中，网关设备和网管设备之间基于预定数据传输协议进行通信，该预定数据传 输协议例如是TR069协议，以及，网关设备与内网设备集群之间基于预定网络管理协议进行通信，该预定网络管理协议例如是SNMP协议，也就是说，网关设备与网管设备和内网设备集群之间的通信协议不同，所以，为了实现网管设备和内网设备集群中的内网设备之间的数据交互，本申请实施例中的网关设备支持协议转换，以通过协议转换功能支持网管设备和内网设备之间的数据交互。另外，网关设备和网管设备之间是基于公网IP地址进行通信，以及网关设备和内网设备之间是基于私网IP地址进行通信，所以通过网关设备的协议转换功能，可以实现采用公网IP地址的设备与采用私网IP地址的设备之间的通信，从而扩展系统的应用。
基于图2所介绍的设备管理系统，本申请实施例提供一种设备管理方法，该设备管理方法包括网管设备与网关设备之间的通信方法、网关设备与内网设备之间的通信方法、网管设备与内网设备之间的通信方法这三部分，为便于理解，以下分别进行说明。
请参见图3所示的，图3所示的是本申请实施例中的设备管理方法中的网管设备与网关设备之间的通信流程。图3所示的流程描述如下。
步骤301：网关设备向网管设备发送第一注册请求消息。
在网关设备与网管设备进行通信之前，网关设备需要向网管设备进行注册，注册可以认为是向网管设备进行认证权限。在进行注册时，网关设备可以向网管设备发送注册请求，例如发送第一注册请求消息，该第一注册请求消息中携带有网关设备的公网IP地址和网关设备的设备标识，网关设备的设备标识是用于唯一标识该网关设备的标识，例如设备序列号等。
步骤302：网管设备在接收到网关设备发送的第一注册请求消息之后，可以根据第一注册请求消息，将网关设备的公网IP地址和设备标识进行登记，以完成对网关设备的注册。
步骤303：网管设备向网关设备发送注册响应消息。
网管设备在对网关设备进行注册认证的过程中，可以先进行权限鉴定，在确定网关设备具备注册权限时则可以进行注册，即注册成功，在确定网关设备不具备注册权限时则可以不进行注册，即注册失败。在成功完成对网关设备的注册之后，网管设备可以对网关设备进行注册响应，例如生成对应的第一注册响应消息，第一注册响应消息是网管设备根据第一注册请求消息对网关设备注册成功后生成的反馈消息，并将该第一注册响应消息反馈给网关设备，以告知网关设备其注册成功。类似的，在注册失败时，网管设备也可以对网关设备进行注册失败的注册反馈，以便于网关设备及时知晓其未成功注册。
步骤304：网关设备向网管设备发送心跳消息。
网关设备可以定时或者周期性地向网管设备发送心跳消息，该心跳消息中携 带网关设备的设备标识，通过心跳消息维护网关设备和网管设备之间的通信在线状态。
步骤305：网管设备向网关设备发送第一管理报文，该第一管理报文携带网关设备的公网IP地址和设备标识。
进一步地，在网关设备注册成功之后，网管设备可以对网关设备进行管理，具体地，网管设备可以通过向网关设备发送管理报文的方式对网关设备进行设备管理。例如，网管设备可以向网关设备发送第一管理报文，该第一管理报文携带网关设备的公网IP地址的和网关设备的设备标识，如前所述的，网关设备和网管设备基于公网通信，所以第一管理报文的目的IP地址即是网关设备的公网IP地址，通过第一管理报文，网管设备可以查询、设置网关设备中的相关参数，或者通知网关设备的某些功能进行升级，等等。
步骤306：网关设备在接收第一管理报文之后，即响应第一管理报文，以执行对应的管理操作。
网关设备在接收第一管理报文之后，例如可以设置网关设备中的某些参数，或者查询网关设备中的某些参数之后反馈给网管设备，或者进行某些功能升级，等等。也就是说，网管设备可以对网关设备进行管理。
请参见图4所示的，图4所示的是本申请实施例中的设备管理方法中的网管设备、网关设备、内网设备(例如第一内网设备)之间的通信流程。图4所示的流程描述如下。
步骤401：第一内网设备向网关设备发送第二注册请求消息，该第二注册请求消息中携带第一内网设备的设备标识，例如是第一设备标识。
在本申请实施例中，由于第一内网设备与网管设备之间存在传输协议的阻碍，所以第一内网设备与网管设备之间的数据交互可以通过网关设备进行协议转换之后再中转换发，而第一内网设备与网管设备之间进行数据交互的前提，也是需要向网管设备进行注册。
具体地，由于第一内网设备和网管设备之间是通过网关设备进行中转通信，所以第一内网设备在向网管设备进行注册时，可以先向网关设备发送携带第一内网设备的第一设备标识的第二注册请求消息，以通过第二注册请求消息经网关设备中转后向网管设备发起注册请求。
在具体实施过程中，若有多个内网设备均需要向网管设备发起注册，那么这些需要注册的内网设备均可以向网关设备发送对应的注册请求消息，也就是说，第一内网设备可以只包括一个内网设备，也可以同时包括多个内网设备，当第一内网设备包括多个内网设备时，第一设备标识即是该多个内网设备分别对应的设备标识。
步骤402：网关设备进行协议转换，将第二注册请求消息转换为符合网管设备和网关设备之间的通信协议(例如前述的TR069协议)的注册请求消息，转换后的注册请求消息携带网关设备的公网IP地址和第一设备标识。
也就是说，第一内网设备进行注册的方式，是通过网关设备的协议转换能力进行注册转发，即，网关设备会先将第一内网设备发送的第二注册请求消息进行协议转换，并且由于是需要对第一内网设备进行注册，所以转换后的注册请求消息中携带了第一内网设备对应的第一设备标识。
步骤403：网关设备将转换后的注册请求消息发送给网管设备，以请求为第一内网设备进行注册。
在具体实施过程中，如前所述的，多个内网设备可能均需要向网管设备请求注册，在一种实施中，网关设备可以将多个内网设备各自发送的注册请求消息统一进行协议转换，以得到一条转换后的注册请求消息，例如将该一条转换后的注册请求消息称作批量注册请求消息，该批量注册请求消息携带了多个内网设备对应的多个设备标识，即对应前述的第一设备标识包括多个设备标识的情形，以此可以对多个内网设备进行批量注册，这样可以减少网关设备与网管设备之间传输消息(例如注册请求消息)的数量，同时可以减少网管设备进行注册之后反馈的注册响应消息，以提升网络性能。
步骤404：网管设备在接收到转换后的注册请求消息后，根据转换后的注册请求消息，登记网关设备的公网IP地址和第一内网设备的第一设备标识，以完成对第一内网设备的注册。
前述的步骤302-步骤303描述的是网管设备对网关设备的注册和注册响应流程，步骤404这里的网管设备对第一内网设备的注册和注册响应过程可以参见前述的步骤302-步骤303的实施，此处就不再重复介绍了。
步骤405：网关设备向第一内网设备发送在线查询消息。
步骤406：第一内网设备向网关设备发送在线反馈消息。
其中，在线查询消息是用于请求第一内网设备的在线状态的查询消息，当第一内网设备在线时，则需要向网关设备发送在线反馈消息，以便于网关设备知晓其在线；若第一内网设备已经离线，那么则没有能力再返回在线反馈消息，所以若没有收到某个内网设备的在线反馈消息，则可以认为该内网设备已经离线，即已经不处于通信状态。通过在线查询消息，网关设备可以动态地标注每个内网设备的在网状态。
步骤407：网关设备向网管设备发送心跳消息，该心跳消息携带网关设备的设备标识和第一内网设备的第一设备标识。
心跳消息中包括的设备标识，可以用于指示哪些设备当前处于在线状态，例 如心跳消息中包括的设备标识1、设备标识2和设备标识3，即可表明与设备标识1、设备标识2和设备标识3分别对应的3个设备当前处于在线状态，即第一设备标识可以是指多个在线状态的内网设备对应的多个设备标识。在具体实施过程中，网关设备可以将自身的心跳消息和内网设备的心跳消息一起发送，那么该心跳消息中可以同时携带网关设备的设备标识和在线的内网设备的设备标识，或者在另外一种实施方式中，网关设备也可以将自身的心跳消息和所有在线的内网设备的心跳消息单独发送。
在实际中，网关设备可以查询每个内网设备的在线状态，所以可以批量地将各个内网设备的心跳消息合成为一个心跳消息一次性发送给网管设备，即只维护网关设备与网管设备之间的心跳，而不用再单独维护网管设备与各个内网设备之间的心跳，因为心跳消息的发送是比较频繁的，且心跳消息的数据量一般很小，所以通过此种批量传输多个内网设备的心跳消息的方式，可以尽量地减少心跳消息的传输数量，以尽量的避免网络拥塞，节约传输资源，同时也可以减少网管设备频繁处理心跳消息的处理负荷，进而提高网管设备的处理性能。
此外，通过统一维护心跳的方式，网关设备可以将各个内网设备的在网状态统一上报给网管设备，无需网管设备分别查询各个内网设备的在线状态，提升了网管设备的处理性能。
步骤408：网管设备向网关设备发送第二管理报文，该第二管理报文携带网关设备的公网IP地址和第一内网设备的第一设备标识。
由于第二管理报文中携带的设备标识是第一内网设备的，即表明该第二管理报文是需要发送给第一内网设备的管理报文，此时，网关设备则需要利用到协议转换功能将第二管理报文进行转换，例如转换成了后文中的第三管理报文。
步骤409：网关设备根据内网设备的设备标识与对应私网IP地址之间的对应关系，确定与第一设备标识对应的第一私网IP地址，并根据第一私网IP地址对第二管理报文进行协议转换，以得到转换后的第三管理报文。
其中，第三管理报文携带的设备标识变成了第一设备标识，并且第三管理报文是符合网关设备与第一内网设备之间的传输协议(例如SNMP协议)的报文。
步骤410：网关设备将转换后得到的第三管理报文通过私网IP地址发送给第一内网设备。
步骤411：第一内网设备在接收到第三管理报文之后，即可以基于本地的协议栈对第三管理报文进行解析，进而可以执行第三管理报文对应的管理操作，例如设置参数等操作。
也就是说，网管设备可以基于第二管理报文(转换后的第三管理报文)对内网设备进行管理，该管理过程中与前述图3中的步骤305-步骤305中的网管设备 通过第一管理报文对网关设备进行管理的过程是类似的，可以参照理解。
以上是从两个设备或者三个设备的交互角度对本申请实施例中的技术方案进行了整体上的描述，以下再结合图5，从网关设备的角度对本申请实施例中的设备管理方法进行的描述。图5所示的流程描述如下。
步骤501：接收网管设备基于预定数据传输协议发送的第一管理报文，该第一管理报文的目的IP地址为网关设备的公网IP地址，第一管理报文携带目的设备标识。
在完成注册之后，网关设备可以接收到网管设备下发的管理报文，例如将该管理报文称作第一管理报文，该第一管理报文有可能是针对网关设备自身的管理报文，也有可能是针对内网设备的管理报文。此外，该第一管理报文有可能是针对单个设备独立管理的管理报文，也有可能是针对多个设备进行批量管理的管理报文。
步骤502：根据检测的网络环境去切换为协议转换及汇聚处理工作模式。
在本申请实施例中，网关设备可以具备网络环境检测功能，能够根据接收报文的协议类型，自动判断所属的网络环境，例如，当检测到网管设备采用SNMP协议与交换机通信，则认为交换机处于非NAT的网络环境，则将模块置为非协议转换及汇聚处理的工作模式，否则将模块置为协议转换及汇聚处理的工作模式，在协议转换及汇聚处理的工作模式下，支持协议转换处理以及消息汇聚处理。这样，使得整个系统具有更好的通用性，网关设备能够自动识别自身是否处于NAT网络环境下，并根据网络类型调整处理模式，使得交换机能够同时兼容与采用不同协议的网管通信。
步骤503：确定目的设备标识是否为网关设备自身的设备标识。
如前所述的，第一管理报文有可能是针对网关设备自身的管理报文，也有可能是针对其它内网设备的管理报文，所以网关设备需要先根据第一管理报文中携带的目的设备标识确定是否是针对自身的管理报文。
步骤504：在目的设备标识为述网关设备自身的设备标识时，响应第一管理报文，以执行与第一管理报文对应的管理操作。
若第一管理报文是针对自身的，例如是仅针对自身或者是同时针对自身和其它内网设备的，那么网关设备需要对该响应第一管理报文，以执行与第一管理报文对应的管理操作，例如完成网管设备指示的查询参数、设置参数等操作。在完成相应操作之后，可以再向网管设备反馈操作响应信息，以告知网管设备自身对于各种操作的完成状态。
步骤505：在目的设备标识不为所述网关设备自身的设备标识时，根据内网设备的设备标识与对应私网IP地址之间的对应关系，确定与目的设备标识对应的第 一私网IP地址。
可以预先在网关设备中存储其下的各个内网设备的私网IP地址与对应设备标识之间的对应关系，在第一管理报文中包括有内网设备的设备标识时，则可以基于该对应关系来确定第一管理报文到底是针对哪个内网设备的。例如，基于该对应关系确定第一管理报文中的目的设备标识对应的私网IP地址是第一私网IP地址，而第一私网IP地址对应的内网设备例如是第一内网设备。
需要说明的是，在具体实施过程中，第一私网IP地址可以仅包括一个私网IP地址，即第一管理报文只针对了一个内网设备，这样可以实现对单个内网设备的独立管理控制；或者，第一私网IP地址可以仅包括多个私网IP地址，即第一管理报文可以同时针对多个内网设备，这样可以实现对多个内网设备的批量管理控制，提升管理效率。
步骤506：根据第一私网IP地址将第一管理报文转换为符合预定网络管理协议的第二管理报文，该第二管理报文的目的IP地址为第一私网IP地址。
在确定了第一私网IP地址之后，网关设备即可以基于协议转换功能实现报文的转发，以转换为符合第一内网设备的协议栈的第二管理报文，以便于第一内网设备能够正确解析第二管理报文。
步骤507：将第二管理报文发送给第一私网IP地址对应的第一内网设备，以使第一内网设备执行与第二管理报文对应的管理操作。
第一内网设备在接收到第二管理报文之后，基于自身的协议栈对第二管理报文进行解析，进而可以执行与第二管理报文对应的管理操作，以完成网管设备对第一内网设备的管理。
本申请实施例提供的技术方案，可以解决现有网管对采用私网IP地址进行集中组网的交换机的监控管理问题，在现有组网设备上实现协议转换及汇聚处理模块的功能，无需额外增加NAT设备将交换机的私网IP地址转换成公网IP地址，同时，在组网所必须时钟同步模块对设备管理装置与交换机之间的数据进行协议转发、数据合并分发和统一处理功能，使得在网管系统可以同时管理和呈现规模组网的协议转发处理模块和多台交换机设备，并且可以实现对交换机单台处理和批量处理(比如批量软件升级、参数设置和查询等)，使得整个系统不仅能够穿越NAT网络，同时减少对网络IP和带宽要求，达到提高整个网络系统的性能和降低总体运营成本的目的，拓展了整个系统的应用范围。
基于同一发明构思，本申请实施例提供了一种设备管理装置，该设备管理装置可以应用于前述方法实施例中的网关设备中，该设备管理装置例如是前述方法实施例中的网关设备，或者是网关设备中的硬件硬件结构、软件模块、或硬件结构加软件模块。该设备管理装置可以由芯片系统实现，芯片系统可以由芯片构成， 也可以包含芯片和其他分立器件。请参见图6a所示，该设备管理装置包括接收模块601、确定模块602、响应模块603和发送模块604。其中：
接收模块601，用于接收网管设备基于预定数据传输协议发送的第一管理报文，其中，第一管理报文的目的IP地址为网关设备的公网IP地址，第一管理报文携带目的设备标识；
确定模块602，用于确定目的设备标识是否为网关设备自身的设备标识；
响应模块603，用于在目的设备标识为网关设备自身的设备标识时，响应第一管理报文，以执行与第一管理报文对应的管理操作；
响应模块603，还用于在目的设备标识不为网关设备自身的设备标识时，根据内网设备的设备标识与对应私网IP地址之间的对应关系，确定与目的设备标识对应的第一私网IP地址；并根据第一私网IP地址将第一管理报文转换为符合预定网络管理协议的第二管理报文，第二管理报文的目的IP地址为第一私网IP地址；
发送模块604，用于将第二管理报文发送给第一私网IP地址对应的第一内网设备，以使第一内网设备执行与第二管理报文对应的管理操作。
在一种可能的实施方式中，目的设备标识包括多个内网设备的设备标识，响应模块603用于：
根据每个内网设备对应的第一私网IP地址，将第一管理报文分别转换为符合预定网络管理协议的多个第二管理报文，其中，各个第二管理报文的目的IP地址为不同的第一私网IP地址；
将第二管理报文发送给第一私网IP地址对应的第一内网设备，包括：
将转换得到的各个第二管理报文，发送给各个第二管理报文携带的第一私网IP地址对应的各个内网设备。
在一种可能的实施方式中，请参见图6b所示，本申请实施例中的设备管理装置还包括注册模块605，用于：
在接收模块604接收网管设备基于预定数据传输协议发送的第一管理报文之前，向网管设备发送第一注册请求消息，第一注册请求消息携带网关设备的公网IP地址和网关设备的设备标识；并接收网管设备发送的第一注册响应消息，其中，第一注册响应消息是网管设备根据第一注册请求消息对网关设备注册成功后生成的反馈消息。
在一种可能的实施方式中，注册模块605还用于：
在接收模块604接收网管设备基于预定数据传输协议发送的第一管理报文之前，接收第一内网设备基于预定网络管理协议发送的第二注册请求消息，第二注册请求消息携带第一内网设备的第一设备标识；
根据预定数据传输协议对第二注册请求消息进行协议转换，以得到符合预定 数据传输协议的第三注册请求消息，第三注册请求消息携带网关设备的公网IP地址和第一设备标识；
向网管设备发送第三注册请求消息；
接收网管设备发送的第二注册响应消息，其中，第二注册响应消息是网管设备根据第三注册请求消息对第一内网设备注册成功后生成的反馈消息。
在一种可能的实施方式中，请参见图6b所示，本申请实施例中的设备管理装置还包括状态查询模块606，用于：
向内网设备集群中的各个内网设备发送在线查询消息；
接收在线反馈消息；
根据接收的在线反馈消息，为各个内网设备标记网络在线状态；其中，将发送在线反馈消息的内网设备标记为在线状态，以及将未发送在线反馈消息的内网设备标记为离线状态。
在一种可能的实施方式中，请参见图6b所示，本申请实施例中的设备管理装置还包括心跳维护模块607，用于：
在状态查询模块606为各个内网设备标记网络在线状态之后，生成心跳消息，心跳消息包括网关设备的设备标识和当前处于在线状态的内网设备的设备标识；
向网管设备发送心跳消息。
在一种可能的实施方式中，响应模块603还用于：
检测网关设备当前所处的网络环境；
若当前所处的网络环境为预定网络环境，则切换为协议转换及汇聚处理工作模式，其中，协议转换及汇聚处理工作模式支持协议转换处理以及消息汇聚处理。
前述的设备管理方法的实施例涉及的各步骤的所有相关内容均可援引到本申请施例中的设备管理装置所对应的功能模块的功能描述，在此不再赘述。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
基于同一发明构思，本申请实施例提供一种通信设备，该通信设备例如是路由器、交换机、网关设备等设备。请参见图7所示，该通信设备包括至少一个处理器701，以及与至少一个处理器连接的存储器702，本申请实施例中不限定处理器701与存储器702之间的具体连接介质，图7中是以处理器701和存储器702之间通过总线700连接为例，总线700在图7中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线700可以分为地址总线、数 据总线、控制总线等，为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例中的通信设备还可以包括通信接口703，该通信接口703例如是网口，计算设备可以通过该通信接口703传输数据，例如接收其它通信设备发送过来的数据包或者报文，或者，可以向其它通信设备发送数据包或报文。
在本申请实施例中，存储器702存储有可被至少一个处理器701执行的指令，至少一个处理器701通过执行存储器702存储的指令，可以执行前述的设备管理方法中所包括的步骤。
其中，处理器701是通信设备的控制中心，可以利用各种接口和线路连接整个计算设备的各个部分，通过运行或执行存储在存储器702内的指令以及调用存储在存储器702内的数据，计算设备的各种功能和处理数据，从而对计算设备进行整体监控。可选的，处理器701可包括一个或多个处理单元，处理器701可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器701中。在一些实施例中，处理器701和存储器702可以在同一芯片上实现，在一些实施例中，它们也可以在独立的芯片上分别实现。
处理器701可以是通用处理器，例如中央处理器(CPU)、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的设备管理方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
存储器702作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块。存储器702可以包括至少一种类型的存储介质，存储器702是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器702还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
进一步地，该通信设备还包括帮助通信设备内的各个器件之间传输信息的基本输入/输出系统(I/O系统)704、用于存储操作系统705、应用程序706和其他程序模块707的大容量存储设备708。
基本输入/输出系统704包括有用于显示信息的显示器709和用于用户输入信息的诸如鼠标、键盘之类的输入设备710。其中显示器709和输入设备710都通过连接到系统总线700的基本输入/输出系统704连接到处理器701。所述基本输入/ 输出系统704还可以包括输入输出控制器以用于接收和处理来自键盘、鼠标、或电子触控笔等多个其他设备的输入。类似地，输入输出控制器还提供输出到显示屏、打印机或其他类型的输出设备。
所述大容量存储设备708通过连接到系统总线700的大容量存储控制器(未示出)连接到处理器701。所述大容量存储设备708及其相关联的计算机可读介质为该服务器包提供非易失性存储。也就是说，大容量存储设备708可以包括诸如硬盘或者CD-ROM驱动器之类的计算机可读介质(未示出)。
根据本申请的各种实施例，该通信设备包还可以通过诸如因特网等网络连接到网络上的远程计算机运行。也即该通信设备可以通过连接在所述系统总线700上的通信接口703连接到网络711，或者说，也可以使用通信接口703来连接到其他类型的网络或远程计算机系统(未示出)。
通过对处理器701进行设计编程，可以将前述实施例中介绍的设备管理方法所对应的代码固化到芯片内，从而使芯片在运行时能够执行前述的设备管理方法的步骤，如何对处理器701进行设计编程为本领域技术人员所公知的技术，这里不再赘述。
基于同一发明构思，本申请实施例还提供一种计算可读存储介质，该计算可读存储介质存储有计算机指令，当该计算机指令在计算机上运行时，使得计算机执行如前述的设备管理方法的步骤。
工业实用性
本申请提供的设备管理方法，应用于网关设备，通过网关设备对网管设备的业务分担来降低网管设备的工作负荷，提升网络系统性能，具有很强的工业实用性。

Claims (10)

  1. 一种设备管理方法，其特征在于，所述方法应用于网关设备，所述网关设备部署于网管设备和内网设备集群之间，所述网关设备与所述网管设备之间基于预定数据传输协议进行通信，所述网关设备与所述内网设备集群之间基于预定网络管理协议进行通信；所述方法包括：
    接收所述网管设备基于所述预定数据传输协议发送的第一管理报文，其中，所述第一管理报文的目的网际协议IP地址为所述网关设备的公网IP地址，所述第一管理报文携带目的设备标识；
    确定所述目的设备标识是否为所述网关设备自身的设备标识；
    在所述目的设备标识为所述网关设备自身的设备标识时，响应所述第一管理报文，以执行与所述第一管理报文对应的管理操作；
    在所述目的设备标识不为所述网关设备自身的设备标识时，根据内网设备的设备标识与对应私网IP地址之间的对应关系，确定与所述目的设备标识对应的第一私网IP地址；并根据所述第一私网IP地址将所述第一管理报文转换为符合所述预定网络管理协议的第二管理报文，所述第二管理报文的目的IP地址为所述第一私网IP地址；以及将所述第二管理报文发送给所述第一私网IP地址对应的第一内网设备，以使所述第一内网设备执行与所述第二管理报文对应的管理操作。
  2. 根据权利要求1所述的设备管理方法，其特征在于，所述目的设备标识包括多个内网设备的设备标识，根据所述第一私网IP地址将所述第一管理报文转换为符合所述预定网络管理协议的第二管理报文，包括：
    根据每个内网设备对应的第一私网IP地址，将所述第一管理报文分别转换为符合所述预定网络管理协议的多个第二管理报文，其中，各个第二管理报文的目的IP地址为不同的第一私网IP地址；
    将所述第二管理报文发送给所述第一私网IP地址对应的第一内网设备，包括：
    将转换得到的各个第二管理报文，发送给各个第二管理报文携带的第一私网IP地址对应的各个内网设备。
  3. 根据权利要求1所述的设备管理方法，其特征在于，在接收所述网管设备基于所述预定数据传输协议发送的第一管理报文之前，所述方法还包括：
    向所述网管设备发送第一注册请求消息，所述第一注册请求消息携带所述网关设备的公网IP地址和所述网关设备的设备标识；
    接收所述网管设备发送的第一注册响应消息，其中，所述第一注册响应消息是所述网管设备根据所述第一注册请求消息对所述网关设备注册成功后生成的反馈消息。
  4. 根据权利要求1所述的设备管理方法，其特征在于，在接收所述网管设备基于所述预定数据传输协议发送的第一管理报文之前，所述方法还包括：
    接收所述第一内网设备基于所述预定网络管理协议发送的第二注册请求消息，所述第二注册请求消息携带所述第一内网设备的第一设备标识；
    根据所述预定数据传输协议对所述第二注册请求消息进行协议转换，以得到符合所述预定数据传输协议的第三注册请求消息，所述第三注册请求消息携带所述网关设备的公网IP地址和所述第一设备标识；
    向所述网管设备发送第三注册请求消息；
    接收所述网管设备发送的第二注册响应消息，其中，所述第二注册响应消息是所述网管设备根据所述第三注册请求消息对所述第一内网设备注册成功后生成的反馈消息。
  5. 根据权利要求1所述的设备管理方法，其特征在于，所述方法还包括：
    向所述内网设备集群中的各个内网设备发送在线查询消息；
    接收在线反馈消息；
    根据接收的在线反馈消息，为各个内网设备标记网络在线状态；其中，将发送在线反馈消息的内网设备标记为在线状态，以及将未发送在线反馈消息的内网设备标记为离线状态。
  6. 根据权利要求5所述的设备管理方法，其特征在于，在为各个内网设备标记网络在线状态之后，所述方法还包括：
    生成心跳消息，所述心跳消息包括所述网关设备的设备标识和当前处于在线状态的内网设备的设备标识；
    向所述网管设备发送所述心跳消息。
  7. 根据权利要求1-6任一所述的设备管理方法，其特征在于，在接收所述网管设备基于所述预定数据传输协议发送的第一管理报文之后，所述方法还包括：
    检测所述网关设备当前所处的网络环境；
    若当前所处的网络环境为预定网络环境，则切换为协议转换及汇聚处理工作模式，其中，所述协议转换及汇聚处理工作模式支持协议转换处理以及消息汇聚处理。
  8. 一种设备管理装置，其特征在于，所述装置应用于网关设备中，所述网关设备部署于网管设备和内网设备集群之间，所述网关设备与所述网管设备之间基于预定数据传输协议进行通信，所述网关设备与所述内网设备集群之间基于预定网络管理协议进行通信；所述装置包括：
    接收模块，用于接收所述网管设备基于所述预定数据传输协议发送的第一管理报文，其中，所述第一管理报文的目的网际协议IP地址为所述网关设备的公网 IP地址，所述第一管理报文携带目的设备标识；
    确定模块，用于确定所述目的设备标识是否为所述网关设备自身的设备标识；
    响应模块，用于在所述目的设备标识为所述网关设备自身的设备标识时，响应所述第一管理报文，以执行与所述第一管理报文对应的管理操作；
    所述响应模块，还用于在所述目的设备标识不为所述网关设备自身的设备标识时，根据内网设备的设备标识与对应私网IP地址之间的对应关系，确定与所述目的设备标识对应的第一私网IP地址；并根据所述第一私网IP地址将所述第一管理报文转换为符合所述预定网络管理协议的第二管理报文，所述第二管理报文的目的IP地址为所述第一私网IP地址；
    发送模块，用于将所述第二管理报文发送给所述第一私网IP地址对应的第一内网设备，以使所述第一内网设备执行与所述第二管理报文对应的管理操作。
  9. 一种通信设备，其特征在于，所述通信设备包括：
    存储器，用于存储程序指令；
    处理器，用于调用所述存储器中存储的程序指令，按照获得的程序指令执行权利要求1-7任一所述的设备管理方法包括的步骤。
  10. 一种存储介质，其特征在于，所述存储介质存储有计算机可执行指令，所述计算机可执行指令用于使计算机执行权利要求1-7任一所述的设备管理方法包括的步骤。
PCT/CN2020/140173 2019-12-30 2020-12-28 设备管理方法、装置、通信设备及存储介质 WO2021136175A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911399631.4A CN111130901B (zh) 2019-12-30 2019-12-30 设备管理方法、装置、通信设备及存储介质
CN201911399631.4 2019-12-30

Publications (1)

Publication Number Publication Date
WO2021136175A1 true WO2021136175A1 (zh) 2021-07-08

Family

ID=70505592

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/140173 WO2021136175A1 (zh) 2019-12-30 2020-12-28 设备管理方法、装置、通信设备及存储介质

Country Status (2)

Country Link
CN (1) CN111130901B (zh)
WO (1) WO2021136175A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114189436A (zh) * 2021-12-08 2022-03-15 深圳Tcl新技术有限公司 一种多集群配置部署方法、装置、电子设备和存储介质
CN114268979A (zh) * 2021-11-23 2022-04-01 贵州电网有限责任公司 一种网管终端北向接口的安全通信方法
CN114337719A (zh) * 2021-12-30 2022-04-12 杭州和利时自动化有限公司 数字天线、无线通信装置、轮询通讯以及通知通信方法
CN114500178A (zh) * 2021-12-21 2022-05-13 特斯联科技集团有限公司 一种自运维的智慧物联网关
CN115150830A (zh) * 2022-09-02 2022-10-04 北京首信科技股份有限公司 5g专网接入认证失败时保障终端公网访问的方法和系统
CN115941777A (zh) * 2022-11-25 2023-04-07 深圳市信锐网科技术有限公司 设备上线使用方法、出口管理设备、目标设备及相关装置
CN117221396A (zh) * 2023-10-26 2023-12-12 深圳市拓普泰尔科技有限公司 网络数据交互方法、装置、系统、存储介质和计算机设备
CN117424352A (zh) * 2023-12-19 2024-01-19 浙江简捷物联科技有限公司 储能柜主从自主切换方法及系统

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111130901B (zh) * 2019-12-30 2021-12-21 京信网络系统股份有限公司 设备管理方法、装置、通信设备及存储介质
CN114006858A (zh) * 2020-07-13 2022-02-01 中国移动通信有限公司研究院 IPv6信息的发现方法、装置、网络节点及存储介质
CN112532704B (zh) * 2020-11-20 2023-07-28 京东方科技集团股份有限公司 数据传输方法、装置、电子设备及存储介质
CN112532761B (zh) * 2020-11-23 2022-09-06 中盈优创资讯科技有限公司 一种公网地址自动上报备案的管理方法和装置
CN112637875B (zh) * 2020-12-22 2023-07-14 超讯通信股份有限公司 远程批量管理小基站的方法
CN112804099A (zh) * 2021-01-07 2021-05-14 大连市共进科技有限公司 参数批量配置方法、装置、计算机设备和可读存储介质
CN113992732B (zh) * 2021-10-26 2024-04-12 迈普通信技术股份有限公司 终端管理控制方法、装置、服务器及存储介质
CN114629518B (zh) * 2022-03-31 2024-03-01 厦门骐俊物联科技股份有限公司 一种数字对讲机的动态自组网方法
CN114710573B (zh) * 2022-06-07 2022-09-30 石家庄科林电气股份有限公司 一种基于ipv6的配电台区边端设备通信方法及装置
CN115550094B (zh) * 2022-12-01 2023-03-10 深圳市人马互动科技有限公司 一种局域网自组网方法以及装置

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1731740A (zh) * 2005-07-29 2006-02-08 杭州华为三康技术有限公司 网络设备的管理方法及网络管理系统
CN101043410A (zh) * 2006-03-24 2007-09-26 华为技术有限公司 实现移动vpn业务的方法及系统
CN101282232A (zh) * 2007-04-05 2008-10-08 华为技术有限公司 一种远端设备管理方法、设备及系统
CN101296203A (zh) * 2007-04-23 2008-10-29 华为技术有限公司 对家庭网络中应用终端进行自动配置的装置、系统和方法
CN102332999A (zh) * 2011-10-31 2012-01-25 迈普通信技术股份有限公司 一种基于共享nat的网络管理交互系统及交互方法
CN109889384A (zh) * 2019-02-22 2019-06-14 北京邮电大学 一种应用snmp协议进行nat穿越管理内网设备的方法
CN111130901A (zh) * 2019-12-30 2020-05-08 京信通信系统（中国）有限公司 设备管理方法、装置、通信设备及存储介质

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108574693A (zh) * 2018-04-17 2018-09-25 四川斐讯信息技术有限公司 一种无线路由器的接入管理方法及无线路由器

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1731740A (zh) * 2005-07-29 2006-02-08 杭州华为三康技术有限公司 网络设备的管理方法及网络管理系统
CN101043410A (zh) * 2006-03-24 2007-09-26 华为技术有限公司 实现移动vpn业务的方法及系统
CN101282232A (zh) * 2007-04-05 2008-10-08 华为技术有限公司 一种远端设备管理方法、设备及系统
CN101296203A (zh) * 2007-04-23 2008-10-29 华为技术有限公司 对家庭网络中应用终端进行自动配置的装置、系统和方法
US20100039958A1 (en) * 2007-04-23 2010-02-18 Huawei Technologies Co., Ltd. Device, system, and method for automatically configuring application terminals in home network
CN102332999A (zh) * 2011-10-31 2012-01-25 迈普通信技术股份有限公司 一种基于共享nat的网络管理交互系统及交互方法
CN109889384A (zh) * 2019-02-22 2019-06-14 北京邮电大学 一种应用snmp协议进行nat穿越管理内网设备的方法
CN111130901A (zh) * 2019-12-30 2020-05-08 京信通信系统（中国）有限公司 设备管理方法、装置、通信设备及存储介质

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114268979A (zh) * 2021-11-23 2022-04-01 贵州电网有限责任公司 一种网管终端北向接口的安全通信方法
CN114189436A (zh) * 2021-12-08 2022-03-15 深圳Tcl新技术有限公司 一种多集群配置部署方法、装置、电子设备和存储介质
CN114189436B (zh) * 2021-12-08 2024-04-30 深圳Tcl新技术有限公司 一种多集群配置部署方法、装置、电子设备和存储介质
CN114500178B (zh) * 2021-12-21 2024-04-02 特斯联科技集团有限公司 一种自运维的智慧物联网关
CN114500178A (zh) * 2021-12-21 2022-05-13 特斯联科技集团有限公司 一种自运维的智慧物联网关
CN114337719A (zh) * 2021-12-30 2022-04-12 杭州和利时自动化有限公司 数字天线、无线通信装置、轮询通讯以及通知通信方法
CN114337719B (zh) * 2021-12-30 2024-04-16 杭州和利时自动化有限公司 数字天线、无线通信装置、轮询通讯以及通知通信方法
CN115150830A (zh) * 2022-09-02 2022-10-04 北京首信科技股份有限公司 5g专网接入认证失败时保障终端公网访问的方法和系统
CN115150830B (zh) * 2022-09-02 2022-11-29 北京首信科技股份有限公司 5g专网接入认证失败时保障终端公网访问的方法和系统
CN115941777A (zh) * 2022-11-25 2023-04-07 深圳市信锐网科技术有限公司 设备上线使用方法、出口管理设备、目标设备及相关装置
CN117221396A (zh) * 2023-10-26 2023-12-12 深圳市拓普泰尔科技有限公司 网络数据交互方法、装置、系统、存储介质和计算机设备
CN117424352B (zh) * 2023-12-19 2024-03-12 浙江简捷物联科技有限公司 储能柜主从自主切换方法及系统
CN117424352A (zh) * 2023-12-19 2024-01-19 浙江简捷物联科技有限公司 储能柜主从自主切换方法及系统

Also Published As

Publication number Publication date
CN111130901B (zh) 2021-12-21
CN111130901A (zh) 2020-05-08

Similar Documents

Publication Publication Date Title
WO2021136175A1 (zh) 设备管理方法、装置、通信设备及存储介质
US8850068B2 (en) United router farm setup
EP2888858B1 (en) Method and apparatus of generalized network controller for a software defined network (sdn)
US9923978B2 (en) Automated network service discovery and communication
EP3594808B1 (en) Virtual machine migration method, switch, and virtual machine system
WO2017181876A1 (zh) 一种设备状态及资源信息监测方法、相关设备及系统
US20170111231A1 (en) System and method for communication
WO2020135574A1 (zh) 报文处理方法、装置、控制面设备和计算机存储介质
US20150058463A1 (en) Proxy methods for suppressing broadcast traffic in a network
US7788363B2 (en) Secure communication over virtual IPMB of a mainframe computing system
WO2017128953A1 (zh) 服务器虚拟化网络共享的装置和方法
CN110430114B (zh) 一种虚拟路由器及实现sdn网络与传统ip网络互联的方法
US7764682B2 (en) Mainframe computing system having virtual IPMI protocol
EP4440085A2 (en) Network function virtualization compute element image upgrade
CN104168338A (zh) 一种网络地址转换装置和方法
US20220247672A1 (en) LAN System, Method and Unit Supporting Dynamic Self-Adaptive Network Configuration
CN112968965B (zh) Nfv网络节点的元数据服务方法、服务器及存储介质
WO2024027217A1 (zh) 一种虚拟化核心网的时间敏感实现方法及系统
US20210075716A1 (en) Automatic routing configuration between hosts and network layer devices
WO2015188331A1 (zh) 转发控制方法、驱动器及sdn网络
KR20190066572A (ko) 가상화 기능 관리 장치 및 방법
WO2014090098A1 (zh) 一种分布式系统中检测协议的实现方法和装置
WO2023139811A1 (ja) Ｏ－ＲＡＮのＭ－ＰｌａｎｅにおけるＩＯＴデバイスのテストプロファイルの管理
US20220321412A1 (en) Method for networking multi-protocol terminals, method for communicating, storage medium, and electronic device
EP4184822A1 (en) Method and apparatus for keeping user terminal alive

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: 20909305

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: 20909305

Country of ref document: EP

Kind code of ref document: A1