CN115858885A - Account set data query method and device, computer equipment and storage medium - Google Patents

Account set data query method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN115858885A
CN115858885A CN202310175775.1A CN202310175775A CN115858885A CN 115858885 A CN115858885 A CN 115858885A CN 202310175775 A CN202310175775 A CN 202310175775A CN 115858885 A CN115858885 A CN 115858885A
Authority
CN
China
Prior art keywords
account set
data
preset
attribute information
target
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.)
Granted
Application number
CN202310175775.1A
Other languages
Chinese (zh)
Other versions
CN115858885B (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.)
Meiyun Zhishu Technology Co ltd
Original Assignee
Meiyun Zhishu 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 Meiyun Zhishu Technology Co ltd filed Critical Meiyun Zhishu Technology Co ltd
Priority to CN202310175775.1A priority Critical patent/CN115858885B/en
Publication of CN115858885A publication Critical patent/CN115858885A/en
Application granted granted Critical
Publication of CN115858885B publication Critical patent/CN115858885B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE 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/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The implementation mode of the specification provides an account set data query method, an account set data query device, computer equipment and a storage medium. The method comprises receiving a data query request; the data query request carries data attribute information and a user account set identifier; the data attribute information represents a data entity queried by the data query request; the user account set identification is used for referring to an account set corresponding to the identity information of the user triggering the data query request; matching from a plurality of preset account set access strategies according to the data attribute information and the user account set identification to obtain a target account set access strategy; wherein, at least one destination account set identification included in the target account set access strategy is used as the target account set identification; based on the data attribute information and the target account set identification, the account set corresponding to the target account set identification is queried to obtain account set data corresponding to the data attribute information, and flexibility of querying the account set data for different services is improved to a certain extent.

Description

Account set data query method and device, computer equipment and storage medium
Technical Field
Embodiments in this specification relate to the technical field of data processing, and in particular, to a method and an apparatus for querying account set data, a computer device, and a storage medium.
Background
The account set is a general name of all accounting business data files for storing accounting objects, is an independent and complete data set and is used for accounting the cost, expense, income and expenditure of enterprises in a certain period and summarizing the economic activities in daily business. The accounting target may be a division or a division of an enterprise, or may be the entire enterprise group.
In the related art, when inquiring the account set data, a corresponding logic branch processing code is usually written for the business logic of each business, so as to obtain the account set data.
However, for different services, the flexibility of the manner of querying the account set data in the related art needs to be improved.
Disclosure of Invention
In view of this, embodiments of the present disclosure are directed to providing a method, an apparatus, a device and a storage medium for querying account set data, so as to improve flexibility of querying the account set data to some extent.
An embodiment of the present specification provides an account set data query method, including: receiving a data query request; the data query request carries data attribute information and a user account set identifier; the data attribute information represents a data entity queried by the data query request; the user account set identification is used for referring to an account set corresponding to the identity information of the user triggering the data query request; matching from a plurality of preset account set access strategies according to the data attribute information and the user account set identification to obtain a target account set access strategy; wherein at least one destination account set identifier included in the target account set access policy is used as a target account set identifier; and inquiring the account set corresponding to the target account set identification based on the data attribute information and the target account set identification to obtain account set data corresponding to the data attribute information.
An embodiment of the present specification provides an account set data query apparatus, including: the query request receiving module is used for receiving a data query request; the data query request carries data attribute information and a user account set identifier; the data attribute information represents a data entity queried by the data query request; the user account set identification is used for referring to an account set corresponding to the identity information of the user triggering the data query request; the access strategy matching module is used for matching from a plurality of preset account set access strategies according to the data attribute information and the user account set identification to obtain a target account set access strategy; wherein, the target account set access strategy comprises at least one target account set identifier as a target account set identifier; and the account set data query module is used for querying an account set corresponding to the target account set identification based on the data attribute information and the target account set identification to obtain account set data corresponding to the data attribute information.
The present specification provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the method of any one of the above embodiments when executing the computer program.
The embodiment of the present specification provides a computer readable storage medium, on which a computer program is stored, and the computer program is executed by a processor to implement the method of any one of the above embodiments.
In a plurality of embodiments provided in this specification, a data query request carrying data attribute information and a user account set identifier is received; matching from a plurality of preset account set access strategies according to the data attribute information and the user account set identification to obtain a target account set access strategy; inquiring the account set corresponding to the target account set identification based on the data attribute information and the target account set identification to obtain account set data corresponding to the data attribute information; the data attribute information represents a data entity of the data query request, the user account set identifier is used for referring to an account set corresponding to the identity information of the user triggering the data query request, and at least one target account set identifier included in the target account set access strategy is used as the target account set identifier, so that the flexibility of the account set data query for different services can be improved.
Drawings
Fig. 1 is a schematic diagram of a ledger data query system according to an embodiment of the present specification.
Fig. 2 is a schematic flow chart of a method for querying account set data according to an embodiment of the present disclosure.
Fig. 3 is a schematic flowchart of determining a preset account set access policy according to an embodiment of the present disclosure.
Fig. 4 is a schematic diagram of determining preset entity attribute information according to an embodiment of the present disclosure.
Fig. 5a is a schematic diagram of determining a preset query range according to an embodiment of the present disclosure.
Fig. 5b is a flowchart illustrating a process of determining a preset query range according to an embodiment of the present disclosure.
Fig. 6 is a schematic diagram for determining a preset query range according to an embodiment of the present disclosure.
Fig. 7 is a schematic flow chart of determining a target account set access policy according to an embodiment of the present disclosure.
Fig. 8 is a flowchart of determining a target account set access policy according to an embodiment of the present disclosure.
Fig. 9 is a schematic flowchart of a method for querying account set data according to an embodiment of the present disclosure.
Fig. 10 is a schematic diagram of a ledger data query apparatus according to an embodiment of the present specification.
FIG. 11 is a schematic diagram of a computer device provided in one embodiment of the present description.
Detailed Description
In order to make the technical solution of the present invention better understood, the technical solution of the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art without any inventive work based on the embodiments in the present specification belong to the protection scope of the present specification.
In the related technology, the account set is an independent and complete data set, and the accounting business data files stored in the account set include a whole set of independent and complete data dictionaries, user permissions, basic files, commodity information, order data and the like. Each division of the enterprise and the headquarters of the enterprise group have corresponding accounting sets for accounting for the aggregation of costs, expenses, incomes, expenses and economic activities occurring in daily business over a certain period of time.
In some cases, there is a need for a sub-account set belonging to the division to query, read, or access to account set data in a main account set belonging to the group headquarters. In the related art, in order to implement cross-account-set data query and read, when some data attribute information is queried in a query process of account-set data, corresponding account-set identification information is transmitted in a query condition of a query statement, but when a main account set or a sub-account set is transmitted in any condition, a corresponding logic branch processing code needs to be written in when a business logic is written according to a specific business. The account set data query method in the related art has the problems that the account set identification to be queried cannot be flexibly set according to specific service data due to the fact that a logic branch processing code needs to be compiled for each service, the code is complicated and redundant, and the development efficiency is low.
Therefore, in order to improve flexibility when performing account set data query on different account sets for different services, it is necessary to provide an account set data query method, which can obtain a target account set access policy by receiving a data query request carrying data attribute information and a user account set identifier, matching the data attribute information and the user account set identifier from a plurality of preset account set access policies, and performing query on an account set corresponding to the target account set identifier based on the data attribute information and the target account set identifier, thereby obtaining account set data corresponding to the data attribute information; the data attribute information represents a data entity queried by the data query request, the account set identifier of the user is used for referring to an account set corresponding to identity information of the user triggering the data query request, and at least one destination account set identifier included in the target account set access policy is used as the target account set identifier. The technical problem of low account set data query flexibility when account set data query is carried out on different services is solved.
Referring to fig. 1, an embodiment of the present disclosure provides an account set data query system. The account set data query system may include a client and a server.
The client may be configured to send a data query request to the server. The client may be an electronic device with network access capabilities. Specifically, for example, the client may be a desktop computer, a tablet computer, a notebook computer, a smart phone, a digital assistant, a smart wearable device, a shopping guide terminal, a television, a smart speaker, a microphone, and the like. Wherein, wearable equipment of intelligence includes but not limited to intelligent bracelet, intelligent wrist-watch, intelligent glasses, intelligent helmet, intelligent necklace etc.. Alternatively, the client may be software capable of running in the electronic device. The server may be an electronic device having a certain arithmetic processing capability. Which may have a network communication module, a processor, memory, etc. Of course, the server may also refer to software running in the electronic device.
The server can perform account set data query according to the received data query request. The server may also be a distributed server, which may be a system with multiple processors, memory, network communication modules, etc. operating in coordination. Alternatively, the server may also be a server cluster formed by several servers. Or, with the development of scientific technology, the server can also be a new technical means capable of realizing the corresponding functions of the specification implementation mode. For example, it may be a new form of "server" implemented based on quantum computing.
In this embodiment, the client may log in a user account representing identity information of a user and have a user account set identifier corresponding to the user account, and the client may generate a data query request carrying data attribute information and the user account set identifier according to a data query requirement of the account set under the user account and send the data query request to the server. The server may be connected with a plurality of account sets, and may be configured with a plurality of preset account set access policies, and the server may acquire, from the plurality of account sets connected with the server, account set data corresponding to the data attribute information based on the plurality of preset account set access policies and the data attribute information and the user account set identifier in the received data query request.
One embodiment of the present specification provides a method for querying account set data. The account set data query method can be applied to a server. Referring to fig. 2, the method for querying account set data may include the following steps.
Step S210: receiving a data query request; the data query request carries data attribute information and a user account set identifier; the data attribute information represents a data entity queried by the data query request; the user account set identification is used for referring to an account set corresponding to the identity information of the user triggering the data query request.
In some cases, because the account set data query requirements are different and various, if the data attribute information to be queried is different, or the data attribute information to be queried belongs to different user accounts, that is, the account set identifiers of the users corresponding to the data attribute information to be queried are different, when the account set data query is performed, a data query request carrying the data attribute information and the account set identifier of the user representing the identity information of the user to which the data attribute information belongs needs to be received.
In this embodiment, the server may receive a data query request. The data query request carries data attribute information and a user account set identifier, the data attribute information represents a data entity queried by the data query request, and the user account set identifier is used for referring to an account set corresponding to identity information of a user triggering the data query request. Specifically, for example, the server may receive a data query request sent by the client, where the data attribute information carried in the data query request may be attribute information of a data entity such as order information, member information, commodity category information, and system parameter information. The carried user account set identifier may be a main account set identifier representing a main account set of the group headquarters, that is, the data query request is triggered by a user account of the group headquarters. The account set identifier of the user carried in the data query request may also be a sub-account set identifier of a sub-account set representing a certain institution, that is, the data query request is triggered by a user account of the institution.
For example, the client may log in a group headquarters account, and the client may send a data query request to the server under the group headquarters account, where the data query request carries a main account cover identifier and data attribute information corresponding to the group headquarters account, and as an example, the data attribute information may be order information. For example, the client may further log in a department account, and the client may send a data query request to the server under the department account, where the data query request carries the account division set identifier and the data attribute information corresponding to the department account, and the department account may be a refrigerator department, a kitchen heating department, an air conditioner department, or the like, and as an example, the data attribute information may be member information or commodity type information.
Step S220: matching from a plurality of preset account set access strategies according to the data attribute information and the user account set identification to obtain a target account set access strategy; wherein at least one destination account set identifier included in the target account set access policy is used as the target account set identifier.
In some cases, in order to improve flexibility of account set data query, after a data query request is received and the received data query request is analyzed to obtain data attribute information and a user account set identifier, a target account set access policy may be determined from a plurality of preset account set access policies according to the data attribute information and the user account set identifier, so as to perform account set data query based on the target account set access policy.
In this embodiment, the server may match the data attribute information obtained by analyzing the data query request and the user account set identifier from the plurality of preset account set access policies, and determine the target account set access policy from the plurality of preset account set access policies, so that at least one target account set identifier included in the target account set access policy may be used as the target account set identifier.
Step S230: and inquiring the account set corresponding to the target account set identification based on the data attribute information and the target account set identification to obtain account set data corresponding to the data attribute information.
In this embodiment, after determining the target account set identifier, based on the data attribute information and the target account set identifier, the account set corresponding to the target account set identifier may be queried to obtain the account set data corresponding to the data attribute information. Exemplarily, when data attribute information obtained by analyzing according to the data query request is order information and a user account set identifier is a master account set identifier, the server may perform matching from a plurality of preset account set access policies according to the order information and the master account set identifier to obtain a target account set access policy, and query an account set corresponding to the target account set identifier with at least one destination account set identifier included in the target account set access policy as the target account set identifier to obtain account set data corresponding to the order information, where the at least one destination account set identifier may be a refrigerator account identifier, a kitchen thermal account identifier, an air conditioner account identifier, a washing machine account identifier, or a water heater account identifier.
In the above embodiment, by receiving a data query request carrying data attribute information and a user account set identifier, matching is performed from a plurality of preset account set access policies according to the data attribute information and the user account set identifier, to obtain at least one destination account set identifier included in a target account set access policy as a target account set identifier, and based on the data attribute information and the target account set identifier, a query is performed on an account set corresponding to the target account set identifier, so that account set data corresponding to the data attribute information can be obtained, and thus, account set data query can be flexibly performed for changes of the data attribute information and the user account set identifier, thereby improving flexibility in performing account set data query for different services. In addition, the target account set identification is directly determined by the server according to the data attribute information and the user account set identification, and the account set data corresponding to the data attribute information is obtained by inquiring the account set corresponding to the target account set identification through the server based on the data attribute information, so that developers do not need to pay attention to branch processing logic of the account set inquiry service when writing business logic codes of the account set data inquiry service, and development efficiency and code simplicity are improved.
In some embodiments, the preset account set access policy may include preset entity attribute information of a preset data entity and a preset query range of the preset data entity. Accordingly, referring to fig. 3, the configuration process of the preset account set access policy may include the following steps.
Step S310: and determining the attribute information of the preset entity under the condition of receiving an attribute configuration request aiming at the preset data entity. The preset entity attribute information is used for representing attribute information of a preset data entity, and the preset entity attribute information at least comprises a data entity name, a data entity code, a data entity type and a data entity effectiveness.
In some cases, in order to improve flexibility of account set data query, a preset account set access policy may be preconfigured before a data query request is received, so that after the data query request is received, matching may be performed according to data attribute information and a user account set identifier carried in the data query request and the preconfigured preset account set access policy.
In this embodiment, the server may determine the preset entity attribute information in a case where an attribute configuration request for the preset data entity is received. Specifically, in order to facilitate determining a preset query range corresponding to preset entity attribute information for preset entity attribute information, in the case of receiving an attribute configuration request for a preset data entity, the server may determine at least a data entity name, a data entity code, a data entity type, and a data entity validity in the preset entity attribute information. Through simplicity and readability of the data entity names, the preset entity attribute information can be easily identified and distinguished, and no ambiguity exists. The preset entity attribute information can be uniquely identified through the uniqueness of the data entity code. The data entity type of the preset data entity corresponding to the preset entity attribute information may be determined by the data entity type, for example, the data entity type may be a service data type corresponding to order information, member information, commodity category information, and the like, and the data entity type may also be a basic data type corresponding to system parameter information, a coding rule of the preset data entity, and the like. Through the effectiveness of the data entity, whether the preset entity attribute information is effective or not can be determined, and the effectiveness of the preset account set access strategy is convenient to adjust.
Specifically, in the event that a property configuration request for a property configuration control is received, the server may determine preset entity property information. The server may determine the data entity name if a data entity name input request for the property configuration control is received and determine the data entity encoding if a data entity encoding input request for the property configuration control is received. The server can be preset with a data entity type list and a data entity effectiveness list, wherein the data entity type list is preset with a basic data type and a business data type, and the data entity effectiveness list is preset with entity effectiveness comprising effective effectiveness and ineffective effectiveness. The server may determine the data entity type as underlying data or business data in case a data entity type selection request for a data entity type in the data entity type list is received, and may determine the data entity validity as valid or invalid in case a data entity validity selection request for a data entity validity in the data entity validity list is received.
For example, referring to fig. 4, the server may determine that the data entity name is an order in case of receiving the data entity name input request, may determine that the data entity code is an order in case of receiving the data entity code input request, may determine that the data entity type is business data in case of receiving the data entity type selection request, and may determine that the data entity is valid in case of receiving the data entity validity selection request, thereby completing the configuration of the preset entity attribute information.
Step S320: and under the condition that a query range configuration request aiming at a preset data entity is received, determining a preset query range corresponding to the attribute information of the preset entity.
Referring to fig. 5a, in the present embodiment, in a case that a query range configuration request for a preset data entity is received, a server may determine a preset query range corresponding to preset entity attribute information. Specifically, after determining the preset entity attribute information of the preset data entity, the server may determine the preset query range corresponding to the preset entity attribute information when receiving a query range configuration request for the preset data entity.
In the above embodiment, by determining the attribute information of the preset entity in the case of receiving the attribute configuration request for the preset data entity, and determining the preset query range corresponding to the attribute information of the preset entity in the case of receiving the query range configuration request for the preset data entity, the configuration of the attribute information of the preset entity in the preset account book access policy and the preset query range corresponding to the attribute information of the preset entity is realized, so that the configuration can be performed with the configured preset account book access policy according to the data attribute information and the account book identifier of the user in the data query request subsequently when the data query request is received. Therefore, the inquiry range of the account set data inquiry can be flexibly adjusted by flexibly configuring the preset account set access strategy, and the inquiry range of the corresponding account set data can be dynamically configured according to specific business requirements by flexibly configuring the preset account set access strategy, so that the adaptive capacity of business expansion is improved.
In some embodiments, the data query mode corresponding to the preset query range may include cross-account set query. Accordingly, referring to fig. 5b, the configuration process of the preset query range may include the following steps.
Step S510: and under the condition of receiving a cross account set query selection request, determining that the data query mode is cross account set query.
In some cases, the server may form a preset entity attribute information list when configuring the preset entity attribute information, the server may further preset an access policy list, a data query manner for cross account set query is preset in the access policy list, and the server may determine that the data query manner is cross account set query by a cross account set query selection request for the data query manner in the access policy list.
In this embodiment, please continue to refer to fig. 5a, the server may select the preset entity attribute information when receiving a preset entity attribute information selection request for the preset entity attribute information in the preset entity attribute information list, and the server may determine the data query mode as a cross-account-set query when receiving the cross-account-set query selection request for the preset entity attribute information.
Step S520: determining a source account set identifier corresponding to preset entity attribute information under the condition of receiving a source account set identifier configuration request; and the source account set identification is used for matching with the user account set identification in the data query request.
In some cases, the server may preset an active account set identification list.
In this embodiment, upon receiving a source account set identifier configuration request, the server may determine a source account set identifier corresponding to the preset entity attribute information. And the source account set identification is used for matching with the user account set identification in the data query request. In some embodiments, upon receiving a source book identification configuration request for a source book identification in a source book identification list, the server may determine the source book identification corresponding to the preset entity attribute information. As an example, the source account set identifier may be a main account set identifier corresponding to a group headquarters or a sub-account set identifier corresponding to each cause department such as a refrigerator cause department, a kitchen heat cause department, an air conditioner cause department, and the source account set identifier list may include the main account set identifier corresponding to the group headquarters and the sub-account set identifier corresponding to each cause department. As an example, the server may determine that the source account set identifier is a master account set identifier of a group headquarters or a sub-account set identifier of each account department upon receiving the source account set identifier configuration request.
Step S530: determining at least one destination account set identifier corresponding to the source account set identifier under the condition of receiving a destination account set identifier configuration request; and the preset inquiry range is the account set corresponding to at least one destination account set identification.
In some cases, the server may pre-populate the destination account set identification list.
In this embodiment, the server may determine at least one destination account set identity corresponding to the source account set identity upon receiving the destination account set identity configuration request. And the preset inquiry range is the account set corresponding to at least one destination account set identification. In some embodiments, the server may determine at least one destination account set corresponding to the source account set identity upon receiving a destination account set identity configuration request for a destination account set identity in the destination account set identity list. As an example, continuing to refer to fig. 5a, the destination account set identifier may be a main account set identifier corresponding to a group headquarters, or may also be a sub-account set identifier corresponding to each ministry such as a refrigerator ministry, a kitchen heating ministry, an air-conditioning ministry, etc., the source account set identifier list may include the main account set identifier corresponding to the group headquarters and the sub-account set identifier corresponding to each ministry, and the at least one destination account set may include at least one of the main account set identifier and each sub-account set identifier.
In the above embodiment, the configuration of the source account set identifier and the at least one destination account set identifier in the preset access policy is realized by determining that the data query mode is cross-account set query when the cross-account set query selection request is received, determining the source account set identifier corresponding to the preset entity attribute information when the source account set identifier configuration request is received, and determining the at least one destination account set identifier corresponding to the source account set identifier when the destination account set identifier configuration request is received, so that the server can perform account set data query based on the preset access policy after receiving the data query request.
In some embodiments, the data query mode corresponding to the preset query range may include querying by a user account set. Accordingly, the process of configuring the preset query scope may include: under the condition of receiving a selection request for inquiring according to a user account set, determining a data inquiry mode as inquiring according to the user account set; and the preset inquiry range defaults to the account set corresponding to the user account set identification carried by the data inquiry request.
In some cases, a data query mode according to the account set query of the user is preset in an access policy list of the server, and the server may determine that the data query mode is the account set query of the user through a query selection request according to the account set query of the user aiming at the data query mode in the access policy list.
In this embodiment, referring to fig. 6, when receiving a preset entity attribute information selection request for preset entity attribute information in a preset entity attribute information list, a server selects the preset entity attribute information, and when receiving a selection request for querying according to a user account set, the server may determine that a data query manner is querying according to the user account set; and the preset inquiry range defaults to the account set corresponding to the user account set identification carried by the data inquiry request. That is, when the data query mode configuring the preset access policy is query according to the user account set, the source account set identifier and the destination account set identifier may not be configured, that is, the source account set identifier configuration and the destination account set identifier configuration of the data query mode configuring the preset access policy according to the user account set are configured to be empty.
In the above embodiment, when it is determined that the data query mode is query according to the account set of the user, the account set corresponding to the account set identifier carried in the data query request is determined by default in the preset query range, so that the configuration of the preset account set access policy for querying according to the account set of the user in the data query mode is realized, and the server can perform account set data query on the account set corresponding to the account set identifier of the user based on the preset account set access policy for querying according to the account set of the user in the data query mode after receiving the data query request.
In some embodiments, referring to fig. 7, matching a target account set access policy from a plurality of preset account set access policies according to data attribute information and a user account set identifier may include the following steps.
Step S710: and aiming at each preset account set access strategy, matching the data attribute information with the preset entity attribute information of each preset account set access strategy, and matching the user account set identification with the source account set identification of each preset account set access strategy.
In some cases, the preset account set access policy may include preset entity attribute information of a preset data entity and a source account set identifier corresponding to the preset entity attribute information, so that when matching operations are performed according to the data attribute information and the user account set identifier in the data query request and a plurality of preset account set access policies, matching may be performed according to the data attribute information and the preset entity attribute information, and matching may be performed according to the user account set identifier and the source account set identifier corresponding to the preset entity attribute information.
In this embodiment, the server may match, for each preset account set access policy, the data attribute information with the preset entity attribute information of each preset account set access policy, and match the user account set identifier with the source account set identifier of each preset account set access policy.
Specifically, the server may match, for each preset account set access policy, the data attribute information with preset entity attribute information for which the data entity of each preset account set access policy is valid, and match with the source account set identifier of each preset account set access policy with the user account set identifier.
Specifically, the data attribute information is matched with the preset entity attribute information of each preset account set access policy, may refer to the data attribute information being matched with the data entity name, may refer to the data attribute information being matched with the data entity code, and may refer to the data attribute information being matched with the data entity name and the data entity code.
Step S720: and determining a target account set access strategy according to a matching result of the preset entity attribute information and the data attribute information and a matching result of the source account set identification and the user account set identification.
In this embodiment, the server may determine the target account set access policy from the multiple preset account set access policies according to a matching result between the preset entity attribute information and the data attribute information and a matching result between the source account set identifier and the user account set identifier, that is, the preset entity attribute information in the target account set access policy is matched with the data attribute information in the data query request, and the source account set identifier in the target account set access policy is also matched with the user account set identifier in the data query request. As an example, the data attribute information and the user account set identifier may be order information and a main account set identifier, respectively, and the server may use, as the target account set access policy, a preset account set access policy in which the preset entity attribute information in the preset account set access policies is the order information and the source account set identifier is the main account set identifier, according to the order information and the main account set identifier.
In the above embodiment, for each preset account set access policy, the data attribute information is used to match with the preset entity attribute information of each preset account set access policy, the user account set identifier is used to match with the source account set identifier of each preset account set access policy, and a target account set access policy is determined from the multiple preset account set access policies according to the matching result of the preset entity attribute information and the data attribute information and the matching result of the source account set identifier and the user account set identifier, so that the account set data corresponding to the data attribute information is obtained by querying the account set corresponding to the target account set identifier based on the data attribute information and the target account set identifier in the target account set access policy.
In some embodiments, referring to fig. 8, determining a target account set access policy according to a matching result of the preset entity attribute information and the data attribute information and a matching result of the source account set identifier and the user account set identifier may include the following steps.
Step S810: and if the preset entity attribute information is matched with the data attribute information and the preset account set access strategies matched with the source account set identification and the user account set identification are multiple, acquiring target account set configuration data corresponding to at least one target account set of the preset account set access strategies.
In some cases, there are cases where the preset entity attribute information in the multiple preset account set access policies matches the data attribute information in the data query request, and where the source account set identifier corresponding to the preset entity attribute information matches the user account set identifier in the data query request, so that multiple preset account set access policies that match both the data attribute information in the data query request and the user account set identifier in the data query request may be screened based on the destination account set configuration data in the preset account set access policies.
In this embodiment, the preset account set access policy may further include destination account set configuration data, and the destination account set configuration data may represent a configuration attribute of at least one destination account set in the preset account set access policy. If the preset entity attribute information is matched with the data attribute information and the preset account set access strategies matched with the source account set identification and the user account set identification are multiple, the server can acquire destination account set configuration data corresponding to at least one destination account set of the preset account set access strategies so as to screen the multiple preset account set access strategies according to the destination account set configuration data.
Step S820: and screening the target account set access strategy from a plurality of preset account set access strategies based on the target account set configuration data.
In this embodiment, the server may filter the target account set access policy from a plurality of preset account set access policies based on the target account set configuration data.
In the above embodiment, the target account set access policy can be obtained by screening from a plurality of preset account set access policies in which the preset entity attribute information is matched with the data attribute information and the source account set identifier is matched with the user account set identifier based on the destination account set configuration data, so that the matching accuracy of the preset account set access policies can be improved, and the accuracy of the account set data query can be improved.
In some embodiments, the destination account set configuration data may identify at least one of an amount of an account set, a level of an account set, and a maintenance time for an account set for at least one destination account set of a preset account set access policy. Accordingly, the target account set access policy may be determined in any of the following ways: and taking the preset account set access strategy with the minimum account set number as a target account set access strategy, taking the preset account set access strategy with the lowest account set level as a target account set access strategy, and taking the preset account set access strategy with the latest account set maintenance time as a target account set access strategy.
In this embodiment, if the preset entity attribute information matches the data attribute information and the preset account set access policy in which the source account set identifier matches the user account set identifier is multiple, the server may use, as the target account set access policy, the preset account set access policy in which the number of account sets is the smallest, may use, as the target account set access policy, the preset account set access policy in which the level of an account set is the lowest, and may use, as the target account set access policy, the preset account set access policy in which the maintenance time of an account set is the latest, among the preset account set access policies.
The account set number refers to the number of destination account set identifiers in a preset account set access strategy.
The account set level refers to a destination account set level corresponding to a preset account set access policy, each destination account set identifier in at least one destination account set identifier included in the preset account set access policy has a corresponding destination account set level, and the account set level of the preset account set access policy is equal to the highest destination account set level in the at least one destination account set identifier in the preset account set access policy. Illustratively, the destination account set identifier in the preset account set access policy may include a main account set identifier of a group headquarters and sub-account set identifiers of a plurality of cause departments, wherein the destination account set level of the main account set identifier is higher than the destination account set level of the sub-account set identifiers, and thus, the account set level corresponding to the preset account set access policy is the destination account set level corresponding to the main account set identifier.
The account set maintenance time refers to the last modification time of the destination account set identifier in the preset account set access policy.
In the above embodiment, the target account set access policy can be obtained by screening from a plurality of preset account set access policies in which preset entity attribute information is matched with data attribute information and a source account set identifier is matched with a user account set identifier, through account set data, account set level and account set maintenance time in the target account set configuration data based on the preset access policy, so that the matching accuracy of the preset account set access policy can be further improved, and the accuracy of account set data query can be further improved.
In some embodiments, referring to fig. 9, the account data query method may further include the following steps.
Step S910: and aiming at each preset account set access strategy, matching the data attribute information with the preset entity attribute information of each preset account set access strategy, and matching the user account set identification with the source account set identification of each preset account set access strategy.
In some cases, when matching operation is performed according to data attribute information and a user account set identifier in a data query request and a plurality of preset account set access policies, there may be a case where no preset account set access policy is matched with the data attribute information and the user account set identifier in the data query request.
In this embodiment, the server may perform matching, for each preset account set access policy, by using the data attribute information and preset entity attribute information of each preset account set access policy, and by using the user account set identifier and the source account set identifier of each preset account set access policy. Specifically, the server may match, for each preset account set access policy, the data attribute information with the data entity name and the data entity code of each preset account set access policy, and match the user account set identifier with the source account set identifier of each preset account set access policy.
Step S920: if the user account set identification does not match the source account set identification in each preset account set access strategy, and a preset account set access strategy that preset entity attribute information is matched with data attribute information and the source account set identification is empty exists, inquiring an account set corresponding to the user account set identification based on the data attribute information and the user account set identification to obtain account set data corresponding to the data attribute information.
In this embodiment, if the user account set identifier does not match the source account set identifier in each preset account set access policy, and there is a preset account set access policy in which the preset entity attribute information matches the data attribute information and the source account set identifier is empty, the server may perform an inquiry on the account set corresponding to the user account set identifier based on the data attribute information and the user account set identifier, to obtain account set data corresponding to the data attribute information. In other words, if the user account set identifier does not match the source account set identifier in each preset account set access policy, and there is a preset account set access policy in which the preset entity attribute information matches the data attribute information and the source account set identifier is empty, the server may use the user account set identifier as the target account set identifier, and perform an inquiry on the account set corresponding to the target account set identifier based on the data attribute information and the target account set identifier, to obtain account set data corresponding to the data attribute information.
In the above embodiment, when the user account set identifier does not match the source account set identifier in each preset account set access policy, and there is a preset account set access policy in which the preset entity attribute information matches the data attribute information and the source account set identifier is empty, the account set corresponding to the user account set identifier is queried based on the data attribute information and the user account set identifier to obtain account set data corresponding to the data attribute information, so that the account set data corresponding to the data attribute information in the data query request can still be queried and obtained without configuring the source account set identifier matching the user account set identifier and the corresponding destination account set identifier.
In some embodiments, based on the data attribute information and the target account set identifier, querying the account set corresponding to the target account set identifier to obtain account set data corresponding to the data attribute information, which may further include: and generating a target query statement based on the data attribute information and the target account set identification, and querying the target account set corresponding to the target account set identification by using the target query statement to obtain account set data corresponding to the data attribute information.
In the above embodiment, the server matches the data attribute information and the user account set identifier obtained by analyzing the data query request with a plurality of preset account set access policies, so as to determine a target account set identifier, and generates a query statement based on the data attribute information and the target sub-account set identifier, and obtains account set data corresponding to the data attribute information from the target account set corresponding to the target account set identifier through the query statement, so that when a developer writes a logic branch processing code to perform account set data query, it is unnecessary to determine whether a logged-in user account is a group head office account or a business department account of each business department, and only data attribute information of a data entity to be queried and the account set identifier of the logged-in account need to be transmitted, thereby simplifying business end determination logic, improving development efficiency, and reducing program errors (bugs). Meanwhile, the adaptation capability of service expansion is improved by flexibly configuring a plurality of preset account set access strategies.
The implementation mode of the specification provides an account set data query method. The account set data query method can be applied to a server. The account set data query method can comprise the following steps.
Step S1002: receiving a data query request; the data query request carries data attribute information and a user account set identifier; the data attribute information represents a data entity queried by the data query request; the user account set identification is used for referring to an account set corresponding to the identity information of the user triggering the data query request.
Step S1004: and aiming at each preset account set access strategy, matching the data attribute information with the preset entity attribute information of each preset account set access strategy, and matching the user account set identification with the source account set identification of each preset account set access strategy.
Step S1006: if the preset entity attribute information is matched with the data attribute information and the number of preset account set access strategies matched with the source account set identification and the user account set identification is multiple, acquiring target account set configuration data corresponding to at least one target account set of the preset account set access strategies; screening a target account set access strategy from a plurality of preset account set access strategies based on the target account set configuration data; wherein at least one destination account set identifier included in the target account set access policy is used as a target account set identifier; the destination account set configuration data is at least one of account set quantity, account set grade and account set maintenance time of at least one destination account set identifier of a preset account set access strategy; determining a target account set access policy in any one of the following ways: taking a preset account set access strategy with the minimum account set quantity as a target account set access strategy; taking a preset account set access strategy with the lowest account set grade as a target account set access strategy; and taking the preset account set access strategy with the latest account set maintenance time as a target account set access strategy.
Step S1008: and if the user account set identification does not match the source account set identification in each preset account set access strategy, and a preset account set access strategy exists, wherein the preset entity attribute information is matched with the data attribute information and the source account set identification is empty, the user account set identification is used as the target account set identification.
Step S1010: and generating a target query statement based on the data attribute information and the target account set identification.
Step S1012: and inquiring the account set corresponding to the target account set identification by using the target inquiry statement to obtain account set data corresponding to the data attribute information.
One embodiment of the present specification also provides an account set data query device. Referring to fig. 10, the ledger data query apparatus may include a query request receiving module 1010, an access policy matching module 1020, and a ledger data query module 1030. A query request receiving module 1010, configured to receive a data query request; the data query request carries data attribute information and a user account set identifier; the data attribute information represents a data entity queried by the data query request; the user account set identifier is used for referring to an account set corresponding to the identity information of the user triggering the data query request. An access policy matching module 1020, configured to match the data attribute information and the user account set identifier from multiple preset account set access policies to obtain a target account set access policy; and the target account set access strategy comprises at least one target account set identifier as a target account set identifier. And the account set data query module 1030 is configured to query, based on the data attribute information and the target account set identifier, an account set corresponding to the target account set identifier to obtain account set data corresponding to the data attribute information.
Specific functions and effects achieved by the account set data query device can be explained by referring to other embodiments in the specification, and are not described herein again. The respective modules in the target data sorting apparatus may be wholly or partially implemented by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
The embodiment of the present specification provides a computer device, please refer to fig. 11, which includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, and when the processor executes the computer program, the processor implements the account set data query method according to any one of the above embodiments.
Embodiments of the present specification also provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a computer, the computer executes the method for querying account set data in any one of the above embodiments.
Embodiments of the present specification further provide a computer program product containing instructions, where the instructions, when executed by a computer, cause the computer to execute the method for querying account set data in any of the above embodiments.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 11. The computer apparatus includes a processor, a memory, a communication interface, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement an exception task identification method. The input device of the computer equipment can be a touch layer covered on a display screen, a key, a track ball or a touch pad arranged on a shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
It should be understood that the specific examples are included merely for purposes of illustrating the embodiments of the disclosure and are not intended to limit the scope of the disclosure.
It should be understood that, in the various embodiments in the present specification, the order of execution of each process does not mean the order of execution, and the order of execution of each process should be determined by its function and inherent logic, and should not limit the implementation process of the embodiments in the present specification.
It is to be understood that the various embodiments described in the present specification may be implemented individually or in combination, and the embodiments in the present specification are not limited thereto.
Unless otherwise defined, all technical and scientific terms used in the embodiments of the present specification have the same meaning as commonly understood by one of ordinary skill in the art to which this specification belongs. The terminology used in the description is for the purpose of describing particular embodiments only and is not intended to limit the scope of the description. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. As used in the specification embodiments and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It is to be understood that the processor of the embodiments of the present description may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of this specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present specification may be embodied directly in a hardware decoding processor, or in a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the implementations of the specification can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EEPROM (EEPROM), or a flash memory. The volatile memory may be Random Access Memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present specification.
It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in this specification, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is merely a logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.
In addition, functional units in the embodiments of the present specification may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present specification may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present specification. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or the like.
The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope disclosed in the present disclosure, and all the changes or substitutions should be covered within the scope of the present disclosure. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (12)

1. A method for inquiring account set data is characterized by comprising the following steps:
receiving a data query request; the data query request carries data attribute information and a user account set identifier; the data attribute information represents a data entity queried by the data query request; the user account set identification is used for referring to an account set corresponding to the identity information of the user triggering the data query request;
matching from a plurality of preset account set access strategies according to the data attribute information and the user account set identification to obtain a target account set access strategy; wherein, the target account set access strategy comprises at least one target account set identifier as a target account set identifier;
and inquiring the account set corresponding to the target account set identification based on the data attribute information and the target account set identification to obtain account set data corresponding to the data attribute information.
2. The book data query method of claim 1, wherein the preset book access policy includes preset entity attribute information of a preset data entity and a preset query range of the preset data entity; the configuration process of the preset account set access strategy comprises the following steps:
determining the attribute information of the preset entity under the condition of receiving an attribute configuration request aiming at the preset data entity; the preset entity attribute information is used for representing attribute information of the preset data entity, and the preset entity attribute information at least comprises a data entity name, a data entity code, a data entity type and a data entity effectiveness;
and determining the preset query range corresponding to the preset entity attribute information under the condition of receiving a query range configuration request aiming at the preset data entity.
3. The account set data query method according to claim 2, wherein the data query mode corresponding to the preset query range comprises cross-account set query; the configuration process of the preset query range comprises the following steps:
determining that the data query mode is the cross account set query under the condition that a cross account set query selection request is received;
determining a source account set identifier corresponding to the preset entity attribute information under the condition of receiving a source account set identifier configuration request; the source account set identification is used for matching with a user account set identification in the data query request;
determining at least one destination account set identifier corresponding to the source account set identifier under the condition of receiving a destination account set identifier configuration request; and the preset inquiry range is the account set corresponding to the at least one destination account set identification.
4. The account set data query method according to claim 2, wherein the data query mode corresponding to the preset query range includes querying according to a user account set; the configuration process of the preset query range comprises the following steps:
under the condition of receiving a selection request for inquiring according to a user account set, determining the data inquiry mode as the inquiry according to the user account set; and the preset inquiry range defaults to the account set corresponding to the user account set identification carried by the data inquiry request.
5. The account set data query method of claim 1, wherein the obtaining a target account set access policy by matching from a plurality of preset account set access policies according to the data attribute information and the user account set identifier comprises:
aiming at each preset account set access strategy, matching the data attribute information with preset entity attribute information of each preset account set access strategy, and matching the user account set identification with a source account set identification of each preset account set access strategy;
and determining the target account set access strategy according to the matching result of the preset entity attribute information and the data attribute information and the matching result of the source account set identification and the user account set identification.
6. The account set data query method of claim 5, wherein said determining the target account set access policy according to the matching result of the preset entity attribute information and the data attribute information and the matching result of the source account set identifier and the user account set identifier comprises:
if the preset entity attribute information is matched with the data attribute information and the number of preset account set access strategies matched with the source account set identification and the user account set identification is multiple, acquiring destination account set configuration data corresponding to at least one destination account set of the preset account set access strategies;
and based on the target account set configuration data, screening the target account set access strategy from a plurality of preset account set access strategies.
7. The account set data query method of claim 6, wherein the destination account set configuration data is at least one of an account set number, an account set level, and an account set maintenance time of at least one destination account set identifier of the preset account set access policy; determining the target ledger access policy in any of the following ways:
taking a preset account set access strategy with the minimum account set quantity as the target account set access strategy;
taking a preset account set access strategy with the lowest account set grade as the target account set access strategy;
and taking a preset account set access strategy with the latest account set maintenance time as the target account set access strategy.
8. The set data query method of any of claims 1-7, further comprising:
aiming at each preset account set access strategy, matching the data attribute information with preset entity attribute information of each preset account set access strategy, and matching the user account set identification with a source account set identification of each preset account set access strategy;
if the user account set identification does not match the source account set identification in each preset account set access strategy, and a preset account set access strategy that preset entity attribute information is matched with the data attribute information and the source account set identification is empty exists, inquiring an account set corresponding to the user account set identification based on the data attribute information and the user account set identification to obtain account set data corresponding to the data attribute information.
9. The account set data query method of any one of claims 1 to 7, wherein the querying, based on the data attribute information and the target account set identifier, in an account set corresponding to the target account set identifier to obtain account set data corresponding to the data attribute information, further comprises:
generating a target query statement based on the data attribute information and the target account set identification;
and inquiring the target account set corresponding to the target account set identification by using the target inquiry statement to obtain account set data corresponding to the data attribute information.
10. An account set data query device, the device comprising:
the query request receiving module is used for receiving a data query request; the data query request carries data attribute information and a user account set identifier; the data attribute information represents a data entity queried by the data query request; the user account set identification is used for referring to an account set corresponding to the identity information of the user triggering the data query request;
the access strategy matching module is used for matching from a plurality of preset account set access strategies according to the data attribute information and the user account set identification to obtain a target account set access strategy; wherein, the target account set access strategy comprises at least one target account set identifier as a target account set identifier;
and the account set data query module is used for querying an account set corresponding to the target account set identification based on the data attribute information and the target account set identification to obtain account set data corresponding to the data attribute information.
11. A computer device comprising a memory storing a computer program and a processor implementing the method of any one of claims 1 to 9 when executing the computer program.
12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of any one of claims 1 to 9.
CN202310175775.1A 2023-02-28 2023-02-28 Account book data query method, device, computer equipment and storage medium Active CN115858885B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310175775.1A CN115858885B (en) 2023-02-28 2023-02-28 Account book data query method, device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310175775.1A CN115858885B (en) 2023-02-28 2023-02-28 Account book data query method, device, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN115858885A true CN115858885A (en) 2023-03-28
CN115858885B CN115858885B (en) 2023-06-30

Family

ID=85659305

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310175775.1A Active CN115858885B (en) 2023-02-28 2023-02-28 Account book data query method, device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115858885B (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101702156A (en) * 2009-10-28 2010-05-05 金蝶软件（中国）有限公司 Method for realizing data query by crossing over account set and system
CN108055312A (en) * 2017-12-07 2018-05-18 畅捷通信息技术股份有限公司 Method for routing and its device and computer installation and its readable storage medium storing program for executing
CN111460298A (en) * 2020-03-31 2020-07-28 深圳市酷开网络科技有限公司 Service data processing method and device, computer equipment and storage medium
CN112035542A (en) * 2020-08-28 2020-12-04 成都质数斯达克科技有限公司 Information query method and device, electronic equipment and readable storage medium
CN112286997A (en) * 2020-11-25 2021-01-29 平安数字信息科技(深圳)有限公司 Salary data query method based on distributed deployment and related equipment
CN113568970A (en) * 2021-02-03 2021-10-29 腾讯科技（深圳）有限公司 Application service data management method, device, equipment and storage medium
CN113868219A (en) * 2020-06-12 2021-12-31 航天信息股份有限公司 Method and device for migrating account set data, electronic equipment and computer storage medium
CN115033211A (en) * 2022-05-24 2022-09-09 青岛海尔科技有限公司 Method, device and equipment for querying article based on strategy mode and storage medium

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101702156A (en) * 2009-10-28 2010-05-05 金蝶软件（中国）有限公司 Method for realizing data query by crossing over account set and system
CN108055312A (en) * 2017-12-07 2018-05-18 畅捷通信息技术股份有限公司 Method for routing and its device and computer installation and its readable storage medium storing program for executing
CN111460298A (en) * 2020-03-31 2020-07-28 深圳市酷开网络科技有限公司 Service data processing method and device, computer equipment and storage medium
CN113868219A (en) * 2020-06-12 2021-12-31 航天信息股份有限公司 Method and device for migrating account set data, electronic equipment and computer storage medium
CN112035542A (en) * 2020-08-28 2020-12-04 成都质数斯达克科技有限公司 Information query method and device, electronic equipment and readable storage medium
CN112286997A (en) * 2020-11-25 2021-01-29 平安数字信息科技(深圳)有限公司 Salary data query method based on distributed deployment and related equipment
CN113568970A (en) * 2021-02-03 2021-10-29 腾讯科技（深圳）有限公司 Application service data management method, device, equipment and storage medium
CN115033211A (en) * 2022-05-24 2022-09-09 青岛海尔科技有限公司 Method, device and equipment for querying article based on strategy mode and storage medium

Also Published As

Publication number Publication date
CN115858885B (en) 2023-06-30

Similar Documents

Publication Publication Date Title
CN107729376B (en) Insurance data auditing method and device, computer equipment and storage medium
KR102435151B1 (en) Personal information matching device and method thereof
CN108388512B (en) Data processing method and server
WO2019125608A1 (en) Management systems for personal identifying data, and methods relating thereto
CN110597511A (en) Page automatic generation method, system, terminal equipment and storage medium
EP2875479A1 (en) System and method for protecting consumer privacy in the measuring of the effectiveness of advertisements
CN112017007A (en) User behavior data processing method and device, computer equipment and storage medium
CN111586177B (en) Cluster session loss prevention method and system
US20220245125A1 (en) Dataset multiplexer for data processing system
CN114138651A (en) Test data generation method and device
CN115766296B (en) Authority control method, device, server and storage medium for user account
CN116993523A (en) Configurable account checking method, device, equipment and storage medium
CN115858885A (en) Account set data query method and device, computer equipment and storage medium
CN106874327B (en) Counting method and device for business data
CN110909376B (en) Paid user management method, device and system
CN114742547A (en) Internet online collection control method, device, medium and electronic equipment
CN114265633A (en) Application parameter configuration and query method of self-service equipment, equipment and storage medium
CN114186961A (en) Business approval process configuration method and device, computer equipment and storage medium
CN114548963A (en) Payment interaction processing method and device
US20240095400A1 (en) Anonymization protocols
CN111611056A (en) Data processing method and device, computer equipment and storage medium
KR102569812B1 (en) Apparatus for processing infomration related to use of coupons and method thereof
US20190332706A1 (en) Systems and Methods for Providing Data Structure Access
CN115423595B (en) File information processing method and device, computer equipment and storage medium
CN110443466B (en) Data processing method and device based on risk management system and electronic equipment

Legal Events

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