CN114372240A - Data acquisition method, device, terminal and computer readable storage medium - Google Patents

Data acquisition method, device, terminal and computer readable storage medium Download PDF

Info

Publication number
CN114372240A
CN114372240A CN202210025846.5A CN202210025846A CN114372240A CN 114372240 A CN114372240 A CN 114372240A CN 202210025846 A CN202210025846 A CN 202210025846A CN 114372240 A CN114372240 A CN 114372240A
Authority
CN
China
Prior art keywords
data acquisition
data
information
user
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210025846.5A
Other languages
Chinese (zh)
Inventor
刘延磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Puhui Enterprise Management Co Ltd
Original Assignee
Ping An Puhui Enterprise Management Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Puhui Enterprise Management Co Ltd filed Critical Ping An Puhui Enterprise Management Co Ltd
Priority to CN202210025846.5A priority Critical patent/CN114372240A/en
Publication of CN114372240A publication Critical patent/CN114372240A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141Access rights, e.g. capability lists, access control lists, access tables, access matrices

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The embodiment of the application provides a data acquisition method and a related device, wherein the method comprises the following steps: receiving a data acquisition request, wherein the data acquisition request comprises user permission information and service information; determining the service authority information of the service information of the user according to the user authority information; determining a first data acquisition list corresponding to the user according to the service authority information; determining a second data acquisition list from the first data acquisition list according to the service information; acquiring a target data set according to the second data acquisition list; and sending the target data set to the user, so that the efficiency of data acquisition can be improved.

Description

Data acquisition method, device, terminal and computer readable storage medium
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a data acquisition method, an apparatus, a terminal, and a computer-readable storage medium.
Background
The traditional query interface realizes the query logic of the interface and returns fixed parameters. In some specific scenes, because the same interface is provided for different callers due to the problems of authority and the like to return different parameter information, the traditional method has the problems that the interface logic has poor reusability, and a plurality of interfaces are possibly repeatedly established to realize the calling of users with different authorities so as to meet the requirements of the users, thereby causing the low efficiency in data acquisition.
Disclosure of Invention
The embodiment of the application provides a data acquisition method, a data acquisition device, a terminal and a computer-readable storage medium, which can improve the efficiency of data acquisition.
A first aspect of an embodiment of the present application provides a data acquisition method, where the method includes:
receiving a user data acquisition request, wherein the data acquisition request comprises user authority information and service information;
determining the service authority information of the service information of the user according to the user authority information;
determining a first data acquisition list corresponding to the user according to the service authority information;
determining a second data acquisition list from the first data acquisition list according to the service information;
acquiring a target data set according to the second data acquisition list;
and sending the target data set to the user.
A second aspect of an embodiment of the present application provides a data acquisition apparatus, including:
the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a data acquisition request which comprises user authority information and service information;
a first determining unit, configured to determine, according to the user permission information, service permission information of the service information of the user;
a second determining unit, configured to determine, according to the service permission information, a first data acquisition list corresponding to the user;
a third determining unit, configured to determine a second data acquisition list from the first data acquisition list according to the service information;
an obtaining unit, configured to obtain a target data set according to the second data obtaining list;
a sending unit, configured to send the target data set to the user.
A third aspect of the embodiments of the present application provides a terminal, including a processor, an input device, an output device, and a memory, where the processor, the input device, the output device, and the memory are connected to each other, where the memory is used to store a computer program, and the computer program includes program instructions, and the processor is configured to call the program instructions to execute the step instructions in the first aspect of the embodiments of the present application.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program for electronic data exchange, where the computer program makes a computer perform part or all of the steps as described in the first aspect of embodiments of the present application.
A fifth aspect of embodiments of the present application provides a computer program product, wherein the computer program product comprises a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps as described in the first aspect of embodiments of the present application. The computer program product may be a software installation package.
The embodiment of the application has at least the following beneficial effects:
the method comprises the steps of receiving a data acquisition request, wherein the data acquisition request comprises user permission information and service information, determining the service permission information of the service information of a user according to the user permission information, determining a first data acquisition list corresponding to the user according to the service permission information, determining a second data acquisition list from the first data acquisition list according to the service information, acquiring a target data set according to the second data acquisition list, and sending the target data set to the user.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a data acquisition method according to an embodiment of the present application;
FIG. 2 is a schematic flow chart diagram illustrating another data acquisition method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a terminal according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a data acquisition apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," and the like in the description and claims of the present application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
Referring to fig. 1, fig. 1 is a schematic flow chart of a data acquisition method according to an embodiment of the present application. As shown in fig. 1, the data acquisition method is applied to an electronic device, which may be a server or the like, and is described here by taking the server as an example, and includes:
101. and receiving a data acquisition request, wherein the data acquisition request comprises user authority information and service information.
The method for receiving the data acquisition request may be: the user sends a data acquisition request to the server through the terminal equipment, and the server receives the data acquisition request sent by the terminal equipment.
The user permission information may include a user identifier and service scenario information, where the user identifier may be a user identification number, and the service scenario information may be understood as information of an application scenario of data that a user needs to acquire. The user identifier and the service scene information are both used for determining service authority information corresponding to the user.
102. And determining the service authority information of the service information of the user according to the user authority information.
The maximum data acquisition list corresponding to the user can be determined according to the user identification in the user permission information, and the service permission information can be determined according to the maximum data acquisition list and the service information.
The maximum data acquisition list may be understood as a highest data acquisition list corresponding to the authority of the user, and the highest data acquisition list may represent a data list corresponding to all service authorities corresponding to the authority of the user.
103. And determining a first data acquisition list corresponding to the user according to the service authority information.
The query can be performed in a database according to the service authority information to obtain a first data acquisition list. Different service authority information corresponds to different data acquisition lists, and the data acquisition lists can be represented by query lists. The first data acquisition list comprises a plurality of data types, and each data type can correspond to different data acquisition logics, so that data related to a user can be acquired according to the data acquisition logics.
104. And determining a second data acquisition list from the first data acquisition list according to the service information.
The second data acquisition list may be determined from the first data acquisition list according to a service parameter type corresponding to the service information. The number of types of data acquired by the second data acquisition list is less than or equal to the type of data acquired by the first data acquisition list.
And determining the second data acquisition list from the first data acquisition list according to the service information, so that unnecessary data acquisition can be reduced, the system overhead is reduced, and the efficiency can be improved.
105. And acquiring a target data set according to the second data acquisition list.
User attribute information of the user can be acquired, and a target data set is determined from the data sets acquired from the second data acquisition list according to the user attribute information. The user attribute information may be understood as: type attribute of the user, e.g., the user is a general user, an administrator, a super administrator, etc.
106. And sending the target data set to the user.
The target data set may be sent to the user at regular time, or the target data set may be directly sent to the user after the target data set is obtained.
In this example, by receiving a data acquisition request sent by a user, the data acquisition request includes user right information and service information, determining service authority information of the service information of the user according to the user authority information, determining a first data acquisition list corresponding to the user according to the service authority information, determining a second data acquisition list from the first data acquisition list according to the service information, obtaining a target data set according to the second data obtaining list, sending the target data set to the user, and therefore, the target data set can be obtained through a second data obtaining list determined by the service authority information of the user without designing different interfaces aiming at different authorities, the data set corresponding to the user permission is acquired, and the efficiency of acquiring the data set is improved.
In a possible implementation manner, the user permission information includes a user identifier and service scenario information, and a possible method for determining service permission information of service information of the user according to the user permission information includes:
a1, determining a maximum data acquisition list corresponding to the user according to the user identification;
a2, determining the service authority information according to the maximum data acquisition list and the service scene information.
The maximum data acquisition list may be understood as a highest data acquisition list corresponding to the authority of the user, and the highest data acquisition list may represent data lists corresponding to all service authorities corresponding to the authority of the user. The maximum data acquisition list corresponding to the user identifier of the user may be acquired according to a pre-stored maximum data acquisition list corresponding to the user identifier. The pre-stored maximum data acquisition list corresponding to the user identifier may be set and stored by the user during registration.
Data information associated with the service scene information can be determined, and service permission information can be determined according to the associated data information and the maximum data acquisition list. The data information associated with the service context information may be understood as: the scene type of the service scene information, and the like. Different scene types and maximum data acquisition lists correspond to different service authority information, so that the service authority information can be determined.
In this example, the service permission information is determined through the maximum data acquisition list and the service scene information corresponding to the user identifier, so that the accuracy of acquiring the service permission information is improved.
In a possible implementation manner, a possible method for determining a second data acquisition list from the first data acquisition list according to the service information includes:
b1, acquiring K service parameter types corresponding to the service information;
b2, acquiring data types corresponding to the K service parameter types to obtain K target data types;
and B3, determining a second data acquisition list from the first data acquisition list according to the K target data types.
The service information may include a plurality of service parameter types, and different service parameter types may correspond to different data types. Keyword extraction can be carried out on the service information to obtain keywords; and determining a plurality of service parameter types corresponding to the service information according to the keywords. And each service parameter type corresponds to a plurality of keywords, so that the service parameter type can be determined according to the keywords. The method for extracting the keywords from the service information may be a general keyword extraction algorithm, and the like.
Data types associated with the target data type in the first data acquisition list may be extracted to obtain the second data acquisition list. The data type associated with the target data type may be understood as the same data type as the target data type or a data type close to the target data type.
In this example, the second data acquisition list is determined from the first data acquisition list by K target data types, so that accuracy in determining the second data acquisition list is improved.
In a possible implementation manner, a possible method for acquiring a target data set according to the second data acquisition list includes:
c1, acquiring the user attribute information of the user;
c2, determining the associated data information of the user according to the user attribute information;
c3, determining a first keyword set according to the associated data information;
c4, acquiring a reference data set according to the data type in the second data acquisition list;
c5, extracting keywords from the reference data set to obtain a second keyword set;
c6, determining a target keyword set according to the first keyword set and the second keyword set;
and C7, determining the target data set from the reference data set according to the target keyword set.
Wherein, the user attribute information can be understood as: type attribute of the user, e.g., the user is a general user, an administrator, a super administrator, etc.
The associated data information of the user can be understood as information data information associated with user attribute information, for example, data information associated with a general user, data information desired to be associated with an administrator, and associated data information of the user, which is different from the user attribute information. The associated data information may be a data range of data information corresponding to the user, for example, if the associated data information of the general user is different from the associated data information of the administrator, the data information may have the same data information, or different data information, the data in the acquired reference data set may be extracted in a limited manner, so as to improve the accuracy of the acquired target data set.
Keyword extraction may be performed on the associated data information to obtain a first set of keywords. The specific keyword extraction method may adopt a general keyword extraction algorithm, which is not described herein again.
A reference data set may be determined according to the reference scene set corresponding to the data type in the second data acquisition list and the data acquisition logic corresponding thereto. The data acquisition logic may be understood as: the data environment for data acquisition may be obtained by running data acquisition logic to obtain data in the reference data set.
The method for obtaining the keywords in the second keyword set may refer to the method for obtaining the first keyword set, and details are not repeated here.
The intersection of the first keyword set and the second keyword set may be determined as a target keyword set. The set of keywords associated with the first keyword set in the second keyword set may be determined as a target keyword set. The keywords in the second keyword set associated with the first keyword set may be understood as keywords in the first keyword set may be associated with keywords in a plurality of second keyword sets, and the association relationship may be set by experience values or historical data.
Therefore, the target data set can be determined from the reference data set according to the target keyword set, and the method specifically includes: and determining data corresponding to the keywords in the target keyword set as data in the target data set.
In this example, the first keyword set and the second keyword set corresponding to the reference data set are determined according to the associated data information determined by the user attribute information of the user, and the target data set is determined from the reference data set according to the target keyword set determined by the first keyword set and the second keyword set, so that the accuracy in determining the target data set is improved.
In a possible implementation manner, a possible method for acquiring a reference data set according to a data type in the second data acquisition list includes:
d1, acquiring a reference scene set corresponding to the data types in the second data acquisition list;
d2, determining a target scene set from the reference scene set according to the service information;
d3, determining the reference data set according to the data acquisition logic corresponding to the target scene set.
The data type may be combined with a plurality of reference scenes, and the corresponding relationship may be set by an empirical value or historical data. The target scene set may be determined according to the association between the service information and the reference scene in the reference scene set, and specifically, the association may be: and determining the reference scene with the association degree between the service information and the reference scene in the reference scene set higher than a preset threshold value as an element in the target scene set. The preset threshold is set by empirical values or historical data. The association between the service information and the reference scenes in the reference scene set may be understood as: and the matching degree between the service information and the reference scene is higher, the association degree is higher, and the matching degree is lower, and the association degree is lower.
If different target scenes correspond to different data acquisition logics, the data acquisition logics corresponding to the target scenes in the target scene set can be operated to obtain the reference data set.
In this example, by acquiring a reference scene set corresponding to the data type in the second data acquisition list, determining a target scene set from the reference scene set according to the service information, and determining the reference data set according to the data acquisition logic corresponding to the target scene set, the accuracy of acquiring the reference data set can be improved.
In a possible implementation manner, another possible method for acquiring a target data set according to the second data acquisition list includes:
e1, acquiring data acquisition logic corresponding to each data type in the second data acquisition list;
e2, operating the data acquisition logic corresponding to each data type in the second data acquisition list to obtain an operation result corresponding to each data type in the second data acquisition list;
e3, determining the target data set according to the operation result corresponding to each data type in the second data acquisition list.
If different data types correspond to different data acquisition logics, the data acquisition logics corresponding to the data types can be operated to obtain operation results corresponding to the data types.
The run result corresponding to each data type in the second data acquisition list may be determined as a target data set. Or combining the operation results corresponding to each data type in the second data acquisition list to obtain a target data set. The method for combining the operation results corresponding to each data type in the second data acquisition list may be to combine the operation results according to the operation order of the data acquisition logic, and the like.
In this example, by operating the data acquisition logic corresponding to each data type in the second data acquisition list to acquire an operation result, and determining the target data set according to the operation result, the target data set can be acquired quickly, and the efficiency of acquiring the target data set is improved.
In a possible implementation manner, the data obtaining list may be configured, and specifically, the data obtaining list may include:
firstly, configuring a parameter base table;
configuring the parameter name of the base, processing mode (simple SQL query, bean type 2),
simple SQL: configuring SQL and SQL entries
The Bean class: and configuring the name of the bean, wherein the specific logic is realized in the bean class.
Secondly, grouping parameters;
classifying parameters, such as same entity, same scene, etc., to obtain types in data acquisition list
The same entity: example client entity (identification number, name, telephone, etc.)
In the same scene: for example, in a process node, a plurality of parameters of a plurality of entities are needed, and a plurality of parameters which are not needed are queried according to entity query, which wastes performance.
Thirdly, configuring entities/scenes and authorities;
the scene/entity of the configuration parameter is associated with the authority, and how many combinations or entities can be inquired by one type of authority. If the client right is not included, the client can not be inquired in the interface.
Referring to fig. 2, fig. 2 is a schematic flow chart of a data acquisition method according to an embodiment of the present application. As shown in fig. 2, the data acquisition method is applied to an electronic device, which may be a server or the like, and is described here by taking the server as an example, and includes:
201. receiving a data acquisition request, wherein the data acquisition request comprises user permission information and service information;
202. determining the service authority information of the service information of the user according to the user authority information;
the user authority information comprises user identification and service scene information.
203. Determining a first data acquisition list corresponding to the user according to the service authority information;
204. acquiring K service parameter types corresponding to the service information;
205. acquiring data types corresponding to the K service parameter types to obtain K target data types;
206. determining a second data acquisition list from the first data acquisition list according to the K target data types;
207. acquiring a target data set according to the second data acquisition list;
208. and sending the target data set to the user.
In this example, the second data acquisition list is determined from the first data acquisition list by K target data types, so that accuracy in determining the second data acquisition list is improved.
In accordance with the foregoing embodiments, please refer to fig. 3, fig. 3 is a schematic structural diagram of a terminal according to an embodiment of the present application, and as shown in the drawing, the terminal includes a processor, an input device, an output device, and a memory, and the processor, the input device, the output device, and the memory are connected to each other, where the memory is used to store a computer program, the computer program includes program instructions, the processor is configured to call the program instructions, and the program includes instructions for performing the following steps;
receiving a data acquisition request, wherein the data acquisition request comprises user permission information and service information;
determining the service authority information of the service information of the user according to the user authority information;
determining a first data acquisition list corresponding to the user according to the service authority information;
determining a second data acquisition list from the first data acquisition list according to the service information;
acquiring a target data set according to the second data acquisition list;
and sending the target data set to the user.
The above description has introduced the solution of the embodiment of the present application mainly from the perspective of the method-side implementation process. It is understood that the terminal includes corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above-described functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative elements and algorithm steps described in connection with the embodiments provided herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the terminal may be divided into the functional units according to the above method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
In accordance with the above, please refer to fig. 4, and fig. 4 is a schematic structural diagram of a data acquisition apparatus according to an embodiment of the present application. As shown in fig. 4, the apparatus includes:
a receiving unit 401, configured to receive a data acquisition request, where the data acquisition request includes user permission information and service information;
a first determining unit 402, configured to determine service authority information of service information of a user according to the user authority information;
a second determining unit 403, configured to determine, according to the service permission information, a first data acquisition list corresponding to the user;
a third determining unit 404, configured to determine a second data acquisition list from the first data acquisition list according to the service information;
an obtaining unit 405, configured to obtain a target data set according to the second data obtaining list;
a sending unit 406, configured to send the target data set to the user.
In a possible implementation manner, the user right information includes a user identifier and service scenario information, and the first determining unit 402 is configured to:
determining a maximum data acquisition list corresponding to the user according to the user identification;
and determining the service authority information according to the maximum data acquisition list and the service scene information.
In one possible implementation manner, the third determining unit 404 is configured to:
acquiring K service parameter types corresponding to the service information;
acquiring data types corresponding to the K service parameter types to obtain K target data types;
and determining a second data acquisition list from the first data acquisition list according to the K target data types.
In one possible implementation manner, the obtaining unit 405 is configured to:
acquiring user attribute information of the user;
determining associated data information of the user according to the user attribute information;
determining a first keyword set according to the associated data information;
acquiring a reference data set according to the data type in the second data acquisition list;
extracting keywords from the reference data set to obtain a second keyword set;
determining a target keyword set according to the first keyword set and the second keyword set;
and determining the target data set from the reference data set according to the target keyword set.
In a possible implementation manner, in the aspect of acquiring the reference data set according to the data type in the second data acquisition list, the acquiring unit 405 is configured to:
acquiring a reference scene set corresponding to the data type in the second data acquisition list;
determining a target scene set from the reference scene set according to the service information;
and determining the reference data set according to the data acquisition logic corresponding to the target scene set.
In one possible implementation manner, the obtaining unit 405 is further configured to:
acquiring data acquisition logic corresponding to each data type in the second data acquisition list;
operating data acquisition logic corresponding to each data type in the second data acquisition list to obtain an operation result corresponding to each data type in the second data acquisition list;
and determining the target data set according to the operation result corresponding to each data type in the second data acquisition list.
Embodiments of the present application also provide a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of any one of the data acquisition methods as described in the above method embodiments.
Embodiments of the present application also provide a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program causes a computer to execute part or all of the steps of any one of the data acquisition methods as described in the above method embodiments.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may be implemented in the form of a software program module.
The integrated units, if implemented in the form of software program modules and sold or used as stand-alone products, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned memory comprises: various media capable of storing program codes, such as a usb disk, a read-only memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and the like.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash memory disks, read-only memory, random access memory, magnetic or optical disks, and the like.
The foregoing detailed description of the embodiments of the present application has been presented to illustrate the principles and implementations of the present application, and the above description of the embodiments is only provided to help understand the method and the core concept of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims (10)

1. A method for data acquisition, the method comprising:
receiving a data acquisition request, wherein the data acquisition request comprises user permission information and service information;
determining the service authority information of the service information of the user according to the user authority information;
determining a first data acquisition list corresponding to the user according to the service authority information;
determining a second data acquisition list from the first data acquisition list according to the service information;
acquiring a target data set according to the second data acquisition list;
and sending the target data set to the user.
2. The method of claim 1, wherein the user permission information includes a user identifier and service scenario information, and the determining the service permission information of the service information of the user according to the user permission information includes:
determining a maximum data acquisition list corresponding to the user according to the user identification;
and determining the service authority information according to the maximum data acquisition list and the service scene information.
3. The method of claim 1, wherein the determining a second data acquisition list from the first data acquisition list according to the service information comprises:
acquiring K service parameter types corresponding to the service information;
acquiring data types corresponding to the K service parameter types to obtain K target data types;
and determining a second data acquisition list from the first data acquisition list according to the K target data types.
4. The method of claim 1, wherein said obtaining a target data set according to the second data acquisition list comprises:
acquiring user attribute information of the user;
determining associated data information of the user according to the user attribute information;
determining a first keyword set according to the associated data information;
acquiring a reference data set according to the data type in the second data acquisition list;
extracting keywords from the reference data set to obtain a second keyword set;
determining a target keyword set according to the first keyword set and the second keyword set;
and determining the target data set from the reference data set according to the target keyword set.
5. The method of claim 4, wherein obtaining a reference data set according to the data type in the second data acquisition list comprises:
acquiring a reference scene set corresponding to the data type in the second data acquisition list;
determining a target scene set from the reference scene set according to the service information;
and determining the reference data set according to the data acquisition logic corresponding to the target scene set.
6. The method of claim 1, wherein said obtaining a target data set according to the second data acquisition list comprises:
acquiring data acquisition logic corresponding to each data type in the second data acquisition list;
operating data acquisition logic corresponding to each data type in the second data acquisition list to obtain an operation result corresponding to each data type in the second data acquisition list;
and determining the target data set according to the operation result corresponding to each data type in the second data acquisition list.
7. A data acquisition apparatus, characterized in that the apparatus comprises:
the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a data acquisition request which comprises user authority information and service information;
the first determining unit is used for determining the service authority information of the service information of the user according to the user authority information;
a second determining unit, configured to determine, according to the service permission information, a first data acquisition list corresponding to the user;
a third determining unit, configured to determine a second data acquisition list from the first data acquisition list according to the service information;
an obtaining unit, configured to obtain a target data set according to the second data obtaining list;
a sending unit, configured to send the target data set to the user.
8. The apparatus of claim 7, wherein the user permission information comprises a user identifier and service scenario information, and wherein the first determining unit is configured to:
determining a maximum data acquisition list corresponding to the user according to the user identification;
and determining the service authority information according to the maximum data acquisition list and the service scene information.
9. A terminal, comprising a processor, an input device, an output device, and a memory, the processor, the input device, the output device, and the memory being interconnected, wherein the memory is configured to store a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the method of any of claims 1-6.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out the method according to any one of claims 1-6.
CN202210025846.5A 2022-01-11 2022-01-11 Data acquisition method, device, terminal and computer readable storage medium Pending CN114372240A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210025846.5A CN114372240A (en) 2022-01-11 2022-01-11 Data acquisition method, device, terminal and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210025846.5A CN114372240A (en) 2022-01-11 2022-01-11 Data acquisition method, device, terminal and computer readable storage medium

Publications (1)

Publication Number Publication Date
CN114372240A true CN114372240A (en) 2022-04-19

Family

ID=81143399

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210025846.5A Pending CN114372240A (en) 2022-01-11 2022-01-11 Data acquisition method, device, terminal and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN114372240A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116521488A (en) * 2023-07-03 2023-08-01 杭州新中大科技股份有限公司 Metadata-based self-defined document tracing method, device, equipment and medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116521488A (en) * 2023-07-03 2023-08-01 杭州新中大科技股份有限公司 Metadata-based self-defined document tracing method, device, equipment and medium
CN116521488B (en) * 2023-07-03 2024-03-26 杭州新中大科技股份有限公司 Metadata-based self-defined document tracing method, device, equipment and medium

Similar Documents

Publication Publication Date Title
CN110661829B (en) File downloading method and device, client and computer readable storage medium
CN109672888B (en) Picture compression method, equipment and computer readable storage medium
CN108985954B (en) Method for establishing association relation of each identifier and related equipment
CN104572727A (en) Data querying method and device
CN110213290B (en) Data acquisition method, API gateway and storage medium
CN109829073B (en) Image searching method and device
CN108154024B (en) Data retrieval method and device and electronic equipment
CN110569249A (en) data change pushing method and device and electronic equipment
CN114372240A (en) Data acquisition method, device, terminal and computer readable storage medium
CN110737458A (en) code updating method and related device
CN105989007B (en) File path processing method and device
CN112118189B (en) Flow sampling method, computer equipment and computer readable storage medium
CN109842482B (en) Information synchronization method, system and terminal equipment
CN111147535A (en) Method and device for preventing Internet of things platform from repeatedly creating terminal equipment
CN106959903A (en) Trap instruction Trap processing method and processing device
CN112162797B (en) Data processing method, system, storage medium and electronic device
CN106528750B (en) Data extraction method and device
CN113886242A (en) Data processing method, device, terminal and storage medium
CN110213267B (en) White list service processing method, server and computer storage medium
CN112738207B (en) Keyword data transmission method and device, storage medium and electronic device
CN110602198B (en) Client network request link configuration method and system
CN110781370B (en) Mobile terminal information query method and computer equipment
CN113282326B (en) Gray scale upgrading method, device, electronic equipment and readable storage medium
CN111240727B (en) Information updating method and device
CN113127692B (en) Data storage structure, retrieval method, data storage method and terminal equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination