CN113472821A

CN113472821A - Data acquisition and management integrated method, system, device and storage medium

Info

Publication number: CN113472821A
Application number: CN202111036870.0A
Authority: CN
Inventors: 鲁方祥
Original assignee: Chengdu Calabar Information Technology Co ltd
Current assignee: Chengdu Calabar Information Technology Co ltd
Priority date: 2021-09-06
Filing date: 2021-09-06
Publication date: 2021-10-01

Abstract

The embodiment of the specification provides a data acquisition and management integrated method, a system, a device and a storage medium, wherein the method comprises the following steps: establishing a network protocol library, wherein the network protocol library comprises at least two different network protocols; matching a network protocol corresponding to the input data from the network protocol library through a protocol adapter; collecting the input data by adopting the matched network protocol; and adopting concurrent management for the network protocol library and a plurality of protocols and protocols in the network protocol library, wherein the concurrent management comprises: based on the generic architecture, at least one identical manager or sub-management system is assigned to at least two different network protocols.

Description

Data acquisition and management integrated method, system, device and storage medium

Technical Field

The present disclosure relates to the field of data transmission, and in particular, to a method, a system, an apparatus, and a storage medium for integrating data acquisition and management.

Background

With the development of internet technology, data acquisition is an important ring in big data processing applications. Because data has characteristics such as many kinds, a large amount, various collection modes, and the like, in order to collect data of different kinds or different batches, related personnel not only need to develop a plurality of corresponding network protocols, interfaces, systems, and the like, but also need to respectively perform subsequent work such as individual management, operation and maintenance on the plurality of research and development achievements, and therefore, for the existing data collection, the defects of low collection efficiency, lack of unified and efficient management, large workload for research and development and operation and maintenance, high cost, and the like exist.

Therefore, how to better determine various types of encrypted traffic and detect abnormal traffic therein becomes an urgent problem to be solved.

Disclosure of Invention

One embodiment of the present specification provides a data acquisition and management integrated method. The data acquisition and management integrated method comprises the following steps: establishing a network protocol library, wherein the network protocol library comprises at least two different network protocols; matching a network protocol corresponding to the input data from the network protocol library through a protocol adapter; collecting the input data by adopting the matched network protocol; and adopting concurrent management for the network protocol library and a plurality of protocols and protocols in the network protocol library, wherein the concurrent management comprises: based on the generic architecture, at least one identical manager or sub-management system is assigned to at least two different network protocols.

One of embodiments of the present specification provides an integrated system for data acquisition and management, where the system includes: a suggestion module for establishing a network protocol library, the network protocol library comprising at least two different network protocols; the first matching module is used for matching the network protocol corresponding to the input data from the network protocol library through a protocol adapter; the acquisition module is used for acquiring the input data by adopting the matched network protocol; and a management module, configured to perform concurrent management on the network protocol library and a plurality of protocols and protocols in the network protocol library, where the concurrent management includes: based on the generic architecture, at least one identical manager or sub-management system is assigned to at least two different network protocols.

One of the embodiments of the present specification provides a data acquisition and management integrated device, which includes a processor, and the processor is configured to execute the method described above.

One of the embodiments of the present specification provides a computer-readable storage medium storing computer instructions, and when the computer instructions in the storage medium are read by a computer, the computer executes the method as described above.

Compared with the prior art, the data acquisition and management integrated method and the data acquisition and management integrated system provided by the embodiment of the application firstly establish the network protocol library to store a plurality of network protocols when data acquisition is carried out, and match the corresponding network protocols and the applicable versions of the network protocols for input data through the protocol adapter, so that for the acquisition of mass data, the workload and the cost of large research and development and deployment for independently developing a plurality of new network protocols are not required; and the concurrent management of the generic architecture can realize the cross and synchronous management of the network protocol library and the protocol adapter by the same person or the same sub-management system, thereby increasing the reusability and the universality of codes in each network protocol and facilitating the selection, upgrade, maintenance, modulation and other work of related persons on each network protocol.

Drawings

The present description will be further explained by way of exemplary embodiments, which will be described in detail by way of the accompanying drawings. These embodiments are not intended to be limiting, and in these embodiments like numerals are used to indicate like structures, wherein:

FIG. 1 is a schematic diagram of an application scenario of a data collection and management integrated system according to some embodiments of the present disclosure;

FIG. 2 is an exemplary flow diagram of a data collection management integration method according to some embodiments described herein;

FIG. 3 is a schematic diagram of a prior art system for collecting and managing data;

FIG. 4 is a schematic illustration of data collection and operation and maintenance management according to some embodiments of the present disclosure;

FIG. 5 is a schematic illustration of a business having input data derived by a business classification model according to some embodiments of the present description;

FIG. 6 is a block diagram of a data collection management integration system in accordance with certain embodiments of the present disclosure.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only examples or embodiments of the present description, and that for a person skilled in the art, the present description can also be applied to other similar scenarios on the basis of these drawings without inventive effort. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.

It should be understood that "system", "apparatus", "unit" and/or "module" as used herein is a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, other words may be substituted by other expressions if they accomplish the same purpose.

As used in this specification and the appended claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are intended to be inclusive in the plural, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.

Flow charts are used in this description to illustrate operations performed by a system according to embodiments of the present description. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, the various steps may be processed in reverse order or simultaneously. Meanwhile, other operations may be added to the processes, or a certain step or several steps of operations may be removed from the processes.

Fig. 1 is a schematic view of an application scenario of a data acquisition and management integrated system according to some embodiments of the present disclosure.

In some embodiments, the data collection and management integrated system 100 may be applied to one or more of an internet service, a traffic service system, a map service system, a navigation system, a transportation system, a financial service system, and the like. For example, the data collection and management integrated system 100 may be applied to an online service platform that provides internet services. For example, the data collection and management integrated system 100 may be applied to a platform for providing home appliance manufacturing services. Specifically, the data collection and management integrated system 100 may be an online service platform, and includes a server 110, a network 120, a terminal 130, and a server 140. The server 110 may include a processing device 112.

In some embodiments, server 110 may be used to process information and/or data related to network services. The server 110 may be a stand-alone server or a group of servers. The set of servers can be centralized or distributed (e.g., server 110 can be a distributed system). In some embodiments, the server 110 may be regional or remote. Server 110 may access information and/or material stored in terminals 130, server 140 via network 120. Server 110 may be directly connected to terminals 130, server 140 to access information and/or material stored therein. Server 110 may also receive traffic data that terminal 130 accesses over network 120. In some embodiments, the server 110 may execute on a cloud platform. For example, the cloud platform may include one or any combination of a private cloud, a public cloud, a hybrid cloud, a community cloud, a decentralized cloud, an internal cloud, and the like. In some embodiments, the server 110 may be an Internet Data Center (IDC).

In some embodiments, the server 110 may include a processing device 112. The processing device 112 may process data and/or information related to network services. In some embodiments, the processing device 112 may perform one or more of the functions described herein. For example, the processing device 112 may perform one or more functions of the network traffic decision system 100. In some embodiments, the processing device 112 may include one or more sub-processing devices (e.g., a single core processing device or a multi-core processing device). By way of example only, the processing device 112 may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction Processor (ASIP), a Graphics Processor (GPU), a Physical Processor (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a programmable logic circuit (PLD), a controller, a micro-controller unit, a Reduced Instruction Set Computer (RISC), a microprocessor, or the like, or any combination thereof.

Network 120 may facilitate the exchange of data and/or information. In some embodiments, one or more components (e.g., server 110, terminal 130, server 140) in the data collection management integration system 100 may send data and/or information to other components in the data collection management integration system 100 via the network 120. In some embodiments, the network 120 may be any type of wired or wireless network. For example, network 120 may include a cable network, a wired network, a fiber optic network, a telecommunications network, an intranet, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Public Switched Telephone Network (PSTN), a bluetooth network, a ZigBee network, a Near Field Communication (NFC) network, a cellular network, the like, or any combination thereof. In some embodiments, network 120 may include one or more network access points. For example, the network 120 may include wired or wireless network access points, such as base stations and/or Internet switching points 1020-1, 1020-2, …, through which one or more components of the data collection and management integrated system 100 may connect to the network 120 to exchange data and/or information. In some embodiments, network 120 may include one or more network devices. Network devices may include, but are not limited to, firewalls, routers, gateways, switches, hubs, bridges, reverse proxies, proxy servers, security devices, intrusion detection devices, load balancers, and the like, or similar devices. In some embodiments, traffic data sent by terminal 130 may be transmitted to server 110 via one or more network devices in network 120. In some embodiments, one or more network devices in network 120 may perform certain operations on the traffic data (e.g., allow access, disallow access, flag, intercept, clear, etc.).

In some embodiments, the user of terminal 130 may be any person or machine, etc. In some embodiments, the terminal 130 may include one or any combination of a mobile device 130-1, a tablet computer 130-2, a laptop computer 130-3, an in-vehicle device 130-4, and the like. In some embodiments, the mobile device 130-1 may include a wearable device, a smart mobile device, a virtual reality device, an augmented reality device, and the like, or any combination thereof. In some embodiments, the wearable device may include a smart bracelet, smart footwear, smart glasses, smart helmet, smart watch, smart clothing, smart backpack, smart accessory, or the like, or any combination thereof. In some embodiments, the smart mobile device may comprise a smart phone, a Personal Digital Assistant (PDA), a gaming device, a navigation device, a POS device, and the like, or any combination thereof. In some embodiments, the metaverse device and/or the augmented reality device may include metaverse helmets, metaverse glasses, metaverse eyewear, augmented reality helmets, augmented reality glasses, augmented reality eyewear, and the like, or any combination thereof. In some embodiments, the in-vehicle device 1030-4 may include an in-vehicle navigator, an in-vehicle locator, a tachograph, and the like, or any combination thereof. In some embodiments, terminal 130 may include a location-enabled device to determine the location of the user and/or terminal 130. In some embodiments, the terminal 130 may send traffic data to the server 110.

Server 140 may store data and/or instructions. In some embodiments, the server 140 may store the profile retrieved from the terminal 130. In some embodiments, server 140 may store information and/or instructions for execution or use by server 110 to perform the example methods described herein. In some embodiments, server 140 may store traffic classification models, feature extraction rules, feature decision rules, and the like. In some embodiments, server 140 may also store traffic to be determined, determined traffic, unknown traffic, and the like. In some embodiments, the server 140 may include mass storage, removable storage, volatile read-and-write memory (e.g., random access memory, RAM), read-only memory (ROM), the like, or any combination thereof. In some embodiments, the server 140 may be implemented on a cloud platform. For example, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a decentralized cloud, an internal cloud, and the like, or any combination thereof.

In some embodiments, the server 140 may be connected to the network 120 to communicate with one or more components of the data collection management integration system 100 (e.g., the server 110, the terminal 130, etc.). One or more components of the data collection management integration system 100 may access data or instructions stored in the server 140 via the network 120. For example, server 110 may invoke traffic classification models, feature extraction rules, feature decision rules, etc. from server 140. In some embodiments, the server 140 may be directly connected to or in communication with one or more components (e.g., the server 110, the terminal 130) in the data collection management integration system 100. In some embodiments, server 140 may be part of server 110.

FIG. 2 is an exemplary flow diagram of a data collection management integration method according to some embodiments described herein; FIG. 3 is a diagram 300 of a prior art system for acquiring and managing operations and maintenance of data; FIG. 4 is a diagram 400 illustrating the collection and operation and maintenance management of data according to some embodiments of the present description.

As shown in fig. 2, the process 200 includes the following steps. In some embodiments, the process 200 may be performed by the processor 112.

Step 210, a network protocol library is established. In some embodiments, step 210 may be performed by setup module 610.

A network protocol library refers to a repository storing one or more network protocols. In some embodiments, the network protocol library may include at least two different network protocols. In some embodiments, the network protocols may include standard network protocols (e.g., HTTPS, HTTP, FTP, SMTP, SSH, NTP, SDP, POP3, etc.), as well as custom network protocols.

In some embodiments, the establishing module 610 may obtain and integrate a plurality of network protocols to form the network protocol library including the plurality of network protocols. In some embodiments, the plurality of network protocol types may include at least one of a standardized network protocol, a service platform network protocol, and a customized network protocol. For example only, a certain household appliance manufacturing platform wants to diagnose an industrial prospect by data acquisition, and needs to mainly acquire downstream sales data and upstream raw material purchasing data of the platform, so the establishing module 610 may acquire network protocols corresponding to the two types of data and centrally store the network protocols in a network protocol library.

In some embodiments, the establishing module 610 may also obtain and store a network protocol under development, so that a corresponding developer may continue to develop the network protocol according to the current stored data.

And step 220, matching the network protocol corresponding to the input data from the network protocol library through the protocol adapter. In some embodiments, step 220 may be performed by the first matching module 620.

According to the foregoing, the input data has a corresponding network protocol. In some embodiments, the protocol adapter may match a network protocol corresponding to the input data from a library of network protocols. For example, for input data a and B, the protocol adapters may match the corresponding network protocols a and B for both, respectively. In some embodiments, the protocol adapter may also match the applicable version of the corresponding network protocol for the input data. For example, for input data a, the protocol adapter may match the 1.1.0 version of network protocol a for the input data; for incoming data B, the protocol adapter may match the 1.3.2 version of network protocol B for the incoming data.

In some embodiments, the protocol adapter can configure a specific protocol packet already existing in the network protocol library directly to the access code block of the new system, set the dependent packet, and only need to write the boundary code, configure the network server and the IP port address.

In some embodiments, the network protocol corresponding to the input data may also be obtained through a machine learning model. For more details on the network protocol for which the machine learning model derives input data, reference may be made to fig. 5 and its associated description.

Through the mode, when data are collected, the corresponding network protocol and the corresponding network protocol version are matched from the network protocol library only through the protocol adapter for input data, and the corresponding network protocol is not required to be re-developed, so that the direct and independent network protocol configuration effect is realized, and the workload and the cost of data collection and research and development can be greatly reduced.

Step 230, collecting the input data by using the matched network protocol. In some embodiments, step 230 may be performed by acquisition module 630.

In some embodiments, the collection module 630 may collect the input data using a matching network protocol. Continuing with the foregoing example, for a home appliance manufacturing platform that desires to collect downstream sales data, collection module 630 can collect according to a network protocol that matches the collected downstream sales data.

Step 240, adopting concurrent management for the network protocol library and a plurality of protocols and protocols in the network protocol library. In some embodiments, step 240 may be performed by management module 640.

As shown in fig. 3, for data acquisition of different service systems (e.g., a home appliance manufacturing service system and a traffic service system), different research and development personnel need to perform operations such as early development, deployment, debugging and later operation and maintenance on corresponding network protocols. That is, different business systems need to correspond to different research and development personnel and/or management systems, and there are many disadvantages. For example, the tuning-away and missing of the research and development personnel results in the loss of the technology stack, the incapability of cross maintenance and assisted maintenance by other personnel, and the need of re-cultivating new responsible personnel; aiming at the requirement of developing a plurality of new network protocols for mass data, the workload of development, operation and maintenance is large, and the cost is high.

In some embodiments, concurrent management may include: based on the generic architecture, at least one identical manager or sub-management system is assigned to at least two different network protocols. Because a large number of developed or developing network protocols are stored in the network protocol library and the network protocols are managed through the generic architecture, the reusability and the universality of codes in each network protocol can be increased, and the network protocols can be conveniently selected, upgraded, maintained, modulated and the like by related personnel.

As shown in fig. 4, in some embodiments, the developer a and the developer B may be arranged to jointly manage the network protocol library, and the developer a may be arranged to manage the protocol adapter. Therefore, the same person or the same sub-management system can simultaneously manage the network protocol library and the protocol adapter, so that the network protocol library can be managed in a cross-concurrent mode, and the defects of the existing management mode in the figure 3 are overcome.

In some embodiments, the analysis module of the system 100 may analyze the input data to obtain a processing policy for the input data; the processing policy includes at least one of: allowing collection, disallowing collection, terminating collection, reporting, alarming, marking and reporting exception. For example, for input data that is analyzed to result in input data that is unsafe or has a low security level, the analysis module may generate one or more of a processing policy for the input data that does not allow collection, terminates collection, or alarms, etc.

It should be noted that the above description related to the flow 200 is only for illustration and description, and does not limit the applicable scope of the present specification. Various modifications and alterations to flow 200 will be apparent to those skilled in the art in light of this description. However, such modifications and variations are intended to be within the scope of the present description.

FIG. 5 is a diagram 500 illustrating a business having input data obtained via a business classification model according to some embodiments of the present description.

In some embodiments, the system 100 may obtain the business corresponding to the input data through a business classification model. The business can produce products and services for enterprises by applying scientific methods and production processes, wherein the products and services can be delivered to users for use. By way of example only, the services may include, but are not limited to, financial services, network appointment services, shared-bicycle services, designated-drive services, public transportation services, navigation services, vehicle marketing services, express services, network security services, and the like.

In some embodiments, the traffic classification model may be a trained machine learning model. By way of example only, the traffic classification model may include, but is not limited to, a combination of one or more of a neural network model, a support vector machine model, a k-nearest neighbor model, a decision tree model, and the like. The neural network model may include one or more of a Convolutional Neural Network (CNN), a Recurrent Neural Network (RNN), a multilayer neural network (MLP), a ballistic neural network (GAN), and the like. In some embodiments, the traffic classification model may include a neural network layer and a classification result output layer. The input of the neural network output layer can be input data, and the output can be a vector of the input data; the input of the classification result output layer may be a vector of input data and the output may be a corresponding classification result. In some embodiments, the classification result output by the traffic classification model may be: the input data corresponds to a certain traffic probability. In some embodiments, the traffic classification model may determine that the input data belongs to a certain traffic type when the probability that the input data belongs to the traffic type is greater than a set threshold (e.g., 0.5, 0.6, 0.8, etc.).

In some embodiments, the system 100 may obtain a plurality of corresponding sets of samples, the corresponding sets of samples including the input data and their corresponding business tags. The service label may be automatically labeled based on historical representation of the input data (e.g., which service the input data ultimately visits), or may be obtained by manual labeling. The system 100 may train a machine learning model using the corresponding set of multiple samples to obtain a trained business decision model.

Through the mode, the business classification model is a machine learning model, so that the business classification model has strong data processing, analyzing and calculating capabilities, and the business classification model can improve the effect of model performance by updating model parameters through iterative training, so that the business classification of input data can be more accurately obtained through the business classification model, and the accuracy of a subsequent network protocol for matching the input data according to the business classification is improved.

In some embodiments, the system 100 may match the corresponding network protocol for the input data according to the service. For more details on matching incoming data with a corresponding network protocol according to a service, reference may be made to fig. 2 and its associated description.

FIG. 6 is an exemplary block diagram 600 illustrating data collection management integration according to some embodiments of the present description.

In some embodiments, the system 100 may include: a suggestion module for establishing a network protocol library, the network protocol library comprising at least two different network protocols; the first matching module is used for matching the network protocol corresponding to the input data from the network protocol library through a protocol adapter; the acquisition module is used for acquiring the input data by adopting the matched network protocol; and a management module, configured to perform concurrent management on the network protocol library and a plurality of protocols and protocols in the network protocol library, where the concurrent management includes: based on the generic architecture, at least one identical manager or sub-management system is assigned to at least two different network protocols.

In some embodiments, the setup module may be further configured to: acquiring and integrating a plurality of network protocols to form the network protocol library containing the plurality of network protocols; the types of the plurality of network protocols comprise at least one of a standardized network protocol, a network protocol of a service platform and a customized network protocol.

In some embodiments, the system 100 may further include an analysis module, which may be configured to analyze the input data to obtain a processing policy for the input data; the processing policy includes at least one of: allowing collection, disallowing collection, terminating collection, reporting, alarming, marking and reporting exception.

In some embodiments, the system 100 may further comprise: the acquisition module can be used for acquiring the service corresponding to the input data through a service classification model; and the second matching module can be used for matching the corresponding network protocol for the input data according to the service.

It should be understood that the system and its modules shown in FIG. 6 may be implemented in a variety of ways. It should be noted that the above descriptions of the candidate item display and determination system and the modules thereof are only for convenience of description, and the description is not limited to the scope of the illustrated embodiments. It will be appreciated by those skilled in the art that, given the teachings of the present system, any combination of modules or sub-system configurations may be used to connect to other modules without departing from such teachings. In some embodiments, the modules disclosed in fig. 6 may be different modules in a system, or may be a module that implements the functions of two or more modules described above. For example, each module may share one memory module, and each module may have its own memory module. Such variations are within the scope of the present disclosure.

Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing detailed disclosure is to be regarded as illustrative only and not as limiting the present specification. Various modifications, improvements and adaptations to the present description may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed in the present specification and thus fall within the spirit and scope of the exemplary embodiments of the present specification.

Also, the description uses specific words to describe embodiments of the description. Reference throughout this specification to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with at least one embodiment of the specification is included. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the specification may be combined as appropriate.

Additionally, the order in which the elements and sequences of the process are recited in the specification, the use of alphanumeric characters, or other designations, is not intended to limit the order in which the processes and methods of the specification occur, unless otherwise specified in the claims. While various presently contemplated embodiments of the invention have been discussed in the foregoing disclosure by way of example, it is to be understood that such detail is solely for that purpose and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements that are within the spirit and scope of the embodiments herein. For example, although the system components described above may be implemented by hardware devices, they may also be implemented by software-only solutions, such as installing the described system on an existing server or mobile device.

Similarly, it should be noted that in the preceding description of embodiments of the present specification, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to imply that more features than are expressly recited in a claim. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.

Numerals describing the number of components, attributes, etc. are used in some embodiments, it being understood that such numerals used in the description of the embodiments are modified in some instances by the use of the modifier "about", "approximately" or "substantially". Unless otherwise indicated, "about", "approximately" or "substantially" indicates that the number allows a variation of ± 20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximations that may vary depending upon the desired properties of the individual embodiments. In some embodiments, the numerical parameter should take into account the specified significant digits and employ a general digit preserving approach. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the range are approximations, in the specific examples, such numerical values are set forth as precisely as possible within the scope of the application.

For each patent, patent application publication, and other material, such as articles, books, specifications, publications, documents, etc., cited in this specification, the entire contents of each are hereby incorporated by reference into this specification. Except where the application history document does not conform to or conflict with the contents of the present specification, it is to be understood that the application history document, as used herein in the present specification or appended claims, is intended to define the broadest scope of the present specification (whether presently or later in the specification) rather than the broadest scope of the present specification. It is to be understood that the descriptions, definitions and/or uses of terms in the accompanying materials of this specification shall control if they are inconsistent or contrary to the descriptions and/or uses of terms in this specification.

Finally, it should be understood that the embodiments described herein are merely illustrative of the principles of the embodiments of the present disclosure. Other variations are also possible within the scope of the present description. Thus, by way of example, and not limitation, alternative configurations of the embodiments of the specification can be considered consistent with the teachings of the specification. Accordingly, the embodiments of the present description are not limited to only those embodiments explicitly described and depicted herein.

Claims

1. A data acquisition and management integrated method comprises the following steps:

establishing a network protocol library, wherein the network protocol library comprises at least two different network protocols;

matching a network protocol corresponding to the input data from the network protocol library through a protocol adapter;

collecting the input data by adopting the matched network protocol; and adopting concurrent management for the network protocol library and a plurality of protocols and protocols in the network protocol library, wherein the concurrent management comprises: based on the generic architecture, at least one identical manager or sub-management system is assigned to at least two different network protocols.

2. The method of claim 1, the establishing a network protocol library comprising: acquiring and integrating a plurality of network protocols to form the network protocol library containing the plurality of network protocols; the types of the plurality of network protocols comprise at least one of a standardized network protocol, a network protocol of a service platform and a customized network protocol.

3. The method of claim 1, further comprising:

analyzing the input data to obtain a processing strategy of the input data; the processing policy includes at least one of: allowing collection, disallowing collection, terminating collection, reporting, alarming, marking and reporting exception.

4. The method of claim 1, further comprising:

obtaining a service corresponding to the input data through a service classification model; and matching a corresponding network protocol for the input data according to the service.

5. A data acquisition and management integrated system comprises:

a suggestion module for establishing a network protocol library, the network protocol library comprising at least two different network protocols;

the first matching module is used for matching the network protocol corresponding to the input data from the network protocol library through a protocol adapter;

the acquisition module is used for acquiring the input data by adopting the matched network protocol; and a management module, configured to perform concurrent management on the network protocol library and a plurality of protocols and protocols in the network protocol library, where the concurrent management includes: based on the generic architecture, at least one identical manager or sub-management system is assigned to at least two different network protocols.

6. The system of claim 5, the setup module further to: acquiring and integrating a plurality of network protocols to form the network protocol library containing the plurality of network protocols;

the types of the plurality of network protocols comprise at least one of a standardized network protocol, a network protocol of a service platform and a customized network protocol.

7. The system of claim 5, further comprising:

the analysis module is used for analyzing the input data to obtain a processing strategy of the input data; the processing policy includes at least one of: allowing collection, disallowing collection, terminating collection, reporting, alarming, marking and reporting exception.

8. The system of claim 5, further comprising:

the acquisition module is used for acquiring the business corresponding to the input data through a business classification model; and the second matching module is used for matching the corresponding network protocol for the input data according to the service.

9. A data acquisition device comprising a processor for performing the data acquisition management integration method of any one of claims 1-4.

10. A computer-readable storage medium storing computer instructions which, when read by a computer, cause the computer to perform the data acquisition method of any one of claims 1 to 4.