Business information query method, device and equipment, computer readable medium and product

Abstract

The embodiment of the invention discloses a business information query method, device and equipment, a computer readable medium and a product. A specific embodiment of the method comprises the following steps: in response to determining that service authority information and a service information query request of a user meet a preset global condition, determining a global service user data table, the combination of a service identifier and a user identity identifier in the table being unique and comprising a user identity identifier corresponding to each level; extracting a to-be-queried user identity identifier from the service information query request; and querying service information corresponding to the to-be-queried user identity identifier from the global service user data table and the service data table based on the to-be-queried user identity identifier. The embodiment is related to the database and the data query, the query of the service information corresponding to different levels of users can be realized through the flattened global service user data table, the data query efficiency is improved, the requirement on the performance of a database system is reduced, and meanwhile, the times of query timeout and database crash are also reduced.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular to a business information query method, apparatus, device, computer-readable medium, and product. Background Art

[0002] In the process of business development, it is necessary to store business data of different dimensions (such as different levels of member types) at different levels (such as different levels of business) and the corresponding member data in the database. The correspondence between the previous level and the next level and the correspondence between the previous dimension and the next dimension are usually one-to-many relationships. At present, when storing and querying business data and member data, the commonly used method is: the business data of each level and each dimension and the corresponding member data are stored separately as data tables. When querying, the data table associated with the next level or dimension is cascaded through the association relationship between the tables to realize the associated query of data tables of different levels and dimensions.

[0003] However, the inventors have found that when using the above method, the following technical problems often arise: the stored data is relatively scattered, and a relatively complex associated query needs to be constructed to obtain the query results at one time, which places high requirements on the performance of the database. In addition, when querying data, it is necessary to simultaneously query a large number of data tables, which requires a large number of IN queries. As a result, the performance of the database system is greatly affected, the number of query timeouts is high, and the number of database system crashes is also high when the amount of data is large.

[0004] The above information disclosed in this Background section is only for enhancement of understanding of the background of the inventive concept and therefore it may contain information that does not form the prior art that is already known to a person of ordinary skill in the art. Summary of the Invention

[0005] The content of this disclosure is used to briefly introduce concepts that will be described in detail in the detailed description section below. The content of this disclosure is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0006] Some embodiments of the present disclosure provide business information query methods, devices, equipment, computer-readable media, and products to solve one or more of the technical problems mentioned in the above background technology section.

[0007] In a first aspect, some embodiments of the present disclosure provide a business information query method, the method comprising: determining the business authority information of a user; in response to determining that the business authority information and the business information query request of the user meet a preset global condition, determining a global business user data table corresponding to the business information query request, wherein each record in the global business user data table includes a business identifier and a user identity identifier corresponding to the business information query request, the combination of the business identifier and the user identity identifier in the global business user data table is unique, and the global business user data table includes user identity identifiers corresponding to each level; extracting the user identity identifier to be queried from the business information query request; based on the user identity identifier to be queried, querying the business information corresponding to the user identity identifier to be queried from the global business user data table and the business data table, wherein the business data table includes various business data records, and each business data record includes a business identifier.

[0008] Optionally, the business data records in the above-mentioned business data table also include a person in charge identifier; and the above-mentioned method also includes: in response to determining that the above-mentioned business authority information and the above-mentioned business information query request do not meet the above-mentioned preset global conditions, based on the above-mentioned user identity identifier to be queried and the various person in charge identifiers in the above-mentioned business data table, querying the business information corresponding to the above-mentioned user identity identifier to be queried from the above-mentioned business data table.

[0009] Optionally, the above-mentioned determination of the global business user data table corresponding to the above-mentioned business information query request includes: in response to determining that the above-mentioned business information query request represents a query collaborative business, determining the business member global table as a global business user data table, wherein each record of the above-mentioned business member global table includes a business identifier, a user identifier and a user type, the user identity identifier in the above-mentioned global business user data table corresponds to the user identifier in the above-mentioned business member global table, and the combination of the business identifier and the user identifier in the above-mentioned business member global table is unique.

[0010] Optionally, the above-mentioned determination of the global business user data table corresponding to the above-mentioned business information query request includes: in response to determining that the above-mentioned business information query request represents a query for all businesses, determining the business organization global table as the global business user data table, wherein each record of the above-mentioned business organization global table includes a business identifier and an organization identifier, the user identity identifier in the above-mentioned global business user data table corresponds to the organization identifier in the above-mentioned business organization global table, and the combination of the business identifier and the organization identifier in the above-mentioned business organization global table is unique.

[0011] Optionally, the above-mentioned querying of business information corresponding to the user identity identifier to be queried from the above-mentioned global business user data table and the business data table based on the above-mentioned user identity identifier to be queried includes: selecting each business identifier whose corresponding user identity identifier is identical to the above-mentioned user identity identifier to be queried from the above-mentioned global business user data table; according to the above-mentioned each business identifier, querying each business data record whose corresponding business identifier is identical to the business identifier in the above-mentioned each business identifier from the above-mentioned business data table; generating business information corresponding to the above-mentioned user identity identifier according to the queried each business data record and each record corresponding to the above-mentioned each business identifier in the above-mentioned global business user data table.

[0012] Optionally, the above-mentioned business member global table is constructed through the following steps: obtaining each business dimension table, wherein the above-mentioned business dimension tables include a business dimension table corresponding to the first level, a business dimension table corresponding to the second level, and a business dimension table corresponding to the third level, and the business dimension table corresponding to the third level corresponds to the level of the above-mentioned business data table, and each record of each business dimension table includes a business dimension identifier and a user identifier, and each user identifier included in each business dimension table corresponds to the same user type; generating a business member global table according to the level, user identifier and user type corresponding to the above-mentioned business data table and each of the above-mentioned business dimension tables.

[0013] Optionally, the above-mentioned business organization global table is constructed through the following steps: for each record in the above-mentioned business member global table, the following steps are performed: obtaining the organization path information corresponding to the user identifier in the above-mentioned record, wherein the above-mentioned organization path information includes each organization identifier; splitting the above-mentioned organization path information to obtain each split organization identifier; generating each business organization information based on the business identifier in the above-mentioned record and each split organization identifier, wherein each business organization information includes a business identifier and an organization identifier; deduplicating the generated each business organization information according to the business identifier and the organization identifier; and saving each business organization information after deduplication as the business organization global table.

[0014] Optionally, the above-mentioned business member global table is generated based on the level, user identifier and user type corresponding to the above-mentioned business data table and the above-mentioned each business dimension table, including: constructing an empty table as the business member global table; for each record in the business dimension table of each first level corresponding to the target user type, based on the business member global table, performing the following steps: determining each group of records associated with the above-mentioned record in the above-mentioned each business dimension table and the above-mentioned business data table as an associated record group; for each associated record in the above-mentioned associated record group, performing the following new steps: in response to determining that the above-mentioned associated record belongs to the first level, determining whether the business member global table meets the first condition, wherein the above-mentioned first condition is that there exists a user identifier in the business member global table whose corresponding user type belongs to the second level or the third level and is the same as the user identifier included in the above-mentioned associated record; in response to determining that the above-mentioned first condition is met, modifying the user type of the above-mentioned user identifier in the business member global table to the user type corresponding to the above-mentioned associated record; in response to determining that the above-mentioned first condition is not met, adding the business identifier corresponding to the above-mentioned associated record group and the user type corresponding to the above-mentioned associated record to the business member global table.

[0015] Optionally, the above-mentioned newly added step also includes: in response to determining that the above-mentioned association record belongs to the second level, determining whether the business member global table meets the second condition, and determining whether the business member global table meets the third condition, wherein the above-mentioned second condition is that the corresponding user type in the business member global table belongs to the first level and is the same as the user identifier included in the above-mentioned association record, and the above-mentioned third condition is that the corresponding user type in the business member global table belongs to the third level and is the same as the user identifier included in the above-mentioned association record; in response to determining that the above-mentioned second condition is not met, the business identifier corresponding to the above-mentioned association record group and the user type corresponding to the above-mentioned association record are added to the business member global table together. business member global table; in response to determining that the above-mentioned third condition is met, modifying the user type of the above-mentioned user identifier in the business member global table to the user type corresponding to the above-mentioned association record; in response to determining that the above-mentioned third condition is not met, adding the business identifier corresponding to the above-mentioned association record group and the user type corresponding to the above-mentioned association record to the business member global table; in response to determining that the above-mentioned association record belongs to the third level, determining whether the business member global table meets the above-mentioned first condition or the above-mentioned second condition; in response to determining that the business member global table does not meet the above-mentioned first condition and the above-mentioned second condition, adding the business identifier corresponding to the above-mentioned association record group and the user type corresponding to the above-mentioned association record to the business member global table.

[0016] Optionally, the method further includes: in response to monitoring new information recorded in the business dimension table, updating the above-mentioned business member global table according to the associated record group corresponding to the above-mentioned new information; in response to monitoring the modification information recorded in the business dimension table, executing the following steps: in response to determining that the modification type representation record corresponding to the above-mentioned modification information is updated, updating the record corresponding to the above-mentioned modification information in the above-mentioned business member global table according to the above-mentioned modification information; in response to determining that the above-mentioned record belongs to the first level and the modification type representation record corresponding to the above-mentioned modification information is deleted, executing the following modification steps: determining whether the above-mentioned business member global table meets the fourth condition, wherein the above-mentioned fourth condition is that the corresponding user type in the business member global table belongs to the second level, and a user identifier that is identical to the user identifier corresponding to the above-mentioned modification information; in response to determining that the above-mentioned fourth condition is satisfied, modifying the user type of the above-mentioned user identifier in the above-mentioned business member global table to a user type corresponding to the second level; in response to determining that the above-mentioned fourth condition is not satisfied, determining whether the above-mentioned business member global table satisfies the fifth condition, wherein the above-mentioned fifth condition is that there exists in the business member global table a user identifier whose corresponding user type belongs to the third level and is identical to the user identifier corresponding to the above-mentioned modification information; in response to determining that the above-mentioned fifth condition is satisfied, modifying the user type of the above-mentioned user identifier in the above-mentioned business member global table to a user type corresponding to the third level; in response to determining that the above-mentioned fifth condition is not satisfied, deleting the record corresponding to the above-mentioned user identifier in the above-mentioned business member global table.

[0017] Optionally, the above-mentioned modification step also includes: in response to determining that the above-mentioned record belongs to the second level and the modification type representation record corresponding to the above-mentioned modification information is deleted, performing the following steps: determining whether the above-mentioned business member global table meets the above-mentioned fifth condition; in response to determining that the above-mentioned fifth condition is met, modifying the user type of the above-mentioned user identifier in the above-mentioned business member global table to a user type corresponding to the third level; in response to determining that the above-mentioned fifth condition is not met, deleting the record corresponding to the above-mentioned user identifier in the above-mentioned business member global table; in response to determining that the above-mentioned record belongs to the third level and the modification type representation record corresponding to the above-mentioned modification information is deleted, deleting the record corresponding to the above-mentioned user identifier in the above-mentioned business member global table.

[0018] Optionally, the method further includes: in response to detecting modification information of a record in the business member global table, executing the following steps: splitting the institution path information corresponding to the user identifier in the above record before modification to obtain an institution identifier set; combining the business identifier corresponding to the above record with each business identifier in the above institution identifier set to obtain each combination information; for each combination information in the above combination information, executing the following steps: determining each record in the above business institution global table that has no corresponding relationship with the user identifier corresponding to the above record as a record set; determining whether there is a record in the above record set that covers the above combination information; in response to determining that it does not exist, deleting the record corresponding to the above combination information in the above business institution global table; and deduplicating the business institution global table based on the business identifier and the institution identifier.

[0019] In a second aspect, some embodiments of the present disclosure provide a business information query device, the device comprising: a first determination unit, configured to determine the business authority information of a user; a second determination unit, configured to determine a global business user data table corresponding to the business information query request in response to determining that the business authority information and the business information query request of the user meet a preset global condition, wherein each record of the global business user data table includes a business identifier and a user identity identifier corresponding to the business information query request, the combination of the business identifier and the user identity identifier in the global business user data table is unique, and the global business user data table includes user identity identifiers corresponding to each level; an extraction unit, configured to extract the user identity identifier to be queried from the business information query request; a query unit, configured to query the business information corresponding to the user identity identifier to be queried from the global business user data table and the business data table based on the user identity identifier to be queried, wherein the business data table includes various business data records, and each business data record includes a business identifier.

[0020] Optionally, the business data record in the business data table further includes a person in charge identifier.

[0021] Optionally, the business information query device also includes: an information query unit, configured to, in response to determining that the above-mentioned business authority information and the above-mentioned business information query request do not meet the above-mentioned preset global conditions, query the business information corresponding to the above-mentioned user identity to be queried from the above-mentioned business data table based on the above-mentioned user identity to be queried and the various responsible person identifiers in the above-mentioned business data table.

[0022] Optionally, the second determination unit is further configured to: in response to determining that the above-mentioned business information query request represents a query collaborative business, determine the business member global table as a global business user data table, wherein each record of the above-mentioned business member global table includes a business identifier, a user identifier and a user type, the user identity identifier in the above-mentioned global business user data table corresponds to the user identifier in the above-mentioned business member global table, and the combination of the business identifier and the user identifier in the above-mentioned business member global table is unique.

[0023] Optionally, the second determination unit is further configured to: in response to determining that the above-mentioned business information query request represents a query for all businesses, determine the business organization global table as a global business user data table, wherein each record of the above-mentioned business organization global table includes a business identifier and an organization identifier, the user identity identifier in the above-mentioned global business user data table corresponds to the organization identifier in the above-mentioned business organization global table, and the combination of the business identifier and the organization identifier in the above-mentioned business organization global table is unique.

[0024] Optionally, the query unit is further configured to: select each business identifier whose corresponding user identity identifier is the same as the above-mentioned user identity identifier to be queried from the above-mentioned global business user data table; based on the above-mentioned each business identifier, query each business data record whose corresponding business identifier is the same as the business identifier in the above-mentioned each business identifier from the above-mentioned business data table; generate business information corresponding to the above-mentioned user identity identifier to be queried based on the queried each business data record and the each record corresponding to the above-mentioned each business identifier in the above-mentioned global business user data table.

[0025] Optionally, the above-mentioned business member global table is constructed through the following steps: obtaining each business dimension table, wherein the above-mentioned business dimension tables include a business dimension table corresponding to the first level, a business dimension table corresponding to the second level, and a business dimension table corresponding to the third level, and the business dimension table corresponding to the third level corresponds to the level of the above-mentioned business data table, and each record of each business dimension table includes a business dimension identifier and a user identifier, and each user identifier included in each business dimension table corresponds to the same user type; generating a business member global table according to the level, user identifier and user type corresponding to the above-mentioned business data table and each of the above-mentioned business dimension tables.

[0026] Optionally, the above-mentioned business organization global table is constructed through the following steps: for each record in the above-mentioned business member global table, the following steps are performed: obtaining the organization path information corresponding to the user identifier in the above-mentioned record, wherein the above-mentioned organization path information includes each organization identifier; splitting the above-mentioned organization path information to obtain each split organization identifier; generating each business organization information based on the business identifier in the above-mentioned record and each split organization identifier, wherein each business organization information includes a business identifier and an organization identifier; deduplicating the generated each business organization information according to the business identifier and the organization identifier; and saving each business organization information after deduplication as the business organization global table.

[0027] Optionally, the above-mentioned business member global table is generated based on the level, user identifier and user type corresponding to the above-mentioned business data table and the above-mentioned each business dimension table, and is further configured to: construct an empty table as the business member global table; for each record in the business dimension table of each first level corresponding to the target user type, based on the business member global table, perform the following steps: determine the groups of records associated with the above-mentioned record in the above-mentioned each business dimension table and the above-mentioned business data table as associated record groups; for each associated record in the above-mentioned associated record group, perform the following additional steps: in response to determining that the above-mentioned associated record belongs to the first level, determine whether the business member global table meets the first condition, wherein the above-mentioned first condition is that there exists a user identifier in the business member global table whose corresponding user type belongs to the second level or the third level and is the same as the user identifier included in the above-mentioned associated record; in response to determining that the above-mentioned first condition is met, modify the user type of the above-mentioned user identifier in the business member global table to the user type corresponding to the above-mentioned associated record; in response to determining that the above-mentioned first condition is not met, add the business identifier corresponding to the above-mentioned associated record group and the user type corresponding to the above-mentioned associated record to the business member global table.

[0028] Optionally, the above-mentioned newly added step also includes: in response to determining that the above-mentioned association record belongs to the second level, determining whether the business member global table meets the second condition, and determining whether the business member global table meets the third condition, wherein the above-mentioned second condition is that the corresponding user type in the business member global table belongs to the first level and is the same as the user identifier included in the above-mentioned association record, and the above-mentioned third condition is that the corresponding user type in the business member global table belongs to the third level and is the same as the user identifier included in the above-mentioned association record; in response to determining that the above-mentioned second condition is not met, the business identifier corresponding to the above-mentioned association record group and the user type corresponding to the above-mentioned association record are added to the business member global table together. business member global table; in response to determining that the above-mentioned third condition is met, modifying the user type of the above-mentioned user identifier in the business member global table to the user type corresponding to the above-mentioned association record; in response to determining that the above-mentioned third condition is not met, adding the business identifier corresponding to the above-mentioned association record group and the user type corresponding to the above-mentioned association record to the business member global table; in response to determining that the above-mentioned association record belongs to the third level, determining whether the business member global table meets the above-mentioned first condition or the above-mentioned second condition; in response to determining that the business member global table does not meet the above-mentioned first condition and the above-mentioned second condition, adding the business identifier corresponding to the above-mentioned association record group and the user type corresponding to the above-mentioned association record to the business member global table.

[0029] Optionally, the business information query device also includes: an update unit and a first execution unit. The update unit is configured to, in response to monitoring the new information recorded in the business dimension table, update the above-mentioned business member global table according to the associated record group corresponding to the above-mentioned new information. The first execution unit is configured to, in response to monitoring the modification information recorded in the business dimension table, execute the following steps: in response to determining that the modification type representation record corresponding to the above-mentioned modification information is updated, according to the above-mentioned modification information, update the record corresponding to the above-mentioned modification information in the above-mentioned business member global table; in response to determining that the above-mentioned record belongs to the first level and the modification type representation record corresponding to the above-mentioned modification information is deleted, execute the following modification steps: determine whether the above-mentioned business member global table meets the fourth condition, wherein the above-mentioned fourth condition is that there is a corresponding user type in the business member global table that belongs to the second level and is the same as the user identifier corresponding to the above-mentioned modification information; in response to determining that it meets the fourth condition, the ... In response to determining that the fourth condition is not met, the user type of the user identifier in the business member global table is modified to a user type corresponding to the second level; in response to determining that the fourth condition is not met, determining whether the business member global table meets the fifth condition, wherein the fifth condition is that there exists in the business member global table a user identifier whose corresponding user type belongs to the third level and is the same as the user identifier corresponding to the modification information; in response to determining that the fifth condition is met, the user type of the user identifier in the business member global table is modified to a user type corresponding to the third level; in response to determining that the fifth condition is not met, deleting the record corresponding to the user identifier in the business member global table.

[0030] Optionally, the above-mentioned modification step also includes: in response to determining that the above-mentioned record belongs to the second level and the modification type representation record corresponding to the above-mentioned modification information is deleted, performing the following steps: determining whether the above-mentioned business member global table meets the above-mentioned fifth condition; in response to determining that the above-mentioned fifth condition is met, modifying the user type of the above-mentioned user identifier in the above-mentioned business member global table to a user type corresponding to the third level; in response to determining that the above-mentioned fifth condition is not met, deleting the record corresponding to the above-mentioned user identifier in the above-mentioned business member global table; in response to determining that the above-mentioned record belongs to the third level and the modification type representation record corresponding to the above-mentioned modification information is deleted, deleting the record corresponding to the above-mentioned user identifier in the above-mentioned business member global table.

[0031] Optionally, the business information query device also includes: a second execution unit, configured to execute the following steps in response to detecting the modification information of the record in the business member global table: splitting the organization path information corresponding to the user identifier in the above record before the modification to obtain an organization identifier set; combining the business identifier corresponding to the above record with each business identifier in the above organization identifier set to obtain each combination information; for each combination information in the above combination information, executing the following steps: determining each record in the above business organization global table that has no corresponding relationship with the user identifier corresponding to the above record as a record set; determining whether there is a record in the above record set that covers the above combination information; in response to determining that it does not exist, deleting the record corresponding to the above combination information in the above business organization global table; and deduplicating the business organization global table based on the business identifier and the organization identifier.

[0032] In a third aspect, some embodiments of the present disclosure provide an electronic device comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by one or more processors, the one or more processors implement the method described in any implementation of the first aspect above.

[0033] In a fourth aspect, some embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method described in any implementation of the first aspect is implemented.

[0034] In a fifth aspect, some embodiments of the present disclosure provide a computer program product, including a computer program, which implements the method described in any implementation of the first aspect when executed by a processor.

[0035] The above-described embodiments of the present disclosure have the following beneficial effects: Through the business information query method of some embodiments of the present disclosure, business information corresponding to users at different levels can be queried using a flattened global business user data table, thereby improving data query efficiency, reducing database system performance requirements, and reducing query timeouts and database crashes. Specifically, the high database performance requirements, high query timeouts, and high database system crashes are caused by the fact that the stored data is relatively dispersed, requiring the construction of complex related queries to obtain query results in one go. This places high database performance requirements on the database, and the need to simultaneously query multiple data tables when querying data requires the use of a large number of IN queries, which significantly impacts database system performance, leading to high query timeouts and, when the data volume is large, high database system crashes. Based on this, the business information query method of some embodiments of the present disclosure first determines the user's business permission information. This allows the business permission of the user whose business information is being queried to be determined. Then, in response to determining that the business permission information and the user's business information query request meet preset global conditions, a global business user data table corresponding to the business information query request is determined. Each record in the global business user data table includes a business identifier and a user identity corresponding to the business information query request. The combination of the business identifier and user identity in the global business user data table is unique. The global business user data table includes user identities corresponding to each level. Therefore, when the current user's business permissions support querying global data tables, the global business user data table corresponding to their business permissions can be determined. Next, the user identity to be queried is extracted from the business information query request. This allows the current user's query criteria to be determined. Finally, based on the user identity to be queried, the business information corresponding to the user identity to be queried is queried from the global business user data table and the business data table. The business data table includes business data records, each of which includes a business identifier. Thus, business information can be queried from both the business data table and the global business user data table that matches the user's business permissions to respond to the user's business information query request. Because data records corresponding to user identities at different levels are all stored in the global business user data table, flat data storage is achieved. Only two tables are used when querying business information, eliminating the need for complex associated queries and large numbers of IN queries. This improves the query efficiency of business information, reduces the requirements for database system performance, and also reduces the number of query timeouts and database crashes. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.

[0037] Figure 1 is an architectural diagram of an exemplary system in which some embodiments of the present disclosure may be applied;

[0038] Figure 2 is a flow chart of some embodiments of the business information query method according to the present disclosure;

[0039] Figure 3 is a flowchart of constructing a business member global table according to some embodiments of the business information query method disclosed herein;

[0040] Figure 4 is a flowchart of constructing a business organization global table according to some embodiments of the business information query method disclosed herein;

[0041] Figure 5 is a schematic structural diagram of some embodiments of the business information query device according to the present disclosure;

[0042] Figure 6 It is a structural diagram of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION

[0043] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0044] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other.

[0045] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0046] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0047] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0048] With regard to the collection, storage, and use of user personal information (such as business authority information and user type) involved in this disclosure, before performing the corresponding operations, the relevant organizations or individuals shall fulfill their obligations, including conducting personal information security impact assessments, fulfilling the obligation to inform the personal information subjects, and obtaining the authorization and consent of the personal information subjects in advance.

[0049] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0050] Figure 1 An exemplary system architecture 100 is shown to which a business information query method or a business information query device according to some embodiments of the present disclosure may be applied.

[0051] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. Network 104 is a medium for providing communication links between terminal devices 101, 102, 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0052] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as web browser applications, business query applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0053] Terminal devices 101, 102, and 103 can be either hardware or software. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices with display screens that support information display, including but not limited to smartphones, tablet computers, e-book readers, laptop computers, and desktop computers. When terminal devices 101, 102, and 103 are software, they can be installed in the electronic devices listed above. They can be implemented as multiple software programs or software modules, for example, to provide distributed services, or as a single software program or software module. This is not specifically limited here.

[0054] The server 105 may be a server that provides various services, such as a backend server that supports the business information displayed on the terminal devices 101, 102, and 103. The backend server may analyze and process received data such as business information query requests, and feed back the processing results (such as business information) to the terminal device.

[0055] It should be noted that the service information query method provided in the embodiments of the present disclosure may be executed by the server 105 . Accordingly, the service information query device may be provided in the server 105 .

[0056] It should be noted that the server can be either hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the server is software, it can be implemented as multiple software programs or software modules, for example, to provide distributed services, or as a single software program or software module. This is not specifically limited here.

[0057] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.

[0058] Continue to refer Figure 2 , shows a process 200 of some embodiments of the business information query method according to the present disclosure. The business information query method includes the following steps:

[0059] Step 201: Determine the user's service authority information.

[0060] In some embodiments, the execution subject of the business information query method (eg Figure 1 The server (shown) can determine the user's service permission information. The user may be a user who has sent a service information query request to query service information via a terminal device. The service permission information may represent the service permissions corresponding to the user. For example, the service permission information may include personal data permissions or full data permissions. Users with personal data permissions can view personal and collaborative service information. Users with full data permissions can view all service information.

[0061] Step 202 : In response to determining that the business authority information and the business information query request of the user meet a preset global condition, a global business user data table corresponding to the business information query request is determined.

[0062] In some embodiments, the execution entity may determine a global service user data table corresponding to the service information query request in response to determining that the service permission information and the user's service information query request meet preset global conditions. The preset global conditions may include the service permission information indicating individual data permissions and the service information query request indicating a query for collaborative services. Alternatively, the preset global conditions may include the service permission information indicating all data permissions and the service information query request indicating a query for all services. A service information query request may be a user request for service information sent by a user via a terminal device and may include, but is not limited to, a service type and a user identity to be queried. The service type may indicate the type of service to be queried, including, but not limited to, personal service, collaborative service, and all services. Personal service may indicate a service for which an individual is responsible. Collaborative service may indicate a service completed collaboratively by multiple individuals and individuals. All services may indicate all services under different organizations. The user identity to be queried may indicate the relevant identifier of the user to be queried. For example, when querying personal services or collaborative services, the user identity to be queried may be a user ID. When querying all services, the user identity to be queried may be an organization ID, indicating a query for relevant service information for all individuals under that organization. The organization ID can represent the unique ID corresponding to the personnel organization.

[0063] The global business user data table may be a global data table corresponding to a business information query request, including business-related records for the user identity to be queried. Each record in the global business user data table includes a business identifier and the user identity corresponding to the business information query request. For example, if the business information query request indicates a query for individual or collaborative business, the user identity may be a user identity. If the business information query request indicates a query for all businesses, the user identity may be an organization identity. It should be noted that the business identifier corresponding to the global business user data table may be the identifier of the lowest-level business. For example, the overall business can be divided into three levels: brand, customer, and opportunity. A brand can correspond to at least one customer, and a customer can correspond to at least one business opportunity. Therefore, the global business user data table may be for businesses at the opportunity level. Each business level may have a corresponding person in charge and team members. That is, each user's user type is either a person in charge or a team member at the corresponding level. Therefore, the global business user data table may include user identities for different user types at different levels. The combination of a business identifier and a user identity in the global business user data table is unique. The global business user data table includes user identities for each level. The above-mentioned global business user data table may be pre-built and continuously maintained.

[0064] In some optional implementations of some embodiments, the above-mentioned execution entity may determine the business member global table as a global business user data table in response to determining that the above-mentioned business information query request represents a query for a collaborative business. Each record of the above-mentioned business member global table may include but is not limited to a business identifier, a user identifier, and a user type. Each record of the above-mentioned business member global table may also include a user name. The user identity identifier in the above-mentioned global business user data table corresponds to the user identifier in the above-mentioned business member global table. The combination of the business identifier and the user identifier in the above-mentioned business member global table is unique. In practice, the above-mentioned execution entity may determine the business member global table that is pre-built and continuously maintained as a global business user data table. Thus, when querying a collaborative business, the business member global table can be determined as the global table that responds to the query request.

[0065] In some optional implementations of some embodiments, the execution subject may also determine the business organization global table as the global business user data table in response to determining that the business information query request represents a query for all businesses. Each record in the business organization global table may include but is not limited to a business identifier and an organization identifier. Each record in the business organization global table may also include an organization name. For example, the organization path information of a person may be XX Logistics (001) - Supply Chain (002) - Guangdong (003) - Guangzhou (004). XX Logistics, Supply Chain, Guangdong, Guangzhou are organization names, and 001, 002, 003, 004 are organization identifiers. The user identity identifier in the global business user data table corresponds to the organization identifier in the business organization global table. The combination of the business identifier and the organization identifier in the business organization global table is unique. Thus, when querying all businesses, the business organization global table may be determined as the global table that responds to the query request.

[0066] Optionally, the execution subject may also, in response to determining that the business authority information and the business information query request do not satisfy the preset global conditions, query the business information corresponding to the user identity to be queried from the business data table based on the user identity to be queried and the respective responsible person identifiers in the business data table. Wherein, when the business authority information represents personal data authority and the business information query request represents a query for personal business, the preset global conditions are not satisfied. The business data record in the business data table may also include a responsible person identifier. The responsible person identifier may indicate that the corresponding business is the responsibility of the user corresponding to the responsible person identifier. At this time, the execution subject may query the business data records including the responsible person identifier and the user identity to be queried from the business data table as business information. In this way, the responsible user can query the business information under the personal business.

[0067] Step 203: extract the user identity to be queried from the service information query request.

[0068] In some embodiments, the execution entity may extract the user identity to be queried from the service information query request. In practice, the execution entity may parse the service information query request to obtain the user identity to be queried.

[0069] Step 204 : Based on the user identity to be queried, query the global service user data table and the service data table for service information corresponding to the user identity to be queried.

[0070] In some embodiments, the execution entity may query the global business user data table and business data table for business information corresponding to the user identity to be queried based on the user identity to be queried. The business data table includes individual business data records. Each business data record may include a business identifier. A business data record may be a detailed data record for a business. For example, if the business is a business opportunity, the business data record may include the business opportunity identifier and business opportunity information. Business opportunity information may include, but is not limited to, the business opportunity name. For example, if the brand is XX and the client is XX Logistics, and the business opportunity is a delivery opportunity, the business opportunity information may include the business opportunity name, delivery destination, delivery vehicle, delivery time, and delivery distance. If the business opportunity is a procurement opportunity, the business opportunity information may include the business opportunity name, purchase item name, supplier, item quantity, and item value. In practice, the execution entity may first extract each record from the global business user data table whose corresponding user identity matches the user identity to be queried. Then, for each extracted record, the business data record whose corresponding business identifier matches the business identifier included in the record may be extracted from the business data table. The record may then be combined with the business data record to form a query result. Finally, the combined query results may be determined as the business information corresponding to the user identity to be queried.

[0071] In some optional implementations of some embodiments, the execution entity may query the service information corresponding to the user identity to be queried from the global service user data table and the service data table based on the user identity to be queried through the following steps:

[0072] The first step is to select, from the global service user data table, each service identifier whose corresponding user identity is identical to the user identity to be queried. In practice, when the determined global service user data table is a global service member table, the execution entity may select, from the global service user data table, each service identifier whose corresponding user identity is identical to the user identity to be queried. When the determined global service user data table is a global service organization table, the execution entity may select, from the global service user data table, each service identifier whose corresponding organization identity is identical to the user identity to be queried.

[0073] In the second step, based on the above-mentioned service identifiers, the service data table is searched for service data records whose corresponding service identifiers are the same as the service identifiers in the above-mentioned service identifiers.

[0074] The third step is to generate business information corresponding to the user identity being queried based on the queried business data records and the records corresponding to the business identifiers in the global business user data table. In practice, the execution entity can perform a left outer join of the records with the queried business data records to generate a query table as the business information. This allows query results to be obtained through inter-table queries and joins.

[0075] The above-described embodiments of the present disclosure have the following beneficial effects: Through the business information query method of some embodiments of the present disclosure, business information corresponding to users at different levels can be queried using a flattened global business user data table, thereby improving data query efficiency, reducing database system performance requirements, and reducing query timeouts and database crashes. Specifically, the high database performance requirements, high query timeouts, and high database system crashes are caused by the fact that the stored data is relatively dispersed, requiring the construction of complex related queries to obtain query results in one go. This places high database performance requirements on the database, and the need to simultaneously query multiple data tables when querying data requires the use of a large number of IN queries, which significantly impacts database system performance, leading to high query timeouts and, when the data volume is large, high database system crashes. Based on this, the business information query method of some embodiments of the present disclosure first determines the user's business permission information. This allows the business permission of the user whose business information is being queried to be determined. Then, in response to determining that the business permission information and the user's business information query request meet preset global conditions, a global business user data table corresponding to the business information query request is determined. Each record in the global business user data table includes a business identifier and a user identity corresponding to the business information query request. The combination of the business identifier and user identity in the global business user data table is unique. The global business user data table includes user identities corresponding to each level. Therefore, when the current user's business permissions support querying global data tables, the global business user data table corresponding to their business permissions can be determined. Next, the user identity to be queried is extracted from the business information query request. This allows the current user's query criteria to be determined. Finally, based on the user identity to be queried, the business information corresponding to the user identity to be queried is queried from the global business user data table and the business data table. The business data table includes business data records, each of which includes a business identifier. Thus, business information can be queried from both the business data table and the global business user data table that matches the user's business permissions to respond to the user's business information query request. Because data records corresponding to user identities at different levels are all stored in the global business user data table, flat data storage is achieved. Only two tables are used when querying business information, eliminating the need for complex associated queries and large numbers of IN queries. This improves the query efficiency of business information, reduces the requirements for database system performance, and also reduces the number of query timeouts and database crashes.

[0076] Further references Figure 3 , which shows a process 300 for constructing a business member global table of a business information query method. The process 300 for constructing a business member global table includes the following steps:

[0077] Step 301: Obtain each business dimension table.

[0078] In some embodiments, the execution subject of the business information query method (eg Figure 1 The server shown) can obtain each business dimension table from the database through a wired connection or a wireless connection. Among them, the above-mentioned business dimension tables include a business dimension table corresponding to the first level, a business dimension table corresponding to the second level, and a business dimension table corresponding to the third level. The business dimension table corresponding to the third level corresponds to the level of the above-mentioned business data table. Each record of each business dimension table includes a business dimension identifier and a user identifier. The business dimension identifier can be used to uniquely identify each record. Each user identifier included in each business dimension table corresponds to the same user type. Each record of the business dimension table corresponding to the second level and the person in charge type also includes the corresponding business dimension identifier of the first level, and each record of the business dimension table corresponding to the third level and the person in charge type also includes the corresponding business dimension identifier of the second level. Each record of the business dimension table corresponding to the first level and the member type also includes the business dimension identifier of the corresponding first level person in charge type to achieve association with the business dimension table of the first level person in charge type. Each record of the business dimension table corresponding to the second level and the member type also includes the business dimension identifier of the corresponding second level person in charge type to achieve association with the business dimension table of the second level person in charge type. Each record of the business dimension table corresponding to the third level and member type also includes the business identifier of the corresponding third level person in charge type to achieve association with the business data table.

[0079] For example, the first level may correspond to brands. The business dimension tables corresponding to the first level may include a business dimension table corresponding to brand managers and a business dimension table corresponding to brand team members. Each user ID in the business dimension table corresponding to the brand manager corresponds to the user type of brand manager. Each user ID in the business dimension table corresponding to the brand team member corresponds to the user type of brand team member. Each record in the business dimension table corresponding to the brand team member includes the business dimension ID of the corresponding brand manager, thereby establishing a link with the business dimension table corresponding to the brand manager. The second level may correspond to customers. The business dimension tables corresponding to the second level may include a business dimension table corresponding to customer managers and a business dimension table corresponding to customer team members. Each user ID in the business dimension table corresponding to the customer manager corresponds to the user type of customer manager. Each user ID in the business dimension table corresponding to the customer team member corresponds to the user type of customer team member. Each record in the business dimension table corresponding to the customer team member includes the business dimension ID of the corresponding customer manager, thereby establishing a link with the business dimension table corresponding to the customer manager. The third level may correspond to opportunities. The business dimension tables corresponding to the third level may include a business dimension table corresponding to opportunity team members. The user type corresponding to each user ID included in the business dimension table corresponding to the business opportunity team member is the business opportunity team member. The corresponding user type is the user ID (person in charge ID) of the business opportunity person in charge stored in the above-mentioned business data table. The business data table can be a data table for the corresponding business opportunity person in charge. Each record in the business dimension table corresponding to the business opportunity team member includes the business ID of the corresponding business opportunity person in charge to achieve association with the corresponding business data table. The business dimension table corresponding to the business opportunity team member and the above-mentioned business data table both correspond to the third level (business opportunity). The business ID in each business dimension table corresponds to its corresponding level and user type. For example, in the business dimension table of the brand team member, the business ID is the brand team member ID.

[0080] Step 302: Generate a business member global table based on the levels, user identifiers, and user types corresponding to the business data table and each business dimension table.

[0081] In some embodiments, the execution entity may generate a global table of business members based on the levels, user identifiers, and user types corresponding to the above-mentioned business dimension tables. In practice, for each associated record group, the execution entity may combine the business identifier corresponding to the associated record group with the corresponding user identifiers and user types to obtain each initial combination information. Then, for each group of initial combination information with repeated user identifiers, only the initial combination information with the highest corresponding level is retained. Finally, the obtained initial combination information may be saved to an empty table to obtain a global table of business members. The associated record group may be data with an associated relationship consisting of a record of a business dimension table of a first-level person in charge type, a record of a business dimension table of a first-level team member type, a corresponding record of a business dimension table of a second-level person in charge type, a corresponding record of a business dimension table of a second-level team member type, a corresponding record of a business data table of a third-level person in charge type, and a corresponding record of a business dimension table of a third-level team member type.

[0082] In some optional implementations of some embodiments, the execution entity may generate a business member global table according to the levels, user identifiers, and user types corresponding to the business data table and each of the business dimension tables through the following steps:

[0083] The first step is to build an empty table as the global table for business members.

[0084] In the second step, for each record in the first-level business dimension table corresponding to the target user type, perform the following steps based on the business member global table:

[0085] In the first sub-step, each group of records associated with the above-mentioned records in the above-mentioned business dimension tables and the above-mentioned business data tables are determined as associated record groups. Among them, the above-mentioned target user type can be a person in charge type. In practice, the above-mentioned execution subject can search in the above-mentioned business dimension tables and the above-mentioned business data tables in the order of the records corresponding to the first-level person in charge (i.e., the above-mentioned records), the records corresponding to a corresponding first-level team member, the records corresponding to a corresponding second-level person in charge, the records corresponding to a corresponding second-level team member, the records corresponding to a corresponding third-level person in charge, and the records corresponding to a corresponding third-level team member, to obtain each group of records as an associated record group.

[0086] In the second sub-step, for each associated record in the above associated record group, perform the following additional steps:

[0087] First, in response to determining that the association record belongs to the first level, determining whether the business member global table satisfies a first condition. The first condition is that the business member global table contains a user ID that is of the second or third level and is the same as the user ID included in the association record.

[0088] Second, in response to determining that the first condition is met, the user type of the user identifier in the business member global table is modified to the user type corresponding to the associated record. In practice, if the user type corresponding to the business dimension table corresponding to the associated record is a first-level person in charge, the modified user type is a first-level person in charge.

[0089] Third, in response to determining that the first condition is not met, the business identifier corresponding to the above-mentioned association record group and the user type corresponding to the above-mentioned association record are added to the business member global table. The business identifier corresponding to the above-mentioned association record group can be the business identifier included in the association record corresponding to the third-level person in charge in the above-mentioned association record group (i.e., the record in the business data table). Therefore, when adding user data of the first level, it is possible to check whether the user data of the user already exists in the business member global table at all levels below. If so, the user type of the user is modified to the user type of the first level. If not, it is directly added.

[0090] Optionally, the above-mentioned additional steps may further include:

[0091] Fourth, in response to determining that the association record belongs to the second level, determine whether the business member global table satisfies a second condition and a third condition. The second condition is that the business member global table contains a user ID that is of the same user type as the first level and includes the association record. The third condition is that the business member global table contains a user ID that is of the same user type as the third level and includes the association record.

[0092] Fifth, in response to determining that the second condition is not satisfied, the service identifier corresponding to the association record group and the user type corresponding to the association record are added to the service member global table.

[0093] Sixth, in response to determining that the third condition is met, the user type of the user identifier in the business member global table is modified to the user type corresponding to the association record.

[0094] Seventh, in response to determining that the third condition is not met, the business identifier corresponding to the associated record group and the user type corresponding to the associated record are added to the business member global table. Thus, when adding second-level user data, the business member global table at the upper level is first checked to see if the user data for that user already exists. If so, it is ignored; otherwise, it is added directly. Then, the business member global table at the lower level is checked to see if the user data for that user already exists. If so, the user type is modified to the second-level user type; otherwise, it is added directly.

[0095] Eighth, in response to determining that the association record belongs to the third level, determine whether the business member global table meets the first condition or the second condition.

[0096] Ninth, in response to determining that the business member global table does not meet the first and second conditions, the business identifier corresponding to the associated record group and the user type corresponding to the associated record are added to the business member global table. Thus, when adding user data at the third level, all levels above the level can verify whether the user data for that user already exists in the business member global table. If it exists, it will be ignored; otherwise, it will be added directly.

[0097] As an example, a related record group may include the following data:

[0098]

[0099]

[0100] The initial combination information generated for the above associated record groups is saved in the business member global table and then referred to the following table:

[0101]

[0102] Optionally, the execution entity may, in response to monitoring new information recorded in a business dimension table, update the business member global table according to the associated record group corresponding to the new information. The new information may represent a new record in at least one business dimension table. In practice, the method for determining the associated record group will not be described in detail. The method for updating the business member global table according to the associated record group corresponding to the new information can refer to the steps for constructing the business member global table and will not be described in detail.

[0103] Optionally, the execution entity may execute the following steps in response to monitoring modification information recorded in the business dimension table:

[0104] The first step is to, in response to determining that the modification type corresponding to the modification information represents a record update, update the record corresponding to the modification information in the business member global table according to the modification information. The modification information may include a user identifier and a modification type. The modification type may include a record update and a record deletion. When the modification type is a record update, the modification information may also include a pre-modification record and a post-modification record. In practice, the execution entity may update the record corresponding to the modification information in the business member global table according to the logic of deleting the pre-modification record and then adding a post-modification record. The method of deleting the pre-modification record can refer to the following modification steps. The method of adding a post-modification record can refer to the method of updating the business member global table.

[0105] In the second step, in response to determining that the record belongs to the first level and the modification type corresponding to the modification information indicates record deletion, the following modification steps are performed:

[0106] The first sub-step is to determine whether the business member global table satisfies a fourth condition, wherein the fourth condition is that the business member global table contains a user ID that belongs to the second level and is the same as the user ID corresponding to the modification information.

[0107] The second sub-step is, in response to determining that the fourth condition is met, modifying the user type of the user identifier in the business member global table to a user type corresponding to the second level.

[0108] The third sub-step is, in response to determining that the fourth condition is not met, determining whether the business member global table meets the fifth condition, wherein the fifth condition is that the business member global table contains a user ID whose corresponding user type belongs to the third level and is the same as the user ID corresponding to the modification information.

[0109] A fourth sub-step is, in response to determining that the fifth condition is satisfied, modifying the user type of the user identifier in the business member global table to a user type corresponding to the third level.

[0110] In a fifth sub-step, in response to determining that the fifth condition is not satisfied, the record corresponding to the user identifier in the business member global table is deleted. Thus, when deleting user data at the first level, a check is performed at the second level to determine whether the user data for the user already exists in the business member global table. If so, the user type of the user is modified to the second level user type. If not, a check is performed at the third level to determine whether the user data for the user already exists in the business member global table. If so, the user type is modified to the third level user type. If not, the user is directly deleted from the business member global table.

[0111] Optionally, the above modification step may further include:

[0112] In the first step, in response to determining that the record belongs to the second level and the modification type corresponding to the modification information indicates record deletion, the following steps are performed:

[0113] The first sub-step is to determine whether the business member global table satisfies the fifth condition.

[0114] The second sub-step is, in response to determining that the fifth condition is met, modifying the user type of the user identifier in the business member global table to a user type corresponding to the third level.

[0115] In the third sub-step, in response to determining that the fifth condition is not met, the record corresponding to the user identifier in the business member global table is deleted. Thus, when deleting the second-level user data, a check is performed at the third level to determine whether the user data of the user already exists in the business member global table. If so, the user type of the user is modified to the third-level user type. If not, the user is directly deleted from the business member global table.

[0116] In the second step, in response to determining that the record belongs to the third level and the modification type corresponding to the modification information indicates record deletion, the record corresponding to the user identifier in the business member global table is deleted. In this way, when deleting user data of the third level, it can be directly deleted from the business member global table.

[0117] from Figure 3 It can be seen that Figure 2 Compared with the description of some corresponding embodiments, Figure 3 Process 300 of the business information query method in some corresponding embodiments embodies the steps of expanding the construction of a global table of business members. Thus, the solutions described in these embodiments can flatten multi-dimensional permission control data and multi-level cascading permission control onto a single dimension, solving the problem of refined management and control at each level during the customer development process. It can also reduce the number of control levels and avoid technically out-of-scope data queries, thereby supporting large-scale horizontal expansion of personnel data.

[0118] Further references Figure 4 , which shows a process 400 for constructing a business organization global table of a business information query method. The process 400 for constructing a business organization global table includes the following steps:

[0119] Step 401: For each record in the business member global table, perform the following steps:

[0120] Step 4011: Obtain the organization path information corresponding to the user identifier in the record, wherein the organization path information includes each organization identifier.

[0121] In some embodiments, the execution subject of the business information query method (eg Figure 1 The server shown in the figure) can obtain the organization path information corresponding to the user identifier in the above record from the database through a wired connection or a wireless connection. Specifically, it can be obtained through a pre-packaged interface for obtaining the user's organization path information. The user identifier can be used as an input parameter of the above interface. The organization path information can be a hierarchical path of the personnel organization to which the user belongs. The above organization path information can include various organization identifiers. There can be a hierarchical order from top to bottom between the various organization identifiers. The organization path information can be XX Logistics (001)-Supply Chain (002)-Guangdong (003)-Guangzhou (004).

[0122] Step 4012: split the organization path information to obtain the identification of each split organization.

[0123] In some embodiments, the execution entity may split the organization path information to obtain the split organization identifiers. For example, the organization path information may be XX Logistics (001) - Supply Chain (002) - Guangdong (003) - Guangzhou (004). The split organization identifiers may be: 001, 002, 003, 004.

[0124] Optionally, the split organization identifiers may not include the top-level organization identifier. This eliminates the need to store the top-level organization identifier, as all personnel with access to the organization's data scope should have unrestricted access. This reduces invalid, redundant data. For example, the split organization identifiers may be: 002, 003, and 004.

[0125] Step 4013: Generate information of each business organization based on the business identifier in the record and the identifiers of each organization that has been split.

[0126] In some embodiments, the execution entity may generate information about each business organization based on the business identifier in the record and the individual organization identifiers that have been split. Information about each business organization may include a business identifier and an organization identifier. Information about each business organization may also include an organization name. In practice, the execution entity may combine the business identifier with each of the individual organization identifiers as business organization information to obtain information about each business organization. Alternatively, the execution entity may combine the business identifier with each of the individual organization identifiers and the organization name corresponding to the individual organization identifiers as business organization information to obtain information about each business organization.

[0127] As an example, a record in the business member global table can refer to the following table:

[0128]

[0129] Among them, the organization path information corresponding to the user identifier maliu can be XX Logistics (001) - Supply Chain (002) - Guangdong (003) - Guangzhou (004). The business organization information generated for the above records and user identifiers is saved in the business organization global table and can be referred to in the following table:

[0130]

[0131]

[0132] Step 402: De-duplication processing is performed on the generated information of each business organization according to the business identifier and the organization identifier.

[0133] In some embodiments, the execution entity may perform deduplication processing on the generated business organization information in a manner that the combination of the corresponding business identifier and the organization identifier is unique.

[0134] Step 403: Save the deduplicated information of each business organization as a global business organization table.

[0135] In some embodiments, the execution entity may save the deduplicated information of each business organization into an empty table as a global business organization table.

[0136] Optionally, the execution entity may execute the following steps in response to detecting modification information recorded in the business member global table:

[0137] The first step is to split the organization path information corresponding to the user ID in the record before modification to obtain an organization ID set. Here, the splitting method can refer to step 4012 and will not be repeated here.

[0138] In the second step, the business identifier corresponding to the above record is combined with each business identifier in the above organization identifier set to obtain each combination information, wherein each combination information includes a business identifier and an organization identifier.

[0139] Step 3: For each of the above combinations, perform the following steps:

[0140] In a first sub-step, each record in the business organization global table that does not correspond to the user identifier corresponding to the record is identified as a record set. The records in the business organization global table that do not correspond to the user identifier corresponding to the record may include business organization information assembled using organization path information of other user identifiers different from the user identifier.

[0141] The second sub-step is to determine whether the record set contains a record that includes the combined information. In practice, the execution entity may determine whether the record set contains a record that includes the same business identifier and organization identifier as the combined information.

[0142] In a third sub-step, in response to determining that the combination information does not exist, the record corresponding to the combination information in the business organization global table is deleted. The record corresponding to the combination information in the business organization global table may be a record in which the business identifier and organization identifier included in the business organization global table are identical to the business identifier and organization identifier included in the combination information.

[0143] The fourth step is to deduplicate the global business organization table based on the business ID and organization ID. In practice, the execution entity can deduplicate each record in the global business organization table based on the unique combination of the corresponding business ID and organization ID. This allows the global business organization table to be dynamically updated when a record in the table changes.

[0144] from Figure 4 It can be seen that Figure 2 Compared with the description of some corresponding embodiments, Figure 4 Process 400 of the business information query method in some corresponding embodiments embodies the steps of expanding the construction of a global table for business organizations. Thus, the solutions described in these embodiments can further flatten multi-dimensional permission control data and multi-level cascading permission control onto a single dimension, addressing the issue of refined management and control at each level during customer development. It can also reduce the number of control levels and avoid technically-induced data query out-of-scope situations, thereby supporting the extensive horizontal expansion of personnel organization depth and personnel data.

[0145] Further references Figure 5 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a business information query device. These device embodiments are similar to Figure 2 Corresponding to the method embodiments shown, the device can be specifically applied to various electronic devices.

[0146] like Figure 5As shown, a service information query apparatus 500 in some embodiments includes: a first determining unit 501, a second determining unit 502, an extraction unit 503, and a query unit 504. The first determining unit 501 is configured to determine the service authority information of a user; the second determining unit 502 is configured to, in response to determining that the service authority information and the service information query request of the user meet a preset global condition, determine a global service user data table corresponding to the service information query request, wherein each record in the global service user data table includes a service identifier and a user identity identifier corresponding to the service information query request, the combination of the service identifier and the user identity identifier in the global service user data table is unique, and the global service user data table includes user identities corresponding to each level; the extraction unit 503 is configured to extract the user identity identifier to be queried from the service information query request; and the query unit 504 is configured to query the service information corresponding to the user identity identifier to be queried from the global service user data table and the service data table based on the user identity identifier to be queried, wherein the service data table includes various service data records, and each service data record includes a service identifier.

[0147] Optionally, the business data record in the business data table further includes a person in charge identifier.

[0148] Optionally, the business information query device 500 may also include: an information query unit (not shown in the figure), which is configured to, in response to determining that the above-mentioned business authority information and the above-mentioned business information query request do not meet the above-mentioned preset global conditions, query the business information corresponding to the above-mentioned user identity to be queried from the above-mentioned business data table based on the above-mentioned user identity to be queried and the various responsible person identifiers in the above-mentioned business data table.

[0149] Optionally, the second determination unit 502 can be further configured to: in response to determining that the above-mentioned business information query request represents a query collaborative business, determine the business member global table as a global business user data table, wherein each record of the above-mentioned business member global table includes a business identifier, a user identifier and a user type, the user identity identifier in the above-mentioned global business user data table corresponds to the user identifier in the above-mentioned business member global table, and the combination of the business identifier and the user identifier in the above-mentioned business member global table is unique.

[0150] Optionally, the second determination unit 502 can be further configured to: in response to determining that the above-mentioned business information query request represents a query for all businesses, determine the business organization global table as a global business user data table, wherein each record of the above-mentioned business organization global table includes a business identifier and an organization identifier, the user identity identifier in the above-mentioned global business user data table corresponds to the organization identifier in the above-mentioned business organization global table, and the combination of the business identifier and the organization identifier in the above-mentioned business organization global table is unique.

[0151] Optionally, the query unit 504 can be further configured to: select each business identifier whose corresponding user identity identifier is the same as the above-mentioned user identity identifier to be queried from the above-mentioned global business user data table; based on the above-mentioned each business identifier, query each business data record whose corresponding business identifier is the same as the business identifier in the above-mentioned each business identifier from the above-mentioned business data table; generate business information corresponding to the above-mentioned user identity identifier to be queried based on the queried each business data record and the each record corresponding to the above-mentioned each business identifier in the above-mentioned global business user data table.

[0152] Optionally, the above-mentioned business member global table is constructed through the following steps: obtaining each business dimension table, wherein the above-mentioned business dimension tables include a business dimension table corresponding to the first level, a business dimension table corresponding to the second level, and a business dimension table corresponding to the third level, and the business dimension table corresponding to the third level corresponds to the level of the above-mentioned business data table, and each record of each business dimension table includes a business dimension identifier and a user identifier, and each user identifier included in each business dimension table corresponds to the same user type; generating a business member global table according to the level, user identifier and user type corresponding to the above-mentioned business data table and each of the above-mentioned business dimension tables.

[0153] Optionally, the above-mentioned business organization global table is constructed through the following steps: for each record in the above-mentioned business member global table, the following steps are performed: obtaining the organization path information corresponding to the user identifier in the above-mentioned record, wherein the above-mentioned organization path information includes each organization identifier; splitting the above-mentioned organization path information to obtain each split organization identifier; generating each business organization information based on the business identifier in the above-mentioned record and each split organization identifier, wherein each business organization information includes a business identifier and an organization identifier; deduplicating the generated each business organization information according to the business identifier and the organization identifier; and saving each business organization information after deduplication as the business organization global table.

[0154] Optionally, the above-mentioned business member global table is generated based on the level, user identifier and user type corresponding to the above-mentioned business data table and the above-mentioned each business dimension table, and can be further configured to: construct an empty table as the business member global table; for each record in the business dimension table of each first level corresponding to the target user type, based on the business member global table, perform the following steps: determine the groups of records associated with the above-mentioned record in the above-mentioned each business dimension table and the above-mentioned business data table as associated record groups; for each associated record in the above-mentioned associated record group, perform the following additional steps: in response to determining that the above-mentioned associated record belongs to the first level, determine whether the business member global table meets the first condition, wherein the above-mentioned first condition is that there exists a user identifier in the business member global table whose corresponding user type belongs to the second level or the third level and is the same as the user identifier included in the above-mentioned associated record; in response to determining that the above-mentioned first condition is met, modify the user type of the above-mentioned user identifier in the business member global table to the user type corresponding to the above-mentioned associated record; in response to determining that the above-mentioned first condition is not met, add the business identifier corresponding to the above-mentioned associated record group and the user type corresponding to the above-mentioned associated record to the business member global table.

[0155] Optionally, the above-mentioned new step may further include: in response to determining that the above-mentioned association record belongs to the second level, determining whether the business member global table meets the second condition, and determining whether the business member global table meets the third condition, wherein the above-mentioned second condition is that the business member global table has a corresponding user type belonging to the first level and a user identifier that is the same as the user identifier included in the above-mentioned association record, and the above-mentioned third condition is that the business member global table has a corresponding user type belonging to the third level and a user identifier that is the same as the user identifier included in the above-mentioned association record; in response to determining that the above-mentioned second condition is not met, adding the business identifier corresponding to the above-mentioned association record group and the user type corresponding to the above-mentioned association record to Business member global table; in response to determining that the above-mentioned third condition is satisfied, modifying the user type of the above-mentioned user identifier in the business member global table to the user type corresponding to the above-mentioned associated record; in response to determining that the above-mentioned third condition is not satisfied, adding the business identifier corresponding to the above-mentioned associated record group and the user type corresponding to the above-mentioned associated record to the business member global table; in response to determining that the above-mentioned associated record belongs to the third level, determining whether the business member global table satisfies the above-mentioned first condition or the above-mentioned second condition; in response to determining that the business member global table does not satisfy the above-mentioned first condition and the above-mentioned second condition, adding the business identifier corresponding to the above-mentioned associated record group and the user type corresponding to the above-mentioned associated record to the business member global table.

[0156] Optionally, the business information query device 500 may also include: an update unit and a first execution unit (not shown in the figure). The update unit is configured to, in response to monitoring the new information recorded in the business dimension table, update the above-mentioned business member global table according to the associated record group corresponding to the above-mentioned new information. The first execution unit is configured to, in response to monitoring the modification information recorded in the business dimension table, perform the following steps: in response to determining that the modification type representation record corresponding to the above-mentioned modification information is updated, according to the above-mentioned modification information, update the record corresponding to the above-mentioned modification information in the above-mentioned business member global table; in response to determining that the above-mentioned record belongs to the first level and the modification type representation record corresponding to the above-mentioned modification information is deleted, perform the following modification steps: determine whether the above-mentioned business member global table meets the fourth condition, wherein the above-mentioned fourth condition is that there is a corresponding user type in the business member global table that belongs to the second level and is the same as the user identifier corresponding to the above-mentioned modification information; in response to determining that it meets the fourth condition, the ... In response to determining that the fourth condition is not met, the user type of the user identifier in the business member global table is modified to a user type corresponding to the second level; in response to determining that the fourth condition is not met, determining whether the business member global table meets the fifth condition, wherein the fifth condition is that there exists in the business member global table a user identifier whose corresponding user type belongs to the third level and is the same as the user identifier corresponding to the modification information; in response to determining that the fifth condition is met, the user type of the user identifier in the business member global table is modified to a user type corresponding to the third level; in response to determining that the fifth condition is not met, deleting the record corresponding to the user identifier in the business member global table.

[0157] Optionally, the above-mentioned modification step also includes: in response to determining that the above-mentioned record belongs to the second level and the modification type representation record corresponding to the above-mentioned modification information is deleted, performing the following steps: determining whether the above-mentioned business member global table meets the above-mentioned fifth condition; in response to determining that the above-mentioned fifth condition is met, modifying the user type of the above-mentioned user identifier in the above-mentioned business member global table to a user type corresponding to the third level; in response to determining that the above-mentioned fifth condition is not met, deleting the record corresponding to the above-mentioned user identifier in the above-mentioned business member global table; in response to determining that the above-mentioned record belongs to the third level and the modification type representation record corresponding to the above-mentioned modification information is deleted, deleting the record corresponding to the above-mentioned user identifier in the above-mentioned business member global table.

[0158] Optionally, the business information query device 500 may also include: a second execution unit (not shown in the figure), which is configured to execute the following steps in response to detecting the modification information of the record in the business member global table: splitting the organization path information corresponding to the user identifier in the above record before the modification to obtain an organization identifier set; combining the business identifier corresponding to the above record with each business identifier in the above organization identifier set to obtain each combination information; for each combination information in the above combination information, executing the following steps: determining each record in the above business organization global table that has no corresponding relationship with the user identifier corresponding to the above record as a record set; determining whether there is a record in the above record set that covers the above combination information; in response to determining that it does not exist, deleting the record corresponding to the above combination information in the above business organization global table; and deduplicating the business organization global table based on the business identifier and the organization identifier.

[0159] It is understood that the units described in the device 500 are similar to those in the reference Figure 2 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the device 500 and the units included therein, and will not be repeated here.

[0160] Reference below Figure 6 , which shows an electronic device 600 (eg, Figure 1 A schematic diagram of the structure of the server in FIG. Figure 6 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0161] like Figure 6 As shown, the electronic device 600 may include a processing device 601 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. Various programs and data required for the operation of the electronic device 600 are also stored in the RAM 603. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0162] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 6 The electronic device 600 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead. Figure 6 Each block shown in the figure may represent one device, or may represent multiple devices as needed.

[0163] In particular, according to some embodiments of the present disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from a network via the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of some embodiments of the present disclosure are performed.

[0164] It should be noted that the computer-readable medium described in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or device. In some embodiments of the present disclosure, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0165] In some embodiments, the client and server can communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0166] The computer-readable medium may be included in the electronic device, or may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device: determines the user's business authority information; in response to determining that the business authority information and the user's business information query request meet a preset global condition, determines a global business user data table corresponding to the business information query request, wherein each record in the global business user data table includes a business identifier and a user identity identifier corresponding to the business information query request, the combination of the business identifier and the user identity identifier in the global business user data table is unique, and the global business user data table includes user identity identifiers corresponding to each level; extracts the user identity identifier to be queried from the business information query request; based on the user identity identifier to be queried, queries the business information corresponding to the user identity identifier to be queried from the global business user data table and the business data table, wherein the business data table includes various business data records, and each business data record includes a business identifier.

[0167] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0168] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0169] The units described in some embodiments of the present disclosure may be implemented in software or in hardware. The described units may also be provided in a processor. For example, they may be described as follows: a processor includes a first determination unit, a second determination unit, an extraction unit, and a query unit. The names of these units do not, in some cases, constitute limitations on the units themselves. For example, the first determination unit may also be described as a "unit for determining the user's service authority information."

[0170] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0171] Some embodiments of the present disclosure further provide a computer program product, including a computer program, which implements any of the above-mentioned business information query methods when executed by a processor.

[0172] The above description is only an illustration of some preferred embodiments of the present disclosure and the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure.

Claims

1. A business information query method, comprising: Determine the user's business authority information; In response to determining that the business authority information and the business information query request of the user meet a preset global condition, determining a global business user data table corresponding to the business information query request, wherein each record of the global business user data table includes a business identifier and a user identity identifier corresponding to the business information query request, a combination of the business identifier and the user identity identifier in the global business user data table is unique, and the global business user data table includes user identity identifiers corresponding to each level; Extracting the identity of the user to be queried from the business information query request; Based on the user identity to be queried, the service information corresponding to the user identity to be queried is queried from the global service user data table and the service data table, wherein the service data table includes various service data records, and each service data record includes a service identity.

2. The method according to claim 1, wherein: The business data record in the business data table also includes a person in charge identifier; and the method further includes: In response to determining that the business authority information and the business information query request do not meet the preset global condition, based on the user identity to be queried and each responsible person identifier in the business data table, the business information corresponding to the user identity to be queried is queried from the business data table.

3. The method according to claim 1, wherein: The determining of the global service user data table corresponding to the service information query request includes: In response to determining that the business information query request represents a query collaborative business, the business member global table is determined to be a global business user data table, wherein each record of the business member global table includes a business identifier, a user identifier and a user type, the user identity identifier in the global business user data table corresponds to the user identifier in the business member global table, and the combination of the business identifier and the user identifier in the business member global table is unique.

4. The method according to claim 1, wherein: The determining of the global service user data table corresponding to the service information query request includes: In response to determining that the business information query request represents a query for all businesses, the business organization global table is determined to be a global business user data table, wherein each record in the business organization global table includes a business identifier and an organization identifier, the user identity identifier in the global business user data table corresponds to the organization identifier in the business organization global table, and the combination of the business identifier and the organization identifier in the business organization global table is unique.

5. The method according to claim 1, wherein: The querying of the service information corresponding to the user identity identifier to be queried from the global service user data table and the service data table based on the user identity identifier to be queried includes: Selecting from the global service user data table each service identifier whose corresponding user identifier is the same as the user identifier to be queried; According to the respective service identifiers, querying the service data table for respective service data records whose corresponding service identifiers are the same as the service identifiers in the respective service identifiers; The business information corresponding to the user identity to be queried is generated according to each of the queried business data records and each of the records corresponding to the each of the business identifiers in the global business user data table.

6. The method according to claim 3, wherein: The business member global table is constructed by the following steps: Obtaining each business dimension table, wherein each business dimension table includes a business dimension table corresponding to the first level, a business dimension table corresponding to the second level, and a business dimension table corresponding to the third level, the business dimension table corresponding to the third level corresponds to the level of the business data table, each record of each business dimension table includes a business dimension identifier and a user identifier, and each user identifier included in each business dimension table corresponds to the same user type; A business member global table is generated according to the levels, user identifiers and user types corresponding to the business data table and each business dimension table.

7. The method according to claim 4, wherein: The business organization global table is constructed through the following steps: For each record in the business member global table, perform the following steps: Obtaining the organization path information corresponding to the user identifier in the record, wherein the organization path information includes each organization identifier; Splitting the organization path information to obtain each split organization identifier; Based on the business identifier in the record and the split individual organization identifiers, generate each business organization information, wherein each business organization information includes a business identifier and an organization identifier; De-duplication of each generated business organization information is performed based on the business identification and organization identification; The deduplicated information of each business organization is saved as a global business organization table.

8. The method according to claim 6, wherein: The generating of a business member global table according to the business data table and the levels, user identifiers and user types corresponding to each business dimension table includes: Construct an empty table as the global table for business members; For each record in each first-level business dimension table corresponding to the target user type, based on the business member global table, perform the following steps: Determine each group of records associated with the record in each business dimension table and the business data table as an associated record group; For each associated record in the associated record group, perform the following additional steps: In response to determining that the association record belongs to the first level, determining whether the business member global table satisfies a first condition, wherein the first condition is that there exists in the business member global table a user identifier of a corresponding user type belonging to the second level or the third level and being the same as the user identifier included in the association record; In response to determining that the first condition is satisfied, modifying the user type of the user identifier in the business member global table to a user type corresponding to the associated record; In response to determining that the first condition is not met, the service identifier corresponding to the association record group and the user type corresponding to the association record are added to the service member global table.

9. The method according to claim 8, wherein: The newly added steps also include: In response to determining that the association record belongs to the second level, determining whether the business member global table satisfies a second condition, and determining whether the business member global table satisfies a third condition, wherein the second condition is that the business member global table has a corresponding user type belonging to the first level and a user identifier that is the same as the user identifier included in the association record, and the third condition is that the business member global table has a corresponding user type belonging to the third level and a user identifier that is the same as the user identifier included in the association record; In response to determining that the second condition is not satisfied, adding the service identifier corresponding to the association record group and the user type corresponding to the association record to the service member global table; In response to determining that the third condition is satisfied, modifying the user type of the user identifier in the business member global table to a user type corresponding to the associated record; In response to determining that the third condition is not satisfied, adding the service identifier corresponding to the association record group and the user type corresponding to the association record to the service member global table; In response to determining that the associated record belongs to the third level, determining whether the business member global table satisfies the first condition or the second condition; In response to determining that the business member global table does not satisfy the first condition and the second condition, the business identifier corresponding to the association record group and the user type corresponding to the association record are added to the business member global table.

10. The method according to claim 6, wherein: The method further comprises: In response to monitoring the new information recorded in the business dimension table, updating the business member global table according to the associated record group corresponding to the new information; In response to monitoring the modification information recorded in the business dimension table, the following steps are performed: In response to determining that the modification type representation record corresponding to the modification information is updated, updating the record corresponding to the modification information in the business member global table according to the modification information; In response to determining that the record belongs to the first level, and the modification type corresponding to the modification information represents record deletion, the following modification steps are performed: Determine whether the business member global table satisfies a fourth condition, wherein the fourth condition is that there exists a user identifier in the business member global table whose corresponding user type belongs to the second level and is the same as the user identifier corresponding to the modification information; In response to determining that the fourth condition is satisfied, modifying the user type of the user identifier in the business member global table to a user type corresponding to the second level; In response to determining that the fourth condition is not satisfied, determining whether the business member global table satisfies a fifth condition, wherein the fifth condition is that there exists in the business member global table a user identifier whose corresponding user type belongs to the third level and is the same as the user identifier corresponding to the modification information; In response to determining that the fifth condition is satisfied, modifying the user type of the user identifier in the business member global table to a user type corresponding to the third level; In response to determining that the fifth condition is not satisfied, the record corresponding to the user identifier in the business member global table is deleted.

11. The method according to claim 10, wherein: The modification step further comprises: In response to determining that the record belongs to the second level, and the modification type corresponding to the modification information represents record deletion, performing the following steps: Determining whether the business member global table satisfies the fifth condition; In response to determining that the fifth condition is satisfied, modifying the user type of the user identifier in the business member global table to a user type corresponding to the third level; In response to determining that the fifth condition is not satisfied, deleting the record corresponding to the user identifier in the business member global table; In response to determining that the record belongs to the third level and the modification type corresponding to the modification information represents record deletion, the record corresponding to the user identifier in the business member global table is deleted.

12. The method according to claim 7, wherein: The method further comprises: In response to detecting the modification information recorded in the business member global table, the following steps are performed: Splitting the organization path information corresponding to the user identifier in the record before modification to obtain an organization identifier set; Combining the business identifier corresponding to the record with each business identifier in the organization identifier set to obtain each combination information; For each piece of combined information in the respective pieces of combined information, the following steps are performed: Determine each record in the business organization global table that has no corresponding relationship with the user identifier corresponding to the record as a record set; Determine whether there is a record in the record set that covers the combined information; In response to determining that the combination information does not exist, deleting the record corresponding to the combination information in the business organization global table; De-duplicate the business organization global table based on the business ID and organization ID.

13. A business information query device, comprising: A first determining unit is configured to determine service authority information of a user; A second determining unit is configured to, in response to determining that the business authority information and the business information query request of the user meet a preset global condition, determine a global business user data table corresponding to the business information query request, wherein each record of the global business user data table includes a business identifier and a user identity identifier corresponding to the business information query request, a combination of the business identifier and the user identity identifier in the global business user data table is unique, and the global business user data table includes user identity identifiers corresponding to each level; An extraction unit, configured to extract a user identity to be queried from the service information query request; The query unit is configured to query the business information corresponding to the user identity to be queried from the global business user data table and the business data table based on the user identity to be queried, wherein the business data table includes various business data records, and each business data record includes a business identifier.

14. An electronic device comprising: one or more processors; a storage device having one or more programs stored thereon, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 12.

15. A computer readable medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 12 is implemented.

16. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 12.

Images