CN112187482A

CN112187482A - Device management method, system, electronic device and storage medium

Info

Publication number: CN112187482A
Application number: CN202010920111.XA
Authority: CN
Inventors: 刘传君; 陈应东; 徐灶良
Original assignee: Hangzhou Runzhou Optoelectronic Technology Co ltd
Current assignee: Hangzhou Runzhou Optoelectronic Technology Co ltd
Priority date: 2020-09-04
Filing date: 2020-09-04
Publication date: 2021-01-05
Anticipated expiration: 2040-09-04
Also published as: CN112187482B

Abstract

The application relates to a device management method, a system, an electronic device and a storage medium, belonging to the technical field of device management, wherein the method is applied to an OLT and comprises the following steps: acquiring information of ONU equipment, wherein the information comprises state information and flow information; monitoring the state and flow of the ONU equipment according to the information, and carrying out charging management on an account of a user, wherein the account is correspondingly bound with the ONU equipment; and executing to close or activate the ONU equipment based on the charging management. The OLT monitors and charges the ONU equipment, and can integrate the management and the charging of the equipment into a whole, thereby improving the management efficiency of the equipment.

Description

Device management method, system, electronic device and storage medium

Technical Field

The present application relates to the field of device management technologies, and in particular, to a device management method, a system, an electronic device, and a storage medium.

Background

In the prior art, for the management of the device, for example, there is a relatively complex monitoring dedicated platform provided by a manufacturer. However, these monitoring-dedicated platforms are usually only managed for hardware devices provided by the manufacturer, and cannot manage devices of other companies. When the equipment is managed, the aspects of the equipment are complicated, a large amount of training is needed, and the specific use flow and convenience of enterprises are not considered. For example, when an enterprise needs to charge in the using process, a pure charging platform on the market can be used, and then the monitoring dedicated platform and the charging platform need to mutually call data to realize the comprehensive management of the device, which may result in low management efficiency of the device.

Disclosure of Invention

The embodiment of the application provides a device management method, a device management system, an electronic device and a computer-readable storage medium, so as to at least solve the problem of low management efficiency of devices in the related art.

In a first aspect, an embodiment of the present application provides an apparatus management method, which is applied to an olt (optical Line terminal), and the method includes: acquiring information of ONU (optical Network unit) equipment, wherein the information comprises state information and flow information; monitoring the state and flow of the ONU equipment according to the information, and carrying out charging management on an account of a user, wherein the account is correspondingly bound with the ONU equipment; and executing to close or activate the ONU equipment based on the charging management.

Optionally, the executing of closing or opening a network channel based on the charging management includes: performing comprehensive calculation on the recharging, charging and refunding of the account; matching the calculation result with a preset service rule; if the service deadline is over, the ONU equipment is automatically closed; and if the service life of the service is prolonged, automatically activating the ONU equipment.

Optionally, the information includes device information, and the device information is obtained by: the device Information is extracted or set by an snmp (simple Network Management protocol) protocol and an mib (Management Information base) library.

Optionally, the information includes device information, and the device information is obtained by: acquiring a parameter object, a pre-programmed script and a preset callback function of the ONU equipment; compiling and generating an executable script according to the parameter object, the script and the callback function; and extracting or setting the equipment information by using the executable script.

Optionally, the pre-compiled script includes a system interaction expectation, an EJS template and a macro.

Optionally, the OLT and the ONU device establish a connection through a telnet.

Optionally, the compiling and generating an executable script according to the parameter object, the script and the callback function includes: acquiring the output of a telnet as the parameter object aiming at the system interaction expectation; and sending the output to the EJS template and the callback function to generate an executable script.

In a second aspect, an embodiment of the present application provides an apparatus management system, including: the system comprises an OLT and at least one ONU device connected with the OLT, wherein the ONU device is used for uploading information, and the information comprises state information and flow information; the OLT is used for acquiring the information; monitoring the state and flow of the ONU equipment according to the information, and carrying out charging management on an account of a user, wherein the account is correspondingly bound with the ONU equipment; and executing to close or activate the ONU equipment based on the charging management.

In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a storage medium storing a computer program, where the computer program, when executed by the processor, implements the device management method according to any one of the above items.

In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the device management method according to any one of the above items.

According to the above, the device management method according to the embodiment of the present invention is applied to the OLT, and the method includes: acquiring information of ONU equipment, wherein the information comprises state information and flow information; monitoring the state and flow of the ONU equipment according to the information, and carrying out charging management on an account of a user, wherein the account is correspondingly bound with the ONU equipment; and executing to close or activate the ONU equipment based on the charging management. The OLT monitors and charges the ONU equipment, and can integrate the management and the charging of the equipment into a whole, thereby improving the management efficiency of the equipment.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a flowchart illustrating a device management method according to embodiment 1 of the present invention;

fig. 2 is a schematic interface diagram showing each ONU device in an OLT list according to embodiment 2 of the present invention;

fig. 3 is a schematic interface diagram illustrating different versions of ONU devices displayed in an OLT list according to embodiment 2 of the present invention;

FIG. 4 is a schematic interface diagram showing a script according to embodiment 2 of the present invention;

fig. 5 is a flowchart illustrating a device management method according to embodiment 2 of the present invention;

fig. 6 is a schematic interface diagram showing fields of an ONU device according to embodiment 2 of the present invention;

fig. 7 is a schematic configuration diagram of a device management system according to embodiment 3 of the present invention;

fig. 8 is a schematic structural diagram of an electronic device according to embodiment 4 of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided in the present application without any inventive step are within the scope of protection of the present application.

It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of ordinary skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.

Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. Reference to "a," "an," "the," and similar words throughout this application are not to be construed as limiting in number, and may refer to the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as referred to herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.

Example 1

Referring to fig. 1, the device management method of the present embodiment includes the following steps:

s1: acquiring information of ONU equipment, wherein the information comprises state information and flow information;

s2: monitoring the state and flow of the ONU equipment according to the information, and carrying out charging management on an account of a user, wherein the account is correspondingly bound with the ONU equipment;

s3: and executing to close or activate the ONU equipment based on the charging management.

As an example, performing closing or opening a network channel based on charging management includes: the recharging, charging and refunding of the account are comprehensively calculated; matching the calculation result with a preset service rule; if the service deadline is over, the ONU equipment is automatically closed; and if the service life of the service is prolonged, automatically activating the ONU equipment.

As an example, the information includes device information obtained by: and extracting or setting the equipment information through the SNMP protocol and the MIB library.

As an example, the device information may also be obtained as follows: acquiring a parameter object, a pre-programmed script and a preset callback function of ONU equipment; compiling and generating an executable script according to the parameter object, the script and the callback function; the device information is extracted or set using the executable script.

As one example, the pre-scripted script includes system interaction expectations, EJS templates, and macros.

As an example, the OLT establishes a connection with the ONU device through a telnet.

As an example, generating an executable script from a parameter object, a script, and a callback function compilation includes: aiming at system interaction expectation, acquiring the output of a telnet as a parameter object; and sending the output to the EJS template and the callback function to generate an executable script.

By the embodiment, the management and the charging of the equipment can be integrated, so that the management efficiency of the equipment is improved, the management (such as expansion, addition and modification) of the ONU equipment script by a user can be realized, and the support to the equipment with an updated version can be ensured even if the equipment version is changed.

Example 2

In reality, the device management software includes two types, one is large and complete relatively complex monitoring dedicated software provided by manufacturers, and the other is comprehensive simple charging software. The first type of software is represented by Hua as a unified network management system U2000, Zhongxing NetNumen U31, aims at and only aims at own hardware equipment as a management object, and cannot manage products of other companies. The management range is equipment, and the aspects related to the equipment are complex, require a great deal of training and do not consider the flow and convenience of specific use enterprises, so that the software does not and should not consider the billing problem. The second type of software is specially used for charging, uses a RADIUS protocol, obtains charging information from network management equipment (typically a router), takes a hundred million network authentication charging system and the like as representatives, has universality and usability, but cannot monitor the management equipment. In general, these are two separate technical and product areas, and it is difficult to think of forces acting in both areas simultaneously. Therefore, the efficiency is low when the device related to charging is comprehensively managed at present.

In the embodiment, the OLT is added to manage and monitor the flow and the state of the ONU equipment, and the account number of the user is bound, so that the charging, the charging and the refunding of the account number of the user are comprehensively calculated, the network channel is automatically closed if the service period expires, and the network channel is automatically opened if the user account number renews the fee.

Specifically, the ONU device needs to interact with the OLT, for example, using an SNMP protocol or a Telnet command line. It should be noted that the SNMP protocol is an international standard that requires vendor support and provides the necessary MIB data to access.

In this embodiment, the device information may be extracted and set through SNMP and/or Telnet command lines. For example, acquiring all the ONU lists registered under the current OLT, activating the ONU device when charging starts, and turning off the ONU device when charging expires, which can be set by SNMP and/or Telnet command line. SNMP (simple network management protocol), an application layer protocol of the TCP/IP protocol cluster, was established in 1988 and adopted by the Internet Architecture Board (IAB) as a short-term network management solution, and has been vigorously developed in the Internet era due to its simplicity, and version SNMPv2 was released in 1992 to enhance the security and functionality of SNMPv1, and version SNMPv3 is now available. The SNMP has the advantages of high speed, simple implementation and easy understanding. When the MIB base provided by the vendor cannot be obtained, the present embodiment can implement management of the device through the Telnet command line.

The Telnet command line method is an administration tool used by the device operator, however, the inventor of the present application considers that the command line results of ONU devices of each manufacturer are different, and the difference between the command line and the output after execution is caused by the device version change, and for this difference, the manufacturer will not update the document nor notify the user in most cases.

As an implementation, the embodiment of the present invention separates the OLT device code from the script, so that the script text can be extended, added, and modified by the user. For example, please refer to fig. 2, a list of the OLT finds multiple types of ONU devices, and further, as shown in fig. 3, different scripts may be hung according to different device versions. On the basis, when a user needs to support a new device, one device can be added to the OLT Type List, and scripts for different hanging nodes are added under the device. When the hanging event occurs, the scripts are compiled and executed by code loading assembly, and the device state is influenced when the scripts are executed, for example, the ONU is registered in the OLT by adding the ONU scripts.

Each script is a set of command sets that can support variables and macros in common languages, as well as branch and loop structures, such as variables in%%, where the capitalized word is a macro. Referring to FIG. 4, the script is divided into three parts: the first part is system interaction expectation; the second part is EJS template language, the command is embedded in the template language, and variables, macros and control structures are added, including judgment of branches, circulation and the like; the third part is the macro, which currently supports only 2 macros, namely RETURN, which indicates that the output caused by this line command needs to be returned to the client, and ENTER, which indicates that an ENTER symbol is sent. Variables are key elements in EJS, and the variable forms are various and are as follows:

% script' tag for process control, no output

Delete space character before it [% ]

Outputting data to template (output is escape HTML tag)

<% -output non-escape data to template

<% # notes tag, no execution, no output content

<%% output character string '<'

% > general end tag

-% > delete the line break immediately following it

% > delete space character after end tag

The control structure includes a judgment and loop, such as if else for, etc., in a syntax that is completely consistent with the JS language.

As an example, please refer to fig. 5, where the device management method according to the embodiment of the present invention includes the following steps:

loading: loading a parameter object, a script and a callback combination;

loading parameter objects: each script allows to provide a parameter object of options, the format requirement is json, and the content is determined according to the specific script;

loading a script: adding a specific script from a database by specifying the name of the script;

loading callback combinations: each script allows to provide a callback combination, the callback combination is a group of callbacks, and when the script needs to return a captured output text and a corresponding callback function exists in the step, the text content is returned in a callback mode;

compiling to generate an executable script: the method is characterized in that the method is expanded into a command array by combining scripts and parameters, elements in the array are command objects, and each command object has three fields: expect, cmd, output function;

opening a telnet host to enable the OLT and the ONU equipment to establish connection, preparing data waiting by the OLT, matching data, sending a command, intercepting output and returning a result as required based on the mode;

distributing and executing the script: if a plurality of OLT host objects exist, the OLT host objects are executed concurrently, and the client is notified after the execution is completed;

returning an assembly message: when the script needs to return the captured output text and the user needs complete information, returning the text content to the ONU equipment;

and (4) macro callback assembly: when the script needs to return the captured output text and the corresponding callback function exists in the step, the text content is returned to the ONU equipment in a callback mode.

In order to more clearly illustrate the idea of the present invention, specific examples are given below as an illustration.

Example 1, please refer to fig. 6, which shows an ONU object found in the ONU Find list of the OLT, wherein the ONU object includes PonIndex, Index, SN, and State fields.

Taking this as a case, the design script is:

Username$<％＝username％>

Password:$<％＝password％>

#$configure terminal

#$show gpon onu uncfg

#$exit$RETURN

let the parameter objects of the ONU devices be:

username:zte

password:zte

promote:ZXAN

then the script is expanded into an array of commands and compiled into an executable script:

name$zte

password:$zte

ZXAN$\\r

ZXAN$en

#$config

#$show gpon onu uncfg

#$\r$function(out){msg+＝output}

in the executable script, the first part of the $ split is taken as expect, the telenet system output is waited, when the output is taken, the telnet system output is sent to the second part (namely EJS template), and if the third part has content (namely callback function), the output is sent to the callback function. The above process is circulated until the script execution is completed, finally the display ont automatic final all is executed, and the output of the command is returned to the user, for example, the user code can put out the desired result from the text, including extracting the serial number, extracting the noutype and other necessary information to the user.

Example 2, ZTE C300 already exists in the list of OLT, and at this time, support for device huabei 5680T needs to be added, because the command is different from ZTE C300, the following script can be newly written without modifying the device code, and support for the same function of the new device can be completed:

for the HUAWEI5680T, the following script can be written:

name$<％＝username％>

password:$<％＝password％>

<％＝prompt％>$ENTER

<％＝prompt％>$en

#$config

#$display ont autofind all

#$ENTER$RETURN

assume that the parametric objects are:

username:huawei

password:huawei

promote:huawei

this script is expanded into an array of commands, generating an executable script:

name$huawei

password:$huawei

huawei$\\r

huawei$en

#$config

#$display ont autofind all

#$\r$function(out){msg+＝output}

in the executable script, the first part of the $ split is taken as expect, the telenet system output is waited, when the output is taken, the second part (namely EJS template) is sent, and if the third part has content (namely callback function), the output is sent to the callback function. The above process is looped until the script execution is completed, finally the display ont automatic all is executed, and the output of the command is returned to the user. For example, the user code may provide the desired result from this text, including extracting the serial number, extracting the noutype, etc., as necessary information to the user.

According to the two examples, in the process of adding the scripts of the two ONU devices, the OLT device code can support the new functions of the two new ONU devices without any modification. Other ways of adding new functionality are the same as the above process.

Example 3

Based on the foregoing embodiments, this embodiment provides an apparatus management system, please refer to fig. 7, where the system includes an OLT and at least one ONU device connected to the OLT, where the ONU device is configured to upload information, and the information includes status information and traffic information; the OLT is used for acquiring the information; monitoring the state and flow of the ONU equipment according to the information, and carrying out charging management on an account number of a user, wherein the account number is correspondingly bound with the ONU equipment; and executing to close or activate the ONU equipment based on charging management. The OLT monitors and charges the ONU equipment, and can integrate the management and the charging of the equipment into a whole, thereby improving the management efficiency of the equipment.

Furthermore, each ONU device can be displayed by the list of the OLT, and a user can manage (such as expand, add, and modify) the script of each ONU device at the OLT end, so that even if the device version is changed, the support for the device with the changed version can be ensured.

Furthermore, a plurality of OLTs can be connected with each other, and the executable scripts of each ONU device can be executed concurrently, so that efficient device management is realized.

Example 4

As shown in fig. 8, the electronic device is a schematic structural diagram, and includes a processor 610, a memory 620, an input device 630, and an output device 640; the number of processors 610 in the electronic device may be one or more; the processor 610, memory 620, input device 630, and output device 640 in the electronic device may be connected by a bus or other means.

The processor 610 executes various functional applications of the electronic device and, namely, a device management method according to various embodiments of the present invention by executing software programs, instructions, and modules stored in the memory 620.

The memory 620 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 620 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 620 can further include memory located remotely from the processor 610, which can be connected to an electronic device through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

Example 5

From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, where the computer software product may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk, or an optical disk of a computer, and includes several instructions to enable an electronic device (which may be a mobile phone, a personal computer, a server, or a network device) to execute the device management method according to various embodiments of the present invention.

The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A device management method is applied to an OLT, and comprises the following steps:

acquiring information of ONU equipment, wherein the information comprises state information and flow information;

monitoring the state and flow of the ONU equipment according to the information, and carrying out charging management on an account of a user, wherein the account is correspondingly bound with the ONU equipment;

and executing to close or activate the ONU equipment based on the charging management.

2. The device management method according to claim 1, wherein said performing a network path shutdown or network path opening based on the charging management comprises:

performing comprehensive calculation on the recharging, charging and refunding of the account;

matching the calculation result with a preset service rule;

if the service deadline is over, the ONU equipment is automatically closed;

and if the service life of the service is prolonged, automatically activating the ONU equipment.

3. The device management method according to claim 1, wherein the information includes device information obtained by:

and extracting or setting the equipment information through an SNMP protocol and an MIB library.

4. The device management method according to claim 1, wherein the information includes device information obtained by:

acquiring a parameter object, a pre-programmed script and a preset callback function of the ONU equipment;

compiling and generating an executable script according to the parameter object, the script and the callback function;

and extracting or setting the equipment information by using the executable script.

5. The device management method according to claim 4, wherein the pre-programmed script comprises system interaction expectations, EJS templates, and macros.

6. The device management method according to claim 5, wherein the OLT establishes a connection with the ONU device via a telnet.

7. The device management method according to claim 6, wherein said compiling and generating an executable script according to the parameter object, the script and the callback function comprises:

acquiring the output of a telnet as the parameter object aiming at the system interaction expectation;

and sending the output to the EJS template and the callback function to generate an executable script.

8. A device management system, comprising: an OLT and at least one ONU device connected to the OLT,

the ONU equipment is used for uploading information, and the information comprises state information and flow information;

the OLT is used for acquiring the information; monitoring the state and flow of the ONU equipment according to the information, and carrying out charging management on an account of a user, wherein the account is correspondingly bound with the ONU equipment; and executing to close or activate the ONU equipment based on the charging management.

9. An electronic device comprising a processor and a storage medium storing a computer program, wherein the computer program, when executed by the processor, implements the device management method of any one of claims 1 to 7.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the device management method according to any one of claims 1 to 7.