WO2021057802A1

WO2021057802A1 - Das system management method and device, electronic device, and storage medium

Info

Publication number: WO2021057802A1
Application number: PCT/CN2020/117184
Authority: WO
Inventors: 徐亚雪; 凌邦祥; 简托
Original assignee: 三维通信股份有限公司
Priority date: 2019-09-23
Filing date: 2020-09-23
Publication date: 2021-04-01
Also published as: CN110808847A; CN110808847B

Abstract

The present application relates to a DAS system management method and device, an electronic device, and a storage medium. A DAS system management method comprises: a master device deploying a simple network management protocol agent according to a preset rule; the simple network management protocol agent in the master device receiving an SNMP message, and the master device parsing the SNMP message, so as to acquire a target device to be managed in a DAS system; and if the target device is a slave device, the master device converting the SNMP message so as to enable the slave device to be managed. The entire DAS system only deploys an SNMP agent in a master device, without deploying an SNMP agent in a slave device of the DAS system, so that all devices in the DAS system can be managed by means of an SNMP, improving the stability of the entire DAS system, simplifying the secondary development.

Description

Method and equipment for managing DAS system, electronic equipment and storage medium

Related application

This application claims the priority of the Chinese patent application filed on September 23, 2019, the application number is 201910900747.5, and the invention title is "Method and equipment for managing DAS system, electronic equipment, storage medium", the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the technical field of DAS systems, and in particular to a method, equipment, electronic equipment, and storage medium for managing a DAS system.

Background technique

The Distributed Antenna System (DAS) is a network composed of multiple antennas distributed in a building and dedicated to providing wireless indoor coverage. In the DAS system, there are AU (Access Unit), EU (Expansion Unit), and RU (Remote Unit). The DAS system is usually composed of a master device (note: this master device is AU), multiple slave devices and optional expansion units. Among them, there is a single master device, which serves as the control center of the entire DAS system and manages itself and all others. The expansion unit and slave device. Among them, the expansion unit EU and the remote unit RU are both slave devices and can be managed by the master device AU. The master device and the slave device are connected through transmission media such as optical fiber and network cable, and communicate using the IP protocol.

When it is necessary to manage the master device and slave device of the DAS system, generally only one master device can be accessed by the external network, and other slave devices have no external network. Even if the simple network management protocol agent is deployed for these slave devices without external network, Cannot be accessed by SNMP clients.

Summary of the invention

According to various embodiments of the present application, there is provided a method for managing a DAS system, the DAS system including a master device and at least one slave device communicating with the master device, and the method includes:

The main device deploys a simple network management protocol agent according to preset rules;

The Simple Network Management Protocol agent in the master device receives an SNMP message, and the SNMP message carries the device code of the target device;

The master device parses the SNMP message to obtain the target device to be managed in the DAS system;

When the target device is the slave device, the master device performs conversion processing on the SNMP message so that the slave device can be accessed and managed.

In one of the embodiments, the master device deploys the simple network management protocol agent according to preset rules, including:

The main device obtains the open source simple network management protocol proxy source code;

The main device compiles and modifies the source code based on the version number of the simple network management protocol, so that the simple network management protocol agent can receive the SNMP message encoded by the portable device;

The host device installs the modified simple network management protocol proxy source code.

In one of the embodiments, the main device compiling and modifying the source code based on the version number of the simple network management protocol includes:

Acquiring, by the master device, a version number of the simple network management protocol, where the version number includes a first version, a second version, or a third version;

When the version number is the first version or the second version, modify the interface function in the source code, and the interface function is used to parse the data message;

When the version number is the third version, modify the registry check function.

In one of the embodiments, the modification of the interface function in the source code includes:

Add netsnmp_agent_request_info*reqinfo parameter.

In one of the embodiments, the master device parsing the SNMP message to obtain the target device to be managed in the DAS system includes:

The master device parses a preset field in the SNMP message to obtain a device code;

Obtain the target device according to the device code; wherein the preset field is the location of the Community or the Context Name in the location of the SNMP message, and the device code is used to identify the target device.

In one of the embodiments, the master device parsing the SNMP message to obtain the target device to be managed in the DAS system further includes:

The main device parses the preset fields in the SNMP message to obtain fixed characters;

Before acquiring the target device according to the device code, the method further includes:

Authenticate the fixed characters in the SNMP message;

After the authentication is passed, the target device is obtained according to the device code.

In one of the embodiments, when the target device is the slave device, the master device performs conversion processing on the SNMP message so that the slave device can be accessed and managed, including:

When the target device is the slave device, the master device converts the SNMP message to form a mobile data packet and outputs it to the target device, and the mobile data packet has a DAS protocol packet format;

The target device processes and responds to the mobile data packet and transmits it to the host device;

The master device converts the mobile data packet after the response into an SNMP data packet so that the slave device can be accessed and managed.

In one of the embodiments, the method further includes:

When the target device is the master device, the master device processes the SNMP message so that the master device can be accessed and managed.

According to various embodiments of the present application, a device for managing a DAS system is also provided, including:

SNMP client, used to send SNMP packets;

The DAS system includes a master device and at least one slave device communicating with the master device; wherein the master device communicates with the SNMP client; the master device is deployed with a simple network management protocol agent according to preset rules , And receive and parse the SNMP message to obtain the target device to be managed in the DAS system. When the target device is the slave device, the master device converts the SNMP message Process to enable the slave device to be accessed and managed.

According to various embodiments of the present application, there is also provided an electronic device, including a memory and a processor, and a computer program is stored in the memory. When the computer program is executed by the processor, the processor executes management Steps of the method of the DAS system.

According to various embodiments of the present application, there is also provided a computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the steps of the method for managing a DAS system are implemented.

The above-mentioned method and equipment for managing DAS system, electronic equipment, and computer-readable storage medium have the following advantages:

The entire DAS system only deploys the SNMP agent on the master device, and does not need to deploy the SNMP agent on the slave device of the DAS system, which can realize the management of all devices in the DAS system through SNMP. Furthermore, most of the slave devices in the DAS system do not need to deploy SNMP agents on the slave devices, which improves the stability of the entire DAS system, and when the SNMP development version needs to be updated, only the agent deployed in the master device needs to be modified. , Simplifies the secondary development.

Description of the drawings

In order to better describe and explain the embodiments and/or examples of those inventions disclosed herein, one or more drawings may be referred to. The additional details or examples used to describe the drawings should not be considered as limiting the scope of any of the disclosed inventions, the currently described embodiments and/or examples, and the best mode of these inventions currently understood.

Fig. 1 is an application environment diagram of a method for managing a DAS system according to an embodiment of the present application.

Fig. 2 is a flowchart of a method for managing a DAS system according to an embodiment of the present application.

Fig. 3 is a flow chart of a device according to an embodiment of the present application deploying a simple network management protocol agent according to preset rules.

Fig. 4 is a flowchart of a master device parsing the SNMP packet in an embodiment of the present application to obtain a target device used for processing the SNMP packet in the DAS system.

FIG. 5 is a flowchart of a master device parsing the SNMP message to obtain a target device used to process the SNMP message in the DAS system according to another embodiment of the present application.

Fig. 6 is a flow chart of the master device converting the SNMP message to enable the slave device to be accessed and managed when the target device is the slave device in an embodiment of the present application.

Fig. 7 is a flowchart of the conversion of SNMP messages between the master device and the slave device according to an embodiment of the present application.

detailed description

In order to facilitate the understanding of this application, and to make the above objectives, features and advantages of this application more comprehensible, specific implementations of this application will be described in detail below with reference to the accompanying drawings. In the following description, many specific details are set forth in order to fully understand the application, and the preferred embodiments of the application are shown in the accompanying drawings. However, this application can be implemented in many different forms and is not limited to the implementation described herein. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of this application more thorough and comprehensive. This application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar improvements without violating the connotation of this application. Therefore, this application is not limited by the specific embodiments disclosed below.

In addition, the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present application, "a plurality of" means at least two, such as two, three, etc., unless specifically defined otherwise. In the description of this application, "several" means at least one, such as one, two, etc., unless otherwise specifically defined.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field of this application. The terminology used herein is only for the purpose of describing specific embodiments, and is not intended to limit the application. The term "and/or" as used herein includes any and all combinations of one or more related listed items.

The DAS system is usually composed of a master device (note: this master device is AU), multiple slave devices and optional expansion units. Among them, there is a single master device, which serves as the control center of the entire DAS system, managing itself and all others. The expansion unit and slave device.

The network management method of the DAS system is based on the Simple Network Management Protocol (SNMP) to manage the master and slave devices in the DAS system. Among them, the SNMP protocol uses the C/S structure. SNMP is a standard protocol specifically designed to manage network nodes (servers, workstations, routers, switches, HUBS, etc.) in an IP network. It is an application layer protocol, for example, an application layer protocol of the TCP/IP protocol suite . Among them, the simple network management protocol includes three SNMP protocol versions: SNMPv1 (RFCs 1155-1157), SNMPv2c (RFCs 1901-1908), and SNMPv3 (RFCs 2271-2275).

Fig. 1 is a schematic diagram of an application environment of a network management method of a DAS system in an embodiment. As shown in Figure 1, the application environment includes SNMP client (network management) and SNMP server. Among them, the SNMP server can be understood as a master device deployed with an SNMP agent. The master device has a unique IP address and MAC address. Both SNMP client and SNMP server support the SNMP protocol to realize the communication between SNMP client and SNMP server. The SNMP client can directly access the main device where the SNMP agent is deployed according to the IP address of the main device.

Fig. 2 is a flowchart of a method of managing a DAS system in an embodiment. The method for managing the DAS system in this embodiment is described by taking the DAS system in FIG. 1 as an example. As shown in FIG. 2, the method of managing the DAS system includes steps 201 to 204.

Step 201: The master device deploys a simple network management protocol agent according to preset rules.

Agent is a network management software module that exists in the managed equipment. The agent is used to control the management information of the local device and transmit the management information in a format compatible with SNMP.

In the embodiment of the present application, the simple network management protocol agent (SNMP agent) is deployed in the master device of the DAS system according to preset rules. Among them, the preset rules can be understood as the rules for compiling and modifying the traditional open source SNMP agent source code. For example, traditional open source SNMP agent source code can be compiled and modified based on preset rules to obtain custom SNMP agent source code. The main device can use the custom SNMP agent source code to install and deploy the SNMP agent.

Step 202: The Simple Network Management Protocol agent in the master device receives an SNMP message.

If the newly compiled SNMP agent is deployed in the main device, the main device can be used as an SNMP server to realize network communication with SNMP clients. When the main device runs based on the modified SNMP agent source code, the SNMP agent in the main device can interact with the SNMP client, and then accept SNMP packets sent by the SNMP client. Among them, the character information in a specific location (for example, Community and Context Name) in the SNMP message sent by the SNMP client can be recognized by the newly compiled SNMP agent. What character information needs to be put in this specific position is provided by the host device developer with the protocol, and the SNMP client fills this field according to the protocol.

For example, the target device to be managed can be set through the WEBOMT interface of the main device. For example, a fixed character can be set through the WEBOMT interface of the main device. The fixed character and the device code form a preset field, which will be placed in a specific location (Community and Context Name) of the SNMP message and transmitted to the main device along with the SNMP message in. The device code can be understood as the unique identification of the device. Among them, in the DAS system, the device number of the slave device can be configured by the master device, and the device number of each slave device in the same DAS system is unique.

In one embodiment, in SNMP v1/v2c, the SNMP client needs to fill the community field in the SNMP v1/v2c data packet with fixed characters + device code before sending SNMP packet data.

In one embodiment, in SNMPv3, the SNMP client needs to fill the Context Name field in the SNMPv3 packet with fixed characters + device code before sending SNMP packet data.

It should be noted that the "+" does not need to be filled when filling.

Step 203: The master device parses the SNMP message to obtain the target device to be managed in the DAS system. The SNMP message carries the device code of the target device.

In an embodiment, for example, a simple SNMP v2c GET message can be displayed as follows: "snmpget-v 2c-c public local host system.sysName.0".

Among them, the community name (Community) in the traditional SNMP v1/v2c message is fixed as public. That is, before the source code is modified, after the master device receives the SNMP message data, it can only parse the Community as public. However, in the embodiment of the present application, after the simple network management protocol agent is deployed by the main device according to preset rules through step 202, the main device of the deployed simple network management protocol agent can handle any community, that is, the main The device can parse the characters in the position to obtain the device code carried in the SNMP message information, and obtain the target device to be managed according to the device code.

In one embodiment, for example, a simple SNMP v3 GET message can be displayed as follows: "snmpget-v 3-n"public"-u noAuthUser-l noAuthNoPriv" or "snmpget-v 3-u noAuthUser-l noAuthNoPriv" . It should be noted that the above two are just examples to illustrate Context Name. Among them, the SNMPv3 message has Context Name. When adding with -n in the source code, only public can be added. When other characters are added, the operation will be abnormally terminated; or it is not displayed in the message, and the default is public at this time. That is, before the source code is modified, after the master device receives the SNMP message data, it can only resolve the Context Name to public or not display it.

In one of the embodiments, the SNMP v3 GET message can be displayed as follows: "snmpget-v 3-n"public"-l authPriv-u username-A spassword-a SHA-X spassword-x AES" or "snmpget-v 3-l authPriv-u username-A spassword-a SHA-X spassword-x AES". Through step 202, after the master device deploys the simple network management protocol agent according to the preset rules, the master device of the deployed simple network management protocol agent can process any Context Name, that is, the master device can parse the characters in the position , To obtain the device code carried in the SNMP message information, and obtain the target device to be managed according to the device code.

It should be noted that the target device can be the master device in the DAS system or the slave device in the DAS system.

Step 204: When the target device is the slave device, the master device performs conversion processing on the SNMP message so that the slave device can be managed.

When the target device is the slave device, the master device can convert the SNMP message to convert it into a DAS internal protocol packet, and then send the DAS internal protocol packet to the corresponding slave device. After the DAS internal protocol packet is processed and responded, it is sent back to the master device. Among them, the data packet received by the slave device has been changed from the SNMP message data to the DAS internal protocol packet by the master device, so there is no need to do any SNMP processing on the slave device. The master device receives the DAS internal protocol packet returned by the slave device, and then converts it into an SNMP packet and sends it to the SNMP network manager, so that the slave device can be accessed and managed by the SNMP network manager.

In the embodiment of the present application, the main device deploys a simple network management protocol agent according to preset rules; the simple network management protocol agent in the main device receives SNMP packets, and the main device parses the SNMP packets, To obtain the target device to be managed in the DAS system; when the target device is the slave device, the master device performs conversion processing on the SNMP message to enable the slave device to be managed. The entire DAS system only deploys the SNMP agent on the master device, and does not need to deploy the SNMP agent on the slave device of the DAS system, which can realize the management of all devices in the DAS system through SNMP. Furthermore, most of the slave devices in the DAS system do not need to deploy SNMP agents on the slave devices, which improves the stability of the entire DAS system, and when the SNMP development version needs to be updated, only the agent deployed in the master device needs to be modified. , Simplifies the secondary development.

In one of the embodiments, the method for managing the DAS system further includes: when the target device is the master device, the master device processes the SNMP message so that the master device can be accessed and managed A step of.

Specifically, when the target device is the main device itself, its main device can process the SNMP packet, for example, it can parse the information contained in the SNMP packet, such as read power, write attenuation, and so on. The main device can feed back the processed SNMP message to the SNMP client based on the SNMP protocol to realize the access management of the main device by SNMP.

In one of the embodiments, as shown in FIG. 3, the master device deploys the simple network management protocol agent according to preset rules, including:

Step 301: The main device obtains the open source simple network management protocol proxy source code.

Step 302: The main device compiles and modifies the source code based on the version number of the simple network management protocol, so that the simple network management protocol agent can receive the SNMP message encoded by the portable device.

Step 303: The host device installs the modified simple network management protocol proxy source code.

The master device obtains the version number of the simple network management protocol. The simple network management protocol includes the first version of SNMPv1 (RFCs 1155-1157), the second version of SNMPv2c (RFCs 1901-1908), or the third version of SNMPv3 (RFCs2271-2275). ) Three SNMP protocol versions.

Among them, the first version of SNMPv1 is the initial version of the SNMP protocol, providing minimal network management functions. SNMPv1 uses community name authentication, which is similar to a password and is used to restrict network management system (NMS) access to agents. The second version of SNMPv2c also uses community name authentication. It is compatible with SNMPv1 and also provides more operation types (GetBulk--Bulk get operation, etc.); supports more data types (Counter32, etc.). The third version of SNMPv3 adds security management methods and remote control, it uses USM (user-based security control model) and VACM (view-based access control model) technology.

Further, the main device compiling and modifying the source code based on the version number of the simple network management protocol specifically includes:

When the simple network management protocol is the first version SNMPv1 or the second version SNMPv2c protocol version, the main device can transplant the open source simple network management protocol agent source code and modify the obtained agent source code. Specifically, the interface function Variables_Handler in the agent source code can be modified, where the interface function Variables_Handler is used to parse the data message. The modification method can be to add the netsnmp_agent_request_info*reqinfo parameter to the interface function Variables_Handler, and add this parameter to all upper-level interface functions in the agent source code.

In the embodiment of this application, after adding formal parameters to the interface function Variables_Handler, after the agent runs in the main device, when the SNMP client enters any character in the Community of the SNMP message, the simple network management protocol in the main device The agent can receive the SNMP message data including the characters in the Community, and forward the SNMP message data to the SNMP process of the main device, and then the main device can analyze and process the SNMP message.

In the embodiment of this application, by adding the netsnmp_agent_request_info*reqinfo parameter to the interface function Variables_Handler, the community name in the SNMP message, that is, the community Community, can not be fixed as public, and the agent in the main device can handle any community.

When the version number is the third version of SNMPv3, there is no community in the SNMP message of SNMPv3, and the modification processing method of SNMPv1 or SNMPv2c cannot be used. However, SNMPv3 is compatible with the above-mentioned SNMPv1 or SNMPv2c. On the basis of the above-mentioned SNMPv1 or SNMPv2c, the source code of the open source simple network management protocol agent is modified again. Specifically, you can focus on modifying the Context Name registry detection function so that the agent can receive and process any Context Name in the SNMP message.

In the embodiment of this application, after modifying the Context Name registry, after the agent runs in the main device, any Context Name in the SNMP message can be received by the Simple Network Management Protocol agent in the main device, and the SNMP message The data is forwarded to the SNMP process of the master device, and then the master device parses the SNMP message.

In the embodiment of the present application, the DAS system implements three SNMP protocol version compatible processing, SNMPv1, SNMPv2c, and SNMPv3. The SNMP client can use any version to access the master device and the slave device in the DAS system.

In one of the embodiments, as shown in FIG. 4, the master device parses the SNMP message to obtain the target device used for processing the SNMP message in the DAS system, which specifically includes:

Step 401: The master device parses a preset field in the SNMP message to obtain a device code;

Step 402: Obtain the target device according to the device code; wherein the preset field is the location of Community or Context Name in the location of the SNMP message, and the device code is used to identify the target device.

In one of the embodiments, in SNMP v1/v2c, the SNMP client needs to fill the community field in the SNMP v1/v2c data packet with fixed characters + device code before sending SNMP packet data. When the master device receives the SNMP message, it can parse the community field location to obtain the device code carried in the SNMP message information, and obtain the target device to be managed according to the device code. Wherein, the device code is used to identify the target device. That is, the preset field of the SNMP message carries identity information used to identify the target device.

Take SNMP v2c as an example for description. Assume that the master device receives the following SNMP message "snmpget-v 2c-c swdas0hostIP OID". The master device can first parse the public swdas0, and then get the number after swdas, which is 0 here. Where 0 can be used to represent the identity information of the master device. Therefore, the SNMP message is sent by the SNMP client to the main device, and can be directly processed by the main device to realize access management to the main device.

Taking SNMP v2c as an example, suppose the master device receives the following SNMP message "snmpget-v 2c-c swdas1hostIP OID". The master device can first parse the swdas1 public body, and then obtain the number after swdas, which is 1 here. Among them, 1 can be used to represent the identity information of a certain slave device. It means that the SNMP message is not sent to the master device, but the SNMP client sends to the slave device corresponding to the device code "1" in the DAS system.

In SNMPv3, the SNMP client needs to fill the Context Name field in the SNMPv3 packet with fixed characters + device sub id before sending SNMP packet data. When the master device receives the SNMP message, it can parse the device code in the Context Name field to obtain the device code carried in the SNMP message information, and obtain the target device to be managed according to the device code.

In one of the embodiments, as shown in FIG. 5, the master device parses the SNMP message to obtain the target device to be managed in the DAS system, and further includes:

Step 403: The master device parses the preset fields in the SNMP message to obtain fixed characters.

Step 402: Before acquiring the target device according to the device code, step 404 is further included.

Step 404: Authenticate the fixed characters in the SNMP message, and execute step 402 after the authentication is passed.

In one of the embodiments, in order to ensure that the master device receives a secure data message, after the master device receives the SNMP message, it will authenticate the fixed characters in a preset field (such as Community or Context Name), that is, Verify whether the Community or Context Name field meets the security requirements. If the security requirements are not met, an error is returned. When the safety requirements are met, step 402 is executed. For example, when the SNMP message received by the master device is "snmpget-v 2c-c swdas1hostIP OID", the master device will parse the swdas1 community, and first determine whether swdas meets the security requirements. If it meets the security requirements, perform step 402, Characters obtain the target device. That is, the master device will obtain the number after swdas, here is 1, which means that the SNMP message is not sent to the master device, but to the slave device corresponding to the device code "1" in the DAS system. That is the target device.

In one of the embodiments, as shown in FIG. 6, when the target device is the slave device, the master device converts the SNMP message so that the slave device can be accessed and managed, including :

Step 501: When the target device is the slave device, the master device converts the SNMP message to form a mobile data packet and outputs it to the target device. The mobile data packet has a DAS protocol packet. format;

Step 502: The target device processes and responds to the mobile data packet and transmits it to the host device;

Step 503: The master device converts the mobile data packet after the response into an SNMP data packet so that the slave device can be accessed and managed.

Specifically, referring to Fig. 7, a simple example of SNMPv2c Community is used for illustration. Packet 1 is an SNMP message received by the master device. The master device parses data packet 1, and the device code contained in its Community is 1, that is, the target device is a slave device with device number 1. At the same time, the data packet 1 also includes the OID in the SNMP protocol. When the target device is the slave device, the master device converts data packet 1 into data packet 2. The data packet 2 can be understood as a packet of other protocols that can be recognized by the slave device, for example, DAS internal protocol packet . The master device sends the mobile data packet to the target device for processing, and the target device does not need to deploy the SNMP agent to process and respond to the mobile data packet. When the target device processes the mobile data packet, it forms data packet 3, and sends the data packet 3 back to the master device. The master device converts the mobile data packet after the response and converts it to something that can be recognized by the SNMP client. SNMP data packet, and then realize the access management to the target device.

It should be understood that, although the steps in the flowcharts of FIGS. 2 to 6 are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, there is no strict order for the execution of these steps, and these steps can be executed in other orders. Moreover, at least part of the steps in Figure 2-6 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. These sub-steps or The execution order of the stages is not necessarily carried out sequentially, but may be executed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

As shown in Figure 1, the equipment that manages the DAS system includes:

SNMP client, used to send SNMP packets;

The entire DAS system only deploys the SNMP agent on the master device, and does not need to deploy the SNMP agent on the slave device of the DAS system, and can manage all devices in the DAS system through SNMP. Furthermore, most of the slave devices in the DAS system do not need to deploy SNMP agents on the slave devices, which improves the stability of the entire DAS system, and when the SNMP development version needs to be updated, only the agent deployed in the master device needs to be modified. , Simplifies the secondary development.

In one of the embodiments, the main device includes:

The deployment module is used to deploy a simple network management protocol agent according to preset rules;

Agent module, used to receive SNMP messages;

A parsing module, configured to parse the SNMP message to obtain the target device to be managed in the DAS system;

The processing module is configured to: when the target device is the slave device, the master device performs conversion processing on the SNMP message so that the slave device can be accessed and managed.

Further, the deployment module is further used to obtain the open source simple network management protocol agent source code; compile and modify the source code based on the version number of the simple network management protocol, so that the simple network management protocol agent can receive and carry The SNMP message encoded by the device; the simple network management protocol agent source code after installation and modification.

Further, the parsing module is further configured to parse a preset field in the SNMP message to obtain a device code; obtain the target device according to the device code; wherein, the preset field is in the SNMP message The location of is the location of Community or ContextName, and the device code is used to identify the target device.

In one of the embodiments, the parsing module is further used to parse preset fields in the SNMP message to obtain fixed characters, and the main device further includes an authentication module for verifying the fixed characters in the SNMP message. For authentication, the parsing module is further configured to obtain the target device according to the device code after the authentication is passed.

In one of the embodiments, the processing module is also used to convert the SNMP message to form a mobile data packet and output it to the target device. The mobile data packet has the format of a DAS protocol packet; The mobile data packet after the device response is converted into an SNMP data packet so that the slave device can be accessed and managed.

In one of the embodiments, the processing module is further configured to, when the target device is the master device, the master device processes the SNMP message so that the master device can be accessed and managed.

The division of each module in the device for managing the DAS system is only for illustration. In other embodiments, the device for managing the DAS system can be divided into different modules as needed to complete all or part of the device for managing the DAS system. Features.

Regarding the specific limitation of the device for managing the DAS system, please refer to the above limitation on the method of managing the DAS system, which will not be repeated here. Each module in the above-mentioned equipment for managing the DAS system can be implemented in whole or in part by software, hardware, and combinations thereof. The above-mentioned modules may be embedded in the form of hardware or independent of the processor in the computer equipment, or may be stored in the memory of the computer equipment in the form of software, so that the processor can call and execute the operations corresponding to the above-mentioned modules.

The implementation of each module in the device for managing the DAS system provided in the embodiments of the present application may be in the form of a computer program. The computer program can be run on a terminal or a server. The program module composed of the computer program can be stored in the memory of the terminal or the server. When the computer program is executed by the processor, it realizes the steps of the method described in the embodiments of the present application.

The embodiment of the present application also provides a computer-readable storage medium. One or more non-volatile computer-readable storage media containing computer-executable instructions, when the computer-executable instructions are executed by one or more processors, cause the processors to perform the steps of the method for managing a DAS system .

The embodiment of the present application also provides a computer program product containing instructions, which when running on a computer, causes the computer to execute the method for managing the DAS system.

An embodiment of the present application also provides an electronic device, including a memory and a processor, the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the method for managing a DAS system A step of.

Any reference to memory, storage, database, or other media used in this application may include non-volatile and/or volatile memory. Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which acts as external cache memory. As an illustration and not a limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The above-mentioned embodiments only express several implementation manners of the present application, and their description is relatively specific and detailed, but they should not be understood as a limitation to the scope of the present application. It should be pointed out that for those of ordinary skill in the art, without departing from the concept of this application, several modifications and improvements can be made, and these all fall within the protection scope of this application. Therefore, the scope of protection of the patent of this application shall be subject to the appended claims.

Claims

A method for managing a DAS system, wherein the DAS system includes a master device and at least one slave device communicating with the master device, and the method includes:

The main device deploys a simple network management protocol agent according to preset rules;

The Simple Network Management Protocol agent in the master device receives an SNMP message, and the SNMP message carries the device code of the target device;

The master device parses the SNMP message to obtain the target device to be managed in the DAS system;

When the target device is the slave device, the master device performs conversion processing on the SNMP message so that the slave device can be accessed and managed.
The method according to claim 1, wherein the main device deploys a simple network management protocol agent according to a preset rule, comprising:

The main device obtains the open source simple network management protocol proxy source code;

The main device compiles and modifies the source code based on the version number of the simple network management protocol, so that the simple network management protocol agent can receive the SNMP message encoded by the portable device;

The host device installs the modified simple network management protocol proxy source code.
The method according to claim 2, wherein the main device compiling and modifying the source code based on the version number of the simple network management protocol comprises:

Acquiring, by the master device, a version number of the simple network management protocol, where the version number includes a first version, a second version, or a third version;

When the version number is the first version or the second version, modify the interface function in the source code, and the interface function is used to parse the data message;

When the version number is the third version, modify the registry check function.
The method according to claim 3, wherein said modifying the interface function in the source code comprises:

Add netsnmp_agent_request_info*reqinfo parameter.
The method according to claim 1, wherein the master device parsing the SNMP message to obtain the target device to be managed in the DAS system comprises:

The master device parses a preset field in the SNMP message to obtain a device code;

Obtain the target device according to the device code; wherein the preset field is the location of the Community or the Context Name in the location of the SNMP message, and the device code is used to identify the target device.
The method according to claim 5, wherein the master device parses the SNMP message to obtain the target device to be managed in the DAS system, further comprising:

The main device parses the preset fields in the SNMP message to obtain fixed characters;

Before acquiring the target device according to the device code, the method further includes:

Authenticate the fixed characters in the SNMP message;

After the authentication is passed, the target device is obtained according to the device code.
The method according to claim 1, wherein when the target device is the slave device, the master device converts the SNMP message so that the slave device can be accessed and managed ,include:

When the target device is the slave device, the master device converts the SNMP message to form a mobile data packet and outputs it to the target device, and the mobile data packet has a DAS protocol packet format;

The target device processes and responds to the mobile data packet and transmits it to the host device;

The master device converts the mobile data packet after the response into an SNMP data packet so that the slave device can be accessed and managed.
The method according to claim 1, wherein the method further comprises:

When the target device is the master device, the master device processes the SNMP message so that the master device can be accessed and managed.
A device for managing a DAS system, characterized in that it includes:

SNMP client, used to send SNMP packets;

The DAS system includes a master device and at least one slave device communicating with the master device; wherein the master device communicates with the SNMP client; the master device is deployed with a simple network management protocol agent according to preset rules , And receive and parse the SNMP message to obtain the target device to be managed in the DAS system. When the target device is the slave device, the master device converts the SNMP message to Enable the slave device to be accessed and managed.
An electronic device, comprising a memory and a processor, and a computer program is stored in the memory. When the computer program is executed by the processor, the processor executes any one of claims 1 to 8. Steps of the method of managing the DAS system.
A computer-readable storage medium with a computer program stored thereon, wherein the computer program implements the steps of the method for managing a DAS system according to any one of claims 1 to 8 when the computer program is executed by a processor.