Data processing methods, apparatus, electronic devices and storage media

Abstract

This disclosure relates to a data processing method, apparatus, electronic device, and storage medium applied to a server. The method includes: the server receiving a data query request from a target account for target data, and obtaining status information of the target data based on a data identifier; obtaining data to be processed based on pre-acquired configuration information, the data query request, the status information, and role information, and determining the target operation corresponding to the data to be processed. The configuration information indicates the correspondence between role information, status information, and supported operations. The data to be processed is target data within the target data that supports the target account performing the target operation; and in response to the target operation performed by the target account on the data to be processed, performing the corresponding processing on the data to be processed. In this way, target data in different states and different operations on the target data correspond to different account roles, restricting data modification and thus improving data security.

Description

Technical Field

[0001] This disclosure relates to the Internet field, and more particularly to a data processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] Typically, internet platforms maintain data that is pushed to most users, resulting in a wide impact. Examples include banner ad data and subscription data. Currently, data maintenance methods are relatively simplistic, and data management is chaotic. Operators can modify data without restrictions, leading to low data security. Summary of the Invention

[0003] This disclosure provides a data processing method, apparatus, electronic device, and storage medium to at least address the problem of low data security in related technologies. The technical solution of this disclosure is as follows:

[0004] According to a first aspect of the present disclosure, a data processing system method is provided, applied to a server, comprising:

[0005] Receive a data query request from a target account for target data, wherein the data query request carries the account identifier of the target account and the data identifier of the target data;

[0006] Based on the account identifier, obtain the role information of the target account, and based on the data identifier, obtain the status information of the target data;

[0007] Based on the pre-acquired configuration information, the data query request, the status information, and the role information, the data to be processed is obtained, and the target operation corresponding to the data to be processed is determined. The configuration information is used to indicate the correspondence between role information, status information, and supported operations. The data to be processed is the data in the target data that supports the target account to perform the target operation.

[0008] In response to the target operation of the target account on the data to be processed, the data to be processed is processed according to the target operation.

[0009] Optionally, the configuration information includes a set of supported operations corresponding to each status information, a first set of role information supporting viewing data for each status information, and a second set of role information supporting executing each operation; the step of obtaining the data to be processed based on the pre-acquired configuration information, the data query request, the status information, and the role information, and determining the target operation corresponding to the data to be processed, includes:

[0010] If the target account's role information is included in the first role information corresponding to the status information of the target data, the target data is treated as data to be processed, and the data to be processed is obtained based on the data query request.

[0011] Candidate operations are determined from the set of supported operations corresponding to the state information of the data to be processed;

[0012] If the second set of candidate operations includes the role information of the target account, the candidate operation is determined as the target operation corresponding to the data to be processed.

[0013] Optionally, obtaining the role information of the target account based on the account identifier further includes:

[0014] Based on the data identifier, obtain the creator information of the target data;

[0015] If the creator information matches the account identifier of the target account, add the creator role to the role information of the target account.

[0016] Optionally, the configuration information includes a set of supported operations corresponding to each state information and a set of second role information that supports the execution of each operation;

[0017] Before performing the processing corresponding to the target operation on the data to be processed in response to the target account's target operation on the data to be processed, the method further includes:

[0018] The data to be processed and the corresponding target operation are displayed.

[0019] The step of responding to the target operation of the target account on the data to be processed, and performing the processing corresponding to the target operation on the data to be processed, includes:

[0020] In response to the target operation of the target account on the data to be processed, obtain the operation identifier corresponding to the target operation and the operation data identifier corresponding to the data to be processed;

[0021] Based on the operation data identifier, obtain the status information of the data to be processed;

[0022] If the operation identifier of the target operation is included in the set of supported operations corresponding to the status information of the operation to be processed, and the role information of the target account is included in the second role set of the target operation, then the data to be processed is processed according to the target operation.

[0023] Optionally, the target data has an online version and a local version. The step of responding to a target operation by the target account on the data to be processed, and performing the processing corresponding to the target operation on the data to be processed, includes:

[0024] In response to the target operation of the target account on the data to be processed, the local version of the data to be processed is processed according to the target operation.

[0025] After the local version of the data to be processed is approved for the processing corresponding to the target operation, the online version of the data to be processed is then processed for the same target operation.

[0026] Optionally, before receiving the data query request for target data from the target account, the method further includes:

[0027] In response to a request to create target data, a local version of the target data is created;

[0028] After the local version of the target data is approved, an online version of the target data is created.

[0029] Optionally, the method further includes:

[0030] In response to a deletion request for any target data, delete both the local and online versions of the target data.

[0031] According to a second aspect of the present disclosure, a data processing apparatus is provided, applied to a server, comprising:

[0032] The receiving unit is configured to execute a data query request for target data from a target account, wherein the data query request carries the account identifier of the target account and the data identifier of the target data;

[0033] The acquisition unit is configured to perform actions such as acquiring the role information of the target account based on the account identifier, and acquiring the status information of the target data based on the data identifier.

[0034] The determining unit is configured to execute, based on pre-acquired configuration information, the data query request, the status information, and the role information, acquire data to be processed, and determine the target operation corresponding to the data to be processed. The configuration information is used to indicate the correspondence between role information, status information, and supported operations. The data to be processed is the data in the target data that supports the target account to perform the target operation.

[0035] The operation unit is configured to perform a target operation in response to the target account on the data to be processed, and to process the data to be processed in accordance with the target operation.

[0036] Optionally, the configuration information includes a set of supported operations for each status information, a first set of role information supporting viewing data for each status information, and a second set of role information supporting executing each operation; the determining unit is specifically configured to execute:

[0037] If the target account's role information is included in the first role information corresponding to the status information of the target data, the target data is treated as data to be processed, and the data to be processed is obtained based on the data query request.

[0038] Candidate operations are determined from the set of supported operations corresponding to the state information of the data to be processed;

[0039] If the second set of candidate operations includes the role information of the target account, the candidate operation is determined as the target operation corresponding to the data to be processed.

[0040] Optionally, the acquisition unit is specifically configured to execute:

[0041] Based on the data identifier, obtain the creator information of the target data;

[0042] If the creator information matches the account identifier of the target account, add the creator role to the role information of the target account.

[0043] Optionally, the configuration information includes a set of supported operations corresponding to each state information and a set of second role information supporting the execution of each operation; the operation unit is configured to execute:

[0044] The data to be processed and the corresponding target operation are displayed.

[0045] In response to the target operation of the target account on the data to be processed, obtain the operation identifier corresponding to the target operation and the operation data identifier corresponding to the data to be processed;

[0046] Based on the operation data identifier, obtain the status information of the data to be processed;

[0047] If the operation identifier of the target operation is included in the set of supported operations corresponding to the status information of the operation to be processed, and the role information of the target account is included in the second role set of the target operation, then the data to be processed is processed according to the target operation.

[0048] Optionally, the target data has an online version and a local version, and the operation unit is further configured to execute:

[0049] In response to the target operation of the target account on the data to be processed, the local version of the data to be processed is processed according to the target operation.

[0050] After the local version of the data to be processed is approved for the processing corresponding to the target operation, the online version of the data to be processed is then processed for the same target operation.

[0051] Optionally, the device further includes:

[0052] The creation unit is configured to perform actions in response to a creation request for target data, including creating a local version of the target data and, after the local version of the target data is approved, creating an online version of the target data.

[0053] Optionally, the device further includes:

[0054] The deletion unit is configured to delete both the local and online versions of the target data in response to a deletion request for any target data.

[0055] According to a third aspect of the present disclosure, a data processing electronic device is provided, comprising:

[0056] processor;

[0057] Memory used to store the processor's executable instructions;

[0058] The processor is configured to execute the instructions to implement the data processing method described in the first item above.

[0059] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the data processing method described in the first item above.

[0060] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the data processing method described in the first item above.

[0061] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0062] The server receives a data query request from the target account for target data. The data query request carries the account identifier of the target account and the data identifier of the target data. Based on the account identifier, the server obtains the role information of the target account and the status information of the target data. Based on the pre-obtained configuration information, data query request, status information, and role information, the server obtains the data to be processed and determines the target operation corresponding to the data to be processed. The configuration information is used to indicate the correspondence between role information, status information, and supported operations. The data to be processed is the target data that supports the target account in performing the target operation. In response to the target operation of the target account on the data to be processed, the server performs the corresponding processing on the data to be processed.

[0063] In this way, based on the different role information corresponding to different accounts and the status information of different target data, different operation permissions can be set in the configuration information in advance. This allows different target data in different statuses and different operations on the target data to correspond to different account roles, thus restricting the modification of data and improving data security.

[0064] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0065] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0066] Figure 1 This is a flowchart illustrating a data processing method according to an exemplary embodiment.

[0067] Figure 2 This is a schematic diagram of role permissions according to an exemplary embodiment.

[0068] Figure 3 This is a logical schematic diagram illustrating one embodiment of the present solution according to an exemplary embodiment.

[0069] Figure 4 This is a schematic diagram illustrating a conversion process between an online version and a local version according to an exemplary embodiment.

[0070] Figure 5 This is a schematic diagram illustrating the conversion logic between an online version and a local version according to an exemplary embodiment.

[0071] Figure 6 This is a block diagram illustrating a data processing apparatus according to an exemplary embodiment.

[0072] Figure 7This is a block diagram illustrating an electronic device for data processing according to an exemplary embodiment.

[0073] Figure 8 This is a block diagram illustrating an apparatus for data processing according to an exemplary embodiment. Detailed Implementation

[0074] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0075] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0076] Figure 1 This is a flowchart illustrating a data processing method according to an exemplary embodiment, applied to an electronic device, such as... Figure 1 As shown, the data processing method includes the following steps.

[0077] In step S11, a data query request for target data from the target account is received. The data query request carries the account identifier of the target account and the data identifier of the target data.

[0078] In some scenarios, the platform maintains data such as banner ad space data or subscription data, which can be modified by different accounts on the platform. When a target account needs to process target data, it first needs to send a data query request to the server, carrying an account identifier and a data identifier. The account identifier uniquely corresponds to the target account, and the data identifier uniquely corresponds to the target data.

[0079] In one implementation, the target data has an online version and a local version. Before receiving a data query request for the target data from the target account, the following steps can be performed: in response to a creation request for the target data, a local version of the target data is created; after the local version of the target data is approved, an online version of the target data is created.

[0080] In other words, upon receiving a request to create target data, the target data can be created locally first. Then, approval is initiated for the target data. Once approved, the target data is synchronized to the online table. This approach has two advantages: firstly, by approving the target data before deployment, the number of modifications to online data is reduced, saving system bandwidth and maintaining system stability; secondly, since the target data is created locally and then synchronized online, both online and local data originate from the same data source, facilitating data synchronization. Furthermore, before initiating approval for the target data, operations personnel can verify it, further improving data accuracy and reducing the system resource consumption caused by multiple data modifications. Moreover, when other accounts query the target data, they see the online version, while the account that created the target data sees the local version. This means other accounts cannot modify the local version of the target data, enhancing data security.

[0081] In one implementation, this disclosure may further include the following steps: in response to a deletion request for any target data, deleting both the local and online versions of the target data.

[0082] In other words, upon receiving a request to delete the target data, both the local and online versions of the target data need to be deleted simultaneously. This helps maintain the consistency between the online and local data, thereby ensuring the synchronization of the two versions of the data.

[0083] For example, two tables with essentially the same structure can be created: an online table and a local table. The purpose is to maintain two versions of data for each record: an online version and a local version, with the same unique identifier for both versions. The local table has a local account field containing multiple statuses such as "Editing," "Approving," "Approved Successfully," "Live," and "Deleted," while the online table only contains "Live" and "Deleted." Upon receiving a request to create target data, a new record is first added to the local table to create the target data. Then, the target data can be approved. After approval, the status of the target data recorded in the local table is changed to "Live," and this target data is simultaneously synchronized to the online table. Upon receiving a request to delete target data, the target data is deleted from both the online and local tables.

[0084] In step S12, the role information of the target account is obtained based on the account identifier, and the status information of the target data is obtained based on the data identifier.

[0085] In this disclosure, each account has a corresponding role, and each piece of data has a corresponding status. Different account roles and different data statuses can correspond to different operation permissions. For example, the relationships between account (user), account role (role), role permission (permission), target data (data), target data status (status), and operation action (action) include, but are not limited to:

[0086] An account has multiple roles, meaning each role has multiple permissions; the relationship between the two is many-to-many. A piece of data has only one status at a time. The status can change under the action, for example, it can change from status A to status B. Status and action form a directed graph. Permissions are divided into read permissions and access permissions, which correspond to the status and action of the data, respectively.

[0087] In one implementation, obtaining the role information of the target account based on the account identifier further includes: obtaining the creator information of the target data based on the data identifier; and adding the creator role to the role information of the target account if the creator information matches the account identifier of the target account.

[0088] In this way, for the data created, the creating account will have an additional creator role. Creators and non-creators are different roles, and different operation permissions can be set for them. For example, it can be set that only the creator can edit and modify the target data, etc., which helps to improve data security, enriches the application scenarios of this solution, and makes the setting of account roles more flexible.

[0089] For example, account roles can include, but are not limited to, regular users and administrators. Additionally, for the data being created, the account will have an extra creator role. Data status includes, but is not limited to, under modification, under approval, live, and deleted. Operations on the data include, but are not limited to, data creation, application for live deployment, approval approved, approval rejected, application withdrawn, and deletion. Specific settings can be customized according to user needs; this application does not impose any limitations on this.

[0090] like Figure 2The diagram shown illustrates the role-based access control scheme in this implementation. The parentheses indicate the role corresponding to the given state or operation: A represents administrator, B represents regular user, and C represents creator. Administrators can see all data; regular users can only create data and submit / withdraw applications for their own data. Administrators can create data, submit / withdraw applications for their own data, and approve or reject applications. Regular users can see the data they created and the data created by other users that is already online.

[0091] In step S13, based on the pre-acquired configuration information, data query request, status information and role information, the data to be processed is obtained, and the target operation corresponding to the data to be processed is determined. The configuration information is used to indicate the correspondence between role information, status information and supported operations. The data to be processed is the target data that supports the target account to perform the target operation.

[0092] As mentioned above, each account has a corresponding role, and each piece of data has a corresponding status. Different account roles and different data statuses can correspond to different operation permissions. In this step, in response to a data query request, the data to be processed can be obtained based on the role information of the target account and the status information of the target data, and the target operation corresponding to the data to be processed can be determined.

[0093] In one implementation, the configuration information includes a set of supported operations for each state information, a first set of role information supporting viewing data for each state information, and a second set of role information supporting executing each operation. Therefore, the steps of obtaining the data to be processed and determining the target operation corresponding to the data to be processed based on the pre-acquired configuration information, data query request, state information, and role information may specifically include:

[0094] If the target data's status information includes the target account's role information in the first role information, the target data is treated as data to be processed, and the data to be processed is obtained based on the data query request; candidate operations are determined from the set of supported operations corresponding to the status information of the data to be processed; if the target account's role information is included in the second role set of candidate operations, the candidate operation is determined as the target operation corresponding to the data to be processed.

[0095] In other words, the process first determines whether the target account's current role supports viewing the target data in its current state. If the target account's role information is included in the first role information corresponding to a certain target data, it means that the target account's current role supports viewing the target data. In this case, the target data can be retrieved in response to a data query request and treated as data to be processed. Next, the operations supported by the data to be processed are determined as candidate operations. As mentioned earlier, different operations correspond to different supported roles. Therefore, it is necessary to further determine whether the target account's current role is included in the roles supporting the candidate operations. If the target account's role information is included in the second set of candidate operations, then the selected candidate operation can be used as the target operation for the data to be processed.

[0096] In this way, based on the different role information corresponding to different accounts and the status information of different target data, different operation permissions can be pre-set in the configuration information. This allows different target data in different states and different operations on the target data to correspond to different account roles. Simply put, based on the configuration information, it can be determined which operations the target account in the current state can perform on the target data in the current state. This realizes the setting of operation permissions for different accounts, which restricts the modification of data by accounts and thus improves data security.

[0097] After acquiring the data to be processed, it can be displayed on the data list page. In other words, based on the current status of each data entry, the current account's role, and configuration data, filtering and distribution are performed; based on the current status of each data entry and the current account's role, supported actions are retrieved from the configuration and displayed as corresponding buttons on the page.

[0098] The meanings of each field in the pre-acquired configuration information are shown in the table below:

[0099] Table 1. Fields and their meanings in the configuration information.

[0100]

[0101] In step S14, in response to the target operation on the data to be processed by the target account, the data to be processed is processed according to the target operation.

[0102] As mentioned above, based on the target account's role information and the target data's status information, the data to be processed can be obtained, and the target operation corresponding to the data to be processed can be determined. The target operation is the executable operation that the target account has permission to perform on the data to be processed in its current state. Therefore, in this step, if an operation instruction for the target operation is received, the system can respond to the target account's target operation on the data to be processed and perform the corresponding processing on the data to be processed. The target operation can include, but is not limited to, editing, deleting, copying, etc., without specific limitations.

[0103] In one implementation, the configuration information includes a set of supported operations corresponding to each type of status information and a set of second role information supporting the execution of each operation. Before processing the data to be processed in response to a target operation by the target account, the data to be processed and the corresponding target operation can be displayed. Then, in response to the target operation by the target account, the operation identifier corresponding to the target operation and the operation data identifier corresponding to the data to be processed are obtained. Based on the operation data identifier, the status information of the data to be processed is obtained. If the set of supported operations corresponding to the status information of the data to be processed includes the operation identifier of the target operation, and the second role set of the target operation includes the role information of the target account, then the data to be processed is processed according to the target operation.

[0104] In other words, after acquiring the data to be processed and determining the target operation corresponding to the data, the system can display the data to be processed and the corresponding target operation. For example, the data to be processed can be displayed in the form of a list, while the corresponding target operation can be displayed as a right-click menu or an operation button; there are no specific limitations. This allows for a more intuitive display of the target operations that the current target account can perform on the target data, making it easier for users to identify and process them promptly, thus improving user experience and processing efficiency.

[0105] For example, such as Figure 3 The diagram shown illustrates one possible logic of this solution. The configuration center filters and distributes configuration data based on the current state of each data entry and the current user's role. The server retrieves the current state and supported actions for each role from the configuration data, displaying the corresponding buttons on the webpage. When a user clicks a button on the webpage, the server calls the backend's interface to modify the state, reporting the data identifier and operation identifier. The server determines whether the user has permission to perform the corresponding operation based on their role and the current state of the data. If permission is granted, the data is set to the next state after the operation; otherwise, the data is not modified.

[0106] In one implementation, when the target data has both an online version and a local version, in response to a target operation on the data to be processed by the target account, the data to be processed is processed according to the target operation, including:

[0107] In response to the target account's target operation on the data to be processed, the local version of the data to be processed is processed accordingly; after the local version of the data to be processed is approved for the target operation, the online version of the data to be processed is processed accordingly.

[0108] In this way, on the one hand, the target data is approved before going online, which reduces the number of times the online data needs to be modified, saves system bandwidth, and helps maintain system stability. On the other hand, the target data is created locally first and then synchronized from local to online. Therefore, the online data and local data come from the same data source, which helps maintain data synchronization.

[0109] For example, such as Figure 4 The diagram illustrates the conversion process between the online and local versions. The parentheses indicate the roles corresponding to the state or operation: A represents the administrator, B represents a regular user, and C represents the creator. After the target account's request is sent to the server, the server can query all non-deleted local data, iterate through the local data, and if the user is present locally, apply the local version of the current data; otherwise, it finds and applies the corresponding online version of the data based on the unique identifier, and then returns all the applied data to the client. Since operational data is generally small, it's advisable to store the data in memory and synchronize it periodically to ensure high performance of the user-side interface.

[0110] For example, such as Figure 5 The diagram illustrates the conversion logic between the online and local versions. The data in the local table can also be referred to as whitelist data. After the client requests the server, the server queries the database for all whitelisted data that is not currently offline. Then, the server iterates through the whitelist data. If the user is on the whitelist, the whitelist version of the current data is applied. Otherwise, if the user is not on the whitelist, the server uses a unique identifier to find and apply the corresponding online version of the data. Finally, the server returns all the applied data to the client.

[0111] As can be seen from the above, the technical solution provided by the embodiments of this disclosure can pre-set different operation permissions in the configuration information according to the different role information corresponding to different accounts and the status information of different target data. This allows different target data in different states and different operations on the target data to correspond to different account roles, thus restricting the modification of data and improving data security.

[0112] Figure 6 This is a block diagram of a data processing apparatus according to an exemplary embodiment, applied to a server, the apparatus comprising:

[0113] The receiving unit 201 is configured to execute a data query request for target data from a target account, wherein the data query request carries the account identifier of the target account and the data identifier of the target data;

[0114] The acquisition unit 202 is configured to perform the following operations: acquiring the role information of the target account based on the account identifier, and acquiring the status information of the target data based on the data identifier;

[0115] The determining unit 203 is configured to perform actions based on pre-acquired configuration information, the data query request, the status information, and the role information to obtain data to be processed and determine the target operation corresponding to the data to be processed. The configuration information is used to indicate the correspondence between role information, status information, and supported operations. The data to be processed is the data in the target data that supports the target account to perform the target operation.

[0116] The operation unit 204 is configured to perform a target operation on the data to be processed in response to the target account, and to process the data to be processed in accordance with the target operation.

[0117] In one implementation, the configuration information includes a set of supported operations corresponding to each state information, a first set of role information supporting viewing data for each state information, and a second set of role information supporting executing each operation; the determining unit 203 is specifically configured to execute:

[0118] If the target account's role information is included in the first role information corresponding to the status information of the target data, the target data is treated as data to be processed, and the data to be processed is obtained based on the data query request.

[0119] Candidate operations are determined from the set of supported operations corresponding to the state information of the data to be processed;

[0120] If the second set of candidate operations includes the role information of the target account, the candidate operation is determined as the target operation corresponding to the data to be processed.

[0121] In one implementation, the acquisition unit 202 is specifically configured to execute:

[0122] Based on the data identifier, obtain the creator information of the target data;

[0123] If the creator information matches the account identifier of the target account, add the creator role to the role information of the target account.

[0124] In one implementation, the configuration information includes a set of supported operations corresponding to each type of status information and a set of second role information supporting the execution of each operation; the operation unit 204 is configured to execute:

[0125] The data to be processed and the corresponding target operation are displayed.

[0126] In response to the target operation of the target account on the data to be processed, obtain the operation identifier corresponding to the target operation and the operation data identifier corresponding to the data to be processed;

[0127] Based on the operation data identifier, obtain the status information of the data to be processed;

[0128] If the operation identifier of the target operation is included in the set of supported operations corresponding to the status information of the operation to be processed, and the role information of the target account is included in the second role set of the target operation, then the data to be processed is processed according to the target operation.

[0129] In one implementation, the target data has an online version and a local version, and the operation unit 204 is further configured to execute:

[0130] In response to the target operation of the target account on the data to be processed, the local version of the data to be processed is processed according to the target operation.

[0131] After the local version of the data to be processed is approved for the processing corresponding to the target operation, the online version of the data to be processed is then processed for the same target operation.

[0132] In one implementation, the apparatus further includes:

[0133] The creation unit is configured to perform actions in response to a creation request for target data, including creating a local version of the target data and, after the local version of the target data is approved, creating an online version of the target data.

[0134] In one implementation, the apparatus further includes:

[0135] The deletion unit is configured to delete both the local and online versions of the target data in response to a deletion request for any target data.

[0136] As can be seen from the above, the technical solution provided by the embodiments of this disclosure can pre-set different operation permissions in the configuration information according to the different role information corresponding to different accounts and the status information of different target data. This allows different target data in different states and different operations on the target data to correspond to different account roles, thus restricting the modification of data and improving data security.

[0137] Figure 7 This is a block diagram illustrating an electronic device for data processing according to an exemplary embodiment.

[0138] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory including instructions that can be executed by a processor of an electronic device to perform the above-described method. Optionally, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data processing device, etc.

[0139] In an exemplary embodiment, a computer program product is also provided, which, when run on a computer, enables the computer to perform the above-described data processing method.

[0140] As can be seen from the above, the technical solution provided by the embodiments of this disclosure can pre-set different operation permissions in the configuration information according to the different role information corresponding to different accounts and the status information of different target data. This allows different target data in different states and different operations on the target data to correspond to different account roles, thus restricting the modification of data and improving data security.

[0141] Figure 8 This is a block diagram illustrating an apparatus 800 for data processing according to an exemplary embodiment.

[0142] For example, device 800 can be a mobile phone, computer, digital broadcasting electronic device, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0143] Reference Figure 8 The device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0144] Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0145] Memory 804 is configured to store various types of data to support the operation of device 800. Examples of this data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-direct memory (EEPROM), erasable programmable read-direct memory (EPROM), programmable read-direct memory (PROM), read-direct memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0146] Power supply component 807 provides power to various components of device 800. Power supply component 807 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 800.

[0147] Multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0148] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when device 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

[0149] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0150] Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of device 800. For example, sensor assembly 814 may detect the on / off state of device 800, the relative positioning of components such as the display and keypad of device 800, changes in the position of device 800 or a component of device 800, the presence or absence of user contact with device 800, the orientation or acceleration / deceleration of device 800, and temperature changes of device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0151] Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices. Device 800 can access wireless networks based on communication standards, such as WiFi, carrier networks (such as 2G, 3G, 4G, or 5G), or combinations thereof. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0152] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described in the first and second aspects.

[0153] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of the device 800 to perform the above-described method. Optionally, for example, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data processing device.

[0154] In an exemplary embodiment, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to perform the data processing method described in the first embodiment above.

[0155] As can be seen from the above, the technical solution provided by the embodiments of this disclosure can pre-set different operation permissions in the configuration information according to the different role information corresponding to different accounts and the status information of different target data. This allows different target data in different states and different operations on the target data to correspond to different account roles, thus restricting the modification of data and improving data security.

[0156] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0157] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A data processing method, characterized by, The method comprises: receiving a data query request of a target account to target data, the data query request carrying an account identifier of the target account and a data identifier of the target data; obtaining role information of the target account according to the account identifier, and obtaining state information of the target data according to the data identifier; based on pre-obtained configuration information, the data query request, the state information and the role information, obtaining to-be-processed data, and determining a target operation corresponding to the to-be-processed data, the configuration information being used to indicate a corresponding relationship among role information, state information and supportable operations, the to-be-processed data being data in the target data that supports the target account to perform the target operation, the target operation corresponding to the to-be-processed data being judging whether a current role of the target account supports viewing the target data in a current state; performing processing corresponding to the target operation on the to-be-processed data in response to the target operation of the target account on the to-be-processed data; the configuration information comprising a supportable operation set corresponding to each state information, a first role information set supporting viewing data in each state information, and a second role information set supporting performing each operation; the obtaining to-be-processed data and determining a target operation corresponding to the to-be-processed data based on pre-obtained configuration information, the data query request, the state information and the role information comprises: in a case where the role information of the target account is included in the first role information corresponding to the state information of the target data, taking the target data as to-be-processed data, and obtaining the to-be-processed data based on the data query request; determining a candidate operation from the supportable operation set corresponding to the state information of the to-be-processed data; in a case where the role information of the target account is included in the second role set of the candidate operation, determining the candidate operation as the target operation corresponding to the to-be-processed data.

2. The data processing method according to claim 1, characterized in that, The obtaining role information of the target account according to the account identifier further comprises: obtaining creator information of the target data according to the data identifier; in a case where the creator information matches the account identifier of the target account, adding a creator role in the role information of the target account.

3. The data processing method of claim 1, wherein, The configuration information comprises a supportable operation set corresponding to each state information and a second role information set supporting performing each operation; before the performing processing corresponding to the target operation on the to-be-processed data in response to the target operation of the target account on the to-be-processed data, the method further comprises: displaying the to-be-processed data and the corresponding target operation; the performing processing corresponding to the target operation on the to-be-processed data in response to the target operation of the target account on the to-be-processed data comprises: in response to the target operation of the target account on the to-be-processed data, obtaining an operation identifier corresponding to the target operation and an operation data identifier corresponding to the to-be-processed data; obtaining state information of the to-be-processed data according to the operation data identifier; In a case where the operation identifier of the target operation is included in the set of supportable operations corresponding to the state information of the to-be-processed operation, and the role information of the target account is included in the second role set of the target operation, performing processing corresponding to the target operation on the to-be-processed data.

4. The data processing method of claim 1, wherein, The target data has an online version and a local version, and the processing corresponding to the target operation on the to-be-processed data in response to the target operation of the target account on the to-be-processed data comprises: performing processing corresponding to the target operation on the local version of the to-be-processed data in response to the target operation of the target account on the to-be-processed data; performing processing corresponding to the target operation on the online version of the to-be-processed data after the processing corresponding to the target operation on the local version of the to-be-processed data is approved.

5. The data processing method according to claim 4, characterized in that, Before receiving the data query request of the target account on the target data, the method further comprises: creating the local version of the target data in response to a creation request of the target data; creating the online version of the target data after the local version of the target data is approved.

6. A data processing apparatus, characterized by, Comprise: a receiving unit configured to receive a data query request of a target account on target data, the data query request carrying an account identifier of the target account and a data identifier of the target data; an obtaining unit configured to obtain role information of the target account according to the account identifier, and obtain state information of the target data according to the data identifier; a determining unit configured to obtain to-be-processed data based on pre-obtained configuration information, the data query request, the state information and the role information, and determine a target operation corresponding to the to-be-processed data, the configuration information being used to indicate a correspondence relationship between role information, state information and supportable operations, the to-be-processed data being data in the target data that supports the target account to perform the target operation; the target operation corresponding to the to-be-processed data is to determine whether the current role of the target account supports viewing the target data in the current state; an operation unit configured to perform processing corresponding to the target operation on the to-be-processed data in response to the target operation of the target account on the to-be-processed data; the configuration information includes a set of supportable operations corresponding to each state information, a first set of role information supporting viewing data in each state information, and a second set of role information supporting performing each operation; the determining unit is specifically configured to: in a case where the role information of the target account is included in the first role information corresponding to the state information of the target data, take the target data as to-be-processed data, and obtain the to-be-processed data based on the data query request; determine a candidate operation from the set of supportable operations corresponding to the state information of the to-be-processed data; in a case where the role information of the target account is included in the second role set of the candidate operation, determine the candidate operation as the target operation corresponding to the to-be-processed data.

7. An electronic device, comprising: Comprise: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the data processing method of any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer program, when executed by a processor, implements the data processing method of any one of claims 1 to 5.

9. A computer program product comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the data processing method of any one of claims 1 to 5.

Images