CN113127909B - Feature data processing method and device, electronic equipment and storage medium - Google Patents

Feature data processing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113127909B
CN113127909B CN202110482756.4A CN202110482756A CN113127909B CN 113127909 B CN113127909 B CN 113127909B CN 202110482756 A CN202110482756 A CN 202110482756A CN 113127909 B CN113127909 B CN 113127909B
Authority
CN
China
Prior art keywords
target
feature
corresponding relation
data
data processing
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.)
Active
Application number
CN202110482756.4A
Other languages
Chinese (zh)
Other versions
CN113127909A (en
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.)
Beijing QIYI Century Science and Technology Co Ltd
Original Assignee
Beijing QIYI Century Science and Technology 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 Beijing QIYI Century Science and Technology Co Ltd filed Critical Beijing QIYI Century Science and Technology Co Ltd
Priority to CN202110482756.4A priority Critical patent/CN113127909B/en
Publication of CN113127909A publication Critical patent/CN113127909A/en
Application granted granted Critical
Publication of CN113127909B publication Critical patent/CN113127909B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/60Protecting data
    • G06F21/604Tools and structures for managing or administering access control systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00Pattern recognition
    • G06F18/20Analysing
    • G06F18/23Clustering techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N3/00Computing arrangements based on biological models
    • G06N3/02Neural networks
    • G06N3/04Architecture, e.g. interconnection topology
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N3/00Computing arrangements based on biological models
    • G06N3/02Neural networks
    • G06N3/08Learning methods
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Evolutionary Computation (AREA)
  • Biomedical Technology (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Biophysics (AREA)
  • Computational Linguistics (AREA)
  • Computer Hardware Design (AREA)
  • Molecular Biology (AREA)
  • Bioethics (AREA)
  • Mathematical Physics (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Databases & Information Systems (AREA)
  • Evolutionary Biology (AREA)
  • Bioinformatics & Computational Biology (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Automation & Control Theory (AREA)
  • Storage Device Security (AREA)

Abstract

The application provides a feature data processing method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: and receiving a first data processing request of the target login user aiming at the target feature library, verifying whether the target login user has the authority corresponding to the first data processing request to the target feature library according to a preset first corresponding relation, a second corresponding relation and a third corresponding relation, and if the target login user has the authority corresponding to the first data processing request to the target feature library, responding to the first data processing request, wherein the first corresponding relation is the corresponding relation between the feature library and the virtual user, the second corresponding relation is the corresponding relation between the virtual user and the item, and the third corresponding relation is the corresponding relation between the login user and the item. And the target login user is subjected to authority verification through the three corresponding relations, and after the verification is passed, the first data processing request is subjected to response processing, so that the data security is improved.

Description

Feature data processing method and device, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of data processing, and in particular, to a feature data processing method, a device, an electronic apparatus, and a storage medium.
Background
In the process of training a model by deep learning, feature data of sample data is usually extracted through feature engineering, the feature data is recorded, and then model training is performed based on the recorded feature data, so that the visible feature data is in a critical position in the deep learning.
At present, when feature data extracted in a feature project is recorded, the feature data is usually stored in a computer and other devices of a user by a brief means such as text or wiki, and is directly bound with the user, so that the sharing of the feature data is not facilitated.
Disclosure of Invention
In order to solve the technical problem of weaker safety of the feature data, the application provides a feature data processing method, a device, electronic equipment and a storage medium.
In a first aspect, the present application provides a feature data processing method, including:
receiving a first data processing request of a target login user aiming at a target feature library;
verifying whether the target login user has the right corresponding to the first data processing request to the target feature library according to a preset first corresponding relation, a second corresponding relation and a third corresponding relation;
If the target login user has the right corresponding to the first data processing request to the target feature library, responding to the first data processing request;
the first corresponding relation is the corresponding relation between the feature library and the virtual user, the second corresponding relation is the corresponding relation between the virtual user and the project, and the third corresponding relation is the corresponding relation between the login user and the project.
As a possible implementation manner, the verifying whether the target login user has the right corresponding to the first data processing request for the target feature library according to the preset first correspondence, second correspondence and third correspondence includes:
determining a target virtual user corresponding to the target feature library according to the first corresponding relation;
determining a target item corresponding to the target virtual user according to the second corresponding relation;
determining whether a target sub-corresponding relation exists between the target login user and the target item according to the third corresponding relation, wherein the target sub-corresponding relation is used for representing that the target login user has the right corresponding to the first data processing request for the target feature library;
And if a target sub-corresponding relation exists between the target login user and the target item, determining that the target login user has the right corresponding to the first data processing request for the target feature library.
As a possible implementation, the rights include an access right or any one of the following rights: read rights, write rights, or edit rights.
As a possible implementation manner, in the first correspondence, one feature library corresponds to one virtual user, and one virtual user corresponds to at least one feature library;
in the second corresponding relation, one virtual user corresponds to one item, and one item corresponds to at least one virtual user;
in the third correspondence, one login user corresponds to at least one item, and one item corresponds to at least one login user.
As a possible implementation manner, the method further includes:
before receiving a first data processing request of a target login user aiming at a target feature library, receiving a second data processing request, wherein the second data processing request is used for indicating to create the target feature library for storing a target feature data set;
Clustering the feature data in the target feature data set according to the feature type of the feature data in the target feature data set to obtain a plurality of feature groups, wherein the feature types of the feature data in the same feature group are the same, and the feature types of the feature data in any two feature groups are different;
combining a plurality of the features into the target feature library;
determining a target virtual user corresponding to the target feature library;
and creating a first corresponding relation between the target feature library and the target virtual user.
As a possible implementation manner, the first data processing request is a data writing request or a data reading request;
the responding processing to the first data processing request comprises the following steps:
if the first data processing request is determined to be a data writing request for indicating writing of first feature data into the target feature library, writing the first feature data into a feature group corresponding to the feature type in the target feature library according to the feature type of the first feature data;
and if the first data processing request is determined to be a data reading request for indicating to read the feature data in the target feature library, the feature data in the target feature library is read, and the read feature data is displayed.
As a possible implementation manner, the method further includes:
receiving a permission editing request, wherein the permission editing request is used for indicating to adjust a target corresponding relation, and the target corresponding relation is at least one of the first corresponding relation, the second corresponding relation and the third corresponding relation;
and adjusting the corresponding relation of the targets based on the permission editing request.
In a second aspect, embodiments of the present application further provide a feature data processing apparatus, including:
the receiving module is used for receiving a first data processing request of a target login user aiming at a target feature library;
the permission verification module is used for verifying whether the target login user has permission corresponding to the first data processing request for the target feature library according to a preset first corresponding relation, a preset second corresponding relation and a preset third corresponding relation;
the request processing module is used for responding to the first data processing request if the target login user has the right corresponding to the first data processing request to the target feature library;
the first corresponding relation is the corresponding relation between the feature library and the virtual user, the second corresponding relation is the corresponding relation between the virtual user and the project, and the third corresponding relation is the corresponding relation between the login user and the project.
In a third aspect, an embodiment of the present invention further provides an electronic device, including: the device comprises a processor and a memory, wherein the processor is used for executing a data processing program stored in the memory so as to realize the characteristic data processing method in the first aspect.
In a fourth aspect, an embodiment of the present invention further provides a storage medium storing one or more programs, where the one or more programs are executable by one or more processors to implement the feature data processing method according to the first aspect.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
according to the feature data processing method provided by the embodiment of the application, a first data processing request of a target login user aiming at a target feature library is received, whether the target login user has the authority corresponding to the first data processing request to the target feature library is verified according to a preset first corresponding relation, a second corresponding relation and a third corresponding relation, if the target login user has the authority corresponding to the first data processing request to the target feature library, the first corresponding relation is the corresponding relation between the feature library and a virtual user, the second corresponding relation is the corresponding relation between the virtual user and a project, and the third corresponding relation is the corresponding relation between the login user and the project. In the scheme, the authority of the target login user to the target feature library is verified through the three corresponding relations, and the first data processing request is responded and processed only when the target login user is determined to have the authority corresponding to the first data processing request to the target feature library, so that the safety of feature data in the feature library is improved.
Furthermore, the scheme enables the feature library and the login user to be associated through the virtual user and the project, so that the direct relationship between the feature library and the login user is decoupled, and rights management and sharing of the feature library are facilitated.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a flowchart of a feature data processing method according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of an association relationship among a login user, a virtual user and a feature library according to an embodiment of the present application;
FIG. 3 is a flowchart of a feature data processing method according to another embodiment of the present application;
FIG. 4 is a schematic diagram of a feature data storage structure according to an embodiment of the present application;
FIG. 5 is a flowchart of a method for creating a feature library according to an embodiment of the present application;
FIG. 6 is a block diagram of a feature data processing apparatus according to an embodiment of the present application;
fig. 7 is a schematic diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of 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 apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present application based on the embodiments herein.
Referring to fig. 1, a flowchart of a feature data processing method according to an exemplary embodiment of the present invention, as shown in fig. 1, may include the following steps:
s11, receiving a first data processing request of a target login user aiming at a target feature library.
The feature data processing method provided by the embodiment of the invention can be applied to a feature data management system, wherein the feature data management system can be a terminal such as a smart phone, a notebook computer, a desktop computer, a server and the like.
In the embodiment of the invention, the login user is a user with an account registered in the feature data management system in advance, and the feature library is a database which is created in the feature data management system in advance and is used for storing feature data.
In the embodiment of the invention, the first data processing request is a request triggered by the target login user and used for indicating to process the feature data in the target feature library, wherein the request can carry a login user identifier and a feature library identifier. After receiving the first data processing request, analyzing the first feature processing request, obtaining a login user identifier and a feature library identifier carried in the first feature processing request, determining that a login user corresponding to the login user identifier is a target login user, and determining that a feature library corresponding to the feature library identifier is a target feature library, wherein the login user identifier can be account information such as an account name and an ID of the login user, and the feature library identifier can be a name of the feature library.
As a possible implementation, the first data processing request may be sent by the target login user through the external device.
As another possible implementation manner, the first data processing request may be input by the target login user through a preset first data processing request output window in the feature data management system.
S12, verifying the authority of the target login user to the target feature library according to the preset first corresponding relation, second corresponding relation and third corresponding relation.
In the embodiment of the invention, the first corresponding relation is the corresponding relation between the feature library and the virtual user, the second corresponding relation is the corresponding relation between the virtual user and the item, the third corresponding relation is the corresponding relation between the login user and the item, wherein the login user is a user registered with an account in a feature data management system, the item is a service which is created in the item system according to actual requirements in advance and needs to be subjected to deep learning, the login user with the third corresponding relation is the login user for realizing the service, the virtual user is a virtual user which is created by a developer and is used for managing the feature library and is not a real user, one virtual user can be bound with at least one feature library, and one virtual user can be bound with one item, so that the association between the feature library and the item can be realized through the virtual user.
In the embodiment of the invention, the first corresponding relation, the second corresponding relation and the third corresponding relation are set, the feature library is associated with the login user through the virtual user and the project, the direct association between the feature library and the login user is decoupled, and the rights management and sharing of the feature library are more convenient.
In practical application, the first correspondence, the second correspondence, and the third correspondence may be stored in the terminal in the form of a table.
As an example, the second correspondence relationship may be set in the following manner: the project system is preset, the project system comprises a plurality of projects, each project is bound with one or more virtual users, and preferably, one virtual user can be bound with one project only, so that a unique project can be determined according to the virtual user. When the second correspondence is set, for each item, a second correspondence between the item and the virtual user having a binding relationship with the item is created, for example, if a binding relationship exists between item 1 and virtual users user1, user2 and user3, then second correspondence between item 1 and user1, user2 and user3 is created respectively.
As an example, the first correspondence relationship may be set in the following manner: and when or after the feature library is created, a first corresponding relation between the feature library and the virtual user is established according to actual requirements.
Preferably, a feature library establishes a first correspondence with only one virtual user, so as to ensure that a unique virtual user can be determined according to the feature library, and one virtual user can establish a first correspondence with a plurality of feature libraries.
As an example, the third relationship may be set in the following manner: and when or after the project is created, creating a third corresponding relation between the login user and the project according to the actual requirement. One of the login users can establish a third corresponding relation with a plurality of items, and one item can also establish the third corresponding relation with a plurality of login users. Based on the three corresponding relations, when verifying the authority of the target login user to the target feature library, the target virtual user corresponding to the target feature library can be determined according to the first corresponding relation, then the target item corresponding to the target virtual user is determined according to the second corresponding relation, then whether a third corresponding relation exists between the target login user and the target item or not is determined, if the third corresponding relation exists between the target login user and the target item, the authority of the target login user to the target item is determined, and if the third corresponding relation does not exist between the target login user and the target item, the authority of the target login user to the target item is determined.
Further, in the embodiment of the present invention, the first data processing request may be a data reading request or a data writing request, where different requests require different rights, for example, the data reading request requires a read right, and the data writing request requires a write right. Thus, after determining that the target login user has the right to the target item, it is further necessary to determine that the right is the right required for the first data processing request. Specifically, the third correspondence between the login user and the item may include at least one sub-correspondence, for example, a first sub-correspondence, a second sub-correspondence, and/or a third sub-correspondence, where the first sub-correspondence is used to indicate that the login user has access rights to the item, that is, that the login user has rights such as reading, writing, editing, etc. to the item, the second sub-correspondence is used to indicate that the login user has reading rights to the item, and the third sub-correspondence is used to indicate that the login user has writing rights to the item. After determining that the third correspondence is provided between the target login user and the target item, further verifying whether a target sub-correspondence exists in the third correspondence between the target login user and the target item is required, where the target sub-correspondence is used to characterize that the target login user has authority corresponding to the first data processing request for the target feature library, for example, if the first data processing request is a data reading request, the target sub-correspondence may be the first sub-correspondence or the second sub-correspondence, and if the first data processing request is a data writing request, the target sub-correspondence may be the first sub-correspondence or the third sub-correspondence. If the third corresponding relation between the target login user and the target item is determined to have the target sub corresponding relation, the target login user is determined to have the right corresponding to the first data processing request to the target feature library, and if the third corresponding relation between the target login user and the target item is determined to not have the target sub corresponding relation, the target login user is determined to have no right corresponding to the first data processing request to the target feature library.
For example, as shown in fig. 2, the project system includes 2 projects and 5 virtual users, where the 2 projects are respectively project 1 and project 2, and the 5 virtual users are respectively user1, user2, user3user4 and user5, where user1, user2 and user3 respectively have a second corresponding relationship with project 1, user4 and user5 respectively have a second corresponding relationship with project 2, the login user a has a third corresponding relationship with project 1, and the feature library 1 has a first corresponding relationship with user 3. If the received first data processing request is a data reading request of the login user a for the feature library 1, it may be determined that the feature library 1 corresponds to the user3 based on the correspondence shown in fig. 2, and the user3 corresponds to the item 1, so that the item 1 is a target item corresponding to the feature library 1, and because the login user a has a third correspondence with the item 1, it is determined that the login user a has the authority of the feature library 1, and further, it is verified whether the third correspondence between the login user a and the item 1 has the first sub-correspondence or the second sub-correspondence, and if the third correspondence between the login user a and the item 1 has the first sub-correspondence or the second sub-correspondence, it is determined that the login user a has the authority (i.e. the reading authority) corresponding to the first data processing request for the item 1, otherwise, it is determined that the login user a does not have the authority corresponding to the first data processing request for the item 1.
S13, if the target login user has the authority corresponding to the first data processing request to the target feature library, responding to the first data processing request.
In the embodiment of the invention, if the target login user is determined to have the right corresponding to the first data processing request to the target feature library, the target login user is determined to process the feature data in the target feature library, so that after the target login user is determined to have the right corresponding to the first data processing request to the target feature library, the feature data in the target feature library can be processed correspondingly based on the first data processing request.
In the embodiment of the present invention, the first data processing request may be a data writing request or a data reading request.
As an embodiment, after feature engineering of sample data for deep learning, for the obtained feature data, the feature data may be written into a previously created feature library for storage, and for this application scenario, a logged-in user may trigger a first data processing request for instructing to write the feature data into the created feature library.
Taking the first data processing request as an example of a data writing request for indicating to write the first feature data into the target feature library, the responding to the first data processing request may include:
And writing the first feature data into a feature group corresponding to the feature type of the first feature data in the target feature library according to the feature type of the first feature data.
In practical application, if the first data processing request is a data writing request, the first data processing request is parsed to obtain feature data (hereinafter referred to as first feature data) to be written into a target feature library, the first feature data may be provided with a feature type tag, a feature type of the first feature data is determined according to the feature type tag (hereinafter referred to as target feature type for convenience of description), whether a feature group corresponding to the target feature type exists in the target feature library is determined, and if the feature group corresponding to the target feature type exists in the target feature library, the first feature data is written into the feature group corresponding to the target feature type; if the fact that the feature group corresponding to the target feature type does not exist in the target feature library is determined, the feature group corresponding to the target feature type is created in the target feature library, the first feature data is written into the created feature group corresponding to the target feature type, and writing of the first feature data is completed.
As another embodiment, after writing the feature data into the feature library, when performing deep learning model training, the feature data in the feature library needs to be read for model training, and for this application scenario, the logged-in user may trigger a first data processing request for indicating to read the feature data stored in the feature library.
Taking the first data request as an example of a data reading request for indicating to read feature data in the target feature database, the responding to the first data processing request may include:
and reading the feature data in the target feature library, and displaying the read feature data.
In practical application, if the first data processing request is determined to be a data reading request, the first data processing request can be analyzed to determine whether the first data processing request carries the feature group identifier, if the first data processing request does not carry the feature group identifier, the feature data of all the feature groups in the target feature library are read, and the read feature data are displayed; if the first feature data processing request carries a feature group identifier, determining a feature group corresponding to the feature group identifier in a target feature library as a target feature group, and reading and displaying feature data in the target feature group.
Specifically, when the read characteristic data is displayed, the display can be performed in a form of a table, so that the display is more visual and is convenient to understand.
Further, if the target login user does not have the right corresponding to the first data processing request to the target feature library, the first data processing request is refused.
Still further, after rejecting the first data processing request, a prompt message for indicating that the authority verification of the current first data processing request fails may be generated, and the prompt message is displayed to prompt the target login user that the authority verification fails.
According to the feature data processing method provided by the embodiment of the application, a first data processing request of a target login user aiming at a target feature library is received, whether the target login user has the authority corresponding to the first data processing request to the target feature library is verified according to a preset first corresponding relation, a second corresponding relation and a third corresponding relation, if the target login user has the authority corresponding to the first data processing request to the target feature library, the first corresponding relation is the corresponding relation between the feature library and a virtual user, the second corresponding relation is the corresponding relation between the virtual user and a project, and the third corresponding relation is the corresponding relation between the login user and the project. In the scheme, the authority of the target login user to the target feature library is verified through the three corresponding relations, and the first data processing request is responded and processed only when the target login user is determined to have the authority corresponding to the first data processing request to the target feature library, so that the safety of feature data in the feature library is improved.
Furthermore, the scheme enables the feature library and the login user to be associated through the virtual user and the project, so that the direct relationship between the feature library and the login user is decoupled, and rights management and sharing of the feature library are facilitated.
Furthermore, by setting the virtual user, the feature library and the project are associated through the virtual user, so that the direct association between the feature library and the project is decoupled, the coupling between the feature data management system and the project system is also relieved, and when the project is renamed or changed, only the project system is required to be changed, the feature data management system is not required to be changed, and the operation and maintenance cost is reduced.
At present, in the deep learning process, a user usually selects a storage mode to store feature data by using a text or wiki (a hypertext system which is opened on a network and can be used for collaborative creation of multiple persons) and other modes, and a corresponding feature library is established, so that the subsequent understanding is difficult and the maintenance is not facilitated.
In order to solve the above problem, referring to fig. 3, a feature data processing method according to another embodiment of the present invention, as shown in fig. 3, the feature data processing method may include the following steps:
S30: and creating a target feature library according to a preset feature data storage structure.
In the embodiment of the invention, after the feature engineering is performed on the sample data for deep learning, the obtained feature data needs to be stored for later use in model training. When the feature data is stored, a feature library for storing the feature data can be newly created. In the embodiment of the invention, a feature data storage structure can be provided in advance, and then when the feature library is created, the feature data storage structure is created according to the preset feature data storage structure, so that the standardization of feature data storage is realized. In the embodiment of the invention, the characteristic data storage structure can be a multi-level structure, such as a secondary structure, a tertiary structure, a quaternary structure and the like, and the specific characteristic data storage structure can be customized according to actual requirements.
S31, receiving a first data processing request of a target login user aiming at a target feature library.
S32, verifying whether the target login user has the right corresponding to the first data processing request to the target feature library according to a preset first corresponding relation, a preset second corresponding relation and a preset third corresponding relation.
S33, if the target login user has the right corresponding to the first data processing request to the target feature library, responding to the first data processing request.
The above S31-S33 can be referred to the description of S11-S13, and will not be repeated here.
The target feature library shown in S30 and the method of creating the same will be described below.
As an embodiment, referring to fig. 4, a schematic diagram of a Feature data storage structure provided in an embodiment of the present application is shown in fig. 4, where the Feature data storage structure is a three-level structure, specifically includes a first level FeatureStore, a second level FeatureGroup, and a third level Feature. One of the feature libraries may include at least one feature set, and one of the feature sets may include at least one feature data.
The above three-level structure is merely exemplary, and does not constitute a limitation of the feature data storage structure, and the feature data storage structure may be a multi-level structure such as a four-level structure, in addition to the three-level structure, and the embodiment of the present invention is not limited thereto.
The process of creating the feature library will be described below taking as an example the creation of a target feature library for storing a target feature data set.
Referring to fig. 5, when creating a target feature library according to the feature data storage structure shown in fig. 4, the following steps may be included:
s51, receiving a second data processing request.
In an embodiment of the invention, the second data processing request is for indicating to create a target feature library for storing the target feature dataset. Specifically, the second data processing request may carry the target feature data set.
As one embodiment, the target feature data set is composed of a plurality of feature data, wherein the plurality of feature data may be feature data obtained by feature extraction of sample data by feature engineering.
Preferably, the feature data in the target feature data set is feature data obtained by subjecting the same set of sample data to feature engineering, wherein the data in the same set of sample data are related logically or in service, for example, the same set of sample data may be sample data obtained in the same deep learning.
For example, if user behavior data of a plurality of users are acquired as sample data for deep learning of user behavior in the video player a, the user behavior data of the plurality of users belong to the same set of sample data. By constructing the target feature data set in this way, it can be ensured that there is a logical or business association between feature data in the target feature data set, that is, it is further ensured that there is a logical or business association between feature data in the created target feature library.
In the embodiment of the invention, when the sample data is subjected to feature extraction to construct the target feature data set, the sample data can be subjected to feature extraction from multiple dimensions, and feature types corresponding to the feature data extracted from different dimensions are different, so that the target feature data set can contain the feature data of multiple different feature types.
One dimension corresponds to one feature type, and after feature extraction is performed on sample data according to a certain dimension, the feature type of the obtained feature data is the feature type corresponding to the dimension. Under different application scenes, feature extraction can be performed from different dimensions, so that feature data of different feature types are obtained. And as to which dimensions to extract features from, it can be set according to actual requirements.
The sample data are user behavior data of a plurality of users in the video player a, when the sample data are subjected to feature extraction in an application scene of analyzing the user behavior of the video player a, the sample data can be respectively subjected to feature extraction from two dimensions of the user viewing behavior and the user searching behavior, specifically, the sample data can be divided into two types, one type is the user viewing behavior data, the other type is the user searching behavior data, and then the feature extraction is performed on the two types of behavior data respectively, so that feature data with feature types being the user viewing behavior and feature data with feature types being the user searching behavior are obtained, and further feature data with feature types being the user viewing behavior and the user searching behavior are contained in a feature data set constructed based on the obtained feature data.
S52, clustering the feature data in the target feature data set according to the feature types of the feature data in the target feature data set to obtain a plurality of feature groups.
In the embodiment of the invention, in order to facilitate the clustering of the feature data, when a target feature data set is constructed, a corresponding feature type label can be added to the feature data, then when the clustering is performed, the feature data belonging to the same feature type can be divided into the same feature group according to the feature type label, and the feature data belonging to different feature types can be divided into different feature groups, so that the feature types of the feature data of the same feature group are the same, and the feature types of the feature data of any two feature groups are different.
Taking the example that the target feature data set contains feature data of two feature types of user watching behaviors and user searching behaviors, when the feature data in the target feature data set are clustered, the feature data of which all feature types are the user watching behaviors are divided into one feature group, and the feature data of which all feature types are the user searching behaviors are divided into another feature group, so that two different feature groups are obtained.
Further, after a plurality of feature groups are obtained by clustering, a feature group identifier may be set for each feature group, so as to distinguish the feature groups, where the feature group identifiers corresponding to different feature groups are different. Specifically, in order to facilitate intuitive understanding of the feature type of the feature data included in the feature group, the feature group identifier may be set according to the feature type of the feature data in the feature group, for example, the feature group identifier of the feature group to which the user viewing behavior feature data belongs is set as "user viewing behavior feature group", and the feature group identifier of the feature group to which the user searching behavior feature data belongs is set as "user searching behavior feature group". Of course, the above manner of setting the feature group identifier is merely exemplary, and the feature group identifier may be specifically set according to actual requirements, which is not limited to this embodiment of the present invention.
S53, forming a target feature library by the feature groups.
In the embodiment of the invention, the obtained plurality of feature groups are stored into the target feature library as the next stage of the target feature library according to a preset three-stage feature data storage structure.
Furthermore, in order to facilitate the distinguishing and searching of the target feature library, feature library identifiers may be set for the target feature library, and different feature libraries correspond to different feature library identifiers. For example, in order to facilitate visual understanding of feature data included in the feature library, a feature library identifier of the feature library may be set according to a service to which sample data corresponding to the feature library belongs, for example, a service corresponding to the sample data is a service for analyzing a user behavior, and then the feature library identifier of the feature library may be a user behavior feature library. Of course, the above manner of setting the identifier of the feature library is merely exemplary, and the identifier of the feature library may be specifically set according to actual requirements, which is not limited to this embodiment of the present invention.
S54, determining a target virtual user corresponding to the target feature library.
In the embodiment of the invention, the target virtual user can be determined before the target feature library is created, or can be determined after the target feature library is created.
As an alternative implementation manner, before the creation of the target feature library, a login user creating the target feature library may select a virtual user from virtual users bound by items having a corresponding relationship with the login user as a target virtual user, and add a virtual user identifier of the target virtual user to the second data processing request. Based on the above, the virtual user identifier carried in the second data processing request can be obtained by analyzing the second data processing request, and the virtual user corresponding to the virtual user identifier is determined as the target virtual user.
As another optional implementation manner, after the target feature library is created, a target virtual user selection interface is displayed, where the interface includes multiple virtual user identifiers, virtual users corresponding to the virtual user identifiers are all virtual users bound with items having a corresponding relationship with the login user creating the target feature library, then the login user creating the target feature library can select one from the multiple displayed virtual user identifiers, and finally it is determined that the virtual user corresponding to the selected virtual user identifier is the target virtual user.
S55, creating a first corresponding relation between the target feature library and the target virtual user.
In the embodiment of the invention, the corresponding relation between the target feature library and the target virtual user is created, namely, the corresponding relation between the feature library identification of the target feature library and the virtual user identification of the target virtual user is created, and the corresponding relation between the created feature library identification of the target feature library and the virtual user identification of the target virtual user is stored into the first corresponding relation, so that the target virtual user corresponding to the target feature library can be determined according to the first corresponding relation.
The method provided by the embodiment of the invention realizes the storage standardization of the characteristic data, and the characteristic data is easier to understand and maintain by grouping the characteristic data, so that the understanding and maintenance cost is reduced.
On the basis of any one of the above embodiments, the feature data processing method provided by the present invention may further include:
and receiving a permission editing request, wherein the permission editing request is used for indicating to adjust the target corresponding relation, the target corresponding relation is at least one of a first corresponding relation, a second corresponding relation and a third corresponding relation, and the target corresponding relation is adjusted based on the received permission editing request. As an embodiment, the rights editing request may be used to indicate that the first correspondence between a feature library and a virtual user is to be adjusted.
For example, taking the correspondence shown in fig. 2 as an example, if the permission editing request is used to indicate that the virtual user corresponding to the feature library 1 in the first correspondence is changed from user3 to user4, after the first correspondence is adjusted according to the permission editing request, the item corresponding to the feature library 1 is changed from item 1 to item 2, and since there is no third correspondence between the login user a and item 2, the login user a has permission to the feature library 1 and does not have permission to the feature library 1.
As another embodiment, the permission editing request may be used to indicate that the second correspondence between a virtual user and an item is adjusted.
For example, taking the correspondence shown in fig. 2 as an example, if the permission editing request is used to indicate that the item corresponding to the virtual user3 in the second correspondence is changed from the item 1 to the item 2, after the second correspondence is adjusted according to the permission editing request, the item corresponding to the virtual user3 is changed from the item 1 to the item 2, and since there is no third correspondence between the login user a and the item 2, the login user a has permission to the feature library 1 corresponding to the virtual user3, and does not have permission to the feature library 1.
As yet another embodiment, the permission editing request may be used to instruct to adjust a correspondence between a certain logged-in user and an item in the third correspondence.
For example, taking the correspondence shown in fig. 2 as an example, if the permission editing request is used to instruct deletion of the correspondence between the login user a and the project 1 in the third correspondence, after the third correspondence is adjusted according to the permission editing request, the login user a changes from having permission to the feature library corresponding to each virtual user in the project 1 to not having permission to the feature library corresponding to each virtual user in the project 1.
According to the embodiment of the invention, the adjustment of the authority of the login user on the feature library can be realized by adjusting the corresponding relation of the targets based on the authority editing request.
Referring to fig. 6, a schematic diagram of a feature data processing apparatus according to another embodiment of the present invention, as shown in fig. 6, the apparatus may include:
a receiving module 601, configured to receive a first data processing request of a target login user for a target feature library;
the permission verification module 602 is configured to verify whether the target login user has permission corresponding to the first data processing request for the target feature library according to a preset first correspondence, a preset second correspondence, and a preset third correspondence;
The request processing module 603 is configured to enable a target login user to have authority corresponding to a first data processing request on a target feature library, and perform response processing on the first data processing request;
the first corresponding relation is the corresponding relation between the feature library and the virtual user, the second corresponding relation is the corresponding relation between the virtual user and the project, and the third corresponding relation is the corresponding relation between the login user and the project.
As one embodiment, the rights verification module 602 is specifically configured to:
determining a target virtual user corresponding to the target feature library according to the first corresponding relation;
determining a target item corresponding to the target virtual user according to the second corresponding relation;
determining whether a target sub-corresponding relation exists between the target login user and the target item according to the third corresponding relation, wherein the target sub-corresponding relation is used for representing that the target login user has the right corresponding to the first data processing request for the target feature library;
and if a target sub-corresponding relation exists between the target login user and the target item, determining that the target login user has the right corresponding to the first data processing request for the target feature library.
As an embodiment, the rights include access rights or any one of the following rights: read rights, write rights, or edit rights.
As an embodiment, in the first correspondence, one feature library corresponds to one virtual user, and one virtual user corresponds to at least one feature library;
in the second corresponding relation, one virtual user corresponds to one item, and one item corresponds to at least one virtual user;
in the third correspondence, one login user corresponds to at least one item, and one item corresponds to at least one login user.
As an example, the apparatus may further include (not shown in fig. 6): the feature library creation module is specifically configured to:
before receiving a first data processing request of a target login user aiming at a target feature database, receiving a second data processing request, wherein the second data processing request is used for indicating to create the target feature database for storing the target feature data set;
clustering the feature data in the target feature data set according to the feature types of the feature data in the target feature data set to obtain a plurality of feature groups, wherein the feature types of the feature data in the same feature group are the same, and the feature types of the feature data in any two feature groups are different;
Forming a plurality of feature groups into a target feature library;
determining a target virtual user corresponding to the target feature library;
and creating a first corresponding relation between the target feature library and the target virtual user.
As an embodiment, the first data processing request is a data writing request or a data reading request, and the request processing module 603 is specifically configured to:
if the first data processing request is determined to be a data writing request for indicating writing of the first feature data into the target feature library, writing the first feature data into a feature group corresponding to the feature type in the target feature library according to the feature type of the first feature data;
and if the first data processing request is determined to be a data reading request for indicating to read the feature data in the target feature library, the feature data in the target feature library is read, and the read feature data is displayed.
As an example, the apparatus may further include (not shown in fig. 6): the permission editing module is specifically used for:
receiving a permission editing request, wherein the permission editing request is used for indicating to adjust a target corresponding relation, and the target corresponding relation is at least one of the first corresponding relation, the second corresponding relation and the third corresponding relation;
And adjusting the corresponding relation of the targets based on the permission editing request.
In another embodiment of the present application, there is also provided an electronic device, as shown in fig. 7, including a processor 701, a communication interface 702, a memory 703, and a communication bus 704, where the processor 701, the communication interface 702, and the memory 703 complete communication with each other through the communication bus 704;
a memory 703 for storing a computer program;
the processor 701 is configured to implement the steps of the feature data processing method according to any one of the above embodiments when executing the program stored in the memory 703.
The communication bus 704 mentioned above for the electronic device may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The communication bus 704 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 7, but not only one bus or one type of bus.
The communication interface 702 is used for communication between the electronic device and other devices described above.
The memory 703 may include random access memory (Random Access Memory, RAM) or may include non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor 701 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), and the like; but also digital signal processors (Digital Signal Processing, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
In another embodiment of the present application, there is further provided a computer readable storage medium, where a characteristic data processing method program is stored on the computer readable storage medium, and the data processing method program when executed by a processor implements the steps of any one of the characteristic data processing methods described above.
When the embodiment of the invention is specifically implemented, the above embodiments can be referred to, and the invention has corresponding technical effects.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is only a specific embodiment of the invention to enable those skilled in the art to understand or practice the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A method of processing feature data, comprising:
receiving a first data processing request of a target login user aiming at a target feature library;
verifying whether the target login user has the right corresponding to the first data processing request to the target feature library according to a preset first corresponding relation, a second corresponding relation and a third corresponding relation;
if the target login user has the right corresponding to the first data processing request to the target feature library, responding to the first data processing request;
the first corresponding relation is the corresponding relation between the feature library and the virtual user, the second corresponding relation is the corresponding relation between the virtual user and the project, and the third corresponding relation is the corresponding relation between the login user and the project.
2. The method according to claim 1, wherein verifying whether the target login user has the right corresponding to the first data processing request to the target feature library according to the preset first correspondence, second correspondence, and third correspondence includes:
determining a target virtual user corresponding to the target feature library according to the first corresponding relation;
determining a target item corresponding to the target virtual user according to the second corresponding relation;
determining whether a target sub-corresponding relation exists between the target login user and the target item according to the third corresponding relation, wherein the target sub-corresponding relation is used for representing that the target login user has the right corresponding to the first data processing request for the target feature library;
and if a target sub-corresponding relation exists between the target login user and the target item, determining that the target login user has the right corresponding to the first data processing request for the target feature library.
3. The method of claim 2, wherein the rights include at least one of access rights or the following rights: read rights, write rights, or edit rights.
4. The method of claim 2, wherein in the first correspondence, one feature library corresponds to one virtual user, and one virtual user corresponds to at least one feature library;
in the second corresponding relation, one virtual user corresponds to one item, and one item corresponds to at least one virtual user;
in the third correspondence, one login user corresponds to at least one item, and one item corresponds to at least one login user.
5. The method of any one of claims 1-4, further comprising:
before receiving a first data processing request of a target login user aiming at a target feature library, receiving a second data processing request, wherein the second data processing request is used for indicating to create the target feature library for storing a target feature data set;
clustering the feature data in the target feature data set according to the feature type of the feature data in the target feature data set to obtain a plurality of feature groups, wherein the feature types of the feature data in the same feature group are the same, and the feature types of the feature data in any two feature groups are different;
combining a plurality of the features into the target feature library;
Determining a target virtual user corresponding to the target feature library;
and creating a first corresponding relation between the target feature library and the target virtual user.
6. The method of claim 1, wherein the first data processing request is a data write request or a data read request;
the responding processing to the first data processing request comprises the following steps:
if the first data processing request is determined to be a data writing request for indicating writing of first feature data into the target feature library, writing the first feature data into a feature group corresponding to the feature type in the target feature library according to the feature type of the first feature data;
and if the first data processing request is determined to be a data reading request for indicating to read the feature data in the target feature library, the feature data in the target feature library is read, and the read feature data is displayed.
7. The method according to claim 1, wherein the method further comprises:
receiving a permission editing request, wherein the permission editing request is used for indicating to adjust a target corresponding relation, and the target corresponding relation is at least one of the first corresponding relation, the second corresponding relation and the third corresponding relation;
And adjusting the corresponding relation of the targets based on the permission editing request.
8. A feature data processing apparatus, comprising:
the receiving module is used for receiving a first data processing request of a target login user aiming at a target feature library;
the permission verification module is used for verifying whether the target login user has permission corresponding to the first data processing request for the target feature library according to a preset first corresponding relation, a preset second corresponding relation and a preset third corresponding relation;
the request processing module is used for responding to the first data processing request if the target login user has the right corresponding to the first data processing request to the target feature library;
the first corresponding relation is the corresponding relation between the feature library and the virtual user, the second corresponding relation is the corresponding relation between the virtual user and the project, and the third corresponding relation is the corresponding relation between the login user and the project.
9. An electronic device, comprising: a processor and a memory, the processor being configured to execute a data processing program stored in the memory, to implement the characteristic data processing method according to any one of claims 1 to 7.
10. A storage medium storing one or more programs executable by one or more processors to implement the method of processing characteristic data as claimed in any one of claims 1 to 7.
CN202110482756.4A 2021-04-30 2021-04-30 Feature data processing method and device, electronic equipment and storage medium Active CN113127909B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110482756.4A CN113127909B (en) 2021-04-30 2021-04-30 Feature data processing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110482756.4A CN113127909B (en) 2021-04-30 2021-04-30 Feature data processing method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113127909A CN113127909A (en) 2021-07-16
CN113127909B true CN113127909B (en) 2023-07-25

Family

ID=76780731

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110482756.4A Active CN113127909B (en) 2021-04-30 2021-04-30 Feature data processing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113127909B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6862686B1 (en) * 1999-10-29 2005-03-01 International Business Machines Corporation Method and apparatus in a data processing system for the separation of role-based permissions specification from its corresponding implementation of its semantic behavior
CN107302536A (en) * 2017-06-29 2017-10-27 郑州云海信息技术有限公司 Method for managing security, device, medium and the storage control of cloud computing platform
CN107689949A (en) * 2017-03-31 2018-02-13 平安科技(深圳)有限公司 Data base authority management method and system
CN110855772A (en) * 2019-11-08 2020-02-28 北京奇艺世纪科技有限公司 Cross-device data storage method, system, device, server and medium
CN111865885A (en) * 2019-04-30 2020-10-30 中移(苏州)软件技术有限公司 Access control method, device, equipment and storage medium
KR20210038285A (en) * 2019-09-30 2021-04-07 한국전자통신연구원 Apparatus and method for managing integrated storage supporting hierachical structure
CN112637214A (en) * 2020-12-24 2021-04-09 北京金山云网络技术有限公司 Resource access method and device and electronic equipment

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8874951B1 (en) * 2010-04-05 2014-10-28 Cloudpic Global Inc. Private peer-to-peer network platform for secure collaborative production and management of digital assets
EP2407907B1 (en) * 2010-07-16 2017-03-08 BlackBerry Limited Device and method for performing role-based access control
US9423922B2 (en) * 2013-12-24 2016-08-23 Dropbox, Inc. Systems and methods for creating shared virtual spaces

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6862686B1 (en) * 1999-10-29 2005-03-01 International Business Machines Corporation Method and apparatus in a data processing system for the separation of role-based permissions specification from its corresponding implementation of its semantic behavior
CN107689949A (en) * 2017-03-31 2018-02-13 平安科技(深圳)有限公司 Data base authority management method and system
CN107302536A (en) * 2017-06-29 2017-10-27 郑州云海信息技术有限公司 Method for managing security, device, medium and the storage control of cloud computing platform
CN111865885A (en) * 2019-04-30 2020-10-30 中移(苏州)软件技术有限公司 Access control method, device, equipment and storage medium
KR20210038285A (en) * 2019-09-30 2021-04-07 한국전자통신연구원 Apparatus and method for managing integrated storage supporting hierachical structure
CN110855772A (en) * 2019-11-08 2020-02-28 北京奇艺世纪科技有限公司 Cross-device data storage method, system, device, server and medium
CN112637214A (en) * 2020-12-24 2021-04-09 北京金山云网络技术有限公司 Resource access method and device and electronic equipment

Also Published As

Publication number Publication date
CN113127909A (en) 2021-07-16

Similar Documents

Publication Publication Date Title
US11588855B2 (en) Policy approval layer
CN104602131A (en) Barrage processing method and system
US20100100967A1 (en) Secure collaborative environment
KR102062796B1 (en) Sns server, system for providing news using the same and method thereof
CN109829286B (en) User authority management system and method for WEB application
US10769270B2 (en) Password protection question setting method and device
US8397156B2 (en) Organizing documents through utilization of people tags
CN111541546B (en) Multi-platform login method, device, equipment and readable medium
US20140068026A1 (en) System for automatically configuring server using pre-recorded configuration script and method thereof
CN107729768B (en) Page display method and device, intelligent panel and storage medium
CN110928626A (en) Interface switching method and device and electronic equipment
CN104036164A (en) Click type video verification code
CN111199028A (en) Resource information access method and device, computer equipment and storage medium
CN112150030A (en) Account management method based on multiple units and multiple identities, terminal equipment and storage medium
CN106874718B (en) Privacy processing method and device and terminal
US11042583B2 (en) Systems and methods for real-time multi-party recommendation in a peer to peer communication
CN107766743B (en) Method and device for setting file access authority, terminal equipment and storage medium
WO2019227572A1 (en) Association topological graph-based collaborative office processing method and apparatus, device, and medium
CN113127909B (en) Feature data processing method and device, electronic equipment and storage medium
US20170169044A1 (en) Property retrieval apparatus, method and system
US10719541B2 (en) Method and system to capture and find information and relationships
CN111954013B (en) Live broadcast interaction method and device, terminal equipment, server and storage medium
US11373001B2 (en) Screen capturing and masking system and method
KR20100133260A (en) Posting scrap method and system
CN112947844A (en) Data storage method and device, electronic equipment and medium

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
GR01 Patent grant
GR01 Patent grant