CN113377367B

CN113377367B - Data collection method, device, computer equipment and storage medium

Info

Publication number: CN113377367B
Application number: CN202010161658.6A
Authority: CN
Inventors: 刘骏健; 郭润增; 黄东庆; 李建东; 欧霄; 崔齐
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-03-10
Filing date: 2020-03-10
Publication date: 2024-04-30
Anticipated expiration: 2040-03-10
Also published as: CN113377367A

Abstract

The application relates to a data collection method, a data collection device, computer equipment and a storage medium. The method comprises the following steps: obtaining a management system generation model; the management system generation model comprises page constraint conditions and data constraint conditions matched with system demand information; running the management system generation model to generate a corresponding management system, and providing a data collection page meeting the page constraint condition through the management system; acquiring configuration data input to the data collection page; storing the configuration data to the management system when the configuration data meets the data constraint condition; the stored configuration data is used for providing the configuration data to a service system for corresponding service processing. By adopting the method, the data collection efficiency can be improved.

Description

Data collection method, device, computer equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a data collection method, apparatus, computer device, and storage medium.

Background

With the development of computer technology, a system development technology is developed, and the system development is a process of performing software coding based on specific business requirement analysis, so as to develop an application system with at least functions of front-end interface display, back-end data processing and the like. For example, when specific business data collection is required, a corresponding management system can be developed based on development requirements to assist in the data collection process.

The traditional management system development needs to be put into front-end development and back-end development, and the process from model design, DAO/AO (DATA ACCESS Object/Application Object ) development to final acceptance and release is numerous, the development process needs to be cooperated by multiple persons and takes a long time, so that the whole processing period of data collection is long, and the efficiency is low.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a data collection method, apparatus, computer device, and storage medium capable of improving data collection efficiency.

A method of data collection, the method comprising:

obtaining a management system generation model; the management system generation model comprises page constraint conditions and data constraint conditions matched with system demand information;

Running the management system generation model to generate a corresponding management system, and providing a data collection page meeting the page constraint condition through the management system;

acquiring configuration data input to the data collection page;

Storing the configuration data to the management system when the configuration data meets the data constraint condition; the stored configuration data is used for providing the configuration data to a service system for corresponding service processing.

A data collection device, the device comprising:

the acquisition module is used for acquiring a management system generation model; the management system generation model comprises page constraint conditions and data constraint conditions matched with system demand information;

the generation module is used for running the management system generation model to generate a corresponding management system and providing a data collection page meeting the page constraint condition through the management system;

the acquisition module is also used for acquiring configuration data input to the data collection page;

The storage module is used for storing the configuration data to the management system when the configuration data meets the data constraint condition; the stored configuration data is used for providing the configuration data to a service system for corresponding service processing.

In one embodiment, the obtaining module is further configured to enter a management system to generate a page, and trigger an authentication request through the management system to generate the page; responding to the identity verification request, and collecting corresponding user identity information; and when the user identity information passes the verification, calling a management system generation model created based on the system demand information from the management system generation page.

In one embodiment, the apparatus further comprises:

The determining module is used for determining a preconfigured management system identifier, a management system name and corresponding system description information, wherein the management system name is input to a management system generation page;

The generation module is also used for operating the management system generation model and generating a corresponding management system according to the management system identification, the management system name and the corresponding system description information.

In one embodiment, the generating module is further configured to display a configuration list page through the management system; the configuration list page comprises an adding control for adding configuration records; when triggering operation acting on the adding control occurs, displaying a data collection page meeting the page constraint condition; and generating corresponding configuration records according to the stored configuration data, and adding the generated configuration records into the configuration list page.

In one embodiment, the device further comprises a display module, wherein:

The generating module is further used for generating calendar version information corresponding to each configuration record respectively based on the sequence of the collection time for collecting the configuration data through the corresponding data collection page for each configuration record;

The display module is used for displaying historical version information corresponding to the target configuration record when a version check instruction of the target configuration record occurs in the configuration list page;

The display module is also used for displaying configuration data corresponding to the target version information selected by the selected instruction according to the selected instruction acting on the calendar version information.

In one embodiment, the storage module is further configured to determine a data format corresponding to each of the configuration data; according to the data constraint conditions, verifying the validity of the data format of each configuration data; and when the validity verification is passed, storing the configuration data into the management system.

In one embodiment, the storage module is further configured to determine a page identifier of a data collection page corresponding to the configuration data and general data entered into the data collection page when the configuration data meets the data constraint condition; determining a corresponding retrieval index according to the page identifier and the general data; and storing the retrieval index and the corresponding configuration data in association with the management system.

In one embodiment, the acquiring module is further configured to acquire system requirement information, where the system requirement information includes page constraint information and data constraint information; the determining module is further used for determining page constraint conditions and data constraint conditions based on a preset data exchange language according to the page constraint information and the data constraint information; the generation module is also used for creating a management system generation model based on the page constraint condition and the data constraint condition.

In one embodiment, the apparatus further comprises a lookup module and a feedback model, wherein:

The acquisition module is also used for receiving a data call request from the service system;

the searching module is used for responding to the data calling request and searching target configuration data corresponding to the data calling request from the management system;

And the feedback module is used for feeding back the target configuration data to the service system through a data calling interface provided by the management system.

A computer device comprising a memory storing a computer program and a processor which when executing the computer program performs the steps of:

acquiring configuration data input to the data collection page;

A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

acquiring configuration data input to the data collection page;

According to the data collection method, the data collection device, the computer equipment and the storage medium, the management system generation model with the page constraint condition and the data constraint condition is directly developed according to the system demand information, and therefore the corresponding management system is directly generated in a model driving mode. And the management system can provide a data collection page matched with the system demand information to collect configuration data, and store the configuration data meeting the data constraint condition so as to provide the configuration data for the service system. Therefore, the management system with the data collection function and the data processing and storing function can be directly generated according to the management system generation model, front-end and back-end development of multi-person cooperation is not needed additionally according to development requirements, the frequency of communication coordination among a demand department, an outsourcing unit and developers in the development process is reduced, the development efficiency of the management system is greatly improved, and further the processing efficiency of data collection through the management system is greatly improved.

Drawings

FIG. 1 is a diagram of an application environment for a data collection method in one embodiment;

FIG. 2 is a flow diagram of a method of data collection in one embodiment;

FIG. 3 is a schematic diagram of an interface for a management system to generate pages in one embodiment;

FIG. 4 is an interface diagram of a configuration list page in one embodiment;

FIG. 5 is a schematic interface diagram of a data collection page in one embodiment;

FIG. 6 is a diagram of an interface for viewing historical version information in one embodiment;

FIG. 7 (a) is a schematic diagram of a data collection method in one embodiment;

FIG. 7 (b) is a schematic diagram of a splice for keys in one embodiment;

FIG. 8 (a) is a schematic diagram of a scenario of a data collection method in one embodiment;

FIG. 8 (b) is a schematic diagram of the generation of a management system in one embodiment;

FIG. 9 is a block diagram of a data collection device in one embodiment;

FIG. 10 is a block diagram of a data collection device in another embodiment;

FIG. 11 is an internal block diagram of a computer device in one embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

The data collection method provided by the application can be applied to an application environment shown in figure 1. Wherein the terminal 102 communicates with the server 104 via a network. The terminal 102 acquires a management system generation model; the management system generation model includes page constraints and data constraints that match the system demand information. The terminal 102 runs the management system generation model to generate a corresponding management system and provides a data collection page satisfying the page constraint condition through the management system. The terminal 102 obtains configuration data entered into the data collection page. When the configuration data satisfies the data constraint, the terminal 102 stores the configuration data to the management system, which may be specifically stored in a database provided in the background of the management system, that is, the server 104. The stored configuration data is used for being provided to a service system to perform corresponding service processing. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smartphones, tablet computers, and portable wearable devices, and the server 104 may be implemented by a stand-alone server or a server cluster composed of a plurality of servers.

In one embodiment, as shown in fig. 2, a data collection method is provided, and the method is applied to the terminal in fig. 1 for illustration, and includes the following steps:

Step S202, obtaining a management system generation model; the management system generation model includes page constraints and data constraints that match the system demand information.

Wherein the management system generation model is a data model for describing specific data conforming to the communication protocol, and can be regarded as an abstract, constraint-based description language which can be recognized by the computer device. The specific data may be JSON data, and the corresponding management system model may be a data model constructed based on JSON Schema. The management system model can specifically build a user interface through a JSON mode, and collect and process data in the user interface. Wherein, JSON Schema defines a set of words and rules that are used to define JSON metadata, and the metadata is also expressed in the form of JSON data. JSON metadata defines specifications that JSON data needs to satisfy, including members, structures, types, constraints, and the like. JSON metadata is data for describing attribute information of data to be collected.

The system requirement information is requirement information for developing the management system, and is used for describing specific display functions and processing functions which the management system to be developed needs to have. For example, the system requirement information may be specifically that the management system may be used to collect configuration information such as text, picture or link address, and may perform functions such as data conversion and storage on the configuration information.

The page constraint condition is a constraint rule for limiting a data collection page automatically displayed by the management system generation model, and specifically may be a page layout rule, a page display size, or a page element category limitation of the data collection page. Where a page element is a data object in a page, such as a word, picture, table, or text box, etc. The page local rule may be a typesetting rule of each page element, for example, a display interval between different page elements, a line interval in the data collection page, and a position where each page element is displayed in the data collection page. The page presentation size may specifically be a length-width size of the display page. The page element category definitions may specifically be which categories of page elements, such as text categories, picture categories, and form categories, may be displayed by the generated data collection page. It will be appreciated that page constraints are used to define the presentation rules of the data collection page, i.e. what effect the data collection page specifically presents at presentation.

The data constraint condition is a rule for defining legal data that can be collected by the data collection page, and specifically may be a data format rule of data that can be collected by the data collection page, for example, a data type or a data length of configuration data collected by the data collection page. The data type may be a string type, a numeric type, an object type, an array type, a boolean type, a NULL type, or the like. The data length is in particular the byte length of the configuration data. It will be appreciated that the data constraints are used to define the formatting rules required for the configuration data to be collected, i.e. what effect the configuration data specifically exhibits at presentation time.

Specifically, when the demand department has a data collection demand, the developer can communicate specific system demand information with the demand department. And then the developer develops a system generation model according to specific system demand information. The terminal can directly search the management system generation model from the local storage medium according to the management system identification. Or the terminal may acquire a link address directed to the management system generation model, through which the management system generation model is acquired. Wherein the management system identifier is used for uniquely identifying one management system, and can be a character string comprising at least one character of numbers, letters and symbols.

In one embodiment, the terminal may obtain a web address pointing to a management system generation page and enter the management system generation page according to the web address. A management system generation model is embedded in the management system generation page, and the terminal can directly acquire the management system generation model. Or a link address pointing to the management system generation model may be displayed in the management system generation page, and the user may download the management system generation model by clicking on the link address.

In one embodiment, the data collection method further includes a creation step of a management system generation model, the step specifically including: acquiring system demand information, wherein the system demand information comprises page constraint information and data constraint information; determining page constraint conditions and data constraint conditions based on a preset data exchange language according to the page constraint information and the data constraint information; the creation management system generates a model based on the page constraints and the data constraints.

The page constraint information is information for constraining a data collection page to be generated, and comprises page layout information, page display size information, page element category information and the like. The data constraint information is information for constraining configuration data to be collected, and includes information such as data type or data length. The preset exchange language is a programming language, is easy to read and write by a person, is easy to analyze and generate by a machine, and can be particularly an ISON (JavaScript Object Notation JavaScript object notation) language.

Specifically, the developer can communicate the system requirements with the product operators, and further determine page constraint information and data constraint information matched with the system requirements. The terminal may further obtain a prompt message describing the configuration data to be collected, where the prompt message may specifically be a title (title) of the configuration data to be collected, and is used to prompt the user about which type of configuration information needs to be filled in. Such as "name" is used to prompt the user to fill in the user's name at the corresponding location. Furthermore, the developer can write corresponding codes through the terminal according to the standard of the preset exchange language based on the page constraint information and the data constraint information or also based on the prompt information so as to determine corresponding page constraint conditions and data constraint conditions. Furthermore, the terminal can jointly construct each page constraint condition and each data constraint condition according to the standard of the preset exchange language so as to form a management system generation model. It will be appreciated that the content of the hint information mentioned above will be used as metadata in the management system model when constructing the management system generation model.

In the above embodiment, the page constraint condition and the data constraint condition may be constructed according to the standard of the preset data exchange language based on the system demand information in advance, and then the management system generation model may be created based on the page constraint condition and the data constraint condition, and the management system generation model may be directly used to generate the management system meeting the demand. Therefore, the system can be realized only by communicating the system requirements of the developer and the product operators, the frequency of multiparty communication is greatly reduced, and the generation efficiency of the management system is improved.

In step S204, the operation management system generates a model to generate a corresponding management system, and provides a data collection page satisfying the page constraint condition through the management system.

Specifically, after the terminal obtains the management system generation model, the terminal may directly run the management system generation model to generate a corresponding management system. It is understood that the management system herein refers to a system with complete functions of both the front end and the back end. The front-end function is complete, namely, the management system can provide a page displayed to a user, such as a data collection page mentioned in the embodiment of the application, and the user can edit and data enter through the page. The complete back-end function means that the management system has a data processing capability of the background, for example, operations such as data verification, format conversion, data storage or data searching can be performed on configuration data collected by the front end. The management system can be specifically realized by the current terminal alone or by the current terminal and the corresponding server together.

In one embodiment, the terminal can directly generate and display the corresponding data collection page according to the page constraint condition by running and compiling the management system generation model. In a particular embodiment, the collection page may be a form through which a user may enter data.

In one embodiment, the data collection page displays prompt information and an editing control corresponding to the prompt information, wherein the editing control is used for inputting configuration data. The editing control may specifically be a text entry box, a tab box, or an image insert button, etc.

Step S206, acquiring configuration data input to a data collection page.

Wherein the configuration data is target data to be collected, and the configuration data is collected effective data about specific services required by a party who puts forward system demand information. Specifically, the terminal may display a data collection page, and the user may input configuration data according to the prompt information through the input device according to the data collection page. When the terminal detects the triggering operation acting on the determination control, the terminal can directly acquire the configuration data input into the data collection page. The input device may be a built-in input device of the terminal, or an input device provided by an external input device, such as a keyboard, a mouse, or a handwriting board. The determination control is a control for indicating that the current input operation is completed and performing the uploading operation. The triggering operation can be specifically touch operation, cursor operation, key operation or voice operation. The touch operation can be a touch click operation, a touch press operation or a touch slide operation, and the touch operation can be a single-point touch operation or a multi-point touch operation; the cursor operation may be an operation of controlling the cursor to click or an operation of controlling the cursor to press; the key operation may be a virtual key operation or a physical key operation, etc.

In one embodiment, a user can input data in the data collection page through the input device, and the terminal can acquire the configuration data input through the input device and automatically detect whether the data format of the configuration data meets the preset data constraint condition. Only data meeting the data constraint conditions can be collected and stored by the data collection page; data that does not meet the data constraint may be rejected, and may be misplaced or automatically cleared after entry.

Step S208, when the configuration data meets the data constraint condition, storing the configuration data to a management system; the stored configuration data is used for providing to the business system for corresponding business processing.

Specifically, after the terminal acquires the configuration data, the terminal may send the configuration data locally or to a system background (system background, such as implemented by a server) to perform data verification. The terminal or the server can verify the data format of the configuration data through the data constraint condition, and when the data format of the configuration data meets the data constraint condition, the terminal can store the configuration data into the management system. The configuration data may be stored locally in the terminal or sent to a server, where the server stores the configuration data in a corresponding database, which is not limited in the embodiment of the present application.

In one embodiment, the step S208, that is, when the configuration data satisfies the data constraint condition, the step of storing the configuration data in the management system specifically includes: determining data formats corresponding to the configuration data respectively; according to the data constraint conditions, verifying the validity of the data format of each configuration data; when the validity verification is passed, the configuration data is stored to the management system.

Specifically, the terminal may determine a data format corresponding to each piece of configuration data, that is, a data type and a data length corresponding to the configuration data, so as to perform validity verification on the data format of each piece of configuration data according to a data constraint condition. When the validity verification is passed, the terminal can store the configuration data into the management system. Thus, the management system generated by the management system generation model can realize validity verification on the collected configuration data so as to judge whether the configuration data is legal or not, thereby saving legal configuration data.

According to the data collection method, the management system generation model with the page constraint condition and the data constraint condition is directly developed according to the system demand information, so that the corresponding management system is directly generated in a model driving mode. And the management system can provide a data collection page matched with the system demand information to collect configuration data, and store the configuration data meeting the data constraint condition so as to provide the configuration data for the service system. Therefore, the management system with the data collection function and the data processing and storing function can be directly generated according to the management system generation model, front-end and back-end development of multi-person cooperation is not needed additionally according to development requirements, the frequency of communication coordination among a demand department, an outsourcing unit and developers in the development process is reduced, the development efficiency of the management system is greatly improved, and further the processing efficiency of data collection through the management system is greatly improved.

In one embodiment, step S202, that is, the step of obtaining the management system generation model specifically includes: entering a management system to generate a page, and triggering an identity verification request through the management system to generate the page; responding to the identity verification request, and collecting corresponding user identity information; and when the user identity information passes the verification, calling a management system generation model created based on the system demand information from the management system generation page.

Wherein the authentication request is a request to trigger the execution of an authentication operation. The user identity information is information indicating the identity of the user, and specifically can be information such as a user account number, a face image, a user fingerprint, or a user voiceprint. Specifically, the terminal may obtain a website address pointing to the generation page of the management system, and enter the generation page of the management system according to the website address. An authentication area is shown in the management system generation page, where a user may trigger an authentication request. For example, the user may input a user account number and an account number password in the authentication area and click on a "login" control, so that the terminal local or the server may perform validity authentication on the collected user account number and account number password. It can be understood that the terminal or the server may store the effective user account number and the effective account number password in advance so as to compare and verify the user account number and the account number password input by the user. And when the comparison is completely consistent, checking the user account to pass, otherwise, not passing. For example, the user may trigger a face acquisition command in the authentication area, and the terminal may start the camera to acquire a face image, and verify the face image locally at the terminal or through the server. It can be appreciated that the terminal or the server may store the effective face image in advance to perform feature comparison on the collected face image of the user. When the matching degree obtained by comparison reaches a preset threshold, the face image of the user passes the verification, otherwise, the face image of the user does not pass the verification.

Further, after the user identity information passes the verification, the terminal may call a management system generation model created based on the system requirement information from the management system generation page. In one embodiment, after the verification of the user identity information is passed, the terminal may display the management system generation model in the management system generation page, or display a link address pointing to the management system generation model in the management system generation page, and the user may download the management system generation model by clicking on the link address.

In the embodiment, only the user passing through the user identity information verification has the authority to acquire the management system generation model so as to automatically generate the management system and realize the functions of automatic page generation and data storage, so that the hidden trouble problems of resource waste and unsafe data caused by the fact that a malicious user triggers the generation management system can be avoided, and the safety and effectiveness of the whole data collection process are greatly improved.

In one embodiment, the data collection method further comprises determining a preconfigured management system identification, and a management system name and corresponding system description information entered into a management system generation page. The step of running the management system generation model to generate the corresponding management system specifically includes: and running the management system to generate a model, and generating a corresponding management system according to the management system identification, the management system name and the corresponding system description information.

Wherein the management system identifier is used for uniquely identifying one management system, and can be a character string comprising at least one character of numbers, letters and symbols. The preconfigured management system identifier may specifically be a serial number allocated according to the generation time of different management systems, so as to mark the different management systems. The management system name is a special name for identifying the management system, can be named according to the purpose of the management system, such as 'upgrade package compatible configuration', or 'advertisement space configuration', and the like, and can clearly express the effect of the management system. The system description information is information describing main functions or main features of the management system, for example, for the management system of the "upgrade package compatible configuration", according to the features of configuration information to be collected, the following description information may be used to describe the management system: the low version does not support the encryption package, and the encryption package is required to be upgraded to support the encryption package version before subsequent upgrading.

Specifically, when the terminal enters the management system generation page according to the website, the terminal can automatically generate the management system identification according to a preset allocation rule through the management system generation page, and a user can input the management system name and corresponding system description information in the management system generation page. When the terminal runs the management system to generate a model, a corresponding management system can be generated according to the management system identification, the management system name and the corresponding system description information, namely, the system identification, the management system name and the corresponding system description information are bound with the management system. Thus, the corresponding management system can be identified by the management system identification.

Referring to fig. 3, fig. 3 is an interface schematic of a management system generating a page in one embodiment. As shown in fig. 3, an information filling area 301 and a management system generation model area 302 are shown in the management system generation page. Prompt information such as "management system identification", "name (simple)", "management system name", "system description", "authority management" and "notice" is displayed in the information filling area 301, and controls such as text input boxes or options are displayed beside the prompt information, so that a user can input corresponding information through the text input boxes and the option boxes. In this management system generation model area 302, the specific contents of a management system generation model including specifically a data model of keys and a data model of values are presented. An example of a data model of a key is shown as 3021 and an example of a data model of a value is shown as 3022. When the user clicks the "confirm modification" control 303, the terminal may automatically generate a corresponding management system according to the related information filled in the information filling area 301 and the management system generation model embedded in the management system generation model area 302.

In the above embodiment, the corresponding management system is generated according to the management system identifier, the management system name and the corresponding system description information, so that the management system with the unique identifier and including the system name and the system description information can be obtained, the user using the management system can more clearly locate the management system, and the management system is primarily known, thereby facilitating the operation of the user.

In one embodiment, the step S206, that is, the step of providing, by the management system, the data collection page satisfying the page constraint condition, specifically includes: displaying a configuration list page through a management system; the configuration list page comprises an adding control for adding configuration records; when a triggering operation on the adding control occurs, a data collection page meeting page constraint conditions is displayed. Step S208, i.e. after the step of storing the configuration data to the management system when the configuration data satisfies the data constraint condition, is the data collection method further comprising: and generating corresponding configuration records according to the stored configuration data, and adding the generated configuration records into a configuration list page.

The configuration list page is a page for displaying configuration records in a list form. Specifically, after the terminal generates the management system, the terminal can directly provide the configuration category page through the management system. In the configuration list page, a history generated configuration record is shown, and an adding control for adding the configuration record is also shown. When triggering operation acting on the adding control is generated, the terminal can automatically generate a data collection page meeting page constraint conditions and jump to the data collection page. The triggering operation can be specifically touch operation, cursor operation, key operation or voice operation.

Further, after the user fills in corresponding configuration data through the data collection page, the terminal can store the effective configuration data meeting the data constraint conditions, and then a configuration record is generated according to the effective configuration data. The configuration record may be added to the configuration list page, i.e. the configuration category page updates the existing configuration record.

Referring to FIG. 4, FIG. 4 is an interface diagram of a configuration list page in one embodiment. When the user clicks on the "determine modification" control 303 in fig. 3, the terminal may present a configuration category page. As shown in fig. 4, the configuration list page has a test area 401, a notice area 402, and a configuration record display area 403 displayed therein. In the test area 401, the user can trigger a model request by entering corresponding information in a text entry box corresponding to the "key". Notice information that needs to be noted when entering configuration data is shown in the notice area 402. The configuration record showing area 403 shows the configuration record having the history in the form of a list. Wherein, for each configuration record, key information of a key corresponding to the configuration, and general data collected through a data model of the key, such as a ROM scene, an operating system and a model, are specifically recorded. The configuration record also includes an "updater" and an "update time". In addition, operations of viewing, copying, editing, version, release, and the like can also be performed in the configuration record presentation area 403. With continued reference to fig. 4, an add control 404, specifically shown as "add configuration", is shown in the upper right hand corner of fig. 4, and when the user clicks on the add control 404, the terminal may jump to fig. 5.

Referring to FIG. 5, FIG. 5 is a schematic diagram of an interface of a data collection page in one embodiment. As shown in fig. 5, the data collection page includes a generic data entry area 501 generated by the data model corresponding to the key and a configuration data entry area 502 generated by the data model corresponding to the value. In this general data entry area 501, relevant prompt information is presented, such as "ROM scene", "operating system" and "model", for prompting the user to enter corresponding general data. The configuration data entry area 502 displays relevant prompt information, such as "version", "download address", "installation package mac check value", "encryption key", "reference version (full package is empty and differential package is not empty)", "client popup", "update log", "installation package name", and "upgrade mode (0: not upgrade, 1: recommended upgrade, 2: forced upgrade, 3: silent upgrade)", etc., for prompting the user to enter corresponding general data. After the user clicks the "determine add" control, the terminal may obtain the general data and configuration data entered into the data collection page.

In the above embodiment, the configuration list page may be displayed by the management system, and the configuration records of the history may be displayed in a list form in the configuration list page, and the configuration records may be newly created by the configuration list page, so that a user may conveniently manage and control a plurality of configuration records.

In one embodiment, the data collection method further includes a step of viewing the calendar version of the configuration record, the step specifically including: generating, for each configuration record, calendar version information corresponding to each configuration record based on a sequence of collection times for collecting configuration data through the corresponding data collection page; when a version check instruction for the target configuration record occurs in the configuration list page, displaying historical version information corresponding to the target configuration record; and displaying the configuration data corresponding to the target version information selected by the selected instruction according to the selected instruction acting on the historical version information.

Specifically, separate on-line and off-line processing and version management may be performed for each configuration record. After the terminal generates a configuration record, the configuration record can be displayed in a configuration list page, when the terminal detects the editing operation of the configuration record, the terminal can enter a data collection page corresponding to the configuration record, and a user can modify, delete or add the configuration data input before the data collection page. The terminal can generate a new version of configuration record according to the modified configuration data. That is, for each configuration record, the terminal may generate the calendar version information corresponding to each configuration record based on the chronological order of the collection time for collecting the configuration data through the corresponding data collection page. The version information may specifically be a version number. When the terminal detects that a version check instruction for the target configuration record occurs in the configuration list page, the terminal displays the historical version information corresponding to the target configuration record, and further displays configuration data corresponding to the target version information selected by the selected instruction according to the selected instruction acting on the historical version information.

Referring to fig. 6, fig. 6 is a schematic diagram of an interface for viewing historical version information in one embodiment. When the user clicks the "version" control corresponding to a label configuration record in fig. 4, the terminal may enter the interface shown in fig. 6. As shown in fig. 6, the terminal may display version information of each version corresponding to the label configuration record, where the version information may specifically include specific information such as version number, record type, operator, and operation time. And, when the user clicks the "roll-back" control, the terminal may display the configuration data corresponding to the target version.

In the above embodiment, the configuration data of different versions of each configuration record is recorded, so that rollback operations of different versions can be implemented, and management of different versions of the configuration record is facilitated.

In one embodiment, the step S208, that is, when the configuration data satisfies the data constraint condition, the step of storing the configuration data in the management system specifically includes: when the configuration data meets the data constraint condition, determining a page identification of a data collection page corresponding to the configuration data and general data input into the data collection page; determining a corresponding retrieval index according to the page identification and the general data; and storing the retrieval index and the corresponding configuration data in association with the management system.

In particular, when the management system generation model specifically includes a data model of keys and a data model of values, the corresponding management system generated by the management system generation model may provide a data collection page including an entry area corresponding to "keys" and an entry area corresponding to "values". The data collected through the entry area of the corresponding "key" is generic data and the data collected through the entry area of the corresponding "value" is configuration data. The general data is data for describing the whole configuration process or setting the large direction and the frame of the configuration process. The general data may be, in particular, configuration scene information or device information of a device to which the corresponding configuration data is applied, etc. For example, when a certain configuration is mainly used for collecting configuration data about "upgrade package compatible configuration", the general data may be, correspondingly, related information of "ROM scene", "operating system", and "model", referring to fig. 5.

Further, when the general data and the configuration data both meet the data constraint condition, the terminal may determine a page identifier of the data collection page corresponding to the configuration record. The page identifier is used for uniquely identifying one page, and specifically may be a character string including at least one character of numbers, letters and symbols. For example, different data collection pages may correspond to different sequence number tags, which may then be used as page identifications for the data collection pages.

Furthermore, the terminal can be used for commonly using keywords in the data, and splicing the page identification and the keywords to obtain corresponding retrieval indexes. The splicing mode may specifically be that a splicing symbol is arranged between the page identifier and the keyword, where the splicing symbol may specifically be a word or a symbol, and the word may be a "sum" symbol, and the symbol may be a symbol such as "|", or ">", which is not limited in the embodiment of the present application. The terminal may store the search index in association with the corresponding configuration data in the management system.

In one embodiment, the terminal may store the general data and the configuration data in a Key-Value (Key-Value pair) storage manner. And splicing the page identifier and the keywords in the general data into information corresponding to the Key by adopting a field splicing mode, and directly storing the JSON character string of the original configuration data by Value.

In one embodiment, when the terminal stores the general data and the configuration data in an associated manner, the user can conveniently and quickly find the corresponding configuration data directly through the index, so that the data processing efficiency is greatly improved.

It will be appreciated that the configuration data collected by different management systems may be stored in an isolated manner, that is, the configuration data collected by the same management system may be stored in the same storage device in a Key-Value manner or stored in a separate storage area. Configuration data collected for different management systems may be stored in different storage devices, or in separate storage areas. In this way, the memory addresses corresponding to different management systems are also added to the Key, and when corresponding configuration data is searched, the memory area corresponding to a specific management system can be accurately positioned, so that the required configuration data can be quickly searched.

Referring to fig. 7 (a) and 7 (b), fig. 7 (a) is a schematic diagram of a data collection method in one embodiment. As shown in FIG. 7 (a), the management system generates a data model comprising data models and values for keys, namely KEY SCHEMA and Value Schema, and the data collection page generated by this model includes a generic data entry area and a configuration data entry area. The universal data collected through the universal data entry area is taken as UniqueKey (independent Key), the page identity provided by KEY SCHEMA is taken as RouteKey (routing Key), and RouteKey and UniqueKey are spliced together to form a Key. The terminal may directly store the Key and Value association directly as Value from JSON strings of configuration data collected by the configuration data entry region.

With continued reference to fig. 7 (b), fig. 7 (b) is a schematic diagram of a splice of keys in one embodiment. As shown in fig. 7 (b), the terminal may generate a corresponding data collection page including a generic data entry area through the created KEY SCHEMA. The general data collected in the data collection page includes: the merchant number is "test", and the sub-merchant number is "123". It can be understood that the terminal can also directly splice the general data corresponding to the merchant number and the sub-merchant number to obtain a corresponding key, wherein the key is: test|123".

It will be appreciated that in some other embodiments, the terminal may also directly splice a plurality of keywords in the data to obtain a corresponding search index. The embodiment of the present application is not limited thereto.

In one embodiment, when a certain configuration record stores configuration data in multiple versions, the particular configuration data found by the search index may be the latest version. In another embodiment, the terminal may display a configuration record corresponding to the latest version of configuration data, and may further search for multiple versions of configuration data corresponding to the configuration record.

In the above embodiment, the general data and the configuration data are stored in an associated manner according to the index, and the specific configuration data in the specific data collection page can be directly located by retrieving the index when the configuration data is searched, so that the data searching efficiency is improved.

In one embodiment, the data collection method further includes a step of searching for target configuration data, the step specifically including: receiving a data call request from a service system; responding to the data calling request, and searching target configuration data corresponding to the data calling request from the management system; and feeding back the target configuration data to the service system through a data calling interface provided by the management system.

Wherein the data call interface is an interface for calling configuration data. Specifically, the management system may provide an interface for performing data call, and the terminal may receive a data call request from the service system, where the data call request may carry key information, where the key information may specifically be a data identifier of the configuration data, or may also be content of at least a part of the search index corresponding to the configuration data. And the terminal can search and find from the management system according to the key information to determine the target configuration data matched with the key information. And the terminal can feed back the target configuration data to the service system through a data calling interface provided by the management system. Therefore, after the service system acquires the target configuration data, the service system can perform corresponding service processing based on the target configuration data according to actual service requirements.

In a specific application scenario, the target configuration data may specifically include white list information, and when the service system acquires the white list information, the service system may set that the corresponding user has authority to access or edit the target service based on the white list information. In another specific application scenario, the configuration data may specifically include advertisement display information and an advertisement to be pushed, and then, after the service system obtains the advertisement display information and the advertisement to be pushed, the service system may set an advertisement page or push the advertisement to a target group based on the information. It will be appreciated that the specific application scenario described above is only for the purpose of aiding in the description of the present application, and is not intended to limit the present application.

In a specific embodiment, referring to fig. 8 (a) and 8 (b), fig. 8 (a) is a schematic view of a scenario of a data collection method in one embodiment. As shown in fig. 8 (a), a developer creates a management system generating model according to the demand information provided by the product/operator, and further, by running the management system generating model to display a data collection page, the product/operator can collect configuration information through the data collection page, and the management system can process and store the collected configuration information.

Referring to fig. 8 (b), fig. 8 (b) is a schematic diagram of generation of a management system in one embodiment. Referring to FIG. 8 (b), the developer "translates" the requirements into a description language recognizable and processable by the computer device, resulting in a corresponding data model, i.e., a programming language model defined by JOSN Schema. And then a corresponding management system is generated by running the data model. The management system has the functions of data storage, data verification, authority control, operation recording, version management, gray level release and the like. The management system can display a data collection page, and a product/operator can input and collect configuration data through the data collection page.

It will be appreciated that for conventional management system development methods, such as model design, storage resource application, DAO/AO development, outsourcing requirement document provision, outsourcing project scheduling, XPHP (based on a coding specification of the php system) development, management end page development, test joint debugging, and acceptance release, the time period required for developing a management system may need to be 7-10 times and be time-consuming and labor-consuming. Compared with the traditional development method of the management system, the generation method of the management system provided by the application only needs to develop a management system generation model meeting the requirements, so that the development time is shortened from more than one period to about 1 hour, and the efficiency is improved by more than 97.5%. Thus, the development of the management system greatly saves time, and the efficiency of data collection through the management system is also greatly improved.

It should be understood that, although the steps in the flowchart of fig. 2 are shown in sequence as indicated by the arrows, the steps are not necessarily performed in sequence as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in fig. 2 may include a plurality of steps or stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily sequential, but may be performed in rotation or alternatively with at least a portion of the steps or stages in other steps or other steps.

In one embodiment, as shown in fig. 9, a data collection device 900 is provided, which may be implemented as a software module or a hardware module, or a combination of both, as part of a computer apparatus, and specifically includes: an acquisition module 901, a generation module 902 and a storage module 903, wherein:

An acquisition module 901, configured to acquire a management system generation model; the management system generation model includes page constraints and data constraints that match the system demand information.

The generating module 902 is configured to run a management system generating model to generate a corresponding management system, and provide, by the management system, a data collection page that satisfies the page constraint condition.

The acquiring module 901 is further configured to acquire configuration data entered into a data collection page.

A storage module 903, configured to store the configuration data to the management system when the configuration data satisfies a data constraint condition; the stored configuration data is used for providing to the business system for corresponding business processing.

In one embodiment, the obtaining module 901 is further configured to enter a management system to generate a page, and trigger an identity verification request through the management system to generate the page; responding to the identity verification request, and collecting corresponding user identity information; and when the user identity information passes the verification, calling a management system generation model created based on the system demand information from the management system generation page.

In one embodiment, the data collection device 900 further includes a determining module 904 configured to determine a preconfigured management system identification, and a management system name and corresponding system description information entered into a management system generation page. The generating module 902 is further configured to run a management system generating model, and generate a corresponding management system according to the management system identifier, the management system name, and the corresponding system description information.

In one embodiment, the generating module 902 is further configured to present a configuration list page through the management system; the configuration list page comprises an adding control for adding configuration records; when triggering operation acting on the adding control occurs, displaying a data collection page meeting page constraint conditions; and generating corresponding configuration records according to the stored configuration data, and adding the generated configuration records into a configuration list page.

In one embodiment, the data collection apparatus 900 further includes a presentation module 905, where the generation module 902 is further configured to generate, for each configuration record, historical version information corresponding to each configuration record, based on a sequence of collection times of collecting the configuration data through the corresponding data collection page. The display module 905 is further configured to display the historical version information corresponding to the target configuration record when a version view instruction for the target configuration record occurs in the configuration list page; and displaying the configuration data corresponding to the target version information selected by the selected instruction according to the selected instruction acting on the historical version information.

In one embodiment, the storage module 903 is further configured to determine a data format corresponding to each configuration data; according to the data constraint conditions, verifying the validity of the data format of each configuration data; when the validity verification is passed, the configuration data is stored to the management system.

In one embodiment, the storage module 903 is further configured to determine a page identifier of a data collection page corresponding to the configuration data and general data entered into the data collection page when the configuration data satisfies a data constraint condition; determining a corresponding retrieval index according to the page identification and the general data; and storing the retrieval index and the corresponding configuration data in association with the management system.

In one embodiment, the obtaining module 901 is further configured to obtain system requirement information, where the system requirement information includes page constraint information and data constraint information. The determining module 904 is further configured to determine a page constraint condition and a data constraint condition based on a preset data exchange language according to the page constraint information and the data constraint information. The generation module 902 is further configured to create a management system generation model based on the page constraints and the data constraints.

Referring to fig. 10, in one embodiment, the data collection apparatus 900 further includes a search module 906 and a feedback module 907, where the obtaining module 901 is further configured to receive a data call request from the service system. And the searching module 906 is used for responding to the data calling request and searching target configuration data corresponding to the data calling request from the management system. And the feedback module 907 is used for feeding back the target configuration data to the service system through the data calling interface provided by the management system.

According to the data collection device, the management system generation model with the page constraint condition and the data constraint condition is directly developed according to the system demand information, so that the corresponding management system is directly generated in a model driving mode. And the management system can provide a data collection page matched with the system demand information to collect configuration data, and store the configuration data meeting the data constraint condition so as to provide the configuration data for the service system. Therefore, the management system with the data collection function and the data processing and storing function can be directly generated according to the management system generation model, front-end and back-end development of multi-person cooperation is not needed additionally according to development requirements, the frequency of communication coordination among a demand department, an outsourcing unit and developers in the development process is reduced, the development efficiency of the management system is greatly improved, and further the processing efficiency of data collection through the management system is greatly improved.

For specific limitations of the data collection device, reference may be made to the above limitations of the data collection method, and no further description is given here. The various modules in the data collection device described above may be implemented in whole or in part in software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 11. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a data collection method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the structure shown in FIG. 11 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.

In an embodiment, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, storing a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.

Claims

1. A method of data collection, the method comprising:

acquiring configuration data input to the data collection page;

When the configuration data meets the data constraint condition, determining a page identifier of a data collection page corresponding to the configuration data and general data input into the data collection page; the general data is data for describing or setting a collection process of configuration data;

determining a corresponding retrieval index according to the page identifier and the general data;

Storing the search index and the corresponding configuration data in association with the management system; the stored configuration data is used for providing the configuration data to a service system for corresponding service processing.

2. The method of claim 1, wherein the acquisition management system generates a model comprising:

Entering a management system to generate a page, and triggering an identity verification request through the management system to generate the page;

responding to the identity verification request, and collecting corresponding user identity information;

And when the user identity information passes the verification, calling a management system generation model created based on the system demand information from the management system generation page.

3. The method according to claim 2, wherein the method further comprises:

determining a preconfigured management system identification, a management system name and corresponding system description information which are input to a management system generation page;

The running the management system generation model to generate a corresponding management system includes:

and running the management system generation model, and generating a corresponding management system according to the management system identification, the management system name and the corresponding system description information.

4. The method of claim 1, wherein the providing, by the management system, a data collection page that satisfies the page constraint comprises:

displaying a configuration list page through the management system; the configuration list page comprises an adding control for adding configuration records;

When triggering operation acting on the adding control occurs, displaying a data collection page meeting the page constraint condition;

after the step of storing the configuration data to the management system when the configuration data satisfies the data constraint condition, the method further includes:

And generating corresponding configuration records according to the stored configuration data, and adding the generated configuration records into the configuration list page.

5. The method according to claim 4, wherein the method further comprises:

generating, for each configuration record, calendar version information corresponding to each configuration record based on a sequence of collection times for collecting configuration data through the corresponding data collection page;

When a version check instruction for a target configuration record occurs in the configuration list page, displaying historical version information corresponding to the target configuration record;

And displaying configuration data corresponding to the target version information selected by the selected instruction according to the selected instruction acting on the historical version information.

6. The method of claim 1, wherein the storing the search index in association with the corresponding configuration data to the management system comprises:

determining the data format corresponding to each configuration data respectively;

According to the data constraint conditions, verifying the validity of the data format of each configuration data;

And when the validity verification is passed, storing the retrieval index and the corresponding configuration data in association with the management system.

7. The method according to claim 1, wherein the method further comprises:

acquiring system demand information, wherein the system demand information comprises page constraint information and data constraint information;

determining page constraint conditions and data constraint conditions based on a preset data exchange language according to the page constraint information and the data constraint information;

Creating a management system generation model based on the page constraint condition and the data constraint condition.

8. The method according to any one of claims 1 to 7, further comprising:

Receiving a data call request from a service system;

Responding to the data calling request, and searching target configuration data corresponding to the data calling request from the management system;

And feeding back the target configuration data to the service system through a data calling interface provided by the management system.

9. A data collection device, the device comprising:

the storage module is used for determining page identification of a data collection page corresponding to the configuration data and general data input into the data collection page when the configuration data meets the data constraint condition; the general data is data for describing or setting a collection process of configuration data; determining a corresponding retrieval index according to the page identifier and the general data; storing the search index and the corresponding configuration data in association with the management system; the stored configuration data is used for providing the configuration data to a service system for corresponding service processing.

10. The apparatus of claim 9, wherein the acquisition module is further configured to enter a management system to generate a page and trigger an authentication request by the management system to generate the page; responding to the identity verification request, and collecting corresponding user identity information; and when the user identity information passes the verification, calling a management system generation model created based on the system demand information from the management system generation page.

11. The apparatus of claim 10, wherein the apparatus further comprises:

12. The apparatus of claim 9, wherein the generation module is further configured to present a configuration list page through the management system; the configuration list page comprises an adding control for adding configuration records; when triggering operation acting on the adding control occurs, displaying a data collection page meeting the page constraint condition; and generating corresponding configuration records according to the stored configuration data, and adding the generated configuration records into the configuration list page.

13. The apparatus of claim 12, further comprising a display module, wherein:

The display module is used for displaying historical version information corresponding to the target configuration record when a version check instruction of the target configuration record occurs in the configuration list page; and displaying configuration data corresponding to the target version information selected by the selected instruction according to the selected instruction acting on the historical version information.

14. The apparatus of claim 9, wherein the memory module is further configured to:

15. The apparatus of claim 9, wherein the device comprises a plurality of sensors,

The acquisition module is further used for acquiring system demand information, wherein the system demand information comprises page constraint information and data constraint information;

the determining module is used for determining page constraint conditions and data constraint conditions based on a preset data exchange language according to the page constraint information and the data constraint information;

the generation module is further used for creating a management system generation model based on the page constraint condition and the data constraint condition.

16. The apparatus according to any one of claims 9 to 15, further comprising a look-up module and a feedback module, wherein:

17. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 8 when the computer program is executed.

18. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method of any one of claims 1 to 8.