WO2018149221A1 - 一种设备管理方法及网管系统 - Google Patents

一种设备管理方法及网管系统 Download PDF

Info

Publication number
WO2018149221A1
WO2018149221A1 PCT/CN2017/116993 CN2017116993W WO2018149221A1 WO 2018149221 A1 WO2018149221 A1 WO 2018149221A1 CN 2017116993 W CN2017116993 W CN 2017116993W WO 2018149221 A1 WO2018149221 A1 WO 2018149221A1
Authority
WO
WIPO (PCT)
Prior art keywords
cluster
cluster server
service
identifier
node identifier
Prior art date
Application number
PCT/CN2017/116993
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 WO2018149221A1 publication Critical patent/WO2018149221A1/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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • 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
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • 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/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present invention relates to the field of computer technologies, and in particular, to a device management method and a network management system.
  • the monitoring and management system of the service device performs centralized monitoring and management for a large number of service devices, and monitors the uplink and downlink of service devices, alarm status of service devices, running status, service data collection, or network quality status of service devices.
  • the monitoring and management system of the service device performs centralized monitoring and management for a large number of service devices, and monitors the uplink and downlink of service devices, alarm status of service devices, running status, service data collection, or network quality status of service devices.
  • the processing capacity of the network management system is also becoming higher and higher, and it is increasingly difficult for a single machine to be processed.
  • To meet the monitoring and management requirements of a large number of service devices it has become one of the top tasks of the stable operation of the network management system by building network management clusters for multiple machines to improve network management processing capabilities.
  • the present invention provides a device management method and a network management system for improving management efficiency of a service device.
  • an embodiment of the present invention provides a device management method, including:
  • the network management system receives the service request of the service device
  • the network management system obtains the cluster node identifier from the service request, the service request is distributed to the cluster server corresponding to the cluster node identifier in the cluster server group;
  • the network management system processes the service request by using a cluster server corresponding to the cluster node identifier.
  • the cluster node identifier includes a primary cluster node identifier and a standby cluster node identifier.
  • the network management system distributes the service request to the cluster server corresponding to the cluster node identifier in the cluster server group, including:
  • the network management system determines that the cluster server corresponding to the primary cluster node identifier is available, the network service system distributes the service request to the cluster server corresponding to the primary cluster node identifier;
  • the network management system determines that the cluster server corresponding to the primary cluster node identifier is unavailable and determines that the cluster server corresponding to the standby cluster node identifier is available, the service request is distributed to the cluster server corresponding to the standby cluster node identifier. .
  • the network management system acquires the service device identifier in the service request, if the cluster node identifier is not obtained from the service request;
  • the network management system searches for the cluster node identifier corresponding to the service device identifier by using the total control cluster server in the cluster server group, where the total control cluster server includes a correspondence between the service device identifier and the cluster node identifier.
  • the network server corresponding to the cluster node identifier processes the service request.
  • the network management system after the network management system processes the service request by using the cluster server corresponding to the cluster node identifier, the network management system further includes:
  • the network management system sends the corresponding relationship between the service device identifier and the cluster node identifier corresponding to the service device identifier to the service device by using the total control cluster server.
  • the cluster server is allocated to the service device by using the total control cluster server;
  • the network management system processes the service request by allocating a cluster server to the service device.
  • the network management system further includes:
  • the network management system sends the correspondence between the service device identifier and the cluster node identifier corresponding to the cluster server to the service device by using the total control cluster server.
  • the method further includes:
  • the network management system generates a delivery command, where the delivered command includes a service device identifier
  • the network management system determines, according to the correspondence between the service device identifier and the cluster server identifier, the cluster server identifier corresponding to the service device identifier in the issued command;
  • the network management system processes the issued command by using a cluster server corresponding to the determined cluster server identifier.
  • an embodiment of the present invention provides a network management system, including:
  • a requesting distribution unit configured to receive a service request of the service device; and, if the cluster node identifier is obtained from the service request, distribute the service request to the cluster server group corresponding to the cluster node identifier Cluster server
  • the service processing unit is configured to process the service request by using a cluster server corresponding to the cluster node identifier in the cluster server group.
  • the cluster node identifier includes a primary cluster node identifier and a standby cluster node identifier.
  • the request distribution unit is specifically configured to:
  • the service request is distributed to the cluster server corresponding to the primary cluster node identifier
  • the service request is distributed to the cluster server corresponding to the standby cluster node identifier.
  • the request distribution unit is further configured to: if the cluster node identifier is not obtained from the service request, obtain the service device identifier in the service request;
  • the service processing unit is further configured to: search, by using a total control cluster server in the cluster server group, a cluster node identifier corresponding to the service device identifier, where the total control cluster server includes a service device identifier and a cluster node identifier. Corresponding relationship; if the cluster node identifier corresponding to the service device identifier is successfully found, the cluster server corresponding to the cluster node identifier is used to identify the industry Request to process.
  • the service processing unit is further configured to: after the service request is processed by the cluster server corresponding to the cluster node identifier, identify the service device and the service by using the total control cluster server The corresponding relationship between the cluster node identifiers corresponding to the device identifiers is sent to the service device.
  • the service processing unit is further configured to: if the cluster node identifier corresponding to the service device identifier fails, the cluster server is allocated to the service device by using the total control cluster server; The device allocation cluster server processes the service request.
  • the service processing unit is further configured to: after the processing of the service request by the clustering server for the service device, identify, by the total control cluster server, the service device identifier and the allocated The mapping between the cluster node identifiers corresponding to the cluster server is sent to the service device.
  • the network management system further includes:
  • a command generating unit configured to generate a delivery command, where the issued command includes a service device identifier
  • a command distribution unit configured to determine, according to a correspondence between the service device identifier and the cluster server identifier, a cluster server identifier corresponding to the service device identifier in the issued command;
  • the service processing unit is further configured to process the issued command by using a cluster server corresponding to the determined cluster server identifier.
  • an embodiment of the present invention provides a network management system, including:
  • At least one processor and,
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform any of the device management of the first aspect described above method.
  • an embodiment of the present invention provides a non-transitory computer readable storage medium, where the non-transitory computer readable storage medium stores computer instructions for causing the computer to perform the first aspect described above Any of the device management methods.
  • an embodiment of the present invention provides a computer program product, the computer program product comprising a computing program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instruction When executed by a computer, the computer is caused to perform any of the device management methods of the above first aspect.
  • the network management system of the present invention receives the service request of the service device, and if the cluster node identifier is obtained from the service request, the service request is distributed to the cluster server corresponding to the cluster node identifier in the cluster server group; and the cluster node identifier is The corresponding cluster server processes the service request.
  • the present invention pre-establishes the correspondence between the service device and the cluster server.
  • the service request of the service device is distributed to the cluster server corresponding to the service device, and the cluster server performs the cluster server. Corresponding processing enables efficient management of service devices, improves the stability of the network management system, ensures uninterrupted service requests from service devices, and improves system throughput of the network management system.
  • FIG. 1 is a flowchart of a device management method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a network management system according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a network management system according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a device management method according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a device management method according to an embodiment of the present invention.
  • FIG. 6 is a network management system according to an embodiment of the present invention.
  • FIG. 7 is another network management system according to an embodiment of the present invention.
  • an embodiment of the present invention provides a device management method, where the execution entity is a network management system, including:
  • Step 101 The network management system receives a service request of the service device.
  • Step 102 If the network management system obtains the cluster node identifier from the service request, the service request is distributed to the cluster server corresponding to the cluster node identifier in the cluster server group.
  • Step 103 The network management system processes the service request by using a cluster server corresponding to the cluster node identifier.
  • a schematic diagram of a network management system includes a web console, a command distribution unit, and a cluster server group (including a master control cluster server and at least one cluster server (each cluster server) It can be called a cluster node)), requesting a distribution unit, wherein the web console is used to generate a delivery command, which is used for parameter query of a service device, restart of a service device, parameter setting of a service device, software upgrade of a service device, etc., command
  • the distribution unit may be a separate entity unit, for example, a single server integrated into a single server, or may be a master control cluster server integrated in the cluster server group, for distributing the issued commands generated by the web console to the corresponding
  • the cluster server performs corresponding processing, and the cluster server group is used to process the service request of the service device and process the command issued by the web console.
  • the network management system is connected to a plurality of service devices, and the service device is a device that needs to be managed by using the network management system, and may be, for example, a small cell (micro base station).
  • the service device is a device that needs to be managed by using the network management system, and may be, for example, a small cell (micro base station).
  • the following is a two-part description of the working process of the network management system.
  • the first part is the service request of the network management system processing device, and the second part is the command issued by the network management system.
  • the network management system receives the service request of the service device.
  • FIG. 3 it is a schematic diagram of a network management system according to an embodiment of the present invention.
  • a request distribution unit of the network management system receives a service request of a service device.
  • the service requesting unit of the network management system after receiving the service request, obtains the cluster node identifier, and the cluster node identifier is used to indicate the cluster server corresponding to the service device.
  • the request distribution unit stores a correspondence between the service device and the cluster server, that is, the service request of the service device is processed by the cluster server corresponding to the service device.
  • the request distribution unit If the request distribution unit successfully obtains the cluster node identifier from the service request, the service request is distributed to the cluster server corresponding to the acquired cluster node identifier in the cluster server group according to the correspondence between the service device and the cluster server.
  • the network management system processes the service request by using a cluster server corresponding to the cluster node identifier.
  • the request distribution unit acquires the cluster node identifier a in the service request A, and then distributes the service request A to the cluster.
  • the cluster server corresponding to the node identifier a is, for example, the cluster server 4, and then the cluster server 4 processes the service request A.
  • the service request may carry the reported file record, so the cluster server 4 can record the files.
  • Storage as shown in Figure 3, can be stored in the database, and the database can be double-backed, that is, the database also has a backup database to ensure data security.
  • the embodiment of the present invention provides the following method for processing a service request.
  • each service device corresponds to two cluster nodes (that is, each service device corresponds to two cluster servers), one of which serves as a primary cluster node and the other serves as a standby cluster node. Therefore, if the primary cluster node identifier is determined, If the cluster server is available, the service request is distributed to the cluster server corresponding to the primary cluster node identifier; if it is determined that the cluster server corresponding to the primary cluster node identifier is unavailable and the cluster server corresponding to the standby cluster node identifier is available, the service request is distributed to The cluster server corresponding to the cluster node ID.
  • the service device may be lost or deleted due to the fault or the restart, and the corresponding relationship between the service device identifier and the cluster server identifier stored in the service device may be lost or deleted. Therefore, the service request reported by the service device may not include the cluster server.
  • the identifier that is, the request distribution unit cannot obtain the cluster node identifier from the service request.
  • the request distribution unit obtains the service device identifier from the service request and forwards it to the master control cluster server in the cluster server group, and the total control cluster server
  • the cluster server identifier corresponding to each service device identifier is stored. Therefore, the total control cluster server searches for the cluster node identifier corresponding to the service device identifier.
  • the cluster server processes the service request, and the corresponding relationship between the service device identifier and the cluster node identifier corresponding to the service device identifier is sent to the service device for saving, and the service device sends the service request again. You can carry cluster server identified in the service request.
  • the master control cluster server searches for the service device.
  • the corresponding cluster node ID fails to be identified.
  • the master control cluster server allocates a cluster server to the service device, and allocates the cluster server for the service device to process the service request, and after that, the master control cluster
  • the server sends the corresponding relationship between the service device identifier and the cluster node identifier corresponding to the allocated cluster server to the service device for storage.
  • the network management system sends a command
  • the network management system generates a delivery command, where the delivery command includes the service device identifier, and the command distribution unit in the network management system determines the cluster corresponding to the service device identifier in the delivery command according to the correspondence between the service device identifier and the cluster server identifier.
  • the server identifier is then distributed by the command distribution unit to the determined cluster server, and the cluster server processes the issued command, where the command can be used for parameter query of the service device, service device restart, and service device. Parameter settings, business equipment software upgrades, etc.
  • the network management system of the present invention receives a service request of a service device, and obtains a set from a service request.
  • the group node identifier is used to distribute the service request to the cluster server corresponding to the cluster node identifier in the cluster server group; and the service request is processed by the cluster server corresponding to the cluster node identifier.
  • the embodiment of the present invention pre-establishes the correspondence between the service device and the cluster server.
  • the service request of the service device is distributed to the cluster server corresponding to the service device, and the cluster is configured by the cluster.
  • the server performs corresponding processing, which implements effective management of the service device, improves the stability of the network management system, ensures uninterrupted service requests of the service device, and improves system throughput of the network management system.
  • the device management method provided by the embodiment of the present invention is further described in detail below with reference to FIG. 4 and FIG.
  • FIG. 4 is a flowchart of a device management method according to an embodiment of the present invention, which is used to describe a process for a network management system to process a service request, and includes the following steps:
  • Step 401 Initialize: cluster server allocation, assign a primary cluster server and a standby cluster server to each service device, and save the correspondence to the database.
  • Step 402 The cluster server group is started, and the mapping relationship table between the service device and the cluster server is initialized to the cache of the primary cluster server.
  • Step 403 The service device sends a service request to the request distribution unit of the network management system.
  • Step 404 The request distribution unit acquires the cluster node identifier from the service request.
  • Step 405 The request distribution unit determines whether the cluster node identifier is acquired, and if yes, proceeds to step 406, otherwise proceeds to step 411.
  • Step 406 Obtain a cluster server status corresponding to the cluster node identifier.
  • Step 407 The request distribution unit determines whether the cluster server is in an active state.
  • Step 408 If the primary cluster server is in an active state, request the primary cluster server to be in the service request.
  • Step 409 If the primary cluster server is in the on-hook state and the standby cluster server is in the active state, requesting the standby cluster server to be in the service request.
  • Step 410 If the primary cluster server and the standby cluster server are both on-hook, return the connection. No error code.
  • Step 411 The request distribution unit sends the service device identifier to the master cluster server.
  • Step 412 The master cluster server searches for a corresponding cluster server. If not, the process goes to step 413. If yes, the process goes to step 414.
  • Step 413 The master cluster server allocates a cluster server to the service device according to the rule.
  • Step 414 The master cluster server determines a corresponding cluster server.
  • Step 415 The master cluster server sends the corresponding relationship between the service device and the cluster server to the service device in a parameter manner.
  • Step 416 The service device saves the correspondence.
  • FIG. 5 is a flowchart of a device management method according to an embodiment of the present invention, which is used to describe a process for a network management system to process a command, including the following steps:
  • Step 501 The web console generates a delivery command and sends the command to the command distribution unit.
  • Step 502 The command distribution unit distributes the issued command to each message queue.
  • Each of the cluster servers corresponds to a message queue, and is used to cache the issued commands distributed to itself.
  • Step 503 The cluster server processes the issued command of the queue transmission.
  • the command is sent to the corresponding service device. If the corresponding service device is not online, the timeout process is performed.
  • the embodiment of the present invention further provides a network management system, as shown in FIG. 6, including:
  • a request distribution unit 601 configured to receive a service request of the service device; and, if the cluster node identifier is obtained from the service request, distribute the service request to the cluster server group and correspond to the cluster node identifier Cluster server;
  • the service processing unit 602 is configured to process the service request by using a cluster server corresponding to the cluster node identifier in the cluster server group.
  • the cluster node identifier includes a primary cluster node identifier and a standby cluster node identifier.
  • the request distribution unit 601 is specifically configured to:
  • the service request is distributed to the cluster server corresponding to the primary cluster node identifier
  • the service request is distributed to the cluster server corresponding to the standby cluster node identifier.
  • the request distribution unit 601 is further configured to: if the cluster node identifier is not obtained from the service request, acquire the service device identifier in the service request;
  • the service processing unit 602 is further configured to: search, by using a total control cluster server in the cluster server group, a cluster node identifier corresponding to the service device identifier, where the total control cluster server includes a service device identifier and a cluster node identifier. Corresponding relationship; if the cluster node identifier corresponding to the service device identifier is successfully found, the service request is processed by the cluster server corresponding to the cluster node identifier.
  • the service processing unit 602 is further configured to: after the service request is processed by the cluster server corresponding to the cluster node identifier, identify the service device by using the total control cluster server The corresponding relationship between the cluster node identifiers corresponding to the service device identifiers is sent to the service device.
  • the service processing unit 602 is further configured to: if the cluster node identifier corresponding to the service device identifier fails, allocate the cluster server to the service device by using the total control cluster server; The service device allocation cluster server processes the service request.
  • the service processing unit 602 is further configured to: after the service server is allocated to the service device, process the service request, and then use the total control cluster server to identify the service device and the allocated device.
  • the corresponding relationship between the cluster node identifiers corresponding to the cluster server is sent to the service device.
  • the network management system further includes:
  • the command generating unit 603 is configured to generate a delivery command, where the delivery command includes a service device identifier knowledge
  • the command distribution unit 604 is configured to determine, according to the correspondence between the service device identifier and the cluster server identifier, the cluster server identifier corresponding to the service device identifier in the issued command;
  • the service processing unit 602 is further configured to process the issued command by using a cluster server corresponding to the determined cluster server identifier.
  • the network management system of the present invention receives the service request of the service device, and if the cluster node identifier is obtained from the service request, the service request is distributed to the cluster server corresponding to the cluster node identifier in the cluster server group; and the cluster node identifier is The corresponding cluster server processes the service request.
  • the present invention pre-establishes the correspondence between the service device and the cluster server.
  • the service request of the service device is distributed to the cluster server corresponding to the service device, and the cluster server performs the cluster server. Corresponding processing enables efficient management of service devices, improves the stability of the network management system, ensures uninterrupted service requests from service devices, and improves system throughput of the network management system.
  • an embodiment of the present invention provides a network management system including at least one processor; and a memory communicatively coupled to the at least one processor; the memory storage being executable by the at least one processor An instruction executed by the at least one processor to enable the at least one processor to perform the device management method in the above embodiments.
  • FIG. 7 is a network management system according to an embodiment of the present invention.
  • the network management system 700 includes a transceiver 701, a processor 702, a memory 703, and a bus system 704.
  • the memory 703 is used to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 703 may be a random access memory (RAM) or a non-volatile memory such as at least one disk storage. Only one memory is shown in the figure, of course, the memory can also be set to a plurality as needed. Memory 703 can also be a memory in processor 702.
  • the memory 703 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof:
  • Operation instructions include various operation instructions for implementing various operations.
  • Operating system Includes a variety of system programs for implementing various basic services and handling hardware-based tasks.
  • the device management method of the foregoing embodiment of the present invention may be applied to the processor 702 or implemented by the processor 702.
  • Processor 702 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing device management method may be completed by an integrated logic circuit of hardware in the processor 702 or an instruction in a form of software.
  • the processor 702 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or discrete hardware. Component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 703, and the processor 702 reads the information in the memory 703 and performs the following steps in conjunction with its hardware:
  • the transceiver 701 is configured to receive a service request of the service device, and if the cluster node identifier is obtained from the service request, distribute the service request to the cluster server group corresponding to the cluster node identifier.
  • Cluster server
  • the processor 702 is configured to process the service request by using a cluster server corresponding to the cluster node identifier in the cluster server group.
  • the cluster node identifier includes a primary cluster node identifier and a standby cluster node identifier
  • the transceiver 701 is specifically configured to:
  • the service request is distributed to the cluster server corresponding to the primary cluster node identifier
  • the service request is distributed to the standby cluster node. Identify the corresponding cluster server.
  • the transceiver 701 is further configured to: if the cluster node identifier is not obtained from the service request, obtain the service device identifier in the service request;
  • the processor 702 is further configured to search, by using a total control cluster server in the cluster server group, a cluster node identifier corresponding to the service device identifier, where the total control cluster server includes a service device identifier and a cluster node identifier. Corresponding relationship; if the cluster node identifier corresponding to the service device identifier is successfully found, the service request is processed by the cluster server corresponding to the cluster node identifier.
  • the processor 702 is further configured to: after the service request is processed by the cluster server corresponding to the cluster node identifier, identify the service device and the service by using the total control cluster server The corresponding relationship between the cluster node identifiers corresponding to the device identifiers is sent to the service device.
  • the processor 702 is further configured to: if the cluster node identifier corresponding to the service device identifier fails, allocate the cluster server to the service device by using the total control cluster server; The device allocation cluster server processes the service request.
  • the processor 702 is further configured to: after the service server is configured to allocate the cluster server to the service device, use the total control cluster server to identify the service device and the allocated The corresponding relationship between the cluster node identifiers corresponding to the cluster server is sent to the service device, where the corresponding relationship is stored in the memory 703.
  • the processor 702 is further configured to generate a sending command, where the sending command includes a service device identifier, and determining, according to a correspondence between the service device identifier and the cluster server identifier, the The cluster server identifier corresponding to the service device identifier; and the clustering server corresponding to the determined cluster server identifier processes the issued command.
  • the network management system of the embodiment of the present invention exists in various forms, including but not limited to:
  • Ultra-mobile personal computer equipment This type of equipment belongs to the category of personal computers, has computing and processing functions, and generally has mobile Internet access.
  • Such terminals include: PDAs, MIDs, and UMPC devices, such as the iPad.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • the present invention also provides a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the apparatus of any of the above Management method.
  • the present invention also provides a computer program product comprising a computing program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer And causing the computer to execute the device management method described in any of the above.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the device is implemented in a flow chart or Multiple processes and/or block diagrams The functions specified in one or more boxes.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Hardware Redundancy (AREA)

Abstract

本发明涉及计算机技术领域，尤其涉及一种设备管理方法及网管系统，用以提高业务设备的管理效率，包括：网管系统接收业务设备的业务请求，若从业务请求中获取到集群节点标识，则将业务请求分发至集群服务器组中与该集群节点标识对应的集群服务器；并通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。本发明通过预先建立业务设备与集群服务器之间的对应关系，当接收到业务设备的业务请求时，则将该业务设备的业务请求分发至与该业务设备对应的集群服务器，由该集群服务器进行相应的处理，从而实现了对业务设备进行有效管理，可提高网管系统的稳定性，保证业务设备的业务请求不间断，以及提高网管系统的系统吞吐量。

Description

一种设备管理方法及网管系统
本申请要求在2017年2月20日提交中华人民共和国知识产权局、申请号为201710090289.4，发明名称为“一种设备管理方法及网管系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及计算机技术领域，尤其涉及一种设备管理方法及网管系统。
背景技术
业务设备的监控网管系统是针对海量的业务设备进行集中监控管理，监控业务设备上下线、业务设备告警状态、运行状态、业务数据采集或业务设备的网络质量状态。随着网络不断扩容，业务设备的数量也越来越多，网管系统需要处理的数据量呈现几何级趋势，因此对网管系统的处理能力要求也越来越高，单台机器已经越来越难于满足大量业务设备的监控管理需求，通过对多台机器搭建网管集群提高网管处理能力已经成为网管系统稳定运行的首要任务之一。
目前，如何对通过由多个集群服务器构成的集群服务器组对业务设备进行有效地管理，还没有一种行之有效的方法。
发明内容
本发明提供一种设备管理方法及网管系统，用以提高业务设备的管理效率。
第一方面，本发明实施例提供一种设备管理方法，包括：
网管系统接收业务设备的业务请求；
所述网管系统若从所述业务请求中获取到集群节点标识，则将所述业务请求分发至集群服务器组中与所述集群节点标识对应的集群服务器；
所述网管系统通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。
可选地，所述集群节点标识包含主集群节点标识和备集群节点标识；
所述网管系统将所述业务请求分发至集群服务器组中与所述集群节点标识对应的集群服务器，包括：
所述网管系统若确定所述主集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述主集群节点标识对应的集群服务器；
所述网管系统若确定所述主集群节点标识对应的集群服务器不可用且确定所述备集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述备集群节点标识对应的集群服务器。
可选地，所述网管系统若从所述业务请求中未获取到集群节点标识，则获取所述业务请求中的业务设备标识；
所述网管系统通过所述集群服务器组中的总控集群服务器查找所述业务设备标识对应的集群节点标识，所述总控集群服务器包含业务设备标识与集群节点标识之间的对应关系；
所述网管系统若成功查找到所述业务设备标识对应的集群节点标识，则通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。
可选地，所述网管系统通过所述集群节点标识对应的集群服务器对所述业务请求进行处理之后，还包括：
所述网管系统通过所述总控集群服务器将所述业务设备标识与所述业务设备标识对应的集群节点标识之间的对应关系下发至所述业务设备。
可选地，所述网管系统若查找所述业务设备标识对应的集群节点标识失败，则通过所述总控集群服务器为所述业务设备分配集群服务器；
所述网管系统通过为所述业务设备分配集群服务器对所述业务请求进行处理。
可选地，所述网管系统通过为所述业务设备分配集群服务器对所述业务请求进行处理之后，还包括：
所述网管系统通过所述总控集群服务器将所述业务设备标识与分配的所述集群服务器对应的集群节点标识之间的对应关系下发至所述业务设备。
可选地，所述方法还包括：
所述网管系统生成下发命令，所述下发命令包含业务设备标识；
所述网管系统根据业务设备标识与集群服务器标识之间的对应关系，确定所述下发命令中的业务设备标识对应的集群服务器标识；
所述网管系统通过确定的集群服务器标识对应的集群服务器对所述下发命令进行处理。
第二方面，本发明实施例提供一种网管系统，包括：
请求分发单元，用于接收业务设备的业务请求；以及，若从所述业务请求中获取到集群节点标识，则将所述业务请求分发至所述集群服务器组中与所述集群节点标识对应的集群服务器；
业务处理单元，用于通过所述集群服务器组中与所述集群节点标识对应的集群服务器对所述业务请求进行处理。
可选地，所述集群节点标识包含主集群节点标识和备集群节点标识；
所述请求分发单元，具体用于：
若确定所述主集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述主集群节点标识对应的集群服务器；
若确定所述主集群节点标识对应的集群服务器不可用且确定所述备集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述备集群节点标识对应的集群服务器。
可选地，所述请求分发单元，还用于若从所述业务请求中未获取到集群节点标识，则获取所述业务请求中的业务设备标识；
所述业务处理单元，还用于通过所述集群服务器组中的总控集群服务器查找所述业务设备标识对应的集群节点标识，所述总控集群服务器包含业务设备标识与集群节点标识之间的对应关系；若成功查找到所述业务设备标识对应的集群节点标识，则通过所述集群节点标识对应的集群服务器对所述业 务请求进行处理。
可选地，所述业务处理单元，还用于：通过所述集群节点标识对应的集群服务器对所述业务请求进行处理之后，通过所述总控集群服务器将所述业务设备标识与所述业务设备标识对应的集群节点标识之间的对应关系下发至所述业务设备。
可选地，所述业务处理单元，还用于：若查找所述业务设备标识对应的集群节点标识失败，则通过所述总控集群服务器为所述业务设备分配集群服务器；通过为所述业务设备分配集群服务器对所述业务请求进行处理。
可选地，所述业务处理单元，还用于：通过为所述业务设备分配集群服务器对所述业务请求进行处理之后，通过所述总控集群服务器将所述业务设备标识与分配的所述集群服务器对应的集群节点标识之间的对应关系下发至所述业务设备。
可选地，所述网管系统还包括：
命令生成单元，用于生成下发命令，所述下发命令包含业务设备标识；
命令分发单元，用于根据业务设备标识与集群服务器标识之间的对应关系，确定所述下发命令中的业务设备标识对应的集群服务器标识；
所述业务处理单元，还用于通过确定的集群服务器标识对应的集群服务器对所述下发命令进行处理。
第三方面，本发明实施例提供了一种网管系统，包括：
至少一个处理器；以及，
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行上述第一方面中的任一项设备管理方法。
第四方面，本发明实施例提供了一种非暂态计算机可读存储介质，所述非暂态计算机可读存储介质存储计算机指令，所述计算机指令用于使所述计算机执行上述第一方面中的任一项设备管理方法。
第五方面，本发明实施例提供了一种计算机程序产品，所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序，所述计算机程序包括程序指令，当所述程序指令被计算机执行时，使所述计算机执行上述第一方面中的任一项设备管理方法。
本发明的网管系统接收业务设备的业务请求，若从业务请求中获取到集群节点标识，则将业务请求分发至集群服务器组中与该集群节点标识对应的集群服务器；并通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。本发明通过预先建立业务设备与集群服务器之间的对应关系，当接收到业务设备的业务请求时，则将该业务设备的业务请求分发至与该业务设备对应的集群服务器，由该集群服务器进行相应的处理，从而实现了对业务设备进行有效管理，可提高网管系统的稳定性，保证业务设备的业务请求不间断，以及提高网管系统的系统吞吐量。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有特别申明，附图中的图不构成比例限制。
图1为本发明实施例提供的设备管理方法流程图；
图2为本发明实施例提供的网管系统示意图；
图3为本发明实施例提供的网管系统示意图；
图4为本发明实施例提供的设备管理方法流程图；
图5为本发明实施例提供的设备管理方法流程图；
图6为本发明实施例提供的一种网管系统；
图7为本发明实施例提供的另一种网管系统。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
下面结合说明书附图对本发明实施例作进一步详细描述。
如图1所示，本发明实施例提供一种设备管理方法，该方法执行主体为网管系统，包括：
步骤101、网管系统接收业务设备的业务请求；
步骤102、网管系统若从所述业务请求中获取到集群节点标识，则将所述业务请求分发至集群服务器组中与所述集群节点标识对应的集群服务器；
步骤103、网管系统通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。
如图2所示，为本发明实施例提供的网管系统示意图，其中，网管系统包含Web控制台、命令分发单元、集群服务器组(包含一个总控集群服务器和至少一个集群服务器(每个集群服务器可称为一个集群节点))、请求分发单元，其中，Web控制台用于生成下发命令，用于业务设备的参数查询、业务设备重启、业务设备的参数设置、业务设备软件升级等，命令分发单元可以是单独的实体单元，例如是一个集成于单独的一台服务器，或者还可以是集成于集群服务器组中的总控集群服务器，用于将Web控制台生成的下发命令分发至对应的集群服务器进行相应处理，集群服务器组用于对业务设备的业务请求进行处理以及对Web控制台的下发命令进行处理。
网管系统与多个业务设备连接，其中业务设备为需要利用网管系统进行管理的设备，例如可以是smallcell(微基站)等。
下面对于网管系统的工作过程分为两部分来介绍，第一部分为网管系统处理设备的业务请求，第二部分为网管系统下发命令。
一、网管系统处理业务请求的过程
上述步骤101中，网管系统接收业务设备的业务请求。具体地，参考图3，为本发明实施例提供的网管系统示意图，由网管系统的请求分发单元接收业务设备的业务请求。
上述步骤102中，网管系统的业务请求单元在接收到业务请求之后，从中获取集群节点标识，集群节点标识用于指示该业务设备所对应的集群服务器。
并且，请求分发单元存储有业务设备与集群服务器之间的对应关系，即业务设备的业务请求由与该业务设备对应的集群服务器进行处理。
请求分发单元若从业务请求中成功获取到集群节点标识，则根据业务设备与集群服务器之间的对应关系，将业务请求分发至集群服务器组中与获取到的集群节点标识对应的集群服务器。
上述步骤103中，网管系统通过集群节点标识对应的集群服务器对所述业务请求进行处理。
举例来说，假设业务设备1的业务请求A，其中携带有集群节点标识，例如为a，则请求分发单元获取到业务请求A中的集群节点标识a之后，将该业务请求A分发至与集群节点标识a所对应的集群服务器，例如为集群服务器4，然后由集群服务器4对该业务请求A进行处理，其中，业务请求中可携带有上报的文件记录，因而集群服务器4可对这些文件记录进行存储，如图3所示，可存储于数据库中，且该数据库可进行双备处理，即该数据库还有一个备份数据库，以保证数据的安全性。
为保证业务请求能够得到有效处理，本发明实施例提供如下方法处理业务请求。
具体地，为每个业务设备对应两个集群节点(即每个业务设备对应两个集群服务器)，其中一个作为主集群节点，另外一个作为备集群节点，因此，若确定主集群节点标识对应的集群服务器可用，则将业务请求分发至主集群节点标识对应的集群服务器；若确定主集群节点标识对应的集群服务器不可用且确定备集群节点标识对应的集群服务器可用，则将业务请求分发至 备集群节点标识对应的集群服务器。
上述步骤102中，业务设备可能由于故障或重启等原因，业务设备内部存储的业务设备标识与集群服务器标识之间的对应关系丢失或删除，因此业务设备上报的业务请求中有可能不包含集群服务器标识，即请求分发单元不能从业务请求中获取到集群节点标识，此时，由请求分发单元从业务请求中获取业务设备标识并转发至集群服务器组中的总控集群服务器，总控集群服务器中存储有每个业务设备标识所对应的集群服务器标识，因此由总控集群服务器查找业务设备标识对应的集群节点标识，若成功查找到业务设备标识对应的集群节点标识，则通过集群节点标识对应的集群服务器对业务请求进行处理，并且，由总控集群服务器将业务设备标识与业务设备标识对应的集群节点标识之间的对应关系下发至业务设备进行保存，后续该业务设备再次发送业务请求时，即可在业务请求中携带集群服务器标识。
当然，对于一些业务设备，例如是首次接入网管系统的业务设备，在总控集群服务器中也没有存储该业务设备标识与集群服务器标识之间的对应关系，因此总控集群服务器会查找业务设备标识对应的集群节点标识失败，此时，总控集群服务器将会为该业务设备分配一个集群服务器，以及由为业务设备分配集群服务器对业务请求进行处理，并且，在这之后，由总控集群服务器将所述业务设备标识与分配的集群服务器对应的集群节点标识之间的对应关系下发至业务设备进行保存。
二、网管系统发送下发命令
网管系统生成下发命令，所述下发命令包含业务设备标识，网管系统中的命令分发单元根据业务设备标识与集群服务器标识之间的对应关系，确定下发命令中的业务设备标识对应的集群服务器标识，然后由命令分发单元将该下发命令分发至确定的集群服务器，由该集群服务器对下发命令进行处理，其中，下发命令可用于业务设备的参数查询、业务设备重启、业务设备的参数设置、业务设备软件升级等。
本发明的网管系统接收业务设备的业务请求，若从业务请求中获取到集 群节点标识，则将业务请求分发至集群服务器组中与该集群节点标识对应的集群服务器；并通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。本发明实施例通过预先建立业务设备与集群服务器之间的对应关系，当接收到业务设备的业务请求时，则将该业务设备的业务请求分发至与该业务设备对应的集群服务器，由该集群服务器进行相应的处理，从而实现了对业务设备进行有效管理，可提高网管系统的稳定性，保证业务设备的业务请求不间断，以及提高网管系统的系统吞吐量。
下面结合图4和图5对本发明实施例提供的设备管理方法做进一步详细描述。
图4为本发明实施例提供的设备管理方法流程图，用于描述网管系统处理业务请求的过程，包括以下步骤：
步骤401、初始化：集群服务器分配，给每个业务设备分配一个主集群服务器和备集群服务器，并把对应关系保存到数据库。
步骤402、集群服务器组启动，把业务设备和集群服务器之间的映射关系表初始化到主集群服务器的缓存中。
步骤403、业务设备发送业务请求到网管系统的请求分发单元。
步骤404、请求分发单元从业务请求中获取集群节点标识。
步骤405、请求分发单元判断是否获取到集群节点标识，若是则转到步骤406，若否则转到步骤411。
步骤406、获取集群节点标识对应的集群服务器状态。
步骤407、请求分发单元判断集群服务器是否处于活动状态。
步骤408、若主集群服务器处于活动状态，则请求主集群服务器处于该业务请求。
步骤409、若主集群服务器处于挂机状态且备集群服务器处于活动状态，则请求备集群服务器处于该业务请求。
步骤410、若主集群服务器和备集群服务器均处于挂机状态，则返回连接 不上错误码。
步骤411、请求分发单元将业务设备标识发到主控集群服务器。
步骤412、主控集群服务器查找是否有对应的集群服务器，若没有则转到步骤413，若有则转到步骤414。
步骤413、主控集群服务器按规则为业务设备分配集群服务器。
步骤414、主控集群服务器确定对应的集群服务器。
步骤415、主控集群服务器将业务设备与集群服务器的对应关系通过参数的方式下发至业务设备。
步骤416、业务设备保存对应关系。
图5为本发明实施例提供的设备管理方法流程图，用于描述网管系统处理下发命令的过程，包括以下步骤：
步骤501、Web控制台生成下发命令，并发送至命令分发单元。
步骤502、命令分发单元将下发命令分发至各消息队列。
其中，每个集群服务器对应一个消息队列，用于缓存分发给自身的下发命令。
步骤503、集群服务器处理队列传输的下发命令。
当对应的业务设备上线时，则将下发命令进行下发至对应的业务设备；若对应的业务设备未上线，则作超时处理。
基于相同的技术构思，本发明实施例还提供一种网管系统，如图6所示，包括：
请求分发单元601，用于接收业务设备的业务请求；以及，若从所述业务请求中获取到集群节点标识，则将所述业务请求分发至所述集群服务器组中与所述集群节点标识对应的集群服务器；
业务处理单元602，用于通过所述集群服务器组中与所述集群节点标识对应的集群服务器对所述业务请求进行处理。
可选地，所述集群节点标识包含主集群节点标识和备集群节点标识；
所述请求分发单元601，具体用于：
若确定所述主集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述主集群节点标识对应的集群服务器；
若确定所述主集群节点标识对应的集群服务器不可用且确定所述备集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述备集群节点标识对应的集群服务器。
可选地，所述请求分发单元601，还用于若从所述业务请求中未获取到集群节点标识，则获取所述业务请求中的业务设备标识；
所述业务处理单元602，还用于通过所述集群服务器组中的总控集群服务器查找所述业务设备标识对应的集群节点标识，所述总控集群服务器包含业务设备标识与集群节点标识之间的对应关系；若成功查找到所述业务设备标识对应的集群节点标识，则通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。
可选地，所述业务处理单元602，还用于：通过所述集群节点标识对应的集群服务器对所述业务请求进行处理之后，通过所述总控集群服务器将所述业务设备标识与所述业务设备标识对应的集群节点标识之间的对应关系下发至所述业务设备。
可选地，所述业务处理单元602，还用于：若查找所述业务设备标识对应的集群节点标识失败，则通过所述总控集群服务器为所述业务设备分配集群服务器；通过为所述业务设备分配集群服务器对所述业务请求进行处理。
可选地，所述业务处理单元602，还用于：通过为所述业务设备分配集群服务器对所述业务请求进行处理之后，通过所述总控集群服务器将所述业务设备标识与分配的所述集群服务器对应的集群节点标识之间的对应关系下发至所述业务设备。
可选地，所述网管系统还包括：
命令生成单元603，用于生成下发命令，所述下发命令包含业务设备标 识；
命令分发单元604，用于根据业务设备标识与集群服务器标识之间的对应关系，确定所述下发命令中的业务设备标识对应的集群服务器标识；
所述业务处理单元602，还用于通过确定的集群服务器标识对应的集群服务器对所述下发命令进行处理。
本发明的网管系统接收业务设备的业务请求，若从业务请求中获取到集群节点标识，则将业务请求分发至集群服务器组中与该集群节点标识对应的集群服务器；并通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。本发明通过预先建立业务设备与集群服务器之间的对应关系，当接收到业务设备的业务请求时，则将该业务设备的业务请求分发至与该业务设备对应的集群服务器，由该集群服务器进行相应的处理，从而实现了对业务设备进行有效管理，可提高网管系统的稳定性，保证业务设备的业务请求不间断，以及提高网管系统的系统吞吐量。
基于相同的技术构思，本发明实施例提供一种网管系统，包括至少一个处理器；以及，与所述至少一个处理器通信连接的存储器；所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行上述实施例中的设备管理方法。
以一个处理器为例，图7为本发明实施例提供的网管系统，该网管系统700包括：收发器701、处理器702、存储器703和总线系统704；
其中，存储器703，用于存放程序。具体地，程序可以包括程序代码，程序代码包括计算机操作指令。存储器703可能为随机存取存储器(random access memory，简称RAM)，也可能为非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。图中仅示出了一个存储器，当然，存储器也可以根据需要，设置为多个。存储器703也可以是处理器702中的存储器。
存储器703存储了如下的元素，可执行模块或者数据结构，或者它们的子集，或者它们的扩展集：
操作指令：包括各种操作指令，用于实现各种操作。
操作系统：包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。
上述本发明实施例设备管理方法可以应用于处理器702中，或者说由处理器702实现。处理器702可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述设备管理方法的各步骤可以通过处理器702中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器702可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器703，处理器702读取存储器703中的信息，结合其硬件执行以下步骤：
收发器701，用于接收业务设备的业务请求；以及，若从所述业务请求中获取到集群节点标识，则将所述业务请求分发至所述集群服务器组中与所述集群节点标识对应的集群服务器；
处理器702，用于通过所述集群服务器组中与所述集群节点标识对应的集群服务器对所述业务请求进行处理。
可选地，所述集群节点标识包含主集群节点标识和备集群节点标识；所述收发器701，具体用于：
若确定所述主集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述主集群节点标识对应的集群服务器；
若确定所述主集群节点标识对应的集群服务器不可用且确定所述备集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述备集群节点 标识对应的集群服务器。
可选地，所述收发器701，还用于若从所述业务请求中未获取到集群节点标识，则获取所述业务请求中的业务设备标识；
所述处理器702，还用于通过所述集群服务器组中的总控集群服务器查找所述业务设备标识对应的集群节点标识，所述总控集群服务器包含业务设备标识与集群节点标识之间的对应关系；若成功查找到所述业务设备标识对应的集群节点标识，则通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。
可选地，所述处理器702，还用于：通过所述集群节点标识对应的集群服务器对所述业务请求进行处理之后，通过所述总控集群服务器将所述业务设备标识与所述业务设备标识对应的集群节点标识之间的对应关系下发至所述业务设备。
可选地，所述处理器702，还用于：若查找所述业务设备标识对应的集群节点标识失败，则通过所述总控集群服务器为所述业务设备分配集群服务器；通过为所述业务设备分配集群服务器对所述业务请求进行处理。
可选地，所述处理器702，还用于：通过为所述业务设备分配集群服务器对所述业务请求进行处理之后，通过所述总控集群服务器将所述业务设备标识与分配的所述集群服务器对应的集群节点标识之间的对应关系下发至所述业务设备，其中，所述对应关系存储于所述存储器703。
可选地，所述处理器702，还用于生成下发命令，所述下发命令包含业务设备标识；根据业务设备标识与集群服务器标识之间的对应关系，确定所述下发命令中的业务设备标识对应的集群服务器标识；以及，通过确定的集群服务器标识对应的集群服务器对所述下发命令进行处理。
本发明实施例的网管系统以多种形式存在，包括但不限于：
(1)超移动个人计算机设备：这类设备属于个人计算机的范畴，有计算和处理功能，一般也具备移动上网特性。这类终端包括：PDA、MID和UMPC设备等，例如iPad。
(2)其他具有流程调度功能的电子装置。
本领域技术人员可以理解实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
另外，本发明还提供一种非暂态计算机可读存储介质，所述非暂态计算机可读存储介质存储计算机指令，所述计算机指令用于使所述计算机执行上述任一项所述的设备管理方法。
另外，本发明还提供一种计算机程序产品，所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序，所述计算机程序包括程序指令，当所述程序指令被计算机执行时，使所述计算机执行上述任一项所述的设备管理方法。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或 多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (17)

  1. 一种设备管理方法，其特征在于，包括：
    网管系统接收业务设备的业务请求；
    所述网管系统若从所述业务请求中获取到集群节点标识，则将所述业务请求分发至集群服务器组中与所述集群节点标识对应的集群服务器；
    所述网管系统通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。
  2. 根据权利要求1所述的方法，其特征在于，所述集群节点标识包含主集群节点标识和备集群节点标识；
    所述网管系统将所述业务请求分发至集群服务器组中与所述集群节点标识对应的集群服务器，包括：
    所述网管系统若确定所述主集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述主集群节点标识对应的集群服务器；
    所述网管系统若确定所述主集群节点标识对应的集群服务器不可用且确定所述备集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述备集群节点标识对应的集群服务器。
  3. 根据权利要求1所述的方法，其特征在于，
    所述网管系统若从所述业务请求中未获取到集群节点标识，则获取所述业务请求中的业务设备标识；
    所述网管系统通过所述集群服务器组中的总控集群服务器查找所述业务设备标识对应的集群节点标识，所述总控集群服务器包含业务设备标识与集群节点标识之间的对应关系；
    所述网管系统若成功查找到所述业务设备标识对应的集群节点标识，则通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。
  4. 根据权利要求3所述的方法，其特征在于，所述网管系统通过所述集群节点标识对应的集群服务器对所述业务请求进行处理之后，还包括：
    所述网管系统通过所述总控集群服务器将所述业务设备标识与所述业务设备标识对应的集群节点标识之间的对应关系下发至所述业务设备。
  5. 根据权利要求3所述的方法，其特征在于，所述网管系统若查找所述业务设备标识对应的集群节点标识失败，则通过所述总控集群服务器为所述业务设备分配集群服务器；
    所述网管系统通过为所述业务设备分配集群服务器对所述业务请求进行处理。
  6. 根据权利要求5所述的方法，其特征在于，所述网管系统通过为所述业务设备分配集群服务器对所述业务请求进行处理之后，还包括：
    所述网管系统通过所述总控集群服务器将所述业务设备标识与分配的所述集群服务器对应的集群节点标识之间的对应关系下发至所述业务设备。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述方法还包括：
    所述网管系统生成下发命令，所述下发命令包含业务设备标识；
    所述网管系统根据业务设备标识与集群服务器标识之间的对应关系，确定所述下发命令中的业务设备标识对应的集群服务器标识；
    所述网管系统通过确定的集群服务器标识对应的集群服务器对所述下发命令进行处理。
  8. 一种网管系统，其特征在于，包括：
    请求分发单元，用于接收业务设备的业务请求；以及，若从所述业务请求中获取到集群节点标识，则将所述业务请求分发至所述集群服务器组中与所述集群节点标识对应的集群服务器；
    业务处理单元，用于通过所述集群服务器组中与所述集群节点标识对应的集群服务器对所述业务请求进行处理。
  9. 根据权利要求8所述的网管系统，其特征在于，所述集群节点标识包含主集群节点标识和备集群节点标识；
    所述请求分发单元，具体用于：
    若确定所述主集群节点标识对应的集群服务器可用，则将所述业务请求 分发至所述主集群节点标识对应的集群服务器；
    若确定所述主集群节点标识对应的集群服务器不可用且确定所述备集群节点标识对应的集群服务器可用，则将所述业务请求分发至所述备集群节点标识对应的集群服务器。
  10. 根据权利要求8所述的网管系统，其特征在于，
    所述请求分发单元，还用于若从所述业务请求中未获取到集群节点标识，则获取所述业务请求中的业务设备标识；
    所述业务处理单元，还用于通过所述集群服务器组中的总控集群服务器查找所述业务设备标识对应的集群节点标识，所述总控集群服务器包含业务设备标识与集群节点标识之间的对应关系；若成功查找到所述业务设备标识对应的集群节点标识，则通过所述集群节点标识对应的集群服务器对所述业务请求进行处理。
  11. 根据权利要求10所述的网管系统，其特征在于，所述业务处理单元，还用于：通过所述集群节点标识对应的集群服务器对所述业务请求进行处理之后，通过所述总控集群服务器将所述业务设备标识与所述业务设备标识对应的集群节点标识之间的对应关系下发至所述业务设备。
  12. 根据权利要求10所述的网管系统，其特征在于，所述业务处理单元，还用于：若查找所述业务设备标识对应的集群节点标识失败，则通过所述总控集群服务器为所述业务设备分配集群服务器；通过为所述业务设备分配集群服务器对所述业务请求进行处理。
  13. 根据权利要求12所述的网管系统，其特征在于，所述业务处理单元，还用于：通过为所述业务设备分配集群服务器对所述业务请求进行处理之后，通过所述总控集群服务器将所述业务设备标识与分配的所述集群服务器对应的集群节点标识之间的对应关系下发至所述业务设备。
  14. 根据权利要求8至13任一所述的网管系统，其特征在于，所述网管系统还包括：
    命令生成单元，用于生成下发命令，所述下发命令包含业务设备标识；
    命令分发单元，用于根据业务设备标识与集群服务器标识之间的对应关系，确定所述下发命令中的业务设备标识对应的集群服务器标识；
    所述业务处理单元，还用于通过确定的集群服务器标识对应的集群服务器对所述下发命令进行处理。
  15. 一种网管系统，其特征在于，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行权利要求1-7任一所述设备管理方法。
  16. 一种非暂态计算机可读存储介质，其特征在于，所述非暂态计算机可读存储介质存储计算机指令，所述计算机指令用于使所述计算机执行权利要求1-7任一所述设备管理方法。
  17. 一种计算机程序产品，所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序，所述计算机程序包括程序指令，当所述程序指令被计算机执行时，使所述计算机执行权利要求1-7任一所述设备管理方法。
PCT/CN2017/116993 2017-02-20 2017-12-18 一种设备管理方法及网管系统 WO2018149221A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710090289.4 2017-02-20
CN201710090289.4A CN106789362B (zh) 2017-02-20 2017-02-20 一种设备管理方法及网管系统

Publications (1)

Publication Number Publication Date
WO2018149221A1 true WO2018149221A1 (zh) 2018-08-23

Family

ID=58958366

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/116993 WO2018149221A1 (zh) 2017-02-20 2017-12-18 一种设备管理方法及网管系统

Country Status (2)

Country Link
CN (1) CN106789362B (zh)
WO (1) WO2018149221A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110008018A (zh) * 2019-01-17 2019-07-12 阿里巴巴集团控股有限公司 一种批量任务处理方法、装置及设备
CN110134546A (zh) * 2019-04-11 2019-08-16 平安科技（深圳）有限公司 批量重启windows系统方法、电子装置及存储介质
CN111538719A (zh) * 2020-04-30 2020-08-14 深圳前海微众银行股份有限公司 数据迁移方法、装置、设备及计算机存储介质
CN112968975A (zh) * 2021-03-31 2021-06-15 中国建设银行股份有限公司 服务请求的处理方法和装置
CN113766027A (zh) * 2021-09-09 2021-12-07 瀚高基础软件股份有限公司 一种流复制集群节点转发数据的方法及设备
CN114070858A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 一种数据处理方法及装置、设备、存储介质
CN114422567A (zh) * 2021-12-09 2022-04-29 阿里巴巴（中国）有限公司 数据请求的处理方法、装置、系统、计算机设备及介质
CN115001960A (zh) * 2021-03-02 2022-09-02 浙江宇视科技有限公司 一种设备自动配置部署方法及装置
CN115086333A (zh) * 2022-04-25 2022-09-20 北京达佳互联信息技术有限公司 服务请求分配方法、装置及存储介质

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106789362B (zh) * 2017-02-20 2020-04-14 京信通信系统（中国）有限公司 一种设备管理方法及网管系统
CN107729176B (zh) * 2017-09-14 2020-09-29 北京京东尚科信息技术有限公司 一种配置文件管理系统的容灾方法及容灾系统
CN107729141B (zh) * 2017-09-27 2022-06-10 华为技术有限公司 一种业务分配方法、装置和服务器
CN108683699B (zh) * 2018-03-29 2021-06-18 广州华多网络科技有限公司 转发业务请求的方法和装置
CN108809730B (zh) * 2018-06-25 2021-11-19 创新先进技术有限公司 一种机房控制切流的方法和装置
CN108829503A (zh) * 2018-06-27 2018-11-16 泰康保险集团股份有限公司 任务调度方法、装置、系统、介质和电子设备
CN109391614B (zh) * 2018-09-06 2021-09-07 视联动力信息技术股份有限公司 一种基于视联网调取监控数据的方法和装置
CN109582451A (zh) * 2018-11-21 2019-04-05 金色熊猫有限公司 任务调度方法、系统、设备以及可读介质
CN111371573B (zh) * 2018-12-25 2021-11-02 大唐移动通信设备有限公司 消息交互方法及装置
CN111464574B (zh) * 2019-01-21 2022-10-21 阿里巴巴集团控股有限公司 调用、加载、注册、管理方法和路由、服务器、节点和介质
CN110493075B (zh) * 2019-08-01 2021-06-25 京信通信系统（中国）有限公司 设备在线时长监测的方法、装置及系统
CN110750289B (zh) * 2019-10-25 2022-05-31 中电福富信息科技有限公司 一种分布式系统的灰度切换状态保持方法
CN111064786B (zh) * 2019-12-17 2022-09-20 联通物联网有限责任公司 账户标识管理方法及设备
CN113055427B (zh) * 2019-12-28 2022-12-23 浙江宇视科技有限公司 一种基于业务的服务器集群接入方法及装置
CN111181859B (zh) * 2019-12-31 2022-03-25 京信网络系统股份有限公司 网络设备的监控方法、系统、路由设备和存储介质
CN113364892B (zh) * 2020-03-04 2023-03-24 阿里巴巴集团控股有限公司 跨多集群服务的域名解析方法、相关方法、装置和系统
CN111526038B (zh) * 2020-03-26 2023-01-20 口碑(上海)信息技术有限公司 业务请求分发方法、装置、计算机设备及可读存储介质
CN111698311A (zh) * 2020-06-08 2020-09-22 星辰天合（北京）数据科技有限公司 分布式存储集群的节点控制方法及装置、电子设备
CN112000735A (zh) * 2020-08-05 2020-11-27 中国邮政储蓄银行股份有限公司 一种数据处理方法、装置、系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101083667A (zh) * 2007-07-04 2007-12-05 华为技术有限公司 通信方法、系统和网关设备
CN101453450A (zh) * 2007-12-06 2009-06-10 中国移动通信集团公司 基于客户端的ims业务实现方法及其装置和系统
CN103997526A (zh) * 2014-05-21 2014-08-20 中国科学院计算技术研究所 一种可扩展负载均衡系统和方法
CN106302611A (zh) * 2015-06-09 2017-01-04 深圳市腾讯计算机系统有限公司 业务请求分配系统、方法和装置
CN106789362A (zh) * 2017-02-20 2017-05-31 京信通信技术(广州)有限公司 一种设备管理方法及网管系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101505472B (zh) * 2008-02-05 2011-07-20 华为技术有限公司 一种用户数据服务器系统和装置
CN101677324B (zh) * 2008-09-17 2012-10-03 华为技术有限公司 业务管理方法、终端、网络系统及相关设备
CN102148850B (zh) * 2010-08-09 2014-08-06 华为软件技术有限公司 一种集群系统的业务处理方法及集群系统
CN106161511B (zh) * 2015-03-31 2020-01-21 华为技术有限公司 业务请求处理方法、相关装置及系统
CN105024855B (zh) * 2015-07-13 2018-09-04 浪潮(北京)电子信息产业有限公司 分布式集群管理系统和方法
CN106406833B (zh) * 2015-07-30 2020-09-01 北京京东尚科信息技术有限公司 一种提供数据的方法和装置
CN105357294B (zh) * 2015-10-31 2018-10-02 成都华为技术有限公司 一种存储数据的方法及集群管理节点
CN106302640A (zh) * 2016-07-27 2017-01-04 乐视控股（北京）有限公司 数据请求处理方法及装置
CN106385437A (zh) * 2016-08-31 2017-02-08 广州唯品会信息科技有限公司 集群选择方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101083667A (zh) * 2007-07-04 2007-12-05 华为技术有限公司 通信方法、系统和网关设备
CN101453450A (zh) * 2007-12-06 2009-06-10 中国移动通信集团公司 基于客户端的ims业务实现方法及其装置和系统
CN103997526A (zh) * 2014-05-21 2014-08-20 中国科学院计算技术研究所 一种可扩展负载均衡系统和方法
CN106302611A (zh) * 2015-06-09 2017-01-04 深圳市腾讯计算机系统有限公司 业务请求分配系统、方法和装置
CN106789362A (zh) * 2017-02-20 2017-05-31 京信通信技术(广州)有限公司 一种设备管理方法及网管系统

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110008018A (zh) * 2019-01-17 2019-07-12 阿里巴巴集团控股有限公司 一种批量任务处理方法、装置及设备
CN110008018B (zh) * 2019-01-17 2023-08-29 创新先进技术有限公司 一种批量任务处理方法、装置及设备
CN110134546A (zh) * 2019-04-11 2019-08-16 平安科技（深圳）有限公司 批量重启windows系统方法、电子装置及存储介质
CN111538719A (zh) * 2020-04-30 2020-08-14 深圳前海微众银行股份有限公司 数据迁移方法、装置、设备及计算机存储介质
CN111538719B (zh) * 2020-04-30 2024-04-19 深圳前海微众银行股份有限公司 数据迁移方法、装置、设备及计算机存储介质
CN114070858A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 一种数据处理方法及装置、设备、存储介质
CN115001960B (zh) * 2021-03-02 2024-04-05 浙江宇视科技有限公司 一种设备自动配置部署方法及装置
CN115001960A (zh) * 2021-03-02 2022-09-02 浙江宇视科技有限公司 一种设备自动配置部署方法及装置
CN112968975B (zh) * 2021-03-31 2023-05-09 中国建设银行股份有限公司 服务请求的处理方法和装置
CN112968975A (zh) * 2021-03-31 2021-06-15 中国建设银行股份有限公司 服务请求的处理方法和装置
CN113766027B (zh) * 2021-09-09 2023-09-26 瀚高基础软件股份有限公司 一种流复制集群节点转发数据的方法及设备
CN113766027A (zh) * 2021-09-09 2021-12-07 瀚高基础软件股份有限公司 一种流复制集群节点转发数据的方法及设备
CN114422567A (zh) * 2021-12-09 2022-04-29 阿里巴巴（中国）有限公司 数据请求的处理方法、装置、系统、计算机设备及介质
CN115086333A (zh) * 2022-04-25 2022-09-20 北京达佳互联信息技术有限公司 服务请求分配方法、装置及存储介质

Also Published As

Publication number Publication date
CN106789362B (zh) 2020-04-14
CN106789362A (zh) 2017-05-31

Similar Documents

Publication Publication Date Title
WO2018149221A1 (zh) 一种设备管理方法及网管系统
US11704144B2 (en) Creating virtual machine groups based on request
US11553034B2 (en) Server computer management system for supporting highly available virtual desktops of multiple different tenants
CN110941481A (zh) 资源调度方法、装置及系统
JP5510556B2 (ja) 仮想マシンのストレージスペースおよび物理ホストを管理するための方法およびシステム
US10686728B2 (en) Systems and methods for allocating computing resources in distributed computing
US20100138540A1 (en) Method of managing organization of a computer system, computer system, and program for managing organization
CN109379448B (zh) 一种文件分布式部署方法、装置、电子设备及存储介质
WO2021227954A1 (zh) 基于容器集群的应用访问请求处理
CN111061432B (zh) 一种业务迁移方法、装置、设备及可读存储介质
CN109416646B (zh) 一种容器分配的优化方法及处理设备
US20230342191A1 (en) Task Scheduling Method and System
EP3629160B1 (en) Method and device for managing vnf instantiation
WO2024082584A1 (zh) 资源分配方法、容器管理组件和资源分配系统
US20200272526A1 (en) Methods and systems for automated scaling of computing clusters
US8819239B2 (en) Distributed resource management systems and methods for resource management thereof
CN111338778B (zh) 任务调度方法、装置、存储介质及计算机设备
CN109005071B (zh) 一种决策部署方法和调度设备
US20160139940A1 (en) Systems and methods for creating virtual machine
CN108984105B (zh) 对网络存储设备中的复制任务进行分配的方法和设备
CN115904640A (zh) 分布式任务处理系统及方法
CN111683164A (zh) 一种ip地址的配置方法及vpn服务系统
CN113452729A (zh) 序列号确定方法、设备及存储介质
CN112052084A (zh) 一种资源分配方法和计算机设备
CN112671871B (zh) 一种镜像分发方法、装置、终端设备及存储介质

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 21.01.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17896769

Country of ref document: EP

Kind code of ref document: A1