WO2023236756A1 - Procédé d'attribution de base de données de données multilocataires, et produit-programme et dispositif électronique - Google Patents

Procédé d'attribution de base de données de données multilocataires, et produit-programme et dispositif électronique Download PDF

Info

Publication number
WO2023236756A1
WO2023236756A1 PCT/CN2023/095171 CN2023095171W WO2023236756A1 WO 2023236756 A1 WO2023236756 A1 WO 2023236756A1 CN 2023095171 W CN2023095171 W CN 2023095171W WO 2023236756 A1 WO2023236756 A1 WO 2023236756A1
Authority
WO
WIPO (PCT)
Prior art keywords
product
data
tenant
database
information
Prior art date
Application number
PCT/CN2023/095171
Other languages
English (en)
Chinese (zh)
Inventor
段凯歌
魏玉婷
莫元武
Original Assignee
易保网络技术(上海)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 易保网络技术(上海)有限公司 filed Critical 易保网络技术(上海)有限公司
Publication of WO2023236756A1 publication Critical patent/WO2023236756A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/211—Schema design and management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2365—Ensuring data consistency and integrity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/278—Data partitioning, e.g. horizontal or vertical partitioning
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database

Definitions

  • the present application relates to the field of computer technology, and in particular to a multi-tenant data sharding method, program products and electronic equipment.
  • SaaS service means that the SaaS provider builds all the network infrastructure, software, and hardware operation platforms required for the company's informatization, and is responsible for a series of services such as all early implementation and later maintenance.
  • the company does not need to purchase software and hardware, build a computer room, Recruiting IT personnel allows you to use information systems through the Internet.
  • multiple tenant projects are deployed on the SaaS service provider's server, and each tenant project has a corresponding database. For example, the urban medical insurance tenant has a corresponding urban medical insurance tenant database, accident insurance Tenants have corresponding accident insurance tenant databases, etc.
  • connection resources of the database in the server are relatively precious.
  • the existing tenant sharding method cannot change with changes in the business. Users of the same tenant in different regions operate the same tenant database. The data in the database can easily cause performance problems such as increased database load and insufficient number of connections. Simply accessing the corresponding tenant database based on tenant information cannot efficiently handle insurance business. For example, for the urban medical insurance project, if only based on the original tenant sharding method, a large number of users from different regions simultaneously request the server to obtain data in the same tenant database, which will easily cause the database load corresponding to the urban medical insurance to increase and the number of connections to be increased. Insufficient and other performance issues prevent the insurance business from being processed efficiently.
  • this application relates to a multi-tenant data sharding method, program product, and electronic device.
  • embodiments of the present application provide a multi-tenant data sharding method for a system including a server and a storage device serving as a database, wherein the server is configured with an interception matching module, and the interception matching module includes a data interception module.
  • the above methods include:
  • the data interception module obtains the request to execute the insurance business
  • the regional rule matching module Based on the product information and geographical area information in the request passed by the data interception module, the regional rule matching module matches the request with the regional database information of the product management database in the database, where the product corresponds to multiple products in the database.
  • Product area database which includes product configuration rules corresponding to insurance business implementers;
  • the regional rule matching module obtains the product configuration rules in the product regional library, and obtains the data required to execute the insurance business according to the product configuration rules;
  • the organizational structure interception module obtains the tenant information in the request; and the tenant rule matching module obtains the tenant information required to execute the insurance business from the tenant library in the database based on the tenant information passed by the organizational structure interception module.
  • the data is not matched.
  • the embodiment of the present application provides a multi-tenant data sharding method for a system including a server and a storage device as a database.
  • the data interception module obtains a request to execute insurance business; the regional rule matching module is based on the request passed by the data interception module.
  • the product information and geographical area information in the database are matched with the regional library information of the product management library in the database; in the case of matching the regional library information, the regional rule matching module obtains product configuration rules from the product regional library in the database.
  • Tenant information obtains the data required to perform insurance business from the tenant library in the database.
  • This method combines geographical area information with the sub-database method. According to the characteristics that the same insurance product can correspond to different regional databases, different regions corresponding to the same product are divided into different databases.
  • the product can access different product regional libraries, which improves the single database sub-rule based on tenant information, which can effectively avoid the problem of insurance business processing failure caused by accessing the same database only based on a single tenant sub-database rule, thereby improving the efficiency of the insurance business. processing efficiency.
  • the product management library in the database may be a lightweight directory access protocol, where the lightweight directory access protocol includes product information and geographical area information corresponding to the product area library in the database. And the name, code name or path address of each product regional library.
  • the lightweight directory access protocol can be used as a special database that organizes information according to a tree structure and is specially optimized for browsing and searching directories and reading content.
  • the product management library adopts a lightweight directory access protocol.
  • the regional rule matching module can more quickly match the request with the regional library information of the product management library in the database based on the product information and geographical area information in the request passed by the data interception module. match.
  • matching the request with the regional library information of the product management library in the database includes,
  • the regional rule matching module obtains product configuration rules from the product regional library in the database, and obtains data required to execute the insurance business according to the product configuration rules, including,
  • the regional rule matching module obtains product configuration rules from the specific regional database corresponding to the product regional database in the database through the regional database connection string, and obtains the data required to execute the insurance business based on the product configuration rules.
  • the regional rule matching module can quickly and efficiently obtain product configuration rules from the product regional library in the database through the regional library connection string, and obtain the data required to execute the insurance business based on the product configuration rules.
  • the product area library includes product configuration rules corresponding to the insurance business implementer as,
  • the product area library includes product configuration rules specified by one insurance business implementer or multiple product configuration rules specified by multiple insurance business implementers.
  • the product area library includes product configuration rules specified by one insurance business implementer or multiple product configuration rules specified by multiple insurance business implementers. Multiple configuration rules are provided for the same insurance product in the same area, so that Regional sub-library rules are more reasonable.
  • the product information includes a product name or product code.
  • the product name or product code is a direct and effective element for expressing the product.
  • the product information includes the product name or product code, which helps to match the regional database information in the product management database according to the product information and regional information.
  • the geographical area information includes the administrative area to which the product is divided or the custom area to which the product is divided based on customization.
  • the geographical area information includes the administrative area to which the product is divided or the custom area to which the product is divided according to customization, which is conducive to obtaining the product area database in combination with product information, and efficiently accessing it according to the area information in the product management database Corresponding specific regional database.
  • the regional library information includes product regional library name, code number or path address.
  • the regional library information including the specific product regional library name, code or path address, provides multiple representation methods for obtaining the product regional library in the product management library.
  • the data required to perform insurance business includes,
  • the data required for executing the insurance business includes at least one of the basic element content data on the policy, executing the policy generation, executing the query of the insurance business status, or executing the logical data for reviewing the insurance document. After obtaining the aforementioned data Finally, insurance business can be effectively processed based on the obtained data.
  • the database includes,
  • Product management library product area library and tenant library.
  • the database includes a product management library, a product area library and a tenant library, which provide conditions for implementing regional sub-database rules and tenant sub-database rules.
  • embodiments of the present application provide a multi-tenant data sharding device, including:
  • Data receiving module used to receive data
  • Data forwarding module used to forward data
  • the interception matching module is used to intercept data and match the intercepted data with regional sharding rules or tenant sharding rules;
  • Execution business logic module used to execute business logic
  • the interception matching module includes,
  • a data interception module used to obtain the first data, where the first data includes product information and geographical area information;
  • the regional rule matching module is used to match regional sub-library rules based on product information and geographical area information;
  • the organizational structure interception module is used to obtain the second data, where the second data includes tenant information;
  • the tenant rule matching module is used to match tenant sharding rules based on tenant information.
  • the above-mentioned first data is the request data transmitted by the data forwarding module; the above-mentioned second data is the request data transmitted by the regional rule matching module.
  • the multi-tenant data sharding device includes a data receiving module, a data forwarding module, an interception matching module, and an execution business logic module.
  • the insurance business can be processed through the aforementioned modules, wherein,
  • the regional rule matching module includes multiple sub-modules that implement dynamic sharding rules based on the geographical area information in the request. Each sub-module can effectively implement a multi-tenant data sharding method.
  • embodiments of the present application provide a computer-readable storage medium. Instructions are stored on the computer-readable storage medium. When the instructions are executed on an electronic device, the electronic device causes the electronic device to execute the above first aspect and the first aspect. Any multi-tenant data sharding method among various possible implementations.
  • inventions of the present application provide a chip device.
  • the chip device includes:
  • a processor configured to execute a computer executable program, so that the electronic device installed with the chip device executes any one of the multi-tenant data sharding methods of the above-mentioned first aspect and various possible implementations of the first aspect.
  • embodiments of the present application provide a computer program product, which is characterized in that the computer program product includes instructions, and when the instructions are executed, the above-mentioned first aspect and various possible implementations of the first aspect are implemented. Any multi-tenant data sharding method.
  • embodiments of the present application provide an electronic device, which is characterized by including:
  • memory for storing instructions for execution by one or more processors of the electronic device
  • a processor when the instructions are executed by one or more processors of the electronic device, the processor is configured to execute the instructions stored in the memory to implement the above first aspect and various possibilities of the first aspect. Implement any multi-tenant data sharding method.
  • the embodiment of the present application provides a multi-tenant data sharding method for a system including a server and a storage device as a database.
  • the data interception module obtains a request to execute insurance business; the regional rule matching module is based on the request passed by the data interception module.
  • the product information and geographical area information in the database are matched with the regional library information of the product management library in the database; in the case of matching the regional library information, the regional rule matching module obtains product configuration rules from the product regional library in the database.
  • Tenant information obtains the data required to perform insurance business from the tenant library in the database.
  • This method combines geographical area information with the sub-database method. According to the characteristics that the same insurance product can correspond to different regional databases, different regions corresponding to the same product are divided into different databases.
  • a multi-tenant data sub-database device has a data receiving module, a data forwarding module, an interception matching module, and an execution business logic module, which can effectively complete the process of processing insurance business.
  • the regional rule matching module includes a data interception module, a regional rule matching module, an organizational structure interception module, and a tenant rule matching module. Multiple sub-modules implement dynamic sub-database rules based on the product information, geographical area information, or tenant information in the request.
  • Figure 1A shows a schematic diagram of an insurance business scenario according to some embodiments of the present application
  • Figure 1B shows an unfinished policy interface schematic diagram according to some embodiments of the present application
  • Figure 1C shows a schematic diagram of a completed policy interface according to some embodiments of the present application.
  • FIG. 2A shows a schematic structural diagram of a server 200b according to some embodiments of the present application
  • Figure 2B shows a schematic structural diagram of an interception matching module 203 according to some embodiments of the present application
  • Figure 2C shows a schematic structural diagram of a database 300 according to some embodiments of the present application.
  • Figure 3 shows a schematic diagram of the interaction process between the interception matching module 203 and each sub-database in the database 300 according to some embodiments of the present application;
  • Figure 4 shows a flow chart of a multi-tenant data sharding method according to some embodiments of the present application
  • Figure 5 shows a schematic diagram of the hardware structure of a server 200b according to some embodiments of the present application.
  • Illustrative embodiments of the present application include, but are not limited to, a multi-tenant data sharding method, program products, and electronic devices.
  • Figure 1A shows an insurance business scenario to which the technical solution of the present application is applicable, according to some embodiments of the present application.
  • it includes the policy holder, the user terminal 100 used by the policy holder, the server 200a corresponding to the insurance company, the server 200b corresponding to the SaaS service, and the database 300 deployed on the server 200b.
  • the insurance company purchase services from SaaS providers. Therefore, the insurance company only needs to deploy the facilities required for processing insurance business on the server, and then it can process the insurance business by accessing the server 200b.
  • the user terminal 100 can be connected to the server 200a through the network, and the server 200a can be connected to the server 200b through the network to handle insurance services.
  • the user terminal 100 can communicate with the server 200a through a wireless fidelity (Wireless-Fidelity, Wi-Fi) network, Bluetooth, and other wireless networks
  • the server 200a can communicate through a wireless fidelity (Wireless-Fidelity, Wi-Fi) network, Bluetooth, and other wireless networks. Wait for the wireless network to communicate with the server 200b.
  • the user terminal 100 can be installed with the insurance company's client software, such as an insurance application (Application, APP).
  • the policyholder can access the server 200a through the insurance APP installed on the user terminal 100 to purchase the insurance products he or she needs, such as purchasing Urban medical insurance, pension insurance, vehicle insurance, accident insurance, etc.; policyholders can also use the instant messaging APP in the user terminal 100 to scan the QR code corresponding to each insurance to purchase insurance. Handle insurance business.
  • the server 200a encrypts the data according to the request data sent by the user terminal 100, and then sends the encrypted request data to the server 200b.
  • the server 200b After receiving the insurance service request, the server 200b identifies the insurance product based on the insurance product tenant information in the request.
  • the specific tenant to which it belongs obtains the stored data in the database 300 corresponding to the tenant in the server 200b according to the tenant sub-database rules, executes the insurance business content, and sends the processed insurance business results to the server 200a, and the server 200a then sends the processed insurance business results to the server 200a.
  • the insurance business result data is decrypted and the final result is sent to the user terminal 100, thereby completing the insurance business processing process.
  • the server 200b is deployed with data according to the insurance company's own business needs.
  • the insurance company places the insurance business that needs to be processed using software services on the server 200b for processing according to the business, which reduces the maintenance cost and improves the availability of resources.
  • FIG. 1B shows the page 101 of the user terminal 100 when the user applies for insurance.
  • a policy needs to be generated.
  • the user terminal 100 sends a request to generate a city medical insurance policy to the server 200a; after receiving the request sent by the policy holder through the user terminal 100, the server 200a encrypts the request data, and then sends the encrypted request data to the server 200b; the server 200b After receiving the encrypted request to generate a city medical insurance policy, 200b identifies the tenant to which the city medical insurance product belongs (hereinafter referred to as the "medical insurance tenant").
  • the medical insurance tenant can be an insurance company.
  • the server 200a decrypts the processed insurance business result data according to the corresponding decryption method, and sends the final result to the user terminal 100.
  • the business request for generating a city medical insurance policy is only one of the insurance services set by the insurance company in the server 200b to be processed by the server 200b, and the above is only an example.
  • the insurance business processed by the server 200b can also generate blank policy business according to the insurance request, query the status of the insurance business, review insurance documents, and so on.
  • the server 200a needs to divide the insurance according to the multi-tenant classification. Database rules accessing the same database can easily cause performance problems such as increased database load and insufficient number of connections. This can easily cause policyholders to fail to apply for insurance, which not only wastes connection resources but also affects the processing of insurance business.
  • the user terminal 100 sends a request to generate a city medical insurance policy to the server 200a. After receiving the request sent by the user terminal 100, the server 200a encrypts data related to privacy security and sends the encrypted request data to the server 200b.
  • the server 200b 200b based on the obtained data request and the tenant sub-database rules, determined that the city's medical insurance belongs to the medical insurance tenant. Due to the large number of connections to the medical insurance tenant database, the connection to the medical insurance tenant database failed, and insurance documents could not be generated, which wasted connection resources. , affecting the process of handling urban medical insurance business.
  • the corresponding policy data content will be different due to the different geographical areas where the policy holder wants to insure.
  • the urban medical reimbursement scope and reimbursement ratio, deductible setting, insurance requirements, geographical use requirements and other protection contents are different.
  • the insurance content of urban medical insurance in city A is different from that of urban medical insurance in city B.
  • the coverage content of medical insurance is different. Therefore, insured products and geographical areas can be associated, and the database can be divided according to the correlation between insured products and geographical areas.
  • this application proposes a multi-tenant data sharding method.
  • the server 200b matches the insurance product information and geographical area information in the request with the regional sharding rules. If the match is successful, the server 200b obtains the data based on the regional sharding rules.
  • the product configuration rules corresponding to the insurance company and the relevant data required to execute the insurance business corresponding to the product configuration rules execute the insurance business logic; if the match with the regional sub-database rules fails, the tenant information in the request is matched with the tenant sub-database rules. , after the matching is successful, the insurance business logic is executed based on the relevant data for executing the insurance business obtained by the tenant sub-database rules.
  • insurance products correspond to multiple product regional libraries
  • the product regional libraries include product configuration rules corresponding to insurance business implementers.
  • geographical areas can be understood as different administrative areas, such as areas divided by provinces, cities, districts, and counties, or they can also be customized geographical areas based on the level of economic development and the number of permanent residents.
  • the user fills out the policy interface shown in Figure 1B.
  • the server 200b receives the request to generate urban medical insurance policy data, it obtains the product name and insurable data in the request. city, and match the product name "xx city medical insurance” and the insurable city “Anyang" with the regional sub-database rules. If the match is successful, the urban medical insurance product configuration rules corresponding to the insurance company are obtained in the corresponding regional database in Anyang (hereinafter referred to as the "Anyang database”), as well as the relevant information required to execute the insurance business corresponding to the urban medical insurance product configuration rules.
  • Anyang database anyang
  • the server 200b executes the business logic of generating medical insurance, it sends the data to the server 200a.
  • the server 200a decrypts the data and then sends it to the user terminal 100.
  • the user terminal 100 displays the insurance document interface 102 as shown in Figure 1C. At this time The insurance document interface cannot be modified.
  • the server 200b receives the information of multiple user terminals 100 in Anyang, Yulin and other places obtained by the server 200a, In the insurance request, the server 200b can obtain the urban medical insurance product configuration rules corresponding to the insurance company in the Anyang database according to the regional sub-database rules, and the relevant data required to execute the insurance business corresponding to the urban medical insurance product configuration rules.
  • the data is executed to generate the urban medical insurance policy business logic; then the urban medical insurance product configuration rules corresponding to the insurance company in the regional database corresponding to Yulin (hereinafter referred to as the "Yulin database") are obtained according to the regional sub-database rules, as well as the urban medical insurance product configuration rules corresponding to the urban medical insurance
  • the product configuration rules correspond to the relevant data required to execute the insurance business, and a city medical insurance policy is generated based on the obtained data.
  • the user terminal 100 in the application scenario shown in FIG. 1A can be any electronic device that can install an insurance company's application program and has a display screen.
  • Server 200a and server 200b may be separate
  • a server can also be a server cluster composed of multiple servers.
  • the device structure corresponding to the server 200b is first introduced.
  • the server 200b includes a data receiving module 201, a data forwarding module 202, an interception matching module 203, and an execution business logic module 204.
  • the data receiving module 201 may be used to receive request data.
  • the data receiving module 201 can receive the request data related to the insurance business sent by the server 200a, and send the request data to the data forwarding module 202.
  • the data receiving module 201 receives a message sent by the server 200a.
  • the message includes at least one field of product information related to the insurance business, regional information, or tenant information to which the insurance product belongs.
  • the data forwarding module 202 may be used to forward request data.
  • the data forwarding module 202 can obtain the request data related to the insurance business sent by the data receiving module 201, filter out the irrelevant data in the request data, and send the filtered request data to the interception matching module. 203.
  • the interception matching module 203 can be used to intercept data, and match the intercepted data with regional sharding rules or tenant sharding rules.
  • the interception matching module 203 can receive the data sent by the data forwarding module 202, and perform regional sub-library rule matching based on the product information and geographical area information in the request data. If the matching is successful, the obtained data will be matched. The result data is sent to the execution business logic module 204; if the matching fails, the tenant information in the request is obtained, the tenant sharding rules are matched according to the tenant information, and the result data obtained by matching is sent to the execution business logic module 204.
  • the corresponding sharding strategy is matched based on the geographical area information or tenant information in the obtained request, which improves the original single tenant sharding method, so that under high concurrency conditions, for the same insurance product, due to Adopt a regional sub-database strategy to access different sub-databases to avoid the problem of failure to obtain data when accessing the same policy database, thereby improving the efficiency of processing insurance business.
  • the interception matching module 203 may be a chained multi-interceptor.
  • the business logic execution module 204 is used to execute business logic.
  • the business execution logic module 204 can receive the insurance business data successfully matched by the interception matching module 203 and execute the insurance business. For example, execute the business of generating insurance documents, reviewing insurance documents, querying the status of insurance business, etc.
  • the specific functional modules that the interception matching module 203 may include and each sub-database included in the database 300 in some embodiments of the present application will be introduced first.
  • the interception matching module 203 may include a data interception module 203a, a regional rule matching module 203b, an organizational structure interception module 203c, and a tenant rule matching module 203d.
  • the data interception module 203a obtains the request data forwarded by the data forwarding module 202, and sends the request data to the regional rule matching module 203b. It can be understood that in some implementations, the data interception module 203a may be a data interceptor.
  • the regional rule matching module 203b can receive the request data sent by the data interception module 203a, and first searches the product management library in the database 300 according to the product information and regional information in the request data. If the product corresponding to the product is found in the product management library, For specific regional library information, search the product regional library in the database 300 based on the regional library information to obtain the product configuration rules corresponding to the product regional library and the insurance business implementer and the data corresponding to the product configuration rules. If the match is successful, If the specific area corresponding to the product is not found in the product management library, then the match fail.
  • the organizational structure interception module 203c obtains the request data sent by the area rule matching module 203b, obtains the tenant information according to the request data, and sends the tenant information to the tenant rule matching module 203d.
  • the tenant information may be information about insurance products or insurance companies corresponding to the insurance products. It can be understood that in some implementations, the organizational structure interception module 203c can be an organizational structure interceptor.
  • the tenant rule matching module 203d receives the data sent by the organizational structure interception module 203c, matches the tenant information in the acquired data in the tenant library in the database 300, and obtains the execution business logic data or policy data of the insurance business corresponding to the tenant. , sending the searched data to the execution business logic module 204.
  • the database 300 includes a product management database 301 , a product area database 302 and a tenant database 303 .
  • each sub-database in the database 300 can be a relational database or a lightweight directory access protocol (Lightweight Directory Access Protocol, LDAP).
  • LDAP Lightweight Directory Access Protocol
  • LDAP can be used as a special database that organizes information according to a tree structure. It is specially optimized for browsing and searching directories and reading content. It is a hierarchical database with very good data reading capabilities. Reading data from a relational database is an order of magnitude faster.
  • the LDAP directory stores record items in the form of a series of "attribute pairs". Each record item includes an attribute type and an attribute value.
  • the product management database 301 may be an LDAP database
  • the regional database information stored in the product management database 301 may be insurance product information, regional information, and the name, code, or path address of the product regional database corresponding to the product regional database 302.
  • the attributes of the record items in the product management library 301 can be customized with product name attributes, region attributes, specific product regional library names, codes, or path address attributes corresponding to specific regional libraries, and corresponding attribute values are obtained according to the attributes.
  • the product management database 301 includes information about each product and multiple regional libraries corresponding to each product, such as product regional library names, codes, or path addresses.
  • product regional libraries corresponding to each product
  • the product is K insurance product
  • the product is sold in cities A, B, and C.
  • the B city library name corresponding to the K insurance product
  • Code name or regional library path address, C city library name, code name or product regional library path address corresponding to the K insurance product, etc.
  • Each of the multiple products will have multiple corresponding regional libraries.
  • the product matching database 301 may include the database names, codes or path addresses corresponding to the urban medical insurance products in Yulin, Anyang and other places.
  • the product area database 302 includes multiple area databases corresponding to products, and each sub-database in the product area database corresponds to the name or path address of the product area database obtained from the product management database.
  • each sub-database includes the A city library corresponding to K insurance product or the path address corresponding to A city library, the B city library corresponding to K insurance product or the path address corresponding to B city library, the K insurance product corresponding C city library or the path address corresponding to the C city library, etc.
  • there are multiple corresponding product regional libraries including Weihai library, Yulin library, Anyang library and other regional libraries.
  • Each product area library includes product configuration rules corresponding to insurance business implementers.
  • One product area library may include product configuration rules corresponding to multiple different insurance companies. Specifically, multiple product configuration rules specified by an insurance company or A product configuration rule stipulated by one insurance company or a product configuration rule stipulated by multiple insurance companies, etc. There are no restrictions on specific circumstances.
  • the Yulin library includes urban medical insurance product configuration rules set by multiple insurance companies.
  • the tenant library 303 includes multiple tenant libraries, such as A tenant library, B tenant library, C tenant library, etc. Each tenant library can store the data required for the same product of the same insurance company, or can store multiple products of the same insurance company. data required for the product.
  • tenant database 303 may include a city health insurance tenant database.
  • the structural diagram shown in the above server 200b is only a schematic.
  • corresponding modules can be added or deleted on this basis, and the specific structure is not required here.
  • it may also include a user management module, a user configuration module, a policy management module, etc.
  • Each sub-database of the database included in the above-mentioned database 300 is only an example. In other embodiments, corresponding sub-databases can also be added or reduced on this basis, and the specific structure is not required here.
  • the data interception module 203a intercepts the request to generate a policy.
  • the requests to generate insurance policies intercepted by the data interception module 203a include information that can characterize insurance products, policyholders' information, insurable geographical area information, product sales channels, etc., which will not be described in detail here.
  • product information can include product code or name
  • geographical area information that can be insured can be different administrative regions, such as areas divided by provinces, cities, districts, and counties, or it can also be based on economic development level, resident status, etc. Geographic areas divided into customizable populations. Among them, product information and insurable cities can be identified by numbers, letters, etc. after being encrypted by the server 200a. The specific identification method is not specified.
  • the data interception module 203a intercepts a request to generate a city medical insurance policy.
  • the request includes information that can characterize the city's medical insurance product, policyholder information, and insurable city information.
  • the data interception module 203a sends a policy generation request to the regional rule matching module 203b.
  • the data interception module 203a sends a request to generate a city medical insurance policy to the regional rule matching module 203b.
  • the regional rule matching module 203b obtains product information and geographical area information according to the request data.
  • the regional rule matching module 203b obtains the code of the city medical insurance product as 01 and the identifier of the insurable city Anyang as AY based on the obtained request to generate a city medical insurance policy.
  • the regional rule matching module 203b sends a request to obtain the specific regional database information corresponding to the product to the product management database 301.
  • the regional rule matching module 203b may be configured to match regional rules through a specific domain language, that is, a consensus language.
  • rule ⁇ rule name 'regional sub-library rule'
  • the regional rule matching module 203b sends a request to obtain the specific regional database information corresponding to the product to the product management database 301 based on the obtained product information and geographical area information.
  • the request may include obtaining the name, code or path of the product regional database corresponding to the insurance product. Address and other information.
  • the regional rule matching module 203b sends the city medical insurance product code 01 to the product management library 301, the insurable city Anyang is identified as AY, and the product area corresponding to the product in the product management library 301 Library name, code or path address.
  • the product management database 301 searches in the database based on the product information and geographical area information obtained in the request, and checks whether there is regional database information corresponding to the product and geographical area information in the database. If yes, proceed to step 314 to obtain the specific regional database information corresponding to the product; if not, proceed to step 306 to return a regional branch database rule matching failure message.
  • the product management database 301 checks whether there is a regional database corresponding to the insurance product code 01 and the insurable city Anyang AY in the database based on the city medical insurance product code 01 and the insurable city Anyang AY obtained in the request. If yes, proceed to step 314 to obtain the specific regional library name, code or path address corresponding to the product; if not, proceed to step 306 to return a regional sub-library matching failure message.
  • S306 The product management library 301 sends a message that there is no matching regional library information to the regional rule matching module 203b.
  • a message that there is no matching regional library information is sent to the regional rule matching module 203b.
  • the product management database 301 does not match the regional database name, code or path address corresponding to the product code 01 and the insurable city Anyang City AY in the database, and sends a message that there is no matching regional database information to the regional rule matching module 203b. .
  • the regional rule matching module 203b sends a request to generate a policy to the organizational structure interception module 203c.
  • the regional rule matching module 203b receives the message sent by the product management library 301 that there is no matching regional library information, determines that the matching of regional sub-library rules fails, and then sends a request to generate a policy to the organizational structure interception module 203c.
  • the regional rule matching module 203b receives the message sent by the product management library 301 that there is no matching regional library information, determines that the matching of regional sub-database rules fails, and sends a request to generate a city medical insurance policy to the organizational structure interception module 203c.
  • the organizational structure interception module 203c sends a request to generate a policy to the tenant rule matching module 203d, where the request includes tenant information.
  • the organizational structure interception module 203c obtains the request to generate a policy sent by the regional rule matching module 203b, it obtains the tenant information in the request data and sends the tenant information to the tenant rule matching module 203d.
  • the tenant information can include the tenant name or code, etc.
  • the representation method can be numbers, letters, or other characters, etc., and there is no specific limit here.
  • the tenant's name and code may be the name or code of the insurance company corresponding to the insurance product, etc.
  • the organizational structure interception module 203c obtains the request to generate a city medical insurance policy sent by the regional rule matching module 203b, it obtains the city's medical insurance tenant information based on the request data, and sends the medical insurance tenant information to the tenant rule matching module 203d.
  • the tenant name corresponding to the urban medical insurance product tenant database can be HMB tenant.
  • the tenant rule matching module 203d obtains a request to generate a policy.
  • tenant rule matching module 203d obtains the request to generate a policy sent by the organizational structure interception module 203c.
  • the tenant rule matching module 203d obtains the generated city medical insurance sent by the organizational structure interception module 203c. Policy Request.
  • the tenant rule matching module 203d sends a request to the tenant library 303 to obtain the data required to generate the policy in the corresponding tenant library.
  • the tenant rule matching module 203d may specify matching with tenant sub-library rules through a specific domain language, that is, a consensus language.
  • rule ⁇ rule name 'tenant sub-database rule'
  • the tenant rule matching module 203d sends a request to the tenant library 303 to obtain the data required to generate the policy in the corresponding tenant library according to the tenant information in the request.
  • the tenant rule matching module 203d sends a request to the tenant library 303 to obtain the data required to generate a city medical insurance policy in the HMB tenant library according to the city medical insurance tenant information in the request.
  • S311 The tenant database 303 obtains the data required to generate the policy.
  • the tenant database 303 searches the corresponding tenant database for data required to generate a policy based on the acquired tenant information. It can be understood that the data required to generate the policy may include the basic elements of the policy and the logical data to generate the policy.
  • the tenant database 303 searches the HMB tenant database for data required to generate a city medical insurance policy based on the tenant information.
  • the tenant database 303 sends the data required to generate a policy to the tenant rule matching module 203d.
  • the tenant library 303 after the tenant library 303 searches the corresponding tenant library for the data required to generate the policy, it sends the obtained data to the tenant rule matching module 203d.
  • the tenant database 303 searches the HMB tenant database for data required to generate a city medical insurance policy, it sends the acquired data to the tenant rule matching module 203d.
  • the tenant rule matching module 203d determines that the tenant sub-database rule is successfully matched.
  • the tenant rule matching module 203d determines that the tenant sub-database rule is successfully matched.
  • the product management database 301 obtains specific regional database information corresponding to the product.
  • the product management library 301 searches the database for corresponding regional library information based on product information and geographical area information.
  • the corresponding regional library information may include the name, code or path address of the product regional library corresponding to the insurance product and geographical area information.
  • the specific representation method may be numbers, letters, etc., which are not specifically limited here.
  • the product management database 301 searches for the city medical product code 01 in the database, the insurable city Anyang city identifier is AY, and the corresponding product area database name in the product management database 301 is Anyang database.
  • the product management library 301 sends the specific regional library information corresponding to the product to the regional rule matching module 203b.
  • the product management database 301 sends the urban medical insurance product corresponding to the regional database where policy data can be obtained and generated to the regional rule matching module 203b.
  • the regional database is the Anyang database.
  • the regional rule matching module 203b sends a request to the product regional database 302 to obtain the product configuration rules in the corresponding product regional database, and obtain the data required to generate the policy according to the product configuration rules.
  • the regional rule matching module 203b sends it to the product regional library 302 to obtain the product configuration rules in the corresponding product regional library, and obtains the requirements for executing the policy generation according to the product configuration rules.
  • one product area library may include product configuration rules corresponding to multiple different insurance companies; specifically, multiple product configuration rules stipulated by one insurance company or one product configuration rule stipulated by one insurance company or multiple product configuration rules stipulated by multiple insurance companies.
  • the regional rule matching module 203b obtains the product regional library corresponding to the urban medical insurance product as the Anyang library, it sends it to the product regional library 302 through the regional library connection string.
  • the urban medical insurance product configuration rules are obtained and based on The product configuration rule obtains a request to perform the data required to generate a city health insurance policy.
  • the product area database 302 obtains product configuration rules, and obtains data required to generate a policy according to the product configuration rules.
  • the product area library 302 searches in the corresponding area library according to the request, obtains product configuration rules, and obtains data required to generate a policy according to the product configuration rules.
  • the product area database 302 searches the Anyang database according to the area database connection string in the request, obtains the urban medical insurance product configuration rules, and obtains the data required to generate the urban medical insurance policy according to the product configuration rules.
  • the product area database 302 sends the obtained product configuration rules to the area rule matching module 203b, as well as the data corresponding to the product configuration rules required to execute the policy generation.
  • the product regional database 302 after acquiring the product configuration rules and generating the data required for the insurance policy according to the execution corresponding to the product configuration rules, the product regional database 302 sends the acquired product configuration rules and the corresponding product configuration rules to the regional rule matching module 203b. The corresponding execution generates the data required for the policy.
  • the product regional database 302 sends the acquired urban medical insurance product configuration rules to the regional rule matching module 203b, and Data required to generate urban medical insurance policies corresponding to product configuration rules.
  • the regional rule matching module 203b determines that the regional sub-library rules are successfully matched.
  • the regional rule matching module 203b determines that the regional sub-database rules are successfully matched.
  • the regional rule matching module 203b determines that the regional sub-database rules are successfully matched.
  • Figure 4 shows a flow chart of using the server 200b as the execution subject to execute the multi-tenant data sharding method in the embodiment of the present application.
  • the specific process includes the following steps:
  • the user terminal 100 sends a request to perform relevant insurance services to the server 200a; after receiving the request sent by the user terminal 100, the server 200a encrypts the request data and converts the encrypted request Sent to the server 200b; the server 200b obtains the request to execute the relevant insurance business.
  • executing relevant insurance business may include generating insurance policies, calculating premiums, querying the current insurance business status, reviewing insurance documents, surrendering insurance, and online claims settlement, etc.
  • the user terminal 100 sends a request to generate a city medical insurance policy to the server 200a; after receiving the request sent by the user through the user terminal 100, the server 200a encrypts the request data and sends the encrypted request to the server 200b; the server 200b Gets a request to execute a city health insurance policy.
  • the data receiving module 201 obtains a request for executing relevant insurance services sent by the server 200a.
  • the data forwarding module 202 filters the data in the request.
  • step S402 Based on the product information and geographical area information in the request data, determine whether it successfully matches the regional sub-library rules. If the judgment result is yes, go to step S404; if the judgment result is no, go to step S403.
  • the server 200b obtains the request to execute the relevant insurance business, it obtains the product information and geographical area information data in the request data, and matches the insurance product information and specific geographical area information in the database 300 to determine whether it contains the The product area library corresponding to the specific location area. If there is a corresponding product area library, the product configuration rules are searched in the corresponding product area library, and the data required to execute the policy generation is obtained according to the product configuration rules, and the regional classification is determined. If the library rule is successfully matched, step S404 is entered; if there is no regional library corresponding to the specific location area, it is determined that the match with the regional sub-library rule fails, and step S403 is entered.
  • the server 200b obtains and executes a request to generate a city medical insurance policy, it obtains the city medical insurance product information and insurable city information data in the request data, and searches in the database 300 based on the insurance product information and insurable cities to see whether there is a The product and the regional library corresponding to the insurable city. If the corresponding regional library exists, the urban medical insurance product configuration rules are searched in the corresponding regional library, and the data required to execute and generate the policy are obtained according to the urban medical insurance product configuration rules. , it is determined that the matching with the regional sub-library rules is successful; if there is no regional database corresponding to the product and insurable city, it is determined that the matching with the regional sub-library rules fails.
  • the data forwarding module 202 filters the obtained request data and sends it to the interception matching module 203, and the regional rules in the interception matching module 203 match.
  • Module 203b determines whether the match with the regional sub-database rules is successful based on the product information and geographical area information in the request data. If the judgment result is yes, go to step S404; if the judgment result is no, go to step S403.
  • the server 200b determines that the match with the regional sharding rules fails based on the product information and geographical area information in the request data, and then matches the tenant sharding rules based on the tenant information in the request data, that is, based on the tenant information in the request data, the server 200b The tenant information is searched and matched in each tenant database to obtain the data required to perform relevant insurance business.
  • the server 200b determines that the match with the regional sub-database rules fails, and then matches the tenant sub-database rules based on the medical insurance tenant information in the request data, that is, based on the request data.
  • the tenant information in each tenant database is matched and searched to obtain the data required to execute the city's medical insurance policy and the logical data for executing the business.
  • the organizational structure interception module 203c in the interception matching module 203 obtains the tenant information in the request data, and the tenant rule matching module 203b matches the tenant based on the tenant information.
  • the sharding rules match.
  • the insurance business logic is executed based on the data required to execute the insurance business obtained by the regional sub-database rule; if the successfully matched sub-database rule is a tenant sub-database rule, According to the database rules, the insurance business logic is executed based on the data required to execute the insurance business obtained from the tenant sub-database rules.
  • the data required to execute the insurance business includes at least one of the basic element content data on the policy, logical data for generating the policy, querying the status of the insurance business, or executing the review of the insurance document.
  • the business logic for generating a policy will be executed based on the data required to generate a city medical insurance policy obtained from the regional sharding rule; if the successfully matched sharding rule is a tenant sharding rule, Database rules, then execute the business logic of generating the policy based on the data required to generate urban medical insurance policies obtained from the tenant sub-database rules.
  • the execution business logic module 204 executes insurance business logic.
  • FIG. 5 shows a schematic structural diagram of a server 200b according to some embodiments of the present application.
  • the server 200b used to execute the multi-tenant data sharding method shown in Figure 4 provided by this application may include one or more processors 201, system memory 202, non-volatile memory (Non -Volatile Memory (NVM) 203, input/output (I/O) device 204, communication interface 205 and for coupling the processor 201, system memory 202, non-volatile memory 203, communication interface 204 and input/output (System control logic 206 for I/O device 205.
  • processors 201 system memory 202
  • non-volatile memory (NVM) 203 Non -Volatile Memory
  • I/O input/output
  • System control logic 206 for I/O device 205.
  • the processor 201 may include one or more single-core or multi-core processors.
  • processor 201 may include any combination of general-purpose processors and special-purpose processors (eg, graphics processors, applications processors, baseband processors, etc.).
  • the processor 201 can be configured to match the regional sharding rules based on the product information and geographical area information in the request data. If the matching fails, match the tenant sharding rules based on the tenant information in the request data. , execute the insurance business logic based on the matching results of the sub-library rules.
  • the system memory 202 is a volatile memory, such as random access memory (Random-Access Memory, RAM), double data rate synchronous dynamic random access memory (Double Data Rate Synchronous Dynamic Random Access Memory, DDR SDRAM), etc.
  • RAM Random-Access Memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • the system memory is used to temporarily store data and/or instructions.
  • the system memory 202 can be used to store the above-mentioned executable program for implementing the multi-tenant data sharding method.
  • Non-volatile memory 203 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions.
  • the non-volatile memory 203 may include any suitable non-volatile memory such as flash memory and/or any suitable non-volatile storage device, such as a hard disk drive (Hard Disk Drive, HDD), optical disk ( Compact Disc (CD), Digital Versatile Disc (DVD), Solid-State Drive (SSD), etc.
  • the non-volatile memory 203 may also be a removable storage medium, such as a Secure Digital (Secure Digital, SD) memory card, etc.
  • system memory 202 and non-volatile memory 203 may include temporary and permanent copies of instructions 207, respectively.
  • Instructions 207 may include, when executed by at least one of the processors 201, causing the server 200 to implement the present application. Please provide program instructions for the multi-tenant data sharding method in each embodiment.
  • Input/output (I/O) device 204 may include a user interface that enables a user to interact with server 200b.
  • the input/output (I/O) device 204 may include an output device such as a display for displaying the software system used in the server 200b, and may also include an input device such as a keyboard, mouse, and touch screen.
  • the maintenance personnel of the server 200b can interact with the server 200b through the user interface and input devices such as keyboard, mouse, and touch screen.
  • Communication interface 205 may include a transceiver for providing a wired or wireless communication interface for server 200b to communicate with any other suitable device over one or more networks.
  • the communication interface 205 can be integrated with other components of the server 200b.
  • the communication interface 205 can be integrated with the processor 201.
  • server 200b may communicate with other devices through communication interface 205.
  • System control logic 206 may include any suitable interface controller to provide any suitable interface to other modules of server 200b.
  • system control logic 206 may include one or more memory controllers to provide an interface to system memory 202 and non-volatile memory 203 .
  • At least one of the processors 201 may be packaged with logic for one or more controllers of the system control logic 206 to form a system in package (SiP). In other embodiments, at least one of the processors 201 may also be integrated on the same chip with the logic of one or more controllers for the system control logic 206 to form a system-on-chip (SoC). ).
  • SiP system in package
  • SoC system-on-chip
  • the server 200b can be any electronic device capable of executing the multi-tenant data sharding method provided by this application, including but not limited to computers, servers, tablets, handheld computers, etc., which are not limited in the embodiments of this application.
  • the structure of the server 200b shown in the embodiment of this application does not constitute a specific limitation on the server 200b.
  • the server 200b may include more or less components than shown in the figures, or some components may be combined, or some components may be separated, or may be arranged differently.
  • the components illustrated may be implemented in hardware, software, or a combination of software and hardware.
  • Embodiments of the mechanisms disclosed in this application may be implemented in hardware, software, firmware, or a combination of these implementation methods.
  • Embodiments of the present application may be implemented as a computer program or program code executing on a programmable system including at least one processor, a storage system (including volatile and non-volatile memory and/or storage elements) , at least one input device and at least one output device.
  • Program code may be applied to input instructions to perform the functions described herein and to generate output information.
  • Output information can be applied to one or more output devices in a known manner.
  • a processing system includes any processor having a processor such as, for example, a Digital Signal Processor (DSP), a microcontroller, an Application Specific Integrated Circuit (ASIC), or a microprocessor. system.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • Program code may be implemented in a high-level procedural language or an object-oriented programming language to communicate with the processing system.
  • assembly language or machine language can also be used to implement program code.
  • the mechanisms described in this application are not limited to the scope of any particular programming language. In either case, the language may be a compiled or interpreted language.
  • the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof.
  • the disclosed embodiments may also be implemented as instructions carried on or stored on one or more transitory or non-transitory machine-readable (e.g., computer-readable) storage media, which may be operated by one or more processors Read and execute.
  • Instructions may be distributed over a network or through other computer-readable media.
  • machine-readable media may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including, but not limited to, floppy disks, optical disks, optical disks, read-only memories (CD-ROMs), magnetic Optical disc, Read Only Memory (ROM), Random Access Memory (RAM), Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Memory Read memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), magnetic or optical card, flash memory, or used to use the Internet to transmit information through electrical, optical, acoustic or other forms of propagation signals (for example, carrier waves, infrared signals, digital signals etc.) tangible machine-readable storage.
  • machine-readable media includes any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, computer).
  • each unit/module mentioned in each device embodiment of this application is a logical unit/module.
  • a logical unit/module can be a physical unit/module, or it can be a physical unit/module.
  • Part of the module can also be implemented as a combination of multiple physical units/modules.
  • the physical implementation of these logical units/modules is not the most important.
  • the combination of functions implemented by these logical units/modules is what solves the problem of this application. Key technical issues raised.
  • the above-mentioned equipment embodiments of this application do not introduce units/modules that are not closely related to solving the technical problems raised by this application. This does not mean that the above-mentioned equipment embodiments do not exist. Other units/modules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

La présente demande se rapporte à un procédé d'attribution de base de données de données multilocataires, et à un produit-programme et à un dispositif électronique. Le procédé consiste : à acquérir une demande d'exécution d'un service d'assurance ; sur la base d'informations de produit et d'informations de région géographique dans la demande, à mettre en correspondance la demande avec des informations de base de données de région d'une base de données de gestion de produit ; lorsque des informations de base de données de région sont mises en correspondance, à acquérir une règle de configuration de produit à partir d'une base de données de région de produit, et à acquérir, selon la règle de configuration de produit, des données qui sont requises pour exécuter le service d'assurance ; et lorsque les informations de base de données de région ne sont pas mises en correspondance, à acquérir des informations de locataire dans la demande, et à acquérir, à partir d'une base de données de locataire, les données qui sont requises pour exécuter le service d'assurance. Dans la solution technique de la présente demande, des informations de région géographique sont combinées à une règle d'attribution de base de données, de telle sorte que le problème d'une défaillance pour traiter un service d'assurance dû à l'accès à la même base de données uniquement selon une règle d'attribution de base de données multilocataires unique peut être efficacement évité.
PCT/CN2023/095171 2022-06-07 2023-05-19 Procédé d'attribution de base de données de données multilocataires, et produit-programme et dispositif électronique WO2023236756A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210637186.6 2022-06-07
CN202210637186.6A CN115080537B (zh) 2022-06-07 2022-06-07 多租户的数据分库方法、装置、存储介质、芯片装置及电子设备

Publications (1)

Publication Number Publication Date
WO2023236756A1 true WO2023236756A1 (fr) 2023-12-14

Family

ID=83252286

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/095171 WO2023236756A1 (fr) 2022-06-07 2023-05-19 Procédé d'attribution de base de données de données multilocataires, et produit-programme et dispositif électronique

Country Status (2)

Country Link
CN (1) CN115080537B (fr)
WO (1) WO2023236756A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115080537B (zh) * 2022-06-07 2023-11-10 易保网络技术(上海)有限公司 多租户的数据分库方法、装置、存储介质、芯片装置及电子设备
CN116401231B (zh) * 2023-03-20 2024-04-26 一临云(深圳)科技有限公司 数据源管理方法、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180176176A1 (en) * 2016-12-21 2018-06-21 International Business Machines Corporation Dns resolution of overlapping domains in a mutli-tenant computing environment
CN112367408A (zh) * 2021-01-13 2021-02-12 树根互联技术有限公司 一种物联网多租户数据的管理系统及方法
CN112860451A (zh) * 2021-01-21 2021-05-28 中国建设银行股份有限公司 一种基于SaaS的多租户数据处理方法和装置
CN112905708A (zh) * 2021-03-31 2021-06-04 浙江太美医疗科技股份有限公司 基于SaaS系统的数据库操作方法及系统
CN115080537A (zh) * 2022-06-07 2022-09-20 易保网络技术(上海)有限公司 多租户的数据分库方法、程序产品及电子设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8423524B1 (en) * 2008-09-12 2013-04-16 Salesforce.Com, Inc. System, method and computer program product for storing reports for use by tenants of a multi-tenant on-demand database service
US11222035B2 (en) * 2020-03-03 2022-01-11 Sap Se Centralized multi-tenancy as a service in cloud-based computing environment
CN113239047A (zh) * 2021-05-24 2021-08-10 中国建设银行股份有限公司 一种分库配置方法、业务处理方法、装置及设备
CN114547043A (zh) * 2022-02-28 2022-05-27 山东浪潮通软信息科技有限公司 多租户场景下的应用系统分库分表方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180176176A1 (en) * 2016-12-21 2018-06-21 International Business Machines Corporation Dns resolution of overlapping domains in a mutli-tenant computing environment
CN112367408A (zh) * 2021-01-13 2021-02-12 树根互联技术有限公司 一种物联网多租户数据的管理系统及方法
CN112860451A (zh) * 2021-01-21 2021-05-28 中国建设银行股份有限公司 一种基于SaaS的多租户数据处理方法和装置
CN112905708A (zh) * 2021-03-31 2021-06-04 浙江太美医疗科技股份有限公司 基于SaaS系统的数据库操作方法及系统
CN115080537A (zh) * 2022-06-07 2022-09-20 易保网络技术(上海)有限公司 多租户的数据分库方法、程序产品及电子设备

Also Published As

Publication number Publication date
CN115080537B (zh) 2023-11-10
CN115080537A (zh) 2022-09-20

Similar Documents

Publication Publication Date Title
US20240045877A1 (en) Facilitating queries of encrypted sensitive data via encrypted variant data objects
WO2023236756A1 (fr) Procédé d'attribution de base de données de données multilocataires, et produit-programme et dispositif électronique
CN107209787B (zh) 提高专用加密数据的搜索能力
US11328083B2 (en) Facilitating entity resolution via secure entity resolution database
CN106776780B (zh) 一种云环境中数据交换与共享方法及系统
US20190138498A1 (en) Resolving in-memory foreign keys in transmitted data packets from single-parent hierarchies
US11394764B2 (en) System and method for anonymously transmitting data in a network
US11388148B2 (en) System and method of anonymous sending of data from a user device to a recipient device
CN113094334A (zh) 基于分布式存储的数字服务方法、装置、设备及储存介质
US11397833B2 (en) System and method for anonymously collecting malware related data from client devices
US9002870B2 (en) System, method and computer program product for EDI-to-EDI translations
EP3716124B1 (fr) Système et procédé de transmission de données confidentielles
JP7351685B2 (ja) 情報連携システム、情報連携方法及びアクセス制御サーバ
US11151110B2 (en) Identification of records for post-cloning tenant identifier translation
CN115022242B (zh) 网络层识别方法、装置、计算机设备和存储介质
JP7399838B2 (ja) 情報処理方法、情報処理システム及びコンピュータプログラム
CN113194127B (zh) 一种数据存储方法、数据传输方法及计算设备
EP3872668A1 (fr) Système et procédé d'envoi anonyme de données d'un dispositif d'utilisateur vers un dispositif récepteur
EP3757845A1 (fr) Systèmes et procédés de routage de données anonyme et cohérent dans une architecture client-serveur
US20220044215A1 (en) Consumer controlled sharing of details of retail transactions
CN115705435A (zh) 云服务的数据处理的方法、装置、设备及介质
JP2010272082A (ja) 情報共有システム、情報共有方法、および情報共有プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23818921

Country of ref document: EP

Kind code of ref document: A1